Significantly boost compile times with alternate API

The problem
phosphor-leptos is a lovely icon library. However, it has surprisingly slow compile times (even for Rust)!
This is due primarily to the fact that a full Leptos component is generated for each icon. With seven view macros and one component macro, rustc ends up having to churn through a fair amount of code for every single file.
Aside from the long compile times, this component-per-icon approach likely produces larger WASM binaries than necessary. Since each icon is a unique component (and therefore a unique function), it's unlikely the Rust compiler and downstream WASM tools will be able to combine or reduce the component code in any meaningful way.
An alternative approach
This PR introduces an alternative approach, similar to leptos-icons. That is, the library provides a single Icon component that takes an icon prop, where the prop holds the actual icon data.
This significantly reduces compile times. In my unscientific testing, a full debug build from scratch went from 92 seconds to just 17. When building a full Leptos project, phosphor-leptos took a nearly negligible amount of time compared to other dependencies (even with all features enabled). This should handily solve #12.
As discussed above, this new API should also minimize the size cost of using many different icons since the icon data is separate from the component code. I have not rigorously profiled this, however.
Drawbacks
This approach is a breaking change. It also now requires bringing the component and icon data into scope:
use phosphor_leptos::{Icon, Acorn};

view! {
    <Icon icon=Acorn />
}

However, in my opinion, the benefits significantly outweigh the drawbacks.
Implementation details
Like leptos-icons, I went with PascalCase for icon data items. It's more idiomatic to use SCREAMING_SNAKE for such const items, but it doesn't look quite as nice in my opinion. It's probably not worth breaking convention in the end (the PascalCase naming sort of hides what the icon data items are), but that can be discussed.
I brought in quote and proc_macro2 since they're a bit nicer to work with than raw strings, at least for generating Rust code. They're not strictly necessary given the small scope of the codegen, so they could be removed if the maintenance desire isn't there.
I have not pushed any generated code to help make reviewing easier. If this PR is accepted, I or anyone else can commit that code before merging.
The documentation can also be improved for each public item (excluding the const icon data items, probably).

Alright I added a small amount of documentation and updated the README for a new release.
I made the decision to convert the icon data items to SCREAMING_SNAKE case. As I mentioned earlier, it's a little less pleasing to my eyes, but it more clearly communicates what they actually are. Let me know if this seems okay!
If this all looks good, I'll commit the generated code!

I think it all looks good! I have no preference regarding casing, so if you generate the code then we can merge this

Alright it should be good to go from my end.

Thanks a lot for the PR! I have merged and published a new release


Resolve version mismatch for datepickers

Synergic UI depends on eonasdan-bootstrap-datetimepicker 3.x.x, but datetime picker depends on the latest version of moment.js. Latest moment.js is however not compatible with eonasdan-bootstrap-datetimepicker 3.x.x.
We need to either hardcode the required versions of both eonasdan-bootstrap-datetimepicker and moment.js in Synergic UI or convicne the author of eonasdan-bootstrap-datetimepicker to not depend on latest moment.js. Namely the author should not use >=x.x.x but ~x.x.x.

Upgraded to datetimepicker 4.x in the meantime. Shall we also notify the datepicker's author? Or close this issue right away?

Since the error is related to an old version of a package and we are not using it anymore I dont think we should bother with it. Lets close it.

OK but we should be aware that >=x.x.x is still there, even in 4.x.


Different type of brackets

Is it possible the same behaviour for different type of brackets?
For example (a b (c [d e]))

I found easy solution based on your last commit with quotes.
Thanks for the great library)


Remove cucumber code from the repository - decision request

Problem description

QualityOnDemand is the only SubProject which has test code based on cucumber in the repository:
https://github.com/camaraproject/QualityOnDemand/tree/main/code/cucumber
The code would need to be updated and regularly maintained.
Expected action

A decision to delete the code from the repository.
Additional context

Decision taken within QoD Meeting July 12th, directory to be removed.


