BUG: cve show -r --raw output is not formatted accooring to the schema

Command:
cve show -r --raw
Expected:
{
    "cveMetadata" : {
        "cve_id": "CVE-2022-36249",
        "cve_year": "2022",
        "owning_cna": "DIVD",
        "requested_by": {
            "cna": "DIVD",
            "user"<EMAIL_ADDRESS>        },
        "reserved": "2022-11-07T11:55:12.047Z",
        "state": "PUBLISHED",
        "time": {
            "created": "2022-11-07T11:55:12.049Z",
            "modified": "2022-11-07T16:03:20.456Z"
        }
    },
    "containers": {
        "cna": {
            "affected": [
                {
<snip>

Got:
[
    {
        "cve_id": "CVE-2022-36249",
        "cve_year": "2022",
        "owning_cna": "DIVD",
        "requested_by": {
            "cna": "DIVD",
            "user"<EMAIL_ADDRESS>        },
        "reserved": "2022-11-07T11:55:12.047Z",
        "state": "PUBLISHED",
        "time": {
            "created": "2022-11-07T11:55:12.049Z",
            "modified": "2022-11-07T16:03:20.456Z"
        }
    },
    {
        "containers": {
            "cna": {
                "affected": [
                    {
<snip>

@MrSeccubus That's because it's the output of two different API calls, one to get the object representing the CVE ID reservation, and the other is the CVE record object. We chose to put them in as two items of an array to still have a valid JSON object as a result.
The CVE record object (the second item in the array) is a full record that is valid against the 5.0 schema; you'll notice it has the cveMetadata object within itself. The CVE ID reservation object is not the part of the schema under cveMetadata. In the actual schema, that object looks like this:
"cveMetadata": {
            "assignerOrgId": "53f830b8-0a3f-465b-8143-3b8a9948e749",
            "assignerShortName": "redhat",
            "cveId": "CVE-2021-20311",
            "datePublished": "2021-05-11T22:30:47",
            "dateReserved": "2020-12-17T00:00:00",
            "dateUpdated": "2021-05-11T22:30:47",
            "state": "PUBLISHED"
        },

which is different from what the API returns:
{
        "cve_id": "CVE-2022-36249",
        "cve_year": "2022",
        "owning_cna": "TEST",
        "requested_by": {
            "cna": "TEST",
            "user": "TEST_USER"
        },
        "reserved": "2022-11-07T11:55:12.047Z",
        "state": "PUBLISHED",
        "time": {
            "created": "2022-11-07T11:55:12.049Z",
            "modified": "2022-11-07T16:03:20.456Z"
        }
    }

If you're parsing the JSON output, and want the record only, you could simply use the second item in the array. If you have any ideas on how to improve this, do let us know :wink:.

Damn! I see what you mean and my PR #45  then doesn't fix this either :-(
I think the help test of cve show -h is misleading.
Options:
  -r, --show-record  Show full CVE record in JSON v5 format.
  --raw              Print response JSON.
  -h, --help         Show this message and exit.

It says that with -r it should return a full cve record.
But, if I take the output of cve show -r --raw CVE-2022-36249 and validate it against the schema, it simply doesn't validate because you are not showing the full record, you are showing an array with the full record and the data of the reservation.
In my opnion -r should show the full record and the full record only.
I have updated PR #45 to change this.

What I was looking for is a cve command to run that would return the full record to me so I could send it to a json file.
cve show -r --raw CVE-2022-36249 >CVE-2022-36249.json doesn't produce a json file with a cve record in it
cve show -r CVE-2022-36249 >CVE-2022-36249.json doesn't produce a valid json file with a cve record in it because it has this header
cve show -r CVE-2022-36249 |jq .[1]>CVE-2022-36249.json might do the trick, but it is not obvious from the docs that this is what you need to do.

Agreed, I guess showing the full record only when the option is specified is the less surprising and would make your first command work as you'd expect.


Type for numeric-string

Is your feature request related to a problem? Please describe.
It would be a Type\numeric_string() that asserts/coerces a string value down to numeric-string.
Describe the solution you'd like
Describe alternatives you've considered
I don't think you can implement the assertion with invariant().
Additional context
I'm converting from webmozart/assert and I don't think there is anything close to Assert::numeric() currently available in psl.

Okay, I was wrong, it's possible to implement with invariant :facepalm:


add parse docker stats to support job exporter

parse docker stats cmd and extract the info for later job exporter to use

Pull Request Test Coverage Report for Build 695

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+14.3%) to 62.156%

Totals

Change from base Build 680:
14.3%

Covered Lines:
964

Relevant Lines:
1546

💛  - Coveralls

Pull Request Test Coverage Report for Build 695

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+14.3%) to 62.156%

Totals

Change from base Build 680:
14.3%

Covered Lines:
964

Relevant Lines:
1546

💛  - Coveralls

Pull Request Test Coverage Report for Build 695

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+14.3%) to 62.156%

Totals

Change from base Build 680:
14.3%

Covered Lines:
964

Relevant Lines:
1546

💛  - Coveralls


fix: handle keyerror during backup settings

Keyerror when ["AdditionalLaunchArguments"] is missing during backup settings. Proposing that it should just pass since you can't do anything about it at that moment.

If you can put a Logger.warning saying that the botty failed to set the launch options and possibly tell the user how to solve the issue


Forcing the screen orientation to horizontal in full screen mode

Have you read the FAQ and checked for duplicate open issues?
Yes.
Is your feature request related to a problem? Please describe.

When clicking the full screen button on phone in vertical, the screen orientation remains in vertical so I've to enable the rotation on the device and rotate it to have a "real" full screen.
Describe the solution you'd like

If full screen on rotate is enabled, the player should switch the orientation to horizontal automatically when clicking the full screen button. Just the same way it happens when rotating the device. It was commented here once.
Describe alternatives you've considered

Additional context

That feature must have slipped between the cracks. Thanks for pointing this out!


Apply IS configuration changes to IS_AM,APIM

The following issues need to be applied in APIM 3.0.0. and IS as KM 5.9.0
https://github.com/wso2/product-is/issues/7017
https://github.com/wso2/product-is/issues/6403
https://github.com/wso2/product-is/issues/6652
https://github.com/wso2/product-is/issues/6484

closing issue and moving to https://github.com/wso2/product-apim/


fix: Update README.md code samples

Update README file to fix code samples in order to run them without issues.

Sorry for the late merge. I had been in vacation the last weeks.
Thanks for contributing!


Need Polymer.Base.unlisten to remove the event listener

Currently we have Polymer.Base.listen to add an event listener e.g. tap.  But we also need Polymer.Base.unlisten to remove the event listener.

This is needed for cases like in iron-selector which wants to default activateEvent to tap (https://github.com/PolymerElements/iron-selector/blob/master/iron-selectable.html#L64).  But user of iron-selector may choose to have activateEvent set to something else like down, up or ''.  We need a way to remove the default tap event.


How does this group radio groups?

If there is no name attribute how does this group radios?
I have these in a table and the ng-repeat is on the td.
But every radio button is checked. And they're not independent of each other.

    <pretty-radio label=false type="radio" ng-model="question.ScaleChoice" name="{{question.Question}}" ng-value="q.Value"></pretty-radio>

Why does every  element have a class of checked on the page?
Thanks

Figured this out. Needed to change ng-value to value.


Install from the source ask for KB binaries

Bug Report
Install from the source is asking for KB binaries:
$ make install
go install -gcflags "all=-trimpath=/Users/camilamacedo86/go/src/github.com/operator-framework" -asmflags "all=-trimpath=/Users/camilamacedo86/go/src/github.com/operator-framework" -ldflags " -X 'github.com/operator-framework/operator-sdk/internal/version.Version=v0.7.0+git' -X 'github.com/operator-framework/operator-sdk/internal/version.GitVersion=v0.7.0-1686-ge3005bfa-dirty' -X 'github.com/operator-framework/operator-sdk/internal/version.GitCommit=e3005bfa8677eadf5b3f34fd14275f8414c80fc8' -X 'github.com/operator-framework/operator-sdk/internal/version.KubernetesVersion=v1.21' -X 'github.com/operator-framework/operator-sdk/internal/version.ImageVersion=v1.13.0' "  ./cmd/{operator-sdk,ansible-operator,helm-operator}
unable to fetch checksum for requested version: unable fetch metadata for kubebuilder-tools-1.21.1-darwin-amd64.tar.gz -- got status "404 Not Found" from GCS

What did you do?
From a new/fresh local env:

Clone the SDK project
Run make install

What did you expect to see?
Build and install the Operator SDK from the source
What did you see instead? Under which circumstances?
It is asking for Kubebuilder binaries when seems that should not.

Ah yeah, this needs a small fix in Makefile. We were exporting KB assets for envtest setup since its no longer downloaded at the default location. This was causing KB assets to be downloaded even while building binaries.
#5336 closes this


fix: also display errors from componentFailures

What does this PR do?
Displays componentFailures that are not already captured with the file responses of the DeployResult.
What issues does this PR fix or reference?
@W-14470146@
https://github.com/forcedotcom/cli/issues/2561

QA:
used the gh issue's dreamhouse Flow example.
✅  see the error with this PR, was not able to without it.


COOPR-665: API endpoints should only return a single version

small comments, then lgtm

Looks like maven test passed according to Travis. Merging now.


Remove cargo warning about "no edition set"

Currently, when I run cargo run from the cpz directory, I get this warning:
warning: /homes/noamyr/sand/fuc/Cargo.toml: no edition set: defaulting to the 2015 edition while the latest is 2021

I understand that it comes from the lint package, which didn't define an edition.
Thanks for cpz and rmz! They already help me a lot.

Nice, thanks!


class / classname & other react formats

Why does a react module spit out html markup that doesn't fit the JSX scheme?
Aka it spits out "class" and not "className", images don't have else closing tags on base64.
Is there a way to enable this and why isn't it  on be default if its built for react?

The DOM nodes created by quill are not controlled by React

The DOM nodes created by quill are not controlled by React

So is there a way to convert it? Why is reeact quill a thing for react if it spits out invalid html for it? Like it just spams my console with errors. really confused as to why its made for react if what it produces is just gonna error on react pages.


Feature/event card

Closes #7

Looks good, missing the add to calendar button

I've added the calendar button, which is functional and will add events to your devices calendar app.


#309 - added better support for Maven Modules

Hi so I tried adding better Maven Modules support. It is my first Pull Request, so sorry for any problems there might be. In that case, just tell me and I will try to fix it...

There are two things. First I recommend to add a copyright header in the source code files and furthermore I would request you to squash your commits and make a commit message like:
Fixed #309 - Headline
 Optional description

and most genius would be to add some tests if you can?
Many thanks Ah...one more thing and entry in the ReleaseNotes.md would also be a good idea...

I already did remove the output in earlier commit. I will try to squash the commits and the rest things tomorrow.
I will also try to create some tests but I don't guarantee anything.

So I did everything except the tests, I have to learn Mockito a bit, so I will maybe add them later when I am able to get them working...


reasearch compression crates

title

sorted from most to least promising

https://crates.io/crates/miniz_oxide/0.8.2
https://crates.io/crates/flate2/1.0.35
https://crates.io/crates/deflate


Upgrade react three next

Created a new issue [Cosmic Platform] Returning to home breaks page #6 in GitHub

also fixes #6


update phpseclib

We just experienced problems with a client's order export using Xtento Sales Export module and it turns out they use the phpseclib library found in the lib/phpseclibrary.
The library bundled with Magento <IP_ADDRESS> is not fully PHP7 compatible it seems and overwriting it with the latest version found here solves the problem:
https://github.com/phpseclib/phpseclib/releases/tag/1.0.5
Could this be something you could add to the module?

It would be a bit too much to include the whole phpseclib, and especially because it solves problems with a 3rd party extension, not Magento core.
Updating phpseclib is, generally, a good idea, though. Just out of scope of this extension.

I guess it could be somehow solved if using composer to manage dependencies and to ensure that the composer autoloader gets called first. This way you could just composer require the latest (known to work with magento) version of phpseclib and let the Autolaoder take care.

@Blackskyliner , you are right - if you install a newer version of phpseclib using Composer, the autoloader will pick it up and everything should work.

Thanks for the tip, I'll check it out!


Debugger fails to launch if breakpoint set in assembly of Jni lib

OS: MacOS 11.6
VSCode version:  1.62.3
CodeLLDB version: v1.6.10
Compiler: android-ndk / clang / armeabi-v7a / SystemVersion22
Debuggee: an android native library
So I believe I actually solved the problem myself, but wanted to report it anyway..
I had been successfully launching and debugging the file I was debugging many times but then it abruptly stopped working (with a recreated error log below). Turns out the problem was that while I was debugging deep into the stack (past where I did not have the source so I had temporarily turned on "show dissassembly always" before stepping in further, I had tried setting a breakpoint inside a native JNI library. The name of the breakpoint as shown on the left hand side in my breakpoints list is @art::JNI::FindClass(_JNIEnv*, char const*) /. When that breakpoint is turned on, the debugger fails to launch (the little progress blue line in the run tab just keeps moving around forever), and produces the error log below; with it disabled, everything works again. Interestingly this does not seem to be a problem with other breakpoints in other disassembly-only areas.

Verbose log
(some non essential names redacted)
configuration: {
name: 'Remote launch calldirectly',
type: 'lldb',
request: 'launch',
justMyCode: false,
program: '${workspaceFolder}/build/example/calldirectly',
initCommands: [
'platform select remote-android',
'platform connect connect://0855555555:10086',
'settings set target.inherit-env false',
'file /cache/calldirectly',
'b main'
],
env: {
PATH: '/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin',
LD_LIBRARY_PATH: '/cache:/data/user/0/something/lib:/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin',
ANDROID_DATA: '/data',
SECONDARY_STORAGE: '/storage/sdcard1',
LOOP_MOUNTPOINT: '/mnt/obb',
ANDROID_ROOT: '/system',
ANDROID_BOOTLOGO: '1',
ANDROID_ASSETS: '/system/app',
ASEC_MOUNTPOINT: '/mnt/asec',
BOOTCLASSPATH: '/system/framework/core-libart.jar:/system/framework/conscrypt.jar:/system/framework/okhttp.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/telephony-common.jar:/system/framework/voip-common.jar:/system/framework/ims-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framework/apache-xml.jar:/system/framework/qcmediaplayer.jar:/system/framework/WfdCommon.jar:/system/framework/oem-services.jar:/system/framework/org.codeaurora.Performance.jar:/system/framework/vcard.jar:/system/framework/tcmiface.jar:/system/framework/com.qrd.plugin.feature_query.jar:/data/app/something/base.apk',
EMULATED_STORAGE_TARGET: '/storage/emulated',
ANDROID_SOCKET_adbd: '10',
EXTERNAL_STORAGE: '/storage/emulated/legacy',
ANDROID_STORAGE: '/storage',
SYSTEMSERVERCLASSPATH: '/system/framework/services.jar:/system/framework/ethernet-service.jar:/system/framework/wifi-service.jar:/data/app/something/base.apk',
ANDROID_PROPERTY_WORKSPACE: '8,0',
EMULATED_STORAGE_SOURCE: '/mnt/shell/emulated'
},
__configurationTarget: 5,
relativePathBase: '/Users/ysaxon/Desktop/folder'
}
liblldb: /Users/ysaxon/.vscode/extensions/vadimcn.vscode-lldb-1.6.10/lldb/lib/liblldb.dylib
environment: { RUST_BACKTRACE: 'FULL' }
params: { evaluateForHovers: true, commandCompletions: true }
Listening on port 57063
[2021-11-30T15:50:24.736Z DEBUG codelldb] New debug session
INFO(Python) 10:50:25 formatters: Initializing
INFO(Python) 10:50:25 formatters.rust: Initializing
[2021-11-30T15:50:25.426Z DEBUG codelldb::dap_codec] --> {"command":"initialize","arguments":{"clientID":"vscode","clientName":"Visual Studio Code","adapterID":"lldb","pathFormat":"path","linesStartAt1":true,"columnsStartAt1":true,"supportsVariableType":true,"supportsVariablePaging":true,"supportsRunInTerminalRequest":true,"locale":"en-us","supportsProgressReporting":true,"supportsInvalidatedEvent":true,"supportsMemoryReferences":true},"type":"request","seq":1}
[2021-11-30T15:50:25.427Z DEBUG codelldb::dap_codec] <-- {"type":"response","request_seq":1,"success":true,"command":"initialize","body":{"exceptionBreakpointFilters":[{"default":true,"filter":"cpp_throw","label":"C++: on throw"},{"default":false,"filter":"cpp_catch","label":"C++: on catch"}],"supportTerminateDebuggee":true,"supportsCancelRequest":true,"supportsCompletionsRequest":true,"supportsConditionalBreakpoints":true,"supportsConfigurationDoneRequest":true,"supportsDataBreakpoints":true,"supportsDelayedStackTraceLoading":true,"supportsEvaluateForHovers":true,"supportsFunctionBreakpoints":true,"supportsGotoTargetsRequest":true,"supportsHitConditionalBreakpoints":true,"supportsLogPoints":true,"supportsReadMemoryRequest":true,"supportsRestartFrame":true,"supportsSetVariable":true}}
[2021-11-30T15:50:25.448Z DEBUG codelldb::dap_codec] --> {"command":"launch","arguments":{"name":"Remote launch calldirectly","type":"lldb","request":"launch","justMyCode":false,"program":"/Users/ysaxon/Desktop/folder/build/example/calldirectly","initCommands":["platform select remote-android","platform connect connect://0855555555:10086","settings set target.inherit-env false","file /cache/calldirectly","b main"],"env":{"PATH":"/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin","LD_LIBRARY_PATH":"/cache:/data/user/0/something/lib:/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin","ANDROID_DATA":"/data","SECONDARY_STORAGE":"/storage/sdcard1","LOOP_MOUNTPOINT":"/mnt/obb","ANDROID_ROOT":"/system","ANDROID_BOOTLOGO":"1","ANDROID_ASSETS":"/system/app","ASEC_MOUNTPOINT":"/mnt/asec","BOOTCLASSPATH":"/system/framework/core-libart.jar:/system/framework/conscrypt.jar:/system/framework/okhttp.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/telephony-common.jar:/system/framework/voip-common.jar:/system/framework/ims-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framework/apache-xml.jar:/system/framework/qcmediaplayer.jar:/system/framework/WfdCommon.jar:/system/framework/oem-services.jar:/system/framework/org.codeaurora.Performance.jar:/system/framework/vcard.jar:/system/framework/tcmiface.jar:/system/framework/com.qrd.plugin.feature_query.jar:/data/app/something/base.apk","EMULATED_STORAGE_TARGET":"/storage/emulated","ANDROID_SOCKET_adbd":"10","EXTERNAL_STORAGE":"/storage/emulated/legacy","ANDROID_STORAGE":"/storage","SYSTEMSERVERCLASSPATH":"/system/framework/services.jar:/system/framework/ethernet-service.jar:/system/framework/wifi-service.jar:/data/app/something/base.apk","ANDROID_PROPERTY_WORKSPACE":"8,0","EMULATED_STORAGE_SOURCE":"/mnt/shell/emulated"},"__configurationTarget":5,"relativePathBase":"/Users/ysaxon/Desktop/folder","_adapterSettings":{"displayFormat":"auto","showDisassembly":"auto","dereferencePointers":true,"suppressMissingSourceFiles":true,"evaluationTimeout":5,"consoleMode":"commands","sourceLanguages":null,"terminalPromptClear":null,"evaluateForHovers":true,"commandCompletions":true,"reproducer":false},"__sessionId":"63e76b9a-3aa3-463b-92cd-bfd68e0d5060"},"type":"request","seq":2}
[2021-11-30T15:50:25.449Z DEBUG codelldb::debug_session] platform select remote-android -> SuccessFinishResult, Error:  Success
Output Message:
Platform: remote-android
Connected: no
[2021-11-30T15:50:25.450Z DEBUG codelldb::dap_codec] <-- {"type":"event","seq":1,"event":"capabilities","body":{"capabilities":{"exceptionBreakpointFilters":[{"default":true,"filter":"cpp_throw","label":"C++: on throw"},{"default":false,"filter":"cpp_catch","label":"C++: on catch"}],"supportTerminateDebuggee":true,"supportsCancelRequest":true,"supportsCompletionsRequest":true,"supportsConditionalBreakpoints":true,"supportsConfigurationDoneRequest":true,"supportsDataBreakpoints":true,"supportsDelayedStackTraceLoading":true,"supportsEvaluateForHovers":true,"supportsFunctionBreakpoints":true,"supportsGotoTargetsRequest":true,"supportsHitConditionalBreakpoints":true,"supportsLogPoints":true,"supportsReadMemoryRequest":true,"supportsRestartFrame":true,"supportsSetVariable":true}}}
[2021-11-30T15:50:25.450Z DEBUG codelldb::dap_codec] <-- {"type":"event","seq":2,"event":"output","body":{"output":"Executing script: initCommands\n"}}
[2021-11-30T15:50:25.450Z DEBUG codelldb::dap_codec] <-- {"type":"event","seq":3,"event":"output","body":{"output":"  Platform: remote-android\n Connected: no\n\n"}}
[2021-11-30T15:50:25.498Z DEBUG codelldb::debug_session] platform connect connect://0855555555:10086 -> SuccessFinishResult, Error:  Success
Output Message:
Platform: remote-android
Triple: arm-unknown-linux-android
OS Version: 22 (3.10.49)
Hostname: localhost
Connected: yes
WorkingDir: /cache
Kernel: #1 SMP PREEMPT Fri Aug 20 11:52:15 HKT 2021
[2021-11-30T15:50:25.498Z DEBUG codelldb::debug_session] settings set target.inherit-env false -> SuccessFinishResult, Error:  Success
[2021-11-30T15:50:25.499Z DEBUG codelldb::dap_codec] <-- {"type":"event","seq":4,"event":"output","body":{"output":"  Platform: remote-android\n    Triple: arm-unknown-linux-android\nOS Version: 22 (3.10.49)\n  Hostname: localhost\n Connected: yes\nWorkingDir: /cache\n    Kernel: #1 SMP PREEMPT Fri Aug 20 11:52:15 HKT 2021\n\n"}}
[2021-11-30T15:50:25.754Z DEBUG codelldb::debug_session] file /cache/calldirectly -> SuccessFinishNoResult, Error:  Success
Output Message:
Current executable set to '/cache/calldirectly' (arm).
[2021-11-30T15:50:25.754Z DEBUG codelldb::dap_codec] <-- {"type":"event","seq":5,"event":"output","body":{"output":"Current executable set to '/cache/calldirectly' (arm).\n\n"}}
[2021-11-30T15:50:25.755Z DEBUG codelldb::debug_session] b main -> SuccessFinishResult, Error:  Success
Output Message:
Breakpoint 1: where = calldirectly`main + 12 at calldirectly.c:181:5, address = 0x00008224
[2021-11-30T15:50:25.755Z DEBUG codelldb::dap_codec] <-- {"type":"event","seq":6,"event":"output","body":{"output":"Breakpoint 1: where = calldirectlymain + 12 at calldirectly.c:181:5, address = 0x00008224\n\n"}} [2021-11-30T15:50:25.763Z DEBUG codelldb::dap_codec] <-- {"type":"event","seq":7,"event":"initialized"} [2021-11-30T15:50:25.769Z DEBUG codelldb::debug_session] Debug event: 0x7ff70be943c8 Event: broadcaster = 0x7ff70d31c040 (lldb.target), type = 0x00000002 (modules-loaded), data = {calldirectly} [2021-11-30T15:50:25.770Z DEBUG codelldb::debug_session] Debug event: 0x7ff70bfff7a8 Event: broadcaster = 0x7ff70d31c040 (lldb.target), type = 0x00000002 (modules-loaded), data = {libart.so, libm.so, libunwind.so, libdl.so, libc.so, libbacktrace_libc++.so, libc++.so, libcutils.so, liblog.so, libnativebridge.so, libnativehelper.so, libselinux.so, libsigchain.so, libutils.so, libstdc++.so, libgccdemangle.so, libunwind-ptrace.so, libstlport.so, libpcre.so, libbacktrace.so} [2021-11-30T15:50:25.771Z DEBUG codelldb::debug_session] Debug event: 0x7ff70bd6ce78 Event: broadcaster = 0x7ff70d31c040 (lldb.target), type = 0x00000001 (breakpoint-changed), data = {} [2021-11-30T15:50:25.771Z DEBUG codelldb::debug_session] Debug event: 0x7ff70bc4bca8 Event: broadcaster = 0x7ff70c283240 (lldb.target), type = 0x00000002 (modules-loaded), data = {calldirectly} [2021-11-30T15:50:25.773Z DEBUG codelldb::dap_codec] <-- {"type":"event","seq":8,"event":"module","body":{"module":{"addressRange":"FFFFFFFFFFFFFFFF","id":"FFFFFFFFFFFFFFFF","name":"calldirectly","path":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/5C1305A0/calldirectly","symbolFilePath":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/5C1305A0/calldirectly","symbolStatus":"Symbols loaded."},"reason":"new"}} [2021-11-30T15:50:25.773Z DEBUG codelldb::dap_codec] <-- {"type":"event","seq":9,"event":"module","body":{"module":{"addressRange":"FFFFFFFFFFFFFFFF","id":"FFFFFFFFFFFFFFFF","name":"libart.so","path":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/1C726E1B/libart.so","symbolFilePath":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/1C726E1B/libart.so","symbolStatus":"Symbols loaded."},"reason":"new"}} [2021-11-30T15:50:25.773Z DEBUG codelldb::dap_codec] <-- {"type":"event","seq":10,"event":"module","body":{"module":{"addressRange":"FFFFFFFFFFFFFFFF","id":"FFFFFFFFFFFFFFFF","name":"libm.so","path":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/1B5EC265/libm.so","symbolFilePath":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/1B5EC265/libm.so","symbolStatus":"Symbols loaded."},"reason":"new"}} [2021-11-30T15:50:25.773Z DEBUG codelldb::dap_codec] <-- {"type":"event","seq":11,"event":"module","body":{"module":{"addressRange":"FFFFFFFFFFFFFFFF","id":"FFFFFFFFFFFFFFFF","name":"libunwind.so","path":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/7A0D6A1E/libunwind.so","symbolFilePath":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/7A0D6A1E/libunwind.so","symbolStatus":"Symbols loaded."},"reason":"new"}} [2021-11-30T15:50:25.773Z DEBUG codelldb::dap_codec] <-- {"type":"event","seq":12,"event":"module","body":{"module":{"addressRange":"FFFFFFFFFFFFFFFF","id":"FFFFFFFFFFFFFFFF","name":"libdl.so","path":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/9241C64E/libdl.so","symbolFilePath":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/9241C64E/libdl.so","symbolStatus":"Symbols loaded."},"reason":"new"}} [2021-11-30T15:50:25.773Z DEBUG codelldb::dap_codec] <-- {"type":"event","seq":13,"event":"module","body":{"module":{"addressRange":"FFFFFFFFFFFFFFFF","id":"FFFFFFFFFFFFFFFF","name":"libc.so","path":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/090C57D2/libc.so","symbolFilePath":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/090C57D2/libc.so","symbolStatus":"Symbols loaded."},"reason":"new"}} [2021-11-30T15:50:25.773Z DEBUG codelldb::dap_codec] <-- {"type":"event","seq":14,"event":"module","body":{"module":{"addressRange":"FFFFFFFFFFFFFFFF","id":"FFFFFFFFFFFFFFFF","name":"libbacktrace_libc++.so","path":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/353A1506/libbacktrace_libc++.so","symbolFilePath":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/353A1506/libbacktrace_libc++.so","symbolStatus":"Symbols loaded."},"reason":"new"}} [2021-11-30T15:50:25.773Z DEBUG codelldb::dap_codec] <-- {"type":"event","seq":15,"event":"module","body":{"module":{"addressRange":"FFFFFFFFFFFFFFFF","id":"FFFFFFFFFFFFFFFF","name":"libc++.so","path":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/0970BBE1/libc++.so","symbolFilePath":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/0970BBE1/libc++.so","symbolStatus":"Symbols loaded."},"reason":"new"}} [2021-11-30T15:50:25.773Z DEBUG codelldb::dap_codec] <-- {"type":"event","seq":16,"event":"module","body":{"module":{"addressRange":"FFFFFFFFFFFFFFFF","id":"FFFFFFFFFFFFFFFF","name":"libcutils.so","path":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/7A7C7462/libcutils.so","symbolFilePath":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/7A7C7462/libcutils.so","symbolStatus":"Symbols loaded."},"reason":"new"}} [2021-11-30T15:50:25.773Z DEBUG codelldb::dap_codec] <-- {"type":"event","seq":17,"event":"module","body":{"module":{"addressRange":"FFFFFFFFFFFFFFFF","id":"FFFFFFFFFFFFFFFF","name":"liblog.so","path":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/39FD59FD/liblog.so","symbolFilePath":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/39FD59FD/liblog.so","symbolStatus":"Symbols loaded."},"reason":"new"}} [2021-11-30T15:50:25.773Z DEBUG codelldb::dap_codec] <-- {"type":"event","seq":18,"event":"module","body":{"module":{"addressRange":"FFFFFFFFFFFFFFFF","id":"FFFFFFFFFFFFFFFF","name":"libnativebridge.so","path":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/FAAFCD5C/libnativebridge.so","symbolFilePath":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/FAAFCD5C/libnativebridge.so","symbolStatus":"Symbols loaded."},"reason":"new"}} [2021-11-30T15:50:25.773Z DEBUG codelldb::dap_codec] <-- {"type":"event","seq":19,"event":"module","body":{"module":{"addressRange":"FFFFFFFFFFFFFFFF","id":"FFFFFFFFFFFFFFFF","name":"libnativehelper.so","path":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/A71700C5/libnativehelper.so","symbolFilePath":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/A71700C5/libnativehelper.so","symbolStatus":"Symbols loaded."},"reason":"new"}} [2021-11-30T15:50:25.773Z DEBUG codelldb::dap_codec] <-- {"type":"event","seq":20,"event":"module","body":{"module":{"addressRange":"FFFFFFFFFFFFFFFF","id":"FFFFFFFFFFFFFFFF","name":"libselinux.so","path":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/FD7617A9/libselinux.so","symbolFilePath":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/FD7617A9/libselinux.so","symbolStatus":"Symbols loaded."},"reason":"new"}} [2021-11-30T15:50:25.773Z DEBUG codelldb::dap_codec] <-- {"type":"event","seq":21,"event":"module","body":{"module":{"addressRange":"FFFFFFFFFFFFFFFF","id":"FFFFFFFFFFFFFFFF","name":"libsigchain.so","path":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/72E106B1/libsigchain.so","symbolFilePath":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/72E106B1/libsigchain.so","symbolStatus":"Symbols loaded."},"reason":"new"}} [2021-11-30T15:50:25.773Z DEBUG codelldb::dap_codec] <-- {"type":"event","seq":22,"event":"module","body":{"module":{"addressRange":"FFFFFFFFFFFFFFFF","id":"FFFFFFFFFFFFFFFF","name":"libutils.so","path":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/D1E8E322/libutils.so","symbolFilePath":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/D1E8E322/libutils.so","symbolStatus":"Symbols loaded."},"reason":"new"}} [2021-11-30T15:50:25.773Z DEBUG codelldb::dap_codec] <-- {"type":"event","seq":23,"event":"module","body":{"module":{"addressRange":"FFFFFFFFFFFFFFFF","id":"FFFFFFFFFFFFFFFF","name":"libstdc++.so","path":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/76988E7D/libstdc++.so","symbolFilePath":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/76988E7D/libstdc++.so","symbolStatus":"Symbols loaded."},"reason":"new"}} [2021-11-30T15:50:25.773Z DEBUG codelldb::dap_codec] <-- {"type":"event","seq":24,"event":"module","body":{"module":{"addressRange":"FFFFFFFFFFFFFFFF","id":"FFFFFFFFFFFFFFFF","name":"libgccdemangle.so","path":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/4FAE932E/libgccdemangle.so","symbolFilePath":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/4FAE932E/libgccdemangle.so","symbolStatus":"Symbols loaded."},"reason":"new"}} [2021-11-30T15:50:25.773Z DEBUG codelldb::dap_codec] <-- {"type":"event","seq":25,"event":"module","body":{"module":{"addressRange":"FFFFFFFFFFFFFFFF","id":"FFFFFFFFFFFFFFFF","name":"libunwind-ptrace.so","path":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/BEA4F862/libunwind-ptrace.so","symbolFilePath":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/BEA4F862/libunwind-ptrace.so","symbolStatus":"Symbols loaded."},"reason":"new"}} [2021-11-30T15:50:25.773Z DEBUG codelldb::dap_codec] <-- {"type":"event","seq":26,"event":"module","body":{"module":{"addressRange":"FFFFFFFFFFFFFFFF","id":"FFFFFFFFFFFFFFFF","name":"libstlport.so","path":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/197831D0/libstlport.so","symbolFilePath":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/197831D0/libstlport.so","symbolStatus":"Symbols loaded."},"reason":"new"}} [2021-11-30T15:50:25.773Z DEBUG codelldb::dap_codec] <-- {"type":"event","seq":27,"event":"module","body":{"module":{"addressRange":"FFFFFFFFFFFFFFFF","id":"FFFFFFFFFFFFFFFF","name":"libpcre.so","path":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/00C88DAB/libpcre.so","symbolFilePath":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/00C88DAB/libpcre.so","symbolStatus":"Symbols loaded."},"reason":"new"}} [2021-11-30T15:50:25.773Z DEBUG codelldb::dap_codec] <-- {"type":"event","seq":28,"event":"module","body":{"module":{"addressRange":"FFFFFFFFFFFFFFFF","id":"FFFFFFFFFFFFFFFF","name":"libbacktrace.so","path":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/F9804682/libbacktrace.so","symbolFilePath":"/Users/ysaxon/.lldb/module_cache/remote-android/.cache/F9804682/libbacktrace.so","symbolStatus":"Symbols loaded."},"reason":"new"}} [2021-11-30T15:50:25.773Z DEBUG codelldb::dap_codec] <-- {"type":"event","seq":29,"event":"breakpoint","body":{"breakpoint":{"id":1,"line":181,"message":"Resolved locations: 0","source":{"name":"calldirectly.c","path":"/path/calldirectly.c"},"verified":true},"reason":"new"}} [2021-11-30T15:50:25.773Z DEBUG codelldb::dap_codec] <-- {"type":"event","seq":30,"event":"module","body":{"module":{"addressRange":"FFFFFFFFFFFFFFFF","id":"FFFFFFFFFFFFFFFF","name":"calldirectly","path":"/Users/ysaxon/Desktop/folder/build/example/calldirectly","symbolFilePath":"/Users/ysaxon/Desktop/folder/build/example/calldirectly","symbolStatus":"Symbols loaded."},"reason":"new"}} [2021-11-30T15:50:25.776Z DEBUG codelldb::dap_codec] --> {"command":"setBreakpoints","arguments":{"source":{"name":"@art::JNI::FindClass(_JNIEnv*, char const*)","path":"@art::JNI::FindClass(_JNIEnv*, char const*)","sourceReference":1028,"adapterData":{"end":3068145000,"lineOffsets":[4,4,4,4,4,4,4,4,4,4,4,4,4,4,4,4,4,4,4,4,4,4,4,4,4,4,4,4,4,4,4,4],"start":3068144872}},"lines":[296],"breakpoints":[{"line":296}],"sourceModified":false},"type":"request","seq":3}  (breakpoints 4..12 omitted) thread '<unnamed>' panicked at 'index out of bounds: the len is 36 but the index is 296', adapter/src/debug_session/breakpoints.rs:188:27 stack backtrace:    0: _rust_begin_unwind    1: core::panicking::panic_fmt    2: core::panicking::panic_bounds_check    3: codelldb::debug_session::DebugSession::handle_request_args    4: codelldb::debug_session::DebugSession::handle_request    5: tokio::loom::std::unsafe_cell::UnsafeCell<T>::with_mut    6: tokio::runtime::task::core::CoreStage<T>::poll    7: tokio::runtime::task::harness::Harness<T,S>::poll    8: std::thread::local::LocalKey<T>::with    9: tokio::task::local::LocalSet::tick   10: <tokio::task::local::LocalSet as core::future::future::Future>::poll   11: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll   12: tokio::park::thread::CachedParkThread::block_on   13: tokio::runtime::thread_pool::ThreadPool::block_on   14: tokio::runtime::Runtime::block_on   15: _entry   16: codelldb::main note: Some details are omitted, run with RUST_BACKTRACE=full` for a verbose backtrace.

I have the same issue.
https://source.android.google.cn/devices/tech/debug/gdb?hl=zh-cn#vscode
the breakpoint set is not work.

@YSaxon thanks for the report, this part clearly needs to be coded more carefully.


Build netstandard2.1 + always build on master

Tests are still failing, but again; That's not in scope of this PR


Update an-introduction-to-recommendations-and-popular-items.md

Updated documentation for #498. Fixed various formatting/links.

@tseward - waiting to hear from @MikePlumleyMSFT and @Techwriter40 on whether they want the PS C:> in the PowerShell examples. If they want them removed let's spin up a project to get them removed through all examples for consistency.


[Marker.io] [tablet] orange dots are appearingon project tiles

Steps to reproduce:

go to projects page
2)notice the project tiles

Actual result: orange dots are shown
Expected result: it should not be shown for tablets devices

Reported by: vinod<EMAIL_ADDRESS>- Contact via Marker.io
Source URL: https://kensway.webflow.io/projects
Issue details: Open in Marker.io
Device typedesktopBrowserSafari 17.1Screen Size1024 x 1366OSOS X 10.15.7Viewport Size1024 x 1292Pixel Ratio@2x

🤖 Marker.io bot - 💬 Vinod commented:

it can be observed in portrait mode of some tablets (browserstack ipad12.9.2021, safari )or the landscape mode of some tablets.(ipad 6th gen, )
when my real tablet device was in landscape mode, issue was observed (below are the dimensions)
resolution: 7681024
viewport: 1024665
(apple ipad 6th gen, safari,ios: 17.3.1)
dots are still visible

Reply here


Additional shapes

First off, let me just say this looks awesome. Just discovered this via Twitter but love what I'm seeing. Great work!
One feature I think would be awesome would be additional shapes similar to what Google Drive's Drawing feature has. If I get some extra time I'll even try to add / contribute what I can.
Thanks!

This issue is too vague. If people want specific shapes, they should be created as individual tickets. I'll add a ticket for a polygon tool myself.


.vscodeignore

A .vscodeignore file should be added decrease the size of the distributed extension package.

I want to do this.

@kevinah95 Contributions are always welcome :D
I've updated the initial issue post with necessary information.


When you will release the code?

Hi, thanks for your interest in the code. However, this project was done at Meta AI and I have run into an issue with them regarding the code release. I expect to have an update by the 2nd week of December. I will get back to you around that time.

Hi, could you send an email to<EMAIL_ADDRESS>about this?


Bump to Scala 2.12.0-RC1

TODO: ImplicitsSpec is failing in Scala 2.12.0-RC1.

akka 2.4.x require Java 8

Hi @takezoe,
Thanks for this pull request. We are not ready to drop scala 2.10 support yet. We will only do so when 2.12 has been out for quite some time.
Regarding the test: we can easily disable the test for 2.12 or later by testing for the current version (given by util.Properties.versionNumberString).
Could you update your PR with this?
Kind regards,
Erik.

@erikvanoosten Thanks. I fixed testcase to turn off by tag and restored Scala 2.10 build.

@erikvanoosten Updated.

What is your opinion? Should we officially release for 2.12-RC1?

I hope that the 2.12.0-RC1 supported version will be released as SNAPSHOT for other libraries or frameworks which depend on metrics-scala. They (and also I) will be able to make progress migration to Scala 2.12 by using that SNAPSHOT version.
And after Scala 2.12 release, you should release for 2.12 as a fixed version.

Excellent!

I hope that the 2.12.0-RC1 supported version will be released as SNAPSHOT for other libraries or frameworks which depend on metrics-scala. They (and also I) will be able to make progress migration to Scala 2.12 by using that SNAPSHOT version.

We can also just release 3.5.5 for 2.12.0-R1, there is no need to mark it as a snapshot. Of course it won't have any support after 2.12 is out for real.

I released "nl.grons" %% "metrics-scala" % "3.5.5" and "nl.grons" %% "metrics-scala" % "3.5.5_a2.4" for scala 2.12.0-RC1.
Thanks @takezoe !


How to do custom assertions

How would one go about adding their own, project-local assertions to qunit-dom?
With QUnit, we can say
QUnit.assert.myAssertion = function() {...}

However, to be able to do that with an object returned from QUnit.dom(...), one would have to extend a DOMAssertions object or prototype. I couldn't seem to find where that is accessible.

custom assertions like that are currently not supported

Are there any plans to do that in the future?

we currently have no such plans. since you can already extend QUnit.assert I'm not sure that we'd necessarily need a way for extending the DOM assertions too. ultimately you would have to use a lot of private API in your custom DOM assertions and since it's private we wouldn't be able to give any stability guarantees anyway.

Thank you for your reply.

we currently have no such plans.
Understood.

since you can already extend QUnit.assert I'm not sure that we'd necessarily need a way for extending the DOM assertions too.
I wanted to do this because I am asserting some quality specifically about the element from querySelector(), which is usually this in your assertions. I'd imagine that I am not the only guy who wants to assert that the div.foo I am looking at has data-whatever set to a specific value while it also has class="my-whatever", and since that is hard to read, name it assert.dom(...).isCorrectWhatever()`; you know, project specific stuff.

Of course you can put that into QUnit.assert, like `assert.isCorrectWhatever(selector, message), but if you are going that far, then you can also put all DOM related assertions there.

assert.dom('x').hasClass('my-whatever')
assert.dom('x').hasAttribute('data-whatever', 'value')

you could make a helper function
function assertMyTwoThings(selector){
 assert.dom('x').hasClass('my-whatever')
 assert.dom('x').hasAttribute('data-whatever', 'value')
}

or
or you can extend QUnit.assert  as @Turbo87 mention
QUnit.extend(QUnit.assert, {
  customDom(selector) {
    return {
       twoThingsAtOnce(){
        //this is not the real way to do the assertion but it will work
         assert.dom(selector).hasClass('my-whatever')
         assert.dom(selector).hasAttribute('data-whatever', 'value')
      }
    }
  },
});

assert.customDom('x').twoThingsAtOnce()

i would just write both assertions but if you really want to do it in one call i recommend the helper function.

Thank you for your response. The problem isn't that I don't know how to write assertions.
The problem is that there are things I would have liked to assert on the node directly in a library- or project-specific manner, and I was baffled at the response that it's just not supported and there are no plans to do so.
Even a generic thing like
assert.dom(selector).satisfies(predicate, "that DOM node satisfies this predicate")

would have been useful. But if I am the only guy who wants extensible DOM assertions I can live with qunit-dom not supporting something like this.


Avogadro2 Plugin NOT Recognizing Imports

The code is crashing in Avogadro2 whenever I need to reference a function within the code base. While I am not sure of the EXACT error, I believe the error is that the function and/or package is not being found. I tried installing the package via the following:
git clone https://github.com/Dfilono/Molecule-Builder
cd Molecule-Builder
pip install .

This does not seem to make a difference. If I import the code as currently uploaded to the repo like the following:
import moleculeBuilder as MB

Avogadro2 recognizes this. However, if I import the code the following way:
from moleculeBuilder import drawMol, readWriteFiles, defaultParams

Avogadro2 no longer recognizes the plugin at all. I'm unsure if the import method makes a difference, however since the first method is not functioning I don't know if finding a way to switch to the second would solve the problem (since in theory they are the same).
I've also attempted this without the package being explicitly installed via pip, with the imports referencing just the local code itself. Unfortunately this has the same result.
The files being referenced in this error are plugin.json and fillBox.py

When you say "crashing" - the plugin doesn't run, or Avogadro GUI crashes?
I'm not enough of a Python expert to know why the two different import statements are working differently. I'd go with what works for now.

It would also help to know if there's any sort of error from the script.

Part of it turned out to be a package issue. My setup.py file and init.py files weren't entirely setup correctly. The script still isn't finishing so I am leaving the issue open, but I am investigating what the current issue is.


Compatible with React Native Web

💬 Question
Hi,
I am in love with this library, my question is can we use this library with REACT NATIVE WEB ?
UI Kitten and Eva version

Package
Version

@eva-design/eva

@ui-kitten/components

Hey @AtifShahzed
https://akveo.github.io/react-native-ui-kitten/docs/guides/running-on-the-web#running-on-the-web
TLDR
yes
If your problem is solved can you please close the issue?
It sparks joy for maintainers ✨


Problems with Initialization

Hello,
i downloaded the repository and created a new folder data inside. Here i put my files:

data.train.txt
data.dev.txt
data.test.txt

In the documentation it is written:

the conversion can be initiated with python data.py <data_dir>

When i perform python data.py data i always get "Data already exists" and without the argument "The path to stage1 source data directory with txt files is missing". Can you please tell me what is the preferred file and folder structure for the data files?
Thanks!

Now i removed some code in data.py and could call the function create_dev_test_train_split_and_vocabulary(path, True, TRAIN_FILE, DEV_FILE, TEST_FILE). It gives me back:

26.32% UNK-s in data/train
25.53% UNK-s in data/dev
25.53% UNK-s in data/test

My content is:
data/english.train.txt:

to be ,COMMA or not to be ,COMMA that is the question .PERIOD
hello ,COMMA how are you .PERIOD
hello ,COMMA how are you today ?QUESTIONMARK
hello ,COMMA can i help you ?QUESTIONMARK
i am fine ,COMMA thanks .PERIOD
what about you ?QUESTIONMARK
can i help you ?QUESTIONMARK
how can i help you ?QUESTIONMARK
do you need help ?QUESTIONMARK
where are you ?QUESTIONMARK
can you help me ?QUESTIONMARK
how was your day ?QUESTIONMARK
i like you .PERIOD
and what about you ?QUESTIONMARK
what is your name ?QUESTIONMARK
okay ,COMMA i have to go .PERIOD
i have to go now .PERIOD

data/english.dev.txt:

to be ,COMMA or not to be ,COMMA that is the question .PERIOD
hello ,COMMA how are you .PERIOD
hello ,COMMA how are you today ?QUESTIONMARK
hello ,COMMA can i help you ?QUESTIONMARK
i am fine ,COMMA thanks .PERIOD
what about you ?QUESTIONMARK
can i help you ?QUESTIONMARK
how can i help you ?QUESTIONMARK
do you need help ?QUESTIONMARK
where are you ?QUESTIONMARK

data/english.test.txt:

to be or not to be that is the question
hello how are you
hello how are you today
hello can i help you
i am fine thanks
what about you
can i help you
how can i help you
do you need help
where are you

I suppose the content or structure is not correct, because when i run python main.py english 256 0.02 i always get this error:

256 0.02 Model_english_h256_lr0.02.pcl
Building model...
Number of parameters is 2040580
WARNING (theano.tensor.blas): We did not found a dynamic library into the library_dir of the library we use for blas. If you use ATLAS, make sure to compile it with dynamics library.
Training...
Total number of training labels: 0
Total number of validation labels: 0
Traceback (most recent call last):
File "main.py", line 175, in
ppl = np.exp(total_neg_log_likelihood / total_num_output_samples)
ZeroDivisionError: division by zero

DATA_PATH = "../data" in data.py is the locaton of the final converted
dataset (in the form of pickled arrays).
If this directory already exists, then the cenversion is skipped (thus, in
case of failed conversion, the directory should be removed).
So these files:

data.train.txt
data.dev.txt
data.test.txt

...should be somewhere else (e.g. in ../raw_data).
Then python data.py ../raw_data should create the ../data directory with
the converted files.
Also, if you want to experiment with such a small dataset, then you might
want to reduce the minibatch size. Otherwise, when the number of samples is
less than the minibatch size, the script will create empty files (this is a
bug that should not be a problem in a realistic setting).
On 1 September 2016 at 17:00, Josef Hölzl<EMAIL_ADDRESS>wrote:

Now i removed some code in data.py and could call the function
create_dev_test_train_split_and_vocabulary(path, True, TRAIN_FILE,
DEV_FILE, TEST_FILE). It gives me back:
26.32% UNK-s in data/train
25.53% UNK-s in data/dev
25.53% UNK-s in data/test
My content is:
data/english.train.txt:
to be ,COMMA or not to be ,COMMA that is the question .PERIOD
hello ,COMMA how are you .PERIOD
hello ,COMMA how are you today ?QUESTIONMARK
hello ,COMMA can i help you ?QUESTIONMARK
i am fine ,COMMA thanks .PERIOD
what about you ?QUESTIONMARK
can i help you ?QUESTIONMARK
how can i help you ?QUESTIONMARK
do you need help ?QUESTIONMARK
where are you ?QUESTIONMARK
can you help me ?QUESTIONMARK
how was your day ?QUESTIONMARK
i like you .PERIOD
and what about you ?QUESTIONMARK
what is your name ?QUESTIONMARK
okay ,COMMA i have to go .PERIOD
i have to go now .PERIOD
data/english.dev.txt:
to be ,COMMA or not to be ,COMMA that is the question .PERIOD
hello ,COMMA how are you .PERIOD
hello ,COMMA how are you today ?QUESTIONMARK
hello ,COMMA can i help you ?QUESTIONMARK
i am fine ,COMMA thanks .PERIOD
what about you ?QUESTIONMARK
can i help you ?QUESTIONMARK
how can i help you ?QUESTIONMARK
do you need help ?QUESTIONMARK
where are you ?QUESTIONMARK
data/english.test.txt:
to be or not to be that is the question
hello how are you
hello how are you today
hello can i help you
i am fine thanks
what about you
can i help you
how can i help you
do you need help
where are you
I suppose the content or structure is not correct, because when i run python
main.py english 256 0.02 i always get this error:
256 0.02 Model_english_h256_lr0.02.pcl
Building model...
Number of parameters is 2040580
WARNING (theano.tensor.blas): We did not found a dynamic library into the
library_dir of the library we use for blas. If you use ATLAS, make sure to
compile it with dynamics library.
Training...
Total number of training labels: 0
Total number of validation labels: 0
Traceback (most recent call last):
File "main.py", line 175, in
ppl = np.exp(total_neg_log_likelihood / total_num_output_samples)
ZeroDivisionError: division by zero
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ottokart/punctuator2/issues/1#issuecomment-244087849,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJWV4DbYjR-4pvSjuaJKwcZKCbslo8_yks5qltqRgaJpZM4JyrRS
.

Thanks for clarification with the data folders!
I tried a minibatch size of 2,4, 8, 32 or 64, but i still get the error. The problem is:

Total number of training labels: 0
Total number of validation labels: 0

So the variable total_num_output_samples always stays 0, therefore in line 175 the division results in

ppl = np.exp(total_neg_log_likelihood / total_num_output_samples)
ZeroDivisionError: division by zero

Do i need more training, dev or test samples?

I also tried the raw_data provided in punctuator version 1, but still the same error.
In the function get_minibatch, there is something wrong with the dev dataset, because the loop
for subsequence in dataset:
is never started and therefore total_num_output_samples in line 173 is zero.

Sorry, I forgot there's another factor that plays a role. To get non-empty batches, all sources (train, dev and test) should contain at least MAX_SEQUENCE_LEN * MINIBATCH_SIZE words. MAX_SEQUENCE_LEN is defined in data.py and is 200 by default.

Okay i got it, thanks!


Update BRCA Exchange URLs

The VCI displays links to variants in the BRCA Exchange in the  "basic information" > "other resources" section of the VCI.  They are updating their system to key off CAR IDs. Please update the links accordingly.
From BRCA exchange:

Historically, the variants have been represented in the URLs via an internal ID (e.g. https://brcaexchange.org/variant/974221), where that ID was specific to the variant and the version of the variant data.  So the URL for the latest version of the variant was always changing.  Now we're using the ClinGen Allele Registry IDs as persistent variant URLs.  For example, https://brcaexchange.org/variant/CA025483 will always point to the latest version of that same variant (BRCA2 c.8168A>C) in this example.  The old URL system will continue to work, at least for a while, but whenever you have a free moment ("what's that!?"), please go ahead and update your links.

SP ticket: https://broadinstitute.atlassian.net/browse/CGSP-666

Closing this


WIP: script demonstrating piecewise-constant definition of coefficient

This is one way to do #89.

It's kind of one-dimensional but done with MeshTri as I wasn't sure that the facilities of MeshLine were the same and I was ultimately interesting myself in two-dimensional problems.

Maybe instead of https://github.com/kinnala/scikit-fem/blob/e52e0ee1fd4fe0c1cd81365bc9700c04eb58cfc0/docs/examples/insulated.py#L38
it would be nicer to specify something like
thermal_conductivity = {'wire': 101., 'insulation': 11.}

and read in the field_data from meshio.read which here contains
{'convection': array([3, 1]), 'wire': array([1, 2]), 'insulation': array([2, 2])}

and can be parsed with
{k: i for k, (i, d) in mesh.field_data.items() if d == mesh.dim()}

to give the mapping
{'wire': 1, 'insulation': 2}

I'll check this out and merge it tomorrow while trying to make the part where you modify mesh.py nicer.


set shared secret in webhook

When using a differnet jenkins url (see https://github.com/jenkinsci/ghprb-plugin/pull/223) the shared secret wasn't being set in the github URL.  As such any received requests came through with:
SEVERE: Request doesn't contain a signature. Check that github has a secret that should be attached
to the hook
This adds the secret. Not sure how this worked beforehand - maybe it wasn't tested with autocreated hooks?

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests

That would make sense to add the secret when auto creating the hook.


[Feature Request] Wire up new debug console icon to be configurable by extensions

originally opened here https://github.com/PowerShell/vscode-powershell/issues/2593

First time I'm seeing this little terminal icon... it looks like it's just a short cut to the Debug Console... This is not ideal because not every debugger uses the Debug Console some use an integrated terminal. This will be confusing for users.
I don't think there's any sort of configuration for us to say "hey jump to this terminal instead of the Debug Console". But it's brand new so I may be wrong.
Not using the Debug Console is a totally valid thing to do:

from https://microsoft.github.io/debug-adapter-protocol/overview

@TylerLeonhardt this is a valid point. Thus keeping this open as a feature request and we might change this in the future.
fyi @weinand

@TylerLeonhardt @isidorn some clarifications:

the "terminal icon" in the debug viewlet is nothing new. It was there since the beginning of time (when VS Code did not have an integrated terminal).
the icon represents the "debug console" and REPL, not a terminal.
the "debug console" is a mandatory part of the DAP adapter protocol. Output events go there and VS Code's generic REPL implementation uses it.
the "debug console" is surfaced in VS Code's extension API.
even when a Debug Adapter does not support to launch the target in the debug console, the REPL and the Output events will always end up there.

From this it is clear that the debug console and the icon representing it, is part of VS Code's debugger architecture. We are not planning to make this configurable.
But we are open to make it possible for extensions to add additional "icons"...

@weinand and @isidorn thanks for the quick reply.

the "terminal icon" in the debug viewlet is nothing new. It was there since the beginning of time (when VS Code did not even had an integrated terminal).

I'm aware of the terminal icon. We leverage it in the PowerShell extension in the satus bar:

which, when clicked, allows you to change the version that is used in the PowerShell Integrated Console (a terminal instance that appears in the VS Code Integrated Terminal).

the icon represents the "debug console" and REPL, not a terminal.

This might be true from the VS Code perspective, but that icon lives as a part of vscode-icons and it seems that extension authors are encouraged to reuse icons where it makes sense and in our case it makes sense to reuse the console icon for our needs.

the "debug console" is a mandatory part of the DAP adapter protocol.

Just some side feedback, this is not clear on https://microsoft.github.io/debug-adapter-protocol/overview
especially with the screenshot I posted from that link above that says you can launch in an integrated console instead of leveraging the debug console.
Anyway...
This feature request was just one suggestion.
Ideally, VS Code could have an icon that specifically represents the Debug Console a little better (adding a little bug on it or something... but this is probably where we bring @misolori in) rather than using the generic "console" icon especially since there's a debug console and an integrated terminal now.

But we are open to make it possible for extensions to add additional "icons"...

This is also something that would be ideal to help customers who are confused by the current experience.

Ideally, VS Code could have an icon that specifically represents the Debug Console a little better (adding a little bug on it or something... but this is probably where we bring @misolori in) rather than using the generic "console" icon especially since there's a debug console and an integrated terminal now.

Funny you mention that because we just went through an iteration and did for our the debug console in dynamic views (see https://github.com/microsoft/vscode/issues/92590#issuecomment-603291917) so we added this icon to our icon set:

So i wonder if it makes sense to update this icon in the debug viewlet as well?

@misolori you're awesome!

@misolori yes, as we aleardy discussed it makes sense to update the icon. I will do that right now - since that icon is just better.

Pushed via 56df825f84


typing: don't trigger typing indicator from weechat commands

Not sure if there's a better way to detect this, but doing things such as /buffer #foobar or /window up, etc, shouldn't be triggering Slack typing notifications since I'm just happily navigating around my terminal. So it seems like just ignoring if the input begins with / is reasonable.

Thanks for catching this, your approach looks reasonable enough to me.

Please release this. My coworker keeps annoying me :D

@mitsuhiko it is released, you need to pull the latest master code.


pre-allocate buffer for reading pixel data in readNativeFrames

addressing #161

Benchmarks looking nice
ReadNativeFrames/10x10,_10_frames,_1_sample/pixel-2    1.89µs ± 6%  2.32µs ± 3%  +23.20%  (p=0.000 n=8+8)
ReadNativeFrames/100x100,_10_frames,_1_sample/pixel-2  86.1µs ± 2%  83.9µs ± 2%   -2.56%  (p=0.002 n=7+7)
ReadNativeFrames/512x512,_10_frames,_1_sample/pixel-2  2.34ms ± 3%  1.65ms ± 6%  -29.48%  (p=0.000 n=8+8)
ReadNativeFrames/512x512,_10_frames,_5_sample/pixel-2   814ms ± 6%     4ms ± 7%  -99.51%  (p=0.000 n=8+8)
Parse/1.dcm-2                                          2.62ms ± 3%  1.33ms ± 2%  -49.34%  (p=0.000 n=8+8)
Parse/2.dcm-2                                          2.69ms ± 3%  1.32ms ± 4%  -50.96%  (p=0.001 n=7+7)
Parse/3.dcm-2                                          2.53ms ± 3%  1.19ms ± 2%  -52.91%  (p=0.000 n=8+8)
Parse/4.dcm-2                                           268ms ± 7%   116ms ± 3%  -56.75%  (p=0.000 n=8+8)
Parse/5.dcm-2                                          38.2ms ± 2%  17.7ms ± 2%  -53.79%  (p=0.000 n=7+8)

@suyashkumar appreciate your suggestions, implemented all of them I believe.

🎉  merged!


feat: tutorial examples

add playground examples for the different type of rules and features like variable mocking
add instruction dialog

Hey Chip. thanks for your feedback. You're right, the current examples are very basic and cover not all possibilities and features. They are more a starting point to show case the basic Idea of tutorials.
at this point I am somewhat dependent on contributions because I have worked little with custom rules and do not know all the possibilities. In principle, I would like to show more examples here or elaborate on the existing ones.

I will provide some suggestions today.

ConfigMap Context Examples

https://kyverno.io/policies/other/allowed_pod_priorities/allowed_pod_priorities/
https://main.kyverno.io/policies/other/exclude-namespaces-dynamically/exclude-namespaces-dynamically/

API Call Context Examples

https://main.kyverno.io/policies/other/restrict-pod-count-per-node/restrict-pod-count-per-node/ (good easy one)
https://main.kyverno.io/policies/other/restrict-ingress-host/restrict-ingress-host/
https://main.kyverno.io/policies/other/require-netpol/require-netpol/

UPDATE Examples

https://kyverno.io/policies/other/allowed_label_changes/allowed-label-changes/
https://main.kyverno.io/policies/other/block-updates-deletes/block-updates-deletes/ (Also uses context for clusterrole)

CONNECT Examples

https://main.kyverno.io/policies/other/block-pod-exec-by-namespace-label/block-pod-exec-by-namespace-label/

Subject Examples

https://main.kyverno.io/policies/other/check-serviceaccount/check-serviceaccount/

These should be good to get started.


Language Switcher Tag helper

What is the benefit of Tag helper over Partial view?

Hope we will discuss this in details after finishing the localization stuff

@thiennn I think using tag helpers over razor syntax make the code more readable.  (its not about tag helpers vs partial views)
Consider the following code snippet for rendering partial views using tag helpers instead of razor syntax
<partial name="a" for="model"/>

###OVER
@Html.Partial()

Tag Helpers simplifies the code and makes it more readable while HtmlHelpers (Razor) makes it hard to read and maintain.
Look at the following page to render partial view using both HtmlHelpers nd tag helpers
https://docs.microsoft.com/en-us/aspnet/core/mvc/views/tag-helpers/built-in/partial-tag-helper?view=aspnetcore-3.1
More about Tag Helpers VS Razor Syntax here:
https://docs.microsoft.com/en-us/aspnet/core/mvc/views/tag-helpers/intro?view=aspnetcore-3.1


Add model-centric tutorial

Description
This MR will include model-centric tutorial (see https://github.com/OpenMined/PySyft/blob/master/examples/tutorials/model-centric-fl/Part 01 - Create Plan.ipynb) in our repository, passing through our integration test

[x] Part 01
[x] Part 02

Affected Dependencies
None
How has this been tested?
I have included a test (actually, it is here where I found some issues, but all of them fixed :) )
Checklist

[x] I have followed the Contribution Guidelines and Code of Conduct
[x] I have commented my code following the OpenMined Styleguide
[x] I have labeled this PR with the relevant Type labels
[x] My changes are covered by tests

@vvmnnnkv please merge this when you're comfortable with the changes. We're just moving the model-centric tutorials from the PySyft repo to the PyGrid repo. Steps for you and your team after this PR is merged:

[ ] Remove the tutorials from PySyft
[ ] Change the links to the tutorials in syft.js
[ ] Change the links to the tutorials in KotlinSyft
[ ] Change the links to the tutorials in SwiftSyft


Rename autoreverses to reverses (Support Swift 4)

Previous function name conflicted with something ObjC.
Method 'autoreverses()' with Objective-C selector 'autoreverses' conflicts with getter for 'autoreverses' with the same Objective-C selector

So fast! 👌🏻🎉


"What's this?" should link to official docs

The "What's this?" link after the Strong mode checkbox links to https://github.com/dart-lang/dev_compiler/blob/master/STRONG_MODE.md. Instead it should probably link to something on www.dartlang.org, such as https://www.dartlang.org/guides/language/sound-faq#what-is-strong-mode.

Ah, excellent, thanks @kwalrath I'll update


[ml] [WIP] Consolidation of loss function

This WIP PR shows a prototypical consolidation of the LossFunction. Furthermore, it introduces some syntactic sugar to make Scala programming more fun :-)

I updated the PR

I closed this PR to open it as a proper PR again.


improve gufunc by catching common user errors

error 1: redefine scalar output variable:
@guvectorize(["(intp, intp[:])"], "()->()", nopython=True)
def foo(x, out):
    out = x

error 2: output never written to

@guvectorize(["(intp, intp[:])"], "()->()", nopython=True)
def foo(x, out):
    pass

Thoughts: what if you use intp[()] instead of intp[:] to represent the output argument? That's a call to __getitem__ with no arguments. This at least provides some logical consistency, since the output really isn't one dimensional here, it's zero-dimensional. And if you really want to be nice, you can support intp[] in the string parsing, even though that can't immediately be eval'ed.
Furthermore: consider allowing this to be used on the inputs as well, so that we can support read/write access on those values, just as we currently can with true one-dimensional and larger inputs.

Also: I would say that it is a genuine bug that this is silently accepted. Numba should issue an error if the output is specified as a scalar like this.
@nb.guvectorize('f8[:],f8', '(s)->()', nopython=True)
def mkt_max(_inarr, res):
    res = np.max(_inarr)
    print(res)

The problem with my zero-dimensional array proposal of course is that accessing that single element would require the syntax x[()], which is a bit clumsy. I blame Python. :-)


race between coqtail#start and CoqToLine

After ac6e91f72c43ea5b7734daca160f8072b6e98799, in both vim (9.1) and neovim (0.11-dev), I get the following error when I run :CoqToLine while coqtail is initializing.
Error detected while processing function coqtail#start[18]..<SNR>41_call[27]..<SNR>48_evalexpr:
line    1:
----------------------------------------
Exception occurred during processing of request from ('<IP_ADDRESS>', 45512)
Traceback (most recent call last):
  File "/usr/lib/python3.10/socketserver.py", line 683, in process_request_thread
    self.finish_request(request, client_address)
  File "/usr/lib/python3.10/socketserver.py", line 360, in finish_request
    self.RequestHandlerClass(request, client_address, self)
  File "/usr/lib/python3.10/socketserver.py", line 747, in __init__
    self.handle()
  File "/home/user/.vim/plugged/Coqtail/python/coqtail.py", line 969, in handle
    ret = handler(**args) if handler is not None else None
  File "/home/user/.vim/plugged/Coqtail/python/coqtail.py", line 205, in find_coq
    ver_or_err = self.coqtop.find_coq(
  File "/home/user/.vim/plugged/Coqtail/python/coqtop.py", line 222, in find_coq
    assert self.coqtop is None
AssertionError
----------------------------------------
Error detected while processing function coqtail#start:
line   18:
E714: List required

This can be consistently reproduced by running :CoqToLine|CoqToLine on a coq buffer that has not :CoqStarted yet.

I worried something like that might be possible. Is this something you came across accidentally during normal use or did you trigger it intentionally by spamming :CoqToLine?

I think I accidentally pressed my mappings for CoqUndo (<C-M-k>) and CoqToLine (<C-M-l>) at the same time


support PyQt5

Hope it will be upgrade to support PyQt5.
<EMAIL_ADDRESS>Wechat:28888502

if you install PyQt5 instead of PyQt4 in your computer.  then do as the following, and it will run well!
replace PyQt4 with PyQt5;
in uiKLine.py, add "from PyQt5.QtWidgets import *";  replace unicode(styleSheet, encoding='utf8') by str(styleSheet).
nothing more at all!

or you can replace it as: styleSheet = str(styleSheet, encoding='utf8')
this works for me

if you install PyQt5 instead of PyQt4 in your computer. then do as the following, and it will run well!
replace PyQt4 with PyQt5;
in uiKLine.py, add "from PyQt5.QtWidgets import *"; replace unicode(styleSheet, encoding='utf8') by str(styleSheet).
nothing more at all!

'json\\uiKLine_button.json')  # 输入配置文件,按钮配置文件

File "D:\quant\pyqt\uikline\uiKLine-master\uiKLine-master\uiBasicIO.py", line 69, in init
self.loadInputSetting()
File "D:\quant\pyqt\uikline\uiKLine-master\uiKLine-master\uiBasicIO.py", line 89, in loadInputSetting
for setting in json.load(f):
File "D:\quant\Python37\lib\json_init_.py", line 296, in load
parse_constant=parse_constant, object_pairs_hook=object_pairs_hook, **kw)
File "D:\quant\Python37\lib\json_init_.py", line 348, in loads
return _default_decoder.decode(s)
File "D:\quant\Python37\lib\json\decoder.py", line 337, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "D:\quant\Python37\lib\json\decoder.py", line 355, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

文件报错


[docs] Add PersonalBlog Gatsby starter to Showcase

The starter itself uses only some elements of the library: Buttons, Menus, Avatars, TextFields and Icons.

@greglobinski You might want to update the primary button wording :)

@greglobinski Nice project 👍

Sure, thanks!


breaking: Replaced deprecated type usage

Removed usage of FastifyLoggerInstance, which is tagged as deprecated by fastify.
Also reran the docs-generation. Not sure if that should go in a separate PR? Looks like it hasn't been run for a while.

I assumed this was breaking, since it changes what types are used, but internally they just alias the old type to the new type 🤷

Codecov Report

Merging #196 (524362a) into main (f2a1dfc) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #196   +/-   ##
=======================================
  Coverage   97.33%   97.33%
=======================================
  Files           7        7
  Lines          75       75
  Branches       17       17
=======================================
  Hits           73       73
  Misses          2        2

Impacted Files
Coverage Δ

src/types.ts
100.00% <ø> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Maybe we don't need to bump major for this then?

Probably not. I noticed there was another deprecated thing we were using. Will add that as well, and we can merge it as a patch version probably

Hmm. No, the other deprecation thing was me being confused. Should I merge this as a patch change?

Hmm. No, the other deprecation thing was me being confused. Should I merge this as a patch change?

Let's do that, then! :)


chore(release): v0.11.7

:robot: I have created a release beep boop
0.11.7 (2023-11-04)
Bug Fixes

gh-88 wrong corner radius on table head. (254bb2b)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/sira-design/sira/releases/tag/v0.11.7 :sunflower:


bug: change pcInput to pcInputText

primevue 4.1.0 change pcInput to pcInputText
see https://github.com/primefaces/primevue/commit/5bc8f2a8e36354168bd0c14b5bda3462f4a7d04b
not shure if we also must change?
https://github.com/primefaces/primevue-tailwind/blob/main/presets/aura/inputotp/index.js#L7
https://github.com/primefaces/primevue-tailwind/blob/main/presets/lara/inputotp/index.js#L7

As of v4.1.1, the new Tailwind styles have been rewritten using the preprocessor approach with @apply and builder is removed as it is not necessary anymore. Thank you.
New Website is live.


Replace libpng with LodePNG

Since libpng seems to cause some discomfort (e.g. by being hosted on sourceforge...), I was wondering whether we want to replace it with LodePNG, which is self-contained and available on github.

Issue was resolved by #410


[SwiftCompiler] Bridge DiagnosticEngine

To call DiagnosticEngine::diagnose() from Swift code.

SwiftCompilerSources cleanups

Move common bridging facilities to Basic
Package.swift cleanups (correct header search paths, configurable)
Move module.modulemap to include/.

AST bridging

Add SourceLoc and CharSourceRange bridging in Basic
Create AST bridging (DiagID, DiagnosticArgument, DiagnosticFixIt, and DiagnosticEngine)

String processing

Rename ExperimentalRegexBridging/Regex module to ParseBridging/Parse module
Pass -D SWIFT_ENABLE_EXPERIMENTAL_STRING_PROCESSING to compilations (C++ and Swift)
PoC implementation calling diagnostics from Regex literal lexing

@swift-ci Please smoke test

@swift-ci Please smoke test


Hero banner-CTA button tooltip

There is no tooltip for the button/anchor for the hero banner button in EDS.

Latest CTA- tooltip for reference:

@Kummu007 - Please validate

This is working as expected.


close save

When closing the atom, what must be said to save the open tab? Like notepad++, can't it? The tab created by notepad++ support is only for temporary use. To close notepad++, you don't have to save the open tab. The next time you open it, the unsaved tab is still there. It is meaningful to save the data temporarily. I hope to support it.

Thanks for reaching out!
Because we treat our issues list as the Atom team's backlog, we close issues that are questions since they don't represent a task needing to be completed. For most questions about Atom there are a lot of options, check out:

User Documentation — The Atom Flight Manual
Developer Documentation — Atom API Documentation
FAQ — The Atom FAQ on Discuss
Message Board — Discuss, the official Atom and Electron message board
Chat — Join the Atom Slack team

On Discuss and in the Atom Slack team, there are a bunch of helpful community members that should be willing to point you in the right direction.

When closing the atom, what must be said to save the open tab?

I'm not sure I understand the question completely but it seems like you're wondering why you're not prompted to save unsaved files when you close Atom?  If that's the case, it's expected behavior when you have a project open, that unsaved file is saved in the project state and will be restored when you reopen the project.


1.4 backports 19-02-26

#7207
#7203
#7200
#7163

This change is

test-me-please

test-missed-k8s

test-docs-please

test-docs-please

test-missed-k8s

rerunning k8s tests, vagrant provisioning failed on CI

fyi @nebril I'm going to push https://github.com/cilium/cilium/pull/7202 before I merge this series to keep backports in order.

Failure:

The alignchecker failure is intriguing. I checked out v1.4 and this is the declaration of the metricsmap.Key: in pkg/maps/metricsmap/metricsmap.go:
// Key must be in sync with struct metrics_key in <bpf/lib/common.h>
type Key struct {
	Reason uint8
	Dir    uint8
	Pad1   uint16
	Pad2   uint32
}

and the corresponding C type:
struct metrics_key {
    __u8      reason;     //0: forwarded, >0 dropped
    __u8      dir:2,      //1: ingress 2: egress
              pad:6;
    __u16     reserved[3]; // reserved for future extension
};

This is because https://github.com/cilium/cilium/pull/7212/commits/f695dc7c66a221ef1096353e022b31071bd0296b got backported which cannot be backported without https://github.com/cilium/cilium/pull/7162. Please see https://github.com/cilium/cilium/issues/6559.

Superseded by #7232.


Add accessibility label for close/cancel cases

@mikekatz please review

Assuming that the specified strings are already in a strings file: 👍


Upgrades of 3rd party dependencies

Are there any plans to upgrade Eureka to Jersey 2+? Currently it is bound to 1+, which leads so classpath problem, when used with other libraries which mostly rely on 2+.

Duplicates #470 ?

Yes, sorry for that. Can be closed.


Allow blacklist typedef

This allows making type aliases to be blacklisted.

@bors-servo: r+

:pushpin: Commit 5c67b7d has been approved by emilio

:hourglass: Testing commit 5c67b7d with merge 2d94347...

:sunny: Test successful - status-travis


Add kml:Link, kml:Icon

Attempt to add support for kml:Link and kml:Icon.
A couple of points to discuss.
First
Since the spec's kml:Icon (or kml:BasicLinkType) is already implemented and exported by the library as Kml::Icon, I used an enum to model the spec's kml:LinkType. Its variants are Kml::Link and Kml:Icon. Both are constructed with kml::types::LinkModel, the common data model used by the spec's kml:LinkType.
If kml:Model was to be implemented using this PR, then it's link field would be of type kml::types::LinkType and it would need to be guarded so as not to have it be set to kml::types::LinkType::Icon:
pub struct Model {
    link: Option<kml::types::LinkType>,
    // ...
}

impl Default for Model {
    fn default() -> Model {
        Model { link: None }
    }
}

impl Model {
    pub fn get_link(&self) -> Option<&kml::types::LinkType> {
        self.link.as_ref()
    }

    pub fn set_link(&mut self, link_model: &kml::types::LinkModel) {
        self.link = Some(kml::types::LinkType::Link(link_model.clone()));
    }
}

Let me know how you feel about this approach.
Alternatively, I could use two identical structs with different names. I could expose Icon as Kml::LinkIcon to not have it interfere with the existing Kml::Icon.
What makes the most sense for an approachable, intuitive API?
Second
I used empty strings for the optional String fields that have no default value. Let me know if you'd prefer to have them be Options instead.
Closes #10.

As much as I like the idea of using an enum, it doesn't make sense from an API ergonomics perspective. If Rust supported enum variants as first-class types, then I think it'd be a clean approach.
I'll break the enum into separate structs.


Better connection pool

Just creating an issue to track status/discussion of this. I spoke to tgriesser on IRC about this some days ago.
generic-pool doesn't track "checked out" objects, and it doesn't validate released objects; in short, it leaves some things to be desired. I pointed at the "advanced-pool" module, which I just tried to integrate in, but it has a problem too that doesn't address knex's needs: there doesn't appear to be a way to remove an idle object from the queue, so things like the pg error event from calling pg_terminate_backend can't readily be made to clean the object from the pool.
I am currently encountering an issue in production that I got more detail on just today, and it appears that part of the problem is generic-pool thinking it has more available objects than it does (which makes sense, production app isn't using my patched up version yet). I don't believe my patch will necessarily solve that problem, though, since it can only remove objects that HAVE been released to the pool. Either way, NOT tracking checked-out objects is a big roadblock in terms of doing this stuff cleanly.
Looking for options other than "write a new connection pooler". Any thoughts?

When Tim and I spoke earlier this week the conclusion was that a new pooling implementation was needed but we'd defer to the driver's pool if it provided one. node-mysql has a pretty good implementation. It's on the roadmap doc I've been working on, soon to be public.
No thoughts on what can be done to deal with this for the presrnt.

 What do you think; should a pooler ever throw an error? I'm leaning towards a synchronous throw in the case of an erroneous release (this is definitely a code error), but silently ignoring calls to destroy ("clean up this thing that's in an uncertain state"). Release doesn't actually need to be async, it's a fire-and-forget. A resource requested by the calling code should not return an error from the underlying resource allocator; these things are separated anyway, even though they're loosely correlated. There are configurable options for timing out on requesting a resource as well as idle duration and reap interval. The raw resource allocation/destruction calls are asynchronous, though any errors returned by the destroy call will not be propagated up past the pooler.

I'm sore tempted to make it promise-based, if only for the potential to know when an acquire or destroy call is sync or async (return a promise for an async call, otherwise sync)

Can't hurt to hack on this. I'd really like to get node-postgres and node-mysql on a common interface so Knex can just consume their pooling interface with minimal code. That way each db can be responsible for handling its own errors at the driver level.
And if you're gonna return a promise, always return one.

What I meant was, since the pooler doesn't know about the resources it's allocating / destroying, the function for doing that work could be synchronous or asynchronous. Expecting a promise for async is a way that the pooler can know that information.
Tim mentioned that node-postgres uses generic-pool, so I'm not sure whether I'd actually want to use its own pooling mechanism for the same reasons I want to improve knex's. node-mysql's does indeed look solid, and I was considering ripping it out, but it's written to be pretty specific to databases. I'm not entirely sure what extra information the database drivers would have to act on that's useful as far as preferring their own poolers that we wouldn't also be able to make use of.
For the sake of consistency across databases, then, and also detailed understanding of connection handling, it seems desirable to use a single pooler even if it's reproducing some work in the case of mysql. This is kind of the same reasoning as using a query builder at all - minimizing the differences between databases from the user's perspective.
I did think of one other error case, which is that on initialization, the pooler should attempt to claim a resource and throw if it fails. This would primarily be to help show networking / configuration problems up front. On the other hand, once it's been proven that the resource IS available, the pooler should probably just silently keep trying if it fails when attempting to allocate a resource later, on the assumption that the failure is temporary. It's actually pretty complex to provide error logic past that, but one possibility is to throw after being unable to provide a resource for over X time...?
I can of course emit events for failed resource allocations, but that then puts some work on the consumer of the pool to get involved in managing the state of the pool's connections, which doesn't seem right.
Any thoughts on how to proactively do something about the application potentially entering an error state where it can no longer allocate resources?

Expecting a promise for async is a way that the pooler can know that information.

Normally there's some perf concerns and you might want to do a return + callback API. Bluebird's pretty good at optimizing immediately available values and I'd rather let it do its thing and expose a single API.

Tim mentioned that node-postgres uses generic-pool, so I'm not sure whether I'd actually want to use its own pooling mechanism for the same reasons I want to improve knex's.

Correct

node-mysql's does indeed look solid, and I was considering ripping it out, but it's written to be pretty specific to databases.

It's actually mostly general, with a big fat query method that could be removed.
The idea here would be to create and then drive adoption around a standard DB pooling module that would support things like clustering be smart about authentication (versus attempting to create a truly generic pooler). The ideal scenario would be that mysql and postgres would adopt it.

Hm, I suppose there's no need for ultimate genericism, though having such a module available is beneficial still. Can you elaborate on what you mean by being smart about authentication and clustering support?

Tim and my shared conclusion from the other day was that the value of nailing the DB-specific concerns was way higher than trying to be truly generic.

:+1: the whole reason you choose a database is to use the features it provides, not some generic subset that will allow you to change to another black box.

And so the ideal version is a generic interface that something like Knex can consume, but leaving it to the database to actually hook up the right listeners on its connections to make sure they're managed within the pool properly.

tkellen: by that logic, you wouldn't want to use knex :) Knex does kind of prevent you from using db-specific features effectively, after all.
Ben: if we use the database driver native pools, then knex wouldn't want or need a pool at all. Are there databases that knex supports that do not have a pooling implementation?

then knex wouldn't want or need a pool at all

Correct. Maria and SQLite don't ship with pools.

Well, I've had success rewriting dialects/postgres/pool.js to use node-pg's pool, will do mysql too; I managed to get a test setup where I can run the appropriate integration tests finally. Problem: upstream/master is bombing a mysql integration test for me, and I'm not sure why.
I am just gonna hope that node-pg does the appropriate bookkeeping to avoid the production problem I'm dealing with; this seems a better shot than the other approach. If there are still problems I can run them down as best I can and submit a patch to node-postgres itself. My enthusiasm for solving the more general "make a good pool module" problem is waning fast :P

Integration Tests Dialect: mysql Schema createTable accepts the table name, and a "container" function:
AssertionError: expected [ Array(4) ] to deeply equal [ Array(4) ]

expected - actual

[

"create table test_table_one (id bigint unsigned not null auto_increment primary key, first_name varchar(255), last_name varchar(255), email varchar(255) null, logins int default '1', about text comment 'A comment.', created_at datetime, updated_at datetime) default character set utf8 engine = InnoDB comment = 'A table comment.'"

"create table test_table_one (id bigint unsigned not null auto_increment primary key, first_name varchar(255), last_name varchar(255), email varchar(255) null, logins int default '1', about text comment 'A comment.', created_at datetime, updated_at datetime) engine = InnoDB comment = 'A table comment.'"
"alter table test_table_one add index test_table_one_first_name_index(first_name)"
"alter table test_table_one add unique test_table_one_email_unique(email)"
"alter table test_table_one add index test_table_one_logins_index(logins)"
]

Well, I wanted to be helpful and do mysql too, but pg is really the one that affects us with a very real problem in production so I figured I'd at least do that one. Yet, even after making the changes and passing the tests, Travis is complaining:
https://github.com/tgriesser/knex/pull/687
I don't really know what to do.

@myndzi so a heads up, node-pg uses essentially the same underlying pool as knex (generic-pool), which is why it seemed like it'd be better to just create a better one with more features like clustering out of the box based on node-mysql's implementation.
See the open issues:
https://github.com/brianc/node-postgres/issues?q=is%3Aissue+is%3Aopen+pool

Yeah, I was hoping its implementation would be at least more proactive about tracking the connection stuff, and lay the groundwork for eliminating knex's pooling in favor of the db-driver pools. I also figured at least we'd get mysql's pool out of the pull, but it had problems as noted.
The more we discuss it, the less convinced I am for making a new pooler for knex's use; I think you're right about instead pushing to improve the db drivers' poolers.
I had a look through mysql's code and I'm not sure how I feel about my ability to rip it out yet.

@myndzi I'm happy to help if you're interested in working on it. But this is also a priority for me, and there's both code issues and a coordination problem here. The roadmap I'm writing up (will be public by Monday) includes a new pooler. I'd really like to get a design doc written and then get preliminary buy-in from mysql and postgres to use it. There is really no sense in duplicating effort solving this problem and hopefully a shared implementation would result in more users and therefore faster bug fixes.

I am interested in working on it, and I'm definitely in favor of this approach. Perhaps we should just submit an issue to mysql requesting the separation of the pool module from the library at large; we could focus our efforts there, and also maybe gain support from people familiar with the code in question

Great. Please hold off on taking this discussion out of this thread for now. But of course by all means continue hacking on this. Really appreciate your help.

I keep wavering back and forth between rip mysql's and write my own. node-mysql's tests, for example, are kind of inconvenient. The pooler is fairly intertwined with the connection methods, which are specific to node-mysql. I'm having trouble running down what happens with a network error on an underlying connection. Stuff like that. Using mysql's gives us a big advantage in trying to get people to adopt something else, but even if we wrote something different, we wouldn't have to be like "yo, mysql, use our stuff now pls" -- what they have in place seems quite robust.
I feel like it's going to be as much work to disentagle the pool from the connection and get all the tests matching up and so on as it will be to just finish up and add a few features to the one I wrote. Unless you have any objections, I think I'll do just that. I'll peruse mysql's code for ideas on what functionality to support and call it a day...?

See: https://github.com/myndzi/pool2
I plan to expand on this with a clustered pool implementation that will make use of the 'capabilities' array to return a subset of the available pool resources -- for example, a database connection with write capabilities.
Comments?

I don't have the time to spend right now to think carefully about this. You're welcome to go ahead but I can't give you a firm thumbs up on anything you're proposing yet.

Clustering is in now too :) Will put together a patch to utilize this instead of generic-pool.


fix: add missing () to toHaveLineCountLessThan in list

adds missing () on the arch testing page

Thanks!


Restoring from the default environment

Does the default environment have limitations when it comes to data recovery/rollback that aren't present with sandbox/production environments?  I'm trying to understand why some recommend having customized SharePoint form stored in a production environment, rather than in the default environment, - and whether there still good reasons for recommending that.

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

ID: c36038a8-28f7-cb20-dc2c-caa3186b9aba
Version Independent ID: c36038a8-28f7-cb20-dc2c-caa3186b9aba
Content: Manage the default environment - Power Platform
Content Source: power-platform/guidance/adoption/manage-default-environment.md
Service: power-platform
Sub-service: guidance
GitHub Login: @rranjit83
Microsoft Alias: rranjit

Thanks for your comment, @agbeaton. This issue has been assigned to the doc author for review.

Added Imad Yanni to help

Although all environments including Default have system backups, the standard retention period is 7 days; Production environment retention period is longer and can be up to 28 days. In addition, admins can create labeled backups for Production environments and are able to perform self-self restore from system or manual backups, this is not possible for Default.  recommend the user read environment strategy guidance here https://learn.microsoft.com/en-us/power-platform/guidance/adoption/environment-strategy


cmd/compile: performance regression with SSA backend

Please answer these questions before submitting your issue. Thanks!

What version of Go are you using (go version)?
go version devel +0d1a98e Wed Mar 2 13:01:44 2016 +0000 linux/amd64
and
go version go1.6 linux/amd64

What operating system and processor architecture are you using (go env)?
linux/amd64

What did you do?
I ran some benchmarks for a consistent hashing algorithm: (multi-probe consistent hashing, code at https://github.com/dgryski/go-mpchash ) with the new SSA backend and also with 1.6.

 ~/work/src/cvs/go.tip/bin/go test -test.bench=Lookup -test.count=20 >choose.ssa
go test -test.bench=Lookup -test.count=20 >choose.16

What did you expect to see?

Not performance regressions.

What did you see instead?

The number after the benchmark is the number of shards.  For 8 and 32 shards, the new SSA backend is faster.  For larger numbers of shards, the lookup time is worse.
<dgryski@kamek[go-mpchash] \ʕ◔ϖ◔ʔ/ > benchstat choose.16 choose.ssa
name          old time/op  new time/op  delta
Lookup8-4      248ns ± 1%   209ns ± 3%  -15.67%  (p=0.000 n=20+17)
Lookup32-4     262ns ± 2%   221ns ± 2%  -15.77%  (p=0.000 n=19+18)
Lookup128-4    410ns ± 1%   410ns ± 1%     ~     (p=0.482 n=20+19)
Lookup512-4    458ns ± 1%   502ns ± 1%   +9.58%  (p=0.000 n=19+20)
Lookup2048-4   501ns ± 1%   548ns ± 1%   +9.41%  (p=0.000 n=20+20)
Lookup8192-4   584ns ± 1%   624ns ± 2%   +6.97%  (p=0.000 n=18+20)

To determine if this was runtime changes or the SSA backend, I also ran it against tip with SSA off (GOSSAHASH=x).  Between 1.6 and tip (without SSA), the performance regression is ~5%.
<dgryski@kamek[go-mpchash] \ʕ◔ϖ◔ʔ/ > benchstat choose.16 choose.tip
name          old time/op  new time/op  delta
Lookup8-4      248ns ± 1%   246ns ± 1%  -1.13%  (p=0.000 n=20+20)
Lookup32-4     262ns ± 2%   276ns ± 2%  +5.16%  (p=0.000 n=19+19)
Lookup128-4    410ns ± 1%   431ns ± 2%  +5.31%  (p=0.000 n=20+20)
Lookup512-4    458ns ± 1%   485ns ± 1%  +5.83%  (p=0.000 n=19+20)
Lookup2048-4   501ns ± 1%   540ns ± 3%  +7.77%  (p=0.000 n=20+20)
Lookup8192-4   584ns ± 1%   624ns ± 2%  +7.00%  (p=0.000 n=18+20)

Between tip and tip-with-ssa, it's faster for 8 and 32 shards, but then only slight changes at larger numbers.
<dgryski@kamek[go-mpchash] \ʕ◔ϖ◔ʔ/ > benchstat choose.tip choose.ssa
name          old time/op  new time/op  delta
Lookup8-4      246ns ± 1%   209ns ± 3%  -14.71%  (p=0.000 n=20+17)
Lookup32-4     276ns ± 2%   221ns ± 2%  -19.90%  (p=0.000 n=19+18)
Lookup128-4    431ns ± 2%   410ns ± 1%   -4.95%  (p=0.000 n=20+19)
Lookup512-4    485ns ± 1%   502ns ± 1%   +3.55%  (p=0.000 n=20+20)
Lookup2048-4   540ns ± 3%   548ns ± 1%   +1.52%  (p=0.000 n=20+20)
Lookup8192-4   624ns ± 2%   624ns ± 2%     ~     (p=0.506 n=20+20)

CC @randall77 @dr2chase

Definitely strange that the performance is data-dependent.  Makes me think there's some code that is slower with SSA and some code that is faster with SSA and the number of shards affects the balance of the two routines that are run.
Can you get a profile from the best and worst tip performers (relative to 1.6)?  It might shed some light.

A quick scan of the 4 profiles shows that for the lookups with 8 keys, after the lookup function itself, the next highest is the siphash core (https://github.com/dchest/siphash ).  For 8192 shards, the second item in the profile is runtime.mapaccess1_fast64.

That makes sense, the map lookup should be more expensive for 8192 shards.  It doesn't explain the performance difference though, as the map access only accounts for ~5% of total running time.
Looks like the extra time is in (*Multi).Hash

I will rerun these benchmarks today against the current tip.

Still present:
<dgryski@kamek[go-mpchash] \ʕ◔ϖ◔ʔ/ >  ~/work/src/cvs/go.tip/bin/go  version
go version devel +b354f91 Fri Mar 11 06:43:01 2016 +0000 linux/amd64
<dgryski@kamek[go-mpchash] ʕ╯◔ϖ◔ʔ╯ > ~/work/src/cvs/go.tip/bin/go test -test.bench=Lookup -test.count=20 >choose.ssa
<dgryski@kamek[go-mpchash] \ʕ◔ϖ◔ʔ/ > go version
go version go1.6 linux/amd64
<dgryski@kamek[go-mpchash] \ʕ◔ϖ◔ʔ/ > go test -test.bench=Lookup -test.count=20 >choose.16
<dgryski@kamek[go-mpchash] \ʕ◔ϖ◔ʔ/ > benchstat choose.16 choose.ssa
name          old time/op  new time/op  delta
Lookup8-4      316ns ±15%   288ns ±18%   -8.97%  (p=0.000 n=19+19)
Lookup32-4     346ns ± 7%   304ns ± 9%  -12.06%  (p=0.000 n=17+20)
Lookup128-4    525ns ±12%   528ns ±12%     ~     (p=0.616 n=20+20)
Lookup512-4    608ns ±15%   676ns ± 8%  +11.31%  (p=0.000 n=20+20)
Lookup2048-4   662ns ±11%   752ns ±12%  +13.49%  (p=0.000 n=18+20)
Lookup8192-4   740ns ±11%   867ns ±20%  +17.10%  (p=0.000 n=20+20)

I found one small fix that should help some.  Generally the performance difference baffles me.  The generated code looks pretty good, certainly as good as the legacy compiler generates.
One problem is that this is a doubly-nested loop where the inner loop count is small.  The SSA optimization for loop entry doesn't trigger on the outer loop.  That's something I intend to get to, I'll open a bug for tracking.
Another suspect is branch mispredicts - the old and new compiler lay out code differently.  The fact that the inner loop count is small may contribute.  This is only a suspicion.

Looks like recent improvements at tip have fixed this.

For the record,
<dgryski@kamek[go-mpchash] \ʕ◔ϖ◔ʔ/ > cat run.sh
#!/bin/sh
set -x
git show |grep ^commit
~/work/src/cvs/go.tip/bin/go version
~/work/src/cvs/go.tip/bin/go test -test.bench=Lookup -test.count=40 >choose.ssa
go version
go test -test.bench=Lookup -test.count=40 >choose.16
benchstat choose.16 choose.ssa
<dgryski@kamek[go-mpchash] \ʕ◔ϖ◔ʔ/ > ./run.sh
+ + grep ^commit
git show
commit 7a1df2af545d653c6e01b11220835896fcd5e124
+ /home/dgryski/work/src/cvs/go.tip/bin/go version
go version devel +45522a6 Thu Apr 21 06:35:48 2016 +0000 linux/amd64
+ /home/dgryski/work/src/cvs/go.tip/bin/go test -test.bench=Lookup -test.count=40
+ go version
go version go1.6.2 linux/amd64
+ go test -test.bench=Lookup -test.count=40
+ benchstat choose.16 choose.ssa
name          old time/op  new time/op  delta
Lookup8-4      224ns ± 2%   187ns ± 3%  -16.30%  (p=0.000 n=37+38)
Lookup32-4     243ns ± 3%   205ns ± 2%  -15.51%  (p=0.000 n=38+40)
Lookup128-4    418ns ± 1%   368ns ± 1%  -11.81%  (p=0.000 n=40+36)
Lookup512-4    458ns ± 1%   446ns ± 2%   -2.50%  (p=0.000 n=39+36)
Lookup2048-4   500ns ± 1%   497ns ± 2%   -0.75%  (p=0.000 n=38+39)
Lookup8192-4   580ns ± 3%   557ns ± 3%   -3.83%  (p=0.000 n=37+40)