TRL version should be 0.8.6

Hello,
Thanks for your great work! As TRL released new versions, the arguments, like ref_model_init_kwargs, don't match anymore.
I backtracked the time of your release so I think trl should be 0.8.6. Will be great to add a note or requirements.txt for new comers.
Best,
Blake

Hi,
Thanks for your note! Yes, the TRL library is being actively updated, and we noticed that there were several issues and bugs when the TRL library version mismatched what we used in our experiments.
We are working on a PR to add SimPO to TRL and hopefully, that'll resolve most of the issues. We'll update our codebase soon as well. Please stay tuned!
Best,
Yu

close as the new release will fix it


Error on YUI Compressor

link of check online : https://www.piliapp.com/minify/yui-compressor/
[Assetic\Exception\FilterException]                                                                                An error occurred while running:                                                                                '/usr/bin/java' '-jar' '/var/www/drapo.dev/app/../bin/yuicompressor.jar' '--charset' 'UTF-8' '-o' '/tmp/assetic_yui_outputM12AO7' '--type' 'js' '/tmp/assetic_yui_input7T7Aau'                                                                                Error Output:                                                                                [ERROR] in /tmp/assetic_yui_input7T7Aau                                                                                38:19:invalid property id                                                                                [ERROR] in /tmp/assetic_yui_input7T7Aau                                                                                38:20:syntax error                                                                                [ERROR] in /tmp/assetic_yui_input7T7Aau                                                                                39:27:syntax error                                                                                [ERROR] in /tmp/assetic_yui_input7T7Aau                                                                                40:26:missing ; before statement                                                                                [ERROR] in /tmp/assetic_yui_input7T7Aau                                                                                41:29:missing ) in parenthetical                                                                                [ERROR] in /tmp/assetic_yui_input7T7Aau                                                                                42:23:syntax error                                                                                [ERROR] in /tmp/assetic_yui_input7T7Aau                                                                                43:30:syntax error                                                                                [ERROR] in /tmp/assetic_yui_input7T7Aau

Thank you. It seems that delete is a reserved keyword and should be quoted.

Thanks for your report, this is now fixed.
As there are BC breaks, I needed to upgrade the major version.
Will update the documentation & demos tonight.


Nested Text components ignore opacity style on Android

Is this a bug report?
Yes
Have you read the Contributing Guidelines?
Yes
Environment
Environment:

OS: macOS High Sierra 10.13.3
Node: 8.9.4
Yarn: 1.3.2
npm: 5.6.0
Watchman: 4.9.0
Xcode: Xcode 9.2 Build version 9C40b
Android Studio: 3.0 AI-171.4443003

Packages: (wanted => installed)

react: 16.2.0 => 16.2.0
react-native: 0.53.0 => 0.53.0

Target Platforms:

Android 5.1
iOS 8.0

Steps to Reproduce

Start a new project.
Render nested Text components with an inner component styled with reduced opacity
Example:

<Text>
  One
  <Text style={{opacity: 0.4}}>
    Two
    <Text style={{opacity: 0.4}}>
      Three
    </Text>
  </Text>
  .
</Text>

Expected Behavior
Both iOS and Android would show the text, with the contents of the nested component rendering slightly transparent.
Actual Behavior

iOS
Android

Ok. Notice "Two" and "Three" are respecting their opacity style.
Nested text component ignores opacity style. "Two" and "Three" have the same opacity as "One"

Reproducible Demo
Snack demo here. You can see that "Two" and "Three" are rendered incorrectly on Android, as shown in the screenshots above.

This issue comment would lead one to believe that this should work on all platforms.

I have encountered the same issue.
I can also reproduce it with border props, as in
return (
    <Text>
        foo
        <Text style={{ borderWidth: 2, borderColor: 'black' }}>bar</Text>
    </Text>
)

renders as

I'm just guessing here but border styles and the opacity are all in the view style props, could it be that only text style props work for nested texts?


Activate Region when 144 citizens have joined

When 144 citizens have joined a region (formerly bioregion), it becomes active
For now we can simply implement this by

Counting the number of members in a region - we might already do that
having an active flag that gets set to true when they've joined
Have an index for the active flag so we can iterate over only the active regions - only active regions get part of the harvest.
A region gets deactivated when it drops below 144 - in case a region gets abandoned

As harvest is concerned, I think we will simply have buckets, then later distribute the buckets to their recipients

Hello I have a question, for this implementation should I use a migration for the bioregions table? or the active flag could be in another table

I am ok having it in another table, or even a badge
I have been thinking about badges

Adding this to milestone as we need it up much sooner than expected


Add support for network acl

Hi @aashishgaba-cn, is this the same as #518? If so, please close one.

Hi @aashishgaba-cn, are you able to close this PR and re-open?


The example provided is not working

Describe the bug
Example usage isn't working (at least not out of the box).
To Reproduce
docker-compose up
psql -U postgres -h <IP_ADDRESS> -p 6432 -d postgres
Password for user postgres:
psql: error: connection to server at "<IP_ADDRESS>", port 6432 failed: FATAL:  No pool configured for database: "postgres", user: "postgres"

Expected behavior
Working out of the box
Desktop (please complete the following information):

OS: ubuntu 22.04

Did you manage to get it working? If so, how? I'm having the same issue.


Chat in edit mode can not be moved to a folder

1 Create a folder
2 Create a chat, hover over the chat name and click on three dots menu
3 Click on Edit in the menu -> tree dots menu disappears, check mark and x buttons appear instead -> ok
4 Drag & drop the chat to the folder -> nothing happens -> bug
Expected result: edit mode is closed, chat is moved to a folder
Note: It works as expected if chat or prompt is in delete mode;

Closing the ticket as Delete mode was redesign, no it works consistently. So it's correct that chat in edit mode can not be drag & dropped


Chart Editor tweak + organization

fixed a bug with the lil' opp/bf not resetting immediately to "idle" after pressing "R" in chart editor

combine the "playAnim = idle" code into a single function, to remove duplicate functions

here's a video that understands what i mean:
https://github.com/user-attachments/assets/d94ccbb3-61bc-4dae-a7ae-506276a63835
another pull request in 1 day wtf-

Thanks!

yw!


Fix scheduled benchmarks

