button area got cut off when app is switched from portrait to horizontal

Note: If you are having problems formatting your issue please refer to this article on using markdown in Github:
https://guides.github.com/features/mastering-markdown/
Note: for support questions, please use one of these channels:
https://forum.ionicframework.com/
http://ionicworldwide.herokuapp.com/
Short description of the problem:
open alert box in portrait mode (android phone), switch device to horizontal mode, buttons became cut off by the bottom of the screen.
Screenshot: http://screencast.com/t/ELvv5airZmD
What behavior are you expecting?
Steps to reproduce:
1.
2.
3.
insert any relevant code between the above and below backticks

Other information: (e.g. stacktraces, related issues, suggestions how to fix, stackoverflow links, forum links, etc)
Which Ionic Version? 2.x
Plunker that shows an example of your issue
For Ionic 1 issues - http://plnkr.co/edit/Xo1QyAUx35ny1Xf9ODHx?p=preview
For Ionic 2 issues - http://plnkr.co/edit/me3Uk0GKWVRhZWU0usad?p=preview
Run ionic info from terminal/cmd prompt: (paste output below)

Same problem. Is there any solution?


⚠ Bofrost.lu has degraded performance

In f3835e2, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1268 ms

Resolved: Bofrost.lu performance has improved in 76f28e8 after 6 minutes.


Move client docs

[ ] Update header link in https://twiki.opensciencegrid.org/bin/view/Documentation/Release3/InstallWNClient
[ ] Update header link in https://twiki.opensciencegrid.org/bin/view/Documentation/Release3/InstallWNClientTarball
[ ] Update header link in https://twiki.opensciencegrid.org/bin/view/Documentation/Release3/UsingOSGWnClientFromOASIS
[ ] Update header link in https://twiki.opensciencegrid.org/bin/view/Documentation/Release3/UsingWorkerNodeClient
[ ] Update header link in https://twiki.opensciencegrid.org/bin/view/Documentation/Release3/InstallGlexec
[ ] Update header link in https://twiki.opensciencegrid.org/bin/view/Documentation/Release3/InstallCvmfs

@drdaved this would also affect the cvmfs/singularity docs that you wrote recently


Add support for autoConnect (and make default) on Android

Martijn van Welie wrote a great article, Making Android BLE work — part 2, which includes a very informative section on autoConnect = true.
Making autoConnect = true the default, as it is generally easier to manage and will match how Kable behaves on Apple platforms.
Closes #410

Note to self: need to integrate reflection based workaround for autoConnect sometimes not being honors on Android API < 23.

Had a question regarding this comment on that issue thread:

TL;DR;
Always call BluetoothDevice#connectGatt() with autoConnect=false (the race condition does not affect that case). If that connection times out you will get a callback with status=133. Then call BluetoothGatt#connect() to initiate a background connection.

Is that a strategy we should employ, or is it ok for our purposes to just always go in with autoConnect=true?

The race condition they are describing only affects Android <= 6 (or, API level <= 23, aka M). Kables minimum support Android version is 5, so the race condition will only hit apps (using Kable) and running on Android 5-6. According to https://apilevels.com/, those versions make up <3% of the phone population. Regardless, I've integrated a workaround for the bug linked, whereas we use reflection (essentially accessing private APIs) to forcefully make sure that the auto connect property is correct, see Reflection.kt. Therefore, the race condition described in that issue won't hit the very small % of users on affected Android versions.
As for if we should always use autoConnect = true, it is slightly slower, but in my testing it wasn't noticeably slower. Because it never times it, the code that calls it tends to be simpler, and I'm hoping that makes for a more reliable user experience (despite being slightly slower to connect).
Additionally, you can get GATT 133 errors for a huge assortment of failures, so to use that to decide to switch to autoConnect = true doesn't feel consistent to me.
Ultimately, if we always use autoConnect = true, I believe we'll test that codepath more and it will ultimately be a better BLE experience.
The article linked in the PR description (autoConnect = true also recommends it as the "preferred way to reconnect". 🤷

@davidtaylor-juul I ended up backtracking on my decision to have the autoConnect be static for the life of a peripheral. I see value in the strategy described in the thread you linked.
Updated to have auto-connect configured via a lambda predicate so that library consumers can employ strategies like the one described in your linked thread.


rename DesktopNav to SiteNav

What does this PR do and why?
Provide a description of what this PR does. Link to any relevant GitHub issues, Notion tasks or Discord discussions.
Screenshots or screen recordings
If applicable, provide screenshots or screen recordings to demonstrate the changes.
Acceptance checklist

[ ] I have evaluated the Approval Guidelines for this PR.
[ ] I have tested this PR in all supported browsers.
[ ] I have tested this PR in dark mode and light mode (if applicable).

Current dependencies on/for this PR:

main

PR #2233

PR #2234

PR #2235

PR #2236

PR #2237

PR #2238

PR #2239

PR #2240   👈

This comment was auto-generated by Graphite.

Graphite Merge Job
Current status: ⏳ Queued to merge
This pull request is currently queued to be merged as part of a stack.
This comment was auto-generated by Graphite.

Job Reference: QYaAht6eMvR7hTnqghel


[mkldnn-v1.0] Rebase the feature branch to the latest master

Description
This PR indents to rebase the feature branch to the latest master to mitigate the discrepancy of the two branches, especially there are some fixes for flaky tests on the master branch which will also save the CI on this feature branch.
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

Puh rebasing makes it really messy since history rewrites are not allowed. How about a merge commit instead?

Thank you @marcoabreu. I didn't know which one is a better practice. But I see the commit ids in the PR are exactly the same as they are in the master history. Anyway I will try your suggestion right now.

@marcoabreu, just force pushed to the PR branch. Hope it looks good to you now. :)

BTW, which option is preferred when merging this PR to the feature branch, "squash and merge" or "rebase and merge"?

Either rebase and merge or merge commit. I'd recommend you to make a copy of the target branch and try out both methods. Then you will see the difference.

Either rebase and merge or merge commit. I'd recommend you to make a copy of the target branch and try out both methods. Then you will see the difference.

"merge commit" is disabled for this repository. "rebase and merge" has conflicts per my experiment. So we just have the last option: "squash and merge". :(

@pengzhao-intel Please review and approve if possible. Thanks!

You have write access to the branch, so you can also just make a merge commit directly without the PR process. Feel free to go ahead.

Just make sure to not force-push please :)


Helidon MP 2.3.0 does not follow Microprofile 3.3 standard

Environment Details

Helidon Version: 2.3.0
Helidon MP
JDK version: 11.0.7
OS: Windows/Linux
Docker version (if applicable): NA

