Add pqtl_entrez_id column to pqtl.tsv

Follows up on https://github.com/greenelab/hetmech/pull/81 by @naglem.
IIRC, some of the in-progress versions of pqtl.tsv from https://github.com/greenelab/hetmech/pull/81 had a column titled pqtl_entrez_id, which had the genes from pqtl_gene, but converted to entrez GeneIDs. It looks like this didn't make it into the merged pqtl.tsv
@naglem would you be able to re-add the pqtl_entrez_id column? Would make the analysis a tad bit easier.

@dhimmel I've updated the data in data/pqtl/pqtl.tsv to have a entrez ID column labeled pqtl_entrez_id. Let me know if you have any issues with this, thanks.

Awesome! We'll need to merge these changes in via a pull request. I created https://github.com/greenelab/hetmech/pull/84, but things have gotten a bit messed up since you haven't been creating new branches for each pull request. Here's a guide on the general pull request workflow. The key is to keep your master branch up to date with upstream/master and to start the pull requests from an up-to-date branch. Note that when we merge PRs, we often squash merge so the actual commits end up getting combined into one. This means it's crucial to always pull the commits from upstream/master.
If you create an up-to-date branch, you should be able to apply the single commit that should form the pull request by running:
git cherry-pick e65dd8d0e3c434369c442c73415d05ba495d4791

Hi @dhimmel, not sure if I resolved this, but i created a new branch for this pull request, when I apply the command git cherry-pick e65dd8d0e3c434369c442c73415d05ba495d4791 it indicates that the branch is up to date, with nothing to commit. Again not sure if it is resolved.

You will know that things are correct if when you do git log you see e65dd8d0e3c434369c442c73415d05ba495d4791 is the most recent commit followed by e3dd5cdc2b97f235d914d43bf39ff7e41965e482.
That's good you know have a branch besides master. Now this is what I think you'll have to do:
# get back to master
git checkout master

# return master branch to a previous state
git reset --hard c34d8d94a072418a97ebd14d86412a78fbe17c03

# Add greenelab/hetmech repo as `upstream` repo
git remote add upstream https://github.com/greenelab/hetmech.git

# Fast forward master branch to upstream
git pull --ff-only upstream master

# Checkout new branch for this PR
git checkout -b issue-62

# Add the commit
git cherry-pick e65dd8d0e3c434369c442c73415d05ba495d4791

# Push to GitHub (it will have an error, copy the suggested command to set the remote branch)
git push

# Go to github and create PR.

Let's see if that works

@dhimmel  e65dd8d is the most recent commit, but it is followed by fb657bd. When I git cherry-pick, it says:

On branch issue-62
You are currently cherry-picking commit e65dd8d.
nothing to commit, working tree clean
The previous cherry-pick is now empty, possibly due to conflict resolution.

