text:
login: allow LoginProvisionedDevice engine to skip online UPAK checks

This lets login offline work in all the cases I tried.
cc @maxtaco @patrickxb @keybase/y2ksquad
Issue: Y2K-927
reviewers: surya for go, @keybase/react-hackers for a single line of TS.

Check the CI failures, they could be legit.  Assuming this passes all tests, LGTM.

same test failed in two CI runs, I agree maybe legit. Will look into them.

@patrickxb I fixed this by changing the behavior of staleOK in the UPAK loader. Do you know if there is anything that relies on that being a short circuit / not even trying the network? If so, I can add a different parameter to the UPAK loader to do that instead; it does seem like the new behavior should be the correct behavior based on the naming though. I had misunderstood what the parameters did as what they now do, based on their names..

Please be super careful here. This exists so you can open the app offline. Why change it? Also the caching is really really hard to get right.

@patrickxb I fixed this by changing the behavior of staleOK in the UPAK loader. Do you know if there is anything that relies on that being a short circuit / not even trying the network? If so, I can add a different parameter to the UPAK loader to do that instead; it does seem like the new behavior should be the correct behavior based on the naming though. I had misunderstood what the parameters did as what they now do, based on their names..

My hope is that we have sufficient tests surrounding all of this.
Changing the behavior of StaleOK sounds precarious.  I'm sure we rely on it not hitting the network.  That being said, upak loading is pretty complex and adding another flag just increases the matrix of possibilities.
The original loginOffline did not rely on making network calls and handling the failures, it actually just logged you in offline without making any network calls.  I think the strategy of making network calls and failing gracefully will be too slow for a login offline situation (you potentially would have to wait for a network call to timeout).

merging over chat test flake

authors: jakob223 maxtaco patrickxb


text:
Added Manage link to #general infopane when you're an admin

@buoyad

The commits 40d4c90be765...6874eb961e88 introduce visual changes on linux. :mag_right: 17 changed

Changed: Search_result-Twitter_Keybase_You (before) (after)

Changed: Search_result-Twitter_Keybase_Not_Following (before) (after)

Changed: Search_result-Twitter_Keybase_Following (before) (after)

Changed: Search_result-Twitter_Keybase (before) (after)

Changed: Search_result-Twitter (before) (after)

Changed: Search_result-Reddit (before) (after)

Changed: Search_result-Keybase_No_Service_You (before) (after)

Changed: Search_result-Keybase_No_Service_Show_Tracker (before) (after) (diff)
Changed: Search_result-Keybase_No_Service_Not_Following (before) (after) (diff)
Changed: Search_result-Keybase_No_Service_No_Follow (before) (after) (diff)
Changed: Search_result-Keybase_No_Service_Following (before) (after) (diff)
Changed: Search_result-Keybase_No_Service (before) (after) (diff)
Changed: Search_result-Keybase_Git_Hub_No_Fullname (before) (after) (diff)
Changed: Search_result-Keybase_Git_Hub (before) (after) (diff)
Changed: Search_result-Hacker_News (before) (after) (diff)
Changed: Search_result-Git_Hub (before) (after) (diff)
Changed: Search_result-Facebook (before) (after) (diff)

@keybase/react-hackers

The commits are a little dicey so I think danny/team-role-map should be merged in before this

source: gharchive/pull-request

repo: keybase/client

license_type: permissive

license_source: github-api


text:
libdokan: Nicer logging of favorite removals

Just makes logging more precise and informative.

LGTM :thumbsup:

authors: taruti zanderz

repo: keybase/kbfs

license_source: bigquery


text:
tlf_journal: cap the number of revisions seen for journal status

Just the quickest fix I could think of.
Issue: KBFS-1615

lgtm

CI flake is unrelated.

authors: akalin-keybase strib


text:
Client Allocation Request for:

Client Allocation Questions
Core Information

Name:
Website / Social Media:
DataCap Requested: 1TiB
Addresses to be Notarized:
Notary Requested: philippbanhardt

Closing this issue as it is a duplicate

source: gharchive/issue

repo: keyko-io/filecoin-clients-onboarding


text:
setup tools deploys wrong version of tornado

The following code line:
https://github.com/keylime/keylime/blob/e22b10b4567bcad25bbcfe321520d1b16311fcca/setup.py#L113
Results in tornado 6.x being installed (which won't work with python 2). Until Python 3 support has merged, we should pin it using ==4.3 instead of greater than.

Fixed with d46237141be8585d337518ec95f91953c637afff

repo: keylime/keylime


text:
tests: Enable tests run in a container

Enable additional test scenarios exercises using custom built keylime containers.
These container tests are run only on CentOS Stream 9 distro.

FYI, test failure in the container IPv6 test is due to a bug https://github.com/keylime/rust-keylime/issues/763

I am closing this PR. We have decided not to include these container tests in to CI as they are a bit fragile and often failing due to changes unrelated to keylime.


text:
Question on damage computation

Since multithreading is explicitly configured in the current code (with tid in most cases), should this line be explicit about the specific thread as well?
https://github.com/kfrb/Peridynamics.jl/blob/4110dd2c62853464314eb617e95b84697f5276c1/src/peridynamics_base.jl#L869

This can lead to unconsistent sequential and parallel results in computing the damage

Hello @vavrines,
Thank you for reaching out - you have a valid point here.
The calculation of the damage with calc_damage is in the current form, one of the functions that only is correct after an update of the body with update_thread_cache! or update_thread_cache_contact!, respectively.
All the values of the tid dimensions are added to the first index.
https://github.com/kfrb/Peridynamics.jl/blob/9e26b578d00c27668ff9a3865f89f2116ab1c2c9/src/peridynamics_base.jl#L1121-L1136
Unfortunately, the current version of the main branch had a bug, which resulted in inconsistent damage results for the reference results because the update functions were missing.
Please do not hesitate to contact me if you have further questions.

Got it. Overall, I think the package is very well written, thanks for creating it! I guess we can close this now.

authors: kfrb vavrines

license: MIT


text:
🛑 microbin is down

In 4235be2, microbin (https://bin.hmuy.tech) was down:

HTTP code: 502
Response time: 3793 ms

Resolved: microbin is back up in 718caf5 after 21 hours, 53 minutes.

repo: khanhmuy/webstatus


text:
🛑 jellyfin is down

In a591a72, jellyfin (https://jellyfin.hmuy.me) was down:

HTTP code: 0
Response time: 0 ms

Resolved: jellyfin is back up in 424a7ac after 11 minutes.


text:
Sometimes it erros if given special characters

I was not able to reproduce the error. It happened two times both when my query included special characters. It was something like host aborted the connection.. might be a connection error...
Also thanks for making this...it is good

I often have issues with special characters, like quotes, or characters that are interpreted as flags for gpt-cli, such as --.  What is a good solution for this?

Some times i have an issue when pasting AWS CLI help stuff in the model: most likely because off "[]" chars, that can be looked as an array by Python

repo: kharvd/gpt-cli


text:
Contact Us Section Of Homepage

The contact us section of the code isn't looking very pleasing , i wish to make it more appealing to the potential consumers and add value to the website.
I wish to work on this issue.

Hey
I would like to work on this issue.

I would like to fix this issue

I am Praful Nigam. Under GSSOC'24, I would like to work on this issue. Pls assign me this!!

Hello @khushi-joshi-05
I'm proposing an update to the Contact Us section design to enhance its aesthetics and usability. This update will include improvements in colour scheme, typography, layout, and responsiveness.

I would like to work on this issue under GSSoC'24.

Hey @khushi-joshi-05,
Hope you're doing well! I'd like to take on the assignment of enhancing the Contact Us section of the homepage. Given my experience as a content writer, having published over 30 articles on Asiana Times' website and completed numerous content writing internships, I believe I can add significant value to this task. Could you please allocate this to me with the GSSOC tag?

Thanks for assigning me this issue,
I have been tinkering for a good layout, I'll be sending a pull request
soon enough.
On Sun, 23 Jun, 2024, 5:36 pm Sukhbir Singh, @.***>
wrote:

Assigned #66
https://github.com/khushi-joshi-05/Food-ordering-website/issues/66 to
@sukritcharredsoul https://github.com/sukritcharredsoul.
—
Reply to this email directly, view it on GitHub
https://github.com/khushi-joshi-05/Food-ordering-website/issues/66#event-13255538662,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BFYW5KNXWQIZNLBYKLWNPTTZI223LAVCNFSM6AAAAABHQVCX3CVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJTGI2TKNJTHA3DMMQ
.
You are receiving this because you were assigned.Message ID:
<khushi-joshi-05/Food-ordering-website/issue/66/issue_event/13255538662@
github.com>


text:
added dark theme to entire website

Related Issue
Closes #1088
Description
The sun and moon icon are totally toggable and apply dark theme successfully to the entire website
Type of PR

[x] Bug fix
[x] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
https://github.com/user-attachments/assets/a9328f9a-16d1-46b9-8bbe-f18b237e9983
Checklist:

[x] I have performed a self-review of my code
[x] I have read and followed the Contribution Guidelines.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[x] I have commented my code, particularly in hard-to-understand areas.

Additional context:
GSSoC'24

Please review my pull request @khushi-joshi-05 @sunny0625

solve conflicts.


text:
Issue #1320 resolved: Cute Cat Dressing Room

Description 📜
Cute Cat Dressing Room
Fixes #1320

Type of change 📝
Please delete options that are not relevant. In order to tick the check box just put x inside them for example [x] like this

[x] Add a new project

Domain of Contribution 📊
Please delete options that are not relevant. In order to tick the check box just put x inside them for example [x] like this

[x] Project using HTML, CSS & JS

Checklist ✅
Please delete options that are not relevant. In order to tick the check box just put x inside them for example [x] like this

[x] I have performed a self-review of my own code or work.
[x] I have commented on my code, particularly in hard-to-understand areas.
[x] My changes generate no new warnings.
[x] I'm GSSoC'22 contributor

Screenshots / Gif (Recommended) 📸

@khushi-purwar please review my pr

Project in different repo https://github.com/Ayush7614/Bundli-Frontend/pull/700

repo: khushi-purwar/WebDev-ProjectKart


text:
這個樣式... 這個排版...

http://drugs.olc.tw/members/login

自己的issue自己解

在 f2f5ec1 套上Bootstrap的class，比原本的樣式好一些些 :P

阿靠 我完全忘記有這件事了..............

沒關係，我習慣了（攤手） XD

resolved at f2f5ec1a5b77d3305d14dad53ac6eb66323fd421

repo: kiang/drugs


text:
[NT-1674] Email Verification Deeplink

📲 What
Adds a deeplink for /profile/verify_email which will open the app and subsequently be accessed in order to either verify the email address or cause a verification email to be re-sent.
Note: Draft PR as there are some outstanding questions to resolve, see TODOs below.
🤔 Why
This is a continuation of our work to add email verification to the app. One might call this the meat an potatoes of it all.
🛠 How

Added the deeplink to Navigation.
Added a request and response handling flow to AppDelegateViewModel. This is separated from our existing API networking code because it is an ad-hoc response for this purpose.
Displaying a banner on DiscoverViewController with the success/failure message.

✅ Acceptance criteria

[ ] Tap on an email verification link in an email, it should open the app.
[ ] If the token has expired, a new verification email should be sent.
[ ] If successful the banner should be displayed and indicated that.
[ ] If unsuccessful the banner should be displayed and indicated that.

⏰ TODO

[ ] Dismiss EmailVerificationViewController if currently displayed.
[x] Handle 403 specifically?
[x] Add more copy for translation or will back-end send success and re-sent messages.

          1 Warning

:warning:
Big PR

  Generated by :no_entry_sign: Danger

authors: justinswart nativeksr

repo: kickstarter/ios-oss


text:
Adbyby Plus的规则保存位置建议改到/tmp目录

16M闪存空间有限，overlay空间捉襟见肘，现在的adbyby的第三方规则下载地址是overlay空间
希望能下载到/tmp空间，像dnsfilter那样

还有一个dnsmasq.adblock文件，900k+的大小，也要占用overlay空间，根本没有修改过，为什么要在overlay中保存一份呢？

暂时用ln -s  /tmp/rules/ /usr/share/adbyby/rules解决了第三方规则的下载位置问题，dnsmasq.adblock无力解决


text:
X86 最新定制固件 全锥Nat不生效

#809 有提到7.10号的固件全锥问题。
为了升级我重新定制了固件（官网显示版本7.14），从6.18版定制固件不保留配置刷入x86路由并从0配置，刷入后nat从全锥nat1变为全锥nat4（upnp开启且生效，防火墙全锥nat打开）
尝试过重新定制、恢复旧版备份、防火墙强开fullcore全不行。
因为旧版固件我也没保存，只能刷回官网通用的618固件，nat恢复到正常的全锥nat1
至少尝试重新定制了五六次，重新刷机九十次….也在这其中遇到了另一个很蛋疼的问题： #819
麻烦大佬抽空修复一下

装个luci-app-turboacc 看 fullconenat 是否显示运行中

装个luci-app-turboacc 看 fullconenat 是否显示运行中

已经试过了，是显示开启的，也有关闭再重启，依旧是没有生效。包括有个叫luci-app-corefullnat什么来着的插件，也是尝试安装运行了，但是nat还是老样子

好像是 firewall4 的问题 以前的规则对新的防火墙无效 我正在测试 如果有最新进展我会继续跟进回复

我是711那版nat4 714的刚刷好开测试软件 nat3 然后再点test显示nat1 运行一段时间再用软件测 连哪个网址都是unkown 不过实际游戏感觉没啥差别 所以也不知道到底有没有生效

啊 刚才刷回618那版玩了会大乱斗 延迟是13、14ms 昨天用新固件玩是22ms左右 还出现过一次卡顿后67ms的
不确定是单纯的服务器波动还是固件NAT真的有问题

啊 刚才刷回618那版玩了会大乱斗 延迟是13、14ms 昨天用新固件玩是22ms左右 还出现过一次卡顿后67ms的
不确定是单纯的服务器波动还是固件NAT真的有问题

因为我有不少pcdn，对nat的变化很敏感，网心云后台明显看出来在升级新固件后nat下降为端口限制，降级后为原来的全锥，所以应该是有问题的

我是711那版nat4 714的刚刷好开测试软件 nat3 然后再点test显示nat1 运行一段时间再用软件测 连哪个网址都是unkown 不过实际游戏感觉没啥差别 所以也不知道到底有没有生效

unknown可以试试换stun软件和服务器，我记得有两三款，有一款的stun软件有国内小米和QQ的检测服务器，就很快

好像是 firewall4 的问题 以前的规则对新的防火墙无效 我正在测试 如果有最新进展我会继续跟进回复

感谢各位大佬

装个luci-app-turboacc 看 fullconenat 是否显示运行中

大哥不知道能不能定制旧版固件呢，618版本是很正常的，当时定制的固件删了😭

我是711那版nat4 714的刚刷好开测试软件 nat3 然后再点test显示nat1 运行一段时间再用软件测 连哪个网址都是unkown 不过实际游戏感觉没啥差别 所以也不知道到底有没有生效

unknown可以试试换stun软件和服务器，我记得有两三款，有一款的stun软件有国内小米和QQ的检测服务器，就很快

用的是NatTypeTester，有小米和QQ的检测，结果就是我说的那样，下午又上游戏测了下，应该是服务器波动，这个对玩游戏应该是没啥影响，可能会影响到别的吧

装个luci-app-turboacc 看 fullconenat 是否显示运行中

大哥不知道能不能定制旧版固件呢，618版本是很正常的，当时定制的固件删了😭

因为上面有人说是firewall4的问题，所以我在软件列表里卸载了firewall4，然后安装了firewall，下载用软件测是正常的了~你可以试一下

装个luci-app-turboacc 看 fullconenat 是否显示运行中

大哥不知道能不能定制旧版固件呢，618版本是很正常的，当时定制的固件删了😭

因为上面有人说是firewall4的问题，所以我在软件列表里卸载了firewall4，然后安装了firewall，然后用软件测是正常的了~
你可以试一下编译的时候-firewall4 然后再添加firewall

已默认换成了 firewall 可在定制时选择firewall4

已默认换成了 firewall 可在定制时选择firewall4

感谢，我明天试试看

已默认换成了 firewall 可在定制时选择firewall4

已尝试重新定制，刷入后发现防火墙无全锥nat开关，此时网络为nat4。只能下载安装turboacc后开启全锥nat，网络变为nat1正常。
但出现另一个问题openwrt后台upnp里没有内容，类似 #811 ，实测upnp实际上成功了。刚刷入的固件没安装其他可能冲突的插件，都是定制时加入的：
luci-app-frpc luci-app-netdata luci-app-netspeedtest luci-app-ramfree luci-app-sqm luci-app-ttyd luci-app-watchcat luci-app-adguardhome luci-app-serverchan luci-app-vlmcsd luci-app-wrtbwmon luci-app-cifs-mount luci-app-hd-idle luci-app-homebox luci-app-jd-dailybonus luci-app-qbittorrent luci-app-transmission luci-app-unblockmusic luci-app-wolplus luci-app-aria2 luci-app-cloudreve luci-app-attendedsysupgrade luci-app-homeassistant luci-app-nlbwmon luci-app-alist luci-app-rclone luci-app-tencentddns my-autocore-x86 luci-app-dockerman

装个luci-app-turboacc 看 fullconenat 是否显示运行中

大哥不知道能不能定制旧版固件呢，618版本是很正常的，当时定制的固件删了😭

因为上面有人说是firewall4的问题，所以我在软件列表里卸载了firewall4，然后安装了firewall，然后用软件测是正常的了~ 你可以试一下编译的时候-firewall4 然后再添加firewall

确实是firewall4的问题。但是莫名其妙我upnp页面里没数据但实际又是成功了

可以参考这里对firewall4进行Patch

这里

哎，只能下旧版普通固件自己opkg install了

这里

哎，只能下旧版普通固件自己opkg install了

LZ最后解决了吗

authors: JiuyeXD NothingNA Seas0 XYZliang junke kiddin9


text:
When will the ffmpeg be supported in this project for godot4 ?

Just like the wonderful godot-vidoedecoder in godot3.
Thank you!

Hi @kidrigger , ffmpeg GDExtension is really useful in godot4. The only one could compatibly run with godot3 I found on the internet is your godot-vidoedecoder. Unfortunately it is a gdnative version and gdnative is not support by godot4 (according to the docs of godot4).
Could you please tell me what's your plan to support ffmpeg in godot4 gdextension?  Or, Is it possible to reuse your work (godot-vidoedecoder)  in godot4 ? Is there a way to use gdnative in godot4 ?
Thanks again for your OUTSTANDING works in this field !   👍   :)

Hi!
I have just started working on the FFmpeg port. I'll link to the new repo as soon as it is up.
Lot of mistakes were made in godot-videodecoder so I can't do a direct port.

Awesome! That is the greatest news I heard today !!!
Hoping everything goes well. Just can't wait to see your new works.  Haha.  👍

I have just started working on the FFmpeg port. I'll link to the new repo as soon as it is up.
Lot of changes from the API so I think it's better to have a full rewrite.

Hi @kidrigger , hoping this message finds you well!  I wonder is there any progress on this project ?  Is there anything I can help?

Currently I have to fix a synchronization bug (audio and video can independently play if I discard frames) once that's done, the plugin should work (albeit inefficiently)
Then I will start optimizing the thing. Sorry for taking the time, I had other priorities to take care of.
I will be focused on this for the next two weeks. You can track the progress here. Please suggest changes if required. (Look at the wip-loader branch)
https://github.com/kidrigger/godot-video-ffmpeg
There's a bit of currently unnecessary wrapping being done but I faced a lot of trouble in godot-videodecoder because I didn't do this. FFmpeg has a lot of reference counting that is better handled with this.
Currently the program is Linux only (possibly MacOS) but doesn't work on windows (due to dlopen) dependency.

Thanks @kidrigger , for FFMpeg - such a complicated project - it's definitely sure we will meet troubles on the way to building a usable GDextension. Please don't worry about the inefficiency or any other little problems. You could polish the extension little by little just like the release the godot engine 4.0. And ultimately you'll provide the community a nice tool on multi-formats audio/video handling. I'm looking forward to your new project and hoping you good luck on the development.  :)

I'm not sure if you intended to have the https://github.com/kidrigger/godot-video-ffmpeg repository public at this point, but if so it doesn't seem to exist as far as I can tell.

Thanks for your great work @kidrigger. I have been trying to make a ffmpeg extension as well but having issues at the frame data conversion stage. Any chance I can take a look at your version to see where I went worng? Your repo is private at time of this post.

@kidrigger Hi Kidrigger, is there any progress on this repo's development ?  As several weeks passed, I was always hoping everything's going well. Looking forward to your productive GDextension.   ;-)

