加载预训练模型出错

我使用的是pytorch      1.2.0 和torchvision 0.4.0，出现如下错误。这个问题已经困扰我好久了，而且在其他地方也遇到过。请廖老师和各位高手帮忙指点迷津。非常感谢。
RuntimeError: Error(s) in loading state_dict for ResNet:
size mismatch for bn1.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer1.0.bn1.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer1.0.bn2.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer1.0.bn3.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer1.0.downsample.1.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer1.1.bn1.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer1.1.bn2.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer1.1.bn3.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer1.2.bn1.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer1.2.bn2.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer1.2.bn3.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer2.0.bn1.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer2.0.bn2.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer2.0.bn3.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer2.0.downsample.1.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer2.1.bn1.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer2.1.bn2.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer2.1.bn3.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer2.2.bn1.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer2.2.bn2.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer2.2.bn3.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer2.3.bn1.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer2.3.bn2.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer2.3.bn3.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer3.0.bn1.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer3.0.bn2.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer3.0.bn3.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer3.0.downsample.1.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer3.1.bn1.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer3.1.bn2.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer3.1.bn3.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer3.2.bn1.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer3.2.bn2.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer3.2.bn3.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer3.3.bn1.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer3.3.bn2.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer3.3.bn3.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer3.4.bn1.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer3.4.bn2.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer3.4.bn3.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer3.5.bn1.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer3.5.bn2.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer3.5.bn3.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer4.0.bn1.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer4.0.bn2.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer4.0.bn3.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer4.0.downsample.1.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer4.1.bn1.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer4.1.bn2.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer4.1.bn3.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer4.2.bn1.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer4.2.bn2.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for layer4.2.bn3.num_batches_tracked: copying a param with shape torch.Size([]) from checkpoint, the shape in current model is torch.Size([1]).

你的 pretrain model state dict 貌似是空的。

更新了 code，现在不需要指定 pretrain_path，你可以再试试。


Using operators without having transformers installed

I'm currently trying to use just the operators defined in fla.ops; however, because of the __init__.py script for the main package, it's not possible to do this without importing things from the HF transformers package, which makes the import slower (and broke it entirely until I upgraded the package).
It would be nice if there were a way to just import the operators without the layer modules or anything else.

@Ronsor Hi, may I know why you need this. I think its hard to use fla as well if transformers is unavailable. Currently this pkgs is heavily tied with 🤗  transformers, e.g., we use its off the shelf utility fns to check Trion versions and raise some warnings and we alse make use of some activations in transformers.


Dashboard settings form QOL improvements

addresses #49
shortBio is marked as optional in the Prisma schema, so the initial value is null which doesn't match with the type CurrentUser. So I'm setting it as an empty string if it is null. Not sure if it is the best approach, but any advice is appreciated!

Thanks for the PR. I will check soon

All good. just need a few changes and then ready to merge. Thanks

you can just call optinal method at the end to make it optional. take a look here
https://zod.dev/?id=optionals

This was my first intuition as well. But it doesn't work if you type something in the short bio field and then remove it. Because then it becomes an empty string (""), but it won't let you update your profile with bio as an empty string as min length is 10 chars.
And the flex class in the other file is to fix the alignment with "cancel" button. During loading state the alignment gets messed up because of the loading icon

And the flex class in the other file is to fix the alignment with "cancel" button. During loading state the alignment gets messed up and causes layout shift because of the loading icon

Hey,

you can just call optinal method at the end to make it optional. take a look here
https://zod.dev/?id=optionals

This was my first intuition as well. But it doesn't work if you type something in the short bio field and then remove it. Because then it becomes an empty string (""), but it won't let you update your profile with bio as an empty string as min length is 10 chars.
And the flex class in the other file is to fix the alignment with "cancel" button. During loading state the alignment gets messed up and causes layout shift because of the loading icon

Hey, seems you are right, I removed the min and max and I noticed font flickering issue while checking the buttons layout shift. I added few adjustments. thanks.


app.config provider object

Hi there, great app.
It lacks however the config provider object so that one can define the settings in tehangular standard way and not via window.CONSTANT..
Is this possible?

Hi, @rosscdh, thanks for your feedback!
Yes, of course it's possible through the use of provider instead of factory.  PRs are always welcome)

I gave it a shot about 40 mins but there are some quirks and I gave up. I would really appreciate it

Fantastic! Thanks

You're welcome)


Add health-check for wireguard

Note:
The actual health-check test requires tweaking: test only passes after gefyra-con-create; that is when wg0 device comes up for first time:
    return popen("ip link show %s up " % device).read() != ""

Hey @CK50 we are currently working on your PR in a new PR #700 because it requires some changes :) I will close this for now and keep you updated!


v1.10 backports 2022-06-29

#19379 -- add support for AKS BYOCNI (@nbusseneau)

Once this PR is merged, you can update the PR labels via:
$ for pr in 19379; do contrib/backporting/set-labels.py $pr done 1.10; done

What were the conflicts?

Helm values / README to regenerate.

For something that simple to fix, we should favor letting the tophat do the backports. We want to avoid having multiple backport PRs in flight as the same time.

For something that simple to fix, we should favor letting the tophat do the backports. We want to avoid having multiple backport PRs in flight as the same time.

Agreed, I thought there'd be more conflicts initially because I intended to only backports Azure IPAM changes (and the structure had changed in previous commits in the PR), but in the end I recalled we had discussed backporting everything because older branches would benefit from BYOCNI as well...
We can drop this PR to include it in regular backports if we think it's better.

We can drop this PR to include it in regular backports if we think it's better.

Let's do that. In general, it's fine to only backport once the tophat tells you they won't pick it up themselves because of conflicts.

Closing as per the discussion above.


feat(): ignoring stateless feature impl

I think you should also set stateful feature to the stateful module here. Because even if we don't enable the feature, the module will still be built. I don't think that this is the expected behavior.
https://github.com/adorsys/didcomm-mediator-rs/blob/bdc5d36a3d4ab6a75aa500b38be1872bd9e49586/crates/plugins/mediator-coordination/src/model/mod.rs#L1-L5

Ok


Remove FCD newrelic alerts

Background
Describe the problem that we are trying to solve with this feature.
If a path to a solution is known, feel free to write it down, but have an open mind
We don't need these
Done when

[x] We're no longer getting any alerts from the FCD server in newrelic https://onenr.io/0vwBL3qa8jp

disabled logging in config file
ubuntu@localhost:~/app/fcd$ cat .envrc
export SERVER_PORT=3060
export CHAIN_ID=paloma-testnet-15
export LCD_URI=https://lcd.testnet.palomaswap.com
export FCD_URI=https://fcd.testnet.palomaswap.com
export RPC_URI=https://testnet.palomaswap.com
export SENTRY_DSN=
export USE_LOG_FILE=false


Copyright YEAR is not handled correctly

About this issue

Briefly describe the issue
In all Licence and Copyright dialogs the year isn't properly parsed and only shows up as YEAR.
Eg. "Copyright (c) YEAR, AOSP" or  "Copyright (c) YEAR, Mike Penz"

How can the issue be reproduced / sample code
Also repruducible here https://play.google.com/store/apps/details?id=com.mikepenz.aboutlibraries.sample but in this version OWNER is also left out.

I have just started to use you lib so not sure if the error is on my side. Good work with this lib so far!
Details

[ ] Used library version
[ ] Used support library version
[ ] Used gradle build tools version
[ ] Used tooling / Android Studio version
[ ] Other used libraries, potential conflicting libraries

Checklist

[x] Searched for similar issues
[x] Checked out the sample application
[x] Read the README
[x] Checked out the CHANGELOG
[ ] Read the MIGRATION GUIDE

I believe with b06 I did the improvements currently the best.
Improved matching for MIT and apache, added theoretical support for all SPDX identifiers.
Also added a way for you to provide the license years for libraries you include. I would still love to automate this somehow, but right now I am in the believe this is out of scope.
We might have an API(?) which scrapes the license info and tries to get the year. from the README. if somehow applicable.
Not sure though if we really want to consider this due to performance / speed topics.

Apply a custom mapping with the year for the licenseId per line:
https://github.com/mikepenz/AboutLibraries/blob/develop/config/custom_license_year_mappings.prop
config the path to the configs:
https://github.com/mikepenz/AboutLibraries/blob/develop/app/build.gradle#L64-L66
get all libraryIds as in your project:
 ./gradlew findLibraries --warning-mode all


fix(dialog-service): Remove 'ngneat-dialog-hidden' from body

fixes ngneat/dialog#26
PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: CONTRIBUTING.md#commit
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

When nested dialog is closed, then class 'ngneat-dialog-hidden' is removed from body.
Issue Number: 26
What is the new behavior?
Class 'ngneat-dialog-hidden' is removed from body after last dialog was closed.
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information

I've seen my auto-format settings adjusted a lot of white-spaces. Not sure if this is a problem and needs to be fixed. Let me now if I should do anything further.

I'll re-submit the pull request with fixed white-spaces and commit message.


Non-Manga Tracking System

Describe your suggested feature
While tracking manga works great, it doesn't have anything for Non-Manga Tracking (i.e. Marvel, DC, Image, etc). While this isn't detrimental, with the ability to add Non-Manga sources, it would be nice to be able to track my other type of comics I read as well.
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 0.16.5.
[X] I will fill out all of the requested information in this form.

If you know of a tracking service for such content with a free public API then toss it in the description, otherwise there's nothing to go on here.

I was requesting hoping that someone knew of something I may not have. I have been able to find a couple of APIs with metadata for comics, but I'm pretty sure that'd only be one part of what is needed for tracking. I personally use Comic Geeks app to track the comics I read, but I couldn't seem to find an API to connect to it. The closest thing I could find was here on GitHub but I'm not sure that would be what is needed.
(Disclaimer: I'm not a Developer. Just a Technical Business Analyst with development ideas)

Make a new request when you find an comic tracking site with api (plus point if you ask in our discord first)


URGENT: Citation of standards that have a withdrawn past incorrectly marked as "withdrawn"

It seems that citing an undated standard that has a withdrawn edition will mark the whole standard as "withdrawn". Remember that the undated standard reference obtains metadata from the "newest active edition".
For example, ISO 9000 is current https://www.iso.org/standard/45481.html

However, this code gives a withdrawn result:
<<ISO_9000>> explains that quality is not an abstract concept of absolute
perfection. Quality is actually the conformance of characteristics to
requirements. This actuality means that any item of data can be of high quality
for one purpose but not for a different purpose. The quality is different
because the requirements are different between the two purposes.

...
[bibliography]
== Bibliography

* [[[ISO_9000,ISO 9000]]]]

Rendered as:

Metanorma is now treating so many documents as withdrawn, incorrectly.

@opoudjis @andrew2net is this a Relaton problem or a Metanorma problem? If a Relaton problem please create a ticket in Relaton-ISO. Thanks!

Metanorma

https://github.com/relaton/relaton-iso/issues/106

