test.py hangs after a few frames

I'm now seeing similar issues as #32 with example_run_emotion_recognition.py. The script runs for a few frames, then hangs.
I'm fairly certain both of these scripts worked at the time of the MVP release.

Fixed by 98fb7753650fbc0326fdff31a10df758f98dab9e.

Re-opened due to c152ab74ab6e65344b0fb0adba87a528cabc76ad.

@itsderek23 I experience the same issue with my device.
Commit: db28c93deeb1a607f83056c8e78e9a4a0f451d91
System information from log_system_information.sh:
Linux paradox 5.3.0-40-generic #32~18.04.1-Ubuntu SMP Mon Feb 3 14:05:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
depthai.__version__ == 0.0.10a
depthai.__dev_version__ == 60a814b225bc4aa6709045f11c9306bf9c647222
numpy.__version__ == 1.16.4
Python 3.6.9

Log for test.py app is attached.
test.log

Thanks @asmorkalov .
So this model is a 'multi-tensor output' model which we're going to put on hold for now as we stabilize more basic object detection and get training flow working.
Once that's in place we'll circle back and fix this.  CC: @GergelySzabolcs

@Luxonis-Brandon The issue is actually reproducible with all samples and tutorials I tried: emotion recognition, test app and face detection tutorial. I posted log for test as it it's a test.

Thanks @asmorkalov - we'll dig into this.
So we've seen such crash before on specific hosts over USB3.  Can you share which host computer you are using and which USB3 cable/length?
And do you have a shorter USB3 cable?  On the host that had this problem, it did not happen on a 3 foot USB3 cable.  And did not happen at all on USB2.  It seems it's a signal integrity problem at the full USB3 speeds for 6 foot cables.
Either way we'll dig in in parallel to see if we can replicate and if get this stabilized.  We'll focus on the test app (test.py).
Thoughts?
Thanks,
Brandon

We had setup a device auto-reset that might be the problem here.  This was for detecting if the user had force-killed the host code w/out giving the host code the opportunity to tell the Myriad X that it's no longer running.
This auto-reset code may be not running properly, and triggering false-alarms (false-resets).
We're investigating.

@Luxonis-Brandon I tried the same procedure with another host with and all pipelines work for me. So, it's something related to USB subsystem on host side. I'll debug it a little bit and will come with details.

Thanks @asmorkalov .  So @alex-luxonis did an intense debugging session yesterday.  We were able to find a computer in our lab machines that reproduces this reliably.  It's actually in Colorado (local to @Luxonis-Brian) and Alex is in Romania so he's been debugging remotely.
According to our building/ordering logs this is the machine.
https://pcpartpicker.com/list/KTDFQZ
So @Luxonis-Brian - could you confirm that this is the machine (most importantly, that the motherboard is correct)?
Here are some observations he shared from our slack with this machine:

This does not look like a hardware issue, but more like a software bug.
A libusb bulk read transfer on host is hanging, and it has an unexpected requested size (none of our fixed frame/meta sizes, but it is a multiple of 1KB -- the low level USB block size).
There are no USB link state events when this happens, the connection is still fine both on host and device. And no errors in the logs.
The firmware on device continues to run fine, but can no longer send on USB because the host is stalled. Adding a timeout on the host and retrying the transfer doesn't help, can't recover.
It could be related to some timings, not sure. Also, there could be some underlying USB errors that contribute to a timing change, but the USB bulk transfer type ensures data integrity (there would be transparent retransmissions in case of errors).
It may be possible that the libusb version on Ubuntu 16, or the platform used (AMD with some Realtek chipsets) may have a role here, but not sure.
Will continue to look at this tomorrow.

So @alex-luxonis is attacking this bug directly, trying to debug it and implement the USB communication such that it doesn't happen.
And @GergelySzabolcs is working to implement a host watchdog.
Thanks,
Brandon

Just an update that we're continuing to debug this.  Will circle back as we learn more.

@asmorkalov so some very interesting results.  The only computer that exhibited this issue is this exact computer:
https://pcpartpicker.com/list/KTDFQZ
Can you share the specs of computer you are using?
Long story short:

This -seems- to be something to do with hardware IOMMU and AMD CPUs, from what we understand.  And it seems like Ubuntu 18.04 and Ubuntu 16.04 handle this differently, with perhaps 18.04 disabling the hardware IOMMU, which then prevents this issue.

We can't get it to happen on any other computer.  And interestingly, this issue shows up in Ubuntu 16.04 on this computer, but does not show up at all in Ubuntu 18.04 on this same computer.
We had spent a week tweaking with settings in Ubuntu 16.04 prior to discovering this, and we were able to increase the mean time between this issue from once a minute or so to about once every couple hours or so.
And then upgrading this same computer to Ubuntu 18.04 from Ubuntu 16.04 resulted in no issues whatsoever under the same settings/tweaks which previously caused the computer to have issues within a minute (running multiple boards for over an hour together... and on Ubuntu 16.04 running multiple boards in parallel would make the issue occur within a handful of seconds).
So this -seems- to be something to do with hardware IOMMU and AMD CPUs, from what we understand.  And it seems like Ubuntu 18.04 and Ubuntu 16.04 handle this differently, with perhaps 18.04 disabling the hardware IOMMU, which then prevents this issue.
Thoughts?
Thanks,
Brandon

OK, to summarize and close this issue:

We've found that some hosts have trouble with USB3 + long cables (2 meter).  It seems to have something do do with the USB controller on the host side.  All Apple computers we've tested with have never exhibited the problem, for example.
Other hosts have no problem at all and run for days (tested well over 3 days on some), even with long cables (tested w/ a total length of a bit over 8 feet).
Ubuntu 16.04 has an independent USB3 issue. On new machines only though, and we think this has to do w/ Ubuntu 16.04 being EOLed prior or around when these new machines having hit the market.  For example, on this computer (here) has rampant USB3 disconnect issues under Ubuntu 16.04 (with a 1 meter cable), but has none under Ubuntu 18.04 (with a 1 meter cable).

So unfortunately we discovered this after we shipped with long USB3 cables (2 meter cables) with DepthAI units.
So if you have see this problem with your host, switching to a shorter USB3 cable (say 1 meter) will very likely make the problem disappear.


