Unable to open Graph Explorer for cosmos graph db

Does this occur consistently? Yes
Repro steps:

Add database connection for azure cosmos graph db with gremlin api
Double click the graph to open graph explorer

Version: 0.18.1
OS: win32
OS Release: 10.0.19043
Product: Visual Studio Code
Product Version: 1.64.2
Language: en
Even after installing the extension trying to open  Graph Explorer throws a popup saying install the extension

Hi @shaik-suhail
We actually deprecated the Graph Explorer extension back in 2020-09-18.  We recommend using the portal to visualize your graph data.
If you would really like to use VS Code for data visualization, you can manually install the vsix from here: https://github.com/microsoft/vscode-cosmosdbgraph/releases
Thanks for filing the issue and using the extension!


Pasting text into body doesn't trigger a change

In Chrome, if I copy paste text and that's it, the ng-model isn't updated with the new value. It's like the component is only changing on key press. But if I just hit the spacebar or whatever, it updates properly.
Edit: Clarifying process to reproduce

With a new, empty text field, click in the field.
Paste some text (I was using ctrl + v). It's very important to not hit any other keys while the text field is still selected as this will "fix" the issue.
Click away from the text field and inspect the variable data bound to it. It should still be undefined/empty

any updates?

My apologies on the delay. Work has been crazy busy. I was able to successfully reproduce on safari and firefox.

I've updated the original comment with a more clear procedure to reproduce.

should be fixed in 4.2.0


Permission improvements of the submission archive feature

Here are some issue with the current implementation:

[ ] All staff can archive an submission, if they then do not have permission to view archived submission they get a 403. If they should be able to do this a redirect would be nicer.
[ ] Should all staff be able to archive a submission?
[ ] Be default no one can see archived submission, SUBMISSIONS_ARCHIVED_ACCESS_STAFF and SUBMISSIONS_ARCHIVED_ACCESS_STAFF_ADMIN are both false be default. Either super admins should have access or SUBMISSIONS_ARCHIVED_ACCESS_STAFF_ADMIN should default to true.
[ ]  Should we show on archived submission who can access them, maybe in the red border add info if staff or staff admins only can see this?

Might make sense for me to wrap these into #3646, four birds one stone. After talking with @Techslammer it seems like it'd be best for OTF's workflow if the only role that could make & access archives would be Staff Admin. @frjo what are your thoughts on that?

I think it makes sense for the default to be that Staff Admins can archive and see archived submissions. Then we have settings that can be turned on that allow staff to do the archiving and see the archives.
So default settings like these, two new added and two renamed for clarity:
SUBMISSIONS_ARCHIVED_VIEW_ACCESS_STAFF = False
SUBMISSIONS_ARCHIVED_VIEW_ACCESS_STAFF_ADMIN = True
SUBMISSIONS_ARCHIVE_ACCESS_STAFF = False
SUBMISSIONS_ARCHIVE_ACCESS_STAFF_ADMIN = True

By settings all to false an organisation can then turn off the feature if they want.
Feel free to improve the settings names!

All of this sounds great! What did you have in mind for the redirects? In my current implementation I just have it redirect the user to the submission list page. Should we have a dedicated view for any permission denied?


Deleting cycle of installations

How to categorize this issue?
/kind bug
/priority normal
What happened:
We have two installations which depend on each other. Each of them imports an export parameter of the other. The installations are in phase PendingDependencies for some time and switch then to phase Failed ("unable to get data object..."). Then we try to delete both installations, but the installations remain there.
What you expected to happen:
It should be possible to delete the installations.

Ah, I always wanted to say that: It's not a bug, it's a feature!
As @schrodit mentioned here, an installation that is depended on by another installation cannot be deleted.
The problem that you saw probably also comes from the cyclic dependency - both installations are waiting for the other installation to finish before updating themselves ... which will never happen.
I think we don't support cyclic dependencies between installations in general. @schrodit correct me, if I'm wrong.

We are facing a similar problem. If one helm deployItem out of four fails, we are not able to delete the installation.
Only the successful deployItems get deleted.
After the installation:
NAME                                                                    TYPE                                            PHASE       EXPORTREF   AGE
deployitem.landscaper.gardener.cloud/c21s-control-prerequisites-5t2qf   landscaper.gardener.cloud/helm                  Succeeded               35s
deployitem.landscaper.gardener.cloud/c21s-controller-q4sxq              landscaper.gardener.cloud/helm                                          35s
deployitem.landscaper.gardener.cloud/c21s-crds-6hdzx                    landscaper.gardener.cloud/helm                  Succeeded               35s
deployitem.landscaper.gardener.cloud/c21s-create-namespace-kj74g        landscaper.gardener.cloud/kubernetes-manifest   Succeeded               35s

NAME                                       PHASE         EXPORTREF   AGE
execution.landscaper.gardener.cloud/c21s   Progressing               35s

NAME                                          PHASE         CONFIGGEN   EXECUTION   AGE
installation.landscaper.gardener.cloud/c21s   Progressing               c21s        42s

After the deletion of the installation:
NAME                                                         TYPE                             PHASE   EXPORTREF   AGE
deployitem.landscaper.gardener.cloud/c21s-controller-q4sxq   landscaper.gardener.cloud/helm                       4m19s

NAME                                       PHASE      EXPORTREF   AGE
execution.landscaper.gardener.cloud/c21s   Deleting               4m19s

NAME                                          PHASE      CONFIGGEN   EXECUTION   AGE
installation.landscaper.gardener.cloud/c21s   Deleting               c21s        4m26s

I agree with the cyclic dependencies (as mentioned in this comment), so we should not allow those.

Wouldn't a suitable follow-up be that we check for cyclic dependencies during designtime, so that the error not being able to delete installations if there is a cyclic dependency will never happen again ?

What about the second issue in this task ? If one Helm deployItem out of 4 fails, the whole installation can not be deleted ? I feel that we can (and have to) improve our tools here.

I agree with the cyclic dependencies (as mentioned in this comment), so we should not allow those.
Wouldn't a suitable follow-up be that we check for cyclic dependencies during designtime, so that the error not being able to delete installations if there is a cyclic dependency will never happen again ?

yes we are able to determine cyclic dependencies and should directly fail the aggregated installation or all involved root installations.

What about the second issue in this task ? If one Helm deployItem out of 4 fails, the whole installation can not be deleted ? I feel that we can (and have to) improve our tools here.

