Docker python container is destroyed immediately after its creation

I define a function(called deploy_linear_regression() ) in a self-defined python module to deploy python regression models.
If I call this function within the module, everything works fine.
However, if I dont call this function within the module, but import this python module in jupyter notebook and call this function, say, module_name.deploy_linear_regression(), then the python docker container is destroyed immediately after its creation.

I think I have figured out what is going wrong.
it is a personal code mistake when trying to build my own prediction model, which leads to the destruction of the python container immediately after its construction.
However,  there is no warning to give that hint, but saying the model is deployed successfully!
And if you call clipper.get_linked_models()  in jupyter notebook, you can still get the deployed model.
But if  you call docker ps in the terminal, you cannot see the the container, which means the python container is actually dead, but the code still says the model is deployed successful.
I can get the ID of the dead python container by calling clipper.get_linked_models(), then I call docker logs container_ID  to find the error.
So maybe this bug should be fixed?

docker logs d253caff91b0
First attempting to run Python container without installing supplied dependencies.
Starting PythonContainer container
Connecting to Clipper with default port: 7000
Initializing Python function container
Traceback (most recent call last):
File "/container/python_container.py", line 95, in
model = PythonContainer(model_path, input_type)
File "/container/python_container.py", line 29, in init
self.predict_func = load_predict_func(predict_path)
File "/container/python_container.py", line 16, in load_predict_func
return cloudpickle.load(serialized_func_file)
File "/opt/conda/lib/python2.7/pickle.py", line 1384, in load
return Unpickler(file).load()
File "/opt/conda/lib/python2.7/pickle.py", line 864, in load
dispatchkey
File "/opt/conda/lib/python2.7/pickle.py", line 1096, in load_global
klass = self.find_class(module, name)
File "/opt/conda/lib/python2.7/pickle.py", line 1130, in find_class
import(module)
File "/model/modules/ClipperClient.py", line 4, in
import Data as dt
File "/model/modules/Data.py", line 8, in
findspark.init()
File "/model/modules/findspark.py", line 121, in init
spark_home = find()
File "/model/modules/findspark.py", line 32, in find
raise ValueError("Couldn't find Spark, make sure SPARK_HOME env is set"

@qingzma Clipper does not currently prune its connected container registry, so that explains why you still see the ID for the crashed container. However, performance is unaffected: Clipper will not attempt to query a container that is no longer connected.


[Coverity CID :197464]Memory - corruptions in /subsys/bluetooth/host/gatt.c

Static code scan issues seen in File: /subsys/bluetooth/host/gatt.c
Category: Memory - corruptions
Function: bt_gatt_discover
Component: Bluetooth
CID: 197464
Please fix or provide comments to square it off in coverity in the link: https://scan9.coverity.com/reports.htm#v32951/p12996

Marked as false positive in Coverity


#7744: Add support for non-4D tensor in moreh_sum, moreh_sum_backward

This PR supports for  non-4D tensor in moreh_sum, moreh_sum_backward.

https://github.com/tenstorrent/tt-metal/actions/runs/8797005233/job/24142593705 passed.


Missing change log for VS Tools for Unity 3.8.0.X

Title says it all.

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

ID: fd09a24e-305b-bb2e-a8b5-9ea9c52fd8a4
Version Independent ID: 83bf7326-a96c-3bc4-a2ff-b1f510ea9308
Content: Change Log (Visual Studio Tools for Unity, Windows) - Visual Studio
Content Source: docs/cross-platform/change-log-visual-studio-tools-for-unity.md
Product: visual-studio-dev15
GitHub Login: @TerryGLee
Microsoft Alias: tglee

@MorphiksBuilder Thanks for your feedback; we appreciate it! @conceptdev FYI

Passed this on to the engineering team, thanks for letting us know.

We haven't shipped 3.8 out of preview yet, we'll update the changelog before it RTW.

Thanks @jbevain; hope that clarifies things @MorphiksBuilder.

Can this be reopened?  The 5.8 patch hit this morning, but but VSTU patch notes are still only up to 3.7.

The changelog has been updated to 3.8.


[QA] - Create multiple transactions

create and submit many (at least 10) transactions (in the same slot)
check that the transactions were submitted successfully and that addresses balances were correctly updated

https://github.com/input-output-hk/cardano-node-tests/blob/master/cardano_node_tests/tests/test_transactions.py#L189-L220


"Duplicate declaration: File[undef] is already declared" on Windows system

Receiving the following message when updating the agent on a Windows 2008 R2 system:
Duplicate declaration: File[undef] is already declared in file /etc/puppet/environments/env/modules/filebeat/manifests/install/windows.pp:7; cannot redeclare at /etc/puppet/environments/env/modules/filebeat/manifests/install/windows.pp:11
windows.pp contents:
`class filebeat::install::windows {
$filename = regsubst($filebeat::download_url, '^https./([^/]+).[^.].', '\1')
$foldername = 'Filebeat'
file { $filebeat::tmp_dir:
ensure => directory
}
file { $filebeat::install_dir:
ensure => directory
}
remote_file {"${filebeat::tmp_dir}/${filename}.zip":
ensure      => present,
source      => $filebeat::download_url,
require     => File[$filebeat::tmp_dir],
verify_peer => false,
}
exec { "unzip ${filename}":
command  => "$sh=New-Object -COM Shell.Application;$sh.namespace((Convert-Path '${filebeat::install_dir}')).Copyhere($sh.namespace((Convert-Path '${filebeat::tmp_dir}/${filename}.zip')).items(), 16)",
creates  => "${filebeat::install_dir}/Filebeat",
provider => powershell,
require  => [
File[$filebeat::install_dir],
Remote_file["${filebeat::tmp_dir}/${filename}.zip"],
],
}
exec { 'rename folder':
command  => "Rename-Item '${filebeat::install_dir}/${filename}' Filebeat",
creates  => "${filebeat::install_dir}/Filebeat",
provider => powershell,
require  => Exec["unzip ${filename}"],
}
exec { "install ${filename}":
cwd      => "${filebeat::install_dir}/Filebeat",
command  => './install-service-filebeat.ps1',
onlyif   => 'if(Get-WmiObject -Class Win32_Service -Filter "Name='filebeat'") { exit 1 } else {exit 0 }',
provider =>  powershell,
require  => Exec['rename folder'],
}
}
`

What version of the puppet agent and server (if not masterless) are you running?

Hi pcfens,
The master is 3.8.7 and agent is 3.8.1

I'm having a little trouble duplicating the issue - can you share the relevant parts of the manifest?

Hi,
I'm getting a similar error:
Error: Failed to apply catalog: Cannot alias File[C:\temp] to ["C:/temp"]; resource ["File", "C:/temp"] already declared at /etc/puppetlabs/code/environments/playground/modules/filebeat/manifests/install/windows.pp:5
Let me see if I can find out what's wrong. I'm using Puppet agent and server version 4.4.1

@williamtsoi1 - This sounds like there's already a resource File['C:/temp']declared in some other manifest or module. I doubt that these 2 issues are related, but likely something that can be handled more gracefully by this module. I'll take a look and try to get a fix in.

@williamtsoi1 - I just pushed what I think is a reasonable fix for your problem. Just like we wouldn't manage /tmp on a Linux system in a module like this, I removed the tmp_dir file resource from the module. It does to expect the directory to exist and be writable by puppet though.

@williamtsoi1 - Did this fix take care of your issue?
@sandfred - Were you able to resolve everything? If the issue is resolved I'd like to go ahead and close this.

Since I haven't heard anything back I'm going to go ahead and close this - if you're still having issues we can re-open it though.


Accessing a previously configured upgrade plan

Suggestion in case the URL with parameters get too long: investigate the lz-string library, in particular compressToEncodedURIComponent .

By URL, or by uploading a previously saved JSON export?


Types are lost when moving code

Describe the bug
All workspace library types are converted to unknown when moving code
https://user-images.githubusercontent.com/13972192/163903384-2729375c-8527-4f8e-a6fb-cb0457aa25f4.mp4
Environment (please complete the following information):
Linux PopOS/ubuntu Vscode, lua-lanugage-server 3.1.0 with and without latest commits
Provide logs
lua.log

This went away (as far as I could tell) until recently
Now it has come back with the recent batch of commits. If I get a chance to narrow down which commit I will update

I have not noticed any weird issues with this lately. I will close to not clutter up the issues. Thank you!


add: encoding and decoding for polar rz

resolves #19

I'll close this PR, please open another one @aayush105


Wrong Variable in Laplace Distribution Chp 10.11, PDF page 1/6

Chp 10.11, PDF page 1/6

\epsilon follows a Laplace distribution which has the density
Why is there an x in the density function? \epsilon should make more sense.  Because this is the density of \epsilon.

done


Add a ToDigest trait

Proposal
Allow to write generic code with type safe wrappers around Digest
Outline
use winter_crypto::Hasher;

trait ToDigest<H: Hasher> {
    type Output: Into<H::Digest>;

    fn to_digest(&self) -> Self::Output;
}

Usage
use hash::rpo::{Rpo256, RpoDigest};

/// Type safe wrapper around [RpoDigest], represents a [NoteNullifier].
struct Nullifier(RpoDigest);
impl From<Nullifier> for RpoDigest {
    fn from(value: Nullifier) -> Self {
        value.0
    }
}

/// Complete representation of a [Nullifier].
struct NoteNullifier {
    serial_num: RpoDigest,
    // ... Note: sample code, missing fields
}

impl ToDigest<Rpo256> for NoteNullifier {
    type Output = Nullifier;

    fn to_digest(&self) -> Self::Output {
        // NOTE: sample code, missing fields
        Nullifier(Rpo256::hash_elements(self.serial_num.as_elements()))
    }
}

Note: I suppose the implementation above could also be made generic over Rpo256, which would make it much easier to migrate to rpx.

If we implement https://github.com/0xPolygonMiden/crypto/issues/312, then we can have a blanket implementation roughly like so:
use hash::rpo::{Rpo256, RpoDigest};
use winter_crypto::{ElementHasher, Hasher};
use winter_math::ToElements;

/// Trait used to associate a type with its digest wrapper
trait Digest<E: FieldElement, H: Hasher>: ToElements<E> {
    type Output;

    fn from_digest(digest: H::Digest) -> Self::Output;
}

/// Trait to perform conversion
trait ToDigest<E: FieldElement, H: Hasher>: Digest<E, H> {
    fn to_digest(&self) -> Self::Output;
}

/// Blanket implementation
impl<T: Digest<E, H>, E: FieldElement, H> ToDigest<E, H> for T
where
    H: ElementHasher<BaseField = E::BaseField>,
{
    fn to_digest(&self) -> Self::Output {
        Self::from_digest(H::hash_elements(&self.to_elements()))
    }
}

Usage
struct Nullifier(RpoDigest);
struct NoteNullifier {
    serial_num: RpoDigest,
}

impl<E> ToElements<E> for NoteNullifier
where
    E: FieldElement,
{
    fn to_elements(&self) -> alloc::vec::Vec<E> {
        todo!()
    }
}

impl<E> Digest<E, Rpo256> for NoteNullifier
where
    E: FieldElement,
{
    type Output = Nullifier;

    fn from_digest(digest: RpoDigest) -> Self::Output {
        Nullifier(digest)
    }
}

The same thing could be done with the Serializable instead, which may simplify things since it has use Hasher instead of ElementHasher. The code above could also be defined in terms of the From trait, which should give us automatic conversion, which may or may not be good (easier to write code, but less explicit code, so less benefit from type safety)

@bitwalker it would be nice if you gave your input here. I feel like the blanket implementation above is cumbersome, I endedup because of 0447-no-unused-impl-parameters. But you may have a better approach for this.

I think one of the issues with this approach is that the same object may be reduced to Digest in multiple ways. Currently, a Note object is one example where we can reduce it to NoteId or Nullifier (both of which are wrappers for Digest). We can define multiple structs for Note to accomodate one-to-one mapping (as you've suggested with NoteNullifier) but I think this actually would be more confusing than having a single struct which can be committed to in different ways.
Another example is something like NoteScript where it could be committed to either as MAST root or just a sequential hash of the underlying MAST. We don't currently do the latter - but might have to in the future.
There may be other examples (though none come to mind) where commitment to the same data needs to be computed differently based on some context.

Leaving some feedback in your code snippet @hackaugusto, since it's a little easier that way:
use hash::rpo::{Rpo256, RpoDigest};
use winter_crypto::{ElementHasher, Hasher};
use winter_math::ToElements;

// I would remove the supertrait constraint of ToElements, as it seems orthogonal to this trait
trait Digest<E: FieldElement, H: Hasher>: ToElements<E> {
    type Output;

    // I find this a bit confusing - the implementation _is_ a digest, but the trait offers a
    // method to convert "from" a digest...to a digest? I'm sure this is just a naming conflict
    // but I do think it would make things a bit too confusing when reading code involving this method
    fn from_digest(digest: H::Digest) -> Self::Output;
}

// Same sort of issue here - it's quite confusing to have something that implements ToDigest _be_ a Digest,
// I would expect the `impl Digest` type here to be an associated type of the trait, since it's hard to imagine
// a case where the implementation of this trait wouldn't be sensitive to at least one of the type parameters
// here, and the type of the digest seems like a reasonable fixed point around which any implementation variance
// would occur - but you'd have a better sense for that than I.
trait ToDigest<E: FieldElement, H: Hasher>: Digest<E, H> {
    fn to_digest(&self) -> Self::Output;
}

// This seems fine, but a couple of thoughts:
//
//  * Blanket implementations make it all but impossible to customize the behavior, so you need to be
//    really super sure that the blanket covers _everything_, or you end up needing newtypes or some other workaround
//
//  * If the design of the Digest and ToDigest traits is oriented towards enabling the blanket implementation, what would
//     things look like if you decided not to provide the blanket? Would those traits be more general and thus more broadly
//     useful? If so, I would strongly consider going that route instead, even if it means needing to manually implement those
//     traits
impl<T: Digest<E, H>, E: FieldElement, H> ToDigest<E, H> for T
where
    H: ElementHasher<BaseField = E::BaseField>,
{
    fn to_digest(&self) -> Self::Output {
        Self::from_digest(H::hash_elements(&self.to_elements()))
    }
}

I'm not super familiar with the ways in which this set of traits would be used, so I'm not sure I can provide much in the way of interesting alternatives or advice - what you've laid out here seems reasonable though! If you have a few examples of where these traits would shine, that would help for sure.
I do think @bobbinth raises a good point, which is that when you have conversions like this that are ambiguous at a callsite without the turbofish operator (i.e. specifying the concrete types with ::<>), then it may be a sign that a different abstraction is more appropriate - but that's not always the case (consider collect, a method which often requires turbofish simply because the compiler isn't able to reason through all of the implicit types involved in a given iterator chain). Hard for me to say what a better approach would be though without feeling the pain points myself.

We can define multiple structs for Note to accomodate one-to-one mapping (as you've suggested with NoteNullifier) but I think this actually would be more confusing than having a single struct which can be committed to in different ways.

If wrappers is a no-go, we can 1. use a method for these special cases (like we do now) 2. change the associated type to a generic. Which one do you prefer?
@bitwalker thanks for having a look! To give you more context. We use hashes everywhere, e.g. mast root, note id/nullifier/recipient, account/note/nullifier dbs root, and so on. In all these cases we have by default a Digest type, this means we often have functions with multiple Digest as arguments, and we have no type safety. So the idea above was 1. wrap the digest to improve typing 2. have a trait to abstract over all things that can be hashed.


Timeline events no longer received for MacOS

Breaking change is here: https://dart-review.googlesource.com/c/sdk/+/131360
DevTools relies on Timeline events for features like the Timeline page and Network Profiler. After this change, we no longer receive timeline events from MacOs devices.
See message in Observatory:

It looks like the events are being forwarded, but they should at least be sent to both streams. The default behavior of flutter run should enable our tools to work without having to pass additional flags as workarounds.
@bkonyi

After talking to @bkonyi we figured out the issue. In DevTools, we were adding the --trace-systrace flag, which before the CL landed to forward those events, did not affect us. Removing that flag fixes the issue and we receive timeline events as expected.
We should add a note to the message that says, "If you'd like to see timeline events in Observatory, please disable the --trace-systrace flag in your <Insert platform specific config file here (e.g. MainFlutterWindow.swift for MacOS)>.
Ben, is there any way we can modify this flag at runtime? It would be useful if we could do this from the DevTools Timeline when --trace-systrace is enabled.

No, it's not currently possible to swap out timeline recorders at runtime. This is something that's theoretically possible but probably wouldn't be considered high priority at this point with the NNBD work going on.


Use YAML instead of env. vars. for HW configuration.

Future development will need more configurable parts. YAML is better suited for that and integrates well with Python.
If the default YAML-file is stored as a Git controlled file and the detector check for a YAML-file in /home/pi/wurb_settings before the default location then there will be no problems with the git pull command.

I strongly agree with the need to move the configuration settings from environment variables to something else.  I will certainly use them in the future.
Not wishing to start a flame war here, because as am not knowlegeable enough and have no preference  about either of them, but have you considered TOML vs YAML? I am only asking, because I recently tried to use poetry for python project management and it uses TOML file, which was advertised as much better than 'requrements.txt` and anything else before :-).
Putting the visual difference aside, what would be the top three technical arguments to choose one over the other (YAML vs. TOML)?
I know that sometimes these discussions can get bogged down in a typical example of bike-shedding and I accept that developers personal experience and preference is valid reason to select one over the other.  Still, it could be useful to have a quick evidence-driven comparison.


Clear the global out of date configs if they were previously set

Fixes https://github.com/keybase/client/issues/9579.
r? @maxtaco

I've been staring at this for a little while, and I'm not sure I can improve on what's there. Everything's protected by this shared lock, and encapsulating that is hard to do without creating another one of those Account-style closure-taking APIs that we hate. In this case, even moving all of these updates into a single function with a consolidated Lock/Unlock is hard, because this defer a.G().NotifyRouter.HandleClientOutOfDate needs to happen after unlock (presumably because it re-acquires the same lock via G.GetOutOfDateInfo somewhere), and that means the unlock can't be deferred from the most natural place. We could put that call on another goroutine, but then I feel like I'm complicating things instead of simplifying them :|
Even something as simple as putting the three member clears behind a Clear function seems unfortunately complicated. Either that function takes the lock itself (and therefore lives on G rather than on GetOutOfDateInfo where it should), or it doesn't take the lock and then it's a footgun that looks like it's safe to call in places it isn't.
I'm going to run with what's here unless there's a different approach you think I should try?

I just meant put those 3 = "" lines into a subfunction is all

leave it locked as before...

but i really don't care either way


[improve] [pip] PIP-348: Trigger offload on topic load stage

Fixes #xyz

Main Issue: #xyz

PIP: #xyz

Motivation

Modifications

Verifying this change

[ ] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

[ ] Dependencies (add or upgrade a dependency)
[ ] The public API
[ ] The schema
[ ] The default values of configurations
[ ] The threading model
[ ] The binary protocol
[ ] The REST endpoints
[ ] The admin CLI options
[ ] The metrics
[ ] Anything that affects deployment

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository:

Need to update the discuss and vote thread.


Refactor with @angular/material

Use material UI instead of bootstrap
https://material.angular.io/components/categories

use dark theme with blue colors

use mat-card for contact list

Reduce margins between lateral border

use placeholders in forms

use FAB button to ADD

remove back button

use logo and title as routes to home

I'll take this one

we are getting this error
where we need to change url error is:
zone.js:3372 GET http://localhost:4200/contacts 404 (Not Found)

Read the manual


Update to nvidia-docker release

The older release candidate will throw an error.

Updating to an stable version makes sense. Thanks for your contribution!


Handle unavailable AccountBalance

The AccountBalance is an optional piece of data coming from SDK but Zashi fallbacks to .zero if it happens. nil value is a regular state we should reflect in the UI though so it must be handled and not ignored.

Can we display a loader instead of 0 - is that an acceptable solution for 1.0? (to discuss with Josh and Richard)

@LukasKorba Discussed this with Josh and Richard, and we can proceed with the loader!


refactor!: update module to v4

BREAKING CHANGE: import paths will need to change to v4

If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/go-mod-messaging/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:

[ ] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[ ] I am not introducing a new dependency (add notes below if you are)
[ ] I have added unit tests for the new feature or bug fix (if not, why?)
[ ] I have fully tested (add details below) this the new feature or bug fix (if not, why?)
[ ] I have opened a PR for the related docs change (if not, why?)

Testing Instructions

New Dependency Instructions (If applicable)

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 63.75%. Comparing base (1d521fa) to head (c98b13c).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #362   +/-   ##
=======================================
  Coverage   63.75%   63.75%
=======================================
  Files          28       28
  Lines        1258     1258
=======================================
  Hits          802      802
  Misses        391      391
  Partials       65       65

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


For a 0.21.7 release

#886 #890 #889 #888

Codecov Report

Merging #891 (af72020) into master (c4d6309) will increase coverage by 0.46%.
The diff coverage is 74.62%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##           master     #891      +/-   ##
==========================================
+ Coverage   85.31%   85.78%   +0.46%
==========================================
  Files          40       40
  Lines        3569     3567       -2
==========================================
+ Hits         3045     3060      +15
+ Misses        524      507      -17

Impacted Files
Coverage Δ

src/operations.jl
90.00% <ø> (ø)

src/resampling.jl
91.19% <66.66%> (-0.21%)
:arrow_down:

src/measures/probabilistic.jl
86.30% <67.85%> (+22.19%)
:arrow_up:

src/measures/measures.jl
70.58% <72.22%> (+0.29%)
:arrow_up:

src/measures/continuous.jl
92.59% <86.66%> (ø)

src/measures/finite.jl
98.60% <100.00%> (ø)

src/measures/loss_functions_interface.jl
73.21% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Can't delete page

Can't delte page. Server displays Error 500.

Could you provide more information? Django and django CMS versions plus the full traceback and settings

I had have forgotten that I can view the traceback if I change DEBUG on True, I'm feeling embarrassed :-). A flash plugin was dropped. Now all works fine, thank you.
On Sat, 30 May 2015 07:56:37 -0700
Iacopo Spalletti<EMAIL_ADDRESS>wrote:

Could you provide more information? Django and django CMS versions plus the full traceback and settings

Reply to this email directly or view it on GitHub:
https://github.com/divio/django-cms/issues/4128#issuecomment-107049743

--
Best regards,
Vladimir Vasilenko<EMAIL_ADDRESS>

Thanks for the update!


Consider refactoring node-feature-discovery to run as a daemonset

Instead of requiring the operator to configure a one-shot / periodic job, a node-feature-discovery daemon pod could be responsible for continuously fleecing node capabilities. This way eventually NFD could be included in cluster addons.
cc @jeremyeder @balajismaniam

Currently, the discovery pod exits immediately after advertising the feature labels. As such it is setup as a one-shot job for simplicity and make sure it doesn't end up in a CrashLoopBackOff state. We might need to change how the discovery job runs (i.e., make it a daemon or long-running process) before switching to using DaemonSet.

What do you think about a flag that tells NFD to daemonize itself instead of exiting after initial discovery?

At the very least, we would want this as an option to NFD.
I agree we will see requests for a pluggable node agent to handle things like "extended-node-fitness": a deeper inspection of the node's running config and comparing it against a profile.
My desire is to use tuned-adm verify for this:
https://git.fedorahosted.org/cgit/tuned.git/tree/man/tuned-adm.8#n55
tuned is shipped in OpenSUSE (and Gentoo I believe).

@ConnorDoyle Yes, that will work.

I like the run to completion model.
And there are also requirements to have NFD detect changes to node features, capabilities etc. as they occur.
Is there any method currently with k8s, to have it execute the NFD pod on a node in response to a specific event on/for that node?
If not, would it be reasonable to consider a solution along those lines, either within k8s itself or externally with the appropriate k8s support?

AFAIU making NFD a DaemonSet would be the only way to make sure that it is run on every node, and, that it would be automatically run on new nodes being added

I'd propose closing this issue now that #105 has been merged.


Deleted App's Database Being Returned

After getting a database reference and deleting the associated app, Firebase will always return the same instance to the initial database for an app's lifecycle.
The issue lies within FIRDatabase: https://github.com/firebase/firebase-ios-sdk/blob/master/Firebase/Database/Api/FIRDatabase.m#L122.
The instances array will hold an outdated reference of the database. The outdated database can point to a then deleted FIRApp. Perhaps when a FIRApp is deleted, any databases it owns should be removed from the instances array.

Xcode version: Version 8.3.3 (8E3004b)
Firebase SDK version: 4.0.4
Library version: 4.0.0
Firebase Product: database

Steps to reproduce:
1.) Create a Firebase app with a specific name.
2.) Authenticate against the app.
3.) Get a Firebase database reference.
4.) Sign out.
5.) Delete the Firebase app.
6.) Create a Firebase app using the same name used in step 1.
7.) Authenticate against the Firebase app created in step 6.
8.) Get a Firebase database reference with databaseForApp: using the app created in step 6.
The final Firebase database reference's app will actually point to the app created in step 1. This causes the database's authentication chain to break. Since the user is authenticated with the app created in step 6, the user will not be able to use the database.

