Add --info option to display current settings

@ericof For the future -- for quick review of a new feature like this it would be helpful to have a screenshot in the pull request


[fix: typing] Explicitly rexport KeyArray in jax.random

Explicitly reexports PRNGKeyArray as KeyArray in accordance with PEP 484
See also: https://github.com/python/mypy/issues/11706

Tiny fix that improves compatibility with strict linters (mypy, pylint)

Thanks!


Make the game Full-Screen by default

Make the game a full-screen window by default . Also add a custom quit button on the window to close and exit the game.

me!

go ahead @Samantha-Susan-John

can i get this?

Please assign this to mee

can i work on this?:) bored

Can I be asigned? I'd like to work on this


fix: standardize installation across demos

Related Issues/PRs

#xxx
What changes are proposed in this pull request?
Briefly describe the changes included in this Pull Request.
How is this patch tested?

[ ] I have written tests (not required for typo or doc fix) and confirmed the proposed feature/bug-fix/change works.

Does this PR change any dependencies?

[ ] No. You can skip this section.
[ ] Yes. Make sure the dependencies are resolved correctly, and list changes here.

Does this PR add a new feature? If so, have you added samples on website?

[ ] No. You can skip this section.
[ ] Yes. Make sure you have added samples following below steps.

Find the corresponding markdown file for your new feature in website/docs/documentation folder.
Make sure you choose the correct class estimators/transformers and namespace.
Follow the pattern in markdown file and add another section for your new API, including pyspark, scala (and .NET potentially) samples.
Make sure the DocTable points to correct API link.
Navigate to website folder, and run yarn run start to make sure the website renders correctly.
Don't forget to add <!--pytest-codeblocks:cont--> before each python code blocks to enable auto-tests for python samples.
Make sure the WebsiteSamplesTests job pass in the pipeline.

/azp run

Codecov Report

Merging #2020 (4beb3df) into master (094c180) will decrease coverage by 74.57%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master    #2020       +/-   ##
===========================================
- Coverage   87.05%   12.48%   -74.57%
===========================================
  Files         306      306
  Lines       16064    16064
  Branches      840      840
===========================================
- Hits        13984     2006    -11978
- Misses       2080    14058    +11978

see 291 files with indirect coverage changes


don't trim whitespaces when parsing markdown contents in julia demos

The following content is a valid markdown content, but the indentation information is lost here because whitespaces are trimmed
# !!! note
#    Although `Gray.(img)` could infer the storage type as well, `ConvertEltype(Gray)` on the other
#    hand, does not do so. To get better performance, it is recommended to specify the storage type
#    when you use this operation, e.g., `ConvertEltype(Gray{Float32})`.

Literate requires a #  prefix, so we have to type five spaces here to get a correctly rendered note block.
I mistakenly typed only four spaces here. 😢


Fix building _nvx_utf8validator extension on non-x86 systems

x86intrin.h does not exist on such systems

thanks! looks good .. for now .. this NVX stuff isn't finished yet in any case

Hmm, I've enabled it in the Arch Linux package for some time. Please tell me if it is better not to do so.

Please tell me if it is better not to do so.

It's good to include the pieces that NVX already provides, because even though those pieces are not yet "complete" (wrt my original plan), the pieces which are there, e.g. the UTF8 validator, have pretty good test coverage https://github.com/crossbario/autobahn-python/blob/master/autobahn/nvx/test/test_nvx_utf8validator.py
IOW: the NVX UTF8 validator can indeed be used in production code (in my eyes / to my knowledge)
what is missing (I do have code .. somewhere ..) is: websocket XOR masking using intrinsics. anyways, I think your Arch package is good as it is! that is, from a quick glance.
however, looking at all the dependencies you have on the Arch package pointing to other Python modules also packaged as Arch packages: looks pretty good! I'm saying this even though I'm usually using Python packages in a venv, directly from PyPI.
One thing I am wondering though: do you provide autobahn[xbr] ? this sadly has some I guess "annoying" dependencies https://github.com/crossbario/autobahn-python/blob/201eeb2bcf9808a705b26ef35c028015f378661e/setup.py#L115
The excuse is, this is pretty cutting edge stuff with Ethereum dependencies, and this is a fast, unsettled universe ..;) Anyways, just mentioning/wondering ..

It's good to include the pieces that NVX already provides, because even though those pieces are not yet "complete" (wrt my original plan), the pieces which are there, e.g. the UTF8 validator, have pretty good test coverage https://github.com/crossbario/autobahn-python/blob/master/autobahn/nvx/test/test_nvx_utf8validator.py
IOW: the NVX UTF8 validator can indeed be used in production code (in my eyes / to my knowledge)

Thanks a lot for detailed comments! I will keep nvx enabled in that package.

however, looking at all the dependencies you have on the Arch package pointing to other Python modules also packaged as Arch packages: looks pretty good! I'm saying this even though I'm usually using Python packages in a venv, directly from PyPI.

Thanks! I often use venv as well. IMO either has pros and cons :)

One thing I am wondering though: do you provide autobahn[xbr] ? this sadly has some I guess "annoying" dependencies

The excuse is, this is pretty cutting edge stuff with Ethereum dependencies, and this is a fast, unsettled universe ..;) Anyways, just mentioning/wondering ..

Nope, dependencies appear only in autobahn[xbr] are not included. The reason is indeed that keeping track with so many Ethereum-related packages is difficult. Hopefully I can get time to find a way for managing so many dependencies efficiently soon :)


Update Sample files to reflect the latest version of Wet

Currently the samples pages are not up to date with WET.

[x] Exit script should be using the new exitscript feature wet-boew/cdts-sgdc#180

The new exitscript feature is now being used, with the latest 4.0.39 update.


Create GIFs showing the use of ViroCon and viroconcom

One GIF should show how one uses ViroCon and one GIF should show how to use viroconcom.
These GIFs should be included in ViroCon's readme.md

Done for viroconweb.


Should we drop suppoprt for rails 3?

Continue from #277

Let's keep rails 3.2 support until something major breaks


Docs Changes Needed from dbt-adapters Issue #327

At a minimum, update body to include a link to the page on docs.getdbt.com requiring updates and what part(s) of the page you would like to see updated.

hey @QMalcolm , i was reviewing this dbt-adapters PR and this core pr -- am i correct in thinking that the following needs to be added to the behavior flag doc:

require_batched_execution_for_custom_microbatch_strategy flag defaults to False, which will raise a deprecation warning. Set it to True to allow custom microbatch strategies (like get_incremental_microbatch_sql) to use batched execution.


Partial dataset loading for NLU

Proposed changes:

described here: https://github.com/RasaHQ/rasa/issues/6836

Status (please check what you already did):

