[Feature] Support pre-aggregation for quantile type

Proposed changes
close #7782
Problem Summary:
Add a new column-type to speed up the approximation of quantiles.

The  new column-type is named quantile_state with fixed aggregation function quantile_union, which stores the intermediate results of pre-aggregated approximation calculations for quantiles.
support pre-aggregation of new column-type and quantile_state related functions.

I will update this page to add some test results about this column-type later.
Checklist(Required)

Does it affect the original behavior: (Almost No)
Has unit tests been added: (Yes)
Has document been added or modified: (Yes)
Does it need to update dependencies: (No)
Are there any changes that cannot be rolled back: (Yes/No)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...
SOME TEST RESULTS
Cluster : 1 FE + 1 BE   in docker
Table Schema
bucket num: 3
replica num: 1
Table A: with the new column-type QuantileState
CREATE TABLE IF NOT EXISTS $db_name.$table_name
(
  k1 int(11) NULL comment "date",
  k2 INT NULL comment "k2 int",
  v1 quantile_state quantile_union,
  v2 INT SUM
)
AGGREGATE KEY(k1, k2)
PARTITION BY RANGE (k1)
(
  PARTITION p1 VALUES [("20210101"), ("20210102")),
  PARTITION p2 VALUES [("20210102"), ("20210103"))
)
DISTRIBUTED BY HASH(k2) BUCKETS $bucket_num
PROPERTIES (
  "replication_num" = "$replica_num",
  "in_memory" = "false",
  "storage_format" = "V2"
);

Query SQL of Table A：
select k1,quantile_percent(quantile_union(v1), 0.95) from test_quantile where k1= 20210101 group by k1;
Table B: use BigInt Sum to replace QuantileState
CREATE TABLE IF NOT EXISTS $db_name.$table_name
(
  k1 int(11) NULL comment "date",
  k2 INT NULL comment "k2 int",
  v1 BigInt SUM,
  v2 INT SUM
)
AGGREGATE KEY(k1, k2)
PARTITION BY RANGE (k1)
(
  PARTITION p1 VALUES [("20210101"), ("20210102")),
  PARTITION p2 VALUES [("20210102"), ("20210103"))
)
DISTRIBUTED BY HASH(k2) BUCKETS $bucket_num
PROPERTIES (
  "replication_num" = "$replica_num",
  "in_memory" = "false",
  "storage_format" = "V2"
);

Query SQL of Table B:
select k1,sum(v2) from test_quantile where k1 = 20210101 group by k1;
Table C:  store the duplicated data of k3
CREATE TABLE IF NOT EXISTS $db_name.$details_test_table
(
  k1 int(11) NULL comment "date",
  k2 INT NULL comment "k2 int",
  k3 BIGINT NULL comment " k3 is int key not value",
  v2 INT SUM
)

AGGREGATE KEY(k1, k2, k3)

PARTITION BY RANGE (k1)
(
  PARTITION p1 VALUES [("20210101"), ("20210102")),
  PARTITION p2 VALUES [("20210102"), ("20210103"))
)
DISTRIBUTED BY HASH(k2) BUCKETS $bucket_num
PROPERTIES (
  "replication_num" = "$replica_num",
  "in_memory" = "false",
  "storage_format" = "V2"
);

Query SQL of Table C:
select k1, percentile_approx(k3,0.95) from test_quantile_detail_test where k1 = 20210101 group by k1;
Results Sets

number of raw data
number of aggregated data
duration of stream load for table A
duration of stream load for table B
partition data size of table A
partition data size of table B
query time of table A
query time of table B
query time of table C

4 million
50,000
15s
14s
16MB
255KB
0.25s
0.20s
0.85s

4 million
500
15s
14s
18MB
5KB
0.15s
0.01s
0.75s

4 million
50
15s
14s
10MB
2KB
0.11s
0.01s
0.69s

40 million
50,000
126s
122s
176MB
282KB
1.87s
0.02s
6s

40 million
500
126s
122s
104MB
5.8KB
1.02s
0.01s
5.8s

40 million
50
126s
122s
11MB
2.5KB
0.09s
0.01s
6s

before we release the feature, maybe we should support it in vec exec engine both.

before we release the feature, maybe we should support it in vec exec engine both.

yeap, i think it is more reasonable to put it in another pr and i will implement it in the near future.

@wangbo @wangshuo128
Already accepted and completed some of your review comments.

Please format the code style. Maybe https://doris.apache.org/branch-0.13/zh-CN/developer-guide/format-code.html#代码风格定制 would help.

@HappenLee @wangbo
I've made the modifications as suggested by the reviewer.
Please review it soon otherwise I need to keep resolving conflicts with master.


fix: remove clean-publish

well, it causes issues during NPM deployment

:tada: This issue has been resolved in version 1.5.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix typo in tests

There was a typo in one of the test cases (gaph instead of graph).

Thank you very much


Swallowing exceptions

I'm trying to rescue from particular exceptions, to add some resiliency to my services with...
# frozen_string_literal: true

module HandlesError
  extend ActiveSupport::Concern

  included do
    include ActiveSupport::Rescuable

    rescue_from StandardError, with: :handle_exception
    rescue_from ArgumentError, with: :handle_exception
    rescue_from ActiveRecord::RecordNotFound, with: :not_found
  end

  protected

  def not_found(exception)
    handle_exception(exception, code: :not_found)
  end

  def handle_exception(exception, code: :internal_server_error)
    context.status_code = Rack::Utils.status_code(code)
    context.message ||= exception.to_s.humanize
    context.fail!
  end
end

I'm including that in my service via include HandlesError.
I know from your readme that .call swallows errors. Could we move where that happens, so that we can react to internal failures more gracefully?

I found that using this from the controllers was sufficient, and capturing the errors within the service was moot. Disregard!


Properly parse the file path to get the module containing the Scenes

This PR will close #171 .
The lines/file concerned are:
https://github.com/ManimCommunity/manim/blob/ea79842b17ccb7e0a5eb33be5edc5abb4ce60b50/manim/__main__.py#L137-L139
The issue was that the regex based approach would fail when there was a . in the path and end up importing all scenes in the library instead of those that were needed.
The pattern "\..+$" matches all characters after a . , and makes sure that the matched characters end with a newline, and replaces them with an empty string.
The pattern works fine when the only characters to the right of the . is py, but fails when you are leading in from another path.
For ./basic.py, the file_name.replace(os.sep,".") makes the string into ..basic.py, and the regex sees that the first character is a . and sees that the line ends with that string, and matches ..basic,py entirely, and replaces it with an empty string.
./basic.py --> .replace(..) --> ..basic.py --> regex --> ""
And then this empty string gets passed to importlib, which imports all the scenes that exist in the entire repo since it didn't receive a proper module to import.
This has been solved by using string slicing and splitting at appropriate places to extract the module name.
module_name = file_name[:-3].replace(os.sep, '.').split('.')[-1]
The string is first sliced to get rid of the .py, then the separators are replaced with .s. The resulting string is split at every . and the last element of that list, which should be the module name, is taken.
I have tested this from multiple locations, with multiple file names.
The only issue that this approach might face is that it will completely fail when there's a . in the name of the file containing the module, like my.module.py, but the original approach would fail in that case too, so, no net loss ;)

The only issue that this approach might face is that it will completely fail when there's a . in the name of the file containing the module, like my.module.py, but the original approach would fail in that case too, so, no net loss ;)

I don't think this is possible in Python.
@huguesdevimeux I'd love to have a test for this so that we can catch it again in the future. The test should check that the number (and name) of the Scenes provided as options is correct. I'm tagging you since you are the Test Master now. Perhaps make a note (or open an issue) about setting this test up, and we can all get back to it after the current test framework is up and running.
Thanks @Aathish04 for a great save.


changed Relational operators

Fixed operators logic and const correctness.
Removed code duplication.
Added tests for operators.

Thanks for your help @arielyyz, and congratulations on your first open source contribution!


Writing Plan

[ ] Bcrypt / PBKDF2, etc => md5 or sha1 Plus a short PHP demo as bonus
[ ] how to upgrade password methodology smoothly and transparently
[ ] 码农的自我修养（OOP 原则）
[ ] 何为 SOLID 系列
[ ] dependency injection container terminology
[ ] golang openID Connect + OAuth (HUGE workload)

[ ] Front end Learning Note series
[ ] Shells and git cheatsheets

[ ] 快文：解释幸存者偏差

-[ ] A Underrated Website: http://devdocs.io


feat: add section about defining custom type casts with Into and TryInto traits

Maybe add this to Advanced Features section @enitrat @TAdev0 ?

Can you specify what you have in mind exactly?

Will paste the example I'm working on for the Cairo track on Exercism:
pub struct Roman {
    value: ByteArray,
}

#[generate_trait]
impl RomanImpl of RomanTrait {
    fn new(num: u32) -> Roman {
        let mut ROMAN_MAP: Array<(u32, ByteArray)> = array![
            (1000, "M"),
            (900, "CM"),
            (500, "D"),
            (400, "CD"),
            (100, "C"),
            (90, "XC"),
            (50, "L"),
            (40, "XL"),
            (10, "X"),
            (9, "IX"),
            (5, "V"),
            (4, "IV"),
            (1, "I"),
        ];

        let mut value: ByteArray = "";
        let mut current_num = num;
        while let Option::Some((numeric, roman_string)) = ROMAN_MAP
            .pop_front() {
                while current_num >= numeric {
                    value.append(@roman_string);
                    current_num -= numeric;
                }
            };

        Roman { value }
    }
}

impl U32IntoRoman of Into<u32, Roman> {
    #[must_use]
    fn into(self: u32) -> Roman {
        RomanImpl::new(self)
    }
}

The last impl is what's important - it would be helpful for learners to know that they can define custom type casts from any custom type to any other by simply implementing the Into or TryInto traits.

do we really need it?
i think we mentioned that try_into trait returns an option<T>, which means its a trait with a generic type that can be implemented for any type? you think it lacks of clarity?

I still think it would be beneficial to show at least a simple example of implementing one of these traits for a custom type.
I try to assume that my experience can be shared by other people - and my experience was that even after reading The Cairo Book, I did not know I can define custom casts until I saw it implemented somewhere (I think it was Cairo corelib), and when I tried implementing it myself, I couldn't find any easily available resource on how to do that (in the end remembered I can reference the corelib to see how it can be used).

well in this case lets do this , @enitrat  what do you think?

Ok, perhaps something similar to https://doc.rust-lang.org/rust-by-example/conversion.html.
Let's have this under Advanced Cairo Features until the need for more structure emerges

Hey @PedroRosalba , I was already working on a PR, was just wrapping it up.


Feat/reward multiplier

Description
Added reward multiplier facet + tests.
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Added test for every growth type + apply modifier

Will reopen this merge request after trying to find a way to maybe achieve the same results without fixed point precision (but with 18 decimals precision)

lgtm


Initial user flow

Continuing from the assumption of the user flow and adjusting based on the user interview, and incorporate some potential flow cards to facilitate an ongoing conversation with the engineer and stakeholder.

Have conducted several initial iterations to clarify the direction with both the stakeholders and the engineering team, and we are close to finalizing the MVP version.


Use main/calculated color structure for metadata binding instead of b…

