Meetings: Exclude Service Council meetings

Metro's Service Councils will be using the Metro Board Granicus iteration to host meetings in May. We'll need to exclude them from showing up on boardagendas.metro.net, by next week - Wednesday at the latest We'd need to exclude these meetings on Councilmatic before we add the meetings in Legistar next week.
The BodyTypeId is 70, as shown below.
[
{
"BodyId": 256,
"BodyGuid": "4D7B1130-DEDA-4B0D-9970-F99351773016",
"BodyLastModifiedUtc": "2020-04-22T23:37:29.973",
"BodyRowVersion": "AAAAAAEddx0=",
"BodyName": "San Fernando Valley Service Council",
"BodyTypeId": 70,
"BodyTypeName": "Service Council",
"BodyMeetFlag": 1,
"BodyActiveFlag": 1,
"BodySort": 999,
"BodyDescription": "",
"BodyContactNameId": 1862,
"BodyContactFullName": "Dolores Ramos",
"BodyContactPhone": "",
"BodyContactEmail"<EMAIL_ADDRESS>"BodyUsedControlFlag": 0,
"BodyNumberOfMembers": 0,
"BodyUsedActingFlag": 0,
"BodyUsedTargetFlag": 0,
"BodyUsedSponsorFlag": 0
},
{
"BodyId": 257,
"BodyGuid": "64F0C0D0-C14D-49D8-9E2B-DCC9CCA60BE0",
"BodyLastModifiedUtc": "2020-04-22T23:38:30.693",
"BodyRowVersion": "AAAAAAEddy8=",
"BodyName": "South Bay Service Council",
"BodyTypeId": 70,
"BodyTypeName": "Service Council",
"BodyMeetFlag": 1,
"BodyActiveFlag": 1,
"BodySort": 999,
"BodyDescription": "",
"BodyContactNameId": 1862,
"BodyContactFullName": "Dolores Ramos",
"BodyContactPhone": "",
"BodyContactEmail"<EMAIL_ADDRESS>"BodyUsedControlFlag": 0,
"BodyNumberOfMembers": 0,
"BodyUsedActingFlag": 0,
"BodyUsedTargetFlag": 0,
"BodyUsedSponsorFlag": 0
},
{
"BodyId": 258,
"BodyGuid": "9F2F2315-99FB-4E4E-9A9D-4A90191D4CF8",
"BodyLastModifiedUtc": "2020-04-22T23:38:57.883",
"BodyRowVersion": "AAAAAAEdd1M=",
"BodyName": "San Gabriel Valley Service Council",
"BodyTypeId": 70,
"BodyTypeName": "Service Council",
"BodyMeetFlag": 1,
"BodyActiveFlag": 1,
"BodySort": 999,
"BodyDescription": "",
"BodyContactNameId": 1862,
"BodyContactFullName": "Dolores Ramos",
"BodyContactPhone": "",
"BodyContactEmail"<EMAIL_ADDRESS>"BodyUsedControlFlag": 0,
"BodyNumberOfMembers": 0,
"BodyUsedActingFlag": 0,
"BodyUsedTargetFlag": 0,
"BodyUsedSponsorFlag": 0
},
{
"BodyId": 259,
"BodyGuid": "70FE89EC-7783-4C05-8D26-1C7A41720205",
"BodyLastModifiedUtc": "2020-04-22T23:39:24.29",
"BodyRowVersion": "AAAAAAEdd1w=",
"BodyName": "Westside/Central Service Council",
"BodyTypeId": 70,
"BodyTypeName": "Service Council",
"BodyMeetFlag": 1,
"BodyActiveFlag": 1,
"BodySort": 999,
"BodyDescription": "",
"BodyContactNameId": 1862,
"BodyContactFullName": "Dolores Ramos",
"BodyContactPhone": "",
"BodyContactEmail"<EMAIL_ADDRESS>"BodyUsedControlFlag": 0,
"BodyNumberOfMembers": 0,
"BodyUsedActingFlag": 0,
"BodyUsedTargetFlag": 0,
"BodyUsedSponsorFlag": 0
},
{
"BodyId": 260,
"BodyGuid": "B82A843F-8254-439D-B108-F7BC3531292F",
"BodyLastModifiedUtc": "2020-04-22T23:39:59.18",
"BodyRowVersion": "AAAAAAEdd0o=",
"BodyName": "Gateway Cities Service Council",
"BodyTypeId": 70,
"BodyTypeName": "Service Council",
"BodyMeetFlag": 1,
"BodyActiveFlag": 1,
"BodySort": 999,
"BodyDescription": "",
"BodyContactNameId": 1862,
"BodyContactFullName": "Dolores Ramos",
"BodyContactPhone": "",
"BodyContactEmail"<EMAIL_ADDRESS>"BodyUsedControlFlag": 0,
"BodyNumberOfMembers": 0,
"BodyUsedActingFlag": 0,
"BodyUsedTargetFlag": 0,
"BodyUsedSponsorFlag": 0
}
]

We only scrape committees and the taxpayer oversight committee, so the ccouncil itself should not be scraped for display on the committees page. I'll look into whether we need to omit these explicitly from the event scrape.

@shrayshray We made a change to the scraper that should skip service council meetings. Let us know if one gets through, otherwise we can consider this done.

Looks like these were successfully omitted!

@hancush it looks like a Service Council Meeting got through - "Service Councils - Meet and Confer" (about 25 of them ... looks like user error). Is the scraper excluding based on "BodyName", or "BodyTypeName" / "BodyTypeID"?
"BodyTypeName "= "Service Council" or "BodyTypeID" = 70 would exclude all non-Public Hearing Service Council meetings, including including "Service Councils - Meet and Confer"
{
    "BodyId": 274,
    "BodyGuid": "91EC6980-4B13-4C1C-AB5B-E9AF9EFD5567",
    "BodyLastModifiedUtc": "2020-07-15T20:12:05.34",
    "BodyRowVersion": "AAAAAAEm9YI=",
    "BodyName": "Service Councils - Meet and Confer",
    "BodyTypeId": 70,
    "BodyTypeName": "Service Council",
    "BodyMeetFlag": 1,
    "BodyActiveFlag": 1,
    "BodySort": 999,
    "BodyDescription": "",
    "BodyContactNameId": 1862,
    "BodyContactFullName": "Dolores Ramos",
    "BodyContactPhone": "",
    "BodyContactEmail"<EMAIL_ADDRESS>    "BodyUsedControlFlag": 0,
    "BodyNumberOfMembers": 0,
    "BodyUsedActingFlag": 0,
    "BodyUsedTargetFlag": 0,
    "BodyUsedSponsorFlag": 0
}

@shrayshray We are using EventBodyName to exclude meetings, specifically we are omitting meetings where the EventBodyName ends with "Service Council" or "Service Council Public Hearing". These don't fit the pattern, so they got through. Would it be safe to omit all meetings where the EventBodyName contains "Service Council"?

I don't think we can 100% guarantee the name will always contain "Service Council". And while it's unlikely, we also can't guarantee a new Board Committee won't be given a name containing "Service Council". Since "BodyTypeName " or "BodyTypeID" are fields we do have control over, since they're created in Legistar, would it be possible to use one of them instead?
Would it be possible to use "BodyTypeName " or "BodyTypeID" instead?
so, exclude
"BodyTypeName "= "Service Council" and "BodyTypeName "= "Service Council Public Hearing"
or
"BodyTypeID" = 70 and "BodyTypeID" = 75

ID would be the best...

From: shrayshray<EMAIL_ADDRESS>Sent: Thursday, July 16, 2020 1:14 PM
To: datamade/la-metro-councilmatic<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: Re: [datamade/la-metro-councilmatic] Meetings: Exclude Service Council meetings (#606)
I don't think we can 100% guarantee the name will always contain "Service Council". And while it's unlikely, we also can't guarantee a new Board Committee won't be given a name containing "Service Council". Since "BodyTypeName " or "BodyTypeID" are fields we do have control over, since they're created in Legistar, would it be possible to use one of them instead?
Would it be possible to use "BodyTypeName " or "BodyTypeID" instead?
so, exclude
"BodyTypeName "= "Service Council" and "BodyTypeName "= "Service Council Public Hearing"
or
"BodyTypeID" = 70 and "BodyTypeID" = 75
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://gcc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdatamade%2Fla-metro-councilmatic%2Fissues%2F606%23issuecomment-659646817&data=02|01|camachoo%40metro.net|74880b0ff0614873a5f508d829c4ea85|ab57129bdbfd4cacaa77fc74c40364af|0|0|637305273012791380&sdata=TGA1sXx0UFViZiaLECBpR%2Bbjgy0ySNSFBxhgg5jDS%2BI%3D&reserved=0, or unsubscribehttps://gcc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAG3PL6VFOQFS3WX5BZWUHLTR35NUFANCNFSM4MOUN5LA&data=02|01|camachoo%40metro.net|74880b0ff0614873a5f508d829c4ea85|ab57129bdbfd4cacaa77fc74c40364af|0|0|637305273012791380&sdata=wF82m3R2NLWzP%2F2DJYipCXjDylQ7BI9Fe6d%2ByTYAXyQ%3D&reserved=0.

I agree that ID would be best. We use the events endpoint in the Legistar API to scrape meetings. Let me see if I can figure out a way to query it that allows us to exclude meetings of certain types of bodies. (@shrayshray, @camachoo – If either one of you has ideas on that, happy for your input. Will update this thread with what I find out.)

Update: This turned out to be a lot easier than I thought! Will publish the change today.

I deployed a change to the scraper to omit meetings of bodies of the "Service Council" (70) or "Service Council Public Hearing" (75) type. I also removed the meetings that got through yesterday from the live site. Look ok?

@hancush yes! You're the best, thank you!

Never a problem!


Create .gitattributes

Trying to run this from my windows laptop and this is a first step. Obviously its going to need WSL or docker to happen, but at the very least I need the bash files changes with the proper line endings.

Thanks!


Possibility to extend Sparklis

Bonjour Sébastien Ferré,
First of all, thanks for this amazing tool!
I am interested to in using Sparklis for my research work and I am curious if there is a possibility to extend and modify the interface of Sparklis?
Is there anything in the pipeline to make it more user-friendly? Or if you could share how this can be done.
Can you please share how to implement templates? and what are the possibilities to do that?
Thank you very much
Regards
Maheen

Bonjour Maheen-Bakhtyar,
there is a JS API for extending and customizing Sparklis.
Have a look at https://github.com/sebferre/sparklis/blob/master/doc/main.md .
Keep in mind that this JS API is under progress, feedback welcome.
Regards

Bonjour,
Thank you for letting me know about this.
I am hopeful it will be helpful for my work.
Regards

Bonjour Sébastien Ferré,
I looked at the documentation https://github.com/sebferre/sparklis/blob/master/doc/main.md that you provided.
It gives a detail of all the functions that we can use.
It would be really helpful if you could also provide one basic example of how we can use it.
I searched on the Internet but was unable to find an example as a starting point.
It will be really helpful to go further if there is one example, please.
Can you please help me and provide a simple example of how I can use a JS API in my code?
Merci Beaucoup

Sorry, I don't yet have proper examples of use of the API.

No problem.
Let me share one soon :-)
Merci

@sebferre : Does Sparklis JS API (mentioned above) allow us to add a new menu item to the horizontal menu that is used for switching between Sparklis, YASGUI and History views?

This ability would be useful, for example, for showing a visualization of the generated SPARQL query.
P.S. Thank you for this great application!

@CaptSolo : yes, this is possible.

