example shortcode: see if we can use a regex

https://github.com/twbs/bootstrap/blob/919b526f17a08cefba51c42b831c922adecb4a9f/site/layouts/shortcodes/example.html#L35-L38
The above basically extracts the class, removes bd-placeholder-img and bd-placeholder-img-lg.
I wonder if we can use findRE along with replaceRE to achieve the same thing.
Not a huge deal, it just feels like a more elegant solution.
Similarly we could try doing the same for:
https://github.com/twbs/bootstrap/blob/919b526f17a08cefba51c42b831c922adecb4a9f/site/layouts/shortcodes/example.html#L27-L29
This just extracts the <svg></svg>.

Something like this?
{{ replaceRE "<svg.*class=.bd\-placeholder\-img(.*?)".*?<\/svg>" `<img src="..." class="$1" alt="..." >` $content_chunk }}

I modified this a bit, I think this will work for all instances.
{{- $content_chunk = replaceRE `<svg.*class=.bd\-placeholder\-img(?:\-lg)?.?(?:bd\-placeholder\-img\-lg)?(.*?)".*?<\/svg>` `<img src="..." class="$1" alt="..." >` $content_chunk -}}

@morrissey-ingenious Can you make a PR and CC me, please?


Updated libsecp256k1 dependency

Removed all references to libsecp256k1 not >=0.5.0.
https://rustsec.org/advisories/RUSTSEC-2021-0076
e2e tests pass.

@alistair-singh do you know why github's bot didn't detect this and let us know? do we have it enabled? does it work well for Rust?

Actually libsecp256k1 is an unused dependency. We should remove it :)


Add skip button

Describe the addition

Context

The original skip button appeared to the right of the player after a few seconds. Clicking it would take the user directly to the next video, or the next point where buttons are displayed.
Proposed Solution

This is technically addressed but is being blocked by other issues, namely #33. Closing in favor of that issue


Updated Jackson-databind package version in the pom file.

Why you are committing in master. I think we have eng branch to map to pulse-dev eng

We don't have eng branch I will rename master to eng


add NameSilo as DNS provider for letsencrypt

Hi. Namesilo DNS registrar does have an api.
It should work just fine for letsencrypt.
Could u add namesilo to the officially supported list?

By the way, I was able to make namesilo work using the exec provider. It looks like this:
    dnsProvider:
    name: exec
    exec:
      EXEC_PATH: /configs/namesilo.sh
  domains:
    enabled: true
    domainsList:
      - main: "*.yourdomain.com"
      - sans:
        - "yourdomain.com"

configFiles:
  namesilo.sh: |
    #!/bin/sh
    export API_KEY=FUSRODAH
    export DOMAIN=$2
    export DOMAIN=$${DOMAIN//.yourdomain.com.}
    export PAYLOAD=$3

    echo "Got $2 and $3"

    if [ $1 == "present" ];
    then
        apk add curl
        curl "https://www.namesilo.com/api/dnsAddRecord?version=1&type=xml&key=$API_KEY&domain=yourdomain.com&rrhost=$DOMAIN&rrtype=TXT&rrvalue=$PAYLOAD&rrttl=7207"
    else
        echo 'lets pretend'
    fi


The default settings result in an unworkable library

Bug description
I created everything on standard settings. Connection to OpenAI and the Neo4j vector database.
Environment
Steps to reproduce
Create connection to OpenAI and create Neo4j vector database.
public EmbeddingModel embeddingModel() {
    return new OpenAiEmbeddingModel(new OpenAiApi(embeddingBaseUrl, embeddingApiKey), MetadataMode.EMBED, OpenAiEmbeddingOptions.builder().withModel(embeddingModel).build());
}

public Neo4jVectorStore neo4jVectorStore(Driver driver, EmbeddingModel embeddingModel) {
    return new Neo4jVectorStore(driver, embeddingModel, Neo4jVectorStoreConfig.defaultConfig(), true);
}

public List<Document> findSimilarContent(SimilarContentRequest request) {
    SearchRequest searchRequest = SearchRequest.query(request.getQuery())
            .withTopK(request.getTopK())
            .withFilterExpression(buildFilterExpression(request.getMetadata()));
    return vectorStore.similaritySearch(searchRequest);
}

org.neo4j.driver.exceptions.ClientException: Failed to invoke procedure `db.index.vector.queryNodes`: Caused by: java.lang.IllegalArgumentException: Index query vector has 3072 dimensions, but indexed vectors have 1536.

I've check using Neo4j Console
there is index spring-ai-document-index
so created by spring ai
with following settings:
{
"indexProvider": "vector-2.0",
"indexConfig": {
"vector.dimensions": 1536,
"vector.similarity_function": "COSINE"
}
}
so spring ai set the wrong index even though he had the embedding model in hand and couldn't put it together properly, causing the solution not to work
Expected behavior
When I use EmbeddingModel to create VectoreStore everything should be created correctly.
Correct indexes and probably other errors that I will come across

@ErykCh can you check latest M2 version to see if this is resolved?


Text in SVG elements is missing

Hello,
I'm using d3.js to draw an svg with lots of elements (60 to be exact). so basically it looks like:
    <div id="canvas">
        <svg>
            <g>
                <g class="node">
                    <circle></circle>
                    <text>Superstring I search for</text>
                </g>
                <g class="node"><circle></circle><text>some other text</text></g>
                      ...
                <g class="node"><circle></circle><text>some other text</text></g>
            </g>
        </svg>
    </div>

I'm using Ruby 1.9.3, Capybara 2.2.1, Poltergeist 1.5.0.
Here is my env.rb
require "rspec/expectations"
require "capybara/cucumber"
require "capybara/poltergeist"

  # DEFAULT: headless tests with poltergeist/PhantomJS
  Capybara.register_driver :poltergeist do |app|
    Capybara::Poltergeist::Driver.new(
      app,
      window_size: [1024, 768],
      phantomjs_options: ["--web-security=false"]
      #,debug:       true
    )
  end
  Capybara.default_driver    = :poltergeist
  Capybara.javascript_driver = :poltergeist

So in my step definition I'm doing:
Then /^page should have vertex with text "([^\"]*)"$/ do |text|
    page.should have_css("g.node text", text: text)
end

But the test fails with
Then page should have vertex with text "Superstring I search for" # features/step_definitions/smoke_test.rb:9
expected to find css "g.node text" with text "Superstring I search for" but there were no matches.
 (Capybara::ExpectationNotMet)

However, it passes, if I rewrite it to not look into svg at all:
Then /^page should have vertex with text "([^\"]*)"$/ do |text|
    page.first("div#canvas").should have_content text
end

Could you please advise?
Thanks!

Closing since this was fixed https://github.com/teampoltergeist/poltergeist/commit/3fc1f4e318ce34154036832bb9da2b70f66739da


CORS error :(

Hello,
when i try to execute, this is what i get
Access to fetch at 'https://twitter.com/i/api/graphql/[...]_download_video_enabled"%3Afalse%2C"responsive_web_enhance_cards_enabled"%3Afalse}' from origin 'https://x.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
Thanxs

I second this

Twitter was switched over to x.com as of May 17th 2024 which broke the script.
I was able to get it working by replacing all instances of twitter.com with x.com before copying it into the console.

I figured that could have happened, thanks!

thank you people

Twitter was switched over to x.com as of May 17th 2024 which broke the script. I was able to get it working by replacing all instances of twitter.com with x.com before copying it into the console.

I did this and I'm still getting the error:

Twitter was switched over to x.com as of May 17th 2024 which broke the script. I was able to get it working by replacing all instances of twitter.com with x.com before copying it into the console.

I did this and I'm still getting the error.

I think i found a fix for this. Go to your settings, and then my account. It'll prompt you to log in, so log in, then go back to your profile and try to use this code again. I just spent hours running various scenarios and it's finally working. I started off with the cors error. then some 403's and other various errors. Keep at it. it very much still works.

Twitter was switched over to x.com as of May 17th 2024 which broke the script. I was able to get it working by replacing all instances of twitter.com with x.com before copying it into the console.

I believe the script has already been updated with this.
What worked for me was by habit I was on twitter.com/my_handle. I updated my URL to x.com/my_handle and re-ran the script and it worked fine.

Access to fetch at 'https://x.com/i/api/graphql/uYU5M2i12UhDvDTzN6hZPg/UserTweetsAndReplies.......' from origin 'https://twitter.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

seems like it's happening again, even with x.com - anyone knows if they changed anything, I used the same script 4 days ago and was ok


docs: ✏ update comment in release.config

Changelog / Description
Remove copy pasta from the docker plugin comment
Checklist -

[ ] New Feature ?
[ ] Updated swagger annotation (if API structure is changed) ?
[ ] Unit Test (if possible) ?
[ ] Updated the Readme.md (if required) ?

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


Adds support for Activate Account password resets

What's this PR do?
Adds showResetForm to the ResetPasswordController to customize the Reset Password form when type query parameter includes activate-account.
How should this be reviewed?
Verify expected content for Forgot Password forms at /password/reset, as well as overrides for when the type query parameter includes activate-account.

Relevant Tickets
Fixes https://www.pivotaltracker.com/n/projects/2019429/stories/164780588
Checklist

[ ] Documentation added for changed endpoints.
[ ] Tests added for new features/bug fixes.
[ ] Post a message in #api if this includes something that causes a rebuild!

If you have time, it might be nice to add a simple testPasswordActivationFlow test to PasswordResetTest that checks that the correct copy is used for that flow.


Add Compliance Manager role

#1372 #1373
Added Compliance Manager role
Changelog:

Renamed Compliance Report Manager to Compliance Reporting
Added Compliance Manager for government

 Compliance Report | Create IDIR Compliance Manager Role |1|

 Compliance Report | Rename BCeID role to Compliance Reporting |1|


Apple M1 Support

As reported in sonata-system repo, using this to track M1 support.

Apple M1 mac support seems unreliable.
It seems to occur more often if the slot has a valid bitstream. It also looks like based on running ioreg -f -c IOUSBHostDevice that the entire USB hub gets disabled. Possibly device is disabled due to timeout during loading bitstream and/or power issue, testing now.

Main issue was TinyUSB intilization sequence. Fixed now, need to check bitstream programming from GUI.


Create examples for Go

In the Go SDK,  the examples are create in the xxxx_examples_test.go files.
Then godoc automatically picks them up and adds them to

https://pkg.go.dev/github.com/senzing/g2-sdk-go-base

References

https://github.com/senzing-garage/garage-roadmap/issues/8

Fixed via https://github.com/senzing-garage/sz-sdk-go-core/issues/232


Pinned offhand weapons and Force Doublehand interaction.

Identified by Sunsette, details from TMTL.
Load a fresh builder page, building Olive 7* for physical damage. Add Automatic pistols to the right hand, remove pin. Add Sparky (or any other weapon) off-hand, keep it pinned. Check Force Doublehand and then hit Build, and the build will never progress past 0%. This does not occur if you keep both weapons pinned.

This has been fixed by not allowing the build to start under these conditions.


Replace application name.

@rs-randallburt Casey wants application name to be changed, just a minor name change.


Tidy .pre-commit-config.yaml

Codecov Report

Merging #26 (e2788f8) into main (0a0d5ae) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #26   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines           27        25    -2
  Branches         8         8
=========================================
- Hits            27        25    -2

Impacted Files
Coverage Δ

src/tox_py.py
100.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


Relative references using $def are being URL encoded

We are using a $defs section in our schemas. Schemas within the $defs section are referenced via local file references, and these schemas can themselves have cross references to other files. The ref parser is correctly injecting a$defs cross-reference but replacing the $defs with %24defs (i.e. it is applying URL encoding). I don’t think this behaviour is correct: while $ is a reserved character in the URIs RFC, it is designated as a sub-delimiter
For example in the parent file:
{
  “properties”: {
     “foo”: “string”
  },
  ”$defs”: {
    “myschema”: {
       “$ref”: “./myschema.json”
    },
    ”otherschema”: {
       “$ref”: “./otherschema.json”
    }
  }
}

And the myschema.json file:
{
      “allOf”: [
        { “$ref”: “./otherschema.json” },
        {
           “properties”: {
              “someProp”: “string”
           }
        }
      ]
}

Flattening results in:
{
  “properties”: {
     “foo”: “string”
  },
  ”$defs”: {
    “myschema”: {
      “allOf”: [
        { “$ref”: “#/%24defs/otherschema.” },
        {
           “properties”: {
              “someProp”: “string”
            }
        }
      ]
    },
    ”otherschema”: {
         “properties”: {
            “otherProp”: “string”
         }
     }
  }
}

There was the same issue 262.

Note that this is occurring in v11.6.4. I haven’t updated to 11.7 yet.

It also seems like the $defs keyword of a schema is not handled like the previous keyword definitions, but since this is not enforced and the convention changed over time makes it really tricky.
Code dealing with "definitions"
https://github.com/search?q=repo%3AAPIDevTools%2Fjson-schema-ref-parser+definitions&type=code
Especially:
https://github.com/APIDevTools/json-schema-ref-parser/blob/27abe40702c18c02cae2ad9a0fdd5a33199d9154/lib/bundle.ts#L77
No matching code for "defs"
https://github.com/search?q=repo%3AAPIDevTools%2Fjson-schema-ref-parser+defs&type=code
However, not really related to the encoding of $ in json-pointers.


Investigate potential DevEx issue

Problem
Currently we do not have all the necessary pre-checks mapped 1-1 with what a normal RPC will behave. Some of the checks are executed at consensus time, which means that the relay will be returning a "success" response code out of the sendRawTransaction call.
Investigate what happens to the client-side applications in the case in which the transaction fails at consensus time that would otherwise fail on precheck (f.e balance is not sufficient for gas cost, gas limit to low etc. Prechecks are listed in #102 )
Solution
The output of this issue is expected to be a description on what happens on client side and will be used to asses how "important" is the addition/implementation of those prechecks.

We aligned checks.
Relay now utilizes precheck.ts to cover some sanity transaction checks prior to submission.
Success is only returned once a transaction has gone E2E


Schema.org annotations for HTML export

The HTML export should (optionally) be annotated with the NewsArticle Schema.

There's actually no need to implement this as part of the gem. The page that renders the article can just use wrapping elements to annotate properly.


What accounts for an index status vs. db-file-size discrepancy ?

On two servers I have an index file of the same size, but one on Server 1 ord index is at 367160/777506 while on Server 2 its 776831/777507.
du -s --block=GB  ./.local/share/ord/index.redb on both servers returns 31GB.
Server 1 was fully indexed yesterday morning. I think ord preview or ord server caused it to regress.
So my question is: what would cause this discrepancy? Is it surely isolated to values in index.redb ?

Also: is there a way to determine "indexing status" outside of the main index process? I'd like to keep track of its progress from a separate process...

After applying the latest master with #1759 merged :
server 1 (custom logs)
ubuntu@ip-172-31-15-165:~$ RUST_LOG=info ord --bitcoin-data-dir=/var/lib/bitcoind index
[2023-02-20T20:18:12Z INFO  ord::index] Connecting to Bitcoin Core RPC server at <IP_ADDRESS>:8332/wallet/ord using credentials from `/var/lib/bitcoind/.cookie`
[2023-02-20T20:18:12Z INFO  ord::index] entering database
[2023-02-20T20:42:49Z INFO  ord::index] in database
[2023-02-20T20:42:49Z INFO  ord::index::updater] Block 777446 at 2023-02-20 05:33:56 UTC with 2199 transactions…

ubuntu@ip-172-31-15-165:~$ du -s --block=GB .local/share/ord
43GB	.local/share/ord

server 2
ubuntu@ip-172-31-17-189:~/ord$ RUST_LOG=info ord --bitcoin-data-dir=/var/lib/bitcoind index
[2023-02-20T20:01:33Z INFO  ord::index] Connecting to Bitcoin Core RPC server at <IP_ADDRESS>:8332/wallet/ord using credentials from `/var/lib/bitcoind/.cookie`
[2023-02-20T20:18:03Z INFO  ord::index::updater] Block 777530 at 2023-02-20 19:15:27 UTC with 2102 transactions…
[2023-02-20T20:18:10Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 7339 ms

ubuntu@ip-172-31-17-189:~$ sudo du -s --block=GB  ./.local/share/ord/index.redb
31GB	./.local/share/ord/index.redb

And both are now synced.
Server 1 has an index.redb that is 12GB larger. I wonder if this is due to ord preview (see https://github.com/casey/ord/issues/1484 ) having run there ?
Server 1 took 24 minutes to "enter the database" on a c6a.8xlarge while server 2 took 17 minutes on a t2.medium1 (much wimpier specs) . Strange behavior.

On a c6a.8xlarge with the latest master ( 9f46f0854055551fe26f4729d9636c0d025ef322 )
ubuntu@ip-172-31-15-165:~$ RUST_LOG=info ord --bitcoin-data-dir=/var/lib/bitcoind index
[2023-02-22T02:06:16Z INFO  ord::index] Connecting to Bitcoin Core RPC server at <IP_ADDRESS>:8332/wallet/ord using credentials from `/var/lib/bitcoind/.cookie`
[2023-02-22T02:06:16Z INFO  ord::index] entering database
[2023-02-22T02:06:16Z INFO  ord::index] in database
[2023-02-22T02:06:22Z INFO  ord::index::updater] Block 777538 at 2023-02-20 20:59:31 UTC with 2951 transactions…
[2023-02-22T02:06:29Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 7485 ms
[2023-02-22T02:06:35Z INFO  ord::index::updater] Block 777539 at 2023-02-20 21:02:42 UTC with 1195 transactions…
[2023-02-22T02:06:40Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 5390 ms
[2023-02-22T02:06:44Z INFO  ord::index::updater] Block 777540 at 2023-02-20 21:06:28 UTC with 2225 transactions…
[2023-02-22T02:06:48Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 3671 ms
[2023-02-22T02:06:49Z INFO  ord::index::updater] Block 777541 at 2023-02-20 21:14:32 UTC with 1653 transactions…
[2023-02-22T02:06:51Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 2027 ms
[2023-02-22T02:06:55Z INFO  ord::index::updater] Block 777542 at 2023-02-20 21:16:59 UTC with 2090 transactions…
[2023-02-22T02:06:59Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 4014 ms
[2023-02-22T02:07:02Z INFO  ord::index::updater] Block 777543 at 2023-02-20 21:20:48 UTC with 1143 transactions…
[2023-02-22T02:07:06Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 3593 ms
[2023-02-22T02:07:07Z INFO  ord::index::updater] Block 777544 at 2023-02-20 21:26:11 UTC with 1270 transactions…
[2023-02-22T02:07:09Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1439 ms
[2023-02-22T02:07:12Z INFO  ord::index::updater] Block 777545 at 2023-02-20 21:27:04 UTC with 956 transactions…
[2023-02-22T02:07:14Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 2829 ms
[2023-02-22T02:07:17Z INFO  ord::index::updater] Block 777546 at 2023-02-20 21:48:30 UTC with 3429 transactions…
[2023-02-22T02:07:20Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 2913 ms
[2023-02-22T02:07:25Z INFO  ord::index::updater] Block 777547 at 2023-02-20 21:48:41 UTC with 991 transactions…
[2023-02-22T02:07:29Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 4412 ms
[2023-02-22T02:07:32Z INFO  ord::index::updater] Block 777548 at 2023-02-20 22:50:06 UTC with 2893 transactions…
[2023-02-22T02:07:34Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 2496 ms
[2023-02-22T02:07:37Z INFO  ord::index::updater] Block 777549 at 2023-02-20 22:52:10 UTC with 3125 transactions…
[2023-02-22T02:07:39Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 2437 ms
[2023-02-22T02:07:42Z INFO  ord::index::updater] Block 777550 at 2023-02-20 22:54:43 UTC with 2548 transactions…
[2023-02-22T02:07:45Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 2769 ms
[2023-02-22T02:07:47Z INFO  ord::index::updater] Block 777551 at 2023-02-20 22:58:39 UTC with 2658 transactions…
[2023-02-22T02:07:49Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1935 ms
[2023-02-22T02:07:50Z INFO  ord::index::updater] Block 777552 at 2023-02-20 23:01:52 UTC with 1559 transactions…
[2023-02-22T02:07:52Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1604 ms
[2023-02-22T02:07:54Z INFO  ord::index::updater] Block 777553 at 2023-02-20 23:13:34 UTC with 2229 transactions…
[2023-02-22T02:07:56Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1995 ms
[2023-02-22T02:07:58Z INFO  ord::index::updater] Block 777554 at 2023-02-20 23:19:27 UTC with 1251 transactions…
[2023-02-22T02:08:01Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 2524 ms
[2023-02-22T02:08:02Z INFO  ord::index::updater] Block 777555 at 2023-02-20 23:31:29 UTC with 1984 transactions…
[2023-02-22T02:08:04Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1476 ms
[2023-02-22T02:08:06Z INFO  ord::index::updater] Block 777556 at 2023-02-20 23:50:43 UTC with 2416 transactions…
[2023-02-22T02:08:08Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1972 ms
[2023-02-22T02:08:09Z INFO  ord::index::updater] Block 777557 at 2023-02-21 00:02:35 UTC with 2411 transactions…
[2023-02-22T02:08:11Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1982 ms
[2023-02-22T02:08:16Z INFO  ord::index::updater] Block 777558 at 2023-02-21 00:03:22 UTC with 588 transactions…
[2023-02-22T02:08:20Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 4118 ms
[2023-02-22T02:08:21Z INFO  ord::index::updater] Block 777559 at 2023-02-21 00:11:00 UTC with 1658 transactions…
[2023-02-22T02:08:22Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1566 ms
[2023-02-22T02:08:25Z INFO  ord::index::updater] Block 777560 at 2023-02-21 00:16:35 UTC with 1282 transactions…
[2023-02-22T02:08:27Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 2254 ms
[2023-02-22T02:08:31Z INFO  ord::index::updater] Block 777561 at 2023-02-21 00:22:32 UTC with 909 transactions…
[2023-02-22T02:08:34Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 3773 ms
[2023-02-22T02:08:35Z INFO  ord::index::updater] Block 777562 at 2023-02-21 00:27:03 UTC with 990 transactions…
[2023-02-22T02:08:36Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 809 ms
[2023-02-22T02:08:36Z INFO  ord::index::updater] Block 777563 at 2023-02-21 00:28:00 UTC with 320 transactions…
[2023-02-22T02:08:36Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 177 ms
[2023-02-22T02:08:38Z INFO  ord::index::updater] Block 777564 at 2023-02-21 01:03:46 UTC with 2902 transactions…
[2023-02-22T02:08:40Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1906 ms
[2023-02-22T02:08:42Z INFO  ord::index::updater] Block 777565 at 2023-02-21 01:05:09 UTC with 1862 transactions…
[2023-02-22T02:08:44Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 2154 ms
[2023-02-22T02:08:46Z INFO  ord::index::updater] Block 777566 at 2023-02-21 01:10:26 UTC with 1098 transactions…
[2023-02-22T02:08:47Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1540 ms
[2023-02-22T02:08:49Z INFO  ord::index::updater] Block 777567 at 2023-02-21 01:27:13 UTC with 2402 transactions…
[2023-02-22T02:08:51Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1957 ms
[2023-02-22T02:08:54Z INFO  ord::index::updater] Block 777568 at 2023-02-21 01:35:50 UTC with 1339 transactions…
[2023-02-22T02:08:57Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 3052 ms
[2023-02-22T02:08:57Z INFO  ord::index::updater] Block 777569 at 2023-02-21 01:36:26 UTC with 261 transactions…
[2023-02-22T02:08:57Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 201 ms
[2023-02-22T02:08:58Z INFO  ord::index::updater] Block 777570 at 2023-02-21 02:01:14 UTC with 2780 transactions…
[2023-02-22T02:09:00Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1353 ms
[2023-02-22T02:09:03Z INFO  ord::index::updater] Block 777571 at 2023-02-21 02:03:42 UTC with 805 transactions…
[2023-02-22T02:09:06Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 3282 ms
[2023-02-22T02:09:07Z INFO  ord::index::updater] Block 777572 at 2023-02-21 02:14:43 UTC with 1647 transactions…
[2023-02-22T02:09:08Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 978 ms
[2023-02-22T02:09:09Z INFO  ord::index::updater] Block 777573 at 2023-02-21 02:19:02 UTC with 701 transactions…
[2023-02-22T02:09:09Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 440 ms
[2023-02-22T02:09:11Z INFO  ord::index::updater] Block 777574 at 2023-02-21 02:23:10 UTC with 629 transactions…
[2023-02-22T02:09:13Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1905 ms
[2023-02-22T02:09:13Z INFO  ord::index::updater] Block 777575 at 2023-02-21 02:25:53 UTC with 465 transactions…
[2023-02-22T02:09:13Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 328 ms
[2023-02-22T02:09:14Z INFO  ord::index::updater] Block 777576 at 2023-02-21 02:28:45 UTC with 538 transactions…
[2023-02-22T02:09:14Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 289 ms
[2023-02-22T02:09:14Z INFO  ord::index::updater] Block 777577 at 2023-02-21 02:29:59 UTC with 214 transactions…
[2023-02-22T02:09:14Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 146 ms
[2023-02-22T02:09:15Z INFO  ord::index::updater] Block 777578 at 2023-02-21 02:41:43 UTC with 1410 transactions…
[2023-02-22T02:09:15Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 676 ms
[2023-02-22T02:09:16Z INFO  ord::index::updater] Block 777579 at 2023-02-21 02:50:32 UTC with 1376 transactions…
[2023-02-22T02:09:17Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 908 ms
[2023-02-22T02:09:19Z INFO  ord::index::updater] Block 777580 at 2023-02-21 03:05:59 UTC with 1953 transactions…
[2023-02-22T02:09:21Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 2058 ms
[2023-02-22T02:09:23Z INFO  ord::index::updater] Block 777581 at 2023-02-21 03:07:17 UTC with 257 transactions…
[2023-02-22T02:09:25Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1810 ms
[2023-02-22T02:09:27Z INFO  ord::index::updater] Block 777582 at 2023-02-21 03:12:52 UTC with 843 transactions…
[2023-02-22T02:09:28Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1572 ms
[2023-02-22T02:09:28Z INFO  ord::index::updater] Block 777583 at 2023-02-21 03:14:25 UTC with 297 transactions…
[2023-02-22T02:09:28Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 230 ms
[2023-02-22T02:09:29Z INFO  ord::index::updater] Block 777584 at 2023-02-21 03:16:07 UTC with 343 transactions…
[2023-02-22T02:09:29Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 269 ms
[2023-02-22T02:09:31Z INFO  ord::index::updater] Block 777585 at 2023-02-21 03:24:13 UTC with 1049 transactions…
[2023-02-22T02:09:33Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 2139 ms
[2023-02-22T02:09:33Z INFO  ord::index::updater] Block 777586 at 2023-02-21 03:25:34 UTC with 293 transactions…
[2023-02-22T02:09:34Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 248 ms
[2023-02-22T02:09:35Z INFO  ord::index::updater] Block 777587 at 2023-02-21 04:10:13 UTC with 2159 transactions…
[2023-02-22T02:09:36Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1012 ms
[2023-02-22T02:09:37Z INFO  ord::index::updater] Block 777588 at 2023-02-21 04:41:24 UTC with 3040 transactions…
[2023-02-22T02:09:38Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1354 ms
[2023-02-22T02:09:40Z INFO  ord::index::updater] Block 777589 at 2023-02-21 04:47:31 UTC with 2038 transactions…
[2023-02-22T02:09:42Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1634 ms
[2023-02-22T02:09:43Z INFO  ord::index::updater] Block 777590 at 2023-02-21 05:00:19 UTC with 2206 transactions…
[2023-02-22T02:09:44Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1073 ms
[2023-02-22T02:09:44Z INFO  ord::index::updater] Block 777591 at 2023-02-21 05:00:30 UTC with 1160 transactions…
[2023-02-22T02:09:45Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 737 ms
[2023-02-22T02:09:46Z INFO  ord::index::updater] Block 777592 at 2023-02-21 05:09:59 UTC with 1313 transactions…
[2023-02-22T02:09:46Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 678 ms
[2023-02-22T02:09:49Z INFO  ord::index::updater] Block 777593 at 2023-02-21 05:11:52 UTC with 754 transactions…
[2023-02-22T02:09:51Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 2344 ms
[2023-02-22T02:09:53Z INFO  ord::index::updater] Block 777594 at 2023-02-21 05:12:54 UTC with 543 transactions…
[2023-02-22T02:09:55Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 2065 ms
[2023-02-22T02:09:56Z INFO  ord::index::updater] Block 777595 at 2023-02-21 05:47:02 UTC with 2577 transactions…
[2023-02-22T02:09:57Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1158 ms
[2023-02-22T02:09:58Z INFO  ord::index::updater] Block 777596 at 2023-02-21 05:52:31 UTC with 881 transactions…
[2023-02-22T02:09:59Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 980 ms
[2023-02-22T02:10:00Z INFO  ord::index::updater] Block 777597 at 2023-02-21 05:52:41 UTC with 989 transactions…
[2023-02-22T02:10:01Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1043 ms
[2023-02-22T02:10:02Z INFO  ord::index::updater] Block 777598 at 2023-02-21 05:59:39 UTC with 1672 transactions…
[2023-02-22T02:10:02Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 451 ms
[2023-02-22T02:10:03Z INFO  ord::index::updater] Block 777599 at 2023-02-21 06:13:39 UTC with 1205 transactions…
[2023-02-22T02:10:04Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 917 ms
[2023-02-22T02:10:05Z INFO  ord::index::updater] Block 777600 at 2023-02-21 06:21:50 UTC with 1592 transactions…
[2023-02-22T02:10:05Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 858 ms
[2023-02-22T02:10:06Z INFO  ord::index::updater] Block 777601 at 2023-02-21 06:23:07 UTC with 989 transactions…
[2023-02-22T02:10:07Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 801 ms
[2023-02-22T02:10:08Z INFO  ord::index::updater] Block 777602 at 2023-02-21 06:40:12 UTC with 2780 transactions…
[2023-02-22T02:10:10Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1809 ms
[2023-02-22T02:10:12Z INFO  ord::index::updater] Block 777603 at 2023-02-21 07:06:36 UTC with 3175 transactions…
[2023-02-22T02:10:14Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1817 ms
[2023-02-22T02:10:15Z INFO  ord::index::updater] Block 777604 at 2023-02-21 07:24:17 UTC with 3322 transactions…
[2023-02-22T02:10:17Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1732 ms
[2023-02-22T02:10:18Z INFO  ord::index::updater] Block 777605 at 2023-02-21 07:27:11 UTC with 1662 transactions…
[2023-02-22T02:10:18Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 875 ms
[2023-02-22T02:10:20Z INFO  ord::index::updater] Block 777606 at 2023-02-21 07:38:52 UTC with 2020 transactions…
[2023-02-22T02:10:21Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1350 ms
[2023-02-22T02:10:22Z INFO  ord::index::updater] Block 777607 at 2023-02-21 07:59:09 UTC with 2686 transactions…
[2023-02-22T02:10:24Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1125 ms
[2023-02-22T02:10:25Z INFO  ord::index::updater] Block 777608 at 2023-02-21 08:08:54 UTC with 1679 transactions…
[2023-02-22T02:10:26Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 969 ms
[2023-02-22T02:10:27Z INFO  ord::index::updater] Block 777609 at 2023-02-21 08:12:26 UTC with 1720 transactions…
[2023-02-22T02:10:29Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1306 ms
[2023-02-22T02:10:29Z INFO  ord::index::updater] Block 777610 at 2023-02-21 08:17:06 UTC with 1236 transactions…
[2023-02-22T02:10:30Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 814 ms
[2023-02-22T02:10:33Z INFO  ord::index::updater] Block 777611 at 2023-02-21 08:25:18 UTC with 1664 transactions…
[2023-02-22T02:10:35Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 2467 ms
[2023-02-22T02:10:37Z INFO  ord::index::updater] Block 777612 at 2023-02-21 08:26:04 UTC with 380 transactions…
[2023-02-22T02:10:38Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1387 ms
[2023-02-22T02:10:38Z INFO  ord::index::updater] Block 777613 at 2023-02-21 08:27:42 UTC with 322 transactions…
[2023-02-22T02:10:38Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 124 ms
[2023-02-22T02:10:40Z INFO  ord::index::updater] Block 777614 at 2023-02-21 08:36:15 UTC with 1705 transactions…
[2023-02-22T02:10:42Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1785 ms
[2023-02-22T02:10:42Z INFO  ord::index::updater] Block 777615 at 2023-02-21 08:37:13 UTC with 259 transactions…
[2023-02-22T02:10:42Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 142 ms
[2023-02-22T02:10:43Z INFO  ord::index::updater] Block 777616 at 2023-02-21 09:05:41 UTC with 3742 transactions…
[2023-02-22T02:10:45Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1416 ms
[2023-02-22T02:10:46Z INFO  ord::index::updater] Block 777617 at 2023-02-21 09:08:50 UTC with 2417 transactions…
[2023-02-22T02:10:48Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1434 ms
[2023-02-22T02:10:51Z INFO  ord::index::updater] Block 777618 at 2023-02-21 09:11:32 UTC with 864 transactions…
[2023-02-22T02:10:54Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 2851 ms
[2023-02-22T02:10:55Z INFO  ord::index::updater] Block 777619 at 2023-02-21 09:30:59 UTC with 3293 transactions…
[2023-02-22T02:10:57Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1969 ms
[2023-02-22T02:10:59Z INFO  ord::index::updater] Block 777620 at 2023-02-21 09:43:55 UTC with 2649 transactions…
[2023-02-22T02:11:00Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1591 ms
[2023-02-22T02:11:02Z INFO  ord::index::updater] Block 777621 at 2023-02-21 09:43:48 UTC with 957 transactions…
[2023-02-22T02:11:04Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1639 ms
[2023-02-22T02:11:04Z INFO  ord::index::updater] Block 777622 at 2023-02-21 09:46:44 UTC with 811 transactions…
[2023-02-22T02:11:04Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 280 ms
[2023-02-22T02:11:06Z INFO  ord::index::updater] Block 777623 at 2023-02-21 09:53:30 UTC with 1601 transactions…
[2023-02-22T02:11:08Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1875 ms
[2023-02-22T02:11:09Z INFO  ord::index::updater] Block 777624 at 2023-02-21 10:04:53 UTC with 1552 transactions…
[2023-02-22T02:11:09Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 709 ms
[2023-02-22T02:11:10Z INFO  ord::index::updater] Block 777625 at 2023-02-21 10:15:46 UTC with 2431 transactions…
[2023-02-22T02:11:11Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 992 ms
[2023-02-22T02:11:12Z INFO  ord::index::updater] Block 777626 at 2023-02-21 10:24:29 UTC with 2710 transactions…
[2023-02-22T02:11:13Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1044 ms
[2023-02-22T02:11:14Z INFO  ord::index::updater] Block 777627 at 2023-02-21 11:08:58 UTC with 3872 transactions…
[2023-02-22T02:11:16Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1127 ms
[2023-02-22T02:11:17Z INFO  ord::index::updater] Block 777628 at 2023-02-21 11:16:01 UTC with 3899 transactions…
[2023-02-22T02:11:19Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1516 ms
[2023-02-22T02:11:20Z INFO  ord::index::updater] Block 777629 at 2023-02-21 11:23:35 UTC with 2536 transactions…
[2023-02-22T02:11:21Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1423 ms
[2023-02-22T02:11:24Z INFO  ord::index::updater] Block 777630 at 2023-02-21 11:23:46 UTC with 1223 transactions…
[2023-02-22T02:11:26Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 2460 ms
[2023-02-22T02:11:28Z INFO  ord::index::updater] Block 777631 at 2023-02-21 11:27:59 UTC with 1156 transactions…
[2023-02-22T02:11:29Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1213 ms
[2023-02-22T02:11:31Z INFO  ord::index::updater] Block 777632 at 2023-02-21 11:36:56 UTC with 2184 transactions…
[2023-02-22T02:11:32Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1588 ms
[2023-02-22T02:11:34Z INFO  ord::index::updater] Block 777633 at 2023-02-21 11:47:37 UTC with 2484 transactions…
[2023-02-22T02:11:36Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1916 ms
[2023-02-22T02:11:37Z INFO  ord::index::updater] Block 777634 at 2023-02-21 12:14:08 UTC with 2865 transactions…
[2023-02-22T02:11:37Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 615 ms
[2023-02-22T02:11:38Z INFO  ord::index::updater] Block 777635 at 2023-02-21 12:37:51 UTC with 3755 transactions…
[2023-02-22T02:11:40Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1083 ms
[2023-02-22T02:11:41Z INFO  ord::index::updater] Block 777636 at 2023-02-21 12:40:02 UTC with 2040 transactions…
[2023-02-22T02:11:42Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1006 ms
[2023-02-22T02:11:42Z INFO  ord::index::updater] Block 777637 at 2023-02-21 12:44:59 UTC with 2415 transactions…
[2023-02-22T02:11:43Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 883 ms
[2023-02-22T02:11:44Z INFO  ord::index::updater] Block 777638 at 2023-02-21 13:02:26 UTC with 2995 transactions…
[2023-02-22T02:11:45Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 810 ms
[2023-02-22T02:11:46Z INFO  ord::index::updater] Block 777639 at 2023-02-21 13:29:12 UTC with 3736 transactions…
[2023-02-22T02:11:47Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1087 ms
[2023-02-22T02:11:48Z INFO  ord::index::updater] Block 777640 at 2023-02-21 13:32:31 UTC with 2185 transactions…
[2023-02-22T02:11:49Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 933 ms
[2023-02-22T02:11:50Z INFO  ord::index::updater] Block 777641 at 2023-02-21 13:37:02 UTC with 2494 transactions…
[2023-02-22T02:11:51Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1019 ms
[2023-02-22T02:11:51Z INFO  ord::index::updater] Block 777642 at 2023-02-21 13:37:48 UTC with 793 transactions…
[2023-02-22T02:11:52Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 250 ms
[2023-02-22T02:11:52Z INFO  ord::index::updater] Block 777643 at 2023-02-21 13:39:34 UTC with 1208 transactions…
[2023-02-22T02:11:53Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 682 ms
[2023-02-22T02:11:55Z INFO  ord::index::updater] Block 777644 at 2023-02-21 13:41:54 UTC with 1192 transactions…
[2023-02-22T02:11:57Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 2136 ms
[2023-02-22T02:12:01Z INFO  ord::index::updater] Block 777645 at 2023-02-21 13:44:40 UTC with 1148 transactions…
[2023-02-22T02:12:04Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 3483 ms
[2023-02-22T02:12:05Z INFO  ord::index::updater] Block 777646 at 2023-02-21 13:52:47 UTC with 2033 transactions…
[2023-02-22T02:12:07Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1352 ms
[2023-02-22T02:12:08Z INFO  ord::index::updater] Block 777647 at 2023-02-21 13:58:37 UTC with 1413 transactions…
[2023-02-22T02:12:09Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 882 ms
[2023-02-22T02:12:09Z INFO  ord::index::updater] Block 777648 at 2023-02-21 13:58:57 UTC with 1 transactions…
[2023-02-22T02:12:09Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 0 ms
[2023-02-22T02:12:10Z INFO  ord::index::updater] Block 777649 at 2023-02-21 14:01:31 UTC with 926 transactions…
[2023-02-22T02:12:12Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1524 ms
[2023-02-22T02:12:12Z INFO  ord::index::updater] Block 777650 at 2023-02-21 14:04:05 UTC with 658 transactions…
[2023-02-22T02:12:12Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 370 ms
[2023-02-22T02:12:13Z INFO  ord::index::updater] Block 777651 at 2023-02-21 14:07:52 UTC with 1107 transactions…
[2023-02-22T02:12:13Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 401 ms
[2023-02-22T02:12:15Z INFO  ord::index::updater] Block 777652 at 2023-02-21 14:12:52 UTC with 1447 transactions…
[2023-02-22T02:12:16Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1534 ms
[2023-02-22T02:12:16Z INFO  ord::index::updater] Block 777653 at 2023-02-21 14:14:47 UTC with 605 transactions…
[2023-02-22T02:12:17Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 254 ms
[2023-02-22T02:12:17Z INFO  ord::index::updater] Block 777654 at 2023-02-21 14:19:33 UTC with 1363 transactions…
[2023-02-22T02:12:17Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 420 ms
[2023-02-22T02:12:19Z INFO  ord::index::updater] Block 777655 at 2023-02-21 14:22:14 UTC with 730 transactions…
[2023-02-22T02:12:20Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1402 ms
[2023-02-22T02:12:21Z INFO  ord::index::updater] Block 777656 at 2023-02-21 14:40:00 UTC with 3417 transactions…
[2023-02-22T02:12:23Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1105 ms
[2023-02-22T02:12:24Z INFO  ord::index::updater] Block 777657 at 2023-02-21 14:43:24 UTC with 1480 transactions…
[2023-02-22T02:12:25Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1301 ms
[2023-02-22T02:12:27Z INFO  ord::index::updater] Block 777658 at 2023-02-21 14:49:38 UTC with 1929 transactions…
[2023-02-22T02:12:28Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1326 ms
[2023-02-22T02:12:30Z INFO  ord::index::updater] Block 777659 at 2023-02-21 14:52:44 UTC with 896 transactions…
[2023-02-22T02:12:32Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1717 ms
[2023-02-22T02:12:32Z INFO  ord::index::updater] Block 777660 at 2023-02-21 14:56:27 UTC with 1021 transactions…
[2023-02-22T02:12:33Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 794 ms
[2023-02-22T02:12:34Z INFO  ord::index::updater] Block 777661 at 2023-02-21 15:06:43 UTC with 2616 transactions…
[2023-02-22T02:12:36Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1298 ms
[2023-02-22T02:12:38Z INFO  ord::index::updater] Block 777662 at 2023-02-21 15:12:55 UTC with 1680 transactions…
[2023-02-22T02:12:39Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1816 ms
[2023-02-22T02:12:41Z INFO  ord::index::updater] Block 777663 at 2023-02-21 15:14:45 UTC with 401 transactions…
[2023-02-22T02:12:42Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1232 ms
[2023-02-22T02:12:43Z INFO  ord::index::updater] Block 777664 at 2023-02-21 15:40:36 UTC with 3660 transactions…
[2023-02-22T02:12:44Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1047 ms
[2023-02-22T02:12:45Z INFO  ord::index::updater] Block 777665 at 2023-02-21 15:50:55 UTC with 3029 transactions…
[2023-02-22T02:12:46Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1112 ms
[2023-02-22T02:12:47Z INFO  ord::index::updater] Block 777666 at 2023-02-21 16:07:07 UTC with 2568 transactions…
[2023-02-22T02:12:48Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 732 ms
[2023-02-22T02:12:48Z INFO  ord::index::updater] Block 777667 at 2023-02-21 16:10:27 UTC with 947 transactions…
[2023-02-22T02:12:49Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 388 ms
[2023-02-22T02:12:49Z INFO  ord::index::updater] Block 777668 at 2023-02-21 16:20:39 UTC with 3050 transactions…
[2023-02-22T02:12:50Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 847 ms
[2023-02-22T02:12:51Z INFO  ord::index::updater] Block 777669 at 2023-02-21 16:33:35 UTC with 2985 transactions…
[2023-02-22T02:12:52Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1017 ms
[2023-02-22T02:12:53Z INFO  ord::index::updater] Block 777670 at 2023-02-21 16:43:26 UTC with 2801 transactions…
[2023-02-22T02:12:54Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 796 ms
[2023-02-22T02:12:55Z INFO  ord::index::updater] Block 777671 at 2023-02-21 16:50:05 UTC with 2767 transactions…
[2023-02-22T02:12:56Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 956 ms
[2023-02-22T02:12:57Z INFO  ord::index::updater] Block 777672 at 2023-02-21 16:55:34 UTC with 2415 transactions…
[2023-02-22T02:12:57Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 850 ms
[2023-02-22T02:12:58Z INFO  ord::index::updater] Block 777673 at 2023-02-21 17:06:44 UTC with 2516 transactions…
[2023-02-22T02:12:59Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 828 ms
[2023-02-22T02:13:00Z INFO  ord::index::updater] Block 777674 at 2023-02-21 17:11:13 UTC with 2798 transactions…
[2023-02-22T02:13:01Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 904 ms
[2023-02-22T02:13:02Z INFO  ord::index::updater] Block 777675 at 2023-02-21 17:18:55 UTC with 2473 transactions…
[2023-02-22T02:13:03Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 799 ms
[2023-02-22T02:13:06Z INFO  ord::index::updater] Block 777676 at 2023-02-21 17:21:48 UTC with 1786 transactions…
[2023-02-22T02:13:08Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 2805 ms
[2023-02-22T02:13:11Z INFO  ord::index::updater] Block 777677 at 2023-02-21 17:22:07 UTC with 302 transactions…
[2023-02-22T02:13:12Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1851 ms
[2023-02-22T02:13:14Z INFO  ord::index::updater] Block 777678 at 2023-02-21 17:24:25 UTC with 735 transactions…
[2023-02-22T02:13:16Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1503 ms
[2023-02-22T02:13:17Z INFO  ord::index::updater] Block 777679 at 2023-02-21 17:33:08 UTC with 2469 transactions…
[2023-02-22T02:13:18Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1402 ms
[2023-02-22T02:13:21Z INFO  ord::index::updater] Block 777680 at 2023-02-21 17:36:08 UTC with 880 transactions…
[2023-02-22T02:13:24Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 2520 ms
[2023-02-22T02:13:25Z INFO  ord::index::updater] Block 777681 at 2023-02-21 17:47:20 UTC with 2882 transactions…
[2023-02-22T02:13:25Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 915 ms
[2023-02-22T02:13:26Z INFO  ord::index::updater] Block 777682 at 2023-02-21 18:05:10 UTC with 2854 transactions…
[2023-02-22T02:13:27Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 579 ms
[2023-02-22T02:13:27Z INFO  ord::index::updater] Block 777683 at 2023-02-21 18:11:08 UTC with 1505 transactions…
[2023-02-22T02:13:27Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 320 ms
[2023-02-22T02:13:28Z INFO  ord::index::updater] Block 777684 at 2023-02-21 18:14:58 UTC with 2473 transactions…
[2023-02-22T02:13:29Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 869 ms
[2023-02-22T02:13:30Z INFO  ord::index::updater] Block 777685 at 2023-02-21 18:19:38 UTC with 1392 transactions…
[2023-02-22T02:13:32Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1442 ms
[2023-02-22T02:13:34Z INFO  ord::index::updater] Block 777686 at 2023-02-21 18:24:19 UTC with 1477 transactions…
[2023-02-22T02:13:35Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1708 ms
[2023-02-22T02:13:37Z INFO  ord::index::updater] Block 777687 at 2023-02-21 18:24:48 UTC with 191 transactions…
[2023-02-22T02:13:39Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1722 ms
[2023-02-22T02:13:39Z INFO  ord::index::updater] Block 777688 at 2023-02-21 18:26:29 UTC with 568 transactions…
[2023-02-22T02:13:40Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 320 ms
[2023-02-22T02:13:40Z INFO  ord::index::updater] Block 777689 at 2023-02-21 18:27:18 UTC with 277 transactions…
[2023-02-22T02:13:41Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 602 ms
[2023-02-22T02:13:42Z INFO  ord::index::updater] Block 777690 at 2023-02-21 18:28:17 UTC with 360 transactions…
[2023-02-22T02:13:43Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1098 ms
[2023-02-22T02:13:44Z INFO  ord::index::updater] Block 777691 at 2023-02-21 18:29:43 UTC with 407 transactions…
[2023-02-22T02:13:45Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1050 ms
[2023-02-22T02:13:47Z INFO  ord::index::updater] Block 777692 at 2023-02-21 18:33:12 UTC with 934 transactions…
[2023-02-22T02:13:49Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1585 ms
[2023-02-22T02:13:50Z INFO  ord::index::updater] Block 777693 at 2023-02-21 18:39:44 UTC with 1610 transactions…
[2023-02-22T02:13:51Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1457 ms
[2023-02-22T02:13:53Z INFO  ord::index::updater] Block 777694 at 2023-02-21 18:44:56 UTC with 1401 transactions…
[2023-02-22T02:13:54Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1292 ms
[2023-02-22T02:13:55Z INFO  ord::index::updater] Block 777695 at 2023-02-21 18:48:43 UTC with 1001 transactions…
[2023-02-22T02:13:56Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 717 ms
[2023-02-22T02:13:57Z INFO  ord::index::updater] Block 777696 at 2023-02-21 18:51:11 UTC with 632 transactions…
[2023-02-22T02:13:59Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1483 ms
[2023-02-22T02:13:59Z INFO  ord::index::updater] Block 777697 at 2023-02-21 19:09:10 UTC with 3418 transactions…
[2023-02-22T02:14:00Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 593 ms
[2023-02-22T02:14:01Z INFO  ord::index::updater] Block 777698 at 2023-02-21 19:15:39 UTC with 2641 transactions…
[2023-02-22T02:14:02Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1195 ms
[2023-02-22T02:14:04Z INFO  ord::index::updater] Block 777699 at 2023-02-21 19:20:53 UTC with 1395 transactions…
[2023-02-22T02:14:06Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 2098 ms
[2023-02-22T02:14:07Z INFO  ord::index::updater] Block 777700 at 2023-02-21 19:47:46 UTC with 3630 transactions…
[2023-02-22T02:14:08Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 763 ms
[2023-02-22T02:14:09Z INFO  ord::index::updater] Block 777701 at 2023-02-21 19:58:55 UTC with 3074 transactions…
[2023-02-22T02:14:09Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 688 ms
[2023-02-22T02:14:10Z INFO  ord::index::updater] Block 777702 at 2023-02-21 20:21:31 UTC with 2768 transactions…
[2023-02-22T02:14:10Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 557 ms
[2023-02-22T02:14:11Z INFO  ord::index::updater] Block 777703 at 2023-02-21 21:06:15 UTC with 3008 transactions…
[2023-02-22T02:14:12Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 597 ms
[2023-02-22T02:14:12Z INFO  ord::index::updater] Block 777704 at 2023-02-21 21:08:30 UTC with 3159 transactions…
[2023-02-22T02:14:13Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 739 ms
[2023-02-22T02:14:13Z INFO  ord::index::updater] Block 777705 at 2023-02-21 21:11:43 UTC with 1601 transactions…
[2023-02-22T02:14:14Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 386 ms
[2023-02-22T02:14:14Z INFO  ord::index::updater] Block 777706 at 2023-02-21 21:22:39 UTC with 3081 transactions…
[2023-02-22T02:14:15Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 596 ms
[2023-02-22T02:14:16Z INFO  ord::index::updater] Block 777707 at 2023-02-21 21:25:21 UTC with 2460 transactions…
[2023-02-22T02:14:17Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1019 ms
[2023-02-22T02:14:18Z INFO  ord::index::updater] Block 777708 at 2023-02-21 21:26:46 UTC with 1825 transactions…
[2023-02-22T02:14:20Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1413 ms
[2023-02-22T02:14:21Z INFO  ord::index::updater] Block 777709 at 2023-02-21 21:29:30 UTC with 862 transactions…
[2023-02-22T02:14:23Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1296 ms
[2023-02-22T02:14:23Z INFO  ord::index::updater] Block 777710 at 2023-02-21 21:45:07 UTC with 2916 transactions…
[2023-02-22T02:14:24Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 648 ms
[2023-02-22T02:14:24Z INFO  ord::index::updater] Block 777711 at 2023-02-21 22:07:33 UTC with 2557 transactions…
[2023-02-22T02:14:25Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 414 ms
[2023-02-22T02:14:25Z INFO  ord::index::updater] Block 777712 at 2023-02-21 22:26:25 UTC with 2197 transactions…
[2023-02-22T02:14:26Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 384 ms
[2023-02-22T02:14:26Z INFO  ord::index::updater] Block 777713 at 2023-02-21 22:36:10 UTC with 3214 transactions…
[2023-02-22T02:14:27Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 632 ms
[2023-02-22T02:14:28Z INFO  ord::index::updater] Block 777714 at 2023-02-21 22:55:33 UTC with 2896 transactions…
[2023-02-22T02:14:28Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 677 ms
[2023-02-22T02:14:29Z INFO  ord::index::updater] Block 777715 at 2023-02-21 23:04:29 UTC with 1863 transactions…
[2023-02-22T02:14:30Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 802 ms
[2023-02-22T02:14:30Z INFO  ord::index::updater] Block 777716 at 2023-02-21 23:04:48 UTC with 2477 transactions…
[2023-02-22T02:14:31Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 726 ms
[2023-02-22T02:14:33Z INFO  ord::index::updater] Block 777717 at 2023-02-21 23:04:56 UTC with 236 transactions…
[2023-02-22T02:14:34Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1628 ms
[2023-02-22T02:14:36Z INFO  ord::index::updater] Block 777718 at 2023-02-21 23:08:52 UTC with 849 transactions…
[2023-02-22T02:14:37Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1090 ms
[2023-02-22T02:14:38Z INFO  ord::index::updater] Block 777719 at 2023-02-21 23:10:42 UTC with 556 transactions…
[2023-02-22T02:14:39Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1352 ms
[2023-02-22T02:14:41Z INFO  ord::index::updater] Block 777720 at 2023-02-21 23:16:40 UTC with 1179 transactions…
[2023-02-22T02:14:42Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1255 ms
[2023-02-22T02:14:43Z INFO  ord::index::updater] Block 777721 at 2023-02-21 23:35:43 UTC with 2724 transactions…
[2023-02-22T02:14:43Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 597 ms
[2023-02-22T02:14:44Z INFO  ord::index::updater] Block 777722 at 2023-02-21 23:43:15 UTC with 1801 transactions…
[2023-02-22T02:14:45Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1024 ms
[2023-02-22T02:14:46Z INFO  ord::index::updater] Block 777723 at 2023-02-21 23:53:36 UTC with 1645 transactions…
[2023-02-22T02:14:47Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 841 ms
[2023-02-22T02:14:47Z INFO  ord::index::updater] Block 777724 at 2023-02-22 00:19:00 UTC with 1955 transactions…
[2023-02-22T02:14:48Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 248 ms
[2023-02-22T02:14:48Z INFO  ord::index::updater] Block 777725 at 2023-02-22 00:24:43 UTC with 1992 transactions…
[2023-02-22T02:14:49Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 465 ms
[2023-02-22T02:14:49Z INFO  ord::index::updater] Block 777726 at 2023-02-22 00:46:07 UTC with 2709 transactions…
[2023-02-22T02:14:50Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 535 ms
[2023-02-22T02:14:51Z INFO  ord::index::updater] Block 777727 at 2023-02-22 00:54:01 UTC with 2054 transactions…
[2023-02-22T02:14:52Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 900 ms
[2023-02-22T02:14:53Z INFO  ord::index::updater] Block 777728 at 2023-02-22 01:03:32 UTC with 1461 transactions…
[2023-02-22T02:14:53Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 934 ms
[2023-02-22T02:14:55Z INFO  ord::index::updater] Block 777729 at 2023-02-22 01:09:04 UTC with 965 transactions…
[2023-02-22T02:14:56Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1437 ms
[2023-02-22T02:14:58Z INFO  ord::index::updater] Block 777730 at 2023-02-22 01:10:02 UTC with 173 transactions…
[2023-02-22T02:15:00Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1553 ms
[2023-02-22T02:15:01Z INFO  ord::index::updater] Block 777731 at 2023-02-22 01:12:11 UTC with 394 transactions…
[2023-02-22T02:15:03Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1433 ms
[2023-02-22T02:15:04Z INFO  ord::index::updater] Block 777732 at 2023-02-22 01:14:41 UTC with 411 transactions…
[2023-02-22T02:15:05Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 1440 ms
[2023-02-22T02:15:06Z INFO  ord::index::updater] Block 777733 at 2023-02-22 01:30:03 UTC with 1998 transactions…
[2023-02-22T02:15:07Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 743 ms
[2023-02-22T02:15:07Z INFO  ord::index::updater] Block 777734 at 2023-02-22 01:40:15 UTC with 1515 transactions…
[2023-02-22T02:15:08Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 562 ms
[2023-02-22T02:15:09Z INFO  ord::index::updater] Block 777735 at 2023-02-22 01:52:30 UTC with 1728 transactions…
[2023-02-22T02:15:09Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 682 ms
[2023-02-22T02:15:10Z INFO  ord::index::updater] Block 777736 at 2023-02-22 02:01:20 UTC with 1299 transactions…
[2023-02-22T02:15:11Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 861 ms
[2023-02-22T02:15:11Z INFO  ord::index::updater] Block 777737 at 2023-02-22 02:05:13 UTC with 694 transactions…
[2023-02-22T02:15:12Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 300 ms
[2023-02-22T02:15:12Z INFO  ord::index::updater] Block 777738 at 2023-02-22 02:12:07 UTC with 1295 transactions…
[2023-02-22T02:15:13Z INFO  ord::index::updater] Wrote 0 sat ranges from 0 outputs in 366 ms
[2023-02-22T02:15:13Z INFO  ord::index::updater] Committing at block height 777739, 0 outputs traversed, 0 in map, 0 cached


Add wizard/target-automated annotation when in Auto Mode

 When in Auto mode, Boluses that include BG data list “Target: Null” in the tooltip


TensorFlow Lite Interpreter get_tensor()

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): CentOS Linux release 7.5.1804 (Core)
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: N/A
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): Nightly 1.13.0-dev20181029
Python version: 3.6.6
Bazel version (if compiling from source): N/A
GCC/Compiler version (if compiling from source): N/A
CUDA/cuDNN version: N/A
GPU model and memory: N/A
Exact command to reproduce: Run the label_image_tflite.py script attached with gray128.jpg, inception_v3-l1a-zero-bias-zero-weights.tflite, labels.txt, and layer_outputs_gray128_f32_b0w0/ in the same directory

Describe the problem
When trying to write out tensors to file using the TensorFlow Lite Interpreter::get_tensor() function, mostly incorrect data is being returned. For the attached input, gray128.jpg, an image with all pixels set to RGB(128, 128, 128), I expect the layer outputs to be fairly repetitive, but it is not.
To further narrow down the issue, I modified the bias and weight tensors for the first layer to 0.0. After convolution and activation, I would expect the output tensor to be completely 0's, but it is not. The output is consistent across runs (deterministic). The input, output, bias, and weight tensors all seem to be written out correctly, but most of the intermediate output tensors do not seem to be.
I am doing this to try and verify the intermediate outputs with my own calculations. I was hoping to get inception verified with floating point, then with the uint8 quantized model, then with my own model.
Source code / logs
Attached is:

label_image_tflite.py
inception_v3-l1a-zero-bias-zero-weights.tflite
labels.txt
gray128.jpg

Just run the script (python3 label_image_tflite.py) in the same directory as the other files and a subdirectory, layer_outputs_gray128_f32_b0w0/ .
You can see in layer_outputs_gray128_f32_b0w0/6_tensor.txt that the output is not zero and doesn't appear to be repetitive despite the gray uniform input.
The label_image script was modified from the TensorFlow Lite example. The modified portion:
.
.
.
  interpreter.set_tensor(input_details[0]['index'], input_data)
  interpreter.invoke()

  # BEGIN Custom code to write out all tensors to files in a subdirectory
  ind = 0
  try:
    while True:
      dets = interpreter._get_tensor_details(ind)
      tens = interpreter.get_tensor(ind)
      # Expects subdirectory to exist
      f_dets = open("layer_outputs_gray128_f32_b0w0/{}_details_{}.txt".format(ind, dets['name'].replace('/', '-')), "w")
      # Write details
      f_dets.write("tensor[{}]: {}\n".format(ind, dets))
      # Write tensor data
      # Output tensors (Relu's) are giving incorrect values
      tens.tofile("layer_outputs_gray128_f32_b0w0/{}_tensor.txt".format(ind), ",")
      ind += 1
      f_dets.close()
  except:
    print("Finished writing tensor data")
  # END custom code

  output_data = interpreter.get_tensor(output_details[0]['index'])
  results = np.squeeze(output_data)
.
.
.

https://drive.google.com/open?id=1OhFLGVm9SVb9RnGxqw6gdePc12i5y1Nw (84MB)
If there is an alternate way I can inspect the intermediate outputs, that would be appreciated as well.
Thanks!
Edit: I suspect this issue is related: #22891

After seeing this answer on SO about it, I guess intermediate tensors are not guaranteed to have useful data, only the graph output(s). That makes sense for memory reasons, so I probably shouldn't expect this to work anytime soon.
I was able to (hackily) achieve what I needed by modifying the .tflite file with different output tensor indices and re-running the interpreter for each new output tensor.
Maybe the documentation can be updated to note that get_tensor() and tensor() can't be used to read intermediate results?

Thanks @raymond-li, you're right that there are no guarantees about intermediate tensors. That's good feedback on updating the documentation.

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

This issue is still relevant. In the documentation there is no mention of the usage of function get_tensor() begin only applicable to input and output tensors of a given model. Please add this to the documentation, deprecate the function or make it possible to initialize the engine so that it creates unique memory locations for each tensor so that it is possible to use this "feature" for other tensors also. Right now it is mostly useless.

I uploaded the hack-y modified label_image.py script I used here: https://github.com/raymond-li/tflite_tensor_outputter
It creates two output files for each tensor, a details file and a data file.


Add machine add option in paictl

Add machine from node-list.
The nodelist.yaml format
# Copyright (c) Microsoft Corporation
# All rights reserved.
#
# MIT License
#
# Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated
# documentation files (the "Software"), to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and
# to permit persons to whom the Software is furnished to do so, subject to the following conditions:
# The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED *AS IS*, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING
# BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
# NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
# DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
# OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

machine-list:

    - hostname: host1 # echo `hostname`
      hostip: <IP_ADDRESS>
      machine-type: D8SV3
      etcdid: etcdid1
      sshport: PORT
      username: username
      password: password
      k8s-role: master
      dashboard: "true"
      zkid: "1"
      pai-master: "true"

    - hostname: host2
      hostip: <IP_ADDRESS>
      machine-type: NC24R
      sshport: PORT
      username: username
      password: password
      k8s-role: worker
      pai-worker: "true"

The command:
./paictl.py machine add -p /conf/path -l nodelist.yaml

Test result
root@dev-box:~/pai/pai-management# kubectl exec -it etcd-server-<IP_ADDRESS> etcdctl member list
17f4464cf534b2c8: name=etcdid5 peerURLs=http://<IP_ADDRESS>:2380 clientURLs=http://<IP_ADDRESS>:4001 isLeader=false
20255328899b8c2e: name=etcdid4 peerURLs=http://<IP_ADDRESS>:2380 clientURLs=http://<IP_ADDRESS>:4001 isLeader=false
abb4499d886b40e0: name=etcdid2 peerURLs=http://<IP_ADDRESS>:2380 clientURLs=http://<IP_ADDRESS>:4001 isLeader=true
eef97f15c8e64b72: name=etcdid3 peerURLs=http://<IP_ADDRESS>:2380 clientURLs=http://<IP_ADDRESS>:4001 isLeader=false
f614574e9935e3db: name=etcdid1 peerURLs=http://<IP_ADDRESS>:2380 clientURLs=http://<IP_ADDRESS>:4001 isLeader=false
root@dev-box:~/pai/pai-management# kubectl exec -it etcd-server-<IP_ADDRESS> etcdctl cluster-health
member 17f4464cf534b2c8 is healthy: got healthy result from http://<IP_ADDRESS>:4001
member<PHONE_NUMBER>9b8c2e is healthy: got healthy result from http://<IP_ADDRESS>:4001
member abb4499d886b40e0 is healthy: got healthy result from http://<IP_ADDRESS>:4001
member eef97f15c8e64b72 is healthy: got healthy result from http://<IP_ADDRESS>:4001
member f614574e9935e3db is healthy: got healthy result from http://<IP_ADDRESS>:4001
cluster is healthy

when i add machine  use command above, the new node only run k8s services and openpai services not run.how start openpai services on this node?


[BUG] Databricks job launcher bugs when adding maven dependencies

Willingness to contribute
No. I cannot contribute a bug fix at this time.
Feathr version
0.10.4-rc1
System information

OS Platform and Distribution (e.g., Linux Ubuntu 20.0):
Python version: 3.8
Spark version, if reporting runtime issue:

Describe the problem
in Databricks job launcher class, adding library dependencies to databricks job api config via index shouldn't be used:
submission_params['libraries'][0]['maven']
...
submission_params['libraries'][1]['maven']
...
submission_params["libraries"][0]["jar"]

since this will break the job api config.
E.g.
in our feature embedding example, we add pypi dependency of transformer package as follows:
"libraries": [
        {"jar": "FEATHR_FILL_IN"},
        # sentence-transformers pip package
        {"pypi": {"package": "sentence-transformers"}},
    ],

The new codes that are adding maven dependencies to the config will modify the config to be:
[
    {
        'jar': 'FEATHR_FILL_IN',
        'maven': {'coordinates': 'com.linkedin.feathr:feathr_2.12:0.10.4-rc1'}
    },
    {
        'pypi': {'package': 'sentence-transformers'},
        'maven': {'coordinates': 'com.github.everit-org.json-schema:org.everit.json.schema:1.9.1', 'repo': 'https://repository.mulesoft.org/nexus/content/repositories/public/'}
    }
]

which has a broken format and will cause unexpected behavior when creating the databricks job.
also, submission_params["libraries"][0]["jar"] is not safe to use. If the first dependency library value is not ['jar']: FEATHR_FILL, but something else like pypi or any custom maven dependency users may set, then "libraries"][0]["jar"] this logic will break the format too.
Tracking information
No response
Code to reproduce bug
No response
What component(s) does this bug affect?

[X] Python Client: This is the client users use to interact with most of our API. Mostly written in Python.
[ ] Computation Engine: The computation engine that execute the actual feature join and generation work. Mostly in Scala and Spark.
[ ] Feature Registry API: The frontend API layer supports SQL, Purview(Atlas) as storage. The API layer is in Python(FAST API)
[ ] Feature Registry Web UI: The Web UI for feature registry. Written in React

Specifiy 'maven': {'coordinates': 'com.github.everit-org.json-schema:org.everit.json.schema:1.9.1', 'repo': 'https://repository.mulesoft.org/nexus/content/repositories/public/'} is no longer needed on notebook side if user is using maven jar with verson greater than v0.10.4-rc5.  everit.json.schema:1.9.1 is not available on maven and current cloud sparks can not pull packages from non maven central repos. Thus PR #1043 removes everit.json.schema:1.9.1' deps.
By default, python client uses same version of maven jar, so to get the fix for this issue, either

Wait till main branch pyhton client version is bumped to v0.10.4-rc5, this should happen soon if no new regressions are found on v0.10.4-rc5
Add a cell to force python client use a newer version maven jar os.environ['MAVEN_ARTIFACT_VERSION'] = "0.10.4-rc5" in notebook.


Add Zoom Feature

Hello, thanks for this lovely extension, I love it so far, and I want to suggest a useful feature to consider, which is the ability to zoom in and out in the preview while not affecting the whole text of the IDE.
Thanks in advance.

duplicate of #113


Redirect page on google

I saw that pages are generated without "/" on the end.
But when I access without it, it is redirecting the page, like
/tags redirects to /tags/

Hello @eerison
Maybe this would help?
And also trailing slash redirects have to deal with the hosting provider like Netlify rather than AstroPaper. You can also check Netlify's trailing-slash redirect option.

This one has been stale for a while.
Thus, close this for now.


Increase tekton remote resolver resources

Request is what is guaranteed so having such low requests vs limit is not good. There is a problem in production where resolving remote bundle is timing out. To rule out lack of resources, set the memory request same as limit to guarantee access to that amount of memory. Also increase CPU request for same reason and remove CPU limit.
If we see over time that we do not need such high memory request, a follow up change will be done to reduce it.

/lgtm


feat: Read external data from s3

Description
Adds the AWS SDK to allow us to read in external data into the showcase app. The homepage and tech radar both have files store in an object bucket claim that we can use AWS to read from. There is also added logic that will default to the files stored in the source code so that the homepage and tech radar will still load data even without access to our OBC.
Which issue(s) does this PR fix

Fixes #79

PR acceptance criteria
Please make sure that the following steps are complete:

GitHub Actions are completed and successful
Unit Tests are updated and passing
E2E Tests are updated and passing
Documentation is updated if necessary
Add a screenshot if the change is UX/UI related

How to test changes / Special notes to the reviewer

Going to close this as there is now a mechanism for reading in external data for the homepage and techradar


Publish the latest version 0.23.1 to PyPI

Currently, only version 0.23 is published to PyPi.
Can the Tableau team publish Tableau's server-client-python version 0.23.1 to PyPi?  Thanks.

@tanng1999 we had some issues with the publishing flow, but it's fixed now. You should be able to install v0.23.4 from PyPI now: https://pypi.org/project/tableauserverclient/


It seems that the code of qkv_transform is missing.

It seems that the code of class qkv_transform is not completed in lib/utils.py. Please provide the completed code. Thanks a lot!

This repo contains a completed code that runs.
qkv_transform is just simply a convolution, but with customized initialization:
https://github.com/csrhddlam/axial-deeplab/blob/master/lib/models/axialnet.py#L176


Multi Domain Support

This is a COPY of Issue 560: Multi Domain Support, filed on Google Code before the project was moved on Github.

Submitted on 2010-11-09T07:16:51.000Z by<EMAIL_ADDRESS>Status: Invalid

Please review the original issue and especially its comments. Comments here on closed issues will be ignored. Thanks.
Original description
I think it would be amazing if Yourls offered support for multiple domains for instance a user who signs up could use a default short url like   my.ly or they could use their own domain like them.ly this is one of the most amazing features that bit.ly currently offers is support for using your own domain instead of bit.ly and if people could simply come to my site and signup and use their own domain god that would rock because open source YOURLS would rock bit.ly and I would stop using bit.ly all together.

**Any idea on how it could be implemented? (interface, code, whatever)**
I imagine that it could be setup so that a user creates a cname record to the main Yourls default short name and then it begins working.... im sure it would require a lot of backend work.... :)

Hi , thanks for great tool.
Is this feature still in the roadmap ?
Keeping one install/docroot per domain only with a change in config seems not good practice.

good idea
and thanks
i will wait it,multi domain

Is there a way to use multiple domains within a single installation but the other domains are in different servers? Thanks for the feedback soon

@mauwiks If the domain is pointed to a different server, how do you propose YOURLS should receive the requests?

Instead of having two sets of files and two different config files, I just did this in my single config file..
 if ($_SERVER['HTTP_HOST'] == 'nice.name') {      define( 'YOURLS_SITE', 'http://nice.name' );  } else {     define( 'YOURLS_SITE', 'http://also-nice-but-long.nice.name' ); }
Not sure if there are any other implications to take into consideration, but this seems to work for me wihtout having to maintain two copies of the site.

I was wondering why my CNAME wasn't working. @alexander7567, your solution did the trick! Thanks!
In case it helps others, I adapted @alexander7567's approach to be a little less verbose if you're adding a bunch of domains:
if(in_array(strtolower($_SERVER["HTTP_HOST"]), array("also-nice-but-long.nice.name", "also-nice-but-long-2.nice.name", "also-nice-but-long-3.nice.name"))) {
	define("YOURLS_SITE", "https://" . strtolower($_SERVER["HTTP_HOST"]));
} else {
	define("YOURLS_SITE", "https://nice.name");
}


Custom classes only work at the root of a project

Godot version
v4.0.alpha4.official.f47097973
System information
Windows 10, Vulkan Clustered, NVIDIA GeForce GTX 1050
Issue description
If I want to create a new class_name, I must place it in the res:// directory. If I place it in some folder res://new_dir, when I click "create a new node", I won't see mine there.
Steps to reproduce
Create script in res://new_dir/test1.gd
extends Node
class_name Test1

Create script in res://test2.gd
extends Node
class_name Test2

Press "+" button (create new node)
Test2 will be in the list, but Test1 not.
Minimal reproduction project
No response

Can't reproduce, can you attach a minimal project?


Update step deploying kube-state-metrics in "Example: Adding logging and metrics..."

Fix path for kube-state-metrics
The path for the kube-state-metrics has been updated, and the sample output when verifying the state of kube-state-metrics has changed (in the current version there is only a single pod created, in the past there were two pods).
Also updated the step at the end (scaling the deployment and viewing the results) as the instructions did not match the narrative (the instructions were to scale down, and the narrative described a scale up).  The instructions, narrative, and screenshot now agree.

/assign @vineethreddy02

Thanks @DanRoscigno for updating the doc.
/lgtm

@VineethReddy02 , is there anything else I need to do?
Thanks,
Dan

@DanRoscigno I am approving it from my end.
/approve

Thanks very much!


invites: Allow users to invite without specifying any stream to join in 6.x.

Copy of #25455 for 6.x
I have not included the typo commit in this PR.

Screenshots and screen captures:

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Note that this is not tested manually yet. https://chat.zulip.org/#narrow/stream/21-provision-help/topic/error.20while.20provisioning.20on.206.2Ex.20branch

I have tested now and it works fine.

Updated the API changelog entry to describe the situation for which feature levels support it clearly.


Add corner detection functionality

This adds corner detection based on the Harris algorithm and the Shi-Tomasi algorithm. These are pretty common image processing tasks, so I thought they may be useful to others.

Need any help with this? Not sure why it was closed. The Travis failures?

Hi Tim,
I was just dealing with a Git issue on my side and was afraid of messing up. I've reopened it now. I've noticed I should add a docstring to the function imcorner() - any other comments ?

I totally understand git issues. It was the biggest barrier for me getting started with contributing to julia.
Adding the docstring would be great. Otherwise, everything looks really good!

FYI I don't get an email when you update this, so if you make changes and want me to look at it, just post a little comment.
If you click on the red "x" you'll see there's a test failure.

Thanks for all your assistance Tim! I've pushed an update that should fix the test failures.

Thanks for the contribution!

Thanks for everything Tim. I hope to be making some more contributions in the fitire.


feat(model-ad): connect the API server to the MongoDB server

Changelog

Initialize the Mongo database with a non-root user (ultimately)
Seed the database with a collection of two genes
Update the API server to list genes from the database
Map Gene document object to DTO
Add the host names model-ad-api and model-ad-mongo to the dev container
Start the Mongo container when starting the API server

Note
The conversion of Documents to DTOs and vice versa is done using the monorepo shared library shared-java-util. This demonstrates the re-usability of Java code across projects in the monorepo.
Preview
Build MODEL-AD images
model-ad-build-images

or just the images needed to test this PR:
nx run-many -t build-image -p model-ad-api model-ad-mongo

Start the API server and MongoDB with Docker Compose
nx serve-detach model-ad-api

Visualize the collection gene with the MongoDB extension for VS Code
Profile:

Host: model-ad-mongo
Port: 27017
Authentication

Username: modelad (defined in apps/model-ad/mongo/.env)
Password: changeme (defined in apps/model-ad/mongo/.env)

List genes
Using Swagger UI, a browser or the file apps/model-ad/api/requests.http:
GET http://localhost:8080/v1/genes

HTTP/1.1 200
Content-Type: application/json
Transfer-Encoding: chunked
Date: Thu, 20 Jun 2024 16:57:40 GMT
Connection: close

{
  "number": 0,
  "size": 2,
  "totalElements": 0,
  "totalPages": 1,
  "hasNext": false,
  "hasPrevious": false,
  "genes": [
    {
      "id": "66737b304e11611be5dab31c",
      "name": "BRCA1",
      "description": "BRCA1 Gene: A Key Player in Breast Cancer Susceptibility"
    },
    {
      "id": "66737b304e11611be5dab31d",
      "name": "TP53",
      "description": "TP53 Gene: Guardian of the Genome and Its Role in Cancer Prevention"
    }
  ]
}

Looks great! I was able to connect to Mongo via the VS Code Extension (after updating apps/model-ad/mongo/.env)

That's a good point: I should document the config files that need to be updated.


AdminClient doesn't use configured properties while starting an container listener

Back-port issue for: https://github.com/spring-projects/spring-kafka/issues/2762

Fixed via: https://github.com/spring-projects/spring-kafka/commit/d370d2d6fe8c5ad3f678ebee2f147b137e590d23


dev does not correspond to KONG_VERSION

I created my vagrant with KONG_VERSION=1.1.2. Kong version 1.1.2 installs but when I cd to /kong the Kong rockspec is 2.0.2 and in the Makefile the DEV_ROCKS look like they're for 2.x:
DEV_ROCKS = "busted 2.0.0" "busted-htest 1.0.0" "luacheck 0.23.0" "lua-llthreads2 0.1.5" "http 0.3"
Removing  kong-2.0.2-0.rockspec  and adding kong-1.1..2-0.rockspec from the Kong repo didn't help, make fails.
Any suggestions on how to create dev for a back-version of Kong?

@msummers-nr For going to a past major version like 1.1.2, I would recommend going back in the Git history of this repo.
git checkout 86760522f44c0a1f45d1e7719ee5d54be995f657

This should give you a 1.1.2-compatible setup.
Alternatively, you might want to take a look at Pongo.

@msummers-nr make sure that you check out your Git source kong of the Kong repo to the same version. The source tree inside the vagrant box at /kong is a mount to your host system. So make sure that repo is checked out to the same version as the binaries installed when you build the vagrant box.

As @hishamhm mentioned you can also use Pongo, if all you want is develop a plugin. That would be the easier way. If developing on Kong itself, use the vagrant box.

@msummers-nr was this resolved? can we close it?


[feature] Return hit barycentric coords along side texture coords

Describe the solution you'd like
Add either 1 new field to the modified TraceResult struct called HitBarycentric which would have a u and v component, or add 2 new fields, HitUGeometric and HitVGeometric.

Added in c4dba7329ca1d4ce77a72862950beea03bdaa8a3


'team' column in play_player

One of the first queries I tried was this:
select * from
play_player
where gsis_id='2009080950'
and i noticed that the first 15 drives (drive_id), all showed BUF as the 'team'.
Not sure if this is a bug, or im supposed to rely on the pos_team column from 'play' table.
Obviously BUF didn't make every single play in the first 15 drives.
To simplify finding the bug, this query returns the result where TEN ran for -3 yards as BUF defended, however both plays (the offensive run, and defensive tackle) both show 'BUF' in the 'team' field:
select * from
play_player
where gsis_id='2009080950' and drive_id=1 and play_id=83

This looks like a bug with this game only.  It's a preseason game and one of the first games entered into nfldb.
select gsis_id,drive_id,team from play_player where gsis_id = '2009080950' order by drive_id;
  gsis_id   | drive_id | team
------------+----------+------
<PHONE_NUMBER> |        1 | BUF
<PHONE_NUMBER> |        1 | BUF
<PHONE_NUMBER> |        1 | BUF
<PHONE_NUMBER> |        1 | BUF
<PHONE_NUMBER> |        1 | BUF
<PHONE_NUMBER> |        1 | BUF
<PHONE_NUMBER> |        1 | BUF
<PHONE_NUMBER> |        1 | BUF
<PHONE_NUMBER> |        1 | BUF
<PHONE_NUMBER> |        1 | BUF
<PHONE_NUMBER> |        1 | BUF
<PHONE_NUMBER> |        1 | BUF
<PHONE_NUMBER> |        1 | BUF
<PHONE_NUMBER> |        1 | BUF
<PHONE_NUMBER> |        1 | BUF
<PHONE_NUMBER> |        1 | BUF
<PHONE_NUMBER> |        1 | BUF
<PHONE_NUMBER> |        1 | BUF
<PHONE_NUMBER> |        1 | BUF
<PHONE_NUMBER> |        1 | BUF
<PHONE_NUMBER> |        1 | BUF
<PHONE_NUMBER> |        1 | BUF
<PHONE_NUMBER> |        1 | BUF

select gsis_id,drive_id,team from play_player where gsis_id = '2015092800' order by drive_id;
  gsis_id   | drive_id | team
------------+----------+------
<PHONE_NUMBER> |        1 | GB
<PHONE_NUMBER> |        1 | GB
<PHONE_NUMBER> |        1 | GB
<PHONE_NUMBER> |        1 | KC
<PHONE_NUMBER> |        1 | GB
<PHONE_NUMBER> |        1 | KC
<PHONE_NUMBER> |        1 | GB
<PHONE_NUMBER> |        1 | GB
<PHONE_NUMBER> |        1 | KC
<PHONE_NUMBER> |        1 | KC
<PHONE_NUMBER> |        1 | GB
<PHONE_NUMBER> |        1 | KC
<PHONE_NUMBER> |        1 | GB
<PHONE_NUMBER> |        2 | KC
<PHONE_NUMBER> |        2 | GB
<PHONE_NUMBER> |        2 | GB
<PHONE_NUMBER> |        2 | KC
<PHONE_NUMBER> |        2 | GB
<PHONE_NUMBER> |        2 | KC
<PHONE_NUMBER> |        2 | GB
<PHONE_NUMBER> |        2 | KC
<PHONE_NUMBER> |        2 | KC
<PHONE_NUMBER> |        2 | GB


Can I put it on bintray.com?

I modified it to support both circle and line menu: https://github.com/callmepeanut/FloatingActionMenu
Can I put it on bintray.com?

I'm going to be putting it on bintray tonight hopefully. I've been really busy, I'll get to it.

ok

would also love to see it on bintray

Will be putting it on tonight, if not then this weekend. Sorry, I've been super busy.

great! can you reopen the bug and close it once it is done to go from pull to push ;-)


fix: Terrain was not set as shown on first start

What does this PR change?
Added the missing TerrainShown flag when doing the GenerateTerrain + renamed method to GenerateTerrainAndShow so its clear that it also shows it. In the future we might wanna extract the show so we dont have GenerateAndShow and just Show methods in the RealmNavigator
How to test the changes?
Previously there would be no "nature" sounds anywhere and the visual culling would not work. so every tree would be visible, even outside of players view cone.
Now it should work as expected.

Also fixes the performance issues!!
Before:

After:


Break up staging release build job

What would you like to be added:
Break apart the staging release build into individual jobs which can (mostly) be run in parallel.
Why is this needed:
Currently the staging build, correctly, rebuilds all projects to ensure no oddities with dependencies.  This is done via a single code build job.  It would be nice if we could split this up into a pipeline which could run most of the builds in parallel and then 1 (or more) final jobs that put everything together and push the bundle.

This could be a potential usecase for Codebuild batch builds. We define the dependency tree in the batch build configuration and maintain the same workflow of queueing some projects until their dependencies have been built.


picture.nil? NoMethodError: undefined method `value' for nil:NilClass

some profiles have a problem with picture.
puts profile.picture
NoMethodError: undefined method `value' for nil:NilClass

I experience the same problem.
Apparently
(@page.at(".profile-picture img").attributes["src"].value.strip if @page.at(".profile-picture img"))

in profile.rb fails. It looks like on some profiles the profile IMG tag is present, but it is missing the SRC attribute...

I did some more digging. On one of the problematic profiles I found this (this is the content of @.page.at(".profile-picture img"):
 #<Nokogiri::XML::Element:0x2ad9dcaf0088 name="img" attributes=[
#<Nokogiri::XML::Attr:0x2ad9dceb8648 name="lazyload" value="true">,
#<Nokogiri::XML::Attr:0x2ad9dceb8634 name="class" value="image photo lazy-load">,
#<Nokogiri::XML::Attr:0x2ad9dceb8620 name="alt" value="Piotr Rykaczewski">,
#<Nokogiri::XML::Attr:0x2ad9dceb860c name="data-delayed-url"
value="https://media.licdn.com/mpr/mpr/shrinknp_200_200/p/2/005/00b/2eb/16f4a3e.jpg">,
#<Nokogiri::XML::Attr:0x2ad9dceb85f8 name="width" value="200">,
#<Nokogiri::XML::Attr:0x2ad9dceb85e4 name="height" value="200">]>

They lazy-load pictures, so we will have to search for src or data-delayed-url attribute.

Can someone send a PR?

I am trying to create it. Unfortunately current HEAD does not work with my app, so I will have to first find out what's the problem. Probably renaming linkedin-scraper to linkedin_scraper broke something...

Ya, I recently renamed the files to follow Ruby conventions

OK - just a side note: after your rename, I had to add explicit :require => 'linkedin_scraper' to my Gemfile. Apparently the name change killed bundler auto-loading..
The PR for this issue is ready.


SMARTS substructure matching failed for spiro compounds

Chem.GetSubstructMatches() using a SMARTS pattern is incomplete for the below spiro compounds.
from rdkit import rdBase
from rdkit.Chem import Draw

print(f"RDKit {rdBase.rdkitVersion}")

mol1 = Chem.MolFromSmiles("C12=C(C=CC=C2)C=CC3(O1)CCCCC3")
mol2 = Chem.MolFromSmiles("C12=C(C=CC=C2)N=CC3(O1)CCCCC3")

for mol in [mol1, mol2]:
    for i, atom in enumerate(mol.GetAtoms()):
        atom.SetProp("atomNote", str(atom.GetIdx()))

patt_1 = Chem.MolFromSmarts('[#6x3R2][#6x3R2][#6][#6]')
matches_1 = sum(mol1.GetSubstructMatches(patt_1), ())
patt_2 = Chem.MolFromSmarts('[#6x3R2][#6x3R2][#7][#6]')
matches_2 = sum(mol2.GetSubstructMatches(patt_2), ())

Draw.MolsToGridImage([mol1, mol2], highlightAtomLists=[matches_1, matches_2])

Expected behavior
Atoms 6 and 7 should be in the matched atoms
Configuration (please complete the following information):

RDKit version: rdkit 2023.09.5
OS: Linux

There’s a double bond between the N and the C in the molecule and not in the SMARTS so it’s correct that no match is reported.

I agree with @DavidACosgrove

@sunghunbae please let us know if we have misunderstood something


output methods

consider breaking different output options into separate methods

created separate methods for output. could use some additional testing.


Repeated redundent "doing nothing" messages

There are 6066 messages in one second, all saying:
2016/08/11 09:12:01 amazon drive root 'XXX': Token expired but no uploads in progress - doing nothing

I believe one message should be enough when the token expiration is detected.

What is your rclone version (eg output from rclone -V)
v1.32-18-g29ab7eaβ
Which OS you are using and how many bits (eg Windows 7, 64 bit)
Windows 10, 64 bit
Which cloud storage system are you using? (eg Google Drive)
Amzon Drive
The command you were trying to run (eg rclone copy /tmp remote:tmp)
rclone --checksum --contimeout=10m --retries 10 --verbose --transfers 6 --log-file "XXX" sync XXX "Amazon_Drive:XXX" --max-size 5M
A log from the command with the -v flag (eg output from rclone -v copy /tmp remote:tmp)
See above

Ha!  That looks like a bug ;-)  Will fix as part of the beta - thanks.

This is fixed now: see http://pub.rclone.org/v1.32-20-g2ebeed6β/


Fix git push error for protected CLA branch

The pull request is created from master636894781331860180 to master to fix git push error for protected CLA branch

@opbld17 : Thanks for your contribution! The author, @, has been notified to review your proposed change.


Fix/progress goes backwards

fix https://forums.ankiweb.net/t/anki-24-04-beta-rc/41792/53?u=l.m.sherlock
In this PR, we will initialize the progress before training.

Thanks for looking into this!


Clair template missing database variable

I believe there's an issue with the clair template missing the dbname value.
The harbor.cfg file gives off the impression that you can change the database name for clair if you use an external database. However the database name change is never picked up as there's no template variable to update the postgresql URI string.
1) Versions
docker-engine version:  17.12.1-ce
docker-compose version:  1.19.0
harbor online install: 1.4.0
2) Harbor.cfg changes:
Everything is default but the following changes:
##########Clair DB configuration############
#Clair DB host address. Only change it when using an external DB.
clair_db_host = harbor.test.com
#The password of the Clair's postgres database. Only effective when Harbor is deployed with Clair.
#Please update it before deployment. Subsequent update will cause Clair's API server and Harbor unable to access Clair's database.
clair_db_password = testing
#Clair DB connect port
clair_db_port = 5432
#Clair DB username
clair_db_username = harbor
#Clair default database
clair_db = clair
3) Log output:
018-03-18 18:33:24.846331"}
Mar 18 18:33:31 <IP_ADDRESS> clair[1260]: {"Event":"pgsql: could not open database: pq: database "harbor" does not exist","Level":"fatal","Location":"main.go:96","Time":"2018-03-18 18:33:31.585771"}
Mar 18 18:33:44 <IP_ADDRESS> clair[1260]: {"Event":"pgsql: could not open database: pq: database "harbor" does not exist","Level":"fatal","Location":"main.go:96","Time":"2018-03-18 18:33:44.720366"}
Mar 18 18:34:10 <IP_ADDRESS> clair[1260]: {"Event":"pgsql: could not open database: pq: database "harbor" does not exist","Level":"fatal","Location":"main.go:96","Time":"2018-03-18 18:34:10.648880"}
Mar 18 18:35:02 <IP_ADDRESS> clair[1260]: {"Event":"pgsql: could not open database: pq: database "harbor" does not exist","Level":"fatal","Location":"main.go:96","Time":"2018-03-18 18:35:02.189687"}
Steps to reproduce the problem:
Clean online install:

Make the config changes that I did
Run ./prepare --with-clair
Check common/config/clair/config.yaml

postgresql source URI is incorrect it's missing /clair from the template generated URI:
source: postgresql://harbor:testing@harbor.test.com:5432?sslmode=disable
Should be:
source: postgresql://harbor:testing@harbor.test.com:5432/clair?sslmode=disable
Note: Clair template in location: common/templates/clair/config.yaml
source: postgresql://$username:$password@$host:$port?sslmode=disable
Should be something like ?:
source: postgresql://$username:$password@$host:$port/$dbname?sslmode=disable

https://github.com/vmware/harbor/pull/4624


Getting lockfile mismatch errors when editing the manifest

λ buffrs install
Error:
   0: Mismatched registry detected for dependency xyz - requested https://xyz.jforg.io/artifactory but lockfile requires https://xyz.jfrog.io/artifactory

Location:
   src/package.rs:586

The lockfile should be updated from the edited manifest

This was intentional but you're right, the manifest should always take precedence.


Translated Japanese words in session_en.json into English

Despite session_en.json, places and categories are written in Japanese.
I translated them into English.
Place
The same as strings displayed in current Map.
ルーム{A,B,C,D} => Hole {A,B,C,D}
基調講演会場 => Keynote venue
Category
基調講演 => Keynote
その他 => Others
UI・デザイン => UI and Design
ハードウェア => Hardware
プラットフォーム => Platform
開発環境・ツール => Environment and Tool
メンテナンス => Maintenance
Androidの最新動向 => Latest Trend in Android
If terms are wrong, please tell me that. I will fix it.

Awesome!

Tagged https://github.com/konifar/droidkaigi2016/issues/29

@hkurokawa Could you review it? :bow:

Awesome! Just reviewed and pointed out one thing.

I am merging this PR and will make the naming of the rooms consistent with another PR.
@jmatsu Really appreciate your support!