[Fix #9843] Fix Style/RedundantSelf to allow conditional nodes to use self in the condition when a variable named is shadowed inside

Previously, Style/RedundantSelf registered false positives when a condition used self to avoid shadowing a local variable:
a = self.a if self.a

This was because the condition was not correlated to the lvar assign because they happen at different times. This is now fixed so if, unless, while and until nodes are covered.
Fixes #9843.

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

Failing CI seems like a false negative.

This looks good! Thank you for catching up with while, until, and masgn cases!


migrating from Foxy to galactic

thank you for your contribution.
I'm using ros2 galactic, and trying to use your lib.
but when I try to build the package, I got

so I tried to migrate it to galactic as mentioned here in ros2-conttrol framework.
this is the package after editing according to the ros2-control migration document,
but I got this error

I'm knew to programming and couldn't solve it, do you have any idea how to solve it?

Hi,
I see that there are some changes in the interface. Actually lifecycle node is indeed a better choice for managing hardware, which is a generic abstraction. I have tried it when implementing other drivers. Since it has not been introduced to the foxy branch of ros2_control, we won't update odrive_hardware_interface for this. We currently only intend to support LTS releases of ROS2. So we'll skip Galactic and look forward to Humble. If you have finished this part of migration, contributions are welcomed.
For your current issue, it seems all the return_type should be replaced by CallbackReturn. From your screenshot, it looks like return_type is still being used somewhere in the code.
Thanks

@borongyuan thank you for your replay.
yes and I changed all the return_type that was proposed in the documentation (configure, active ,deactive), but wasn't sure about the 'prepare_command_mode_switch', and if I do change it I got this error, sorry for the inconvenient

In this file both return_type and CallbackReturn are used. I just glanced at the code but don't know why. Anyway, this is the base class so we should have the same declaration.


Question: displaying images from S3

I created a custom ImageUploadField for uploading images to S3. It's working great, except when I select a single record - the img src tag now prepends /static/ to all of my file routes and I can't see the image. This is the generated tag from Flask-Admin:

<input class="form-control" id="image1" name="image1" type="file">

I also serve static files from my app, so globally changing the static directory wouldn't be a good idea.
There appears to be several properties on ImageUploadField that can be modified for this need (endpoint, url_relative_path, relative_path and base_path) but I was still unable to fix it.

Using the code example below, you could retrieve the object stored in database using filename and get the proper url. So you can choose to return it if you find a match.
https://github.com/mrjoes/flask-admin/blob/master/flask_admin/form/upload.py#L107
for exemple:
url = MyMedia.query.filter_by(filename=filename).first()
return url

It turns out that the widget was responsible for generating the URL. It also looks for the image in the static endpoint (hence why endpoint defaults to static when initializing the ImageUploadField class). To solve this, I created a subclass of this widget and modified the HTML to point directly to the S3 URL, which get's stored on the form.
Although widgets aren't talked about in depth in the Flask-Admin documentation, you can see how they work from pieces of the source code.
Below is the full code for the widget, and part of my custom ImageUploadField.
class S3ImageUploadInput(ImageUploadInput):

    def __call__(self, field, **kwargs):
        kwargs.setdefault('id', field.id)
        kwargs.setdefault('name', field.name)

        args = {
            'file': html_params(type='file',
                                **kwargs),
            'marker': '_%s-delete' % field.name
        }

        if field.data and isinstance(field.data, string_types):
            # calling field.data to directly return S3 URL
            url = field.data
            args['image'] = html_params(src=url)

            template = self.data_template
        else:
            template = self.empty_template

        return HTMLString(template % args)

class S3ImageUploadField(ImageUploadField):

    widget = S3ImageUploadInput()

    def __init__(self, *args, **kwargs):
        super(S3ImageUploadField, self).__init__(*args, **kwargs)


Detect focused window correctly under GNOME Shell + Wayland

The xprop strategy for checking window focus presumably works correctly when GNOME Shell is using X11. However, when GNOME Shell is using Wayland, the focused window is always reported as 0x0 regardless of what actually has focus.
My understanding is that Wayland in general does not have a "current focused window" concept at all. Any specific Wayland-based compositor might have such a concept, though. GNOME Shell does have such a concept, and exposes an API for checking the current window focus via JavaScript. We can use the session D-Bus to pass JavaScript to GNOME Shell for evaluation. This should work the same regardless of whether GNOME Shell is using Wayland or X11.

@liblit thank you for the contribution. Could you test if this is indeed also working with Gnome on x11? thanks!

Could you test if this is indeed also working with Gnome on x11?

Tested. It works correctly when GNOME is running under Xorg (X11) instead of Wayland.

Thank you for the contribution!


Add support for shutter opening curves to camera

For reference, see https://rmanwiki.pixar.com/display/REN/Motion+Blur+in+Maya#MotionBlurinMaya-ShutterOpeningShutterOpening, "Shutter Opening" section.

Maybe a start point.

The change is likely to take place in renderer::Camera::initialize_ray():
sampling_context.split_in_place(1, 1);
ray.m_time =
    ShadingRay::Time::create_with_normalized_time(
        sampling_context.next2<float>(),
        m_shutter_open_time,
        m_shutter_close_time);

The idea is to map sampling_context.next2<float>() to the desired curve before passing it to ShadingRay::Time::create_with_normalized_time().

I want to point what RenderMan do because I think it's the more evolved and interesting.

That's rather awesome :)

Hey I'd like to try this issue.

Definitely, go for it!

@dictoon link is dead :(

@pjessesco They keep changing their links, it's annoying. Here: https://rmanwiki.pixar.com/display/RFM/Motion+Blur+in+Maya

@fedormatantsev @pjessesco I think we can consider this done now that we support linear and Bézier opening/closing curves. What do you think?

@dictoon agree.


feat: fixed the structure of our file storage

Pull Request
Fixing up the storage of files made it alot neater
And added in testing for ne pages
Scope
https://github.com/DominicGBauer/information-access.git
Work Done
Steps to Test
npm run start
Screenshot

There's a warning being thrown by the navbar test, nonetheless the test passes though. Docs show it has to do with the router but workarounds provided do not resolve the warning. Refer https://next.vue-test-utils.vuejs.org/guide/advanced/vue-router.html#using-a-real-router


Multinomial Sampling May Not Ensure the Reliability of the Answer

Dear Author,
Thank you for your inspiring work. I noticed a problem that might be worth a recheck or your clarification.
In your implementation, you used the prompt " Please answer this question with one word." That means that the model will very likely output only a token "yes" or "no".
However, in your sampling method, you used multinomial sampling instead of greedy decoding. (https://github.com/DAMO-NLP-SG/VCD/blob/65a8fd771e9fbb9e26be5633c9d51db99222fbe7/experiments/eval/object_hallucination_vqa_llava.py#L75) This decoding strategy samples the next token via sampling from a multinomial distribution instead of argmax. Therefore, the predicted token (which is simply "yes" or "no") is not deterministic for the same question even the random seed is fixed.
For example, if you run question 7 in POPE random set solely, or run the same question in POPE's order, the model might give a different result.
Thank you.

Hi Eason, thanks for your interest in our work. Indeed, the sampling may lead to uncertainty in outputs.
That's why we ran several times for each experiment and reported their average scores and standard deviation to make it as robust and fair as possible.
You may also refer to our experiments that report the results of greedy decoding, where the output and score should always be fixed.


Stage #1 Connection

Both the link to select a server and the "Connect to Server" button do not work in stage #1 when trying to set up the EOS wallet in v.0.1.6 exe version.

Duplicate of #104 and resolved in version 0.1.7 (released a few minutes ago).


Ugly README iframe on home pages

The README iframes on the home pages is unformatted and very ugly. Either remove this iframe or format it.

We will remove this iframe.

The login/splash page and HQ page have been redesigned for release v0.2.1.


BatchSettings.builder().build() encourages failure by making required arguments optional

Current pubsub Publisher settings seem to require an instance of BatchingSettings with multiple values set to non-null values. However, the builder pattern encourages setting a single setting at a time.  For example, I wanted to make sure that messages were batched into 100 messages batches. So I did this:
publisher = Publisher.defaultBuilder(topicName).setBatchingSettings(                 BatchingSettings.newBuilder().setElementCountThreshold(100L).build()).build();
which fails with a NullPointerException .
Turns out I must set all other values of BatchingSettings to set one since the call above produces an object like this:
BatchingSettings{elementCountThreshold=100, requestByteThreshold=null, delayThreshold=null, isEnabled=true, flowControlSettings=FlowControlSettings{maxOutstandingElementCount=null, maxOutstandingRequestBytes=null, limitExceededBehavior=Ignore}}
Which took me a good 20 minutes to figure out.
What I wish we did here was an API that required all required parameters, like so (for example):
BatchingSettings.newBuilder().setThresholds(elementCount, requestByte, delay)

What about giving everything defaults, so that it's ok if you only set one value?

Proposal:
I think we should fix this by documentation.

Give error message so at least the user knows what we're complaining about.

Expose either DEFAULT_BATCHING_SETTINGS or defaultBatchingSettings(), and recommend users to call builder.setBatchingSettings(DEFAULT_BATCHING_SETTINGS.toBuilder().setElementCountThreshold(100L).build()). This call will work and keep all other parameters default.

WDYT?

I think we should just set defaults in newBuilder().

Note that there are two defaults at play here. One is BatchingSettings.DEFAULT and another is Subscriber.DEFAULT_BATCHING_SETTINGS.
I think Subscriber.DEFAULT_BATCHING_SETTINGS can stay as is.
BatchingSettings.DEFAULT defaulted to null for "never trigger". Eg, if you set element count to null, batch will only trigger on number of bytes and duration. What should default be here, Long.MAX?

I think the default for BatchingSettings should be the values for no batching (send one at a time).

I vote against addressing this in documentation only.  It's like hanging an
"open" sign on a locked door with a little note at the bottom that says
"JK. We are closed for the day."
On Fri, Oct 27, 2017 at 12:45 AM Garrett Jones<EMAIL_ADDRESS>wrote:

I think the default for BatchingSettings should be the values for no
batching (send one at a time).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-java/issues/2542#issuecomment-339871243,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARrMFuwzmeXdjz9k-SWXbQNMX_As9VR8ks5swV_UgaJpZM4QA7ZM
.

--
Kir Titievsky | Product Manager | Google Cloud Pub/Sub
https://cloud.google.com/pubsub/overview


Support parallel_tests

The issue name says it all. Make sure we can (safely) run tests in parallel by leveraging the parallel_tests gem. This becomes more and more important as test suites grow. puppetlabs-apache now takes a whole 7 minutes but every of those _spec.rb's should be able to run fully independently.

I tried this on puppetlabs-apache after installing parallel_tests in the bundle and it seems to work as is:
bundle exec spec_prep
bundle exec rake parallel:spec[spec/{classes,defines,unit,functions,hosts,integration,types}/.\*/.\*_spec.rb]
1368 examples, 0 failures

Took 149 seconds (2:29)

I'm weary of the caching mechanism in rspec-puppet though and how this might be affected.

AFAIK the parallel spec gem does fork off a new sub process for each
thread, so this should be very safe.
On Feb 16, 2016 23:08, "Daniele Sluijters"<EMAIL_ADDRESS>wrote:

I tried this on puppetlabs-apache after installing parallel_tests in the
bundle and it seems to work as is:
bundle exec spec_prep
bundle exec rake parallel:spec[spec/{classes,defines,unit,functions,hosts,integration,types}/.*/.*_spec.rb]
1368 examples, 0 failures
Took 149 seconds (2:29)
I'm weary of the caching mechanism in rspec-puppet though and how this
might be affected.
—
Reply to this email directly or view it on GitHub
https://github.com/rodjek/rspec-puppet/issues/367#issuecomment-184913466
.

FWIW I wrote a blog post showing how to set up parallel_tests  http://razorconsulting.com.au/parallelising-rspec-puppet.html

@alexharv074 Awesome, thank you! I was working on something similar for the test matrix here.

:+1:

Also, puppetlabs_spec_helper recently added parallel fixtures cloning: https://github.com/puppetlabs/puppetlabs_spec_helper/pull/126

I also opened a PR to puppetlabs_spec_helper to split up tests using CI/Travis matrices: https://github.com/puppetlabs/puppetlabs_spec_helper/pull/116.

Cool! Merged.

Going to close this out as there's nothing really actionable here


fix(web_debranding): no more bytes returned

Closes #762

Break... this is not the solution

Ok, this is the correct solution, but it exposes an underlying odoo bug, which I will solve in a second... please help accepting.

Here is the PR: https://github.com/odoo/odoo/pull/34751
The commit: https://github.com/odoo/odoo/pull/34751/commits/5a8c31ac1af31dd13626f83435d4b818398c26ab

Patch is here: https://patch-diff.githubusercontent.com/raw/odoo/odoo/pull/34751.patch

CI Failure due to upstream patch not applied...

Okk, I assume odoo might merge the fix and forward port the patch... I hope... You could upvote...

So this has been merged: https://github.com/odoo/odoo/pull/34751 Now we can look over this again from a new perspective, I guess the fix became obsolete, now.

It looks like this is obsolete now, and byte is the expected return value from 11.0 onwards.

@yelizariev This is the correct fix now that the upstream patch coerces to bytes...

From travis:
  File "/home/travis/build/it-projects-llc/misc-addons/web_debranding/controllers/main.py", line 84, in qweb
    content = debrand(request.session.db and request.env or None, content)

after the fix this line ought to be:
content = debrand_bytes(request.session.db and request.env or None, content)

My bad


Syntax highlighting for local variables in SAP ASE and SAP IQ

Please implement highlighting of local variables for SAP ASE and SAP IQ
Local variables have @ (at) sign in the front of the variable name
SAP documentation on local variabes
Example:
BEGIN
	DECLARE @local_var INT ;
	SET @local_var = 10 ;
	SELECT @local_var;
END

Thanks for suggestion!

Implemented (for HANA and SQL Server):

Using # symbol in the name breaks the highlighting

Verified

Verified


StreamField should accept min_num / max_num / block_counts directly

StreamBlock accepts keyword arguments min_num / max_num / block_types to limit the number of blocks in the stream:
body = StreamField(
    blocks.StreamBlock([
        ('heading', blocks.CharBlock()),
        ('paragraph', blocks.RichTextBlock()),
    ], max_num=3)
)

However, these arguments are only available when using an explicit StreamBlock - ideally StreamField itself should recognise these too, so that the above could be rewritten as:
body = StreamField([
    ('heading', blocks.CharBlock()),
    ('paragraph', blocks.RichTextBlock()),
], max_num=3)

This probably just requires StreamField to pass on these arguments when creating its internal StreamBlock (along with corresponding tests / documentation updates).

I've created a PR for this on #5185, but it currently doesn't update any documentation - Would adding some arguments definition to streamfield.rst, above the "Basic block types" section sound like roughly what you'd be looking for?

I understand that the only bit left on this one is to update the docs. I'll take care of it if it's still an open issue.

@paqman85 Not quite - the issue mentioned on https://github.com/wagtail/wagtail/pull/5185#issuecomment-478083855 (ensuring max_num / min_num are respected when the first argument to StreamField is a StreamBlock class rather than a list of blocks) is still open. That may or may not be solvable without going down the rabbit-hole of #4306...

@paqman85 Not quite - the issue mentioned on https://github.com/wagtail/wagtail/pull/5185#issuecomment-478083855 (ensuring max_num / min_num are respected when the first argument to StreamField is a StreamBlock class rather than a list of blocks) is still open. That may or may not be solvable without going down the rabbit-hole of #4306...

Oh boy. I'll do some digging and see if I can figure it out.

Yes, this is quite the rabbit hole indeed. I'm afraid it's out of my current understanding. 😞 Perhaps not the best labelling for this one?

Fixed in #6718

Fixed in #6718


Upgrade formally to DeviceDefault theme as default

Change-Id: Iaa638a74b3e992caf05ef7376de5ff7aab57ab6f

@jisqyv So a side-effect of the fix for the Samsung issue was that we implicitly changed all apps to have the device default theme even if they had been using classic. This change does 2 things. First, it implements a formal upgrader to handle the default theme change. Second, I think the Theme needs to be handled specially since it is specified in the XML and for compiled apps there's no need to programmatically set it.
Lastly, I have submitted this to master since at the very least we probably want to update the website and buildservers, even if we don't put out a companion for immediate release. I think the recently released companion should be compatible with this change.
This is a draft because I have not had a chance to extensively test it yet. Please test on Samsung to make sure I didn't reintroduce the problem fixed in the last release.


HDFS-16105. Edit log corruption due to mismatch between fileId and path

NOTICE
Please create an issue in ASF JIRA before opening a pull request,
and you need to set the title of the pull request which starts with
the corresponding JIRA issue number. (e.g. HADOOP-XXXXX. Fix a typo in YYY.)
For more details, please see https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 54s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
33m 19s

trunk passed

+1 :green_heart:
compile
1m 25s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
compile
1m 14s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
checkstyle
1m  4s

trunk passed

+1 :green_heart:
mvnsite
1m 21s

trunk passed

+1 :green_heart:
javadoc
0m 57s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 24s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
3m 18s

trunk passed

+1 :green_heart:
shadedclient
19m  7s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 17s

the patch passed

+1 :green_heart:
compile
1m 19s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javac
1m 19s

the patch passed

+1 :green_heart:
compile
1m 10s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
javac
1m 10s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m  0s

the patch passed

+1 :green_heart:
mvnsite
1m 22s

the patch passed

+1 :green_heart:
javadoc
0m 55s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 22s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
3m 47s

the patch passed

+1 :green_heart:
shadedclient
20m 10s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
356m 16s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 38s

The patch does not generate ASF License warnings.

450m 35s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.namenode.TestINodeFile

hadoop.hdfs.TestFileCreation

hadoop.hdfs.server.namenode.TestDeleteRace

hadoop.fs.contract.hdfs.TestHDFSContractAppend

hadoop.hdfs.TestRenameWhileOpen

hadoop.hdfs.TestLease

hadoop.hdfs.server.namenode.ha.TestBootstrapStandby

hadoop.hdfs.server.namenode.TestNameNodeXAttr

hadoop.hdfs.TestReservedRawPaths

hadoop.hdfs.server.namenode.TestHDFSConcat

hadoop.hdfs.server.namenode.ha.TestEditLogTailer

hadoop.hdfs.TestDFSShell

hadoop.hdfs.server.namenode.TestFileContextXAttr

hadoop.hdfs.server.datanode.fsdataset.impl.TestFsVolumeList

hadoop.hdfs.TestEncryptionZones

hadoop.hdfs.TestEncryptionZonesWithKMS

hadoop.hdfs.web.TestWebHDFSXAttr

hadoop.hdfs.server.namenode.TestDecommissioningStatusWithBackoffMonitor

hadoop.hdfs.TestFileAppend3

hadoop.hdfs.server.namenode.TestDecommissioningStatus

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3161/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3161

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux 86719da9b39d 4.15.0-136-generic #140-Ubuntu SMP Thu Jan 28 05:20:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 5e870bc84a1ec1cc7f0444a7e30b23e68dbd025c

Default Java
Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3161/1/testReport/

Max. process+thread count
2318 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3161/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.


cannot find credentials if AWS_PROFILE or AWS_DEFAULT_PROFILE environment vars are set

if either:
AWS_PROFILE or AWS_DEFAULT_PROFILE is set, the client will not find aws credentials:
or if you run the command with the AWS_PROFILE env variable it will also fail to find the creds
AWS_PROFILE=dev ./blessclient.run --nocache --region WEST --config ~/bin/python-blessclient/conf/dev.cfg
Can't get your user information from AWS! Either you don't have your user aws credentials set as [default] in ~/.aws/credentials, or you have another process setting AWS credentials for a service account in your environment.Could not connect to BLESS in any configured region.

stack trace:
AWS_PROFILE=dev ./blessclient.run --nocache --region WEST --config ~/bin/python-blessclient/conf/dev.cfg
Traceback (most recent call last):
File "/Users/gjyoung1974/bin/python-blessclient/blessclient.run", line 9, in
load_entry_point('blessclient==0.2.0', 'console_scripts', 'blessclient')()
File "/Users/gjyoung1974/bin/python-blessclient/blessclient/client.py", line 621, in main
bless(region, args.nocache, args.gui, args.host, bless_config)
File "/Users/gjyoung1974/bin/python-blessclient/blessclient/client.py", line 428, in bless
username = get_username(aws, bless_cache)
File "/Users/gjyoung1974/bin/python-blessclient/blessclient/client.py", line 368, in get_username
user = aws.iam_client().get_user()['User']
File "/Users/gjyoung1974/bin/python-blessclient/venv/lib/python2.7/site-packages/botocore/client.py", line 310, in _api_call
return self._make_api_call(operation_name, kwargs)
File "/Users/gjyoung1974/bin/python-blessclient/venv/lib/python2.7/site-packages/botocore/client.py", line 586, in _make_api_call
operation_model, request_dict)
File "/Users/gjyoung1974/bin/python-blessclient/venv/lib/python2.7/site-packages/botocore/endpoint.py", line 141, in make_request
return self._send_request(request_dict, operation_model)
File "/Users/gjyoung1974/bin/python-blessclient/venv/lib/python2.7/site-packages/botocore/endpoint.py", line 166, in _send_request
request = self.create_request(request_dict, operation_model)
File "/Users/gjyoung1974/bin/python-blessclient/venv/lib/python2.7/site-packages/botocore/endpoint.py", line 150, in create_request
operation_name=operation_model.name)
File "/Users/gjyoung1974/bin/python-blessclient/venv/lib/python2.7/site-packages/botocore/hooks.py", line 227, in emit
return self._emit(event_name, kwargs)
File "/Users/gjyoung1974/bin/python-blessclient/venv/lib/python2.7/site-packages/botocore/hooks.py", line 210, in _emit
response = handler(**kwargs)
File "/Users/gjyoung1974/bin/python-blessclient/venv/lib/python2.7/site-packages/botocore/signers.py", line 90, in handler
return self.sign(operation_name, request)
File "/Users/gjyoung1974/bin/python-blessclient/venv/lib/python2.7/site-packages/botocore/signers.py", line 154, in sign
auth.add_auth(request)
File "/Users/gjyoung1974/bin/python-blessclient/venv/lib/python2.7/site-packages/botocore/auth.py", line 340, in add_auth
raise NoCredentialsError
botocore.exceptions.NoCredentialsError: Unable to locate credentials

@gjyoung1974 just to clarify, when you're setting AWS_PROFILE=dev, do you want blessclient to access aws as that user? Or is the profile preventing your default user from being correctly used?
At Lyft we have users put their iam credentials in their default profile, so I've been considering unsetting AWS_PROFILE when users run bless. But if you're intentionally trying to run bless with that profile that won't work for you.

This issue can be closed


Request: Masking with low init-image-strength should be allowed to move the masked area in the output

When using a mask, the masked area always stays in the exact same place. With a low init-image-strength (and/or a new mask parameter) the area should be allowed to be scaled and moved.
For example, with a closeup of a face, it should be possible to generate outputs that are "zoomed out" and have a body attached.

It sounds like you're asking for outpainting.  To do what you describe you'd just place shrunk down image where desired and then mask everything in the image.  I may eventually add some helper functions to assist with that.

Part of what's great about the models is that they can come up with novel "ideas" - I'm not requesting outpainting, but rather the ability for the masked area to be adjusted by random seed in whatever way is feasible. If I for example want "dog's head on person's body" with a mask of "dog's head", then the model should be able to put the head on a short person, a tall person, a person walking down a street, a person driving a car, whatever. The mask function currently overly restricts the text prompt; it would be nice if it could also serve as just an input. Text prompt = idea; mask = resource to be used in the idea, without any restriction on size, position.

This could be accomplished via an integration with the openai api but is outside the scope of this library.


TypeError: rawRef is not iterable

Version
3.0.0
Reproduction link
https://codesandbox.io/s/brave-brown-ux5cq
Steps to reproduce
generate package from the link and use in demo app:  https://codesandbox.io/s/brave-brown-ux5cq?file=/demo-example
What is expected?
Generate Component which could be imported as dependency
What is actually happening?
I want to create UMD package with webpack ( rollup are not suitable because of package is using 3rd party where use strict broken because of with operator) . When I create component and import it from the directory of the same application it works great. But when from the package I get an error TypeError: rawRef is not iterable form const setRef = (rawRef, oldRawRef, parentComponent, parentSuspense, vnode) => { ... const [owner, ref] = rawRef;
Also, when I import it from the same application, Component is looks like:
name: "ZiggeoPlayer"
props: {apiKey: {…}, auto-install-vue: {…}, auth: {…}, debug: {…}, testing_application: {…}, …}
render: ƒ render(_ctx, _cache, $props, $setup, $data, $options)
setup: setup(props, { emit }) { const player = Object(vue__WEBPACK_IMPORTED_MODULE_0__["markRaw"])({}); const ziggeoPlayer = Object(vue__WEBPACK_IMPORTED_MODULE_0__["ref"])(null); const _ziggeoAttributes = () => {…}
__emits: {0: null}
__file: "src/tmp/components/ZiggeoPlayer/ZiggeoPlayer.vue"
__hmrId: "3f52f3f2"
__props: {0: Array(2)}
__proto__: Object

but when from package:
name: "ZiggeoPlayer"
props: {apiKey: {…}, auto-install-vue: {…}, auth: {…}, debug: {…}, testing_application: {…}, …}
render: ƒ render(_ctx, _cache)
setup: ƒ setup(props, _ref)
__emits: {0: null}
__props: {0: Array(2)}
__proto__: Object

As you can see, setup is different

Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the forum, the Discord server or StackOverflow.

This is just too much for a reproduction, if you manage to reproduce without the ZiggeoPlayer, then we can take a look. A git repository would also be more suitable

I've got this warning, so why open issue here: [Vue warn]: Unhandled error during execution of scheduler flush. This is likely a Vue internals bug. Please open an issue at https://new-issue.vuejs.org/?repo=vuejs/vue-next


Update start.bat, support set port

Coverage remained the same at 92.474% when pulling 7634707e434a75cd9b8f7e9f6d32011207b96de1 on guangyun1013:2.1.1 into d69994c45cab3a667dcee0b6733b961427662b25 on dangdangdotcom:2.1.1.


Poudriere should allow native xtools for non-QEMU builds

Prerequisites

[x] Have you checked for an existing issue describing your idea?

What is your proposal?
Poudriere should permit to create and use native-xtools when building for a natively supported architecture that is not the same architecture as the host system (i.e. i386 on amd64).
What is the existing behavior, if any?
Poudriere only permits native xtools when building with emulation.
What is the motivation / use case for the change?
Some architectures (amd64, arm64, potentially mips64, ppc64, riscv64) support running 32 bit binaries on a 32 bit kernel, so ports for the 32 bit variant can be built natively.  Neverthless it is very useful to build these ports with a 64 bit tool chain because often running 64 bit code is faster on these platforms.  Additionally, some ports require more than 4 GB of virtual memory to compile and link, so building them with a native toolchain is impossible.  Xtools are required in such a situation to get a 32 bit binary of the port at all.
Did you consider any alternatives?
No.
Is this really a ports feature request?
Yes.
Example
On an arm64 system, I want to be able to do
poudriere jail -c -j 13Rarmv7 -a arm.armv7 -b -x -m src=/usr/src

But right now, the -x option is silently ignored as armv7 builds do not require QEMU on arm64.
Additional context
n/a

definitely +1.
Am looking to do this for arm.armv6

Have found that the reason poudriere calls for qemu on aarch64 when trying to build a jail for armv6 is because on aarch64 MACHINE_ARCH32 is set to armv7. To get poudriere to build on aarch64 an armv6 jail, one must modify /usr/src/sys/arm64/include/param.h and rebuild the kernel. (thanks to markml for the suggestion)

The only real bug here is that on aarch64, poudriere prompts for QEMU when asked to compile a jail for a non-native host. It does this in spite of QEMU not being available as an emulating host on aarch64.

@ivr588 That is a different issue.  I am specifically interested in using native x-tools to build armv7 packages on aarch64 or i386 packaged on amd64 because a 64 bit compiler runs faster than a 32 bit compiler on these platforms.  QEMU does not enter the picture here.


Always sort snapshots lists ascending by timestamp

Fixes #1219.

Codecov Report

Merging #1275 into master will decrease coverage by 5.81%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master   #1275      +/-   ##
=========================================
- Coverage   52.72%   46.9%   -5.82%
=========================================
  Files         130     130
  Lines       12466   12469       +3
=========================================
- Hits         6573    5849     -724
- Misses       5126    5908     +782
+ Partials      767     712      -55

Impacted Files
Coverage Δ

cmd/restic/cmd_snapshots.go
32.2% <0%> (-0.85%)
:arrow_down:

internal/backend/b2/b2.go
0% <0%> (-79.93%)
:arrow_down:

internal/backend/azure/azure.go
0% <0%> (-75.35%)
:arrow_down:

internal/backend/swift/swift.go
0% <0%> (-73.9%)
:arrow_down:

internal/backend/gs/gs.go
0% <0%> (-70.82%)
:arrow_down:

internal/backend/swift/config.go
34.37% <0%> (-56.25%)
: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 24c62e7...ea1ab96. Read the comment docs.


Extension Attribute scripts not working correctly

Hello,
some of the extension attribute scripts are not working correctly with the latest Jamf Protect Version 4.0.0.
Especially there are the following issues with the "jamf_protect_last_check_in_compliance.sh" script I was using.
The Output of the following command for example is empty because there are no colons after Status anymore and the column in the awk command does not match anymore.
jamf_protect_status=$(echo "$jamf_protect_info" | /usr/bin/grep 'Status:' | /usr/bin/awk '{print $2}')

It is working with the following though:
jamf_protect_status=$(echo "$jamf_protect_info" | /usr/bin/grep 'Status' | /usr/bin/awk '{print $4}')

There is a similar problem with the following command, where the columns $3 and $4 do not match anymore:
jamf_protect_lastcheckin=$(echo "$jamf_protect_info" | /usr/bin/grep "Last Check-in" | /usr/bin/awk '{ print $3, $4 }' | /usr/bin/sed -e 's/ /-/g' -e 's/:/-/g' -e 's/\./-/g')

It's working with $5, $6:
jamf_protect_lastcheckin=$(echo "$jamf_protect_info" | /usr/bin/grep "Last Check-in" | /usr/bin/awk '{ print $5, $6 }' | /usr/bin/sed -e 's/ /-/g' -e 's/:/-/g' -e 's/\./-/g')

Users might get empty Extensions Attributes as a result or parsing issues while running the script.
Cheers,
Dominik

@czernedo thanks for raising this issue. Can you check out the branch task/issue_66. I've made some changes so the EA should work properly. I removed the grep altogether and just using awk. Can you please test and let me know. Thanks again.
Allen

Hey @golbiga, I am testing the change and so far it seems to be reporting back info on a number of machines that previously  were only returning a blank result. I will keep an eye on it through tomorrow to see if anything otherwise stands out. Appreciate your work on this!


Declare null_value_pattern as regexp

Because it is a regexp actually. This change provides flexibility and better document to users.
What this PR does / why we need it:
The null_value_pattern is defined as string currently, but it's actually compiled as a Regexp. But documents are written as string and it makes users confused.
Docs Changes:
Needed here: https://docs.fluentd.org/configuration/parse-section
Release Note:
Probably no need to mention this. No compatibility will be broken by this change.

Thanks! I'll fix the document.


Compatibility with vulkan

This PR adds Vulkan shader support. The tex2DgatherR, tex2DgatherG and tex2DgatherB functionality is not supported, so we have changed it.

I think you are confused. tex2DgatherR, tex2DgatherG and tex2DgatherB are supported in Reshade.
See https://github.com/crosire/reshade-shaders/blob/slim/REFERENCE.md

Then that is an issue with vkBasalt.
Also an odd one. To my knowledge vkBasalt runs the ReshadeFX shader compiler which will take a shader written in ReshadeFX (like mine) and translate that to either HLSL (for either SM3,4,5 or 6) or GLSL or SPIR-V
What other programs that also have some support for ReshadeFX shaders usually lack is depth buffer support and support for the shader annotations in ReshadeFX that tell Reshade what textures to load, and what passes and renderstates to set up, and UI is also commonly lacking.
This is all doable (especially because Reshade is open-source and they can copy the code for those parts if they want) but it does require work.
Anyways I'm closing this as it is out of scope for SweetFX. It's designed for Reshade. If vkBasalt has issues then it needs to up it's compatibility with Reshade effects.


Add an option to turn brackets matching on or off

VSCode Version: Code 1.5.3 (5be4091987a98e3870d89d630eb87be6d9bafd27, 2016-09-22T08:50:42.185Z)
OS Version: Windows_NT ia32 6.1.7601

I would like to have an option in preferences file to turn bracket matching on or off.
Sometimes, when typing it is hard to detect where the caret is. For example:

In this case it is better to hide bracket markers altogether.
When I need to locate a matching brace I could use key-bound command "Go to bracket".

I'd really like to see theme support for brackets matching so that:

the very annoying boxes can be turned off
matching brackets can be highlighted by color (foreground, background, or both)

You can set "editor.matchBrackets": false

@bpasero turning off bracket matching is not the same thing. I don't appreciate the issue being closed without actually being addressed. I want bracket matching; I just want it with color instead of this legibility killing outline.

@jsumners please follow our bug guidelines when reporting issues, we do not want different issues in one issue exactly for this reason. I closed this item because the things described by @fantaclaus were solved.
As for theming of bracket matching, you can set the following setting to tune the experience:
"workbench.colorCustomizations": {
	"editorBracketMatch.background": "",
	"editorBracketMatch.border": ""
}

This is only available yet in our insiders build. You can give our preview releases a try from: http://code.visualstudio.com/Download#insiders

@bpasero is that setting scheduled for the next release?


chore(avm): renamings and comments

Painful.
Also cleaned up the generated files. Some hadn't been deleted when the renaming took place.

Merge activity

Jun 20, 6:13 AM EDT: @fcarreiro merged this pull request with Graphite.


Configure to make x64 the default project

Is there a way to make the default x64 instead of x86 for all newly opened projects? If not, there should be.

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

ID: 56287d26-a426-a30f-bdb4-432125710e49
Version Independent ID: 6af8f7c6-9657-739c-0e06-3b1f43fae7e4
Content: How to: Configure Visual Studio C++ projects to Target 64-Bit, x64 Platforms
Content Source: docs/build/how-to-configure-visual-cpp-projects-to-target-64-bit-platforms.md
Product: visual-cpp
Technology: cpp-tools
GitHub Login: @corob-msft
Microsoft Alias: corob

@troglobytor
That's a worthy idea, and I'm sure you're not the only one who'd appreciate that ability. At present, there's no simple way to switch the default configuration for new projects. If you'd like to see one added to the product, you can make a suggestion from within Visual Studio by using the Help > Send Feedback > Suggest a Feature menu item, or by entering an issue directly on the Developer Community site. That's the easiest way to bring ideas to the attention of the development team. If enough other people upvote your idea, odds are good it will be implemented. Give it a shot, and good luck.


Input of $ character

There is a problem with $ and $$
When $ is input next to a letter there should be no automatic second $added by the system.
This is because sometime one wants to add a forgotten $ in front or at the end of an equation in the middle of the text and then it is super annoying to remove the second $ that automatically pops up all the time.
Only when a space is preceding AND a space or newline is following the cursor, the pattern $<cursor_here>$ should be executed.
Please also compare with {}, however this case is slightly different.

I agree this is a useful fix. Will work on that.

I installed the 0.6.0 update today but it still seems to not work.
example:
before: <cursor_here>equation
after: $<cursor_here>$equation

The atom version will wait for some days to see the update. Ref #13.
You can read the readme for cutting edge changes installation.


Range Slider doesn't work inside modal view

Short description of the problem:
Range Slider is not draggable when inside a modal view running on the phone.
What behavior are you expecting?
Range Slider should be draggable to select desired value.
Steps to reproduce:

Add a range slider component inside a modal view
Launch modal view in your controller

<ion-modal-view>

        <input type="range" name="volume">

</ion-modal-view>

Other information: (e.g. stacktraces, related issues, suggestions how to fix, stackoverflow links, forum links, etc)
When ran on Chrome browser, the range slider is at least tappable allowing to change the value but dragging the slider is still not working.  The following message is appearing in my console the moment I tap or try to drag the slider:

Deferred long-running timer task(s) to improve scrolling smoothness. See crbug.com/574343.

Which Ionic Version? 1.2.x up to 1.3.x

Hello, thanks for opening an issue with us! Would you be able to provide a plunker that demonstrates this issue? Thanks for using Ionic!

I don't have a plunker but you can view this with Ionic View using this ID: fcf03f24
All I did here was just start with the blank starter project and modified the following files:
index.html (replace body with this)

    <ion-pane>
      <ion-header-bar class="bar-stable">

Ionic Blank Starter

      </ion-header-bar>
      <ion-content>

This range slider works as expected.

            <input type="range" name="volume">

Launch a modal with the same range slider.

          <button class="button button-block button-outline button-positive" ng-click="openModal()">
            Open Modal View
          </button>

      </ion-content>
    </ion-pane>

app.js (add this code)
.controller('RangeCtrl', function($scope, $ionicModal) {
  $scope.data = {};

  $scope.openModal = function() {
    $ionicModal.fromTemplateUrl('modal-range.html', {
      scope: $scope,
      animation: 'slide-in-up'
    }).then(function(modal) {
      $scope.modal = modal;
      $scope.modal.show();
    });
  };

  $scope.closeModal = function() {
    $scope.modal.remove();
  };

  // Cleanup the modal when we're done with it!
  $scope.$on('$destroy', function() {
    $scope.modal.remove();
  });

  // Execute action on hide modal
  $scope.$on('modal.hidden', function() {
    // Execute action
  });

  // Execute action on remove modal
  $scope.$on('modal.removed', function() {
    // Execute action
  });
})

modal-range.html (create this file)
<ion-modal-view>

This range slider doesnt work as expected.

			<input type="range" name="volume">

		<button class="button button-block button-outline button-positive" ng-click="closeModal()">
            Close Modal View
        </button>

</ion-modal-view>

This is the malefactor:
https://github.com/driftyco/ionic/blob/1.x/js/angular/service/modal.js#L194
I fixed it temporarily by changing the code to:
var isInScroll = ionic.DomUtil.getParentOrSelfWithClass(e.target, 'scroll');
if (isInScroll !== null && !isInScroll) {
    e.preventDefault();
}

Thanks @basdp I'll give this a try.

+1 for this - the only way to get it working for me seems to be to downgrade to 1.2.0 😢

As a workaround you can use @basdp's code above. I verified it resolves the issue with sliders on modals.

This issue was moved to driftyco/ionic-v1#121


events_journal: add Adobe I/O Events Journaling API wrapping Service

see https://www.adobe.io/apis/experienceplatform/events/docs.html#!adobedocs/adobeio-events/master/api/journaling_api.md

released with version 0.0.3
see https://github.com/adobe/aio-lib-java/tree/aio-lib-java-0.0.3


sentence classification release date?

Hello,
I opened an issue on Jan 24th asking about sentence/document classification functionality to which you replied there would be a release soon. Can you provide any updates on this? possibly an estimated release date?
Thank you

Hi @jonnykira , thanks for your interest. Currently, the basic classification functions are ready. But more features and test are ongoing. It may take me about another one month to make it ready as I am quite busy these days.

Hi, @jiesutd i run a sentence classfication use lstm, and i find it can run and ritch 0.94 of P

@chuanfanyoudong glad to hear that. Indeed the sentence classification can work properly. But I am trying to add more feature and make the code more concise.

@jiesutd 赞

Hello,
I am also able to get the sentence classification working, just needed to change the format of my training data to sentence, label pairs per line and ensure the delimiter (the split_token) between these was correct. From my reading of the code it seems like a character level NN is used to generate a sentence representation which is then concatenated with the word embedding sentence representation, which is then fed to another NN layer followed by crf/softmax to generate the sentence predictions.

Hello,
I am also able to get the sentence classification working, just needed to change the format of my training data to sentence, label pairs per line and ensure the delimiter (the split_token) between these was correct. From my reading of the code it seems like a character level NN is used to generate a sentence representation which is then concatenated with the word embedding sentence representation, which is then fed to another NN layer followed by crf/softmax to generate the sentence predictions.

Yes, the sentence classification has the same feature extraction structure as the sequence labeling. The difference is the final output is a sentence level classifier rather than each token. I am still working on make the sentence classification function more powerful and easy-to-use.

@jiesutd there is one thing i can't understand, why there id a function called "sentence_representation" and i find  this function is almost the same as the function forward except the "torch.cat(feature_list, 1)" ?

Yes, the sentence classification has the same feature extraction structure as the sequence labeling. The difference is the final output is a sentence level classifier rather than each token. I am still working on make the sentence classification function more powerful and easy-to-use.

Hello,
First of all, congratulations and thanks for sharing this awesome work :-)
I am also waiting for updates about sentence classification (I made it work but it was a bit difficult to understand).
I have a question about it. Does the sentence classification allow custom features? (like [CAP]=0 [POS]=NP , etc. for sequence labelling). If so, what would be the correct format of the training file?
Thank you :-)

@aitor-garcia-p Good question! This is what I am working on. The current version does not support the custom features, but I am working on adding this function in. However, I am quite busy in recent days, I can not guarantee when will I release a complete version of the sentence classification.

@jiesutd there is one thing i can't understand, why there id a function called "sentence_representation" and i find this function is almost the same as the function forward except the "torch.cat(feature_list, 1)" ?

The sentence classification is to extract the representation of the whole sentence.  They are more difference than the "torch.cat(feature_list, 1)". You can compare them carefully.

@jiesutd thank you, I understood wrong before.，i will compare them more carefully

Thanks for your work，我是来催更的，哈哈。

@aitor-garcia-p @jonny-d @shenxuhui
Hi everyone,  I have just released the sentence classification version in the dev branch: https://github.com/jiesutd/NCRFpp/tree/dev
Welcome to try it if you are interested. It supported the additional features as @aitor-garcia-p  requested. You can add any features you want (just follow the format as file sample_data/clf.train.feature.txt).
You can start with the demo code python ncrf.py --config demo.clf.train.config
There are several major revisions in this branch, I will work on this branch to integrate BERTs and will merge it into the main branch later.
I just notice that it has been one year since my last response. How time flies! Thank you for your support.

Thank you very much for your work :-)
The time flies indeed!
I am terribly busy these days, but if I have the chance I will give it a look.


