Support None as input in forward and hybrid_forward?

Description
(Hybrid) forward supports None as defaults, but not as inputs. I was wondering if there are any fundamental reasons why None cannot be taken as input - if the pattern is consistent and I do not change the computation graph? Similarly, None in the output should also be allowed.
Environment info (Required)
----------Python Info----------
Version      : 3.6.5
Compiler     : GCC 7.2.0
Build        : ('default', 'Apr 29 2018 16:14:56')
Arch         : ('64bit', '')
------------Pip Info-----------
Version      : 10.0.1
Directory    : /home/ec2-user/anaconda3/envs/mxnet_p36/lib/python3.6/site-packages/pip
----------MXNet Info-----------
Version      : 1.3.0
Directory    : /home/ec2-user/anaconda3/envs/mxnet_p36/lib/python3.6/site-packages/mxnet
Commit Hash   : b3be92f4a48bce62a5a8424271871c2f81c8f7f1
----------System Info----------
Platform     : Linux-4.14.77-69.57.amzn1.x86_64-x86_64-with-glibc2.9
system       : Linux
node         : ip-172-16-72-155
release      : 4.14.77-69.57.amzn1.x86_64
version      : #1 SMP Tue Nov 6 21:32:55 UTC 2018
----------Hardware Info----------
machine      : x86_64
processor    : x86_64
----------Network Test----------
Setting timeout: 10
Timing for MXNet: https://github.com/apache/incubator-mxnet, DNS: 0.0016 sec, LOAD: 0.4079 sec.
Timing for Gluon Tutorial(en): http://gluon.mxnet.io, DNS: 0.1175 sec, LOAD: 0.1057 sec.
Timing for Gluon Tutorial(cn): https://zh.gluon.ai, DNS: 0.2767 sec, LOAD: 0.1359 sec.
Timing for FashionMNIST: https://apache-mxnet.s3-accelerate.dualstack.amazonaws.com/gluon/dataset/fashion-mnist/train-labels-idx1-ubyte.gz, DNS: 0.0274 sec, LOAD: 0.1023 sec.
Timing for PYPI: https://pypi.python.org/pypi/pip, DNS: 0.0023 sec, LOAD: 0.3404 sec.
Timing for Conda: https://repo.continuum.io/pkgs/free/, DNS: 0.0081 sec, LOAD: 0.3184 sec.

Package used (Python/R/Scala/Julia):
Python
Error Message:
AssertionError: HybridBlock input must be (nested) list of Symbol or NDArray, but got None of type <class 'NoneType'>
AssertionError: HybridBlock output must be (nested) list of Symbol or NDArray, but got None of type <class 'NoneType'>

Minimum reproducible example
import mxnet as mx
rnn = mx.gluon.rnn.GRU(10)
rnn.hybridize()
rnn.collect_params().initialize()
rnn(mx.nd.zeros((3,2,10)), ) # this is okay
rnn(mx.nd.zeros((3,2,10)), None) # this is not okay

Steps to reproduce

The example is self-contained.

What have you tried to solve it?

Manually construct an *args list, which seems error-prone.

@mxnet-label-bot add [Feature Request, Python, Gluon]

@zachgk Thanks! I should also mention that None output type should also be similarly allowed for completeness. Will edit the original feature request.

Thank you for the suggestion @yifeim. We welcome contributions, so feel free to try making these changes yourself if you want to get involved

Thanks for the offers, but I don’t think I need to fix it in a hurry, because I have my workaround. Mxnet for me still seems to have large amount of obvious hacks or bugs, understandably. Nonetheless, I like the better side of mxnet.
I appreciate that you feel this is an sensible suggestion and an obvious thing to do. Will revisit later.

@yifeim Should be solved by https://github.com/apache/incubator-mxnet/pull/16280

@yifeim Currently, only supports None as the input.


Allow restclient to specify if keepalives should be used

Allow restclient to support disabling of HTTP keep-alives. Just offers another constructor NewDisableKeepAlives() to accomplish this so the default behavior has not changed.
When keepalives are disabled, we also set req.Close = true to close the connection once it has been sent.
@krobertson @wallyqs @shobhit85

LGTM


feat(rbac): integrate RBAC plugin

Description
Please explain the changes you made here.
Which issue(s) does this PR fix

Fixes #?

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

[ ] GitHub Actions are completed and successful
[ ] Unit Tests are updated and passing
[ ] E2E Tests are updated and passing
[ ] Documentation is updated if necessary (requirement for new features)
[ ] Add a screenshot if the change is UX/UI related

How to test changes / Special notes to the reviewer

Looks like I am getting an error whenever I run this. Backend failed to start up Error: ENOENT: no such file or directory, open<EMAIL_ADDRESS>I believe it is because of models being under the keywords section here. I have issued a PR to get it fixed.
Other then that, I was able to get it to work after I added the folder to the node_modules.


Add "to be announced" item in the pull request checklist

This is based on the discussion with @marco-c on Matrix.
If the PR is worth announcing, we will add the TBA tag (To Be Announced) tag. Once we announce the change (i.e., sent to dev-platform/firefox-dev mailing lists and add to EE newsletter), we must replace TBA with announced.
Checklist

[ ] Type annotations added to new functions
[ ] Docs added to functions touched in main classes
[ ] Dry-run produced the expected results

Nit: we could be more explicit and call the tag "to-be-announced" :)

Nit: we could be more explicit and call the tag "to-be-announced" :)

I agree; done in aa86566f6e36ca5495ef700fe8f73a00d2397841.


PMID:15302827

abnormal RNA level oscillation during mitotic cell cycle

abnormal RNA level oscillation during mitotic cell cycle FYPO:0004988

edit file: 6adc5c7b7a97cd970a52f947b6202ff47111b8f7
release: 9615de7a68bece38aa177aaedef1da62debe40c9


Cobertura is not working for a simple ant project.

seems fine

accept or close

This fix is already checked in.


Documentation needs to by updated

Documentation needs to be updated, Microsoft.Configuration.ConfigurationBuilders.Azure.1.0.0-alpha1.nupkg no longer exists as a nuget package. It seems the nuget packages for configuration builder have been divided into Base, Azure, Enivronment, Json, and UserSecrets.

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

ID: ba5deb43-08e3-09fe-1696-29f49764580b
Version Independent ID: 0c910667-1d39-47dd-c70b-ab40999ea160
Content: Securely saving secret application settings for a web application
Content Source: articles/key-vault/vs-secure-secret-appsettings.md
Service: unspecified
GitHub Login: @cawa
Microsoft Alias: cawa

@jimmykurian Thanks for the feedback. We are actively investigating and will get back to you soon.

Microsoft.Configuration.ConfigurationBuilders.Basic? i guess it means Microsoft.Configuration.ConfigurationBuilders.Base right?

The page provides an example for a .Core app. How about pre.Core?


Pigar, while awesome, misses some packages?

Hello. Firstly, this module is a godsend. Thank you.
I ran pigar in my repository and all but one package was correctly identified. The missing package, python-box (import box), was necessary to load the module. And I know that module is no dependency of any of the packages pigar identified for requirements.txt.
I ran pigar -u to update the package list. Though it did not change the pigar output (or at least add python-box).
What to do?
Thanks again!

The latest version should fix it.


fix logging example

I didn't run pre-commit since this is a very small doc update

Thank you! @all-contributors please add @LonelyVikingMichael for docs


folder_path and model_prefix functionality for generate_model_yaml

Describe the feature
I want to introduce folder_path and model_prefix functionality for generate_model_yaml macro.
I already have working code here: https://github.com/dbt-labs/dbt-codegen/compare/main...erkanncelen:dbt-codegen:main
This way the macro can be used as:

{{ generate_model_yaml(model_prefix='fct_') }} --> all models starting with fct_
{{ generate_model_yaml(folder_path='marts/marketing') }} --> all models in marts/marketing folder
{{ generate_model_yaml(folder_path='marts/marketing', model_prefix='fct_') }} --> all models in marts/marketing folder starting with fct_

**Please let me know if you think this'd be a nice addition to the codegen so that I can finalise and submit my PR! **
Describe alternatives you've considered
The alternative to this approach would be providing manually made lists to the macro, which is already possible. It is however time consuming and repetitive. I believe this approach will make dbt folks' lives easier.
Additional context
This feature is not database specific, at least not in my initial design. I basically utilise manifest.json information, to retrieve all models in a project, with model names and folder paths.
Who will this benefit?
These features will be extremely beneficial when we start documenting our dbt projects. Combining the two, we will be able to generate YAMLs for any group of models we desire. I personally used my approach at two of my clients already.
Are you interested in contributing this feature?
Yes I am!
I actually have the PR almost ready, just missing the tests, waiting for the first approval.
You can see my code here: https://github.com/dbt-labs/dbt-codegen/compare/main...erkanncelen:dbt-codegen:main

Hi @joellabes , do you think this'd be a nice addition to the codegen? If so, I want to polish it up and finish the PR

Oooooh this is a really good idea! Sorry for the delay in getting back to you.
Instead of overloading the generate_model_yaml macro, what about a new macro called something like get_models_by_prefix_in_directory(prefix, directory) which returns an array of model names that can be passed directly into the existing unchanged macro?

Hi @joellabes , thanks for your input. Your suggestion really makes sense.
I created a macro named get_models in macros/helpers directory. It takes directory and prefix arguments. Based on these arguments, it returns an array of matching model_names retrieved from the graph object.
Here I completed the PR with all requirements checked: https://github.com/dbt-labs/dbt-codegen/pull/115
I created an integration test for "model_" prefix, which returns an array of 4 models. The test passes in all 4 environments.
Please let me know if this is good to go!


docs: deploy new web interface on moov.io

We should replace the existing demo at moov.io/ofac/ with our new web UI. This involves shifting how that site is deployed and removes the auth requirement, but we should be able to do so in a straightforward way.

Done via https://github.com/moov-io/moov-io/commit/2fe9303deff7046f0529fc4fbd33df5202484f8e and https://github.com/moov-io/moov-io/commit/0e44bfafb57cb629312e1defcdde8863deebfc1a


FileNotFoundError： [Errno 2] No such file or directory： 'datasets/BOP_DATASETS/ycbv/test/test_bboxes/yolox_x_640_ycbv_real_pbr_ycbv_bop_test.json'

Hello, I encountered an error during testing. The specific error is as follows: FileNotFoundError: [Errno 2] No such file or directory: 'datasets/BOP_DATASETS/ycbv/test/test_bboxes/yolox_x_640_ycbv_real_pbr_ycbv_bop_test.json'. Where can I obtain this file? I look forward to your reply.

Hello, I encountered an error during testing. The specific error is as follows: FileNotFoundError: [Errno 2] No such file or directory: 'datasets/BOP_DATASETS/ycbv/test/test_bboxes/yolox_x_640_ycbv_real_pbr_ycbv_bop_test.json'. Where can I obtain this file? I look forward to your reply.您好，我在训练期间遇到了一个错误。具体错误如下：FileNotFoundError： [Errno 2] No such file or directory： 'datasets/BOP_DATASETS/ycbv/test/test_bboxes/yolox_x_640_ycbv_real_pbr_ycbv_bop_test.json'。我在哪里可以获得此文件？我期待着您的回复。

It seems that you didn't download the provided test_bboxes directory.
You can follow the guidence of README to download it.

Download the 6D pose datasets from the BOP website and VOC 2012 for background images. Please also download the test_bboxes from here OneDrive (password: groupji) or BaiDuYunPan(password: vp58).

You can just download the whole datasets directory and put it under your project's path.


discrete distribution with non-integer xk

I'm just checking an example that uses a noninteger xk. I'm surprised that it actually seems to be working for pmf, cdf and ppf. I thought this is not allowed, and I don't remember any unit tests for this. I'm puzzled and think that it's not supposed to work correctly.
http://stackoverflow.com/questions/24401723/given-a-frozen-scipy-discrete-random-variable-how-can-i-know-its-support/24407565
>>> scipy.__version__
'0.13.3'