Problem Description
Helidon MP 2.3.0 introduced a dependency upgrade of Jersey en MP RestClient 2.0 (see https://github.com/oracle/helidon/pull/2971) which makes this release partly following the MicroProfile 4.0 standard.
When coding against the MicroProfile standard 3.3 using the corresponding MP RestClient, it is not possible to upgrade Helidon MP 2.2.2 to Helidon MP 2.3.0 while keeping our code compatible with MicroProfile 3.3 standard.
Which Helidon MP release is scheduled to implement the MicroProfile 4.0 standard completely?

When coding against the MicroProfile standard 3.3 using the corresponding MP RestClient, it is not possible to upgrade Helidon MP 2.2.2 to Helidon MP 2.3.0 while keeping our code compatible with MicroProfile 3.3 standard.

What exactly makes it impossible to upgrade your app?

When coding against the MicroProfile standard 3.3 using the corresponding MP RestClient, it is not possible to upgrade Helidon MP 2.2.2 to Helidon MP 2.3.0 while keeping our code compatible with MicroProfile 3.3 standard.

What exactly makes it impossible to upgrade your app?

We do not develop our application for Helidon MP (use Helidon as a runtime only) but compile our code against the MicroProfile 3.3 interfaces. In our code we are using the RestClient API interfaces coming with MicroProfile 3.3, which turned to be incompatible with the RestClient implementation coming with Helidon 2.3.0.
It seems Heldion 2.3.0 is still implementing the MicroProfile 3.3 version, except for the MP RestClient API 2.0 which is part of the MicroProfile 4.0 standard (Implementation within Helidon 2.3.0 is from Jersey, i guess?)
I hope that i was able to clearify our setup.

@gtenham Yes, Jersey 2.34 is bringing support for RestClient 2.0. With some pom gymnastics, there should be way to downgrade the API and the Jersey module that implements RestClient. I just tried it out in some basic app: the general idea is to exclude the new and include the old.
First exclude new deps from Helidon bundle, or wherever they are pulled from in your pom as reported by mvn dependency:tree:
       <dependency>
            <groupId>io.helidon.microprofile.bundles</groupId>
            <artifactId>helidon-microprofile</artifactId>
            <exclusions>
                <exclusion>
                    <groupId>org.glassfish.jersey.ext.microprofile</groupId>
                    <artifactId>jersey-mp-rest-client</artifactId>
                </exclusion>
                <exclusion>
                    <groupId>org.glassfish.jersey.ext.microprofile</groupId>
                    <artifactId>jersey-mp-rest-client</artifactId>
                </exclusion>
            </exclusions>
        </dependency>

Next include the old API and Jersey jars as follows:
        <dependency>
            <groupId>org.glassfish.jersey.ext.microprofile</groupId>
            <artifactId>jersey-mp-rest-client</artifactId>
            <version>2.33</version>
            <scope>test</scope>
            <exclusions>
                <exclusion>
                    <groupId>jakarta.enterprise</groupId>
                    <artifactId>jakarta.enterprise.cdi-api</artifactId>
                </exclusion>
                <exclusion>
                    <groupId>javax.enterprise</groupId>
                    <artifactId>cdi-api</artifactId>
                </exclusion>
            </exclusions>
        </dependency>
        <dependency>
            <groupId>org.eclipse.microprofile.rest.client</groupId>
            <artifactId>microprofile-rest-client-api</artifactId>
            <version>1.4.1</version>
        </dependency>

Note that the deps above refer to Jersey 2.33 instead of 2.34 and revert the RestClient API to the previous version. Let me know how it goes.

@gtenham Yes, Jersey 2.34 is bringing support for RestClient 2.0. With some pom gymnastics, there should be way to downgrade the API and the Jersey module that implements RestClient. I just tried it out in some basic app: the general idea is to exclude the new and include the old.
First exclude new deps from Helidon bundle, or wherever they are pulled from in your pom as reported by mvn dependency:tree:
       <dependency>
            <groupId>io.helidon.microprofile.bundles</groupId>
            <artifactId>helidon-microprofile</artifactId>
            <exclusions>
                <exclusion>
                    <groupId>org.glassfish.jersey.ext.microprofile</groupId>
                    <artifactId>jersey-mp-rest-client</artifactId>
                </exclusion>
                <exclusion>
                    <groupId>org.glassfish.jersey.ext.microprofile</groupId>
                    <artifactId>jersey-mp-rest-client</artifactId>
                </exclusion>
            </exclusions>
        </dependency>

Next include the old API and Jersey jars as follows:
        <dependency>
            <groupId>org.glassfish.jersey.ext.microprofile</groupId>
            <artifactId>jersey-mp-rest-client</artifactId>
            <version>2.33</version>
            <scope>test</scope>
            <exclusions>
                <exclusion>
                    <groupId>jakarta.enterprise</groupId>
                    <artifactId>jakarta.enterprise.cdi-api</artifactId>
                </exclusion>
                <exclusion>
                    <groupId>javax.enterprise</groupId>
                    <artifactId>cdi-api</artifactId>
                </exclusion>
            </exclusions>
        </dependency>
        <dependency>
            <groupId>org.eclipse.microprofile.rest.client</groupId>
            <artifactId>microprofile-rest-client-api</artifactId>
            <version>1.4.1</version>
        </dependency>

Note that the deps above refer to Jersey 2.33 instead of 2.34 and revert the RestClient API to the previous version. Let me know how it goes.

We are using the helidon-core bundle so only need to change the rest-client dependency part.
Works for me.
Waiting anxious for Helidon supporting MP 4.
Thanks.

Could you please check if your MP specifications are defined in compile or provided scope in your application?
If you compile against them and the use helidon bundle, it should be sufficient to change the scope to provided for MP Rest client.
The API has not changed, so there should be not problem changing the dependency.
If this does not help, would you kindly share the stacktrace you get?
Thanks a lot,
Tomas

@tomas-langer
Added mvn dependency-tree and runtime stacktrace after changing Helidon to version 2.3.0 with MicroProfile 3.3 in attachment.
MP Restclient scope changed to provided. Still not able to run the application
Gerton
helidon-bugreport.zip

@gtenham The dependencies file in your zip file is empty. Could you provide that and possibly your pom? I got the runtime error from the other file.

mvn-dependencies.txt

@gtenham Thanks, it would really help if you can attach your pom as well. It would help me understand some things in the deps file. Otherwise, if you can't share, we should consider creating a sample app that shows the problem.

@spericas Uploaded a sample multi-module project with a pom-file setup which look like our project setup.
parent pom contains the versions for MicroProfile and Helidon
service-a module contains a basic jaxrs service with one endpoint http://localhost:8080/service-a/ping
service-b module contains a restclient to service-a called through http://localhost:8081/service-b/ping
When calling service-b endpoint an error occurs from the rest client which is different than the one uploaded before (probably due to some additional code not in this sample)!
When changing helidon.version property to 2.2.2 everything works fine also when changing the service-b pom-file using the workaround provided (change jersy-rest-client to 2.33) combined with helidon 2.3.0 it also works fine.
I hope this helps you investigating the problem
sample-project.zip

@gtenham Thanks, this helps. First thing I see is that your pom files do not generate self-contained, executable jar files. How are you executing these services? Using an IDE?

@gtenham Made a few changes to your sample to produce executable jars and was able to reproduce the problem.
Caused by: java.lang.NoSuchMethodError: 'org.eclipse.microprofile.rest.client.RestClientBuilder org.eclipse.microprofile.rest.client.RestClientBuilder.followRedirects(boolean)'
	at org.glassfish.jersey.microprofile.restclient.RestClientProducer.create(RestClientProducer.java:142)
	at org.jboss.weld.contexts.unbound.DependentContextImpl.get(DependentContextImpl.java:64)
	at org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:100)
	at org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50)
	at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:694)
	at org.jboss.weld.manager.BeanManagerImpl.getInjectableReference(BeanManagerImpl.java:794)
	at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:92)

This is because Jersey is calling a 2.0 API method. So, in summary, if you force the classpath to include Rest Client 1.4, then you'll run into this error. But from the point of view of the application, there is no incompatibility: your application should run without changes provided the classpath is setup properly. If it is required for you to use Rest Client 1.4, then you'd need to downgrade Jersey's module as discussed above.

@spericas Thanks for the update.
Rest Client 1.4 is part of MicroProfile 3.3 and Rest Client 2.0 is part of MicroProfile 4, which means my issue is valid that Helidon MP 2.3.0 is not fully compatible with MicroProfile 3.3 nor MicroProfile 4.0.
This means i have to downgrade Jersey Rest Client to stay updated with Helidon 2 MP as a MicroProfile implementation or change implementation.

Reopening so we can provide some documentation about this

@gtenham I'm not saying it is invalid, just that there's an easy workaround. For example, in your sample project, if you swap the imports on your main pom.xml, you should get the 2.0 jar.
We are currently discussing using reflection in Jersey to remain fully compatible with the 1.4 jar. Will keep you posted.

Jersey's PR https://github.com/eclipse-ee4j/jersey/pull/4835

@gtenham This issue is now targeted for 2.4.0. Stay tuned.

Integration with Jersey 2.35 is now complete. This incompatibility issue will resolved in Helidon 2.4.0.


docs: Issue in page Build an IoT App with JavaScript - redendent Scylla setup phases

I would like to report an issue on page https://iot.scylladb.com/master/build-with-javascript
Problem
The JS page includes instructions on setting up a Scylla Cluster with Docker.

This is redundant wit the same info in https://iot.scylladb.com/stable/getting-started.html
Do not mention the Scylla Cloud / Terraform alternative

Now I'm finally getting into this issue, so: besides the Terraform example, all other projects has a docker-compose.yml.
Would be a good thing to have a folder specifically for the docker instance instead have to manage all the images in a update.


Add baseurl to all URLs in templates and redirects.

https://github.com/thephpleague/omnipay-example/issues/3
Here you go - take it or leave it :-)
I personally find the example application very useful when developing on a gateway, and also as the first point of call when trying to understand OmniPay for the first time. There are so many different platforms to develop on these days, that it helps to have this flexibility. I tend to have so many things on the go at once, that it is easier to plonk a bunch of projects on one server than to have a gazzillion servers brought up all over the place. But YMMV, naturally :-)
I've tested this in a sub-directory and also the root folder of a domain, with mod_php 5.4, and it works for me, though there could always be some path I've not taken into account.

Thanks @judgej !

Thanks :-)
I've just tested it from the command line on a non-GUI server using php -S localhost:8081 and the lynx text browser. It looks rather nice like that.


Chips, and their underlaying fd's, should be closed in FindLine

Hi
In FindLine, I would imagine chips and underlying file descriptors should be closed for us not to leak file descriptors
Best

Yeah, that makes sense.


[Feature Request] Support the new user profile banners

Title ^

I thought about it, the problem is that initially there is no way to call any context menu on the banner


Is --recursive-copy-metadata supported somehow?

If not, how could one add support?

Hi @matanyall,
Package metadata copy is not yet supported, could be a nice feature to add to the plugin.
I have at the moment not the time to implement this feature but feel free to open a pull-request.

Available in v1.1.9
Example pyproject.toml
[tool.poetry-pyinstaller-plugin]
recursive-copy-metadata = [
    "requests"
]


Typos Roundup 1

Used cSpell to flag some typos and put the fixes into individual commits

@nschonni : Thanks for your contribution! The author, @evanwindom, has been notified to review your proposed change.

@nschonni : Thanks for your contribution! The author, @evanwindom, has been notified to review your proposed change.

@nschonni : Thanks for your contribution! The author, @evanwindom, has been notified to review your proposed change.


CopyingHandler OnCopy method in RichTextBox does not work as expected

I have tried your repository. Thank you for your great effort! I have checked the CopyingHandler in RichTextBox. But it doesn't work as expected regardless of the selection. It just copies space characters of the number of selected characters. Anyways I have solved the issue internally. If you wish, I can provide you the modified code. :) Though my code is not well-optimized, but it just works as expected.

Thanks for the report. RichTextBox is not very well designed for now, only TextBlock is in a reasonably good shape. I would be happy to have a look at your code.

Feel free to let me know if any further change is necessary to fix the issue! :)

I'm came up with this solution:
 protected void OnCopy(object o, DataObjectCopyingEventArgs e)
{
    string clipboard = "";

    for (TextPointer p = MsgViewer.Selection.Start, next = null;
            p != null && p.CompareTo(MsgViewer.Selection.End) < 0;
            p = next)
    {
        next = p.GetNextInsertionPosition(LogicalDirection.Forward);
        if (next == null)
            break;

        var t = new TextRange(p, next);
        var emoji = (next.Parent as Run)?.PreviousInline as Emoji.Wpf.EmojiInline;
        if ((p.Parent as Run).PreviousInline != emoji && emoji != null) clipboard += emoji?.Text;
        else clipboard += t.Text;
    }

    Clipboard.SetText(clipboard);
    e.Handled = true;
    e.CancelCommand();
}

Thank you for your contributions and your patience. After lots of inaction and a lot of reading, too, I finally found a more elegant solution to this problem.

I closed this issue some time ago, but I just wanted to let you know copy/paste support has been greatly improved in the current master branch, and Undo/Redo now works properly, too.

I closed this issue some time ago, but I just wanted to let you know copy/paste support has been greatly improved in the current master branch, and Undo/Redo now works properly, too.


Import Error on version update

Expected Behavior
When importing two files, an interface with a component referencing the v1 schema and the v2 interface versioned with additional properties, the models should be imported. I would expect the folder structure to be this after running the command:
versionedRepo
    testmodel.json
    testcomponentmodel.json
localRepo
    testmodel-1.json
    testmodel-2.json
    testcomponentmodel-1.json

