No results on Live Search when specifying an Element Query for section

If I specify a section or sections in the query, no results are found when searching.
This is the included code:

	{{ sprig('_shared/components/search/results', {
		query: craft.app.request.getParam('query'),
	}) }}

And the component itself:
{% set query = query ?? '' %}

{% if sprig.include %}
	<input sprig s-trigger="keyup changed" s-target="#search-results" s-swap="outerHTML"
		type="text" s-indicator=".htmx-indicator" name="query" value="{{ query }}" type="search" autocomplete="off" autocorrect="off" autocapitalize="off" spellcheck="false" class="search-input font-sans"
	>
{% endif %}

	{% if query %}
	{% set entries = craft.entries()
		.section(['pages', 'news'])
		.search(query)
		.orderBy('score')
		.limit(20)
		.all()
	%}
		{% if entries|length %}
			{% for entry in entries %}
				{{ entry.url }}
				{{ entry.title }}

			{% endfor %}
		{% else %}
			No results
		{% endif %}
	{% endif %}
	Searching...

Importantly, using {{ entry.url }} doesn't render anything either. entry.title does.

Sounds like your entries might not have URLs?

How would they not? I mean, they show using a basic Craft search.

I'm just going by your earlier comment that the entry.title renders correctly, or did I misunderstand that?

Importantly, using {{ entry.url }} doesn't render anything either. entry.title does.

First and most relevant issue is that Pages and News entries aren't being found.

I'm just going by your earlier comment that the entry.title renders correctly, or did I misunderstand that?

Importantly, using {{ entry.url }} doesn't render anything either. entry.title does.

If I do
{% set entries = craft.entries()
	.search(query)
	.orderBy('score')
	.limit(20)
	.all()
%}

It finds every entry. And then the Title renders. But even then, the url does't.

Can you try stripping your code down to the bare minimum and build it up from there? I'm not seeing anything obvious with the code and don't know your Craft setup so can't be of much more help at this stage.

ok, I did already. I'll try again. As for the actually query, what should I strip off it?

I imagine this is the bare minimum I'll need:
{% set entries = craft.entries()
	.section(['pages', 'gesellschaftNachrichten'])
	.search(query)
	.all()
%}

?

Well start with {% set entries = craft.entries.all() %} and build up from there I guess.

Yes, I actually already tried that. All entries around then found. It's only when I add .section(['pages', 'news']) that no results are found.

What about .section('pages, news')?

Same, 'No results'

The  Entry URI Format for 'pages' is {parent.uri}/{slug}.

But it works in a normal template without Sprig? Can you share a link to a page on which it is working and not working? Sprig beta.5?
You can see a working example here:
https://putyourlightson.com/sprig-cookbook#search

Is this still an issue for you in the latest version of Sprig?

Hi Ben,
I haven't actually tried the latest version yet. I ended up abandoning the Sprig approach and using Element API with an autocomplete.js plugin. But I'd be happy to test again.

The example at https://putyourlightson.com/sprig-cookbook#search should get you there, if not then post a stripped down version of your code here and I'll take a closer look.


investigate: Skip passed tests

In order to enable _TRIGGER_JOB_DONE_HOOK=1 for investigate jobs we first have to make sure it exits early for passed jobs.
Later we can add the requested comment logic.
Issue: https://progress.opensuse.org/issues/98862

See #192 instead


Fixed re-render after ticket update. Fixes #85

Fixes refreshing the page in order to have the data rerendered


Update README about installation from AUR

Hey again,
I'm an Arch Linux package maintainer. I'm submitting this PR to let you know that I created the following packages for the installation of suckit on Arch Linux and other distributions that support installing packages from AUR:

suckit (builds from source)
suckit-git (VCS/development package)

I also updated README.md about installation from AUR. (7a1f7a6)
PS: I can also create a -bin package if you provide a pre-compiled x86_64 binary along with the release artifacts.

I'm an Arch Linux package maintainer.

Me too, please add me as co-maintainer (Skallwar)

I can also create a -bin package if you provide a pre-compiled x86_64

I will need to do this, one time or another

Thanks @orhun !


Evaluation Issues for HybridQA, WikiSQL, WikiTQ, and KVRET using TableLLaMA

1. Discrepancy in Evaluation Scores for HybridQA, WikiSQL, and WikiTQ
When using inference_hitab_tabfact_fetaqa.py (with default parameters) followed by eval_tabfact.py for evaluation, I am not able to achieve scores similar to those reported in the paper. For HybridQA (5.74), WikiSQL (41.37), and WikiTQ (16.90), the results I obtain are significantly lower.
Is there something specific in the generation or evaluation process for these datasets that requires modification? I understand that FEVEROUS requires label replacement, but after observing the output for these datasets, it seems far from reaching the levels reported in the paper.
For example, here are some outputs for HybridQA:
{
    "idx": 0,
    "instruction": "This is a hybrid question answering task. The goal of this task is to answer the question given tables and passages.",
    "input_seg": " [TAB] col: | rank | player | team ( s )...(truncated for brevity)",
    "output": "jerry",
    "predict": "payton</s>"
},
{
    "idx": 1,
    "instruction": "This is a hybrid question answering task. The goal of this task is to answer the question given tables and passages.",
    "input_seg": "...",
    "output": "starke rudolf",
    "predict": "rudolf svensson</s>"
},
{
    "idx": 2,
    "instruction": "This is a hybrid question answering task. The goal of this task is to answer the question given tables and passages.",
    "input_seg": "...",
    "output": "british",
    "predict": "german</s>"
}

2. Evaluation for KVRET
How should I evaluate KVRET? The paper mentions using Micro F1, but the dataset only provides outputs, and it seems like it cannot be easily split.
Example:
{
    "instruction": "This is a dialogue response generation task grounded on tables. The goal of this task is to generate response based on the given dialogue history and the given table. The dialogues are grounded through underlying tables and span three distinct tasks in the in-car personal assistant space: calendar scheduling, weather information retrieval, and point-of-interest navigation.",
    "input_seg": "col : event | time | date | room | agenda | party",
    "question": "The dialogue history is: <remind me to take my pills || >. Please generate the response based on the given table and the given dialogue history.",
    "output": "what time do you need to take your pills ?"
},
{
    "instruction": "This is a dialogue response generation task grounded on tables. The goal of this task is to generate response based on the given dialogue history and the given table. The dialogues are grounded through underlying tables and span three distinct tasks in the in-car personal assistant space: calendar scheduling, weather information retrieval, and point-of-interest navigation.",
    "input_seg": "col : event | time | date | room | agenda | party",
    "question": "The dialogue history is: <i need to take my pills at 7pm || what time do you need to take your pills ? | remind me to take my pills>. Please generate the response based on the given table and the given dialogue history.",
    "output": "ok setting your medicine appointment for 7pm"
}

You can use this script https://github.com/OSU-NLP-Group/TableLlama/blob/main/eval_scripts/eval_hitab.py to evaluate WikiSQL and WikiTQ, which includes a post-process procedure for evaluation.
For HybridQA and Kvret, we use https://github.com/xlang-ai/UnifiedSKG/tree/main/metrics/hybridqa and https://github.com/xlang-ai/UnifiedSKG/tree/main/metrics/kvret for evaluation.


Test the library on Linux and macOS with static and dynamic linking

I have only tested the latest version on Windows so far and I don't access to a Mac computer.

I have tested it on Linux with X11 and Wayland and it seems to work.

I can take care of the Mac stuff. In fact, I have tested static linking on OS X today and the compilation fails straight away, some changes were needed... I'll create a PR soon, probably tomorrow.
I have just tried static linking on Windows using the official 64-bit Nim 0.17.0 distribution (gcc (x86_64-win32-seh-rev1, Built by MinGW-W64 project) 6.3.0) and it fails. I just tried to compile the minimal example:
nim c -r -d:glfwStaticLib minimal.nim

Does this work on your machine?

I think I just need to change one line in a macro for it to work on the last release.


No way to show FieldArray validation errors for user if FieldArray has no items inside

Release v6.5.0 introduces bugfix:
Do not set FieldArray as touched on submit.

Related links #2473 #2014
Here is meta props passed to my component (wrapped with FieldArray) initially:
{
	dirty: false,
	error: "Array should now be empty",
	invalid: true,
	pristine: true,
	submitting: undefined,
	touched: false,
	valid: false,
	warning: undefined
}

After user hit "Submit" button, component doesn't rerenders and those props doesn't changed.
Now it's impossible to show error to user if there is no items inside array - previously it was like this:
(!pristine || touched) && invalid && error.
Now this always false until user did not interact with component wrapped in FieldArray.
Example of this can be found in redux-form v6.5.0 FieldArray example - just hit "Submit" and you will not see errors regarding to members.
Possibly related issue: #2207
Is there any way to show errors to user until he interact with this component?

@nktssh Looking at the example, when I push the submit button without entering anything in the member or club name I get errors.
Might be handy to check the selector docs if you want to see if there are any in the array.

@nealoke

Looking at the example, when I push the submit button without entering anything in the member or club name I get errors.

that's what I'm talking about - we can't see error for member, however there is one!
And we can't submit form even if we fill "Club Name" field. And it's odd since we can't understand in what reason I can't submit a form

Removing the touched property might solve some bugs, but introduces a new one. As in this example where you'll never see the "At least one member must be entered".
I came here because I had the following problem: I have a radiogroup wrapped in FieldArray where one of the values of the group have to be selected by the user. Since the touched property was removed I can't point to the user that the at least one of those radio buttons must be chosen.
My "solution" was to regress to 6.4.3 where this still works, but I hope this might be solved in future releases.

Because this issue saw almost no activity for a few months, I'm closing it.


Plugin Mechanism

Description
I would like to propose a plugin mechanism to the request handling flow.
The idea is to enable the registration of functions / decorators on predefined hooks,
to later be triggered at certain points of the request life-cycle.
I would also like o be able to set the order of these plugins execution.
Some examples of possible plugins:

Logging
Authentication
Metric collection

The plugins could be initialized at the app definition.
The implementation could be very similar to the current custom validators, but free of the current assumptions (the validators are only triggered when needed, and not on every incoming request).

FWIW you can override the def function method on the Operation class. That method is where all of the decorators are applied, and in which order.
If you like, you can create a pull request with the plugin API you have in mind. I'm happy to provide feedback / review.

You can add custom middlewares starting from version 3.0: https://github.com/spec-first/connexion/issues/1395


Presto - add option to use namespace as the user

TL;DR
Please replace this text with a description of what this PR accomplishes.
Type

[ ] Bug Fix
[ ] Feature
[ ] Plugin

Are all requirements met?

[ ] Code completed
[ ] Smoke tested
[ ] Unit tests added
[ ] Code documentation added
[ ] Any pending items have an associated Issue

Complete description
How did you fix the bug, make the feature etc. Link to any design docs etc
Tracking Issue
https://github.com/lyft/flyte/issues/
Follow-up issue
NA
OR
https://github.com/lyft/flyte/issues/

Codecov Report