Sorry, was on vacation the past week. Getting back to this now!

@dylancopeland the PR should fix the issue but I wanted to check - what's the use case / reason for deleting FIRApp and recreating it?

@ryanwilson Awesome, thank you!
Our data is sharded across a few Firebase projects. We were hoping to delete an old FIRApp that a user may have used from a previous session. The whole point of that was just to free up local & Firebase resources.

Okay great, thanks for the reply. I created a new issue (#202) to investigate some of the other SDKs as well to make sure we're cleaning up properly.
For your use case, I'd just suggest making sure that when you delete the FIRApp ensure that all existing instances are cleared out (any properties, local variables, etc).
Thanks for reporting this! I'll close it when #194 is closed.

Thanks again for reporting, @dylancopeland.


SEAB-5015: Use [skip] to run partial CI build

Description
When pushing non-code changes, it is ideal to save build minutes by skipping CircleCI tests. However, using the [skip ci] tag (which skips the entire pipeline) isn't always great because automatic deployment requires a build.
One solution is having the option to run a short CI. To achieve this, this PR attempts to implement a custom tag, [skip]: if included in the most recent commit message, CircleCI should skip all jobs excluding the actual build (i.e. skip testing-related jobs). Whether or not to skip testing is decided by an intermediate job called skip_check: CircleCI should run all tests if skip_check succeeds, and should stop after the build if skip_check fails (i.e. finds [skip] in the commit message).
Review Instructions
The most recent commit uses the [skip] tag, so: 1) the build job should succeed, and 2) skip_check should fail, meaning the remaining CI jobs should be skipped.