the status of the returned by relaton document is 90.93 "confirmed"
<status>
    <stage>90</stage>
    <substage>93</substage>
</status>

as it is on the document's page

I don't understand what we need to fix.

90.93 is correct as in “confirmed”. Maybe Metanorma is mistaking that code for withdrawn?

It is.


[WFLY-9016] - SecurityDomain is lost when setting up remote outbound connections

References

https://issues.jboss.org/browse/WFLY-9016
https://issues.jboss.org/browse/JBEAP-11377

After this is merged, please re-test https://github.com/wildfly/wildfly-core/pull/2591

Retest this please

Retest this please


RDK-37910 Added HdmiCecSink test framework

RDK-37910 Added HdmiCecSink test framework

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

will create another one


"Hidden" endpoint file

Another thing, now my project is getting bigger, the endpoint files are getting bigger too, especially when I'm dealing with different REST requests. What I'm doing right now is using the file inside the endpoint folder just to redirect requests to another file in a utils folder. Like this:
/endpoints
  - project.ts

/utils
  - /handlers
    - /project
      - handleGet.ts
      - handlePut.ts
      - handlePatch.ts

But what if we could add files inside the endpoints folder that don't turn into an endpoint? This way we could use something like this:
/endpoints
  - /project
    - index.ts (to handle)
    - _handleGet.ts
    - _handlePut.ts
    - _handlePatch.ts

Some languages use _ to reference a private element, we could use this at the beginning of the file to not turn it into an endpoint