Sorry, I can't currently work on this project.
I'll get back to this shortly. But I don't want to make promises I may not be able to follow up with.
I sincerely apologize for the inconvenience caused.
I'll post an update whenever I can recover my work, and restart.
@htang63 Please find the WIP code here, but the code for frame data conversion is not there yet.
For the resampling code, you can refer to the old plugin

I have released my own ffmpeg code, if anyone wants to take a look at it: https://github.com/EIRTeam/EIRTeam.FFmpeg

authors: EIREXE cyberpsyche ecurtz htang63 kidrigger

repo: kidrigger/godot-video-reference


text:
[KOGITO-6979] Added IT to check that we can use JQ expression inside …

…workflows
Signed-off-by: Davide Salerno dsalerno@redhat.com
See: https://issues.redhat.com/browse/KOGITO-6979
Many thanks for submitting your Pull Request :heart:!

Summary of the changes in this PR

This PR will add an integration test that will let us be confident about the fact that we can use jq for expressions inside Kogito services developed using Quarkus and containerized into a docker image without a jq binary.
Everything will work because we are using jackson-jq that is a pure Java implementation of jq and so no native jq binary is needed inside the docker image.

Please make sure that your PR meets the following requirements:

[x] You have read the contributors guide
[x] Your code is properly formatted according to this configuration
[x] Pull Request title is properly formatted: KOGITO-XYZ Subject
[x] Pull Request title contains the target branch if not targeting main: [0.9.x] KOGITO-XYZ Subject
[x] Pull Request contains link to the JIRA issue
[x] Pull Request contains link to any dependent or related Pull Request
[x] Pull Request contains description of the issue
[x] Pull Request does not include fixes for issues other than the main ticket

How to replicate CI configuration locally?

Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use build-chain tool to handle cross repository builds and be sure that we always use latest version of the code for each repository.
build-chain tool is a build tool which can be used on command line locally or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See local execution details to get more information about it.

How to retest this PR or trigger a specific build:

Run all builds
Please add comment: Jenkins retest this

Run (or rerun) specific test(s)
Please add comment: Jenkins (re)run [kogito-runtimes|optaplanner|kogito-apps|kogito-examples|optaplanner-quickstarts|optaweb-employee-rostering|optaweb-vehicle-routing] tests

Quarkus LTS checks
Please add comment: Jenkins run LTS

Run (or rerun) LTS specific test(s)
Please add comment: Jenkins (re)run [kogito-runtimes|optaplanner|kogito-apps|kogito-examples|optaplanner-quickstarts|optaweb-employee-rostering|optaweb-vehicle-routing] LTS

Native checks
Please add comment: Jenkins run native

Run (or rerun) native specific test(s)
Please add comment: Jenkins (re)run [kogito-runtimes|optaplanner|kogito-apps|kogito-examples|optaplanner-quickstarts|optaweb-employee-rostering|optaweb-vehicle-routing] native

Full Kogito testing (with cloud images and operator BDD testing)
Please add comment: Jenkins run BDD
This check should be used only if a big change is done as it takes time to run, need resources and one full BDD tests check can be done at a time ...

(tests) - kogito-apps job #1573 was: FAILURE
Possible explanation: Pipeline failure or project build failure
Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-runtimes.tests.downstream.kogito-apps/1573/display/redirect or see console log:

Console Logs
Checking out Revision b844f47b3febcc273841e554486088d18b72b704 (origin/main) > git config core.sparsecheckout # timeout=10 > git checkout -f b844f47b3febcc273841e554486088d18b72b704 # timeout=10Commit message: "Correct Repo seeds (#425)" > git rev-list --no-walk b844f47b3febcc273841e554486088d18b72b704 # timeout=10Loading library jenkins-pipeline-shared-libraries@mainAttempting to resolve main from remote references... > git --version # timeout=10 > git --version # 'git version 1.8.3.1'using GIT_SSH to set credentials SSH: kie-ci service account with access to jboss-integration private github space[INFO] Currently running in a labeled security context > /usr/bin/chcon --type=ssh_home_t /tmp/jenkins-gitclient-ssh392147952062519499.key > git ls-remote -h https://github.com/kiegroup/jenkins-pipeline-shared-libraries # timeout=10Found match: refs/heads/main revision 21afeeac35a851b46d694688c2562d914fab8e63The recommended git tool is: NONEusing credential kie-ci-user-key > git rev-parse --resolve-git-dir /var/lib/jenkins/jobs/KIE/jobs/kogito/jobs/main/jobs/pullrequest/jobs/kogito-runtimes.tests.downstream.kogito-apps/workspace@libs/jenkins-pipeline-shared-libraries/.git # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/kiegroup/jenkins-pipeline-shared-libraries # timeout=10Fetching without tagsFetching upstream changes from https://github.com/kiegroup/jenkins-pipeline-shared-libraries > git --version # timeout=10 > git --version # 'git version 1.8.3.1'using GIT_SSH to set credentials SSH: kie-ci service account with access to jboss-integration private github space[INFO] Currently running in a labeled security context > /usr/bin/chcon --type=ssh_home_t /var/lib/jenkins/jobs/KIE/jobs/kogito/jobs/main/jobs/pullrequest/jobs/kogito-runtimes.tests.downstream.kogito-apps/workspace@libs/jenkins-pipeline-shared-libraries@tmp/jenkins-gitclient-ssh1110545512718132671.key > git fetch --no-tags --progress https://github.com/kiegroup/jenkins-pipeline-shared-libraries +refs/heads/*:refs/remotes/origin/* # timeout=10Checking out Revision 21afeeac35a851b46d694688c2562d914fab8e63 (main) > git config core.sparsecheckout # timeout=10 > git checkout -f 21afeeac35a851b46d694688c2562d914fab8e63 # timeout=10Commit message: "pmebuild cleanScript (#188)" > git rev-list --no-walk 21afeeac35a851b46d694688c2562d914fab8e63 # timeout=10[Pipeline] Start of Pipeline[Pipeline] nodeRunning on rhos-01-kie-psi-rhel7-xlarge-5751 in /home/jenkins/workspace/KIE/kogito/main/pullrequest/kogito-runtimes.tests.downstream.kogito-apps[Pipeline] {[Pipeline] stage[Pipeline] { (Declarative: Checkout SCM)[Pipeline] checkoutThe recommended git tool is: NONEusing credential kie-ciCloning the remote Git repositoryAvoid second fetchChecking out Revision b844f47b3febcc273841e554486088d18b72b704 (origin/main)Commit message: "Correct Repo seeds (#425)"[Pipeline] }[Pipeline] // stage[Pipeline] withEnv[Pipeline] {[Pipeline] withEnv[Pipeline] {[Pipeline] timestamps[Pipeline] {[Pipeline] timeout[2022-04-27T15:42:32.064Z] Timeout set to expire in 3 hr 30 min[Pipeline] {[Pipeline] stage[Pipeline] { (Declarative: Tool Install)[Pipeline] tool[Pipeline] envVarsForTool[Pipeline] }[Pipeline] // stage[Pipeline] withEnvCloning repository https://github.com/kiegroup/kogito-pipelines.git > git init /home/jenkins/workspace/KIE/kogito/main/pullrequest/kogito-runtimes.tests.downstream.kogito-apps # timeout=10Fetching upstream changes from https://github.com/kiegroup/kogito-pipelines.git > git --version # timeout=10 > git --version # 'git version 2.34.1'using GIT_ASKPASS to set credentials PSSWD: kie-ci service account with access to jboss-integration private github space > git fetch --tags --force --progress -- https://github.com/kiegroup/kogito-pipelines.git +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url https://github.com/kiegroup/kogito-pipelines.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git rev-parse origin/main^{commit} # timeout=10 > git config core.sparsecheckout # timeout=10 > git checkout -f b844f47b3febcc273841e554486088d18b72b704 # timeout=10[Pipeline] {[Pipeline] stage[Pipeline] { (Initialize)[Pipeline] tool[Pipeline] envVarsForTool[Pipeline] withEnv[Pipeline] {[Pipeline] script[Pipeline] {[Pipeline] sh[2022-04-27T15:42:32.822Z] + printenv[Pipeline] archiveArtifacts[2022-04-27T15:42:32.845Z] Archiving artifacts[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (check space before build)[Pipeline] tool[Pipeline] envVarsForTool[Pipeline] withEnv[Pipeline] {[Pipeline] script[Pipeline] {[Pipeline] dir[2022-04-27T15:42:33.423Z] Running in /home/jenkins/workspace/KIE/kogito/main/pullrequest/kogito-runtimes.tests.downstream.kogito-apps[Pipeline] {[Pipeline] echo[2022-04-27T15:42:33.451Z] [INFO] space left on the machine[Pipeline] sh[2022-04-27T15:42:33.749Z] + df -h[2022-04-27T15:42:33.749Z] Filesystem      Size  Used Avail Use% Mounted on[2022-04-27T15:42:33.749Z] devtmpfs        7.8G     0  7.8G   0% /dev[2022-04-27T15:42:33.749Z] tmpfs           7.8G     0  7.8G   0% /dev/shm[2022-04-27T15:42:33.749Z] tmpfs           7.8G   17M  7.8G   1% /run[2022-04-27T15:42:33.749Z] tmpfs           7.8G     0  7.8G   0% /sys/fs/cgroup[2022-04-27T15:42:33.749Z] /dev/vda1        80G   18G   63G  23% /[2022-04-27T15:42:33.749Z] tmpfs           1.6G     0  1.6G   0% /run/user/1000[Pipeline] echo[2022-04-27T15:42:33.768Z] [INFO] space of /home/jenkins[Pipeline] sh[2022-04-27T15:42:34.063Z] + du -h -d1 /home/jenkins[2022-04-27T15:42:34.063Z] 4.0K	/home/jenkins/.ssh[2022-04-27T15:42:34.063Z] 0	/home/jenkins/go[2022-04-27T15:42:34.063Z] 8.0K	/home/jenkins/.vnc[2022-04-27T15:42:34.063Z] 19M	/home/jenkins/.m2[2022-04-27T15:42:34.063Z] 2.1G	/home/jenkins/git-repos[2022-04-27T15:42:34.063Z] 8.0K	/home/jenkins/.config[2022-04-27T15:42:34.063Z] 4.0K	/home/jenkins/.cekit[2022-04-27T15:42:34.063Z] 80M	/home/jenkins/virtenvs[2022-04-27T15:42:34.063Z] 31M	/home/jenkins/remoting[2022-04-27T15:42:34.063Z] 0	/home/jenkins/.cache[2022-04-27T15:42:34.063Z] 2.2M	/home/jenkins/workspace[2022-04-27T15:42:34.063Z] 0	/home/jenkins/.pki[2022-04-27T15:42:34.063Z] 117M	/home/jenkins/tools[2022-04-27T15:42:34.063Z] 0	/home/jenkins/caches[2022-04-27T15:42:34.063Z] 24M	/home/jenkins/.npm[2022-04-27T15:42:34.063Z] 2.4G	/home/jenkins[Pipeline] echo[2022-04-27T15:42:34.091Z] [INFO] space of workspace[Pipeline] sh[2022-04-27T15:42:34.376Z] + du -h -d3 /home/jenkins/workspace[2022-04-27T15:42:34.377Z] 0	/home/jenkins/workspace/KIE/kogito/1.21.x[2022-04-27T15:42:34.377Z] 2.2M	/home/jenkins/workspace/KIE/kogito/main[2022-04-27T15:42:34.377Z] 2.2M	/home/jenkins/workspace/KIE/kogito[2022-04-27T15:42:34.377Z] 2.2M	/home/jenkins/workspace/KIE[2022-04-27T15:42:34.377Z] 2.2M	/home/jenkins/workspace[Pipeline] }[Pipeline] // dir[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Install build-chain tool)[Pipeline] tool[Pipeline] envVarsForTool[Pipeline] withEnv[Pipeline] {[Pipeline] script[Pipeline] {[Pipeline] echo[2022-04-27T15:42:34.710Z] [INFO] Getting build-chain version from composite action file[Pipeline] readFile[Pipeline] echo[2022-04-27T15:42:34.805Z] [INFO] build-chain version recovered '2.3.34'[Pipeline] sh[2022-04-27T15:42:35.117Z] + npm install -g @kie/build-chain-action@2.3.34 -registry=https://repository.engineering.redhat.com/nexus/repository/registry.npmjs.org/[2022-04-27T15:42:37.010Z] /home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-12.16.3/bin/build-chain-action -> /home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-12.16.3/lib/node_modules/@kie/build-chain-action/bin/build-chain-cli.js[2022-04-27T15:42:37.010Z] npm WARN notsup Unsupported engine for @kie/build-chain-action@2.3.34: wanted: {"node":">= 12.18.0"} (current: {"node":"12.16.3","npm":"6.14.4"})[2022-04-27T15:42:37.010Z] npm WARN notsup Not compatible with your version of node/npm: @kie/build-chain-action@2.3.34[2022-04-27T15:42:37.010Z] npm WARN @octokit/plugin-request-log@1.0.4 requires a peer of @octokit/core@>=3 but none is installed. You must install peer dependencies yourself.[2022-04-27T15:42:37.010Z] [2022-04-27T15:42:37.010Z] + @kie/build-chain-action@2.3.34[2022-04-27T15:42:37.010Z] updated 1 package in 1.357s[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Build projects)[Pipeline] tool[Pipeline] envVarsForTool[Pipeline] tool[Pipeline] envVarsForTool[Pipeline] tool[Pipeline] envVarsForTool[Pipeline] withEnv[Pipeline] {[Pipeline] script[Pipeline] {[Pipeline] configFileProvider[2022-04-27T15:42:37.406Z] provisioning config files...[2022-04-27T15:42:37.411Z] copy managed file [kogito_pr_settings] to file:/home/jenkins/workspace/KIE/kogito/main/pullrequest/kogito-runtimes.tests.downstream.kogito-apps@tmp/config7193497513971508939tmp[Pipeline] {[Pipeline] withCredentials[2022-04-27T15:42:37.460Z] Masking supported pattern matches of $GITHUB_TOKEN[Pipeline] {[Pipeline] sh[2022-04-27T15:42:37.492Z] Warning: A secret was passed to "sh" using Groovy String interpolation, which is insecure.[2022-04-27T15:42:37.492Z] 		 Affected argument(s) used the following variable(s): [GITHUB_TOKEN][2022-04-27T15:42:37.492Z] 		 See https://jenkins.io/redirect/groovy-string-interpolation for details.[2022-04-27T15:42:37.764Z] + build-chain-action -token=**** -df=https://raw.githubusercontent.com/kiegroup/kogito-pipelines/main/.ci/pull-request-config.yaml -folder=bc build pr -url=https://github.com/kiegroup/kogito-runtimes/pull/2176 -sp=kiegroup/kogito-apps --skipParallelCheckout -cct '(^mvn .*)||$1 -s /home/jenkins/workspace/KIE/kogito/main/pullrequest/kogito-runtimes.tests.downstream.kogito-apps@tmp/config7193497513971508939tmp -Dmaven.wagon.http.ssl.insecure=true -Dmaven.test.failure.ignore=true'[2022-04-27T15:42:38.327Z] [INFO]  Executing pull request flow for https://github.com/kiegroup/kogito-runtimes/pull/2176 in bc[2022-04-27T15:42:38.584Z] [INFO]  https://raw.githubusercontent.com/kiegroup/kogito-pipelines/main/.ci/pull-request-config.yaml exists, using it[2022-04-27T15:42:38.584Z] ::group::[PRE] Executing pre section for https://raw.githubusercontent.com/kiegroup/kogito-pipelines/main/.ci/pull-request-config.yaml[2022-04-27T15:42:38.584Z] [INFO]  Execute command 'export BUILD_MVN_OPTS=" -nsu -ntp -fae -e -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false dependency:tree -Dmaven.wagon.httpconnectionManager.ttlSeconds=120 -Dmaven.wagon.http.retryHandler.count=3"' in dir '/home/jenkins/workspace/KIE/kogito/main/pullrequest/kogito-runtimes.tests.downstream.kogito-apps'[2022-04-27T15:42:38.584Z] [INFO]  Treating export command since it's not possible to run it from the runner itself[2022-04-27T15:42:38.584Z] [INFO]  The variable BUILD_MVN_OPTS has been stored with ' -nsu -ntp -fae -e -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false dependency:tree -Dmaven.wagon.httpconnectionManager.ttlSeconds=120 -Dmaven.wagon.http.retryHandler.count=3' value[2022-04-27T15:42:38.584Z] ::notice title= [PRE] [Execution OK]::export BUILD_MVN_OPTS=" -nsu -ntp -fae -e -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false dependency:tree -Dmaven.wagon.httpconnectionManager.ttlSeconds=120 -Dmaven.wagon.http.retryHandler.count=3"[2022-04-27T15:42:38.584Z] [INFO]  Execute command 'echo "BUILD_MVN_OPTS= -nsu -ntp -fae -e -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false dependency:tree -Dmaven.wagon.httpconnectionManager.ttlSeconds=120 -Dmaven.wagon.http.retryHandler.count=3"' in dir '/home/jenkins/workspace/KIE/kogito/main/pullrequest/kogito-runtimes.tests.downstream.kogito-apps'[2022-04-27T15:42:38.584Z] [command]/usr/bin/echo BUILD_MVN_OPTS= -nsu -ntp -fae -e -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false dependency:tree -Dmaven.wagon.httpconnectionManager.ttlSeconds=120 -Dmaven.wagon.http.retryHandler.count=3[2022-04-27T15:42:38.585Z] BUILD_MVN_OPTS= -nsu -ntp -fae -e -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false dependency:tree -Dmaven.wagon.httpconnectionManager.ttlSeconds=120 -Dmaven.wagon.http.retryHandler.count=3[2022-04-27T15:42:38.585Z] ::notice title= [PRE] [Execution OK]::echo "BUILD_MVN_OPTS= -nsu -ntp -fae -e -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false dependency:tree -Dmaven.wagon.httpconnectionManager.ttlSeconds=120 -Dmaven.wagon.http.retryHandler.count=3"[2022-04-27T15:42:38.585Z] ::endgroup::[2022-04-27T15:42:38.841Z] ::group::[Pull Request Flow] Execution Plan...[2022-04-27T15:42:38.841Z] [INFO]  ----------------------------------------------[2022-04-27T15:42:38.841Z] [INFO]  [4] projects will be executed[2022-04-27T15:42:38.841Z] [2022-04-27T15:42:38.841Z] [INFO]  [kiegroup/drools][2022-04-27T15:42:38.841Z] [INFO]  Level Type: [upstream].[2022-04-27T15:42:38.841Z] [INFO]  mvn clean install -Dquickly ${{ env.BUILD_MVN_OPTS }} ${{ env.BUILD_MVN_OPTS_UPSTREAM }} ${{ env.DROOLS_BUILD_MVN_OPTS_UPSTREAM }}[2022-04-27T15:42:38.841Z] [INFO]  [ 'docker system prune -f' ][2022-04-27T15:42:38.841Z] [2022-04-27T15:42:38.841Z] [INFO]  [kiegroup/kogito-runtimes][2022-04-27T15:42:38.841Z] [INFO]  Level Type: [upstream].[2022-04-27T15:42:38.841Z] [INFO]  mvn clean install -Dquickly ${{ env.BUILD_MVN_OPTS }} ${{ env.BUILD_MVN_OPTS_UPSTREAM }} ${{ env.KOGITO_RUNTIMES_BUILD_MVN_OPTS_UPSTREAM }}[2022-04-27T15:42:38.841Z] [INFO]  [ 'docker system prune -f' ][2022-04-27T15:42:38.841Z] [2022-04-27T15:42:38.841Z] [INFO]  [kiegroup/optaplanner][2022-04-27T15:42:38.841Z] [INFO]  Level Type: [upstream].[2022-04-27T15:42:38.841Z] [INFO]  mvn clean install -Dquickly ${{ env.BUILD_MVN_OPTS }} ${{ env.BUILD_MVN_OPTS_UPSTREAM }} ${{ env.OPTAPLANNER_BUILD_MVN_OPTS_UPSTREAM }}[2022-04-27T15:42:38.841Z] [INFO]  [ 'docker system prune -f' ][2022-04-27T15:42:38.841Z] [2022-04-27T15:42:38.841Z] [INFO]  [kiegroup/kogito-apps][2022-04-27T15:42:38.841Z] [INFO]  Level Type: [current].[2022-04-27T15:42:38.841Z] [INFO]  [[2022-04-27T15:42:38.841Z]   'mvn -f kogito-apps/pom.xml clean install -Dvalidate-formatting ${{ env.BUILD_MVN_OPTS }} ${{ env.BUILD_MVN_OPTS_CURRENT }} ${{ env.KOGITO_APPS_BUILD_MVN_OPTS }}'[2022-04-27T15:42:38.841Z] ][2022-04-27T15:42:38.841Z] [INFO]  [ 'docker system prune -f' ][2022-04-27T15:42:38.841Z] [2022-04-27T15:42:38.841Z] [INFO]  ----------------------------------------------[2022-04-27T15:42:38.841Z] ::endgroup::[2022-04-27T15:42:38.841Z] ::group::[Pull Request Flow] Checking out kiegroup/kogito-runtimes and its dependencies[2022-04-27T15:42:38.841Z] [INFO]  Tree for project kiegroup/kogito-apps. Dependencies: [2022-04-27T15:42:38.841Z] kiegroup/drools,[2022-04-27T15:42:38.841Z] kiegroup/kogito-runtimes,[2022-04-27T15:42:38.841Z] kiegroup/optaplanner,[2022-04-27T15:42:38.841Z] kiegroup/kogito-apps[2022-04-27T15:42:38.841Z] [INFO]  [kiegroup/drools] Checking out project[2022-04-27T15:42:38.841Z] [WARN]  davidesalerno/drools not found. Trying to get it by forked project list.[2022-04-27T15:43:17.563Z] [ERROR]  You have exceeded a secondary rate limit. Please wait a few minutes before you try again.[Pipeline] }[Pipeline] // withCredentials[Pipeline] }[2022-04-27T15:43:17.624Z] Deleting 1 temporary files[Pipeline] // configFileProvider[Pipeline] }[Pipeline] // scriptPost stage[Pipeline] junit[2022-04-27T15:43:17.704Z] Recording test results[2022-04-27T15:43:17.711Z] No test report files were found. Configuration error?Error when executing always post condition:Also:   hudson.remoting.Channel$CallSiteStackTrace: Remote call to rhos-01-kie-psi-rhel7-xlarge-5751		at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1797)		at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356)		at hudson.remoting.Channel.call(Channel.java:1001)		at hudson.FilePath.act(FilePath.java:1166)		at hudson.FilePath.act(FilePath.java:1155)		at hudson.tasks.junit.JUnitParser.parseResult(JUnitParser.java:107)		at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:153)		at hudson.tasks.junit.JUnitResultArchiver.parseAndSummarize(JUnitResultArchiver.java:247)		at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:63)		at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:29)		at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)		at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)		at java.util.concurrent.FutureTask.run(FutureTask.java:266)		at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)		at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)		at java.lang.Thread.run(Thread.java:748)hudson.AbortException: No test report files were found. Configuration error?	at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:154)	at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3338)	at hudson.remoting.UserRequest.perform(UserRequest.java:211)	at hudson.remoting.UserRequest.perform(UserRequest.java:54)	at hudson.remoting.Request$2.run(Request.java:376)	at hudson.remoting.InterceptingExecutorService.lambda$wrap$0(InterceptingExecutorService.java:78)	at java.util.concurrent.FutureTask.run(FutureTask.java:266)	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)	at java.lang.Thread.run(Thread.java:750)[Pipeline] script[Pipeline] {[Pipeline] sh[2022-04-27T15:43:18.126Z] + rm -rf console.log[Pipeline] sh