Threaded Binary Tree And Convex Hull Algo Implementation

Added implementation of Threaded Binary Tree in Cpp, as well as Polygon Convex Hull Algorithm in O(nlogn) time
This PR is resolved #51

Also, Kartik please append your name to the contributors.md file.

Sure done.

Can't see

Thanks for your contributions😃


add initial galley intro to "what is istio" concept page

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: ayj
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: frankbu
If they are not already assigned, you can assign the PR to them by writing /assign @frankbu in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

content/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Add Big-Bench Lite to eval-harness

We want to be able to evaluate our models on BIG-Bench Lite. The BIGBench code is not the most outsider-friendly so I'll try to add the BigBench lite tasks to the eval-harness, and test on GPT2 for equivalence to confirm the scores should transfer back to the original implementation.
So far: have looked through the BigBench HF code a bit.

I remember testing T0 on Bigbench with Eval Harness last year. This probably could save us time and effort.

Oh that would be awesome if so. was this in mesh-tensorflow / t5x or in Huggingface?


Typo in DBB Documentation

Hi I'm unsure if this is the right place to share this but you guys have a documentation typo. I couldn't find where the doc was generated.
I'm assuming that this line
As part of BM Z and Cloud Modernization Stack
Should be
As part of IBM Z and Cloud Modernization Stack
https://ibm.github.io/mainframe-downloads/products/ibm-dependency-based-build.html

