'ng new' fails

Bug Report
Versions
@angular/cli — 1.4.5
node — 7.2.1
npm — 5.4.2
os — win32 x64 (Windows 10)

Repro Steps
ng new sample-app

The log given by the failure
C:\Development>ng new sample-app
The command "new" has an option without the required type and name fields.
Error: The command "new" has an option without the required type and name fields.
    at Class.validateOption (C:\Users\username\AppData\Roaming\npm\node_modules\@angular\cli\ember-cli\lib\models\command.js:377:13)
    at Array.map (native)
    at Class.registerOptions (C:\Users\username\AppData\Roaming\npm\node_modules\@angular\cli\ember-cli\lib\models\command.js:163:27)
    at getOptionsTask.run.then (C:\Users\username\AppData\Roaming\npm\node_modules\@angular\cli\commands\new.js:95:18)

Other details that might be useful
I have used npm to uninstall @angular/cli and reinstall it globally.
Other commands also fail with the same error. For example ng g component some-new-component also throws the error:
The command "generate" has an option without the required type and name fields.

Getting this too. On a fresh install of node/npm.
@angular/cli — 1.4.5
node — 6.11.4
npm — 3.10.10
os — Windows 10 x64

I have the same problem after uninstalling and reinstalling  to the latest version using npm.

stdout@desktop-94847:/data/nodejs/angular4$ ng generate component my-new-component
The command "generate" has an option without the required type and name fields.
Error: The command "generate" has an option without the required type and name fields.
    at Class.validateOption (/data/nodejs/angular4/node_modules/@angular/cli/ember-cli/lib/models/command.js:377:13)
    at Array.map (<anonymous>)
    at Class.registerOptions (/data/nodejs/angular4/node_modules/@angular/cli/ember-cli/lib/models/command.js:163:27)
    at getOptionsTask.run.then (/data/nodejs/angular4/node_modules/@angular/cli/commands/generate.js:98:18)
    at <anonymous>

I have the same problem

I am having the same problem
The command "new" has an option without the required type and name fields.
Error: The command "new" has an option without the required type and name fields.
at Class.validateOption (/node_modules/@angular/cli/ember-cli/lib/models/command.js:377:13)
at Array.map (native)
at Class.registerOptions (/node_modules/@angular/cli/ember-cli/lib/models/command.js:163:27)
at getOptionsTask.run.then (/node_modules/@angular/cli/commands/new.js:95:18)

I have the same problem
@angular/cli: 1.4.5
node: 6.11.4
os: win32 x64
npm: 5.4.2
The command "new" has an option without the required type and name fields.
Error: The command "new" has an option without the required type and name fields.
at Class.validateOption (/node_modules/@angular/cli/ember-cli/lib/models/command.js:377:13)
at Array.map (native)
at Class.registerOptions (/node_modules/@angular/cli/ember-cli/lib/models/command.js:163:27)
at getOptionsTask.run.then (/node_modules/@angular/cli/commands/new.js:95:18)

Same here with new:
@angular/cli — 1.4.5
node — 8.6.0
npm — 5.3.0
os — MacOS Sierra (10.12.6)

20:44 $ ng new static
The command "new" has an option without the required type and name fields.
Error: The command "new" has an option without the required type and name fields.
    at Class.validateOption (/Users/jameskbride/.config/yarn/global/node_modules/@angular/cli/ember-cli/lib/models/command.js:377:13)
    at Array.map (<anonymous>)
    at Class.registerOptions (/Users/jameskbride/.config/yarn/global/node_modules/@angular/cli/ember-cli/lib/models/command.js:163:27)
    at getOptionsTask.run.then (/Users/jameskbride/.config/yarn/global/node_modules/@angular/cli/commands/new.js:95:18)
    at <anonymous>

Getting the same error on a fresh installation.
C:\Dropbox\Nodejs>ng new Angular The command "new" has an option without the required type and name fields. Error: The command "new" has an option without the required type and name fields.     at Class.validateOption (C:\Users\TRABAJO\AppData\Roaming\npm\node_modules\@angular\cli\ember-cli\lib\models\command.js:377:13)     at Array.map (native)     at Class.registerOptions (C:\Users\TRABAJO\AppData\Roaming\npm\node_modules\@angular\cli\ember-cli\lib\models\command.js:163:27)     at getOptionsTask.run.then (C:\Users\TRABAJO\AppData\Roaming\npm\node_modules\@angular\cli\commands\new.js:95:18)

I am also experiencing the issue. Freshly installed CLI.
The command "new" has an option without the required type and name fields.
Error: The command "new" has an option without the required type and name fields.
    at Class.validateOption (/usr/local/lib/node_modules/@angular/cli/ember-cli/lib/models/command.js:377:13)
    at Array.map (<anonymous>)
    at Class.registerOptions (/usr/local/lib/node_modules/@angular/cli/ember-cli/lib/models/command.js:163:27)
    at getOptionsTask.run.then (/usr/local/lib/node_modules/@angular/cli/commands/new.js:95:18)
    at <anonymous>

The command "generate" has an option without the required type and name fields.
Error: The command "generate" has an option without the required type and name fields.

I have the same issue:
@angular/cli - 1.4.5
node - 8.6.0
npm - 5.3.0
OS - MacOS Sierra 10.12.6
The command "new" has an option without the required type and name fields. Error: The command "new" has an option without the required type and name fields.     at Class.validateOption (/usr/local/lib/node_modules/@angular/cli/ember-cli/lib/models/command.js:377:13)     at Array.map (<anonymous>)     at Class.registerOptions (/usr/local/lib/node_modules/@angular/cli/ember-cli/lib/models/command.js:163:27)     at getOptionsTask.run.then (/usr/local/lib/node_modules/@angular/cli/commands/new.js:95:18)     at <anonymous>

I have the same problem
@angular/cli - 8.6.0
node - 1.4.5
npm - 5.3.0
OS - MacOS High Sierra 10.13
Error: The command "new" has an option without the required type and name fields.
at Class.validateOption (/Users/chris/.nvm/versions/node/v8.6.0/lib/node_modules/@angular/cli/ember-cli/lib/models/command.js:377:13)
at Array.map ()
at Class.registerOptions (/Users/chris/.nvm/versions/node/v8.6.0/lib/node_modules/@angular/cli/ember-cli/lib/models/command.js:163:27)
at getOptionsTask.run.then (/Users/chris/.nvm/versions/node/v8.6.0/lib/node_modules/@angular/cli/commands/new.js:95:18)
at

I have the same problem as well
node - v6.11.4
npm - 3.10.10
@angular/cli - 1.4.5
os - win32 x64

ng new testdemo

The command "new" has an option without the required type and name fields.
Error: The command "new" has an option without the required type and name fields.
at Class.validateOption (C:\Users\shmoorth\AppData\Roaming\npm\node_modules@angular\cli\ember-cli\lib\models\command.js:377:13)
at Array.map (native)
at Class.registerOptions (C:\Users\shmoorth\AppData\Roaming\npm\node_modules@angular\cli\ember-cli\lib\models\command.js:163:27)
at getOptionsTask.run.then (C:\Users\shmoorth\AppData\Roaming\npm\node_modules@angular\cli\commands\new.js:95:18)

Same
I have the same problem.  I had to install 1.3.2 to be able to use the command "new" again.
@angular/cli: 1.4.5
node: 6.11.4
os: win32 x64
npm: 5.4.2

Just spoke with @hansl - he reverted the last commit to github.com/angular/devkit. I just tested after reinstalling the CLI and everything is back to working.

Yup. worked for me now.   Thanks @delasteve and @hansl

@delasteve Uninstalled @angular/cli and reinstalled (on the assumption that devkit has been updataed).  Back in business now.  Thanks!

the problem was solved!
now run
npm uninstall -g @angular/cli
npm cache clean
if npm version is > 5 then use npm cache verify to avoid errors (or to avoid using --force)
npm install -g @angular/cli@latest

@delasteve all working now! Cheers ::))

Fixed by reverting the faulty PR. We'll need to be more careful when untangling the Schematics from the CLI. Closing this as fixed.

Working fine for me now. Thank you @delasteve and @hansl

Working! Thank You

Is depending on ~0.0.x for devkit (https://github.com/angular/angular-cli/blob/master/package.json#L45) the right move?
Since this means any changes to devkit get rolled out to existing cli versions arbitrarily on the next npm install, I expect this kind of breakage will happen relatively often.
If the cli is depending on 'latest' from upstream packages, having any kind of cli release tags becomes somewhat meaningless.

Working now, thanks.

I still have the same error

i can create project via ng new project-name but can not to generate component and another :)

I still not able to get. Same error is coming.

I have a possible solution.
Either upgrade from Node 6 to Node 8 or, downgrade to Angular 1.4.2.
This error happens under:
Node 6 with Angular 1.4.3
Node 6 with Angular 1.4.4
Node 6 with Angular 1.4.5
However Node 8 with Angular 1.4.5, works.
Node 6 with Angular 1.4.2 works.

Working fine now. Thanks.

I updated to node 8 and it is now working for me.

I'm still getting this error even with Node 8 and by installing 1.4.2 manually from NPM.
Windows 10

me too getting the same error. completely removed the node and verified the package.


Initializing form with an object from the DB

Hi,
I know this is an issue that was discussed many times before and also appears on the redux-form guide (I read it of course), but I tried so many approaches and still couldn't get it right..
I have a container where I use redux-form and want to initialize it with an object I get from the DB.
The thing is, that when the initialization happens, the object is not yet available on the redux store..
I used the connect function like this -
connect(state => ({ initialValues: state.myObject }), { getMyObject })(MyObject);
where getMyObject is an action that has a corresponding reducer that saves the object on the redux store under the name of myObject and MyObject is my container.
What happens is that the initialization of the form occurs before the reducer updates the state so if I look at the state after the container was rendered I see myObject with the correct data (from the DB) but the initial field (inside the relevant form object) is still empty.
I'd appreciate your help.
Thanks

Use enableReinitialize option in your reduxForm wrapped component.
Thanks for using Redux Form, but in the future please open questions at StackOverflow, which is proper place for them, not our GitHub issue tracker.

Thanks @gustavohenke !


How to solve this problem

Error will be occure when run lms service --> A JSONObject text must begin with '{' at 0 [character 1 line 1]","lname":"org.sunbird.actor.background.ChannelRegistrationActor

Please replay on this issue


Extra spaces in code blocks running locally from Windows

I do a translation and noticed that on initial load everything looks good, but if I manually reload the page suddenly appears extra lines.
Initial:

After reload:

It goes okay again if i go to another page:

But if I reload the page:

The code in my IDE does not change. That issue is only in runtime.