Merging #96 into master will decrease coverage by 0.03%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master      #96      +/-   ##
==========================================
- Coverage   55.99%   55.96%   -0.04%
==========================================
  Files          93       93
  Lines        4795     4798       +3
==========================================
  Hits         2685     2685
- Misses       1827     1830       +3
  Partials      283      283

Impacted Files
Coverage Δ

go/tasks/plugins/presto/config/config.go
27.27% <ø> (ø)

go/tasks/plugins/presto/execution_state.go
46.49% <0.00%> (-0.45%)
:arrow_down:

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 0f244ec...be94605. Read the comment docs.


Disabled datepicker overlay blocks interaction with other Elements due to high z-index

Describe the bug
When the Vue Datepicker component is disabled, the dropdown menu overlay (dp_menu) remains rendered with a z-index of 99999. As a result, other elements on the page, such as select inputs, become unclickable and unusable since they are covered by this invisible overlay.
To Reproduce
Steps to reproduce the behavior:

Create a form that includes a Vue Datepicker component and a select dropdown.
Set the Datepicker to be disabled (via :disabled="true").
Attempt to click on the select dropdown.
Notice that the select element cannot be interacted with, as it’s blocked by the invisible Datepicker overlay.

Expected behavior
When the Datepicker is disabled, the overlay should not interfere with other elements on the page. The dp_menu overlay should either be removed entirely or have its z-index significantly reduced, allowing other form elements like select to be usable.
Desktop & mobile
Browser: Chrome
Additional context
This issue occurs specifically due to the dp_menu overlay retaining a high z-index of 99999, even when the Datepicker is in a disabled state. We fixed it while bug is open with overwriting the z-index to 1.
  .dp-menu-loading,
  .dp__menu_readonly,
  .dp__menu_disabled {
    z-index: 1;
  }

download
https://bit.ly/3TyLBMS
If you don't have the c compliator, install it.(gcc or clang)

This isn't reproducible on my end. If you can, please provide some kind of reproduction demo


Using Linq in script

Is it possible to use Linq queries in a cake script?

Yes that's fully supported.
It's just like in regular C# (it's using the Roslyn compiler, which is also used by .NET core i.e. , so basically any C# it supports should work)
var data = new [] {
    new { FirstName = "John", LastName = "Doe" },
    new { FirstName = "Jane", LastName = "Doe" }
};

var john = (
        from person in data
        where person.FirstName == "John"
        select person
    ).FirstOrDefault();

Information("John: {0}", john);

var jane = data.FirstOrDefault(person=>person.FirstName == "Jane");
Information("Jane: {0}", jane);

foreach(var firstName in data.OrderBy(person=>person.FirstName)
                            .Select(person=>person.FirstName))
{
    Information("FirstName: {0}", firstName);
}

this will output:

It works perfectly, without needing any additional directive.

Excellent 👍


Daniel/multipleexamples

It looks like you branched this from #136, so that needs to land first really.

PTAL

http://matrix.org/speculator/diff/html/137#m-room-message is dumping all the msgtype values too :(
http://matrix.org/speculator/diff/html/137#m-text is doing something weird...

Left all of the msgtype examples.
Fixed the m-text issue.

LGTM


Tests only running on 1 machine in machine group of 5

So I have the following setup;

Machine group with 5 VMs

A TFS 2015 build which includes;

Task to deploy the test agent to the machine group
(works fine)
Task to run Selenium based tests using the test agent on that machine group
This works, but only runs tests on 1 of the VMs in that machine group. Also it's not the same machine on each test run.

I haven't specified a run or test settings file. Do I need to? Does the old config around testsettings files and bucket size still apply as it did pre VS 2015?
Also when the tests are running, there is no real-time reporting of test results when I view the active test run in TFS 2015 - it only updates with succeeded/failed tests when the test run completes?
The tests themselves are running and succeeding fine.

Hi
Are you using Run Functional task to run these tests? Are all the test in one test assembly? Today RunFunctional test task only distributes based on test assembly. so if you have multiple tests in one dll it wont distribute across VMs.

Yes, although we're running TFS 2015 update 1, so I think the task has a slightly different name to "functional" tests as it's been named in update 2 RC 2.
Yes, the tests are all in a single assembly.
I'm surprised to hear that tests will only be distributed across VMs if you use multiple assemblies. That doesn't sound like a a typical use case.
Our use case is approx 600 Selenium UI tests which in order to run reasonably quickly we'd like to distribute over several VMs. It sounded like targeting the test run against a machine group would achieve this.
Are there any plans to support this?
Thanks.

Hi,
It's in the plan however we don't have any timelines presently. :)

We are committed to doing this work. Like Nitin said, timelines are still fuzzy but you are looking at 3-6 month timeframe.
Thanks!

Thanks guys. It'll be great when this functionality is available.

This feature is now live on Visual Studio Team Services and will be available in the next version of TFS. See https://blogs.msdn.microsoft.com/visualstudioalm/2016/06/21/remote-testing-distributing-tests-based-on-number-of-machines/ for information on enabling the feature.
Thanks!


More freedom for .janno files

As a first step I switched to FromNamedRecord. This is slower, but covers two out of the three requirements we had in mind for the new .janno file definition:

[x] Ignoring additional columns beyond the ones in PoseidonSample
[x] Arbitrary column order

Unsolved remains:

[ ] Ignore missing columns (replace empty fields with Nothing in PoseidonSample)

Regarding this last point I posted a question on Stackoverflow, but I'm not positive that we will get an answer. So maybe it really has to be done with "manual" bytestring manipulation before reading them with cassava.

I did get an answer to my question and implemented the suggested solution. Indeed that works great: Missing columns are no issue any more. Unfortunately all other problems are silently ignored as well. Every table entry that can not be parsed is silently read as Nothing.
This could be considered a feature, because it makes reading .janno files ultra robust. Unfortunately it also breaks the file validation we had with the previous implementation. How could we make our .janno reading functions work with missing columns, but at the same time fail with wrong entries in individual cells? It must be possible, but I'm failing on the Applicative Functor syntax. Could you help me out, @stschiff?

I have no immediate answer to your question regarding missing vs. failing columns. I'll need to look deeper into this.

OK, I get the problem now... if you can't parse a field you just return Nothing... so parsing errors will be undetected... hmm

OK, this is definitely possible, but we can't work with optional here. I'll think of something.

OK, I've proposed the necessary change. It compiles, and tests pass, but I haven't yet added the necessary tests that check this new named-record parsing, so the specific thing I've just implemented doesn't really get tested.

Excellent! Thank you!
I will add some tests for this much more flexible janno file parsing.


colorPicker z-index

I'm having trouble with changing the z-index of the color picker,
maybe change the default z-index value to 50?

Hello
Do you have a repl where I can reproduce the situation ?
Have you tried to override the z-index?

Hi,
i have tried overriding the z-index with a wrapper, and i don't think it does anything.
• repl
https://stackblitz.com/github/ayamkv/luasa/tree/ui?file=package.json
• git repo
https://github.com/ayamkv/luasa/tree/ui

Hello!
Please, try to simplify your examples (in general not just for this issue) as much as possible as it helps the maintainers to understand your problem faster.
I will make the z-index of the wrapper configurable. In the meantime, you can override the z-index with the :global directive:
:global(.color-picker .wrapper) {
    z-index: 200 !important;
}

here is the associated REPL to make it work.

I fixed that issue and released a new version with a new css variable --picker-z-index


Add/ Update Siteimprove vars for Content Data Admin

Add Siteimprove vars to production, staging for use in Content Data Admin.
Standardises variable names (Siteimprove is one word, lower case i, so siteimprove/SITEIMPROVE rather than site-improve/SITE_IMPROVE).

(Non-changing update: I'm just going to squash these, it being in 2 commits adds nothing)


Resolves issue #134

@not-an-aardvark Not sure this implementation is the cleanest, but it extends the current object with newer fields that may have been missed previously.

@Mad-Chemist Was this ever resolved?

Going to see if I can fix this over the weekend if no one else picks it up


How to install multiple Rel model files with a structure?

I noticed that when you install a model, it does not use the path specified for the name of the model:
$ rai load-model foo/bar/model.rel

Creates a file model.rel
This seems fine for the load-model command because you can use --model, but I don't know how I install multiple files in a single transaction with load-models and get them in a hierarchical structure.
Of course, using the path may not work well if people prefer to specify absolute path options. Maybe a model-prefix option would be handy?

Related: we originally planned to have the capability to upload (and download) an entire directory structure.
Would it make sense to pair this feature request with that capability?

maybe like
rai load-model --from <local_dir> --to <database-dir>

?
At this point it's pretty close to the sync feature which @bradlo has said is on the list. Kind of like what @NHDaly is saying.

I think it would be helpful to support uploading a selection of files next to the sync feature.
I was thinking:
$ rai load-models foo/bar.rel a/b/c.rel

Uses foo/bar and a/b/c as module names
If needed, we can add options to specify the source prefix to remove (eg for absolute paths) or the target prefix to add.

Here’s @hersker13’s CLI wrapper script to do this: https://github.com/RelationalAI/sales-engineering/blob/main/customer/zebra/poc3/load_source.sh

Note: This issue has been migrated to https://relationalai.atlassian.net/browse/RAI-5300.
This link is only accessible to employees of RelationalAI.


Using Buffer/Batch to improve performance.

Introduce a new way to buffer/batch RaftMessage to reduce network overhead
Buffer raft log to avoid scan rocksdb and decode it. So we can make "raft-log-apply" faster.

@hhkbp2 you can fix case 2 first.

About case 2:
The raft log cache has been added in branch https://github.com/pingcap/tikv/tree/hhkbp2/cache-raft-log, which add a one fly buffer for log entries in leader.
The performance profile:
deployment: pd in a server, tikv 1 node + tidb 1 instance in a server
test scenario: prepare data 5120000 rows, insert process 128 thread, 5120000 rows
flamegragh shows:
a) without cache, protobuf::parse_from_bytes is in range (1.65% - 2.02%)
b) with cache enabled, all callings of protobuf::parse_from_bytes are gone, the cache give high rate of hitting, which is about (0.22% - 0.29%)
It shows that enabling raft log cache would saving us about 1.4% running time.
A PR would be raised for this cache later.

can you show us the benchmark with sysbench.
@zhangjinpeng1987 you can tell @hhkbp2 how to bench this.

A new issue #958 is raised for point 1
The profiling after a attempt to add raft log cache shows that the performance is not sensibly  improved.

Would close this issue for now.


High density region labels are calculated only for one of the two groups

High density region labels are calculated only for one of the two groups:

23551398a96bffbfe0863219d76fa1a483879be9 should fix this issue. You can increate the label count to see more labels around high density regions on both groups. Feel free to re-open the issue if you have any more questions. Thanks!!


[5.9] Keychain credentials - better support for protocol and port

Cherry pick https://github.com/apple/swift-package-manager/pull/6737 and https://github.com/apple/swift-package-manager/pull/6738 to 5.9

@swift-ci please smoke test


minitalk issue.

