text:
How do I remove oscillations from the frequency noise curve?

Hello！Maodong，I am using pycosh to process the frequency noise of the laser, and I found that the curve is with this oscillation at the end of the curve, from the paper I know that this is due to the non-equilibrium MZI interference. However, this oscillation does not appear in your paper, may I ask how you remove this oscillation, because the appearance of the oscillation will prevent me from calculating the laser to get the intrinsic linewidth, I look forward to your reply!

The above figure shows data processing with oscillating frequency noise, which seriously affects the computation of the intrinsic linewidth.

Your paper's graph doesn't show this oscillation.
Another small question is that in many other papers, the intrinsic linewidth is calculated by multiplying by pi, so why is this paper's calculated intrinsic linewidth multiplied by 2pi?

Hello Zhiming,
Thank you for reaching out! I am working on your request and will get back to you as soon as possible.
Maodong

Hello Zhiming,
Another thing I noticed is your PSD at low offset frequency is very high (~10^8), which made me hesitate to conclude the problem you have is purely MZI.
If possible, could you share a plot (together with a zoom-in of the plot) of your original traces on the oscilloscope; and a plot (together with a zoom-in of the plot) the phase you extracted from the traces after Hilbert transformation?
Maodong

Hello Zhiming,
Another thing I noticed is your PSD at low offset frequency is very high (~10^8), which made me hesitate to conclude the problem you have is purely MZI.
If possible, could you share a plot (together with a zoom-in of the plot) of your original traces on the oscilloscope; and a plot (together with a zoom-in of the plot) the phase you extracted from the traces after Hilbert transformation?
Maodong

Hello Maodong，
This is the data collected by my oscilloscope, I don't know how to see the phase after the Hilbert transform, if it is convenient can you provide me with your e-mail, I will send you the raw data and attach my processing code. Meanwhile, I have made a concise PPT to explain my experimental setup and processing. Thank you very much!

Here's the data from the oscilloscope.

Hello Zhiming,
Thanks for the further information! If you have some data you would like to share with me directly, please get in touch with me at maodonggao@gmail.com
Maodong

For all pycosh users:
I will publish a software package update in one or two weeks to prevent some observed unexpected behavior.
The observed unexpected behaviors are only related to python type and exception handling and some unreasonable default values. The underlining data processing codes are still correct and will NOT be changed. Therefore, if you are familiar with python and can fix some simple problems by yourself, you can keep using the package after making some small modifications.
The expecting update will only focus on the user interface to prevent similar problems in the future. Therefore, I will keep this issue open now.
Hello Zhiming,
Much appreciate for sharing your data with me over email. After reviewing the problem you mentioned, I realized some behaviors of the current package is different from when I published the package. Give me some time to fix this and I will provide you a detailed explanation on your specific case over the email.
Best regards,
Maodong

Hello Zhiming,
Thank you for reaching out! I am working on your request and will get back to you as soon as possible.
Maodong

Hi~, I have a small question, which is that in many other papers, the intrinsic linewidth is calculated by multiplying by π, so why is this paper's calculated intrinsic linewidth multiplied by 2pi?

authors: MaodongGao Nuts-sugar ZhimingShi

repo: MaodongGao/pycosh


text:
Mappings cant be generated if one of mapped entity have external dependency.