Hey @poznianski!
I actually noticed this too yesterday. From what I can tell the issue comes from Git's core.autocrlf option. The documentation builder seems to be interpreting the Windows \r\n as two line breaks. That puts us Windows users in a bit of a tricky position.
The good thing is that most modern IDEs on Windows support using LF as well CRLF. I would recommend setting core.autocrlf to input, which preserves the LF at checkout and converts any stray CRLFs to LFs at commit.
If you want to change this behavior machine-wide, run git config --global core.autocrlf input. If you only want to change it for just the one repo, cd to the repo and run git config core.autocrlf input.
I've not tested, but you might need to empty your stash or re-checkout the branch after reconfiguring git. I'd also close the IDE before you run the command.
Hope this helps!

Hey @poznianski!
I actually noticed this too yesterday. From what I can tell the issue comes from Git's core.autocrlf option. The documentation builder seems to be interpreting the Windows \r\n as two line breaks. That puts us Windows users in a bit of a tricky position.
The good thing is that most modern IDEs on Windows support using LF as well CRLF. I would recommend setting core.autocrlf to input, which preserves the LF at checkout and converts any stray CRLFs to LFs at commit.
If you want to change this behavior machine-wide, run git config --global core.autocrlf input. If you only want to change it for just the one repo, cd to the repo and run git config core.autocrlf input.
I've not tested, but you might need to empty your stash or re-checkout the branch after reconfiguring git. I'd also close the IDE before you run the command.
Hope this helps!

 But I have no opportunity to test it, coz I fixed  this annoying bug more radically. I switched to Manjaro as my main operating system. There is no bug 😁
Thanks for your investigation!

Well, I guess that works too! 😃
@poznianski I don't actually have the permissions to close this issue myself (not a collaborator on the repo or the author of the issue), so would you mind doing that? Thanks!


testadd new case for pg jdbc table

Proposed changes
Issue Number: close #xxx
Problem summary
Describe your changes.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[x] No
[ ] I don't know

Has unit tests been added:

[x] Yes
[ ] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[x] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[x] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[x] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 35.3 seconds
load time: 441 seconds
storage size:<PHONE_NUMBER>1 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20221125081607_clickbench_pr_52873.html


Error: Error occurred while sending email Error: connect ETIMEDOUT

Hi. I'm getting this error: INFO	Error While getting the lead assignment Data: Error: Error occurred while sending email Error: connect ETIMEDOUT everytime I try to send an email from my Node.js Lambda function. I'm trying to change something in my codebase so that I'll be able to use the dynamic template data handlebars notation. Could this problem be caused by the current version of SendGrid used in the app? It currently has "@sendgrid/mail": "^6.4.0" in its dependencies.

This issue looks related to #894. As of version 6.5.0 the MailService class includes a setTimeout function (if using TypeScript, support was added in 7.0.0). Try updating your @sendgrid/mail package and increasing the timeout.

Okay thank you. I will definitely try this out. But just to add some more details to this, the error mostly happens when I have more than 1 field inside my dynamic_template_data object. For example here. When the personalizations look like this:
```
personalizations:[
{
to: [
{
email: email
}
],
dynamic_template_data: {
subject: emailSubject
}
}
]
the Lambda works but when I update it into this one:
        ```
personalizations:[
          {
             to: [
                {
                   email: email
                }
             ],
             dynamic_template_data: {
                subject: emailSubject,
                exportType: exportType
              }
          }
       ]

that's when the timeout error pops up in the CloudWatch logs.

It's a bit strange that the mail send request times out when I add another field in the dynamic_template_data object. Could that also be because of the version not being latest?

Hi @carlzacher-placester,
What does your template look like? Maybe exportType is not defined correctly in the template.
I suggest that you log the personalization object on each failure to see if there are any other patterns of note.
With best regards,
Elmer

Do all handlebars variables need to be supported in my payload to SendGrid? Because currently our template has 4 handlebars but when I send a request to SendGrid I only send in two, subject and exportType. What's strange is sometimes it works but most cases it fails because of the timeout. I've used the sgMail.setTimeout(10000) line and it still times out. Like last night after I added that line to the function code I tested like 6 consecutive email sending requests and all were sent successfully but this morning all of my tests have failed.

Given your test results, I do not believe you need all handlbar variables present for a successful email send.
If you are using the same code with the same parameters and in one case it sends fine and in the other it times out (you can double check this by comparing the payloads), then I believe this would be a network error that likely needs investigating by your server's service provider. I do not think you should need a 10 second timeout.


logstash5.1.7 input kafka

