Feature/serialization siblings

Made serialization nodes have keys so that they can be siblings
Changed apparatus serialization to only have paths and metadata
Changed apparatus loading to work completely based on metadata
Updated apparatus jsons

I have a few questions:

they serialization node had key before right? how that helps in having siblings?
The identifier field does not exists on the json anymore. To get the identifier of the apparatus should we look at the identifier of the first element in the path ?
is there any changes needed in the container or provider codes ?

Q1) The serialization node didn't have a key before. Now the identifier is used to give it a unique id in the path, and the key is used to actually pull the apparatus from the backend. This means you can have the same key. but different ids.

Q2) I removed all the extra info because I realized it can all be given via metadata. You're right, to get the apparatus info, you can just look at the metadata in the root (1st path).
It's possible that in the future, that we need to attach specific info to the apparatus that dosen't belong in meta, but its not clear atm. Everything for now can be parsed from meta.

Q3) We will need to rebuild the container cause I changed some of the code that runs it. That should be my job to test though, so I won't merge until I do that.


"We plan" is wrong

Here, it says "We plan to add support ... in EF Core 6.0", which is already out. I'm not sure of the current state of things, so I can't do a PR to fix this, but I think it was pushed to version 8.

The second note here should also be reviewed.

@AntonC9018 thanks, submitted #4135 to fix these.


vm/DirectoryRename and DirectoryCreateDelete seem flaky

I often get flaky failure messages on DirecotryRename and DirectoryCreateDelete. Here are some example cases:
https://build.chromium.org/p/client.dart/builders/vm-win-product-x64-be/builds/685/steps/vm tests/logs/stdio
https://build.chromium.org/p/client.dart/builders/vm-win-product-x64-be/builds/680/steps/vm tests/logs/stdio
https://build.chromium.org/p/client.dart/builders/vm-win-release-ia32-be/builds/2864/steps/steps/logs/stdio
cc: @whesse @a-siva

It is strange that it is happening in product mode and not in debug or release mode.  I checked the runtime/tests/vm/vm.status file, and there is no mention of those tests there.  What could the difference be in product mode?

I've seen the failures in release mode too though (see https://build.chromium.org/p/client.dart/builders/vm-win-release-ia32-be/builds/2864/steps/vm tests/logs/stdio)