Typo is fixed.


SMARTS for FP Bits?

Is there a way to understand what SMARTS patterns are being used for a given bit in a circular/morgan FP? I've seen some explanations about how to extract which atoms were hit via why FPbit by using bitInfo dictionaries, but there doesn't seem to be any easy to to know which patterns represent each bit. Is there a way to do this?

http://www.rdkit.org/docs/GettingStartedInPython.html#explaining-bits-from-morgan-fingerprints
Does this not do what you want?

As far as I understand, that is a process that can only be done in retrospect at an atom level. The code will retrieve atoms in a given molecule that match a given pattern, but not what the actual pattern is.
What I was hoping for was some kind of SMARTS-like pattern that was assosciated with each bit position in the FP; essentially, I would like to be able to, for a given FP bit index, retrieve a SMARTS pattern that I can use to find other compounds with that substructure (a bit convoluted, I understand).

Ah, I think I get it. That's not the way those fingerprints work.
The fingerprinting algorithm enumerates all the atomic environments and hashes each of them to come up with a bit id. The only way back from ID -> atom environment is using the approach described in the documentation.
I believe that the best way to do the search you want to do is to just generate and store the fingerprints for all the molecules you would want to search and then just check to see if they have the bit(s) set that you care about.

Ah, gotcha. Much appreciated.


