Russia.TV site suddenly unavailable to d/l video

Hello author and contributors!
I have never met the problems with http://russia.tv to get videos from this site, but now I see the problem. Here is the log, please inspect the thing and reply back - is it youtube-dl problem or site problem, Thanks !
C:\temp>youtube-dl.exe -v http://russia.tv/video/show/brand_id/5402/episode_id/986443/video_id/998716/
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'-v', u'http://russia.tv/video/show/brand_id/5402/episode_id/986443/video_id/998716/']
[debug] Encodings: locale cp1251, fs mbcs, out cp866, pref cp1251
[debug] youtube-dl version 2015.11.24
[debug] Python version 2.7.10 - Windows-7-6.1.7601-SP1
[debug] exe versions: ffmpeg N-76741-g8eadabf
[debug] Proxy map: {}
[generic] 998716: Requesting header
WARNING: Falling back on generic information extractor.
[generic] 998716: Downloading webpage
[generic] 998716: Extracting information
[RUTV] 796047: Downloading JSON
[RUTV] 796047: Downloading m3u8 information
ERROR: Failed to download m3u8 information: '' (caused by BadStatusLine("''",));
please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
File "youtube_dl\extractor\common.pyo", line 329, in _request_webpage
File "youtube_dl\YoutubeDL.pyo", line 1878, in urlopen
File "urllib2.pyo", line 431, in open
File "urllib2.pyo", line 449, in _open
File "urllib2.pyo", line 409, in _call_chain
File "youtube_dl\utils.pyo", line 691, in http_open
File "urllib2.pyo", line 1200, in do_open
File "httplib.pyo", line 1132, in getresponse
File "httplib.pyo", line 453, in begin
File "httplib.pyo", line 417, in _read_status
In other hand I am able to DL (almost?) all videos from the same site:
C:\temp>youtube-dl.exe http://russia.tv/video/show/brand_id/5402/episode_id/1253957/video_id/1412995/
[generic] 1412995: Requesting header
WARNING: Falling back on generic information extractor.
[generic] 1412995: Downloading webpage
[generic] 1412995: Extracting information
[RUTV] 1453641: Downloading JSON
[RUTV] 1453641: Downloading m3u8 information
[download] Destination: Вести. Эфир от 26.11.2015 (17_00)-1453641.mp4
ffmpeg version N-76741-g8eadabf Copyright (c) 2000-2015 the FFmpeg developers
built with gcc 5.2.0 (GCC)
configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libdcadec --enable-libfreetype --enable-libgme --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-libzimg --enable-lzma --enable-decklink --enable-zlib
libavutil      55.  7.100 / 55.  7.100
libavcodec     57. 15.100 / 57. 15.100
libavformat    57. 16.100 / 57. 16.100
libavdevice    57.  0.100 / 57.  0.100
libavfilter     6. 15.100 /  6. 15.100
libswscale      4.  0.100 /  4.  0.100
libswresample   2.  0.101 /  2.  0.101
libpostproc    54.  0.100 / 54.  0.100
Input #0, hls,applehttp, from 'http://cdn.v.rtr-vesti.ru/_cdn_auth/secure/v/vh/vod_hls/definst/smil:vh/smil/001/412/995_d20151126184511.smil/chunklist_w423434632_b1800000_pd2962000.m3u8':
Duration: 00:49:21.12, start: 0.000000, bitrate: 0 kb/s
Program 0
Metadata:
variant_bitrate : 0
Stream #0:0: Data: timed_id3 (ID3  / 0x20334449)
Stream #0:1: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p, 1280x720
[SAR 1:1 DAR 16:9], 25 fps, 25 tbr, 90k tbn, 50 tbc
Stream #0:2: Audio: aac (LC) ([15][0][0][0] / 0x000F), 48000 Hz, stereo, fltp, 129 kb/s
[mp4 @<PHONE_NUMBER>9b00c0] Codec for stream 0 does not use global headers but container format requires global headers
[mp4 @<PHONE_NUMBER>9b00c0] Codec for stream 1 does not use global headers but container format requires global headers
Output #0, mp4, to 'file:╨Т╨╡╤Б╤В╨╕. ╨н╤Д╨╕╤А ╨╛╤В 26.11.2015 (17_00)-1453641.mp4.part':
Metadata:
encoder         : Lavf57.16.100
Stream #0:0: Video: h264 ([33][0][0][0] / 0x0021), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], q=2-31, 25 fps, 25 tbr, 90k tbn, 90k tbc
Stream #0:1: Audio: aac ([64][0][0][0] / 0x0040), 48000 Hz, stereo, 129 kb/s
Stream mapping:
Stream #0:1 -> #0:0 (copy)
Stream #0:2 -> #0:1 (copy)
Press [q] to stop, [?] for help
frame=  481 fps=0.0 q=-1.0 size=    4666kB time=00:00:19.22 bitrate=1988.8kbits/
frame=  961 fps=805 q=-1.0 size=    9122kB time=00:00:38.42 bitrate=1944.9kbits/
...
Thanks in advance!
-t

Works fine for me. Should be a temporary issue. Is it reproducible now?

I found the problem point. To get video as usual it need to be added /viewtype/picture at the end of address, like :  http://russia.tv/video/show/brand_id/5402/episode_id/986443/video_id/998716/viewtype/picture. I will close issue now, thanks anyway !:)

/viewtype/picture at the end does not affect extraction in any way.

Strange... I ran 1st step again: youtube-dl.exe -v http://russia.tv/video/show/brand_id/5402/episode_id/986443/video_id/998716/ , and video starts downloading w/o problems.

btw, I found something interesting. When I run youtube-dl --list-formats http://russia.tv/brand/show/brand_id/59967/ -- I get this 'unsupported' stuff again, yet when I visit this url - video itself is NOT available, only screenshots are listed.
Adding "viewtype/picture" to the url I get list of all supported formats and one of them is hls-1800 (720p) - hooray, I discovered the hidden way to get videos from the russia.tv site b4 they officially post it to the public ;)


new psf behavior update

E.G:
Windows10.0-KB5004567-x64-baseless_41fdbca3.cab | 41fdbca3d0868b158a332a744f5ede77d83f2e2e | 29.11 KiB
Windows10.0-KB5004567-x64-baseless_87afeecd.psf | 87afeecd1e0a587f16390eac4ee277269ef80e39 | 116.17 KiB
Windows10.0-KB5004567-x64_611502da.cab | 611502dae49fd21cc5f5c1b4c998d9e75cfe099a | 27.01 KiB

Actually, baseless PSFs aren't necessary for installing an update, although it could be supported in a future version, or maybe not. Currently you can just delete any update which contains "baseless".

del the small one baseless and place others cab and psf alone, that's works.

del the small one baseless and place others cab and psf alone, that's works.

Windows10.0-KB5004567-x64_611502da.cab is already independant, it does not need the psf
baseless cab/psf works together


1.12和1.12.1版本出现错误提示,1.11没问题，不知什么原因

INFO: scrcpy 1.12.1 https://github.com/Genymobile/scrcpy
stat: No such file or directory
ERROR: 'E:\安卓\黑域\scrcpy-win64-v1.12.1\scrcpy-server' does not exist or is not a regular file
Press any key to continue...

Fixed by #1002 (merged on dev).
To avoid the problem for now, do not use non-ASCII characters in your path (so move E:\安卓\黑域\scrcpy-win64-v1.12.1 to E:\Android\scrcpy-win64-v1.12.1 for example).
Please post issues in English, I don't understand chinese.

1.12 and 1.12.1 version error message appears, 1.11 is no problem, for some reason


Usage with hyper's RequestBuilder