(tests) - kogito-runtimes job #1525 was: FAILURE
Possible explanation: Pipeline failure or project build failure
Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-runtimes.tests.kogito-runtimes/1525/display/redirect or see console log:

Console Logs
Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10Fetching upstream changes from https://github.com/kiegroup/kogito-pipelines.git > git --version # timeout=10 > git --version # 'git version 1.8.3.1'using GIT_ASKPASS to set credentials PSSWD: kie-ci service account with access to jboss-integration private github space > git fetch --tags --progress https://github.com/kiegroup/kogito-pipelines.git +refs/heads/*:refs/remotes/origin/* # timeout=10 > git rev-parse origin/main^{commit} # timeout=10Checking out Revision b844f47b3febcc273841e554486088d18b72b704 (origin/main) > git config core.sparsecheckout # timeout=10 > git checkout -f b844f47b3febcc273841e554486088d18b72b704 # timeout=10Commit message: "Correct Repo seeds (#425)" > git rev-list --no-walk b844f47b3febcc273841e554486088d18b72b704 # timeout=10Loading library jenkins-pipeline-shared-libraries@mainAttempting to resolve main from remote references... > git --version # timeout=10 > git --version # 'git version 1.8.3.1'using GIT_SSH to set credentials SSH: kie-ci service account with access to jboss-integration private github space[INFO] Currently running in a labeled security context > /usr/bin/chcon --type=ssh_home_t /tmp/jenkins-gitclient-ssh4047587582825615102.key > git ls-remote -h https://github.com/kiegroup/jenkins-pipeline-shared-libraries # timeout=10Found match: refs/heads/main revision 21afeeac35a851b46d694688c2562d914fab8e63The recommended git tool is: NONEusing credential kie-ci-user-key > git rev-parse --resolve-git-dir /var/lib/jenkins/jobs/KIE/jobs/kogito/jobs/main/jobs/pullrequest/jobs/kogito-runtimes.tests.kogito-runtimes/workspace@libs/jenkins-pipeline-shared-libraries/.git # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/kiegroup/jenkins-pipeline-shared-libraries # timeout=10Fetching without tagsFetching upstream changes from https://github.com/kiegroup/jenkins-pipeline-shared-libraries > git --version # timeout=10 > git --version # 'git version 1.8.3.1'using GIT_SSH to set credentials SSH: kie-ci service account with access to jboss-integration private github space[INFO] Currently running in a labeled security context > /usr/bin/chcon --type=ssh_home_t /var/lib/jenkins/jobs/KIE/jobs/kogito/jobs/main/jobs/pullrequest/jobs/kogito-runtimes.tests.kogito-runtimes/workspace@libs/jenkins-pipeline-shared-libraries@tmp/jenkins-gitclient-ssh2725508576494786942.key > git fetch --no-tags --progress https://github.com/kiegroup/jenkins-pipeline-shared-libraries +refs/heads/*:refs/remotes/origin/* # timeout=10Checking out Revision 21afeeac35a851b46d694688c2562d914fab8e63 (main) > git config core.sparsecheckout # timeout=10 > git checkout -f 21afeeac35a851b46d694688c2562d914fab8e63 # timeout=10Commit message: "pmebuild cleanScript (#188)" > git rev-list --no-walk 21afeeac35a851b46d694688c2562d914fab8e63 # timeout=10[Pipeline] Start of Pipeline[Pipeline] nodeRunning on rhos-01-kie-psi-rhel7-xlarge-5780 in /home/jenkins/workspace/KIE/kogito/main/pullrequest/kogito-runtimes.tests.kogito-runtimes[Pipeline] {[Pipeline] stage[Pipeline] { (Declarative: Checkout SCM)[Pipeline] checkoutThe recommended git tool is: NONEusing credential kie-ciCloning the remote Git repositoryAvoid second fetchChecking out Revision b844f47b3febcc273841e554486088d18b72b704 (origin/main)Commit message: "Correct Repo seeds (#425)"[Pipeline] }[Pipeline] // stage[Pipeline] withEnv[Pipeline] {[Pipeline] withEnv[Pipeline] {[Pipeline] timestamps[Pipeline] {[Pipeline] timeout[2022-04-27T15:42:32.078Z] Timeout set to expire in 3 hr 0 min[Pipeline] {[Pipeline] stage[Pipeline] { (Declarative: Tool Install)[Pipeline] tool[Pipeline] envVarsForTool[Pipeline] }[Pipeline] // stageCloning repository https://github.com/kiegroup/kogito-pipelines.git > git init /home/jenkins/workspace/KIE/kogito/main/pullrequest/kogito-runtimes.tests.kogito-runtimes # timeout=10Fetching upstream changes from https://github.com/kiegroup/kogito-pipelines.git > git --version # timeout=10 > git --version # 'git version 2.34.1'using GIT_ASKPASS to set credentials PSSWD: kie-ci service account with access to jboss-integration private github space > git fetch --tags --force --progress -- https://github.com/kiegroup/kogito-pipelines.git +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url https://github.com/kiegroup/kogito-pipelines.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git rev-parse origin/main^{commit} # timeout=10 > git config core.sparsecheckout # timeout=10 > git checkout -f b844f47b3febcc273841e554486088d18b72b704 # timeout=10[Pipeline] withEnv[Pipeline] {[Pipeline] stage[Pipeline] { (Initialize)[Pipeline] tool[Pipeline] envVarsForTool[Pipeline] withEnv[Pipeline] {[Pipeline] script[Pipeline] {[Pipeline] sh[2022-04-27T15:42:32.832Z] + printenv[Pipeline] archiveArtifacts[2022-04-27T15:42:32.886Z] Archiving artifacts[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (check space before build)[Pipeline] tool[Pipeline] envVarsForTool[Pipeline] withEnv[Pipeline] {[Pipeline] script[Pipeline] {[Pipeline] dir[2022-04-27T15:42:33.428Z] Running in /home/jenkins/workspace/KIE/kogito/main/pullrequest/kogito-runtimes.tests.kogito-runtimes[Pipeline] {[Pipeline] echo[2022-04-27T15:42:33.457Z] [INFO] space left on the machine[Pipeline] sh[2022-04-27T15:42:33.756Z] + df -h[2022-04-27T15:42:33.758Z] Filesystem      Size  Used Avail Use% Mounted on[2022-04-27T15:42:33.758Z] devtmpfs        7.8G     0  7.8G   0% /dev[2022-04-27T15:42:33.758Z] tmpfs           7.8G     0  7.8G   0% /dev/shm[2022-04-27T15:42:33.758Z] tmpfs           7.8G   17M  7.8G   1% /run[2022-04-27T15:42:33.758Z] tmpfs           7.8G     0  7.8G   0% /sys/fs/cgroup[2022-04-27T15:42:33.759Z] /dev/vda1        80G   18G   63G  23% /[2022-04-27T15:42:33.759Z] tmpfs           1.6G     0  1.6G   0% /run/user/1000[Pipeline] echo[2022-04-27T15:42:33.774Z] [INFO] space of /home/jenkins[Pipeline] sh[2022-04-27T15:42:34.057Z] + du -h -d1 /home/jenkins[2022-04-27T15:42:34.057Z] 4.0K	/home/jenkins/.ssh[2022-04-27T15:42:34.057Z] 0	/home/jenkins/go[2022-04-27T15:42:34.057Z] 8.0K	/home/jenkins/.vnc[2022-04-27T15:42:34.057Z] 12K	/home/jenkins/.m2[2022-04-27T15:42:34.057Z] 2.1G	/home/jenkins/git-repos[2022-04-27T15:42:34.057Z] 8.0K	/home/jenkins/.config[2022-04-27T15:42:34.057Z] 4.0K	/home/jenkins/.cekit[2022-04-27T15:42:34.057Z] 80M	/home/jenkins/virtenvs[2022-04-27T15:42:34.057Z] 31M	/home/jenkins/remoting[2022-04-27T15:42:34.057Z] 0	/home/jenkins/.cache[2022-04-27T15:42:34.057Z] 2.2M	/home/jenkins/workspace[2022-04-27T15:42:34.057Z] 0	/home/jenkins/.pki[2022-04-27T15:42:34.057Z] 117M	/home/jenkins/tools[2022-04-27T15:42:34.057Z] 0	/home/jenkins/caches[2022-04-27T15:42:34.057Z] 24M	/home/jenkins/.npm[2022-04-27T15:42:34.057Z] 8.0K	/home/jenkins/.java[2022-04-27T15:42:34.057Z] 2.3G	/home/jenkins[Pipeline] echo[2022-04-27T15:42:34.084Z] [INFO] space of workspace[Pipeline] sh[2022-04-27T15:42:34.379Z] + du -h -d3 /home/jenkins/workspace[2022-04-27T15:42:34.379Z] 0	/home/jenkins/workspace/custom/tradisso/kogito-6962[2022-04-27T15:42:34.379Z] 0	/home/jenkins/workspace/custom/tradisso[2022-04-27T15:42:34.379Z] 0	/home/jenkins/workspace/custom[2022-04-27T15:42:34.379Z] 2.2M	/home/jenkins/workspace/KIE/kogito/main[2022-04-27T15:42:34.379Z] 2.2M	/home/jenkins/workspace/KIE/kogito[2022-04-27T15:42:34.379Z] 2.2M	/home/jenkins/workspace/KIE[2022-04-27T15:42:34.379Z] 2.2M	/home/jenkins/workspace[Pipeline] }[Pipeline] // dir[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Install build-chain tool)[Pipeline] tool[Pipeline] envVarsForTool[Pipeline] withEnv[Pipeline] {[Pipeline] script[Pipeline] {[Pipeline] echo[2022-04-27T15:42:34.709Z] [INFO] Getting build-chain version from composite action file[Pipeline] readFile[Pipeline] echo[2022-04-27T15:42:34.806Z] [INFO] build-chain version recovered '2.3.34'[Pipeline] sh[2022-04-27T15:42:35.099Z] + npm install -g @kie/build-chain-action@2.3.34 -registry=https://repository.engineering.redhat.com/nexus/repository/registry.npmjs.org/[2022-04-27T15:42:36.463Z] /home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-12.16.3/bin/build-chain-action -> /home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-12.16.3/lib/node_modules/@kie/build-chain-action/bin/build-chain-cli.js[2022-04-27T15:42:36.463Z] npm WARN notsup Unsupported engine for @kie/build-chain-action@2.3.34: wanted: {"node":">= 12.18.0"} (current: {"node":"12.16.3","npm":"6.14.4"})[2022-04-27T15:42:36.463Z] npm WARN notsup Not compatible with your version of node/npm: @kie/build-chain-action@2.3.34[2022-04-27T15:42:36.463Z] npm WARN @octokit/plugin-request-log@1.0.4 requires a peer of @octokit/core@>=3 but none is installed. You must install peer dependencies yourself.[2022-04-27T15:42:36.463Z] [2022-04-27T15:42:36.463Z] + @kie/build-chain-action@2.3.34[2022-04-27T15:42:36.463Z] updated 1 package in 1.113s[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Build projects)[Pipeline] tool[Pipeline] envVarsForTool[Pipeline] tool[Pipeline] envVarsForTool[Pipeline] tool[Pipeline] envVarsForTool[Pipeline] withEnv[Pipeline] {[Pipeline] script[Pipeline] {[Pipeline] configFileProvider[2022-04-27T15:42:36.837Z] provisioning config files...[2022-04-27T15:42:36.842Z] copy managed file [kogito_pr_settings] to file:/home/jenkins/workspace/KIE/kogito/main/pullrequest/kogito-runtimes.tests.kogito-runtimes@tmp/config8724066432778356321tmp[Pipeline] {[Pipeline] withCredentials[2022-04-27T15:42:36.876Z] Masking supported pattern matches of $GITHUB_TOKEN[Pipeline] {[Pipeline] sh[2022-04-27T15:42:36.930Z] Warning: A secret was passed to "sh" using Groovy String interpolation, which is insecure.[2022-04-27T15:42:36.931Z] 		 Affected argument(s) used the following variable(s): [GITHUB_TOKEN][2022-04-27T15:42:36.931Z] 		 See https://jenkins.io/redirect/groovy-string-interpolation for details.[2022-04-27T15:42:37.201Z] + build-chain-action -token=**** -df=https://raw.githubusercontent.com/kiegroup/kogito-pipelines/main/.ci/pull-request-config.yaml -folder=bc build pr -url=https://github.com/kiegroup/kogito-runtimes/pull/2176 -sp=kiegroup/kogito-runtimes --skipParallelCheckout -cct '(^mvn .*)||$1 -s /home/jenkins/workspace/KIE/kogito/main/pullrequest/kogito-runtimes.tests.kogito-runtimes@tmp/config8724066432778356321tmp -Dmaven.wagon.http.ssl.insecure=true -Dmaven.test.failure.ignore=true'[2022-04-27T15:42:37.456Z] [INFO]  Executing pull request flow for https://github.com/kiegroup/kogito-runtimes/pull/2176 in bc[2022-04-27T15:42:38.020Z] [INFO]  https://raw.githubusercontent.com/kiegroup/kogito-pipelines/main/.ci/pull-request-config.yaml exists, using it[2022-04-27T15:42:38.020Z] ::group::[PRE] Executing pre section for https://raw.githubusercontent.com/kiegroup/kogito-pipelines/main/.ci/pull-request-config.yaml[2022-04-27T15:42:38.020Z] [INFO]  Execute command 'export BUILD_MVN_OPTS=" -nsu -ntp -fae -e -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false dependency:tree -Dmaven.wagon.httpconnectionManager.ttlSeconds=120 -Dmaven.wagon.http.retryHandler.count=3"' in dir '/home/jenkins/workspace/KIE/kogito/main/pullrequest/kogito-runtimes.tests.kogito-runtimes'[2022-04-27T15:42:38.020Z] [INFO]  Treating export command since it's not possible to run it from the runner itself[2022-04-27T15:42:38.020Z] [INFO]  The variable BUILD_MVN_OPTS has been stored with ' -nsu -ntp -fae -e -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false dependency:tree -Dmaven.wagon.httpconnectionManager.ttlSeconds=120 -Dmaven.wagon.http.retryHandler.count=3' value[2022-04-27T15:42:38.020Z] ::notice title= [PRE] [Execution OK]::export BUILD_MVN_OPTS=" -nsu -ntp -fae -e -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false dependency:tree -Dmaven.wagon.httpconnectionManager.ttlSeconds=120 -Dmaven.wagon.http.retryHandler.count=3"[2022-04-27T15:42:38.020Z] [INFO]  Execute command 'echo "BUILD_MVN_OPTS= -nsu -ntp -fae -e -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false dependency:tree -Dmaven.wagon.httpconnectionManager.ttlSeconds=120 -Dmaven.wagon.http.retryHandler.count=3"' in dir '/home/jenkins/workspace/KIE/kogito/main/pullrequest/kogito-runtimes.tests.kogito-runtimes'[2022-04-27T15:42:38.020Z] [command]/usr/bin/echo BUILD_MVN_OPTS= -nsu -ntp -fae -e -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false dependency:tree -Dmaven.wagon.httpconnectionManager.ttlSeconds=120 -Dmaven.wagon.http.retryHandler.count=3[2022-04-27T15:42:38.020Z] BUILD_MVN_OPTS= -nsu -ntp -fae -e -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false dependency:tree -Dmaven.wagon.httpconnectionManager.ttlSeconds=120 -Dmaven.wagon.http.retryHandler.count=3[2022-04-27T15:42:38.020Z] ::notice title= [PRE] [Execution OK]::echo "BUILD_MVN_OPTS= -nsu -ntp -fae -e -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false dependency:tree -Dmaven.wagon.httpconnectionManager.ttlSeconds=120 -Dmaven.wagon.http.retryHandler.count=3"[2022-04-27T15:42:38.020Z] ::endgroup::[2022-04-27T15:42:38.020Z] ::group::[Pull Request Flow] Execution Plan...[2022-04-27T15:42:38.020Z] [INFO]  ----------------------------------------------[2022-04-27T15:42:38.020Z] [INFO]  [2] projects will be executed[2022-04-27T15:42:38.020Z] [2022-04-27T15:42:38.020Z] [INFO]  [kiegroup/drools][2022-04-27T15:42:38.020Z] [INFO]  Level Type: [upstream].[2022-04-27T15:42:38.020Z] [INFO]  mvn clean install -Dquickly ${{ env.BUILD_MVN_OPTS }} ${{ env.BUILD_MVN_OPTS_UPSTREAM }} ${{ env.DROOLS_BUILD_MVN_OPTS_UPSTREAM }}[2022-04-27T15:42:38.020Z] [INFO]  [ 'docker system prune -f' ][2022-04-27T15:42:38.020Z] [2022-04-27T15:42:38.020Z] [INFO]  [kiegroup/kogito-runtimes][2022-04-27T15:42:38.020Z] [INFO]  Level Type: [current].[2022-04-27T15:42:38.020Z] [INFO]  [[2022-04-27T15:42:38.020Z]   'mvn -f kogito-runtimes/pom.xml clean install -Dvalidate-formatting -Dquarkus.bootstrap.effective-model-builder ${{ env.BUILD_MVN_OPTS }} ${{ env.BUILD_MVN_OPTS_CURRENT }} ${{ env.KOGITO_RUNTIMES_BUILD_MVN_OPTS }}'[2022-04-27T15:42:38.020Z] ][2022-04-27T15:42:38.020Z] [INFO]  [ 'docker system prune -f' ][2022-04-27T15:42:38.020Z] [2022-04-27T15:42:38.020Z] [INFO]  ----------------------------------------------[2022-04-27T15:42:38.020Z] ::endgroup::[2022-04-27T15:42:38.020Z] ::group::[Pull Request Flow] Checking out kiegroup/kogito-runtimes and its dependencies[2022-04-27T15:42:38.020Z] [INFO]  Tree for project kiegroup/kogito-runtimes. Dependencies: [2022-04-27T15:42:38.020Z] kiegroup/drools,[2022-04-27T15:42:38.020Z] kiegroup/kogito-runtimes[2022-04-27T15:42:38.020Z] [INFO]  [kiegroup/drools] Checking out project[2022-04-27T15:42:38.287Z] [WARN]  davidesalerno/drools not found. Trying to get it by forked project list.[2022-04-27T15:43:16.996Z] [ERROR]  You have exceeded a secondary rate limit. Please wait a few minutes before you try again.[Pipeline] }[Pipeline] // withCredentials[Pipeline] }[2022-04-27T15:43:17.080Z] Deleting 1 temporary files[Pipeline] // configFileProvider[Pipeline] }[Pipeline] // scriptPost stage[Pipeline] junit[2022-04-27T15:43:17.167Z] Recording test results[2022-04-27T15:43:17.172Z] No test report files were found. Configuration error?Error when executing always post condition:Also:   hudson.remoting.Channel$CallSiteStackTrace: Remote call to rhos-01-kie-psi-rhel7-xlarge-5780		at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1797)		at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356)		at hudson.remoting.Channel.call(Channel.java:1001)		at hudson.FilePath.act(FilePath.java:1166)		at hudson.FilePath.act(FilePath.java:1155)		at hudson.tasks.junit.JUnitParser.parseResult(JUnitParser.java:107)		at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:153)		at hudson.tasks.junit.JUnitResultArchiver.parseAndSummarize(JUnitResultArchiver.java:247)		at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:63)		at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:29)		at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)		at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)		at java.util.concurrent.FutureTask.run(FutureTask.java:266)		at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)		at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)		at java.lang.Thread.run(Thread.java:748)hudson.AbortException: No test report files were found. Configuration error?	at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:154)	at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3338)	at hudson.remoting.UserRequest.perform(UserRequest.java:211)	at hudson.remoting.UserRequest.perform(UserRequest.java:54)	at hudson.remoting.Request$2.run(Request.java:376)	at hudson.remoting.InterceptingExecutorService.lambda$wrap$0(InterceptingExecutorService.java:78)	at java.util.concurrent.FutureTask.run(FutureTask.java:266)	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)	at java.lang.Thread.run(Thread.java:750)[Pipeline] script[Pipeline] {[Pipeline] sh[2022-04-27T15:43:17.536Z] + rm -rf console.log[Pipeline] sh