Description
Benchmarks running here - https://github.com/Saransh-cpp/PyBaMM/actions/runs/4469585290/jobs/7851901865
Fixes #2783
Type of change
Please add a line in the relevant section of CHANGELOG.md to document the change (include PR #) - note reverse order of PR #s. If necessary, also add to the list of breaking changes.

[ ] New feature (non-breaking change which adds functionality)
[ ] Optimization (back-end change that speeds up the code)
[ ] Bug fix (non-breaking change which fixes an issue)

Key checklist:

[ ] No style issues: $ pre-commit run (see CONTRIBUTING.md for how to set this up to run automatically when committing locally, in just two lines of code)
[ ] All tests pass: $ python run-tests.py --all
[ ] The documentation builds: $ python run-tests.py --doctest

You can run unit and doctests together at once, using $ python run-tests.py --quick.
Further checks:

[ ] Code is commented, particularly in hard-to-understand areas
[ ] Tests added that prove fix is effective or that feature works

You can see the failing benchmarks here - https://github.com/Saransh-cpp/PyBaMM/actions/runs/4469585290/jobs/7851901865
The benchmarks are failing because of PyBaMM related errors - https://github.com/pybamm-team/PyBaMM/pull/2784#issuecomment-1476491320 (same for both the PRs)

@tinosulzer I think this should still be merged as the scheduled benchmarks have a different workflow and that is also broken. However, I cannot re-open this PR for some reason (maybe because I rebased the branch while the PR was closed). I'll open a new PR for this.


integration-docs: Update for new format (Github, Github Sponsors, UptimeRobot, Updown).

The changes are implementing the new integration-docs format and does not modify content.
There are 4 commit each updating one doc.md file.
Fixes part of https://github.com/zulip/zulip/issues/29592.
Updates the following integration documentation pages:

Github
Doc link

Github Sponsors
Doc link

UptimeRobot
Doc link

Updown
Doc link

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

docs LGTM!

@zulipbot add "mentor review" "area: documentation (api and integrations)"
@zormit, please review this too, thanks!

@zulipbot remove "mentor review"
@zulipbot add "maintainer review"

Hi @laurynmm,
Could you please review this?
I hope to be able to apply the feedback here to more PRs for the other integration docs as well (maybe next week).
So, specific guidance and perspectives on wording changes can help.
Thanks!
I referred to documenting an integration (which needs to be updated too #29593). I could make a PR for that too, but I have some more pressing work for at least the next couple of weeks, I might get to it if it is still open later.
Note: This is my first PR for the zulip/zulip repo. So, please do excuse me and let me know if there are any processes or conventions that I'm not following properly, or anything that can be improved.

Thank you for the detailed review, @laurynmm! :)
I've updated the PR.

@Niloth-p - These updates look great!
One more thing, can you remove the if blocks around {!event-filtering-additional-feature.md!} in these updated docs (see #30765). I realized it's confusing about when to include that file when it's conditional. We should just add it for any webhook that supports event filtering in it's implementation/view, which is the case for these four integrations in this PR.
Once that's done, feel free to remove the "maintainer review" label and add the "integration review" label.

Oops, you beat me by 20 minutes :smile: I was about to update it after finishing a bit of work on another repo. Sorry for making you type that explanation. Thank you for the reviews and the patient explanations, @laurynmm!
@zulipbot remove "maintainer review"
@zulipbot add "integration review"

Merged, thanks @Niloth-p!


[Docs] Fix Docker instructions

The quay.io/etcd-io/zetcd links were no longer working/useable
Signed-off-by: lloydmeta<EMAIL_ADDRESS>

we should fix the etcd-io one, not switching back to coreos one.

Got it, I was unaware of the org-level going-ons. Closing.


fix control data & status stage always start with DATA1

control data & status stage always start with DATA1. This pr fixes an issue with an Control OUT transfer (with data) where the PID is incorrectly DATA0. This should fix #55
PS: This issue is kind of critical for me to get host cdc running (need SET LINE CODING). @sekigon-gonnoc if possible, would you mind making a release after reviewed/merged. Thank you in advance.

@hathach will check either later tonight or tomorrow.

@soulfish5 have you got the chance to test this PR out, just wonder if this work for you ?

@soulfish5 have you got the chance to test this PR out, just wonder if this work for you ?

👍🏾
Closed the issue.  Thanks for the fix!

@hathach Thank you for your PR. I released this as 0.5.1

thank you @sekigon-gonnoc, release seems still 0.5.0, could you also make an release in addition to 0.5.1 tag. I think arduino index fetching based on that


Remove aria-labelledby from accordion sections

Adding aria-labelledby to a <div> with no explicit role is explicitly disallowed by the 'ARIA in HTML' specification and in our testing provides little or no benefit to users, including users of assistive technologies.
We’ve explored using <section> elements for each accordion section (for which a label would make sense), however best practise is to limit the use of region landmarks ‘as too many landmarks can dilute their usefulness in quickly navigating to important areas of a page’.
We don’t have clear evidence that marking accordion sections up as regions is useful, so more research is needed in this area.
There has also been a suggestion that we could use <article> elements, but it would depend on how the accordion is being used.
We may still want to pursue these options in the future, but until we make a decision on whether the sections should have a semantic role remove the aria-labelledby attribute – it’s trivial to reintroduce it later.
Closes #2472.

Merging (and releasing) this should allow us to remove the related issue from our accessibility statement.

All these pesky tests, getting in the way of me ripping out bits of code – what have they ever done for us, eh? 😉


deploy using paramiko not compatible with OpenSSH 6.7

Please update the paramiko version to 1.15.1
https://github.com/paramiko/paramiko/issues/423

Thanks for the PR! :)


Blocking UWP Issue Net Native

So I am trying to reference a UWP library that references a .NET Standard 2.0 library. The UWP library targets 16299 as the Target and Min version.
Whenever I try to build it in Release or Debug with .NET Native compilation from a 16299 app I get the following:
3>C:\Users\[username]\.nuget\packages\microsoft.net.native.compiler\2.2.8-rel-28605-00\tools\Microsoft.NetNative.targets(801,5): error : MCG0023: MCG0023:UnresolvableAssemblyReference Unresolvable assembly reference 'Assembly(Name=Windows.Foundation.UniversalApiContract, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null, ContentType=WindowsRuntime)' found. Please check the references in your build system. A reference is either missing or an assembly is missing an expected type.

This is blocking me pretty hard at the moment. I've tried a lot of different variations of versions of UWP library and/or .NET Native Compiler and nothing seems to make a difference. I've also got a default.rd.xml file in the library with the default
<Directives xmlns="http://schemas.microsoft.com/netfx/2013/01/metadata">
  <Library>
    <Assembly Name="*Application*" Dynamic="Required All" />
  </Library>
</Directives>

in it, and that doesn't seem to help either.

 And the UWP library I'm using is 6.2.10

In making the min-repo, I discovered that it appears to be coming from the Microsoft.Toolkit.Uwp.UI.Controls library. I'll move this issue to there.
I hope for .NET 5, issues like this will have the faulting library including in the output. This is painful to debug.

For anyone who finds this - https://github.com/windows-toolkit/WindowsCommunityToolkit/issues/3559
I'll close this here.


Warning: CocoaPods not installed. Skipping pod install.

Steps to Reproduce

I try to run my IOS app in Android Studio.
Android Studio return in console window of Android Studio the message:
Warning: CocoaPods not installed. Skipping pod install.
CocoaPods is used to retrieve the iOS and macOS platform side's plugin code that responds to your plugin usage on the Dart side.
Without CocoaPods, plugins will not work on iOS or macOS.
For more info, see https://flutter.dev/platform-plugins
To install see https://guides.cocoapods.org/using/getting-started.html#installation for instructions.

CocoaPods not installed or not in valid state.
Error launching application on iPhone 13 Pro Max.

I have installed coocoapods:
sudo gem install cocoapods
gem list

*** LOCAL GEMS ***
cocoapods (1.11.2, 1.10.1)
cocoapods-core (1.11.2, 1.10.1)
cocoapods-deintegrate (1.0.5, 1.0.4)
cocoapods-downloader (1.5.1, 1.4.0)
cocoapods-plugins (1.0.0)
cocoapods-search (1.0.1, 1.0.0)
cocoapods-trunk (1.6.0, 1.5.0)
cocoapods-try (1.2.0)

I have opened my terminal and i went to my IOs root level project. I worte:
pod install:
Analyzing dependencies
[!] The version of CocoaPods used to generate the lockfile (1.11.2) is higher than the version of the current executable (1.10.1).      Incompatibility issues may arise.
Downloading dependencies
Installing FMDB (2.7.5)
Installing Flutter (1.0.0)
Installing geocoding (1.0.5)
Installing geolocator_apple (1.2.0)
Installing path_provider_ios (0.0.1)
Installing shared_preferences_ios (0.0.1)
Installing sqflite (0.0.2)
Generating Pods project
Integrating client project
Pod installation complete! There are 6 dependencies from the Podfile and 7 total pods installed.

[!] Automatically assigning platform iOS with version 9.0 on target Runner because no platform was specified. Please specify a platform for this target in your Podfile. See https://guides.cocoapods.org/syntax/podfile.html#platform.
[!] CocoaPods did not set the base configuration of your project because your project already has a custom config set. In order for CocoaPods integration to work at all, please either set the base configurations of the target Runner to Target Support Files/Pods-Runner/Pods-Runner.profile.xcconfig or include the Target Support Files/Pods-Runner/Pods-Runner.profile.xcconfig in your build configuration (Flutter/Release.xcconfig).

Finally it doent still work.
I can't run my IOS App from Android Studio.

Important things:

I have recently upgrade my Mac OS version from Big Sur to Monterey.

I have recently upgrade my Android Studio to the latest version Bumblebee.

¿Can anyone help me?
Thanks a lot.
Logs

flutter doctor --verbose

When i run flutter doctor --verbose on the command line, i get the next:
flutter doctor -v
[✓] Flutter (Channel stable, 2.8.1, on macOS 12.1 21C52 darwin-x64, locale es-ES)
• Flutter version 2.8.1 at /Users/angelruizcanton/Flutter/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 77d935af4d (6 weeks ago), 2021-12-16 08:37:33 -0800
• Engine revision 890a5fca2e
• Dart version 2.15.1
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
• Android SDK at /Users/angelruizcanton/Library/Android/sdk
• Platform android-31, build-tools 30.0.2
• Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7590822)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
• Xcode at /Applications/Xcode.app/Contents/Developer
• CocoaPods version 1.11.2
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 2021.1)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7590822)
[✓] IntelliJ IDEA Community Edition (version 2021.2.4)
• IntelliJ at /Applications/IntelliJ IDEA CE.app
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
[✓] VS Code (version 1.63.2)
• VS Code at /Users/angelruizcanton/Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.32.0
[✓] Connected device (2 available)
• iPhone 13 Pro Max (mobile) • 1C4765E3-DC05-4F41-972F-96F8581FBF0F • ios            • com.apple.CoreSimulator.SimRuntime.iOS-15-2 (simulator)
• Chrome (web)               • chrome                               • web-javascript • Google Chrome 97.0.4692.99
• No issues found!

Closing this as a duplicate of https://github.com/flutter/flutter/issues/97251


⚠ ClamAV has degraded performance

In 4a7eeb7, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 200 ms

Resolved: ClamAV performance has improved in 82202c6.


⚠ ClamAV has degraded performance

In 2e50167, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 238 ms

Resolved: ClamAV performance has improved in 1a504ea after 22 minutes.


When you hover, submenu should be different color and with notchy thing

Version: master 2/24
Steps to Reproduce:

hover over different menu then what you are on

Results: Submenu is same color as selected submenu
Expected: submenu should be different color and have notchy thingy
+1 from Darren and Vincent

Beginning of fix in https://github.com/rancher/ui/pull/484 @vincent99 will you take a look at how the toggleClass is set up

Version - master UI 3/3
Verified fixed


Skin heads do not change in Slack.

This might be because of UUIDs, or cache.
Are you able to access with the updated skin head? https://cravatar.eu/head/INSERT_NICKNAME/128.png

Yes.  That was to first thing I check to see if their skin was not updated there, but it is correct.

Ok, I will move to use UUIDs instead of player names in 1.5 to see if that helps.

Got it! Thanks!

Check to see if the latest dev build from 8f6a596395174fd279590361a7be30ea4b5bd311 fixes this.

Yep, the heads were corrected!

Yay! :D


Consider running build on PRs

I think at the moment it only runs on main. But it's probably useful (if expensive) to run on PRs, probably some kinds of malformed metadata will only be caught by actually trying to build the repo?

Yes, we should. But we should also save the repo as an artifact after the build (so one can fetch it and troubleshoot). At this moment, uploading the artifact and publishing are a bit interweened. I can work to disentagle them.
Or one could push the build repo to new branch per build/PR?

Saving the artifact sounds sensible so long as it's easy enough to get? Although tbh people can probably reproduce by building locally. It's like CI: you mostly just try and reproduce the problem locally.


CAMEL-20495: camel-jsonpath - If resultType is List then automatic wr…

…ap single element into a List.
Description

Target

[ ] I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

[ ] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

[ ] I checked that each commit in the pull request has a meaningful subject line and body.

[ ] I have run mvn clean install -DskipTests locally and I have committed all auto-generated changes

I am backporting to supported 3.x versions


Add null terminator to RoutingToken in nego_set_routing_token

While working on the proxy we're implementing, We used the routing token as a temporary solution for passing the target server from the client. After running some manual tests, I noticed that nego->RoutingToken isn't null terminated correctly in nego_set_routing_token. While it is being parsed, the function nego_read_request_token_or_cookie replaces the CRLF with zeros:
if (crlf == 0x0A0D)
{
	Stream_Rewind(s, 2);
	len = Stream_GetPosition(s) - pos;
	Stream_Write_UINT16(s, 0); /* Here the CRLF bytes are being replaced with zeros */
	if (strlen((char*)str) == len)
	{
		if (isToken)
			result = nego_set_routing_token(nego, str, len);
		else
			result = nego_set_cookie(nego, (char*)str);
	}
}

