[StyleCop] Fix all the warnings on Bot.Builder.Tests

Changes made:

Add/ Remove trailing whitespace
Add trailing coma
Remove extra spaces

No issues found in Microsoft.Bot.Builder.dll
No issues found in Microsoft.Bot.Builder.AI.Luis.dll
No issues found in Microsoft.Bot.Builder.AI.QnA.dll
No issues found in Microsoft.Bot.Builder.ApplicationInsights.dll
No issues found in Microsoft.Bot.Builder.Azure.dll
No issues found in Microsoft.Bot.Builder.Dialogs.dll
No issues found in Microsoft.Bot.Builder.TemplateManager.dll
No issues found in Microsoft.Bot.Configuration.dll
No issues found in Microsoft.Bot.Connector.dll
No issues found in Microsoft.Bot.Schema.dll

Compat issues with assembly Microsoft.Bot.Builder:
TypesMustExist : Type 'Microsoft.Bot.Builder.AutoSaveStateMiddleware' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.BotAdapter' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.BotAssert' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.BotCallbackHandler' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.BotFrameworkAdapter' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.BotFrameworkHttpStatusCodeErrorDetectionStrategy' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.BotState' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.BotStateSet' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.ConversationState' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.DeleteActivityHandler' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.IBot' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.IBotTelemetryClient' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.IMiddleware' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.IntentScore' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.InvokeResponse' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.IPropertyManager' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.IRecognizer' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.IRecognizerConvert' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.IStatePropertyAccessor<T>' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.IStatePropertyInfo' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.IStorage' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.IStoreItem' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.ITranscriptLogger' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.ITranscriptStore' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.ITurnContext' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.MemoryStorage' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.MemoryTranscriptStore' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.MessageFactory' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.MiddlewareSet' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.NextDelegate' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.NullBotTelemetryClient' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.PagedResult<T>' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.PrivateConversationState' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.RecognizerResult' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.RecognizerResultExtensions' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.SendActivitiesHandler' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.Severity' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.ShowTypingMiddleware' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.StorageExtensions' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.TraceTranscriptLogger' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.TranscriptInfo' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.TranscriptLoggerMiddleware' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.TurnContext' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.TurnContextStateCollection' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.UpdateActivityHandler' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.UserState' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.Adapters.TestAdapter' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.Adapters.TestFlow' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.Adapters.ValidateReply' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.Integration.BotFrameworkOptions' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.Integration.BotFrameworkPaths' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.Integration.IAdapterIntegration' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.Integration.MessageSerializerSettings' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Builder.TraceExtensions.ITurnContextExtensions' does not exist in the implementation but it does exist in the contract.

Compat issues with assembly Microsoft.Bot.Schema:
TypesMustExist : Type 'Microsoft.Bot.Schema.AadResourceUrls' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.ActionTypes' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.Activity' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.ActivityExtensions' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.ActivityImportance' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.ActivityTypes' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.ActivityTypesEx' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.AnimationCard' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.Attachment' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.AttachmentData' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.AttachmentInfo' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.AttachmentLayoutTypes' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.AttachmentView' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.AudioCard' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.BasicCard' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.CardAction' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.CardImage' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.ChannelAccount' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.ContactRelationUpdateActionTypes' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.ConversationAccount' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.ConversationMembers' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.ConversationParameters' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.ConversationReference' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.ConversationResourceResponse' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.ConversationsResult' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.DeliveryModes' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.EndOfConversationCodes' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.Entity' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.Error' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.ErrorCodes' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.ErrorResponse' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.Extensions' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.Fact' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.GeoCoordinates' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.HeroCard' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.IActivity' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.IContactRelationUpdateActivity' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.IConversationUpdateActivity' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.IEndOfConversationActivity' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.IEventActivity' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.IHandoffActivity' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.IInstallationUpdateActivity' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.IInvokeActivity' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.IMessageActivity' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.IMessageDeleteActivity' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.IMessageReactionActivity' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.IMessageUpdateActivity' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.InnerHttpError' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.InputHints' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.InstallationUpdateActionTypes' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.ISuggestionActivity' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.ITraceActivity' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.ITypingActivity' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.MediaCard' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.MediaEventValue' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.MediaUrl' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.Mention' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.MessageReaction' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.MessageReactionTypes' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.MicrosoftPayMethodData' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.OAuthCard' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.PagedMembersResult' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.PaymentAddress' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.PaymentCurrencyAmount' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.PaymentDetails' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.PaymentDetailsModifier' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.PaymentItem' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.PaymentMethodData' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.PaymentOperations' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.PaymentOptions' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.PaymentRequest' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.PaymentRequestComplete' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.PaymentRequestCompleteResult' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.PaymentRequestUpdate' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.PaymentRequestUpdateResult' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.PaymentResponse' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.PaymentShippingOption' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.PaymentShippingTypes' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.Place' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.ReceiptCard' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.ReceiptItem' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.ResourceResponse' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.RoleTypes' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.SemanticAction' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.SigninCard' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.SuggestedActions' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.TextFormatTypes' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.TextHighlight' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.Thing' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.ThumbnailCard' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.ThumbnailUrl' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.TokenExchangeState' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.TokenRequest' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.TokenResponse' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.TokenStatus' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.Transcript' does not exist in the implementation but it does exist in the contract.
TypesMustExist : Type 'Microsoft.Bot.Schema.VideoCard' does not exist in the implementation but it does exist in the contract.

Promoted to MS 1623


PhantomJS fails with TypeError

File:
var casper = require('casper');
var url = './dist/index.html';

casper.
  start( url ).
  then(function(){
    // Take a screenshot of the UI component
    phantomcss.screenshot('#intro', 'a screenshot of my dialog');
  });

