Dated walkthrough

This walkthrough was last updated in 2017 and it's a bit outdated. While the steps are still valid, there's now a new unified Azure Management SDK (Microsoft.Azure.Management.Fluent) which makes things simplier and cleaner.
// service principal credentials
var credentials = SdkContext.AzureCredentialsFactory.FromServicePrincipal(appId, appSecret, tenantId, AzureEnvironment.AzureGlobalCloud);

// create Azure management client
var azure = Azure
                .Configure()
                .Authenticate(credentials)
                .WithDefaultSubscription();

// purge endpoint
azure.CdnProfiles.PurgeEndpointContent(resourceGroupName, profileName, endpointName, new List<string>() { "/*" });

And also: the CDN management library used in this walkthrough (Microsoft.Azure.Management.Cdn) puts resourceGroupName as the first parameter, therefore the samples in this article don't work.

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

ID: cda67fd8-ca0e-5eb1-f58c-cafebbdd855f
Version Independent ID: 21582c44-4cc0-9f6b-6042-8afc98b99c08
Content: Get started with the Azure CDN Library for .NET
Content Source: articles/cdn/cdn-app-dev-net.md
Service: cdn
GitHub Login: @zhangmanling
Microsoft Alias: mazha

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

@msimecek Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

Assigning to PM for review
#reassign:@sohamnchatterjee

Assigning to PM for review
#reassign:@amitsriva

#reassign: jessie-jyy

Thank you for you dedication to our documentation.
Unfortunately, we have been unable to review this issue in a timely manner. We sincerely apologize for the delayed response. We will create an internal tracking work item to address this issue. For now, we are closing this issue. If you have any additional information you would like to provide, please respond to this issue with any additional details.
Please continue to provide feedback about the documentation. We appreciate your contributions to our community.
#please-close


Migrate to Swift 2.0

Another option to close issue #37.
I pulled master and ran through the Swift 2.0 migration using the Xcode 7 GM release. In this branch you should still see a full suite of passing tests, 0 warnings when build with the GM, and a version bump to 3.0.0 to account for the backwards incompatible change to Swift 2.0.
I'd like to exercise this more completely but I still have some other 2.0 migration issues to fix before I can see it in action in my current app. All I can be completely confident of at the moment is that installation (via pod 'SwiftValidator', git: 'https://github.com/goodeggs/SwiftValidator.git', branch: 'swift-2.0') gives my app a Pods sub project which builds cleanly.

great work @jonah-williams! Would you be interested in helping as a contributor of this project?

Does the specs repo need to be updated for the pod?
[!] Unable to satisfy the following requirements:

SwiftValidator (~> 3.0.0) required by Podfile

@jpotts18 happy to help if I can, let's talk about what you expect from contributors?

@jpotts18
I'm getting the same error as @byronsorrells using the line:
    pod 'SwiftValidator',       '~> 3.0.0'

Are we updating this incorrectly?

@byronsorrells
Until we can figure out why it's not working normally in Pods, here's my solution. Just target the commit itself:
pod 'SwiftValidator',       :git => 'https://github.com/jpotts18/SwiftValidator.git', :commit => 'd801538'

so is this the file that we cocoapod from for swift 2.0?

@AdventureOfMar That's what worked for me, yes. I'm not sure why downloading the master branch in CocoaPods didn't work, so this is what I'm using for now. That line downloads the specific commit where they merged the Swift 2.0 branch in.

Hey guys 3.0.0 is not pushed to the cocoapods repo. Sorry for the delay!

Thanks so much guys!


WT500 mags don't fit in the WT500

Try to put a mag in the WT500. It won't fit even thought it's custom made for the gun.

on the topic of guns https://github.com/space-wizards/space-station-14/pull/1033#issuecomment-660405916


Terminal: font characters are shifted down when cursor is on top of them

/duplicate https://github.com/microsoft/vscode/issues/84432


Adding a toml to help get rid of the setup.py deprecation notice

Eliminates this:
DEPRECATION: gpt3-prompt-to-text is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559

Thank you for the contribnution. I just learned how to do this with flit_scm in another project and only came back to this project just now :)


Assign proper (2D) lat-lon coords with getvar

The variables don't have the unmasked 2D lat-lon coordinates so after we load a variable
var = cosima_cookbook.querying.getvar(experiment, variable, session, frequency='1 monthly', n=-1)

we need to do something like
geolon_t = cosima_cookbook.querying.getvar(experiment, 'geolon_t', session, n=-1)
geolat_t = cosima_cookbook.querying.getvar(experiment, 'geolat_t', session, n=-1)

var = var.assign_coords({'geolon_t': geolon_t, 'geolat_t': geolat_t})

to be able to plot properly; see https://cosima-recipes.readthedocs.io/en/latest/Tutorials/Making_Maps_with_Cartopy.html#Fixing-the-tripole
Why don't we modify the cosima_cookbook.querying.getvar method to load and assign the coords before returning back the dataarray/dataset?

This is similar to https://github.com/ACCESS-NRI/access-nri-intake-catalog/issues/112 for the intake catalog.


python3Packages.ehtim: init at 1.2.4

Add the python package ehtim to nixpkgs. It is widely used in the Event Horizon Telescope community.

Description of changes
Add the python package ehtim to nixpkgs. It is widely used in the Event Horizon Telescope community.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Is there any more I can do here?


[SPARK-47712][CONNECT] Allow connect plugins to create and process Datasets

What changes were proposed in this pull request?

This PR adds new versions of SparkSession.createDataset and SparkSession.createDataFrame that take an Array[Byte] as input. The older versions that take a protobuf.Any are deprecated. This PR also adds new versions of SparkConnectPlanner.transformRelation and SparkConnectPlanner.transformExpression that take an Array[Byte].
Why are the changes needed?

Without these changes it's difficult to create plugins for Spark Connect. The methods above used to take a protobuf class that is shaded as input, meaning that that plugins had to shade these classes in the exact same way. Now they can just serialize the protobuf object to bytes and pass that in instead.
Does this PR introduce any user-facing change?

No
How was this patch tested?

Tests were added
Was this patch authored or co-authored using generative AI tooling?

No

cc @grundprinzip

Merged to master.


Crash

After recently upgrading node.js, coc.nvim and rust-analyzer, rust-analyzer mostly just stopped working for me. I wasn't sure at first if this is a rust-analyzer issue or the CoC integration but after some troubleshooting, it turns out that rust-analyzer was crashing for me:
thread '<unnamed>' panicked at 'Internal error, cycle detected:

DatabaseKeyIndex { group_index: 7, query_index: 11, key_index: 680 }
DatabaseKeyIndex { group_index: 7, query_index: 9, key_index: 62 }
', /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/salsa-0.16.0/src/lib.rs:490:48
stack backtrace:
   0: rust_begin_unwind
             at /rustc/e1884a8e3c3e813aada8254edfa120e85bf5ffca/library/std/src/panicking.rs:495:5
   1: std::panicking::begin_panic_fmt
             at /rustc/e1884a8e3c3e813aada8254edfa120e85bf5ffca/library/std/src/panicking.rs:437:5
   2: salsa::QueryTable<Q>::get::{{closure}}
   3: <DB as hir_ty::db::HirDatabase>::generic_defaults::__shim
   4: <DB as hir_ty::db::HirDatabase>::generic_defaults
   5: hir_ty::lower::substs_from_path_segment
   6: hir_ty::lower::<impl hir_ty::TraitRef>::from_resolved_path
   7: hir_ty::lower::<impl hir_ty::TraitRef>::from_path
   8: hir_ty::lower::<impl hir_ty::GenericPredicate>::from_type_bound
   9: hir_ty::lower::<impl hir_ty::GenericPredicate>::from_where_predicate
  10: <core::iter::adapters::flatten::FlatMap<I,U,F> as core::iter::traits::iterator::Iterator>::next
  11: <alloc::vec::Vec<T> as alloc::vec::SpecFromIter<T,I>>::from_iter
  12: <hir_ty::db::GenericPredicatesForParamQuery as salsa::plumbing::QueryFunction>::execute
  13: salsa::runtime::Runtime::execute_query_implementation
  14: salsa::derived::slot::Slot<Q,MP>::read_upgrade
  15: salsa::derived::slot::Slot<Q,MP>::read
  16: <salsa::derived::DerivedStorage<Q,MP> as salsa::plumbing::QueryStorageOps<Q>>::try_fetch
  17: <DB as hir_ty::db::HirDatabase>::generic_predicates_for_param::__shim
  18: <DB as hir_ty::db::HirDatabase>::generic_predicates_for_param
  19: hir_ty::utils::all_super_trait_refs
  20: hir_ty::utils::associated_type_by_name_including_super_traits
  21: hir_ty::lower::<impl hir_ty::Ty>::from_partly_resolved_hir_path
  22: hir_ty::lower::<impl hir_ty::Ty>::from_hir_ext
  23: core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &mut F>::call_once
  24: <alloc::vec::Vec<T> as alloc::vec::SpecFromIter<T,I>>::from_iter
  25: <hir_ty::db::GenericDefaultsQuery as salsa::plumbing::QueryFunction>::execute
  26: salsa::runtime::Runtime::execute_query_implementation
  27: salsa::derived::slot::Slot<Q,MP>::read_upgrade
  28: salsa::derived::slot::Slot<Q,MP>::read
  29: <salsa::derived::DerivedStorage<Q,MP> as salsa::plumbing::QueryStorageOps<Q>>::try_fetch
  30: <DB as hir_ty::db::HirDatabase>::generic_defaults::__shim
  31: <DB as hir_ty::db::HirDatabase>::generic_defaults
  32: hir_ty::lower::substs_from_path_segment
  33: hir_ty::lower::<impl hir_ty::TraitRef>::from_resolved_path
  34: hir_ty::lower::<impl hir_ty::TraitRef>::from_path
  35: <hir_ty::db::ImplTraitQuery as salsa::plumbing::QueryFunction>::execute
  36: salsa::runtime::Runtime::execute_query_implementation
  37: salsa::derived::slot::Slot<Q,MP>::read_upgrade
  38: salsa::derived::slot::Slot<Q,MP>::read
  39: <salsa::derived::DerivedStorage<Q,MP> as salsa::plumbing::QueryStorageOps<Q>>::try_fetch
  40: <DB as hir_ty::db::HirDatabase>::impl_trait::__shim
  41: <DB as hir_ty::db::HirDatabase>::impl_trait
  42: hir_ty::method_resolution::TraitImpls::trait_impls_in_crate_query
  43: salsa::runtime::Runtime::execute_query_implementation
  44: salsa::derived::slot::Slot<Q,MP>::read_upgrade
  45: salsa::derived::slot::Slot<Q,MP>::read
  46: <salsa::derived::DerivedStorage<Q,MP> as salsa::plumbing::QueryStorageOps<Q>>::try_fetch
  47: <DB as hir_ty::db::HirDatabase>::trait_impls_in_crate::__shim
  48: hir_ty::method_resolution::TraitImpls::trait_impls_in_deps_query
  49: salsa::runtime::Runtime::execute_query_implementation
  50: salsa::derived::slot::Slot<Q,MP>::read_upgrade
  51: salsa::derived::slot::Slot<Q,MP>::read
  52: <salsa::derived::DerivedStorage<Q,MP> as salsa::plumbing::QueryStorageOps<Q>>::try_fetch
  53: <DB as hir_ty::db::HirDatabase>::trait_impls_in_deps::__shim
  54: hir_ty::traits::chalk::<impl chalk_solve::RustIrDatabase<hir_ty::traits::chalk::interner::Interner> for hir_ty::traits::ChalkContext>::impls_for_trait
  55: chalk_solve::clauses::program_clauses_for_goal
  56: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  57: <chalk_recursive::recursive::RecursiveSolver<I> as chalk_solve::solve::Solver<I>>::solve_limited
  58: hir_ty::traits::solve::{{closure}}
  59: hir_ty::traits::trait_solve_query
  60: salsa::runtime::Runtime::execute_query_implementation
  61: salsa::derived::slot::Slot<Q,MP>::read_upgrade
  62: salsa::derived::slot::Slot<Q,MP>::read
  63: <salsa::derived::DerivedStorage<Q,MP> as salsa::plumbing::QueryStorageOps<Q>>::try_fetch
  64: salsa::QueryTable<Q>::get
  65: <DB as hir_ty::db::HirDatabase>::trait_solve::__shim
  66: <DB as hir_ty::db::HirDatabase>::trait_solve
  67: hir_ty::autoderef::deref
  68: <core::iter::sources::Successors<T,F> as core::iter::traits::iterator::Iterator>::next
  69: core::iter::traits::iterator::Iterator::find_map
  70: hir_ty::infer::expr::<impl hir_ty::infer::InferenceContext>::infer_expr_inner
  71: hir_ty::infer::expr::<impl hir_ty::infer::InferenceContext>::infer_expr_coerce
  72: hir_ty::infer::expr::<impl hir_ty::infer::InferenceContext>::infer_block
  73: hir_ty::infer::expr::<impl hir_ty::infer::InferenceContext>::infer_expr_inner
  74: hir_ty::infer::expr::<impl hir_ty::infer::InferenceContext>::infer_expr_coerce
  75: hir_ty::infer::infer_query
  76: salsa::runtime::Runtime::execute_query_implementation
  77: salsa::derived::slot::Slot<Q,MP>::read_upgrade
  78: salsa::derived::slot::Slot<Q,MP>::read
  79: <salsa::derived::DerivedStorage<Q,MP> as salsa::plumbing::QueryStorageOps<Q>>::try_fetch
  80: <DB as hir_ty::db::HirDatabase>::infer_query::__shim
  81: hir_ty::db::infer_wait
  82: hir_ty::diagnostics::validate_body
  83: hir::code_model::Function::diagnostics
  84: hir::code_model::Module::diagnostics
  85: ide::diagnostics::diagnostics
  86: ide::Analysis::diagnostics
  87: rust_analyzer::handlers::publish_diagnostics
  88: core::ops::function::impls::<impl core::ops::function::FnMut<A> for &mut F>::call_mut
  89: <alloc::vec::Vec<T> as alloc::vec::SpecFromIter<T,I>>::from_iter
  90: <F as threadpool::FnBox>::call_box
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
[Trace - 4:45:04 PM] Received response 'textDocument/semanticTokens/full - (1)' in 3631ms. Request failed: content modified (-32801).
[Trace - 4:45:32 PM] Sending request 'textDocument/documentHighlight - (2)'.
Params: {
    "textDocument": {
        "uri": "file:///home/zeenix/checkout/smol-rs/async-broadcast/src/lib.rs"
    },
    "position": {
        "line": 156,
        "character": 4
    }
}