Batch Purchases & Selling Options

I'm not sure why you limited insertion/extraction to only hoppers, but is it possible to add Pipes/Itemducts/Inserters/Conveyors support?

Lol, silly me. That not about hoppers, that about any inventory on top or bottom of market
So, can you add buttons for BATCH purchases at one operation cycle?

And probably it should work with Auto-buying too.

Yeah this was an idea that I was going to implement in the first version, but then I got to focused on getting just the Market itself working.


netdata: fix start cgroup-network-helper.sh

Description of changes
Fix this error:
/nix/store/5qzqdmbf5c87h0amsxxpcnqv75kcw4yz-wrapped-plugins/libexec/netdata/plugins.d/cgroup-network ERROR : MAIN : child pid 25934 exited with code 127.
/nix/store/5qzqdmbf5c87h0amsxxpcnqv75kcw4yz-wrapped-plugins/libexec/netdata/plugins.d/cgroup-network INFO  : MAIN : there are no double-linked host interfaces available.
cgroup-name.sh: INFO: cgroup 'machine.slice_machine-qemu_x2d2_x2dvm02_x2dmail.scope_libvirt' is called 'qemu_vm02mail_libvirt'
cgroup-name.sh: INFO: cgroup 'machine.slice_machine-qemu_x2d2_x2dvm02_x2dmail.scope_libvirt_vcpu1' is called 'qemu_vm02mail_libvirt_vcpu1'
cgroup-name.sh: INFO: cgroup 'machine.slice_machine-qemu_x2d2_x2dvm02_x2dmail.scope_libvirt_vcpu0' is called 'qemu_vm02mail_libvirt_vcpu0'
cgroup-name.sh: INFO: cgroup 'machine.slice_machine-qemu_x2d2_x2dvm02_x2dmail.scope_libvirt_emulator' is called 'qemu_vm02mail_libvirt_emulator'
cgroup-name.sh: INFO: cgroup 'machine.slice_machine-qemu_x2d3_x2dvm01_x2dweb.scope' is called 'qemu_vm01web'
/nix/store/5qzqdmbf5c87h0amsxxpcnqv75kcw4yz-wrapped-plugins/libexec/netdata/plugins.d/cgroup-network ERROR : MAIN : Cannot open pid_from_cgroup() file '/sys/fs/cgroup/machine.slice/machine-qemu\x2d3\x2dvm01\x2dweb.scope/tasks'. (errno 2, No such file or directory)
/nix/store/5qzqdmbf5c87h0amsxxpcnqv75kcw4yz-wrapped-plugins/libexec/netdata/plugins.d/cgroup-network INFO  : MAIN : running: exec /nix/store/9y66swks0vb4l6fd2094cpfklrmby2cq-netdata-1.38.1/libexec/netdata/plugins.d/cgroup-network-helper.sh --cgroup '/sys/fs/cgroup/machine.slice/machine-qemu\x2d3\x2dvm01\x2dweb.scope'
/usr/bin/env: 'bash': No such file or directory
/nix/store/5qzqdmbf5c87h0amsxxpcnqv75kcw4yz-wrapped-plugins/libexec/netdata/plugins.d/cgroup-network ERROR : MAIN : child pid 32504 exited with code 127.
/nix/store/5qzqdmbf5c87h0amsxxpcnqv75kcw4yz-wrapped-plugins/libexec/netdata/plugins.d/cgroup-network INFO  : MAIN : there are no double-linked host interfaces available.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