[2017-08-01T14:22:05,319][FATAL][logstash.runner          ] An unexpected error occurred! {:error=>#<NameError: undefined local variable or method dotfile' for #<AwesomePrint::Inspector:0x89e35a4>>, :backtrace=>["/usr/local/logstash-5.4.3/vendor/bundle/jruby/1.9/gems/awesome_print-1.8.0/lib/awesome_print/inspector.rb:163:in merge_custom_defaults!'", "/usr/local/logstash-5.4.3/vendor/bundle/jruby/1.9/gems/awesome_print-1.8.0/lib/awesome_print/inspector.rb:50:in initialize'", "/usr/local/logstash-5.4.3/vendor/bundle/jruby/1.9/gems/awesome_print-1.8.0/lib/awesome_print/core_ext/kernel.rb:9:in ai'", "/usr/local/logstash-5.4.3/vendor/bundle/jruby/1.9/gems/logstash-codec-rubydebug-3.0.2/lib/logstash/codecs/rubydebug.rb:39:in encode_default'", "org/jruby/RubyMethod.java:120:in call'", "/usr/local/logstash-5.4.3/vendor/bundle/jruby/1.9/gems/logstash-codec-rubydebug-3.0.2/lib/logstash/codecs/rubydebug.rb:35:in encode'", "/usr/local/logstash-5.4.3/logstash-core/lib/logstash/codecs/base.rb:50:in multi_encode'", "org/jruby/RubyArray.java:1613:in each'", "/usr/local/logstash-5.4.3/logstash-core/lib/logstash/codecs/base.rb:50:in multi_encode'", "/usr/local/logstash-5.4.3/logstash-core/lib/logstash/outputs/base.rb:90:in multi_receive'", "/usr/local/logstash-5.4.3/logstash-core/lib/logstash/output_delegator_strategies/single.rb:15:in multi_receive'", "org/jruby/ext/thread/Mutex.java:149:in synchronize'", "/usr/local/logstash-5.4.3/logstash-core/lib/logstash/output_delegator_strategies/single.rb:14:in multi_receive'", "/usr/local/logstash-5.4.3/logstash-core/lib/logstash/output_delegator.rb:47:in multi_receive'", "/usr/local/logstash-5.4.3/logstash-core/lib/logstash/pipeline.rb:407:in output_batch'", "org/jruby/RubyHash.java:1342:in each'", "/usr/local/logstash-5.4.3/logstash-core/lib/logstash/pipeline.rb:406:in output_batch'", "/usr/local/logstash-5.4.3/logstash-core/lib/logstash/pipeline.rb:352:in worker_loop'", "/usr/local/logstash-5.4.3/logstash-core/lib/logstash/pipeline.rb:317:in start_workers'"]}

kafka {
bootstrap_servers => "localhost:9092"
topics => "mylog_topic"
group_id => "12"
consumer_threads =>1
decorate_events => true
key_deserializer_class => "org.apache.kafka.common.serialization.ByteArrayDeserializer"
value_deserializer_class => "org.apache.kafka.common.serialization.StringDeserializer"
}

why error?


deflate64 support possible?

I know that this is likely to get a no, since virtually all open source zip handling libraries have declined to add support, but I figured it wouldn't hurt to ask.
While the benefits for compression performance are negligible, there are a lot of deflate64 compressed zip files out there.  Unfortunately it's particularly a problem for my project, OpenKJ (karaoke hosting software), since one of the major tools which was used to rip karaoke CD+Gs for many years defaulted to deflate64 (pointlessly for files of the small size generated, but I guess the reasoning was zOMG 64bitz is moar bitz!).  So many of my users have thousands or tens of thousands of files using it.
I know zlib has a contrib for handling it, infback9, which might be adaptable to use in miniz, but unfortunately it's a fair bit beyond my skill level to figure out. While I submitted a couple bugfixes in the past, compression is still basically voodoo to me, else I'd do the work and send a PR.
I'm currently using miniz in my project, and it's amazing, but have had to code a hacky workaround to fall back to running an external unzip binary when a file is detected to be using deflate64.  It works, but it's ugly. lol
Anyway, if it's possible, awesome.  If not, I understand completely, and appreciate all the hard work on miniz regardless. :)

As a proof of concept, I wrote this Deflate64 decompression patch for miniz 2.2.0. (It patches the main package, not the "source code".)
It hasn't been fully tested. It might not work right, and might break other things.
It isn't suitable for being added to miniz as it is. One issue is that it unconditionally enlarges the m_dict array in the inflate_state struct from 32K to 64K.
Deflate64 support in miniz would be useful to me, though not in a very big way. I don't have a strong opinion about whether it ought to be done.

If they are so rare, I guess we could add it but condition it on a define being set? E.g. MINIZ_WITH_DEFLATE64 ? @jsummers Could you do a pull request for that?

Sorry -- I'd like to take part in the discussion, but I'm very reluctant to make such a pull request. To do it right looks like more work than I'm prepared to take on at the moment.
Again, my patch has barely been tested. I tried to make it minimally-invasive, but it's not elegant, or zero-cost. Anyone is welcome to adapt it and use it (I consider it to be public domain / not creative enough to be copyrightable).


fix(ci): adds full sync jobs for 1800k, 1810k, and 1820k blocks

Motivation
This is the standard fix for when the full sync job runs too long.
Specifications

Solution
Add full sync jobs for 1800k, 1810k, and 1820k blocks
Review
Anyone can review
Reviewer Checklist

[ ] Will the PR name make sense to users?

[ ] Does it need extra CHANGELOG info? (new features, breaking changes, large changes)

[ ] Are the PR labels correct?
[ ] Does the code do what the ticket and PR says?
[ ] How do you know it works? Does it have tests?

There's an open checkpoint update in PR #5360, do we need to skip it and go straight to this change?

It may have been excessively pre-emptive.
I'll close this for now and remove two of the three steps so that it follows the 4-5h guideline if it's needed after https://github.com/ZcashFoundation/zebra/pull/5367 has merged.

There's an open checkpoint update in PR #5360, do we need to skip it and go straight to this change?

It may have been excessively pre-emptive.

No worries, thanks for doing this!
It's just we're at a tricky stage with CI fixes right now.

Opened a new PR https://github.com/ZcashFoundation/zebra/pull/5391 off this branch because the rebase was force pushed.


Add linting github action

hmm... the linting job didn't run. @dfarrell07 is this a chicken-and-the-egg thing, ie the file must be added first then will work on subsequent PRs, or did I miss something? I haven't seen anything where actions need to be specifically enabled on a project in order to run.

It should run in this PR, it shouldn't be a chicken-an-egg situation. I wonder if there's a subtle error in the GHA definitions? That's causes them to silently not run, as we're seeing here. I could also imagine it just needing a force push or something for GH to pick up the new jobs and run them.

It should run in this PR, it shouldn't be a chicken-an-egg situation. I wonder if there's a subtle error in the GHA definitions? That causes them to silently not run, as we're seeing here. I could also imagine it just needing a force push or something for GH to pick up the new jobs and run them.

I'll try that.  I copied this from submariner as is (only removed the code-gen job) so it should be fine.

Well, I'm not sure what you did but I see it's working now. :heavy_check_mark:


Improve performance of connection info in the script editor

Hopefully resolved most of the performance issues with the connection info in the script editor.
The majority of the time was spent in get_language()->find_function as it parses the script line by line for the function. Changing this to has_method / get_member_line improves performance as it uses the preparsed script, however, it will now require a valid script for it to work.
It now keeps a Set of methods that already have a connection, saving having to search for it again.
Lastly, swapped checking for a valid texture resource and string for a plain bool.
should close #32236

Thanks!


BUG: stats: Fix handling of misaligned masks in mstats.pearsonr.

After compressing the masked arrays using a common mask for x and
y, the data is passed to stats.pearsonr to do the calculation.
Closes gh-3645.

Expert approval, no old tests modified, new test added, 100% patch diff coverage (codecov working properly now). Merging, thanks both.
I did notice some contention about what the problem actually was in the original issue--presumably that is resolved now.


SECURITY: Do NOT ignore server certificate

Twitter.com のサーバー証明書を無視していますが、証明書は飾りではないので、ちゃんと検証すべきです。

Your proposal has been accepted by our organization and made the best use to get the program better. Thanks a lot.


Detect filetype by shebang

Request for detection of filetype by shebang and/or doctype as not all files have extensions, however reading through a file and guessing the filetype rom syntax is way too complex and taxing

Micro does detect filetype based on the first line of a file (the header). So shell filetype should be detected from a shebang even if the file has no extension (this was momentarily broken since yesterday, but I just fixed it).

Can confirm this is now working as of 67ec0d3c807893a56745a49cbfa3d4848cd9ba2f

For me this doesn't work with a PHP shebang (#!/usr/bin/php) and no file extension, micro detects shell and applies no highlighting whatsoever. PHP files without the shebang and with a file extension are processed properly.


Since 4.1.2, rebuild takes 10s instead of 700ms

Hey,
I've tried versions 4.1.2 and 4.1.3, and rebuild takes 10s (hanging on SCSS) instead of 700ms with 4.1.0. Did not try 4.1.1.
I've looked at the commits but do not understand how they could have broken this.
Please tell me if I can be of any help!
Cheers

Like you pointed out, can't think of a reason why any recent changes would cause slower builds.
Anyone else experience this?


Found issue under recommended alerts

[This page has error under recommended alerts:
There is no way to create this :
If data path availability split by Frontend IP address and Frontend Port (all known and future values) is equal to zero and health probe status is equal to zero, then fire alerts
Since Azure does not support VipAvailability and DipAvailability under same rule]

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

ID: 8ef8318b-fcb3-e9e6-4522-b6bc46e28c8e
Version Independent ID: ebcb2253-31a7-e3e6-d177-ba9f79b7d37a
Content: Monitoring Azure Load Balancer
Content Source: articles/load-balancer/monitor-load-balancer.md
Service: load-balancer
GitHub Login: @mbender-ms
Microsoft Alias: mbender

@networklord , thank you for your feedback. We'll review this and get back to you shortly!

@networklord, thanks for bringing this to our notice.
@mbender-ms, I cannot create a rule in combination with VIP Availability metric.
I am getting the below error message.

Please update the document accordingly.

I'll review this with the LB team after the first of the year, and adjust the article accordingly.
Thanks for the feedback!

Hi @networklord, thank you for the feedback. We were able to confirm that this is currently not supported by Azure Monitor Alerts and will be updating documentation shortly. Please feel free to reach out again if you have any questions at all!
#please-close


NPE when upgrading Spark-DynamoDB to 1.0.0

Hi we are using your project (many thanks by the way) and we wanted to upgrade the connector with the 1.0.0 version.
Because of Guava we weren't able to test the connector locally (conflicts between our guava and yours). So 1.0.0 is a great news for us.
Sadly when I update the version, the code is not working anymore , I got an NPE.
java.lang.NullPointerException: null 	at org.apache.spark.sql.catalyst.InternalRow.getString(InternalRow.scala:34) 	at com.audienceproject.spark.dynamodb.catalyst.JavaConverter$.convertRowValue(JavaConverter.scala:39) 	at com.audienceproject.spark.dynamodb.catalyst.JavaConverter$$anonfun$5.apply(JavaConverter.scala:71) 	at com.audienceproject.spark.dynamodb.catalyst.JavaConverter$$anonfun$5.apply(JavaConverter.scala:70) 	at scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:234) 	at scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:234) 	at scala.collection.immutable.Range.foreach(Range.scala:160) 	at scala.collection.TraversableLike$class.map(TraversableLike.scala:234) 	at scala.collection.AbstractTraversable.map(Traversable.scala:104) 	at com.audienceproject.spark.dynamodb.catalyst.JavaConverter$.convertStruct(JavaConverter.scala:70) 	at com.audienceproject.spark.dynamodb.catalyst.JavaConverter$.convertRowValue(JavaConverter.scala:38) 	at com.audienceproject.spark.dynamodb.connector.TableConnector$$anonfun$putItems$1$$anonfun$apply$7.apply(TableConnector.scala:134) 	at com.audienceproject.spark.dynamodb.connector.TableConnector$$anonfun$putItems$1$$anonfun$apply$7.apply(TableConnector.scala:132) 	at scala.collection.immutable.List.foreach(List.scala:392)
The data and the code are exactly the same the only thing which has changed is the connector version.
Our data are json based, some fields could be missing but we replace any null column with a null object. For example

name
info

foo
{"age":18, "address" : "..."}

bar
null

Becames

name
info

foo
{"age":18, "address" : "..."}

bar
{"age": null, "address" : null}

If you have any clue about how can we make the 1.0.0 working for our case, it would be great :)

Hi @lucienfregosi, on the top of my head, DynamoDB does not support blank or null values. If you don't have a non-empty value for the address, it must not be in the dataset. Can you please confirm?

So if I understand correctly, the problem arises when you are trying to persist the data to DyanmoDB, right?
Also, the info field is actually a String, right?
Better yet, can you do a printSchema() on your dataframe just before you try to write it to DyanmoDB, and then paste it here?

Yes but it worked with the previous version of the connector.
The info field is more a struct or an array
Results of the print Schema :
 |-- localizedData: struct (nullable = true)
 |    |-- address: struct (nullable = true)
 |    |    |-- postCodes: array (nullable = true)
 |    |    |    |-- element: struct (containsNull = true)
 |    |    |    |    |-- postCodeTypeCode: string (nullable = true)
 |    |    |    |    |-- postCodeValue: string (nullable = true)
 |    |    |-- postOfficeBox: string (nullable = true)
 |    |    |-- streetName: string (nullable = true)
 |    |    |-- streetNumber: string (nullable = true)
 |    |    |-- complementaryStreetName: string (nullable = true)
 |    |    |-- town: string (nullable = true)
 |    |-- communicationChannels: array (nullable = true)
 |    |    |-- element: struct (containsNull = true)
 |    |    |    |-- typeCode: string (nullable = true)
 |    |    |    |-- value: string (nullable = true)
 |    |-- alphabetCode: string (nullable = true)
 |    |-- localizedLegalData: struct (nullable = true)
 |    |    |-- companyName: string (nullable = true)
 |    |    |-- secondaryNames: array (nullable = true)
 |    |    |    |-- element: struct (containsNull = true)
 |    |    |    |    |-- alternativeName: string (nullable = true)
 |    |    |    |    |-- nameTypeCode: string (nullable = true)

Thanks :)

This is being fixed with release 1.0.1

Version 1.0.1 is now on Maven Central.

Thanks it works well with 1.0.1 :D
Many thanks for your work


Do not track configuration inputs when inside the ValueSource

The ValueSource's value is a part of the configuration cache fingerprint
and it is recomputed each time the build runs, even when it runs from
cache. There is no need to additionally track inputs as only the value
of the ValueSource matters in the end.
For example, this allows users to implement complex filtering of the
available system properties without making every property an input to
the configuration phase.
Fixes https://github.com/gradle/configuration-cache/issues/569.
Another option would be to introduce a BuildOperation to compute ValueSource and use BuildOperationDetails to filter it out, similar to the TaskExecutionTracking, but this isn't as straightforward. It might be beneficial to make ValueSources visible to the build scan in the future, though.

@bot-gradle test QF, ACC

OK, I've already triggered the following builds for you:

QuickFeedback build
AllConfigCacheTestsPullRequestFeedback build

@bot-gradle test and merge
@bamboo branching date is close, so I'm going to merge it as is. I'm eager to fix any comments in follow-up PRs.

OK, I've already triggered a build for you.

Pre-tested commit build failed.

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

Error while scheduling pre-tested commit, please contact the administrator.

@bot-gradle test and merge

OK, I've already triggered a build for you.