I had a short look. It looks like the directory tests work directly on /tmp/ (or c:/TEMP) and have the potential to interfere with each other (and any other file there).
We should update the tests to create a temp directory first (even though that makes the test kind of redundant: create a temp directory, to test creating a directory...

Fixed by https://github.com/dart-lang/sdk/commit/682a4d0036687120f03f2ec10b32995492cb5e08

This won't be enough, when multiple configurations (debug, release, ...) are running on the same machine. They could still interfere with each other.
Also, there is no guarantee, that there isn't another program that uses /tmp/create_delete_test_name or /tmp/rename_test_name for other purposes.
I think the only correct way to run the tests is to use Directory_CreateTemp and work in that directory.

For work on porting to Fuchsia there is a lot of value in keeping these tests simple and self contained. I don't think there is sufficient value in working around the problems you mention to make the changes you suggest, especially since there have been no flakes on the bots since the change.

I think it is quite straightforward to also add a nesting call to dart::bin::Directory::CreateTemp(name) in these tests, and they are just as self-contained - the C++ class Directory contains both methods.
This would make them perfectly free of race conditions.  But if the problem has disappeared, we don't absolutely need to do it.  I just want to note this here, so if it recurs, we know how to fix it.  We could also add a comment or a TODO at the site, but having it in the issue should be enough.


SDSTOR-9859 : add http server port option for dense sku and expose recovery latency metrics

Enabling the option http_port in test_volume, test_log_store, and test_meta_blk_mgr that one can specify the http port, o.w, a random port is picked. Furthermore, some gauges have been introduced in homeblk to expose the values of recovery latencies to Sherlock dashboard.
The http port is set to 5000 in nightly test suit as it is required by Sherlock.
Testing
The changes have been manually tested on 137/sds-tess85-01.
script: python3 /usr/local/bin/vol_test.py --test_suits=nightly --dirpath=/usr/local/bin/ --dev_list=/dev/data1 --http_port=5000
Accordingly a Homestore-test dashboard has been created to consume the introduced metrics in a plot named "recovery latency" (link)

Can you document the test you've done in your PR description?

@shosseinimotlagh after you merge, can you raise a PR to access-mgr to include the new homestore changes.


vstest.console.exe fails test run with socket exception

Description
Seemingly at random, our test run will fail with a socket connection error as follows:
vstest.console.exe, ProxyDataCollectionManager.InvokeDataCollectionServiceAction: TestPlatformException = System.IO.IOException: Unable to read data from the transport connection: An established connection was aborted by the software in your host machine. ---> System.Net.Sockets.SocketException: An established connection was aborted by the software in your host machine
   at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
   at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
   --- End of inner exception stack trace ---
   at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
   at System.IO.Stream.ReadByte()
   at System.IO.BinaryReader.ReadByte()
   at System.IO.BinaryReader.Read7BitEncodedInt()
   at System.IO.BinaryReader.ReadString()
   at Microsoft.VisualStudio.TestPlatform.CommunicationUtilities.SocketCommunicationManager.ReceiveMessage()
   at Microsoft.VisualStudio.TestPlatform.CommunicationUtilities.DataCollection.DataCollectionRequestSender.SendAfterTestRunStartAndGetResult(ITestMessageEventHandler runEventsHandler, Boolean isCancelled)
   at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.DataCollection.ProxyDataCollectionManager.<>c__DisplayClass15_0.<AfterTestRunEnd>b__0()
   at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.DataCollection.ProxyDataCollectionManager.InvokeDataCollectionServiceAction(Action action, ITestMessageEventHandler runEventsHandler).

We never received this error until we migrated to 15.6.
Steps to reproduce
I'm not sure how to reproduce this reliably.  We run it on an Azure VM with multiple VSTS agent instances installed, and it seems to happen more frequently when the VM resources are taxed, but occasionally it occurs when no other instances are performing tasks.
Expected behavior
Test run finishes successfully
Actual behavior
Test run fails
Diagnostic logs
Here are the diagnostic logs surrounding the error.  If there is any other diagnostic information you need, let me know. https://gist.github.com/NateB2/f97f8da22492cfb4489ddef87a0946e2
Environment
Windows Server 2016, VS 2017 15.6, VSTS agent 2.129.1.

We are seeing a similar issue on VSTS. This fails the test run though all tests pass. Can we disable this datacollection via a parameter in runsettings or commandline argument to vstest

Also seeing this IOException on VSTS, have been encountering it for the last two days. It seems to happen pretty frequently on builds - occasionally the exception is not thrown and the build succeeds. We're seeing the exact same exception as above.

I currently got it 100% of the time on VSTS, sometimes 2 or 3 times per build when running unit tests

same thing here, we got it systematically. Our build pipeline is currently broken, goodbye continous feedback :(

Primary investigation indicates this issue occurs when running datacollection(Code Coverage, Fakes, etc..) in parallel. To unblock, Please disable the parallel(MaxCpuCount in runsettings) option while running tests. I'm working on fix. Will let you know once fix is available.

Published Microsoft.TestPlatform.15.6.2 package with fix. You can get the latest test platform by using the Visual studio test platform installer task to try out the fix right away.
We are planning to fix this issue in VS 15.6 coming update.

We have ran builds with the fixed version since Monday, and no builds have failed due to the socket exception, so it appears to be fixed for us.  Thanks!

We're experiencing the same socket exception intermittently, in ~30% of builds. Vstest.console.exe_SocketException.txt
Environment details: We're running VsTest in an Azure Pipeline on a Hosted Agent. We've tried VsTest versions 16.0.0, 15.8.0.
We have an issue raised as well in
https://github.com/Microsoft/azure-pipelines-tasks/issues/9095 [Logs are attached in TestRunLog_log_19_5820.zip]

Same here, using VS 2017 Test Platform <IP_ADDRESS>9030503, I have to kill the vstest.console.exe-Processes to get another Unittest running.
Sometimes there are 2 processes spawned but I only run 1 Method with Test Explorer.
I will update von VS 2019 in a week and will look if it's buggy there too.
As a workaround I am adding PostBuild-Events to the Unit Test Project with cmd.exe /K "kill vstest.console.exe" but thats realy a hack, because its not with every testrun, sometimes you run 200 tests without a problem...

Hi @sroe,
We were able to resolve this issue in https://github.com/microsoft/azure-pipelines-tasks/issues/9095. The underlying error was covered up, and could be revealed by enabling a custom batch size. This allowed us to fix it.


More examples are needed

The ISAAR.MSolve.SamplesConsole project needs to be extended with more examples which will feature all of the available functionalities that MSolve provides. (@isaar/core)

Every team should contribute with examples


Calculate actions correctly

Did small changes to get_actions method.
It will hide and disable "delete" action if user has no delete permission.
It will show all actions if user has "change" permission.
It will show no actions if user has not "change" permission

Coverage decreased (-1.2%) to 88.562% when pulling 0386a6d53b6590fe3b5e0eca6ab8ba521f3c0119 on Anton-Shutik:master into 0ef047724123ce99014d8f247bd395c697d536d2 on ctxis:master.

@lefterisnik would you mind taking a look pls ?

@lefterisnik thanks a lot. Would you mind release it to pypi with minor version (1.7.1 for example) change ?

@Anton-Shutik done.

thanks a lot


[Task]: Test cythonized package on Windows and macOS

What needs to happen?
The released python wheels are cythonized and compiled. However, currently we only tests cython on linux platform (precommit on jenkins). Windows and macOS tests should be added probably with Github Action.
Issue Priority
Priority: 2
Issue Component
Component: build-system

I think it would be pretty straightforward to add a cython build to the GHA workflows that run python unit tests: https://github.com/apache/beam/blob/master/.github/workflows/python_tests.yml


[Feature] Could "emphasis.focus = 'series'" support DIY other series' fade out style ?

What problem does this feature solve?
when emphasis.focus is 'series', other series fading out. If we can custom the style, such as 'opacity', we can complete more visual effect.
What does the proposed API look like?
such as the configuration:
options = {
    series: [
        ...
    ],
    emphasis: {
        focus: 'series',
        fadeOut: { // work when focus is 'series'
            lineStyle: {
                opacity: 0.5,
            }
            ...
        }
};

You can specify the blur style for each line series. Please refer to this example.

Thx, I hava come true my design by setting blur.


java: Add "example" project to demonstrate how to use the Java client.

@enisoc
I've also added the example to test/local_example.sh and it passed in Travis! Cool! :)

LGTM!

Merging this now.
I didn't get the Travis test right initially but it's working now :)


Regression

It seems that my PR #273 has caused a regression where the first element will sometimes not appear.
if I change :  currentSlides = |] on L291 to currentSlides, this doesn't happen but this is obviously not a good fix, does anyone know why this would be happening ?

Having the same issue.  Removing the initial array fixes it for me too.


Added sitepoint/container to README

This container is a functioning component, but the motivation behind its creation is educational purposes. We/They will be encouraging developers to fork/modify/extend the container and make it their own.

:+1:


I added a readme.

U still need to write the installation & compiling part but okay.

By the way I can clone the repo, change the commit name, then force push soooo

From: MoltenCoreDev<EMAIL_ADDRESS>Sent: Saturday, February 13, 2021 12:19:32 AM
To: cainy-a/DiscordRichPresencePresets<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [cainy-a/DiscordRichPresencePresets] I added a readme. (#1)
U still need to write the installation & compiling part but okay.

You can view, comment on, or merge this pull request online at:
https://github.com/cainy-a/DiscordRichPresencePresets/pull/1
Commit Summary

I know you like descriptive commit names so i am going to ruin ur life!

File Changes

A README.mdhttps://github.com/cainy-a/DiscordRichPresencePresets/pull/1/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5 (16)

Patch Links:

https://github.com/cainy-a/DiscordRichPresencePresets/pull/1.patch
https://github.com/cainy-a/DiscordRichPresencePresets/pull/1.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/cainy-a/DiscordRichPresencePresets/pull/1, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AETAXXSQECFBGCIRTVVDCJ3S6XARJANCNFSM4XRROFSA.

Anyway yeah thanks!


Support persistent raw kernel sessions

Testing microsoft/vscode#127378
Create IW from a code lens
Reload VS code
IW has two sys infos in it after it starts up

This is currently not supported and we might want to reconsider since we can restore history in IW now.

duplicate of #3998


RoadMap 0.2

Support different log levels. Make a debug level that is verbose (logs headers & params) and trim the info level a bit further (remove params).
Log exceptions in JSON tagged with the request id (see support_errors branch for first attempt)

For those thinking of using 0.1, plug_logger_json is used in very high traffic services on production without issue and sends those logs to an ELK stack.
Future Improvements:

Find a way to make the fields logged more customizable.

https://github.com/bleacherreport/plug_logger_json/pull/4 solves point 2. Splitting up this ticket into other issues.


test/canary: troubleshoot corrupt witness memory

This is the canary method to find missing assignments in RowMajorMatrix.
If interested, I can turn this into a testing feature.

Better improve the API instead of this hack. Issue https://github.com/scroll-tech/ceno/issues/600


Module rename gulp task

Task which changes the name of the module folder, files in the folder and if the module has JavaScript change the path string in 'amd-config.json' to the new name.

Closed. This is no applicable anymore since we are moving to browserify. Check #45.


Haddock's resource directory ... does not exist!

I have cabal haddock (and stack haddock) failing with
Haddock's resource directory (/home/___/software/haskell/haddock/.cabal-sandbox/share/x86_64-linux-ghc-7.10.3/haddock-api-2.16.2) does not exist!

I have no idea how haddock thinks that this should be its resource directory, and what it needs it for. I do not see this concept mentioned in haddock -v|grep resource. The haddock I am using is quite  elsewhere:
which haddock
/opt/ghc/stable/bin/haddock

because I configured ghc with --prefix=/opt/ghc/ghc-7.10.3 and stable is a symlink to that.
Is haddock reading some stale dotfile?

OK, I could work around this by removing/re-installing/re-compiling half of the world ... but I still don't know what was happening.

When this happens to me, I find a resource directory that is known good and create a symlink to it (or copy paste the files to it). If you installed Haddock "normally", the resource files should have been installed to that directory.

This is definitely not a bug in Haddock (since Haddock lists the resource files in its haddock-api.cabal):
https://github.com/haskell/haddock/blob/8964666efc4d4ab9756a83d16a02115a38744408/haddock-api/haddock-api.cabal#L20-L39
For people running into this issue:

if you installed Haddock from cabal, stack, or used haddock bundled with a GHC/GHCJS/etc installation (the usual case), the bug is upstream with how resource files are handled

if you built the Haddock binary yourself (for instance with v2-build), consider:

installing the binary properly (recommended if you intend to use this binary later)
symlinking the resource folder to wherever it is you are calling Haddock
invoking Haddock with --lib=<path-to-resource-folder>


docs: Migrate Makefile to Compose V2 syntax

docs: Migrate Makefile to Compose V2 syntax
Description：The Makefile now reflects the change from using Compose V1 (docker-compose) to Compose V2 (docker compose).

these aren't used by many people - I'd be more tempted to remove than upgrade!


Review which error types don't need to be sent to Sentry

Candidates for ignoring:

missing chain param
pool id not found
sor:

The contract function "queryBatchSwap" reverted with the following
Invalid path, swap amount exceeds maximum for pool
Division by zero

sor division by zero comes from inputing 0 as swap amount. I think we should do input verification rather than ignoring the error for this.


PC Holographic Remoting Tutorials

Improved tutorial grammar and format.

Docs Build status updates of commit 6bcacfb:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/mr-learning-pc-holographic-remoting-01.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-pc-holographic-remoting-02.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

@jessemcculloch

@mr0ng Have these gone through the Flesche readability score check?

@hferrone Here are the readability score results:

@jessemcculloch This is ready for merging!


The region based isolation checker does not understand how to check.

Description
I got the Pattern that the region based isolation checker does not understand how to check. Please file a bug; this is an error in the Swift 6 language mode.
I stripped down the code from our application to the bare minimum.
The issue is observable on line containing the following code: await image.drawText(text: property.text)
Reproduction
import SwiftUI

@globalActor actor ImageActor: GlobalActor {
    static let shared = ImageActor()
}

@main
class OurApp: App {
    required init() {

    }

    var body: some Scene {
          WindowGroup { [self] in
              EmptyView()
                  .environmentObject(self.textProperties)
          }
    }

    let textProperties = TextProperties()

    @ImageActor
    private func generateImage() async -> ImageGenerator? {
        guard let image = ImageGenerator(size: CGSizeMake(240, 120)) else { return nil }
        for property in await textProperties.properties {
            await image.drawText(text: property.text)
        }
        return image
    }

}

@MainActor
@Observable
final class TextProperty: ObservableObject, Sendable {
    var text: String = "" {
        willSet {
            guard text != newValue else { return }
            // something to do
        }
    }
}

@MainActor
@Observable
class TextProperties: ObservableObject {
    var properties: Array<TextProperty> = [TextProperty()]
}

@ImageActor
final class ImageGenerator {
    public init? (size: CGSize) {
    }

    public func drawText(text: String) {
        guard !text.isEmpty else { return }
    }

}

Expected behavior
The result of the isolation checker shall be provided (compilation without any warnings vs. isolation warnings/errors). Now the isolation check cannot be completed which is wrong.
Environment
Swift toolchain from the XCode 16 beta 3
swift-driver version: 1.111.2 Apple Swift version 6.0 (swiftlang-<IP_ADDRESS>.15 clang-16<IP_ADDRESS>)
Target: arm64-apple-macosx14.0

Additional information
No response

Find out that the root cause of the issue is hidden in multiple macros:
@MainActor
@Observable
final class TextProperty: ObservableObject, Sendable {

If I remove @Observable the isolation checker provides feedback.

@vookimedlo I verified and this is already fixed.

(going to try to find a toolchain for you that you can use to validate this)

(also, thank you for filing the bug report! They are really helpful!)


Make more class methods private

Migrated from GitLab: https://gitlab.com/meltano/sdk/-/issues/70
Originally created by @aaronsteers on 2021-03-30 06:56:15

On further passes through the code (#69), a few methods pop out as methods we might not want developers to create a dependency on at this time - either because we don't think these components are fully stable, or because they should be treated as strictly internal.
For example, all of the methods and properties prefixed with singer_ should be treated as internal because (1) we don't want developers to be hung up in the Singer Spec, and (2) because the classes defined in the python-singer library are not to be considered stable. For instance, many of the python-singer functions and classes lack typing or proper documentation, and I'm not entirely sure we wouldn't replace those functions and classes with our own SDK-centric ones.

View 3 previous comments from the original issue on GitLab


support tencentos 3.1

What type of PR is this?
/kind feature
What this PR does / why we need it:

[x] Clean up kubean website related CI steps.
[x] Support for installing clusters on TencentOS 3.1 in air-gaped scenarios.

Which issue(s) this PR fixes:

Fixes #792 #785
Special notes for your reviewer:

https://github.com/ErikJiang/kubean/actions/runs/5208193274/jobs/9396612288

/lgtm

/lgtm


[BEAM-7024] Calcite BINARY to Beam Schema BYTES missing in CalciteUtils

Currently the mapping between FieldType to Calcite SqlTypeName is 1 to 1.
However, there is a special case where Calcite has both BINARY and VARBINARY, which should both be saved to bytes in Beam schema.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.


[amqp-common] Validate 'resource' parameter on credentials

For more context refer to #3971

Just an FYI - @chradek  seems like abort-controller build sometimes fails on Mac OS

Thanks @ramya0820
The issue with the flaky test on mac was actually fixed in master with #3784
It looks like the version on this branch is older than this change.

This will break existing Event Hubs customers who might not have been passing the "resource" when creating MSITokenCredentials. Therefore before closing #3971, we should ensure the below

Service Bus uses the preview 6 of amqp-common, but also sets the resource to Constants.aadServiceBusAudience

If we indeed move the setting of resource this way from amqp-common to Service Bus/Event Hubs, then I believe we don't need this check and error being thrown here.

Oh, I thought the approach was already thought through and wanted the specific implementation - will investigate

@mitchdenny @ramya-rao-a
I have verified that the changes in this PR work by testing using the repro app linked in #3971 description.
Had cloned run the app in VM with MSI enabled as discussed offline

Please remove the Event Hubs and Service Bus related changes from this PR
Create a new PR for Service Bus that uses amqp-common preview.6 and with the change from this PR
We don't need to ship a fix for Event Hubs as it is not broken.


Update website with new multi-module references

Now that 2.0-RC3 is out with the new project structure (yay - no more test code in prod), we should also update the website to mention the various sub-packages.
I see it's been updated to mention 2.0-RC3, but not the new structure.

yay - no more test code in prod

:+1: :smile:
Yes, I'm on it. Website and documentation will get some love within the next days

Done. This will be continued in more detail... (download links, api references etc.)


Resolve dialyzer warnings

Fixes #1

This PR resolves two dialyzer warnings. The first one was generated due to an invalid typespec while the latter was generated because of a potentially too "generous" typespec - that is an overloaded contract.
To resolve the latter I decided to ignore the overloaded contract warning, as it's merely dialyzer telling us that it doesn't support this kind of contract and as such doesn't produce any harm.

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[x] Feature branch is up-to-date with main (if not - merge main into your branch).
[ ] ~Added tests.~
[x] Ran mix check.all, it verifies the formatting and runs credo and dialyzer
[x] Ran mix test
[ ] Added an entry to the Changelog if the new code introduces user-observable changes. See the changelog entry format.

Pull Request Test Coverage Report for Build b3532b1e9f8fd2336d10f8e1eb5b50a3c3b305f0-PR-2

10 of 10 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.2%) to 98.75%

Totals

Change from base Build 2c2712146ba59b639a2c1fc37b76c64485eaeb07:
0.2%

Covered Lines:
79

Relevant Lines:
80

💛  - Coveralls


docs: fix Rule spec document typos

Fix typos in the Rule spec document

@nrnrk
This PR had to be reverted because I forgot to run the lint and build jobs for this PR that would have told us that you need to run make generate-k8s-api generate-hubble-api generate-api and make -C Documentation update-cmdref for this change. These commands will auto-generate additional changes in other files that will also need to be part of the changes submitted.
Please resubmit your changes in a new PR, being sure to run the above commands and submit those changes with your new PR as well. Thanks! Sorry for the mistake on our end :pray: .

Thank you for explanation in details. I will be sure to execute the make command and resubmit.


segfault when importing phy.cluster and phy.gui after installing pyqt5 from pip

phy doesn't work with PyQt5 unfortunately https://github.com/kwikteam/phy/pull/735

ok, I can live with that

closing in favor of #664

if someone finds a workaround for https://github.com/ContinuumIO/anaconda-issues/issues/1267 I'd be happy to see it!

We had the same issue in other projects and I found the following combination to work with Python 3.5:
pip install pyqt5==5.7 sip==4.18

But I guess this workaround is very temporary and will break with newer versions of Python.


Markdownlint fails with "Could not find 'bundler'" on MacOS - install specific bundler version

I have a pre-commit coinfiguration clause like this.
- repo: https://github.com/jumanjihouse/pre-commit-hooks
  rev: 'master'  # Use the sha / tag you want to point at
  hooks:
  - id: markdownlint
    args:
    - -r MD046=consistent

when running pre-commit it failed like so:
/usr/local/Cellar/ruby/2.6.2/lib/ruby/2.6.0/rubygems/dependency.rb:311:in `to_specs': Could not find 'bundler' (>= 1.2.0, < 3) among 41 total gem(s) (Gem::MissingSpecError)
Checked in 'GEM_PATH=/Users/michael-mbp/.gem/ruby/2.6.0:/usr/local/lib/ruby/gems/2.6.0:/usr/local/Cellar/ruby/2.6.2/lib/ruby/gems/2.6.0:/Users/michael-mbp/.cache/pre-commit/repo1_2m2ecl/rbenv-default/gems', execute `gem env` for more information
	from /usr/local/Cellar/ruby/2.6.2/lib/ruby/2.6.0/rubygems/specification.rb:1449:in `block in activate_dependencies'
	from /usr/local/Cellar/ruby/2.6.2/lib/ruby/2.6.0/rubygems/specification.rb:1438:in `each'
	from /usr/local/Cellar/ruby/2.6.2/lib/ruby/2.6.0/rubygems/specification.rb:1438:in `activate_dependencies'
	from /usr/local/Cellar/ruby/2.6.2/lib/ruby/2.6.0/rubygems/specification.rb:1420:in `activate'
	from /usr/local/Cellar/ruby/2.6.2/lib/ruby/2.6.0/rubygems/specification.rb:1452:in `block in activate_dependencies'
	from /usr/local/Cellar/ruby/2.6.2/lib/ruby/2.6.0/rubygems/specification.rb:1438:in `each'
	from /usr/local/Cellar/ruby/2.6.2/lib/ruby/2.6.0/rubygems/specification.rb:1438:in `activate_dependencies'
	from /usr/local/Cellar/ruby/2.6.2/lib/ruby/2.6.0/rubygems/specification.rb:1420:in `activate'
	from /usr/local/Cellar/ruby/2.6.2/lib/ruby/2.6.0/rubygems.rb:304:in `block in activate_bin_path'
	from /usr/local/Cellar/ruby/2.6.2/lib/ruby/2.6.0/rubygems.rb:303:in `synchronize'
	from /usr/local/Cellar/ruby/2.6.2/lib/ruby/2.6.0/rubygems.rb:303:in `activate_bin_path'
	from /Users/michael-mbp/.cache/pre-commit/repo1_2m2ecl/rbenv-default/gems/bin/run-mdl:23:in `<main>'

This appears to be related to this issue with bundler - https://bundler.io/blog/2019/01/04/an-update-on-the-bundler-2-release.html

I have ruby installed from homebrew.  Running
gem install bundler -v 2.0.1
solved this problem for me.  Leaving this record for posterity in case someone else hits the same issue.  There might be an automated fix that is possible for pre-commit but I think it would be too complex so I'm closing this ticket.  Please reopen if you have some reason to think there's a reasonable proper way to fix.


test(app): Android test for auth code flow

Codecov Report
Patch and project coverage have no change.

Comparison is base (365ccaa) 89.66% compared to head (9313d67) 89.66%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #472   +/-   ##
=======================================
  Coverage   89.66%   89.66%
=======================================
  Files          88       88
  Lines        3270     3270
=======================================
  Hits         2932     2932
  Misses        221      221
  Partials      117      117

see 2 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


When proxy is cycled app does not reconnect to running router

This issue is identical to https://github.com/smartdevicelink/sdl_android/issues/328 except that it happens when the proxy is cycled rather than when the app is restarted.  I first tried modifying the way the proxy service handled onProxyClosed() call but it did not resolve the issue.  I tried modifying the SdlBroadcastReceiver and this fixed the issue.
This one is block our testing of certain functionality in the HU such as changing languages; also when something bad happens like when some exception occurs such as https://github.com/smartdevicelink/sdl_android/issues/332.
Here is the existing code:
https://github.com/smartdevicelink/sdl_android/blob/develop/sdl_android_lib/src/com/smartdevicelink/transport/SdlBroadcastReceiver.java#L194-L198
	private static boolean isRouterServiceRunning(Context context, boolean pingService){
		...

	    		return true;
	        }
	    }

		return false;

	}

Here is my change to that code:
	private static boolean isRouterServiceRunning(Context context, boolean pingService){
		...

//	    		return true;
	        }
	    }

//		return false;
	        return runningBluetoothServicePackage.size() > 0;
	}

Yup that logic makes sense. Looks like I was trying to optimize to only run through as long as needed, but since that's where the list is populate it wasn't becoming a full list. Hotfix PR will be coming.


Maybe: Plunder golden inputs for TEST-PRINT-PARSED-PROGRAM-GOLDEN-FILES

As discussed in #257, it might be useful to have a function to steal golden inputs from other Quil test files for use in test-print-parsed-program-golden-files.
Two potential sources of pilfered golden inputs are tests/good-test-files/ and tests/compiler-hook-test-files/. Of the two, good-test-files appears to have the juicier inputs. Possibly there are other sources that could be plundered as well.
It's debatable whether this is a good idea or overkill, and probably depends on how often new test cases are added to the above directories. Note, however, that plundering golden inputs has already yielded one potential bug (#272).
Additional considerations
Any such function would probably need to maintain a blacklist of input files that should be skipped.
One reason to skip input files is that their printed form contains floats with lots of digits in the printed representation, which may or may not be portable and in any case seems sketchy to depend on the default formatting for ~F.
Also consider that INCLUDES would need to have their paths re-written since the newly produced golden file will not live in the same directory as the source file that is being plundered.
For example, the file tests/good-test-files/good-include.quil contains the following Quil program:
# include a file

INCLUDE "bell.quil"

BELL

In order to work with the existing test-print-parsed-program-golden-files test, the INCLUDE path would need to be re-written to INCLUDE "good-test-files/bell.quil", and also the test would need to be run with *allow-unresolved-applications* bound to t (I think).
Alternatively, any file containing an INCLUDE could be added to the blacklist.
POC bash script
Here is a proof-of-concept bash script. If we decide to implement the gold-plundering mechanism described in this issue, then the script would be converted to a lisp function and moved into tests/printer-tests.lisp alongside the function update-print-parsed-program-golden-files. Presumably, the cutesy pirate references would also be toned down!
This script is written with the assumption that it lives in the directory tests/printer-test-files/.
#!/usr/bin/bash

BURIED_TREASURE="../good-test-files/*.quil ../compiler-hook-test-files/*.quil"
TREASURE_CHEST=plundered-gold.quil

for gold in $BURIED_TREASURE; do
    echo "# Input"
    echo "# Plundered from $gold"
    cat "$gold"
    echo
    echo "# Output"
    echo
done >> "$TREASURE_CHEST"

echo "Arr. All the gold has been plundered from $BURIED_TREASURE."
echo "Don't forget to run CL-QUIL-TESTS::UPDATE-PRINT-PARSED-PROGRAM-GOLDEN-FILES in your lisp REPL."

With the benefit of time, I'm now fairly sure that, despite the amazing pirate-themed puns I'll be leaving on the table, automating the process of plundering golden inputs is probably overkill.
I do still think it makes sense to do a one-time import of at least the test cases from good-test-files, since doing so uncovered a potential bug in #272, in which case #272 should probably be fixed first.


PowerShell 2.* task documentation

In my case it looked like having a variable named Path was causing the release to fail on a PowerShell 2.* task with the following message:

Task         : PowerShell
Description  : This is an early preview. Run a PowerShell script on Windows, macOS, or Linux.
Version      : 2.129.0
Author       : Microsoft Corporation
Help         : More Information

Generating script.
##[error]The term 'powershell.exe' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

In this context it might be argued that the error message is explicit enough, but it wasn't obvious to me that the task was complaining about the Path release variable itself. I think that this behavior should be documented, as I couldn't find any reference to it anywhere else.

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

ID: 611642f0-881f-10b9-ae94-3c562001d1f0
Version Independent ID: 41efb94b-4c7a-64a3-b23b-70c8634ae727
Content: Release variables and debugging - Azure Pipelines
Content Source: docs/pipelines/release/variables.md
Product: devops
Technology: devops-cicd
GitHub Login: @RoopeshNair
Microsoft Alias: ronai

hi @dragosd, Thank you for your feedback.  Would it be possible to see a scrubbed version of your usage of the task?

This is an export of a test release containing a single task that can be used to reproduce the issue. I've replaced all Guids with empty ones and renamed URLs/org/project names:
PowerShell Task Test.json.txt
There is a single task for PowerShell 2.* (preview) which just simply writes the variable:

This is the variable definition:

This is the output:
PowerShell Task Test.log.output.txt
As soon as I rename Path to anything else, like OkPath the task completes successfully.

Here is the output with OkPath instead:
PowerShell Task Test-Ok.log.output.txt

@dragosd, Thanks for the great, detailed response! You can see in the logs you have posted:
2019-08-20T16:52:20.9678236Z Environment variables available are below...
...
[PATH] --> [ok value]

In PowerShell in a Windows environment the path environment variable, $env:Path, references the windows path environment variable. When you replace that in your pipeline, the OS no longer nows how to get to PowerShell.
Does that make sense?

@chasewilson, yes it makes sense, as in the end I noticed the same thing. The reason that I opened this issue is that I was expecting this behavior to be documented. It's not an obvious reason for why the failure occurs, unless you are aware that pipeline variables will clash with the environment ones.

I understand, I think it might be difficult to document every scenario like this, I might be able to place a not to be aware of predefined language variables. Do you think that would be have helped you avoid some of the confusion?

Yes, it would be helpful. Thanks!

I've created a note @dragosd. Thanks for all of your help and input! :) You should see the update within 24 hours


wrong error checks for recvfrom and recvmmsg

While testing i found when you send metrics exactly 11 or 4 characters long, those are dropped because if this checks (line 88+ in statsd.c):
int res = recvfrom(sock, buffer,
		sizeof(buffer) - 1, 0,
		(struct sockaddr *)&reporter, &reporter_len);
if (res == EAGAIN || res == EINTR || res == 0)
    continue;

res is either the message length or -1 on error. EAGAIN = 11 and EINTR = 4 so messages with length 4 or 11 are dropped.  This check should be res == -1 or replaced with the check further down, which check if res < 0 (line 99 in stats.c) and mark the message dropped.
I guess messages with length 4 or 11 are unlikely but maybe someone uses them.

Ugh, nice catch.  I've fixed this in #20.


Escape the request parameter

Fix for unescaped request parameter, resulting in an exception when the original URI contains ? or &.
Before the fix:

After:

@joozek78 I need your help again...
The tests on TeamCity fail with the following error:
System.Exception: Default template is missing
   at WebsiteProvider.ContentHandlers.<Register>b__8_3(String requestUri, String responseKey) in C:\TeamCity\BuildAgent\work\71b2b03598c46cc5\Website\src\WebsiteProvider\Api\ContentHandlers.cs:line 111
   at lambda_method(Closure , Request , IntPtr , IntPtr )
   at Starcounter.Rest.UserHandlerInfo.RunUserDelegate(Request req, IntPtr methodSpaceUriSpaceOnStack, IntPtr parametersInfoOnStack) in C:\TeamCity\BuildAgent\work\sc-5672\Level1\src\Starcounter.Rest\UriHandlersManager.cs:line 347
   at Starcounter.Internal.Web.AppRestServer.RunDelegateAndProcessResponse(IntPtr methodSpaceUriSpaceOnStack, IntPtr parametersInfoOnStack, Request req) in C:\TeamCity\BuildAgent\work\sc-5672\Level1\src\Starcounter.Apps.JsonPatch\AppRestServer.cs:line 98
   at Starcounter.Rest.UriManagedHandlersCodegen.RunUriMatcherAndCallHandler(String methodSpaceUriSpace, String methodSpaceUriSpaceLower, Request req, UInt16 portNumber, Response& resp) in C:\TeamCity\BuildAgent\work\sc-5672\Level1\src\Starcounter.Rest\UriManagedHandlersCodegen.cs:line 1140
   at Starcounter.Self.DoSelfCall(UInt16 portNumber, String method, String relativeUri, Dictionary`2 headersDictionary, String body, Byte[] bodyBytes, HandlerOptions handlerOptions, Request req) in C:\TeamCity\BuildAgent\work\sc-5672\Level1\src\Starcounter.Internal\Rest\Self.cs:line 390
   at Starcounter.Self.GET(String uri) in C:\TeamCity\BuildAgent\work\sc-5672\Level1\src\Starcounter.Internal\Rest\Self.cs:line 74
   at WebsiteProvider.ContentHandlers.<RegisterFilter>b__9_1(Request request, Response response) in C:\TeamCity\BuildAgent\work\71b2b03598c46cc5\Website\src\WebsiteProvider\Api\ContentHandlers.cs:line 157
   at Starcounter.Handle.RunResponseFilters(Request req, Response resp) in C:\TeamCity\BuildAgent\work\sc-5672\Level1\src\Starcounter.Internal\Handle.cs:line 509
   at Starcounter.Request.SendResponse(Response resp, Byte[] serializationBuf) in C:\TeamCity\BuildAgent\work\sc-5672\Level1\src\Starcounter.Internal\Http\Request.cs:line 1212
   at Starcounter.Internal.AppsBootstrapper.ProcessExternalRequest(Request req) in C:\TeamCity\BuildAgent\work\sc-5672\Level1\src\Starcounter.Apps.JsonPatch\AppsBootstrapper.cs:line 810
HResult=-2146233088

More information about this error may be available in the server error log.

Does TC cleanup the database properly between the test runs? I cannot see a call to staradmin delete db in the test script, but maybe it is somewhere else?

Should we add staradmin delete db before this line: https://github.com/StarcounterApps/Website/blob/develop/tools/Teamcity.ps1#L53
Or should it be handled elsewhere? I assume the latter

I believe we never implemented cleaning db between tests, because that
would make them run too long. We could try that tough, maybe the penalty
isn't so bad.
Simply changing the test script won't help, as we're talking about what's
happening between individual tests. We would need to change the tests to
delete database and restart apps

Pozdrawiam,
Marcin Goliński
On Fri, Jun 9, 2017 at 4:39 PM, Marcin Warpechowski <
<EMAIL_ADDRESS>wrote:

Should we add staradmin delete db before this line: https://github.com/
StarcounterApps/Website/blob/develop/tools/Teamcity.ps1#L53
Or should it be handled elsewhere? I assume the latter
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/StarcounterApps/Website/pull/110#issuecomment-307406928,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFvBIdTME65U7Sdw2aC-PPYlMxiCistXks5sCVkYgaJpZM4N1Vk2
.

No no, I mean only deleting the database before the build, not between the invidual tests.

On Fri, Jun 9, 2017 at 9:01 AM, Marcin Warpechowski <
<EMAIL_ADDRESS>wrote:

No no, I mean only deleting the database before the build, not between the
invidual tests.

Then I think it is done already by the @createrepo command (
https://github.com/StarcounterApps/Website/blob/develop/tools/Teamcity.ps1#L27
)

Pozdrawiam,
Marcin Goliński

Once again this seems to be a problem in the code that I submitted.
I swear that I test locally. I must have some fairy that substitutes that code that I test with the last working version.
Since @PatrykSzwer already positively reviewed, merging.

I will add tests.


android: Update Android Studio and Gradle.

cc @akalin-keybase @songgao

@akalin-keybase for this I think I need to update the CircleCI docker image. Do we have a guide for that?

cc @chrisnojima @mmaxim: I've gotten local plaintext notifications on Android halfway-working. Is this consistent with the approach we should be taking? And any ideas for making it work correctly when stopped?

OK this works now, ready for review. Plaintext notifications work even if the app was fully off when the remote notification was received.
cc @cjb

Bump, could use a review here.

@MarcoPolo I started to try the getConstants thing, but I couldn't figure out how you wanted me to plumb those through. So I'm going to look at it again tomorrow with fresh eyes.

@MarcoPolo ok all feedback implemented or resolved, and an additional comment explaining WTF is going on, which replaces the old (incorrect) explanation.


Very many (if not all) database operations may throw CouchDbException, which inherits RuntimeException and is thus an unchecked exception

I just realized that very many (if not all) Cloudant database operations may (rather unexpectedly) throw CouchDbException, which inherits Java's RuntimeException and is thus an unchecked exception.
Because of this, it's very easy to mistakenly write Cloudant API calls that do not have proper error handling since it's easy to leave exception handling out, since the exceptions thrown by the Cloudant API are not checked and thus not explicitly declared in the API method declarations.
Is this a deliberate design choice to have it like this? Perhaps to keep the API clean and easy to use? As the API is right now, it gives the impression that the actual API call never throws an exception but that any error handling logic is dependent on examining the state of the Response object.
Anyway, it's a bit annoying to have it hidden like that, since having proper and comprehensive error handling is quite crucial. I just stumbled upon an uncaught CouchDbException and realized the state of the API and now I need to wrap all my Cloudant API calls into a try {...} catch (CouchDbException e) {...} construct (in addition to later examining the state of the Response object) in order to have complete error handling logic at the lowest database client level. This would have been much more obvious if the exception in the API was checked to begin with.
Please improve the Javadoc, the code examples and/or other documentation to better guide the users of the API in proper error handling. Even better, please fix the API in the next major revision.

Thanks for raising this @sevokn - it was something inherited from the original lightcouch library and it is definitely something we have had in mind for the next major API change - in fact I thought we already had an issue open for it, but it appears we don't.
You are correct that the current approach is generally Response object for successful cases and CouchDbExceptions for errors.
The documentation is a bit sparse in this respect, we do in at least some places refer to sub-types of CouchDbException that may be thrown, but it should be clear throughout.
I think ultimately a move to checked exceptions from unchecked is preferable as it is more obvious to the programmer and also gives us tooling to warn/fail for missing @throws declarations in the javadoc.

We're not going to be changing this here. Our new cloudant-java-sdk(beta) follows the pattern of the IBM Cloud SDK core (which also prefers unchecked RuntimeExceptions), but we have tried to document more clearly the error handling expectations.


Feature: add paste from clipboard

Probably out of scope for the dropzone.

@jcalfee thank you for your feedback!
I also think it's out of the scope of this library and thanks to React's composition is easily done in userland.
I also think that a feature like this will raise the complexity of the project. For example, if you have multiple dropzones on screen, which one should react to the onPaste event?

Could maybe make the dropzones focusable by keyboard and only the currently focused one responds to the event

@jpdevries see my previous comment:

I also think it's out of the scope of this library and thanks to React's composition is easily done in userland.


Progress bar a11y

#721

reverted back to version with role="progressbar as it caused a11y violations

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


feature/button unit test

Add unit test packages (vitest/testing-library/happy-dom)
Add vitest config/Modify tsconfig/package.json for unit test
Fix unit test failed bugs
Summarize test reports into test-results
Add unit test workflow, refactor test workflows
change cache key for test
Fix workflow 'if' property bugs
Add storycap_deploy
rename storycap_deploy
modify on timing for test
Revert "modify on timing for test"
rename storycap_deploy
Replace vrt jobs with docs/storycap branch
add coverage check steps
Fix tests workflow bugs, refactor
Fix unit test workflow coverage path differ bug
Add unplugin-auto-import and settings
Modify vitest configs
Add button unit test

need recreate branch


(maint) Bump ruby version to 2.1.8

:+1:

In 3.x as well? I guess it works, so why not...

Yeah I figure latest 2.1.z for each branch that support 2.1.z (which is all of 3.x/stable/master right now). So I'm thinking once we merge this, we merge up and all branches get this.

whoa. I was under the impression that 3.x was 1.9.3/2.0.0 for Windows.

Guess it doesn't really matter given it's just testing. :)

@ferventcoder this is a travis-only change, no windows impact.


Creating and using array of ComPtr objects

Is there exist a sample of operating with some simple array of D3D12 resources that are ComPtr objects ?
Typically 'Hello' samples uses statically declared in .h file objects. If processing require an array od ComPtr objects of dynamic size - how to create it?
Tried:
In .h file:
  // pool of resources in accelerator
  int iNumFrameResources; // number of textures
  Microsoft::WRL::ComPtr<ID3D12Resource>** ppFramesResources; // pointer to array of frames textures resources

In array init:
      iNumFrameResources = 2 * df + 1; // number of frames to operate in the accelerator's pool
      ppFramesResources = new ComPtr<ID3D12Resource>*[iNumFrameResources];
      for (int i = 0; i < iNumFrameResources; i++)
      {
        ComPtr<ID3D12Resource>* pRes = new ComPtr<ID3D12Resource>;
        ppFramesResources[i] = pRes;
      }

And in usage loop for creating textures:
    for (int i = 0; i < iNumFrameResources; i++)
    {
      ID3D12Resource* pTextureResource = ppFramesResources[i]->Get();

      hr = m_D3D12device->CreateCommittedResource(
        &CD3DX12_HEAP_PROPERTIES(D3D12_HEAP_TYPE_DEFAULT),
        D3D12_HEAP_FLAG_NONE,
        &textureDesc,
        D3D12_RESOURCE_STATE_COMMON,
        nullptr,
        IID_PPV_ARGS(&pTextureResource));
}

The C++ compiler build it but
ID3D12Resource* pTextureResource = ppFramesResources[i]->Get(); - return zero pointer.

There's nothing in your 'creating textures' loop that is actually assigning the raw pointer to ID3D12Resource to any ComPtr instance. In fact, it just leaks all the resources.
Your code above is an unusual mix of raw pointers and smart-pointers, so it's really easy to get confused. You are losing a lot of the utility of the smart-pointer in the process. A better usage would be something like a std::vector<Microsoft::WRL::ComPtr<ID3D12Resource>> of resources. That said, you normally embed the smart-pointer in a data structure that's doing more than just tracking the resource reference.
You can find a lot of examples of ComPtr usage in DirectX Tool Kit. I also have a short tutorial page on ComPtr here.


[cmd][benchgraph] Remove benchgraph command

removed because https://github.com/benchhub/benchboard will be a super set of it, put this in a pull request so we can view (copy) stuff later ....
original introduced https://github.com/dyweb/gommon/issues/27

was trying to benchmark logger allocation and performance, using benchmark from zap ...


Assorted bugfixes to the recorder apps

Hi,
I don't know what the etiquette is around modifying apps authored by other people. In any case, I have noticed a few bugs in the recorder apps:

The label for the back button and the total distance label were put into fixed positions, designed for the Bangle.js 1
The X axis label (there was only one!) was odd and misaligned
In Recorder, the speed and altitude plotting tools didn't handle missing coordinates (this doesn't affect GPS recorder, as that one doesn't log records for situations where a GPS fix is not available) (Incidentally, I think the graph library should handle NaNs better)

That's great - thanks! And no worries at all about submitting fixes to other people's apps!


Add lenses for record types

The Raylib.Types modules contains many nested record types, which may need to be accessed deep inside.
This pull request implements lenses for those record types, which allow compositionally getting, setting, modifying the insides of data types.
P.S.: Note that the abstract "lenses" here obviously have nothing to do with camera lenses, even though there are camera data types in this library. For more information about lenses, see e.g. https://hackage.haskell.org/package/lens-tutorial-1.0.4/docs/Control-Lens-Tutorial.html
P.P.S.: If for some reason the dependency on the lens package is an issue, it can be removed without too much effort; see https://github.com/ekmett/lens/wiki/How-can-I-write-lenses-without-depending-on-lens%3F

Published in version <IP_ADDRESS>


HOTFIX: fix partition ordering in assignment

workround partition ordering not preserved by the consumer group management.
@guozhangwang

LGTM and merged to trunk.


added coalesce statement to provide a

default empty description
Description

Change overview (tick true):

[ ] This introduces backward incompatible changes
[x] This adds a new backward compatible Feature
[x] This fixes a Bug

Version information:

Previous Version: 0.0.1 major.minor.patch

Next Version based on Semantic Versioning (see above):0.0.2   major.minor.patch

How Has This Been Tested?

Checklist:

[ ] I have run tests and documented them above
[x] I have performed a self-review of my own code
[ ] I have updated the documentation
[ ] I have updated the CHANGELOG

Your change is fine but we seem to have forgotten a PR review on the initial commit.
Please update the PR description:

Description
Version tags
Checkbox formatting
Remove Tests if you didn't need them

Also please update the README:

Change the title from "Module" to the module name
Update the links in the badges
Add an example (this is also missing in the examples folder)

In variables.tf:

Add parameter descriptions
Don't use type any

In outputs.tf:

Add descriptions

Also in my opinion remove locals.tf if it's emtpy or move all locals into that file.

Your change is fine but we seem to have forgotten a PR review on the initial commit.
Please update the PR description:

Description
Version tags
Checkbox formatting
Remove Tests if you didn't need them

Also please update the README:

Change the title from "Module" to the module name
Update the links in the badges
Add an example (this is also missing in the examples folder)

In variables.tf:

Add parameter descriptions
Don't use type any

In outputs.tf:

Add descriptions

Also in my opinion remove locals.tf if it's emtpy or move all locals into that file.

as discussed we dont work on that anymore. This PR fixes a bug


deny missing docs

Deny missing_docs for the entire crate.

Will this be possible to deny with the protobuf module? It currently auto-generates the rust code for the protobufs and thus is not fully documented by default.
Perhaps there's a way to exclude that module from the restriction?


Stop depending on qiskit-terra qiskit.quantum_info.operators.symplectic.clifford.Clifford.stabilizer | Upgrade Qiskit-Terra Dependency Cap the Qiskit-Terra version

What is the expected behavior?
We want to continue being able to use the latest version of Qiskit Terra as the Qiskit ecosystem evolves. Right now, our dependence on the soon-to-be-deprecated in qiskit-terra 0.24.0:   qiskit.quantum_info.operators.symplectic.clifford.Clifford.stabilizer is causing issues for us.
The solution might be as simple as finding where qiskit.quantum_info.operators.symplectic.clifford.Clifford.stabilizer has been moved to - or might be very complicated if that feature is being deprecated with no equivalence.

Hey @dsvandet inside the private method _evolve_clifford inside BasePauli we have an import
        # pylint: disable=cyclic-import
        from qiskit_qec.operators.pauli import Pauli
        from qiskit_qec.operators.pauli_list import PauliList

Is there a reason we don't import these at the top?

Handled in #385


Only critical logs should use ERROR logging level

Description

Currently, some logged errors are actually not errors, but debugging messages and warnings. Therefore, there're too many errors in Kibana which makes finding real issues more difficult. Also, it's not clear what cases need to be investigated and what don't.
We should use the ERROR logging level only for critical errors which require immediate investigation and which mean that something went wrong. Other logs should be classified as WARN/INFO/DEBUG.
After only critical errors are classified to the ERROR level, we may consider using notifications for such logs.

Thanks for bringing this up, @nkryuchkov!! I've been having thoughts about this for ages.
I think we should formalize a "logging methodology" that will make logs more consistent and our lives easier.
My thoughts about the matter:
As you said ERRORs should be reserved for rare and unexpected situations that could indicate a code problem. If an error occurs often, not due to a bug, it means we need to handle this case better. As I see it, errors should only be caused by internal conditions to the node. A database inconsistency is a classic example.
Any unexpected input to the node should only ever result in a WARNING.
I still haven't decided how we should handle consensus-related log messages. E.g. a Hare iteration not reaching consensus would cause another iteration to start - I intuitively want to make it a warning.
The difference between INFO and DEBUG is more about frequency. The default for messages about natural progression of the protocol and node should be info, with frequent "spammy" messages downgraded to debug.
I really wish that as a user I could be able to see a log of only high level info messages and warnings/errors. So for example, I'd like to see a message when the Hare reaches consensus and a layer is validated (every 5 minutes), but every received block (~50 within a few seconds, every 5 minutes) would be spammy. I'd like to know when I publish an ATX (every 2 weeks), but not when every ATX is received (possibly thousands every 2 weeks). I'm not sure if this should be our INFO level, or if there should be another "INFO+" level, or some other mechanism for this (some way of filtering log messages).


Use interrupts where possible.

 The logical next step is to implement a module interface for interrupts using callbacks perhaps. This is an Issue to remind myself, or if somebody else fancies taking it on, PRs are welcome!

Hello to make it faster : change the sleep(0.05) to sleep(0.02) ;-)