Duplicate and adapt the HTML code in osparklis.html for e.g. the YASGUI view (look for yasgui-view). There are two components: the button and the div containing the view.
Use the function sparklis_extension.hookSparql from the JS API to define some behavior when a new SPARQL query is defined, e.g. filling the new view with a graphical representation of the query.

Hope this helps.


SAP How-to's: Changes identified when following the instructions

Looks good @MarkvanMents. Only needed to change "SAP Cloud platform" to "SAP Cloud Platform" based on SAP's style guide.

Hi @MarkvanMents. There was a broken link in this PR: "(howto/security/create-a-secure-app)" needed to be "(../security/create-a-secure-app)", because "security" is only a sub-folder in the same main folder as "Use the SAP XSUAA Connector." When sending a PR, please try to make sure there will be no merge conflicts by checking the continuous-integration/travis-ci-pr build log at the bottom (click Details to see the test results if necessary, and you can see any errors in the log). Thanks.

Sorry, Adam.
Is there a way to test this when I’m editing locally?
Is there some documentation on using travis-ci-pr, I can’t remember whether we covered it in our meetings?
Perhaps you can go through this at our meeting tomorrow as I have obviously missed something important?
Mark
From: Adam Dupaski<EMAIL_ADDRESS>Sent: 13 February 2018 09:38
To: mendix/docs<EMAIL_ADDRESS>Cc: Mark van Ments<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [mendix/docs] SAP How-to's: Changes identified when following the instructions (#988)
Hi @MarkvanMentshttps://github.com/markvanments. There was a broken link in this PR: "(howto/security/create-a-secure-app)" needed to be "(../security/create-a-secure-app)", because "security" is only a sub-folder in the same main folder as "Use the SAP XSUAA Connector." When sending a PR, please try to make sure there will be no merge conflicts by checking the continuous-integration/travis-ci-pr build log at the bottom (click Details to see the test results if necessary, and you can see any errors in the log). Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/mendix/docs/pull/988#issuecomment-365187972, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Ah2RWKGgmOejq7E_Q3ALBligdwCOVWZyks5tUUnvgaJpZM4SCT63.

No problem Mark, we’ll go over this tomorrow. Using Travis is relatively simple. Fixing build errors and merge conflicts takes some practice. 😊
From: Mark van Ments<EMAIL_ADDRESS>Sent: February 13, 2018 9:44 AM
To: mendix/docs<EMAIL_ADDRESS>Cc: Adam Dupaski<EMAIL_ADDRESS>State change<EMAIL_ADDRESS>Subject: Re: [mendix/docs] SAP How-to's: Changes identified when following the instructions (#988)
Sorry, Adam.
Is there a way to test this when I’m editing locally?
Is there some documentation on using travis-ci-pr, I can’t remember whether we covered it in our meetings?
Perhaps you can go through this at our meeting tomorrow as I have obviously missed something important?
Mark
From: Adam Dupaski<EMAIL_ADDRESS>Sent: 13 February 2018 09:38
To: mendix/docs<EMAIL_ADDRESS>Cc: Mark van Ments<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [mendix/docs] SAP How-to's: Changes identified when following the instructions (#988)
Hi @MarkvanMentshttps://github.com/markvanments. There was a broken link in this PR: "(howto/security/create-a-secure-app)" needed to be "(../security/create-a-secure-app)", because "security" is only a sub-folder in the same main folder as "Use the SAP XSUAA Connector." When sending a PR, please try to make sure there will be no merge conflicts by checking the continuous-integration/travis-ci-pr build log at the bottom (click Details to see the test results if necessary, and you can see any errors in the log). Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/mendix/docs/pull/988#issuecomment-365187972, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Ah2RWKGgmOejq7E_Q3ALBligdwCOVWZyks5tUUnvgaJpZM4SCT63.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://github.com/mendix/docs/pull/988#issuecomment-365189335, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ATZPMZGuxlVYvi7VeVi-ZDjGuz_hO4sSks5tUUtIgaJpZM4SCT63.


Windows Server 2008/2016 r2 安装VN Studio 2.1.4 后无法启动图形界面，发生qt相关错误。

Hi @vnpy
我在Windows Server 2008/2016 r2安装VN Studio 2.1.4 遇到错误，请求帮助，先行谢过，感谢！
环境

操作系统: 如Windows Server 2008 r2 / Windows Server 2016 r2
Python版本: 如VNStudio-2.1.4
vn.py版本: 如v2.1.4

Issue类型
三选一：Bug
预期程序行为
预期VN Studio 安装后，图形界面能够正常运行（如WIN10）。
实际程序行为
1.尝试Windows Server 2008 r2 / Windows Server 2016 r2安装 VN STUDIO 2.1.4后，双击图标无反应。
2.直接运行run.py:
Traceback (most recent call last):
  File "run.py", line 4, in <module>
    from vnpy.trader.ui import QtGui, create_qapp
  File "C:\vnstudio\lib\site-packages\vnpy\trader\ui\__init__.py", line 11, in <
module>
    from .mainwindow import MainWindow
  File "C:\vnstudio\lib\site-packages\vnpy\trader\ui\mainwindow.py", line 28, in
 <module>
    from .editor import CodeEditor
  File "C:\vnstudio\lib\site-packages\vnpy\trader\ui\editor.py", line 4, in <mod
ule>
    from PyQt5 import QtWidgets, Qsci, QtGui
ImportError: DLL load failed: 找不到指定的模块。

3.升级pip install -U pyqt5 sip后再次运行run.py：
遇到弹框错误：
python.exe - 系统错误
无法启动此程序，因为计算机中丢失 MFPlat.DLL。尝试重新安装该程序以解决此问题。

QtWebEngineProcess.exe - 系统错误
无法启动此程序，因为计算机中丢失 MFPlat.DLL。尝试重新安装该程序以解决此问题。

确定后：
qt.network.ssl: QSslSocket: cannot resolve SSL_CTX_set_ciphersuites
qt.network.ssl: QSslSocket: cannot resolve SSL_set_psk_use_session_callback
qt.network.ssl: QSslSocket: cannot resolve SSL_SESSION_is_resumable
qt.network.ssl: QSslSocket: OpenSSL >= 1.1.1 is required; OpenSSL 1.1.0i  14 Aug
 2018 was found instead
qt.network.ssl: QSslSocket: OpenSSL >= 1.1.1 is required; OpenSSL 1.1.0i  14 Aug
 2018 was found instead
qt.network.ssl: QSslSocket: OpenSSL >= 1.1.1 is required; OpenSSL 1.1.0i  14 Aug
 2018 was found instead
qt.network.ssl: QSslSocket: OpenSSL >= 1.1.1 is required; OpenSSL 1.1.0i  14 Aug
 2018 was found instead
qt.network.ssl: QSslSocket: OpenSSL >= 1.1.1 is required; OpenSSL 1.1.0i  14 Aug
 2018 was found instead
qt.network.ssl: QSslSocket: OpenSSL >= 1.1.1 is required; OpenSSL 1.1.0i  14 Aug
 2018 was found instead
qt.network.ssl: QSslSocket: OpenSSL >= 1.1.1 is required; OpenSSL 1.1.0i  14 Aug
 2018 was found instead
qt.network.ssl: QSslSocket: OpenSSL >= 1.1.1 is required; OpenSSL 1.1.0i  14 Aug
 2018 was found instead
qt.network.ssl: QSslSocket: OpenSSL >= 1.1.1 is required; OpenSSL 1.1.0i  14 Aug
 2018 was found instead
qt.network.ssl: QSslSocket: OpenSSL >= 1.1.1 is required; OpenSSL 1.1.0i  14 Aug
 2018 was found instead
qt.network.ssl: QSslSocket: OpenSSL >= 1.1.1 is required; OpenSSL 1.1.0i  14 Aug
 2018 was found instead
qt.network.ssl: QSslSocket: OpenSSL >= 1.1.1 is required; OpenSSL 1.1.0i  14 Aug
 2018 was found instead
qt.network.ssl: QSslSocket: OpenSSL >= 1.1.1 is required; OpenSSL 1.1.0i  14 Aug
 2018 was found instead
qt.network.ssl: QSslSocket: OpenSSL >= 1.1.1 is required; OpenSSL 1.1.0i  14 Aug
 2018 was found instead
qt.network.ssl: QSslSocket: OpenSSL >= 1.1.1 is required; OpenSSL 1.1.0i  14 Aug
 2018 was found instead
qt.network.ssl: QSslSocket: OpenSSL >= 1.1.1 is required; OpenSSL 1.1.0i  14 Aug
 2018 was found instead
qt.network.ssl: QSslSocket: OpenSSL >= 1.1.1 is required; OpenSSL 1.1.0i  14 Aug
 2018 was found instead
qt.network.ssl: QSslSocket: OpenSSL >= 1.1.1 is required; OpenSSL 1.1.0i  14 Aug
 2018 was found instead
qt.network.ssl: QSslSocket: OpenSSL >= 1.1.1 is required; OpenSSL 1.1.0i  14 Aug
 2018 was found instead
qt.network.ssl: QSslSocket: OpenSSL >= 1.1.1 is required; OpenSSL 1.1.0i  14 Aug
 2018 was found instead
qt.network.ssl: QSslSocket::connectToHostEncrypted: TLS initialization failed

请下载安装vcredist x64 2019
https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads
安装好后重启电脑，再运行vn.py


Rebrand SanchoNet and remove copyrighted content

We need to find a name for GovTool on other networks besides Sancho. We are moving beyond Sancho now.
There is currently no rebrand that's approved, or new name for the app, however I would suggest that we call it "Cardano GovTool". This is in preference to "Voltaire" as Voltaire is not a thing that's being governed, it's a phase of the Cardano blockchain development.
@Ryun1 also tells me that the digital pumpkin is not owned by us, nor do we have the rights to use it. It also delivers very little identity or branding content. It needs to be replaced with something. Possibly a Cardano logo, if we go with "Cardano GovTool" as the name.
@l-br1 Can you please have a look and comment? I'd like to ask the designers to work on this right away. I'm assigning this to you for your attention.

I think we need to re-size what we mean by rebranding.
I would agree that Cardano govtool would be nice, but we don't have the rights to use Cardano, that is why we called it Voltaire Govtool (which is the official name), for short, govtool.
The rebranding in this instance just refers to witching back logos and text (especially on landing page) to refer to Voltaire Govtool instead of sanchonet govtool.
Regarding the pumpkin, it's free to use use, so we can use it, if needed I can pay $49 to get the full set.
So TLDR:

Name: Voltaire Govtool (logo already exists)
not the time to start an actual rebranding
Action: change logo to the original one and check copy to reference the production tool

cc: @bosko-m

OK, that's simple enough. @l-br1


I want my channels to be monitored

User Story
As Chris I want my channels to be monitored so that I can go offline after receiving a transfer.
Acceptance criteria
Additional information
Monitoring Service Spec: https://raiden-network-specification.readthedocs.io/en/latest/monitoring_service.html

We can split the story like this:

Closing as individual issues have been created.


sys_pm: fragility in residency policy

The residency policy for system power management captures a list of defined residency durations in the order of SLEEP levels 1, 2, and 3 followed by DEEP_SLEEP levels 1, 2, and 3.
The policy then looks for deepest level for which a requested timeout meets the minimum requirements.
There are a couple problems with the design and implementation:

The algorithm assumes that the residency durations are monotonically increasing, but nothing verifies it;
The table includes a complex nesting of preprocessor directives to produce a list with only defined elements, and replicates these directives when defining available sleep modes, creating a potential for inconsistency;
When a sleep state is enabled that requires an external signal to wake (e.g. deep sleep) the policy may inadvertently result in an unbounded sleep acceptable because enabling CONFIG_SYS_POWER_DEEP_SLEEP_STATES is opt-in, see https://github.com/zephyrproject-rtos/zephyr/pull/22084#issuecomment-578498729