Error:
⇒  casperjs test/home.test.js
TypeError: undefined is not a constructor (evaluating 'casper.
  start( url )')

  phantomjs://code/home.test.js:5 in global code
  :0 in injectJs
  phantomjs://code/bootstrap.js:456

This is an identified issue in phantomJS: https://github.com/ariya/phantomjs/issues/14211 and will be fixed in 2.5. Until then, is there anything we can do with here to handle this?

I don't think you need to require CasperJS if you invoke from the command line (https://github.com/Huddle/PhantomCSS/blob/master/casperjs.bat) on Windows or just the Casperjs executable on other platforms. The demo works without it, https://github.com/Huddle/PhantomCSS/blob/master/demo/testsuite.js


RuntimeError: IOLoop is already running

I ran the project in web ui and return exception
(i pull the newest version of pyspider )
Traceback (most recent call last):
File "run.py", line 360, in
app.config['fetch'] = lambda x: webui_fetcher.fetch(x)[1]
File "/Users/ericyue/kechengpuzi/pyspider/fetcher/tornado_fetcher.py", line 109, in fetch
return self.ioloop.run_sync(functools.partial(self.async_fetch, task, callback))
File "/usr/local/lib/python2.7/site-packages/tornado/ioloop.py", line 448, in run_sync
self.start()
File "/usr/local/lib/python2.7/site-packages/tornado/ioloop.py", line 748, in start
raise RuntimeError("IOLoop is already running")
RuntimeError: IOLoop is already running

i got the same error after installing the latest version


Don't display a 'Trade' button next to assets that are prohibited by Swap page

Describe the bug
A 'trade' button appears next to tokens that cannot be swapped
To Reproduce
Steps to reproduce the behavior:

Delegate UM to a validator, optionally unbond some UM from a validator
Navigate to Assets page
Mouseover the token in your asset list
Click the Trade button to view a swap form pre-filled with this asset
See you have 0 of this asset available to swap

Expected behavior
The asset list should not invite the user to trade a token that is considered invalid by the swap page.
Screenshots

Additional context
I examined this problem on a local devnet

i agree that the correct action may be to simply not filter assets for swap input.
i think it may also make sense to not show delegation tokens in the normal asset list, but provide a trade button next to the appropriate validator on the stake page.


Turning an output off unsets its CRTC

Turning a connector off should just set active to 0. The mode and CRTC should not be changed. Need to experiment and check if that improves time taken to enable/disable a connector.
Need to make sure we unset the CRTC on the disabled connector when we use it to light up another connector.

Looks like Weston does this as well. Also amdgpu returns EINVAL. Maybe I'm mistaken then, but I'm not sure why ACTIVE exists.

According to #dri-devel, setting ACTIVE without changing anything else should work properly.


implemented drop command

Closes #3.

Figured I'd take a stab at it. This is just drop for formulae and casks. I figured mas/whalebrew integration into add/drop was a separate feature and could be implemented as such. let me know what you think!

One case I didn't account for and that we didn't discuss is the ability to drop a tap if dropping the only/last formula/cask that requires it. But I think that could be a separate feature/PR if it is desired.

Thank you so much for submitting this! This looks really great. I was struggling to get mas parsing to work with Homebrew's API and I think you're right that it should be done separately.

Thanks for the review! I believe I've applied all the changes you suggested. My apologies for leaving in hardcoded strings I had used for testing a dummy local Brewfile lol.
As to your last point, I do think there is a potential conflict that needs to be addressed. As the code is written right now if a brewfile contains both of the following lines:
brew "pyenv"
brew "some-tap/pyenv"

I'm not actually sure what would happen if the user did brew drop pyenv. Would the homebrew formula check default to the core formula over the custom tap? If it did, then we'd only remove the first line. If it didn't, we'd potentially drop both. But I'm also not sure how important this case is, considering those two formula would conflict with each other anyway and probably wouldn't both be installed/present in the Brewfile.
I could be missing something though. Let me know if you think we need to address it in this PR and I can think of a work around.

@boldandbrad I made some changes that I believe resolve the problem of formulae/casks having the same short name (and brew drop potentially removing the wrong lines). Let me know if you have any feedback or improvements with it, or if you find any logic errors.

In addition to my changes in https://github.com/superatomic/homebrew-bundle-extensions/pull/7/commits/6fcefe5edd6d229b259c2e5e3e1e459af4ce8b70, I have also added a section to the README.md file about brew drop in https://github.com/superatomic/homebrew-bundle-extensions/pull/7/commits/84a26265593535a8556131bed39a3801444b08b8.

@boldandbrad I made some changes that I believe resolve the problem of formulae/casks having the same short name (and brew drop potentially removing the wrong lines). Let me know if you have any feedback or improvements with it, or if you find any logic errors.
Changes: 6fcefe5

I think this logic looks good and makes sense. In practice if we find edge cases we can always patch.

@boldandbrad I made one more change (see https://github.com/superatomic/homebrew-bundle-extensions/pull/7/commits/419c4c199b8e3feb55032a354f942f6ae43eb1c4). Before the regular expression was updated, I noticed that sometimes brew drop wouldn't detect anything to remove, but it would still say that it succeeded. I have added modifications to check whether this happens, and to display an error message if it does. Hopefully it is impossible for this message to appear with the new improvements, but if we missed something, the correct message will be displayed.
Here's what it would look like:
==> Using Brewfile at '/Users/Ethan/.dotfiles/brew/Brewfile'
Error: Couldn't remove Formula coreutils from Brewfile
Please open an issue on GitHub:
    https://github.com/superatomic/homebrew-bundle-extensions

@boldandbrad Unless you have any additional feedback or changes that you want to make, I think this PR is ready to be merged. :tada:

I say send it!

@boldandbrad Thank you so much for submitting this PR and for being so helpful!


Using custom EF builds - public signing service?

Disclaimer: This is also a general question which applies to all microsoft open source libs, but I am posting it here because it currently affects me in context of EF.
Story:
For a large project we have been using my custom fork to overcome this issue.
Since it took almost 2 years for this feature to land into EF master (and still not released) (https://github.com/aspnet/EntityFramework6/pull/40), I am happy that at least we had the opportunity to use my custom EF version (we could not wait 2 years for this feature - so open source FTW! 👍 )
However, If you want to use a custom EF version, you need you to build it using your own signing key because the official MS signing key is obviously not public.
This leads to the following problem:
All external tools  (e.x. Linqpad) / libraries  (ex. extensions for EF6) reference the official strong named version of EF6. So these tools/libs will not work with your custom build and so you cannot use them.
This is a major drawback and really sucks.
Because #40 is now resolved and will land in EF 6.2, I am planning to switch back to the official nuget version of EF. This will allow tools depending on the offical version to work again. However, as soon as I would need a custom build again (for example a new fix which will need its time before landing in official), I'd have all of these problems again. (And i would probably have to remove third party EF extensions because they would break again)
I think this could be solved if microsoft could provide a public signing / build service or something similar. Is there any way of solving this issue?

Unfortunately if we solved this, then anyone would be able to use the mechanism, which would defeat the purpose of strong naming.
You could use our nightly builds, which are signed and include the fix you want.
You could also look at disabling strong name verification for the EF runtime (see bullet 6 of Building the Runtime). Obviously there is some risk with doing that.

@rowanmiller Thanks for your feedback.
I have a question though:
What do you mean by this:

if we solved this, then anyone would be able to use the mechanism, which would defeat the purpose of strong naming.

According to the corefx wiki,  strong-names are used for identity, and not for security.
Furthermore it's the recommended practice to check-in the signing key to enable drop in replacements for open source libraries.
While i understand that you cannot publish the signing key for EF6 (since this is the global signing key MS uses for all it's libs since .NET 1.0?), I don't understand how a public signing service would defeat the purpose of strong naming?
Remember: For all Core** related projects everyone has access to the signing key, so this obviously does not defeat the purpose of strong naming.
Could you please elaborate this? Thanks :)

Fair point, to be a little more explicit...

I don't understand how a public signing service would defeat the purpose of strong naming?

The issue is that EF6 is signed with a Microsoft key. So if we had a public service then the output would be signed as if it were owned by Microsoft. With EF Core, we decided not to do this and we only strong name so that it can be consumed from strong named applications - not as a way to help verify the producer.
We can't really move EF6 to that model, because changing the key would break everything that currently works with EF6.

Thanks for the clarification @rowanmiller
I am glad that at least this is solved with EF Core and all other DotNet Core projects.


Blockchains (or Wallet) can’t be on VirtualBox shared folders

I have host system Windows 10 and Linux Mint 18.3 na VirtualBox as Guest.
I have shared Windows folder and I mount it:
sudo mount -t vboxsf vbshare ~/host
I prefer have several blockchains in shared folders, it is especially important for Bitcoin because has 211 GB od data, and I can share between my Virtual Linuxes. Also I can share Litecoin.
I can’t share Dash and I must all blocks in Linux, I also can’t copy from Linux to Windows and copy to another Virtual LInux due to errors. I must in Linux download from scratch.
Maybe problem is with BerkeleyDB and LevelDB enables it? I read that blocks are with LevelDB but Wallet no. Is possible have wallet on other directory than -datadir (as argument)?
But I don't know it is due to LevelDB:
"In 2013 a new bitcoin core was released and one of the supposed improvement was migrating from Berkeley DB to LevelDB"
But nice change in Bitcoin was in 2017 year between version 0.14.2 and 0.15.0

I don't think it has anything to do with LevelDB / BerkeleyDB. Should always be possible to do a symlink anyways if you just need to trick your system into thinking the folder is in one place when it's actually in another.


Docs

Closes #9

[x] Create initial docs with auto generated reference docs.
[x] Setup RTD.
[ ] Wait for #18 because that affects the docs quite a bit.
[ ] Clean up, complete, and improve the docs.
[ ] Set RTD branch to main.

See https://jupyter-rfb.readthedocs.io/

How does mkdocs compare to sphinx for api docs? For example the stuff in the vispy core repository has plugins for auto-generating the api docs from the source when the docs are built. There is also intersphinx which lets us link to other projects. This may be helpful so you can link to jupyter or ipywidgets docs elements. I also have my sphinx-gallery stuff that I just finished up that would be really nice to show produce automatic notebook examples that people can download and run.

My main motivation is that I like markdown so much more than rst :)
mkdocs feels a bit more work to setup (getting RTD configured correctly). But I've done that dance in another project so I had a head-start here.
I use mkautodoc which produces the reference docs. No intersphinx but also there's just one link to ipywidgets. Also there is no actual reference doc for ipywidgets.Widget (or I could not find it, if you do, let me know).
Example notebooks is a good point, though we can also leverage Github or MyBinder (?) for that. Not as slick, but this lib is more developer-facing than user-facing, so no need to be too fancy :)

Intersphinx downloads this file:
https://ipywidgets.readthedocs.io/en/latest/objects.inv
Running with the intersphinx module on the command line gives you a lot of output but looks like mostly examples. Looks like they don't document their API:
$ python -m sphinx.ext.intersphinx https://ipywidgets.readthedocs.io/en/latest/objects.inv
std:doc
        changelog                                ipywidgets Changelog                    : changelog.html
        contributing                             Contributing                            : contributing.html
        dev_docs                                 Develop and Build Documentation         : dev_docs.html
        dev_install                              Developer Install                       : dev_install.html
        dev_release                              Developer Release Procedure             : dev_release.html
        dev_testing                              Unit Tests                              : dev_testing.html
        developer_docs                           ipywidgets Development                  : developer_docs.html
        embedding                                Embedding Jupyter Widgets in Other Contexts than the Notebook: embedding.html
        examples/Layout Example                  Example.html Weather map                : examples/Layout
        examples/Layout Templates                Templates.html Using Layout Templates   : examples/Layout
        examples/Output Widget                   Widget.html Output widgets: leveraging Jupyter’s display system: examples/Output
        examples/Using Interact                  Interact.html Using Interact            : examples/Using
        examples/Widget Asynchronous             Asynchronous.html Asynchronous Widgets  : examples/Widget
        examples/Widget Basics                   Basics.html Simple Widget Introduction  : examples/Widget
        examples/Widget Custom                   Custom.html Building a Custom Widget - Email widget: examples/Widget
        examples/Widget Events                   Events.html Widget Events               : examples/Widget
        examples/Widget List                     List.html Widget List                   : examples/Widget
        examples/Widget Low Level                Low Level.html Low Level Widget Tutorial: examples/Widget
        examples/Widget Styling                  Styling.html Layout and Styling of Jupyter widgets: examples/Widget
        examples/Widget TagsInput                TagsInput.html TagsInput widget         : examples/Widget
        index                                    ipywidgets                              : index.html
        migration_guides                         Migrating custom widget libraries       : migration_guides.html
        user_install                             Installation                            : user_install.html
std:label
        /changelog.md                            ipywidgets Changelog                    : changelog.html
        ...

Not as slick, but this lib is more developer-facing than user-facing, so no need to be too fancy :)