Handling varargs in Python

fixes #1653

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Leutrim Shala seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Back As Difficulty / Cant Change Bf Strums?

Describe your bug here.
1.Error in menu
2.Idk someone said this in discord i need if is real or not
Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
Yes, EX BF(Bob a Bullshit) and Tails (Triple Trouble ñ)

Back was fixed, update your source
Press 7, go to the chart editor, and change the note assets file there

Back was fixed, update your source
Press 7, go to the chart editor, and change the note assets file there


Attempt to fix upgrade.sh to support --cluster-init

Could fix #23

I wonder if rather than using sed here, a quick update to the grep is all that's needed?
K3S_PID=$(ps -ef | grep -E "k3s .*(server|agent)" | grep -E -v "([^-]init|grep|channelserver)" | awk '{print $1}')
Based on #5 they were trying to capture the case of a container init, so this should suffice.
@galal-hussein I don't suppose you have a chance to look at this? This bug has bitten me as well.

Hey guys, any chance to actually merge it?
It would be great to have working updates on embedded ha setups.
Thank you:)

Hey guys, any chance to actually merge it?
It would be great to have working updates on embedded ha setups.
Thank you:)

Relatively recent versions of k3s actually hide their command-line flags using setproctitle, so this shouldn't be necessary any longer. Are you running an older version of k3s with dqlite?

