SocketTimeoutException

always give SocketTimeoutException . I have dwonloaded same file on mobile browser and with another code but when i am using FileDownloader library then error throw during start downloading
java.lang.RuntimeException: SocketTimeoutException
i have also set timeout time
FileDownloader.init(this,
new FileDownloadHelper.OkHttpClientCustomMaker() { // is not has to provide.
@Override
public OkHttpClient customMake() {
// just for OkHttpClient customize.
final OkHttpClient.Builder builder = new OkHttpClient.Builder();
// you can set the connection timeout.
builder.connectTimeout(3*60 * 1000, TimeUnit.MILLISECONDS);
// you can set the HTTP proxy.
builder.proxy(Proxy.NO_PROXY);
// etc.
return builder.build();
}
});
Please help....
Thanks

Sorry, this is Http-Connection Error, Please change your Net-Environment and retry.


Whitelist editor specific theme tags

block-styles and wide-blocks are two newly approved theme tags. They should be whitelisted.

it looks like the api call internally to fetch the tags includes them, perhaps the call is cached?

The call is cached so it could be that.
https://github.com/WPTRT/theme-sniffer/blob/feature/use-namespace/src/api/class-template-tags-request.php#L39

Should be fixed in the latest release


Making both ascending and descending ordering default option

Currently to allow ordering results in ascending and descending order one must explicitly add names twice:
class Meta(object):
        model = models.MyModel
        fields = [
            'name',
        ]
        order_by = [
            'name',
            '-name',
        ]

Now it doesn't feel right - asc/desc sorting (almost) always comes in pairs. What would you think about modifying default behaviour by offering those sorting directions at once?

I'm going to close this as Out of Scope for the moment. Happy to consider documented, tested pull requests. We may have capacity to reconsider in the future.


[improve][broker] Add gzip compression support for /metrics endpoint

Fixes #16321
Replace the PR: https://github.com/apache/pulsar/pull/16888

Regarding the comment by @asafm in https://github.com/apache/pulsar/pull/16888#issuecomment-1233894144 , I think that all endpoints would benefit of compression. Having the compression support doesn't mean that the response will always be compressed, it's only if the client sends a Accept-Encoding: gzip header.

I tested the Prometheus metric with 1000 topics and enabled the compression to get 33x data saving.
# curl -H 'Accept-Encoding: gzip' -o kk0.log.gz http://localhost:8080/metrics/
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  927k    0  927k    0     0  1910k      0 --:--:-- --:--:-- --:--:-- 1941k
# curl -o kk1.log http://localhost:8080/metrics/
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 33.2M    0 33.2M    0     0  73.1M      0 --:--:-- --:--:-- --:--:-- 74.4M
# ll -lrt |grep kk
-rw-r--r--     1 hangc  staff   928K Nov 28 18:46 kk0.log.gz
-rw-r--r--     1 hangc  staff    33M Nov 28 18:46 kk1.log

Due to the response being compressed according to the client request header, I think we can add the GzipHandler for all the endpoints instead of the metric endpoint.
However, the Prometheus server sends a fetch metric request with Accept-Encoding: gzip header, which will fetch the metrics with compression. https://github.com/prometheus/prometheus/issues/12319. It may cause the Prometheus server to run into high CPU usage. https://github.com/prometheus/blackbox_exporter/issues/270.
For the master branch of Prometheus supports disabling compression in the client request header https://github.com/prometheus/prometheus/pull/13166, I'm not sure if we need to add a flag to control whether the Pulsar HTTP server supports compression or not.  @lhotari @asafm @codelipenghui Do you guys have any ideas?

@xuesongxs Please rebase the master.

I tested the Prometheus metric with 1000 topics and enabled the compression to get 33x data saving.
# curl -H 'Accept-Encoding: gzip' -o kk0.log.gz http://localhost:8080/metrics/
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  927k    0  927k    0     0  1910k      0 --:--:-- --:--:-- --:--:-- 1941k
# curl -o kk1.log http://localhost:8080/metrics/
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 33.2M    0 33.2M    0     0  73.1M      0 --:--:-- --:--:-- --:--:-- 74.4M
# ll -lrt |grep kk
-rw-r--r--     1 hangc  staff   928K Nov 28 18:46 kk0.log.gz
-rw-r--r--     1 hangc  staff    33M Nov 28 18:46 kk1.log

Due to the response being compressed according to the client request header, I think we can add the GzipHandler for all the endpoints instead of the metric endpoint.
However, the Prometheus server sends a fetch metric request with Accept-Encoding: gzip header, which will fetch the metrics with compression. prometheus/prometheus#12319. It may cause the Prometheus server to run into high CPU usage. prometheus/blackbox_exporter#270.
For the master branch of Prometheus supports disabling compression in the client request header prometheus/prometheus#13166, I'm not sure if we need to add a flag to control whether the Pulsar HTTP server supports compression or not. @lhotari @asafm @codelipenghui Do you guys have any ideas?

Since io.prometheus.client.exporter.HTTPServer supports returning compresses responses based on headers, Pulsar shouldn't be different.

I still have pending comments from 2022 @hangc0276 :)

Replaced by #21667


Fix order of code comments in GULSwizzlingCache

The order of the code documentation params and the the arguments of the methods cacheCurrentIMP:forNewIMP:forClass:withSelector: and cacheCurrentIMP:forNewIMP:forClass:withSelector: doesn't match. This is fixed now by changing the order of the code documentation.

I accepted the CLA with my GitHub user name philipphofmann. Can you rerun the check please?


[Request for External/Coderefactoring] Page 6510 - "Item Tracking Lines"

Hello,
I would like to create a pageextension of the Page 6510 "Item Tracking Line".
To access the temporary records of the global variables there are the functions GetVariables and SetVariables. The parameter "var SourceQuantityArray2: array[3] of Decimal" in the function GetVariables has only 3 dimensions. However, the global variable on page 6510 has the dimension 5, which means that there are constellations where the CopyArray command runs on a runtime error. The dimension of the parameter should be increased to 5.

As an even better alternative it would be useful to mark all global variables (or parts of them) as "protected var", so that they would be directly accessible from a page extension.

This would have the advantage that you could do everything without the functions GetVariables and SetVariables and you still have access to all necessary variables.
A consideration in one of the next cumulative updates would be great.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Implement CREATE TABLE LIKE

This should copy the columns and table properties from the old table and create a new table with the given name and the same columns and table properties.
Example: CREATE TABLE my_new_table (LIKE my_old_table)

@suyucs is going to work on this

The proper syntax is CREATE TABLE <table name> (LIKE <table name>)

Technically speaking, it supports multiple LIKE clauses and it can be interleaved with regular column definitions, but let's not worry about that for now

The relevant part of the SQL grammar is:
<table definition>
  : CREATE <table scope>? TABLE <table name> <table contents source>
      (WITH <system versioning clause>)?
      (ON COMMIT <table commit action> ROWS)?
  ;

<table contents source>
  : <table element list>
  | <typed table clause>
  | <as subquery clause>
  ;

<table element list>
  : <left paren> <table element> ( <comma> <table element> )* <right paren>
  ;

<table element>
  : <column definition>
  | <table constraint definition>
  | <like clause>
  ;

<like clause>
  : LIKE <table name> <like options>?
  ;

I think we should also support the common non parenthesized form, just like we do for AS SELECT.

I'd rather we didn't try to jam that in for now. The semantics of LIKE are different from AS SELECT. For instance, you can do:
CREATE TABLE foo (
    xxx VARCHAR,
    LIKE bar,
    yyy BIGINT
)

Trying to support the non parenthesized form will require some contortions in the grammar, potentially introduce ambiguities or make it harder to add the full syntax later.


Syntaxis error (Folie 2.10 on W10 & RasPi)

New in Folie 2.10 (on W10) is a syntaxis error before the serial port select.
After that everything is OK
Folie v2.10

? De syntaxis van de bestandsnaam, mapnaam of volumenaam is onjuist.
1
Enter '!help' for additional help, or ctrl-d to quit.
[connected to COM9]
Mecrisp-Stellaris RA 2.3.3 with M0 core for STM32L053C8 by Matthias Koch
64 KB <jnz> 3239023E ram/flash: 4928 20352 free ok.

Running 2.10 on RasPi same result:
Folie v2.10
no such file or directory
Select the serial port:
  1: /dev/ttyACM0
  2: /dev/ttyAMA0
? 1
Enter '!help' for additional help, or ctrl-d to quit.
[connected to /dev/ttyACM0]
Mecrisp-Stellaris RA 2.3.3 for STM32F103 by Matthias Koch
128 KB <jnz> 31395E08 ram/flash: 19256 34940 free ok.

Yikes. Looks like I broke something.

If I start Folie with -p COM9 it's OK.
So somewhere an unspecified port is not handled properly.

This is probably not Windows-related, it just happens that goroutine-order brings out this bug.
I will keep this open for now, it needs to be revisited once I have done a fairly major re-design of the goroutines in Folie to handle some other cases properly (Linux serial re-open fails to re-init properly).

I think the Linux case has been fixed, could you do a git pull and see how it behaves on Windows?
Note that you may need to re-upload a new image if you're using the USB-driver in Mecrisp. Its back-to-back bug has been fixed, and the workaround has been removed from the latest Folie code.

I can/will run a test on W10 tomorrow evening

On RasPi everything seems to be OK now.
Also on W10 the syntaxis error now seems to be disappeared and startup looks good now.
But sometimes the port selection table is not printed. Typing the correct nr. ( for me it's 1) however starts everything as expected:
Folie v2.10-test
Select the serial port:

1
Enter '!help' for additional help, or ctrl-d to quit.
[connected to COM9]
Mecrisp-Stellaris RA 2.3.3 with M0 core for STM32L053C8 by Matthias Koch
64 KB <jnz> 3239023E ram/flash: 4928 20352 free ok.

Ah, thx - yeah, the startup order is still not quite right. Baby steps...

Port selection should work better now.

I agree. Just tested opening of folie 2.10 on W10 some 20 times with a 100% OK-score. It looks like you have solved this one. Great!


Test Items to be Used in Building the Dataset

Describe the aim of this enhancement
Add test items for building the dataset
Describe the solution you'd like

[ ] Get the original document of:

so that it can be added (copy pasta) and test runs can be done

[ ] Add the test items extracted from the above document to a json file
[ ] Add command to generate quiz from the json file
[ ] Add command to export quiz taking data for the above scenario, in csv format
[ ] Add command to reset quiz taking data

@ralf-t @xtian18 @XSeed21 @jebjebs anong set gagamitin naten sa data gathering
from CCS 4980 - CHAPTERS 1-3.gdoc

from 2nd sem thesis.gdoc

Set? I thought iisang exam lang ginawa naten na ipagagamit for all participants?

by set i mean yung lumang set ba or yung bago/ updated

Kung ano siguro napasa natin sa panel 😖 Di ko knows yung bago sry

oks hanapin ko lang yung original docu


Error when signing up to the mail list

I was hoping to get added to the mail list and look out for any work I could support around COVID-19 and brining awareness but I was got an internal error when trying to sign up

Hi @p0onage,
The allready project hasn't been active for quite a few months (at least new development hasn't been happening)
If you contact Richard Campbell directly via twitter he may be organising something that he needs help with.