Actual Behavior
The dmr-client will see duplicate properties and fail to import the new interface.
Error:
[Error]: dtmi:TestModel:UnchangedProperty;1 has more than one definition. Remove all but one JSON object containing '@id' property with value dtmi:TestModel:UnchangedProperty;1, or change the '@id' values so there are no duplicates.

Steps to Reproduce
Run the command from the attached repository: tests.zip
dmr-client import --directory ./versionedRepo --search-pattern "*.json" --local-repo ./localRepo

versionedRepo/testdevice.json and versionedRepo/testcomponentmodel.json  have the same @id what is not permitted in the DMR, each interface must be unique.
if you want to version TestModel, it should have  a new version.

Sorry, I attached the wrong files with a copy and paste error. I've attached an updated example with the correct files.
tests.zip

I see, seems there is a conflict when the updated model has an @id in a property. I see two workarounds:

remove the '@id' from the property
import files one by one instead of importing the full folder.


cIient is zoomed in

When i launch the hooked client, i cant see most of the client as it is liked zoomed in and doesnt fit to the window. I only see the parts as i captured in the screenshot.

Hey,
Duplicate issue (most likely)
I am currently aware of this. The problem is not with Mecha itself, but how the client works by default. This is due to the CEF build the League of Legends client uses, which has this issue.
I already have a (semi-)fix for this coming with the next update.
I will leave this issue open until then.

for the time being I solved the issue by switching to 100% in the scaling but the issue persists in the 125%

How can I set the scale to 100%? help pls


Training process gets killed.

Hi!
When running train.py the process always gets killed for some reason.
Could you please help with pointing out if I am doing anything wrong?
I have attached my terminal output.
trainkilled.txt

Hi! I have tried playing around with the data I use, but the train.py still gets killed during epochs.
Maybe I'm not fully understanding what kind of data should be in certain files.
I have a correctly formatted corpus of data.

Should the train_processed_dialogs.txt and val_processed_dialogs.txt contain the same dialog sets?
train_processed_dialogs.txt
val_processed_dialogs.txt

Here are the contents I have in the quality folder:
context_free_questions.txt
context_free_test_set.txt
context_free_validation_set.txt
I made the context_free_test_set.txt contain a sample of context free dialogs from the train_processed_dialogs.txt file. Then I made the context_free_questions.txt contain only the questions from the context_free_test_set.txt file.
What should be the contents of the context_free_validation_set.txt file?
At the moment I have made it to contain a sample of dialogs from the train_processed_dialogs.txt which are not in the context_free_test_set.txt file.
Could you please confirm if this is incorrect?
Unfortunately I could not get a proper understanding of what the exact functionality of val_processed_dialogs.txt and context_free_validation_set.txt files is.
Any help would be much appreciated.

@vasiabratchuk The format of your data seems to be correct. The amount of train data is too small to learn anything meaningful from scratch, consider enlarging your train_processed_dialogs dataset.

Should the train_processed_dialogs.txt and val_processed_dialogs.txt contain the same dialog sets?

No, they should be different: train set is used for training your model and validation set for evaluating the performance of the trained model. These datasets should not intersect if you want to evaluate your model's performance correctly. The size of validation set can a 1k-10k examples, while train set typically has millions of examples.

What should be the contents of the context_free_validation_set.txt file?

The default contents of the files stored in data/quality folder is ok, you can leave them as is.

Unfortunately I could not get a proper understanding of what the exact functionality of val_processed_dialogs.txt and context_free_validation_set.txt files is.

val_processed_dialogs.txt – the samples are context sensitive, i.e. you need to provide samples with several consequent phrases to let your model understand the meaning of the context
context_free_validation_set.txt – the samples are context independent, i.e. you can feed only one phrase and it should be enough for a model to generate a meaningful answer

When running train.py the process always gets killed for some reason.

What machine are you using for training? Most likely your OS runs out of memory and thus sends kill signal to stop the process.

@vasiabratchuk

Would you recommend using the cloud for training?

Yes, for sure.

I'm closing this issue now. Feel free to add more comments later.


LepIndex - searching for a source returns an erroneous record at end of list

When searching for a source the last one on the returned list does not match the search criteria (and is always a Chalcid reference). See attached screenshot examples (sources_erroneous_search_return_1.jpg & sources_erroneous_search_return_2.jpg).

Sources are shared across projects, and referenced as belong to a particular project (Project Sources).  Here you are searching through all sources, so the behaviour is expected, but see #58


message log is logging input message on loglevel "Terse" should be moved to "Basic"

Describe the bug
The messages.log is needed for integrity check in production environments. By logging the input message in the "Terse" loglevel the logfiles will become to big.
by moving the logging of the input to the "Basic" loglevel this problem will be solved
To Reproduce
Steps to reproduce the behavior:

Go to a running ibis with a framwork 7.4+
Click on the log button
Scroll down to messages.log
Open and see the input message being logged

Expected behavior
The logging of the input should be logged only using the "Basic" loglevel

issue is fixed removing a fualty log message from the adapter.java


fix: update library again

:tada: This PR is included in version 1.0.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add more unit test cases for UnmodifiableArrayList

What changes are proposed in this pull request?
I added more unit test cases for UnmodifiableArrayList, including cases detecting illegal access and verifying ListIterator behaviors.
Why are the changes needed?
To better proof the correctness of the class UnmodifiableArrayList.
Does this PR introduce any user facing changes?
No.

alluxio-bot, merge this please


version 5

Codecov Report

Merging #112 (c07335a) into master (fb0d1e7) will increase coverage by 100.00%.
The diff coverage is 100.00%.

@@              Coverage Diff              @@
##           master      #112        +/-   ##
=============================================
+ Coverage        0   100.00%   +100.00%
=============================================
  Files           0         9         +9
  Lines           0       310       +310
  Branches        0        54        +54
=============================================
+ Hits            0       310       +310

Impacted Files
Coverage Δ

...le/src/lib/draggable-scroll-container.directive.ts
100.00% <ø> (ø)

projects/angular-draggable-droppable/src/test.ts
100.00% <ø> (ø)

...draggable-droppable/src/lib/draggable.directive.ts
100.00% <100.00%> (ø)

...draggable-droppable/src/lib/droppable.directive.ts
100.00% <100.00%> (ø)

.../angular-draggable-droppable/src/test-polyfills.ts
100.00% <100.00%> (ø)

...ects/angular-draggable-droppable/src/test-utils.ts
100.00% <0.00%> (ø)

...ble-droppable/src/lib/draggable-helper.provider.ts
100.00% <0.00%> (ø)

...ojects/angular-draggable-droppable/src/lib/util.ts
100.00% <0.00%> (ø)

... and 4 more

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 fb0d1e7...c07335a. Read the comment docs.


I18n for error message attributes merged from ActiveRecord

Hi guys,
I am fighting with translating error messages that come out of ActiveRecord merged by ActiveInteraction. I can't get attribute names correctly translated.
Assume I have following classes:
# app/models/user.rb
class User < ActiveRecord::Base
  validates :email, presence: true
end

# app/interactions/create_user.rb
class CreateUser < ActiveInteraction::Base
  def execute
    user = User.first         # Assume I have any users.
    user.update email: nil    # ActiveRecord will mark user invalid with errors.
    errors.merge!(user.errors) if user.errors.any?
    user
  end
end

and these translations:
# config/locales/models/user.nl.yml
nl:
  activerecord:
    attributes:
      user:
        email: E-mailadres # which I want to be used instead of some `attribute.humanize` magic.
  errors:
    messages:
      blank: moet opgegeven zijn

So when I CreateUser.run the interaction, it returns the following errors.full_messages:
["Email moet opgegeven zijn"] # Should be `["E-mailadres moet opgegeven zijn"]`

Which makes sense to developers, but not to endusers.
Question is: Is there a way to also translate those attributes?

They're translated as types within ActiveInteraction. Take a look at https://github.com/orgsync/active_interaction/blob/master/lib/active_interaction/locale/ folder for examples.
Let me know if this helps out.

So basically I can do the following?
nl:
  active_interaction:
    types:
      email: E-mailadres

Does it also mean there's is no way to translate column names which, as a result of bad software design, have the same names, but a slightly different meaning across the tables/objects? For example Person#address would translate to 'Home address' and User#address to 'Work address'.

You should be able to do:
en:
  active_interaction:
    attributes:
      person:
        address: Home address
      user:
        address: Work address

Hey @AaronLasseigne,
Unfortunately, after lot's of debugging, I figured out that ActiveInteraction doesn't really respect ActiveRecord when merging errors. The following worked for me:
nl:
  active_interaction:
    attributes:
      create_user:
        email: E-mailadres

Notice create_user which is a snake case version of my interaction's name CreateUser. This is either:
a) undocumented; or
b) a bug in ActiveInteraction::Errors#attribute? method which assumes ActiveModel::Errors's  @base instance, which is at that point CreateUser < ActiveInteraction::Base and not User < ActiveRecord::Base.

Unfortunately, after lot's of debugging, I figured out that ActiveInteraction doesn't really respect ActiveRecord when merging errors.

I'm not sure what you mean by that. Are you talking about error message translations?

Notice create_user which is a snake case version of my interaction's name CreateUser. This is either:
a) undocumented; or
b) a bug in ActiveInteraction::Errors#attribute? method which assumes ActiveModel::Errors's @base instance, which is at that point CreateUser [ActiveInteraction::Base] and not User [ActiveRecord::Base].

Using snake case for the name is standard for Rails internationalization. We don't do any form of inheritance based on the attributes being internationalized. The interaction is entirely separate from the model. When you pass a string into the interaction we can't know if that came from an existing model.

I'm going to go ahead and close this but if you have any more questions please feel free to re-open the issue.


Feature further enhancement

Implemented #34
This allows the user to, by clicking buttons, add additional columns which will display the custom fields. The fields can be set from within each person.
The column will display that persons field value, and if it is empty, it will display empty(" ").
The selection is also saved.

Looks good, merging


Allowing consumers to pass in agent in the httpMiddlewareOptions

I wasn't able to see any configuration which allowed consumers to modify the fetch agent configuration. This could help clients reduce their latency response time by reusing TCP connections.
Any thoughts on the above?
https://stackoverflow.com/questions/62500011/reuse-tcp-connection-with-node-fetch-in-node-js