Relatively recent versions of k3s actually hide their command-line flags using setproctitle, so this shouldn't be necessary any longer. Are you running an older version of k3s with dqlite?

k3s version v1.19.7+k3s1 (5a00e38d)
ubuntu@node-1:~$ sudo ./k3s server --cluster-init &>/dev/null  &
[1] 1514
ubuntu@node-1:~$
ubuntu@node-1:~$ ps aux | grep k3s
root        1514  0.2  0.5  11164  4744 pts/0    S    08:39   0:00 sudo ./k3s server --cluster-init
root        1515 59.6 11.0 11301700 97744 pts/0  Sl   08:39   0:02 ./k3s server
ubuntu      1526  2.0  0.0   8160   736 pts/0    S+   08:39   0:00 grep --color=auto k3s
ubuntu@node-1:~$```

looks like it's not fixed unfortunately

k3s version v1.19.7+k3s1 (5a00e38d)
ubuntu@node-1:~$ sudo ./k3s server --cluster-init &>/dev/null  &
[1] 1514
ubuntu@node-1:~$
ubuntu@node-1:~$ ps aux | grep k3s
root        1514  0.2  0.5  11164  4744 pts/0    S    08:39   0:00 sudo ./k3s server --cluster-init
root        1515 59.6 11.0 11301700 97744 pts/0  Sl   08:39   0:02 ./k3s server
ubuntu      1526  2.0  0.0   8160   736 pts/0    S+   08:39   0:00 grep --color=auto k3s
ubuntu@node-1:~$```