Fix null convertion in Num::fromString (#1131)

When strtod returns 0.0, no conversion could have happened. Handle the error case correctly.

If there's no conversion then strtod will return 0.0 but it would also return 0.0 if passed "0.0" or "0.0suffix" say.
However, your actual patch does handle that correctly.
Personally, I'd like to have seen "1.2suffix" return 1.2 as it does in several other languages I've used including C itself which saves you having to trim off extraneous characters after the numerical part. However, I've just checked and it returns null at present so, unfortunately, that would be a breaking change.

The statement "C itself which saves you having to trim off extraneous characters after the numerical part" is misleading. The libc API offers incremental parsing. As such it is up to the user to decide/handle error cases, such as extraneous characters.
But I think I prefer the stricter route for parsing. It is more easier to compose (to parse more diverse inputs) and propagate errors. Relying on these incremental parsing API based on expected usages, always backfire when you have to fight against these expected usages.

Personally, I'd like to have seen "1.2suffix" return 1.2 as it does in several other languages I've used including C itself which saves you having to trim off extraneous characters after the numerical part. However, I've just checked and it returns null at present so, unfortunately, that would be a breaking change.

I suppose that #984 could provide this functionality. Though I'd argue that this behavior should be a separate function or using extra, optional parameters on fromString to specify whether we want to parse the whole string or just the first parse-able number. wrenParseNum is also able to return the number of characters in the number which could be useful for consuming strings in wren, as well as providing info of what caused a parse to fail.
I think if there is interest on this topic, we could open a new discussion.

@mhermier
Well it's worth noting that Num.fromString is not completely 'pure' in that it does ignore extraneous whitespace (" 123  " works fine) and also parses number forms such as 0X123 with a capital X or 0123 which are not valid Wren though, thankfully, the latter is parsed as a decimal rather than a C-style octal literal.
However, the general vibe of the method seems to be to parse anything that looks in its entirety like a number and return null for anything else so I'm content to leave things as they are.
In most cases that arise in practice you know (or think you know) that the numeric part will either be followed by a space + a word or by a fixed-length non-numeric suffix so it's easy to trim these off using split or by taking a sub-string. Other cases are more awkward to deal with (particularly when the number is a hex literal) and you then need to search for the first non-numeric character. I might add something which does this to my 'str' module though it's already bulging at the seams following the recent addition of some more Unicode-aware versions of lower and upper case conversion methods :)
@CrazyInfin8
Hadn't considered it but, yes, we could provide the above functionality via an extra parameter to Num.toString. This would be backwards compatible as the current version could then become an overload of it which maintained the status quo by setting the extra parameter to false.
I don't mind having a separate discussion about it though I suspect @mhermier might not be too keen as he's against the idea on principle.
Perhaps it's best to leave it for now until we see what's going to happen about binary/octal literals and digit separators being added to the language which would, of course, necessitate #984 or something like it being seriously entertained.

@PureFox48 I'm not against it, but if an API is complex and user can fall into a pit of partial success by being lazy, they will do. The problem with strtod is exactly that. The API is simple and meant to be used for incremental parsing, ie the user get back how much was parsed. On the other hand Num.fromString lack the possibility to output how much was parsed. So we can't know if a string parsed today, will be parsed the same way tomorrow, unless we properly check for a  complete parsing of the input.
As an example, 16rcafebabe is a valid hexadecimal number in smalltalk. With what you suggest 16 would be returned and rcafebabe would be ignored because it would makes no sense. If tomorrow, we decide to support that syntax, it would return hex cafebabe value, breaking code and there is no sane way to recover from that.

Well, if this were done as an extra parameter, then the user would have to explicitly set it. We'd therefore have:
var a = Num.fromString("16rcafebabe")       //> null
var b = Num.fromString("16rcafebabe", true) //> 16

So I don't really accept that this would be an easy pit into which a lazy user could unwittingly fall.
However, I do accept that as we don't know what the future may hold we should stick to the status quo for now as far as the core library is concerned (folks like me can always roll their own) though I'd be very surprised indeed if Smalltalk-type integer literals were ever to be introduced into Wren!

Anyway, I think the way it is fixed here is acceptable.

Yes, so do I and the quicker it's merged the better.

OK, this is what I've come up with for my 'str' module:
class Str {
    //  ... (existing stuff)

    // After trimming whitespace from the string 's', takes as many characters as possible
    // to form a valid number and converts it thereto using the Num.fromString method.
    // Returns null if such a conversion is impossible.
    static toNum(s) {
        if (s is Num) return s
        if (!(s is String)) s = "%(s)"
        s = s.trim()
        var n = Num.fromString(s)
        if (n) return n
        if (s.count < 2) return null
        var chars = s.toList
        for (i in chars.count-1..1) {
            chars.removeAt(i)
            if (n = Num.fromString(chars.join())) return n
        }
        return null
    }
}

var strs = ["", "?", "7Z", "3 dog night", "123.45 dollars", "$123.45", "-infiniteCalm", "nansAreGoodToEat", "0x1gen"]
for (s in strs) System.print("\"%(s)\" -> %(Str.toNum(s))")

/* output:

"" -> null
"?" -> null
"7Z" -> 7
"3 dog night" -> 3
"123.45 dollars" -> 123.45
"$123.45" -> null
"-infiniteCalm" -> -infinity
"nansAreGoodToEat" -> nan
"0x1gen" -> 1

*/

This isn't very efficient as I'm just removing characters from the end of the string until I find something that Num.toString can parse or returning null if nothing can be parsed.
However, it's a heck of a lot less code than trying to parse the string from the front and deal with all the possibilities that can arise.
As the strings would not usually be very long, it should be quick enough in practice. However, if anyone has any suggestions for improvement, I'd be glad to hear them :)


How to debug JsRender with Node.js, with break points and error messages

Hi,
I'm trying to use JsRender with Node to generate static source code, but I found that if I use a HTML page, everything is OK, if I use a tag that is not defined for instance, the error is shown in console.
Now if I use Node with JSRender (installed with: npm install jsrender --save ), then I tried the following example:
var $ = require('jsrender');
$.views.settings.debugMode(true);

function renderVueVar(value) {
   return "{{" + value + "}}";
}

// $.views.tags("mv", renderVueVar); // Provide just a render method