https://github.com/smol-rs/async-broadcast is the repo I can easily reproduce this with but I think it's crashing on my machine for all projects. :(

This looks like an old crash. Can you check which RA version you're running?

yeah this doesn't include https://github.com/salsa-rs/salsa/pull/260, so it must be an old r-a version

yeah this doesn't include salsa-rs/salsa#260, so it must be an old r-a version

Right. Turns out I had some old data files in the  ~/.config/coc/extensions/coc-rust-analyzer-data file and somehow that was the source of the problem. I uninstalled coc-rust-analyzer extension, removed that directory and installed coc-rust-analyzer again and now everything works again.
Sorry for the noise.


Railway [Metro] IT/OT System Cyber Security Test Platform

@timyardley do I do anything wrong with the pull requests? Some of my pull requests are pending since May. Or maybe you just haven't had change to see them.

@anton-shipulin No, I think I just approved them but didn't merge. My apologies.


arcadia.linear/v4- does not take one argument

Neither does v2-, but v3- does. We need a consistent policy.

Actually it did work, but identically to v3-; so really we needed a less consistent policy. Closed by 0796e4641802b1f80d8e06bc16a488298d3def1f.


Make proper profile page

Is your feature request related to a problem? Please describe.
Currently the profile page is static and doesn't pull data from the database...
Describe the solution you'd like
I will make sure that the profile page is connected to the backend and the database...
Flow of work:
The profile page will make call to the route to fetch the user data stored in the database...
The backend will contain the logic for the GET req to fetch the data...
Database will send the data using the backend and the frontend will show the data after fetching the data from the backend using the JS.
Additional context

Make sure to add the labels :)
Personally its a level3 sol. so hope it will be marked as such

please assign this to me i want to work on this.


stylua: 0.15.2 -> 0.15.3

Diff: https://github.com/johnnymorganz/stylua/compare/v0.15.2...v0.15.3
Changelog: https://github.com/johnnymorganz/stylua/blob/v0.15.3/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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

[x] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

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

1 package built:

stylua

Thank you!


We couldn't connect to 'https://huggingface.co'

Hey guys. I'm trying to run the training script , and it gives me the following error.
OSError: We couldn't connect to 'https://huggingface.co' to load this model, couldn't find it in the cached files and it looks like runwayml/stable-diffusion-v1-5/ is not the path to a directory containing a scheduler_config.json file.
Checkout your internet connection or see how to run the library in offline mode at 'https://huggingface.co/docs/diffusers/installation#offline-mode'.

Anyone have an idea what I'm doing wrong?

maybe you can firstly download the model into local path

Hey @xiaohu2015 . Is the v1-5-pruned.ckpt ok ?I've just downloaded it

from diffusers import StableDiffusionPipeline
import torch

model_id = "runwayml/stable-diffusion-v1-5"
pipe = StableDiffusionPipeline.from_pretrained(model_id, torch_dtype=torch.float16)
pipe.save_pretrained("local_path")

Hey guys. I'm trying to run the training script , and it gives me the following error.

OSError: We couldn't connect to 'https://huggingface.co' to load this model, couldn't find it in the cached files and it looks like runwayml/stable-diffusion-v1-5/ is not the path to a directory containing a scheduler_config.json file.

Checkout your internet connection or see how to run the library in offline mode at 'https://huggingface.co/docs/diffusers/installation#offline-mode'.

Anyone have an idea what I'm doing wrong?

What's the training for?

@rafstahelin please see here


Add support for webpack 5

Currently getting this warning from yarn:
warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^3.0.0 || ^4.0.0".

PR welcome


Open the Wiki as a tab in your browser instead of the origin browser

Think it could be so much more useful if the wiki is opening in your actual browser when you click the tab (like discord does) instead of opening it in our origin browser

Not really a Northstar issue, there seems to be a problem with how your OS/Origin configuration handles links

No it's not, the discord link is opening in the normal browser as a new tab, it's only the wiki that opens in the origin browser
Also this is a suggestion to get added....

Weird, on Linux all links including the wiki one open through the default browser

Actually @biast12 is right, we added logic to always open Discord links in browser instead of Origin overlay one and we could probably do the same for wiki by adding some logic here.
It's more of a design decision than a technical one whether we want to change that ^^

Yep! i had a look myself (i was planning on making a pull request), tho i couldn't find where the wiki was being opened so i thought making a suggestion would be better instead (to leave it to someone who knows where it is)


Feature Request - add metadata for custom Enterprise-Scale Policy/Set definitions

Add metadata 'EnterpriseScale' or something like that for custom Enterprise-Scale Policy/Set definitions.
Having that identifier may be helpful consolidating custom Policy/Set definitions.
e.g.
            "metadata": {
              "version": "1.0.0",
              "category": "Monitoring",
              "EnterpriseScale": true
            }

https://docs.microsoft.com/en-us/azure/governance/policy/concepts/definition-structure#metadata

Thanks for submitting this issue. Can you please elaborate on 'helpful consolidating custom policy/set definitions'?

some use cases that I have in mind:

assessing the environment for policy/set definitions determine which belong to ESLZ
cleanup of unused policy/set definitions (one may want to keep the unused ESLZ definitions but decommission other custom definitions). Today the mapping of policy/set definitions to ESLZ can only be done by the policy/set's displayName (I think)
inventory based on metadata

Thanks for the suggestion @JulianHayward. 👍  Is it not sufficient to select Custom in the Azure Portal Dropdown menu?

ESLZ custom policies should probably not be treated differently than any other custom policies defined inside the tenant.
Do you agree?
Can you please elaborate how the tags improve the user experience?
Are you querying and filtering defined policies in the tenant using Tags and Azure CLI or PowerShell?

The ESLZ policies are transitioning to built-ins, and for now, you can filter on custom as Marvin said, and also by category as we use the same categories as built-ins. We do not intend to surface as unique policies in ESLZ context by populating the metadata object.


The route is not specified

    Route::get('/{any}', 'LaravueController@index')->where('any', '.*');
Why use {any}?
Is that means no matter what the route is, the background page is displayed?

@nookery i think its alternative for Route::fallback


Ability to Supply an old iTunes Library.xml

Requested Feature
Recently found myself In a position where I had all the metadata to my entire library but none of the music files. Ended up writing a node script to fuzzy find as many of the songs as possible and put them into a Spotify playlist.
https://github.com/johnnyshankman/itunes-library-xml-to-spotify-migrator
It would be so much better to use your tool as Youtube is way more likely to find random songs that were not traditional releases (such as DatPiff Mixtapes, and SoundCloud Remixes). It would be great if there were some way to ingest a library.xml file.
Possible implementation
You can use my library as a starting point 100%.
Also https://github.com/shawnbot/itunes-data

that's a very niche use case. I don't think implementing this into spotDL would benefit bigger % of the userbase.


Issue with columns that have Precision specified on SSDL metadata