The problem is that nego_set_routing_token calls CopyMemory with Length = nego->RoutingTokenLength which is the length of the routing token without the null terminator byte.
I chose to fix it by adding the null terminator "manually" instead of calling CopyMemory with RoutingTokenLength + 1 because I found it more readable and understandable.

@freerdp-bot test

@kubistika I understand that it might help to have a \0 terminator appended, but what kind of issue did you have?
The whole routing token is not a string but a byte array and no termination is required. (and even then you have the length argument which limits the size of the buffer)
Sounds like there is some other issue hiding beneath

@akallabeth As I said, we use the routing token as a solution to pass the target host from the client. Meaning that settings->ServerHostname is set to the client's routing token. Therefore, without the null byte, sometimes the connection couldn't be opened because the hostname wasn't terminated and that's caused a bug. I understand that no null-termination is required, but I don't think there are any disadvantages of adding it. It will just add the option to use the RoutingToken as a string.
We can solve this by copying the routing token to a buffer and add a null terminator, if you don't think that this change should be merged.

Same as @akallabeth , the spec doesn't require null termination and you have a way to achieve what you want without any changes. IMHO this PR is useless.

:+1:


Cancelling Uploading File Once Uploading Started

In Our Application, We had a file input control once we select a file we are uploading that file to the blob. We need to upload 1Gb File so it will take some time to upload. If a user wants to change that file then we don't want to upload that file completely. In that case, we want to abort the file upload and upload a new file. To achieving that functionality We are searching for a feature to cancel the file upload.
We haven't found any solution for this problem. Can you help us a solution to our problem.

@shanmuksai
Which version of the @azure/storage-blob library are you using?
If you're using version 12.0.0, you can pass an abortSignal as one of the options to your upload method.
You can get an abortSignal by instantiating an AbortController, either using the one that's natively available in your web browser or from the @azure/abort-controller package.
When you start an upload, you can instantiate a new AbortController, and pass abortController.abortSignal to your upload function. Then when the user triggers a cancellation (e.g. pressing a cancel button) you would call abortController.abort() using the AbortController you instantiated earlier. This should cause your upload operation to cancel and throw an AbortError.
Here's a link to examples for using an AbortController: https://github.com/Azure/azure-sdk-for-js/tree/master/sdk/core/abort-controller#examples
Let us know if the above helps or if anything is unclear!

@chradek this worked for us. Thanks for your quick response.


Not able to create build or package executable

npm run app-package not able create build package executable
To Reproduce
Install and Link Dependencies
npm run bootstrap
npm run  app-package
Expected behavior
Should create build or package
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. macOS 10.15.1]
Installation Method: [e.g. homebrew]
App Version [e.g. v7.0.3]

Additional context
insomnia-app: npm
insomnia-app: WARN deprecated<EMAIL_ADDRESS>This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
insomnia-app: npm
insomnia-app:  WARN deprecated<EMAIL_ADDRESS>This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
insomnia-app: npm
insomnia-app:  WARN deprecated<EMAIL_ADDRESS>This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
insomnia-app: npm WARN deprecated<EMAIL_ADDRESS>This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
insomnia-app: npm
insomnia-app: WARN deprecated<EMAIL_ADDRESS>This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
insomnia-app: npm
insomnia-app: WARN deprecated<EMAIL_ADDRESS>Package no longer supported. Contact<EMAIL_ADDRESS>for more info.
insomnia-app: npm
insomnia-app: WARN deprecated<EMAIL_ADDRESS>This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
insomnia-app: npm
insomnia-app: WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
insomnia-app: npm ERR!
insomnia-app:  Unexpected end of JSON input while parsing near '...+MIbw\nUcokI2mnCj4Z3+'
insomnia-app: npm
insomnia-app:  ERR! A complete log of this run can be found in:
insomnia-app: npm
insomnia-app: ERR!     /Users/sunilbagde/.npm/_logs/2020-07-03T22_35_31_829Z-debug.log
insomnia-app: child process exited with code 1
insomnia-app: [build] Complete!
insomnia-app: [package] Removing existing directories
insomnia-app: [package] Packaging app
insomnia-app:   • electron-builder  version=21.2.0 os=19.2.0
insomnia-app:   • installing production dependencies  platform=darwin arch=x64 appDir=/Users/sunilbagde/code/http1/packages/insomnia-app/build
insomnia-app: [package] ERROR: { Error: /usr/local/bin/node exited with code ERR_ELECTRON_BUILDER_CANNOT_EXECUTE
insomnia-app: Error output:
insomnia-app: Error output:
insomnia-app: npm WARN deprecated<EMAIL_ADDRESS>This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
insomnia-app: npm WARN deprecated<EMAIL_ADDRESS>This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
insomnia-app: npm WARN deprecated<EMAIL_ADDRESS>This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
insomnia-app: npm WARN deprecated<EMAIL_ADDRESS>This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
insomnia-app: npm WARN deprecated<EMAIL_ADDRESS>This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
insomnia-app: npm WARN deprecated<EMAIL_ADDRESS>Package no longer supported. Contact<EMAIL_ADDRESS>for more info.
insomnia-app: npm WARN deprecated<EMAIL_ADDRESS>This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
insomnia-app: npm WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
insomnia-app: npm ERR! Unexpected end of JSON input while parsing near '...+MIbw\nUcokI2mnCj4Z3+'
insomnia-app: npm ERR!      /Users/sunilbagde/.npm/_logs/2020-07-03T22_35_35_731Z-debug.log
insomnia-app:     at ChildProcess.childProcess.once.code (/Users/sunilbagde/code/http1/packages/insomnia-app/node_modules/builder-util/src/util.ts:239:14)
insomnia-app:     at Object.onceWrapper (events.js:286:20)
insomnia-app:     at ChildProcess.emit (events.js:198:13)
insomnia-app:     at maybeClose (internal/child_process.js:982:16)
insomnia-app:     at Socket.stream.socket.on (internal/child_process.js:389:11)
insomnia-app:     at Socket.emit (events.js:198:13)
insomnia-app:     at Pipe._handle.close (net.js:606:12)
insomnia-app:   exitCode: 1,
insomnia-app:   alreadyLogged: false,
insomnia-app:   code: 'ERR_ELECTRON_BUILDER_CANNOT_EXECUTE' }
insomnia-app: npm ERR! code ELIFECYCLE
insomnia-app: npm ERR! errno 1
insomnia-app: npm ERR<EMAIL_ADDRESS>package: node ./scripts/package.js
insomnia-app: npm ERR! Exit status 1
insomnia-app: npm ERR!
insomnia-app: npm ERR! Failed at the<EMAIL_ADDRESS>package script.
insomnia-app: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
insomnia-app: npm ERR!      /Users/sunilbagde/.npm/_logs/2020-07-03T22_35_35_801Z-debug.log
lerna ERR! npm run package exited 1 in 'insomnia-app'
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>app-package: lerna run package --stream --parallel --bail
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>app-package script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!      /Users/sunilbagde/.npm/_logs/2020-07-03T22_35_35_824Z-debug.log

Fixed

@thesunilbagde how?

Old way used mentioned version and removed node_module installed


Sync

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 59.45946% with 45 lines in your changes missing coverage. Please review.

Files with missing lines
Patch %
Lines

...c/main/java/seedu/address/ui/MeetingListPanel.java
0.00%
13 Missing :warning:

src/main/java/seedu/address/ui/MainWindow.java
0.00%
8 Missing :warning:

src/main/java/seedu/address/ui/MeetingCard.java
0.00%
7 Missing :warning:

...eedu/address/logic/commands/AddMeetingCommand.java
73.68%
4 Missing and 1 partial :warning:

src/main/java/seedu/address/MainApp.java
0.00%
4 Missing :warning:

src/main/java/seedu/address/ui/PropertyCard.java
0.00%
3 Missing :warning:

...rc/main/java/seedu/address/model/ModelManager.java
90.47%
2 Missing :warning:

...rc/main/java/seedu/address/logic/LogicManager.java
66.66%
1 Missing :warning:

.../address/logic/parser/AddMeetingCommandParser.java
91.66%
0 Missing and 1 partial :warning:

...java/seedu/address/model/meeting/MeetingTitle.java
75.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Files with missing lines
Coverage Δ
Complexity Δ

...edu/address/logic/commands/AddPropertyCommand.java
85.00% <100.00%> (+0.78%)
7.00 <1.00> (ø)

.../address/logic/commands/FilterPropertyCommand.java
100.00% <100.00%> (ø)
13.00 <0.00> (ø)

...eedu/address/logic/commands/ListBuyersCommand.java
100.00% <100.00%> (ø)
3.00 <1.00> (+1.00)

...edu/address/logic/commands/ListClientsCommand.java
100.00% <100.00%> (ø)
3.00 <1.00> (+1.00)

...java/seedu/address/logic/commands/ListCommand.java
100.00% <ø> (ø)
2.00 <0.00> (ø)

...du/address/logic/commands/ListMeetingsCommand.java
100.00% <100.00%> (ø)
3.00 <3.00> (?)

.../address/logic/commands/ListPropertiesCommand.java
100.00% <100.00%> (ø)
3.00 <1.00> (+1.00)

...edu/address/logic/commands/ListSellersCommand.java
100.00% <100.00%> (ø)
3.00 <1.00> (+1.00)

.../seedu/address/logic/parser/AddressBookParser.java
100.00% <100.00%> (ø)
22.00 <0.00> (+1.00)

.../seedu/address/logic/parser/ListCommandParser.java
100.00% <100.00%> (+42.85%)
8.00 <0.00> (+3.00)

... and 14 more


Prefer named sink args to prevent overriding defaults set with show rule

https://github.com/tingerrr/subpar/blob/cac5e0763f773fd8290db815839a9f9e8ea18cf3/src/lib.typ#L114-L115
By defining these to have a default value through the function signature, and passing them directly to figure, any values set through set/show rules are overridden. Taking sink arguments and destructuring named arguments into the parent figure should suitably retain control without applying defaults.

Hmm, I guess this makes sense to some degree. I initially went this route to ensure I can easily replicate the exact API of figure, from the allowed arguments to the type validation.
I'll probably change it then.