>>> xk = [0, 1, 4, 9.1, 9.5, 9.6, 11]
>>> pk = np.ones(len(xk)) / float(len(xk))
>>> di = stats.rv_discrete(values=(xk, pk))
>>> di.ppf(np.linspace(0, 1, len(xk) + 1))
array([ -1. ,   0. ,   1. ,   4. ,   9.1,   9.5,  11. ,  11. ])
>>> di.ppf(np.linspace(0, 1, len(xk) + 1) + 0.01)
array([  0. ,   1. ,   4. ,   9.1,   9.5,   9.6,  11. ,   nan])
>>> di.ppf(np.linspace(0, 1, len(xk) + 1) - 0.01)
array([  nan,   0. ,   1. ,   4. ,   9.1,   9.5,   9.6,  11. ])

>>> xk = np.linspace(0, 1, 6)
>>> pk = np.ones(len(xk)) / float(len(xk))
>>> di = stats.rv_discrete(values=(xk, pk))
>>> di.ppf(np.linspace(0, 1, len(xk) + 1))
array([-1. ,  0. ,  0.2,  0.4,  0.6,  0.8,  1. ])
>>> di.ppf(np.linspace(0, 1, len(xk) + 1) - 0.01)
array([ nan,  0. ,  0.2,  0.4,  0.6,  0.8,  1. ])
>>> di.ppf(np.linspace(0, 1, len(xk) + 1) + 0.01)
array([ 0. ,  0.2,  0.4,  0.6,  0.8,  1. ,  nan])
>>> di.inc
1

check if it really works, or raise Error ?

I'm strongly in favor of raising warnings to catch this problem (well, I'm even more strongly in favor of allowing lists of floats as input, but that's what it is) after coming across today an issue where mean worked as expected but expect behaving unexpectedly:
>>> import scipy.stats
>>> p = [0.5, 0.5]
>>> x1 = [1, 2]
>>> x2 = [1, 1.5]
>>> dist1 = scipy.stats.rv_discrete(values=(x1, p))
>>> dist2 = scipy.stats.rv_discrete(values=(x2, p))
>>> dist1.mean()    # Gives the right thing
1.5
>>> dist1.expect()  # Also gives the right thing
1.5
>>> dist2.mean()    # Gives the right thing, even though it probably shouldn't
1.25
>>> dist2.expect()  # Gives what at first sight looks like arbitrary nonsense
0.5

