Defined active record model's HABTM associations

It looks like the Neo4Apis::ActiveRecord:: model_importer method is able to handle has_one, has_many and belongs_to reflected associations, which in most cases will be able to handle most of the 1:M, M:1 or M:M (with intervening model that links the many to many related tables, ex: projects, researchers, advisors: a project has many advisors through researchers) relationships.
However for a direct M:M relationship, with no intervening model (departments, employees departments_employees for example), which model wise, can be defined with the has_and_belongs_to_many association within the Employee and Department models, will the relationship, translated into neo4j appropriately, even though it is not a handled association?

It's true!  I would definitely like to add HABTM associations.  If people do a table import then it will actually import these associations as nodes, but if they're importing from an existing ActiveRecord app then it won't.
I'm wondering if there should be an option to import tables with two foreign keys as relationships rather than nodes with two relationships and to put the key/values from that table into the relationship.  Maybe when importing models it should always do this for has_many :through and has_and_belongs_to_many.  What do you think?

I agree @cheerfulstoic and thanks for the prompt reply.
I think when importing AR models, it should, like you've mentioned, keep the defined association for has_many :through and has_and_belongs_to_many as relationships (or edges, is that the right term, still not familiar with neoj4 terminologies).
This will ensure that the referential integrity of the related models, when translated into neo4j land as model -> node, then, either the nodes are linked when foreign keys are matched, or dangling when M:M table doesn't have an entry to associate the models, or the  has many through relationship's through relationship is not defined, so that there isn't a 1:M relationship either. What is an edge for a M:M relationship like in neo4j land?
For straight table import, with no definitive relationship, will neo4j, allow you to define relationships to link the nodes, once tables are imported as nodes?

So neo4j's modeling is pretty simple.  There are nodes and relationships.  Both can have key/value pairs to store data.  Nodes can have 0 or more "labels" (like User, Post, Comment, etc...) while relationships are required to have just one "type" (like wrote_post or comments_on, etc...).  In neo4j terminology, relationships match the idea of "edges" in mathematical graph terminology.
So in neo4j, you can have 1:M and M:M, but they're modeled the same way: as relationships between nodes.  If nodes of a particular label always happen to have many nodes leading to one node, then that could be considered 1:M, but there's nothing stopping it from being M:M.  You might even say that all relationships in neo4j are M:M because relationships are a separate data store from nodes and they can always link any node to any other node.
So if you use the all_tables command in neo4apis-activerecord, it will read through your tables generate ActiveRecord models by looking for primary keys and for primary-key-like-columns.  The primary keys become neo4j indexes and the primary-key-like-columns get imported into neo4j, but they also get imported as relationships.  So if you have posts and comments tables where the comments table has a post_id, then the Comment nodes will also have post_id keys, but there will also be a relationship from Comment nodes to Post nodes with the relationship type post.
So, with that background, to make sure that I'm being clear in my proposal:
With both has_and_belongs_to_many and has_many :through you have in SQL a third M:M table.  The difference between them is that has_many :through has an ActiveRecord model in between because you need to do something more with them (store additional data, run validations/callbacks/whatever).
If a user of neo4apis-activerecord uses the all_tables command then obviously we don't know if they would have modeled a join table as has_and_belongs_to_many or  has_many :through, though normally people only use HABTM when they have a M:M table with a primary key and two foreign keys, and they use has_many :through when there are more columns than that.
Either way, though, I can imagine that a table with two foreign keys could naturally be modeled as a relationship because there is a connection between the two (although direction isn't usually clear).  Even if it's has_many :through, you can store data on the relationship and in the neo4j gem you can optionally model relationships with the Neo4j::ActiveRel module, which approximates a has_many :through association pretty well.
So the point of that was mainly to explain how neo4j works and how neo4apis-activerecord works, but it's also kind of helped my talk (or at least type) things out.  I think that there should be a command-line option to import tables with just a primary key and two foreign keys as relationships, but otherwise it just imports tables as nodes and creates relationships for any foreign key references.  When importing ActiveRecord, I think that all HABTM and HMT associations should be relationships.
What do you think?  I'd also like @subvertallchris 's opinion as well ;)

@cheerfulstoic thanks for explaining some of the neo4j basics.
I think having another option for neo4apis-activerecord to tell whether to import a table with 2 foreign keys, which acts as a join table, as relationships, makes sense. Without the option, it will just default to be imported as a node.

Just ran into this on the neo4j developer resources pages:
http://neo4j.com/developer/graph-db-vs-rdbms/#_data_model_transformation
Putting here for reference as I think it's very appropriate to the gem

FYI I just implemented HABTM in version 0.7.0!  It works if you already have it defined in your models.  Haven't yet played around with building in assumptions based on table structure when there are no models


Updated List of Contributors

Motivation and Context

This PR updates the list of contributors to include new contributors.
Your Changes

Description:
Added myself to doc/markus-contributors as my first PR was just merged into the master branch.
Type of change (select all that apply):

[x] Other (please specify):
Updating contributors list.

Testing

Testing does not appear to be necessary for this change.
Checklist

[x] I have performed a self-review of my own code.
[ ] I have verified that the pre-commit.ci checks have passed.
[ ] I have verified that the CI tests have passed.
[ ] I have reviewed the test coverage changes reported on Coveralls.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage remained the same at 91.562%

Files with Coverage Reduction
New Missed Lines
%

spec/models/course_spec.rb
3
99.21%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
36838

Relevant Lines:
39692

💛  - Coveralls


Problem in test_bscdfsl.py

while choosing the learning rates, the iterator of data_loader_val seems to stop at the last one after finish training with lr=0, so it's not able to train with lr=0.0001.
(I set the iter_num to 20 for experiment)

Hi @YingYuChen97 Sorry for late reply! I was on holidays.
This seems like this for loop is skipped, so loss is not computed, and therefore metric_logger.loss doesn't exist. You may need to check whether data_loader_val is correctly set up.


cmake: don't include syslog files if CONFIG_SYSLOG=n

Summary
don't include syslog files if CONFIG_SYSLOG=n
Impact
sync with make build system
Testing
local build

[Experimental Bot, please feedback here]
No, this PR does not fully meet the NuttX requirements. While it provides some information, it lacks crucial details.
Here's a breakdown of what's missing:

Summary:  While it states what is being changed, it doesn't explain why.  Is this a bug fix? A performance improvement?  What problem does it solve? It also lacks details on how the change is implemented.  Does it modify Kconfig files?  Makefile? Source code?  Specific file names should be mentioned.  Issue references are missing.

Impact: The provided information is too vague.  "Sync with make build system" doesn't explain the actual impact. Does this change affect any users?  Does it change build dependencies? Does it affect any specific architectures or boards? Does it require documentation updates?  The security, compatibility, and "anything else" sections are completely omitted.

Testing:  The testing information is insufficient. It mentions "local build," but provides no details about the host or target environment.  Specific OS, architecture, board, and configuration should be listed. Critically, it's missing the "before" and "after" testing logs which are crucial to demonstrating the change's effect.

Example of how the PR description could be improved:
Summary
This PR fixes a build issue where syslog files were being included in the build even when CONFIG_SYSLOG=n. This was causing unnecessary increases in the final binary size.  The change modifies the Makefile in fs/syslog to conditionally include the syslog source files based on the CONFIG_SYSLOG Kconfig option.
Impact

Is new feature added? NO
Is existing feature changed? YES - Build system logic for syslog.
Impact on user (will user need to adapt to change)? NO
Impact on build (will build process change)? YES - Syslog files will no longer be included if CONFIG_SYSLOG=n, resulting in smaller binary sizes.
Impact on hardware (will arch(s) / board(s) / driver(s) change)? NO
Impact on documentation (is update required / provided)? NO
Impact on security (any sort of implications)? NO
Impact on compatibility (backward/forward/interoperability)? NO
Anything else to consider? NO

Testing
I confirm that changes are verified on local setup and works as intended:

Build Host(s): Linux (Ubuntu 20.04), x86_64, GCC 9.4.0
Target(s): sim:qemu-x86_64

Testing logs before change:
make clean
make menuconfig  # Set CONFIG_SYSLOG=n
make
size nuttx
   text    data     bss     dec     hex filename
  12345   67890  12345  203690   31c7a nuttx  <-- Large binary size

Testing logs after change:
make clean
make menuconfig  # Set CONFIG_SYSLOG=n
make
size nuttx
   text    data     bss     dec     hex filename
  10000   50000  10000  160000   27100 nuttx  <-- Reduced binary size

By providing more context and specific details, the PR becomes much clearer and easier to review. Remember to always include relevant issue numbers as well.


bug report

I found that line 126 of  scad.py use action before action has been defined.

Good catch! I have fixed it https://github.com/twni2016/pomdp-baselines/commit/4909f65bfc934ab13214053cb4cc183d95a720c5


I can't login

Describe the bug
I can't login
To Reproduce
instaloader --login xxx -p xxx
i see a link. i click on it and sign in to IG in my browser. i run the login command again and get the same link.
Expected behavior
log me in after the second time i enter the --login command
Error messages and tracebacks
Instaloader version
4.9
Additional context
ubuntu on chrome in incognito mode

Your description lacks of an error message/output. the link you see is maybe a challenge link.
Logging in with browser does not say that you can then login with instaloader afterwards.
Maybe you try this: https://instaloader.github.io/troubleshooting.html#login-error