A potential resolution to part of this would be to remove the deep sleep states (which include power gating) from the residency policy.  Note that also there are legitimate uses of K_FOREVER sleeps that are expected to be woken due to external events not monitored by poll, so IMO a "forever timeout" should never power-off the system.

Tagged as has-pr because if #20950 gets merged this can be reduced to low priority (but shouldn't be closed).

per discussion in release meeting #20950 has been approved and merged and the priority of this issue has been set to low for now

A potential resolution to part of this would be to remove the deep sleep states (which include power gating) from the residency policy. Note that also there are legitimate uses of K_FOREVER sleeps that are expected to be woken due to external events not monitored by poll, so IMO a "forever timeout" should never power-off the system.

deep sleep doesn't power-off whole system, at least some circuit(like PMU in our system) and some always on RAM(which is to save system state, like ARM's registers) is alive help to power on CPU, most of the devices, and power offed RAM again.
And I don't think removing deep sleep from residency policy is good, if your system doesn't support deep sleep, just configure CONFIG_SYS_POWER_DEEP_SLEEP_STATES=n.

Nordic does support deep sleep, but it can be woken only by external signal from certain triggers: logic level change, analog level change, NFC, USB voltage.  It does not support wakeup from a timeout.
Since deep sleep as currently defined for Zephyr does not require that it be possible to wake from a timeout it should be excluded from policies that select sleep state based solely on time until next activity.

Nordic does support deep sleep, but it can be woken only by external signal from certain triggers: logic level change, analog level change, NFC, USB voltage. It does not support wakeup from a timeout.
Since deep sleep as currently defined for Zephyr does not require that it be possible to wake from a timeout it should be excluded from policies that select sleep state based solely on time until next activity.

does that mean timer will not work well in deep sleep of that platform?

The timer does not work at all in deep sleep on that platform.  Uptime restarts from zero when the system is woken.

I'm not familiar with your platform, but if end users need timer how you handle it?

@wentongwu it would be good to keep working on your #18007 to clarify and fix all those issues.

I suspect the residency policy will be updated in the context of new work that eliminates the hard-coded states, which should settle this, but for now I think it should be left open.


[BUG]  MacOS not working.

Not sure how to install for MacOS. I cannot exactly copy the Submod folder into the thing, it will just replace it and even if I put manually, it will not work, and the mod will not show up. How to fix?

Sorry for late answer, life's been busy!
I've only recently started using MacOS myself so I can't really help here, I just made sure the binary part of the submod was compiled and worked on Mac 😅
I recommend waiting for rewrite of this mod, which happens whenever MAS gets upgrade to newer Ren'Py version!


LoadBasket in special controller

Me likes nice urls.
sharebasket/load/bID/[id] isn't nice.
Maybe a different controller loadbasket for this, rsulting like loadbasket/bID/[id] ?

👍 for something nice and short
Maybe even consider inserting into s_core_rewrite_url and you could have /[id]
Those entries would have to be deleted too once saved baskets get deleted by the cron job.

Great idea @dneustadt 😱
loadBasket/OurBestProducts 👍


Strip known bad character sequence before parsing

The bad character sequence leads to the whole response failing to parse.
Specifically this is the substitute character and is not valid for
use in XML. Therefore, this change should be safe, or at least lead to a
preferable outcome to outright failure.
Related issues: #166 #219

We've had this live for a few days now and the related errors have disappeared.


Theme does not work online as a project site while renders correctly locally

I'm trying to set up SinglePaged theme for one of my github projects. I already have my personal site set up using another Jekyll theme (So-Simple). So, lets assume my personal site runs on UserName.github.io.
For a project site, I created gh-pages branch for my github project repository and used SinglePaged files to set up the content of my page. The address of the site would be something like UserName.github.io/ProjectName.
When I run bundle exec jekyll serve on my machine, the site is built correctly locally. However, when I check how it looks online, all I see is a plain content of the last "post" without any text formatting.
I'm new in Jekyll and web development, but I did little bit of research and found this situation can happen when a certain variable baseurl is not set (correctly) for a project site. I do not see baseurl variable at the _config.yml of SinglePaged.
So my question is: how do I fix this situation? Assuming I add the baseurl variable, what files and how do I need to edit them so that they take the baseurl into account? Or do I not use SinglePaged theme correctly and it is supposed to work without baseurl? For reference, I tried some other theme where it is possible to specify the baseurl and it rendered correctly online; so from this experience I feel like it is about missing baseurl.
I really would like to use SinglePaged for my project, so would appreciate any hints in what direction to move.

Hi,
it should render correctly if you use the fork of CjS77.
A link to his fork is here.

Thanks for answering, however I already used another fork ( htacg ), and then had to modify it to reset the font and other settings to default values, as I liked them more. Using baseurl indeed solved the problem in my case.


Adding apache nifi

Adding apache nifi would allow to have an ETL in the stack, sqoop being deprecated.
A retag of apache nifi TDP version is done at this URL: https://github.com/Linagora-BigData/nifi-TDP
We are working on the integration steps.
Code modifications will follow soon:

Artifact (tar.gz) download URL in tdp-getting-started
ansible playbooks in tdp-collection-extras

Hello @Drasrax,
Thanks for wanting to contribute to TDP !
I have checked the your NiFi fork and have some remarks:

You commited the pom.xml.versionsBackup files which we don't need. You should use -DgenerateBackupPoms=false with mvn versions:set.
You should build and test NiFi against the TDP versions of Hadoop, Hive, Ranger and HBase.
You should also add a tdp dir to the fork with informations about how to package / test / which tests are not passing and why, etc. Please find a good example of what @Nuttymoon did with Spark 3 here.

Once we have all that, we'll create a nifi repo to the TOSIT-IO organization and integrate your playbooks to the TDP extra collection.

Thanks for the proposal. Give me some time to back to you with an update about that.

IMHO, the code changes should be discussed in the PR (not in the issue)

IMHO, the code changes should be discussed in the PR (not in the issue)

Agreed! Thought it's a bit special here because we are talking about integrating their repo into the TOSIT-FR org.
I created an issue in their repo here: https://github.com/Linagora-BigData/nifi-TDP/issues/1

Close as inactive.


Any releases expected soon?

Hi. I see a lot of changes being pushed to master since last commit, and it would be really awesome to see them released. At least I'm looking forward to preventCloseOnClick for SubMenu component.
Any ETA? Thank you for great work

I'll try to make a release soon.

Done


ATmega2560 - 3 byte Program Counter

