fix(schema): Remove uniqueItems: true from noParse

Please check if the PR fulfills these requirements

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

What is the current behavior? (You can also link to an open issue here)
Schema validation of noParse breaks with multiple RegExps as of beta26.
What is the new behavior?
noParse validation no longer breaks.
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information:
Fixes #3284
Note: this should technically be possible to use, but
uniqueItems is broken in ajv; see
https://github.com/epoberezkin/ajv/issues/342
Regardless it is better to fix this bug, and there is technically
no reason why identical noParse RegExps are wrong, just superflous.

Thanks

Could you also send a PR that adds a schema test for the bug? So we avoid regression.
https://github.com/webpack/webpack/blob/master/test/Validation.test.js


How to take the prediction mask of each target in the previous frame?

@hkchengrex Because two targets are fixed during training, prev_mask[:,0:1] and prev_mask[:,1:2] can be used to take the masks of the two targets in the previous frame. However, the number of targets during testing is not fixed. How to take the prediction mask of each target in the previous frame?
for i, oi in enumerate(self.enabled_obj):
self.prob[self.enabled_obj,ti-1].cuda()

You're right.
self.enabled_obj is a list containing object indices that we have seen.

Yes.
That seems to be already explained in another issue that you opened: #60

Ok, thank you very much!

Yes.
That seems to be already explained in another issue that you opened: #60

Ok, thank you very much!

@hkchengrex
for i, oi in enumerate(self.enabled_obj):
self.prob[oi, ti-1].cuda().unsqueeze(0))
print(self.prob[oi, ti-1].cuda().size())
             torch.Size([1, 480, 864])
            print(self.prob[self.enabled_obj, ti-1].cuda().size())
             torch.Size([3,1, 480, 864])

So I want to code mask, I have to, right?
self.prob[oi, ti-1].cuda().unsqueeze(0))
or   self.prob[oi, ti-1].cuda().unsqueeze(1))

Yes.
That seems to be already explained in another issue that you opened: #60

Ok, thank you very much!

@hkchengrex
for i, oi in enumerate(self.enabled_obj):
self.prob[oi, ti-1].cuda().unsqueeze(0))
print(self.prob[oi, ti-1].cuda().size())
             torch.Size([1, 480, 864])
            print(self.prob[self.enabled_obj, ti-1].cuda().size())
             torch.Size([3,1, 480, 864])

So I want to code mask, I have to, right?
self.prob[oi, ti-1].cuda().unsqueeze(0))
or   self.prob[oi, ti-1].cuda().unsqueeze(1))

Whether to use unsqueeze depends on your needs.


Update licenses

I complained on the last update that they didn't sort like they promised. But I was wrong–they did sort. It's only now on our second post-sort update that we see the granular diff as a result of that. Yay!

Of course, their reference numbers are still basically Random.nextInt()...


feat(TinyTabs): 选项卡组件配置项的modelValue改为select组件，且其options随着选项卡而变化

English | 简体中文
PR
PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our Commit Message Guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
[ ] Built its own designer, fully self-validated

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

Background and solution

What is the current behavior?
选项卡tabs组件默认选中的标签页modelValue需要用户手动填写，体验不友好

Issue Number: N/A
What is the new behavior?
选项卡tabs组件默认选中的标签页modelValue改为下拉选择，且options随着新增或删除选项卡时同步变化
Does this PR introduce a breaking change?

[x] Yes
[ ] No

Other information

 建议删除当前选项卡后选中第一个选项卡

已解决

 建议删除当前选项卡后选中第一个选项卡


make RequestStream not dependent on CF log lines

refactor:

RequestStream becomes more generic: works with path & query string only (instead of CF log line)
add GeneratePath(type) stream to do a generic log --> path&querystring conversion. Currently accepts "cloudfront" as type.
add bin/generatepath
update bin/cflogreplay to reflect this structure

cc @yhahn

:+1:

Do you want to add a new bin for going from cfloglines => paths?

@yhahn y, switched to bin/generatepath to do something like generatepath cloudfront --> idea is we can add something like generatepath elb for other kinds of logs.

@emilymcafee add to package.json bin so that npm link knows what commands to make global? (https://github.com/mapbox/cloudfront-log-reader/blob/master/package.json#L22-L25)
And then :ship:

:ok_hand:


Move channel scripts to run on eris

Currently untested. Planning to do a test deploy tomorrow, just dumping this here in the meantime if someone cares :)
Note that I very much went for minimal diff to make things work, I'm not trying to also renovate the service config along the way. There are tons of improvements TBD - using systemd credentials management, a better format for the credentials, etc.

This is now deployed to bastion+eris. Things seem to be working OK.


Ability to pull from the interface

I feel that is important to have a feature per service (and/or also on stack) on UI to pull docker image on targeted hosts.

(: I guess this is a duplicate issue for: #1872 and #1044

Closing in favor of the image management feature issue. If you have other ideas of image management, please add comments to the issue.
https://github.com/rancher/rancher/issues/1277

Whoops, please ignore my comment on using #1277, but instead you should refer to #1872.

Thank you both! :)


#7 - Adds Ruby on Rails to the README

@gabrielbonner  contribute here https://github.com/Ishaan28malik/Get-Dev-Resources


Crash when applying include after projection

If I apply Include(..) on the root expression, everything is fine:
(from pos in Context.Set<OrderPosition>().Include(x => x.Order)
select new
{
	Position = pos,
})
.ToList();

However when applied after the projection, the query crashes:
(from pos in Context.Set<OrderPosition>()
select new
{
	Position = pos,
})
.Include(x => x.Position.Order)
.ToList();

Exception:
Exception thrown: 'System.InvalidCastException' in EntityFramework.Core.dll
Additional information: Unable to cast object of type 'System.Linq.Expressions.NewExpression' to type 'System.Linq.Expressions.MemberExpression'.

This is obviously a simplified version where it would be easy to include at the top of the expression.
However, there are scenarios, where it is nice to include later when not having access tho the root expression.For example one might pass the projected query to another method which then decides to include based on some conditions.

This is by-design because you can only call the Include method on an entity type. Before the call to select new the type of your query is IQueryable<OrderPosition>, after it is IQuerable<AnonymousTypeWithPostitionProperty> . Since the anonymous type you projected to is not an entity type, EF is not able to include related data.

@rowanmiller
But this could be supported in a future EF version right? The expression has the link to the original entity type/root expression. Shouldn't this be marked for backlog / up4grabs instead?
Furthermore the exception System.InvalidCastException does not look as design and does not indicate that this feature is not supported by EF. I think it would be better to throw an explicit System.NotSupportedException with the remark, that including via a projection is not supported.