[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog (please check changelog for instructions)
[ ] reformat files using black (please check Readme for instructions)

Hey @Ghostvv good stuff and wow this is one big boi of a PR. I know you linked the issue where initial discussions around this issue took place. However there are many lists of checkboxes that seem to not have been used consistently, and it's difficult to know what is really relevant here.
If you could provide a high level overview / conceptual description of the things you actually ended up implementing, it would really help determining where to start with reviewing this big PR

@twerkmeister did you take a look at the linked doc: https://docs.google.com/document/d/1dwKfdju5ZqhOQtURLF3-eU3PdxvdlyXafPHE_0sLPzI/edit?usp=sharing?

@Ghostvv really appreciate your efforts here. It looks like it's been a lot of work and it's been challenging. Yet, that should also make you realize that reviewing the PR is also challenging.

@twerkmeister did you take a look at the linked doc: https://docs.google.com/document/d/1dwKfdju5ZqhOQtURLF3-eU3PdxvdlyXafPHE_0sLPzI/edit?usp=sharing?

I had a look now and I learned something about the ideas that were floating around. However, it's an 'ideas' document and it's not obvious what parts of the things you originally discussed you ended up implementing. I wish you would provide some more context in form of a summary of the current status. Otherwise it's difficult to think things through and judge whether we are moving in a good direction, not having high level context to guide one's attention as a starting point.
For example, I wonder:

This pull request seems to be only part of the full solution. What parts and key ideas are included in this PR and which have been left out? And why?
What is the pathway forward to the full solution?
What is the rational for merging this into main at this stage?
How come you decided for managing two separate data set representations and training styles? TrainingDataFull could be just a special case of chunked datasets, for number of chunks = 1.
Why setting number of chunks instead of the somewhat more dataset-independent concept of examples per chunk?
What will happen with the components that raise the RasaTrainChunkException with message "This method should neither be called nor implemented in our code." There are 5 of these (intent classifiers and entity extractors). Does this mean that we don't intend to support the chunk training methods for these?
A core part of this PR seems to be the caching of featurized data to hard disc to save memory. Potentially this a special case in the the general Rasa 3.0 pipeline / computation graph discussions that @wochinge, @joejuzl are having - has there been any exchange on that front?

More detailed (secondary in terms of importance) code Questions / notes:

Is the randomization procedure of RasaDataChunkFileGenerator random enough? Looks to me that if you have 50k examples and split into 4 chunks, you'd still have buckets of 12.5k items each that will be generated in the same order in every epoch. Either we need to give some hints to setting a good chunk size or we could shuffle big chunks internally again after loading.
There needs to be more documentation / better error messages for when components not support chunked training. Imagine someone having memory issues with some pipeline, discovering this option, switching to it and then just getting a RasaTrainChunkException('This method should neither be called nor implemented in our code').
naming of _max_batch_number_per_chunk related things in the RasaDataChunkFileGenerator are somewhat confusing. It's not a list of number of batches per chunk but a cumulative sum of batches across the chunks

This pull request seems to be only part of the full solution. What parts and key ideas are included in this PR and which have been left out? And why?

This is the full solution for nlu. The next part will be core. We decided to split them to make the sizes of the PRs smaller

What is the pathway forward to the full solution?

it is described in last 2 comments in the linked issue: https://github.com/RasaHQ/rasa/issues/6836

What is the rational for merging this into main at this stage?

this PR incorporates partial dataset loading for nlu, since core is build upon NLU, it makes these changes independent

How come you decided for managing two separate data set representations and training styles? TrainingDataFull could be just a special case of chunked datasets, for number of chunks = 1.

I don't think, it can. TrainingDataFull contain more data and helpers like responses, lookup tables etc

Why setting number of chunks instead of the somewhat more dataset-independent concept of examples per chunk?

I don't know, it was just a decision to make. We can change it to examples per chunk if you think it is better, but I expect it'll be hard for users to estimate number of examples

What will happen with the components that raise the RasaTrainChunkException with message "This method should neither be called nor implemented in our code." There are 5 of these (intent classifiers and entity extractors). Does this mean that we don't intend to support the chunk training methods for these?

they shouldn't be present in the config if users want/need to train in chunks

A core part of this PR seems to be the caching of featurized data to hard disc to save memory. Potentially this a special case in the the general Rasa 3.0 pipeline / computation graph discussions that @wochinge, @joejuzl are having - has there been any exchange on that front?

it started before Rasa 3.0 pipeline / computation graph discussions. But yes it is linked. I'd say the core part is make tf model load data from files on the fly

Is the randomization procedure of RasaDataChunkFileGenerator random enough? Looks to me that if you have 50k examples and split into 4 chunks, you'd still have buckets of 12.5k items each that will be generated in the same order in every epoch. Either we need to give some hints to setting a good chunk size or we could shuffle big chunks internally again after loading.

yes, but shuffling data between chunks would require additional persist of chunks from inside tf training. I suggest to pursue it separately in follow up PR, if you think it is necessary

There needs to be more documentation / better error messages for when components do not support chunked training. Imagine someone having memory issues with some pipeline, discovering this option, switching to it and then just getting a RasaTrainChunkException('This method should neither be called nor implemented in our code').

could you please make a suggestion in code review?

naming of _max_batch_number_per_chunk related things in the RasaDataChunkFileGenerator are somewhat confusing. It's not a list of number of batches per chunk but a cumulative sum of batches across the chunks

could you suggest a better name?

The new training procedure is a specialized solution suited to selected components. Other components that might also suffer from large memory requirements have been excluded from this training procedure for unspecified reasons.

the reason is that it is not obvious how some ML algorithms like CRFEntityExtractor can support training on the files

From a user's point of view, it isn't obvious what components support the new training procedure and which don't.

that is the documentation issue, that is not merged yet

Maintenance of two training procedures increases complexity of the components.

yes it is the nature of this ML task

Each training procedure has slightly different preparatory steps that are done with the data

yes, it happens because majority of our components are drastically different from each other

For example, surprisingly, the original training procedure of the DietClassifier, that operates on the full dataset in memory, now calls prepare_partial_training, although this naming points directly to the opposite training procedure.

that's not the case. prepare_partial_training in DietClassifier doesn't contain the training.

To me, this pull request has the quality of an experiment/prototype.

that's not for me to decide

I am not convinced that a more elegant and generic design does not exist

it exists, but I don't think it is possible to achieve within current rasa oss architecture

Why do components need to know whether their training data is stored in memory or on disc in separate files?

because the training loop significantly differs in these cases

Whether that stream comes from memory, from hard disc, or from the cloud shouldn't matter.

it does matter, because it changes how batching is implemented and which classes are used to perform batching

If a component needs to collect some dataset-wide metadata first, it can consume the stream twice

that is what we're doing

Such a solution wouldn't suffer any of the drawbacks of the current proposal mentioned before.

I don't see the difference in your proposal, except that I don't think you have taken into account changes needed to internal training loop of ML components

@twerkmeister I agree that this PR has some qualities of being a prototype. The problem is that rasa architecture doesn't suit this feature. Maybe, it makes sense not to merge it, but use it as a template for 3.0 major refactor? cc @wochinge @joejuzl

Maybe, it makes sense not to merge it, but use it as a template for 3.0 major refactor? cc @wochinge @joejuzl

@joejuzl and I looked into how partial training could fit into the new architecture yesterday. This PR was already very insightful for us, e.g. the fact that DIET needs access to all chunks to shuffle them after each epoch. We've also figured that we can most probably do without the prepare step. Our plan yesterday was very close to the current implementation (separate train_on_chunks method on Components. Note that we rather focused upon general feasability of the new architecture - definitely worth giving it another thought when creating the actual plan.
Thanks for your comments, Vova and Thomas! They are super high quality, concise and helpful!

most probably do without the prepare step

how would you achieve that? do you plan move model and label data creation out of diet?

the reason is that it is not obvious how some ML algorithms like CRFEntityExtractor can support training on the files

It's true, that CRFEntityExtractor will build some representation of the entire dataset internally. Yet, I think we can save roughly 50% memory if we didn't hold the entire featurized dataset in memory on top of what the crf extractor is doing. When I was fixing the memory leak in that component recently, I was using a dataset with about 60k sentences, which consumed about 4GB by itself when featurized with 300 dimensional vectors from spacy. When the CRF training started, the crf - internal representation took another 4 GB or so. Makes 8GB in total. If we have a way where we don't keep the whole data set in memory we could save around 4GB of that. Obviously not perfect, and there will be limits at some point, but 50% saving isn't bad.

yes it is the nature of this ML task

I think we were talking past each other here. Yes, ML is complicated, but what I am saying is that we shouldn't just add additional complexity on top through our engineering/design choices.

that's not the case. prepare_partial_training in DietClassifier doesn't contain the training.

I was saying that the "training on the full dataset" calls prepare partial training, which is confusing. I wanted to underline that managing two separate training procedures will become very tiresome very fast.
https://github.com/RasaHQ/rasa/blob/9e731d54e883fee5521a677b4aef4ec60f2af6f0/rasa/nlu/classifiers/diet_classifier.py#L895-L907

because the training loop significantly differs in these cases

it does matter, because it changes how batching is implemented and which classes are used to perform batching

I don't think this is the case. From my understanding, what most components are doing is iterating over a stream of messages, preprocessing them, and training on them. It doesn't really matter what happens behind this interface of a list or stream of messages. They could be kept in memory, they could be kept on disc, they could be downloaded from the cloud, they could just be generated on the fly. A component that just consumes a stream of messages, doesn't need to care. If a specific batching procedure is needed by a component, that component can take care of that. If it wants batches of 32, it can just take 32 Messages out of the stream and do its thing. Shuffling and the like would have to happen where the stream is managed.

I don't see the difference in your proposal, except that I don't think you have taken into account changes needed to internal training loop of ML components

I don't really see why you couldn't just keep the normal TrainingData class and instead of it managing the examples as a list in memory it manages some data on the hard drive, maybe with some shuffling when needed etc. From the outside you are just asking for the nlu_examples as before, and you wouldn't notice that anything has changed from the outside. I think this way is much more generic, works for all components, results in a single training procedure per component, and probably doesn't require as much code changes.
What are some of the things that I am overlooking here with respect to the training loop?

I think we can save roughly 50% memory CRFEntityExtractor

that's a completely different problem that we don't try to address in this PR

I was saying that the "training on the full dataset" calls prepare partial training, which is confusing.

then I'd say it's just the matter of naming and comments. Logic-wise, it's very clear what's going on there

From my understanding, what most components are doing is iterating over a stream of messages, preprocessing them, and training on them.

I'm sorry, but that's not accurate, there are a couple of methods that require to see all the messages

It doesn't really matter what happens behind this interface of a list or stream of messages.

ye if you persist per message, but then you'd have awful lot of read operations

I don't really see why you couldn't just keep the normal TrainingData class and instead of it managing the examples as a list in memory it manages some data on the hard drive, maybe with some shuffling when needed etc.

we want to avoid unnecessary read/write operations, therefore we cannot persist per message

that's a completely different problem that we don't try to address in this PR

I am saying that with a different design you would get this for free. And it is what you are adressing: only loading the dataset partially at any given time.

then I'd say it's just the matter of naming and comments. Logic-wise, it's very clear what's going on there

What I am saying is that with managing two very similar methods with a lot of code duplication but subtle differences, it will always be very prone to error.

I'm sorry, but that's not accurate, there are a couple of methods that require to see all the messages

That's what we talked about earlier. If you need to see all messages to collect dataset-wide metadata you run over the stream twice, no?

ye if you persist per message, but then you'd have awful lot of read operations
obviously I am not proposing to persist every single message one by one, but in batches/chunks just like you did in principle

But I'd be doing it inside the the TrainingDataset which makes that whole procedure invisible to whoever consumes the messages

but implementation of which tf data generator to use depends on whether you load from files or keep data in the memory

how would you achieve that? do you plan to move model and label data creation out of diet classifier?

With the graph we can pass in the original training data set (without features) in addition to the chunks


docs(concat): clarify array as input

Description:
Since an array is itself an ObservableInput and so considered as an observable source, this specifies the use of spread operator to pass an array of observables.
Related issue (if exists):
#4697

Pull Request Test Coverage Report for Build 8354

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.02%) to 96.65%

Files with Coverage Reduction
New Missed Lines
%

src/internal/Subscriber.ts
1
81.48%

Totals