there are no errors or output beyond what I wrote. I'll look into your link. thank you!


Incorrect behaviour

Extractor gets MessageWriteInterface and MessageReadInterface, but they are available only in CategoryMessage context.
Whole application can have multiple messages sources, using only one of them is incorrect.

Do you mean you want to be able to write extracted messages into multiple sources at once?

Not really. I would say to have writer or reader as a service is wrong design. They are needed only for polymorphism now.
This extractor should work by the following rules:

Gets path where it will find messages
Category (messages domain) that it will append.

For example:
./yii extract views/module1 module1 it will search any new messages from the directory views/module1/* and will append to translations file resources/messages/en/module1.php, if that file configured for module1 category.

Well, it does more than that:

It reads all the messages from the source code.
It reads all the message translations from message source (it may be DB or something else, not necessary files).
It checks if all the current message translations have corresponding messages in the message source. If not, it may either make these translations as deprecated or remove them.
It checks if all the message from the source code have translations in the message source. If not, an empty translation is added.

These actions are time-tested with Yii 2. The approach worked really well.

It checks if all the message from the source code have translations in the message source.

Yes, but it should check all sources, but only "main".


CustomFields to UserDefinedFields

See CMs comments on forum post https://community.superoffice.com/en/developer/forum/rooms/topic/superoffice-product-api-group/customer-service/sth-changed-in-edsetoutputvalue-for-udef-of-company-after-new-released-so-10/
CustomFields > UserDefinedFields is worth mentioning anywhere we talk about UserDefinedFields.
This means that you need to create sibling issues and branches in the other repos when picking this issue.

Revised link on new community

Note: It's the other way around, UserDefinedFields usage should be replaced with CustomFields, for at least entity contact and person for now. This because with SuperOffice V10 & configurable screens the CS extra fields are now also available, but only in the CustomFields property.

Thanks for pointing this out, @acdavidh. We're moving this issue to the new monorepo now.


Merge variant values in deduplication

Add an option to the deduplication filter to merge variant values into a list instead of just choosing the first one.
May require changing the basic operation of the filter.

This and #197 are closely related.


[BUG] API freezes when input body payload is greater than 100kb

Information

Version: 5.45
I have following handlers in app in Server.ts:

$beforeRoutesInit():` void {
    this.app
      .use(cors())
      .use(cookieParser())
      .use(compressExceptCached())
      .use(methodOverride())
      .use(bodyParser.json())
      .use(
        bodyParser.urlencoded({
          extended: true
        })
      );
  }

When API payload of size > 100kb is received, there is no exception thrown and API is just stuck.
We can solve this by using limit in bodyParser.json as:
bodyParser.json({
    limit: "10mb"
  });

but the point is, API should throw some error.

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

v6.75.11
GitHub release

Your semantic-release bot :package::rocket:


test: use mock.Anything to simplify tests

Signed-off-by: Boris Glimcher<EMAIL_ADDRESS>

simplifying tests like this will cause them to be more weak, so deciding to abandon this change


Support for Developer edition environment?

testing you plugin in free developer edition. Looks like the plugin can only connect with sandbox and prod. Any plan on adding this?

You should be able to use the production setting for developer sandboxes. They use the https://login.salesforce.com base name as well.
Thanks,
Anthony

From: niristotle okram <notifications<EMAIL_ADDRESS>Sent: Friday, June 9, 2017 1:23 PM
Subject: [jenkinsci/salesforce-migration-assistant-plugin] Support for Developer edition environment? (#23)
To: jenkinsci/salesforce-migration-assistant-plugin <salesforce-migration-assistant-plugin<EMAIL_ADDRESS>Cc: Subscribed <subscribed<EMAIL_ADDRESS>testing you plugin in free developer edition. Looks like the plugin can only connect with sandbox and prod. Any plan on adding this?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/jenkinsci/salesforce-migration-assistant-plugin/issues/23, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AHCJ0lvB9uHWm4bHUcxOE8Z_cLJawxSGks5sCamsgaJpZM4N1y6M.


Performance test fixes

Out of band from what we're doing, but while I was going through the practice exercise of reorganizing our metaPureJS repo, I noticed that there were some defects in the performance/benchmark test suites. This branch fixes them:

The native, RPC Broker socket-based test timing numbers were off, due to the asynchronous nature of the runs and the fact that the stopwatch events weren't happening as close to the wire as possible.
The RPCs need to be run in strict serial order to keep the tests consistent, which they were not. This was fixed by using the async.eachSerial function to ensure that only one RPC was run at a time.
The raw RPC message string translator function was broken, caused by an incorrect argument string length being passed in. Fixed this as well.

Here's a sample report with much better looking numbers: https://gist.github.com/mfuroyama/b2cf5ed50fad61912bfced54e08141d4

Awesome! but whoa, why is GMV-CONVERT-DATE taking so long?


feat: improve performance

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Upgrading to OpenSSL 1.0.2d

after this one is merged, we should also rebuild the NuGet packages used by C, C++ and C# on windows.
https://www.nuget.org/packages/grpc.dependencies.openssl/

ping?

Ping.


latex report errors

This is a note. The latex report is missing a begin{document} and end{document} segment that will not allow for direct use in a compiler, that I know of. Perhaps that is an easy fix for the latex output, though that is far from my document style preference.

Hi, thank you for reporting! I'll check the examples in this repository. In one of the more recent versions of TESPy I added some formatters to the report, maybe I forgot to update here or the defaults are chosen poorly. Did you specify 'latex_body': True in the formatting dictionary? The default value is False, which generates a report without the LaTeX body to include within a different file.  Your formatting dictionary could look like this (see https://tespy.readthedocs.io/en/main/tespy_modules.html#automatic-model-documentation):
fmt = {
    'latex_body': True,  # adds LaTeX body to compile report out of the box
    'include_results': True,  # include parameter specification and results
    'HeatExchanger': {  # for components of class HeatExchanger
        'params': ['Q', 'ttd_l', 'ttd_u', 'pr1', 'pr2']},  # change columns displayed
    'Condenser': {  # for components of class HeatExchanger
        'params': ['Q', 'ttd_l', 'ttd_u', 'pr1', 'pr2']
        'float_fmt': '{:,.2f}'},  # change float format of data
    'Connection': {  # for Connection instances
        'p': {'float_fmt': '{:,.4f}'},  # change float format of pressure
        's': {'float_fmt': '{:,.4f}'},
        'h': {'float_fmt': '{:,.2f}'},
        'params': ['m', 'p', 'h', 's']  # list results of mass flow, ...
        'fluid': {'include_results': False}  # exclude results of fluid composition
    },
    'include_results': True,  # include results
    'draft': False  # disable draft mode
}
document_model(mynetwork, fmt=fmt)

Is there a specific example you are talking about in this repository?
Btw: All the results and specifications are available as dictionary containing pandas DataFrames after a simulation. The dictionary's keys are the class name of the respective instance, e.g. 'HeatExchanger' or 'Connection':
mynetwork.results['HeatExchanger']
mynetwork.results['Connection']
mynetwork.specifications['Connection']


HPA Autoscaling in v1.9.n clusters

Auto-scaling isn't working in our v1.9 clusters using the vanilla demo here:
http://blog.kubernetes.io/2016/07/autoscaling-in-kubernetes.html
At a minimum, it looks like we need metrics service component to make this work in 1.9.

@jackfrancis HPA is failing because k8s 1.8+ require metrics server. Metrics server in turn requires enabling Aggregated API's. I suggest Aggregated API's and metrics server be enabled for k8s 1.8+
I am happy to raise a PR for these if this is ok ?

Yes please

@pidah change that to 1.9+ and we're good to go :)

FYI: I don't think the metrics server is a hard requirement, we just finished the integration of HPA with custom metric support. While the metric server will become the defacto server, I think that the support for the new metric API was back ported to heapster.
You can configure heapster with the --api-server configuration, enable api aggregation on the api-server and finally for custom metrics, run the prometheus-adapter (assuming you have a prometheus) backend.


Typo in environment.yaml

There is a typo in the environment.yaml file, at line 201 the required package is
    - PyOpenGL-acclerate==3.1.6
should actually be looking for the PyOpenGL-accelerate instead.

Hi,
Thanks! Issue solved!
Best,
Youmin


Use trilinear interpolation on the limb-darkening models

Introduce a selection of stellar models surrounding the input values rather than the closest model. This will create a grid of 8 models, two for [M/H], two for Teff, and two for logg. Then use trilinear interpolation to calculate the desired limb darkening parameter.

I have the IDL code to do this for the 1D grid which can be translated to the 3D grid but I am having trouble working out where to put the information I need within the current structure of the limb-darkening code.
I think this will involve a fair amount of changes to the structure of the code but not the inputs or outputs so I will run a series of tests and show what is being done.
First is a def to calculate the tri-linear interpolation following https://en.wikipedia.org/wiki/Trilinear_interpolation

The structure of the data files for the 1D and 3D stellar models is the biggest problem here.
For the 1D stellar model data files from Kurucz the structure changes after 6000K meaning it is not a simple grid set-up posting the bounds for the grid points.
For the 3D grid it is so small any number outside the grid cannot be interpolated between using trilinear interpolation, as you cannot fully populate the corners of the cube space.

I have now created an .npz file which contains the full structure of the 1D array. This file is then loaded and searched to determine the starting line value for the needed table of intensities for each model that is used in the interpolation.


Add a --force option to tools/update_schema

When rebasing newer commits into your branch, one can enter the situation that the JSON schema has been updated in both your feature branch and in the commits you are rebasing into it.
https://github.com/equinor/fmu-dataio/blob/main/schema/definitions/0.8.0/schema/fmu_meta.json
The json schema is very large and changes to it can number in the hundreds of lines; not something we want to resolve by hand. Furthermore, the update_schema script will fail when this scenario is encountered because git adds its merge conflict lines (<<<<... and >>>>... etc) which makes the json invalid to parse.
https://github.com/equinor/fmu-dataio/blob/113fcaf3f387557173cf2e9b1f7251269530641e/tools/update_schema#L68-L70
We can do two things here:

[ ] Add a --force flag to the command line arguments that skips checking if the existing schema is the same as the new schema being generated, and just overwrite the existing schema. This function call can be skipped, but should issue an informational message that it is
https://github.com/equinor/fmu-dataio/blob/113fcaf3f387557173cf2e9b1f7251269530641e/tools/update_schema#L113
[ ] Add a try: except block when loading json so we can catch the exception and issue an error message that the json is malformed and that --force is an available option if you know why

Relevant standard argparse library docs: https://docs.python.org/3.11/library/argparse.html
with open(): https://docs.python.org/3/reference/datamodel.html#context-managers, https://docs.python.org/3/library/functions.html#open
NB: this script has no tests associated with it and probably does not need them since it is a rather simple utility script.

Merged with #745


Allows for circular dependencies

When working with ES Module dependencies, this graph is very handy. I'd
like to expand it to support circular dependencies, which aren't an
issue in this realm.
I don't think this API is the most ideal, since it tacks on yet another
argument to all the calls. I didn't add tests yet, since I wanted to
gauge your opinion.

A dependency graph has to be a DAG (Directed Acyclic Graph). If there are any cycles there's not really any way to produce a topological sort (i.e. the overall order).
E.g. if you have
A -> B -> C
^---------v

There's no way to satisfy the dependencies of A because it (eventually) depends on C, which depends on A

@jriecken Makes sense. I'm using this module outside of your intended use case, as it's especially useful for my ES module bundler. I can fully normalize every dependency and get an accurate order back for inlining into a single file. My thought here is that I'm intentionally breaking the guarantees afforded by no cyclic dependencies. So far I haven't seen any evidence that the overall order produced by my patch will cause any issues.
If you have interest in supporting my use case (module bundling) I'll research why my patch works for cyclic modules (valid in ES6 specification), my guess is that the algorithm for determining overall order with cyclic dependencies goes with first occurrence.

That's true - I guess as long as it outputs a potentially valid (assuming the cycle can be resolved by whatever is using the output) order and doesn't infinitely loop, an additional option to allow cycles would work.
A better place for the option would probably be a constructor parameter for DepGraph rather than in all the methods?


CMake Error

Dear Author：
I'm trying to reproduce this source code:https://github.com/JBLanier/pipeline-psro
but an error occurred when I compiled it with cmake,As you wrote in the installation tutorial, I got the error here:
mkdir build
cd build
CXX=clang++ cmake -DPython3_EXECUTABLE=$(which python3) -DCMAKE_CXX_COMPILER=${CXX} ../open_spiel
make -j$(nproc)
ctest -j$(nproc)
when i run this command：
CXX=clang++ cmake -DPython3_EXECUTABLE=$(which python3) -DCMAKE_CXX_COMPILER=${CXX} ../open_spiel
I got a lot of errors like this：

(p2sro_release) root@lx:~/pipeline-psro/dependencies/open_spiel/build# CXX=g++ cmake -DPython_TARGET_VERSION=3.6 -DCMAKE_CXX_COMPILER=${CXX} ../open_spiel
CMake Warning at abseil-cpp/CMakeLists.txt:72 (message):
A future Abseil release will default ABSL_PROPAGATE_CXX_STD to ON for CMake
3.8 and up.  We recommend enabling this option to ensure your project still
builds correctly.
-- Found Python3: /usr/lib/x86_64-linux-gnu/libpython3.8.so (found version "3.8") found components: Development
-- Configuring done
You have changed variables that require your cache to be deleted.
Configure will be re-run and you may have to reset some variables.
The following variables have changed:
CMAKE_CXX_COMPILER=
CMAKE_CXX_COMPILER=
-- The C compiler identification is GNU 9.4.0
-- The CXX compiler identification is GNU 9.4.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/g++
-- Check for working CXX compiler: /usr/bin/g++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Warning at abseil-cpp/CMakeLists.txt:72 (message):
A future Abseil release will default ABSL_PROPAGATE_CXX_STD to ON for CMake
3.8 and up.  We recommend enabling this option to ensure your project still
builds correctly.
-- Performing Test ABSL_INTERNAL_AT_LEAST_CXX17
-- Performing Test ABSL_INTERNAL_AT_LEAST_CXX17 - Success
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Found Python: /usr/lib/x86_64-linux-gnu/libpython3.8.so (found version "3.8") found components: Development
-- Configuring done
CMake Error at algorithms/CMakeLists.txt:91 (add_executable):
Target "trajectories_test" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at algorithms/CMakeLists.txt:87 (add_executable):
Target "tabular_exploitability_test" links to target "absl::container" but
the target was not found.  Perhaps a find_package() call is missing for an
IMPORTED target, or an ALIAS target is missing?
CMake Error at algorithms/CMakeLists.txt:39 (add_executable):
Target "best_response_test" links to target "absl::container" but the
target was not found.  Perhaps a find_package() call is missing for an
IMPORTED target, or an ALIAS target is missing?
CMake Error at algorithms/CMakeLists.txt:51 (add_executable):
Target "deterministic_policy_test" links to target "absl::container" but
the target was not found.  Perhaps a find_package() call is missing for an
IMPORTED target, or an ALIAS target is missing?
CMake Error at algorithms/CMakeLists.txt:55 (add_executable):
Target "evaluate_bots_test" links to target "absl::container" but the
target was not found.  Perhaps a find_package() call is missing for an
IMPORTED target, or an ALIAS target is missing?
CMake Error at algorithms/CMakeLists.txt:79 (add_executable):
Target "minimax_test" links to target "absl::container" but the target was
not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at algorithms/CMakeLists.txt:43 (add_executable):
Target "cfr_test" links to target "absl::container" but the target was not
found.  Perhaps a find_package() call is missing for an IMPORTED target, or
an ALIAS target is missing?
CMake Error at algorithms/CMakeLists.txt:47 (add_executable):
Target "cfr_br_test" links to target "absl::container" but the target was
not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at algorithms/CMakeLists.txt:71 (add_executable):
Target "history_tree_test" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at algorithms/CMakeLists.txt:67 (add_executable):
Target "get_legal_actions_map_test" links to target "absl::container" but
the target was not found.  Perhaps a find_package() call is missing for an
IMPORTED target, or an ALIAS target is missing?
CMake Error at algorithms/CMakeLists.txt:75 (add_executable):
Target "matrix_game_utils_test" links to target "absl::container" but the
target was not found.  Perhaps a find_package() call is missing for an
IMPORTED target, or an ALIAS target is missing?
CMake Error at algorithms/CMakeLists.txt:59 (add_executable):
Target "external_sampling_mccfr_test" links to target "absl::container" but
the target was not found.  Perhaps a find_package() call is missing for an
IMPORTED target, or an ALIAS target is missing?
CMake Error at algorithms/CMakeLists.txt:63 (add_executable):
Target "get_all_states_test" links to target "absl::container" but the
target was not found.  Perhaps a find_package() call is missing for an
IMPORTED target, or an ALIAS target is missing?
CMake Error at algorithms/CMakeLists.txt:83 (add_executable):
Target "outcome_sampling_mccfr_test" links to target "absl::container" but
the target was not found.  Perhaps a find_package() call is missing for an
IMPORTED target, or an ALIAS target is missing?
CMake Error at examples/CMakeLists.txt:16 (add_executable):
Target "cfr_example" links to target "absl::container" but the target was
not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at examples/CMakeLists.txt:10 (add_executable):
Target "mcts_example" links to target "absl::container" but the target was
not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at examples/CMakeLists.txt:7 (add_executable):
Target "matrix_example" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at examples/CMakeLists.txt:4 (add_executable):
Target "example" links to target "absl::container" but the target was not
found.  Perhaps a find_package() call is missing for an IMPORTED target, or
an ALIAS target is missing?
CMake Error at examples/CMakeLists.txt:13 (add_executable):
Target "value_iteration_example" links to target "absl::container" but the
target was not found.  Perhaps a find_package() call is missing for an
IMPORTED target, or an ALIAS target is missing?
CMake Error at examples/CMakeLists.txt:1 (add_executable):
Target "benchmark_game" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:288 (add_executable):
Target "y_test" links to target "absl::container" but the target was not
found.  Perhaps a find_package() call is missing for an IMPORTED target, or
an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:183 (add_executable):
Target "coop_box_pushing_test" links to target "absl::container" but the
target was not found.  Perhaps a find_package() call is missing for an
IMPORTED target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:161 (add_executable):
Target "bridge_test" links to target "absl::container" but the target was
not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:224 (add_executable):
Target "markov_soccer_test" links to target "absl::container" but the
target was not found.  Perhaps a find_package() call is missing for an
IMPORTED target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:274 (add_executable):
Target "laser_tag_test" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:244 (add_executable):
Target "oshi_zumo_test" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:165 (add_executable):
Target "catch_test" links to target "absl::container" but the target was
not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:193 (add_executable):
Target "go_test" links to target "absl::container" but the target was not
found.  Perhaps a find_package() call is missing for an IMPORTED target, or
an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:209 (add_executable):
Target "kuhn_poker_test" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:278 (add_executable):
Target "tiny_bridge_test" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:258 (add_executable):
Target "phantom_ttt_test" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:205 (add_executable):
Target "hex_test" links to target "absl::container" but the target was not
found.  Perhaps a find_package() call is missing for an IMPORTED target, or
an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:153 (add_executable):
Target "blotto_test" links to target "absl::container" but the target was
not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:178 (add_executable):
Target "connect_four_test" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:157 (add_executable):
Target "breakthrough_test" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:149 (add_executable):
Target "backgammon_test" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:262 (add_executable):
Target "pig_test" links to target "absl::container" but the target was not
found.  Perhaps a find_package() call is missing for an IMPORTED target, or
an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:283 (add_executable):
Target "tiny_hanabi_test" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:254 (add_executable):
Target "pentago_test" links to target "absl::container" but the target was
not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:197 (add_executable):
Target "goofspiel_test" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:173 (add_executable):
Target "coin_game_test" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:169 (add_executable):
Target "chess_test" links to target "absl::container" but the target was
not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:239 (add_executable):
Target "negotiation_test" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:214 (add_executable):
Target "leduc_poker_test" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:229 (add_executable):
Target "matching_pennies_3p_test" links to target "absl::container" but the
target was not found.  Perhaps a find_package() call is missing for an
IMPORTED target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:270 (add_executable):
Target "tic_tac_toe_test" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:219 (add_executable):
Target "liars_dice_test" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:201 (add_executable):
Target "havannah_test" links to target "absl::container" but the target was
not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:235 (add_executable):
Target "matrix_games_test" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:188 (add_executable):
Target "first_sealed_auction_test" links to target "absl::container" but
the target was not found.  Perhaps a find_package() call is missing for an
IMPORTED target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:249 (add_executable):
Target "oware_test" links to target "absl::container" but the target was
not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:266 (add_executable):
Target "quoridor_test" links to target "absl::container" but the target was
not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at game_transforms/CMakeLists.txt:15 (add_executable):
Target "misere_test" links to target "absl::container" but the target was
not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at game_transforms/CMakeLists.txt:9 (add_executable):
Target "turn_based_simultaneous_game_test" links to target
"absl::container" but the target was not found.  Perhaps a find_package()
call is missing for an IMPORTED target, or an ALIAS target is missing?
CMake Error at tests/CMakeLists.txt:7 (add_executable):
Target "spiel_test" links to target "absl::container" but the target was
not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at python/CMakeLists.txt:16 (add_library):
Target "pyspiel" links to target "absl::container" but the target was not
found.  Perhaps a find_package() call is missing for an IMPORTED target, or
an ALIAS target is missing?
CMake Error at CMakeLists.txt:72 (add_library):
Target "open_spiel_query" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at algorithms/CMakeLists.txt:1 (add_library):
Target "algorithms" links to target "absl::container" but the target was
not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:87 (add_library):
Target "bridge_double_dummy_solver" links to target "absl::container" but
the target was not found.  Perhaps a find_package() call is missing for an
IMPORTED target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:1 (add_library):
Target "games" links to target "absl::container" but the target was not
found.  Perhaps a find_package() call is missing for an IMPORTED target, or
an ALIAS target is missing?
CMake Error at game_transforms/CMakeLists.txt:1 (add_library):
Target "game_transforms" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at tests/CMakeLists.txt:1 (add_library):
Target "tests" links to target "absl::container" but the target was not
found.  Perhaps a find_package() call is missing for an IMPORTED target, or
an ALIAS target is missing?
-- Generating done
CMake Generate step failed.  Build files cannot be regenerated correctly.
(p2sro_release) root@lx:~/pipeline-psro/dependencies/open_spiel/build# CXX=clang++ cmake -DPython3_EXECUTABLE=$(which python3) -DCMAKE_CXX_COMPILER=${CXX} ../open_spiel
CMake Warning at abseil-cpp/CMakeLists.txt:72 (message):
A future Abseil release will default ABSL_PROPAGATE_CXX_STD to ON for CMake
3.8 and up.  We recommend enabling this option to ensure your project still
builds correctly.
-- Configuring done
You have changed variables that require your cache to be deleted.
Configure will be re-run and you may have to reset some variables.
The following variables have changed:
CMAKE_CXX_COMPILER=
CMAKE_CXX_COMPILER=
-- The C compiler identification is GNU 9.4.0
-- The CXX compiler identification is Clang 10.0.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/clang++
-- Check for working CXX compiler: /usr/bin/clang++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Warning at abseil-cpp/CMakeLists.txt:72 (message):
A future Abseil release will default ABSL_PROPAGATE_CXX_STD to ON for CMake
3.8 and up.  We recommend enabling this option to ensure your project still
builds correctly.
-- Performing Test ABSL_INTERNAL_AT_LEAST_CXX17
-- Performing Test ABSL_INTERNAL_AT_LEAST_CXX17 - Success
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Found Python: /usr/lib/x86_64-linux-gnu/libpython3.8.so (found version "3.8") found components: Development
-- Configuring done
CMake Error at algorithms/CMakeLists.txt:91 (add_executable):
Target "trajectories_test" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at algorithms/CMakeLists.txt:87 (add_executable):
Target "tabular_exploitability_test" links to target "absl::container" but
the target was not found.  Perhaps a find_package() call is missing for an
IMPORTED target, or an ALIAS target is missing?
CMake Error at algorithms/CMakeLists.txt:39 (add_executable):
Target "best_response_test" links to target "absl::container" but the
target was not found.  Perhaps a find_package() call is missing for an
IMPORTED target, or an ALIAS target is missing?
CMake Error at algorithms/CMakeLists.txt:51 (add_executable):
Target "deterministic_policy_test" links to target "absl::container" but
the target was not found.  Perhaps a find_package() call is missing for an
IMPORTED target, or an ALIAS target is missing?
CMake Error at algorithms/CMakeLists.txt:55 (add_executable):
Target "evaluate_bots_test" links to target "absl::container" but the
target was not found.  Perhaps a find_package() call is missing for an
IMPORTED target, or an ALIAS target is missing?
CMake Error at algorithms/CMakeLists.txt:79 (add_executable):
Target "minimax_test" links to target "absl::container" but the target was
not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at algorithms/CMakeLists.txt:43 (add_executable):
Target "cfr_test" links to target "absl::container" but the target was not
found.  Perhaps a find_package() call is missing for an IMPORTED target, or
an ALIAS target is missing?
CMake Error at algorithms/CMakeLists.txt:47 (add_executable):
Target "cfr_br_test" links to target "absl::container" but the target was
not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at algorithms/CMakeLists.txt:71 (add_executable):
Target "history_tree_test" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at algorithms/CMakeLists.txt:67 (add_executable):
Target "get_legal_actions_map_test" links to target "absl::container" but
the target was not found.  Perhaps a find_package() call is missing for an
IMPORTED target, or an ALIAS target is missing?
CMake Error at algorithms/CMakeLists.txt:75 (add_executable):
Target "matrix_game_utils_test" links to target "absl::container" but the
target was not found.  Perhaps a find_package() call is missing for an
IMPORTED target, or an ALIAS target is missing?
CMake Error at algorithms/CMakeLists.txt:59 (add_executable):
Target "external_sampling_mccfr_test" links to target "absl::container" but
the target was not found.  Perhaps a find_package() call is missing for an
IMPORTED target, or an ALIAS target is missing?
CMake Error at algorithms/CMakeLists.txt:63 (add_executable):
Target "get_all_states_test" links to target "absl::container" but the
target was not found.  Perhaps a find_package() call is missing for an
IMPORTED target, or an ALIAS target is missing?
CMake Error at algorithms/CMakeLists.txt:83 (add_executable):
Target "outcome_sampling_mccfr_test" links to target "absl::container" but
the target was not found.  Perhaps a find_package() call is missing for an
IMPORTED target, or an ALIAS target is missing?
CMake Error at examples/CMakeLists.txt:16 (add_executable):
Target "cfr_example" links to target "absl::container" but the target was
not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at examples/CMakeLists.txt:10 (add_executable):
Target "mcts_example" links to target "absl::container" but the target was
not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at examples/CMakeLists.txt:7 (add_executable):
Target "matrix_example" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at examples/CMakeLists.txt:4 (add_executable):
Target "example" links to target "absl::container" but the target was not
found.  Perhaps a find_package() call is missing for an IMPORTED target, or
an ALIAS target is missing?
CMake Error at examples/CMakeLists.txt:13 (add_executable):
Target "value_iteration_example" links to target "absl::container" but the
target was not found.  Perhaps a find_package() call is missing for an
IMPORTED target, or an ALIAS target is missing?
CMake Error at examples/CMakeLists.txt:1 (add_executable):
Target "benchmark_game" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:288 (add_executable):
Target "y_test" links to target "absl::container" but the target was not
found.  Perhaps a find_package() call is missing for an IMPORTED target, or
an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:183 (add_executable):
Target "coop_box_pushing_test" links to target "absl::container" but the
target was not found.  Perhaps a find_package() call is missing for an
IMPORTED target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:161 (add_executable):
Target "bridge_test" links to target "absl::container" but the target was
not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:224 (add_executable):
Target "markov_soccer_test" links to target "absl::container" but the
target was not found.  Perhaps a find_package() call is missing for an
IMPORTED target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:274 (add_executable):
Target "laser_tag_test" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:244 (add_executable):
Target "oshi_zumo_test" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:165 (add_executable):
Target "catch_test" links to target "absl::container" but the target was
not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:193 (add_executable):
Target "go_test" links to target "absl::container" but the target was not
found.  Perhaps a find_package() call is missing for an IMPORTED target, or
an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:209 (add_executable):
Target "kuhn_poker_test" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:278 (add_executable):
Target "tiny_bridge_test" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:258 (add_executable):
Target "phantom_ttt_test" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:205 (add_executable):
Target "hex_test" links to target "absl::container" but the target was not
found.  Perhaps a find_package() call is missing for an IMPORTED target, or
an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:153 (add_executable):
Target "blotto_test" links to target "absl::container" but the target was
not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:178 (add_executable):
Target "connect_four_test" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:157 (add_executable):
Target "breakthrough_test" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:149 (add_executable):
Target "backgammon_test" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:262 (add_executable):
Target "pig_test" links to target "absl::container" but the target was not
found.  Perhaps a find_package() call is missing for an IMPORTED target, or
an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:283 (add_executable):
Target "tiny_hanabi_test" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:254 (add_executable):
Target "pentago_test" links to target "absl::container" but the target was
not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:197 (add_executable):
Target "goofspiel_test" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:173 (add_executable):
Target "coin_game_test" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:169 (add_executable):
Target "chess_test" links to target "absl::container" but the target was
not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:239 (add_executable):
Target "negotiation_test" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:214 (add_executable):
Target "leduc_poker_test" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:229 (add_executable):
Target "matching_pennies_3p_test" links to target "absl::container" but the
target was not found.  Perhaps a find_package() call is missing for an
IMPORTED target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:270 (add_executable):
Target "tic_tac_toe_test" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:219 (add_executable):
Target "liars_dice_test" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:201 (add_executable):
Target "havannah_test" links to target "absl::container" but the target was
not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:235 (add_executable):
Target "matrix_games_test" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:188 (add_executable):
Target "first_sealed_auction_test" links to target "absl::container" but
the target was not found.  Perhaps a find_package() call is missing for an
IMPORTED target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:249 (add_executable):
Target "oware_test" links to target "absl::container" but the target was
not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:266 (add_executable):
Target "quoridor_test" links to target "absl::container" but the target was
not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at game_transforms/CMakeLists.txt:15 (add_executable):
Target "misere_test" links to target "absl::container" but the target was
not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at game_transforms/CMakeLists.txt:9 (add_executable):
Target "turn_based_simultaneous_game_test" links to target
"absl::container" but the target was not found.  Perhaps a find_package()
call is missing for an IMPORTED target, or an ALIAS target is missing?
CMake Error at tests/CMakeLists.txt:7 (add_executable):
Target "spiel_test" links to target "absl::container" but the target was
not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at python/CMakeLists.txt:16 (add_library):
Target "pyspiel" links to target "absl::container" but the target was not
found.  Perhaps a find_package() call is missing for an IMPORTED target, or
an ALIAS target is missing?
CMake Error at CMakeLists.txt:72 (add_library):
Target "open_spiel_query" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at algorithms/CMakeLists.txt:1 (add_library):
Target "algorithms" links to target "absl::container" but the target was
not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:87 (add_library):
Target "bridge_double_dummy_solver" links to target "absl::container" but
the target was not found.  Perhaps a find_package() call is missing for an
IMPORTED target, or an ALIAS target is missing?
CMake Error at games/CMakeLists.txt:1 (add_library):
Target "games" links to target "absl::container" but the target was not
found.  Perhaps a find_package() call is missing for an IMPORTED target, or
an ALIAS target is missing?
CMake Error at game_transforms/CMakeLists.txt:1 (add_library):
Target "game_transforms" links to target "absl::container" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
CMake Error at tests/CMakeLists.txt:1 (add_library):
Target "tests" links to target "absl::container" but the target was not
found.  Perhaps a find_package() call is missing for an IMPORTED target, or
an ALIAS target is missing?
-- Generating done
CMake Warning:
Manually-specified variables were not used by the project:
Python3_EXECUTABLE

CMake Generate step failed.  Build files cannot be regenerated correctly.
My environment is completely configured in accordance with the ReadMe：
https://github.com/JBLanier/pipeline-psro/blob/master/README.md
My system is Ubuntu 20.04
My environment.yml:
name: p2sro_release
channels:

defaults
dependencies:
python=3.6.12
pip=20.2.3
tensorflow-gpu==1.13.1
psutil=5.7.2
jupyter
pip:

ray==0.8
opencv-python==<IP_ADDRESS>
plotly==4.1.1
dm-sonnet==1.32
IPython==5.8.0
tensorflow-probability==0.6.0
cvxopt==1.2.3
networkx==2.2
mock==3.0.5
matplotlib==3.1.1
nashpy==0.0.19
scipy==1.1.0
attrs==19.1.0
absl-py==0.7.1
numpy==1.19.2
progress==1.5
pyglet==1.5.0
gym==0.17.3
pandas==1.1.3
tabulate==0.8.7
bidict==0.21.2
minio==6.0.0
lz4==3.1.0
setproctitle==1.1.10

I have updated Cmake and Clang to the latest version, but still can't compile, please help!

It is probably using an old abseil install. You should probably use and old version of OpenSpiel compatible with the instructions of pipeline PSRO code (check the release dates of our older versions and match it with the pupeline PSRO code).
But you can install OpenSpiel quite easily via pip these days. I doubt you would need to compile from scratch. See here

Can I check: did you run ./install.sh?

Yes I followed the steps exactly

My guess is that you are using and old install.sh cached from their repos, or somehow mixing the code. Our build from source works at master... I just did myself a few days ago.
Did you see the part where you can install from pip in one command these days? You should not need to install from source. Those are old instructions.
My advice is to open an issue on the Pipeline-PSRO repos.

My guess is that you are using and old install.sh cached from their repos, or somehow mixing the code. Our build from source works at master... I just did myself a few days ago.
Did you see the part where you can install from pip in one command these days? You should not need to install from source. Those are old instructions.
My advice is to open an issue on the Pipeline-PSRO repos.
If I install from pip,I am afraid that the version is inconsistent and cannot run the code.
Because the author of the code is using an old version of openspiel.
Is it feasible for me to install the latest version with pip?

Is it feasible for me to install the latest version with pip?

Yes, see the top of this page: https://github.com/deepmind/open_spiel/blob/master/docs/install.md
The core API has not changed much, so I think it should still work. (Assuming the code interacts with OpenSpiel only through Python)

Is it feasible for me to install the latest version with pip?

Yes, see the top of this page: https://github.com/deepmind/open_spiel/blob/master/docs/install.md:
python3 -m pip install open_spiel

The core API has not changed much, so I think it should still work. (Assuming the code interacts with OpenSpiel only through Python)

I used pip to install the latest version of openspiel. Will this directly overwrite the previous version? I'm not sure which version is used now, and the errors in running the code are the same, as shown below:

I used pip to install the latest version of openspiel. Will this directly overwrite the previous version? I'm not sure which version is used now, and the errors in running the code are the same, as shown below:

I used pip to install the latest version of openspiel. Will this directly overwrite the previous version? I'm not sure which version is used now, and the errors in running the code are the same, as shown below:

Where is the payoff table? How do I determine if the Payoff table I'm using is the latest version?

I believe this is coming from the Pipeline PSRO code. Please open an issue on their github repos: https://github.com/JBLanier/pipeline-psro/issues
I noticed the author JB Lanier also included an email address contact in the installation instructions.

Ok,thank you for your answer!I will put the question on the author's repo.


Can not enter date range in certain EDTF fields

Entering a date range like 2009/2010 seems to work fine for 2 of the 4 date fields on a Repository Item.
That range works well for Date Available and Date Copyrighted. However, that range doesn't work in the Date Created and Date Published fields.

Found a config issue and it'll be fixed in the next PR I create for content type configuration.

Fix is in https://github.com/jhu-idc/idc-isle-dc/pull/84


fix(ips): change optinrequired to uint32

:tada: This PR is included in version 2.3.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Make it possible to enable agent mode

https://prometheus.io/blog/2021/11/16/agent/

https://github.com/prometheus-operator/prometheus-operator/issues/3989


Beam mode does not work with geo-search?

Awesome tool!
Is this the expected behavior?
import asf_search as asf
from shapely.geometry import box
from dateparser import parse
import pandas as pd

# bay area
bounds: list = [-121.5, 34.95, -120.2, 36.25]
start_str: str = '2021-06-02'
end_str: str = '2021-06-09'

box_geo = box(*bounds)
start = parse(start_str)
end = parse(end_str)

results = asf.geo_search(platform=[asf.PLATFORM.SENTINEL1],
                         intersectsWith=box_geo.to_wkt(),
                         start=start,
                         end=end,
                         maxResults=100,
                         beamMode=[asf.BEAMMODE.IW]
                        )
df = pd.DataFrame([r.properties for r in results])

df.beamModeType.unique()

The output is array(['IW', 'slc'], dtype=object).

Hi Charlie, glad you’re enjoying the tool, even in its infancy.
If I’m reading this correctly, it looks like you’re seeing some unexpected results when doing a search restricted by beam mode, specifically some products are coming back with a beamModeType property of slc (looks like S1 InSAR products specifically.)
This appears to be a bug in how a couple fields were being handled in our REST API that asf_search communicates with, specifically beamMode vs. beamModeType. Most of our datasets conflate the two, but the S1 InSAR dataset has different values, as you see with the slc beamModeType property. What should be happening is that there should instead be a beamMode property in your results with the correct value.
We’ll take a closer look to confirm all this and assuming it all checks out, we’ll push a change that should fix it right away. For this one, since the data is coming from our REST API, no update to asf_search will be required, we’ll simply add the new beamMode field at our end via the backend REST API. Once you’ve had a chance to make any required changes, only then will we phase out the erroneous beamModeType property.
That is to say, once we have pushed this fix, the only change to your code below should be the last line, which would become:
df.beamMode.unique()

Additionally, I’m going to guess you didn’t actually want to include those S1 InSAR products in your search results. To alleviate that, I recommend including instrument=[asf.INSTRUMENT.C_SAR] as a search parameter. You’ll need to update asf_search to v2.0.2 for the instrument constants, they were just added. I’ll expose that value in the results properties as well, no update will be needed for that at your end.
Let us know if you have any further questions or concerns with this, and we’ll let you know as soon as we’ve applied a fix.


unsupported syntax:

Running this query fails on the latest release:
SELECT LANGUAGE(f.file_path, f.blob_content) AS lang, COUNT(*)  as n
FROM   files AS f
       JOIN commit_files
       JOIN refs
WHERE  ref_name = 'HEAD'
GROUP BY lang

I do not think this query is actually wrong, since simplifying it to this one makes it run successfully:
SELECT LANGUAGE(f.file_path, f.blob_content) AS lang, COUNT(*)  as n
FROM   files AS f
GROUP BY lang

The biggest problem right now is that the error message is this:
Query Failed - unknown error: unsupported syntax: <nil>

I just realized the problem was that I forgot to use NATURAL JOIN, that was the syntax error apparently.
We need to improve the error.


Ui disambiguation

Also pulls in a trivial guard for the balancer to not throw an exception when there are no busy nodes, because that's kind of/sort of like UI.

thanks for the fix!


Suggestion and Go to definition not working

Issue Type: Bug
I cannot use suggestion and go to definition feature anywhere, any language. I tried deleting all settings and reinstalling but it didn't work. Please help me.
Thanks
VS Code version: Code 1.40.0 (86405ea23e3937316009fc27c9361deee66ffbf5, 2019-11-06T17:02:13.381Z)
OS version: Windows_NT x64 10.0.18362

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz (6 x 2808)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_offsurface_control: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
23.93GB (17.52GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (2)

Extension
Author (truncated)
Version

vscode-react-native
msj
0.13.0

JavaScriptSnippets
xab
1.7.2

Same issue after 1.40.0 update

/needsMoreInfo
Please update this issue after reading https://github.com/Microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions#writing-good-bug-reports-and-feature-requests. Thanks.

Would like to report that it's working now! 😄

@nguyentd-uet ping for repro steps

I think it happened when I initialized a react native project with expo, using nativebase and customized the theme following this tutorial:
https://docs.nativebase.io/Customize.html#theaming-nb-headref

Can you try to repro a second time with that?

I have reproduced that way.

Does it reproduce when disabling extensions?

Yes. I tried disabled all extensions but it still doesn't work. And I can use 2 features (Suggestion and Go to definition) when I start the app for few seconds.

and in what files are you editing? JS, HTML, CSS?

It's JS file.

Ok, then please add the file and the exact steps that you are doing in that file so that it reproduces this

This is the project I reproduced: https://github.com/nguyentd-uet/AwesomeProject
Steps to reproduce:

Init a React native project with Expo: https://facebook.github.io/react-native/docs/getting-started
Install Nativebase (setup with Expo): https://docs.nativebase.io/docs/GetStarted.html
Customize Nativebase theme by following this toturial: https://docs.nativebase.io/Customize.html#theaming-nb-headref

Install Nativebase (setup with Expo):

Sorry, but not doing that. This should reproduce without that, eg. by opening a file and interacting with that file

Install Nativebase with Expo:

Install NativeBase by: yarn add native-base --save
Install Expo Fonts: expo install expo-font

Customize Nativebase theme:

Run this command from your terminal: node node_modules/native-base/ejectTheme.js

Raplace App.js by:
import React, { Component } from 'react'; import { Container, Content, Text, StyleProvider } from 'native-base'; import getTheme from './native-base-theme/components'; import material from './native-base-theme/variables/material'; export default class ThemeExample extends Component { render() {   return (     <StyleProvider style={getTheme(material)}>       <Container>         <Content>           <Text>             I have changed the text color.           </Text>         </Content>       </Container>     </StyleProvider>   ); } }

After that I could not use Go to difinition and Suggestion

Works for me

I don't know why but I tried on 3 different computers and all had the same error.


[bug] gradients of scatter_nd_add return None

The gradient of scatter_nd_add  always return None.  If the gradient is not implemented, it should raise an exception.

import tensorflow as tf
import numpy as np
import matplotlib.pyplot as plt
rng = np.random

x = tf.Variable(np.random.random((2, 4)).astype('float32'))
indice = tf.Variable(np.random.randint(0, 4, size=(2, 4, )), dtype=tf.int32)

x_val = np.random.random((2, 4))
indice_val = np.random.randint(0, 4, size=(2, 4, ))
val_val = np.random.random((2, 4))

# tf Graph Input
X = tf.placeholder("float")
Y = tf.placeholder("float")

# Set model weights
W = tf.Variable(np.random.random((2, 4)).astype('float32'), name="weight")
b = tf.Variable(np.random.random((2, )).astype('float32'), name="bias")

# Construct a linear model
pred = tf.add(tf.multiply(X, W), b)

y = tf.scatter_nd_add(x, indice, pred)

grad = tf.gradients(y, [W,b])

@narphorium, @ebrevdo  Can you take a look?

It has been 14 days with no activity and the awaiting tensorflower label was assigned. Please update the label and/or status accordingly.

scatter_nd_add has been changed into tensor_scatter_nd_add.
Also, in Tensorflow 2, placeholder has been deprecated, please use the latest Tensorflow compatible code see Migration Guide.


Splat message options when doing ActiveModel errors.add

Fix for https://github.com/adzap/validates_timeliness/issues/204

Thanks but the validator specs should cover it given it add errors internally and the issue should have showed up already. I'm interested in why it hadn't.

@adzap is it worth setting up GitHub actions to run the specs for Ruby 2.7 and 3?

Yes. Looks like we need to move off Travis to GitHub actions anyway. Any help in doing that would be appreciated.
On 26 Nov 2021, 9:11 PM +1100, Stuart Chinery @.***>, wrote:

@adzap is it worth setting up GitHub actions to run the specs for Ruby 2.7 and 3?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

@adzap sure thing, I've added the config for GitHub actions to run the tests as part of this PR (if that's cool?) and threw in the Dependabot config too.
Here are the specs running for both Ruby 2.7 and 3.0.

Excellent thanks! So ruby 3.0 is passing. Weird.
Do you know how to add the appraisal gemfiles into the actions matrix?
On 27 Nov 2021, 12:16 AM +1100, Stuart Chinery @.***>, wrote:

@adzap sure thing, I've added the config for GitHub actions to run the tests as part of this PR (if that's cool?) and threw in the Dependabot config too.
Here are the specs running for both Ruby 2.7 and 3.0.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Ignore me I was looking this on my phone and now realise it's part of the PR to fix it also. I will merge.


Unexpected grouping for ratios

Problem
We noticed that when using regex, !~ or =~ in a total query for a ratio, the resulting burnrate alerts are grouped by that label. This seems to come from this code. This doesn't happen for latency SLOs.
The consequences of this is that the alerting rule is calculated by groups, which is confusing because no grouping is explicitly configured and can result in alerts that can not be understood when checking the data shown in the Pyrra UI.
I was just wondering the purpose of that original piece of code doing the "invisible" grouping. It was removed from latency SLOs for this same reason apparently: #327
Example
An example for this is a metric that you export for many clusters but you want to narrow down to only a subset:
Error query: controller_runtime_reconcile_total{cluster=~"prod-1|prod-2|prod-3|prod-infra|prod-us-east4|stage",result="error"}
Total query: controller_runtime_reconcile_total{cluster=~"prod-1|prod-2|prod-3|prod-infra|prod-us-east4|stage"}
Will result in firing errorbudget burns when any of the cluster's burnrate hits the threshold, while the UI might show the budget of all clusters like expected.

I encountered the same behavior today while troubleshooting the alerting of one ratio SLO.
Looking into the implementation of all four types of SLOs, Ratio is the only one that creates this "fake grouping" based on regexp filters.
Took the liberty of opening #1053 to fix the issue.


fix issue with multiple java runtimes on macOS

Description
Flutter developers on macOS with multiple JVM installations encounter an issue where flutter reports an installation error with the installed Android SDK.
I found out that this was due to how Flutter looks for the JDK on macOS.
Below is a screenshot of what the error looks like, and the results after this fix.

Related Issues
Replace this paragraph with a list of issues related to this PR from our issue database. Indicate, which of these issues are resolved or fixed by this PR. There should be at least one issue listed here.
Tests
I added the following tests:
Replace this with a list of the tests that you added as part of this PR. A change in behaviour with no test covering it
will likely get reverted accidentally sooner or later. PRs must include tests for all changed/updated/fixed behaviors. See Test Coverage.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.

[ ] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change. If not, delete the remainder of this section.

[ ] I wrote a design doc: https://flutter.dev/go/template Replace this with a link to your design doc's short link
[ ] I got input from the developer relations team, specifically from: Replace with the names of who gave advice
[ ] I wrote a migration guide: Replace with a link to your migration guide

@mimam419 If you'd like to continue with this PR, please follow the instructions of the fluttergithubbot and the googlebot. Thanks!

Hi @zanderso,
I am having difficulties fixing the tests because I am quite new to flutter.
Would you mind guiding me on how to get that sorted?
Thank you.

See also https://github.com/flutter/flutter/issues/9429

LG after the comment is addressed + the test added

On the test, I would appreciate any guidance from your end, as I am encountering this error whenever I try to run the particular

Thank you.

LG after the comment is addressed + the test added

I was having difficulty running the test locally, but I have managed to proceed now.

LG after the comment is addressed + the test added

Hello @blasten, the tests are also fixed now.

Thanks for the contribution!


compile the pluginDemo went to wrong using "sh make.sh"

What went wrong:
A problem occurred configuring project ':app'.

Failed to notify project evaluation listener.
com/android/builder/dependency/ManifestDependency

@ChengKeven 参考 常见问题解答

我也遇到了这个问题，但改了路径没用呀，还是会出现

提问必看


'SPIFFS_format'? [-Werror=implicit-function-declaration] (IDFGH-7692)

I get the error when I recompile my project after executing the git pull, and I still get this error after I copy one from the example and compile it
I searched the whole idf directory and didn't find this function prototype.
/home/xiang/esp/esp-idf/components/spiffs/esp_spiffs.c: In function 'vfs_spiffs_truncate':
/home/xiang/esp/esp-idf/components/spiffs/esp_spiffs.c:798:15: error: implicit declaration of function 'SPIFFS_ftruncate'; did you mean 'SPIFFS_format'? [-Werror=implicit-function-declaration]
int res = SPIFFS_ftruncate(efs->fs, fd, length);
^~~~~~~~~~~~~~~~
SPIFFS_format

After I delete the idf and re-pull it, it compiles normally.


Option to force episode separation

In some cases, you've got a set of episodes that are ordered sequentially, however, they are actually double episodes.
So for instance:
Show - S01E01.avi
Show - S01E02.avi
Show - S01E03.avi
Show - S01E04.avi
They'd be renamed using an option to get the following:
Show - S01E01-E02.avi
Show - S01E03-E04.avi
Show - S01E05-E06.avi
Show - S01E07-E08.avi
In other words, tell the parser I need to treat each file as two episodes regardless of the naming.
Thank you =)

zsh helps prep the files at least:
zmv '([0-9][0-9])x([0-9][0-9]) - (*).avi' 'S$1E${(l:2::0:)$((($2 * 2) - 1))}-E${(l:2::0:)$(($2 * 2))} - $3.avi'

unsubscribe
On Fri, Feb 16, 2018 at 7:21 AM, Brian Ellwood<EMAIL_ADDRESS>wrote:

zsh helps prep the files at least:
zmv '([0-9][0-9])x([0-9][0-9]) - (*).avi' 'S$1E${(l:2::0:)$((($2 * 2) - 1))}-E${(l:2::0:)$(($2 * 2))} - $3.avi'
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dbr/tvnamer/issues/142#issuecomment-366247846, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AB05mu9s_JmEGPFRtv_1mEHGJE1FSJS9ks5tVY7hgaJpZM4SEUou
.

--
Jordan

Preprocessing the files like you did with zmv is a good solution to this I'd say - an option in tvnamer to do this would be overly specific


Squash Migrations [OSF-7651]

Purpose
Limit size of osf/migrations directory and optimize migration runtime
Changes

Create squash migration
Manually add migrations that couldn't be auto-squashed

Side effects
None expected
TODO
Follow up migration removing old migration files after this has been ran everywhere, as per the docs
Ticket
[OSF-7651]

This will need to be redone after @cwisecarver's file changes go out, closing


Module not found: Error: Can't resolve 'plot/hint' for Sankey

What error is that?
Module not found: Error: Can't resolve 'plot/hint'

Why do you have it in your examples but throws?
import Sankey from 'sankey';
import Hint from 'plot/hint';

Hey @wzup,
Those examples are making use of the directory structure from inside of the package. If you want to access sankey/hint you can import them from react-vis, vis:
import {
Sankey,
Hint
} from 'react-vis'

But you make a good point, the example should be converted so that they can all be be plug and play


Added new icons for Kubernetes components

Added icons for Kubernetes components - Token Review and Subject Access Review
Notes for Reviewers
I've not updated the Integrations spreadsheet yet. Waiting to get these icons approved first before I go ahead.
For the cytoscape shape, I propose we use a rounded rectangle for both icons.
Signed commits

[x] Yes, I signed my commits.

Title updated.


Clean and integrate sliced Wasserstein

TODO:
Code:

[x] break dependency on mpmath (new versions of sympy don't include it, we probably dont need it anyways)
[x] convert expected input to (n,2) numpy arrays rather than pandas frame.
[x] Add a couple tests.
[ ] Optimizations?
[ ] list comprehension instead of maps

Documentation:

[ ] Add a page in the documentation.
[ ] reframe all the docs to not be just persistence images.
[x] Add numpy docstrings
[ ] ensure docstrings render in the documentation.

Codecov Report

Merging #8 into master will increase coverage by 1.91%.
The diff coverage is 90.47%.

@@            Coverage Diff             @@
##           master       #8      +/-   ##
==========================================
+ Coverage   81.25%   83.16%   +1.91%
==========================================
  Files           3        4       +1
  Lines          80      101      +21
  Branches       15       23       +8
==========================================
+ Hits           65       84      +19
- Misses         14       15       +1
- Partials        1        2       +1

Impacted Files
Coverage Δ

persim/__init__.py
100% <100%> (ø)
:arrow_up:

persim/sliced_wasserstein.py
90% <90%> (ø)

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 3d022ac...b2915af. Read the comment docs.


Telegram 2.8.5+ don't allow any .dll-s near Telegram.exe

https://github.com/telegramdesktop/tdesktop/commit/5b2db4112fc4d5c9759685bb457ec0106b3bba1a
Since Telegram 2.8.5 FontMod is not loaded. Any ways to fix?

Double it.
Telegram ignores FontMod's dll under any proposed mimic name. FontMod doesn't load, debug log doesn't work.

Well... Just found good enough (for me) workaround via Registry FontSubstitutes (my OS is Windows 10).
Here is the tweaked part (I prefer old-styled pixel-hinted fonts like Arial or Tahoma):
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontSubstitutes]
"DAOpenSansRegular"="Arial"
"DAOpenSansRegularItalic"="Arial"
"DAOpenSansSemibold"="Arial"
"DAOpenSansSemiboldItalic"="Arial"
"DAVazirMedium"="Arial"
"DAVazirRegular"="Arial"

Font names are taken from Telegram's boot log 'log.txt'.
Look like it fixes almost everyting, except monospaced font.
Under Win10 Telegram uses system font 'Consolas' for monospaced text, so you can substitute it too (for 'Lucida Console' or 'Courier New', e.g.), but it will affect many applications compared to substitution of Telegram-specific 'DA...' fonts.

This issue was reported some days ago (#70) and can not be fixed. A solution is to use third-party dll injector.

If you are using Microsoft Store version of Telegram (link), you can try my project AppXLauncher.
Download exe here, put FontMod64.dll next to the exe and create AppXLauncher.json with following content:
{
	"PackageFamilyName": "TelegramMessengerLLP.TelegramDesktop_t4vj0pshhgkwm",
	"AppId": "Telegram.TelegramDesktop.Store",
	"InjectDll": "FontMod64.dll",
	"Persistent": true,
	"KillRunning": false
}

When Persistent is turned on, after open AppXLauncher.exe the first time, you can just open Telegram in Start Menu, without needing to open AppXLauncher.exe.
Notice that these files can not be moved or deleted. If you moved and unable open Telegram, or want to uninstall, just change Persistent to false and open AppXLauncher.exe once.

There is an unofficial Telegram Desktop called 64Gram (formerly Telegram Desktop x64). It provides Windows 64bit build with some enhancements, including allowing fontmod dll.


Unable to append to iceberg table with Polaris Open Catalog

Describe the bug
Unable to update a table with the write_iceberg method. Received an error  AWS Error UNKNOWN (HTTP status 301) during CreateMultipartUpload operation: Unable to parse ExceptionName: PermanentRedirect Message: The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint.
tried to do a written_df = df_write.write_iceberg(table, mode="append", io_config=[daft.io](http://daft.io/).IOConfig(s3=[daft.io](http://daft.io/).S3Config(region_name="us-west-2"))) but this didnt work
To Reproduce
from pyiceberg.catalog import load_catalog
import pyarrow.parquet as pq
catalog = load_catalog('demo_catalog',
**{'uri': 'https://xxxxxxxxx.snowflakecomputing.com/polaris/api/catalog',
'warehouse': 'demo_catalog',
'credential': 'sasasasas',
'scope':'PRINCIPAL_ROLE:ALL',
'client.region':'us-west-2'})
table = catalog.load_table("taxi.taxi_dataset")
df = daft.read_iceberg(table)
df_write = daft.sql("select * from df limit 1")
written_df = df_write.write_iceberg(df, mode="append") --> throws error unspecified endpoint
Tried
written_df = df_write.write_iceberg(table, mode="append", io_config=daft.io.IOConfig(s3=daft.io.S3Config(region_name="us-west-2"))) --> TypeError: got an unexpected keyword argument 'io_config'
Expected behavior
Supposed to append the new rows to the dataframe
Component(s)
Python Runner
Additional context
No response

Hey @sfc-gh-adlee, taking a look into this now. Will get back to you asap.

Oh looks like @jaychia and you were talking on our open Slack channel. Let me follow up with him.


Error: Error creating DB Subnet Group: InvalidSubnet: Subnet IDs are required.

Description
I usually run terraform via Jenkins to make changes on an environment. Occasionally I'll run a terraform plan and even apply from my local machine. I kept running into this issue where I ran the exact same code to run a terraform plan and apply successfully from my machine, but if I ran the code from Jenkins then I would encounter the issue:
When I ran the terraform plan on my local and apply everything would be fine and there would be no changes in the output of the terraform plan regarding a subnet option group.
When I ran the same code on Jenkins (btw our Jenkins downloads each module brand new everytime we run a build, as opposed to my local setup where
This is what I would see as part of the terraform plan on Jenkins:
...
[2021-04-15T12:54:22.002Z]   # module.master.module.db_subnet_group.aws_db_subnet_group.this[0] will be created
[2021-04-15T12:54:22.002Z]   + resource "aws_db_subnet_group" "this" {
[2021-04-15T12:54:22.002Z]       + arn         = (known after apply)
[2021-04-15T12:54:22.002Z]       + description = "prod-main-vpc subnet group"
[2021-04-15T12:54:22.002Z]       + id          = (known after apply)
[2021-04-15T12:54:22.002Z]       + name        = (known after apply)
[2021-04-15T12:54:22.002Z]       + name_prefix = "prod-main-vpc-"
[2021-04-15T12:54:22.002Z]       + tags        = {
[2021-04-15T12:54:22.002Z]           + "Name" = "prod-main-vpc"
[2021-04-15T12:54:22.002Z]         }
[2021-04-15T12:54:22.002Z]     }

Btw this is how I set my subnet group in my code:
...

db_subnet_group_name = data.terraform_remote_state.env.outputs.main_vpc_database_subnet_group_id
...

That value that it points to is:
terraform state show data.terraform_remote_state.env.

main_vpc_database_subnet_group_id    = "prod-main-vpc"

This is the issue I would get if I ran a terraform apply on Jenkins:
...
[2021-04-15T12:54:31.680Z]
[2021-04-15T12:54:31.680Z] Error: Error creating DB Subnet Group: InvalidSubnet: Subnet IDs are required.
[2021-04-15T12:54:31.680Z] 	status code: 400, request id: 4593024b-8900-4087-974c-83df65d26b81
[2021-04-15T12:54:31.680Z]
...

The same code would complete without issue on my local machine.
After a long few hours/days of debugging I figured out that the version
I then tried using different versions on my local.
Finally the fix for this was to pin the version of the module to this
  source = "terraform-aws-modules/rds/aws"
  version = "2.27.0"

To reproduce the issue just do: (Something along those lines)
..
module "master" {
  source = "terraform-aws-modules/rds/aws"

  engine               = "mysql"
  engine_version       = "8.0.20"
  family               = "mysql8.0" # DB parameter group
  major_engine_version = "8.0"      # DB option group
  instance_class       = "db.t3.large"

  vpc_security_group_ids = [aws_security_group.mysql[0].id]
  db_subnet_group_name = data.terraform_remote_state.env.outputs.main_vpc_database_subnet_group_id

...

Not sure if this is related, but on my local machine I also cache my terraform plugins with by putting this in my ~/.bash_profile
...
export TF_PLUGIN_CACHE_DIR="/var/tmp"
...

Hope this helps someone.

## ⚠ Note

Before you submit an issue, please perform the following first:

1. Remove the local `.terraform` directory (! ONLY if state is stored remotely, which hopefully you are following that best practice!): `rm -rf .terraform/`
2. Re-initialize the project root to pull down modules: `terraform init`
3. Re-attempt your terraform plan or apply and check if the issue still persists

## Versions
<!-- REQUIRED -->
 - Terraform: 0.12.30
<!-- Execute terraform -version -->

Terraform v0.12.30
+ provider.aws v3.10.0
+ provider.cloudflare v2.20.0
+ provider.external v2.1.0
+ provider.helm v1.3.2
+ provider.kubernetes v1.13.3
+ provider.null v2.1.2
+ provider.random v3.1.0
+ provider.template v2.1.2

Your version of Terraform is out of date! The latest version
is 0.15.0. You can update by downloading from https://www.terraform.io/downloads.html

 - Provider(s):
<!-- Execute: terraform providers -version -->
 - Module:

Terraform v0.12.30
+ provider.aws v3.10.0
+ provider.cloudflare v2.20.0
+ provider.external v2.1.0
+ provider.helm v1.3.2
+ provider.kubernetes v1.13.3
+ provider.null v2.1.2
+ provider.random v3.1.0
+ provider.template v2.1.2

Your version of Terraform is out of date! The latest version
is 0.15.0. You can update by downloading from https://www.terraform.io/downloads.html

## Reproduction
<!-- REQUIRED -->
Steps to reproduce the behavior:
<!-- Are you using workspaces? -->
Yes
<!-- Have you cleared the local cache (see Notice section above)? -->
On Jenkins, but not on local.
<!-- List steps in order that led up to the issue you encountered -->

### Code Snippet to Reproduce
<!-- Optional but very helpful -->

## Expected behavior
<!-- A clear and concise description of what you expected to happen -->

## Actual behavior
<!-- A clear and concise description of what actually happened -->

### Terminal Output Screenshot(s)
<!-- Optional but helpful -->

## Additional context
<!-- Add any other context about the problem here -->

This also happens for MSSQL using this module.

is this still an issue?
Just looking at a few things with the details provided:

db_subnet_group_name on its own means that by default the module will try to create a subnet group with the name provided (var.create_db_subnet_group defaults to true). to create a subnet group with this module you would need to use:

	db_subnet_group_name = <name>
	subnet_ids = [<one>, ...]

if you wish to pass an existing subnet group to the module you would need to use:

	create_db_subnet_group = false
	db_subnet_group_name = <name>

closing for now since I think the info above resolves the issue. please feel to comment back here if there is any new info and we can re-open


Replaced CAPNSOpenSSL with CNIOBoringSSL

I think it's better to reuse CNIOBoringSSL from NIOSSL 😉
Tested on macOS 10.14.4 and ubuntu server 16.04

Oh sorry i just saw pull request #12


joint_state_publisher: 1.12.13-0 in 'melodic/distribution.yaml' [bloom]

Increasing version of package(s) in repository joint_state_publisher to 1.12.13-0:

upstream repository: https://github.com/ros/joint_state_publisher.git
release repository: https://github.com/ros-gbp/joint_state_publisher-release.git
distro file: melodic/distribution.yaml
bloom version: 0.6.3
previous version for package: null

joint_state_publisher
* add bugtracker link now that this is not hosted on robot_model anymore
* Added a scrollarea around the gridlayout to support large number of joints
* pass robot objects into init_collada() and init_urdf()
* add test for collada supports
* add support for collada model : moved from https://github.com/ros/robot_model/pull/97
* Contributors: Guillaume Walck, Kei Okada, Mikael Arguedas

Merging for Melodic since it is still so small.


FAN - Auto mode

Main Fan slider is set with max value to 5, but 7 ( means auto ) is a correct value.
When I set auto on the IOS app, the slider change to 7. But how to set it to 7 with the slider ?

I'll look into it. Need to implement two more switches one for HIGH mode and one for AUTO mode (like the one for SILENT mode).
Please give me some time 😉

OK, latest commit includes Auto mode for Fan.
Not tested but should work. Let me know...

It works perfectly ! thank you :-)

It works perfectly ! thank you :-)

UI doesn't update immediately but the command works. Thank you for downloading my integration.


Memory error when creating fine anisotropic grid

error when creating fine anisotropic grid, i.e., memory error for nr_exp = fac_ani +1, fac_ani >3 and alpha_coeff = 0 or 2

@CodingAllan Please put details in the description and give a simple title. Can you give more details on the type of error?