not sure why we are unable to delete it. but it should be possible to delete a failed helm deploy item.
Are there steps to reproduce the issue (because I currently do not see why it shouldn't work)?

@In-Ko closed because outdated and/or copied into internal project


is Java APM support officially supported?

Not finding it in this list ..

but I found this project, so I am wondering, if this is something we can test out

Hi @mjobin-mdsol , thanks for your interest! Unfortunately Raygun's APM product does not yet support Java, but we've recorded your request for this.
Raygun4java is for our Crash Reporting product, not APM.


[BUG] scale is 0.

Describe the bug
A clear and concise description of what the bug is.
Have you run the unit tests?

[x] Yes
[] No --- then this issue will be closed.

Installed Dependencies
Please report the versions of all dependencies you installed, as well as your OS.
To Reproduce
Please post the exact steps you executed to reproduce the bug.
Additional context
Add any other context about the problem here.
I used my own data set and used scale estimation. I entered my own feature matching pairs for teaser++, and finally the scale estimated by teaser++ was 0 and the rotation matrix was np.ones((1,1,1)). I wanted to know if the feature matching pairs I used were not correct enough. Thank you in advance.

It seems like the rotation noise bound set is infinite, which should not occur. Did you explicitly set the parameters for the solver when you use the Python API?

If there are no further questions, we will close the issue. Thx!


Can't pass negative values for  START_X or START_Y

Running MinecraftLandGenerator-3.1.0.jar with these arguments:
auto-spawnpoints -6250 -6250 12500 12500
results in this error:
Missing required parameters: WIDTH, HEIGHT
I'm not familiar with this code but I think it's intended behavior by the command line parser: https://github.com/remkop/picocli/issues/446
I've tried in both Ubuntu and Windows 10 and the result is the same.

Yes, this is "intended" behaviour. You should be able to work around it with auto-spawnpoints -- -6250 -6250 12500 12500. I'll have a look at it, CommandLine.setUnmatchedOptionsArePositionalParams(true) seems like a better solution in the long run.

@m2xcomcastnet Please try out latest master if you can, and tell me if it's better.

@m2xcomcastnet Please try out latest master if you can, and tell me if it's better.


Readme Typo

I'm not sure if you prefer an Issue or a pull request for something so trivial, but the second code snippet in the readme file is missing Section in the import statement.
from st_pages import Page, show_pages, add_page_title

add_page_title() # By default this also adds indentation

# Specify what pages should be shown in the sidebar, and what their titles and icons
# should be
show_pages(
    [
        Page("streamlit_app.py", "Home", "🏠"),
        Page("other_pages/page2.py", "Page 2", ":books:"),
        Section("My section", icon="🎈"),
        # Pages after a section will be indented
        Page("Another page", icon="💪"),
    ]
)

should have
from st_pages import Page, Section, show_pages, add_page_title

Thanks, @MathCatsAnd! I'll just go ahead and fix that.


Create the footer using tailwind css

…in external CSS stylesheet were replaced with Tailwind CSS classes. The code to import the external stylesheet was commented to prevent style conflicts.
Purpose

The purpose of this PR is to develop the footer of the website and replace the Antd styles with Tailwind CSS which is a part of fixing issue #50.
Goals
Tailwind classes were used to enhance efficiency and readability and the structure.
Approach
The CSS flexbox was used and Tailwind CSS classes were used to achieve the Antd styles. The code to import the external stylesheet was commented to prevent conflicts in styles and to be used if required.
Screenshots

Checklist

[X ] This PR doesn't commit any keys, passwords, tokens, usernames, or other secrets.
[X ] I have read and understood the development best practices guidelines ( http://bit.ly/sef-best-practices )
[X ] My code follows the style guidelines of this project
[X ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation

Related PRs
Test environment
Learning

Hi, @mayura-andrew ,  I fixed the ESLint errors, but the ESLint check still fails.

Hi, @mayura-andrew , I fixed the ESLint errors, but the ESLint check still fails.

@vishwaikon Run npm run lint and see the lint errors should be shown there

@mayura-andrew . I ran the command already and fixed the displayed issues for the new files and fixed. Now when run the command shows 10 errors from external files. I'll recheck if I have to fix the configurations.


Possible panic in public function mem::elts

Hi. When T is a zero-sized type, function mem::elts<T> would panic because of the remainder operation bits % width.
Probably this function should have private visibility if it is not intended to be exposed to users.

This is required to have pub visibility so that it can be used in macros. It is not public API, as evinced by #[doc(hidden)].
const fns cannot take trait bounds at this time; this function is only called on non-ZST types, so I have never added checks for ZST behavior. However, since const fn supports branching, I am able to add a check to avoid computations on ZST. As a compile-time check, adding such a branch imposes no cost and is therefore the right thing to do.


Flask Oauth2 Auth Server: Error trying to decode a non urlencoded string. But it was encoded in the request

authlib.flask.oauth2.authorization_server._create_oauth2_request inits OAuth2Request() with q.url, which ends up not keeping percent-encoding for spaces (so instead of the %20 from the url, it becomes an actual space  ). q being a Flask request in the context of that function.
Issue shows up when passing scope=openid%20user or the like.
GET {{ROOT}}/oauth2/authorize?response_type=code&client_id={{CLIENT_ID}}&redirect_uri={{REDIRECT}}&scope=openid%20user
Trace:
Traceback (most recent call last):
  File "virtual-env/local/lib/python2.7/site-packages/flask/app.py", line 1475, in full_dispatch_request
    rv = self.dispatch_request()
  File "virtual-env/local/lib/python2.7/site-packages/flask/app.py", line 1461, in dispatch_request
    return self.view_functions[rule.endpoint](**req.view_args)
  File "{{OUR_APP}}", line 83, in authorize
    grant = server.validate_consent_request(end_user=user)
  File "virtual-env/local/lib/python2.7/site-packages/authlib/flask/oauth2/authorization_server.py", line 208, in validate_consent_request
    req = _create_oauth2_request(request)
  File "virtual-env/local/lib/python2.7/site-packages/authlib/flask/oauth2/authorization_server.py", line 274, in _create_oauth2_request
    q.headers
  File "virtual-env/local/lib/python2.7/site-packages/authlib/specs/rfc6749/wrappers.py", line 39, in __init__
    self.query_params = url_decode(self.query)
  File "virtual-env/local/lib/python2.7/site-packages/authlib/common/urls.py", line 64, in url_decode
    raise ValueError(error % (set(query) - urlencoded, query))
ValueError: Error trying to decode a non urlencoded string. Found invalid characters: set([u' ']) in the string: 'response_type=code&client_id={{CLIENT_ID}}&redirect_uri={{REDIRECT}}&scope=openid user'. Please ensure the request/response body is x-www-form-urlencoded.

Currently Using:
authlib==0.9
flask==0.10.1
Werkzeug==0.12.2
NOTE: Our server class...
class OIDCServer(AuthorizationServer):
    """
    Implement the OIDC provider to attach to the flask app.

    Specific OAuth grants (authorization code, refresh token) are added on to
    a server instance using ``OIDCServer.register_grant_endpoint(grant)``. For
    usage, see ``fence/oidc/server.py``.
    """

    def init_app(self, app, query_client=None, save_token=None):
        if query_client is not None:
            self.query_client = query_client
        if save_token is not None:
            self.save_token = save_token
        self.app = app
        self.generate_token = generate_token
        self.init_jwt_config(app)
        if getattr(self, "query_client"):
            self.authenticate_client = ClientAuthentication(query_client)

It appears that in werkzeug, there's a werkzeug.urls.url_to_iri function that gets called to set the url attribute in the request (here: werkzeug.wrappers.BaseRequest.url) and at this point, the %20 becomes a space  .
See: http://werkzeug.pocoo.org/docs/0.14/wrappers/#werkzeug.wrappers.BaseRequest.url
That url then gets passed into OAuth2Request in authlib.flask.oauth2.authorization_server._create_oauth2_request which eventually causes the issue noted above.
I assume that in _create_oauth2_request we should reconstruct the url without using the .url and instead combining perhaps q.url_root + q.path + q.query_string ? Note that q.query_string does maintain the %20 without replacing it with a space.
Hopefully this has made sense, let me know if you want/need additional information.

note that replacing q.url with q.url.replace(" ", "%20") (or even q.url.replace(" ", "+")) fixes the issue. However, since this is an internal function, our class cannot easily override it

NOTE: I was able to work around the issue by modifying the flask request and passing it into the functions. Our new class:
class OIDCServer(AuthorizationServer):
    """
    Implement the OIDC provider to attach to the flask app.

    Specific OAuth grants (authorization code, refresh token) are added on to
    a server instance using ``OIDCServer.register_grant_endpoint(grant)``. For
    usage, see ``fence/oidc/server.py``.
    """

    def init_app(self, app, query_client=None, save_token=None):
        if query_client is not None:
            self.query_client = query_client
        if save_token is not None:
            self.save_token = save_token
        self.app = app
        self.generate_token = generate_token
        self.init_jwt_config(app)
        if getattr(self, "query_client"):
            self.authenticate_client = ClientAuthentication(query_client)

    def validate_consent_request(self, *args, **kwargs):
        request = kwargs.pop("request", None)
        kwargs["request"] = _ensure_spaces_percent_encoded(request)
        return super(OIDCServer, self).validate_consent_request(*args, **kwargs)

    def create_token_response(self, *args, **kwargs):
        request = kwargs.pop("request", None)
        kwargs["request"] = _ensure_spaces_percent_encoded(request)
        return super(OIDCServer, self).create_token_response(*args, **kwargs)

    def create_endpoint_response(self, *args, **kwargs):
        request = kwargs.pop("request", None)
        kwargs["request"] = _ensure_spaces_percent_encoded(request)
        return super(OIDCServer, self).create_endpoint_response(*args, **kwargs)

def _ensure_spaces_percent_encoded(request):
    q = request or flask_req
    q.url = q.url.replace(" ", "%20")
    return q

I had a stack overflow post that was related to this that was answered and fixed. Or worked-around anyways.  The fix is, I think but am not sure, not yet in any of the releases.  It'll probably in 0.10.  Here's the link to his answer
and just for laziness's sake, link to the commit

This is a known issue. Fixed in 0.10.


Fix typed property without default value support

Bug Report

Q
A

BC Break
no

Version
2.0.5

Summary
We are having same (or similar) issue described in this issue and PR on ORM albeit with Mongo ODM although the doctrine/persistence is on 1.3.6.
Aside from embedded documents, we get the Error: Typed property Document::$field must not be accessed before initialization. error for scalar types, probably for all fields actually.

Change \Doctrine\ODM\MongoDB\Mapping\ClassMetadata::getIdentifierValue() into:
    public function getIdentifierValue(object $document)
    {
        return $this->reflFields[$this->identifier]->isInitialized($document) ? $this->reflFields[$this->identifier]->getValue($document) : null;
    }

@tehplague @josefsabl if one of you have a moment please open a PR with test case, that'd be much appreciated!

This happens with postgres too.

This happens on postgres too, so it's probably another problem.

This happens on postgres too, so it's probably another problem.

@MLDMoritz how this happening on Postgres is relevant for ODM and MongoDB?

There is probably a more underlying issue, as this seems to happen on odm and orm.

@MLDMoritz If you compare my snippet from above with the current body of said function you will see what kind of an issue there is. Both ODM and ORM implement the same ClassMetadata interface and both implementations need to be changed to account for typed properties.

To everybody reporting: could you please test and see if #2188 fixes the issues for you?

Unfortunatelly no, I was able to reproduce the problem in v2.1.2. As I tried to reproduce and isolate, it went away.
I am not sure if it helps, but this is the code I put to base documents so as to help debugging them (all the doctrine stuff crashes var_dump on memory).
    public function __debugInfo()
    {
        try {
            return array_reduce(
                array_filter(
                    (new \ReflectionClass($this))
                        ->getProperties(\ReflectionProperty::IS_PUBLIC),
                    fn(
                        \ReflectionProperty $property
                    ): bool => !\Nette\Utils\Strings::startsWith(
                        'Proxy\__PM__\\',
                        $property->getDeclaringClass()->getNamespaceName(),
                    )
                ),
                fn(
                    array $carry,
                    \ReflectionProperty $property
                ): array => array_merge(
                    $carry,
                    [$property->getName() => $this->{$property->getName()}]
                ),
                []
            );
        } catch (\ReflectionException $e) {
            throw new \LogicException(
                $e->getMessage(),
                $e->getCode(),
                $e
            );
        }
    }

When I tried to debug the document like: var_dump($document) I got the aforementioned error. The document has referenced document Foo which property $bar IS in the database yet the PHP complained that it is uninitialized.
I changed the code to: echo $document->foo->bar; var_dump($document); which for sure displayed the content of $bar and the var_dump also passed and displayed correct data.

@josefsabl it seems to me that you are the one accessing uninitialized properties in [$property->getName() => $this->{$property->getName()}] part. You need to account for uninitialized properties on your own since you're the one using reflection

Thanks for the reply. I don't understand this, however.
How is:
$this->foo
different from
$name = 'foo';
$this->{$name};

?
And what does it have to do with the Reflection?
The part that makes this a problem is that the property is not initialized not how do I access it. Or am I mislead?
Thanks again.

Hard to say what I was thinking 2 weeks ago, I must have mistakenly think you are accessing object's value with reflection, not via de facto $this->$name. I have never used documents with public properties so this is a bit of gray area for me, maybe new proxying can't handle it properly (although I expect it should). I believe that without an isolated test case we won't be able to help any further

I believe that without an isolated test case we won't be able to help any further

Yeah, I understand. The problem is, when I try to isolate it it always disappears and even if I put the code right back to the state where it was failing, it doesn't reappear. Weird stuff indeed :-)

@josefsabl maybe you're using cache that is not cleared properly?

@josefsabl maybe you're using cache that is not cleared properly?

🤔Interesting idea. We have a custom made adapter that integrates Nette/Cache as Doctrine/Cache, although we use it in production for years there might be a bug. It is pretty simple thing however. But thanks for direction.

@josefsabl What I meant is Doctrine creates proxy classes on it's own and usually on production regeneration of those is disabled for performance. Considering that "the problem went away" as soon as you started working with the files is a sign for me of a cache that's stale.

This "bug" appeared for me in the localhost development environment with proxy cache set to AUTOGENERATE_EVAL.


For empty LoaderState it should immidiatly transfer the state

I discovered this bug by commenting and uncommenting code to debug an issue. If LoaderState is empty, the transition to new state will never happen instead of happening immidiatly.

Thanks for finding and reporting this :slightly_smiling_face:


Feature Request(s): Use Playwright's TestCase.id or allow report dump to file

I might be missing something, but it seems the testCaseId in this reporter's terminology differs from the actual Playwright type that's called TestCase.id?
The data that gets sent to ReportPortal gets stored, seemingly without any correlating Item field to what Playwright sends to its own reporters (json reporter for instance)... So instead I'm left with creating a concatenation used the same way this reporter generates codeRef, which can be very big, and not friendly to passing/storing.
Is there a particular reason the Playwright TestCase.id wan't used instead?

Additionally, a different feature of dumping the report's data would help create that correlation, post-run.
All of this is in hopes of creating a tighter integration with our CI in Github. Ideally, a user would have the ability to click on a failed test's output link, and be directed to ReportPortal where a full Playwright integration would show its trace viewer.

Hi @jeremy-daley-kr !
You're right. Right now we are not using TestCase.id from Playwright.
It was added in Playwright 1.25, so we were initially forced to use our own id's.
We have a backlog task to implement using Playwright's TestCase.id as RP testCaseId, so I assume this will be available by toggling some option in the config for backwards compatibility. So for this case, if I understand correctly, that would be enough for you to provide the necessary binding.
As for your second question, could you describe it a bit more in detail?
Do you expect to see a link in CI for each specific failed test case in RP?
Right now, all reporters print a link to the RP launch at the end of the entire run.

As I started digging through the built-in JSON reporter more, I think I'm seeing that TestCase.id doesn't persist through retries, and perhaps that's one reason the testPath() concatenation is necessary to keep retries grouped to the same actual test... but maybe that's the codeRef field's purpose?
Additionally, I didn't realize there's a link to the RP launch at the end of the run. Does that require a config value be set? Perhaps we need to upgrade our current version (5.1.1).

As for your second question, could you describe it a bit more in detail?

Sure... simply put, writing a report-portal-results.json file to the results folder. I imagine this is the data I would see logged if debug: true. That's mostly the TLDR of that question. I don't need specific CI platforms (Github) integration, just the data to make correlation in my own integrations that then read the data via the RP API.
The final sentence was probably more of a "pie in the sky" RP platform feature request that would allow an integration here:

...It would allow a more seamless end-to-end from failure to inspection:


merge freecen_parsing into master

Once we're comfortable with the toggle's effects, we should merge it into master

We should possibly create a freecen_develop branch to track freecen-specific work after doing this.


Update

2.0.1

This minor release contains a new seaname list and a bug fix to setup.py

2.0.0

Adds checkers to support the [NCEI NetCDF templates v2.0](https://www.nodc.noaa.gov/data/formats/netcdf/v2.0/) for the following feature types:

- point
- timeSeries
- trajectory
- profile
- timeSeriesProfile
- trajectoryProfile
- grid

Updates the global sea_name attribute check to query the NCEI vocabulary lookup service
Drops check for allowable variable names for elevation variable
Drops requirement for a comment attribute

Support for swath feature types will be added once NCEI guidance is in place.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@lukecampbell I add a new command line test compliance-checker -t ncei-trajectoryprofile-orthogonal -v https://data.nodc.noaa.gov/thredds/dodsC/testdata/mbiddle/GOLD_STANDARD_NETCDF/1.1/NODC_trajectoryProfile_template_v1.1_2016-06-15_133721.704494.nc and it is failing with:
+ compliance-checker -t ncei-trajectoryprofile-orthogonal -v https://data.nodc.noaa.gov/thredds/dodsC/testdata/mbiddle/GOLD_STANDARD_NETCDF/1.1/NODC_trajectoryProfile_template_v1.1_2016-06-15_133721.704494.nc
Running Compliance Checker on the dataset from: https://data.nodc.noaa.gov/thredds/dodsC/testdata/mbiddle/GOLD_STANDARD_NETCDF/1.1/NODC_trajectoryProfile_template_v1.1_2016-06-15_133721.704494.nc
No valid checkers found for tests 'ncei-trajectoryprofile-orthogonal'
Traceback (most recent call last):
  File "/opt/conda/envs/_test/bin/compliance-checker", line 6, in <module>
    sys.exit(cchecker.main())
  File "/opt/conda/envs/_test/bin/cchecker.py", line 73, in main
    args.format)
  File "/opt/conda/envs/_test/lib/python2.7/site-packages/compliance_checker/runner.py", line 62, in run_checker
    groups = cls.stdout_output(cs, score_groups, verbose, limit)
  File "/opt/conda/envs/_test/lib/python2.7/site-packages/compliance_checker/runner.py", line 103, in stdout_output
    return groups
UnboundLocalError: local variable 'groups' referenced before assignment
TESTS FAILED: cc-plugin-ncei-2.0.0-py27_0

Is that a real failure of the test is wrong? Note that I had to change the URL from the README b/c that one no longer exists.

That looks like a very old bug in compliance checker. Do you know what version of compliance checker got downloaded?

That looks like a very old bug in compliance checker. Do you know what version of compliance checker got downloaded?

It is 2.3.0. See https://travis-ci.org/conda-forge/cc-plugin-ncei-feedstock/jobs/172355655#L530

Give me a few minutes, I'll release a 2.3.1 with the fix... I thought we fixed this long ago.

So the symptom shown in the test is because there is no check ncei-trajectoryprofile-orthogonal the check name is ncei-trajectory-profile-orthogonal. Unfortunately it manifests itself in a very unclear manner.

@Bobfrat could you look into this?

2.0.1

This minor release contains a new seaname list and a bug fix to setup.py

The CLI call worked but because it returns a non-zero exit code we cannot use for testing here. See
+ /bin/bash -x -e /feedstock_root/build_artefacts/test-tmp_dir/run_test.sh
+ compliance-checker -t ncei-trajectory-profile-orthogonal -v https://data.nodc.noaa.gov/thredds/dodsC/testdata/mbiddle/GOLD_STANDARD_NETCDF/1.1/NODC_trajectoryProfile_template_v1.1_2016-06-15_133721.704494.nc
Running Compliance Checker on the dataset from: https://data.nodc.noaa.gov/thredds/dodsC/testdata/mbiddle/GOLD_STANDARD_NETCDF/1.1/NODC_trajectoryProfile_template_v1.1_2016-06-15_133721.704494.nc

--------------------------------------------------------------------------------
                    The dataset scored 108 out of 117 points
              during the ncei-trajectory-profile-orthogonal check
--------------------------------------------------------------------------------
                           Verbose Scoring Breakdown:

                                 High Priority
--------------------------------------------------------------------------------
    Name                            :Priority: Score
All geophysical variables are trajector :3:     2/2
Highly Recommended global attributes    :3:     3/3
Required Global Attributes for Trajecto :3:     2/3
Required attributes for variable lat    :3:     3/3
Required attributes for variable lon    :3:     3/3
Required attributes for variable sal    :3:     3/3
Required attributes for variable temp   :3:     3/3
Required attributes for variable time   :3:     3/3
Required attributes for variable z      :3:     4/4
Required global attributes              :3:     1/2

                                Medium Priority
--------------------------------------------------------------------------------
    Name                            :Priority: Score
Recommended attributes for coordinate v :2:     3/3
Recommended attributes for grid mapping :2:     4/4
Recommended attributes for instrument v :2:     2/2
Recommended attributes for platform var :2:     4/4
Recommended attributes for the trajecto :2:     1/1
Recommended attributes for variable lat :2:     6/6
Recommended attributes for variable lon :2:     5/5
Recommended attributes for variable sal :2:    11/12
Recommended attributes for variable tem :2:    11/12
Recommended attributes for variable tim :2:     2/2
Recommended global attributes           :2:    31/36
Variable defining "trajectory_id" exist :2:     1/1

                                  Low Priority
--------------------------------------------------------------------------------
    Name                            :Priority: Score
Suggested global attributes             :1:    19/28

--------------------------------------------------------------------------------
                  Reasoning for the failed tests given below:

Name                             Priority:     Score:Reasoning
--------------------------------------------------------------------------------
Required Global Attributes for Trajecto:3:     2/ 3 : ncei_template_version
                                                      attribute must be NCEI_Net
                                                      CDF_TrajectoryProfile_Orth
                                                      ogonal_Template_v2.0
Required global attributes             :3:     1/ 2 : Conventions attribute is
                                                      missing or is not equal to
                                                      "CF-1.6, ACDD-1.3": CF-1.6
Recommended attributes for variable sal:2:    11/12 : coverage_content_type
                                                      should exist and be one of
                                                      the following:image,
                                                      thematicClassification,
                                                      physicalMeasurement,
                                                      auxiliaryInformation,
                                                      qualityInformation,
                                                      referenceInformation,
                                                      modelResult, or coordinate
Recommended attributes for variable tem:2:    11/12 : coverage_content_type
                                                      should exist and be one of
                                                      the following:image,
                                                      thematicClassification,
                                                      physicalMeasurement,
                                                      auxiliaryInformation,
                                                      qualityInformation,
                                                      referenceInformation,
                                                      modelResult, or coordinate
Recommended global attributes          :2:    31/36 : geospatial_bounds should
                                                      exist and not be empty.,
                                                      geospatial_bounds_crs
                                                      should exist and not be
                                                      empty., geospatial_bounds_
                                                      vertical_crs should exist
                                                      and not be empty.,
                                                      time_coverage_duration
                                                      should exist and be
                                                      ISO-8601 format (example:
                                                      PT1M30S), currently:
                                                      PT1M30.S,
                                                      time_coverage_resolution
                                                      should exist and be
                                                      ISO-8601 format (example:
                                                      PT1M30S), currently:
                                                      PT10.S
Suggested global attributes            :1:    19/28 : date_metadata_modified
                                                      should exist and be
                                                      ISO-8601 format (example:
                                                      PT1M30S), currently: ,
                                                      creator_type should exist
                                                      and not be empty.,
                                                      creator_institution should
                                                      exist and not be empty.,
                                                      publisher_type should
                                                      exist and not be empty.,
                                                      publisher_institution
                                                      should exist and not be
                                                      empty., program should
                                                      exist and not be empty.,
                                                      product_version should
                                                      exist and not be empty.,
                                                      platform_vocabulary should
                                                      exist and not be empty.,
                                                      instrument_vocabulary
                                                      should exist and not be
                                                      empty.
TESTS FAILED: cc-plugin-ncei-2.0.1-py27_0

./ci_support/run_docker_build.sh returned exit code 1

@lukecampbell is that because the dataset hasis failing? Do we have a real GOLD_STANDARD_NETCDF  :wink: that passes? Would that return a 0 exit code? What is the meaning of life? Can we return 42 instead? :stuck_out_tongue_winking_eye:

Why not just || true the call if we know it will fail?

Why not just || true the call if we know it will fail?

Because other failures, like the one that lead to 2.0.1 would be ignored.

There is such thing as a perfect score:
compliance-checker -t ncei-trajectory -v https://data.nodc.noaa.gov/thredds/dodsC/testdata/mbiddle/GOLD_STANDARD_NETCDF/1.1/NODC_trajectory_template_v1.1_2016-06-15_133719.365561.nc

There is such thing as a perfect score:

Awesome! That one returns 0. Let me know if you recommend running more CLI tests here. I see that there are many entrypoints in the setup.py and I chose that one only because it was in the readme.

Not there yet @Bobfrat.  The dataset scored 109 out of 118 points :smile:

@ocefpaf looks like the last circleci test scored 128 out of 128.

@ocefpaf looks like the last circleci test scored 128 out of 128.

Not in the previous run.

As you can see from https://github.com/conda-forge/cc-plugin-ncei-feedstock/pull/5/commits/282e9a70bb7a023f148b14dee74dc320a65a7da3 the only change was || true  # [not win].  Maybe the data change in between runs.

Can you post the links here? I'd like to get to the bottom of this.

Just follow the last two commits:
https://github.com/conda-forge/cc-plugin-ncei-feedstock/pull/5/commits

Wow, that's a tricky one. The only difference I see in the execution is one is py34, the other is py35. But the REALLY odd bits is that the number of points available changed.


read_until now always assumes the minimum number of return bytes is 1

Codecov Report

Merging #120 (1e037cd) into main (890fe42) will decrease coverage by 0.08%.
The diff coverage is 0.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main     #120      +/-   ##
==========================================
- Coverage   76.65%   76.57%   -0.08%
==========================================
  Files          32       32
  Lines        1315     1315
  Branches      213      213
==========================================
- Hits         1008     1007       -1
  Misses        239      239
- Partials       68       69       +1

Flag
Coverage Δ

unittests
76.57% <0.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

belay/device.py
77.30% <0.00%> (ø)

... and 1 file with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


WIP port to scala-native

Blocked by https://github.com/scala-native/scala-native/issues/1280

@lihaoyi
Not to be a pest, but did you get notice of my post to your Scala-Native issue #1280?
Just checking for "lost tokens" of communication.
Short story was that I looked at the issue, trying to unblock this port. I could not replicate
using 0.3.7 in an sbt project, so I was looking for help replicating.
I admire your work and would like to help your porting if I can.
Cheers,
Lee

@LeeTibbert perhaps you could try replicating it in the existing Mill project, minimizing it there, and then seeing what the difference is between how Mill and SBT use scala-native?


Question about the training result on 4 A100 with batch size = 36

I trained using four A100 GUP and the total batch size is 36.
After a total of 300,000 times of training, this is the result of the model:

which is quite different from the result given in your paper :

I did not change the code, what could be the cause?

How long do you train the model on 4 A100?

@lizhyuxi I have the same issue. Do you have any idea? I find FP is very high, which means that many images with objects are incorrectly classified as having no objects.


Using nvarguscamerasrc in conda environment?

Hey @mdegans,
thanks for putting so much effort into ensuring people to get access to machine vision on the Jetson!
I've succesfully used your script to install opencv in a miniforge environment and face an issue when trying to access the camera. I think I'm very close, but there is one last error when executing the following line:
mypipeline = "nvarguscamerasrc sensor-id=0 !video/x-raw(memory:NVMM), width=(int)1920, height=(int)1080, framerate=(fraction)30/1 ! nvvidconv flip-method=0 ! video/x-raw, width=(int)960, height=(int)540, format=(string)BGRx ! videoconvert ! video/x-raw, format=(string)BGR ! appsink"
cv2.VideoCapture(mypipeline, cv2.CAP_GSTREAMER)

It gives the following error:
[ WARN:0] global /home/uc2/Downloads/opencv-4.5.2/modules/videoio/src/cap_gstreamer.cpp (854) open OpenCV | GStreamer warning: Error opening bin: no element "nvarguscamerasrc"
[ WARN:0] global /home/uc2/Downloads/opencv-4.5.2/modules/videoio/src/cap_gstreamer.cpp (597) isPipelinePlaying OpenCV | GStreamer warning: GStreamer: pipeline have not been created
Error: Unable to open camera

gstreamer should be installed properly and the shared library created with tis script is linked properly (at least it installed).. Did I miss anything? In the non pyhton environment python it works just fine. Same as in the terminal.
>>> cv2.getBuildInformation()
'\nGeneral configuration for OpenCV 4.5.2 =====================================\n  Version control:               unknown\n\n  Platform:\n    Timestamp:                   2022-01-25T22:14:52Z\n    Host:                        Linux 4.9.253-tegra aarch64\n    CMake:                       3.10.2\n    CMake generator:             Unix Makefiles\n    CMake build tool:            /usr/bin/make\n    Configuration:               RELEASE\n\n  CPU/HW features:\n    Baseline:                    NEON FP16\n\n  C/C++:\n    Built as dynamic libs?:      YES\n    C++ standard:                11\n    C++ Compiler:                /usr/bin/c++  (ver 7.5.0)\n    C++ flags (Release):         -fsigned-char -ffast-math -W -Wall -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Wformat -Werror=format-security -Wmissing-declarations -Wundef -Winit-self -Wpointer-arith -Wshadow -Wsign-promo -Wuninitialized -Wsuggest-override -Wno-delete-non-virtual-dtor -Wno-comment -Wimplicit-fallthrough=3 -Wno-strict-overflow -fdiagnostics-show-option -pthread -fomit-frame-pointer -ffunction-sections -fdata-sections    -fvisibility=hidden -fvisibility-inlines-hidden -O3 -DNDEBUG  -DNDEBUG\n    C++ flags (Debug):           -fsigned-char -ffast-math -W -Wall -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Wformat -Werror=format-security -Wmissing-declarations -Wundef -Winit-self -Wpointer-arith -Wshadow -Wsign-promo -Wuninitialized -Wsuggest-override -Wno-delete-non-virtual-dtor -Wno-comment -Wimplicit-fallthrough=3 -Wno-strict-overflow -fdiagnostics-show-option -pthread -fomit-frame-pointer -ffunction-sections -fdata-sections    -fvisibility=hidden -fvisibility-inlines-hidden -g  -O0 -DDEBUG -D_DEBUG\n    C Compiler:                  /usr/bin/cc\n    C flags (Release):           -fsigned-char -ffast-math -W -Wall -Werror=return-type -Werror=address -Werror=sequence-point -Wformat -Werror=format-security -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wundef -Winit-self -Wpointer-arith -Wshadow -Wuninitialized -Wno-comment -Wimplicit-fallthrough=3 -Wno-strict-overflow -fdiagnostics-show-option -pthread -fomit-frame-pointer -ffunction-sections -fdata-sections    -fvisibility=hidden -O3 -DNDEBUG  -DNDEBUG\n    C flags (Debug):             -fsigned-char -ffast-math -W -Wall -Werror=return-type -Werror=address -Werror=sequence-point -Wformat -Werror=format-security -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wundef -Winit-self -Wpointer-arith -Wshadow -Wuninitialized -Wno-comment -Wimplicit-fallthrough=3 -Wno-strict-overflow -fdiagnostics-show-option -pthread -fomit-frame-pointer -ffunction-sections -fdata-sections    -fvisibility=hidden -g  -O0 -DDEBUG -D_DEBUG\n    Linker flags (Release):      -Wl,--gc-sections -Wl,--as-needed  \n    Linker flags (Debug):        -Wl,--gc-sections -Wl,--as-needed  \n    ccache:                      NO\n    Precompiled headers:         NO\n    Extra dependencies:          dl m pthread rt\n    3rdparty dependencies:\n\n  OpenCV modules:\n    To be built:                 calib3d core dnn features2d flann gapi highgui imgcodecs imgproc ml objdetect photo python3 stitching ts video videoio\n    Disabled:                    world\n    Disabled by dependency:      -\n    Unavailable:                 java python2\n    Applications:                tests perf_tests examples apps\n    Documentation:               NO\n    Non-free algorithms:         YES\n\n  GUI: \n    GTK+:                        NO\n    OpenGL support:              NO\n    VTK support:                 NO\n\n  Media I/O: \n    ZLib:                        /usr/lib/aarch64-linux-gnu/libz.so (ver 1.2.11)\n    JPEG:                        /usr/lib/aarch64-linux-gnu/libjpeg.so (ver 80)\n    WEBP:                        build (ver encoder: 0x020f)\n    PNG:                         /usr/lib/aarch64-linux-gnu/libpng.so (ver 1.6.34)\n    TIFF:                        /usr/lib/aarch64-linux-gnu/libtiff.so (ver 42 / 4.0.9)\n    JPEG 2000:                   build (ver 2.4.0)\n    OpenEXR:                     build (ver 2.3.0)\n    HDR:                         YES\n    SUNRASTER:                   YES\n    PXM:                         YES\n    PFM:                         YES\n\n  Video I/O:\n    DC1394:                      NO\n    FFMPEG:                      YES\n      avcodec:                   YES (57.107.100)\n      avformat:                  YES (57.83.100)\n      avutil:                    YES (55.78.100)\n      swscale:                   YES (4.8.100)\n      avresample:                YES (3.7.0)\n    GStreamer:                   YES (1.14.5)\n    v4l/v4l2:                    YES (linux/videodev2.h)\n\n  Parallel framework:            TBB (ver 2017.0 interface 9107)\n\n  Trace:                         YES (with Intel ITT)\n\n  Other third-party libraries:\n    Lapack:                      NO\n    Eigen:                       YES (ver 3.3.4)\n    Custom HAL:                  YES (carotene (ver 0.0.1))\n    Protobuf:                    build (3.5.1)\n\n  OpenCL:                        YES (no extra features)\n    Include path:                /home/uc2/Downloads/opencv-4.5.2/3rdparty/include/opencl/1.2\n    Link libraries:              Dynamic load\n\n  Python 3:\n    Interpreter:                 /home/uc2/miniforge3/envs/imswitch/bin/python3 (ver 3.7.12)\n    Libraries:                   /home/uc2/miniforge3/envs/imswitch/lib/libpython3.7m.so (ver 3.7.12)\n    numpy:                       /home/uc2/miniforge3/envs/imswitch/lib/python3.7/site-packages/numpy/core/include (ver 1.21.5)\n    install path:                /home/uc2/miniforge3/envs/imswitch/lib/python3.7/site-packages/cv2/python-3.7\n\n  Python (for build):            /home/uc2/miniforge3/envs/imswitch/bin/python3\n\n  Java:                          \n    ant:                         NO\n    JNI:                         NO\n    Java wrappers:               NO\n    Java tests:                  NO\n\n  Install to:                    /home/uc2/miniforge3/envs/imswitch\n-----------------------------------------------------------------\n\n'

Sorry, the camera in the dev branch is intended to bypass cv2.VideoCapture and still in development. It's only been tested with an IMX477, but intended usage is a bit like this
(see the Camera class's docstring for how it's supposed to work)
It also yields RGBA frames, not BGR or BGRA since that's what I was dealing with on the project where I used this.  The reason why VideoCapture must be bypassed is because there is no way (I know of) to pairs of images with metadata through that function.

Thanks! :)


Updated usr_23.txt to match :help enctryption

Currently, usr_23.txt and :help encryption conflict about whether swap files are encrypted are not

Thanks.  Must have been forgotten to update when this was implemented.
I'll also update the text a bit to avoid duplication.


No menu in Domoticz

Issue description
I managed to install my zigbee usb stick on my rpi4 and installed the plugin via the plugin manager. My zigbee device was found and added to domoticz, and it works. The issue is that nothing happens when I choose the Zigbee2MQTT pull down menu in domoticz. I see the screen with tabs, but it only says 'Loading...". Nothing else happens.
Additional information
Zigbee2MQTT version: don't know. Fresh installed yesterday.
Python version: 3.7.3
Domoticz version: 2021.1 13872
Plugin version: 3.1.0 bet
Logs
Attach any additional logs here which might be useful: mqtt, domoticz, plugin logs

I'm struggeling too since a fresh install yesterday, but I just managed to fix the same issue you are having. In domoticz go to the devices tab, search for the transport api (a text device) and add it as a device. Restart domoticz and there should me a menu.

I'm experiencing the same issue:
Domoticz: Version: 2021.1 (build 13949)
Zigbee2MQTT: 1.22.1-dev commit: 53003b3d
Zigbee2MQTT Domoticz Plugin: v3.1.0 beta
After adding the api_transport as device, it works as expected. You can also add this device as hidden device by using an $ sign before the name of the device, so it doesn't show up under other devices.

Thanks for the hint about the $ sign, I didn't know about this before.

After adding the api_transport as device, it works as expected. You can also add this device as hidden device by using an $ sign before the name of the device, so it doesn't show up under other devices.

I forgot to reply. Your solution worked. Thanks!


Support complex SPARQL UPDATE bodies

As discussed in https://github.com/solid/community-server/pull/786#discussion_r658847207 . Depends on the discussion in https://github.com/solid/specification/issues/125 on how to announce this.

Currently not a necessity, since the 0.9 spec will gravitate towards N3 Patch: https://github.com/solid/specification/pull/346


Removed apt install package versions because it was causing dependenc…

Removing apt install package versions because it is causing dependencies errors when a stable debian 11 package was updated the dependencies is not specified in the install command. I'm also worried these older versions will become unsupported and won't be available for download.
As of 9/4 this is the error you will see when building the docker image from the Dockerfile:
$ DOCKER_DEFAULT_PLATFORM=linux/amd64 SS_ARGS="--no-op" docker compose up --force-recreate --build --detach
[+] Building 8.5s (6/12)                                                                                docker:desktop-linux
 => [build-images internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 1.03kB                                                                                0.0s
 => [build-images internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [build-images internal] load metadata for docker.io/library/debian:11                                                                                0.9s
 => [build-images 1/9] FROM docker.io/library/debian:11@sha256:1beb7cf458bdfe71b5220cb2069eb45e3fc7eb77a1ccfb169eaebf5f6c4809ab                                                                          3.4s
 => => resolve docker.io/library/debian:11@sha256:1beb7cf458bdfe71b5220cb2069eb45e3fc7eb77a1ccfb169eaebf5f6c4809ab                                                                                0.0s
 => => sha256:1beb7cf458bdfe71b5220cb2069eb45e3fc7eb77a1ccfb169eaebf5f6c4809ab 1.85kB / 1.85kB                                                                                0.0s
 => => sha256:7ac88cb3b95d347e89126a46696374fab97153b63d25995a5c6e75b5e98a0c79 529B / 529B                                                                                0.0s
 => => sha256:07585eb557378946b168a6d3e6eba76f310d0f0fa9872d010844a2d7ebe9c1eb 1.46kB / 1.46kB                                                                                0.0s
 => => sha256:6a70103cc499a199e10e379794c60aa524d9598587cc2bdfe2995642c2da8df7 55.06MB / 55.06MB                                                                                1.9s
 => => extracting sha256:6a70103cc499a199e10e379794c60aa524d9598587cc2bdfe2995642c2da8df7                                                                                1.4s
 => [build-images 2/9] RUN apt-get -qq update                                                                                3.3s
 => ERROR [build-images 3/9] RUN apt-get -qq -y install locales=2.31-13+deb11u6 lsb-release=11.1.0 git=1:2.30.2-1+deb11u2 wget=1.21-1+deb11u1 make=4.3-4.1 binutils=2.35.2-2 gcc=4:10.2.1-1 g++=4:10.2.  0.8s
------
 > [build-images 3/9] RUN apt-get -qq -y install locales=2.31-13+deb11u6 lsb-release=11.1.0 git=1:2.30.2-1+deb11u2 wget=1.21-1+deb11u1 make=4.3-4.1 binutils=2.35.2-2 gcc=4:10.2.1-1 g++=4:10.2.1-1 patch=2.7.6-7 gzip=1.10-4+deb11u1 bzip2=1.0.8-4 perl=5.32.1-4+deb11u2 tar=1.34+dfsg-1 cpio=2.13+dfsg-4 unzip=6.0-26+deb11u1 rsync=3.2.3-4+deb11u1 file=1:5.39-3 bc=1.07.1-2+b2 libssl-dev=1.1.1n-0+deb11u5 vim=2:8.2.2434-3+deb11u1 build-essential=12.9 libncurses-dev=6.2+20201114-2+deb11u1 mtools=4.0.26-1 fdisk=2.36.1-8+deb11u1 dosfstools=4.2-1:
0.814 E: Unable to correct problems, you have held broken packages.
------
failed to solve: process "/bin/sh -c apt-get -qq -y install locales=2.31-13+deb11u6 lsb-release=11.1.0 git=1:2.30.2-1+deb11u2 wget=1.21-1+deb11u1 make=4.3-4.1 binutils=2.35.2-2 gcc=4:10.2.1-1 g++=4:10.2.1-1 patch=2.7.6-7 gzip=1.10-4+deb11u1 bzip2=1.0.8-4 perl=5.32.1-4+deb11u2 tar=1.34+dfsg-1 cpio=2.13+dfsg-4 unzip=6.0-26+deb11u1 rsync=3.2.3-4+deb11u1 file=1:5.39-3 bc=1.07.1-2+b2 libssl-dev=1.1.1n-0+deb11u5 vim=2:8.2.2434-3+deb11u1 build-essential=12.9 libncurses-dev=6.2+20201114-2+deb11u1 mtools=4.0.26-1 fdisk=2.36.1-8+deb11u1 dosfstools=4.2-1" did not complete successfully: exit code: 100

If you remove the quiet flags from apt-get install you'll see a more specific error text:
0.700 Some packages could not be installed. This may mean that you have
0.700 requested an impossible situation or if you are using the unstable
0.700 distribution that some required packages have not yet been created
0.700 or been moved out of Incoming.
0.700 The following information may help to resolve the situation:
0.700
0.700 The following packages have unmet dependencies:
0.737  file : Depends: libmagic1 (= 1:5.39-3) but 1:5.39-3+deb11u1 is to be installed
0.747 E: Unable to correct problems, you have held broken packages.

The file package has a dependency on libmagic1. You can see that libmagic1 was updated here: https://tracker.debian.org/pkg/file
From what I know (and I'm happy to be corrected). I think the best option is to remove these specific versions. The packages apt installs in the Dockerfile are not directly used to build SeedSigner OS. They are only needed because Buildroot depends on them to setup the host env to actually build the embedded linux OS. My worry with identifying more specific versions of dependencies is that some of these versions might eventually not be available for download.

I confirmed this PR has no impact to the seedsigner final image sha256 hash for 0.7.0-rc1.

This seems like a best-practice if we want to be sure that we don't miss what the debian-community best-practices have moved to. By default and without special effort, we'd be tracking the respected security-focused debian community.
Personally, I'd like to be aware of exactly what those moves are.  In the telegram group, I opined for devil's advocate that we still might be better-off specifying our requirements by version, even if it means more maintenance.
If this pr goes through, and I have no major issue with it, my above concern can be dealt-with simply by building the image and tracking the requirements changes as I notice them, then 1) failing to figure out what the issues/upgrades were all about or 2) informing myself of the what the issues/upgrades were all about.
Perhaps I would request to add a file, much like a log, to the seedsigner-os repo which lists all of the installed docker requirements with their version numbers, so that we'd always be using latest and could also know what versions were being used at a moment in time.

as of commit 571a013
ACK
I have reproduced expected binaries when building seedsigner app-branch=0.7.0-rc1 for: pi0.
...still testing and will update above for pi02w, pi2, pi4
Note to others: don't forget docker system prune -a to remove existing containers and cache.

To clarify this: Since these packages are (per Nick) used by Buildroot, not SeedSigner-OS, - Could someone please remind me where the seedsigner-OS packages (version specific ) are listed?  (The packages it does use. )
Thx. M


Receiving No Notifications

I like the idea of notifications from an extension, but I do not see any.
I'm following twbs/boostrap, and I've seen issues and PRs generated via the GH "watch" repo, but I haven't seen a single notification from this extension.
Chrome Version 51

I finally saw a notification, which happened to be after restarting Chrome. Maybe a restart is the solution?


Adding fixed axe texture

Contains
This PR fixes the backwards axe texture as attempted in #2876.
Before:

After:

How to test
Join a world and grab an axe as your active item.
Outstanding before merging

[ ] Make sure icon looks satisfactory in the inventory bar and while held

Can one of the admins please verify this patch?

Thanks so much! Might look like a small fix but it all helps :-)
I noticed your log over at https://github.com/nyu-ossd-s18/terasology-plan/blob/master/Work_Log.md - cool stuff! Do reach out more on chat if you have questions or need some more easy issues, sounds like that might be useful since you're on a timeline of sorts with that course.
On the resolution and UI elements not fitting I don't actually recall anybody actively working on it. Maybe I missed a comment somewhere. Keep in mind it is really easy for somebody to comment that they're looking at something, then they never come back. Or alternatively by the time somebody notices a comment the work may have already been done. In any case feel free to ask :-)
Added your account to the game credits, although I'm not sure how/when to credit you all as a group. Let me know! And welcome to officially being an open source developer :D

Thanks so much @Cervator for all your help and guidance so far! We really appreciate your understanding and quick response times! This project has been more daunting than any of us expected but you've been a huge help through all of it. We definitely will be reaching out on the chat, and I'll probably go back and take a look at the UI elements again!
I really appreciate the credits; hopefully we'll be contributing more soon and all of us will make it onto the game credits :D


Get-dbadatabasebackuphistory output issues

Output property backupsetupid should be backupsetid (when this is fixed please also look for the commented out fix in restore-dbadatabase)
Filelist property isn't specified properly. Needs to return a hash table or an object as that's whats expected
Both of these are prevent pipeline the output from this function into the restore chain. Have mitigated other issues in that side already.

Get-DbaBackupHistory -SqlServer ProdServer1 -Databases Hr,Finance | Restore-DbaDatabase -SqlServer StageSrv2 -DestinationDataDirectory D:\Staging

Should restore the database. Currently throws errors on the file relocate part of the restore. Have worked around most of the other things with the output changes.

This issue also linked - https://github.com/sqlcollaborative/dbatools/issues/1196

@Stuart-Moore is this still an issue or superseded by the many changes since? (DM me in Slack if it's still ongoing, otherwise feel free to close it)

Nah, fixed a while ago. then fixed again last week. Test in CI build to catch it next time someone tinkers.


-v counting broke

invoking with -vv breaks

make this binary; tidy up places looking for values outside of 0 and 1


#135 Conan package support

Hi!
This PR brings the support for Conan.
Including:

.conan/build.py
Build script to create Conan package on Travis CI
.conan/test_package/CMakeLists.txt
CMake file to build test package
.conan/test_package/conanfile.py
Conan recipe to build test package
.conan/test_package/test_package.cpp
Example code to consume Conan package created
.travis.yml
Update to run Conan job on CI
conanfile.py
Conan recipe to provide UVM package
bintray badge on README
Download link page for UVM package

Conan uses the file conanfile.py as recipe to execute all steps necessary to create the package. As your project is header-only it doesn't need build anything, just copy all headers and license. Conan defines the package id by settings + options and UVW is header-only so it doesn't need set anything.
To make sure that your package is working well, Conan provides test_package, where we put a simple example consuming your package and building as well. When test_package.cpp is including uvw header, all files are imported from the packaged provided by Conan. Test package is not for unit testing propose, it's a package validation.
When running your package on CI (appveyor, travis or any other) we could run Conan to create the package and check. But prepare a full environment with compiler, build-essential , conan and all stuff could be boring, so we use Docker. Conan provides a good range of images, including gcc and clang. Here I added only GCC 8 because we only need to create a package for any architecture or OS -- header-only project doesn't provide binaries by platform.
How to upload?
Conan uses Bintray to store their packages. You need to create an account on bintray for that. There is a good documentation how to create a bintray account here.
The build.py is configured following the reference skypjack/conan/uvw/. Where:

skypjack is your Bintray user name
conan is the repository name
uvw is the package name

Both username and repository you will need to set manually on web interface. Both username and repository could be changed by your preference, I just followed the convention.
Also, build.py has a rule to upload only tags or any branch with the pattern name "v\d+.\d+.\d+.*".
And finally, you must set the variable CONAN_PASSWORD on Travis settings. The password is the Bintray API Key, not your account password. To read your API key you need to access https://bintray.com/profile/edit and click on API Key button. Don't forget to mark as secret on Travis settings.
After to upload your package by CI, we recommend update the Bintray package page:
https://bintray.com/skypjack/conan/uvw%3Askypjack/edit?tab=general
The page contains only project metadata, as url, maturity (official), license -- There is a field for package avatar, you could use conan-uvw logo with you prefer or uvw official.
Okay, this is a lot of information. Please, feel free to ask anything.
I included @danimtb to review this PR. He is a Conan expert and maintainer.
Regards!
/cc @danimtb
closes #135

Conan log on Travis CI: https://travis-ci.org/uilianries/uvw/jobs/444613849

Hi!
It seems I've quite a lot of stuff to read.
I think I'll have the time to work on it tomorrow or the day after tomorrow.
Thank you a lot for your efforts, really appreciated.
I'll do my best to give you a feedback as soon as possible!

Coverage remained the same at 98.007% when pulling 74991a6fb106f238ad71c3f4e67cdd3f574c77bd on uilianries:feature/conanio into 9eaab52bd27151911fb075c377b5d0bb272304bb on skypjack:master.

My only concern is that this will create and upload a new package for every commit if am not missing something.

Sorry, I forgot to apply the filter. I just updated it now, thanks.

Maybe the Conan CI part should only be fired only on a new TAG

The only problem is broken jobs during new release. We will need fix the job or recipe and the author re-create the tag.

Ok, account and travis are set. What about if I merge your work on a dedicated branch and create a tag there to test it, before to merge everything on master?

Sure! build.py will upload any branch named as v?... So you could create the branch v1.11.2_conan.
I checked your Bintray repo, it looks good.

Done. Not sure everything worked as expected actually.
I'm not yet much confident with conan. If you can confirm it, I'll merge everything on master and create a dedicated tag there to track the changes.
Thank you!!

It's alive! All working good!
Reading some details on the log:
At the line 578 our python script detected the branch name as v1.11.2_conan
On the next step, line 581, it matched your branch name with the regex pattern 'v?\d+.\d+.\d+.'*. Once matched, package channel is named as stable automatically.
Your login was verified with success at the line 616.
All tests and build are executed into a docker container by the image conanio/gcc8. It's listed at line 629. That image is based on ubuntu 18.04 + gcc 8.2 + python 2 + conan
Your package is created at the line 854 and tested at 928.
The upload starts at 990.
All looks good in your bintray page:

Now you could merge into master and request the Conan Center inclusion.
Conan center is a promotion to get your package distributed as official in Conan channel. Otherwise, people will need to add your bintray repository directly.
To request that inclusion, just click on the mug icon. There is screenshot here as example.
If you are interested, I could open a new PR including some info about how to use Conan in your README file.
Regards!

Badge links were broken. Fixed.
It's ready to merge now. :+1:

I don't know what it means to use Conan in a README file, so I cannot promise I'll accept it, but it would be welcome in any case!! :-)

I would like to add a package section on readme file, explaining how to create and install conan package for uvw. Also, it could be update with vcpkg info

Badge links were broken. Fixed.

Thanks!

Just out of curiosity, what's the difference between the stuff you added to the repository and what happens with the import from github link from my account?
The latter looks far easier to do and it seems there is nothing to add to the repo, so I was wondering what are the cons of that.

They are different strategies.
When you have both the conan recipe and your project in same repo, you're in the control. All the necessary things are downloaded at once. It's centralized, easier to maintain. Also, you don't need to update the recipe for each new release.
When we need to create a Conan recipe for a project that dont care about packaging or dont want mix both code and tools stuff, we create a separated repository that imports the project by git or by any other. But we need to update the recipe version for each new release. The advantage is that we have more freedom by changing the repository, files and CI without affecting the code.
Some projects, like Poco, opted by keeping a second repository: https://github.com/pocoproject/conan-poco. Poco is a huge project and have a complex matrix to be built on CI.
As your project is header-only and you are interested in package tools, I think keep both on same repo is the better strategy. Also, we have an experimental feature for SCM. I'll open a new PR when SCM becomes official and stable.

I would like to add a package section on readme file, explaining how to create and install conan package for uvw. Also, it could be update with vcpkg info

Yeah, I did something similar in the README of EnTT. If you want to open a PR, I can proceed as I did for this one, that is I can merge it on a branch, add also a note for vcpkg and then squash everything on master at once.

They are different strategies. [...] I'll open a new PR when SCM becomes official and stable.

Thanks for the time you spent to give me all the details. Really, really appreciated. I'm just curious to know how things work under the hood and therefore I'm used to ask. It's a pleasure when I find someone willing to explain. :smile: :+1:

Uhm... not sure this is the expected behavior.
It created another project from the tag on master, this time called uvw:skypjack.

Yes, bintray uses : I checked now.
You could remove remove the uploaded package, rename the created before and restart Travis CI job,
OR,
Remove the package created before and update the new one.
sorry for my misunderstanding

Oh, my fault, I didn't get it. I'm sorry. Thanks for your reply.

Just dont forget to ask for Conan center inclusion!
Cheers!

Good point. Done.


status and kubectl sporadically become unresponsive

Hello.
I've got a cluster up, but I'm experiencing sporadic "outages" where status and kubectl claim that "microk8s is not running."
After some time, the cluster recovers. It also feels like it recovers after runing inspect, but I am not exactly sure.
Since I am not familiar with microk8s, I am looking for some help in interpreting the logs. Below is the inspect tarball right after the "outage."
inspection-report-20210704_211708.tar.gz
Thank you.

The scheduler or controller manager fails to elect a leader as shown in the logs.
Jul 04 20:24:32 mk8s microk8s.daemon-kubelite[1104878]: E0704 20:24:32.286762 1104878 status.go:71] apiserver received an error that is not an metav1.Status: &errors.errorString{s:"http: Handler timeout"}: http: Handler timeout
Jul 04 20:24:32 mk8s microk8s.daemon-kubelite[1104878]: E0704 20:24:32.287786 1104878 writers.go:130] apiserver was unable to write a fallback JSON response: http: Handler timeout
Jul 04 20:24:32 mk8s microk8s.daemon-kubelite[1104878]: I0704 20:24:32.301613 1104878 trace.go:205] Trace[1054552885]: "Update" url:/apis/coordination.k8s.io/v1/namespaces/kube-node-lease/leases/mk8s,user-agent:kubelite/v1.21.1 (linux/amd64) kubernetes/ba11848,client:<IP_ADDRESS>,accept:application/vnd.kubernetes.protobuf,application/json,protocol:HTTP/2.0 (04-Jul-2021 20:24:22.294) (total time: 10006ms):
Jul 04 20:24:32 mk8s microk8s.daemon-kubelite[1104878]: Trace[1054552885]: [10.006921944s] [10.006921944s] END
Jul 04 20:24:33 mk8s microk8s.daemon-kubelite[1104878]: E0704 20:24:33.192275 1104878 leaderelection.go:361] Failed to update lock: Put "https://<IP_ADDRESS>:16443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=15s": context deadline exceeded
Jul 04 20:24:33 mk8s microk8s.daemon-kubelite[1104878]: I0704 20:24:33.192384 1104878 leaderelection.go:278] failed to renew lease kube-system/kube-scheduler: timed out waiting for the condition
Jul 04 20:24:33 mk8s microk8s.daemon-kubelite[1104878]: F0704 20:24:33.192416 1104878 server.go:205] leaderelection lost
Jul 04 20:24:33 mk8s microk8s.daemon-kubelite[1104878]: goroutine 4981 [running]:
Jul 04 20:24:33 mk8s microk8s.daemon-kubelite[1104878]: k8s.io/kubernetes/vendor/k8s.io/klog/v2.stacks(0xc000010001, 0xc011e2f2c0, 0x41, 0x124)
Jul 04 20:24:33 mk8s microk8s.daemon-kubelite[1104878]:         /build/microk8s/parts/k8s-binaries/build/go/src/github.com/kubernetes/kubernetes/_output/local/go/src/k8s.io/kubernetes/vendor/k8s.io/klog/v2/klog.go:1021 +0xb9