I personally like consistency, but I also only know sphinx really and I don't care that much here. Go for it.

I personally like consistency

Yeah I understand that too :)  - I think I might turn this to rst after all.


Implement GetConsensusState method

Implement ConsensusState method , for compatibility with Tendermint RPC.
See: client.go

This method is specific to Tendermint. Optimint should always return meaningful error.


Trolling / Making Friends

hmmm what does this look like to you,
first commit is just my linter going mad
removed explicit binding, didn't test haven't used firebase before but since we are using an arrow function they implicitly bind

good trolling


Fix "file_lines" issue in testinfra_bdd/init.py

File __init__.py has 649 lines of code (exceeds 250 allowed). Consider refactoring.
https://codeclimate.com/github/locp/testinfra-bdd/testinfra_bdd/__init__.py#issue_629b55461d7f32000100001f

May be assisted with https://docs.pytest.org/en/7.1.x/how-to/writing_plugins.html#requiring-loading-plugins-in-a-test-module-or-conftest-file


Fix type of devices type

Fixes: https://github.com/opencontainers/runc/issues/566
For type rune, we can assign char as 'c' in struct, but after
marshal, it'll be presented as int32. So it should be a
number in our example of json file. Otherwise we'll got error:
json: cannot unmarshal string into Go value of type int32
If we trying to unmarshal the json file.
Signed-off-by: Qiang Huang<EMAIL_ADDRESS>

I found the example of fileMode is also wrong, pushing a patch to fix it.

I think we should change it from rune to string so that you can actually write "b", "c" in the json spec and you can easily know what type of device it is.  What do you think?

+1 for switching to string.

On Mon, Feb 22, 2016 at 11:32:06AM -0800, Vish Kannan wrote:

+1 for switching to string.

ditto

Updated, thanks.

On Mon, Feb 22, 2016 at 05:24:03PM -0800, Qiang Huang wrote:

Updated, thanks.

I prefer backticks to quotes for Markdown literals, but other than
that minor quibble, both 9cd1ae59 and 96c5ff07 look good to me.

@wking Using quotes so people know that's a string, after a second thought, I think backticks won't cause confusion, and it's more consistent with other usage in specs, updated, thanks.

On Mon, Feb 22, 2016 at 10:36:46PM -0800, Qiang Huang wrote:

… I think backticks won't cause confusion… updated…

9bab93004 and ccf3a246c look good to me.

LGTM

LGTM


gmaps dev version

We need to look at alternatives. Gmaps is very expensive. Unless we have a chance to get credits, we should explore OSM based options. @naveenpf What are you thoughts on mapbox ?

My preference would be Malayalam rendering of HOT Maps.
(https://github.com/hotosm/HDM-CartoCSS)
http://map.hotosm.org/#15/9.9840/76.2897


Urls for django 1.10

Please include this small fix and bump version so pip will be able to install a django 1.10 compatible version.

Hi. Thanks for sending in the pull request. I just realised you're second person sending one in, so I'll try to get a new release out during this week. Hopefully I can have it support the LTS as well. :)

Happy to hear you're still maintaining on the project!
Looking forward to the new version from pip ;-)

Ok, done a quick test against Django 1.8 + Django 1.10. Seems to work fine, just had to apply the same type of change in testproject.
I'll also need to update Django version in requirements (so probably just going to mark it as Django >= 1.8 for now).
Since I maintain my own repo and issue tracker, I might close this pull request once the changes have been made, and mirror it to Github (pull requests/issue reports over Github are still welcome, just a bit of manual work on my side to sync them to my own infra :)
I'll probably push the new version on Friday (atm a bit preoccupied :)

Of course, it might happen I lied a bit and that release is made tomorrow... On the positive side, it should also include support for transparency once I update pydenticon as well.

Whoops, clicked the wrong button.

Ok, merged the changes and created release. Attribution has been applied via git's --author flag.


⚠ Samsung has degraded performance

In 8ff954b, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2837 ms

Resolved: Samsung performance has improved in 69d3407.


Expose transport mode

Expose TransportMode in client facing APIs, rather than opaque reliable bool.

Tests are failing because of the changes that were merged from main. Minor updates needed.


Remove sd adapter retry