Other thoughts:

A slight drawback: if [skip] is used, something needs to fail in order to skip future jobs, so overall it looks like the pipeline failed. Would this affect the build required for deployment? (The original goal was to conditionally run steps in a job, so [skip] would just bypass certain actions during the run, but I haven't yet found a way to incorporate the commit message into conditional steps)
Are there any other jobs that, when the [skip] tag is used, should be run alongside the build?
Open to renaming skip_check, which may seem a bit unintuitive? (i.e. it fails if it succeeds to find [skip], and succeeds if it fails to find [skip])

Issue
SEAB-5015
Security and Privacy
If there are any concerns that require extra attention from the security team, highlight them here and check the box when complete.

[x] Security and Privacy assessed

e.g. Does this change...

Any user data we collect, or data location?
Access control, authentication or authorization?
Encryption features?

Please make sure that you've checked the following before submitting your pull request. Thanks!

[x] Check that you pass the basic style checks and unit tests by running mvn clean install
[x] Ensure that the PR targets the correct branch. Check the milestone or fix version of the ticket.
[x] Follow the existing JPA patterns for queries, using named parameters, to avoid SQL injection
[x] If you are changing dependencies, check the Snyk status check or the dashboard to ensure you are not introducing new high/critical vulnerabilities
[x] Assume that inputs to the API can be malicious, and sanitize and/or check for Denial of Service type values, e.g., massive sizes
[x] Do not serve user-uploaded binary images through the Dockstore API
[x] Ensure that endpoints that only allow privileged access enforce that with the @RolesAllowed annotation
[x] Do not create cookies, although this may change in the future
[x] If this PR is for a user-facing feature, create and link a documentation ticket for this feature (usually in the same milestone as the linked issue). Style points if you create a documentation PR directly and link that instead.

If the additional CircleCI tests are required to merge a PR, then the most recent commit cannot contain [skip]? I guess in order to skip tests for the merge, you would include [skip] in the merge commit?

Are there any other jobs that, when the [skip] tag is used, should be run alongside the build?

I think you'd still want to run the relatively short unit tests job.
It uploads the jar that is sometimes used for the UI

3. Maybe a more "positive" name? Instead of skipTests, quickBuild (especially since you are going to be running the unit tests)?

Kinda prefer not making something up, but point taken on unit tests now.
We could do skipITs
https://maven.apache.org/surefire/maven-failsafe-plugin/examples/skipping-tests.html


Add a note to CameraGeometry docs about from_name()

Note that from_name() is not guaranteed to correspond with event data.
Closes #2484

CameraTypes is a set, you can't Index it

Can we  (also?) raise an actual code warning?
i.e.:
warnings.warn(".from_name methods use pre-defined data that is likely different from the data being analyzed. Access instrument information via the SubarrayDescription instead.")

The docs failure here is real and due to the changes made

@kosack, I added the actual warning now to those methods and made it fail the CI if it occurs unexpectedly.
It's your PR, so you cannot really approve, but please have a look.
@Tobychev  please review again :)


mipgen linearized/srgb issue

It looks like if you are writing ktx with astc compression from mipgen, that the .srgb parameter in the astc configuration is not initialized or set? In the case of a non-ktx file, g_linearized is used to decide if the final data output is fromLinearToRGB or fromLinearTosRGB... however I don't see matching logic to control astc output from ktx code. I think the files are always being created as linear, which would be a quality loss for color images.
Perhaps I'm missing something somewhere, but it seems like a line along the lines of:
config.astc.srgb = !g_linearized;

is required after parseOptionString to output the correct color space? Or perhaps input params for astc compression need expanding to astc_[fast|thorough]_[srgb|linear]_[ldr|hdr]_WxH?

Correct, sRGB has not been implemented in the ASTC path, I had set aside working ASTC due to flakiness and crashes in ARM's encoder library.  Side note: the library has been rewritten and it we need to upgrade to the new version.
Another thing in my notes is that we do not support non-divisible-by-4 textures in the ASTC path.
Related issue: we also were not honoring the format in the KTX file until https://github.com/google/filament/pull/4039
I'll look into this.


Implement JpqlSerializer for JpqlCoalesce

Backgrounds

In Kotlin JDSL 3.0.0, the Query objects no longer know how to draw themselves as SQL String.
The Query object is drawn in JPQL String by JpqlSerializer.