Hello Davide,
good initiative to complement the tests with this one! A quick comment from my side is that maybe you can try to locate it here instead:
https://github.com/kiegroup/kogito-runtimes/tree/4cbceded6c9b5bef4313b50bdcb1f076b9ee620e/quarkus/extensions/kogito-quarkus-serverless-workflow-extension/kogito-quarkus-serverless-workflow-integration-test/src/main/resources
There we have already some integration tests for the sw.

Hello Davide, good initiative to complement the tests with this one! A quick comment from my side is that maybe you can try to locate it here instead:
https://github.com/kiegroup/kogito-runtimes/tree/4cbceded6c9b5bef4313b50bdcb1f076b9ee620e/quarkus/extensions/kogito-quarkus-serverless-workflow-extension/kogito-quarkus-serverless-workflow-integration-test/src/main/resources
There we have already some integration tests for the sw.

Hi @wmedvede,
yes, we could probably move the test in the folder https://github.com/davidesalerno/kogito-runtimes/tree/main/quarkus/extensions/kogito-quarkus-serverless-workflow-extension but I've got some concerns related to moving it inside https://github.com/davidesalerno/kogito-runtimes/tree/main/quarkus/extensions/kogito-quarkus-serverless-workflow-extension/kogito-quarkus-serverless-workflow-integration-test because at the moment the QuarkusIntegrationTests that we have got in the kogito-quarkus-serverless-workflow-integration-test are not designed to be executed inside a container as the IT test that we would like to add it is.
In fact if you add the constraint to execute the tests inside a docker image (you have to add to the pom the  quarkus-container-image-jib dependency and in the application properties quarkus.container-image.build=true), you will have some test failures due to some docker networking issues.
Is it fine if we will move as a new maven project here https://github.com/davidesalerno/kogito-runtimes/tree/main/quarkus/extensions/kogito-quarkus-serverless-workflow-extension ?
We could maybe find together a more meaningful name for the project in order to identifiy all the integration tests where the code is testes inside a docker image and not simply executing the jar as in the other integration test project.
For example kogito-quarkus-serverless-workflow-cloud-integration-test so that in future we can add here also other tests like this one.