Remove retry logic from sd adapter monitoring. Stackdriver server no longer returns detailed timeseries that are failed to be written, but instead just returns a summary (https://github.com/googleapis/googleapis/blob/a667ffab90deb5e2669eb40ec7b61ec96a3d0454/google/monitoring/v3/metric_service.proto#L323). So this retry logic is effectively not working. Retry the whole CreateTimeSeries is not safe because there is no response code to reliably identify whether the request has reached the server or not. https://github.com/istio/istio/pull/19784#issuecomment-570275581 has more context (thanks @nicktrav for digging this up!).

@bianpengyuan: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pilot-multicluster-e2e_istio
412a4c8d29f29b9da3049073b577d13ff6bc01d3
link
/test pilot-multicluster-e2e_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

LGTM. Thanks for fixing.
Side note - do the Stackdriver folks know that this is essentially a regression in their API? i.e. there is no way to tell what time series failed and retry specific TimeSeries, which feels objectively useful?
I can mention it to some of our contacts, but I figured that given you work for G, you might have some backchannel and they could point you at an alternative approach?
At the end of the day, retries would be useful ...

@nicktrav yeah the reason is tracked internally and it seems being individual time series is too large to put in grpc error details. imo it might make sense because mostly what we want to retry is connection failure (server does not receive request), which will need to retry the whole batch. If individual time series is failed to be written, it suggests that time series is malformed and may not worth retry anyway.

@bianpengyuan - makes sense. Thanks.

Updated to retry the batch only for unavailable and deadline exceed. This removes the usage of CreateTimeSeriesError.

Updated to retry the batch only for unavailable and deadline exceed. This removes the usage of CreateTimeSeriesError.

Awesome. I think this should unblock the linter warnings I was seeing on #19784. I'll rebase once this lands.

Updated to retry the batch only for unavailable and deadline exceed. This removes the usage of CreateTimeSeriesError.

You can use CreateTimeSeriesSummary for client-side access to server-side statistics, if you find that useful.


Allow empty permissions on links again

Empty permissions are needed for infamous alias links. Through some PR that functionailty was dropped. Now it is back again

Works like a charm 👌🏽


Simplify configuration api docs

Refs: #31448
Currently the documentation around confgurations in vscode.d.ts sound very puzzling to me. Could we somehow simplify this - make it nicer?
If you agree this is needed I can come up with a proposal
fyi @jrieken

Sure, suggestion are very much appreciated

@isidorn Do you thought about any suggestions?

If nobody else complained then I believe it is good.
Also nothing better comes to mind at the moment


Remaining adapter sequences

Hello,
I was wondering if the inputs can handle adapter sequences between the fused transcripts without too much problems?
Thanks,
Chang

Dear Chang,
I don't understand how there could be adapter sequences between the fused transcripts. The adapters are added to the transcripts that are being sequenced, and the hypothesis of fusion transcripts is, that these transcript exist in the cell due to biological mechanisms, such as translocation in a cancer cell.
Therefore, I don't think that your case can happen. Or do you have some other datasource in mind?
Hope that helps,
Marcel

Ah well I'm looking to see if it can detect chimeric PCR transcripts and to see if it can map both (or more) transcripts with an adapter sequence in between.

I see. Well AERON allows for a large number of sequencing errors so if there was a short adapter at either end of the chimeric read, it may be able to find that.
You could simulate the case you have in mind and see whether AERON finds it. We have not tested it for this task.


pressed wrong button, ignore this

updating my fork

updating the fork

See https://docs.godotengine.org/en/3.1/community/contributing/pr_workflow.html for instructions on how to update your fork, PRs are not the right way to do it.


503 error using v3 endpoint

Hello,
Our team has been using v3 endpoint of the application for a while now and we're experiencing a 503 error. This normally infers an issue with the application's end, so I'm pinging @eduardoboucas for assistance on getting the application back up to speed, if needed.

Working on the same project, as unpreceden7ed, giving a screenshot of the error. Seems to be CORS related.

I want to make a statement to our progress.
We moved away from the public instance because it's not working anymore, as what this issue is about. We have set up our own instance on heroku and it's working fine as of now. However, we didn't clone this repository because apparently, it's in a broken state. Instead, we cloned the deploy branch of @VincentTam's fork. He went through the effort of merging PRs which brought the repo back to a working state, as explained in this issue. Thank you Vincent for that!
So to recap: the public instance is broken because of a CORS issue, the self-hosted instance is broken because of legacy functionalities not working because of v3.
Pinging @eduardoboucas to make you aware of this situation.

Thanks for the great info.  Looks like I need to spin up a new instance for myself.  Always fun.

I also hit this error by using the default API endpoint in the theme Hugo Future Imperfect Slim.

Needs to try other instances:

@staticmanaima
@BloggerBust-bot
???

I've picked up this project. The staticman public instance is not functional right now and your best bet is rolling back to a previous commit you know was working before and self hosting.

Duplicate of #317

@VincentTam I still get this error, using staticman master ("deploy to heroku"), and Hugo Future Imperfect Slim. I assumed that this master branch would have resolved this at this point (based on #319 and such). Do you have any tips?

@VincentTam I still get this error, using staticman master ("deploy to heroku"), and Hugo Future Imperfect Slim. I assumed that this master branch would have resolved this at this point (based on #319 and such). Do you have any tips?

@RyanTG I'm sorry I'm now occupied with my job training & I'm learning C#.  I haven't followed the development of Staticman for a year.  I might retake this if I've free time again.

No problem, good luck with your training. I opted to use staticmanlab, and that's been working for me. But, I question if that's a sustainable approach, given that you're not actively involved. But at any rate, thanks for that tool!

No problem, good luck with your training. I opted to use staticmanlab, and that's been working for me. But, I question if that's a sustainable approach, given that you're not actively involved. But at any rate, thanks for that tool!

I'll leave this question to others, while trying to find time to pick up Node.JS (maybe several months) later.

@RyanTG when did you deploy Staticman to Heroku? Prior to about 9 days ago when #346 was merged, master was still broken. As of right now, deploying master to Heroku should be working. As far as sustainable approaches, this project currently in need of maintainers. I do my best to resolve any breaking issues as they pop up but do not have much time to actively work on Staticman development lately.

Yes, it was within 9 days (7 days ago).
I don't know enough about staticmanlab to know what is different with that setup. But once it worked with that app, I gave up on troubleshooting my 503 error.

@alexwaibel I can confirm master works on Heroku, or at least the master I forked yesterday: https://github.com/shaftoe/staticman
I might have some time to help out here, where should I start from?

@alexwaibel I can confirm master works on Heroku, or at least the master I forked yesterday: https://github.com/shaftoe/staticman
I might have some time to help out here, where should I start from?

I'd greatly appreciate your contributions! The highest-value item right now is definitely updating the docs on the website. They're super out of date at the moment so it would help a lot of new users if we added things like notes about setting up Heroku instances and whatnot. Should be a good starter task too getting used to the whole system. Right now we have some great articles that I've been pointing users to, but having this info on the site would be better.
Relevant links:

https://travisdowns.github.io/blog/2020/02/05/now-with-comments.html
https://spinningnumbers.org/a/staticman-heroku.html
https://mademistakes.com/articles/improving-jekyll-static-comments/

I wonder if my issues were theme-related. I read all those relevant links when setting it up. I'll give it a shot with another theme, not https://github.com/pacollins/hugo-future-imperfect-slim, just to rule that out.


Continued ClientNode and REPL development

This builds out the controller for the node API to the point where I need to address a conflict between InteractionClient and InteractionServer.
Adds:

ControllerBehavior - initializes the node environment to act as a controller and tracks active discoveries
Discovery - a set of classes that manage discovery of commissionable devices
CommissioningClient - a behavior that handles commissioning and related metadata management

Fleshes out ClientNode related API.  Persistence and management of known nodes work now.
Also includes continued development on the "cli tool" REPL including numerous quality of life and aesthetic improvements.

For Discovery: In fact there are currently 3 types, "Locate", "Timed" with limited time and without time ... or is timed with no limit also a timed ? did not followed that up in code

The "timed" one will run until canceled if there is no timeout, I'll rename to "Continuous" and update documentation.

For Discovery: In fact there are currently 3 types, "Locate", "Timed" with limited time and without time ... or is timed with no limit also a timed ? did not followed that up in code

Actually, as noted in discord, for commissioning discovery it appears there's a default timeout of 60 seconds on BLE scans and 900 seconds on MDNS scans.  (See findCommissionableDevicesContinuously in MdnsScanner and BleScanner)...  so to support indefinite discovery I think we need to remove those timeouts


Added Oracle DB Extractor

Please merge this, I really this. I have added support for Oracle DB in dbcat to get the metadata.

Please merge this.

I need this feature too, you are a lifesaver!

+1

Thanks for the contribution @keenborder786 . The code looks good to me. Can you add a couple of tests?

Add another entry to connections.yaml. You'll also have to add corresponding asserts in test_add_sources
Add an OracleExtractor test similar to test_snowflake_extractor

These should be easy to add. I'll accept and merge it once the tests run successfully. Also can you confirm that you've tested the changes on an oracle db? I dont have one to test with.

@vrajat okay.


full-width characters are being cropped when minimap is enabled.

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.69.1
OS Version: Windows 10

Steps to Reproduce:

open / input text which is long enough to wrap lines, the line is consist of full-width characters (e.g. Chinese characters)
enable minimap

maybe we can consider making the display container one/two more text width wider?

Can you please try "editor.wrappingStrategy": "advanced"? The default wrapping strategy is optimised for being fast, but it doesn't work perfectly for non-monospace characters.

@alexdima
yes it helps. but it makes resizing windows very slow.
actually, double-spaced chars are technically monospaced (strictly occupying two monospaces).
maybe we can possibly optimize it.

PR most welcome. The "fast" word wrap computer is here

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


DTVF: Display of category timeseries

The digital lab use case has some string/ category time series for eg On/Off status, with values of on and off over time. It would be nice to be able to visualise this type of time series in the DTVF.
Also, the line chart may not be a suitable diagram for this. I have tested the visualisation with a boolean time series, but they do not look appropriate.

@sandradeng20 has also requested a similar ability.
There are a number of different ways to handle the ability to plot charts of different types, and a number of questions that need to be answerered before we can work on this (some of these I've listed below). Unfortunately, I don't think we'll add anything to support this in the short term.
To be discussed:

Should "timeseries" be used for data that isn't dependent on time (i.e. category data)?
Do we forgo charts in the side panel and wholly rely on a new dashboard system to show this data?
Should new triples (and new TBoxes) be created to denote how timeseries measurements should be displayed?
Should we continue using the FeatureInfoAgent to return data series, or look into some other method?

Tagging those that I think will need to be in that discussion (whenever it is): @gpeb2, @sm453, @jwja2, @cmclscourtney

Should "timeseries" be used for data that isn't dependent on time (i.e. category data)?

I believe the answer to the question "Should timeseries be used for data that isn't time-dependent?" should be a categorical no (pardon the pun). However, I believe what is meant by the original question is whether we can handle timeseries of categorical data, so definitely time-dependent data, but the values are categorical (e.g. "on" or "off" as categories) rather than continuous (e.g. temperature).

Do we forgo charts in the side panel and wholly rely on a new dashboard system to show this data?

I think we will probably want both (because both can be nice and useful).

Should new triples (and new TBoxes) be created to denote how timeseries measurements should be displayed?

Absolutely yes. In fact, we'd want to be much more general. As previously discussed on a number of occasions, we eventually want ontological mark-up of how to display anything.

Should we continue using the FeatureInfoAgent to return data series, or look into some other method?

I believe yes, for the time being, unless there are ideas for other methods on the table?


Revert "Bump viper version from 1.13.0 to 1.13.2"

What does this PR do?
Reverts https://github.com/DataDog/datadog-agent/pull/25107
Motivation
#incident-27075
Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


Split node into multiple modules, and QoL updates

From<Preset/HexColor> for Color
Numerical values for Color
Pass clippy lints
use thiserror for error handling
cargo fmt
replace JsonCanvas::new with derive Default

This is quite a big diff but most of it is just cargo fmt.

Thanks a lot! I will have a look on it.

I will try to use cargo fmt on my own to split format changes from "real changes"
I may have some question :) ( And thank you again to spend time to learn me all this best practices / usually used crates, etc...)

Any good editor will let you run cargo fmt whenever the file is saved, that helps keep things organised!
I'm happy to help! I recently got a job working in rust, and I'd never have gained the experience I needed for that without the FOSS community taking the time to help me; we should all pay it forward :)
I have another branch with some more speculative changes (using newtypes around node and edge IDs so that the type system prevents people mixing them up and prevents people mutating them) but I'll save that for another time.

Any good editor will let you run cargo fmt whenever the file is saved, that helps keep things organised!

I am using visual studio code. Just checked, editor.formatOnSave was not activated :-(

I'm happy to help! I recently got a job working in rust, and I'd never have gained the experience I needed for that without the FOSS community taking the time to help me; we should all pay it forward :)

I like it!

I have another branch with some more speculative changes (using newtypes around node and edge IDs so that the type system prevents people mixing them up and prevents people mutating them) but I'll save that for another time.

Let's manage this one, and then, I will be happy to have a look on your next one!


Different geometries for different zoom levels

While it is possible to define different tables for different zoom levels in the layer tables configuration it is currently impossible to define different geometries for different tables, or indeed the same table with different geometry fields.
It should be possible to define a geometry field with a table in the tables configuration to support multiple geometry fields. This will allow to have simplified geometries for the same location at lower zoom levels.
It would be possible to define the geometry field separated by a pipe or other symbol which cannot be part of a regular table or field name.

5 stars if this is solved

This is no possible by defining a geoms object in similar fashion to the tables array. Obviously null won't do anything in this object.
{
  "locales": {
    "UK": {
      "bounds": {
        "north": 62,
        "east": 5,
        "south": 49,
        "west": -13
      },
      "minZoom": 2,
      "maxZoom": 17,
      "maskBounds": true,
      "showScaleBar": true,
      "layers": {
        "ZoomGeom": {
          "display": true,
          "format": "mvt",
          "geom": "geom_3857_5m",
          "srid": "3857",
          "dbs": "MAPP",
          "qID": "id",
          "geoms": {
            "7": "geom_3857_100m",
            "8": "geom_3857_50m",
            "9": "geom_3857_50m",
            "10": "geom_3857_5m",
            "11": "geom_3857_5m",
            "12": "geom_3857"
          },
          "table": "geodata.uk_glx_geodata_seamless_shopper_town"
        }
      }
    }
  }
}

The geom will be determined in the mvt mod.
  const geoms = Object.keys(layer.geoms)

  var geom = geoms && layer.geoms[z] || layer.geom

  var geom = geoms && z < parseInt(geoms[0]) && Object.values(layer.geoms)[0] || geom

  var geom = geoms && z > parseInt(geoms[geoms.length -1]) && Object.values(layer.geoms)[geoms.length -1]  || geom

https://github.com/GEOLYTIX/xyz/commit/43dbab1d93bed30a8b24ed613c71e28e11aa5150


Two covers in the beginning.

(It it's not bug, please make check box to turn off it).

Considering how cover system works on Kindle this is working as intended.


decoding output

We have to do couple of things regarding decoding output:

Add configuration to write file to disk;

Compare WER/CER with standard tools.

Assigning tasks to myself for now.

We implemented CER/WER computation with sclite. Please help us review it at https://github.com/athena-team/athena/pull/170

This issue has been addressed with this pr and this pr. Closing this issue for now. Please reopen it if further question exists.


Stackable functions do not work for Input

This should be handled in #108
A pair of typos prevent stackable functions for working for any other function than prompt.

I would like to work on this issue.


SSL configuration is Running - Keeps running forever

App Id: d20qo1ulqdu90t
Region: us-east-2
Step: SSL configuration
Status: Running
Issue/question
I transferred my domain from GoDaddy to Route53 since then I have been trying to link my Amplify app to the domain name on route53
when setting up I select the domain name which is on route 53 and it automatically populates the ACM verification and CNAME and ANAME records on route53
After then I am still stuck at SSL configuration for almost 3 days now
I have deleted the domain and added it back to no  avail

Hi @cariloapp, apologies for the delay on this ticket. This sounds like the NS records were probably not transferred properly from GoDaddy to Route53. Because if Amplify was able to add the ACM verification record and CNAME records on your hosted zone, but they were still not resolving to the correct values, it means the domain wasn't really pointing to Route53.
I know it's been a while since you opened this ticket but I recommend you use dnschecker.org to verify whether your domain is actually resolving any record defined on Route53 even before you add the domain to Amplify. Feel free to re-open this case if you have issues again.


JRef from an AsyncAPI perspective

This is a response to #14. By request, I'm responding here so we can fork the discussion for JRef specific discussion.

Here's how I see that JRef applies to your requirements for AsyncAPI. I hope it's helpful.

Should always produce a valid JSON document (resolving referenced resource should always be compatible with JSON)

In JRef, references are always transparent. Developers are always working only with the standard JSON types. When you get a value from a JRef document, the JRef tooling follows the reference automatically and gives you the referenced value as if the referenced value was always there.
Example
const doc = JRef.load({
  "foo": { "$href": "#/bar" },
  "bar": "42"
});

const foo = JRef.get("/foo", doc); // => 42
const bar = JRef.get("/bar", doc); // => 42

Should define the behavior for referencing non-JSON resources in a JSON document (this can be as simple as resolving the content into a string value)

JRef allows implementations to define how they want non-JSON values to be represented. Everything is based on media types. You can have XML converted into a JRef compatible document, or just return it as a string. You would write a plugin for the JRef tooling describing the behavior you expect for each media type.
Example:
const doc = JRef.load({
  "schema": { "$href": "./my-xml-schema.xml" }
});

const xmlSchema = JRef.get("/schema", doc); // => Some representation of an XML document
const value = XML.get(someXPathExpression, xmlSchema); // => The value of applying the XPath expression to the XML document

Should define the behavior for referencing JSON data

The JRef proposal covers the behavior of references in JRef documents. Although JRef is syntactically compatible with JSON, it's considered a different media type and must be configured as a plugin the same way you would for XML.
Example
const doc = JRef.load({
  "foo": { "$href": "./my-json-document.json" }
});

// ./my-json-document.json
// {
//    "aaa": { "$href": "#/bbb" },
//    "bbb": 42
// }

const foo = JRef.get("/foo", doc);
const aaa = foo.aaa; // => { "$href": "#/bbb" } # A value that looks like a JRef reference, but is actually just a plain JSON object with no special meaning
const bar = foo.bbb; // => 42

Should define the behavior for referencing JSON data that also have reference behavior, and how they interconnect / or not (say two standards both use $ref the new standard should define a clear separation between the two and how referencing tools should interpret it)

Every document has a media type and each media type has it's own rules for referencing. If you reference a JSON Schema from a JRef document, once you follow that reference, then only the rules for JSON Schema apply. Because it's document based, there are some consequences to be aware of. If your AsyncAPI document identifies as a JRef media type, you can't embed a JSON Schema in that document because it's a different media type. You can only reference to a JSON Schema. That shouldn't be a big deal because it's what you already have to do for non-JSON compatible types already.
One way around that is to define AsyncAPI as a separate media type that defines that certain locations are to be interpreted as JSON Schemas. Then it can be a reference or inline. But, that would require extra work to extend the standard JRef tooling.
Another way around that is to introduce some syntax for embedding external documents in a JRef document. I've explained why an embedding/bundling feature is not included in https://github.com/json-schema-org/referencing/issues/7, but I'm open to discussion if there's demand for it.
If both AsyncAPI and JSON Schema decide to adopt JRef, this problem goes away, but I don't think that's likely from the JSON Schema side.

Should define the behavior of nested schemas within the same file (so there is no difference between what the spec allows and what tooling enables)

JRef doesn't restrict where a reference can be or what can be referenced. Because the tooling abstracts away references, there should be no developer burden and AsyncAPI document authors are empowered to use references however fits their needs. If AsyncAPI does want to make restrictions like this, they would need to define their own media type and would have to extend the standard tooling.

You can have XML converted into a JRef compatible document

Is this conversion defined by JRef, or is it implementation defined (you also mentioned a user-defined plugin)?  If the latter, how can we ensure consistency across implementations (interoperability)?

It would be an application-specific plugin. The application chooses how it wants to consume the non-JRef document content. It should be purely an application concern that doesn't effect interoperability.
However, if JRef allowed for embedded documents (bundling), interoperability could become an issue depending on how the embedding feature is defined.
Example
{
  "stuff": { "$href": "./stuff.xml" }
}

./my-schema.xml
<xml>
 <stuff/>
</xml>

If you try to embed this reference, you'd end up with something like this.
{
  "stuff": "<xml><stuff/></xml>"
}

If you did this, you'd loose the context that the value is an XML document encoded as a string and there would have to be some interoperable feature added to recognize that this was an XML document.
For example
{
  "stuff": {
    "$href": "./stuff.xml",
    "$contentType": "application/xml",
    "$content": "<xml><stuff/></xml>"
  }
}

I don't see any reason why this would be preferred over the tar solution to bundling I mentioned, so it seemed best to just not complicate things by including an embedding feature.


[Reproducers] Extend reproducer support to Swift

This extends reproducer support to Swift and adds a test case, similar
to the one we have for C.

@swift-ci please test

Extend reproducer support to Swift

Bold statement :-)
Great to see progress!
Does this work when Swift code imports Clang modules or bridging headers? Does it keep track of .swiftmodule / .swiftinterface files imported during the debug session?

Extend reproducer support to Swift

Bold statement :-)

We have to start somewhere :-)