Change from base Build 8343:
-0.02%

Covered Lines:
5251

Relevant Lines:
5433

💛  - Coveralls


Timeout error

We are currently using phantom-html-to-pdf to generate a user report pdf, but on one specific linux server running nginx we're getting a 504 timeout error no matter what we try. It is as if it never gets to startup phantomjs. There aren't any errors (except timeout) in any of our logs or anything.
We have a different server running almost the exact same setup, where the setup works completely fine. The server where it doesn't work is a more closed test server, where only a selected range of IP-adresses have access. Other than that we can't find any noticeable differences that should affect this package.
We have tried to specify a port range and opening access for localhost requests in that range in the nginx configuration, but without luck. All localhost access should already be accepted, but we tried it nonetheless. We also tried changing the node version around to see if that had any effect, which it didn't. Giving the package a larger timeout in the global setting didn't change anything but the amount of time it took before the timeout error page was displayed.
Our implementation looks like this:
var converter = require('phantom-html-to-pdf')({
	host: '<IP_ADDRESS>'
});

converter({
	html: html,
	header: '
{#pageNum}
',
	footer: '

',
	waitForJS: true,
	waitForJSVarName: 'PHANTOM_HTML_TO_PDF_READY',
	allowLocalFilesAccess: true,
	paperSize: {
		format: 'A4',
		orientation: 'landscape',
		margin: '0.5in',
		headerHeight: '0.3in',
		footerHeight: '0.7in'
	},
	settings: {
		javascriptEnabled: true
	},
	format: {
		quality: 100
	},
	phantomPath: require('phantomjs-prebuilt').path
}, function(err, pdf) {
	if (err) {
		console.log(err);
		return;
	}

	console.log(pdf.logs);
	console.log(pdf.numberOfPages);
	pdf.stream.pipe(res);
});

Here's some server information which could be useful:

Linux server v. 3.10.0-514.el7.x86_64
Nginx v. 1.10.2
Node v. 4.2.6 (also tried running version 6 but there was no difference)
MongoDB v. 2.6.12
phantom-html-to-pdf v. 0.4.7
phantomjs-prebuilt v. 2.1.12

We are currently running out of ideas and hoping that someone could help us figure out what we can do to fix this?

I see you have enabled flag waitForJS: true. Did you try to run it with false?

But ofcause! Don't know why I didn't try that. That helped me find the error which is caused by a wrong filepath..
Thanks for your help! :)

Oh well, seems I was a bit too quick to close this issue. I've resolved the issues that I found previously, but as soon as I enable the flag waitForJS: true it hangs up and returns a timeout again.
I've tried setting the window. PHANTOM_HTML_TO_PDF_READY = true; on document ready to be sure that nothing of my JS code was failing. Even that results in a timeout error. And to check if there were any errors in the rendering of the html, I tried to simply return the html instead of starting the PDF converter. This returned the HTML correctly and the window. PHANTOM_HTML_TO_PDF_READY was correctly set to true.
Any other ideas that might help solve my issue? :)

So the problem is in waitForJS?
I don't know what could be a problem from your description.
You can see how it works in code. We basically create artificial script tag with particular url
https://github.com/pofider/phantom-html-to-pdf/blob/master/lib/scripts/conversionScriptPart.js#L60
and if the phantomjs catches this request, we finish the rendering and print
https://github.com/pofider/phantom-html-to-pdf/blob/master/lib/scripts/conversionScriptPart.js#L28

Hi @pofider
We've finally had some time again to get our hands into this problem and we've found a solution to the problem! It actually turned out that our javascript file wasn't loaded, but we never got an error telling us that the phantom browser couldn't load the file. It did trigger the onResourceRequested function, but it never triggered the onResourceError function. So we had no idea it was failing before all of our many attempts to console.log something from our javascript didn't appear in any logs.
Thanks for the help once again. 👍


Template error checker

Imported from Bugzilla 313
It would be super cool to have the templates validated so an unclosed control would error or an unclosed if etc.

Maybe looking at https://github.com/eclipse/webtools.sourceediting/tree/master/bundles/org.eclipse.jst.jsp.core/src/org/eclipse/jst/jsp/core/internal/validation would be better since JSP uses similar syntax

Updated link to the jsp validator https://github.com/eclipse/webtools.sourceediting/tree/master/web/bundles/org.eclipse.jst.jsp.core/src/org/eclipse/jst/jsp/core/internal/validation


[BUG] read C:.....\node_modules@types\sap__cds: Incorrect function. FAILED

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
When I try to deploy using cf push command I get the below error:
read C:\projects\......node_modules\@types\sap__cds: Incorrect function.
FAILED

tried doing npm rebuild before cf push as well, but still get the same error.
Expected Behavior
No response
References
https://community.sap.com/t5/application-development-blog-posts/july-developer-challenge-quot-reverse-apis-quot/ba-p/13749653#toc-hId-165109844
Versions

comp

@cap-js/asyncapi
1.0.2

@cap-js/cds-types
0.8.0

@cap-js/db-service
1.16.0

@cap-js/openapi
1.0.7

@cap-js/sqlite
1.7.7

@sap/cds
8.5.0

@sap/cds-compiler
5.5.2

@sap/cds-dk (global)
8.5.0

@sap/cds-fiori
1.2.8

@sap/cds-foss
5.0.1

@sap/cds-mtxs
2.4.0

@sap/eslint-plugin-cds
3.1.2

Node.js
v20.16.0

home
C:\projects\MoonSlate\comp\node_modules@sap\cds

Anything else? Logs?
No response

Hi @333sachin ,
please provide a minimal reproducible example, thanks!
Best,
Daniel

Here's a minimum reproducible example.
https://github.com/333sachin/issue-364
please run the below commands to get the error
cf login
cf push issue-364

Thank you for the reproduction!
This could be related to the symlink we generate in @types/sap__cds.
Can you please try out adjusting the "types" proerty in your tsconfig.json?

thanks @daogrady - but the sample was not a typescript project at all.
I added typescript support with cds add typescript   and update the tsconfig.json file according to the link.
I am able to run the project with cds-ts but still get the same error on cf push command
https://github.com/333sachin/issue-364 is updated with the above changes.