looks like it's not fixed unfortunately

@engineer11111 sure it is. Your sudo command has the full args but the actual k3s process below it does not.

@engineer11111 sure it is. Your sudo command has the full args but the actual k3s process below it does not.

I haven't checked it myself but it does look like it's fixed. Going to close this.


Remove commented out, but also illegal props from FlatList

getItem and getItemCount are both illegal. They are already not enabled (commented out), this PR removes them for good. For reference, RN is supposed to throw an error whenever either prop is passed to FlatList, as below:
invariant(
      !getItem && !getItemCount,
      'FlatList does not support custom data formats.',
    );

Further, data prop cannot be any type, but must be an array.
Finally, it seems _CellRendererComponent can be enabled (this I did not test)

I would prefer to keep all Virtualized props & comment the ones that aren't supported so we don't have to check all the time when we have to sync inherited props (my comments also works for the same pattern we use in lot of places)

I wasn't sure if they were disabled by mistake and RN documentation was not quite helpful. I think it will be good to have comments so that it's clear what's going on with that module.

Adding comment is fine, and we should have some locally (on top of each "disabled" props) for future bindings update imo.

What do we want to do with this PR?
I would go for either just add a comment before commented stuff & maybe uncomment the thing we are not sure about?

I've neglected this, I'll prepare a PR to at least add the comment.