Great to see progress!
Does this work when Swift code imports Clang modules or bridging headers? Does it keep track of .swiftmodule / .swiftinterface files imported during the debug session?

That's the next step, this just check for basic support, hence the name of the test.

Awesome!

@swift-ci please test linux

I cannot reproduce this locally, but I think I know what the issue is. I'll probably tackle this in a different PR, get it into Stable, and then try again here.

@swift-ci test linux platform

@swift-ci please test and merge


View data options and retrieve data from catalog without using the GUI

Description of PR
PLEASE READ PR DESCRIPTION FOR INSTRUCTIONS ON HOW TO REVIEW :D
This PR adds a few new functions that enable users to view the data options and retrieve data from the catalog without using the selections GUI or needing to work with the intake library. It's intended to be much easier to use than intake, with more user-friendly language that matches what we have in the selections GUI, while enabling more tech-savvy users to retrieve and subset data using a python function instead of a GUI.
I created a python notebook to showcase the functions I wrote!! Please run through this notebook in the hub to review the PR. I also hope to showcase this notebook and new functionality to the larger team at some point after getting reviews on this PR.
AE_catalog_access_and_download.ipynb.zip
Also, I improved the documentation on some existing functions that my new code utilizes :)
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
No tests written, not sure if these functions need them.
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