Hi @333sachin ,
thanks for trying out the proposed solution (you probably could have stayed with pure JS and used a jsconfig.json instead, in case you don't want to migrate to TS with your actual app 🙂).
Now that the type resolution mechanism should be able to find cds-types based on your config file, can you please delete the node_modules/@types/sap__cds (which is just a symlink to node_modules/cap-js/cds-types) and try again?
Best,
Daniel

Thanks,
Deleting the synlink worked for non ts project.


Feat: Healthcheck

Summary
This checks that everything in the library is as it should

Checklist

[x] If code changes were made then they have been tested.

[ ] I have updated the documentation to reflect the changes.

[x] This PR fixes an issue.
[x] This PR adds something new (e.g. new method or parameters).
[ ] This PR is a breaking change (e.g. methods or parameters removed/renamed)
[ ] This PR is not a code change (e.g. documentation, README, ...)

@TAG-Epic you need to catch pkg_resources.DistributionNotFound instead of all exceptions because warnings are technically built-in exceptions. Also you might want to warn with something other than a UserWarning which is the default warning if you don't specify a different warning in the category parameter in warnings.warn()
otherwise LGTM


Introduce the Download#FailOnError option.

This change allows preventing the executable start if the requested file cannot be downloaded. It also adds logging of download operations to the wrapper log.

[x] Code
[x] Test
[x] Documentation

The approach still needs to be finalized, because FailOnError does not propagate errors to the start command (as all other similar commands)
CC @nightman68 I just decided to write it in order to provide an example. If you want, I can integrate your auth proposals in the same way.

Hi Oleg,
I updated the pull request. Have a look to it and give me a hint how to proceed.

@nightman68 FYI will merge it to the master and then refactor and finalize both changes

Sounds good 👍
Waiting that it is integrated in Jenkins LTS.


Missing outlinks and inlinks under 0.5.1

What happened?
I am using dataviewjs to query ToDos for mentioned Names. Therefore, I use something like:
dv.current().file.inlinks
to get the current's file mentionings, yet this is apparently broken and renders no results anymore. I downgraded manually to 0.4.26 and it all works fine again.
DQL
No response
JS
dv.current().file.inlinks

Dataview Version
0.5.1
Obsidian Version
0.12.19
OS
Windows

Can you inspect the object in console and see what's happening there?

Can you provide an example file which replicates the problem? I have inlink/outlink test queries which work (based on links in text and in inline fields).


Research on implementation of offline web application

A app manifest is to be provided when the webapp is first accessed by the user. The browser should automatically cache the necessary files for offline usage.
Connectivity can be tested programatically.
Relevant resources:

https://developer.mozilla.org/en-US/Apps/Fundamentals/Offline
https://developers.google.com/web/fundamentals/engage-and-retain/web-app-manifest/


regenerate protos

googleapis 730ae385e8ddae8672c3d0fcbd3554d524456319
protobuf v3.4.0

@jba This commit adds firestore/admin files. We didn't add this before, but I believe adding it here is OK. We'll continue to not generate GAPIC client for it. Please let me know if you disagree.

https://code-review.googlesource.com/#/c/gocloud/+/19090/ should land first


docs: rename bagua.torch_api.contrib  package and update doc

What does the rename mean in the title?

What does the rename mean in the title?

rename bagua.torch_api.contrib.load_balancing_data_loader to bagua.torch_api.contrib.data


Massive high risk

CodeScene PR Check

Recommended Review Level
Inspect the code that degrades in code health.

Warnings
Degrades in Code HealthFifthHifhRisk.java degrades from a Code Health of 6.85 -> 1.0TenthHighRisk.java degrades from a Code Health of 6.85 -> 1.0FouurthHighRisk.java degrades from a Code Health of 6.85 -> 1.0SeventhHighRisk.java degrades from a Code Health of 6.85 -> 1.0ThirdHighRisk.java degrades from a Code Health of 6.85 -> 1.0NinthHighRisk.java degrades from a Code Health of 6.85 -> 1.0FirstHighRisk.java degrades from a Code Health of 6.85 -> 1.0EightHighRisk.java degrades from a Code Health of 6.85 -> 1.0SixthHighRisk.java degrades from a Code Health of 6.85 -> 1.0SecondHighRisk.java degrades from a Code Health of 6.85 -> 1.0

Code Health Delta Descriptions
FifthHifhRisk.java Degradations: Lines of Code in a Single File(total of 37706, recommended next goal: 10000 lines of code) - new issueNumber of Functions in a Single Module - new issueOverall Code Complexity - new issueLines of Declarations in a Single File - new issueLow Cohesion - new issueBrain Method (Change with 385 lines of code and increase with 77 conditional complexity (cc) in processRequest: cc = 95, cc threshold = 9) - getting worseBumpy Road Ahead (processRequest has 7 logical blocks with deeply nested code. Threshold is 1 (one) single block per function) - getting worseDeep, Nested Complexity (Increasing with 67 deeply nested functions) - getting worseTenthHighRisk.java Degradations: Lines of Code in a Single File(total of 37706, recommended next goal: 10000 lines of code) - new issueNumber of Functions in a Single Module - new issueOverall Code Complexity - new issueLines of Declarations in a Single File - new issueLow Cohesion - new issueBrain Method (Change with 385 lines of code and increase with 77 conditional complexity (cc) in processRequest: cc = 95, cc threshold = 9) - getting worseBumpy Road Ahead (processRequest has 7 logical blocks with deeply nested code. Threshold is 1 (one) single block per function) - getting worseDeep, Nested Complexity (Increasing with 67 deeply nested functions) - getting worseFouurthHighRisk.java Degradations: Lines of Code in a Single File(total of 18853, recommended next goal: 10000 lines of code) - new issueNumber of Functions in a Single Module - new issueOverall Code Complexity - new issueLines of Declarations in a Single File - new issueLow Cohesion - new issueBrain Method (Change with 385 lines of code and increase with 77 conditional complexity (cc) in processRequest: cc = 95, cc threshold = 9) - getting worseBumpy Road Ahead (processRequest has 7 logical blocks with deeply nested code. Threshold is 1 (one) single block per function) - getting worseDeep, Nested Complexity (Increasing with 33 deeply nested functions) - getting worseSeventhHighRisk.java Degradations: Lines of Code in a Single File(total of 56559, recommended next goal: 10000 lines of code) - new issueNumber of Functions in a Single Module - new issueOverall Code Complexity - new issueLines of Declarations in a Single File - new issueLow Cohesion - new issueBrain Method (Change with 385 lines of code and increase with 77 conditional complexity (cc) in processRequest: cc = 95, cc threshold = 9) - getting worseBumpy Road Ahead (processRequest has 7 logical blocks with deeply nested code. Threshold is 1 (one) single block per function) - getting worseDeep, Nested Complexity (Increasing with 101 deeply nested functions) - getting worseThirdHighRisk.java Degradations: Lines of Code in a Single File(total of 18853, recommended next goal: 10000 lines of code) - new issueNumber of Functions in a Single Module - new issueOverall Code Complexity - new issueLines of Declarations in a Single File - new issueLow Cohesion - new issueBrain Method (Change with 385 lines of code and increase with 77 conditional complexity (cc) in processRequest: cc = 95, cc threshold = 9) - getting worseBumpy Road Ahead (processRequest has 7 logical blocks with deeply nested code. Threshold is 1 (one) single block per function) - getting worseDeep, Nested Complexity (Increasing with 33 deeply nested functions) - getting worseNinthHighRisk.java Degradations: Lines of Code in a Single File(total of 37706, recommended next goal: 10000 lines of code) - new issueNumber of Functions in a Single Module - new issueOverall Code Complexity - new issueLines of Declarations in a Single File - new issueLow Cohesion - new issueBrain Method (Change with 385 lines of code and increase with 77 conditional complexity (cc) in processRequest: cc = 95, cc threshold = 9) - getting worseBumpy Road Ahead (processRequest has 7 logical blocks with deeply nested code. Threshold is 1 (one) single block per function) - getting worseDeep, Nested Complexity (Increasing with 67 deeply nested functions) - getting worseFirstHighRisk.java Degradations: Lines of Code in a Single File(total of 18853, recommended next goal: 10000 lines of code) - new issueNumber of Functions in a Single Module - new issueOverall Code Complexity - new issueLines of Declarations in a Single File - new issueLow Cohesion - new issueBrain Method (Change with 385 lines of code and increase with 77 conditional complexity (cc) in processRequest: cc = 95, cc threshold = 9) - getting worseBumpy Road Ahead (processRequest has 7 logical blocks with deeply nested code. Threshold is 1 (one) single block per function) - getting worseDeep, Nested Complexity (Increasing with 33 deeply nested functions) - getting worseEightHighRisk.java Degradations: Lines of Code in a Single File(total of 56559, recommended next goal: 10000 lines of code) - new issueNumber of Functions in a Single Module - new issueOverall Code Complexity - new issueLines of Declarations in a Single File - new issueLow Cohesion - new issueBrain Method (Change with 385 lines of code and increase with 77 conditional complexity (cc) in processRequest: cc = 95, cc threshold = 9) - getting worseBumpy Road Ahead (processRequest has 7 logical blocks with deeply nested code. Threshold is 1 (one) single block per function) - getting worseDeep, Nested Complexity (Increasing with 101 deeply nested functions) - getting worseSixthHighRisk.java Degradations: Lines of Code in a Single File(total of 37706, recommended next goal: 10000 lines of code) - new issueNumber of Functions in a Single Module - new issueOverall Code Complexity - new issueLines of Declarations in a Single File - new issueLow Cohesion - new issueBrain Method (Change with 385 lines of code and increase with 77 conditional complexity (cc) in processRequest: cc = 95, cc threshold = 9) - getting worseBumpy Road Ahead (processRequest has 7 logical blocks with deeply nested code. Threshold is 1 (one) single block per function) - getting worseDeep, Nested Complexity (Increasing with 67 deeply nested functions) - getting worseSecondHighRisk.java Degradations: Lines of Code in a Single File(total of 18853, recommended next goal: 10000 lines of code) - new issueNumber of Functions in a Single Module - new issueOverall Code Complexity - new issueLines of Declarations in a Single File - new issueLow Cohesion - new issueBrain Method (Change with 385 lines of code and increase with 77 conditional complexity (cc) in processRequest: cc = 95, cc threshold = 9) - getting worseBumpy Road Ahead (processRequest has 7 logical blocks with deeply nested code. Threshold is 1 (one) single block per function) - getting worseDeep, Nested Complexity (Increasing with 33 deeply nested functions) - getting worse


Org: OPSEC guidelines (suggestion)

A set of recommendations to protect contributors from opsec attacks, e.g.

do you know of a good list that we can piggyback off of?

@benawad I can look into this and see how we could go about implementing it. This would probably belong in the thinking required list on the main board since I don't really see anything else around (from a very brief search).

ok


Builtin Resources new constexpr storage data updates

there was also an attempt of making per built-in resource data compilations I want to save https://github.com/Devsh-Graphics-Programming/Nabla/commit/d5fd97a9539708cbe2da905f3db2d25c621349a3, but decided to not go into this because it needs us to generate another PCH/reuse & even with that it's just slow and not worth it


Improved rwlock release logic.

Minor code beautification, which I missed due to time constraints when fixing #238.

Thanks for the review Tom!

@wally-the-cartographer  merge

Merge requested by authorized user feuerste. Merge queue now has a length of 1.


Mongo not connecting with username and password for authentication

Authenticating the connection to MongoKitten.Database<mongodb://localhost:27017/samespace_alpha>    [Main:Convenience.swift:info] org.openkitten.mongokitten
13:50:44 [Error] Authentication for MongoDB user root with SASL failed against Optional("admin") because of the following error    [Main:Convenience.swift:error] org.openkitten.mongokitten
13:50:44 [Error] {"ok":0.0,"errmsg":"Authentication failed.","code":18,"codeName":"AuthenticationFailed"}    [Main:Database+Authentication.swift:challenge(with:using:usingConnection:)]

let server = try Server(hostname: "localhost", port: 27017, authenticatedAs: MongoCredentials(username: "username", password: "password", database: "admin"))
Config.log.debug("\(try server["db_name"]["collection_name"].findOne())")

I can't imagine this failing on our end, honestly. I'd need more details (verbose logging?) to say more.

I guess it was the problem with mongokitten3.
I upgraded the version to mongokitten4.
It is working on mac but failing on linux.
I am getting invalidBuildInfoDocument error

The detailed error is here
fatal error: Error raised at top level: MongoKitten.MongoError.invalidBuildInfoDocument: file /home/buildnode/disk2/workspace/oss-swift-3.1-package-linux-ubuntu-16_04/swift/stdlib/public/core/ErrorType.swift, line 188
Current stack trace:
0    libswiftCore.so                    0x00007fb68d5271c0 swift_reportError + 120
1    libswiftCore.so                    0x00007fb68d541ad0 _swift_stdlib_reportFatalErrorInFile + 100
2    libswiftCore.so                    0x00007fb68d33c40c <unavailable> + 1188876
3    libswiftCore.so                    0x00007fb68d4d437d <unavailable> + 2859901
4    libswiftCore.so                    0x00007fb68d33bbe6 <unavailable> + 1186790
5    libswiftCore.so                    0x00007fb68d4da290 <unavailable> + 2884240
6    libswiftCore.so                    0x00007fb68d33c01f <unavailable> + 1187871
7    libswiftCore.so                    0x00007fb68d49afa9 <unavailable> + 2625449
8    libswiftCore.so                    0x00007fb68d33bbe6 <unavailable> + 1186790
9    libswiftCore.so                    0x00007fb68d458260 specialized _assertionFailure(StaticString, String, file : StaticString, line : UInt, flags : UInt32) -> Never + 144
10   libswiftCore.so                    0x00007fb68d364d15 <unavailable> + 1355029
11   MongoKittenTest                    0x0000000000418a41 <unavailable> + 100929
12   libc.so.6                          0x00007fb68adec740 __libc_start_main + 240
13   MongoKittenTest                    0x00000000004184a9 <unavailable> + 99497
Illegal instruction (core dumped)

I've seen this before with a previous user. Whenever you're ready, you can poke me on slack. I'll need to know why the build info document is seen as invalid.

Fixed in 4.0.10


refactor!: rename solvers -> solver

bindings/python/src/OpenSpaceToolkitAstrodynamicsPy/Solvers.cpp
src/OpenSpaceToolkit/Astrodynamics/Solvers/
^those need to be changed I believe


[Knowledge Agent KIT] Fix Markdown Linting Issues

Due to the activation of the markdown linter in #674, several problems with different markdown files exist that need to be fixed.
Output:
docs-kits/kits/knowledge-agents/adoption-view/intro.md:37:51 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]
docs-kits/kits/knowledge-agents/adoption-view/intro.md:38:58 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]
docs-kits/kits/knowledge-agents/adoption-view/intro.md:56:267 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]
docs-kits/kits/knowledge-agents/adoption-view/intro.md:60:184 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]
docs-kits/kits/knowledge-agents/adoption-view/intro.md:77:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/adoption-view/intro.md:77 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- do not focus on exchanging/a..."]
docs-kits/kits/knowledge-agents/adoption-view/intro.md:78:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/adoption-view/intro.md:79:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/adoption-view/intro.md:80:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/adoption-view/intro.md:83:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/adoption-view/intro.md:83 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- allow you to easily bind you..."]
docs-kits/kits/knowledge-agents/adoption-view/intro.md:84:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/adoption-view/intro.md:100:98 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]
docs-kits/kits/knowledge-agents/adoption-view/intro.md:193:23 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]
docs-kits/kits/knowledge-agents/adoption-view/intro.md:197:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/adoption-view/intro.md:197:104 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]
docs-kits/kits/knowledge-agents/adoption-view/intro.md:198:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/adoption-view/intro.md:199:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/adoption-view/intro.md:205:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/adoption-view/intro.md:206:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/adoption-view/intro.md:207:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/adoption-view/intro.md:208:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/adoption-view/intro.md:209:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/adoption-view/intro.md:210:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/adoption-view/intro.md:211:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/development-view/Arc42.md:137 MD012/no-multiple-blanks Multiple consecutive blank lines [Expected: 1; Actual: 2]
docs-kits/kits/knowledge-agents/development-view/Arc42.md:144 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "1. A data provider provides a ..."]
docs-kits/kits/knowledge-agents/development-view/Arc42.md:145:1 MD007/ul-indent Unordered list indentation [Expected: 0; Actual: 2]
docs-kits/kits/knowledge-agents/development-view/Arc42.md:145 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "* Graph assets describe means ..."]
docs-kits/kits/knowledge-agents/development-view/Arc42.md:146:1 MD007/ul-indent Unordered list indentation [Expected: 2; Actual: 4]
docs-kits/kits/knowledge-agents/development-view/Arc42.md:147:1 MD007/ul-indent Unordered list indentation [Expected: 2; Actual: 4]
docs-kits/kits/knowledge-agents/development-view/Arc42.md:148:1 MD007/ul-indent Unordered list indentation [Expected: 2; Actual: 4]
docs-kits/kits/knowledge-agents/development-view/Arc42.md:148:87 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]
docs-kits/kits/knowledge-agents/development-view/Arc42.md:149:1 MD007/ul-indent Unordered list indentation [Expected: 2; Actual: 4]
docs-kits/kits/knowledge-agents/development-view/Arc42.md:150:1 MD007/ul-indent Unordered list indentation [Expected: 0; Actual: 2]
docs-kits/kits/knowledge-agents/development-view/Arc42.md:151:1 MD007/ul-indent Unordered list indentation [Expected: 2; Actual: 4]
docs-kits/kits/knowledge-agents/development-view/Arc42.md:152:1 MD007/ul-indent Unordered list indentation [Expected: 2; Actual: 4]
docs-kits/kits/knowledge-agents/development-view/Arc42.md:153:1 MD007/ul-indent Unordered list indentation [Expected: 2; Actual: 4]
docs-kits/kits/knowledge-agents/development-view/Arc42.md:154:1 MD007/ul-indent Unordered list indentation [Expected: 2; Actual: 4]
docs-kits/kits/knowledge-agents/development-view/Arc42.md:155:1 MD007/ul-indent Unordered list indentation [Expected: 2; Actual: 4]
docs-kits/kits/knowledge-agents/development-view/Arc42.md:155:15 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]
docs-kits/kits/knowledge-agents/development-view/Arc42.md:156:1 MD007/ul-indent Unordered list indentation [Expected: 2; Actual: 4]
docs-kits/kits/knowledge-agents/development-view/Arc42.md:157 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "(Although the diagram depicts ..."]
docs-kits/kits/knowledge-agents/development-view/Arc42.md:158:1 MD029/ol-prefix Ordered list item prefix [Expected: 1; Actual: 2; Style: 1/2/3]
docs-kits/kits/knowledge-agents/development-view/Arc42.md:158 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "2. A data provider marks parti..."]
docs-kits/kits/knowledge-agents/development-view/Arc42.md:159:1 MD029/ol-prefix Ordered list item prefix [Expected: 2; Actual: 3; Style: 1/2/3]
docs-kits/kits/knowledge-agents/development-view/Arc42.md:160:172 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]
docs-kits/kits/knowledge-agents/development-view/Arc42.md:160:1 MD029/ol-prefix Ordered list item prefix [Expected: 3; Actual: 4; Style: 1/2/3]
docs-kits/kits/knowledge-agents/development-view/Arc42.md:161:1 MD029/ol-prefix Ordered list item prefix [Expected: 4; Actual: 5; Style: 1/2/3]
docs-kits/kits/knowledge-agents/development-view/Arc42.md:162:1 MD029/ol-prefix Ordered list item prefix [Expected: 5; Actual: 6; Style: 1/2/3]
docs-kits/kits/knowledge-agents/development-view/Arc42.md:163:1 MD029/ol-prefix Ordered list item prefix [Expected: 6; Actual: 7; Style: 1/2/3]
docs-kits/kits/knowledge-agents/development-view/Arc42.md:164:119 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]
docs-kits/kits/knowledge-agents/development-view/Arc42.md:164:1 MD029/ol-prefix Ordered list item prefix [Expected: 7; Actual: 8; Style: 1/2/3]
docs-kits/kits/knowledge-agents/development-view/Arc42.md:167 MD022/blanks-around-headings/blanks-around-headers Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Above] [Context: "## Deployment View"]
docs-kits/kits/knowledge-agents/development-view/modules.md:83:138 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]
docs-kits/kits/knowledge-agents/development-view/modules.md:84:178 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]
docs-kits/kits/knowledge-agents/development-view/modules.md:90:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/development-view/modules.md:91:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/development-view/modules.md:92:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/development-view/modules.md:93:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/development-view/modules.md:94:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/development-view/modules.md:95:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/development-view/modules.md:96:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/development-view/modules.md:97:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/development-view/modules.md:134:52 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]
docs-kits/kits/knowledge-agents/development-view/modules.md:147 MD034/no-bare-urls Bare URL used [Context: "https://w3id.org/catenax/ontol..."]
docs-kits/kits/knowledge-agents/development-view/modules.md:170:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/development-view/modules.md:170:130 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]
docs-kits/kits/knowledge-agents/development-view/modules.md:170 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- will detunnel all protocol-s..."]
docs-kits/kits/knowledge-agents/development-view/modules.md:171:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/development-view/modules.md:172:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/development-view/modules.md:173:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/development-view/modules.md:174:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/development-view/modules.md:223:182 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]
docs-kits/kits/knowledge-agents/development-view/modules.md:287:108 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]
docs-kits/kits/knowledge-agents/development-view/modules.md:288:186 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]
docs-kits/kits/knowledge-agents/development-view/modules.md:289:126 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]
docs-kits/kits/knowledge-agents/development-view/modules.md:290:183 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]
docs-kits/kits/knowledge-agents/development-view/modules.md:291:123 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]
docs-kits/kits/knowledge-agents/development-view/reference.md:58:146 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]
docs-kits/kits/knowledge-agents/development-view/reference.md:62:140 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]
docs-kits/kits/knowledge-agents/development-view/reference.md:66:150 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]
docs-kits/kits/knowledge-agents/operation-view/agent_edc.md:41:167 MD037/no-space-in-emphasis Spaces inside emphasis markers [Context: "*vaultsettings and *"]
docs-kits/kits/knowledge-agents/operation-view/agent_edc.md:137:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/agent_edc.md:138:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/agent_edc.md:139:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/agent_edc.md:140:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/agent_edc.md:141:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/agent_edc.md:142:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/agent_edc.md:143:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/agent_edc.md:144:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/agent_edc.md:145:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/agent_edc.md:148:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/agent_edc.md:149:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/agent_edc.md:151:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/agent_edc.md:152:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/agent_edc.md:153:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/agent_edc.md:156:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/agent_edc.md:157:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/agent_edc.md:158:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/agent_edc.md:159:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/agent_edc.md:204:13 MD010/no-hard-tabs Hard tabs [Column: 13]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:46 MD012/no-multiple-blanks Multiple consecutive blank lines [Expected: 1; Actual: 2]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:101:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:101 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- App Provider 1 (BPNL00000000..."]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:102:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:103:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:104:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:105:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:106:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:107:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:108:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:109:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:110:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:114:90 MD034/no-bare-urls Bare URL used [Context: "https://portal.stable.demo.cat..."]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:115:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:115 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- App Provider 1: sa4"]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:116:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:118 MD012/no-multiple-blanks Multiple consecutive blank lines [Expected: 1; Actual: 2]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:119:49 MD034/no-bare-urls Bare URL used [Context: "https://vault.demo.catena-x.ne..."]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:120:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:120 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- stable-provider-miw"]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:121:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:124:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:124 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- oem-cert"]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:125:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:126:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:127:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:128:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:129:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:135:7 MD034/no-bare-urls Bare URL used [Context: "https://argo.stable.demo.caten..."]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:369:7 MD034/no-bare-urls Bare URL used [Context: "https://argo.stable.demo.caten..."]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:445:7 MD034/no-bare-urls Bare URL used [Context: "https://argo.stable.demo.caten..."]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:529:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:529 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Query Provider Agent (Intern..."]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:530:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:531:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:532:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:533:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:534:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:535:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:536:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:537:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:538:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:539:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:540:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:542 MD012/no-multiple-blanks Multiple consecutive blank lines [Expected: 1; Actual: 2]
docs-kits/kits/knowledge-agents/operation-view/deployment.md:543 MD012/no-multiple-blanks Multiple consecutive blank lines [Expected: 1; Actual: 3]
docs-kits/kits/knowledge-agents/operation-view/policy.md:40 MD012/no-multiple-blanks Multiple consecutive blank lines [Expected: 1; Actual: 2]
docs-kits/kits/knowledge-agents/operation-view/provider.md:36 MD012/no-multiple-blanks Multiple consecutive blank lines [Expected: 1; Actual: 2]
docs-kits/kits/knowledge-agents/operation-view/provider.md:81:14 MD010/no-hard-tabs Hard tabs [Column: 14]
docs-kits/kits/knowledge-agents/operation-view/provider.md:82:14 MD010/no-hard-tabs Hard tabs [Column: 14]
docs-kits/kits/knowledge-agents/operation-view/provider.md:83:13 MD010/no-hard-tabs Hard tabs [Column: 13]
docs-kits/kits/knowledge-agents/operation-view/provider.md:84:13 MD010/no-hard-tabs Hard tabs [Column: 13]
docs-kits/kits/knowledge-agents/operation-view/provider.md:85:13 MD010/no-hard-tabs Hard tabs [Column: 13]
docs-kits/kits/knowledge-agents/operation-view/provider.md:86:13 MD010/no-hard-tabs Hard tabs [Column: 13]
docs-kits/kits/knowledge-agents/operation-view/provider.md:88:14 MD010/no-hard-tabs Hard tabs [Column: 14]
docs-kits/kits/knowledge-agents/operation-view/provider.md:89:14 MD010/no-hard-tabs Hard tabs [Column: 14]
docs-kits/kits/knowledge-agents/operation-view/provider.md:93:18 MD010/no-hard-tabs Hard tabs [Column: 18]
docs-kits/kits/knowledge-agents/operation-view/provider.md:94:15 MD010/no-hard-tabs Hard tabs [Column: 15]
docs-kits/kits/knowledge-agents/operation-view/provider.md:95:15 MD010/no-hard-tabs Hard tabs [Column: 15]
docs-kits/kits/knowledge-agents/operation-view/provider.md:97:18 MD010/no-hard-tabs Hard tabs [Column: 18]
docs-kits/kits/knowledge-agents/operation-view/provider.md:98:15 MD010/no-hard-tabs Hard tabs [Column: 15]
docs-kits/kits/knowledge-agents/operation-view/provider.md:99:15 MD010/no-hard-tabs Hard tabs [Column: 15]
docs-kits/kits/knowledge-agents/operation-view/provider.md:101:18 MD010/no-hard-tabs Hard tabs [Column: 18]
docs-kits/kits/knowledge-agents/operation-view/provider.md:102:15 MD010/no-hard-tabs Hard tabs [Column: 15]
docs-kits/kits/knowledge-agents/operation-view/provider.md:103:15 MD010/no-hard-tabs Hard tabs [Column: 15]
docs-kits/kits/knowledge-agents/operation-view/provider.md:105:18 MD010/no-hard-tabs Hard tabs [Column: 18]
docs-kits/kits/knowledge-agents/operation-view/provider.md:106:15 MD010/no-hard-tabs Hard tabs [Column: 15]
docs-kits/kits/knowledge-agents/operation-view/provider.md:107:15 MD010/no-hard-tabs Hard tabs [Column: 15]
docs-kits/kits/knowledge-agents/operation-view/provider.md:110:15 MD010/no-hard-tabs Hard tabs [Column: 15]
docs-kits/kits/knowledge-agents/operation-view/provider.md:111:15 MD010/no-hard-tabs Hard tabs [Column: 15]
docs-kits/kits/knowledge-agents/operation-view/provider.md:115:15 MD010/no-hard-tabs Hard tabs [Column: 15]
docs-kits/kits/knowledge-agents/operation-view/provider.md:118:15 MD010/no-hard-tabs Hard tabs [Column: 15]
docs-kits/kits/knowledge-agents/operation-view/provider.md:119:15 MD010/no-hard-tabs Hard tabs [Column: 15]
docs-kits/kits/knowledge-agents/operation-view/provider.md:123:15 MD010/no-hard-tabs Hard tabs [Column: 15]
docs-kits/kits/knowledge-agents/operation-view/provider.md:419:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/provider.md:420:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/provider.md:421:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/provider.md:422:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/provider.md:423:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/provider.md:424:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/provider.md:425:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/provider.md:426:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/provider.md:427:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/provider.md:430:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/provider.md:431:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/provider.md:433:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/provider.md:434:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/provider.md:435:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/provider.md:438:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/provider.md:439:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/provider.md:440:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/provider.md:441:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/provider.md:526 MD003/heading-style/header-style Heading style [Expected: atx; Actual: atx_closed]
docs-kits/kits/knowledge-agents/operation-view/provider.md:526:3 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:48:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:48 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- 01_TESTASSETS - asset descri..."]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:49:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:49:52 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:50:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:51:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:52:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:53:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:54:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:54:59 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:55:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:56:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:57:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:58:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:59:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:60:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:60:1 MD007/ul-indent Unordered list indentation [Expected: 2; Actual: 3]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:61:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:61:1 MD007/ul-indent Unordered list indentation [Expected: 4; Actual: 5]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:62:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:63:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:63:1 MD007/ul-indent Unordered list indentation [Expected: 2; Actual: 3]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:64:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:64:1 MD007/ul-indent Unordered list indentation [Expected: 4; Actual: 5]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:65:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:65:1 MD007/ul-indent Unordered list indentation [Expected: 4; Actual: 5]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:82:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:83:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:84:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:85:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:86:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:102:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:103:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:104:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:105:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:106:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:107:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:108:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:111:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:112:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/operation-view/testbed.md:113:1 MD010/no-hard-tabs Hard tabs [Column: 1]
docs-kits/kits/knowledge-agents/page_changelog.md:36:24 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]
docs-kits/kits/knowledge-agents/page_changelog.md:48:24 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]
docs-kits/kits/knowledge-agents/page_changelog.md:58:44 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]
docs-kits/kits/knowledge-agents/page_changelog.md:60:38 MD034/no-bare-urls Bare URL used [Context: "https://w3id.org/catenax"]
docs-kits/kits/knowledge-agents/page_changelog.md:64 MD012/no-multiple-blanks Multiple consecutive blank lines [Expected: 1; Actual: 2]