I don't see what would be gained by complicating the endpoints rules that we don't already have.  How exactly is /endpoints/project/_* better than /utils/handlers/*?


Test with Auto Generated Id Types

Since it's a common practice to have an auto-incrementing numerical id for the entities, the library should support this. It, in theory, already supports this but all the examples and tests are using UUID type. This needs to be tested properly and perhaps the documentation should show both approaches.

Tested in template repositories


Ability to define custom generators

Hello!
I would like to define my own custom generators using this library. However, I noticed that the Generator type is opaque, which seems to prevent this. I am curious about the rationale behind making Generator opaque and if there are any ways to define custom generators.
Why?
I am currently working on a project where I need to implement dice roll mechanics, such as "dice explosion." This involves rolling n dice and rerolling dice based on specific conditions (e.g., rerolling up to the number of maximum values rolled).
Here’s a specific example using d10 dice:

Initial roll: [10, 4, 5, 5, 2]
Since there is one maximum value (10), I get to reroll one additional dice.

Below is an example of the usage I am aiming for:
let seed = seed.new(0)

random.int(1, 10)
|> dice_explosion(5)
|> random.sample(seed)
|> io.debug // [10, 8, 7, 3, 4, 1]

In this example, we asked for 5 dice in the dice_explosion call, but the output has a length of 6 due to rerolling the 10.
Here’s a potential implementation for the dice_explosion (I took inspiration from the fixed_size_list implementation):
fn do_dice_explosion(
  acc: List(Int),
  seed: Seed,
  generator: Generator(Int),
  length: Int,
) -> #(List(Int), Seed) {
  case length {
    0 -> #(acc, seed)
    n -> {
      let #(roll, next_seed) =
        generator
        |> random.fixed_size_list(n)
        |> random.step(seed)

      // This example isn't generic on the random.int range of values, but illustrates the concept
      let rerolls = roll |> list.filter(fn(x) { x == 10 }) |> list.length

      do_dice_explosion(list.concat([acc, roll]), next_seed, generator, rerolls)
    }
  }
}

fn dice_explosion(generator: Generator(Int), n: Int) -> Generator(List(Int)) {
  use seed <- Generator
  do_dice_explosion([], seed, generator, n)
}

But this requires me to create a Generator via use seed <- Generator, which is not possible with the current implementation since Generator type is opaque.
Questions

Why is the Generator type defined as opaque?
Is there an alternative approach to achieve similar functionality? I was not able to find an alternative where I could get the updated seed from the previous piped generator, update it throughout the dice rolling process and pass it down to the next piped function.

Thank you!

Hello! Thanks for asking, this is the perfect use case for random.then: I'd write something like this
pub type Dice {
  Dice(faces: Int)
}

pub fn explosive_roll(dice: Dice) -> Random(List(Int)) {
  let initial_rolls_size = 5
  use initial_rolls <- random.then(roll(dice, initial_rolls_size))
  //  ^^^^^^^^^^^^^ Thanks to `then` we have access to the randomly
  //                generated sequence and can decide how to go on
  //                and what to return.

  let additional_rolls_size =
    count(initial_rolls, fn(roll) { roll == dice.faces })

  use additional_rolls <- random.then(roll(dice, additional_rolls))
  //  ^^^^^^^^^^^^^^^^ Once again, thanks to `then` we also have the
  //                   randomly generated additional rolls.

  random.constant(list.append(initial_rolls, additional_rolls))
  //     ^^^^^^^^ In the end we must still return a generator, not
  //              just a list, so we can wrap the randomly generated
  //              list in a `constant` generator.
}

pub fn roll(dice: Dice, times n: Int) -> List(Int) {
  random.fixed_size_list(n, from: random.int(1, dice.faces))
}

In general, when you need to combine simple generators into more complex ones you'll want to reach for map, map2, ... and then (which is the most powerful one as it gives you the ability to access the randomly generated value and decide what to generate based on its actual value).
I hope this helps!

That is exactly what I was looking for, thank you so much! I had experimented with .then, but the idea of nesting them in the way you showed never crossed my mind. As a result, I was composing functions in a way that didn't make much sense and didn't really worked out. But the solution was so simple all along!
Now I can also see the full power of then, in the docs you mentioned how powerful it was but now it clicked in my head. Thanks a lot again!

 Always happy to help 💕


fix(light-apps): Put Network and Provider dropdowns in TopBar

@goldsteinsveta i would appreciate a quick look on yarn start:ui!
In particular, I kept the block number for now. I think it's still useful to show it somewhere, maybe in a tooltip on hover over the green circle? We could also show some reasons when the circle is yellow/red (e.g. node is syncing, not enough peers, no network detected...)

@amaurymartiny yeah, it's necessary to keep it. If you start the storybook and open http://localhost:9001/?path=/story/connectednodes-topbar--providerhealth there's a block number there. I'll make sure there's a way to access full block num and the info you mention in the next PR


non-human disease by gene - dosdp

This PR create a new pattern for non-human diseases coming from omia and defined by a variation in a specific gene.
Note that this pattern is the same as the human disease pattern, but the class for disease is specific to non-human diseases.

@matentzn and I discussed this on our 1:1 on Feb 14th, 2024.
The pattern OMIM_disease_series_by_gene refers to the variable "disease" as "MONDO:0000001", which is the parent term of "human disease" and "non-human disease". Therefore, it would make sense to keep the original for both human and non-human diseases. (note: I have confirmed that "human disease" and "non-human disease" are disjointed).
I will close this PR, and create a new one where the description of the original pattern is updated to reflect this.


CAS menu

Hello good ppl. Can anyone provide a quick explanation of what the CAS menu is or what it does?

It's an abbreviation for Current Address Space. It's mainly intended for developers.

Thank you for your reply. So do I just keep the setting at Auto?


setPageWithoutAnimation changing pages with animation

Environment
RN 0.68.1
react-native-pager-view 5.4.17 and newer
iOS 15.5
Description
setPageWithoutAnimation changing pages WITH animation.

@mateusz-ramski I have added a comment here: https://github.com/callstack/react-native-pager-view/pull/564#issuecomment-1137801550 could you take a look on it and create a PR with the appropriate fix ?


Node images are missing dependencies for Playwright

For Premium customers, Consumption Images support playwright but, the same app fails on premium workers because of a bad dependency.  Need to include the dependency here.

@pragnagopa @CooperLink any update on this? We are currently being blocked to upgrading to V4 because of the missing dependencies. This is becoming a critical issue for us? Any reason the dependencies were removed from V4?

Hi @CooperLink Hope Hope you are doing well. Could you give me any updates if playwight supports in EP plan? thank you

Hi @yuna-s this has been completed, The node images should support playwright. I checked the node18 image below
https://github.com/Azure/azure-functions-docker/blob/dev/host/4/bullseye/amd64/node/node18/node18-composite.template#L12


Adding Polars instead of pandas

Codecov Report

Merging #11 (f1f3010) into master (535d097) will decrease coverage by 1.8%.
The diff coverage is 81.5%.

:exclamation: Current head f1f3010 differs from pull request most recent head 28e4b17. Consider uploading reports for the commit 28e4b17 to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@           Coverage Diff            @@
##           master     #11     +/-   ##
========================================
- Coverage    91.1%   89.4%   -1.8%
========================================
  Files           7       7
  Lines         441     464     +23
========================================
+ Hits          402     415     +13
- Misses         39      49     +10

Files
Coverage Δ

src/data_toolset/main.py
97.5% <100.0%> (+0.2%)
:arrow_up:

src/data_toolset/utils/base.py
82.1% <77.7%> (-0.8%)
:arrow_down:

src/data_toolset/utils/avro.py
94.3% <80.0%> (-2.1%)
:arrow_down:

src/data_toolset/utils/parquet.py
92.7% <76.9%> (-4.5%)
:arrow_down:


Upgrade to a more recent cachix release

We are using 0.3.5 while 0.6.0 is out, with a ton of speed improvements.

Ah no, cachix comes from nixpkgs and I was using a 20.03 image when I opened this issue.
All good.

Ah no, cachix comes from nixpkgs and I was using a 20.03 image when I opened this issue.
All good.


feat(telemetry): Add url data to operator updates on telemetry service

Description
This PR adds new data to be updated for each operator on the telemetry service, which includes:

eth_rpc_url
eth_rpc_url_fallback
eth_ws_url
eth_ws_url_fallback
version (this one was already present)

The implementation is also updated from the operator's side.
Testing
In order to test, the following steps were taken:

Start anvil and the aggregator with:

make anvil_start_with_block_time
make aggregator_start

Build and register operator with:

make build_operator
make operator_full_registration CONFIG_FILE=config-files/config-operator-1.yaml

Start telemetry service with:

make telemetry_clean_db
make telemetry_run_db
make telemetry_start

Go to http://localhost:4001/api/operators and you should see the operator with its data fields. Some of them, like the version and RPC related should be set as null, since the operator is not up yet.
Start the operator with ./operator/build/aligned-operator start --config ./config-files/config-operator-1.yaml
Go to http://localhost:4001/api/operators and you should see the operator, now with all fields with a certain value, including version and RPC related.

It is also highly advisable to test previous functionality as it's described on this already merged PR

Tested on my machine, and it worked fine. One thing, in the diff I see you changed the eigenlayer-middleware, is that on purpose?

No, I haven't touched anything related to that. There was a merge from staging branch, so maybe it was an auto merge error? eigenlayer-middleware is a submodule, I checked and the staging branch points to the same commit as this one, so Idk what caused that diff.

Tested on my machine, and it worked fine. One thing, in the diff I see you changed the eigenlayer-middleware, is that on purpose?

No, I haven't touched anything related to that. There was a merge from staging branch, so maybe it was an auto merge error? eigenlayer-middleware is a submodule, I checked and the staging branch points to the same commit as this one, so Idk what caused that diff.

My bad. The submodule commit was in fact different from the one in staging branch. Good catch!

everything worked correctly, but I am thinking that it does not make much sense to register the http and websocket providers separately. Since the protocol and the API key are stripped, they will always be the same, or am I missing something?


Does the 'Supported regions' section need to be updated to fit the current situation in Mooncake?

Hi, team
To my knowledge, Azure file shares backup is not available in Mooncake. In addition to this, Azure Backup has been available in a new Chinese region called 'China North 3' for a period of time. But the 'Supported regions' section within the article hasn't incorporated the information of the new region, so it could confuse the reader in a sense.
In this case, there is one customer considered that Azure file shares backup had been available in China North 3 after he read this section, in fact, he can't use this feature in Mooncake at this moment. So, he asked us for confirmation after trying to test Azure file shares backup in China North 3.
So, could you please help to double check this issue and update the article accordingly? Thanks.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 57659ffa-1319-269b-246c-6b3c9943a25c
Version Independent ID: a010c014-b116-5032-bc4b-627a893b1477
Content: Support Matrix for Azure file share backup - Azure Backup
Content Source: articles/backup/azure-file-share-support-matrix.md
Service: backup
GitHub Login: @v-amallick
Microsoft Alias: v-amallick

@Johnnytechn Thank you for posting this question. We will review the content with the doc owner and update as appropriate.

Hi @Johnnytechn - we have updated the supported region section in the Azure File share article using PR #214555; the updates will be live soon.
@SadiqhAhmed-MSFT - FYI, as there are no further doc updates needed, closed this issue.
Thanks!
#please-close


User Interface Improvements [session close]

Description

Some minor changes in UI.

Remove linear gradient in the close button
Added [closed] label when the tab is closed
Removed the close button after the tab is closed.
Re-indent code

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

@satanb4, can you review it, please?


No longer generate JUnit, Reactor Test, and SLF4J Simple dependencies

No longer generate JUnit, Reactor Test, and SLF4J Simple dependencies in test in POMs. These dependencies are now managed by azure-core-test and should not be added manually.

No changes needing a change description found.

You can try these changes here

🛝 Playground
🌐 Website
📚 Next docs


Sound engineering principles are telling me to fix everything that is "wrong" inside this code first.

One can either develop on Ad-Hoc basis. i.e. "debug" as bugs come along, or one can make the code more resilient and then debug the many bugs that will appear. Just like lifting the proverbial rock :)
I am here to help not to criticize. Unless help is not wanted.
One (probably unrelated to this bug) example: this code has no local static functions.  Thus "everything" is in essence global. Which works until it does not. I might fix this on the "my side" but will it be accepted?
Sound engineering principles are telling me to fix everything that is "wrong" inside this code first. And then hunt for the bugs. Starting with  application design. In (small) manageable steps.

Unfortunately what's "wrong" with the code is a little subjective.
Taking the example here, you appear to acknowledge that using globals instead of statics hasn't really been a source of bugs.  (One could imagine bugs preventable with statics if globals were generating namespace collisions, but that seems unlikely with such a small amount of code.)  At the same time, it seems understood that making the changes here run a decent chance of introducing bugs.
The other thing I'd point out, and this goes back to my earlier post about not really sharing a vision, is that a lot of language changes are incompatible with running on older systems, so some of these changes would end up driving a hard fork in the code.  Whether it's a big deal depends on the value each individual places on downlevel support.
The bug in the other thread seemed to me to result from some bad design choices in Win32.  Unfortunately winfile is stuck with some of those choices by virtue of being Win32.  About the best it can do is abstract away the Win32-ness (eg. have wrapper functions that return the error without depending on a subsequent call to GetLastError.)
The big bugs I'm seeing stem from being an old codebase that was trying to be maximally compact by overloading bits which made sense when it was written but today just seems like the wrong tradeoff.  Those are tedious to change, but they don't require any language/compiler/library support to fix.

From my own experience over the years, I have gone through my personal phases of reorganizing my own systems and refactoring my code because of theoretical benefit. When I would get started, I'd be at a high point, excited about improving the back end structure. But as work piled up one over other, especially when having to fix more and more unforeseen effects of a particular change, I would always end up feeling a bit of regret taking on a massive task, pursuing some perceived efficiency that really didn't seem to make much practical difference on the end product.
So I had eventually changed my personal strategy. No, I didn't just give up improving things in the back end or refactoring code or restructuring my work flow. But rather than creating a massive project or task to "fix" things, I now try to take on a particular or improving things as their need arrives. When I see something that can directly benefit from refactoring, I thake the opportunity to do that, which improves a bit of the back end while having an impact on the end result as well.
The end result is that over a long period of time, I notice that a lot of things have been fixed through small, incremental, changes that didn't feel that daunting.
My belief is that changes in Winfile should take this approach. An application that is "mature", i.e. done, can benefit in following this model. So far, we are looking at a particular need, isolating it, making it bite-size, and addressing that need. Some changes improve on a previous commit. And we have already "modernized" portions of the code (such as adding a manifest file) as their need arrived.
I'm confident that over the long term, much of the code will be fixed, as more and more changes are made.
As for keeping the look and feel of the "classic" Winfile, that is, indeed, the vision, for a lack of a better word, for now. However, I must remind us all that an application can be modern while keep the "classic" feel. Take a look at Visual Studio IDE. It still has the classic feel of VS and VB6 IDE; yet it incorporates almost all modern UI guidelines, including tearing tabs, dark mise, dynamic workspace, etc.
What will be the state of Winfile in a few years remains a mystery, and that's what I love about software development. We see our work shaping a product over the years that we ourselves wouldn't have imagined.
Best

I do understand the wider context of this project, still @malxau nailed it: "not really sharing a vision".
In the mean time, I shall "plough" on my side ...  with what I think are no brainers.  Like using _ASSERTE and a such ...  Just a common sense, nothing pompous.
Seeing the code from primordial soup of WIN development is fascinating. Thank you @craigwi .

Yup, the individual "no-brainer" changes can be short PRs, in keeping the way it's been done so far and seems to work pretty well.

@NazmusLabs  well can I then submit a PR , fixing these 147 "no brainers" VS2017 Code Analyzer is reporting?  One might think to fix these first and then go bug hunting? Here is the list for everyones perusal ...
vs2017 code analyzer tool rezult.txt

Yeah, I'd just submit a PR report with these fixes. It allows us to download and test the app for compat issues.

@craigwi  I submitted the PR to solve the Warning C6400. Just a solution not the use of it which requires a knowledge of the WINFILE internals which I do not have.

@DBJDBJ, because your solution is not complete ("Just a solution not the use of it"), I will not accept it as is.  Furthermore, it includes files not related to the purpose of the commit.  In case you haven't read #88, please do.  Changing WinFile is hard and it takes time to understand things (the "internals" as you call it).

@craigwi  Agreed. I am sure you can see this is all about PR #88, mainly point 2.  I shall close the PR #156 and redo it properly. As for using it I shall do that too.  The key to the solution is to (have and) use the string ordinal comparisons when appropriate and  UI strings comparison when locale is involved.


doc: Change the user name in the doc to myuser

I was testing ubuntu containerdisk image with the example in the doc, and I could not ssh into the vm with error ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain.
After some investigations it turns out the user admin cannot be added by cloud-init, since the name admin conflicts with predefined user group admin in the OS.
This PR changes the user name to myuser to avoid conflict with predefined names.

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

NONE

/ok-to-test

thank you!
/cc @lyarwood

IMHO the example is wrong, it should be using the default ubuntu user without creating any additional users.
$ cat ubuntu.yaml
[..]
      volumes:
      - containerDisk:
          image: quay.io/containerdisks/ubuntu:22.04
        name: containerdisk
      - cloudInitNoCloud:
          userData: |
            #cloud-config
            ssh_authorized_keys:
              - ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAvt7H8ZxcIjlxTg6LTOwVXdM1oi5GTv29y9vdtwlcNPJmRpjiNgITQWiXmyjwZA+h5838HZkwbXVkIYxzJFAUMobFm2SDgapHbFUzOMONhFxbDLouxtDbjsoiwqewFFTZE0N20ayPxdjDLkEImQ/dKpna+EggYQSNpM8c+sitJ67wpHdudYQqnov4Or/gcD1GKE8LvV/G9SKTWNLCb5I/u6I37vpDYikRN2IiNtlCiHZMFLxmtf/MfJPhzKzN83wYdV3h7iWN7GTFDRIAkTn8tiQZDUQSU+iJLXC86zl5fQ1ME2AlhRR0WHFITbLOy/6Hi3OmLOCGKNfB3RiG4uwLNw==<EMAIL_ADDRESS>$ ./cluster-up/kubectl.sh apply -f ubuntu.yaml && ./cluster-up/virtctl.sh console ubuntu
[..]
ubuntu login: [   16.513205] cloud-init[1208]: Cloud-init v. 22.4.2-0ubuntu0~22.04.1 running 'modules:final' at Tue, 18 Apr 2023 14:30:41 +0000. Up 16.49 seconds.
ci-info: +++++++++++++++++++++++++++++++++++Authorized keys from /home/ubuntu/.ssh/authorized_keys for user ubuntu++++++++++++++++++++++++++++++++++++
ci-info: +---------+-------------------------------------------------------------------------------------------------+---------+---------------------+
ci-info: | Keytype |                                       Fingerprint (sha256)                                      | Options |       Comment       |
ci-info: +---------+-------------------------------------------------------------------------------------------------+---------+---------------------+
ci-info: | ssh-rsa | c4:68:8d:df:13:cd:da:f3:a2:54:78:03:a0:45:44:9e:a9:9a:05:0b:9f:75:df:48:32:f2:8b:dd:73:60:47:1f |    -    |<EMAIL_ADDRESS>|
ci-info: +---------+-------------------------------------------------------------------------------------------------+---------+---------------------+
[..]
$ ./cluster-up/virtctl.sh ssh ubuntu@ubuntu
selecting docker as container runtime
Welcome to Ubuntu 22.04.2 LTS (GNU/Linux 5.15.0-67-generic x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management:     https://landscape.canonical.com
 * Support:        https://ubuntu.com/advantage

  System information as of Tue Apr 18 14:38:11 UTC 2023

  System load:  0.0               Processes:               107
  Usage of /:   72.6% of 1.96GB   Users logged in:         0
  Memory usage: 18%               IPv4 address for enp1s0: <IP_ADDRESS>
  Swap usage:   0%

Expanded Security Maintenance for Applications is not enabled.

0 updates can be applied immediately.

Enable ESM Apps to receive additional future security updates.
See https://ubuntu.com/esm or run: sudo pro status

The list of available updates is more than a week old.
To check for new updates run: sudo apt update

The programs included with the Ubuntu system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
applicable law.

To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

ubuntu@ubuntu:~$

@lyarwood  Thanks, I confirm that using default ubuntu user with configured ssh_authorized_keys also works well. Feel free to close this PR and open another PR to fix then 👍

@xiaoPierre thanks, I've raised issue #61 and will track a more complete fix there, it's likely we will also need to change the examples for fedora etc as well.

/close


Can not use Multiple PS Eyes even with CL Eye SDK.

Hello. I bought the CL Eye SDK so that I could use multiple PS Eyes. I have 2 and they both work great. The problem is this: If I have the standard driver installed both of them work fine. Whenever I test one it works flawlessly. If I remove the standard 1 camera driver and install the CL Eye SDK Both cameras work but only in the provided demos from CL Eye. I know that they're both detected in the CL Eye Device Manager and that theyre working as the SDK demos show the 2 cameras and their image working perfectly however PSMoveService does not recognize or use those. I have chosen the developer version of the SDK which allows for the 2 free cameras. The only way for me to make it work is to install the standard 1 camera driver but then the second camera doesnt work.
So do I have to install both the standard driver and the SDK at the same time? That only shows 1 camera. If I only have the SDK their demos work fine with the cameras but PSMoveService does not detect them at all with the SDK. What do I have to to to make PSMoveService recognize that there are cameras connected with the SDK.
OS: Windows 10 x64
Camera driver: Have both CL Eye SDK and normal CL Eye Driver
Camera: 2 PS Eyes for PS3.
What do I have to do to make PSMoveService recognise the cameras with the SDK. Simply installing it does not work and they are not recognized. The CL Eye Multicam demos work fine.

Personally I'd say give up on CL-Eye and use libusb-win32. I have three PSEyes working just fine. However, if you really want to use it, have you gone through what they say in #74? I'm reluctant to troubleshoot it myself since I'd have to break my setup in the process. HipsterSloth is working on improving the PSEye integration.

Yes. I got that idea already but libUSB just simply doesn't work like I
need it to. Its 100% fine with 1 camera but as soon as I plug in the second
one and start the test again it just shows 2 green windows. Its solid
color. Both of the cameras work absolutely fine on their own but together
its just 2 green windows.
On Thu, Jun 30, 2016 at 12:50 PM, William<EMAIL_ADDRESS>wrote:

Personally I'd say give up on CL-Eye and use libusb-win32. I have three
PSEyes working just fine. However, if you really want to use it, have you
gone through what they say in #74
https://github.com/cboulay/PSMoveService/issues/74? I'm reluctant to
troubleshoot it myself since I'd have to break my setup in the process.
HipsterSloth is working on improving the PSEye integration.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cboulay/PSMoveService/issues/85#issuecomment-229613852,
or mute the thread
https://github.com/notifications/unsubscribe/AEuvEQTkvyA8DYD7eJAQJl8j47iSFno_ks5qQ5FlgaJpZM4JB-Dw
.

Check if turning off your headset resolves the problem. If it does, then it's the same problem as me : try to plug your cameras and headset in multiple usb controllers, and switch ports if it still do not work unitl it work (that's how i got it working). Also, try to uninstall all the USB Camera-B<IP_ADDRESS> (Interface 1) in usbdeview.


Add "Guides for parents, carers & students" page

Context
Changes proposed in this pull request
Guidance to review

 Add "Guides for parents, carers and pupils"


Expand collapsed arrays on schema validation error

Maybe not an issue; but curious to if anyones done something similar/has any ideas.
I've created a custom array type that uses bootstrap accordions. Works great. However, when the submit button validates the form, the accordion remains collapsed even though it contains invalid form fields
I would like to somehow get the offending accordion to automatically expand.
I thought about creating an attr directive that sits on the accordion that listens for an event, and has access to the AccordionController from bootstrap. With the $index I could call toggleOpen().
Thoughts?

Interesting... maybe you could wrap each accordions fields inside an ng-form, I haven't tried it, but I understand they can be nested? Then you could get validation status directly from the form controller and maybe do something with that. Sounds cool!

 And thats exactly what I did.
Heres the gist
https://gist.github.com/deyceg/84cd2428a6c8291de66a

:+1: Nice! Love to see an add-on of it if you get time ;)

@davidlgj Definately! It'll be the weekend after easter though as I'm a little snowed under with a client at the moment with a deadline approaching!
I have a couple of other useful extensions too but I'll keep those a surprise!

Ooooh cool! let, me now if I can help!

@davidlgj Didn't want to create a new issue, but have some additional discussion along similar lines.
I'm working on an modal type where we can take a fieldset out of the form and place it inside a modal window with its own schema-form lifecycle. Must admit I havent got very far yet although I did something similar with my own form controls a while back without the desired flexibility we'd need here though.
My current trail of thought is to wait for the fieldset to be rendered, then move the dom element into the modal whilst somehow keeping it bound to the original scope (read: transclusion).
The issues I'm running into however are two-fold:

Angular-UIs bootstrap modal accepts a $scope parameter for $modal.open(), but it creates a child scope of this scope, rather than binding the template to the sf-decorator scope.

Accessing the model passed into schema-form. I can't seem to locate it anywhere although I might just be looking in the wrong place. I was hoping it was on the $parent of the sf-decorator scope.

Any ideas/thoughts appreciated :)

Why not just render the form again inside the modal and then hide the other? Since they both bind against the same model that should work. Moving the DOM nodes around seems tricky... sorry I don't think I have any better answer :)

@deyceg how did you go with this one, did you ever get a chance to make an add on? #800 just got added by someone looking for a solution to use.

@Anthropic I did create schema-form-modal although I havent published it! Heres the component:
'use strict';

angular
  .module('schema-form-modal')
  .directive('sfModal', modal)
  .directive('sfTransclude', function ($compile) {
    return {
      restrict: 'A',
      transclude: true,
      link: function ($scope, $element, $attrs, controller, $transclude) {
        $transclude($scope.$parent, function (clone, scope) {
          $element.empty();
          $element.append(clone);
        });
      }
    }
  })
  .controller('ModalCtrl', ModalCtrl);

function modal($compile, $modal) {
  var modalTmpl =
    '
'+
    '
'+
    'Close'+
    '
'+
    '
' +
    '
'+
    '
'+
    '<button type="button" class="schema-form-modal-submit" ng-click="submit()">Submit</button>'+
    '
'+
    '
';

  var ddo = {
    scope: false,
    compile: compiler
  };

  return ddo;

  ///////////

  function compiler(element) {
    //remove contents of sf-decorator and insert into modal
    var children = element.children();

    // Wrap the children in our template
    var tmpl = angular.element(modalTmpl);
    tmpl.find('.modal-body').append(children);

    return linker;

    function linker(scope, elem, attrs, controller, transcludeFn) {
      var form = scope.$eval(attrs.wwModal);

      scope.btnText = !!form ? form.title : 'Open';
      scope.open = openModal;

      var openBtn = $compile('<button type="button" class="schema-form-modal-open" ng-click="open()">{{btnText}}</button>')(scope);

      //Add button to sf-decorator
      elem.append(openBtn);

      function openModal() {
        scope.modalInstance = $modal.open({
          template: tmpl.html(),
          scope: scope,
          controller: 'ModalCtrl',
          backdrop: 'static',
          windowClass: form ? form.modalClass : ''
        });
      }
    }
  }
}

function ModalCtrl($scope, $modalInstance) {
  $scope.close = closeModal;

  $scope.submit = submit;

  function closeModal() {
    $modalInstance.dismiss(1); //do nothing
  }

  function submit() {
    $modalInstance.close(0);
  }
}

@deyceg thanks for that! :)

@Anthropic No problem! FYI I was using 0.8.x of schema-form!

Can any help me integrating and using https://gist.github.com/deyceg/6a3bfe870f258ef839b3aaf6b1c5a912 in my project?


Issue while creating the reconstructed data cube

Hello.
I'm trying to do analysis on a MUSE ifu and constantly being encountered with the same error at the step where I try to reconstruct the datacube.

I have tried to run the example fits file but it still shows the same error. Although while trying multiple times, at one point it does actually worked but when i tried again the error comes back.
I would be grateful if you could help me out.
Thanks
Arshi Ali

Hi, Arshi.  Could you please post or link your options and line list?  This will start to help me figure out what might have gone wrong.

BADASS3_ifu_MUSE.zip

Thank, Arshi.  @smd1526 informed me that the latest version of the code does make sure to check for the key that is causing your error.  Is your version of the code the latest version?

I think I'm using the latest version... although I have downloaded the repository around July so I'm not sure if there has been any update after that.

Hi Remington,
Just letting you know that the problem is been solved . I guess the issue was indeed related to the updates. Thanks for the suggestions.
Thanks
Arshi


update description of integrations

Closes #51 .

@oalders would you mind looking at the changed text and let me know if it makes more sense? Thanks.


python312Packages.teslajsonpy: 3.12.0 -> 3.12.1

Diff: https://github.com/zabuldon/teslajsonpy/compare/refs/tags/v3.12.0...v3.12.1
Changelog: https://github.com/zabuldon/teslajsonpy/releases/tag/v3.12.1
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 345281 run on x86_64-linux 1

4 packages built:

python311Packages.teslajsonpy
python311Packages.teslajsonpy.dist
python312Packages.teslajsonpy
python312Packages.teslajsonpy.dist


python: How adbc_driver_manager.AdbcConnection gets outgoing call headers

I use Python adbc_driver_flightsql to connect to Flight SQL Server implemented in Java, my Arrow Flight SQL Server implements Auth2 CallHeaderAuthenticator, and the AuthResult returned by authenticate contains the Bearer Token.
db = adbc_driver_flightsql.connect(uri="grpc://xxx:xx", db_kwargs={
            adbc_driver_manager.DatabaseOptions.USERNAME.value: "root",
            adbc_driver_manager.DatabaseOptions.PASSWORD.value: "",
        })
conn = adbc_driver_manager.AdbcConnection(db)

It looks like the Bearer Token is in the outgoing call headers and I want to get the Bearer Token from Python adbc_driver_manager.AdbcConnection and use it afterwards, like this:
db = adbc_driver_flightsql.connect(uri="grpc://xxx:xxx", db_kwargs={
            adbc_driver_flightsql.DatabaseOptions.AUTHORIZATION_HEADER.value: "Bearer <token>",
        })
conn = adbc_driver_manager.AdbcConnection(db)

I need help, thanks~

Hmm, what are you trying to accomplish? We already send the bearer token back to the server in future requests - you don't need to explicitly set it.

All I need is send the bearer token back to the server in future requests, is this supported on ADBC 0.6?
When I tested on python ADBC 0.6 the bearer token did not return to the server

AuthResult is returned like this:
private AuthResult createAuthResultWithBearerToken(String token) {
        return new AuthResult() {
            @Override
            public void appendToOutgoingHeaders(CallHeaders outgoingHeaders) {
                outgoingHeaders.insert(Auth2Constants.AUTHORIZATION_HEADER,
                        Auth2Constants.BEARER_PREFIX + token);
            }

            @Override
            public String getPeerIdentity() {
                return token;
            }
        };
    }

In fact I'm referring to Dremio's BearerTokenAuthenticator.
thanks! , I will try a nightly build

cool! , indeed send the bearer token back to the server.
I observed:
When creating adbc_driver_manager.AdbcConnection, the bearer token returned by authentication will only be used once (used in the first RPC getFlightInfoSqlInfo).
After that, the first statement request will generate a new bearer token again, and subsequent statement requests will send the bearer token back to the server.
Is this expected? This has misled me before.

Sorry, can you elaborate? Does any request get sent without a bearer token?

Sorry, the above description is not accurate, correction:
adbc_driver_manager.AdbcConnection will trigger authenticate 4 times, two of the handshakes will use BASIC_PREFIX, Why do we need two handshakes?
1.
methodName: arrow.flight.protocol.FlightService/Handshake
incomingHeaders: authorization=Basic cm9vdDo
2.
methodName: arrow.flight.protocol.FlightService/GetFlightInfo
incomingHeaders: authorization=Bearer test_token)
3.
methodName: arrow.flight.protocol.FlightService/Handshake
incomingHeaders: authorization=Basic cm9vdDo
4.
methodName: arrow.flight.protocol.FlightService/DoGet
incomingHeaders: authorization=Bearer test_token)
stmt.execute_query() will trigger the fifth authenticate, correct use of bearer tokens:
5.
methodName: arrow.flight.protocol.FlightService/GetFlightInfo
incomingHeaders: authorization=Bearer test_token)
import pyarrow

import adbc_driver_flightsql.dbapi as flight_sql
import adbc_driver_flightsql
import adbc_driver_manager

db = adbc_driver_flightsql.connect(uri="grpc://<IP_ADDRESS>:10478", db_kwargs={
            adbc_driver_manager.DatabaseOptions.USERNAME.value: "root",
            adbc_driver_manager.DatabaseOptions.PASSWORD.value: "",
        })

conn = adbc_driver_manager.AdbcConnection(db)

stmt = adbc_driver_manager.AdbcStatement(conn)

stmt.set_sql_query("select * from tpch.hdf5 limit 1000000;")
stream, rows = stmt.execute_query()

CC @zeroshade

Hmm, that's definitely odd that it's triggering that many authentications, generally that would mean it's creating multiple connections (we do the auth whenever we start a connection), which might make sense if it was sending back multiple FlightEndpoints (since we attempt to download them in parallel) but I'm pretty sure that dremio doesn't do that (unless they've changed it). So i'll take a look and see if i can figure out why it's initializing so many handshakes and connections and get back to you

https://github.com/apache/arrow-adbc/issues/1087

Thanks, I will add more information later.

Solved, impl auth2 in Arrow 13.0.
Close this issue.


Any solution to focus Input

I'm having an issue with focus on-load  in . Seems refs is breaking things. Any solutions welcome.
Thanks.

Can you make a simple example in http://codesandbox.io?


#867: Remove ksonnet from AWS Azure deployment pages

Removed references to ksonnet on AWS deployment page
Removed references to ksonnet on Azure deployment page
Removed unnecessary whitespace

This change is

/ok-to-test
/assign @richardsliu

/cc @Jeffwan
/cc @mohona17

@richardsliu I think I did what you wanted.

/lgtm
/approve


SDK changes for Vmss Flex deleteOption

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

/azp run net - mgmt - ci

/azp run net - mgmt - ci

/azp run net - mgmt - ci


Use new shib idp, use yaml inventory

As discussed, the solr servers in the vagrant (dev) inventory need a default of:
state: present
Also, the solr group needs to be a child of the dev group


(macOS) connect remote docker server over ssh is failed

ENV
macOS Mojave version 10.14.1
dockstation v1.4.1
macOS Docker version 18.09.0, build 4d60db4
RemoteServer CentOS7 Docker version 18.09.0-ce-beta1, build 78a6bdb
Problem
connect remote docker server over ssh is failed

Connection to /var/run/docker.sock on remote server failed.(SSH) Channel open failure: open failed

I use docker -H ssh://user@remoteServerIP command. CLI is worked.

Same problem here.

тоже не могу подключиться, хотя из консоли подключение происходит по команде docker -H ssh://root@ip

I am having same problem. Any solution or am I missing some type of configuration? This is with Amazon EC2 instance.

I am having same problem.

Same issue here with local Synology NAS

I had the same problem. The ssh user I was logging in with didn't have permission to access docker.sock
Giving user permission to access docker.sock
https://stackoverflow.com/questions/48568172/docker-sock-permission-denied

We are forwarding a tunnel through SSH. Please check that you have a possibility to open SSH tunnels.

What solved this for me was, on my remote host, checking sshd_config for AllowTcpForwarding. It needs to not be set to no. Commenting out the line worked. You may also need to set PermitTunnel yes as well.

ok just want to share, this what works for me using docker socket 2375 (ssh port 22 not working for me)


Make TAP::Harness and TAP::Parser optional.

In OpenSSL 1.1.1 the script run_tests.pl has an effectiver
workaround to fall back to Test::Harness, if TAP::Harness
is not available. That code has substantially changed,
but it seems it should still fall back but doesn't.
Observed on SuSE Linux Enterprise Server 11 (SLES11).
Error messages:
Can't locate TAP/Parser.pm in @inc (@inc contains: /path/to/bld/openssl300/test/../util/perl /path/to/local/perl/lib/perl5 /usr/lib/perl5/5.10.0/x86_64-linux-thread-multi /usr/lib/perl5/5.10.0 /usr/lib/perl5/site_perl/5.10.0/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.10.0 /usr/lib/perl5/vendor_perl/5.10.0/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.10.0 /usr/lib/perl5/vendor_perl .) at /path/to/local/perl/lib/perl5/parent.pm line 20.
BEGIN failed--compilation aborted at /path/to/bld/openssl300/test/run_tests.pl line 131.
and
Can't locate TAP/Harness.pm in @inc (@inc contains: /path/to/bld/openssl300/test/../util/perl /path/to/local/perl/lib/perl5 /usr/lib/perl5/5.10.0/x86_64-linux-thread-multi /usr/lib/perl5/5.10.0 /usr/lib/perl5/site_perl/5.10.0/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.10.0 /usr/lib/perl5/vendor_perl/5.10.0/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.10.0 /usr/lib/perl5/vendor_perl .) at /path/to/local/perl/lib/perl5/parent.pm line 20.
BEGIN failed--compilation aborted at /path/to/bld/openssl300/test/run_tests.pl line 215.
Concerning the fix: the docs for parent.pm show, that without
the "-norequire" it puts the require statement in a BEGIN block
which probably runs before the eval, to the loading is no
longer encapsulated by the eval. Without the additional require
line, the loading doesn't happen at all, so the availability
testing fails. Combining the "-norequire" and an explicit
"require" worked for me.
Tested on the original problem platform SLES 11, but also on
SLES 12 and 15, RHEL 6, 7 and 8 plus Solaris 10 Sparc.
Fixes #12352

Checklist

[ ] documentation is added or updated
[ ] tests are added or updated

Close/reopen to kick CLA bot

I can't look at the output of the single test run that failed on Travis. So I can't check, whether that's an unrelated failure or not.

Kicking it off again to see if the issue has resolved itself.

This PR is in a state where it requires action by @openssl/committers but the last update was 30 days ago

LGTM, second review needed.

This pull request is ready to merge

Merged. Thank you for the PR and for the patience with the reviews.


Cannot start spyder5.4.1

Spyder, which has always been updated with Pip, does not like anaconda. The latest version 5.4.1 of Spyder was updated a few days ago, and it cannot be started. Several new Python environments have been reset. The first thing is to install Spyder 5.4.1. From 3.11.1 to 3.11.0 to 3.10, it cannot be started.

Hey @jy99846025, thanks for reporting. You said

Spyder, which has always been updated with Pip, does not like anaconda.

If you're using pip to update Spyder in Anaconda, please stop doing it. That's a terrible practice because conda and pip packages are binary incompatible, which leads to all sorts of strange problems. Furthermore, we recommend you to remove and reinstall Anaconda, as described in our video.
In the future, we recommend you to use conda-forge to get the latest Spyder and use a dedicated conda environment to install/update it, as described in our documentation.

The latest version 5.4.1 of Spyder was updated a few days ago, and it cannot be started. Several new Python environments have been reset. The first thing is to install Spyder 5.4.1. From 3.11.1 to 3.11.0 to 3.10, it cannot be started.

This looks like a duplicate of issue #20097, so I'm going to close it in favor of that issue since you didn't provide more details about the problem.


cannot open client HELLO -- wrong server key?

docker-compose version 1.23.1, build b02f1306
Docker version 18.09.1, build 4c52b90
Does someone know how to resolve this issue, one of my guess would be do set IP and IPS manually in te Dockerfile but I don't know what to add there.
WARNING: The IP variable is not set. Defaulting to a blank string.
WARNING: The IPS variable is not set. Defaulting to a blank string.
Creating von_node4_1_6fa17919a466 ... done
Creating von_node1_1_5476b390308f ... done
Creating von_node2_1_4a9d0ef05463 ... done
Creating von_node3_1_fb60e3651b93 ... done
Creating von_von-web_1_e7c2cd2e1876 ... done
Attaching to von_node4_1_8a0db220c2a0, von_node1_1_5607204968b3, von_node3_1_93ef0a741eb2, von_node2_1_862571c6cde1, von_von-web_1_9cac5775c7b9
node4_1_8a0db220c2a0 | Ledger exists - using...
node4_1_8a0db220c2a0 | start_indy_node Node4 9707 9708
node4_1_8a0db220c2a0 | 2019-01-24 10:56:41,137 | DEBUG    | init.py          (60) | register | Registered VCS backend: git
node4_1_8a0db220c2a0 | 2019-01-24 10:56:41,162 | DEBUG    | init.py          (60) | register | Registered VCS backend: hg
node4_1_8a0db220c2a0 | 2019-01-24 10:56:41,224 | DEBUG    | init.py          (60) | register | Registered VCS backend: svn
node4_1_8a0db220c2a0 | 2019-01-24 10:56:41,225 | DEBUG    | init.py          (60) | register | Registered VCS backend: bzr
node4_1_8a0db220c2a0 | 2019-01-24 10:56:42,879 | DEBUG    | selector_events.py   (53) | init | Using selector: EpollSelector
node4_1_8a0db220c2a0 | 2019-01-24 10:56:42,904 | DEBUG    | ledger.py            (201) | start | Starting ledger...
node4_1_8a0db220c2a0 | 2019-01-24 10:56:42,916 | DEBUG    | ledger.py            (67) | recoverTree | Recovering tree from transaction log
node4_1_8a0db220c2a0 | 2019-01-24 10:56:42,948 | DEBUG    | ledger.py            (82) | recoverTree | Recovered tree in 0.032732644001953304 seconds
node4_1_8a0db220c2a0 | 2019-01-24 10:56:43,016 | DEBUG    | ledger.py            (201) | start | Starting ledger...
node4_1_8a0db220c2a0 | 2019-01-24 10:56:43,028 | DEBUG    | ledger.py            (67) | recoverTree | Recovering tree from transaction log
node4_1_8a0db220c2a0 | 2019-01-24 10:56:43,060 | DEBUG    | ledger.py            (82) | recoverTree | Recovered tree in 0.03139139600170893 seconds
node4_1_8a0db220c2a0 | 2019-01-24 10:56:43,071 | INFO     | node.py              (2636) | initStateFromLedger | Node4 found state to be empty, recreating from ledger
node4_1_8a0db220c2a0 | 2019-01-24 10:56:43,093 | INFO     | node.py              (786) | _create_bls_bft | BLS: BLS Signatures will be used for Node Node4
node4_1_8a0db220c2a0 | 2019-01-24 10:56:43,106 | INFO     | node.py              (2636) | initStateFromLedger | Node4 found state to be empty, recreating from ledger
node4_1_8a0db220c2a0 | 2019-01-24 10:56:43,108 | INFO     | node.py              (612) | setPoolParams | Node4 updated its pool parameters: f 0, totalNodes 1, allNodeNames {'Node4'}, requiredNumberOfInstances 1, minimumNodes 1, quorums {'bls_signatures': Quorum(1), 'propagate': Quorum(1), 'observer_data': Quorum(1), 'prepare': Quorum(0), 'view_change_done': Quorum(1), 'election': Quorum(1), 'propagate_primary': Quorum(1), 'reply': Quorum(1), 'same_consistency_proof': Quorum(1), 'view_change': Quorum(1), 'commit': Quorum(1), 'consistency_proof': Quorum(1), 'f': 0, 'checkpoint': Quorum(0), 'timestamp': Quorum(1), 'ledger_status': Quorum(0)}
node4_1_8a0db220c2a0 | 2019-01-24 10:56:43,235 | INFO     | plugin_loader.py     (118) | _load | plugin FirebaseStatsConsumer successfully loaded from module plugin_firebase_stats_consumer
node4_1_8a0db220c2a0 | 2019-01-24 10:56:43,236 | DISPLAY  | replicas.py          (41) | grow | Node4 added replica Node4:0 to instance 0 (master)
node4_1_8a0db220c2a0 | 2019-01-24 10:56:43,237 | DEBUG    | plugin_helper.py     (23) | loadPlugins | Plugin loading started to load plugins from plugins_dir: /var/lib/indy/plugins
node4_1_8a0db220c2a0 | 2019-01-24 10:56:43,237 | DEBUG    | plugin_helper.py     (63) | loadPlugins | Total plugins loaded from plugins_dir /var/lib/indy/plugins are : 0
node4_1_8a0db220c2a0 | 2019-01-24 10:56:43,285 | DEBUG    | ledger.py            (201) | start | Starting ledger...
node4_1_8a0db220c2a0 | 2019-01-24 10:56:43,303 | DEBUG    | ledger.py            (67) | recoverTree | Recovering tree from transaction log
node4_1_8a0db220c2a0 | 2019-01-24 10:56:43,343 | DEBUG    | ledger.py            (82) | recoverTree | Recovered tree in 0.04053984500205843 seconds
node4_1_8a0db220c2a0 | 2019-01-24 10:56:43,374 | INFO     | node.py              (2636) | initStateFromLedger | Node4 found state to be empty, recreating from ledger
node4_1_8a0db220c2a0 | 2019-01-24 10:56:43,374 | DEBUG    | ledger.py            (199) | start | Ledger already started.
node4_1_8a0db220c2a0 | 2019-01-24 10:56:43,375 | DEBUG    | ledger.py            (199) | start | Ledger already started.
node4_1_8a0db220c2a0 | 2019-01-24 10:56:43,375 | DEBUG    | ledger.py            (199) | start | Ledger already started.
node4_1_8a0db220c2a0 | 2019-01-24 10:56:43,376 | DEBUG    | authenticator.py     (31) | start | Starting ZAP at inproc://zeromq.zap.1
node4_1_8a0db220c2a0 | 2019-01-24 10:56:43,376 | DEBUG    | base.py              (72) | allow | Allowing <IP_ADDRESS>
node4_1_8a0db220c2a0 | 2019-01-24 10:56:43,377 | DEBUG    | base.py              (112) | configure_curve | Configure curve: *[/var/lib/indy/sandbox/keys/Node4/public_keys]
node4_1_8a0db220c2a0 | 2019-01-24 10:56:43,387 | INFO     | stacks.py            (84) | start | CONNECTION: Node4 listening for other nodes at <IP_ADDRESS>:9707
node4_1_8a0db220c2a0 | 2019-01-24 10:56:43,389 | DEBUG    | authenticator.py     (31) | start | Starting ZAP at inproc://zeromq.zap.2
node4_1_8a0db220c2a0 | 2019-01-24 10:56:43,389 | DEBUG    | base.py              (72) | allow | Allowing <IP_ADDRESS>
node4_1_8a0db220c2a0 | 2019-01-24 10:56:43,389 | DEBUG    | base.py              (112) | configure_curve | Configure curve: []
node4_1_8a0db220c2a0 | 2019-01-24 10:56:43,391 | INFO     | node.py              (853) | start | Node4 first time running...
node3_1_93ef0a741eb2 | Ledger exists - using...
node3_1_93ef0a741eb2 | start_indy_node Node3 9705 9706
von-web_1_9cac5775c7b9 | Ledger exists - using...
node2_1_862571c6cde1 | Ledger exists - using...
node2_1_862571c6cde1 | start_indy_node Node2 9703 9704
node1_1_5607204968b3 | Ledger exists - using...
node1_1_5607204968b3 | start_indy_node Node1 9701 9702
node1_1_5607204968b3 | 2019-01-24 10:56:42,527 | DEBUG    | init.py          (60) | register | Registered VCS backend: git
node1_1_5607204968b3 | 2019-01-24 10:56:42,547 | DEBUG    | init.py          (60) | register | Registered VCS backend: hg
node1_1_5607204968b3 | 2019-01-24 10:56:42,606 | DEBUG    | init.py          (60) | register | Registered VCS backend: svn
node1_1_5607204968b3 | 2019-01-24 10:56:42,607 | DEBUG    | init.py          (60) | register | Registered VCS backend: bzr
node1_1_5607204968b3 | 2019-01-24 10:56:44,066 | DEBUG    | selector_events.py   (53) | init | Using selector: EpollSelector
node1_1_5607204968b3 | 2019-01-24 10:56:44,094 | DEBUG    | ledger.py            (201) | start | Starting ledger...
node1_1_5607204968b3 | 2019-01-24 10:56:44,111 | DEBUG    | ledger.py            (67) | recoverTree | Recovering tree from transaction log
node1_1_5607204968b3 | 2019-01-24 10:56:44,149 | DEBUG    | ledger.py            (82) | recoverTree | Recovered tree in 0.037827896001545014 seconds
node1_1_5607204968b3 | 2019-01-24 10:56:44,213 | DEBUG    | ledger.py            (201) | start | Starting ledger...
node1_1_5607204968b3 | 2019-01-24 10:56:44,232 | DEBUG    | ledger.py            (67) | recoverTree | Recovering tree from transaction log
node1_1_5607204968b3 | 2019-01-24 10:56:44,275 | DEBUG    | ledger.py            (82) | recoverTree | Recovered tree in 0.04375988299943856 seconds
node1_1_5607204968b3 | 2019-01-24 10:56:44,292 | INFO     | node.py              (2636) | initStateFromLedger | Node1 found state to be empty, recreating from ledger
node1_1_5607204968b3 | 2019-01-24 10:56:44,317 | INFO     | node.py              (786) | _create_bls_bft | BLS: BLS Signatures will be used for Node Node1
node1_1_5607204968b3 | 2019-01-24 10:56:44,329 | INFO     | node.py              (2636) | initStateFromLedger | Node1 found state to be empty, recreating from ledger
node1_1_5607204968b3 | 2019-01-24 10:56:44,332 | INFO     | node.py              (612) | setPoolParams | Node1 updated its pool parameters: f 0, totalNodes 1, allNodeNames {'Node1'}, requiredNumberOfInstances 1, minimumNodes 1, quorums {'propagate': Quorum(1), 'timestamp': Quorum(1), 'prepare': Quorum(0), 'bls_signatures': Quorum(1), 'same_consistency_proof': Quorum(1), 'observer_data': Quorum(1), 'view_change': Quorum(1), 'consistency_proof': Quorum(1), 'election': Quorum(1), 'f': 0, 'ledger_status': Quorum(0), 'checkpoint': Quorum(0), 'propagate_primary': Quorum(1), 'commit': Quorum(1), 'view_change_done': Quorum(1), 'reply': Quorum(1)}
node3_1_93ef0a741eb2 | 2019-01-24 10:56:44,406 | DEBUG    | init.py          (60) | register | Registered VCS backend: git
node1_1_5607204968b3 | 2019-01-24 10:56:44,410 | INFO     | plugin_loader.py     (118) | _load | plugin FirebaseStatsConsumer successfully loaded from module plugin_firebase_stats_consumer
node1_1_5607204968b3 | 2019-01-24 10:56:44,412 | DISPLAY  | replicas.py          (41) | grow | Node1 added replica Node1:0 to instance 0 (master)
node1_1_5607204968b3 | 2019-01-24 10:56:44,413 | DEBUG    | plugin_helper.py     (23) | loadPlugins | Plugin loading started to load plugins from plugins_dir: /var/lib/indy/plugins
node1_1_5607204968b3 | 2019-01-24 10:56:44,413 | DEBUG    | plugin_helper.py     (63) | loadPlugins | Total plugins loaded from plugins_dir /var/lib/indy/plugins are : 0
node3_1_93ef0a741eb2 | 2019-01-24 10:56:44,424 | DEBUG    | init.py          (60) | register | Registered VCS backend: hg
node1_1_5607204968b3 | 2019-01-24 10:56:44,449 | DEBUG    | ledger.py            (201) | start | Starting ledger...
node1_1_5607204968b3 | 2019-01-24 10:56:44,460 | DEBUG    | ledger.py            (67) | recoverTree | Recovering tree from transaction log
node3_1_93ef0a741eb2 | 2019-01-24 10:56:44,470 | DEBUG    | init.py          (60) | register | Registered VCS backend: svn
node3_1_93ef0a741eb2 | 2019-01-24 10:56:44,471 | DEBUG    | init.py          (60) | register | Registered VCS backend: bzr
node1_1_5607204968b3 | 2019-01-24 10:56:44,490 | DEBUG    | ledger.py            (82) | recoverTree | Recovered tree in 0.03003599099974963 seconds
node1_1_5607204968b3 | 2019-01-24 10:56:44,503 | INFO     | node.py              (2636) | initStateFromLedger | Node1 found state to be empty, recreating from ledger
node1_1_5607204968b3 | 2019-01-24 10:56:44,506 | DEBUG    | ledger.py            (199) | start | Ledger already started.
node1_1_5607204968b3 | 2019-01-24 10:56:44,506 | DEBUG    | ledger.py            (199) | start | Ledger already started.
node1_1_5607204968b3 | 2019-01-24 10:56:44,507 | DEBUG    | ledger.py            (199) | start | Ledger already started.
node1_1_5607204968b3 | 2019-01-24 10:56:44,508 | DEBUG    | authenticator.py     (31) | start | Starting ZAP at inproc://zeromq.zap.1
node1_1_5607204968b3 | 2019-01-24 10:56:44,508 | DEBUG    | base.py              (72) | allow | Allowing <IP_ADDRESS>
node1_1_5607204968b3 | 2019-01-24 10:56:44,508 | DEBUG    | base.py              (112) | configure_curve | Configure curve: *[/var/lib/indy/sandbox/keys/Node1/public_keys]
node1_1_5607204968b3 | 2019-01-24 10:56:44,510 | INFO     | stacks.py            (84) | start | CONNECTION: Node1 listening for other nodes at <IP_ADDRESS>:9701
node1_1_5607204968b3 | 2019-01-24 10:56:44,510 | DEBUG    | authenticator.py     (31) | start | Starting ZAP at inproc://zeromq.zap.2
node1_1_5607204968b3 | 2019-01-24 10:56:44,511 | DEBUG    | base.py              (72) | allow | Allowing <IP_ADDRESS>
node1_1_5607204968b3 | 2019-01-24 10:56:44,511 | DEBUG    | base.py              (112) | configure_curve | Configure curve: []
node1_1_5607204968b3 | 2019-01-24 10:56:44,513 | INFO     | node.py              (853) | start | Node1 first time running...
node2_1_862571c6cde1 | 2019-01-24 10:56:45,240 | DEBUG    | init.py          (60) | register | Registered VCS backend: git
node2_1_862571c6cde1 | 2019-01-24 10:56:45,257 | DEBUG    | init.py          (60) | register | Registered VCS backend: hg
node2_1_862571c6cde1 | 2019-01-24 10:56:45,305 | DEBUG    | init.py          (60) | register | Registered VCS backend: svn
node2_1_862571c6cde1 | 2019-01-24 10:56:45,305 | DEBUG    | init.py          (60) | register | Registered VCS backend: bzr
node3_1_93ef0a741eb2 | 2019-01-24 10:56:45,445 | DEBUG    | selector_events.py   (53) | init | Using selector: EpollSelector
node3_1_93ef0a741eb2 | 2019-01-24 10:56:45,476 | DEBUG    | ledger.py            (201) | start | Starting ledger...
node3_1_93ef0a741eb2 | 2019-01-24 10:56:45,488 | DEBUG    | ledger.py            (67) | recoverTree | Recovering tree from transaction log
node3_1_93ef0a741eb2 | 2019-01-24 10:56:45,524 | DEBUG    | ledger.py            (82) | recoverTree | Recovered tree in 0.03575115900093806 seconds
node3_1_93ef0a741eb2 | 2019-01-24 10:56:45,568 | DEBUG    | ledger.py            (201) | start | Starting ledger...
node3_1_93ef0a741eb2 | 2019-01-24 10:56:45,580 | DEBUG    | ledger.py            (67) | recoverTree | Recovering tree from transaction log
node3_1_93ef0a741eb2 | 2019-01-24 10:56:45,609 | DEBUG    | ledger.py            (82) | recoverTree | Recovered tree in 0.029137293000530917 seconds
node3_1_93ef0a741eb2 | 2019-01-24 10:56:45,620 | INFO     | node.py              (2636) | initStateFromLedger | Node3 found state to be empty, recreating from ledger
node3_1_93ef0a741eb2 | 2019-01-24 10:56:45,635 | INFO     | node.py              (786) | _create_bls_bft | BLS: BLS Signatures will be used for Node Node3
node3_1_93ef0a741eb2 | 2019-01-24 10:56:45,647 | INFO     | node.py              (2636) | initStateFromLedger | Node3 found state to be empty, recreating from ledger
node3_1_93ef0a741eb2 | 2019-01-24 10:56:45,649 | INFO     | node.py              (612) | setPoolParams | Node3 updated its pool parameters: f 0, totalNodes 1, allNodeNames {'Node3'}, requiredNumberOfInstances 1, minimumNodes 1, quorums {'prepare': Quorum(0), 'election': Quorum(1), 'commit': Quorum(1), 'checkpoint': Quorum(0), 'view_change': Quorum(1), 'observer_data': Quorum(1), 'propagate_primary': Quorum(1), 'same_consistency_proof': Quorum(1), 'view_change_done': Quorum(1), 'bls_signatures': Quorum(1), 'timestamp': Quorum(1), 'f': 0, 'reply': Quorum(1), 'consistency_proof': Quorum(1), 'propagate': Quorum(1), 'ledger_status': Quorum(0)}
node3_1_93ef0a741eb2 | 2019-01-24 10:56:45,726 | INFO     | plugin_loader.py     (118) | _load | plugin FirebaseStatsConsumer successfully loaded from module plugin_firebase_stats_consumer
node3_1_93ef0a741eb2 | 2019-01-24 10:56:45,728 | DISPLAY  | replicas.py          (41) | grow | Node3 added replica Node3:0 to instance 0 (master)
node3_1_93ef0a741eb2 | 2019-01-24 10:56:45,728 | DEBUG    | plugin_helper.py     (23) | loadPlugins | Plugin loading started to load plugins from plugins_dir: /var/lib/indy/plugins
node3_1_93ef0a741eb2 | 2019-01-24 10:56:45,728 | DEBUG    | plugin_helper.py     (63) | loadPlugins | Total plugins loaded from plugins_dir /var/lib/indy/plugins are : 0
node3_1_93ef0a741eb2 | 2019-01-24 10:56:45,762 | DEBUG    | ledger.py            (201) | start | Starting ledger...
node3_1_93ef0a741eb2 | 2019-01-24 10:56:45,774 | DEBUG    | ledger.py            (67) | recoverTree | Recovering tree from transaction log
node3_1_93ef0a741eb2 | 2019-01-24 10:56:45,805 | DEBUG    | ledger.py            (82) | recoverTree | Recovered tree in 0.03139743900101166 seconds
node3_1_93ef0a741eb2 | 2019-01-24 10:56:45,820 | INFO     | node.py              (2636) | initStateFromLedger | Node3 found state to be empty, recreating from ledger
node3_1_93ef0a741eb2 | 2019-01-24 10:56:45,821 | DEBUG    | ledger.py            (199) | start | Ledger already started.
node3_1_93ef0a741eb2 | 2019-01-24 10:56:45,821 | DEBUG    | ledger.py            (199) | start | Ledger already started.
node3_1_93ef0a741eb2 | 2019-01-24 10:56:45,821 | DEBUG    | ledger.py            (199) | start | Ledger already started.
node3_1_93ef0a741eb2 | 2019-01-24 10:56:45,822 | DEBUG    | authenticator.py     (31) | start | Starting ZAP at inproc://zeromq.zap.1
node3_1_93ef0a741eb2 | 2019-01-24 10:56:45,822 | DEBUG    | base.py              (72) | allow | Allowing <IP_ADDRESS>
node3_1_93ef0a741eb2 | 2019-01-24 10:56:45,822 | DEBUG    | base.py              (112) | configure_curve | Configure curve: *[/var/lib/indy/sandbox/keys/Node3/public_keys]
node3_1_93ef0a741eb2 | 2019-01-24 10:56:45,823 | INFO     | stacks.py            (84) | start | CONNECTION: Node3 listening for other nodes at <IP_ADDRESS>:9705
node3_1_93ef0a741eb2 | 2019-01-24 10:56:45,823 | DEBUG    | authenticator.py     (31) | start | Starting ZAP at inproc://zeromq.zap.2
node3_1_93ef0a741eb2 | 2019-01-24 10:56:45,823 | DEBUG    | base.py              (72) | allow | Allowing <IP_ADDRESS>
node3_1_93ef0a741eb2 | 2019-01-24 10:56:45,824 | DEBUG    | base.py              (112) | configure_curve | Configure curve: []
node3_1_93ef0a741eb2 | 2019-01-24 10:56:45,825 | INFO     | node.py              (853) | start | Node3 first time running...
node2_1_862571c6cde1 | 2019-01-24 10:56:46,244 | DEBUG    | selector_events.py   (53) | init | Using selector: EpollSelector
node2_1_862571c6cde1 | 2019-01-24 10:56:46,272 | DEBUG    | ledger.py            (201) | start | Starting ledger...
node2_1_862571c6cde1 | 2019-01-24 10:56:46,287 | DEBUG    | ledger.py            (67) | recoverTree | Recovering tree from transaction log
node2_1_862571c6cde1 | 2019-01-24 10:56:46,326 | DEBUG    | ledger.py            (82) | recoverTree | Recovered tree in 0.03936544899988803 seconds
node2_1_862571c6cde1 | 2019-01-24 10:56:46,380 | DEBUG    | ledger.py            (201) | start | Starting ledger...
node2_1_862571c6cde1 | 2019-01-24 10:56:46,394 | DEBUG    | ledger.py            (67) | recoverTree | Recovering tree from transaction log
node2_1_862571c6cde1 | 2019-01-24 10:56:46,434 | DEBUG    | ledger.py            (82) | recoverTree | Recovered tree in 0.040256519001559354 seconds
node2_1_862571c6cde1 | 2019-01-24 10:56:46,450 | INFO     | node.py              (2636) | initStateFromLedger | Node2 found state to be empty, recreating from ledger
node2_1_862571c6cde1 | 2019-01-24 10:56:46,477 | INFO     | node.py              (786) | _create_bls_bft | BLS: BLS Signatures will be used for Node Node2
node2_1_862571c6cde1 | 2019-01-24 10:56:46,496 | INFO     | node.py              (2636) | initStateFromLedger | Node2 found state to be empty, recreating from ledger
node2_1_862571c6cde1 | 2019-01-24 10:56:46,510 | INFO     | node.py              (612) | setPoolParams | Node2 updated its pool parameters: f 0, totalNodes 1, allNodeNames {'Node2'}, requiredNumberOfInstances 1, minimumNodes 1, quorums {'view_change': Quorum(1), 'checkpoint': Quorum(0), 'bls_signatures': Quorum(1), 'same_consistency_proof': Quorum(1), 'prepare': Quorum(0), 'f': 0, 'propagate': Quorum(1), 'propagate_primary': Quorum(1), 'reply': Quorum(1), 'view_change_done': Quorum(1), 'commit': Quorum(1), 'ledger_status': Quorum(0), 'election': Quorum(1), 'timestamp': Quorum(1), 'consistency_proof': Quorum(1), 'observer_data': Quorum(1)}
node2_1_862571c6cde1 | 2019-01-24 10:56:46,590 | INFO     | plugin_loader.py     (118) | _load | plugin FirebaseStatsConsumer successfully loaded from module plugin_firebase_stats_consumer
node2_1_862571c6cde1 | 2019-01-24 10:56:46,592 | DISPLAY  | replicas.py          (41) | grow | Node2 added replica Node2:0 to instance 0 (master)
node2_1_862571c6cde1 | 2019-01-24 10:56:46,592 | DEBUG    | plugin_helper.py     (23) | loadPlugins | Plugin loading started to load plugins from plugins_dir: /var/lib/indy/plugins
node2_1_862571c6cde1 | 2019-01-24 10:56:46,592 | DEBUG    | plugin_helper.py     (63) | loadPlugins | Total plugins loaded from plugins_dir /var/lib/indy/plugins are : 0
node2_1_862571c6cde1 | 2019-01-24 10:56:46,626 | DEBUG    | ledger.py            (201) | start | Starting ledger...
node2_1_862571c6cde1 | 2019-01-24 10:56:46,637 | DEBUG    | ledger.py            (67) | recoverTree | Recovering tree from transaction log
node2_1_862571c6cde1 | 2019-01-24 10:56:46,668 | DEBUG    | ledger.py            (82) | recoverTree | Recovered tree in 0.030970766001701122 seconds
node2_1_862571c6cde1 | 2019-01-24 10:56:46,687 | INFO     | node.py              (2636) | initStateFromLedger | Node2 found state to be empty, recreating from ledger
node2_1_862571c6cde1 | 2019-01-24 10:56:46,689 | DEBUG    | ledger.py            (199) | start | Ledger already started.
node2_1_862571c6cde1 | 2019-01-24 10:56:46,689 | DEBUG    | ledger.py            (199) | start | Ledger already started.
node2_1_862571c6cde1 | 2019-01-24 10:56:46,690 | DEBUG    | ledger.py            (199) | start | Ledger already started.
node2_1_862571c6cde1 | 2019-01-24 10:56:46,692 | DEBUG    | authenticator.py     (31) | start | Starting ZAP at inproc://zeromq.zap.1
node2_1_862571c6cde1 | 2019-01-24 10:56:46,693 | DEBUG    | base.py              (72) | allow | Allowing <IP_ADDRESS>
node2_1_862571c6cde1 | 2019-01-24 10:56:46,693 | DEBUG    | base.py              (112) | configure_curve | Configure curve: *[/var/lib/indy/sandbox/keys/Node2/public_keys]
node2_1_862571c6cde1 | 2019-01-24 10:56:46,697 | INFO     | stacks.py            (84) | start | CONNECTION: Node2 listening for other nodes at <IP_ADDRESS>:9703
node2_1_862571c6cde1 | 2019-01-24 10:56:46,698 | DEBUG    | authenticator.py     (31) | start | Starting ZAP at inproc://zeromq.zap.2
node2_1_862571c6cde1 | 2019-01-24 10:56:46,699 | DEBUG    | base.py              (72) | allow | Allowing <IP_ADDRESS>
node2_1_862571c6cde1 | 2019-01-24 10:56:46,700 | DEBUG    | base.py              (112) | configure_curve | Configure curve: []
node2_1_862571c6cde1 | 2019-01-24 10:56:46,703 | INFO     | node.py              (853) | start | Node2 first time running...
node4_1_8a0db220c2a0 | CURVE I: cannot open client HELLO -- wrong server key?
node4_1_8a0db220c2a0 | CURVE I: cannot open client HELLO -- wrong server key?
...
node4_1_8a0db220c2a0 | CURVE I: cannot open client HELLO -- wrong server key?
node1_1_5607204968b3 | CURVE I: cannot open client HELLO -- wrong server key?
...
node1_1_5607204968b3 | CURVE I: cannot open client HELLO -- wrong server key?
node3_1_93ef0a741eb2 | CURVE I: cannot open client HELLO -- wrong server key?
...
node3_1_93ef0a741eb2 | CURVE I: cannot open client HELLO -- wrong server key?
node2_1_862571c6cde1 | CURVE I: cannot open client HELLO -- wrong server key?
...
node2_1_862571c6cde1 | CURVE I: cannot open client HELLO -- wrong server key?
node4_1_8a0db220c2a0 | CURVE I: cannot open client HELLO -- wrong server key?
...
node4_1_8a0db220c2a0 | CURVE I: cannot open client HELLO -- wrong server key?
node1_1_5607204968b3 | CURVE I: cannot open client HELLO -- wrong server key?
...
node1_1_5607204968b3 | CURVE I: cannot open client HELLO -- wrong server key?
node3_1_93ef0a741eb2 | CURVE I: cannot open client HELLO -- wrong server key?
...
node3_1_93ef0a741eb2 | CURVE I: cannot open client HELLO -- wrong server key?
node2_1_862571c6cde1 | CURVE I: cannot open client HELLO -- wrong server key?
...
node2_1_862571c6cde1 | CURVE I: cannot open client HELLO -- wrong server key?
node4_1_8a0db220c2a0 | CURVE I: cannot open client HELLO -- wrong server key?
...
node4_1_8a0db220c2a0 | CURVE I: cannot open client HELLO -- wrong server key?
node1_1_5607204968b3 | CURVE I: cannot open client HELLO -- wrong server key?
...
node1_1_5607204968b3 | CURVE I: cannot open client HELLO -- wrong server key?
node3_1_93ef0a741eb2 | CURVE I: cannot open client HELLO -- wrong server key?
...
node3_1_93ef0a741eb2 | CURVE I: cannot open client HELLO -- wrong server key?
node2_1_862571c6cde1 | CURVE I: cannot open client HELLO -- wrong server key?
...
node2_1_862571c6cde1 | CURVE I: cannot open client HELLO -- wrong server key?
node4_1_8a0db220c2a0 | CURVE I: cannot open client HELLO -- wrong server key?
...
node4_1_8a0db220c2a0 | CURVE I: cannot open client HELLO -- wrong server key?
von-web_1_9cac5775c7b9 | ERROR|indy::services::pool          |           src/services/pool/mod.rs:426 | Pool worker thread finished with error Timeout
von-web_1_9cac5775c7b9 | ERROR|indy::errors::indy            |                 src/errors/indy.rs:68  | Casting error to ErrorCode: Timeout
von-web_1_9cac5775c7b9 | _indy_loop_callback: Function returned error 307
von-web_1_9cac5775c7b9 | Traceback (most recent call last):
von-web_1_9cac5775c7b9 |   File "server.py", line 295, in
von-web_1_9cac5775c7b9 |     loop.run_until_complete(boot())
von-web_1_9cac5775c7b9 |   File "/usr/lib/python3.5/asyncio/base_events.py", line 387, in run_until_complete
von-web_1_9cac5775c7b9 |     return future.result()
von-web_1_9cac5775c7b9 |   File "/usr/lib/python3.5/asyncio/futures.py", line 274, in result
von-web_1_9cac5775c7b9 |     raise self._exception
von-web_1_9cac5775c7b9 |   File "/usr/lib/python3.5/asyncio/tasks.py", line 241, in _step
von-web_1_9cac5775c7b9 |     result = coro.throw(exc)
von-web_1_9cac5775c7b9 |   File "server.py", line 112, in boot
von-web_1_9cac5775c7b9 |     await pool.open()
von-web_1_9cac5775c7b9 |   File "/home/indy/.local/share/virtualenvs/server-8XoupS0v/lib/python3.5/site-packages/von_agent/nodepool.py", line 125, in open
von-web_1_9cac5775c7b9 |     self._handle = await pool.open_pool_ledger(self.name, None)
von-web_1_9cac5775c7b9 |   File "/home/indy/.local/share/virtualenvs/server-8XoupS0v/lib/python3.5/site-packages/indy/pool.py", line 82, in open_pool_ledger
von-web_1_9cac5775c7b9 |     open_pool_ledger.cb)
von-web_1_9cac5775c7b9 |   File "/usr/lib/python3.5/asyncio/futures.py", line 361, in iter
von-web_1_9cac5775c7b9 |     yield self  # This tells Task to wait for completion.
von-web_1_9cac5775c7b9 |   File "/usr/lib/python3.5/asyncio/tasks.py", line 296, in _wakeup
von-web_1_9cac5775c7b9 |     future.result()
von-web_1_9cac5775c7b9 |   File "/usr/lib/python3.5/asyncio/futures.py", line 274, in result
von-web_1_9cac5775c7b9 |     raise self._exception
von-web_1_9cac5775c7b9 | indy.error.IndyError: ErrorCode.PoolLedgerTimeout
von_von-web_1_9cac5775c7b9 exited with code 1

Moved to ubuntu 16.04 and the issue was solved


Docker images versioning

Hi. I'm not really sure where to ask this, so let me know if there's a better place for this question/issue.
The issue is: Docker images don't have proper tags.
But a more broad question can be: How exactly aurora images are built?
I have two intentions,

First is to pin the versions of these three images (endpoint, database, nearcore), so it is possible to keep track of the changes.

Secondly, to build the images on my own. Currently, I build them by running similar commands:
git clone https://github.com/aurora-is-near/aurora-relayer && cd aurora-relayer
git checkout <specific tag, e.g. 2022.05.17>
./.ci/setup.sh # to build 'testing' images
export RUNNER_NAME="github-runner"
./.ci/setup.sh # to build 'prod' images

# then I tag specific images with certain tags
# e.g. aurora-endpoint:2022.05.17 or aurora-endpoint:mainnet-2022.05.17

Not sure if it's a proper way to do this.

I was trying to understand how the images on Docker Hub are versioned and tagged, but I'm totally confused now. It seems like there are two main tags: mainnet and testnet, and on every update those are 'overwritten'.
I know it's possible to use image digests to pin a specific version of an image, but it's still not clear how to distinguish between releases.
More confusion is caused by the fact that some images are not updated even after a new 'release' happens. For example, nearaurora/database:mainnet image on docker hub was pushed 4 months ago.
I will be happy to realise that I'm wrong, and this issue is resolved already 🙂
Expected behavior

Each new image is tagged with a release tag or commit hash. For example :mainnet-2022.05.17 or :mainnet-97ed9aa
latest images point to the most recent release. In this case, it could be mainnet and testnet.

Hey, @qezz. This repository is deprecated. We released Aurora Relayer v2. You can check Standalone Aurora Relayer and Refiner repo on how we build images.