I am using Effort Framework to unit test with a Sybase ASE databse. I am able to access the database with the entity model in both my main project and unit test project, however when try to use Effort to create an in memory database, I get an exception.
Problem Code in Unit Test project
public SetUpShims()
{
     string connString = System.Configuration.ConfigurationManager.ConnectionStrings["CoPathDataContext"].ConnectionString;
     MyDbContext context;
     // CreateTransient throws exception
     EntityConnection conn = Effort.EntityConnectionFactory.CreateTransient(connString);

     context = new Data.CoPathDataContext(conn);

}

Exception Details: (System.Data.MetadataException)
Schema specified is not valid.

Stack Trace
at System.Data.Metadata.Edm.StoreItemCollection.Loader.ThrowOnNonWarningErrors()
at System.Data.Metadata.Edm.StoreItemCollection.Loader.LoadItems(IEnumerable`1 xmlReaders, IEnumerable`1 sourceFilePaths)
at System.Data.Metadata.Edm.StoreItemCollection.Loader..ctor(IEnumerable`1 xmlReaders, IEnumerable`1 sourceFilePaths, Boolean throwOnError)
at System.Data.Metadata.Edm.StoreItemCollection.Init(IEnumerable`1 xmlReaders, IEnumerable`1 filePaths, Boolean throwOnError, DbProviderManifest& providerManifest, DbProviderFactory& providerFactory, String& providerManifestToken, Memoizer`2& cachedCTypeFunction)
at System.Data.Metadata.Edm.StoreItemCollection..ctor(IEnumerable`1 xmlReaders)
at Effort.Internal.Common.MetadataWorkspaceHelper.CreateMetadataWorkspace(List`1 csdl, List`1 ssdl, List`1 msl)
at Effort.Internal.Common.MetadataWorkspaceHelper.Rewrite(String metadata, String providerInvariantName, String providerManifestToken)
at Effort.EntityConnectionFactory.<GetEffortCompatibleMetadataWorkspace>b__1(String metadata)
at Effort.Internal.Caching.MetadataWorkspaceStore.<>c__DisplayClass1.<GetMetadataWorkspace>b__0()
at System.Lazy`1.CreateValue()
at System.Lazy`1.LazyInitValue()
at System.Lazy`1.get_Value()
at Effort.Internal.Caching.ConcurrentCache`2.Get(TKey key, Func`1 factory)
at Effort.Internal.Caching.MetadataWorkspaceStore.GetMetadataWorkspace(String metadata, Func 2 workspaceFactoryMethod)
at Effort.EntityConnectionFactory.GetEffortCompatibleMetadataWorkspace(String& entityConnectionString)
at Effort.EntityConnectionFactory.CreateTransient(String entityConnectionString, IDataLoader dataLoader)
at Effort.EntityConnectionFactory.CreateTransient(String entityConnectionString)

After looking at the .csdl and .ssdl files that Entity made, I believe I found the fields causing the problem.
SSDL
<Property Name="sequence_num" Type="float" Precision="24" Nullable="false" />

CSDL
<Property Name="sequence_num" Type="Double" Nullable="false" />

I tried removing the Precision attribute from the SSDL fields, but I still received the same error.
Anyone thoughts on what is causing the exception and how I should resolve it?
Effort Framework Version 1.1.0
NMemory Version: 1.0.0

Hello @elliot-j ,
Is it possible for you to create a sample project with this issue?
We are currently making an issue cleanup and make sure we focus on issues people still require since it will be impossible to make them all (It's a free library!). Since that's has been a long time that this issue has been answered, it might also be already fixed.
Best Regards,
Jonathan

Hi @JonathanMagnan  here is a sample project that reproduces the issue on v.1.37 of Effort Framework. I also saw that I omitted that what version of EntityFramework i'm using in my original post. Due to driver limitations of the source database, the project is using EntityFramework v5.0.0
WebApplication2.zip

Thank a lot @elliot-j  for the solution,
We will look at it next week,
Best Regards,
Jonathan

@JonathanMagnan Would giving you the installer for the DB drivers work ? The DB drivers that get referenced in the project depend on a bunch of other DLL's, and teasing out which one's would need to be included will take some digging.

Anything will do the job as long as we are able to run it ;)

The database drivers can be found at https://drive.google.com/open?id=1c_wZgcG9jeG-VzBjzoun5cMVgT_1861v . I've include a quick README for installing the drivers. Note that you will need either VS 2013 or 2015 (any patch level) in order to register the provider in Visual Studio

Thank @elliot-j ,
I will have my developer try it again probably tomorrow.
Best Regards,
Jonathan


Adding repo metric GitHub action

Adding GitHub Action to record repository metrics to Firebase

@marinaserranomontes Just pinging for a PR review


How to Remove The MDBottomAppBar White Background

Reproduce: Run the MDBottomAppBar example from the docs
The widget has a white background, even seen on the example behind the FAB. Is there a way to remove that white background? I tried checking the docs AND the implementation but seems like the MDBottomAppBar simply inherits from a FloatLayout with no canvas instructions(I checked all canvas instructions associated with the widget and zilch).
Is there ANY way of doing this? even if its a hack because I have a ScrollView behind that Bar and that white background simply messes up my design hopes

@qodzero Do you mean this?

Yes, that

@HeaTTheatR or atleast in my case, change the color of that white background

@qodzero It cannot be removed as this white circle is for technical purposes.

Hmm..ok then, @HeaTTheatR , is it atleast possible to make it smaller, I think maybe its a bug but sometimes, the white back appears quite big, as demonstrated in the image below:

it looks like the end of the scroll view
so that means that the shadow should be dissmissed or cut in two where the floating button starts and ends

Fix https://github.com/kivymd/KivyMD/pull/798


[Feature Request] Add callback at the end of discovery process and just after user select desired device.

The function registered with registerInitialiseFunction is called too late and in some situations it is necessary to perform an action (example loading data for configuration) when the user selects the device after the discovery process.
.registerAfterDiscoveryFunction(controller.afterDiscovery)
// Example code in the controller:
module.exports.initialise = function() {
debug('call api and load some data from home automation device');
// dynamically add switches or buttons
};
Regards

Hi @Krikroff77
Thats possible but I think that would make the SDK too complicated. You could for example do a lazy initialisation of your controller, the first time a device is used in a controller you can load the needed data.
Did you take a look for example what the LIFX example does: https://github.com/NEEOInc/neeo-sdk-examples/blob/master/lib/device/lifx-local/lifxcontroller.js?

Hi @neophob thanks you for your quick reply ;)
I'm already using lazy initialisation but that does not exactly answer the need.
The goal is to build dynamically the buttons or switches the first time so i can use them in recipes.
I think the only solution today and not to use a discovery service unfortunately. It is therefore necessary to prepare in a configuration file, load the data and only then create the device. The limit of this architecture is the impossibility to update then ...
Example:
1. At the creation of the device I can have
switch1: scene 1
switch2: scene 2
etc ..
2. If I add a new scene to my home automation controller, I have no way to update the device and add a new switch to the adapter
br,

Not sure If I really understand you issue. I think discovery has nothing to do with your request, I think you want something like https://github.com/NEEOInc/neeo-sdk/issues/52 - correct?

Yes and no ;)
I really think that the callback registered with registerInitialiseFunction is raised too late. Handle process just after discovery & user action is the right place, this request is complementary with https://github.com/NEEOInc/neeo-sdk/issues/52.
Use case:
If we supposed you add the ability to add dynamically buttons AND if i use registerInitialiseFunction to create and add buttons/switches/sliders it will never work because callback "initialise" will never called because at this time there are no buttons/switches  expose by device ;)

What I think is that you want is the ability to construct the device capabilities dynamically after the device is selected at the discovery proces. Is this correct?
This is something Tim and myself ran in to when we wanted to build intergrations for other systems.

I changed the text of #52 - where the request is adding favorites (as its called today) - but that feature can be used to add the dynamic part of a device.
the idea of the registerInitialiseFunction is, that you can start initialising tasks like starting a discovery service. this function is called when the first request for that device is handled - so there is no such thing as "too late" in this context.
What exactly do you try to do?

As @neophob said if you need dynamic elements based on 'live' data from the device, favorites #52 or lists #8 would cover that. This is will be the way to go for data that might be short lived on the SDK device and could be removed at any time since it will be queried just in time.
If a device has new functionality that would be covered by updates via #18, this will add the ability to update, add or remove buttons. However it isn't meant to be used to create buttons for 'live' data, it needs represent the capability of the device. That's because buttons could be added as recipe steps or shortcuts and if they're all of a sudden removed it can be problematic and confusing.
As a work around currently using favorite switches (switch A, switch B, and switch C) might be the best option.
The Brain sees 3 switches, but on the SDK you're free to reassign them to different scene, switch A could be using scene 1, but then switched to scene 2 without the Brain having to know anything except if the state changed. It might do the trick in a limited way until the features mentioned above are released.


documentation fix

Hi, great work - very very useful documentation. I'm working on adapting prudaq code for a similar project.
I think this line:
cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMI
should be
cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN

Right you are!  Fixed.

It's off topic but I was wondering if you could explain how the sample code
enables the pins. I use the dto but then i also need to export the pin
manually to allow the prus to control the pins. I can't see how this would
happen in the prudaq code.
On 20 Aug 2016 04:28, "credentiality"<EMAIL_ADDRESS>wrote:

Right you are! Fixed.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/google/prudaq/issues/29#issuecomment-241173596, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAmtbPnhM9zSVrD4fmBS0eHgpBljyYXxks5qhmZigaJpZM4Joo8k
.

http://credentiality2.blogspot.com/2015/09/beaglebone-pru-gpio-example.html?m=1
sent from my android

thanks, nice website.
I figured out my problem was either a buggy install or buggy tools. A dts
will only only load once and then any changes need a reboot.
On 20 August 2016 at 17:18, credentiality<EMAIL_ADDRESS>wrote:

http://credentiality2.blogspot.com/2015/09/beaglebone-pru-gpio-example.
html?m=1
sent from my android
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/google/prudaq/issues/29#issuecomment-241205814, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAmtbGQozSFUfLIGzEDT1FVk6MBxZYt5ks5qhxrRgaJpZM4Joo8k
.

--
Matthew Venn
web mattvenn.net twitter @matthewvenn https://twitter.com/matthewvenn


Missing paramiko

Testing the example notebooks stellargraph-metapath2vec.ipynb and embeddings-unsupervised-graphsage-cora.ipynb in the embeddings demo directory showed that the paramiko package was required. I added installation instructions to README.md and a requirements.txt to make it easy for users to install.
Please review.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Jess Moore seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Coverage remained the same at 84.253% when pulling b85d913981f84210e3b5f16b47e746b730b190ab on missing_paramiko into da453463aaf6d455f166fbb10d94596b8c71684b on develop.