Requirements

Please implement  JpqlSerializer that draws JpqlCoalesce as a SQL String.
Please implement a unit test for the implemented class.

Contribution

Please check if there is an assignee in this issue. And if it don't have an assignee, please change the assignee to yourself.
Please check the commit convention through the commitlint.config.js file. The commit  convention also described in the PR template.
When you use intellij, please set the code style through the .editorconfig file.
Please create the PR for develop/3.0.0 as the base branch.
If you have any questions, please leave comment in Kotlin-JDSL Discord Channel in LINE Open Source

제가 가져 갈게요 ~

@sbcoba 이슈 할당 받으신지 좀 오래되었는데 구현이 안되어서요.. 제가 가져가도 괜찮을까요?

아 죄송합니다. 부탁드리겠습니다.


Make all dependencies optional

Except for log.
Closes #71
Closes #72
This PR refactors the internals of the fmt module so we can optionally exclude dependencies and their supported features. The goal of making things optional is to improve compile times and reduce artifact sizes so rather than trying to shim the same public API we exclude swathes of API that are tied to specific dependencies when those dependencies aren't available.
By default all current dependencies are included. Since env_logger usually lives at the top of a dependency graph, if an application disables default features then it should be unlikely that another dependency adds them back in.
This is still in a bit of a strawman phase, there might be other approaches we'll want to consider.

A potential source of breakage here is if folks are currently using no_default_features with env_logger to exclude regex. With this change that will now also exclude styling and timestamps.

Possibly also worth noting that libraries using env_logger as a dev-dependency won't cause the default features to be activated if you happen to depend on them.

cc @briansmith
This makes a pretty big impact on compile-times. On my machine locally for release builds I'm waiting ~18s with default features, and ~1.5s without them. Artifact size is also a bit smaller.
I'll do a proper review of the APIs that are available and unavailable depending on features, but this seems worth following through for folks that care about compile times and don't care about the format.
What do you think?

Thank you for this. The community needs more of these PRs.

I did a quick run through source on GitHub and came up with a few dependencies that would see a change in their default format following this PR:

tower-h2
mesabox
compiletest (and other tools within rust-lang)
srt-transport
quickcheck

I'm starting to lean towards pushing this and #82 together as a minor version bump, so 0.6.0 where we can start that version with clear semantics about how changes to the default format will be handled. I'll open up an issue to get some feedback.

I've added a simple test harness as a local crate that runs tests for all feature permutations. The number of permutations will increase exponentially with the number of optional features so in the future we might need a different strategy for maintaining confidence that everything plays nicely.


Services stopped working with latest update

I updated baby buddy and home assistant at the same time so I'm not sure which one is the culprit, but services stopped working as of the 1 April home assistant update.
Happen to anyone else? Any ideas what it could be?

Any errors in log?

None that I can see.