When the scheduler or controller manager is unable to elect a leader, it will tip over kubelite and bring down the apiserver with it.
This is in my opinion a symptom of the backend getting slow response.
@ktsakalozos do you think the slow down coincides when kine performs compaction?  I don't have proof here though.  Looking at the logs, it seems that it can acquire the lease. But only on certain occassions where it find it too slow.

Having the same issue. Some nodes are just going down from time to time. Is there a known way of troubleshooting this?
Seen the following in the logs:
Jul 06 13:30:42 two microk8s.daemon-kubelite[2340737]: E0706 13:30:42.019434 2340737 kubelet_node_status.go:470] "Error updating node status, will retry" err="failed to patch status \"{\\\"status\\\":{\\\"$setElementOrder/conditions\\\":[{\\
\"type\\\":\\\"NetworkUnavailable\\\"},{\\\"type\\\":\\\"MemoryPressure\\\"},{\\\"type\\\":\\\"DiskPressure\\\"},{\\\"type\\\":\\\"PIDPressure\\\"},{\\\"type\\\":\\\"Ready\\\"}],\\\"conditions\\\":[{\\\"lastHeartbeatTime\\\":\\\"2021-07-06T1
3:30:32Z\\\",\\\"lastTransitionTime\\\":\\\"2021-07-06T13:30:32Z\\\",\\\"message\\\":\\\"kubelet has sufficient memory available\\\",\\\"reason\\\":\\\"KubeletHasSufficientMemory\\\",\\\"status\\\":\\\"False\\\",\\\"type\\\":\\\"MemoryPressu
re\\\"},{\\\"lastHeartbeatTime\\\":\\\"2021-07-06T13:30:32Z\\\",\\\"lastTransitionTime\\\":\\\"2021-07-06T13:30:32Z\\\",\\\"message\\\":\\\"kubelet has no disk pressure\\\",\\\"reason\\\":\\\"KubeletHasNoDiskPressure\\\",\\\"status\\\":\\\"F
alse\\\",\\\"type\\\":\\\"DiskPressure\\\"},{\\\"lastHeartbeatTime\\\":\\\"2021-07-06T13:30:32Z\\\",\\\"lastTransitionTime\\\":\\\"2021-07-06T13:30:32Z\\\",\\\"message\\\":\\\"kubelet has sufficient PID available\\\",\\\"reason\\\":\\\"Kubel
etHasSufficientPID\\\",\\\"status\\\":\\\"False\\\",\\\"type\\\":\\\"PIDPressure\\\"},{\\\"lastHeartbeatTime\\\":\\\"2021-07-06T13:30:32Z\\\",\\\"lastTransitionTime\\\":\\\"2021-07-06T13:30:32Z\\\",\\\"message\\\":\\\"kubelet is posting read
y status. AppArmor enabled\\\",\\\"reason\\\":\\\"KubeletReady\\\",\\\"status\\\":\\\"True\\\",\\\"type\\\":\\\"Ready\\\"}]}}\" for node \"two\": Patch \"https://<IP_ADDRESS>:16443/api/v1/nodes/two/status?timeout=10s\": read tcp <IP_ADDRESS>:60664
-><IP_ADDRESS>:16443: use of closed network connection"