The SDK allows to configure a fetch function for the http and auth middleware. See https://github.com/commercetools/commercetools-sdk-typescript/blob/5e61cc76d8a6442310adf91fdf473549af13036c/packages/sdk-client/src/sdk-middleware-http/http.ts#L89
The fetch function must implement the node-fetch API please see
https://github.com/commercetools/commercetools-sdk-typescript/blob/5e61cc76d8a6442310adf91fdf473549af13036c/packages/sdk-client/src/sdk-middleware-http/http.ts#L177
So it's possible to wrap the node-fetch as stated by the linked post

Are you able to provide an example on how I can pass an agent to the fetcher?

Didn't tried it but should look something like this:
const fetch = require('node-fetch');

const http = require('http');
const https = require('https');

const httpAgent = new http.Agent({ keepAlive: true });
const httpsAgent = new https.Agent({ keepAlive: true });
const agent = (_parsedURL) => _parsedURL.protocol == 'http:' ? httpAgent : httpsAgent;

const wrappedFetch = (url, options) => {
         wrappedOptions = {
           options,
           agent: agent
         }
         return fetch(url, options)
}

example with dynamic import of node-fetch 3.x and ts
// @ts-ignore @types not existing
import { createRequestBuilder } from '@commercetools/api-request-builder'
// @ts-ignore @types not existing
import { createClient } from '@commercetools/sdk-client-v2'
// @ts-ignore @types not existing
import { createAuthMiddlewareForClientCredentialsFlow } from '@commercetools/sdk-middleware-auth'
// @ts-ignore @types not existing
import { createHttpMiddleware } from '@commercetools/sdk-middleware-http'
import { Agent } from 'https'

const agent = new Agent({
  maxSockets: 2
})

const fetch = async (url: string, init: any) => {
  const { default: nodeFetch } = await import('node-fetch')

  return nodeFetch(url, Object.assign({}, init, { agent }))
}

// ...

    const abortController = new AbortController()

    const ctClient = createClient({
      middlewares: [
        createAuthMiddlewareForClientCredentialsFlow({
          host: authApiURL,
          projectKey,
          credentials: {
            clientId
            clientSecret
          },
          scopes: arrayOfScopes,

          fetch,
          timeout: 5000, // timeout the request if it doesn't complete in 5000ms or 5 seconds
          retryConfig: { retryOnAbort: false, maxRetries: 0 },
          abortController,
          getAbortController: () => abortController,
        }),
        createHttpMiddleware({
          host: apiUrl,
          fetch,
          timeout: 10000,
          retryConfig: { retryOnAbort: false, maxRetries: 0 },
          abortController,
        }),
      ],
    })

  return ctClient
    .execute({
      uri,
      method: 'GET',
    })
    .then((payload: any, error = undefined) => {
      if (error || payload.error) {
        throw new Error(error || payload.error)
      }

      return payload.body
    })

uri example
const getFullCategoriesData = (
  rootCategoryId: string,
  { offset, limit, lastId }: any
): Promise<any> => {
  const where = []

  if (lastId) {
    where.push('id > "' + lastId + '"')
  }

  where.push('ancestors(id = "' + rootCategoryId + '")')

  const queryArgs: any = {
    where,
    sort: [{ by: 'id', direction: 'asc' }],
    expand: ['ancestors[*]'],
    page: offset / limit + 1,
    perPage: limit,
    withTotal: false,
  }

const uri = createRequestBuilder({
    projectKey,
  }).categories.parse(queryArgs).build()

Thanks for sharing both, much appreciated 🙌 .
I had a similar solution already create, but I was wondering there was a better way of solving this, but it seems not.


add a pre-delete-hook to clean up mutatingwebhookconfigurations

Issue https://github.com/rancher/rancher/issues/33988
Cause:
When rancher-webhook is uninstalled, it will leave the resource MutatingWebhookConfiguration named rancher.cattle.io, which prevents us from re-installing Rancher into the cluster.
Fixes:
We need to fix the rancher-webhook chart such that it will delete the MutatingWebhookConfiguration when the app is uninstalled.
Pre-delete-hook is used here because

we can run a Job successfully only when either both the MutatingWebhookConfiguration  and Validatingwebhookconfigurations exist or not
and because the MutatingWebhookConfiguration is not part of the helm chart, so Helm cleans only the
Validatingwebhookconfigurations by itself
therefore, we have to use the pre-delete-hook to remove both of them before Helm starts deleting other managed resources

Note:
We have another PR in rancher/rancher for adding missing permissions for rancher's post-delete-hook to run the helm uninstall rancher-webhook command
TODO after merging:

[ ] cut a new tag
[ ] update the chart in rancher/charts
[ ] need the rancher/rancher PR to be merged

For reference, here are the output of the helm uninstall command
> helm uninstall rancher-webhook -n cattle-system --debug
uninstall.go:93: [debug] uninstall: Deleting rancher-webhook
client.go:290: [debug] Starting delete for "rancher-webhook-pre-delete" ServiceAccount
client.go:319: [debug] serviceaccounts "rancher-webhook-pre-delete" not found
client.go:128: [debug] creating 1 resource(s)
client.go:290: [debug] Starting delete for "rancher-webhook-pre-delete" ClusterRole
client.go:319: [debug] clusterroles.rbac.authorization.k8s.io "rancher-webhook-pre-delete" not found
client.go:128: [debug] creating 1 resource(s)
client.go:290: [debug] Starting delete for "rancher-webhook-pre-delete" ClusterRoleBinding
client.go:319: [debug] clusterrolebindings.rbac.authorization.k8s.io "rancher-webhook-pre-delete" not found
client.go:128: [debug] creating 1 resource(s)
client.go:290: [debug] Starting delete for "rancher-webhook-pre-delete" Job
client.go:319: [debug] jobs.batch "rancher-webhook-pre-delete" not found
client.go:128: [debug] creating 1 resource(s)
client.go:519: [debug] Watching for changes to Job rancher-webhook-pre-delete with timeout of 5m0s
client.go:547: [debug] Add/Modify event for rancher-webhook-pre-delete: ADDED
client.go:586: [debug] rancher-webhook-pre-delete: Jobs active: 0, jobs failed: 0, jobs succeeded: 0
client.go:547: [debug] Add/Modify event for rancher-webhook-pre-delete: MODIFIED
client.go:586: [debug] rancher-webhook-pre-delete: Jobs active: 1, jobs failed: 0, jobs succeeded: 0
client.go:547: [debug] Add/Modify event for rancher-webhook-pre-delete: MODIFIED
client.go:290: [debug] Starting delete for "rancher-webhook-pre-delete" ServiceAccount
client.go:290: [debug] Starting delete for "rancher-webhook-pre-delete" ClusterRole
client.go:290: [debug] Starting delete for "rancher-webhook-pre-delete" ClusterRoleBinding
client.go:290: [debug] Starting delete for "rancher-webhook-pre-delete" Job
client.go:290: [debug] Starting delete for "rancher-webhook" Service
client.go:290: [debug] Starting delete for "rancher-webhook" Deployment
client.go:290: [debug] Starting delete for "rancher-webhook" ClusterRoleBinding
client.go:290: [debug] Starting delete for "rancher-webhook" ServiceAccount
client.go:290: [debug] Starting delete for "rancher.cattle.io" ValidatingWebhookConfiguration
uninstall.go:134: [debug] purge requested for rancher-webhook
release "rancher-webhook" uninstalled


Add = None at optional parameters

Adds = None to optional values so that the following can be done:
from huggingface_hub import AutomaticSpeechRecognitionParameters

AutomaticSpeechRecognitionParameters()

without this PR, we cannot due to the following:
TypeError: __init__() missing 2 required positional arguments: 'generate' and 'return_timestamps'

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 82.96%.  Consider uploading reports for the commit 9dba3b6 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2095      +/-   ##
==========================================
+ Coverage   82.94%   82.96%   +0.02%
==========================================
  Files         102      102
  Lines        9540     9540
==========================================
+ Hits         7913     7915       +2
+ Misses       1627     1625       -2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[TOPI] Fix dtype legalize logic for CPU dot product instruction

The logic in https://github.com/apache/tvm/blob/52d6b59a39f503fe382b4d7cbac4b02f9e44aae0/python/tvm/topi/generic/conv2d.py#L480-L499 is supposed to legalize the input dtype to be able to apply target-specific intrinsics that only support one of int8 or uint8. For example, the x86 VNNI instruction only supports uint8 activation.
But the logic is incorrect (two cases are flipped) and leads to incorrect result in the following case:

The input activation is int8, and we want to use the x86 VNNI intrinsic which only supports uint8 activations.
The input activation is uint8, and we want to use the ARM sdot intrinsic which only supports int8 activations.

The first case also applies to the Hexagon vrmpy intrinsic. I found this bug while testing vrmpy conv2d on int8 input.
To test this on CI, we need to be running on a cascadelake or ARM v8.2 (with dot product support) instance. I cannot find a way to detect such cpu feature from a python script. try / catch doesn't work because the error is raised from LLVM (LLVM ERROR: Do not know how to split the result of this operator) that I don't know how to catch. So for now the test is skipped. Any suggestion on this? @areusch @driazati
cc @tkonolige @mbrookhart

To test this on CI

Could we have a short test that triggers the LLVM error that we run in a subprocess? That way we could just read the stdout of the process to get the C++ exception and detect the feature.


Make cart invisible

BkCommonLib version: 1.67-SNAPSHOT
TrainCarts version: i dunno
Spigot version: 1.8.9
Dear BergerHealer,
i have a issue about hiding a cart for players.
In my code:
for(TrainProperties tc : TrainProperties.getAll()) {
if(tc.getTrainName().contains("pirana1")) {
Kar1.rideLocation = tc.getLocation().getLocation();
if(!pr1already) {
tc.setinvisible(true);
pr1already = true;
Kar1.start(tc);
}
}
}
I want to make the train with the name pirana1 invisble but it won't work.

As you see the cart in the middle is'nt invisible.
Hope you can help me!
Danique de Jong

I could be wrong but I don't think there's a way to make non-living entities invisible.

It is possible, you could just disguise it as an chicken and make that one invisible. Really cheaty way, but is works :)

Could you explain me about the disguising. Because why is their anyway an option to vanish traincarts carts when it won't work?

You could cancel all outgoing packets about the minecart.