@davidroth we aren't planning to support it. LINQ is one of those things where anything could be supported but we need to chose where we focus and this doesn't seem like it adds enough value as you can always just write the include in terms of the entity being queried.
The same is true for exception messages, we could spend endless time adding pretty exception messages for negative cases. But we typically only fix ones where you get a NullReferenceException etc.
This does exclude someone deciding to contribute support for this (or a better exception message). We just aren't planning to work on it and we try not to keep issues around that we don't ever plan to tackle (otherwise we'd have thousands of work items on our backlog :smile:)

@rowanmiller I understand, thanks for the reply.


fix: registry URL comparison

Changes
Registries with different subdomain should be considered non-equal with exception of docker.io and it's subdomains.

@lance PTAL


Documentation for 'findNearest' is misleading

I just lost some time trying to debug this message:
undefined is not an object (evaluating 'this.getKeys(point).latitude')

The data I was passing in for the coords argument to the findNearest function looks like this:
{
    "6f94619c-c17c-11e6-a4a6-cec0c932ce01": {
        latitude: -73,
        longitude: 42
    },
    ...
}

From the examples, the structure of coords looks like:
var spots = {
    "Brandenburg Gate, Berlin": {latitude: 52.516272, longitude: 13.377722},
    "Dortmund U-Tower": {latitude: 51.515, longitude: 7.453619},
    ...
}
// in this case set offset to 1 otherwise the nearest point will always be your reference point
geolib.findNearest(spots['Dortmund U-Tower'], spots, 1)

or generally speaking:
{
    name: {latitude: ..., longitude: ...}
}

The code doesn't seem to be expecting a top level string key (like "Brandenburg Gate, Berlin" in the readme example):
/**
        * Finds the nearest coordinate to a reference coordinate
        *
        * @param        object      reference coordinate e.g. {latitude: 51.5023, longitude: 7.3815}
        * @param        mixed       array or object with coords [{latitude: 51.5143, longitude: 7.4138}, {latitude: 123, longitude: 123}, ...]
        * @return       array       ordered array
        */
        findNearest: function(latlng, coords, offset, limit) {
        ...

@nitindhar7 I had this issue too when is was using an array.
**[**
    "Aalborg Airport": {latitude: '57.0952', 'longitude: 9.85606'},
    "Newport News': { latitude: '36.9805', longitude: -76.4295},
    ...
**]**

I converted it to an object and now I'm not getting that error anymore.

This function was massively simplified in v3 which will be released shortly.


Application won't to run if there russian characters in path

Kotlin v1.4.32, compose 0.4.0-build180, Windows10
Have 2x SSD and 1x HDD. On both SSD installed application work, on HDD not.
Additionally this function when run app in IDE downloading image from URL and save into folder, when installed - not.
fun loadImg(url: String) {
    val img = ImageIO.read(URL(url))
    ImageIO.write(img, "jpg", File("MyImg.jpg"))
}

I'm a little confused.  Is this one issue (all your comments are related) or two issues (one dealing with HDD/SSD, and another dealing with fetching URLs from IDE vs Packaged)?  Can you be a lot more detailed (write out HDD and SSD if they indeed mean something other than Hard Disk Drive and Solid State Drive) and provide full stack traces?
Assuming this is intended to be two separate issues...

The first issue seems confusing/surprising.  I don't think Compose would care (or even know the difference) if executed from a SSD or HDD.  Is there a full stack trace available or what do you mean when you say "On both SSD installed application work, on HDD not."
Fetching URLs from a packaged app failing looks like a duplicate of https://github.com/JetBrains/compose-jb/issues/429 and thus potentially related to https://github.com/JetBrains/compose-jb/issues/463 ?

My fault, didn't check everything before write. It's not hard drive problem, it's about russian symbols in path.
About downloading images it was just a question, cos i'm understand what it's not compose problem but can't find info. Thx for links.

What kind of error do you see? Is it native distribution or just Gradle run task?

Tested on macOS that both ./gradlew run and ./gradlew  runDistributable in folder /Users/Nikolay.Igotti/compose/визард3 works just fine.

I was tested it on stand alone app, window opened without content and instantly closed. Will check gradle task soon.

UPD: task run work fine, task runDistributable throw exception:
A problem was found with the configuration of task ':createDistributable' (type 'AbstractJPackageTask').
> Directory 'C:\Users\UserName\Desktop\��������������\GUITest\build\compose\tmp\main\runtime' specified for property 'runtimeImage' does not exist.

@Exidel This is a general Gradle issue, you should therefore avoid (if possible) using non-ascii characters for paths or file encodings. I had similar issues with non-ascii project paths. Gradle cannot handle properly non-ascii characters. Same applies for file encodings like ISO-8859-1 on Windows.
I reproduced similar behavior by creating a project, placing it in an ASCII-restricted path, executing it once (making sure everything works fine) and moving it later to a non-ascii path, clearing the cache try to rebuild and execute the main class. The Error: Could not find or load main class MainKt occurred. Recreating the project directly into non ascii path caused the same issue.
Also doing an invalid change to the gradle file and syncing it caused an output that showed the path like this:
C:\Users\Christos\workspace\temp\???????????\nonasciipath\build.gradle.kts:14:5: ...

Since I am not yet that deep into the matter of compiler and so on, I guess you probably want me to run something like kotlinc-native main.kt -o main, right?
I could yet only find kotlinc and execute it as follow:
$ cd ~/AppData/Local/JetBrains/Toolbox/apps/IDEA-U/ch-0/211.6693.111/plugins/Kotlin/kotlinc/bin
$ ./kotlinc ~/workspace/temp/лмнпрελλσδη/nonasciipath/src/main/kotlin/main.kt
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.intellij.util.ReflectionUtil to method java.util.ResourceBundle.setParent(java.util.ResourceBundle)
WARNING: Please consider reporting this to the maintainers of com.intellij.util.ReflectionUtil
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
error: source file or directory not found: C:/Users/Christos/workspace/temp/?????e??sd?/nonasciipath/src/main/kotlin/main.kt

By having the project outside of the non-ascii character path I get only unresolved references:
$ ./kotlinc ~/workspace/temp/nonasciipath/src/main/kotlin/main.kt
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.intellij.util.ReflectionUtil to method java.util.ResourceBundle.setParent(java.util.ResourceBundle)
WARNING: Please consider reporting this to the maintainers of com.intellij.util.ReflectionUtil
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
[ONLY A BUNCH OF UNRESOLVED REFERENCES]

Hope that answers at least partly your question.

Running native distributive in rus named folder work fine now, but runDistributable still throw same exception and create new folder (what ectually not a problem for me cos nobody in sane will create a project folder with name other than english).

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Is it ready to use?

Hi,
Is the plugin ready to use? Or is it still on working?
"Simply copy the contents of this repository to the base directory of the add-on you are developing."
Which directory do you mean?
Greedings
Nils

Hey Nils
Working hard on it.. for now its not.. sorry..
I have issues mostly with HA dev environment ..
will update here once its working

Hey @konradwalsh
ok. Thank you for your fast Answer :)
Good luck.
Greedings
Nils


AzureML creates Ingress Controller that potentially impacts existing Ingress Controllers.

az k8s-extension create --name  --extension-type Microsoft.AzureML.Kubernetes --config enableTraining=True enableInference=True inferenceRouterServiceType=LoadBalancer sslCname= --config-protected sslCertPemFile= sslKeyPemFile= --cluster-type managedClusters --cluster-name  --resource-group  --scope cluster
which automatically creates aml ingress controller
IF the cluster already has an ingress controller this will create contention for the ingress controller, where every 5 minutes the IP addresses keep changing.
AzureML Product Group should re-implement their ingress controller following the same guidance they suggest customers follow. Using a unique electionID: azureml-ingress-controller-leader Name: azureml-internal-nginx, controller: k8s.io/azureml-ingress-nginx.

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

ID: 8d81c8d7-02dd-76bb-0dc5-dc863f937410
Version Independent ID: dc17bdde-5092-78f5-6722-67b40427a63f
Content: Deploy Azure Machine Learning extension on Kubernetes cluster - Azure Machine Learning
Content Source: articles/machine-learning/how-to-deploy-kubernetes-extension.md
Service: machine-learning
Sub-service: core
GitHub Login: @Bozhong68
Microsoft Alias: bozhlin

@AdamSheltz
Thanks for your feedback! We will investigate and update as appropriate.

@AdamSheltz
Thank you for bringing this to our attention.
I've delegated this to content author @Bozhong68, who will review it and offer their insightful opinions.

@Bozhong68
Could you please review add comments on this, update as appropriate.

@Naveenommi-MSFT We have successfully implemented the new feature to support multi-ingress. It will be available in about 2 weeks for the release. We're now working on updating the documentation and publishing the guidance.

Hi @jiaochenlu
Thank you for your update.

@Naveenommi-MSFT We have successfully implemented the new feature to support multi-ingress. It will be available in about 2 weeks for the release. We're now working on updating the documentation and publishing the guidance.

Thanks for the update.
@jiaochenlu,  Has the implementation of this request made it through testing, is there a date this will be released (previously it was suggested 2 weeks)?

@AdamSheltz
It has released, please refer to our documentation


Rwanda common wealth

This PR explores the steps to take to include Rwanda in the list of Commonwealth countries.
This is a continuation of the work on PR #2516: see comments: https://github.com/alphagov/smart-answers/pull/2516#issuecomment-219454608, https://github.com/alphagov/smart-answers/pull/2516#issuecomment-218456039, https://github.com/alphagov/smart-answers/pull/2516#issuecomment-219687650
Trello card to track this work.
URL to fact-check
So far, it impacts on Register a Death and Register a Birth as both flows as checking if the country is included in the list of Commonwealth countries.
Next steps:

[ ] Validate with the content team if this changes are valid
[ ] Run all regression tests to validate no other tool is affected
[x] Verify that the regression tests are covering all the options for Rwanda (as we are not getting update on the regression tests, only deletions)
[ ] Regenerate checksums before and after adding the country to the list

Minor: I found the commit titles "Regenerate artefacts for *" confusing, because in these commits you are generating the artefacts for the first time i.e. "Generate artefacts for *" would be preferable.

I don't understand why lots of artefacts are being removed in the last two commits entitled "Regression tests updated for Rwanda...".

@floehopper thank you for your help here.
As I understand it, the artefacts are removed because those paths are not exercised:
next_node_calculation :responded_with_commonwealth_country do |response|
  Calculators::RegistrationsDataQuery::COMMONWEALTH_COUNTRIES.include?(response)
end

next_node do
  if country_has_no_embassy
    outcome :no_embassy_result
  elsif responded_with_commonwealth_country
    outcome :commonwealth_result
  else
    question :who_has_british_nationality?
  end
end

After including Rwanda in the list, the third exit is never exercised.

What still I don't get is why no new artefact is generated for the new path.
...still looking into it...

@floehopper, thank you for your review

I have addressed your comment about the commit title in https://github.com/alphagov/smart-answers/pull/2536/commits/6cf798d355b24bbadfb3138c23a242831e1cc1a5, and in https://github.com/alphagov/smart-answers/pull/2536/commits/ec2e0ad993537ec23ee7fc381a7f55e8620b16d3
Regarding your comment about the deleted artefacts, I have had a look at it, and my understanding is still the same I explained above.
Regarding how the artefacts are affected after adding Rwanda to the Commonwealth list, it seems to be ok. After regenerating the questions and expected responses in https://github.com/alphagov/smart-answers/pull/2536/commits/9b2dd0ea22027893b7fcd984dd63be95e6612d43 and https://github.com/alphagov/smart-answers/pull/2536/commits/b2bd679ab5c9fa4120c32d687abccdc8ece37bf6, all artefacts but Rwanda are deleted.

I would say it makes sense. What are your thoughts?

@pmanrubia:
Thanks - that does all makes sense. I think one of the key things to understand is that once Rwanda is added to the list of Commonwealth countries, users reach an outcome page much sooner i.e. they don't get taken to a bunch of question pages. Hence the reason why many artefacts are removed in the last couple of commits. It would be good to make this clear in the commit notes.
Here are some suggestions for improvements to the commit notes:

Adds Rwanda to register-a-death

This commit adds rwanda to the regression test responses for the which_country? question in register-a-death, because I plan to change the logic and I want to see the effect of this change in the regression tests. I've also updated the responses & expected results accordingly. I plan to update the regression test artefacts in a later commit.

Add Rwanda to register-a-birth.

Similar to the previous commit, but for register-a-birth.

Generate artefacts for register-a-birth

This commit updates the regression test artefacts in the light of the addition of rwanda to the regression test responses for the which_country? question in register-a-death in an earlier commit. As expected this has resulted in only additions to the artefacts and all the additions are related to rwanda.

Generate artefacts for register-a-death

Similar to the previous commit, but for register-a-death.

Add Rwanda to the Common Wealth country list.

Rwanda is a Common Wealth country 1, so it makes sense to include it within the common list for all the flows. This will result in a change to the externally visible behaviour. I plan to update the regression tests accordingly in subsequent commits.

Regenerate questions & expected responses: register-a-birth

Artefacts need regeneration because the next node calculation depends on the Calculators::RegistrationsDataQuery::COMMONWEALTH_COUNTRIES and we have just added rwanda to this list, thus changing the behaviour.

Regenerate questions & expected responses: register-a-death

Similar to the previous commit, but for register-a-death.

Regenerate artefacts for register-a-birth

Now when a user responds with rwanda to the which_country? question, they are taken straight to an outcome page and not to a series of question pages. This explains why there is a single addition to the artefacts for the rwanda version of the outcome page, and a bunch of removals for the question pages which used to follow.

Regenerate artefacts for register-a-death

Similar to the previous commit, but for register-a-death.

Thinking about this a bit more, I wonder how valuable it is to keep rwanda in the responses for the which_country? question for the regression tests, given that it looks as if we already have australia in there to test the Commonwealth country path.
I think I might be inclined to remove it, although I realise that would mean there aren't any tests that require the presence of rwanda in the list of Commonwealth countries. I think that's already true for a bunch of other Commonwealth countries.
As a compromise, I might still add rwanda to the regression tests early in the PR to demonstrate the change in behaviour, but then remove it again before the end of the PR.
@chrisroos: Do you have any thoughts on this?

@floehopper: thank you for your review and for the suggested improvements on the commit notes. This was a spike, but if we finally decide to go forward with it and create a PR, I will for sure consider your notes suggestions.
I’ve just got feedback from the Content team, and both flows should only show the Commonwealth outcome for the following countries: Canada, South Africa, Ireland, New Zealand or Australia
Once we have amended both flows, and the dependency with the Commonwealth list has been removed we will be able to include Rwanda in the Commonwealth list as intended per this conversation in Spike.
I am closing this spike as it seems that it served its purpose.


some performance optimizations for starting apps

Some performance optimizations for starting apps:

only seed the random value if we're going to use it (~600ms)
switch to the sha256 implementation from crypto (~700ms => 70ms)
default to not calling stop when starting an app. Android is ok w/ it, and stop isn't implemented for iOS (stop was ~500ms)
reduce the number of times we call simctl list --json - each call was ~100ms, and we had 5-6 calls. Down to 2 now. This is the isConnected change. The semantics of that method are different now that we only create a Device instance for devices that actually exist

The biggest outstanding piece of work now is zipping the snapshot into an flx. We can re-write to shell out to zip when it's available, and save about 1000ms.

flutter -v run:
[  17 ms] - Using Android SDK at /Users/devoncarew/tools/android-sdk-macosx/.
[  17 ms] - [/Users/devoncarew/tools/android-sdk-macosx/, SDK version 23, build-tools 23.0.2]
[  39 ms] - xcodebuild -version
[ 102 ms] - Xcode 7.2.1
Build version 7C1002
[ 105 ms] - /Users/devoncarew/tools/android-sdk-macosx/platform-tools/adb devices -l
[ 115 ms] - List of devices attached
TA95000FQA             device usb:336592896X product:peregrine_retus model:XT1045 device:peregrine
[ 149 ms] - which idevice_id
[ 152 ms] - /Users/devoncarew/homebrew/bin/idevice_id
[ 152 ms] - /Users/devoncarew/homebrew/bin/idevice_id -l
[ 161 ms] - /usr/bin/xcrun simctl list --json devices
[ 242 ms] - Downloading toolchain.
[ 270 ms] - /usr/bin/defaults read /Users/devoncarew/flutter/flutter_sunflower/ios/Info CFBundleIdentifier
[ 314 ms] - io.flutter.runner.Runner
[ 315 ms] - /Users/devoncarew/tools/android-sdk-macosx/platform-tools/adb devices -l
[ 325 ms] - List of devices attached
TA95000FQA             device usb:336592896X product:peregrine_retus model:XT1045 device:peregrine
[ 330 ms] - /Users/devoncarew/homebrew/bin/idevice_id -l
[ 336 ms] - /usr/bin/xcrun simctl list --json devices
[ 413 ms] - Running build command.
[ 416 ms] - APK up to date. Skipping build step.
[ 416 ms] - Running install command.
[ 417 ms] - /Users/devoncarew/tools/android-sdk-macosx/platform-tools/adb -s TA95000FQA shell pm path com.example.flutter_sunflower
[ 871 ms] - package:/data/app/com.example.flutter_sunflower-1/base.apk
[ 874 ms] - /Users/devoncarew/tools/android-sdk-macosx/platform-tools/adb -s TA95000FQA shell cat /data/local/tmp/sky.com.example.flutter_sunflower.sha1
[ 898 ms] - c5ea78f5d3d30eb1e2c19c29a8100836ce2522cc
[1156 ms] - Running build command for AndroidDevice TA95000FQA.
[1156 ms] Starting lib/main.dart on XT1045...
[1157 ms] - /Users/devoncarew/tools/android-sdk-macosx/platform-tools/adb version
[1166 ms] - Android Debug Bridge version 1.0.32
Revision 09a0d98bebce-android
[1168 ms] - /Users/devoncarew/tools/android-sdk-macosx/platform-tools/adb -s TA95000FQA start-server
[1178 ms] - /Users/devoncarew/tools/android-sdk-macosx/platform-tools/adb -s TA95000FQA shell getprop ro.build.version.sdk
[1213 ms] - 22
[1291 ms] - /Users/devoncarew/projects/flutter/flutter/bin/cache/artifacts/engine/darwin-x64/sky_snapshot /Users/devoncarew/flutter/flutter_sunflower/lib/main.dart --package-root=packages --snapshot=/var/folders/00/0w978000h01000cxqpysvccm003j4x/T/flutter_toolsZTLoaB/snapshot_blob.bin
[1684 ms] - Building /var/folders/00/0w978000h01000cxqpysvccm003j4x/T/flutter_toolsZTLoaB/app.flx
[1710 ms] - KeyPair from privatekey.der: null.
[1710 ms] - Encoding zip file.
[2543 ms] - Creating flx at /var/folders/00/0w978000h01000cxqpysvccm003j4x/T/flutter_toolsZTLoaB/app.flx.
[2592 ms] - Built and signed flx at /var/folders/00/0w978000h01000cxqpysvccm003j4x/T/flutter_toolsZTLoaB/app.flx.
[2592 ms] - Starting bundle for AndroidDevice TA95000FQA.
[2594 ms] - AndroidDevice TA95000FQA startBundle
[2594 ms] - /Users/devoncarew/tools/android-sdk-macosx/platform-tools/adb -s TA95000FQA forward tcp:8181 tcp:8181
[2606 ms] - /Users/devoncarew/tools/android-sdk-macosx/platform-tools/adb -s TA95000FQA -s TA95000FQA logcat -c
[2645 ms] - /Users/devoncarew/tools/android-sdk-macosx/platform-tools/adb -s TA95000FQA push /var/folders/00/0w978000h01000cxqpysvccm003j4x/T/flutter_toolsZTLoaB/app.flx /data/local/tmp/dev.flx
[2787 ms] - /Users/devoncarew/tools/android-sdk-macosx/platform-tools/adb -s TA95000FQA shell am start -a android.intent.action.RUN -d /data/local/tmp/dev.flx -f 0x20000000 --ez enable-background-compilation true --ez enable-checked-mode true com.example.flutter_sunflower/org.domokit.sky.shell.SkyActivity
[3411 ms] - Starting: Intent { act=android.intent.action.RUN dat=/data/local/tmp/dev.flx flg=0x20000000 cmp=com.example.flutter_sunflower/org.domokit.sky.shell.SkyActivity (has extras) }
Warning: Activity not started, its current task has been brought to the front
[3412 ms] - Finished run command.

LGTM


Possibility of the zero-cost stack overflow protection

Well, this is not necessarily an issue, but maybe some information that could be used as a starting point to bring back the stack overflow protection.
After reading the zero-cost stack overflow protection article and realizing that the cortex-m-rt-ld no longer works, I've found that the following statemenet is somewhat false:

We can’t specify the start address of .bss+.data to be 0x2000_4000 or some other fixed number because the correct number depends on the size of the .bss+.data section and linker scripts don’t provide support to get the size of an output section

At least on the current nightly, the following works:
  /* ## Sections in RAM */
  /* ### .data */
  .data ORIGIN(RAM) + LENGTH(RAM) - SIZEOF(.heap) - SIZEOF(.uninit) - SIZEOF(.bss) - SIZEOF(.data) - 4 : AT(__erodata) ALIGN(4)
  {
    . = ALIGN(4);
    __sdata = .;
    *(.data .data.*);
    . = ALIGN(4); /* 4-byte align the end (VMA) of this section */
    __edata = .;
  } > RAM

  /* LMA of .data */
  __sidata = LOADADDR(.data);

  /* ### .bss */
  .bss ORIGIN(RAM) + LENGTH(RAM) - SIZEOF(.heap) - SIZEOF(.uninit) - SIZEOF(.bss) - 4 (NOLOAD) : ALIGN(4)
  {
    . = ALIGN(4);
    __sbss = .;
    *(.bss .bss.*);
    . = ALIGN(4); /* 4-byte align the end (VMA) of this section */
    __ebss = .;
  } > RAM

  /* ### .uninit */
  .uninit ORIGIN(RAM) + LENGTH(RAM) - SIZEOF(.heap) - SIZEOF(.uninit) (NOLOAD) : ALIGN(4)
  {
    . = ALIGN(4);
    *(.uninit .uninit.*);
    . = ALIGN(4);
  } > RAM

  /* Heap */
  .heap ORIGIN(RAM) + LENGTH(RAM) - SIZEOF(.heap): ALIGN(4)
  {
    . = ALIGN(4);
    __sheap = .;
    *(.heap .heap.*);
    . = __sheap + __heap_size;
    __eheap = .;
  } > RAM

... and produces the following placement on an nRF52 with 64K RAM:
section               size         addr
.vector_table         0xdc          0x0
.text              0x14d6c         0xdc
.rodata             0x424c      0x14e50
.data                  0x0   0x2000cd58
.bss                 0xe5c   0x2000cd58
.uninit             0x1448   0x2000dbb8
.heap               0x1000   0x2000f000
[...]

I admit, it's not beautiful, but with PROVIDE(_stack_start = __sdata); (I think) I have the sections arranged in a way that implements the overflow protection, without double linking.

Does this still work with a non-empty .data section?

It seems that way. Adding a static mut FOO: i32 = 5; and making sure it doesn't get optimized away, I get
section               size         addr
.vector_table         0xdc          0x0
.text              0x14d98         0xdc
.rodata             0x425c      0x14e80
.data                  0x4   0x2000cd54
.bss                 0xe5c   0x2000cd58
.uninit             0x1448   0x2000dbb8
.heap               0x1000   0x2000f000

One thing I noticed is that cargo size adds the heap size to the value reported under data. I'm not sure how correct that is, but it's possible I just misrepresented the heap segment in some way. I'm not really fluent in linker speech.

(also note that on Armv8-M, the MSPLIM and PSPLIM registers provide hardware checks of stack overflows, this PR added access)

(also note that on Armv8-M, the MSPLIM and PSPLIM registers provide hardware checks of stack overflows, this PR added access)

That's neat, but I think it's a bit more device-specific than a memory segment reorder :) Unfortunately, a lot of devices out in the wild are v7-m, in my case a nRF52832.
I wonder whether this linker hackery could be implemented by default. Bypassing this is as simple as changing the .cargo/config file, so I think if someone needs custom memory segment placement, they are still able to do it.