@Izorkin We have a conflict, I think this is good to merge after the conflict and I will do a small test on my production.

Resolved conflict.

I am still seeing somewhat of an error, but seems unrelated to this PR:
root@staging-infra:~/ > /nix/store/605i25kkfx8n5872dv9iw7zifgnqnk85-netdata-1.38.1/libexec/netdata/plugins.d/cgroup-network-helper.sh --cgroup /sys/fs/cgroup/system.slice/systemd-udevd.service/udev
2023-03-19 19:09:04: .cgroup-network-helper.sh-wrapped: INFO: searching for network interfaces of cgroup '/sys/fs/cgroup/system.slice/systemd-udevd.service/udev'

I have no cgroup to monitor probably, so good to me.


ImportError: libcudart.so.12

Was working yesterday.
Today it gives the following error:
from vllm import cuda_utils
ImportError: libcudart.so.12: cannot open shared object file: No such file or directory

I've tried turning it off and on again multiple times.

Hi @tranhoangnguyen03 , we just released a new version (v0.2.2) which depends on PyTorch 2.1 and CUDA 12.1. This might cause error if you environment does not have CUDA 12.1.

Please upgrade PyTorch using pip install --upgrade torch
If it does not work, please install vLLM + CUDA 11.8 following the instructions here.

doesn't work
takes a long time
--> I'm reverting back to vllm==0.2.1.post1

In case anyone else runs into the same trouble as I did. Here's how to make it work on Google Colab:
!pip -q install --upgrade fschat accelerate autoawq vllm
!pip install torch==2.1.0+cu121 torchvision==0.16.0+cu121 torchaudio==2.1.0 torchtext==0.16.0+cpu torchdata==0.7.0 --index-url https://download.pytorch.org/whl/cu121

In case anyone else runs into the same trouble as I did. Here's how to make it work on Google Colab:
!pip -q install --upgrade fschat accelerate autoawq vllm
!pip install torch==2.1.0+cu121 torchvision==0.16.0+cu121 torchaudio==2.1.0 torchtext==0.16.0+cpu torchdata==0.7.0 --index-url https://download.pytorch.org/whl/cu121

Thank you! Super useful.

Hi @tranhoangnguyen03 , we just released a new version (v0.2.2) which depends on PyTorch 2.1 and CUDA 12.1. This might cause error if you environment does not have CUDA 12.1.

Please upgrade PyTorch using pip install --upgrade torch and see if the error persists.
If it does not work, please install vLLM + CUDA 11.8 following the instructions here.

Is there a cuda11.7 version?

Hi @tranhoangnguyen03 , we just released a new version (v0.2.2) which depends on PyTorch 2.1 and CUDA 12.1. This might cause error if you environment does not have CUDA 12.1.

Please upgrade PyTorch using pip install --upgrade torch and see if the error persists.
If it does not work, please install vLLM + CUDA 11.8 following the instructions here.

Is there a cuda11.7 version?

Is there a cuda11.1 version?

CUDA 12.1.

Is there a cuda11.7 version?

Hi @tranhoangnguyen03 , we just released a new version (v0.2.2) which depends on PyTorch 2.1 and CUDA 12.1. This might cause error if you environment does not have CUDA 12.1.

Please upgrade PyTorch using pip install --upgrade torch and see if the error persists.
If it does not work, please install vLLM + CUDA 11.8 following the instructions here.

Is there a cuda11.7 version?

same question, is there anyone solve it?

In case anyone else runs into the same trouble as I did. Here's how to make it work on Google Colab:
!pip -q install --upgrade fschat accelerate autoawq vllm
!pip install torch==2.1.0+cu121 torchvision==0.16.0+cu121 torchaudio==2.1.0 torchtext==0.16.0+cpu torchdata==0.7.0 --index-url https://download.pytorch.org/whl/cu121

Excuse me, what is the version of vllm?

In case anyone else runs into the same trouble as I did. Here's how to make it work on Google Colab:
!pip -q install --upgrade fschat accelerate autoawq vllm
!pip install torch==2.1.0+cu121 torchvision==0.16.0+cu121 torchaudio==2.1.0 torchtext==0.16.0+cpu torchdata==0.7.0 --index-url https://download.pytorch.org/whl/cu121

Excuse me, what is the version of vllm?

That is a very old version. I recommend you install the latest vLLM on a clean environment.


Support cryptographic checks for app repositories

Add support for signed repositories and trusted public keys in the user configuration.

Depends on #90


Consider hypercore dependency injection

Just tossing this one out there:
Replacing the top-level storage parameter with an asynchronous hypercore factory might be a nice abstraction for a few reasons:
First, storage management is already performed by hypercore, and is effectively duplicated in hyperdb -- it'd be nice to be able to write a single module that wraps storage (and networking) for a set of hypercores, then passes those up to hyperdb.
Second, introducing one level of indirection would allow us to inject objects proxies that mirror the hypercore interface. As an example use-case, consider applying permissions to local dbs (i.e. you have N writable dbs being accessed by K local programs, where only P < K programs should be able to perform writes):
Currently one would have to replicate the writable db into a read-only copy before passing it to a restricted program (correct me if I'm wrong, but I believe other approaches could be circumvented by inspecting the hypercore object). With a proxy, direct access could be transparently replaced by RPC calls that contain an auth token, for example.

It's worth mentioning a third use-case as well: locking writes to a single writable db across processes. In the current version, you'll quickly get into trouble attempting that, but RPCing requests to a single writer process would solve this.

This would also allow injecting modified hypercore versions (or wrappers), like my hypercore-encrypted.
Currently I use a fork of hyperdb that requires my module instead of the normal hypercore.
The main problem is that this would be a breaking API change...

Interesting. I am currently exploring how to handle multiple writers on a single machine without having to duplicate the database on-disk.

One writer per process is likely the way to go in most cases

Is there already a way to make that work currently? Because the "local" feed and the corresponding secret key would differ per writer, while the other feeds I want to not duplicate (for disk space reasons). I though of implementing a custom storage function that maps "local" to "peer/[current_writers_key]" but was wondering if there is a cleaner solution (or if it is considered clean to remap path names in the storage function).


Hosts editor should keep backups

Description of the new feature / enhancement
The host file editor should keep automatic backups in another file - perhaps more than one revision.
Scenario when this would be used?
If the file becomes corrupted or gets lost, then it can be restored
Supporting information
I was alternating between using Notepad and the Powertoy Hosts editor and somehow the file got truncated. Was a real pain to recreate. A backup feature would have helped a lot here!

This is already possible. Please have another look at the documentation.

I found this on the website. Hope it helps!

Hosts File Editor creates a backup of the hosts file before editing session. The backup files are located near the hosts file in %SystemRoot%\System32\drivers\etc named hosts_PowerToysBackup_YYYYMMDDHHMMSS.

Personally, in Notepad, I do "save as" and save one to my desktop first. Then when I break it five minutes later, hey there it is!

/helped


Change copyright year

Change the copyright year from 2014 to 2015.

I made a pull request to fix this


Add cloudbuild job to generate binaries and images

What type of PR is this?
/kind feature
What this PR does / why we need it:

add cloudbuild job and mage rules to build the binaries and images and push those to our bom staging GCP project to be later promoted when needed

I need to run a test before we merge this but it is pending some final bits in the GCP project
also need to create the postsubmit job which I will do soon

/assign @puerco @justaugustus
cc @kubernetes-sigs/release-engineering
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
Does this PR introduce a user-facing change?

NONE

/hold for manual tests and test infra pr

run the job on cloudbuild, run example: https://console.cloud.google.com/cloud-build/builds/74cea60f-7a43-4b6d-96b7-3ba175c19101?project=533528353884
can find the test image: https://console.cloud.google.com/gcr/images/k8s-staging-bom/global/bom?project=k8s-staging-bom
and the binaries in https://console.cloud.google.com/storage/browser/k8s-staging-bom/add-cloudbuild?project=k8s-staging-bom&pageState=("StorageObjectListTable":("f":"%255B%255D"))&prefix=&forceOnObjectsSortingFiltering=false
I will create a post submit job to run the build when we merge to main or tag
sounds good @puerco ?

/lgtm

Prow postsubmit job PR https://github.com/kubernetes/test-infra/pull/25436

Thank you @cpanato !
/lgtm

/unhold

ran here: https://console.cloud.google.com/cloud-build/builds;region=global/1b1847e1-148e-4c2c-a84f-080738c63db3?project=k8s-staging-bom
$ docker run gcr.io/k8s-staging-bom/bom:b68b231 version
  ____     ___    __  __
 | __ )   / _ \  |  \/  |
 |  _ \  | | | | | |\/| |
 | |_) | | |_| | | |  | |
 |____/   \___/  |_|  |_|
bom: A tool for working with SPDX manifests

GitVersion:    (devel)
GitCommit:     unknown
GitTreeState:  unknown
BuildDate:     unknown
GoVersion:     go1.17rc2
Compiler:      gc
Platform:      linux/arm64

checking why it did not get the git information like hash...

the binary is fine, only the the image is missing the info
$ ./main_bom-darwin-arm64 version
  ____     ___    __  __
 | __ )   / _ \  |  \/  |
 |  _ \  | | | | | |\/| |
 | |_) | | |_| | | |  | |
 |____/   \___/  |_|  |_|
bom: A tool for working with SPDX manifests

GitVersion:    v0.2.2-26-gb68b231
GitCommit:     b68b231
GitTreeState:  clean
BuildDate:     2022-03-02T09:55:14Z
GoVersion:     go1.17rc2
Compiler:      gc
Platform:      darwin/arm64


Angular 6 CLI: found 13 vulnerabilities (9 low, 4 high) run npm audit fix to fix them, or npm audit for details