Ugh, I was afraid we would get a cycular import issue...
Go ahead and put them in utils...

rats! I'll change it back :(

I made some improvements as suggested by Tianchi and Eric! Everything looks good to me now. I will merge it shortly


Option to have persistent folders inside tmp

Most of PHP frameworks including Laravel require writable paths to maintain various types of caches (view cache, bootstrap cache, application cache etc). Because the only writeable path is /tmp, multiple caching systems using the same folder cause conflict possibility and eventual security risk. If /tmp could have a persistent folder cache can be separated. It could be a single folder inside /tmp for example /tmp/build
Proposed solution:
/tmp/build folder could be persistent from build to production run stage.
Impact:
Developer can create a folder on build and then symlink for example /bootstrap/cache to /tmp/build/boostrap/cache maintaining complete framework compatibility without hackcs to change pre-set bootstrap cache paths to /tmp.

@sl0wik is this for local development inside a Docker instance, or is this when deploying with Cloud Build?
I'm struggling to understand the use case for needing this to persist.
You mention bootstrap/cache with Laravel, which we struggled with when deploying to App Engine for production, so we made a php artisan gae:prepare command that pre-generates those cache files, and can be run from Cloud Build:
https://github.com/a1comms/GaeSupportLaravel/blob/php8.1-laravel9.x/src/A1comms/GaeSupportLaravel/Console/GaePrepareCommand.php#L72
https://github.com/a1comms/GaeSupportLaravel/blob/php8.1-laravel9.x/src/A1comms/GaeSupportLaravel/Foundation/ProviderRepository.php
Similarly for the view cache you mention, we made an artisan command to pre-compile all the views before deployment:
https://github.com/a1comms/GaeSupportLaravel/blob/php8.1-laravel9.x/src/A1comms/GaeSupportLaravel/Console/GaeViewCompileCommand.php
This meant that everything sits inside the storage folder and is deployed alongside the application, reducing the need for anything to end up in /tmp, except what we explicitly define as InstanceLocal cache:
https://github.com/a1comms/GaeSupportLaravel/blob/php8.1-laravel9.x/src/A1comms/GaeSupportLaravel/Cache/InstanceLocal.php
For more general application cache, storing to /tmp doesn't seem like a good fit, as in a multi-instance environment like App Engine or Cloud Run, your cache would be different on each instance, and you'd likely find they could end up serving different content, based on how fresh each cache was - so something like Redis / memcache is preferred.

