Error with Rimatomics Compatability

I was hosting a game with the following mods enabled In this order: (creator)
Hugslib (unlimitedhugs) , miscellaneous ‘CORE’ (Haplo_X1),  modmanager (Fluffy),  jecstools (jecrell),  morevanilla turrets extension pack (XeoNovaDan), Expanded prothsthetics and organ engeneering (Ykara), more trade ships (pinochemicali), [XND] Turret Extension (XeoNovaDan), embrasure (brunayla), morevanillafactions (avis), glittertech (Sam_), increase stack (taveron), rimatomics (dubwise), [kv] trading spot - 1.0 (kiame vivacity), edb prepare carefully (edbmods),  morevanillaturrets 1.0 (paradox), farmable neutroamine (nanonator).
Two (2) friends and I were playing when I finished Rimatomics nuclear power and went to interact with the command console for the reactor. When I interacted with the command console and the panel for its control popped up everyone, including myself, desynched with the error stating "incorrect random map state 0".


MS Partners do not have access to C2R-P keys

We have 5 Visio licenses because we are Microsoft Partner, but we do not have access to VLSC. I already spent hours on the phone with different MS support departments. Conclusion:
Partner support is unable to generate these C2R-P keys and unwilling to help on this subject.
VLSC support is able to generate the keys, but requires a volume license contract number. (which we don't have, because as MS Partner we did not bought a volume license)
This really sucks!

Dokumentdetails
⚠ Bearbeiten Sie diesen Abschnitt nicht. Er ist für die Verknüpfung von docs.microsoft.com zum GitHub-Artikel erforderlich.

ID: 1e6c0641-503d-7959-2afb-839821cc792f
Version Independent ID: 046c52d9-4fbe-4fe7-0778-5c1d4138f69e
Content: Verwenden des Office-Bereitstellungstools zum Installieren von Volumenlizenzeditionen von Visio 2016 und Project 2016
Content Source: DeployOffice/use-the-office-deployment-tool-to-install-volume-licensed-editions-of-visio-2016.md
Service: o365-proplus-itpro
GitHub Login: @DHB-MSFT
Microsoft Alias: danbrown

I'm trying to get clarification/confirmation about what partners should be able to get for this scenario.

Thanks simon-baer, we have the same question and problem. Rolling out Office 365 to all employees and therefor have the need for Visio ODT installation but can not use our MPN benefits. Very annoying situation...

Sorry for the delay in responding. I've been able to confirm that C2R-P keys are only available from the VLSC. I have forwarded on your comments/feedback to the appropriate team. I recognize this situation is a source of frustration for you. Please know that our product and program teams take this feedback seriously, and it has been added as evidence for potential future improvements to the program.  Thank you again for your comments/feedback.

@DHB-MSFT, we 10 months further, is there already an option for an MS partner to get C2R-P keys based on IUR benefits?

@gkienhuis  / @simon-baer
We cloud activate Visio Professional 2016 with our partner keys by creating our own c2r installation media with office deployment tool, see: https://docs.microsoft.com/de-de/deployoffice/use-the-office-deployment-tool-to-install-volume-licensed-editions-of-visio-2016 using ID "VisioProXVolume"

@MatthiasLaechele thanks for sharing your experience, gone try to do the same.


Introduce alternative, slightly more efficient version of fetchpriority opportunity query

This query is a slightly more efficient version of the query introduced in #15. The results are pretty much the same, except for some extremely small differences that are natural given that one uses the overall table while this one uses the monthly tables.
One thing to note is that for now this query is set for October 1, 2022 results instead of November 1, 2022, since for some reason HTTP Archive is currently still missing the mobile results for November. That shouldn't matter too much though, we can always rerun the query later for a newer dataset.
This version of the query is heavily inspired by https://discuss.httparchive.org/t/lazy-loaded-lcp-images-by-wordpress-version/2455/2.
Comparing the two queries in terms of efficiency (when running both queries against the October dataset), both take roughly the same time to complete. However this query consumes only 4.18 TB while the other one consumes 7.91 TB.
This PR does not overwrite the original query as it is worth keeping both versions for reference.
Query results

Row
client
with_fetchpriority_on_lcp
without_fetchpriority_on_lcp
total_with_lcp
total_wp_sites
pct_opportunity
pct_overall_opportunity

1
desktop
284
1503490
1503774
3502837
0.99981114183381281
0.42922065742710835

2
mobile
337
2091778
2092115
5465547
0.99983891898867894
0.382720704

For comparison, the results for the query from #15 for the same month are:

Row
client
with_fetchpriority_on_lcp
without_fetchpriority_on_lcp
total_with_lcp
total_wp_sites
opportunity
overall_opportunity

1
desktop
284
1504820
1505104
3505796
99.981 %
42.924 %

2
mobile
337
2092862
2093199
5468298
99.984 %
38.273 %

Based on October 2022 dataset

@kt-12 Reviewed https://discuss.httparchive.org/t/lazy-loaded-lcp-images-by-wordpress-version/2455 today and tried to use that approach for an alternative version of your fetchpriority query. Here's the result.
TLDR it is slightly more efficient, results are almost the same. I think we should keep both for reference purposes, it shows two different ways to achieve a similar goal.

@kt-12 Reviewed https://discuss.httparchive.org/t/lazy-loaded-lcp-images-by-wordpress-version/2455 today and tried to use that approach for an alternative version of your fetchpriority query. Here's the result.
TLDR it is slightly more efficient, results are almost the same. I think we should keep both for reference purposes, it shows two different ways to achieve a similar goal.

Thanks @felixarntz. I happened to review the exact same query today for another task. It makes more sense as we don't have to traverse a very large table or do join with the technologies table just to know if it's a WordPress site.
The same logic can be extended while working with the Lighthouse report. Lighthouse report has "stackPacks" array and the very first object if it was a WordPress site is of WordPress. We can use this to avoid joining with another table
    "stackPacks": [
        {
            "id": "wordpress",
            "title": "WordPress",


Electricity generation data validation script

Closes # (if applicable).
Changes proposed in this Pull Request

Checklist

[✓] I tested my contribution locally and it seems to work fine.
[✓] Code and workflow changes are sufficiently documented.
[ ] Changed dependencies are added to envs/environment.yaml.
[ ] Changes in configuration options are added in all of config.default.yaml.
[ ] Changes in configuration options are also documented in doc/configtables/*.csv.

Nice! @nomineb Can you revert the changes to

config.default.yaml - let's leave this as is.
solve_network.py - probably best we hold off on the transport model for now. Do keep the script somewhere for later use.
data_validation.ipynb - I think you can move this to pypsa-usa/notebooks and it should be ignored auotmatically?


Unable to install the Firebase iOS SDK (9.0.0) through SPM in xcode 14.1

Description
I have ios project which work fine in xcode 13.4.1, To release this application, it is require to check it in xcode 14.1 to give support of ios 16, so I have downloaded new xcode 14.1 and open existing application in it. when I build the project, it gives me lots of fire base related error. so I remove added firebase ios sdk  and add it again.
I tried to add firebase ios sdk in xcode 14.1 project using SPM, every time it show pop up with message "Communication with the service was interrupted ". It works fine in xcode 13.4.1

I had created new project and had tried to add firebase ios sdk, got same error.
Reproducing the issue
No response
Firebase SDK Version
9.0.0
Xcode Version
14.1
Installation Method
Swift Package Manager
Firebase Product(s)
All
Targeted Platforms
iOS
Relevant Log Output
No response
If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

Replace this line with the contents of your Podfile.lock!

Thanks for reporting, @shraddha-crest. I'm unable to reproduce the issue on Xcode 14.1.  I also found a solution here which might fix the issue.

Thanks for reporting, @shraddha-crest. I'm unable to reproduce the issue on Xcode 14.1.  I also found a solution here which might fix the issue.

@rizafran Thanks for replay, Yes i did all the things you mention in replay, even I delete gitconfig file and build application. It did not fix the issue.

Are you able to git clone git@github.com:firebase/firebase-ios-sdk.git in the command line outside of Xcode?

Yesterday, I downloaded Xcode14.2 and open my existing application in it and firebase-ios-SDK works fine in it.
I don't know why it is not working in Xcode14.1 but works fine in 14.2. it solved my problem.
Thanks for your support and immediate replay.

Thanks for the update, @shraddha-crest. Good to know that it's working on 14.2. If the issue arises, feel free to comment to reopen the ticket.


Issues building on ARM platform

I'm trying to build parity (ethereum client written in rust) on a Raspberry Pi using rustc 1.7.0-a5d1e7a59 (stable). First problem was seeing that mio depends on nix prior to 0.5.0, which has been fixed and now compiles properly on ARM using rustc 1.7.0.
So I attempted to checkout the source for mio from git, and bump the dependency on nix manually to 0.5.0.
This does fix it, but now the same build error occurs in mio (same as in same errors shown on nix before 0.5.0):
   Compiling mio v0.5.0 (file:///usr/src/mio)
src/sys/unix/uds.rs:53:86: 53:87 error: mismatched types:
 expected `nix::sys::socket::consts::os::MsgFlags`,
    found `_`
(expected struct `nix::sys::socket::consts::os::MsgFlags`,
    found integral variable) [E0308]
src/sys/unix/uds.rs:53         let msg = try!(nix::recvmsg(self.io.as_raw_fd(), &iov, Some(&mut cmsgspace), 0)
                                                                                ^
src/sys/unix/uds.rs:53:19: 54:60 note: in this expansion of try! (defined in <std macros>)
src/sys/unix/uds.rs:53:86: 53:87 help: run `rustc --explain E0308` to see a detailed explanation
src/sys/unix/uds.rs:72:57: 72:58 error: mismatched types:
 expected `nix::sys::socket::consts::os::MsgFlags`,
    found `_`
(expected struct `nix::sys::socket::consts::os::MsgFlags`,
    found integral variable) [E0308]
src/sys/unix/uds.rs:72         nix::sendmsg(self.io.as_raw_fd(),&iov, &[cmsg], 0, None)
                                                                               ^
src/sys/unix/uds.rs:72:57: 72:58 help: run `rustc --explain E0308` to see a detailed explanation
error: aborting due to 2 previous errors
       error Could not compile `mio`.

To learn more, run the command again with --verbose.

The description for the error message is as follows.

This error occurs when the compiler was unable to infer the concrete type of a
variable. It can occur for several cases, the most common of which is a
mismatch in the expected type that the compiler inferred for a variable's
initializing expression, and the actual type explicitly assigned to the
variable.
For example:
let x: i32 = "I am not a number!";
//     ~~~   ~~~~~~~~~~~~~~~~~~~~
//      |             |
//      |    initializing expression;
//      |    compiler infers type `&str`
//      |
//    type `i32` assigned to variable `x`

Another situation in which this occurs is when you attempt to use the try!
macro inside a function that does not return a Result<T, E>:
use std::fs::File;

fn main() {
    let mut f = try!(File::create("foo.txt"));
}

This code gives an error like this:
<std macros>:5:8: 6:42 error: mismatched types:
 expected `()`,
     found `core::result::Result<_, _>`
 (expected (),
     found enum `core::result::Result`) [E0308]

try! returns a Result<T, E>, and so the function must. But main() has
() as its return type, hence the error.

I'm not familiar enough with rust to craft a patch, but hope this is not a too horrible thing to track down (really looking forward to trying this client on my Pi).
Br, Ian J.

@ijohanne  -  is this still an issue?   Mio 0.5.0 depends on Nix 0.5.0 by default and there doesn't appear to be the type mismatch in uds.rs.

Looks like you might to do something like this:
fn some_func() -> io::Result<()> {
    some_code_here;
    Ok(()).unwrap()
}

The Ok (()) contains a () type, so if you unwrap the Ok(()), you should get () as the return type!

use std::io;
use std::fs::File;
use std::path::Path;
use std::io::prelude::*;

fn main() {
    some_function().unwrap();
}

fn some_function() -> io::Result<(())> {
    let foo_path = Path::new("foo.txt");

    let mut buffer = try!(File::create(foo_path));

    let bar_text = String::from("Hello World!");

    try!(buffer.write_all(bar_text.as_bytes()));

    Ok(())
}

This will work because the function returns an io::Result<(())> which contains the () type.
This result Ok (()) needs to be unwrapped in order to have the function return the () inside of main.
Hope this helps!

I think this should hopefully be fixed on master, so I am going to close this. However, I do not have an ARM setup on which I can test this. I will need help figuring out the issue as, again, I don't have access to an ARM setup.
If anyone depends on mio + ARM, I would appreciate some help setting up CI for arm environments :)


Support vertical preview panel right to content pane

Vertical preview panel right to the content pane uses available screen space much better.

As of 1.1.3, it is now possible to detach the preview pane from the editor into a separate window. This is  extremely useful with a second monitor. Implementing a vertical panel next to the editor pane is still not officially supported and will definitely cause conflicts with other extensions trying to do the same.

Cool!

Closing the issue. Brackets still does not really provide a clean way to implement extensions with a vertical window. Using a detached preview pane should be good enough for now.

Any update on it yet?

Unfortunately, I did not find a good way in Barckets to implement this and therefore gave up on this. However, you can just detach the bottom pane and use the detached window by placing it right or left the of Brackets editor window.


[SPARK-42270][SQL] Sort merge join may oom when right match rows are very large

What changes were proposed in this pull request?
Sort merge join may oom when right match rows are very large.
Why are the changes needed?
Improve the stability for SortMergeJoin
Does this PR introduce any user-facing change?
No
How was this patch tested?
Exists UT

The pr title is more suitable for Jira. Could you change it from the work and goal of pr instead?


Set maxNumberOfFiles anywhere outside the uploader instantation

Hi,
I have my own custom jquery code which is outside the uploader instance, and i would like to access the maxNumberOfFiles value there, and be able to modify it too. Is there any way I can do this?
Thanks!

You can access and modify it the same way you can access and modify jQuery UI options:
// Get:
var max = $('#fileupload').fileupload('option', 'maxNumberOfFiles');
// Set:
$('#fileupload').fileupload('option', 'maxNumberOfFiles', 10);

Thank you! Much appreciated :)


GitHub version vs crates.io + sections mutable borrow API

The version on GitHub is
version = "0.27.5"

while the latest on crates.io:
parity-wasm = "0.27.6"

Does that include any code that's not on GitHub?
Also, are there plans to publish sections mutable borrow API https://github.com/paritytech/parity-wasm/commit/d1a74151e1cada759fdf6ae807ee54c10d6308b7 any time soon?
That would allow me to clean up a lot of code. I've been using latest parity-wasm from GitHub but would prefer to simply use a version from crates.io.

0.28 is out!


Add fixit testing for optional-to-any coercion warning.

Test a couple of the warnings to ensure that the fixits are placed properly.

@swift-ci Smoke test and merge.


Add support for generic system IPv4/6 loopback pools

Looks good.
should we rename these to IPv4/IPv6 from ip4/ip6?


added opt-out for autotune

Autotune is still experimental so I think it would be good to provide the possibility to opt-out (I personally would like this for testing purposes).

I am a bit unsure, about this. I think we should definitely give people the opportunity to customize this, but at least for autotuning TensorFlow datasets actually uses autotuning under the hood as well so this flag might be a bit confusing. I'll take a closer look at this tomorrow.

Closing this for now, until we can come up with a general solution.


Add support for other platforms with libpopcnt

Introduces a new header only library libpopcount from https://github.com/kimwalisch/libpopcnt
Just dropping in this library for all platforms reduced performance on Linux (as measured by throughput in the anonlink.benchmark), so I've  new path through dice_one_against_many.cpp for the MSVC compiler to use - attempting to pass larger buffers to popcnt so it can take advantage of AVX2 etc.
With this addition anonlink installs and passes all tests on Windows. Performance isn't as good as Linux - about half the speed.
I'll follow with a separate PR for building and publishing binary wheels for Windows.
Benchmarks
Measured on my laptop (native OS is Windows, and Linux measurements via the Linux subsystem for Windows).
Windows
Anonlink benchmark -- see README for explanation
------------------------------------------------

Threshold: 0.5
Size 1 | Size 2 | Comparisons      | Total Time (s)          | Throughput
       |        |        (match %) | (comparisons / matching)|  (1e6 cmp/s)
-------+--------+------------------+-------------------------+-------------
  1000 |   1000 |    1e6  ( 0.00%) |  1.341  (58.6% / 41.4%) |     1.272
  2000 |   2000 |    4e6  ( 0.00%) |  6.238  (51.9% / 48.1%) |     1.236
  3000 |   3000 |    9e6  ( 0.00%) | 16.158  (46.5% / 53.5%) |     1.197
  4000 |   4000 |   16e6  ( 0.00%) | 29.770  (43.8% / 56.2%) |     1.227

Threshold: 0.7
Size 1 | Size 2 | Comparisons      | Total Time (s)          | Throughput
       |        |        (match %) | (comparisons / matching)|  (1e6 cmp/s)
-------+--------+------------------+-------------------------+-------------
  1000 |   1000 |    1e6  ( 0.00%) |  0.021  (99.1% /  0.9%) |    48.739
  2000 |   2000 |    4e6  ( 0.00%) |  0.071  (99.4% /  0.6%) |    56.741
  3000 |   3000 |    9e6  ( 0.00%) |  0.174  (99.4% /  0.6%) |    52.114
  4000 |   4000 |   16e6  ( 0.00%) |  0.283  (99.0% /  1.0%) |    57.061
  5000 |   5000 |   25e6  ( 0.00%) |  0.420  (99.2% /  0.8%) |    59.928
  6000 |   6000 |   36e6  ( 0.00%) |  0.626  (99.2% /  0.8%) |    57.932
  7000 |   7000 |   49e6  ( 0.00%) |  0.833  (99.1% /  0.9%) |    59.350
  8000 |   8000 |   64e6  ( 0.00%) |  1.058  (98.8% /  1.2%) |    61.259
  9000 |   9000 |   81e6  ( 0.00%) |  1.377  (99.2% /  0.8%) |    59.291
 10000 |  10000 |  100e6  ( 0.00%) |  1.696  (99.1% /  0.9%) |    59.507
 20000 |  20000 |  400e6  ( 0.00%) |  6.755  (99.1% /  0.9%) |    59.763

Linux
Anonlink benchmark -- see README for explanation
------------------------------------------------

Threshold: 0.5
Size 1 | Size 2 | Comparisons      | Total Time (s)          | Throughput
       |        |        (match %) | (comparisons / matching)|  (1e6 cmp/s)
-------+--------+------------------+-------------------------+-------------
  1000 |   1000 |    1e6  ( 0.00%) |  1.197  (52.2% / 47.8%) |     1.601
  2000 |   2000 |    4e6  ( 0.00%) |  5.230  (47.2% / 52.8%) |     1.620
  3000 |   3000 |    9e6  ( 0.00%) | 15.155  (42.5% / 57.5%) |     1.399
  4000 |   4000 |   16e6  ( 0.00%) | 55.438  (65.1% / 34.9%) |     0.444

Threshold: 0.7
Size 1 | Size 2 | Comparisons      | Total Time (s)          | Throughput
       |        |        (match %) | (comparisons / matching)|  (1e6 cmp/s)
-------+--------+------------------+-------------------------+-------------
  1000 |   1000 |    1e6  ( 0.00%) |  0.017  (98.7% /  1.3%) |    58.244
  2000 |   2000 |    4e6  ( 0.00%) |  0.051  (99.2% /  0.8%) |    78.589
  3000 |   3000 |    9e6  ( 0.00%) |  0.103  (99.2% /  0.8%) |    88.180
  4000 |   4000 |   16e6  ( 0.00%) |  0.177  (99.2% /  0.8%) |    90.987
  5000 |   5000 |   25e6  ( 0.00%) |  0.262  (99.0% /  1.0%) |    96.208
  6000 |   6000 |   36e6  ( 0.00%) |  0.396  (98.9% /  1.1%) |    91.916
  7000 |   7000 |   49e6  ( 0.00%) |  0.606  (99.1% /  0.9%) |    81.576
  8000 |   8000 |   64e6  ( 0.00%) |  0.651  (99.1% /  0.9%) |    99.271
  9000 |   9000 |   81e6  ( 0.00%) |  0.831  (98.7% /  1.3%) |    98.701
 10000 |  10000 |  100e6  ( 0.00%) |  1.067  (98.8% /  1.2%) |    94.876
 20000 |  20000 |  400e6  ( 0.00%) |  4.191  (98.9% /  1.1%) |    96.514

@nbgl you might be interested in making fun of my C. Any suggestions are most welcome.

I've just merged this in, but happy to revisit if anyone has feedback.


unknown flag: --missing-hash-policy

Which version of the AzCopy was used?
10.17.0
Note: The version is visible when running AzCopy without any argument
Which platform are you using? (ex: Windows, Mac, Linux)-
Windows
What command did you run?
azcopy sync
Note: Please remove the SAS to avoid exposing your credentials. If you cannot remember the exact command, please retrieve it from the beginning of the log file.
What problem was encountered?
unknown flag: --missing-hash-policy
How can we reproduce the problem in the simplest way?
Add the flag: --missing-hash-policy
Have you found a mitigation/solution?
It seems this is not working but it is mentioned in the changelogs of version 10.17.0
Is something missing?

Oh, sorry, this accidentally made it into the change log. Missing hash policy was removed shortly before the work was merged in, as it didn't feel especially intuitive to have to opt-in to hashing for local files when working with the hash based sync feature.

Ok that makes sense but then i have a follow-up question.
Knowing most files are not hashed if they are bigger the 250MB then what will azcopy do?
One of the most usefull cases i found personally is that you can copy two remote blob storages as you don't need to duplicate the data locally. But i have been struggling to make sure all files are hashed and verified.
The hash generate part seemed promising as it would create a way to always have the files MD5 hashed no?
If you have any other advice to make sure I can verify all files i'm happy to have advice there as well :)


Fix "occured" -> "occurred" typos

See: https://tinyurl.com/occured

Codecov Report

Merging #2761 into canary will decrease coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           canary    #2761      +/-   ##
==========================================
- Coverage    13.9%   13.89%   -0.02%
==========================================
  Files         262      262
  Lines       10570    10558      -12
  Branches     1366     1365       -1
==========================================
- Hits         1470     1467       -3
+ Misses       8951     8942       -9
  Partials      149      149

Impacted Files
Coverage Δ

src/commands/deploy/latest.js
0% <ø> (ø)
:arrow_up:

src/util/dev/server.ts
62.48% <100%> (ø)
:arrow_up:

src/util/dev/builder-cache.ts
74.86% <0%> (+1.5%)
:arrow_up:

src/util/dev/router.ts
83.33% <0%> (+4.76%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ef793bf...46679ac. Read the comment docs.


cargo-vet skeleton mvp

hacky hacky hacky

Went through the book again and got schemas/apis to match things to the best of my understanding.
Lots more explicit TODOs added for stuff I don't do yet.
Error handling still a mess (experimenting with some new stuff, feeling out what approaches I like, so kinda doing random stuff all over the place. Also mildly enticed to mess around with color-eyre but not sure it's right for this project...).

Also see https://github.com/Gankra/cargo-vet#cargo-vet for rendered CLI docs

Updates:

removed Vetted.lock
removed forbid command
kinda-WIP pivot to using registry cache (problems now shifted from "we explode on multiple versions of the same package" to "we completely fail to actually pull down anything you ask about unless it happens to be in your cargo.lock/cargo.toml"

Also I'm still not implementing the "find the closest audited/allowed package to the current version" logic I mentioned in #13, so anything other than a "0.0.0 => now" will uh... Not Work.
That's next on my plate.

NB suggest is still pretty heavyweight since just... diffing 200 crates is still just a ton of disk access and non-trivial work, even for git diff!
I know this "smoothes out" over time as you mark things as suggest=false and just review them and maybe we cache results and whatnot, but it's... not a great first run UX? (and also useless to do in a CI vet?)

Or wait, hold on there's kind of 2 suggests isn't there?

suggest what to fix when vet fails
suggest what to audit to just clear up your unaudited backlog

no?

Pushed up: new vet resolution algorithm that is criteria-aware and maps in foreign criteria. current caveats:

local dependency_criteria not yet implemented

need to make sure the array is properly sorted for dependency resolution first

foreign dependency_criteria not yet implemented (see #16)
foreign criteria are mapped immediately, and all resolution is performed in local terms

this can result in "problem b" in https://github.com/bholley/cargo-vet/issues/16#issuecomment-1099133351

policy is not actually checked

I don't think it's tricky/interesting, just haven't looked at it

implies is not actually applied yet

literally forgot it exists until I started writing this comment lol

Most of this is noted in TODOS

Pushed up dependency_criteria / dependency-order resolution. Checked in some test data just to make sure things weren't completely broken... this is getting complex enough that I desperately need to write the testing framework.

NB while I'm still thinking through foreign dep_criteria, I am currently unconditionally setting that stuff to "default" (and aborting if custom criteria is set). More work to do here, but should vaguely do the right thing in defaulted bijective cases.


[groovy 2.3.9] cannot build, bad sha256 hash

When I try to install groovy I get the following
$ nix-env --install groovy
...
/nix/store/vid0qvzarq5frzwdqnjg4nhhkal4sqpn-curl-7.39.0/bin/curl-config: interpreter directive changed from " /bin/sh" to "/nix/store/8a0sc9nhmx273mmrf0pxs9jkbwac58qi-bash-4.3-p30/bin/sh  "
building path(s) ‘/nix/store/p85gzy67x98fnr1y2i9f22528izpjj0w-groovy-binary-2.3.9.zip’

trying http://dl.bintray.com/groovy/maven/groovy-binary-2.3.9.zip
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 31.4M  100 31.4M    0     0  16.5M      0  0:00:01  0:00:01 --:--:-- 18.2M
output path ‘/nix/store/p85gzy67x98fnr1y2i9f22528izpjj0w-groovy-binary-2.3.9.zip’ should have sha256 hash ‘1lk942v7gd3ism4cw8gqk9ndr6yjwkgxc55z7p366khiv8d4f608’, instead has ‘069nsmas1bdzdcd06mz9zw1zrzmfdhpsr4l4y0v9ilw4pchd2h48’
cannot build derivation ‘/nix/store/px9a3s3y1l7f57lr6231vxxf8vq8v6nc-groovy-2.3.9.drv’: 1 dependencies couldn't be built

Tried using the last version in 14.12 channel but doesn't seem that this worked still.
$ nix-channel --add http://nixos.org/releases/nixos/14.12/nixos-14.12.335.676e8d7/ nixpkgs-14.12
$ nix-channel --update
$ nix-end -i groovy-2.3.8
...
loading initial cache file /private/var/folders/qh/f4d7nfz93tg5fcj3t261f9f40000gp/T/nix-build-cmake-<IP_ADDRESS>.drv-0/cmake-<IP_ADDRESS>/Bootstrap.cmk/InitialCacheFlags.cmake
-- The C compiler identification is Clang 5.1.0
-- The CXX compiler identification is Clang 5.1.0
CMake Error at Modules/Platform/Darwin.cmake:211 (message):
  CMAKE_OSX_DEPLOYMENT_TARGET is '10.9' but CMAKE_OSX_SYSROOT:

   ""

  is not set to a MacOSX SDK with a recognized version.  Either set
  CMAKE_OSX_SYSROOT to a valid SDK or set CMAKE_OSX_DEPLOYMENT_TARGET to
  empty.
Call Stack (most recent call first):
  Modules/CMakeSystemSpecificInformation.cmake:36 (include)
  CMakeLists.txt:14 (project)

-- Configuring incomplete, errors occurred!
See also "/private/var/folders/qh/f4d7nfz93tg5fcj3t261f9f40000gp/T/nix-build-cmake-<IP_ADDRESS>.drv-0/cmake-<IP_ADDRESS>/CMakeFiles/CMakeOutput.log".
---------------------------------------------
Error when bootstrapping CMake:
Problem while running initial CMake
---------------------------------------------
builder for ‘/nix/store/9sx0m12dkcag96m4k73hjxr75qaga0sh-cmake-<IP_ADDRESS>.drv’ failed with exit code 11
cannot build derivation ‘/nix/store/1gmm2vz72whi2flf2v0768bc4h1kd5l4-clang-3.3.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/mx49q5jc05aacs6nq49bsid9r24spw6i-libc++-3.4.2.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/sbwr8h48a29qimgji5wmrgfb9w9r7jwn-clang-wrapper-3.3.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/31phkaiccqkdhljwhhldc13wqqphcr1h-stdenv.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/41nkvcix5cvk5gkwv40hjwk9w535sjqm-groovy-2.3.8.drv’: 1 dependencies couldn't be built
error: build of ‘/nix/store/41nkvcix5cvk5gkwv40hjwk9w535sjqm-groovy-2.3.8.drv’ failed

I think this is just another instance of Mac OS builds being generally broken, right?

Not seen this with other packages I use, so first for me. Other langs work well (clojure,Scala,Haskel)

I have two possible explanations for a bad hash:

They changed the archive upstream and the hash is just wrong
The contents of the archive have files/folders differing only in case, and extracting the archive on Mac OS collapses the case, changing the hash of the folder.

I don't think the latter option is likely given that groovy isn't using fetchzip.

Does this problem persists with groovy-2.4.0?

@dcapwell ping

Closing. If you still have problems feel to reopen or to create a new ticket.


Add parameter to choose install method

This PR will add option for cookbook users to download Odoo source from git.

Coverage remained the same at 98.876% when pulling 7b58552b39e6b843f3637eaf38c4d0c82b25b343 on joelhandwell:git into 194808bd33e83f82d1724f8dccdcf7244f9f4720 on gospelandit:master.

Coverage increased (+0.1%) to 99.02% when pulling b42853f253023dcee47f643ea7530b6c1ef825bf on joelhandwell:git into 194808bd33e83f82d1724f8dccdcf7244f9f4720 on gospelandit:master.


Print automatically closes on IOS devices

It's impossible to print from a IOS device.

Hello @stevendejongnl thank you for reporting this. I haven't tested this on other browsers other than google chrome. I will try to investigate this soon. Sorry for the inconvenience.


Best quality extraxtion of sohu not correct

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like that [x])
Use Preview tab to see how your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2016.11.22. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2016.11.22

Before submitting an issue make sure you have:

[x] At least skimmed through README and most notably FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

$ youtube-dl -v -F http://tv.sohu.com/20161013/n470208193.shtml
[debug] System config: []
[debug] User config: []
[debug] Command-line args: ['-v', '-F', 'http://tv.sohu.com/20161013/n470208193.shtml']
[debug] Encodings: locale cp936, fs mbcs, out cp936, pref cp936
[debug] youtube-dl version 2016.11.22
[debug] Python version 3.4.4 - Windows-10-10.0.14393
[debug] exe versions: ffmpeg N-82324-g872b358, ffprobe N-82324-g872b358
[debug] Proxy map: {}
[Sohu] 470208193: Downloading webpage
[Sohu] 470208193: Downloading JSON data for 3323578
[Sohu] 470208193: Downloading JSON data for 3323579
[Sohu] 470208193: Downloading JSON data for 3323580
[Sohu] 470208193: Downloading JSON data for 3323590
[Sohu] 470208193: Downloading ori video URL part 1 of 7
[Sohu] 470208193: Downloading high video URL part 1 of 7
[Sohu] 470208193: Downloading super video URL part 1 of 7
[Sohu] 470208193: Downloading nor video URL part 1 of 7
[Sohu] 470208193: Downloading ori video URL part 2 of 7
[Sohu] 470208193: Downloading high video URL part 2 of 7
[Sohu] 470208193: Downloading super video URL part 2 of 7
[Sohu] 470208193: Downloading nor video URL part 2 of 7
[Sohu] 470208193: Downloading ori video URL part 3 of 7
[Sohu] 470208193: Downloading high video URL part 3 of 7
[Sohu] 470208193: Downloading super video URL part 3 of 7
[Sohu] 470208193: Downloading nor video URL part 3 of 7
[Sohu] 470208193: Downloading ori video URL part 4 of 7
[Sohu] 470208193: Downloading high video URL part 4 of 7
[Sohu] 470208193: Downloading super video URL part 4 of 7
[Sohu] 470208193: Downloading nor video URL part 4 of 7
[Sohu] 470208193: Downloading ori video URL part 5 of 7
[Sohu] 470208193: Downloading high video URL part 5 of 7
[Sohu] 470208193: Downloading super video URL part 5 of 7
[Sohu] 470208193: Downloading nor video URL part 5 of 7
[Sohu] 470208193: Downloading ori video URL part 6 of 7
[Sohu] 470208193: Downloading high video URL part 6 of 7
[Sohu] 470208193: Downloading super video URL part 6 of 7
[Sohu] 470208193: Downloading nor video URL part 6 of 7
[Sohu] 470208193: Downloading ori video URL part 7 of 7
[Sohu] 470208193: Downloading high video URL part 7 of 7
[Sohu] 470208193: Downloading super video URL part 7 of 7
[Sohu] 470208193: Downloading nor video URL part 7 of 7
[download] Downloading playlist: 《法医秦明》第1集 - 高清正版在线观看
[Sohu] playlist 《法医秦明》第1集 - 高清正版在线观看: Collected 7 video ids (downloading 7 of them)
[download] Downloading video 1 of 7
[info] Available formats for 470208193_part1:
format code  extension  resolution note
nor          mp4        640x268    25fps, 10.62MiB
high         mp4        1024x430   25fps, 17.39MiB
ori          mp4        1280x538   25fps, 36.39MiB
super        mp4        1280x538   25fps, 36.39MiB (best)
[download] Downloading video 2 of 7
[info] Available formats for 470208193_part2:
format code  extension  resolution note
nor          mp4        640x268    25fps, 10.64MiB
high         mp4        1024x430   25fps, 17.45MiB
ori          mp4        1280x538   25fps, 36.52MiB
super        mp4        1280x538   25fps, 36.52MiB (best)
[download] Downloading video 3 of 7
[info] Available formats for 470208193_part3:
format code  extension  resolution note
nor          mp4        640x268    25fps, 10.63MiB
high         mp4        1024x430   25fps, 17.42MiB
ori          mp4        1280x538   25fps, 36.43MiB
super        mp4        1280x538   25fps, 36.43MiB (best)
[download] Downloading video 4 of 7
[info] Available formats for 470208193_part4:
format code  extension  resolution note
nor          mp4        640x268    25fps, 10.67MiB
high         mp4        1024x430   25fps, 17.51MiB
ori          mp4        1280x538   25fps, 36.62MiB
super        mp4        1280x538   25fps, 36.62MiB (best)
[download] Downloading video 5 of 7
[info] Available formats for 470208193_part5:
format code  extension  resolution note
nor          mp4        640x268    25fps, 10.62MiB
high         mp4        1024x430   25fps, 17.42MiB
ori          mp4        1280x538   25fps, 36.44MiB
super        mp4        1280x538   25fps, 36.44MiB (best)
[download] Downloading video 6 of 7
[info] Available formats for 470208193_part6:
format code  extension  resolution note
nor          mp4        640x268    25fps, 10.65MiB
high         mp4        1024x430   25fps, 17.44MiB
ori          mp4        1280x538   25fps, 36.50MiB
super        mp4        1280x538   25fps, 36.50MiB (best)
[download] Downloading video 7 of 7
[info] Available formats for 470208193_part7:
format code  extension  resolution note
nor          mp4        640x268    25fps, 7.35MiB
high         mp4        1024x430   25fps, 12.07MiB
ori          mp4        1280x538   25fps, 24.82MiB
super        mp4        1280x538   25fps, 24.82MiB (best)
[download] Finished downloading playlist: 《法医秦明》第1集 - 高清正版在线观看
<end of log>

Description of your issue, suggested solution and other information
The extraction of the site tv.sohu.com has a bug. The format "ori" links are the same as "super", but actually they are different. "ori" links should be 1080p and the files should be larger than the "super"s. See the output log above

For this video, 1080P requires login. Maybe that's the reason.


May/June release p3diffexp update

This update enables automatic detection of the source id in the user input. It also covers the switch from seed_id to patric_id in SOLR.

Whoops wrong direction


Include a zero bucket, zeros are being reported as 1

With a min bucket of 1, a 0 is reported as a 1, which is quite misleading for this kind of use.
Sorta obvious in retrospect, but we have so few histograms anywhere that I apparently don't have any safe habits built up.

Pull Request Test Coverage Report for Build 019074a7-be79-43e7-b97d-7674d472b3a6
Details

0 of 0   changed or added relevant lines in 0 files are covered.
48 unchanged lines in 10 files lost coverage.
Overall coverage decreased (-0.02%) to 71.505%

Files with Coverage Reduction
New Missed Lines
%

common/task/weighted_round_robin_task_scheduler.go
2
89.05%

service/matching/tasklist/task_list_manager.go
2
77.05%

service/frontend/api/handler.go
2
75.62%

service/history/task/transfer_standby_task_executor.go
3
86.23%

service/history/task/task.go
3
84.81%

common/persistence/nosql/nosql_task_store.go
3
85.52%

common/task/fifo_task_scheduler.go
3
84.54%

common/archiver/filestore/historyArchiver.go
4
80.95%

service/history/execution/cache.go
6
74.61%

service/history/task/task_util.go
20
60.29%

Totals

Change from base Build 01907465-3a13-43f8-89cc-21fc60d6d529:
-0.02%

Covered Lines:
105293

Relevant Lines:
147252

💛  - Coveralls


Import PriorityClassList component on index.vue explicitly

What type of PR is this?

/kind bug
What this PR does / why we need it:
We import PriorityClassListcomponent onindex.vue.
(Why was it working all this time?)
Which issue(s) this PR fixes:

No fixes.
Special notes for your reviewer:
/label tide/merge-method-squash
/assgin @sanposhiho

/ok-to-test


How should I unit test a rule?

Question about GraphQL Shield
I'm unit testing my rules and I managed to do it like this but it doesn't feels right, is very verbose and I have to use "any" on typescript so types don't fail.
  it("is valid when a valid token is provided", async () => {
    const context = {
      req: jest.fn()
    }

    const isValid = await isAuthenticated.resolve(
      null, // parent
      null, // args
      context, // Context
      null, // Info
      {} as any, // Options
    );

    expect(isValid).toEqual(true);
  });

Like this resolve does nothing :/
What approach you will use?

[x ] I have checked other questions and found none that matches mine.

Hey 👋,
I think this is a great question! Would you mind sharing a bit more context regarding the input/output of your tests? I belive we could compose an official function to test rules.

I've been fairly interested in graphql-shield and writing specs that is specific to my codebase. So I'll share on how I've been designing my unit tests in order to get confidence in my app without necessarily having to unit test graphql-shield. This library is solid and rather than writing tests in your own library validating the library works as its advertised, all tests related to graphql-shield logic should lie inside this repo. As for in your codebase, you should write specs more geared to the rules you write so that should allow you to feel confident in reusing your rules. I would manually just validate that the caching works completely fine (unless someone has an easy to implement spec :) )
So I will be speaking around the topic of resolver level rules, and not field specific rules. Right now we are currently still developing so I haven't had to face that challenge yet.
Because i'm not doing any field specific rules, I've created helper functions that assert whether the permission passed or did not. (Note: I'm using mocha/chai for my unit tests) The premise of these specs is, if there's anything in the "data" key, then assume it worked and expect no errors. For validating failing tests, assert the exact error. Just to note, the validateSuccessfulRequest expects your the resolvers inputs/payloads to be required in the schema. resolver(input: ResolverInput!): ResolverPayload!
/*
 PERMISSION GRANTED SPECS
*/

const validateSuccessfulRequest = (res, operationName, debug = false) => {
  if (debug || res.body.errors) {
    res.body.should.be.eql({});
    // sometimes on errors, the body doesn't get set so we check text as well
    res.text.should.be.eql({});
  }
  res.status.should.be.eql(200);
  // since we are doing permission specs, we do assertions on if there is data available and no errors. We don't care
  // about what's inside, this is just to check that if it is present, then the user does/does not have access.
  res.body.should.not.have.property('errors');
  res.body.should.have.property('data');
  res.body.should.have.nested.property(`data.${operationName}`).that.should.not.be.null;
};

/*
* PERMISSION DENIED SPECS
* */

export const validateRejectedRequest = (res, operationName, nullable, debug = false) => {
  if (debug || res.status === 400) {
    // In order to get better visibility of what our error is, we compare it
    // to an empty obj to deep display what our payload is
    res.body.should.be.eql({});
  }

  if (nullable) {
    res.body.should.have.nested.property(`data.${operationName}`, null);
  } else {
    res.body.should.have.nested.property(`data`, null);
  }

  res.body.should.have.property('errors').that.deep.equals([
    {
      locations: [],
      message: 'Not Authorised!',
      path: [operationName]
    }
  ]);
};

Then I have reusable spec helpers that are tied to specific rules. The two spec helper functions are tied to specific rules which are named isAdmin and isAuthenticated respectively.
export const adminAllowedSpec = (setupCallback, debug) => {
  const specFunc = debug ? it.only : it;
  return specFunc(`adminAllowedSpec: allows admin to view the current resource`, async () => {
    const { graphqlInstance, operationName, query, variables } = setupCallback();
    const admin = await setupAdmin({});
    await authorizeUser(admin, graphqlInstance);

    const res = await graphqlInstance.send({
      query,
      variables
    });

    validateSuccessfulRequest(res, operationName, debug);
  });
};

export const isNotAuthenticatedRejectedSpec = (setupCallback, debug) => {
  const specFunc = debug ? it.only : it;
  return specFunc(`isNotAuthenticatedRejectedSpec: should restrict if not authenticated`, async () => {
    const { graphqlInstance, operationName, query, variables, nullable } = setupCallback();
    unAuthorizeUser(graphqlInstance);
    const res = await graphqlInstance.send({
      query,
      variables
    });

    validateRejectedRequest(res, operationName, nullable, debug);
  });
};

And then I individually test resolvers independently from one another and I write a describe block related to specifically around permissions

describe('Mutation#myGraphqlResolverMutation', () => {
  // vars go here

  before(async () => {
    //...before setup
  });

  beforeEach(async () => {
    //  this is just a request object that points to `/graphql`
    graphqlInstance = requestGraphqlInstance();

    await authorizeUser(testOwner, graphqlInstance);
    setupData = {
      graphqlInstance,
      operationName: 'myGraphqlResolverMutation',
      query: MY_GRAPHQL_RESOLVER_MUTATION,
      variables: {
        input: {
          myInputVariable: 5
        }
      }
    };
  });
  // there is a 'permissions' block in each of our resolvers forcing us to treat permissions differently than the resolvers logic
  describe('permissions', () => {
    adminAllowedSpec(() => setupData);
    providedUserAllowedToAccessObjectSpec(() => setupData, () => userWhoIsAllowedToAccess);
    isNotAuthenticatedRejectedSpec(() => setupData);
  });

  // the rest of the code the tests the resolver, nothing related to permissions
  it('does some cool mutations!', ()=>{

  })

});

So far this approach has been splendid. Right now, in the codebase I'm in, we have all the fields whiteliste in order to deny any permissions outright and we have to go field by field in order to think about the proper permissions and enable them. So we've gotten to the point where we think about what rules we need to implement, drop in the helper functions to test specific rules, fail them, and then get them passing once the rule is applied.
We've even gone as far as made a ruleSet helper functions since some specs are specific to the type of argument passed in. These help us group specific mutations/queries based off of the input and reuse all of the same specs for different resolvers.
fruitIdArgPermissionsSpec vegetableIdArgPermissionSpec and each of them import the smaller helper specs, so we can just drop in a function and get a lot of free tests.
Let me know if you guys need me to clean something up in this. Hope someone finds us around this topic. I'm considering even creating an article around the subject but I'd like to get more insight on the topic to see if anyone else has another approach. I'm still tweaking and thinking of new ways.

I've been building a toy graphql-blog and had to set up a little bit of mocking (see applyResolver) to test my permissions.  The function is mostly customized to my use case but I can imagine providing a general one that takes args, variables, and mocks out _shield in context as a part of this package to facilitate testing.

@maticzav Have there been any updates on this? Would love to see a workaround or spec regarding this.


get configTypeName a little flaw

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Ⅰ. Issue Description
when building a configuration, there are insufficient prompts for configuration items that do not exist or are not supported
当配置不存在或者不支持时,无法从异常提示中捕捉到对应的问题
question 1: not support register type should change to not support config type
问题1:not support register type: 应该改为not support config type:
question 2: the prompt that the configuration type that cannot be read and the configuration type is empty should be separated
问题2:应该将不支持配置中心类型,跟读不到配置中心类型的异常提示区分开
有兴趣处理的同学,可以回复你要认领即可
if you are interested in dealing with this problem, you can reply, please assign it to me

Ⅱ. Describe what happened
If there is an exception, please attach the exception trace:
Just paste your stack trace here!

Ⅲ. Describe what you expected to happen
Ⅳ. How to reproduce it (as minimally and precisely as possible)

xxx
xxx
xxx

Ⅴ. Anything else we need to know?
Ⅵ. Environment:

JDK version :
OS :
Others:

I will fix it.


Corrected a typo in Dequantize comments

Given dequantize pseudocode is same as quantization. Corrected that
range_scale = number_of_steps / range --> range_scale = range / number_of_steps

Can one of the admins verify this patch?


Add option to warn on local variables that shadow allowed globals

The intent is to catch code like this:
allowed_global = "whatever"

local function func(allowed_global)
	 print(allowed_global)
end

func(3)

local t = {1,2,3,4}
for allowed_global,_ in pairs(t) do
    print(allowed_global)
end

[arichard@arichard Documents]$ luacheck text.lua --new-globals="allowed_global"
Checking text.lua                                 OK

Total: 0 warnings / 0 errors in 1 file

A few ways that this could be done:

Allow config to submit a list of banned local names
Have a flag to ban local usages of permitted globals (perhaps separate flags for read-only/read-write?)

This was also suggested in #39. The main problem is that stuff like local allowed_global = allowed_global should be valid. And even when the value of the shadowing local is not exactly the corresponding global, the code could be perfectly valid, like local unpack = table.unpack or unpack or this:
local old_xpcall = xpcall
local function xpcall(func, handler, ...) -- Shadows global xpcall with version that behaves like xpcall in Lua 5,2+ even under Lua 5.1
   local args = {...}
   local num_args = select("#", ...)
   return old_xpcall(function() return func(unpack(args, 1, num_args)) end, handler)
end

So, in general, when the purpose of shadowing is establishing a local that does same thing as the global, perhaps with some extra features or compatibility, it probably should not be a warning. But figuring this out in the general case is difficult.

Nothing changed here. Figuring out whether the shadowing local is compatible with the global in some way requires more sophisticated analysis that what luacheck does right now.


Resposive visiblity class

Prerequisites

[X] I have searched for duplicate or closed feature requests
[X] I have read the contributing guidelines

Proposal
A responsive visiblity class would be helpful, like a class that shows only on a specific screen size.
Motivation and context
I feel like a responsive visiblity class should be added because, for example, if a element is intended to be seen on smaller screens, it should not display on bigger screens and display on smaller screens.

Thanks for opening this issue @mdwalters. Do you mean something linked to our .visibility utility?
Because we have already d-(*-)none classes: (e.g. .d-none, d-sm-none etc.).

Do you mean something linked to our .visibility utility?

yes

but since this already exists, should this be closed?


Fix delete sample prep analysis refactor

Changes Unknown when pulling 93f2d3d6028d767422d169c8b73d5607b0300e60 on antgonza:fix-delete-sample-prep-analysis-refactor into ** on biocore:analysis-refactor**.


Add Vercal Analytics

Describe the Problem
Its missing Vercel Analytics
References
https://vercel.com/docs/analytics
Describe the Proposed Solution
We're just not getting analytics

Updated @vercel/analytics package, added inject script into +layout.svelte. Currently setting up a test deployment on vercel to test the analytics before I submit the PR.


Remove links to docs in Builder UI

Hi Jamon!
Based on our conversation in this docs ticket #1102, we'd like to remove the links to documentation. We audited the Builder for all current links and documented it in docs ticket #1102. Once we have more Map Academy content live, we'll do an exercise of adding new links within the Builder UI where appropriate.
cc' @michellechandra @csobier @saleiva

:+1:


install TM1py error

I follow tm1py install guide, download Anaconda, window, 3.7 version, launch Anaconda prompt, type pip install TM1py, I got "Could not find a version that satisfies the requirement TM1py (from versions: )
No matching distribution found for TM1py"
The problem appears unable to connect to something, log looks different from the sample.
Do I missing any step? Thanks so much for helping.

looks like you have python 2.7 installed.
If run
python --version
in the anaconda prompt what does it show you ?

Hi, Marius, 3.7.3.  It appears that I can not connect to installation source, my company has lots of firewall, I will try using my home internet, let you know, thanks so much for getting back to me from your busy schedule!
On Wednesday, July 17, 2019 12:24:34 PM PDT, Marius Wirtz<EMAIL_ADDRESS>wrote:

looks like you have python 2.7 installed.
If run
python --version
in the anaconda prompt what does it show you ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi Marius, I installed successfully at home, see below, but no luck to 'connect to tm1' via check.py in sample master yet.
thanks again, you can close my issue.
On Wednesday, July 17, 2019 01:18:08 PM PDT, Shirley Lu<EMAIL_ADDRESS>wrote:

Hi, Marius, 3.7.3.  It appears that I can not connect to installation source, my company has lots of firewall, I will try using my home internet, let you know, thanks so much for getting back to me from your busy schedule!
On Wednesday, July 17, 2019 12:24:34 PM PDT, Marius Wirtz<EMAIL_ADDRESS>wrote:

looks like you have python 2.7 installed.
If run
python --version
in the anaconda prompt what does it show you ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi Marius,
it is working now, I am very excited to start learning tm1py (start with your samples).  I am sorry for the mistake and thank you so much for your time. You can close the issue now
have a great weekend
Shirley
On Thursday, July 18, 2019 12:52:06 PM PDT, Marius Wirtz<EMAIL_ADDRESS>wrote:

Closed #56.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Coco example

Hi, may I know where to download the _frozen_inference_graph.pb in the Coco example? Thanks.

Sure!
If you look for "Coco tensorflow zoo" on a search engine you will find a GitHub repo with different models. Once there you can download the one you want, although in the example I used ssd_inception_v2_coco. Also you can download the model directly from here.
Hope you find it!


Method Overloads are not propagating in IntelliSense

In VS RC1 with F# installed, type the following in a console app:
open System

[<EntryPoint>]
let main argv =
    Console.WriteLine(
    0 // return an integer exit code

Note that the overloads for WiteLine do not show up in IntelliSense:

Seems the same as #1766


chore: 1.3.0

Description
New patch version

This change is way too out of date. I am just going to close it.


Add MemFree

Introduction
MemFree is a hybrid AI search engine that simultaneously performs searches on your personal knowledge base (such as bookmarks, notes, documents, etc.) and the Internet.
Highlights

Hybrid AI Search Engine
One-Click Chrome Bookmarks Sync and Index
Support multiple traditional search engines as source
Self-hosted Super Fast Serverless Vector Database
Self-hosted Super Fast Local Embedding and Rerank Service
Full Code Open Source
One-Click Deployment On Production

@ahaapple nice project, thanks for adding it


Travis

Pull Request Template
Issue
Addresses # (issue)

[ ] This change addresses the issue in full
[ ] This change addresses only certain aspects of the issue
[ ] This change is a dependency for another issue
[ ] This change has a dependency from another issue

Description
Setting up initial travis-ci integration.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Prototype/POC (not to merge)
[ ] This change is a refactor/address technical debt
[ ] This change requires a documentation update
[ ] This change requires a SQL Script

How Can This Be Tested/Reviewed?
Please describe the tests that you ran to verify your changes. Provide instructions so we can review. Please also list any relevant details for your test configuration

[ ] Desktop View
[ ] Mobile View
[ ] Test A
[ ] Test B

Checklist:

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

Is it possible to re-run the checks? Or would you need to create a new commit?

Any changes to this branch will trigger a re-run. There are currently a couple of lint issues that need to be fix.

Once we check this in, this would run against any PR's to the main branch? Can we have this run tests? There's another github action for ESLint that we can use.

I merged in a different version of the .travis.yml file that builds the sites, so it should be working now on PRs to main. Thanks for the example!


Connector Lines

Hello, is there a way to have the values outside with a padding and a line pointing to it's respective slice in the pie?
Example, I have a pie where two slices are very thin, and the values outside are very close, wondering if a line pointing from the slice to the value can be added.
Thank you!

This would be fantastic, only thing stopping us using this plugin at the moment. Otherwise this really fills a gap in chartjs for some orgs.

There’s a plug-in that is in the chart ja webpage, called outlabeled, that can do it....!!!


Using XDG_RUNTIME_DIR to get DOCKLE_HOST not working in GitHub runner

From today, we had a problem with our actions on in GitHub runner (ubuntu-latest).
Error: FATAL	unable to initialize a image struct: failed to initialize source: reading manifest <IMAGE> in <REGISTRY>: manifest unknown: manifest tagged by <TAG> is not found

It seems in GitHub runner, the XDG_RUNTIME_DIR env value is /run/user/1001 so dockle tries to use unix:///run/user/1001/docker.sock as docker sock file location and can't connect to docker.
Can we use another env as default value for checking to get dockerSockPath. here

We are seeing the same issue. Utilizing the Dockle CLI application with GitHub Actions running on an ubuntu:latest, dockle is unable to scan local images.
Hacking this by adding:
env:
  XDG_RUNTIME_DIR: ""

To force the correct docker sock setting resolves the issue.

@iamahern Thanks!


Switch over to published Docker image on Cassandra example

Now that we can run it in CI we should add a test for it.

We can't test it at the moment for the same reason described here: https://github.com/shotover/shotover-proxy/pull/346#discussion_r755561861

Should we add support for that in this PR then?
Otherwise I dont know when we will pay off that debt.

Yep I think so.

Shouldn't we be using the local docker image built using the shotover executable for the current build?

I don't think so, that would mean the user would be downloading the Shotover source code and building it themselves. The purpose of this example is to demonstrate to user's how to setup Shotover for production use and we want to encourage them to use a released version of Shotover.

I want to talk about this more on monday, but I think bens confusion here might be valid and possibly we should do one of:

move these shotover docker examples into a seperate repo
or rewrite the examples to build from local shotover.

What would be the advantage of those over the current setup?

here is the downsides for each approach:
example-configs contains examples that use ShotoverManager and examples that use release shotover image

confusing for developers - Easy to accidentally write an integration test that is only run against the latest release.
confusing for users browsing examples

its confusing that some examples in the folder need a shotover binary to be acquired separately while other examples do not.
its not clear that some examples can be used on the latest release and some examples are not yet compatible with the latest release.

example-configs contains examples that use ShotoverManager and examples that use locally built shotover image

not as useful for users as they will have to change the examples to run them

example-configs only contains examples that use ShotoverManager, a separate folder or repo is used for examples with release shotover image

users have to search multiple folders to find examples.

I'm currently thinking the best solution here would be to put docker-compose.yml's that use release shotover images in a separate example-configs-published-docker/ folder?
By keeping a consistent naming scheme with example-configs it should help both developers and users differentiate between these two kinds of examples.

Thanks for that great write-up. To be honest I didn't think it was that confusing but I'm happy to go forward with that recommendation given it's pretty inconsequential.

keep in mind we can build shotover as a docker image and tag it useing -t shotover.io/shotover which will resolve the above path and use the locally built version if you dont have the locally built version it will pull from the repo.
I think part of the confusion as well arises from the fact we use the examples as part of the tests (which is good cause it keeps examples up to date), but also forces us a bit into a corner with how we use them.
Having said all of the above...I'm happy with splitting into the two different ones (published vs built locally)

BTW, the base64 is already a dependency.


[CS] Fixes #2318 : Bug with CheckUnneededSymfonyStyleUsageRule that requires to use MethodCall with $scope context

All checks have passed 🎉 @TomasVotruba it is ready for review.

Woohoo, thanks :+1:

@TomasVotruba automerge label seems not working as it requires 1 approving review

Thanks for letting me know. That's good 💯


Filters

Implement filters for session management

A couple of suggested comment STRIKE's, Suggested renaming - Ok to ignore me, talk w/ Tim about xref, may wish to move to parent.  (or [EXCLUDE_]
Consider adding jetty-jsp-maven-plugin to precompile your jsp's.  Then LGTM

It appears I was able to manually merge.
@shun-fan @tswast
You configure by setting values in the pom, or passing them on the command line, I'm going to checkin a prototype for this next, then exclude it from git.
@shun-fan I'm able to successfully login locally, but not when deployed - could you take a look.


Podman volume parent directory created are owned by root when using --user and --uidmap

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
When mounting a configuration volume, the parent directory is owned by root, which prevent the container user from creating lateral configuration.
Steps to reproduce the issue:

Create user in image
cid=$(buildah from registry.fedoraproject.org/fedora); buildah run $cid useradd -m user && buildah commit --rm $cid fedora-user

Start the container

host$ podman run -it --rm --volume ~/.config/pavucontrol.ini:/home/user/.config/pavucontrol.ini --user 1000 --uidmap 1000:0:1 --uidmap 0:1:999 --uidmap 1001:1001:64535 fedora-user
[user@7246ce1da224 /]$ ls -la ~/.config
total 8
drwxr-xr-x. 2 root root 4096 Sep  9 20:14 .
drwx------. 3 user user 4096 Sep  9 20:14 ..
-rw-rw-r--. 1 user user    0 Sep  9 20:04 pavucontrol.ini
[user@7246ce1da224 /]$ mkdir ~/.config/pulseaudio
mkdir: cannot create directory ‘/home/user/.config/pulseaudio’: Permission denied

Describe the results you received:
Volume parent directory created by podman are not writable by the container user.
Describe the results you expected:
Volume parent directory should respect their parent owner uid or the volume target owner.
Additional information you deem important (e.g. issue happens only occasionally):
A solution is to pre-create the directory structure:
host$ mkdir -p /tmp/pavucontrol-container/.config
host$ chcon -R system_u:object_r:container_file_t:s0 /tmp/pavucontrol-container/
host$ podman run -it --rm --volume /tmp/pavucontrol-container:/home/user --volume ~/.config/pavucontrol.ini:/home/user/.config/pavucontrol.ini --user 1000 --uidmap 1000:0:1 --uidmap 0:1:999 --uidmap 1001:1001:64535 fedora-user
bash-5.0$ mkdir ~/.config/pulseaudio
bash-5.0$ ls -la ~/.config
total 12
drwxrwxr-x. 3 user user 4096 Sep  9 20:23 .
drwxrwxr-x. 3 user user 4096 Sep  9 20:21 ..
-rw-rw-r--. 1 user user    0 Sep  9 20:04 pavucontrol.ini
drwxr-xr-x. 2 user user 4096 Sep  9 20:23 pulseaudio

Output of podman version:
Version:            1.5.1
RemoteAPI Version:  1
Go Version:         go1.12.7
OS/Arch:            linux/amd64

Output of podman info --debug:
debug:
  compiler: gc
  git commit: ""
  go version: go1.12.7
  podman version: 1.5.1
host:
  BuildahVersion: 1.10.1
  Conmon:
    package: podman-1.5.1-3.fc30.x86_64
    path: /usr/libexec/podman/conmon
    version: 'conmon version 2.0.0, commit: d728afa06cd2df86a27f32a4692c7099a56acc97-dirty'
  Distribution:
    distribution: fedora
    version: "30"
  MemFree: 464338944
  MemTotal:<PHONE_NUMBER>4
  OCIRuntime:
    package: containerd.io-1.2.6-3.3.fc30.x86_64
    path: /usr/bin/runc
    version: |-
      runc version 1.0.0-rc8
      commit: 425e105d5a03fabd737a126ad93d62a9eeede87f
      spec: 1.0.1-dev
  SwapFree: 0
  SwapTotal: 0
  arch: amd64
  cpus: 8
  eventlogger: file
  hostname: ocp.rdocloud
  kernel: 5.2.9-200.fc30.x86_64
  os: linux
  rootless: true
  uptime: 121h 59m 13.33s (Approximately 5.04 days)
registries:
  blocked: null
  insecure: null
  search:
  - docker.io
  - registry.fedoraproject.org
  - quay.io
  - registry.access.redhat.com
  - registry.centos.org
store:
  ConfigFile: /home/fedora/.config/containers/storage.conf
  ContainerStore:
    number: 9
  GraphDriverName: vfs
  GraphOptions: null
  GraphRoot: /home/fedora/.local/share/containers/storage
  GraphStatus: {}
  ImageStore:
    number: 37
  RunRoot: /tmp/1000
  VolumePath: /home/fedora/.local/share/containers/storage/volumes

Package info (e.g. output of rpm -q podman or apt list podman):
podman-1.5.1-3.fc30.x86_64

Additional environment details (AWS, VirtualBox, physical, etc.):
The host is running in OpenStack

I'll take this one

Hello
Any progress?

@12factor-mx Interested in opening a PR?  @mheon has been off working on other issues/features...

could it be a security issue if two containers running with different --user use the same volume?
This is something that could be easily fixed by creating the directory before running the container with the correct permissions.

The source directory should always be created by the user, if using a volume.  We could add a flag to the volume when we start running in random User Namespace, for the container engine to "Chown" the directory.

@giuseppe Interested in opening a PR?

@ashley-cui Could you fix this bug.  Basically any directory created by podman within the container should match the parent directory.
In this case the podman is creating ~/.config/ as owned by root when it should have created it with the ownership of ~ "$HOME"

I don't think this is a bug.  I did the same thing on Docker and got the same results.
docker run -ti -v $PWD/Dockerfile:/test/Dockerfile --user bin fedora sh
sh-5.0$ id
uid=1(bin) gid=1(bin) groups=1(bin)
sh-5.0$ cd /test/
sh-5.0$ ls
Dockerfile
sh-5.0$ touch dan
touch: cannot touch 'dan': Permission denied
sh-5.0$ id
uid=1(bin) gid=1(bin) groups=1(bin)


Turbolinks not firing load event on Rails 6 with Webpacker

Describe the bug
The event turbolinks:load doesn't get fired when I navigate to a new page.
To Reproduce
I created a fresh Rails app so it's easy to reproduce the bug. You can also follow along the steps below.
// index.html.erb

<%= javascript_pack_tag 'SomeComponent', 'data-turbolinks-track': 'reload' %>

// SomeComponent.js
const renderComponent = () => {
  const node = document.getElementById("some-id");
  const data = JSON.parse(node.getAttribute("data"));

  ReactDOM.render(<SomeComponent {...data} />, node);
};

// Listen to `turbolinks:load` event
document.addEventListener("turbolinks:load", renderComponent);

Steps to reproduce the behavior:

Start from some other page than index.html.erb
Navigate to index.html.erb
Notice that SomeComponent isn't rendered because turbolinks:load isn't fired
Refresh the page
Notice that SomeComponent is rendered because turbolinks:load is fired

Expected behavior

Start from some other page than index.html.erb
Go to the page that renders index.html.erb
SomeComponent is rendered because turbolinks:load is fired

Details (please complete the following information):

MacOS Catalina
Chrome Version 80.0
Rails <IP_ADDRESS>
ruby 2.7.1p83
turbolinks 5.2.1
webpacker 4.2.2

Additional context
I was able to reproduce this problem in a clean project that uses the latest Rails, Webpacker, Turbolinks packages. The following links might be related but none of them seemed to solve the problem but only worked around it by disabling turbolinks.

https://github.com/rails/webpacker/issues/354
https://github.com/turbolinks/turbolinks/issues/477

I also posted this issue on https://github.com/rails/webpacker/issues/2527.

turbolinks:load is always fired when Turbolinks loads a page via AJAX, but it does not wait for scripts to load. In your example, turbolinks:load is being fired before SomeComponent.js is loaded and executed. When a page is "fully" loaded e.g. via a refresh, Turbolinks fires turbolinks:load on DOMContentLoaded, so in this case it will wait for scripts to load.
If you're loading some scripts at the end of the  element, you may not need to listen out for turbolinks:load; the DOM should be accessible without having to wait for the load event.
Hope that helps.

Having the same issue here and it seems pretty unintuitive that turbolinks:load is fired before the javascript_pack_tag is loaded. Got it to work by adding the following to my packs based on Issue #354 referenced above, but not a huge fan of the workaround:
if (!Turbolinks) {
location.reload();
}
Turbolinks.dispatch("turbolinks:load");


Error API Imou

same for me.

Hi, have a look here: https://community.home-assistant.io/t/imou-life-cloud-integration/462439/202
If this is what you are experiencing. Thanks


buttonhoveringeffect

Closes
Closes #1512
Description
i have added the hovering effect on the message us button with linear gradient from left to right
Screenshots

Note to reviewers

Checklist:

[x] I have linked the PR to the correct issue.
[x] I have read the Contribution Guidelines
[x] I have built and tested the changes, and they do not break or show any errors.

can you please review my pr @Vaishnavi-Patil2211

can you please review my pr @Vaishnavi-Patil2211

can you please review my pr @Vaishnavi-Patil2211

can you please review my pr @Vaishnavi-Patil2211

can you please review my pr @Vaishnavi-Patil2211


chore: update C# platform name

#384  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @jonathannorris and the rest of your teammates on  Graphite


--hide-dot-files is not hidding dot files

I want to hide the dot files in my home directory but this isn't working like expected, here is an screenshot:

Thanks for reporting this.
It got broken by a refactor in cb16e60f3302ad77f7450e22deaf15c8e82f1906 on 2/19.

v0.15 was published with the fix.
If you're aiming for defaults similar to ls then you might also be happy with --nix (or even prefer it) which implies hiding dot files, among other things.


Deploying trader for Decision Tree and Random Forest

Hello, thank you for sharing this project. I would like to test with different machine learning frameworks.
Are there any examples or notebooks available for deploying a trader for operation on real (or simulated ) accounts with Decision Tree and Random Forest?

Hi t3ch9, Thank you for your interest in mt5se project and sorry for the late answer.
Yes, you can find examples using Decision Tree and Random Forest in: https://paulo-al-castro.github.io/mt5se/ai_mt5se.html
You may also find another examples in : https://paulo-al-castro.github.io/mt5se/


Create task returns invalid instructions after saving in UmpleOnline

Summary
Within the UmpleOnline, the users can create a task and save it. Once the task a saved, the system displays the information of saved task at the same task panel. The system returns the details of a different task once it saves a task. It shows a details of previously saved task.
Steps to Reproduce

Go to the "TASKS", then click on the "Create a Task".

Enter a sample value at task name (testTask10) and instructions (test value as example) . Click "Submit Task".

The system will save the task and display the details.
Now, perform the step (2) for with a different task name. and check the task details. It will retrieve the task details of previously saved task.

Expected Feature
The system should display the details of current task.

The reproduction steps are unclear. After step 3 you can't do step 2 again since the task name field is not editable. How do you get back to step 2? Please be more precise. I tried 'start over' but the issue did not occur.

The issue is not re-producible. I have tested it for 20 occurrences in three different browsers and found it working as expected.
I would request to close this ticket.


Split worlds into different .pak files

We should be able to split the worlds up into different .pak files. That way we can distribute "HolodeckCore" that has the engine executable but download .pak files with individual levels on demand. This will allow users to only download the world they want to use, and we will be able to patch a level without rebuilding the whole engine and requiring a new download.
And changes to the engine executable would probably require a redownload of everything.

We aren't going to do this, instead each package is going to be a separate executable. This works well enough


fix: remove unnecessary basename

Fixes #141
In #99 I added a dependency to basename when it's not really needed.
Credit and thanks to @birunts for finding the issue and providing the solution!

Just hit this as well. It would be great to get this merged. Thanks for the fix @jjmaestro!


move dockerjava client to simpler okhttp transport

The http client and docker transport dependencies in the --docker-metrics support are forcing shading and a glut of dependencies. Moving to the simpler and leaner okhttp transport will reduce this.
Java HttpClient can be used elsewhere.

complete in master


Vim9: crash when concatenating boolean option with string

Describe the bug
In Vim9 script, concatenating the value of a boolean option with a string inside a :def function might make Vim crash.
To Reproduce
Run this shell command:
vim -Nu NONE -S <(cat <<'EOF'
    vim9script
    def Func()
        set tgc
        echom '&tgc: ' .. &tgc
    enddef
    Func()
EOF
)

Vim crashes.
Expected behavior
Vim doesn't crash.
Environment

Vim version: 8.2 Included patches: 1-2257
OS: Ubuntu 16.04.7 LTS
Terminal: xterm(363)

Additional context
Regression introduced in 8.2.2254.

backtrace
valgrind log
asan log

I can't reproduce anymore.  It was probably fixed by 8.2.2261.

I can't reproduce anymore.  It was probably fixed by 8.2.2261.

Also fixed by 8.2.2261.
I do think that the result should be "&tgc: true" instead of "&tgc: v:true".

Also fixed by 8.2.2261.
I do think that the result should be "&tgc: true" instead of "&tgc: v:true".

I do think that the result should be "&tgc: true" instead of "&tgc: v:true".

That's what I've always thought too.  If in the Vim9 context, true should be printed, otherwise v:true.  But I think :echo and :echom have always printed v:true.  And that's what the help seems to document:
https://github.com/vim/vim/blob/d5ea8f08f78d20fde8773663894de5e8c023bd83/runtime/doc/vim9.txt#L632
If :echo printed true, then this example should be re-written like this:
'hello ' .. v:true  == 'hello true'
                              ^--^
                              no "v:" prefix

I do think that the result should be "&tgc: true" instead of "&tgc: v:true".

That's what I've always thought too.  If in the Vim9 context, true should be printed, otherwise v:true.  But I think :echo and :echom have always printed v:true.  And that's what the help seems to document:
https://github.com/vim/vim/blob/d5ea8f08f78d20fde8773663894de5e8c023bd83/runtime/doc/vim9.txt#L632
If :echo printed true, then this example should be re-written like this:
'hello ' .. v:true  == 'hello true'
                              ^--^
                              no "v:" prefix

If we use "true" and "false" when writing Vim9 script, then Vim should also echo that.
Using v:true and v:false is unexpected.

If we use "true" and "false" when writing Vim9 script, then Vim should also echo that.
Using v:true and v:false is unexpected.


[Type Checker] Fix two crashes related to SE-0091 (operators as members)

What's in this pull request?
This PR fixes two crashes in the type checker due to ill-formed uses of operators as members of types.
Resolved bug number: (rdar://problem/27940842)

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

A smoke test on macOS does the following:

Builds the compiler incrementally.
Builds the standard library only for macOS. Simulator standard libraries and
device standard libraries are not built.
lldb is not built.
The test and validation-test targets are run only for macOS. The optimized
version of these tests are not run.

A smoke test on Linux does the following:

Builds the compiler incrementally.
Builds the standard library incrementally.
lldb is built incrementally.
The swift test and validation-test targets are run. The optimized version of these
tests are not run.
lldb is tested.

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

@swift-ci please test

@rudkx please review

@DougGregor LGTM!


wrap Dict.fromList into a Result (in the documentation)

decodeString returns a Result, so Dict.fromList needs to be wrapped into a Result too

Thank you for pointing this out! Some modules got moved around, so I made the changes in the appropriate places.


has_subwoofer throws KeyError: 'model_name'

I'm looking to work with a subwoofer in the Arc+Sub setup and started from the simple example:
from soco import SoCo
my_zone = SoCo('***')
print(my_zone.has_subwoofer)

It returns the error:

Traceback (most recent call last):
File "main.py", line 3, in
print(my_zone.has_subwoofer)
File "/.venv/lib/python3.9/site-packages/soco/core.py", line 518, in has_subwoofer
model_name = self.speaker_info["model_name"].lower()
KeyError: 'model_name'

The code works fine if I run it under the debugger line by line. When I set a breakpoint to core.py at model_name = self.speaker_info["model_name"].lower(), I found that self.speaker_info was an empty collection until I didn't manually expand the properties of the self object in the debugger's watch. They were recalculated at that moment, which allowed the line to pass successfully. The sub_gain relies on has_subwoofer and also fails.

I've made the has_subwoofer to work explicitly calling my_zone.get_speaker_info() before it, but I believe there should be a guard code inside has_subwoofer as for is_soundbar
if not self.speaker_info:
    self.get_speaker_info()

I agree. Thanks for spotting the issue and identifying the fix.

Fix released in SoCo v0.30.4.


HTTP: Fix BIO_mem_d2i() on NULL mem BIO input

This fixes BIO_mem_d2i() on NULL mem BIO input and
related failure behavior of OSSL_HTTP_REQ_CTX_sendreq_d2i(), OCSP_sendreq_nbio(), etc.
Also removes the unused declaration of HTTP_sendreq_bio() from http_local.h
and simplifies OCSP_sendreq_bio().
Fixes #14322

Can this be approved now?

This pull request is ready to merge

Merged - thanks @t8m


[MRG] Fix edf reader when preload=False.

Closes https://github.com/mne-tools/mne-python/issues/3894
In the end, the solution was really simple. We should probably update the test files to have channels with different sampling rates.

Current coverage is 85.59% (diff: 100%)

Merging #3895 into master will decrease coverage by <.01%

@@             master      #3895   diff @@
==========================================
  Files           347        347
  Lines         61914      61913     -1
  Methods           0          0
  Messages          0          0
  Branches       9495       9495
==========================================
- Hits          52995      52994     -1
  Misses         6257       6257
  Partials       2662       2662

Powered by Codecov. Last update d00d27e...db69072

+1 for a test if you can find a tiny one.
cc @slasnista

I was able to modify the test file with edfbrowser. The new file is the same as the old one, but some of the channels are resampled to various frequencies. Maybe we can even get rid of the old test file.

how long does the test take?
how big is the file?
does the test fail on master?

The whole test_edf module takes 1 sec for me. It's basically the same file as before, but some of the channels are downsampled so it's a bit smaller (820kB) and yes, the test fails on master.

perfect !
+1 for merge then.

I don't like adding files to the repo for testing anymore. It's not sustainable from a repo bloat perspective. Can we add the file to mne-testing-data instead?

How about I just remove the old file? It's basically the same data. I think the clean up should be on it's own PR.

if you remove the old file it will remain in the commit history and will
not reduce the repo size.
mne-testing-data
is certainly the cleanest option.

Ok. testing-data updated.

thx @jaeilepp


Enhancement and Issue Notes.

Acceptance Criteria

[ ] I have identified different styles, enhancement issues added them in the issues list
[ ] I have resolved and opened  issues for required enhancements

Issues lists

[ ] Reading Section Contains dummy data. Configure it to fetch IDMS-tagged blogs from oknp website.
[ ] Smooth button for showcase in homepage
[ ] Explore and finalize the hero and IDMS for section images

@Zaymes  Here are some review feedbacks.

Logo not align

Remove some padding

Learn more link not clickable.

Good to have a hover effect, eg. the Background would be light green if user hover the containe

inconsistent hights on icons

These images do not look good, try with a simple clipart.

Make the whole container clickable and maybe add a hover effect as well with a background change.

Dropdown as a container view, maybe with a border or shadows.

Increase header container as main page.

@Zaymes  One last minor feedback, could you try another image here, and color one that matches with main color.

@sagargg dai can we go with this

Fixed all the major enhancements listed and closing this as done!


feat: Add 'Delete Catalog' feature in the catalog details page

Closes #37
https://github.com/user-attachments/assets/cfde7a34-a2c9-42b8-8037-851567c089a9
Thanks to @jamieknight-db for providing a nice baseline with the delete table PR. 😄

Could someone squash and merge this PR? I do not have permissions.
Thank you! 😄


WIP: Prototype debugging exercises for part 2, TDD

Addresses part two of TheOdinProject/ruby-exercises/issues/15

This is the problem description as a README


Open a new window if no suitable candidate to pick found

Hello! I'm using window-picker with neo-tree and configured it the way I always try to open a file with window-picker from the file tree. It doesn't work properly in a case, when there are no open windows except for the ones that I'm ignoring. In this case window-picker gives back a message No windows left to pick after filtering, but it'd be nice if it could open a new window in this case.

This is definitely something neotree author can implement. I might consider this in the future


[Bottom-navigation][android] Frame.topmost().navigate doesn't work when activity resumed

Hi,
On android if the app just start every think work as expected, but when the app is in background and then it resumed the Frame.topmost().navigate wont work until you change the tabs then the navigate will be triggered!
Please found this sample project

open the app and click on TAP ME
it is expected to navigate to the PAGE TEST 2 successfully
Go back  to home
put the app on background and reopen it
click on TAP ME: then the navigation will not occur any more!!

@farfromrefug did you have any idea about this behavior ?

@kefahB absolutely not . And i am sorry but i realy dont have time to investigate this. Hope you can

I tried for the whole day today but I really understand no think :)

@farfromrefug how can I get the source code in TS ? when I navigate to packages/bottom-navigation I dont see the sources code ! I mean there is no index.ios.ts, index.androis.ts....

it is in src. this is a monorepo. the packages folder is for the output odf the build

@farfromrefug I think I got the error but am not sure, the problem occur if the selectedView instanceof Frame.
When the app is loaded for the first time every think work as expected  selectedView.isCurrent() return true.
But when you click on home button and reopen the app selectedView.isCurrent() return FALSE ! I've tried to do some stuff with selectedView.setCurrent but not work for the moment !
Any Idea ?
Look here for the Frame

@kefahB thanks for investigating. i just dont understand your isCurrent reference. dont see that code

The code doesn't exist .. I've add during the investigation
const selectedView = newItem && newItem.content;
        if (selectedView instanceof Frame) {
            selectedView._pushInFrameStack();
            console.log("isCurrent", selectedView.isCurrent())
            console.log("navigationQueueIsEmpty", selectedView.navigationQueueIsEmpty())
            console.log("isUserInteractionEnabled", selectedView.isUserInteractionEnabled)
            console.log("isLayoutValid", selectedView.isLayoutValid)
            console.log("isLoaded", selectedView.isLoaded)
            console.log("_isInFrameStack", selectedView._isInFrameStack)
            if(!selectedView.isCurrent()) {
                selectedView.setCurrent(selectedView._currentEntry, 1);
            }
            console.log("isCurrent", selectedView.isCurrent())
            //selectedView._pushInFrameStack();
        }

@kefahB isCurrent() is not a correct test. it takes an argument. What you see : true => false is 100% normal


Update README.md - type in simulate

just a simple typo simulare->simulate

Awesome! Thank you so much for catching it and fixing it! 👏


Hello,metrics question.

Hello,How to improve PSNR as much as possible? Can you give me some direction???whether about datasets ,postprocess or networks?

There are many related papers for improving PSNR. You are advised to have a look at these papers.

thx


udev issues causes hangs and docker crashing

Have you read and understood this part of the readme?
[X] YES
[] NO
Issue description: unraid and other Linux Distro UDEV ISSUES
This is not intended to be a bug that requires work by rix1337 or changes in the docker. This is an issue with Docker hosts that appears to be prevalent across multiple distros (Manjaro, Arch, Fedora, Unraid, and possibly more). This is merely to document the issue and the solution for those possibly experiencing problems and possibly believe the issue could be the docker.
There is a udev rule for persistent storage that can cause hanging upon entering specific video disc into drives.
If you wish to fix/correct this problem without altering the core udev files you may follow these instructions:
Copy the current persistent-storage.rules to the directory for custom rules.
sudo cp /usr/lib/udev/rules.d/60-persistent-storage.rules /etc/udev/rules.d/60-persistent-storage.rules
sudo vim /etc/udev/rules.d/60-persistent-storage.rules

In the file you should be looking for this line:
# probe filesystem metadata of optical drives which have a media inserted
KERNEL=="sr*", ENV{DISK_EJECT_REQUEST}!="?*", ENV{ID_CDROM_MEDIA_TRACK_COUNT_DATA}=="?*", ENV{ID_CDROM_MEDIA_SESSION_LAST_OFFSET}=="?*", \
  IMPORT{builtin}="blkid --offset=$env{ID_CDROM_MEDIA_SESSION_LAST_OFFSET}"
# single-session CDs do not have ID_CDROM_MEDIA_SESSION_LAST_OFFSET
KERNEL=="sr*", ENV{DISK_EJECT_REQUEST}!="?*", ENV{ID_CDROM_MEDIA_TRACK_COUNT_DATA}=="?*", ENV{ID_CDROM_MEDIA_SESSION_LAST_OFFSET}=="", \
  IMPORT{builtin}="blkid --noraid"

Those IMPORT lines cause issues so we need to replace them with a line that tells udev to end additional rules for SR* devices:
# probe filesystem metadata of optical drives which have a media inserted
KERNEL=="sr*", ENV{DISK_EJECT_REQUEST}!="?*", ENV{ID_CDROM_MEDIA_TRACK_COUNT_DATA}=="?*", ENV{ID_CDROM_MEDIA_SESSION_LAST_OFFSET}=="?*", \
  GOTO="persistent_storage_end"
##  IMPORT{builtin}="blkid --offset=$env{ID_CDROM_MEDIA_SESSION_LAST_OFFSET}"
# single-session CDs do not have ID_CDROM_MEDIA_SESSION_LAST_OFFSET
KERNEL=="sr*", ENV{DISK_EJECT_REQUEST}!="?*", ENV{ID_CDROM_MEDIA_TRACK_COUNT_DATA}=="?*", ENV{ID_CDROM_MEDIA_SESSION_LAST_OFFSET}=="", \
  GOTO="persistent_storage_end"
##  IMPORT{builtin}="blkid --noraid"

You can comment these lines out or delete them all together, then replace them with the GOTO lines. You may then either reboot OR reload the rules. If you're using Unraid, you'll need to edit the the original udev rule and reload.
root@linuxbox# udevadm control --reload-rules && udevadm trigger

Thank you for documenting this. #98 is merged. Closing this now.


Sectigo and cert-manager(v1.5.4) - error creating new order: 500 urn:ietf:params:acme:error:serverInternal

Hi,
I have the following setup to use cert-manager v1.5.4 with Sectigo and but receiving error at the time of Order. Can anyone please help/advise or provide any existing working setup for Sectigo-Cert-Manager (v1.5.4). Note: We have a working setup with cert-manager v0.10.0 with sectigo in some of our older environments.
Versions:
Cert-Manager - v1.5.4
Kubernetes - v1.21
Following setups were completed:

Created privateKeySecretRef using eab-acme-tool (which takes inputs of url, keyid, hmac)

Created clusterissuer
apiVersion: cert-manager.io/v1 kind: ClusterIssuer metadata: name: clusterissuer spec: acme: email<EMAIL_ADDRESS>server: https://acme.sectigo.com/v2/XXX privateKeySecretRef: name: sectigo-secret solvers: http01: ingress: class: nginx

On trying to create certificate, we are seeing this error in logs of cert-manager:
cert-manager/controller/orders "msg"="syncing item" "key"="grafana/monitor.xxxxx.dev-tls-ckz7c-1392367824" cert-manager/controller/orders "msg"="Creating new ACME order as status.url is not set" "resource_kind"="Order" "resource_name"="monitor.xxxxx.dev-tls-ckz7c-1392367824" "resource_namespace"="grafana" "resource_version"="v1" cert-manager/controller/orders "msg"="order URL not set, submitting Order to ACME server" "resource_kind"="Order" "resource_name"="monitor.xxxxx.dev-tls-ckz7c-1392367824" "resource_namespace"="grafana" "resource_version"="v1" cert-manager/controller/orders "msg"="build set of domains for Order" "resource_kind"="Order" "resource_name"="monitor.xxxxx.dev-tls-ckz7c-1392367824" "resource_namespace"="grafana" "resource_version"="v1" "domains"=["monitor.xxxxx.dev"] cert-manager/controller/orders "msg"="build set of IPs for Order" "resource_kind"="Order" "resource_name"="monitor.xxxxx.dev-tls-ckz7c-1392367824" "resource_namespace"="grafana" "resource_version"="v1" "domains"=["monitor.xxxxx.dev"] cert-manager/controller/orders "msg"="skipping updating resource as new status == existing status" "resource_kind"="Order" "resource_name"="monitor.xxxxx.dev-tls-ckz7c-1392367824" "resource_namespace"="grafana" "resource_version"="v1" cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="error creating new order: 500 urn:ietf:params:acme:error:serverInternal: The server experienced an internal error" "key"="grafana/monitor.xxxxx.dev-tls-ckz7c-1392367824"

I could see that is is failing in order stage. Not exactly sure why it is giving me an internal server error.

We slightly changed how cert-manager performs ACME challenges in cert-manager 1.6 to address an ambiguity in the ACME spec that caused issues with some ACME servers. Could you try the beta (installable with helm as normal) and see if that fixes it?

@jakexks can you please suggest which version of cert-manager you want me to try ? Is it v1.6-beta ?


Add async-profiler to docker images

Add profiler(https://github.com/jvm-profiling-tools/async-profiler) to docker image for further investigation on performance bottleneck.
Signed-off-by: cheyang<EMAIL_ADDRESS>

Can one of the admins verify this patch?

Codecov Report

Merging #12851 (d5fc811) into master (2923f93) will decrease coverage by 20.58%.
The diff coverage is n/a.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2923f93...d5fc811. Read the comment docs.

alluxio-bot, merge this please


Allow docstring when using terse

This PR makes it possible to add docstrings to structs using the @concrete terse ... pattern.

Codecov Report

Merging #9 (6a5b170) into master (dd869e0) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master        #9   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines           97        97
=========================================
  Hits            97        97

Impacted Files
Coverage Δ

src/ConcreteStructs.jl
100.00% <ø> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update dd869e0...6a5b170. Read the comment docs.

Awesome! Thanks for this.


ORC file sampler is not able to identify the date data type

Please provide a detailed title (e.g. "Broker crashes when using TopN query with Bound filter" instead of just "Broker crashes").
Affected Version
We observed the issue from Druid version 26.0.0 and the same issue is there on the latest version which is 29.0.1
on Version 0.22.1 we are not seeing this issue.
Description
we encountering an issue when trying to parse the ORC file created from a Hive external table on Druid version 27.0.0. The error message "Failed to sample data: Unhandled type: COMPLEX" is displayed. However, I can load the data into the cluster using the pre-created JSON spec, and the data is being received correctly. The error only occurs during the Parse data step. Interestingly, I can parse the same file on Druid version 0.22.1.
(The JSON spec used to load the data on version 27 was created from version 0.22.1)
we have also tried the latest version (29.0.1)of Druid, but we are still encountering the same error.
in this case it is an issue with the date type. our ORC reader returns it as a Joda DateTime object. our auto type detection code is not able to figure out what to do with this. the type detection code is expecting to see more primitive types like strings, numbers, & arrays. what changed in recent druid versions is that the sampler started using auto type detection.

@asdf2014 Is there any progress or update on this issue ? Which version we can expect this to be fixed ?


[FLINK-20188][Connectors/FileSystem,Documentation] Add Documentation …

…for new File Source

What is the purpose of the change
(For example: This pull request makes task deployment go through the blob server, rather than through RPC. That way we avoid re-transferring them on each deployment (during recovery).)
Brief change log
(for example:)

The TaskInfo is stored in the blob store on job creation time as a persistent artifact
Deployments RPC transmits only the blob storage reference
TaskManagers retrieve the TaskInfo from the blob cache

Verifying this change
Please make sure both new and modified tests in this PR follows the conventions defined in our code quality guide: https://flink.apache.org/contributing/code-style-and-quality-common.html#testing
(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (100MB)
Extended integration test for recovery after master (JobManager) failure
Added test that validates that TaskInfo is transferred only once across recoveries
Manually verified the change by running a 4 node cluser with 2 JobManagers and 4 TaskManagers, a stateful streaming program, and killing one JobManager and two TaskManagers during the execution, verifying that recovery happens correctly.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@MartijnVisser I have made a series of modifications according to your suggestions, and you can see if they meet your requirements

@MonsterChenzhuo Sorry for not replying earlier. I've been looking at your PR but I still think we could have improved it a bit more. I took the liberty to cherry-pick your commit and added/changed some things to the overall structure. You can see my draft PR here https://github.com/apache/flink/pull/18288