Hmm. Did all of the previous commands work, or did some appear to result in errors? git remote add will error if its already been configured (that's fine). I'm not sure why you are still seeing https://github.com/greenelab/hetmech/commit/fb657bd810212e6b039648b86c8b40bc246fcdec in your history because the git reset --hard should have removed that.

When I perform git pull --ff-only upstream master, I get:

From github.com:naglem/hetmech

branch            master     -> FETCH_HEAD
Updating c34d8d9..e65dd8d
Fast-forward
data/pqtl/README.md               |      3 +
data/pqtl/pqtl.tsv                |   2558 +++
data/pqtl/snps-to-locus-genes.tsv | 131466 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
environment.yml                   |      1 +
4 files changed, 134028 insertions(+)
create mode 100644 data/pqtl/README.md
create mode 100644 data/pqtl/pqtl.tsv
create mode 100644 data/pqtl/snps-to-locus-genes.tsv
Is this correct? The other commands work...

Yes, the git pull looks good. --ff-only stands for fast forward only and ensures that there are no commits in the local branch that aren't in the remote branch you're pulling from. In other words, you cannot have a divergence.
Since the cherry-pick seems that it may not be working, can you create a new branch and just replace the pqtl.tsv with the correct version (i.e. this one). Then add that file and commit it?

I closed the last PR. It seems that when I perform git pull --ff-only upstream master, it pulls all commit history into the current branch, including the commits that I made. When I do a hard reset, the git log indicates that I am back to that commit, so it must be related to the git pull command.

What does git remote --verbose output? It sounds like you may have upstream configured to point at naglem/hetmech rather than greenelab/hetmech.

@dhimmel I think this was the issue, I reset the upstream branch, and now it appears to be correct when I do the PR. Let me know if you see other issues. Thanks for the help!

Nice. Here are the steps to avoid this from happening in future. Now that the PR has been merged you can go:
# Return to your master branch
git checkout master

# Fast forward master branch to upstream
git pull --ff-only upstream master

# Update master branch on your github
git push origin master

It's a good idea to do the git pull command right before you start a new PR to make sure you're working from the latest upstream version. Before making any commits for a new feature / PR, make sure to checkout a new branch. This way your master will always be behind or in line with the upstream.


AI-Data-Analysis-MultiAgent for no computer science professional

I'm not a computer science professional, but I want to use this tool. Can you give me the steps to use it in a google collab?

I don't recommend using google colab. Some functions may be abnormal. I recommend running this library locally.

I don't have OpenAI's API, but if I use the Whisper Large v3 Turbo model provided by Groq, do I basically not need to change parameters? Can I simply clone and install it locally?

Currently, only OpenAI is supported, others are still under development.

How can I use the azure open ai endpoints?

How can I use the azure open ai endpoints?
Maybe you can start modifying it from here
https://github.com/starpig1129/AI-Data-Analysis-MultiAgent/blob/main/core/language_models.py


Added pluggable storage (#419):

This PR introduces a new option "storage" for Datastore and also for Persistence. This allows to create a custom storage module (with the same API as the "bundled" storage.js module(s)) and use that as a low-level layer to the file system.
This makes it possible, for example, to create virtual filesystems for NeDB with very specific properties. For example (taken from a real-world application):

in the browser, a custom storage layer for NeDB, that notices changes, can take snapshots and synchronizes with the server at byte level
generally, provide a in-memory "file system" for NeDB, for example to temporarily read a datastore that has been received via HTTP, without needing to store it as real files

This change is also the basis for an experimental two-way, realtime data sync with a server including snapshot capabilities (similar to PouchDB, but with more control over syncing and conflict resolution).
I really hope this gets merged! Thanks in advance.
See issue #419

CHANGES:

added new, optional "storage" options to Datastore and Persistence, to allow overriding the default "storage.js" module

Necessary changes to make that possible:

turn all static method of "Persistence" class into normal methods
adjust static calls to Persistence.ensureDirectoryExists() into normal class method invocations (applies to benchmarks and tests only)
reimplemented (benchmarks) commonUtilities prepareDb() to remove Persistence dependency. The module already relies on a Node environment and so can also use "mkdirp" module directly. The new implementation behaves exactly as before (ie. ignores mkdirp() errors)

All tests and benchmarks still passing.

@louischatriot can you look at this one?
Would really like to see it in

@jampy @farfromrefug  Merged into nedb3

This also makes it easier to support alternative file systems like React Native and WinJS (#390)


ImageManager::inspect(), use id not repo:tag to identify.

Images need not have a name and tag, so __toString(9 may return ":"
hence one needs to the the id (e.g. 5a6ad7a9472d661def485ec19146a69f7ae1a78d3064c9d0cc18b44fe445f279).
I came across this when trying to list all images as follows. the inspect() line will not work without this fix.
$images = $imagemgr->findAll();
foreach ($images as $image) {
$data=$imagemgr->inspect($image);
print($image->__toString() . " " . $data['Created'] . " " . $image->getID() . "\n");
}
Also:

Improved error string. Doc: correct return.

Could we briefly talk about these two lines, before finalising the commit? See #78
$image->setId($data['Id']);
// @TODO Add extra info on image

hey @Boran, thanks a bunch for contributing. If you could fix the coding style according to the comments I left that would be great!

Apologies for the simple styling errors.
Could we briefly talk about these two lines? See #78
$image->setId($data['Id']);
// @TODO Add extra info on image

Thank you @Boran !


Highly confusing error message when you forget the "new" on a call to a constructor

Uncaught Error: Class '_Type' has no instance method 'call'.
A better error would be:
Uncaught Error: Class '_Type' has no instance method 'call'. Did you forget to use 'new' when calling a constructor?

If you "forget" the new operator you end up with, say, the expression
var x = List()
The right hand side is a type literal followed by the call operator. That is a perfectly legal Dart expression. However, class literals (of type _Type) do not implement the call operator, thus the error message at runtime when the call is resolved.
I think the more helpful error message proposed here belongs to the Analyzer or another tool. The VM should not be in the business of second-guessing completely legal Dart code.
I do like the idea of making Dart a more robust language with more compile-time errors.

The proposed change doesn't affect the VM. The proposed change is to add a _Type.noSuchMethod implementation.

(or to make the Object.noSuchMethod implementation check for this case)

In Dart 2 there is optional new anyway.


Allow a "git" registry to be consumed from a repository subdirectory

Currently, vcpkg assumes that a registry is its own separately versioned project and that its content directories live at the root of the repository. It would be convenient to also allow hosting a custom port directly from a project subdirectory as an alternative to bundling multiple ports together under a single custom registry.
Proposed solution
Here is an example vcpkg-configuration.json showing the single "path" entry needed to support this registry model. Supporting the "path" field does not change the semantics or configuration of the current registry model, only that of the "git" registry entry in vcpkg-configuration.json.
The repository and branch reference show below are live as of Sep 14, 2022:
{
  "default-registry": {
    "$info": "The currently support vcpkg baseline",
    "kind": "builtin",
    "baseline": "d474b26040207c89d81f50dd39be7d335f1d3745"
  },

  "registries": [
    {
      "$info": "A custom git registry published as a relative subdirectory of a project",
      "kind": "git",
      "repository": "https://github.com/propulsortech/lexertl14",
      "path": "vcpkg",
      "packages": [ "lexertl14" ],
      "baseline": "5dbc61f0ced9aef6d75f8c9025e7a9366137a94d",
      "reference": "1-experiment-with-lexertl14-as-its-own-vcpkg-registry"
    }
  ]
}

Describe alternatives you've considered
At the moment, I have a single custom registry containing ports for several projects. The other alternatives I have considered include exposing the ports and versions directories in the root of the project and creating a separate project under the same namespace just for the registry (e.g. propulsortech/lexertl14-vcpkg). Both options work as expected but are not as elegant or straightforward to maintain as having the custom registry under the project itself.
Additional context
I dove into the vcpkg-tool source (at 3c502fa609 on main) to convince myself that this feature is even possible. The files affected appear to be vcpkg/configuration.cpp and vcpkg/registries.cpp, as well as vcpkg-test/registries.cpp for verifying that parsing works and azure-pipelines/end-to-end-tests-dir/registries.ps1 for e2e testing. Documentation for the git registry would also need to be updated to include a description of how the "path" field works.

I was able to implement enough of the "path" field support so that the JSON example from the issue description works with a local build of vcpkg.exe. For reference, I also made a fork to record my changes for future reference: https://github.com/demianmnave-pti/vcpkg-tool.git

@JackBoosY Thanks for the input. I'm wondering how you envision manifests, version isolation, and vcpkg.json helping here?
I think what I'm suggesting is simpler than what you have in mind. I just want to expose a custom git registry under a subdirectory of a project, rather than have the registry "version" and "ports" paths exposed in the root of the project.
This isn't adding new functionality, it's just a small addition to the supported fields in vcpkg-configuration.json. You can see the limited extent of the changes if you'd like to take a look at my fork.
Also, if it helps clarify my request, the initial registries specification mentions what would appear to be the functionality I am after (copied here for reference, emphasis mine):

<registry-implementation.git>:

"kind": The string "git"
"repository": A URI
Optionally, "path": An absolute path into the git repository
Optionally, "ref": A git reference

I did not find any information in the issues or in the documentation concerning why the "path" field was dropped from the current git registry specification. If you happen to know the reason or if you have a reference to a public discussion, please do let me know.
Thank you.

Ah, I think this was interpreted as 'allow the registry itself to have a path relative to a vcpkg.json' rather than 'implement the path field'.

My apologies for being unclear at the outset. Hopefully the request clear now, though.

Sorry I misunderstood what you meant.

No worries, thanks for considering my request.
If you'd like to move forward with this feature, I can work on a pull request. Just let me know.

I also just discovered the concept of an orphaned git branch, which would provide a viable alternative. The only drawback is that a custom registry in an orphaned branch is not as transparent as one in a subdirectory.
I understand if you would prefer to table my feature request because similar functionality exists.

I also just discovered the concept of an orphaned git branch, which would provide a viable alternative.

If it's orphaned then the commits associated with be removed at the next git gc as soon as they age out of the reflog.

@BillyONeal I thought git gc only prunes dangling or unreachable commits? The commits in an orphaned branch are reachable from that branch, so I think they would be safe from git gc.
Just as an experiment, I tried git gc --prune=now on a clone with an orphan branch, and all commits in the branch seem intact. Please do correct me if I'm missing something, though.

Hmmm I think I may be mixing up orphan and detached...

No worries!

Fork moved here: https://github.com/propulsortech/vcpkg-tool/tree/support-a-git-registry-under-a-subdirectory

This has dropped in priority for us, so I've moved the fork back to: https://github.com/demianmnave-pti/vcpkg-tool.git

Hi, I see that this was marked as a stale issue and closed by the bot as not planned – we would love this functionality to be included as a part of vcpkg since we use multiple custom registries in different repositories when building our CMake target on one repository. As a workaround, I am considering using different branches in the same repository which mirror the registries as mentioned above; if there is a better way at this time (December 2023), any help would be appreciated!

Hi, it would be great to keep this feature request open

Still relevant!


Patch for #19: Error Building on Mac OS X Sierra 10.13.3

See #19. Adjusting CMakeLists.txt to adjust for newest Boost 1.67 and Boost.Python 1.67 separately

@Achimh3011 I'd update it too although I think there's a better way to adjust it via CMakeLists to check for different Python versions.

I'd be glad to hear better ideas to check for different python versions within CMakeLists.

Confirming it works, weirdly we need the line 3 on CMakeLists.txt
(build-_6dbz9g0)  grokmachine@spock  ~/dev/boost-python-examples/build   patch/osx-boost-python3 ●  cmake ..
-- The C compiler identification is AppleClang <IP_ADDRESS>20039
-- The CXX compiler identification is AppleClang <IP_ADDRESS>20039
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/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: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++
-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found PythonInterp: /Users/grokmachine/.local/share/virtualenvs/build-_6dbz9g0/bin/python (found version "3.6.5")
-- Boost version: 1.67.0
-- Found the following Boost libraries:
--   python3
-- Found PythonInterp: /Users/grokmachine/.local/share/virtualenvs/build-_6dbz9g0/bin/python (found suitable version "3.6.5", minimum required is "3")
-- Found PythonLibs: /usr/local/Frameworks/Python.framework/Versions/3.6/lib/libpython3.6m.dylib (found suitable version "3.6.5", minimum required is "3")
-- PYTHON_LIBRARIES = /usr/local/Frameworks/Python.framework/Versions/3.6/lib/libpython3.6m.dylib
-- PYTHON_EXECUTABLE = /Users/grokmachine/.local/share/virtualenvs/build-_6dbz9g0/bin/python
-- PYTHON_INCLUDE_DIRS = /usr/local/Frameworks/Python.framework/Versions/3.6/include/python3.6m
-- Boost_LIBRARIES = /usr/local/lib/libboost_python3-mt.dylib
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/grokmachine/dev/boost-python-examples/build
 (build-_6dbz9g0)  grokmachine@spock  ~/dev/boost-python-examples/build   patch/osx-boost-python3 ●  make -j16
Scanning dependencies of target hello
Scanning dependencies of target classes
Scanning dependencies of target operators
Scanning dependencies of target ctor
Scanning dependencies of target member
Scanning dependencies of target inheritance
Scanning dependencies of target virtual
Scanning dependencies of target embedding
Scanning dependencies of target overload
Scanning dependencies of target policies
Scanning dependencies of target mymodule
Scanning dependencies of target myexceptions
Scanning dependencies of target iterators
Scanning dependencies of target auto_instance
[  6%] Building CXX object 07-Operators/CMakeFiles/operators.dir/operators.cpp.o
[  6%] Building CXX object 11-Iterators/CMakeFiles/iterators.dir/iterators.cpp.o
[ 10%] Building CXX object 03-Constructors/CMakeFiles/ctor.dir/ctor.cpp.o
[ 13%] Building CXX object 09-Overloading/CMakeFiles/overload.dir/overload.cpp.o
[ 16%] Building CXX object 05-Inheritance/CMakeFiles/inheritance.dir/inheritance.cpp.o
[ 20%] Building CXX object 12-Exceptions/CMakeFiles/myexceptions.dir/myexceptions.cpp.o
[ 23%] Building CXX object 10-Embedding/CMakeFiles/mymodule.dir/mymodule.cpp.o
[ 26%] Building CXX object 04-ClassMembers/CMakeFiles/member.dir/member.cpp.o
[ 30%] Building CXX object 10-Embedding/CMakeFiles/embedding.dir/mymodule.cpp.o
[ 33%] Building CXX object 10-Embedding/CMakeFiles/embedding.dir/embedding.cpp.o
[ 36%] Building CXX object 01-HelloWorld/CMakeFiles/hello.dir/hello.cpp.o
[ 40%] Building CXX object 08-CallPolicies/CMakeFiles/policies.dir/policies.cpp.o
[ 46%] Building CXX object 06-VirtualFunctionsInPython/CMakeFiles/virtual.dir/virtual.cpp.o
[ 46%] Building CXX object 02-ExposingClasses/CMakeFiles/classes.dir/classes.cpp.o
[ 50%] Building CXX object 13-AutoInstantiation/CMakeFiles/auto_instance.dir/myextension.cpp.o
[ 53%] Building CXX object 13-AutoInstantiation/CMakeFiles/auto_instance.dir/auto_instance.cpp.o
[ 56%] Linking CXX shared module hello.so
[ 60%] Linking CXX shared module myexceptions.so
[ 60%] Built target hello
[ 60%] Built target myexceptions
[ 63%] Linking CXX executable embedding
[ 66%] Linking CXX shared module mymodule.so
[ 66%] Built target embedding
[ 70%] Linking CXX executable auto_instance
[ 70%] Built target mymodule
[ 73%] Linking CXX shared module policies.so
[ 76%] Linking CXX shared module member.so
[ 76%] Built target auto_instance
[ 80%] Linking CXX shared module virtual.so
[ 83%] Linking CXX shared module inheritance.so
[ 86%] Linking CXX shared module operators.so
[ 90%] Linking CXX shared module iterators.so
[ 90%] Built target member
[ 90%] Built target policies
[ 93%] Linking CXX shared module classes.so
[ 93%] Built target operators
[ 93%] Built target virtual
[ 93%] Built target inheritance
[ 93%] Built target iterators
[ 96%] Linking CXX shared module ctor.so
[ 96%] Built target classes
[100%] Linking CXX shared module overload.so
[100%] Built target ctor
[100%] Built target overload


No way to put client id into the extnesion preferences

No way to put spotify client id and client secret into the extension preferences

Could you explain the issue a bit more?

Closing this issue due to inactivity. @itslexii feel free to re-open it with more details.


function inlining, simplification

@robin-swift I see the EMBEDDED define, can you send me an email to<EMAIL_ADDRESS>I am curious about your use-case, and wanted to know how I could help.

Oh that should be ARDUINO, I'll get that in the other PR (see #91 )

Based on reading the code and bits of docs we have I thought we were working under the assumption of an embedded version that would run within 32kb of code on an Arduino?

I personally don't have an embedded system to test this on. I've just got a Brother PES something or other that I'm using.

That makes sense, you've been doing great work cleaning up what is here. I
was just trying to see if there is a specific use case.
On Thu, Sep 16, 2021 at 12:41 PM robin-swift @.***>
wrote:

I personally don't have an embedded system to test this on. I've just got
a Brother PES something or other that I'm using.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Embroidermodder/libembroidery/pull/89#issuecomment-921101932,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADBZHHAX74H3HJN75KQ3IDUCIT5HANCNFSM5EEY3URA
.


need to provide support for VisualStudio

generate Visual Studio Solution/project files using qmake

A VisualStudio 2019 project file *.vcxprj has ben created.
see project subdir future-cpp-loop


Review wiki pages to add as heredocs in Python files

@hrubyjan Is the GitLab wiki still relevant, or can we lose it without worry?
https://gitlab.com/open-contracting/dqt/-/wikis/home
If it's needed, I can transfer it as well.

Moved most of the wiki. Pasting the rest here. First compiled release-level checks:
contracts.value.consistent.md
This rule can be applied if and only if

for a particular contracts.awardID exists exactly one item in awards array.
all relevant values have currency and amount fields set
all relevant values either have the same currency or can be converted to USD using date field
relevant values

award.value
contracts[i].value for all contracts that have a particular awardID set

it passes if

the sum of all relevant contracts[i].value does not differ from the matching awards.value by more than 50 %

if fails if

the sum of all relevant contracts[i].value differs from the matching awards.value by more than 50 %

Metadata

awardID
awards.value
sum contracts[i].value

contracts[].awardID.reference.md
This rule can be applied on any instance of type $ref: "#/definitions/Contract" from OCDS schema
It fails if

awardID is not set for a particular contract
awards array is not set
awards array does not contain referenced item
awards array contains multiple items with referenced id

It passes if

awards array contains exactly one item with a proper id set

Metadata

path to a tested instance of $ref: "#/definitions/Contract"

contracts[].implementation.transactions.value.consistent.md
This rule can be applied if and only if

for a particular contract exists non-empty contracts[i].implementation.transactions array
for a particular contracts.awardID exists exactly one item in awards array.
all relevant values have currency and amount fields set
all relevant values either have the same currency or can be converted to USD using date field
relevant values

contracts[i].value
contracts[i].implementation.transactions[j].value

it passes if

the sum of all relevant contracts[i].implementation.transactions[j].value is less or equal to contracts[i].value

Otherwise, it fails
Metadata

path to the tested contract
contracts[i].value
sum contracts[i].implementation.transactions[j].value

parties.roles.consistent.md
This rule can be applied to any member of parties array which has one of the following roles set: procuringEntity, tenderer,supplier,payer,payee
It passes if

If one of these roles is set and there exists a proper $ref: "#/definitions/OrganizationReference to this party.

Role
OrganizationReference

procuringEntity
tender.procuringEntity

tenderer
any member of tender.tenderer[]

supplier
any member of awards[i].suppliers[]

payer
any member of contracts[i].implementation.transactions[j].payer

payee
any member of contracts[i].implementation.transactions[j].payee

It fails

If a proper $ref: "#/definitions/OrganizationReference to this party does not exists

Metadata

path to a tested party
party role that was examined
identification of a resource

Period.durationInDays.consistent.md
This rule can be applied to any instance of type $ref: "#/definitions/Period from OCDS schema if and only if the instance has either startDate,endDate and durationInDays set or startDate, maxExtentDate and durationInDays set.
It passes if

durationInDays equals to the difference between startDate and endDate.

or

if endDate is not set then durationInDays equals to the difference between startDate and maxExtentDate.

Otherwise, it fails
Metadata will contain

path to a tested instance of Period

tender.value.consistent.md
This rule can be applied if and only if

tender.value is set
planning.budget.amount is set
both values are positive or both values are negative
both values have both amount and currency fields set
both values either have the same currency or can be converted to USD using date field

Otherwise, the value is undefined.
It passes

if tender.value does not differ from planning.budget.amount by more than 50 %

100% - planning.budget.amount

It fails

if tender.value differs from planning.budget.amount by more than 50 %

Metadata

tender.value
planning.budget.amount

Value.realistic.md
This rule can be applied to any instance of $ref: "#/definitions/Value" from OCDS schema if it has amount and currency set and if currency is either USD or is convertible to USD using releases date field
Otherwise, the value is undefined
It passes if

-5 billion USD <= amount <= 5 billion USD

If fails if

-5 billion USD > amount  or amount > 5 billion USD

Dataset-level
buyer.distribution.md
Short description

Get a number of distinct ocid's per buyer (identified by buyer.identifier.scheme and buyer.identifier.id)
Check if the total share of all buyers with 1 ocid only is 0 % < share < 50 % of all OCIDs

Details
This check can be evaluated only if a dataset contains at least 1000 resources that have both fields buyer.identifier.id and buyer.identifier.scheme set
Otherwise, the check is N/A

Get a total number of distinct ocid from a dataset

get only ocid that has identifiable buyer (buyer.identifier.id and buyer.identifier.scheme is set)

Get a number of distinct ocid per buyer.

buyer is identified by a unique combination of buyer.identifier.id and buyer.identifier.scheme

The check passes

total count of distinct ocid of all buyers with only 1 ocid is lower than 0,5 x total number of distinct  ocid with identifiable buyer

The check fails

if the share of single ocid buyers on the total number of compiled releases reaches 50%

Metadata

total number of distinct ocid for groups of buyers that have

1 ocid
2 - 20 ocids
21 - 50 ocids
51 - 100 ocids
100+

total number of ocids with identifiable buyer
reference to up to 20 compiled releases belonging to buyers with only one ocid

buyer.repetition.md
Short description

Get a number of distinct ocid's per buyer (identified by buyer.identifier.scheme and buyer.identifier.id)
Check if the share of the largest buyer on a total number of compiled releases is 1% < share < 50%

Details
This check can be evaluated only if a dataset contains at least 1000 resources that have both fields buyer.identifier.id and buyer.identifier.scheme set
Otherwise, the check is N/A

Get a total number of distinct ocid from a dataset

get only ocid that has identifiable buyer (buyer.identifier.id and buyer.identifier.scheme is set)

Get a number of distinct ocid per buyer.

buyer is identified by a unique combination of buyer.identifier.id and buyer.identifier.scheme

The check passes if

number of distinct ocid for a buyer with the highest number of distinct ocid is

bigger than 0,01 x total number of distinct ocid with identifiable buyer
lower than 0,5 x total number of distinct ocid with identifiable buyer

The check fails

if the share of the biggest buyer on the total number of compiled releases is not within interval <1%-50%)

Metadata

for the biggest buyer

buyer.identifier.id and buyer.identifier.scheme
number of compiledReleases belonging to this buyer
share on total number of distinct compiled releases with an identifiable buyer

total number of distinct compiled releases with an identifiable buyer
reference to up to 20 compiled releases belonging to the biggest buyer

CODE.distribution.md
Short description

Check frequencies of distinct values of enum field.
Return 0 if any of input values has frequency outside 0.1 % - 99 % range

Details
This check works with fields that have a restricted number of values. Some of those values can be selected and tested whether its presence in a dataset has a frequency from the interval <0.1% - 99%>.
It is not obligatory that at least one value must be tested. In such case, the check will always pass and the information we'll get is a distribution of enumeration values.
The check pass if

all input values have a share from interval <0.1% - 99%>
or
if there is no input value

The check fails if

share of at least one of the input values is outside the interval <0.1% - 99%>

The check is N/A

if there is no value to be tested

The value of this check is

100% if it passes
0% if it fails

Metadata

share of all enum values
reference to up to 20 sample resources for each detected value with a share higher than 0%

RelatedProcess.identifier.reference.md
Short description
If its scheme is ocid, then its identifier value matches the ocid of another compiled release
Details
Collect all instances of #/definitions/RelatedProcess from OCDS schema that have scheme set to ocid. Such instances can appear in

all instances in relatedProcesses
all instances in contracts[i].relatedProcesses

This check passes

if all related processes exist within a dataset. This means for each relatedProcess there exists a compiled release that has ocid equal to relatedProcess.identifier

This check fails

if the dataset does not contain all the relatedProcesses

This check is N/A

if there is no #/definitions/RelatedProcess instance

The value of this check is

(100 * number of existing relatedProcesses)/total count of tested instances

Metadata

up to 100 identification of tested instances of #/definitions/RelatedProcess for both results pass and fail
for each example it's result

failed/passed

total number of tester instances
total number of instances that passed
total number of instances that failed

RelatedProcess.title.consistent.md
Short description
If its scheme is ocid, and its identifier value matches the ocid of another compiled release, then its title value is equal to the tender.title of the match
Details

Search for pairs of processes that are related.
take all instances of #/definitions/RelatedProcess from OCDS schema that have scheme set to ocid

search in relatedProcesses
search in contracts[i].relatedProcesses

find its related process in a dataset

Two processes are related when relatedProcess.identifier of one equals ocid of another.

for each pair of related processes test whether their titles equals

This check passes

if all pairs of related processes have equal titles

This check fails

if at least one pair of related processes do not have equal titles

This check is N/A

if there is no pair of related processes in a dataset

The value of this check is

(100 * number of pairs with equal titles)/total count of tested pairs of related processes

Metadata

up to 100 pairs of ocid for both results pass and fail
for each example it's result

failed/passed

total number of tester pairs
total number of pairs that passed
total number of pairs that failed

supplier.distribution.md
Short description

Get a number of distinct ocid's per supplier (identified by awards[i].suppliers[j].identifier.scheme and awards[i].suppliers[j].identifier.identifier.id)
Check if the share of the largest supplier is 1 % < share < 50 % of all OCIDs
Check if the total share of all suppliers with 1 ocid only is 0 % < share < 50 % of all OCIDs

Details
This check can be evaluated only if a dataset contains at least 1000 resources that contain at least one supplier that has both fields identifier.id and identifier.scheme set
Otherwise, the check is N/A

Get a total number of suppliers from a dataset
*
Get a number of distinct ocid per supplier.

supplier is identified by a unique combination of buyer.identifier.id and buyer.identifier.scheme

The check passes

number of distinct ocid for a buyer with the highest number of distinct ocid is

bigger than 0,01 x total number of distinct ocid from a dataset
lower than 0,5 x total number of distinct ocid from a dataset

total count of distinct ocid of all buyers with only 1 ocid is lower than 0,5 x total number of distinct ocid from a dataset

The check fails

if at least one of the two above-described rules for passage fails

Metadata

total number of distinct ocid for groups of buyers that have

1 ocid
2 - 20 ocids
21 - 50 ocids
51 - 100 ocids
100+

reference to up to 20 compiled releases belonging to buyers with only one ocid
reference to up to 20 compiled releases belonging to the buyer with the highest number of ocids

tender.id.unique.md
Short description
tender.id is unique within the whole dataset
Details

for each compiled release verify that its tender.id is unique within the dataset
such releases that do not have tender.id set are excluded from this calculation

The check will pass if

100% tender ids are unique

The check will fail if

there is at least one id that occurs at least twice

This check is N/A

if there is no compiled release having tender.id set

The value of this check is

(100*number of compiled releases with unique tender.id)/(number of compiled releases with tender.id set)

Metadata

up to 100 sample tender.id values that occurred more than once and ocids that contains given duplicated tender.id

tender.mainProcurementCategory.distribution.md
Short description
No value of tender.mainProcurementCategory occurs more than 95 % of the time.
Details

calculate a share of all distinct non-empty and not null values present in tender.mainProcurementCategory

The check pass if

none of the values occurs in more than 95%

The check fails if

exists one value that occurs in more than 95%

The check is N/A

if tender.mainProcurementCategory is present in zero compiledReleases

The value of this check is

100% if it passes
0% if it fails

Metadata

share of all distinct values present in tender.mainProcurementCategory
reference to 100 sample resources that represents a category with most frequent tender.mainProcurementCategory

URL.availability.md
Short description
A random sample of X values is taken and tested whether a GET request for each URL returns a non-error HTTP status (e.g. 2XX, 3XX).
Details

select X (let's start with 100) random URLs from following arrays

planning.documents
tender.documents
awards[i].documents
contracts[i].documents
contracts.implementation.documents.url

try a GET request for a given URL and store whether this call was succesfull or not

This check passes

if all GET requests finish successfully

This check fails

if at least one GET request fails

This check is N/A

if there is less then X URLs in the whole dataset

The value of this check is

(100*number of successful requests)/X

Metadata

identification of all tested URLs and resources to which particular URL belongs
result of a GET request

faile/passed

value.distribution.md
This algorithm evaluates a distribution of instances of objects of type $ref: "#/definitions/Value from OCDS schema

get a set of instances of type $ref: "#/definitions/Value
convert all values to USD using compiled releases date field

if the date field is not present for a compiled release then those values that are not in USD are excluded from the calculation
if the currency is missing then such value is excluded from the calculation
if the amount is missing then such value is excluded from the calculation

calculate a total amount of all values as sum(value.amount in USD)
sort values by the amount in descending order
calculate a share for

top 1% of values
(1% - 5%> of values
(5% - 20%> of values
(20% - 50%> of values
(50% - 100%> of values

the above mentioned percentage is related to a sequence number not to a value

for example when we have 100 values and both the 5th and 6th is 100$ then the 5th goes to the interval (1% - 5%> and the 6th goes to the interval (5% - 20%>

The check will pass if

the share for top 1% of values is less than 50% of the total amount

The check will fail if

the share for top 1% of values is bigger or equal to 50% of the total amount

The value of this check is

100% if it passes
0% if it fails

Metadata

share on the total value for each interval
sample of 10 tender ids from each interval and path to a specific contract value

value.repetition.md
This algorithm evaluates a distribution of instances of objects of type $ref: "#/definitions/Value from OCDS schema

get a set of instances of type $ref: "#/definitions/Value

if the amount is missing then such value is excluded from the calculation
if the currency is missing then such value is excluded from the calculation

calculate a frequency of occurrence of 3 most frequent value.amount and value.currency combinations

This check will pass if

overall frequency of top 3 combinations is less than 10%

This check will fail if

overall frequency of top 3 combinations is 10% or more

Metadata

frequency of occurrence of 3 most frequent value.amount and value.currency combinations
up to ten representatives (compiled releases) of all three critical combinations

Time-based
ocid.persistent.md
This check controls whether all ocid present in the old version of the dataset is also present in the new version.

take all ocid from the old version of the dataset
one by one check that the ocid is present in the new version of the dataset
each comparison passes if the ocid is present in both versions of the dataset

The check passes

if the value of the check is 100%

phase.stable.md
This check controls that each OCID in the new dataset has the same or higher number of planning, tender, awards and contracts objects than in the old dataset.

take all ocid from the old version of the dataset
if the ocid is present in the new version check that

planning exist in the new version if it existed in the old version
tender exist in the new version if it existed in the old version
size of awards in the new version is higher or equal to the size of awards in the old version
size of contracts in the new version is higher or equal to the size of cotnracts in the old version

the comparison fails if at least one of the above-described comparisons fails

The check passes

if the value of the check is 100% or higher

tender.title.stable.md
This check controls whether all ocid present in both the old and new version of the dataset has a stable 'tender.title'

take all ocid from the old version of the dataset
if the ocid is present in the new version of the dataset and both have tender.title set

compare both values
the comparison is considered successful if both standardized values equal

the standardization removes all white spaces and converts everything to lower case

The check passes

if the value of the check is 95% or higher

Noting that no check matching supplier.distribution.md was implemented.


Loading a capture hangs the app

Description
When loading a specific capture file, RenderDoc, at first it seems normal. I can switch between tabs, and I see the progress bar at the bottom constantly showing movement. But when I click on one of the events on the left, everything hangs.
Steps to reproduce

Load  wgpu-player-capture-bug.zip
Click on the "Color Pass #1"

The diagnostic log complains about nonCoherentAtomSize not being respected, but I'm not seeing in the app code where it would be the case. Not sure if it's related.
Environment

RenderDoc version: 1.7 rev a56af589d94dc851809fd5344d0ae441da70c1f2
Operating System: Linux
Graphics API: Vulkan

The log lists 2 GPUs, not sure which one RenderDoc is using:

Core     PID 188431: [23:07:24]  vk_device_funcs.cpp(1356) - Log     - physical device 0: Intel(R) UHD Graphics 630 (Coffeelake 3x8 GT2) (ver 19.3 patch 0x4) - 8086:3e9b
Core     PID 188431: [23:07:24]  vk_device_funcs.cpp(1356) - Log     - physical device 1: GeForce GTX 1050 Ti with Max-Q Design (ver 440.64 patch 0x0) - 10de:1c8c

Just double-checked that running the same app on either of the GPUs I have is totally validation-free. So I wonder if these flush errors come from RenderDoc itself?

I'm not able to reproduce this unfortunately. On the closest hardware I could get running the same mesa version I'm able to open the capture and see things working as I'd expect.
One thing I noticed which seems quite strange and might have something to do with the problem is that memory which is allocated and only bound to optimal tiled images (the color/depth attachments) is mapped and has writes to it in the frame. Since these images aren't in a host-accessible format those writes seem like they're invalid and might cause problems. FWIW it looks like the errors you see are due to RenderDoc mapping coherent map writes into flushes for the sake of serialisation.
Are you able to reproduce the problem on a capture without those optimal tiled images having their memory mapped?

Huh, we by no means are trying to map that memory (used for render attachments). It would make little sense:) We only map (some of the) buffer memory.
Are you sure that is something our application does, and not RenderDoc itself? I'll definitely double check on our end.

Yes indeed it stood out to me for that reason :). I can't check without being able to reproduce the capture side, but this is recorded as an application map write and I don't see any way it could be caused by RenderDoc.

I double checked and didn't find us mapping textures. What we do, however, is mapping any memory that is CPU-visible on allocation. This never applies to textures in practice, because we prefer non-cpu-visible memory types for them.
It must have something to do with the way RenderDoc exposes different memory types to us. Could it be the case that all the memory types you are exposing are CPU-visible? We'd then be mapping it, but not doing anything with that memory on CPU side.
If you are seeing any writes to that memory, that's especially strange. Would it be possible if the memory types you are exposing are just happen to support both buffers and textures? We'd then end up sub-allocating all of them from the same memory type, and you'd see writes to this memory that are caused by our buffer writes, unrelated to the textures.

FWIW it looks like the errors you see are due to RenderDoc mapping coherent map writes into flushes for the sake of serialisation.

Is that a known issue on your side? Would be good to get fixed in order to avoid confusing the users about these validation errors.

RenderDoc doesn't have anything to do with the memory types that are exposed, that comes from the driver itself. This capture is using the intel GPU which only exposes two memory types - both are CPU visible.
It's possible RenderDoc is detecting writes to the memory because the GPU is modifying that memory. It's not possible for me to know where such a write came from, so it will be recorded either way and then replayed as a CPU write.
I'll need to think about how/if this can be solved, it likely won't be easy to fix. I'd recommend in the meantime only mapping memory you intend to modify from the CPU so that memory being modified by the GPU isn't visible to the CPU while RenderDoc is capturing it.

the GPU is modifying that memory

Yes, GPU is modifying the render attachment memory.

I'd recommend in the meantime only mapping memory you intend to modify from the CPU so that memory being modified by the GPU isn't visible to the CPU while RenderDoc is capturing it.

Thank you for the suggestion, filed https://github.com/gfx-rs/gfx-extras/issues/12
Looking forward to a solution you can find, if any, on your side.

That commit will skip flushed memory writes to memory that only has tiled images bound to it. It will not work if there's aliasing with linear images or buffers, and I haven't been able to test if this really fixes the problem since I wasn't able to reproduce it.
It also comes with a performance penalty if it has to process in this way rather than memcpy'ing directly so I'd still strongly recommend not mapping memory regions you're using for GPU-only images.


Impossible to only run a dynamically generated test

I'm working inside of a very large mocha test suite with hundreds of tests, so having the ability to run a single test using .only is extremely useful during test development.
However, as far as I can tell, there's no way to mark a dynamically generated test suite as being the only one that runs. I'd really like to write some dynamically generated tests, and it's hard to run all the tests every time. Am I missing something? Is there a pattern you might suggest to get around this issue?
I expected there might be something like:
mocha = new Mocha
suite = Mocha.Suite.create mocha.suite, config.name
suite.only()
mocha.run()

I have stumbled across this pattern, but it only runs the first of my dynamically generated tests
describe.only config.name, ->
  it 'should run tests', ->
     mocha = new Mocha
     ...stuff...
     mocha.run()

I don't understand why only doesn't work.  please supply more code

IMO, if you have 6 describe.only blocks, dynamically generated or not, all 6 should run not just the first one.
Otherwise, if you want only the first registered describe.only to be run, then Mocha should throw an error if there is more than one describe.only.
Pick one.

One year and no feedback. For future reference, use --grep to filter out relevant tests from the command line

Also, for the record, multiple only (including on suites) has already been made well-defined in 3.x: https://mochajs.org/#exclusive-tests

--grep  will be difficult to do for tests with dynamically generated names?


Checkpoint

Add error 'checkpoint' record to output dataframe. Created automatic Springer secondary loop to meet request limits.

Resolved error directory conflict. Merge checkpoint branch with main


feat: added boolean to get_trajectories and get_last_point methods in experiment entity to toggle assertion for simulation completion

Jira - https://modelonproducts.atlassian.net/browse/FLOW-544

As discussed on teams, I have modified the code to remove checks for simulation completion from experiment entity api's.


Add 'config' option to specify different kubectl configs

My team uses multiple config files and I thought I'd see if you'd be open to adding support to facilitate this approach: by adding a 'config' option to allow users to specify a non-default kubectl config file.
I'm not a python dev and brand new to this project, so apologies in advance if I've trampled over some guidelines/best-practices

Codecov Report

Merging #38 into master will increase coverage by 0.39%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master      #38      +/-   ##
==========================================
+ Coverage   50.92%   51.32%   +0.39%
==========================================
  Files          10       10
  Lines         377      378       +1
  Branches       46       46
==========================================
+ Hits          192      194       +2
  Misses        181      181
+ Partials        4        3       -1

Impacted Files
Coverage Δ

src/kubetop/_script.py
0% <0%> (ø)
:arrow_up:

src/kubetop/_textrenderer.py
82.87% <0%> (+1.36%)
:arrow_up:

Continue to review full report at Codecov.

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

Great, thank you!


fromBeginning option doesn't seem to be working

I'm not entirely sure what fromBeginning is supposed to do, and there don't seem to be tests for it; but what I'm trying to do is have the tail.on('line', callback) be fired once for each line in a given file when the on is first registered, then call it once for each following line that is appended.
Here's what I've got:
        for (const filename of files) {
            let t = new Tail(filename, {fromBeginning: true});
            // Each time a new line comes in, send it along
            t.on("line", function(line){
                console.log(line);
                callback(line);
            });
        }

Passing the option doesn't seem to be changing anything at all, could someone please explain how it's supposed to work? Thanks!

fromBeginning tells the library to do exactly what you are looking for, i.e. start tailing from the beginning of the file rather than the first line appended. But what you highlighted is an actual bug, thanks for that. I'll try to release a new version with the bug fix over the next few days.

Thanks for this, this is affecting me too. Any chance of publishing a new version so we can starting using it? :)

fixed with v 1.0.1


Support "masks", a.k.a. "exclusion regions"?

Sometimes parts of the image should be ignored, e.g. because there is missing or invalid data.
One way to signal these "exclusion regions" to the convolution method is to give an extra mask image [1],
another method is to use magic values.
Using NaN is especially popular for float images, see e.g. [2].
Let's see if we need this or if it is enough that the user simply multiplies her image with an exclusion mask (zeroing out the parts she doesn't want) before handing it to ringtophat.
[1] http://docs.scipy.org/doc/numpy/reference/routines.ma.html
[2] https://github.com/astropy/astropy/pull/155

In the current version, the map is an integer array, and for most applications negative values won't occur anyway (at least not on gamma maps). So what do you think about defining the positive range of an int as data and the negative range as mask?
If negative values are needed, then let's just use the MIN_INT (or MIN_LONG) as magic value. Accessing the mask each time would be slow, I think.


fix: 4206 - search page misalignment in search-history_view.dart (#4210)

Impacted file:
search-history_view.dart: added padding to the list tile for proper alignment Resolved the misalignment issue on the search page by adding appropriate padding to the list tile in the search-history_view.dart file. This adjustment ensures that the elements within the list are properly aligned, improving the visual consistency of the search page.
What

Added padding to the list tile in the search-history_view.dart file to achieve proper alignment.
This adjustment ensures that the elements within the list are properly aligned, improving the visual consistency of the search page.

Screenshot

Fixes bug(s)

Fixes: #4206 search page history tiles are misaligned

Part of

#4206

Sorry mb, I will make the necessary changes
Does this look good?

Far better 👍

Hey, I have made the changes. Can you verify?

Almost perfect, the Ripple effect should take the full width:
Search.webm

Added the ripple effect to the complete List tile. Please verify and let me know if there are any other changes.

The fix is done ig. It is ready to merge

It seems that there is still an issue: https://share.waldo.com/294ab6ee641dd9f72e008124c281df26024024?tab=timeline&startTime=39.688
As you can see, the Ripple around the pen (Edit mode) is really small. There should be some padding

Did the fix!


Model events are only triggered once

If I have a feature with a single scenario that triggers model events (saving) everything is good.
If I run this feature with other tests or have few scenarios in the same feature - only the first one triggers the model event, rest are ignored.
Example (always works if only this feature file is called):
Scenario: paid invoice does have enough payments
    Given I have a "paid" invoice
    When I remove payments so that the total is not covered
    Then invoices totals should match isPaid field value

Example 2 (first scenario works, second does not):
Scenario: unpaid invoice does not have enough payments
   Given I have an "unpaid" invoice
   When I add payments so that the total is covered
   Then invoices totals should match isPaid field value

Scenario: paid invoice does have enough payments
   Given I have a "paid" invoice
   When I remove payments so that the total is not covered
   Then invoices totals should match isPaid field value

Example 3 (same as 2 but switched - still first works, second does not):
Scenario: paid invoice does have enough payments
   Given I have a "paid" invoice
   When I remove payments so that the total is not covered
   Then invoices totals should match isPaid field value

Scenario: unpaid invoice does not have enough payments
   Given I have an "unpaid" invoice
   When I add payments so that the total is covered
   Then invoices totals should match isPaid field value

Had a similar issue. My problem was that I had multiple model files for the same resource. All of those files extended the BaseMyResourceModel class. I thought that BaseMyResourceModel::created() would trigger for all of the descendant models would inherit that event handler. But that is not the case. I had to pick out all the models...
MyResourceModel::created(...)
SameResourceInADifferentModule::created(...)

Not my case, I have simple Models, might have something to do with the way Events are triggered (I use separate Observer class)
Model file:
/**
 * Register observer
 */
public static function boot()
{
    parent::boot();

    self::observe(new ModelObserver);
}

and then in ModelObserver.php
/**
 * Update on every change
 */
public function saved($model) {
    ...
}

@bcat-eu did you find a solution to this? If not I will look into it.

@alnutile it started working after update to Laravel 5.2, I think the project had 5.0 at the time of the issue so it was resolved somewhere in between without much change on the behat extension's side. You can have a look if it works with older Laravel versions though

going to close this feel free to reopen if needed.
Not sure unless someone brings it up agains if it is worth me trying it in 5.0
I soon will tests running for each version 5.1 and higher


Add script to create Formulas for all Google Fonts

All open source Google Fonts are available here: https://github.com/google/fonts
This repository is grouped by license type. The three folders with fonts are:

apache/* under the Apache license
ofl/* under the Open Font License
ufl/* under the Ubuntu Font License

Each folder within these license folders contains a font set. e.g.
https://github.com/google/fonts/tree/master/ofl/notosans contains the "Noto Sans" font. It contains these files:

METADATA.pb: the metadata of this font in the ProtoBuffer format.
NotoSans-*.ttf the font files
OFL.txt the license file of this font.

This task is to create a script that can clone the Google Fonts repo, and for every font family, create a Fontist Formula for it that fills in the details.
The otfinfo command can be installed on macOS via brew install lcdf-typetools. This is the output for NotoSans-Regular.ttf:
otfinfo --info ../NotoSans-Regular.ttf
Family:              Noto Sans
Subfamily:           Regular
Full name:           Noto Sans
PostScript name:     NotoSans
Version:             Version 1.04
Unique ID:           Monotype Imaging - Noto Sans
Description:         Designed by Monotype design team
Designer:            Monotype Design team
Designer URL:        http://www.monotypeimaging.com/ProductsServices/TypeDesignerShowcase
Manufacturer:        Monotype Imaging Inc.
Vendor URL:          http://code.google.com/p/noto/
Trademark:           Noto is a trademark of Google Inc. and may be registered in certain jurisdictions.
Copyright:           Copyright 2012 Google Inc. All Rights Reserved.
License URL:         http://www.apache.org/licenses/LICENSE-2.0
License Description: Licensed under the Apache License, Version 2.0
Vendor ID:           MONO

From this output, we can create the Fontist Formula and provide these details: Family, Subfamily, Version, Designer, Designer URL, Vendor URL, Copyright, License URL and License Description.
i.e. NotoSans will be represented by this formula: googlefonts/notosans.rb (because the repo uses the path fonts/ofl/notosans).
module Fontist
  module Formulas
    class NotoSansFont < FontFormula

      fullname = "Noto Sans"  # This is from METADATA.pb "name:"
      cleanname = "NotoSans" # This is name with no spaces

      desc fullname
      homepage "http://code.google.com/p/noto/"  # From otfinfo

      resource "#{cleanname}.zip" do
        # NOTE: This URL is common for all Google Fonts
        url "https://fonts.google.com/download?family=Noto%20Sans"
        sha256 "..."
      end

      provides_font(fullname, match_styles_from_file: {
        # NOTE: This information is from METADATA.pb
        # TODO: update this structure after implementation of #109
        "Italic" => "NotoSans-Italic.ttf",
        "Regular" => "NotoSans-Regular.ttf",
        "Bold" => "NotoSans-Bold.ttf",
        "BoldItalic" => "NotoSans-BoldItalic.ttf"
      })

      def extract
        resource("#{cleanname}.zip") do |resource|
          zip_extract(resource) do |fontdir|
            match_fonts(fontdir, fullname)
          end
        end
      end

      def install
        case platform
        when :macos
          install_matched_fonts "$HOME/Library/Fonts/#{cleanname}"
        when :linux
          install_matched_fonts "/usr/share/fonts/truetype/#{cleanname.downcase}"
        end
      end

      test do
        case platform
        when :macos
          assert_predicate "$HOME/Library/Fonts/#{cleanname}/NotoSans-Regular.ttf", :exist?
        when :linux
          assert_predicate "/usr/share/fonts/truetype/#{cleanname.downcase}/NotoSans-Regular.ttf", :exist?
        end
      end

      # This is from METADATA.pb "copyright:"
      copyright "Copyright 2012 Google Inc. All Rights Reserved."

      # From otfinfo "License URL"
      # Notice this font is a MISMATCH -- the font itself uses the Apache 2.0 license,
      # but the Google Font site shows OFL license.
      license_url "http://www.apache.org/licenses/LICENSE-2.0"

      # From GitHub repo folder `fonts/ofl/notosans/OFL.txt
      open_license <<~EOS
        Copyright 2012 Google Inc. All Rights Reserved.

This Font Software is licensed under the SIL Open Font License,
Version 1.1.
...
      EOS
  end
end

This is necessary for https://github.com/metanorma/metanorma-ogc/issues/174

This depends on #109 .

Handled by @alexeymorozov, thanks!

Most formulas merged, remaining ones detailed in #122

Closing now.


feat: add WorkspaceStopped method to RoutingSolver

Signed-off-by: David Kwon<EMAIL_ADDRESS>What does this PR do?
Adds a func (s *ClusterSolver) WorkspaceStopped(routing *controllerv1alpha1.DevWorkspaceRouting, workspaceMeta DevWorkspaceMetadata) error method to RoutingSolver interface. This function runs when the corresponding devworkspace has stopped.
What issues does this PR fix or reference?
This PR was created to help support https://github.com/eclipse-che/che-operator/pull/1386
Is it tested? How?

Check out this branch: https://github.com/dkwon17/devworkspace-operator/tree/workspacestoppedtesting
This branch contains the same commit as this current PR's branch, except that there is a new commit on top of it with a print statement that can be used for testing.
After checking out the above branch, run the code locally by following these instructions: https://github.com/devfile/devworkspace-operator#run-controller-locally
Run the following to create a devworkspace in the devworkspace-controller namespace from the devworkspace samples:

kubectl apply -f samples/theia-latest.yaml -n devworkspace-controller

Stop the devworkspace by setting spec.started to false.

In the output from the terminal used to run DWO from step 2, verify that the we see the print statement:

PR Checklist

[ ] E2E tests pass (when PR is ready, comment /test v8-devworkspace-operator-e2e, v8-che-happy-path to trigger)

[ ] v8-devworkspace-operator-e2e: DevWorkspace e2e test
[ ] v8-che-happy-path: Happy path for verification integration with Che

For more context, the approach for https://github.com/eclipse-che/che-operator/pull/1386 is that the traefik config is updated when the devworkspace stops. The traefik config is updated so that the mainurl for the workspace is routed to the dashboard.
I use the WorkspaceStopped method in that PR: https://github.com/eclipse-che/che-operator/blob/a8cbf103af1a108fab4d10d53b8fd1255dbaa7e2/controllers/devworkspace/solver/solver.go#L200-L206 so that I can provision new traefik config when the workspace has stopped.

@dkwon17 it's up to you -- if there's no intention of merging this PR at the moment it can be closed and re-implemented later if need be.

Sounds good, I will close for now


Fix Linting Issue

Fix for #539

@sdras any updates here? this should resolve the CI issue.

thanks!


Context propagates wrongly => wrong error message

The “context” is persisting into the checking of the body of the “else” branch, but not being reset.
Therefor we get too specific error message:

[x] Reproduce in test
[ ] fix context propagation

similar case:

Arg this destroyed this case:

@dsyme:
One of the issues is:
// f x
| SynExpr.App (hpa,_,func,arg,mFuncAndArg) ->
    TcExprThen cenv overallTy env tpenv func ((DelayedApp (hpa, arg, mFuncAndArg)):: delayed)

we want to keep the context for the result type check, but erase for x and for whaterver happens inside of f.

I think what we actually want to do is not set a context here at all. We just

something like:
            let tempty = NewInferenceType ()
            let e3',tpenv = TcExprThatCanBeCtorBody cenv tempty env tpenv e3

            let env = { env with eContextInfo = ContextInfo.ElseBranch }
            UnifyTypes cenv env m overallTy tempty

instead of:
            let env = { env with eContextInfo = ContextInfo.ElseBranch }
            let e3',tpenv = TcExprThatCanBeCtorBody cenv overallTy env tpenv e3

looks like https://github.com/Microsoft/visualfsharp/pull/1827#issuecomment-262790519 is not enough since it forces us for type hints: cb3fa24

and there are coming more.
@dsyme is there another way to let the context only work for the return type check?

That sort of implementation looks much more robust (once it's green)

Ok this strategy didn't work, but now I think we can do this:
            let env = { env with eContextInfo = ContextInfo.ElseBranchResult e3.Range }
            let e3',tpenv = TcExprThatCanBeCtorBody cenv overallTy env tpenv e3
            e3',SequencePointAtTarget,tpenv

and at the error reporting site we check if the type error comes from the right range. that's basically narrowing the context to a minimum.

This is how it felt:

But I think this is now the correct strategy and my manual checks are all working.

 But tbf I assume
most "original authors" are the initial OSS commit anyways.
Am 24.11.2016 9:23 nachm. schrieb "Matthias Dittrich" <
<EMAIL_ADDRESS>@matthid commented on this pull request.
In src/fsharp/CompileOps.fs
https://github.com/Microsoft/visualfsharp/pull/1827:

       (if m.StartLine <> m2.StartLine then

          os.Append(SeeAlsoE().Format (stringOfRange m))  |> ignore)

 | ConstraintSolverTypesNotInEqualityRelation(denv,t1,t2,m,m2) ->

     // REVIEW: consider if we need to show _cxs (the type

parameter constrants)

 | ConstraintSolverTypesNotInEqualityRelation(denv,t1,t2,m,m2,contextInfo)

->

     // REVIEW: consider if we need to show _cxs (the type

parameter constraints)
I mean if I ever go across a comment like this I might want to talk with
the original author (which would be you now). But that was really just a
suggestion, as one can figure it out with multiple git calls as well ...
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/visualfsharp/pull/1827, or mute the thread
https://github.com/notifications/unsubscribe-auth/AADgNBdr6Cf9IdICkDFiGL0jqIuwV4NMks5rBfJdgaJpZM4K7YlH
.

This is fixed as well 👍

this is ready for review. I had to disable the nice async error message for now since the range where the exception happens is inside the "return" part. So that can't be found right now. I leave that for F# 4.2
But this is now removign all the false positive warnings and should be merged to FCS as soon as possible since Ionide and Xamarin Studio? (cc @Krzysztof-Cieslak @nosami) are already using it.

All green. Yay. Finally


List file behavior differs from Get file

When listing files in a repo, if multiple files of the same name coexist (We will definitely discourage this behavior and promote a healthy way for datums to write into files - by requesting one unique filename per datum), the list file lists each of the identical files and augments the info with a TAG to help disambiguate.
This is sub-optimal for several reasons:

Displaying the TAG implies that this behavior is normalized which it is not. It can lead to potentially disastrous behaviors in the downstream pipelines and should be avoided at all costs.
We do not have the ability to retrieve the content of those files anyway since the get file aggregates the content of all identical files.

You should probably display one file per path in the list file and add a clear warning when we detect that multiple files with the same name coexist.

Going to check with @brycemcanally but I think we can close this because it won't be possible for the user to get into this situation.

Confirmed with @brycemcanally, closing. We should remove the TAG field of the list file output, there might just be a single commit which can be reverted that contains the change.


add ref to manager when disabled prop goes from true to false

This fixes an issue for when a SortableElement goes from a disabled to a non-disabled state.

Ah, good catch. Thanks for submitting this! Looks good, though I believe you missed the case for when the prop goes from enabled to disabled though no?

@clauderic oops, did not think to handle that since it was the other way that was broken for me. Does this look OK for handling both cases? Have not had a chance to test yet.

@clauderic any thoughts on this? would be nice to get this merged so I can stop using my fork.

Hey @wmdmark, sorry I didn't get back to you. There's another PR to the same effect (https://github.com/clauderic/react-sortable-hoc/pull/34), I'm undecided as to which implementation I prefer, but I will merge one of the two as soon as I get the chance

I just merged #34, going to close this out. Thank you for submitting this.


Incompatibility with fastload.

Try for yourself... You should be stuck on loading world screen indefinitely.

I am also using version beta10 btw


add example flows to project

Added in https://github.com/pedesen/node-red-contrib-zeebe/commit/94309d0f910ff9bd7e269f201eef18b49a0c6c7f


Supported version must be between 2 and 2 inclusive

wget https://github.com/EOSIO/eos/releases/download/v1.8.0-rc2/eosio-1.8.0-rc2.el7.x86_64.rpm
sudo yum install eosio-1.8.0-rc2.el7.x86_64.rpm
nodeos --genesis-json genesis.json
nodeos --delete-all-blocks --snapshot snapshots/snapshot-038fbd95fc268eec34ea53b1903935fa871d95934754988119e4a39204e86
bdc.bin
error 2019-05-24T03:34:54.609 nodeos    main.cpp:120                  main                 ] 3240001 snapshot_validation_exce
ption: Snapshot Validation Exception
Unsupported version of chain snapshot: 1. Supported version must be between 2 and 2 inclusive.
{"version":1,"min":2,"max":2}
nodeos  chain_snapshot.hpp:31 validate
{}
nodeos  chain_plugin.cpp:989 plugin_startup

It looks to me like you're using a snapshot from version 1.7 or earlier.  These are not compatible with 1.8

Matthew is correct -- snapshots pre-1.8 cannot be loaded in 1.8. The wording for this error is a little wonky but for 2.0.0 this will be "between 2 and 3" so not worth changing the wording at this point either.

why the snapshot doesn't compatible with 1.8?have any other ideal to solve this?

Please review the 1.8 release candidate release notes.
You should get  a snapshot created on version 1.8.

eos1.8 snapshots download from https://snapshots.eossweden.org/


Added default sizes attribute to articles promos

What is this PR trying to achieve?
Reduce the page size by providing sizes attribute to images
What does it look like?
Before:

After:

Is it not worth looking at the logic here rather - surely 'default' should be in the else statement rather than elif?

Default refers to one of the 4 weights we have: lead, standalone, default and supporting, rather than a fallback default in the case that nothing is specified.
It is confusing, do you think I should rename the weight type, to something like 'normal'?

I personally prefer default.
I think the misunderstanding is in the idea of the value being optional - which it doesn't feel like it should be.

Or maybe it should be optional - and we remove the "default" value?

No, I think you're right it probably shouldn't be optional, I'll amend the logic


[HOLD for payment 2024-10-17] Tracker: Patch and Bump for date-fns-tz

Description
This issue is a tracker for reverting the patch and bumping date-fns-tz to the version which contains our changes. For context, we created a PR to upstream here but we didn't get any feedback, so we are proceeding with creating a patch in Expensify here.
The ultimate goal is to revert the patch PR in Expensify, once PR to date-fns-tz is merged and available on NPM. Then we will have to bump date-fns-tz in Expensify.

The patch for date-fns-tz was merged and released in v3.2.0, I'll try to bump this version, but the peerDependency of this version is "date-fns" with versions "^3.0.0 || ^4.0.0", so date-fns should be also reviewed and bumped.

Do we need payment on this one? (Should I assign a BZ?) I think no, right?

hi @slafortune! @dukenv0307 reviewed the linked PR which was raised by one of our agencies. I think the standard $250 should be fine here!

Offer sent here @dukenv0307

Paid


Atom in WSL does not respect changing the windows drive root mount point

Description
If the mount point for windows drives in WSL is changed via editing /etc/wsl.conf, detailed here, atom no longer works to open windows directories/files that it once opened without issue.
Steps to Reproduce

Change WSL default windows drive mount points to anything other than /mnt/%drive_letter%.
This is done in the /etc/wsl.conf file, specified here
Navigate to a directory on the windows filesystem inside WSL. Eg /c/dev/
Run "atom ."

Expected behavior: Atom to open using the current directory
Actual behavior: Command line outputs "The system cannot find the path specified."
Reproduces how often: 100%
Versions
Windows 10 - 18.03 + WSL Ubuntu 18.04
Additional Information
Contents of /etc/wsl.conf are as follows:

[network]
generateResolvConf = false

[automount]
root = /
options = "metadata"

Thanks for the report (and for the pull request :v:)!  Reproduced on Windows 10 + Ubuntu 18.04 and Atom 1.29.


MSID: 88540 Version: 1 DOI: 10.1101/2<IP_ADDRESS>9533

MSID: 88540
Version: 1
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>9533
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=88540
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>9533

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/88540v1
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>9533
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/88540/v1/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

This is a v2 not a v1 (hence no message from the bot).
Package is present - s3://prod-elife-epp-meca/reviewed-preprints/88540-v2-meca.zip. I think this is good to check


Update findbugsExcludeFile.xml

NOTICE
Please create an issue in ASF JIRA before opening a pull request,
and you need to set the title of the pull request which starts with
the corresponding JIRA issue number. (e.g. HADOOP-XXXXX. Fix a typo in YYY.)
For more details, please see https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m  3s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

_ trunk Compile Tests _

+1 :green_heart:
shadedclient
22m  7s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
whitespace
0m  0s

The patch has no whitespace issues.

+1 :green_heart:
xml
0m  2s

The patch has no ill-formed XML file.

+1 :green_heart:
shadedclient
15m 31s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
asflicense
0m 29s

The patch does not generate ASF License warnings.

40m 52s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2376/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2376

Optional Tests
dupname asflicense xml

uname
Linux ad790fdad9d0 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 2de7240d4ff

Max. process+thread count
310 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs-httpfs U: hadoop-hdfs-project/hadoop-hdfs-httpfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2376/1/console

versions
git=2.17.1 maven=3.6.0

Powered by
Apache Yetus 0.13.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

Please create an issue in ASF JIRA before opening a pull request
Please do not modify the license header.

Closing as invalid.


XML output from Marshaller

I think there might be a problem with the array marshaller.
If you call the endpoint with "Accept: application/xml" , the XML response is syntactically correct, but the result is doubled. My guess would be replacing this:
Source.fromIterator(() ⇒ persons.iterator).mapAsync(1) { person ⇒
            Marshal(persons.map(person ⇒ PersonV2(person.name, person.age, person.married))).to[NodeSeq]
          }.map(ns ⇒ ByteString(ns.toString))

with this:
Source.fromIterator(() ⇒ persons.iterator).mapAsync(1) { person ⇒
            Marshal(PersonV2(person.name, person.age, person.married)).to[NodeSeq]
          }.map(ns ⇒ ByteString(ns.toString))

Basically I think you're going through the same iterator twice :)

Thanks for notifying me about this issue. I will look into it!


Object detection demo about coral dev board setup

Hi:
I encounter some error about build the Object detection demo for coral dev board.
Please give me some suggestion for this. Thank a lot!
https://github.com/google/mediapipe/tree/master/mediapipe/examples/coral
-- Issue 1:
if i add the following step, i would encounter the following error
==============================================================
Edit /edgetpu/WORKSPACE

update /mediapipe/WORKSPACE TENSORFLOW_* variables to match what /edgetpu/WORKSPACE has:

  grep TENSORFLOW_ /mediapipe/WORKSPACE
  grep TENSORFLOW_ /edgetpu/WORKSPACE

  #  Make sure the /mediapipe/WORKSPACE  _TENSORFLOW_GIT_COMMIT  and  _TENSORFLOW_SHA256
  #   match the /edgetpu/WORKSPACE  TENSORFLOW_COMMIT  and  TENSORFLOW_SHA256  respectively.

  # If they do not match, modify /mediapipe/WORKSPACE to match what /edgetpu/WORKSPACE has.
  # Also comment out the MediaPipe org_tensorflow patch section.
===============================================================

error:
===============================================================
DEBUG: Repository rules_foreign_cc instantiated at:
  /mediapipe/WORKSPACE:42:13: in <toplevel>
Repository rule http_archive defined at:
  /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/bazel_tools/tools/build_defs/repo/http.bzl:336:31: in <toplevel>
ERROR: error loading package '': cannot load '@org_tensorflow//tensorflow:workspace3.bzl': no such file
INFO: Elapsed time: 6.157s
================================================================

-- Issue 2:
If i don't modify issue-1 patches, i would encounter the following error.
error:
================================================================
Use --sandbox_debug to see verbose messages from the sandbox
mediapipe/calculators/tflite/tflite_inference_calculator.cc: In member function 'absl::lts_2020_09_23::Status mediapipe::TfLiteInferenceCalculator::LoadModel(mediapipe::CalculatorContext*)':
mediapipe/calculators/tflite/tflite_inference_calculator.cc:809:77: error: invalid conversion from 'const tflite::ops::builtin::BuiltinOpResolver*' to 'tflite::ops::builtin::BuiltinOpResolver*' [-fpermissive]
       BuildEdgeTpuInterpreter(model, op_resolver_ptr, edgetpu_context_.get());
==================================================================

Hi
I bypass the above issue and then fix rules_python issue by 749. But, i still encounter the following eigen3 issue.
Could you give some suggestion for this. Thank a lot!
command:
root@7b1f65f0196d:/mediapipe# bazel build -c opt --crosstool_top=@crosstool//:toolchains --compiler=gcc --cpu=aarch64 --define MEDIAPIPE_DISABLE_GPU=1 --copt -DMEDIAPIPE_EDGE_TPU --copt=-flax-vector-conversions mediapipe/examples/coral:object_detection_tpu

Error:
DEBUG: Repository rules_cc instantiated at:
  /mediapipe/WORKSPACE:36:13: in <toplevel>
Repository rule http_archive defined at:
  /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/bazel_tools/tools/build_defs/repo/http.bzl:336:31: in <toplevel>
ERROR: /mediapipe/mediapipe/framework/formats/BUILD:105:11: no such target '@eigen_archive//:eigen3': target 'eigen3' not declared in package '' (did you mean 'eigen'?) defined by /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/eigen_archive/BUILD.bazel and referenced by '//mediapipe/framework/formats:matrix'
ERROR: Analysis of target '//mediapipe/examples/coral:object_detection_tpu' failed; build aborted: Analysis failed

Hi @yishinhung, Your Issue1 is similar to this.   And for the error mentioned in the next comment, Please have a look at here. Thanks!

Hi @sgowroji :
The error maybe cause by the following steps because "comment out the MediaPipe org_tensorflow patch section" remove the section about alias eigen3 to eigen . I can't find the  eigen3 folder under the third_party.
Did you have any suggestion for this? Thank a lot!

./third_party/org_tensorflow_compatibility_fixes.diff

============================================================
diff --git a/third_party/eigen3/eigen_archive.BUILD b/third_party/eigen3/eigen_archive.BUILD
index dad592bec48..670017c2c0f 100644
--- a/third_party/eigen3/eigen_archive.BUILD
+++ b/third_party/eigen3/eigen_archive.BUILD
@@ -49,6 +49,13 @@ cc_library(
     visibility = ["//visibility:public"],
 )

+# For backward compatibility.
+alias(
+    name = "eigen",
+    actual=":eigen3",
+    visibility = ["//visibility:public"],
+)
+
===========================================================

Steps
Edit /edgetpu/WORKSPACE
update /mediapipe/WORKSPACE TENSORFLOW_* variables to match what /edgetpu/WORKSPACE has:
grep TENSORFLOW_ /mediapipe/WORKSPACE
grep TENSORFLOW_ /edgetpu/WORKSPACE
Make sure the /mediapipe/WORKSPACE  _TENSORFLOW_GIT_COMMIT  and  _TENSORFLOW_SHA256
match the /edgetpu/WORKSPACE  TENSORFLOW_COMMIT  and  TENSORFLOW_SHA256  respectively.
If they do not match, modify /mediapipe/WORKSPACE to match what /edgetpu/WORKSPACE has.
Also comment out the MediaPipe org_tensorflow patch section.
===============================================================
Error:
DEBUG: Repository rules_cc instantiated at:
  /mediapipe/WORKSPACE:36:13: in <toplevel>
Repository rule http_archive defined at:
  /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/bazel_tools/tools/build_defs/repo/http.bzl:336:31: in <toplevel>
**ERROR: /mediapipe/mediapipe/framework/formats/BUILD:105:11: no such target '@eigen_archive//:eigen3': target 'eigen3' not declared in package '' (did you mean 'eigen'?) defined by** /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/eigen_archive/BUILD.bazel and referenced by '//mediapipe/framework/formats:matrix'
ERROR: Analysis of target '//mediapipe/examples/coral:object_detection_tpu' failed; build aborted: Analysis failed

Hi @sgowroji :
I modify the eigen3 to eigen to bypass the build fail but i still encounter the following error.
Could you have any idea and suggestion for this? Thank a lot!
Error:
mediapipe/calculators/tflite/tflite_inference_calculator.cc: In member function 'absl::lts_2020_09_23::Status mediapipe::TfLiteInferenceCalculator::LoadModel(mediapipe::CalculatorContext*)':
mediapipe/calculators/tflite/tflite_inference_calculator.cc:795:25: error: 'BuiltinOpResolverWithoutDefaultDelegates' is not a member of 'tflite::ops::builtin'
   tflite::ops::builtin::BuiltinOpResolverWithoutDefaultDelegates
                         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
mediapipe/calculators/tflite/tflite_inference_calculator.cc:799:12: error: 'default_op_resolver' was not declared in this scope
           &default_op_resolver);
            ^~~~~~~~~~~~~~~~~~~
Target //mediapipe/examples/coral:object_detection_tpu failed to build

Hi @jiuqiant:
Did you have any idea for the build fail? I build the sample for coral board.
Thank al ot!

Hi @sgowroji :
I modify the eigen3 to eigen to bypass the build fail but i still encounter the following error.
Could you have any idea and suggestion for this? Thank a lot!
Error:
mediapipe/calculators/tflite/tflite_inference_calculator.cc: In member function 'absl::lts_2020_09_23::Status mediapipe::TfLiteInferenceCalculator::LoadModel(mediapipe::CalculatorContext*)':
mediapipe/calculators/tflite/tflite_inference_calculator.cc:795:25: error: 'BuiltinOpResolverWithoutDefaultDelegates' is not a member of 'tflite::ops::builtin'
   tflite::ops::builtin::BuiltinOpResolverWithoutDefaultDelegates
                         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
mediapipe/calculators/tflite/tflite_inference_calculator.cc:799:12: error: 'default_op_resolver' was not declared in this scope
           &default_op_resolver);
            ^~~~~~~~~~~~~~~~~~~
Target //mediapipe/examples/coral:object_detection_tpu failed to build

Hi @jiuqiant :
Did you have any idea for the build fail ? I build the sample for coral board.
Thank a lot!

@mcclanahoochie is the owner of coral examples. Reassign this issue to @mcclanahoochie.

Hi @jiuqiant :
Did you have any idea for the build fail ? I build the sample for coral board.
Thank a lot!

Hi @mcclanahoochie
Did you have any idea for the build fail ? I build the sample for coral board.
Thank a lot!

Hi @jiuqiant :
Did you have any idea for this issue?
Thank a lot!

the coral example setup has recently been updated,  https://github.com/google/mediapipe/blob/master/mediapipe/examples/coral/README.md
please try the new version

Hi @mcclanahoochie :

the coral example setup has recently been updated, https://github.com/google/mediapipe/blob/master/mediapipe/examples/coral/README.md
please try the new version

The new version can compiler the mediapipe samples for coral devices.
Thank for your help!


help ! who   provide   superbtc  version  Support  insight-api

who   provide     superbtc  version  Support  insight-api ?
LIKE  http://block.superbtc.org/
THK

Blockchain Browser?The third development
sbtc api is here

The insight explorer doesn't seem to have any parameters set for distribution supply. ie ?=gettotalbc or
?=getmoneysupply
Is this explorer set up to provide the total and free float supply with an api end-point rather than a calculation on the block height and coinbase tx.


Messages are being logged although logger is disabled

Environment

Ruby Version: 2.4.x
Rails Version. 4.2.x
Semantic Logger Version. 4.1
Rails Semantic Logger Version. 4.1.3
Other Application/framework names and versions (e.g. Puma, etc.) unicorn
Rails configuration: config.action_mailer.logger = nil

Basically if I set config.action_mailer.logger = nil I expect messages not to be logged at all.
Expected Behavior
Should not log messages if logging is disabled in app config 👌
Actual Behavior
Messages are being logged 😢

To change a logger instance so that it’s log messages do not show up, raise its log level beyond the current global level, for example :trace:
ActionMailer.logger.level = :trace

Hi @reidmorrison ! Thanks, I understand, probably it will work.
config.action_mailer.logger = nil is a Rails configuration where you tell the framework not to log certain messages coming from a certain framework.
Here's the rails guide about this config:

config.action_mailer.logger accepts a logger conforming to the interface of Log4r or the default Ruby Logger class, which is then used to log information from Action Mailer. Set to nil to disable logging.

rails_semantic_logger ignores this configuration and sets it to something else than nil, thus logging the messages.
This info should be added to the documentation somehow.


Error when sending confirmation e-mails

Hello everyone, I hope you are very well.
I have hung my pocketbase on an AWS instance, everything seems to be fine, but when I try to send confirmation and verification emails I get an error.
I get the following error:
Failed to send the test email. Raw error:
535 Authentication Failed.
Would anyone know what is going on? Thank you for your response.

The error message 535 Authentication Failed comes from the SMTP server you're using and means your credentials are invalid.
Check your server settings :)

@Jasics0 As the others mentioned, make sure to check that your credentials are valid and you are using the correct port (for TLS/STARTTLS that's usually 587).
I'll move the issue to Q&A discussion.