[stable/*] Sidecar template pattern

In last week's charts office hours we agreed the sidecar containers template pattern added in #2829 is a good, reproducible pattern for all relevant chart templates. Adding this issue to discuss which chart templates are relevant, and track rolling out this feature across them.

Couldn't make it to the call. Do we want to proactively update charts? In any case, I think this could be a good addition to our best practices. We may have to extend this pattern with e. g. sidecarVolumes or sidecarSecrets, though. Was this discussed?

@unguiculus It wasn't discussed, but I was thinking something similar. Perhaps we could also rename this to extraContainers, extraVolumes, extraSecrets (similar to how we add extraVars to existing containers on some charts). This way, we're not accidentally recommending any one of the 3 main sidecar patterns, just making charts more flexible - without adding loads of verbose detail logic - for those who want to use it for outlying use cases?

Another example: #3983

@unguiculus Ah, thanks, this is the example I was looking for initially 😄 I'll update the description.

Just came across this one: #4059

With extraSecrets comes extraConfigMaps. And their actual names should be prefixed by the release name to ensure unicity (but this makes them somewhat hidden).

On Today's call, @prydonius suggested we look at https://kubernetes.io/docs/tasks/inject-data-application/podpreset/. It's in alpha right now, so we can't use it yet in stable charts, but it's something we may want to plan on using because it's more robust, and it will keep charts cleaner.

@depohmel suggested recommending an umbrella chart with this would be a good pattern.
Note this will need to be tested out

@scottrigby @prydonius
I got this one when trying to use containers: in PodPreset :(
error: error validating "pod-preset.yaml": error validating data: found invalid field containers for v1alpha1.PodPresetSpec;

also here is the api proto https://github.com/kubernetes/api/blob/master/settings/v1alpha1/generated.proto

@depohmel Bummer, PodPreset still sounds like an elegant solution for this use case.
So far I see two options for supporting sidecars in charts now:

Work on "Admission Controller: Enhance PodPreset to inject containers and init containers" https://github.com/kubernetes/kubernetes/issues/43874
Adopt the patters #3983 + #4059 on an as-needed basis (we can still do this to unblock people while working on option 1)

Though still open to other ideas.

Thanks @scottrigby, agreed and both options sound good to me. Might be a good idea to bring up kubernetes/kubernetes#43874 to see if people are interested in it, and if so try to push it through.


Increase number of outliers allowed in grid registration

This PR increases the number of outlier fiducial spots allowed in grid registration up to 3 when n(fiducial)=5, which was constrained to be 1. This is necessary to get the OD from images where some fiducials are not detected in @lenafb 's recent data.
@jennyfolkesson I submitted an IT request to add you to Biohub Github so I can add you as a reviewer too.

Cool, thanks. I'll take a look tonight!
On Wed, Sep 1, 2021, 17:38 smguo @.***> wrote:

This PR increases the number of outlier fiducial spots allowed in grid
registration up to 3 when n(fiducial)=5, which was constrained to be 1.
This is necessary to get the OD from images where some fiducials are not
detected in @lenafb https://github.com/lenafb 's recent data.
@jennyfolkesson https://github.com/jennyfolkesson I submitted an IT
request to add you to Biohub Github so I can add you as a reviewer too.
You can view, comment on, or merge this pull request online at:
https://github.com/czbiohub/pysero/pull/83
Commit Summary

fix bug about nbr_outliers
relax nbr_outliers constraint

File Changes

M array_analyzer/transform/point_registration.py
https://github.com/czbiohub/pysero/pull/83/files#diff-8639715c1035823fc936d119b62a2b6064cea92961037ad04862999047aa8a6e
(7)

Patch Links:

https://github.com/czbiohub/pysero/pull/83.patch
https://github.com/czbiohub/pysero/pull/83.diff

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/czbiohub/pysero/pull/83, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABT3MZOLCB7XHNRQBQLFAS3T73BPHANCNFSM5DHXHMYA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


aap-lv2 repository split

We are getting more and more LV2 plugin examples with the repo itself, which is not good. But due to the way how we resolve dependency resolution, it still is kind of optimal way so far. It has to be sorted out by having library and LV2 deps split from others (samples).
This involves appropriate prefab packaging, but due to incapabaility on resolving dependencies https://github.com/atsushieno/android-audio-plugin-framework/issues/59 it is stuck.

Now that maven-publish integration has landed in AAP, it is possible to split those LV2 ports from this repo.

There are aap-lv2-fluidsynth and aap-lv2-sfizz repositories now.

With aap-lv2-guitarix split, I would say it's done.


DateTimePicker version 3.2.5 keep re-render

Hi,
After upgrading to version 3.2.5 my page keeps re-rendering infinitely. Seems some sates are not managed properly. The issue fixed once downgraded to 3.2.4. Please take a look.
Thanks
Duy

It will rerender if you abuse onError prop

@dmtrKovalenko Thanks for the reply. Not sure what wrong with my code, but I'm not even aware the onError is there and not using it as well.

Spent 30 minutes in Profiler today trying to find cascade rerenders and didn't find anything. Please provide some valid description or example

Hey so I am experiencing this issue of re-rendering when the date is changed.
This is my setup for DateTimePicker
const DateTimePickerField = ({ field, form, ...other }) => {
  const currentError = form.errors[field.name];
  return (
    <DateTimePicker
      format="MMM dd, yyyy @ p"
      showTodayButton
      autoOk
      inputVariant={other.variant}
      name={field.name}
      value={field.value}
      label={other.label}
      helperText={currentError}
      error={Boolean(currentError)}
      onError={(_, error) => {
        // handle as a side effect
        if (error !== currentError) {
          form.setFieldError(field.name, error);
        }
      }}
      onChange={(date) => {
        return form.setFieldValue(field.name, date, true);
      }}
      {...other}
    />
  );
};

I am using it with Formik like so
const DateSelector = (props) => {
  const { datesSelectedList, index } = props;
  return (
    <FormControl
      className={classnames({
        [style.dateField]: true,
        [style.unfilled]: !datesSelectedList[index],
      })}
    >
      <Field
        name={`classDates.${index}.start`}
        required
        render={(p) => (
          <DateTimePickerField
            variant="outlined"
            autoOk
            disablePast
            initialFocusedDate={addDays(index + 30)(
              new Date().setHours(9, 0, 0, 0)
            )}
            label="Start Day & Time"
            {...p}
          />
        )}
      />
    </FormControl>
  );
};

And like the OP said when I downgrade to v3.2.4 everything works great. But the upgrade to v3.2.5 or v3.2.6 causes an infinite re render when the date is changed.
If you need more information of my setup please let me know and I will do my best to help diagnose this issue. Or just fix whatever I have wrong :laughing:

I'm seeing the same using v3.2.8.


Refactor tests and allow concurrency

Pull Request
Related issue
Fixes #298
What does this PR do?

Major refactor for all tests
a special TestMeiliSearchClient is created which will audit used keys and indexes and delete them after they are used
I tested this with concurrency values [2,4,6,8,...] but found that 4 was the sweet spot, with no measurable performance gain after it
Testing time went from 00:34 (concurrency=1) to 00:13 (concurrency=4) on my machine, so about 2.6x improvement
Contributing.md table of contents got updated automatically I think
waitFor extensions got updated to throw by default if a task fails, this removes the need for asserting success state for each action
Added an assert to SwapIndex to ensure only 2 indexes are passed

Note: tasks don't get teared down and they might grow infinitely large (ref https://github.com/meilisearch/product/discussions/641)
Also the refactor is very big and I might have missed some things, sorry about that in advance
PR checklist
Please check if your PR fulfills the following requirements:

[x] Does this PR fix an existing issue, or have you listed the changes applied in the PR description (and why they are needed)?
[x] Have you read the contributing guidelines?
[x] Have you made sure that the title is accurate and descriptive of the changes?

Thank you so much for contributing to Meilisearch!
cc @brunoocasali

I changed the refactor to create a special client that will store used resources and delete them on tearDown
I also added a little assert to SwapIndex to ensure it's used correctly

Added bonus: tests are now platform agnostic, so running
dart test -p "chrome,vm"

should work


fix(/lib/queries/facultyList.js): Changed search string to slug

The original query was a 'whiteboard' build. $slug should have been the original search field.
mostly partial fix to issue #110
With the exception of one facultyDepartment, this fixes the multi-word slug issue. "Fine Arts" s the only one that removed the space entirely, instead of replacing it with a hyphen.
The following returns all of the department names and their slugs, showing that Fine Arts is the outsider.
{
  facultyDepartments (first: 100) {
    edges {
      node {
        name
        slug
      }
    }
  }
}

Wow, great work! I had so much trouble with this. I had assumed that "name" in this case already corresponded with "slug" like it seems to in some other cases. Thank you!


Use roundRobin balancing even if only one hostname

Which problem is this PR solving?

When using GRPC between jaeger-agent and jaeger-collector, one must currently enumerate each backend on the commandline in order to get any load balancing.  GRPC can do better with its pluggable resolver modules.

Short description of the changes

If you run jaeger-agent with --reporter.grpc.host-port dns:///jaeger-collector-hostname:14250 (note the dns:/// part!), the GRPC client resolves the given hostname to one or more IPs and can load balance among the backend addresses it finds.  It even looks up and obeys SRV records, if they exist.  This change makes jaeger-agent use round-robin load balancing in that situation, rather than the default of pick_first.  If there is only one backend, or the user doesn't explicitly put dns:/// before the hostname, this will have no effect.

See https://www.marwan.io/blog/grpc-dns-load-balancing for more details.
Question: should this dns resolver style be the default behaviour? That can be done easily as well.

In time: you'd get bonus points if you could add this to the documentation and/or to the help options.

In time: you'd get bonus points if you could add this to the documentation and/or to the help options.

How does this look? https://github.com/jaegertracing/documentation/pull/212

@benley awesome!
did you see any tickets that might be closed by this? I'm pretty sure we had these discussions.
Also, would you like to add Postmates to #207 / ADOPTERS.md ?

did you see any tickets that might be closed by this?

https://github.com/jaegertracing/jaeger/issues/213 is closely related but I'm not sure if this really closes it. We're adding some much-needed functionality for grpc balancing but DNS service discovery isn't going to be as reliable as, say, Zookeeper or etcd or Kubernetes API watches for noticing when the set of backends changes.

Also, would you like to add Postmates to #207 / ADOPTERS.md ?

Sure, I will do that!


Fix tags list on posts.

Uses non-deprecated GetPage call. See release notes for Hugo 0.45 for further information.
I'm a complete newb to both Hugo, this theme, and half the languages used. So if I've screwed something up or misunderstood some underlying concept, please let me know. Thanks!

I think it's better to use GetPage instead of the more brittle printf, but I'm still working out how. (Using Hugo master branch, the GetPage function has changed [since 0.45] and no longer accepts more than one parameter.)
I want to call $.Site.GetPage "tags/$v").Permalink but am unsure how to concatenate "tags" and the value of $v.

Hi @godbyk - have you verified that this change works? I haven't worked on tags yet so it's hard for me to test, but reading over the 0.45 changes this seems to work. I'm still on 0.42.2 myself so haven't experienced GetPage breaking yet.

@jhu247 It allows tags to appear on my blog post pages. I haven't dug into the tags functionality thoroughly yet, though, so I can't say whether it handles everything.


SwiftSyntax: Allow absolute position access for dangling nodes.

Since absolute position is defined by accumulating proceeding nodes,
we should allow its access for nodes without SourceFileSyntax as root.

@swift-ci please smoke test


Update key.cpp

consensus: guard against openssl's new strict DER checks
It was bothering me for a while.

That's funny, I have this in a branch I just keep forgetting about it cause of other issues.

Yep, it's not critical, but it's been updated everywhere for some times now xD

Agreed, only thing that was holding me back is I really know nothing about DER checks in the first place and wasn't sure how to go about testing it.

How can i make it happen ?

Do to the initial delay in the update we opted to not merge this prior to the update as we have not had time to fully test it.
That does not mean it will not be merged. We're attempting to make sure changes are tested in full before being merged. I am aware similar code has been pushed to most other coins but without comparing it I cannot speak to it's validity.
Please understand that this is not a matter of us not trusting you or your code it's simply a matter of wanting to make sure everything is checked multiple times before being merged.

Ho no, im not mad about it not being merged !
i know you must have a schedule, but i can't access it :-(
My question was maybe not well written: my point was: i know i can't do the tests for you, since you have to check it yourselves, but it there any other way to help ?
Now i know that it's just a matter of time now, and that i can't help further on this matter.
i will move to the next fix.

I feel like we need a test method for this but I haven't been able to attempt to write one yet and there's not one in bitcoin do to the huge differences in the key.cpp code in the first place.

Closing this pull request.

Why close this ?

Yeah I don't understand why this is closed either.... As I said it would be nice to test this but I wouldn't have closed it. @xmk3 @evanlucas thoughts? @PaycoinMaster what gives?

It was closed due to it being out of the ability to merge. And So far no tests have been Ran against the system. Once i test is Designed and this pull can be used we will reopen the ticket and test it and approve or disapprove the request.

Ahh... I wasn't aware we broke the ability to merge it lol.
Should we leave it open though in case @HFRleto wants to update the PR? With it closed he will have to open a new one after force pushing his branch github will not let him reopen this PR at that point while it would auto-update it if it were still open.

Very Well we will mark it.

Sorry for the delay, but like IngCr3at1on, i wasn't aware i broke the ability to merge this !
I mean: "This pull request can be automatically merged by project collaborators." is pretty clear to me xD

Yeah @HFRleto I'm not really sure what @PaycoinMaster is referring to I noticed that after he re-opened it (perhaps confused it with another PR when writing that?)

Currently this change would not be effective/utilized; the following is an excerpt from the bitcoin 0.10.0 release notes (which can be viewed @ https://bitcoin.org/en/release/v0.10.0):
BIP 66: strict DER encoding for signatures
Bitcoin Core 0.10 implements BIP 66, which introduces block version 3, and a new consensus rule, which prohibits non-DER signatures. Such transactions have been non-standard since Bitcoin v0.8.0 (released in February 2013), but were technically still permitted inside blocks.
This change breaks the dependency on OpenSSL’s signature parsing, and is required if implementations would want to remove all of OpenSSL from the consensus code.
The same miner-voting mechanism as in BIP 34 is used: when 751 out of a sequence of 1001 blocks have version number 3 or higher, the new consensus rule becomes active for those blocks. When 951 out of a sequence of 1001 blocks have version number 3 or higher, it becomes mandatory for all blocks.
Backward compatibility with current mining software is NOT provided, thus miners should read the first paragraph of “Mining and relay policy enhancements” above.

Since the bitcoin code present in Paycoin is from version 0.6.3 this will not have any effect on the current wallet.
If the code is updated to require this functionality it would be prudent to fetch the following patch along with this one: https://github.com/bitcoin/bitcoin/commit/c6b7b29f232c651f898eeffb93f36c8f537c56d2

You are right !
I saw Bitcoin 0.10 in the roadmap for may, but it was only for the  Wallet Port, not for a change in the transaction process !

Need to update alot for this to work.


https://-int.azurehdinsight.net works without need to manually configure DNS and deal with IPs

For HDInisght clusters gateway has internal endpoint https://<clustername>-int.azurehdinsight.net that resolves to private ip range.
That simplifies steps a lot
Also it will be nice if UI when selecting cluster from a subscription will be able to use  <clustername>-int

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

ID: 72619422-d5dd-bf46-cd80-e123880f8d59
Version Independent ID: fd55edf7-b301-5261-5ed2-3b1983f7f4fb
Content: Transform data using Hive in Azure Virtual Network - Azure Data Factory
Content Source: articles/data-factory/tutorial-transform-data-hive-virtual-network.md
Service: data-factory
GitHub Login: @nabhishek
Microsoft Alias: abnarain

Hi @kosinsky , Thanks for the feedback! We have assigned the issue to the content author to further review this and update the document as appropriate.

@nabhishek Could you please have a look at the feedback above? - Thanks.

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. The requested updates have not been made since the creation of this issue, and the timeline for resolution may vary based on resourcing, so we've created an internal work item to incorporate your suggestions. We are closing this issue for now, but feel free to comment here as necessary. #please-close


Using Service in Action breaks Authentication to Gitea Container Registry

Description
Defining a service seems to invalidate credentials given to check out main container.
This works just fine:
name: Some Action
on: [push]
jobs:
  build_and_deploy:
    runs-on: ubuntu-latest
    container:
      image: git.foobar.myhost.tld/foobar/foobar-dev:latest
      credentials:
        username: ${{ secrets.REGISTRY_USERNAME }}
        password: ${{ secrets.REGISTRY_TOKEN }}
    steps:
      - name: Nothing really
        run: echo "Hello, world!"

The logs of the Set up job step show that the credentials are used (username=***):
Start image=git.foobar.myhost.tld/foobar/foobar-dev:latest
  docker pull image=git.foobar.myhost.tld/foobar/foobar-dev:latest platform= username=*** forcePull=true
  docker pull git.foobar.myhost.tld/foobar/foobar-dev:latest

Now, adding a service (without credentials) to the action, results in credentials for the main container being empty:
name: Build Project
on: [push]
jobs:
  build_and_deploy:
    runs-on: ubuntu-latest
    container:
      image: git.foobar.myhost.tld/foobar/foobar-dev:latest
      credentials:
        username: ${{ secrets.REGISTRY_USERNAME }}
        password: ${{ secrets.REGISTRY_TOKEN }}
    services:
      db:
        image: postgres:16.4
        shm_size: 128mb
        environment:
          POSTGRES_PASSWORD: foobar
    steps:
      - name: Nothing really
        run: echo "Hello, world!"

The logs show that the credentials are no longer being used (username=):
  Start image=git.foobar.myhost.tld/foobar/foobar-dev:latest
  docker pull image=docker.io/library/postgres:16.4 platform= username= forcePull=true
  docker pull docker.io/library/postgres:16.4
pulling image 'docker.io/library/postgres:16.4' ()
Pulling from library/postgres :: 16.4
Digest: sha256:59c554e6f26822fd489ebbdef431457db2debd0c5762b24f11f603db5b91dfcc ::
Status: Image is up to date for postgres:16.4 ::
  docker pull image=git.foobar.myhost.tld/foobar/foobar-dev:latest platform= username= forcePull=true
  docker pull git.foobar.myhost.tld/foobar/foobar-dev:latest
pulling image 'git.foobar.myhost.tld/foobar/foobar-dev:latest' ()
Error response from daemon: unauthorized: authentication required

I guess this bug is in https://github.com/nektos/act/blob/master/pkg/runner/run_context.go, where main container credentials are overwritten by service credentials (even if the latter are empty).
Gitea Version
1.22.1
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
(logs are inlinded in the issue)
Screenshots
No response
Git Version
2.43.0
Operating System
Ubuntu 24.04 LTS
How are you running Gitea?
self-hosted via docker
Database
SQLite

Fixing this should be as easy as:
index 8abc435..b78bbc7 100644
--- a/pkg/runner/run_context.go
+++ b/pkg/runner/run_context.go
@@ -293,7 +293,7 @@ func (rc *RunContext) startJobContainer() common.Executor {
                        for k, v := range interpolatedEnvs {
                                envs = append(envs, fmt.Sprintf("%s=%s", k, v))
                        }
-                       username, password, err = rc.handleServiceCredentials(ctx, spec.Credentials)
+                       username, password, err := rc.handleServiceCredentials(ctx, spec.Credentials)
                        if err != nil {
                                return fmt.Errorf("failed to handle service %s credentials: %w", serviceID, err)
                        }

Sorry for misplacing this issue, it should have gone into https://gitea.com/gitea/act_runner of course.

@belowm I noticed that you pushed a commit for this, could you please post a PR to nektos/act? And I'll review it and port it to act_runner.

@wolfogre I'd like to, but didn't have the time to set things up so taht I can build and test the project. I can probably look into this  by the end of this week.
BTW -  have you considered adding a devcontainer configuration to the project? That would allow new developers to get things running more easily.


feat: custom type for stepper title and content

Enabled ReactNode type for Stepper title and content.
This is required by designed here:

@BillyG83 Using typography for both title and content.

can you resolve the conflict please @dani69654 🙏

@BillyG83 Conflicts have been fixed


mutex held to long in h2quic.QuicRoundTripper

in QuicRoundTripper.getClient the mutex is locked while a connection is dialed.

@lucas-clemente: This is API design question, and we should think about this carefully before running in the wrong direction again.
The h2quic.Client is part of our public API, and provides a Dial method that established the QUIC connection to the remote server, which is then used by Do to execute HTTP requests to that one server.
The h2quic.QuicRoundTripper is an implementation of http.RoundTripper which can execute requests to multiple destinations. If it is already has a connection to a certain server, it reuses that one instead of dialing a new done. It thus needs to createsh2quic.Clients as requests come in. If this was our only public interface, I'd make h2quic.Client.Dial private (and maybe dial lazily when Do is called). The interesting case here is two requests for the same destination that are executed at the same time. Who's supposed to dial here then?

We decided to privatize the h2quic.Client.


[Bug] With  in in select smt and  group by will cause missing from GROUP BY

Search before asking

[X] I had searched in the issues and found no similar issues.

Version
1.1.0
What's Wrong?
select list expression not produced by aggregation output (missing from GROUP BY clause?): sum(if(stat_type IN (1), 1, 0))
What You Expected?
No error
How to Reproduce?
create a test table
CREATE TABLE `test_doris_11_log` (
    `date` date NOT NULL COMMENT "",
    `uid` varchar(64) NOT NULL,
    `stat_type` int(11) NOT NULL COMMENT "",

    `price` varchar(255) NULL COMMENT "price"
)
DUPLICATE KEY(`date`, `uid`, `stat_type`)
COMMENT "OLAP"
PARTITION BY RANGE(`date`)()
DISTRIBUTED BY HASH(`uid`) BUCKETS 8
PROPERTIES (
"replication_allocation" = "tag.location.default: 3",
"dynamic_partition.enable" = "true",
"dynamic_partition.time_unit" = "DAY",
"dynamic_partition.end" = "2",
"dynamic_partition.prefix" = "p",
"dynamic_partition.replication_allocation" = "tag.location.default: 3",
"dynamic_partition.buckets" = "8",
"dynamic_partition.create_history_partition" = "true",
"dynamic_partition.history_partition_num" = "2",
"dynamic_partition.hot_partition_num" = "2",
"storage_format" = "V2"
);

insert test data
insert into test_doris_11_log values ('2022-07-15', '2222', 1, NULL), ('2022-07-15', 'ddddd', 2, '0.5');

Try some times to reproduce error
select date, sum(if(stat_type in (1), 1, 0)) from  test_doris_11_log group by date ;

Anything Else?
No response
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I can't reproduce this bug on my local machine....


Independent alignment subscenes

The main feature introduced here is the ability to create independent alignment managers, each of which can be applied to a different subset of the scene.

Also included is the ability to specify the filename used for persistence of alignment (space pins). This is obviously useful when using multiple alignment managers within the same scene, but also useful when using the single global alignment manager for multiple scenes.

/azp run

/azp run


libdoc is not generating the updated  keyword documentation

I am trying to create the keyword documentation for our python automation framework library.  libdoc is generating the keyword documentation for first time. But when I go and update the documentations in the code and re-run the utility, it doesn't pick up the changes and still generating the old documentation. Can someone help to resolve this? Thanks

I have never encountered this problem. My guess is that Libdoc is using installed version of your library. How do your run Libdoc?

Issue was with my PYTHONPATH, it was incorrect.  After  updating it to the correct path everything worked as expected. Thanks


Support specifying which services to expose from the environments

Currently, preevy exposes all services by default

I think we should respect docker-compose public ports binding, and support a label for exposing a service port if it's not defined as public

@Yshayy by "compose public ports binding" do you mean the expose property?


[neteasemusic] Unable to download

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm reporting that yt-dlp is broken on a supported site
[X] I've verified that I have updated yt-dlp to nightly or master (update instructions)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[X] I've read about sharing account credentials and I'm willing to share it if required

Region
China
Provide a description that is worded well enough to be understood
@bashonly Sorry to bother you, but we only tested the request and not the download. Seems there is a problem with the parser?
I tried all the parameters I could think of, but the problem persisted.
e.g: all best ba b* ba*
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
yt-dlp -format best --cookies-from-browser chrome -v 'https://music.163.com/#/song?id=1948825591'
[debug] Command-line config: ['-format', 'best', '--cookies-from-browser', 'chrome', '-v', 'https://music.163.com/#/song?id=1948825591']
[debug] Encodings: locale cp936, fs utf-8, pref cp936, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>from yt-dlp/yt-dlp [7ead7332a] (win_exe)
[debug] Python 3.8.10 (CPython AMD64 64bit) - Windows-10-10.0.22631-SP0 (OpenSSL 1.1.1k  25 Mar 2021)
[debug] exe versions: ffmpeg N-110338-g4570ba5d86-20230421 (setts), ffprobe N-110338-g4570ba5d86-20230421
[debug] Optional libraries: Cryptodome-3.20.0, brotli-1.1.0, certifi-2024.07.04, curl_cffi-0.5.10, mutagen-1.47.0, requests-2.32.3, sqlite3-3.35.5, urllib3-2.2.2, websockets-12.0
[debug] Proxy map: {'http': 'http://<IP_ADDRESS>:7890', 'https': 'http://<IP_ADDRESS>:7890', 'ftp': 'http://<IP_ADDRESS>:7890'}
Extracting cookies from chrome
[debug] Extracting cookies from: "C:\Users\timi\AppData\Local\Google\Chrome\User Data\Default\Network\Cookies"
[debug] Found local state file at "C:\Users\timi\AppData\Local\Google\Chrome\User Data\Local State"
Attempting to unlock cookies
Extracted 3629 cookies from chrome
[debug] cookie version breakdown: {'v10': 4132, 'other': 0, 'unencrypted': 23}
[debug] Request Handlers: urllib, requests, websockets, curl_cffi
[debug] Plugin directories: ['D:\\App\\System\\Other\\YoutudeDownloader\\yt-dlp-plugins\\cookie_unlock\\yt_dlp_plugins', 'C:\\Users\\timi\\AppData\\Roaming\\yt-dlp-plugins\\cookie_unlock\\yt_dlp_plugins']
[debug] Loaded 1834 extractors
[generic] Extracting URL: best
ERROR: [generic] 'best' is not a valid URL. Set --default-search "ytsearch" (or run  yt-dlp "ytsearch:best" ) to search YouTube
  File "yt_dlp\extractor\common.py", line 740, in extract
  File "yt_dlp\extractor\generic.py", line 2357, in _real_extract

[netease:song] Extracting URL: https://music.163.com/#/song?id=1948825591
[netease:song]<PHONE_NUMBER>: Downloading song info
[netease:song]<PHONE_NUMBER>: Downloading song URL info: level standard
[netease:song]<PHONE_NUMBER>: Downloading song URL info: level higher
[netease:song]<PHONE_NUMBER>: Downloading song URL info: level exhigh
[netease:song]<PHONE_NUMBER>: Downloading song URL info: level lossless
[netease:song]<PHONE_NUMBER>: Downloading song URL info: level hires
[netease:song]<PHONE_NUMBER>: Downloading song URL info: level jyeffect
[netease:song]<PHONE_NUMBER>: Downloading song URL info: level jymaster
[netease:song]<PHONE_NUMBER>: Downloading song URL info: level sky
[netease:song]<PHONE_NUMBER>: Downloading lyrics data
[debug] Formats sorted by: hasvid, ie_pref, lang, quality, res, fps, hdr:12(7), vcodec:vp9.2(10), channels, acodec, size, br, asr, proto, vext, aext, hasaud, source, id
ERROR: [netease:song]<PHONE_NUMBER>: Requested format is not available. Use --list-formats for a list of available formats
Traceback (most recent call last):
  File "yt_dlp\YoutubeDL.py", line 1622, in wrapper
  File "yt_dlp\YoutubeDL.py", line 1778, in __extract_info
  File "yt_dlp\YoutubeDL.py", line 1837, in process_ie_result
  File "yt_dlp\YoutubeDL.py", line 2973, in process_video_result
yt_dlp.utils.ExtractorError: [netease:song]<PHONE_NUMBER>: Requested format is not available. Use --list-formats for a list of available formats

try --format not -format

At the command line he was normal.
But that doesn't seem to be an option in my third-party program, so maybe you can help me
thank you.

that looks correct

Too bad it looks bad:(
But everyone else is good

add 'verbose': True to your ydl_opts and run it again, copy/paste the full output here please

oh shit，Thank you for reminding me, I ran install yt-dlp today and I thought it had been updated.
Thank you very much. I deleted it for him and it's back to normal. :)


feature(utility classes): implements utility classes

Documentation will need to be enhanced. Current examples are basic.
closes #459
closes #431

Deploy preview for pf-next ready!
Built with commit 2f4f610e13efdddcfc2929a622af8ef5f4934751
https://deploy-preview-501--pf-next.netlify.com

:tada: This PR is included in version 1.0.14 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Submit a project for our projects map

We want to highlight the many use cases and great projects in bioacoustics and conservation that use BirdNET in their workflow. Therefore, we have created an interactive map showing the approximate locations of these projects and some additional information.
You can access the map here: Open projects map
We will update the map regularly and also work on the visual representation. However, we need your help to add more projects to the map and keep the information accurate.
There are three ways to contribute: you can submit a pull request with an additional entry in the projects data file, you can submit this Google form, or you can simply reply in this thread and provide the following information:

Project name*
Organization/project lead*
Target species*
Country
Region/Location*
Latitude*
Longitude*
Contact
Website
Paper
Species Image URL
Species Image Credit

The fields marked with an asterisk are required to place a valid mark on the map.
If you would like to update a project or find that some information is incorrect, please reply to this thread as well.

This should probably be moved to the wiki.


Sending packets to server from microphone

Heelo, i was wondering if someone can give me some directions.
We are tyring to send  raw audio data retireved from the mic to a server Endpoint using keep alive connection.
Any implementation guidlines will be appreciated.

I'm using WebSockets for this


Allow default runner to run and reporting on unit tests before exit()

There are a number of cases when you want unit tests to run earlier than the program exits. E.g. an application may want to run and report failing unit tests on startup. While this is doable with a custom runner, it should be fairly straightforward to add a method to replicate the default runner's destructor behavior. Something that effectively allows:
    int main(int argc, char **argv)
    {
        boost::ut::cfg<>.run();                            // (1)
        boost::ut::cfg<>.on(boost::ut::events::summary{}); // (2) currently not accessible
        ...

Possible APIs could be a bool run_and_report() method to replicate the current destructor functionality or more flexible a void report_summary() to just do (2).

Thanks @OskarLinde, good point :+1:
Should be fixed by https://github.com/boost-experimental/ut/commit/8811bd5c1e7f8c26fe45c20cc047ffb93ab89159
Example usage:
int main() {
  const auto result = ut::cfg<>.run({.report_errors = true});
  std::cout << "After report\n";
  return result;
}

Thanks for amazingly quick fix. Just tested it; works as advertised. 👍


Errors when building engine on RPi 4

Hello,
First of all, thanks a lot for your job!
I was trying to build engine on my RPi 4 using:
git clone https://github.com/jwinarske/flutter_embedded
cd flutter_embedded
mkdir build && cd build
cmake ..
make package -j8

and also:
cmake .. -DENGINE_DISABLE_DESKTOP=OFF -DENGINE_EMBEDDER_FOR_TARGET=OFF
make package -j8

but both make commands failed with errors:
Errors:
  failed to resolve infra/3pp/tools/git/linux-armv6l@version:2.28.0.chromium.6 (line 27): no such package: infra/3pp/tools/git/linux-armv6l
  failed to resolve infra/3pp/tools/cpython/linux-armv6l@version:2.7.17.chromium.22 (line 21): no such package: infra/3pp/tools/cpython/linux-armv6l
  failed to resolve infra/3pp/tools/cpython3/linux-armv6l@version:3.8.0.chromium.8 (line 24): no such package: infra/3pp/tools/cpython3/linux-armv6l
/home/pi/Projects/flutter_embedded/third_party/depot_tools/bootstrap_python3: line 32: bootstrap-3.8.0.chromium.8_bin/python3/bin/python3: No such file or directory
cat: /home/pi/Projects/flutter_embedded/third_party/depot_tools/python3_bin_reldir.txt: No such file or directory
[E2020-10-16T22:11:41.668882+02:00 22451 0 annotate.go:241] original error: no such file or directory
[E2020-10-16T22:11:41.669088+02:00 22451 0 annotate.go:241]
[E2020-10-16T22:11:41.669211+02:00 22451 0 annotate.go:241] goroutine 1:
[E2020-10-16T22:11:41.669282+02:00 22451 0 annotate.go:241] #0 go.chromium.org/luci/vpython/python/interpreter.go:120 - python.(*Interpreter).GetVersion()
[E2020-10-16T22:11:41.669407+02:00 22451 0 annotate.go:241] #1 go.chromium.org/luci/vpython/venv/config.go:286 - venv.(*Config).resolvePythonInterpreter()
[E2020-10-16T22:11:41.669471+02:00 22451 0 annotate.go:241]   reason: failed to determine Python version for: /home/pi/Projects/flutter_embedded/third_party/depot_tools//python3
[E2020-10-16T22:11:41.669554+02:00 22451 0 annotate.go:241]
[E2020-10-16T22:11:41.669614+02:00 22451 0 annotate.go:241] #2 go.chromium.org/luci/vpython/venv/config.go:186 - venv.(*Config).makeEnv()
[E2020-10-16T22:11:41.669686+02:00 22451 0 annotate.go:241]   reason: failed to resolve system Python interpreter
[E2020-10-16T22:11:41.669745+02:00 22451 0 annotate.go:241]
[E2020-10-16T22:11:41.669801+02:00 22451 0 annotate.go:241] #3 go.chromium.org/luci/vpython/venv/venv.go:150 - venv.With()
[E2020-10-16T22:11:41.669858+02:00 22451 0 annotate.go:241]   reason: failed to initialize empty probe environment
[E2020-10-16T22:11:41.669916+02:00 22451 0 annotate.go:241]
[E2020-10-16T22:11:41.669973+02:00 22451 0 annotate.go:241] #4 go.chromium.org/luci/vpython/run.go:62 - vpython.Run()
[E2020-10-16T22:11:41.670030+02:00 22451 0 annotate.go:241] #5 go.chromium.org/luci/vpython/application/application.go:320 - application.(*application).mainImpl()
[E2020-10-16T22:11:41.670088+02:00 22451 0 annotate.go:241] #6 go.chromium.org/luci/vpython/application/application.go:408 - application.(*Config).Main.func1()
[E2020-10-16T22:11:41.670147+02:00 22451 0 annotate.go:241] #7 go.chromium.org/luci/vpython/application/support.go:46 - application.run()
[E2020-10-16T22:11:41.670205+02:00 22451 0 annotate.go:241] #8 go.chromium.org/luci/vpython/application/application.go:407 - application.(*Config).Main()
[E2020-10-16T22:11:41.670264+02:00 22451 0 annotate.go:241] #9 vpython/main.go:106 - main.mainImpl()
[E2020-10-16T22:11:41.670322+02:00 22451 0 annotate.go:241] #10 vpython/main.go:112 - main.main()
[E2020-10-16T22:11:41.670379+02:00 22451 0 annotate.go:241] #11 runtime/proc.go:204 - runtime.main()
[E2020-10-16T22:11:41.670437+02:00 22451 0 annotate.go:241] #12 runtime/asm_arm.s:857 - runtime.goexit()
make[2]: *** [CMakeFiles/engine.dir/build.make:109: engine-prefix/src/engine-stamp/engine-download] Error 1
make[2]: Leaving directory '/home/pi/Projects/flutter_embedded/build'
make[1]: *** [CMakeFiles/Makefile2:187: CMakeFiles/engine.dir/all] Error 2
make[1]: Leaving directory '/home/pi/Projects/flutter_embedded/build'
make: *** [Makefile:171: all] Error 2

What did I do wrong or what am I missing?
Thanks in advance!

Please use the ci branch.  I'm in the process of making this main.


Check for non-zero length before hashing

Landing without review to get the build back to a good place.


Buttons disappearing

Describe the bug
The buttons (Loop, etc) disappear
To Reproduce
They are not present in some videos. It seems random
Expected behavior
The buttons should always be there
Desktop (please complete the following information):
Windows, chrome v 124.0.6367.118 (Build officiel) (64 bits)

can't reproduce, what's the placement for buttons? can you attach some clip of it happening?

@stebo02 what version of the extension are you using.

I just got the latest update! (<IP_ADDRESS>) The issue persists so that's why I came here.

sorry i got the wrong github then ://

sorry i got the wrong github then ://

It's fine.

Should I delete my comments since they're unrelated?

Should I delete my comments since they're unrelated?

No you can leave them. The person who originally made this issue maybe using enhancer for youtube as well. The names are similar but they are two different extensions my extension YouTube Enhancer is open source, the other extension named Enhancer for YouTube is closed source.

@Rewdyy what version of the extension are you using?


You can see this contribution as Vaseline in your shell.

Close #455 definitely (I hope ?)


Some errors that appear on the training results

When we started trying your sample model, the result was a noisy video, again, each frame is a noisy image, I wonder if we need input or other errors during training? thank
This is one frame in entire_video

This is  our results video
https://user-images.githubusercontent.com/82143592/199881206-6f9d285b-2d32-4dae-8a66-0d76577ec1e4.mp4
Thanks a lot

I also want to know why.

It is not done yet. please be patient and stop sending me emails
If there is a "wip" flag, it isn't done

It is not done yet
For any of my repositories, if there is an wip flag, it means "work is in progress"

Got is. Thanks！


Validation error on InlinePanel during page creation

Issue Summary
On upgrading to Wagtail 1.11 and Django 1.11.3 the InlinePanel component issues the error 'please send 1 or more forms' on new page creation if no content has been entered into a field in the InlinePanel.  This error can be worked around by entering some data into field panel prior to the page creation.  After the page is created the content can be removed to be empty and the page can be saved as expected (with or without content).
Steps to Reproduce

Start a new project with wagtail start myproject
Example models.py provided below.
Run migrations and then server
Create a new page, enter only a title and press 'Save Draft'.  The page save will fail with a validation error.
Add content to 'text1' field, press 'save draft', the page will create successfully.
Remove content from 'text1' field, press 'save draft', the page will update successfully.
Save again with no content in 'text1' field, press 'save draft', the page will update successfully.

from __future__ import absolute_import, unicode_literals

from django.db import models

from modelcluster.fields import ParentalKey

from wagtail.wagtailcore.models import Page
from wagtail.wagtailadmin.edit_handlers import FieldPanel, InlinePanel

class HomePageItem(models.Model):
    page = ParentalKey('HomePage', related_name='homepage_item')

    text1 = models.TextField(blank=True)

    panels = [
        FieldPanel('text1'),
    ]

class HomePage(Page):
    content_panels = Page.content_panels + [
        InlinePanel('homepage_item', label='Items', min_num=1, max_num=1),
    ]

This seems related to #3563 but the Django version I'm using should have this problem fixed (it was fixed in Django v1.11.1)
Technical details

Python version: 3.6.1
Django version: 1.11.3
Wagtail version: 1.11
Browser version: Firefox v54 (Mac)

I think this might be a Django limitation - the basic Django formset implementation presents you with several empty forms up front (rather than having a dynamic "add item" button), so in cases like this where a completely blank form is a valid object, there's no way to distinguish between "I left this form blank because I want to add a blank object here" and "I left this form blank because I don't want to add an object here". Perhaps we can work around this by adding an always-filled dummy hidden field to each form...

I looked at how Django handled this prior to DJ v1.11 and it doesn't create entries in the DB for the related objects that are empty during creation (the HomePageItem in the above example).  But now the validation is in place and from your explanation I can see why this now fails.
In my particular case I can convert the site to using a MultiFieldPanel and make the referenced model, abstract, and part of the page and write a data migration.


Why does worker not support uninstalling or updating WorkflowType?

Is your feature request related to a problem? Please describe.
My requirement requires work support for uninstalling or updating workflowType, and I need to check if they are registered through workflow name.
Proposed Solution

Provide an API for uninstalling workflowType.
Provide APIs for updating workflow types.
Provide an API for querying whether registered through workflow name.

Additional context
I have implemented these locally.

I implement these functions based on the registry structure cache mapping.

Hey. Could you elaborate what is your usecase?
I'm not sure I understand.

@3vilhamster Thanks.
My scenario is to combine multiple HTTP interfaces into a workflow, including registering, uninstalling, or updating workflows. I require the entire process to be dynamic, rather than sending new versions every time changes are made.
I have already implemented the corresponding requirements locally. The general processing process is as follows:

Dynamically generate corresponding functions based on GO plugins, where each plugin corresponds to a complete workflow processing logic.
Dynamically register, uninstall, or update workflows based on the above functions, although cadence currently does not support uninstallation or update workflows. So I implemented it by modifying the cadence source code, first defining three interfaces in the cadence/worker that correspond to uninstallation, update, and detecting whether the workflow has been registered through name. Then implement these three interfaces in cadence/internal/registry, mainly based on a series of operations on registry.workflowFuncMap.

I am not sure if dynamic updates or uninstallations are suitable for long-term or scheduled workflows. But in my scenario, it seems reasonable.

This is probably because it was not a use case previously. I don't see a downside for unregistering workflows dynamically. Especially long running workflows, since the task is automatically matched by Cadence to any available worker that has the workflow registered and is polling the task list.


Enable video scaler

vcam support the resolution converter from 640 * 480 to 1280 * 720 when vcam enables the conv_res_on.
$ v4l2-ctl -d /dev/video0 --list-formats-ext
ioctl: VIDIOC_ENUM_FMT
	Type: Video Capture

	[0]: 'RGB3' (24-bit RGB 8-8-8)
		Size: Discrete 1280x720
			Interval: Stepwise 0.017s - 1001.000s with step 0.017s (0.001-59.940 fps)

You should show the result of the following command as well.
$ v4l2-ctl -d /dev/video? --list-formats-ext

Here /dev/video? is the device file associated with vcam.

It is NOT resolution converter. Instead, use "scaler."

By the way, please do git rebase with the latest master branch.

Improve the grammar of git commit message.

I already do git rebase on the newest master.

Thank @WayneLin1992 for contributing! I amended the git commit messages for minor improvements.


fix(plugins/acme): username/password is a valid authentication method

Fixed an issue where username and password were not accepted as valid authentication methods.
Depends on this PR of lua-resty-acme: https://github.com/fffonion/lua-resty-acme/pull/121
Fix FTI-6143

Summary

Checklist

[x] The Pull Request has tests
[x] A changelog file has been created under changelog/unreleased/kong or skip-changelog label added on PR if changelog is unnecessary. README.md
[ ] There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - PUT DOCS PR HERE

Issue reference

Fix FTI-6143

@fffonion can you take another look at the PR, please?


Added styleci config

@GrahamCampbell Should we remove the .php_cs as well?

Nah, that's still useful for people running php-cs-fixer locally.

Ok.


Sorted sets are sometimes printed as unsorted sets

Evaluating (into (sorted-set) [64 37 10 -18 52 21 54 88 -102]) prints #{64 37 10 -18 52 21 54 88 -102}. However, evaluating (into (sorted-set) [64 37 10 -18]) prints #{-18 10 37 64}. Seems weird.

This is caused by the pretty printing issue as described in #77. You can disable the auto pretty printing in the Proto REPL settings to work around it.
Auto pretty printing turned off
(into (sorted-set) [64 37 10 -18 52 21 54 88 -102])
user=> #{-102 -18 10 21 37 52 54 64 88}

Auto pretty printing turned on
(into (sorted-set) [64 37 10 -18 52 21 54 88 -102])
user=>
#{64 37 10 -18 52 21 54 88 -102}


Bundle TypeScript 3.2

Tracking shipping TypeScript 3.2 as the version bundled with VS Code
You can track features and bug fixes:

For RC: https://github.com/Microsoft/TypeScript/issues?q=is%3Aopen+is%3Aissue+milestone%3A"TypeScript+3.2"
For final: https://github.com/Microsoft/TypeScript/issues?q=is%3Aopen+is%3Aissue+milestone%3A"TypeScript+3.2.1"

Please, consider better support of Typescript#13730.
Im using 3.2.0-dev right now to get Intelliscence on my leading slash imports (Meteor)
And there is some little bugs :

Intelliscence is mixing system root and jsconfig root
Reload is required when changing some leading slash paths settings in jsconfig.json
Maybe intelliscence should resolve by default "/*" as project root when baseUrl is set to "." ? Because the current way to change it is not really intuitive

Links in OP don't work. See here for more info.


Few RabbitMQ related polish

21:20:13,496 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:3.3.0:check (check-style) on project james-server-queue-rabbitmq: You have 1 Checkstyle violation. -> [Help 1]

Fixed the checkstyle issue


Fix DOIs of Lebrasseur 2024

Pull Request
This PR is for a

[ ] New Publication(s)
[x] Correction

For the following list(s):

[ ] ancientmetagenome-environmental (README)
[ ] ancientmetagenome-hostassociated (README)
[x] ancientsinglegenome-hostassociated (README)

This fixes the DOI of Lebrasseur 2024 to comply with the requirements of the field data_publication_doi:

Must correspond to the publication_doi of the publication in the corresponding sample metadata table!

Created the branch from the wrong base branch!


Reverse tab open order for open-all-notifications

Description
Currently, when using the "Open unread" button on repositories' notifications tabs are opened in the order they appear in the document, i.e. in reverse chronological order. Especially when following only releases of a repo I'd much prefer tabs to be opened chronologically in release order, and personally feel like that would make sense for other notification types as well.
While I see a change of open order for release notifications as a clear improvement I can imagine it may be more controversial for other notifications? Alternatively, a way to sort the notifications manually - at least for the current page - might be an option? I wouldn't consider a new global feature for reversing notification order as reverse chronological order by default makes sense to me for display.
Example URLs
https://github.com/notifications

might be an option?

We don't have optional features. All features should make sense as a default.

a way to sort the notifications manually

It's a can of worms I'd rather not open. Example of issues:

confusing behavior because it only sorts the current view, unlike how the rest of the website works
confusing behavior when you mark most notifications as done and new notifications are ajaxed in… appearing at the top 🤔
etc

Reverse tab open order for open-all-notifications

I think this makes sense and would as easy as notificationsArray.reverse(). PR welcome

Glad to read you think the main idea makes sense, I opened a corresponding PR for it just now.
The manual sort feature was as I was trying to say just an alternative idea in case the simple main one wouldn't have been welcomed, so seems to not need further discussion anyway, but I would have been somewhat unsure about the potential for confusion there as well. I'm aware that optional features aren't a thing here and wasn't what I intended the phrase "might be an option" to mean (to my knowledge that's just a common way of saying "another thing one could do instead", not a native speaker).


No coverage for typescript compiled project

https://gist.github.com/repinvv/9440648d1f128dd9d144589e5be7d456
npm i
npm test
Expected Behavior
This is how it works with<EMAIL_ADDRESS>
Observed Behavior
nyc@14

Environment Information
System:
OS: Windows 10
CPU: (8) x64 Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz
Memory: 1.83 GB / 7.84 GB
Binaries:
Node: 12.11.1 - C:\Program Files\nodejs\node.EXE
npm: 6.11.3 - C:\Program Files\nodejs\npm.CMD

the same on another PC:
System:
OS: Linux 4.4 Ubuntu 18.04.1 LTS (Bionic Beaver)
CPU: (16) x64 AMD Ryzen 7 1700X Eight-Core Processor
Memory: 20.86 GB / 31.94 GB
Binaries:
Node: 12.0.0 - /usr/bin/node
npm: 6.9.0 - /usr/bin/npm
npmPackages:
nyc: ^14.1.1 => 14.1.1
typescript: ^3.6.4 => 3.6.4

I think you need  to remove the nyc include option and set "extension": [".ts"].  .js is automatically added to allow nyc to instrument the output of tsc but your current configuration is excluding the original source filename which causes it to be removed from the reports.

Still does not work. I expect to see 1 line add.ts and it has to be 100% covered.
Forgot to add, with nyc 13.3 it works, with 14.1.1 it fails.
But with 13.3 there is another issue now, which caused me to go upgrade.

I experience the same behaviour that istanbul is only reporting 100% Branch coverage.

I'm also running into this issue with v14.1.1. Configuration is pretty simple:
  "nyc": {
    "extends": "@istanbuljs/nyc-config-typescript",
    "check-coverage": true
  }

in my package.json. v13.3 did not cause this issue as reported in this issue.

@rhysd this is a known breaking change of 14.x.  Changing the default extension list is also considered a breaking change for nyc so adding .ts to the defaults is part of nyc@15.  You can get that version using npm i -D nyc@next, subscribe to #1104 for updates on progress towards the final release.
@repinvv I've had a moment to clone your gist.  I recommend upgrading to nyc 15 which includes some fixes that apply to your project.  After upgrading make changes to your nyc configuration:

Set "cache": false
Remove include and extension settings
Change exclude to ["*.spec.*"]

@coreyfarrell Thank you for the information. I'll wait for v15 keeping my configuration meantime.

yes, nyc@15 beta works for me. Needs a lot more specified in exclude section, but it works. I wonder if it does instrument more files than needed which might impact its performance, since I don't specify what to include anymore.

As an alternative you could specify "include": ["*.js", "*.ts"] if you are worried about sub-directories potentially being included, otherwise the default extension list already restricts what can be included.  Unless you have specific performance issues with the --all feature then I'd recommend not worrying about being more strict than you need to.


I was thinking of how to make it more practical and reduce energy consumption. So like the charging station in homes for the Tesla what if we had a smaller charging station that we could use to mine for said coins?  I did the math there are roughly 5 billion cell phones in the world and 2.17 billion smart phones. @ .25 to charge just a phone if that cost was reduced by using a charging station 2.17 billion * .25 is roughly 500 million dollars we would not be putting into the electric companies pockets. If cars will be mostly electric it only makes sense we would transition other devices in the same manor. So how does it help doge? Well simply put we would be using renewable energy on the  devices we mine with.[feat]

Feature Request
Describe the Feature Request

Describe Preferred Solution

Describe Alternatives

Related Code

Additional Context

Brilliant - I’m in, that’s a great idea.
Reply to this email directly, view it on GitHub
https://github.com/dogecoin/dogecoin/issues/2186, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AS7OEDYUPKUOQA2JT3CQHNLTPYFPFANCNFSM45T2ZT3Q
.

--
Cat Mayville
President, Spot Digital Media
404-357-4503

wow, I couldn't ignore this one.... answer this.... what powers the charging station? LOL

The spam going on in this repo is ridiculous and absolutely absurd. Where were all these people before ? Now that doge's price is up and some made profit. suddenly NOW they care ffs.  This is not a place for proposing ideas that have no application to actual code changes people. stop spamming !! I've almost had to unfollow this repo because my inbox is full of nonsense.

Decentralisation means miners are independent of the core maintainers, rather than something we (as open source software maintainers) control, as much as yes it would be great if they used more renewables.
The better news is others are trying to encourage more responsible practices httpswww.theverge.com202152422451900elon-musk-bitcoin-miners-council-sustainability

1st your response is un neccasry. The power generated would come from the tesla solar roof. 2nd a simple thanks for the imput would have sufficed but this is not the type of ideas we are lookibg for. The question was how to improve doge.  Pathetic.

This is not the appropriate venue to bring these topics. It is only wasting time of developers from focusing on actual proposed code implementations. These sudden influx of issues being filed almost seems like a targeted attack on the repository. Getting attention on these matters would be best done elsewhere such as reddit/discord/zoom or putting together a team to research, develop and gather capable individuals to accomplish any proposed goals. Also those venues are better suited where the discussions can be properly followed, pinned, and referenced to.
Finding better energy sources to reduce Dogecoin's carbon footprint is a novel and wonderful idea. However, github is simply not the place to address and make that change where there isn't even a sliver of mention of changing the code to make such an endeavor happen.
So I urge people that have awesome ideas for this project to present them where they would be better challenged and reach an audience that would gain the support and movement it needs to succeed.  If it results that actual code updates could be proposed then they should presented to the developers through properly fashioned pull requests.

DemonRx that is a very positive and thoughtful way of saying that. So thank you for not insulting my idea even if its a bad one unrealistic or not related to the topic. I was unaware that the goal here is to improve it in functionability through the coding processs. I simy thought it was a discussion on how to improve doge all together. If its coding and software development then im out of my leauge and in the wrong place. But its the thought that counts i suppose. Cheers.

Just to  clarify, filing issues in github...  means that there's an actual problem occurring with the code / software itself. So to say the software isn't energy efficient is a bit hypocritical when considering the amount of power being used by hardcore gamers on their playstations, xbox's and gamer systems and let's not even get into datacenters ;). Dogecoin's mining power is miniscule in comparison to world's energy consumption with other activities going on.
The current Dogecoin hashrate is 407.17 TH/s, representing the global Dogecoin network hashrate with a mining difficulty of 5.97 M at block height 3,746,372.
So we can say hypothetically that the electrical cost of dogecoin's network hashrate @0.10$/kWh at 2100 watts per miner = 5.06$ / day. 🔋
And just some food for thought:

According to the University of Cambridge's bitcoin electricity consumption index, bitcoin miners are expected to consume roughly 130 Terawatt-hours of energy (TWh), which is roughly 0.6% of global electricity consumption.Mar 21, 2021

@cmpitts yes I think many people coming here don't understand what github is about. That this space is specifically for coding/software development. I hope others will come to that realization too and save us our inboxes from the flood of issues herein as of recent 😄


MANIFEST: Add "reqs"

If not added, source installations created with sdist
don't work.
Fixes https://github.com/CamDavidsonPilon/lifelines/issues/900

@CamDavidsonPilon would it be possible to push a bugfix version into pypi for this issue ?

@AbdealiJK thanks for this PR - and yes, I think it's important enough to hotfix on PyPI.


bug: no generic DB credentials?

Via @marcionemec-daitan:
We need to change the Oracle Connection credentials to another one (currently we are using my credentials while we don't have an specific for ETL Tool), as I'm leaving the project I don't know if my DB credentials will be removed (I hope yes).

Resolved!


Clarify and align supported CycloneDX versions in the AboutCode stack

We should have a consistent support for versions we can import and export and this may not be consistent?
My take is that this should support:

1.5 for the output format across all tools
1.4 and up (or 1.3 and up) as the input format for all tools

We should also ensure that we update all tools at once.

SCIO https://github.com/nexB/scancode.io/blob/main/scanpipe/pipes/cyclonedx.py 1.4? 1.5?
SCTK https://github.com/nexB/scancode-toolkit/blob/develop/src/formattedcode/output_cyclonedx.py 1.3?
DJCD https://github.com/nexB/dejacode/blob/badc0d68ec5e6535069c003e10676d230da8560d/dje/views.py#L2343 ?

I am filing this issue here and we may need to break this down as needed in each repo.

For compat, it may be useful to support reporting CycloneDX 1.4 AND 1.5

ScanCode.io:

input: 1.2 to 1.5 https://github.com/nexB/scancode.io/blob/main/scanpipe/pipes/cyclonedx.py
output: 1.5 https://github.com/nexB/scancode.io/blob/main/scanpipe/pipes/output.py#L715


Feature/msienkie/prep qc modifications

Requesting changes for PAQC to be merged into 'develop' and future tags.
The impetus for this request is to add the NCEP changes in CQCVAD need to process the new 'Level 2' data - increases in array sizes.   Should be zero diff prior to the new data start (3/30/2022).
There is a small bug fix in fix_ascat.f90 to correctly implement a quality control check.   I believe this program is only needed when running with gdas_prepbufr files during the period before 2011/05/09 12z when the ASCATW data was given a purge flag.
Modified the formatting in a few routines - gsidiag_bin2txt.f90, scanbuf2.f
Add some new routines used in MERRA2  flag_NPbuoy.f, twindow.f (twindow.rc, twindow_m2.rc)  Also added utility program scanbuf0_accum.f (like scanbuf0 but only prints cumulative counts at the end).
Merged in NCEP changes to bring code up to date with latest NCEP (obsproc_prep.v5.5.0) - prevents.f, cqcbufr.f cqcvad.f profcqc.f
Modified ancient copy of 'read_prepbufr' code in radcor directory to work with current prepbufr format files.
Modified oiqcbufr.f to use 10-digit dates (yyyymmddhh) with the BUFR library .  This avoids future problems with the shifting time window for 8-digit dates.

Sorry about including all the miscellaneous files - if necessary I can pull some of these off onto separate requests.  After the CQCVAD problem I thought it would be a good idea to catch up with changes that I had been accumulating, to bring us up to date with NCEP

Technically the changes are non-zero diff.  It is extremely unlikely for the modification in fix_ascat to trigger a change in the output and more than likely that the data formerly unflagged would be used in the assimilation.
The changes in cqcvad.f to increase the array size are only non-zero after the start of the new data at the end of March 2022.

I ran some tests with this code and compared with results from running with code from a 5_29_4 tag.  It looks like the cqcvad.f already had changes to increase array sizes versus the code in MERRA2.  The BUFR files resulting from running gmao_prepqc were zero diff.   It would still be good to bring in the various prepqc changes in this tag so we can be prepared for possible future changes.

Meta, I am bring this in, ok?

I modified CQCVAD to increase the maximum number of reports, and I tested the code to see there are zero diffs for files with less than 50000 levels and that files with more than that number of levels are handled correctly by the new code.
I merged the current develop branch and pushed my changes to GitHub.


Base Colors & Alpha Colors Conflict

The result of this line is that you only end up with the alpha colors:
https://github.com/viktorbonino/radix-themes-tw/blob/59928a5019d10b8b4acba2748987f73fc5a39332/src/index.ts#L65
Is that the intention? (Still trying to figure out themes)

I fixed it. Upgrade the package and should work. I forgot to add an A on the alpha colors name.
Now you can access both colors and alpha colors.
For example(with bg utility):
bg-red-5

bg-redA-5

How do we access alpha for bg-accent?


Graphical User Interface

Hi Christian:
To do a GUI you can use HTML, as in any regular web application, it is way better this way than me creating a new GUI library.


boards: add initial support for Zion generic board

Add Zion board, a small generic stm32f303k8 based board.
Tested samples:
* blinky

Hi, apologize for the multiple force-push, this is my first patch here, still learning.

Hi, apologize for the multiple force-push, this is my first patch here, still learning.

No need to apologize! And thanks for the PR :)

@spectrum70 will you be able to address migration of this PR to the new hardware model?https://docs.zephyrproject.org/latest/hardware/porting/board_porting.html#transition-to-the-current-hardware-model

@spectrum70 ping?


[FEATURE]

Please add a detailed description of the feature you would like added
1: Battery icon remains completely filled even when battery percentage is low or are any random number, it should fill according to battery percentage like original iOS 16.x
2: While charging Bolt icon/symbol should be inside the the battery icon like original iOS 16.x style.
3: Newly added preference page in iOS settings is getting crashed randomly.

Add a toggle to revert back to the old battery fill method


add PER support

Hi,
I implemented the Prioritized Experience Replay (PER) described in the MuZero paper, where the priority of each transition is calculated according to the difference between the predicted value and true n-step target value. In the replay buffer, the game_history is sampled according to game priority, which is the mean of all the transition priorities in the game_history. Then the position is sampled according to transition priorities. The priorities are calculated in the update_weights() function, which is then updated in the replay_buffer. update_priorities() function.
Let me know if it looks good to you!

Hi,
Thank you, I was just working on it.
I created a branch to continue the work on it.
I just have a question on one line:
Why did you choose 'wrap' mode in numpy.put() ? I may be wrong but I have the impression that the probability of the absorbing states is out of bound and overwrites the probabilities at the beginning of the list.
Also do you have a reference for the mean?
I tried to list the things that still have to be added. I'm going to work on it, feel free to contribute.

Make an option to choose whether or not to use the priority replay. (I will commit it soon)
Add the loss scaling using the importance sampling ratio. (I'm having trouble figuring out how to do this without turning the buffer into a very long list with all the steps of each game)
Maybe assign an initial value of probabilities based on the loss of root.value and the predicted value in MCTS (or 1 as you did, could be a parameter).
Add the possibility of adjusting alpha.
Find a way to avoid duplicating support_to_scalar

Here are the references on which I work, I am interested if you have other references:
PRIORITIZED EXPERIENCE REPLAY
DISTRIBUTED PRIORITIZED EXPERIENCE REPLAY


built docker image on Umbrel, but failing to load

Built docker image fine. Lot of module errors and fails to load. Is Warden meant to run on Umbrel/RaspPi4?

Not yet. Need to test and run on Umbrel - development has started but should not be able to currently built.
Alternatively, you may ssh into the Umbrel machine and install WARden. Or, preferably, install it at a different machine then just point WARden to connect to Specter Onion address.
Install:
git clone https://github.com/pxsocs/warden
cd warden
python3 -m pip install -r requirements.txt

Then run the WARden server:
python3 warden

Ah ok, thank you very much


Added a boolean prop which will determine if to ask media permission on mount.

#25 #26 #39

@github-id01 thanks a lot!


/vagrant/artifacts/tls/admin.pem: no such file or directory

==> master:
==> master: Switched to context "local".
==> master: Remote command execution finished.
==> master: Configuring Kubernetes DNS...
==> master: Executing remote command "/opt/bin/kubectl create -f /home/core/dns-controller.yaml"...
==> master:
==> master:
**```
==> master: Error in configuration:
==> master: * unable to read client-cert /vagrant/artifacts/tls/admin.pem for default-admin due to open /vagrant/artifacts/tls/admin.pem: no such file or directory
==> master: * unable to read client-key /vagrant/artifacts/tls/admin-key.pem for default-admin due to open /vagrant/artifacts/tls/admin-key.pem: no such file or directory
==> master: * unable to read certificate-authority /vagrant/artifacts/tls/ca.pem for default-cluster due to open /vagrant/artifacts/tls/ca.pem: no such file or directory
==> master: Remote command execution finished.
The remote command "/opt/bin/kubectl create -f /home/core/dns-controller.yaml" returned a failed exit
code or an exception. The error output is shown below:
Error in configuration:

unable to read client-cert /vagrant/artifacts/tls/admin.pem for default-admin due to open /vagrant/artifacts/tls/admin.pem: no such file or directory
unable to read client-key /vagrant/artifacts/tls/admin-key.pem for default-admin due to open /vagrant/artifacts/tls/admin-key.pem: no such file or directory
unable to read certificate-authority /vagrant/artifacts/tls/ca.pem for default-cluster due to open /vagrant/artifacts/tls/ca.pem: no such file or directory

How should i deal with it? Thank you.

Are you running this on Windows?

yes, your OS？

MacOS.
Can you repeat the setup and share the entire log here? The TLS artifacts should've been generated when provisioning the master node.

{ kubernetes-vagrant-coreos-cluster } master » vagrant up
Bringing machine 'master' up with 'virtualbox' provider...
Bringing machine 'node-01' up with 'virtualbox' provider...
Bringing machine 'node-02' up with 'virtualbox' provider...
==> master: Running triggers before up...
==> master: 2017-05-10 08:30:59 +0100: setting up Kubernetes master...
==> master: Setting Kubernetes version 1.6.2
==> master: Importing base box 'coreos-alpha'...
==> master: Matching MAC address for NAT networking...
==> master: Checking if box 'coreos-alpha' is up to date...
==> master: Setting the name of the VM: kubernetes-vagrant-coreos-cluster_master_1494401473960_5                                                              3633
==> master: Clearing any previously set network interfaces...
==> master: Preparing network interfaces based on configuration...
master: Adapter 1: nat
master: Adapter 2: hostonly
==> master: Forwarding ports...
master: 22 (guest) => 2222 (host) (adapter 1)
==> master: Running 'pre-boot' VM customizations...
==> master: Booting VM...
==> master: Waiting for machine to boot. This may take a few minutes...
master: SSH address: <IP_ADDRESS>:2222
master: SSH username: core
master: SSH auth method: private key
==> master: Machine booted and ready!
==> master: Setting hostname...
==> master: Configuring and enabling network interfaces...
==> master: Exporting NFS shared folders...
==> master: Preparing to edit nfs mounting file.
[NFS] Status: running
==> master: Mounting NFS shared folders...
==> master: Setting time zone...
==> master: Running provisioner: file...
==> master: Running provisioner: file...
==> master: Running provisioner: file...
==> master: Running provisioner: file...
==> master: Running provisioner: file...
==> master: Running provisioner: shell...
master: Running: inline script
==> master: Running provisioner: shell...
master: Running: inline script
==> master: Running provisioner: shell...
master: Running: inline script
==> master: Running provisioner: file...
==> master: Running provisioner: shell...
master: Running: inline script
==> master: Running triggers after up...
==> master: Waiting for Kubernetes master to become ready...
==> master: 2017-05-10 08:41:20 +0100: failed to deploy master within timeout count of 50
==> master: Installing kubectl for the Kubernetes version we just bootstrapped...
==> master: Executing remote command "sudo -u core /bin/sh /home/core/kubectlsetup install"...
==> master: Downloading and installing linux version of 'kubectl' v1.6.2 into /opt/bin. This may                                                               take a couple minutes, depending on your internet speed..
==> master: Configuring environment..
==> master: Remote command execution finished.
==> master: Executing remote command "/opt/bin/kubectl config set-cluster default-cluster --serv                                                              er=https://<IP_ADDRESS> --certificate-authority=/vagrant/artifacts/tls/ca.pem"...
==> master: Cluster "default-cluster" set.
==> master: Remote command execution finished.
==> master: Executing remote command "/opt/bin/kubectl config set-credentials default-admin --ce                                                              rtificate-authority=/vagrant/artifacts/tls/ca.pem --client-key=/vagrant/artifacts/tls/admin-key.                                                              pem --client-certificate=/vagrant/artifacts/tls/admin.pem"...
==> master: User "default-admin" set.
==> master: Remote command execution finished.
==> master: Executing remote command "/opt/bin/kubectl config set-context local --cluster=defaul                                                              t-cluster --user=default-admin"...
==> master: Context "local" set.
==> master: Remote command execution finished.
==> master: Executing remote command "/opt/bin/kubectl config use-context local"...
==> master: Switched to context "local".
==> master: Remote command execution finished.
==> master: Configuring Kubernetes DNS...
==> master: Executing remote command "/opt/bin/kubectl create -f /home/core/dns-controller.yaml"                                                              ...
==> master: Error in configuration:
==> master: * unable to read client-cert /vagrant/artifacts/tls/admin.pem for default-admin due                                                               to open /vagrant/artifacts/tls/admin.pem: no such file or directory
==> master: * unable to read client-key /vagrant/artifacts/tls/admin-key.pem for default-admin d                                                              ue to open /vagrant/artifacts/tls/admin-key.pem: no such file or directory
==> master: * unable to read certificate-authority /vagrant/artifacts/tls/ca.pem for default-clu                                                              ster due to open /vagrant/artifacts/tls/ca.pem: no such file or directory
==> master: Remote command execution finished.
The remote command "/opt/bin/kubectl create -f /home/core/dns-controller.yaml" returned a failed                                                               exit
code or an exception. The error output is shown below:
Error in configuration:

unable to read client-cert /vagrant/artifacts/tls/admin.pem for default-admin due to open /vag                                                              rant/artifacts/tls/admin.pem: no such file or directory
unable to read client-key /vagrant/artifacts/tls/admin-key.pem for default-admin due to open /                                                              vagrant/artifacts/tls/admin-key.pem: no such file or directory
unable to read certificate-authority /vagrant/artifacts/tls/ca.pem for default-cluster due to                                                               open /vagrant/artifacts/tls/ca.pem: no such file or directory

Do you want these? I hope that my understanding is right.

The master was not provisioned correctly. Can you log into the machine and check logs?
vagrant ssh master

If some unit failed, it should show up as soon as you log. You can use journalctl to check the logs for that unit.

I am having similar issues on windows with exact same error. I then tried login to master and after login the output of create and journalctl commands were
core@master ~ $ ls
dns-controller.yaml  dns-service.yaml  kubectlsetup
core@master ~ $ kubectl create -f dns-controller.yaml
The connection to the server localhost:8080 was refused - did you specify the right host or port?
core@master ~ $ journalctl
WARNING: terminal is not fully functional
-- Logs begin at Sat 2017-05-13 02:08:26 GMT-5, end at Sat 2017-05-13 03:03:23 GMT-5. --
May 13 02:08:26 localhost kernel: Linux version 4.11.0-coreos (jenkins@worker-1) (gcc version 4.9.4 (Gentoo Hardened 4.9.4 p1.0, pie-0.6.4) ) #1 SMP Wed May 10 22:35:23 UTC 2017
May 13 02:08:26 localhost kernel: Command line: BOOT_IMAGE=/coreos/vmlinuz-a mount.usr=/dev/mapper/usr verity.usr=PARTUUID=7130c94a-213a-4e5a-8e26-6cce9662f132 rootflags=rw mount.usrf
May 13 02:08:26 localhost kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
May 13 02:08:26 localhost kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
May 13 02:08:26 localhost kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
May 13 02:08:26 localhost kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
May 13 02:08:26 localhost kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
May 13 02:08:26 localhost kernel: e820: BIOS-provided physical RAM map:
May 13 02:08:26 localhost kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
May 13 02:08:26 localhost kernel: BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
May 13 02:08:26 localhost kernel: BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
May 13 02:08:26 localhost kernel: BIOS-e820: [mem 0x0000000000100000-0x000000003ffeffff] usable
May 13 02:08:26 localhost kernel: BIOS-e820: [mem 0x000000003fff0000-0x000000003fffffff] ACPI data
May 13 02:08:26 localhost kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
May 13 02:08:26 localhost kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
May 13 02:08:26 localhost kernel: BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved
May 13 02:08:26 localhost kernel: NX (Execute Disable) protection: active
May 13 02:08:26 localhost kernel: SMBIOS 2.5 present.
May 13 02:08:26 localhost kernel: DMI: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
May 13 02:08:26 localhost kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
May 13 02:08:26 localhost kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
May 13 02:08:26 localhost kernel: AGP: No AGP bridge found
May 13 02:08:26 localhost kernel: e820: last_pfn = 0x3fff0 max_arch_pfn = 0x400000000
May 13 02:08:26 localhost kernel: MTRR default type: uncachable
May 13 02:08:26 localhost kernel: MTRR variable ranges disabled:
lines 1-26

Also, the deployment is working correctly on windows for the branch tag 1.5.7

So the apiserver is not running. I need more logs.

How can i generate more detailed log?

Did someone found a workaround for this problem?

thats the log i got from the master:
master_log.txt

Hello,
I have the same error. On the master there's IMHO an error in kube-certs.service, the script make-certs.sh is called without any args, so it display an help message and exit.

Find the issue: the two shell scripts (in my case) was still in Windows Format, even if I deleted the git directory, run those git global commands and doing git clone again.. I don't know why.
So i fixed the EOL in notepad++ and now the kube-certs service is OK and the vm creation is continuing without errors.

@thefausap open PR please.

@pires Sorry but I never did before :-) How can I do that ?

https://help.github.com/articles/creating-a-pull-request-from-a-fork/

@TheFausap Could you at least update which files had an were malformed? I am facing the same issue

Sorry for the delay, today I will open the PR.

@TheFausap Any word on that PR? Or the files that were malformed?

Hi,
I am too facing the issue for the latest release tag 1.7.4

This resolved for me after I uninstalled minikube.
Others please check and confirm this.

This might caused by make-certs.sh fails.
I noticed my tls/make-certs-*.sh files line ending with CRLF.
Even I configure core.autocrlf to false.
Line ending conversion is forced by .gitattributes below.
* text=auto

https://git-scm.com/docs/gitattributes

When text is set to "auto", the path is marked for automatic end-of-line conversion. If Git decides that the content is text, its line endings are converted to LF on checkin. When the file has been committed with CRLF, no conversion is done.

Hi, I got the same issue, as you said, i tried to run :
Vagrant ssh master, it shows me as following:
On MacOS Hight Seris
$ vagrant ssh master
Last login: Wed Dec  6 19:43:38 GMT-8 2017 from <IP_ADDRESS> on ssh
Container Linux by CoreOS stable (1520.9.0)
Failed Units: 1
<EMAIL_ADDRESS>core@master ~ $

As i described above, i used the stable coreos channel, but after i change to alpha, it is ok now. I am not sure what was wrong.


doc: Encourage everyone to explicitly set HRA scaleTargetRef kind

Ref #1343

Is there an ETA for this PR?
0.26.0 seems to be blocked by this.

@kimxogus Hey! We don't provide any ETA at the moment for anything. If you need 0.26.0 to be released earlier, it would be great if you could give it a shot using our canary image and the chart from the main branch. https://github.com/actions-runner-controller/actions-runner-controller/pull/1371#issuecomment-1210057401

@mumoshu Thanks! 👍

@toast-gear Thanks for reviewing!


[POS-UI] TextField state not updating correctly

Please list the package(s) involved in the issue, and include the version you are using
@shopify/retail-ui-extensions-react v 1.2.0 and 1.3.0
Describe the bug
The general state of Textfield is buggy.

error display state (red color with message) won't remove after setting it to undefined when error is solved
helpText doesn't remove after setting it to undefined
onChange value state change flickers (https://github.com/Shopify/ui-extensions/issues/1284)

Steps to reproduce the behavior:
Do error and helpText in separate tests:

Create a Textfield
Set the value of errors or helpText to a message.
Set the value of error or helpText to undefined.
Error and helpText keep showing after changing to undefined.

Expected behavior
When error is set to undefined, the error state should disappear. (Red color + message)
When helpText is set to undefined, the helpText should disappear.
onChange to update value state shouldn't flicker (Related ticket: https://github.com/Shopify/ui-extensions/issues/1284)
Additional context
I'm using both IOS and Android devices in a test store and CLI preview.

Hi @pkhanal, thanks for the response. I still have this experience where the error and helpText won't go away even when the state variable I'm using is set to undefined. The visual indication of the error or the helpText stays.
I'm using @shopify/retail-ui-extensions-react v1.3.0
Version 1.4.0 is not available. It jumped from 1.4.0rc3 to 1.5.0rc0 and now 1.5.0rc1

https://www.npmjs.com/package/@shopify/retail-ui-extensions-react?activeTab=versions


Remove sample callback (second part of DFCT0010080)

What does this PR do and why?
Describe in detail what your merge request does and why.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other pull requests.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
PR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

[ ] I have evaluated the PR acceptance checklist for this PR.

@ChrisHuynh333 did this better in #629


Frequency domain corrections for nth octave spectrum and screening for tones functions

The function noct_synthesis and noct_freq_filter have been enhanced for better accuracy compared to the filtering in time domain. The function butter and sosfreqz from scipy.signal are used.
In time domain, the use of a,b filter representation have been replaced by sos to improve the performance of noct_spectrum.
The function screening_for_tones has been corrected to correctly detect a potential peak on the first index
The function spectrum_smoothing now takes as input a spectrum of  dimension (nperseg, nseg) as the rest of the functions

All the tests are running without any warning.
Tks :)

Thank you for your contribution


Align class event handler creation with React docs

This is small change to align example React app with current advised way of assigning
event handlers that are declared as ES6 class methods:
https://reactjs.org/docs/handling-events.html
Thanks!

@SteveSandersonMS another one for you.

Thanks @peterblazejewicz! This is now merged.


🔥 cleanup: remove setup.ps1 powershell script

The setup script is no longer needed as the installation process has been completed.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (3206660) to head (300aa60).
Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #491   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           30        30
  Lines          313       313
  Branches        82        82
=========================================
  Hits           313       313

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


CLID-160: upgrade distribution/distribution to the latest released version

Currently in oc-mirror it is not possible to upgrade containers/image dependency because of the indirect dependency on library-go. The upgrade of containers/image is required to fix CVE-2024-3727
In order to upgrade the containers/image it is required to upgrade the distribution/distribution version in the library-go. Before this PR the library-go was depending on a non released version of distribution/distribution v3.0.0-20230511163743-f7717b7855ca. This PR upgrades the library-go to the latest v3 release version.
Since code required by library-go was removed from the latest released version of distribution/distribution, the required code was copied as a new package (pkg/registry) on the library-go

/jira refresh

Closing this PR as it looks like there is no interest in merging it.


Preparation of GCWeb to allow design token integration

TODO

[ ] Prepare a demo showing the current situation
[ ] Remove the double integration layer of wet-boew that import bootstrap3
[ ] Reorganize how SASS file are imported and override style. Ensure happen as expected and utility CSS are added at the end.
[ ] Group and identify override

[ ] For each: Clean up override

[ ] Update the build script to automate the SASS integration
[ ] Perform a visual test of each components to ensure they still work as expected

[ ] For each: Fix reported issue

[ ] Validate and indicate where design token can be integrated

Outcomes

Improved CSS integration in GCWeb which should reduce the size of the CSS file and unessary browser override
Integration of design token without requiring to apply an override

Deliverable

Intruction on how to integrate design token
Removal of the double CSS framework interdependance (GCWeb -> wetboew and GCWeb -> Bootstrap)

Out of scope

New style or dependancy upgrade
Documentation of currently undocumented style

Démo
The following is the presenter notes
1. CSS Dependency
Currently: GCWeb -@import-> wet-boew -@import-> bootstrap
First mod: GCWeb -@import-> wet-boew -and- bootstrap
Keys files

GCWeb - Main entry - https://github.com/wet-boew/GCWeb/blob/master/sites/theme.scss
wet-boew - Bootstrap - https://github.com/wet-boew/wet-boew/blob/master/src/base/_bootstrap.scss
Bootstrap - Main entry - https://github.com/twbs/bootstrap-sass/blob/master/assets/stylesheets/_bootstrap.scss
wet-boew - Baseline and components - https://github.com/wet-boew/wet-boew/blob/master/src/base/_wet-boew.scss
GCWeb - wet-boew overrides - https://github.com/wet-boew/GCWeb/blob/master/components/baseline/wet-boew-overrides.scss

2. Issue
Show the CSS rules override like font-size from the browser console
Any future change, like applying design token, will require an override, which slow down the performance of the website
3. GCWeb version 5
Explain the technical challenges
4. Overview of the proposed changes
5. Open discussion

PR in wet-boew was approved and PR in GCWeb was submitted: https://github.com/wet-boew/GCWeb/pull/1897
We are initiating the testing today which will be coordinated by @GormFrank

pr merged today

Those update is not included in the latest version of GCWeb v10.0.1.
So when the design token will be ready, we would be able to experiment it also with GCWeb.
During this exercise, we can now use this file to easily find all the component included in GCWeb.: https://github.com/wet-boew/GCWeb/blob/master/sites/theme.scss