Add schema checks to make sure all block have metadata

In this repository all the <pb_type> objects should have a metadata tag which contains;
 <metadata>
  <meta name="type>xxxx</meta>
  <meta name="subtype>xxxx</meta>
</metadata>

It should also check that the type + subtype values are valid.

Previously it was;

Names are of the form XXX_YY-aaaaaa where;

XXX is the high level type of the block. It should be one of;

BLK, for composite blocks,
BEL, for primitives which can not be decomposed, or
PAD, for special input/output blocks.

YY is the subtype of the block. It is dependent on the high level block
type.

aaaaa is the name of the block. The name should generally match both the
file and directory that the files are found in.

BLK_MB-block_1_name-block_2_name - BLOCK which is a "mega block".

BLK_XX-name       - BLOCK which is the hierarchy. Maps to BLK_SI -> SITE and BLK_TI -> TILE in Xilinx terminology.

BLK_IG-name       - BLOCK which is ignored. They don't appear in the output hierarchy and are normally used when something is needed in the description which doesn't match actual architecture.

BEL_RX-mux_name   - BEL which is a routing mux. Routing muxes are statically configured at PnR time.

BEL_MX-mux_name   - BEL which is a mux .

BEL_LT-lut_name   - BEL which is a look up table.

BEL_MM-mem_name   - BEL which is a memory.

BEL_FF-ff_name    - BEL which is a flip flop (FF).

BEL_LL-latch_name - BEL which is a latch (LL).

BEL_BB-name       - BEL which is a black box (BB).

PAD_IN-name       - A signal input location.

PAD_OT-name       - A signal output location.

I think the valid types are;

bel
block

If type is bel then valid subtypes are;

routing - Routing mux
lut - Lookup table.
flipflop - Lookup table.
memory - Memory.
blackbox - Black box object.

If type is block then valid subtypes are;

tile
slice
ignore

@Laksen do you know how to do this?

@mithro not sure. Can you give an example of a valid metadata block?

@Laksen In words it would be;