var tmpl = $.templates('Name: {{:name}}
 ');
var html = tmpl.render({name: "Jim"}); // Render

console.log(html);

It works Ok, it prints: Name: Jim
But if I try to use a tag that does not exist, the template line is now:
var tmpl = $.templates('Name: {{:name}}
 {{tagne}} ');
I get the following output:
/home/jose/K/jsrender/wn/node_modules/jsrender/jsrender-node.js:1821
	throw new $sub.Err(message);
	^
Error
    at /home/jose/K/jsrender/wn/node_modules/jsrender/jsrender-node.js:223:27
    at Object.<anonymous> (/home/jose/K/jsrender/wn/node_modules/jsrender/jsrender-node.js:2879:2)
    at Module._compile (internal/modules/cjs/loader.js:689:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
    at Module.load (internal/modules/cjs/loader.js:599:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
    at Function.Module._load (internal/modules/cjs/loader.js:530:3)
    at Module.require (internal/modules/cjs/loader.js:637:17)
    at require (internal/modules/cjs/helpers.js:22:18)
    at Object.<anonymous> (/home/jose/K/jsrender/wn/f.jsr:2:9)

How I can get the right error message? I tried also to test an example that use a custom tag, but I can not fix it (because I got the same error message), however, the same example is working fine an HTML
I'm using node 10.15.2 and jsrender 1.0.5
Thanks in advance,

I'm sorry I started on a reply to this back in  October, but missed that I had not actually posted the reply...
If you launch your script from the command line using  >node myscript.js then it will run with no attached debugger and so will not provide full debugging information. You will just get the call stack of any exception that is thrown, as you show above.
You can launch the script with a debugger, and it will pause at the exception, and you can see the error message. For example you can debug in chrome, by navigating to about:inspect and then clicking on "Open dedicated DevTools for Node".
Then you can launch with debugger from your command window:
 > node --inspect-brk myscript.js

If you don't want to run with a debugger, you can still get the full error message by modifying your script file and putting a try catch block around the code for which you want to see the error messages on any exceptions. In the catch block you can write the message back to the console:
var $ = require('jsrender');

try {
	var tmpl = $.templates('Name: {{:name}}
 {{tagne/}} ');
	var html = tmpl.render({name: "Jim"}); // Render
}
catch (e) {
	console.log(e)
}

console.log(html);

which will output
{ Error
    ... (call stack)
    at Object.<anonymous> (...mysript.js:1:9)
  name: 'JsRender Error',
  message:
   'Unknown tag: {{tagne}}'
}

@jsturnio  - I didn't hear back from you. Did the above suggestions work for you?
Closing this issue.

Hi Boris, thank you about your clear  suggestions!!
I tested and work fine and sorry for my late answer.

And by the way, your documentation is very nice and clear!


Enable bucket versioning-Azure

@nguptaopensds so many issues. Hard to track right? Will it be better we combine the issues based on the development plan (as it is dev issues)? Esp operations for the same cloud provider?
Also, do not see updates on these issues for the progress. Please do update accordingly.

PR #739 resolves the Enabling of versioning on bucket , The PR is for PUT bucket versioning


Possible Star Eater fix ?

Just wondering if your hack could fix for the Possible Star Eater fix:
https://www.change.org/p/sony-remove-star-eater-en
Basically, the noise reduction algorithm should be switched to off on-demand.
Sony A7 I/II, A7S I/II, A7R I/II and A9

Also A6300/A6500 (where "star eater" is still as in A7 3.x firmware series - doing very, very hardcore spatial filtering, unlike 4.x firmware for A7RII) and probably few more....


docs(guide/Directives): Use data-ng-model

Use data-ng-model instead of data-ng:model which is accepted for legacy reason.
The next "Normalization" section is saying:

Best Practice: Prefer using the dash-delimited format (e.g. ng-bind for
ngBind). If you want to use an HTML validating tool, you can instead use the
data-prefixed version (e.g. data-ng-bind for ngBind). The other forms
shown above are accepted for legacy reasons but we advise you to avoid
them.

I signed it!


CutPasteTranspose() does not check if any of the selected cells reference only cells within the selection.

From Issue #8 discussion, if cells have formulas that reference the cells within the selection to be cut, the formulas will break.
Similarly, if you try to account for that, then any cells in the selection that reference cells outside of the selection will break.
For Each c In rngSelect
        c.Copy
        ActiveSheet.Cells(iORow + c.Column - iCCol, iOCol + c.Row - iCRow).PasteSpecial Transpose:=True
        c.ClearContents
    Next c

Additionally, trying to check for this would still leave fringe cases where a cell references both a cell within the selection and outside the selection.
ref. CutPasteTranspose

Is there an example to test this on?  I believe it works as intended in most cases.
My first thought is that things should work out in most circumstances.  The code cuts each cell one-by-one so this ensures that all dependents are updated each time.  This should happen regardless of whether or not the cell is in the moving range or somewhere else.  I think this process should continue through the entire operation updating each cell and its dependents in turn.
Where it will break is if you are pasting the cut range in a way that overlaps the source.  This will quickly lead to unpredictable results because you may overwrite a cell that is needed before it has time to "get out of the way".
The downside of doing the clear afterward, is you lose the ability for cells referring into the table to maintain their relationships.  The cut approach works for this because it updates references in and out of the original range.
The original goal for this code was to take tables of calculations (e.g. monthly financial results for a year, split by budget category) and flip the table so that rows and columns swapped places.  This was needed sometimes for visual reasons (trade horizontal scrolling for vertical), sometimes to help a later calculation, sometimes to then make a PivotTable, etc.  I was doing a lot of this in financial spreadsheets where the cells being flipped were needed elsewhere in the spreadsheet, and I couldn't afford to break the spreadsheet just to get the layout I wanted.

Sure, on a blank WS
A1 = 11
A2 = 2
A3 = sum(A1:A2)
Run the macro on that selection and pick anywhere to output, A3 keeps the A1:A2 reference

Ah, I see it now.  Excel will only update the multi cell range if the whole ranges moves at one time.
Well, that is an issue.  And that is going to be tough to get around.

The solution might be just to warn the user and allow them to abort.
We can handle the error of destination intersecting, but that might stop you from setting a target where there wouldn't be an error (it gets out of the way).

Yea, I guess my testing on this was not that thorough.  It might be possible to run through the formula, find the colons, grab the range, and check if it intersects the selection being moved.  Then it can warn the user or abort.
A simple warning for now is probably adequate.
That might get into heavy string processing to pull out the formula ranges.  I have been meaning to write a formula parser for Excel so maybe this is the chance to do it.  There is something similar going on to parse the SERIES formula inside the bUTLChartSeries class: https://github.com/byronwall/bUTL/blob/master/src/code/bUTLChartSeries.vba#L95.

This would be an adequate test, I think -
For Each c In rngSelect
        If Not Intersect(rngSelect, Cells(iORow + c.Column - iCCol, iOCol + c.Row - iCRow)) Is Nothing Then
            MsgBox ("Your destination intersects with your data")
            Exit Sub
        End If

That should work.  Might want to qualify the Cells reference with a Worksheet. I think it's possible for those InputBox calls to go a different sheet if the user wants to.

That works with the downside being that it might hit an error halfway through the operation with the input/output ranges in disarray.
A conservative check could be to see if a box that contains all of the input intersects with a box that contains all of the output.

ah yeah, I forgot my next - that's a closed loop prior to the next for each c loop

Perfect.  That will work nicely.

This was completed in the last sync and can be closed.


No LoginModule found for ScramLoginModule

Hello,
We have updated Zeebe version (from 0.26 to 1.2.9) including Kafka exporter version (from 2.0.0 to 3.0.0) and started to it for our projects. The problem is new version of Kafka exporter does not work for now. You can see a trace log in the screenshot:

Therefore I cannot find any messages in a Kafka topic where Kafka exporter must produce.
We have managed to find a ticket (https://github.com/camunda-community-hub/zeebe-kafka-exporter/issues/78) where @npepinpe advised to put JAR file into /usr/local/zeebe/lib path and JAR is placed in correct path for now but there is still the same issue.
It seems there is no same issue in the previous version of the Kafka exporter (that was compatible for earlier Zeebe version) and sasl.jaas.config is the same for both (older and newer) Zeebe versions:
sasl.jaas.config = org.apache.kafka.common.security.scram.ScramLoginModule required username='user' password='user_pwd'
There is one more thing. It seams there is no ScramLoginModule class into zeebe-kafka-exporter-3.0.0-jar-with-dependencies.jar:
find . -name "Scram*.class" -type file
./org/apache/kafka/common/security/scram/ScramCredentialCallback.class
./org/apache/kafka/common/security/scram/internals/ScramCredentialUtils.class
./org/apache/kafka/common/security/scram/internals/ScramMechanism.class
./org/apache/kafka/common/security/scram/internals/ScramServerCallbackHandler.class
./org/apache/kafka/common/security/scram/ScramCredential.class
./org/apache/kafka/common/security/scram/ScramExtensionsCallback.class
Kafka exporter uses kafka-clients v. 2.8.0 (https://github.com/camunda-community-hub/zeebe-kafka-exporter/blob/3.0.0/pom.xml#L47), but kafka-clients includes that class:
find . -name "Scram*.class" -type file
./org/apache/kafka/clients/admin/ScramCredentialInfo.class
./org/apache/kafka/clients/admin/ScramMechanism.class
./org/apache/kafka/common/security/scram/ScramCredentialCallback.class
./org/apache/kafka/common/security/scram/internals/ScramExtensions.class
./org/apache/kafka/common/security/scram/internals/ScramMessages$AbstractScramMessage.class
./org/apache/kafka/common/security/scram/internals/ScramMessages$ClientFinalMessage.class
./org/apache/kafka/common/security/scram/internals/ScramMessages$ServerFinalMessage.class
./org/apache/kafka/common/security/scram/internals/ScramSaslServerProvider.class
./org/apache/kafka/common/security/scram/internals/ScramSaslServer$ScramSaslServerFactory.class
./org/apache/kafka/common/security/scram/internals/ScramFormatter.class
./org/apache/kafka/common/security/scram/internals/ScramSaslClient.class
./org/apache/kafka/common/security/scram/internals/ScramSaslClient$1.class
./org/apache/kafka/common/security/scram/internals/ScramSaslClient$ScramSaslClientFactory.class
./org/apache/kafka/common/security/scram/internals/ScramSaslServer$State.class
./org/apache/kafka/common/security/scram/internals/ScramSaslServer.class
./org/apache/kafka/common/security/scram/internals/ScramCredentialUtils.class
./org/apache/kafka/common/security/scram/internals/ScramSaslServer$1.class
./org/apache/kafka/common/security/scram/internals/ScramMechanism.class
./org/apache/kafka/common/security/scram/internals/ScramSaslClientProvider.class
./org/apache/kafka/common/security/scram/internals/ScramSaslClient$State.class
./org/apache/kafka/common/security/scram/internals/ScramMessages.class
./org/apache/kafka/common/security/scram/internals/ScramMessages$ClientFirstMessage.class
./org/apache/kafka/common/security/scram/internals/ScramServerCallbackHandler.class
./org/apache/kafka/common/security/scram/internals/ScramMessages$ServerFirstMessage.class
./org/apache/kafka/common/security/scram/ScramCredential.class
./org/apache/kafka/common/security/scram/ScramExtensionsCallback.class
./org/apache/kafka/common/security/scram/ScramLoginModule.class
Could you, please, help us to sort this issue out?
Thank you in advance.

@npepinpe Hello Nicolas,
Thank you for your advice. I am not build a new JAR file as you advised before with the another plugin but I have done a workaround. I have just tried to put JAR of kafka-clients near Kafka exporter JAR. But it does not help and the issue is still here. If you have more ideas about it, let me know, please.


"'location' of null" error in real-world example

I'm totally new to redux... but it looks sick.
Seems to be an issue in the "DevTools". When I install and run "real-world" example, search for 'rackt', then click anything in DevTools, errors start appearing in the console:
Uncaught TypeError: Cannot read property 'location' of nullmapStateToProps @ App.js?7e8f:68
Version 3.0.4
To reproduce:

cd redux/examples/examples/real-world
npm install
npm start
Go to site in browser: http://localhost:3000/
Enter: 'rackt'
In the DevTools(redux's), click "Reset"

Error occurs....

Thanks for the report. I'd say you should file this with redux-router.
By default it sets router state field to null, but I think it should have initial value before first change action. The app should never see null state there, I think, but RESET effectively gets us back to the initial state. The same error will occur if you “toggle” action in DevTools.
@acdlite Ideas?


[gym] hard error on xcode 8.3 with legacy api

hard error if xcode >= 8.3 is used and use_legacy_build_api is set.
error message modeled after this https://github.com/fastlane/fastlane/issues/8672#issuecomment-290544806

originally i wanted to remove all code paths with use_legacy_build_api but maybe there are some folks still using xode8.2 or below.

These changes are not enough?
https://github.com/fastlane/fastlane/pull/8692 https://github.com/fastlane/fastlane/pull/8717

@nafu  they only trigger on packaging errors, not if for example an ipa is uploaded and later on rejected on apple servers. - i think we should start (with 8.3) to hard disallow legacy api, to protect users from following errors, and therefore keeping issue impact low.

@KrauseFx  spec's added

Nice! 🚀


pydantic 2

Although this repository seems to not define any dependency, it uses pydantic.
I tried to migrate a stac_fastapi project to fastapi 0.100.0 and pydantic 2, but I've import errors:
  File "/Users/keul/mambaforge/envs/copds3.10/lib/python3.10/site-packages/stac_fastapi/types/core.py", line 9, in <module>
    from stac_pydantic.links import Relations
  File "/Users/keul/mambaforge/envs/copds3.10/lib/python3.10/site-packages/stac_pydantic/__init__.py", line 1, in <module>
    from .catalog import Catalog
  File "/Users/keul/mambaforge/envs/copds3.10/lib/python3.10/site-packages/stac_pydantic/catalog.py", line 5, in <module>
    from stac_pydantic.links import Links
  File "/Users/keul/mambaforge/envs/copds3.10/lib/python3.10/site-packages/stac_pydantic/links.py", line 59, in <module>
    class Links(BaseModel):
  File "/Users/keul/mambaforge/envs/copds3.10/lib/python3.10/site-packages/pydantic/_internal/_model_construction.py", line 95, in __new__
    private_attributes = inspect_namespace(
  File "/Users/keul/mambaforge/envs/copds3.10/lib/python3.10/site-packages/pydantic/_internal/_model_construction.py", line 279, in inspect_namespace
    raise TypeError("To define root models, use `pydantic.RootModel` rather than a field called '__root__'")
TypeError: To define root models, use `pydantic.RootModel` rather than a field called '__root__'

Pydantic 2 has been released. Any plan to migrate?

See also https://github.com/stac-utils/stac-fastapi/issues/588

Closed by https://github.com/stac-utils/stac-pydantic/pull/127


Failed to check/redeclare auto-delete queue(s) - missing exception cause

In what version(s) of Spring AMQP are you seeing this issue?
3.0.6
Describe the bug
We sporadically see the error log
2023-08-07 14:32:34.768 UTC ERROR [deadLetterQueueListenerContainer-10] SimpleMessageListenerContainer: Failed to check/redeclare auto-delete queue(s).
Unfortunately, the error log is missing the exception that caused it, which obviously makes it hard to debug in a larger system.
I suspect in our case this happens when the application starts. Looking at AbstractMessageListenerContainer.java below, this.logDeclarationException is always false when something fails already during startup.
protected synchronized void redeclareElementsIfNecessary() {
		AmqpAdmin admin = getAmqpAdmin();
		if (!this.lazyLoad && admin != null && isAutoDeclare()) {
			try {
				attemptDeclarations(admin);
				this.logDeclarationException.set(true);
			}
			catch (Exception e) {
				if (RabbitUtils.isMismatchedQueueArgs(e)) {
					throw new FatalListenerStartupException("Mismatched queues", e);
				}
				if (this.logDeclarationException.getAndSet(false)) {
					this.logger.error("Failed to check/redeclare auto-delete queue(s).", e);
				}
				else {
					this.logger.error("Failed to check/redeclare auto-delete queue(s).");
				}
			}
		}
	}

To Reproduce
Just connect to an non-existing host :-)
Expected behavior
I'd at least expect one exception logged before switching to logs without a full stack trace.
According to https://github.com/spring-projects/spring-amqp/pull/1523 this was introduced to reduce log spam when the host is temporarily unavailable.
My suggestion would be to initialize this.logDeclarationException with true, so the first occurrence of an exception still logs the stack trace. I can prepare a PR if you like.
Sample

Sorry, I'm not sure where is the problem.
According to the current AbstractMessageListenerContainer we have this logic:
private final AtomicBoolean logDeclarationException = new AtomicBoolean(true);

So, when attemptDeclarations(admin); throws an exception on a first attempt, we go to that if (this.logDeclarationException.getAndSet(false)) { which is true for this first case.
What do I miss?
What kind of change are you anticipating?
Thanks

Hey, sorry for bothering you yesterday. Apparently the long working day took a toll on my brain -- the current behavior is exactly as I suggested. My log monitoring tool simply didn't show the log line correctly hence my wrong assumption. I was now able to dig up the stack trace.
Thank you for responding so quickly and my apologies again for stealing your time :)


fix build failure caused by typo in eng_cryptodev.c

This patch fixes a typo introduced in
a03f81f4ead24c234dc26e388d86a352685f3948 (Fix NULL-return checks in 1.0.2)
that becomes apparent when both -DHAVE_CRYPTODEV and -DUSE_CRYPTODEV_DIGESTS
options are used with configure.
Signed-off-by: Cristian Stoica<EMAIL_ADDRESS>

we already fixed it with commit 581215a :)


Automatically build Docker images for branch and tag pushes

What this PR does / why we need it:
Adds GitHub Actions workflows for automatically building images on main/next branch and tag pushes.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Provides a controller Red Hat artifact for https://github.com/Kong/team-k8s/issues/33
Fixes #901
Special notes for your reviewer:
I haven't actually created this repo in the Docker Hub Kong org yet. Figured I'd confirm this is what we want to do first.
This requires Docker credentials in a GitHub repo secret. I have access to add a token, but not access to create repo secrets, so we'd need to have a repo admin do that. Do not merge until this and repo creation are complete.
Not sure if there's a better way (i.e. something we can add in the Dockerfile itself) to handle making Alpine the default target that doesn't rely on the --target argument in the make target. However, since using make container is our standard way to manually build images, that approach seems fine.
This doesn't yet handle RC images, and we'd probably want it to. I'm trying to think of a way to do that without creating a third workflow, since the only difference would be that we don't push latest.
For practical examples, see the branch builds and tag builds (ignore the workflow name, it was incorrect when I tested) on my fork.
Outputs can be seen on my Docker Hub repo. The names are a bit different from the final version.

Thinking over how to handle RC images some more, I realized that tagging latest automatically doesn't work for the non-RC images either, since we may backport fixes and release patch releases for older versions also. As such, changing the tag job to just handle all git tags, but only push the images for those tags specifically in 0faa158.
We'll need to tag Docker latest manually when appropriate, since there's nothing in the tag itself that'd allow us to use workflow filters to distinguish when a tag is the newest available version versus a backport.

Credential secrets are now in place, so this is clear to go in once we're happy with it. Removed do not merge label.

Based on Colin's suggestion, added a unified workflow in 3f9fdb3. This is intended to ultimately replace the others, but I haven't removed those yet to preserve existing comments (we should remove them before merging).
https://github.com/rainest/kubernetes-ingress-controller/runs/2423767024 is an example tag push run.
https://github.com/rainest/kubernetes-ingress-controller/runs/2423764803 is an example branch push run.
During the course of setting that up, I realized that the TAG argument handling in the workflow differed from the current behavior, sort of. In the Makefile targets, TAG is a static value (normally set to the newest tag) at the top of the Makefile. Builds of unreleased content (e.g. the tip of main) still indicate that their version is 1.2.0 or whatever. Earlier versions of the workflows used the same version as used in the Docker tag (e.g. the image would have the label version=main for those builds). Do we have a preference for one or the other? I added a step to fetch the most recent tag in the interest of preserving existing behavior, but personally feel the existing behavior is less appropriate for the main and next builds.

Do we have a preference for one or the other? I added a step to fetch the most recent tag in the interest of preserving existing behavior, but personally feel the existing behavior is less appropriate for the main and next builds.

My preference is that if an image gets built from a source that's different than the source for a well-defined tag (say. 1.2.0) then its tag should not be 1.2.0 to avoid confusion. So I opt for dropping the existing behavior.

@mflendrich raise a concern with the major/minor Docker tags applying to rc/alpha/etc. releases during Wednesday's sync, but I believe these are fine. Consider the following order of releases:

We push a 1.2.1 git tag. CI tags this image kic:1.2.1 and kic:1.2.
We push a 2.0.0-alpha.1 tag. CI tags this image kic:2.0.0-alpha.1 and kic:2.0
We push a 1.2.2 git tag. CI tags this image kic:1.2.2 and kic:1.2, overriding the previous 1.2 tag, which was an alias 1.2.1.
We push a 2.0.0 tag. CI tags this image kic:2.0.0 and kic:2.0, overriding the previous 2.0 tag, which was an alias 2.0.0-alpha.1.

This does not inadvertently upgrade you to a pre-release version if you are using the major-minor tags: if you've set the current stable major-minor tag (1.2), you'll only get 1.2.x patch releases. To get 2.0.0-alpha.1, you'd need to intentionally upgrade to 2.0.
Major-minor tags would downgrade you if we performed a release out of order, e.g. if there was a step 5 that released 2.0.0-alpha.2. However, I see no reason that we'd do this--once we've pushed out a stable 2.0.0, we have no reason to release additional pre-release versions after. All subsequent 2.0 releases should be stable patch releases.
Automatic latest tagging would present an issue. As far as I know, docker-meta has no logic beyond just tagging latest when it's enabled, so latest always points to the artifact generated by the CI run that completed last. Using it (although bad practice) would upgrade you to 2.0.0-alpha.1 from 1.2.1 at step 2, and then downgrade you to 1.2.2 at step 3, which we don't want.
Automatic major tags would present a similar issue if we released a 1.2.1 and then a 1.3.0-alpha.1 or similar, but we don't use automatic major tags because even a stable release on them (e.g. 1.2.1 followed by 1.3.0) could contain breaking changes; so we wouldn't want users to receive those updates automatically.

@mflendrich ping following https://github.com/Kong/kubernetes-ingress-controller/pull/1156/commits/b0d43dd2741e5e9cd9c40901f6da33535fe3fd6e


CI Fix

Codecov Report

Merging #124 (b2543a4) into main (0ad83ed) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #124   +/-   ##
=======================================
  Coverage   91.93%   91.93%
=======================================
  Files          23       23
  Lines        1240     1240
=======================================
  Hits         1140     1140
  Misses        100      100

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 87672aa...b2543a4. Read the comment docs.


Use TokenListing event instead of adding a call handler

We currently use a call handler on addToken for keeping track of token listings, but we can use the TokenListing event so that it works for networks that don't support call indexing.
@anxolin  do you know why it is setup like this?

Yes, this is because this was done before TokenList event existed in the contract. I think it's fine to change it to use the event if u want to go for it. The addToken adds it on the first time it sees a token, this is how I got by when there was no event.

Fixed with #107. Currently deployed to:

xDAI
Rinkeby
Staging

Deployed and working!


add support for downloading data files from the web

This is related to #934
In the simplest sense, the following code collects remote data
import urllib.request
import io

url = "https://gavinhuttley.github.io/tib/_downloads/b772b1a069dd1c0925b4e5a7f3ceb4f9/brca1-bats.fasta"
d = urllib.request.urlopen(url)
f = io.TextIOWrapper(d)

In the first instance, this requires adding a function to cogent3.util.io called open_url. What should it return? Should it just be d, or f? Something else?
The function should fit in with top level load functions, e.g.
from cogent3 import load_aligtned_seqs

aln = load_aligned_seqs(url, moltype="dna")

Should work.
We need tests (added to tests/test_util/test_io.py) for the case where the remote data is a plain text file of a supported format, and a compressed file of a supported format.

Hi
I would like to solve this issue.
I am going to read contributing guideline and code of conduct before starting.

Awesome! Let me know if you hit any stumbling blocks or need to discuss anything!

Hi
I have written some small code to download file from ftp server. I need some sample addresses to test it. Please provide me some links for ftp, http and https files.
Thank you

Use the cogent3 tests/data files.
The base url to all the raw data files (as distinct from GitHub html presentation of those) is https://raw.githubusercontent.com/cogent3/cogent3/develop/tests/data/. Here's a couple of examples:

the url for  data/brca1_5.tree is https://raw.githubusercontent.com/cogent3/cogent3/develop/tests/data/brca1_5.tree
the url for  data/sample.tsv is https://raw.githubusercontent.com/cogent3/cogent3/develop/tests/data/sample.tsv

Hi Gavin,
I pushed my changes and created a pull request. Please review and give me comments or merge this.
I removed url as pathlib.Path, because it does not work with "http://" format. It removes one of / characters.
Also I wrote my name as "Nick Shahmaras", because I use this name in work environments. If you don't agree, I can change it.
Thank you
Nabi

Awesome, thanks Nabi!
Happy for you to specify whatever name you like.
Unfortunately, the tests failed because windows uses different line
endings. You should get a "review" from me via GitHub which outlines how
to simplify your code and also how to address the test failure.
Cheers,
g
On 28 Jun 2022, at 5:29, Nick-Foto wrote:

Hi Gavin,
I pushed my changes and created a pull request. Please review and give
me comments or merge this.
I removed url as pathlib.Path, because it does not work with "http://"
format. It removes one of / characters.
Also I wrote my name as "Nick Shahmaras", because I use this name in
work environments. If you don't agree, I can change it.
Thank you
Nabi
--
Reply to this email directly or view it on GitHub:
https://github.com/cogent3/cogent3/issues/992#issuecomment-1167791116
You are receiving this because you authored the thread.
Message ID: @.***>

Professor Gavin Huttley,
Convenor, Masters in Quantitative Biology and Bioinformatics,
Research School of Biology,
ANU College of Science,
RN Robertson Building,
46 Sullivans Creek Road,
The Australian National University
Canberra ACT 2600 Australia
+61 2 6125 5308
CRICOS #00120C


[beta] Sandpack: provide bare components and move styles

It aims to remove the hack to avoid runtime CSS and introduces the possibility of moving all styles from Sandpack to React Docs. By doing this, we can eliminate Stitches runtime execution and add only the necessary styles instead of injecting everything.
Revert & solves: https://github.com/reactjs/reactjs.org/pull/5122

Server
Client

@gaearon it's ready to go!

awesome, thanks!

this regressed a couple of things:
there's a weird space to the left of the highlight

the focus ring is messed up

fixed in https://github.com/reactjs/reactjs.org/pull/5162


latest tag for edm images

Hi,
It would be convenient push latest tag for each edm image.
Thank you.

Hi,
I have changed the Jenkinsfile and both the docker-compose.yml (in root and deploy folders) to use latest images.
Please check and let me know if you need anything else.
Regards

Hi,
it's working correctly.
Thank you


Request a method for loading neurons from a byte stream

Something similar like load_data from neurom.io but taking byte stream and a type would be nice to have.
Thanks.

Rather than load_data, I think having the semantics of load_neuron (ie: returns a Neuron-like class) would be more useful.  For the textual formats (SWC & ASC), it should be pretty easy.  For a binary stream, like h5, I think it might be more difficult.

Done, StringIO can be now be used as an input of load_data.
It will save the input stream in a temp file and use it for loading the neuron.


.net5pv8 - Win32Exception when calling windows-auth-API from blazor page

Issue Title
in .net5, when calling a windows-auth-based API from a blazor page results in Win32Exception: the token supplied to the function is invalid, while in .net 3.1 the same call works fine.
General
.net SDK 5.0.100-preview.8.20417.9
vstudio 2019 preview 2
win10 latest, iis express
i have a fairly simple test app to showcase this error:

generate a default blazor server side app in visual studio
select "windows authentication"
switch to .net50 in the framework settings
remove all demo code and add the following two files:

index.razor (a blazor page to trigger an API request)
@page "/"

impersonation test

<button @onclick="doItHttps">test https</button>

@code{
    private void doItHttps()
    {
        string pichtmlsource = "https://localhost:44313/api/Image/9f3b4a7c-0d5f-41c5-aa92-b28b7aa80bf6";

        using (System.Net.WebClient client = new System.Net.WebClient())
        {
            client.UseDefaultCredentials = true;
            client.DownloadFile(new Uri(pichtmlsource), @"c:\temp\image.png");
        }
    }
}

ImageController.cs (API handler)
namespace imagetest
{
    [Route("api/[controller]")]
    [ApiController]
    public class ImageController : ControllerBase
    {
        [HttpGet("{guid}")]
        public async Task<ActionResult> Get(Guid guid)
        {
            return NotFound();  // breakpoint here
        }

    }
}

what is happening?
run the project.
access the api with a browser on https://localhost:44313/api/Image/9f3b4a7c-0d5f-41c5-aa92-b28b7aa80bf6
this works fine, the controller method is called correctly, verified with a breakpoint in debug mode.
now click the test https button in the blazor page -> you get an exception "Win32Exception: The token supplied to the function is invalid"

when running the same test with .net core 3.1 as target framework, the call succeeds without problem, verified with a breakpoint:

additionally, it seems that switching to http instead of https also gets rid of this issue. so this seems to be only happening with https calls and .net 5 preview.

i could not reproduce this with .net5 RC1
will try some more but this can probably be considered as "fixed"

Thanks for testing in RC1.


Player/game deletions only delete last item checked

Both player and game pages have checkbox-based delete functions, but both only respect the last item selected. This is due to the form submitting multiple player_id parameters with the POST, but the PlayerCreateForm and GameCreateForm only defining that parameter as a single item. This should theoretically be fixable using a FieldList but I haven't yet gotten it working.

Should be implemented using new CheckboxTableField introduced in #47

#53 fixes this for games, and introduces (yet another) new way to manage tables. Players view should be updated similarly (and probably, Users as well)


ValueError: Configurable 'ExperimentConfig' doesn't have a parameter named 'datasource_spec'.

Just following along the colab notebooks.
Processed the video, trained the model with dataset saved to /content/gdrive/My Drive/nerfies/captures/capture1 and config.gin and checkpoints saved to /content/gdrive/My Drive/nerfies/experiments/capture1/exp1.
For Model and dataset configuration during rendering, the following error occurs:
Loading config from /content/gdrive/My Drive/nerfies/experiments/capture1/exp1/config.gin
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-13-573aff68880d> in <module>()
     27   logging.info('Loading config from %s', config_path)
     28   config_str = f.read()
---> 29 gin.parse_config(config_str)
     30
     31 config_path = Path(train_dir, 'config.gin')

7 frames
/usr/local/lib/python3.7/dist-packages/gin/config.py in parse(cls, binding_key)
    917     if not _might_have_parameter(configurable_.wrapper, arg_name):
    918       err_str = "Configurable '{}' doesn't have a parameter named '{}'."
--> 919       raise ValueError(err_str.format(selector, arg_name))
    920
    921     if configurable_.allowlist and arg_name not in configurable_.allowlist:

ValueError: Configurable 'ExperimentConfig' doesn't have a parameter named 'datasource_spec'.
  In bindings string line 3
    ExperimentConfig.datasource_spec = {

I checked config.gin file and ExperimentConfig.datasource_spec is there.
I check configs.py and I see datasource_cls instead of datasource_spec - should this be changed?

Similarly, ModelConfig in the colab should be changed to NerfModel?
and I've commented out the following in the generated config.gin as these are not available in configs.py
# NerfModel.use_appearance_metadata = 1
# NerfModel.warp_field_type = 'se3'
# NerfModel.num_warp_freqs = 8

Are you going to update how config.gin is setup in the colab notebook so that gin.parse_config(config_str) works smoothly?

I think that I've found a workaround for this issue.
I was mistakenly running the Nerfies training colab notebook, because this was linked in the "Process a video into a dataset" colab linked from the README. This creates this file: /content/gdrive/My Drive/nerfies/experiments/capture1/exp1/config.gin
This config.bin file is not compatible with HyperNeRF_Render_Video.ipynb.
For example, it includes ExperimentConfig.datasource_spec, and generally looks very different.
Instead, I tried running the HyperNeRF training colab notebook, which creates the hypernerf_experiments folder. The corresponding config.gin file is compatible with the HyperNeRF_Render_Video.ipynb.


Add documentation to use kubectl proxy --port 8002  incase aks browse does not work

I faced this issue with my AKS cluster:  https://github.com/Azure/azure-cli/issues/6811
I was able to workaround with this suggestion. Its useful to provide this here in documentation until the issue is Open
instead of az aks browse run:
kubectl proxy --port 8002
then navigate to:
http://<IP_ADDRESS>:8002/api/v1/namespaces/kube-system/services/http:kubernetes-dashboard:/proxy/

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

ID: 2ba1dad2-9792-2a7b-cdb6-68da0524cff3
Version Independent ID: 42736112-f6db-d241-e89b-48fd2c35ceb7
Content: Manage an Azure Kubernetes Service cluster with the web dashboard
Content Source: articles/aks/kubernetes-dashboard.md
Service: container-service
GitHub Login: @TylerMSFT
Microsoft Alias: twhitney

Thanks for the feedback! We are currently investigating and will update you shortly.

@anushreeringne  I have assigned the issue to the content author to investigate further and update the document as appropriate.

Sorry you ran into issues, @anushreeringne
As noted in that product issue, the workaround doesn't consistently unblock people that are having problems. I'll following up with the product team and CLI owners for an actual engineering fix here. There shouldn't be a need to specify alternate ports, or at the least, the error message should be more prescriptive as to what can be done to workaround specific port issues. If needed, we'll update the docs following that engineering work.
@MicahMcKittrick-MSFT For now, #please-close


password wrong?

i cant longin in the interface, can u helpme?

Although empire has <IP_ADDRESS> as its Host, try entering the actual IP address of your empire server. If its on your localhost, <IP_ADDRESS>
Let me know if that works

Thanks for your answer, I had little time but tomorrow I'll check and confirm it

I've tried as you mentioned but I can't log in, in the image I show the command I use to run empire

Ok, I think I see the issue. I have the port 1337 as a placeholder for that textbox, but you still need to type in 1337 to set that value. I should change that to be  or something. Try entering that manually then connecting.

Hahahahaha! That's what it was! OMG! solved problem


Modernise the library structure to use pyproject.toml?

ocf-data-sampler was created from our template which I think is the slightly older way of doing it. We use requirements.txt and a setup.py file. We should check if the current best-practice is still to use pyproject.toml and update to whatever this best-practice is

Hello there @peterdudfield! I've created a PR for this issue. Would you mind reviewing and letting me know your feedback, please?


[Integration Tests] Re-architect and re-factor integration tests

Objective
Define the line between integration tests and E2E tests, and update the codebase to reflect those changes.
Origin Document
This is followup to some of the work & exploration done in pkg/client/delegation/client_integration_test.go as part of #220 and relates to this comment

Goals

Clearly identify the distinction between unit tests (i.e. no network), integration tests (i.e. in-memory network) and E2E tests (i.e. local network)
Define patterns and helpers to implement integration tests in the future easily
Avoid using LocalNet in integration tests and reserve that for e2e tests

Deliverables

[ ] Document the difference between unit tests, integration tests and e2e tests
[ ] A PR that re-factor NewLocalNet and related helpers after determining how integration tests should be designed
[ ] A PR that enables existing integration tests in our CI (skipping failing integration tests w/ TODOs)
[ ] Separate PRs for each test (or helper refactor, etc.) to fix failing integration tests and/or complete in-progress integration tests from #220.
[ ] A PR that refactors TxClient to be a ReplayClient (see: #256)

Non-goals / Non-deliverables

Adding new integration tests
Adding new e2e tests
Adding new functionality

General deliverables

[ ] Comments: Add/update TODOs and comments alongside the source code so it is easier to follow.
[ ] Testing: Add new tests (unit and/or E2E) to the test suite.
[ ] Makefile: Add new targets to the Makefile to make the new functionality easier to use.
[ ] Documentation: Update architectural or development READMEs; use mermaid diagrams where appropriate.

Creator: @Olshansk
Co-Owners: @bryanchriswhite @h5law

@bryanchriswhite Can you review the goals & deliverables and let me know if it captures what's needed in conjunction with what you had in mind.

Given my current understanding, I agree that it makes sense to remove the integration tag from "integration" tests as they SHOULD, by definition, not depend on localnet/devnet.

Relates to:

#266
#250

@bryanchriswhite While continuing to learn & understand the Cosmos SDK source, I came by [1].
I haven't looked at the overlap or inter-dependencies in code / approach between what we have and [1], but wanted to understand if:

Is there overlap here?
Should we consider leveraging this approach or keep following what we have in flight?

[1]  https://github.com/cosmos/cosmos-sdk/blob/main/tests/integration/distribution/keeper/msg_server_test.go#L47

We've got this figured out now after the migration.


14975-fix style and validation

Issue #: /bcgov/entity#14975
Description of changes:
UX observations:

display one check mark beside the related applicant type since only one type of applicant is required

alignment of the action buttons be the same level as text on the left

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the bcrs-entities-create-ui license (Apache 2.0).

^^ I restarted the failed jobs -- looked like environment error, not code error.

^^ I restarted the failed jobs -- looked like environment error, not code error.

Thank you!


Add golang endpoints to fetch and save uri signing keys.

This PR adds rest endpoints to fetch and store jwk keysets to riak.  A new bucket is created in RIAK for this purpose.  Execute this command to create the bucket:
$ riak-admin security grant riak_kv.get,riak_kv.put,riak_kv.delete on default cdn_uri_sig_keys to keysusers
The api adds two vendored  libraries as this api uses the native Riak protobuffer endpoints.
vendor/github.com/go-jwx
vendor/github.com/basho/riak-go-client
Files changed or added, not including the vendored library files are:
traffic_ops/app/conf/development/riak.conf
traffic_ops/app/conf/integration/riak.conf
traffic_ops/app/conf/production/riak.conf
traffic_ops/app/conf/test/riak.conf
traffic_ops/traffic_ops_golang/config.go
traffic_ops/traffic_ops_golang/perlconfig.go
traffic_ops/traffic_ops_golang/perlconfig_test.go
traffic_ops/traffic_ops_golang/riak.go
traffic_ops/traffic_ops_golang/routes.go
traffic_ops/traffic_ops_golang/traffic_ops_golang.go
traffic_ops/traffic_ops_golang/wrappers.go

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/397/

can you update the docs with your new riak-admin command?
https://github.com/apache/incubator-trafficcontrol/blob/master/docs/source/admin/traffic_vault.rst

@dneuman64 - docs are updated.  See 2nd commit.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/398/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/354/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/355/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/399/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/400/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/356/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/357/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/401/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/358/

@jrushford - can you create a simple issue (https://github.com/apache/incubator-trafficcontrol/issues) with a short description of what you adding exactly. really, i'm just curious which api endpoints are being added.
and then you can link the issue to this PR

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/406/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/362/

@mitchell852 I updated the PR comments and added info about the api endpoints.  Is there api documentation that needs updating?

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/409/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/365/

@jrushford - yes, you should add these endpoints to the deliveryservice.rst file for version 1.2. thanks.

@mitchell852 why would he add it to the 1.2 docs when it is a 1.3 route?

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/417/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/436/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/392/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/452/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/408/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/463/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/464/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/419/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/420/


gnomeExtensions.timepp: unstable-2019-03-30 -> unstable-2020-03-15

Motivation for this change
This update is supposed to unbreak the package.
Things done
I didn't test the extension yet.

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

/nix/store/kx1qhzmpffzpib6ivvbqjvrs1db1v767-gnome-shell-extension-timepp-3.32  35.8M

/marvin opt-in
/status needs_reviewer

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/279

Could you backport to 20.09?

Done. #98287
Thanks!


Add noImplicitOverride flag

The flag noImplictOverride has been set, ensuring that the override keyword is used whenever a subclass overrides a field/method from a parent class. This ensures this library remains compatible with projects that use this flag.
The override keyword was only needed in one place.
Fixes https://github.com/KeystoneHQ/ur-registry/issues/17

This PR is in draft because it depends upon #18


Add build.config to make sure we are not adding "Demo App" logic to the final lib

We have 2 different build.config:

Demo/Development/Calibration - one of the names
Release

the differences between these 2 configurations are:

in Release, we should not bring any dependencies in Gradle (besides google services)
in Release we have different functionality onScanResult (we will not measure GPS location, we will get is as part of the ble message).

@ButtersHub what dependencies we have on dev config ?

@orenktaboola for example the library that creates csv


seriesCountLimit is not explained

The below statement does not make sense and fails to convey what the seriesCountLimit configuration option represents.

seriesCountLimit is the max number of data time series a metric can contain. Once this limit is reached, calls to TrackValue().

Please provide an explicit example on how seriesCountLimit can be exceeded. In a similar manner to the example of how valuesPerDimensionLimit is exceeded.

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

ID: cd881c48-d5ae-45b5-7225-2633c523b48f
Version Independent ID: 7f35db02-2944-7453-85ec-a5816a635fa1
Content: Get-Metric in Azure Monitor Application Insights - Azure Monitor
Content Source: articles/azure-monitor/app/get-metric.md
Service: azure-monitor
Sub-service: application-insights
GitHub Login: @lgayhardt
Microsoft Alias: lagayhar

@olitomlinson -
Thanks for brining this to our attention. We will investigate it further and update you shortly.

I found these tutorials and samples on similar travels which helped with my understanding
https://github.com/microsoft/ApplicationInsights-dotnet/issues/774

Sorry for the delay and thanks for the feedback. I made a PR and added on to the statement you mentioned to make it more clear "seriesCountLimit is the max number of data time series a metric can contain. Once this limit is reached, calls to TrackValue() that would normally result in a new series will return false."
The change should go live tomorrow.
#please-close


refactor enricher module

Need to manage state inside runner.enricher instead of using global vars
Need to refactor internals of enricher to be easier to test and extend
Consider breaking feed manager out into a separate module, recycle only feed manager and let enricher persist.

Calibrate breakout: 26430a849d40effa37a1c61f76103411cb00052e


Potential Feature: Module/Plugin Functionality

Hi Guys,
This is a feature proposal aimed towards addressing the problem of common modifications on Peatio exchanges.
Problem Statement
Peatio Exchanges of all fork derivations often have similar modifications done to the code locally upon install, for the purpose of implementing or integrating commercial, proprietary, needed software. Due to the nature of Peatio, and the RubyKube flavor being an MIT License codebase, integrating potentially proprietary software or commercial software such as Tradingview, ChartIQ or Trulioo is made potentially difficult due to licensing issues related to including it in the codebase and the implications of being reliant on a third-party service provider.
Solution Statement
By creating a system to allow for modules, which in this context is snippets of code that override certain existing functionality or adds new functionality to the codebase without having it included in the main repository, we can allow for third-party software integrations without having to define explicit support for it, allow for the standardization of commonly repeated additions, potentially improve the security of said additions as they can be vetted by the open market versus having individual developers build custom integrations for each exchange.
Here's a Potential Integration Scenario, using Chart.IQ (as I'm sure everyone's sick of hearing about TradingView all the time),
integration can be broken apart into two parts, the code that overwrites the existing charting library and the proprietary code, which can be dropped in (in this case, the licensed/trial ChartIQ javascript library)

Introduced Complications
Since Peatio is handling crypto, the obvious issue of allowing third-party plugins overwrite anything can be raised.  One way we can mitigate the aforementioned issue is by limiting what a "module" can have access to. While it won't protect a motivated party, it can be used as a litmus test when analyzing modules.
I know that proposals are a dime a dozen and that this specific feature proposal introduces a lot of potential issues, so I thought I'd put this out there as a starting point of conversation to go deeper into expanding the sideways functionality of the OpenWare implementation of Peatio.
Let me know what y'all think!

I think your example is old.
From 2.0 the trading UI has been removed from the peatio completely and you are free to implement your own UI.
I feel like your approach is similar to what WordPress does, you can install a plugin and it can overwrite exiting functions.
About the overwriting files and extending the functionality, it will help a lot in managing the custom functionalities, but also comes with a big risk, a potential risk of getting unwanted code which was in a third-party module.
All in all, I'd say you can create custom Docker image in which you can copy the required files to the proper location and you can use the image.

I'm closing this issue as @martianatwork is correct


Revert "Use local IPC adapter instead of DBUS one if possible"

Reverts Pelagicore/facelift#239

Not needed anymore.


convert environment0000.txt to snellius/ossc

This pull request adds requirements files for copying the venv for the summer school from the RA to the OSSC.
Instructions. On a snellius login node, run
source ossc/modules.sh

this creates the following files:

requirements_ossc.txt: file to share with SURF for setting up the venv
snellius_missing: the packages that are in requirements0000.txt but not in the snellius environment

Once SURF has installed the venv, one should be able to activate the entire environment with
module load xyz # load all modules that have `module load` in the the file `ossc/modules.sh`
source ossc_env/bin/activate

for duckdb, do we need other dependencies, ie the executable mentioned here?

This looks great @f-hafner! I wonder if it's worth separating the libraries required for data processing and modeling (which we need at OSSC) from jupyter and the libraries required from visualization (which we don't need at OSSC). Regarding duckdb, we could also not support it. I doubt people will end up using it.

@jgarciab , I removed duck db and the jupyter dependencies. I think it could be handy to plot some learning curves or similar directly on the ossc, so I suggest keeping the plotting libraries.


DEPR: Remove legacy offsets

[x] tests passed
[x] passes git diff upstream/master | flake8 --diff
[x] whatsnew entry

Follow-up to #13590. Remove legacy offset aliases that remained in pandas/tseries/frequencies.py: _period_alias_dictionary() and _period_alias_dict.

@sinhrks
hmm, were these previously deprecated?

@jreback All the removed aliases raise a FutureWarning in 0.18.1 and a ValueError in master.

@agraboso ok, guess weren't tested!
@sinhrks ?

The are a few tests — see, for example,

test_period.py#L444-463
test_period.py#L689-691
test_period.py#L1148-1165
test_offsets.py#L4561-4565

But I don't know if there may be some edge cases in which the removed aliases could be accepted.

Current coverage is 85.23% (diff: 100%)

Merging #13868 into master will decrease coverage by 0.01%

@@             master     #13868   diff @@
==========================================
  Files           140        140
  Lines         50455      50399    -56
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits          43014      42958    -56
  Misses         7441       7441
  Partials          0          0

Powered by Codecov. Last update 59f2557...2544d41

Yes it has been missed as not tested. Thanks for the catch!
NOTE: I found a condition which doesn't show warning. I think it is rare and can't be a reason to keep the impl, but may need discussion.
pd.Period(ordinal=1, freq='SECONDLY')
# Period('1970-01-01 00:00:01', 'S')

@sinhrks pd.Period(ordinal=1, freq='SECONDLY') raised a FutureWarning in 0.18.1. I added a test of pd.Period(ordinal=1, freq='SECONDLY') (and other removed aliases) that fails on master but passes with this PR.

@agraboso You're right, confirmed using 0.18.1 to show warning.

thanks!