His Twitter is (@richcampbell): https://twitter.com/richcampbell?s=09

Thanks @jonparker i'll drop a message


JSON patching is hard

git push github HEAD:refs/heads/dev/migrie/b/json-patching-is-hard thanks @DHowett-MSFT for putting this out there

user settings is "{}" -- AppendDynamic transforms that into , { guid, name commandline }, {guid, name, ...}{}

user settings is {"profiles":[]} gets transformed into something lovecraftian too

Let's add some tests for these, and fix them.

meh, literally nobody's reported this. Moving it to 1.1

Since we're not json patching anymore, I'm moving this to closed


gnome3.at-spi2-core: Set environment variable NO_AT_BRIDGE=1 if disabled

As suggested by @jtojnar and @abbradar in #16327.
Motivation for this change
See https://github.com/NixOS/nixpkgs/issues/16327#issuecomment-315729994
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

Hmm, the evaluation still fails
https://gist.github.com/3cb5e6fcc5b61fc40ed9def7e104efb1

Yeah, the parentheses around the negation were missing...

Also added the missing parentheses around the two mkIf … {…} expressions. Now all checks are passing.


Upgrade SimpleWebServer to version 2.1.1

Currently Clipper uses SimpleWebServer(Oct 25, 2016) for http serving.
We need to upgrade this module to resolve some bugs and support keep-alive connection.
So we applied all patches except of some to reach version 2.1.1 (May 27, 2017).
Diff between SimpleWebServer v2.1.1(left). and SimpleWebServer(right) in this PR is here.

applied patch list

Nov 7, 2016: Fixes #82: wrong reset method called in ::start
Nov 10, 2016: Fixed crash if server instance gets deleted after the call to io_serv
Nov 23, 2016: Fixes #86: can now set timeout on client requests
Nov 23, 2016: Minor timeout source cleanups
Nov 23: 2016: Simplified Server::parse_request
Dec 4, 2016: string::substr comparisons replaced by string::compare
Dec 13, 2016: compile clean with gcc 4.6.3
Dec 19, 2016: Added client verification when a verify file is passed to Server<HTTP
Dec 19, 2016: Added error reporting through on_error std::function
Dec 19, 2016: Minor cleanup
Dec 19, 2016: Minor cleanup
Dec 29, 2016: Cleanup of server-constructors. Previous constructors have been marked
Dec 29, 2016: Bugfix for last commit: config.timeout_content now correctly set in old constructor
Dec 30, 2016: Fixed DEPRECATED macro in cases where it is already defined
Dec 31, 2016: Case insensitive header cleanup. Also cleanup and additions to parse_test
Jan 1, 2017: Added on_upgrade for cases where one wants to handle connection upgrades
Jan 11, 2017: Fixed Boost.Regex workaround in regex_orderable. Fixes #100
Jan 24, 2017: Possible implementation for fixing #106
Jan 24, 2017: Renamed close_connection_after_send to close_connection_after_response
Feb 5, 2017: Added query string parsing and member to request
Feb 5, 2017: Travis CI build failed
Feb 14, 2017: remove locale dependent stof()
Feb 27, 2017: If query string is present then cut it from the reqeust path so find
May 6, 2017: Added support for request header Connection: keep-alive (see #123)
May 27, 2017: Finished query string parsing implementation (PR #109)
May 27, 2017: Fixed g++ error in Server::Request::parse_query_string

excluded patch list

Jan 2, 2017: Code simplification: got rid of opt_resource at minimal cost
Jan 2, 2017: Added warning to Server::resource
Jan 3, 2017: Removed unnecessary public

Can one of the admins verify this patch?

jenkins ok to test

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/1120/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/1122/
Test FAILed.

@withsmilo The formatter can be a little finicky. I just formatted and pushed to this branch, so it should clear the format checker now.

@dcrankshaw
Thank you. The formatter seems to have varying behavior across versions or systems.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/1123/
Test FAILed.

I will check run_unittests.sh.

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


PartialLoop, Entities and HydratingResultSet

Hey Team,
I'm having an issue and I'm not sure if it's a bug or a feature (which is rather annoying). Essentially I'm using HydratingResultSet to iterate through some database output and returning this to my view to be iterated through.
Generally, I'd foreach over this and be able to call the entity methods such as $this->getFirstName() to get the users name.
However, I thought to save some code I'd use a partialLoop.
Essentially partialLoop converts the output to an array using iterator_to_array (that's fine) but then flattens by entity object which changes my key cases.
Here's the iterator_to_array item as I'd expect it. (shortened for example)
[0]=>
  object(Users\Entity\Users)#295 (17) {
    ["firstName":protected]=>
    "Aaron"
    ["lastName":protected]=>
    "Test"
  }

Now, after passing $users to partialLoop
<?= $this->partialLoop ('partial\user-row', $users) ?>

We get the following in the loop
object(Zend\View\Variables)#301 (2) {
  ["strictVars":protected]=>
  bool(false)
  ["storage":"ArrayObject":private]=>
  array(17) {
    ["first_name"]=>
    "Aaron"
    ["last_name"]=>
    "Test"
  }
}

It sounds like you were using ClassMethods hydrator with HydratingResultSet; the default behaviour of that hydrator is to convert camel-case to underscore-separated (https://github.com/zendframework/zend-hydrator/blob/master/src/ClassMethods.php#L49).
@Maks3w this can be closed


Improve style of pages

[ ] Sending cart form
[ ] Confirmation view
[ ] Valentine card
[x] 404 page

[ ] Favicon
[ ] Mobile versions


Error building examples/bzlmod

cd examples/bzlmod

bazel build //root
ERROR: Skipping '//root': error loading package 'root': Unable to find package for @bazel_skylib//rules:write_file.bzl: The repository '@bazel_skylib' could not be resolved: Repository '@bazel_skylib' is not defined.
WARNING: Target pattern parsing failed.
ERROR: error loading package 'root': Unable to find package for @bazel_skylib//rules:write_file.bzl: The repository '@bazel_skylib' could not be resolved: Repository '@bazel_skylib' is not defined.
INFO: Elapsed time: 0.061s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded)
    currently loading: root

How strange: I only just saw this issue today. I'm not sure why I'm not subscribed automatically to issues against my own repository. I'm looking into that now.
I have a patch ready for merging that sets this repository to using the recently released Bazel version 7.0.0, which enables use of Bazel modules by default. As part of it, I removed the top-level .bazelrc file, having found it now empty after finally removing the command-line flag to enable use of Bazel modules. Given that, I don't think that adding a second .bazelrc file as you proposed in #9 will be necessary.

LGTM


Fix rspec eventually bug

Created from https://github.com/mojotech/dill/pull/103

:shipit: (feel free to merge @adsteel)

@david Hmm... It doesn't like that this error class is defined. I can't require 'rspec' either. Any suggestions? I could store the classes as strings and convert them to classes in the rescue block, but that seems a bit dirty.

@adsteel perhaps you could add that class only if RSpec is defined? I'd rather avoid using strings.


Please consider adding an alias from --auto-correct to --autocorrect

Hi there,
Please consider adding an alias from --auto-correct to --autocorrect so
that rubocop can be invoked via --autocorrect as well. The middle -
is a bit awkward for me to type, I would like to be able to also use
--autocorrect in addition to this.
If this is not to your liking, just close the issue request here, no problem
at all.
Thank you for reading!

We already have -a, as an alias for --auto-correct, so adding one more seems kind of redundant to me. @jonas054 Thoughts?

Agreed. The long options are for readability, the short for ease of typing. A third seems redundant.


Add a flag to control usage of min_progress_size in TCP for receive buffer allocation

Add a flag to control usage of min_progress_size in TCP for receive buffer allocation. This could play an important role if the receiver is under high memory pressure.

Let's add something to tcp_posix_test.cc to prove that this works.

Let's add something to tcp_posix_test.cc to prove that this works.

Added a min_progress_size to grpc_endpoint_read in tcp_posix_test.cc


Python2 functions in Windows 18.1.1 CAVE version

Derived parameter functions that have python2 coding in them fail in this version of CAVE. The results in several fields not plotting for a specific example, bulk shear vectors. See attached image of output.
conda 4.8.2
python 3.7.6
numpy 1.15.1
jep 3.8.2
I also added the miniconda3 python.exe to the python interpreter in CAVE.
Thoughts?

I'd like to add that if I copy the Python3 versions of the derived parameter files into my user folder in ../caveData/common/user//derivedParameters/<functions,definitions,python> it is essentially yelling at me that something is not in the package.

Is there a way to have CAVE not download localization files from a server and instead reference the data in the Unidata/AWIPS CAVE folder on Windows? Or is there a SITE that I can put in the EDEX server that has updated localization files?
Thank you!


Url encoding of backtick ("`") character in query strings

I have a query string that includes a backtick character in it, and the server I'm communicating with expects this character to not be percent encoded. However, superagent encodes it. Superagent's behavior is correct according to RFC 3986, but incorrect according to the WHATWG URL spec, which tracks what browsers do. My guess is that it'd be generally more useful to follow the browser behavior, but I'd at least like to see an option to be able to customize the behavior to match the browser; right now, there doesn't seem to be any way for me to use superagent to make the request with the unencoded character.
I'd note that superagent already follows browser behavior wrt percent encoding the single quote character, which RFC 3986 says shouldn't be percent encoded. This means it's also impossible to make a request with the single quote unencoded through superagent, even though that would be RFC 3986-compliant. Not being able to use either the backtick or the single quote makes it really hard to build nice DSLs for use in query strings.

To be clear, this happens even when I call request.query(String) with my unencoded string, and a bit of debugging reveals that the issue goes all the way down to node's built-in url.parse (i.e., url.parse("http://example.com/?test=`") returns { ..., query: "test=%60" }).
Node's solution to this issue is to offer both the RFC 3986-compliant url.parse and the WHATWG URL API in core, so perhaps superagent should simply surface both of those options? Note that using the built-in new (require('url').URL)("http://example.com/?test=").search` does leave the backtick unescaped.

We depend on encodeURIComponent("`") which returns '%60'.
It's not clear to me whether WHATWG URL recommends unescaped "`" or merely tolerates it as a recoverable error. The path encode set contains fragment set, which contains backtick.
In superagent you can set query as a string req.query("foo=`"), and IIRC it won't escape it in the Node version (in the browser version it depends on what the browser enforces).
But in general I've got a feeling your server depends on a problematic feature. Given decades-old mess of fragmented specs for URL/URI/IRI the server should be prepared to support the lowest common denominator.

We depend on encodeURIComponent("") which returns '%60'. We still support IE, so we can't easily switch to the URL API.... In superagent you can set query as a string req.query("foo="), and IIRC it won't escape it in the Node version (in the browser version it depends on what the browser enforces).

The issue here isn't encodeURIComponent; even in the Node version of superagent with req.query("foo=`"), the backtick gets escaped, because of superagent's internal use of url.parse. I'm pretty sure this is the problematic call/the spot where node's WHATWG API could be used instead.

It's not clear to me whether WHATWG URL recommends unescaped "`" or merely tolerates it as a recoverable error. The path encode set contains fragment set, which contains backtick.

I agree that the spec's pretty hard to follow. I don't think the path encode set is relevant, though, as that seems to only be referenced in the path processing steps, not the query ones. My best reading is that the key bit is the query state of the parser, where the spec explicitly doesn't include backtick as one of the characters that gets percent encoded during parsing. (Normally, I'd expect encoding to be part of the serialization step, but that's not how the spec is structured; the serialization is just dumb concatenation, with the percent encoding having already happened during parsing/construction. Either way, the point is that, under WHATWG URL, serialize(parse(http://exmaple.com?t=`)) leaves the backtick as is.)

But in general I've got a feeling your server depends on a problematic feature. Given decades-old mess of fragmented specs for URL/URI/IRI the server should be prepared to support the lowest common denominator.

I kind of agree with this, and I'm probably going to switch the server to a new delimiter. However, let me give a bit more context. In my use case, I need a way to delimit literal strings from other query param data, and I think a reasonable approach would be to allow the client to delimit the string with either literal single quotes (for RFC 3986-compliant clients, which should leave these unencoded) or by backticks (for WHATWG based clients, like browsers, that will encode the single quotes but not the backticks). However, even this scheme of allowing either delimiter doesn't work with superagent, because it unconditionally encodes both characters. To me, that seems pretty bad/frustrating.
I think it's reasonable for new client libraries to correctly support at least one of RFC 3986 or WHATWG URL. Superagent, by encoding both backtick and single quote, is supporting neither. This isn't really it's fault — it all goes back to url.parse encoding single quotes in violation of RFC 3986, but that's probably good for security (that's why browsers do it), so I wouldn't suggest changing that in Node core even if it weren't a big breaking change. The upshot of all this, though, is that it's still impossible to make a bunch of useful requests from superagent. That's what I'd like to see some escape hatch for.

You're effectively making quotes a new special character, and creating your own new syntax for the query string. Consider using something else, e.g. double URL-encode or your own escaping within query string values. Maybe use \t as a delimiter? Or if you're adventurous, NUL (%00).

You're effectively making quotes a new special character, and creating your own new syntax for the query string.

Not sure I follow; single quotes already are a special character under RFC 3986 — they're part of the sub-delims set, which is for unencoded use in query strings precisely to enable custom DSL syntaxes like this. That's my point...

It's not impossible. You can have any query syntax you like with:
req.get("http://foo").query("``````````")

This sends 'GET /?`````````` HTTP/1.1\r\nHost: foo\r\nAccept-Encoding: gzip, deflate\r\nCookie: \r\nConnection: close\r\n\r\n'

I've checked superagent's code. As far as superagent's own code goes, and it carefully preserves encoding of both ' and ` when you use .query(""). It all breaks due to Node's url.parse(). Node's http module requires parsed URL, so that's hard to avoid. The WHATWG parser was added in 7.0, so we won't be able to use it until April 2019. I'm reluctant to add another 3rd party parser just to support such an edge case.

Node's http module requires parsed URL, so that's hard to avoid.

Ahh, I didn't know this. Definitely makes things trickier.

The WHATWG parser was added in 7.0, so we won't be able to use it until April 2019 (6.0 EOL). I'm reluctant to add another 3rd party parser just to support such an edge case.

Fair enough. Would it be possible to do some very minimal post-processing on the result of url.parse to add back the unescaped versions of any ' or ``` that were present in the .query() arg?

I've used `` ` ``

Is it allowed to have unescaped '/` in the path? path.replace(/%60/g,'`') may be an OK solution,

Yeah, the above obviously isn't as simple as a one-liner; that said, it doesn't seem too bad to me. Is there something in particular that bothers you about it?
Also, just to clarify, the above snippet could be used across the board, without superagent importing require("url").URL at all. (That is, I didn't mean to suggest importing the WHATWG stuff conditionally and then falling back to the above; that would be needless complexity and open the door to bugs caused by WHATWG URL doing other subtle things that the non-WHATWG-superagent still wouldn't do.)
If the above snippet were implemented, it could get applied to all requests unconditionally (i.e., no need for a user facing option either) because applying it unconditionally doesn't actually take away any expressive power; a user who wants the escaping can still get it (by escaping the ` before passing it in). Also, in practice, applying it automatically is likely to actually increase interop, as it's what browsers do, and I imagine pretty much every server should be able to accept requests from browsers.
That said, applying this automatically would technically be a breaking change, so it probably should live behind a user opt-in option just until the next major version.

@kornelski Any more thoughts on this?

It seems that url.parse() is guilty here, so it should be changed. You should probably raise this issue with the Node core, but since it's a stable API they probably won't like the idea of changing it.
I'd be OK with moving to the WHATWG parser, except for the pain of Node 6 compatibility. I'm worried that conditional require() will have nasty side effects in bundlers (we already get super weird bug reports about them).
The workaround you proposed is narrow (requires query as a string) and little bit on the convoluted side. It feels like tech debt for a solution that you will be the only person in the world to ever use.

OK, if you maintain it, I can accept the change :)