Let me elaborate a bit more.
The test itself already exist as integration test in a different module.
Therefore, we are not testing any new functionality, but that an existing functionality work in a different enviroment.
The same we are not creating specific modules to test, lets said that everything work in windows, I do not think is the right path to create new projects for testing docker env.
So I think we need to explore how to test this by creating a maven profile in the existing testing project, if possible
If not possible, then, we should create another pom (at the same level of the existing test) and rather than copy paste the existing workflow file, use maven to copy it to the new project automatically.

Im wondering if we cannot test this by using a different profile in the existing quarkus extension tests pom

I think that's feasible.

@fjtirado I investigated on what we can do with using maven profile, quarkus profile and quarkus test profile and also mixing this 3 featuer I wasn't able to find a way to let the current integrations test we have got on the kogito-quarkus-serverless-workflow-integration-test project still working and adding a new test that will verify that the workflow could be also executed in a different environment (a container).
The main issue is that to do that we have to add a Quarkus extensions that will cause all the existing @QuarkusIntegrationTests to be executed inside a docker container and this will cause a failure "by-design".
Probably the best thing to do is the other options and so creating a new pom with the test and let to maven to copy all the other things from the current kogito-quarkus-serverless-workflow-integration-test project.

(tests) - kogito-apps job #1620 was: UNSTABLE
Possible explanation: This should be test failures
Test results:

PASSED: 2723
FAILED: 1

Those are the test failures:

org.kie.kogito.index.ProcessDataIndexInfinispanIT.testProcessInstanceEvents
java.lang.AssertionError: 1 expectation failed.JSON path data.UserTaskInstances[0].attachments[0].name doesn't match.Expected: newAttachmentContent  Actual: NewTaskAttachmentName

Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-runtimes.tests.downstream.kogito-apps/1620/display/redirect

@wmedvede @fjtirado I followed your suggestions and:

moved the test under the quarkus/extensions/kogito-quarkus-serverless-workflow-extension/ in a new module kogito-quarkus-serverless-workflow-image-integration-test
importing all the needed resources from kogito-quarkus-serverless-workflow-integration-test

What do you think?

@wmedvede @fjtirado I followed your suggestions and:

moved the test under the quarkus/extensions/kogito-quarkus-serverless-workflow-extension/ in a new module kogito-quarkus-serverless-workflow-image-integration-test
importing all the needed resources from kogito-quarkus-serverless-workflow-integration-test

What do you think?