The ATmega2560 R3 uses a 3-byte Program Counter.  For compatibility, please consider a minor enhancement to address the different platforms that use a 3-byte Program Counter vs 2-byte.  The documentation regarding compatibility found on the arduino.cc site should also be reviewed.  (https://www.arduino.cc/reference/en/libraries/avr-context/)

Hi! Thanks for the interest in the library!
I do not have an Arduino mega at hand at the moment, but will take a look when I can.

Has there been any process on this? Or is there any help you need?


Any other way to include the library?

Is there any other way to include the library without going through the workspace hassle on existing projects?

No that I know of. You could just include the code in your project, but you'd have to mess with internal imports to get them to work.
We're doing our best to enforce the best practice, which is to use workspaces with static libraries. However, I think some work has been done to integrate KKGridView with CocoaPods (which is supposed to handle the workspace wrangling for you). I have no experience with CocoaPods, though, so I don't know the specifics of how it works.

OK to close this?


Update version

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

#sign-off

@mihaelablendea: I'm sorry - only the author of this article, @rothja, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

@rothja could you please sign off? The AKS version has to be at least 1.12 for a single node AKS cluster to accommodate more than 16 disks.

#sign-off


[MultiKueue] Document batch/Job managedBy field usage

What type of PR is this?
/kind documentation

What this PR does / why we need it:
Document how to use managedBy provided by the Job Controller.
Which issue(s) this PR fixes:

Fixes #3357
Special notes for your reviewer:
Does this PR introduce a user-facing change?

NONE

@tenzen-y @mimowo ptal

Otherwise lgtm

/cherry-pick website


Share track: incl. actual track data

At the moment, only a summary (as text) is shared while not sharing the actual data.
Needs to be done in ShareActionProvider while the actual data needs to be stored in a temporary file.

Implemented.


travis-ci: Update infrastructure to Trusty Tahr.

Update Travis to use the latest version of Ubuntu: 14.04.3 Trusty Tahr.

Fix issue where Node v0.10 did not get installed, therefore builds
would fail. In addition, don't hardcode the path to Node v0.10.36 as
there have since been updates to v0.10.
Fix issue where CMake cannot find the PythonLibs folder, fixed via
https://github.com/travis-ci/travis-ci/issues/5326
Ensure that we have the Python2 development headers

Nice! Please sign off your commit.
https://github.com/intel-iot-devkit/mraa/blob/master/CONTRIBUTING.md

Thanks @tingleby, done now!

yay!

Looks very good but no java builds in this. JNI not around? It seems that openjdk was on by default on old travis builds but not those 14.04 containers :(

What do you mean @arfoll? I'm seeing a Java build occuring https://travis-ci.org/intel-iot-devkit/mraa/jobs/143317670#L1730 https://travis-ci.org/intel-iot-devkit/mraa/jobs/143317672#L1728 and https://travis-ci.org/intel-iot-devkit/mraa/jobs/143317676#L1732.

I must have been looking at the clang builds sorry, you're right it's all there...
Merged, thanks alot!


pull request for e2e test at 11/21/2016 12:26:06

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


fix(Button): remove unnecessary utils call and return calculated text width

Description

When dealing with fonts with custom fontStyle set, the measureTextWidth util method acts unexpectedly. It does not seem to actually be needed for the Button anyway.
References

Testing

Automation

Checklist

[ ] all commented code has been removed
[ ] any new console issues have been resolved
[ ] code linter and formatter has been run
[ ] test coverage meets repo requirements
[ ] PR name matches the expected semantic-commit syntax

Sanity Tests Execution Failed.

This change should resolve the failing Button test: https://github.com/rdkcentral/Lightning-UI-Components/pull/242.

:tada: This PR is included in version @lightningjs/ui-components-v2.3.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update test_cli.py

added comments

fixes #

Checklist:

[ ] Add tests that demonstrate the correct behavior of the change. Tests should fail without the change.
[ ] Add or update relevant docs, in the docs folder and in code.
[ ] Add an entry in CHANGES.rst summarizing the change and linking to the issue.
[ ] Add .. versionchanged:: entries in any relevant code docs.
[ ] Run pre-commit hooks and fix any issues.
[ ] Run pytest and tox, no tests failed.

Thanks, but we don't typically accept changes like this, especially from new users. If you're looking for ways to contribute, check out it open issues that do not yet have a linked open PR.


Command: build

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

Migrated to limetext/lime-backend#61.


Unexpected type in pulls.get response

Bug Report
Current Behavior
I have the following code:
  const diff = await context.github.pulls.get({
    owner,
    repo,
    pull_number,
    mediaType: {
      format: 'diff'
    }
  })

  console.log(typeof diff.data)

The console.log line prints out string when I run this code in my probot app. However, it seems like the typechecker sees diff.data is of type Octokit.PullsGetResponse. Furthermore, when I do: console.log(diff.data.body), I get undefined (which seems consistent with diff.data being seen as a string at runtime. When I try to use diff.data in a string-accepting function, I get the following error:
Argument of type 'PullsGetResponse' is not assignable to parameter of type 'string'.

Expected behavior/code
A clear and concise description of what you expected to happen (or code).
Environment

Probot version(s): ^9.5.0 (includes the patch from my previous bug report, #1024 )
Node/npm version: 10.16.0
OS: MacOS

Possible Solution

Additional context/Screenshots
Add any other context about the problem here. If applicable, add screenshots to help explain.

Sorry that nobody got back to you! We don't currently have the right response types if you use the media type format. It's hard to make that work with all possible configurations, but not impossible.
If you want to help out, the right place do do is is in the @octokit/rest repository at https://github.com/octokit/rest.js/blob/master/scripts/update-endpoints/typescript.js. Pull requests welcome :)


Possible to explicitly specify output paths?

I'd like to be able to explicitly specify the output destination of directories during build
For example, I have a "/templates" folder in my source, that contains many sub directories, each of which contains template files. I want to change where the contents of that folder get built to.
For sanity, I like to keep this /templates folder in source directory, rather than moving all of its children "up a level" to my directory root. However, on build output, I would like the contents of "/templates" to be served to "/". I understand Middleman likes to map 1:1 but for larger projects it's unmanageable to keep all template files in a flat structure.
Is there a way to accomplish this? Thanks in advance.

So, using after_build, I'm able to manually move the contents. For example I want to move /es, /fr, etc. from /translations where they are built to the root directory, as well as move the contents of /templates up to the root, I do the following:
`after_build do |builder|
after build we move our translations folders up to the root of the project so we can access them as url roots
we use force incase a previous build's files remain, we'll overwrite with latest
FileUtils.mv(Dir['build/translations/*'],'build/', {:force => true})
and we also move out template files up to the root so we can have cleaner urls
FileUtils.mv(Dir['build/templates/*'],'build/', {:force => true})
then delete the folders in their original locations
FileUtils.rm_rf('build/templates')
FileUtils.rm_rf('build/translations')
end`
It would be nice to have this be a during-build option if possible to avoid extra steps during deploy!

Hiya
I do not understand why you want to move whats inside /templates though - they should be dynamic and utilised by proxy pages.
It seems to me you should create most of these as partials and then call them into say modules that already exist in the source. Check out my pattern here: https://github.com/iwarner/CodeBlender-Middleman/tree/master/source  and https://github.com/iwarner/CodeBlender-Middleman/tree/master/source/atom/badge I have loads of partials in the source folder that I simply call into the templates. Maybe we are doing something similar?
Check out : https://github.com/middleman/middleman/issues/697
Basically you can build an extension to utilise the internal thor actions and do what you need to do - either within Config or as a standalone lib.
also an example of a extension that uses this
https://github.com/bbtfr/middleman-bower/blob/master/lib/middleman-bower/commands.rb
Hope this helps a little at least
Ian

@iwarner Thanks for the response, maybe I didn't explain well. I think we do have a similar set up.
Here's my source
source -partials -layouts -templates --resources ---casestudy ----template.html.erb ----index.html.erb ---ebook ---etc --blog --etc -javascripts -images -etc
So, I do build my dynamic pages via proxy pages helper - that all works fine. Where I run into trouble is getting the contents of /templates in source to output to /build ROOT so that my published paths don't contain /templates.
Further, I've found the need to roll my own translation system, and it works almost perfectly. Basically, on build, I'm manually creating looping through my partials, and layouts, and certain template files, copying those to new locations (basically /partials/translations, /translations/ etc.), with a folder per language, and then do a regex search and replace to replace instances of "en-US" with all languages I've defined. Again, this works fine.
However, I'm left with /translations/es, /translations/fr, /translations/etc in my source directory. Which is intended, as I don't want to litter my source directory with dozens of language folders.
After build, I use FileUtils to take the contents of /translations, and /templates that have been output into build directory, and move them all "up a level" to the root of the build directory, so the paths on deployed site for users are /fr vs /translations/fr, and /blog vs. /templates/blog
SO - now my build folder is totally "flat" - and my templates are all output as desired to root, however because I moved the files with FileUtils, MM's sitemap is not aware of the new structure, and as such middleman s3_sync can't upload this new structure. So, I'm manually calling
import_path File.expand_path('build/*', app.root)
which, upon looking at /__middleman, correctly maps my build (now, this means that my local sitemap has both versions of paths, which isn't ideal, but works)
BUT - the issue here is that things that are dependent on the MM sitemap during build process, like creating a sitemap with builder, aren't aware since the files are moved after build.
Looking through your code it seems we have a similar setup, it's just my desire to keep all templates within a folder in source to stay organized.


Adding TeXstudio.gitignore

This gitignore can be useful for LaTeX XeTeX, LuaTex in general and TeXstudio projects in particular.
*TeX creates a plethora of temporary files which will be re-generated when compiling the .tex, bibilography and style files. All these files should not be included in versioning systems like git.
You may wonder why .pdf files are not ignored, as the compiled result of a TeX project is a pdf. This is because illustrations in a TeX document can be pdf files which you will need for compilation.
Reasons for making this change:
It was missing!
Links to documentation supporting these rule changes:
No changes, this is new!
If this is a new template:

Link to application or project’s homepage: https://www.texstudio.org/ https://github.com/texstudio-org/texstudio/

We already have TeX.gitignore for TeX. Could you have a look at it and maybe just add patterns missing from TeX.gitignore which are important for TeXstudio? Patterns like *.dvi, for example, are already there.

Per the feedback provided by @Anton-Sakovich. Please edit the https://github.com/github/gitignore/blob/main/TeX.gitignore


[FEAT]: Question about connection an API to AnythingLLM

What would you like to see?
I would like to know if Anything LLM supports a feature that allows integration with external APIs, specifically Dify API. I already have the API URL and API key from Dify, and I want to use this API to handle all chat interactions instead of the default LLM model in Anything LLM. Specifically, I'm looking for the following:
API Integration: The ability to input the Dify API URL and API key into the system and establish a connection between Anything LLM and Dify's services.
Redirect Requests: I want all incoming queries from the current chat interface to be automatically sent to the Dify API, and the responses from Dify should seamlessly display in the chat interface.
Security: The integration should ensure the API key is securely stored and protected.
Configurable: The admin interface should provide an option to enable/disable the use of the Dify API and easily update the API URL and key when needed.
Logging and Monitoring: There should be a logging mechanism to track the requests sent to the Dify API and the responses received for monitoring and troubleshooting.
Does Anything LLM support such a feature or is there a way to integrate an external API like Dify for chat interactions?

I am not intimately familiar with DIfy, but if the endpoint is the same request/response format as OpenAI you can use the OpenAI Generic Connector in our "LLM Preference" selection and use the correct base URL and params and you should be able to use Dify as your LLM.
Everything except Logging and Monitoring will be present, that is a separate piece of work we are looking to add and is on the roadmp

@timothycarambat
Sadly dify's api format is not the same as OpenAI
I love anythingLLM's chat interfaces, but regarding agent, I prefer dify's workflow style.
I think it's a waste for this project to chase an agent-configure like dify, so it may be better and easier to support dify api?

think it's a waste for this project to chase an agent-configure like dify, so it may be better and easier to support dify API?

You can do this already. Just make a custom agent that calls the Dify endpoint

@timothycarambat

You can do this already
But using agent means I should add "@agent" in my every prompt , right? That's not convenient.
So maybe the approach is to enable a "default agent" in a workspace which takes over all prompts by default instead of waiting for a mention?

@Reekin the reason @agent is a separate flow from just regular chat is that it can lead to much more latency per request and token consumption and since agent skills are not yet scoped per workspace this can lead to hallucination calls invoking skills that are unrelated to a prompt causing side effects.
So we have it to where if you want to run an agent skill, you do so intentionally to prevent user foot-gunning during a prompt response flow. Ideally, in the future it is all in one for a prompt and the decision is made based on the user prompt


$ in entry causes fatal error

I've been using the CLI to parse a bibtex file of conference proceedings, which includes abstracts. Every time the parser hits a dollar sign ($) it errors out (it took me awhile to figure out which character was causing the problem).
If anyone else has this issue you can escape the characters in the text with \$ as a temporary fix.
Here's the error output:
   at Lexer._token (/Users/abi/.nvm/versions/node/v14.15.0/lib/node_modules/citation-js/node_modules/moo/moo.js:533:13)
    at Lexer.next (/Users/abi/.nvm/versions/node/v14.15.0/lib/node_modules/citation-js/node_modules/moo/moo.js:480:19)
    at Grammar.consumeToken (/Users/abi/.nvm/versions/node/v14.15.0/lib/node_modules/citation-js/node_modules/@citation-js/core/lib/util/grammar.js:34:31)
    at Grammar.Text (/Users/abi/.nvm/versions/node/v14.15.0/lib/node_modules/citation-js/node_modules/@citation-js/plugin-bibtex/lib/input/text.js:330:18)
    at Grammar.consumeRule (/Users/abi/.nvm/versions/node/v14.15.0/lib/node_modules/citation-js/node_modules/@citation-js/core/lib/util/grammar.js:48:37)
    at Grammar.MathString (/Users/abi/.nvm/versions/node/v14.15.0/lib/node_modules/citation-js/node_modules/@citation-js/plugin-bibtex/lib/input/text.js:309:24)
    at Grammar.consumeRule (/Users/abi/.nvm/versions/node/v14.15.0/lib/node_modules/citation-js/node_modules/@citation-js/core/lib/util/grammar.js:48:37)
    at Grammar.Text (/Users/abi/.nvm/versions/node/v14.15.0/lib/node_modules/citation-js/node_modules/@citation-js/plugin-bibtex/lib/input/text.js:323:18)
    at Grammar.consumeRule (/Users/abi/.nvm/versions/node/v14.15.0/lib/node_modules/citation-js/node_modules/@citation-js/core/lib/util/grammar.js:48:37)
    at Grammar.BracketString (/Users/abi/.nvm/versions/node/v14.15.0/lib/node_modules/citation-js/node_modules/@citation-js/plugin-bibtex/lib/input/text.js:272:22)

Thank you for taking the time to make a bug report! What version of Citation.js are you using?

I am only able to reproduce this in the case of unbalanced $ which do need to be escaped in all TeX-based syntax, as far as I am aware. If you have a different problem, please provide more information.

I am only able to reproduce this in the case of unbalanced $ which do need to be escaped in all TeX-based syntax, as far as I am aware. If you have a different problem, please provide more information.


SCTP unreliable data channels seems no to recover from poor network conditions

Hi,
We have a publisher/subscriber scenario based on WebRTC where we have a chrome peer publishing data trough a data channel to a server, upon receiving that data, the server forwards it to other the webrtc subscribers. We have observed that some times, when peers start entering and leaving areas with poor connectivity, there are occasions where data channels in some of those peers stop receiving data after coming back to areas where the connectivity should not be a problem without any apparent reason.
This issue mainly happens when unreliable data channels are used.
We have managed to replicate that scenario by connecting peers into a controlled network where we can induce losses and delay. Here, we connect a publisher to the server and then we connect three more subscribers. The publisher never stop sending data through the data channels, we check that receivers start getting data and after a while we induce 30% of losses and 200 ms of delay in the direction from server to subscribers, the publisher network never changes and it remains sending data all the time. We leave that configuration for a few seconds and then we remove those network restrictions. We repeat this experiment for several times until all of a sudden one of the peer stops receiving data once the network conditions are back to normal.
What should we expect?
We should expect that after network restrictions are removed, all peers should start receiving data again.
What happens?
Some peers start receiving data again, but some other peers never get data again.
I certainly can not explain this behaviour, I got traces from the subscribers where we can clearly see how the bitrate varies based on network conditions applied. I uploaded a chart with the data I collected from the subscribers browsers.

I also managed to dump a decrypted SCTP capture of the traffic that the server sends toward the subscribers, the only difference I see from peers whose data channels work and the ones whose data channels stop receiving data is that in the latter ones, when the network has recovered, there are a lot of FORWARD_TSN messages whereas in the ones where the data flows, those messages stop being sent as soon as the connectivity goes back to normal again.
I attached a capture of the peer whose data channel stops receiving data even a while after the network restriction is removed. Next pcap file belongs to chrome-1 in above graph.
chrome_1_sctp.zip
Is there anything I'm missing?

You are using an unordered data channel. What kind of unreliability are you using?

So far, I was not able to reproduce the issue. My setup consists of three FreeBSD hosts.
S -- r -- R
where S is the sender, r the router and R the receiver. I used tsctp (https://github.com/nplab/tsctp/) on S and R to test the SCTP implementation of the FreeBSD kernel. I used dummynet on r to control the network conditions.
Sender: ./tsctp -P 2 -t 0 -u -T 72000 <IP_ADDRESS>
Sends 1024 byte messages as fast as possible for 20 hours (-T) unordered (-u) with Partial Reliability (-P) and a number of retransmissions of 0 (-t)
Receiver: ./tsctp -L <IP_ADDRESS> -d 3
Receives all data and prints every 3 seconds the current goodput (-d)
Router: Toggles every 15 seconds between no packet loss, no delay and a packet loss rate of 30 %, a delay of 200 ms for the packets from the sender to the receiver.
The receiver shows how the packet loss rate and delay reduces the goodput, but also that it is always able to increase the goodput after the packet loss rate and delay were removed.
It might be an issue specific to usrsctp. I will proceed with a similar test for usrsctp.

I had also no success in reproducing the issue with usrsctp. I used the same setup as above and the usrsctp version of tsctp on the sender and receiver.
Sender: programs/tsctp -P 2 -t 0 -u -T 72000 -U 9899 -l 1000 <IP_ADDRESS>
Receiver programs/tsctp -L <IP_ADDRESS> -d 3
Router: Toggles every 15 seconds between no packet loss, no delay and a packet loss rate of 30 %, a delay of 200 ms for the packets from the sender to the receiver.
It showed the same behavior as with the FreeBSD kernel implementation of SCTP. The throughput clearly decreases when the router activates the packet loss and delay, but it always increases to the previous throughput value afterwards.
@sancane The packet capture file helped me to better understand the issue. However, we see only one side, the side of the sender. At the end of the file, for the sender, it looks like the packets simply does not make it to the receiver. Do you have the chance to rerun your test and capture on both sides?


Edits to CSV file download tables

[ ] Change "receiver" to "description"
[ ] Reorganize order now that we're using UUID as well

This has been basically resolved already, closing!


Invalid URI error

Hi,
I get this message.
System.InvalidOperationException: 'An invalid request URI was provided. The request URI must either be an absolute URI or BaseAddress must be set.'
Any recommendations?

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

ID: 1df9d0f9-f84c-2e24-9ea2-9956af815b92
Version Independent ID: 0437ab02-8f50-17df-10be-219beddec22b
Content: Visual Studio Connected Service - Computer Vision - Azure Cognitive Services
Content Source: articles/cognitive-services/Computer-vision/vs-computer-vision-connected-service.md
Service: cognitive-services
GitHub Login: @ghogen
Microsoft Alias: ghogen

@toenie23 For this issue, you simply need to specify the full URL ( including the protocol). Please try and tell us if you still suffering from this problem. Thank you.

@toenie23 We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

@YutongTie-MSFT sorry i am just seeing this notification, how do i retrieve the full URL with protocol?


Percolator only crashes, Qvality doesn't work

Hello,
Thanks for making ursgal.
I'm trying to use just the basic search.py example and it seems the output of qvality will only be "1" for PEP, and "-1.#IND" for q-value regardless of any input.
Secondly, I can't get percolator to work on any data sets. I'd found a previous issue with this, Issue#13 ( https://github.com/ursgal/ursgal/issues/13 ), but the only inference was that the data set was not large enough. I've had this crash on both small and large data sets alike with no success whatsoever.
The largest data set I've tried is a proteomic experiment available on PRIDE, q01511.raw of:
https://www.ebi.ac.uk/pride/archive/projects/PXD008222/files
that was searched with the canonical & isoform proteom from uniprot:
http://www.uniprot.org/proteomes/UP000005640
I believe this would be large enough to perform validation on based on the number of peptides identified in the publication.
The version I'm using was cloned yesterday. I'm really interested in getting this workflow up and running, is there anything I could do to alleviate this problem?
Output from large data set crash and the small data set crash are the same:
percolator_2_08 crashed!

  The executable
    ursgal\resources\win32\64bit\percolator_2_08\percolator.exe
  terminated with Error code<PHONE_NUMBER> .
  Inspect the printouts above for possible causes and verify that all input files are valid.

Hi NameyMcNamo,
thanks for using Ursgal ;-)
I am not sure which example script with validation you mean, the simple_example_search.py script doesn't include a validation step, but e.g. the xtandem_version_comparison.py or the do_it_all_folder_wide.py does. The first one should work without any additional input. But it doesn't for you?
The PRIDE dataset looks more than large enough, yes. However, did you generate a target-decoy database after downloading the human proteome? If not, then this could be you problem. There is an example script for that: target_decoy_generation_example.py (although I would suggest to use 'shuffle_peptide' isntead of 'reverse_protein')
If this the above doesn't work and if the missing decoy is not the problem, then could you include the script that you are using and ideally more of the output message before the crash report (i.e. the output message of Percolator that you can also see in #13)?

Oh, I had been doing that wrong hah. The do_it_all folder_wide worked after generating decoys.
Sorry, sometimes I swear I belong in a special ed class.
Cheers :)

No problem, let us know if you encounter any other problems ;)

I do have a quick question, where can one find the MSAmanda engines to download and put into the resources folder?

You can download the latest MSAmanda version here: http://ms.imp.ac.at/index.php?action=ms-amanda
(see the standalone versions somewhere at the bottom)
For older versions you probably need to contact them directly.
We have implemented the new version in Ursgal v0.6.0 (see pull request #57), which will probably be merged in the next days, but you can also directly pull this branch. In general, there are some bigger changes in v0.6.0, so if you are starting with Ursgal right now, I would suggest to directly use v0.6.0 to avoid compatibility problems. Sorry, I might should have mentioned this earlier ...

That's great, I'll jump into the newer version when it's ready. Thanks for letting me know.


ability to ignore some files

We have some files that have been copied from another project and have additional copyright / license information that must be displayed. Is it possible to ignore such files?
I'm thinking of a workaround whereby those files simply have two header sections.

+1
Same here.
I think I'd prefer some way of marking a particular header as "untouchable", e.g. via another regex.
And a task showing me all the files with "KEEP" headers would be the cherry on the cake... :)

Ouch. This little innocent project is getting too much attention. I don't have any spare cycles to work on this or similar issues these days. But hey, of course this is open source and you can help yourself and create PRs.

There is no such thing as "too much attention" in OSS... :)

... in theory ;-)

heh, funny I was thinking about this today.
I'll be giving a talk about copyright / licensing at ScalaSphere. It's only 15 minutes, so not enough time to fall asleep at the back.


Explicit name warning disabled for context parameters

Currently when parameter doesn't have name compiled from source code (javac -parameters) or   using @GraphQLArgument annotation warning is logged. This is great because I don't want to have arguments in GraphQL API accidentally named arg0, arg1 and do on. But for "context" parameters this warning is not useful because their names are not used in generated GraphQL API.
So this PR adds condition for this warning that parameter is not annotated using GraphQLContext or GraphQLRootContext annotations.

Thanks for instant response. I used GraphQLIgnore as you suggested. That's really much better 😄

Thanks for merging my PR.

Thanks for another contribution :)


