Error During Colorization Training

I am getting the following error while training the colorization task. Please help me solve it.
Traceback (most recent call last):
  File "/content/drive/MyDrive/ColabNotebooks/img2img/palette/run.py", line 92, in <module>
    main_worker(0, 1, opt)
  File "/content/drive/MyDrive/ColabNotebooks/img2img/palette/run.py", line 44, in main_worker
    model = create_model(
  File "/content/drive/MyDrive/ColabNotebooks/img2img/palette/models/__init__.py", line 10, in create_model
    model = init_obj(model_opt, logger, default_file_name='models.model', init_type='Model')
  File "/content/drive/MyDrive/ColabNotebooks/img2img/palette/core/praser.py", line 49, in init_obj
    raise NotImplementedError('{} [{:s}() form {:s}] not recognized.'.format(init_type, class_name, file_name))
NotImplementedError: Model [Palette() form models.model] not recognized.``

Maybe your checkpoint haven't been found.


Add preBuildScript to zstd-jni to remove build.gradle and build.sbt

I don't think this will work? Build detection is run before the pre build script.

I don't think this will work? Build detection is run before the pre build script.

You're right, it won't work.
I actually meant to create a pom.xml there, too, but I guess it would need to be forked to do that, for the same reason.
The native build system is actually sbt.


cannot import name 'decoded_latents_to_frames' from 'genmo.mochi_preview.vae.models'

There is no decoded_latents_to_frames method in genmo.mochi_preview.vae.models

@v4if This bug has been fixed, git pull and try again?


init singularity

Breaks some things in docker in order to work for singularity. Not ready for merge to master. Either we need to keep 2 separate branches, or add code to address the differences in containers.

Removing stale PR. We're self hosting now and relying less on multiprocessing.


Weblate integration for mods repo

See https://discord.com/channels/920776187884732556/928440885723664394/1020079799747747931
(if you have access that is)

Translation integration has been running quite well so far

https://github.com/R2Northstar/NorthstarMods/pull/739
https://github.com/R2Northstar/NorthstarMods/pull/712
https://github.com/R2Northstar/NorthstarMods/pull/703
https://github.com/R2Northstar/NorthstarMods/pull/697
https://github.com/R2Northstar/NorthstarMods/pull/675
https://github.com/R2Northstar/NorthstarMods/pull/670
https://github.com/R2Northstar/NorthstarMods/pull/669
https://github.com/R2Northstar/NorthstarMods/pull/668
https://github.com/R2Northstar/NorthstarMods/pull/646

The integration only seems to run on the Northstar.Client localisation, not the Northstar.Custom localisation.
Just to note: a long time ago the Northstar.Custom localisation wasnt working, so everything was moved to Northstar.Client. Since this has been fixed, we should move the custom stuff back to custom

Not actually closed yet as per comment above


Feedback on RISC-V Trace Control Interface Specification - chapter 6

The number of bits requiring reset should be reduced to the minimal needed to ensure that the trace tool can initialize the trace encoder to desired state. For trace encoder, Reset to 0 should  be needed only for trTeActive and trTeEnable. When trTeEnable is 0 the trace encoder does not emit any trace and all other register state may then be initialized by the trace  tools to the desired state. Read-only fields by definition have a defined read-only value. This feedback applies to all trace control registers.

trTeInstTrigEnable - The description incorrectly states that this signal is set or cleared by the Debug Module instead of the Trigger Module specified by the Sdtrig ISA extension. The description can also be reworded for better readability/clarity.

trTeInstTracing - this signal is volatile and can be set or cleared by triggers. Guideline for a safe sequence to write this bit - for instance as part of writing say 1 to trTeInstStallOrOverflow is missing in the specification. Likewise for trTeDataTracing.

trTeInstExtendAddrMSB - the name of the control bit and its description is misleading as the encoder does not do any extension of address bits. Further it is indicated as being limited to Sv39/48/57 - which contradicts N-trace which allows compression for Sv32 and also physical addresses.

trTeDataDrop - why is this bit not redundant in relation to trTeDataStallOrOverflow

trTeDataStallOrOverflow - why is this bit set when a overflow message is generated and not when overflow is detected? Why is there a subtle difference in behavior compared to trTeInstStallOrOverflow?

trTeDataDropEna - how is this control different than trTeDataStallEna?

Specify behavior if both trTeDataNoValue and trTeDataNoAddr are both set to 1.

trTeDataAddrCompress - For E-trace data trace,  the address is always differential and the data can be compressed using XOR or differential encoding. The 4 encodings specified here do not match up with the 4 diff options specified by E-trace data trace protocol.

"In a system with Internal Core Timestamp counter" - the earlier description implied that the core level sharing was only the clock and the  timestamp counter is per hart. This text seems to contradict that. Having a shared timestamp counter among multiple harts is not very useful - especially since it may be reset by per-hart controls. This should be changed to a per hart timestamp counter.

trTsCount - this field should be WARL as it is legal to hardwire this unit to 0 when an  internal timestamp unit is not implemented.

Timestamp unit - two terms are used "Internal timestamp" and "Internal core timestamp". Are these intended  to be different. If not please unify to use a single term.

trTsRunInDebug - this should be renamed "trTsRunWhenHalted" to support additional cases where the timestamp counter may halt  - such as low power entry, being held in reset, or due to security reasons as being discussed in context of external debug security.

trTsPrescale - is the prescale to scale up or scale down?

Timestamp units - bits  23:16 - does "System-dependent" mean they are designated for custom extension?

Section 6.2.1 - should be renamed to "Trigger Module"

section 6.2.1  - (breakpoint or watchpoint) - is this an exhaustive list? Why is trace-on/trace-off action prohibited for other forms of triggers?

Planning on updating the spec for the follow issues:
2,4,11,12,16
Response:

RC: I really want to have trace functional with minimal settings. Just enable and it reasonably works. Trace may be enabled (for debug ...) from early boot code. Setting many registers would complicate things. Also with WARL semantics it should not be beneficial to have reset value as the only value.

Jay: Suggest rewording to: “Allows trTeInstTracing to be set or cleared by Trace-on and Trace-off triggers signals generated by the corresponding Trigger module”. ACTION UPDATE SPEC.

RC: When trace triggers are used to enable trace you do not set this bit. Otherwise you set it. Setting in the middle while triggers are on/off will be random. The only reasonable use case would be to enable tracing to see where code is if from some reason enable trigger didn't fire

Robert: Description was not fixed after we removed from Ntrace. Jay: Agree, we need to align this control bit to the updated description used in the message document. ACTION UPDATE SPEC.

Jay: This bit is used to notify of dropped data message. This may occur independent of a stall and/or overflow.

Jay: To me it makes sense to get set when the message is generated. Makes sure the last stall/overflow is detected when the message is sent. Doing it earlier has no real value.

RC: Stall and drop are different things. If someone doesn't want to stall they may still want to drop data trace to prevent loosing of instruction trace.

Robert: You may only see that transfer occurred and have timestamp (if configured). With heave filtering it can be seen as generating markers which can be counted. Setting data trace at Ethernet controller register may allow you to see who and how often is sending packets ...

RC. It was heavily discussed. E-trace is not perfect ...

Rc. Terms hart/core are not always consistently used.

Jay :We will update DOC to WARL ACTION UPDATE SPEC

Jay: We will update DOC to unify to a single term. ACTION UPDATE SPEC

RC. Seems you are mixing halt of hart with halt of timestamp. This bit is strictly for debug mode

RC. It is divider so down ...

Rc. No it's just different for different systems.... Jay: Should we rename this to Vendor defined?

Agree it should be renamed to Trigger Module ACTION UPDATE SPEC

??, Not clear ont he comment, Trace-on/off is only defined for trigger actions 2/3 when supported by the hart

See comment above - closing it.

Reopening this issue for a few open points:

The reset burden should be removed to the minimal needed for SW
such as the external trace tools to be able to configure the trace
control interface to enable. Besides the fields that would prevent
the trace tool from performing such configurations, all other fields
should have a legal but unspecified value at reset. The documented
sequence for enabling reset, discovery, and enabling trace. This
includes actions such training PIB sink or configuring base addresses
in system memory for the RAM sinks.

trTeInstTracing - the specific question was with respect to
trTeInstStallOrOverflow which are RW1C. Consider a condition such as
follows:
- trace-on sets trTeInstTracing to 1
- A stall occurs causing trTeInstStallOrOverflow to be set to 1
- The tracing tool reads trTeControl - let this read value be A.
The read value A has trTeInstTracing as 1.
- A trace-off trigger clears trTeInstTracing to 0 in trTeControl
- The tracing tool now set trTeInstStallOrOverflow in A and
writes this value to trTeControl. This will cause the
trTeInstTracing  to be set to 1 when it should be 0.
Since the trTeInstTracing has two writers - a hardware writer
and a SW writer - a safe sequence to writing trTeControl when
trace is enabled should be documented. This may be to disable
trace before making any writes to trTeControl.

trTeDataStallOrOverflow - Is there a reason why the behavior
for asserting this is different than behavior specified for
trTeInstStallOrOverflow. Jay indicates that this should be
done when Overflow message is generated and not when Overflow
condition is detected then the trTeInstStallOrOverflow behavior
should be updated to match trTeDataStallOrOverflow. It may however
be more useful to indicate on overflow condition being detected than
when it is removed (When Overflow message is generated) as it allows
to provide a status indication that trace has stopped due to  an overflow.
Delaying it to when the overflow message is generated i.e. overflow
condition no longer exists may not be useful as the overflow message
itself will tell the decoder that such a condition occurred.

trTeDataAddrCompress. The E-trace specification provides the following:
00: Full address and data (sync)
01: Differential address, XOR-compressed data
10: Differential address, full data
11: Differential address, differential data
The only two address compression options are to send full address or
to send differential data. The is an option for XOR compression of data
but not the address.
The trace control specification indicates:
0: Only send full (unmodified) addresses
1: Use XOR compression
2: Use differential compression
3: Dynamically select XOR or differential on a per-packet basis in
order to minimize packet length.
How should the difference between the options provided by the trace
control interface options and the Etrace specification be reconciled?
What controls select the data compression form?

"Rc. Terms hart/core are not always consistently used." Please address
the inconsistency.

"RC. It is divider so down "  Please update the description.


Update github4s to 0.29.1

Updates com.47deg:github4s from 0.27.1 to 0.29.1.
GitHub Release Notes - Changelog - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.47deg", artifactId = "github4s" } ]

labels: library-update, semver-minor

Superseded by #110.


tests for $.fetch

We need tests for $.fetch, have had a few of issues reported around this method #111 #127 #128 #91 , and its difficult to begin making changes without tests in place.
a good testing strategy would be to use sinon.server
https://gist.github.com/cjohansen/739589

I created a simple template for testing $.fetch.
For now it's just echoing the request data back to the client. However, we have to discuss whether #128 is still a valid bug though. Should we improve the way data is stringified?

great thanks for helping. much appreciated.

Ugh, I will create a new PR with tests for fetch soon.
I somehow managed to do a bad merge i think...

Argh. On it, thanks for spotting!

$.fetch tests have been merged in no? closing this.


⚠ Secret Website 3 has degraded performance

In 2ef608a, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 3097 ms

Resolved: Secret Website 3 performance has improved in 629d754.


Error with img Tag

Hi, First off, thank you for the amazing work. Im still a novice developer so please excuse me,
I get the following error after building the site with github pages:
"Your site is having problems building: The tag img in _posts/2015-12-20-deep.markdown/#excerpt is not a recognized Liquid tag"
So far my research says I should Use "rake generate" and "rake deploy" to fix this problem but I think this is for Octopress sites only. Have you seen this before?

Do you have the _plugins/images.rb file? The img tag is in that file.

yes that file exists.

I can confirm the site builds perfectly on my FTP server. So this is just a Github Pages issue. We can close this since I have a work-around for now.
Thanks again for this great tool!

I'm having the same issue when trying to use Github Pages. Is there any incompatible plugin? Or is it a configuration issue that can be worked around so as to use github.io ?

I actually use github page as well for delightfuldev.com. can you show me the markdown post that causing this error so I can try it?

The page build failed with the following error:
The tag `img` in `_posts/2015-12-20-deep.markdown/#excerpt` is not a recognized Liquid tag. For more information, see https://help.github.com/articles/page-build-failed-unknown-tag-error.

Ok, I think I know what happened. Did you guys add Gemfile with the following content?
source 'https://rubygems.org'
gem 'github-pages'

and safe: false in _config.yml, then build using bundle exec jekyll build?
There are two problems here:

safe: false makes Jekyll ignore the plugins in the _plugins directory.
Unfortunately, you will bump into different error by removing safe: false: jekyll 2.4.0 | Error:  uninitialized constant Jekyll::Hooks. This happens because github-pages gem is using jekyll 2.4.0, while my img tag plugin uses Jekyll::Hooks which seems only available in jekyll 3.0.1.

So what I propose is:

Remove the Gemfile
Remove safe: false from _config.yml
Build the site using jekyll build. Make sure jekyll --version returns jekyll 3.0.1. Update jekyll if needed.
Push the built site in _site directory to Github Pages. I'm using Octopress 3.0 to do this. Check out the deployment using Octopress here. Basically just run octopress deploy init git git@github.com:user/project, edit _deploy.yml if needed, then run octopress deploy to deploy it to Github Pages.

Thanks for the help! This seemed to work, as github does not report any errors, but I'm guessing it is not picking up the plugins, showing just the raw html. (You can see it here[http://fedelcar.github.io/portfolio/])
Any ideas as to why?

Apparently I didn't handle if Appolo is not in root url. I'm fixing it but I'll push the update as soon as I get a decent internet connection :)

I just tried again with the latests commits and I'm still not having any luck with this.
I cloned your repo, ran jekyll build then octopress deploy init git git@github.com:user/project, edited deploy.yml to point to the gh-pagesbranch and finally octopress deploy
The site was uploaded to the github repo, but Iwhile the page is building, it only shows raw html, with no style. (You can check it out here)

Can you try the newest commit, and set the baseurl in _config.yml to /portfolio/. Then jekyll build and publish again?
I tested with a dummy project page here and the corresponding repo here.

Yup, that worked! Thank you very much both for the great work you've done and the help! Congrats!


Sub: add Eq & Functor instances + law checks

The Monoid associative laws are not passing. It could be that the Eq instance I wrote is not entirely correct (I don't know if the id of Observe is the right way to compare two subs?) , or that there is an issue with the Monoid[Sub] implementation.
The following instance yields the same outcome:
given [F[_], Msg: Eq]: Eq[Sub[F, Msg]] = Eq.fromUniversalEquals

Perhaps you have a better idea?

If we don't look at the content of Combine, then all laws pass, but it doesn't look right, does it? 😄
  given [F[_], Msg: Eq]: Eq[Sub[F, Msg]] with
    def eqv(x: Sub[F, Msg], y: Sub[F, Msg]): Boolean = (x, y) match {
      case (Sub.None, Sub.None)                             => true
      case (Sub.Observe(id1, _, _), Sub.Observe(id2, _, _)) => id1 === id2
      case (Sub.Combine(x1, y1), Sub.Combine(x2, y2))       => true // eqv(x1, x2) && eqv(y1, y2)
      case (Sub.Batch(xs), Sub.Batch(ys)) =>
        xs.size === ys.size && xs.zip(ys).forall((x, y) => eqv(x, y))
      case _ => false
    }

@gvolpe can you share the output of the law failure?

Complete logs on the previous run: https://github.com/PurpleKingdomGames/tyrian/actions/runs/3923472574/jobs/6707104827
failing seed for monoid.associative is AwxoYtLVgxbb7SGjeVcntk5yQaHpLoW1ygsjeuxy4cI=
==> X tyrian.SubLawsTests.Monoid[Sub]: monoid.associative 0.02s munit.FailException: /home/runner/work/tyrian/tyrian/tyrian/js/src/test/scala/tyrian/SubLawsTest.scala:26
25:  checkAll("Functor[Sub]", FunctorTests[Sub[IO, *]].functor[Int, Double, String])
26:  checkAll("Monoid[Sub]", MonoidTests[Sub[IO, String]].monoid)
27:

Failing seed: AwxoYtLVgxbb7SGjeVcntk5yQaHpLoW1ygsjeuxy4cI=
You can reproduce this failure by adding the following override to your suite:

  override val scalaCheckInitialSeed = "AwxoYtLVgxbb7SGjeVcntk5yQaHpLoW1ygsjeuxy4cI="

Falsified after 0 passed tests.
> Labels of failing property:
Expected: Combine(Observe(,IO(...),<function1>),Combine(Observe(,IO(...),<function1>),Observe(,IO(...),<function1>)))
Received: Combine(Combine(Observe(,IO(...),<function1>),Observe(,IO(...),<function1>)),Observe(,IO(...),<function1>))
> ARG_0: Observe(,IO(...),<function1>)
> ARG_1: Observe(,IO(...),<function1>)
> ARG_2: Observe(,IO(...),<function1>)

I expect that if you change the Monoid instance to use Batch instead of Combine, you'll find the law check passes, because it'll form a monoid on the basis that list is a monoid.
Combine isn't associative because these structures clearly don't equate (I assume, this isn't something I look into much):
Combine(Combine(a, b), c) =!= Combine(a, Combine(b, c))

@davesmith00000 do you mean doing this?
  final def merge[F[_], Msg, LubMsg >: Msg](a: Sub[F, Msg], b: Sub[F, LubMsg]): Sub[F, LubMsg] =
    (a, b) match {
      case (Sub.None, Sub.None) => Sub.None
      case (Sub.None, s2)       => s2
      case (s1, Sub.None)       => s1
      case (s1, s2)             => Sub.Batch(s1, s2)
    }

This isn't passing associativity either :/
failing seed for monoid.associative is _q2a0WOV17VQG2T-uuiwqK5-8BxvNQvW5ZXKG5VllcO=
==> X tyrian.SubLawsTests.Monoid[Sub]: monoid.associative 0.02s munit.FailException: /home/gvolpe/workspace/tyrian-fork/tyrian/js/src/test/scala/tyrian/SubLawsTest.scala:27
26:  checkAll("Functor[Sub]", FunctorTests[Sub[IO, *]].functor[Int, Double, String])
27:  checkAll("Monoid[Sub]", MonoidTests[Sub[IO, String]].monoid)
28:
Failing seed: _q2a0WOV17VQG2T-uuiwqK5-8BxvNQvW5ZXKG5VllcO=
You can reproduce this failure by adding the following override to your suite:

  override val scalaCheckInitialSeed = "_q2a0WOV17VQG2T-uuiwqK5-8BxvNQvW5ZXKG5VllcO="

Falsified after 0 passed tests.
> Labels of failing property:
Expected: Batch(List(Observe(,IO(...),<function1>), Batch(List(Observe(,IO(...),<function1>), Observe(,IO(...),<function1>)))))
Received: Batch(List(Batch(List(Observe(,IO(...),<function1>), Observe(,IO(...),<function1>))), Observe(,IO(...),<function1>)))
> ARG_0: Observe(,IO(...),<function1>)
> ARG_1: Observe(,IO(...),<function1>)
> ARG_2: Observe(,IO(...),<function1>)

No that won't do it, you'll have to be sneakier. :smile:
Essentially all results of a merge will have to produce a Sub.Batch, or you'll forever be comparing trees of different shapes that will never be trivially equal.
The alternative is to work on the Eq instance so that is essentially disregards the shape of the tree and only concerns itself with the ultimate order of the concrete subs. Essentially flatten then check equals.

The alternative is to work on the Eq instance so that it essentially disregards the shape of the tree and only concerns itself with the ultimate order of the concrete subs. Essentially flatten then check equals.

👍 this sounds right.

The alternative is to work on the Eq instance so that it essentially disregards the shape of the tree and only concerns itself with the ultimate order of the concrete subs. Essentially flatten then check equals.

Sounds good. Now how would I "flatten" a sub? 🤔 Need to implement FlatMap now? 😄

Subs and Cmds are just trees of values. So all you have to do (other that implement flatMap) is recursively unwrap the tree into a flat List. E.g.:
Combine(Batch(a, b, c), Combine(d, Combine(e, None)))

becomes
List(a, b, c, d, e)

@gvolpe ...in fact:
https://github.com/PurpleKingdomGames/tyrian/blob/d5dab3faa80a132b87b7dcaac36c6c61d34ca791/tyrian/js/src/main/scala/tyrian/runtime/SubHelper.scala#L12

Awesome! That helps a lot, got it working now 🥳

@gvolpe I'll be doing some work on Tyrian a bit later (trying to get a release together). If you're happy that this is good to go then I'll have a go at merging it?

@davesmith00000 yes, go for it. I plan to get back to getting that Cogen instance right at some point, but I am afraid I won't have time until next weekend at least.


FR: Center embedded map on front matter "Location" entry

What the title says - I have several notes that represent a place, with embedded maps. Would be great if I could set the center of the embedded map to the location in the front matter - at the moment I'm copy-pasting the location info into the mapview block, which is a little cumbersome.
Is there a better way to do this? Or can I just 'reference' the existing location somehow?
Thanks!

There is currently no way to do it, and it's definitely a very nice idea to add.


Enhancement: Make it more apparent when model specified in yml configuration does not exist in the project

Describe the feature
When doing a run or test, a warning is given when a yml file has a model specified to document/test against. This warning is easily missed.
To test this:

Create a .yml file and give it some documentation/testing parameters for a model that is not in the project.
Do a dbt run or dbt test and see the warning at the top.

Although the warning is there and you will catch this if you're paying attention, this is something that is missed frequently which results in more time spent explaining this, being very diligent in catching this in reviews, and more time for users to pay careful attention to this. I think we can make this easier for all of us. Here's a couple of ideas:

Highlight the warning as a different color
Throw a line in for the model name specified anyway, but show as an error/warning with more details after the testing is done

Describe alternatives you've considered
The solution to resolving instances of this issue currently is a matter of training users to be mindful of not just glancing at their dbt run and dbt test outputs.
Who will this benefit?
Anyone who uses dbt and the docs/testing functionality!

good idea @christineberger! I think changing the color for this warning would work well. Let me know if this is something you might be interested in working on when you get some spare time 😉

@drewbanin I absolutely would love to take a stab at this! I can't promise I'll get anywhere, but I will definitely try. =)


json omitempty ignore valid input for float64 data type

https://github.com/grafadruid/go-druid/blob/master/builder/havingspec/equal_to.go#L6
If we want to filter a column where the value is greater than 0, the json marshal will ignore the value field because of "omitempty" while this is a valid use case.

This issue exists in greater than, equal to, less than, ... etc


"docker inspect gcr.io/google_containers/pause:0.8.0" command returned message slowly.

The "gcr.io/google_containers/pause:0.8.0" image is the default "pod-infra-container-image" of kubernetes, that means when started a pods in kubernetes, it need to start a "gcr.io/google_containers/pause:0.8.0" container.
But I found when I typed "docker inspect gcr.io/google_containers/pause:0.8.0", it took about 10 seconds to return message.
But when I typed "docker inspect hello-world", it returned the message immediately.
All of the images above had already been pulled into my machine before, so I'm wonder about why it happened.

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

I read the code in api/client/inspect and fount that the inspect command just sent a GET request to the daemon, so I used the "wget" tools to do the same thing.
Then I found the follow command got the return message immediately:

wget <IP_ADDRESS>:4243/images/hello-world/json
wget <IP_ADDRESS>:4243/images/docker.registry:5000/test/hello-world/json
wget <IP_ADDRESS>:4243/images/2c40b0526b63/json

The "hello-world" image is the classical images pulled from docker hub.
The "docker.registry:5000/test/hello-world" image is the images pulled from our local registry.
The "2c40b0526b63" is the image_id of "gcr.io/google_containers/pause:0.8.0" image.
But the below command returned message after about 10 second.

wget <IP_ADDRESS>:4243/images/gcr.io/google_containers/pause:0.8.0/json

Is there anyone can tell me what's different between these command?

@aaronlehmann Could you try to answer this question?

Sorry, no idea. If I try the command without pulling the image first, I get:
Error: No such image, container or task: gcr.io/google_containers/pause:0.8.0

If I pull the image and try again, it runs instantly.
Could this be some issue with locking slowing things down (cc @cpuguy83)? What version of Docker are you running?

@aaronlehmann Maybe it was fixed. The issue is a year old. Thanks for testing. Going to close now because we can't reproduce. Feel free to open new if the problem persists.


Ignore test database fixtures

While debugging failed migrate_drupal inspections, I saw this on my deprecation bot:
18:45:33 mmap() failed: [12] Cannot allocate memory
18:45:33
18:45:33 mmap() failed: [12] Cannot allocate memory
18:45:33 PHP Fatal error:  Out of memory (allocated<PHONE_NUMBER>) (tried to allocate 262144 bytes) in phar:///usr/local/bin/drupal-check/vendor/nikic/php-parser/lib/PhpParser/PrettyPrinter/Standard.php on line 945

I'm going to bet it is due to the test fixtures.

This is added in: https://github.com/mglaman/drupal-check/blob/master/phpstan/base_config.neon
	excludes_analyse:
		- */tests/Drupal/Tests/Listeners/Legacy/*
		- */tests/fixtures/*.php


Reenable sonarqube scan as GH action

Description
Describe the changes made and why they were made.
Ignore if these details are present on the associated Apache Fineract JIRA ticket.
Checklist
Please make sure these boxes are checked before submitting your pull request - thanks!

[x] Write the commit message as per https://github.com/apache/fineract/#pull-requests

[x] Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.

[x] Create/update unit or integration tests for verifying the changes made.

[x] Follow coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions.

[x] Add required Swagger annotation and update API documentation at fineract-provider/src/main/resources/static/api-docs/apiLive.htm with details of any API changes

[x] Submission is not a "code dump".  (Large changes can be made "in repository" via a branch.  Ask on the developer mailing list for guidance, if required.)

FYI our guidelines for code reviews are at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide.

Hi - looks like this is failing due to the missing credentials as secrets. Did you try adding the required secrets to GitHub? @vorburger posted the instructions on how to do this earlier but I haven't had a chance to try them yet.

@ptuomola ... first we would need the credentials... do you have them? BTW: we'll share these things now on 1password... you should have received an invite.

@ptuomola yeah, I was trying to figure out what credentials we have configured for the repo since I don't have the access to see that. In addition, as @vidakovic said, we would need to credentials but as soon as those 2 things are resolved and the credentials are configured for the repo, we're free to relieve the Travis build from the duties and switch over completely to GH Actions.

If I recall @vorburger's explanation correctly, I don't think it's possible to see / configure secrets through the Github GUI - what we need to do is to push the secret using the Github REST API. I think I have the rights now to create a new SonarQube token but I haven't tried pushing any secrets using the REST API, so not sure how easy that is...

as for setting secrets on Github: if I'm not mistaken we need to place a
Jira ticket in Apache Infrastructure... these guys are the only ones who
have full access...
Having said that: we should investigate these Apache Wiki pages
https://cwiki.apache.org/confluence/display/INFRA/Github+Secrets+and+Tokens
On Sat, Apr 9, 2022 at 1:10 PM Petri Tuomola @.***>
wrote:

If I recall @vorburger https://github.com/vorburger's explanation
correctly, I don't think it's possible to see / configure secrets through
the Github GUI - what we need to do is to push the secret using the Github
REST API. I think I have the rights now to create a new SonarQube token but
I haven't tried pushing any secrets using the REST API, so not sure how
easy that is...
—
Reply to this email directly, view it on GitHub
https://github.com/apache/fineract/pull/2270#issuecomment-1093917026,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAC4ZL2ZEESJJG3YD7XGGM3VEFQRBANCNFSM5S4LLVAA
.
You are receiving this because you were mentioned.Message ID:
@.***>

... as I see it that Sonar token is already defined on an org level for all
Apache projects at Github... so no need to create anything else as I see
it... same for Docker Hub (which is great... because that was the next
thing I needed for the releases)...
On Mon, Apr 11, 2022 at 12:21 AM Aleksandar Vidakovic <
@.***> wrote:

as for setting secrets on Github: if I'm not mistaken we need to place a
Jira ticket in Apache Infrastructure... these guys are the only ones who
have full access...
Having said that: we should investigate these Apache Wiki pages
https://cwiki.apache.org/confluence/display/INFRA/Github+Secrets+and+Tokens
On Sat, Apr 9, 2022 at 1:10 PM Petri Tuomola @.***>
wrote:

If I recall @vorburger https://github.com/vorburger's explanation
correctly, I don't think it's possible to see / configure secrets through
the Github GUI - what we need to do is to push the secret using the Github
REST API. I think I have the rights now to create a new SonarQube token but
I haven't tried pushing any secrets using the REST API, so not sure how
easy that is...
—
Reply to this email directly, view it on GitHub
https://github.com/apache/fineract/pull/2270#issuecomment-1093917026,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAC4ZL2ZEESJJG3YD7XGGM3VEFQRBANCNFSM5S4LLVAA
.
You are receiving this because you were mentioned.Message ID:
@.***>

That’s great. Let me see if I can find a way to grant that token an access
to our project
On Mon, 11 Apr 2022 at 6:26 AM, Aleksandar Vidakovic <
@.***> wrote:

... as I see it that Sonar token is already defined on an org level for all
Apache projects at Github... so no need to create anything else as I see
it... same for Docker Hub (which is great... because that was the next
thing I needed for the releases)...
On Mon, Apr 11, 2022 at 12:21 AM Aleksandar Vidakovic <
@.***> wrote:

as for setting secrets on Github: if I'm not mistaken we need to place a
Jira ticket in Apache Infrastructure... these guys are the only ones who
have full access...
Having said that: we should investigate these Apache Wiki pages

https://cwiki.apache.org/confluence/display/INFRA/Github+Secrets+and+Tokens

On Sat, Apr 9, 2022 at 1:10 PM Petri Tuomola @.***>
wrote:

If I recall @vorburger https://github.com/vorburger's explanation
correctly, I don't think it's possible to see / configure secrets
through
the Github GUI - what we need to do is to push the secret using the
Github
REST API. I think I have the rights now to create a new SonarQube token
but
I haven't tried pushing any secrets using the REST API, so not sure how
easy that is...
—
Reply to this email directly, view it on GitHub
https://github.com/apache/fineract/pull/2270#issuecomment-1093917026,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AAC4ZL2ZEESJJG3YD7XGGM3VEFQRBANCNFSM5S4LLVAA

.
You are receiving this because you were mentioned.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/apache/fineract/pull/2270#issuecomment-1094387603,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AASJVCUAENCGLPEWMODTTODVENIRRANCNFSM5S4LLVAA
.
You are receiving this because you were mentioned.Message ID:
@.***>

@ptuomola any luck so far?

Sorry - my dev machine died, so have been without access for a while...
However I've just enabled the user gmcdonald with permissions to execute
analysis on our Fineract sonarcloud project.
If I understood the wiki page correctly, this should mean we can now use
the prepopulated sonarcloud token secret to trigger the analysis?
Regards
Petri
On Tue, Apr 19, 2022, 20:36 Arnold Gálovics @.***>
wrote:

@ptuomola https://github.com/ptuomola any luck so far?
—
Reply to this email directly, view it on GitHub
https://github.com/apache/fineract/pull/2270#issuecomment-1102590833,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AASJVCRQUDYG3SPXA3VYONLVF2SEHANCNFSM5S4LLVAA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi Petri... I came across this issue coincidentally today... I think we are
using the "wrong" project handle on Sonarcloud... because Apache (the org)
has prepared them for all of their projects... the one we are using - as I
understand it - was created "manually"... but there is another one... kind
of the official Sonar project slug for Fineract... if you search for
Fineract you'll see it immediately... the other thing is empty.
Having said that: by default our Github repo should already contain the
secret for our "official" Sonar project... just FYI
On Tue, Apr 19, 2022 at 3:02 PM Petri Tuomola @.***>
wrote:

Sorry - my dev machine died, so have been without access for a while...
However I've just enabled the user gmcdonald with permissions to execute
analysis on our Fineract sonarcloud project.
If I understood the wiki page correctly, this should mean we can now use
the prepopulated sonarcloud token secret to trigger the analysis?
Regards
Petri
On Tue, Apr 19, 2022, 20:36 Arnold Gálovics @.***>
wrote:

@ptuomola https://github.com/ptuomola any luck so far?
—
Reply to this email directly, view it on GitHub
https://github.com/apache/fineract/pull/2270#issuecomment-1102590833,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AASJVCRQUDYG3SPXA3VYONLVF2SEHANCNFSM5S4LLVAA
.
You are receiving this because you were mentioned.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/apache/fineract/pull/2270#issuecomment-1102625172,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAC4ZL32C3Z57UPSS65JG5DVF2VF7ANCNFSM5S4LLVAA
.
You are receiving this because you were mentioned.Message ID:
@.***>

aha... now both projects show data... yesterday night one of them was
definitely empty... but the one you just sent seems to be the right one
(under Apache)... we should be good here.
On Tue, Apr 19, 2022 at 5:23 PM Petri Tuomola @.***>
wrote:

Hi Aleks
The one we've been using is this:
https://sonarcloud.io/project/overview?id=apache_fineract
I believe this was created by Victor (?) and he granted me access to it a
couple of months ago. I've also granted the access to the account with what
the token was created today - so hopefully the secret token should work
now.
There's also a project called "Apache Fineract" in Sonarcloud:
https://sonarcloud.io/project/configuration?id=fineract
I don't know who has access to this and how it had been configured. If it
already has the token authorized we can of course also use that.
Should be pretty easy to try accessing either/both from the GitHub action
with the existing secret token. Maybe someone can give this a go?
Alternatively I can try it when I get my machine back…
Regards
Petri
On Tue, Apr 19, 2022, 23:05 Aleksandar Vidakovic @.***>
wrote:

Hi Petri... I came across this issue coincidentally today... I think we
are
using the "wrong" project handle on Sonarcloud... because Apache (the
org)
has prepared them for all of their projects... the one we are using - as
I
understand it - was created "manually"... but there is another one...
kind
of the official Sonar project slug for Fineract... if you search for
Fineract you'll see it immediately... the other thing is empty.
Having said that: by default our Github repo should already contain the
secret for our "official" Sonar project... just FYI
On Tue, Apr 19, 2022 at 3:02 PM Petri Tuomola @.***>
wrote:

Sorry - my dev machine died, so have been without access for a while...
However I've just enabled the user gmcdonald with permissions to
execute
analysis on our Fineract sonarcloud project.
If I understood the wiki page correctly, this should mean we can now
use
the prepopulated sonarcloud token secret to trigger the analysis?
Regards
Petri
On Tue, Apr 19, 2022, 20:36 Arnold Gálovics @.***>
wrote:

@ptuomola https://github.com/ptuomola any luck so far?
—
Reply to this email directly, view it on GitHub
<
https://github.com/apache/fineract/pull/2270#issuecomment-1102590833
,
or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AASJVCRQUDYG3SPXA3VYONLVF2SEHANCNFSM5S4LLVAA

.
You are receiving this because you were mentioned.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
<https://github.com/apache/fineract/pull/2270#issuecomment-1102625172
,
or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AAC4ZL32C3Z57UPSS65JG5DVF2VF7ANCNFSM5S4LLVAA

.
You are receiving this because you were mentioned.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/apache/fineract/pull/2270#issuecomment-1102766360,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AASJVCXLTGLLBJVTFW6DYD3VF3DTDANCNFSM5S4LLVAA
.
You are receiving this because you were mentioned.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/apache/fineract/pull/2270#issuecomment-1102786207,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAC4ZL6Q7QAX2KD3OI7VK7TVF3FV3ANCNFSM5S4LLVAA
.
You are receiving this because you were mentioned.Message ID:
@.***>

guys, I'm kinda lost in the discussion. Are you suggesting the secrets are already configured within GitHub? If so, what are the keys I should reference in the workflow?
Tbh, I'd love to get rid of the Travis builds ASAP because it just takes an enormous amount of time to run them.

I've created a new pull request that fixes the authentication issue - seems to work at least at first glance. See https://github.com/apache/fineract/pull/2289


Decode gziped sitemaps

Fixes #6

That causes lots of new problems. Many .xml.gz files actually is an .xml file, and those will now fail. It's like trying to decompress a uncompressed XML file using GZIP.
This is the right place to start, but it's just an part of a bigger solution.
WIP

But the rest of code is counting on gziped sitemaps having xml.gz extension and if it finds it it calls method downloadAndExtractGZIP. Code should not call this method in the first place, but that change should be in different issue and PR.

I opened the issue about compressed sitemaps detection. #9


Unable to connect to private server

Hey guys,
I am trying to connect to my own Valheim server - unfortunately not working yet.
I am using the docker image of this repository.
Docker start command: docker run -d --name valheim-server -p 2456-2458:2456-2458/udp -p 2456-2458:2456-2458/tcp -v /home/nexlo/valheim-config:/config -e SERVER_NAME="NexloTest" -e WORLD_NAME="Neotopia" -e SERVER_PASS="secret" <image-path>
My server gets listed here: https://southnode.net/steamquery.php
If I start the same image locally, I am able to connect locally. Remote I only get the server listed (via port 2457) but unable to connect.
Host-Native OS is Debian10
Any suggestions? What do I miss? Thanks in advance! :)

The tcp ports are not required but shouldn't harm either. Since you can connect locally but not remote by process of elimination it is very likely a packet filtering / firewalling issue. When you connect remotely what steps do you take? The ones described here? https://github.com/lloesche/valheim-server-docker#steam-server-favorites--lan-play

Hey @lloesche ,
thanks for your quick response!
Well, what should I say now... - its working :D - I have nothing changed - its really about the Steam-Server listing/connect... penetrating the refresh button was the solution what the....
I am used to use steam-connect links e.g. steam://connect/  (helped me with ARK servers), but in this case it seems not working well.
SumUp (if people encounter similar issues):
Add your sever to your favourite list (with 2456). It may will disappear - thats when you press "refresh" as much as you can and if the server is visible double click it. Do not use port 2457 for connection/favourites. Filtering for Game: Valheim may also help if your list is too long.
@lloesche Dank nochmals! :) Saubere Lösung ohne unnötiges Zeugs ;) <3


API: Private url authentication

Create an API endpoint that takes a username and returns a url authenticated for that username

We may have other uses for this. I suggest making it generic.
You should return a private token that can be used for more than just voting.

But obviously for voting.

We can also include commands for removing the token: @chesster login @chesster logout  etc

Implemented a get_private_url endpoint (wiki).
The way I have it implemented right now is you specify the page (e.g. "vote"), and it returns a URL with a token that has a fixed expiry time (1 hour for now). The token itself is not tied to a particular page, but in practice you would call the API to create a new token/url to visit another page.

Cool. Your productivity makes me feel worthless.


Whisk CLI fails with a cannot invoke action error if 1 of your keys is named response

@sroorda commented on Fri Sep 15 2017
Environment details:

local deployment, vagrant, native ubuntu, Mac OS, Bluemix, ...
version of docker, vagrant, ubuntu, ...
Deployed to Bluemix api.ng.bluemix.net

It appears that if you invoke your Cloud Function via the CLI it will fail with
error: Unable to invoke action 'nestedDictionaryError': The connection failed, or timed out. (HTTP status code 200) if you include a key labeled response in your output.
Steps to reproduce the issue:
Create the following Cloud Function in python
def main(args):
    result = {'message': 'error result', 'response': {'key1': 'value1','key2': 'value2' }}

    if args and args['resultType'] and args['resultType'] == 'error':
        return {'message': 'error result', 'response': {'key1': 'value1','key2': 'value2' }}
    else:
        return {'message': 'error result', 'not_response': {'key1': 'value1', 'key2': 'value2'}}

Provide the expected results and outputs:
Provide the actual results and outputs:
Fails
wsk action invoke --result nestedDictionaryError --param resultType "error"
error: Unable to invoke action 'nestedDictionaryError': The connection failed, or timed out. (HTTP status code 200)
Run 'wsk --help' for usage.

Works
wsk action invoke --result nestedDictionaryError
{
    "message": "error result",
    "not_response": {
        "key1": "value1",
        "key2": "value2"
    }
}

Even if response is reserved we should get a better message than that.
Additional information you deem important:

issue happens only occasionally or under certain circumstances
changes you did or observed in the environment

can't reproduce and suspect fixed because of schema removal on results.


Can't pass in custom toolbar

I'm trying to wrap react-quill in my own components, and use a custom toolbar via the toolbar prop to ReactQuill.  There are some issues that combine to prevent me from doing so.
When my component does setState, ReactQuill's shouldComponentUpdate gets called. The equality on this line however will return true on the toolbar prop, causing ReactQuill to update when it should not.
When it is doing this update, the component's state fails to include an editor property.  Therefore when it rerenders, destroyEditor fails, it can't call .destroy of undefined.
Any thoughts on this?

Mmh, I'm not able to reproduce this.
Can you check if #44 solved your issue? Otherwise, are you able to share a minimal program that presents the issue?
By the way, as you saw there is no shallow comparison of object props. I may implement something like that in the future, so please open a separate issue about it if this is important to you.
Still, the correct thing to do would be to keep a static instance of the the object your are passing as the toolbar prop around, and keep passing the same unless it changes. This should sidestep your issue completely – unless you're passing other anonymous objects as props, that is.

Closed for inactivity.
Note that with the latest release, the format of the toolbar changed radically. See Upgrading to React-Quill v1.0.0 for further information.


Hostname names should not contain underscores

Describe the bug
All hostnames contain underscores. This is against both RFC1035 and (digicert also refers to RFC1123, but I couldn't find anything in there).

The labels must follow the rules for ARPANET host names. They must start with a letter, end with a letter or digit, and have as interior characters only letters, digits, and hyphen.

I don't remember exactly what I ran into, but I posted it a while ago on discord.
To Reproduce
Run any container.
Expected behavior
The hostname of any container should have be valid (a-z A-Z 0-9, hyphen-)
Diagnostic report (REQUIRED)
OrbStack info:
Version: 1.1.0
Commit: bfae870a3b9d4fba5c1c26711ac5a5b9183bdb74 (v1.1.0)
System info:
macOS: 14.1.1 (23B81)
CPU: arm64, 8 cores
CPU model: Apple M1
Model: MacBookAir10,1
Memory: 16 GiB
Screenshots and additional context (optional)
No response

Duplicate of #490

There are plans to fix this, just not done yet.

Sorry, wrong issue.
This was fixed for domain names after you mentioned it on Discord. If you check [orb.local][http://orb.local], _ is translated to - for domains.
The Docker (Moby) engine's default behavior is to use _ for randomly generated container names, and it also allows _ in custom names. The container name is used as the hostname inside the container, but this isn't exposed anywhere else. For compatibility, OrbStack can't change this.


Notifications settings constallation

It is possible to select the following varity of options:
On every day
No Banner
No Sound
This is not how 'notifications' are used to be. We should either make a default value or deny this constallation.
@MalteBartels What do you think?

#38 has to be fixed with this change.

https://github.com/dhbw-timetable/dhbw-timetable-android/commit/5de8c45ce1ed0a39f329af17a8ca1df918058924 will force to select one valid option.


Fix for creation of UNIX domain sockets on macOS

On macOS, when attempting to connect to a domain socket, I received the following error: Warning: socket_create(): Unable to create socket [43]: Protocol not supported - #0 . I was able to resolve the issue by setting the protocol parameter of socket_create() to 0, and I changed the domain parameter to AF_UNIX for clarity. I also tested this change on Alpine Linux (via Docker) and it appears to work.
Additional reference: http://php.net/manual/en/function.socket-create.php#58257

Coverage remained the same at 50.336% when pulling a69c5913e93a530a77508395fb88b4932bcafedd on bgetsug:master into 4c958bd356c35f07adca2016773bbabb1a8d6595 on spiral:master.

Interesting. Let me test this change first prior to merge. I'm going to verify your update using this repo https://github.com/spiral/roadrunner which includes extensive tests for communication for all socket types at top of goridge.
Awesome catch! Thank you.

All tests passed.


Adds streaming versions and refactors code

Adds streaming versions and refactors code significantly to avoid duplication

@tomkail everything starting to look good. Just needs Unit tests for all the new methods


Configure split-bundle task interval different than loadReportGenerationTask-interval

Motivation
If loadBalancerReportUpdateMaxIntervalMinutes is same as loadBalancerNamespaceBundleSplitIntervalMinutes (by default = 15 mins) then splitBundleTask may read stale List of Bundles and it will end up splitting invalid bundles which cause #172
Modifications
Keep different interval value for :  loadBalancerReportUpdateMaxIntervalMinutes and loadBalancerNamespaceBundleSplitIntervalMinutes, to avoid stale-read of bundle data.
Result
It will fix #172

Is it possible to make it working for any config values? I haven't checked the code there but maybe there's a way to prevent both tasks from running st the same time.

I think we can remove splitTaskConfiguration(loadBalancerNamespaceBundleSplitIntervalMinutes) instead keep its value as loadBalancerReportUpdateMaxIntervalMinutes + 5  because we have to make sure that splitBundle should run only after loadReport gets updated, otherwise there could be a possibility to read stale loadReport value.
Any thought?

Wouldn't it be easier to chain the 2 tasks in the same thread? Compute the load report and then check for bundles to be split.
Though, my concern is that the exception in #172 could happen anyway, cause a bundle could be unloaded after the report was generated. We should just ignore that bundle and move on at that point.

Make sense. I will make the change.

updated PR by merging loadReportGeneration and splitBundleTask.

@rdhabalia Anything else for 1.16 ?


Binding for labs/Autocomplete plez!!! :pray:

Would love to have this... currently implementing my own less good version of this with TextField and Menu... except it doesn't autocomplete 🤷♂ .

All lab components are now available here.
yarn add @jsiebern/bs-material-ui-lab

These are untested yet, so we might need to iterate a bit, before everything works.