It's a deal :) I'll work up a PR tomorrow or Friday.
After that, how do you want to me to handle maintenance? I imagine you'd just tag me if/when any relevant bugs come up?
Also, for the PR, how do you want to land it: as a major version bump, or by adding an opt-in option to request.query? Unless there's some big cost to releasing a new major, I'd strongly prefer to do that; an option would have no good reason to exist long-term and would be a big API kludge. (As I mentioned earlier, if a user wants the old behavior, they can get it with request.query(oldInput.replace(/`/g, '%60')) — no option needed.)

I've just bumped major, which I plan to release on April 30th

Cool. So, I imagine that means that, if I get you the PR ASAP, it can go out with that release?

Yes

Closed by #1369.


Remove annoying blinking cursor from Loading the future

Resolves issue: https://github.com/stratisproject/Breeze/issues/252

@nopara73 We are not using the CSS files defined in the components, instead we are using SCSS to do the design.
You can add the CSS line in Breeze.UI/src/scss/_custom.scss
After that run: npm run build:styling, it will generate the new styles.css we are using.
If u need anything ping me on Slack.

@dev0tion I don't succeed.

@nopara73 shall I do it?

@dev0tion Yes, please. I tried to solve all the UI issues open yesterday and today, but I was only able to do just a small percentage of it

Done in #271


Updated README

Swapped the npm cache verify around (line 130). Commented out the npm cache clean for npm version older than 5.

I signed it!
Kind Regards,
Jose Estrella
(978) 798-2677
<EMAIL_ADDRESS>On Sat, Feb 17, 2018 at 8:42 AM, googlebot<EMAIL_ADDRESS>wrote:

Thanks for your pull request. It looks like this may be your first
contribution to a Google open source project. Before we can look at your
pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/
https://cla.developers.google.com/ to sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll
verify. Thanks.

If you've already signed a CLA, it's possible we don't have your
GitHub username or you're using a different email address on your commit.
Check your existing CLA data https://cla.developers.google.com/clas
and verify that your email is set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.
If your company signed a CLA, they designated a Point of Contact who
decides which employees are authorized to participate. You may need to
contact the Point of Contact for your company and ask to be added to the
group of authorized contributors. If you don't know who your Point of
Contact is, direct the project maintainer to go/cla#troubleshoot. The email
used to register you as an authorized contributor must be the email used
for the Git commit.
In order to pass this check, please resolve this problem and have
the pull request author add another comment and the bot will run again. If
the bot doesn't comment, it means it doesn't think anything has changed.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/angular/angular-cli/pull/9666#issuecomment-366449390,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHG-ciQtgTXnb5RKusqD4EKohIYh4zuuks5tVvNegaJpZM4SJWcH
.

I cannot comment on why the Travis CI build failed. I only made a change on the README. Please advise.

@hansl was able to do that for you 👍

Makes sense. Will follow moving forward. Forgive the oversight.


ocamlPackages.cairo2: 0.6 -> 0.6.1; ocamlPackages.lablgtk3: 3.0.beta5 -> 3.0.beta6

Motivation for this change
Fixes and improvements:
https://github.com/Chris00/ocaml-cairo/releases/tag/0.6.1
https://github.com/garrigue/lablgtk/releases/tag/3.0.beta6
Things done

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

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

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

@GrahamcOfBorg build acgtk ocamlPackages.lablgtk3-sourceview3 ocamlPackages.lablgtk3-gtkspell3


ClairS quits with exit code 0 but no output, no error logged

I'm using ClairS on three samples right now. Two have been running since last night, no issue yet. The third quits within seconds of launching the job with exit code 0 but no output is written. The directory structure is created in the output file. No errors are written in the log. This job is using a custom reference but I get the same behavior with these files if I substitute hg38 as the reference. Is there a debug flag or something I can use to tell me what is going wrong? This is the code I'm running. Any help would be greatly appreciated.
./run_clairs
-T /home/nparma/eee_bams_dsa/DSA_hifiasm_60x/ONT/COLO829-T_PS00361.all.sorted.bam
-N /home/nparma/eee_bams_dsa/DSA_hifiasm_60x/ONT/COLO829-BL_PS00342.all.sorted.bam
-R /home/nparma/eee_bams_dsa/references/dsa60/COLO829-BL_60X_hifisam_merged_haplotypes.fasta
-t 4
-p ont_r10_dorado_sup_5khz
-o /home/nparma/eee_bams_dsa/myanalysis/clairs/T/dsa/clairsout

@nparmalee
Could you share  logs directory and  run_clairs.log log file in your output dir /home/nparma/eee_bams_dsa/myanalysis/clairs/T/dsa/clairsout for us to pinpoint the issue?
My email address is<EMAIL_ADDRESS>thanks.

Thanks so much for your quick reply.
Here are the contents of the run_clairs.log file:
[COMMAND] /gpfs/home/nparma/programs/ClairS/run_clairs --tumor_bam_fn /home/nparma/eee_bams_dsa/DSA_hifiasm_60x/ONT/COLO829-T_PS00361.all.sorted.bam --normal_bam_fn /home/nparma/eee_bams_dsa/DSA_hifiasm_60x/ONT/COLO829-BL_PS00342.all.sorted.bam --ref_fn /home/nparma/eee_bams_dsa/references/dsa60/COLO829-BL_60X_hifisam_merged_haplotypes.fasta --threads 4 --platform ont_r10_dorado_sup_5khz --output_dir /home/nparma/eee_bams_dsa/myanalysis/clairs/T/dsa/clairsout
[INFO] --include_all_ctgs not enabled, use chr{1..22,X,Y} and {1..22,X,Y} by default

On Apr 26, 2024, at 10:47 PM, zhenxian @.***> wrote:
@nparmalee
Could you share logs directory and run_clairs.log log file in your output dir /home/nparma/eee_bams_dsa/myanalysis/clairs/T/dsa/clairsout for us to pinpoint the issue?
My email address is @.***, thanks.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.

Thanks for pointing me to that log file, I had missed it. I updated the code and so far this is running. This bam file is aligned to a donor specific assembly and I’m not sure how the contains are named so this error makes some sense.
./run_clairs
-T /home/nparma/eee_bams_dsa/DSA_hifiasm_60x/ONT/COLO829-T_PS00361.all.sorted.bam
-N /home/nparma/eee_bams_dsa/DSA_hifiasm_60x/ONT/COLO829-BL_PS00342.all.sorted.bam
-R /home/nparma/eee_bams_dsa/references/dsa60/COLO829-BL_60X_hifisam_merged_haplotypes.fasta
-t 4
-p ont_r10_dorado_sup_5khz
-o /home/nparma/eee_bams_dsa/myanalysis/clairs/T/dsa/clairsout
--include_all_ctgs

On Apr 27, 2024, at 10:18 AM, Nancy Parmalee @.***> wrote:
Thanks so much for your quick reply.
Here are the contents of the run_clairs.log file:
[COMMAND] /gpfs/home/nparma/programs/ClairS/run_clairs --tumor_bam_fn /home/nparma/eee_bams_dsa/DSA_hifiasm_60x/ONT/COLO829-T_PS00361.all.sorted.bam --normal_bam_fn /home/nparma/eee_bams_dsa/DSA_hifiasm_60x/ONT/COLO829-BL_PS00342.all.sorted.bam --ref_fn /home/nparma/eee_bams_dsa/references/dsa60/COLO829-BL_60X_hifisam_merged_haplotypes.fasta --threads 4 --platform ont_r10_dorado_sup_5khz --output_dir /home/nparma/eee_bams_dsa/myanalysis/clairs/T/dsa/clairsout
[INFO] --include_all_ctgs not enabled, use chr{1..22,X,Y} and {1..22,X,Y} by default

On Apr 26, 2024, at 10:47 PM, zhenxian @.***> wrote:
@nparmalee
Could you share logs directory and run_clairs.log log file in your output dir /home/nparma/eee_bams_dsa/myanalysis/clairs/T/dsa/clairsout for us to pinpoint the issue?
My email address is @.***, thanks.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.

Hello, and thank you for your help earlier. Unfortunately the run finished without producing a vcf file. This is the code I ran. I am attaching the log file. I would really appreciate your help with this.
Thanks,
Nancy
./run_clairs
-T /home/nparma/eee_bams_dsa/DSA_hifiasm_60x/ONT/COLO829-T_PS00361.all.sorted.bam
-N /home/nparma/eee_bams_dsa/DSA_hifiasm_60x/ONT/COLO829-BL_PS00342.all.sorted.bam
-R /home/nparma/eee_bams_dsa/references/dsa60/COLO829-BL_60X_hifisam_merged_haplotypes.fasta
-t 4
-p ont_r10_dorado_sup_5khz
-o /home/nparma/eee_bams_dsa/myanalysis/clairs/T/dsa/clairsout
--include_all_ctgs

On Apr 27, 2024, at 10:29 AM, Nancy Parmalee @.***> wrote:
Thanks for pointing me to that log file, I had missed it. I updated the code and so far this is running. This bam file is aligned to a donor specific assembly and I’m not sure how the contains are named so this error makes some sense.
./run_clairs
-T /home/nparma/eee_bams_dsa/DSA_hifiasm_60x/ONT/COLO829-T_PS00361.all.sorted.bam
-N /home/nparma/eee_bams_dsa/DSA_hifiasm_60x/ONT/COLO829-BL_PS00342.all.sorted.bam
-R /home/nparma/eee_bams_dsa/references/dsa60/COLO829-BL_60X_hifisam_merged_haplotypes.fasta
-t 4
-p ont_r10_dorado_sup_5khz
-o /home/nparma/eee_bams_dsa/myanalysis/clairs/T/dsa/clairsout
--include_all_ctgs

On Apr 27, 2024, at 10:18 AM, Nancy Parmalee @.*** @.***>> wrote:
Thanks so much for your quick reply.
Here are the contents of the run_clairs.log file:
[COMMAND] /gpfs/home/nparma/programs/ClairS/run_clairs --tumor_bam_fn /home/nparma/eee_bams_dsa/DSA_hifiasm_60x/ONT/COLO829-T_PS00361.all.sorted.bam --normal_bam_fn /home/nparma/eee_bams_dsa/DSA_hifiasm_60x/ONT/COLO829-BL_PS00342.all.sorted.bam --ref_fn /home/nparma/eee_bams_dsa/references/dsa60/COLO829-BL_60X_hifisam_merged_haplotypes.fasta --threads 4 --platform ont_r10_dorado_sup_5khz --output_dir /home/nparma/eee_bams_dsa/myanalysis/clairs/T/dsa/clairsout
[INFO] --include_all_ctgs not enabled, use chr{1..22,X,Y} and {1..22,X,Y} by default

On Apr 26, 2024, at 10:47 PM, zhenxian @.*** @.***>> wrote:
@nparmalee
Could you share logs directory and run_clairs.log log file in your output dir /home/nparma/eee_bams_dsa/myanalysis/clairs/T/dsa/clairsout for us to pinpoint the issue?
My email address is @.***, thanks.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.

Hello, nparmalee
I encountered a similar issue and wanted to share a potential solution. Please ensure that a .bai file exists in the same path as your bam file. ClairS relies on the 'samtools mpileup' command for candidate selection, which requires a .bai file. Without it, ClairS will not produce results or log errors, as it does not check stderr.
I hope this helps!


Statement is always true

https://github.com/photonstorm/phaser/blob/cd1854630eb8fec5c43e59a64f005a701c5c16f7/src/renderer/webgl/WebGLRenderer.js#L26
This statement is always true. typeof always return a non-empty string.
I guess it should be something like:
if (typeof WEBGL_DEBUG !== 'undefined' && (WEBGL_DEBUG === true || WEBGL_DEBUG === 'true'))

This is on purpose, although I don't think I can explain it perfectly.

This isn't actual code, it's never run, so these changes are not required. It's part of the DefinePlugin for Webpack, which is just a pure text replacement plugin. The actual code that ends-up in the built files doesn't include the typeof at all. See here: https://webpack.js.org/plugins/define-plugin/

The actual code that ends-up in the built files

Maybe not if you build it with webpack. But it is shipped to npm. And there, you can't disable loading phaser3spectorjs.

 "dependencies": {
   "canvas": "^2.10.2",
   "jsdom": "^20.0.3",
+  "phaser3spectorjs"<EMAIL_ADDRESS> },

Solved it by aliasing phaser3spectorjs with empty-npm-package. This way it will just load the empty module.

I can't see how using it from npm will make any difference as it uses the dist build when you import from npm, not the source, so the conditional code-swap has already taken place.
If you're directly importing specific source files into your game, that's a different issue entirely.  Building from source should be done with webpack and DefinePlugin or an equivalent that does the exact same thing, otherwise it will break all of the conditional features (canvas/webgl, audio, debug, etc) used through-out the codebase.

Ok, fair enough, if you're crazy enough to be running Phaser on the server, then yes, it will pull it from the source. Just understand that none of the conditional checks will work at all (and there are loads of them). They're build flags, should be treated as such and handled as such.

I know. I have worked with the definePlugin before.
Well, I do not personally run Phaser on the server, but I maintain phaser-on-nodejs :)
But I personally recommend using the following approach, which works with and without webpack, instead of that weird approach with the typeof as prefix in https://github.com/photonstorm/phaser/blob/master/config/webpack.config.js#L39.
// webpack.config.cjs

const path = require('path')
const webpack = require('webpack')

module.exports = {
  entry: './index.js',
  output: {
    filename: 'bundle.js',
    path: path.resolve(__dirname)
  },
  plugins: [
    new webpack.DefinePlugin({
      WEBGL_DEBUG: JSON.stringify(true)
    })
  ]
}

// works with and without webpack
if (typeof WEBGL_DEBUG !== 'undefined') {
  console.log('is debug')
} else {
  console.log('normal')
}

// or even better
if (typeof WEBGL_DEBUG !== 'undefined' && WEBGL_DEBUG === true) {
  console.log('is debug')
} else {
  console.log('normal')
}

If you bundle the above with webpack, it will produce:
console.log("is debug"),console.log("is debug");

If you run node index.js, it will output:
normal
normal

😅👍🏻

So I tested this today, by changing the webpack config as such:
            new webpack.DefinePlugin({
                CANVAS_RENDERER: JSON.stringify(true),
                WEBGL_RENDERER: JSON.stringify(true),
                WEBGL_DEBUG: JSON.stringify(true),
                EXPERIMENTAL: JSON.stringify(true),
                PLUGIN_3D: JSON.stringify(false),
                PLUGIN_CAMERA3D: JSON.stringify(false),
                PLUGIN_FBINSTANT: JSON.stringify(false),
                FEATURE_SOUND: JSON.stringify(true)
            }),

and the checks to:
if (typeof WEBGL_RENDERER !== 'undefined')
{
    renderWebGL = require('./ContainerWebGLRenderer');
}

and it does not work. The DefinePlugin fails to replace the code correctly and it always gets included.
So while it may fix it for node, it breaks it for the actual build. I tried changing it to: if (typeof WEBGL_RENDERER !== 'undefined' && WEBGL_RENDERER === true) and it still didn't work, DefinePlugin still included it, no matter what the flag was set to in the webpack config.

So, sadly, I'm reverting this change.

It is easier for me to reply in a video:
https://github.com/phaserjs/phaser/assets/20306025/36a9d505-679e-4294-9db8-7247e95da905

On the plus side, I found a way to stop ESLint moaning about the undefs, so I'm not worried about that any longer!


METRON-2109: Add option to use Metron GUID as the id in Elasticsearch

Contributor Comments
This PR adds the option described in the title.  A user can now configure a sensor (or all sensors) to use the Metron generated GUID instead of letting Elasticsearch generate one.
Changes Included

Added a configuration option to the various indexing and writer configuration classes
Added logic in the ElasticsearchWriter class to conditionally include the Metron GUID as the document id
Added unit tests to cover this new use case
Added documentation to the metron-indexing README explaining the setting

Testing
This has been tested in full dev.

Spin up full dev and verify data is showing up in Elasticsearch and the Alerts UI
Perform a basic search against the bro index:

curl -X POST --header 'Content-Type: application/json' --header 'Accept: application/json' -d '{
  "from": 0,
  "indices": [
    "bro"
  ],
  "query": "*",
  "size": 5
}' 'http://user:password@node1:8082/api/v1/search/search'

The id fields should have an id that was generated by ES:
{
  "total": 93780,
  "results": [
    {
      "id": "AWqbP-_e08M1mJHcFnht",
      "source": {
    ...

Configure the bro sensor to use the Metron generated GUID instead:

curl -X POST --header 'Content-Type: application/json' --header 'Accept: application/json' -d '{
  "hdfs": {
    "index": "bro",
    "batchSize": 1,
    "enabled": true
  },
  "elasticsearch": {
    "index": "bro",
    "batchSize": 1,
    "enabled": true,
    "metronId": true
  },
  "solr": {
    "index": "bro",
    "batchSize": 1,
    "enabled": true
  }
}' 'http://user:password@node1:8082/api/v1/sensor/indexing/config/bro'

Perform another search against bro and verify the id field is now the same as the Metron guid field:

{
  "total": 95475,
  "results": [
    {
      "id": "023ed7d1-3d1a-4530-bd1c-8a177e9a8323",
      "source": {
      ...

Perform a search against snort and verify the id field is still being generated by ES.
Set all sensors to use the Metron generated GUID in the global config:

curl -X POST --header 'Content-Type: application/json' --header 'Accept: application/json' -d '{
    ...
    "indexing.writer.metronId": true
}' 'http://user:password@node1:8082/api/v1/global/config'

Verify searches against bro, snort, and yaf all return results with the id field set to the Metron guid field.
Navigate to the Alerts UI.  Verify messages (with and without the Metron generated GUID) can be updated by clicking on an alert and setting it's status to OPEN or any other status.

I also tested the REST endpoints directly and found no issues.
Pull Request Checklist
Thank you for submitting a contribution to Apache Metron.
Please refer to our Development Guidelines for the complete guide to follow for contributions.
Please refer also to our Build Verification Guidelines for complete smoke testing guides.
In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following:
For all changes:

[x] Is there a JIRA ticket associated with this PR? If not one needs to be created at Metron Jira.
[x] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

For code changes:

[x] Have you included steps to reproduce the behavior or problem that is being changed or addressed?

[x] Have you included steps or a guide to how the change may be verified and tested manually?

[x] Have you ensured that the full suite of tests and checks have been executed in the root metron folder via:
mvn -q clean integration-test install && dev-utilities/build-utils/verify_licenses.sh

[x] Have you written or updated unit tests and or integration tests to verify your changes?

[x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

[x] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?

For documentation related changes:

[x] Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via site-book/target/site/index.html:
cd site-book
mvn site

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
It is also recommended that travis-ci is set up for your personal repository such that your branches are built there before submitting a pull request.

The latest commit should address all of your feedback so far.  For read-side testing I was able to add this to the ElasticsearchSearchIntegrationTest with only a couple of changes ElasticSearchComponent class.  The test now includes bro messages with and without the Metron GUID.  Does that provide the coverage you're looking for?

+1 Looks great @merrimanr .  Nice work.


Run all cells in a notebook is slow

This is a regression, we fixed this to ensure its as fast as Jupyter notebook.
Now its very very slow.
takes around 5 seconds to run 10 cells that just prints a number.
Same perf issues in IW as well, but we can look into that separately.

Original issue was here https://github.com/microsoft/vscode-jupyter/issues/5662

Unable to repro anymore, seems to be fast again.


can't use mnist data after download using tensoerflow.It's give below error

I'll use os as fedora
Install python via Conda-navigator
Editor use pycharm
Os Platform:fedora
Tensorflow installed from anaconda
Tensorflow version:1.8.0
python version : 3.6.5
Bazel version:Not installed
WARNING:tensorflow:From /home/sunil/PycharmProjects/test/testFile.py:7: read_data_sets (from tensorflow.contrib.learn.python.learn.datasets.mnist) is deprecated and will be removed in a future version.
Instructions for updating:
Please use alternatives such as official/mnist/dataset.py from tensorflow/models.
Extracting MNIST_data/train-images-idx3-ubyte.gz
WARNING:tensorflow:From /home/sunil/anaconda3/envs/condaEnvTest/lib/python3.6/site-packages/tensorflow/contrib/learn/python/learn/datasets/mnist.py:260: maybe_download (from tensorflow.contrib.learn.python.learn.datasets.base) is deprecated and will be removed in a future version.
Instructions for updating:
Please write your own downloading logic.
WARNING:tensorflow:From /home/sunil/anaconda3/envs/condaEnvTest/lib/python3.6/site-packages/tensorflow/contrib/learn/python/learn/datasets/mnist.py:262: extract_images (from tensorflow.contrib.learn.python.learn.datasets.mnist) is deprecated and will be removed in a future version.
Instructions for updating:
Please use tf.data to implement this functionality.
Extracting MNIST_data/train-labels-idx1-ubyte.gz
WARNING:tensorflow:From /home/sunil/anaconda3/envs/condaEnvTest/lib/python3.6/site-packages/tensorflow/contrib/learn/python/learn/datasets/mnist.py:267: extract_labels (from tensorflow.contrib.learn.python.learn.datasets.mnist) is deprecated and will be removed in a future version.
Instructions for updating:
Please use tf.data to implement this functionality.
WARNING:tensorflow:From /home/sunil/anaconda3/envs/condaEnvTest/lib/python3.6/site-packages/tensorflow/contrib/learn/python/learn/datasets/mnist.py:110: dense_to_one_hot (from tensorflow.contrib.learn.python.learn.datasets.mnist) is deprecated and will be removed in a future version.
Instructions for updating:
Please use tf.one_hot on tensors.
Extracting MNIST_data/t10k-images-idx3-ubyte.gz
Extracting MNIST_data/t10k-labels-idx1-ubyte.gz
WARNING:tensorflow:From /home/sunil/anaconda3/envs/condaEnvTest/lib/python3.6/site-packages/tensorflow/contrib/learn/python/learn/datasets/mnist.py:290: DataSet.init (from tensorflow.contrib.learn.python.learn.datasets.mnist) is deprecated and will be removed in a future version.
Instructions for updating:
Please use alternatives such as official/mnist/dataset.py from tensorflow/models.

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
TensorFlow installed from
TensorFlow version
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce

I'll use os as fedora
Install python via Conda-navigator
Editor use pycharm
Os Platform:fedora
Tensorflow installed from anaconda
Tensorflow version:1.8.0
python version : 3.6.5
Bazel version:Not installed
WARNING:tensorflow:From /home/sunil/PycharmProjects/test/testFile.py:7: read_data_sets (from tensorflow.contrib.learn.python.learn.datasets.mnist) is deprecated and will be removed in a future version.
Instructions for updating:
Please use alternatives such as official/mnist/dataset.py from tensorflow/models.
Extracting MNIST_data/train-images-idx3-ubyte.gz
WARNING:tensorflow:From /home/sunil/anaconda3/envs/condaEnvTest/lib/python3.6/site-packages/tensorflow/contrib/learn/python/learn/datasets/mnist.py:260: maybe_download (from tensorflow.contrib.learn.python.learn.datasets.base) is deprecated and will be removed in a future version.
Instructions for updating:
Please write your own downloading logic.
WARNING:tensorflow:From /home/sunil/anaconda3/envs/condaEnvTest/lib/python3.6/site-packages/tensorflow/contrib/learn/python/learn/datasets/mnist.py:262: extract_images (from tensorflow.contrib.learn.python.learn.datasets.mnist) is deprecated and will be removed in a future version.
Instructions for updating:
Please use tf.data to implement this functionality.
Extracting MNIST_data/train-labels-idx1-ubyte.gz
WARNING:tensorflow:From /home/sunil/anaconda3/envs/condaEnvTest/lib/python3.6/site-packages/tensorflow/contrib/learn/python/learn/datasets/mnist.py:267: extract_labels (from tensorflow.contrib.learn.python.learn.datasets.mnist) is deprecated and will be removed in a future version.
Instructions for updating:
Please use tf.data to implement this functionality.
WARNING:tensorflow:From /home/sunil/anaconda3/envs/condaEnvTest/lib/python3.6/site-packages/tensorflow/contrib/learn/python/learn/datasets/mnist.py:110: dense_to_one_hot (from tensorflow.contrib.learn.python.learn.datasets.mnist) is deprecated and will be removed in a future version.
Instructions for updating:
Please use tf.one_hot on tensors.
Extracting MNIST_data/t10k-images-idx3-ubyte.gz
Extracting MNIST_data/t10k-labels-idx1-ubyte.gz
WARNING:tensorflow:From /home/sunil/anaconda3/envs/condaEnvTest/lib/python3.6/site-packages/tensorflow/contrib/learn/python/learn/datasets/mnist.py:290: DataSet.init (from tensorflow.contrib.learn.python.learn.datasets.mnist) is deprecated and will be removed in a future version.
Instructions for updating:
Please use alternatives such as official/mnist/dataset.py from tensorflow/models.
I'll Updated Please check

I just occurred a same question like yours, and my version of tensorflow is 1.8 as well.Have you found the resolution?

Help me above problem

No, can't found solution
On Fri, Jul 20, 2018, 20:47 JeffersonZeng<EMAIL_ADDRESS>wrote:

I just occurred a same question like yours, and my version of tensorflow
is 1.8 as well.Have you found the resolution?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/20961#issuecomment-406631504,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AZAqAdos-V3PrJSQEoKYyz3LGYONKTBlks5uIfSegaJpZM4VV-H2
.

Nagging Assignee @jart: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @jart: It has been 29 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @jart: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @jart: It has been 29 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @jart: It has been 44 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @jart: It has been 59 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @jart: It has been 74 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @jart: It has been 89 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @jart: It has been 104 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Suppress warnings as below
`
import numpy as np
import tensorflow as tf
old_v = tf.logging.get_verbosity()
tf.logging.set_verbosity(tf.logging.ERROR)
from tensorflow.examples.tutorials.mnist import input_data
mnist = input_data.read_data_sets("MNIST_data/", one_hot=True)
train_data = mnist.train.images  # Returns np.array
train_labels = np.asarray(mnist.train.labels, dtype=np.int32)
eval_data = mnist.test.images  # Returns np.array
eval_labels = np.asarray(mnist.test.labels, dtype=np.int32)
tf.logging.set_verbosity(old_v)
`


[Diagnosis registration]

[Actual Results]: The system allows the user select the current date as the day of the next visit
[Expected results]: The system must not allow the user to select a current date or a previouse date as a day of a cosultation
[Steps to reproduce]: Clinic Module -> Patient Dashboard ->Cosultation -> diagnostico-Pediatria/ Diagnostico-adulto -> Proxima visita -> Select the current date or a date before current date

@Benilde can you try this on dev server?

@valvijo I tried in dev server too and is doing the same thing.


Set Induvial projects as example rather than hardcode

Basically create toggle in the editProjectForm.js that when switched on allows any user to access the project without any admin's explicit permission
To Test

Create a new user
See that projects are not given to new user
return to admin
edit a project to have example permissions
Return to new user and see they now can access the project
return to admin
edit same project to remove example permissions
return to new user
see that they cannot access the project anymore

Resolved conflicts

Ready to test and merge


render_reactions.py and render_species.py require pygraphviz which isn't a declared dependency

pygraphviz can be a pain to install, especially on Windows and Mac, so I don't want to make it a full dependency. These scripts could import pygraphviz at runtime, and print an error if it's not available.
(Found this when nose started searching these files for tests when it hadn't before, and they failed to import in a fresh virtualenv without pygraphviz)

I put pygraphviz in tests_require so we won't have test failures from this, but the bigger issue still stands.


[LOC] Invalid link in an article

There is an invalid link in an article:
Repro steps:

Go to https://docs.microsoft.com/en-us/OneDrive/plan-onedrive-enterprise
Search for the "Install and configure a software update point" Link
Click on the link

Actual results:
Link does not work
Expected result:
Link should work
GH article:
https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/blob/live/OneDrive/plan-onedrive-enterprise.md

@OfficeGlobal Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.

@OfficeGlobal Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.


Generate sprite file rather than embed in the HTML

The spritesheet implementation wraps the generated SVG with a <div> which hides the sprite. This makes a lot of sense.
https://github.com/patrickxchong/eleventy-plugin-svg-sprite/blob/5f2ca08a08d588f86ad8e03a84c8f579e1e65f66/src/SVGSprite.js#L67-L68
However, would it be possible to make this optional?
Ideally I'd like to generate the spritesheet into a svg file (via 11ty permalinks), and then cache it for a longtime at the clientside. This means I could then reference the speicific icon, eg:
<svg class="">
   <use xlink:href="https://cdn.com/spriteSheet.svg#logo"></use>
</svg>

Hey James, I wanted to clarify, would the problem be solved if the sprite is written to an external filepath (outputPath) that is provided via the config? eg, (assuming array config, would work for non array config as well)
module.exports = function (eleventyConfig) {

  eleventyConfig.addPlugin(svgSprite, [
    {
      path: "./src/assets/svg_1", // relative path to SVG directory
      svgSpriteShortcode: "svgsprite1",
      outputPath: "./sprites/svgsprite1" // filepath for the first spritesheet
    },
    {
      path: "./src/assets/svg_2", // relative path to SVG directory
      svgSpriteShortcode: "svgsprite2",
      outputPath: "./sprites/svgsprite2" // filepath for the second spritesheet
    }
  ]);
};

That would be an even better solution that the one I suggested!

What you suggested is really cool actually, and I definitely agree that would be preferable, but alas, Eleventy 1 doesn't support that yet because the plugin has no access to the dir object. It'll only be available in Eleventy 2 which is still in progress (https://www.11ty.dev/docs/events/#event-arguments). The best solution for now would be to go with outputFilepath. I've already implemented the changes and published version 2.1.0 with updated documentation. Give it a try and let me know if it solves your problem!

Well, that is perfect. Thank you Patrick.
Implemented here: https://github.com/theglobechurch/globe-static/commit/e859dcbfce6722b647c6bcad122e62146a2cec04

Great! Glad it worked for you, and definitely a good idea to create shortcode for it. I didn't add that in because the spritesheet could be used in different ways. Cheers!


Fixes a grammar error

CIs, test this please.

Jenkins CI test (for commit 80a21eae26dc91763c6abdd754dfefb82292a5bb, target branch master) failed with status FAILURE.

@toslunar This pull-request is marked as st:test-and-merge, but there were no activities for the last 3 days. Could you check?


Develop/rafo test0606

Codecov Report

Merging #8 (d338b90) into main (8258875) will decrease coverage by 4.21%.
The diff coverage is 18.75%.

@@            Coverage Diff             @@
##             main       #8      +/-   ##
==========================================
- Coverage   20.00%   15.78%   -4.22%
==========================================
  Files           3        8       +5
  Lines          10       38      +28
  Branches        0        5       +5
==========================================
+ Hits            2        6       +4
- Misses          8       31      +23
- Partials        0        1       +1

Impacted Files
Coverage Δ

src/context/ThemeContext/context.ts
0.00% <0.00%> (ø)

src/context/ThemeContext/index.ts
0.00% <0.00%> (ø)

src/context/ThemeContext/provider.tsx
0.00% <0.00%> (ø)

src/hooks/useTheme/index.ts
0.00% <0.00%> (ø)

src/pages/index.tsx
0.00% <0.00%> (ø)

src/components/TestComponent/index.tsx
100.00% <100.00%> (ø)

src/components/TestComponent/styles.ts
100.00% <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 870e604...d338b90. Read the comment docs.


STS: Create OCM Role

Related: SDA-4988
This MR has a lot in common with https://github.com/openshift/rosa/pull/525
If merged after https://github.com/openshift/rosa/pull/525, I will fix the conflicts

@pvasant @vkareh @ciaranRoche PTAL
Not tested yet. I have some local issues

@vkareh @pvasant @ciaranRoche I addressed the issues you raised and tested the code.
Please take another look

This is great! Thanks for getting this done so fast! LGTM
I'll let @pvasant give it the last stamp and merge

Verified and it works :+1:

Rebased.
@vkareh @pvasant PTAL

/lgtm


pd.DataFrame not in completion results

Environment data

Language Server version: 2020.6.1
OS and version: Windows 10
Python version (& distribution if applicable, e.g. Anaconda): Python 3.8.0 32-bit virtualenv

Expected behaviour
pd.DataFrame is in completion results
Actual behaviour

Same behavior with pd.Series, pd.Timestamp etc. They are not exactly functions I guess, maybe that's the cause of the problem?

I think the stubs are alright here, but the only class that's showing as a completion off pd. is the public one defined in __init__.py itself, not the ones that are imported from other modules by __init__.py. Those classes work fine once you have them; i.e. you get completions for pd.DataFrame(). etc. So there's something odd going on.

Is this perhaps related to this bug? https://github.com/microsoft/pyright/issues/782

Looks like it but I will wait to confirm before marking this as fixed.

I am getting this error as well. For example, Pylance thinks this is invalid because it cannot see the types of DataFrame:
df = pd.DataFrame.from_dict(my_dict)
I get IntelliSense when I use Jedi alone without Pylance.
Pylance Version: 2020.6.1
Python Language Server Version: 2020.6.91350
Python: 3.7.6
OS: Windows 10

This issue has been fixed in version 2020.7.0, which we've just released. You can find the changelog here: https://github.com/microsoft/pylance-release/blob/master/CHANGELOG.md#202070-9-july-2020

That was a fast update!
I just tried out the new 2020.7.0 release. It looks like the errors have stopped, but I am still not getting IntelliSense like I get with Pyright for pandas dataframes. Should I open a new issue for this?

Yes, please do. Pyright doesn't ship any pandas stubs, but we do, so there may be a difference there where it's reading the "real" code.


:space_invader: Variable clinics for selecting appointments.

I've reused partials clinic-filters.html and clinic-map.html off of select-your-clinic.hml and I've switched the side of the page they are displayed on so both pages are consistent. This has had the effect of breaking the filtering (again :dizzy_face: :gun: :open_hands:).
I'll get them sorted. And I'll get the appointments loading from the data.

st3v3nhunt: This has had the effect of breaking the filtering

Yeah, this will be a pretty simple fix. I'll take a look today if i get a chance.


elementum 0.1.55 causes kodi crashes

Since I see that still the project updating and in latest 2 versions started the problem I mentioned here in case there is a posibility of a fix.
I mentioned frequent crashes of kodi after 0.1.54 update, but I didn't knew if elementum or something else was responcible yet. I tried to update to 0.1.55 version some days ago, which always fail. So, I downloaded the zip from here and I updated manually elementum and burst 0.0.49.
After the update the crashes happen more frequently and kodi cannot stay open more that 20 minutes, no matter if I use elementum, other plugins, or playing videos from library. I tried today to disable it and after that there was no problem for some hours and until I closed kodi. After that I re-enable elementum and tried a torrent. Again kodi crashed after about 20 mins.
So, seems that elementum is responsible.
The crashes aren't after 20 mins every time. Sometimes are 2-3 minutes after kodi start, 5mins or 10mins, but kodi cannot stay open more than 20mins.
Here are the crash logs:
http://www.mediafire.com/file/7an7aea5lf3sau3/kodicrashlogs.zip

After I tested some previous versions(from 0.1.52) and in all I had problems with elementum, I deleted the addon settings folder and upgrade again to 0.1.55. I didn't do it before because I didn' t do any change to elementum settings for months. After that elementum works fine again, so it seems that something there caused the problems.


Integrate Pulse into Nova?

Hello,
Thanks for your work on Pulse! I want to ask whether there are long-term plans to integrate Pulse into Nova, where Pulse can be one of the dashboards of a Nova admin. Or maybe the Pulse cards can be used as cards in the Nova admin.

We don't have any plans for this at the moment, @jadjoubran


[SIP-135]  Proposal for aggregate dimensions

Please make sure you are familiar with the SIP process documented
here. The SIP will be numbered by a committer upon acceptance.
[SIP-135] Proposal for aggregate dimensions
Motivation
Adding columns to a report that are functionality dependent on an already added dimension should come at a low cost.
For example:
'GROUP BY person_id'
If we then want to add columns to the report "first_name,last_name,age" we'd have the choice of adding it to the dimension or as a metric.
Simply adding it to the dimension incurs penalty of putting in the GROUP BY. This is an expensive operation as well as a potential error (what if one of the rows actually had the wrong age and we ended up creating a new person)
Simply adding it as a metric is a bit awkward but is the best fit for my use case now. I have dozens of these columns and perfer to just wrap them in an ANY aggregate function.
Proposed Change
I propose we add a toggle to set a dimension as an "aggregate dimension" Instead of adding this column to the group by the user can just pick the aggregate it would like (min,max,any, first, etc). By default we would not have to duplicate this as a new metric column but could keep the same name. I think this would also work with the newer Drill features in a better way than the metrics.
Rejected Alternatives
Currently adding these strings as a metric in an ANY aggregate works best for me. This awkward and confusing to the end user to see dimensional type data as well as a lot of duplicated column naming "any(first_name) as first_name"

I'm not quite understanding the proposal, to be honest. Can you provide some examples (both good and bad) of the use cases and the queries they'd generate?

If you had a denormalized table with a persons information called PersonSightings
with a row like:
person_id:1,f_name:evan,l_name:r, address:"343232 W. Palm St Jacksonville,Flordia",:sighting_timestamp:2024-01-01
imagine there was a new row for everytime a camera spotted the person
You would want to take advantage of the fact that most of the columsn are functionality depenendt on person_id
Currently to get a report on distinct sightings you'd need to add most of the columns as a dimension which generates:
SELECT person_id,f_name,l_name, address,sighting_timestamp,count(distinct sighting_timestamp)
from PersonSightings
GROUP BY person_id,f_name,l_name, address,sighting_timestamp
The main problem is the GROUP BY is very inefficient. I'd want SQL Like
SELECT person_id,any(f_name),any(l_name), any(address),any(sighting_timestamp),count(distinct sighting_timestamp)
from PersonSightings
GROUP BY person_id
To do this I need to turn those dimensions into metrics and add custom sql. But they should be treated as dimensions not metrics.
So I proposed a way to put an aggregate around a dimension so superset can apply ANY or FIRST (whatever the database supports)
In my use case I actually have a few dozen of these and using clickhouse which can be exponentially faster with smaller GROUP BYs

@yousoph @geido - please check this out and let us know your thoughts :)

Can you propose a bit more about how you would implement these aggregate functions (e.g. ANY or FIRST), maybe some example queries, and how this would be surfaced in the Dataset modal, the chart builder, the DrillBy/DrillToDetail modals, etc?

@michaelritsema do you have intent to follow through with the questions and work here? If this is just a feature request, we'll move it to a GitHub Discussion or close it.

Closing for lack of follow-up clarity. I'm assuming this is a feature request, essentially. Please open a GitHub Discussion under the "Ideas" category if you want to seek help adding this. Happy to reopen this if you can provide more clarity of approach.


Add QueryAssert#doesNotContain

I think it may turn out I don't need this. Since this API is slightly leaning towards error-proneness, let's not merge this now and revisit when needed.


Revert "Reduce staticcheck warnings (SA4023) (#344)"

This reverts commit f7131b6e5448d2b77ab3aba23ab175e80a97c93b.

This reverts PR #344 as it was already merged before ready!


Ships disappear when pressing Mount

Minecraft version: 1.12.2
Mod version: davincisvessels-1.12-6.340-full
movingworld-1.12-6.342-full
1.12.2-forge1.12.2-<IP_ADDRESS>2
When I press the mount option, the blocks I have placed will just disappear. I'm using blocks that are allowed in the config file, so am at a loss for what is going on.

Sorry, I mean when I choose to mount the vessel, assembly works fine

I have dropped in some screenshots of the process. As you can see, up to the point of mounting the ship, everything seems to be fine, but as soon as I press mount, the ship disappears.

same i just posted the same problem


Xcode 16 building errors

Hello, thanks for this awesome repo, we were using it in our app but lately with Xcode 16 this errors. It occurs with SDK SCNRecorder (2.8.1) Could you guys guide me how to fix these errors?

Hey @ozgurshn  this issue is already fixed on master but there hasn't been a new release. Changing your package dependency to use branch master instead of release versioning should fix this for you.

Hey @tarrouye thank you for the guidance.


https://unit.atlassian.net/browse/NP-45237

mediatype cause trouble fix

Maybe write a unit test for different accept headers, otherwise OK

It is tested in the Handler which is in another subproject  shouldReturnTextCsvWithGivenAcceptHeader


std::logic_error in SQLite deleter

In "near" develop TOT this test on gfx900 (haven't tested other ASICS):
bin/test_conv2d --float --cmode conv --pmode default --group-count 1 --enable-fdb 1 --batch_size 1 --input_channels 32 --output_channels 32 --spatial_dim_elements 28 28 --filter_dims 1 1 --pads_strides_dilations 0 0 1 1 2 2 --trans_output_pads 0 0
Causes:
terminate called after throwing an instance of 'std::logic_error'
  what():  basic_string::_M_construct null not valid
Aborted (core dumped)
dlowell@tengu:[reshuffleAndReduceTestCases]~/MIOpen/oclbuild$

Partial frames in GDB:
#2  0x00007ffff680f56c in std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_construct<char const*> (this=0x7fffffffdcf0, __beg=0x0, __end=0xffffffffffffffff <error: Cannot access memory at address 0xffffffffffffffff>)
    at /usr/include/c++/7/bits/basic_string.tcc:212
212               std::__throw_logic_error(__N("basic_string::"
(gdb) list
207           _M_construct(_InIterator __beg, _InIterator __end,
208                        std::forward_iterator_tag)
209           {
210             // NB: Not required, but considered best practice.
211             if (__gnu_cxx::__is_null_pointer(__beg) && __beg != __end)
212               std::__throw_logic_error(__N("basic_string::"
213                                            "_M_construct null not valid"));
214
215             size_type __dnew = static_cast<size_type>(std::distance(__beg, __end));
216
(gdb) up
#3  0x00007ffff6ad9f63 in miopen::SQLite::impl::SQLiteCloser::operator() (this=0x555555e26720, ptr=0x555555d22128)
    at /home/dlowell/MIOpen/src/sqlite_db.cpp:59
59                  std::string filename_(sqlite3_db_filename(ptr, "main"));
(gdb)
#4  0x00007ffff6adb363 in std::unique_ptr<sqlite3, miopen::SQLite::impl::SQLiteCloser>::~unique_ptr (this=0x555555e26720,
    __in_chrg=<optimized out>) at /usr/include/c++/7/bits/unique_ptr.h:263
263               get_deleter()(__ptr);
(gdb) up
#5  0x00007ffff6add812 in miopen::SQLite::impl::~impl (this=0x555555e26720, __in_chrg=<optimized out>)
    at /home/dlowell/MIOpen/src/sqlite_db.cpp:53
53      class SQLite::impl
(gdb)
#6  0x00007ffff6add838 in std::default_delete<miopen::SQLite::impl>::operator() (this=0x555555d22650, __ptr=0x555555e26720)
    at /usr/include/c++/7/bits/unique_ptr.h:78
78              delete __ptr;
(gdb)

The actual branch I used was reshuffleAndReduceTestCases
Full backtrace attached below.
bt1.txt

This is a ROCm 3.5 environment. So I perhaps there is something with my environment. Let me check another machine.

@dlowell can you share the CMake env ?

I don’t haven’t it anymore. Please ask @asroy @zjing14 @TejashShah

I saw this issue once, but now I cannot see it anymore. But the hardware team saw it again today:
root@b4ad303ff32c:/MIOpen_trial# export MIOPEN_DEBUG_CONV_FFT=0
root@b4ad303ff32c:/MIOpen_trial# export MIOPEN_DEBUG_CONV_DIRECT=0
root@b4ad303ff32c:/MIOpen_trial# export MIOPEN_DEBUG_CONV_GEMM=0
root@b4ad303ff32c:/MIOpen_trial# export MIOPEN_DEBUG_CONV_SCGEMM=0
root@b4ad303ff32c:/MIOpen_trial# export MIOPEN_DEBUG_CONV_IMPLICIT_GEMM=1
root@b4ad303ff32c:/MIOpen_trial# export MIOPEN_FIND_ENFORCE=0
root@b4ad303ff32c:/MIOpen_trial# ./build/bin/MIOpenDriver conv -F 1 -n 256 -g 1 -k 1024 -c 1024 -H  14 -W  14  -y 1 -x 1 -p 0 -q 0 -u 1 -v 1 -l 1 -j 1 -V 0 -w 1 -t 1 -i 1
MIOpenDriver conv -F 1 -n 256 -g 1 -k 1024 -c 1024 -H 14 -W 14 -y 1 -x 1 -p 0 -q 0 -u 1 -v 1 -l 1 -j 1 -V 0 -w 1 -t 1 -i 1
MIOpen(HIP): Error [GetFindEnforceActionImpl] Wrong MIOPEN_FIND_ENFORCE, using default.
MIOpen(HIP): Warning [Prefetch] File is unreadable: /opt/rocm/miopen/share/miopen/db/gfx90878.HIP.fdb.txt
MIOpen(HIP): Warning [SQLiteBase] Unable to read system database file:/opt/rocm/miopen/share/miopen/db/miopen.db Performance may degrade
Wall-clock Time Forward Conv. Elapsed: 6.67449 ms, Auxiliary API calls: 6032 ms (GWSS: 1079.66)
MIOpen Forward Conv. Algorithm: 5, Solution: 64/ConvHipImplicitGemmForwardV4R4Xdlops
GPU Kernel Time Forward Conv. Elapsed: 5.952481 ms (average)
stats: name, n, c, ho, wo, x, y, k, flopCnt, bytesRead, bytesWritten, GFLOPs, GB/s, timeMs
stats: fwd-conv1x1u1, 256, 1024, 14, 14, 1, 1, 1024,<PHONE_NUMBER>52, 209715200, 205520896, 17678, 70, 5.952481
terminate called after throwing an instance of 'std::logic_error'
  what():  basic_string::_M_construct null not valid
Aborted (core dumped)

So he commented out all the code inside the operator() function of Sqlite struct, and was able to workaround the core dump issue

@asroy Thanks for the update, I will triage it further and try to reproduce it. I believe it has something to do with Debug vs Release builds. This is not high-priority since the SQLite object only gets created once and is destroyed when the library is unloaded.


Docs have failed to publish for some crates for several releases

This isn't an exhaustive list, but a few examples where I've noticed failures.
The docs for the generated crate azure_mgmt_network have failed to publish with the message recursive without indirection. Links to docs.rs follow:

https://docs.rs/crate/azure_mgmt_network/0.16.0
https://docs.rs/crate/azure_mgmt_network/0.17.0
https://docs.rs/crate/azure_mgmt_network/0.18.0

There's been some work in the past to counteract this - notably the properties.boxed section of the autorust.toml file.  However, the source of failure here is introduction of new tags. The tags are taken from the README in the spec: https://github.com/Azure/azure-rest-api-specs/blob/main/specification/network/resource-manager/readme.md
The tag which is currently failing is profile_hybrid_2020_09_01 - there's a question here as to whether this tag needs to be generated at all.
However, it's also worth noting that the latest tag now is package-2023-09 - which was released last week. When the Rust SDK crates are regenerated with the latest specs, this will be another faulty tag.
Another example I found whilst running cargo clippy --all-features locally was on the azure_mgmt_hardwaresecuritymodules crate. This time, docs have failed to publish since version 0.12 due to multiple definitions of models within the preview tags.

https://docs.rs/crate/azure_mgmt_hardwaresecuritymodules/0.18.0

It's worth noting that something like this would have been spotted by cargo clippy --all-features or `cargo check  - something the GitHub actions which currently run don't do.

Good idea. We have a Geneva Action that you can run from the Actions tab in any fork for any branch named check-all-services. May be we could add one named clippy-all-services.

https://github.com/Azure/azure-sdk-for-rust/actions/workflows/check-all-services.yml
https://github.com/Azure/azure-sdk-for-rust/blob/main/.github/workflows/check-all-services.yml
https://github.com/Azure/azure-sdk-for-rust/blob/main/services/autorust/codegen/templates/check-all-services.yml.jinja

It would be good to run after updating the services. After new versions are published, you can monitor the failures at https://docs.rs/releases/recent-failures .

Do you mean github-action?

This should fix the issues, but does not ensure the issue is fixed long term.
https://github.com/Azure/azure-sdk-for-rust/pull/1545

It would be good to run after updating the services. May be we could add one named clippy-all-services

Is there any reason we're not just updating the github-actions that run in all PR's to run cargo clippy --all-features instead? That way, any change that goes in meets this quality bar and there's less action on the user to run any actions manually.

This isn't isolated to generated services either...

https://docs.rs/crate/azure_messaging_servicebus/0.19.0
https://docs.rs/crate/azure_messaging_eventgrid/0.19.0
https://docs.rs/crate/azure_iot_hub/0.19.0


Update release issue template to reflect branching strategy changes

Context
We are in the process of deprecating the main branch, keeping only develop. We need to update the release issue template to reflect this changes and guide contributors when preparing a new release
Value and/or benefit
We'll have a consistent release procedure, allowing any interested person to easily understand how to contribute to the release process.
Anything else?
No response

Also, I wonder, do we need the upgrade command to be present for an RC? -- To me, it does not make sense as we need to pin the version in the class anyways, so this looks like a final release thing to me.


feat(http): Add XHR Timeout configuration

@bluepnume Not sure why the button size test is failing...  It did that for me locally as well.  The test doesn't use the http library at all so I am not sure whats up

Think I found the problem. Let me restart the PR job...


Remove potential false positive assertions

querySelector() returns null but expect(document.querySelector('...')).toBeDefined() checks that the value is not undefined. This can lead to false positive tests

Can you check if there are more cases please?

Added more cases I could find in unit tests for assertions against values that assigned from .querySelector(...)

Thanks for the PR. There must be more instances, from a quick look. At least for getInstance.

Do we still want these changes?
I can rebase to resolve conflicts so it can be ready to merge, otherwise I will close this PR

@XhmikosR this might has to be in 5-stable

Thanks @GeoSot please let me know when is the best time to rebase, it would be great if I can avoid doing it multiple times :+1:

in case of stable-5 is a good time to be rebased. But it doesn't depends by me and only. Thanks for your understanding

I have rebased the changes against master

Sorry for the delay @spicalous but we are only a few volunteers.
This PR can wait after 5.0.0, since it doesn't fix any bug. I hope you understand.
The same applies to your other PR you closed, you should reopen it until someone has a look at it.

No problemos, just give me a shout when this needs to be rebased again :+1:

@spicalous  I saw about 17 more deDefined checks. If it is easy, please make a check on them too

When looking through some of the matchers, I think it's not very clear when some return null or undefined
What do you guys think about using toBeTruthy / toBeFalsy ?

toBeTruthy() coerces the values AFAICT so it's a little moot IMHO. Either we are always explicit or not :)

@GeoSot I have updated more cases
Regarding these ones, I think they provide no value and can be removed. What do you guys think?
https://github.com/twbs/bootstrap/blob/f61a0218b36d915db80dc23635a9078e98e2e3e0/js/tests/unit/dom/manipulator.spec.js#L118
https://github.com/twbs/bootstrap/blob/f61a0218b36d915db80dc23635a9078e98e2e3e0/js/tests/unit/dom/manipulator.spec.js#L131
https://github.com/twbs/bootstrap/blob/f61a0218b36d915db80dc23635a9078e98e2e3e0/js/tests/unit/scrollspy.spec.js#L79

toBeTruthy() coerces the values AFAICT so it's a little moot IMHO. Either we are always explicit or not :)

So the original reason for this PR was that I noticed the assertions could result in a failing test to pass e.g. in the case where element is null
expect(element).toBeDefined() === TEST PASS false positive
expect(element).not.toBeNull() === TEST FAIL correct
expect(element).toBeFalsy() === TEST FAIL correct
wouldn't toBeFalsy suffice here?
https://github.com/jasmine/jasmine/blob/2fc5182ddcdd67456b89c92c2eedbc2443c928c6/src/core/matchers/toBeDefined.js
Similar case for truthy checks
Given that a property is null, we assert .not.toBeNulll (null !== actual)
What happens if behaviour is changed
e.g.
instead of property = null, someone may delete property
In this case, the assertion would pass as undefined !== null and we end up with false positives again
In this case, I think truthy assert would be better again, we just don't want null AND undefined
Ah... Javascript..... :)


Add a JetBrains / IntelliJ plugin

We recently released the Infracost VSCode Extension that got a lot of love from the community. Some users have asked for an IntelliJ plugin.
Community note

👍 if you'd like to upvote or subscribe to this issue for updates
Comment here if you're interested on working on this, the VSCode extension might act as a useful model to learn from

Definitely down to work on this

I think if we want to support other editors I think it's best that we build out our own Infracost Language Server first. The VSCode extension is kinda hacky at the moment in that it uses the raw binary directly. With a language server, it will be much easier for us and community members like @WoodyWoodster to add support for additional editors (intelij, vim, sublime, e.t.c). Additionally, it will make keeping functionality and updates across updates much simpler.

Definitely agree, language server is certainly the better route.

Agree that a LS is the best way forward, until we have developed one, we now have a JetBrains plugin https://plugins.jetbrains.com/plugin/24761-infracost/

Its an initial version so please raise any issues you face here - https://github.com/infracost/jetbrains-infracost/issues/new


Dbeaver 23.2.3 - data export fails with I/O error and no other  details

Description
it shows up with export screen and green bar moving then ends abruptly with no explanation.
File name was not existing. Tried as CSV, TXT but got same error. Tried couple of different connections/drivers - same issue.
Reverting to previous version of Dbeaver solved the problem.
DBeaver Version
Community Edition 23.2.3
Operating System
Windows 10 enterprise
Database and driver
Presto Trinio,
Databricks Spark SQL
Steps to reproduce
take any query and try to export data, doesnt matter how many records
Additional context
No response

Please provide the log files. You can find instructions here https://dbeaver.com/docs/wiki/Log-files/.

Thank you for bug report. It's a duplicate of #21611
We have already fixed this bug and the fix is available in the early access version https://dbeaver.io/files/ea/


Output warning when deserializing object stream

We have received another security vulnerability report caused by object stream deserialization.
When all of the following conditions are met, the attacker can trigger RCE (remote code execution).

the user enabled the built-in 2nd level cache [1]
the user did not setup JEP-290 filter
the attacker found a way to modify entries of the private Map field i.e. org.apache.ibatis.cache.impl.PerpetualCache.cache and a valid cache key

Once this PR gets merged, MyBatis outputs WARN level log message when deserializing object.

As you are using functionality that deserializes object streams, it is recommended to define the JEP-290 serial filter. Please refer to https://docs.oracle.com/pls/topic/lookup?ctx=javase15&id=GUID-8296D8E8-2B93-4B9A-856E-0A65AF9B8C66

Note that:

the message is not logged when the JEP-290 filter is already defined
the message is logged just once right before the first deserialization

If WARN message is not enough, we can throw an exception instead, but that may surprise users a little bit.
[1] Some of the custom cache implementations also perform deserialization (e.g. mybatis-redis-cache). I plan to look into it later, but the recommended solution is the same i.e. the JEP-290 filter.

if the LookAheadObjectInputStream has been removed , will it affect the functionality of earlier version？like the blacklist.

Thank you for the feedback, @nothingzhl !
This change won't break anything if that is what you mean.
You just need to setup the JEP-290 filter by yourself (using whitelist approach, preferably) to protect your application instead of relying on the built-in blacklist filter.


Update: added connected message

Fixes / Enhancements
Added message when websocket is connected
Docs
Added message when websocket is connected

please change the commit header to feat(graphql): print the connection status with ws

also the CI is complaing
8s
Run make ci_fmt_client
dart pub global run melos run client_analyze --no-select
melos run client_analyze
  └> melos exec -c [1](https://github.com/zino-hofmann/graphql-flutter/actions/runs/4425459030/jobs/7760880769#step:5:1) -- "dart format --set-exit-if-changed . && dart analyze . --fatal-infos"
     └> RUNNING

$ melos exec
  └> dart format --set-exit-if-changed . && dart analyze . --fatal-infos
     └> RUNNING (in 2 packages)

--------------------------------------------------------------------------------
example:
Formatted 3 files (0 changed) in 0.2[7](https://github.com/zino-hofmann/graphql-flutter/actions/runs/4425459030/jobs/7760880769#step:5:8) seconds.
Analyzing ....
No issues found!
example: SUCCESS
--------------------------------------------------------------------------------
graphql:
Formatted lib/src/links/websocket_link/websocket_client.dart
Formatted 54 files (1 changed) in 0.79 seconds.
--------------------------------------------------------------------------------

$ melos exec
  └> dart format --set-exit-if-changed . && dart analyze . --fatal-infos
     └> FAILED (in 1 packages)
        └> graphql (with exit code 1)

melos run client_analyze
  └> melos exec -c 1 -- "dart format --set-exit-if-changed . && dart analyze . --fatal-infos"
     └> FAILED
ScriptException: The script client_analyze failed to execute
make: *** [Makefile:[32](https://github.com/zino-hofmann/graphql-flutter/actions/runs/4425459030/jobs/7760880769#step:5:33): ci_fmt_client] Error 1

Changed

Need commit need to be removed https://github.com/zino-hofmann/graphql-flutter/pull/1309/commits/7757b8b17cfaf4cb83e856cde5238d841cf8d406
This required to squash your commit with the previous one

when it will be released?


Choose assay for Seurat objects?

Is there any way we can specify the assay to pull data from? This matters for Seurat objects because integrated assays don't typically contain all genes, and SCT assay normalized counts often have noise regressed out that makes the counts dependent in some way on each other.
Typically, the "RNA" assay is what is wanted, but it'd be nice to be able to specify this directly. I have not dug through the source code to see how the current assay is chosen, but I assume it just uses the default assay of the object?

I guess one can always change the assay of the object itself using DefaultAssay, but that gets a bit annoying swapping back and forth.

You are correct that DittoSeq currently uses the default assay.

I think adding this option would require a new, Seurat-v3 specific, input for most viz functions + my gene extraction-related functions + dimensional reduction extraction functions.  It can be done, but would take time.

Yeah, this is probably something best just left to the user then, frankly. Noting it in the docs may be a good idea, but I wouldn't make adding it a huge priority.

I'm glad you agree =p.


About the featuremetric alignment.

Thanks for the excellent work on Structure from Motion.
One question for the paper:
In the feature extraction, are the features extracted from the pre-trained CNNs? Since I found no loss function to train the CNNs.

Thanks for your question. We indeed use pre-trained CNNs. Most experiments are conducted with S2DNet (Germain et al. ECCV 2020) but we also experiment with other weights in the ablation study (Table 4).


Pkg-config not in path when installing formula

Trying to install a formula and was getting error about ncurses not installed.
Investigate further it shows pkg-config is the one at /usr/bin
~/.linuxbrew/bin is not in the path of the shell (by entering the shell using brew install --debug)
How should I debug this?
Thanks!

Which formula are you trying to install?

Thanks. The formula I am trying to install is progress and it is not using what you mentioned here.


Build with aot or prod flag with error

When I'm building a project with query builder with ng build --aot or ng build --prod I get the following error:
ERROR in Unexpected value 'QueryBuilderModule in /.../node_modules/angular2-query-builder/dist/angular2-query-builder/bundles/angular2-query-builder.umd.js' imported by the module 'AppModule in /.../src/app/app.module.ts'. Please add a @NgModule annotation.
Without the flags, with a simple ng build, everything works fine.
I'm using angular 8 and my declarations are the following:
import { BrowserModule } from '@angular/platform-browser';
import { NgModule } from '@angular/core';
import {FormsModule} from '@angular/forms';
import { AppComponent } from './app.component';
import { QueryBuilderModule } from 'angular2-query-builder';

@NgModule({
  declarations: [
    AppComponent
  ],
  imports: [
    BrowserModule,
    FormsModule,
    QueryBuilderModule
  ],
  providers: [],
  bootstrap: [AppComponent]
})
export class AppModule { }

Anyone can point me in the right direction for this one?
Thanks for your help.

Please note that this is only with angular cli 8.
With angular cli 7, works fine.

same with 9th