Tagging my friend @timmaker in this, because he is a master in disguise (pun intended)

Hmm mabe take a look at this?
https://gist.github.com/aadnk/5871793

@timmaker but if you use BKC, You should also use protocollib

There is no setInvisible(boolean) method in TrainProperties only a setInvincible(boolean). So that could be the problem.

https://bugs.mojang.com/browse/MC-118329
This will be relevant for readers


Wrong constant usage in tests

https://github.com/Anchor-Protocol/anchor-token-contracts/blob/c66a89cb986ee423ef669766a514359bab3cd605/contracts/gov/src/tests.rs#L1066
It should be: creator_env.block.height += DEFAULT_VOTING_PERIOD;
but, because values are the same:
const DEFAULT_VOTING_PERIOD: u64 = 10000u64;
const DEFAULT_TIMELOCK_PERIOD: u64 = 10000u64;

test passed. I recommend to always use unique values in constants for tests.

Thanks for bringing this up @pronvis! Fixed in the PR mentioned above :) Will close this issue when that merges

https://github.com/Anchor-Protocol/anchor-token-contracts/pull/15 merged


Added Queue.mo

FIFO queue using purely-functional, singly-linked lists.

We already have Deque, which uses the same data structure with more methods: https://github.com/dfinity/motoko-base/blob/master/src/Deque.mo

Ok thanks, I did wonder if this would still be useful, I spoke with Claudio about it a while back, deque was possibly the result.


macOS error during include

I installed xplot for the jupyter notebook as described by the README.md via conda.
On macOS 10.14.6 I got the following error when loading
#include "xplot/xfigure.hpp"
#include "xplot/xmarks.hpp"
#include "xplot/xaxes.hpp"

Error:
In file included from input_line_7:1:
In file included from /Users/.../anaconda/install/envs/data_analysis/include/xplot/xfigure.hpp:16:
In file included from /Users/.../anaconda/install/envs/data_analysis/include/xwidgets/xeither.hpp:16:
In file included from /Users/.../anaconda/install/envs/data_analysis/include/xtl/xoptional.hpp:21:
In file included from /Users/.../anaconda/install/envs/data_analysis/include/xtl/xoptional_meta.hpp:15:
/Users/.../anaconda/install/envs/data_analysis/include/xtl/xmasked_value_meta.hpp:37:40: error: no template named 'enable_if_t' in namespace 'std'; did you mean 'enable_if'?
    using disable_xmasked_value = std::enable_if_t<!is_xmasked_value<E>::value, R>;
                                  ~~~~~^~~~~~~~~~~
                                       enable_if
/Users/.../anaconda/install/envs/data_analysis/include/c++/v1/type_traits:420:63: note: 'enable_if' declared here
template <bool, class _Tp = void> struct _LIBCPP_TEMPLATE_VIS enable_if {};

How can I avoid this error?

This issue only arises for C++11, not for C++14 or C++17.

xplot depends on xwidgets which is not supported in C++11, so xplot is not supported in C++11 either.

@JohanMabille thanks for the clarification

You're welcome ;)

@JohanMabille Is using the github issue tracker for such questions okay or should they better be directed somewhere else? (mailing list, user forum, etc.)

It's fine, although you might get faster answers on gitter


fix mparticle failed deploy

Issue #, if available:
Description of changes:
Description of testing performed to validate your changes (required if pull request includes CloudFormation or source code changes):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

not required


Secretless has a test app to exercise the database handlers

Description
In this task, we will write an application that can be deployed as a container to OpenShift. We will use this application to validate:

The experience of adding Secretless with DAP to an existing application
The stability of Secretless Broker in handling database connections
The request throughput is within 20% of direct-to-DB speed

Requirements for the application

Can be deployed as a container (eg there is a Docker image)
Is reusable, so the code should be added to an existing GitHub repository or a new repository should be created
Can connect to PostgreSQL and/or MySQL
Can retrieve its database connection info from its environment, which may include address, username, and password or just address (if connecting via Secretless)
The app should support the following connection modes:

Open a connection, keep the connection open indefinitely, send regular / frequent queries, and print clear errors to stderr if the connection fails
Open multiple connections at once, add query load, and print clear errors to stderr if the connection fails
Continuously open connections and send queries, and print clear errors to stderr if the connection fails
Open a connection, send a number of queries, measure the time for each query request, and print clear query time info to stdout

Application tracking requirements
The application should track:

The direct-to-DB query time data vs the query data via Secretless
Any errors that the application logs, and the connection mode / database backend that caused that error (and any other relevant data)

Open Questions

Can the app be monitored so that we are alerted about errors reported in its logs?
Are there other connection modes that the app should support? Are the current modes well enough defined?
Are there other indicators that we need to capture and compare? Return codes? Connection properties?
Are there ways to make this pluggable, so we can drop in new connection modules for things like HTTP, SSH, etc.?

AC:

[ ] An application exists that fulfills the functionality described above
[ ] A manifest exists to deploy this application to OpenShift (without Secretless), retrieving the credentials for the database connection from Kubernetes Secrets

If possible, in addition to the above, it would be nice to have

the application track times to open & close a DB connection, with & without Secretless
compare the results of the query made through Secretless to that made without Secretless to ensure the same results come back. I'm not sure what the best result set for this would be - do we need to have a large query result? A query result with a variety of data types? Not sure exactly how this could fail if there's a bug (truncation feels more likely to me than mutation of the results, though).
if there are other values like return codes from methods or connection properties that we think might look different between the with Secretless and without Secretless modes, compare those
the ability to rotate the password during app execution to ensure Secretless keeps functioning. This might complicate the connect without Secretless portion.

Additional Open Questions

If the app does find that any db connection is dropping (either the long-term one or the short-term looping ones), what do we need to know to figure out why and fix the underlying issue?
Are there ways that Secretless could fail but continue to make new connections? If so, can we extend the app to detect these failure scenarios as well?
If we add query results comparison, is there anything we need to add to better diagnose why a results compare failed if it does happen?

Note on what the app contains relative to the epic AC:

[ ] Secretless is stable

[ ] It does not randomly drop connections while running
[ ] It can run without failure for an extended period of time (~4 days)
[ ] It can consistently open connections while running
[ ] When it fails, the pod is destroyed and rescheduled

[ ] Secretless is easy to set up, and setup takes less than 10 minutes

This assumes DAP is already deployed and configured to use the Kubernetes authenticator - that is, "Secretless Setup" is the set of steps that the developer takes in the description below

[ ] Secretless has minimal impact on connection speeds

[ ] Request throughput is within 20% of direct-to-DB speed

[ ] Secretless performs under load in a realistic environment
[ ] Secretless handles connections transparently, so that requests from the client are appropriately transmitted to the server and messages from the server are propagated back to the client


Update version error message

Update version error message to match the minimum support UCX version and provide instructions to check where UCX is being loaded from.
Ported from https://github.com/rapidsai/ucx-py/pull/1069

Thanks @madsbk for the review/approval!

/merge


Use timex to convert dates to correct timezone

This fixes the issue described in #185
The posts are being created and stored in Chicago timezone. However, when they are displayed, UTC is used. This means looking at a post created in the evening in Chicago will show a display date of the next day. This PR uses the timezone information in the inserted_at field to produce a more accurate display time.

I failed the test relating to the date in RSS feed post display. That now makes me wonder if the date displayed for RSS should be GMT (as it is now) or the same as the display date. Thoughts?

@jbranchaud I see a precedent for using GMT for an item's published date, despite what we show on the site:
http://www.rssboard.org/rss-specification#ltpubdategtSubelementOfLtitemgt


Cookie output with setCookieJar() broken in PHP8

What steps will reproduce the problem?
$curl = new Curl();
$cookieJar = tempnam(sys_get_temp_dir(), 'manni_dkb_cookie_out');
$curl->setCookieJar($cookieJar); // Write cookies to this file.
$curl->get('https://github.com');
$curl->close();
$cookies = file_get_contents($cookieJar);

What is the expected behavior?
$cookies is non-empty, like with PHP7.
What is the actual behavior?
$cookies is empty.
Why is that?
curl_init() now returns resource|false|CurlHandle, and in practice it returns \CurlHandle. But is_resource(\CurlHandle) returns false, so here php-curl-class thinks it doesn't have to close anymore.

I'll send a fix.


Issue #430 has reappeared

I have a .net core application and used bower to import adminlte version 2.3.11 (visual studios 2015).
At first i thought i was just doing something wrong, but then i noticed the example pages didn't work correctly either.
I run it and go straight to the example pages and view for example the 404.html, if you click a menu item, the whole page start to slide again on the load.
How can we get the sliding to stop and work correctly like the preview?

Do you have class hold-transition in the body?

I found the problem, I was using the latest version of JQuery which bootstrap doesn't support! Sorry about that!


Not able to prepare Train Data

Hi, Great Project! One issue I am facing is when I am running trainer.py, I can't get an option to prepare data. It's just the "start" button. I tried using the CLI also, but there, by putting >python prepare_data.py r "C:\Users\singh-93\Desktop\Application\InvoiceNet"  train_data/  I am getting "need data_dir" as an argument error.

hello
get this error too "Couldn't find any validation data! Have you prepared your training data?"

Me too.. Anyone who fix it ?


Added a normalMapping example to WebGPU Samples and Box Mesh Creation Utilities

Box Mesh utilities are ported from Threejs.

I think this project could benefit from more extensive testing. Have you considered using ABC to automate tests?

I think this project could benefit from more extensive testing. Have you considered using ABC to automate tests?

What are you referring to when you say ABC?


Spelling error

I just wanted to adjust the spelling of components
I can't visually see what the GitHub editor did/thinks I changed on the line 56 one, but I expect it's an editor based challenge that I'm not going to dig into.

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


Service requires "kick" to update active when servers return to "Active" state from "Reconnecting"

Rancher Version: 1.1.3
Docker Version: 1.12.1
OS and where are the hosts located? (cloud, bare metal, etc): AWS EC2
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB) Single node, External DB
Environment Type: (Cattle/Kubernetes/Swarm/Mesos) Cattle
Steps to Reproduce:

Start a long-running service with the scheduling policy of "Run on all hosts matching the following label" and pick a label that matches some hosts, and responds to a health check.
Sever the network connection to a host or peg its CPU to vCPU * 100%, making the agent and container with its health check unreachable. Let the health checks kill the container on the host.
Restore the network connection to a host, the IP shouldn't have changed on reconnect.