Hi @davidesalerno , I think it's fine and thanks for trying other alternatives! Really appreciate this effort. +1 from my side.
A general comment (don't need to change now), to all of us @wmedvede @ricardozanini @fjtirado @jstastny-cz etc. (and of course including my self :) ), is that we shouldn't use things like :
my_name=javierito
the_answer_is=que lindo que soy!   (what a beautiful I am)
Instead, we should use neutral names, phrases, etc, that makes easy to follow the tests.
Equivalent neutral version:
my_name=user1
the_answer_is=service answer
etc

authors: davidesalerno fjtirado kie-ci1 ricardozanini wmedvede

repo: kiegroup/kogito-runtimes


text:
For single brushnet: brushnet_conditioning_scale must be type float.

File "D:\ComfyUI_windows_portable\ComfyUI\execution.py", line 151, in recursive_execute
output_data, output_ui = get_output_data(obj, input_data_all)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\ComfyUI_windows_portable\ComfyUI\execution.py", line 81, in get_output_data
return_values = map_node_over_list(obj, input_data_all, obj.FUNCTION, allow_interrupt=True)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\ComfyUI_windows_portable\ComfyUI\execution.py", line 74, in map_node_over_list
results.append(getattr(obj, func)(**slice_dict(input_data_all, i)))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-BrushNet-Wrapper\nodes.py", line 369, in process
images = pipe(
^^^^^
File "D:\ComfyUI_windows_portable\python_embeded\Lib\site-packages\torch\utils_contextlib.py", line 115, in decorate_context
return func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "D:\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-BrushNet-Wrapper\brushnet\pipeline_brushnet.py", line 1010, in call
self.check_inputs(
File "D:\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-BrushNet-Wrapper\brushnet\pipeline_brushnet.py", line 636, in check_inputs
raise TypeError("For single brushnet: brushnet_conditioning_scale must be type float.")
TypeError:

It's me who encountered the same problem, which usually occurs after using two brushnet nodes or running multiple batches

authors: MingZeY liekkasfc

repo: kijai/ComfyUI-BrushNet-Wrapper


text:
Update 브라우저 동작 방법.md

링크가 '을'까지 걸려있어서 수정했습니다 👍

감사합니다~!


text:
Add support for pnpm

Hi - thanks for this helpful package.
I've created a PR for supporting pnpm in addition to yarn:
https://pnpm.js.org
Hope this is helpful.
Let me know if need to update/change anything.
Thanks

Coverage remained the same at 100.0% when pulling cd1c76414b36b3180cb45fe47825302f2fc33305 on admmasters:add-pnpm-support into 54b6456eb5054ec32de9d81717b143d2ca8f8f6d on kimmobrunfeldt:master.

Thanks @gustavohenke

Hello! First of all thanks for this!
Any idea when it's going to be released @gustavohenke ?

Release as v5.3.0!

authors: admmasters coveralls gustavohenke poteirard

repo: kimmobrunfeldt/concurrently

license: mit


text:
P3 cubic element

I consider degrees of freedom and Lagrange basis for the P3 cubic element on a triangle. There are three types of dofs: vertex type, edge type and element type.  In scifit-fem, I find those dofs can be expressed as nodal_dofs, facet_dofs, interior_dofs. Following the code of P2 quadric element and I try to code P3 cubic element as  follow. I am wondering whether  facet_dofs are only at the midpoint the edges(such as P2 elemnt, Crouzeix-Raviart element etc), but P3 case has two dofs of one edge.
`class ElementTriP3(ElementH1):
"""Piecewise cubic element."""
nodal_dofs = 1
facet_dofs = 2
interior_dofs = 1
maxdeg = 3
dofnames = ['u', 'u', 'u']
doflocs = np.array([[0., 0.],
                    [1., 0.],
                    [0., 1.],
                    [1./3, 0.],
                    [2./3, 1./3],
                    [0., 2./3],
                    [2./3, 0.],
                    [1./3, 2./3],
                    [0., 1./3],
                    [1./3, 1./3]])

refdom = RefTri

def lbasis(self, X, i):
    x, y = X

    if i == 0:  # (0., 0.)
        phi = 1/2 * (1-x-y) * (2-3*x-3*y) * (1-3*x-3*y)
        dphi = np.array([
        	18*x + 18*y - 27*x*y - (27*x**2)/2 - (27*y**2)/2 - 11/2,
            18*x + 18*y - 27*x*y - (27*x**2)/2 - (27*y**2)/2 - 11/2
        ])
    elif i == 1:  # (1., 0.)
        phi = 1./2 * x * (3*x-1) * (3*x-2)
        dphi = np.array([
        	(27*x**2)/2 - 9*x + 1,
            0.* x
        ])
    elif i == 2:  # (0., 1.)
        phi = 1. /2 * y * (3*y-1) * (3*y-2)
        dphi = np.array([
        	0.* x,
        	(27*y**2)/2 - 9*y + 1
        ])
    elif i == 3:  # 0->1: (1/3,0)
        phi = 9. /2 * x * (1-x-y) * (2-3*x-3*y)
        dphi = np.array([
        	(81*x**2)/2 + 54*x*y - 45*x + (27*y**2)/2 - (45*y)/2 + 9,
            (9*x*(6*x + 6*y - 5))/2
        ])
    elif i == 4:  # 1->2: (2/3,1/3)
        phi = 9./2 * x * y * (3*x-1)
        dphi = np.array([
        	(9*y*(6*x - 1))/2,
            (9*x*(3*x - 1))/2
        ])
    elif i == 5:  # 2->0: (0,2/3)
        phi = 9. /2 * y * (1-x-y) * (3*y-1)
        dphi = np.array([
        	-(9*y*(3*y - 1))/2,
            (9*x)/2 + 36*y - 27*x*y - (81*y**2)/2 - 9/2
        ])
    elif i == 6:  # 0->1: (2/3,0)
        phi = 9./2 * x * (1-x-y) * (3*x-1)
        dphi = np.array([
        	36*x + (9*y)/2 - 27*x*y - (81*x**2)/2 - 9/2,
            -(9*x*(3*x - 1))/2
        ])
    elif i == 7:  # 1->2: (1/3,2/3)
        phi = 9./2 * x * y * (3*y-1)
        dphi = np.array([
        	(9*y*(3*y - 1))/2,
            (9*x*(6*y - 1))/2
        ])
    elif i == 8:  # 3->0: (0,1/3)
        phi = 9/2 * y * (1-x-y) * (2-3*x-3*y)
        dphi = np.array([
        	(9*y*(6*x + 6*y - 5))/2,
            (27*x**2)/2 + 54*x*y - (45*x)/2 + (81*y**2)/2 - 45*y + 9
        ])
    elif i == 9:  # centroid (1/3,1/3)
        phi = 27*x*y*(-x - y + 1)
        dphi = np.array([
            27*y*(-2*x - y + 1),
            27*x*(-x - 2*y + 1)
        ])
    else:
        self._index_error()

    return phi, dphi

`

Facet DOFs can be more than one. However, it is nontrivial in which order those DOFs should be so that the neighbouring elements correctly share the DOF. I'm working on the same problem while implementing BDM element. I'll come back to this when it's ready.

Meanwhile there is ElementQuadP which already solves this, however, it requires some in depth understanding of the indexing used in scikitfem

Now that I think of it, ElementQuadP might rely on something which is true only for structured meshes, i.e first and third facets are opposite to one another. We need another more general edge orientation. This can be done in ElementH1.

Drawing this basis on a two element mesh and random DOF vector reveals the issue:

After making some changes it looks better:

Here is the changed code, didn't fix doflocs, just the order of the basis:
class ElementTriP3(ElementH1):
    """Piecewise cubic element."""

    nodal_dofs = 1
    facet_dofs = 2
    interior_dofs = 1
    maxdeg = 3
    dofnames = ['u', 'u', 'u']
    doflocs = np.array([[0., 0.],
                        [1., 0.],
                        [0., 1.],
                        [1./3, 0.],
                        [2./3, 1./3],
                        [0., 2./3],
                        [2./3, 0.],
                        [1./3, 2./3],
                        [0., 1./3],
                        [1./3, 1./3]])

    refdom = RefTri

    def lbasis(self, X, i):
        x, y = X

        if i == 0:  # (0., 0.)
            phi = 1/2 * (1-x-y) * (2-3*x-3*y) * (1-3*x-3*y)
            dphi = np.array([
                    18*x + 18*y - 27*x*y - (27*x**2)/2 - (27*y**2)/2 - 11/2,
                18*x + 18*y - 27*x*y - (27*x**2)/2 - (27*y**2)/2 - 11/2
            ])
        elif i == 1:  # (1., 0.)
            phi = 1./2 * x * (3*x-1) * (3*x-2)
            dphi = np.array([
                    (27*x**2)/2 - 9*x + 1,
                0.* x
            ])
        elif i == 2:  # (0., 1.)
            phi = 1. /2 * y * (3*y-1) * (3*y-2)
            dphi = np.array([
                    0.* x,
                    (27*y**2)/2 - 9*y + 1
            ])
        elif i == 3:  # 0->1: (1/3,0)
            phi = 9. /2 * x * (1-x-y) * (2-3*x-3*y)
            dphi = np.array([
                    (81*x**2)/2 + 54*x*y - 45*x + (27*y**2)/2 - (45*y)/2 + 9,
                (9*x*(6*x + 6*y - 5))/2
            ])
        elif i == 5:  # 1->2: (2/3,1/3)
            phi = 9./2 * x * y * (3*x-1)
            dphi = np.array([
                    (9*y*(6*x - 1))/2,
                (9*x*(3*x - 1))/2
            ])
        elif i == 8:  # 2->0: (0,2/3)
            phi = 9. /2 * y * (1-x-y) * (3*y-1)
            dphi = np.array([
                    -(9*y*(3*y - 1))/2,
                (9*x)/2 + 36*y - 27*x*y - (81*y**2)/2 - 9/2
            ])
        elif i == 4:  # 0->1: (2/3,0)
            phi = 9./2 * x * (1-x-y) * (3*x-1)
            dphi = np.array([
                    36*x + (9*y)/2 - 27*x*y - (81*x**2)/2 - 9/2,
                -(9*x*(3*x - 1))/2
            ])
        elif i == 6:  # 1->2: (1/3,2/3)
            phi = 9./2 * x * y * (3*y-1)
            dphi = np.array([
                    (9*y*(3*y - 1))/2,
                (9*x*(6*y - 1))/2
            ])
        elif i == 7:  # 3->0: (0,1/3)
            phi = 9/2 * y * (1-x-y) * (2-3*x-3*y)
            dphi = np.array([
                    (9*y*(6*x + 6*y - 5))/2,
                (27*x**2)/2 + 54*x*y - (45*x)/2 + (81*y**2)/2 - 45*y + 9
            ])
        elif i == 9:  # centroid (1/3,1/3)
            phi = 27*x*y*(-x - y + 1)
            dphi = np.array([
                27*y*(-2*x - y + 1),
                27*x*(-x - 2*y + 1)
            ])
        else:
            self._index_error()

        return phi, dphi

Now it's solving Poisson equation nicely:

I fixed doflocs and dofnames:
class ElementTriP3(ElementH1):
    """Piecewise cubic element."""

    nodal_dofs = 1
    facet_dofs = 2
    interior_dofs = 1
    maxdeg = 3
    dofnames = ['u', 'u', 'u', 'u']
    doflocs = np.array([[0., 0.],
                        [1., 0.],
                        [0., 1.],
                        [1./3, 0.],
                        [2./3, 0.],
                        [1./3, 2./3],
                        [2./3, 1./3],
                        [0., 1./3],
                        [0., 2./3],
                        [1./3, 1./3]])

    refdom = RefTri

    def lbasis(self, X, i):
        x, y = X

        if i == 0:  # (0., 0.)
            phi = 1/2 * (1-x-y) * (2-3*x-3*y) * (1-3*x-3*y)
            dphi = np.array([
                    18*x + 18*y - 27*x*y - (27*x**2)/2 - (27*y**2)/2 - 11/2,
                18*x + 18*y - 27*x*y - (27*x**2)/2 - (27*y**2)/2 - 11/2
            ])
        elif i == 1:  # (1., 0.)
            phi = 1./2 * x * (3*x-1) * (3*x-2)
            dphi = np.array([
                    (27*x**2)/2 - 9*x + 1,
                0.* x
            ])
        elif i == 2:  # (0., 1.)
            phi = 1. /2 * y * (3*y-1) * (3*y-2)
            dphi = np.array([
                    0.* x,
                    (27*y**2)/2 - 9*y + 1
            ])
        elif i == 3:  # 0->1: (1/3,0)
            phi = 9. /2 * x * (1-x-y) * (2-3*x-3*y)
            dphi = np.array([
                    (81*x**2)/2 + 54*x*y - 45*x + (27*y**2)/2 - (45*y)/2 + 9,
                (9*x*(6*x + 6*y - 5))/2
            ])
        elif i == 5:  # 1->2: (2/3,1/3)
            phi = 9./2 * x * y * (3*x-1)
            dphi = np.array([
                    (9*y*(6*x - 1))/2,
                (9*x*(3*x - 1))/2
            ])
        elif i == 8:  # 2->0: (0,2/3)
            phi = 9. /2 * y * (1-x-y) * (3*y-1)
            dphi = np.array([
                    -(9*y*(3*y - 1))/2,
                (9*x)/2 + 36*y - 27*x*y - (81*y**2)/2 - 9/2
            ])
        elif i == 4:  # 0->1: (2/3,0)
            phi = 9./2 * x * (1-x-y) * (3*x-1)
            dphi = np.array([
                    36*x + (9*y)/2 - 27*x*y - (81*x**2)/2 - 9/2,
                -(9*x*(3*x - 1))/2
            ])
        elif i == 6:  # 1->2: (1/3,2/3)
            phi = 9./2 * x * y * (3*y-1)
            dphi = np.array([
                    (9*y*(3*y - 1))/2,
                (9*x*(6*y - 1))/2
            ])
        elif i == 7:  # 3->0: (0,1/3)
            phi = 9/2 * y * (1-x-y) * (2-3*x-3*y)
            dphi = np.array([
                    (9*y*(6*x + 6*y - 5))/2,
                (27*x**2)/2 + 54*x*y - (45*x)/2 + (81*y**2)/2 - 45*y + 9
            ])
        elif i == 9:  # centroid (1/3,1/3)
            phi = 27*x*y*(-x - y + 1)
            dphi = np.array([
                27*y*(-2*x - y + 1),
                27*x*(-x - 2*y + 1)
            ])
        else:
            self._index_error()

        return phi, dphi

Can I clean this code a bit and add it to scikit-fem or do you want to open a PR?

Thanks so much for your help. You add this code to scikit-fem and I want figure out the difference betweent your code and mine of this P3 cubic elment.

I want to using C^0 interior penalty Galerkin method to solve four order problem, which can can efficiently capture smooth solution using high order Lagrange basis functions(such as P3 cubic element and P4 quartic element), so I need to calculate second derivative of basis funtions, and to construct a new affine mapping for this. Another question is how to use Hessian matrix in mapping_affine.py.

In 2-dimensional case, I try to use matrix A to derive H in class MappingAffine.
        self.H = np.empty((dim+1, dim+1, nt))

        elif dim == 2:
            self.detA = (self.A[0, 0] * self.A[1, 1] -
                         self.A[0, 1] * self.A[1, 0])
            h00 = self.A[0, 0] * self.A[0, 0]
            h01 = 2 * self.A[0, 0] * self.A[1, 0]
            h02 = self.A[1, 0] * self.A[1, 0]
            h10 = self.A[0, 1] * self.A[0, 0]
            h11 = self.A[0, 1] * self.A[1, 0] + self.A[0, 0] * self.A[1, 1]
            h12 = self.A[1, 0] * self.A[1, 1]
            h20 = self.A[0, 1] * self.A[0, 1]
            h21 =  2 * self.A[1, 1] * self.A[0, 1]
            h22 = self.A[1, 1] * self.A[1, 1]
            self.detH = h00 * (h11 * h22 - h12 * h21) -\
                        h01 * (h10 * h22 - h12 * h20) +\
                        h02 * (h10 * h21 - h11 * h20)

        elif dim == 2:
            self.invA[0, 0] =  self.A[1, 1] / self.detA  # noqa
            self.invA[0, 1] = -self.A[0, 1] / self.detA
            self.invA[1, 0] = -self.A[1, 0] / self.detA
            self.invA[1, 1] =  self.A[0, 0] / self.detA  # noqa
            h00 = self.A[0, 0] * self.A[0, 0]
            h01 = 2 * self.A[0, 0] * self.A[1, 0]
            h02 = self.A[1, 0] * self.A[1, 0]
            h10 = self.A[0, 1] * self.A[0, 0]
            h11 = self.A[0, 1] * self.A[1, 0] + self.A[0, 0] * self.A[1, 1]
            h12 = self.A[1, 0] * self.A[1, 1]
            h20 = self.A[0, 1] * self.A[0, 1]
            h21 =  2 * self.A[1, 1] * self.A[0, 1]
            h22 = self.A[1, 1] * self.A[1, 1]
            self.invH[0, 0] = (-h12 * h21 +  h11 * h22) / self.detH
            self.invH[1, 0] = (h12 * h20 - h10 * h22) / self.detH
            self.invH[2, 0] = (-h11 * h20 + h10 * h21) / self.detH
            self.invH[0, 1] = (h02 * h21 - h01 * h22) / self.detH
            self.invH[1, 1] = (-h02 * h20 + h00 * h22) / self.detH
            self.invH[2, 1] = (h01 * h20 - h00 * h21) / self.detH
            self.invH[0, 2] = (-h02 * h11 + h01 * h12) / self.detH
            self.invH[1, 2] = (h02 * h10 - h00 * h12) / self.detH
            self.invH[2, 2] = (-h01 * h10 + h00 * h11) / self.detH

def invDH(self, X, tind=None):
    if tind is None:
        invDH = self.invH
    else:
        invDH = self.invH[:, :, tind]

    ones = np.ones(X.shape[-1])
    return np.einsum('ijk,l->ijkl', invDH, ones)

and then I add codes in class ElementH1,
def gbasis(self, mapping, X, i, tind=None):
    """Identity transformation."""
    phi, dphi, d2phi = self.lbasis(X, i)
    invDF = mapping.invDF(X, tind)
    invDH = mapping.invDH(X, tind)

    if len(X.shape) == 2:
        return (DiscreteField(
            value=np.broadcast_to(phi, (invDF.shape[2], invDF.shape[3])),
            grad=np.einsum('ijkl,il->jkl', invDF, dphi),
            hess=np.einsum('ijkl,il->jkl', invDH, d2phi)
        ),)

I am not sure that such modifications are correct. If not and how to fix these. Thanks in advance.

ElementGlobal supports arbitrary derivatives. However, it is not directly compatible with explicit bases. I think we can implement a flag to ElementH1 which enables second derivative. I'll check your code when I get kids to sleep.

Your idea makes sense. How did you modify ElementTriP3 to return the second derivatives? I think we don't want to do that modification to all elements in scikit-fem, so I suggest that we implement an alternative to ElementH1 class which takes into account second derivatives.

I agree with you. Indeed, it's not necessary to modify it like that for all element.

If you want to move forwards with this without larger changes, I propose that you do something like this:

class ElementTriP2Global(ElementGlobal):

    nodal_dofs = 1
    facet_dofs = 1
    maxdeg = 2
    dofnames = ['u', 'u']
    doflocs = np.array([[0., 0.],
                        [1., 0.],
                        [0., 1.],
                        [.5, 0.],
                        [.5, .5],
                        [0., .5]])
    refdom = RefTri

    def gdof(self, F, w, i):
        if i == 0:
            return F[()](*w['v'][0])
        elif i == 1:
            return F[()](*w['v'][1])
        elif i == 2:
            return F[()](*w['v'][2])
        elif i == 3:
            return F[()](*w['e'][0])
        elif i == 4:
            return F[()](*w['e'][1])
        elif i == 5:
            return F[()](*w['e'][2])
        self._index_error()

m = MeshTri1().refined(4)
basis = Basis(m, ElementTriP2Global())

y = projection(lambda x: x[0] ** 3, basis)

@Functional
def ddf(w):
    return w['y'].hess[0, 0]

out = ddf.assemble(basis, y=y)
print(out)

I have not tried implementing P3 and P4 but if you are doing DG methods it shouldn't matter too much where the DOFs are located because everything should be interior_dofs.

Alright, you are doing C^0 method. Here is my adaptation of
An a posteriori error estimator for a quadratic C0-interior penalty method for the biharmonic problem
SC Brenner, T Gudi, L Sung
I didn't check it too carefully but it should give you some ideas how to begin:
import numpy as np
from skfem import *
from skfem.element.element_global import ElementGlobal
from skfem.models.poisson import *
from skfem.helpers import *
from skfem.element.element_tri.element_tri_p2_hessian import *

import numpy as np

from skfem.refdom import RefTri

class ElementTriP2Global(ElementGlobal):

    nodal_dofs = 1
    facet_dofs = 1
    maxdeg = 2
    dofnames = ['u'] * 6
    doflocs = np.array([[0., 0.],
                        [1., 0.],
                        [0., 1.],
                        [.5, 0.],
                        [.5, .5],
                        [0., .5]])
    refdom = RefTri

    def gdof(self, F, w, i):
        if i == 0:
            return F[()](*w['v'][0])
        elif i == 1:
            return F[()](*w['v'][1])
        elif i == 2:
            return F[()](*w['v'][2])
        elif i == 3:
            return F[()](*w['e'][0])
        elif i == 4:
            return F[()](*w['e'][1])
        elif i == 5:
            return F[()](*w['e'][2])
        self._index_error()

m = MeshTri1().refined(3)
e = ElementTriP2Global()
alpha = 1e1

ib = Basis(m, e)
bb = FacetBasis(m, e)
fb = [InteriorFacetBasis(m, e, side=i) for i in [0, 1]]

@BilinearForm
def bilinf(u, v, p):
    return ddot(dd(u), dd(v))

@BilinearForm
def dgform(u, v, p):
    h = p.h
    n = p.n
    ju = dot(grad(u), n) * p.sign1
    jv = dot(grad(v), n) * p.sign2
    mu = .5 * ddot(dd(u), prod(n, n))
    mv = .5 * ddot(dd(v), prod(n, n))
    return alpha * ju * jv / h + mu * jv + mv * ju

A = asm(bilinf, ib)
B = asm(dgform, fb, fb)
C = asm(dgform, bb)
b = asm(unit_load, ib)

x = solve(*condense(A + B + C, b, D=ib.get_dofs()))

if __name__ == "__main__":
    from skfem.visuals.matplotlib import plot, show, draw
    ax = draw(m)
    plot(ib, x, Nrefs=3, shading="gouraud", colorbar=True, ax=ax)
    show()

Note: There is a bug somewhere above because alpha affects the solution too much.

Nice! Thank you for your sharing!

One issue above is that when assembling C you should not have the coefficient .5 in mu and mv. Still there is something else.

Alright, now it gives same answer as Morley element:
import numpy as np
from skfem import *
from skfem.element.element_global import ElementGlobal
from skfem.models.poisson import *
from skfem.helpers import *
from skfem.element.element_tri.element_tri_p2_hessian import *

import numpy as np

from skfem.refdom import RefTri

class ElementTriP2Global(ElementGlobal):

    nodal_dofs = 1
    facet_dofs = 1
    maxdeg = 2
    dofnames = ['u'] * 2
    doflocs = np.array([[0., 0.],
                        [1., 0.],
                        [0., 1.],
                        [.5, 0.],
                        [.5, .5],
                        [0., .5]])
    refdom = RefTri

    def gdof(self, F, w, i):
        if i == 0:
            return F[()](*w['v'][0])
        elif i == 1:
            return F[()](*w['v'][1])
        elif i == 2:
            return F[()](*w['v'][2])
        elif i == 3:
            return F[()](*w['e'][0])
        elif i == 4:
            return F[()](*w['e'][1])
        elif i == 5:
            return F[()](*w['e'][2])
        self._index_error()

m = MeshTri1().refined(4)
e = ElementTriP2Global()
morley = False
if morley:
    e = ElementTriMorley()
alpha = 10

ib = Basis(m, e)
bb = FacetBasis(m, e)
fb = [InteriorFacetBasis(m, e, side=i) for i in [0, 1]]

@BilinearForm
def bilinf(u, v, p):
    return ddot(dd(u), dd(v))

@BilinearForm
def iform(u, v, p):
    h = p.h
    n = p.n
    ju = -dot(grad(u), n) * p.sign1
    jv = -dot(grad(v), n) * p.sign2
    mu = .5 * ddot(dd(u), prod(n, n))
    mv = .5 * ddot(dd(v), prod(n, n))
    return alpha * ju * jv / h + mu * jv + mv * ju

@BilinearForm
def bform(u, v, p):
    h = p.h
    n = p.n
    ju = -dot(grad(u), n)
    jv = -dot(grad(v), n)
    mu = ddot(dd(u), prod(n, n))
    mv = ddot(dd(v), prod(n, n))
    return alpha * ju * jv / h + mu * jv + mv * ju

A = asm(bilinf, ib)
B = asm(iform, fb, fb)
C = asm(bform, bb)
b = asm(unit_load, ib)
c = 0 if morley else 1

x = solve(*condense(A + c * B + c * C, b, D=ib.get_dofs()))

if __name__ == "__main__":
    from skfem.visuals.matplotlib import plot, show, draw
    ax = draw(m)
    plot(ib, x, Nrefs=3, shading="gouraud", colorbar=True, ax=ax)
    show()

There is maybe some assumption in
An a posteriori error estimator for a quadratic C0-interior penalty method for the biharmonic problem
SC Brenner, T Gudi, L Sung

that I'm not fully understanding but I had to change the sign of the consistency terms. Nevertheless, this gives you some ideas how to move forwards.

Note: All of the above require master branch which will in some days be released as 4.0.0.

Original issue was fixed by #742

I can't find ".element_tri.element_tri_p2_hessian"
ModuleNotFoundError: No module named 'skfem.element.element_tri.element_tri_p2_h
essian'
Would you do me a favor and share this file?

Sorry, you can remove that line. It is not used.

repo: kinnala/scikit-fem


text:
is kit b too aggressive in determining processes?

E.g. if i have a package containing
foo/
bar/
lib/

where lib/ is meant to be imported by foo/ and/or bar/ but is not itself a process, should there be a way to specify that lib/ is not a process?
Current workaround is to nest dirs, e.g.
foo/
bar/
crate/
  lib/

the code that identifies a process dir in the package:
https://github.com/kinode-dao/kit/blob/master/src/build/mod.rs#L414-L415
https://github.com/kinode-dao/kit/blob/master/src/build/mod.rs#L370-L371
so if it

is a dir in the package
has src/lib.rs
its assumed to be a rust process

https://discord.com/channels/1186394868336038080/1186421052071477428/1240714974930669760

repo: kinode-dao/kit


text:
fix: improve an error message when process failed due to the wrong encoding

Why
It's hard to know the root cause when an error happens due to the mismatch encoding between the specified CSV file and the specified encoding.
Background
https://community.cybozu.dev/t/topic/1672
What

[x] Show a clear error message when mismatch encoding happens

How to test
N/A
Checklist

[x] Read CONTRIBUTING.md
[x] Updated documentation if it is required.
[x] Added tests if it is required.
[x] Passed pnpm lint and pnpm test on the root directory.

I checked the operations.
LGTM!
## Importing UTF-8 encoded CSV with default encoding (UTF-8).
$ ./bin/cli-kintone-macos record import \
        --app 123 \
        --file-path ./app123_utf8.csv \
        --attachments-dir attachments.app123_utf8 \
        --update-key レコード番号
[2023-08-22T12:59:29.878Z] INFO: Preparing to import records...
[2023-08-22T12:59:30.156Z] INFO: Starting to import records...
[2023-08-22T12:59:30.731Z] INFO: Imported 20 records successfully

## Importing UTF-8 encoded CSV with UTF-8 encoding.
$ ./bin/cli-kintone-macos record import \
        --app 123 \
        --file-path ./app123_utf8.csv \
        --attachments-dir attachments.app123_utf8 \
        --update-key レコード番号 \
        --encoding utf8
[2023-08-22T12:59:36.882Z] INFO: Preparing to import records...
[2023-08-22T12:59:37.148Z] INFO: Starting to import records...
[2023-08-22T12:59:37.776Z] INFO: Imported 20 records successfully

## Importing UTF-8 encoded CSV with SJIS encoding.
$ ./bin/cli-kintone-macos record import \
        --app 123 \
        --file-path ./app123_utf8.csv \
        --attachments-dir attachments.app123_utf8 \
        --update-key レコード番号 \
        --encoding sjis
[2023-08-22T12:59:40.955Z] ERROR: Error: Failed to decode the specified CSV file.
[2023-08-22T12:59:40.955Z] ERROR: The specified encoding (sjis) might mismatch the actual encoding of the CSV file.

## Importing SJIS encoded CSV with default encoding (UTF-8).
$ ./bin/cli-kintone-macos record import \
        --app 123 \
        --file-path ./app123_sjis.csv \
        --attachments-dir attachments.app123_sjis \
        --update-key レコード番号
[2023-08-22T12:59:57.408Z] ERROR: Error: Failed to decode the specified CSV file.
[2023-08-22T12:59:57.408Z] ERROR: The specified encoding (utf8) might mismatch the actual encoding of the CSV file.

## Importing SJIS encoded CSV with UTF-8 encoding.
$ ./bin/cli-kintone-macos record import \
        --app 123 \
        --file-path ./app123_sjis.csv \
        --attachments-dir attachments.app123_sjis \
        --update-key レコード番号 \
        --encoding utf8
[2023-08-22T13:00:05.979Z] ERROR: Error: Failed to decode the specified CSV file.
[2023-08-22T13:00:05.979Z] ERROR: The specified encoding (utf8) might mismatch the actual encoding of the CSV file.

## Importing SJIS encoded CSV with SJIS encoding.
$ ./bin/cli-kintone-macos record import \
        --app 123 \
        --file-path ./app123_sjis.csv \
        --attachments-dir attachments.app123_sjis \
        --update-key レコード番号 \
        --encoding sjis
[2023-08-22T13:00:08.549Z] INFO: Preparing to import records...
[2023-08-22T13:00:08.821Z] INFO: Starting to import records...
[2023-08-22T13:00:09.381Z] INFO: Imported 20 records successfully

NOTE: I updated the PR title to make the release note more helpful.

authors: hung-cybo mshrtsr

repo: kintone/cli-kintone


text:
multiselectize functionality in demo

Trying to find the source behind the multi selectize in the demo but unable to. I thought it would be part of the demo/demo.elm, all I found though was this issue saying that it isn't implemented in this repo: https://github.com/kirchner/elm-selectize/issues/2 dating back to august.
So is the functionality shown in the demo implemented in the repo? Confused... if yes, how do I do multi selection? ( as on further investigation, there are commits related to it! :)

@mordrax yes, the multiselectize implementation is in the master branch. :) I have not decided yet if the api is good as it is now, so it is not published, yet.

authors: kirchner mordrax

repo: kirchner/elm-selectize


text:
Switch control with default set to OFF shows as ON

Issue description:
All of my 40 themes have this issue when updating. Switch controls set to OFF as default shows as ON and are broken.
Version used:
Kirki 4.0.15
Using theme_mods or options?
Code to reproduce the issue (config + field(s))
Example field:
// Blog: Frontpage Widgets Bottom
Kirki::add_field( 'incolor_theme', array(
	'type'			=> 'switch',
	'settings'		=> 'frontpage-widgets-bottom',
	'label'			=> esc_html__( 'Frontpage Widgets Bottom', 'incolor' ),
	'description'	=> esc_html__( '2 columns of widgets', 'incolor' ),
	'section'		=> 'blog',
	'default'		=> 'off',
) );

Or download one of my themes here and check: https://alx.media/themes/incolor/ (/functions/kirki/ folder needs to be updated to 4.0.15)
Customize > Theme Options > Blog > Frontpage Widgets Top/Bottom (shown as ON with it set to OFF)
(The code could look like this in a theme:)
<?php if ( get_theme_mod('my-option','off') == 'on' ) : ?>

I'd do anything for backwards compatibility here on the switch. Rebuilding many options in each theme, and then do it 40 times is... well, far from fun.

We got you, this was an oversight. I'll report back once this is fixed! :)

Hi @AlxMedia , thanks a lot for reporting this issue.
It's is now fixed (I have tested it) in v4.0.16. Download link: v4.0.16
Please let us know if this version fixes your issue :)
Thanks!

Seem to work great from the testing I've done, thanks for this @contactjavas - I can now sleep without worrying about having to remake 40 themes :D

Hi @AlxMedia , I'm sorry, v4.0.16 contains some notice messages if you don't define the default argument.
Please update to v4.0.17 that include the fix for that. Download link: v4.0.17
Thanks :)