Replace duplicate() by try_clone() in std::net.

The alleged implementation of this RFC in
https://github.com/rust-lang/rust/pull/22015 included try_clone rather
than duplicate. This commit updates the approved RFC to match the actual
implementation.

Fixes https://github.com/rust-lang/rust/issues/23696

Oops, thanks!


Attribution updates

I don't know how you go about doing bespoke differences like this, but I think it's important to add this disclaimer of sorts.
... AND yes, the irony of this PR is not lost on me. :trollface:

superseded by https://github.com/Azure/Azure-Governance-Visualizer/pull/31


stats issues

histograms should be normalized
boolean should not show "100.00% IN TOP 10 CAT" since there are only 3 possible values
histogram does not match somtimes (see bathroms in image, check accommodates as well), the dataset is here https://team.cartodb.com/u/saleiva/tables/airbnb_listings_sample_nyc_jan1_3
some columns are duplicated, for example number_of_reviews appears twice in the data panel

cc @nobuti

Last item is fixed in https://github.com/CartoDB/cartodb/pull/8044


Official Amazon AWS AMI images

I believe @jgarzik had floated the possibility[1] that there could be official AMI images produced. This, along with an official Docker image would be a great way of lowering the barrier for setting up a full node. Especially if the blockchain is bootstrapped so each new instance that gets spun up is not required to sync from scratch.
[1] https://twitter.com/jgarzik/status/688355566478032897

@jzbz Can you mention Docker in the name of the issue? So there wont be a duplicated issue created (Or maybe it's better to have this one for AWS and another for docker?)

@tuxayo Done. If the devs think it is better to have two separate issues I'll change it back.

Somebody did a Docker Image https://hub.docker.com/r/bitcoinclassic/bitcoinclassic/
But I don't know is it's trustworthy.

Others have picked up this ball, so closing.

Others have picked up this ball

@zander Does that means that this image gets an official endorsement?
And what about AWS AMI?

Would be nice to know the answer to @tuxayo's question too. The Docker image linked to does not seem to have a Dockerfile publicly available (at least, not that I can readily find/see from that link). I don't yet feel comfortable running it on my hosts. It would be nice if there was an official/endorsed Dockerfile somewhere to base things on.

I've done some work on installing Classic on standard AWS Linux.
It would be relatively easy to create a set of AMIs with an updated blockchain DB.
Note 1: Two flavours are required (EC2 HVM and EC2 PV) for different EC2 instance types.
Note 2: Then a copy for each AWS Region (i.e.: Ireland, Virginia, Oregon, etc.).

Thank juan!
To answer previous requests, the Classic team does not at this time have a solution we tested or are ready to endorse.
With that said, I want to point out that on a AWS or similar hosting solution you should not have any coins in your bitcoin wallet.
If you also avoid that docker image doing anything other than just running the bitcoin image there is very little that you can lose.  So if you keep an eye on the logs of both Bitcoin and your AWS image (usage, connection count etc) you can rule out abusive software and you should be largely Ok running a well documented docker image.

@zander

So if you keep an eye on the logs of both Bitcoin and your AWS image (usage, connection count etc) you can rule out abusive software and you should be largely Ok running a well documented docker image.

A good strategy to sabotage a such a docker image would be to introduce an abusive software that isn't constantly active. So it may remain unnoticed until a strategic moment and by the time, a certain number of people would be running node based a such a hypothetical malicious image.
And since there are people motivated enough to pay to DDoS classic nodes, it would be normal for the most precocious of us to fear the hypothetical scenario described above and not trust binary software distributed by a unknown source.
Anyway, keep working on the stuff you prioritize the most. Thanks for your time and work :)


