opt let column dist info check msg same with legacy planner

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Cashe still warming up notice, plus crashing

elementum latest update running  on Android.Adding torrents possible but searching for shows or movies result in infinite loading/ search does it also.
Backing out of Kodi or trying to access elementum or burst settings result in crash.
Sorry even more issues appeared I'll follow the guide and try to do it right

When you create an issue - there is a template. And it is there for a reason :-) It has a link to "how to create a debug log", for example, also info about versions, environment and etc.

Closing due to no log provided.


Fix flaky test

see https://github.com/hardkoded/playwright-sharp/runs/668927169
PlaywrightSharp.Tests.RequestInterception.PageSetRequestInterceptionTests.ShouldWorkWithEqualRequests is flaky.
in playwright this fixed this in version v0.12.0

see here https://github.com/microsoft/playwright/compare/v0.11.0...v0.12.0#diff-7ff6d7fc2247e88768a12321914b9a2bL247-R259
I think it's worth it fixing this now

@kblok what do you think?

@Meir017 yeah, let's do it.


feat: remove support for baseFlags

Remove support for baseFlags
Currently, in order for one Command class to inherit flags from another Command class is to use a property called baseFlags (see docs).
This solution assumes that you'll only ever have one layer of abstraction, which is not a safe assumption. So in order for commands to inherit flags from multiple parents you have to use the spread operator
import {Command, Flags} from '@oclif/core'

abstract class BaseCommand1 extends Command {
  static baseFlags = {
    loglevel: Flags.boolean()
  }
}

abstract class BaseCommand2 extends BaseCommand1 {
  static baseFlags = {
    ...BaseCommand1.baseFlags,
    verbose: Flags.boolean()
  }
}

abstract class BaseCommand3 extends BaseCommand2 {
  static baseFlags = {
    ...BaseCommand2.baseFlags,
    silent: Flags.boolean()
  }
}

export default class MyCommand extends BaseCommand3 {
  static flags = {
    username: Flags.string()
  }
}

Because of this, we're removing baseFlags and requiring the spread operator anytime you want flags to be inherited. So the above example would change to this:
import {Command, Flags} from '@oclif/core'

abstract class BaseCommand1 extends Command {
  static flags = {
    loglevel: Flags.boolean()
  }
}

abstract class BaseCommand2 extends BaseCommand1 {
  static flags = {
    ...BaseCommand1.flags,
    verbose: Flags.boolean()
  }
}

abstract class BaseCommand3 extends BaseCommand2 {
  static flags = {
    ...BaseCommand2.flags,
    silent: Flags.boolean()
  }
}

export default class MyCommand extends BaseCommand3 {
  static flags = {
    ...BaseCommand3.flags,
    username: Flags.string()
  }
}

The downside is that it will require an extra line of code for those who are only using a single base Command class but the upside is that there won't be any confusion about the difference between baseFlags and flags and when to use each.
Other Changes

Use https://github.com/oclif/test/pull/550
Improve test coverage

@W-15470630@

I don't see a major bump in pjson, or in commit messages - did I miss it?

This is going into the prerelease/beta branch which has the major version bump in it


Enable / desable notification

How would you make a checkbox to turn off notifications?

That would be awesome!

Would be great. +1 for that!

+1 here


Added PR Number overriding

Added an input for PR_NUMBER. This allows workflows to override what PR (and maybe issue) the action is commenting on.

Testing workflow commenting


[REQUEST/IDEAS]

Hello. So I just found fork and so far I'm loving it. I did have an idea for it though.
Is there any plans of releasing a Web Panel for server hosts that might want to use fork?

Yes will be a core part of the Fork recode -> https://github.com/ForkGG/Fork


doc: Readme update.

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

Project coverage is 100.00%. Comparing base (267de3a) to head (ebecda8).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##              main       #32   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           14        14
  Lines         1412      1412
  Branches       119       119
=========================================
  Hits          1412      1412

Flag
Coverage Δ

unittests
100.00% <ø> (ø)

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

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


Deprecate/Remove opencensus tracing support

Now that Opentelemetry is getting closer to being a stable release, we can remove/deprecate openCensus tracing support.

Closed with #7167


DB Name start with Numeric; Procedure is not visible in Database Navigator Panel.

I am facing an issue while viewing of procedures on UI database Navigator. It happens where the DBNAME start with Numeric and followed by alphabets.
To recreate the issue:

Create database using snowflake Datawarehouse. start with "1test". (Database name must start with numeric.)
Create a procedure in same database with any name you want.
Check Database Navigator panel, select newly created database. select procedure dropdown.
You won't be able to see the procedure which you just created above.
we can run or access the procedure by SQL editor. Doing query on top of this procedure.

I want to see the procedure in database navigator where DB name start with Numeric.

Hello @jdabhi-hah
Sorry for the late response. Ticket reopening can lead to it.
Could you please clarify this step?

Create a procedure in the same database with any name you want.

Did you try to refresh the navigator view after the procedure was created?

For now, I can't reproduce your issue.

Oh. that's weird.
I have one request here.
Can you create a schema name which start like '1up'. then try to create SP in that schema. Now, can you see the procedure inside that schema?

Hello @jdabhi-hah
Sorry for the late response. Ticket reopening can lead to it.
Could you please clarify this step?

Create a procedure in the same database with any name you want.

Did you try to refresh the navigator view after the procedure was created?

For now, I can't reproduce your issue.

Yes, I am refreshing the DB every time.

Unfortunately still cannot reproduce the issue against 24.1.4

Unfortunately still cannot reproduce the issue against 24.1.4

If you cannot reproduce the issue, feel free to close this issue.

Unfortunately, we can't reproduce the issue.
For now, I'm closing the issue. If we get similar report from another user or reproduce the issue, we will return to it.


proposal: testing: add TB.Chdir

Sometimes a test need to call os.Chdir(). Here is a bare minimum implementation of what's needed from a test to do that:
        oldwd, err := Getwd()
        if err != nil {
                t.Fatal(err)
        }
        if err := Chdir(dir); err != nil {
                t.Fatal(err)
        }
        t.Cleanup(func() {
                if err := Chdir(oldwd); err != nil {
                        // It's not safe to continue with tests if we can't get back to
                        // the original working directory.
                        panic(err)
                }
        })

The code above can be used as a test helper; in fact, this repository already contains at least 5 helpers similar to the one above:

https://github.com/golang/go/blob/1d538f198dd3da072d00e3dca70c28c40bbde87e/src/os/os_windows_test.go#L35
https://github.com/golang/go/blob/1d538f198dd3da072d00e3dca70c28c40bbde87e/src/os/os_test.go#L917
https://github.com/golang/go/blob/1d538f198dd3da072d00e3dca70c28c40bbde87e/src/path/filepath/path_test.go#L510
https://github.com/golang/go/blob/1d538f198dd3da072d00e3dca70c28c40bbde87e/src/path/filepath/path_test.go#L527
https://github.com/golang/go/blob/1d538f198dd3da072d00e3dca70c28c40bbde87e/src/syscall/syscall_linux_test.go#L27