Hello,
I am facing issue that mapper cant be generated when at least one of the mapped entities have any using, so any external dependency.
We are corrently using Mapster:7.4.0-pre06 with MapsterTools:8.4.0-pre.6 due to .NET7 need. We have all the project in .NET7.
Corrently we found one workaround and that is that we need to manually copy all the required dependencies to bin folder. Then it works.
We have following error for each dependency: (replace <myDependency> with any dependency you can imagine)
  Tool 'mapster.tool' (version '8.4.0-pre06') was restored. Available commands: dotnet-mapster

  Restore was successful.
  Unhandled exception. System.IO.FileNotFoundException: Could not load file or assembly '<myDependency>, Version=2.0.1.0, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.

  File name: '<myDependency>, Version=2.0.1.0, Culture=neutral, PublicKeyToken=null'
     at System.ModuleHandle.ResolveType(QCallModule module, Int32 typeToken, IntPtr* typeInstArgs, Int32 typeInstCount, IntPtr* methodInstArgs, Int32 methodInstCount, ObjectHandleOnStack type)
     at System.ModuleHandle.ResolveTypeHandle(Int32 typeToken, RuntimeTypeHandle[] typeInstantiationContext, RuntimeTypeHandle[] methodInstantiationContext)
     at System.Reflection.RuntimeModule.ResolveType(Int32 metadataToken, Type[] genericTypeArguments, Type[] genericMethodArguments)
     at System.Reflection.CustomAttribute.FilterCustomAttributeRecord(MetadataToken caCtorToken, MetadataImport& scope, RuntimeModule decoratedModule, MetadataToken decoratedToken, RuntimeType attributeFilterType, Boolean mustBeInheritable, ListBuilder`1& derivedAttributes, RuntimeType& attributeType, IRuntimeMethodInfo& ctorWithParameters, Boolean& isVarArg)
     at System.Reflection.CustomAttribute.AddCustomAttributes(ListBuilder`1& attributes, RuntimeModule decoratedModule, Int32 decoratedMetadataToken, RuntimeType attributeFilterType, Boolean mustBeInheritable, ListBuilder`1 derivedAttributes)
     at System.Reflection.CustomAttribute.GetCustomAttributes(RuntimeType type, RuntimeType caType, Boolean inherit)
     at System.Attribute.GetCustomAttributes(MemberInfo element, Type attributeType, Boolean inherit)
     at System.Attribute.GetCustomAttribute(MemberInfo element, Type attributeType, Boolean inherit)
     at System.Reflection.CustomAttributeExtensions.GetCustomAttribute[T](MemberInfo element)
     at Mapster.Tool.Program.GenerateMappers(MapperOptions opt) in C:\Projects\Mapster\src\Mapster.Tool\Program.cs:line 71
     at CommandLine.ParserResultExtensions.WithParsed[T](ParserResult`1 result, Action`1 action)
     at Mapster.Tool.Program.Main(String[] args) in C:\Projects\Mapster\src\Mapster.Tool\Program.cs:line 18

What kind of project is this ? Class library or console application?

Hello, it is class library.

Try to add msbuild property that copies all dependencies to output folder :
<CopyLocalLockFileAssemblies>true</CopyLocalLockFileAssemblies>

Thanks, yes I confirm, that fix my issue.

I'm not sure this is what you want to do...
You MIGHT have it  as -p property  when building assembly to generate the mapping  BEFORE  building your project, but definitely NOT as property in your main project.
I would advise to give a try to 8.4.0-pre06 tool (without CopyLocalLockFileAssemblies property)

Something like this I think :
 <Exec WorkingDirectory="$(ProjectDir)" Command="dotnet build -p:CopyLocalLockFileAssemblies=true" />

source: gharchive/issue

authors: Fennixx jvmlet

repo: MapsterMapper/Mapster

license: MIT

license_type: permissive

license_source: github-api


text:
Intro to Servers (AWS, OpenStack, Digital Ocean, etc)

Intro to Servers (AWS, OpenStack, Digital Ocean, etc)

Suggestion: contact Cybera to get some free server space sponsored.

+1

+1

+1
have some experience, but interested to discuuss it

authors: albykov alukach sgnewson spinzel


text:
initial data inspection, missing data interpolation (unfinished), bas…

…eline model

I finished the interpolation (got stuck there for a while bc my fillna was filling in 0s where there should still be nans). Can update you on what i did and what were the issues i faced.
Did not do any validation bc I am struggling to figure out how since we have place x time data.

source: gharchive/pull-request

repo: MarKaplanova/ds-ml-project


text:
fix: update local dependencies specified in the workspace manifest

We've encountered issues when using release-plz at lumina. It seems like currently release-plz is capable of updating dependencies specified directly in packages' manifests and is ignoring dependencies specified on workspace level. The latter doesn't get version bumps which results in failures in resolving.
I'm not sure if there are additional things needed when updating also workspace-wide dependencies tho. Let me know wdyt

Nice catch, thanks!
I didn't even think about specifying local dependencies at the workspace level :)

authors: MarcoIeni zvolin

repo: MarcoIeni/release-plz


text:
Mark-Lauman/DominionPicker:master pull request.

Can’t automatically merge.

Got it! You have been merged.
Some notes:

I think your text editor may be replacing tab characters with spaces. All the Spanish .tsv files have no tabs inside them, making them malformed (for more on the .tsv format, look here).
app/src/main/res/values/all_locales.xml has two new fields worth noting: "debt" and "format_debt" which are used to label debt tokens (from Dominion: Empires). The rest of the new content is to accommodate the new languages.
I changed the layout of encoding.txt and added the encoding for Spanish (UTF-8).

Ok.
Thank you!

authors: Mark-Lauman kikecalpe

repo: Mark-Lauman/DominionPicker

license: mit

license_source: bigquery


text:
Add case-insensitive assertion

Currently there's no direct way of doing a case-insensitive assertion and you need to do something like Get Text    .my-element    validate    value.lower() == "some text".
Instead of "having" to use validate there could be a case-insensitive assertion something like
Get Text    .my-element   should be case-insensitive   some text    # option 1
Get Text    .my-element    ==!    some text    # option 2

There's the [https://marketsquare.github.io/robotframework-browser/Browser.html#Assertions](formatters for assertion), so this could probably be implemented as a formatter instead of a separate assertion as well.

This actually belongs to AssertionEngine project, please recreate issue in the AssertionEngine side. Nevertheless I think it is a good idea.

authors: aaltat asimell

repo: MarketSquare/robotframework-browser


text:
Linux download link is broken

OS: Ubuntu GNOME, Windows 10, Android
Issue Descriptions: The Linux download links on your site aren't working. I tried on multiple devices and networks, so there must be an issue with the site. Hope this gets fixed soon; I'm looking forward to trying this out! :)
Steps to Reproduce: Visit https://www.googleplaymusicdesktopplayer.com/#!, click "DOWNLOAD LATEST - V4.1.1", click "LINUX", click any of the four options.

Latest version broke. Download this: https://github.com/MarshallOfSound/Google-Play-Music-Desktop-Player-UNOFFICIAL-/releases/tag/v4.0.5

Do people not read the issue template?
#2118 #2117 #2103 #2124

I have checked that there are no issues with similar or the same content
YOU SHOULD CHECK CLOSED ISSUES ASWELL

^^ I mean, it's right there.... Please guys, the issue template is there so that I don't have to waste time managing duplicate issues.


text:
Main window is blank!

OS: Windows 10 Pro
Issue Descriptions: When opening the application first time in windows 10, the main window remain blank and I'm not able to do action on the screen.
Steps to Reproduce: Open the application right after that window first launching.

Sounds, like Electron crashed for some reason.  Would recommend uninstalling and reinstalling, ensure you have a network connection and if you are using a proxy or a VPN turn it off 👍

authors: MarshallOfSound lordluzbel


text:
Group#properties issue

Hello.
Recently, I noticed that the Group#properties have an issue with the .shout & .memberCount properties.
This is the code I have:
const Discord = require('discord.js');
const bloxy = require('bloxy');
const bloxyClient = new bloxy();
const groupId = '4366007';

module.exports.run = async (bot, message, args) => {
    bloxyClient.getGroup(groupId).then(group => {
        let embed = new Discord.RichEmbed()
        .setColor('BLUE')
        .setAuthor('Group Information', bot.user.displayAvatarURL)
        .addField('Group Name', group.name)
        .addField('Group ID', group.groupId)
        .addField('Membercount', group.memberCount)
        .addField('Owner', group.owner.username)
        .addField('Description', group.description)
        .addField('Current Shout', group.shout.body);
        message.channel.send(embed);
    });
}

On the Membercount & Current Shout fields, it shows:
Membercount; the membercount of approximately 1 week ago.
Current Shout: the group shout which was made 1 week ago.
In my side of view, this is an issue which should be fixed as many people may be using those properties on their bot and the bloxy source is giving incorrect information on those two properties.

The code i use works fine, So it must be just you

Thanks for the issue, it should be fixed in the new version of bloxy (v4 alpha).

authors: NodeWired Visualizememe dhBxnny

repo: MartinRBX/bloxy


text:
DeprecationWarning in 3.8

asyncio.coroutine is deprecated in python/cpython#13346 . Since 3.4 not supported maybe async def can be used? I ran pytest on CPython master and warnings as below :
========================================= warnings summary =========================================
/home/karthi/pydev-venv/lib/python3.8/site-packages/asynctest-0.13.0-py3.8.egg/asynctest/mock.py:434
  /home/karthi/pydev-venv/lib/python3.8/site-packages/asynctest-0.13.0-py3.8.egg/asynctest/mock.py:434: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead

/home/karthi/pydev-venv/lib/python3.8/site-packages/asynctest-0.13.0-py3.8.egg/asynctest/mock.py:448
  /home/karthi/pydev-venv/lib/python3.8/site-packages/asynctest-0.13.0-py3.8.egg/asynctest/mock.py:448: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead

/home/karthi/pydev-venv/lib/python3.8/site-packages/asynctest-0.13.0-py3.8.egg/asynctest/mock.py:468
  /home/karthi/pydev-venv/lib/python3.8/site-packages/asynctest-0.13.0-py3.8.egg/asynctest/mock.py:468: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead

/home/karthi/pydev-venv/lib/python3.8/site-packages/asynctest-0.13.0-py3.8.egg/asynctest/mock.py:489
  /home/karthi/pydev-venv/lib/python3.8/site-packages/asynctest-0.13.0-py3.8.egg/asynctest/mock.py:489: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead

/home/karthi/pydev-venv/lib/python3.8/site-packages/asynctest-0.13.0-py3.8.egg/asynctest/case.py:357
  /home/karthi/pydev-venv/lib/python3.8/site-packages/asynctest-0.13.0-py3.8.egg/asynctest/case.py:357: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead

/home/karthi/pydev-venv/lib/python3.8/site-packages/asynctest-0.13.0-py3.8.egg/asynctest/case.py:381
  /home/karthi/pydev-venv/lib/python3.8/site-packages/asynctest-0.13.0-py3.8.egg/asynctest/case.py:381: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead

/home/karthi/pydev-venv/lib/python3.8/site-packages/asynctest-0.13.0-py3.8.egg/asynctest/case.py:392
  /home/karthi/pydev-venv/lib/python3.8/site-packages/asynctest-0.13.0-py3.8.egg/asynctest/case.py:392: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead

/home/karthi/pydev-venv/lib/python3.8/site-packages/asynctest-0.13.0-py3.8.egg/asynctest/case.py:403
  /home/karthi/pydev-venv/lib/python3.8/site-packages/asynctest-0.13.0-py3.8.egg/asynctest/case.py:403: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead

/home/karthi/pydev-venv/lib/python3.8/site-packages/asynctest-0.13.0-py3.8.egg/asynctest/case.py:414
  /home/karthi/pydev-venv/lib/python3.8/site-packages/asynctest-0.13.0-py3.8.egg/asynctest/case.py:414: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead

/home/karthi/pydev-venv/lib/python3.8/site-packages/asynctest-0.13.0-py3.8.egg/asynctest/case.py:445
  /home/karthi/pydev-venv/lib/python3.8/site-packages/asynctest-0.13.0-py3.8.egg/asynctest/case.py:445: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead

/home/karthi/pydev-venv/lib/python3.8/site-packages/asynctest-0.13.0-py3.8.egg/asynctest/case.py:487
  /home/karthi/pydev-venv/lib/python3.8/site-packages/asynctest-0.13.0-py3.8.egg/asynctest/case.py:487: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead

/home/karthi/pydev-venv/lib/python3.8/site-packages/asynctest-0.13.0-py3.8.egg/asynctest/helpers.py:13
  /home/karthi/pydev-venv/lib/python3.8/site-packages/asynctest-0.13.0-py3.8.egg/asynctest/helpers.py:13: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead

test/test_case.py:44
  /home/karthi/asynctest/test/test_case.py:44: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def start_wait_process(loop):

test/test_case.py:58
  /home/karthi/asynctest/test/test_case.py:58: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def runTest(self):

test/test_case.py:399
  /home/karthi/asynctest/test/test_case.py:399: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def advance(self, seconds):

test/test_case.py:412
  /home/karthi/asynctest/test/test_case.py:412: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def test_advance(self):

test/test_case.py:445
  /home/karthi/asynctest/test/test_case.py:445: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def test_negative_advance(self):

test/test_case.py:451
  /home/karthi/asynctest/test/test_case.py:451: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def test_callbacks_are_called_on_time(self):

test/test_case.py:477
  /home/karthi/asynctest/test/test_case.py:477: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def test_setUp(self):

test/test_case.py:484
  /home/karthi/asynctest/test/test_case.py:484: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def setUp(self):

test/test_case.py:494
  /home/karthi/asynctest/test/test_case.py:494: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def test_setUp(self):

test/test_case.py:876
  /home/karthi/asynctest/test/test_case.py:876: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def test_assertAsyncRaises(self):

test/test_case.py:887
  /home/karthi/asynctest/test/test_case.py:887: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def test_assertAsyncRaisesRegex(self):

test/test_case.py:905
  /home/karthi/asynctest/test/test_case.py:905: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def warns(cls):

test/test_case.py:916
  /home/karthi/asynctest/test/test_case.py:916: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def test_assertAsyncWarns(self):

test/test_case.py:926
  /home/karthi/asynctest/test/test_case.py:926: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def test_assertAsyncWarnsRegex(self):

test/test_helpers.py:11
  /home/karthi/asynctest/test/test_helpers.py:11: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def wait_for(self, coro):

test/test_mock.py:19
  /home/karthi/asynctest/test/test_mock.py:19: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def a_coroutine(self):

test/test_mock.py:35
  /home/karthi/asynctest/test/test_mock.py:35: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def a_coroutine_with_args(self, arg, arg2):

test/test_mock.py:40
  /home/karthi/asynctest/test/test_mock.py:40: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def a_classmethod_coroutine(cls):

test/test_mock.py:45
  /home/karthi/asynctest/test/test_mock.py:45: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def a_staticmethod_coroutine():

test/test_mock.py:522
  /home/karthi/asynctest/test/test_mock.py:522: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def test_awaited_CoroutineMock_sets_awaited(self):

test/test_mock.py:540
  /home/karthi/asynctest/test/test_mock.py:540: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def test_awaited_CoroutineMock_counts(self):

test/test_mock.py:569
  /home/karthi/asynctest/test/test_mock.py:569: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def test_awaited_from_autospec_mock(self):

test/test_mock.py:580
  /home/karthi/asynctest/test/test_mock.py:580: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def test_awaited_wait(self):

test/test_mock.py:595
  /home/karthi/asynctest/test/test_mock.py:595: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def test_awaited_wait_next(self):

test/test_mock.py:614
  /home/karthi/asynctest/test/test_mock.py:614: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def test_await_args(self):

test/test_mock.py:632
  /home/karthi/asynctest/test/test_mock.py:632: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def test_await_args_list(self):

test/test_mock.py:650
  /home/karthi/asynctest/test/test_mock.py:650: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def test_assert_awaited(self):

test/test_mock.py:660
  /home/karthi/asynctest/test/test_mock.py:660: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def test_assert_awaited_once(self):

test/test_mock.py:674
  /home/karthi/asynctest/test/test_mock.py:674: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def test_assert_awaited_with(self):

test/test_mock.py:688
  /home/karthi/asynctest/test/test_mock.py:688: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def test_assert_awaited_once_with(self):

test/test_mock.py:702
  /home/karthi/asynctest/test/test_mock.py:702: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def test_assert_any_wait(self):

test/test_mock.py:719
  /home/karthi/asynctest/test/test_mock.py:719: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def test_assert_has_awaits(self):

test/test_mock.py:763
  /home/karthi/asynctest/test/test_mock.py:763: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def test_assert_not_awaited(self):

test/test_case.py::Test::StartWaitProcessTestCase::runTest
test/test_case.py::Test_TestCase_and_ChildWatcher::test_original_watcher_works_outside_loop
test/test_case.py::Test_TestCase_and_ChildWatcher::test_original_watcher_works_outside_loop
test/test_case.py::Test_TestCase_and_ChildWatcher::test_original_watcher_works_outside_loop
test/test_case.py::Test_TestCase_and_ChildWatcher::test_original_watcher_works_outside_loop
test/test_case.py::Test_TestCase_and_ChildWatcher::test_original_watcher_works_outside_loop
test/test_case.py::Test_TestCase_and_ChildWatcher::test_original_watcher_works_outside_loop
test/test_case.py::Test_TestCase_and_ChildWatcher::test_watched_process_is_awaited
test/test_case.py::Test_TestCase_and_ChildWatcher::test_watched_process_is_awaited
  /home/karthi/asynctest/test/test_case.py:50: DeprecationWarning: The loop argument is deprecated and scheduled for removal in Python 3.10.
    out, err = yield from asyncio.wait_for(

test/test_case.py::Test_TestCase::test_cleanup_functions_can_be_coroutines
  /home/karthi/asynctest/test/test_case.py:320: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def cleanup_coro():

test/test_case.py::Test_TestCase::test_coroutine_returned_executed
  /home/karthi/asynctest/test/test_case.py:236: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def set_ran(self):

test/test_case.py::Test_TestCase::test_coroutinefunction_executed
  /home/karthi/asynctest/test/test_case.py:213: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def runTest(self):

test/test_case.py::Test_TestCase::test_init_and_close_loop_for_test
test/test_case.py::Test_TestCase::test_init_and_close_loop_for_test
test/test_case.py::Test_TestCase::test_init_and_close_loop_for_test
test/test_case.py::Test_TestCase::test_init_and_close_loop_for_test
test/test_mock.py::Test_NonCallabableMock::test_mock_has_correct_name
test/test_mock.py::Test_NonCallabableMock::test_mock_has_correct_name
test/test_mock.py::Test_NonCallabableMock::test_mock_returns_coroutine_according_to_spec
test/test_mock.py::Test_NonCallabableMock::test_mock_returns_coroutine_according_to_spec
test/test_mock.py::Test_NonCallabableMock::test_mock_returns_coroutine_according_to_spec
test/test_mock.py::Test_NonCallabableMock::test_mock_returns_coroutine_according_to_spec
test/test_mock.py::Test_NonCallableMagicMock::test_context_manager_raise_exception_by_default
test/test_mock.py::Test_NonCallableMagicMock::test_context_manager_raise_exception_by_default
test/test_mock.py::Test_NonCallableMagicMock::test_mock_customize_async_context_manager
test/test_mock.py::Test_NonCallableMagicMock::test_mock_customize_async_context_manager
test/test_mock.py::Test_NonCallableMagicMock::test_mock_has_correct_name
test/test_mock.py::Test_NonCallableMagicMock::test_mock_has_correct_name
test/test_mock.py::Test_NonCallableMagicMock::test_mock_returns_coroutine_according_to_spec
test/test_mock.py::Test_NonCallableMagicMock::test_mock_returns_coroutine_according_to_spec
test/test_mock.py::Test_NonCallableMagicMock::test_mock_returns_coroutine_according_to_spec
test/test_mock.py::Test_NonCallableMagicMock::test_mock_returns_coroutine_according_to_spec
test/test_mock.py::Test_NonCallableMagicMock::test_mock_supports_async_context_manager
test/test_mock.py::Test_NonCallableMagicMock::test_mock_supports_async_context_manager
test/test_mock.py::Test_Mock::test_mock_has_correct_name
test/test_mock.py::Test_Mock::test_mock_has_correct_name
test/test_mock.py::Test_Mock::test_mock_returns_coroutine_according_to_spec
test/test_mock.py::Test_Mock::test_mock_returns_coroutine_according_to_spec
test/test_mock.py::Test_Mock::test_mock_returns_coroutine_according_to_spec
test/test_mock.py::Test_Mock::test_mock_returns_coroutine_according_to_spec
test/test_mock.py::Test_MagicMock::test_context_manager_raise_exception_by_default
test/test_mock.py::Test_MagicMock::test_context_manager_raise_exception_by_default
test/test_mock.py::Test_MagicMock::test_mock_customize_async_context_manager
test/test_mock.py::Test_MagicMock::test_mock_customize_async_context_manager
test/test_mock.py::Test_MagicMock::test_mock_has_correct_name
test/test_mock.py::Test_MagicMock::test_mock_has_correct_name
test/test_mock.py::Test_MagicMock::test_mock_returns_coroutine_according_to_spec
test/test_mock.py::Test_MagicMock::test_mock_returns_coroutine_according_to_spec
test/test_mock.py::Test_MagicMock::test_mock_returns_coroutine_according_to_spec
test/test_mock.py::Test_MagicMock::test_mock_returns_coroutine_according_to_spec
test/test_mock.py::Test_MagicMock::test_mock_supports_async_context_manager
test/test_mock.py::Test_MagicMock::test_mock_supports_async_context_manager
test/test_mock.py::Test_CoroutineMock::test_called_CoroutineMock_returns_MagicMock
test/test_mock.py::Test_CoroutineMock::test_exception_side_effect_raises_in_coroutine
test/test_mock.py::Test_CoroutineMock::test_mock_has_correct_name
test/test_mock.py::Test_CoroutineMock::test_mock_has_correct_name
test/test_mock.py::Test_CoroutineMock::test_mock_returns_coroutine_according_to_spec
test/test_mock.py::Test_CoroutineMock::test_mock_returns_coroutine_according_to_spec
test/test_mock.py::Test_CoroutineMock::test_mock_returns_coroutine_according_to_spec
test/test_mock.py::Test_CoroutineMock::test_mock_returns_coroutine_according_to_spec
test/test_mock.py::Test_CoroutineMock::test_returns_coroutine
test/test_mock.py::Test_CoroutineMock::test_returns_coroutine_from_return_value
test/test_mock.py::Test_CoroutineMock::test_returns_coroutine_from_side_effect
test/test_mock.py::Test_CoroutineMock::test_returns_coroutine_from_side_effect_being_a_coroutine
test/test_mock.py::Test_CoroutineMock::test_returns_coroutine_from_side_effect_being_an_iterable
test/test_mock.py::Test_CoroutineMock::test_returns_coroutine_from_side_effect_being_an_iterable
test/test_mock.py::Test_CoroutineMock::test_returns_coroutine_from_side_effect_being_an_iterable
test/test_mock.py::Test_CoroutineMock::test_returns_coroutine_with_return_value_being_a_coroutine
test/test_mock.py::Test_CoroutineMock_awaited::test_assert_any_wait
test/test_mock.py::Test_CoroutineMock_awaited::test_assert_any_wait
test/test_mock.py::Test_CoroutineMock_awaited::test_assert_any_wait
test/test_mock.py::Test_CoroutineMock_awaited::test_assert_awaited
test/test_mock.py::Test_CoroutineMock_awaited::test_assert_awaited_once
test/test_mock.py::Test_CoroutineMock_awaited::test_assert_awaited_once
test/test_mock.py::Test_CoroutineMock_awaited::test_assert_awaited_once_with
test/test_mock.py::Test_CoroutineMock_awaited::test_assert_awaited_once_with
test/test_mock.py::Test_CoroutineMock_awaited::test_assert_awaited_with
test/test_mock.py::Test_CoroutineMock_awaited::test_assert_awaited_with
test/test_mock.py::Test_CoroutineMock_awaited::test_assert_has_awaits
test/test_mock.py::Test_CoroutineMock_awaited::test_assert_has_awaits
test/test_mock.py::Test_CoroutineMock_awaited::test_assert_has_awaits
test/test_mock.py::Test_CoroutineMock_awaited::test_assert_has_awaits
test/test_mock.py::Test_CoroutineMock_awaited::test_assert_has_awaits
test/test_mock.py::Test_CoroutineMock_awaited::test_assert_has_awaits
test/test_mock.py::Test_CoroutineMock_awaited::test_assert_has_awaits
test/test_mock.py::Test_CoroutineMock_awaited::test_assert_has_awaits
test/test_mock.py::Test_CoroutineMock_awaited::test_assert_not_awaited
test/test_mock.py::Test_CoroutineMock_awaited::test_await_args
test/test_mock.py::Test_CoroutineMock_awaited::test_await_args
test/test_mock.py::Test_CoroutineMock_awaited::test_await_args
test/test_mock.py::Test_CoroutineMock_awaited::test_await_args
test/test_mock.py::Test_CoroutineMock_awaited::test_await_args_list
test/test_mock.py::Test_CoroutineMock_awaited::test_await_args_list
test/test_mock.py::Test_CoroutineMock_awaited::test_await_args_list
test/test_mock.py::Test_CoroutineMock_awaited::test_await_args_list
test/test_mock.py::Test_CoroutineMock_awaited::test_awaited_CoroutineMock_counts
test/test_mock.py::Test_CoroutineMock_awaited::test_awaited_CoroutineMock_counts
test/test_mock.py::Test_CoroutineMock_awaited::test_awaited_CoroutineMock_counts
test/test_mock.py::Test_CoroutineMock_awaited::test_awaited_CoroutineMock_counts
test/test_mock.py::Test_CoroutineMock_awaited::test_awaited_CoroutineMock_sets_awaited
test/test_mock.py::Test_CoroutineMock_awaited::test_awaited_CoroutineMock_sets_awaited
test/test_mock.py::Test_CoroutineMock_awaited::test_awaited_delays_creation_of_condition
test/test_mock.py::Test_CoroutineMock_awaited::test_awaited_from_autospec_mock
test/test_mock.py::Test_CoroutineMock_awaited::test_awaited_wait
test/test_mock.py::Test_CoroutineMock_awaited::test_awaited_wait
test/test_mock.py::Test_CoroutineMock_awaited::test_awaited_wait
test/test_mock.py::Test_CoroutineMock_awaited::test_awaited_wait
test/test_mock.py::Test_CoroutineMock_awaited::test_awaited_wait_next
test/test_mock.py::Test_CoroutineMock_awaited::test_awaited_wait_next
test/test_mock.py::Test_CoroutineMock_awaited::test_awaited_wait_next
test/test_mock.py::Test_CoroutineMock_awaited::test_awaited_wait_next
test/test_mock.py::Test_CoroutineMock_awaited::test_awaited_wait_next
test/test_mock.py::Test_CoroutineMock_awaited::test_create_autospec_on_coroutine_and_using_assert_methods
test/test_mock.py::Test_patch_autospec::test_patch_multiple_autospec
test/test_mock.py::Test_patch_autospec::test_patch_multiple_autospec
test/test_mock.py::Test_patch_autospec::test_patch_object_autospec
test/test_mock.py::Test_create_autospec::test_create_autospec_on_coroutine_with_coroutine_side_effect
test/test_mock.py::Test_create_autospec::test_create_autospec_on_coroutine_with_coroutine_side_effect
test/test_mock.py::Test_create_autospec::test_create_autospec_on_coroutine_with_exception_side_effect
test/test_mock.py::Test_create_autospec::test_create_autospec_on_coroutine_with_exception_side_effect
test/test_mock.py::Test_create_autospec::test_create_autospec_on_coroutine_with_iterable_side_effect
test/test_mock.py::Test_create_autospec::test_create_autospec_on_coroutine_with_iterable_side_effect
test/test_mock.py::Test_create_autospec::test_create_autospec_on_coroutine_with_iterable_side_effect
test/test_mock.py::Test_create_autospec::test_create_autospec_on_coroutine_with_iterable_side_effect
test/test_mock.py::Test_create_autospec::test_create_autospec_on_coroutine_with_return_value
test/test_mock.py::Test_create_autospec::test_create_autospec_on_coroutine_with_return_value
  /home/karthi/pydev-venv/lib/python3.8/site-packages/asynctest-0.13.0-py3.8.egg/asynctest/mock.py:599: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead

test/test_case.py::Test_TestCase::test_setup_teardown_may_be_coroutines
  /home/karthi/asynctest/test/test_case.py:283: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def setUp(self):

test/test_case.py::Test_fail_on_unused_loop::test_fails_when_loop_ran_only_during_cleanup
test/test_case.py::Test_fail_on_unused_loop::test_fails_when_loop_ran_only_during_cleanup
test/test_case.py::Test_fail_on_unused_loop::test_fails_when_loop_ran_only_during_cleanup
test/test_case.py::Test_fail_on_unused_loop::test_fails_when_loop_ran_only_during_cleanup
  /home/karthi/asynctest/test/test_case.py:848: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    self.addCleanup(asyncio.coroutine(lambda: None))

test/test_case.py::Test_fail_on_unused_loop::test_passes_when_ignore_loop_or_loop_run
  /home/karthi/asynctest/test/test_case.py:800: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def runTest(self):

test/test_helpers.py::TestExhaust::test_exhaust_callbacks_cascading_callbacks
test/test_helpers.py::TestExhaust::test_exhaust_callbacks_nothing_to_wait
test/test_helpers.py::TestExhaust::test_exhaust_callbacks_one_callback
  /home/karthi/asynctest/test/test_helpers.py:12: DeprecationWarning: The loop argument is deprecated and scheduled for removal in Python 3.10.
    return (yield from asyncio.wait_for(coro, loop=self.loop, timeout=1))

test/test_mock.py::Test_CoroutineMock::test_exception_side_effect_raises_in_coroutine
test/test_mock.py::Test_CoroutineMock_awaited::test_awaited_CoroutineMock_counts
test/test_mock.py::Test_create_autospec::test_create_autospec_on_coroutine_with_exception_side_effect
test/test_mock.py::Test_create_autospec::test_create_autospec_on_coroutine_with_exception_side_effect
  /home/karthi/pydev-venv/lib/python3.8/site-packages/asynctest-0.13.0-py3.8.egg/asynctest/mock.py:594: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead

test/test_mock.py::Test_CoroutineMock::test_returns_coroutine_from_side_effect_being_a_coroutine
  /home/karthi/asynctest/test/test_mock.py:176: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    mock.side_effect = asyncio.coroutine(lambda: 'ProbeValue')

test/test_mock.py::Test_CoroutineMock::test_returns_coroutine_with_return_value_being_a_coroutine
  /home/karthi/asynctest/test/test_mock.py:163: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    coroutine = asyncio.coroutine(lambda: 'ProbeValue')

test/test_mock.py::Test_CoroutineMock_awaited::test_awaited_CoroutineMock_counts
  /home/karthi/asynctest/test/test_mock.py:550: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def side_effect():

test/test_mock.py::Test_CoroutineMock_awaited::test_awaited_CoroutineMock_sets_awaited
  /home/karthi/asynctest/test/test_mock.py:531: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def side_effect():

test/test_mock.py::Test_patch::test_patch_is_enabled_when_running_decorated_coroutine
  /home/karthi/asynctest/test/test_mock.py:971: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def a_coroutine():

test/test_mock.py::Test_patch::test_patch_is_enabled_when_running_decorated_coroutine
test/test_mock.py::Test_patch_decorator_coroutine_or_generator::test_concurrent_patches_dont_affect_each_other
test/test_mock.py::Test_patch_decorator_coroutine_or_generator::test_coroutine_type_when_patched
test/test_mock.py::Test_patch_decorator_coroutine_or_generator::test_mock_on_patched_coroutine_is_a_new_mock_for_each_call
test/test_mock.py::Test_patch_object::test_patch_decorates_coroutine
test/test_mock.py::Test_patch_multiple::test_patch_decorates_coroutine
test/test_mock.py::Test_patch_dict::test_patch_decorates_class
test/test_mock.py::Test_patch_dict::test_patch_decorates_concurrent_coroutines
test/test_mock.py::Test_patch_dict::test_patch_decorates_coroutine
test/test_mock.py::Test_patch_dict_decorator_coroutine_or_generator_scope::test_patch_coroutine_with_multiple_scopes
test/test_mock.py::Test_patch_dict_decorator_coroutine_or_generator_scope::test_patch_coroutine_with_multiple_scopes
test/test_mock.py::Test_patch_and_patch_dict_scope::test_both_patch_and_patch_dict_with_scope_global
test/test_mock.py::Test_patch_and_patch_dict_scope::test_both_patch_and_patch_dict_with_scope_global
test/test_mock.py::Test_patch_decorator_coroutine_or_generator_scope_GLOBAL::test_deactivate_patch_when_generator_exec_fails
test/test_mock.py::Test_patch_decorator_coroutine_or_generator_scope_LIMITED::test_deactivate_patch_when_generator_exec_fails
test/test_mock.py::Test_patch_decorator_coroutine_or_generator_scope_LIMITED::test_patched_coroutine_with_mock_args
  /home/karthi/pydev-venv/lib/python3.8/site-packages/asynctest-0.13.0-py3.8.egg/asynctest/mock.py:1008: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead

test/test_mock.py::Test_patch_decorator_coroutine_or_generator::test_concurrent_patches_dont_affect_each_other
  /home/karthi/asynctest/test/test_mock.py:1110: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def test_patch(recursive, *_):

test/test_mock.py::Test_patch_decorator_coroutine_or_generator::test_coroutine_arg_is_default_mock
  /home/karthi/asynctest/test/test_mock.py:1043: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def tester(coroutine_function):

test/test_mock.py::Test_patch_decorator_coroutine_or_generator::test_mock_on_patched_coroutine_is_a_new_mock_for_each_call
  /home/karthi/asynctest/test/test_mock.py:1086: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def store_mock_from_patch(mock):

test/test_mock.py::Test_patch_object::test_patch_decorates_coroutine
  /home/karthi/asynctest/test/test_mock.py:1158: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def a_coroutine():

test/test_mock.py::Test_patch_multiple::test_patch_decorates_coroutine
  /home/karthi/asynctest/test/test_mock.py:1196: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def a_coroutine():

test/test_mock.py::Test_patch_dict::test_patch_decorates_class
  /home/karthi/asynctest/test/test_mock.py:1245: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def test_a_coroutine(self):

test/test_mock.py::Test_patch_dict::test_patch_decorates_concurrent_coroutines
  /home/karthi/asynctest/test/test_mock.py:1263: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def a_coroutine(recursive):

test/test_mock.py::Test_patch_dict::test_patch_decorates_coroutine
  /home/karthi/asynctest/test/test_mock.py:1217: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def a_coroutine():

test/test_mock.py::Test_patch_dict_decorator_coroutine_or_generator_scope::test_patch_coroutine_with_multiple_scopes
  /home/karthi/asynctest/test/test_mock.py:1571: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def tester_coroutine(future):

test/test_mock.py::Test_patch_dict_decorator_coroutine_or_generator_scope::test_patch_coroutine_with_multiple_scopes
  /home/karthi/asynctest/test/test_mock.py:1595: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def a_coroutine(future):

test/test_mock.py::Test_patch_dict_decorator_coroutine_or_generator_scope::test_patch_coroutine_with_multiple_scopes
  /home/karthi/asynctest/test/test_mock.py:1607: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def a_coroutine(future):

test/test_mock.py::Test_patch_and_patch_dict_scope::test_both_patch_and_patch_dict_with_scope_global
  /home/karthi/asynctest/test/test_mock.py:1655: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def a_coroutine():

test/test_mock.py::Test_patch_and_patch_dict_scope::test_both_patch_and_patch_dict_with_scope_global
  /home/karthi/asynctest/test/test_mock.py:1664: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def a_coroutine():

test/test_mock.py::Test_patch_decorator_coroutine_or_generator_scope::test_patch_coroutine_with_multiple_scopes
  /home/karthi/asynctest/test/test_mock.py:1758: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def tester(coro_function):

test/test_mock.py::Test_patch_decorator_coroutine_or_generator_scope_GLOBAL::test_deactivate_patch_when_generator_exec_fails
test/test_mock.py::Test_patch_decorator_coroutine_or_generator_scope_LIMITED::test_deactivate_patch_when_generator_exec_fails
  /home/karthi/asynctest/test/test_mock.py:1415: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def a_coroutine(missing_arg):

test/test_mock.py::Test_patch_decorator_coroutine_or_generator_scope_GLOBAL::test_deactivate_patch_when_generator_exec_fails
test/test_mock.py::Test_patch_decorator_coroutine_or_generator_scope_LIMITED::test_deactivate_patch_when_generator_exec_fails
  /home/karthi/asynctest/test/test_mock.py:1420: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def tester():

test/test_mock.py::Test_patch_decorator_coroutine_or_generator_scope_GLOBAL::test_deactivate_patch_when_generator_exec_fails
test/test_mock.py::Test_patch_decorator_coroutine_or_generator_scope_LIMITED::test_deactivate_patch_when_generator_exec_fails
  /home/karthi/asynctest/test/test_mock.py:1437: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def tester():

test/test_mock.py::Test_patch_decorator_coroutine_or_generator_scope_GLOBAL::test_multiple_patches_on_coroutine
  /home/karthi/asynctest/test/test_mock.py:1951: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def tester(coro_function):

test/test_mock.py::Test_patch_decorator_coroutine_or_generator_scope_GLOBAL::test_patch_coroutine_during_its_lifetime
  /home/karthi/asynctest/test/test_mock.py:1869: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def tester(coro_function):

test/test_mock.py::Test_patch_decorator_coroutine_or_generator_scope_LIMITED::test_multiple_patches_on_coroutine
  /home/karthi/asynctest/test/test_mock.py:2057: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def tester(coro_function):

test/test_mock.py::Test_patch_decorator_coroutine_or_generator_scope_LIMITED::test_patch_coroutine_only_when_running
  /home/karthi/asynctest/test/test_mock.py:2009: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def tester(coro_function):

test/test_mock.py::Test_patch_decorator_coroutine_or_generator_scope_LIMITED::test_patched_coroutine_with_mock_args
  /home/karthi/asynctest/test/test_mock.py:2042: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def a_coroutine(mock):

test/test_mock.py::Test_create_autospec::test_create_autospec_on_coroutine_with_coroutine_side_effect
test/test_mock.py::Test_create_autospec::test_create_autospec_on_coroutine_with_coroutine_side_effect
  /home/karthi/asynctest/test/test_mock.py:2256: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    a_coroutine, side_effect=asyncio.coroutine(lambda r: r))

Worth noting that just changing to async-def's is not enough, as this will cause your current code base to produce RuntimeWarnings.
Reason being that failing to await an asyncio.coroutine-marked function's coroutine does not produce a warning in Python3.7, but failing to await an async-def coroutine will.
Python 3.7.3 (default, Jun 24 2019, 04:54:02)
[GCC 9.1.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import asyncio
>>>
>>> @asyncio.coroutine
... def foo():
...     pass
...
>>> f = foo()
>>> del f
>>>
>>> async def bar():
...     pass
...
>>> b = bar()
>>> del b
__main__:1: RuntimeWarning: coroutine 'bar' was never awaited
RuntimeWarning: Enable tracemalloc to get the object allocation traceback

I can put a pull request up with the main changes, but specifically, we have a few failures that appear to be because of this issue. Without knowing this code base any better, I am reluctant to do something that is against how you would like this code base to be designed :-)

It's relatively easy to silence "never awaited" warnings: just add a dummy callback.
The tricky part is to understand why it was never awaited in the first place!

authors: dimaqq nekokatt tirkarthi

repo: Martiusweb/asynctest


text:
test

issueのテスト

あああ

repo: MasahiroHayashi/pyramid


text:
prevent additional properties beyond the scope of the ALF format

additionalProperties: false

Don't do it yet, it depends on the discussion in the other repo.

authors: SGrondin ahmadnassri

repo: Mashape/alf-validator


text:
request_host and request_path

Summary
I have two API end points hosted in the same host and I want to proxy them through kong. I did the following
Steps To Reproduce

curl -i -X POST
--url http://host1:8001/apis/
--data 'name=api1'
--data 'upstream_url=http://backend:8765/'
--data 'request_host=host1'

The above worked fine

curl -i -X POST
--url http://host1:8001/apis/
--data 'name=api2'
--data 'upstream_url=http://backend:8765/'
--data 'request_host=host1'

Step 3 failed because the request_host is same. It seems that either request_host or request path is mandatory. Is there a way to get around this?

Obviously that doesn't work. If a request comes in for "http://host1/some/path", then Kong looks up what api it should use. Now should it be routing to api1 or api2?
Instead of using request_host=host1 you could use request_path=/path/to/api1 and similar for api2.
Not that the request_path is basically a base path, so a path /path/to/api1/but/deeper/ will also be matched on api1.

thanks @Tieske for your response. If I dont configure the request host when I add the api, it does not work
so If I have multiple end points in the same host, depending upon the request uri, I need it to routed to api1 or api2. However it seems to me that the request_host is mandatory and does not work if I dont specify it

@Tieske @thefosk can someone please help me on this? I added two APIs without the request_host but with the request path and added an oauth2 plugin on top of one of them. After this, Im not getting the oauth2 tokens when I make the request.. All it returns is {"request_path":"/oauth2/token","message":"API not found with these values","request_host":["host"]}

@saithala you need to append /oauth2/token to whatever request_path you have specified

Thanks @thefosk . The issue I have is if I follow that approach I will need to have one Token url for each API I add to Kong. Is there a way I can have just one token URL that I can use for all APIs?
Also, how can I add Oauth2 plugin for a single API? Right now, if I add an API for which I dont need oauth2 authentication, it fails and asks for valid token. As always thanks for your support

Piggy-backing on the question, is it possible with Kong to route requests from the same host but different relative path to different proxy definitions? (e.g. handle static files differently than everything else)

@rogoman Such routing capabilities are to be added in Kong 0.10. Closing this as I believe all the questions have been answered.

authors: Tieske rogoman saithala thefosk thibaultcha

repo: Mashape/kong


text:
load balancer is abnormal when the uris=["/"]  ?

The Kong version is kong:0.10.2 and the database is postgres:9.4.
When i add the follow API,upstream,target to load balance,it has some exceptions.
First,i add the api:
POST:http://${kong_ip}:8001/apis

{

"methods": [
               "POST",
		"PUT",
		"GET",
		"DELETE"
  ],
  "upstream_url": "http://ab-web",
  "https_only": false,
  "name": "ab-web",
	"uris":["/"],
	"strip_uri":false
}

the upstream:
POST:http://${kong_ip}:8001/upstreams

{"name":"ab-web"}

and the target:
POST:http://${kong_ip}:8001/upstreams/ab-web/targets

{
	"target": "139.1.2.12:3006",
	"weight": 2
}

Now,i request the url:  http://${kong_ip}:8000 and it can proxy normally the url: http://139.1.2.12:3006(a microService)
Second,i add the api
POST:http://${kong_ip}:8001/apis

{

   "methods": [
                "POST",
		"PUT",
		"GET",
		"DELETE"
  ],
  "upstream_url": "http://ab-system",
  "https_only": false,
  "name": "ab-system",
	"uris":["/system"],
	"strip_uri":false
}

the upstream:
POST:http://${kong_ip}:8001/upstreams

{"name":"ab-system"}

and the target:
POST:http://${kong_ip}:8001/upstreams/ab-system/targets

{
	"target": "139.1.2.12:8323",
	"weight": 2
}

Now, i request the url:  http://${kong_ip}:8000/system/api/v1/users and it can't proxy normally the url: http://139.1.2.12:8323/system/api/v1/users
The second step can proxy normally sometime and  can't proxy normally sometime.
When the  apis is not include uris=["/"], the all api can proxy normally.
why?

Can you please provide some more detail about

The second step can proxy normally sometime and can't proxy normally sometime.

What do you mean "can't proxy"? Do you receive an error? A timeout? What specifically is the problem you're seeing? How often does this occur?

I guess that the "/" rule has the highest priority.
Check the order of the rules when you request the apis list.
Regards

Also @sarraz1 it sounds like this was possibly resolved with https://github.com/Mashape/kong/pull/2523. Can you try your environment with Kong 0.10.3 and let us know if you still see any issues?

sarraz1 ping :)

I will try, but not yet. For the moment, I can't update my kong environment with the 0.10.3.

Would you be able to try with the patch noted in #2523?

I was able to duplicate this behavior in 0.10.2, and not able to duplicate it with the patch noted above (or on 0.10.3). @sarraz1 let us know if you still see this behavior on 0.10.3 and we can reexamine this issue, but I believe your problem has been resolved in the latest release. Thanks!


text:
HAR format should be optional

We'd like to use this with an existing service to mock new features in the API under development, but we don't use HAR format.
It would be ideal if the WHOLE body and content type could be specified rather than just the 'content' portion.

so with minimal requirements it would look like this:
{
  "content": {
    "mimeType": "text/plain",
    "text": "Hello"
  }
}

status, and statusText, will default to 200 & OK.
Content-Type header will default to mimeType

Well our API responses typically look like:
{
    success: true,
    payload: ['array of stuff']
}

So we're hoping to have a way to directly return a body like that, with payload in the root and containing JSON. The additional HAR headers aren't the problem so much as that my body ends up nested inside 'content' as text even if I say the content type is application/json
So I was hoping there was maybe a way to either select HAR and get this format or maybe a raw where i can indicate the content type and dump a stringified JSON body
If there's some way we can help with the feature, we're not afraid to roll our sleeves up

oh ... methinks we are talking about two different things and perhaps you are using this wrong ...
after creating a bin, accessing it will give you the response body directly:
curl mockbin.org/bin/create -H "Content-Type: application/json" --data '{"status": 200,"statusText": "OK","httpVersion": "HTTP/1.1","headers": [{"name": "content-type","value": "application/json"}],"cookies": [],"content": {"mimeType": "application/json","text": "{\"success\": true, \"payload\": [\"array of stuff\"]}","size": 0},"redirectURL": "","bodySize": 0,"headersSize": 0}'

curl -v http://mockbin.com/bin/8fbdd762-3c3e-4429-8ab1-2338b594b705

result
> GET /bin/8fbdd762-3c3e-4429-8ab1-2338b594b705 HTTP/1.1
> User-Agent: curl/7.35.0
> Host: mockbin.com
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Mon, 13 Apr 2015 21:00:30 GMT
< Content-Type: application/json; charset=utf-8
< Content-Length: 48
< Connection: keep-alive
< Set-Cookie: __cfduid=df778ad7ddd1adf14c39590ccb5ade4041428958830; expires=Tue, 12-Apr-16 21:00:30 GMT; path=/; domain=.mockbin.com; HttpOnly
< Etag: W/"30-e5878040"
< Vary: Accept-Encoding
< Via: 1.1 vegur
* Server cloudflare-nginx is not blacklisted
< Server: cloudflare-nginx
< CF-RAY: 1d6a19d186810d8b-SJC
<
{"success": true, "payload": ["array of stuff"]}

I was definitely using it wrong! Okay I see it working as expected now. I was confused by the /bin/xxx/view page and thought it was my final output.
Thanks!

perhaps better documentation is needed then :)

authors: ahmadnassri bitwit

repo: Mashape/mockbin


text:
Effective borehole thermal resistance of coaxial pipe

I have a question w.r.t. the effective borehole thermal resistance of the coaxial pipe.
In my tests with pygfunction, the Rb* for a coaxial pipe seems independent from the ground thermal conductivity, where this is not the case for a single/double U-tube. I do not know whether this is a bug or it is indeed correct that the Rb* for coaxial pipes is independent from the ground thermal conductivity ...
Best regards,
Wouter Peere

For a centered coaxial pipe, the (horizontal) thermal resistance R_b is indeed independent of the ground thermal properties since the dimensionless temperature distribution in the borehole is independent of the soil.
For the effective borehole thermal resistance R_b^*, we implement the definition of Hellström (Ph.D. Thesis, 1991) which assumes a uniform borehole wall temperature :
R_b^* = R_b * eta * coth(eta)
eta = H / (C_f * V_f) * 1 / (2 * R_b) * sqrt(1 + 4 * R_b / R_12)

The value of R_b^* is then only dependent on the ground properties if the delta-circuit thermal resistances (R_b and R_12) are themselves dependent on the soil thermal properties. Note that the implementation of these equations into pygfunction is different, but equivalent.
The soil properties can still influence the borehole wall temperature profile along the borehole. In pygfunction, these effects are encapsulated into the g-function (and the calculation of the effective borehole wall temperature T_b^*) when using the Mixed inlet fluid temperatures ('MIFT') boundary condition.

authors: MassimoCimmino wouterpeere

repo: MassimoCimmino/pygfunction


text:
[Manage Race] Name and location are mandatory

Parent: #21
Name and location are mandatory.

Necesito mirar esto bien. Ahora mismo tenemos un builder de Race proporcionado por Lombok y hay que ver cómo sobreescribirlo o cómo lo haríamos.

Añadida función isValid

repo: MasterCloudApps-Projects/your-race


text:
2-DOM

Vladmaked.github.io

Класна робота. Тільки одна невеличка ремарка на майбутнє, коли пишеш використовуючи БЕМ пишеш блок, то можна не називати його page__wrapper. Достатньо просто підписати page

Класна робота. Тільки одна невеличка ремарка на майбутнє, коли пишеш використовуючи БЕМ пишеш блок, то можна не називати його page__wrapper. Достатньо просто підписати page

Дякую, також про це думав :+1:

authors: AlexKuskov Vladmaked


text:
Require conversation resolution before merging

During the PR review process conversations often become outdated as thus much less visible. I propose that we enable the "Require conversation resolution before merging" option [1] on the develop (and possibly other) branches to ensure that all comments are properly addressed.
[1] https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches#require-conversation-resolution-before-merging

Agreed, they can be hard to find. I've just enabled it, please raise any disagreements here otherwise we can close this soon.

I think there was no disagreement about this when raised at a recent discussion, so I'll close this now.

authors: ml-evs vaitkus

repo: Materials-Consortia/OPTIMADE


text:
valis requires and outdated version of pydantic through ome-types

The latest release of valis-wsi installed by pip results in ome-types==0.3.4 being installed. This in turn requires a v1-era pydantic, which is  outdated. The latest release ome-types==0.5.1.post1 supports both pydantic v1 and v2 through pydantic_compat. This is a major imporovement in compatibility of ome-types which is not yet adopted by valis-wsi.
Could you possibly update to the latest ome-types?

Hi @iRyoka,
Thanks for bringing this to my attention. I'll be sure to update the pyproject.toml and poetry.lock files to have the latest version of ome-types in the next update, which should be pretty soon.
Best,
-Chandler

Hi @iRyoka,
Just wanted to let you know the latest release of valis (1.1.0) has updated ome-types to 0.5.1.post1. I'll go ahead and close the issue, but if you run into any problems, please let me know.
Best,
-Chandler

authors: cdgatenbee iRyoka

repo: MathOnco/valis


text:
🛑 BackOffice App [CL] is down

In c244393, BackOffice App [CL] (https://backoffice.voluntariosgreenpeace.cl/) was down:

HTTP code: 502
Response time: 230 ms

Resolved: BackOffice App [CL] is back up in 168e219.


text:
Add support to virtual-hyperscript for false value in children

An error of UnexpectedVirtualElement is being thrown when using jsx-transform with the following use-case.
<div>{x > 1 && 'You have more than one item'}</div> Reference
It's being transformed to the following:
h("h1", null, [ false ])
The attached pull request would ignore any false values in addChild of virtual-hyperscript

closed via https://github.com/Matt-Esch/virtual-dom/pull/154

@Zolmeister I'm not trying to coerce the type of a boolean.
I would like false to be treated the same as null and undefined.

:+1:

:+1:

authors: Zolmeister durango kuraga otaku

repo: Matt-Esch/virtual-dom


text:
Boot and Grub menu gone

Hello Matt,
I just updated the Legacy RW on my Falco and I don't have the "boot menu" (where you can choose to boot from usb) neither the grub menu anymore.
I tested with John Lewis Legacy RW and it's there. I don't know if it's relevant but I flashed the John Lewis stock bios too.
I hope that you can fix it !
Thanks !

With my SeaBIOS builds, the prompt for the boot menu only shows if there
is >1 boot device present; if there's only 1, it boots immediately
without showing the prompt.  John's builds are completely "stock" and do
not have this behavior.  If you're not seeing the boot menu prompt with
a USB device inserted, it could be an issue with the version of SeaBIOS
I'm using, or it could be an issue with the USB device itself not
announcing within the USB-spec required time (100ms).  The Grub menu
showing or not has nothing to do with the legacy boot payload AFAIK.
On 7/4/2016 12:56 PM, Paviluf wrote:

Hello Matt,
I just updated the Legacy RW on my Falco and I don't have the "boot
menu" (where you can choose to boot from usb) neither the grub menu
anymore.
I tested with John Lewis Legacy RW and it's there. I don't know if
it's relevant but I flashed the John Lewis default bios too.
I hope that you can fix it !
Thanks !
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/MattDevo/scripts/issues/6, or mute the thread
https://github.com/notifications/unsubscribe/AA56plEG7z7VSYT6qCPU_4PYDHd2Qlroks5qSUlhgaJpZM4JEkDP.

Sorry I should have said that I'm not seeing the boot menu prompt with a USB device inserted. It worked before with the same usb stick. About the Grub menu, I can see it with John Lewis Legacy RW but not with yours.
When I boot it seem that the Chromebook stay on the "warning" image instead of displaying the boot menu or grub. It disappear only when Fedora start to boot.
Like you said, maybe there is an issue with the version of SeaBIOS you are using that don't discard the warning screen.

ok, I see the problem, there was a file missing from the build.  Go
ahead and re-run the script and it should work correctly now
On 7/4/2016 1:21 PM, Paviluf wrote:

Sorry I should have said that I'm not seeing the boot menu prompt with
a USB device inserted. It worked before with the same usb stick. About
the Grub menu, I can see it with John Lewis Legacy RW but not with yours.
When I boot it seem that the Chromebook stay on the "warning
http://www.howtogeek.com/wp-content/uploads/2015/02/ximg_54f13e9a6f60f.jpg.pagespeed.gp+jp+jw+pj+js+rj+rp+rw+ri+cp+md.ic.9D9nY51pCC.jpg"
image instead of displaying the boot menu or grub. It disappear only
when Fedora start to boot.
Like you said, maybe there is an issue with the version of SeaBIOS you
are using that don't discard the warning screen.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/MattDevo/scripts/issues/6#issuecomment-230337437,
or mute the thread
https://github.com/notifications/unsubscribe/AA56piViI9Qwnk-nrL817cSMy-gqUBQBks5qSU9AgaJpZM4JEkDP.

That works now ! That was super fast, thank you so much Matt.
Now, I will install Fedora 24 that can boot perfectly with the live usb, thanks to you that confirmed that the syslinux patch worked and because of this that is now included in Fedora. You are awesome !!!

authors: MattDevo Paviluf

repo: MattDevo/scripts

license: Unlicense


text:
Add tiers of chests

User Story
As a game designer, I'd like to have different tiers of chests, so that a player has some guarantee of the rarity/type of items that can receive from a given chest.
Acceptance Criteria

Gold, silver and bronze chest tiles are added
Gold chests only give the player high level items (Steel Armour, Amethyst/Diamond Rings, Dragon's Bane, Lich Bane)
Silver chests only give the player low level items (Leather Armour, Steel Sword, Broadsword)
Bronze chests only give potions (Health Potion, Great Health Potion)
Different tiers of chests are placed at appropriate places in appropriate levels (i.e. higher level chests in later levels)

Notes
These changes are not intended to modify the Gold/EXP given out by chests currently, but that may be an additional AC.

Why is this feature needed? Please describe the problem your requested feature wants to solve
To give the player more guarantees surrounding the items received from chests.
Describe the solution you'd like
At different points in the game, a player encounters differing tiers of chests. Each tier gives out certain items exclusive to that tier.

This will need to be adapted to account for the changes in #190.

repo: Matteas-Eden/roll-for-reaction


text:
GCM register has failed

Hi I have the same issue a few people had before, I get a PHONE_REGISTRATION_ERROR when building and running my desktop app with electron-builder. I use webpack and copy the proto files with CopyWebPackPlugin when building. It works perfectly in my dev (localhost) environment, but when i package the app with electron-builder and run it I get a "GCM register has failed" error (which is more specifically a "Error=PHONE_REGISTRATION_ERROR"). The proto files are included in the asar file and loaded successfully (I've checked putting logs in my node modules). So the problem comes from elsewhere but I can't figure it out. Would you have any ideas ?

Might not be of any use but here is a comparison of logs the requests going on both cases (my  working localhost on the left, and the non working built on the rights): http://www.mergely.com/D0yFktuh/

It's weird that it's only failing when packaged with electron-builder but it's not proto related 😕 I don't know how electron-builder works but I think that except for file paths everything should work the same

We found the cause and a workaround, I'll post an issue/PR in push-receiver because that's where the bug comes from.

authors: MatthieuLemoine tom-s

repo: MatthieuLemoine/electron-push-receiver


text:
SDE: Fix production environment settings.

Please fill in the sections below, adding/removing information where applicable:
Description
The new sde endpoint environment settings were missed from the production configuration, which is preventing the production build from completing successfully. The sde end point needs to be copied into the production build.

Code has been merged.

repo: MauroDataMapper/mdm-explorer


text:
Fix trimValueWhitespaces removing needed white-spaces

Hello everyone!
I found that the logic for trimming white-spaces (trimValueWhitespaces) may inadvertently remove white-spaces from inside the string value of the element, if XMLParser reports the content of a single element as multiple strings.
This happens for example with non-ascii characters like German umlauts:
Lösen is split up and reported separately as L and ösen.
Or where we have "mixed" strings, e.g. containing a segment of Japanese or Chinese characters:
Japanese 日本語 is split into Japanese and  日本語.
If there's a white-space adjacent to the split, as in the Japanese example above, the white-space gets trimmed before it's joined together. Resulting in Japanese日本語 without a space in the middle.
I added failing tests with the first commit.

see also: https://stackoverflow.com/a/1076951/2064473

The parser object may send the delegate several parser:foundCharacters: messages to report the characters of an element. Because string may be only part of the total character content for the current element, you should append it to the current accumulation of characters until the element changes.

@wooj2 Since you've introduced this in the first place, WDYT about this change?

Thank you for having a look, @MaxDesiatov .
I have an idea for a patch, but will wait on @wooj2 to weigh in before I spend time on it.

I added a possible fix which seems to be not to intrusive.
It seems like a commit in #92 caused the change and added process(string:) in parser(_:foundCharacters:).
I kept it there for the relevant check for emptiness only and moved the actual trimming into parser(_:didEndElement:namespaceURI:qualifiedName:) where it's sure that no further strings will be appended.
Tests are passing, but please let me know if you can think of possible regressions.

Thank you for having a look, @MaxDesiatov .
I have an idea for a patch, but will wait on @wooj2 to weigh in before I spend time on it.

Sorry for the delay.  There was some confusion around trimValueWhitespaces in that I was mistakenly identified as the one who introduced this flag.  That is not the case :).
If I understand the problem correctly, it seems that in the case of "Stilles Örtchen", parser(XMLParser, foundCharacters:) is getting called once w/ the value of "Stilles " and subsequently with "Örtchen".  When trimValueWhitespaces is set to true, the XMLParser delegate incorrectly strips out the space between s and Ö.
Looking at your approach for a fix, I think applying trimValueWhitespaces to the value of the element after the entire element's value has been parsed(parser(XMLParser, didEndElement:...)) is elegant, and seems to make sense.  The only comment that I would have is maybe adding a test case for the nested case.  E.g.:
private let deCharacterXMLNested = """
<si><t xml:space="preserve">\(deCharacterString)</t></si>
""".data(using: .utf8)!

...snip...

    func testNonStandardCharactersNested() throws {
        let decoder = XMLDecoder()
        decoder.trimValueWhitespaces = true

        let resultGerman = try XMLDecoder().decode(Item.self, from: deCharacterXMLNested)

        XCTAssertEqual(resultGerman.text, deCharacterString)
    }

I'll defer to @MaxDesiatov for the final approval and/or any other comments.

Sorry for the confusion @wooj2!
Thank you for having a look at my solution and especially for suggesting the additional tests.
I think I don't fully understand the XML specification for whitespace preservation, yet, so I highly appreciate it!
I went ahead and added the tests. I hope that's OK.

If I may, I have another slightly different question about whitespaces in XML.
(I can open a new issue if that makes more sense.)
In http://www.xmlplease.com/xml/xmlspace/ under 3. Whitespace only text nodes it says that something like
<root xml:space="preserve">
    <test> This is     great. </test>
</root>

would have the consecutive spaces between "is" and "great" (...) be reduced to just one space character. like in normal HTML parsing. This doesn't seem to be the case for the current implementation of XMLCoder.
I.e. a test as below
private let multipleSpacesBetween = "A      word"
private let multipleSpacesBetweenXML = """
<t>\(multipleSpacesBetween)</t>
""".data(using: .utf8)!

...snip...

    func testMultipleSpacesBetween() throws {
        let decoder = XMLDecoder(trimValueWhitespaces: true)

        let resultJapanese = try decoder.decode(String.self, from: multipleSpacesBetweenXML)

        XCTAssertEqual(resultJapanese, "A word")
    }

produces XCTAssertEqual failed: ("A      word") is not equal to ("A word").
I'm sorry if I've missed something, but could you tell me if that is the way it should be or might this warrant a fix?
Best regards,
Martin

Sorry, I'm a bit confused about XCTAssertEqual failed: ("A word") is not equal to ("A word"). Does this make any sense to you? These strings seem to be equal to each other at a first glance. Am I missing something? Is the comparison flawed, or is there some other whitespace character there that makes these strings not equal to each other?

I'm sorry! I did not realize that GitHub's markdown parser processes whitespace differently for code in single-backticks than for three-backticks. So, the single-backtick version reduces consecutive whitespaces into one, just like normal HTML (which is ironically just what I was asking about and the documentation I linked is about).
I edited it to use three-backticks, so the error message displays correctly now.
XCTAssertEqual failed: ("A      word") is not equal to ("A word")

Stuff like this related to the actual low level parsing of XML is a question about Foundation's XMLParser behavior. We only provide helpers on top of it.
I wonder how with this caveat in the standard one is supposed to encode or decode any strings with multiple spaces in them? The fact that multiple whitespaces aren't currently collapsed into one is either a happy accident or a deliberate decision made by Foundation authors. Either way, if that's not directly related to this PR, it does make sense to open a separate issue or PR for that.

That makes a lot of sense. Thank you for the explanation!🙂
Since it's the underlying parser's behavior this is working as intended.
Thank you for taking the time to answer this and sorry for the excursion.

No problem at all, thanks for digging into all of these details! Very illuminating and super helpful 🙂

BTW, is there still anything to do within the scope of this PR? Or is it fully ready for review now?

From my perspective it's complete.
Please let me know if you think there's something missing.

Thank-you for raising and fixing this, @MartinP7r.
I found that this was affecting text containing &. For example, "one & two" would be parsed into the string one&two. I love investigating a problem, and then finding that someone else has already fixed it! ❤

Thanks for letting me know this is a widespread problem. I'll tag 0.13.1 with this fix soon.

@mflint, thank you for your kind words! It's very rewarding to hear that this is helpful to others 😃
Also, thank you for bringing up your use case. It might not be entirely necessary, but since XML entities like &, < or > are somewhat special, I opened a PR adding another test.

repo: MaxDesiatov/XMLCoder


text:
How to reconstruct/data recover the dataset after FADM transform? (inverse_transform like)

Hi! I've started using Prince package in order to apply a FADM in my binary and categorical dataset (btw, thanks @MaxHalford for this amazing library!!!).
Now I'm trying to find a way to reconstruct my original dataset (something like the inverse_transform function of sklearn PCA), so I could check which points are in each cluster. But I could not find a way to do this, neither a function that gives me the original indexes.
Any ideas?
Thankss!!

Hey there,
Your request is a good one. I'll make a note and try to get it done soon.
Cheers.

Hey @MaxHalford, any news about implementing this nice feature ?
Thanks :) !

I just implemented inverse_transform for the PCA class. I'm not exactly sure about how to go about this for CA, MCA and FAMD but I'm making steady progress. Feel free to contribute!

Hi there @MaxHalford, will there be any updates on this? If not can you give some rough guidance on how to proceed with inverse transforming the data?

Hey there! Actually I took a look and I have no idea on how to do this for FAMD, sorry :(. Actually I'm pretty sure you could write a scientific paper if you found a way haha.

authors: MaxHalford Melkaz frazerng pollyannagoncalves-hotmart

repo: MaxHalford/prince


text:
🛑 TrueSafe App API is down

In e6df09a, TrueSafe App API ($STATUS_APP_API) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TrueSafe App API is back up in 3137295 after 6 minutes.


text:
Added factory pattern

Added factory pattern to instantiate enemy

Critical. merging....


text:
Fix NotSerializableException caused by Writers

StringWriter and PrintWriter are not Serializable, so factor the relevant code out into a NonCPS function.

Pre-patch test run
Post-patch test run

@paul-elliott-arm Could you try logging in on https://ci.staging.trustedfirmware.org/ and trying the links again?
It seems to log me out every so often (maybe every time the jenkins instance is restarted?)

repo: Mbed-TLS/mbedtls-test


text:
feature: Add another obsidian.nvim workaround to README.md

Is your feature request related to a problem? Please describe.
I enjoy using markdown.nvim. However, I do find it a little bit more heavyweight than the built in ui to obsidian.nvim. The ideal solution would be to use both. If only there were a way to do that.... so I made one!
return {
  "MeanderingProgrammer/markdown.nvim",
  main = "render-markdown",
  name = "render-markdown", -- Only needed if you have another plugin named markdown.nvim
  cmd = { "RenderMarkdown" },
  -- dependencies = { 'nvim-treesitter/nvim-treesitter', 'echasnovski/mini.nvim' }, -- if you use the mini.nvim suite
  -- dependencies = { 'nvim-treesitter/nvim-treesitter', 'echasnovski/mini.icons' }, -- if you use standalone mini plugins
  dependencies = { "nvim-treesitter/nvim-treesitter", "nvim-tree/nvim-web-devicons" }, -- if you prefer nvim-web-devicons
  config = function()
    local client = require("obsidian").get_client()
    client.opts.ui.enable = false
    local namespaceID = vim.api.nvim_get_namespaces()["ObsidianUI"]
    vim.api.nvim_buf_clear_namespace(0,namespaceID,0,-1) -- Clear all the obsidian UI stuff before loading this.
    require("render-markdown").setup({})
  end
}

Running the changes made to config after the plugin loads turns off the obsidian ui and clears it, then enables markdown.nvim! Loading is triggered by running the command RenderMarkdown.
Describe the solution you'd like
Simply add my code to the obsidian.nvim section of README.md. I'd be happy to submit a PR myself if you'd like!
Describe alternatives you've considered
I have considered using only markdown.nvim, but I didn't editing in it as much as I liked reading in it as a sort of preview. This solution allows me to have my cake and eat it too, and I was thinking other people would like to see it. Up to you!
Additional information
No response

Sure added: https://github.com/MeanderingProgrammer/markdown.nvim?tab=readme-ov-file#obsidiannvim
Definitely a use at your own risk kind of thing, but more options are always good.
Thanks!

authors: MeanderingProgrammer pachungulo


text:
Add visualization for 2d and 3d rotations

Currently there is no way to visualize a lone rotation. This could be useful for viewing raw IMU data.

You can already view a single 2D rotation on the swerve tab, but otherwise I agree that this would be a useful addition.

authors: jwbonner rzblue

repo: Mechanical-Advantage/AdvantageScope


text:
Support Auth0 style Oauth2 flow.

As an external developer, I'd like to authenticate against the MediaMath APIs using the SDK with the latest authorization standard, so I have a lot of time to migrate to a new system before Cookie Auth gets turned off.

Support Oauth2-Resource Owner Flow

Client Credentials and Authorization Grant flow aren't technically necessary for this as it's unlikely that our services will use the SDKs (Client Credentials) or the SDKs will be used for web services (Authorization Code grant).
https://connect2id.com/products/nimbus-jose-jwt might be a good place to start.
Production: https://sso.mediamath.auth0.com/
Development: https://sso.mediamath-dev.auth0.com/
https://auth0.com/docs/api-auth/grant/password
https://auth0.com/docs/api-auth/tutorials/password-grant

Added support for Auth0 style Oauth2 flow, so closing this issue.

authors: fsargent karthik-mediamath


text:
🛑 MediaNext is down

In 65660e4, MediaNext (https://the-bot.thein321.repl.co) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MediaNext is back up in ec7adc1.

repo: MediaPlay-Discord/status


text:
避免手动设置python解释器路径

detail | 详细描述
根据当前python环境自动寻找python lib路径，避免手动设置路径

issue 是提问题用的...别闹。

authors: Easonzero tpoisonooo

repo: MegEngine/MegFlow


text:
how work this? WTF OMG

I FOUND THIS SERVER OGAR PROGRAM OMG HOW WORK THIS ? you can test the server and client on my agar http://ogar.pw/agar5 LOL

wtf

i can give the direct download link if you want


text:
getting mAP=0 after every epoch in training

When digging in the code i found that calculating map use XML attribute called 'difficult' -in the VOC file.  I have it 'unspecified' that gave me error while converting and i handled it while converting. But while training, I found mAP use this attribute -difficult-.
The question here why using this attribute and how to avoid that issue?

"difficult" in VOC means "ignore" in COCO.

seem that the .txt from your dataset havnt been read

Thanks all, I replaced its value with 0

authors: FateScript hassannassar01 improgress

repo: Megvii-BaseDetection/YOLOX


text:
Training of experiment is done and the best AP is 0.00

This is the training command I use,
python tools/train.py
-f exps/example/custom/nano-hagrid4k_one_quarter.py
-d 0
-b 64
--fp16
-o
-c yolox_nano.pth
During training, such as the following log,
2022-03-28 08:00:47 | INFO     | yolox.core.trainer:252 - epoch: 14/300, iter: 460/2043, mem: 10089Mb, iter_time: 8.669s, data_time: 8.448s, total_loss: 0.0, iou_loss: 0.0, l1_loss: 0.0, conf_loss: 0.0, cls_loss: 0.0, lr: 9.980e-03, size: 608, ETA: 55 days, 11:49:53
2022-03-28 08:01:55 | INFO     | yolox.core.trainer:252 - epoch: 14/300, iter: 470/2043, mem: 10089Mb, iter_time: 6.826s, data_time: 6.610s, total_loss: 0.0, iou_loss: 0.0, l1_loss: 0.0, conf_loss: 0.0, cls_loss: 0.0, lr: 9.980e-03, size: 608, ETA: 55 days, 11:43:37
2022-03-28 08:03:29 | INFO     | yolox.core.trainer:252 - epoch: 14/300, iter: 480/2043, mem: 10089Mb, iter_time: 9.435s, data_time: 9.261s, total_loss: 0.0, iou_loss: 0.0, l1_loss: 0.0, conf_loss: 0.0, cls_loss: 0.0, lr: 9.980e-03, size: 480, ETA: 55 days, 11:46:47
2022-03-28 08:04:34 | INFO     | yolox.core.trainer:252 - epoch: 14/300, iter: 490/2043, mem: 10089Mb, iter_time: 6.462s, data_time: 6.331s, total_loss: 0.0, iou_loss: 0.0, l1_loss: 0.0, conf_loss: 0.0, cls_loss: 0.0, lr: 9.980e-03, size: 384, ETA: 55 days, 11:39:12
2022-03-28 08:06:13 | INFO     | yolox.core.trainer:252 - epoch: 14/300, iter: 500/2043, mem: 10089Mb, iter_time: 9.919s, data_time: 9.702s, total_loss: 0.0, iou_loss: 0.0, l1_loss: 0.0, conf_loss: 0.0, cls_loss: 0.0, lr: 9.980e-03, size: 576, ETA: 55 days, 11:44:06
2022-03-28 08:07:24 | INFO     | yolox.core.trainer:252 - epoch: 14/300, iter: 510/2043, mem: 10089Mb, iter_time: 7.051s, data_time: 6.810s, total_loss: 0.0, iou_loss: 0.0, l1_loss: 0.0, conf_loss: 0.0, cls_loss: 0.0, lr: 9.980e-03, size: 640, ETA: 55 days, 11:38:39
^C2022-03-28 08:07:59 | INFO     | yolox.core.trainer:194 - Training of experiment is done and the best AP is 0.00
Why is this so?
Where is the model I trained? I can't find it.

had you solve this problem

hello,had you solve this problem？

hello, have you solved the problem?
I used the official tutorial training hint, but it says AP is zero too.
!python tools/train.py -n yolox-s -d 1 -b 16 --fp16 -o --cache -c /content/yolox_s.pth

i use my data with yolox_s,it's successful,the environment is python3.8 pytorch1.11+cuda11.2  and install follow the official documentation step by step
------------------ 原始邮件 ------------------
发件人:                                                                                "Megvii-BaseDetection/YOLOX"                                                                                @.>;
发送时间: 2022年5月16日(星期一) 晚上8:10
@.>;
@.@.>;
主题: Re: [Megvii-BaseDetection/YOLOX] Training of experiment is done and the best AP is 0.00 (Issue #1199)
hello, have you solved the problem?
I used the official tutorial training hint, but it says AP is zero too.
!python tools/train.py -n yolox-s -d 1 -b 16 --fp16 -o --cache -c /content/yolox_s.pth
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

any news on this? I have AP=0 for all metrics in eval.

If you change your batchsize, please check your learning rate carefully. Issues of unproducble performance are often caused by wrong learning rate.

I have faced the exact same issue, also changing to -b 64


text:
Error: _aureliaPal.DOM.createElement is not a function

This is the first time I am using this tool. I think it is going to be very useful. I hope at some point if you could integrate with tools like Visual Studio Code (intellisense, linting etc), it will enhance the utility many times more.
Unfortunately on my first attempt, I encountered following error. I am using latest version of aurelia and latest version of the lint. Not sure what I am doing wrong, any help will be appreciated.
[14:03:18] Using gulpfile C:\Test\gulpfile.js
[14:03:18] Starting 'au-lint'...
[14:03:18] 'au-lint' errored after 14 ms
[14:03:18] Error: Error invoking SVGAnalyzer. Check the inner error for details.
Inner Error:
Message: _aureliaPal.DOM.createElement is not a function
Inner Error Stack:
TypeError: _aureliaPal.DOM.createElement is not a function
at createElement (C:\Test\node_modules\gulp-aurelia-template-lint\node_modules\aurelia-template-lint\node_modules\aurelia-binding\dist\commonjs\aurelia-binding.js:4431:29)
at new SVGAnalyzer (C:\Test\node_modules\gulp-aurelia-template-lint\node_modules\aurelia-template-lint\node_modules\aurelia-binding\dist\commonjs\aurelia-binding.js:4440:9)
at Object.invoke (C:\Test\node_modules\gulp-aurelia-template-lint\node_modules\aurelia-template-lint\node_modules\aurelia-dependency-injection\dist\commonjs\aurelia-dependency-injection.js:415:12)
at InvocationHandler.invoke (C:\Test\node_modules\gulp-aurelia-template-lint\node_modules\aurelia-template-lint\node_modules\aurelia-dependency-injection\dist\commonjs\aurelia-dependency-injection.js:392:166)
at Container.invoke (C:\Test\node_modules\gulp-aurelia-template-lint\node_modules\aurelia-template-lint\node_modules\aurelia-dependency-injection\dist\commonjs\aurelia-dependency-injection.js:654:23)
at StrategyResolver.get (C:\Test\node_modules\gulp-aurelia-template-lint\node_modules\aurelia-template-lint\node_modules\aurelia-dependency-injection\dist\commonjs\aurelia-dependency-injection.js:133:35)
at Container.get (C:\Test\node_modules\gulp-aurelia-template-lint\node_modules\aurelia-template-lint\node_modules\aurelia-dependency-injection\dist\commonjs\aurelia-dependency-injection.js:585:39)
at Object.invoke (C:\Test\node_modules\gulp-aurelia-template-lint\node_modules\aurelia-template-lint\node_modules\aurelia-dependency-injection\dist\commonjs\aurelia-dependency-injection.js:445:103)
at InvocationHandler.invoke (C:\Test\node_modules\gulp-aurelia-template-lint\node_modules\aurelia-template-lint\node_modules\aurelia-dependency-injection\dist\commonjs\aurelia-dependency-injection.js:392:166)
at Container.invoke (C:\Test\node_modules\gulp-aurelia-template-lint\node_modules\aurelia-template-lint\node_modules\aurelia-dependency-injection\dist\commonjs\aurelia-dependency-injection.js:654:23)
at StrategyResolver.get (C:\Test\node_modules\gulp-aurelia-template-lint\node_modules\aurelia-template-lint\node_modules\aurelia-dependency-injection\dist\commonjs\aurelia-dependency-injection.js:133:35)
at Container.get (C:\Test\node_modules\gulp-aurelia-template-lint\node_modules\aurelia-template-lint\node_modules\aurelia-dependency-injection\dist\commonjs\aurelia-dependency-injection.js:585:39)
at Object.invoke (C:\Test\node_modules\gulp-aurelia-template-lint\node_modules\aurelia-template-lint\node_modules\aurelia-dependency-injection\dist\commonjs\aurelia-dependency-injection.js:439:55)
at InvocationHandler.invoke (C:\Test\node_modules\gulp-aurelia-template-lint\node_modules\aurelia-template-lint\node_modules\aurelia-dependency-injection\dist\commonjs\aurelia-dependency-injection.js:392:166)
at Container.invoke (C:\Test\node_modules\gulp-aurelia-template-lint\node_modules\aurelia-template-lint\node_modules\aurelia-dependency-injection\dist\commonjs\aurelia-dependency-injection.js:654:23)
at StrategyResolver.get (C:\Test\node_modules\gulp-aurelia-template-lint\node_modules\aurelia-template-lint\node_modules\aurelia-dependency-injection\dist\commonjs\aurelia-dependency-injection.js:133:35)
End Inner Error Stack
at new AggregateError (C:\Test\node_modules\gulp-aurelia-template-lint\node_modules\aurelia-template-lint\node_modules\aurelia-dependency-injection\node_modules\aurelia-pal\dist\commonjs\aurelia-pal.js:36:11)
at Container.invoke (C:\Test\node_modules\gulp-aurelia-template-lint\node_modules\aurelia-template-lint\node_modules\aurelia-dependency-injection\dist\commonjs\aurelia-dependency-injection.js:656:13)
at StrategyResolver.get (C:\Test\node_modules\gulp-aurelia-template-lint\node_modules\aurelia-template-lint\node_modules\aurelia-dependency-injection\dist\commonjs\aurelia-dependency-injection.js:133:35)
at Container.get (C:\Test\node_modules\gulp-aurelia-template-lint\node_modules\aurelia-template-lint\node_modules\aurelia-dependency-injection\dist\commonjs\aurelia-dependency-injection.js:585:39)
at Object.invoke (C:\Test\node_modules\gulp-aurelia-template-lint\node_modules\aurelia-template-lint\node_modules\aurelia-dependency-injection\dist\commonjs\aurelia-dependency-injection.js:445:103)
at InvocationHandler.invoke (C:\Test\node_modules\gulp-aurelia-template-lint\node_modules\aurelia-template-lint\node_modules\aurelia-dependency-injection\dist\commonjs\aurelia-dependency-injection.js:392:166)
at Container.invoke (C:\Test\node_modules\gulp-aurelia-template-lint\node_modules\aurelia-template-lint\node_modules\aurelia-dependency-injection\dist\commonjs\aurelia-dependency-injection.js:654:23)
at StrategyResolver.get (C:\Test\node_modules\gulp-aurelia-template-lint\node_modules\aurelia-template-lint\node_modules\aurelia-dependency-injection\dist\commonjs\aurelia-dependency-injection.js:133:35)
at Container.get (C:\Test\node_modules\gulp-aurelia-template-lint\node_modules\aurelia-template-lint\node_modules\aurelia-dependency-injection\dist\commonjs\aurelia-dependency-injection.js:585:39)
at Object.invoke (C:\Test\node_modules\gulp-aurelia-template-lint\node_modules\aurelia-template-lint\node_modules\aurelia-dependency-injection\dist\commonjs\aurelia-dependency-injection.js:439:55)
at InvocationHandler.invoke (C:\Test\node_modules\gulp-aurelia-template-lint\node_modules\aurelia-template-lint\node_modules\aurelia-dependency-injection\dist\commonjs\aurelia-dependency-injection.js:392:166)
at Container.invoke (C:\Test\node_modules\gulp-aurelia-template-lint\node_modules\aurelia-template-lint\node_modules\aurelia-dependency-injection\dist\commonjs\aurelia-dependency-injection.js:654:23)
at StrategyResolver.get (C:\Test\node_modules\gulp-aurelia-template-lint\node_modules\aurelia-template-lint\node_modules\aurelia-dependency-injection\dist\commonjs\aurelia-dependency-injection.js:133:35)
at Container.get (C:\Test\node_modules\gulp-aurelia-template-lint\node_modules\aurelia-template-lint\node_modules\aurelia-dependency-injection\dist\commonjs\aurelia-dependency-injection.js:585:39)
at SyntaxRule.ASTBuilder (C:\Test\node_modules\gulp-aurelia-template-lint\node_modules\aurelia-template-lint\dist\ast.js:11:47)
at SyntaxRule (C:\Test\node_modules\gulp-aurelia-template-lint\node_modules\aurelia-template-lint\dist\rules\syntax.js:12:14)

C:\Test>

looks like its not loaded pal-nodejs I will upgrade everything to use the actual 1.0.0 release. I think everything is still on the RC.

I've pushed 0.9 for gulp-aurelia-template-lint and aurelia-template-lint; this should bump all dependencies to aurelia ^1.0.0 apart from that I think you will need node >= 5 and npm >= 3 and it should be good.

Thanks @MeirionHughes. I did not pay attention that node >= 5 is required. After I did that and upgraded to latest version it seems to be working fine.
I did notice one thing though. lint provides a warning that "WARNING: replaceable attribute is obsolete". However I think that replaceable was taken out in RC but added back in RTM. So it should not come up as warning. please confirm.

oh was it? odd I thought they replaced it with slot. I will ask
You can reconfigure the options for that btw: https://github.com/MeirionHughes/aurelia-template-lint#usage
oh was it? odd I thought they replaced it with slot. I will ask
You can reconfigure the options for that btw: https://github.com/MeirionHughes/aurelia-template-lint#usage
Still very much alpha, quite a lot of the static type checking is a bit hairy, getting there slowly; if you notice something you think is wrong feel free to raise an issue here
Closing this as you solved your problem. :)

Thanks @MeirionHughes. I did see some issue. Opening new ticket.


text:
v-else 元素上绑定事件失效

v-else 元素上绑定事件失效
问题复现步骤:

line 1

line 2

[其他步骤...]

期望的表现:
foo2 正常使用
观察到的表现:
foo2 失效，查看编译后的代码发现没有 foo2

同 #18 请升级 mpvue, mpvue-template-compiler, mpvue-loader 这三个依赖

authors: GaryChangCN anchengjian

repo: Meituan-Dianping/mpvue


text:
如何优雅的封装vue组件

现在看了几个mpvue的ui框架，大多数引用很麻烦，能不能实现类似正常的vue ui框架一样使用，只需import组件，component增加依赖即可

和 vue 的组件差别不大吧，现有的 ui 库可能是因为对 slot 支持不够好，所以封装的相对简单


text:
ci: Wait 2 minutes to start second tests attempt instead of 1 hour

Currently it's waiting a whole hour to start

@edgarrmondragon I guess the test failure above sort of confirms that we need more than 2 min wait time between CI attempts. The 1h wait time was added to ensure github rate limits are reset (their limits are N reqs/hour). We've been agonising over this, but haven't really figured out the solution.
The best option is probably making request caching work, but we haven't managed to do this. See https://github.com/MeltanoLabs/tap-github/pull/60 and #169

authors: edgarrmondragon laurentS

repo: MeltanoLabs/tap-github


text:
update some code for Xcode 8.3

update some code for latest Xcode 8.3
remove minor build code warnings
thank you.

Merged, thanks!

authors: MengTo puyanlin

repo: MengTo/Spring


text:
Ensemble ingestation with read operator

Improves the read operator so it can read from multiple files, and correctly tag ensemble data with a realization coordinate.
Still to do:

[x] Add tests of new functionality
[x] Add documentation of new functionality
[x] Allow more generic templating for where the ensemble number is in the name? Depends if this is different for partners. We'll leave this for now as it is basically impossible to know all the naming conventions until partners actually use it, and its an easy thing to change.

Fixes #133

I think this PR is ready to merge, but I've sort of forgotten what is in it over the past two weeks, and want to refamiliarise myself with it first.

I've had a look back over and rebased this PR, so with your approval @jwarner8 it is ready to merge.

repo: MetOffice/CSET