Bug Report or Feature Request (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request

Versions

node --version
v8.11.3
npm --version
6.1.0
macOS: High Sierra 10.13.4
Repro steps

Step 1:
sudo npm install -g @angular/cli
Step 2:
Create new app using : ng new my-app
The log given by the failure

added 1184 packages from 1293 contributors and audited 21885 packages in 149.189s
found 13 vulnerabilities (9 low, 4 high)
  run `npm audit fix` to fix them, or `npm audit` for details
    Successfully initialized git

npm audit
npm ERR! code EAUDITNOPJSON
npm ERR! audit No package.json found: Cannot audit a project without a package.json

@freelancersunil try some of the solutions at #10963 if that pleases your code, please close this issue, and if not I'd suggest to stay tuned to #10963 because it looks like a solution will pop up there soon. Thanks for understanding :)

How can we really solve this issue


statsmodels: init at 0.6.1

Requires #8635
I've disabled the tests, because one test requires an optional dependency. The optional dependency is X-13 ARIMA, which isn't available in nixpkgs.

Just saw how 04f6a1c6656a disabled/removed a test. I'll give that a try, since that seems a better solution.

Okay, I was partially wrong with the test. One test failed, which I now removed. The test with the optional dependency is the test before the one that fails, and is skipped correctly.
I've built and tested the package locally with python 3.4. Didn't run nox-review wip because running all the tests for all versions takes a very long time.
@pSub no longer work-in-progress

Two other tests seem to fail now with Python 3.3 when running nox-review wip.
Reported upstream https://github.com/statsmodels/statsmodels/issues/2602

is this ready for review?

@domenkozar I just had a look at it again, and with the updates of numpy and such even more tests are failing. Because this version is already quite old and there haven't been any releases since then I suggest disabling the tests for now as I've done and just merging it.

@domenkozar same as above still applies.


Build tools support

WIP for build tools support

I've got that other commit at https://github.com/NotANameServer/incipyt/pull/44/commits/5b3754b439ab67806b72222326755bce8b7e8400 that adds a way to load a string-template from a file, it helps with DRY when it comes to the README, it is part of my #44 branch but I can isolate it in a dedicated PR or maybe you could cherry-pick it inside of your own branch (if you are fine with the changes).

Codecov Report

:exclamation: No coverage uploaded for pull request base (merge-2023-04-02@61ef17e). Click here to learn what that means.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@                 Coverage Diff                 @@
##             merge-2023-04-02      #45   +/-   ##
===================================================
  Coverage                    ?   49.25%
===================================================
  Files                       ?       17
  Lines                       ?      737
  Branches                    ?        0
===================================================
  Hits                        ?      363
  Misses                      ?      374
  Partials                    ?        0

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


EDU-644 Restyle lessons list on room page

Closes https://educandu.atlassian.net/browse/EDU-644
DESKTOP (ROOM OWNER):

DESKTOP (ROOM MEMBER):

PHONE (ROOM OWNER):

PHONE (ROOM MEMBER):

Closes https://educandu.atlassian.net/browse/EDU-644
[...]

So many combinations here 🤦♀ Looks nice though! 👍


Update Object.xml

Change the code and use the new method of godot4
URL:https://docs.godotengine.org/en/latest/classes/class_object.html

This PR tries changes the function shown in the examples of Object.emit_signal() itself to use Signal.emit() which is not what is being described.

Well, we're using Signal's API for connecting and disconnecting, for example. So I think this change is valid.

this entire set of paragraphs should be stripped away instead, and moved somewhere else, at best. The entire thing is needlessly long and verbose.

You are probably right there.

Rebased, and gave the PR and commit a meaningful title.
Would be good that @godotengine/dotnet checks that the C# example is correct.

Hi. Nope, this does not work in C#. Currently, the only way to emit signals is through EmitSignal (see https://docs.godotengine.org/en/latest/tutorials/scripting/c_sharp/c_sharp_signals.html#signal-emission). There are WIPs to have access to a strongly typed API (#68233), but it is not merged at the moment.

@paulloz I restored the C# code to its original state. Sorry, I’m not familiar with C#.

Looks good! Could you squash the commits? See PR workflow for instructions.

@akien-mga I am not a professional programmer. I have been reading PR workflow and learning git, and it may take a few days. If you have already helped me complete the "rebase", I am very grateful.

Yes it's all good now :) I'll merge this soon.

Thanks! And congrats for your first merged Godot contribution :tada:
And apologies for the delay getting this reviewed.


[MXNET-744] Sphinx error reduction

Description
This PR reduces the number of Sphinx errors and warnings from 1628 to 251 on a full Sphinx build.
It reduces the warnings from a Sphinx toctree being missing from 170 to 0 on incremental Sphinx builds.
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[x] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)

[x] Changes are complete (i.e. I finished coding on this PR)

[ ] All changes have test coverage:
The customizations in docs/_static/js/sidebar.js do not appear to have any tests or documentation. This PR disables some of its functionality as it behaves erratically and causes problems with the  Sphinx's documented (default) behavior.

[ ] Code is well-documented: Much of the Sphinx setup is undocumented already.
This PR helps cleanup some of problems to pave the way for a better understanding of how the parts work together, and how they might be updated or replaced.