Results:
Service does not update and start a container for the service on the host. Host looks like this:

Expected:
Service should update on the newly available host.
Workaround:
I can "kick" the service into gear by manually deactivating the host, then reactivating it right away.

Reproduced the same issue in v1.2.0-pre3 now:

Service Journal for the service in question on this one:

Tested with latest build from master and using rancher/healthcheck:v0.1.0.
Had a global service with health check enabled instances.
Brought down network on one of the hosts , so that it goes to "reconnecting" state.
Health check enabled instance is found unhealthy and marked for removal.
After sometime , restore connectivity on this host.
When host state transitions to"active" , we see the health check instance start successfully on the host.
@schuylr, this fix will be available in rancher-server 1.2 release.


Transition setFrameCompletedCallback to take a CallbackHandler

setFrameCompletedCallback should use the same CallbackHandler mechanism as the rest of Filament. This is particularly useful for clients to control which thread the frame completed callback is called on.

should we do it for setFrameScheduledCallback as well?

Yes, I'll do it in a separate PR.


Openmolcas Tag Fix & MKL Support

Now that I have a running Hydra I noticed that OpenMolcas 20.10 does not build. The Molcas version hashes are not stable. v20.10 was moved to a different commit multiple times (which one does not realise if the sources are cached in the store). I fixed this by pinning to the current commit hash of the tags, as the tags of molcas are not really stable. For the current molcas 21.02 i also enabled building with MKL.

Done


Add namespace support to signalfx-agent helm chart

What this PR does / why we need it:
Add a values option to specify the namespace you want the signalfx-agent to run under.
This is particularly useful if the agent is deployed as a dependency in your master chart.
Namespace in values.yaml is optional. If its not specified, the behavior of this chart
will be the same as it is now.
Special notes for your reviewer:
Tested by deploying signalfx-agent with and without namespace option specified. Confirmed agent was working as expected.

@keitwb PTAL

/assign @lachie83

I don't think this makes sense. Why would you want this change? You can specify the namespace when you install a chart.

/assign

That is correct when you directly install this chart. However this is a monitoring agent which is defined as a dependency in my case (and perhaps many others). I dont want the monitoring agent to assume the same namespace as my global deployment and would rather be explicit about it. Note that this is an optional argument.

/ok-to-test

/lgtm


file:// instead of http://

a lot of JS scripts use something like: script.src = '//cdn.syndication.twimg.com/widgets/timelines/'
which becomes 'file://cdn.syndication.twimg.com/widgets/timelines/'
would there be a way to fix this, except hardcoding it to http or https?

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/10634688-file-instead-of-http?utm_campaign=plugin&utm_content=tracker%2F899498&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F899498&utm_medium=issues&utm_source=github).

Good point, but there would not be an easy fix. We will have to bundle a micro web server and serve the static files.


SVGO: Add plugin "reusePaths".

Find duplicated  elements and replace them with  links. (disabled by default)

This maybe should check for other styling attributes than stroke and fill — it could change rendering if one of the paths has stroke-dasharray, for example. It probably shouldn't clone paths unless the differences fall under the attributes where it's safe for the <use> to differ:

id and class
transform
Maybe some others

It also doesn't have to move the "source" <path> into a <defs> block — referencing an already-visible element with <use>  is perfectly okay.

SVGO v1.2.0 has been just released!
@tigt worth sending PR?


Adds a lobby screen by Foxei.

About the PR

Added a lobby screen for Foxei
Why / Balance

Adds a game breaking lobby screen!
Technical details

Just copied code from other lobby screens.
Media

Requirements

[X] I have read and am following the Pull Request and Changelog Guidelines.
[X] I have added media to this PR or it does not require an ingame showcase.


Extract feature toggle library from bundle

Possible competitor: https://github.com/qandidate-labs/qandidate-toggle-bundle
Downsides: It is unnecessarily complex.

Absolutely. Splitting this up into three different packages makes sense: One for the library, one for twig related stuff and one symfony specific bundle which will also contain the annotation logic for the controllers.


Create 1.9 edge and stable bundle definitions

Context
This repository should have a 1.9 bundle definition to be able to build and publish it.
What needs to get done

Add a 1.9/ directory to hold the bundle definitions for that version
Add 1.9/stable and 1.9/edge directories
Add bundle.yaml files for each risk of the 1.9 version based off the bundle definition in latest/edge

Definition of Done
There is a bundle.yaml file for 1.9/stable and 1.9/edge that can be built for releasing the CKF bundle.

Fixed by https://github.com/canonical/bundle-kubeflow/pull/999


EPIC: Upgrade Pigeons to Support Arbitrum and Optimism Mainnets

Upgrade Pigeons to support Arbitrum and Optimism L2 Blockchains.
EPIC: https://www.notion.so/volumefi/EPIC-07-14-23-Upgrade-Paloma-GETH-for-L2-Chains-Arbitrum-and-Optimism-to-confirm-Deployment-success-a3d53da980f1485bb4736fc7e556ac43

Closing as we have delivered support for Optimism. However, we'll need to update architecture for arbitrum.


GEODE-10193: Replace openhft compiler with geode-junit compiler

PROBLEM
QueryPdxDataDUnitTest compiles and loads classes using the
net.openhft.compiler library, which attempts to access a field of
Unsafe that does not exist on JDK 17.
SOLUTION
Use the compiler system from geode-junit's
org.apache.geode.test.compiler package.

This PR fixes only QueryPdxDataDUnitTest on JDK 17. Other test failures on JDK 17 are expected, and will be fixed by other PRs.

What is the story on the openjdk17 failures?

What is the story on the openjdk17 failures?

We are slowly working through those on separate PRs.


Feature: Improvement in the styling of the Home Page

Feature description
I would like to contribute to this by changing the font of the entire website and making it more eye-catching. I would like to change the navbar hover effect as an underline would be preferable to the entire hover effect. Please assign me this issue under GSSOC'23.

👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

I think this would be a very big issue can you create sub issues maybe one for hover effect, one for font @crapbagaah
So I am closing this issue, you can create sub issues so that it is easy for us to track...


[Snyk] Security upgrade org.webjars.npm:dompurify from 2.3.6 to 2.5.0

Snyk has created this PR to fix 1 vulnerabilities in the maven dependencies of this project.
Snyk changed the following file(s):

library/pom.xml

Vulnerabilities that will be fixed with an upgrade:

Issue
Score
Upgrade

Cross-site Scripting (XSS) SNYK-JAVA-ORGWEBJARSNPM-8184975
  227
org.webjars.npm:dompurify:  2.3.6 -> 2.5.0  Proof of Concept

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Cross-site Scripting (XSS)

🎉 Snyk hasn't found any issues so far.
✅ code/snyk check is completed. No issues were found. (View Details)


Fixing occasional wrong layout.

Hi and thanks for useful project, it helped me a lot!
I've found an edge case and came up with quick and dirty fix for it, any improvements are appreciated.
Sometimes contentOffset of containerView, that is used for positioning of subviews during layout, is not final and may change after contentSize change. This can happen when containerView is scrolled to bottom and some cells are deleted from tableView, that is located at the bottom. This triggers layoutSubviews during which contentOffset contains not updated value.
Here is an example project: https://github.com/imaks/OLEContainerScrollViewBug

Thanks a lot. Sorry for replying so late.


Simplify path for the loaded path in automatically retrieved graphs.

The paths currently retrieved look like this:
path = "graphs/yue/MashupPPI/yue/Mashup_PPI_labels.txt"

The name of the library is redounded.

Done!


When testing chef cookbooks that use the LWRP

The ChefSpec github page recommends providing the following for others to use when testing:
NOTE: If your cookbook exposes LWRPs, it is highly recommended you also create a       libraries/matchers.rb file as outlined below in the "Packaging Custom Matchers" section. You should never step_into an LWRP unless you are testing it. Never step_into an LWRP from another cookbook!
I'm seeing the following problem within my local cookbook that uses the tomcat cookbook when trying to leverage ChefSpec against my local cookbook:
Chef::Exceptions::InvalidDataBagPath
------------------------------------
Data bag path '/var/folders/l6/b838zky96_b9ncymw645q8kwcsd0d3/T/d20151116-48594-1hffvk7/data_bags' is invalid

/var/folders/l6/b838zky96_b9ncymw645q8kwcsd0d3/T/d20151116-48594-1hffvk7/cookbooks/tomcat/libraries/chef_tomcat_cookbook.rb:

 73>>                   data_bag = Chef::DataBag.load(USERS_DATA_BAG)

I'm relatively new to ChefSpec, would this be a result of not providing the libraries matcher?  Let me know your thoughts.  Thanks in advance.

@Z3r0Sum If you want to open a PR with the matchers I'd love to get that merged in

@tas50 Yeah, I can get that done - I just wanted to make sure that would resolve the problem and I wasn't missing anything.  I'll try and get a PR submitted that adds the matchers in.

matchers are exactly how you'd solve this problem.

Matchers have been added for the new resources


Nova v4 Compatibility

Update for Laravel Nova v4 and fix for #118, tested and working on Laravel Nova · v4.5.2
Inspired on the initial PR #117

Using the new Table Rows & Styling from Nova
Changed to Vue 3 and changed the Draggable package.

Still has an issue with overriding the default fields of Nova:
Nova's bug: Package fails to override Nova's default Vue components
Temporary Fix: https://github.com/laravel/nova-issues/issues/4143#issue-1221940614

For testing pusoses; Published this fork on marshmallow/nova-sortable with v3 tag.
Will remove the package as soon the original is fixed.

The fix on novas side was released today with the 4.6.0 update: https://nova.laravel.com/releases/4.6.0

@LTKort did you do anything special with the install?  Running Nova 4.6.  Installed the package out of dev-main.  Looks like it is not overriding the Nova table rows.  I have the model and resource setup appropriately for sorting.  I'm planning to add some debug code to the ResourceTableRow Vue component and see if i can figure out if it's even attempting to fire.

@ramcda what about v3 instead of main? If it won't work, could you check our fork marshmallow/nova-sortable
To debug the code you should check https://nova.laravel.com/docs/4.0/customization/frontend.html#vue-devtools
If there are any errors they will be reported in console.