Hmmm… can't reach this page

Hi,
The below link is not working. Getting "Hmmm… can't reach this page"
Comparison of JavaScript Frameworks
https://jsreport.io/the-ultimate-guide-to-javascript-frameworks/
Thanks,
Mohan
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 1ad8df5d-9295-d659-a561-ec9cabd5b61f
Version Independent ID: 7ee71103-d997-140e-2d35-d9f2a3913e09
Content: Choose between traditional web apps and single page apps
Content Source: docs/architecture/modern-web-apps-azure/choose-between-traditional-web-and-single-page-apps.md
Product: dotnet-architecture
Technology: modern-web-apps-azure
GitHub Login: @ardalis
Microsoft Alias: wiwagn

I found it archived in WayBack Machine. Not sure whether the docs should use this link?

Hi @kumarmohe - thanks for posting this issue. I think we could just replace the comparison link to another SPA reference.


add some info of how to contribute to create-graphql

Current coverage is 46.82% (diff: 100%)

Merging #11 into master will not change coverage

@@             master        #11   diff @@
==========================================
  Files            12         12
  Lines           173        173
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits             81         81
  Misses           92         92
  Partials          0          0

Powered by Codecov. Last update b1678e4...a550168

Awesome, thank you!

Feel free to move this to that file


VRV.co

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like this: [x])
Use the Preview tab to see what your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2018.03.20. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[ x] I've verified and I assure that I'm running youtube-dl 2018.03.20

Before submitting an issue make sure you have:

[x ] At least skimmed through the README, most notably the FAQ and BUGS sections
[ x] Searched the bugtracker for similar issues including closed ones
[ x] Checked that provided video/audio/playlist URLs (if any) are alive and playable in a browser

What is the purpose of your issue?

[x ] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add the -v flag to your command line you run youtube-dl with (youtube-dl -v <your command line>), copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'-v', u'http://www.youtube.com/watch?v=BaW_jenozKcj']
[debug] Encodings: locale cp1251, fs mbcs, out cp866, pref cp1251
[debug] youtube-dl version 2018.03.20
[debug] Python version 2.7.11 - Windows-2003Server-5.2.3790-SP2
[debug] exe versions: ffmpeg N-75573-g1d0487f, ffprobe N-75573-g1d0487f, rtmpdump 2.4
[debug] Proxy map: {}
...
<end of log>

If the purpose of this issue is a site support request please provide all kinds of example URLs support for which should be included (replace following example URLs by yours):

Single video: https://www.youtube.com/watch?v=BaW_jenozKc
Single video: https://youtu.be/BaW_jenozKc
Playlist: https://www.youtube.com/playlist?list=PL4lCao7KL_QFVb7Iudeipvc2BCavECqzc

Note that youtube-dl does not support sites dedicated to copyright infringement. In order for site support request to be accepted all provided example URLs should not violate any copyrights.

Description of your issue, suggested solution and other information
Unable to use youtube-dl on VRV.co for shows requiring an account even when passing login through cookies.
In this test I am not able to download Black Clover as a Series or on a per episode basis.
Series:
[03/20/18 22:08:39]
[03/20/18 22:23:28] [debug] System config: []
[03/20/18 22:23:28] [debug] User config: []
[03/20/18 22:23:28] [debug] Custom config: []
[03/20/18 22:23:28] [debug] Command-line args: ['--newline', '-i', '-o', 'C:\\Users\\tetra\\%(title)s.%(ext)s', '-f', 'mp4', '-v', '--ignore-config', '--hls-prefer-native', '--cookies', 'C:\\Users\\tetra\\Downloads\\Youtube-DL\\cookies.txt', 'https://vrv.co/series/GR2PQVD7R/Black-Clover']
[03/20/18 22:23:28] [debug] Encodings: locale cp1252, fs mbcs, out cp1252, pref cp1252
[03/20/18 22:23:28] [debug] youtube-dl version 2018.03.20
[03/20/18 22:23:28] [debug] Python version 3.4.4 (CPython) - Windows-10-10.0.16299
[03/20/18 22:23:28] [debug] exe versions: ffmpeg 3.3.2, ffprobe 3.3.2
[03/20/18 22:23:28] [debug] Proxy map: {}
[03/20/18 22:23:28] ERROR: Unable to download JSON metadata: HTTP Error 401: Unauthorized (caused by HTTPError()); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
[03/20/18 22:23:28]   File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpbt_jbnlh\build\youtube_dl\extractor\common.py", line 519, in _request_webpage
[03/20/18 22:23:28]   File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpbt_jbnlh\build\youtube_dl\YoutubeDL.py", line 2199, in urlopen
[03/20/18 22:23:28]   File "C:\Python\Python34\lib\urllib\request.py", line 470, in open
[03/20/18 22:23:28]   File "C:\Python\Python34\lib\urllib\request.py", line 580, in http_response
[03/20/18 22:23:28]   File "C:\Python\Python34\lib\urllib\request.py", line 508, in error
[03/20/18 22:23:28]   File "C:\Python\Python34\lib\urllib\request.py", line 442, in _call_chain
[03/20/18 22:23:28]   File "C:\Python\Python34\lib\urllib\request.py", line 588, in http_error_default
[03/20/18 22:23:28]