Correction- I noticed there was no associated child and tried to add one. Here is the error from that:
aiohttp.client_exceptions.ContentTypeError: 0, message='Attempt to decode JSON with unexpected mimetype: text/plain; charset=utf-8', url=URL('https://www.galaxyfamily.net/api/children/

I think the issue may be that it does not seem to add the port in the API call

Seems unlikely. Unless something with your BB host/port also changed?

I was previously using the local dns but that won't even get a response now (though it works from a browser) so I removed the integration and added it as the external url. That one can be added but does not receive data or make service calls without this error.
Here's the full error:
`This error originated from a custom integration.
Logger: homeassistant.helpers.script.websocket_api_script
Source: custom_components/babybuddy/client.py:64
Integration: Baby Buddy (documentation, issues)
First occurred: April 9, 2022, 9:40:06 PM (6 occurrences)
Last logged: 1:28:09 AM
websocket_api script: Error executing script. Unexpected error for call_service at pos 1: 0, message='Attempt to decode JSON with unexpected mimetype: text/plain; charset=utf-8', url=URL('https://www.url.com/api/children/')
websocket_api script: Error executing script. Unexpected error for call_service at pos 1: 0, message='Attempt to decode JSON with unexpected mimetype: text/html', url=URL('http://www.url.com/api/children/')
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 379, in _async_step
await getattr(self, handler)()
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 582, in _async_call_service_step
await service_task
File "/usr/src/homeassistant/homeassistant/core.py", line 1634, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1671, in _execute_service
await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
File "/config/custom_components/babybuddy/init.py", line 178, in async_add_child
await self.client.async_post(ATTR_CHILDREN, data)
File "/config/custom_components/babybuddy/client.py", line 64, in async_post
error = await resp.json()
File "/usr/local/lib/python3.9/site-packages/aiohttp/client_reqrep.py", line 1103, in json
raise ContentTypeError(
aiohttp.client_exceptions.ContentTypeError: 0, message='Attempt to decode JSON with unexpected mimetype: text/plain; charset=utf-8', url=URL('https://www.url.com/api/children/')
`

This is starting to sound like [this] (https://github.com/jcgoette/baby_buddy_homeassistant/issues/54#issuecomment-1004330905).
Are you familiar with editing the code in your own HA instance?

It looks like its related to the new CSRF_TRUSTED_ORIGINS requirement that I think others have had problems with. I needed to add both external and local urls and now I can access both separately. Ive reinstalled the add on but its still not recognizing either of those instances through Home Assistant.

Are you familiar with editing the code in your own HA instance? If so, could you edit this, restart Home Assistant, and attempt workflow again?
https://github.com/jcgoette/baby_buddy_homeassistant/blob/c69f29d0217196152a02e2fa364655fa8c8f7460/custom_components/babybuddy/client.py#L64
From error = await resp.json()
To error = await resp.json(content_type=None)

I made that code change and I'm not sure if it made a difference. I can't seem to get it to recognize the existing child that's in there. Any ideas?

`This error originated from a custom integration.
Logger: homeassistant.helpers.script.websocket_api_script
Source: custom_components/babybuddy/client.py:64
Integration: Baby Buddy (documentation, issues)
First occurred: 11:09:33 PM (1 occurrences)
Last logged: 11:09:33 PM
websocket_api script: Error executing script. Unexpected error for call_service at pos 1: Expecting value: line 1 column 1 (char 0)
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 379, in _async_step
await getattr(self, handler)()
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 582, in _async_call_service_step
await service_task
File "/usr/src/homeassistant/homeassistant/core.py", line 1634, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1671, in _execute_service
await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
File "/config/custom_components/babybuddy/init.py", line 178, in async_add_child
await self.client.async_post(ATTR_CHILDREN, data)
File "/config/custom_components/babybuddy/client.py", line 64, in async_post
error = await resp.json(content_type=None)
File "/usr/local/lib/python3.9/site-packages/aiohttp/client_reqrep.py", line 1119, in json
return loads(stripped.decode(encoding))
File "/usr/local/lib/python3.9/json/init.py", line 346, in loads
return _default_decoder.decode(s)
File "/usr/local/lib/python3.9/json/decoder.py", line 337, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/local/lib/python3.9/json/decoder.py", line 355, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
`

Hmm. Can you try changing to resp.text()?

OK. Where is that?

Same line as before.
From error = await resp.json()
To error = await resp.text()

I made that change and tried to recreate child - got an error in every language! 🤣
This error originated from a custom integration.

Logger: custom_components.babybuddy.client
Source: custom_components/babybuddy/client.py:65
Integration: Baby Buddy (documentation, issues)
First occurred: 9:13:56 PM (1 occurrences)
Last logged: 9:13:56 PM

Could not create children. error: <!DOCTYPE html>   <meta charset="utf-8">

404

That's funny. Not sure how much it helps.
Does this part mean anything to you?
Copyright (c) 2021 Synology Inc. All rights reserved.

Yes. Both baby buddy and home assistant are running in a Docker container on a Synology NAS. It appears to be a generic Synology 404 page, but I don't get that when I am accessing the api url directly.

I'm messing with the baby buddy settings and I think I might be getting closer. I think there was a problem with my setup as far as the new CSRF_ORIGINS setting, but also now that I think I've gotten around that, I'm getting this
This error originated from a custom integration.

Logger: custom_components.babybuddy
Source: custom_components/babybuddy/__init__.py:134
Integration: Baby Buddy (documentation, issues)
First occurred: 1:18:40 AM (29 occurrences)
Last logged: 1:46:40 AM

Unexpected error fetching babybuddy data: 'count'
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 190, in _async_refresh
    self.data = await self._async_update_data()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 150, in _async_update_data
    return await self.update_method()
  File "/config/custom_components/babybuddy/__init__.py", line 134, in async_update
    if children_list[ATTR_COUNT] == 0:
KeyError: 'count'

I rolled back to BabyBuddy 1.9.3 and removed the new CSRF_ORIGINS settings and it works fine as before - that version is fine for my use case. I assume it's something related to docker settings and https://github.com/babybuddy/babybuddy/issues/393 but I can't spend more time with it while keeping track of the new kiddo. 😄 Thank you for the help!

Updated HA last night and ran into the same issue as @sfgabe. Rolled back HAOSS to before the april update and still had the issue. Changed the version of my BabyBuddy docker container and removed CSRF_ORIGIN env variable and now it works...

I have Swag setup to access HA outside the network, but HA integration is accessing BB locally through my IP, not my domain. All aspects of BB were 'unavailable' in HA. However, I do have a few REST items in the config pulling information (how many diaper changes in a day) and that was working, but that is NOT from the BB integration.

I have a similar setup to @Borlean where I'm using nginx, and have an outside https domain but was accessing through home assistant via the http local ip.

The only thing I can add at this point is: if your nginx.conf has the line proxy_pass in it for BB, check your proxy_set_header settings in nginx.conf. I am using latest HA and latest BB image and all works for me.

My nginx.conf file for BB does NOT have the proxy_pass line. It's the 2021/10/24 version, is yours newer? I don't even see a proxy_set_header option.

It stopped working on my installation as well.
What I can see is this in the logs after setting up the integration:
Source: helpers/update_coordinator.py:222
Integration: Baby Buddy ([documentation](https://github.com/jcgoette/baby_buddy_homeassistant), [issues](https://github.com/jcgoette/baby_buddy_homeassistant/issues))
First occurred: 07:32:49 (2 occurrences)
Last logged: 07:39:05

Error fetching babybuddy data: Cannot connect to host <IP_ADDRESS>:80 ssl:default [Connect call failed ('<IP_ADDRESS>', 80)]```

It seems it tries to connect on port 80 but I have set up the integration on a different port.
This looks odd to me.

@myxor looks like you left off the http or https when setting up.

@jcgoette
I re-setup the integration now multiple times with http:// and also https:// but the error messages stays the same no matter which port i type in:

Error fetching babybuddy data: Cannot connect to host <IP_ADDRESS>:80 ssl:default [Connect call failed ('<IP_ADDRESS>', 80)]

If i type in a wrong port the setup of the integration does not work of course. So i type in the correct port and setup confirms it with a success message. Right after that i see the above error in the log where the port is set to 80 again.
Can i somehow lookup what is stored as configuration for the integration in the database? As the frontend does not show the port in the integration overview and therefore i am not sure if the port is even stored in the configuration.

Did you obfuscate and truncate your API key? Because if not, it looks like not enough characters.
Checking that you've set to this integration successfully before?

Did you obfuscate and truncate your API key? Because if not, it looks like not enough characters.

Yes i did. Sorry - i should have pointed that out.

Checking that you've set to this integration successfully before?

It was working around one week ago for sure. Meanwhile i updated HA to 2022.4.6 and BB to v1.10.2.

Collecting more data: what is your setup like? Docker? Local or hosted HA and BB? NGINX? If so, would you (or anyone else on this thread) be willing to share your nginx.conf?

My setup:

HA and BB in docker container
Nginx in docker dontainer as reverse proxy

Nginx config part:
Note:  [my external server name] is my DNS of the server.
# Baby Buddy
server {
     listen 8127 ssl;
     server_name [my external server name];
     ssl_certificate /etc/letsencrypt/live/[my external server name]/fullchain.pem;
     ssl_certificate_key /etc/letsencrypt/live/[my external server name]/privkey.pem;

     location / {
          proxy_pass http://<IP_ADDRESS>:8027;
          proxy_set_header X-Forwarded-For $remote_addr;
      }
  }

So i am trying to setup the integration with either
http://<IP_ADDRESS>:8027 or https://[my external server name]:8127  and i also tried https://<IP_ADDRESS>:8127.
I can access BB with all three of the above addresses via browser while the last one having a SSL certificate not matching the address.

My configuration is HAOS on VM, Babybuddy and NGINX proxy manager running in docker in another VM, different IP addresses. Baby buddy accessible normally either via internal or external access. Configured baby buddy using the local IP address rather than external domain

I'm not an expert, but this looks strange to me. I would expect:

listen line to be 443 if you are using SSL
proxy_pass to be http://<IP_ADDRESS>:8027;

Beyond that, I can provide some additional changes to try:
http {

    # Connection header for WebSocket reverse proxy
    map $http_upgrade $connection_upgrade {
        default upgrade;
        "" close;
    }

    map $remote_addr $proxy_forwarded_elem {
        # IPv4 addresses can be sent as-is
        ~^[0-9.]+$ "for=$remote_addr";

        # IPv6 addresses need to be bracketed and quoted
        ~^[0-9A-Fa-f:.]+$ "for=\"[$remote_addr]\"";

        # Unix domain socket names cannot be represented in RFC 7239 syntax
        default "for=unknown";
    }

    map $http_forwarded $proxy_add_forwarded {
        # If the incoming Forwarded header is syntactically valid, append to it
        "~^(,[ \\t]*)*([!#$%&'*+.^_`|~0-9A-Za-z-]+=([!#$%&'*+.^_`|~0-9A-Za-z-]+|\"([\\t \\x21\\x23-\\x5B\\x5D-\\x7E\\x80-\\xFF]|\\\\[\\t \\x21-\\x7E\\x80-\\xFF])*\"))?(;([!#$%&'*+.^_`|~0-9A-Za-z-]+=([!#$%&'*+.^_`|~0-9A-Za-z-]+|\"([\\t \\x21\\x23-\\x5B\\x5D-\\x7E\\x80-\\xFF]|\\\\[\\t \\x21-\\x7E\\x80-\\xFF])*\"))?)*([ \\t]*,([ \\t]*([!#$%&'*+.^_`|~0-9A-Za-z-]+=([!#$%&'*+.^_`|~0-9A-Za-z-]+|\"([\\t \\x21\\x23-\\x5B\\x5D-\\x7E\\x80-\\xFF]|\\\\[\\t \\x21-\\x7E\\x80-\\xFF])*\"))?(;([!#$%&'*+.^_`|~0-9A-Za-z-]+=([!#$%&'*+.^_`|~0-9A-Za-z-]+|\"([\\t \\x21\\x23-\\x5B\\x5D-\\x7E\\x80-\\xFF]|\\\\[\\t \\x21-\\x7E\\x80-\\xFF])*\"))?)*)?)*$" "$http_forwarded, $proxy_forwarded_elem";

        # Otherwise, replace it
        default "$proxy_forwarded_elem";
    }

	# Baby Buddy
    server {
        listen 443 ssl;
        server_name [my external server name];

        # SSL
		ssl_certificate /etc/letsencrypt/live/[my external server name]/fullchain.pem;
		ssl_certificate_key /etc/letsencrypt/live/[my external server name]/privkey.pem;

        location / {
            proxy_pass http://<IP_ADDRESS>:8027;
            proxy_http_version 1.1;
            proxy_cache_bypass $http_upgrade;

            # Proxy headers
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection $connection_upgrade;
            proxy_set_header Host $host;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header Forwarded $proxy_add_forwarded;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header X-Forwarded-Proto $scheme;
            proxy_set_header X-Forwarded-Host $host;
            proxy_set_header X-Forwarded-Port $server_port;
        }
    }
}

I'm not an expert, but this looks strange to me. I would expect:
listen line to be 443 if you are using SSL
proxy_pass to be http://<IP_ADDRESS>:8027;

I am using non-default SSL port and having multiple network interfaces - therefore the port and IP.
after adding your suggestions to my nginx config i am now getting an actual python error:
Unexpected error fetching babybuddy data: 'count'

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 190, in _async_refresh
    self.data = await self._async_update_data()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 150, in _async_update_data
    return await self.update_method()
  File "/config/custom_components/babybuddy/__init__.py", line 134, in async_update
    if children_list[ATTR_COUNT] == 0:
KeyError: 'count'

Progress! :)
I have one child set up on my BB installation.
Btw: @jcgoette  thx for your help!

That's perfect!
Maybe the other folks on here could try config from https://github.com/jcgoette/baby_buddy_homeassistant/issues/60#issuecomment-1105149254.

I added some hopefully helpful debug-level logging in v2.4.1 if anyone wants to upgrade and enable debug-level logging.
# Example configuration.yaml entry
logger:
  default: info
  logs:
    custom_components.babybuddy: debug

Debug log:
2022-04-23 12:19:53 DEBUG (MainThread) [custom_components.babybuddy.client] Client API Token: 0ef2516c6 [truncated by me]
2022-04-23 12:19:53 DEBUG (MainThread) [custom_components.babybuddy.client] Client URL: http://<IP_ADDRESS>:8027
2022-04-23 12:19:53 DEBUG (MainThread) [custom_components.babybuddy.client] GET URL: http://<IP_ADDRESS>:8027/api/
2022-04-23 12:20:23 DEBUG (MainThread) [custom_components.babybuddy.client] GET response: {"children":"http://<IP_ADDRESS>/api/children/","changes":"http://<IP_ADDRESS>/api/changes/","feedings":"http://<IP_ADDRESS>/api/feedings/","notes":"http://<IP_ADDRESS>/api/notes/","sleep":"http://<IP_ADDRESS>/api/sleep/","temperature":"http://<IP_ADDRESS>/api/temperature/","timers":"http://<IP_ADDRESS>/api/timers/","tummy-times":"http://<IP_ADDRESS>/api/tummy-times/","weight":"http://<IP_ADDRESS>/api/weight/","height":"http://<IP_ADDRESS>/api/height/","head-circumference":"http://<IP_ADDRESS>/api/head-circumference/","bmi":"http://<IP_ADDRESS>/api/bmi/"}
2022-04-23 12:20:23 DEBUG (MainThread) [custom_components.babybuddy.client] Endpoints: {'children': 'http://<IP_ADDRESS>/api/children/', 'changes': 'http://<IP_ADDRESS>/api/changes/', 'feedings': 'http://<IP_ADDRESS>/api/feedings/', 'notes': 'http://<IP_ADDRESS>/api/notes/', 'sleep': 'http://<IP_ADDRESS>/api/sleep/', 'temperature': 'http://<IP_ADDRESS>/api/temperature/', 'timers': 'http://<IP_ADDRESS>/api/timers/', 'tummy-times': 'http://<IP_ADDRESS>/api/tummy-times/', 'weight': 'http://<IP_ADDRESS>/api/weight/', 'height': 'http://<IP_ADDRESS>/api/height/', 'head-circumference': 'http://<IP_ADDRESS>/api/head-circumference/', 'bmi': 'http://<IP_ADDRESS>/api/bmi/'}
2022-04-23 12:20:23 DEBUG (MainThread) [custom_components.babybuddy.client] GET URL: http://<IP_ADDRESS>/api/children/
2022-04-23 12:20:27 ERROR (MainThread) [custom_components.babybuddy] Error fetching babybuddy data: Cannot connect to host <IP_ADDRESS>:80 ssl:default [Connect call failed ('<IP_ADDRESS>', 80)]
2022-04-23 12:20:27 DEBUG (MainThread) [custom_components.babybuddy] Finished fetching babybuddy data in 4.479 seconds (success: False)

Looks like the port is missing in the API endpoint list response JSON as i pointed out here: https://github.com/babybuddy/babybuddy/issues/446

I think you're right. My debug log pulls a HTML page of my pihole server, which is of course on port 80. Will post logs when I can get to a PC

Solution #2 looks promising.

I'm confused, haven't the proposed solutions so far been to open port 80 on the Baby Buddy server? That may be a workaround, but the bug is with the HACS integration using port 80 when it should be something else (typically 8000). How do we fix that?

All current signs point to an issue with reverse proxy setup. Your own debug logs show the host:port correctly until it hits /api/ endpoints, which is on the BB/Django side of things:
2022-04-23 08:29:29 DEBUG (MainThread) [custom_components.babybuddy.client] GET URL: http://babybuddy:8000/api/
2022-04-23 08:29:29 DEBUG (MainThread) [custom_components.babybuddy.client] GET response: {"children":"http://babybuddy/api/children/","changes":"http://babybuddy/api/changes/","feedings":"http://babybuddy/api/feedings/","notes":"http://babybuddy/api/notes/","sleep":"http://babybuddy/api/sleep/","temperature":"http://babybuddy/api/temperature/","timers":"http://babybuddy/api/timers/","tummy-times":"http://babybuddy/api/tummy-times/","weight":"http://babybuddy/api/weight/","height":"http://babybuddy/api/height/","head-circumference":"http://babybuddy/api/head-circumference/","bmi":"http://babybuddy/api/bmi/"}
2022-04-23 08:29:29 DEBUG (MainThread) [custom_components.babybuddy.client] Endpoints: {'children': 'http://babybuddy/api/children/', 'changes': 'http://babybuddy/api/changes/', 'feedings': 'http://babybuddy/api/feedings/', 'notes': 'http://babybuddy/api/notes/', 'sleep': 'http://babybuddy/api/sleep/', 'temperature': 'http://babybuddy/api/temperature/', 'timers': 'http://babybuddy/api/timers/', 'tummy-times': 'http://babybuddy/api/tummy-times/', 'weight': 'http://babybuddy/api/weight/', 'height': 'http://babybuddy/api/height/', 'head-circumference': 'http://babybuddy/api/head-circumference/', 'bmi': 'http://babybuddy/api/bmi/'}

I'm also confused - I'm not sure how the reverse proxy comes into it as the reverse proxy doesn't have anything to do with the link between HA BB integration and the BB server (all my internal things talk via local IP, nothing goes out of the network)
I could test by stopping my NGINX container, but I'm not sure that would do anything

My understanding is DRF extends Django HttpRequest(). Django first checks "HTTP_X_FORWARDED_HOST (if USE_X_FORWARDED_HOST is enabled) and HTTP_HOST headers, in that order. If they don’t provide a value, the method uses a combination of SERVER_NAME and SERVER_PORT."
I am happy to continue helping you fix your problem, but cannot help much more if you are cannot test your reverse proxy settings.

I will have a dig around and see what I can do. I'm not too sure what I need to modify through NGINX proxy manager,  but I'll do some googling and see how I go. I do appreciate your efforts. I'm not as much as a wiz as I once was unfortunately

I stopped my nginx proxy and set up BB HA integration with the internal IP and port of BB installation and set up reports it was successful but no sensors are available and the error message stays the same:
Error fetching babybuddy data: Cannot connect to host <IP_ADDRESS>:80 ssl:default [Connect call failed ('<IP_ADDRESS>', 80)]
So i think we can agree that nginx configuration does not affect this error.
Maybe @kazzaw  can confirm this at some time.

The HA integration is configured to call port 8000. It's actually calling port 80. That's a bug in this package.
The fact that messing with Django/BB config "fixes" it is likely only because it opens port 80.
As others have said, reverse proxy has nothing to do with it since this is a call between two Docker containers on the same machine.

Your own debug logs show the host:port correctly until it hits /api/ endpoints, which is on the BB/Django side of things:

Those logs are entirely from the HA integration. The HA integration is calling port 80 instead of 8000. Unless you're saying that those logs are somehow introspected from BB itself.

I agree but i have to add as well that the bug is probably on BB/Django side:

Looks like the port is missing in the API endpoint list response JSON as i pointed out here: https://github.com/babybuddy/babybuddy/issues/446

Thanks for a more thorough explanation. It was not obvious that the HA integration actually reads the endpoints, including port, from BB. So that could be a BB bug.

I'm guessing your docker-compose.yaml looks similar to this?
services:
 app:
  environment:
   - CSRF_TRUSTED_ORIGINS=http://localhost:8000
   - DJANGO_SETTINGS_MODULE=babybuddy.settings.base
  image: ghcr.io/linuxserver/babybuddy
  ports:
   - '8000:8000'

If so, I'm able to reproduce the issue:
http://localhost:8000/api/ returns: {"children":"http://localhost/api/children/","changes":"http://localhost/api/changes/","feedings":"http://localhost/api/feedings/","notes":"http://localhost/api/notes/","sleep":"http://localhost/api/sleep/","temperature":"http://localhost/api/temperature/","timers":"http://localhost/api/timers/","tummy-times":"http://localhost/api/tummy-times/","weight":"http://localhost/api/weight/","height":"http://localhost/api/height/","head-circumference":"http://localhost/api/head-circumference/","bmi":"http://localhost/api/bmi/"}.
I think the problem may be here:
https://github.com/linuxserver/docker-babybuddy/blob/21b1afc9405d70aba0630054fdd07e0a6ff22a0e/root/defaults/default#L12
When I change the LSIO nginx.conf from proxy_set_header Host $host; to proxy_set_header Host $http_host;, all works as expected:
{"children":"http://localhost:8000/api/children/","changes":"http://localhost:8000/api/changes/","feedings":"http://localhost:8000/api/feedings/","notes":"http://localhost:8000/api/notes/","sleep":"http://localhost:8000/api/sleep/","temperature":"http://localhost:8000/api/temperature/","timers":"http://localhost:8000/api/timers/","tummy-times":"http://localhost:8000/api/tummy-times/","weight":"http://localhost:8000/api/weight/","height":"http://localhost:8000/api/height/","head-circumference":"http://localhost:8000/api/head-circumference/","bmi":"http://localhost:8000/api/bmi/"}
I am going to open a PR with LSIO and see what they think.
Thanks all.

@jcgoette great catch! I haven't even thought about the Lsio docker image having a nginx proxy as well...
Let's hope on a quick merge! Thanks for your help!

@jcgoette i tried out the potential fix from https://github.com/linuxserver/docker-babybuddy/pull/19 but sadly it does not fix the problem on my side.

I also had the same error when trying to call a service through the internal docker network, which previously worked:
Cannot connect to host babybuddy:80 ssl:default [Connect call failed ('<IP_ADDRESS>', 80)]
After modifying my docker compose to the following, service calls began working as expected.
  ports:
   - '8000:8000'
   - '80:80'

Closed by https://github.com/linuxserver/docker-babybuddy/pull/19.

I still have this issue with the most recent update from lsio. Anyone else?

Yeah this is still broken in Baby Buddy v1.10.2-ls33

ls33 is from 4/17. This fix looks like it was put on https://github.com/linuxserver/docker-babybuddy/releases/tag/v1.10.2-ls36.

Sorry, still a problem with v1.10.2-ls37 as well (have I mentioned how much I hate Docker versioning and "tags"? 😄)
I tried explicitly exposing port 8000 on the babybuddy container to no effect. I cannot expose port 80 (already in use), nor would I want to.

I am running 1.10.2-ls36 just FYI

I mistakenly thought the PR would fix this automatically. You will still need to take some action. See links below:

https://github.com/linuxserver/docker-babybuddy/pull/19#issuecomment-1127118226
https://github.com/linuxserver/docker-babybuddy/pull/19#issuecomment-1127122750

Manually changing the mounted file /config/nginx/site-confs/default and restarting the container fixes the problem! thanks everyone!

Can you confirm what you changed? Appreciated

I mounted /config as a volume of the container and the change from this commit: https://github.com/linuxserver/docker-babybuddy/pull/19/files in the file /config/nginx/site-confs/default.


Color Guessing Game Using JavaScript DOM

Is your feature request related to a problem? Please describe.
No its not a problem.
Describe the solution you'd like
I am suggesting to add a RGB color game using DOM.
In this game there are 6 blocks of random color and at the top there is a random RGB text indicating a color. The player have to guess which block corresponds to the color enclosed by the RGB at the top. The player can guess the right block by clicking on it.  Each time the player clicks on "play again" button the whole page would get refreshed, with new RGB color at top and new color of all the 6 blocks.

Additional context
This interactive game project  can enhance the DOM understanding of anyone who is a beginner in JavaScript.
I am also attaching the git hub link of my proposed project. ==>> https://github.com/prayas7102/Color-Guessing-Game-Using-Js-DOM

sorry @prayas7102 , but this project already exists in the repo , you can either improve that or add any other awesome js project :)

Ok sir, I've created other issue #1690. Please have a look at it and let me
know if I can work on it.
On Wed, 19 May, 2021, 6:40 PM Riddhi Suteri, @.***>
wrote:

sorry @prayas7102 https://github.com/prayas7102 , but this project
already exists in the repo , you can either improve that or add any other
awesome js project :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Vishal-raj-1/Awesome-JavaScript-Projects/issues/1491#issuecomment-844091602,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARDFEOP2WX2NLDW7BJUTYCLTOO2FBANCNFSM45CKQGOA
.


Tools: Add flag --selector.relabel-config-file / --selector.relabel-config / --max-time / --min-time to filter served blocks.

fix #4452
Signed-off-by: hanjm<EMAIL_ADDRESS>

[x] I added CHANGELOG entry for this change.
[ ] Change is not relevant to the end user.

Changes

add min-time max-time selector.relabel-config flag to thanos tools bucket web.

Verification

e2e test.
run with new flag, it works.

I have add e2e test, @yeya24 could you help me review again? thank you.


v-model in input and textarea forms doen't work correctly on several mobile devices

Version
3.2.31
Reproduction link
github.com
Steps to reproduce
Problem
v-model on textarea and input forms doesn't work properly on some mobile devices. When user type something, value sync only after unfocus (blur)
Code

  <textarea v-model="text"></textarea>

{{ text }}

Works on most mobile devices and browsers, i.e Meizu C9 PRO (android 8.1.0 Chrome 99.0.4844.58)

But doen't work correctly on several mobile devices, i.e. Samsung Galaxy A50 (Android 11 Chrome 99.0.4844.58)

Our technical support kept information from clients about devices where problems also occurred:

Samsung s10e (internal browser)
Xiaomi Mi6 (internal browser)
Apple Iphone XS (Safari v12.10.5-go)

But via "@input" it work's fine

    <textarea @input="typing" type="text"></textarea>

{{ text }}

Samsung Galaxy A50

Versions
Vue 3
What is expected?
The same code works equally on any modern mobile devices, i.e. data from input sync when user typing (with v-model)
What is actually happening?
The same code doesn't work equally on some modern mobile devices, i.e. data from input sync only when blur input

Problem with our app on production

This is caused by IME composition as stated in the documentation here : https://vuejs.org/guide/essentials/forms.html#text (see Note about IME).
A workaround is to listen for @input event and manually update your ref.

@paraboul thanks for explanation and reference!

Closing this as v-model is working as expected here.

I know it's not an issue with Vue, but might be worth adding things like the type of keyboard you use causing these types of problems (e.g. gboard), not just the language being typed, to that note in the docs. Just ran into this too, and when I originally read over the comment in the docs, it mislead me to think it wasn't related, as I wasn't using a language that is designated as IME.


Handle disconnect

Hello,
I cheked in on irc yesterday with a bug and wanted to follow through here.
Sometimes, The Lounge loses the connexion to the irc server / internet, but when that happens, nothing is reported to the user. Everything seems normal except you don't receive any more messages and can't send any either.
I'm still a bit confused about when this happens and can't reproduce it reliably, but apparently it's something inherited from shout (see here and here for example).
Are there any plans to address this?

Duplicate of #18

Aw sorry, I searched the issues for "disconnect" so didn't find it^^


Disable Python in Renovate

It helps to reduce the Renovate PRs.
As the idea is to convert the Python package to Node.js:

https://github.com/Qiskit/platypus/issues/321

thanks


The processor instance ... owns a higher than recommended number of partitions for average workloads

Hi,
With the latest SDK we started getting the below error:
Azure.Messaging.EventHubs[104] The processor instance with identifier '696b32d5-0a4c-4a9f-b79e-7aabe9456f8a' for Event Hub: xxx-xxxxxxx-xxxx-xxxxxx-xxxxx owns a higher than recommended number of partitions for average workloads. Owning too many partitions can cause slow performance and stability issues. Consider monitoring performance and partition ownership stability to ensure that they meet expectations. If not, adding processors to the group may help. Total partition count: '4'. Owned partition count: '4'. Maximum recommended partitions owned: '3'.
I cannot see any documentation regarding it, especially for the part "Consider monitoring performance and partition ownership stability to ensure that they meet expectations" - what exactly is unstable/slow in case too many partitions are handled by 1 EventProcessorClient?
Additionally, why is there no way to suppress this? Standard Event Hubs do not allow changing the partition count after creation, so we are somehow punished all of a sudden for something we cannot even fix, or?
Br,
Deyan

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

ID: 27b148ea-a4e1-f9c1-0345-2b090be9db1b
Version Independent ID: c149af73-514a-39b8-3fdf-9a59bb9def2f
Content: Balance partition load across multiple instances - Azure Event Hubs - Azure Event Hubs
Content Source: articles/event-hubs/event-processor-balance-partition-load.md
Service: event-hubs
GitHub Login: @spelluru
Microsoft Alias: spelluru

@deyanp Thanks for your feedback. We will review and update as appropriate.

@deyanp - Opened an issue in the SDK repo. Here's the link:
https://github.com/Azure/azure-sdk-for-net/issues/31555

Please see the response in the linked SDK repo issue. Thanks.
#please-close


Images not being detected

Hey,
Thanks very much for the package!
I noticed the other day that CraigslistForSale results weren't being correctly populated with images.
I ran through the code with a debugger.
It looks like everything is OK until this line:
if 'src' not in img:  # Some posts contain empty <img> tags.
It seems to always evaluate to True.
This is the type of img:
<class 'bs4.element.Tag'>

I wonder if something recently changed in Beautiful Soup?
This seems to fix the problem for me:
if 'src' not in str(img):

Or maybe this is better?
if 'src' not in img.attrs.keys():

Versions:
Python 3.8.2 on Linux
beautifulsoup4==4.9.1
python-craigslist==1.0.8

Thanks so much @weebsnore for reporting this! Seems to be that the package has been having an issue with images for some time. I've fixed it and already released version 1.0.10 with the fix.
Thanks again!


Which parameter controls GPU memory consumption?

Hello,I am using PyOpenpose with below settings:
       self.poseSize = (656, 368)
        self.faceHandSize = (240, 240)
        self.outSize = (640, 480)
        self.modelType = "COCO"
        self.logLevel = 0
        self.downloadHeatmaps = False
        self.detectFace = False
        self.detectHands = False

Same python scripts+same settings as above,
under my laptop with a nvidia 1070 card,python wrapped openpose process consumed
1516MB GPU memory,
but under a server with nvidia 1080Ti card,openpose process consumed
7883MB GPU memory,
where does this big memory consumption comef from?Any parameter to specify GPU memory consumption?
(I have asked in openpose issue list:https://github.com/CMU-Perceptual-Computing-Lab/openpose/issues/526,but openpose guys said it isn't their problem)

This is not a PyOpenPose related issue. That said, try changing (reducing) the input resolution when initializing the PyOpenPose class and see how the memory consumption changes.

On that note, is there a parameter which determines which GPUId is utilized?
Thanks!


srs.sh: 文件里的命令没写适配？只能用Mac系统么

项目怎么跑应该描述一下呀；在哪里配置等等。你那配置文件都把MySQL数据库和redis数据库的默认端口都改了。我改后报错：
SUCCESS  加载所有route成功~
INFO  当前不是beta环境，初始化websocket
SUCCESS  项目启动成功！
WARN  当前监听的端口: 4300
WARN  当前的项目名称: billd-live-server
WARN  当前的项目环境: development
INFO  2023/5/3 22:03:17，子进程退出了，sh E:\test\billd-live-server\srs.sh
INFO  2023/5/3 22:03:17，有打印
Error: Command failed: sh E:\test\billd-live-server\srs.sh
E:\test\billd-live-server\srs.sh: line 16: ifconfig: command not found
error during connect: This error may indicate that the docker daemon is not running.: Post "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/containers/billd-live-server-srs/stop": open //./pipe/docker_engine: The system cannot find the file specified.
error during connect: This error may indicate that the docker daemon is not running.: Delete "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/containers/billd-live-server-srs": open //./pipe/docker_engine: The system cannot find the file specified.
docker: error during connect: This error may indicate that the docker daemon is not running.: Post "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/containers/create": open //./pipe/docker_engine: The system cannot find the file specified.
See 'docker run --help'.

   at ChildProcess.exithandler (node:child_process:419:12)
   at ChildProcess.emit (node:events:513:28)
   at ChildProcess.emit (node:domain:489:12)
   at maybeClose (node:internal/child_process:1091:16)
   at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5) {
 code: 127,
 killed: false,
 signal: null,
 cmd: 'sh E:\\test\\billd-live-server\\srs.sh'
} 停掉旧的容器billd-live-server-srs:
删掉旧的容器billd-live-server-srs:
启动新的容器billd-live-server-srs:

你微信多少，我加你
发自我的iPhone
------------------ 原始邮件 ------------------
发件人: 董路飞 @.>
发送时间: 2023年5月3日 22:10
收件人: galaxy-s10/billd-live-server @.>
抄送: Subscribed @.***>
主题: Re: [galaxy-s10/billd-live-server] srs.sh: 文件里的命令没写适配？只能用Mac系统么 (Issue #1)
项目怎么跑应该描述一下呀；在哪里配置等等。你那配置文件都把MySQL数据库和redis数据库的默认端口都改了。我改后报错：
SUCCESS  加载所有route成功~ INFO  当前不是beta环境，初始化websocket SUCCESS  项目启动成功！ WARN  当前监听的端口: 4300 WARN  当前的项目名称: billd-live-server WARN  当前的项目环境: development INFO  2023/5/3 22:03:17，子进程退出了，sh E:\test\billd-live-server\srs.sh INFO  2023/5/3 22:03:17，有打印 Error: Command failed: sh E:\test\billd-live-server\srs.sh E:\test\billd-live-server\srs.sh: line 16: ifconfig: command not found error during connect: This error may indicate that the docker daemon is not running.: Post "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/containers/billd-live-server-srs/stop": open //./pipe/docker_engine: The system cannot find the file specified. error during connect: This error may indicate that the docker daemon is not running.: Delete "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/containers/billd-live-server-srs": open //./pipe/docker_engine: The system cannot find the file specified. docker: error during connect: This error may indicate that the docker daemon is not running.: Post "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/containers/create": open //./pipe/docker_engine: The system cannot find the file specified. See 'docker run --help'.    at ChildProcess.exithandler (node:child_process:419:12)    at ChildProcess.emit (node:events:513:28)    at ChildProcess.emit (node:domain:489:12)    at maybeClose (node:internal/child_process:1091:16)    at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5) {  code: 127,  killed: false,  signal: null,  cmd: 'sh E:\test\billd-live-server\srs.sh' } 停掉旧的容器billd-live-server-srs: 删掉旧的容器billd-live-server-srs: 启动新的容器billd-live-server-srs:
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

项目怎么跑应该描述一下呀；在哪里配置等等。你那配置文件都把MySQL数据库和redis数据库的默认端口都改了。我改后报错：
SUCCESS  加载所有route成功~
INFO  当前不是beta环境，初始化websocket
SUCCESS  项目启动成功！
WARN  当前监听的端口: 4300
WARN  当前的项目名称: billd-live-server
WARN  当前的项目环境: development
INFO  2023/5/3 22:03:17，子进程退出了，sh E:\test\billd-live-server\srs.sh
INFO  2023/5/3 22:03:17，有打印
Error: Command failed: sh E:\test\billd-live-server\srs.sh
E:\test\billd-live-server\srs.sh: line 16: ifconfig: command not found
error during connect: This error may indicate that the docker daemon is not running.: Post "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/containers/billd-live-server-srs/stop": open //./pipe/docker_engine: The system cannot find the file specified.
error during connect: This error may indicate that the docker daemon is not running.: Delete "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/containers/billd-live-server-srs": open //./pipe/docker_engine: The system cannot find the file specified.
docker: error during connect: This error may indicate that the docker daemon is not running.: Post "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/containers/create": open //./pipe/docker_engine: The system cannot find the file specified.
See 'docker run --help'.

   at ChildProcess.exithandler (node:child_process:419:12)
   at ChildProcess.emit (node:events:513:28)
   at ChildProcess.emit (node:domain:489:12)
   at maybeClose (node:internal/child_process:1091:16)
   at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5) {
 code: 127,
 killed: false,
 signal: null,
 cmd: 'sh E:\\test\\billd-live-server\\srs.sh'
} 停掉旧的容器billd-live-server-srs:
删掉旧的容器billd-live-server-srs:
启动新的容器billd-live-server-srs:

更新readme了，看看

CANDIDATE=$(ifconfig en0 inet | grep 'inet ' | awk '{print $2}')
你这命令全球用户量最大的操作系统 windows 跑不了，windows 没有 ifconfig 命令 有ipconfig。windows 也可以跑docker和podman

CANDIDATE=$(ifconfig en0 inet | grep 'inet ' | awk '{print $2}') 你这命令全球用户量最大的操作系统 windows 跑不了，windows 没有 ifconfig 命令 有ipconfig。windows 也可以跑docker和podman

苹果测试window需要模拟器，比较麻烦，后续再兼容，当然你也可以提pr~


Log: Allow override context within logging calls

Extracted from https://forum.crystal-lang.org/t/proposal-to-have-all-data-be-key-value-data-in-log/1966/14
Let's add a spec to ensure that will keep working + allow the restoring of the previous context.
cc: @paulcsmith

Not sure if this was discussed somewhere, but could we yield the context? That would make it more explicit at callsite that mutating methods affect the local context only.

@straight-shoota the context is immutable, so we would need to yield some other structure.
Yielding the whole Log::Entry could be an option, but then we need to allow entries to be mutable also, and initialize them without message.
All the options I can think of that depart from these facts yeilds to more API to learn that will have their own quirks IMO.

Ah, okay. And Log.conetxt.set() works because it's not assigned to a local variable.


⚠ Bofrost.at has degraded performance

In 5b0be72, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1871 ms

Resolved: Bofrost.at performance has improved in 28f6ce1 after 7 minutes.


Remove outdated js snippet caveat on imports

I'm not sure if import statements are universally implemented now but myself and others seem to be having success using them in snippets.

I honestly don't know anything about this limitation.
Going through git blame didn't help either.
@Liamolucko do you know something about the historical context here? Testing it out locally seems to work fine for me.

@Liamolucko do you know something about the historical context here? Testing it out locally seems to work fine for me.

No, but I found the original RFC for snippets and there's a note about it there. It looks like what the caveat's supposed to mean is that imports don't work relative to the original path of the snippet like you'd expect, but there's nothing stopping you from writing them anyway and having them be resolved relative to the final path of the snippet. The fact that that works seems to be an unintended side effect of not processing the JS at all.

Thank you!
@crajcan at best I would update the documentation then instead of removing it.


Plants can go through doors with a gravity anomaly

Bug is either:
A) Plants can always go through doors, or
B) Gravity objects being pulled need to be marked as awake.
I don't think plants have CollisionWake.