…ackup raw one parsed from file

Thanks for this! Can you give an example or what the behaviour is before and after your change? And for both cases before/after postprocessing. Based on that it's easier to understand API semantics changes and possibly writing test cases.

Can do, if you provide a win-64 wheel please. No toolchain here, sorry...

You can download the wheel from continuous integration. Just click on the green tick next to your commit and go to Appveyor. Then select the right build configuration and download the wheel from the artifacts tab.

Nice... Unfortunately the patch is not doing what I hoped...
Before:
import rawpy

with rawpy.imread('./sony.ARW') as raw:
    print(raw.black_level_per_channel)
    print(raw.color_matrix)
    rgb = raw.postprocess()
    print(raw.black_level_per_channel)
    print(raw.color_matrix)

with rawpy.imread('./huawei.dng') as raw:
    print(raw.black_level_per_channel)
    print(raw.color_matrix)
    rgb = raw.postprocess()
    print(raw.black_level_per_channel)
    print(raw.color_matrix)

[512, 512, 512, 512]
[[0. 0. 0. 0.]
 [0. 0. 0. 0.]
 [0. 0. 0. 0.]]
[512, 512, 512, 512]
[[0. 0. 0. 0.]
 [0. 0. 0. 0.]
 [0. 0. 0. 0.]]
[0, 0, 0, 0]
[[ 0.92103994  0.43409887 -0.35513884  0.        ]
 [-0.20845512  1.1323496   0.07610554  0.        ]
 [ 0.00490609 -0.4078749   1.4029689   0.        ]]
[0, 0, 0, 0]
[[ 0.92103994  0.43409887 -0.35513884  0.        ]
 [-0.20845512  1.1323496   0.07610554  0.        ]
 [ 0.00490609 -0.4078749   1.4029689   0.        ]]

After:
import rawpy

with rawpy.imread('./sony.ARW') as raw:
    print(raw.black_level_per_channel)
    print(raw.color_matrix)
    rgb = raw.postprocess()
    print(raw.black_level_per_channel)
    print(raw.color_matrix)

with rawpy.imread('./huawei.dng') as raw:
    print(raw.black_level_per_channel)
    print(raw.color_matrix)
    rgb = raw.postprocess()
    print(raw.black_level_per_channel)
    print(raw.color_matrix)

[512, 512, 512, 512]
[[0. 0. 0. 0.]
 [0. 0. 0. 0.]
 [0. 0. 0. 0.]]
[0, 0, 0, 0]
[[0. 0. 0. 0.]
 [0. 0. 0. 0.]
 [0. 0. 0. 0.]]
[0, 0, 0, 0]
[[ 0.92103994  0.43409887 -0.35513884  0.        ]
 [-0.20845512  1.1323496   0.07610554  0.        ]
 [ 0.00490609 -0.4078749   1.4029689   0.        ]]
[0, 0, 0, 0]
[[ 0.92103994  0.43409887 -0.35513884  0.        ]
 [-0.20845512  1.1323496   0.07610554  0.        ]
 [ 0.00490609 -0.4078749   1.4029689   0.        ]]

So it actually removes the black level in the ARW case, no impact on the DNG one...
Cancelling this PR for now, sorry.


Added fetchWeatherHourly functionality to Weather.gov provider

Added fetchWeatherHourly functionality to:
modules/default/weather/providers/weathergov.js

Looks good @dWoolridge I think you can convert this Draft now into a "real" Pull Request :-)


Update Login.vue

Set autofocus property for "email" field to improve user experience

Just updated. Thanks :smile:


Select: Keyboard Navigation

Description
Keyboard nav in select. open with Enter or Space, select item with arrows, in multiselect check/uncheck with Enter
also fixes #2905
How Has This Been Tested?

Types of changes

[x] New feature (non-breaking change which adds functionality)

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.

Remanining Issues:

When dropdown is in closed state, we cant change value of select by arrow keys (needed especially on single select)
Deciding arrow keys should infinite selecting,
It didn't scroll to the item when we use the overflow dropdown
Alt + Arrow keys didn't work
First enter key didn't work on multiselect
Ctrl+A didn't work completely and properly on multiselect

I will add this on a seperate issue


Wrong third parameters for the getSelfRoutedURLNoQuery in Utils.php

Hello,
I'm facing a bug on Utils.php
The code :
$pos = strpos($selfRoutedURLNoQuery, "?");
if ($pos !== false) {
$selfRoutedURLNoQuery = substr($selfRoutedURLNoQuery, 0, $pos-1);
}
I'm using this bundle on a Nginx web server routing 2 symfony applications.
On my first app I log my users with SSO and the remote IDP return to the URL I defined => myproject.com/app/saml/acs.
The return request go through the function getSelfRoutedURLNoQuery and at the line 645 the function check if there is a "?" in the request (which in my conf NGINX does).
But if a "?" is found, the route is goes through substr and on my side there is a mistake with the third parameter $pos-1 which remove one char before the ?. So instead of have a route like myproject.com/app/saml/acs I have a route like that : myproject.com/app/saml/ac
In my opinion is a bug and someone should fix into $selfRoutedURLNoQuery = substr($selfRoutedURLNoQuery, 0, $pos);

This method tries to get a substring from selfRoutedURLNoQuery if an ? appears
If you have
myproject.com/app/saml/acs?xxxxx

then it calculates the position of ?, and then get the substring before the ?, so
myproject.com/app/saml/acs

Can you add a debug at this method and print before and after the line of the
$selfRoutedURLNoQuery = substr($selfRoutedURLNoQuery, 0, $pos-1);

what values has $pos and $selfRoutedURLNoQuery?

Indeed I have an uri like myproject.com/app/saml/acs?xxxxx.
The strpos ($pos) return 34 for my 60 length uri.
strpos return the position of the "?" substr start at 0 and must finish juste before the "?". So it must finish at the position 34 (at the $pos position). I don't understand why there is a minus one at the $pos which remove the last char before the ?
At the end the var $selfRoutedURLNoQuery return myproject.com/app/saml/ac and not myproject.com/app/saml/acs cause of the minus one after the $pos.

Feel free to update the unit test with your case

Thanks @pitbulk for this fix. Coult it be added to v3 too?

It is at 3.6.1 branch already: https://github.com/onelogin/php-saml/commits/3.6.1

@pitbulk we're impacted by this issue too, when do you see 3.6.1 being available as a release?

Versions 2.19.1, 3.6.1 and 4.0.0 released today.
Let me know if you experience any issues.

Amazing, thank you!


Wave Sort using C++

💥 Proposal
Hi, I am a participant of GSSOC'21.
I want to add the code for wave sort in sorting techniques in C++.
Yes, I have read all the guidelines.
Please assign me this issue.

/assign


Call to undefined method Illuminate\Database\Query\Builder::attachPermission()

Why is this happened? Need help. Here's my code:
use App\Models\Role;
use App\Models\Permission;

$admin = Role::where('name', 'admin');
$createPermission = Permission::where('name', 'create-post');
$admin->attachPermission($createPermission);
dd('Success.');

It returns an error:
BadMethodCallException in Builder.php line 2123:
Call to undefined method Illuminate\Database\Query\Builder::attachPermission()

Note: I already have `admin` role and `create-post` permission in my database.

$admin->attachPermission($createPermission); should be $admin->attachPerms($createPermission);


[Minor][SQL] Replace logger name

This is very minor update. @rxin Please see if it is proper for you. If not, I will close it. Thanks.

LGTM - missed that one.

Test build #48585 has started for PR 10555 at commit 2132171.

@viirya I am working on a PR to remove all Hive dependencies from the parser. In order to do this, I am also touching the ParseDriver. That might supercede this PR.

Ok. No problem. Close this now.

Test build #48585 has finished for PR 10555 at commit 2132171.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/48585/
Test PASSed.


lollypop: 1.4.39 -> 1.4.40

Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

Could you, in a separate commit, also move the file to pkgs/by-name?

Could you, in a separate commit, also move the file to pkgs/by-name?

done


Badges and revert

- What I did
added fancy badges to the readme and revert useless commits
- How I did it
vi
- How to verify it
check it out
- Description for the changelog

/test all

/test all

Looks like the cause is https://github.com/kubernetes/kubernetes/pull/69441 which has caused other test issues in general, let's see

Yeah that is failing for us consistently. We can open a revert if no one does tomorrow.

/test e2e

@mrunalp this is ready

/lgtm


Correct location of partition table in flash ...

I have a gut feel that the partition table is located in flash at flash address 0x8000.  This seems to contradict the address 0x4000 that is listed in the documentation as of the date of this post ... that article can be found here.
http://esp-idf.readthedocs.io/en/latest/partition-tables.html

Thanks @nkolban . We moved the partition table a couple of weeks ago and missed this documentation point.
There's an update in the pipeline for this.

I also seem to find that the old address of 0x4000 is documented in the ESP32-DevKitC getting started guide ... see ... https://espressif.com/sites/default/files/documentation/esp32-devkitc_getting_started_guide_en.pdf

Thanks for reporting that and sorry for the slow turnaround. I've relayed this to the documentation team, the Getting Started guide should be updated soon.


Show Positive and Negative Comment Counts

Fits the use case for our team at Constant Contact:

We have a kind of outdated GitHub Enterprise. It doesn't support reactions yet, so we use comments to review PRs.
Our team has decided on 2 👍 's (or other "positive" emoji) and no 👎  (or for us, a 🌵)
Before this feature, we'd have to open each PR to see if they had been reviewed. Now we can, at a glance, see what PRs have been reviewed and which ones need attention.

You don't need to use emoji, you can also match text strings ("lgtm"). If you give an emoji short code, it will check the comment for both the emoji and the short code (because our old GitHub Enterprise returns the shortcode, but new GitHub returns the actual emoji.
Fetching comments for each PR can be slow, and filtering for key emoji in all the comments can make it worse. So, if you don't provide the comment config in config.json, it should skip those calls entirely.

PS: This is my first time using React/Redux, so please point out any bad patterns I may have used!

I don't have much React/Redux experience, so the rest of the app probably uses bad patterns. 😆
I will take a look and merge this this weekend. Thanks for the PR!


chore: add maxNumProviders to findprovs

In the context of libp2p/js-libp2p-kad-dht#54.
Needs:

[x] libp2p/js-libp2p-kad-dht#55

Thanks, I feel that feat is better in fact!


Add Things Cats Cannot Eat Page & Content

Add a page called "Things Cats Cannot Eat" with some content. Please provide references as well.
Feel free to make any adjustments you may like.
VitePress Docs: https://vitepress.dev/

hey @SanditZZ  assign me this issue


Is possible to make login with a nodejs app in cas server

I there,
I have a cas server 4.1 and a cas-manager on a Ubuntu machine.
I have a nodejs app that as a login page, can I use the app login page and do login by code, using REST API ou other method?

yes you can use the rest api.

I see the info in https://jasig.github.io/cas/4.1.x/protocol/REST-Protocol.html#components
This is an example for CAS-SERVICES is this correct?
1º Request: POST  https://S3:8443/cas/v1/tickets
postdata: sername=casuser&password=Mellon&service=https%3A%2F%2FS3%3A8443%2Fcas-services%2Flogin%2Fcas
1º Response: 201 CreatedTGT CreatedService:
2º request: GET  https://S3:8443/cas-services/login/cas?ticket=TGT-25-ohuGxLKGMWTitkxtufNQ94odOPfvCtUOwbJQV9j7eHq5jctPYb-casc3.example.org
2 response
...