Updated README.md with installation instructions

Got an error during installation with a libpq-dev dependency and added instructions for its installation.

Closing, since I've moved the issue over to Q&A:
https://github.com/recap-cloud/recap/discussions/74


chore: COMPASS-4132: Replace usage of mongodb-stitch w/ mongodb-stitch-browser-sdk|mongodb-stitch-browser-sdk

Replaces the usage of mongodb-stitch w/ mongodb-stitch-browser-sdk|mongodb-stitch-browser-sdk for the Stitch tracker.
For now, we just do a conditional require() for server or browser like we already do for electron.
The server side stitch SDK requires manually closing stitch clients like the node.js driver. A top-level helper function is available if manually closing the client is required:
// close any open stitch clients
metrics.close();

I've also updated travis to test in an electron renderer process as well.

  1) Stitch Tracker
       "before each" hook for "correctly sets enabledAndConfigured when props change":
     TypeError: Cannot read property 'create' of undefined
      at F._setup (lib/trackers/stitch.js:131:39)
      at F._enabledConfiguredChanged (lib/trackers/stitch.js:101:12)
      at Object.triggerEvents (node_modules/ampersand-events/libs/utils.js:16:59)
      at F.trigger (node_modules/ampersand-events/ampersand-events.js:77:27)
      at update (node_modules/ampersand-state/ampersand-state.js:455:26)
      at /home/travis/build/mongodb-js/metrics/node_modules/ampersand-state/ampersand-state.js:467:21
      at Array.forEach (<anonymous>)
      at F.<anonymous> (node_modules/ampersand-state/ampersand-state.js:466:60)
      at Object.triggerEvents (node_modules/ampersand-events/libs/utils.js:18:60)
      at F.trigger (node_modules/ampersand-events/ampersand-events.js:78:30)
      at /home/travis/build/mongodb-js/metrics/node_modules/ampersand-state/ampersand-state.js:268:18
      at Array.forEach (<anonymous>)
      at F.set (node_modules/ampersand-state/ampersand-state.js:267:22)
      at F.<anonymous> (lib/index.js:49:19)
      at /home/travis/build/mongodb-js/metrics/node_modules/lodash/lodash.js:4905:15
      at baseForOwn (node_modules/lodash/lodash.js:2990:24)
      at /home/travis/build/mongodb-js/metrics/node_modules/lodash/lodash.js:4874:18
      at Function.forEach (node_modules/lodash/lodash.js:9342:14)
      at F.configure (lib/index.js:38:7)
      at Context.<anonymous> (test/stitch.test.js:16:13)
      at processImmediate (internal/timers.js:439:21)

@rueckstiess thank you. No, close() is only necessary when the server sdk is being used.
On Feb 11, 2020, 8:00 AM +0100, Thomas Rückstieß<EMAIL_ADDRESS>wrote:

@rueckstiess approved this pull request.
Hi @imlucas thanks for the PR, I tested this version and everything seems to be working fine.
Do we need to call close() for the browser version as well or is that only necessary for the node version?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

<EMAIL_ADDRESS>


runner: StatusQuery allows waiting (WIP)

Every user of Runner wanted polling, so add polling.
runner/statuser.go is the new interface
Merge runner/local into runner/runners
runner/runners/README.md describes the new strategy: refactor the file f/k/a simple.go, which was doing three things:
*) should I run this -> SingleController (runner/runners/single.go)
*) how do I run this -> Invoker (runner/runners/invoke.go)
*) status database -> Statuses (runner/runners/statuses.go)
This refactor allows QueueingRunner to melt into QueueController (queue.go)
Extracts controller_test.go from simple_test.go
Awkwardly copy/update the SnapshotID due to merge conflicts (and remove its own type)
Currently, lots of code is broken because this changes an interface but not every implementation. If we like this, I'll go add the implementation (and start removing the polling code this obviates)

I question whether this batch query interface should be in the Runner codebase.
If runner is supposed to be common code shared between the Worker nodes and the Scoot Local Daemon, this will only ever be used by the later.  To me this suggests moving it up a layer above the runner.
In addition it seems like formulating query that checks the status of multiple Jobs would be useful at the CloudExec Level too, which also suggests that this code should live at a higher level, and perhaps not use the RunId as the query mechanism, but the JobId/TaskId.
A suggestion would be to modify the current CloudExec api to support querying the GetStatus API and supporting taking a list of TaskIds to query for or the masks.  This will be generally useful and greatly reduce network traffic.