In addition, there are a few in-line implementations of the same functionality, another implementation in golang.org/x/sys/unix and so on.
The problem with this (except for multiple implementations and re-implementations) is, tests that use it  can not use t.Parallel. Currently, there is no way to ensure that.
The issue is very similar to one for os.Setenv (#41260, fixed by https://golang.org/cl/326790); thus the solution is also similar.
The proposal is to add a Chdir method to the testing package, which will take care about all of the above.
The implementation may look like this: https://go-review.googlesource.com/c/go/+/529895

@rsc anything I could do to move it forward?

If tests need to chdir often, then I do think it is worth doing well, in much the same way that t.Setenv did (takes care of undoing, also takes care of not being in parallel tests). That said, I am not sure whether tests need to chdir often enough.
Skimming CL 529896, it seems telling that all the changes are in packages like os, path/filepath, syscall, which are specifically about directories. Tests for code that is not about directories would be more compelling. I will try to gather some data from the open source Go corpus.

This proposal has been added to the active column of the proposals project
and will now be reviewed at the weekly proposal review meetings.
— rsc for the proposal review group

I ran into this recently. If it is helpful: https://github.com/jimmyfrasche/autoreadme/blob/0fbe6087ce8309d209b6e9caf3621e781bc73fcb/autoreadme_test.go
(The program works on go modules in git repos and it needs to run in a directory within such a module and update files in that tree. Normally I would try to mock such things out but that would have increased the complexity of both the code and the tests too much. It was simpler to just have the test cd into mock projects and run the program there and then check the results against golden output. Because the projects contain go.mod in testdata they're stored indirectly in .txtar archives that are expanded into a tmp dir which is not relevant to the issue at hand but explains why there's all those other things happening in the test code.)

This is needed to test any functionality/code that uses relative paths.
You can find many examples of tests that use os.Chdir here: https://sourcegraph.com/search?q=context:global+file:_test.go%24+os.Chdir&patternType=keyword&sm=0
Most of them do the same sequence as in this issue description (save cwd, chdir, defer chdir to saved). Most are not entirely correct as they should panic if Chdir to oldwd failed.
None are preventing running tests using Chdir in parallel, although some warn about it, see eg https://github.com/moby/moby/blob/ceefb7d0b9c5b6fbd1ea7511592a4ddb28ec4821/pkg/idtools/idtools_unix_test.go#L210-L221). This is somewhat hard to implement as you'd need a wrapper around t.Parallel.

Took me longer than expected but I finished scanning the latest versions of each module in the proxy cache. Overall there are 8756664 _test.go files, and 23963 files mention os.Chdir, or about 0.27%. It's not high, but we didn't expect it to be that high. The next question is whether os.Chdir is really necessary in those tests. I sampled 20 at random (numbers 1..20 in the sampled results here) and found:

1 unnecessary substitute for filepath.ResolveSymlinks (2)
4 not strictly necessary but helpful (1, 7, 8, 15)
15 necessary (3, 4, 5, 6, 9, 10, 11, 12, 13, 14, 16, 17, 18, 19, 20)

And 5 (25%) forgot to chdir back, which could break other tests (5, 10, 12, 16, 18).
It still doesn't come up often, but when it does it's difficult to get right. I think it is reasonable for the testing package to help, in the same way that it helps with os.Setenv.

Based on the discussion above, this proposal seems like a likely accept.
— rsc for the proposal review group
The proposal is to add a method Chdir(dir string) to to testing.T, testing.B, testing.TB.
The method calls t/b.Fatal if the chdir fails.
It also calls t/b.Fatal if called during a parallel test.
It also makes sure to restore the previous current directory when the test finishes.
Internally, it can use Open(".") and os.Fchdir.
It should probably also call t.Setenv to set $PWD, like os/exec does when Dir is set.

No change in consensus, so accepted. 🎉
This issue now tracks the work of implementing the proposal.
— rsc for the proposal review group
The proposal is to add a method Chdir(dir string) to to testing.T, testing.B, testing.TB.
The method calls t/b.Fatal if the chdir fails.
It also calls t/b.Fatal if called during a parallel test.
It also makes sure to restore the previous current directory when the test finishes.
Internally, it can use Open(".") and os.Fchdir.
It should probably also call t.Setenv to set $PWD, like os/exec does when Dir is set.

Why wasn't this issue closed as fixed by https://go-review.googlesource.com/c/go/+/529895? cc @kolyshkin @ianlancetaylor

I think it was left open to start using it in the standard library.  But let's close it now.  Thanks.


Systemd-resolve workaround for Ubuntu 18.

Description
Bug fixing
Sometimes, stub DNS for systemd-resolve does not work properly, and it is not possible to determine what exactly is happening. It looks like a bug in systemd-resolve service.
Related issue:
https://github.com/actions/virtual-environments/issues/798
Check list

[+] Related issue / work item is attached
[ ] Changes are tested and related VM images are successfully generated

I have deployed Ubuntu 18 agent with the workaround and it works fine.

Do you know the root cause why default systemd-resolve doesn't work properly?
you mentioned that it is workaround. If so, when it can be removed?

Do you know the root cause why default systemd-resolve doesn't work properly?
you mentioned that it is workaround. If so, when it can be removed?

Agree, @Darleev could you please provide some more data about the issue? Maybe some similar issues links.

Do you know the root cause why default systemd-resolve doesn't work properly?
you mentioned that it is workaround. If so, when it can be removed?
@miketimofeev @maxim-lobanov
Let me describe my findings below:

There is Github issue, with exactly the same problem, which was not fixed, only workaround was provided as solution.
Root cause is unclear.
I'm not sure that we can remove systemd-resolve without effects. but we can disable it by default. However, in this case, it is required to add manually nameserver record to /etc/resolv.conf file.
In the official documentation, I didn't find misconfigurations.

So, why workaround was added as solution? - This is simple solution, without any effects and further support is not required for this workaround.


Feature: Add page showing Hour/Daily gas and fee volumes

Summary
Service has an API to fetch gas and fee volumes on an hourly or daily basis. We should show those metrics
Proposal

[ ] Add page for Gas and Fee Volume
[ ] Using api/v2/gas/volume?fromDate=2022-01-20&toDate=2022-01-25&granularity={HOUR/DAILY}

[ ] Add graph for gas volume, toggle on HOURLY or DAILY with date filter
[ ] Add graph for fee volume, toggle on HOURLY or DAILY with date filter

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

closed via PR #285


⚠ Guya.moe Proxied has degraded performance

In 79fd3cc, Guya.moe Proxied (https://ice.guya.moe/) experienced degraded performance:

HTTP code: 200
Response time: 11919 ms

Resolved: Guya.moe Proxied performance has improved in e3b7628 after 1 hour, 18 minutes.


Question : Is this good practice ?

Hi, if I wanted to store the underlying view inside a variable that can be accessed later, is below code good practice ?
struct ContentView: View {
    @State var content: String = ""
    @State var _textField:UITextField?

...
TextField("Content", text: $content)
.introspectTextField { textField in
                            print("debug")
                            _textField=textField
  }

so that later I can call that _textField?.becomeFirstResponder() like
Button(action: {
    _textField?.becomeFirstResponder()
}) {
    Text("Focus it")
}

Will the _textField become memory leak ?
Thanks for answering

Perhaps it's better to keep a weak reference

Perhaps it's better to keep a weak reference

Hi @x4080, that hugely depends somehow on how you use it. In your ContentView, if this is the main struct of the app, it will obviously never be removed, but that is also expected, right? Also, if you store a view behaving like this somewhere, it will also never be initialized, but that is rather a problem with that code then.
Assuming it is a view that gets shown and also disappears at some point, it depends on the underlying structure of SwiftUI. That said the structure would have to be very strange for this to become a memory leak.
I have tested this with the current version of SwiftUI in Xcode 12.4 and iOS 12.4 with the following Code:
struct ContentView: View {

    @State var isModalShowing = false

    var body: some View {
        Text("Hello, World!")
            .onTapGesture {
                self.isModalShowing.toggle()
            }
            .sheet(isPresented: $isModalShowing) {
                ModalView()
            }

    }
}

class TestObject {
    init() {}

    deinit {
        print("deinitialized")
    }
}

struct ModalView : View {

    @State private var usernmae =  "hello"
    @State var textField: UITextField?
    @State var testObject: TestObject?

    var body : some View {
        VStack(alignment: .leading) {
            TextField("test", text: $usernmae)
                .introspectTextField { textField in
                    print("setting:", textField)
                    self.textField = textField
                    self.testObject = TestObject()
                }

        }
        .padding(.horizontal, 50)
    }
}

It prints:
setting: <SwiftUI.SwiftUITextField: 0x16090a800; baseClass = UITextField; frame = (0 0; 290 22); text = 'hello'; opaque = NO; gestureRecognizers = <NSArray: 0x60000073e0d0>; placeholder = test; borderStyle = None; background = <_UITextFieldNoBackgroundProvider: 0x600000bb4af0: textfield=<SwiftUI.SwiftUITextField 0x16090a800>>; layer = <CALayer: 0x600000904320>>

deinitialized

Seeing that the deinitialized does get printed when the view is dismissed, the current version of SwiftUI will not create a memory leak because of this practice.
I hope this answers your question. I will close this issue for now.
PS: @MohammadNjf's solution doesn't work since state variables cannot be weak. You could create an object that has a weak reference to it though.

@JannThomas Thanks


Update flake packages workflow is failing

I configured a gpg key as per #165 but the workflow is failing with a gpg error:
Run crazy-max/ghaction-import-gpg@v5
GnuPG info
GPG private key info
  Fingerprint  : F968BDB6099B7FCA8328B1EACBF5A8D24A6CD4E8
  KeyID        : CBF5A8D24A6CD4E8
  Name         : Bottie McBotFace
  Email<EMAIL_ADDRESS>  CreationTime : Thu Mar 16 2023 14:49:41 GMT+0000 (Coordinated Universal Time)
Fingerprint to use
Importing GPG private key
  gpg: directory '/home/runner/.gnupg' created
  gpg: keybox '/home/runner/.gnupg/pubring.kbx' created
  gpg: /home/runner/.gnupg/trustdb.gpg: trustdb created
  gpg: key CBF5A8D24A6CD4E8: public key "Bottie McBotFace (Bot Account<EMAIL_ADDRESS>imported
  gpg: To migrate 'secring.gpg', with each smartcard, run: gpg --card-status
  gpg: key CBF5A8D24A6CD4E8: secret key imported
  gpg: Total number processed: 1
  gpg:               imported: 1
  gpg:       secret keys read: 1
  gpg:   secret keys imported: 1
Configuring GnuPG agent
Getting keygrips
  Presetting passphrase for 25679D6ACD61BCB318735E720E08CBED3372F061
Error: ERR 67108891 Not found <GPG Agent>

So strange, it works perfectly in my own fork, I will check that.

Seems like you use a subkey to sign a commit, so it's related to https://github.com/crazy-max/ghaction-import-gpg/issues/119.
We need to add gpg-fingerprint to our action. Can you provide it via GPG_FINGERPRINT secret please?


EVEMonDevelopmentTeam.EVEMon version 4.1.3

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

I'm not sure where this is failing.

@denelon Is it possible to get more verbose errors? I think the issue is that this app needs .NET to run/install but I'm not entirely confident on it.

also, the site for smartscreen submissions seems to have changed. now it forces you to give it a malware or PUA detection name, which doesn't apply to the way winget submissions used to require it.

You can drill into the Azure DevOps build results and download artifacts. This is what I see:
{
  "OverallResult": "Failure",
  "TestPlansResults": [
    {
      "TestPlan": "Validation-Installation-Error",
      "Result": "Failure",
      "Metadata": "",
      "ResultMetadata": {
        "Message": "-1978335226",
        "FieldsMetadata": [
          {
            "Field": "Exit Code",
            "Message": "-1978335226"
          },
          {
            "Field": "Architecture",
            "Message": "x86"
          },
          {
            "Field": "Scope"
          },
          {
            "Field": "Locale"
          }
        ]
      }
    }
  ],
  "AnalysisResults": []
}

same error code "-1978335226" happened again. i can't find anything online about this, but this error code popped up a few times for other apps submitted to winget without resolution. the common denominator here is that it seems like app installers built with visual studio are affected? i don't have VS installed right now to check what kind of project type it is, but I believe this app still uses .net framework 4.0.


[BUG] Wrong date on one node creates an error expired event which can't be deleted

Describe the bug
We had an incident with one node on our Service Fabric cluster. The system date of the server was changed to the future. We fixed this issue, but Service Fabric still has an OK event in the future that cause an error on the partition that run the system service fabric:/System/FailoverManagerService.
On the 14/08/2024 one of the node had the date changed to 29/09/2024 for about 5 hours before fixing the date. The node is a normal node (not seed).
Error :
PS D:\> Get-ServiceFabricPartitionHealth

cmdlet Get-ServiceFabricPartitionHealth at command pipeline position 1
Supply values for the following parameters:

PartitionId           : 00000000-0000-0000-0000-000000000001
AggregatedHealthState : Error
UnhealthyEvaluations  :
                        The OK reported by 'System.FMM' for property 'State' is expired. The report was applied at 2024-08-14 01:00:27.218 with TTL 15:00.000.
                        Partition is healthy.

ReplicaHealthStates   :
                        ReplicaId             :<PHONE_NUMBER>22355426
                        AggregatedHealthState : Ok

                        ReplicaId             :<PHONE_NUMBER>08971912
                        AggregatedHealthState : Ok

                        ReplicaId             :<PHONE_NUMBER>22355427
                        AggregatedHealthState : Ok

HealthEvents          :
                        SourceId              : System.FMM
                        Property              : State
                        HealthState           : Ok
                        SequenceNumber        :<PHONE_NUMBER>40404006
                        SentAt                : 29/09/2024 07:22:04
                        ReceivedAt            : 14/08/2024 01:00:27
                        TTL                   : 00:15:00
                        RemoveWhenExpired     : False
                        IsExpired             : True
                        HealthReportID        : FMM_7.0_1009
                        Transitions           : Warning->Ok = 12/07/2024 22:50:20, LastError = 01/01/0001 00:00:00

HealthStatistics      :
                        Replica               : 3 Ok, 0 Warning, 0 Error

Area/Component:
Partition that run the system service fabric:/System/FailoverManagerService
To Reproduce
Steps to reproduce the behavior:

Update the date of one node  fare to the future.
The cluster should receive events from this node with the date on the future.
Fix the date on this node.
The partition will have the error : The OK reported by 'System.FMM' for property 'State' is expired...

Expected behavior
Fixing the date on the node should generate new events that fixes the error event.
Observed  behavior:
The cluster status is error. This block Service Fabric package updates.
Screenshots

Service Fabric Runtime Version:
9.1.1390.9590
Environment:

Standalone
OS: Windows Server 2016
Version 9.1.1390.9590

If this is a regression, which version did it regress from?
Additional context
We tried to restart VMs.
We tried also to send a partition health report Send-ServiceFabricPartitionHealthReport -PartitionId 00000000-0000-0000-0000-000000000001 -SourceId "System.FMM" -HealthProperty "State" -HealthState Ok -TimeToLiveSec 30 -RemoveWhenExpired
Also a repair : Repair-ServiceFabricPartition -PartitionId 00000000-0000-0000-0000-000000000001
There's no way we can reset the event status

Assignees: /cc @microsoft/service-fabric-triage

Same here. It is present on our 10.0.1949.9590 single node cluster and is still there after updating it to 10.1.2338.9590.


perf(request-id): use proxy_set_header instead of lua api set_header

Summary
If we utilize the nginx original directive proxy_set_header X-Kong-Request-Id $kong_request_id instead of lua source code set_header(Kong-Request-Id ,request_id), we can enhance the QPS by ~2% in the testing scenario where no plugins are used and pure http proxying is deployed.
And there are no set_header calls within the core path. All the headers that are added to the upstream are currently configured using the proxy_set_header directive.

Checklist

[x] The Pull Request has tests

Reuse old test cases. The functionality hasn't been modified

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

Full changelog

This PR replaces the lua api call of set_header with proxy_set_header.

Issue reference
KAG-2814

The transmission of the X-Kong-Request-ID to the upstream or downstream is contingent on the configurations specified in kong.conf (the headers and headers_upstream settings).

yea get it. I have changed this pr's state to draft. I'm trying to resolve this problem

I also find there is another invoke of request_id_get() in handler.lua, could we replace it with the directive add_header?
If we have not enough time we could do it in next PR.

I also find there is another invoke of request_id_get() in handler.lua, could we replace it with the directive add_header?
If we have not enough time we could do it in next PR.

yea, could evaluate it later. I looked it briefly that we didnt use add_header directive in nginx-kong.conf and most of add_header logic was implemented via ngx.header[k] = v in kong , so I do not modify this one in this pr.

Should https://github.com/Kong/kong/blob/master/spec/fixtures/custom_nginx.template be updated too?

Its uncessary to modify nginx.conf , only nginx-kong.conf needs to be fixed.


Support sending email and SMS in 'util.py'

I'm closing this pull request. Please submit another one after new requirements are met


1.9.0: More plain Result features

add WasmJS target
add WasmWasi target
add wrappingPlain, which works just like wrapping but on a Result rather than a KmmResult to avoid instantiation overhead
rename catchingUnwrapped to catchingPlain to avoid confusions with wrapping but keep the old name as deprecated alternative
add nonFatalOrThrow

@JesusMcCloud ready for review

track KT-72600 for contract boilerplate

track KT-72601 for @Suppress hackery

will release on Monday evening, unless someone objects


operator apicurio-registry (1.1.0-v2.4.12.final)

Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions

[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?

[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want use semantic versioning order?
[ ] Is your submission signed?
[ ] Is operator icon set?

Updates to existing Operators

[x] Did you create a ci.yaml file according to the update instructions?
[x] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[x] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description about the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

Please wait on https://github.com/redhat-openshift-ecosystem/community-operators-prod/pull/3404 to be ready as well.

/merge possible

/merge possible

/merge possible

/merge possible


Counter set values

Hi,
I'm testing library with influxDB <IP_ADDRESS> (last Windows release).
I've noticed that the library doesn't save values for counter set items
(as in example from https://github.com/etishor/Metrics.NET/wiki/Counters - Counting values from a set).
I think problem may lay in following lines in InfluxDbReport.cs:
var itemValues = value.Items.SelectMany(i => new [] { i.Count, i.Percent });
foreach (var data in new[] {(double) value.Count}.Concat(itemValues)) {
       Pack (name, columns, data, tags);
}

The foreach loop will call
private void Pack (string name, IEnumerable<string> columns, object value, MetricTags tags)
method, which can add only one value for counter set.
I've changed counter reporting code for:
var itemValues = value.Items.SelectMany (i => new object[] { i.Count, i.Percent });
Pack(name, columns, (new[] { (object)value.Count }.Concat(itemValues)), tags);

to get set values saved in db.
Are there any better ways to handle such case?

Thanks, I see the issue now. I'm currently reworking how the data is
represented in Influx, and will address this with those changes.
On Mon, Jan 4, 2016 at 9:07 AM, marcinsikora<EMAIL_ADDRESS>wrote:

Hi,
I'm testing library with influxDB 0942 (last Windows release)
I've noticed that the library doesn't save values for counter set items
(as in example from https://githubcom/etishor/MetricsNET/wiki/Counters -
Counting values from a set)
I think problem may lay in following lines in InfluxDbReportcs:
var itemValues = valueItemsSelectMany(i => new [] { iCount, iPercent });
foreach (var data in new[] {(double) valueCount}Concat(itemValues)) {
Pack (name, columns, data, tags);
}
The foreach loop will call
private void Pack (string name, IEnumerable columns, object value,
MetricTags tags)
method, which can add only one value for counter set
I've changed counter reporting code for:
var itemValues = valueItemsSelectMany (i => new object[] { iCount, iPercent });
Pack(name, columns, (new[] { (object)valueCount }Concat(itemValues)), tags);
to get set values saved in db
Are there any better ways to handle such case?
—
Reply to this email directly or view it on GitHub
https://github.com/mnadel/metrics.net.influxdb/issues/5.

Fixed in latest 2.x prelease on NuGet. Note that this is not backwards compatible w/ the 1.x series. See Changelog section of README.md.


Create BindingProperties and Converter to replace the current Map-based logic

LGTM, squashed and merged as 10c1f5051cd427ddd76a6968b0aa81eecf26e859


Add a function to extract specific line from TextLines?

I'm currently looking at implementing some functionality in haskell language server which uses this library.
I would like to implement something like
getTextAtRange :: LSP.Range -> Rope -> Maybe Text
and
getLine :: Word -> TextLines -> Maybe Text
With the current api I can do it like this

Rope.lines r and then index to the resulting list (I assume this is inefficient - linear time in number of lines?)
Use Rope.splitAtLine twice (example of this in hls: https://github.com/haskell/haskell-language-server/blob/50923e5c790e9c55c2b9b1bfcc8e78f7169f8ea3/ghcide/src/Development/IDE/Plugin/Completions/Logic.hs#L907-L908) - this seems like more efficient way to achieve that, but not very convenient.

What do you think about adding few high-level helpers like this to the library?

I'd prefer
getLine :: Word -> Rope -> Text
getRange :: Position -> Position -> Rope -> Text

and same for TextLines instead of Rope, but let's wait for #4 to land first.

Great, I'm not in a hurry to implement it.
Just a question about your proposed types:
Wouldn't it make more sense to wrap the return types within Maybe?
You know, to distinguish between cases where given Word / Position x Position are "out of bounds"?
getLine 0 "hello" == Just "hello"
getLine 1 "hello" == Nothing

@jhrcek #4 has landed, so feel free to take a stab at this issue.
I'd prefer to keep new functions consistent with existing split* functions, which do not return Maybe.

Thanks, will look into it in the next few days.

Is there still an interest to work on getTextAtRange? Or shall I get HEAD released as is?

I think it would be very useful.
There are bunch of places in hls which would benefit from this and I believe using ready-made helper from text-rope would improve correctness in many places, which are currently extracting text using char-based indexing.
But I won't have time in the near future to implement it, so I think you can release HEAD as is.

Thanks, I released https://hackage.haskell.org/package/text-rope-0.3


Font component's glyph is not loaded in after serialization

fix via https://github.com/xubury/SDEngine/commit/a8becad30a0015cc6fd3660a91438c12f54b096a.
Fonts are loaded in through a .font file


Landing page Mobile Layout

The cards needs to take full size in mobile view. Also, the backdrop should be cropped in mobile view

closed #a4147404767446ddc6d2206fc1f11099ee5eaf8e


Find previously deployed to managed environment and recommend them

I toyed with the idea of using grouping instead of description. Not sure if we want to go that route though in case we started grouping things by resource group or something.
Also supressedPersistence because the (recently used) description looks kind of silly with recommended.

Also supressedPersistence because the (recently used) description looks kind of silly with recommended.
Lol that's funny I also added this same thing to my PR because it was bothering me too 😂


Dump logs upon failure in CI

Signed-off-by: Bruno Vavala<EMAIL_ADDRESS>

Per our discussion, dumping logs in the run-tests cleanup subroutine may be more appropriate.
However, the contracts/wawaka makefile still has to be updated not to discard logs.
Will open a new pr for that.


Twig support in frontmatter broken

As per our previous conversation @rhukster, Twig support in frontmatter must have been broken by a previous update.
Currently the following code:
---
area_name: 'South London'
new_var: '{{ site.title }}'
---
{{ site.title }}

The page.content reports the correct site.title however, page.header.new_var does not process the twig.

just tested with:
---
area_name: 'South London'
new_var: '{{ site.title }}'
process:
    twig: true
---

{{ site.title }}

{{ page.header.new_var }}

both output the title just fine.
Check to make sure you have page.frontmatter.process_twig: true in your system settings. Best way is to turn on debugger and look there:


Fix comment in DetachRelationship

Thanks for the PR!

The tests are failing, something to do with a Laravel 9 change most likely. Nothing to do with what youv'e done so I'll merge this PR anyway.


K8SPXC-408 Set monitor user max connections to 100

Test name
Status

init-deploy
passed

scaling
passed

recreate
passed

storage
passed

big-data
passed

self-healing
passed

limits
passed

scaling-proxysql
passed

restore-to-encrypted-cluster
passed

upgrade
passed

monitoring
passed

self-healing-advanced
passed

upgrade-consistency
passed

security-context
passed

operator-self-healing
passed

monitoring-2-0
passed

demand-backup
passed

affinity
passed

one-pod
passed

auto-tuning
passed

scheduled-backup
failed

proxysql-sidecar-res-limits
passed

users
passed

demand-backup-encrypted-with-tls
failed


add jupyter-structured scripts

This pull request adds the scripts to transform the jupyter notebooks from the stack into the jupyter-structured dataset used by Starcoder.

I have updated the readme.md files both in the main folder and the preprocessing folder. Correctly formatted scripts are now uploaded.

Thanks!


enroot+pyxis

install enroot on compute nodes
added scheduler and login cluster-inits
update template for new specs
compile pyxis on scheduler
share spank_pyxis.so on /sched
group everything in same scripts and call functions based on roles
enable user namespace for AlmaLinux to fix "no space left on device" enroot error

@ryanhamel good to review


[WIP] Improve Linky integration

Use @bokub/linky module in linky integration.
Fixes #57

enedis can only return the hourly data for a single day

That's actually not true.
I'll improve my PR later this week

Also, in the config object, you should add your name as contributor:
const config = {
  label: 'Linky',
+ contributors: ['bokub'],
  country: 'FR',
  description: 'collects electricity data from your smart meter',
  type: ACTIVITY_TYPE_ELECTRICITY,
  isPrivate: true,
  // minRefreshInterval: 60
};

I've updated my code 🦉
Result :

By the way, I have noticed that the daily and hourly values are not coherent on the official Enedis website 🤦♂
Daily consumption : 7000 Wh

Sum of hourly consumption : obviously more that 7000 Wh

That's insane! I'm approving but will need to test on React Native to make sure it works.
Is there any credential that I can use to test? Maybe the best is that you ping me on slack so we can

do a test inside the app
give you access to the app


Add Open API document for OSB API

Relates to https://github.com/openservicebrokerapi/servicebroker/issues/160
Ready.

@rhodie27 Yes, there is an open bug with swagger editor not pulling in parameters from components correctly. https://github.com/swagger-api/swagger-ui/issues/3976 https://github.com/swagger-api/swagger-ui/issues/3558
But I think what is in this PR is correct based on the Open API spec. The swagger UI works correctly.
I will double check the spec... I think I am correct and the tools have not caught up to the new stuff in 3.0.0. https://swagger.io/docs/specification/components/

Rendered version: http://petstore.swagger.io/?url=https://raw.githubusercontent.com/n3wscott/servicebroker/9bc40f42ecaa3ab89fe632404a3eb56f15fb03b8/openapi.yaml

Here are some random nit-picking comments.

In the spec we several places with wording like this: "MUST be a non-empty string". "minLength: 1" should cover this.
In the schema definition Service -> properties -> requires, items should be an array of enums (syslog_drain, route_forwarding, volume_mount).
The schema of the status code '409' of 'PUT /v2/service_instances/{instance_id}' could be an Error, not an Object.
The status code '400' of 'PUT /v2/service_instances/{instance_id}/service_bindings/{binding_id}' is lacking a content definition.
The definitions of "route" and "*_url" properties and could be enhanced by "format: url".
The conventions for service and plan metadata are not in the spec, but we link to them from the spec. Should we do something similar here?

@fmui

In the spec we several places with wording like this: "MUST be a non-empty string". "minLength: 1" should cover this.

I would vote for no validation in the first version of the swagger spec. It might be useful to not have the validation in to allow folks to poke at bad brokers. If we still want validation, could it be a followup exercise?

The schema of the status code '409' of 'PUT /v2/service_instances/{instance_id}' could be an Error, not an Object.

The spec says MAY for an error and expected to be {}:
| 409 Conflict | MUST be returned if a Service Instance with the same id already exists but with different attributes. The expected response body is `{}`, though the description field MAY be used to return a user-facing error message, as described in [Service Broker Errors](#service-broker-errors).|

The conventions for service and plan metadata are not in the spec, but we link to them from the spec. Should we do something similar here?

I opted to only use the spec.
I have updated based on feedback, adding the missing return types and enums, but I am hesitating to add more validation to the doc just because it is hard to know when to stop. I think it could be a valuable addition to the Open API document, but it is still possible to do as a followup and we could do it one resources

So, what's the meaning of this excerpt:

| 409 Conflict | MUST be returned if a Service Instance with the same id already exists but with different attributes. The expected response body is {}, though the description field MAY be used to return a user-facing error message, as described in Service Broker Errors.|

You can add a description, but you better shouldn't. The platform doesn't expect it.
This a broker error, but you don't have to provide a description.

@fmui it means that 409 must at least return {} and optionally return a service broker error.

@avade thanks for the review! I will fix those missing return params up when I next get a chance.


[ENHANCEMENT] Proposal for Enhancing Makefile Optimization

Hello everyone,
I've been working with our Makefile and I noticed that there are several areas where we can improve its structure and functionality. Optimizing the Makefile can lead to better maintainability, faster builds, and improved clarity for new contributors.
Here are a few best practices I believe we could implement:

Use of Variables: Defining variables for compiler flags, directories, and sources can simplify edits and enhance readability.

Phony Targets: Adding .PHONY for non-file targets helps avoid conflicts with files of the same name.

  .PHONY: all clean

Automatic Dependency Generation: This can help manage header files automatically, ensuring the correct recompilation of files as needed.

Modularization: Breaking down the Makefile into multiple smaller files if it gets too complex will help keep things organized.

Improved Clean Targets: Including more thorough clean up options to ensure no residual files are left behind.

I would love to hear from others about their experiences and thoughts on these proposals. If anyone is interested, we could collaborate on updating the Makefile together!
References
GNU Make Manual
Makefile Best Practices

I would glad to help :)

Thanks for your help!  I hope that before we actually start coding, we can identify a few specific directions for optimizing the makefile. Later, I will summarize some tasks we need to accomplish. If you have any suggestions, please feel free to bring them up, and let’s see which ones you are interested in.

Thanks for your help! @omerap12
I hope that before we actually start coding, we can identify a few specific directions for optimizing the makefile. Later, I will summarize some directions. If you have any suggestions, please feel free to bring them up, and let’s see which ones you are interested in.

/assign @omerap12

Sounds good, @Syspretor .
Keep me posted :)


oom_score_adj update is not supported.

This is not supported by runc. We should not have flag for it.
https://github.com/opencontainers/runc/blob/master/man/runc-update.8.md
Signed-off-by: Lantao Liu<EMAIL_ADDRESS>

/lgtm


Execution commands page.location("[name='search']").visible? or page.query_selector("[name='search']").visible? ended with Timeout error

Step To Reproduce / Observed behavior
require 'playwright'
@playwright_exec = Playwright.create(playwright_cli_executable_path: 'npx playwright')
playwright = @playwright_exec.playwright
browser = playwright.chromium.launch(headless: false, channel: "chrome")
context = browser.new_context
page = context.new_page
page.goto('https://bing.com')
page.location("[name='search']").visible?

Expected behavior
True response is occurred.
Environment
Paste the output of ruby --version
ruby 2.6.0p0 (2018-12-25 revision 66547) [x86_64-darwin20]

page.location is not defined.
The timeout error seems to be caused in RubyMine.
require 'playwright'

Playwright.create(playwright_cli_executable_path: 'npx playwright') do |playwright|
  playwright.chromium.launch(headless: false, channel: :chrome) do |browser|
    page = browser.new_page
    page.goto('https://bing.com')
    puts page.location("[name='search']").visible?
  end
end

I tried this code and got an error as expected:
bing.rb:7:in `block (2 levels) in <main>': undefined method `location' for #<Playwright::Page:0x00007ff119297ea0> (NoMethodError)
Did you mean?  locator

And, it works by replacing location with locator.
    page.locator("[name='search']").visible?

(it returns false)

Is still doesn't work for me.
After calling page.locator("[name='search']").visible? I got ->

I guess RubyMine's breakpoint suspends all threads (including background messaging thread for communicating with Playwright driver).
https://stackoverflow.com/questions/27784413/how-to-debug-a-multi-threaded-app-in-intellij
Can you choose the option for suspending only the working thread?

Feel free to reopen if needed.

Yes issue was in rubyMine IDE debugger, many thanks.


It would be great to have author/authors of feed items

If an atom feed entry has no author set, feedparser could fill in the author from the feed element.

@onli  Good point.  The author/authors are missing. Need to get added if present. Cheers.

@onli  FYI: Authors are now included in all feed formats (Atom, RSS, JSON) if present. See the new authors.rb struct/class. Please, update your feedparser gem to 1.2+. Cheers.

Thanks!


feat(storage): Add startOffset and endOffset

PR for #4493

This change is

Failed because of test bench, I will check it

@coryan
One question: How to set up an integration test with test bench and bazel or run only some tests using cmake ?
Thank you

One question: How to set up an integration test with test bench and bazel or run only some tests using cmake ?

There is no "easy" way to do that, but this works for me:
Create a python virtual environment to install the dependencies for the testbench:
cd $HOME
python3 -m virtualenv ~/v-dev
source ~/v-dev/bin/activate
pip3 install flask==1.1.1 Werkzeug==1.0.0 httpbin==0.7.0     gevent==1.4.0 gunicorn==19.10.0 crc32c==2.0

In that shell start the testbench on a fixed port (I am using 8585 here) with name for the test bucket:
cd google-cloud-cpp
env GOOGLE_CLOUD_CPP_STORAGE_TEST_BUCKET_NAME=bucket gunicorn --bind "<IP_ADDRESS>:8585"     --worker-class gevent     --access-logfile -     --pythonpath "${PWD}/google/cloud/storage/testbench" --reload    testbench:application

On a separate shell run the integration test you want, typically, the last one I ran was:
GOOGLE_CLOUD_PROJECT=test GOOGLE_CLOUD_CPP_STORAGE_TEST_BUCKET_NAME=bucket CLOUD_STORAGE_TESTBENCH_ENDPOINT=http://localhost:8585 \
    ./cmake-build-debug/google/cloud/storage/tests/object_resumable_write_integration_test  --gtest_filter=ObjectResumableWriteIntegrationTest.WriteNotChunked

In that example ./cmake-build-debug is my binary directory for CMake. You can use Bazel too, but remember that Bazel does not pass any environment variables to tests.  You need to pass each environment variable using the --test_env option.
Each test requires a slightly different set of environment variables, I am sure you can figure out that part.

There is one indentation error in python which cause some errors related prefixes. But in the last PR, there were too many tests run at a time and they all passed so I don't know about it. I think it will increase the coverage rate in ListObjectsAndPrefixes sample too.


BIG-IQ regkey pool only working with IQ 5.2

Currently DO allows for the use of regkey pools within BIG-IQ, but only in version 5.2. This issue will be used to track the addition of future versions.

Completed under AT-241 for release in DO 1.5


Login not working

Using the example on the README page it gives me the following error when I try to log in:
TypeError: Cannot read property 'token' of undefined
   at verifyToken (/home/tudurom/squirrel/squirrel.server/node_modules/feathers-authentication/lib/index.js:166:17)

It looks like your request is missing a body, or it might be due to the missing .use(bodyParser.json()) just before the .use(bodyParser.urlencoded({ extended: true })) in the server setup.
I'm updating the README.md right now.  I'll let you know when it's done.

I've updated the README with a short tutorial on getting up and running.  Let me know if you run in to anything else.  Thanks for your feedback.

It works! Thank you very much! The problem was I was loading the modules in a random order.

You are welcome.  Have fun!


Docs refer multiple times to use slack, but there's no clear instructions on signing up

I signed up for slack under the name paul-reviewpush, and there's no ability to read or write anything.
If the slack is for contributors only, employees of improbable-engineering only, or so on it should mention that in contributing.md or similar.
Rules and guidelines for interactions there would also be good to mention, even if they are repeated in a slack motd or similar.
Personally I think some kind of community help channel would be useful to have, but even if there is a decision not to have an open one, it would be helpful to clear that up, so that people don't think they made some technical mistake in the sign up process.

and there's no ability to read or write anything.
Sorry, what do you mean? (:

Slack is open for everyone who sign. Have you tried to search for any channel? #thanos and #thanos-dev channel is what you need (:
Good point with help channel. Will do!

Thanks for reporting it, I created #help channel for new guests.


Add possitility to edit kafka-manager.X properties using ENV variables.

Currently, to edit  kafka manager properties you should edit  file located under VOLUME /kafka-manager/conf volume in running container. We can extend application.conf file with properties using next env variable notation:
kafka-manager.consumer.properties.file=${?CONSUMER_PROPERTIES_FILE}
basicAuthentication.username=${?KAFKA_MANAGER_USERNAME}

@hleb-albau In fact one could edit all the variables from application.conf by providing arguments to CMAK docker via CMD instruction.
E.g. docker run hlebalbau/kafka-manager -Dhttp.port=7070
I think this should be described in README and this issue then could be closed.
If you're OK with that - I'm ready to provide a PR.

@eshepelyuk cool, waiting for your PR

@hleb-albau opened #31

@hleb-albau and could you pleae check my comment on other issue
https://github.com/hleb-albau/kafka-manager-docker/issues/25#issuecomment-783980266


FAT32, there are no entries?

so i got to the point where i've read the FAT32 table into a struct and most of the information seems correct as far as i can tell.
except there isn't any root directory entries despite there being at least 2 files on the drive (the font used by the bootloader and then the kernel itself).
i can't tell if this is me failing to read the drive somehow or if i'm not writing the drive correctly somehow or maybe it's a flaw in the tools i use?
relevant files and documentation.

https://wiki.osdev.org/FAT (mainly for the structure of the data on the disk.)
https://wiki.osdev.org/User:Requimrar/FAT32 (i'm using the entry structure)
FAT.hpp
FAT.cpp

ok so it might be the tools, just read this
"It is important to notice that, while MTools claims to include only the minimal BIOS Parameter Block (BPB), it actually uses the FAT16 extension"
from the bottom of https://wiki.osdev.org/MTools
so it looks like the first thing i need to try is replacing mtools with something else that works for FAT32

nope, did the creation of the image manually instead of with mtools, same result.
am i suppose to update the table somehow?

I tried reading the first entry anyways despite it saying there are no entries, i was initially excited that i got any data at all but then i realized something... the file size is 0 and the type doesn't match anything i saw in the wiki.
name            45,
name            46,
name            49,
name            20,
name            20,
name            20,
name            20,
name            20,
ext             20,
ext             20,
ext             20,
attrib          10,
userattrib      00,
undelete        9E,
createtime      9A,
createtime      A8,
createdate      7B,
createdate      55,
accessdate      7B,
accessdate      55,
clusterhigh     00,
clusterhigh     00,
modifiedtime    9A,
modifiedtime    A8,
modifieddate    7B,
modifieddate    55,
clusterlow      03,
clusterlow      00,
filesize        00,
filesize        00,
filesize        00,
filesize        00

ok so uhmm... they don't use the count for the root entries anymore apparently.
i think that's rather stupid of them to do but whatever, another thing they do that's incredibly weird along with not using the full 32 bits.
I think i have this solved now? i'm going to leave it open for the rest of the day just to be sure and then close it tonight before i go to bed.

ok this is still semi broken , works fine for small files but not for larger files that take up multiple clusters.
i'd say though this specific issue is solved though, that multiple cluster issue is something else i'll have to sort out.


SwiftUI ScrollView in UIPilot will get stuck after a while.

SwiftUI ScrollView in UIPilot will get stuck after a while.

I think you are having issue with ScrollView  because library is working fine you can check it out in Justly this app is using this library and working pretty smooth. Still you have the issue you can create demo app with issue we will review it and if issue is identified then we'll resolve it.


This page needs examples of what the project file should look like for each section

For example, what does a file look like that correctly implements some of the Nuget metadata properties or AssemblyInfo properties?

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

ID: cb4428fc-215c-78e1-5ff0-fe73f7a08260
Version Independent ID: 6741b1de-38a4-fbb1-d79d-acc47d549a2d
Content: Additions to the csproj format for .NET Core - .NET Core CLI
Content Source: docs/core/tools/csproj.md
Product: dotnet-core
Technology: dotnet-cli
GitHub Login: @tdykstra
Microsoft Alias: mairaw

There are lots of gray areas as docs concerned. Build targets, variable-like XML properties, pre-post build and or publishing... I just need to run a simple webpack task before publishing but there are lots of approaches over the web. Maybe a kitchensink csproj would be great.

An example or even an XSD (with defaults) would still be appreciated

An example or even an XSD (with defaults) would still be appreciated

This article was retired and its URL now forwards to https://docs.microsoft.com/en-us/dotnet/core/project-sdk/msbuild-props
cc @gewarren

This article was retired and its URL now forwards to https://docs.microsoft.com/en-us/dotnet/core/project-sdk/msbuild-props
cc @gewarren

@tdykstra  - thanks. I may open a new issue on the other one if I cant find the defaults that are used when the elements are omitted.

@tdykstra  - thanks. I may open a new issue on the other one if I cant find the defaults that are used when the elements are omitted.


Re-order custom fields

Reference SimpleDesk Website: Re-order custom fields
===
Add ability to reorder custom fields.

Add a sort column.
Default to current index during upgrade.
Add UI aspect to move around in ACP
Update front end to use the order.

Can be closed?


pull request for e2e test at 12/24/2016 23:15:07

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Format Table

Thank you for publishing this package
Let marksman provide a format function which formats GFM tables.
It may also format paragraphs, blockquotes, and lists by max line length

I recommend you use Prettier for that, it is pretty much the industry standard for Markdown. If that is too slow checkout Deno that uses Rust.


[logging] security logging for invalid transactions received from peer

This commit adds a security log to detect invalid transactions that were forwarded by other peers (via mempool)

@bors-libra r=joshlind

:pushpin: Commit ffef309 has been approved by joshlind

:hourglass: Testing commit ffef30902c8e3ef837c3c6dbbfde6d3ed0bbe43e with merge 5aa71408d66170407a63e7b47350208efb5639ea...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: joshlind
Pushing 5aa71408d66170407a63e7b47350208efb5639ea to master...

Thanks!


odo dev should exit if the build command fails

/kind feature

Which functionality do you think we should add?
If the build command as defined in the devfile fails, odo dev should exit and indicate which command in the devfile should be be fixed/investigated
Why is this needed?
When bootstrapping a project via odo init, it may be the case that the build command needs to be modified so that the application can be compiled.
This is particularly true for go-based projects. The stacks currently available on https://github.com/devfile/registry/blob/main/stacks/go assume there is a main.go at the project root. This is not universally true - there is no firm consensus in the go community that this pattern should be adopted, and many teams/projects have their own idioms around "main" files. Example - putting command line invocations in the cmd package is common.
Stopping the sync loop and printing the last lines of the log (current behavior) followed by a helpful action statement would improve the developer flow.

Thank you for raising this, Adam. We'll be sure to groom this soon.

The PR #6762 mkes some refactoring on the Dev code, to simplify the legacy code:

getting the values passed into the context
Move Devfile param to WatchParams insted of being part of the Adapter structure,  and build adapter only once


Safari Bug: editing embedded Flems jumps the page as if possessed by the devil

It's sporadic, but ƒ.e. editing the "Putting It All Together" example on this page will make the whole page jump back up, oftentimes taking the active flem out of view. There's something about "least surprise" here, but I can't quite put my finger on it...

Thanks @CreaturesInUnitards.. This also removed an ugly unnecessary hack at the same time :P


speed up IBD by not storing unspent coins in UTXO memory cache

Background
The UTXO, aka chainstate, database is stored on disk and partially in a memory cache whose size is determined by -dbcache`). The size of this cache significantly affects IBD time. As we validate each block, we loop through its transactions, and verify that each input spends an existing UTXO. Even if we're not checking signatures (AssumeValid), we verify that the input refers to an unspent output (to prevent double-spends). It's much faster if the UTXO is in the memory cache. We also add each transaction output to our memory UTXO cache so a subsequent transaction can refer to it. This memory cache is implemented as an unordered map whose key is an outpoint (txid and output index) and whose data is the scriptPubKey (what's needed to validate the input that wants to spend this output). When this cache becomes full, we flush it to disk; you can see those flushing cliffs in graphs.
We don't flush a "dirty" in-memory UTXO entry to disk right away, because another near-term tx may spend this UTXO -- even within the same block. In that case, we never write this UTXO to disk! That's a nice savings. I think this explains the downward arcs of those graphs before each flush. UTXOs are continuously added to the cache at about the same rate, but as the cache becomes populated, it's more likely that inputs spend UTXOs that are in the memory cache, which allows those UTXOs to be dropped (and never written to disk). So the net rate of addition to the cache slows down. If the cache is large enough to hold the entire UTXO set, then the cache size would gradually level off. But it's unusual for node runners to configure the cache to be this large.
As an aside, it seems like an improvement would be to retain these items in the memory cache after we flush them to disk, instead of clearing the memory cache. There may be a reason I'm not aware of that this can't be done (or done easily).
The problem
There are many coins, such as Satoshi's early coins, that to this day have not been spent. They will eventually get flushed to disk -- but they hold onto memory until that happens. This means there is less memory available for other UTXOs that will be spent before being flushed. The time Satoshi's coins are sitting in memory isn't a very efficient use of that memory.
One interesting property of IBD is that we know the (likely) future. Every node will go through the same sequence of coin creation and spending (in the database) until reaching the tip.
A solution
So the idea is, we have a static, hard-coded bloom filter (in the source code) that's probably updated for each major release (similar to the AssumeValid block hash). This bloom filter will contain outpoints referring to UTXOs that remain unspent (at least up to the time the filter is constructed), such as Satoshi's coins. When we add an entry to the memory cache, if the outpoint is (probably) in the bloom filter, then we want to flush it to disk -- and free its cache entry in memory -- soon. The flushing seems to be done in batches, so we may need to bundle up a bunch of these and flush them at the same time. (I haven't figured out how to do this yet.) This will free up cache space, making it more likely that an input we're validating refers to a UTXO that is in the memory cache (and thus doesn't need to be read from disk). It makes the cache more effective -- storing items that are more likely to be needed. It would have the same effect as having a larger cache.
A bloom filter can have false-positives, so we may flush some cache entries that do get spent, and that may make it worse when those get spent than currently. But if we size the filter correctly, this should be rare. We could instead invert the sense of the filter so it contains entries that will be spent (and flush entries that are not in the filter). This way, the false positives would cause us to keep entries in the cache that would be better to flush. But that's no different from today. I'm not sure which way around the filter should be implemented, but for now, let's assume it contains unspent UTXOs.
A refinement to this idea would be to add UTXOs to the bloom filter that are long-lived, not spent "soon" for some definition of soon. Unfortunately, this definition would ideally depend on the node's -dbcache setting, which we can't predict when we're creating the static bloom filter. We could have a few filters and use the appropriate one based on cache size, but that may be getting too complicated. If we choose "soon" based on the default cache size, that may be close enough. Also, we could not activate this optimization (do these "early" flushes) at all until the cache becomes something like 90% full. That way if a node is configured with a very large cache, this change wouldn't make performance worse.
Another refinement (thanks to @theStack) would be to inspect the scriptPubKey to see if the output is likely or actually unspendable (for example, dust or public keys not on the curve).
Note that this idea doesn't increase trust in the devs; it's just a performance improvement in the most likely case.

What's the maximum theoretical benefit here?  I'd think it'd be roughly equivalent to the sync time difference between the following two:

IBD on a node with a spinning disk (and maybe less than default cache size)
IBD on the same node with the cache size set to higher than the maximum historic UTXO set size (something like 8 GB, I think)

I think running that test in a mostly-controlled environment (e.g. syncing over a LAN) would be pretty easy and would quantify the maximum upside, which could point to whether this is a worthwhile optimization or not.

If this ends up being worthwhile; instead of the hand-crafted bloom filter, what about scheduling a task every 24 hours, or.. every week, to flush UTXOs from the cache that surpasses certain depth.

@furszy - thanks, I think the 24-hour flush is already being done (note static constexpr std::chrono::hours DATABASE_FLUSH_INTERVAL{24})
The key part of this proposal (what may make it unique) is to use knowledge of the "future" (at least the expected future) to improve memory utxo caching behavior -- which may or may not work out, of course. I think you're suggesting improving caching policy with no reference to the "future", but this has been discussed at least as far back as 2019 in detail (review club). I'm still trying to absorb all the discussion myself.
One of the things I've noticed that's probably fairly unique to this project is that when I start to dig into an area of the code in what I consider to be significant detail, it turns out that I'm just scratching the surface of what's already been discussed!


Upgrade site-maven-plugin to 0.12

Upgrade site-maven-plugin to 0.12 to avoid the "nil" bug causing the mvn site to fail. The bug has been fixed but if the dependency is not upgraded, the tutorial won't work.
Once in à.12, it runs fine !

thanks !


ScrollViews conflict with the swipe back gesture on iOS

This is pretty similar to https://github.com/react-navigation/stack/issues/127 but its not related to a Modal so I thought it might deserve its own issue.
Basically put a ScrollView on a screen, and try to swipe back on iOS diagonally (which is very common).  Very frequently the ScrollView "takes" the gesture instead of the stack navigator and so instead of swiping back you end up scrolling.
Compared to a native app, the swipe back gesture takes precedence and is much easier to trigger.
I can fix this by wrapping my ScrollView like this:
import { NativeViewGestureHandler } from 'react-native-gesture-handler';
import { StackGestureContext } from 'react-navigation-stack';
...
 <StackGestureContext.Consumer>
          {(ref: any) => (
            <NativeViewGestureHandler waitFor={ref}>
                <ScrollView>...</ScrollView>
            </NativeViewGestureHandler>
          )}
 </StackGestureContext.Consumer>

But I feel like this should be handled in the library itself.
https://github.com/react-navigation/stack/issues/137 is also probably caused by this.

Also one thing to note is this is a regression from older versions of react-navigation (1.*).

Can you import ScrollView from gesture handler and try?


Add Pi Gateway Doc

Summary

@neoaggelos wrote up a great guide on creating your own pi gateway. Let's add it to the docs, maybe under gateways/raspberry-pi? It could also be a good guide for the forums. @nejraselimovic can you weigh in on what you think and take this one?
https://neoaggelos.github.io/blog/005-ic880a-gateway-basicstation/

yep, I can take this one, @neoaggelos really provided an awesome tutorial!


GROOVY-8109: Unsupported operator with @CompileStatic causes BUG! () …

…during compilation

Not for Parrot branch

I miss a test for this ;)


[api] Multiple compile errors related to IGet<K, V>

I get multiple errors in package @thi.ng/associative:
node_modules/@thi.ng/associative/array-set.d.ts:18:5 - error TS2416: Property 'copy' in type 'ArraySet<T>' is not assignable to the same property in base type 'IEquivSet<T>'.
  Type '() => ArraySet<T>' is not assignable to type '() => IEquivSet<T>'.
    Type 'ArraySet<T>' is not assignable to type 'IEquivSet<T>'.
      Types of property 'get' are incompatible.
        Type '(x: T, notFound?: T | undefined) => T | undefined' is not assignable to type '(key: T, notfound?: T | undefined) => T'.
          Type 'T | undefined' is not assignable to type 'T'.
            Type 'undefined' is not assignable to type 'T'.

18     copy(): ArraySet<T>;
       ~~~~

I think the reason is an incorrect return type in IGet.get(), it should be V | undefined:
// @thi.ng/api/api.d.ts:
export interface IGet<K, V> {
    get(key: K, notfound?: V): V | undefined;
}

Hi @andrew8er - let me guess, you're having some TS "strict" compiler flags enabled? Coincidentally I've recently done some initial work on a local feature branch to finally enable "strict" (minus "strictNullChecks", which I find too intensive to fully support right now). Only updated around a dozen of the 90 packages in total so far, but will merge WIP into develop branch..

Yes, I always use strict, including strictNullChecks. I really think it forces me to write better code. Do you need some help?

Thanks, @andrew8er - I will push the updates done so far later today and if you've got time would very much appreciate your watchful eye passing over them and maybe even help w/ updating the rest. Have done some more last night and guessing around 50% done so far...
In general, I'm all for enabling strict (hence why I started already on this), but am also pragmatic (coming from Clojure) and went for low hanging fruits only so far...

I think you are referring to branch feature/strict? I will have a look at it. I only used @thi.ng/rstream and @thi.ng/transducers so far, so I might be most helpful with these.

Well, yes, with pushing updates, I did mean the #89 PR (feature/strict branch), but generally I was referring to the strict compiler flag. Btw. all packages are now updated with more type hints and in some cases minor new type additions, so yarn build will succeed now in. I started updating the tests too, but prob will take me another few days...


HDDS-3196 New PipelineManager interface to persist to RatisServer.

What changes were proposed in this pull request?
Construct new PipelineManager and PipelineStateManager interface for SCM.
(Please fill in changes proposed in this fix)
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-3196
(Please create an issue in ASF JIRA before opening a pull request,
and you need to set the title of the pull request which starts with
the corresponding JIRA issue number. (e.g. HDDS-XXXX. Fix a typo in YYY.)
Please replace this section with the link to the Apache JIRA)
How was this patch tested?
TODO in https://issues.apache.org/jira/browse/HDDS-3679
(Please explain how this patch was tested. Ex: unit tests, manual tests)
(If this patch involves UI changes, please attach a screen-shot; otherwise, remove this)

@xiaoyuyao, if you're ok with the changes I will go ahead and merge it.

@timmylicheng thanks for the contribution.


Make threads more visible in docs

Via Community Slack

Some docs on this exist, but they are only for CLI and not very easy to discover. Per @amychen1776 this question comes up a lot for folks getting started. Also imagine this is a pattern Airflow users are familiar with, and might be looking out for.
Proposal: have this info live on its own page instead, and cover both CLI and Cloud
cc @sophiad96 @amychen1776
h/t @jtcohen6 for link to a good article on the subject that may be helpful too.

@annafil do you have any thoughts on where in the docs we should add this? I'm going to think about this a bit more today but would love to hear your thoughts!


[Feature request] Specify branch for beta

Nice plugin, thanks.
I would like to have a possibility to specify a branch for beta releases.
As I understand I have to have actual manifest-beta.json in branch for releases and I have to chose between two options:

Merge beta code with new version with master
Create separate commit to update manifest-beta.json and resolve conflicts lately.

But it will be great to have a file, for example, manifest-beta-brach.json where I can specify branch which have actual manifest-beta.json.

Actually, the manifest-beta.json just points to a "Release". So if you can generate a release from a specific branch and point the manifest-beta.json to that release, BRAT will pull that release.
There is a "Frozen" version option where a user can also specify a release number and its a one time install. See step 3 here for frozen version: https://github.com/TfTHacker/obsidian42-brat#adding-a-beta-plugin

This is a great idea, but its beyond the scope for now. Frankly I just don't have the time to take it much deeper. Sorry.


Example app error - Couldn't find preset "react-native" relative to directory

I get this error when following the readme instructions to install the example app
Error: Couldn't find preset "react-native" relative to directory "<root.dir>/react-native-pathjs-charts"

Two ways to workaround this until it gets fixed:

Remove .babelrc from the root directory (../example)
Do npm install on the root directory (../example)

That helped. Thanks!


feat: add erasing op lint

addresses #17
I will be adding more code since i am having trouble evaluating of an literal is zero or not

check that there might be a usable function there to help you https://github.com/starkware-libs/cairo/blob/main/crates/cairo-lang-lowering/src/optimizations/const_folding.rs

@all-contributors please add @guha-rahul for code and test


Question about passing parameters

I customized a Calculator, the rough code is as follows:
::mediapipe::Status MyCalculator::Process(CalculatorContext* cc) {

    /////////////////////////////// hardcoded path.
    cv::Mat background = cv::imread("mediapipe/calculators/image/testdata/clouds2.png");

    ......
}

, in the code, I have to hardcode, but what I hope is that this path can be passed in through parameters? All in all don't want to be hardcoded, any good suggestions?

Hi @Alvazz ,can you please elaborate this issue to investigate further.

@sureshdagooglecom Hi,
I customized a Calculator. My purpose is to use it as a background to replace Selfie Segmentation. The default Mediapipe is that the virtual background is blue, but I want to use a picture as a virtual background, so for this, I wrote a Calculator, but in the "Process(CalculatorContext* cc)" processing function, I cannot accept the hard-coded form to read the image used for the virtual background. What I hope is that the virtual The image path (or data) of the background is passed into the "Process(CalculatorContext* cc)" function, so that I can control it externally.
I am using C++ and the runtime environment is Windows 10. Version v0.8 is used.

Didn't find any useful information, need help.

Marking it as duplicate https://github.com/google/mediapipe/issues/3108

Hi @Alvazz, have you found any solution to this? I am not getting any good results, this is my calculator file for background replacement, I dont know where I'm doing this wrong.
   ::mediapipe::Status BackgroundMaskingCalculator::Process(CalculatorContext* cc) {

  ///////////////////////////////// DESKTOP Asset reading method
   cv::Mat background = cv::imread("mediapipe/calculators/image/testdata/dino.jpg");

  std::cout << " Process() of BgMasking" << std::endl;

  const auto& input_img = cc->Inputs().Tag("IMAGE").Get<ImageFrame>();
  cv::Mat input_mat = formats::MatView(&input_img);

  const auto& mask_img = cc->Inputs().Tag("MASK").Get<ImageFrame>();
  cv::Mat mask_mat = formats::MatView(&mask_img);

  cv::cvtColor(background, background, cv::COLOR_BGR2RGB);
  cv::cvtColor(background, background, cv::COLOR_RGB2RGBA);
  cv::resize(background, background, input_mat.size());

  cv::Mat channels[4];
  cv::split(mask_mat, channels);

  cv::Mat bg_mask;
  cv::Mat fg_mask;

  cv::Mat in[] = {channels[3], channels[3], channels[3],channels[3]};
  cv::merge(in, 4, bg_mask);

  cv::bitwise_not(bg_mask, fg_mask);
  bg_mask.convertTo(bg_mask,CV_32FC3,1.0/255);
  fg_mask.convertTo(fg_mask,CV_32FC3,1.0/255);

  int k= 9;
  cv::GaussianBlur(bg_mask, bg_mask, cv::Size(k,k), 7);
  cv::GaussianBlur(fg_mask, fg_mask, cv::Size(k,k), 7);

  background.convertTo(background,CV_32FC3);
  input_mat.convertTo(input_mat,CV_32FC3);

  cv::Mat bg_image;
  cv::multiply(background,bg_mask, bg_image);

  cv::Mat fg_image;
  cv::multiply(input_mat,fg_mask, fg_image);

  cv::Mat output_image;
  cv::add(bg_image, fg_image, output_image);

  std::unique_ptr<ImageFrame> output_frame(
      new ImageFrame(input_img.Format(), input_img.Width(), input_img.Height()));

  cv::Mat output_mat = formats::MatView(output_frame.get());

  output_image.convertTo(output_image,CV_8UC3);
  output_image.copyTo(output_mat);
  cc->Outputs().Tag("OUTPUT_VIDEO").Add(output_frame.release(), cc->InputTimestamp());

  return ::mediapipe::OkStatus();

  }
   REGISTER_CALCULATOR(::mediapipe::BackgroundMaskingCalculator);}

Hello @Alvazz,
We are upgrading the MediaPipe Legacy Solutions to new MediaPipe solutions However, the libraries, documentation, and source code for all the MediapPipe Legacy Solutions will continue to be available in our GitHub repository and through library distribution services, such as Maven and NPM.
You can continue to use those legacy solutions in your applications if you choose. Though, we would request you to check new MediaPipe solutions which can help you more easily build and customize ML solutions for your applications. These new solutions will provide a superset of capabilities available in the legacy solutions. Thank you


Error while authenticating

Hi !
When I try to authenticate with your node module I get this error :
undefined
^
SyntaxError: Unexpected token u
    at Object.parse (native)
    at /var/www/node_modules/t411/index.js:197:21
    at Request.callback (/var/www/node_modules/t411/node_modules/superagent/lib/node/index.js:691:12)
    at ClientRequest.<anonymous> (/var/www/node_modules/t411/node_modules/superagent/lib/node/index.js:901:12)
    at ClientRequest.EventEmitter.emit (events.js:95:17)
    at HTTPParser.parserOnIncomingClient [as onIncoming] (http.js:1688:21)
    at HTTPParser.parserOnHeadersComplete [as onHeadersComplete] (http.js:121:23)
    at CleartextStream.socketOnData [as ondata] (http.js:1583:20)
    at CleartextStream.read [as _read] (tls.js:511:12)
    at CleartextStream.Readable.read (_stream_readable.js:320:10)

I think it's from the index.js class at
var data = JSON.parse(res.text);
res doesn't have a 'text'

Hi, the module is working  but the api is down right now. Don t know when
it will be fix.
On Tue, 11 Apr 2017 at 23:15, Simar Jérémy<EMAIL_ADDRESS>wrote:

Hi !
When I try to authenticate with your node module I get this error :
undefined
^
SyntaxError: Unexpected token u
at Object.parse (native)
at /var/www/node_modules/t411/index.js:197:21
at Request.callback (/var/www/node_modules/t411/node_modules/superagent/lib/node/index.js:691:12)
at ClientRequest. (/var/www/node_modules/t411/node_modules/superagent/lib/node/index.js:901:12)
at ClientRequest.EventEmitter.emit (events.js:95:17)
at HTTPParser.parserOnIncomingClient [as onIncoming] (http.js:1688:21)
at HTTPParser.parserOnHeadersComplete [as onHeadersComplete] (http.js:121:23)
at CleartextStream.socketOnData [as ondata] (http.js:1583:20)
at CleartextStream.read [as _read] (tls.js:511:12)
at CleartextStream.Readable.read (_stream_readable.js:320:10)
I think it's from the index.js class at
var data = JSON.parse(res.text);
res doesn't have a 'text'
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/thibauts/t411/issues/11, or mute the thread
https://github.com/notifications/unsubscribe-auth/AB13oi4hVPeO43VMZ01EJXL-51DnXeFeks5ru-11gaJpZM4M6qJr
.

api ok.

Yes sorry for the inconvenience


libsql URL protocol support

We have two protocols: HTTP and WebSockets. Let's make the client also accept a third one:libsql, which uses the right sqld protocol depending on whether interactive transactions are needed or not.

that's solved for a while now, closing


Remodel the error type

Here is a proposal for the redesign of the crate's top-level error type.
It uses a strongly typed enum for the possible errors and encapsulates the native error code instead of storing a message string.
This makes errors more transparent, drops the need for extra allocations with an indirection,   and makes way for more memory optimizations in the future if we want to (i.e. at the moment it should be possible to save the native error code in a NonZeroI16, which would further reduce the error type's inline size in memory).
I already tested the changes against DICOM-rs locally. While I would mark this PR as a breaking change to be released in version 0.3.0, no changes were required in the DICOM-rs code base, so it will be a smooth migration.

Great contribution.


Please invite me to the GitHub Community Organization

Name
Ryo
Discord Username (if applicable)
superjunior_017
Additional Context
Hi, Jaidevstudio Teams!
I really want to join your community!
Plz give me invite : github username (supersenior017)
Thanks

Check you email please


Update content in README.md

Update content for accuracy and consistency across documentation.

@x85446 Could you please tag Ben C. as a reviewer? I've updated this page based on the content he provided.

@bentcooke @deepakpoornachandra

@AnotherButler Hate to be a butt, but this groups's development branch is actually dev.
Once another release is ready/made, changes from 'dev' will be pulled into 'master'.

What I'm hearing is:

I should close this PR and recreate it against dev.
We should add that information to the README, so anyone else contributing doesn't make the same mistake.

Yes and yes

Closing in favor of PR #20


allow implementing servers in DS

[x] add ds._serverHandler(pkt => { ... }) function; returns device id for these servers and will call the handler on all incoming packets for that device id
[x] add ds.Role.spec field - RegisterSpec, EventSpec, CommandSpec - allow for creating/parsing packets matching these specs

this is now done


make it possible to define processing interval of the input video

i need this package to select samples from specific parts of my video files, not the whole duration.
i tried to solve it by only adding 2 optional params into config: start_frame and end_frame.
what do you think @LemurPwned ?
Summary by Sourcery
Add support for specifying a processing interval in video sampling by introducing start_frame and end_frame configuration options, allowing users to select specific parts of video files for processing.
New Features:

Introduce the ability to define a processing interval for input videos by adding optional start_frame and end_frame parameters in the configuration.

Thanks a lot for your contribution @fcakyon!
I think this is a very good feature to have, and I have a few thoughts:
1.

Thanks a lot for your contribution @fcakyon!
I think this is a very good feature and here are my thoughts:
Perhaps it's easier to specify the start_time and end_time than the equivalents in frames? Meaning the user does not have to count or estimate frames, and they can instead just put time values?
Additionally, in VFR (variable frame rate) the frame seeking and frame counting may become inaccurate (esp. when using avg_framerate).
What do you think?

Thanks a lot for your contribution @fcakyon!
I think this is a very good feature and here are my thoughts:
Perhaps it's easier to specify the start_time and end_time than the equivalents in frames? Meaning the user does not have to count or estimate frames, and they can instead just put time values?
Additionally, in VFR (variable frame rate) the frame seeking and frame counting may become inaccurate (esp. when using avg_framerate), while it'll be still reliable if we use the time as the locating factor.
What do you think?

You are right, specifying time would be more stable than frames 👍🏻

Thanks @fcakyon, I'll merge it to main.

Thanks for finishing the PR, I couldnt find the time 🚀


Finally fixed incorrect dep graph sizes

@kwalcock: I believe this finally fixed that Eidos crash. Thanks for the examples!

This did seem to fix the problem.  The file 3_ALPAN_Paper_10.txt could be removed now.  Can this version be sent to maven?  It might be the version just before dynet goes parallel and it is a good fallback position if parallel goes wrong.  If it doesn't get published, people (I) would need to use the locally published version to get the fix.

Good idea. Can you please release this?

It was just released.

Nice, thanks!


Question: How to add unique ID to table row selection radio button?

I've successfully implemented a sortable, paging table.
Here's a snippet of my code showing a custom selectionRenderer.
Is it possible to generate a unique ID for each radio button instance?
<BootstrapTable
  keyField="index"
  data={ props.data.map((row, index) => ({...row, index})) }
  columns={ props.columns }
  selectRow={{
    mode: 'radio',
    clickToSelect: true,
    classes: 'is-selected',
    onSelect: props.rowClick,
    selectionRenderer: ({ mode, ...rest }) => (
      <input type={ mode } id={somethingUnique} { ...rest } />
    )
  }}
  hover
/>

I can see from React devtools that there's a rowIndex prop passed down to <SelectionCell> component, but I can't figure out how to expose that via <BootstrapTable> props to my selectionRenderer?
The docs also say that selectionRenderer only accepts 3 props.

@basher if rowIndex is helpful to you, I will add it in next version, thanks

@AllenFang That would be great. Thanks.
Any idea when that will be?

ETA 2/20

Excellent. Thanks for your prompt fix.

@basher, We have new release for fixing this issue: please check RELEASE NOTE and upgrade related packages

Thanks @AllenFang
I'll implement fix asap.

please tag me if the issue still remain, thanks

Works a treat, @AllenFang
Here's a working snippet of the relevant code to add an ID to a row selector.
The important bit is rowIndex.
<BootstrapTable
  selectRow={{
    mode: 'radio',
    selectionRenderer: ({ mode, rowIndex, ...rest }) => (
      <input type={mode} id={`row${rowIndex + 1}`} {...rest} />
    ),
    // other 'selectRow' props...
  }}
  // other 'BootstrapTable' props...
/>


S2U-21 SAK-49646 T&Q: Fix early timer start with SEB - MASTER

https://sakaiproject.atlassian.net/browse/S2U-21
https://sakaiproject.atlassian.net/browse/SAK-49646

Did you test this with and without enabling SEB?

I'm going to test this patch! Thanks @stetsche!! :)

@mpellicer I didn't test it without SEB, as I am only touching SEB specific areas of the code, but I will do a quick test.

Just tested using linear and flexible assessments without SEB configured and it seems to work just fine as before.

Just tested on our test environment. This works fine and can be merged!
Great job @stetsche!

Awesome, thanks @jesusmmp!

Thanks for the review and the implementation guys @stetsche @jesusmmp


Fonts dependencies?

can you provide a list of fonts to mimic the setup??

The fonts in the screenshot are the same as the ones in the userChrome.css
On Sat, Jan 11, 2020 at 10:31 PM Srinath koilakonda <
<EMAIL_ADDRESS>wrote:

can you provide a list of fonts to mimic the setup??
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/turing753/minimal-functional-fox/issues/14?email_source=notifications&email_token=AFCH4PLHTSDEYJZG6LMEQLDQ5KTJHA5CNFSM4KFV2PFKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IFR2AYA,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFCH4PLF52EQ5H75VPIYNUTQ5KTJHANCNFSM4KFV2PFA
.


Build ARM64 image

I've added the building of the ARM64 version of the image because the ARM platform is so popular nowadays.

Thanks for your contribution @rostyslavkhaniukov!
This image contains the toolchain to support cross-compiling cgo programs for amd64, arm64 and s390x. This is then used in other repos to actually build binaries for the supported architectures. However, amd64 hosts the cross-compilation.
Is your usecase to host the cross-compilation on arm64?

Stale.


minor: release V2.2.18

Codecov Report

Merging #922 (a80043a) into V2.2.X (6e22bae) will decrease coverage by 0.04%.
The diff coverage is 37.50%.

@@            Coverage Diff             @@
##           V2.2.X     #922      +/-   ##
==========================================
- Coverage   71.05%   71.00%   -0.05%
==========================================
  Files         294      294
  Lines       21597    21610      +13
==========================================
- Hits        15345    15344       -1
- Misses       6252     6266      +14

Impacted Files
Coverage Δ

apps/backend/subscription/views.py
50.57% <0.00%> (-0.44%)
:arrow_down:

config/default.py
80.39% <ø> (+0.77%)
:arrow_up:

apps/node_man/serializers/policy.py
64.76% <22.22%> (-9.40%)
:arrow_down:

.../components/collections/agent_new/register_host.py
97.28% <100.00%> (+1.17%)
:arrow_up:

apps/backend/subscription/serializers.py
87.67% <100.00%> (-0.57%)
:arrow_down:

apps/node_man/constants.py
98.22% <100.00%> (ø)

apps/node_man/handlers/plugin_v2.py
85.00% <100.00%> (+0.15%)
:arrow_up:

env/paas_version_diff/paas_v2.py
100.00% <100.00%> (ø)

apps/backend/subscription/steps/plugin.py
47.48% <0.00%> (-0.56%)
:arrow_down:

...nents/collections/agent_new/choose_access_point.py
95.60% <0.00%> (+0.48%)
:arrow_up:

... and 1 more

Continue to review full report at Codecov.

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


Fix/training progress

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Fix: During a source doc upload/ training, the transition progress from upload to training is super fast. Also, the progress bar isn't in sync with current progress.

Why was this change needed? (You can also link to an open issue here)
To address the above issue and improve the UX.

Other information:
closes: https://github.com/arc53/DocsGPT/issues/1003

Thank you so much @utin-francis-peter

Thank you so much @utin-francis-peter

It's my pleasure, @dartpain.
Thanks for having me.


gc: fix race and test failures

Ensures that all callers and the garbage collector are using the same lock instances to prevent cleanup of objects during creation.
Locks tend to work better when everything is using the same lock. This was missed during a refactor of the gc code before merge. This should fix the snapshot does not exist test failures.
Also added snapshot label command which I needed to debug.

Codecov Report

Merging #1650 into master will increase coverage by 0.19%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1650      +/-   ##
==========================================
+ Coverage   48.67%   48.87%   +0.19%
==========================================
  Files          27       27
  Lines        4074     4080       +6
==========================================
+ Hits         1983     1994      +11
+ Misses       1672     1667       -5
  Partials      419      419

Impacted Files
Coverage Δ

metadata/db.go
65.5% <100%> (+1.06%)
:arrow_up:

metadata/content.go
32.22% <0%> (+1.18%)
:arrow_up:

Continue to review full report at Codecov.

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

LGTM


Bug add conjunct slotref id to table function node to avoid result incorrect

Proposed changes
add conjunct slotref id to table function node to avoid result incorrect
Problem summary
Describe your changes.
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 34.84 seconds
stream load tsv:          451 seconds loaded<PHONE_NUMBER>9 Bytes, about 158 MB/s
stream load json:         23 seconds loaded<PHONE_NUMBER> Bytes, about 97 MB/s
stream load orc:          74 seconds loaded<PHONE_NUMBER> Bytes, about 14 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230323134907_clickbench_pr_119673.html


Initial release of managed devops pools

This checklist is used to make sure that common guidelines for a pull request are followed.
Related command

General Guidelines

[ ] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
[ ] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
[ ] My extension version conforms to the Extension version schema

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.
Testing screenshots:

Thank you for your contribution! We will review the pull request and get back to you soon.

Currently its in draft, since we want to check the command naming conventions.

@AllyW, @necusjz, please help review.


feat: enable wdc06 and mad02 PER DCs

Description
Enable new PER DCs, WDC06 and MAD02
Release required?

[ ] No release
[] Patch release (x.x.X)
[x] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

:tada: This PR is included in version 1.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Bump oauthenticator

This bumps the oauthenticator version to 15.0.0. However, doing this revealed some shortcomings and this PR contains some workarounds for those.
OAuthenticator
Some upstream issues that are relevant and provide more info:

https://github.com/jupyterhub/oauthenticator/issues/514
https://github.com/jupyterhub/oauthenticator/issues/515

CILogon
There is a possible issue with CILogon using an old OIDC endpoint for google (and open an issue upstream about this) (Old endpoint is http://google.com/accounts/o8/id, and new endpoint should be https://accounts.google.com/o/oauth2/v2/auth).
Look how for shown idps, the correct url is https://github.com/2i2c-org/infrastructure/blob/6debc6f283276922cc9d69fb40e34ce8694a31b0/config/clusters/2i2c/anu.values.yaml#L42
But the idp field of the userinfo response
https://github.com/jupyterhub/oauthenticator/blob/f3af268474ecce4fc2a9eb789c2e06cd692375fa/oauthenticator/cilogon.py#L306
is an old endpoint https://github.com/2i2c-org/infrastructure/blob/6debc6f283276922cc9d69fb40e34ce8694a31b0/config/clusters/2i2c/anu.values.yaml#L44
Opened an issue upstream about this one. https://github.com/ncsa/OA4MP/issues/45
TODO list

[ ] use oauthenticator 15.0.1 release instead of 15.0.0

This should now be ready for review. See the initial comment about follow-up issues. Also, I left a comment inline about deleting invalid users when using username_pattern that would love your thoughts on.

I've deployed this change to all of the hubs mentioned in the top comment and I was able to successfully login and start a server on those afterwards, so merging it 🚀 Thank you ✨


Prompt on Reload when other extensions are installing.

Reload will affect on other extensions installing process.

Reload won't impact the installation process as it happens in a separate process.

@sandy081
also we have this problem when it should restart vscode for new update.

Makes sense to prompt when VS Code is restarting.

Makes sense to prompt when VS Code is restarting.

also it can be makes sense when user trying to close app.
it should warn for incomplete procceings before users close app.

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.
If you wonder what we are up to, please see our roadmap and issue reporting guidelines.
Thanks for your understanding, and happy coding!