@jessclmoore none of the examples mentioned in the description above require the paramiko package. I ran them in an environment without paramiko installed, they work fine. Are you sure this is required?

Could I ask what the difference between this PR and the "Missing paramiko ps" PR?


Silliness Reduction

This PR represents a motion to usher in a regime change, reducing the overall silliness and levity of this entire project.

Test process output instead of code invocation
Restored Top Level Statements
Removed AssemblyInfo.cs
Obliterates the comedy of errors

It also reduces the amount of code, thus the liability it represents.

This is why we can't have nice things. 🤦♂
Guessing the paths are not comparing 1:1 on lin-bun-tux. FFS.

PR rejected, it's not in the spirit of the project.


filter dropdown fix

Description

How Has This Been Tested?

Types of changes

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

Checklist:

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[ ] I've added relevant tests.

latest grid filter dropdown broken, it repeats the current column filter name over and over instead of displaying the other column names.  easy fix. please accept


Uncaught Error: Cannot call function 'getPosition' on missing remote object 232Error: Cannot cal...

[Enter steps to reproduce:]

...
...

Atom: 1.23.1 x64
Electron: 1.6.15
OS: Mac OS X 10.11.6
Thrown From: Atom Core
Stack Trace
Uncaught Error: Cannot call function 'getPosition' on missing remote object 232
Error: Cannot call function 'getPosition' on missing remote object 232
at throwRPCError (/Applications/Atom.app/Contents/Resources/electron.asar/browser/rpc-server.js:143:17)
at EventEmitter. (/Applications/Atom.app/Contents/Resources/electron.asar/browser/rpc-server.js:354:7)
at emitMany (events.js:127:13)
at EventEmitter.emit (events.js:201:7)
at WebContents. (/Applications/Atom.app/Contents/Resources/electron.asar/browser/api/web-contents.js:256:37)
at emitTwo (events.js:106:13)
at WebContents.emit (events.js:191:7)
At /Applications/Atom.app/Contents/Resources/electron.asar/renderer/api/remote.js:234

Error: Cannot call function 'getPosition' on missing remote object 232
Error: Cannot call function 'getPosition' on missing remote object 232
    at throwRPCError (/Applications/Atom.app/Contents/Resources/electron.asar/browser/rpc-server.js:143:17)
    at EventEmitter.<anonymous> (/Applications/Atom.app/Contents/Resources/electron.asar/browser/rpc-server.js:354:7)
    at emitMany (events.js:127:13)
    at EventEmitter.emit (events.js:201:7)
    at WebContents.<anonymous> (/Applications/Atom.app/Contents/Resources/electron.asar/browser/api/web-contents.js:256:37)
    at emitTwo (events.js:106:13)
    at WebContents.emit (events.js:191:7)
    at metaToValue (/Applications/Atom.app/Contents/Resources/electron.asar/renderer/api/remote.js:234:13)
    at Object.remoteMemberFunction (/Applications/Atom.app/Contents/Resources/electron.asar/renderer/api/remote.js:118:18)
    at AtomEnvironment.module.exports.AtomEnvironment.getWindowDimensions (/Applications/Atom.app/Contents/Resources/app/src/atom-environment.js:691:34)
    at AtomEnvironment.module.exports.AtomEnvironment.storeWindowDimensions (/Applications/Atom.app/Contents/Resources/app/src/atom-environment.js:725:42)
    at WindowEventHandler.handleWindowBlur (/Applications/Atom.app/Contents/Resources/app/src/window-event-handler.js:189:32)

Commands
     -5:13.3.0 core:paste (input.hidden-input)
  2x -5:03.4.0 core:select-right (input.hidden-input)
     -5:02.5.0 core:paste (input.hidden-input)
     -5:00.9.0 core:save (input.hidden-input)
     -4:53.1.0 core:backspace (input.hidden-input)
  4x -4:52.5.0 core:save (input.hidden-input)

Non-Core Packages
atom-beautify 0.30.9
color-picker 2.2.5
compare-files 0.8.1
editorconfig 2.2.2
file-icons 2.1.15
git-clone 0.2.0
import 1.7.0
remove-whitespace 0.2.1
split-diff 1.5.1

Thanks for the report!  Can you confirm a few things for us?

what were you doing at the time of the error?
is the error is reproducible?
if reproducible, do you see the error in safe mode (atom --safe)?

Thanks again for reporting this, I'm going to go ahead and close as a duplicate of https://github.com/atom/atom/issues/16630.  If you remember what you were doing at the time of the error or if you have steps to reproduce, feel free to let us know in #16630.

Because we treat our issues list as the Atom team's backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn't an exact duplicate but is closely related.
For information on how to use GitHub's search feature to find out if something is a duplicate before filing, see the How Can I Contribute? section of the Atom CONTRIBUTING guide.


EF7 Reverse Engineer Existing DB - Timout error

I have already logged it on stackoverflow but no responses so I thought I would try here
http://stackoverflow.com/questions/34712605/ef7-reverse-engineer-existing-db-timout-error

My commandline for comparism is
dnx ef dbcontext scaffold "Server=myserver;Database=mydatabase;Trusted_Connection=True;MultipleActiveResultSets=true" EntityFramework.MicrosoftSqlServer --context ReportingDbContext --output-dir Models
Run from the root of my project directory

My guess is that this is probably something specific to your environment. Searching around it seems like folks hit this when there is an issue with network configuration (this post on StackOverflow for example). Are you able to try from a different machine and with a different instance of the database server?
If you are able to share your schema, then I'm also happy to see if I can reproduce the issue at our end.

Closing as we have not heard back with requested details. Feel free to re-open if you are able to provide steps for us to reproduce the issue.


Inconsistent router helpers

Hey, minor quibble, but just wondering if there is a reason the sign_in_route and sign_out_route accept path arguments differently? One as an argument, the other as an option? Reckon they both could be options???
Current:
    sign_in_route path: "/login"
    sign_out_route AuthController, "/logout"

Better?:
    sign_in_route path: "/login"
    sign_out_route AuthController, path: "/logout"