I tried dragging a plant through the door, it just passes through.


ryujinx: disable tests due to flakiness

Description of changes
Deadlocking appears to happen when under load, so disable the tests entirely.
"fixes" #325857
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

ryujinx

Things done

Built on platform(s)

[x] 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

[x] 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

[x] Fits CONTRIBUTING.md.

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

I think I found the upstream bug: https://github.com/Ryujinx/Ryujinx/pull/7239


simple README for boa3_test/examples

It would be nice if you could add a simple README.md file in the boa3_test/examples directory, briefly explaining the purpose of each smart contract example, and how to build/test them.

Add details on how to build/test each smart contract example to the new README that was implemented by #387 for boa3_test/examples.


start using zorm

WIP

Obv needs some styling, but using a native form and controls with react-zorm now:
https://user-images.githubusercontent.com/51714798/205340858-67f1dd3a-1a5f-4bca-bf1b-69ad03bab391.mp4

Might be blocked here: https://github.com/esamattis/react-zorm/issues/29#issuecomment-1336407882
Their repro didn't work either


How long does it take for a staff member to reviews the posts in https://community.sanicframework.org/

I created an account in https://community.sanicframework.org/ and asked a question. To be precise - https://stackoverflow.com/questions/58329770/use-sanics-inbuilt-webserver-in-production
The forum is saying since last 18 hours -