Expose of API port

Expose of API port added in Docker image.

Withdrawn due to incorrect upstream branch selection.


Add configuration yaml validation check to github tests

Addressed by https://github.com/chanzuckerberg/cryoet-data-portal-backend/pull/130


[FEATURE] minify task: Use workerpool for terser

Based on https://github.com/SAP/ui5-builder/pull/700:

Changed logging to verbose
Added option 'useWorkers' to processor. Implicit activation through
taskUtil parameter seemed a bit odd. Moved that to the minify task
Added JSDoc

Coverage: 94.572% (-0.04%) from 94.609% when pulling ca3190ead28845f57741133e203f2d5d95f7c3a8 on minify-task-workerpool into cfe639097ce7a0776a6d2dc6c61445bf6e720f18 on main.

I did some benchmarks according to our documentation, comparing this PR to the current main branch:
openui5-sample-app

ui5-builder Ref
Command
Mean [s]
Min [s]
Max [s]
Relative

main (9aa8b1c)
ui5 build
748.5 ± 20.9
725.2
803.0
Baseline

minify-task-workerpool (75463c3)
ui5 build
796.5 ± 33.7
739.3
870.6
+7%

sap.ui.core

ui5-builder Ref
Command
Mean [s]
Min [s]
Max [s]
Relative

main (9aa8b1c)
ui5 build
10.915 ± 0.219
10.718
11.451
Baseline

minify-task-workerpool (75463c3)
ui5 build
7.790 ± 0.061
7.659
7.856
-29%

OpenUI5 testsuite (including dependencies)

ui5-builder Ref
Command
Mean [s]
Min [s]
Max [s]
Relative

main (9aa8b1c)
ui5 build --all
86.258 ± 1.258
84.060
87.747
Baseline

minify-task-workerpool (75463c3)
ui5 build --all
73.263 ± 1.187
70.492
74.629
-15%

Specs: MacBook Pro M1 Max


[bug]: Inconsistent number of occurrences for definitions.standards.requirements.descriptions

The number of occurrences in the JSON, XML and Protobuf Schemas are different for the
definitions.standards.requirements.descriptions field.
In JSON schema we have descriptions array:
https://github.com/CycloneDX/specification/blob/bfb6f8baf77bbf98a4c0a54392508ba3ccf2e22e/schema/bom-1.6.schema.json#L4950-L4955
where the following would be possible:
  "descriptions": [
    "Requirement is described here",
    "and here"
  ],

In the XML schema we have 0..1 descriptions/description entries:
https://github.com/CycloneDX/specification/blob/bfb6f8baf77bbf98a4c0a54392508ba3ccf2e22e/schema/bom-1.6.xsd#L8022-L8033
where this would not be possible:
  <descriptions>
    <description>Requirement is described here</description>
    <description>and here</description>
  </descriptions>