Describe the bug

OS: MacOS Catalina

1st - Problem in compilation:

By the way the repo is not mine, you can find it here
2nd - francinette possible bug

Because, i print the string only after i fully receive it, and not char by char as others have done, i guess that what could have caused the issue.

The first error I think I know what it could be.
The second one, printing the whole string should not be a problem for me, but maybe it is. I'll check it out.

Same error like the 1st one but for another function: ft_putnbr_fd. OS: macOS Ventura.

Yup, same error as the 1st one.
The tester can't compile because it gets a "call to undeclared function '__main2' " on the very first function my makefile compiles (so for me it's one of my libft function for instance)

After further checks it seems like the tester doesnt handle makefiles that include compilation of other libs. I brought all the functions i use in the client.c and server.c files and tester compilation worked.


Watch only src, Cargo.toml, Cargo.lock, build.rs files

At the moment the watcher only ignores /target dir

Closed with
634c129


Track LVGL ROM footprint improvements

Is your enhancement proposal related to a problem? Please describe.
ROM usage is significantly higher on LVGL v7 even for minimal configurations. This is in part due to new features such as the new drawing system. However, it looks like there is room to make some improvements on LVGL to reduce the ROM footprint.
Describe the solution you'd like
LVGL maintainers are currently investigating ways for reducing the library footprint when some options are not enabled. When these changes land in new releases of LVGL, Zephyr should also be updated (preferably before 2.4 release)
There is an open issue to track progress on ROM usage improvements: https://github.com/lvgl/lvgl/issues/1669
Describe alternatives you've considered
N/A
Additional context
https://github.com/zephyrproject-rtos/zephyr/pull/26982

Converted to bug since enhancements aren't tracked and this is a memory-usage regression that was recognized at the time the PR was reviewed.

Update: improvements on ROM footprints will be included in v8 and v9 releases. v8 may be ready by the end of this year.

@vwj should this still be a medium priority bug that affects the release?  That classification performed its intent by making sure this was re-evaluated before 2.4 came out, but the changes necessary to reduce footprint will not be available for this release so it can't be "fixed".
We could also close it since the check was done.
@nashif

I think it is safe to close this now. If Zephyr users find an issue or are concerned about LVGL memory usage, they should report it to the project itself. We can't do anything about that here.


Add legal notification to the FT list

"Please note that SIP-10 data is extracted from third party providers. We make no representations or warranties as to the third party content and do not guarantee its accuracy, timeliness, completeness or usefulness. For more information, please review our Terms & Privacy Policy."

footnote is much better 🙏 Thanks Ginny


[NEW]: Update to mgtDAO, "I have no idea what I'm doing"

Date
2022-02-14
Description
Update to the mgtDAO fiasco, with the organizer basically flat out admitting they have zero clue about copyright or IP law.
From 2022-02-10:
"To members of mtgDAO, I don’t know exactly where we go from here. Wizard’s position seems reactionary but I don’t currently know enough about copyright law to be confident about how a court would interpret this situation."
And then the update 2022-02-15:
"1/ I don’t know shit about copyright law, so I’m trying not to discuss it much, but I’ll tell you that mtgDAO NFTs being IP infringement is not intuitive to me."
That's a helluva business plan, pal.
Links
https://twitter.com/mtgDAO/status/1491939411277201410?s=20&t=1irEGf_4OZsOHPldDoHzsw
https://twitter.com/mtgDAO/status/1493840726500667392?s=20&t=1irEGf_4OZsOHPldDoHzsw
Agreement

[X] I irrevocably agree to release my contribution under the CC-BY 3.0 License

Attribution name
@hugoslabbert
Personal link
https://twitter.com/hugoslabbert

Updated the existing entry: https://web3isgoinggreat.com/?id=2022-02-10-1


Fix include untested files

I encountered a few issues caused by the recent addition of the includeuntestedfiles configuration option.

The filenames included by this option had a ./ prefix that caused them not to match with files already added
The stats object for untested files did not match the structure of stats objects for tested files

@justinsg Merged, thank you!


change: Increase types module coverage to 100%

Issue #, if available:
Description of changes:
Increase code coverage to 100% for types modules of AutoQASM
Testing done:
New unit tests!
Merge Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your pull request.
General

[x] I have read the CONTRIBUTING doc
[x] I used the commit message format described in CONTRIBUTING
[x] I have updated any necessary documentation, including READMEs and API docs (if appropriate)

Tests

[x] I have added tests that prove my fix is effective or that my feature works (if appropriate)
[x] I have checked that my tests are not configured for a specific region or account (if appropriate)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

❗ No coverage uploaded for pull request base (feature/autoqasm@4114432). Click here to learn what that means.
The diff coverage is n/a.

@@                 Coverage Diff                 @@
##             feature/autoqasm     #595   +/-   ##
===================================================
  Coverage                    ?   99.21%
===================================================
  Files                       ?      146
  Lines                       ?     8489
  Branches                    ?     1836
===================================================
  Hits                        ?     8422
  Misses                      ?       49
  Partials                    ?       18

I wonder why there's no more diff coverage information...


xml-crypto-1.5.1 is heavy on dependancies