I'm finding it quite challenging to retrofit multipart into a client library that was built using hyper's RequestBuilder. I've been trying to implement HttpRequest and HttpStream for a wrapper around hyper's RequestBuilder (I can't see an obvious way to implement it directly against RequestBuilder), and perhaps my Rust is still just inadequate, but I keep hitting walls. I've worked around a few limitations of RequestBuilder by handling it very much like SizedRequest in this library (buffer input to a Vec and defer setting headers until finish is called since RequestBuilder consumes self to set headers).
However, I can't seem to call RequestBuilder's body method inside finish given the trait's lifetimes: RequestBuilder only borrows the buffer, and (if I understand correctly), I can't ensure that self (which owns the buffer) outlives the response (I'm not sure I grok why it even needs to outlive the response, but the borrow checker has defeated me for today.)
I thought I'd reach out and see if there was an obvious answer that I've been overlooking all along. Are there any examples of multipart used in conjunction with hyper's RequestBuilder? Is this even in-scope for this lib?
pub struct MultipartBuilder<'a> {
    inner: RequestBuilder<'a, Url>,
    boundary: String,
    buffer: Vec<u8>,
}

impl <'a> HttpRequest for MultipartBuilder<'a>  {
    type Stream = Self;
    type Error = HyperError;

    fn apply_headers(&mut self, boundary: &str, content_len: Option<u64>) -> bool {
        // Can't actually set headers, because RequestBuilder's header method consumes self
        self.boundary = boundary.into();
        true
    }
    fn open_stream(mut self) -> Result<Self::Stream, Self::Error> {
        // Can't actually get RequestBuilder's stream, so we'll buffer it and handle it in `finish`
        self.buffer.clear();
        Ok(self)
    }

}

impl <'a> HttpStream for MultipartBuilder<'a>  {
    type Request = Self;
    type Response = Response;
    type Error = HyperError;

    fn finish(mut self) -> Result<Self::Response, Self::Error> {
        self.inner
            .header(ContentType(Mime(
                TopLevel::Multipart, SubLevel::Ext("form-data".into()),
                vec![(Attr::Ext("boundary".into()), Value::Ext(self.boundary))]
            )))
            .header(ContentLength(self.buffer.len() as u64))
            .body(&*self.buffer)  // BAD: &*self.buffer doesn't live long enough
            .send()
    }
}

So RequestBuilder has a lifetime 'a, which, as you guessed correctly, means it only borrows the buffer passed to .body(), so it requires that that buffer outlive 'a.
There's a couple possible ways you could fix this. I think you should be able to lift self.inner to a local let binding, which should hint to the compiler that it won't outlive finish(). It may necessitate lifting the borrow of self.buffer to the same level:
let buffer = &*self.buffer;
let inner = self.inner;
inner.header(...)
    .header(...)
    .body(buffer)
    .send();

The other would be to delay creating the RequestBuilder, only storing the Url and then using it to construct RequestBuilder in finish(). That way you don't have a lifetime to bind to MultipartBuilder.
The client-side of multipart wasn't really designed with RequestBuilder in mind. That feature came a little while after principle development and RequestBuilder didn't seem flexible enough to support important features in multipart, like writing the request fields directly to the stream as they come in.
Is there anything wrong with using multipart as it was designed? The hyper::client::Request API really is much more flexible.

Thanks for taking the time to suggest some changes on my end. Unfortunately lifting buffer and inner didn't resolve it. I suspect it's because the builder pattern is consuming self at every step so the compiler seems to believe the borrowed buffer is part of the object being returned. I'll chew on your other suggestion a bit more, although in the context of an API client with lots of non-multipart requests, it feels a bit strange to have a very different mechanism for injecting other headers (like Auth) into multipart requests.
I agree that hyper's RequestBuilder isn't nearly as flexible as Request. I did start down the route of ripping out all usage of RequestBuilder, and multipart is great for working with Request, but Request just felt too low-level for what I want to accomplish. Perhaps I overcomplicated it, but I quickly found myself basically reinventing RequestBuilder: shamelessly copying from RequestBuilder to configure/share a connection pool, handle timeouts, follow redirects, think about chunked vs sized requests and set content-length myself (for non-multipart requests), and then expose all that in a ergonomic module that I could use throughout the rest of the library. I felt like it was a lot of overhead just to add support for multipart requests.
RequestBuilder provides a really simple abstraction that frees me from thinking of all of that. While it may be out of scope for this this project, it seems like there is a place for combining that level of simplicity with the ability to make multipart requests. I'm just trying to decide if I feel strongly enough about it to build it.


merge task being retried indefinitely

Bug Report
Merge task fails to complete due to 404 response from s3. Here is the exception logged by write worker.
2024.01.11 13:29:57.263550 [ 357 ] {} <Error> executeManipulationTask: Failed to execute ManipulationTask {446950223951429682}, type Merge, ed_mt_v1.`ed_metric_2d6be233-f7bb-4fe1-90a5-28a95c86ec9c` (37908a4f-d72e-4221-aa1e-972fd9854aad):  source_parts: { 20240111_446943989621063692_446943989621063692_0_446943989503098945, 20240111_446944005218369554_446944005218369554_0_446944005139726375, 20240111_446944025483149469_446944025483149469_0_446944023498457152, 20240111_446944036770021421_446944036770021421_0_446944036691116063, 20240111_446944052581761035_446944052581761035_0_446944052463796277 } new_part_names: { 20240111_446943989621063692_446944052581761035_1_446950223951429682 } columns_commit_time:<PHONE_NUMBER>79593252: Code: 499, e.displayText() = DB::S3::S3Exception: Encounter exception when request s3, HTTP Code: 404, RemoteHost: , RequestID: , ExceptionName: , ErrorMessage: No response body., Extra:  SQLSTATE: HY000, Stack trace (when copying this message, always include the lines below):
0. Poco::Exception::Exception(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, int) @ 0x1f837c12 in /opt/byconity/bin/clickhouse
1. DB::Exception::Exception(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, int, bool) @ 0xdbc33a0 in /opt/byconity/bin/clickhouse
2. DB::S3::S3Exception::S3Exception(Aws::S3::S3Error const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) @ 0xdd53910 in /opt/byconity/bin/clickhouse
3. DB::S3::S3Util::headObject(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) const @ 0xdd5a33a in /opt/byconity/bin/clickhouse
4. DB::S3::S3Util::getObjectSize(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) const @ 0xdd59d83 in /opt/byconity/bin/clickhouse
5. DB::DiskByteS3::getFileSize(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) const @ 0x194123de in /opt/byconity/bin/clickhouse
6. DB::MergeTreeDataPartCNCH::loadPartDataFooter() const @ 0x1a634508 in /opt/byconity/bin/clickhouse
7. DB::MergeTreeDataPartCNCH::loadChecksumsForPart(bool) @ 0x1a6305df in /opt/byconity/bin/clickhouse
8. DB::MergeTreeDataPartCNCH::loadChecksums(bool) @ 0x1a63684e in /opt/byconity/bin/clickhouse
9. DB::IMergeTreeDataPart::getChecksums() const @ 0x1a54fe6a in /opt/byconity/bin/clickhouse
10. DB::MergeTreeDataPartCNCH::loadColumnsChecksumsIndexes(bool, bool) @ 0x1a62ed70 in /opt/byconity/bin/clickhouse
11. void std::__1::__function::__policy_invoker<void (std::__1::shared_ptr<DB::IMergeTreeDataPart>&)>::__call_impl<std::__1::__function::__default_alloc_func<DB::MergeTreeCloudData::loadDataPartsInParallel(std::__1::vector<std::__1::shared_ptr<DB::IMergeTreeDataPart>, std::__1::allocator<std::__1::shared_ptr<DB::IMergeTreeDataPart> > >&)::$_0, void (std::__1::shared_ptr<DB::IMergeTreeDataPart>&)> >(std::__1::__function::__policy_storage const*, std::__1::shared_ptr<DB::IMergeTreeDataPart>&) @ 0x1a5a701a in /opt/byconity/bin/clickhouse
12. ThreadPoolImpl<ThreadFromGlobalPool>::worker(std::__1::__list_iterator<ThreadFromGlobalPool, void*>) @ 0xdc06b9e in /opt/byconity/bin/clickhouse
13. ThreadFromGlobalPool::ThreadFromGlobalPool<void ThreadPoolImpl<ThreadFromGlobalPool>::scheduleImpl<void>(std::__1::function<void ()>, int, std::__1::optional<unsigned long>)::'lambda0'()>(void&&, void ThreadPoolImpl<ThreadFromGlobalPool>::scheduleImpl<void>(std::__1::function<void ()>, int, std::__1::optional<unsigned long>)::'lambda0'()&&...)::'lambda'()::operator()() @ 0xdc089e8 in /opt/byconity/bin/clickhouse
14. ThreadPoolImpl<std::__1::thread>::worker(std::__1::__list_iterator<std::__1::thread, void*>) @ 0xdc0377f in /opt/byconity/bin/clickhouse
15. void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void ThreadPoolImpl<std::__1::thread>::scheduleImpl<void>(std::__1::function<void ()>, int, std::__1::optional<unsigned long>)::'lambda0'()> >(void*) @ 0xdc07a5a in /opt/byconity/bin/clickhouse
16. start_thread @ 0x7ea7 in /lib/x86_64-linux-gnu/libpthread-2.31.so
17. clone @ 0xfca2f in /lib/x86_64-linux-gnu/libc-2.31.so
 (version <IP_ADDRESS>)

Briefly describe the bug
We realized a merge task being rescheduled continuously. We observed the merge task fails with the above message.
The result you expected
If the error is an unrecoverable error like expected files somehow not being present in the storage, server should not retry the merge indefinitely.
How to Reproduce
Not sure about the root cause but maybe deleting some underlying files from s3 manually might put the server in this stuck merge state.
Version
We built from the source code: 39d7858f351be516ebccceb59be129c45d4abe98

@dogauzuncukoglu
Hi, are the writes and queries all working well, only the merge task fails?

Hi, @Alima777
Yes everything works well if stuck merge task count is not large. We observed at some point there was ~90 merge tasks that were failing for a table. If it gets to that amount it blocks other merge tasks from being run so performance starts to degrade. It can be resolved by increasing the worker count.
We have truncated the problematic table to fix the issue.

Hi, @dogauzuncukoglu

We have truncated the problematic table to fix the issue.

Is only one table wrong?  It seems the meta data of this table somehow not consistent with the acutal data.

Yes. This might be due to some misconfiguration on our side. The table in question had was a target table for a materialized view and we were dropping and recreating mat views very frequently at the time we observed the issue.
I am not sure about the root cause. I would like to ask whether it is possible to prevent task failures in this case?
For example would it make sense to try something like this. Assuming the stuck merge task is running for an older partition?

stop merges for the table
set cnch_merge_only_realtime_partition to true
start merges for the table

Hi @dogauzuncukoglu , from your description, seems there are some consistency issue between part meta (in fdb) and part files (in S3). To find the root cause, we need more informations like

the merge log on worker side, shows which parts are selected to the merge task.
the system.server_part_log, to check the operation records of those problematic parts.
and check the operation records of the part files on S3 side. (like when the part file is deleted).

And about the workaround like what you suggested, we have no such strategies for now.
If there are only a small number of partitions encounter this issue, maybe you can:

export the data to a tmp table. INSERT INTO tmp SELECT * FROM table WHERE partition_expression ;
drop the problematic partitions. ALTER TABLE table DROP PARTITION ... ;
reimport the data from tmp. INSERT INTO table SELECT * FROM tmp;

Hi @dogauzuncukoglu , would you please provide the information zeromem listed?


Separate field array props

As voted in #1063.

It would be a good idea to refactor createFieldArrayProps because it creates multiple closures and is called on every render of FieldArray. Adding some kind of memoization would improve perf and prevent additional GC.

@ooflorent I nominate you for doing that memoization. 😃

@erikras is there any plan to make the same change to Field components? The same issue for passing along props exists and it's been awkward that they're inconsistent.
i.e.
const MCHammer = ({ field, hammerTime }) => (
  <input {...field} placeholder={hammerTime ? 'Stop, hammer time' : ''} />
);

// etc

<Field component={MCHammer} hammerTime />


Add Author Data

For each author, four works were added in the respective language of the model.
Four negative examples were also added per author.

looks good!


/ticket for users to open issues

Feature request: We have workflows in place for bugs and frs but nothing for just general help when dollar is having issues. /ticket should DM the user an invite link to the mfDiscord, specifically the issues channel. We should be sending invite links with expiration so that users don't have long standing access to the issues channel.
Submitted by: Cash#8915
Server: mfDiscord

Was able to create the following, won't be able to test since my dev environment is not in the mfDiscord, so during Dollar's downtime tonight I will test this:

Works if you are in a discord outside of the mfDiscord, but if you are already a member of the mfDiscord it should simply grant permission to join the #issues channel, this is fine but that logic should be added in 1.1.2


Replace the hyperlink of downloading iTwin Synchronizer

Current link leads to a wrong page.  BE Communities is probably not the best reference but at least its topic is relevant and there is a download button to download ITSYNC.

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


Burp Extension with Custom Profiles

I'm using Autochrome to check different user profiles. Therefore I created a seperate "person" for each profile.
However, when I'm using my own profiles, the profile is not added to the user-agent header. Hence there is no way to see the different profiles in Burp.

AFAIK, there's no way for a chrome extension to get info about the profile.  What AutoChrome does to work around this is create a special bookmark with the profile that the extension reads.
(A UI to create/edit this field would be nice, but it's probably not going to happen unless somebody submits a patch.)
Otherwise, a workaround / manual process for you is:

Create the new profile.
Enable the integration extension for the new profile via the yellow exclamation point icon in the upper right.  (I think this is only available until you quit chromium, so you may need to recreate your profiles.)
Create a bookmark (cmd/ctrl-D on any page, click "more...") with the name "Autochrome Profile Name" and the URL "http://foobar", where "foobar" is the profile's name.
Restart Chromium.

Hi there. I do not see a yellow exclamation point icon anywhere in the browser UI. I have been unable to see any functionality from the burp extension. I followed the steps above to no avail.

Closing, please re-open the issue if it is still a problem.

It wasn't resolved so it is still a problem?


Accidental donation

I have made an accidental donation back in september, tried to reach the support a few times but they stopped responding. It's not a little bit of money, at least to me. Can anybody help me? Thank you!

Closed and resolved:
@mpablopavan


Documentation: path delimiter

Working: ["notepad.exe"]
Not working: ["C:\Program Files (x86)\Kodi\Kodi.exe"]
Working: ["C:\\Program Files (x86)\\Kodi\\Kodi.exe"]
Working: ["C:/Program Files (x86)/Kodi/Kodi.exe"]
Please correct the README

Thanks, fixed.

Great!


Throw errors with more meaningful paths

Closes https://github.com/APIDevTools/json-schema-ref-parser/issues/164
I felt like a separate test suite was the best choice here, but happy to spread these new tests across some existing ones if you think that'd be a better option.

@P0lip - It looks like something in this PR doesn't work on Windows.  CI is passing on Linux and Mac but failing on Windows
https://github.com/APIDevTools/json-schema-ref-parser/actions/runs/93093603

@JamesMessinger I see - going to take a look this weekend. Seems like a path might be incorrect (slashes), but I need to take a look to confirm.
Will create a follow-up PR when I have the updated test

Thanks @P0lip !


[Research] Add toxicity detection pipeline

Goals :soccer:
The addition of a Toxicity Detection pipeline that monitors discussion on GitHub and which responds to toxic comments.
Did you ever consider the addition of a toxicity detection bot to this project?
We’re Nathan Cassee and Alexander Serebrenik (Eindhoven University of Technology, The Netherlands), Nicole Novielli (University of Bari, Italy), Christian Kastner (Carnegie Mellon University, USA), and Bogdan Vasilescu (Carnegie Mellon University, USA). And we are conducting research to understand the effectiveness of toxicity detection bots on GitHub. As part of our research we want to understand the impact of a state of the art toxicity detection bot in your project. We hope that a better knowledge and understanding of how these toxicity bots operate can be used to further improve the health of open-source projects.
To participate in this experiment we ask you to adopt a toxicity bot in Alamofire/Alamofire. You can adopt the bot by merging this pull-request. This bot will monitor issues and pull-requests for comments containing toxicity, and will post a comment if it detects toxicity. Additionally, the bot will securely store comments and edits or deletions made to those comments. This will allow us to study the frequency of toxic comments, and whether and how toxic comments are edited or deleted.
We expect that the toxicity bot reduces toxicity in issues or in pull-requests. However, there might be cases where the bot responds in issues or pull-requests where there is no toxicity (a false positive) and this might distract on-topic discussions.
Implementation Details :construction:
Your participation in this study is completely voluntary, at any point in time you can retract your project from this study. This can be done by disabling the toxicity bot, or by sending us an email. Additionally, if you don’t want us to use the results of your project in the analysis of the study, you can always email us to inform us that you want to retract your data from the study.
The study itself will run for roughly three months, at the end of this time we will open a PR in your project to remove the toxicity bot from the project. If after the experiment you want to keep using the toxicity bot we can also provide you with a version of the toxicity bot that does not record telemetry.
The data collected for this study will be stored securely on a private server, and the raw data will only be available to the researchers involved in this study. When we release or publicize results of the study the results will be released anonymously or in an aggregated way. Additionally, we will not list the projects that participated in this study, nor will will we release or report on any information that can be used to compare whether one project is more toxic than the other.
This study has been approved by the Ethical Review Board of the Eindhoven University of Technology.
Closing and Survey
If you have any questions about the bot feel free to ask them here, or mail them to<EMAIL_ADDRESS>If you are not interested in participating we would really appreciate it if you would let us know why you are not participating.
Secondly, it would be really helpful if everyone involved in the project could respond to the following survey on your expectations of the bot, especially if you are not interested in adopting the bot (https://docs.google.com/forms/d/e/1FAIpQLSdwaKnGbmVwYW0LVVymTvh6XPgPN1A6Jpuwh3_m7hSxYqn1dw/viewform)!

No thanks. There's really not enough traffic to this repo for this to be useful. What toxicity we get is easy to handle so far.

Thank you for your quick response, and best of luck with Alamofire!


Interfaces name is prefixed with 'I'

When running tsd-jsdoc on openlayers 3, it prefixes the interface names with 'I' which lead to errors since typescript cannot find the original type. For example, the olx.style.CircleOptions interface is created as:
interface ICircleOptions {
...
}

but others types still reference it as CircleOptions:
class Circle ... {
    constructor(opt_options?: olx.style.CircleOptions);
...
}

What is the reason for that 'I' prefix?

Probably isn't necessary, can you give a me a code snippet that reproduces?

It's rather difficult to provide a snippet that reproduces the behavior of jsdoc with openlayers. They use plugins to preprocess their files.
For example, the CircleOptions type is defined as follow:
/**
 * @typedef {{fill: (ol.style.Fill|undefined),
 *     radius: number,
 *     snapToPixel: (boolean|undefined),
 *     stroke: (ol.style.Stroke|undefined),
 *     atlasManager: (ol.style.AtlasManager|undefined)}}
 */
olx.style.CircleOptions;

/**
 * Fill style.
 * @type {ol.style.Fill|undefined}
 * @api
 */
olx.style.CircleOptions.prototype.fill;
...

and results as:
/**
 * @typedef {{fill: (ol.style.Fill|undefined),
 *     radius: number,
 *     snapToPixel: (boolean|undefined),
 *     stroke: (ol.style.Stroke|undefined),
 *     atlasManager: (ol.style.AtlasManager|undefined)}}
 */
interface ICircleOptions {
    fill: (ol.style.Fill|undefined);
    ...
}

Everything is fine except the 'I' prefix.
In your code, I saw you just add that prefix. Is it possible to have an option to enable/disable that behavior?

Thanks for opening #5, I'm sure that will be super useful!

Merged!


[KOGITO-8652] Exception/Error thrown in a sub-process doesn't reach the boundary error in the parent Service Task

TEST CASE

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

PASSED: 1602
FAILED: 0

Those are the test failures: none
See console log:

Console Logs
[2023-02-14T08:34:09.778Z] [INFO] Kogito :: Quarkus Workflows Extension :: Deployment  SKIPPED[2023-02-14T08:34:09.778Z] [INFO] Kogito :: Add-Ons :: Persistence :: Parent ......... SUCCESS [  0.036 s][2023-02-14T08:34:09.778Z] [INFO] Kogito :: Add-Ons :: Persistence :: JDBC ........... SKIPPED[2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Quarkus Persistence .................. SUCCESS [  0.051 s][2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Persistence JDBC - Parent ............ SUCCESS [  0.035 s][2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Persistence JDBC ..................... SKIPPED[2023-02-14T08:34:09.778Z] [INFO] Kogito :: Add-Ons :: Quarkus :: Events ............. SUCCESS [  0.064 s][2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Events Process - Parent .............. SUCCESS [  0.048 s][2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Events Process ....................... SUCCESS [  1.297 s][2023-02-14T08:34:09.778Z] [INFO] Kogito :: Test Utilities :: Quarkus ................ SUCCESS [ 22.894 s][2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Persistence JDBC - Deployment ........ SKIPPED[2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Events Process - Deployment ..........  SUCCESS [  1.856 s][2023-02-14T08:34:09.778Z] [INFO] Kogito :: Add-Ons :: Persistence :: Infinispan ..... SKIPPED[2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Persistence Infinispan - Parent ...... SUCCESS [  0.034 s][2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Persistence Infinispan ............... SKIPPED[2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Persistence Infinispan - Deployment .. SKIPPED[2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Persistence Infinispan Health Check .. SUCCESS [01:41 min][2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Persistence Kafka Streams - Parent ... SUCCESS [  0.043 s][2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Persistence Kafka Streams ............ SKIPPED[2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Persistence Kafka Streams - Deployment SKIPPED[2023-02-14T08:34:09.778Z] [INFO] Kogito :: Add-Ons :: Persistence :: File System .... SKIPPED[2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Persistence FileSystem - Parent ...... SUCCESS [  0.024 s][2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Persistence FileSystem ............... SKIPPED[2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Persistence FileSystem - Deployment .. SKIPPED[2023-02-14T08:34:09.778Z] [INFO] Kogito :: Add-Ons :: Persistence :: MongoDB ........ SKIPPED[2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Persistence MongoDB - Parent ......... SUCCESS [  0.034 s][2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Persistence MongoDB .................. SKIPPED[2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Persistence MongoDB - Deployment ..... SKIPPED[2023-02-14T08:34:09.778Z] [INFO] Kogito :: Add-Ons :: Persistence :: PostgreSQL ..... SKIPPED[2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Persistence PostgreSQL - Parent ...... SUCCESS [  0.030 s][2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Persistence PostgreSQL ............... SKIPPED[2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Persistence PostgreSQL - Deployment .. SKIPPED[2023-02-14T08:34:09.778Z] [INFO] Kogito :: Add-Ons :: Process SVG :: Common ......... SUCCESS [  9.803 s][2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Process SVG - Parent ................. SUCCESS [  0.136 s][2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Process SVG .......................... SUCCESS [ 12.920 s][2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Process SVG - Deployment ............. SKIPPED[2023-02-14T08:34:09.778Z] [INFO] Kogito :: Add-Ons :: Process Management :: Common .. SUCCESS [  8.437 s][2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Process Management - Parent .......... SUCCESS [  0.143 s][2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Process Management ................... SUCCESS [ 10.132 s][2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Process Management - Deployment ...... SKIPPED[2023-02-14T08:34:09.778Z] [INFO] Kogito :: Add-Ons :: Source Files :: Common ........ SKIPPED[2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Source Files - Parent ................ SUCCESS [  0.115 s][2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Source Files ......................... SKIPPED[2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Source Files - Deployment ............ SKIPPED[2023-02-14T08:34:09.778Z] [INFO] Kogito :: Add-Ons :: Knative :: Parent ............. SUCCESS [  0.029 s][2023-02-14T08:34:09.778Z] [INFO] Kogito :: Add-Ons :: Knative :: Eventing ........... SUCCESS [  9.713 s][2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Knative - Parent ..................... SUCCESS [  0.059 s][2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Knative Eventing - Parent ............ SUCCESS [  0.023 s][2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Knative Eventing ..................... SUCCESS [  3.240 s][2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Knative Eventing - Deployment ........ SKIPPED[2023-02-14T08:34:09.778Z] [INFO] Kogito :: Add-Ons :: Events :: Parent .............. SUCCESS [  0.039 s][2023-02-14T08:34:09.778Z] [INFO] Kogito :: Add-Ons :: Events :: Event-Driven Decisions SUCCESS [ 16.835 s][2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Events Decisions - Parent ............ SUCCESS [  0.036 s][2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Events Decisions ..................... SUCCESS [  1.346 s][2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Events Decisions - Deployment ........ SKIPPED[2023-02-14T08:34:09.778Z] [INFO] Kogito :: Add-Ons :: Events :: Event-Driven Predictions SUCCESS [ 10.204 s][2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Events Predictions - Parent .......... SUCCESS [  0.022 s][2023-02-14T08:34:09.778Z] [INFO] Kogito Add-On Events Predictions ................... SUCCESS [  1.180 s][2023-02-14T08:34:09.779Z] [INFO] Kogito Add-On Events Predictions - Deployment ...... SKIPPED[2023-02-14T08:34:09.779Z] [INFO] Kogito :: Add-Ons :: Events :: Event-Driven Rules .. SUCCESS [  8.125 s][2023-02-14T08:34:09.779Z] [INFO] Kogito Add-On Events Rules - Parent ................ SUCCESS [  0.034 s][2023-02-14T08:34:09.779Z] [INFO] Kogito :: Add-Ons :: Events :: Event-Driven Rules :: Quarkus SUCCESS [  1.399 s][2023-02-14T08:34:09.779Z] [INFO] Kogito Add-On Events Rules - Deployment ............ SKIPPED[2023-02-14T08:34:09.779Z] [INFO] Kogito :: Add-Ons :: Events :: MongoDB ............. SKIPPED[2023-02-14T08:34:09.779Z] [INFO] Kogito Add-On Events MongoDB - Parent .............. SUCCESS [  0.024 s][2023-02-14T08:34:09.779Z] [INFO] Kogito Add-On Events MongoDB ....................... SKIPPED[2023-02-14T08:34:09.779Z] [INFO] Kogito Add-On Events MongoDB - Deployment .......... SKIPPED[2023-02-14T08:34:09.779Z] [INFO] Kogito :: Add-Ons :: Marshallers :: Parent ......... SUCCESS [  0.035 s][2023-02-14T08:34:09.779Z] [INFO] Kogito :: Add-Ons :: Marshallers:: Avro ............ SUCCESS [ 11.888 s][2023-02-14T08:34:09.779Z] [INFO] Kogito :: Add-Ons :: Quarkus:: Marshallers :: Parent SUCCESS [  0.035 s][2023-02-14T08:34:09.779Z] [INFO] Kogito :: Add-Ons :: Quarkus:: Marshallers:: Avro:: Parent SUCCESS [  0.046 s][2023-02-14T08:34:09.779Z] [INFO] Kogito :: Add-Ons :: Quarkus:: Marshallers:: Avro .. SUCCESS [  0.830 s][2023-02-14T08:34:09.779Z] [INFO] Kogito :: Add-Ons :: Quarkus:: Marshallers:: Avro:: Deployment SUCCESS [  1.170 s][2023-02-14T08:34:09.779Z] [INFO] Kogito :: Add-Ons :: Quarkus :: Camel :: Parent .... SUCCESS [  0.033 s][2023-02-14T08:34:09.779Z] [INFO] Kogito :: Add-Ons :: Quarkus :: Camel :: Runtimes .. SUCCESS [  3.126 s][2023-02-14T08:34:09.779Z] [INFO] Kogito :: Add-Ons :: Quarkus :: Camel :: Deployment  SKIPPED[2023-02-14T08:34:09.779Z] [INFO] Kogito :: Add-Ons :: Quarkus :: Camel :: Integration Tests SKIPPED[2023-02-14T08:34:09.779Z] [INFO] Kogito :: Add-Ons :: Explainability ................ SUCCESS [ 12.916 s][2023-02-14T08:34:09.779Z] [INFO] Kogito Add-On Explainability - Parent .............. SUCCESS [  0.048 s][2023-02-14T08:34:09.779Z] [INFO] Kogito Add-On Explainability ....................... SUCCESS [  3.456 s][2023-02-14T08:34:09.779Z] [INFO] Kogito Add-On Explainability - Deployment .......... SKIPPED[2023-02-14T08:34:09.779Z] [INFO] Kogito Add-On Explainability - Integration tests ... SKIPPED[2023-02-14T08:34:09.779Z] [INFO] Kogito :: Add-Ons :: Jobs .......................... SUCCESS [  0.028 s][2023-02-14T08:34:09.779Z] [INFO] Kogito :: Add-Ons :: Jobs :: API ................... SUCCESS [  8.038 s][2023-02-14T08:34:09.779Z] [INFO] Kogito Add-Ons Quarkus Jobs Parent ................. SUCCESS [  0.031 s][2023-02-14T08:34:09.779Z] [INFO] Kogito Add-Ons Quarkus Jobs Common - Parent ........ SUCCESS [  0.042 s][2023-02-14T08:34:09.779Z] [INFO] Kogito Add-Ons Quarkus Jobs Common - Messaging ..... SUCCESS [  7.171 s][2023-02-14T08:34:09.779Z] [INFO] Kogito Add-Ons Quarkus - Rest Callback ............. SUCCESS [ 13.767 s][2023-02-14T08:34:09.779Z] [INFO] Kogito :: Add-Ons :: Jobs :: Management Common ..... SUCCESS [  4.565 s][2023-02-14T08:34:09.779Z] [INFO] Kogito Add-Ons Quarkus Jobs Management - Parent .... SUCCESS [  0.042 s][2023-02-14T08:34:09.779Z] [INFO] Kogito Add-Ons Quarkus Jobs - Management ........... SUCCESS [ 13.048 s][2023-02-14T08:34:09.779Z] [INFO] Kogito Add-Ons Quarkus Jobs Management - Deployment  SKIPPED[2023-02-14T08:34:09.779Z] [INFO] Kogito Add-Ons Quarkus Jobs Messaging - Parent ..... SUCCESS [  0.028 s][2023-02-14T08:34:09.779Z] [INFO] Kogito Add-Ons Quarkus Jobs - Messaging ............ SUCCESS [ 19.041 s][2023-02-14T08:34:09.779Z] [INFO] Kogito Add-Ons Quarkus Jobs Messaging - Deployment . SKIPPED[2023-02-14T08:34:09.779Z] [INFO] Kogito Add-Ons Quarkus Jobs Knative Eventing - Parent SUCCESS [  0.023 s][2023-02-14T08:34:09.779Z] [INFO] Kogito Add-Ons Quarkus Jobs - Knative Eventing ..... SUCCESS [ 12.820 s][2023-02-14T08:34:09.779Z] [INFO] Kogito Add-Ons Quarkus Jobs Knative Eventing - Deployment SKIPPED[2023-02-14T08:34:09.779Z] [INFO] Kogito :: Add-Ons :: E-Mail :: Common .............. SUCCESS [  8.350 s][2023-02-14T08:34:09.779Z] [INFO] Kogito Add-On Mail - Parent ........................ SUCCESS [  0.023 s][2023-02-14T08:34:09.779Z] [INFO] Kogito Add-On Mail ................................. SUCCESS [ 47.801 s][2023-02-14T08:34:09.779Z] [INFO] Kogito Add-On Mail - Deployment .................... SKIPPED[2023-02-14T08:34:09.779Z] [INFO] Kogito :: Add-Ons :: Monitoring .................... SUCCESS [  0.027 s][2023-02-14T08:34:09.779Z] [INFO] Kogito :: Add-Ons :: Monitoring Core ............... SUCCESS [ 15.298 s][2023-02-14T08:34:09.779Z] [INFO] Kogito Add-On Monitoring - Parent .................. SUCCESS [  0.034 s][2023-02-14T08:34:09.779Z] [INFO] Kogito Add-On Monitoring Core ...................... SUCCESS [ 19.150 s][2023-02-14T08:34:09.779Z] [INFO] Kogito :: Add-Ons :: Monitoring Prometheus Common .. SUCCESS [  1.163 s][2023-02-14T08:34:09.779Z] [INFO] Kogito Add-On Monitoring Prometheus - Parent ....... SUCCESS [  0.030 s][2023-02-14T08:34:09.779Z] [INFO] Kogito Add-On Monitoring Prometheus ................ SUCCESS [  6.907 s][2023-02-14T08:34:09.779Z] [INFO] Kogito Add-On Monitoring Prometheus - Deployment ... SKIPPED[2023-02-14T08:34:09.779Z] [INFO] Kogito :: Add-Ons :: Monitoring Elastic Common ..... SUCCESS [  8.715 s][2023-02-14T08:34:09.779Z] [INFO] Kogito Add-On Monitoring Elastic - Parent .......... SUCCESS [  0.027 s][2023-02-14T08:34:09.779Z] [INFO] Kogito Add-On Monitoring Elastic ................... SUCCESS [  1.510 s][2023-02-14T08:34:09.779Z] [INFO] Kogito Add-On Monitoring Elastic - Deployment ...... SKIPPED[2023-02-14T08:34:09.779Z] [INFO] Kogito Add-On Task Notification - Parent ........... SUCCESS [  0.055 s][2023-02-14T08:34:09.779Z] [INFO] Kogito Add-On Task Notification .................... SUCCESS [  2.806 s][2023-02-14T08:34:09.779Z] [INFO] Kogito Add-On Task Notification - Deployment ....... SKIPPED[2023-02-14T08:34:09.779Z] [INFO] Kogito :: Add-Ons :: Tracing ....................... SUCCESS [  0.027 s][2023-02-14T08:34:09.779Z] [INFO] Kogito :: Add-Ons :: TypedValue API ................ SUCCESS [  7.745 s][2023-02-14T08:34:09.779Z] [INFO] Kogito :: Add-Ons :: Tracing :: API ................ SUCCESS [ 10.574 s][2023-02-14T08:34:09.779Z] [INFO] Kogito :: Add-Ons :: Tracing :: Common ............. SUCCESS [ 22.404 s][2023-02-14T08:34:09.779Z] [INFO] Kogito Add-On Tracing Decision - Parent ............ SUCCESS [  0.041 s][2023-02-14T08:34:09.779Z] [INFO] Kogito Add-On Tracing Decision ..................... SUCCESS [ 23.579 s][2023-02-14T08:34:09.779Z] [INFO] Kogito Add-On Tracing Decision - Deployment ........ SKIPPED[2023-02-14T08:34:09.779Z] [INFO] Kogito Add-On Tracing Decision - Integration tests . SKIPPED[2023-02-14T08:34:09.779Z] [INFO] Kogito :: Add-Ons :: Task Management :: Common ..... SUCCESS [  0.721 s][2023-02-14T08:34:09.779Z] [INFO] Kogito Add-On Task Management - Parent ............. SUCCESS [  0.048 s][2023-02-14T08:34:09.779Z] [INFO] Kogito Add-On Task Management ...................... SUCCESS [  5.137 s][2023-02-14T08:34:09.779Z] [INFO] Kogito Add-On Task Management - Deployment ......... SKIPPED[2023-02-14T08:34:09.779Z] [INFO] Kogito :: Integration Tests :: Quarkus ............. SUCCESS [  0.052 s][2023-02-14T08:34:09.779Z] [INFO] Kogito :: Integration Tests :: Quarkus :: OpenAPI Client Codegen SKIPPED[2023-02-14T08:34:09.779Z] [INFO] Kogito :: Integration Tests :: Quarkus :: Rules .... SUCCESS [ 54.614 s][2023-02-14T08:34:09.779Z] [INFO] Kogito :: Integration Tests :: Quarkus :: Decisions  SUCCESS [01:01 min][2023-02-14T08:34:09.779Z] [INFO] Kogito :: Integration Tests :: Quarkus :: RESTEasy Classic SUCCESS [ 49.748 s][2023-02-14T08:34:09.779Z] [INFO] Kogito :: Integration Tests :: Quarkus :: RESTEasy Reactive SUCCESS [ 47.730 s][2023-02-14T08:34:09.779Z] [INFO] Kogito :: Maven Plugin ............................. SKIPPED[2023-02-14T08:34:09.779Z] [INFO] Kogito :: Integration Tests :: Maven Plugin ........  SKIPPED[2023-02-14T08:34:09.779Z] [INFO] Kogito :: DB Scripts Collection .................... SUCCESS [  1.858 s][2023-02-14T08:34:09.780Z] [INFO] Kogito :: Add-Ons :: Predictions ................... SUCCESS [  0.039 s][2023-02-14T08:34:09.780Z] [INFO] Kogito :: Add-Ons :: Predictions :: API ............ SKIPPED[2023-02-14T08:34:09.780Z] [INFO] Kogito :: Add-Ons :: Predictions :: SMILE .......... SKIPPED[2023-02-14T08:34:09.780Z] [INFO] Kogito :: Spring Boot .............................. SUCCESS [  0.050 s][2023-02-14T08:34:09.780Z] [INFO] Kogito :: Spring Boot :: BOM ....................... SUCCESS [  0.070 s][2023-02-14T08:34:09.780Z] [INFO] Kogito :: Add-Ons :: Spring Boot ................... SUCCESS [  0.058 s][2023-02-14T08:34:09.780Z] [INFO] Kogito :: Add-Ons :: CloudEvents :: Spring Boot .... SUCCESS [  0.247 s][2023-02-14T08:34:09.780Z] [INFO] Kogito :: Add-Ons :: Messaging :: Spring Boot ...... SUCCESS [  0.624 s][2023-02-14T08:34:09.780Z] [INFO] Kogito :: Add-Ons :: Spring Boot :: Events - Parent  SUCCESS [  0.248 s][2023-02-14T08:34:09.780Z] [INFO] Kogito :: Add-Ons :: Events :: Event-Driven Decisions :: Spring Boot SUCCESS [  1.040 s][2023-02-14T08:34:09.780Z] [INFO] Kogito :: Add-Ons :: Events :: Event-Driven Predictions :: Spring Boot SUCCESS [  0.707 s][2023-02-14T08:34:09.780Z] [INFO] Kogito :: Add-Ons :: Events :: Event-Driven Rules :: Spring Boot SUCCESS [  0.264 s][2023-02-14T08:34:09.780Z] [INFO] Kogito :: Add-Ons :: Events :: SprintBoot :: Process :: Kafka SUCCESS [  2.557 s][2023-02-14T08:34:09.780Z] [INFO] Kogito :: Add-Ons :: Events ::  MongoDB :: SprintBoot SKIPPED[2023-02-14T08:34:09.780Z] [INFO] Kogito :: Spring Boot :: Starters Parent ........... SUCCESS [  8.410 s][2023-02-14T08:34:09.780Z] [INFO] Kogito :: Spring Boot :: Starter :: Decisions ...... SUCCESS [  0.221 s][2023-02-14T08:34:09.780Z] [INFO] Kogito :: Add-Ons :: Messaging :: Spring Boot (ITs)  SKIPPED[2023-02-14T08:34:09.780Z] [INFO] Kogito :: Add-Ons :: Spring Boot :: Monitoring :: Parent SUCCESS [  0.145 s][2023-02-14T08:34:09.780Z] [INFO] Kogito :: Add-Ons :: Monitoring Core Springboot .... SUCCESS [ 19.083 s][2023-02-14T08:34:09.780Z] [INFO] Kogito :: Add-Ons :: Monitoring Prometheus Springboot SUCCESS [  0.796 s][2023-02-14T08:34:09.780Z] [INFO] Kogito :: Add-Ons :: Monitoring Elastic Springboot . SUCCESS [  0.422 s][2023-02-14T08:34:09.780Z] [INFO] Kogito :: Add-Ons :: Explainability :: Spring Boot Addon SUCCESS [ 11.838 s][2023-02-14T08:34:09.780Z] [INFO] Kogito :: Spring Boot :: Starter :: Rules .......... SUCCESS [  0.277 s][2023-02-14T08:34:09.780Z] [INFO] Kogito :: Spring Boot :: Starter :: Processes ...... SKIPPED[2023-02-14T08:34:09.780Z] [INFO] Kogito :: Spring Boot :: Starter :: Predictions .... SUCCESS [  0.201 s][2023-02-14T08:34:09.780Z] [INFO] Kogito :: Spring Boot :: Starter ................... SKIPPED[2023-02-14T08:34:09.780Z] [INFO] Kogito :: Add-Ons :: Jobs :: Management SprintBoot Addon SKIPPED[2023-02-14T08:34:09.780Z] [INFO] Kogito :: Add-Ons :: E-Mail :: Spring Boot Addon ... SUCCESS [  1.238 s][2023-02-14T08:34:09.780Z] [INFO] Kogito :: Add-Ons :: Task notification :: Spring Boot Addon SUCCESS [  2.073 s][2023-02-14T08:34:09.780Z] [INFO] Kogito :: Add-Ons :: Tracing :: Spring Boot ........ SUCCESS [ 19.706 s][2023-02-14T08:34:09.780Z] [INFO] Kogito :: Rest Exception Handler:: Spring Boot ..... SUCCESS [  7.673 s][2023-02-14T08:34:09.780Z] [INFO] Kogito :: Add-Ons :: Process SVG :: Spring Boot Addon SKIPPED[2023-02-14T08:34:09.780Z] [INFO] Kogito :: Add-Ons :: Process Management :: Spring Boot Addon SUCCESS [  7.901 s][2023-02-14T08:34:09.780Z] [INFO] Kogito :: Add-Ons :: Task Management :: Spring Boot Addon SUCCESS [  1.345 s][2023-02-14T08:34:09.780Z] [INFO] Kogito :: Add-Ons :: Spring Boot :: Kubernetes ..... SUCCESS [ 32.077 s][2023-02-14T08:34:09.780Z] [INFO] Kogito :: Add-Ons :: Spring Boot :: Persistence :: Parent SUCCESS [  0.143 s][2023-02-14T08:34:09.780Z] [INFO] Kogito :: Add-Ons :: Persistence File System :: Springboot SKIPPED[2023-02-14T08:34:09.780Z] [INFO] Kogito :: Add-Ons :: Persistence Infinispan :: Springboot SKIPPED[2023-02-14T08:34:09.780Z] [INFO] Kogito :: Add-Ons :: Persistence JDBC :: Springboot  SKIPPED[2023-02-14T08:34:09.780Z] [INFO] Kogito :: Add-Ons :: Persistence MongoDB :: Springboot SKIPPED[2023-02-14T08:34:09.780Z] [INFO] Kogito :: Add-Ons :: Persistence PostgreSQL :: Springboot SKIPPED[2023-02-14T08:34:09.780Z] [INFO] Kogito :: Spring Boot :: Maven Archetype ........... SKIPPED[2023-02-14T08:34:09.780Z] [INFO] Kogito :: Test Utilities :: Spring Boot ............ SUCCESS [ 19.385 s][2023-02-14T08:34:09.780Z] [INFO] Kogito :: Integration Tests :: Spring Boot ......... SKIPPED[2023-02-14T08:34:09.780Z] [INFO] ------------------------------------------------------------------------[2023-02-14T08:34:09.780Z] [INFO] BUILD FAILURE[2023-02-14T08:34:09.780Z] [INFO] ------------------------------------------------------------------------[2023-02-14T08:34:09.780Z] [INFO] Total time:  05:24 min (Wall Clock)[2023-02-14T08:34:09.780Z] [INFO] Finished at: 2023-02-14T03:34:08-05:00[2023-02-14T08:34:09.780Z] [INFO] ------------------------------------------------------------------------[2023-02-14T08:34:09.780Z] [ERROR] Failed to execute goal net.revelc.code.formatter:formatter-maven-plugin:2.13.0:validate (default) on project jbpm-bpmn2: File '/home/jenkins/workspace/KIE/kogito/main/pullrequest/kogito-runtimes.tests.kogito-runtimes/bc/kiegroup_kogito-runtimes/jbpm/jbpm-bpmn2/src/test/java/org/jbpm/bpmn2/ErrorEventTest.java' has not been previously formatted.  Please format file and commit before running validation! -> [Help 1][2023-02-14T08:34:09.780Z] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal net.revelc.code.formatter:formatter-maven-plugin:2.13.0:validate (default) on project jbpm-bpmn2: File '/home/jenkins/workspace/KIE/kogito/main/pullrequest/kogito-runtimes.tests.kogito-runtimes/bc/kiegroup_kogito-runtimes/jbpm/jbpm-bpmn2/src/test/java/org/jbpm/bpmn2/ErrorEventTest.java' has not been previously formatted.  Please format file and commit before running validation![2023-02-14T08:34:09.780Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:375)[2023-02-14T08:34:09.780Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:351)[2023-02-14T08:34:09.780Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)[2023-02-14T08:34:09.780Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:171)[2023-02-14T08:34:09.780Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:163)[2023-02-14T08:34:09.780Z]     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)[2023-02-14T08:34:09.780Z]     at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:210)[2023-02-14T08:34:09.780Z]     at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:195)[2023-02-14T08:34:09.780Z]     at java.util.concurrent.FutureTask.run (FutureTask.java:264)[2023-02-14T08:34:09.780Z]     at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:515)[2023-02-14T08:34:09.780Z]     at java.util.concurrent.FutureTask.run (FutureTask.java:264)[2023-02-14T08:34:09.780Z]     at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1128)[2023-02-14T08:34:09.780Z]     at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:628)[2023-02-14T08:34:09.780Z]     at java.lang.Thread.run (Thread.java:829)[2023-02-14T08:34:09.780Z] Caused by: org.apache.maven.plugin.MojoFailureException: File '/home/jenkins/workspace/KIE/kogito/main/pullrequest/kogito-runtimes.tests.kogito-runtimes/bc/kiegroup_kogito-runtimes/jbpm/jbpm-bpmn2/src/test/java/org/jbpm/bpmn2/ErrorEventTest.java' has not been previously formatted.  Please format file and commit before running validation![2023-02-14T08:34:09.780Z]     at net.revelc.code.formatter.ValidateMojo.doFormatFile (ValidateMojo.java:58)[2023-02-14T08:34:09.780Z]     at net.revelc.code.formatter.FormatterMojo.formatFile (FormatterMojo.java:531)[2023-02-14T08:34:09.780Z]     at net.revelc.code.formatter.FormatterMojo.execute (FormatterMojo.java:402)[2023-02-14T08:34:09.780Z]     at net.revelc.code.formatter.ValidateMojo.execute (ValidateMojo.java:49)[2023-02-14T08:34:09.780Z]     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)[2023-02-14T08:34:09.780Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:370)[2023-02-14T08:34:09.781Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:351)[2023-02-14T08:34:09.781Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)[2023-02-14T08:34:09.781Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:171)[2023-02-14T08:34:09.781Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:163)[2023-02-14T08:34:09.781Z]     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)[2023-02-14T08:34:09.781Z]     at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:210)[2023-02-14T08:34:09.781Z]     at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:195)[2023-02-14T08:34:09.781Z]     at java.util.concurrent.FutureTask.run (FutureTask.java:264)[2023-02-14T08:34:09.781Z]     at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:515)[2023-02-14T08:34:09.781Z]     at java.util.concurrent.FutureTask.run (FutureTask.java:264)[2023-02-14T08:34:09.781Z]     at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1128)[2023-02-14T08:34:09.781Z]     at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:628)[2023-02-14T08:34:09.781Z]     at java.lang.Thread.run (Thread.java:829)[2023-02-14T08:34:09.781Z] [ERROR] [2023-02-14T08:34:09.781Z] [ERROR] Re-run Maven using the -X switch to enable full debug logging.[2023-02-14T08:34:09.781Z] [ERROR] [2023-02-14T08:34:09.781Z] [ERROR] For more information about the errors and possible solutions, please read the following articles:[2023-02-14T08:34:09.781Z] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException[2023-02-14T08:34:09.781Z] [ERROR] [2023-02-14T08:34:09.781Z] [ERROR] After correcting the problems, you can resume the build with the command[2023-02-14T08:34:09.781Z] [ERROR]   mvn  -rf :jbpm-bpmn2[2023-02-14T08:34:10.376Z] [ERROR] Error executing command mvn clean install  -s /home/jenkins/workspace/KIE/kogito/main/pullrequest/kogito-runtimes.tests.kogito-runtimes@tmp/config1149521718633109494tmp -Dmaven.wagon.http.ssl.insecure=true -Dmaven.test.failure.ignore=true -nsu -ntp -fae -e -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false -Dmaven.wagon.httpconnectionManager.ttlSeconds=120 -Dmaven.wagon.http.retryHandler.count=3 -T 1C -Dvalidate-formatting -Prun-code-coverage dependency:tree  -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn -B. The process '/opt/tools/apache-maven-3.8.7/bin/mvn' failed with exit code 1[2023-02-14T08:34:10.376Z] [command]/usr/bin/docker system prune -f[2023-02-14T08:34:11.274Z] Total reclaimed space: 0B[2023-02-14T08:34:11.274Z] [INFO] Execution summary for kiegroup/kogito-runtimes[2023-02-14T08:34:11.274Z] # [BEFORE] [kiegroup/kogito-runtimes] export INTEGRATION_BRANCH=[2023-02-14T08:34:11.274Z] [INFO] OK [Executed in 0.246141 ms][2023-02-14T08:34:11.274Z]  [2023-02-14T08:34:11.274Z] # [BEFORE] [kiegroup/kogito-runtimes] bash -c "if [ ! -z '' ] && [ -f .ci/environments/update.sh ]; then .ci/environments/update.sh ""; fi"[2023-02-14T08:34:11.274Z] [INFO] OK [Executed in 6.445012 ms][2023-02-14T08:34:11.274Z]  [2023-02-14T08:34:11.274Z] # [COMMANDS] [kiegroup/kogito-runtimes] export MVN_CMD=`bash -c "if [ '' = 'true' ]; then printf 'deploy  '; else printf 'install'; fi"`[2023-02-14T08:34:11.274Z] [INFO] OK [Executed in 5.869513 ms][2023-02-14T08:34:11.274Z]  [2023-02-14T08:34:11.274Z] # [COMMANDS] [kiegroup/kogito-runtimes] mvn clean install  -s /home/jenkins/workspace/KIE/kogito/main/pullrequest/kogito-runtimes.tests.kogito-runtimes@tmp/config1149521718633109494tmp -Dmaven.wagon.http.ssl.insecure=true -Dmaven.test.failure.ignore=true -nsu -ntp -fae -e -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false -Dmaven.wagon.httpconnectionManager.ttlSeconds=120 -Dmaven.wagon.http.retryHandler.count=3 -T 1C -Dvalidate-formatting -Prun-code-coverage dependency:tree  -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn -B[2023-02-14T08:34:11.274Z] [INFO] NOT OK [Executed in<PHONE_NUMBER>88 ms][2023-02-14T08:34:11.274Z] [ERROR] The process '/opt/tools/apache-maven-3.8.7/bin/mvn' failed with exit code 1[2023-02-14T08:34:11.274Z]  [2023-02-14T08:34:11.274Z] # [AFTER] [kiegroup/kogito-runtimes] docker system prune -f[2023-02-14T08:34:11.274Z] [INFO] OK [Executed in 304.832133 ms][2023-02-14T08:34:11.274Z]  [2023-02-14T08:34:11.274Z]  [2023-02-14T08:34:11.274Z] # Uploading artifacts[2023-02-14T08:34:11.274Z] [INFO] Will not upload any artifacts in CLI environment[2023-02-14T08:34:11.274Z]  [2023-02-14T08:34:11.275Z] [ERROR] Failed to execute commands for kiegroup/kogito-runtimes[2023-02-14T08:34:11.275Z] [ERROR] Failed to execute mvn clean install  -s /home/jenkins/workspace/KIE/kogito/main/pullrequest/kogito-runtimes.tests.kogito-runtimes@tmp/config1149521718633109494tmp -Dmaven.wagon.http.ssl.insecure=true -Dmaven.test.failure.ignore=true -nsu -ntp -fae -e -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false -Dmaven.wagon.httpconnectionManager.ttlSeconds=120 -Dmaven.wagon.http.retryHandler.count=3 -T 1C -Dvalidate-formatting -Prun-code-coverage dependency:tree  -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn -B :[2023-02-14T08:34:11.275Z] [ERROR] The process '/opt/tools/apache-maven-3.8.7/bin/mvn' failed with exit code 1[Pipeline] }[Pipeline] // withCredentials[Pipeline] }[2023-02-14T08:34:14.583Z] Deleting 1 temporary files[Pipeline] // configFileProvider[Pipeline] }[Pipeline] // scriptPost stage[Pipeline] junit[2023-02-14T08:34:16.374Z] Recording test results[2023-02-14T08:34:22.274Z] [Checks API] No suitable checks publisher found.[Pipeline] archiveArtifacts[2023-02-14T08:34:22.481Z] Archiving artifacts[Pipeline] script[Pipeline] {[Pipeline] sh[2023-02-14T08:34:24.377Z] + rm -rf console.log[Pipeline] sh[2023-02-14T08:34:25.078Z] + 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/1968/consoleText[2023-02-14T08:34:25.078Z] + tail -n 300


Change the gem to be production ready

Hi @mephux,
We would like to use this gem for production purpose.
We have started a big refactoring to clean some old stuff and do unit-test.
https://github.com/Cyberwatch/ruby-nessus
=> Can you take a look or if you are no more interested to maintained this gem, could you give us the write access to the repository / rubygems.
Thanks,

@fwininger I gave you write access to the repo and I can also add you to the gem site

I'm open to everything I saw in your fork,

@mephux thanks for the begin, this gem is very helpful. I submit some PR tomorrow. We hope to have a new release at the end of next week.

@fwininger np, thanks! I also just added CI - I'll get you access.


Could you provide a RPM Package？

In wiki page，there is an example

sudo dpkg -i target/clickhouse-jdbc-bridge.deb
Could you provide a RPM package?

Could you try code from master branch? It will produce not only deb but also rpm package.


Title: Improving Footer UI Alignment and spacing

Initiative (Required)
GSSoC (Girl Script Summer of Code) 🌸
Is your feature request related to a problem? Please describe.
I have noticed a design inconsistency or opportunity for improvement in the footer section, as shown in the attached screenshot.

Describe the solution you'd like.
Improve spacing and alignment of the "Quick Links" section. Increase the visibility of social media icons, making them more balanced with the rest of the content.
I am willing to work on this please assign me
Add any other context or screenshots about the feature request here.
No response

@Raj-banerjee25 Assign me this issue..

Can you please assign me this issue @Raj-banerjee25

I am the  mentor of this project.
@Raj-banerjee25 Hello
I appreciate your pull issue, but it is not required!
Kindly open new concept of pull issue..
Thank you!!
@Kushal997-das kindly close this issue!!!

Can you please assign me this issue @Raj-banerjee25

@charmi2109 Hello
Kindly create your own pull issue, if any problem then tell me!!
Thank you!

@Raj-banerjee25 Assign me this issue..

@PriyanshuValiya Hello
Kindly create your own pull issue, if any problem then tell me!!
Thank you!


build: fix travis required tests not running

Fixes that the travis_required CI mode isn't running. This mode is important for Firefox and Chrome testing.

@jelbourn Fixed the test failure in Firefox 57. Everything is green now!


question about license

Hello, i am thinking about using this lib in my app however im not sure if the license is right - version 2.0 should be MIT according to you but from what i can see you are using these files inside:
qtx11extras.cpp
qtx11extras_p.h
qwinregistry.cpp
qwinregistry_p.h
and these files are internal qt files released under either commercial / lgpl ver.X / gpl ver.X  licenses - and those licenses cant be mixed(with MIT) - so in reality it makes your whole library gpl / lgpl.
i think it should be stated somewhere - as its very important - im trying to avoid lgpl where possible.
is there a way to kick-out that code? or any plans? to make it truly MIT lib?

Hi, sorry for the confusion.
The QWinRegistry class was introduced in Qt 5.14, and the QX11Info class was introduced in Qt 5.1. The QX11Info class in Qt5 was in a separate module called Qt X11Extras, and this module was removed in Qt 6.0 but the content of it was added back in Qt 6.2 to QtCore as a private feature. I've checked the source code of it from Qt 5.15.2 and Qt dev (currently will be Qt 6.4), and found that the code was not touched, so in reality the QX11Info class was just moved to a different place. And I use preprocessor macros to control whether to use the copy in this project or the original one in Qt. The only chance to make qwinregistry_p.h and qwinregistry.cpp compile into this library is (1) building for the Windows platform and (2) you are using a Qt of some version lower than 5.14. The condition for qtx11extras_p.h and qtx11extras.cpp is (1) building for the Linux platform and (2) you are using a Qt of some version below 6.2 (including Qt5). I didn't actually read the content of the GPL/LGPL license text, but I guess it won't break our MIT license if the source code are not compiled into our library?

is there a way to kick-out that code?

Of course. The QWinRegistry is just a convenient helper class to access Windows registry, we can replace it with the public QSettings instead, if you really want to get rid of that code. And we can get rid of qtx11extras_p.h and qtx11extras.cpp by using Qt's own code, for example, for Qt5 we can just use the X11Extras module, for Qt 6.2 and greater we can use the QtCore feature directly. But there are no good replacement for Qt versions between 6.0 and 6.2. However, QX11Info is just a conenient helper of some QPA functions, we can totally remove the usage of QX11Info by calling the QPA functions directly by ourself.
Currently there are no plans to do the above migration process, but you can make a PR for this and I'll surely accept it.

OK, I think I may have some time next week. I'll do the above migration in next week, if I have enough time. Anyway, thanks for your suggestion about the license issue!

All the bundled Qt classes have been removed in main branch, I'll release the 2.1 version based on the latest code of the main branch soon.


WindowCovering Example

Hi there, has anyone experience how to setup a window covering device.
I tried to modify the LightOnOff Example, but the window covering device always shows as "Not responding". Maybe my initial config is invalid or the update process has to be done differently.
I also could not find any example online.

Have you figured it out?

Unfortunately not

I may look at this. Which Matter Controller are you using?

HomePod mini as Border Router
ESP32 as controller (https://www.amazon.de/dp/B071P98VTG?psc=1&ref=ppx_yo2ov_dt_b_product_details)

Our window shade controller just bit the big one and i was going to replace it with a matter/eps32 by modifying the LightOnOff Example (Matter project # 3 for me :)  ) through google home wifi.  Anybody have luck moving this forward?

Any luck getting it to work?

@weidingerc
The hint worked with my code, the Matter device is not marked with "Not responding".
You will find this already incorporated in my code.
https://github.com/espressif/esp-matter/issues/343#issuecomment-1531494497
Unfortunately my programming skills are not good, so I have difficulties to finalize my project.
I want to control belt winders, but I don't know how to redirect the Matter functions to my code.
Maybe someone can give me a push in the right direction.
Here is my current code:
https://github.com/Robothaler/BeltWinder-Matter/tree/dev

@Robothaler Thanks a lot, I got it working with the additional control clusters in your code.
But what I still did not manage was to just have a "Default lifting" window covering that just can "open/close" and nothing more.

@weidingercI'm pleased that you're now one step further.
With my code, the Apple Home and EVE app only show me a roller shutter with up/down and stop function.
You may also be interested in how the WindowCovering type can be changed.
Take a look at the following entry:
https://github.com/espressif/esp-matter/issues/280#issuecomment-1488907563
The required line is the following:
window_covering_device::config_t wcd_config(static_cast<uint8_t>(chip::app::Clusters::WindowCovering::EndProductType::kRollerShutter));
How do you control your roller shutter? In other words, how do you transfer the position change to your code? Frankly, I have not yet understood the Matter functions.
In my code, I want to pass the new position from the Home app to my newPosition function to the newPercentage variable. Maybe you can help me at this point.
Also, I can't see any custom DEBUG output in the serial output.
I have already changed this to the following format:
ESP_LOGD(TAG, "window_covering_device cluster created with cluster_id %d", cluster);
I still can't see the output!

@Robothaler Thanks, I‘ll try this different window covering config once I have time again ;-P

@weidingercI'm pleased that you're now one step further. With my code, the Apple Home and EVE app only show me a roller shutter with up/down and stop function. You may also be interested in how the WindowCovering type can be changed. Take a look at the following entry: espressif/esp-matter#280 (comment)
The required line is the following: window_covering_device::config_t wcd_config(static_cast<uint8_t>(chip::app::Clusters::WindowCovering::EndProductType::kRollerShutter));
How do you control your roller shutter? In other words, how do you transfer the position change to your code? Frankly, I have not yet understood the Matter functions. In my code, I want to pass the new position from the Home app to my newPosition function to the newPercentage variable. Maybe you can help me at this point. Also, I can't see any custom DEBUG output in the serial output. I have already changed this to the following format:
ESP_LOGD(TAG, "window_covering_device cluster created with cluster_id %d", cluster); I still can't see the output!

This line you suggested only leads to "Device not responding" again. I guess I'll stay at the Glider shades from 0 to 100% to open and close my shades.

I have also had some luck with the matter window covering device -- A simple system controlling multiple shades, one at a time, using a single esp32, a timer for the intermediate shade positions, and limit switches for full open/close. I'm not a programmer, I only play one in retirement ;)
I haven't had a chance to work carefully through the recent comments, yet for me stumbling upon the "int val->val.i" in the static esp_err_t on_attribute_update routine was the key moving from the "bool val->val.b" in the two existing on/off device examples to a variable slider for the shade positions. val.i returns the % closed (which is 10000 - the % open value in the google home slider). Will try the "val->val.u16" as suggested as that seems more logical and should match the GH slide.
Neither the get- or set- attributes, nor the matter shade functions are working for me either - it would be great to learn more about the matter shade controller's inner workings...
However, The current problem I need to solve for intermediate shade positions before implementation is: when moving the slider slowly in the GH app, I am getting multiple values for the open % (val->val.i) along the way. Thus, moving from say 20% to 80% open is returning intermediate values such as 42%, 57%, and 67% before my finger stops moving the slider at 80%. It shouldn't be too hard to figure this out with a simple timer.
Having said that, I wonder if there is a matter function out there that takes care of this automatically?? For full open/close of the shades, the limit switches work.
I thought it might be useful to attach my minimalist Arduino ide code skeleton which commissions a two shade slider group in GH. Perhaps the experts can chime in what matter functions are missing and how to use them... Minimal_window_covering.zip

@Sustainable-Me I have solved the problem of intermediate values when dragging the slider with a new function. The incoming values are buffered there and forwarded to the function for determining the position after a filter time. This works quite well for my case. Here is my current code, of course you still have to create the appropriate global variables.
` // buffering new target values
void bufferNewPosition() {
unsigned long currentTime = millis();
// The very first new target value received
if (newPercentageReceived && !bufferedValueSaved) {
    bufferedPercentage = newPercentage;
    DEBUGPRINTLN2("[BELTWINDER] bufferNewPosition: New percentage received - " + String(newPercentage) + "%");
    DEBUGPRINTLN2("[BELTWINDER] bufferNewPosition: First value buffered - " + String(bufferedPercentage) + "%");

    bufferedValueSaved = true;

    lastUpdateTime = currentTime;
    DEBUGPRINTLN2("[BELTWINDER] lastUpdateTime was 0 will be changed to: New timestamp - " + String(lastUpdateTime) + "ms");
    return;
    }

// A new target value received within filter duration
if (newPercentageReceived && bufferedValueSaved && currentTime - lastUpdateTime <= filterDuration) {

  if (newPercentage == bufferedPercentage) {
    DEBUGPRINTLN2("[BELTWINDER] bufferNewPosition: New percentage is equal to buffered Percentage - " + String(newPercentage) + "%");
  } else {
    bufferedPercentage = newPercentage;
    bufferedValueSaved = true;
    return;
    }
} else if (newPercentageReceived && bufferedValueSaved && currentTime - lastUpdateTime > filterDuration){
  // Time has expired, use the last buffered value
    DEBUGPRINTLN2("[BELTWINDER] bufferNewPosition: Time limit for buffering exceeded. Use last buffered value for new position.");
    filteredPercentage = bufferedPercentage;

    DEBUGPRINTLN2("[BELTWINDER] bufferNewPosition: Filtered percentage - " + String(filteredPercentage));

    lastUpdateTime = 0; // Set lastUpdateTime to 0 for the next update
    newPercentageReceived = false;
    bufferedValueSaved = false;
    newPosition(filteredPercentage);
}

}`

I made a Matter device with 3 windowCovering endpoints. It controls 3 Somfy blinds and I can open, close at set to x% opening from Google Home. It is build using Arduino IDE with esp32_arduino_matter library.
It works fine, but II do have a few problems. The conversion from the matter device to Google Home (and other apps) "Up" to be position 100% and down  to be 0%.  So when I want to position to 20% open, I get 80% open.
I tried to do a manual convertion by calculating the opening percentage top 100-value. This works, but on power up, all blinds go down to fully extended position. not good en a power failure situation when the storm is on!.
Either I need to invert the action between the matter device and google home, or I need to be able to set start position to fully extended and then calculate 100-value.
Any idea is apreciated.
Regards
erik

@palsbo
Hi,
you can find the solution in my repository:
BeltWinder-Matter)
You have to use "Mode" and change the motordirection:
// Attribute: Id 23 Mode
  set_window_covering_mode(window_covering_endpoint_id, Mode::kMotorDirectionReversed);

To submit the new mode I've created this function:
void set_window_covering_mode(chip::EndpointId endpoint, chip::app::Clusters::WindowCovering::Mode newMode)
{
    esp_matter_attr_val_t modeValue;
    modeValue = esp_matter_int8(static_cast<int8_t>(newMode));

    esp_err_t result = attribute::update(window_covering_endpoint_id, WINDOW_COVERING_CLUSTER_ID, WINDOW_COVERING_ATTRIBUTE_ID_MODE, &modeValue);

    if (result == ESP_OK)
    {
        DEBUGPRINTLN2("[BELTWINDER] Window covering Mode updated successfully");
        chip::DeviceLayer::PlatformMgr().LockChipStack();
        DEBUGPRINTLN2("[BELTWINDER] Current Mode: "); ModePrint(ModeGet(window_covering_endpoint_id));
        chip::DeviceLayer::PlatformMgr().UnlockChipStack();
    }
    else
    {
        DEBUGPRINTLN2("[BELTWINDER] Failed to update window covering Mode");
        // Handle error if needed
    }
}

I hope this will help you.

Thank your for quick response. I will try  it.
Best regards
Erik


Implement Global Cache (Japan)

Task
Progress
Date

Design and develop a GC
100%
March 2023

Subscribe to GBs
100%

Coordinate with other GBs and GCs
100%

Download data from WIS2 nodes
100%

Provide metrics on system performance and data availability
0%

Risks and Issues
Downloading traffic volume and latency should be monitored to achieve enough performance of GC
It is difficult to estimate costs of operational system to be operational in 2025


udp question

I'm seeing a strange behavior and I must be doing something incorrectly. For an incoming udp server I'm able to get the first request and read it but any subsequent requests never make it to the onRead event handler.
Config:
udp config: gain.Config{Architecture:0, AsyncHandler:false, GoroutinePool:false, CPUAffinity:false, ProcessPriority:false, Workers:1, CBPFilter:true, LoadBalancing:0, SocketRecvBufferSize:0, SocketSendBufferSize:0, TCPKeepAlive:0, LoggerLevel:0, PrettyLogger:true, MaxSQEntries:0x4000, MaxCQEvents:0x4000}

i added some debug logs and see it ending in: https://github.com/pawelgaczynski/gain/blob/41f1e60a18da7a92a15f377c52e4f7b7d78cf796/read_write_worker.go#L186
It appears to have the flag set for:
IORING_CQE_F_SOCK_NONEMPTY
2:16AM INF Starting worker loop... component=worker fd=7 ring fd=8 worker index=0
2:16AM DBG Process event Res=51 component=worker req flag="read flag" req key=1 ring fd=8 user data=4611686018427387905 worker index=0
2:16AM DBG Bytes read component=worker count=51 fd=7 ring fd=8 worker index=0
2:16AM DBG here1 component=worker n=51 ring fd=8 sendRecvMsg=true worker index=0
2:16AM DBG sync Handler component=worker ring fd=8 worker index=0
onRead, input size: 51
leaving onRead, input size: 51 buffered: 0
2:16AM DBG Process event Res=135 component=worker req flag="write flag" req key=2 ring fd=8 user data=2305843009213693954 worker index=0
2:16AM DBG Bytes writed component=worker count=135 fd=7 ring fd=8 worker index=0
2:16AM DBG Process event Res=51 component=worker req flag="read flag" req key=1 ring fd=8 user data=4611686018427387905 worker index=0
2:16AM DBG Bytes read component=worker count=51 fd=7 ring fd=8 worker index=0
2:16AM DBG here1 component=worker n=51 ring fd=8 sendRecvMsg=true worker index=0
2:16AM DBG w.addReadRequest2 component=worker conn.isClosed=false ring fd=8 worker index=0
2:16AM DBG Process event Res=51 component=worker req flag="read flag" req key=1 ring fd=8 user data=4611686018427387905 worker index=0
2:16AM DBG Bytes read component=worker count=51 fd=7 ring fd=8 worker index=0
2:16AM DBG here1 component=worker n=51 ring fd=8 sendRecvMsg=true worker index=0
2:16AM DBG w.addReadRequest2 component=worker conn.isClosed=false ring fd=8 worker index=0

Am I missing a step?  I'm trying this on a conversion from gnet so maybe I have some assumption in the handling.

i also checked the c.InboundBuffered() which was 0 right before the onRead() returns.


Update Docker README

PR Summary
As of now, all community images have been moved to the PowerShell/PowerShell-Docker

cc @TravisEz13
PR Context
#8990 removed the last community image and this section is in the README of the linked repository.

PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Change is not breaking
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[x] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

[x] Add [feature] to your commit messages if the change is significant or affects feature tests

Comment to make sure this doesn't become stale.


Voting webapp for høstcamp

Acceptance criteria:

[ ] Webapp for voting (without inlogging)
[ ] LED element for showing vote statistic

Note, this should be used as the backend: https://github.com/bcc-code/bcc-media-utils/tree/main/counter
It can handle basically anything you throw at it with a small VM.

Details after meeting with Fredrik Floor:
1 Question
4 Answers
Results in "admin" no need for nice presentations, will be copied to PP
Can be open all the time, needs a reset button.

Status:

[ ] Webpage implemented and approved by Fedrik Floor
[ ] Translations ready for translators
[ ] Translations Imported
[ ] Redirect on re-visit

Ready tested, but disabled in code

[ ] Submit data to server

Ready, tested locally. Needs correct server IP/DNS

[ ] Counter server

Software ready, needs to be deployed to a VM (< 1h work)


NPM scripts explorer doesn't show all scripts in multiroot workspace

VSCode Version: 1.25.1
OS Version: Arch Linux x64

Steps to Reproduce:

create a multiroot workspace with 2 folders
add package.json to each folder containing npm scripts, some of them having the same name in both folders

Expected results: all npm scripts for both folders are shown
Actual results: all npm scripts for the first folder are shown; for the second folder, only npm scripts that have a name not occurring in the first folder are shown
Does this issue occur when all extensions are disabled?: Yes

I checked the listed issues and none of them seems to be a duplicate of this one.

This looks like a duplicate of #54085.
This is the interesting information

Actual results: all npm scripts for the first folder are shown; for the second folder, only npm scripts that have a name not occurring in the first folder are shown

Closing as duplicate of #54085


pip3

If you want to use python3+ to install the packages you need to use pip3 install packageName, please update.
Tks.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 30a20df2-727c-1afd-2b87-836ea1ea4f7a
Version Independent ID: 157fc262-fb1f-f12d-0890-e90119feb444
Content: Create a bot using Bot Framework SDK for Python - Bot Service
Content Source: articles/python/bot-builder-python-quickstart.md
Service: bot-service
GitHub Login: @emgrol
Microsoft Alias: kamrani

Hi @cfl81 , pip vs. pip3 is installation specific and out of the scope our documentation. Closing this issue since there are no documentation issues.


fix: attempt to fix the failing legacy test

lets see if this fixes the things. Otherwise we'll just remove this test for now.

Yup, almost as expected, no F* luck... with such tests...


Add validation to push package

Purpose

$Subject

Fixes #33696
Approach

Implement new method for validating push package and call the relevant central endpoint inside it.

Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[x] Added necessary tests

[x] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

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


Website design suggestions

Kind of issue

[X] Feature

Description
Would it be possible to add an on-site help page on how to use the site?
Also, maybe make the site's footer and header floating on top of the search results?

Header is always on top of the search results. Are you experimenting a different behaviour?
Footer is too big to maintain in the screen always and is not clear what benefit could bring that.
The site seems very straitghtforward and simple to understand it so I think that a help page is not neccesary. What you don't understand?

Closing due to lack of additional information. Feel free to reopen it if you deem necessary.


Tmp release 3.4.1

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 3 committers have signed the CLA.:white_check_mark: IlliaDaliek:white_check_mark: Igor-Gorchakov:x: TotoroDevEbscoYou have signed the CLA already but the status is still pending? Let us recheck it.


Some images built from the same Dockerfile have different layers

This repo has several images which have multiple tags; for example, 1.0.1-runtime and 1.0-runtime point to the same image.  For some images, we are assigning the same image multiple tags, either by the build hooks or the Nano Server VSTS build definitions.  For other images, we have multiple entries in the Docker Hub Build Settings for the same Dockerfiles to be built with different tags.
In the former case, the image digests are the same (meaning the tags point to the exact same image). In the latter case, the expectation is that the images should have different digests but contain the same layers.  However, this is currently not the case for some images; for example, microsoft/dotnet-nightly:1.0-sdk-msbuild and microsoft/dotnet-nightly:1.0.1-sdk-msbuild contain three different layers, which can be seen with the docker inspect command.  This means that users who pull both tags will have separate layers for them on their machines, which takes up a substantial amount of extra space and increases download times.

Docker Hub auto-build functionality does not have support for multi-tagging an image.  Currently multiple build rules are defined but this results in images that don't share layers.  To fix this, build hooks must be used.


feat: fixing - feedback - Default view for Stars and Forks graph should be time-series

Description
Fixes  #3862
I have replaced the previous bar charts with area charts in the star graphs. I have submitted this as a draft PR. If it works well, I will implement this change throughout.
Related Tickets & Documents

Fixes #3862
Mobile & Desktop Screenshots/Recordings

Steps to QA

Tier (staff will fill in)

[ ] Tier 1
[ ] Tier 2
[ ] Tier 3
[ ] Tier 4

[optional] What gif best describes this PR or how it makes you feel?

Should I proceed with creating an area graph under the time series for each plot on the repo page (Stars and forks)? @jpmcb @BekahHW

cc @isabensusan - any thoughts on the design here?

Hey everyone,
Should I proceed with the proposed idea?

@SURAJ-SHARMA27 I believe the original issue to be resolved was just changing the default. We can revisit changing the style of the chart separately.

@SURAJ-SHARMA27 thanks for your contribution! But like @brandonroberts mentioned, if you take a close look at the original issue #3862 the goal was to just change the default view for the stars and forks charts from Daily to History.
We are not currently looking to update the design of these charts, so I'll be closing this PR, but if you want to tackle changing the default view in a different PR you are welcome to do so!

Okay, I understand. Should I just convert the stars and forks graph into a time-series graph as mentioned in the original issue?

I'm not sure where we landed on this @open-sauced/design @open-sauced/engineering.

I'm going to go ahead and close this for now. Feel free to reopen it if you want to continue working on this @SURAJ-SHARMA27.