I agree that CloudExec API needs something similar-ish, but in terms of its API.
The motivation here is that right now we use the Runner in two places:
*) Daemon
*) Worker
And despite having two uses, we actually have three implementations of polling:
*) sched/worker/polling.go
*) daemon/server/handler.go
*) runner/local/simple_test.go
So, the reason for this is more for the Polling/Waiting than the Batching.
The Batching will be useful for the Daemon API right now, which could make sense moving it up. But I suspect it will make sense for the Worker eventually, when we are running multiple Tasks simultaneously on one Worker (which won't be for a long time!).

Dan and I discussed this today via hangouts:
The fundamental problem here is the Runner Interface as it is today does too much.  The original goal of the Runner was to encapsulate shared logic need to run a task.  This can be shared between the Scoot Cloud Workers and the Local Scoot Daemon.
One of the core problems is the async nature of Run function.  There is no reason to do this asynchronously since the context which this library runs in is always a local one.  It should just block until the task is completed, and potentially provide an update channel.  This removes the need for polling completely.
The Worker code, will need to provide an API for polling for failure detection between itself and the scheduler, but this is because its running as part of a distributed system.  This is not core Runner functionality.
The Local Scoot Daemon will need to provide code which controls what tasks get sent to the Runner and to Scoot Cloud Exec.  But the runner in this context is not part of a distributed system, failures are correlated since they are on the same machine, and doesn't need to provide a polling API.  Ideally we want these code bases that use the Runner to evolve separately.  Their contexts are different (remote execution vs local), multi-tenancy concerns are different (cloud workers are uniform, whereas resources on dev laptops are not) etc... They look very similar now but will diverge in the future, so we should not try to make a common abstraction here.  The common shared code should be what runs the task, and this is all the Runner interface should supply.
The proposal we came up with was to replace the Runner Interface with a slimmed down version.  The Run command, returns when the task has completed.  It can also take a channel which updates are sent on.  This way callers of this method are notified immediately when a task completes instead of having to poll a local process.

Closing for now until it's ready again


@ref combined with PointSeries parameter

I'm sorry that I have to open another issue already. I have not managed to use the functions of PointColor when I want to update a chart at the same time. The colors are not displayed. Furthermore the labels are not displayed correctly. Only series-x is displayed.
Could it be that I have overlooked some option or is this currently not yet implemented?

Hi,
This looks like a bug, I'll look into it.

@WukovatzD, Could you please provide some details on how to reproduce.
You are using the PointColor function and the UpdateSeries Method?
What chart type are you using? You mention the labels are not correct, in what way?
If you could use one of the existing samples and just add code to reproduce that would help a lot.

Below the important parts of my code:
@if (_data is not null)
{
    <ApexChart Width="350" @ref="@_chart" TItem="CurrentValueWithTimeMarkDetailCountRecord">
        <ApexPointSeries TItem="CurrentValueWithTimeMarkDetailCountRecord"
                     Items="_data"
                     Name="States"
                     SeriesType="SeriesType.Pie"
                     XValue="@(e => e.Name)"
                     PointColor="@(e => StateRepository.Data.First(x => x.Id == e.Id).HexColor)"
                     YAggregate="@(e => e.Sum(x => x.Count))" />
    </ApexChart>
}

@code {
    [Parameter] public int UnitId { get; set; }

    private List<CurrentValueWithTimeMarkDetailCountRecord> _data = new();
    private ApexChart<CurrentValueWithTimeMarkDetailCountRecord> _chart;

    private Task _backgroundUpdateTask;
    private bool _disposed;

    protected override void OnAfterRender(bool firstRender)
    {
        if (!firstRender) return;

        _backgroundUpdateTask = Task.Run(async () =>
        {
            while (!_disposed)
            {
                await UpdateChartSeries();
                await Task.Delay(2000);
            }
        });
    }

    private async Task UpdateChartSeries()
    {
            if (_disposed) return;

            await SetData();
            await _chart.UpdateSeriesAsync(false);
            //await InvokeAsync(StateHasChanged);
    }

    private async Task SetData()
    {
        // Setting data this way is not working either
        //_data = await MachineRepositoryService.GetMaschineValuesWithDetailGroupCountAsync(UnitId);

        _data.Clear();
        _data.AddRange(await MachineRepositoryService.GetMaschineValuesWithDetailGroupCountAsync(UnitId));
    }

    public void Dispose()
    {
        _disposed = true;
        _chart?.Dispose();
    }
}

The graphics below is the outcome:

The set of colors which should be there:
#ff0000
#00c800
#00aaff
#ffaa00
#ffff00
#55ffff
#c86400
#aa55ff
#989c9b

Setting the colors the way below works for the colors, however not for the labels. Furthermore using PointColor in the ApexPointSeries is not working in both cases:
    private void SetOptions()
    {
        _options.Labels = StateRepository.Data.Select(x => x.Name).ToList();
        _options.Colors = StateRepository.Data.Select(x => x.HexColor).ToList();
    }

If I omit the @ref it works as desired. So my assumption is that it has to do with the @ref...
Hope this helps. If you need some more information just let me know!
Thank you for taking care of this problem!!

Hi,
Thank you for your example.
Could you do test to change the series type to bar instead of Pie  to see if you get the same issue.
I'm pretty sure this is related to how NoAxisCharts work in Apexcharts.
Onther test could be to render the chart instead of UpdateSeries.

Switching the chart type to Bar was successful. Labels and Colors are displayed in the correct way. Updating (UpdateSeries) is working with Bar too!
UpdateOptionsAsync results in that the chart is printed in the correct colors and labels and updated.
RenderAsync seems to work as well.
I hope my test result will help you!
Best regards
DW

Thank you,
The result is what I expected, for your use case using a no axis chart I would say that you should use UpdateOptionsAsync rather then UpdateSeriesAsync. The reason for this is that UpdateSeries is only sending the series data, and for a no axis chart this is limited to the values, all other settings like labels and colors are set in the options.
Please let me know if this would work for you.

Great jeah it will work! Could you add this information into documentation?
Thanks for the fast reply helped me a lot!

Great, Yes I will update the documentation.


Kafka source should check that required bootstrapServers is in yaml

Expected Behavior
Validate yaml and print useful error message when required parameters are missing
If the field is misnamed or missing then it is connecting to "" and failing with not obvious error ...
Actual Behavior
(base) macs-MacBook-Pro:knative aslom$ k logs kafka-source-strimzi-8gj2f-5867675996-rt58h
Error from server (BadRequest): a container name must be specified for pod kafka-source-strimzi-8gj2f-5867675996-rt58h, choose one of: [receive-adapter istio-proxy] or one of the init containers: [istio-init]
(base) macs-MacBook-Pro:knative aslom$ k logs kafka-source-strimzi-8gj2f-5867675996-rt58h -c receive-adapter
{"level":"info","ts":"2019-03-27T19:02:52.471Z","caller":"receive_adapter/main.go:97","msg":"Starting Apache Kafka Receive Adapter...","adapter":{"BootstrapServers":"","Topics":"","ConsumerGroup":"group9","Net":{"SASL":{"Enable":false,"User":"","Password":""},"TLS":{"Enable":false}},"SinkURI":"http://event-display.default.svc.cluster.local/"}}
{"level":"info","ts":1553713372.4723501,"logger":"fallback","caller":"adapter/adapter.go:92","msg":"Starting with config: {adapter 22 0  0xc00014c480}"}
panic: kafka: client has run out of available brokers to talk to (Is your cluster reachable?)

goroutine 1 [running]:
github.com/knative/eventing-sources/contrib/kafka/pkg/adapter.(*Adapter).Start(0xc00014c480, 0xd4e920, 0xc0000b4078, 0xc00009e6c0, 0x0, 0x0)
	/Users/aslom/Documents/awsm/go/src/github.com/knative/eventing-sources/contrib/kafka/pkg/adapter/adapter.go:106 +0x568
main.main()
	/Users/aslom/Documents/awsm/go/src/github.com/knative/eventing-sources/contrib/kafka/cmd/receive_adapter/main.go:98 +0x5d7

Steps to Reproduce the Problem

Rename or remove bootstrapServers field form kafka source config
Follow steps descrined in README in https://github.com/knative/eventing-sources/tree/master/contrib/kafka/samples

Additional Info

@dubee @matzew Is there some schema/validation tool for yaml config files? It would be great to automatically validate config and print useful messages before using invalid config.

The same happens to misnamed topics but error message is better
{"level":"info","ts":"2019-03-27T19:13:57.528Z","caller":"receive_adapter/main.go:97","msg":"Starting Apache Kafka Receive Adapter...","adapter":{"BootstrapServers":"my-cluster-kafka-bootstrap.kafka:9092","Topics":"","ConsumerGroup":"group9","Net":{"SASL":{"Enable":false,"User":"","Password":""},"TLS":{"Enable":false}},"SinkURI":"http://event-display.default.svc.cluster.local/"}}
{"level":"info","ts":1553714037.52898,"logger":"fallback","caller":"adapter/adapter.go:92","msg":"Starting with config: {adapter 22 0  0xc00012c480}"}
panic: kafka server: The request attempted to perform an operation on an invalid topic.

I have tested possible error situations with latest code
For empty strings we get nice validations errors now:
apiVersion: sources.eventing.knative.dev/v1alpha1
kind: KafkaSource
metadata:
  name: kafka-source-empty-strings
spec:
  consumerGroup: KAFKA_CONSUMER_GROUP_NAME
  bootstrapServers:
  topics:
  net:
    sasl:
      enable: KAFKA_SASL_ENABLE
      user: KAFKA_SASL_USERNAME
      password: KAFKA_SASL_PASSWORD
    tls:
      enable: KAFKA_TLS_ENABLE
  sink:
    apiVersion: serving.knative.dev/v1alpha1
    kind: Service
    name: event-display

$ ko apply -f event-source-empty-strings.yaml
The KafkaSource "kafka-source-empty-strings" is invalid: []: Invalid value: map[string]interface {}{"apiVersion":"sources.eventing.knative.dev/v1alpha1", "kind":"KafkaSource", "metadata":map[string]interface {}{"uid":"48516ea6-524d-11e9-a47e-0618ef206bb9", "name":"kafka-source-empty-strings", "namespace":"default", "creationTimestamp":"2019-03-29T18:05:49Z", "annotations":map[string]interface {}{"kubectl.kubernetes.io/last-applied-configuration":"{\"apiVersion\":\"sources.eventing.knative.dev/v1alpha1\",\"kind\":\"KafkaSource\",\"metadata\":{\"annotations\":{},\"name\":\"kafka-source-empty-strings\",\"namespace\":\"default\"},\"spec\":{\"bootstrapServers\":null,\"consumerGroup\":\"KAFKA_CONSUMER_GROUP_NAME\",\"net\":{\"sasl\":{\"enable\":\"KAFKA_SASL_ENABLE\",\"password\":\"KAFKA_SASL_PASSWORD\",\"user\":\"KAFKA_SASL_USERNAME\"},\"tls\":{\"enable\":\"KAFKA_TLS_ENABLE\"}},\"sink\":{\"apiVersion\":\"serving.knative.dev/v1alpha1\",\"kind\":\"Service\",\"name\":\"event-display\"},\"topics\":null}}\n"}, "generation":1}, "spec":map[string]interface {}{"consumerGroup":"KAFKA_CONSUMER_GROUP_NAME", "net":map[string]interface {}{"sasl":map[string]interface {}{"enable":"KAFKA_SASL_ENABLE", "password":"KAFKA_SASL_PASSWORD", "user":"KAFKA_SASL_USERNAME"}, "tls":map[string]interface {}{"enable":"KAFKA_TLS_ENABLE"}}, "sink":map[string]interface {}{"apiVersion":"serving.knative.dev/v1alpha1", "kind":"Service", "name":"event-display"}, "topics":interface {}(nil), "bootstrapServers":interface {}(nil)}}: validation failure list:
spec.topics in body must be of type string: "null"
spec.bootstrapServers in body must be of type string: "null"
2019/03/29 14:05:49 error executing 'kubectl apply': exit status 1

However if actual parameters (bootstrapServers and topics) are missing it deploys with no error:
apiVersion: sources.eventing.knative.dev/v1alpha1
kind: KafkaSource
metadata:
  name: kafka-source-missing-required
spec:
  consumerGroup: KAFKA_CONSUMER_GROUP_NAME
  net:
    sasl:
      enable: KAFKA_SASL_ENABLE
      user: KAFKA_SASL_USERNAME
      password: KAFKA_SASL_PASSWORD
    tls:
      enable: KAFKA_TLS_ENABLE
  sink:
    apiVersion: serving.knative.dev/v1alpha1
    kind: Service
    name: event-display

kafkasource.sources.eventing.knative.dev/kafka-source-missing-required created

and controller fails to create receive adapter with non-descriptive errors
ERROR: logging before flag.Parse: E0329 18:11:33.018451       1 streamwatcher.go:109] Unable to decode an event from the watch stream: unable to decode watch event: v1alpha1.KafkaSource.Spec: v1alpha1.KafkaSourceSpec.Net: v1alpha1.KafkaSourceNetSpec.SASL: v1alpha1.KafkaSourceSASLSpec.Enable: ReadBool: expect t or f, but found ", error found in #10 byte of ...|"enable":"KAFKA_SASL|..., bigger context ...|FKA_CONSUMER_GROUP_NAME","net":{"sasl":{"enable":"KAFKA_SASL_ENABLE","password":"KAFKA_SASL_PASSWORD|...
ERROR: logging before flag.Parse: E0329 18:11:33.023135       1 streamwatcher.go:109] Unable to decode an event from the watch stream: unable to decode watch event: v1alpha1.KafkaSource.Spec: v1alpha1.KafkaSourceSpec.Net: v1alpha1.KafkaSourceNetSpec.SASL: v1alpha1.KafkaSourceSASLSpec.Enable: ReadBool: expect t or f, but found ", error found in #10 byte of ...|"enable":"KAFKA_SASL|..., bigger context ...|FKA_CONSUMER_GROUP_NAME","net":{"sasl":{"enable":"KAFKA_SASL_ENABLE","password":"KAFKA_SASL_PASSWORD|...
ERROR: logging before flag.Parse: W0329 18:11:33.023205       1 reflector.go:270] sigs.k8s.io/controller-runtime/pkg/cache/internal/informers_map.go:126: watch of *v1alpha1.KafkaSource ended with: very short watch: sigs.k8s.io/controller-runtime/pkg/cache/internal/informers_map.go:126: Unexpected watch close - watch lasted less than a second and no items received
ERROR: logging before flag.Parse: E0329 18:11:34.072024       1 reflector.go:134] sigs.k8s.io/controller-runtime/pkg/cache/internal/informers_map.go:126: Failed to list *v1alpha1.KafkaSource: v1alpha1.KafkaSourceList.Items: []v1alpha1.KafkaSource: v1alpha1.KafkaSource.Spec: v1alpha1.KafkaSourceSpec.Net: v1alpha1.KafkaSourceNetSpec.SASL: v1alpha1.KafkaSourceSASLSpec.Enable: ReadBool: expect t or f, but found ", error found in #10 byte of ...|"enable":"KAFKA_SASL|..., bigger context ...|FKA_CONSUMER_GROUP_NAME","net":{"sasl":{"enable":"KAFKA_SASL_ENABLE","password":"KAFKA_SASL_PASSWORD|...
ERROR: logging before flag.Parse: E0329 18:11:35.073614       1 reflector.go:134] sigs.k8s.io/controller-runtime/pkg/cache/internal/informers_map.go:126: Failed to list *v1alpha1.KafkaSource: v1alpha1.KafkaSourceList.Items: []v1alpha1.KafkaSource: v1alpha1.KafkaSource.Spec: v1alpha1.KafkaSourceSpec.Net: v1alpha1.KafkaSourceNetSpec.SASL: v1alpha1.KafkaSourceSASLSpec.Enable: ReadBool: expect t or f, but found ", error found in #10 byte of ...|"enable":"KAFKA_SASL|..., bigger context ...|FKA_CONSUMER_GROUP_NAME","net":{"sasl":{"enable":"KAFKA_SASL_ENABLE","password":"KAFKA_SASL_PASSWORD|...

If I remove placeholder fields then receiver is created but it keeps connecting to server '' then leads to Panic so there is not very useful CrashLoopBackOff

$ cat event-source-missing-required-minimum.yaml
apiVersion: sources.eventing.knative.dev/v1alpha1
kind: KafkaSource
metadata:
name: kafka-source-missing-required-minimum
spec:
sink:
apiVersion: serving.knative.dev/v1alpha1
kind: Service
name: event-display

$ ko apply -f event-source-missing-required-minimum.yaml
kafkasource.sources.eventing.knative.dev/kafka-source-missing-required-minimum created
(base) macs-MacBook-Pro:knative aslom$ k get pods
NAME                                                          READY   STATUS             RESTARTS   AGE
busybox                                                       0/1     Completed          0          10d
kafka-source-missing-required-minimum-6tw9p-8d5c96d94-pxqs8   1/2     CrashLoopBackOff   1          14s

$ k get pods
NAME                                                          READY   STATUS             RESTARTS   AGE
busybox                                                       0/1     Completed          0          10d
$ k logs kafka-source-missing-required-minimum-6tw9p-8d5c96d94-pxqs8 -c receive-adapter
{"level":"info","ts":"2019-03-29T18:15:36.475Z","caller":"receive_adapter/main.go:97","msg":"Starting Apache Kafka Receive Adapter...","adapter":{"BootstrapServers":"","Topics":"","ConsumerGroup":"","Net":{"SASL":{"Enable":false,"User":"","Password":""},"TLS":{"Enable":false}},"SinkURI":"http://event-display.default.svc.cluster.local/"}}
{"level":"info","ts":1553883336.4762325,"logger":"fallback","caller":"adapter/adapter.go:100","msg":"Starting with config: {adapter 22 0  0xc00014a480}"}
panic: kafka: client has run out of available brokers to talk to (Is your cluster reachable?)
goroutine 1 [running]:
github.com/knative/eventing-sources/contrib/kafka/pkg/adapter.(*Adapter).Start(0xc00014a480, 0xd4e8a0, 0xc0000b4078, 0xc00009e6c0, 0x0, 0x0)
/Users/aslom/Documents/awsm/go/src/github.com/knative/eventing-sources/contrib/kafka/pkg/adapter/adapter.go:114 +0x568
main.main()
/Users/aslom/Documents/awsm/go/src/github.com/knative/eventing-sources/contrib/kafka/cmd/receive_adapter/main.go:98 +0x5d7

/kind bug

Fixed by https://github.com/knative/eventing-sources/issues/302


