Update Surefire to non-milestone version

Description
Discovered in https://github.com/dockstore/swagger-java-zenodo-client/pull/24#discussion_r1727146058
Review Instructions
None. If it works, CI tests will pass, and if they work, the PR will be merged.
Issue
None
Security and Privacy
If there are any concerns that require extra attention from the security team, highlight them here and check the box when complete.

[x] Security and Privacy assessed

e.g. Does this change...

Any user data we collect, or data location?
Access control, authentication or authorization?
Encryption features?

Please make sure that you've checked the following before submitting your pull request. Thanks!

[x] Check that you pass the basic style checks and unit tests by running mvn clean install
[x] Ensure that the PR targets the correct branch. Check the milestone or fix version of the ticket.
[x] Follow the existing JPA patterns for queries, using named parameters, to avoid SQL injection
[x] If you are changing dependencies, check the Snyk status check or the dashboard to ensure you are not introducing new high/critical vulnerabilities
[x] Assume that inputs to the API can be malicious, and sanitize and/or check for Denial of Service type values, e.g., massive sizes
[x] Do not serve user-uploaded binary images through the Dockstore API
[x] Ensure that endpoints that only allow privileged access enforce that with the @RolesAllowed annotation
[x] Do not create cookies, although this may change in the future
[x] If this PR is for a user-facing feature, create and link a documentation ticket for this feature (usually in the same milestone as the linked issue). Style points if you create a documentation PR directly and link that instead.

Jeez, tests keep failing.

Makes sense in principle, may need to add https://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#failifnospecifiedtests to the configuration

Do you know off-hand why we have profiles with no specified tests? I can look at it more in detail if you don't know, but I wonder if it's flagging a legit issue.

Do you know off-hand why we have profiles with no specified tests? I can look at it more in detail if you don't know, but I wonder if it's flagging a legit issue.

If I had to guess, we have profiles for things like unit tests, hoverfly tests, non-confidential tests, but not all modules have the full set, so when a profile is set I would not be surprised if a particular module does not have any tests.
The weird part is that it seems like it should have occurred already.
But I do see that that module had no tests before, so maybe a regression?
[INFO] --- maven-surefire-plugin:3.0.0-M5:test (default-test) @ dockstore-language-plugin-parent ---
[INFO] No tests to run.

I think one thing to do is to set the flag and then see what the total number of unit tests recorded on Circle CI ends up being.

seems ready to merge, but not needed for 1.16 (barring conflict)

seems ready to merge, but not needed for 1.16 (barring conflict)

I keep meaning to double-check if this is a regression or not before merging. I don't think it is, that it is caused by a surefire update, and not that we stopped executing tests. In any case, I think this can wait.


Fixed spelling of uri_parser_class in code example

The uri_parsing_class option presented in the docs does not exist. It took me some time to figure out that the name of this option is actually uri_parser_class.
Changes proposed in this pull request:

Correct uri_parsing_class to uri_parser_class in docs example.

Coverage increased (+0.2%) to 96.475% when pulling cec61f204f92f6e24d1d69e07d5d79b534f06e2c on Klebert-Engineering:improvement/docs-uri-parser-class-option-spelling into 96bdcb010a4e5180c2bce18295e7b576c9c1ef0f on zalando:master.

Thank you!

:+1:


fix unbound this in createReadStream()

fixes #269

Just noting here as in the issue, that this seems to be a problem for some transpilers, and not an actual bug. Will merge anyway.

@mafintosh thanks!


Upgrade to gRPC Request

Hello Latest Truecaller 13 versions are using grpc, so we should library like https://github.com/fullstorydev/grpcurl to make grpc requests.
.proto files are available inside apk and by using grpc it will ensure working for future versions.

Hello Latest Truecaller 13 versions are using grpc, so we should library like https://github.com/fullstorydev/grpcurl to make grpc requests. .proto files are available inside apk and by using grpc it will ensure working for future versions.

Would you share those .proto files so I give it a try?

@TonyAnine, and @ArielS1 Were you able to crack?


Release code update

All fixes from testing release 1-0-11.

This is unfortunately a big chunk of code, it's all the fixes requested during testing.


scrollToX() calls normalizeVertical()

Should call normalizeHorizontal() ?

That's my bad~ Thanks @yusiwen
https://github.com/BosNaufal/vue2-scrollbar/commit/605a9e24f955be201be6a00b9b84b1966ed29904


fix: entropy of openssl rand -base64 32

Fixes #821
corrected typo mistake by replacing 512 with 256.

Thanks for spotting this


WarningReader: always return nil records after err

While working on #1895 I ran into some unexpected zqd behavior (illustrated in the yaml test) when posting to the log/paths endpoint: records continue to be read after a bad line. This is not the case with the /log endpoint.
The bug is caused by an interaction between zbuf.WarningReader and zbuf.ReadBatch. WarningReader returns nil, nil after encountering an error, which means that no records remain. But if called subsequently, it does return more records. This trips up zbuf.ReadBatch, which needs to read two consecutive nil records in order to return a nil batch.
(Arguably ReadBatch should also be adjusted ... but it doesn't seem entirely unreasonable to call an EOF'd reader a second time).

While that doesn't seem unreasonable at all, it does represent a change to the zbuf.Reader contract

@nwt there's no change to the zbuf.Reader contract in this PR. To help me understand, can you clarify what should be checked in the 36 lines found by git grep?

I guess I was looking at the zbuf.Reader contract as making no guarantees about the behavior of Read after it returns nil, nil and at this PR as saying, "Actually, Read should continue to return nil, nil, and here's a change to one implementation to make it do that," so I was saying, "That feels like a change to the contract, so we should update the contract, and we should also make sure that all the implementation implement the contract."

Ah! I see.

at this PR as saying, "Actually, Read should continue to return nil, nil,

Since ReadBatch has relied on this behavior for some time, I'd inferred that other Reads do continue to return nil, nil, or we'd have noticed this earlier.

That feels like a change to the contract

Hmm, I was thinking at this part of the zbuf.Reader comment:

a nil record and nil error to indicate that no records remain.

And thinking if you send something indicating that no records remain, it would be broken behavior to send a record after that. Otherwise what's the point of ever returning nil, nil?
Regardless, the fact that there are differing interpretations mean that this might be worthy of an after-discussion. In 2021 🎉 !

#1962

#1962


feature iter_find_many

Rendered

Just FYI, I think most standard library additions go through the API Change Proposal process. I'm reluctant to speak for the libs-api team, but I think that is the process they typically use for a change like this.

I feel like this API is too overloaded. It's essentially just filter / filter_map + collecting into an array, with the former being stable APIs and the latter having lots of unresolved questions which would all apply to this API as well.

This is not quite the same as filter or filter map I think. The use case is quite different. To achieve the same thing with filter map would take 6 or 7 lines of code likely.  I like the API for find many, but I agree it definitely gets a little more dense for find_many_map. I think the trade off is worth it, but that’s a matter of taste. Cheers,Eric WoolseyOn Nov 19, 2022, at 8:21 AM, Christopher Serr @.***> wrote:
I feel like this API is too overloaded. It's essentially just filter / filter_map + collecting into an array, with the former being stable APIs and the latter having lots of unresolved questions which would all apply to this API as well.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

Just FYI, I think most standard library additions go through the API Change Proposal process. I'm reluctant to speak for the libs-api team, but I think that is the process they typically use for a change like this.

Entirely poissible. This is my first contribution here so I may have got the process wrong. It seemed like this was the right place based off of The contribution book.

Link to cuviper's comment on IRLO, and ewoolsey's comment that introduced those functions.
I think they are well motivated but would work better as methods.

I think they are well motivated but would work better as methods.

Oh yeah perhaps I should have been more clear in this RFC. The intention 100% would be to implement them as methods.

I have to be missing something since the RFC gives implementations that appear to be entirely safe code, but what happens if I write an iterator which continually returns a mutable reference to the same thing?  In normal code, the returned reference would stop further advancement of the iterator, but this API is for explicitly collecting multiple mutable references in a way that (appears to be) generic over all iterators, and that would let me have two mutable references to the same memory.
For instance, say that iter_mut() on something is evil. Then, I could:
something.iter_mut().enumerate().map(|(v, i)| { *v = i; v })

This API appears to be offering soundness by assuming that unique keys point to unique references, but the above iterator doesn't (and if it doesn't compile--I didn't try--then more advanced things could, e.g. via unsafe).

So where do things go from here? I would love to move forward with this if possible. So far it seems like the only complaint is that the api is a bit chunky.


How to install wids??

Wids is automatically installed along with webdataset. That is, when you install the webdataset package, you can import webdataset as wds and import wids.


[stable/openebs]: update owner and maintainer

Signed-off-by: prateekpandey14<EMAIL_ADDRESS>Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[ ] Variables are documented in the README.md
[ ] title of the PR contains starts with chart name e.g. [stable/chart]

/ok-to-test

/ok-to-test

/lgtm

/test pull-charts-e2e


Is there a log_file for reviewing?

When I train, the log will output in the terminal, but I can't find a log_file in the project path? Is there a log_file for reviewing?

Redirecting the output to a file is the easiest way to handle this.


If a collection or map attribute is final it should be possible to just update the content without touching the attribute [DATAJDBC-254]

Jens Schauder opened DATAJDBC-254 and commented

No further details from DATAJDBC-254

This is a best guess as there isn't much to go on here, but from the referenced issue on spring-data-commons it seems that the question is regarding the immutable object support added in the Spring Data Lovelace RC1 Release and whether this adversely impacts making updates to entities with final Collection or Map type attributes. I created a quick test to verify that this is not the case and I believe this issue can safely be closed.


Lacks visual appeal and flow

As someone has been in multiple compromise situations, this document does not flow well. It needs screen shots and a greater visual appeal for all types of users.

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

ID: 04d540fc-67c0-86ea-7bcb-9a08cdc52e1b
Version Independent ID: 022eebfd-370d-7b8b-1a26-81d0dfb0aae7
Content: Responding to a Compromised Email Account in Office 365
Content Source: Enterprise/responding-to-a-compromised-email-account.md
Service: o365-solutions
GitHub Login: @chrfox
Microsoft Alias: chrfox

Thanks for the feedback. There is a video embedded and given that this is a fast turn around topic for deflection, additional revisions will be considered later.