@LTKort Working with v3.0.  Was dealing with a browser side caching issue.  Have a bit more testing to do however the component override in 4.6 is clean now.

I'm using Nova 4.8 and a ManyToMany sorting as outlined in the documentation. The interface appears to work (when dragging the alert says "Resource Successfully Reordered") but the sort_order in the database does not change. Can anyone confirm whether it should work or not?


Add instance to ResolveExpressionName to allow advanced scenerios

I know this is a breaking change, but not having any contextual information to control the resolved name is a blocker for my use case.  Any ideas on how to implement this without it being a breaking change?

Oops I didn't mean to add the broken test to this pull request. I am investigating ways to fix this test.

I'm curious what the underlying problem case is

The problem is that my normal naming convention is lower_case for json, but I also have unknown data types added to a dictionary that can be any case.

Going to delete this one and resubmit correctly


Make CGO optional + use the builder base image for non-cgo

Associated with prometheus/golang-builder#13
This PR gives the ability to crossbuild with or without CGO. Non-CGO crossbuilds will be using the golang-builer base image which only contains Golang without any crossbuild toolchains.
Non-CGO builds should be faster now given that there is only a single lighter docker image for all platforms.
The CircleCI fail because it depends on the golang-builder PR. The later must be merged and successfully builded before merging this one.

This will fix prometheus/prometheus#1769

With that change, the node_exporter will be the only one to use CGO for now. Therefore, we need to add the following config in the .promu.yml file:
build:
    cgo: true

We should also change the DOCKER_TEST_IMAGE_NAME envvar in circleci.yml file to use the base docker image instead of the main one.
machine:
    environment:
        DOCKER_TEST_IMAGE_NAME: quay.io/prometheus/golang-builder:1.6-base

Thank you @sdurrheimer! LGTM
👍

:+1: but please check that this won't break any of our official repositories. I guess due to your recent updates to remove the hardcoded go version from the .promu files, we should be good?

I will do a last check tomorrow before merging.


feat(react): Support mutiple useOnSelectionChange hook subscribers

Solves:  Support Mutiple useOnSelectionChange Hook #2980

Thanks @juspky! Because it will take some time until we publish v12, I will also add your changes to the next v11 release.

Amazing!


Added variable binding

Coverage increased (+1.0%) to 91.724% when pulling d04fdba01b872baa47428f99bc8a34734558af5a on variable-binding into b37d1b2ebd8343e500ef5863de8693ff7f5fa3b4 on master.


Travis and Galaxy not refreshed.

@jaredledvina it seems that Travis and Galaxy did not refresh with the latest release.
https://galaxy.ansible.com/sensu/sensu
https://travis-ci.org/sensu/sensu-ansible/builds

Manually kicked it! Looks like Debian timed out which probably didn't kick off Travis? Should be live now though


V2 Reconfigure modal feels cramped

Problem to solve
The bottom of the modal feels cramped between the buttons and the end of the modal in relation to other elements:

(Pink vs red)
Proposal
Increase the space between the buttons and the bottom of the modal:

More details
Add any other notes or screenshots about the feature request here.

This is likely the case for all modals it seems


Email send , but recipient didn't receive. No errors