[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
Note: while this might provide a simple preview and help test the left nav and toctree features, I'd advise looking at a full site build with the versions dropdown.

Changes

docs/get_started folder is deleted: it only held a redirect which already being handled by .htaccess. Removing it reduces warnings/errors.
docs/architecture/release_note_0_9.md is deleted: it was the only legacy release note. Release notes are held on the releases page. Removing it reduces warnings/errors.
Sphinx's docs/conf.py updates:

exclude_patterns : added these to reduce warnings/errors: ['build_version_doc' (working dir), 'api/python/model.md' (depricated), 'README.md' (not needed for Sphinx's indexing)]
update config to the working Sphinx version 1.5.6
update config to 2018 copyright
update config to have correct project URL

I disabled/removed some functionality it docs/_static/js/sidebar.js. I was able to find some info about it by digging through old commits and PRs, but many of the PRs and commits have no description or commit message. I can see that the functionality may have been of some benefit before where it magically modified the output of Sphinx. However, since it wasn't documented, this caused me hours of frustration when Sphinx's documented behavior was being nullified by this client-side activity.

Replaying the previous sidebar layout and merging with the existing one plays havoc with the UI after one has gone through and configured the toctree for each folder. This is why I removed it. It is possible if the original authors took a look, they could update it, but for reasons I outline later, I think it would be better to remove it.
Adding Clojure to the nav can come in a separate PR. But since I was in the sidebar already, I added it.

Added new index pages where ones were missing or modified existing ones. This is generally a good practice for SEO, and drastically improves the warnings/errors situation.

I used the :hidden: directive for tutorials and faq as they already have custom indexes, but were the source of many warnings/errors.
I skipped modifying index pages that did not result in warnings/errors.
I used the :glob: pattern where I could to auto-index a folder. This works best when there are no subfolders to index. You can see this mostly in the tutorials section. :

.. toctree::
   :glob:
    *

Comments

As we gear up for foreign translations of the site, I really can't see how undocumented, custom client-side overrides are going to be maintainable. We should work within the features of the site generator. I recommend we try to fix the site at it's core and as part of a regular build pipeline, and remove these kind of "magical" features.
There is additional complexity with the versions dropdown that seems to be covered in the sidebar logic. Disabling this client-side hack might result in uncovering more issues and entanglements. I'd appreciate any SMEs to assist figuring out solutions that can help simply things and get us ready for internationalization of the site.

Usage
These changes gets triggered in a regular make docs, but you can run just the Sphinx section of the docs pipeline by commenting out these in docs/mxdoc.py:
#app.connect("builder-inited", generate_doxygen)
#app.connect("builder-inited", build_scala_docs)
#app.connect("builder-inited", build_clojure_docs)

Then run (from /docs):
make html

@ThomasDelteil @thomelane @sandeep-krishnamurthy @kevinthesun @piiswrong @mli @nswamy @marcoabreu - you all use this, or have used it... please let me know if you have any suggestions.

Thanks for cleaning this up @aaronmarkham

I found an issue with the versions and the sidebar.js. The sidebar is missing in the API pages with older versions (non-master). Let's hold off merging until I can figure out what magic it was doing.

UPDATE:
Part of the problem is changes I make here are not viewable in the full site build pipeline as that checks out from specific branches on the main repo and not my fork. Then each legacy version only uses the configurations it has and not any updates I make here.
So... while I can fix the current build, the builds for every other version are still buggy as hell. :confounded:
I'm working on the tooling now so that you can supply logic from your fork/branch and supply that as an arbitrary version in the build. This process also is belabored by every version and every API build which makes for test cycles of about 40 minutes.  I'm updating the build tools to turn on/off documentation sets via a config file instead of how they're hard-coded in the Sphinx plugin file, mxdoc.py. I've got it down to 18 minutes for all versions.
This has led to certain realizations.
:bulb: We're probably going to have to refactor the docs build process, so that we have better control.
:bulb: Each version should be built separately and maintained separately, rather than an overlapping pipeline.
:bulb: Each version should be built with configurations held in master, or...
:bulb: We're probably going to have to make some commits to the old version branches to fix legacy bugs, so that we're not doing hot patches during every build.
:bulb: Maybe we can cache old versions and not have to rebuild every time. Then builds can be done in a few minutes.
:bulb: And finally, maybe I can actually debug whatever is going on with this Sphinx theme! Or if anyone really knows Sphinx theme customization and how this code works, they can help address why the left navigation behaves unexpectedly now that index files and table of contents are being supplied as per Sphinx's documentation. Basically, it seems to copy state from previous views and when you toggle between versions --> shenanigans.
Any help would be appreciated. :pray:

I rebased this on top of #11990, so I get the benefit of the docs build tools refactor.
Also, the Jenkinsfile in this PR will need to be reset to production settings once everything is approved.

Using the new build pipeline, I created a preview website with the versions dropdown to show what happens with the toctree updates. Note that the dropdown show my fork's branch, which was used to create one of the versions of the website, and as the default version. Here's a screenshot showing the left side nav is unexpectedly different. Not bad really. Just not what we had before. It now lists the APIs which is coming from the toctree.

Here's the view if you switch to the 1.2.1 version:

I'm not sure how to make the updated version where all of the toctrees are in place, to look like the old version. Or, maybe the old version was always buggy, but we didn't realize it since it worked despite all of the Sphinx errors.
If no one is opposed to this new behavior for the left navigation, then I would say this PR is ready.

Looks good

Need to rebase and test after recent updates! Let me do that before merging. Thanks!

This is viewable here: http://<IP_ADDRESS>/
Looks good to me.
I should have noted earlier that this only fixes the errors in master and versions going forward. There are still a ton of errors when we build the old versions of the docs and website. I think this patch could be applied to each old branch with good success if that's of interest.


[help] How to call other lua plugin exposed methods

Like I want to develop my own plugin based on telescope, is it possible to use nvim-ox? Thanks

Hello ! I've got the same question. :smile:
Moreover I think that it would be a good example.

Ok so after searching a couple hours, I understood that I was supposed to use mlua. Here is a small example :
// You must add `mlua` as a dependency in your Cargo.toml file.
use mlua::prelude::{LuaFunction, LuaTable};

use nvim_oxi::{self as oxi, Dictionary, Function};

// I don't understand yet what is this `_none` parameter.
// I added it and it's working but I guess I'll need to understand why at some point.
fn mlua_test(_none: ()) -> oxi::Result<()> {
    // You must also add feature `mlua` for nvim_oxi to your `Cargo.toml` as well.
    let lua = oxi::mlua::lua();

    // `lua.globals()` returns a reference to the global table of the Lua state.
    // `LuaFunction` is the type of what you `get` from the global table.
    // In this case it's a Lua function.
    let require = lua.globals().get::<_, LuaFunction>("require")?;

    // You can call this fuction like this to get the `telescope.builtin` table.
    let telescope_builtin: LuaTable = require.call("telescope.builtin")?;

    // I think that you get the point now.
    let find_files = telescope_builtin.get::<_, LuaFunction>("find_files")?;
    find_files.call(())?;

    Ok(())
}

#[oxi::module]
pub fn my_module() -> oxi::Result<Dictionary> {
    let mlua_test = Function::from_fn(mlua_test);
    Ok(Dictionary::from_iter([("mlua_test", mlua_test)]))
}

I guess that you can go there for more in depth mlua usage -> https://github.com/mlua-rs/mlua

// I don't understand yet what is this _none parameter.

You need to add it because Function::from_fn() accepts a closure (or a function in this case) whose argument implements Poppable. If your function doesn't take any arguments you can just use (), just like you did.

I'll close this as completed but feel free to re-open it if you still have questions.


[backend] [feature] Added Idgenerator

Codecov Report

Merging #1 into master will increase coverage by 0.05%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master       #1      +/-   ##
==========================================
+ Coverage   96.71%   96.76%   +0.05%
==========================================
  Files          30       31       +1
  Lines         365      371       +6
  Branches       14       14
==========================================
+ Hits          353      359       +6
  Misses         12       12

Impacted Files
Coverage Δ

...es/monolith-backend/src/IDGenerator/IdGenerator.js
100% <100%> (ø)

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 134711b...51eafb6. Read the comment docs.


samples: drivers: counter: alarm: Fix compilation for nrf boards

Sample was not compiling for nordic boards because RTC_0
instance was not enabled by default and RTC_0 device is using
different DT define.
Signed-off-by: Krzysztof Chruscinski<EMAIL_ADDRESS>

@carlescufi @nashif can we merge it?


mac-2 & mac-8 lost external connect phone device.

Type of Request
bug
Infrastructure Environment
LUCI, Github, Cocoon scheduler, Autosubmit, etc...
What is happening?
mac-2 & mac-8 lost external connect phone device.

Steps to reproduce
Step 1:
Step 2:
..
Step n:
Expected results
I expect to see X when Y is finished.

Rebooting both machines to restore connection.


Support SolidFire iSCSI Expansion

hi,
we are using trident 18.10 in production, using solid-fire iSCSI as a backend, OpenShift cluster version 3.9 (upgrading to 3.11 soon).
we would like to know if iSCSI resize is in the road-map.
we looked at this commit but the feature isn't available yet.
we understand that the file system resize part is missing currently, not sure how to implement it (daemon set?).
this feature very important to us, and willing to contribute for this feature, but we would love some guidance with how exactly to do this .
thank you, best regards.

If this isn't natively available yet, are there any workarounds that can be executed to manually resize an iscsi PVC?
I attempted to update the requests field in my PVC, but it returned an error on Kubernetes 1.13
...
spec:
  accessModes:
  - ReadWriteOnce
  dataSource: null
  resources:
    requests:
      storage: 30Gi
...

You can run `kubectl replace -f /var/folders/5k/wvflv8r90551zw2798jcbh6h0000gn/T/kubectl-edit-06cpa.yaml` to try this update again.```

This is how to do it

Resize your ISCSI volume in solidfire
Terminate your pod that was mounting that volume
Allow pod to get re-created
SSH to node that the pod is running on
Run lsblk to find out the Device ID of your iscsi volume (i.e. /dev/sdc for example)
Assuming an ext4 filesystem, run resize2fs /dev/sdc (the device ID that you identified previously)
Your container should now see the larger filesystem
NOTES
Your pv and pvc resources in Kubernetes won't know that you resized it, so they will still show the old size.
You may be able to avoid pod deletion by rescanning the iscsi targets - YMMV.

Feature added in 19.10: https://github.com/NetApp/trident/releases/tag/v19.10.0


ERROR: Unable to load library steamclient64.dll

Hello!
I would like to understand better and how to resolve this error.
I have the F1 2021 game files and I was able to successfully crack them using the tool.
When I try to start the game, the following error message appears: Unable to load library steamclient64.dll
Prints.:
https://uploaddeimagens.com.br/imagens/6yxRTL8
https://uploaddeimagens.com.br/imagens/Suwdasg

Hi! Sorry for the late answer.
This game seems to use Denuvo DRM or another type of DRM that SAC can't handle.
It seems like the game wasn't cracked by anyone yet, so it's probably Denuvo, but I could be wrong, I didn't search much.
https://cs.rin.ru/forum/viewtopic.php?f=10&t=112737


Disable broken e2e tests

What does this PR do?
Temporarily disable the Kind e2e tests on oldest versions of Kubernetes because of an issue still under investigation.
Motivation
On those oldest versions of Kubernetes, the cluster-agent admission controller is injecting a continuous profiler library that is breaking the alpine-based containers.
It makes them fail with:
Error loading shared library ld-linux-x86-64.so.2: No such file or directory (needed by /datadog-lib/continuousprofiler/Datadog.Linux.ApiWrapper.x64.so)
Error relocating /datadog-lib/continuousprofiler/Datadog.Linux.ApiWrapper.x64.so: __strdup: symbol not found

Additional Notes
https://dd.slack.com/archives/CLWN64GAW/p1719500225503479
Possible Drawbacks / Trade-offs
Describe how to test/QA your changes

/merge


Error in mPointStart

mPointSize is using a.getColor(R.styleable.CustomGauge_pointSize,0) instead of a.getInt(R.styleable.CustomGauge_pointSize,0)  because of which it was giving errors. Should it be getColor or getInt ?

As I remember getColor is correct. Can you copy+paste this error?
Pawel
Pozdrawiam, Best regards,
Paweł Kleczkowski  |  Freelancer - Mobile Developer
mobile  +48 669 934 133
email<EMAIL_ADDRESS><EMAIL_ADDRESS>skype  pkleczko
Rozwiązania Informatyczne dla Biznesu - Paweł Kleczkowski
03-556 Warszawa, ul. Handlowa 34/17
www.pawelkleczkowski.pl
2015-06-23 10:23 GMT+02:00 Ravi Shenoy<EMAIL_ADDRESS>
mPointSize is using a.getColor(R.styleable.CustomGauge_pointSize,0)
instead of a.getInt(R.styleable.CustomGauge_pointSize,0) because of which
it was giving errors. Should it be getColor or getInt ?
—
Reply to this email directly or view it on GitHub
https://github.com/pkleczko/CustomGauge/issues/1.

Why should it be getColor() ? The pointSize in xml is setting the point size, an int and the parser is just setting to mPointSize. Color is set separately, isnt it ?

Oh, yes, it's mPointSize (size). You're probably right. In fact I
remembered this code had worked for me, but maybe I made some changes and
didn't verify them. If it works for you with getInt it's a bug.
Pozdrawiam, Best regards,
Paweł Kleczkowski  |  Freelancer - Mobile Developer
mobile  +48 669 934 133
email<EMAIL_ADDRESS><EMAIL_ADDRESS>skype  pkleczko
Rozwiązania Informatyczne dla Biznesu - Paweł Kleczkowski
03-556 Warszawa, ul. Handlowa 34/17
www.pawelkleczkowski.pl
2015-06-23 11:46 GMT+02:00 Ravi Shenoy<EMAIL_ADDRESS>
Why should it be getColor() ? The pointSize in xml is setting the point
size, an int and the parser is just setting to mPointSize. Color is set
separately, isnt it ?
—
Reply to this email directly or view it on GitHub
https://github.com/pkleczko/CustomGauge/issues/1#issuecomment-114423259.

Thanks for the response. getColor will also work, because getColor also takes Int and returns Int. But it might return a size (some enum) it might be the size that app wants.


Please provide an api key.

Hi, First of all I would like to thank you on the amazing work on building this package.
Running this piece of code:
library(indicoio) make_request(api_key="67a9e47bea0d36924569edfcfa94ee74")  emotion <- sentiment("Thanks everyone for the birthday wishes!!                       It was a crazy few days ><")
I got the error message:
Error in request_url(cloud, api, batch, api_key, version, apis, method,  :    Please provide an api key.
I do have the api key but i just cant get to understand how i can get around this error on Rstudio.
Thanks for the assistance.

I got it sorted thanks
emotion <- sentiment("Thanks everyone for the birthday wishes!!                       It was a crazy few days ><", api_key = 'XXXXXXXXXXXXX') emotion


Get slider instance in two different sliders

I have an issue with two sliders, when i use them as SwiperDirective.
I have #slider1, and #slider2 for example, how can i get instance of these sliders using ViewChild?
Actually, I want to create gallery with thumbnails and use slider1 control for slider2 like in this example:
 galleryTop.controller.control = galleryThumbs;     galleryThumbs.controller.control = galleryTop;
There's no exapmle for getting instance of two different SwiperDirective.
Could you help, please?

Check angular documantation, you can name the component in the template and use the name with the viewchild.

And then we have ElementRef, but not the swiper insatnce.

Yes you can tell the type with the name just check the Angular documentation :) Like #mySwiper="ngxSwiper".

Atm you need to use directive though, the component is missing the exportAs. I will add it for next release.

Do you mean component instead of directive?

No, I mean that only the directive has the exportAs which is needed for you to be able to target the directive reference with the name. So you need to use the swiper directive for now. Next 5.1.0 release will have the exportAs in the component as well so then its possible to use the same way to get the component references.
Of course you can already use ViewChildren for component as well. Anyway all this is basic Angular stuff not related to this library or this library usage. You just need to check the Angular documentation about ViewChild and ViewChildren.