how about adding a   "lint-kits-fix": "markdownlint-cli2-fix .markdownlint.yaml "docs-kits/**/*.md" "#node_modules"" command ?

Based on the documentation of markdownlint-cli2, the --fix option only helps with "fixable issues". Further, adding a command like lint-kits-fix would change all KITs, which can cause problems.
But feel free to execute the command locally with the specific folder of your KIT instead of docs-kits/**/*.md.
Nevertheless, being aware of the --fix option is a good idea that could be added to the documentation of the README.

Fixed in #704


[WIP] *: Attempt to fix multiarch builds

[ ] I added CHANGELOG entry for this change.
[X] Change is not relevant to the end user.

Changes
This PR attempts to fix current issue on CI - #5077 - which causes the publish_* jobs not to pass on the CircleCI.
The first attempt is to update the remote Docker engine version (see: https://circleci.com/docs/2.0/building-docker-images/#docker-version)
Temporarily, the job has been allowed on all branches but pushing images has been commented out, we just need to make sure we pass the docker-test step
Verification
Waiting on CI to pass

It's looking good, this time the emulator was installed - https://app.circleci.com/pipelines/github/thanos-io/thanos/8646/workflows/fda3dfa9-d706-47c8-8df1-b32ec8c8976e/jobs/17975/parallel-runs/0/steps/0-107

Tests are successful :+1: Removing the test commit and opening this up for review.

publish_main works :tada:


bump v1.6 rc.0, fix integration tests

This PR bumps the workload to v1.6, as well as (attempts to) fix integration tests

I'm stuck on the integration test fixes.  v1.6's dashboard removed the ID (#newResource) that was on the button we want to press, so now I'm at a loss.  I think the tests are working or nearly working apart from that issue.  I also think the charm is working with volumes v1.6, although its only been lightly manually tested

This is good to merge, unless we want to address @dnplas' comment


Narrow down trigger events

Purpose

$subject.

Codecov Report

Merging #23940 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #23940   +/-   ##
=======================================
  Coverage   14.59%   14.59%
=======================================
  Files          51       51
  Lines        1411     1411
  Branches      219      219
=======================================
  Hits          206      206
  Misses       1189     1189
  Partials       16       16

Continue to review full report at Codecov.

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


Add cloud provider config to kubeadm deployments

Add cloud provider to kubeadm deployments.
According to https://github.com/kubernetes/kubeadm/issues/1018#issuecomment-407721598 the cloud provider config should be in the extra args of each control plane.

@woopstar kubelet_kubeadm.env, Also need to configure cloud_provider.

Both apiserver and controllerManager need to mount cloud_config？

Both apiserver and controllerManager need to mount cloud_config？

They do ?

I think  need to do that, They are 2 containers. I don't know how to supports it by kubeadm.

/hold


Fix Table alignment issue

The table alignment for clients, queues and topics page is crashing after changing the value from dropdown.

Closed as completed!


review: Change MergeMap

Close this pull request as we should not change the function to sometimes mutate an object  sometime not


Can any one help me how to implement Feature Files in WinAppDriver using Java

Currently I am using data files like Excel to read the data to do the automation in WinAppDriver using Java. For example, If I input the number in the edit box then I am reading that number from excel. So, instead of reading Excel, I need to implement using "Feature Files"/Given - Then
Could you please help me how to implement this in WinAppDriver using Java.

Really not sure what you mean.  Do you have a code example?

We did a POC using WinappDriver for a desktop application automation with JAVA, we are using Excel for test data to execute automation scripts.
Now we are planning to implement feature file (Cucumber) and here are the questions

How can we implement feature file concept (Given, When, Then)
How to generate step definition file to implement logic to execute the automation scripts?
Is any example code-base to understand with feature files (cucumber)

have you checked this
https://stackoverflow.com/questions/31941689/how-to-read-excel-file-in-cucumber-project


Crash when using a property named “yes” or “no” using Results.filter in Swift

Goals
Filter a Results object by a property in Swift named “yes" or “no”.
Expected Results
Return filtered Results.
Actual Results
*** Terminating app due to uncaught exception 'Invalid predicate', reason: 'The 'valueForKeyPath:' function is not supported.’
*** First throw call stack:
(
    0   CoreFoundation                      0x00007fffcfb997bb __exceptionPreprocess + 171
    1   libobjc.A.dylib                     0x00007fffe4306a2a objc_exception_throw + 48
    2   Realm                               0x0000000100155448 _ZN12_GLOBAL__N_112QueryBuilder15apply_predicateEP11NSPredicateP15RLMObjectSchema + 4806
    3   Realm                               0x0000000100153ff2 _Z19RLMPredicateToQueryP11NSPredicateP15RLMObjectSchemaP9RLMSchemaRN5realm5GroupE + 154
    4   Realm                               0x00000001001bbde1 -[RLMResults objectsWithPredicate:] + 162
    5   RealmSwift                          0x00000001008b88f4 _TFC10RealmSwift7Results6filterftSSGSaP___GS0_x_ + 228
    6   InfinityChan                        0x000000010000dffc _TFC12InfinityChan13ICRealmThread12requestPostsfT7handlerFGO10RealmSwift21RealmCollectionChangeGCS1_7ResultsCS_11ICRea
libc++abi.dylib: terminating with uncaught exception of type NSException

Steps to Reproduce
Access a property named “yes” or “no” when filtering a Results query.
Code Sample
class Test: Object {
    dynamic var no = “foo”
}
…
try! Realm().objects(Test.self).filter(“no = %@“, “foo”)

Version of Realm and Tooling
In the CONTRIBUTING guidelines, you will find a script,
which will help determining these versions.
ProductName:    Mac OS X
ProductVersion: 10.12
BuildVersion:   16A323

/Applications/Xcode.app/Contents/Developer
Xcode 8.0
Build version 8A218a

/usr/local/bin/pod
0.39.0
(not in use here)

/bin/bash
GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin16)

/usr/local/bin/carthage
0.18.1
(not in use here)

/usr/bin/git
git version 2.8.4 (Apple Git-73)

"no = %@" is not a valid NSPredicate string. You'll need to use the %K formatter:
let realm = try! Realm()
realm.beginWrite()
realm.add(Test())
print(realm.objects(Test.self).filter("%K = %@", "no", "foo"))
// Prints:
// Results<Test> (
// 	[0] Test {
// 		no = foo;
// 	}
// )
realm.cancelWrite()

See Apple's Predicate Programming Guide for details.

@jpsim How to make it display 2 values ?
what I main
I have value only
it could contents boy , girl , all
I can use your filter to display only boy or only girl
I want to display only boy or all
Could you help me how can I do that ?


Check if app is installed

The plugin often reinstalls the helper app instead of checking if it is already installed.

in 1.0.3


NC | Noobaa syslogs are sent to two different files

Explain the changes

The Cosole log is silent depending on whether the syslog running or not. Because logs are not pushed to the console imjournal will not pick it and duplicate it to a message file.
Native layer logs are moved to noobaa.log file.

Note :  Created PR assuming all the Noobaa logs are read from var/log/noobaa.log
Issues: Fixed #xxx / Gap #xxx

https://github.com/noobaa/noobaa-core/issues/8032

Testing Instructions:

Install rsyslog and Noobaa RPM
And verify noobaa specific log are pushed only to /var/log/noobaa.log
Noobaa logs are not duplicated in /var/log/noobaa.log and /var/log/message

[ ] Doc added/updated
[ ] Tests added

@naveenpaul1 we discussed also about changing the debug_module to not print to console when syslog is true, right?

@romayalon We are silenting console log when syslog is enabled
this._log_console_silent = process.env.SYSLOG_ENABLED;


Handle the exception of IndexError when list item access is out of range

I am not strong with font tables but this commit is a try to fix small bug and catch case when accessing array item out of range

https://github.com/googlefonts/fontbakery/issues/501

I have removed more white spaces changes and leave only needed ones


Add pendingMocks() to global scope

This PR is similar to #388 and exposes the pendingMocks() function to the global scope. It allows users to determine which expectations have not been met.

@nunofgs thanks!
Landed on v2.17.0.


[Product/Project] Protocol PM Knowledge Transfer & Onboarding

Objective
This ☂  ticket organizes links, references and details to onboard a PM (Project/Product/Program/Protocol) Manager to the protocol team. It acts as a central point of coordination to capture questions, discussions and results to enable a new core team member to own and drive the project and product direction of the protocol.
Goals

Communicate: Improve communication within the core protocol team and between the core team and the community so they have visibility into what we're working on. Avoid anyone needing to ask: "What's the protocol team working on?`
Streamline: Update, add or remove processes to streamline how to help the team function effectively.
Update: Update scope, revisit timelines, clarifying deliverables, etc...
Deliver: Support the protocol team, in whatever way necessary, to deliver a TestNet in Q3/Q4.

Origin Document
Lots of documentation with details is not useful if no one reads it. Scope that's too broad is applicable in some cases, and scope that's very granular is applicable in others. We need to find a balance that tends to what the team, org, community and project requires.
This Video intends just to show a quick walkthrough of what we have, but everything is fully captured in the links below.
Click on the link above to view. Screenshot preview below:

Links

Roadmap

V1 Roadmap on GitHub
V1 Milestones on GitHub
E2E Feature List
Github Issues backlog on GitHub
Note: None of the milestones have all the issues created a head of time. We add issues "just in time" as things come up for the near/distant future, or on an at-needed basis

V1 Dashboard

V1 Dashboard Settings

Devlogs

Devlog template
Example Devlog

Weekly Sync
Iteration Planning
Protocol Iteration Retros
Protocol Hours
Protocol <> PNF

Deliverable
Weekly Sync

[ ] Update (IF needed) the template for weekly sync
[ ] Get up to speed on leading the weekly sync

Iteration Planning

[ ] Update (IF needed) the template for iteration planning
[ ] 	Get up to speed on leading the iteration planning

Devlog

[ ] Update (IS needed) the DevLog Template
[ ] Streamline the process of transferring iteration goals & results to public Devlog
[ ] Announce & live stream at least one public DevLog with the community

V1 Dashboard

[ ] Update (IF needed) the v1 dashboard
[ ] Update (if needed) the v1 dashboard settings

V1 Roadmap & Backlog

[ ] Update (IS needed) the V1 Roadmap

[ ] Update both timelines, details, scope and community to the community

[ ] Get up to speed on the E2E Feature List

Creator:  @Olshansk
Co-Owners: Matthew

@mokn Could you PTAL and let us know if you have any additional thoughts or updates for this onboarding ticket?

@RossiNYC One of the deliverables of this ticket is taking over DevLogs. Would you be comfortable submitting the one for this week?


Singularity availability on LSF

I work on a cluster where I need to do module load singularity to add singularity to the path. I must do this within every new job, not once at the start -- module load singularity && bsub "singularity" fails. Based on my experience with a solution similar to what you have here, I suspect that this setup won't allow --use-singularity. I predict it will fail with the same sort of error, which will manifest like this:
Building DAG of jobs...
WorkflowError:
The singularity command has to be available in order to use singularity integration.

My current workaround is to do load module singularity as a prefix to the variable you call jobscript in the wrapper (line 98 of lsf-submit.py).

Actually, I was totally wrong. I can load singularity once at the start of my session and use it everywhere "downstream".


allow cloning roles; fix unlabeled multi-select style

Summary
Fixes #6956 #7204
This PR adds the ability to clone global/cluster/namespace roles and fixes a couple style issues in the role form:

Nice catch @aalves08 - I've updated the form to give the two modes more consistent styling:


OCP has errors thrown due to dagrejs dep

Describe the problem
From findings in https://github.com/patternfly/patternfly-react/issues/10403. When building OCP using prerelease numbers, and either a) not updating the Charts version or b) using resolutions for Victory dep + updating charts version, there are errors thrown due to the dagrejs dep in Topology:
ERROR in<EMAIL_ADDRESS>9:7
Module parse failed: Unexpected token (9:7)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|  */
| class PriorityQueue {
>   _arr = [];
|   _keyIndices = {};
|
ERROR in packages/knative-plugin/src/topology/listView/knativeListViewComponentFactory.ts:34:7

How do you reproduce the problem?
Provide steps to reproduce. A codesandbox demonstrating the problem is appreciated.
Expected behavior
A clear and concise description of the expected behavior.
Is this issue blocking you?
List the workaround if there is one.
Screenshots
If applicable, add screenshots to help explain the issue.
What is your environment?

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

What is your product and what release date are you targeting?
Any other information?

@thatblindgeye Which releases are you using?

From my latest testing, these are the PatternFly releases I used:
"@patternfly/patternfly": "5.4.0-prerelease.5",
"@patternfly/quickstarts": "5.3.0",
"@patternfly/react-catalog-view-extension": "5.0.0",
"@patternfly/react-charts": "7.4.0-prerelease.12",
"@patternfly/react-component-groups": "5.3.0-prerelease.1",
"@patternfly/react-console": "5.0.0",
"@patternfly/react-core": "^5.4.0-prerelease.16",
"@patternfly/react-icons": "^5.4.0-prerelease.6",
"@patternfly/react-log-viewer": "5.2.0",
"@patternfly/react-styles": "^5.4.0-prerelease.7",
"@patternfly/react-table": "^5.4.0-prerelease.17",
"@patternfly/react-tokens": "^5.4.0-prerelease.6",
"@patternfly/react-topology": "5.4.0-prerelease.10",
"@patternfly/react-user-feedback": "5.0.0",
"@patternfly/react-virtualized-extension": "5.1.0",

The only difference is that the @patternfly/react-charts was either using the prelease version mentioned above + resolutions for Victory deps to use their 36.9.1 release, or using the 7.2.2 release of @patternfly/react-charts without Victory resolutions.


swagger 3.0 java.lang.NullPointerException: null

springfox.documentation.schema.Example
java.lang.NullPointerException: null
[ERROR] 2020-08-22 15:15:40,491 - (AbstractDocumentationPluginsBootstrapper.java:98) - Unable to scan documentation context default
java.lang.NullPointerException: null
	at springfox.documentation.schema.Example.equals(Example.java:131) ~[springfox-core-3.0.0.jar:3.0.0]
	at java.util.Objects.equals(Objects.java:59) ~[?:1.8.0_231]
	at springfox.documentation.service.RequestParameter.equals(RequestParameter.java:132) ~[springfox-core-3.0.0.jar:3.0.0]
	at java.util.HashMap.putVal(HashMap.java:635) ~[?:1.8.0_231]
	at java.util.HashMap.put(HashMap.java:612) ~[?:1.8.0_231]
	at java.util.HashSet.add(HashSet.java:220) ~[?:1.8.0_231]
	at java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169) ~[?:1.8.0_231]
	at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) ~[?:1.8.0_231]
	at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175) ~[?:1.8.0_231]

The snapshot versions are published, just not to maven central.

when to publish to maven central

I have also run into this issue and would appreciate any updates on target publish date to maven central. Or any workarounds?

I have also run into this issue and would appreciate any updates on target publish date to maven central. Or any workarounds?

I have also run into this issue and would appreciate any updates on target publish date to maven central. Or any workarounds?

i have the save issue. plz publish 3.0.1 to the maven central ASAP!

I also meet the issue, plz publish a fix version!

I also meet the issue, plz publish a fix version!

I also meet the issue, plz publish a fix version!

I also meet the issue, plz publish a fix version!

Apart from waiting for the release of 3.0.1, is there any workaround for this ? Is it related to the presence of "example" in the request param  ?

The snapshot versions are published, just not to maven central.

Where then ? jcenter.bintray.com has been closed for a while (and it is referenced in the springfox documentation as the main repository). Moreover, for snapshots releases it seems to be hosted on https://oss.jfrog.org, but how do you access it ? Is it even publicly accessible ?
Is there any way to build the 3.0.1-SNAPSHOT locally, I can't find any branch or tag for the ongoing development.
Thanks in advance for your response

So, what's the fix?

We can define the same package named springfox.documentation.schema ,and define a java file named Example in our project   just copy this code into the java file
https://github.com/springfox/springfox/blob/master/springfoxcore/src/main/java/springfox/documentation/schema/Example.java
the problem will be solved


Aws: Instrument elasticache

Instrument aws-sdk-elasticache
This gem will cover both:
AWS_ELASTICACHE_REDIS_CLUSTER
AWS_ELASTICACHE_MEMCACHED_CLUSTER

Redis test environments ready for testing.
memcached environments blocked by elastic IP problem.

Reopening until testing passes upstream


[docs] Recursive flag when first cloning from GitHub

Perhaps it would be useful to state in the readme that if cloning from the terminal, one should be using the recursive flag, since the dependencies should be cloned too (e.g. eigen).
In my case: git clone url did not work, but git clone --recursive url did.
pip install -e . ran smoothly afterwards.

solved since e935a28


Support Active Directory / Office365

https://github.com/appscode/gologin/commit/edbb42ecb10c96de37f30774210ac462777b32fd

kubectl OIDC provider demo: https://www.youtube.com/watch?v=giV0WHtp49A

https://developer.microsoft.com/en-us/graph/graph-explorer
Azure AD Graph, https://graphexplorer.azurewebsites.net/

Python:
https://azure-sdk-for-python.readthedocs.io/en/latest/graphrbac.html
https://github.com/Azure/azure-sdk-for-python/blob/master/doc/graphrbac.rst
https://msdn.microsoft.com/library/azure/ad/graph/howto/azure-ad-graph-api-operations-overview#TenantIdentifier
API:
https://msdn.microsoft.com/en-us/library/azure/ad/graph/api/users-operations#GetUsersMemberships

Docs:
https://github.com/microsoftgraph/microsoft-graph-docs/blob/master/api-reference/v1.0/api/directoryobject_getmembergroups.md
Azure AD Concepts:
https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-dev-glossary#multi-tenant-application

Application and service principal objects : https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-application-objects


Remove kubernetes.io from the taint key.

What?
This removes kubernetes.io from the taint key as per our changes to the node taints.
Related

https://github.com/alphagov/govuk-infrastructure/pull/1264

I think you'll also need to change the nodeSelector below

I think the nodeSelector is targeting the built-in label rather than the taint.

Oh yeah good point, sorry ignore me 🙃


Documentation: make build before running ./fabio

fabio binary has to be built first after go get github.com/eBay/fabio using
make build

It may be useful in documentation.
Thank you and
with best regards

That is not necessary since go get will run go install which will build a binary for fabio and store it in $GOPATH/bin Only, if you want a fully static binary on OSX then you need the Makefile since it sets the -tags netgo for the linker. On Linux this is the default. You can check that with ldd fabio and should get no dependencies.
Also, go build has the same effect. The only thing the Makefile does really is to ensure the git hash is stored in the main.version variable.

Thank you for your answer.
Yes, go get will also build the binary.
However, the binary will be in folder ./bin/, so it may be helpful to change the example ("To start fabio run") in documentation from
./fabio

to
./bin/fabio

With best regards

The binary will only be in an unexpected folder if you set your GOPATH per project. Also, then go get will put the binary into $GOPATH/bin whereas the source lives in $GOPATH/src/github.com/eBay/fabio. I'm going to close this as wontfix since this is the documented behavior of Go apps.


check available balance when issuing cheques

ensure that we are solvent when issuing a cheque.
also changes the /chequebook/balance endpoint to return both the total and the available balance.
closes #738

@janos @svetomir to clarify this is the /chequebook/balance not to be confused with the /balances endpoint from accounting. /chequebook/balance is very new and not used anywhere yet afaik.

@metacertain It would be good to have openapi spec updated in this PR or in the following one. It is needed for the documentation before the beta release.


how to hidden content in small screen

i found class d-sm-none it only show content that sm and up size, where i expected to hidden something in sm and down screen, is there have some common utilities for use  ?

yes, I discovered the same challenge, what if you want to hide something md and down?

you can combine multiple classes like this d-none d-sm-flex

Yeah, you need to use a combination of the above.