Series.setShowInLegend(false) does not disable legend entry

It looks like there's a missing ! in the code.  From [line 72 of Legend_AxesChart] (https://github.com/timmolter/XChart/blob/4421317ca19f5df3fe0b5fe1833087b3a31d95c6/xchart/src/main/java/org/knowm/xchart/internal/chartpart/Legend_AxesChart.java#L72):
      if (series.isShowInLegend()) {
        continue;
      }

p.s. thanks for XChart, it's fantastic!

Thanks, fix pushed. Will release 3.0.1 soon.


non sqlite handling like reflect result gh not working

Describe the bug
non sqlite handling like reflect result gh not working.
more detail in followinf discussion.
https://github.com/hrntsm/Tunny/discussions/154#discussioncomment-5385556
To Reproduce

run optimize using tunny v0.7.0 and journal storage.
move output tab and push reflect result to gh

Expected behavior
run any beheiver correctly like sqlite
Screenshots
Environment

OS: Windows 11
Rhino Version v7.23
Tunny Version v0.7.0

Additional context

#154


Sample buildpacking a simple python app

Write a sample app in Python, make it getting an image created without Dockerfile aka using Buildpacks

@ulises-jeremias let me know if it works for you

sounds great! feel free to create a new dir called examples/buildpack/ on your PR

great! hands-on it


Remove submodule

+1 for letting the makefile pull the submodule, but it's even better to not have it at all.

Thanks so much! This makes the code base a lot smaller. Removing the string dependency cleans things up too. Good call!


Cargo: Build command does nothing

Version of VSCode: 1.11.2
Version of the extension: 0.3.13
OS: macOS
Description:
After upgrading to 0.3.13, running the "Cargo: Build" or "Cargo: Test" commands from the Cmd+Shift+P menu does nothing.
Output of the "Rust logging" channel:
DEBUG: Configuration: Rustup: updateComponents: this.components=["cargo-x86_64-apple-darwin (default)","rust-docs-x86_64-apple-darwin (default)","rust-src (installed)","rust-std-aarch64-apple-ios","rust-std-aarch64-linux-android","rust-std-aarch64-unknown-fuchsia","rust-std-aarch64-unknown-linux-gnu","rust-std-arm-linux-androideabi","rust-std-arm-unknown-linux-gnueabi","rust-std-arm-unknown-linux-gnueabihf","rust-std-arm-unknown-linux-musleabi","rust-std-arm-unknown-linux-musleabihf","rust-std-armv7-apple-ios","rust-std-armv7-linux-androideabi","rust-std-armv7-unknown-linux-gnueabihf","rust-std-armv7-unknown-linux-musleabihf","rust-std-armv7s-apple-ios","rust-std-asmjs-unknown-emscripten","rust-std-i386-apple-ios","rust-std-i586-pc-windows-msvc","rust-std-i586-unknown-linux-gnu","rust-std-i686-apple-darwin","rust-std-i686-linux-android","rust-std-i686-pc-windows-gnu","rust-std-i686-pc-windows-msvc","rust-std-i686-unknown-freebsd","rust-std-i686-unknown-linux-gnu","rust-std-i686-unknown-linux-musl","rust-std-mips-unknown-linux-gnu","rust-std-mips-unknown-linux-musl","rust-std-mips64-unknown-linux-gnuabi64","rust-std-mips64el-unknown-linux-gnuabi64","rust-std-mipsel-unknown-linux-gnu","rust-std-mipsel-unknown-linux-musl","rust-std-powerpc-unknown-linux-gnu","rust-std-powerpc64-unknown-linux-gnu","rust-std-powerpc64le-unknown-linux-gnu","rust-std-s390x-unknown-linux-gnu","rust-std-sparc64-unknown-linux-gnu","rust-std-wasm32-unknown-emscripten","rust-std-x86_64-apple-darwin (default)","rust-std-x86_64-apple-ios","rust-std-x86_64-pc-windows-gnu","rust-std-x86_64-pc-windows-msvc","rust-std-x86_64-rumprun-netbsd","rust-std-x86_64-unknown-freebsd","rust-std-x86_64-unknown-fuchsia","rust-std-x86_64-unknown-linux-gnu","rust-std-x86_64-unknown-linux-musl","rust-std-x86_64-unknown-netbsd","rustc-x86_64-apple-darwin (default)",""]
DEBUG: Configuration: Rustup: updatePathToRlsExecutable: rlsInstalled=false
DEBUG: askPermissionToInstallRls: choice=undefined
DEBUG: handleMissingRls: permissionToInstallRlsGranted=false
DEBUG: Configuration: updatePathToRacer: findRacerPathSpecifiedByUser: path=undefined
DEBUG: Configuration: updatePathToRacer: findDefaultRacerPath: foundPath=/Users/sfackler/.cargo/bin/racer
DEBUG: Legacy Mode Manager: MissingToolsInstallator: getMissingTools(): pathDirectories=["/usr/local/opt/openssl/bin","/usr/local/bin","/usr/bin","/bin","/usr/sbin","/sbin","/Applications/Wireshark.app/Contents/MacOS","/Users/sfackler/.cargo/bin","/Volumes/git/autopr","/usr/local/dev-env/bin"]
DEBUG: Legacy Mode Manager: MissingToolsInstallator: getMissingTools(): tools={"racer":"/Users/sfackler/.cargo/bin/racer","rustfmt":"rustfmt","rustsym":"rustsym"}
DEBUG: Legacy Mode Manager: MissingToolsInstallator: getMissingTools(): racer's path=/Users/sfackler/.cargo/bin/racer
DEBUG: Legacy Mode Manager: MissingToolsInstallator: getMissingTools(): this.missingTools = []
DEBUG: Legacy Mode Manager: CompletionManager: start: enter
DEBUG: Legacy Mode Manager: CompletionManager: start: racerPath=/Users/sfackler/.cargo/bin/racer
DEBUG: Legacy Mode Manager: CompletionManager: start: ENV[RUST_SRC_PATH] = /Users/sfackler/.rustup/toolchains/stable-x86_64-apple-darwin/lib/rustlib/src/rust/src

I think pull request #212 fixes this.

I'm seeing something similar after the new update, declining RLS leads to "no build command defined" for .rs files.

Done.

I'm still seeing this even with 3.14 and:
    "rust.forceLegacyMode": true

Ctrl+Shift+B in any .rs file shows prompt "No build task defined".

@vvanders add this to your keybindings.json as a workaround:
{
        "key": "ctrl+shift+b",
        "command": "rust.cargo.build.default",
        "when": "editorLangId == rust"
    },
    {
        "key": "ctrl+shift+t",
        "command": "rust.cargo.test.default",
        "when": "editorLangId == rust"
    },
    {
        "key": "ctrl+shift+r",
        "command": "rust.cargo.run.default",
        "when": "editorLangId == rust"
    }

@vvanders,
It is described in CHANGELOG.md
I removed keybindings as Visual Studio Code uses them too.

Ah I see.
That seems like a pretty severe breaking change. I can't define a cargo build task that links in errors and overriding the keybindings seems like something that a new user won't attempt and bounce off the plugin.
Right now RLS is still nightly so if you're using stable the new plugin doesn't give much over syntax highlighting in that configuration.

Also keybindings.json doesn't work, the task caller overrides it and doesn't pick up the bindings.

You still can execute commands with command palette showed by CTRL+P

I use the last version of VSCode.
File->Preferences->Keyboard Shortcuts.
In the field enter "Cargo".
Hover "Cargo: Build".
Press the plus button to the left.
Choose some keybinding.
Test it.
It works for me.

Working for me now on 0.3.14, thanks for the fix!

@sfackler,
I actually doesn't know why it broke in the first place.

Does anyone have a problem matcher definition?

@lnicola,
Why do you need it?
Why can't you use Cargo check?

A problem checker would make the VSCode integration nicer, as the build errors would show up in the "Problems" pane.
I'm pretty sure the Cargo Build command used to do that in the previous version (now it just opens a the terminal). It feels like a step back in usability, just like @vvanders said.

If RLS is enabled, then yes. Cargo command is executed in a terminal.
This is because RLS provides diagnostics.

Ah, I see. Changing the file didn't trigger the analysis for me (or it was stuck), which caused the confusion. It worked after I clicked the status bar button.

For those who don't understand why the extension does not parse the output of Cargo command.
Disadvantages:

Duplicate diagnostics: from RLS and from the last command
Obsolete diagnostics: RLS hides diagnostics after fixing them, but they would still be presented as a result from the last command.

The issue with RLS is it's just not stable enough for me to use. Anything of moderate complexity or including unit tests causes it to give bad results.
Don't get me wrong I'm really looking forward to it but it's just not at point where I can use it for production work.
I've reverted back to 0.3.11 and I'll be staying there until things stabilize a bit.

@vvanders,
You can use "forceLegacyMode".

And now I realized that I didn't add information about it to the documentation.


[Linters/CI] fixes current golangci-lint errors

Description
Resolves current errors on main related to golangci-lint linters checks not passing.

Summary generated by Reviewpad on 21 Jun 23 22:00 UTC
This pull request fixes current golangci-lint errors. It touches three files, making a total of 17 insertions and 2 deletions. The changes include the removal of a duplicated import statement, the commenting of an unused code element, and the modification of a variable's data type in one function within a Go package. There are also some unused code elements and mocks included in the patch.

Type of change
Please mark the relevant option(s):

[x] Code health or cleanup

List of changes
Resolves the following issues reported by golangci-lint:
app/client/cli/consensus.go:4: File is not `goimports`-ed (goimports)
	"fmt"
p2p/raintree/router.go:58:2: field `nonceDeduper` is unused (unused)
	nonceDeduper          *mempool.GenericFIFOSet[uint64, uint64]
	^