A <pb_type> tag should contain a <metadata> tag.
A <pb_type> with a <metadata> tag should have a <meta name="type"> and a ```
<meta name="type"> text value should be one of bel or block
If <pb_type> has <meta name="type>block</meta> then the text value of <meta name="subtype"> should be tile, slice or ignore.
If <pb_type> has <meta name="type>bel</meta> then the text value of <meta name="subtype"> should be routing, lut or flipflop, ....

Valid example;
<pb_type>
 <metadata>
   <meta name="type">bel</meta>
   <meta name="subtype">routing</meta>
 </metadata>
</pb_type>

Broken example -- missing <meta name="subtype">;
<pb_type>
 <metadata>
   <meta name="type">bel</meta>
 </metadata>
</pb_type>

Broken example -- <meta name="type"> text value is invalid;
<pb_type>
 <metadata>
   <meta name="type">random</meta>
   <meta name="subtype">routing</meta>
 </metadata>
</pb_type>

Broken example -- <meta name="subtype"> text value is invalid for <meta name="type">block</meta>;
<pb_type>
 <metadata>
   <meta name="type">block</meta>
   <meta name="subtype">routing</meta>
 </metadata>
</pb_type>

@mithro Can the metadata contain other meta tags? Is it okay to enforce ordering (subtype meta tags should follow type meta tags)?

@Laksen Yes, it can contain other <meta name="xxx"> values.

@Laksen I think enforcing ordering should be fine?

@mithro Hmm. Don't think it's possible with a version 1.0 schema

@Laksen Should be able to enforce some parts (like must have a <metadata> and <meta name="type"> tags).

You can guarantee that there should be a meta element with that name and that type attribute. But nothing more really. It's very context sensitive and not good xml, from reading about it.
Could the overall design be changed?

@Laksen How would you suggest it be changed?


Nightly publish NPM packages

Context: https://github.com/knative-extensions/backstage-plugins/pull/13#discussion_r1439249304

/close
This is done. ...slightly different way. Instead of publishing every night, a snapshot is published with every commit pushed to main


The SSL authentication fails in the Java test of the CI.

[ ] Did you create an Apache Jira ticket?  (not required for trivial changes)
[ ] If a ticket exists: Does your pull request title follow the pattern "THRIFT-NNNN: describe my issue"?
[ ] Did you squash your changes to a single commit?  (not required, but preferred)
[ ] Did you do your best to avoid breaking changes?  If one was needed, did you label the Jira ticket with "Breaking-Change"?
[ ] If your change does not involve any code, include [skip ci] anywhere in the commit message to free up build resources.

Hi,
After many tests (each time waiting for CI execution is too long, which is equivalent to a basketball game), this problem has been determined to be a cross-language SSL communication test between a Java service and an erlang client, because erlang is not familiar to me, and I carelessly ignored it earlier.
Now, I only add the keystore and truststore to java-test and quickly check the test_client of Erlang. For --ssl, there are ssltransport and certificate. Next, I need to confirm the protocols on both sides. Has anyone investigated the CI problem?
Any help is welcome.

Hi @zeshuai007 — I was looking if anyone has done anything to fix this thing on Travis:
===============================================================================
*** Following 6 failures were unexpected ***:
If it is introduced by you, please fix it before submitting the code.
===============================================================================
server-client:          protocol:         transport:               result:
java-erl                multi-binary      fastframed-framed-ip-ssl failure(1)
java-erl                multi-binary      buffered-ip-ssl          failure(1)
java-erl                multi-binary      framed-ip-ssl            failure(1)
java-erl                binary            fastframed-framed-ip-ssl failure(1)
java-erl                binary            buffered-ip-ssl          failure(1)
java-erl                binary            framed-ip-ssl            failure(1)
===============================================================================

And I see you added explicit truststore support in the Test{Client,Server} for Java. Do you need the same for Erlang?

Hi @ulidtko
Sorry we didn't get updates in time.
This problem is caused by the communication authentication failure between the Java server and Erlang client. The cause has been found out.
The Erlang community released OTP-23 in May this year. This version has major changes that damage compatibility. SSL3.0 is abandoned and TLS1.3+TLS1.2 is used by default. However, the Java server uses TLS1.2 by default and does not support TLS1.3. Therefore, the Travis-CI integration test has not been working properly since the end of May.
For now, I think a feasible solution is available.

By default, Travis-CI uses the latest Erlang version for integration tests. It may be set to OTP-22. After all, the Erlang version 22 is also specified on the readme.
Upgrade JDK8 to JDK11. TLS1.3 is supported by default.
The TLS1.3 protocol can also be supported on JDK8. That's what I've been working on.

Hi @zeshuai007

SSL3.0 is abandoned

That's a good update.

and TLS1.3+TLS1.2 is used by default. However, the Java server uses TLS1.2 by default and does not support TLS1.3.

This gives me doubt about whether the root cause was identified correctly and precisely. TLS protocol, just like every other good protocol, has versions, and allows both the client and the server to support multiple versions. As long as the Java server speaks TLS1.2, any client which speaks TLS1.2 should be able to connect — regardless of TLS1.3.

The Erlang community released OTP-23 in May this year.

BTW, last successful build of master on Travis is 7 months old. I am in doubt whether Erlang update is really relevant. But I understand that it certainly makes finding the real root cause more complicated.

It may be set to OTP-22.
That's not a good idea. It will only entrench the stagnation and multiply the effort to update for the next engineer.

Whew, what a ride! Diving into Erlang is joy.
I did a bit of testing on this... Except for the fiddly setup and a few deprecation-updates needed, the Erlang library looks mostly functional. All unit-tests under lib/erl/test pass (well, after you've had enough fun with the setup required to run them).
I also run the Erlang client on OTP 23 against some implementations, including the Java server from the cross-test suite. Findings:

The Erlang client does connect to openssl s_server using TLS1.2.

The Erlang client does connect to openssl s_server using TLS1.3.

The Erlang client does connect to openssl s_server using TLS1.2 with client cert required (-Verify 2).

The Erlang client does connect to openssl s_server using TLS1.3 with client cert required (-Verify 2).

The Erlang client does not connect to socat - openssl-listen:9008,cert=test/keys/server.pem,cafile=test/keys/CA.pem despite using the very same OpenSSL; error produced:
socat[1847925] E SSL_accept(): error:1417C086:SSL routines:tls_process_client_certificate:certificate verify failed

I tend to think it's a bug in how socat instructs the openssl API to verify client certs. Didn't investigate this deeper.

The Java cross-test server [on git master] claims to only support TLS1.3:

Which is really really weird. I'm not sure this is intentional. Somebody needs to check this. @zeshuai007 please see above; bytes on the wire directly contradict your claim "the Java server uses TLS1.2 by default and does not support TLS1.3". It shows the opposite: TLS1.3 only is advertised by the Java server. I'm running openjdk version "11.0.8" 2020-07-14.

You can run a section of the Thrift cross-test suite (a.k.a. "Apache Thrift - Integration Test Suite") directly:
./test.py --server java --client erl --regex ip-ssl

This runs in ~20 seconds. Still way faster than waiting many basketball games for Travis to run it. :wink:

Finally: the TLS 1.3 connection from Erlang client to Java server does not go well indeed. Here's a debug dump from Erlang side: java-erl-tls1.3_client.log. It appears that the Java server is doing something that makes the Erlang client crash :/
Anyhow, all tests pass if I restrict Erlang to only TLS 1.2 & TLS 1.1:
ulidtko@pasocon ~/s/t/test (master)> ./test.py --server java --client erl
Apache Thrift - Integration Test Suite
Sun Aug 09 20:37:26 2020
===============================================================================
server-client:          protocol:         transport:               result:
java-erl                binary            buffered-ip              success
java-erl                binary            fastframed-framed-ip     success
java-erl                binary            framed-ip                success
java-erl                binary            fastframed-framed-ip-ssl success
java-erl                binary            framed-ip-ssl            success
java-erl                binary            buffered-ip-ssl          success
java-erl                multic-compact    framed-ip                success
java-erl                multic-compact    buffered-ip              success
java-erl                multic-compact    framed-ip-ssl            success
java-erl                multic-compact    buffered-ip-ssl          success
java-erl                multic-compact    fastframed-framed-ip     success
java-erl                multic-compact    fastframed-framed-ip-ssl success
java-erl                multi-binary      framed-ip                success
java-erl                multi-binary      buffered-ip              success
java-erl                multi-binary      fastframed-framed-ip     success
java-erl                multi-binary      framed-ip-ssl            success
java-erl                multi-binary      buffered-ip-ssl          success
java-erl                multi-binary      fastframed-framed-ip-ssl success
java-erl                compact           framed-ip                success
java-erl                compact           framed-ip-ssl            success
java-erl                compact           buffered-ip              success
java-erl                compact           fastframed-framed-ip     success
java-erl                compact           buffered-ip-ssl          success
java-erl                compact           fastframed-framed-ip-ssl success
===============================================================================
No unexpected failures.

... Which is be done by passing -ssl protocol_version "['tlsv1.2', 'tlsv1.1']" to the erl invocation.

Amusingly, the very same Java server which says it only speaks TLS1.3 to TLS1.3 clients — suddenly starts talking TLS1.2 just fine, to a non-tls13 client. What a mess!

Hi @ulidtko
I'm not sure whether this is a new issue.
The Java8 server supports only TLS1.2. When negotiating with the Erlang client over the TLS protocol, the Java8 server does not support TLS1.3. I think we should revert to the actual scenario because JDK8 was used in the Tranov-ci integration test. Can you use JDK8 to retest it?
Cheers,
Zezeng Wang

Hi @zeshuai007 — well, that totally makes sense.
I retested with Java 8 (OpenJDK as before).
The result with Java8 (for test.py --server java --client erl only) is success of all tests for me. Both with TLS1.3 allowed and disallowed for the Erlang client — the java server doesn't offer TLS1.3, exactly as you say; so it just negotiates down to TLS1.2, and all proceeds well from there.
Which is a puzzling result. I remember seeing this failure on Travis — but can no longer find any build exhibiting it. Do you perhaps have a link to such a build on Travis?
I did found one from March 22, which has reached running the cross step — and had passed all of it (log line 21337 onwards). Notice (log line 13268) that it used Java 11!
That confused me at first, since Java11 + Erlang23 = TLS1.3 = broken according to my testing, should not have passed — but as you mention, Erlang/OTP 23 was only released in May, later than the build I linked.
What makes you think that Java 8 is in use? Can you find a failed build with Java 8 on Travis?

Just to keep track of things:

I minimized the TLS 1.3 handshake failure against Java 11 — filed as https://bugs.erlang.org/browse/ERL-1331
The issue can be temporarily worked around by adding "-ssl", "protocol_version", "['tlsv1.2', 'tlsv1.1']", to the Erlang client commandline in tests.json — this disables TLS1.3 on Erlang side and then all java-erl cross-tests pass.

Hi @ulidtko
I didn't investigate the CORSS run you found on March 22, but in all the compilation builds on Travis, I compared the last successful run log of erlang22 jobs to the last failed run log of erlang23, so I'm sure, this problem is caused by the upgrade to erlang23.
Travis-CI:
erlang22 - Last successful (build#6701)
https://travis-ci.org/github/apache/thrift/jobs/692484722
erlang23 - First execution failed (build#6702)
https://travis-ci.org/github/apache/thrift/jobs/692597058
Note that log line 13101 uses jdk11, and JAVA_HOME set in log line 12340 is java-8-oracle (Java JVM running environment, so I think Java8 is used actually).
Therefore, erlang-client uses TLS1.3 (Erlang23 supports two TLS versions, which seems to be a feature of the new Erlang version) and Java-server (JDK11/TLS1.3) / (JDK8/TLS1.2).
Thank you for your work. If there is no better solution, setting up TLS1.2+TLS1.1 temporarily will look great as setting up Erlang22, but it will require two or more post-maintenance. I saw the ticket you submitted in Erlang, and I look forward to the Erlang expert's investigation.
I have plans to learn Erlang recently, and unfortunately for some reason I'm focusing on C, but I'll be back.
Cheers,
Zezeng Wang

JAVA_HOME set in log line 12340 is java-8-oracle

Okay, I understand now. Let me convince you that this is noise and Java8 is not actually used. Two reasons:

This line 12340 is part of output from printenv | sort from build/docker/run.sh: it shows the JAVA_HOME environment variable set outside the Docker container. It's not existing inside the container where ./configure and tests run.
If it was — we'd see Oracle JDK 8, not OpenJDK, in the output of ./configure (line 13101).

I'm glad to collaborate for the public good and for safe and sustainable future of technology. Thanks for your responses, effort and friendliness in this space, Zezeng Wang, this is deeply appreciated.

Heads up about the Erlang TLS 1.3 issue:

This is a known bug;
It is already fixed, but isn't released yet;
OTP 23.1 is planned for release in September, and will contain the fix for TLS 1.3;
OTP 24 is planned for release on a yearly timescale, and will contain the fix too.

This PR resolves the CI issue caused by the upgrade from Erlang23 to TLS1.3. This issue has been resolved in OPT23.1 [https://bugs.erlang.org/browse/ERL-1331]. Therefore, I close this PR.
It should be noted that the current CI issue is a rebar3 issue and should be tracked on other tickets.


Exclude meshes from SSAO2 pipeline

Is your feature request related to a problem? Please describe.
SSAO renders on the yellow skybox, making the sky black:

Describe the solution you'd like
It should be easy to exclude skybox from SSAO
There should be a way to exclude meshes or materials, i.e. ssao2Pipeline.excludeMeshes = [ skyboxMesh ]
Discussion
https://www.html5gamedevs.com/topic/34132-how-i-can-exclude-skybox-from-ssao/

Hello do you mind checking on the "new" forum first: forum.babylonjs.com?
Thanks a lot

@deltakosh Only thing I can find is this and looks like they also could not find a good solution

Sorry I meant: please discuss that topic on the new forum (Create an thread) so we can see how we can help

Okay cool will do


Fix docs

Referenced issues
None
Description of the Change
Minor issues in docs
Benefits
Fixed docs
Possible Drawbacks
None

✨👍✨


MultiExecutor is not working now.

I forgot from which version, our app sometimes encounters the error Unhandled Exception: Operation was cancelled, but recently it has become more and more frequent. We finally found out that it was caused by MultiExecutor, but we really need parallel queries (some queries are too slow).
Below is our code for creating the database.
Future<Database> connectToDatabase({
  bool fromMainIsolate = false,
}) async {
  const writePortName = 'write';
  const readPortName = 'read';

  final isolates = await Future.wait([
    _crateIsolate(
      writePortName,
      fromMainIsolate: fromMainIsolate,
    ).then((value) => value.connect()),
    ...List.generate(
        4,
        (index) => _crateIsolate(
              '$readPortName$index',
              fromMainIsolate: fromMainIsolate,
            ).then((value) => value.connect())),
  ]);

  final executor = isolates[0].withExecutor(MultiExecutor.withReadPool(
    reads: isolates.skip(1).toList(),
    write: isolates[0],
  ));

  return Database(executor);
}

Future<DriftIsolate> _crateIsolate(
  String name, {
  bool fromMainIsolate = true,
}) async {
  if (fromMainIsolate) {
    // Remove port if it exists. to avoid port leak on hot reload.
    IsolateNameServer.removePortNameMapping(name);
  }

  final existedSendPort = IsolateNameServer.lookupPortByName(name);

  if (existedSendPort == null) {
    assert(fromMainIsolate, 'Isolate should be created from main isolate');

    final directory = (await getApplicationDocumentsDirectory()).path;
    String path = p.join(directory, 'db.sqlite');

    final dbFile = File(path);

    final driftIsolate = await DriftIsolate.spawn(
        () => LazyDatabase(() => NativeDatabase(dbFile, setup: (rawDb) {
              rawDb
                ..execute('PRAGMA journal_mode=WAL;')
                ..execute('PRAGMA foreign_keys=ON;')
                ..execute('PRAGMA synchronous=NORMAL;');
            })));

    IsolateNameServer.registerPortWithName(driftIsolate.connectPort, name);
    return driftIsolate;
  } else {
    return DriftIsolate.fromConnectPort(existedSendPort, serialize: false);
  }
}

stack trace:
[ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: Operation was cancelled
#0      checkIfCancelled (package:drift/src/runtime/cancellation_zone.dart:91:5)
#1      _BaseExecutor._runRequest (package:drift/src/remote/client_impl.dart:87:5)
#2      _BaseExecutor.runSelect (package:drift/src/remote/client_impl.dart:130:26)
#3      DatabaseConnection.runSelect (package:drift/src/runtime/api/connection.dart:108:16)
#4      _QueryExecutorPool._run (package:drift/src/runtime/executor/connection_pool.dart:97:10)
#5      _QueryExecutorPool.runSelect (package:drift/src/runtime/executor/connection_pool.dart:77:5)
#6      _MultiExecutorImpl.runSelect (package:drift/src/runtime/executor/connection_pool.dart:146:26)
#7      SimpleSelectStatement._getRaw.<anonymous closure> (package:drift/src/runtime/query_builder/statements/select/select.dart:68:16)
#8      DatabaseConnectionUser.doWhenOpened.<anonymous closure> (package:drift/src/runtime/api/connection_user.dart:162:64)
#9      _rootRunUnary (dart:async/zone.dart:1406:47)
#10     _CustomZone.runUnary (dart:async/zone.dart:1307:19)
<asynchronous suspension>
#11     NonNullableCancellationExtension.resultOrNullIfCancelled (package:drift/src/runtime/cancellation_zone.dart:62:24)
<asynchronous suspension>
#12     QueryStream.fetchAndEmitData (package:drift/src/runtime/executor/stream_queries.dart:315:20)
<asynchronous suspension>

demo: https://github.com/YeungKC/drift_issue_2323

Thanks for the report! I'll need to investigate this further, do you get a stack trace for the Operation was cancelled errors?

I updated demo and stack trace. Please check it.

@simolus3
This is very important to us. Do you have any ideas?

@YeungKC Sorry for the delay! Your example works with b137b4065e5e4b3e6a7eeab844c6c77bdf6ab95b, can you check if that also fixes the problem in your app?

@simolus3
The commit works fine in the demo without any CancellationException, but it is still occurring in our project which is much more complex.
I am still trying to reproduce it in the demo.

There has been no activity in this issue for over a year and no reproducible bug exists.


SVN Add Functionality.

Whenever we add new file to the project or solution, SVN is not able to add that file to repository. Is this enhancement is possible?

Added as an option in the new 4.3.23 release!

Thanks @sboulema , Will test and provide you feedback.

Its working as expected, Thanks again @sboulema . Your are doing wonderful job.


failed to download -  curl option ?

trying to install ruby
yves@MacMini: ~ $ rbenv install 2.2.2    ( same with 2.2.3 )
Downloading ruby-2.2.2.tar.gz...
/usr/local/bin/ruby-build: line 288: 82656 Trace/BPT trap: 5       curl -qsILf ${options} "$1" 1>&4 2>&1
-> https://cache.ruby-lang.org/pub/ruby/2.2/ruby-2.2.2.tar.gz
error: failed to download ruby-2.2.2.tar.gz
BUILD FAILED (OS X 10.11 using ruby-build 20150928)
it seems that my curl doesn't accept these options .. -qsILf  ,  I had to install brew with the -k option

Dup of https://github.com/sstephenson/ruby-build/issues/812


Why would Typhoeus be hammering my site causing it to crash

ec2-54-204-92-226.compute-1.amazonaws.com - - [01/Apr/2015:11:07:49 -0500] "HEAD /publications/ HTTP/1.1" 403 - "-" "Typhoeus - https://github.com/typhoeus/typhoeus"
The above keeps either slowing my site down or crashing it entirely. It happens every couple days.
It's a Wordpress site. How do I get this to stop?

Hi.
Typhoeus is an HTTP client, so this line tells me that someone is using it to access your website.
Because the issues are for issues with the gem itself, there isn't much we can do to help out :-(
Good luck.

You could blacklist it by user agent (Typhoeus - https://github.com/typhoeus/typhoeus).
You can't do much other than that.

Same with me. My website is also down because of this.
<IP_ADDRESS> - - [13/Apr/2015:22:18:22 +0000] "HEAD /about/ HTTP/1.1" 200 - "-" "Typhoeus - https://github.com/typhoeus/typhoeus"

The above keeps either slowing my site down or crashing it entirely. How do I get this to stop?

You're not by any chance also using Wordpress are you?

Btw that IP address belongs to Amazon AWS, it looks like someone's enumerating files and directories, probably as part of an unauthorized vulneravility scan.
You should contact Amazon AWS, there's nothing we can do.

Yes, I am using WordPress. You said something about blocking user agent. How to do that on Linux server?

I've no idea, depends on your firewall config. You should contact your hosting provider, maybe hey can help you out.

using a cdn would be another option.


Smoketest failures after 2018_07 import

call_command ('run_smoketests', '2018_07')
.........F.F
======================================================================
FAIL: test_chemical_by_one_practice (pipeline.smoketests.TestSmokeTestSpendingByOnePractice)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/webapps/openprescribing/openprescribing/pipeline/smoketests.py", line 98, in test_chemical_by_one_practice
    params
  File "/webapps/openprescribing/openprescribing/pipeline/smoketests.py", line 40, in _run_tests
    self.assertEqual(len(all_rows), PRESCRIBING_DATA_MONTHS)
AssertionError: 58 != 60

======================================================================
FAIL: test_presentation_by_one_practice (pipeline.smoketests.TestSmokeTestSpendingByOnePractice)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/webapps/openprescribing/openprescribing/pipeline/smoketests.py", line 90, in test_presentation_by_one_practice
    params
  File "/webapps/openprescribing/openprescribing/pipeline/smoketests.py", line 40, in _run_tests
    self.assertEqual(len(all_rows), PRESCRIBING_DATA_MONTHS)
AssertionError: 58 != 60

----------------------------------------------------------------------
Ran 12 tests in 5.407s

FAILED (failures=2)

These failures suggest that the API is only returning 58 months of data when we expect 60 months.  (60 == 12 * 5, ie five years.)
The tests are making requests to the following end points:

https://openprescribing.net/api/1.0/spending_by_practice/?format=json&code=0212000AA&org=A81015
https://openprescribing.net/api/1.0/spending_by_practice/?format=json&code=0703021Q0BBAAAA&org=A81015

For both endpoints we're getting 58 records, for dates between 2013_08 and 2018_05 (inclusive):
>>> rsp = requests.get('https://openprescribing.net/api/1.0/spending_by_practice/?format=json&code=0212000AA&org=A81015')
>>> rr = rsp.json()
>>> len(rr)
58
>>> min(r['date'] for r in rr)
'2013-08-01'
>>> max(r['date'] for r in rr)
'2018-05-01'

The practice in question has prescribed nothing for 0212000AA or 0703021Q0BBAAAA in 2018_06 or 2018_07:
>>> Prescription.objects.filter(practice=p, processing_date__in=['2018-06-01', '2018-07-01'], presentation_code__startswith='0212000AA').count()
0
>>> Prescription.objects.filter(practice=p, processing_date__in=['2018-06-01', '2018-07-01'], presentation_code__startswith='0703021Q0BBAAAA').count()
0

The practice hasn't closed:
>>> Practice.objects.get(pk='A81015').close_date is None
True

But the practice has prescribed significantly less in 2018_06 and 2018_07:
>>> for month in '34567':
...   date = '2018-0{}-01'.format(month)
...   print date, Prescription.objects.filter(practice=p, processing_date=date).count()
...
2018-03-01 901
2018-04-01 925
2018-05-01 497
2018-06-01 95
2018-07-01 42

Which suggests it may be in the process of closing.
And yes, it's dormant:
>>> Practice.objects.get(pk='A81015').status_code
u'D'


SPARK-30975: rename config spark memoryOverhead

What changes were proposed in this pull request?
Rename spark config to the new one for memoryOverhead
Why are the changes needed?
Remove old name in the configuration, it will be deprecated
Does this PR introduce any user-facing change?
Yes, we change the config parameter name
How was this patch tested?
No need

Can one of the admins verify this patch?

Can one of the admins verify this patch?

I don't think this a necessary change, the config spark.yarn.driver.memoryOverhead is still being used in a few production workloads (as I grep the config name in Spark JIRA issues), also the maintaining burden of this alternative config is very close to zero.


Suggestion to create tempory files used by the converter  in the user area's temp folder

Thanks for your very appealing tool.
When launching it from Windows PowerShell, it attempts creating a temporary file in  PowerShell's installation folder. This folder requires elevation to write to. May I suggest creating the temporary file in the user area instead.
Steps to reproduce:
Add-Type -path 'C:\Program Files\PackageManagement\NuGet\Packages\CoreHtmlToImage.1.0.5\lib\netstandard2.0\CoreHtmlToImage.dll' -PassThru
$converter = [CoreHtmlToImage.HtmlConverter]::new()
$converter.FromHtmlString('Hello World!', 100)
Exception calling "FromHtmlString" with "2" argument(s): "Access to the path
'C:\WINDOWS\system32\WindowsPowerShell\v1.0\eec70834-fbf7-47dc-8ae6-dd55a6e970dc.html' is denied."

@wi-fr it creates an .exe file in the working directory. Apparently for powershell system32 is a working directory. I think it is ok and as you pointed out you can use elevated permissions. I wouldn't expect the package to be used from the command line. I suggest you to use wkhtmltoimage.exe directly instead of using my library as that is what I use under the hood.

Thanks for the feedback. I used it from the PowerShell command line just to illustrate the issue. As you suggested, I switched over to wkhtmltoimage.exe.


Where is the ontology hosted?

This https://purl.industrialontologies.org/ontology/core/Core/ 404s

I think this is being updated. You can download ontology from the git repo.


🐞 [Bug]: colors are not visible in live and operational section in landing page light mode

Is there an existing issue for this?

[X] I have searched the existing issues

which package/s did you face the problem with?
Dashboard
What happened?
The live and operational section in the dashboard landing page are not visible in light mode; however it works fine in dark mode.
Steps To Reproduce
No response
which network/s did you face the problem on?
Dev, QA, Test, Main
version
2.6.2
Twin ID/s
No response
Node ID/s
No response
Farm ID/s
No response
Contract ID/s
No response
Relevant screenshots/screen records

Relevant log output
--

Work done waiting for review

Verified on Dev,
Version: f0f91d9
The map image has been updated to be clear in light mode

Related Link:

https://app.testlodge.com/a/26076/projects/40893/runs/763032?tab=2#executed_case_33539733


Should DeployDB accept/store more detailed version information?

We had some discussions around this a long time ago inside of @Lookout, but the gist of the idea would be to allow tooling in Jenkins (for example) to publish the full dependency tree for a .war artifact.
This might just be the parse output of ./gradlew dependencies for all I care, but being able to look up the disparate versions of dependencies between artifacts would be valuable both in aggregate ("who's using jruby-jars 1.7.16?") and in a debuggin scenario ("what went into this artifact?")

That sounds like a good idea. I assume you're including the transitive
dependencies. For me, the most human readable way to do that is with
dependency:tree
On Wed, Jan 14, 2015 at 9:37 AM, R. Tyler Croy<EMAIL_ADDRESS>wrote:

We had some discussions around this a long time ago inside of @Lookout
https://github.com/Lookout, but the gist of the idea would be to allow
tooling in Jenkins (for example) to publish the full dependency tree for a
.war artifact.
This might just be the parse output of ./gradlew dependencies for all I
care, but being able to look up the disparate versions of dependencies
between artifacts would be valuable both in aggregate ("who's using
jruby-jars 1.7.16?") and in a debuggin scenario ("what went into this
artifact?")
—
Reply to this email directly or view it on GitHub
https://github.com/lookout/deploydb/issues/16.

@csanders-lookout yeah, my thinking does include transitive dependencies particularly for java-based artifacts.

Yeah - then we should push a similarly version dependency tree flat file
for each war. Or, alternatively, we could put it in the war metadata
directory. It'll be pretty small.
On Wed, Jan 14, 2015 at 10:53 AM, R. Tyler Croy<EMAIL_ADDRESS>wrote:

@csanders-lookout https://github.com/csanders-lookout yeah, my thinking
does include transitive dependencies particularly for java-based artifacts.
—
Reply to this email directly or view it on GitHub
https://github.com/lookout/deploydb/issues/16#issuecomment-69969398.

similarly versioned
On Wed, Jan 14, 2015 at 11:17 AM, Carter Sanders<EMAIL_ADDRESS>
wrote:

Yeah - then we should push a similarly version dependency tree flat file
for each war. Or, alternatively, we could put it in the war metadata
directory. It'll be pretty small.
On Wed, Jan 14, 2015 at 10:53 AM, R. Tyler Croy<EMAIL_ADDRESS>wrote:

@csanders-lookout https://github.com/csanders-lookout yeah, my
thinking does include transitive dependencies particularly for java-based
artifacts.
—
Reply to this email directly or view it on GitHub
https://github.com/lookout/deploydb/issues/16#issuecomment-69969398.

I spoke with @cbleach about this IRL and for the purposes of baking AMIs and using DeployDB to track AMIs through a pipeline (as artifacts).  We would want to know all the version information not only of the artifact (e.g. .war) but also the versions of cookbooks, etc that were used to bake the AMI.

OK - so that's more than maven will give us. Sounds like we need a custom
script.
On Wed, Jan 21, 2015 at 4:47 PM, R. Tyler Croy<EMAIL_ADDRESS>wrote:

I spoke with @cbleach https://github.com/cbleach about this IRL and for
the purposes of baking AMIs and using DeployDB to track AMIs through a
pipeline (as artifacts). We would want to know all the version information
not only of the artifact (e.g. .war) but also the versions of cookbooks,
etc that were used to bake the AMI.
—
Reply to this email directly or view it on GitHub
https://github.com/lookout/deploydb/issues/16#issuecomment-70952008.

After much discussion with @polynomial on the subject he's convinced me that this should not go into DeployDB. There's a definite requirement for it somewhere in the Ci/CD ecosystem so maybe we'll build an ArtifactDB at some point, but for now I'm closing this with prejudice :)

Here are my thoughts on #16 and #20.
To answers the questions described in the issue. We need to model the dependency information as a "artifact dependency graph".   Libraries we should look at are. JUNG, JGraphT, neo4j. An approach to store the graph data in persistent memory can be what's described in this presentation. http://www.slideshare.net/billkarwin/models-for-hierarchical-data


[QUESTION]Error Azure Active Directory is only supported on Windows operating systems

Question
Regarding the connection issue to Azure SQL server database with Azure Active Directory, running into an error and hopefully we could get official support on this. Thank you!

Details:

System details:  Ubuntu 16.04.3 LTS (GNU/Linux 4.15.0-1039-azure x86_64)

Programming Language: Java

classpath jar file: sqljdbc42.jar

Detailed Error Response from below code snippets with above system and jar lib file:

com.microsoft.sqlserver.jdbc.SQLServerException: Azure Active Directory is only supported on Windows operating systems.
        at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectInternal(SQLServerConnection.java:1289)
        at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:773)
        at com.microsoft.sqlserver.jdbc.SQLServerDataSource.getConnectionInternal(SQLServerDataSource.java:704)
        at com.microsoft.sqlserver.jdbc.SQLServerDataSource.getConnection(SQLServerDataSource.java:54)
        at AADUserPassword.main(AADUserPassword.java:21)

Here are the sample code we tried:
The first attempt
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.SQLException;

public class main {
    public static void main(String args[]) throws SQLException {
        String driver = "com.microsoft.sqlserver.jdbc.SQLServerDriver";
        try {
        Class.forName(driver).newInstance();
        String url = "jdbc:sqlserver://XXXX.database.windows.net;database=${dbname};sslProtocol=TLSv1.2;encrypt=true;hostNameInCertificate=*.database.windows.net;authentication=ActiveDirectoryPassword";

        String username = ${user_name};

        String password = ${password};

        Connection conn = DriverManager.getConnection(url, username, password);
       }catch (Exception e) {
            e.printStackTrace();
        }
    }
}

The second attempt. and this is the Azure official document AAD example
import java.sql.Connection;
import java.sql.ResultSet;
import java.sql.Statement;

import com.microsoft.sqlserver.jdbc.SQLServerDataSource;

public class AADUserPassword {

    public static void main(String[] args) throws Exception{

        String driver = "com.microsoft.sqlserver.jdbc.SQLServerDataSource";
        Class.forName(driver).newInstance();

        SQLServerDataSource ds = new SQLServerDataSource();
        ds.setServerName("XXXX.database.windows.net"); // Replace with your server name
        ds.setDatabaseName(${dbname}); // Replace with your database
        ds.setUser(${user_name}); // Replace with your user name
        ds.setPassword(${password}); // Replace with your password
        ds.setAuthentication("ActiveDirectoryPassword");

        try {Connection connection = ds.getConnection();
                Statement stmt = connection.createStatement();
      }catch(Exception e){
              e.printStackTrace();
        }
    }
}

Hi @BingjieGao
Please verify driver version in use. AAD Support for cross platform authentication is available from JDBC driver v6.4 onwards and we recommend using latest driver v7.2 which also contains improvements and fixes. Please find more information here and download latest driver v7.2 to test the same.
Thanks.

Closing due to inactivity. Please feel free to re-open or create another thread if there's an update.


fix: update docker.sh statement, deduplicate logic

As a follow up to #605, this updates the docker.sh output to better
reflect what the docker build is doing.
I also took the time to combine the logic for the docker build test
logic and the docker build release logic (determined by the presence
of CIRCLE_TAG. This brings the added benefit of us building a docker
image on all archs that we would release to on PRs.
Updated buildx to reflect what is in use on most user's machines.

Tested the PR validation part, seems to work great: https://app.circleci.com/pipelines/github/getoutreach/discovery/685/workflows/49a79f7a-fe7f-418d-b221-22e501a351c1/jobs/2321


Video:
https://github.com/epam/ketcher/assets/14859362/6f0ac88c-732e-4cc2-8b28-7b5a161c7dfe
Expected behavior
Merging between macro and micro entities should be ingored.

Manual tests added to the table.

Verified.


compiler crashes

Changes to tuple coercion has caused compiler crashes in the test runner and the standalone runner. A workaround for the test runner is to use std.meta.ArgsTuple, but no workaround for the standalone runner has been figured out yet.
Upstream issue: https://github.com/ziglang/zig/issues/16874

This has been resolved upstream.


Extensive use of "strcmp"

It is quiet noticeable that strcmp is used extensively (it is not only the tcmalloc).
In comparison of strcmp use between the memory-allocators,
for the comparison, a count of all binaries that have strcmp in the assembly instructions:
objdump -D /opt/swcdb/{bin/*,lib/libswcdb*.so} | grep "strcmp" -c:

tcmalloc_minimal:    1,227,568
tcmalloc:                     515,979
glicmalloc:                1,673,994
jemalloc:                      492,417

While without malloc the (SWC-DB as example) source includes only specific use count (a case of 76 for all Libraries).
As tcmalloc is a malloc-function and not a kind of CLI(NLP)-match or a full-text search library, It is surprising and most likely it is a performance sensitive subject. Considering a static-built excl. libc the executable-build size is 8,751,704 swcdbRanger and the strcmp must be playing a big role.

with some deeper-checking, by replacing all strcmp in tcmalloc src: (https://github.com/gperftools/gperftools/search?q=strcmp)
tcmalloc.cc base/logging.h stacktrace.cc heap-checker.cc base/elf_mem_image.cc debugallocation.cc
to an inline-ed _str_cmp (https://github.com/kashirin-alex/swc-db/blob/cf365d14e33cd6e7944d54d1b78b92797b446be8/src/cc/include/swcdb/core/Comparators_basic.h#L129)
The resulting use cases count of strcmp is not from tcmalloc source with just a slight~-change from 1,229,868 to 1,228,431 (for 7 executables and 26 libraries)


Console spam

I just updated to latest versions of thermal expansion mods on my server and everything seems to be working fine, but the console keeps spamming this:
23.02 07:55:16 [Server] Server thread/WARN [EnderIO]: NetworkPowerManager: Exception thrown when updating power network java.lang.NullPointerException
23.02 07:55:16 [Server] Server thread/WARN [EnderIO]: NetworkPowerManager: Exception thrown when updating power network java.lang.NullPointerException
23.02 07:55:16 [Server] Server thread/WARN [EnderIO]: NetworkPowerManager: Exception thrown when updating power network java.lang.NullPointerException
That is just three lines, but it seems to happen every tick. So, it is dozens of times a second with the same message. I would rather not pull out all the conduits I placed to figure out the problem. I am using several tesseracts transmitting power and items. The logistic pipes do not seem to be sending power to other pipes through the tesseracts too. It may be related. Probably a change in how power is sent.

I tracked down the issue to a logistic pipe RF provider the energy conduit was attached. The console spawn stopped when I removed it. It only starts if the conduit is near the block. Happens even when energy conduit is disabled next to the RF provider. I will open up an issue on Logistic Pipes issue tracker.


Change backbone used in efficient finetuning tutorial to FLAN-T5

Issue #, if available:
Description of changes:
FLAN-T5 was released by Google. The model has been pretrained on a wide collection of tasks, and is performing very well on downstream applications. In this PR, we are adding FLAN-T5 in the test case of efficient finetuning and also change the backbone in our efficient finetuning tutorial as FLAN-T5.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@zhiqiangdon @cheungdaven @suzhoum  We may need to benchmark the performance of FLAN-T5 in NER / Matching / Classification / Regression tasks. It seems to outperform DeBERTa.


Add column "mentees" for each person

Implemented by https://github.com/illyz/serlo-highrise-report/commit/dd2c2c6e106f71f74203a9d4769824501aa6eb79


OLS-934: Bump-up nltk to version 3.9b1

Description
Bump-up nltk to version 3.9b1
Fixes issue introduced by https://github.com/nltk/nltk/issues/3301
Type of change

[ ] Refactor
[ ] New feature
[ ] Bug fix
[x] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library
[ ] Bump-up library or tool used for development (does not change the final image)

Related Tickets & Documents

Related Issue #OLS-934

Hi @tisnik Do you know when there might be a full 3.9.1 release (or similar)?

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 94.68%. Comparing base (5da37ca) to head (2bda449).
Report is 33 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1422      +/-   ##
==========================================
+ Coverage   92.32%   94.68%   +2.35%
==========================================
  Files          58       58
  Lines        2503     2503
==========================================
+ Hits         2311     2370      +59
+ Misses        192      133      -59

see 6 files with indirect coverage changes

Hi @tisnik Do you know when there might be a full 3.9.1 release (or similar)?

according to this thread https://github.com/nltk/nltk/issues/3301 it will be 3.9.3 (3.9.2 was deleted), but no ETA

Hi @tisnik Do you know when there might be a full 3.9.1 release (or similar)?

according to this thread nltk/nltk#3301 it will be 3.9.3 (3.9.2 was deleted), but no ETA

thanks

Hi @tisnik Do you know when there might be a full 3.9.1 release (or similar)?

according to this thread nltk/nltk#3301 it will be 3.9.3 (3.9.2 was deleted), but no ETA

thanks

are you waiting for the new version? We had to bump-up to anything else than 3.9.1 because it has CVE vulnerability recorded and it won't pass our CI checks ;)

Hi @tisnik Do you know when there might be a full 3.9.1 release (or similar)?

according to this thread nltk/nltk#3301 it will be 3.9.3 (3.9.2 was deleted), but no ETA

thanks

are you waiting for the new version? We had to bump-up to anything else than 3.9.1 because it has CVE vulnerability recorded and it won't pass our CI checks ;)

@tisnik Yes, we are waiting for the new version. As far as I understand 3.8.2 was the version that fixed the vulnerability associated with 3.81, and 3.8.2 is the latest version that had been released (but was later deleted). Now you are referring to recorded vulnerability in 3.9.1 (rather than 3.8.1). Please let me know if there is a gap in my knowledge or understanding of this situation. Thank you.

/approve

/lgtm

/override "Red Hat Konflux / ols-e2e-tests-rosa / lightspeed-service"
/override "Red Hat Konflux / ols-enterprise-contract / lightspeed-service"


Spawn blog post

Do not merge.
rendered
Should we make this a standalone blog post or include it in the alpha 3 announcement? (Let's not rush the release of alpha 3, though)

i think we should have one blog post, with both the Compat stuff and the spawn! macros. this by itself feels a little light

Alright, then I have to get multi author posts working ^^'

I've updated the blog post. We can now either include @tinaun's upcoming compatibility layer blog post in this post or we can publish it as a standalone post.
@Nemo157 @cramertj please review the newly added sections


Break generation out into separate lib

I'd like to see the code base broken up into two pieces:

lower level generation lib
cli app that takes a python class path and returns the flattened output through means (html, sql, etc)
cli app (for ccbv.co.uk) that looks at CBVs specifically and updates the db
web app reading from the db

The new flow for updating ccbv.co.uk would use the ccbv specific script to generate a docset for a given django version (number or path) and update the db. The web app then doesn't need to restart for docset updates/additions. e.g.
<ccbv-script> [1.5|[-p|--path]path/to/a/django]

This ccbv-script removes the pain of needing to update the web app's django version for each version of docs it hosts.
The CLI app would be a more generic implementation of the ccbv-script that takes the python path to a class and can output some SQL or HTML. My use case is - I have a class, I want the ccbv style html output for it.
I hope that this could be taken further to generating API style sphinx docs, I'm looking at you Django forms.

@ghickman, any plans on making this happen?

@alizain – the plan is still there, the new work is on static-pages-requiem but I got stalled looking into a nice way to build the current home page and the menu (since they both deal with multiple versions).
I don't have any spare time to work on this atm but @meshy and I hope to plan a weekend to push it through eventually.  Unfortunately I'm very tied up with my startup and a newborn right now.

There are some great ideas in here that we should (and intend to) carry forward, but for the moment, given this has stalled, I'm going to close this PR. Maybe one day it will live again :)


php 5.6 on Centos 7.1.1503

I'm trying to install php 5.6 on Centos 7.1.1503 by adding manage_repos => true.
It ends with error:
Error: Execution of '/usr/bin/yum -d 0 -e 0 -y install php-common' returned 1: Error: Package: php-pecl-zip-1.13.1-1.el7.remi.5.6.x86_64 (remi-php56)
           Requires: libzip.so.4()(64bit)
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest
Error: /Stage[main]/Php::Packages/Package[php-common]/ensure: change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y install php-common' returned 1: Error: Package: php-pecl-zip-1.13.1-1.el7.remi.5.6.x86_64 (remi-php56)
           Requires: libzip.so.4()(64bit)
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest
Error: Execution of '/usr/bin/yum -d 0 -e 0 -y install php-cli' returned 1: Error: Package: php-pecl-zip-1.13.1-1.el7.remi.5.6.x86_64 (remi-php56)
           Requires: libzip.so.4()(64bit)
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest
Error: /Stage[main]/Php::Packages/Package[php-cli]/ensure: change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y install php-cli' returned 1: Error: Package: php-pecl-zip-1.13.1-1.el7.remi.5.6.x86_64 (remi-php56)
           Requires: libzip.so.4()(64bit)
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

Solution for this error is to add remi or remi-safe repository to manifests/repo/redhat.pp:
contain "::yum::repo::remi"

or
yum::managed_yumrepo { 'remi-safe':
    descr         => 'Les RPM de remi pour Enterpise Linux $releasever - $basearch - PHP 5.6',
    mirrorlist    => 'http://rpms.famillecollet.com/enterprise/$releasever/safe/mirror',
    enabled       => 1,
    gpgcheck      => 1,
    gpgkey        => 'file:///etc/pki/rpm-gpg/RPM-GPG-KEY-remi',
    gpgkey_source => 'puppet:///modules/yum/rpm-gpg/RPM-GPG-KEY-remi',
    priority      => 1,
  }

Can you add one of these solutions to module?

After reading http://blog.remirepo.net/pages/English-FAQ#safe as a non-RedHat user, I would rather go with remi-safe. Given that remi is already available in the yum module, we should for the sake of compatibility go with including ::yum::repo::remi to prevent users from adding the remi-safe repo multiple times or run into duplicated resources errors.
Will do before 4.0.0. Should be released later this week.

I am having this issue as well.  I vote for:
contain '::yum::repo::remi'

Shall I submit a pull request or is someone else doing it?

@edestecd I wanted to do it, but haven't gotten around lately. Please do! :)

I submitted a PR just now. Works for me. https://github.com/mayflower/puppet-php/pull/148

Awesome!

Fixed by #148.


Failing to echo special characters like "&"

I came across this error when trying to download an anime with the "&" character in the title.
Succesfully Downloaded File to 'C:\Users\mikah\Downloads\Love Chunibyo Other Delusions\Love, Chunibyo & Other Delusions - S1E1.mp4'
2024-10-31 18:12:57 - CRITICAL - execute_command - Command 'cmd /c echo Downloading to 'C:\Users\mikah\Downloads\Love Chunibyo Other Delusions\Love, Chunibyo & Other Delusions - S1E1.mp4'' returned non-zero exit status 1.

Hi Mika,
thanks for telling, yes that definitely needs to be fixed by sanitising the string before echoing it out.

After some further analysis i figured out that the error is coming from the spaces in the directory name
So, "Love, Chunibyo % Other Delusions" is invalid.
Now that i mention, it would be a good idea to let the user specify the output directory including the directory where the final mp4 s end up

The output folder should be named Love Chunibyo Other Delusions without any invalid characters anyways.
I'm not able to test if adding "" around the filename would fix the echo issue.
I’ll also add an option to select the final output directory. Thanks for the suggestion!

Could you try running it again using the latest commit?

I’ll test this on Windows tomorrow to see if it works.
It already does on macOS and likely Linux.

Works on my end with the newest commit!


No tasks from celery-php

PHP (https://github.com/gjedeer/celery-php):
const QUEUE_NAME = 'tasks';
$this->queue = new Celery(
		    $host,
            null,
            $password,
            '0',
            self::QUEUE_NAME,
            'celery',
            $port,
            'redis',
            true
        );
...
$asyncResult = $this->queue->PostTask('sample', ['foo'], true);
$queuer->postTask('sample', ['foo']);

In go:
func buildClient(host string, port int, password string, workers int) (*celery.CeleryClient, error) {
	queueBroker := celery.NewRedisCeleryBroker(fmt.Sprintf("redis://:%s@%s:%d/0", password, host, port))
	queueBackend := celery.NewRedisCeleryBackend(fmt.Sprintf("redis://:%s@%s:%d/0", password, host, port))

	client, err := celery.NewCeleryClient(queueBroker, queueBackend, workers)
	if err != nil {
		return nil, err
	}

	return client, nil
}

client, err := buildClient(queueHost, queuePort, queuePass, workers)
client.Register('sample' sampleTask);

However, the go client never sees the tasks submitted.
In Redis in debug logging, I see:
mq_1_9a03f7d641e2 | 1:M 21 Nov 10:45:26.140 - Accepted <IP_ADDRESS>:58794
mq_1_9a03f7d641e2 | 1:M 21 Nov 10:45:26.141 - Client closed connection
mq_1_9a03f7d641e2 | 1:M 21 Nov 10:45:26.803 - DB 0: 2 keys (0 volatile) in 4 slots HT.
mq_1_9a03f7d641e2 | 1:M 21 Nov 10:45:26.804 - 0 clients connected (0 slaves), 846196 bytes in use
mq_1_9a03f7d641e2 | 1:M 21 Nov 10:45:31.255 - Accepted <IP_ADDRESS>:58802
mq_1_9a03f7d641e2 | 1:M 21 Nov 10:45:31.257 - Client closed connection
mq_1_9a03f7d641e2 | 1:M 21 Nov 10:45:31.817 - DB 0: 2 keys (0 volatile) in 4 slots HT.
mq_1_9a03f7d641e2 | 1:M 21 Nov 10:45:31.817 - 0 clients connected (0 slaves), 846196 bytes in use
mq_1_9a03f7d641e2 | 1:M 21 Nov 10:45:36.382 - Accepted <IP_ADDRESS>:58810
mq_1_9a03f7d641e2 | 1:M 21 Nov 10:45:36.383 - Client closed connection
mq_1_9a03f7d641e2 | 1:M 21 Nov 10:45:36.830 - DB 0: 2 keys (0 volatile) in 4 slots HT.
mq_1_9a03f7d641e2 | 1:M 21 Nov 10:45:36.830 - 0 clients connected (0 slaves), 846196 bytes in use
mq_1_9a03f7d641e2 | 1:M 21 Nov 10:45:41.490 - Accepted <IP_ADDRESS>:58818
mq_1_9a03f7d641e2 | 1:M 21 Nov 10:45:41.491 - Client closed connection
mq_1_9a03f7d641e2 | 1:M 21 Nov 10:45:41.841 - DB 0: 2 keys (0 volatile) in 4 slots HT.
mq_1_9a03f7d641e2 | 1:M 21 Nov 10:45:41.841 - 0 clients connected (0 slaves), 846196 bytes in use

Anything im missing?
In redis;
<IP_ADDRESS>:6379> blpop celery 1
1) "celery"
2) "{\"body\":\"eyJpZCI6InBocF81YmY1NzYzNzQ3Yzc3OC4zODY3MDc0NyIsInRhc2siOiJzYW1wbGUiLCJhcmdzIjpbImZvbyJdLCJrd2FyZ3MiOnt9fQ==\",\"headers\":{},\"content-type\":\"application\\/json\",\"content-encoding\":\"binary\",\"properties\":{\"body_encoding\":\"base64\",\"reply_to\":\"php_5bf5763747c778.38670747\",\"delivery_info\":{\"priority\":0,\"routing_key\":\"celery\",\"exchange\":\"celery\"},\"delivery_mode\":2,\"delivery_tag\":\"php_5bf5763747c778.38670747\"}}"

Edit: seems to be incompatible.


Inconsistent layout from one page to another

Hello,
When updating to 0.10.1 I have noticed that the layout is inconsistent from one page to another. It may be related to #904
0.10.1:
Screencast from 31-08-2022 10:30:09.webm
0.9.0:
Screencast from 31-08-2022 10:41:39.webm
In my opinion previous layout was cleaner than the new one.
What do you think ?

the left sidebar is disappearing on some pages because the search box is no longer there (and on 0.9.0 some of your pages have nothing in the left sidebar except the search box).  You can revert that change if you want (see docs here).
The main content is shifting sideways sometimes I think because of #861 (?) and is already reported in #904 (by you).
I'll close because the first issue (left-sidebar hide-when-empty behavior) is expected and there's a config option to bring back the search box if you want it; and the second issue (main content shifting around) is already reported in #904.  Feel free to re-open if you think I've missed something here.

Thanks a lot for your help !


Corrected impropoer use of .base on quantities objects

This is a follow up of #198 in the spike_train_generation module.

Hello @mdenker! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file elephant/spike_train_generation.py:

Line 167:80: E501 line too long (83 > 79 characters)
Line 244:80: E501 line too long (83 > 79 characters)

Coverage decreased (-0.02%) to 87.275% when pulling c3f2f19d4f957b59c46964c4aa56bbd3a8a2c645 on INM-6:fix/generation_base into 941518a676609b59a2ab50728c90927b01742f0f on NeuralEnsemble:master.

Coverage decreased (-0.02%) to 87.275% when pulling c3f2f19d4f957b59c46964c4aa56bbd3a8a2c645 on INM-6:fix/generation_base into 941518a676609b59a2ab50728c90927b01742f0f on NeuralEnsemble:master.

Coverage decreased (-0.02%) to 87.275% when pulling c3f2f19d4f957b59c46964c4aa56bbd3a8a2c645 on INM-6:fix/generation_base into 941518a676609b59a2ab50728c90927b01742f0f on NeuralEnsemble:master.

Coverage decreased (-0.02%) to 87.275% when pulling c3f2f19d4f957b59c46964c4aa56bbd3a8a2c645 on INM-6:fix/generation_base into 941518a676609b59a2ab50728c90927b01742f0f on NeuralEnsemble:master.

Cross-checked by @PaulinaDabrowska


Ray has died with a red screen on my Linux Mint - Something went wrong here: Reload Ray to try again.

Describe the bug
Ray was working fine for a few weeks. Then I noticed that an error was repeating, something like:
Missing } and then I had to click on ErrorHandler which didn't show the real problem.
I don't recall the precise message but I can tell you it was repeating and I can't use Ray anymore at all.
Versions
Bit of a mystery here, as I click on Ray-1.13.0.AppImage but Menu/About says 1.12.0

spatie/ray package version: 1.20.0
spatie/laravel-ray package version (if applicable): 1.13.0

PHP version: 7.4.15
Laravel version: 8.29.0
To Reproduce
Steps to reproduce the behavior:

Start Ray
A red screen appears, "Something went wrong here. Reload Ray to try again."
Click Reload Ray. Nothing happens.
Click View menu, New Blank Screen and Clear History. Nothing happens.

Expected behavior
Ray should work and clearing screens should "reset" it.
Screenshots

Desktop (please complete the following information):

OS: Linux Mint
Version 20 Ulyana

Additional context
If Ray has some kind of buffer that stores messaging, my belief is it was overwhelmed by the constant repeats of "Missing }" and eventually just crashed due to too much data. One would expect "New Blank Screen..." fixes the problem, but perhaps because it's so overwhelmed it's now just fubar.
I love Ray so please let Ray love me back <3

Could you create a minimal app to recreate the issue your are experiencing? This would help us a lot debugging and fixing this issue.

Ok I did that, started a new project and it's working. I'm going to close this issue for now until I can figure out what's wrong with my project. Perhaps vendor files are broken I'm not sure but will come back if there is still an issue.


use drive_id on onedrive addon

https://github.com/yacchin1205/RDM2-osf.io/pull/77

https://github.com/RCOSDP/RDM-waterbutler/commit/0492845307cce54c00d974cbd6949fa23ce25a8c


Resolve photo dome issues

Photo dome example has the following issues:

Image is flipped
Default camera view is wrong
Deallocation of dangling mesh pointers in camera destructor

Resolved flipped image by commit fbb108e0872b3c91429ac4eb0aec73d7fc98deed
Other issue already resolved.


How to run a Bot in a loop

Hi,
I have triggered the bot, But it executed and it returned by not performing any thing.  Do i need to run the bot in a loop ? To continuous check in the market for trading ?
Here is what i am getting.

do you have "stats: 1 in your config by any chance? try removing that line and run the bot again. I have the same issue when run-in with stats enabled in the config.

Yes. It worked than you
Get Outlook for iOShttps://aka.ms/o0ukef

From: Matt Warrillow @.>
Sent: Sunday, November 21, 2021 5:49:43 AM
To: whittlem/pycryptobot @.>
Cc: esaravanakumar89 @.>; Author @.>
Subject: Re: [whittlem/pycryptobot] How to run a Bot in a loop (Issue #561)
do you have "stats: 1 in your config by any chance? try removing that line and run the bot again. I have the same issue when run-in with stats enabled in the config.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/whittlem/pycryptobot/issues/561#issuecomment-974801792, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABOFJ4YPIUE3ZCL7FA6UNDTUNDMFPANCNFSM5HUIKWMA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Turtlebot3 + ROS Melodic + Ubuntu 18.04 for remote computer

Is there any known reason to stick to Ubuntu 16.04 and ROS Kinetic as the emanual says?
Or is Ubuntu 18.04 (on remote) + ROS Melodic fully supported for the TB3 software provided here?
What is the recommendation?
Thanks!

Hi,
TB3 fully support ROS melodic, but some dependency packages do not. So If you use ROS melodic, you have to manually compile these packages. (ex. gmapping)
check the following list.
https://index.ros.org/packages/#melodic
Regards,
Kayman

Thanks. Can you give (or link to) instructions on how to “correctly” manually compile the packages? Thanks,
Pito Salas
Brandeis Computer Science
Volen 134

On May 13, 2019, at 9:15 PM, Kayman<EMAIL_ADDRESS>wrote:
Hi,
TB3 fully support ROS melodic, but some dependency packages do not. So If you use ROS melodic, you have to manually compile these packages. (ex. gmapping)
check the following list.
https://index.ros.org/packages/#melodic
Regards,
Kayman
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

This is ros wiki for building the packages : LINK

Download the source to the catkin workspace
The location of the source file can be found on the ros wiki.
Build a package using catkin_make

In case of gmapping, it may not work in melodic due to the development stopped in the hydro version.
Regards,
Kayman

@pitosalas What is your reason of choosing Melodic and 18.04?

I would like to move to 18.04. I am trying to determine if I should do that. Kinetic is 16.04 only, so to go to 18.04 I need to use melodic.
Pito Salas
Brandeis Computer Science
Volen 134

On May 27, 2019, at 9:50 PM, Yoshimaru Tanaka<EMAIL_ADDRESS>wrote:
@pitosalas https://github.com/pitosalas What is your reason of choosing Melodic and 18.04?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/ROBOTIS-GIT/turtlebot3/issues/423?email_source=notifications&email_token=AAAK5CM2Y6XMESSGBBJGB63PXSTYZA5CNFSM4HMO4GT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWK4QBA#issuecomment-496355332, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAK5CKMJ4HKC5SK4ZTKM7DPXSTYZANCNFSM4HMO4GTQ.

This issue will be closed since there were no actions for a while. You can reopen this issue to show this issue to the users whenever. Thanks.

can u give me the link to install packages of turtlebot3 on ros melodic??

@amna786-rajpoot
There is no instruction for TB3 Melodic but you can refer to this link. You can see the following three points that you need to note.

Install Ubuntu 18.04 instead of Ubuntu 16.04
Install ROS Melodic instead of Kinetic (you can download a shell script file for melodic install from our eManual by using wget)
Install relevant packages for melodic instead of kinetic
(e.g., 'sudo apt-get install ros-melodic-ros-controllers' instead of 'sudo apt-get install ros-kinetic-ros-controllers')
If there is no existing binary file, you will need to find source file for it and catkin_make with other packages as mentioned in the early conversation by pitosalas and Kayman in this thread.

Let us know if you have any other questions,
Ryan

I have tried doing that I have installed all the packages in Melodic but somehow TB3 doesn't seem to work on Melodic. In the coming future will TB3 be made compatible with ROS Melodic?

@kjyothiswaroop I have the same problem. Turtlebot3 doesn't work with Ubuntu 18 and ros melodic. What should we do? Can anyone help?

@kjyothiswaroop @RahulSTrivedi
Please open a new issue for the question.
Thanks,
Ryan


First edition of proposal for dns trait

This PR provides a simple DNS trait, similar to that provided by both lwip and the Berkeley sockets API, consisting of a simple gethostbyname function that resolves a hostname to the first ip address given by A or AAAA DNS record, depending on the requested addr_type, and a gethostbyaddr to resolve the hostname given an ip address. The later function has the addr_type encoded in the given IpAddr input.
This is a proposal for a first edition. It will not cover the full DNS, but it is equivalent of both lwip and the Berkeley sockets API, as well as the functionality given by std::net::ToSocketAddrs
Fixes #8

LGTM!


Suggestions do not show up in Simulator

Inline suggestions work fine, but the dropdown does not work in the simulator.
Attached is a screenshot of the example app running on Simulator (iPhone 6 iOS 10.3)

It's because the keyboard is hidden. Just press Cmd+k in order to force it to appear and the dropdown will show.


not opening youtube.com and some other sites

Describe the bug
its opening websites like github/google/... but not youtube and some other websites
To Reproduce
Steps to reproduce the behavior:

run the gt docker container  using docker run -d --restart unless-stopped -p "<IP_ADDRESS>:1081":8000 --name gt sadeghhayeri/green-tunnel
set the https and http proxy setting to http > <IP_ADDRESS> > 1081
open google.com > ok / open youtube.com > An error occurred during a connection to www.youtube.com. PR_END_OF_FILE_ERROR

Expected behavior
it should open youtube.com
Screenshots

Desktop (please complete the following information):

OS:ubuntu 20
Browser firefox
Version latest

and two question  : do i need to enable the secure dns setting in my browser?
im setting the green tunnel as an http proxy for http and https connections, is it correct?.(google and other sites work just not youtube and maybe something else ) :

Same here.
It seems it's not working anymore.

Same here.
GreenTunnel installed in Docker container, tested with Firefox and Chromium on Windows.


HelpWindow: Gibberish text (Mac only)

Tested on java version "1.8.0_121" and Mac OS version "10.12.4"
It turns out to be a bug in JavaFx WebView on Mac, it tries to load some fonts locally and is disallowed (explained in this StackOveflow answer). Also as pointed out in the related open JDK issue, this is fixed in Java 9 early access version (9-ea+148)
Some possible walk-arounds:

change GitHub Pages theme. For example, MERLOT THEME works.
programatically insert another <style> tag into the WebView html to change the font used.
revert this PR

There is still possibility that if we download open sans font as a .tff file and add to the app, then load it in JavaFX at runtime, it will display the font correctly, but this approach is relatively more complicated and not yet tried out.

I don't think downloading the font helps as the WebView cannot be styled by our CSS, rather the webpage's CSS

@MightyCupcakes I agree it maybe doesn't help. But actually we can style WebView's content using our CSS, i.e. we can programatically change the font used in the html by adding some additional style tag.

Any other themes that work?

Any other themes that work?

Yes, actually out of the default 12 themes provided in GitHub Pages settings, only "Cayman" doesn't work. The rest are all fine.

@chao1995 We chose Cayman because it gives a clean dev/user guide pdf file that can be used for CS2101.
Can you check if semester fork is affected? If not, we can leave this alone until we move to asciidoc.

Can you check if semester fork is affected?

I cloned the repo, confirmed that the fork is affected.

I cloned the repo, confirmed that the fork is affected.

I see. In that case I'll inform CS2103 teaching team that students can fix it by changing the theme.

Does this persist even after converting to asciidocs?

@damithc Just updated to the latest commit, but now I get a 404 due to this broken link: https://se-edu.github.io/addressbook-level4/docs/UserGuide.html.
The link should actually be https://se-edu.github.io/addressbook-level4/UserGuide.html (without the docs) @yamgent for your notice.
However, the gibberish text issue still persists.

The link should actually be https://se-edu.github.io/addressbook-level4/UserGuide.html (without the docs) @yamgent for your notice.

Thanks for the notice, will raise this issue if I still haven't fix the offline docs issue.

Apparently, this is fixed in JDK 9: https://bugs.openjdk.java.net/browse/JDK-8175802
Refer to the comments at the bottom of the page.

Could you possibly look at some other asciidoctor themes that uses a different font without it becoming gibberish?

Perhaps we should give this a try? I don't think we can upgrade to jdk 9.0 at this point.

BTW, does this affect all Mac users?

Perhaps we should give this a try? I don't think we can upgrade to jdk 9.0 at this point.

As @chao1995 mentioned, all other default themes for GitHub Pages work.

As @chao1995 mentioned, all other default themes for GitHub Pages work.

But we are using asciidoc, so we can't use the themes provided by GitHub, right?

Wait, the original issue was supposedly caused by a specific font in a specific GitHub pages theme. The asciidoc theme has the same font?

If I didn't read the bug report wrongly, it seems to be an issue of how JavaFx tries to load fonts without a proper family name, So it could be happening to groups of fonts, rather than it being the issue of a particular font.
Since now we have control of the css file, perhaps a Mac user can try and experiment around with the file to see which fonts won't cause that behaviour.

perhaps a Mac user can try and experiment around with the file to see which fonts won't cause that behaviour.

Paging @Zhiyuan-Amos

won't work on this unless someone guides me with css (i.e. just tell me which line to edit).

We'll get this issue again when we downgrade to JDK8.
Reopening so I don't forget.

Since now we have control of the css file, perhaps a Mac user can try and experiment around with the file to see which fonts won't cause that behaviour.

And yeah, we should workaround it by doing this.


Using Swagger/OpenAPI definitions

Now that API Gateway supports importing Swagger/OpenAPI definitions directly (see documentation), would it be possible to support the import API method in this custom CloudFormation resource? This would make the need to maintain all intermediate resources obsolete, if it would be possible to just add a Swagger definition to a CloudFormation property directly.

I will definitely look into this and perhaps offer it as an alternative way
to write your API definitions.
On lör 9 apr. 2016 at 03:39, Will Jordan<EMAIL_ADDRESS>wrote:

Now that API Gateway supports importing Swagger/OpenAPI definitions
directly (see documentation
http://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-import-api.html),
would it be possible to support the import API method in this custom
CloudFormation resource? This would make the need to maintain all
intermediate resources obsolete, if it would be possible to just add a
Swagger definition to a CloudFormation property directly.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/carlnordenfelt/aws-api-gateway-for-cloudformation/issues/38

Added in version 1.5.0 with a couple of caveats. Check it out here: https://apigatewaycloudformation.bynordenfelt.com/#custom-ApiImport


Metaballs created in edit mode under a single object are not exported properly.

Regression Suite No. 3 fails because the metaballs are all within a single object, and the exporter doesn't inspect within to find them. It only exports and blends separate metaball objects in a meta-family.

It looks like we need to iterate through the bpy.data.metaballs collection, and each member's .elements collection, in order to export all meta elements used in the scene. We may just need to export these in a separate pass, skipping any meta objects found during the main object tree export loop.

I'm redoing the blob export code to fix this up. Going well, but not there yet.

nice.

I am still working on this. I got tripped up a bit, because meta elements nested under one object share a single parent, and therefore share a single parent transform.
Meta elements that are completely separate objects but share the same family name should also blend as one blobby, but each inherits a completely different parent transform.

I updated my repo to fix up the transforms.  There are still some minor scaling issues.

Also, particle-system emitted blobs have not been addressed.

Do you want me to look at the changes?  What are the scaling issues?  I can do particles as well.

The scaling issues are mainly to do with the Threshold of a MetaBall and Stiffness of a MetaElement not being properly mapped to the exported data. I couldn't figure out how to map these properties to RIS blobs.
Feel free to have a look, and also let me know if you're ok with how the other MetaBall code works. It was a challenging task, for sure.

With your latest pull request can we close this issue?

We can close it. There is a ton of stuff that could still be done with metaballs (segments, planes, subtraction, etc), those can be addressed later.

Thanks for doing the blobby particles code, works great!


Switch component. thumbColor and trackColor do not work.

🐛 Bug Report
Switch component. New options thumbColor and trackColor do not work.
To Reproduce
According to documentation I use trackColor and thumbColor
            <Switch
              value={true}
              trackColor={'green'}
              thumbColor={'gray'}
            />

This removes warnings but does nothing with colors.
Okay, when I put deprecated option onTintColor and thumbTintColor back:
            <Switch
              value={true}
              onTintColor={'green'}
              thumbTintColor={'gray'}
            />

there are warnings, but colors are changed.
Expected Behavior
I expect code works well according to the docs: https://facebook.github.io/react-native/docs/switch#thumbcolor
Code Example
            <Switch
              value={true}
              trackColor={'green'}
              thumbColor={'gray'}
            />

Environment
React Native Environment Info:
System:
OS: macOS 10.14.3
CPU: (8) x64 Intel(R) Core(TM) i7-3615QM CPU @ 2.30GHz
Memory: 2.66 GB / 12.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 11.2.0 - /usr/local/bin/node
Yarn: 1.12.3 - /usr/local/bin/yarn
npm: 6.4.1 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 11.4, macOS 10.13, tvOS 11.4, watchOS 4.3
Android SDK:
API Levels: 23, 25, 26, 27, 28
Build Tools: 23.0.1, 23.0.2, 25.0.2, 25.0.3, 26.0.2, 26.0.3, 27.0.0, 27.0.1, 27.0.3, 28.0.0, 28.0.2, 28.0.3
System Images: android-28 | Google APIs Intel x86 Atom
IDEs:
Android Studio: 3.2 AI-181.55<IP_ADDRESS>56338
Xcode: 9.4.1/9F2000 - /usr/bin/xcodebuild
npmPackages:
react: 16.6.3 => 16.6.3
react-native: 0.57.8 => 0.57.8
npmGlobalPackages:
react-native-cli: 2.0.1

Now it is getting more clear. I tried to npm install latest version of react-native. Then my application was not able to build and run at all!
But I bet it refers to some another react-native issue.
Updating react-native modules is common pain...

Can you clarify what your expected behavior is? It's not clear what exactly is not working as expected. Screenshots might help.

Track color takes an object, not a single color: https://facebook.github.io/react-native/docs/switch#trackcolor
Snack: https://snack.expo.io/@jkcooper/rn-issue-#23570---switch-track-color

Thanks @JKCooper2. Closing as working as expected.

Track color takes an object, not a single color: https://facebook.github.io/react-native/docs/switch#trackcolor
Snack: https://snack.expo.io/@jkcooper/rn-issue-#23570---switch-track-color

Thank you. It works!


Is firebase-analytics required when using firebase-auth?

Is there a dependency between the two?
I'm trying to minimize the amount of ref count (DEX-limit stuff). And currently I only wanna use the ´firebase-auth´, but it seems that it comes bundled with ´firebase-analytics´ which uses around 5k refs.
Is it safe to remove ´firebase-analytics´? My guess is not, but would like to confirm, and also make a wish for the decoupling of the two?

Yep Firebase Analytics is required by all Firebase components for the suite to work correctly.
To reduce the number of included methods you can export to Android Studio and enable proguard for the moment.   We currently have experimental proguard stripping support in https://github.com/googlesamples/unity-jar-resolver but unfortunately we're having some issues specifically with the Analytics AAR at the moment.
@johnb003 FYI

Thanks for the quick response! I've never used Proguard, does it apply to the whole project, or is it possible to use only for certain libs (like play services)?
Thanks again!

Yep proguard applies to your whole project.  See
https://developer.android.com/topic/performance/reduce-apk-size.html and
https://developer.android.com/studio/build/shrink-code.html
On Fri, Aug 18, 2017 at 3:31 AM, Whyser<EMAIL_ADDRESS>wrote:

Thanks for the quick response! I've never used Proguard, does it apply to
the whole project, or is it possible to use only for certain libs (like
play services)?
Thanks again!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/firebase/quickstart-unity/issues/103#issuecomment-323281728,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFw1RDu6Ti9rv_j_hFVT68OUZB14GmzEks5sZT3NgaJpZM4O6fz2
.

I thought as much, with all libs currently in the project it seems risky to try proguard:ing it. Thanks anyway, I'll have to stick with the Firebase REST API for now.


Skip default and swagger cache (task #2555)

Applicable only when in development, default and swagger cache have a duration of 2 seconds.
The implementation is identical to routing caching. Another solution is to completely disabling cache.

Codecov Report

Merging #725 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #725   +/-   ##
=========================================
  Coverage     35.58%   35.58%
  Complexity     1267     1267
=========================================
  Files           108      108
  Lines          4210     4210
=========================================
  Hits           1498     1498
  Misses         2712     2712

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 b8a1c7d...d744bc3. Read the comment docs.


Return a FlexVersion object instead of a String.

-This will allow a user to extract information from the version w/o needing to parse
-Gradle is smart enough to take an Object for a version so this will work as it calls toString
-Anything expecting an actual String will fail and need to change to have a toString()

@EXBreder
@atrocities

As per @EXBreder  and Richard's comments, I moved the string building logic into the object itself.  It's always going to be an integer, I just had kept the string that it was going.  Changed to be an int.


[Docs] 404 Link in Component API > Page

When clicking on "spread to the root element" on any Component API page it'll link to "https://material-ui-next.com/customization/api#spread" which is 404.
Here is a list of all pages with wrong links: https://github.com/callemall/material-ui/search?p=1&q="customization%2Fapi%23spread"&type=&utf8=✓

@Skaronator Good catch, thanks for raising!