@iamacarpet congrats for your package. I wish I checked it earlier.
The package vs separate Laravel-based project approach is the subject of a long discussion.
In general:

App Engine should not force users to have CI. The build process should be handled on app deploy.
Manual compiling of templates is a bit hacky and not natively supported by Laravel.
This solution would resolve only Laravel issues. Any other package could try to create something inside storage.

If we could simply have the option to create writeable folders, it would resolve majority of compatibility problems. It can be done today by symlinking but App would still need to make sure that folder exists in tmp.
Copying /tmp/build from build machine to production should be simple and would basically allow to run Laravel without CI.

Professional but more time-consuming solution would be adding to app.yaml option to set a writeable parameter that would contain a list of paths that should be writeable, for example:
writeable:
  - bootstrap/cache
  - storage

Build script could copy those directories to tmp/ and add symlinks. Normally I wouldn't trust tmp to store anything but it looks like App Engine currently using it to store files like nginx config.

I pushed changes to Laravel framework so the storage path can be overwritten using LARAVEL_STORAGE_PATH.


[Discover Page] Filter by Owner does not work

If I try to filter by owner, it will not do the filter accordingly.
For example, I tried to filter by owner in which David Tartoban was the owner, and when I did so, most of the choices that were available, Mr.Tartoban was not an explicit owner (if you click on the resource, it shows the owners.)

Addressed by #2578


bintray: automatically run brew mirror if needed

[ ] Have you followed the guidelines in our Contributing document?
[ ] Have you checked to ensure there aren't other open Pull Requests for the same change?
[ ] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[ ] Have you successfully run brew style with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

Closes: https://github.com/Homebrew/brew/issues/7708
Don't know if it is the correct implementation here. The code is basically taken from brew pull source.
Also it isn't tested yet, don't know how to bite it.

This looks good to me but I think the responsibility for calling mirror_formula should lie with e.g. brew pr-pull or similar rather than being called from bintray.rb. This will also likely address the concern in https://github.com/Homebrew/brew/pull/7709/files#r437202915 since we would always be using the most up-to-date Formula definition.

This looks good to me but I think the responsibility for calling mirror_formula should lie with e.g. brew pr-pull or similar rather than being called from bintray.rb. This will also likely address the concern in #7709 (comment) since we would always be using the most up-to-date Formula definition.

Works for me 👍

Think I made it. Just had to duplicate some logic in pr-pull.rb from bintray.rb.
I'm open for more suggestions though.

Nice work @dawidd6!


dbip-country-lite: 2024-09 -> 2024-10

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 345936 run on x86_64-linux 1

10 packages built:

clash-verge-rev
dbip-country-lite
i2p
nekoray
qv2ray
sing-geoip
v2ray
v2ray-geoip
v2raya
xray


Example from docs doesn't conform to tmlanguage.json schema

Issue Type: Bug