Makes sense. Would need to be a backwards compatible change (i.e a string should be treated as path: String, but thats easy enough to do. Feel free to make a PR also <3

Discussion moved to #236


Build test app filters

New filter tabs for the build test app page.

This change is

Looking great. But as mentioned in asana, can you adjust it so that there's always a slight margin between the buttons (something like 2px)? This is only an issue for widths before it wraps to two lines.

hi updated!

Looks great, @eballeste. Merging now.


libui since 13 June 2016 uses int instead of intmax_t in most functions

... and this includes uiNewSpinbox.
(https://github.com/andlabs/libui/compare/857bbbf5062f86ef7c7ac175a1505b39088097e7...fa4542f217f1557490ba4b7dddf493ddf616b5d7)
In iui 0.3.0, Spinbox::new_unlimited() will forward to Spinbox::new(i64::MIN, i64::MAX). However, as uiNewSpinbox takes the 32-bit int instead of the 64-bit intmax_t, the C library will truncate the numbers and read as uiNewSpinbox(0, -1), which creates a spinbox with only two valid values: -1 and 0.

Thanks, I'll address this shortly.


API and Secret Key

Hi I want to know how can I get the key and secret values?

Hi, you will need to reach out to AutoTrader directly.
See: https://developers.autotrader.co.uk/api#contact-us


[FEATURE REQ] Investigate whether we can deprecate azure-spring-boot-starter-active-directory.

Investigate whether we can deprecate azure-spring-boot-starter-active-directory.
1, List all AAD's features that spring-security can not provide.
2. Investigate if we can add these features in spring-security-repo.

Here is the detail of aad java classed, seems azure-spring-security-oauth2-resource-server can be deprecated.

azure-spring-security-web
AADHandleConditionalAccessFilter

azure-spring-security-oauth2-core
OAuth2AuthenticatedPrincipal

azure-spring-security-oauth2-client
AADOBOOAuth2AuthorizedClientProvider
AADAzureDelegatedOAuth2AuthorizedClientProvider (Consider move to spring-security)
AADOAuth2AuthorizationCodeGrantRequestEntityConverter
AADOAuth2AuthorizationRequestResolver
AADOAuth2UserService (Can be deleted)
AzureClientRegistration (Consider move to spring-boot)

azure-spring-security-oauth2-resource-server
JwtGrantedAuthoritiesConverter (Consider move to spring-boot)
AADJwtGrantedAuthoritiesConverter (Consider move to spring-boot)
AADJwtBearerTokenAuthenticationConverter (Consider move to spring-boot)

Now I decide to deprecate azure-spring-boot-starter-active-directory, and write samples in this repo: https://github.com/Azure-Samples/spring-boot-application-with-azure-active-directory


Account creation ...

... does not show seed phrases to write them down.

Old ticket :-/
No seed phrase, What do you mean ? That's for wallet account during onboarding or when you add another crypto account @jdsika ?

When new account is created the seed phrase is shown. If user import an account (private key, seed phrase), nothing is shown.


[BugFix] Fix delete index file failed when destory VerticalRowsetWriter after compaction

Use delete_dir_recursive for the index, because the index path is directory but not file.
Fixes #issue
What type of PR is this:

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

[ ] This is a backport pr

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.3
[ ] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

@Mergify close


DE/RE Pin feature

Now this library can be used with RS485 ic MAX485CSA+ or similar. these ICs have DE and RE pins that should be handled properly to enable the transmission, now this library can handle that on any GPIO.
client-rtu_DE_RE.ino and server-rtu_DE_RE.ino examples have been added to explain the uses.

I don't really think this is a necessary addition to the library. I think it makes far more sense to implement any driver enabling within the user implemented function.
Like this:
int32_t write_serial(const uint8_t* buf, uint16_t count, int32_t byte_timeout_ms, void* arg) {
  Serial.setTimeout(byte_timeout_ms);
  SetDE();
  size_t bytes_written = Serial.write(buf, count);
  ResetDE();
  return bytes_written;
}

Since you only need to enable the driver when transmitting you just disable it immediately after sending anything.

Thank you for the feedback.
since I'm not very good at firmware/coding, can you help me add the proper NULL checks to prevent faults
I want to implement it in my project

Closing this, if you have more questions feel free to open an issue


Refactor test driver to make space for more tests

Organized the e2e test driver following the plan for #533. Minimal functional change (e.g. checking for ingress proxy logs)

Jenkins job manager/presubmit passed

Jenkins job manager/presubmit passed

Jenkins job manager/e2e-smoketest passed

merging, but feel free comment, this is not fully done.

Can you please reduce the amount of printfs on the Jenkins console? Either
we carefully sort all printouts into various log levels or we mute it as
one chunk.
This makes it very easy to spot failures (which test failed) in the Jenkins
logs. Secondly, while we are running concurrent tests (ingress, internal,
auth, egress), I think we should serialize the final pass or fail output,
so that in the end, one sees a test failure with name of test that failed.
(If you have already tackled this, please ignore this comment). I believe
@esnible had a similar request a while back when he was trying to find the
failing test in Jenkins logs.
May be these can be logged as nice to haves or features, that we can work
on over time.
On Fri, Apr 14, 2017 at 8:40 PM Jason Young<EMAIL_ADDRESS>wrote:

@ayj commented on this pull request.
In platform/kube/controller_test.go
https://github.com/istio/manager/pull/542#discussion_r111648576:

)

func TestSecret(t *testing.T) {
cl := makeClient(t)

ns := makeNamespace(cl.client, t)
defer deleteNamespace(cl.client, ns)

ns, err := util.CreateNamespace(cl.client)

This pattern of making a client and creating a namespace is repeated a
lot. Maybe refactor into makeClientWithNamespace(), e.g.
cl, ns, err := makeClientWithNamespace()if err != nil {
t.Fatal(err.Error())
}defer cl.close()

In test/integration/driver.go
https://github.com/istio/manager/pull/542#discussion_r111648997:

_, err = shell(fmt.Sprintf("kubectl -n %s apply -f test/integration/config-auth.

yaml", params.namespace))

} else {

_, err = shell(fmt.Sprintf("kubectl -n %s apply -f test/integration/config.yaml", params.namespace))

params.infra.Mixer = true
switch authmode {
case "enable":

params.infra.Auth = proxyconfig.ProxyMeshConfig_MUTUAL_TLS

params.infra.Ingress = false

params.infra.Egress = false

check(runTests())

case "disable":

params.infra.Auth = proxyconfig.ProxyMeshConfig_NONE

params.infra.Ingress = true

params.infra.Egress = true

check(runTests())

case "both":

I'm not sure the both option is necessary here since bin/e2e.sh can run
//test/integration twice (or user of bin/e2e.sh can invoked twice), e.g.
bin/e2e.sh -auth=enable
bin/e2e.sh -auth=disable

In test/integration/driver.go
https://github.com/istio/manager/pull/542#discussion_r111649747:

}

-func deploy(name, svcName, dType, port1, port2, port3, port4, version string, injectProxy bool) error {

// write template
configFile := name + "-" + dType + ".yaml"
+func runTests() error {

This might be a good candidate for Testmain, e.g.
func TestMain(m *testing.M) {
// flags.Parse()
// setup
// deploy
ret := m.Run()
// teardown
os.Exit(ret)
}
func TestReachability(t *testing.T) {
// ...
}
Then we could selectively run test variants from the command line, e.g.
bazel-bin/test/integration/integration -test.run="^TestReachability"
Or with bazel
bazel test //test/integration --test_arg=-test.run="^TestReachability"

In test/integration/driver.go
https://github.com/istio/manager/pull/542#discussion_r111650270:

-/*
-func waitForNewRestartEpoch(pod string, start int) error {

log.Println("Waiting for Envoy restart epoch to increment from ", start)
for n := 0; n < budget; n++ {

current, err := getRestartEpoch(pod)

if err != nil {

	log.Printf("Could not obtain Envoy restart epoch for %s: %v", pod, err)

}

if current > start {

	return nil

for i := 0; i < params.count; i++ {

for _, test := range tests {

	log("Setting up test", test.String())

	if err := test.setup(); err != nil {

		errs = multierror.Append(errs, multierror.Prefix(err, test.String()))

These would probably becomet.Errorf() if TestMain approach were used.
In test/integration/egress.go
https://github.com/istio/manager/pull/542#discussion_r111651509:

+func (t *egress) setup() error {

return nil
+}

+func (t *egress) run() error {

if !t.Egress {

return nil

}
extServices := []string{

"httpbin",

//"httpsbin",TODO

}

funcs := make(map[string]func() status)
for _, src := range []string{"a", "b"} {

This is difficult to read. It might be good to add a new type for these
requests, e.g.
type request struct {
name string
do   func() status
}
func (e *egress) request(src, dst string) status {
// shell("kubectl exec ...")
// return failure|success|again
}
func (e *egress) run() error {
var requests []request
for _, src := range []string{"a", "b"} {
for _, dst := range extServices {
req := request{
name: fmt.Sprintf("External request from %s to %s", src, dst),
do:   e.request(src, dst),
}
requests = append(requests, req)
}
}
return parallel(requests)
}

In test/integration/egress.go
https://github.com/istio/manager/pull/542#discussion_r111652128:

//"httpsbin",TODO

}

funcs := make(map[string]func() status)
for _, src := range []string{"a", "b"} {

for _, dst := range extServices {

	name := fmt.Sprintf("External request from %s to %s", src, dst)

	funcs[name] = (func(src, dst string) func() status {

		url := fmt.Sprintf("http://%s/headers", dst)

		trace := fmt.Sprint(time.Now().UnixNano())

		return func() status {

			resp, err := util.Shell(fmt.Sprintf(

				"kubectl exec %s -n %s -c app -- client -url %s -insecure -key Trace-Id -val %q",

				t.apps[src][0], t.Namespace, url, trace))

			if err != nil {

				glog.Error(err)

An error message is printed twice for this failure: once here (via
glog.Error) and another by the caller of parallel(). It might be better to
propagate the request status via normal error handling, e.g.
type errRequestRepeat struct {}func (e *errRequestRepeat) Error() string { "" } // doesn't matter since we never print it
Then the request runner in parallel would look something like this:
if err := f(); err != nil {
if _, ok := err.(errRequestRequest); ok {
continue // try again
}
return  fmt.Errorf("Failed %s at attempt %d", name, n)
}return nil // success

In test/integration/infra.go
https://github.com/istio/manager/pull/542#discussion_r111652313:

if infra.Auth != proxyconfig.ProxyMeshConfig_NONE {

if err := deploy("ca.yaml.tmpl"); err != nil {

	return err

}

}
if infra.Ingress {

if err := deploy("ingress-proxy.yaml.tmpl"); err != nil {

	return err

}

}
if infra.Egress {

if err := deploy("egress-proxy.yaml.tmpl"); err != nil {

	return err

}

}

I think you had suggested making this table based before. Might be a good
time to do that now, e.g.
deployments := []struct {
filename string
deploy   bool
}{
{"config.yaml.tmpl", true},
{"manager.yaml.tmpl", true},
{"mixer.yaml.tmpl", true},
{"ca.yaml.tmpl", infra.Auth != proxyconfig.ProxyMeshConfig_NONE},
{"ingress-proxy.yaml.tmpl", infra.Ingress},
{"egress-proxy.yaml.tmpl", infra.Egress},
}
for _, d := range deployments {
if d.deploy {
if err := d.deploy(d.filename); err != nil {
return err
}
}
}

In test/util/shell.go
https://github.com/istio/manager/pull/542#discussion_r111652454:

+// limitations under the License.

+package util
+
+import (

"fmt"
"os"
"os/exec"
"strings"

"github.com/golang/glog"
+)

+// Run command and stream output
+func Run(command string) error {

glog.Info(command)

Might be better to have the caller doing the logging in case we want to
use these functions in tests.
In test/integration/ingress.go
https://github.com/istio/manager/pull/542#discussion_r111652830:

+func (t *ingress) String() string {

return "ingress controller"
+}

+func (t *ingress) setup() error {

if !t.Ingress {

return nil

}
t.accessLogs = make(map[string][]string)
for app := range t.apps {

t.accessLogs[app] = make([]string, 0)

}

// setup ingress resources
if err := util.Run(fmt.Sprintf("kubectl -n %s create secret generic ingress "+

We could commit the secret resource with-line key/cert data to reduce the
number of test file dependencies, e.g.
kubectl create secret generic ingress
--from-file=tls.key=test/integration/cert.key
--from-file=tls.crt=test/integration/cert.crt --dry-run -o yaml > test/integration/testdata/ingress-secret.yaml
Then we'd just kubectl apply like we do for ingress.yaml
In test/integration/infra.go
https://github.com/istio/manager/pull/542#discussion_r111653541:

if _, err := io.Copy(writer, strings.NewReader(w)); err != nil {

	return err

}

}

return infra.kubeApply(writer.String())
+}

+func (infra *infra) teardown() {

if infra.namespaceCreated {

util.DeleteNamespace(client, infra.Namespace)

infra.Namespace = ""

}
+}

+func (infra *infra) kubeApply(yaml string) error {
Does it make sense to add similar helper functions for the other kubectl
operations that are repeated throughout? e.g.
func (i *infra) kubectlExec(pod, namespace, container string, format string, args ...interface{}) (string error) {
podCmd := fmt.Sprintf(format, args...)
cmd := fmt.Sprintf("kubectl exec %s -n %s -c app -- %s", pod, namespace, container, podCmd)
return util.Shell(cmd)
}
// oldresp, err := util.Shell(fmt.Sprintf(
"kubectl exec %s -n %s -c app -- client -url %s -insecure -key Trace-Id -val %q",
t.apps[src][0], t.Namespace, url, trace))
// newresp, err := infra.kubectlExec(t.apps[src[0]], t.namespace, "app",
"client -url %s -insecure -key Trace-Id -val %q", url, trace)
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/istio/manager/pull/542#pullrequestreview-32911062,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AH0qd29Zc9uSpHjafkE3YIjEtPPswSPxks5rwBIFgaJpZM4M-JJX
.

--
~shriram

Can you please reduce the amount of printfs on the Jenkins console?

+1
Splitting up features into tests/subtests would help capture the high-level test flow cleanly without adding extra logs. It would also make it much more obvious which tests were passing/failing at the end of the test run.

The noise in jenkins logs got removed in the next PR. The logs are now structured by test and failures are aggregated.


NLPPipeline and Summarizer object not up to par with the rest of the code.

Summarizer (core) object (in sadedgel/core.py) needs to be updated to use better defaults such as Rouge1 summarizer and SBD sentence tokenizer. Documentation on the main README.md should be updated to reflect the changes
As an alternative this can be scrapped entirely, instead relying on Doc + Summarizers.
As another note, #40 depends on this issue's outcome.

Addressed to issue #40 and #45


Unable to create actions with redux-saga plugin

# npm install rekit@next -g
# npm ls -g | grep rekit
+--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>
# rekit install redux-saga
[2020-03-17 04:55:05.733] [info] Plugin installed successfully<EMAIL_ADDRESS>
# rekit create pa-sbo-ui-4 --sass
[2020-03-17 04:55:25.804] [info] Failed to load rekit.json, it doesn't exist or there is some syntax error.
[2020-03-17 04:55:25.810] [info] All plugins: ["common-core","rekit-plugin","rekit-react","redux-saga"]
[2020-03-17 04:55:25.810] [info] Applied plugins for appType common:  ["common-core","redux-saga"]

# rekit add action home/my-action -a
The action is created but with the default redux-thunk middleware, not with redux-saga.
In the old stable version of Rekit (2.3.3) creating the first async action adjusting all Redux-Saga configurations as reported in this issue https://github.com/rekit/rekit/issues/99.
Any suggestion/workaround?
Thanks in advance for the response and for Rekit!

@aritgithub have you been able to find any workaround? I'm going through the same issue

:-( I didn't find any workaround; I downgraded my environment to the<EMAIL_ADDRESS>version.

hi @supnate, any workarounds on this? though using 2.3.3 works fine with redux-saga but that version of react doesnt support hooks API. Im hoping rekit-plugin-redux-saga  has workaround with rekit@latest atleast


Feature Request

Please support furnace advanced macros so that we can pass arguments to the macros - i.e. allow parameter specs in the journal entry and with furnace enabled do macro.execture(...args) instead of macro.execute().
Love the module - wish I thought to write it.

added with 73c4263ae2fb2131a2795b38dc45416199558623


added tests; refactor some code.

Coverage decreased (-32.8%) to 5.714% when pulling 0fbbe99de3ce80993cf8e15697b3e6eb2fc2cd05 on develop into df3e80d559af8ca37025c31170890c0219cd7c3e on master.

Coverage decreased (-32.8%) to 5.714% when pulling 0fbbe99de3ce80993cf8e15697b3e6eb2fc2cd05 on develop into df3e80d559af8ca37025c31170890c0219cd7c3e on master.

Coverage decreased (-32.8%) to 5.714% when pulling efc1142a9482fa1682bf3dfc28b754ebab56ad65 on develop into df3e80d559af8ca37025c31170890c0219cd7c3e on master.

No idea why coveralls rating decreased. I moved a couple functions into their own files under /lib and according to Jest's coverage report, I increased the coverage a good bit. Clearly everything bombed here with Travis, but locally everything passed.

Coverage decreased (-32.8%) to 5.714% when pulling 5e2b5eb8e7a50acb6eb7f8781673468db21a30dd on develop into df3e80d559af8ca37025c31170890c0219cd7c3e on master.

Coverage decreased (-32.8%) to 5.714% when pulling 7be7810b48aa487ab17af404e60ef21b93386d30 on develop into df3e80d559af8ca37025c31170890c0219cd7c3e on master.

Coverage increased (+20.7%) to 59.259% when pulling 9268d64f3f79134dea7882863a1eabcc416e4dbd on develop into df3e80d559af8ca37025c31170890c0219cd7c3e on master.

Coverage increased (+20.7%) to 59.259% when pulling 9268d64f3f79134dea7882863a1eabcc416e4dbd on develop into df3e80d559af8ca37025c31170890c0219cd7c3e on master.


On Delete table page returns to edit screen of that pk, but is a 404 as the table is deleted

go to the list of tables
hit the little eraser
click confirm
404

Superset version
master branch as of 2016-11-15
Expected results
after delete redirect to the /tablemodelview/list/
Actual results
reloads /tablemodelview/edit/{pk}/
Steps to reproduce
make a table, then hit the delete icon

Notice: this issue has been closed because it has been inactive for 523 days. Feel free to comment and request for this issue to be reopened.


User should be able to change the resolution of static heatmaps

Right now it is limited to animated heatmaps.

Fixed in https://github.com/CartoDB/cartodb/pull/2087


Review Assembly Instructions

In #21 I created the first draft of the assembly instructions. @eren-rudy I would appreciate a review of those documents and feel free to make any additions you see fit!
I created this ticket to track that work and I'm assigning it to you.

For some reason, I can't yet assign it to you haha. Maybe you have to comment here first to confirm.

Hey @keenanjohnson, happy to give this a review! And thanks for re-organizing the tasks as well, I think there was some overlap.
Were you thinking that this ticket should include a full assembly to test out the instructions? I want to get a sensor running anyways so I'm happy to get the parts ordered this week and put it together as soon as I can!

I think that maybe let's do a review here of just proof reading the docs and then whenever you have parts for a build, we can creat news issue(s) for that :)

Done! Thanks @eren-rudy !


49 create content type tests

Please, see my pull request

[213] - https://transfer.sh/g3FNa/jdi-dark-bdd-tests.tar.gz

[213] - https://transfer.sh/TidZO/jdi-dark-tests.tar.gz

[213] - Allure report on Netlify: https://5e394443065133087200913a--jdi-dark.netlify.com

[227] - https://transfer.sh/Ri0sw/jdi-dark-bdd-tests.tar.gz

[227] - https://transfer.sh/n0REB/jdi-dark-tests.tar.gz

[227] - Allure report on Netlify: https://5e396f16e4730c4595d4357e--jdi-dark.netlify.com


Feat: footer of sign in page

Describe the feature
footer is not same as other page
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

try to remove this gap too

please check pr @Suchitra-Sahoo


"xo: Fix all auto-fixable problems" not working. Logging: Cannot read properties of undefined (reading 'protocol2CodeConverter')

The "Fix all auto-fixable problems" command ain't working for me.
On the "Runtime Status" there's this Cannot read properties of undefined (reading 'protocol2CodeConverter') error logged for each try.

closed by 89702e2e18bc6ece22425d149fe2a121add8cb80


Not working with latest version of graphql 16.3.0

Getting Error: Expected undefined to be a GraphQL schema.

same

Issue is only with documentation.  Latest version of graphqlSync takes an object as input.
const introspection = graphqlSync({ schema, source: getIntrospectionQuery() }).data


variableInfo not found with test dataset

Needs to be reproduced/diagnosed
May be related to camelcase/etc.

duck MOCK_DATA 5 vars no missing.csv


Update Species “new”

Automatically generated by Static CMS

👷 Deploy Preview for la-chicharra processing.

Name
Link

🔨 Latest commit
18fe7d6761ca6ea453dd6bf91dbab6d39f8d814c

🔍 Latest deploy log
https://app.netlify.com/sites/la-chicharra/deploys/661fc18d862a6e0008dfb8ac


4.x: Host header validation for server request

Resolves #9270
Description
Host header is now fully validated according to the specification in server request. If invalid, a 400 is returned (bad request).

Maybe we can mention new switch in the performance-tuning.adoc

The switch is deprecated for removal, so I would rather not.

What sort of performance impact can we expect from this validation?

If header validation is disabled, none (it is skipped as is all header validation). If header validation is enabled, then there will be an impact for sure, as it does a lot of validation. On the other hand this is required by the HTTP specification, so there is not much we can do about it.

We need a way to turn this off in certain cases, regardless of what spec states. I didn't get the deprecation of the switch.

RE @spericas: validate-request-headers turns it off, and we already have that in perf tuning guide
  protocols:
    "http_1_1":
      validate-request-headers: true|false
      validate-response-headers: true|false

RE @spericas: validate-request-headers turns it off, and we already have that in perf tuning guide
  protocols:
    "http_1_1":
      validate-request-headers: true|false
      validate-response-headers: true|false

Cool, I wasn't sure that flag would control this new validation too


useButton doesn't forward tabIndex prop

🐛 Bug Report
useButton doesn't forward the tabIndex prop.
🤔 Expected Behavior
useButton returns a tabIndex when passed to it as a parameter.
😯 Current Behavior
useButton does not return a tabIndex when passed to it as a parameter.
💁 Possible Solution
https://github.com/adobe/react-spectrum/blob/main/packages/%40react-aria/button/src/useButton.ts
It looks like tabIndex is excluded if the elementType is the default "button". By my current understanding, this shouldn't be the case (https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/tabindex).
🔦 Context
I'm treating tabIndex as a special case in my Button component, which is simple enough, but it would be nice if I and others didn't have to (or debug the issue in the first place).
💻 Code Sample
https://codesandbox.io/s/polished-dust-0k2d1?file=/src/App.js
🌍 Your Environment

Software
Version(s)

react-aria
3.12.0

Browser
Chrome 97.0.4692.99

Operating System
MacOs 11.6.4

Can you explain more of why you need to pass in a tabIndex?
We've found that it's pretty unnecessary and can actually lead to worse accessibility when it is used for anything other than -1 or 0. Therefore, we do not allow it in most places and instead rely on specific hooks that set one of those two values for you. For example, useDialog will set a tabIndex of -1 on the entire dialog specifically for accessibility purposes.

The excludeFromTabOrder prop does allow setting the tabIndex to -1, but we don't recommend setting it to any other value. That said, you can always override the props returned by useButton yourself. e.g. <button {...buttonProps} tabIndex={whatever}>.


Billable?

If I have a logic app with a condition, where it looks like this:
                   Trigger
                      |
                 Condition
                /                \

Connector(Success)      Connector(Skipped)
Do I pay for all actions/connectors or only the ones I have consumed(status success), such as in this instance, 1 x trigger, 1 x condition & 1 x connector? Do I still pay for the skipped connector? Can you further explain this logic?

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

ID: 63815982-c91f-8078-f89d-af3a89dda954
Version Independent ID: 0ffd6861-b0df-a675-6b56-16542c2ef0e5
Content: Pricing & billing - Azure Logic Apps
Content Source: articles/logic-apps/logic-apps-pricing.md
Service: logic-apps
GitHub Login: @kevinlam1
Microsoft Alias: klam

Hi @boltlol Thank you for your feedback! We will review and provide an update as appropriate.

@boltlol Azure Logic Apps meters all successful and unsuccessful actions as executions. However, Logic Apps doesn't meter these actions:

Actions that get skipped due to unmet conditions
Actions that don't run because the logic app stopped before finishing

For more details , follow the doc.
https://docs.microsoft.com/en-us/azure/logic-apps/logic-apps-pricing#actions

@boltlol Hope my previous comment help. Let me know if any other question.

Yes, it did, thank you! I am uncertain if this was there before? If so my apologies!

@boltlol Thanks for the update . Yes it was there before :)


Can I run a job with pytorch distributed training?

Can I run a job with pytorch distributed training?
If I run this commend, does it work?
torchrun --nproc_per_node=$WORLD_SIZE --master_port=1234 newsreclib/train.py experiment=nrms_mindsmall_pretrainedemb_celoss_bertsent

You can run a job with PyTorch distributed training by changing the accelerator, strategy and devices number of the trainer. For example, you can use the ddp_config.
Alternatively, you can do this from command line as python newsreclib/train.py experiment=nrms_mindsmall_pretrainedemb_celoss_bertsent trainer.accelerator=gpu trainer.strategy=ddp trainer.devices=4


KAFKA-14589 [1/3] Tests of ConsoleGroupCommand rewritten in java

This PR is part of https://github.com/apache/kafka/pull/14471
Is contains some of ConsoleGroupCommand tests rewritten in java.
Intention of separate PR is to reduce changes and simplify review.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Will take a look next week. Thanks.

@showuon Thanks for review. Answered to all your comments. Please, take a look one more time.

Re-running the CI build.

CI results looks good for me.

Hello @showuon
CI is OK for me. Are you ready to merge this PR or have other questions, comments?

@nizhikov , thanks for the reminder, I forgot about this PR.
I just checked https://ci-builds.apache.org/job/Kafka/job/kafka-pr/job/PR-15256/8 and https://ci-builds.apache.org/job/Kafka/job/kafka-pr/job/PR-15256/7, the test: kafka.server.DynamicBrokerReconfigurationTest.testThreadPoolResize() failed on each job once. But it didn't appear in earlier run, https://ci-builds.apache.org/job/Kafka/job/kafka-pr/job/PR-15256/4/, as well as the Kafka trunk build: https://ci-builds.apache.org/job/Kafka/job/kafka/job/trunk/2607/ . Could you help check that? Thanks.

@nizhikov I merged https://github.com/apache/kafka/pull/15253. I am not sure if it has any impact on this PR. Does it?

@dajac It has impact, for sure :)
I reflect your changes in the main PR #14471 and will merge them to this PR in the nearest time.

@showuon I run DynamicBrokerReconfigurationTest locally and it passed.
Not sure, how those failures can relate to this PR as I change only specific tests classes.

@nizhikov , could you rebase with the latest trunk branch and let's see if it fixed the test?

@showuon I run DynamicBrokerReconfigurationTest locally and it passed. Not sure, how those failures can relate to this PR as I change only specific tests classes.

OK, let's wait and see if the latest CI build fixes the test.

could you rebase with the latest trunk branch and let's see if it fixed the test?

PR currently merged with the latest trunk changes. https://github.com/apache/kafka/pull/15256/commits/74980be0279f908835ef2ce9f5b1c0aabdf8dcec

@showuon CI results are ready.
AFAICS other tests of DynamicBrokerReconfigurationTest failed in the latest trunk:
https://ci-builds.apache.org/blue/organizations/jenkins/Kafka%2Fkafka/detail/trunk/2609/tests

Other trunk test run contains DynamicBrokerReconfigurationTest  fails, also (but only for 1 environment).
https://ci-builds.apache.org/blue/organizations/jenkins/Kafka%2Fkafka/detail/trunk/2610/tests

@showuon Please, wright me, If those failures should be further investigated.

Hello @showuon
What do you think? DynamicBrokerReconfigurationTest failures related to this PR? Or it can be merged as is?

I think the kafka.server.DynamicBrokerReconfigurationTest.testThreadPoolResize() is caused by this PR. We need to investigate it. From the error, it said there is a thread leaked:
org.opentest4j.AssertionFailedError: Invalid threads: expected 6, got 7: List(data-plane-kafka-socket-acceptor-ListenerName(EXTERNAL)-SASL_SSL-0, data-plane-kafka-socket-acceptor-ListenerName(INTERNAL)-SSL-0, data-plane-kafka-socket-acceptor-ListenerName(CONTROLLER)-PLAINTEXT-0, data-plane-kafka-socket-acceptor-ListenerName(INTERNAL)-SSL-0, data-plane-kafka-socket-acceptor-ListenerName(INTERNAL)-SSL-0, data-plane-kafka-socket-acceptor-ListenerName(EXTERNAL)-SASL_SSL-0, data-plane-kafka-socket-acceptor-ListenerName(EXTERNAL)-SASL_SSL-0) ==> expected: <true> but was: <false>

You can try to run your changed test suites 1 by 1, and check that after all test suite completes, is there any network thread leaked. Let me know if you need help.

@showuon Looks like kafka.server.DynamicBrokerReconfigurationTest.testThreadPoolResize() fails in the latest trunk, also:
https://ci-builds.apache.org/blue/organizations/jenkins/Kafka%2Fkafka/detail/trunk/2618/tests
So, maybe the fail not caused by this PR?

I just re-run CI this morning, and this time, it failed 2 tests in all 4 jobs. Trying to run it again. I can't merge anything introducing test failures, I think you also understand it. It would be helpful if you could help identify the reason why it failed.
Build / JDK 8 and Scala 2.12 / kafka.api.SslAdminIntegrationTest.testAsynchronousAuthorizerAclUpdatesDontBlockRequestThreads()
Build / JDK 8 and Scala 2.12 / kafka.api.SslAdminIntegrationTest.testSynchronousAuthorizerAclUpdatesBlockRequestThreads()

Hello @showuon
I found that DeleteTopicTest.scala don't close resources allocated in case of kraft run.
It was hided by removed tests and lead to the tests failures we observed earlier.
I fixed DeleteTopicTest and now it seems that CI is OK.
Take a look one more time, please.

Hello, @mimaison @jolshan
Can you, please, take a look.
Looks like this PR are ready to merge.

Hello @showuon
I found that DeleteTopicTest.scala don't close resources allocated in case of kraft run. It was hided by removed tests and lead to the tests failures we observed earlier.
I fixed DeleteTopicTest and now it seems that CI is OK.
Take a look one more time, please.

Nice find! Thanks for the fix!

@showuon Thank you for review and merging!


API endpoint to determine withdrawal limit status?

So, this is more of a question, but wasn't sure where else to ask. Is there a way to determine what your withdrawal limit is and how much of it you have available at a certain time? I've looked at all the endpoints on GDAX and Coinbase and cannot seem to find it.

Hi Matt, thanks for your support!
There's a method in the AuthenticatedClient called get_payment_methods.  You may find the limit's listed here.  If not, I can continue digging around, but this is usually a number that doesn't change much and could easily be added to your implementation of the project.
https://docs.gdax.com/#list-payment-methods

Thanks Dan. I was just over-complicating things. I'm trying to determine exactly how much of my limit is available at the second I want to make a trade, which turns out to be quite difficult without an endpoint that tells me this information.
The payment methods endpoint does not tell me what my withdrawal limit is or how much of it is available. I know what the limit is. It's the $10,000 base limit that every knew GDAX user gets.
I am trying to build an arbitrage bot, which will require regular crypto withdrawals to another exchange.  Every time I make a crypto withdrawal, the limit is reduced by the amount of the withdrawal, which sounds simple enough.
Now, here's the tricky part. GDAX starts returning my available withdrawal space as soon as I make the withdrawal. It doesn't just sit there for 24 hours and then return. They actually start giving me back my withdrawal limit at a rate of about 11 cents per second.
I can use my prior transactions, which I have to get through the Coinbase API, to determine when I will have those prior withdrawals added back onto my balance, but it would be nice to use the space that is available in the interim.
In other words, let's say I made a $10,000 withdrawal. I know that 24 hours later I will have $10,000 available again, but 12 hours later I will have $5,000 available. I might want to tell my bot to make a trade at that moment when only $5,000 is available.
However, without knowing how much I had available at an exact, recent point in time, I'm lost as to how to determine it. I'm pretty sure I can do it with math, but THAT IS HARD. Why isn't there just an endpoint that would tell me this information?
Anyways, I will contact the GDAX folks and see if I am missing something. There's always a chance someone else may have figured this out. So, thought it might be worth adding here. If I end up figuring this out I will let you know.
Again, thanks for your response and your awesome work here. Everything is working great and has of course saved me a tremendous amount of time. THANK YOU.

HI,
I am stuck with exactly same issue. I scanned the API documentation and have not found anything that would mention an end point on how to retrieve the withdrawal amount at time X. Even just the static daily limit would be nice, I would write the growth formula myself.
If anyone finds an answer, please, post here.
Thanks!

I believe we cover all API endpoints for the CBPro API.  If there's not an endpoint covered, please share the link here and we can add it to the package.  If the data does not exist on the API currently, we will not add it to the project here, but I would be happy to link to anything supplemental if you'd like.


When will a new stable version be released?

The last stable version released from nextra was 6 August 2021. And from nextra-theme-docs was on 27 March 2021.
Any news on when the new versions will be released?

❤

😏

@shuding can we help you in any way?

Hey @lucasbaquinoo and all! I’m sorry that I couldn't get faster on this. I have been testing out 2.0 with https://github.com/vercel/swr-site for a long time. So far the design of the docs theme feels good to go, but I haven’t started to work on the docs yet. That’s the biggest blocker as far as I can see.
If anyone wants to help, a PR to upgrade the current master branch to 2.0 alpha with new docs would be deeply appreciated. Then we can work on the content together and I can update the logo, card, etc. to prepare for the stable release 👍

Hey @lucasbaquinoo and all! I’m sorry that I couldn't get faster on this. I have been testing out 2.0 with https://github.com/vercel/swr-site for a long time. So far the design of the docs theme feels good to go, but I haven’t started to work on the docs yet. That’s the biggest blocker as far as I can see.
If anyone wants to help, a PR to upgrade the current master branch to 2.0 alpha with new docs would be deeply appreciated. Then we can work on the content together and I can update the logo, card, etc. to prepare for the stable release +1

Good. I will work on it to help you.

@shuding I updated the documentation with the latest versions of the two libraries in alpha. I've hidden the Bleed page because of the styles protruding from the side menu. Perhaps something to be seen later specifically in the library.


Launch with externalTerminal opening in Windows Terminal, but settings point to cmd.exe

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

VS Code Version:

1.86.0

OS Version:

Windows_NT x64 10.0.10945

Steps to Reproduce:

Use default setting for Terminal > External: Windows Exec of C:\WINDOWS\System32\cmd.exe
Set up a launch.json configuration which uses console of externalTerminal
Debug using that launch configuration
Notice that a new Windows Terminal window is opened, with a popup stating: The following argument was not expected: /c  Run with --help for more information

I would have expected this if I set my Terminal > External: Windows Exec to wt; but it's still set to cmd.exe - not sure why this is happening (it didn't happen yesterday, and I haven't modified any settings)

Any help would be appreciated, if there's a particular log I can look in I'd gladly do so.
Thank you!

I pretty agree the response above that some troubles are in external terminal spawnTerminal function. You could refer to the source code. externalTerminalService.ts

I pretty agree with the response above that some troubles are in external terminal service function spawnTerminal. There is an old comment familiar to this issue#104221.

Update, if it's helpful, the launch that we're using is of cppvsdbg type:
    {
      "name": "(Windows) Debug main",
      "type": "cppvsdbg",
      "request": "launch",
      "program": "${workspaceRoot}/<executable>.exe",
      "preLaunchTask": "<task>",
      "args": [],
      "cwd": "${workspaceRoot}",
      "console": "externalTerminal",
      "envFile": "${workspaceFolder}/.env",
    },

I have the same issue since upgrading from 1.85 to 1.86.
From my little investigation I suspect that this is due to the changes from #201020.
I see that the application being spawned begins with:

wt.exe -d  C:\Windows\System32\cmd.exe /c ...

It looks like the Current Directory parameter (following -d) is not set, probably an empty string from what I can see see looking at the code :
			} else if (wt) {
				// prefer to use the window terminal to spawn if it's available instead
				// of start, since that allows ctrl+c handling (#81322)
				spawnExec = wt;
				cmdArgs = ['-d', dir, exec, '/c', command];
			}

This comment is correct. Based on the DAP for RunInTerminalRequest, even if cwd was null, it would use . as the directory before. That commit breaks the scenario where a debug adapter sends an empty string for 'cwd'.
See https://github.com/microsoft/debug-adapter-protocol/blob/774f54178b0ef688219431b4fa55dc1af39118a1/debugAdapterProtocol.json#L766

@roblourens any update on this? like is it confirmed and a fix will come, or do i have to stay on 1.85.2 forever now?

Please fix - downgraded to 1.85 to deal with it; auto-update just brought 1.86 back and it's broken again... This is a major usability issue

Thanks for the investigation, Sebastian. I applied a fix to ensure a directory is passed when launching wt.exe. Please let me know if that resolves the issue.
Terminal > External: Windows Exec is still respected as the shell we launch use in the windows terminal, but since the last release we prefer to run that in the Windows Terminal since there were issues that came up if we launch cmd.exe directly.

Closing this issue now that the candidate PR has been merged.

Issue marked as unreleased but unable to locate closing commit in issue timeline. You can manually reference a commit by commenting \closedWith someCommitSha, or directly add the insiders-released label if you know this has already been releaased

I'm still seeing Tyler's issue with the latest Insiders.
Let me know if there are any logs I can attach.

I am still seeing this issue. It is likely a problem with core VS Code, not the cpptools extension. See my comment here: vscode-cpptools#11970
TL;DR: Set Terminal > External: Windows Exec to be wt (or wt.exe) to work around the issue.


Rewrite Buffer.Utils.xor_bytes_inplace

This appeared to successfully re-extract on my machine, just waiting on CI to come back.
Fixes #43
cc @protz @BarryBo

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: jroesch sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

This is now verifying, so if there are no objections, I'll merge it very soon...
https://msresearch-ext.visualstudio.com/Everest/_build/index?buildId=13141&_a=summary


Support C-n and C-p for up/down by default

While it's very easy to add:
inoremap <silent> <buffer> <C-n> <C-R>=clap#handler#navigate_result('down')<CR>
inoremap <silent> <buffer> <C-p> <C-R>=clap#handler#navigate_result('up')<CR>

to, for example, after/ftplugin/clap_input.vim, it seems like this should be the default to match vim's default. There is no documentation for mappings, either, so I had to root around in the code to find out how you mapped it, which is a bit much for restoring vimlike default behavior.

This has been discussed before, please see https://github.com/liuchengxu/vim-clap/pull/52 .

I can definitely respect your original design decision, <C-n/p> makes sense for input history as well as the result navigation. Do you think it would be worth having some <Plug> mappings so that users could change to their liking more easily? At least, documenting it would be nice.
Aside, I really love the plugin! Great work!

Yes, I thought <Plug> mappings is convenient, but I just saw this issue https://github.com/vim/vim/issues/5147. Plus the popup of vim is unable to be focused, changing the default key bindings means more works. Hence I'm reluctant to add these <Plug> mappings at the moment, it's not hard though.

I'd like to see Ctrl-P/N be the default as well. Not just in Vim, but in many other places Ctrl N/P is the defacto keyboard shortcut for up/down, and I'd expect the same here.

Checkout #52, Ctrl-N/P has been reserved for navigating the input history.

While it's very easy to add:
inoremap <silent> <buffer> <C-n> <C-R>=clap#handler#navigate_result('down')<CR>
inoremap <silent> <buffer> <C-p> <C-R>=clap#handler#navigate_result('up')<CR>

to, for example, after/ftplugin/clap_input.vim

Just a note for anybody stumbling into this issue: The API changed so the code to use is as follows:
inoremap <silent> <buffer> <C-n> <C-R>=clap#navigation#linewise('down')<CR>
inoremap <silent> <buffer> <C-p> <C-R>=clap#navigation#linewise('up')<CR>


chromedriver,chromium: 125.0.6422.141 -> 126.0.6478.55, rebase patches, extend tarball exclude

Description of changes
https://chromereleases.googleblog.com/2024/06/stable-channel-update-for-desktop.html
This update includes 21 security fixes.
CVEs:
CVE-2024-5830 CVE-2024-5831 CVE-2024-5832 CVE-2024-5833 CVE-2024-5834
CVE-2024-5835 CVE-2024-5836 CVE-2024-5837 CVE-2024-5838 CVE-2024-5839
CVE-2024-5840 CVE-2024-5841 CVE-2024-5842 CVE-2024-5843 CVE-2024-5844
CVE-2024-5845 CVE-2024-5846 CVE-2024-5847
Details about the patch rebase and tarball exclude commits are in their respective commit messages.
Things done

Built on platform(s)

[ ] 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.

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

2 packages marked as broken and skipped:

archivebox
archivebox.dist

19 packages failed to build:

aws-azure-login
chromium
chromium.sandbox
fast-cli
grafana-kiosk
mermaid-cli
mermaid-filter
percollate
playwright-test
puppeteer-cli
python311Packages.pytest-playwright
python311Packages.pytest-playwright.dist
python312Packages.pytest-playwright
python312Packages.pytest-playwright.dist
sharedown
single-file-cli
sitespeed-io
vhs
wayback

3 packages built:

chromedriver
selendroid
selenium-server-standalone

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

2 packages marked as broken and skipped:

archivebox
archivebox.dist

22 packages built:

aws-azure-login
chromedriver
chromium
chromium.sandbox
fast-cli
grafana-kiosk
mermaid-cli
mermaid-filter
percollate
playwright-test
puppeteer-cli
python311Packages.pytest-playwright
python311Packages.pytest-playwright.dist
python312Packages.pytest-playwright
python312Packages.pytest-playwright.dist
selendroid
selenium-server-standalone
sharedown
single-file-cli
sitespeed-io
vhs
wayback


Strange/incorrect docs examples in ansys.mapdl.core.math

Describe the bug
Some of the examples in the docstrings in ansys.mapdl.core.math don't seem to be correct, although I'm not sure if it's this or if they are just unclear.
For example:
class AnsMat(ApdlMathObj):
...
    def asarray(self):
        """Returns vector as a numpy array

        Examples
        --------
        >>> from ansys.mapdl import Mapdl
        >>> mm = mapdl.math()
        >>> v = mm.ones(10)
        >>> v.asarray()
        [1. 1. 1. 1. 1. 1. 1. 1. 1. 1.]
        """
        return self._mapdl._mat_data(self.id)

The example given uses the mapdl namespace but doesn't import it, and the import is importing Mapdl which isn't available at the level it is shown at. So I am assuming that it should read:
from ansys.mapdl.core import launch_mapdl
mapdl = launch_mapdl()
mm = mapdl.math()
v = mm.ones(10)
v.asarray()

Am I understanding this correctly?
I noticed other ineeresting examples in the following docstirngs:

MapdlMath init
AnsVec asarray
AnsMat T

This is broken and uses the older API and we need to fix this.

OK I'll take this on for now


[MATLAB] Implement Feather V1 Reader using new MATLAB Interface APIs

Describe the enhancement requested
Now that we've have the basic building blocks for tabular IO in the MATLAB Interface (Array, Schema, RecordBatch), we can implement a Feather V1 reader in terms of the new APIs.
This is the first in a series of issues in which we will work on replacing the legacy feather V1 infrastructure with a new implementation that use the MATLAB Interface APIs. A side effect of doing this work is that we can eventually delete a lot of legacy build infrastructure and code.
Component(s)
MATLAB

take

I meant to take ownership of #37042. Un-assigning my self.


Offset is incorrectly reset after each processed buffer?

Hello.
According to the OpenAL specs found here, documentation for  AL_SEC_OFFSET (page 39) sais:

The position is relative to the beginning of all the queued buffers for the source, and any
queued buffers traversed by a set call will be marked as processed.

At the same time mojoAL resets the source offset after each processed buffer:
https://github.com/icculus/mojoAL/blob/42035035b4e5debb6fe30e475683da2c30e51326/mojoal.c#L1455
Is that a mistake?

I'm sorry, I was mistaken about how this works in mojoAL, and also as a result found a wrong assumption in our own code.
What i missed is that in source_get_offset the returned offset is already summed with the lengths of the processed buffers (if there's a queue of these):
https://github.com/icculus/mojoAL/blob/42035035b4e5debb6fe30e475683da2c30e51326/mojoal.c#L4208


[Doc] Unify broker-related info to BROKER LOAD

Signed-off-by: amber-create<EMAIL_ADDRESS>Why I'm doing: Broker-related info is dispersed in several docs.
What I'm doing: Unify broker-related info to BROKER LOAD
Fixes #issue
What type of PR is this:

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

@mergify backport branch-3.1 branch-3.2


De-alias frame_system in node template runtime

This PR removes the alias frame_system -> system from the node template runtime.
see also: #3295, #6500

@JoshOrndorff good change, but you should go further imo
We should try to remove aliasing from the pallets in general: https://github.com/paritytech/polkadot/pull/1530
So balances -> pallet_balances, sudo -> pallet_sudo, etc...
Looking at the cargo.toml file is an easy way to spot where aliasing is happening.

it needs some change in the chain-spec, but otherwise should be good

I've fixed the build and added the B0 label.
Is that the correct label here? If so I'm ready to merge.

bot merge


Purge Mind doesn't clear actions if Gremlin Leader is killed but not the minions.

Version 0.53.0
Found by Discord user Erichilles#8909
Purge Mind will still cause Wanderer to snap if it kills Gremlin Leader or Reptomancer. I imagine the same happens against Collector too.
Expected: Purge Mind causes Wanderer to snap with killing the non-minion monster in a room of minions.
Actual: fight ends without snapping.

Fixed by #270


Trying to hit Jaeger udp port  from otel collector config yaml file.

Inside open telemetry config YAML, for the Jaeger exporters section currently, we are exporting to port 14250.
Is there a way we can hit any UDP port provided by jaeger.
Currently:
exporters:
jaeger:
endpoint: jaeger:14250
insecure: true
Expected:
exporters:
jaeger:
endpoint: jaeger:6832
insecure: true
All the below ports are supported by jaeger.

UDP and port 6832 are for Jaeger Agent not for collector.
But maybe for your this question around collector you should ask directly on OpenTelemetry collector.
I see you already do it => https://github.com/open-telemetry/opentelemetry-collector/discussions/3080
so I close this issue