p2p/utils_test.go:86:6: func `waitForNetworkSimulationCompletion` is unused (unused)
func waitForNetworkSimulationCompletion(t *testing.T, wg *sync.WaitGroup) {
     ^
p2p/utils_test.go:107:6: func `createP2PModules` is unused (unused)
func createP2PModules(t *testing.T, busMocks []*mockModules.MockBus, netMock mocknet.Mocknet) (p2pModules map[string]*p2pModule) {
     ^
p2p/utils_test.go:120:6: func `setupMockNetPeers` is unused (unused)
func setupMockNetPeers(t *testing.T, netMock mocknet.Mocknet, numPeers int) (peerIDs []libp2pPeer.ID) {
     ^
p2p/utils_test.go:149:6: func `createMockRuntimeMgrs` is unused (unused)
func createMockRuntimeMgrs(t *testing.T, numValidators int) []modules.RuntimeMgr {
     ^
p2p/utils_test.go:183:6: func `createMockBuses` is unused (unused)
func createMockBuses(t *testing.T, runtimeMgrs []modules.RuntimeMgr) []*mockModules.MockBus {
     ^
p2p/utils_test.go:230:6: func `prepareBusMock` is unused (unused)
func prepareBusMock(busMock *mockModules.MockBus,
     ^
p2p/utils_test.go:241:6: func `prepareConsensusMock` is unused (unused)
func prepareConsensusMock(t *testing.T, busMock *mockModules.MockBus) *mockModules.MockConsensusModule {
     ^
p2p/utils_test.go:282:6: func `prepareTelemetryMock` is unused (unused)
func prepareTelemetryMock(t *testing.T, busMock *mockModules.MockBus, valId string, wg *sync.WaitGroup, expectedNumNetworkWrites int) *mockModules.MockTelemetryModule {
     ^
p2p/utils_test.go:312:6: func `prepareEventMetricsAgentMock` is unused (unused)
func prepareEventMetricsAgentMock(t *testing.T, valId string, wg *sync.WaitGroup, expectedNumNetworkWrites int) *mockModules.MockEventMetricsAgent {
     ^

@bryanchriswhite can you please check if functions/vars with //nolint:unused are needed or can be deleted? Linter has been complaining that this code is not in use.

@okdas have you been running the linter via the make target and/or using --build-tags test? All of those except the nonceDeduper field are definitely used in tests. The `nonceDeduper should be cleaned up in #855 (check about halfway though the commits.

@bryanchriswhite I have not – these issues were reported by the CI. Thank you! I'll check how we can include the build tags for linter in GitHub Actions.

I thought I had updated it already in both the makefile and CI but maybe I missed something.

This ticket has been superseded by #885.


Fix #1205 #1131 #1127 #1029 #942 - Requirements updates

Describe the contribution
Fix #1205: Added task and CDS file write default filenames
Fix #1131: Removed optional from EVS log
Fix #1127: Non-parameter reload/restart doesn't increment cmd error
Fix #1029: Removed system log elements from reset preservation list
Fix #942: Simplifed table partial load file requirement
Testing performed
CI - requirements documentation only
Expected behavior changes
None
System(s) tested on
CI
Additional context
None
Third party code
None
Contributor Info - All information REQUIRED for consideration of pull request
Jacob Hageman - NASA/GSFC

Ping @olamoo13 - updated requirements for testing.

CCB:2021-06-09 APPROVED

catches up requirements to code


do not select objects on right-click

Currently, if DNA ends are selectable, and one right clicks on a DNA end to bring up the context menu, it becomes selected:

This is incorrect behavior; only left-click should select.

I approved the PR without actually running the code (assuming that it had been tested for the desired behavior).
I just checked this in the latest dev branch, and it's still appears to be happening:

I think this code will be relevant:
https://github.com/UC-Davis-molecular-computing/scadnano/blob/b6c8b208ec8623fdbc3c2c45ffa5ab46130d785d/lib/src/view/design_main_strand_dna_end.dart#L171-L176

I think I made it so if a user right clicks on a dna-end, then it does not get selected. But if a user were to select a dna-end and then right click on a strand it doesn't automatically unselect it. Should I account for the second case too?

I think I made it so if a user right clicks on a dna-end, then it does not get selected.

I right-clicked on the end itself, and it was selected. Try it out yourself.

I'm not sure if I am clicking on right area, the dna ends are the sqaure/triangles on the strands right?

That's quite strange. I see the behavior on the current dev site, using both Chrome and Firefox.
Can you try Firefox to see if you get the same behavior?
I wonder if it's a Mac/PC thing, where your Mac is not detecting the same click events.

By the way, I don't see the pink to select it until the up-click, so it's definitely the mouseup event that is causing it.

I just tried it on Firefox and you were right, the ends still get clicked. It looks like it worked perfectly for chrome on a mac but not on Firefox. I'll fix this issue right now.

I just tested this and it looks like on a Mac with chrome, the mouse pointer down method was never accessed when I right-click. On Firefox for example, event.button is printed for both mouse/pointer up and down when I right-click. On the other hand on chrome, the event.button is only printed for mouse/pointer up.

(copied from a PR so we have a record in the issues)
I wonder if the thing that was supposed to be implemented by the left-click down works properly on a Mac. It would be good to meet and try to flesh this out to make sure that there's not some functionality disabled on Mac that should be there.

Sure, I'm free for the rest of the day so any time is convenient.


weave bits obscured by seas of infrastructure setup and shell scripts

The self-contained, start from scratch nature of the guides makes it quite difficult to see the weave bits. This is especially a problem for experienced users, who know perfectly well how to provision a bunch of machines for testing, and just want to skip to the 'interesting' stuff.
Not sure what to do about that. Perhaps have a very clear delineation in each guide between the infrastructure setup, and weave bits. Which might be tricky in some cases.

Could have beginner and advanced versions… downside is more guides to maintain.

On Jun 25, 2015, at 12:28 PM, Matthias Radestock<EMAIL_ADDRESS>wrote:
The self-contained, start from scratch nature of the guides makes it quite difficult to see the weave bits. This is especially a problem for experienced users, who know perfectly well how to provision a bunch of machines for testing, and just want to skip to the 'interesting' stuff.
Not sure what to do about that. Perhaps have a very clear delineation in each guide between the infrastructure setup, and weave bits. Which might be tricky in some cases.
—
Reply to this email directly or view it on GitHub https://github.com/weaveworks/guides/issues/6.

--
John Merrells
blog: http://johnmerrells.com
profile: http://linkedin.com/in/merrells
email<EMAIL_ADDRESS>twitter: @merrells
phone:<PHONE_NUMBER>

Eliminate anything to do with provisioning altogether. If someone doesn't know how to spin up their own instances to test out Weave then what exactly do they need the software for in the first place?
You could offer the 'off-the-shelf' versions of the guides too, but the primary guides should assume knowledge of how to provision basic linux boxes.

I am with Stellaverse- to a point. Provisioning in the form of Vagrantfiles and Ansible playbooks (etc) are totally fine because you get a line by line command history of what needs to be executed and how it talks.
My major gripe is the attempt to use Docker Machine to make things simpler/easier. Think of your target audience for this. We're early adopters by definition of using Weave and we're most likely using it to couple it with Swarm and by extension, Compose.
My coworker now has a Swarm + Weave cluster up but he did it using Machine so we're both totally confused as to how any of these pieces should talk to each other. This is very important information as we aren't going to use Machine in production, so we have this big knowledge gap that isn't covered by any documentation or explained in any meaningful way. "Use Docker-Machine" is not documentation.
I want to see diagrams of use cases with dependencies and commands. I want to see these because that's what it takes to design an infrastructure for production.

@rade a self-contained from-scratch type of guide let's the author guarantee that things will work for most folks and avoid having to handle tiny differences whether in the code or the text.

@ljsommer I believe most of the guides that we have cover what you are looking for, modulo the details of config tool type/flavour.

I want to see diagrams of use cases with dependencies and commands. I want to see these because that's what it takes to design an infrastructure for production.

Ok, I'll open a separate ticket for that, kept meaning to do this since a while.

@merrells I've been thinking of various different things in that respect... may be it's more about having beginner part where it's do A, B & C, and then there is an advanced explanation of how it works exactly part (which might even just hide in code comments in some cases, perhaps).

@Stellaverse I agree with what you are suggesting in general, however please note that the difficult bits are when Swarm/Mesos/Kubernetes come into play.

I have been thinking about this issue, about advanced users vs. beginners and am in the process of working on a plan.
But briefly, I think the guides should grouped into:

Tutorial/getting started guides, these would be what you have right now with simple examples to get up and running and I would remove the bits that are repetitive,i.e. the section on installing the virtualboxes and vagrant and put these into one section, where it can be linked to it if someone needs to know that.

Production/real world topics for more advanced users

Put the documentation on the website with a linked table of contents on the left-hand-side (like the way Docker and Vagrant have theirs) and make it more topic -based, rather than self-contained chapters.

Just for the record, one very general idea is to have well-maintained higher level guides and one-off  demos (mostly quite a bit more advanced, best effort maintenance).


Add marketing video to parents page

Context
Adds our marketing video to the parents page.
Screenshot of design (that can be seen by checking the figma)

Gif of implementation

Checked video responsiveness on a smaller screen. The gif doesn't correctly display the loRes font which should work in production. Adding fallback font can be done in separate PR.
I also added a commit that added lazy loading to the various <img> tags. This should result in the page loading these resources when required.
Testing and how to test
Set up your local development environment pointing at proxy.
This can be done by checking out this branch and running npm run dev and npm run proxy in separate command line tabs.
Then navigate to localhost:3000/parents
Scroll down slightly till you see the video.
I also tested minor responsiveness. One final note is that this should behave the same on all user types. Being logged in or not shouldn't change page.

@nwinter What do you think of this as a thumbnail?


Use Secret for st2.docker.conf  instead of ConfigMap

Here all these credentials are stored in ConfigMap
Doesn't it make more sense to use Secret since this contains credentials.

This is supported via st2.existingConfigSecret. You create a secret with your st2.conf contents, and then pass that secret name to the chart. It then gets mounted like this:
https://github.com/StackStorm/stackstorm-k8s/blob/fabbea9fb89bce6d093ad718def3e28fcfc47c5e/templates/_helpers.tpl#L167-L171
https://github.com/StackStorm/stackstorm-k8s/blob/fabbea9fb89bce6d093ad718def3e28fcfc47c5e/templates/_helpers.tpl#L177-L181
The value is described here:
https://github.com/StackStorm/stackstorm-k8s/blob/fabbea9fb89bce6d093ad718def3e28fcfc47c5e/values.yaml#L112-L116
Does that resolve your concerns?

Can we add this to docs please?

I'm using the existingConfig and now I have a secret called st2-secrets-conf that contains the DB / LDAP / RabbitMQ connection info and also a configMap called -st2-config that contains both st2.docker.conf that contains redis and rabbitMQ connection info in clear text.
imo there should be a way to force the installation to only accept credentials from secrets.


RFC #9: clarify that .const() can return a value-castable.

We have discussed this on the 2023-10-09 weekly meeting. The disposition was to merge.


Syncer Performs One Action at a Time

refac Syncer to have a more modular and user-friendly CLI
split Syncer up into component parts, one execution of the exe corresponds with only one action
stops and reports to user on first failure
reflect API changes on extension's end

Nice job :) Looks good


Error: There was an error building the project. Please read the logs for details

Bug description
After successfully build on the license step fails saying  "Error: There was an error building the project. Please read the logs for details."
How to reproduce

Configure the step

      # Build
      - name: Build project
        uses: game-ci/unity-builder@v3
        env:
          UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
        with:
          unityVersion: ${{ matrix.unityVersion }}
          targetPlatform: ${{ matrix.targetPlatform }}

Setup the secret variable UNITY_LICENSE
Launch the build action manually
Linux/Mac/Windws build will fail

Step configured
https://github.com/humbertodias/unity-mugen/blob/main/.github/workflows/release.yml
Expected behavior
Should pass through without any problem, because the activation was completed.
Changing to "/github/workspace/_activate-license~" directory.
/github/workspace/_activate-license~ /github/workspace
Requesting activation (personal license)
Activation complete.

Another weird behavior is related to WebGL version that works well

However, linux, windows and mac fails.
Additional details
Log
https://github.com/humbertodias/unity-mugen/actions/runs/6508708719/job/17680421661
Build succeeded

###########################
#       Build output      #
###########################

total 32M
drwxr-xr-x 4 root root 4.0K Oct 13 14:04 .
drwxr-xr-x 3 root root 4.0K Oct 13 13:50 ..
-rwxr-xr-x 1 1000 1000  15K Oct 13 14:04 StandaloneLinux64
drwxr-xr-x 3 root root 4.0K Oct 13 14:04 StandaloneLinux64_BurstDebugInformation_DoNotShip
drwxr-xr-x 7 root root 4.0K Oct 13 14:04 StandaloneLinux64_Data
-rwxr-xr-x 1 1000 1000  32M Oct 13 14:04 UnityPlayer.so
Changing to "/github/workspace/_activate-license~" directory.
/github/workspace/_activate-license~ /github/workspace
/github/workspace
Error: There was an error building the project. Please read the logs for details.
##[debug]Node Action run completed with exit code 1
##[debug]Finishing: Build project

Before v3, we didn't look for actual errors, we only considered Unity's exit code.
In your case, we can see that Unity build succeeded:

2023-10-13T14:04:41.5215929Z Build succeeded!

but have a look at this here:
2023-10-13T14:04:41.5195289Z ###########################
2023-10-13T14:04:41.5196270Z #      Build results      #
2023-10-13T14:04:41.5197178Z ###########################
2023-10-13T14:04:41.5197731Z
2023-10-13T14:04:41.5198080Z Duration: 00:08:38.1499180
2023-10-13T14:04:41.5198940Z Warnings: 94
2023-10-13T14:04:41.5199691Z Errors: 4
2023-10-13T14:04:41.5200452Z Size: 193454560 bytes
2023-10-13T14:04:41.5200956Z
2023-10-13T14:04:41.5206352Z
2023-10-13T14:04:41.5215929Z Build succeeded!

The pipeline failed due to 4 errors during the build. Yes Unity managed to create a build, but a few things went wrong.
Based on action implementation, this is handled here.
As you can see, if it finds Errors:  (and it did find it in your case), then the workflow is marked as failed even if there was a build produced.
v2 to v3 of the actions added this error checking in logs. There are active discussions about this possible breaking change and how we should actually improve this.
Here's some related issues
https://github.com/game-ci/unity-builder/issues/564
https://github.com/game-ci/unity-builder/issues/563
https://github.com/game-ci/unity-builder/issues/578
And there are others too
This is actually a proposal that will most likely help with that:
https://github.com/game-ci/unity-builder/pull/576

Searching in the logs you linked, I found this:
2023-10-13T13:56:43.7126070Z Failed to find a suitable OpenCL device for the GPU Lightmapper. Please change your lightmapper or install the latest graphics driver.
2023-10-13T13:56:43.7129356Z UnityEngine.StackTraceUtility:ExtractStackTrace () (at /home/bokken/build/output/unity/unity/Runtime/Export/Scripting/StackTrace.cs:37)
2023-10-13T13:56:43.7134730Z UnityEditor.BuildPipeline:BuildPlayerInternal (string[],string,string,UnityEditor.BuildTargetGroup,UnityEditor.BuildTarget,int,UnityEditor.BuildOptions,string[]) (at /home/bokken/build/output/unity/unity/Editor/Mono/BuildPipeline.bindings.cs:508)
2023-10-13T13:56:43.7140102Z UnityEditor.BuildPipeline:BuildPlayer (string[],string,string,UnityEditor.BuildTargetGroup,UnityEditor.BuildTarget,int,UnityEditor.BuildOptions,string[]) (at /home/bokken/build/output/unity/unity/Editor/Mono/BuildPipeline.bindings.cs:372)
2023-10-13T13:56:43.7144451Z UnityEditor.BuildPipeline:BuildPlayer (UnityEditor.BuildPlayerOptions) (at /home/bokken/build/output/unity/unity/Editor/Mono/BuildPipeline.bindings.cs:336)
2023-10-13T13:56:43.7147264Z UnityBuilderAction.Builder:BuildProject () (at Assets/Editor/Editor/UnityBuilderAction/Builder.cs:82)
2023-10-13T13:56:43.7148534Z
2023-10-13T13:56:43.7149516Z [/home/bokken/build/output/unity/unity/Editor/Mono/BuildPipeline.bindings.cs line 508]
2023-10-13T13:56:43.7150897Z
2023-10-13T13:56:43.7151340Z Falling back to CPU lightmapper.
2023-10-13T13:56:43.7153330Z UnityEngine.StackTraceUtility:ExtractStackTrace () (at /home/bokken/build/output/unity/unity/Runtime/Export/Scripting/StackTrace.cs:37)
2023-10-13T13:56:43.7157568Z UnityEditor.BuildPipeline:BuildPlayerInternal (string[],string,string,UnityEditor.BuildTargetGroup,UnityEditor.BuildTarget,int,UnityEditor.BuildOptions,string[]) (at /home/bokken/build/output/unity/unity/Editor/Mono/BuildPipeline.bindings.cs:508)
2023-10-13T13:56:43.7162990Z UnityEditor.BuildPipeline:BuildPlayer (string[],string,string,UnityEditor.BuildTargetGroup,UnityEditor.BuildTarget,int,UnityEditor.BuildOptions,string[]) (at /home/bokken/build/output/unity/unity/Editor/Mono/BuildPipeline.bindings.cs:372)
2023-10-13T13:56:43.7167411Z UnityEditor.BuildPipeline:BuildPlayer (UnityEditor.BuildPlayerOptions) (at /home/bokken/build/output/unity/unity/Editor/Mono/BuildPipeline.bindings.cs:336)
2023-10-13T13:56:43.7170240Z UnityBuilderAction.Builder:BuildProject () (at Assets/Editor/Editor/UnityBuilderAction/Builder.cs:82)

In other words, something went wrong trying to build with these lighting settings (if I understand correctly). Here's a very similar issue posted on our discord server.

v4 goes back to v2 style checks so this should be resolved once you upgrade


 Until I restart the IDE I cannot start debugging again, because otherwise it will complain that "Python debugger is already debugging another instance". My colleaques haven experiened this issue as well, and it seems to be a recent regression (last couple of weeks).
As I wrote this, I cannot click the "Create on GitHub" button because VSCode is seeming unresponsive. I resolved by restarting the IDE.
Steps to reproduce:

Use the below config for debugger
Run python -m debugpy --wait-for-client --listen 5678 /path/to/module.py
Run debugger
Either detach debugger or CTRL-C the process on command line

Diagnostic data

launch.json configuration

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [

        {
            "name": "Python: Remote Attach",
            "type": "python",
            "request": "attach",
            "connect": {
                "host": "localhost",
                "port": 5678
            },
            "pathMappings": [
                {
                    "localRoot": "${workspaceFolder}",
                    "remoteRoot": "."
                }
            ],
            "justMyCode": false
        }
    ]
}

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

XXX

Output for Python Debugger in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python Debugger)

XXX

Extension version: 2024.15.2024121301
VS Code version: Code 1.95.3 (f1a4fb101478ce6ec82fe9627c43efbf9e98c813, 2024-11-13T14:50:04.152Z)
OS version: Windows_NT x64 10.0.22631
Modes:
Remote OS version: Linux x64 4.18.0-372.32.1.el8_6.x86_64
Remote OS version: Linux x64 4.18.0-372.32.1.el8_6.x86_64
Remote OS version: Linux x64 4.18.0-372.32.1.el8_6.x86_64
Connection to 'SSH: zbs-carp2' could not be established  Canceled
Remote OS version: Linux x64 4.18.0-372.32.1.el8_6.x86_64

Python version (& distribution if applicable, e.g. Anaconda): 3.8.19
Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Conda

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i9-11950H @ 2.60GHz (16 x 2611)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabledwebnn: disabled_off

Load (avg)
undefined

Memory (System)
63.73GB (37.47GB free)

Process Argv
--folder-uri vscode-remote://ssh-remote%2Bzbs-carp2/physical/gpfs/carp2-home/car_home02/data_files/jcs/zsilversmith/dev/git/eis3 --crash-reporter-id 2a67a766-b9ca-442f-87e6-12fdf4c1e37f

Screen Reader
no

VM
0%

Item
Value

Remote
SSH: zbs-carp2

OS
Linux x64 4.18.0-372.32.1.el8_6.x86_64

CPUs
AMD EPYC 7763 64-Core Processor (128 x 0)

Memory (System)
2014.91GB (1217.89GB free)

VM
0%

Item
Value

Remote
SSH: zbs-carp2

OS
Linux x64 4.18.0-372.32.1.el8_6.x86_64

CPUs
AMD EPYC 7763 64-Core Processor (128 x 0)

Memory (System)
2014.91GB (1217.89GB free)

VM
0%

Item
Value

Remote
SSH: zbs-carp2

OS
Linux x64 4.18.0-372.32.1.el8_6.x86_64

CPUs
AMD EPYC 7763 64-Core Processor (128 x 0)

Memory (System)
2014.91GB (1217.89GB free)

VM
0%

Connection to 'SSH: zbs-carp2' could not be established  Canceled

Item
Value

Remote
SSH: zbs-carp2

OS
Linux x64 4.18.0-372.32.1.el8_6.x86_64

CPUs
AMD EPYC 7763 64-Core Processor (128 x 0)

Memory (System)
2014.91GB (1217.89GB free)

VM
0%

A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
pythonnoceb:30805159
pythonmypyd1:30879173
2e7ec940:31000449
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
dvdeprecation:31068756
dwnewjupyter:31046869
newcmakeconfigv2:31071590
nativerepl2:31139839
pythonrstrctxt:31112756
nativeloc1:31192215
cf971741:31144450
iacca1:31171482
notype1:31157159
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
6074i472:31201624

@zbs In this case is the debugger process (i.e., python -m debugpy) terminated? or is that also blocked.
Moving this to debugpy to investigate. Basically, if the process is terminated, we do an atexit registration that should let IDE know that the debugger is terminated. We need to make sure that the termination message is being sent to the IDE.
If debugpy is terminating correctly after sending the message, then this issue is in the DAP Client, and we should move this issue to VS Code core.


Angular Version Update!

Hi guys, thanks for your effort! My question is why there is no visible work on a Carbon version with an up-to-date Angular? The currently used Angular 8 is no longer under support and even Angular 9 reaches end of life on august this year. There are some major performance improvements on Angular 9+ (especially compile time).
https://angular.io/guide/releases#support-policy-and-schedule

Hi guys, thanks for your effort! My question is why there is no visible work on a Carbon version with an up-to-date Angular? The currently used Angular 8 is no longer under support and even Angular 9 reaches end of life on august this year. There are some major performance improvements on Angular 9+ (especially compile time).
https://angular.io/guide/releases#support-policy-and-schedule

I wouldn't have my hopes up, the Angular team for Carbon Components is ridiculous. AOT vendor.js bundles are still in the tens of MBs size

My question is why there is no visible work on a Carbon version with an up-to-date Angular?

Hey @seriouz, thanks for the question. I'd be curious what's preventing you from adopting newer versions of Angular? We do support the latest version (11), and you can take advantage of all the benefits you list in your app. We do develop on an older version, but we do that to provide the greatest level of version compatibility - there should be no effect on your application.

I wouldn't have my hopes up, the Angular team for Carbon Components is ridiculous.

Hi @lepidotteri I would like to make sure you have read and understood our code of conduct. If you have an issue with the components please don't hesitate to raise an issue and we'll work with you to resolve it, however attacking the core team will not be tolerated - we are humans too.
Now given your following comment:

AOT vendor.js bundles are still in the tens of MBs size

This absolutely should not be the case. Please make sure you're on a recent version of Angular (10/11) and the latest version of carbon-components-angular, you can drop the @carbon/icons-angular dependency and replace it with IconModule and @carbon/icons. If you still have issues with bundle sizes make sure you're taking advantage of per-component modules (ex. import { ButtonModule } from "carbon-components-angular/button";) and lazy-loading.
If you have further specific issues with bundle sizes please open an issue with as much detail as you can (a minimal reproduction would be ideal).

My question is why there is no visible work on a Carbon version with an up-to-date Angular?

Hey @seriouz, thanks for the question. I'd be curious what's preventing you from adopting newer versions of Angular? We do support the latest version (11), and you can take advantage of all the benefits you list in your app. We do develop on an older version, but we do that to provide the greatest level of version compatibility - there should be no effect on your application.

Sorry i haven't seen it anywhere that gave me a hint that the newer Angular version are supported. Did i miss it, or is it nowhere recorded?

My question is why there is no visible work on a Carbon version with an up-to-date Angular?

Hey @seriouz, thanks for the question. I'd be curious what's preventing you from adopting newer versions of Angular? We do support the latest version (11), and you can take advantage of all the benefits you list in your app. We do develop on an older version, but we do that to provide the greatest level of version compatibility - there should be no effect on your application.

Sorry i haven't seen it anywhere that gave me a hint that the newer Angular version are supported. Did i miss it, or is it nowhere documented?

We declare our version support via peerDependencies here: https://github.com/IBM/carbon-components-angular/blob/master/package.json#L62-L64
Definitly open to suggestions as to how we can make our version support more obvious 👍

I'm going to assume this issue has been resolved.

@cal-smith Thank you!


Table of contents link does not work when headers contain special characters

Headers in markdown have an anchor which is used for links, format is '#' then the header text converted to lower-case, spaces replaced with hyphens, and special characters removed.
The Table of Contents in MdUtils has a link to the header by converting to lower-case and replacing spaces with hyphens, but does not remove special characters.  This means that some of the links in the ToC will not work.
For example I have a header level 2, with text "Unnamed: 41", when I create a ToC the link to this is #unnamed:-41, but should be #unnamed-41, i.e. without the colon. Clicking on the link does not take me to the header section of the document as it should do..

Thanks for reporting the bug I will take a look as soon as I can.


Add ref tests for 3dtransforms

Fail analysis: Actual pic is different with expected pic when crosswalk
render pics. For example: css-transform-3d-rotate3d-X-negative.html,
there is a red border outside black border, but the ref has not.
Impacted tests(approved): new 0, update 40, delete 0
Unit test platform: Crosswalk Project for Android 15.44.361.0
Unit test result summary: pass 38, fail 29, block 0

Please double whether we can improve these tests to avoid fractional pixel as we talked.


build docker image

Following the issue #20 I've built docker image for se-scraper.
Build docker image
docker build -t se-scraper .
Ready-to-use image is available at https://hub.docker.com/r/slotix/se-scraper
Run se-scraper.
docker  run -it -p 3000:3000 slotix/se-scraper
Curl dockerized se-scraper service.
curl -XPOST http://<IP_ADDRESS>:3000 -H 'Content-Type: application/json' \
-d '{
    "user_agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Safari/537.36",
    "random_user_agent":true,
    "sleep_range":"",
"search_engine":"baidu",
    "debug":true,
    "verbose":true,
    "keywords":[ "cat",  "mouse" ],
    "keyword_file":"",
    "num_pages":1,
    "headless":true,
    "chrome_flags":[ ],
    "output_file":"examples/results/baidu.json",
    "block_assets":false,
    "custom_func":"",
    "proxy":"",
    "proxy_file":"",
    "test_evasion":false,
    "apply_evasion_techniques":true,
    "log_ip_address":false,
    "log_http_headers":false,
    "puppeteer_cluster_config":{
        "timeout":600000,
        "monitor":false,
        "concurrency":1,
        "maxConcurrency":1
    }
}'

can you provide also the Dockerfile please

Thank you for adding support of docker in master branch. Closing this pull request...


Allowing setting and updating nests within iterables

Actually solves problem from #21 in addition to #28.

piggy backed a little here and allow passing a custom dict class for the underlying _values, such that one could use an OrderedDict, for example

@gmr and change to get this and #30 merged and released? I want to use this in a project and I need both fixes.

Can you resolve the merge conflict so I can more easily merge?


File size, download time & reading time

What do you need?
https://github.com/AusDTO/gov-au-content-guide/issues/110

Now being tracked in Trello


feat: Implement the from_utf16_lossy(...) API

This issue for tracking the implementation of the from_utf16_lossy(...) method that exists on String.

String has only one method for this, but shouldn't it be three methods? UTF-16 in native, little and big endian.

Great point! What do you think about supporting the following 6 APIs:

from_utf16(...) (native endianness)
from_utf16_lossy(...) (native endianness)
from_utf16_be(...)
from_utf16_be_lossy(...)
from_utf16_le(...)
from_utf16_le_lossy(...)

Side note: looks like @CAD97 has a PR to introduce this to the stdlib too! https://github.com/rust-lang/rust/pull/95967

Also cc @NobodyXu, any thoughts here?

Also cc @NobodyXu, any thoughts here?

I'm not that familiar with utf16 APIs, but this looks alright to me.


Change neuralnet setConfig to throw

Change Neuralnet::setConfig to throw instead of return status
This PR also patches:

Minor typos
Delete unused function
Fix neuralnet ctor delegation order

Self evaluation:

Build test: [X]Passed [ ]Failed [ ]Skipped
Run test: [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: Jihoon Lee<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.4.20191203. Thank you for submitting PR #372. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnsuite.mooo.com/.

:octocat: cibot: @zhoonit, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/372-202007281801250.97635006904602-08b16b789aa6419e051cdf7e72fa8bb0bd319ddd/.

I think you need to modify applications to take throw as well.

I think you need to modify applications to take throw as well.

I've changed accordingly, PTAL


When will there be a new nuget release of CLRMD?

CLRMD is a great library and we're actively using it (https://github.com/Dynatrace/superdump).
The last (and only) release of CLRMD was in October 2015 (0.8.31-beta, which is also on nuget.org). Clearly, some work has been done on the library since then. Are there plans for a new release? Should we build CLRMD ourself to get the latest and greatest bits?

+1, find this cool library and want to know when is it officially released so we could reference it in production.

I am working on this now (but can't promise any ETA).
ClrMD fell into a window of time before we really figured out the open source thing.  This project was one of the first to be open sourced and didn't get update to work like other projects (such as coreclr/corefx).  As such it's not up to date with our current workflow, which is why it's been so long since release.

Thanks @leculver! It's great to hear that something is happening at least.

I know it's been three weeks, but this hasn't been forgotten or dropped.  Work has been scheduled and hopefully "Soon (TM)" we should have the right process in place.  Once all the work is done to build, sign, and package things we can ship as frequently as needed.

@leculver No worries. Keep up the good work! +1 for this great library!

@leculver the WPFDXInterop project seems to have similar problems, being an old repository and getting no attention anymore. I know that repository is a totally different subject, sorry for cross-posting but any idea how to get attention back to it again, or if that's even possible?

@weltkante Sorry, this is outside my team's area so I'm not sure I can promise a response here.  I've asked around but the person to find out from is on vacation.  I'll reply back if I find something I can share (when they get back).

@discostu105 @chuanboz I have published a new release of ClrMD to NuGet.  I haven't decided what cadence to ship at in the future, but it now only takes me a half hour to release changes (instead of the week it took before).  I should be able to get fixes out faster now.

@zone117x Would you mind pulling down the Microsoft.Diagnostics.Runtime.Latest package now that we have our act together?  =)
I worry that someone will get confused, and it's now out of date.
Thank you!

Nuget is having a server error when trying to delist the package. Will try it again later 👍


Updated README community section

Description
Updated README community section and added the required text.
This PR fixes
#161
Notes for Reviewers
I also added the link of the Community member form with this link provided in the issues section.
Signed commits

[x] Yes, I signed my commits.

Hi @Evavic44 ,
some of the checks were not successful, to contribute to this project, you must agree to the Developer Certificate of Origin (DCO) for each commit you make, that is you would have to Sign-off on Commits ; using
git commit --signoff -m'<commit subject>'

git commit --signoff -m''

Oh, sorry about that. Will sign it this time

Thank you for picking this issue @Evavic44.
Please remove the google drive link from "Community drive" and leave it as just text.
Include a full stop (.)at the end of the text.

I've updated it with the requested changes. 👍🏾

git commit --signoff -m''

Oh, sorry about that. Will sign it this time
I tried the above command but it still couldn't sign off the commits. Is there something I'm doing wrong?

Try using this exact command
git commit --signoff -m'Updated README community section '

git commit --signoff -m''

Oh, sorry about that. Will sign it this time
I tried the above command but it still couldn't sign off the commits. Is there something I'm doing wrong?

Try using this exact command
git commit --signoff -m'Updated README community section '

Done

git commit --signoff -m''

Oh, sorry about that. Will sign it this time
I tried the above command but it still couldn't sign off the commits. Is there something I'm doing wrong?

Try using this exact command
git commit --signoff -m'Updated README community section '

Done

Please Remove the Google drive link from the "Community Drive", we do not need it again in the text.

I used the command provided and pushed it. Here's a preview. Is this the sign-off you're asking about. Also, I've already removed the google drive link. Here

Run these commands in the terminal. https://github.com/layer5io/meshery-operator/pull/162/checks?check_run_id=2618292683

Run these commands in the terminal. https://github.com/layer5io/meshery-operator/pull/162/checks?check_run_id=2618292683

I did and this is what I got.

So sorry for wasting your time, would it be better to close this issue, so I can create a new PR but this time signing the commits? Or is there a better way to solve this?


Fix instructions for adding synonyms

Corrects the name of the button to fix.
Delivers https://www.pivotaltracker.com/story/show/61089358
Manual test

Go to any Name page (e.g. http://localhost:3000/name/show_name/800
Click Change Synonyms
In the "Names" box, type at least one Name that doesn't exist in MO, e.g., Uttercompletegarbage
Submit Changes
Expected Result: page is redisplayed with flash:

"Click Submit Changes .... If you want to correct any names ... click Submit Changes ...." (boldface added).

This probably doesn't need review; its a one-line change to en.txt.
(I was looking for super-easy tickets because my head's swimming trying to understand our combined geocode, client side js, server side js, bootstrap, etc. )

This probably doesn't need review; its a one-line change to en.txt.
(I was looking for super-easy tickets because my head's swimming trying to understand our combined geocode, client side js, server side js, bootstrap, etc. )


[1.x] ec2-net-utils probes for nonexistent local-ipv4s key in IPv6-only subnets

Instance is Amazon Linux 2.  Secondary ENI is in an IPv6-only subnet and attached as a secondary ENI. The following is logged:
Mar 24 22:01:27 ip-10-0-0-244.us-west-2.compute.internal ec2net[13788]: [plug_interface] eth1 plugged
Mar 24 22:01:27 ip-10-0-0-244.us-west-2.compute.internal ec2net[13789]: [rewrite_primary] Rewriting configs for eth1
Mar 24 22:01:27 ip-10-0-0-244.us-west-2.compute.internal ec2net[13793]: [activate_primary] Activating eth1
Mar 24 22:01:28 ip-10-0-0-244.us-west-2.compute.internal kernel: ena 0000:00:06.0 eth1: Local page cache is disabled for less than 16 channels
Mar 24 22:01:28 ip-10-0-0-244.us-west-2.compute.internal kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Mar 24 22:01:28 ip-10-0-0-244.us-west-2.compute.internal dhclient[13811]: DHCPREQUEST on eth1 to <IP_ADDRESS> port 67 (xid=0x1dda62f9)
Mar 24 22:01:36 ip-10-0-0-244.us-west-2.compute.internal dhclient[13811]: DHCPREQUEST on eth1 to <IP_ADDRESS> port 67 (xid=0x1dda62f9)
Mar 24 22:01:36 ip-10-0-0-244.us-west-2.compute.internal dhclient[13811]: DHCPNAK from <IP_ADDRESS> (xid=0x1dda62f9)
Mar 24 22:01:36 ip-10-0-0-244.us-west-2.compute.internal ec2net[13848]: [remove_aliases] Removing aliases of eth1
Mar 24 22:01:36 ip-10-0-0-244.us-west-2.compute.internal ec2net[13850]: [remove_rules] Removing rules for eth1
Mar 24 22:01:36 ip-10-0-0-244.us-west-2.compute.internal dhclient[13811]: DHCPDISCOVER on eth1 to <IP_ADDRESS> port 67 interval 7 (xid=0x329a8de1)
Mar 24 22:01:36 ip-10-0-0-244.us-west-2.compute.internal dhclient[13811]: DHCPREQUEST on eth1 to <IP_ADDRESS> port 67 (xid=0x329a8de1)
Mar 24 22:01:36 ip-10-0-0-244.us-west-2.compute.internal dhclient[13811]: DHCPOFFER from <IP_ADDRESS>
Mar 24 22:01:36 ip-10-0-0-244.us-west-2.compute.internal dhclient[13811]: DHCPACK from <IP_ADDRESS> (xid=0x329a8de1)
Mar 24 22:01:37 ip-10-0-0-244.us-west-2.compute.internal ec2net[13914]: [get_meta] Querying IMDS for meta-data/network/interfaces/macs/02:c0:eb:86:d0:cf/local-ipv4s
Mar 24 22:01:37 ip-10-0-0-244.us-west-2.compute.internal ec2net[13915]: [get_meta] Getting token for IMDSv2.
Mar 24 22:01:37 ip-10-0-0-244.us-west-2.compute.internal ec2net[13918]: [get_meta] Trying to get http://<IP_ADDRESS>/latest/meta-data/network/interfaces/macs/02:c0:eb:86:d0:cf/local-ipv4s
Mar 24 22:01:37 ip-10-0-0-244.us-west-2.compute.internal ec2net[13922]: [get_meta] Trying to get http://<IP_ADDRESS>/latest/meta-data/network/interfaces/macs/02:c0:eb:86:d0:cf/local-ipv4s
Mar 24 22:01:38 ip-10-0-0-244.us-west-2.compute.internal ec2net[13926]: [get_meta] Trying to get http://<IP_ADDRESS>/latest/meta-data/network/interfaces/macs/02:c0:eb:86:d0:cf/local-ipv4s
Mar 24 22:01:38 ip-10-0-0-244.us-west-2.compute.internal ec2net[13930]: [get_meta] Trying to get http://<IP_ADDRESS>/latest/meta-data/network/interfaces/macs/02:c0:eb:86:d0:cf/local-ipv4s
Mar 24 22:01:39 ip-10-0-0-244.us-west-2.compute.internal ec2net[13934]: [get_meta] Trying to get http://<IP_ADDRESS>/latest/meta-data/network/interfaces/macs/02:c0:eb:86:d0:cf/local-ipv4s
Mar 24 22:01:39 ip-10-0-0-244.us-west-2.compute.internal ec2net[13938]: [get_meta] Trying to get http://<IP_ADDRESS>/latest/meta-data/network/interfaces/macs/02:c0:eb:86:d0:cf/local-ipv4s
Mar 24 22:01:40 ip-10-0-0-244.us-west-2.compute.internal ec2net[13942]: [get_meta] Trying to get http://<IP_ADDRESS>/latest/meta-data/network/interfaces/macs/02:c0:eb:86:d0:cf/local-ipv4s
Mar 24 22:01:40 ip-10-0-0-244.us-west-2.compute.internal ec2net[13946]: [get_meta] Trying to get http://<IP_ADDRESS>/latest/meta-data/network/interfaces/macs/02:c0:eb:86:d0:cf/local-ipv4s
Mar 24 22:01:41 ip-10-0-0-244.us-west-2.compute.internal ec2net[13950]: [get_meta] Trying to get http://<IP_ADDRESS>/latest/meta-data/network/interfaces/macs/02:c0:eb:86:d0:cf/local-ipv4s
Mar 24 22:01:41 ip-10-0-0-244.us-west-2.compute.internal ec2net[13954]: [get_meta] Trying to get http://<IP_ADDRESS>/latest/meta-data/network/interfaces/macs/02:c0:eb:86:d0:cf/local-ipv4s
...

The interface is still configured with the expected link-local IPv4 and global IPv6 addresses, but the extra noise in the logs is unnecessary and unhelpful.

Fix merged. Will include this in an upcoming 1.6.2 release.


[DRAFT]: Test GitHub Release Publishing in Workflows

:warning: DO NOT MERGE :warning:
Currently, release publishing is failing in GitHub workflows with the following error:
publishing draft release
HTTP 422: Validation Failed (https://api.github.com/repos/safe-global/safe-deployments/releases/165840580)
pre_receive Repository rule violations found
Cannot create ref due to create name restrictions.
Published releases must have a valid tag

In order to more quickly debug the issue and try to find solutions to the problem, I created this Draft PR that will run workflows that try to publish the draft release.

Fixed: https://github.com/safe-global/safe-deployments/actions/runs/9975305349/job/27564711644


Enable using class exception's __doc__ as message

Let the user use a class exception's __doc__ as the message. For instance:
>>> class IncorrectSomethingError(Exception):
...     """Something should be smaller than 10."""

>>> check_if(
...     something < 10,
...     handle_with=IncorrectSomethingError,
...     message=ExceptionDoc()

For this, we need to defined ExceptionDoc (or something like this). Enough to use an empty class:
>>> class ExceptionDoc:
...     pass

and then, in code, when a message is created, enough to check
if isinstance(message, ExceptionDoc):
    message=handle_with.__doc__

Such an opportunity will unlikely be used with built-in errors, but can be very useful in the case of custom exceptions.

Alternatively, instead of rather unnatural ExceptionDoc(), maybe we can define a simple function
``python
def doc(exception):
return exception.doc
I think it will be more natural to do something like that:
```python
>>> check_if(
...     something < 10,
...     handle_with=IncorrectSomethingError,
...     message=doc(IncorrectSomethingError)

than either of these two:
>>> check_if(
...     something < 10,
...     handle_with=IncorrectSomethingError,
...     message=ExceptionDoc()

or
>>> check_if(
...     something < 10,
...     handle_with=IncorrectSomethingError,
...     message=IncorrectSomethingError.__doc__


Binary cache

Is there any way to upload dependencies derivations to binary cache using cachix or nix copy --to file:///tmp/cache ...?
In other words, is there any way to reference crate dependencies derivations inside nix, not just the workspace.crate_name?

Figured out that I can use inputDerivation to reference deps, so to upload crate deps build by cargo2nix the following should work (i use nix flakes):
nix copy --to http://my-store?secret-key=/cache.key .#my-crate.inputDerivation


[SIEMINT-42] [Release] DDS: Mimecast: Crawler Integration v1.0.0

What does this PR do?
This is a initial release PR of Mimecast integration including all the required assets.
Additional Notes

Crawler code for this integration has been committed in its respective repo
Pipeline and Facet group created for this integration are available in our sandbox and would be shared separately with the required teams.
Samples for the pipeline review would also be shared separately with the required teams.
OOTB detection rules JSON would be shared separately with the required teams as a part of separate repository.
Since during the standard attribute remapping we are not preserving the source attributes as per suggested best practices, it would result in filters using these standard attributes populating the values of other integrations as well as per current Datadog behaviour

Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Changelog entries must be created for modifications to shipped code
[ ] Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
[ ] If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

Thanks, created DOCS-8355 to review

Overall the PR is looking quite good for me, great job on this integration. I have added 2 comments, once reviewed we can push this PR in staging for the final check!

I am moving this integration in our test env. I will test it soon and keep you posted later today

@thibaultkrebs are test in our test env ok? can we move forward with this integration today?

@djova I was off for one week. there is an issue with another asset that is blocking me from testing it in staging, I will check internally if we can unblock this PR as soon as possible.

@bhargavnariyanicrest this PR needs to be rebased. once you've done that feel free to remove the assets/no-deploy label

@ravindrasojitra-crest this PR needs to be rebased. once you've done that feel free to remove the assets/no-deploy label

Maybe we don't have rights to remove labels, can someone help with this please?

I have just removed the no deploy label. I will also be able to test this in our test environment later today 👍

@savandalasaniya-crest please fix the failing CI errors


OCPBUGS-21228: disable http2 on webhooks

/retest

/override ci/prow/ci-index-upgrade-bundle

/label backport-risk-assessed

/label cherry-pick-approved

/lgtm

/override ci/prow/ci-index-upgrade-bundle


Update schema on schemastore.org

What happened?
Intellij pulls the schema from schemastore.org in order to provide code completion and assistance. The current schema there doesn't recognize version v2beta1 and the IDE thinks everything is wrong.
What did you expect to happen instead?
The schema to recognize v2beta1 and either provide no assistance or updated to reflect the v2beta1 schema.

/kind bug

The current schema is added for v2beta1 only

Looking a little closer, I think maybe the schema definition might be off ... or the documentation.
Example in the documentation:

From IDE:

Example in the documentation:

From IDE:

Documentation:

From IDE:

Documentation:

From IDE:

We have valid schema plus schema generator already in docs/hack and schema folder. I'll make sure we generate the newest version and submit to schemastore. Thanks for the contribution in hack/ on the root level but it's not producing the correct output. I'll make sure we get the official schema updated. @FabianKramm for reference not to accept any PRs on this topic since we already have a working script to produce a valid schema.

@LukasGentele @tukobadnyanoba It appears that the devspace-schema.json isn't a fully valid representation of the devspace.yaml schema. For example the name variable is required on vars and it doesn't recognize strings as a valid value. It seems that the generator isn't able to pick up on all the nuances built into the UnmarshalYAML methods.
Is there a valid schema somewhere that can be used for development?

@dolfelt not yet, but we will update that very shortly. The following tasks are left todo:

Allow string or object as value for vars, pipelines and commands (and all the others where we have an UnmarshalYAML method)
Remove the ./hack/genjsonschema implementation in favor of /docs/hack/config/schemas/ implementation
Remove the json spec description annotations in the devspace latest version
Update the jsonschema in the schemastore.org


Measuring Unit costs

I think it's necessary to point out to the reader of this page that Unit Economics is a derivative of Activity Based Costing methodology. What you are proposing on the page is only capturing Batch or online activity, what about manual processes and steps outside of the cloud that are critical for calculating units that are critical for business rather than just Cloud related?
Most people who use this page, take it for face value and do not spend time to dwell deeper into Unit Economics and try to calculate values that are not complete and hence provide wrong results. That's the danger of providing half-baked information.

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

ID: 72cdb50f-bad9-40b8-c40c-908d7446a0d1
Version Independent ID: 8827d458-626a-3573-e5f1-53bf094c6ea6
Content: Measuring unit costs - Microsoft Cost Management
Content Source: articles/cost-management-billing/finops/capabilities-unit-costs.md
Service: cost-management-billing
Sub-service: finops
GitHub Login: @bandersmsft
Microsoft Alias: banders

@sriram08854
Thanks for your feedback! We will investigate and update as appropriate.

@MonikaReddy-MSFT I sent email to the team about this. We need their input to resolve.

@sriram08854 -  Thanks for bringing this to our attention.
I'm going to assign this to the document author so they can review and update accordingly.

https://github.com/MicrosoftDocs/azure-docs-pr/pull/256184

@sriram08854 Thanks for your feedback. After speaking with my engineering team, we updated the article to address your feedback with the following addition:

The ultimate goal of unit economics, as a derivative of activity-based costing methodology, is to factor in the whole picture of your business's cost. This article focuses on capturing how you can factor your Microsoft Cloud costs into those efforts. As your FinOps practice matures, consider the manual processes and steps outside of the cloud that might be important for calculating units that are critical for your business to track the most accurate cost per unit.

#please-close

Appreciate your follow-up Bill.
On Wed, Oct 25, 2023 at 6:21 PM Bill Anderson @.***>
wrote:

@sriram08854 https://github.com/sriram08854 Thanks for your feedback.
After speaking with my engineering team, we updated the article to address
your feedback with the following addition:
The ultimate goal of unit economics, as a derivative of activity-based
costing methodology, is to factor in the whole picture of your business's
cost. This article focuses on capturing how you can factor your Microsoft
Cloud costs into those efforts. As your FinOps practice matures, consider
the manual processes and steps outside of the cloud that might be important
for calculating units that are critical for your business to track the most
accurate cost per unit.
#please-close
—
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/115360#issuecomment-1780137433,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFZ4NHAKHOYRCU45VUZYFCTYBGGHFAVCNFSM6AAAAAA5LZYY6KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBQGEZTONBTGM
.
You are receiving this because you were mentioned.Message ID:
@.***>


Add link:fix command

Runing npm run lint:fix would now easily repair the errors
that are shown by npm run lint.
Signed-off-by: fenn-cs<EMAIL_ADDRESS>

Thanks @jasonaowen


Remove broken republish_withdrawn_document script

This script relies on ManualsPublisher#document_services which is broken in a couple of different ways:

The AbstractDocumentServiceRegistry class was removed in this commit.
The ManualsPublisher#observer_registry method was removed in this commit.

Writing about this script in this PR comment, @h-lame said:

Suspect this could be got rid of and we re-write as/when requested via a support ticket.

So I think it's safe to remove the script. It's then sensible to remove the ManualsPublisher module which at that point is unused as well as broken.

@h-lame: Yes. Thanks - I've just been fixing it. I've also added a new commit to remove another method.


SVG has an invalid size

Hi,
Firstable, thanks for this awesome lib!
I used it on different kind of svg files and some doesn't been parse.
This svg example:
<? xml version = "1.0" encoding = "UTF-8" standalone = "no"?>
<svg>
     <circle cx = "100" cy = "100" r = "100" />
</svg>

will interprated by some other svg engine like this:
<? xml version = "1.0" encoding = "UTF-8" standalone = "no"?>
<svg
    xmlns = "http://www.w3.org/2000/svg"
    viewBox = "0 0 200 200">
    <circle cx = "100" cy = "100" r = "100" />
</svg>

In other word, several engine add a default xmlns if it's empty and define a viewbox adjust on the content if the viewbox isn't explicilty defined.
I'm ok that svg is malformed like you say here https://github.com/RazrFalcon/resvg/issues/192, but can you consider an ** ugly ** option for integrate it (or converting)?
If this engine is integrated on an app design for "non dev", malformed svg is a difficult speech especially if svg was produce by an application.

<? xml is malformed. The space there is not allowed.
xmlns is mandatory. Try opening you file in the browser. It will not be rendered.
resvg doesn't support size autodetection, so an SVG without viewBox or width/height is still malformed.

Yes, some apps can ignore xmlns, but this against the standard.

Ok, tks for the quick reply.

a mistake, ignore it
ok, i will find a solution for my usage and understand your choise
is it a possible development ? (Sure, seems a very complex algo)

Yes, it would be done eventually: #40


Multiple document roots AND install from makefile

I want to use this one VM to run a few separate Drupal installs (not multisite)
I believe I can set up multiple document roots by adding to these vars in config.yml
vagrant_synced_folders
apache_vhosts
mysql_databases
mysql_users

I would like each new site to be installed using the make file, however the makefile seems to be configured with variables starting  drupal_*
Is it limitation of the project (deliberate or otherwise) that only the first site can be installed automatically?
I'm not complaining btw ;-) just wondering if I've missed something. I guess I can change config.yml to create the roots then vagrant ssh in run some commands myself, it's just that the rest of it is so slick I wanted to check if there is a better way.
I'd like to point out that I definitely don't have a bug or anything. I am already using this successfully with all the recommended versions of dependencies.
Thanks

It's a limitation—deliberate for now, but hopefully fixed someday to allow multiple sites to be installed via make files (or any other method of your choosing).
The primary use cases currently allows for multiple sites to be managed independently—but you have to do some manual manipulation of the config.yml file for each site (see Deployment Strategies section in the Docs). However, only one site can be installed via makefile on initial provision.
One pattern I've seen used in certain places is multiple copies of Drupal VM—one for each site/project. That way it can be tuned for each project individually, and as long as you have a unique IP address and machine name for each, they won't conflict and can be brought up and down whenever you like.
For now, I'm closing this issue. I'm hoping to solve this problem (support as many sites with whatever install methods out of the box) by 3.x, but we'll see :)

Thanks for the reply, that's cool. And I guessed as much - just wanted to check. Thanks for project :)


Key events not captured when page content loses focus then regains it

If I click the location bar, then the webpage again, key events seem to not be captured.  The same goes for if I use a keyboard shortcut to launch Developer Tools and turn it off again.  The key events get captured again if I switch to a different tab and back, or if I reload the page.  Can anyone reproduce this?
I'm on a Mac, using Chrome 13.0.782.218

I am also having this issue on a mac, in Chrome / Safari / FF. Sometimes after switching with ⌘+Tab to other application and back, the ⌘ modifier remains set.

Same issue here on Chrome with OS+X and pressing Cmd+L to go to the location bar.

Hey all, i tried a few scenarios already, but lemme know if this fix doesn't solve your problem.

Hey Lowe, tried your fix, seems to work OK. Thanks!

@lowe, it didn't help in my case. When I switch to other window and back by QUICKLY hitting ⌘+tab, the command modifier being reset as expected. But if I hold down Command key before switching to the other window for a little longer (for about a second), then after I switch back Command modifier remains set.
I checked that resetModifiers() being called in both cases.


Support for SHADEGRP Command

When the plugin talks to Homeworks QS system with Lutron shade rollers, it receives commands containing "SHADEGRP" which is currently not recognized. It seems the open/close still works (I am controlling one shade at a time, never used shade group, but still receives this command), but probably we are missing other information like status and the ability to set shades to specific locations. This command can be found in the Lutron Integration Protocol on page 43 (2019-11 rev ac 14). Here's an example of the logs from my Indigo setup:
   Lutron RRA2/Caséta Debug       Family Room Shade 2: actionControlDimmerRelay sending: '#OUTPUT,124,1,100' to gateway<PHONE_NUMBER>
   Lutron RRA2/Caséta Debug       Lutron IP Gateway: Sending command: '#OUTPUT,124,1,100'
   Lutron RRA2/Caséta Threaddebug Lutron IP Gateway: 50 characters read:
QNET> ~SHADEGRP,123,1,100.00
~SHADEGRP,123,32,0,1
   Lutron RRA2/Caséta Threaddebug Lutron IP Gateway: self.buffer = 'QNET> ~SHADEGRP,123,1,100.00
~SHADEGRP,123,32,0,1'
   Lutron RRA2/Caséta Threaddebug Lutron IP Gateway: msg = 'QNET> ~SHADEGRP,123,1,100.00
'
   Lutron RRA2/Caséta Threaddebug Lutron IP Gateway: self.buffer = '~SHADEGRP,123,32,0,1'
   Lutron RRA2/Caséta Threaddebug Received command: QNET> ~SHADEGRP,123,1,100.00 from Gateway<PHONE_NUMBER>
   Lutron RRA2/Caséta Debug       Gateway<PHONE_NUMBER> Unrecognized command: QNET> ~SHADEGRP,123,1,100.00
   Lutron RRA2/Caséta Threaddebug Lutron IP Gateway: 50 characters read:
3094
~OUTPUT,124,1,100.00
~OUTPUT,124,29,6
~OUT
   Lutron RRA2/Caséta Threaddebug Lutron IP Gateway: self.buffer = '~SHADEGRP,123,32,0,13094
~OUTPUT,124,1,100.00
~OUTPUT,124,29,6
~OUT'
   Lutron RRA2/Caséta Threaddebug Lutron IP Gateway: msg = '~SHADEGRP,123,32,0,13094
'
   Lutron RRA2/Caséta Threaddebug Lutron IP Gateway: self.buffer = '~OUTPUT,124,1,100.00
~OUTPUT,124,29,6
~OUT'
   Lutron RRA2/Caséta Threaddebug Received command: ~SHADEGRP,123,32,0,13094 from Gateway<PHONE_NUMBER>
   Lutron RRA2/Caséta Debug       Gateway<PHONE_NUMBER> Unrecognized command: ~SHADEGRP,123,32,0,13094
   Lutron RRA2/Caséta Threaddebug Lutron IP Gateway: 45 characters read:
PUT,124,30,1,100.00
~OUTPUT,124,32,0,13094

   Lutron RRA2/Caséta Threaddebug Lutron IP Gateway: self.buffer = '~OUTPUT,124,1,100.00
~OUTPUT,124,29,6
~OUTPUT,124,30,1,100.00
~OUTPUT,124,32,0,13094
'
   Lutron RRA2/Caséta Threaddebug Lutron IP Gateway: msg = '~OUTPUT,124,1,100.00
'
   Lutron RRA2/Caséta Threaddebug Lutron IP Gateway: self.buffer = '~OUTPUT,124,29,6
~OUTPUT,124,30,1,100.00
~OUTPUT,124,32,0,13094
'
   Lutron RRA2/Caséta Threaddebug Received command: ~OUTPUT,124,1,100.00 from Gateway<PHONE_NUMBER>
   Lutron RRA2/Caséta Threaddebug Received an Output message: ~OUTPUT,124,1,100.00
   Lutron RRA2/Caséta Debug       Received: Shade Family Room Shade 2 opening set to 100.0
   Lutron RRA2/Caséta Threaddebug Lutron IP Gateway: self.buffer = '~OUTPUT,124,29,6
~OUTPUT,124,30,1,100.00
~OUTPUT,124,32,0,13094
'
   Lutron RRA2/Caséta Threaddebug Lutron IP Gateway: msg = '~OUTPUT,124,29,6
'
   Lutron RRA2/Caséta Threaddebug Lutron IP Gateway: self.buffer = '~OUTPUT,124,30,1,100.00
~OUTPUT,124,32,0,13094
'
   Lutron RRA2/Caséta Threaddebug Received command: ~OUTPUT,124,29,6 from Gateway<PHONE_NUMBER>
   Lutron RRA2/Caséta Threaddebug Received an Output message: ~OUTPUT,124,29,6
   Lutron RRA2/Caséta Threaddebug Lutron IP Gateway: self.buffer = '~OUTPUT,124,30,1,100.00
~OUTPUT,124,32,0,13094
'
   Lutron RRA2/Caséta Threaddebug Lutron IP Gateway: msg = '~OUTPUT,124,30,1,100.00
'
   Lutron RRA2/Caséta Threaddebug Lutron IP Gateway: self.buffer = '~OUTPUT,124,32,0,13094
'
   Lutron RRA2/Caséta Threaddebug Received command: ~OUTPUT,124,30,1,100.00 from Gateway<PHONE_NUMBER>
   Lutron RRA2/Caséta Threaddebug Received an Output message: ~OUTPUT,124,30,1,100.00
   Lutron RRA2/Caséta Threaddebug Lutron IP Gateway: self.buffer = '~OUTPUT,124,32,0,13094
'
   Lutron RRA2/Caséta Threaddebug Lutron IP Gateway: msg = '~OUTPUT,124,32,0,13094
'
   Lutron RRA2/Caséta Threaddebug Lutron IP Gateway: self.buffer = ''
   Lutron RRA2/Caséta Threaddebug Received command: ~OUTPUT,124,32,0,13094 from Gateway<PHONE_NUMBER>
   Lutron RRA2/Caséta Threaddebug Received an Output message: ~OUTPUT,124,32,0,13094
   Lutron RRA2/Caséta Threaddebug Lutron IP Gateway: 50 characters read:
~SHADEGRP,123,32,2,100.00
~OUTPUT,124,32,2,100.00
   Lutron RRA2/Caséta Threaddebug Lutron IP Gateway: self.buffer = '~SHADEGRP,123,32,2,100.00
~OUTPUT,124,32,2,100.00'
   Lutron RRA2/Caséta Threaddebug Lutron IP Gateway: msg = '~SHADEGRP,123,32,2,100.00
'
   Lutron RRA2/Caséta Threaddebug Lutron IP Gateway: self.buffer = '~OUTPUT,124,32,2,100.00'
   Lutron RRA2/Caséta Threaddebug Received command: ~SHADEGRP,123,32,2,100.00 from Gateway<PHONE_NUMBER>
   Lutron RRA2/Caséta Debug       Gateway<PHONE_NUMBER> Unrecognized command: ~SHADEGRP,123,32,2,100.00
   Lutron RRA2/Caséta Threaddebug Lutron IP Gateway: 2 characters read:

   Lutron RRA2/Caséta Threaddebug Lutron IP Gateway: self.buffer = '~OUTPUT,124,32,2,100.00
'
   Lutron RRA2/Caséta Threaddebug Lutron IP Gateway: msg = '~OUTPUT,124,32,2,100.00
'
   Lutron RRA2/Caséta Threaddebug Lutron IP Gateway: self.buffer = ''
   Lutron RRA2/Caséta Threaddebug Received command: ~OUTPUT,124,32,2,100.00 from Gateway<PHONE_NUMBER>
   Lutron RRA2/Caséta Threaddebug Received an Output message: ~OUTPUT,124,32,2,100.00

The current Integration doc is version AE from 4/27/20.  The SHADEGRP command doesn't document action 32, which is one of the updates you're getting.  I wonder if the MW software is automatically creating the groups.
I'll see if my RRA2 software does this.

I could use the XML file from your Homeworks systems.  Can you follow the directions in this link and post the zip file to this issue.
https://forums.indigodomo.com/viewtopic.php?f=217&t=20382

Hi sorry for the late reply, missed the notification from Github. I sent the XML to you via the Indigo forum :)

I can see the SHADEGRP definitions in the XML file, but I'm really not sure what capabilities need to be implemented to use them.
Homeworks DbXmlInfo.xml.zip

Did you ever figure out what these commands are used for?  Hard to implement if I have no clue how they're used.  Or should we punt and just close this?