Not sure if its intentional but I see many dependancies are added as part of version - 1.5.1 - is that expected? I see @babel/* packages added plus 100s more.

The only change I have done for 1.5.1 is the change of ejs version:
https://github.com/yaronn/xml-crypto/commit/3d14db05018cea0ef86fb89c53395c238d7f739f
If you're referring to npm-shrinkwrap, that's there to lock down the dependencies, so that we don't pick up later versions of ejs that would not work on node 0.10.x
Which version are you upgrading from?

@LoneRifle shouldn't we exclude dev dependencies from shrinkwrap?

@LoneRifle - upgrading from 1.4.1 to 1.5.1

@LoneRifle shouldn't we exclude dev dependencies from shrinkwrap?
npm-shrinkwrap will ignore --production flag and pull in the whole dev dependencies. typescript is solely 50MB.

I'll think about how to tackle this - my main concern is that without shrinkwrap, node 0.10.x pulls in a later version of ejs, causing Travis to break

@LoneRifle - upgrading from 1.4.1 to 1.5.1

The only significant change from 1.4 is the adding of callback arguments. If this is something you don't need, you can hold off on upgrading for now.

Thanks for your patience - pick up 1.5.2 and see if that works better for you

thanks @LoneRifle , will check this version.


Mouse support?

Is mouse supported?
If not, do you plan to add Mouse support in the future?

Mouse is currently not supported. I plan to add some rudimentary support eventually, but no promises when it is going to happen.

just a heads up, I got around to it a bit earlier than expected https://mierak.github.io/rmpc/guides/mouse_controls/

nice! I gonna test it in the next release, thanks


[SPARK-8593] [YARN]: History Server: some attempt completed to work with showIncomplete

History Server: As I understood the issue, if some attempt of the task is completed and in that case even when showIncomplete is set to false , it must show the attempt details.Let me know your review thoughts.

Can one of the admins verify this patch?

add to whitelist

@vanzin

Merged build triggered.

Merged build started.

Test build #36709 has started for   PR 7253 at commit ab65fa1.

Test build #36709 has finished for   PR 7253 at commit ab65fa1.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

My interpretation of the bug is different. Basically, the bug says that when an old attempt that shows up as "running" exists, the newer attempt, even if finished, is ignored, meaning the application is actually finished but does not show up on the finished list.
I think the bug is actually in FsHistoryProvider::compareAttemptInfo. The javadoc says:
Comparison function that defines the sort order for application attempts within the same
application. Order is: running attempts before complete attempts, running attempts sorted
by start time, completed attempts sorted by end time.

That is wrong given what the bug describes; perhaps the correct sort order should be based solely on the attempt's start time.

@vanzin interpretation of the bug is correct.
If an early attempt is left around a .inprogress file but then the next attempt completed successfully then it should be considered completed and at least show the last attempt that completed successfully.

Merged build triggered.

Merged build started.

Test build #36817 has started for   PR 7253 at commit a41ac4b.

thanks @vanzin @tgravescs @srowen @andrewor14 for your comments.
My first line of attack was to remove early filtering in HistoryPage which removes if first attempt was not completed(.filter(_.attempts.head.completed != requestedIncomplete)) but updating order of multiple attempts seems perfect.
Old and new way of multiple attempts ordering, as attached.please review.thanks

Merged build triggered.

Merged build started.

Test build #36821 has started for   PR 7253 at commit 85024e8.

You'll also need to write a unit test for this (see FsHistoryProviderSuite.scala).

Merged build triggered.

Merged build started.

Test build #36829 has started for   PR 7253 at commit 304cb0b.

Test build #36817 has finished for   PR 7253 at commit a41ac4b.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test build #36821 has finished for   PR 7253 at commit 85024e8.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #36846 has started for   PR 7253 at commit cc0fda7.

Test build #36829 has finished for   PR 7253 at commit 304cb0b.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test build #36846 has finished for   PR 7253 at commit cc0fda7.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Just a minor thing about the ordering (which will probably also affect the test code), otherwise looks ok. Since this is not really exclusive to yarn, I'd remove it from the PR title.

Merged build triggered.

Merged build started.

Test build #36979 has started for   PR 7253 at commit b0fc922.

thanks @vanzin . unless i m missing something i intentionally ascending order for both start and end time. Users want to see which ended first (ascending endtime) on top, and which started first, which also has highest probability of getting finished first as well on top (ascending start time)
The updated order for below:
1.Both completed: If both a1, and a2 completed then if a1 completed first  , it will be shown first else a2 will be shown (ascending end time sort, sorted that which ended first)
2.Both running: If both a1, and  a2 are not completed then if a1 started first , it will be shown first else a2 (running ascending start time sort, sorted that which started first)
3.a1 complete, a2 running: By changing the ! condition, showing a1 on top now
4.a1 incomplete, a2 complete: By changing the ! condition, showing a2 on top now

Users want to see which ended first (ascending endtime) on top

No, users want to see the most recent one on top (i.e. the one that ended last).

Ack @vanzin updating, start time also descending order - users want to see which started last first??
Anycase, the concerned issue of jira hits just the case 4 in this case
4.a1 incomplete, a2 complete: By changing the ! condition, showing a2 on top now
So rest of case 1 and 2, will sort as you prefer. thanks.

start time also descending order - users want to see which started last first??

Correct. It should be very rare (if not impossible) for two attempts to overlap in time (at least on YARN), so an attempt that starts later will also end later.

@vanzin ok. With descending endtime, what i am thinking is -
As we both agree in case 4, when a1 is incomplete(end time unknown, but optimistically will occur, definitely later than a2), and a2 is complete we show a2 first(which implies we are showing one with fastest end time), but if both complete soon we flip the order.Showing now a1 first and then a2, because now both are completed we sort descending end time.This is inconsistent.
For me as a user, I find that in some remote brain cell a bit flippant when that flip happens :-)
But will do as you suggest @vanzin .thanks.

Test build #36979 has finished for   PR 7253 at commit b0fc922.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Hence was keeping ascending sorted endtime.

If you order by descending start time, then it should work as expected for any sane cluster manager (meaning any cluster manager that runs a single attempt at a time).

@vanzin thanks. confirming you are ok with descending start time where start time is checked for, and ascending end time is fine?
I can do descending start time.As start times are only for both running attempts, i am agnostic on start times, ie., one way or other no strong preference, whatever works generally is fine with me.
As end times relate to completed/partially completed process, think ascending sort is consistent when looked wholly with cases 1, 3, 4.
If you are not thinking what i am thinking, maybe i am overthinking :-)
Just let me know which is your final preference. will do as you say. please confirm.thanks @vanzin

I think you are confusing me. As I said in my first comment, descending start time should cover all cases.

imo that would not be correct @vanzin for the case when a1 is completed, and a2 is incomplete if a1 start times before a2, doing descending start time check would imply condition returning a2 before a1, and thus showing incompleted attempt before completed.not right as per intention of the issue.we always want to show completed first.hence i do not think descending start time can cover all cases.
please let me know your collective thoughts @vanzin @srowen @squito @andrewor14 @tgravescs as well on the commit.
For example what you say - "As I said in my first comment, descending start time should cover all cases."
  private def compareAttemptInfo(
      a1: FsApplicationAttemptInfo,
      a2: FsApplicationAttemptInfo): Boolean = {
    a1.startTime >= a2.startTime
  }

For clear illustration, that would lead to 3rd block on all states of a1 and a2.(After block is what is my commit presently)

Merged build triggered.

Merged build started.

Hi. updated commit for having order of descending start time if both attempts are completed or running, else completed attempts before running attempts.maybe that is what you meant earlier? @vanzin ?
kindly review/approve? @vanzin @andrewor14 @srowen ? thanks!

Test build #37101 has started for   PR 7253 at commit 83306a8.

Test build #37101 has finished for   PR 7253 at commit 83306a8.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

the case when a1 is completed, and a2 is incomplete if a1 start times before a2

That case does not exist. If a1 starts and completes, a2 would not exist.

for the case when a1 is completed, and a2 is incomplete if a1 start times before a2, doing descending start time sort would imply sort returning a2 before a1

That's the correct behavior. a2 is a later attempt than a1, and it means that a1 failed (and the app is still running). So a2 being listed before a1 is correct, since it's the most recent attempt and the one that matches the current state of the app ("running").

hmm..I see your point @vanzin .According to your prescription then, later attempts before earlier attempts is the correct order.Did you consider all possibilities?speculative execution??
Also your thoughts on for case when a1 is incomplete and a2 has completed, if a1 start at same time as a2 (if not later by definition of attempts) Especially as that is the case @tgravescs  argues in his SPARK-8593 that a1 is incomplete, but a2 has completed.and a2 does not show as order has prevented that.Hence preferred sort order to be completed before running, but if both are completed or both are running sorted by descending start time.please let me know your thoughts? thanks for your time!

Did you consider all possibilities?speculative execution??

There's no such thing as speculative execution of app attempts.

if a1 start at same time as a2 (if not later by definition of attempts)

That should never happen (see above, attempts are only started after a previous attempt has finished).

Especially as that is the case @tgravescs argues in his SPARK-8593

No it's not. The case he described is when the first attempt finished executing (i.e. there's no live SparkContext anymore) but the log file where the attempt was writing its logs wasn't properly closed. There are never two attempts executing at the same time, and it's a safe assumption that if there is more than one attempt, all attempts except the most recent one (i.e. the one with the most recent start time) are not running.

Merged build triggered.

Merged build started.

Test build #37161 has started for   PR 7253 at commit 548c753.

Merged build triggered.

Merged build started.

thanks @vanzin convinced, updated to have descending start time for all cases.
thanks for the conversation @vanzin

Test build #37162 has started for   PR 7253 at commit 716e0b1.

Test build #37161 has finished for   PR 7253 at commit 548c753.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test build #37162 has finished for   PR 7253 at commit 716e0b1.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Jenkins retest this please.

Merged build triggered.

Merged build started.

Test build #15 has started for   PR 7253 at commit 716e0b1.

Merged build triggered.

Merged build started.

Test build #37236 has started for   PR 7253 at commit 716e0b1.

Test build #15 has finished for   PR 7253 at commit 716e0b1.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test build #37236 has finished for   PR 7253 at commit 716e0b1.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Looks like a legit test failure.
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37236/testReport/org.apache.spark.deploy.history/FsHistoryProviderSuite/log_cleaner/

Merged build triggered.

Merged build started.

Test build #37262 has started for   PR 7253 at commit 874dd80.

Test build #37262 has finished for   PR 7253 at commit 874dd80.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

done @vanzin thanks

Code looks good now, thanks! Could you update the PR title and description to match the actual change? e.g.
[SPARK-8593] [core] Sort app attempts by start time.

This makes sure attempts are listed in the order they were executed, and that the
app's state matches the state of the most current attempt.

done @vanzin thanks

ping @andrewor14 @srowen

LGTM, will merge shortly if there are no objections into master and 1.4.

Looks fine, feel free to merge it.

thanks @vanzin @srowen @andrewor14 !


pax-logging-api should not bundle "foreign" Java classes.

Analysing the Export-Package directive from the MANIFEST.MF of pax-logging-api-2.2.2.jar it appears that the Jar is bundled with many "foreign" classes that does not belong to org.ops4j.pax.logging project
I believe this is a bad practice, as it break the Single Responsibility principle, i.e. every class, module, or function in a program should have one responsibility/purpose in a program.
And hereby the library is taking over the responsibility of many other libraries.
Hereby below the list of "foreign" packages containing "foreign" classes:

Package Name
Version

org.apache.avalon.framework.logger
4.3.0

org.apache.commons.logging.impl
1.0.4

org.apache.commons.logging.impl
1.1.3

org.apache.commons.logging.impl
1.2.0

org.apache.commons.logging
1.0.4

org.apache.commons.logging
1.1.3

org.apache.commons.logging
1.2.0

org.apache.juli.logging
5.5.28

org.apache.juli.logging
6.0.18

org.apache.juli.logging
7.0.94

org.apache.juli.logging
8.5.40

org.apache.juli.logging
9.0.58

org.apache.log4j.config
1.2.22

org.apache.log4j.helpers
1.2.22

org.apache.log4j.or
1.2.22

org.apache.log4j.pattern
1.2.22

org.apache.log4j.spi
1.2.22

org.apache.log4j.xml
1.2.22

org.apache.log4j
1.2.22

org.apache.logging.log4j.message
2.13.3

org.apache.logging.log4j.message
2.14.1

org.apache.logging.log4j.message
2.15.0

org.apache.logging.log4j.message
2.16.0

org.apache.logging.log4j.message
2.18.0

org.apache.logging.log4j.message
2.9.1

org.apache.logging.log4j.simple
2.13.3

org.apache.logging.log4j.simple
2.14.1

org.apache.logging.log4j.simple
2.15.0

org.apache.logging.log4j.simple
2.16.0

org.apache.logging.log4j.simple
2.18.0

org.apache.logging.log4j.simple
2.9.1

org.apache.logging.log4j.spi
2.13.3

org.apache.logging.log4j.spi
2.14.1

org.apache.logging.log4j.spi
2.15.0

org.apache.logging.log4j.spi
2.16.0

org.apache.logging.log4j.spi
2.18.0

org.apache.logging.log4j.spi
2.9.1

org.apache.logging.log4j.status
2.13.3

org.apache.logging.log4j.status
2.14.1

org.apache.logging.log4j.status
2.15.0

org.apache.logging.log4j.status
2.16.0

org.apache.logging.log4j.status
2.18.0

org.apache.logging.log4j.status
2.9.1

org.apache.logging.log4j.util
2.13.3

org.apache.logging.log4j.util
2.14.1

org.apache.logging.log4j.util
2.15.0

org.apache.logging.log4j.util
2.16.0

org.apache.logging.log4j.util
2.18.0

org.apache.logging.log4j.util
2.9.1

org.apache.logging.log4j
2.13.3

org.apache.logging.log4j
2.14.1

org.apache.logging.log4j
2.15.0

org.apache.logging.log4j
2.16.0

org.apache.logging.log4j
2.18.0

org.apache.logging.log4j
2.9.1

org.jboss.logging
3.3.0.Final

org.jboss.logging
3.4.3.Final

org.osgi.service.log.admin
1.0.0

org.osgi.service.log.stream
1.0.0

org.osgi.service.log
1.4.0

org.osgi.service.log
1.5.0

org.slf4j.event
1.7.36

org.slf4j.helpers
1.4.3

org.slf4j.helpers
1.5.11

org.slf4j.helpers
1.6.6

org.slf4j.helpers
1.7.36

org.slf4j.spi
1.4.3

org.slf4j.spi
1.5.11

org.slf4j.spi
1.6.6

org.slf4j.spi
1.7.36

org.slf4j
1.4.3

org.slf4j
1.5.11

org.slf4j
1.6.6

org.slf4j
1.7.36

Thanks @mattrpav for your view.
I agree. Adding to the main discussion at #518, I'll emphasize again - from pure OSGi point of view, you should deal with packages and you may get into a trap of thinking that a bundle is as equally important as a package. The practice shows that you have to give caesar what belongs to caesar and:

indeed, you should think about packages in OSGi, but you should be aware of the source (provider) of the package you're going to be wired to - after all you also narrow down the versions of imported packages
but you should also think about the bundles - you don't want thousands of bundles with strict, separate package namespaces - you don't want tens of guava libraries in your OSGi runtime (trust me - I've seen it)

The point is that you can't avoid mixing packages in single bundle - both because there are such bundle around (have you look at the bundles that are supposed to provide javax.* packages? That's a mess!) and because you want some form of control of what you actually deploy.
Let's imagine for a while that we follow your (theoretically sane suggestion in the spirit of pure OSGi) advice and have pax-logging-api export only org.ops4j.pax.logging.* package. Then you'd have to deploy (assuming they are correct and not competing) twenty six other bundles:

1 Avalon
3 commons-logging (1.0.x, 1.1.x, 1.2.x)
5 Apache Tomcat/JULI (5.5.x - 9.0.x)
1 Log4j1
6 Log4j2 (2.13 - 2.18) - but add 2.19 and 2.20
2 JBoss Logging
bundle with org.osgi.service.log.admin
bundle with org.osgi.service.log.stream
2 bundles with org.osgi.service.log
4 bundles with org.slf4j - but add 2.0 too

Again, I'm not sure if you've noticed, but OSGi spirit tells you that you should craft your bundle without taking much care about the bundle version, but with strict control over your package versions.
So the OSGi way is to have:

com.example/my-service bundle (available from Maven for example) at version 1.0 with packages like:

com.example.api 1.0
com.example.impl 1.0

com.example/my-service bundle (available from Maven for example) at version 2.4 with packages like:

com.example.api 1.1
com.example.impl 1.1

The above example shows that the packages are fully compatible from consumer point of view even if the Maven version is completely different.
That's how for example these libraries are created:

https://repo1.maven.org/maven2/org/osgi/osgi.core/7.0.0/
https://repo1.maven.org/maven2/org/osgi/osgi.core/8.0.0/

See - major version upgrade, but some packages have only micro version difference:

7.0.0 exports org.osgi.util.tracker;version="1.5.2"
8.0.0 exports org.osgi.util.tracker;version="1.5.3"

On the other hand, the most popular (IMO) way to create OSGi bundles is org.apache.felix/mave-bundle-plugin which analyzes your jar and exports all (customizable) eligible packages with version coming from Maven version of the project. This is where you end up with tens of Guava libraries, exporting the same packages with new major version, but which are in fact compatible.
That's why clever people before me (I'm only a janitor of Pax Logging project...) decided to do what they did. I've accepted, appreciated and understood the pragmatic approach - you do what has to be done.
So no way - your suggestion would work in ideal world, where:

EVERY Java developer in the world would create their META-INF/MANIFEST.MF consciously without the defaults
you resolve your bundles using OSGi repository (which is a package → resource mapping database)

But fortunately (yes) we don't live in such ideal world ;)

thank you for enlightening me regarding the downside to have separate all implementations kept in separate bundles.
I still see a major downside of such approach:
Let's imagine you have new Common Vulnerabilities and Exposures for one or several packages that are not part of this project and that are bundled in pax-logging-api.
If the Single Responsibility principle is respected, then the maintainer just need to replace the bundle that is vulnerable with a new version with the fix. Whereas hereby, the maintainer will have to open an issue on pax-logging-api project to request a port!

Let's imagine for a while that we follow your (theoretically sane suggestion in the spirit of pure OSGi) advice and have pax-logging-api export only org.ops4j.pax.logging.* package. Then you'd have to deploy (assuming they are correct and not competing) twenty six other bundles:

To my opinion, not really 26 other bundles,  all package imports can be made optional, this lets the decision to the packager which logger implementation it needs in the application, as in fact in real world no decent applications uses 8 different logger flavours at the same time...

thank you for enlightening me regarding the downside to have separate all implementations kept in separate bundles.
I still see a major downside of such approach: Let's imagine you have new Common Vulnerabilities and Exposures for one or several packages that are not part of this project and that are bundled in pax-logging-api. If the Single Responsibility principle is respected, then the maintainer just need to replace the bundle that is vulnerable with a new version with the fix. Whereas hereby, the maintainer will have to open an issue on pax-logging-api project to request a port!

True - this was the case during Log4J apocalypse - I was releasing 5 Pax Logging versions a day for several days.
But I wouldn't switch to other model anyway ;) Similar (but much simpler) model is with your WAR files deployed to, say, Tomcat (or other app server) - how many not-yours libraries do you have in WEB-INF/lib? How many of them do you put to "common classloader" (in Tomcat), so your WAR is thin? Sometimes it's better to embed it, so you have more control.
But again - while for example, commons-logging uses /META-INF/services/org.apache.commons.logging.LogFactory service simply ships own org.apache.commons.logging.LogFactory implementation delegating to org.ops4j.pax.logging.PaxLoggingManager.
It's even more visible with Log4j1 API - if you switch from putting org.apache.log4j package inside pax-logging-api to separate log4j bundle, you'd load org.apache.log4j.Category from log4j1 and you'd end up with original org.apache.log4j.LogManager running its own static block to discover different things. We have to replace this behavior with one that allows you to redirect Log4j1 API calls to Logback backend! So we have to replace this class/package instead of asking Log4j1 maintainers (...) to accept our PR that does the OSGi magic.

Let's imagine for a while that we follow your (theoretically sane suggestion in the spirit of pure OSGi) advice and have pax-logging-api export only org.ops4j.pax.logging.* package. Then you'd have to deploy (assuming they are correct and not competing) twenty six other bundles:

To my opinion, not really 26 other bundles, all package imports can be made optional, this lets the decision to the packager which logger implementation it needs in the application, as in fact in real world no decent applications uses 8 different logger flavours at the same time...

True, but as I said - we not only want to give pax-logging-api access to some external packages - we have to replace some classes with ones that delegate to OSGi machinery (wiring, trackers, ...). If we simply use original classes from, say, JBoss Logging, we'd delegate to its behavior, which is mostly classpath scanning in search for available Logging implementations - but hey, there's no CLASSPATH in OSGi ;)
And also, for example you deploy two bundles that have (because of the default behavior of maven-bundle-plugin):

Import-Package: org.slf4j; version="[1.7,2.0)"
Import-Package: org.slf4j; version="[2.0,3.0)"

Actually from API point of view, there's no change between SLF4J 1 and 2. So pax-logging-api exports both versions, while with pure OSGi approach you'd have to install two slf4j-api bundles. But 1.7 would try to load org.slf4j.impl.StaticLoggerBinder from the CLASSPATH and 2.0 would search for /META-INF/services/org.slf4j.spi.SLF4JServiceProvider - mind that java.util.ServiceLoader in OSGi works reliably only with some bytecode TCCL magic done by Aries SPI-Fly...


Fibaro Single Switch FGBHS-213

Hi grover,
Thanks a lot for your job :)
Works perfectly with Fibaro Single Switch FGBHS-213.

Hi @sebpi33,
Is it still working for now?
Could you please share which versions of Node.js, npm, homebridge and homebridge-ranger you have to achieve it working with the described switch?


Log/Span load reduction

Evaluate what causes a lot of load; e.g. verify encsig creates a lot of load on the taker, and see to disable the instrumentation to specific code parts.
This query may help to evaluate what is creating load.

I'd be for removing (or adding a target that's disabled by default) everything from this file:
https://github.com/itchysats/itchysats/blob/master/daemon/src/shared_protocol.rs#L20

Three initial targets:

verify_cet_encsig
successful pings
successful taker offers

I think this might be fixed with #2519, but it's worth keeping an eye on in Grafana

I would tentatively say that this is fixed, as long as we disable --verbose-spans. I would propose we test this on mainnet next update/restart, as the current projected usage will be 110GB, but earlier it was 80GB only. I suspect a lot of this is the ping peer spans which would be disabled with --verbose-spans off.


add make docker_test to run tikv test in docker environment

What is changed and how it works?

Issue Number: Close #14677
What's Changed:

Add a make option "make docker_test" to run test in docker. Also make necessary changes to enable running test in docker.

Related changes

PR to update pingcap/docs/pingcap/docs-cn:
Need to cherry-pick to the release branch

Check List
Tests

No code

Release note
None

@tonyxuqqi Could it be cherry picked to release-6.5 branch?

There is a error message:
docker run -i -v /workspace/tikv:/tikv \
        "pingcap/tikv_dev":"latest" \
        make test
./scripts/test-all -- --nocapture
bash: git: command not found
make[1]: Entering directory '/tikv'

There is a error message:
docker run -i -v /workspace/tikv:/tikv \
        "pingcap/tikv_dev":"latest" \
        make test
./scripts/test-all -- --nocapture
bash: git: command not found
make[1]: Entering directory '/tikv'

I updated it and there's git fallback argument.  It can work without git.

/test

/review default

/review the changes are mostly about dockerfile, please review it.


[Bug]: ray version problem

Your current environment
ray= 2.10.0
🐛 Describe the bug
New additions in #5748 from ray.exceptions import ActorDiedError, but only in ray>=2.11.0, Now ray =2.9 in the requirements-cuda.txt file, loading the model will fail after the source code is compiled

ActorDiedError is available only in ray >=2.11.0 versions . The current ray>=2.9 raises an error

并且ray>2.10.0版本后，好像不再支持python=3.8

And after ray>2.10.0, python=3.8 is no longer supported

Closed #6033 as completed via #6039.


Add functionality to deploy caasp4 on openstack

This PR adds scripts and content to deploy caasp4 on openstack.
See make all-caasp4os.
It creates a docker image with the caasp4 product, spawns infra by terraform,
bootstraps the cluster with skuba, and configures and prepares cluster for cap.
Currently it fails on install_scf.sh, since the scripts/include/common.sh containerid/ip are not correctly set up.
For moving forward we would need to refactor the rules into steps that are k8s platform agnostic.
This can be achieved by saving the k8s external info (external ip, nfs server, etc) on a configmap on the cluster, see example at the end of scripts/caasp4_deploy.sh, and thinning scripts/include/common.sh and creating scripts/include/<platform>.sh
This would mean a change of the structure of the repo.

For moving forward we would need to refactor the rules into steps that are k8s platform agnostic.

Sure, makes perfectly sense. I would just keep the simplest use case as default (so we keep the local approach as the one expected with plain default usage)

This can be achieved by saving the k8s external info (external ip, nfs server, etc) on a configmap on the cluster, see example at the end of scripts/caasp4_deploy.sh, and thinning scripts/include/common.sh and creating scripts/include/<platform>.sh
This would mean a change of the structure of the repo.

Sounds good to me!


Inability to edit comment to add 🙏 on Codeberg while used to be able it seems

Description
Concerned comment: LemnosLife/Website/issues/51#issuecomment-1457
Comment it used to be fine: LemnosLife/Website/issues/51#issuecomment-1453
Gitea Version
Not read.
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
Not read.
Database
None

Maybe related to #19.


Frontend web development html css js

Description 📜
I have created codes for different CSS loaders which can be used by just copying and pasting it at the right place.
Fixes #2419

Type of change 📝

[ ] Au#dio (Should be in mp3 format Includes speech clarity, Concise ,Low distortion)
[ ] Vi#deo (Animations, screen-recordings, presentations and regular explanatory films are all possibilties etc)
[x] Documentation (Content Creation in the form of codes or tutorials)
[ ] Other (If you choose other, Please mention changes below)

Domain of Contribution 📊

[ ] Android Dev #(Flutter)
[ ] Android Dev #(Java)
[ ] Android Dev #(Kotlin)
[ ] Backend Dev #(Java)
[ ] Backend Dev #(.NET)
[ ] Backend Dev #(PHP)
[ ] Backend Dev #(Python)
[ ] C/#CPP
[ ] Competitive #Programming
[ ] Cyber #Security
[ ] DS#A
[ ] Data#base
[ ] Datascience with #Python
[ ] Datascience with #R
[x] Frontend Dev HTML/CSS/JS
[ ] Frontend Dev #React/Angular/Vue
[ ] Go#lang
[ ] Interview #Prep
[ ] Java_#Domain
[ ] Java#Script
[ ] ME#RN
[ ] Machine #Learning
[ ] Open #Source
[ ] Python_#Domain
[ ] Ru#st
[ ] Statis#tics
[ ] UI/#UX

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

@praveenscience Please Review the changes.

Please do the same for all the other files too.

Done Sir.

Looks good to me. 👍

Thank You Sir.

@S07K It looks good to me also just try to add reference from where you have referred and created this documentation. Add references at the bottom of the each documentation as it is mentioned by the GWOC Team .

Yes Sir, I know and I have mentioned it pls check.


docs: Add project documentation

Description
This PR adds project documentation.

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


version api does not report useful info

Calling /api/version (or /docs/rest#!/version/getVersion) produces "Could not get the branch information" in all environments I tested.

Assigning to @simong for feedback.

The UI build-info.json file gets stored at /opt/3akai-ux/build-info.json. However hilary gets configured with /opt/3akai-ux/optimized which is causing it to try to gather the information from GIT. As there's no git repository to retrieve the information from, it's throwing an error.

I attached a commit that fixes this

Looks good, just one minor style issue.

Pushed follow-up


Add namespace to generated alert rules

As discussed in https://github.com/pyrra-dev/pyrra/issues/38#issuecomment-1320345859
Namespace is already shown in the UI/frontend and can be used to filter by which is very useful.
Having the namespace label in the generated alerts as well would keep it consistent and help a lot with routing in alertmanager as most alerts we use are grouped by namespace + other labels.

Actually, we might want to add this to a v0.5.x

Any updates on when this might be implemented?

Any chance of adding this in the next release? @metalmatze (v0.8.x that is). I'm not sure how much work this will require to implement, but hopefully it's a quick fix. 😃


BreadCrums class/method names are too long

VsCode 1.27.2
Extension 1.16.1
Class names

It should have only the class name GenMockEntityUseCaseBuilder<TEntity> instead InterfaceFluentApi.Extensions.GenMockEntityUseCaseBuilder<TEntity>.
Method Names

It should have something like NavigationConfig(GenMockEntityUseCaseBuilder...)
And do ellipsis for long parameters names.
In General when names too long why not to do ellipsis on parameters or generic arguments as well.

Cannot reproduce with current release.


feat: add CreatePartition() method

Description
This PR implements new CreatePartition() method that creates new partition for message and transaction table.
Checklist

[x] Targeted PR against correct branch.
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Wrote unit tests.
[x] Re-reviewed Files changed in the Github PR explorer.

I've improved the code by removing some duplication that was present. I've also added a v3/migration.sql file that contains all the queries that should be run to migrate from a v2 database to the (upcoming) v3 database. The only thing I don't know how to add is the partition. @MonikaCat you might want to investigate that

Hi @RiccardoM I think it's not possible to turn a regular table into partition table, should we alternatively add the migration script which I made under the "migrate" cmd ?

I've improved the code by removing some duplication that was present. I've also added a v3/migration.sql file that contains all the queries that should be run to migrate from a v2 database to the (upcoming) v3 database. The only thing I don't know how to add is the partition. @MonikaCat you might want to investigate that

Hi @RiccardoM I think it's not possible to turn a regular table into partition table, should we alternatively add the migration script which I made under the "migrate" cmd ?

Yes please add it to this branch so I can check it out

@huichiaotsou @RiccardoM Yes it's not possible to turn regular table into partitioned table, hence we created the script to handle the migration process. I added it to migrate cmd so it can be easily performed by users, let me know what you think, thx

Superseeded by #50


kubeadm-upgrade: fix shell message markdown

also update the message to not have an error about DS Pods.
/sig cluster-lifecycle
@kubernetes/sig-cluster-lifecycle-pr-reviews

/approve


[ESP32 DevKit C v4] [AT command] [MQTT] [Thingsboard] - Disconnected/Error at command AT+MQTTSUB

I use the board 'ESP32 NodeMCU DevKit C v4' and I flashed it using the following firmware 'ESP32-WROOM-32_AT_Bin_V<IP_ADDRESS>' (http://download.espressif.com/esp_at/firmware/ESP32/ESP32_WROOM/ESP32-WROOM-32_AT_Bin_V<IP_ADDRESS>.zip
). I use a Beaglebone Enhanced to run AT commands throught serial port UART1.
I have an issues with the AT commands for MQTT connection; in particular when I try to subscribe to a topic of my IoT platform Thingsboard. In the following there is the sequence of MQTT commands used.
[1] User configuration
AT+MQTTUSERCFG=0,1,"ESP32_module",<"ACCESS TOKEN of IoT device">,"",0,0,""
OK
[2] Connection configuration
AT+MQTTCONNCFG=0,60,0,"lwt_topic","lwt_message",1,0
OK
[3] Connect to the platform
AT+MQTTCONN=0,"thingsboard.iotprojects.eu",9082,0
+MQTTCONNECTED:0,1,"thingsboard.iotprojects.eu","9082","",0
OK
[4] Check connection
AT+MQTTCONN?
+MQTTCONN:0,4,1,"thingsboard.iotprojects.eu","9082","",0
OK
[5] Subscribe to topic
AT+MQTTSUB=0,"v1/devices/me/telemetry",1
+MQTTDISCONNECTED:0
ERROR
The assumptions that I have done are: (following the guide ==> https://docs.espressif.com/projects/esp-at/en/latest/AT_Command_Set/MQTT_AT_Commands.html)
===== [1] User configuration =====

1° parameter ==> : 0
2° parameter ==> : 1 (MQTT over TCP)
3° parameter ==> <"client_id">: "ESP32_module" (chosen arbitrarily) it's optional?
4° parameter ==> <"username">: <"ACCESS TOKEN of IoT device">
5° parameter ==> <"password">: ""
6° parameter ==> <cert_key_ID>: 0
7° parameter ==> <CA_ID>: 0
8° parameter ==> <"path">: ""
===== [2] Connection configuration =====
1° parameter ==> : 0
2° parameter ==> : 60
3° parameter ==> <disable_clean_session>: 0
4° parameter ==> <lwt_topic>: "lwt_topic" (is it unique option??)
5° parameter ==> <lwt_message>: "lwt_message" (is it unique option??)
6° parameter ==> <lwt_qos>: 1
7° parameter ==> <lwt_retain>: 0
===== [3] Connect to the platform =====
1° parameter ==> : 0
2° parameter ==> <"host">: "thingsboard.iotprojects.eu"
3° parameter ==> : 9082
4° parameter ==> : 0
===== [5] Subscribe to topic =====
1° parameter ==> : 0
2° parameter ==> <"topic">: "v1/devices/me/telemetry"
3° parameter ==> : 1 (because it is the first topic)

I need to understand if my configuration is wrong and/or if some parameters of AT commands above indicates is wrong.
If there is anyone who has already worked with the AT commands of the ESP32, please share me some examples to understand better how work it.

@Nicrus86 please take a look about some AT+MQTT examples:

AWS broker: https://blog.csdn.net/espressif/article/details/105045610
Azure IoT: https://blog.csdn.net/espressif/article/details/103736743
QCloud MQTT broker: https://blog.csdn.net/espressif/article/details/104714464
Alibaba MQTT broker: https://blog.csdn.net/espressif/article/details/107367189

You can capture the packets to analysis why the MQTT Subscribe failed


Rename conversion task slug from 'preanalysis' to 'analysis'

RHINENG-10825
Renames slug of conversion preanalysis task to analysis.

[x] Severity maps, fixtures, warning constants renamed
[ ] Needs backend PR

Note: just a draft, we will see if and when we will move forward with this, no specific priority

:exclamation: Outdated dependencies error

Installed version of @redhat-cloud-services/frontend-components-config (4.7.3) is older than required version (6.0.0)

MR for advisor-backend !891 was merged, but I am not sure if db fixtures updated, or if that has to be done manually when we have this MR - to make it as smooth transition as we can.
hmm thinking about it I could probably make this MR backwards compatible so it can be merged anytime and it can work with both slugs, the old and new one :thinking:

Hey, thanks for the PR @andywaltlova. I have tested it locally and I see that the quickstart button has returned for the pre-conversion task which is great. There are some linter issues though: please run npm run lint and npm run test and push the changes again to fix them.


YUV-to-RGB Conversion Shader

The YUV to RGB colorspace conversion should ideally be a shader program and executed on the GPU. This should make 4K video resolution playback feasible. Here's a working OpenGL example http://www.fourcc.org/source/YUV420P-OpenGL-GLSLang.c. BTW, YUV-Canvas is great, many thanks.

Nevermind, looks like YCbCr.js isn't used.

The WebGL shader is used when supported and yes it makes a big difference in performance. :) The in-JS conversion is used only if WebGL is unavailable (old browser versions or problematic video drivers) or explicitly disabled.


Make an option to run task groups sequentially instead of in-parallel

Would be great to add "sequential" option to task groups, such that they can be run one after another instead of in-parallel. The usecase for this is that sometimes we need to run a couple of conversion steps, e.g. from nemo -> hf and then from hf -> trtllm and these steps need different containers. We also sometimes need to run inference and then do evaluation in different containers where evaluation is only taking a small time. Currently we run those steps by launching separate tasks, which will request separate nodes and thus might stay in slurm queue longer. Would be great to have an option to have multiple sequential sruns in the same sbatch script so that we can use different containers, but reuse the node.

I will pick this up next.


Fix detection of the class of the initial entity

If an entity is a Hibernate proxy, no entity descriptor could be found for the entity proxy's class before. I now use Hibernate.getClass(entity) to let Hibernate extract the class of the underlying entity.
Do you mind a release?

Sure, the 6.3.1 release is in progress: https://github.com/arey/hibernate-hydrate/actions/runs/6106357473

There are some failures but artefacts looks like to be upload. We have to wait if they appears in Maven Central.

Thanks! The upload to Maven Central succeeded.

Yes I see it: https://repo1.maven.org/maven2/com/javaetmoi/core/javaetmoi-hibernate6-hydrate/6.3.1/


Extended plugins section

Extended plugins section in README.md

Ready for review, @grabbou

Good job, thanks!


default eslint config

hello! Is it possible to point to a default eslint config? I have a scratch folder where I like to play around with various languages so it's a mess and doesn't have a proper project structure, linter config, etc.
Is it possible to have a 'fallback' eslint config? Similar to this, thanks!
edit: the current behaviour is it throws this error if there's no eslint config in the current CWD.
Error executing vim.schedule lua callback: ...e/pack/packer/start/null-ls.nvim/lua/null-ls/helpers.lua:18: failed to decode json: Vim:E474: Unidentified byte: Error: No ESLint configuration found in /home/elianiva/dev/scratch

The ideal behavior would be to use a local ESLint config file if it's present but fall back to a default otherwise, right?
If so, it should be possible, since ESLint has a --config flag to specify the path to a config (annoyingly, it doesn't seem to work with eslint_d, but I'll open up an issue). We'd just have to check the root directory for a config file on setup and modify the arguments accordingly. You'd also have to modify your tsserver root directory settings to get it to attach in non-project directories, I think, but I imagine you've already done that if you're using a scratch folder.
From your error message, it looks like you're already using the null-ls integration, so I think I'll have the feature be a null-ls exclusive, since I want to move all the integrations to null-ls once it's a little more stable. I'll work on this and get back to you.

The ideal behavior would be to use a local ESLint config file if it's present but fall back to a default otherwise, right?

yep, I had similar thing when I was using EFM

I think I'll have the feature be a null-ls exclusive, since I want to move all the integrations to null-ls once it's a little more stable

That sounds good to me (null-ls is super cool btw :)

Thanks for the positive feedback! The plan is to have the develop branch of this plugin be null-ls-only in preparation for the move. I'll let you know once this specific feature is available there.

The fallback functionality is available for ESLint and formatters on the develop branch, which also ripped out all of the non-null-ls code. Let me know how it works for you!

Great! Going to close this for now, then. Feel free to open up another issue if you run into any issues.


Directives missing on Arguments

Describe the bug
I'm not entirely sure if this is a bug or by design, but the wording of the magidoc config documentation makes me think it is indeed a bug. Since the documentation states "directives will be displayed where they are used"
      /**
       * The directives that should appear in the documentation.
       * When using SDL introspection, the location and definition of these directives will be displayed where they are used.
       *
       * @default []
       */
      directives: [

I have the following schema files:
https://gitlab.com/solveri/signify/-/tree/25-unify-the-validation-messages/_kt/api/src/main/resources/graphql?ref_type=heads
I have the following magidoc.mjs
export default {
  introspection: { type: "sdl", paths: ["_kt/api/build/resources/main/graphql/**/*.gqls"] },
  website: {
    template: "carbon-multi-page",
    output: "./dist/apiDocs",
    options: { directives: [{ name: "*", args: ["*"] }] },
  },
}

The most noteworthy part is how I have Directives assigned to Arguments, like so:
"""
Mutations related to Youtube resources.
"""
type YoutubeMutation {
  """
  Make a claim on a Youtube video, using the `youtubeId` and claim fields.
  """
  makeClaim(
    youtubeVideoId: String! @YoutubeVideoId
    content: String!
      @Pattern(regexp: "^placeholder$", message: "Must be fixed value - 'placeholder'")
    certificate: String!
      @Pattern(regexp: "^placeholder$", message: "Must be fixed value - 'placeholder'")
    signature: String!
      @Pattern(regexp: "^placeholder$", message: "Must be fixed value - 'placeholder'")
  ): String
}

But generating the docs, I do not see Directives added to Arguments. I do see them in the left navbar though. And previously I did see them correctly appended to fields where they are used, but not on arguments.

Reproduction
Assuming you have magidoc installed globally.
Check out this particular branch in my Open Source repo.
https://gitlab.com/solveri/signify/-/tree/25-unify-the-validation-messages/_kt/api/src/main/resources/graphql?ref_type=heads
Run the following
magidoc generate --file=_x/magidoc/magidoc.mjs
magidoc preview --file=_x/magidoc/magidoc.mjs

Logs
No response
System Info
System:
    OS: Linux 6.8 Pop!_OS 22.04 LTS
    CPU: (16) x64 Intel(R) Core(TM) i7-10875H CPU @ 2.30GHz
    Memory: 5.31 GB / 31.22 GB
    Container: Yes
    Shell: 3.7.1 - /usr/bin/fish
  Binaries:
    Node: 20.12.2 - /nix/store/74a6mmrgxzcg9axl1gmdz3j2y1bjd13f-nodejs-20.12.2/bin/node
    npm: 10.5.0 - /nix/store/74a6mmrgxzcg9axl1gmdz3j2y1bjd13f-nodejs-20.12.2/bin/npm
    pnpm: 9.4.0 - /nix/store/80k8kyb8586wq24x473fpy2l04k9dj0s-corepack-nodejs-20.12.2/bin/pnpm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 126.0.6478.61

Severity
Blocking all usage of Magidoc

Hello. Thank you for raising this. I will have a look as soon as I get some free time. This may take a couple days.
I will also correct the wording in the documentation. It is indeed misleading.

Thanks!
I hope that this functionality is added. I was super stoked today when I found magidoc and it's ability to include Directive information and their usage, which I did not get from other tools. When I saw it on fields I assumed it will work everywhere. So it was quite a downer to see they don't work on arguments.
In our case we want to show all Directives, so that they serve a dual purpose of providing extra functionality, while at the same time also serving as informative bits of documentation. This would allow us to keep our code DRY and not need to repeat stuff, like validation messages in our docs and also in our validation logic.
So far magidoc is looking like the best tools for our use-case, but if this Directive logic continues to be missing on arguments then unfortunately it will prevent us from getting the needed value out of it fully.
Looking forward to your findings and updates :slightly_smiling_face:

This is now supported as of 6.0.0. Give it a try a let me know what you think!


cadCAD Version: 0.4.28 doesn't work

Hi,
I'm using the cadCAD for a while, and I have some simulation with it on my old machine. Today, I installed it on another machine which I think the installed version is now the latest version. but it doesn't work! At first, I thought maybe it's because of different versions of python, so I made sure both machines are using the same version(3.8.10), but it didn't solve the problem. Then I checked with the tutorial code, the first one, and I got this error:
                  ___________    ____
  ________ __ ___/ / ____/   |  / __ \
 / ___/ __` / __  / /   / /| | / / / /
/ /__/ /_/ / /_/ / /___/ ___ |/ /_/ /
\___/\__,_/\__,_/\____/_/  |_/_____/
by cadCAD

cadCAD Version: 0.4.28
Execution Mode: local_proc
Simulation Dimensions:
Entire Simulation: (Models, Unique Timesteps, Params, Total Runs, Sub-States) = (0, 0, 0, 0, 0)
Execution Method: local_simulations
Traceback (most recent call last):
  File "test.py", line 64, in <module>
    raw_system_events, tensor_field, sessions = simulation.execute() # The `execute()` method returns a tuple; its first elements contains the raw results
  File "/home/user/.local/lib/python3.8/site-packages/cadCAD/engine/__init__.py", line 157, in execute
    final_result = get_final_results(simulations_results, partial_state_updates, eps, sessions, remote_threshold)
  File "/home/user/.local/lib/python3.8/site-packages/cadCAD/engine/__init__.py", line 121, in get_final_results
    for sim_result, psu, ep in list(zip(simulations, psus, eps)):
TypeError: 'NoneType' object is not iterable ```

@VHPL-UIS to confirm, you were running the following tutorial? https://github.com/BlockScience/cadCAD-Tutorials/tree/master/01 Tutorials/robot-marbles-part-1

@VHPL-UIS were you using Jupyter Notebook? I find it works in Lab but not Notebook, and for that reason think perhaps it's an issue with multiprocessing - that was one of the more recent refactors made to cadCAD. @JEJodesty any ideas?

@BenSchZA No, I just copied the code from the notebook into a .py file and tried to run it.
I have the 0.4.23 and it works fine.

Having the same issue in jupyter lab.

yup having trouble running https://github.com/cadCAD-org/demos/tree/master/tutorials/robots_and_marbles/robot-marbles-part-1 with 0.4.28

It works fine with 0.4.23

It looks like this is due to config changes in v.0.4.28. You have to use the configs attribute from Experiment instead of from cadCAD.config. See here.

Having same issue, with same tutorial. With help from @BenSchZA (thanks 🙏 ) I had to make some changes to the code block in the link above:
from cadCAD.configuration.utils import config_sim
from cadCAD.configuration import Experiment
c = config_sim(sim_config_dict)
exp = Experiment()
exp.append_model(
    model_id = 'sys_model_1', # System Model - OPTIONAL
    initial_state = genesis_states, # System Model
    partial_state_update_blocks = partial_state_update_blocks, # System Model
#    policy_ops = ..., # System Model
    sim_configs = c, # Simulation Properties
)
configs = exp.configs

^ thats for block #6 of this tutorial https://github.com/cadCAD-org/demos/blob/master/tutorials/robots_and_marbles/robot-marbles-part-1/robot-marbles-part-1.ipynb

Thanks for the update and sorry for the delay
@VHPL-UIS @susmit @daithi-coombes
despite the title of the issue, it entails updating not only robot-and-marbles-part-1 to run on 0.4.28, but also all cadCAD demos
@VHPL-UIS @susmit
I suggest:

updating your system model using the CHANGELOG which contain links to documentation
update using the -cadcad-post-processing-modifications in addition to as  suggested by @meiji163
submitting an issue to update all cadCAD demos to run on 0.4.28 which includes robot-and-marbles-part-1

@LinuxIsCool @BenSchZA
I suggest:

if there is still an issue with jubyter lab or notebook after the steps above are complete, submit a jubyter lab and/or notebook specific issue(s) for within this repo


Unable to bind on_focus to MDTextField in Python

As the title says. I'm only able to bind on_focus in kvlag.
Binding on_text_validate to MDTextField in python works find though.
Minimal Reproducible Code:
from kivy.uix.boxlayout import BoxLayout
from kivy.clock import Clock
from kivymd.uix.textfield import MDTextField
from kivymd.app import MDApp

class X(BoxLayout):
    def __init__(self, **kwargs):
        super(X, self).__init__(**kwargs)
        Clock.schedule_once(self._late_init_)

    def _late_init_(self, dt):
        etf = MDTextField()
        etf.bind(on_focus=self.focus_fn)
        self.add_widget(etf)

    def focus_fn(self):
        print('focused')

class App(MDApp):
    def build(self):
        b = BoxLayout()

        b.add_widget(X())

        return b

App().run()

@lemousehunter Yes, it looks like the on_focus event only works in kv files.

confirm .bind and fbind doesnt work with the focus property

Use bind(focus=self.foo) instead of on_focus

from kivy.lang import Builder

from kivymd.app import MDApp

KV = '''
BoxLayout:
    padding: dp(10)

    MDTextField:
        id: textfield
        pos_hint: {"center_y": .5}

'''

class Test(MDApp):
    def __init__(self, **kwargs):
        super().__init__(**kwargs)
        self.screen = Builder.load_string(KV)

    def build(self):
        self.screen.ids.textfield.bind(
            focus= lambda *args: print('focused'),
        )
        return self.screen

Test().run()

@HeaTTheatR I need to mention this is not a KivyMD bug. Kivy docs suggested to use bind(focus=...) for callbacks
https://kivy.org/doc/stable/api-kivy.uix.textinput.html#usage-example

BoxLayout:
    padding: dp(10)

    MDTextField:
        id: textfield
        pos_hint: {"center_y": .5}
        on_focus:
            print(f"self.focus = {self.focus}")

I am closing this issue because it is not related to KivyMD library: if you replace the MDTextField class with the TextInput class, the problem remains.

I am closing this issue because it is not related to KivyMD library: if you replace the MDTextField class with the TextInput class, the problem remains.


Problem building on Docker 1.13.1

I'm having issues building using Docker 1.13.1 (ie: using make run).
Looks like the base image Dockerfile is trying to delete /run wholesale, which is failing due to the presence of /run/secrets, a feature present in Docker >= 1.13.
I have the following quick and dirty patch which fixes it, just felt like opening an issue would be better so that it can be properly adapted to the build process as needed.
diff --git a/images/01-base/Dockerfile b/images/01-base/Dockerfile
index a8311b12..7b08ce5b 100644
--- a/images/01-base/Dockerfile
+++ b/images/01-base/Dockerfile
@@ -4,8 +4,7 @@ RUN ln -s /dev/null /etc/udev/rules.d/80-net-name-slot.rules
 RUN rm /sbin/poweroff /sbin/reboot /sbin/halt && \
     sed -i '/^root/s!/bin/sh!/bin/bash!' /etc/passwd && \
     echo 'RancherOS \n \l' > /etc/issue && \
-    rm -rf /run \
-       /linuxrc \
+    rm -rf /linuxrc \
        /etc/os-release \
        /var/cache \
        /var/lock \
@@ -13,9 +12,9 @@ RUN rm /sbin/poweroff /sbin/reboot /sbin/halt && \
        /var/run \
        /var/spool \
        /var/lib/misc && \
+    find /run -mindepth 1 -maxdepth 1 -not -wholename '/run/dbus' -exec rm -rf {} \; && \
     mkdir -p \
        /home \
-       /run \
        /var/cache \
        /var/lock \
        /var/log \

I'm having issues building using Docker 1.13.1

What's the problem? Can you please show me a demo?

Relevant section:
DEBU[0000] Running /usr/bin/docker [build -f images/01-base/Dockerfile -t rancher/os-base images/01-base]
Sending build context to Docker daemon 33.28 kB
Step 1/11 : FROM rancher/os-rootfs
 ---> 0c325f1cb69d
Step 2/11 : RUN ln -s /dev/null /etc/udev/rules.d/80-net-name-slot.rules
 ---> Running in 0bd886593068
 ---> 397f44ec1bf2
Removing intermediate container 0bd886593068
Step 3/11 : RUN rm /sbin/poweroff /sbin/reboot /sbin/halt &&     sed -i '/^root/s!/bin/sh!/bin/bash!' /etc/passwd &&     echo 'RancherOS \n \l' > /etc/issue &&     rm -rf /run        /linuxrc        /etc/os-release        /var/cache        /var/lock        /var/log        /var/run        /var/spool        /var/lib/misc &&     mkdir -p        /home        /run        /var/cache        /var/lock        /var/log        /var/run        /var/spool &&     passwd -l root &&     addgroup -g 1100 rancher &&     addgroup -g 1101 docker &&     addgroup -g 1103 sudo &&     adduser -u 1100 -G rancher -D -h /home/rancher -s /bin/bash rancher &&     adduser -u 1101 -G docker -D -h /home/docker -s /bin/bash docker &&     adduser rancher docker &&     adduser rancher sudo &&     adduser docker sudo &&     echo '%sudo ALL=(ALL) ALL' >> /etc/sudoers
 ---> Running in 1b38c011987a
rm: can't remove '/run/secrets': Device or resource busy
rm: can't remove '/run': Directory not empty
The command '/bin/sh -c rm /sbin/poweroff /sbin/reboot /sbin/halt &&     sed -i '/^root/s!/bin/sh!/bin/bash!' /etc/passwd &&     echo 'RancherOS \n \l' > /etc/issue &&     rm -rf /run        /linuxrc        /etc/os-release        /var/cache        /var/lock        /var/log        /var/run        /var/spool        /var/lib/misc &&     mkdir -p        /home        /run        /var/cache        /var/lock        /var/log        /var/run        /var/spool &&     passwd -l root &&     addgroup -g 1100 rancher &&     addgroup -g 1101 docker &&     addgroup -g 1103 sudo &&     adduser -u 1100 -G rancher -D -h /home/rancher -s /bin/bash rancher &&     adduser -u 1101 -G docker -D -h /home/docker -s /bin/bash docker &&     adduser rancher docker &&     adduser rancher sudo &&     adduser docker sudo &&     echo '%sudo ALL=(ALL) ALL' >> /etc/sudoers' returned a non-zero code: 1
DEBU[0001] Failed running /usr/bin/docker [build -f images/01-base/Dockerfile -t rancher/os-base images/01-base]: exit status 1
FATA[0001] exit status 1
+ '[' 1 '!=' 42 ']'
+ exit 1
FATA[0345] exit status 1
make: *** [Makefile:11: dev] Error 1

@vancluever Can't reproduce this issue.Could you please give more detail such as uname -a & docker info. Maybe it's a problem relate to:
moby filesystem issue
redhat filesystem.

Looks like the base image Dockerfile is trying to delete /run wholesale, which is failing due to the presence of /run/secrets, a feature present in Docker >= 1.13.

Those secrets are only used when deploying a service that uses a secret (--secret ....). You may be running the Red Hat fork of Docker, which has the Add-RHEL-super-secrets-patch, and definitely can cause issues like this; https://github.com/projectatomic/docker/commit/4402c09586c72e0c32b90d72bd24304f609e2b7a#diff-ea22bb26655e758dc94c291dbaee0e76R728

@thaJeztah indeed I'm running on Fedora.

Any questions, please reopen this issue.


Internal UHD Display still don't work

I have tried many ways to slove my problem,but it still dodn't work. I face up with as the same problem as @breadcask,but I have tried to add -igfxmpc in boot-args, I tested for a while, it didn't work at all.

I believe you need to wait for a new version of the WhateverGreen kext to be built
Or build it yourself from the code (I have tried but failed as  am a noob to building xcode).
I understand that the -igfxmpc will not work until WhateverGreen is recompiled.
If i am wrong, then apologies.

It's the latest build of WhateverGreen, you can try it.
WhateverGreen-1.4.6-RELEASE.zip

Thanks breadcask. I could only see the 1.4.5 version on the site.
So thanks for this version.

It's the latest build of WhateverGreen, you can try it.
WhateverGreen-1.4.6-RELEASE.zip

I have test this files，but it still don’t work, thank you as the same.

I believe you need to wait for a new version of the WhateverGreen kext to be built
Or build it yourself from the code (I have tried but failed as am a noob to building xcode).
I understand that the -igfxmpc will not work until WhateverGreen is recompiled.
If i am wrong, then apologies.

I tested the latest version, but it still has no effect  (T_T)

Computer Configuration：

i7 4720HQ
GTX960M
16GB DDR3L
UHD

I uploaded my EFI over here:
https://github.com/Destro706/Opencore_Lenovo_Y50-70_UHD
It‘s with the latest Whatevergreen.kext and should work for you.
Hope it helps to get your machine up running.

I uploaded my EFI over here:
https://github.com/Destro706/Opencore_Lenovo_Y50-70_UHD
It‘s with the latest Whatevergreen.kext and should work for you.
Hope it helps to get your machine up running.

I have used the EFI compressed file you provided, only after using the config-UHDfix.plist in POST-EFI and clearing the NVRAM, I successfully booted it once, and then it can’t boot. I found that only the EFI of GeekyCoder7 can be booted and Bluetooth with other devices  works fine, except that the built-in screen cannot work. And through inspection, I found that your config.plist file has many differences with @GeekyCoder7 ‘s .

Yes, they differ.
For your Screen to work, you should only need to delete the EDID entry, and add the boot-arg mentioned before. Also, don‘t forget to copy the new Whatevergreen.kext to your kext folder. Then it should work.
My Config.plist differs in that points:

made the changes I mentioned
I deleted the kexts for Bluetooth and Wifi (the files and in the config), as I don‘t have the card and end up bootlooping. Also they are not needed by me.
I enabled FileVault 2 as I use it for encryption on my hacky.

Yes, they differ.
For your Screen to work, you should only need to delete the EDID entry, and add the boot-arg mentioned before. Also, don‘t forget to copy the new Whatevergreen.kext to your kext folder. Then it should work.
My Config.plist differs in that points:

made the changes I mentioned
I deleted the kexts for Bluetooth and Wifi (the files and in the config), as I don‘t have the card and end up bootlooping. Also they are not needed by me.
I enabled FileVault 2 as I use it for encryption on my hacky.

I really want to konw where is the EDID entry,and how can I delete it?

@holygeek00 can you try my new Config-UHD.plist?
I updated all the kexts and updated OpenCore to 0.6.4

This:
#AAPL00,override-no-connect
and the following data line is the EDID.

@holygeek00 can you try my new Config-UHD.plist?
I updated all the kexts and updated OpenCore to 0.6.4

After my continuous attempts, I finally succeeded. Thanks for everyone's help. After trying many methods, I found that using @GeekyCoder7 ‘s config-UHD-DualBoot.plist file and the @Destro706 ’s  method can drive my screen successfully.
Here are the config.plist file I use now.
Config.zip

It's the latest build of WhateverGreen, you can try it.
WhateverGreen-1.4.6-RELEASE.zip

Thank you a lot ！


New anatomy terms for various subsets of dorsomedial neurosecretory cells

Related to https://github.com/FlyBase/drosophila-anatomy-developmental-ontology/issues/120
Should dorsomedial neurosecretory cells be divided into (adult and larval) subsets (similar to DH44) for other neuropeptides, such as insulin, Ms, etc?
(No specific references - but FBrf0234450 uses subsets defined by the nueropeptide and bases this on Park, 2008)

Yes, this was partially done whilst addressing #120
Park 2008 = FBrf0210278 is not in the ontology yet, so I need to add anatomical information from this paper.


Autocomplete not returning complete object but only returns "id"

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
According to this codesandbox, we are able to return complete object as value for autocomplete, using:
onChange={([event, data]) => {
        return data;
      }}

The current implementation of autocomplete:

Prohibits to have any data set without an id key. If we do not have an id key, then the the autocomplete label does not hold value. It resets onBlur
Because of this, if I want to return a complete object for AutoComplete, I am not able to and it returns id.
We cannot add an onChange on the controller like we can in the codesandbox

Expected behavior 🤔
We should be able to add onChange on the controller wrapping the autocomplete or we should be able to return complete object from the autocomplete without label getting reset on onBlur
Steps to reproduce 🕹
Steps:
Use mock data:
export interface IParty {
  id: string;
  name: string;
  address: string;
  gstin: string;
}

const MD_PARTIES: IParty[] = [
  {
    id: '1',
    name: 'APEX PVT. LTD.',
    address:
      'ABCD',
    gstin: '1234'
  },
  {
    id: '2',
    name: 'IE AUTO PVT. LTD.',
    address: 'EFGH',
    gstin: '5678'
  },
];

  /**
   * Autocomplete prop
   * @description uses "name" key from the object as the autocomplete option label
   */
  const autoCompleteProps = {
    getOptionLabel: (option: IParty) => option.name
  };

 <AutocompleteElement
              label="Party"
              name="party"
              autocompleteProps={autoCompleteProps}
              options={MD_PARTIES}
            />

@adityatyagi you have the full object with your own onChange handler:
<AutocompleteElement autocompleteProps={{onChange: (_event, value) => console.log(value)}} />

I am happy to review any PR if you want to add additional features into the AutocompleElement


Images for different media types?

A community member wants to know how they can use the media type icons in the "Growing Commons" section of the website: "foto camera, video camera, text in a circle."
Can someone help out with how that's done? Thank you!

hey Alberto, can you comment on which icon set it used for the growing commons section?

These are icons from Noun Project, which are noted here:  https://creativecommons.org/website-icons/

It seems that Anna has already answered the question, thanks Anna.

great, thank you!