In the Protobuf schema Definition.Standard.Requirement.descriptions is a text field:
https://github.com/CycloneDX/specification/blob/bfb6f8baf77bbf98a4c0a54392508ba3ccf2e22e/schema/bom-1.6.proto#L1888-L1889
Already discussed this with @jkowalleck during python-lib improvements and decided that we should address it here.

@stevespringett is this something we would put in an interim bugfix release, or do we wait until 1.7 ?

Looks like the JSON and Protobuf are good, but description should be unbounded in the XML. @jkowalleck lets go ahead and do a point release for the XML only if that makes sense to you. If so, would you mind doing it. I'm traveling for the next two weeks.

Looks like the JSON and Protobuf are good, but description should be unbounded in the XML. @jkowalleck lets go ahead and do a point release for the XML only if that makes sense to you. If so, would you mind doing it. I'm traveling for the next two weeks.

I might be able to provide a patch for this next week.

i will merge @hakandilek's upcoming patch and do the dot release for XML.

@hakandilek ,
When preparing a fix, please also extend the related test files:

https://github.com/CycloneDX/specification/blob/master/tools/src/test/resources/1.6/valid-standard-1.6.json
https://github.com/CycloneDX/specification/blob/master/tools/src/test/resources/1.6/valid-standard-1.6.xml
https://github.com/CycloneDX/specification/blob/master/tools/src/test/resources/1.6/valid-standard-1.6.textproto

it appears that there is no case with multiple descriptions, yet.
Thank you very much in advance.

When preparing a fix, please also extend the related test files:

Sure, fix is in place. Test files to follow.


Permission by Block

we look for the permission functionality by block instead of duplicating the pages we can play on the blocks.
Because I like to hide some button.
Is it planned in the next release?

@khanfouf not in the next release but we are planning on reworking internal data logic which would enable us to support different views. I don't have a timeline for you, so just keep an eye out on our forum.

hi @khanfouf, you wrote you want to hide buttons - can you please explain more? Are you talking about automation buttons or UI buttons (Add record, Import, Export)?

Inactive. Closing.


Advice on Visualizing Multivariate Optimization in GPyOpt

Hello All -
Thank you in advance for your help and thank you for this great library! It is very useful.
I am using GPyOpt to do Bayesian Optimization provided 3D data (eventually higher dimensional data as well) i.e. X1, X2, and X3. I am wondering if you have any advice on how to effectively visualize the results of the optimization. The plot_acquisition function is great for the 1D case, so I am wondering if there is a way I can extract the optimization results and take a 2D slice that I can then feed into the plot_acquisition function somehow.
If you have any advice on how to achieve this or if you could refer me to example, I would really appreciate the help. Thank you in advance!

I like to use a pairs plot with the color proportional to the score on the lower triangular and the color proportional to the step number on the upper triangular.
You could also try a pairs plot with size proportional to step and score proportional to color - it's a taste thing.
I've also used animations (time = step, z = score, x = X1, y = X2) for projections onto X1 and X2, but it really depends on who you're presenting to - sometimes the glitz of an animation can distract from your message.

Thank you @ekalosak.  I will definitely try these ideas!

e.g. the diagonal is just the marginal frequencies of values used on each dimension, the lower diagonal is a 2D marginal of the ibid - just using 2D marginals rather than 1D marginals - and the upper diagonal colors the score and uses size for step number.

This is nice, is there someway of adding the code to create it e.g. as a gist somewhere?

@lawrennd that modified pairs-plot is written in R, for better or worse. I can turn around a gist pretty quickly (pending an internal review here at Opsani) if there're no concerns about bleeding the codebase into another language.

No worries if it's too much trouble, but it would be cool to see it somewhere!

@lawrennd here's the gist: https://gist.github.com/ekalosak/f2582f7420374d394ab10d2dda056aaa


js 的 demo 运行不起来啊

Your file name in command line is incorrect. Your file name is ollama.js, while you've typed alama.js in terminal 😑

Hi, @chergn as m0o0scar pointed out it looks like you have a typo in your file name. Let me know if that is not the case 👍


Unify cell base images

Testing on existing VL workflows:

[x] Laserfarm
[ ] Veluwe Proto DT
[ ] Vol2bird


use conf override in favor of telemetry abstraction

Replaces previous .Values.telemetry abstraction with a top level configOverride to configure the collector.

Thanks for the feedback @dmitryax
I've been thinking, while the baseConfig generation is clever, it might be nice and simple to have, within the values file, a top level .Values.baseConfig laid out in its entirety, no templating tricks, and then .Values.(agent/standalone)Collector.configOverride values. WDYT?

Having the templates for yaml configs, makes it clean and easy to introduce tricks like default memory_limiter processor configuration based on provided k8s resources memory limits. With .Values.baseConfig, it would be not that straightforward, I tried that approach, but I'm open to suggestions if you can manage to do it in a cleaner way.

Looks good. Thanks!
Should we update the examples in README along with this change?

Yep, done! PTAL

Thanks @dmitryax , PTAL

Looks good to me. Just one nit. Thanks for rewriting it!

My pleasure and thanks for bouncing back ideas, I like how it turned out!

Thanks for this PR! I had to dig a bit to understand how configuration worked in the previous format. Now it's much more clearer 👍

Great to hear @ferrarimarco!


Is there any way to detect scroll direction

I'd like to know if there is any way to detect which direction user scrolled horizontally.
Is there any?
Thank you for the great plugin!

Is there any solution to detect horiyontal  scroll direction?


plugin import fail

from cil.plugins.ccpi_regularisation.functions import FGP_TV
fails to import, produces message
----> 1 from .regulariser import FGP_TV, ROF_TV, TGV, LLT_ROF, FGP_dTV,\
      2         SB_TV, TNV

ModuleNotFoundError: No module named 'cil.plugins.ccpi_regularisation.functions.regulariser'

Maybe it is because the module file is called regularisers.py (plural), not regulariser.py?

yes that is a problem
https://github.com/vais-ral/CCPi-Framework/tree/master/Wrappers/Python/cil/plugins/ccpi_regularisation/functions

Closed by #709


[HELP] RGPLua Crashes Finale

What do you need help with?
When I tried to install it, it was fine, until it asked me which folder(s) for it to look through for plug-ins.  It accepted my request (the entire plug-ins folder), then told me to close finale. I did so, and upon reopening it, it immediately crashes. Finale runs when I do not have RGP in the plugins folder, but then I can't use my Lua scripts.
What have you tried?
I have tried downloading a fresh version of RGP and replacing it. I tried an uninstall and immediately reinstall it. I attempted to see if there was a way to "reset" RGP's search to something else.
A few details I should mention: I am running Windows 11 Pro (Build 22621), and have Finale 27.

I've been tracking what appears to be the same issue with another user. I traced the code down to a call to CryptDecrypt in wincrypt.h. It appears to be failing there, and I am getting no diagnostic info. The program simply aborts. @asherber do you have any ideas of how to proceed? (You know more about Win than I do.) Could some windows installs be missing a component? Is there a way to check for messages in the system logs?

Hmm. I would think that the crypto resources would be standard on all installs, since they're used for lots of things. @rpatters1 Do you have a sample app or sample code you could send with a minimal repro of the issue? Of course, I'm still on Windows 10, but at least maybe I can see what areas might be problematic.
Maybe also ask the mailing list if anyone is successfully using RGPLua latest on Windows 11.

I can't reproduce it at all on my machine. I had to use debug printfs to trace it on a user's machine. He say he's using Win10, so it may not be related to Win11.
That said, I found a notice that wincrypt apis are deprecated, which made me wonder if there is an optional installer somewhere.

Deprecated, but not yet removed. These are part of the basic Win32 api, so I would expect them to be present.

I think I've fixed it. Fairly or not, Imma blame this on ChatGPT. But my code was calling CryptDecrypt with a null output buffer (to get the length). But that ain't how it works, because of course it's a Microsoft API so it's not going to be parallel to CryptEncrypt. That would make too much sense.
No, CryptDecrypt apparently takes as given that the decrypted text will be no longer than than the encrypted text. To be fair to ChatGPT, it also pointed out this discrepancy in my code after I asked it about it point blank.
So I think I've found the bug. I'll think about the best way to release a fix.

Was I meant to do anything with this? If not, it's fine! I just don't quite understand what's going on.

I have uploaded a fix at the download site. If you encounter any further problems, please open a new issue.


Update reference-connect-accounts-permissions.md

Per internal discussion, clarifying the type of account for AD DS connector since VSA, MSA or gMSA are not supported.

@billmath
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


New-RubrikSnapshot not working correctly when confirming the action

Current Behavior:
Using New-RubrikSnapshot prompts whether we want to proceed using:
Are you sure you want to perform this action?
Performing the operation "Testing SLA" on target "Gold".
There seems to be two issues here:

If you enter "N", it still proceeds and takes a new snapshot.
If you enter "Y", it proceeds and takes a snapshot using the SLA specified (Gold in the example below). If you select "N", it uses *Forever" SLA.

PS C:\Users\Jan> Get-RubrikVM -name "jp-lt-rhel"  | new-rubriksnapshot -sla Gold -verbose
VERBOSE: Validate the Rubrik token exists
VERBOSE: Found a Rubrik token for authentication
VERBOSE: Gather API Data for New-RubrikSnapshot
VERBOSE: Selected 1.0 API Data for New-RubrikSnapshot
VERBOSE: Load API data for New-RubrikSnapshot
VERBOSE: Description: Create an on-demand snapshot for the given object ID