Please do continue to browse, but you won’t be able to reply or create topics until a staff member reviews your most recent posts. We apologize for the inconvenience.

How long does it take for a staff member to reviews the posts?
Can someone please answer my stackoverflow question.

~1.5 Days passed. Not Approved. It seems very hard to get started with this community.

I'm not sure what you're asking and the stack overflow question is unclear. The reddit post is old and from a time where the project was essentially on hiatus and in transition to a new team. Some issues have been addressed; new issues have been found. It's up to you to decide whether Sanic fits what you're doing.

My question was regarding https://community.sanicframework.org/
I created an account and asked a question. It says -

Please do continue to browse, but you won’t be able to reply or create topics until a staff member reviews your most recent posts. We apologize for the inconvenience.

How long does it take for a staff member to reviews the posts?

I do not see any posts there; your account must be trapped by the spam filter and @ahopkins will have to release it. He's on a minor hiatus at the moment. If you did not log in with your github account, that may be why there is a problem. If you did log in with your github account, it will have to wait.


minor typo in readme?

the readme file reads:
From source
Get latest version using Git
$ git clone https://github.com/ig-python/ig-markets-api-python-library
$ cd ig-markets-api-python-library
$ python setup.py install https://github.com/ig-python/ig-markets-api-python-library
or
$ pip install git+https://github.com/ig-python/ig-markets-api-python-library