Episode:
[03/20/18 22:23:28]
[03/20/18 22:27:48] [debug] System config: []
[03/20/18 22:27:48] [debug] User config: []
[03/20/18 22:27:48] [debug] Custom config: []
[03/20/18 22:27:48] [debug] Command-line args: ['--newline', '-i', '-o', 'C:\\Users\\tetra\\%(title)s.%(ext)s', '-f', 'mp4', '-v', '--ignore-config', '--hls-prefer-native', '--cookies', 'C:\\Users\\tetra\\Downloads\\Youtube-DL\\cookies.txt', 'https://vrv.co/watch/GR2PQJ32R/Black-Clover:A-Young-Mans-Vow']
[03/20/18 22:27:48] [debug] Encodings: locale cp1252, fs mbcs, out cp1252, pref cp1252
[03/20/18 22:27:48] [debug] youtube-dl version 2018.03.20
[03/20/18 22:27:48] [debug] Python version 3.4.4 (CPython) - Windows-10-10.0.16299
[03/20/18 22:27:48] [debug] exe versions: ffmpeg 3.3.2, ffprobe 3.3.2
[03/20/18 22:27:48] [debug] Proxy map: {}
[03/20/18 22:27:48] ERROR: An extractor error has occurred. (caused by KeyError('streams',)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
[03/20/18 22:27:48] Traceback (most recent call last):
[03/20/18 22:27:48]   File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpbt_jbnlh\build\youtube_dl\extractor\common.py", line 440, in extract
[03/20/18 22:27:48]   File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpbt_jbnlh\build\youtube_dl\extractor\vrv.py", line 110, in _real_extract
[03/20/18 22:27:48] KeyError: 'streams'
[03/20/18 22:27:48] Traceback (most recent call last):
[03/20/18 22:27:48]   File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpbt_jbnlh\build\youtube_dl\extractor\common.py", line 440, in extract
[03/20/18 22:27:48]   File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpbt_jbnlh\build\youtube_dl\extractor\vrv.py", line 110, in _real_extract
[03/20/18 22:27:48] KeyError: 'streams'
[03/20/18 22:27:48]
[03/20/18 22:27:48] During handling of the above exception, another exception occurred:
[03/20/18 22:27:48]
[03/20/18 22:27:48] Traceback (most recent call last):
[03/20/18 22:27:48]   File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpbt_jbnlh\build\youtube_dl\YoutubeDL.py", line 785, in extract_info
[03/20/18 22:27:48]   File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpbt_jbnlh\build\youtube_dl\extractor\common.py", line 453, in extract
[03/20/18 22:27:48] youtube_dl.utils.ExtractorError: An extractor error has occurred. (caused by KeyError('streams',)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
[03/20/18 22:27:48]

This is related to https://github.com/rg3/youtube-dl/issues/14307.

Duplicate of #14307.


Update supported-technologies.asciidoc

Added reference to 32-bit and 64-bit for Java versions for clarification
Per discussion with @eyalkoren, as long as the supported Java version is used, both 32-bit and 64-bit Java should work.

Codecov Report

Merging #715 into master will decrease coverage by 4.34%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #715      +/-   ##
============================================
- Coverage     66.52%   62.17%   -4.35%
+ Complexity       85       68      -17
============================================
  Files           209      199      -10
  Lines          9325     7726    -1599
  Branches       1307      948     -359
============================================
- Hits           6203     4804    -1399
+ Misses         2775     2625     -150
+ Partials        347      297      -50

Impacted Files
Coverage Δ
Complexity Δ

...va/co/elastic/apm/agent/impl/payload/Language.java
66.66% <0%> (-33.34%)
0% <0%> (ø)

...co/elastic/apm/agent/impl/payload/RuntimeInfo.java
66.66% <0%> (-33.34%)
0% <0%> (ø)

...iguration/PrefixingConfigurationSourceWrapper.java
41.66% <0%> (-16.67%)
0% <0%> (ø)

...astic/apm/agent/report/ApmServerHealthChecker.java
43.58% <0%> (-12.78%)
0% <0%> (ø)

...a/co/elastic/apm/agent/report/ReporterFactory.java
76.92% <0%> (-8.38%)
0% <0%> (ø)

.../apm/agent/report/serialize/DslJsonSerializer.java
83.52% <0%> (-7.78%)
0% <0%> (ø)

...ic/apm/agent/servlet/ServletTransactionHelper.java
76.38% <0%> (-6.29%)
0% <0%> (ø)

.../co/elastic/apm/agent/impl/payload/SystemInfo.java
79.61% <0%> (-5.91%)
0% <0%> (ø)

...lastic/apm/agent/impl/ElasticApmTracerBuilder.java
73.21% <0%> (-5.8%)
0% <0%> (ø)

...astic/apm/agent/impl/transaction/AbstractSpan.java
75.67% <0%> (-5.5%)
0% <0%> (ø)

... and 34 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7865146...bfa1f4f. Read the comment docs.

Thanks @ppf2 !
We are a bit disinclined to add this, as we are not adding anything regarding the required OS.
Since we only work in the bytecode level, we are under the assumption that using a supported JVM is good enough, regardless of the OS. If we find out we have a specific issue with a specific OS, we will probably add that.


Can't find keyplane that supports type 5 for keyboard

Hi,
I'm using a numeric keyboard for a specific input the first time I tap to use it, it takes a lot of time to show up. Meanwhile the console spits out:
Can't find keyplane that supports type 5 for keyboard iPhone-Portrait-NumberPad; using<PHONE_NUMBER>_Portrait_iPhone-Simple-Pad_Default
I've updated Ionic Keyboard to 1.0.4 and still get the error.

Duplicate of: https://github.com/driftyco/ionic-plugins-keyboard/issues/48.


Extracting a subgraph as comprehensively as possible is to be explored.

This follows https://github.com/DDMAL/linkedmusic-datalake/issues/161, where "subgraph extraction SPARQL" is referable.
I mean “not omitting” any potential properties or classes from an oversized ontology by "as comprehensively as possible".

Some SPARQL strategies for retrieving entities in an ontology is available here: https://github.com/candlecao/Chinese-Traditional-Music-Culture-Knowledge-Base_Cooperation/wiki/A-demonstration-of-SPARQL-query-against-the-OWL-file-which-is-the-ontology-for-"ChineseTraditionalMusicCultureKnowledgeBase"(CTM)

I have been experimenting on the ontology of Chinese Traditional Music (CTM) Knowledge Base these days, which (CTM) can be accessed from the http://www.usources.cn:8891/sparql SPARQL endpoint and Default Data Set Name (Graph IRI) https://lib.ccmusic.edu.cn/graph/music_inf

CTM's Ontology is a typical example as it demonstrates various practical applicaitons of OWL semantics.

For the LinkedMusic Data Lake, the current reconciliation process does not yield a complete ontology. One reason is that some entity types for property values lack assertions. This may need to be discussed as a future issue for resolution.

Alternatively, of course, we can manually define the ontology for each reconciled and converted DB.

This is solved from another issue.


"HTTPS Port" content placed in row instead of column

As in the title, section "HTTPS Port" under the "Host configuration values" has specification content placed in row instead of column

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

ID: 04eafd1b-403a-4aa3-48bc-78fed5b4d05e
Version Independent ID: f35451f4-7c74-3ada-e969-b769428b94f4
Content: ASP.NET Core Web Host
Content Source: aspnetcore/fundamentals/host/web-host.md
Product: aspnet-core
Technology: aspnetcore-fundamentals
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

Thanks @oreze ... I'll patch that up ... it's a quick fix. Two spaces at the of a line signifies to the doc build engine to drop in a
; but on some edit of the file, the doc author removed (or didn't add) the double spaces at the ends of these lines ... so no
s were added to them.


Fullchain.pem expired / force renewal doesn't renew

So, just recently i've been getting curl certificate expired errors on my ubuntu 14.04 server, however it works just fine on any other server, including my local machine
curl: (60) SSL certificate problem: certificate has expired
A bit of investigating, I believe that the Intermediate has expired or is invalid, whynopadlock result shows that, along with /app/cert_status command showing that the fullchain.pem has expired, force renewing doesn't seem to fix the issue, it 100% renews the certificate however.
##### Certificate status #####
/etc/nginx/certs/domain/fullchain.pem: EXPIRED
Certificate was issued by R3
Certificate was valid until Jan  9 05:04:47 2022 GMT
Subject Name:
- domain
Certificate is used by the following domain(s):
- domain

Info: running acme-companion version v2.1.0-28-g1785bc5
version: '2'
services:
  nginx-proxy:
    image: nginxproxy/nginx-proxy:alpine
    container_name: nginx-proxy
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - conf:/etc/nginx/conf.d
      - vhost:/etc/nginx/vhost.d
      - html:/usr/share/nginx/html
      - dhparam:/etc/nginx/dhparam
      - certs:/etc/nginx/certs:ro
      - /var/run/docker.sock:/tmp/docker.sock:ro

  nginx-proxy-letsencrypt:
    image: nginxproxy/acme-companion
    container_name: nginx-proxy-letsencrypt
    volumes_from:
      - nginx-proxy
    volumes:
      - certs:/etc/nginx/certs:rw
      - acme:/etc/acme.sh
      - /var/run/docker.sock:/var/run/docker.sock:ro
    environment:
      - DEFAULT_EMAIL=

  whoami:
    image: jwilder/whoami
    environment:
      - VIRTUAL_HOST=whoami.local

volumes:
  conf:
  vhost:
  html:
  dhparam:
  certs:
  acme:

rendered nginx configuration
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
# configuration file /etc/nginx/nginx.conf:

user  nginx;
worker_processes  auto;

error_log  /var/log/nginx/error.log notice;
pid        /var/run/nginx.pid;

events {
    worker_connections  10240;
}

http {
    include       /etc/nginx/mime.types;
    default_type  application/octet-stream;

    log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
                      '$status $body_bytes_sent "$http_referer" '
                      '"$http_user_agent" "$http_x_forwarded_for"';

    access_log  /var/log/nginx/access.log  main;

    sendfile        on;
    #tcp_nopush     on;

    keepalive_timeout  65;

    #gzip  on;

    include /etc/nginx/conf.d/*.conf;
}
daemon off;

# configuration file /etc/nginx/mime.types:

types {
    text/html                                        html htm shtml;
    text/css                                         css;
    text/xml                                         xml;
    image/gif                                        gif;
    image/jpeg                                       jpeg jpg;
    application/javascript                           js;
    application/atom+xml                             atom;
    application/rss+xml                              rss;

    text/mathml                                      mml;
    text/plain                                       txt;
    text/vnd.sun.j2me.app-descriptor                 jad;
    text/vnd.wap.wml                                 wml;
    text/x-component                                 htc;

    image/png                                        png;
    image/svg+xml                                    svg svgz;
    image/tiff                                       tif tiff;
    image/vnd.wap.wbmp                               wbmp;
    image/webp                                       webp;
    image/x-icon                                     ico;
    image/x-jng                                      jng;
    image/x-ms-bmp                                   bmp;

    font/woff                                        woff;
    font/woff2                                       woff2;

    application/java-archive                         jar war ear;
    application/json                                 json;
    application/mac-binhex40                         hqx;
    application/msword                               doc;
    application/pdf                                  pdf;
    application/postscript                           ps eps ai;
    application/rtf                                  rtf;
    application/vnd.apple.mpegurl                    m3u8;
    application/vnd.google-earth.kml+xml             kml;
    application/vnd.google-earth.kmz                 kmz;
    application/vnd.ms-excel                         xls;
    application/vnd.ms-fontobject                    eot;
    application/vnd.ms-powerpoint                    ppt;
    application/vnd.oasis.opendocument.graphics      odg;
    application/vnd.oasis.opendocument.presentation  odp;
    application/vnd.oasis.opendocument.spreadsheet   ods;
    application/vnd.oasis.opendocument.text          odt;
    application/vnd.openxmlformats-officedocument.presentationml.presentation
                                                     pptx;
    application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
                                                     xlsx;
    application/vnd.openxmlformats-officedocument.wordprocessingml.document
                                                     docx;
    application/vnd.wap.wmlc                         wmlc;
    application/wasm                                 wasm;
    application/x-7z-compressed                      7z;
    application/x-cocoa                              cco;
    application/x-java-archive-diff                  jardiff;
    application/x-java-jnlp-file                     jnlp;
    application/x-makeself                           run;
    application/x-perl                               pl pm;
    application/x-pilot                              prc pdb;
    application/x-rar-compressed                     rar;
    application/x-redhat-package-manager             rpm;
    application/x-sea                                sea;
    application/x-shockwave-flash                    swf;
    application/x-stuffit                            sit;
    application/x-tcl                                tcl tk;
    application/x-x509-ca-cert                       der pem crt;
    application/x-xpinstall                          xpi;
    application/xhtml+xml                            xhtml;
    application/xspf+xml                             xspf;
    application/zip                                  zip;

    application/octet-stream                         bin exe dll;
    application/octet-stream                         deb;
    application/octet-stream                         dmg;
    application/octet-stream                         iso img;
    application/octet-stream                         msi msp msm;

    audio/midi                                       mid midi kar;
    audio/mpeg                                       mp3;
    audio/ogg                                        ogg;
    audio/x-m4a                                      m4a;
    audio/x-realaudio                                ra;

    video/3gpp                                       3gpp 3gp;
    video/mp2t                                       ts;
    video/mp4                                        mp4;
    video/mpeg                                       mpeg mpg;
    video/quicktime                                  mov;
    video/webm                                       webm;
    video/x-flv                                      flv;
    video/x-m4v                                      m4v;
    video/x-mng                                      mng;
    video/x-ms-asf                                   asx asf;
    video/x-ms-wmv                                   wmv;
    video/x-msvideo                                  avi;
}

# configuration file /etc/nginx/conf.d/default.conf:
# If we receive X-Forwarded-Proto, pass it through; otherwise, pass along the
# scheme used to connect to this server
map $http_x_forwarded_proto $proxy_x_forwarded_proto {
  default $http_x_forwarded_proto;
  ''      $scheme;
}
# If we receive X-Forwarded-Port, pass it through; otherwise, pass along the
# server port the client connected to
map $http_x_forwarded_port $proxy_x_forwarded_port {
  default $http_x_forwarded_port;
  ''      $server_port;
}
# If we receive Upgrade, set Connection to "upgrade"; otherwise, delete any
# Connection header that may have been passed to this server
map $http_upgrade $proxy_connection {
  default upgrade;
  '' close;
}
# Apply fix for very long server names
server_names_hash_bucket_size 128;
# Default dhparam
ssl_dhparam /etc/nginx/dhparam/dhparam.pem;
# Set appropriate X-Forwarded-Ssl header based on $proxy_x_forwarded_proto
map $proxy_x_forwarded_proto $proxy_x_forwarded_ssl {
  default off;
  https on;
}
gzip_types text/plain text/css application/javascript application/json application/x-javascript text/xml application/xml application/xml+rss text/javascript;
log_format vhost '$host $remote_addr - $remote_user [$time_local] '
                 '"$request" $status $body_bytes_sent '
                 '"$http_referer" "$http_user_agent" '
                 '"$upstream_addr"';
access_log off;
                ssl_protocols TLSv1.2 TLSv1.3;
                ssl_ciphers 'ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384';
                ssl_prefer_server_ciphers off;
resolver <IP_ADDRESS>;
# HTTP 1.1 support
proxy_http_version 1.1;
proxy_buffering off;
proxy_set_header Host $http_host;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $proxy_connection;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $proxy_x_forwarded_proto;
proxy_set_header X-Forwarded-Ssl $proxy_x_forwarded_ssl;
proxy_set_header X-Forwarded-Port $proxy_x_forwarded_port;
# Mitigate httpoxy attack (see README for details)
proxy_set_header Proxy "";
server {
        server_name _; # This is just an invalid value which will never trigger on a real hostname.
        server_tokens off;
        listen 80;
        access_log /var/log/nginx/access.log vhost;
        return 503;
}
server {
        server_name _; # This is just an invalid value which will never trigger on a real hostname.
        server_tokens off;
        listen 443 ssl http2;
        access_log /var/log/nginx/access.log vhost;
        return 503;
        ssl_session_cache shared:SSL:50m;
        ssl_session_tickets off;
        ssl_certificate /etc/nginx/certs/default.crt;
        ssl_certificate_key /etc/nginx/certs/default.key;
}
# domain
upstream domain {
        ## Can be connected with "nginx-proxy_default" network
        # domain_nginx_1
        server <IP_ADDRESS>:80;
}
server {
        server_name domain;
        listen 80 ;
        access_log /var/log/nginx/access.log vhost;
        # Do not HTTPS redirect Let'sEncrypt ACME challenge
        location ^~ /.well-known/acme-challenge/ {
                auth_basic off;
                auth_request off;
                allow all;
                root /usr/share/nginx/html;
                try_files $uri =404;
                break;
        }
        location / {
                return 301 https://$host$request_uri;
        }
}
server {
        server_name domain;
        listen 443 ssl http2 ;
        access_log /var/log/nginx/access.log vhost;
        ssl_session_timeout 5m;
        ssl_session_cache shared:SSL:50m;
        ssl_session_tickets off;
        ssl_certificate /etc/nginx/certs/domain.crt;
        ssl_certificate_key /etc/nginx/certs/domain.key;
        ssl_dhparam /etc/nginx/certs/domain.dhparam.pem;
        ssl_stapling on;
        ssl_stapling_verify on;
        ssl_trusted_certificate /etc/nginx/certs/domain.chain.pem;
        add_header Strict-Transport-Security "max-age=31536000" always;
        include /etc/nginx/vhost.d/default;
        location / {
                proxy_pass http://domain;
        }
}
# whoami.local
upstream whoami.local {
        ## Can be connected with "nginx-proxy_default" network
        # nginx-proxy_whoami_1
        server <IP_ADDRESS>:8000;
}
server {
        server_name whoami.local;
        listen 80 ;
        access_log /var/log/nginx/access.log vhost;
        include /etc/nginx/vhost.d/default;
        location / {
                proxy_pass http://whoami.local;
        }
}
server {
        server_name whoami.local;
        listen 443 ssl http2 ;
        access_log /var/log/nginx/access.log vhost;
        return 500;
        ssl_certificate /etc/nginx/certs/default.crt;
        ssl_certificate_key /etc/nginx/certs/default.key;
}

# configuration file /etc/nginx/vhost.d/default:
## Start of configuration add by letsencrypt container
location ^~ /.well-known/acme-challenge/ {
    auth_basic off;
    auth_request off;
    allow all;
    root /usr/share/nginx/html;
    try_files $uri =404;
    break;
}
## End of configuration add by letsencrypt container

I have the same issue and still could not figure out if it is related to this project or not.
docker exec letsencrypt /app/cert_status shows all certificates as expired however force renewal works all certificates are getting renewed. I use docker so the server being old should not be an issue.

@gurumark @fluffyst nginxproxy/acme-companion:2.1.1 has been updated to use a newer version of acme.sh (2.8.8 -> 2.9.0), could you test again with this version of the container ?

Didn't fix it for me at least. I've got the same phenomenon, that cert_status shows all fullchains as expired (Certificate was valid until Mar 5 2022), but I don't have any other issues besides that. The certificates and the renewal seems to work as usual.
It doesn't seem to make a difference if I use ACME_PREFERRED_CHAIN on a container or not. I'm on a fully updated Ubuntu 20.04 machine with the latest images.

Did someone find the fix for this? I'm facing the same issue with the fullchain.pem file

The only way to show the fullchain as OK instead of expired is to manually edit the fullchain.pem and remove the last cert in the chain.

Just to clarify: the cert_status function is a small utility that was hastily written a while ago, it's not meant to actually reflect the internal state of acme.sh in any way.
I know the preferred chain stuff has been an issue on the acme.sh side for a while, the more recent version 3.x might finally solve this but I'll have to check a few things before bumping to this version. It's fairly easy to locally build an acme-companion image with a different version of acme.sh, I can provide instructions for this if needed.

Since one year I'm running a mailcow-dockerized behind nginx-proxy.
Today I'm facing exactly this issue myself from one day to the other.
In my case IMAPS does not work anymore.
openssl connection to the server returns: certificate has expired
force renewal works but cert_status on my mailserver says that fullchain.pem has exired and:
"Certificate was valid until Jun 22 06:06:14 2022 GMT"
really strange

Hi, isn't this caused by the DST Root CA X3 expiration ?

I think that is so. I've created an issue on the Let's Encrypt forum. And they suggested a solution.
I tried to find a solution myself, and the following is probably not needed anymore, but just in case, to extract the first certificate from a file:
$ awk '/BEGIN/{if (matched) exit; else matched=1}; {print}' < /etc/nginx/certs/example.com/chain.pem | less


represent "deprecated" as owl:deprecated

Various terms have a stereotype "deprecated", eg
dcterms:creator  rdf:type  rdf:Property ;
        rdfs:comment       "... This property is deprecated. Use dcterms:publisher.]." ;
        cims:stereotype    "deprecated" , "dcterms" ;

[ ] Represent this in a standard way

dcterms:creator
  owl:deprecated true

[ ] Then it would also be nice to delete this value from cims:stereotype, so it has fewer free-text values.

Here's a count per ontology:
grep -c '"deprecated"' *.ttl|grep -v ':0'
EquipmentReliability-AP-Voc-RDFS2020.ttl:1
Header-AP-Voc-RDFS2020.ttl:9
ObjectRegistry-AP-Voc-RDFS2020.ttl:2

I like this. Originally it should have the same meaning. However, is this the relevant link to the definition: https://www.w3.org/TR/owl-ref/#Deprecation

The up-to-date spec is OWL2: https://www.w3.org/TR/2012/REC-owl2-syntax-20121211/#a_deprecated
This is useful to find OWL2 stuff:  https://www.w3.org/TR/owl2-quick-reference/

[ ] must also count in CGMES ontologies (above is NC)

Updated count:
grep -rc '"deprecated"' |grep -v ':0'
CGMES/ttl/61970-600-2_Equipment-AP-Voc-RDFS2020_v3-0-0.ttl:7
CGMES/ttl/61970-600-2_EquipmentBoundary-AP-Voc-RDFS2020_v3-0-0.ttl:2
CGMES/ttl/61970-600-2_Topology-AP-Voc-RDFS2020_v3-0-0.ttl:2
CGMES-NC/ttl/EquipmentReliability-AP-Voc-RDFS2020.ttl:1
CGMES-NC/ttl/ObjectRegistry-AP-Voc-RDFS2020.ttl:2

So 13 occurrences.
A query shows this is used on 7 props:
PREFIX cims: <http://iec.ch/TC57/1999/rdf-schema-extensions-19990926#>
select * {
  ?p cims:stereotype "deprecated"
}

p

eu: IdentifiedObject.energyIdentCodeEic

eu: IdentifiedObject.shortName

cim: SVCControlMode

cim: PhaseTapChangerLinear.xMin

cim: PhaseTapChangerNonLinear.xMin

cim: StaticVarCompensator.sVCControlMode

cim: StaticVarCompensator.voltageSetPoint

Done in fix15-deprecated-24.ru.
Assigning to @Sveino @griddigit-ci to answer why EIC is deprecated?

We would like to remove eu namespace. We are creating an ObjectRegisry profile that can handle multiple names and identification on the same object. My proposal (but not yet approved) is:

eu: IdentifiedObject.energyIdentCodeEic -> cim:Name.name and cim:Name.kind = eIC

Until this proposal is accepted, how can one record EICs? I think you should deprecate it AFTER the proposal is acceped
For all deprecated props, please describe the reason for deprecation: in skos:scopeNote, or simply in rdfs:comment


[Hero] Invokers sister

Lore:
Invokers modest sister. 'Nuff.
Mechanix:
the first cast determines the effect of the spell (select),
the second the form (cast); so order matters above all.
The spell is cast when the second skill was cast, no targeting required.
Her ult shoudl be considered a regular spell (like Udyr in the unnamed game)
After selecting a spell you should have several seconds to chose a form (cast)
The selected ability should be disabled until you cast it, so QQ/WW/EE/RR combinations are not allowed.
I've tried to create the skill orders in the examples in a way that will not result in strictly better spells.
Your damaging spells are: a skillshot (RQ), a close-target self damaging spell (RW) and a dash-attack (RE); I've made sure that you cant do the large aoe dmg - 'cuz thats not interesting.
With the same logic you can't do: debuffs in a line, heal yourself (and the nearest ally), buff allies after the dash.
On second thought it might be an okay Aghanim's upgrade, to allow duplicate skillcasts  such as QQ.
Using the below examples:

if you cast R then Q you will fire a "missile" ahead and behind damaging enemies
if you cast E then W you will buff yourself and the nearest ally (like Sona W in the unnamed game)

effect examples (first cast - select):
Q: debuff  | affects enemies | armor, mspd, stat, healing, disarm, break, mute
W: heal    | affects allies  |
E: buff    | affects allies  | armor, mspd, stat, healing, aspd, mrez
R: damage  | affects enemies |
forms examples (second cast - cast):
Q: forward and backward projectile                         | magic damage
W: nearest ally+self / enemy                               | pure damage
E: dash forward and "attack" in a short wide cone in fornt | physical  damage
R: circle aoe, self center                                 | magic damage

Neat idea but have same problem as invoker had, a lot of this feels kike a filler spells

One little sligthly kinda probably one of mayby most important things, TALENT TREE


Update title of Pipeline window for accessibility purpose

Screen reader users identify the currently open application from the title of the active window.
Both Pipeline UI and command line has the same title "DAISY Pipeline".
We should differentiate the title of UI a little. Something like DAISY Pipeline app.

The window is now called "DAISY Pipeline (2023) - App"


NIFI-3229 When a queue contains only Penalized FlowFile's the next pr…

…ocessor Tasks/Time statistics becomes extremely large
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

[x] Is your initial contribution a single, squashed commit?

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

@patricker thanks for the PR! I had gone down this path before but I backed out the changes. The changes in this PR will result in obtaining a Write Lock on the queue of every incoming connection for every running processor in the graph. This can become quite expensive for a complex flow that is made up of thousands (or even 10's of thousands) of processors) and result in overall system performance suffering. This is why we are so care in the FlowFile Queue's implementation to ensure that isActiveQueueEmpty() never obtains a lock but instead only references AtomicReference variables.
We should be able to do better, though. For example, when we pull a FlowFile from the queue, we check if it's penalized. If so, we throw it back on. Since the queue is ordered, we could do some smart things like looking at the FlowFile expiration date, then keeping track of the fact that we know all FlowFiles are penalized until that time is reached - or until a non-penalized FlowFile is added to the queue.

@markap14 I was worried about the same thing, which is why the if statement is structured as it is. First, we do the standard check on isActiveQueueEmpty. This happens in the code now as you mentioned, and right now if this passes we create a writelock update the queue and call the processor.
All my change does is add one additional check, but only if the queue is not empty. So as far as I can tell, I'm locking one extra time for a queue that is already going to get locked, but not locking any queues that would not already get locked. Also, because I'm updating the queue during my check, when the processor does get called the lock should not last as long as it would otherwise, as there is less work to do. So overall lock time should be affected only minimally. Thoughts?

@patricker you're right - it may perform just fine. However, the concern is not that we are holding a lock longer but rather that we are obtaining it twice as often now when there's data queued. The acquisition of the lock itself can be expensive. So all I am suggesting is that we don't want to make such a change without knowing how it's going to affect things. We'd want to gather some performance numbers before and after this changeset is applied.
Specifically, I'd want to setup a test suite that calculates things like:
How long does it take to check if there are FlowFiles queued 10 million times when there are no FlowFiles queued?
How long does it take to check if there are FlowFiles queued 10 million times when there are FlowFiles queued?
How do these numbers change when you have 1 thread vs. 2 threads vs. 12 threads vs. 25 threads?
I'd want to run these tests 10-20 times in a row to ensure that the numbers are steady, and then get these numbers before and after the changeset is applied.
If the worst-case differs by say 5% then it's probably fine. If the worse case differs by say 50% then it probably makes sense to look for a different solution.

@markap14 I built unit tests, but I'm having trouble running them at scale. I temporarily checked back in the original method so I could run side-by-side speed comparisons on the same Connectable. But if I exceed about 100k tests my unit tests seem to go out to lunch, even if I increase heap so they don't run out.
These are checked in right now to run 1 million iterations, but that has not succeeded for me... This is true of the unmodified method if run by itself also (at least on my poor little computer).

Hey @patricker sorry for the delay in getting back to this. I looked into the unit tests, and did some quick profiling. It looks like the reason that it seemed to "go out to lunch" as you say was because of Mockito objects being used. They are super useful but don't provide great performance. I updated the test so that instead of using Mockito it just created simple objects like Funnels or implemented interfaces directly without much of anything happening. That resulted in much better performance.
I updated the test about to run in multiple threads, as well, because this is where we are going to see the heavy contention and therefore the performance concerns. When I run with a single thread, we see pretty comparable results between the existing implementation and the new implementation that checks for penalization:

1M checks for FlowFiles, non-empty queue: 57 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 101 millis
1M checks for FlowFiles, non-empty queue: 47 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 67 millis
1M checks for FlowFiles, non-empty queue: 60 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 77 millis
1M checks for FlowFiles, non-empty queue: 38 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 66 millis
1M checks for FlowFiles, non-empty queue: 34 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 54 millis
1M checks for FlowFiles, non-empty queue: 28 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 91 millis
1M checks for FlowFiles, non-empty queue: 67 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 96 millis
1M checks for FlowFiles, non-empty queue: 35 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 59 millis
1M checks for FlowFiles, non-empty queue: 29 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 55 millis
1M checks for FlowFiles, non-empty queue: 36 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 50 millis

The difference is measurable but not necessarily concerning.
At 2 threads, the performance is more concerning but still not necessarily a deal breaker:

1M checks for FlowFiles, non-empty queue: 314 millis
1M checks for FlowFiles, non-empty queue: 315 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 4 seconds, 410 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 4 seconds, 412 millis
1M checks for FlowFiles, non-empty queue: 240 millis
1M checks for FlowFiles, non-empty queue: 240 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 4 seconds, 166 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 4 seconds, 167 millis
1M checks for FlowFiles, non-empty queue: 235 millis
1M checks for FlowFiles, non-empty queue: 236 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 4 seconds, 510 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 4 seconds, 510 millis
1M checks for FlowFiles, non-empty queue: 225 millis
1M checks for FlowFiles, non-empty queue: 227 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 3 seconds, 994 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 3 seconds, 995 millis
1M checks for FlowFiles, non-empty queue: 239 millis
1M checks for FlowFiles, non-empty queue: 239 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 4 seconds, 102 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 4 seconds, 102 millis
1M checks for FlowFiles, non-empty queue: 229 millis
1M checks for FlowFiles, non-empty queue: 231 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 4 seconds, 634 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 4 seconds, 634 millis
1M checks for FlowFiles, non-empty queue: 234 millis
1M checks for FlowFiles, non-empty queue: 235 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 3 seconds, 732 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 3 seconds, 732 millis
1M checks for FlowFiles, non-empty queue: 231 millis
1M checks for FlowFiles, non-empty queue: 233 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 4 seconds, 252 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 4 seconds, 253 millis
1M checks for FlowFiles, non-empty queue: 231 millis
1M checks for FlowFiles, non-empty queue: 231 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 4 seconds, 195 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 4 seconds, 195 millis
1M checks for FlowFiles, non-empty queue: 235 millis
1M checks for FlowFiles, non-empty queue: 237 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 4 seconds, 89 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 4 seconds, 89 millis

However, when we update the test to use 12 threads, we see some results that are more concerning:

1M checks for FlowFiles, non-empty queue: 4 seconds, 430 millis
1M checks for FlowFiles, non-empty queue: 4 seconds, 463 millis
1M checks for FlowFiles, non-empty queue: 4 seconds, 486 millis
1M checks for FlowFiles, non-empty queue: 4 seconds, 331 millis
1M checks for FlowFiles, non-empty queue: 4 seconds, 316 millis
1M checks for FlowFiles, non-empty queue: 4 seconds, 484 millis
1M checks for FlowFiles, non-empty queue: 4 seconds, 517 millis
1M checks for FlowFiles, non-empty queue: 4 seconds, 357 millis
1M checks for FlowFiles, non-empty queue: 4 seconds, 357 millis
1M checks for FlowFiles, non-empty queue: 4 seconds, 349 millis
1M checks for FlowFiles, non-empty queue: 4 seconds, 478 millis
1M checks for FlowFiles, non-empty queue: 4 seconds, 372 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 31 seconds, 434 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 31 seconds, 434 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 31 seconds, 434 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 31 seconds, 434 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 31 seconds, 434 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 31 seconds, 434 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 31 seconds, 434 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 31 seconds, 434 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 31 seconds, 434 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 31 seconds, 434 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 31 seconds, 435 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 31 seconds, 434 millis
1M checks for FlowFiles, non-empty queue: 4 seconds, 142 millis
1M checks for FlowFiles, non-empty queue: 4 seconds, 422 millis
1M checks for FlowFiles, non-empty queue: 4 seconds, 444 millis
1M checks for FlowFiles, non-empty queue: 4 seconds, 513 millis
1M checks for FlowFiles, non-empty queue: 4 seconds, 520 millis
1M checks for FlowFiles, non-empty queue: 4 seconds, 567 millis
1M checks for FlowFiles, non-empty queue: 4 seconds, 572 millis
1M checks for FlowFiles, non-empty queue: 4 seconds, 579 millis
1M checks for FlowFiles, non-empty queue: 4 seconds, 587 millis
1M checks for FlowFiles, non-empty queue: 4 seconds, 586 millis
1M checks for FlowFiles, non-empty queue: 4 seconds, 582 millis
1M checks for FlowFiles, non-empty queue: 4 seconds, 594 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 21 seconds, 787 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 21 seconds, 787 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 21 seconds, 787 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 21 seconds, 787 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 21 seconds, 787 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 21 seconds, 787 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 21 seconds, 787 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 21 seconds, 787 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 21 seconds, 787 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 21 seconds, 787 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 21 seconds, 787 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 21 seconds, 787 millis
1M checks for FlowFiles, non-empty queue: 2 seconds, 755 millis
1M checks for FlowFiles, non-empty queue: 2 seconds, 772 millis
1M checks for FlowFiles, non-empty queue: 2 seconds, 777 millis
1M checks for FlowFiles, non-empty queue: 2 seconds, 780 millis
1M checks for FlowFiles, non-empty queue: 2 seconds, 794 millis
1M checks for FlowFiles, non-empty queue: 2 seconds, 804 millis
1M checks for FlowFiles, non-empty queue: 2 seconds, 813 millis
1M checks for FlowFiles, non-empty queue: 2 seconds, 819 millis
1M checks for FlowFiles, non-empty queue: 2 seconds, 819 millis
1M checks for FlowFiles, non-empty queue: 2 seconds, 807 millis
1M checks for FlowFiles, non-empty queue: 2 seconds, 810 millis
1M checks for FlowFiles, non-empty queue: 2 seconds, 802 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 10 seconds, 8 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 10 seconds, 9 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 10 seconds, 15 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 10 seconds, 15 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 10 seconds, 16 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 10 seconds, 15 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 10 seconds, 15 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 10 seconds, 16 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 10 seconds, 15 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 10 seconds, 15 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 10 seconds, 15 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 10 seconds, 16 millis
1M checks for FlowFiles, non-empty queue: 2 seconds, 469 millis
1M checks for FlowFiles, non-empty queue: 2 seconds, 481 millis
1M checks for FlowFiles, non-empty queue: 2 seconds, 479 millis
1M checks for FlowFiles, non-empty queue: 2 seconds, 521 millis
1M checks for FlowFiles, non-empty queue: 2 seconds, 544 millis
1M checks for FlowFiles, non-empty queue: 2 seconds, 553 millis
1M checks for FlowFiles, non-empty queue: 2 seconds, 575 millis
1M checks for FlowFiles, non-empty queue: 2 seconds, 566 millis
1M checks for FlowFiles, non-empty queue: 2 seconds, 581 millis
1M checks for FlowFiles, non-empty queue: 2 seconds, 582 millis
1M checks for FlowFiles, non-empty queue: 2 seconds, 583 millis
1M checks for FlowFiles, non-empty queue: 2 seconds, 572 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 19 seconds, 926 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 19 seconds, 960 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 19 seconds, 965 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 19 seconds, 965 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 19 seconds, 965 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 19 seconds, 965 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 19 seconds, 965 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 19 seconds, 965 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 19 seconds, 965 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 19 seconds, 965 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 19 seconds, 965 millis
1M checks for FlowFiles, non-penalized method, non-empty queue: 1 minutes, 19 seconds, 965 millis
1M checks for FlowFiles, non-empty queue: 2 seconds, 724 millis
1M checks for FlowFiles, non-empty queue: 2 seconds, 745 millis
1M checks for FlowFiles, non-empty queue: 2 seconds, 761 millis
1M checks for FlowFiles, non-empty queue: 2 seconds, 764 millis
1M checks for FlowFiles, non-empty queue: 2 seconds, 776 millis
1M checks for FlowFiles, non-empty queue: 2 seconds, 774 millis
1M checks for FlowFiles, non-empty queue: 2 seconds, 800 millis
1M checks for FlowFiles, non-empty queue: 2 seconds, 800 millis
1M checks for FlowFiles, non-empty queue: 2 seconds, 802 millis
1M checks for FlowFiles, non-empty queue: 2 seconds, 803 millis
1M checks for FlowFiles, non-empty queue: 2 seconds, 805 millis
1M checks for FlowFiles, non-empty queue: 2 seconds, 795 millis

So with 12 threads, each checking 1 million times, the difference in performance/latency goes from 2-3 seconds to 70-90 seconds.
We can also see what happens to the CPU utilization as it switches between the version that checks penalization and the one that doesn't:

So at one thread, I'm not concerned about the performance difference. But if you start adding several threads to a processor, the performance concern is definitely more significant and I think is concerning.


fuzz_calculate_max_short occasionally failing

---- short::max::tests::fuzz_calculate_max_short stdout ----
thread 'short::max::tests::fuzz_calculate_max_short' panicked at crates/hyperdrive-math/src/short/max.rs:742:17:
expected (base=70430895.800062968817706189) < (budget=70964720.871387510943216964) * 0.001000000000000000 = 70964.720871387510943216

I posted about a similar error here but closed that issue in favor of this dedicated one.

my testing shows a problem occurring in a specific range of fixed rates from about 100% to 300%:
Total tests: 17720 Both pass: 8496 Both fail: 8873 Mismatched: 351 Failure rate: 0.019808126410835215
Fuzzed over fixed rate from Some(FixedPoint(0.000385747703397417)) to Some(FixedPoint(399.625149689078101990))
Mismatched  fixed rate from Some(FixedPoint(3.131040290023483491)) to Some(FixedPoint(133.805637502892130607))

that's from wip draft pr #19

still get a 2% mismatch rate after #122 allows the test to run to the end
Total tests: 100,000 Both pass: 48,054 Both fail: 49,871 Mismatched: 2,075 Failure rate: 0.02075

looks like Rust succeeds when Solidity doesn't:
Fixed rate: 9.258702584950471355
MISMATCHED: actual: Ok(Ok(FixedPoint(44767131.875921600404760400))) expected: Revert(Bytes(0x4e487b710000000000000000000000000000000000000000000000000000000000000011))
Rust: FixedPoint(44767131.875921600404760400) Solidity: Revert(Bytes(0x4e487b710000000000000000000000000000000000000000000000000000000000000011))
Fixed rate: 5.460357484762586677
MISMATCHED: actual: Ok(Ok(FixedPoint(835897164.703558754582240549))) expected: Revert(Bytes(0x4e487b710000000000000000000000000000000000000000000000000000000000000011))

this result is on 989ad42c89e4b9179331f8b879e376a356433bca

Fuzz testing is seeing the following errors:

calculate_max_long

InsufficientLiquidity: Negative Interest
Initial guess in calculate_max_long is insolvent
target share reserves less than effective share reserves

calculate_max_short

absolute_max_short is insolvent
arithmetic operation overflow

The fuzz pool is initialized to a known-good state (@slundqui is 80% certain it is good based on visual inspection of the parameters from himself, Jonny, & Alex and comparison against rust CI tests).
Random bots make trades and call calc_max_long and calc_max_short at random times throughout.


Skype integration with Ionic framework as front-end and CodeIgniter as Backend

Sir, I need your guide, advice, and expertise on skype. I am to build a Hybrid Mobile App using Ionic Framework as Front-end and I will also use CodeIgniter as my backend. Is there any plugins or API for skype to run into my Hybrid Mobile App? I've search something about this in https://forum.ionicframework.com/t/open-skype-through-ionic-app/54580 but every time I serve (execute it) it will just open my Skype Desktop Application.
I only want to execute the call in my Mobile App only, it doesnt suppose to open a desktop application. I also search another and here it is https://forum.ionicframework.com/t/make-skype-call/48988/9 but again nothing happen.
Please sir, any links or guides?

@jb181991 any update on this thing ?
I am also looking for something similar, I want develop as native messenger app which uses SfB as its backend, I would be developing the UI for the data i get it from SfB server.
Thanks


Issue in "seldon-container-engine" with MLFLOW_SERVER

Hello Adrian,
Firstly thank you very much for the amazing talk on youtube and the source code for it.
I have an issue while running this content on my PC. I am using docker for desktop with K8 installed I exactly followed instructions in your jupyter notebook to set up seldon-core, seldon-analytics, and ambassador. I have my model in a remote Minio bucket. The initContainer classifier-model-initializer and the classifier executed successfully. I have a new issue in the "seldon-container-engine"
{"level":"info","ts":1591611950.8325408,"logger":"SeldonRestApi","msg":"Listening","Address":"<IP_ADDRESS>:8000"}
{"level":"error","ts":1591611965.4901059,"logger":"SeldonRestApi","msg":"Ready check failed","error":"dial tcp <IP_ADDRESS>:9000: connect: connection refused","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-logr/zapr@v0.1.0/zapr.go:128\ngithub.com/seldonio/seldon-core/executor/api/rest.(*SeldonRestApi).checkReady\n\t/workspace/api/rest/server.go:198\nnet/http.HandlerFunc.ServeHTTP\n\t/usr/local/go/src/net/http/server.go:2007\ngithub.com/seldonio/seldon-core/executor/api/rest.(*CloudeventHeaderMiddleware).Middleware.func1\n\t/workspace/api/rest/server.go:176\nnet/http.HandlerFunc.ServeHTTP\n\t/usr/local/go/src/net/http/server.go:2007\ngithub.com/seldonio/seldoncore/executor/api/rest.puidHeader.func1\n\t/workspace/api/rest/server.go:191\nnet/http.HandlerFunc.ServeHTTP\n\t/usr/local/go/src/net/http/server.go:2007\ngithub.com/gorilla/mux.(*Router).ServeHTTP\n\t/go/pkg/mod/github.com/gorilla/mux@v1.7.3/mux.go:212\nnet/http.serverHandler.ServeHTTP\n\t/usr/local/go/src/net/http/server.go:2802\nnet/http.(*conn).serve\n\t/usr/local/go/src/net/http/server.go:1890"}

Could you please help me out with this or suggest to me where I am going wrong!
Thank you very much.
Regards,
Nithin

Hey @Nithinbs18, I'm glad that you enjoyed the talk!
We can continue the discussion on the other thread in the seldon-core repo: https://github.com/SeldonIO/seldon-core/issues/1922


Failed to compile

I am using Node v7.3.0 and have the latest truffle and testrpc installed.  Any ideas?

Hi @chtmorris.
Did you run truffle compile from the project directory?  That's what generates the *.json artifacts in that directory.
Let me know if that works.
Thanks,
Dave./

Haha.  Yup.  Thanks Dave.  This is an awesome resource.

Glad it's helpful.  Thanks Charlie.


Latest OneDrive as part of Office for Mac Install

I use the installOfficeBusinessPro.sh script to install Office for Mac and upon launching OneDrive and logging in it will go through a few updates and OneDrive will close and reopen requiring login 1-2 additional times. Is there any way to guarantee the latest OneDrive is installed and this login process is more seamless? Does this have to do with Consumer vs Enterprise and tenant features? Would be ideal if there was a way to just install the latest final version for my tenant.

I've had a chat with the Office team and this is expected due to the different release cadences between Teams, OneDrive and Office.
I think i can resolve by installing the standalone installers rather than the Suite. I'll take a look in the morning and see if I can update the sample to show how to do it.

Thank you @theneiljohnson

I did this eventually in the individual Office installation script. It should pull down the latest of each individual app. https://github.com/microsoft/shell-intune-samples/blob/master/macOS/Apps/Office for Mac/installOffice365Pro_individual.zsh