How do I pull in this library + time picker?

I am currently pulling in this library in my bower.json, that supports time picking as well:
"bootstrap-datepicker": "git@github.com:rchavik/bootstrap-datepicker.git#5d82d35f54c25b8cebda0c0f7493a39a80f1c4e8",

How can I pull in the latest 1.6 alpha AND have the timepicker?

That's a fork of this repository so the owner of the fork should update his fork with the original codebase! You should contact @rchavik about it!

@rchavik would that be doable? :)

@canfiax sorry, i'm unable to do this due to time constraints.
maybe you can help rebasing #909 on top of latest master?

Yes timepicking is something we have planned for 2.0/2.x but before we integrate that feature we want to rewrite some inner works so we can handle dates and datetimes better!

@acrobat any updates on this? There are currently no libraries out there that efficiently support this.

@canfiax you could use Eonasdan/bootstrap-datetimepicker. Which is sort of the same code base but with time picking and some other different features.
Again timepicking is something that should come to this lib in the future. But currently I don't have the time to added new features, etc to thislib. I hope that I can make some time in a few months!
So for now you could use the eonasdan datetimepicker!

Thanks @acrobat :)


Custom nodes are not exposed to statically compiled languages

Is it possible to use Jolt types from C#? It is impossible to inherit from JoltGeneric6DofJoint3D for example, as the type doesn't exist or I can't find the right namespace it belongs to..?

No, this is not possible at the moment, unfortunately. This is a somewhat general problem with Godot, where bindings for statically compiled languages like C#, C++ and Rust are sort of "frozen in time" from when that build of Godot was made, and anything exposed by a GDExtension (or even GDScript as seen here) won't be available from these languages. I've been meaning to investigate this since long before I even added the Jolt-specific nodes, but I haven't gotten around to it.
My initial hope/ambition was to distribute a separate NuGet package with bindings that somehow utilize GodotObject.Get, GodotObject.Set and GodotObject.Call to at least make the interface more ergonomic, but honestly I'm not sure how well that plays out in practice. I don't think you'd be able to things like inherit from such a class in any case.
There are other alternatives as well, like the approach taken by the Debug Draw 3D extension, where the bindings are generated on-demand by the extension through an editor action and compiled along with the rest of the Godot project. I believe the circumstances for Debug Draw 3D are quite different though, in that the entirety of the API can be expressed as a static class in C#, which makes this approach a lot more feasible.
The workaround in the meantime would be to utilize things like GodotObject.Get, GodotObject.Set and GodotObject.Call yourself when interacting with these nodes from C#. I don't think there's anything like that which would let you inherit from the class, but you could always make your own wrapper for it instead I guess.

Can you get access from a another GDExtension if not from C#?

Assuming your GDExtension is written in C, C++ or Rust, or any other statically compiled language, you'd have the exact same issue, and you would need to use Object::get, Object::set and Object::call to interact with any of the custom nodes.
If it's written in some dynamic language like Python or Lua (that isn't relying on bindings generated by extension_api.json) it might be a different story, but I'm not familiar enough with the scripting side of GDExtension to really say for sure.
And just be clear, you can still use this extension just fine to power all the default Godot nodes (RigidBody3D, Generic6DOFJoint, etc.) which you can obviously interact with just fine from another GDExtension, but using the substitute joints (JoltGeneric6DOFJoint, etc.) won't be very ergonomic unfortunately.

I'm new to the GDExtensions, but how do different GDExtensions communicate typically? My thinking was if there was a way to access the more advanced features of jolt, for example the simulation rollback.

There is no such channel of communication between extensions, official or otherwise. The only public symbol that's exposed from the DLL is the extension entry point, which then registers the physics server, the custom nodes, the editor plugin, etc.
Rollback in particular is also not something you'll be likely to achieve by just exposing the underlying Jolt stuff to some other extension. See this comment for more details as to why.

This is unlikely to ever be addressed from this extension alone, and with this extension now having been merged into Godot in the form of an engine module (see README), albeit without the substitute joint nodes, it will be considered to be in maintenance mode going forward, where only bug fixes will be considered for merging. As such, I'll go ahead and close this issue.
Note that the joint properties introduced by the substitute joint nodes (JoltGeneric6DOFJoint3D, etc.) will eventually be exposed by the new Godot engine module on the default joint nodes instead, when such a mechanism is in place. At that point we'll likely find ourselves with the same problem of not being able to access them from statically compiled languages, but hopefully we can come up with some kind of solution for it.


refactor server.py move db parts to other modules

the server code should not have itselfs calls of the database functions.
These parts should be moved to e.g. the file_manager

I want to work on this issue please assign me


Returning an empty hash in a HTTP delete results in an exception

After upgrading to Grape >= 0.19.1, the default status code for DELETE is now 204 instead of 200.
When returning a response which is not empty (for example {'key'=>'value'}, a 200 is returned with the correct response body.
When a non empty hash is returned on webrick (default development rails server) this goes well: the hash is returned. However, if an empty hash is provided {}, it results in an exception:
[2018-07-10 15:38:03] ERROR TypeError: no implicit conversion of Hash into String
	/Users/bas.janssen/.rvm/gems/ruby-2.4.4@rails4/gems/rack-1.6.10/lib/rack/handler/webrick.rb:113:in `block in service'
	/Users/bas.janssen/.rvm/gems/ruby-2.4.4@rails4/gems/rack-1.6.10/lib/rack/body_proxy.rb:31:in `each'
	/Users/bas.janssen/.rvm/gems/ruby-2.4.4@rails4/gems/rack-1.6.10/lib/rack/body_proxy.rb:31:in `each'
	/Users/bas.janssen/.rvm/gems/ruby-2.4.4@rails4/gems/rack-1.6.10/lib/rack/body_proxy.rb:31:in `each'
	/Users/bas.janssen/.rvm/gems/ruby-2.4.4@rails4/gems/rack-1.6.10/lib/rack/body_proxy.rb:31:in `each'
	/Users/bas.janssen/.rvm/gems/ruby-2.4.4@rails4/gems/rack-1.6.10/lib/rack/body_proxy.rb:31:in `each'
	/Users/bas.janssen/.rvm/gems/ruby-2.4.4@rails4/gems/rack-1.6.10/lib/rack/body_proxy.rb:31:in `each'
	/Users/bas.janssen/.rvm/gems/ruby-2.4.4@rails4/gems/rack-1.6.10/lib/rack/body_proxy.rb:31:in `each'
	/Users/bas.janssen/.rvm/gems/ruby-2.4.4@rails4/gems/rack-1.6.10/lib/rack/handler/webrick.rb:112:in `service'
	/Users/bas.janssen/.rvm/rubies/ruby-2.4.4/lib/ruby/2.4.0/webrick/httpserver.rb:140:in `service'
	/Users/bas.janssen/.rvm/rubies/ruby-2.4.4/lib/ruby/2.4.0/webrick/httpserver.rb:96:in `run'
	/Users/bas.janssen/.rvm/rubies/ruby-2.4.4/lib/ruby/2.4.0/webrick/server.rb:308:in `block in start_thread'

with the following output (http 500):

        <TITLE>Internal Server Error</TITLE>

Internal Server Error

    no implicit conversion of Hash into String

        <ADDRESS>
     WEBrick/1.3.1 (Ruby/2.4.4/2018-03-28) at
     localhost:3005
    </ADDRESS>

Adding an explicit status of 200 solves this:
delete do
  status 200
  {}
end

Is this issue known, can someone confirm this and can it be solved in some way?

When investigating in the grape code, I see that inside_route wil check for a value in the body using .present? This will return false if an empty hash is used. I'm not sure if this should be the case. Returning an empty json object is done returning {}. The body is clearly not empty: it returns a valid json object. However: the grape implementation would regard this as no content -> 204.

Interesting, I think this is a bug. Try writing a test for it, maybe a fix?

I love to get some feedback. As a grape rookie, I hope I'm on the right track.


Maintenance for long running clusters

Currently Arroyo stores all metadata for checkpoints in checkpoints table, overtime it grows upto a significant size which may impact performance.

Immediate solve (by @mwylde ) is to run this query manually ->
DELETE FROM checkpoints
WHERE checkpoints.id != (
  SELECT id FROM checkpoints
  WHERE job_id = '{{ JOB_ID }}'
  ORDER BY finish_time DESC
  LIMIT 1
) AND job_id='{{ JOB_ID }}';

Just merged the fix


Feature: Visualise skipped tests

It would be great if skipped tests were displayed in the output.
(In much the same was as QUnit does..)

Either by a different colour, or by a count at the end of the suite.

+1


feat: ray orchestrator - add inference

Describe your changes

add inference step
add PVC
update docs

Preview

Checklist before requesting a review

[x] I updated CHANGELOG.MD with a description of my changes
[x] If the change was to a module, I ran the code validation script (scripts/validate.sh)
[x] If the change was to a module, I have added thorough tests
[x] If the change was to a module, I have added/updated the module's README.md
[x] If a module was added, I added a reference to the module to the repository's README.md
[x] I verified that my code deploys successfully using seedfarmer apply

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

AWS CodeBuild CI Report

CodeBuild project: AIOpsModuleTestsInfrastruct-doMLXEYsnmxr
Commit ID: a1de10a708e4d7e6b78e50132797991a0d56e082
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


MicroBitConfig has many fewer settings compared to DAL version

Maybe most of these have moved elsewhere?

@martinwork are there still outstanding bits of config that you need for compat, or are we okay to close this issue now? As it stands I think we have adequate compatibility.

OK to close


Added an option for a more generic observer time, and aligned with v0.2

Summary
Based from the discussion https://github.com/sigstore/sigstore-go/issues/44
Currently there is not possible to define a policy that either a SET or a signed timestamp should be used. This PR addresses that via the ObserverTimestampOptions. Also as v0.2 does prefer inclusion proofs over SET, this PR allows for option on using the SET or not, and when using the SET, the timestamp can be used during X.509 certificate verification.
Release Note
TBD

Documentation
N/A

Updated to match this PR: https://github.com/sigstore/sigstore-go/pull/51

As part of adding the ObserverTimestampOptions, I modified the default verification parameters to be more user-friendly. The default option is now to require one ObserverTimestamp (that is, one from a tlog or from a RFC3161), if a user would like to control this better they can override this. I think this makes the default options easier to reason about, and aligns with the example sigstore-go binary: https://github.com/sigstore/sigstore-go/blob/1195bd5938daaf53eb2c011608235880e8a8524c/cmd/sigstore-go/main.go#L59


Update customer-key-set-up.md

Updated licensing information based on SKU changes from Marketing. The changes to go live on April 1, 2020.

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks.

@brdesai  - please merge the commit on the copy/edit review done by JohanFreelancer9 or make the necessary changes on the PR following the suggestions made. Thank you.

Suggested changes have been committed.

@KCCross, @JohanFreelancer9  Do you want me to close the pull request or are you going to do it.

@KCCross, @JohanFreelancer9  I'd to make one more commit to update the list of supported SKUs based on the discussion with PMM.

@KCCross , @JohanFreelancer9 The changes have been made, take a look and do the needful to merge the changes. Thanks.

@KCCross - PR has been copy edited and is ready for final review.
Thank you.
cc: @kenwith

I'm concerned at how these did not make it live after the PR was merged. Please verify the accuracy against the new service description release in June.


feat(Search): re-implement Search component

Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Re-implement the Search component, fixing existing bugs and adding features

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


remove beta warning from c++ client

🚀 Deployed on https://6658b963c001c34d94e4393f--cozy-fox-0defec.netlify.app