Access Denied
You are not authorized to access this resource. Contact your CAS administrator for more info.

...
What I'm doing wrong?
Thanks

Please use CAS users mailing list for questions like these.


Update<EMAIL_ADDRESS>

I've used ember-cli-update for automatic update.
It also ran ember-modules-codemod to update Ember imports.
Notable changes:

new modules imports
jshint -> eslint
PhantomJS -> Chrome/Chrome Headless for CI
No usages of Ember.HTMLBars.compile and page.render. It replaced by htmlbars-inline-prcompile and this.render().

Originally I've tried to remove bower dependencies as well, but it led to test failures for ember@1 scenarios. I think it can be solved in a separate pr by proper ember try configuration.
Also we've added testdouble dependency for now in order to make node tests pass.

Coverage decreased (-0.5%) to 97.965% when pulling aead2e4be63766b5df4c537780543927ebb34a08 on ec-update into 0ed993233eeff32f08f6dcad0f39debf5c470ca7 on master.

Are there any reasons not to merge?

Any movement on this PR? It appears that the coverage failure is for a branch is due to previous changes (hard to read exactly, the diff doesn't line up at all with the current changes)


Theories directory for Coq source files

This pull request proposes to have all Coq source files in a directory called theories, which is a common way to avoid having many files in the root directory. I also did some updates to the README to use Markdown typesetting.

Thanks, Karl. It looks clear now!


fix missing attribute error schemas.tx_metadata_label_json.items

Errors:
	- attribute components.schemas.tx_metadata_label_json.items is missing

Not sure about the impact of this on backend side.

Thank you for your contribution! This is greatly appreciated, as I  have spent an hour trying to find this bug :)


noImplicitAny not working Typescript

In my root folder I have tsconfig.json file which looks like this:
{
  "compilerOptions": {
    /* Basic Options */
    "target": "es2015", /* Specify ECMAScript target version: 'ES3' (default), 'ES5', 'ES2015', 'ES2016', 'ES2017','ES2018' or 'ESNEXT'. */
    "module": "commonjs", /* Specify module code generation: 'none', 'commonjs', 'amd', 'system', 'umd', 'es2015', or 'ESNext'. */
    "lib": [
      "es2017",
      "dom"
    ],                             /* Specify library files to be included in the compilation. */
    "declaration": false,                   /* Generates corresponding '.d.ts' file. */
    "outDir": "./dist", /* Redirect output structure to the directory. */
    "rootDir": "./src",                       /* Specify the root directory of input files. Use to control the output directory structure with --outDir. */
    /* Strict Type-Checking Options */
    "strict": true, /* Enable all strict type-checking options. */
    "noImplicitAny": true,                 /* Raise error on expressions and declarations with an implied 'any' type. */
    "strictNullChecks": true,              /* Enable strict null checks. */
    "strictFunctionTypes": true,           /* Enable strict checking of function types. */
    /* Additional Checks */
    "noUnusedLocals": true,                /* Report errors on unused locals. */
    "moduleResolution": "node",
    "typeRoots": [
      "node_modules/@types"
    ],                       /* List of folders to include type definitions from. */
    "experimentalDecorators": true,        /* Enables experimental support for ES7 decorators. */
    "emitDecoratorMetadata": true         /* Enables experimental support for emitting type metadata for decorators. */
  }
}

And inside my src filder I have file where I have something like this:
export class CompareDatesLogic implements ICRUD {

    public create() {
        let test;

        test = 'aaaa';
        return {
            name: test,
        };
    }
}

But Visal Code not detecting noImplicitAny, anyone know what can be a problem?

In that example it's not implicitly any. The type is correctly deduced as string.

Yes it is, check image: http://dodaj.rs/images/aLLLP.png

The type shows any because the variable hasn't been given a type. But you won't be able to use it until a value is assigned to it, and after you've assigned to it, it will have that type.

Aha, okay. I tried also another example, to create interface with function and params are reauired but compiler not warn me...
ex.
http://dodaj.rs/images/atxPd.png
Do you know why is that?

You're not required to declare parameters you don't use -- they will just be ignored. In other words, () => boolean is a subtype of (s: string) => boolean.


api.enablePermissiveCORSPolicy modifies the kargo-api configmap, but doesn't seem to do anything

Checklist

[x] I've searched the issue queue to verify this is not a duplicate bug report.
[x] I've included steps to reproduce the bug.
[x] I've pasted the output of kargo version.
[x] I've pasted logs, if applicable.

Description
When using a non-dex oidc provider the login fails with:
No 'Access-Control-Allow-Origin' header is present

Access to fetch at 'https://keycloak.vc-prod.k.home.net/realms/ldap/protocol/openid-connect/token' from origin 'https://kargo.vc-prod.k.home.net' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

Steps to Reproduce

use a provider other than dex?

Version
$ kargo version
Client Version: v0.7.1

Logs
enabled 'debug' logging, but no relevant logs are produced, the error is captured via the browser using the developer tool console

Attempts to resolve

setting api.enablePermissiveCORSPolicy results in kargo-api cm being modified with PERMISSIVE_CORS_POLICY_ENABLED: "true"
restarted all pods
fully uninstalled kargo and reinstalled
tried with a new tab, and via a different web browser
still, same error is generated saying blocked due to cors policy

Thank you.  I was able to add the kargo url as a permitted origin via keycloak and it's working now.  I was able to login.

I just ran into this issue again.  I didn't document how I added the kargo url as a permitted origin, today I added it by setting 'Web origins' to '+' like so:

Reference issue:  https://github.com/akuity/kargo/issues/2950


Replace Brendan Burns with Steve Lasker on maintainers.

This PR must get at least 5 LGTMs before merging:

[x] Brendan Burns<EMAIL_ADDRESS>(@brendandburns)
[ ] Jon Johnson<EMAIL_ADDRESS>(@jonjohnsonjr)
[x] John Starks<EMAIL_ADDRESS>(@jstarks)
[ ] Jonathan Boulle<EMAIL_ADDRESS>(@jonboulle)
[ ] Stephen Day<EMAIL_ADDRESS>(@stevvooe)
[ ] Vincent Batts<EMAIL_ADDRESS>(@vbatts)
[ ] Aleksa Sarai<EMAIL_ADDRESS>(@cyphar)

Signed-off-by: Brendan Burns<EMAIL_ADDRESS>

LGTM (obviously)

needs rebase