I wonder whether this linker hackery could be implemented by default.

That would be great! The only thing that might be tricky is GNU LD support, have you checked if that also works? And from what I understand LLD aims to be compatible with GNU LD, so if it doesn't work in the latter, LLD might be "fixed" in the future and break this again.
(if it doesn't work in GNU LD then we could ship 2 different linker scripts, LLD is the default linker anyways, so users still get the stack overflow protection by default)

It seems LD substitutes 0 in place of SIZEOF.
C:\gcc\bin\arm-none-eabi-ld.exe: address 0x20010fd4 of [...] section .bss' is not within region RAM'
C:\gcc\bin\arm-none-eabi-ld.exe: address 0x20011448 of [...] section .uninit' is not within region RAM'
C:\gcc\bin\arm-none-eabi-ld.exe: address 0x20011000 of [...] section .heap' is not within region RAM'
:(

That's a shame but not too surprising. I think these days LLD is generally usable so we could consider swapping to a linker script that only works with LD and provide the current script under a different name for use with gcc/ld. Stack overflow protection for free like this would be totally worth it IMO. I think it would have to be a breaking change for cortex-m-rt.
Of course, the ideal solution would be a linker script that does work the same with rustlld, arm-none-eabi-ld, and arm-none-eabi-gcc as linkers... even if it somehow only had stack protection for rustlld.

This was fun while it lasted. Latest nightly rust-lld "broke" my hack. Oh well...

Such is life with linkers... Closing, but thanks for the investigation, @bugadani!


Problem in running code

Whenever i try to run your your code it shows a window of available classes and it is empty why?

Like this
Can you help me?

Hi @itoshi-sae5,
This issue often arises due to version mismatches. This project was originally developed using Oracle's Java version 8. It's possible you might be running it with a newer Java version. Please ensure you're using the specified requirements, as mentioned here: https://github.com/AbdelrahmanBayoumi/HotelFX#requirements.
Make sure you've also started the SQL server with XAMPP, following the instructions here: https://github.com/AbdelrahmanBayoumi/HotelFX#how-to-run.
To run the project, navigate to the Project.java file (located under the project package in src). Right-click within the file and select 'Run File'. Let me know if this resolves your issue!

What is the username and password for login?


fix(app): prevent base image update if tests failed to execute

:pencil: Description

Now that the "tests failed to execute" status is being properly set, need to prevent base image update if this is the latest status.

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


Docker pull fails due to nonvalid image name

Docker image download fails if a specific container version is downloaded. The following script has been executed (NOTE: I removed the parameter -u and -p and added ********* instead):
$imagename = 'bcinsider.azurecr.io/bcsandbox-master:14.0.26322.0-de'

$containername = "NCHTest0420"
$navlicense = '..\..\Lizenz\2018-10-04.flf'

Install-Module navcontainerhelper -Force
docker login "bcinsider.azurecr.io" *********
New-NavContainer -accept_eula -alwaysPull -imageName $imagename -includeCSide -containerName $containername -licenseFile $navlicense

It seems that image name is erroneously extended by ltsc2016.
Error message:

NavContainerHelper version: <IP_ADDRESS>

It is intentional that it adds the ltsc2016 - but it of course shouldn't do that unless the image exists.
I will fix this tonight - in the meantime you will have to revert back to navcontainerhelper <IP_ADDRESS> if you need to run the master image.

I fixed the bug - update navcontainerhelper and you should be good to go.

Thanks for the quick reaction. Now it works as expected.


Pubsub ordering keys

Copy ordering keys code to master branch. The performance regression for the non-ordering case has been fixed.

@sduskis I have removed the test that was problematic. It was the one that had been using the now-private elements of the class and so I think it is too dependent on the internal details to be able to consistently test something meaningful. Do you want to complete this review or do you want me to hand it off to someone else? Thanks!

@kamalaboulhosn, please find someone else.


untrusted constraints

This page should include some discussion of the 'with check check constraint' clause. As written, I believe it will leave the keys in question untrusted, which I am told means they will not be used by the query optimizer.

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

ID: d04ece6f-5b0e-1fbc-b083-c561025fcb87
Version Independent ID: 633f8c59-bdf7-f33f-fab6-a3b9cd2ce111
Content: Disable Foreign Key Constraints in INSERT and UPDATE Statements - SQL Server
Content Source: docs/relational-databases/tables/disable-foreign-key-constraints-with-insert-and-update-statements.md
Product: sql
Technology: table-view-index
GitHub Login: @WilliamDAssafMSFT
Microsoft Alias: wiassaf

This would be a great add @duanerchuk, thanks for raising awareness to it.  A doc update is in progress.


Image Upload

Hello,
I don't understand how to do the image upload. What am I supposed to do with the signingURL? I have an AWS s3 account, but I just need help putting it all together. Thank you!

Hi @denzils! You need to expose an endpoint like this. This example was made in Ruby on Rails. You need to adapt it using the programming language that you want. After that, you need to export the REACT_APP_API_URL and REACT_APP_SIGNING_URL_ENDPOINT environment variables like:

REACT_APP_API_URL: https://api.bonde.org
REACT_APP_SIGNING_URL_ENDPOINT: /uploads

Making this, the slate-editor image plugin, will identify it to upload and use the signed image url.

@denzils an working example could be found at these issue: https://github.com/nossas/slate-editor/issues/80
If you still have issues, let me know.


Foundry v10

initial support for v10 Foundry.
only known issue is that the vehicle roller has been implemented natively in the system as well, meaning it can be retired from here.

Updates look sensible. Confirmed you tested it, so this LGTM.


Wrong source positions for Tables with empty TableHead/TableBody

For TableBlocks containing either an empty TableHead or an empty TableBody (or both) the start position of the TableBlock is always set to 0, even if there are other things before the table. The start and end position of the empty head/body are both 0 in that case.
For example, this markdown:
foo

---|---

turns into this AST:
Document[0, 12]
  Paragraph[0, 4] isTrailingBlankLine
    Text[0, 3] chars:[0, 3, "foo"]
  TableBlock[0, 12]
    TableHead[0, 0]
    TableSeparator[5, 12]
      TableRow[5, 12]
        TableCell[5, 9] text:[5, 8, "---"] textClose:[8, 9, "|"]
          Text[5, 8] chars:[5, 8, "---"]
        TableCell[9, 12] text:[9, 12, "---"]
          Text[9, 12] chars:[9, 12, "---"]
    TableBody[0, 0]

I would expect the start of the TableBlock to be 5, the start and end of the TableHead to be 5 and the start and end of the TableBody to be 12.

@fjalowski, test added. release in progress.
Here are the corrected results:
```````````````````````````````` example Issue 216: 3
foo

---|---

.

foo

.
Document[0, 14]
  Paragraph[0, 4] isTrailingBlankLine
    Text[0, 3] chars:[0, 3, "foo"]
  TableBlock[5, 13]
    TableHead[5, 5]
    TableSeparator[5, 12]
      TableRow[5, 12]
        TableCell[5, 9] text:[5, 8, "---"] textClose:[8, 9, "|"]
          Text[5, 8] chars:[5, 8, "---"]
        TableCell[9, 12] text:[9, 12, "---"]
          Text[9, 12] chars:[9, 12, "---"]
    TableBody[12, 12]
````````````````````````````````

Repo updated. Maven updated. Maven index may take some time to reflect the new version.


feat: prefer "reckless" > "dangerous"

Description
For Prepare Hooks, the term "dangerous" sounds scary, but the dangerous usage isn't really "dangerous" at all. The term "reckless" fits better.
https://www.youtube.com/watch?v=JIrUqsB-0vw

API design is my passion.


ui-bootstrap template like tabset is not loading with build

ui-bootstrap template like tabset is not getting downloaded by Bower in ngbp

i have done two things.

Enabled the Cache in Google chrome.
our code has conflict between bootstrap and angular-bootstrap. i have removed bootstrap dependency in build.config.js


Certain Keys Not Lighting Up

What are you experiencing an issue with?

[x] Aurora

What kind of an issue is it?

[x] Visual bug

Expected behavior:
The keys should light up with the selected effects.
Actual behavior:
The keys stay dark 100% of the time
How often does this problem occur?
Every time
What is the version of Aurora you are experiencing this issue with?
My version is beta v0.6.0b
Does the previous version of Aurora have this issue?
The previous version did not have this issue.
Please include any logs, screenshots, or files that are related to this issue:
http://imgur.com/OKuT7gF
http://imgur.com/XqDDteh

Layout of keyboard and Aurora aren't the same. Did you choose the correct layout at Settings > Devices & Wrappers > Preferred Keyboard Layout?

I did, already fixed it though, some kind of file was preventing my changes in the program to apply irl


Build Issue

Hello, I attempted to utilize this plugin because I wanted to avoid dealing with Conan-UE4, UE4 CLI, or downloading UE source from GitHub. However, it seems that I am encountering difficulties in building this plugin as well. I did not find CMake for Glad inside the plugin.

Hi, I do have a release distribution in the 'Releases' section of the project, give that a try.
Otherwise, you need to build GDAL from source as detailed in the GDAL documentation here: https://gdal.org/development/building_from_source.html. Alternatively, you can source prebuilt GDAL binaries from the OSGEO4W package manager. You can then copy the binaries into the location described in this plugin's README.


Cow: Watch pieseford.ro

Cow requests the watch of the watch_keyword pieseford\.ro. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

pieseford\.ro has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by tripleee in Charcoal HQ


Rancher CLI --system option not respected while installing catalog

When I install a system catalog from the rancher cli (v0.4.1) using --system flag, then the stack that I create does not show up in the Infrastructure stacks menu.
If I look in the API, the the system parameter of the stack is set to false, even though I specified it in the CLI.
Rancher version: v1.4.0
Environment: Cattle

With the release of Rancher 2.0, development on v1.6 is only limited to critical bug fixes and security patches.


Remove default monitor value from the EarlyStopping callback

🚀 Feature

Remove the default for the Early Stopping callback's monitor: https://github.com/PyTorchLightning/pytorch-lightning/blob/b214442e745e9400e4f842d406939b4e2cd33390/pytorch_lightning/callbacks/early_stopping.py#L91
Motivation
This is a holdover from pre-1.0 when the Result object defined this key. We should remove the default for these reasons:

It's possible to construct an EarlyStopping callback without setting this. This can lead to runtime issues during training in case the default key (early_stop_on) isn't found in the list of available metrics. Since this happens at the end of either training or validation, this can waste a ton of time compared to failure on construction before training starts.
We don't want to recommend or suggest that people must log this key within their lightning module to get early stopping to work. self.log("early_stop_on", <val>)

Pitch
Deprecate the default value and force users to explicitly provide a monitor
Alternatives

Additional context

Hey I am new to pytorch. Can I help ?

@bamblebam Welcome!
Unless @ananthsub has already prepared or started a branch, you could try to remove the monitor default and check which tests need updating. As Ananth said, we need to add a deprecation message printed if someone does not provide the argument.
Also, since you said you are new, here is the contributing guideline, you may find it helpful 😃


Reject expired deploys sent from a client

CHANGELOG:

Modified the DeployAcceptor to reject expired deploys received from a client.
Added two tests to ensure the correct behavior

Closes #2330

bors r+

bors merge


/baltop throwing an error

http://pastebin.com/hE8MwRQe

Thanks for the log, but please provider further information, such as Sponge and TotalEconomy versions.
May be related to my last comment on #94

Oh um Total Economy Version 1.5.0 and sponge 1792 for 5.0.0 Mc version 1.10.2

Can also confirm.
Versions: http://puu.sh/rFFXC/79bc033fc8.jpg
Total eco v1.5.1

Going to close this issue and ask for you to post on #94 from here on out as it is the same issue.


Unclear which channels will be looped into when using automatic channel selection

I don't quite understand the automatic channel selection option. After initiating a loop with automatic channel selection enabled I'm unsure which channels will be looped into. How/when does it decide? Can it be presented to users in some way? When you do manual channel selection there is a >> icon that appears next to the channels with pending loop in operations. Can something similar be done when using automatic channel selection?

When no restriction on the channels to use is placed, then the routing algorithm of lnd (called "mission control") will decide what channels to use when paying the swap invoice. That cannot really be influenced and I'm not sure if it can easily be shown while in progress.
And even with manual channel selection, it's never guaranteed to use all the selected channels. Mission control will just restrict the channels to choose from, but if there is no route through one of the selected channels, it won't be used (if I'm not mistaken).


Random seeding for FIPS

As part of the FIPS 140-2 project, there need to be some additional changes to the random number generation infrastructure.  FIPS 140-2 has a requirement for continuous random number generation tests (CRNG) to be run.  These are outlined on page number 36 of the FIPS 140-2 document:

Continuous random number generator test. If a cryptographic module employs Approved or non-Approved RNGs in an Approved mode of operation, the module shall perform the following continuous random number generator test on each RNG that tests for failure to a constant value.

If each call to a RNG produces blocks of n bits (where n > 15), the first n-bit block generated after power-up, initialization, or reset shall not be used, but shall be saved for comparison with the next n-bit block to be generated. Each subsequent generation of an n-bit block shall be compared with the previously generated block. The test shall fail if any two compared n-bit blocks are equal.
If each call to a RNG produces fewer than 16 bits, the first n bits generated after power-up, initialization, or reset (for some n > 15) shall not be used, but shall be saved for comparison with the next n generated bits. Each subsequent generation of n bits shall be compared with the previously generated n bits. The test fails if any two compared n-bit sequences are equal.

The same testing is repeated on page number 95 of the FIPS 140-2 Derived Test Requirements document.  The testing requirements are expounded upon somewhat confusingly in section 9.8 Continuous Random Number Generator Tests by the FIPS 140-2 implementation guidance document.  However, this doesn't appear to be relevant at this point because SP 800-90A hasn't been finalised yet.
The upshot of all of this is that we need to include a CRNG test when operating in a FIPS 140-2 environment.  Because this involves discarding some data, it should not be made mandatory outside of FIPS 140-2.  The CRNG testing needs to check the blocks being fed into our master (master_drbg) from our various entropy sources.  It does not need to be performed for any of the DRBG that chain from the master.
In essence, the master DRBG will need to save the previous block of seed material it used.  When reseeding, it must confirm that the new seed material is different to the saved block.  It then consumes the new seed block and saves it for comparison during the next reseed operation.  The natural size for the block would be the seed length for the DRBG, although smaller might be permissible.
There is one nuance at startup: the first block of entropy gathered is not used as seed material.  Instead, it must be saved and a second block obtained for seeding purposes.  The second block is compared to the first before discarding the first and actually seeding the master DRBG.
If we have several different seed sources available, there is no need for the CRNG testing to be done separately for each.  We can agglomerate their output into a single pool which is used to seed the master DRBG.

@kroeckx @mspncp

An update: it is okay to choose a block size that is smaller than the DRBG seed length.
I posit a 64 bit block size.  This is a balance between reaping and discarding too much entropy from the operating system and the probability of accidentally getting a duplicated block.

16 bytes (i.e. 128-bit) is a normal block size in this sort of context but smaller would also be workable.

I believe we seed using 384 bits, a 128 bit block would mean reading 512 bits.  A 64 bit block reads 448 bits.  The choice is where to place the trade off?
I vaguely remember a guidance suggesting the probability of failure for this test be in the range 232 to 2-40.  I can't find the reference and am likely wrong about the context.

This was addressed by #8599
Closing.


Add tests for type checking

This issue is tracking the coverage of the test suite for the type-checker:

[ ] Check that literals match their own type.

[ ] true and false must be Bools.
[ ] unit must be Unit.
[ ] numbers must be Int.

[ ] Check that functions have type T -> U where T is the type of the argument and U the type of the return.
[ ] Check  binary operations:

[ ] Check that binary operations are rejected if the terms doesn't have the same type.
[ ] Check that arithmetic operations have type Int and only work with integers.
[ ] Check that boolean operations have type Bool and only work with booleans.
[ ] Check that integer comparison operations have type Bool  and only work with integers.
[ ] Check that equal and not equal have type Bool for every base type.

[ ] Check unary operations:

[ ] Check that arithmetic operations have type Int and only work with integers.
[ ] Check that boolean operations have type Bool and only work with booleans.

[ ] Check function calls (applications):

[ ] Check that f(x) has type U if f has type T -> U and x has type T.
[ ] Check that f(x) is rejected if f has type T -> U and x has a type different from T.

[ ] Check bindings:

[ ] Check that x = y actually enforces that x has the same type as y.

[ ] Check conditionals:

[ ] Check that if x do y else z end has type T if y and z have type T and x has type Bool.
[ ] Check that if x do y else z end is rejected if y and z have different types.
[ ] Check that if x do y else z end is rejected if x is not a boolean.

[ ] Check ignored terms (TODO)
[ ] Check recursive functions (TODO)

@DarkDrek this is a lot but it should give you an idea of what you can cover. Thanks for the help!

For things like "Check that arithmetic operations have type Int and only work with integers." we probably want to check all operators or is it ok for now to just write 1 test case for 1 operator?

For things like "Check that arithmetic operations have type Int and only work with integers." we probably want to check all operators or is it ok for now to just write 1 test case for 1 operator?

I think we can add one for now and then figure out if we can apply the same test for several files.

@DarkDrek which ones can be checked now after the ones you added?


[Backport r0.8] Update macos build version

Backport 4499d713642015865d910002a2f8bc0c8f592138 from #1110

I'm so proud of my bot 😭

Godspeed, little one!

It seems that github actions doesn't like when we restart those tests...

We need to upgrade our action/checkout to v2 -> https://github.com/actions/checkout/issues/23


Bug About The Table Showing Upvotes'

Expected behavior
I would look a post's upvote statistics by clicking the number near the upvote button. I expected to see the click-to-open table.

Actual behavior
Two tables opened when i clicked the number. One of them was hover-to-open and other one was click-to-open table. Because of the hover-to-open table i couldn't see the other table clearly.

How to reproduce
"Hover-to-open table" should be disabled for browsers that are used with mobile devices.

Browser:

Operating system:

Recording Of The Bug
https://d.tube/#!/v/biriki3/340oquc1
Posted on Utopian.io -  Rewarding Open Source Contributors

It should be fixed now.


Add storybook build to github actions

Currently the release action does not build the latest storybook, adding it there would be a good step.

@zyc9012 please help here

@zyc9012 can you please update the storybook?

if you tell me how to do it manually I can help you with the CI part

hi @Kreijstal the issue is that the current storybook is being served by a separate repo to which i have no rights to, it would have been ideal if a link could have been estblished between this and that repo.
we are working on having a storybook available via this repo and it should be available in a few days. its being tracked by #621


Remove this page - service in no longer offered by docker hub.

File: docker-cloud/apps/auto-redeploy.md

so many people get tripped up by this. Please remove this page as you no longer offer this service to non-enterprise users.

Closing this ticket due to its age, and the impending refactor. If you think this is in error, feel free to reopen. Thanks!


Support merging in addition to replacing objects in patches

Description of your changes

Please refer to https://github.com/crossplane/crossplane/issues/2211 for more background on this PR.
This PR aims to add merge support to the fieldpath package and moves some code from the crossplane repo to the crossplane-runtime repo to implement common functionality & prevent code duplication. For merging objects (map[string]interface{}), the mergo library is used. Certain aspects of the behavior of the mergo library can be controlled via the new fieldpath.MergeOptions struct. Merging of a value at a given path of the desired runtime.Object into the actual (current) runtime.Object is achieved via a resource.ApplyOption that's passed as an argument to resource.Applicator.Apply. This new kind of ApplyOption can be obtained using the new resource.WithMergeOptions constructor. crossplane repo PR https://github.com/crossplane/crossplane/pull/2409 depends on this PR.
I have:

[X] Read and followed Crossplane's contribution process.
[X] Run make reviewable test to ensure this PR is ready for review.
[x] Added automated tests

How has this code been tested

Together with https://github.com/crossplane/crossplane/pull/2409, I have manually tested this PR using the following manifests. I have kubectl edited resources to test & observe the behavior (e.g., when keepMapValues is false or is missing in the composition for the metadata patch, observe that claim's annotations overwrite composed's annotations with the same keys. However, when keepMapValues is true, existing values in the composed annotations are preserved even if the claim (and correspondingly the XR) has a different value for the same key):
---
apiVersion: apiextensions.crossplane.io/v1
kind: CompositeResourceDefinition
metadata:
  name: compositepostgresqlinstances.database.example.org
spec:
  group: database.example.org
  names:
    kind: CompositePostgreSQLInstance
    plural: compositepostgresqlinstances
  claimNames:
    kind: PostgreSQLInstance
    plural: postgresqlinstances
  connectionSecretKeys:
    - username
    - password
    - endpoint
    - port
  versions:
  - name: v1alpha1
    served: true
    referenceable: true
    schema:
      openAPIV3Schema:
        type: object
        properties:
          spec:
            type: object
            properties:
              parameters:
                type: object
                properties:
                  vpcSecurityGroupIDSelector:
                    description: VPCSecurityGroupIDSelector selects references to VPCSecurityGroups used to set the VPCSecurityGroupIDs.
                    properties:
                      matchControllerRef:
                        description: MatchControllerRef ensures an object with the same controller reference as the selecting object is selected.
                        type: boolean
                      matchLabels:
                        additionalProperties:
                          type: string
                        description: MatchLabels ensures an object with matching labels is selected.
                        type: object
                    type: object
                  storageGB:
                    type: integer
                required:
                  - storageGB
            required:
              - parameters
---
apiVersion: apiextensions.crossplane.io/v1
kind: Composition
metadata:
  name: composition-new
  labels:
    provider: aws
    guide: quickstart
    vpc: default
spec:
  writeConnectionSecretsToNamespace: crossplane-system
  compositeTypeRef:
    apiVersion: database.example.org/v1alpha1
    kind: CompositePostgreSQLInstance
  patchSets:
  - name: selector
    patches:
    - fromFieldPath: spec.parameters.vpcSecurityGroupIDSelector
      toFieldPath: spec.forProvider.vpcSecurityGroupIDSelector
      policy:
        mergeOptions:
          appendSlice: true
          keepMapValues: true
  - name: metadata
    patches:
    - fromFieldPath: metadata.annotations
      policy:
        mergeOptions:
          keepMapValues: true
      type: FromCompositeFieldPath
  resources:
    - name: rdsinstance
      base:
        apiVersion: database.aws.crossplane.io/v1beta1
        kind: RDSInstance
        spec:
          forProvider:
            region: us-east-1
            dbInstanceClass: db.t2.small
            masterUsername: masteruser
            engine: postgres
            engineVersion: "9.6"
            skipFinalSnapshotBeforeDeletion: true
            publiclyAccessible: true
            allocatedStorage: 20
      patches:
         - type: PatchSet
           patchSetName: selector
         - type: PatchSet
           patchSetName: metadata
         - fromFieldPath: "spec.writeConnectionSecretToRef.namespace"
           toFieldPath: "spec.writeConnectionSecretToRef.namespace"
         - fromFieldPath: "metadata.uid"
           toFieldPath: "spec.writeConnectionSecretToRef.name"
           transforms:
             - type: string
               string:
                 fmt: "%s-postgresql"
         - fromFieldPath: "spec.parameters.storageGB"
           toFieldPath: "spec.forProvider.allocatedStorage"
      connectionDetails:
        - fromConnectionSecretKey: username
        - fromConnectionSecretKey: password
        - fromConnectionSecretKey: endpoint
        - fromConnectionSecretKey: port
---
apiVersion: database.example.org/v1alpha1
kind: PostgreSQLInstance
metadata:
  name: my-db
  namespace: default
  annotations:
    a: a-from-claim
    b: b-from-claim
spec:
  parameters:
    vpcSecurityGroupIDSelector:
      matchLabels:
        l1: l1-from-claim
        l2: l2-from-claim
    storageGB: 20
  compositionSelector:
    matchLabels:
      provider: aws
      vpc: default

Hi @negz,
Thank you very much for the review. I really appreciate it. I see it as a great learning opportunity.
I realized that when MergeOptions.AppendSlice is set and the intersection between the destination and the source slices is not empty, we get duplicate items in the destination slice.  I believe this is not the UX we would want and I've added fieldpath.removeSourceDuplicates to handle duplicates by default. I have also added test cases in pkg/fieldpath/merge_test.go for this case and various others.


fix: 32bit build error

The PR environment is ready, please check the PR environment
[Attention]: This environment will be automatically cleaned up after 6 hours, please make sure to test it in time. If you have any questions, please contact the author of the PR or the community team.


Chart cordon metric

Toward giantswarm/giantswarm#6078
This is new cordon metric support for chart CR.

Damn, I will move this part of functionality to app-operator soon.


[Publisher/Bug] Importing a swagger definition

How to reproduce:

Go to Create an API using Open-API definition tab
Provide an OAS document
Click Next
Click Back

Event though the uploaded file is shown under the files next button is disabled

Cannot be reproduced in latest pack.


[API] System allows to change the name, which has more than 20 characters

Environment: macOS High Sierra 10.13, Google Chrome 81.0.4044.129 (64-bit).
Reproducable: always.
Build found: commit 1e33458.
Preconditions

Open Swagger: https://greencity.azurewebsites.net/swagger-ui.html#/ ;
Sign in with controller Post /ownSecurity/signIn;
Use token to authorize in Swagger;

Steps to reproduce

Open user-controller
Click on controller PATCH /user Update User
Click on "Try it out" button
Set parameters ("emailNotification": "DISABLED", "name": "My name is User_Lviv2020")
Click on "Execute" button

Actual result
Code 200.
Name of user is changed.
Expected result
Code 400
{
"name": "name",
"message": "User name must be from 1 to 20 characters"
}
User story and test case links
User story #385
[Test case in JIRA]: GC-1041

Verified


Op type not registered 'TensorArrayV3'

I've been building graph in python and deploy to c++ since r0.10. After upgrading to r1.0, I've retrained the model, re-created the graph, and re-link the library all in r1.0. However, I got this error when try to use the graph in the c++:
Not found: Op type not registered 'TensorArrayV3'
Here is how I created the tensorflow shared lib:
cc_binary(
    name = "libtensorflow_all.so",
    linkshared = 1,
    deps = [
        "//tensorflow/cc:cc_ops",
        "//tensorflow/core:framework_internal",
        "//tensorflow/core:tensorflow",
    ],
)

I don't find TensorArrayV3 symbol in the official lib package either ( e.g: https://storage.googleapis.com/tensorflow/libtensorflow/libtensorflow-cpu-darwin-x86_64-1.0.0.tar.gz)
Can you please advise how to fix it?

Any update on this?
> find tensorflow -type f | xargs grep TensorArrayV3 |grep -v '/go/'
tensorflow/cc/ops/op_gen_overrides.pbtxt:op { name: "TensorArrayV3" rename_to: "TensorArray" }
tensorflow/core/kernels/tensor_array_ops.cc:REGISTER_KERNEL_BUILDER(Name("TensorArrayV3").Device(DEVICE_CPU),
tensorflow/core/kernels/tensor_array_ops.cc:  REGISTER_KERNEL_BUILDER(Name("TensorArrayV3")              \
tensorflow/core/ops/compat/ops_history.v0.pbtxt:  name: "TensorArrayV3"
tensorflow/core/ops/compat/ops_history.v1.pbtxt:  name: "TensorArrayV3"
tensorflow/core/ops/data_flow_ops.cc:REGISTER_OP("TensorArrayV3")
tensorflow/core/ops/data_flow_ops.cc:    .Deprecated(16, "Use TensorArrayV3");
tensorflow/core/ops/data_flow_ops.cc:    .Doc("Deprecated. Use TensorArrayV3");
tensorflow/core/ops/ops.pbtxt:    explanation: "Use TensorArrayV3"
tensorflow/core/ops/ops.pbtxt:  summary: "Deprecated. Use TensorArrayV3"
tensorflow/core/ops/ops.pbtxt:  name: "TensorArrayV3"
tensorflow/core/public/version.h://     division and mod semantics. TensorArrayV3. (12dec2016)
tensorflow/python/ops/hidden_ops.txt:TensorArrayV3
tensorflow/python/ops/tensor_array_grad.py:ops.NotDifferentiable("TensorArrayV3")

It suggests to register TensorArrayV3, but on one line, it also says rename TensorArrayV3 to TensorArray. Do these mismatches cause issues?
(I'm looking at commit 904510eeaa40b0c8f982fbb679d827688cb35b01 in the master now.)

This is fine: the rename is for the python layer, in which the op is still called TensorArray. The dependencies look ok, you should definitely get the TensorArrayV3 kernel. built into your .so file.
I am wondering whether maybe there is a bad interaction between linkshared and the op registrations. Have you tried the official tensorflow dynamic library build rule (//tensorflow:libtensorflow.so)?

Tried //tensorflow:libtensorflow.so now, it doesn't have TensorArrayV3 symbol either.

Eugene, do you have an idea about why TensorArray may be missing?

No, all seems in order. Maybe Josh can help?

r1.1 also has the problem

If you include linkstatic=1 as well, does it work?
It appears that with linkshared only, it will be in the DYNAMIC case listed for linkstatic here: https://bazel.build/versions/master/docs/be/c-cpp.html
(this is guessing that there is a .so available at runtime that provides the operators from an older release of tensorflow)

This issue is automatically closed due to lack of activity. Please re-open if this is still an issue for you. Thanks!


Variable-time division improvements

Implement the variable-time division algorithm from "Handbook of Applied Cryptography"

TODO:

The divisor should be normalized first so that the MSB is set (see the notes in the Handbook). But that might put the dividend out of bounds of Uint.
(tangential) mul_mod_special() is variable time in c - need to either change the name, or to make a constant-time equivalent of mul_rem_vartime that it uses.
(also tangential) the algorithm in mul_mod_special() is not actually the one from "Handbook of Applied Cryptography"; there are some modifications made, and I'm trying to understand why they work. It needs comments.
The division-by-limb methods can have variable-time equivalents, but we need to see if they are actually faster. The variable time algorithms can be introduced at div_rem_limb_with_reciprocal(), short_div(), and possibly div2by1() (although the latter mostly has additions and multiplications, and only a few constant-time comparisons)

Closing in favor of #608


Using SslStream to make an ALPN connection - confusion over parameters to use.

I've updated to the .NET Core 2.1 preview in order to make an SSL connection. Our server requires an ALPN negotiation to occur. As I understand it, the preview is the first version of .NET Core to support ALPN.
Here is essentially what I'm doing:
TcpClient tcpClient = new TcpClient();
tcpClient.Connect(ProxyClient.TestUbuntuHost, ProxyClient.TestUbuntuPort);
var stream = tcpClient.GetStream();
SslStream sslStream = new SslStream(stream, false, new RemoteCertificateValidationCallback(ValidateServerCertificate));

X509Certificate2 certificate = new X509Certificate2(@"<a filename provided>);
X509Certificate2Collection certColl = new X509Certificate2Collection(certificate);
sslStream.AuthenticateAsClient(
                ProxyClient.TestUbuntuHost,
                certColl,
                SslProtocols.Tls11 | SslProtocols.Tls12, false);

The ValidateServerCertificate looks like this:
public static bool ValidateServerCertificate(
              object sender,
              X509Certificate certificate,
              X509Chain chain,
              SslPolicyErrors sslPolicyErrors)
{
            if (sslPolicyErrors == SslPolicyErrors.None)
                return true;

            Console.WriteLine("Certificate error: {0}", sslPolicyErrors);

            // Do not allow this client to communicate with unauthenticated servers.
            return false;
}

I get this error:  System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure. whether or not I pass that 3rd param to the SslStream constructor.
Can you shed some light on whether I need to do something else to enforce the ALPN negotiation?
Thanks,
Bob

Issue moved to dotnet/corefx #28230 via ZenHub


[QA] 模型格式

Describe the question.
是否有ONNX格式的模型提供

For now, we do not provide ONNX format of the model. You can refer to https://github.com/InternLM/lmdeploy for deployment of InternLM.


加载ner模型报错

Describe the bug
使用MSRA_NER_BERT_BASE_ZH模型调用ner，会去下载模型，但是加载路径下模型文件是存在的.
Code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate the problem.
ner = hanlp.load(hanlp.pretrained.ner.MSRA_NER_BERT_BASE_ZH)
sen_ner = tok(sentence)
print(sen_ner)

Describe the current behavior
A clear and concise description of what happened.
Expected behavior
A clear and concise description of what you expected to happen.
System information
OS: Windows-10-10.0.22621-SP0
Python: 3.8.12
PyTorch: 2.0.1+cpu
TensorFlow: 2.13.0
HanLP: 2.1.0-beta.50
Other info / logs
Traceback (most recent call last):
File "", line 991, in _find_and_load
File "", line 975, in _find_and_load_unlocked
File "", line 671, in load_unlocked
File "", line 843, in exec_module
File "", line 219, in call_with_frames_removed
File "C:\PowerChen\work\workspace\Idea\python\hanlp-server\test\server\hanlp_api.py", line 18, in
ner_handle = hanlp.load(hanlp.pretrained.ner.MSRA_NER_BERT_BASE_ZH)
File "C:\PowerChen\work\environment\miniconda3\lib\site-packages\hanlp_init.py", line 43, in load
return load_from_meta_file(save_dir, 'meta.json', verbose=verbose, **kwargs)
File "C:\PowerChen\work\environment\miniconda3\lib\site-packages\hanlp\utils\component_util.py", line 186, in load_from_meta_file
raise e from None
File "C:\PowerChen\work\environment\miniconda3\lib\site-packages\hanlp\utils\component_util.py", line 106, in load_from_meta_file
obj.load(save_dir, verbose=verbose, **kwargs)
File "C:\PowerChen\work\environment\miniconda3\lib\site-packages\hanlp\common\keras_component.py", line 215, in load
self.build(**merge_dict(self.config, training=False, logger=logger, **kwargs, overwrite=True, inplace=True))
File "C:\PowerChen\work\environment\miniconda3\lib\site-packages\hanlp\common\keras_component.py", line 225, in build
self.model = self.build_model(**merge_dict(self.config, training=kwargs.get('training', None),
File "C:\PowerChen\work\environment\miniconda3\lib\site-packages\hanlp\components\taggers\transformers\transformer_tagger_tf.py", line 34, in build_model
model, tokenizer = build_transformer(transformer, max_seq_length, len(self.transform.tag_vocab), tagging=True)
File "C:\PowerChen\work\environment\miniconda3\lib\site-packages\hanlp\layers\transformers\loader_tf.py", line 11, in build_transformer
tokenizer = AutoTokenizer.from_pretrained(transformer)
File "C:\PowerChen\work\environment\miniconda3\lib\site-packages\hanlp\layers\transformers\pt_imports.py", line 65, in from_pretrained
tokenizer = cls.from_pretrained(get_tokenizer_mirror(transformer), use_fast=use_fast,
File "C:\PowerChen\work\environment\miniconda3\lib\site-packages\transformers\models\auto\tokenization_auto.py", line 658, in from_pretrained
config = AutoConfig.from_pretrained(
File "C:\PowerChen\work\environment\miniconda3\lib\site-packages\transformers\models\auto\configuration_auto.py", line 944, in from_pretrained
config_dict, unused_kwargs = PretrainedConfig.get_config_dict(pretrained_model_name_or_path, **kwargs)
File "C:\PowerChen\work\environment\miniconda3\lib\site-packages\transformers\configuration_utils.py", line 574, in get_config_dict
config_dict, kwargs = cls._get_config_dict(pretrained_model_name_or_path, **kwargs)
File "C:\PowerChen\work\environment\miniconda3\lib\site-packages\transformers\configuration_utils.py", line 629, in _get_config_dict
resolved_config_file = cached_file(
File "C:\PowerChen\work\environment\miniconda3\lib\site-packages\transformers\utils\hub.py", line 452, in cached_file
raise EnvironmentError(
OSError: We couldn't connect to 'https://huggingface.co' to load this file, couldn't find it in the cached files and it looks like bert-base-chinese is not the path to a directory containing a file named config.json.
Checkout your internet connection or see how to run the library in offline mode at 'https://huggingface.co/docs/transformers/installation#offline-mode'.

[x] I've completed this form and searched the web for solutions.

加载路径下的模型文件只是一个组件运行所需资源的一部分。文档都有写：https://hanlp.hankcs.com/docs/install.html#download-error
Hugging Face管理的资源下载失败的话请按日志向对方求助：

OSError: We couldn't connect to 'https://huggingface.co/' to load this file, couldn't find it in the cached files and it looks like bert-base-chinese is not the path to a directory containing a file named config.json.
Checkout your internet connection or see how to run the library in offline mode at 'https://huggingface.co/docs/transformers/installation#offline-mode'.


chore(bpmn): integrate popup editor

closes https://github.com/camunda/camunda-modeler/issues/3877
This does not address https://github.com/camunda/camunda-modeler/issues/3902 and reuses the (sometimes broken) undo/redo handling already present for forms.

I adjusted the commit message in 53aeca4


Add SDK support for Linux / Vapor

Description of the feature request:
The ability to use the SDK in a server-side Swift environment, such as Vapor, typically on Linux.
What problem are you trying to solve with this feature?
No response
Any other information you'd like to share?
No response

This is not a currently prioritized feature request, but will continue to evaluate.
Please indicate interest with a thumbs-up vote on the issue.

yeah please add it

Please God, please add this.

yeah i mean seriously


add method forEach

Codecov Report

Merging #110 (2412388) into main (6d8d4e2) will increase coverage by 0.09%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #110      +/-   ##
==========================================
+ Coverage   96.05%   96.15%   +0.09%
==========================================
  Files         148      149       +1
  Lines        1497     1508      +11
==========================================
+ Hits         1438     1450      +12
+ Misses         59       58       -1

Impacted Files
Coverage Δ

ramda/__init__.py
100.00% <100.00%> (ø)

ramda/forEach.py
100.00% <100.00%> (ø)

ramda/private/_checkForMethod.py
91.66% <0.00%> (+8.33%)
:arrow_up:

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 6d8d4e2...2412388. Read the comment docs.


Use linear RGB downscaling for most/some downscaling operations.

Didn't include nearest_aligned since it shouldn't matter when there's no blending of pixels going on.
This is a pretty minimal, targeted change, and it's also really poorly tested since I've only run it locally myself without testing a wide range of settings or inputs. I am also certainly missing some places where downscaling can happen, but these seem to be the places used during OTF augmentations for my config and I didn't want to make a very invasive change to an unfamiliar Python codebase.
Probably not ready to merge, but probably usable by people who want to apply it locally.

Since the nearest neighbour implementation is using blending it should also be done in linear RGB, and I was able to replicate the same problems from the bug report.


Add some examples please

Hey.
Could you please provide some examples or at least one, to know how to use it with our sout command?
Thank you

I have added some examples to the README.md file, see https://github.com/galexrt/docker-vlc/blob/master/README.md#vlc-examples.
What do you think?

Awesome, Thanks a lot


Resolve license issue with the utf8proc code.

Re: Github issue https://github.com/Unidata/netcdf-c/issues/349.
Update utf8proc.[ch] to use the version now
maintained by the Julia Language project
(https://github.com/JuliaLang/utf8proc/blob/master/LICENSE.md).
The license for the previous version was
unacceptable for the Debian and Ubuntu release
systems. The new version both updates the code
and addresses the license issue.
It turns out that the utf8proc software we are using
was turned over to the Julia Language developers
and the license terms changed to allow modification.
(https://github.com/JuliaLang/utf8proc/blob/master/LICENSE.md).
So the fix here is as follows:

Wrap the library with a fixed interface: libdispatch/dutf8.c
and include/ncutf8.h.
Replace the existing utf8proc code with the new version
from https://github.com/JuliaLang/utf8proc.
Add a couple more test cases: nc_test/tst_utf8_validate.c
and nc_test_utf8_phrases.c.  If/when I can find a usable
normalization test, I will incorporate that later.

Sorry, I always forget to test with cmake.
=Dennis
On 2/17/2017 1:04 PM, Ward Fisher wrote:

There are some build failures on Windows with Visual Studio. I'll get
them resolved and then merge this pull request.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Unidata/netcdf-c/pull/364#issuecomment-280752587,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA3P29mw4KuXxcNOpjkM3pLggH8eMnWHks5rdf1fgaJpZM4MDkUB.

Not a problem.  The root of the issue is described here, and should be easy enough for me to fix. Attending to it now.

https://msdn.microsoft.com/en-us/library/62688esh.aspx

For what its worth, I only use a couple of the functions in utf8proc. None of the others
need to be exported.

Propagating changes from master into branch, then working on resolving this.


Merged plugin and exec network internal implementation

Based on https://github.com/openvinotoolkit/openvino/pull/4923

@apankratovantonp please pull the latest changes from master  - it should fix arm build on Azure.

CI passed: https://gitlab-icv.inn.intel.com/inference-engine/product-configs/merge_requests/1740


Please distinguish URL strings from URL records

The service worker standard is a very confusing read when it comes to URL terminology and I this has led to several mistakes. Internal algorithms should almost never deal with absolute URLs. They deal with URL records.

It was my mistake. I thought it was a parsed URL. Some in HTML is using absolute URL too - e.g. for API base URL type.


[BUG] testClusterGetSettingsWithDefault fails intermittently

What is the bug?
See https://github.com/opensearch-project/opensearch-java/runs/5645720812?check_suite_focus=true, tests failed on main against 1.3.0.
What is the expected behavior?
Tests pass.

Fails randomly (flaky?):
> Task :java-client:integrationTest

org.opensearch.client.opensearch.integTest.ClusterClientIT > testClusterGetSettingsWithDefault FAILED
    java.lang.AssertionError at ClusterClientIT.java:159

36 tests completed, 1 failed

> Task :java-client:integrationTest FAILED

It failed again in https://github.com/opensearch-project/opensearch-java/pull/131#pullrequestreview-926687067, retried, and it passed.


Second pod does not come up for me

When I update the config in the directory the pod does not come up and is stuck forever, only older pod keeps running:
Detailed issue in https://github.com/kubernetes/kubernetes/issues/52939

Please excuse this one, my bad, should have tried on the latest version of cluster!


options.autoCreate not working

Tried with database.get({ autoCreate: true }) and instance.get({ autoCreate: true }). They both return the standard 404 error for the resource not existing.

I put a bunch of thoughts about how to handle this in my PR, but I'm going to move them here, since we might decide that PR is the wrong solution.
These methods say they support autoCreate, but they aren't working currently. I went off to fix that, then realized... maybe they shouldn't support auto-create functionality, because the response arguments (and how to handle them) would be different depending on if the resource existed or not.
For example, this code doesn't currently work, but if it did, it would be like this:
function onDatabase(database) {
  // do whatever with `database`
}

database.get({ autoCreate: true }, function(err, database, operation, apiResponse) {
  if (err) {
    // handle error
    return
  }

  if (operation instanceof Spanner.Operation) {
    operation
      .on('error', handleCreateFailed)
      .on('complete', () => onDatabase(database))
  } else {
    onDatabase(database)
  }
})

I think that's not so great, and kills the point of having one method simply "get or create", and when it's done, you have a database-- no extra logic to worry about.
We could hide this from the user-- their callback would be called either right away, when we confirm it exists, or eventually, after the create operation completes. We would simply subscribe to the operation internally, and execute the user's callback after it complete. The downside to that is hidden behavior (we could document it), as well as inconsistent response times to the user (one near-instant, the other eventual).
What do you all think? @callmehiphop @alexander-fenster

IMO if a user is using the autoCreate option, it's because they don't want to go through the hassle of checking the error code and then creating the resource, etc. Something tells me if they're looking for convenience then they're not going to mind if we abstract away the operation as well.

The downside to that is hidden behavior (we could document it)

I think that if the user requires a finite level of control we would just direct them to exists() and allow them to handle it how they see fit. IMO its ok to have hidden functionality as long as there is a lower level counterpart.

as well as inconsistent response times to the user (one near-instant, the other eventual).

I think if the user is using autoCreate then they have to be aware that the resource might not exist, so longer response times should be expected.

SGTM. Just want to see if @alexander-fenster agrees 👍

My understanding has always been that we should make common operations easy, and complicated operations possible. So I see nothing wrong in hiding any details (e.g. allowing {autoCreate: true} and performing some hidden stuff under the hood), if (a) the hidden stuff is well-documented, and (b) it's possible for the user to choose not to use {autoCreate: true} and control the creation manually. As I understand the proposed solution satisfies both (a) and (b), so I'm OK with it.

Alright, done! #133


[datasets][PoC] Enable dataset usage for recognition task

This PR is handled as Proof of Concept for further discussions to enable the ability to use existing datasets also for recognition task ( main goal: benchmarks ).
It's easier to show the idea directly in code instead of opening a discussion.
Things to investigate if the concept should be fine:

Synthtext cropping (if use_polygons=True) is to slow (multiprocessing ? maybe in another PR
reminder: maybe a good reference)

@fg-mindee
No worry we can split this later in parts (maybe geometry, torch, tf) for review if you want :sweat_smile:
Issue:
#855  First task of this
A good documentation would be part two
(ATTENTION: reminder for docs: SROIE & SVT does only provide uppercase labels and does not match the 'case-sensitive' in images)
Any feedback is very welcome :+1:
@charlesmindee @SiddhantBahuguna @fg-mindee

@fg-mindee
I saw we have already extract_crops extract_rcrops in models/_utils.py  can we maybe move this to geometry ?

@frgfm
Same here any feedback ? 😄

Hey there 🙂
So I had thought about this a few months back. To make sure we are all on the same page, the goal is to:

take OCR annotated datasets
make a text recognition dataset out of it

Correct?
If so, two major options arise:

doing this dynamically (at it getitem)
doing this statically in the constructor

If this is for training, I'd argue the second option is the one for a few reasons :

latency
memory consumption (opening an image 100 times as big to crop it, in a number of samples that isn't necessarily the batch size comes with heavy consequences)

So perhaps this could be done in a temporary or cache folder 🤷♂
What do you think?

@frgfm
Yes you are right that's the goal :)
I have had this ways also in mind so currently i have implemented the 'constructor' option (which works really good) with one problem .... SynthText 😓 it is much to slow and needs a lot of memory (really much ~30gb ram) ...but thanks for your opinon now i can iterate on this and find a way to make it better performing 👍
I was also on track to think about saving for faster reload but it's no option it would waste a lot of the users space
One last thing for the moment are you fine if i move extract_rcrops / extract_crops to geometry otherwise we will have duplicated stuff !? :)

I think it's mostly done i will split it into 2 PRs for easier reviews :+1:

@fharper that' s only a PoC PR will be split into 2 PRs for review 👍
Part 1: #889


Rename pkg/config to pkg/agent & add unit tests for mwinsight

I see some good improvements.

more sensible naming : config => agent
documentation in config functions
use of context for having common timestamp for the whole batch of logs

I think we are good to go with this, once we finalize the structure of logs. camelCase based v/s snake_case based


double delete in tokenizer_kernel_1.cpp

In tokenizer_kernel_1.cpp line 32 headset is deleted twice. Should be bodyset. I used PVS studio to find this issue.

Cool, thanks for finding the bug.  I just fixed it.

Wow so fast, Next time I'll create a pull request for such easy fixes.


[Error] in building xgboost with GPU

For bugs or installation issues, please provide the following information.
The more information you provide, the more easily we will be able to offer
help and advice.
Environment info

Operating System:
Ubuntu 16.04 LTS

Compiler:
gcc version 5.4

Package used (python/R/jvm/C++):
python

If installing from source, please provide

The commit hash (git rev-parse HEAD)
5cd851ccef8cf0a0a71094d0d0e33a9d102f1f55

Logs will be helpful (If logs are large, please upload as attachment).
~/xgboost/build/CMakeFiles/CMakeError.log

Determining if the pthread_create exist failed with the following output:
Change Dir: /home/dp/xgboost/build/CMakeFiles/CMakeTmp

Run Build Command:"/usr/bin/make" "cmTC_67b9f/fast"
/usr/bin/make -f CMakeFiles/cmTC_67b9f.dir/build.make CMakeFiles/cmTC_67b9f.dir/build
make[1]: Entering directory '/home/dp/xgboost/build/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_67b9f.dir/CheckSymbolExists.c.o
/usr/bin/cc    -fPIC  -fPIE   -o CMakeFiles/cmTC_67b9f.dir/CheckSymbolExists.c.o   -c /home/dp/xgboost/build/CMakeFiles/CMakeTmp/CheckSymbolExists.c
Linking C executable cmTC_67b9f
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_67b9f.dir/link.txt --verbose=1
/usr/bin/cc  -fPIC     CMakeFiles/cmTC_67b9f.dir/CheckSymbolExists.c.o  -o cmTC_67b9f -rdynamic
CMakeFiles/cmTC_67b9f.dir/CheckSymbolExists.c.o: In function `main':
CheckSymbolExists.c:(.text+0x1b): undefined reference to `pthread_create'
collect2: error: ld returned 1 exit status
CMakeFiles/cmTC_67b9f.dir/build.make:97: recipe for target 'cmTC_67b9f' failed
make[1]: *** [cmTC_67b9f] Error 1
make[1]: Leaving directory '/home/dp/xgboost/build/CMakeFiles/CMakeTmp'
Makefile:126: recipe for target 'cmTC_67b9f/fast' failed
make: *** [cmTC_67b9f/fast] Error 2

File /home/dp/xgboost/build/CMakeFiles/CMakeTmp/CheckSymbolExists.c:
/* */
#include <pthread.h>

int main(int argc, char** argv)
{
  (void)argv;
#ifndef pthread_create
  return ((int*)(&pthread_create))[argc];
#else
  (void)argc;
  return 0;
#endif
}

Determining if the function pthread_create exists in the pthreads failed with the following output:
Change Dir: /home/dp/xgboost/build/CMakeFiles/CMakeTmp

Run Build Command:"/usr/bin/make" "cmTC_9d4ca/fast"
/usr/bin/make -f CMakeFiles/cmTC_9d4ca.dir/build.make CMakeFiles/cmTC_9d4ca.dir/build
make[1]: Entering directory '/home/dp/xgboost/build/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_9d4ca.dir/CheckFunctionExists.c.o
/usr/bin/cc    -fPIC -DCHECK_FUNCTION_EXISTS=pthread_create -fPIE   -o CMakeFiles/cmTC_9d4ca.dir/CheckFunctionExists.c.o   -c /usr/share/cmake-3.5/Modules/CheckFunctionExists.c
Linking C executable cmTC_9d4ca
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_9d4ca.dir/link.txt --verbose=1
/usr/bin/cc  -fPIC -DCHECK_FUNCTION_EXISTS=pthread_create    CMakeFiles/cmTC_9d4ca.dir/CheckFunctionExists.c.o  -o cmTC_9d4ca -rdynamic -lpthreads
/usr/bin/ld: cannot find -lpthreads
collect2: error: ld returned 1 exit status
CMakeFiles/cmTC_9d4ca.dir/build.make:97: recipe for target 'cmTC_9d4ca' failed
make[1]: *** [cmTC_9d4ca] Error 1
make[1]: Leaving directory '/home/dp/xgboost/build/CMakeFiles/CMakeTmp'
Makefile:126: recipe for target 'cmTC_9d4ca/fast' failed
make: *** [cmTC_9d4ca/fast] Error 2

If you are using python package, please provide

The python version and distribution
Python 3.6.4 Anaconda distribution

Steps to reproduce

CUDA version - both 8.0 and 9.0
Error (terminal)

dp@lab119:~/xgboost$ make -j4
dp@lab119:~/xgboost$ cd build
dp@lab119:~/xgboost/build$ cmake .. -DUSE_CUDA=ON -DR_LIB=OFF
-- The C compiler identification is GNU 5.4.0
-- The CXX compiler identification is GNU 5.4.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Try OpenMP C flag = [-fopenmp]
-- Performing Test OpenMP_FLAG_DETECTED
-- Performing Test OpenMP_FLAG_DETECTED - Success
-- Try OpenMP CXX flag = [-fopenmp]
-- Performing Test OpenMP_FLAG_DETECTED
-- Performing Test OpenMP_FLAG_DETECTED - Success
-- Found OpenMP: -fopenmp
-- Setting build type to 'Release' as none was specified.
-- Performing Test SUPPORT_CXX11
-- Performing Test SUPPORT_CXX11 - Success
-- Performing Test SUPPORT_CXX0X
-- Performing Test SUPPORT_CXX0X - Success
-- Performing Test SUPPORT_MSSE2
-- Performing Test SUPPORT_MSSE2 - Success
-- Could not find the GTest library. Looked in  system search paths.
CMake Warning at dmlc-core/test/unittest/CMakeLists.txt:36 (message):
  Google Test not found

-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Found CUDA: /usr/local/cuda-8.0 (found suitable version "8.0", minimum required is "8.0")
CMake Error at /usr/share/cmake-3.5/Modules/FindCUDA.cmake:360 (message):
  parse_cubin.cmake not found in /usr/share/cmake-3.5/Modules/FindCUDA
Call Stack (most recent call first):
  /usr/share/cmake-3.5/Modules/FindCUDA.cmake:977 (cuda_find_helper_file)
  CMakeLists.txt:113 (find_package)

-- Configuring incomplete, errors occurred!
See also "/home/dp/xgboost/build/CMakeFiles/CMakeOutput.log".
See also "/home/dp/xgboost/build/CMakeFiles/CMakeError.log".

What have you tried?
Not sure what to try. Did some Google search, coundn't find this issue.

@tqchen This issue is still not resolved. Is this the right place for such issues?

This issue was closed due to the current triaging. We try to aggressive close issues from now on so opened issues like this can get attended to. I went ahead and re-opened it.
If you are using Linux, you may want to install GPU-enabled binary wheels from PyPI. Just type
pip3 install xgboost

Also, you should post any future inquiries to https://discuss.xgboost.ai/. From now on, the issue tracker will be reserved for actionable items such as feature proposals discussion, roadmaps, and bug tracking. This transition is to make sure that the issues get to attend to (which they are not at the moment due to the number of issues that are open).

Please use https://discuss.xgboost.ai/ for installation questions

If you are using Linux, you may want to install GPU-enabled binary wheels from PyPI.

I didn't know that PyPI version was GPU enabled. There is no such information in the xgboost installation guide, and I thought it was the only way for GPU support.

The GPU-enabled wheel was uploaded yesterday, so the document was not updated yet. I'll file a pull request.


TUM conversion algorithm & mask creation and refinement

I would also suggest organizing directory structure like:
--make_tum.py
--utils
----[some other useful files with functions for conversion]