Attaching my tarball as well inspection-report-20210706_133003.tar.gz


File name(dataset/main_xml1\scene0299_00\immask_8.png,.....) does not exist

Hi, I encountered the following problems

this problem is caused by this

I have downloaded OpenRooms dataset  and put them in the ./dataset folder, there are no pictures of  png format in main_xml1 folder. Now, I don't know where are the pictures of png format from.

Hi, did you also download the Mask.zip from OpenRooms dataset and put them together with the image?  :)

Thank you,but I only have the link of image.zip and demo.zip, I can't download Material, Geometry, Mask.zip and so on. Could you share them, thanks again!

you are welcome! Did you send an email to<EMAIL_ADDRESS>If yes, you should have received the download links to other zip files already.

Yes, I have sent, but I only received the links of image.zip and demo.zip. Other zip files haven't download links. My email is<EMAIL_ADDRESS>Could you share them, Thanks!

From my gmail record, I can see that I sent the links to the<EMAIL_ADDRESS>on Sat, Aug 7, 1:32 PM (3 days ago). I will send you the links again now :). Please let me know if you do not receive it. Thanks!

Thank you. Now the download link is available.


Flow doesn't refine type when using a reference of Array.isArray

Example:
let isArray = Array.isArray

function f (arr: Array<mixed>): Array<mixed> {
  let subArr:mixed = []

  if (isArray(subArr)) {
    return subArr
  }

  return []
}