Hi ,
Just occur this last month, previously was ok.
Email send , but recipient didn't receive.
Using valid api key, and email
No errors.
          const sgMail = require('@sendgrid/mail');
          sgMail.setApiKey('xxxxx');
          const msg = {
            to: ['b<EMAIL_ADDRESS>            from<EMAIL_ADDRESS>            subject: 'Test',
            html: '<b>Body</b>',
            attachments
          };

        sgMail.send(msg);

Have the same issue with  next data:
let msg = {             "personalizations": [                 {                     "to": [                         { "email"<EMAIL_ADDRESS>}                     ]                 }             ],             "subject": "qwe2",             "from": { "email"<EMAIL_ADDRESS>},             "template_id": "d-af55a5aeab424dd290ab8c2cd9e69d20"         };

Recommend first waiting for the response and handling any errors. Examples here: https://github.com/sendgrid/sendgrid-nodejs/blob/master/docs/use-cases/success-failure-errors.md

Recommend first waiting for the response and handling any errors. Examples here: https://github.com/sendgrid/sendgrid-nodejs/blob/master/docs/use-cases/success-failure-errors.md

I got success and in the response i have 202 status and id of the created message. but in the console I have status "not delivered". What is weird - in the field "TO" data is empty. so I suppose something with library while detecting recepient

@mishatron It's unlikely this is a library issue given that you're getting back a 202. Recommend inspecting the request body to ensure the to field is getting set properly: https://github.com/sendgrid/sendgrid-nodejs/blob/master/TROUBLESHOOTING.md#viewing-the-request-body
If it looks proper, best to reach out to support for investigation.

I saw documentation and it doesn't work for me. I use the next code to send message
let msg = {
            "personalizations": [
                {
                    "to": [
                        { "email"<EMAIL_ADDRESS>}
                    ]
                }
            ],
            "subject": "111",
            "from": { "email"<EMAIL_ADDRESS>},
            "template_id": "d-af55a5aeab424dd290ab8c2cd9e69d20"
        };
        let mail = Mail.create(msg);
        let body = mail.toJSON();
        console.log(body);
        await sgMail.send(body, (error, result) => {
            console.log(error);
            console.log(result);
            if (error) {
                res.send(error);
            } else {
                return res.status(200).send('Success')
            }
        });

And my console logs are:
{

from: EmailAddress { email<EMAIL_ADDRESS>},
subject: '111',
personalizations: [ { to: [Array] } ],
template_id: 'd-af55a5aeab424dd290ab8c2cd9e69d20'
}
null
[
Response {
statusCode: 202,
body: '',
headers: {
server: 'nginx',
date: 'Sat, 01 Aug 2020 18:51:30 GMT',
'content-length': '0',
connection: 'close',
'x-message-id': 'KrrV4QzeTtez9NVi6191_A',
'access-control-allow-origin': 'https://sendgrid.api-docs.io',
'access-control-allow-methods': 'POST',
'access-control-allow-headers': 'Authorization, Content-Type, On-behalf-of, x-sg-elas-acl',
'access-control-max-age': '600',
'x-no-cors-reason': 'https://sendgrid.com/docs/Classroom/Basics/API/cors.html'
}
},
''
]

Best to reach out to support for investigation then.

Hello @Kihoshi,
Thanks for submitting a GitHub issue! We are very sorry that you are running into this problem. In order to better serve you, as this does not present itself as a library specific issue, we would like to ask that you reach out to our support team at https://support.sendgrid.com.
Thank you!
SendGrid DX Team


Adding conf.yaml parameter command doc

What does this PR do?
In order to continue our journey of having standardized declarative integrations, one step is to have a norm for our conf.yaml files.
This norm should impact:

The parameter naming
The parameter typing
The comments layout
The placeholder norm

Motivation
This Norm needs to address two main goals:

Enhance readability of configuration files to make it easier for the users to visually decode a config file:

Documenting all parameters (name - required/optional - type - desc)
Making it more obvious when a parameter description is missing
Having a normalized way to comment params

Enable post-processing and information extraction:

Easily extracting list of parameters in each configuration file with their associated meta-data
Allowing display of those informations in other places than the conf file like in the doc/app (like we have currently for http check: https://docs.datadoghq.com/integrations/http_check/#configuration but it’s hard coded)

@masci @gzussa I updated the content in order to distinguish parameter description from parameter commands, what do you think of it?

IMHO, That's much better!

This file is getting pretty big. Let's finish this PR and split the file in another PR

and

We should split this into multiple files. But let's do so as part of another PR otherwise the review is going to be hard.

Agreed on both counts. Let's get this PR merged then we can sort out the documentation in a subsequent PR.


[Question] Is the result of algorithm in OpenCV stereo the same as the result in ZED SDK?

I want to use ZED camera to compute depth map without discrete GPU.
According to the issue, I want to get more detail about computing depth map.
Thanks.

Hi @violet17
the starting point for you is the rectify example.
Once you have the rectified images right_rect and left_rect you can directly use them with one of the OpenCV stereo matcher to obtain the disparity map:
https://docs.opencv.org/trunk/dd/d86/group__stereo.html
This is an example:
https://resources.oreilly.com/examples/9781786469717/blob/master/OpenCV3ComputerVisionApplicationProgrammingCookbookThirdEdition_Code/Chapter11/stereoMatcher.cpp#L144-173

@Myzhar   Thanks for the solution. I will have a try.

Hi @violet17
the starting point for you is the rectify example.
Once you have the rectified images right_rect and left_rect you can directly use them with one of the OpenCV stereo matcher to obtain the disparity map:
https://docs.opencv.org/trunk/dd/d86/group__stereo.html
This is an example:
https://resources.oreilly.com/examples/9781786469717/blob/master/OpenCV3ComputerVisionApplicationProgrammingCookbookThirdEdition_Code/Chapter11/stereoMatcher.cpp#L144-173

Hi @Myzhar , Can I directly compute the depth map using this formula： Z = B*f/disparity? Do I need to add some scales?
How to get the value of distance of two cameras B?


An error has occurred while uploading (Code: )

I'm getting the following error since a couple of days. This happens for different files, too.
Could the internet connection be the problem, or did you see something similar already?
2015-12-11 03:46:35 Upload of chunk 241 of '/media/hdd/backups/_250_Daten_Backups_2015-12-04.part2.rar' finished (Code: 202)
2015-12-11 03:46:35 Acquiring new access token
2015-12-11 03:46:39 Uploading chunk 242 of '/media/hdd/backups/_250_Daten_Backups_2015-12-04.part2.rar'
2015-12-11 03:46:39 Content-Length: 20971520
2015-12-11 03:46:39 Content-Range: bytes<PHONE_NUMBER>-5096079359/9000000000
2015-12-11 03:52:46 Upload of chunk 242 of '/media/hdd/backups/_250_Daten_Backups_2015-12-04.part2.rar' finished (Code: )
An error has occurred while uploading '/media/hdd/backups/_250_Daten_Backups_2015-12-04.part2.rar' (Code: )

I think, when there is no status code in the logs, the server did not respond properly.
This might have to do with your internet connection. Since the server responds only after the client has POSTed its data, any connection failure (timeout, loss of internet connection, ...) will lead to this error.
It seems as if it would be reasonable to restart any failed upload that did not return a status code (see #8).

Please update to the latest version of the script and tell me, if the problem still occurs.

I have uploaded >3000 files with a total size of more than 30 GiB without this error. There have been some chunk retries und some full retries:
2016-03-19 04:51:30 Retrying upload of chunk 2 of '/path/to/file.ext' (Previous code: )
...
2016-03-19 04:51:41 Retrying full upload of '/path/to/file.ext' (Previous code: )

but eventually the file was successfully uploaded.
Feel free to reopen the ticket, if you still encouter the error, but for now I will close this issue.


luazmq_skt_setopt_* functions make a mistake getting option_value

lua use case:
socket,err = self.ctx:socket(zmq.XREQ)
assert(socket,err)
socket:setopt_int(zmq.SNDTIMEO,1000)
but the option value 1000 doesn't work.
please have a look at the codes below,
...
{"setopt_int",     luazmq_skt_setopt_int   },
...
static int luazmq_skt_setopt_int(lua_State *L){ return luazmq_skt_set_int(L, luaL_checkint(L,2)); }
...
static int luazmq_skt_set_int (lua_State *L, int option_name) {
zsocket *skt = luazmq_getsocket(L);
int option_value = luaL_checkint(L, 2);
int ret = zmq_setsockopt(skt->skt, option_name, &option_value, sizeof(option_value));
...
}
the paramter "option_value" is just the same as "option_name", because they're the same stack 2 of lua_State, it seems definitely a bug to me.  so as the other functions,
luazmq_skt_set_i64
luazmq_skt_set_u64
luazmq_skt_set_str
the "option_value" should be the return value of "luaL_checkint(L, 3);"

This is bug, but your fix is not correct.
Need create separate function to set arbitrary option.
You can use set_sndtimeo function

@moteus  thanks


Is v2.3.0 published to npm === current master

According to npm, latest is v2.3.0.
However there is no corresponding tag or release here, and the version in package.json still indicates v2.2.0?

Fixed, missing push.


Mi-8MT PZ69/R-863 radio frequency range

Currently (Mi-8MT PZ69/R-863) the following frequency ranges can be set:
100.000 - 149.000, 220.000 - 399.000
Valid ranges:
100.000 - 149.975, 220.000 - 399.975
Any chance to change these ranges? This is not a critical issue, but it would be nice...;-).

OK check 4.4.23.

Works. Thank you.!!!


Illegal instruction error Linux

Just pulled down LillyMol 2.0 and compiled on Linux with no problems. When I try running the molecular_scaffold utility with the provided Pubchem example set I get results but also get the error message: "Illegal instruction". When I try other smiles files I just get the "Illegal instruction" error and no results. Other utilties work fine, (eg. trxn, fetch_smiles_quick, concat_files, msort). What does this error mean or indicate?
Thanks,
Greg

Hi Greg,
Could you please send me your command and result for molecular_scaffold. I will check if I can reproduce it here. Thanks
Kind Regards,
Gordon
From: gldurst<EMAIL_ADDRESS>Sent: Wednesday, November 14, 2018 11:07 PM
To: EliLillyCo/LillyMol<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [EXTERNAL] [EliLillyCo/LillyMol] Illegal instruction error Linux (#7)
EXTERNAL EMAIL: Use caution before replying, clicking links, and opening attachments.
Just pulled down LillyMol 2.0 and compiled on Linux with no problems. When I try running the molecular_scaffold utility with the provided Pubchem example set I get results but also get the error message: "Illegal instruction". When I try other smiles files I just get the "Illegal instruction" error and no results. Other utilties work fine, (eg. trxn, fetch_smiles_quick, concat_files, msort). What does this error mean or indicate?
Thanks,
Greg
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/EliLillyCo/LillyMol/issues/7, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AjtljNluQpFq5mCU6K10mP23jgWM4HQZks5uvOhpgaJpZM4YfC3U.


Grammar and Spelling Mistakes

There is a million and 1 grammar and spelling mistakes through out the site.
Find, track and fix them. Start with reporting here 1st.

@EvanGKelly
Having a look at this

Below are some pointers that may be of use to you :
There are 2 types of text content in this project

WEBSITE : text located in razor files under "Website" project folder, these are usually minor, since very visible most have been found and corrected. I believe only grammatical mistakes remain if any. These include quick guide and about page text.
Perhaps you can even add to text here to improve ease of understanding.

PREDICTION : these are text found inside Life Predictor chart, horoscope and match report page. Here we truly have many mistakes, pretty sure about that. But the best part is all text is only in 2 files, "EventDataList.xml" and "HoroscopeDataList.xml". Very easy to edit, ZERO coding knowledge needed.

once mistakes found --> make edits --> submit pull request --> changes will be live in <24h

@EvanGKelly i recommend you join our Slack, can post Q&A there if any and we appreciate your enthusiasm to help 🚀 🙏

Leverage https://devblogs.microsoft.com/visualstudio/visual-studio-spell-checker-preview-now-available/

@ByteMyst Thank you for the suggestion 🙏


Update requirements

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin Please rerender

cc @isuruf

cc @conda-forge/openmp

I think clangdev needs to be fixed before this

That's not correct. Because clangdev depends on llvmdev, we only need to fix llvmdev.


Should we rename the project?

Anchor.fm doesn't exist anymore.
Should we rename the repository to reflect the product changes?
What about calling the project:

youtube2spotify
youtube-to-spotify
youtube-to-podcast
Y2S
any other ideas?

For me Y2S is easy to use and more enabler for a new logo

@matevskial @abe-101 do you agree to change the repo name to y2s ?

I like the name actually, but lets sleep on it first.

I really like the name y2s,  simple, and easy to refer to.

Any words about this from @abe-101 ?

I like y2s
Just to state the obvious - at the top of the README we should spell it out (y2s = YouTube to Spotify)

We have a name :1st_place_medal:

I've open a pr to remove anchor.fm from the project, do we want to update the description and the repository name after the merge?

What happened with this? Can we rename it? We could sync it with the new release of the website


contrib/apiage: Provide links to go docs for APIs

fixes #592

Did you try any of the links generated? I ask because I was under the impression that preview APIs would not show up on pkg.go.dev because there's no way to indicate to pkg.go.dev what build tags you want it to use. Therefore, it would not include anything that requires the ceph_preview build tag (see #601 ).

I ask because I was under the impression that preview APIs would not show up on pkg.go.dev because there's no way to indicate to pkg.go.dev what build tags you want it to use.

That's not just your impression but a fact, easily confirmed by for example searching in the rados docs for SetLocator, which is in preview since v0.15.0.
This makes #592 a bit moot tbh, since then there will be just a few links to deprecated functions, that we don't want that people use anyway.

I ask because I was under the impression that preview APIs would not show up on pkg.go.dev because there's no way to indicate to pkg.go.dev what build tags you want it to use.

That's not just your impression but a fact, easily confirmed by for example searching in the rados docs for SetLocator, which is in preview since v0.15.0.

Correct. I should have asked first the very same question when I noticed this issue with doc generation while making the change.

This makes #592 a bit moot tbh, since then there will be just a few links to deprecated functions, that we don't want that people use anyway.

I agree.

Following the discussion on #592 , I am taking the PR out.


Test: atttributable test coverage

Refs: https://github.com/microsoft/vscode/issues/212196

[x] anyOS @aiday-mar
[ ] anyOS @Yoyokrazy

Complexity: 3
Create Issue

This month we've finalized the attributable test coverage API. To verify this, please:

Look at the API and see that it makes sense and is clear to you, the new properties are FileCoverage.includesTests and TestRunProfile. loadDetailedCoverageForTest
Try the UI and make sure the UI interactions are sensible. The selfhost test provider implements per-test coverage. Please try out the various interactions:

When per-test coverage is available, you can filter to a test in the heading in the Test Coverage view:
When filtered to a test, only files with coverage information from that test are show in the Test Coverage view, allowing you to navigate to them. Percentages are not shown in this state because they aren't meaningful.
If you don't have it on, run the Test Coverage Toolbar command to make the test coverage toolbar visible
Click on the filter action in the toolbar to filter to test coverage information in that file . Only tests in the file are filterable in that quickpick, and selecting a test will bring you to its first covered or uncovered range in the file.

Currently testing this. In the latests @types/vscode package which has version 1.95, the index.d.ts file does not contain the field includesTests. I saw that the the vscode.d.ts in our vscode repo has it, so I think the new version of the types has not been released yet.

I am not exactly sure where to find the UI part in

I ran the command Test: Open Coverage which adds an icon into the editor right toolbar. IT does not seem to add some UI element that resembles that of the image.

I am not exactly sure where to find the UI part in

That's visible in the editor once you run the Test Coverage Toolbar command

@connor4312 I'm not super clear on how to test this, I haven't been able to find the test coverage section and the command Test Coverage Toolbar doesn't seem to be registered.
Is there a step I might be missing?

You first need to "Run Test[s] with Coverage" which you can do as a context menu action in any of the points where you'd normally run them (test explorer or gutter actions)

Hi @connor4312 thank you for the response. So I see the following when a file that has coverage is open and the toolbar is visible. I don't think I see the UI element in the picture. Let me know if I need to set up something else?

The filtering is only shown when you have a file with coverage data that is run during a single test. For things in codicons those are likely run 'globally' during the require process and it may not have code executed in any given test case.
I suggest going into the Test Coverage view and filtering for a test case's coverage in there. The files in the remaining tree will be those which have individual per-test coverage, and the filter actions should be visible in those files.

Summarizing the steps here to get stuff moving:

Open microsoft/vscode and make sure it's building
Ensure that the VS Code Selfhost Test Provider extension is installed (built in this repo)

Open Testing window in your sidebar (beaker icon), and 'Run Test With Coverage'

You'll now see a 'Test Coverage' pane

Very neat feature, I hope to use it more!


Add feature extraction module

@gwaybio This is ready for review!

In general, it would be nice to see a bit more documentation in your functions and jupyter notebooks. Why did you make certain decisions, why is processing data in INSERT METHOD HERE important? What is the expected input data format?

Noted! Will put more effort into this documentation in the future!