Go through the yeoman scaffolding process for creating a new language extension as described in https://code.visualstudio.com/api/language-extensions/syntax-highlight-guide#developing-a-new-grammar-extension.
Replace patterns and repositories fields in syntaxes/abc.tmLanguage.json with their counterparts from the second json snippet from https://code.visualstudio.com/api/language-extensions/syntax-highlight-guide#contributing-a-basic-grammar.
(This snippet appears before the snippet referenced in 1.
Notice that the letter key in the repository object is undersquiggled and I get a warning.
Delete the $schema field and the undersquiggle and warning go away.

With $schema field:

Without $schema field:

VS Code version: Code 1.35.0 (553cfb2c2205db5f15f3ee8395bbd5cf066d357d, 2019-06-04T01:16:40.241Z)
OS version: Darwin x64 18.6.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz (12 x 2200)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: enabledrasterization: enabledsurface_synchronization: enabled_onvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
1, 1, 1

Memory (System)
16.00GB (6.11GB free)

Process Argv
.

Screen Reader
no

VM
0%

Extensions (18)

Extension
Author (truncated)
Version

vscode-hie-server
ala
0.0.27

markdown-preview-github-styles
bie
0.1.6

dart-code
Dar
3.1.0

flutter
Dar
3.1.0

vscode-eslint
dba
1.9.0

prettier-vscode
esb
1.9.0

code-runner
for
0.9.10

mdmath
goe
2.3.9

gc-excelviewer
Gra
2.1.32

latex-workshop
Jam
7.0.0

language-haskell
jus
2.6.0

xml-format
mik
1.0.2

python
ms-
2019.5.18678

azure-account
ms-
0.8.4

vscode-react-native
msj
0.9.3

r-lsp
REd
0.1.0

rust
rus
0.6.1

vscode-icons
vsc
8.7.0

(2 theme extensions excluded)

This isn't actually an issue with VS code at all. Rather, it's an issue with the tmlanguage JSON schema. See https://github.com/martinring/tmlanguage/pull/2. Hopefully it'll get merged soon.


Why and how should blas be added to dependencies

Comment:
Motivated by this comment I'd like to centralize the info regarding BLAS requirements for Aesara.
In order to solve these sorts of errors, the blas package was added as a host dependency in https://github.com/conda-forge/aesara-feedstock/pull/48 (see also the links inside).
Since Aesara tries to compile with BLAS at runtime, I believe this should instead be a runtime dependency rather than a host dependency.
Unfortunately I don't currently have a very good understanding of the BLAS libraries. The Conda-Forge BLAS docs seem to be written from the perspective of a program which needs to be built using BLAS, rather than a program that relies on dynamic BLAS compilation at runtime.

I think adding it to runtime is pretty obvious then, no?

This seems to be a weird edge case: I just added blas to the runtime requirements in 2efe1d4, and now pypy3.7 on Windows fails with
configparser.NoSectionError: No section: 'blas'

2022-07-03T12:55:12.1607314Z TEST START: D:\bld\win-64\aesara-2.7.4-py37he04ca5b_1.tar.bz2
2022-07-03T12:55:12.2311102Z Multiple meta files found. The meta.yaml file in the base directory (C:\Users\VSSADM~1\AppData\Local\Temp\tmpxgrr8_ot\info\recipe) will be used.
2022-07-03T12:55:12.2313000Z WARNING:conda_build.utils:Multiple meta files found.   If you are using conda, update the numpy
2022-07-03T12:57:46.4797148Z packages to the latest build otherwise, set MKL_THREADING_LAYER=GNU in
2022-07-03T12:57:46.4797877Z your environment for MKL 2018.
2022-07-03T12:57:46.4798227Z
2022-07-03T12:57:46.4798744Z If you have MKL 2017 install and are not in a conda environment you
2022-07-03T12:57:46.4799465Z can set the Aesara flag blas__check_openmp to False.  Be warned that if
2022-07-03T12:57:46.4800126Z you set this flag and don't set the appropriate environment or make
2022-07-03T12:57:46.4800826Z sure you have the right version you *will* get wrong results.
2022-07-03T12:57:46.4802019Z
2022-07-03T12:57:46.4935588Z
2022-07-03T12:57:46.4938214Z (%PREFIX%) %SRC_DIR%>IF 1 NEQ 0 exit /B 1
2022-07-03T12:57:48.0278925Z Tests failed for aesara-2.7.4-py37he04ca5b_1.tar.bz2 - moving package to D:\bld\broken
2022-07-03T12:57:48.0288346Z WARNING:conda_build.build:Tests failed for aesara-2.7.4-py37he04ca5b_1.tar.bz2 - moving package to D:\bld\broken
2022-07-03T12:57:48.1048451Z TESTS FAILED: aesara-2.7.4-py37he04ca5b_1.tar.bz2
2022-07-03T12:58:01.7718531Z ##[error]Cmd.exe exited with code '1'.

On the base or main package?

@twiecki, on main. Thanks for catching that, I updated my comment above.

That exact error is due to a failure in import mkl, and I believe that the importable mkl package is provided by mkl-service.

Looking at the codebase, it doesn't seem like we use the mkl-service package for anything other than two mkl.get_version_string() calls.  If there's another way to get the version string, or skip the checks that use those calls altogether, then we should definitely get rid of this implicit mkl-service requirement.

I think the blas in run makes sense, given the package isn't itself built with -lblas flags. However, the specifying of a specific BLAS implementation (openblas, mkl-service) is questionable. In particular, OpenBLAS was the worst of all possible choices for Apple Silicon in some NumPy testing. Generally, Conda Forge wants to leave choice of BLAS/LAPACK implementation up to the end-user, not the package maintainer, i.e., blas should be sufficient.

Thanks so much @mfansler for the feedback!!!
If we were to remove openblas and mkl-service, do you understand how a default BLAS implementation would be chosen?
Also, from the knowledge base and the BLAS feedstock it seems like the blas package is deprecated. Perhaps we should be using libblas instead?

Just opened #135 to test

If we were to remove openblas and mkl-service, do you understand how a default BLAS implementation would be chosen?

In my experience it defaults to mkl on win-64 and openblas otherwise. I'm unclear on whether this is configured somewhere in the channel, is an artifact of build order in the libblas recipe, or something even more arbitrary, like what implementation build was last built.
At least in Conda Forge, the pinnings dictate that libblas in a host requirement will always install the netlib version (a reference interface). Packages can safely link against this generically and the other implementations will have a consistent ABI.

Also, from the knowledge base and the BLAS feedstock it seems like the blas package is deprecated. Perhaps we should be using libblas instead?

I believe you are correct that libblas is the more correct specification. blas is a metapackage provided for end-users to control the implementation. For example, from the linked SO post, it shows how it works:
## Note that `conda-forge` channel is prioritized on my system

# MKL
mamba create -n np_mkl python=3.9 numpy 'blas=*=mkl'

# BLIS
mamba create -n np_blis python=3.9 numpy 'blas=*=blis'

# OpenBLAS
mamba create -n np_openblas python=3.9 numpy 'blas=*=openblas'

# Accelerate
mamba create -n np_accelerate python=3.9 numpy 'blas=*=accelerate'

# Netlib
mamba create -n np_netlib python=3.9 numpy 'blas=*=netlib'

However, I'm beginning to grok a bit more the motivating problems involved here. The workaround of including blas was about needing to find include/cblas.h. I did a few checks on include/cblas.h in the different implementations and see that openblas provides it, but blis puts it in include/blis/cblas.h and accelerate doesn't even package one (though maybe you could pick it up from the system SDK?).
Further, mkl-service alone installs mkl, but does not include include/mkl_cblas.h (its version of this) which is instead provided by mkl-include.
A bit of a mess. It seems like

We should maybe do some unification to ensure that all the BLAS implementations of libblas ensure that some form of cblas.h is provided.
Work out some robust way for aesera to find this (e.g., via pkg-config?).

@mfansler, many thanks for these insights!

Oh! - I just noticed that mkl-service + blas specification on osx-64 installs MKL, but still resolves to blas=*=openblas, i.e., it installs OpenBLAS which is what ends up providing an include/cblas.h.

I created an Issue in the blas feedstock. Please amend it if my explanation there is not correctly characterizing the needs here. My understanding is that this package requires an include/cblas.h and Conda Forge's BLAS implementations lack a consistent way to express this precisely, which is the source of confusion.
https://github.com/conda-forge/blas-feedstock/issues/111

I created an Issue in the blas feedstock. Please amend it if my explanation there is not correctly characterizing the needs here. My understanding is that this package requires an include/cblas.h and Conda Forge's BLAS implementations lack a consistent way to express this precisely, which is the source of confusion.
conda-forge/blas-feedstock#111

That sounds correct, and thanks again!

Last note for the night is that Netlib delivers this with the Netlib implementation of libcblas. Since Netlib is the reference for BLAS, that suggests to me that really libcblas, not libblas, would be the proper dependency, or perhaps even that we need to create a new output package like libcblas-devel as a dependency that would be dedicated to packing the associated header files.

What's going on between the blas package's headers and https://github.com/aesara-devs/aesara/blob/main/aesara/tensor/blas_headers.py?

What's going on between the blas package's headers and https://github.com/aesara-devs/aesara/blob/main/aesara/tensor/blas_headers.py?

If I recall correctly, some code uses the custom headers created there and some other code uses the externally provided headers.


Faraday exception rescue does not work with older versions of Faraday

The gemspec gives a version range for Faraday here: https://github.com/getsentry/raven-ruby/blob/master/sentry-raven.gemspec#L19
However, Faraday < 0.9.0 has Faraday::Error::ClientError and this was moved to Faraday::ClientError only in that version and higher.  My application current pins at Faraday v0.8.11 and Sentry request failures blow up with
Uninitialized constant Faraday::ClientError`.

Hm. What's pinning your bundle at 0.8?

Well, since both versions inherit from Faraday::Error this is a simple fix.


Fix flaky TestChildWorkflowExecution

Coverage increased (+0.02%) to 66.257% when pulling a71192408a639146edc13656ffe44496791b5ad7 on fixtest into 35a3d1da6be4fe02471794faa9e02a41859f92b2 on master.

Looks good, I would rename the PR to say "Add more logs to debug flaky test" since this code change is not actually to fix it.

Coverage increased (+0.03%) to 66.275% when pulling 981e94f43ffeec70ac312548e18c666a796f7d0a on fixtest into 35a3d1da6be4fe02471794faa9e02a41859f92b2 on master.


Council motions for approving treasury proposals

Closes #680

[x] Repot Permill and add constructors
[x] Integrate treasury into demo runtime
[x] Introduce EnsureOrigin trait for allowing parameterised origin-guards
[x] Introduce system implementations of EnsureOrigin
[x] Introduce council Members origin and an according implementation of EnsureOrigin
[x] Introduce parameterisable origin guard for treasury
[x] Introduce council_motions module that can dispatch from council origin
[x] Integrate council_motions into demo runtime.
[x] Tests.

@pepyakin ^^^

@pepyakin ^^^

@bkchr ^^^


chore(all): fix deps that were bumped past 1.11

Noticed this when looking at #2394

Test failure is unrelated to this change. Merging this so that more PRs get unblocked.


Please invite me to the GitHub Community Organization

Name
vishal krishna
Discord Username (if applicable)
No response
Additional Context
Hello Everyone, I am Vishal Krishna, a frontend developer from India. I have 2 years of experience in the software domain working for product based company. I would love to connect and grow with Jaidevstudio community

It's great having you contribute to this project
If you would like to continue contributing to open source and would like to do it with an awesome inclusive community, you should join our Discord Server and our GitHub Organisation - we help and encourage each other to contribute to open source little and often 🤓 . Any questions let us know.

Invitation sent for the GitHub Organisation. Welcome to the community 🎉#
Don't forget after accepting to make it public so it appears on your GitHub profile for everyone else to see, you can do this by finding your name in the GitHub organisation list and change the dropdown to public https://github.com/orgs/jaidevstudio/people
Like this

Tips for practising:
Remember contributing to open source is not just about code, its about collaboration, communication and adding value
I hope that helps

Please check your email or organisation page 🙏


(WIP) Color Scales

This addresses #384 and changes how color scales work. The new features are:

The user can pass n colors, rather than just 2 or 3

The linear color schemes are better. We used to interpolate between the extreme colors (min/max or min/mid/max), now we use all the scheme's colors.
As an illustration, here are some colorbrewer schemes, before and after:

'Reds'

'Blues'

'RdYlGn'

As an added bonus we have the new matplotlib color schemes

Viridis

Magma

Inferno

Plasma

Some points up for discussion @SylvainCorlay @dmadeka @ssunkara1 :

This is still a WIP because I haven't implemented the mid attribute
more than just a mid, we can now pass as many values as there are colors, so we could think of how to handle that.
we don't need the divergent attribute anymore

💯 🥇 👍

The mid attribute now works as before, this is ready to be looked at, please test

@rmenegaux This looks awesome!! Testing it out

Reviewed in person with @rmenegaux merging WOOOOT!