I'm not sure that these three PR's for maintainers accurately surface a maintainer election process.
It seems that while just barely, we have had a re-kindled interaction among maintainers recently, spurred by this initial audit.
Though two of the nominees (vrothberg and tych0) are not really present in reviews, PRs or the calls. Lasker is present in discussion and the calls, but not in contributions.
I move that we close these (#841 #842 #844) and among the active contributors as we continue rekindling, we have a proper nomination.

agree with vbatts - I think we can close these and reconsider "proper" nominations in the coming weeks if there's general sentiment it's desirable.

Should this be closed?
This one is different from #842 since it's a resignation and a nomination. Is there any real reason they should be coupled?

Closing these three PRs (#841 #842 #844), so that adding/replacing maintainers can go through the regular nomination process


Fixed deadlock issue related with MMDetWandbHook

Co-authored-by: WangYudong<EMAIL_ADDRESS>Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
Please refer to https://github.com/open-mmlab/mmdetection/issues/8145.
To summarize problem, when we use MMDetWandbHook after TextLoggerHook, problem such as deadlock or AssertionError: loss log variables are different across GPUs! occurs. These are because of same reason and I summarized the reason in https://github.com/open-mmlab/mmdetection/issues/8145#issuecomment-1345343076 here.
Since same problem occurs in mmseg https://github.com/open-mmlab/mmsegmentation/issues/2137, I'm going to make almost-same PR on mmseg after merge of this PR.
Modification
Made MMDetWandbHook to clear runner.log_buffer on every process, including process for GPU 1,2,3...
BC-breaking (Optional)
Does the modification introduce changes that break the backward-compatibility of the downstream repos?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.
Checklist

Pre-commit or other linting tools are used to fix the potential lint issues.
The modification is covered by complete unit tests. If not, please add more unit test to ensure the correctness.
If the modification has potential influence on downstream projects, this PR should be tested with downstream projects, like MMDet or MMCls.
The documentation has been modified accordingly, like docstring or example tutorials.

There was already a similar commit on mmcls https://github.com/open-mmlab/mmclassification/pull/1242, which I didn't know! (this commit was only 5 days ago)
I spent quite a long time trying to figure out the cause of the bug, but there was someone who already figured out the causes :(
Anyway, please merge this PR. Even though detailed implementation is different with https://github.com/open-mmlab/mmclassification/pull/1242, purpose is the same.
Also I guess we don't need separating after_train_epoch, since runner's output buffer is cleared before epoch. I'll test once and update PR.

I've verified my commit.


[material-next][Switch] Change files to TypeScript

[x] I have followed (at least) the PR section of the contributing guide.

Switch issue: #39886
Material You umbrella issue: #29345
Changes

Change Switch files to TS
Fix ts errors
Apply new type style

@mj12albert @mnajdova Since #39935 is now merged, I have changed the types accordingly. Now everything should be ready in this PR.

@mj12albert @mnajdova What about this PR?


Static IP isn't possible.

wifi.config(ip) is not available.

fix it here
https://github.com/mikebutrimov/ESP8266wifi
add setStaticIp method.
Pull request created.


Testbranch

Basic block acceptance unit tests. Also added a sample block
(from July 2011).
The makefile.am.user can be discarded, it got generated
wihout my noticing when I viewed the project in QT creator.

Thanks!  Another interesting test would be to create a chain with a fork and based on the excessive block and accept depth settings see which fork is active.


find()/contains() Doesn't Work on Non-React Elements via componentDidMount()

Refer to enzyme-example-karma-webpack to reproduce my issue:
https://github.com/lelandrichardson/enzyme-example-karma-webpack
So I'd like to write a test to see if my component rendered a non-React child with a particular class name. This child is added via componentDidMount(). Here's a modified Foo component I added to the karma-webpack example repo:
componentDidMount() {
  var div = document.createElement('div');
  div.className = 'bar';
  this.refs.container.appendChild(div);
}
render() {
  return (

  );
}

Then I created a custom test:
it("contains container element", function() {
  expect(mount(<Foo />).find(".container").length).toBe(1);
});

Naturally this test passes. Next I try to find(".bar") and the tests will fail:
it("contains container's 'bar' element", function() {
  expect(mount(<Foo />).find(".bar").length).toBe(1);
});

Is there something fundamental that I am misunderstanding about how enzyme's query selection behavior works? It is not clear to me if this is expected behavior or not based on the documentation.

Update: Sorry I just edited the example, turns out the problem is more specific than I thought. I've updated the issue title and sample code in my first message

My guess is that you're appending the div to the actual DOM, outside of the awareness of React.  I don't believe enzyme is going to find that because enzyme is not searching the DOM, it is searching the React tree.  The tree is a virtual dom, a javascript representation of what the DOM should look like.
I bet you could mount and attach your component to the document body, then find it in the actual DOM and assert on that:
it("contains container's 'bar' element", function() {
  mount(<Foo />, { attachTo: document.body })
  const bar = document.querySelector('.bar')

  expect(bar).find('.bar').length).not.toBeNull()

  wrapper.detach()
})

I didn't test any of this, but I'd explore this direction... back to my day job!

@levithomason Thanks for the tip! I've learned a lot about React in these past few weeks so that makes perfect sense. Anyway, you came up with a pretty easy workaround, so i'll just go with that when i need it

Rather than attaching to document.body, one could use getDOMNode():
const wrapper = mount(<Foo />);
wrapper.getDOMNode().getElementsByClassName("my-class");


fixed #38 (cards overlapping at 100% zoom level)

for better user experience
before ---

after ---

add before after image

add before after image

yeah , done sir


Fix: Do not try too much

This PR

[x] tries not to try too hard

Follows #380.
💁There's probably no need to extend the try and catch block further than trying to find a user, especially if we're only catching UserNotFoundExceptions.

Thanks @localheinz


Do not exclude files if using --suite option

Currently when the --suite option is used, files not matching the specified suite aren't parsed at all. This is a useful performance optimization, but it doesn't work well with the new Name setting (#4583) that allows configuring the suite name in the parsed file itself. Name and --suite not working is documented, but it's still a bug that needs to be fixed and the only way to do that removing the performance optimization.
This change is backwards incompatible and doing it requires having some other way to limit what files are parsed (#4687). Assuming such functionality exists, doing the change in a major version is fine.

Several things have changed after I submitted this issue:

Support for limiting (#4687) will be included in RF 6.1 thanks to get PR #4735.
We got issue #4758 explaining problems caused by --suite not working with the new Name setting.
External parser API has been added (#1283). External parsers may create suites with whatever names and --suite should work with them.

Due to the above changes, I believe this change needs to be done already in RF 6.1.


Project Feedback!

:+1: nice work. A few notes after checking out the code:

Good work on a clean UI
Good to see you were able to format the timestamp cleanly
Good to see you refreshed the timeline after composing a new tweet
Nice touch with the character count being displayed while the user composes a tweet
Nice to see you used a SwipeRefreshLayout library for easy timeline refreshes
Glad to see you made the compose activity into a dialog instead
Good to see you added DBFlow annotations to the models
Good job adding offline support
Great job embedding media image in tweet object
Good job getting retweet and favorite counts displayed
Good job moving compose to FloatingActionButton
Consider adding [progress bars] (http://guides.codepath.com/android/Handling-ProgressBars#actionbar-progress-bar) to your app whenever a network request goes out
Consider using Butterknife for View injection
Code can be refactored in few places, looks good otherwise

Here's a detailed Project 3 Feedback Guide here which covers the most common issues with this submitted project. Read through the feedback guide point-by-point to determine how you could improve your submission.
Let us know if you have any other thoughts or questions about this assignment. Hopefully by now you feel pretty comfortable with all the major pieces to basic Android apps (Views, Controllers, ActionBar, Navigation, Models, Authentication, API Communication, Persistence, et al) and see how they all fit together. We are close now to a turning point in the course where you should be hitting a "critical mass" towards your knowledge of Android.

:+1: Nice work. A few notes after checking out the code:

Nicely done architecting the fragments (base class and extension classes) such that you put as much code and logic as possible in the base class and then used abstract methods to define only the specific behavior where they differ
Good to see you properly communicated the user to the user timeline fragment from the profile activity.
Nice to see you used the ViewPager to properly setup the tabs
The TwitterClient code has duplication in methods for fetching home, mentions and user timeline.
Consider adding progress bars to your app whenever a network request goes out
Try to implement more optional features so that you will get to play with more widgets and understand complexities involved
In the future, definitely consider additional polish for the UI by reviewing the cloning a screen tutorial and Q&A and the drawables guide

Here's a detailed Project 4 Feedback Guide here which covers the most common issues with this submitted project. Read through the feedback guide point-by-point to determine how you might be able to improve your submission.
This week (Week 5), we are going to cover the last major piece to the Android puzzle and that is using the hardware and SDK components such as the camera, photo gallery, location, maps, etc. After that, Week 6 and week 7 we will be covering a few important intermediate topics such as more about styling and animation as well as testing.
Following the bootcamp, we are going to have a public demo day to celebrate the progress you've all made with our next batch of Android students and multiple companies attending to see the group projects that you all have built. We are going to help however we can over the next few weeks to get the team project apps in shape for that.


file-test doesn't wait for async process

I had a hard time writing a failing test using the with-cpp-file macro: It always succeeded because @body  is evaluated using an async callback (while Emacs already exited).
I added
(while (get-process "cmake")
    (sleep-for 0.1))

after the with-cpp-file usage. Now the callback for test-one-cpp-fileis evaluated, but fails:
    (ert-test-failed
     ((should
       (equal-lists ac-clang-flags
		    (list "-DDAS_DEF" ... "-Wall" "-Wextra" "-o" "CMakeFiles/app.dir/foo.cpp.o")))
      :form
      (equal-lists nil
		   ("-DDAS_DEF" "-I/home/juergen/elisp/cmake-ide/test/sandbox/leincludes" "-Wall" "-Wextra" "-o" "CMakeFiles/app.dir/foo.cpp.o"))
      :value nil))

F

Thanks for writing up the issue.


aurelia-cli beta 1.7/typescript 3.2.2 activationStrategy not allowed in router.config

I'm submitting a bug report

Library Version:
aurelia-cli 1.0.7 beta

Please tell us about your environment:

Operating System:
Windows 10

Node Version:
10.11.0

Yarn Version:
1.12.3

JSPM OR Webpack AND Version
Webpack 4.27.1

Browser:
Chrome 70.0.3538.110

Language:
TypeScript 3.2.2

Current behavior:
Just ran yarn upgrade. It updated aurelia-cli from beta 5 to to beta 7
au build fails to compile on
route.config[map ..... activationStrategy:'replace".....
Expected/desired behavior:
It should compile

What is the expected behavior?

What is the motivation / use case for changing the behavior?

Can you show more details? It looks like a syntax error 'replace".

Sorry - that was my bad typing. This was the actual code. I removed activationStrategy and it compiles now.
 public configureRouter(config: RouterConfiguration, router: Router) {
    config.title = "Amberwood";

    config.map([
      { route: ["", "home"], moduleId: PLATFORM.moduleName("modules/home/home"), name: "home", nav: true, title: "Home" },
      { route: "client/:id?", href: "#/client", moduleId: PLATFORM.moduleName("modules/client/client-edit"), name: "clientEdit", nav: true, title: "Clients" },
      {
        route: "contract/:id?", href: "#/contract", moduleId: PLATFORM.moduleName("modules/contract/contract-edit"), name: "contractEdit", nav: true, title: "Contracts",
        activationStrategy: "replace"
      },
      { route: "contract/print", moduleId: PLATFORM.moduleName("modules/printContract/print-contract"), name: "printContract", nav: false, title: "Print contract" },
      {

Sorry, I am not TS user. But can you try TS v3.1.6 + cli beta7? It could be the same reason for the bluebird import failure.

I suspect it was the upgrade to TS 3.2.2 - Stupidly I did them both at the same time. Each time I upgrade TS it find more errors in my code (good thing!).
I do remember that putting in activationStrategy:"replace" never worked anyway. I ended up changing the query string when wanting to reload the same page. I should have removed from route.config at the time.

Based on the d.ts file, I guess you need to do
import {activationStrategy} from 'aurelia-router';
... activationStrategy: activationStrategy.replace,

Nope - doesn't like that

[ts]
Argument of type '({ route: string[]; moduleId: string; name: string; nav: boolean; title: string; } | { route: string; href: string; moduleId: string; name: string; nav: boolean; title: string; } | { route: string; href: string; ... 4 more ...; activationStrategy: string; } | { ...; } | { ...; } | { ...; })[]' is not assignable to parameter of type 'RouteConfig | RouteConfig[]'.
  Type '({ route: string[]; moduleId: string; name: string; nav: boolean; title: string; } | { route: string; href: string; moduleId: string; name: string; nav: boolean; title: string; } | { route: string; href: string; ... 4 more ...; activationStrategy: string; } | { ...; } | { ...; } | { ...; })[]' is not assignable to type 'RouteConfig[]'.
    Type '{ route: string[]; moduleId: string; name: string; nav: boolean; title: string; } | { route: string; href: string; moduleId: string; name: string; nav: boolean; title: string; } | { route: string; href: string; ... 4 more ...; activationStrategy: string; } | { ...; } | { ...; } | { ...; }' is not assignable to type 'RouteConfig'.
      Type '{ route: string; href: string; moduleId: string; name: string; nav: boolean; title: string; activationStrategy: string; }' is not assignable to type 'RouteConfig'.
        Types of property 'activationStrategy' are incompatible.
          Type 'string' is not assignable to type '"replace" | "no-change" | "invoke-lifecycle"'. [2345]

OK  - so it's just a problem in the d-ts. Need to change it to
activationStrategy: "replace" | "no-change" | "invoke-lifecycle"

@bigopon @davismj some typing problem with latest TS?

Sorry - misspoke. It is correct in the d.ts. Can't see why it throws an error for 'replace'.

The router typings are correct. This is a bug or a quirk, depending on how positive you are, in TypeScript itself. See https://github.com/Microsoft/TypeScript/issues/10570.
config.map([
  { route: 'foo', moduleId: 'bar', activationStrategy: 'invoke-lifecycle' }
]);

What happens is that when you write the above TypeScript infers a type from the route config object literal and then tries to match it up with RouteConfig. In the first step, it recognizes 'invoke-lifecycle' as a string and not a string literal type, which is incompatible with the string literal type.
Workaround
config.map([
  { route: 'foo', moduleId: 'bar', activationStrategy: 'invoke-lifecycle' },
  { route: 'foo', moduleId: 'bar', activationStrategy: 'invoke-lifecycle' }
] as RouteConfig[]);

For now, this will work. You could also cast just the activationStrategy: <'invoke-lifecycle'>'invoke-lifecycle' or the individual route configs { ... } as RouteConfig,
Fix
We need to drop the string literal typing in favor of either a string or an enum-like.

I think this was fixed in the latest version of TS, wasn't it?

Haven't seen that. Issue is still open in MS repo and upgrading to latest is what brought my attention to this issue.

I had this issue and got around with
var replaceStrat: any = "replace";     config.map([       {         route: "",         name: "index",         moduleId: PLATFORM.moduleName("pages/index/index", "index"),         title: "Front page",         nav: 0,         activationStrategy: replaceStrat       },


[tool_crash] FileSystemException: Failed to decode data using encoding 'utf-8', null

Command
flutter --no-color pub get

Steps to Reproduce

...
...
...

Logs
FileSystemException: Failed to decode data using encoding 'utf-8', null
#0      _File._tryDecode (dart:io/file_impl.dart:564:7)
#1      _File.readAsStringSync (dart:io/file_impl.dart:584:7)
#2      ForwardingFile.readAsStringSync (package:file/src/forwarding/forwarding_file.dart:96:16)
#3      ErrorHandlingFile.readAsStringSync.<anonymous closure> (package:flutter_tools/src/base/error_handling_io.dart:221:22)
#4      _runSync (package:flutter_tools/src/base/error_handling_io.dart:573:14)
#5      ErrorHandlingFile.readAsStringSync (package:flutter_tools/src/base/error_handling_io.dart:220:12)
#6      AndroidPlugin._getSupportedEmbeddings (package:flutter_tools/src/platform_plugins.dart:137:53)
#7      AndroidPlugin._supportedEmbedings (package:flutter_tools/src/platform_plugins.dart:91:70)
#8      AndroidPlugin.toMap (package:flutter_tools/src/platform_plugins.dart:83:30)
#9      _extractPlatformMaps (package:flutter_tools/src/plugins.dart:606:40)
#10     _writeAndroidPluginRegistrant (package:flutter_tools/src/plugins.dart:622:5)
#11     injectPlugins (package:flutter_tools/src/plugins.dart:1202:11)
<asynchronous suspension>
#12     FlutterProject.ensureReadyForPlatformSpecificTooling (package:flutter_tools/src/project.dart:322:5)
<asynchronous suspension>
#13     PackagesGetCommand.runCommand (package:flutter_tools/src/commands/packages.dart:167:5)
<asynchronous suspension>
#14     FlutterCommand.run.<anonymous closure> (package:flutter_tools/sr

@Steadyoung you had filed the same issue here a week back and it was closed because it was a duplicate, Please do not file a duplicate issue. Closing this issue as a duplicate of https://github.com/flutter/flutter/issues/65021 you may follow up there for further updates
Thank you.


Update postcss

Current version used by sanitize-html has vulnerabilities
https://github.com/advisories/GHSA-7fh5-64p2-3v2j

Hi @suharelli
If you look again at package.json you'll see this is a semver (Semantic Versioning) rule. The "^" means "at least" that version, e.g. it will install the newest in the 8.x series. It does not install that specific version. We do not update package.json every time a dependency releases an update, as long as the semantic versioning rule is correct.
Thanks,
Bob


~HERE'S!!* Lions vs Cowboys Live Steam Free On Tv Channel October 13, 2024

[NFL/TV] — Cowboys vs Lions  LiVe 𝐒𝐭𝐫𝐞𝐚𝐦𝐬 FrEe BrOaDcAsT oN tV cHaNnEl
Dallas Cowboys vs. Detroit Lions: How to watch, kickoff time, channel and more
WATCH 🔴📺▶ Cowboys vs Lions LIVE
WATCH 🔴📺▶ Sunday Night Football LIVE
WATCH 🔴📺▶ Packers vs Cardinals Game LIVE
WATCH 🔴📺▶ Packers vs Cardinals Football LIVE
The Dallas Cowboys and the Detroit Lions, both currently ranked #2 in their conferences, will face off at AT&T Stadium in Arlington, TX this Sunday afternoon. The Lions, fresh off a bye-week, will be rested and ready to play the Cowboys who are currently hoping to halt a three-game losing streak. This Sunday's game will air on Fox, and Tom Brady will be calling it alongside announcer Kevin Burkhardt. Here’s all the info you need about today's Lions vs. Cowboys game, and check out live game-day updates here.
How to watch the Lions vs. Cowboys game:
Date: October 13, 2024
Time: 4:25 p.m. ET/1:25 p.m. PT
Game: Lions vs. Cowboys
TV channel: Fox
Streaming: Fubo, DirecTV, NFL Sunday Ticket on YouTube, and more
What channel is the Lions vs. Cowboys game on?
The Detroit Lions play the Dallas Cowboys this Sunday, Oct. 13 airing live at 4:25 p.m. ET during Fox's late broadcast window.
How to watch the Lions vs. Cowboys game:
You can watch the Lions vs. Cowboys game on Fox on streaming platforms like Fubo TV, DirecTV, and Hulu with Live TV. This Sunday's game also be available on NFL Sunday Ticket on YouTube TV.
2024 NFL season Week 6 full schedule:
All times Eastern
Thursday, Oct. 10
San Francisco 49ers vs. Seattle Seahawks: 8:15 p.m. (Prime Video)
Sunday, Oct. 13
Jacksonville Jaguars vs. Chicago Bears: 9:30 a.m. (NFL Network)
Washington Commanders vs. Baltimore Ravens: 1 p.m. (CBS)
Arizona Cardinals vs. Green Bay Packers: 1 p.m. (FOX)
Houston Texans vs, New England Patriots: 1 p.m. (CBS)
Tampa Bay Buccaneers vs. New Orleans Saints: 1 p.m. (FOX)
Cleveland Browns vs. Philadelphia Eagles: 1 p.m. (FOX)
Indianapolis Colts vs. Tennessee Titans: 1 p.m. (CBS)
Los Angeles Chargers vs. Denver Broncos: 4:05 p.m. (CBS)
Pittsburgh Steelers vs. Las Vegas Raiders: 4:05 p.m. (CBS)
Atlanta Falcons vs. Carolina Panthers 4:25 p.m. (FOX)
Detroit Lions vs. Dallas Cowboys: 4:25 p.m. (FOX)
Cincinatti Bengals vs. New York Giants: 8:20 p.m. NBC)
Monday, Oct. 14
Buffalo Bills vs. New York Jets: 8:15 p.m. (ESPN)
How to watch every NFL game this season:
Many NFL games are broadcast on local channels, so if you're looking to catch an in-market game, it may be as simple as turning on your TV (or setting up a digital TV antenna). A $7/month subscription to NFL+ will get you access to NFL Network which can be great for watching some games, but the downside of NFL+ is that when it comes to the regular season, it's just local and primetime games (and only on mobile or tablet!). In which case, here's what we recommend to watch the NFL.


Update to React 15.0.1

@jaredpalmer what are your thoughts about updating this to React 15.0.1?

I have updated all packages to latest (including React 15.0.2) and all seems to be well. All build and test operations work as expected and no app errors have been observed.
I used npm install package1@* package2@* etc@* --save but npm-check-updates looks to make this even easier.


separate WebRoot for serving MSeedWrite directory

Would be nice to have a separate (and standard) URL endpoint for serving miniseed data archive via MSeedWrite to keep the mseed archive directory separate from normal files.
Also, making this a standard, maybe /mseed would make it easier to write clients that can interact with any ringserver with less special configuration.
Perhaps something like:
MSeedWrite /data/archive/%n/%s/%Y/%j/%n.%s.%l.%c.%Y.%j.%H
MSeedWebRoot /data/archive/

which would serve the contents of /data/archive via http as /mseed.
Additional nice thing would be to allow dir listing via http for this so clients can easily tell which mseed files exist, and if they are smart enough at parsing the pattern, could figure out what networks and stations exist and what the time range is for them.
Being able to get the pattern from the server would also be handy, maybe /pattern could return the part of MSeedWrite less that of MSeedWebRoot, so in this case it would return %n/%s/%Y/%j/%n.%s.%l.%c.%Y.%j.%H

ringserver refuses to serve files outside of the WebRoot for security.  This is similar to Apache httpd and probably many other web servers, which require explicit permission to serve files from given locations.
I suggest doing what you want with a full blown web server, e.g. Apache httpd, and adding a few proxies for the endpoints that you want ringserver to serve, e.g. /streams, /seedlink, etc.  There is no need to reinvent this wheel in ringserver itself.


vscode-csharp - new lsp server

Language server
vscode-csharp
Requested feature
https://devblogs.microsoft.com/visualstudio/announcing-csharp-dev-kit-for-visual-studio-code/
Microsoft released a new version of vscode extension for C# on 06/06.
by a new fully open-source Language Server Protocol (LSP) host, creating a performant, extensible, and flexible tooling environment that easily integrates new experiences into C# for VS Code
Here is the process that run instead of Omnisharp.dll:
79855   ??  Ss     0:41.46 dotnet /Users/redacted/.vscode-insiders/extensions/ms-dotnettools.csharp-2.0.206-darwin-arm64/.roslyn/Microsoft.CodeAnalysis.LanguageServer.dll --logLevel Information --starredCompletionComponentPath /Users/redacted/.vscode-insiders/extensions/ms-dotnettools.vscodeintellicode-csharp-0.1.9-darwin-arm64/components/starred-suggestions/node_modules/@vsintellicode/starred-suggestions-csharp --extension<EMAIL_ADDRESS>--sessionId af60e874-a2e7-41d4-8854-b6e1646b9f601686121999271 --telemetryLevel all
other resources:

https://github.com/dotnet/vscode-csharp
https://github.com/dotnet/vscode-csharp/issues/5708

Other clients which have this feature
No response

I just see  this (powered by OmniSharp) .looks like also based on omnisharp?

I'm not really sure. The repo is confusing.
In this commit: references to omnisharp has been removed:
https://github.com/dotnet/vscode-csharp/commit/08682dc08ce7283e934c6a9c8acf13d4b17db71f
In the process I put in the original post, the process is now called LanguageServer.dll and not Omnisharp.dll
But I'm not sure

It seems the new dll is part of a new internal Roslyn LSP server:

https://github.com/dotnet/vscode-csharp/issues/5276#issuecomment-1581651560
https://github.com/dotnet/roslyn/pull/68461.

Please be aware that it's not really clear whether or not it's allowed to use the new LSP server outside of VS family editors.
https://github.com/dotnet/roslyn/issues/68463

According to this comment, the intent is that new LSP server will be part of roslyn and share the same license (MIT), though.
Hopefully this will get sorted out soon.

Looks to be sorted out. https://github.com/dotnet/roslyn/pull/68942

has anyone tried to manually configure the new LSP in Neovim? would the license allow us to integrate it in this repo?

has anyone tried to manually configure the new LSP in Neovim? would the license allow us to integrate it in this repo?

The license is MIT, so there should be no issues there.
I have not tried to set it up manually though.

For anyone interested, I was able to set it up manually with this config (using the new LSP installed via the vscode extension):
local lsp_configurations = require('lspconfig.configs')
if not lsp_configurations.roslyn then
    lsp_configurations.roslyn = {
        default_config = {
            name = 'roslyn',
            cmd = {
                "dotnet",
                "c:\\users\\max\\.vscode\\extensions\\ms-dotnettools.csharp-2.0.346-win32-x64\\.roslyn\\Microsoft.CodeAnalysis.LanguageServer.dll",
                "--logLevel=Information",
                "--extensionLogDirectory=c:\\temp\\"
            },
            filetypes = { 'cs' },
            root_dir = require('lspconfig.util').root_pattern('*.sln'),
        }
    }
end

local on_attach = function(client, bufnr)
    -- keymaps
end

require("lspconfig").roslyn.setup({
    on_attach = on_attach,
})

What seems to work:

Renaming symbols
Applying code actions
Code formatting
Loading "simple" nvim-cmp LSP suggestions

keywords
local symbols
class names, etc. work, but I can't get suggestions for nested properties/methods

What doesn't work for me:

Go to definition
Diagnostics or code errors
Loading "complex" nvim-cmp LSP suggestions

properties/methods of a class instance
symbols from other namespaces
etc.

Applying nvim-cmp suggestions causes the LSP to crash with the following error:

"[LanguageServerHost]System.ArgumentException: The changes must not overlap. (Parameter 'changes')...

Any ideas on what I might be doing wrong?

Really love to have this. I think OmniSharp will be deprecated soon. A lot of issues in the github repo have not been resolved for months (for example auto importing not working).

Just an update, the manual config I posted above no longer works at all... It appears that a change was made to the LSP to use "named pipes" instead of stdout and I can no longer attach to the LSP from nvim.
This is not really something I am familiar with, so if anyone has any experience with this, I could really use some help!

@maxle5
I have gotten around the pipes issue by making the below modification to program.cs in the Roslyn repo: https://github.com/dotnet/roslyn/blob/main/src/Features/LanguageServer/Microsoft.CodeAnalysis.LanguageServer/Program.cs#L119
    // var (clientPipeName, serverPipeName) = CreateNewPipeNames();
    // var pipeServer = new NamedPipeServerStream(serverPipeName,
    //     PipeDirection.InOut,
    //     maxNumberOfServerInstances: 1,
    //     PipeTransmissionMode.Byte,
    //     PipeOptions.CurrentUserOnly | PipeOptions.Asynchronous);

    // Send the named pipe connection info to the client
    //Console.WriteLine(JsonConvert.SerializeObject(new NamedPipeInformation(clientPipeName)));

    // Wait for connection from client
    // await pipeServer.WaitForConnectionAsync(cancellationToken);

    using var stdIn = Console.OpenStandardInput();
    using var stdOut = Console.OpenStandardOutput();

    // UTF8Encoding utf8 = new UTF8Encoding();
    // var stuff = "Starting the LSP";
    // var bytes = utf8.GetBytes(stuff);
    // stdOut.Write(new ReadOnlySpan<byte>(bytes));

    // var server = new LanguageServerHost(pipeServer, pipeServer, exportProvider, languageServerLogger);
    var server = new LanguageServerHost(stdIn, stdOut, exportProvider, languageServerLogger);
    server.Start();

That being said, based on the PR you linked, it sounds like they found that a named pipe offers advantages to standard out. If that is the case, I suppose we have to open a feature request to Neovim to allow named pipe communication? Looking at the code this did not look like an option at the moment.
After getting the Roslyn Language Server to attach, I also had to make a "solution/open" notification request to the Language Server in order for things like "Go To Definition" to work. "solution/open" does not appear to be part of the LSP spec. Maybe we could make a custom handler for the "initialize" request response that would fire back a "solution/open" request?
I am currently working on the Diagnostics. In order to get them running at all, I had to use the development release of Neovim. It has support for the textDocument/diagnostic request. It seems to fire it off after it makes textDocument/didChange requests. The diagnostics request seems to work fine given it has the correct text of a ".cs" file. However, that was not always the case. The Language Server's copy of the ".cs" file gets corrupted. This appears to be happening in trying to keep the ".cs" file up to date with the textDocument/didChange requests. I'm currently trying to figure out if the requests are not being issued properly by Neovim or if they are not being handled properly by the server.

Looks like an issue was opened up in the Roslyn repo to address the issue with handling textDocument/didChange notifications: https://github.com/dotnet/roslyn/issues/70392
To continue testing, I applied this patch locally to the Roslyn LanguageSever code:
diff --git a/src/Features/LanguageServer/Protocol/Handler/DocumentChanges/DidChangeHandler.cs b/src/Features/LanguageServer/Protocol/Handler/DocumentChanges/DidChangeHandler.cs
index 6a8f66ffbfc..a09b9463de2 100644
--- a/src/Features/LanguageServer/Protocol/Handler/DocumentChanges/DidChangeHandler.cs
+++ b/src/Features/LanguageServer/Protocol/Handler/DocumentChanges/DidChangeHandler.cs
@@ -4,7 +4,6 @@

 using System;
 using System.Composition;
-using System.Linq;
 using System.Threading;
 using System.Threading.Tasks;
 using Microsoft.CodeAnalysis.Host.Mef;
@@ -33,11 +32,12 @@ public DidChangeHandler()
         {
             var text = context.GetTrackedDocumentSourceText(request.TextDocument.Uri);

-            // Per the LSP spec, each text change builds upon the previous, so we don't need to translate
-            // any text positions between changes, which makes this quite easy.
-            var changes = request.ContentChanges.Select(change => ProtocolConversions.ContentChangeEventToTextChange(change, text));
+            foreach (var change in request.ContentChanges)
+            {
+                var textChange = ProtocolConversions.ContentChangeEventToTextChange(change, text);
+                text = text.WithChanges(textChange);
+            }

-            text = text.WithChanges(changes);

             context.UpdateTrackedDocument(request.TextDocument.Uri, text);

Although I have not done extensive testing yet, Go To Definition, Find References, Diagnostics, Completions, etc. seem to be working for me.

@boost1231  Thank you a lot for all this amazing work. I applied your fixes and attached the roslyn Lsp succesfully. It seemed to work quite well an fast, but one bug I ran into was, that the auto-completion didn't when I wanted to call a method of a service or a Property of a class. So when entering a "." after a service I didn't get the possible methods.
Did you also have this problem or is it only with me?

There are multiple issues in the current Roslyn LSP, it doesn't follow the LSP spec in some scenarios. I created a plugin that installs and sets everything up so that we can use the Roslyn LSP from neovim, the experience should be pretty good out of the box. I've been using it, and I have code-completion, go to definition, go to reference, etc. I intercept some calls to and from the lsp to workaround the scenarios where Roslyn doesn't follow the spec.
https://github.com/jmederosalvarado/roslyn.nvim

@jmederosalvarado Thank you so much! With the PR from @maxle5 this is working really well in Windows 11. Thank you @boost1231, @maxle5 and @jmederosalvarado for diving in for the rest of us!

@jmederosalvarado Thanks for putting this plugin together! I have not fully digested it yet, but just have a few questions.

Were there any reasons you chose to add a command to install the Language Server as oppose to using a package manager like Mason.nvim?
In regards to: "There are multiple issues in the current Roslyn LSP, it doesn't follow the LSP spec in some scenarios." Can you expand on what isn't following the spec? It looks like they fixed the issue with TextDocument/didChange notifications.

Hi @boost1231

Were there any reasons you chose to add a command to install the Language Server as oppose to using a package manager like Mason.nvim?

Not at all, from the beginning my purpose was to integrate the installation process into Mason.nvim, but first I wanted to make sure the install process worked correctly, otherwise trying to reverse engineer the vscode extension for how the install should be done at the same time I implemented it in Mason would have been too complicated. This is the next thing I'm planning to focus on.

There are multiple issues in the current Roslyn LSP, it doesn't follow the LSP spec in some scenarios." Can you expand on what isn't following the spec? It looks like they fixed the issue with TextDocument/didChange notifications.

if you go to the hacks file in the plugin, you will see there are multiple scenario that need some kind of workaround for neovim to work well with roslyn. Not all of them are problems with roslyn, some are neovim lsp client issues, and for others I'm yet to figure out which one is not following the spec. I'll list them bellow and link to the issue in the corresponding repo:

textDocument/didChange issue: https://github.com/dotnet/roslyn/issues/70392
Neovim emitting warning on unknown diagnostic tag: this is a neovim issue, as unknown diagnostic tags should be ignored -> [this] PR will fix that in neovim
On didChangeWatchedFiles registration roslyn is asking neovim to watch a baseDir that doesn't exist and neovim file watcher crashes. I'm yet to figure out if roslyn shouldn't be asking to watch missing directories or if neovim should ignore this watcher when the baseDir doesn't exist.
Also on didChangeWatchedFiles roslyn is sending the baseDir to watch with a trailing /, but neovim is assuming no trailing slash exist and it's adding one to the pattern which results in pattern trying to match paths with // (two consecutive slashes). This one will probably be on the neovim side to just sanitize the uri received from the server.

So, (3) and (4) are fairly low priority for now, as you could just disable file watching. Neovim nightly introduces support for didChangeWatchedFiles. Neovim uses system file watchers to let the server know whenever a file changes. You can disable this capability by doing:
capabilities = vim.tbl_deep_extend("force", capabilities, {
    workspace = {
        didChangeWatchedFiles = {
            dynamicRegistration = false,
        },
    },
})

My intention is to slim down the plugin as much as possible, by porting install functionality to mason, and fixing in neovim the rest of the issues, but it will take some time to get there.

Thanks for the detailed response, and nice work! Much appreciated.

Thank you so much for the detailed work. This new library is so awesome. It support lots of things that Omnisharp failed to provide such as the ability to auto import after completion <3 and so much more.

@jmederosalvarado I have also added an issue in the Roslyn repo to add support for semanticTokens/full request: https://github.com/dotnet/roslyn/issues/70536

Sounds good @AnhQuanTrl , have you thought of opening an issue in neovim asking for support for semanticTokens/range?

I found it is already requested in this issue: https://github.com/neovim/neovim/issues/23026.

I find that when I make code changes to FileA that breaks code in a FileB that is loaded in another hidden buffer, diagnostics are not reported when I switch to FileB.
The LSP spec has a "relatedDocuments" property that appears like it would support this very scenario. (https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#relatedFullDocumentDiagnosticReport). However, as far as I can tell, Roslyn does not populate that property even though the serverCapabilities it reports would indicate otherwise. In any case, I opened an issue: https://github.com/dotnet/roslyn/issues/70616
In the mean time, I added this to the on_attach callback:
if client.supports_method(require('vim.lsp.protocol').Methods.textDocument_diagnostic) then

    vim.api.nvim_create_autocmd('BufEnter', {
      buffer = bufnr,
      callback = function()
            require('vim.lsp.util')._refresh(
                require('vim.lsp.protocol').Methods.textDocument_diagnostic,
                { only_visible = true, client_id = client.id })
      end,
    })

end

So that diagnostics are pulled every time I enter a buffer.
Has anyone else experienced this issue? Or have any other suggestions on how to deal with it? I wonder if neovim should allow configuration around when diagnostics are pulled. It seems like how often and when could be a matter of preference. Here is a code link in the neovim repo that shows when diagnostics are pulled: https://github.com/neovim/neovim/blob/master/runtime/lua/vim/lsp/diagnostic.lua#L425

Not sure if it belongs here, but wouldn't know where else to find all the people using the new vs-code-LS.
Does anybody know if it is possible that the language server also includes files which are created with a source generator?

the language capabilities (LSP) is provided by another extension (https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.csharp) which is also installed alogside csdevkit, but if you read there:

To be on the save side, we should get it from the source and not rely on the packages that are distributed via vscode extensions. This is only how I understand it, I am not that experienced in the legal stuff.

any news on this?

I took a look at this today, but the server wants to communicate via a unix socket/named pipe instead of stdin/out. Do you think this should be supported in nvim, lspconfig or should we ask for a --stdio option on roslyn-ls? I did not understand why they were moving away from stdin, it seemed something was printing garbage on stdout so it broke RPC.

I took a look at this today, but the server wants to communicate via a unix socket/named pipe instead of stdin/out. Do you think this should be supported in nvim, lspconfig or should we ask for a --stdio option on roslyn-ls? I did not understand why they were moving away from stdin, it seemed something was printing garbage on stdout so it broke RPC.
PS: This is my current draft if anyone wants to take a look:
Draft
local util = require 'lspconfig.util'

local function open_sln(client, sln)
  client.notify("solution/open", {
    ["solution"] = vim.uri_from_fname(sln),
  })
end

return {
  default_config = {
    cmd = {
      'Microsoft.CodeAnalysis.LanguageServer',
      '--logLevel=Information',
      '--extensionLogDirectory=' .. vim.fs.dirname(vim.lsp.get_log_path()),
    },
    filetypes = { 'cs', 'vb' },
    root_dir = util.root_pattern('*.sln', '*.csproj'),
    init_options = {},
    on_init = function(client)
      print("on_init")
      -- Not sure if client.root_dir exists, since the server/client can't communicate without unix sockets I did not get to this point.
      print(vim.inspect(client))
      local sln_dir = client.root_dir
      if not sln_dir then
        return
      end

      local targets = vim.fn.glob(util.path.join(sln_dir, "*.sln"))
      if #targets == 0 then
        vim.notify("Starting in single file mode")
      elseif #targets == 1 then
        open_sln(client, targets[1])
      else
        vim.ui.select(targets, {
          prompt = "Select solution file",
        }, function(sln) open_sln(client, sln) end)
      end
    end,

  },
  docs = {
    description = [[
https://github.com/dotnet/vscode-csharp

The language server behind C# Dev Kit for Visual Studio Code
]],
    default_config = {
      root_dir = [[root_pattern("*.sln", "*.csproj")]],
    },
  },
}

neovim already supports named pipes, see https://github.com/neovim/neovim/pull/26032
Or do I miss something here?

Neovim does support named pipes but no LSP in lspconfig is using it as far as I can tell. Maybe it's an easy one line change, maybe not. I must say, I never used the raw lsp API without lspconfig, so I'm not really knowledgeable in this area.

I have been looking into this as well:

This requires a very custom module, and currently, https://github.com/jmederosalvarado/roslyn.nvim works by essentially copy-pasting the whole rpc.lua module from neovim and modifying here and there to get it to work.
In my config, I do it similarly. Copying is needed because we need to use some functions/classes that are private.

While trying to debug another issue today regarding performance, I found out that the code to getting roslyn to work in neovim can be simplified a lot, and that it isn't actually necessary to duplicate the whole rpc module: https://github.com/seblj/roslyn.nvim/commit/8f097106b61d51fe13d8c424a347f305c48ffefd
TLDR; You can just start the language server, and in the stdout handler, parse the name of the pipe and use it as a parameter for vim.lsp.rpc.connect. Then you can just schedule vim.lsp.start, and use vim.lsp.rpc.connect(pipe_name) as cmd, and everything should work
I am still having a couple of issues with the language server though, and on some repos I have, it will come to a serious halt. Neovim will be really slow to quit, and in some cases, I also get a lot of errors... I haven't really figured out these issues, and it also doesn't seem like vscode has the same issue. I don't know if anyone else have been looking into this, but I thought I should share my findings in removing the entire duplication of the rpc module😄

I'm a noob, is nvim-lspconfig needed here if I use the plugin maintained by @seblj? I'm not sure if that plugin handles adding new buffers to the lsp.

@zoriya's draft looks great but it looks like it won't play well with @seblj's plugin, as they both send a solution/open notification. I'm still new to nvim, is the intention to use both the nvim-lspconfig and roslyn.nvim plugins together?

You don't need nvim-lspconfig to use the plugin. The plugin was created because the server can't be started without some hacks. Because the server doesn't follow the spec for initializing communication with the client, as pointed out earlier in this issue

@seblj thanks. In that case is there still a need for nvim-lspconfig here? From what I can see your plugin seems to handle it all.

The plugin is standalone, so no need for nvim-lspconfig

Thanks. I suppose we can close this then?

Thanks. I suppose we can close this then?

Probably.
I've been daily driving seblj plugin without real blockers ( a restart is sometimes required after suspend tho ).
Currently only awaiting the Mason MR.


only debug mode occur error

I used the retrofit library to perform a Get request. The response is in JSON format, and I'm encountering the following error in the auto-generated code:
"type '_Map<String, dynamic>' is not a subtype of type 'String' in type cast"
The strange thing is that the error doesn't occur when running in release mode; it only happens in debug mode.
version:  retrofit: ^4.0.3
write code:
@GET('/somethingpoint')
Future<DataClass> getSomethingPoint();

** DataClass created by "freezed" lib **
auto gen code:
@override
  Future<DataClass> getSomethingPoint() async {
    const _extra = <String, dynamic>{};
    final queryParameters = <String, dynamic>{};
    final _headers = <String, dynamic>{};
    final Map<String, dynamic>? _data = null;
    final _result = await _dio
        .fetch<Map<String, dynamic>>(_setStreamType<DataClass>(Options(
      method: 'GET',
      headers: _headers,
      extra: _extra,
    )
            .compose(
              _dio.options,
              '/somethingpoint',
              queryParameters: queryParameters,
              data: _data,
            )
            .copyWith(
                baseUrl: _combineBaseUrls(
              _dio.options.baseUrl,
              baseUrl,
            ))));
    final value = DataClass.fromJson(_result.data!);
    return value;
}

I think that a variable that you define as String in the DataClass object appears as Map<String,dynamic> type in the service.


Delete this issue.

Sorry for being unprofessional. I accidentally opened the wrong tab

Haha sure ok :P Don't worry about, I barely know what I'm doing with github half the time


fix partial delete multi value index unexpected behavior

manual index command, DELETE FROM index: WHERE key =
was failing on composite key, when rid wasn't specified.
expected behavior, to remove all values under specified (partial/full) key
Use case:
CREATE INDEX index:test notunique string,string
INSERT INTO index:test (key,rid) values (['test','me'],#1:1)
INSERT INTO index:test (key,rid) values (['test','me'],#1:2)
DELETE FROM index:test where key = ['test']
SELECT FROM index:test
expected return 1 row
actual return 2 row
related to #2741

Thanks!


Stereo and RGB-D problems

Hi,when I run stereo and RGB-D examples,I face following problems:
OpenCV Error: Assertion failed (maxLevel >= 0 && winSize.width > 2 && winSize.height > 2) in calc, file /tmp/binarydeb/ros-kinetic-opencv3-3.3.1/modules/video/src/lkpyramid.cpp, line 1241 terminate called after throwing an instance of 'cv::Exception'   what():  /tmp/binarydeb/ros-kinetic-opencv3-3.3.1/modules/video/src/lkpyramid.cpp:1241: error: (-215) maxLevel >= 0 && winSize.width > 2 && winSize.height > 2 in function calc.
It seems that there is a problem reading the images. Please have you ever encountered this situation?

This project currently only supports monocular mode and does not provide adaptations for stereo and RGB-D.

This project currently only supports monocular mode and does not provide adaptations for stereo and RGB-D.

Thanks for your reply and look forward to more works.Do you have any related papers to introduce this project?


Disabling warnings about inline value attributes for v-model

Hi,
Forms generated by Phoenix HTML helpers have an inline value (like on Rails). I use Vue.js on those forms by creating the View Model data on the fly by introspecting the form inputs and values. I works fine but these warnings are no longer necessary in my case. I wonder if there could be a way to disable them?
To illustrate in this fork I used a new modifier named "nowarn" on v-model. I am not sure it's the best way to do it, but it works for me.

First off: You can disable all logs and warnings by setting Vue.config.silent = true. See here: https://vuejs.org/v2/api/#silent – But I understand that this is probably not what you want, because it will hide ALL warnings.
However, I would also welcome a way to exclusively turn off the warnings about the value attribute.
My use case is that I generate my HTML code with Python/Flask/WTForms. I only use Vue for some optional nice things, but would like to keep JavaScript as optional as possible. By using the value attribute, I can provide default values for everyone, not only people with JavaScript activated. I still provide an Object (with the same values) to Vue, so I don't need the warning.

This makes sense to me. IMO if the user explicitly uses v-model with provided data option, he should know by fact that the input should take its value from there instead of inline.


Block sync hangs at height of 220259

Notice that block hangs at height of 220259, so i update my node version form 1.2.0 to 1.2.2, and config all the new settings for SPORK_15 as mentioned in https://github.com/AXErunners/docs/blob/master/masternodes/setup.rst#id13, however it still hangs at 220259, should i remove all the block info stored before or just need to wait for some time?

yes, resync from the ground - this is due ongoing network upgrade


Imports clobber field names in locally defined structs

#import dep::{foo, bar}

struct Example {
    bar: u32,
}

fn test() {
    let example = Example(0u);
    foo(example.bar);
}

This code produces this error:
error: invalid field accessor `bar`
  ┌─ shaders/test.wgsl:9:39
  │
9 │     dep::foo(example.bar);
  │                                       ^^^ invalid accessor
  │
  = invalid field accessor `bar`

If I amend the code to not import a symbol named bar, the error goes away. But it took a lot more debugging than I'd have liked to figure out that that's what was happening.

That makes sense actually. It sounds like the current behavior is from https://github.com/bevyengine/naga_oil/pull/31? If there's already an exception carved out for identifiers following ., maybe an alternative here could be widening that exception to include identifiers preceding : (presumably, these are always struct members or function arguments)

That sounds like a better idea.

What about switch statements? They can also have a colon after a variable name.
switch foo {
  case bar: {       // Const-expression can be used in case selectors
    foo = 3;
  }
  default {
    foo = 4;
  }
}

Perhaps it’s best to explicitly disallow shadowing of modules with variables then.


Return proper REST API view status codes for project lock exceptions

It seems we raise the same locking exception in TaskflowAPI.run_flow() regardless whether the lock is active or if there's an unexpected problem, such as the Redis server being misconfigured or unavailable.
This is a problem because in e.g. ZoneSubmitMoveAPIView, we should return a different status based on what type of locking exception was encountered. The response should be 503 if the project is simply locked, or 500 if e.g. a Redis error occurs. Right now, we return APIException with the status of 500 in any case.
As this is a slightly breaking change for the REST API, I'm tentatively setting this for the v1.0 milestone.
This is related to #1842 and #1844.

 Exception handling in taskflow should be improved in the future, see #1505.


Bitwidth of datatypes should be an immutable property or name should change on assignment

On the current master:
In [1]: from numba.core import types

In [2]: int16 = types.Integer.from_bitwidth(16)

In [3]: int16.bitwidth = 32

In [4]: int16.name
Out[4]: 'int16'

In [5]: int16.bitwidth
Out[5]: 32

The problem is, that name includes the bitwidth as it was at creation. If the bitwidth is assigned later it is not updated.

Thanks for the report. Whilst this is not great, I'm wondering what the context is for doing this?

@stuartarchibald  Upcasting an existing Integer datatype coming from some type determination algorithm to avoid overflows.
This seemed like the simplest option before I realized there was a problem with this approach... I was surprised that I could do something that probably has "very bad" effects down the line.

for the record: same problem with datetime64 and timedelta64

Thanks, task here is to make these properties.


bdr:G162 bdo:placeType bdr:PlaceTypeDgonPa

see http://purl.bdrc.io/resource/G162.ttl
it has bdo:placeType  bdr:PlaceTypeDgonPa
not in possible values for http://purl.bdrc.io/ontology/core/PlaceType

Yes the proper type is bdr:PT0037. Now to find where the problem is.
It seems that PlaceMigration.java is using an old resource ids of PlaceTypes rather than the current resource ids like bdr:PT0037
So currently none of the :placeType values in bdrcrw are in sync with the ontology. For example, bdr:G601 shows bdr:PlaceTypeGrongTsho instead of bdr:PT0084
If the current resource ids in the ontology are used in the 55K+ :Places what is going to break?

I think it's safe to proceed with the change in the migration


Feature request: Order mv list output alphabetically

Spigot 1.13.2
MV-Core 2.7.0-SNAPSHOT-b747
>mv list
[22:58:17 INFO]: ====[ Multiverse World List ]====
[22:58:17 INFO]: minigames - NORMAL
[22:58:17 INFO]: yellowdog - NORMAL
[22:58:17 INFO]: skyblock-the-end - THE_END
[22:58:17 INFO]: void - NORMAL
[22:58:17 INFO]: skyblock-nether - NETHER
[22:58:17 INFO]: luckyblock - NORMAL
[22:58:17 INFO]: parkour - NORMAL
[22:58:17 INFO]: skyblock - NORMAL
[22:58:17 INFO]: playground-the-end - THE_END
[22:58:17 INFO]: playground - NORMAL
[22:58:17 INFO]: playground-nether - NETHER
[22:58:17 INFO]: yellowdog-nether - NETHER
[22:58:17 INFO]: lobby - NORMAL
[22:58:17 INFO]: city - NORMAL
[22:58:17 INFO]: city-nether - NETHER

would be more user-friendly if it were
>mv list
[22:58:17 INFO]: ====[ Multiverse World List ]====
[22:58:17 INFO]: city - NORMAL
[22:58:17 INFO]: city-nether - NETHER
[22:58:17 INFO]: lobby - NORMAL
[22:58:17 INFO]: luckyblock - NORMAL
[22:58:17 INFO]: minigames - NORMAL
[22:58:17 INFO]: parkour - NORMAL
[22:58:17 INFO]: playground - NORMAL
[22:58:17 INFO]: playground-nether - NETHER
[22:58:17 INFO]: playground-the-end - THE_END
[22:58:17 INFO]: skyblock - NORMAL
[22:58:17 INFO]: skyblock-nether - NETHER
[22:58:17 INFO]: skyblock-the-end - THE_END
[22:58:17 INFO]: void - NORMAL
[22:58:17 INFO]: yellowdog - NORMAL
[22:58:17 INFO]: yellowdog-nether - NETHER

What is the current reasoning behind how worlds get sorted? It is so annoying having them mixed at random, even if you import them in a specific order. Even more so, if you try and edit the worlds.yml file to manually sort them, they reset back to the "random" order.

Another vote for alpha sort. This should include /mv list as well as the api for plugins like dynmap so that worlds are sorted there as well.

Ah yes, dynmap is also affected by this. Iirc you can fix it on the dynmap side by manually rearranging the generated web files, but again, still a pain. Please add alphabetical sort!

It might be as easy as adding a sort(compareByAlias) to getMVWorlds() with something like:
Collection<MultiverseWorld> compareByAlias = new Comparator<MultiverseWorld>() {
    @Override
    public int compare(MultiverseWorlds a, MultiverseWorld b) {
        return a.getAlias().compareTo(b.getAlias());
    }
};


Use https instead of http

Avoids security error on https://istio.io/

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

#287 will cleanup to copy pasta/duplication in those 3 files


Option type handling regression in 8.0.1

In upgrading from click 7.1.2 to 8.0.1, our click-based CLI started failing with type errors. We have click options whose default values are classes, and as of 8.0.1 they're being converted to strings.
This script is able to reproduce the behavior change:
import click

class Class1:
    pass

class Class2:
    pass

@click.command()
@click.option("--cls1", "config_cls", flag_value=Class1, default=True)
@click.option("--cls2", "config_cls", flag_value=Class2)
def test(config_cls):
    print(config_cls)
    print(type(config_cls))

if __name__ == "__main__":
    test()

Behavior with click 7.1.2:
# pip freeze | grep click
click==7.1.2
# python test.py
<class '__main__.Class1'>
<class 'type'>

Behavior with 8.0.1:
# pip freeze | grep click
click==8.0.1
# python test.py
<class '__main__.Class1'>
<class 'str'>

The type of config_cls should be the class we specified, not 'str'.
Environment:

Python version: 3.9
Click version: 8.0.1

This seems to have already appeared in the 8.0.0 version.
Ran into this myself using enum member as the flag_value.

Had the same issue and just adding a type to the click options fixed it for me.

We've stumbled across this same issue. And I'm a bit confused.
Looking at the docu, which states

Changed in version 8.0.1: type is detected from flag_value if given.

I would expect some behavior along the lines of
if type is MISSING:
   type = type(flag_value)

However reading davidism comment and looking at https://github.com/pallets/click/blob/2996d3c11972ad1d71339481f2119495185e7d8d/src/click/types.py#L959
this only hold true, if the autoguessed type is one of str, int, float, bool. If that is the intended behavior I think the documentation should state so, as I find it very surprising.
However I think, in the case of flag_value I would simply expect click not to touch that all and simply pass it back to me.


feat(authOriginPull): adding authenticated origin pull

PR summary

Fixes: <! -- link to issue -->
PR Checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] New tests
[ ] Build/CI related changes
[ ] Documentation content changes
[ ] Other (please describe)

What is the current behavior?

What is the new behavior?
  feat: Authenticated Origin Pull

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

:tada: This PR is included in version 0.26.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


problems in safari

Hi there, we're having issues using the fetch-client library in safari. It fails as soon as we try to configure the client, please have a look @ http://embed.plnkr.co/wc2GDF for a basic sample. We also tried to configure the library using property setters instead of passing in a lambda expression, but then any subsequent "fetch" operation fails.
Thanks,
Javier.

@bryanrsmith Could this be related to a missing polyfill? We should find a better way to handle that if it's the case. One solution is to make fetch depend on the polyfill, then implement it as an aurelia plugin..with the plugin's configure method detecting whether native fetch is present of not and loading the polyfill if appropriate. If we don't do that, we should definitely make sure to have very clear documentation on it.

Yep. @javier-troconis-q2 the Fetch API isn't yet supported in Safari, so you'll need to include a polyfill like https://github.com/github/fetch. The aurelia fetch library doesn't include the polyfill at this time.
@EisenbergEffect What do you think is the best way to handle this? I originally left out the polyfill because 1) some environments (electron apps, for example) don't need it, and 2) polyfill implementations differ between node & the browser. If we add a dependency on a browser polyfill it won't work in node. There are universal polyfills, but they're larger... Do you think it's acceptable to just document the need for a polyfill? It should be pretty easy to detect lack of support for fetch & log a helpful message to the console.

Let's start with the warning message. That will at least help people out in the mean time. I'm not quite sure what real solution should be yet. I know that we do want to support both client and server, especially since we want to have "universal" JS in the end. How much larger are the polyfills that cover both node and browser?

+1

So to be clear, using the https://github.com/github/fetch with Aurelia-http-fetch is supported?
Additionally, the TypeScript definition for this project lacks references to some obejcts (Request, Response, BufferSource, URLSearchParams,) which if used with whatwg-fetch.d.ts (DefinitelyTyped) has collisions/conflicts.  Some comments, documentation, guidance and/or suggestions would greatly help.
It seems Http-Client stopped working on many mobile device browsers which is what has prompted my research on this project instead.

The http client stopped working?! What is wrong with that? @bryanrsmith

iOS devices use mobile Safari. Since aurelia-http-fetch is not working with Safari, the mobile devices are broken as well. It works in Chrome but not Safari and Firefox. As a workaround, I’m using the fetch polyfill as a replacement.

On Sep 4, 2015, at 1:46 PM, Rob Eisenberg<EMAIL_ADDRESS>wrote:
The http client stopped working?! What is wrong with that? @bryanrsmith https://github.com/bryanrsmith
—
Reply to this email directly or view it on GitHub https://github.com/aurelia/fetch-client/issues/13#issuecomment-137818387.

Ok I think I got confused. You are just referring to the fact that it's broken without the polyfill. Is that correct?

Correct. At least in my case. I believe this is the situation for @KarlDirck as well.

The aurelia-http-client issue was observed on Android and iOS on Chrome and iOS mobile Safari.  I am happy to help provide more information, if needed.

Additionally, I am trying to confirm if the aurelia-fetch-client would have maximum compatibility if used WITH the fetch polyfil from github referenced above.  We have an immenent demo on iO (iPhone) that has to work by COB Tuesday.
Thanks.

Yes. I can confirm the polyfill works on mobile and desktop browsers.

On Sep 4, 2015, at 6:22 PM, Karl Dirck<EMAIL_ADDRESS>wrote:
Additionally, I am trying to confirm if the aurelia-fetch-client would have maximum compatibility if used WITH the fetch polyfil from github referenced above. We have an immenent demo on iO (iPhone) that has to work by COB Tuesday.
Thanks.
—
Reply to this email directly or view it on GitHub.

@KarlDirck, just add "import 'fetch';" to the list of imports of your app.js. Also, make sure you have a fetch polyfill installed (https://github.com/github/fetch).

Thank you.

Sorry for such a newbie question, but could someone give me a helping hand on how to include the fetch polyfill (and only if it's needed), and where this code should go inside an Aurelia app?

@jeff-h No problem! You can find instructions at https://github.com/aurelia/fetch-client/tree/master/doc#bring-your-own-polyfill. You can import the polyfill anywhere you like, as long as it's loaded before you try to use aurelia-fetch-client. That could be somewhere like main.js, or it could be in the specific view model or service module that uses aurelia-fetch-client.

Awesome! Thanks for that, and getting back so quickly! Those docs are exactly what I was hoping for. I didn't even go looking for docs in the fetch-client repo honestly — primarily because I am still being caught by surprise at the extent of the docs already in Aurelia :)


New contamination overlap fails on the web-version with MIRI-LRS or NIRCam

Hi folks,
When trying the new contamination overlap implemented by @jaymedina in our test server, the code fails to perform the calculation for MIRI or NIRCam (works for SOSS!) with the following error:

We reviewed this briefly with @mfixstsci, @hover2pi and @bourque --- this might be an issue with the actual web app perhaps, but we are not sure. Currently @mfixstsci and @hover2pi looking into this, but would be good to know if @jaymedina has any ideas on why this is not working!
N.

As an update to this: it seems the contamination overlap code is trying to find files that are not on our ExoCTK data files. @jaymedina contacted us internally confirming this, and files will be moved. They have to be added to the Box folder as well!

Posting my e-mail reply here for record-keeping:
I’m almost certain this is because the new data has not been moved! I modified the NIRCam traces to put them in the correct orientation. The new exoctk_contam data lives here: /user/jmedina/exoctk_data/exoctk_data/exoctk_contam/traces
[...]
Please keep me updated on your progress! I will ramp back up on science as soon as I can.
Best,
Jenny

All right, this has been fixed!