Confirm
Are you sure you want to perform this action?
Performing the operation "Testing SLA" on target "Gold".
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "Y"): N
VERBOSE: Multiple URIs detected. Selecting URI based on VirtualMachine:::298e0713-6c59-484a-9009-38686e422170-vm-12970
VERBOSE: Loading VMware API data
VERBOSE: List of set parameters: [SLA, Gold] [Verbose, True] [id,
VirtualMachine:::298e0713-6c59-484a-9009-38686e422170-vm-12970]
VERBOSE: Build the body parameters
VERBOSE: Adding forceFullSnapshot...
VERBOSE: Adding slaId...
VERBOSE: No body for this request
VERBOSE: Submitting the request
VERBOSE: Invoking request with a custom timeout of 15 seconds
VERBOSE: POST
https://<IP_ADDRESS>/api/v1/vmware/vm/VirtualMachine:::298e0713-6c59-484a-9009-38686e422170-vm-12970/snapshot with
-1-byte payload
VERBOSE: received 382-byte response of content type application/json
VERBOSE: Received HTTP Status 202
VERBOSE: Formatting return value
VERBOSE: Filter the results

progress  : 0.0
status    : QUEUED
startTime : 2020-10-28T13:50:13.944Z
id        : CREATE_VMWARE_SNAPSHOT_298e0713-6c59-484a-9009-38686e422170-vm-12970_56f5a180-e5ea-4043-b9c7-20b4d2f04fa9::
            :0
links     : @{rel=self; href=https://<IP_ADDRESS>/api/v1/vmware/vm/request/CREATE_VMWARE_SNAPSHOT_298e0713-6c59-484a-
            9009-38686e422170-vm-12970_56f5a180-e5ea-4043-b9c7-20b4d2f04fa9:::0}

PS C:\Users\Jan>

Expected Behavior:
I would say that the expectation is that we are prompted whether we are 100 % sure we want to take a snapshot. If we reply "Y", then snapshot is taken (using the SLA specified). If "N" is entered, snapshot is not taken.
Steps to Reproduce:
Please provide detailed steps for reproducing the issue.

Run "Get-RubrikVM -name <VM_THAT_EXISTS>  | new-rubriksnapshot -sla <SLA_NAME_THAT_EXISTS>"
You are prompted if you want to proceed.
Enter "N" - snapshot is still taken.
Check the snapshot that was created - it was created with "FOREVER" SLA instead of your specified <SLA_NAME_THAT_EXISTS>

Context:

Rubrik PowerShell Module Version: 5.0.3
PowerShell Version: 5.1.18362.752
Operating System: Microsoft Windows 10 Pro

Failure Logs
N/A

Hey @JanPillarRubrik,
I've changed the behavior of the New-RubrikSnapshot cmdlet:

It will not prompt for Test-RubrikSLA by default anymore
If -Confirm is used and Test-RubrikSLA didn't run, the script will not continue, determining that if SLAID is empty while SLA was specified, something is wrong.

The changes are staged in #714


evaluate code

I read your experimental results in detail, but I didn't find the evaluation part of the code in the code. Can you share it?

Hi! Thank you for this comment - the experiments are in a separate repo here in notebooks!


How end product look like ?

Can you please add more details in readme like screen shots.. etc

Sure! Thanks for requesting this. I will add some more details @sanjay555. Thanks


Improvement for k8s.io/docs/setup/independent/troubleshooting-kubeadm/

This is a...

[ X] Feature Request
[ ] Bug Report

Problem:
missing command for fixing
Proposed Solution:
please add missing command fixing issue "TLS certificate errors"
export KUBECONFIG=/etc/kubernetes/admin.conf
Page to Update:
https://kubernetes.io/docs/setup/independent/troubleshooting-kubeadm/#tls-certificate-errors

the command is not exactly missing, as $HOME/.kube/config is also a search path, but if you set KUBECONFIG it will take precedence.
the troubleshooting tutorial assumes that you have not set KUBECONFIG, but if you have, you might
as well update it to another location.
free free to send a PR for this clarification if you want
/help
/kind cleanup
/priority backlog
/sig cluster-lifecycle


[Test] [Builtins] Ensure 'Typeable', 'Lift' etc instances are present

This adds static tests ensuring the existence of Lift and Typeable instances for built-in types.
 Ok, we have a problem then!  Ok, we have a problem then! But let me rerun to see if it's persistent.

It wasn't persistent, all other runs were fine.

Screenshoting a slack discussion (can't bother copying and then fixing formatting):

I'm working on fixing all of that, plus making the general mkNil and mkPair.

Closing in favor of #5971.


Feed URL
https://evilmartians.com/chronicles.atom
More Info
No response

closed by https://github.com/murtuzaalisurti/rssed/commit/267ef2c4dae3b3c17e69ba10822edba6852e9518


nbest in server outputs

the nbest are put on stdout regardless the verbosity value.

I solved this issue on branch direct-server. I've removed the line:
manager.OutputNBest(cout, nBestList);
There's no need to output all the nbest list anymore, because these results are going to be passed programmatically to the upper layers, instead outputting them on standard output.

I will check if this change do not cause any problem in the xmlrpc server version
If ok, I will commit the change in mmt-dev as well.
Does anyone have objections?
Nicola
On Jan 20, 2016, at 3:55 PM, Davide Caroselli wrote:

I solved this issue on branch direct-server. I've removed the line:
manager.OutputNBest(cout, nBestList);
There's no need to output all the nbest list anymore, because these results are going to be passed programmatically to the upper layers, instead outputting them on standard output.
—
Reply to this email directly or view it on GitHub.

This change has been made on code that replaces XMLRPC, so there 's no backward compatibility issue. If you want to look at the code, it's available here: https://github.com/ModernMT/MMT/tree/direct-server/src/Decoder/native

Update @nicolabertoldi : I decided to skip for now the new server implementation  in branch direct-server because it's becoming too expensive in terms of time and effort.
Anyway, you could apply the same fix to the XMLRPC server here: https://github.com/ModernMT/mosesdecoder/blob/mmt-dev/moses/server/TranslationRequest.cpp#L220
I'm going to close this issue for now because it is actually a Moses issue, not MMT.
Please let me know if you have any questions.


Altering the default settings

Hi there, I've been using multielo in a google sheets document to track game data. I've been running it in a colab notebook, and I haven't figured out a good way to change the default settings for K,D and Scoring function base. I thought editing the multielo.py file would work, just rewriting the relevant lines with .sub() but that doesn't work even with reloading the module.
If possible does anyone have a nice way of doing this without downloading and creating a custom version for my use? I want it to be all done within the colab notebook.
Thanks!
ps, love the project, super useful.

found the setting, it's in demo.ipynb facepalm


Terminal search skips some entries while searching upwards

VSCode Version: 1.33.1
OS Version: linux

Steps to Reproduce:

Open a terminal on the right side (about 80 chars wide)
cat attached file LOG2.txt
Press search and enter error to the searchbar, search upwards (shift + enter)
line 373 e.g. got skipped, check with grep -i error

Does this issue occur when all extensions are disabled?: Yes/No

I believe this will be fixed when we update xterm.js, there were 2 recent fixes to search https://github.com/xtermjs/xterm.js/pull/1866 and https://github.com/xtermjs/xterm.js/pull/2025


LEDDisplay handle negative numbers

In this PR, the minus sign is handled as a digit, and must be in first
position. See issue #12.

Sorry, I'm not responsible of the adjunction of .react to all the md docs, this has been done automatically when I commit changes. Is this normal?

@shammamah any thoughts on this?

Hey!

Sorry, I'm not responsible of the adjunction of .react to all the md docs, this has been done automatically when I commit changes. Is this normal?

Yeah, that's run automatically when you build the package: https://github.com/plotly/dash-daq/blob/master/bin/generateDocs

Sorry, I'm not responsible of the adjunction of .react to all the md docs, this has been done automatically when I commit changes. Is this normal?

That's another side effect of building the package.
Have you been able to install the package locally and run demo.py without any issues?

Everything works: python demo.py is running(without change) and npm run demo gives this output.

I'd like to delete my github account. Are you interested in this PR, or should I close it.

@benjaminabel I can take care of it from here on out!

any news on this? In one application we use the led display to display user selectable data which also include e.g. data from an accelerometer which can be negative...

@bearsh This PR looks like it's an orphan, so I made the same changes in #52. I'll let you know when that's merged in!


Debug aids

Make it a bit easier to debug GPU errors.

PR #2317 is an expanded replacement for this PR.


Fix cmd line settings to be passed with -C and not -Des.

which is deprecated and will be removed in newer crate versions.

Please add a entry in the CHANGES.txt. This breaks the test layer for use with older crate versions


Ensure that SMTP connection failures do not cause messages to drop

Currently, if himalaya fails to connect or authenticate to the remote SMTP server, it causes the written message to be discarded with no user recourse. I propose re-opening the (s)end, (d)raft, (e)dit or (q)uit? dialogue, so that the user may select "edit" in order to save their written message. Alternatively, you could prompt the user to save their drafted message to disk somewhere.

Duplicate #59


Centralize Ruby Version to .ruby-version

What are you trying to accomplish?
The .ruby-version file is the ecosystem standard for defining a Ruby version.  This PR adds the .ruby-version file, and removes all other references to Ruby in this repository, aligning it with the standard.
What should reviewers focus on?

[!IMPORTANT]
Please verify the following before merging:

Verify that the changes in the PR meets the following requirements or adjust manually to make it compliant:

[ ] .ruby-version file is present with the correct Ruby version defined
[ ] There is no Ruby version/requirement referenced in the Gemfile (no lines with ruby  <some-version>)
[ ] A Gemfile.lock is built with the defined Ruby version
[ ] There is no TargetRubyVersion defined  in rubocop.yml
[ ] There is no Ruby argument  present in  ruby/setup-ruby Github Actions that do not  run on a Ruby matrix (no lines with ruby-version: “x.x”)

Please merge this PR if it looks good, this PR will be merged if there isn't any activity after 4 weeks.

For yjit-bench, we need to constantly use multiple Ruby versions. Can we avoid locking the Ruby version in this repository? I don't want .ruby-version to inadvertently switch Ruby from master to 3.3.0 when I enter yjit-bench directory, for example.