Flow result:
7:     return subArr
              ^ mixed. This type is incompatible with the expected return type of
3: function f (arr: Array<mixed>): Array<mixed> {
                                   ^ array type

However, it refines just fine in the following code:
function f (arr: Array<mixed>): Array<mixed> {
  let subArr:mixed = []

  if (Array.isArray(subArr)) {
    return subArr
  }

  return []
}

Array.isArray is handled specially right now. If/when https://github.com/facebook/flow/issues/34 is implemented, then the isArray method could be annotated as a normal type-checking function and this would be handled correctly.

Ok, I will close this issue and follow development on #34, thanks.

@HeavenVolkoff can you reopen this? Predicates are already merged, but this is still a problem. Another example of incorrect behaviour:
const Array = {
  isArray: () => true
};

function test(x: null | Array<mixed>) {
  if (Array.isArray(x)) {
     x.forEach(() => {});
  }
}

This problem still persists as of v0.107.0.


can CocoaHTTPServer supoort transform MPEG-4 to MPEG-2 TS and publish?

i have local file with mp4 (MPEG-4),  and want to play use M3U8, but the M3U8 only play MPEG-2 TS , how can do that?

Hhahhaaaa


Added addons: horses2foam

This addons convert .hsol to foam format in Paraview. Doesnt change the core part of the code

Should we add this to the docs?

If I understand correctly, @hmarbona, you copied the sources of horses2plt to create this new add-on. That means that if new functionalities were added to horses2plt, these would need to be added manually to horses2foam, right?

Correct, the outputVariables module was modified from horses2plt, so new function needs to be added manually

@hmarbona, what's the status of this pull request?

I havent worked to combine it. I will try to do it this week, shouldnt take much time.

This pull request can be closed as it has been accommodated by other request.


Add icons for payments and finances

Checkout flows and finance interfaces use following icons missing in the package:
Suggestions:

BankBuilding
CoinIcons
RaisedHand
ShieldCheck

Examples:

and a shopping cart?

is the project active? because the lastest commit in the main branch was 8 months ago.


Add eslint for scaffolding lib

What does this PR do?
This PR add eslint for the scaffolding library.
We can't add eslint to the fontend js because too many rules aren't suited for frontend.
How should this be manually tested?

Step 1 : npm run lint

Snippets tests reports

Obsolete


Can't deploy the website on Githubs.

I am trying to use the chirpy theme for my personal blogging. And all I see is the following.
--- layout: home # Index page ---
I know that this issue has been raised multiple times here, which I have tried all but still to no avail.

in _config.yml file
# Change the following value to '/PROJECT_NAME' ONLY IF your site type is GitHub Pages Project sites
# and doesn't have a custom domain.
baseurl: '/blog'

make sure to make baseurl equal to the name of your repo.
in my case my repo was blog


[Bug]: build error

What happened?
Build error happens when I run "make -j"
Steps To Reproduce
Follow the README
Relevant log output
ld: unknown option: --whole-archive
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [libxquic.dylib] Error 1
make[1]: *** [CMakeFiles/xquic.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 90%] Built target xquic-static
make: *** [all] Error 2

what version of gcc you are using? it seems that gcc with higher version is required, we use 4.8.5 for building xquic, but latest boringssl might require higher

GCC 4.2.1. I will upadte gcc  and try again, Thanks for your response

Upgrade GCC to lates version and still not work:
gcc --version
gcc (Homebrew GCC 11.2.0_3) 11.2.0
Copyright (C) 2021 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Upgrade GCC to lates version and still not work:
gcc --version
gcc (Homebrew GCC 11.2.0_3) 11.2.0
Copyright (C) 2021 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

check if the gcc used is the one you installed, try to print the CC variable

Is the problem solved after upgrade gcc? It seems that #16 is having a problem similar to yours, you can discuss it with people in the discussion forum.

The issue is because of ld, not gcc. If you remove --whole-archive -Wl, from line 245 in CMakeLists.txt it should work.
sed -i 's/--whole-archive -Wl,//g' CMakeLists.txt

This is because you are compiling xquic on macOS, but if(PLATFORM MATCHES "mac") in cmakelists returns false which causes this problem.
A workaround is to additionally define -DPLATFORM=mac as cflags and pass it to cmake when compiling. Or patch CMakelists.txt
we can aslo use xmake/xrepo to build and use it, this library has been added xmake-repo repository. https://github.com/xmake-io/xmake-repo/blob/master/packages/x/xquic/xmake.lua
And these patches have been applied to fix it.
Only install library and export it.
$ xrepo install xquic
$ xrepo export -o /xxx/ xquic

Use xmake to build and use it directly.
add_requires("xquic")
target("test")
    set_kind("binary")
    add_files("src/*.c")
    add_packages("xquic")

This is because you are compiling xquic on macOS, but if(PLATFORM MATCHES "mac") in cmakelists returns false which causes this problem.
A workaround is to additionally define -DPLATFORM=mac as cflags and pass it to cmake when compiling. Or patch CMakelists.txt
we can aslo use xmake/xrepo to build and use it, this library has been added xmake-repo repository. https://github.com/xmake-io/xmake-repo/blob/master/packages/x/xquic/xmake.lua
And these patches have been applied to fix it.
Only install library and export all binaries.
$ xrepo install xquic
$ xrepo export -o /xxx/ xquic

$ xrepo install xquic
note: install or modify (m) these packages (pass -y to skip confirm)?
in xmake-repo:
  -> cmake 3.22.1 [from:boringssl,xquic]
  -> go 1.17.6 [from:boringssl,xquic]
  -> boringssl 2021.12.29 [from:xquic]
  -> xquic 2022.01.08
please input: y (y/n/m)

  => install go 1.17.6 .. ok
  => download https://cmake.org/files/v3.22/cmake-3.22.1-macos-universal.tar.gz .. ok
  => install cmake 3.22.1 .. ok
  => install boringssl 2021.12.29 .. ok
  => install xquic 2022.01.08 .. ok
$ xrepo fetch xquic
{
  {
    version = "2022.01.08",
    static = true,
    linkdirs = {
      "/Users/ruki/.xmake/packages/x/xquic/2022.01.08/6153e85e6d2e4ab9b5c207d956fe8698/lib"
    },
    links = {
      "xquic-static"
    },
    license = "Apache-2.0",
    libfiles = {
      "/Users/ruki/.xmake/packages/x/xquic/2022.01.08/6153e85e6d2e4ab9b5c207d956fe8698/lib/libxquic-static.a"
    },
    includedirs = {
      "/Users/ruki/.xmake/packages/x/xquic/2022.01.08/6153e85e6d2e4ab9b5c207d956fe8698/include"
    }
  }
}

Or use xmake to build and use it directly, do not use xrepo command.
add_requires("xquic")
target("test")
    set_kind("binary")
    add_files("src/*.c")
    add_packages("xquic")

$ xmake
note: install or modify (m) these packages (pass -y to skip confirm)?
in xmake-repo:
  -> cmake 3.22.1 [from:boringssl,xquic]
  -> go 1.17.6 [from:boringssl,xquic]
  -> boringssl 2021.12.29 [from:xquic]
  -> xquic 2022.01.08
please input: y (y/n/m)

  => install go 1.17.6 .. ok
  => download https://cmake.org/files/v3.22/cmake-3.22.1-macos-universal.tar.gz .. ok
  => install cmake 3.22.1 .. ok
  => install boringssl 2021.12.29 .. ok
  => install xquic 2022.01.08 .. ok
[ 25%]: ccache compiling.release src/main.cpp
/usr/local/bin/ccache /usr/bin/xcrun -sdk macosx clang -c -Qunused-arguments -arch x86_64 -mmacosx-version-min=11.4 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk -fvisibility=hidden -fvisibility-inlines-hidden -O3 -isystem /Users/ruki/.xmake/packages/x/xquic/2022.01.08/6153e85e6d2e4ab9b5c207d956fe8698/include -isystem /Users/ruki/.xmake/packages/b/boringssl/2021.12.29/6b4d6ed9952d472ba8e7d69e7e216f3f/include -DNDEBUG -o build/.objs/test/macosx/x86_64/release/src/main.cpp.o src/main.cpp
checking for flags (-MMD -MF) ... ok
checking for flags (-fdiagnostics-color=always) ... ok
[ 50%]: linking.release test
"/usr/bin/xcrun -sdk macosx clang++" -o build/macosx/x86_64/release/test build/.objs/test/macosx/x86_64/release/src/main.cpp.o -arch x86_64 -mmacosx-version-min=11.4 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk -stdlib=libc++ -L/Users/ruki/.xmake/packages/x/xquic/2022.01.08/6153e85e6d2e4ab9b5c207d956fe8698/lib -L/Users/ruki/.xmake/packages/b/boringssl/2021.12.29/6b4d6ed9952d472ba8e7d69e7e216f3f/lib -Wl,-x -lxquic-static -lssl -lcrypto -lz

Problem resolved after add -DPLATFORM=mac flag. Thanks a lot


From private repo

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

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

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


Update README.md

Added a resource for learning Java

Hello, thanks for your contribution. Youtube channel are hard to check in terms of provided content. No more channels will be added thanks.


Symbol lookup error after upgrading

Hi there. I'm using waybar on arch. I recently upgraded using pacman -Syu. And since then I got the error.
waybar: symbol lookup error: waybar: undefined symbol: _ZN4Json5ValueaSES0_
steps to reproduce
run waybar from terminal
(This is my first ever issue i open on github. So if I'm supposed to add anything or do something else please let me know)

Not sure if it is the same issue but since you mentioned using arch: What is your libjsoncpp version? Mine was updated to 1.9.1-1 about a week ago and it does not provide the libjsoncpp.so.20 required by Waybar anymore but .21 instead. I tried a symbolic link but that does not work unfortunatly. I get a waybar: error while loading shared libraries: libjsoncpp.so.20: cannot open shared object file: No such file or directory whet trying to start waybar. A downgrade should work.

Ow okay! But I don't actually know how I can downgrade. Do you know how I could do that?

Hey! I fixed my issue. Like ppascher said

A downgrade should work.

Just downgrade jsoncpp to 1.8.4 and waybar should work again. To downgrade I used the downgrader tool: https://github.com/pbrisbin/downgrade
I had to remove waybar though. Because this tool gives an error when it encounters dependencies.
Steps I used to fix:
-Remove waybar
-Downgrade jsoncpp
-Recompile and make waybar
-Profit
Should I close this issue now? I don't know how github works yet.

Yet another lookup error, not sure either if that's the same issue:
waybar: symbol lookup error: /usr/lib/libspdlog.so.1: undefined symbol: _ZN3fmt2v68internal14sprintf_formatIdEEPcT_RNS1_6bufferIcEENS1_13sprintf_specsE
I'm going to have to downgrade too then...

Yet another lookup error, not sure either if that's the same issue:
waybar: symbol lookup error: /usr/lib/libspdlog.so.1: undefined symbol: _ZN3fmt2v68internal14sprintf_formatIdEEPcT_RNS1_6bufferIcEENS1_13sprintf_specsE
I'm going to have to downgrade too then...
EDIT: doesn't really seem to have to do anything specifically with waybar saw the issue with other programs as well probably a issue with a dependency...

That's an issue with fmt. Upgrade fmt to 6.1.2 or downgrade to 6.1.0

Oh great thanks my aur helper (pacaur) has somehow not upgraded that.

I'm finding this as an issue with latest version of fmt again.
pacman -U /var/cache/pacman/pkg/fmt-7.0.3-1-x86_64.pkg.tar.zst
and boom fixed

I am experiencing the same problem on Manjaro (which it looks inherited the issue from Arch). Downgrading to fmt 7.0.3-1 solves the problem...for now.

I'm facing a smiliar issue:

waybar: symbol lookup error: waybar: undefined symbol: ZN6spdlog7details7log_msgC1ENS_10source_locEN3fmt2v617basic_string_viewIcEENS_5level10level_enumES6

I'm using debian:

No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux bullseye/sid
Release:	unstable
Codename:	sid

And waybar installed from debian repo:

waybar/unstable,now 0.9.4-1+b1 amd64

Since there were some comments about libfmt, here is the version I have:

libfmt7/unstable,now 7.1.3+ds1-4 amd64

And also:

libjsoncpp24/unstable,now 1.9.4-4 amd64

Any suggestion on how to debug / figure out what is going on is very welcome!

I couldn't get a thing with this to compile and run on Debian or Ubuntu with an up to date version of sway. Best advice is to reconsider your choice of distro for its package management philosophy if you want to use this without headaches, unless managing sid backports that maybe don't even exist along with the current version of waybar sounds like fun to you. The supporting libs packages with the distro are simply too crumbly and old for moving targets like this without someone supporting it on the distro side
-------- Original Message --------
On 28 Dec 2020, 10:02, Diego Rabatone Oliveira wrote:

I'm facing a smiliar issue:

waybar: symbol lookup error: waybar: undefined symbol: ZN6spdlog7details7log_msgC1ENS_10source_locEN3fmt2v617basic_string_viewIcEENS_5level10level_enumES6

I'm using debian:

No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux bullseye/sid
Release: unstable
Codename: sid

And waybar installed from debian repo:

waybar/unstable,now 0.9.4-1+b1 amd64

Since there were some comments about libfmt, here is the version I have:

libfmt7/unstable,now 7.1.3+ds1-4 amd64

And also:

libjsoncpp24/unstable,now 1.9.4-4 amd64

Any suggestion on how to debug / figure out what is going on is very welcome!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

wait you're actually running sid? yeah might be fixed in some days on package maintainers end but still having to deal with this on a distro like that was more trouble than it was worth for me personally.
-------- Original Message --------
On 28 Dec 2020, 18:53, Dmitri DB wrote:

I couldn't get a thing with this to compile and run on Debian or Ubuntu with an up to date version of sway. Best advice is to reconsider your choice of distro for its package management philosophy if you want to use this without headaches, unless managing sid backports that maybe don't even exist along with the current version of waybar sounds like fun to you. The supporting libs packages with the distro are simply too crumbly and old for moving targets like this without someone supporting it on the distro side
-------- Original Message --------
On 28 Dec 2020, 10:02, Diego Rabatone Oliveira wrote:

I'm facing a smiliar issue:

waybar: symbol lookup error: waybar: undefined symbol: ZN6spdlog7details7log_msgC1ENS_10source_locEN3fmt2v617basic_string_viewIcEENS_5level10level_enumES6

I'm using debian:

No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux bullseye/sid
Release: unstable
Codename: sid

And waybar installed from debian repo:

waybar/unstable,now 0.9.4-1+b1 amd64

Since there were some comments about libfmt, here is the version I have:

libfmt7/unstable,now 7.1.3+ds1-4 amd64

And also:

libjsoncpp24/unstable,now 1.9.4-4 amd64

Any suggestion on how to debug / figure out what is going on is very welcome!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

Yeap, I'm a sid user! (and I'm pretty much aware of what does this mean).
To be honest, usually it is quite ok. Indeed sometimes I face some issues that are fixed within some days (usually less then a day). And I'm good with it, especially because debian is the distro I feel more comfortable with.
Anyway, if you guys have tips for me in order to track down the error so I can file a bug report (in the broken package tracker) that would be welcome :)