authors: AlxMedia MapSteps contactjavas

repo: kirki-framework/kirki


text:
Typo fix

fix typo in readme file

Thank you @jinjorge !!

authors: jinjorge kishikawakatsumi

repo: kishikawakatsumi/KeychainAccess


text:
Fix tests link error

Supersedes https://github.com/kishikawakatsumi/UICKeyChainStore/pull/139

Coverage remained the same at 73.272% when pulling 1fc9f189d3ce88c5e3ef7c698a960c762b31cefe on fix-tests-link-error into 3ef4a14fdbbc2d1891a5403c1877d2d6286b62be on master.

Coverage remained the same at 73.272% when pulling 1fc9f189d3ce88c5e3ef7c698a960c762b31cefe on fix-tests-link-error into 3ef4a14fdbbc2d1891a5403c1877d2d6286b62be on master.

authors: coveralls kishikawakatsumi

repo: kishikawakatsumi/UICKeyChainStore


text:
Implement complete tests

This branch implements "complete" end to end tests which actually send data to the server. The code does include an API key but it is my test key so no problem for me.
Also, this branch implements POST if the URL body of a request is too big.

I'm not sure either. Ask Paul what he thinks. AFAIK forTesting will not
cause any harm when called even in a production setting, it just prevents a
race condition which normally does not occur in practice.
On Thu, Feb 23, 2017 at 11:05 AM, Andrew Hanna notifications@github.com
wrote:

@percyhanna commented on this pull request.
👍
In KISSmetricsAPI/KISSmetricsAPI.h
https://github.com/kissmetrics/KISSmetrics-iOS-SDK/pull/23#discussion_r102790497
:

@@ -57,7 +57,17 @@ typedef NS_ENUM(NSInteger, KMARecordCondition) {
//---

(KISSmetricsAPI *)sharedAPI;

+//------------
+// - forTesting:
+//
+// Prepares the API to be used for unit testing.
+//
+// Discussion:
+// The API initializes in a state that does not send events to the server. Sending is enabled in the verification process which happens asynchronously.
+// When performing end-to-end testing, a race condition occurs where test events get sent before verification completes. This method ensures the verification
+// processc completes before events are sent.
+//---
+- (void) forTesting;
Not sure about best practices, but should this be excluded from release
builds with some form of preprocessor directive?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kissmetrics/KISSmetrics-iOS-SDK/pull/23#pullrequestreview-23558470,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEEm4ME64XyUBJ-qPYa1bKupxpYxgItuks5rfdhdgaJpZM4MH_o0
.

Good catch, yes it can be removed.
On Thu, Feb 23, 2017 at 12:34 PM, Andrew Hanna notifications@github.com
wrote:

@percyhanna commented on this pull request.
In KISSmetricsAPI/KMAConnection.m
https://github.com/kissmetrics/KISSmetrics-iOS-SDK/pull/23#discussion_r102811513
:

@@ -61,10 +61,39 @@ - (void)sendRecordWithURLString:(NSString *)urlString delegate:(id <KMAConnectio
// Retain the urlString, we'll need to pass this back to the delegate
_urlString = urlString;

// We use the default cachePolicy but set our own timeoutInterval
NSURLRequest *request = [NSURLRequest requestWithURL:[NSURL URLWithString:urlString]

NSURL* url = [NSURL URLWithString:urlString];

long query_length = (long) url.query.length;

NSMutableURLRequest *request;

if (query_length > 2000)

While glancing at some other code, I noticed this comment
https://github.com/kissmetrics/KISSmetrics-iOS-SDK/blob/master/KISSmetricsAPI/KISSmetricsAPI.h#L216-L222.
Could we update/remove it, since it should no longer apply.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kissmetrics/KISSmetrics-iOS-SDK/pull/23#pullrequestreview-23579991,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEEm4OtP12t40IHJQi1P3Ypb1pCG8PWLks5rfe1xgaJpZM4MH_o0
.

repo: kissmetrics/KISSmetrics-iOS-SDK


text:
Closing a whitelisting notification blacklists the project directory

Open a file which is not whitelisted and not yet blacklisted
The VSCode plugin will show a notification which has a Close button
A click on close blacklists the project dir ("C:\users\jansorg" in my case) but it should blacklist the current file only

I don't think that have been any different in the other plugins, we're blacklisting the directory returned by the projectdir endpoint, because otherwise a user would be bugged for every file of a project on which he doesn't care having kite running

@abe33 As far as I can tell this is different than the in the other editors.
As far as I see blacklisting with the file's path adds the parent directory to the list in Kite's settings.
I just tested with Atom, a click on the X button to close the notification blacklisted "c:\users\jansorg\pycharmprojects\testpython\blacklisted" and not "c:\users\jansorg".
PyCharm and Sublime work in the same way.
Could you update the "blacklist after user clicked on X" to blacklist the file?
Spec is at https://kite.quip.com/8xWpAmOqyh96/Behavioral-specification-Permissions#GZbACABGYBx.
We can discuss the best path to blackliste here, of course. But that will have to be done for all editors then. For now, VSCode should work the same way as the others do.

repo: kiteco/vscode-plugin