text:
Support for applying marker method in parallel with ufo

Feature description
Hi there! Is it somehow possible to implement support to apply methods, that was selected in ufo (ts/lsp) simultaneously with marker (to support vim's default {{{/}}} at the same time)?
Describe the solution you'd like
I'm not sure, how is it supposed to look like if taking {n,}vim's internal marker method, but, probably, it can be made by writing custom function, that implements same behaviour :shrug:
I'll try to invent something myself, but can't promise anything, and would be glad to get some help/code snippets for that.
Or, if that would "internal" functionality of ufo :grinning:
Thanks in advance!
Additional context
No response

thanks

This was my solution to this problem.  it is not perfect, but it works well enough for my needs.
	{
		"kevinhwang91/nvim-ufo",
		event = { "BufRead" },
		dependencies = "kevinhwang91/promise-async",
		config = function()
			vim.o.foldcolumn = "1" -- '0' is not bad
			vim.o.foldlevel = 99 -- Using ufo provider need a large value, feel free to decrease the value
			vim.o.foldlevelstart = 99
			vim.o.foldenable = true

			-- Using ufo provider need remap `zR` and `zM`. If Neovim is 0.6.1, remap yourself
			vim.keymap.set("n", "zR", require("ufo").openAllFolds)
			vim.keymap.set("n", "zM", require("ufo").closeAllFolds)
			vim.keymap.set("n", "zK", function()
				local winid = require("ufo").peekFoldedLinesUnderCursor()
				if not winid then
					vim.lsp.buf.hover()
				end
			end, { desc = "Peek Fold" })

			local ftMap = {
				git = "",
			}
			local foldingrange = require("ufo.model.foldingrange")
			local bufmanager = require("ufo.bufmanager")

			local CustomMarkerProvider = {}

			function CustomMarkerProvider.getFolds(bufnr)
				local buf = bufmanager:get(bufnr)
				if not buf then
					return
				end
				local fmrOpen  = vim.opt.foldmarker:get()[1]
				local fmrClose = vim.opt.foldmarker:get()[2]
				local commentstring = vim.opt.commentstring:get()
				if commentstring == "/*%s*/" then
					-- Hack for c++ and other // and /* */ langs
					commentstring = "//%s"
				end
				local openRegx = commentstring .. "*.-" .. fmrOpen
				local closeRegx = commentstring .. "*.-" .. fmrClose
				local summaryRegx = openRegx .. "%s*(.*)"
				local lines = buf:lines(1, -1)

				local ranges = {}
				local stack = {}

				for lnum, line in ipairs(lines) do
					-- Check for start marker
					if line:match(openRegx) then
						table.insert(stack, lnum)
					-- Check for end marker
					elseif line:match(closeRegx) then
						local startLnum = table.remove(stack)
						if startLnum then
							local summary = lines[startLnum]:match(summaryRegx)
							table.insert(ranges, foldingrange.new(startLnum - 1, lnum - 1, summary))
						end
					end
				end

				return ranges
			end

			local function customizeSelector(bufnr)
				local ranges = CustomMarkerProvider.getFolds(bufnr)
				local maybe_additional_ranges = require("ufo").getFolds(bufnr, "treesitter")
				if next(maybe_additional_ranges) ~= nil then
					ranges = vim.list_extend(ranges, maybe_additional_ranges)
				else
					ranges = vim.list_extend(ranges, require("ufo").getFolds(bufnr, "indent"))
				end
				return ranges
			end

			require("ufo").setup({
				provider_selector = function(bufnr, filetype, buftype)
					return ftMap[filetype] or customizeSelector
				end,
			})
		end,
	},

This was my solution to this problem. it is not perfect, but it works well enough for my needs.
	{
		"kevinhwang91/nvim-ufo",
		event = { "BufRead" },
		dependencies = "kevinhwang91/promise-async",
		config = function()
			vim.o.foldcolumn = "1" -- '0' is not bad
			vim.o.foldlevel = 99 -- Using ufo provider need a large value, feel free to decrease the value
			vim.o.foldlevelstart = 99
			vim.o.foldenable = true

			-- Using ufo provider need remap `zR` and `zM`. If Neovim is 0.6.1, remap yourself
			vim.keymap.set("n", "zR", require("ufo").openAllFolds)
			vim.keymap.set("n", "zM", require("ufo").closeAllFolds)
			vim.keymap.set("n", "zK", function()
				local winid = require("ufo").peekFoldedLinesUnderCursor()
				if not winid then
					vim.lsp.buf.hover()
				end
			end, { desc = "Peek Fold" })

			local ftMap = {
				git = "",
			}
			local foldingrange = require("ufo.model.foldingrange")
			local bufmanager = require("ufo.bufmanager")

			local CustomMarkerProvider = {}

			function CustomMarkerProvider.getFolds(bufnr)
				local buf = bufmanager:get(bufnr)
				if not buf then
					return
				end
				local fmrOpen  = vim.opt.foldmarker:get()[1]
				local fmrClose = vim.opt.foldmarker:get()[2]
				local commentstring = vim.opt.commentstring:get()
				if commentstring == "/*%s*/" then
					-- Hack for c++ and other // and /* */ langs
					commentstring = "//%s"
				end
				local openRegx = commentstring .. "*.-" .. fmrOpen
				local closeRegx = commentstring .. "*.-" .. fmrClose
				local summaryRegx = openRegx .. "%s*(.*)"
				local lines = buf:lines(1, -1)

				local ranges = {}
				local stack = {}

				for lnum, line in ipairs(lines) do
					-- Check for start marker
					if line:match(openRegx) then
						table.insert(stack, lnum)
					-- Check for end marker
					elseif line:match(closeRegx) then
						local startLnum = table.remove(stack)
						if startLnum then
							local summary = lines[startLnum]:match(summaryRegx)
							table.insert(ranges, foldingrange.new(startLnum - 1, lnum - 1, summary))
						end
					end
				end

				return ranges
			end

			local function customizeSelector(bufnr)
				local ranges = CustomMarkerProvider.getFolds(bufnr)
				local maybe_additional_ranges = require("ufo").getFolds(bufnr, "treesitter")
				if next(maybe_additional_ranges) ~= nil then
					ranges = vim.list_extend(ranges, maybe_additional_ranges)
				else
					ranges = vim.list_extend(ranges, require("ufo").getFolds(bufnr, "indent"))
				end
				return ranges
			end

			require("ufo").setup({
				provider_selector = function(bufnr, filetype, buftype)
					return ftMap[filetype] or customizeSelector
				end,
			})
		end,
	},

Don't use regex to parse it, should use stack structure.
Regex can't handle open and closed markers for complicated content that contains open and closed marks.

This was my solution to this problem. it is not perfect, but it works well enough for my needs.
	{
		"kevinhwang91/nvim-ufo",
		event = { "BufRead" },
		dependencies = "kevinhwang91/promise-async",
		config = function()
			vim.o.foldcolumn = "1" -- '0' is not bad
			vim.o.foldlevel = 99 -- Using ufo provider need a large value, feel free to decrease the value
			vim.o.foldlevelstart = 99
			vim.o.foldenable = true

			-- Using ufo provider need remap `zR` and `zM`. If Neovim is 0.6.1, remap yourself
			vim.keymap.set("n", "zR", require("ufo").openAllFolds)
			vim.keymap.set("n", "zM", require("ufo").closeAllFolds)
			vim.keymap.set("n", "zK", function()
				local winid = require("ufo").peekFoldedLinesUnderCursor()
				if not winid then
					vim.lsp.buf.hover()
				end
			end, { desc = "Peek Fold" })

			local ftMap = {
				git = "",
			}
			local foldingrange = require("ufo.model.foldingrange")
			local bufmanager = require("ufo.bufmanager")

			local CustomMarkerProvider = {}

			function CustomMarkerProvider.getFolds(bufnr)
				local buf = bufmanager:get(bufnr)
				if not buf then
					return
				end
				local fmrOpen  = vim.opt.foldmarker:get()[1]
				local fmrClose = vim.opt.foldmarker:get()[2]
				local commentstring = vim.opt.commentstring:get()
				if commentstring == "/*%s*/" then
					-- Hack for c++ and other // and /* */ langs
					commentstring = "//%s"
				end
				local openRegx = commentstring .. "*.-" .. fmrOpen
				local closeRegx = commentstring .. "*.-" .. fmrClose
				local summaryRegx = openRegx .. "%s*(.*)"
				local lines = buf:lines(1, -1)

				local ranges = {}
				local stack = {}

				for lnum, line in ipairs(lines) do
					-- Check for start marker
					if line:match(openRegx) then
						table.insert(stack, lnum)
					-- Check for end marker
					elseif line:match(closeRegx) then
						local startLnum = table.remove(stack)
						if startLnum then
							local summary = lines[startLnum]:match(summaryRegx)
							table.insert(ranges, foldingrange.new(startLnum - 1, lnum - 1, summary))
						end
					end
				end

				return ranges
			end

			local function customizeSelector(bufnr)
				local ranges = CustomMarkerProvider.getFolds(bufnr)
				local maybe_additional_ranges = require("ufo").getFolds(bufnr, "treesitter")
				if next(maybe_additional_ranges) ~= nil then
					ranges = vim.list_extend(ranges, maybe_additional_ranges)
				else
					ranges = vim.list_extend(ranges, require("ufo").getFolds(bufnr, "indent"))
				end
				return ranges
			end

			require("ufo").setup({
				provider_selector = function(bufnr, filetype, buftype)
					return ftMap[filetype] or customizeSelector
				end,
			})
		end,
	},

No need to handle commentstring;
Use string.find({s}, {pattern}, 0, true]])  to handle plain marker instead of regex;

I implemented the marker provider in a fork: https://github.com/LucasAVasco/nvim-ufo/tree/main
Pull request: https://github.com/kevinhwang91/nvim-ufo/pull/218
I also implemented a function to merge UFO providers (also can merge functions that returns Foldings): https://github.com/LucasAVasco/nvim-ufo/tree/featMergeProviders
Pull request: https://github.com/kevinhwang91/nvim-ufo/pull/219
If you want to use both (and my pull requests have not yet been accepted), you can use this branch: https://github.com/LucasAVasco/nvim-ufo/tree/markerAndMergeProviders

authors: LucasAVasco danpf kevinhwang91 msva


text:
🛑 FX blog (kty) is down