AFAIR (I haven't looked in a while)
merging this distribution into the base class rv_discrete is pretty awful design and makes it messy to change.
In a proper subclass we could overwrite expect just to do the full calculation, since the support is always a finite number of points. And fix/overwrite whatever else needs fixing. I think this works currently by accident and AFAIR doesn't have unit tests.
(I never checked this case systematically.)
All other distributions work on integers with fixed inc, behavior with floats is "undefined". However, integers are not and should not be enforced everywhere, e.g. pdf and logpdf of Poisson and Binomial are very useful with floats. (But statsmodels uses it's own implementation of them.)

However, integers are not and should not be enforced everywhere

If I want to maintain some rv_discrete code, do I have to dance around whatever arbitrary behavior happens when you give the function floating point inputs?

Maybe one can subclass rv_discrete and branch in rv_discrete.__new__
https://gist.github.com/ev-br/11369f1c97e141bfedbd

@argriffing   In general yes. But I was talking mostly about the predefined distributions. rv_discrete for user defined finite distributions can be fixed or get warnings. I have almost never used it.
For other distributions we have trunc or ceil or maybe round if we need integers. In other cases the functions are continuous for floats so we don't need an exact integer, and if users provide an "integer" float that is a few epsilon away from an "exact" integer, then we are still within floating point noise of the correct solution.
Wether it makes sense to call any distribution or method with arbitrary floats, depends on the specific case, but that's a "at your own risk", "I assume you know what you are doing" use case.
e.g. the use of gamma or gammaln instead of factorial extends nicely to floats. Some cdf don't make sense for floats away from integer values. ppf and isf always return an integer (as float dtype).
This behavior is practical but not fool proof (doesn't raise on user mistakes).
all AFAIR.

Proof of concept WIP PR: https://github.com/scipy/scipy/pull/5672
This fixes the specific bug with expect, https://github.com/scipy/scipy/issues/3758#issuecomment-168757015, but there are several others to fix still.
I guess it never worked, so it's an enhancement.

Wether it makes sense to call any distribution or method with arbitrary floats, depends on the specific case, but that's a "at your own risk", "I assume you know what you are doing" use case.

Just to be clear, even though it is "at your own risk" is it also guaranteed to not change between scipy versions without going through a deprecation process?

Just to be clear, even though it is "at your own risk" is it also guaranteed to not change between scipy versions without going through a deprecation process?

It's a grey zone because it's currently not systematically checked.
However, I would consider the main use cases where floats make sense like pdf and logpdf for Poisson and Binomial as guaranteed, and that we get good results in the neighborhood of an int.
I would not consider numerical implementation details as guaranteed. E.g. For some distribution (which I don't remember), the cdf is monotonic in floats but the values away from integers don't make sense, i.e. it looks like a purely numerical extension from integers to floats. There might (? I don't have one now) be use cases for monotonicity, but the exact numbers are just how it's implemented in scipy.special.
AFAIR.
I never figured out whether the use of trunc could cause problems if we have floats close to but below an integer. AFAIR, we did not have an actual bug with it.

http://stackoverflow.com/questions/37467486/getting-scipys-rv-discrete-to-work-with-floating-point-values
I think the accepted answer should make it to the documentation.

It seems like all this needs to work for arbitrary values is:

set .inc to None, to favor errorring over invalid results
Implement rv_sample.expect
Update the comment

It would need some work, sadly.
The problem with expect can indeed be fixed by implementing rv_sample.expect:
https://github.com/ev-br/scipy/commits/rv_sample_expect
However, adding stats.rv_discrete(values=([1.0, 1.5], [0.5, 0.5])) to the test loop (https://github.com/ev-br/scipy/commit/208f9d6f16d84fbf57590f9a56327f14152ae0ae) brings two more failures. The assumption that the support is a set of integers is baked somewhere deeper down.
======================================================================
FAIL: test_discrete_basic.test_discrete_basic(<scipy.stats._distn_infrastructure.rv_sample object at 0x7fd8cabbff50>, (), 'sample distribution')
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/br/virtualenvs/scipy_py27/local/lib/python2.7/site-packages/nose/case.py", line 197, in runTest
    self.test(*self.arg)
  File "/home/br/repos/scipy/build/testenv/lib/python2.7/site-packages/scipy/stats/tests/test_discrete_basic.py", line 159, in check_pmf_cdf
    atol=atol, rtol=rtol)
  File "/home/br/virtualenvs/scipy_py27/local/lib/python2.7/site-packages/numpy/testing/utils.py", line 1359, in assert_allclose
    verbose=verbose, header=header)
  File "/home/br/virtualenvs/scipy_py27/local/lib/python2.7/site-packages/numpy/testing/utils.py", line 713, in assert_array_compare
    raise AssertionError(msg)
AssertionError:
Not equal to tolerance rtol=1e-10, atol=1e-10

(mismatch 50.0%)
 x: array([ 0. ,  0.5])
 y: array([ 0.,  0.])

======================================================================
FAIL: test_discrete_basic.test_discrete_basic(<scipy.stats._distn_infrastructure.rv_sample object at 0x7fd8cabbff50>, (), array([1, 1, 1, ..., 1, 1, 1]), 0.01, 'sample distribution chisquare')
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/br/virtualenvs/scipy_py27/local/lib/python2.7/site-packages/nose/case.py", line 197, in runTest
    self.test(*self.arg)
  File "/home/br/repos/scipy/build/testenv/lib/python2.7/site-packages/scipy/stats/tests/test_discrete_basic.py", line 232, in check_discrete_chisquare
    (msg, str(arg), str(pval)))
  File "/home/br/virtualenvs/scipy_py27/local/lib/python2.7/site-packages/numpy/testing/utils.py", line 53, in assert_
    raise AssertionError(smsg)
AssertionError: chisquare - test for sample distribution chisquare at arg = () with pval = 0.0

----------------------------------------------------------------------
Ran 3147 tests in 49.695s

FAILED (KNOWNFAIL=4, SKIP=34, failures=2)

I missed the doc's indication of integer only values, so I found that the std method also behave's unexpectedly:
>>> from scipy import stats
>>> x = stats.rv_discrete(values=([2.964],[1.0]))
>>> x.std() # Expected 0.0
nan

I thought it might be useful for those trying to figure out which methods are impacted by the integrality assumption.

I would like to implement an empirical distribution, either just for myself or as a contribution to scipy.stats.
The idea is that the CDF of this empirical distribution would be the standard empirical CDF
and drawing numbers from this distribution could be used for bootstrap replications.
rv_discrete with the values parameter would be the natural way to do that. But then I quickly noticed the things discussed here, that it is per documentation restricted to integers and in practice works with reals, but only partially.
The issue is still open, but the last comment is over a year old, so I'm guessing nobody is working on this?
I would try to do it myself, but looking at the code leaves me extremely confused. And the documentation is sparse; I don't even really understand how I would subclass rv_discrete, and the rv_sample mentioned here doesn't appear in the documentation. What's a ctor?!

Here is a sketch of an implementation:

code
import numpy as np

rng = np.random.default_rng()

class discrete:
    """
    discrete distribution
    """

    def __init__(self, values, weights=None):
        # input checking and normalization
        values = np.array(values).flatten()
        values, index, counts = np.unique(values, return_index=True, return_counts=True)
        if np.any(counts > 1):
            raise ValueError('values must be unique')
        if weights is not None:
            weights = np.array(weights).flatten()
            weights = weights[index]
            if len(weights) != len(values):
                raise ValueError('number of weights must match number of values')
        else:
            weights = np.ones(len(values))
        # class state
        self.xk = values
        self.pk = weights / sum(weights)
        self.Pk = np.hstack(([0], np.cumsum(self.pk)))

    def pmf(self, x, tol=0.0):
        """
        probability mass function
        """
        # normalization
        x = np.array(x)
        shape = x.shape
        x = x.flatten()
        # compute
        e = np.abs(x - self.xk[:, np.newaxis])
        ind = np.argmin(e, axis=0)
        p = self.pk[ind]
        eMin = e[ind, np.arange(e.shape[1])]
        p[eMin > tol] = 0.0
        # back into shape
        p = np.reshape(p, shape)
        return p

    def cdf(self, x):
        """
        cumulative distribution function
        """
        # normalization
        x = np.array(x)
        shape = x.shape
        x = x.flatten()
        # compute
        ind = np.sum(self.xk[:, np.newaxis] <= x, axis=0)
        P = self.Pk[ind]
        # back into shape
        P = np.reshape(P, shape)
        return P

    def rvs(self, size=None):
        return rng.choice(self.xk, p=self.pk, size=size)

class empirical(discrete):
    """
    empirical distribution
    """

    def __init__(self, sample):
        (xu, cu) = np.unique(sample, return_counts=True)
        super().__init__(xu, cu)
        self.n = len(sample)

    def bootstrap_sample(self, N=1):
        if N == 1:
            return self.rvs(size=self.n)
        else:
            return self.rvs(size=(N, self.n))

But as I said, I don't know how to put that into the framework of scipy.stats.

What's a ctor?!

Usually short for constructor

Is there a developer's guide?

There is a guide showing an example for adding a continuous distribution, but it's straightforwards to substitute discrete distributions instead: https://docs.scipy.org/doc/scipy/reference/dev/contributor/adding_new.html

What's a ctor?!

Usually short for constructor

Is there a developer's guide?

There is a guide showing an example for adding a continuous distribution, but it's straightforwards to substitute discrete distributions instead: https://docs.scipy.org/doc/scipy/reference/dev/contributor/adding_new.html

This issue is not about built-in discrete distributions like binom; it's about custom discrete distribution defined with the values argument. Since gh-5672 merged, these are really instances of rv_sample.

I'm surprised that it actually seems to be working for pmf, cdf and ppf

pmf does not work as desired for non-integer xk because it shares the pmf implementation with built-in distributions. For these, the domain is the integers, so it makes sense for the pmf to be zero at non-integer xk. But this condition is built into pmf, so that needs to be changed.
cdf does not work as I would expect. ppf does seem to work as desired, but they need to be checked systematically.


Post 'extend' operator: Failed to resolve table or column expression named 'WaaSDeploymentStatus'...

Describe the bug
A clear and concise description of what the bug is. 'extend' operator: Failed to resolve table or column expression named 'WaaSDeploymentStatus'...
Post uploading to Intune Portal reporting getting error and Update Compliance Table not getting created
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

Additional context
Add any other context about the problem here.

i have the same pb

You have to actually send update data to log analytics in order for that table to be created as stated in the blog post.
Enable Windows diagnostics

I have the same problem, I had created the diagnostic settings and even left them for a week, however I don't see that table in the Log Analytics Workspace:

Currently we only have an Update ring, and Driver update policy assigned. We also have a feature update policy that hasn't been assigned and nothing under the quality updates tab. Do we need to create a quality update/expedite update policy for this table to show up in the Intune logs or does the WaaSDeploymentStatus table come from somewhere else?
I'm asking because I don't see that log listed here https://learn.microsoft.com/en-us/mem/intune/fundamentals/review-logs-using-azure-monitor#send-logs-to-azure-monitor

Ensure the devices are correctly configured to send Windows Update reporting data to Log Analytics

Go to the Microsoft Endpoint Manager Admin Center:
•	Navigate to Reports > Windows updates.
•	Verify that the reporting data collection for Windows Update for Business (WUfB) is enabled.
Ensure that Update compliance settings are configured:
•	Log in to the Azure portal.
•	Go to Azure Monitor > Log Analytics Workspaces > Workspace Settings.
•	Under Agents Management, ensure devices are correctly connected to the workspace.

Ensure that Update compliance settings are configured:
•	Log in to the Azure portal.
•	Go to Azure Monitor > Log Analytics Workspaces > Workspace Settings.
•	Under Agents Management, ensure devices are correctly connected to the workspace.
Check Intune Device Configuration Policy for Update Compliance
The Update Compliance integration requires a Custom Device Configuration profile in Intune.

Go to Endpoint Manager Admin Center > Devices > Configuration Profiles.
Create or verify the following:
•	OMA-URI Configuration:
•	OMA-URI Path:  ./Vendor/MSFT/Policy/Config/Update/AllowWUfBCloudProcessing
•	Value: 1
This ensures Windows Update for Business telemetry data is sent to Azure.
Ensure the policy is deployed to the correct device group.

Verify Device Telemetry Settings
The WaaSDeploymentStatus data relies on telemetry. Ensure devices have the proper diagnostic data settings:

Open Settings on the device:
•	Go to Privacy > Diagnostics & Feedback.
•	Ensure that Optional diagnostic data is enabled.
In Intune:
•	Go to Devices > Windows > Configuration profiles.
•	Create or update a profile to set:
•	Telemetry level to Enhanced or Full.

Custom OMA-URI for Telemetry Settings
If required, deploy the following setting via a custom configuration profile:
•	OMA-URI Path: ./Vendor/MSFT/Policy/Config/System/AllowTelemetry
•	Value: Enhanced (2) or Full (3).
Verify Devices are Reporting to Log Analytics

Go to your Log Analytics Workspace in the Azure Portal.
Use the following query to check for data:
,,,
UpdateCompliance
| summarize count() by DeviceName
,,,

If no data is returned:
•	Confirm the workspace ID and key are correct in your configuration.
•	Ensure that devices can communicate with the Log Analytics endpoint.
Check for Windows Update Compliance Delay
•	Windows Update reporting can take up to 24-48 hours to appear in Log Analytics.
•	Devices must have internet connectivity and Telemetry Services running.
Validate Required Firewall and Network Connectivity
Devices must reach Log Analytics endpoints and Windows Update for Business (WUfB) telemetry endpoints. Allow the following URLs in your firewall/proxy:
•	*.monitor.azure.com
•	*.ods.opinsights.azure.com
•	*.loganalytics.io
•	v20.events.data.microsoft.com
Revalidate Device Enrollment
Devices must be enrolled in both Intune and correctly configured for WUfB.
Run the following commands on a client machine to validate settings:
# Check Telemetry Level
Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection"

# Check Connectivity to Windows Update Service
Test-NetConnection -ComputerName settings-win.data.microsoft.com -Port 443


Installing messageformat with npm from github is all over the shop

Hi
If I have this in my package.json
 "devDependencies": {
    "messageformat": "SlexAxton/messageformat.js#0.3.0-0"
 }

and do a npm install all seems good. But when I try to bundle messageformat with webpack I get all sort of errors which I don't get with the npm version
WARNING in ./~/messageformat/~/make-plural/make-plural.js
Critical dependencies:
192:49-71 the request of a dependency is an expression
 @ ./~/messageformat/~/make-plural/make-plural.js 192:49-71

WARNING in ./~/messageformat/~/make-plural/package.json
Module parse failed: /PATH//node_modules/messageformat/node_modules/make-plural/package.json Line 2: Unexpected token :
You may need an appropriate loader to handle this file type.
| {
|   "name": "make-plural",
|   "version": "2.1.3",
|   "description": "Translates Unicode CLDR pluralization rules to executable JavaScript",
 @ ./~/messageformat/~/make-plural ^\.\/.*$

WARNING in ./~/messageformat/~/make-plural/LICENSE
Module parse failed: /PATH//node_modules/messageformat/node_modules/make-plural/LICENSE Line 1: Unexpected number
You may need an appropriate loader to handle this file type.
| Copyright (c) 2014, Eemeli Aro<EMAIL_ADDRESS>|
| Permission to use, copy, modify, and/or distribute this software for any
 @ ./~/messageformat/~/make-plural ^\.\/.*$

WARNING in ./~/messageformat/~/make-plural/bin/make-plural
Module parse failed: /PATH//node_modules/messageformat/node_modules/make-plural/bin/make-plural Line 1: Unexpected token ILLEGAL
You may need an appropriate loader to handle this file type.
| #!/usr/bin/env node
|
| /** A minimal/sample interface for make-plural.js
 @ ./~/messageformat/~/make-plural ^\.\/.*$

WARNING in ./~/messageformat/~/make-plural/README.md
Module parse failed: /PATH//node_modules/messageformat/node_modules/make-plural/README.md Line 2: Unexpected token ===
You may need an appropriate loader to handle this file type.
| make-plural
| ===========
|
| A JavaScript module that translates [Unicode CLDR](http://cldr.unicode.org/)
 @ ./~/messageformat/~/make-plural ^\.\/.*$

WARNING in ./~/messageformat/~/make-plural/data/unicode-cldr-ordinal-rules.json
Module parse failed: /PATH//node_modules/messageformat/node_modules/make-plural/data/unicode-cldr-ordinal-rules.json Line 2: Unexpected token :
You may need an appropriate loader to handle this file type.
| {
|   "supplemental": {
|     "version": {
|       "_cldrVersion": "26",
 @ ./~/messageformat/~/make-plural ^\.\/.*$

WARNING in ./~/messageformat/~/make-plural/data/unicode-cldr-plural-rules.json
Module parse failed: /PATH//node_modules/messageformat/node_modules/make-plural/data/unicode-cldr-plural-rules.json Line 2: Unexpected token :
You may need an appropriate loader to handle this file type.
| {
|   "supplemental": {
|     "version": {
|       "_cldrVersion": "26",
 @ ./~/messageformat/~/make-plural ^\.\/.*$

All these failures are on non-javascript files. Unsure why it's changed between the two versions, but I assume there's something you can do in webpack to ignore non-js files.

(The make-plural dependency is new as of 0.3.0)

Installing via npm with the @prerelease tag as suggested in issue 107 solves the problem - so it's either something to do with npm or with webpack. Thanks, closing issue.


response logEvents should honor ignorePaths

It seems ignorePaths is only used when logEvent is request but would be beneficial when the log event is response as well. Like the README states, ignoring certain paths can reduce the noise in the logs for health check routes (Kubernetes pings a service quite frequently for health check routes).
If this sounds good I can submit a PR when time permits.

Go for it!
Il giorno gio 16 ago 2018 alle 16:49 robert mcguinness <
<EMAIL_ADDRESS>ha scritto:

It seems ignorePaths is only used when logEvent is request but would be
beneficial when the log event is response as well. Like the README
states, ignoring certain paths can reduce the noise in the logs for health
check routes (Kubernetes pings a service quite frequently for health check
routes).
If this sounds good I can submit a PR when time permits.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pinojs/hapi-pino/issues/63, or mute the thread
https://github.com/notifications/unsubscribe-auth/AADL48NEs_iUGkQBFft_owhgssbrQA0iks5uRYZ_gaJpZM4WAAUq
.


More broken anchor link...

Signed-off-by: Guillaume Tardif<EMAIL_ADDRESS>

Tested the link now works in VSCode with the fix...


Error: Uploading to a HockeyApp store app is not supported

I have apps that are getting currently uploaded to Hockey App. But since Hockey App will be deprecated after a couple of months, we are currently in the process of migrating / uploading our mobile builds to App Center. We have both Android and iOS builds for various configurations like Debug, Beta, Automation, Production and so on. I followed the documentation provided in the link https://docs.microsoft.com/en-us/appcenter/distribution/uploading and was successfully able to upload both Android and iOS builds for various configurations to App Center. But only for Android Production configuration, I get an error "Error: Uploading to a HockeyApp store app is not supported" in the first step itself when I am trying to get an upload url using the following curl command. Can anyone please help me? I am not sure why this alone is failing.
curl -s -X POST --header 'Content-Type: application/json' --header 'Accept: application/json' --header 'X-API-Token: MyToken' https://api.appcenter.ms/v0.1/apps/org-name/Android-Production/release_uploads

@venh The comments feature of our documentation is intended to enable customers to suggest changes to the docs or ask clarifying questions about the docs.
App Center support is provided directly from within the App Center portal. Any time you need help, just click the blue chat button in the lower-right corner of any page and our dedicated support team will respond. For additional information, see the App Center Help Center.


Update AggregateBuilderStage

Description
I updated AggregateBuilderStage with 2 tiny updates :

Modified assert condition in skip, to work with 0 as value
Modified access-controles for AggregateBuilderStage Struct to create custom object with many documents

Motivation
The modification on access-controles for AggregateBuilderStage, allow to create custom a new AggregateBuilderStage with many document outside the MongoKitten package.
How Has This Been Tested?

Skip: no unit test 😬  but tested in Mongo Shell
New access-controles: a new unit test 😎

Checklist:

[ ] If applicable, I have updated the documentation accordingly.
[x] If applicable, I have added tests to cover my changes.

Hey! Thanks for the PR. Just a question; why did you make stages public

Hey! Thanks for the PR. Just a question; why did you make stages public

As in the exemple present in unit test, I used stages to build a custom AggregateBuilderStage by reducing like the Result Builder function in AggregateBuilder.swift.
// AggregateBuilder.swift

public static func buildBlock(_ content: AggregateBuilderStage...) -> AggregateBuilderStage {
    return AggregateBuilderStage(documents: content.reduce([], { $0 + $1.stages }))
}

I can revert the getter access-control in stages, this can works without this change.

Sorry, I had a vacation so this was being delayed a bit :)


Update python package identification to use DependencyDescriptor

This adds version metadata to the dependencies created by python package identification.

Distlib is a library which implements low-level functions that relate to packaging and distribution of Python software. It consists in part of the functions in the packaging Python package, which was intended to be released as part of Python 3.3, but was removed shortly before Python 3.3 entered beta testing.

It seems like distlib is the correct library to use for the parsing functionality. Pip uses distlib as seen here.

Codecov Report

Merging #118 into master will increase coverage by <.01%.
The diff coverage is 84.61%.

@@            Coverage Diff             @@
##           master     #118      +/-   ##
==========================================
+ Coverage   78.23%   78.24%   +<.01%
==========================================
  Files          51       51
  Lines        2840     2850      +10
  Branches      479      482       +3
==========================================
+ Hits         2222     2230       +8
- Misses        593      594       +1
- Partials       25       26       +1

Impacted Files
Coverage Δ

colcon_core/package_identification/python.py
84.61% <84.61%> (-0.84%)
:arrow_down:

Continue to review full report at Codecov.

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

Awesome update, it's a great idea to use the join instead of messing with string concatenation. Thanks for all your help with this.

Ready to be merged :+1:
Since I shuffled a bit of code around I wanted to give you @murphm8 a chance to take another look before it gets merged though. Let me know what you think. Thanks.

Never mind - just saw your post... Merging!


Dev: console error on create task when user skip Assignee while creating task

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

click on + button
choose Assign task option
Enter title
click on Next button
click on share somewhere
click on any member from list
click on confirm task

Expected Result:
should not show any console error
Actual Result:
shows console error
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.3.17-1
Reproducible in staging?: needs reproduction (Occurs in Dev)
Reproducible in production?: n/a
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/43996225/c3c5c895-8300-4519-b0e5-ef6ac3b60e81
Expensify/Expensify Issue URL:
Issue reported by: @gadhiyamanan
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1684906837341679
View all open jobs on GitHub

This is already being fixed in https://github.com/Expensify/App/pull/19639

Not overdue, weighting for https://github.com/Expensify/App/pull/19639 to hit staging to see if its fixed


less results when keyboard up

Hey!
When I first navigate to my screen with the search bar it shows the full list on the screen. As soon as I press on the search field and the keyboard comes up it removes a lot of the results and only shows 3 even though there is a lot of space left between the keyboard and the results.

Thanks for the awesome package!

You shouldn't use MaterialSearch in Scaffold because MaterialSearch returned Scaffold.
Change to  return new MaterialSearch
Hope this to help you

Changed it to return MaterialSearch but it made no difference. :/

That resolved the issue I had, thanks!

Woow! Cool. I didn't have time to look in to it. Happy that @lidroider found the solution! Thanks!


Optionally disable internal metric collection with NullStatser

If a server configuration has DisableInternalMetrics: true use NullStatser in place of InternalStatser to disable the internal metrics collected. Add the field StatserType to the Server struct and make that field configurable to an InternalStatser, LoggingStatser, or NullStatser.
Closes #167
Signed-off-by: Nikki Attea<EMAIL_ADDRESS>

@ash2k @tiedotguy Thank you both for the feedback! I'd love to make this more configurable for the other statsers as well! I'm thinking something along the lines below should do the trick, but I'm not sure how exactly to configure a TaggedStatser as it requires another statser as a parameter. Any guidance on the matter would be greatly appreciated!
var statser stats.Statser
switch s.StatserType {
case StatserNull:
    statser = stats.NewNullStatser()
case StatserTagged:
    statser := stats.NewTaggedStatser(statser?, s.InternalTags)
case StatserLogging:
    statser := stats.NewLoggingStatser(s.InternalTags, log.NewEntry(log.New()))
default:
    statser = stats.NewInternalStatser(bufferSize, s.InternalTags, namespace, hostname, metrics, events)
    stage = stgr.NextStage()
    stage.StartWithContext(statser.Run)
}

Ahh actually I see, a TaggedStatser is created through the func WithTags!

@tiedotguy @ash2k Okay, this should be better. Second pass when you get a chance?

Looks good to me.  I can see you've signed the CLA, but as this is being done for Sensu, can you sign the corporate CLA?  Sorry for the rigmarole.

I'm ok with the indenting thing, I'll fix it after merge to master when I update the CHANGELOG.md, just need the corporate CLA!

@tiedotguy Haha, no problem! We're just in the process of clearing the corporate CLA with legal, should be done soon, thanks!

@tiedotguy The corporate CLA has been executed by @grepory on behalf of Sensu! Thanks y'all for all your help!

This is fantastic, can't wait for this to get in 💪

Thanks for your patience, there was some issues with the CLA tracking, but all sorted now!


Double quote to prevent globbing and word splitting.

Codacy detected an issue:
Message: Double quote to prevent globbing and word splitting.
Occurred on:

Commit:  a54e88ef01217fa74a4cf24c26067c7741af4c67
File:    lib/trash.sh
LineNum: 89
Code:    _rmlist=($(find "$OMS_CACHE/trash" -maxdepth 1 -printf "%f\n" | grep $NP))

Currently on:

Commit:  a54e88ef01217fa74a4cf24c26067c7741af4c67
File:    lib/trash.sh
LineNum: 89

            _rmlist=()
            find "$OMS_CACHE/trash" -maxdepth 1 -printf "%f\n" | grep $NP | while IFS= read -r i
            do
                _rmlist+=("$i")
            done

not working...


Correct misleading wording in Pod DNS Policies

A debugging rabbit hole lead me to digging around kublet's behavior regarding certain DNS Policies.
This commit updates some potentially misleading wordings to more correctly convey kubelet's behavior which was discovered after some rabbit hole debugging of DNS Policies.
The ClusterFirst policy documentation would imply that the resolve.conf of a Pod would contain a fallback to the Node's nameserver. This is not the cause, kubelet explicitly mentions that the fallback is handled by whatever system is running kube-dns or coredns which dramatically changes the behavior of the system when the cluster's DNS is unavailable.
The ClusterFirstWithHostNet policy is lacking any amount of detail as to why one would desire to use it. This commit doesn't go into complete detail but adds an important note about the behavior of hostNetwork when not using the ClusterFirstWIthHostNet Policy.

/approve


Introduce functionality for kafka functionality for tempo

Currently tempo has clients that talk to remote models. In order to introduce support for stream processing such as through Kafka, we would need to extend the current interfaces to support asynchronous processing.
Models would be defined the same way
sklearn_model = Model(
    name="test-iris-sklearn",
    platform=ModelFramework.SKLearn,
    local_folder=f"{artifacts_folder}/{SKLearnFolder}",
    uri="s3://tempo/basic/sklearn",
)

xgboost_model = Model(
    name="test-iris-xgboost",
    platform=ModelFramework.XGBoost,
    local_folder=f"{artifacts_folder}/{XGBoostFolder}",
    uri="s3://tempo/basic/xgboost",
)

Option 1: AsyncIO
Each instance to a pipeline is processed synchronously, with each subsequent model "synchronously", of course using AsyncIO to release control, but waiting until the respective model "returns" the output to the output_topic.
Advantages

syntax wouldn't change for requests based vs stream based processing.
State is maintained, which means that "combiner" logic is orders of magnitude simpler (or even feasible)

Disadvantages

The logic to await for the model to respond is not trivial with Python + Kafka.
The models would be dependent on the availability of processing as opposed to being fully async (eg could run forever or time out logic needs to be introduced)

@pipeline(
    name="classifier",
    uri="s3://tempo/basic/pipeline",
    local_folder=f"{artifacts_folder}/{PipelineFolder}",
    models=PipelineModels(sklearn=sklearn_model, xgboost=xgboost_model),
)
def classifier(payload: np.ndarray) -> Tuple[np.ndarray, str]:
    res1 = await classifier.models.sklearn(input=payload)

    if res1[0] == 1:
        return res1, SKLearnTag
    else:
        return await classifier.models.xgboost(input=payload), XGBoostTag

Option 2: Fully Asynchronous Streams
The second option is to approach it in the fully traditional independent stream processing approach, where each independent data instance would be processes as single step across the streaming pipeline process.
Advantages

Each data point is processed asynchronously which means more efficient use of compute

Disadvantage

Different syntax
No state locally

p = Pipeline(
    name="classifier",
    uri="s3://tempo/basic/pipeline",
    local_folder=f"{artifacts_folder}/{PipelineFolder}",
    models=PipelineModels(sklearn=sklearn_model, xgboost=xgboost_model),
)

@p.pipeline
def classifier(payload: np.ndarray) -> Tuple[np.ndarray, str]:
    classifier.models.sklearn.send(input=payload)

@p.models.sklearn
def sklearn(res1):
    if res1[0] == 1:
        return res1, SKLearnTag
    else:
        p.models.xgboost.send(input=payload), XGBoostTag

@p.models.xgboost
def xgboost(res):
    return res

I think both options can probably be combined.
From my point of view, asyncio support is a must. Even without streaming, it's probably needed to optimise pipelines (where I imagine most of the time would be spent in IO, waiting for the model's answer). For the streaming scenario, asyncio can be leveraged to optimise the waiting time for Kafka to come back.
We could think about making it optional though. That is, let people define both async or "classic" methods, and let Tempo decide how to call a custom function (i.e. with await or synchronously). This is similar to how FastAPI handles this, without forcing the user to write full async code.


bugfix: fix jedis unlock fail

Ⅰ. Describe what this PR did
fix jedis unlock fail
Ⅱ. Does this pull request fix one issue?

fix #2898
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #2897 into develop will decrease coverage by 0.00%.
The diff coverage is 0.00%.

@@              Coverage Diff              @@
##             develop    #2897      +/-   ##
=============================================
- Coverage      49.96%   49.96%   -0.01%
  Complexity      3013     3013
=============================================
  Files            597      597
  Lines          19267    19268       +1
  Branches        2304     2304
=============================================
  Hits            9627     9627
- Misses          8656     8657       +1
  Partials         984      984

Impacted Files
Coverage Δ
Complexity Δ

...o/seata/server/storage/redis/lock/RedisLocker.java
38.31% <0.00%> (-0.37%)
10.00 <0.00> (ø)

What is the meaning of logQueryLimit?
relieve redis query pressure? If so, why not delete in batches? Will memory be OOM?

The maximum value of a single query is used to relieve the pressure of redis reading a large amount of data at one time
Use the pipeline to make a one-time request to delete


FIX fixing ssh connection issues

Please prefix your pull request with one of the following: [FEATURE] [FIX] [IMPROVEMENT].
In raising this pull request, I confirm the following (please check boxes):

[X] I have read and understood the contributing guidelines?
[X] I have checked that another pull request for this purpose does not exist.
[X] I have considered, and confirmed that this submission will be valuable to others.
[ ] Do the TravisCI tests pass?
[ ] Does the StyleCI test pass?

NOTE: The last 2 are not required to open a PR and can be done afterwards /
while the PR is open.

Description of change
Please provide a description of the change here.
trying to reproduce the error that doesn't let me to set my server on the project panel, I looked into the log stored in storage/app/XXXX.log and I got this message
[2016-11-08 12:26:51] production.DEBUG: ssh -o CheckHostIP=no
-o IdentitiesOnly=yes
-o StrictHostKeyChecking=no
-o PasswordAuthentication=no
-o IdentityFile=/var/projects/deployer/storage/app/sshkeyOZD8Nj
-p 22 XXXXXX@XXXXXX 'bash -s' << 'EOF'  etc ...
NOTE:
the file sshkey???? is removed by deployer inmediately but I just trick it filling in with the private_key field on the DB for the current project
Executing the same command by hand I got:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@         WARNING: UNPROTECTED PRIVATE KEY FILE!          @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Permissions 0644 for '/var/projects/deployer/storage/app/sshkeyOZD8Nj' are too open.
It is required that your private key files are NOT accessible by others.
This private key will be ignored.
bad permissions: ignore key: /var/projects/deployer/storage/app/sshkeyOZD8Nj
whith my change we ensure that the privatekey gots the proper permissions
right now with this change I passed the server check and I am able to deploy

Thanks, I shall take a look at this

Just noticed this is pointing at the wrong branch, can you open a new PR for merging into master?

Seems that is not working my fix in a production environment. For any reason when the process is launched is using another user and I cannot debug the process by hand. I will come later with the solution if any.
Sorry to bother you ;)

Hmm, the script which creates the SSH key should be running as the same user as the process which uses it, they are after all bother launched by the Laravel queue daemon which is run by supervisor :|


http: invalid host header on docker-compose up

Running Ubuntu 20.04 Focal
$ docker-compose --profile linux up
generates:
[+] Running 1/1
! pull-model Warning                                                                             1.4s
[+] Building 0.0s (0/0)
http: invalid Host header
Hoping for suggestions.

Is your problem similar to : https://stackoverflow.com/questions/77225539/docker-compose-error-internal-booting-buildkit-http-invalid-host-header ?

Is your problem similar to : https://stackoverflow.com/questions/77225539/docker-compose-error-internal-booting-buildkit-http-invalid-host-header ?

Yes thank you. For other reasons I rebuilt the entire host clean. ubuntu 23.10 and got past this. It was a docker compose v2 issue I guess. But now I have another issue building the containers and get this error:

failed to solve: process "/bin/sh -c apt-get update && apt-get install -y     build-essential     curl     software-properties-common     && rm -rf /var/lib/apt/lists/*" did not complete successfully: exit code: 100

I believe I have already seen this issue which fails at apt-get install -y build-essential curl software-properties-common. Often people fixed it by clearing the build cache and rebuilding the container.

I believe I have already seen this issue which fails at apt-get install -y build-essential curl software-properties-common. Often people fixed it by clearing the build cache and rebuilding the container.

Thanks for the suggestion, but it didn't seem to change anything. Still stuck at building the containers.

What's the full stacktrace of the error ?

docker compose --profile linux up
WARN[0000] The "LANGCHAIN_PROJECT" variable is not set. Defaulting to a blank string.
WARN[0000] The "LANGCHAIN_API_KEY" variable is not set. Defaulting to a blank string.
WARN[0000] The "AWS_ACCESS_KEY_ID" variable is not set. Defaulting to a blank string.
WARN[0000] The "AWS_SECRET_ACCESS_KEY" variable is not set. Defaulting to a blank string.
WARN[0000] The "AWS_DEFAULT_REGION" variable is not set. Defaulting to a blank string.
WARN[0000] The "LANGCHAIN_PROJECT" variable is not set. Defaulting to a blank string.
WARN[0000] The "LANGCHAIN_API_KEY" variable is not set. Defaulting to a blank string.
WARN[0000] The "AWS_ACCESS_KEY_ID" variable is not set. Defaulting to a blank string.
WARN[0000] The "AWS_SECRET_ACCESS_KEY" variable is not set. Defaulting to a blank string.
WARN[0000] The "AWS_DEFAULT_REGION" variable is not set. Defaulting to a blank string.
WARN[0000] The "LANGCHAIN_PROJECT" variable is not set. Defaulting to a blank string.
WARN[0000] The "LANGCHAIN_API_KEY" variable is not set. Defaulting to a blank string.
WARN[0000] The "AWS_ACCESS_KEY_ID" variable is not set. Defaulting to a blank string.
WARN[0000] The "AWS_SECRET_ACCESS_KEY" variable is not set. Defaulting to a blank string.
WARN[0000] The "AWS_DEFAULT_REGION" variable is not set. Defaulting to a blank string.
WARN[0000] The "LANGCHAIN_PROJECT" variable is not set. Defaulting to a blank string.
WARN[0000] The "LANGCHAIN_API_KEY" variable is not set. Defaulting to a blank string.
WARN[0000] The "AWS_ACCESS_KEY_ID" variable is not set. Defaulting to a blank string.
WARN[0000] The "AWS_SECRET_ACCESS_KEY" variable is not set. Defaulting to a blank string.
WARN[0000] The "AWS_DEFAULT_REGION" variable is not set.

(Reading database ... 24887 files and directories currently installed.)
6.541 Preparing to unpack .../00-systemd-sysv_252.17-1~deb12u1_amd64.deb ...
6.543 Unpacking systemd-sysv (252.17-1~deb12u1) ...
6.567 Selecting previously unselected package libdbus-1-3:amd64.
6.569 Preparing to unpack .../01-libdbus-1-3_1.14.10-1~deb12u1_amd64.deb ...
6.570 Unpacking libdbus-1-3:amd64 (1.14.10-1~deb12u1) ...
6.595 Selecting previously unselected package dbus-bin.
6.597 Preparing to unpack .../02-dbus-bin_1.14.10-1~deb12u1_amd64.deb ...
6.599 Unpacking dbus-bin (1.14.10-1~deb12u1) ...
6.620 Selecting previously unselected package dbus-session-bus-common.
6.622 Preparing to unpack .../03-dbus-session-bus-common_1.14.10-1~deb12u1_all.deb ...
6.623 Unpacking dbus-session-bus-common (1.14.10-1~deb12u1) ...
6.645 Selecting previously unselected package dbus-daemon.
6.647 Preparing to unpack .../04-dbus-daemon_1.14.10-1~deb12u1_amd64.deb ...
6.648 Unpacking dbus-daemon (1.14.10-1~deb12u1) ...
6.673 Selecting previously unselected package dbus-system-bus-common.
6.675 Preparing to unpack .../05-dbus-system-bus-common_1.14.10-1~deb12u1_all.deb ...
6.676 Unpacking dbus-system-bus-common (1.14.10-1~deb12u1) ...
6.701 Selecting previously unselected package dbus.
6.703 Preparing to unpack .../06-dbus_1.14.10-1~deb12u1_amd64.deb ...
6.705 Unpacking dbus (1.14.10-1~deb12u1) ...
6.730 Selecting previously unselected package sgml-base.
6.732 Preparing to unpack .../07-sgml-base_1.31_all.deb ...
6.736 Unpacking sgml-base (1.31) ...
6.762 Selecting previously unselected package libnss-systemd:amd64.
6.764 Preparing to unpack .../08-libnss-systemd_252.17-1~deb12u1_amd64.deb ...
6.767 Unpacking libnss-systemd:amd64 (252.17-1~deb12u1) ...
6.793 Selecting previously unselected package libpam-systemd:amd64.
6.795 Preparing to unpack .../09-libpam-systemd_252.17-1~deb12u1_amd64.deb ...
6.796 Unpacking libpam-systemd:amd64 (252.17-1~deb12u1) ...
6.826 Selecting previously unselected package systemd-timesyncd.
6.827 Preparing to unpack .../10-systemd-timesyncd_252.17-1~deb12u1_amd64.deb ...
6.829 Unpacking systemd-timesyncd (252.17-1~deb12u1) ...
6.852 Selecting previously unselected package libstemmer0d:amd64.
6.854 Preparing to unpack .../11-libstemmer0d_2.2.0-2_amd64.deb ...
6.855 Unpacking libstemmer0d:amd64 (2.2.0-2) ...
6.881 Selecting previously unselected package libxmlb2:amd64.
6.883 Preparing to unpack .../12-libxmlb2_0.3.10-2_amd64.deb ...
6.885 Unpacking libxmlb2:amd64 (0.3.10-2) ...
6.906 Selecting previously unselected package libappstream4:amd64.
6.908 Preparing to unpack .../13-libappstream4_0.16.1-2_amd64.deb ...
6.910 Unpacking libappstream4:amd64 (0.16.1-2) ...
6.938 Selecting previously unselected package appstream.
6.940 Preparing to unpack .../14-appstream_0.16.1-2_amd64.deb ...
6.942 Unpacking appstream (0.16.1-2) ...
6.981 Selecting previously unselected package build-essential.
6.983 Preparing to unpack .../15-build-essential_12.9_amd64.deb ...
6.985 Unpacking build-essential (12.9) ...
7.004 Selecting previously unselected package dbus-user-session.
7.005 Preparing to unpack .../16-dbus-user-session_1.14.10-1~deb12u1_amd64.deb ...
7.007 Unpacking dbus-user-session (1.14.10-1~deb12u1) ...
7.027 Selecting previously unselected package distro-info-data.
7.029 Preparing to unpack .../17-distro-info-data_0.58_all.deb ...
7.030 Unpacking distro-info-data (0.58) ...
7.049 Selecting previously unselected package libpackagekit-glib2-18:amd64.
7.051 Preparing to unpack .../18-libpackagekit-glib2-18_1.2.6-5_amd64.deb ...
7.052 Unpacking libpackagekit-glib2-18:amd64 (1.2.6-5) ...
7.075 Selecting previously unselected package gir1.2-packagekitglib-1.0.
7.077 Preparing to unpack .../19-gir1.2-packagekitglib-1.0_1.2.6-5_amd64.deb ...
7.078 Unpacking gir1.2-packagekitglib-1.0 (1.2.6-5) ...
7.096 Selecting previously unselected package iso-codes.
7.098 Preparing to unpack .../20-iso-codes_4.15.0-1_all.deb ...
7.100 Unpacking iso-codes (4.15.0-1) ...
7.332 Selecting previously unselected package libcap2-bin.
7.334 Preparing to unpack .../21-libcap2-bin_1%3a2.66-4_amd64.deb ...
7.336 Unpacking libcap2-bin (1:2.66-4) ...
7.358 Selecting previously unselected package libduktape207:amd64.
7.360 Preparing to unpack .../22-libduktape207_2.7.0-2_amd64.deb ...
7.362 Unpacking libduktape207:amd64 (2.7.0-2) ...
7.388 Selecting previously unselected package libdw1:amd64.
7.390 Preparing to unpack .../23-libdw1_0.188-2.1_amd64.deb ...
7.392 Unpacking libdw1:amd64 (0.188-2.1) ...
7.420 Selecting previously unselected package libunwind8:amd64.
7.422 Preparing to unpack .../24-libunwind8_1.6.2-3_amd64.deb ...
7.424 Unpacking libunwind8:amd64 (1.6.2-3) ...
7.447 Selecting previously unselected package libgstreamer1.0-0:amd64.
7.449 Preparing to unpack .../25-libgstreamer1.0-0_1.22.0-2_amd64.deb ...
7.451 Unpacking libgstreamer1.0-0:amd64 (1.22.0-2) ...
7.523 Selecting previously unselected package libpam-cap:amd64.
7.525 Preparing to unpack .../26-libpam-cap_1%3a2.66-4_amd64.deb ...
7.527 Unpacking libpam-cap:amd64 (1:2.66-4) ...
7.548 Selecting previously unselected package libpolkit-gobject-1-0:amd64.
7.550 Preparing to unpack .../27-libpolkit-gobject-1-0_122-3_amd64.deb ...
7.552 Unpacking libpolkit-gobject-1-0:amd64 (122-3) ...
7.573 Selecting previously unselected package libpolkit-agent-1-0:amd64.
7.575 Preparing to unpack .../28-libpolkit-agent-1-0_122-3_amd64.deb ...
7.577 Unpacking libpolkit-agent-1-0:amd64 (122-3) ...
7.595 Selecting previously unselected package lsb-release.
7.597 Preparing to unpack .../29-lsb-release_12.0-1_all.deb ...
7.599 Unpacking lsb-release (12.0-1) ...
7.620 Selecting previously unselected package xml-core.
7.622 Preparing to unpack .../30-xml-core_0.18+nmu1_all.deb ...
7.625 Unpacking xml-core (0.18+nmu1) ...
7.652 Selecting previously unselected package polkitd.
7.654 Preparing to unpack .../31-polkitd_122-3_amd64.deb ...
7.680 Unpacking polkitd (122-3) ...
7.712 Selecting previously unselected package packagekit.
7.715 Preparing to unpack .../32-packagekit_1.2.6-5_amd64.deb ...
7.717 Unpacking packagekit (1.2.6-5) ...
7.771 Selecting previously unselected package packagekit-tools.
7.773 Preparing to unpack .../33-packagekit-tools_1.2.6-5_amd64.deb ...
7.774 Unpacking packagekit-tools (1.2.6-5) ...
7.794 Selecting previously unselected package python-apt-common.
7.796 Preparing to unpack .../34-python-apt-common_2.6.0_all.deb ...
7.797 Unpacking python-apt-common (2.6.0) ...
7.831 Selecting previously unselected package python3-apt.
7.833 Preparing to unpack .../35-python3-apt_2.6.0_amd64.deb ...
7.834 Unpacking python3-apt (2.6.0) ...
7.861 Selecting previously unselected package python3-blinker.
7.863 Preparing to unpack .../36-python3-blinker_1.5-1_all.deb ...
7.864 Unpacking python3-blinker (1.5-1) ...
7.884 Selecting previously unselected package python3-cffi-backend:amd64.
7.886 Preparing to unpack .../37-python3-cffi-backend_1.15.1-5+b1_amd64.deb ...
7.887 Unpacking python3-cffi-backend:amd64 (1.15.1-5+b1) ...
7.911 Selecting previously unselected package python3-cryptography.
7.913 Preparing to unpack .../38-python3-cryptography_38.0.4-3_amd64.deb ...
7.914 Unpacking python3-cryptography (38.0.4-3) ...
7.973 Selecting previously unselected package python3-dbus.
7.975 Preparing to unpack .../39-python3-dbus_1.3.2-4+b1_amd64.deb ...
7.976 Unpacking python3-dbus (1.3.2-4+b1) ...
8.001 Selecting previously unselected package python3-distro.
8.002 Preparing to unpack .../40-python3-distro_1.8.0-1_all.deb ...
8.004 Unpacking python3-distro (1.8.0-1) ...
8.025 Selecting previously unselected package python3-gi.
8.027 Preparing to unpack .../41-python3-gi_3.42.2-3+b1_amd64.deb ...
8.028 Unpacking python3-gi (3.42.2-3+b1) ...
8.056 Selecting previously unselected package python3-pyparsing.
8.059 Preparing to unpack .../42-python3-pyparsing_3.0.9-1_all.deb ...
8.060 Unpacking python3-pyparsing (3.0.9-1) ...
8.085 Selecting previously unselected package python3-httplib2.
8.087 Preparing to unpack .../43-python3-httplib2_0.20.4-3_all.deb ...
8.088 Unpacking python3-httplib2 (0.20.4-3) ...
8.109 Selecting previously unselected package python3-jwt.
8.112 Preparing to unpack .../44-python3-jwt_2.6.0-1_all.deb ...
8.113 Unpacking python3-jwt (2.6.0-1) ...
8.136 Selecting previously unselected package python3-pkg-resources.
8.138 Preparing to unpack .../45-python3-pkg-resources_66.1.1-1_all.deb ...
8.139 Unpacking python3-pkg-resources (66.1.1-1) ...
8.171 Selecting previously unselected package python3-lazr.uri.
8.173 Preparing to unpack .../46-python3-lazr.uri_1.0.6-3_all.deb ...
8.175 Unpacking python3-lazr.uri (1.0.6-3) ...
8.196 Selecting previously unselected package python3-wadllib.
8.199 Preparing to unpack .../47-python3-wadllib_1.3.6-4_all.deb ...
8.200 Unpacking python3-wadllib (1.3.6-4) ...
8.224 Selecting previously unselected package python3-oauthlib.
8.226 Preparing to unpack .../48-python3-oauthlib_3.2.2-1_all.deb ...
8.227 Unpacking python3-oauthlib (3.2.2-1) ...
8.259 Selecting previously unselected package python3-six.
8.261 Preparing to unpack .../49-python3-six_1.16.0-4_all.deb ...
8.262 Unpacking python3-six (1.16.0-4) ...
8.284 Selecting previously unselected package python3-lazr.restfulclient.
8.286 Preparing to unpack .../50-python3-lazr.restfulclient_0.14.5-1_all.deb ...
8.288 Unpacking python3-lazr.restfulclient (0.14.5-1) ...
8.313 Selecting previously unselected package python3-software-properties.
8.315 Preparing to unpack .../51-python3-software-properties_0.99.30-4_all.deb ...
8.317 Unpacking python3-software-properties (0.99.30-4) ...
8.339 Selecting previously unselected package software-properties-common.
8.341 Preparing to unpack .../52-software-properties-common_0.99.30-4_all.deb ...
8.342 Unpacking software-properties-common (0.99.30-4) ...
8.388 Setting up python3-pkg-resources (66.1.1-1) ...
8.469 [Errno 13] Permission denied: '/usr/lib/python3/dist-packages/pkg_resources/pycache/init.cpython-311.pyc.140048748514448'dpkg: error processing package python3-pkg-resources (--configure):
8.476  installed python3-pkg-resources package post-installation script subprocess returned error exit status 1
8.476 Setting up libdw1:amd64 (0.188-2.1) ...
8.481 Setting up systemd-sysv (252.17-1~deb12u1) ...
8.486 Setting up python3-jwt (2.6.0-1) ...
8.553 [Errno 13] Permission denied: '/usr/lib/python3/dist-packages/jwt/pycache/init.cpython-311.pyc.139806615152048'dpkg: error processing package python3-jwt (--configure):
8.561  installed python3-jwt package post-installation script subprocess returned error exit status 1
8.561 Setting up distro-info-data (0.58) ...
8.565 Setting up libxmlb2:amd64 (0.3.10-2) ...
8.569 Setting up libpackagekit-glib2-18:amd64 (1.2.6-5) ...
8.573 Setting up libnss-systemd:amd64 (252.17-1~deb12u1) ...
8.587 dpkg: dependency problems prevent configuration of python3-lazr.uri:
8.587  python3-lazr.uri depends on python3-pkg-resources; however:
8.587   Package python3-pkg-resources is not configured yet.
8.587
8.587 dpkg: error processing package python3-lazr.uri (--configure):
8.587  dependency problems - leaving unconfigured
8.587 Setting up libunwind8:amd64 (1.6.2-3) ...
8.591 Setting up libcap2-bin (1:2.66-4) ...
8.594 Setting up python3-six (1.16.0-4) ...
8.665 [Errno 13] Permission denied: '/usr/lib/python3/dist-packages/pycache/six.cpython-311.pyc.140132822336208'dpkg: error processing package python3-six (--configure):
8.673  installed python3-six package post-installation script subprocess returned error exit status 1
8.673 Setting up gir1.2-packagekitglib-1.0 (1.2.6-5) ...
8.677 dpkg: dependency problems prevent configuration of python3-oauthlib:
8.677  python3-oauthlib depends on python3-jwt; however:
8.677   Package python3-jwt is not configured yet.
8.677
8.677 dpkg: error processing package python3-oauthlib (--configure):
8.677  dependency problems - leaving unconfigured
8.677 Setting up python3-pyparsing (3.0.9-1) ...
8.745 [Errno 13] Permission denied: '/usr/lib/python3/dist-packages/pyparsing/pycache/init.cpython-311.pyc.139741594576304'dpkg: error processing package python3-pyparsing (--configure):
8.753  installed python3-pyparsing package post-installation script subprocess returned error exit status 1
8.753 dpkg: dependency problems prevent configuration of python3-wadllib:
8.753  python3-wadllib depends on python3-lazr.uri; however:
8.753   Package python3-lazr.uri is not configured yet.
8.753  python3-wadllib depends on python3-pkg-resources; however:
8.753   Package python3-pkg-resources is not configured yet.
8.753
8.753 dpkg: error processing package python3-wadllib (--configure):
8.753  dependency problems - leaving unconfigured
8.753 Setting up libdbus-1-3:amd64 (1.14.10-1~deb12u1) ...
8.757 Setting up python3-gi (3.42.2-3+b1) ...
8.826 [Errno 13] Permission denied: '/usr/lib/python3/dist-packages/gi/pycache/init.cpython-311.pyc.139980503393840'dpkg: error processing package python3-gi (--configure):
8.834  installed python3-gi package post-installation script subprocess returned error exit status 1
8.834 Setting up systemd-timesyncd (252.17-1~deb12u1) ...
8.846 Creating group 'systemd-timesync' with GID 997.
8.847 Creating user 'systemd-timesync' (systemd Time Synchronization) with UID 997 and GID 997.
8.933 Created symlink /etc/systemd/system/dbus-org.freedesktop.timesync1.service → /lib/systemd/system/systemd-timesyncd.service.
8.933 Created symlink /etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.
8.937 Setting up python-apt-common (2.6.0) ...
8.941 Setting up libduktape207:amd64 (2.7.0-2) ...
8.945 Setting up dbus-session-bus-common (1.14.10-1~deb12u1) ...
8.949 dpkg: dependency problems prevent configuration of python3-httplib2:
8.949  python3-httplib2 depends on python3-pyparsing; however:
8.949   Package python3-pyparsing is not configured yet.
8.949
8.949 dpkg: error processing package python3-httplib2 (--configure):
8.949  dependency problems - leaving unconfigured
8.949 Setting up build-essential (12.9) ...
8.953 Setting up sgml-base (1.31) ...
8.982 Setting up libstemmer0d:amd64 (2.2.0-2) ...
8.986 Setting up lsb-release (12.0-1) ...
8.991 Setting up dbus-system-bus-common (1.14.10-1~deb12u1) ...
9.039 dpkg: dependency problems prevent configuration of python3-lazr.restfulclient:
9.039  python3-lazr.restfulclient depends on python3-httplib2 (>= 0.7.7); however:
9.039   Package python3-httplib2 is not configured yet.
9.039  python3-lazr.restfulclient depends on python3-lazr.uri; however:
9.039   Package python3-lazr.uri is not configured yet.
9.039  python3-lazr.restfulclient depends on python3-wadllib (>= 1.1.4); however:
9.039   Package python3-wadllib is not configured yet.
9.039  python3-lazr.restfulclient depends on python3-oauthlib; however:
9.039   Package python3-oauthlib is not configured yet.
9.039  python3-lazr.restfulclient depends on python3-pkg-resources; however:
9.039   Package python3-pkg-resources is not configured yet.
9.039  python3-lazr.restfulclient depends on python3-six; however:
9.039   Package python3-six is not configured yet.
9.039
9.039 dpkg: error processing package python3-lazr.restfulclient (--configure):
9.039  dependency problems - leaving unconfigured
9.039 Setting up libpam-cap:amd64 (1:2.66-4) ...
9.091 debconf: unable to initialize frontend: Dialog
9.091 debconf: (TERM is not set, so the dialog frontend is not usable.)
9.091 debconf: falling back to frontend: Readline
9.097 debconf: unable to initialize frontend: Readline
9.097 debconf: (This frontend requires a controlling tty.)
9.097 debconf: falling back to frontend: Teletype
9.141 Setting up iso-codes (4.15.0-1) ...
9.145 Setting up dbus-bin (1.14.10-1~deb12u1) ...
9.149 Setting up libpolkit-gobject-1-0:amd64 (122-3) ...
9.153 Setting up libgstreamer1.0-0:amd64 (1.22.0-2) ...
9.157 Setcap worked! gst-ptp-helper is not suid!
9.159 Setting up python3-cffi-backend:amd64 (1.15.1-5+b1) ...
9.163 Setting up python3-blinker (1.5-1) ...
9.230 [Errno 13] Permission denied: '/usr/lib/python3/dist-packages/blinker/pycache/init.cpython-311.pyc.140698286319024'dpkg: error processing package python3-blinker (--configure):
9.238  installed python3-blinker package post-installation script subprocess returned error exit status 1
9.238 Setting up python3-dbus (1.3.2-4+b1) ...
9.308 [Errno 13] Permission denied: '/usr/lib/python3/dist-packages/dbus/pycache/init.cpython-311.pyc.140399567316400'dpkg: error processing package python3-dbus (--configure):
9.315  installed python3-dbus package post-installation script subprocess returned error exit status 1
9.315 Setting up python3-distro (1.8.0-1) ...
9.383 [Errno 13] Permission denied: '/usr/lib/python3/dist-packages/distro/pycache/init.cpython-311.pyc.140612260734384'dpkg: error processing package python3-distro (--configure):
9.391  installed python3-distro package post-installation script subprocess returned error exit status 1
9.391 Setting up python3-apt (2.6.0) ...
9.461 [Errno 13] Permission denied: '/usr/lib/python3/dist-packages/apt/pycache/init.cpython-311.pyc.140410134209968'dpkg: error processing package python3-apt (--configure):
9.469  installed python3-apt package post-installation script subprocess returned error exit status 1
9.469 Setting up dbus-daemon (1.14.10-1~deb12u1) ...
9.482 Setting up libappstream4:amd64 (0.16.1-2) ...
9.486 dpkg: dependency problems prevent configuration of software-properties-common:
9.486  software-properties-common depends on python3-dbus; however:
9.486   Package python3-dbus is not configured yet.
9.486  software-properties-common depends on python3-gi; however:
9.486   Package python3-gi is not configured yet.
9.486
9.486 dpkg: error processing package software-properties-common (--configure):
9.486  dependency problems - leaving unconfigured
9.486 Setting up appstream (0.16.1-2) ...
9.504 ✔ Metadata cache was updated successfully.
9.507 dpkg: dependency problems prevent configuration of python3-software-properties:
9.507  python3-software-properties depends on python3-apt; however:
9.507   Package python3-apt is not configured yet.
9.507  python3-software-properties depends on python3-gi; however:
9.507   Package python3-gi is not configured yet.
9.507  python3-software-properties depends on python3-lazr.restfulclient; however:
9.507   Package python3-lazr.restfulclient is not configured yet.
9.507
9.507 dpkg: error processing package python3-software-properties (--configure):
9.507  dependency problems - leaving unconfigured
9.507 Setting up python3-cryptography (38.0.4-3) ...
9.580 [Errno 13] Permission denied: '/usr/lib/python3/dist-packages/cryptography/pycache/about.cpython-311.pyc.140116343704720'dpkg: error processing package python3-cryptography (--configure):
9.588  installed python3-cryptography package post-installation script subprocess returned error exit status 1
9.588 Setting up dbus (1.14.10-1~deb12u1) ...
9.610 invoke-rc.d: could not determine current runlevel
9.614 invoke-rc.d: policy-rc.d denied execution of start.
9.616 Setting up xml-core (0.18+nmu1) ...
9.746 Setting up libpam-systemd:amd64 (252.17-1~deb12u1) ...
9.797 debconf: unable to initialize frontend: Dialog
9.797 debconf: (TERM is not set, so the dialog frontend is not usable.)
9.797 debconf: falling back to frontend: Readline
9.803 debconf: unable to initialize frontend: Readline
9.803 debconf: (This frontend requires a controlling tty.)
9.803 debconf: falling back to frontend: Teletype
9.847 Setting up libpolkit-agent-1-0:amd64 (122-3) ...
9.851 Setting up dbus-user-session (1.14.10-1~deb12u1) ...
9.858 Processing triggers for libc-bin (2.36-9+deb12u3) ...
9.887 Processing triggers for sgml-base (1.31) ...
9.898 Setting up polkitd (122-3) ...
9.908 Creating group 'polkitd' with GID 996.
9.908 Creating user 'polkitd' (polkit) with UID 996 and GID 996.
9.938 invoke-rc.d: could not determine current runlevel
9.941 invoke-rc.d: policy-rc.d denied execution of reload.
10.02 start-stop-daemon: unable to stat /usr/libexec/polkitd (No such file or directory)
10.03 Setting up packagekit (1.2.6-5) ...
10.04 invoke-rc.d: could not determine current runlevel
10.05 invoke-rc.d: policy-rc.d denied execution of force-reload.
10.05 Failed to open connection to "system" message bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
10.13 Created symlink /etc/systemd/user/sockets.target.wants/pk-debconf-helper.socket → /usr/lib/systemd/user/pk-debconf-helper.socket.
10.13 Setting up packagekit-tools (1.2.6-5) ...
10.13 Processing triggers for dbus (1.14.10-1~deb12u1) ...
10.15 Errors were encountered while processing:
10.15  python3-pkg-resources
10.15  python3-jwt
10.15  python3-lazr.uri
10.15  python3-six
10.15  python3-oauthlib
10.15  python3-pyparsing
10.15  python3-wadllib
10.15  python3-gi
10.15  python3-httplib2
10.15  python3-lazr.restfulclient
10.15  python3-blinker
10.15  python3-dbus
10.15  python3-distro
10.15  python3-apt
10.15  software-properties-common
10.15  python3-software-properties
10.15  python3-cryptography
10.16 E: Sub-process /usr/bin/dpkg returned an error code (1)

failed to solve: process "/bin/sh -c apt-get update && apt-get install -y     build-essential     curl     software-properties-common     && rm -rf /var/lib/apt/lists/*" did not complete successfully: exit code: 100

If you installed Docker through Snap there is a chance you are experiencing this bug : https://forums.docker.com/t/bug-on-apt-install-permission-denied/100196
If this is the case you can either install Docker without Snap (https://docs.docker.com/engine/install/ubuntu/) or you can change the daemon.json as explained in the forum link.

If you installed Docker through Snap there is a chance you are experiencing this bug : https://forums.docker.com/t/bug-on-apt-install-permission-denied/100196
If this is the case you can either install Docker without Snap (https://docs.docker.com/engine/install/ubuntu/) or you can change the daemon.json as explained in the forum link.

Wonderful pointer @matthieuml  Thank you. Ditching snap and installing per docker with he vfs for storage vs overlay2 did get this running. (But ollama doesn't seem to reliably communicate and everything is too slow without a GPU). I'll close this and check other issue threads as necessary. TY


Force python2 when running test262

The test262 python script is not python 3 compatible
so we force it to be executed with python2.
Additionally print out the reason if the execution
failed.
JerryScript-DCO-1.0-Signed-off-by: Peter Gal<EMAIL_ADDRESS>

LGTM


:sparkles: Add get raw HTML element

Changes :

Add HTML field in HTMLElement struct that contain raw html element given

Notes :

No error test coverage on

html, err := goquery.NewDocumentFromNode(n).Html()
	if err != nil {
		log.Println("err on get html from node, ", err)
	}
`

Thanks for your contribution.
You can use HTMLElement.DOM.Html() to get the selection's raw HTML content. It has error handling and it is more efficient (it doesn't allocate memory for the HTML content in every element). As I see this is a redundant functionality so closing.

I'm sorry that I didn't know that i can use HTMLElement.DOM.Html() before. that's why i try to create this PR. any way thanks for your response @asciimoo :+1:


Run cpplint in quiet mode

Removes lots of
Done processing ...

spam from cpplint logs.
cc @driazati

also cc @tqchen due to related dmlc-core change.

:/ i think maybe the rust build is busted when dlpack is updated.

#10897 also gets rid of the output

blocked on https://github.com/dmlc/dmlc-core/pull/658#pullrequestreview-949205382

busted copy constructor was reverted for now, retrying this one


[Circletracer] add dependency to package

Add flatbuffers and dependency files.
ONE-vscode-DCO-1.0-Signed-off-by: Seunghyun Kang<EMAIL_ADDRESS>

from draft #179
from issue #66.

Please resolve check-format failure.

Please resolve check-format failure.

Checking format.patch, there is no problem other than adding the package contents while adding flatbuffers. Are there any other issues I'm missing out on?

Please check Details link and look at the format.patch file

Please check Details link and look at the format.patch file

I confirmed with the team that there was nothing wrong with npm7. Perhaps it is because the npm version of the format checker is 6.

Interesting... the format.patch includes reverting all the changes in this PR @.@ (Except package.json)

This is script to run check format in CI
  check-format:
    runs-on: ubuntu-20.04

    steps:
      - uses: actions/checkout@v2
      - uses: actions/setup-node@v2
        with:
          node-version: '12'

node version 12 be the reason?

I've reopened #21

If the npm version is lower, it is recommended to manually update it because there are security issues. In general, there is an npm version that is automatically installed for each nodejs, but we update it manually.
There are two workarounds.

Update the format checker's npm
npm i -g npm

I lower the npm version to version 6 and modify the code as required by the format checker.

what would be better?

I lower the npm version to version 6 and modify the code as required by the format checker.
what would be better?

As to land this change, this would be faster :)

As to land this change, this would be faster :)

Done. Thank you :)


add docker file cheat-sheet

Structure will be changed to give some high-level understanding of docker and improve the documentation when it comes to docker cli and file


Component library graphic on mobile (on home)

The component library graphic on smaller phone sizes (Pixel 3a) looks funky:

This seems to be fixed already.

This looks good to go, checked on my Pixel 3a. Apologies for the delay. I saw this was still open.

I see this is marked as done. Can we close it @kmbrlygl ?

@chachasikes yes!


Remove unnecessary folders/files

It's not necessary.

Thanks for pointing this out - I had planned to do so but totally forgot


Alfred Workflow to search Good Links by tag

Thanks for the Add To Good Links workflow.
It made me wonder, have you by chance developed an Alfred Workflow to search Good Links by tag, and not yet posted it here?

No, I haven't made a search workflow. You're welcome for the existing workflow though! Have a nice day!

So far, I've got as far as this working ZSH script...
listGoodLinksTags() {
  DB_PATH="$HOME/Library/Group Containers/group.com.ngocluu.goodlinks/Data/data.sqlite"
  sqlite3 "$DB_PATH" "SELECT DISTINCT tags FROM link" | tr ' ' '\n' | sort -u
}

Better, but not yet using Alfred...

openGoodLinksTag() {
  DB_PATH="$HOME/Library/Group Containers/group.com.ngocluu.goodlinks/Data/data.sqlite"
  TAGS=$(sqlite3 "$DB_PATH" "SELECT DISTINCT tags FROM link" | tr ' ' '\n' | sort -u)
  TAG="$(echo $TAGS | fzf)"
  URL="goodlinks://x-callback-url/tag?name=$TAG"
  open "$URL"
}

Almost there.
Here's what I have:

But when I type "gl agile" in the Alfred launcher and press return, it just wants to search Google for the phrase "gl agile".

I revised the script filter to provide what looks like valid output:
DB_PATH="$HOME/Library/Group Containers/group.com.ngocluu.goodlinks/Data/data.sqlite"

TAGS=$(
  sqlite3 "$DB_PATH" "SELECT DISTINCT tags FROM link" \
    | sort -u \
    | xargs printf "{ \"title\": \"%s\", \"subtitle\": \"Open tag in GoodLinks\", \"arg\": \"%s\" },"
)

echo "{\"items\": [$TAGS]}" | sed 's/\(.*\),/\1 /'

(Or echo "{\"items\": [$TAGS]}" | sed 's/\(.*\),/\1 /' | jq for debugging)


MINOR: Various cleanups in clients tests

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Thanks for the reviews! Test failures are not related, merging to trunk


add trivy_exposedsecrets_info metric with discovered secrets details

Description
Adding a new metric: trivy_exposedsecrets_info that provides details about discovered secrets
The metric exposes the following labels (in addition to the base set):

secret_category
secret_rule_id
secret_target
secret_title

Related issues

Close #998

Remove this section if you don't have related PRs.
Checklist

[x] I've read the guidelines for contributing to this repository.
[x] I've added tests that prove my fix is effective or that my feature works.
[x] I've updated the documentation with the relevant information (if needed).
[x] I've added usage information (if the PR introduces new options)
[ ] I've included a "before" and "after" example to the description (if the PR is a user interface change).

note I didn't change anything in Chart.yaml which I assume would be taken care of when a new release is prepped, but the chart was updated to support the new configuration flag and env variable.

Hey @chen-keinan 👋 this is ready for review 🙏🏼

@dkulchinsky thanks , will review it later on

@dkulchinsky  pr is looking good , I have added one comment

lgtm 🚀


Use Objects to handle Issues and ArchReport

Also gitignore .swp files

Please split commits for the .gitignore change and the rest
please use lower case names in git commit subject line
Call the flake8 check and correct it

Rebased and fixed.


Define a global for reconciler.DefaultTimeout.

Serving currently uses a fixed constant for the context timeout on reconciliation, which is causing some bad interactions with certain policy webhooks.
Based on feedback on https://github.com/knative/serving/pull/13323 I am hoisting this into a shared variable, so that folks can turn it into a flag, so it is configurable.

/assign @vaikas

... and the kitchen sink grows. 😁


Include best practices for sharing code?

I was immediately curious how users share with each other.
Perhaps for now the best practice is sharing via github. Any package registry (even if a simple list)?

One day we'll have a package manager for Ada and SPARK :)
Until then, yes I think github is a good starting point. There is an active community on comp.lang.ada - you can also follow twitter accounts like @adaprogrammers.


Using toolchain config file instead of cmd rustup default nightly and fix i32 overflow

Using rust-toolchain.toml allows you to set the nightly toolchain for a project rather than globally.
And
Fix the i32 overflow issue.

This would close #25
Not sure if there was another issue for this. The error mentioned here is not the error I got, but does solve it with just the toolchain config file.


[FLINK-10298] [JobManager] Batch Job Failover Strategy

What is the purpose of the change
The new failover strategy needs to consider handling failures according to different failure types. It orchestrates the batch job failover logic in onTaskFailure method of the FailoverStrategy interface, with the logic inline:
public void onTaskFailure(Execution taskExecution, Throwable cause) {
    //1. Get the throwable type

    //2. If the type is NonRecoverableError fail the job

    //3. If the type is PatritionDataMissingError, do revocation

    //4. If the type is EnvironmentError, do check blacklist

    //5. Other failure types are recoverable, but we need to remember the count
     of the failure

    //6. if it exceeds the threshold, fail the job

}
Brief change log

*Add a configuration MAX_ATTEMPTS_EXECUTION_FAILURE_COUNT, the default value is 6 *
Add a failure counter in the failed region
**

Verifying this change
This change added tests and can be verified as follows:

Added Tests to validate job fail immediately and not restart if meet a NoRecoverableError
*Added a test to validate job fail after MAX_ATTEMPTS_EXECUTION_FAILURE_COUNT times if meet a RecoverableError"
Added BatchJobFailoverStrategy that inherited from RestartPipelinedRegionStrategy

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

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no )
The runtime per-record code paths (performance sensitive): (no )
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no )
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (yes )
If yes, how is the feature documented? (document)

Closing this ticket as abandoned.


⚠ Ixtanet SAT has degraded performance

In ba1be47, Ixtanet SAT ($MEDIA_SAT) experienced degraded performance:

HTTP code: 200
Response time: 20693 ms

Resolved: Ixtanet SAT performance has improved in b0c2212 after 291 days, 1 hours, 4 minutes.


Create helper function to initialize Dialogflow CX options

Dialogflow uses regional endpoints and requires the authority to match the target endpoint:
We need something like this:
namespace gc = google::cloud;
auto DefaultOptions(std::string const& region) {
  return   gc::Options{}
          .set<gc::EndpointOption>(region + "-dialogflow.googleapis.com")
          .set<gc::AuthorityOption>(region + "-dialogflow.googleapis.com");
}

We don't need the helper function for setting the EndpointOption now. You can pass the location directly to one of the MakeFooConnection() functions instead.


View authors page

List the authors added from #15

I'd love to help you out with your project, I will get it running on my machine and then start working on this issue.


Database Diagramming

The diagram under https://docs.microsoft.com/en-us/azure/sql-database/sql-database-design-first-database#create-tables-in-the-database showing how the tables link to each other would be very useful.  Is there a way in the product to produce this for a database or is it just artwork for this tutorial?

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

ID: 5802ba59-8c08-7b41-7aec-2640cc287ae3
Version Independent ID: 13c04835-76a2-96bc-01ad-1c0dcdf65cb0
Content: Tutorial: Design your first Azure SQL database using SSMS
Content Source: articles/sql-database/sql-database-design-first-database.md
Service: sql-database
GitHub Login: @CarlRabeler
Microsoft Alias: carlrab

@JohnBoncek Thanks for the feedback! We are currently investigating and will update you shortly.

@JohnBoncek This capability is part of SQL Server Management Studio. While connected to the database you wish to have a diagram created, follow these steps:
If this is the first time you are using Database Diagrams, create the necessary system objects.

Next right-click on Database Diagrams and Select Create New.

Add the desired tables.

Close the Add Tables dialoge box.

Database Diagram created.

You will need an installation of SSMS and an Azure SQL Database instance to connect to and create a database diagram for. Please let me know if you have any additional questions. Regards, Mike

Excellent.  Thank you!

@JohnBoncek Correct! The screen capture of the database diagram I included here is 'as-built' by the database diagram functionality. I could have moved the tables around to make it match the image in the documentation. If there are no additional questions, I am going to move to close this out. If you should have any additional questions, feel free to reopen this dialog and we can continue the discussion. Regards, Mike


Add redis specific session tests

This adds a few session specific test to make sure the redis session handler returns the correct session handler.
I was also thinking it might be best to add a Redis specific domain for testing specific get set. Though I am going to write cache tests as a separate PR that would test get set anyway.
This test fails because redisArray password isnt passed see - https://github.com/concrete5/concrete5/pull/8162

Not sure the best way forward on this since the tests aren't passing.

There was a couple of issues with the travis build
First was the redis server setup was incorrect.
I fixed the issue by correct the server setup.
The 2nd is to do with phpredis v5.0.0 and above, when using ping with a password it causes a segfault - https://github.com/phpredis/phpredis/issues/1658
I've fixed this by ignoring testing ping on phpredis versions 5.0.0 to 5.0.9. Ive added testing for 5.1.0RC2 on the php7.3 branch until 5.1.0 is released next week roughly

Looks good to me, gonna have @KorvinSzanto take a look at this one

Unless there's a good reason for these I say we do not include it in our unit testing suite, the tests are already slow as it is and this is only testing if the PHP extension is working, which IMO we can just assume is the case.
https://github.com/concrete5/concrete5/pull/8397#issuecomment-585314102

To be honest, I can change this to mocks, and remove the redis server.
I just prefer to test on real, but i understand the speed considerations. So i'll add in a mock and remove the actual redis parts. Its mainly checking that it connects to the server using our configuration loader and with/without a password


Worth making shell scripts npm scripts?

Hey just wondering why the shell scripts are needed when they could be npm scripts?
Happy to fire through a PR?
Cheers,
Otis.

I remove scripts from package.json recently, cuz I think they are too long to maintain in a single file. But it can not cross-platform.
Any ideas? PR welcome of course!


[FEATURE] Handling TFRecords

🚨🚨 Feature Request

[ ] Related to an existing Issue
[x] A new implementation (Improvement, Extension)

Is your feature request related to a problem?
There is no opinionated way on how TFRecords should play with Hub.
If your feature will improve HUB
Treating TFRecords as if its a first class data type would reduce friction. Currently, users (like me) unpack TFRecords into str before pushing to Hub.

I would like to  work on this issue if no one is already working on it

Great! Assigning you to it

@mynameisvinn @AbhinavTuli, so essentially, what we want is TFRecords to be a Hub supported Data Format. Like Hub already has ClassLabels() to store labels, should I make a similar class that handles TFRecords?

@DebadityaPal exactly, we want TFRecords to be a first class schema. I believe you're familiar with TFRecords while digging through benchmarking :-)

Yep! I shall get it done

I  was working  with TFRecords and I came across a doubt. TFRecords can store multiple key-value pairs inside them and they have a schema of their own. So while implementing TFRecords as a datatype for hub, should I set a constraint to only allow one key-value pair inside each TFRecords object? Or should it be such that a single TFRecords object can store multiple fields?
Or another option would be to store the raw binary byte string and then have functions to extract the data from that using underlying tensorflow function calls when the user needs to.
Any inputs from the community  would be greatly appreciated.

I don't think we should constrain to a single key value pair. For example, AudioSet, a popular dataset, has multiple fields.
Can you show an example of a function that deserializes a tfrecord, where there is random access?

I don't have much experience working with TFRecords, so the way I  usually deserialize it is I create a dataset object from the tfrecords file and use a parsing function.
dataset = tf.data.TFRecordDataset(filename)
dataset = dataset.shuffle().repeat()
dataset = dataset.map(parse_func)
dataset = dataset.batch()

Something like this.

We might have a problem ahead. Currently, after the TF 2.0 update, The TFRecordReaders have been deprecated and the recommended way to read TFRecord files is by using the TFRecordDataset class in the tf.data  API. Upon reading a bit, I found out that TensorFlow datasets might not support random access. This might cause a conflict with the way hub works right now.

@DebadityaPal That's really unfortunate. I think we have already had issues with TF 2.4 compliance. When did TFRecordReaders become deprecated? Was it before TF 2.3.1? @mynameisvinn will probably help you here

In their docs, I have found the TFRecords Reader twice.

tf.compat.v1.TFRecordsReader : Problem with this is it is deprecated in all versions  of TF 2. Does not support eager execution.
tf.raw_ops.TFRecordsReader : Couldn't find proper documentation for this, really hard to read and properly understand its current docs as not much is written, also does not support eager execution.

I went through the TF documentation and found it unhelpful too. I prefer moving forward with >=TF 2.0 so we're not wasting time solving compatibility issues.

Closing this feature request due to inactivity and lack of interest. Will revive it if more users request it.


Training refactoring

As described in #296, simplifying the training script to make it clear what is happening.

Moved model and optimiser configuration to its own files.
Created function for gamma/beta annealing configuration, and moved it to its own file.
Moved pass_batch functionally back to train.py and evaluation.py as it can be a bit confusing to see what is happening if is not explicit in the batch loop.
Aesthetic changes to make train.py script shorter.
Renamed variables for further clarity (e.g input_size to input_shape).
Added missing doctrings.
Updated readme with the latest configuration option and some aesthetic changes for readability (a lot more changes are needed to the README).

@jolaem would it be ok to merge this PR?

I'll merge this now as is stopping further progress.


Best way to import large objects?

I am migrating from another search service to elastic search on an app. I have defined the index (20 fields, 10 nested multilevel objects) and when I try to index, I am getting a stack level too deep error. I am using grape entities to serialise the json for the nested models (some of them also contain dynamic field names) like this:
field :the_model, type: 'object', value: ->{ TheModel::Entity.represent(the_model).as_json }

Have looked on stack overflow, but since there is nothing on there, I decided to post here. I know that it is because of the depth of the objects, because when I remove a couple, the error goes away.
Am using the latest version of chewy, with grape and grape entities, and running locally.

You probably have to find out where the exact error happens because it seems like it happens in your code, outside of chewy


[API Page Generation] ContentChild Apit doc page is empty

The page https://angular.io/docs/ts/latest/api/core/index/ContentChild-decorator.html of the API documentation is empty, it should contain this: https://github.com/angular/angular/blob/2.0.0/modules/%40angular/core/src/metadata/di.ts#L232-L270
ContentChildren (which is in the same file) works fine: https://angular.io/docs/ts/latest/api/core/index/ContentChildren-decorator.html

This  is because the source code docs are in the wrong place.
See this commit for a similar fix by @vsavkin for ContentChildren https://github.com/angular/angular/commit/b6287ccc5126da9c1a052bd28b3a9e2743f67eae


Remove unused files before archiving build dir

The archive step of build_all job uses up almost all RAM disk space. In addition to enlarging the RAM disk, we can also remove the unused files before the archive step.
This only takes 1s to run and saves about 10G disk space for the following archive step:
Filesystem      Size  Used Avail Use% Mounted on
tmpfs            50G   35G   16G  69% /runner-root

Tar has another option called --remove-files . It seems like tar will delete the processed files during the archiving. But I think this is overkill as when we unarchive the build-dir.tar it will still take the space of tar size + unarchived build dir. So even we successfully finish build_all, the following jobs might run out of space when unarchiving.

https://github.com/iree-org/iree/pull/10725 the LLVM bump seems to work with this change. I'd wait for the review from @GMNGeoffrey