if you can figure out how apt does an operation like pacman -U in arch, you're good. I just don't know if that exists, I try and run stable personally because that's debian's stronger point... and mostly just on servers
-------- Original Message --------
On 29 Dec 2020, 11:26, Diego Rabatone Oliveira wrote:

Yeap, I'm a sid user! (and I'm pretty much aware of what does this mean).
To be honest, usually it is quite ok. Indeed sometimes I face some issues that are fixed within some days (usually less then a day). And I'm good with it, especially because debian is the distro I feel more comfortable with.
Anyway, if you guys have tips for me in order to track down the error so I can file a bug report (in the broken package tracker) that would be welcome :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

What does pacman -U does?
Regarding stables and servers, then I totally agree, for servers I would never think about sid!

allows you to downgrade to a specific recent version in the package cache
-------- Original Message --------
On 29 Dec 2020, 14:29, Diego Rabatone Oliveira wrote:

What does pacman -U does?
Regarding stables and servers, then I totally agree, for servers I would never think about sid!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

Hum... I just found out something weird.
I have another computer with debian where I have a mix of testing and unstable packages (yeah, I know, this goes against debian recommendations).
In this second computer I the same waybar version installed, but I don't have the libfmt7 package installed, and waybar is working perfectly.
Eventually this has something to do with the fact that I had built waybar before it was available with apt.
I'll try to install fmt from source and see what happens.
Regarding downgrades, we can apt install <packager>=<version>. But that requires the version to be available and, in this specific case, neither waybar nor libfmt7 are available in different versions other than the one installed. (I don't know debian policies for package versions in sid)

heh yeah you're fighting a battle where literally "install gentoo" would be less of an enormous pain in the rear and waste of time
-------- Original Message --------
On 29 Dec 2020, 14:39, Diego Rabatone Oliveira wrote:

Hum... I just found out something weird.
I have another computer with debian where I have a mix of testing and unstable packages (yeah, I know, this goes against debian recommendations).
In this second computer I the same waybar version installed, but I don't have the libfmt7 package installed, and waybar is working perfectly.
Eventually this has something to do with the fact that I had built waybar before it was available with apt.
I'll try to install fmt from source and see what happens.
Regarding downgrades, we can apt install =. But that requires the version to be available and, in this specific case, neither waybar nor libfmt7 are available in different versions other than the one installed. (I don't know debian policies for package versions in sid)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

Issue already being tracked here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978471
Neither related to waybar nor fmt, it is related to: libspdlog1


Table Styling for First-Time Buyers

Table styling was broken because buy_price is not entered by first-time buyers. I allowed the Sunday minimum value from the predictions to substitute in this case for styling purposes.
Fixes the bug portion of issue #288

Tweaking to style table whenever buy price is empty for both first-timers and regular users


Replace alpine with busybox image for better response from nslookup

Replaced alpine image with gcr.io/google-containers/busybox for better response from nslookup
Fixes issue #21436

Here is the preview page to help with PR review

Let's shift that discussion to the issue: https://github.com/kubernetes/website/issues/21436#issuecomment-711075021

@ljnaresh, please update https://github.com/kubernetes/website/issues/21436 with a (brief) explanation about why this approach is the right one to choose.

/lgtm