the command python setup.py install https://github.com/ig-python/ig-markets-api-python-library should be python setup.py install right? because otherwise I get error invalid command name 'https://github.com/ig-python/ig-markets-api-python-library'

Thanks @wangjian2020 for reporting.
Fixed


Readme: missing bp

It is in the utility buildpack section lower.

@ForestEckhardt Ahh I didn't see it. Thanks


[Grid] [next] Grid blips before column classes are assigned

Branch: next

Describe in detail the issue you're having.

Grid columns are first rendered without classes and then after a moment classes are added.
This causes a blip a layout shift because of setTimeout used here:
https://github.com/carbon-design-system/carbon-components-angular/blob/next/src/grid/grid.directive.ts#L73
Is it possible to set classes without the setTimeout?
I'm aware it is currently used because GridDirective is modifying isCss property on column.
Maybe the method updateColumnClasses() can be made public and
after setting isCss property by GridDirective method updateColumnClasses() can be called explicitly?
With this approach setTimeout can be removed and isCss real value will be available within the method.
if (this.columnChildren) {
    this.columnChildren.forEach(column => {
        column.isCss = true;
        column.updateColumnClasses();
    });
}

Is this issue related to a specific component?

Grid.

What version of the Carbon Design System are you using?

"carbon-components": "^11.25.0",
"carbon-components-angular": "^5.7.0",

Steps to reproduce the issue

It can be observed in storybook when switching between Basic and Css Grid.
Thank you

I just noticed a PR #2497 regarding this issue is already opened. I'm closing the issue.


Cannot download by any version blender

It failed
Exception in thread Thread-45 (check_for_new_assets):
Traceback (most recent call last):
  File "G:\blender\36\3.6\python\lib\threading.py", line 1016, in _bootstrap_inner
    self.run()
  File "G:\blender\36\3.6\python\lib\threading.py", line 953, in run
    self._target(*self._args, **self._kwargs)
  File "G:\blenderplus\3.0\addons\Baked_Blender_Suite\operators\library_download.py", line 365, in check_for_new_assets
    assets = get_asset_list().items()
  File "G:\blenderplus\3.0\addons\Baked_Blender_Suite\operators\library_download.py", line 61, in get_asset_list
    result = request.execute()
  File "G:\blenderplus\3.0\addons\Baked_Blender_Suite\dependencies/windows\googleapiclient\_helpers.py", line 130, in positional_wrapper
    return wrapped(*args, **kwargs)
  File "G:\blenderplus\3.0\addons\Baked_Blender_Suite\dependencies/windows\googleapiclient\http.py", line 923, in execute
    resp, content = _retry_request(
  File "G:\blenderplus\3.0\addons\Baked_Blender_Suite\dependencies/windows\googleapiclient\http.py", line 222, in _retry_request
    raise exception
  File "G:\blenderplus\3.0\addons\Baked_Blender_Suite\dependencies/windows\googleapiclient\http.py", line 191, in _retry_request
    resp, content = http.request(uri, method, *args, **kwargs)
  File "G:\blenderplus\3.0\addons\Baked_Blender_Suite\dependencies/windows\oauth2client\transport.py", line 159, in new_request
    credentials._refresh(orig_request_method)
  File "G:\blenderplus\3.0\addons\Baked_Blender_Suite\dependencies/windows\oauth2client\client.py", line 749, in _refresh
    self._do_refresh_request(http)
  File "G:\blenderplus\3.0\addons\Baked_Blender_Suite\dependencies/windows\oauth2client\client.py", line 778, in _do_refresh_request
    resp, content = transport.request(
  File "G:\blenderplus\3.0\addons\Baked_Blender_Suite\dependencies/windows\oauth2client\transport.py", line 280, in request
    return http_callable(uri, method=method, body=body, headers=headers,
  File "G:\blenderplus\3.0\addons\Baked_Blender_Suite\dependencies/windows\httplib2\__init__.py", line 1724, in request
    (response, content) = self._request(
  File "G:\blenderplus\3.0\addons\Baked_Blender_Suite\dependencies/windows\httplib2\__init__.py", line 1444, in _request
    (response, content) = self._conn_request(conn, request_uri, method, body, headers)
  File "G:\blenderplus\3.0\addons\Baked_Blender_Suite\dependencies/windows\httplib2\__init__.py", line 1366, in _conn_request
    conn.connect()
  File "G:\blenderplus\3.0\addons\Baked_Blender_Suite\dependencies/windows\httplib2\__init__.py", line 1156, in connect
    sock.connect((self.host, self.port))
TimeoutError: [WinError 10060]

Could you Update asset files on github or gumroad individually？（Like update it every 3 day）
Help the user who can‘t download it as normal as me.

What version of blender are you using. minimum requirment is 3.5
3.6 has noot been tested yet. The above error shows two version? 3.6 and 3.0

What version of blender are you using. minimum requirment is 3.5 3.6 has noot been tested yet. The above error shows two version? 3.6 and 3.0

3.5 and 3.6

TimeoutError: [WinError 10060] is a connection issue between your pc and the server. It takes to long to respond to the request.  So the request gets timed out.
Do you have a vpn running or something similar? It can also be a  firewall issue.

It might be easier to join our discord and see if we can find a solution. https://discord.gg/bakeduniverse


Updatewd nc_template.ipynb to use paths defined in marisco.configs

Accepted your suggestion to not hardcode the "_" separator here but rather defined it in configs.
Not we have to keep casting "massnb" as int.
Let's discuss the purpose of './files/cdl.toml'. They are generated directly from configs.ipynb and used for testing purpose. The ones under ./marisco are only created upon install via maris_init. But again let's discuss it.


Add support to Temporal tables

There are some issues with temporal tables at the moment

Added in version 1.7.1