In ca2e744, FX blog (kty) (https://foxter-blogeditor.konecty.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FX blog (kty) is back up in a805d75 after 6 minutes.

source: gharchive/issue

repo: keviocastro/upptime

license: MIT

license_type: permissive

license_source: github-api


text:
🛑 FX blog (kty) is down

In 8f60faf, FX blog (kty) (https://foxter-blogeditor.konecty.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FX blog (kty) is back up in 573cda7 after 9 minutes.


text:
🛑 FX corretor (kty) is down

In 3be958d, FX corretor (kty) (https://corretores.foxterciaimobiliaria.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FX corretor (kty) is back up in cbdd0a2 after 9 minutes.


text:
🛑 FX corretor (kty) is down

In d8a5847, FX corretor (kty) (https://corretores.foxterciaimobiliaria.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FX corretor (kty) is back up in 8c4af8a after 9 minutes.


text:
🛑 FX corretor (kty) is down

In c11bf03, FX corretor (kty) (https://corretores.foxterciaimobiliaria.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FX corretor (kty) is back up in a0628eb after 24 minutes.


text:
🛑 FX corretor (kty) is down

In 64f1615, FX corretor (kty) (https://corretores.foxterciaimobiliaria.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FX corretor (kty) is back up in 393c368 after 8 minutes.


text:
🛑 FX corretor (kty) is down

In cc806df, FX corretor (kty) (https://corretores.foxterciaimobiliaria.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FX corretor (kty) is back up in f1c8e3d after 8 minutes.


text:
🛑 FX corretor (kty) is down

In 32f9b7c, FX corretor (kty) (https://corretores.foxterciaimobiliaria.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FX corretor (kty) is back up in afd1c0c after 6 minutes.


text:
🛑 FX corretor (kty) is down

In 827655d, FX corretor (kty) (https://corretores.foxterciaimobiliaria.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FX corretor (kty) is back up in 7de86f8 after 38 minutes.


text:
🛑 FX corretor (kty) is down

In bd5eca7, FX corretor (kty) (https://corretores.foxterciaimobiliaria.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FX corretor (kty) is back up in c05cfcd after 10 minutes.


text:
🛑 FX blog (kty) is down

In 59c2441, FX blog (kty) (https://foxter-blogeditor.konecty.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FX blog (kty) is back up in b33a040 after 41 minutes.


text:
🛑 FX corretor (kty) is down

In 14e2a89, FX corretor (kty) (https://corretores.foxterciaimobiliaria.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FX corretor (kty) is back up in 700993d after 6 minutes.


text:
🛑 FX corretor (kty) is down

In ad5e11f, FX corretor (kty) (https://corretores.foxterciaimobiliaria.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FX corretor (kty) is back up in 4f6c48b after 18 minutes.


text:
🛑 FX corretor (kty) is down

In 7bec5b7, FX corretor (kty) (https://corretores.foxterciaimobiliaria.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FX corretor (kty) is back up in ee38d56 after 13 minutes.


text:
🛑 FX blog (kty) is down

In c8e7629, FX blog (kty) (https://foxter-blogeditor.konecty.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FX blog (kty) is back up in 8e4f8a2 after 5 minutes.


text:
🛑 FX net (kty) is down

In 0bef64b, FX net (kty) (https://foxter.net.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FX net (kty) is back up in f93cf38.


text:
🛑 ky sicesp ky is down

In 5014d42, ky sicesp ky (sinicesp.konecty.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ky sicesp ky is back up in 8971fb1 after 7 minutes.


text:
🛑 GIPI financial is down

In 8edbfd6, GIPI financial (https://financial.app.gipisistemas.com.br/public/check/health) was down:

HTTP code: 404
Response time: 298 ms

Resolved: GIPI financial is back up in f19c0bb after 9 minutes.


text:
🛑 FX corretor (kty) is down

In 2e3f15b, FX corretor (kty) (https://corretores.foxterciaimobiliaria.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FX corretor (kty) is back up in be27f12 after 7 minutes.


text:
Add proxy auth

I'm working in an environment where there is an authenticated proxy.
Fix authentication information to pass to the proxy.

Just pass {proxy: {proxyAuth: 'auth'}} to the options.

Thank you tell me a good way. But, it did not work it's that way.
var agent = require('caw')('http://proxy.host.example.com:8080', {
    proxy: {
        proxyAuth: 'hoge'
    }
});

console.log(agent.options);

I ran this script. but, results were not set proxy information well.
{ proxy: { proxyAuth: 'hoge' } }

This PR, the kevva/download#64 in my environment is one of the reasons for not working.
Would you merge?

Fixed in https://github.com/kevva/caw/pull/9. Seems the author changed his mind.
Thanks for the contribution, @masakura.

I tested it with authentication proxy. It works normally.
I'm happy!
Thanks!

source: gharchive/pull-request

authors: kevva masakura shinnn

repo: kevva/caw

license: mit

license_source: bigquery


text:
Switch events without reload #37 + auto event select #34

BEGINRELEASENOTES

2 (somewhat important) issues are addressed here. First, #37 is developed here. Now, users can change an event without having to reload. This improves the interactivity of dmx.
In #34, users must choose an initial event to visualize when loading a file. However, this value sometimes cannot be found (always on 0), which could be confusing. That's why this recommendation is implemented here. Now the value is auto-selected according to the file.

ENDRELEASENOTES

Very nice.
I observed the following issue: If I switch events very quickly in the tree view, I can trigger a mis-render, where I think what is happening is that the symbols from one event are overlaid onto another event. Or maybe the symbols of the current event are drawn twice but once out of position (see screenshot on the left)

And then I would also have an additional feature request (which might already solve the first one). Instead of having the lef-right arrows for the event selection in the tree view, I think I would also like a drop-down menu there. Or if both options are possible simultaneously, e.g. by having the arrows for switching, and if I click on the event itself I get a dropdown menu to select.

And then I would also have an additional feature request (which might already solve the first one). Instead of having the lef-right arrows for the event selection in the tree view, I think I would also like a drop-down menu there. Or if both options are possible simultaneously, e.g. by having the arrows for switching, and if I click on the event itself I get a dropdown menu to select.

I didn't specify it, but indeed there is a dropdown menu. If you click over the event number, then you can see the available events and choose between them (so both options are present, arrows + menu).

Huh, I didn't see that (or didn't figure it out at least). Very nice then. I am wondering whether it could be made a bit more obvious that this is clickable and will give you a list to select from.

This is nice :)

Can you unify the font sizes in the menus? It looks to me that the font size of the event switcher is a bit larger
Would it be possible to keep window in the position from the previous event?
What happens with the dropdown if there is many events to select from? Is there any scrollbar?

More comments from the meeting:

Event selection in the tree view should have a max height and a scroll bar for event selection
Drawing of symbols is lagging a bit, so that symbols from previous events are visible. We could document that toggling the PDG IDs, can fix things
Maybe delay start drawing of events after the selection to avoid some issues when quickly switching events

be made a bit more obvious that this is clickable and will give you a list to select from.

[x] Now, when users hover on an element, the background color changes + underline.

Can you unify the font sizes in the "menus"? It looks to me that the font size of the event switcher is a bit larger

[x] Oh didn't notice this 😄, fixed.

Would it be possible to keep window in the position from the previous event?

[x] Done!

What happens with the dropdown if there is many events to select from? Is there any scrollbar?

[x] The scrollbar is now implemented.

Maybe delay start drawing of events after the selection to avoid some issues when quickly switching events

[ ] Hmm, this is a technical issue and somewhat "hard" to fix. Even if we add a setTimeOut function, and disable the arrows to switch between events, the code that draws the PDGs has an event on it, that forces to draw sooner or later the image for MCParticles. We could make this code async, so we always wait for the image to load even if is already loaded but then we have to make all drawing-related code async, and this could affect other functions behave. For example, filtering or getting visible particles. This causes a bit of noise when drawing. So taking into account the trade-offs, we may want to leave it as it is. The simplest way to show the user a "loading" state, is to change the event number after the objects have been drawn (we can not take for granted that all images will be loaded). I would like to know what you both @tmadlener and @kjvbrt think, we can try the option I mentioned. But this is how I see this.

Very nice work on the visuals. I like it.
If we cannot change the drawing easily, can we put a loading ... or drawing ... on the screen, or maybe simply make the arrows / event selection unclickable until it's done? Otherwise we keep it as it is at the moment and open an issue to keep track of it.

Otherwise we keep it as it is at the moment and open an issue to keep track of it.

Yeah, I would prefer to open an issue and not lose this. I know how to fix it, but I would have to incorporate a lot of "boilerplate" async code. However, drawing functions may change (making these changes in vain), so right I wouldn't worry about too much.

Would it be possible to keep window in the position from the previous event?

* [ ]  Done!

The position is still reset for me (to x: 0, y: middle). I'm on latest Firefox in Fedora 40.

Can you also harmonize shades of grey in the "menus"? I found three different ones :)

The position is still reset for me (to x: 0, y: middle). I'm on latest Firefox in Fedora 40.

Could you please try "hard" reloading the website (maybe ctrl + r)? I think it's cached because it works for me both in the preview and on firefox 126.0.1.

Can you also harmonize shades of grey in the "menus"? I found three different ones :)

Of course!

The position is still reset for me (to x: 0, y: middle). I'm on latest Firefox in Fedora 40.

Could you please try "hard" reloading the website (maybe ctrl + r)? I think it's cached because it works for me both in the preview and on firefox 126.0.1.

Still does not work, but let's merge this PR and see. If it does not work I will create issue...

authors: brauliorivas kjvbrt tmadlener


text:
Reddit Verification Immediately Fails - looks like keybase is blocked from accessing the subreddit

Here's my proof (replaced an older one that previously worked). I tried deleting a post and re-posting just in case, no change in the failure behaviour:
https://old.reddit.com/r/KeybaseProofs/comments/o0c2hw/my_keybase_proof_redditarkham_keybasecomerford/
This is the original from 6 years ago which used to work, but failed recently:
https://old.reddit.com/r/KeybaseProofs/comments/2eu8q2/my_keybase_proof_redditarkham_keybasecomerford/

This just started working again (~10 hours after I filed this issue), closing

repo: keybase/client


text:
cant find race-free state for 5004b083e94e008e9f88bdb9ede5a724 (error 236)

Hi, my whole team on Keybase has gone down. I get the following message, error recalculating name for shalimardairy: cant find race free state 5004b083e94e008e9f88bdb9ede5a724 (error 236). this will pop up when im trying to post a picture or write a message in any of my teams channels. can dm me for username or any other details that are required. Thanks!

Adding that multiple folks on the chia_network team have seen this problem too.

Have the exact same issue, started on Windows 10, and in my case, it happened after I tried to create a team. It generated an almost identical error (except for the uid associated with my user instead, 95ee15759d9b44fad5e9a33f27540b19) in my case at the 'channel creation' step. I ended up needing to hit 'back' until the team creation dialog was gone. Even though it gave an error, it still gave me the team as an option to the left. But I wasn't able to create any additional channels in the team. I didn't add any other users to my team, had planned to do that later. I also tried to upload a picture as the team profile picture and this spun for an inordinately long time and then gave an error that the image wasn't supported (which is odd since I was able to use literally the exact same file 2 days ago on another team). Thinking it was related to perhaps some cache or local file corruption, I completely signed out of keybase on my Windows system, only to be greeted with the error 236 message right after I give the app my username. I also tried completely blowing away all the files on my Windows computer.
I was unable to see any devices in the list on my Android phone, but the account was still signed in and I was able to send/receive messages with other keybase users. I cleared the app data on my android app to see if the same error 236 showed up when I tried to sign back in on that device (yes, it does).
I have also attempted to sign back in using the cli on Linux, no joy there either. I still have a paper key so I'm sure I can sign back in as needed, and my account on keybase.io still shows all the history/devices.
I have attached the keybase log files from %LOCALAPPDATA% on my Win10 system. Hopefully nothing sensitive there lol
Keybase.zip

hi all, this should be resolved. sorry for the trouble.
cc @maxtaco

Thank you!


text:
Installer can lookup bundled version instead of storing in plist

I was doing this really roundabout way of storing what the versions of the bundled binaries were.
The installer can look this up when it runs since it know the paths to the binaries. This simplifies stuff and makes the installer even simpler/smarter, and fixes a bug where the installer wasn't restarting services on upgrade.

cc @cjb

Concept looks good to me, maybe @maxtaco could do a quick review of the Go code?

Looks good to me

authors: cjb gabriel maxtaco


text:
Tweaks on user switching

@keybase/react-hackers

@jakob223 I can't manage to see the mobile version for this feature. Is it behind a feature flag on mobile?

Will this show a badge on users with currently unread notifications?

@junderw The first version of it won't have badges but it's on our roadmap.

@keybase/react-hackers Bump ^

@jakob223 I can't manage to see the mobile version for this feature. Is it behind a feature flag on mobile?

I think I answered this in chat, but in case I didn't: yes, it's behind a feature flag for now until we can polish it when IMP TOFU is finished.

authors: cecileboucheron jakob223 junderw


text:
PICNIC-448: What's New Thingy

Summary
Whats New is enabled behind feature flag whatsNew.

On desktop edit Keyabse.app.debug

On native edit local-debug.native.tsx

The badge state of the items is a function of the last version that has been viewed. To reset the last seen version, execute DEBUGStore.dispatch({ type: 'config:setWhatsNewLastSeenVersion', payload: { lastSeenVersion: '0.0.0' } }) in the console.
Mockups
Whats-New-Thingy Desktop Zeplin
Whats-New-Thingy Mobile Zeplin
@keybase/react-hackers

Looks cool!
A few visual design comments:

Buttons should be Small=true
Pane shoud have a drop shadow (the same as all the other tooltips around the app)
First card should start 8px from the top, right now it sticks to it

It seems like the space is too big here between the text and the button. Is it because there's no image?

Should we add it to local-debug.desktop.tsx's inAdmin section so that the feature flag turns on for admins only on desktop immediately?

authors: cecileboucheron cjb thebearjew


text:
alignment for whats new on an ipad

whats new looks weird on ipad. this tightens it up.

i pulled in commits from https://github.com/keybase/client/pull/22472/files so i could use mediumWidth rather than hardcoding the same constant
i checked on iphone and it looks the same before and after

before

after

@keybase/picnicsquad @keybase/react-hackers


text:
Fix 'Someone else...' dropdown on mobile

@keybase/react-hackers
The dropdown calls this.setState({value}) and then this._selected(), which looks at this.state.value to see what was chosen.  But setState() is asynchronous -- it registers a pending state transition, it's not atomic.  To wait for setState to complete before inspecting this.state, we can pass our callback as the second argument to setState().
Tested on Android and iOS.

👍

authors: MarcoPolo cjb


text:
Image and non-image attachment popups on mobile

This PR is split into 3 commits:

[x] Forces portrait mode on ios and changes a console.warn to a log so i don't get yellowboxed on every inbox load (https://github.com/keybase/client/commit/fc1421b850da66892af7d3bd6c928539d3748112)
[x] Reduces overdraw on mobile. This is due to transparent backgrounds on things blending that serve no purpose. The fix is to explicitly set background colors on the children so they're opaque and no longer need to blend (https://github.com/keybase/client/commit/b5552c5807b713b2160dff4f9549fc99fda6abc2)
[x] The actual popup. https://github.com/keybase/client/commit/f42953cc4fff09de66c13e77b71284930b5d6dee

@keybase/react-hackers

The commits 8a752c99b78b...f42953cc4fff introduce visual changes on linux. :mag_right: 2 changed

Changed: Attachment_Message-Basic_Preview_Image_Downloaded (before) (after)

Changed: Attachment_Message-Basic_Downloading (before) (after)

[ ] Fix desktop visdiff

authors: chrisnojima keybase-ci-visdiff


text:
update flow to version 52

I forget, should I take out yarn.lock?
@keybase/react-hackers

We always check in yarn.lock
On Tue, Aug 15, 2017 at 6:36 PM Steve Sanders notifications@github.com
wrote:

I forget, should I take out yarn.lock?
@keybase/react-hackers
https://github.com/orgs/keybase/teams/react-hackers
You can view, comment on, or merge this pull request online at:
https://github.com/keybase/client/pull/8129
Commit Summary

update flow, WIP
FlowIssue

File Changes

M shared/.flowconfig
https://github.com/keybase/client/pull/8129/files#diff-0 (2)
M shared/constants/types/flux.js
https://github.com/keybase/client/pull/8129/files#diff-1 (1)
M shared/engine/index.platform.desktop.js
https://github.com/keybase/client/pull/8129/files#diff-2 (1)
M shared/package.json
https://github.com/keybase/client/pull/8129/files#diff-3 (2)
M shared/yarn.lock
https://github.com/keybase/client/pull/8129/files#diff-4 (6)

Patch Links:

https://github.com/keybase/client/pull/8129.patch
https://github.com/keybase/client/pull/8129.diff

—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
https://github.com/keybase/client/pull/8129, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAfhU0HzeBJspJSgthXPjzS5XxUjIalTks5sYh1dgaJpZM4O4Mtz
.

authors: chrisnojima zanderz


text:
make GetPasswd take a terminal file descriptor

There are times when we need user input from the terminal, even though
our stdin is piped from something else. (For example, reading an
encrypted file over stdin, and asking the user for the password.) Make
GetPasswd* take an explicit file descriptor for the terminal, so that
the caller has the option of using /dev/tty.

Tested this on BSD and it turned out the build was broken. Needed a C.int cast.

LGTM if @zanderz is ok with it

A further BSD fix.

LGTM, pending Max's comment :thumbsup:

authors: maxtaco oconnor663 zanderz

repo: keybase/gopass

license: isc


text:
🛑 Telia Sverige AB is down

In 663eb9a, Telia Sverige AB (https://www.telia.se/privat/mitt-telia) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Telia Sverige AB is back up in 1f37cbf after 7 hours, 24 minutes.

repo: keywordnew/stockholm-watchtower


text:
Tekton pipelines

As an alternative to the native Argo pipelines we should allow a user to install Tekton pipelines as explained in the KF documentation here:
https://github.com/kubeflow/kfp-tekton
We should do this using a flag like --tekton

Closing because a duplicate of https://github.com/kf5i/k3ai-plugins/issues/5


text:
Separate termcontext whenever possible

do not review yet

@dwightguth @andreistefanescu please review
There are two major changes in this pull request:

replace TermContext with GlobalContext as much as possible; the key insight here is that KItem doesn't need the fresh counter inside TermContext to compute its sort so that a TermContext could be recreated from the GlobalContext to feed to MetaK.matchable
modify CopyOnWriteTransformer to use the GlobalContext carried by the parameter of the transform method by default so that most substitution related operations do not have to take a TermContext or GlobalContext argument

Are you sure this is actually safe to do? GlobalContext is actually not safe to serialize in a lot of cases. Originally it was not intended to be serialized at all but Andrei persuaded me to let it be serialized in a really hackish way that means that you can get NullPointerExceptions really easily. I think it works right now because we are not actually currently serializing any java kil classes, but that is likely to change for performance reasons eventually. I would feel much better if you either did not include Global Context as part of terms, or found a way to recover the correct GlobalContext for a term following serialization.

@dwightguth I am fully aware of the serialization problem of GlobalContext. But the previous version that carries a TermContext is only worse. I will keep looking for a way to eventually eliminate GlobalContext from terms but, for now, people should just properly set the GlobalContext (e.g., using a CopyOnWriteTransformer) inside the initial term at the beginning of krun whenever necessary.

@dwightguth The fundamental problem of TermContext and/or GlobalContext is the way we invoke builtin functions: it always take a TermContext as an argument even if the function is pure and the argument is not used. In KItem, the GlobalContext is used to compute its sort by MetaK.matchable/unifiable. I cannot imagine that such operation should involve evaluating any impure function (probably not even pure function?). Therefore, I think GlobalContext can be removed from KItem and thus BuiltinMap/Set/List but I just don't have more time to work on it now.

Technically that's not true though. I can write a rule like:
rule isFoo(foo(I:Int)) => someImpureFunction(I)

I think it's safe to require sort predicate rules to be side-effect free.

@andreistefanescu could you take a look at this pull request too?

lgtm

authors: andreistefanescu dwightguth yilongli

repo: kframework/k


text:
Add get capital config request

The /sapi/v1/capital/config/getall route return the wallet status for all coins Binance, useful to know the withdrawal status on different networks per example.

Hello. Sorry, not very active anymore with my projects. You followed the param builder style I had written. nice :)

authors: kgeronim remigastaldi

repo: kgeronim/tokio-binance


text:
Inputmap on cloud

relates to #147:
<+Imago> what do u think of the idea
<+Imago> of automatically saving/loading your inputmap
<+Imago> regardless waht artwork or install or where you are
<+Imago> it will pull your inputmap based off your callsign from the server
<+Imago> for the pilot it would'nt be any work at all
<+Imago> and it would save the pain of reconfiguring your controls
<+Imago> i'm strongly considering implementing the get/post for the inputmap ;p
<+Imago> if it didnt pull it in by the time you join a game (not a trianing missino) then it just uses what you got saved last or the default
<+Imago> and once u connect to he lobby is when it trys to posts ur last saved
<+Imago> how does that sound?
<C101_> it sounds like what you are suggesting is a "steam cloud"
<+Imago> see thats why we all need our own kepmaps saved to the cloud1
Imported from trac ticket #176,  created by Imago on 07-25-2010 at 13:08, last modified: 02-25-2012 at 16:21

it's up to you now.
Trac comment by Imago on 07-28-2010 at 23:24

i don't know how it could get any better than this, besides paying for more than one storage (inbound) node
Trac comment by Imago on 07-30-2010 at 09:32

xynth found a bug.  yay - it's probably with the scramble/unscramble.
Trac comment by Imago on 08-01-2010 at 19:18

scramble/unscramble seemed fine - added debugging for Xynth so he can better confirm if there really is an issue.  Please reopen this ticket if so.
Trac comment by Imago on 08-04-2010 at 01:47

I will need to see the code behind this.
Trac comment by Bard on 08-06-2010 at 00:32

you have access to everything
Trac comment by anonymous on 08-06-2010 at 00:33

Replying to anonymous:

you have access to everything

Where is this particular code? I don't see it and there's nothing here telling me what files to look for.
Trac comment by Bard on 08-07-2010 at 23:18

Code was removed from R6, we need to find a different solution for storing input map.
Trac comment by pkk on 02-25-2012 at 16:21

I didn't know I needed to hold your hand or else be accused of being a thief.  I see now that if I do not hold your hand with things you do not want to put forth effort into understanding, you will slander me.  Please don't do that again.  For now, I will take the time to answer your particularly stupid question.
The code is at "Repository Changesets":
r842 r847 r848 r860 r879
The handler is on CDN at C:\Inetpub\wwwroot\build\nph-InputMap.cgi as the code I outlined in the repository suggests.
Trac comment by anonymous on 08-09-2010 at 19:13

Can't we create a batch script that backups the user's inputmap1.mdl in "my documents/allegbackup" when run?

@echo off
xcopy /W “C:\Program Files(x86)\Microsoft Games\Allegiance 1.2\Production\Artwork/inputmap1.mdl" C:/Users/My Documents

imho, this is very low priority and depends on a much needed major reorganization of artwork files and game files in general.
Meanwhile ACSS could handle this. it's easier to do from it. so better open that issue on ACSS issue list.

authors: LordBlacksun kgersen

repo: kgersen/Allegiance


text:
Can we drop support for autohintexe in Python scripts

Can we drop support for autohintexe in Python scripts and require the Python C extension? This would allow for some simplification of the Python code but I’m not sure if the C extension works with AFDKO setup.

Go ahead and do it. The FDK setup can be adjusted as needed to use this version.

authors: khaledhosny miguelsousa

repo: khaledhosny/psautohint


text:
Project crystal

I think of adding targets to plugin option so if build and test not present in the project.json or the project.json is not present. This will be added automatically:
{
  "targets": [
    {
      "defaultName": "build",
      "customName": "build-maven",
      "defaultTask": "install"
    },
    {
      "defaultName": "test",
      "customName": "test-maven",
      "defaultTask": "test"
    },
    {
      "defaultName": "ktlint",
      "defaultTask": "antrun:run@ktlint"
    }
  ]
}

the customName will be optional.
we should use task from Nx default targets first and if not present we use defaultTask from plugin options.

Im curious how crystal can help with the maven integration. On another note, we could contribute migrators as we currently maintain them ourselves but would be good to put them where they belong?

New design:
{
  "mavenRootDirectory": "nx-maven",
  "localRepoRelativePath: ".m2/repository",
  "buildTargetName": "build-maven",
  "testTargetName": "test-maven",
  "targets": [
    {
      "target": "build-maven",
      "defaultTask": "install"
    },
    {
      "target": "test-maven",
      "defaultTask": "test"
    },
    {
      "target": "ktlint",
      "defaultTask": "antrun:run@ktlint"
    }
  ]
}

I like the *TargetName options.
would change defaultTask to task.

I already added buildTargetName to the plugin options: https://github.com/khalilou88/jnxplus/commit/628c80f1f1652e1f7478b3dae37cf8a0a9ce9789

I believe we need more than one task:
    {
      "target": "build-maven",
     "appTask": "compile -DskipTests=true",
     "libTask": " -DskipTests=true",
      "defaultTask": "install"
    },

Why not use maven lifecycle as names and map to Nx conventions:
{
  "mavenRootDirectory": ".",
  "localRepoRelativePath: ".m2/repository",
  "lintTargetName": "maven-lint",
  "formatTargetName": "maven-format",
  "testTargetName": "maven-test",
  "buildTargetName": "maven-build",
  "releaseTargetName": "maven-release",
  "e2eTestTargetName": "maven-e2e"
  "targets": [
    {
      "target": "testTargetName",
      "task": "test"
    },
    {
      "target": "buildTargetName",
      "task": "clean install -DskipTests=true"
    }
    ...
  ]
}


text:
🛑 screenshots is down

In 447a7dd, screenshots (https://ss.hmuy.tech) was down:

HTTP code: 502
Response time: 3826 ms

Resolved: screenshots is back up in 37f6e7c after 15 minutes.

repo: khanhmuy/webstatus


text:
fix(deps): update module github.com/vektah/gqlparser/v2 to v2.5.19

This PR contains the following updates:

Package
Type
Update
Change

github.com/vektah/gqlparser/v2
require
patch
v2.5.17 -> v2.5.19

Release Notes

vektah/gqlparser (github.com/vektah/gqlparser/v2)
v2.5.19
Compare Source
What's Changed

When format a doc without description, don't add new line between args by @fredzqm in https://github.com/vektah/gqlparser/pull/327
feat(gqlerror): optimize Error method perfomance by @dienvt in https://github.com/vektah/gqlparser/pull/328
Bump the actions-deps group in /validator/imported with 7 updates by @dependabot in https://github.com/vektah/gqlparser/pull/329
Update yaml.v2 to yaml.v3 by @StevenACoffman in https://github.com/vektah/gqlparser/pull/331

New Contributors

@dienvt made their first contribution in https://github.com/vektah/gqlparser/pull/328

Full Changelog: https://github.com/vektah/gqlparser/compare/v2.5.18...v2.5.19
v2.5.18
Compare Source
What's Changed

[SECURITY PROBLEM] Implement a configuration option to disable the suggestion feature when a GraphQL query fails by @tomoikey in https://github.com/vektah/gqlparser/pull/319
Bump @babel/cli from 7.24.8 to 7.25.6 in /validator/imported in the actions-deps group by @dependabot in https://github.com/vektah/gqlparser/pull/315
Bump the actions-deps group in /validator/imported with 6 updates by @dependabot in https://github.com/vektah/gqlparser/pull/323
Bump golangci/golangci-lint-action from 6.1.0 to 6.1.1 in the actions-deps group by @dependabot in https://github.com/vektah/gqlparser/pull/322
Add exported function to remove rules by @ldebruijn in https://github.com/vektah/gqlparser/pull/316
Bump the actions-deps group in /validator/imported with 2 updates by @dependabot in https://github.com/vektah/gqlparser/pull/324
Add an option to format GQL without description by @fredzqm in https://github.com/vektah/gqlparser/pull/325
Update to go v1.21 by @StevenACoffman in https://github.com/vektah/gqlparser/pull/326

New Contributors

@tomoikey made their first contribution in https://github.com/vektah/gqlparser/pull/319
@ldebruijn made their first contribution in https://github.com/vektah/gqlparser/pull/316

Full Changelog: https://github.com/vektah/gqlparser/compare/v2.5.17...v2.5.18

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: dagger/go.sum
Command failed: go get -d -t ./...
go: -d flag is deprecated. -d=true is a no-op
go: dagger/navecd imports
	dagger/navecd/internal/dagger: package dagger/navecd/internal/dagger is not in std (/usr/local/go/src/dagger/navecd/internal/dagger)

repo: kharf/navecd


text:
🛑 Apanova is down

In e41d3b9, Apanova (https://www.apanovabucuresti.ro) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Apanova is back up in 2dc3ed1 after 9 minutes.


text:
Singleton design pattern

Make the App() class to be singleton - can be defined only once.

Go for it @rehan-sattar

repo: khattakdev/bunify


text:
Minimal example for running PWM with custom frequency

Hi,
I am quite new to arduino and need to run PWM with a custom frequency on a pin in a precisely timed fashion at a slow frequency (30/100Hz) on an arduino nano every in an experimental setup (I work in a neuroscience lab).
I guess this toolbox could help doing so, I am however a bit confused by the provided examples which are relatively complex.
I for instance managed to do something similar on an arduino uno using the Arduino PWM Frequency Library (which is unfortunately not compatible with arduino nano every). Using this library, I was for instance able to run PWM at 100Hz with a duty cycle of 50% on pin 3 using:
#include <PWM.h>
#define PIN_PWM 3
int32_t FREQUENCY = 100;  // frequency, Hz
byte DUTY_CYCLE = 128; // 0-255, 128 corresponds to a 50% duty cycle

void setup(){
  InitTimersSafe();
  bool success = SetPinFrequencySafe(PIN_PWM, FREQUENCY);
  pinMode(PIN_PWM, OUTPUT);
}

void loop(){
  // Start PWM on PIN_PWM
  pwmWrite(PIN_PWM, DUTY_CYCLE);
  delay(1000);
  // Stop PWM on PIN_PWM
  digitalWrite(PIN_PWM, LOW);
  delay(1000);
}

Would it be possible to provide a similar minimal example for setting up the frequency/duty cycle and running/stopping PWM on a given pin ? Or did I misunderstand the purpose of this library and should I use a different one ?
Thanks !
rfayat

Ok no worries, the point was not to get you to work code for me, ISR_PWM.setPWM is documented in the README but starting the PWM is not obvious from reading the example. I simply thought that adding a minimal example could help me and others to know how to program and use the library.
Cheers


text:
Minor issues in plotters output

I noticed that the plotters integration has some minor rendering issues when compared to the "reference" plotters backend. Given the two minimal reproduction examples:

Example using cushy/kludgine backend
// Note that this requires to enable the corresponding plotters feature,
// i.e., default-feature = false will not work.
use cushy::widget::MakeWidget;
use cushy::widgets::Canvas;
use cushy::Run;
use plotters::prelude::*;

pub fn basic_plot<A>(
    root: &DrawingArea<A, plotters::coord::Shift>,
) -> Result<(), Box<dyn std::error::Error>>
where
    A: DrawingBackend,
    A::ErrorType: 'static,
{
    root.fill(&WHITE)?;
    let mut chart = ChartBuilder::on(&root)
        .caption("y=x^2", ("sans-serif", 50).into_font())
        .margin(5)
        .x_label_area_size(30)
        .y_label_area_size(30)
        .build_cartesian_2d(-2f32..2f32, -0.1f32..1f32)?;

    chart.configure_mesh().draw()?;

    chart
        .draw_series(LineSeries::new(
            (-100..=100).map(|x| x as f32 / 50.0).map(|x| (x, x * x)),
            &RED,
        ))?
        .label("y = x^2")
        .legend(|(x, y)| PathElement::new(vec![(x, y), (x + 20, y)], &RED));

    chart
        .configure_series_labels()
        .background_style(&WHITE.mix(0.8))
        .border_style(&BLACK)
        .draw()?;

    Ok(())
}

fn plotters() -> impl MakeWidget {
    Canvas::new({
        move |context| {
            basic_plot(&context.gfx.as_plot_area()).unwrap();
        }
    })
}

fn main() -> cushy::Result<()> {
    plotters().run()
}

Example using plain plotters backend
use plotters::prelude::*;

fn main() -> Result<(), Box<dyn std::error::Error>> {
    let root = BitMapBackend::new("basic_plot.png", (640, 480)).into_drawing_area();

    root.fill(&WHITE)?;
    let mut chart = ChartBuilder::on(&root)
        .caption("y=x^2", ("sans-serif", 50).into_font())
        .margin(5)
        .x_label_area_size(30)
        .y_label_area_size(30)
        .build_cartesian_2d(-2f32..2f32, -0.1f32..1f32)?;

    chart.configure_mesh().draw()?;

    chart
        .draw_series(LineSeries::new(
            (-100..=100).map(|x| x as f32 / 50.0).map(|x| (x, x * x)),
            &RED,
        ))?
        .label("y = x^2")
        .legend(|(x, y)| PathElement::new(vec![(x, y), (x + 20, y)], &RED));

    chart
        .configure_series_labels()
        .background_style(&WHITE.mix(0.8))
        .border_style(&BLACK)
        .draw()?;

    root.present()?;

    Ok(())
}

The cushy/kludgine based output is:

The plotters based output is:

The main issue is that text labels are wrongly aligned. Minor issues are that the line anti-aliasing doesn't look as good, and that the grid get aliased instead of being pixel perfect (but likely that is expected if the size of the drawing area doesn't allow for integer multiples of the grid size).
Since I'm not entirely sure if this a cushy or kludgine issue (or even further upstream?), I decided to report it on cushy. Do you generally prefer such issues being raised further upstream if possible?
Note that the lack of clipping is an upsteam issue in plotters https://github.com/plotters-rs/plotters/issues/622

Thank you for reporting this! I knew I had under-tested some of the plotters code, but some of that label drawing is pretty bad too.
The fuzziness is almost certainly due to me trying to automatically scale the plotters output based on DPI scaling. It seems like the more correct approach is going to be to let it be pixel-perfect rendering, and require that the plotters-integrator worry about dpi scaling themselves.
As for where to report the issue, I'm happy with most issues being reported on this repository -- it's where most users might actually encounter a bug. I can always create a separate issue and link them if I think someone else might tackle it, but right now I'm usually the person to fix something in Kludgine!

Things are looking better! I can't seem to figure out how the labels are sized -- I put a lot of logging code in, and I notice plotters measures the chart caption, but not the labels. My picture shows two series because I was trying to see if that would cause it to measure the text... but it didn't.
The issues were not what I originally suspected. It was that to draw a pixel-perfect 1px wide line, the coordinates need to be offset because lyon generates a rectangle centered on the path coordinates. To ensure the 1px wide line isn't split across two lines with Kludgine's subpixel rendering support, the coordinates need to be offset by 1/2 a pixel, or more generalized, half of the stroke width.
Beyond that, the text drawing code didn't support anchoring or alignment or rotation. This plot doesn't rotate text, but in theory everything is handled correctly now -- don't hesitate to let me know if you run into other issues! If you test the main branch, be sure to use cargo update to get Kludgine's changes.

Actually I'm reopening this because I'd like to have you weigh in on what's happening with the labels, if you know more about how plotters works.

Thanks for the fix!

Actually I'm reopening this because I'd like to have you weigh in on what's happening with the labels, if you know more about how plotters works.

In my opinion, this looks pretty much what I would expect now, so closing the issue should be fine. In case anything else comes up I'll let you know. I also don't have much expertise with plotters, mainly just trying things out so far.

repo: khonsulabs/cushy


text:
Write to file failed

I am trying to embed an exe through vb in a document, but when the vb is run there is a 3004 runtime error  which says "Write to file failes". I also tried the test.vb that you provide, but I get the same error. I also get the same error when I run the vb as a standalone.

If the vbs is created from linux, then the runtime error occurs. I created the vbs from windows and everything is working fine.

It sounds like a write permission error on the linux OS.  What flavor of
linux were you using, what user were you logged into as, and lastly what
does ls -al show?  I've only tested the code on Kali, debian, and ubuntu in
a chmod 777 directory. I'll run some tests on my end to see if I can
replicate and correct the error.
On Sun, Jul 19, 2015 at 6:38 PM, Chondrokoukis Dimitrios <
notifications@github.com> wrote:

If the vbs is created from linux, then the runtime error occurs. I created
the vbs from windows and everything is working fine.
—
Reply to this email directly or view it on GitHub
https://github.com/khr0x40sh/MacroShop/issues/1#issuecomment-122711937.

I think I misunderstood your first comment.  Can you post both files (the vb generated in linux and the one from windows) somewhere so I can run a diff on them and see maybe it is an environment issue?  Thanks.

The Payload type I used in Veil was cs/meterpreter/rev_http
These are the parameters
COMPILE_TO_EXE = Y
LHOST=192.168.2.10
LPORT=4444
USE_ARYA=Y
The output file was payload.exe
Then I used the following command in Linux
python exeinvba.py --exe ./payload.exe --out payloadLinux.vbs --dest "C:\payloadLinux.exe"
and the following command in Windows to create the respective files.
python exeinvba.py --exe ./payload.exe --out payloadWindows.vbs --dest "C:\payloadWindows.exe"
When I run payloadLinux.vbs there is a 3004 runtime error which says "Write to file failes". The payloadWindows.vbs runs successfully.
The Linux machine runs the latest version of Kali Linux 32bit with the latest updates from the official repo.
The Windows machine runs Windows XP 32bit with the latest updates.
Here is a link to download the generated files.
https://www.dropbox.com/s/mnrojz3axofneo8/files.zip?dl=0

It appears the linux vba does not escape the backslash properly in the
destination name.  Also, diff reports every line as different, so I am
thinking an environmental newline issue may be present. Thanks for your
help, I should have a fix for this soon.
On Tue, Jul 21, 2015 at 7:24 PM, Chondrokoukis Dimitrios <
notifications@github.com> wrote:

The Payload type I used in Veil was cs/meterpreter/rev_http
These are the parameters
COMPILE_TO_EXE = Y
LHOST=192.168.2.10
LPORT=4444
USE_ARYA=Y
The output file was payload.exe
Then I used the following command in Linux
python exeinvba.py --exe ./payload.exe --out payloadLinux.vbs --dest
"C:\payloadLinux.exe"
and the following command in Windows to create the respective files.
python exeinvba.py --exe ./payload.exe --out payloadWindows.vbs --dest
"C:\payloadWindows.exe"
When I run payloadLinux.vbs there is a 3004 runtime error which says
"Write to file failes". The payloadWindows.vbs runs successfully.
The Linux machine runs the latest version of Kali Linux 32bit with the
latest updates from the official repo.
The Windows machine runs Windows XP 32bit with the latest updates.
Here is a link to download the generated files.
https://www.dropbox.com/s/mnrojz3axofneo8/files.zip?dl=0
—
Reply to this email directly or view it on GitHub
https://github.com/khr0x40sh/MacroShop/issues/1#issuecomment-123506510.

As long as you escape the backslash, i.e C:\payloadLinux.exe vice
C:\payloadLinux.exe, it works fine.  It looks like it is a pain in the rear
to get python to escape backslashes on a variable, so I'm just going to add
error checking to remind the user to escape all backslashes for now, and
work on a more elegant solution later.
On Wed, Jul 22, 2015 at 9:28 AM, khrash 41414141 khr0x40sh@gmail.com
wrote:

It appears the linux vba does not escape the backslash properly in the
destination name.  Also, diff reports every line as different, so I am
thinking an environmental newline issue may be present. Thanks for your
help, I should have a fix for this soon.
On Tue, Jul 21, 2015 at 7:24 PM, Chondrokoukis Dimitrios <
notifications@github.com> wrote:

The Payload type I used in Veil was cs/meterpreter/rev_http
These are the parameters
COMPILE_TO_EXE = Y
LHOST=192.168.2.10
LPORT=4444
USE_ARYA=Y
The output file was payload.exe
Then I used the following command in Linux
python exeinvba.py --exe ./payload.exe --out payloadLinux.vbs --dest
"C:\payloadLinux.exe"
and the following command in Windows to create the respective files.
python exeinvba.py --exe ./payload.exe --out payloadWindows.vbs --dest
"C:\payloadWindows.exe"
When I run payloadLinux.vbs there is a 3004 runtime error which says
"Write to file failes". The payloadWindows.vbs runs successfully.
The Linux machine runs the latest version of Kali Linux 32bit with the
latest updates from the official repo.
The Windows machine runs Windows XP 32bit with the latest updates.
Here is a link to download the generated files.
https://www.dropbox.com/s/mnrojz3axofneo8/files.zip?dl=0
—
Reply to this email directly or view it on GitHub
https://github.com/khr0x40sh/MacroShop/issues/1#issuecomment-123506510.

The bug label will be removed as the README clearly states escaping the backslashes for the destination variable.


text:
[KOGITO-4180] Setup different lock for BDD

https://issues.redhat.com/browse/KOGITO-4180
Many thanks for submitting your Pull Request :heart:!
Please make sure your PR meets the following requirements:

[x] You have read the contributors' guide
[x] Pull Request title is properly formatted: [KOGITO-XYZ] Subject
[x] Pull Request contains a link to the JIRA issue
[x] Pull Request contains a description of the issue
[ ] Pull Request does not include fixes for issues other than the main ticket
[ ] Your feature/bug fix has a unit test that verifies it
[x] You've tested the new feature/bug fix in an actual OpenShift cluster
[ ] You've added a RELEASE_NOTES.md entry regarding this change

test done:

test1 with kogito image test1
test1-2 with kogito image test1
test2 with kogito image test2

result

Logs =>
test1
Trying to acquire lock on [BDD tests on branch test1 and OCP API ****]
Resource [BDD tests on branch test1 and OCP API ****] did not exist. Created.
Lock acquired on [BDD tests on branch test1 and OCP API ****]

test1-2
[Pipeline] { (Run BDD tests)
[Pipeline] lock
Trying to acquire lock on [BDD tests on branch test1 and OCP API ****]
Found 0 available resource(s). Waiting for correct amount: 1.
[BDD tests on branch test1 and OCP API ****] is locked, waiting...

test2
Trying to acquire lock on [BDD tests on branch test2 and OCP API ****]
Resource [BDD tests on branch test2 and OCP API ****] did not exist. Created.
Lock acquired on [BDD tests on branch test2 and OCP API ****]

test done:

test1 with kogito image test1
test1-2 with kogito image test1
test2 with kogito image test2

result

Logs =>
test1
Trying to acquire lock on [BDD tests on branch test1 and OCP API ****]
Resource [BDD tests on branch test1 and OCP API ****] did not exist. Created.
Lock acquired on [BDD tests on branch test1 and OCP API ****]

test1-2
[Pipeline] { (Run BDD tests)
[Pipeline] lock
Trying to acquire lock on [BDD tests on branch test1 and OCP API ****]
Found 0 available resource(s). Waiting for correct amount: 1.
[BDD tests on branch test1 and OCP API ****] is locked, waiting...

test2
Trying to acquire lock on [BDD tests on branch test2 and OCP API ****]
Resource [BDD tests on branch test2 and OCP API ****] did not exist. Created.
Lock acquired on [BDD tests on branch test2 and OCP API ****]

Where are many commented lines, should it be there?

Where are many commented lines, should it be there?

oups ... corrected

oups ... corrected

authors: radtriste sutaakar

repo: kiegroup/kogito-cloud-operator


text:
[KOGITO-6773] Add support to dataInputSchema on generated OpenAPI files

(WIP)
Signed-off-by: Ricardo Zanini zanini@redhat.com
Many thanks for submitting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:

[ ] You have read the contributors guide
[ ] Your code is properly formatted according to this configuration
[ ] Pull Request title is properly formatted: KOGITO-XYZ Subject
[ ] Pull Request title contains the target branch if not targeting main: [0.9.x] KOGITO-XYZ Subject
[ ] Pull Request contains link to the JIRA issue
[ ] Pull Request contains link to any dependent or related Pull Request
[ ] Pull Request contains description of the issue
[ ] 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-runtimes job #1405 was: FAILURE
Possible explanation: Pipeline failure or project build failure
Test results:

PASSED: 2294
FAILED: 0

Those are the test failures: none
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/1405/display/redirect or see console log:

Console Logs
[2022-04-07T21:44:17.253Z] [INFO] Kogito :: Add-Ons :: Persistence :: PostgreSQL ..... SUCCESS [  6.866 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Add-Ons :: Persistence PostgreSQL :: Springboot SUCCESS [  0.160 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Spring Boot :: Starter (DEPRECATED!) ..... SUCCESS [  0.186 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Spring Boot :: Maven Archetype ........... SUCCESS [ 56.337 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Test Utilities :: Spring Boot ............ SUCCESS [  4.339 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Quarkus :: Parent ........................ SUCCESS [  0.021 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Quarkus :: BOM ........................... SUCCESS [  0.024 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Quarkus Extensions :: Parent ............. SUCCESS [  0.024 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Quarkus Extension SPI .................... SUCCESS [  0.462 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Quarkus Extension Common ................. SUCCESS [  0.024 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Quarkus Extension Common :: Runtime ...... SUCCESS [  1.371 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Quarkus Extension Common :: Deployment ... SUCCESS [  1.740 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Quarkus Rules Extension .................. SUCCESS [  0.026 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Quarkus Rules Extension :: Runtime ....... SUCCESS [  0.827 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Quarkus Rules Extension :: Deployment .... SUCCESS [  0.346 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Quarkus Rules Extension :: Integration Tests SUCCESS [ 25.808 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Quarkus Rules Extension :: Integration Tests (Hot Reload) SUCCESS [ 34.366 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Quarkus Rules Extension :: Integration Tests (KieSession API) SUCCESS [ 10.921 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Quarkus Decisions Extension .............. SUCCESS [  0.028 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Quarkus Decisions Extension :: Runtime ... SUCCESS [  0.406 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Quarkus Decisions Extension :: Deployment  SUCCESS [  0.371 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Quarkus Decisions Extension :: Integration Tests SUCCESS [ 40.316 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Quarkus Decicions Extension :: Integration Tests (Hot Reload) SUCCESS [ 26.004 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Quarkus Predictions Extension ............ SUCCESS [  0.025 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Quarkus Predictions Extension :: Runtime . SUCCESS [  0.510 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Quarkus Predictions Extension :: Deployment SUCCESS [  0.379 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Quarkus Predictions Extension :: Integration Tests SUCCESS [ 12.203 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Quarkus Processes Extension .............. SUCCESS [  0.023 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Quarkus Processes Extension :: Runtime ... SUCCESS [  1.167 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Quarkus Extension ........................ SUCCESS [  0.023 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Quarkus Extension :: Runtime ............. SUCCESS [  0.302 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Quarkus Processes Extension :: Deployment  SUCCESS [  3.613 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Quarkus Extension :: Deployment .......... SUCCESS [  0.166 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Quarkus Extension :: Integration Tests ... SUCCESS [ 13.595 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Quarkus Extension :: Integration Tests (Maven devmode) SUCCESS [ 58.849 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Quarkus Processes Extension :: Integration Tests SUCCESS [ 17.137 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Quarkus Processes Extension :: Integration Tests (Hot Reload) SUCCESS [01:16 min][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Add-Ons :: Quarkus ....................... SUCCESS [  0.023 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Rest Exception Handler :: Quarkus ........ SUCCESS [  1.734 s][2022-04-07T21:44:17.253Z] [INFO] Kogito Add-On Messaging - Parent ................... SUCCESS [  0.021 s][2022-04-07T21:44:17.253Z] [INFO] Kogito Add-On Messaging - Common ................... SUCCESS [ 11.128 s][2022-04-07T21:44:17.253Z] [INFO] Kogito Add-On Messaging ............................ SUCCESS [  0.356 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Quarkus Serverless Workflow Extension .... SUCCESS [  0.021 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Quarkus Serverless Workflow Extension :: Runtime SUCCESS [  1.390 s][2022-04-07T21:44:17.253Z] [INFO] Kogito Add-On Common - Parent ...................... SUCCESS [  0.023 s][2022-04-07T21:44:17.253Z] [INFO] Kogito Add-On Common - Deployment .................. SUCCESS [  1.214 s][2022-04-07T21:44:17.253Z] [INFO] Kogito Add-On Messaging - Deployment ............... SUCCESS [  0.549 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Quarkus Workflows Extension :: Deployment  SUCCESS [  0.616 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Test Utilities :: Quarkus ................ SUCCESS [  5.026 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Quarkus Workflows Extension :: Integration Tests SUCCESS [01:07 min][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Quarkus Test List ........................ SUCCESS [  0.966 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Add-Ons :: Quarkus :: Events ............. SUCCESS [  0.021 s][2022-04-07T21:44:17.253Z] [INFO] Kogito Add-On Events Decisions - Parent ............ SUCCESS [  0.022 s][2022-04-07T21:44:17.253Z] [INFO] Kogito Add-On Events Decisions ..................... SUCCESS [  0.396 s][2022-04-07T21:44:17.253Z] [INFO] Kogito Add-On Events Decisions - Deployment ........ SUCCESS [  0.444 s][2022-04-07T21:44:17.253Z] [INFO] Kogito Add-On Events Predictions - Parent .......... SUCCESS [  0.030 s][2022-04-07T21:44:17.253Z] [INFO] Kogito Add-On Events Predictions ................... SUCCESS [  0.382 s][2022-04-07T21:44:17.253Z] [INFO] Kogito Add-On Events Predictions - Deployment ...... SUCCESS [  0.433 s][2022-04-07T21:44:17.253Z] [INFO] Kogito Add-On Events Rules - Parent ................ SUCCESS [  0.022 s][2022-04-07T21:44:17.253Z] [INFO] Kogito :: Add-Ons :: Events :: Event-Driven Rules :: Quarkus SUCCESS [  0.321 s][2022-04-07T21:44:17.253Z] [INFO] Kogito Add-On Events Rules - Deployment ............ SUCCESS [  0.400 s][2022-04-07T21:44:17.253Z] [INFO] Kogito Add-On Events Process - Parent .............. SUCCESS [  0.025 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Events Process ....................... SUCCESS [  0.372 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Events Process - Deployment .......... SUCCESS [  0.303 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Events MongoDB - Parent .............. SUCCESS [  0.022 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Events MongoDB ....................... SUCCESS [  8.350 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Events MongoDB - Deployment .......... SUCCESS [  0.367 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Messaging - Integration Tests ........ SUCCESS [ 24.088 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Monitoring - Parent .................. SUCCESS [  0.024 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Monitoring Core ...................... SUCCESS [  3.290 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Monitoring Prometheus - Parent ....... SUCCESS [  0.023 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Monitoring Prometheus ................ SUCCESS [  0.337 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Monitoring Prometheus - Deployment ... SUCCESS [  0.430 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Monitoring Elastic - Parent .......... SUCCESS [  0.023 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Monitoring Elastic ................... SUCCESS [  0.401 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Monitoring Elastic - Deployment ...... SUCCESS [  0.359 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Explainability - Parent .............. SUCCESS [  0.023 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Explainability ....................... SUCCESS [  8.566 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Explainability - Deployment .......... SUCCESS [  0.378 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-Ons Quarkus Jobs Parent ................. SUCCESS [  0.033 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-Ons Quarkus Jobs Common - Parent ........ SUCCESS [  0.026 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-Ons Quarkus - Rest Callback ............. SUCCESS [  2.366 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-Ons Quarkus Jobs Management - Parent .... SUCCESS [  0.037 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-Ons Quarkus Jobs - Management ........... SUCCESS [  3.062 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-Ons Quarkus Jobs Management - Deployment  SUCCESS [  0.369 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-Ons Quarkus Jobs Messaging - Parent ..... SUCCESS [  0.024 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-Ons Quarkus Jobs - Messaging ............ SUCCESS [  3.570 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-Ons Quarkus Jobs Messaging - Deployment . SUCCESS [  0.340 s][2022-04-07T21:44:17.511Z] [INFO] Kogito :: Add-Ons :: Knative :: Parent ............. SUCCESS [  0.023 s][2022-04-07T21:44:17.511Z] [INFO] Kogito :: Add-Ons :: Knative :: Eventing ........... SUCCESS [  2.026 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Knative - Parent ..................... SUCCESS [  0.020 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Knative Eventing - Parent ............ SUCCESS [  0.020 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Knative Eventing ..................... SUCCESS [  1.595 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Knative Eventing - Deployment ........ SUCCESS [  3.619 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Knative Eventing - Parent ............ SUCCESS [  0.021 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Kubernetes ........................... SUCCESS [ 11.036 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Kubernetes - Deployment .............. SUCCESS [  8.324 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Mail - Parent ........................ SUCCESS [  0.021 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Mail ................................. SUCCESS [ 11.752 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Mail - Deployment .................... SUCCESS [  0.341 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Quarkus Persistence .................. SUCCESS [  0.023 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Persistence Infinispan - Parent ...... SUCCESS [  0.022 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Persistence Infinispan ............... SUCCESS [  2.353 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Persistence Infinispan - Deployment .. SUCCESS [  0.457 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Persistence Infinispan Health Check .. SUCCESS [ 48.185 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Persistence Kafka Streams - Parent ... SUCCESS [  0.022 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Persistence Kafka Streams ............ SUCCESS [ 18.071 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Persistence Kafka Streams - Deployment SUCCESS [  0.410 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Persistence FileSystem - Parent ...... SUCCESS [  0.024 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Persistence FileSystem ............... SUCCESS [  0.408 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Persistence FileSystem - Deployment .. SUCCESS [  0.322 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Persistence JDBC - Parent ............ SUCCESS [  0.021 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Persistence JDBC ..................... SUCCESS [  0.355 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Persistence JDBC - Deployment ........ SUCCESS [  0.402 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Persistence MongoDB - Parent ......... SUCCESS [  0.023 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Persistence MongoDB .................. SUCCESS [  0.711 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Persistence MongoDB - Deployment ..... SUCCESS [  0.442 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Persistence PostgreSQL - Parent ...... SUCCESS [  0.031 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Persistence PostgreSQL ............... SUCCESS [  1.078 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Persistence PostgreSQL - Deployment .. SUCCESS [  0.422 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Task Notification - Parent ........... SUCCESS [  0.020 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Task Notification .................... SUCCESS [  0.306 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Task Notification - Deployment ....... SUCCESS [  0.329 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Tracing Decision - Parent ............ SUCCESS [  0.025 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Tracing Decision ..................... SUCCESS [  4.472 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Tracing Decision - Deployment ........ SUCCESS [  0.808 s][2022-04-07T21:44:17.511Z] [INFO] Integration tests for the Tracing Decision Add-On (Quarkus) SUCCESS [ 37.627 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Process SVG - Parent ................. SUCCESS [  0.021 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Process SVG .......................... SUCCESS [  3.266 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Process SVG - Deployment ............. SUCCESS [  0.357 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Process Management - Parent .......... SUCCESS [  0.026 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Process Management ................... SUCCESS [  2.773 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Process Management - Deployment ...... SUCCESS [  0.324 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Task Management - Parent ............. SUCCESS [  0.021 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Task Management ...................... SUCCESS [  1.078 s][2022-04-07T21:44:17.511Z] [INFO] Kogito Add-On Task Management - Deployment ......... SUCCESS [  0.331 s][2022-04-07T21:44:17.511Z] [INFO] Kogito :: Add-Ons :: Predictions ................... SUCCESS [  0.033 s][2022-04-07T21:44:17.511Z] [INFO] Kogito :: Add-Ons :: Predictions :: API ............ SUCCESS [  2.020 s][2022-04-07T21:44:17.511Z] [INFO] Kogito :: Add-Ons :: Predictions :: SMILE .......... SUCCESS [  2.198 s][2022-04-07T21:44:17.511Z] [INFO] Kogito :: DB Scripts Collection .................... SUCCESS [  0.208 s][2022-04-07T21:44:17.511Z] [INFO] Kogito :: Add-Ons :: Deprecated .................... SUCCESS [  0.020 s][2022-04-07T21:44:17.511Z] [INFO] Kogito :: Add-Ons :: Deprecated :: Event Driven Decisions Common SUCCESS [  0.044 s][2022-04-07T21:44:17.511Z] [INFO] Kogito :: Add-Ons :: Deprecated :: Event Driven Decisions Quarkus SUCCESS [  0.947 s][2022-04-07T21:44:17.511Z] [INFO] Kogito :: Add-Ons :: Deprecated :: Event Driven Decisions Spring Boot SUCCESS [  0.483 s][2022-04-07T21:44:17.511Z] [INFO] Kogito :: Add-Ons :: Deprecated :: Monitoring Common SUCCESS [  0.043 s][2022-04-07T21:44:17.511Z] [INFO] Kogito :: Add-Ons :: Deprecated :: Monitoring Core Quarkus SUCCESS [  0.779 s][2022-04-07T21:44:17.511Z] [INFO] Kogito :: Add-Ons :: Deprecated :: Monitoring Core Spring Boot SUCCESS [  0.142 s][2022-04-07T21:44:17.511Z] [INFO] Kogito :: Add-Ons :: Deprecated :: Monitoring Prometheus Common SUCCESS [  0.046 s][2022-04-07T21:44:17.511Z] [INFO] Kogito :: Add-Ons :: Deprecated :: Monitoring Prometheus Quarkus SUCCESS [  0.197 s][2022-04-07T21:44:17.511Z] [INFO] Kogito :: Add-Ons :: Deprecated :: Monitoring Prometheus Spring Boot SUCCESS [  0.049 s][2022-04-07T21:44:17.511Z] [INFO] Kogito :: Add-Ons :: Deprecated :: CloudEvents ..... SUCCESS [  0.040 s][2022-04-07T21:44:17.511Z] [INFO] Kogito :: Add-Ons :: Deprecated :: CloudEvents Common SUCCESS [  0.034 s][2022-04-07T21:44:17.511Z] [INFO] Kogito :: Add-Ons :: Deprecated :: CloudEvents :: Quarkus SUCCESS [  0.125 s][2022-04-07T21:44:17.511Z] [INFO] Kogito :: Add-Ons :: Deprecated :: CloudEvents Quarkus SUCCESS [  0.141 s][2022-04-07T21:44:17.511Z] [INFO] Kogito :: Add-Ons :: Deprecated :: CloudEvents :: Springboot SUCCESS [  0.106 s][2022-04-07T21:44:17.512Z] [INFO] Kogito :: Add-Ons :: Deprecated :: CloudEvents Spring Boot SUCCESS [  0.109 s][2022-04-07T21:44:17.512Z] [INFO] Kogito :: Add-Ons :: Deprecated :: CloudEvents :: Multi channel :: Quarkus SUCCESS [  0.140 s][2022-04-07T21:44:17.512Z] [INFO] Kogito :: Add-Ons :: Deprecated :: Events :: Smallrye Messaging SUCCESS [  0.129 s][2022-04-07T21:44:17.512Z] [INFO] Kogito :: Add-Ons :: Events :: SprintBoot :: Kafka . SUCCESS [  0.077 s][2022-04-07T21:44:17.512Z] [INFO] Kogito :: Add-Ons :: Deprecated :: Knative Eventing  SUCCESS [  0.220 s][2022-04-07T21:44:17.512Z] [INFO] Kogito :: Integration Tests ........................ SUCCESS [  0.020 s][2022-04-07T21:44:17.512Z] [INFO] Kogito :: Integration Tests :: Quarkus :: Rules .... SUCCESS [ 12.348 s][2022-04-07T21:44:17.512Z] [INFO] Kogito :: Integration Tests :: Quarkus :: Decisions  SUCCESS [ 14.372 s][2022-04-07T21:44:17.512Z] [INFO] Kogito :: Integration Tests :: Quarkus :: Predictions SUCCESS [ 13.298 s][2022-04-07T21:44:17.512Z] [INFO] Kogito :: Integration Tests :: Quarkus :: RESTEasy Classic SUCCESS [ 11.264 s][2022-04-07T21:44:17.512Z] [INFO] Kogito :: Integration Tests :: Quarkus :: RESTEasy Reactive SUCCESS [ 11.505 s][2022-04-07T21:44:17.512Z] [INFO] Kogito :: Integration Tests :: Spring Boot ......... SUCCESS [02:09 min][2022-04-07T21:44:17.512Z] [INFO] Kogito :: Integration Tests :: Maven Plugin ........ SUCCESS [ 26.029 s][2022-04-07T21:44:17.512Z] [INFO] Kogito :: Integration Tests :: Quarkus :: Without REST SUCCESS [ 27.251 s][2022-04-07T21:44:17.512Z] [INFO] Kogito :: Integration Tests :: Quarkus :: Processes  SUCCESS [ 26.579 s][2022-04-07T21:44:17.512Z] [INFO] Kogito :: Integration Tests :: Quarkus :: Processes :: Persistence SUCCESS [  0.027 s][2022-04-07T21:44:17.512Z] [INFO] Kogito :: Integration Tests :: Processes :: Persistence :: Common SUCCESS [  1.598 s][2022-04-07T21:44:17.512Z] [INFO] Kogito :: Integration Tests :: Quarkus :: Processes :: Persistence :: PostgreSQL SUCCESS [ 19.654 s][2022-04-07T21:44:17.512Z] [INFO] Kogito :: Integration Tests :: Quarkus :: Processes :: Persistence :: Infinispan SUCCESS [ 22.774 s][2022-04-07T21:44:17.512Z] [INFO] Kogito :: Integration Tests :: Quarkus :: Processes :: Persistence :: MongoDB SUCCESS [ 19.704 s][2022-04-07T21:44:17.512Z] [INFO] Kogito :: Integration Tests :: Quarkus :: Processes :: Persistence :: Kafka SUCCESS [ 26.500 s][2022-04-07T21:44:17.512Z] [INFO] Kogito :: Integration Tests :: Quarkus :: Processes :: Persistence :: JDBC SUCCESS [ 20.056 s][2022-04-07T21:44:17.512Z] [INFO] Kogito :: Integration Tests :: Quarkus :: Processes :: Persistence :: File System SUCCESS [ 15.953 s][2022-04-07T21:44:17.512Z] [INFO] Kogito :: Integration Tests :: Quarkus :: Gradle ... SUCCESS [01:09 min][2022-04-07T21:44:17.512Z] [INFO] Kogito :: Integration Tests :: Quarkus :: OpenAPI Client Codegen SUCCESS [ 14.453 s][2022-04-07T21:44:17.512Z] [INFO] ------------------------------------------------------------------------[2022-04-07T21:44:17.512Z] [INFO] BUILD FAILURE[2022-04-07T21:44:17.512Z] [INFO] ------------------------------------------------------------------------[2022-04-07T21:44:17.512Z] [INFO] Total time:  28:50 min[2022-04-07T21:44:17.512Z] [INFO] Finished at: 2022-04-07T17:44:16-04:00[2022-04-07T21:44:17.512Z] [INFO] ------------------------------------------------------------------------[2022-04-07T21:44:17.512Z] [ERROR] Failed to execute goal net.revelc.code:impsort-maven-plugin:1.5.0:check (default) on project kogito-codegen-processes-integration-tests: Imports are not sorted in /home/jenkins/workspace/KIE/kogito/main/pullrequest/kogito-runtimes.tests.kogito-runtimes/bc/kiegroup_kogito_runtimes/kogito-runtimes/kogito-codegen-modules/kogito-codegen-processes-integration-tests/src/test/java/org/kie/kogito/codegen/process/ProcessGenerationIT.java -> [Help 1][2022-04-07T21:44:17.512Z] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal net.revelc.code:impsort-maven-plugin:1.5.0:check (default) on project kogito-codegen-processes-integration-tests: Imports are not sorted in /home/jenkins/workspace/KIE/kogito/main/pullrequest/kogito-runtimes.tests.kogito-runtimes/bc/kiegroup_kogito_runtimes/kogito-runtimes/kogito-codegen-modules/kogito-codegen-processes-integration-tests/src/test/java/org/kie/kogito/codegen/process/ProcessGenerationIT.java[2022-04-07T21:44:17.512Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)[2022-04-07T21:44:17.512Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)[2022-04-07T21:44:17.512Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)[2022-04-07T21:44:17.512Z]     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)[2022-04-07T21:44:17.512Z]     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)[2022-04-07T21:44:17.512Z]     at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)[2022-04-07T21:44:17.512Z]     at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)[2022-04-07T21:44:17.512Z]     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)[2022-04-07T21:44:17.512Z]     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)[2022-04-07T21:44:17.512Z]     at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)[2022-04-07T21:44:17.512Z]     at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)[2022-04-07T21:44:17.512Z]     at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)[2022-04-07T21:44:17.512Z]     at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)[2022-04-07T21:44:17.512Z]     at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)[2022-04-07T21:44:17.512Z]     at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)[2022-04-07T21:44:17.512Z]     at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)[2022-04-07T21:44:17.512Z]     at java.lang.reflect.Method.invoke (Method.java:566)[2022-04-07T21:44:17.512Z]     at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)[2022-04-07T21:44:17.512Z]     at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)[2022-04-07T21:44:17.512Z]     at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)[2022-04-07T21:44:17.512Z]     at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)[2022-04-07T21:44:17.512Z] Caused by: org.apache.maven.plugin.MojoFailureException: Imports are not sorted in /home/jenkins/workspace/KIE/kogito/main/pullrequest/kogito-runtimes.tests.kogito-runtimes/bc/kiegroup_kogito_runtimes/kogito-runtimes/kogito-codegen-modules/kogito-codegen-processes-integration-tests/src/test/java/org/kie/kogito/codegen/process/ProcessGenerationIT.java[2022-04-07T21:44:17.512Z]     at net.revelc.code.impsort.maven.plugin.AbstractImpSortMojo.fail (AbstractImpSortMojo.java:308)[2022-04-07T21:44:17.512Z]     at net.revelc.code.impsort.maven.plugin.AbstractImpSortMojo.fail (AbstractImpSortMojo.java:304)[2022-04-07T21:44:17.512Z]     at net.revelc.code.impsort.maven.plugin.CheckMojo.processResult (CheckMojo.java:33)[2022-04-07T21:44:17.512Z]     at net.revelc.code.impsort.maven.plugin.AbstractImpSortMojo.lambda$execute$3 (AbstractImpSortMojo.java:249)[2022-04-07T21:44:17.512Z]     at java.util.stream.ReferencePipeline$3$1.accept (ReferencePipeline.java:195)[2022-04-07T21:44:17.512Z]     at java.util.stream.ReferencePipeline$3$1.accept (ReferencePipeline.java:195)[2022-04-07T21:44:17.512Z]     at java.util.stream.ForEachOps$ForEachOp$OfRef.accept (ForEachOps.java:183)[2022-04-07T21:44:17.512Z]     at java.util.stream.ReferencePipeline$3$1.accept (ReferencePipeline.java:195)[2022-04-07T21:44:17.512Z]     at java.util.Spliterators$ArraySpliterator.forEachRemaining (Spliterators.java:948)[2022-04-07T21:44:17.512Z]     at java.util.stream.AbstractPipeline.copyInto (AbstractPipeline.java:484)[2022-04-07T21:44:17.512Z]     at java.util.stream.AbstractPipeline.wrapAndCopyInto (AbstractPipeline.java:474)[2022-04-07T21:44:17.512Z]     at java.util.stream.ForEachOps$ForEachOp.evaluateSequential (ForEachOps.java:150)[2022-04-07T21:44:17.512Z]     at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential (ForEachOps.java:173)[2022-04-07T21:44:17.512Z]     at java.util.stream.AbstractPipeline.evaluate (AbstractPipeline.java:234)[2022-04-07T21:44:17.512Z]     at java.util.stream.ReferencePipeline.forEach (ReferencePipeline.java:497)[2022-04-07T21:44:17.512Z]     at java.util.stream.ReferencePipeline$7$1.accept (ReferencePipeline.java:274)[2022-04-07T21:44:17.512Z]     at java.util.Spliterators$ArraySpliterator.forEachRemaining (Spliterators.java:948)[2022-04-07T21:44:17.512Z]     at java.util.stream.AbstractPipeline.copyInto (AbstractPipeline.java:484)[2022-04-07T21:44:17.512Z]     at java.util.stream.AbstractPipeline.wrapAndCopyInto (AbstractPipeline.java:474)[2022-04-07T21:44:17.512Z]     at java.util.stream.ReduceOps$ReduceTask.doLeaf (ReduceOps.java:952)[2022-04-07T21:44:17.512Z]     at java.util.stream.ReduceOps$ReduceTask.doLeaf (ReduceOps.java:926)[2022-04-07T21:44:17.512Z]     at java.util.stream.AbstractTask.compute (AbstractTask.java:327)[2022-04-07T21:44:17.512Z]     at java.util.concurrent.CountedCompleter.exec (CountedCompleter.java:746)[2022-04-07T21:44:17.512Z]     at java.util.concurrent.ForkJoinTask.doExec (ForkJoinTask.java:290)[2022-04-07T21:44:17.512Z]     at java.util.concurrent.ForkJoinTask.doInvoke (ForkJoinTask.java:408)[2022-04-07T21:44:17.512Z]     at java.util.concurrent.ForkJoinTask.invoke (ForkJoinTask.java:736)[2022-04-07T21:44:17.512Z]     at java.util.stream.ReduceOps$ReduceOp.evaluateParallel (ReduceOps.java:919)[2022-04-07T21:44:17.512Z]     at java.util.stream.AbstractPipeline.evaluate (AbstractPipeline.java:233)[2022-04-07T21:44:17.512Z]     at java.util.stream.ReferencePipeline.reduce (ReferencePipeline.java:558)[2022-04-07T21:44:17.512Z]     at net.revelc.code.impsort.maven.plugin.AbstractImpSortMojo.execute (AbstractImpSortMojo.java:265)[2022-04-07T21:44:17.512Z]     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)[2022-04-07T21:44:17.512Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)[2022-04-07T21:44:17.512Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)[2022-04-07T21:44:17.512Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)[2022-04-07T21:44:17.512Z]     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)[2022-04-07T21:44:17.512Z]     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)[2022-04-07T21:44:17.512Z]     at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)[2022-04-07T21:44:17.512Z]     at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)[2022-04-07T21:44:17.512Z]     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)[2022-04-07T21:44:17.512Z]     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)[2022-04-07T21:44:17.512Z]     at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)[2022-04-07T21:44:17.512Z]     at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)[2022-04-07T21:44:17.512Z]     at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)[2022-04-07T21:44:17.512Z]     at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)[2022-04-07T21:44:17.512Z]     at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)[2022-04-07T21:44:17.512Z]     at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)[2022-04-07T21:44:17.512Z]     at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)[2022-04-07T21:44:17.512Z]     at java.lang.reflect.Method.invoke (Method.java:566)[2022-04-07T21:44:17.512Z]     at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)[2022-04-07T21:44:17.512Z]     at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)[2022-04-07T21:44:17.512Z]     at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)[2022-04-07T21:44:17.512Z]     at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)[2022-04-07T21:44:17.512Z] [ERROR] [2022-04-07T21:44:17.512Z] [ERROR] Re-run Maven using the -X switch to enable full debug logging.[2022-04-07T21:44:17.512Z] [ERROR] [2022-04-07T21:44:17.512Z] [ERROR] For more information about the errors and possible solutions, please read the following articles:[2022-04-07T21:44:17.512Z] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException[2022-04-07T21:44:17.512Z] [ERROR] [2022-04-07T21:44:17.512Z] [ERROR] After correcting the problems, you can resume the build with the command[2022-04-07T21:44:17.512Z] [ERROR]   mvn  -rf :kogito-codegen-processes-integration-tests[2022-04-07T21:44:17.512Z] ::error title= [kiegroup/kogito-runtimes] [Execution ERROR]::mvn -f kogito-runtimes/pom.xml clean install -Dvalidate-formatting -Dquarkus.bootstrap.effective-model-builder  -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  -Prun-code-coverage  -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn -B -s /home/jenkins/workspace/KIE/kogito/main/pullrequest/kogito-runtimes.tests.kogito-runtimes@tmp/config9052684376321678124tmp -Dmaven.wagon.http.ssl.insecure=true -Dmaven.test.failure.ignore=true[2022-04-07T21:44:17.512Z] [INFO]  Archive artifact won't be executed[2022-04-07T21:44:17.512Z] ::group::[Pull Request Flow] Execution Summary...[2022-04-07T21:44:17.512Z] [INFO]  ----------------------------------------------[2022-04-07T21:44:17.512Z] [INFO]  [kiegroup/drools]. Execution Result: ok. Time: 2m 17.6s (137620 ms)[2022-04-07T21:44:17.512Z] [INFO]  [kiegroup/kogito-runtimes]. Execution Result: error. Time: 28m 51.7s (1731761 ms)[2022-04-07T21:44:17.512Z] [INFO]  ----------------------------------------------[2022-04-07T21:44:17.512Z] ::endgroup::[2022-04-07T21:44:17.768Z] [ERROR]  [kiegroup/kogito-runtimes] error executing command: 'mvn -f kogito-runtimes/pom.xml clean install -Dvalidate-formatting -Dquarkus.bootstrap.effective-model-builder  -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  -Prun-code-coverage  -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn -B -s /home/jenkins/workspace/KIE/kogito/main/pullrequest/kogito-runtimes.tests.kogito-runtimes@tmp/config9052684376321678124tmp -Dmaven.wagon.http.ssl.insecure=true -Dmaven.test.failure.ignore=true'. Message: Error: The process '/opt/tools/apache-maven-3.8.1/bin/mvn' failed with exit code 1[2022-04-07T21:44:17.768Z] [ERROR]  Command executions have failed, please review latest execution Error: [kiegroup/kogito-runtimes] error executing command: 'mvn -f kogito-runtimes/pom.xml clean install -Dvalidate-formatting -Dquarkus.bootstrap.effective-model-builder  -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  -Prun-code-coverage  -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn -B -s /home/jenkins/workspace/KIE/kogito/main/pullrequest/kogito-runtimes.tests.kogito-runtimes@tmp/config9052684376321678124tmp -Dmaven.wagon.http.ssl.insecure=true -Dmaven.test.failure.ignore=true'. Message: Error: The process '/opt/tools/apache-maven-3.8.1/bin/mvn' failed with exit code 1[Pipeline] }[Pipeline] // withCredentials[Pipeline] }[2022-04-07T21:44:17.829Z] Deleting 1 temporary files[Pipeline] // configFileProvider[Pipeline] }[Pipeline] // scriptPost stage[Pipeline] junit[2022-04-07T21:44:17.924Z] Recording test results[2022-04-07T21:44:20.218Z] [Checks API] No suitable checks publisher found.[Pipeline] archiveArtifacts[2022-04-07T21:44:20.258Z] Archiving artifacts[Pipeline] script[Pipeline] {[Pipeline] sh[2022-04-07T21:44:22.912Z] + rm -rf console.log[Pipeline] sh[2022-04-07T21:44:23.218Z] + wget --no-check-certificate -qO - 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/1405/consoleText[2022-04-07T21:44:23.218Z] + tail -n 300

repo: kiegroup/kogito-runtimes


text:
feat: add ability to select kingdoms for easier viewing

resolves #25

@kieranmillar here is what I was thinking for the hover/selection of a kingdom.
I've used treasure yellow, but feel free to suggest another colour or any other changes :)

repo: kieranmillar/extra-recommended-sets


text:
[feature request] better performance and return function name

The decode_function takes my laptop 10 seconds to decode 10000 transaction inputs. It is considered slow comparing to millions of transactions on uniswap a day. And the function name that the transaction invokes is usually important. So I recast the decoder into a class as follows:
class InputDecoder():
    def __init__(self, abi):
        self.selector_to_type_def = {}

        for type_def in abi:
            if type_def["type"] == "function":
                selector = function_abi_to_4byte_selector(type_def)
                self.selector_to_type_def[selector] = type_def

    def decode(self, tx_input):
        tx_input = hex_to_bytes(tx_input)
        selector, args = tx_input[:4], tx_input[4:]
        if selector not in self.selector_to_type_def:
            raise InputDataError("Specified method not found in ABI")

        # type_def = selector_to_type_def[selector]["inputs"]
        func_abi = self.selector_to_type_def[selector]
        types, names = get_types_names(func_abi['inputs'])

        values = decode_abi(types, args)
        # return [(t, n, v) for t, n, v in zip(types, names, values)]
        return func_abi['name'], dict(zip(names, values))

This takes 0.6s for decoding 10000 transactions. It's fine.
Btw, the contract.decode_function_input of web3py takes about 20s to decode 10000 transactions. It's unbearable.

Thanks for pointing out redundant call of function_abi_to_4byte_selector 😃

authors: faustoid kigawas


text:
Cannot open MenuItem on click

I cannot open my MenuItem "File" with my mouse but I can with a keyboard
Code:
<Window [...]
        Classes="NakedWindow Blurred">
    <suki:DesktopPage Title="OrigamiEditor"
                      MenuVisibility="True">
        <suki:DesktopPage.LogoContent>
            <Image Source="avares://OrigamiEditor/assets/logo.ico" MaxHeight="16"/>
        </suki:DesktopPage.LogoContent>
        <suki:DesktopPage.MenuItems>
                <MenuItem Header="File">
                    <MenuItem Header="Test" Foreground="{DynamicResource SukiText}" />
                    <MenuItem Header="Test" Foreground="{DynamicResource SukiText}" />
                    <MenuItem Header="Test" Foreground="{DynamicResource SukiText}" />
                    <MenuItem Header="Test" Foreground="{DynamicResource SukiText}" />
                </MenuItem>
                <MenuItem Header="Edit" Foreground="{DynamicResource SukiText}" />
                <MenuItem Header="Help" Foreground="{DynamicResource SukiText}" />
        </suki:DesktopPage.MenuItems>
    </suki:DesktopPage>
</Window>

Actual behavior:

Expected behavior:

Definitely not normal, the vertical alignment of the buttons on the right too. I guess it's the HitTest when adding Glassmorphism that became false.
I will fix that this week.

Fixed in Nuget 5.2.2

repo: kikipoulet/SukiUI


text:
feat: 🎸 add notebook that allows iterating on plugins

✅ Closes: DATA-784

Draft because I did not add yet the actual upload of plugins, doing that now

repo: kili-technology/kili-python-sdk


text:
Add sensitive fields

cc @pierre

Once the depending PR: https://github.com/killbill/killbill-plugin-framework-ruby/pull/64/files is merged, I'll update gem file

FYI, our CI sandbox is FUBAR'ed. I've reached out to PayPal for help.

@daliwei Can you confirm the integration tests are passing on your sandbox?
I've setup a new one as suggested by PayPal support, but the HTML seems to be different.
From the Selenium logs at https://circleci.com/gh/killbill/killbill-paypal-express-plugin/12 ('Container selenium/standalone-firefox:3.1.0' tab):
17:42:51.777 INFO - Executing: [switch to frame: injectedUl])
17:42:51.806 WARN - Exception thrown
org.openqa.selenium.NoSuchFrameException: No frame element found by name or id injectedUl

authors: daliwei pierre

repo: killbill/killbill-paypal-express-plugin


text:
fix bug where setDefaultPaymentMethod changing isDefault of payment methods for other accounts

The test would fail before the fix

See 996490c9c76a35579b3d2c7ccf2ff2b27879a446.

authors: almalki pierre

repo: killbill/killbill-plugin-framework-java