Go to Previous Change plays cue for current and previous change

Testing #171860
I have a file like this

When I am on the last change and play Go to Previous Change via the command palette, I hear both the deleted cue and the modified cue.

I think what you're hearing is actually the Error on Line cue, which is because the prior line has an error and is also modified. the sound is quit similar, so I see why that's confusing.


test(server): Update and re-enable the tests/server.rs test

These tests were temporarily disabled during the migration to the
std::future::Future type that's part of the stable Rust now.
These are updates to the tests that make them pass again.

I've rebased this manually into master, thanks so much!


figure out why the SVG file import logic isn't working correctly

right now the workaround of creating a component for just the svg doesn't sit well tbh

vite-svgr-plugin wasn't being configured correctly. fixed in recent pr's


Traffic Router inconsistent behavior on HTTP HEAD requests

I'm submitting a ...

[x] bug report
[ ] new feature / enhancement request
[ ] improvement request (usability, performance, tech debt, etc.)
[ ] other

Traffic Control components affected ...

[ ] CDN in a Box
[ ] Documentation
[ ] Grove
[ ] Traffic Control Client
[ ] Traffic Monitor
[ ] Traffic Ops
[ ] Traffic Ops ORT
[ ] Traffic Portal
[x] Traffic Router
[ ] Traffic Stats
[ ] Traffic Vault
[ ] unknown

Current behavior:

The TR response to a HEAD request should resemble the same as a GET response. However, the behavior I'm seeing seems problematic. Following examples of each (from curl output) with timing info included:
Proper GET response:
> GET / HTTP/1.1
> Host: [REDACTED]
> User-Agent: curl/7.54.0
> Accept: */*
>
< HTTP/1.1 302 Found
< Location: [REDACTED]
< Content-Length: 0
< Date: Tue, 08 Oct 2019 14:58:45 GMT
<
* Connection #0 to host [REDACTED] left intact

real	0m0.705s
user	0m0.008s
sys	0m0.015s

Improper HEAD response:
> HEAD / HTTP/1.1
> Host: [REDACTED]
> User-Agent: curl/7.54.0
> Accept: */*
>
< HTTP/1.1 302 Found
< Location: [REDACTED]
< Transfer-Encoding: chunked
< Date: Tue, 08 Oct 2019 15:23:12 GMT
<
* transfer closed with outstanding read data remaining
* stopped the pause stream!
* Closing connection 0

real	0m10.855s
user	0m0.007s
sys	0m0.017s

Note that the HEAD response is including Transfer-Encoding: chunked, which is causing the client to wait for body data which never arrives. After ~10 seconds, Traffic Router times out the connection and resets the TCP connection (verified TR sends FIN at this point with a packet capture).
Expected / new behavior:

TR should be responding to a HEAD request with Content-Length: 0, and NOT Transfer-Encoding: chunked.
Minimal reproduction of the problem with instructions:

Traffic Router version: 3.0.0-9930.f225e63b.el7
Problem can easily be replicated by sending a HEAD request with curl:
time curl -vs -o /dev/null -X HEAD http://ccr.invalid.cdn.example.com/

Anything else:

Alternatively, chunked responses with zero chunks would be fine, I think. Not sure why we'd want to do that, but it just seems like something on the TR end is expecting to write data but doesn't get it.

The wait itself is wontfix cURL-specific behavior. From a curl-users mailing list thread:

The difference in the HTTP protocol between a HEAD and a GET response is that a HEAD response is exactly the same as the GET response except that there's no response body. Since curl knows it sent a GET request, it will wait for a response body if the response headers indicate there is one. If curl knows it sent a HEAD it will just not wait for a response, even if the headers say there is one, since it knows a server will never send a response body to such a request.

That said, setting a content length does get rid of the timeout. As a proof-of-concept, I have added the Content-Length header for steering responses on a branch: https://github.com/apache/trafficcontrol/compare/a5a4bb9012...zrhoffman:set_content_length
Would we also want to ensure a content length for the TR API?

Per RFC 7231:
The server SHOULD send the same
 header fields in response to a HEAD request as it would have sent if
 the request had been a GET, except that the payload header fields
(Section 3.3) MAY be omitted.

TR sends Content-Length: 0 as part of a HTTP GET response, so based on the RFC recommended behavior, then I believe it should do the same in response to an HTTP HEAD.

Sorry... actually, Content-Length is one of the payload headers that MAY be omitted in a HEAD response. At any rate, keeping that header as part of the HEAD response is still RFC-compliant behavior.
I think the bigger problem is the Transfer-Encoding: chunked header, which is NOT part of the standard HTTP GET request from TR. Its unclear why we would want TR to send that at in any case of a 302 response.

Most of the API's mappings return a ResponseEntity, which guarantees setting Content-Length for any status code. The exceptions are in LocationController, StatsController, ZonesController (which return Content-Length for HEAD but not GET), but it looks like we can just use ResponseEntity for those, too. The object order in the response seems different, but the structure is the same and LocationsTest, and StatsTest, ZonesTest still pass.
The documentation will need to be updated to reflect the change in response headers.

I haven't verified hits PR, but what would be the Content-Length on a Steering delivery services with ?trred=false ?

This seems to be a big deal.. More than half our requests are HEAD requests... That should change the TCP stats for our Traffic Routers considerably.

I don't object to the change itself, but I have concerns about what's driving it.
The HTTP Spec says servers MUST NOT send Content-Length if they use Chunked encoding, and clients MUST accept Chunked encoding.
Therefore, any Clients which require Content-Length are in violation of HTTP.

actually, Content-Length is one of the payload headers that MAY be omitted in a HEAD response.

Right. So, the server isn't in violation of the spec here, it's permitted to include Tranfer-Encoding. I agree, it probably shouldn't.
But moreover, Transfer-Encoding is a payload field, and HEAD payloads have no defined semantics. So, if it's confusing any clients, those clients are violating the HTTP spec.
So again, it doesn't seem wrong to change the server (maybe even following the Robustness Principle). But we should fix the broken clients driving this.

But why do we bother to send Transfer-Encoding: chunked on a HEAD response with no body? Even if the spec says we can, should we be? Seems to serve no purpose.

Is GET not chunked?

Nope. See my examples of the current GET/HEAD responses in the issue description.


Smart Contracts Not Appearing on OpenSea After Deployment

Description:
We've encountered a critical issue with the scripty.sol library as we approach our project release. Despite following the deployment procedures that worked previously, our smart contracts are not visible on OpenSea. This issue is not isolated to our custom contracts; it also affects the example contracts provided within the library's repository.
Steps to Reproduce:
npx hardhat run examples/randomShapes/deploy.js --network --goerli
Search for the deployed NFTs on OpenSea.
Expected Behavior:
The deployed smart contracts should be visible and verifiable on OpenSea as they have been in the past.
Actual Behavior:
The deployed smart contracts do not appear on OpenSea, neither through direct search nor through the OpenSea verification process. This issue persists even with the example contracts from the scripty.sol library.
Additional Information:
This sudden change in behavior is puzzling since the deployment and verification steps have not changed, and they previously resulted in the contracts appearing on OpenSea without issue.
We are working with a tight deadline and are eager to resolve this issue promptly.
Questions:
Has anyone experienced a similar issue with smart contracts not appearing on OpenSea after deployment using the scripty.sol library?
Are there specific details or log information that would be particularly helpful for troubleshooting this issue?
Any insights, advice, or suggestions on how to address this problem would be greatly appreciated.
Thank you in advance for any help or guidance you can provide. We are looking forward to your suggestions and are happy to provide any additional information that might help resolve this issue.

Hello!
Thanks for using scripty.sol! Recently OpenSea dropped supporting Goerli. I suggest you to switch to Sepolia.
Also, scripty.sol went under some updates but changes are not merged to main branch yet. You can check the changes here.
In that branch, you will see that all the examples are upgraded to Sepolia and we upgraded our storage solution and EthFS V2 storage wrapper to EthFS V2.


Streaming Request?

I'm playing around with the EWS streaming subscription and am wondering if there is a way to access the streaming request as data comes in instead of waiting until it finishes?
For example, if I create a subscription then use the "GetStreamingEvents" function like so:
		ews.run("GetStreamingEvents",{
			SubscriptionIds:{
				SubscriptionId:this.subscriptionId
			},
			ConnectionTimeout:1
		}).then(events => {
			//Do something with events
		}, err => {
			//Ooops, something went wrong!
		});

The "then(events => {..."
I've been digging through the node-ews and node-soap code but am not seeing anything that can allow me to do that without forking it. I was hoping someone here may have another idea or knows of something that I've missed?
Thanks in advance!

We are already on a modified fork of node-soap to fix a recursion issue with stack overflow when parsing the MS wdsl. If it makes sense to, we can modify that fork? Otherwise, been thinking of replacing node-soap completely, but yet to find the time to research another library.

I ended up putting this on the back burner and focusing on push notifications instead which I was able to get working with minimal modifications. However, I think I've got an idea on how to do this.
It would appear that the node-soap HttpClient (soap\lib\http.js:21) accepts options.request as an option that later gets used to make the eventual request to the soap server. I then tracked the wsdlOptions object and it would appear that it gets passed along to wsdl.open_wsdl whereby it is then used to create a new HttpClient (soap\lib\wsdl.js:2149). I think I can tap into that by passing a custom function as wsdlOptions.request that wraps the request module. Then I should be able to intercept the request and pipe (https://github.com/request/request#streaming) it to a function that can process the incoming stream.
If that works then no modifications should be needed. I'll keep everyone posted on how it goes.

Also, have you seen strong-soap? (https://github.com/strongloop/strong-soap) I haven't played with it yet but it might be a suitable alternative and would seem to fit in node-ews perfectly with little to no modification. I'm just not sure about the stack overflow issue. But if I get a chance I'll replace node-soap with that and let you know how it goes. Can you link me to the original issue and fix for the stack overflow problem so I can be sure to test properly?

Issue #17

Oh yeah... I remember that issue now! :)

Moved over to the updated version of node-soap (19.2) in version 3.2.x. Im curious if this is working now?

Has this issue been fixed aready? I still encounter the Problem


tmuxPlugins.mode-indicator: init at 2021-10-01

Description of changes

Add a new plugin for tmux
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/697

@ofborg build tmuxPlugins.mode-indicator

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/1590


update max objects limit to 10 when jsonrpc updates the return limit

Description
When calling Transaction.build and the parameters contain more than 10 objects, jsonrpc returns Input exceeds limit of 10. The reason is that the jsonrpc request parameters previously allowed a maximum of 50 objects, but starting from 11/09, it was limited to 10.
Test plan
How did you test the new or updated feature?

Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.

[ ] Protocol:
[ ] Nodes (Validators and Full nodes):
[ ] Indexer:
[x] JSON-RPC: update max objects limit to 10 when jsonrpc updates the return limit,  <Input exceeds limit of 10> will be fixed
[ ] GraphQL:
[ ] CLI:
[ ] Rust SDK:
[ ] REST API:

This RPC change has been reverted, but I am adding an option to configure this limit here: https://github.com/MystenLabs/sui/pull/19345#pullrequestreview-2301532342


Restrict manager access to a specific namespace for some resources

Except for M4DApplications, manager does not need cluster-wide access to resources.
For example, pods and deployments are created in m4d-blueprints, m4dmodules are read from m4d-system, etc.
A new release of controller-runtime (0.9.0 and higher) enables to control manager access.
Required: to upgrade controller-runtime version to 0.9.0 with all relevant dependencies.

Why does it need cluster wide access to secrets? Cluster wide access to secrets is an issue.

Why does it need cluster wide access to secrets? Cluster wide access to secrets is an issue.

My mistake, it does not. The secrets manager needs are from m4d-system.

Should we stop importing datashim and use unstructured.Unstructured instead? I'm not sure when they will upgrade to newer operator-sdk that doesn't cause so many dependency issues.

Depends on https://github.com/mesh-for-data/mesh-for-data/issues/674

From a multi-tenancy perspective, is it possible to configure more than one mesh-for-data control plane in a single kubernetes/openshift cluster?
Based on my experimentation, it seems that if multiple managers are installed to the same cluster, all will act on a new m4dapplication, and there doesn't seem to be a way to scope on a namespace-by-namespace basis.  I've tried adjusting clusterrolebindings -> rolebindings, but it seems the reconcilers are attempting to query cluster-wide, so this just results in errors in the manager logs.

From a multi-tenancy perspective, is it possible to configure more than one mesh-for-data control plane in a single kubernetes/openshift cluster?
Based on my experimentation, it seems that if multiple managers are installed to the same cluster, all will act on a new m4dapplication, and there doesn't seem to be a way to scope on a namespace-by-namespace basis. I've tried adjusting clusterrolebindings -> rolebindings, but it seems the reconcilers are attempting to query cluster-wide, so this just results in errors in the manager logs.

@ngoracke at this time you can have only one instance of mesh for data, we have been following the Istio model which is one control plane per cluster. We are considering moving to a model similar that Red Hat implemented for their variant of Istio, which would allow multi tenancy.

@ronenkat is there an issue open for that work? or not yet decided to do so?

@ronenkat is there an issue open for that work? or not yet decided to do so?

@jlkaus there is no open issue yet, it is on the "want to do", please feel free to open an issue, add requirements.
We would be happy to get help for this interesting topic.

@ronenkat Do we need a new issue or can the effort be added here?  We can certainly create a separate issue if that is desired.  For our internal cluster pipelines, developer needs, as well as customers that share a cluster with multiple CPD instances, we will all need cluster "multi-tenancy" support for all of  M4D.  Do you want assistance from our team or will this be handled by the research team?  Do you have a prioritization scheme for your git issues?


Changelog upon new version

Hi,
There were many recent great additions to BRouter-web (which I missed, congrats for these!). What about keeping track of a CHANGELOG between versions and having it displayed automatically at first visit of Brouter-web?
It would probably help old users discover and get started with new features!
Best,

It's actually something that landed a few weeks ago in master (no release since), because indeed a lot of new features are coming and it's hard to follow/discover all of them :). Cf #372


How to use dynamic xpaths in this

Hello
Tried this framework but stuck when i need to use dynamic xath

Hello @Ducistech,
You can add XPath selectors to your page objects like here - https://github.com/Marketionist/protractor-cucumber-steps/blob/master/tests/page_objects/test.page.js#L8 and then use them in your spec files


Create configuration screen

This will let users configure some parts of the UI like the number of rows shown by default.

The configuration will be saved in a cookie as a JSON object. Should I compress the JSON string. Some testing:
import gzip
import base64
import json

data = {
    "max_rows": 10,
    "sqlite_bin_paths": ["/usr/bin/sqlite3", "/home/ubuntu/.bin/sqlite3"],
    "recent_dbs": ["/home/ubuntu/data.db", "/home/ubuntu/app/data.db"],
    "ssh_key": "~/.ssh/id_rsa",
}

data_2 = {
    "max_rows": 10,
    "sqlite_bin_paths": ["/usr/bin/sqlite3", "/home/ubuntu/.bin/sqlite3"],
    "recent_dbs": ["/home/ubuntu/data.db", "/home/ubuntu/app/data.db"],
    "ssh_key": "~/.ssh/id_rsa",
    "foo_max_rows": 10,
    "foo_sqlite_bin_paths": ["/usr/bin/sqlite3", "/home/ubuntu/.bin/sqlite3"],
    "foo_recent_dbs": ["/home/ubuntu/data.db", "/home/ubuntu/app/data.db"],
    "foo_ssh_key": "~/.ssh/id_rsa",
    "bar_max_rows": 10,
    "bar_sqlite_bin_paths": ["/usr/bin/sqlite3", "/home/ubuntu/.bin/sqlite3"],
    "bar_recent_dbs": ["/home/ubuntu/data.db", "/home/ubuntu/app/data.db"],
    "bar_ssh_key": "~/.ssh/id_rsa",
}

raw_data = json.dumps(data).encode()

print(f"Raw data: {len(raw_data)}")

compressed_data = gzip.compress(raw_data)

print(f"Compressed data: {len(compressed_data)}")

compressed_b64 = base64.b64encode(compressed_data)

print(f"Compressed b64: {len(compressed_b64)}")

With data:
Raw data: 183
Compressed data: 136
Compressed b64: 184

With data_2:
Raw data: 581
Compressed data: 175
Compressed b64: 236

With a small configuration mapping, it doesn't make much sense to compress it. It would make debugging harder and add overhead. But when the mapping grows (data_2) it may be worth compressing the data.


Add Stateless example to the workflow

Testing the build with the stateless examples

Thanks @DavideD, appreciated.


UI: using autocomplete on command line

Would there be a possibility to get autocompletion on the 'Enter debugger commands here' field? This would be especially useful when using "print some_variable" commands.

Thank you for the suggestion. That would be quite handy but I currently don't have much time to look into it. I'll be happy to review a pull request though.

Thanks for your fast answer.
I never wrote code for any Atom module so it may be a quite high threshold, but I will have a look at it. Any advise where I should look in your code, how / where I may be able to add this kind of feature?

To be honest, I have no idea how to implement autocomplete. The first thing to do is probably to study another package that implements autocomplete, but it may be a steep learning curve.


Network with hundreds of bots has latency (spike) issues!!!

At least on macOS

also "too many open file handles error"

This is largely been fixed by chunking into one giant buffer.

also has if we go this route again could be improved by us now using writev


Investigate why deserializing ledger proofs takes so long

Deserializing proofs should basically be a memcpy, @ghost-not-in-the-shell can you investigate ?

https://github.com/CodaProtocol/coda/issues/3674 see this

This is mitigated by https://github.com/o1-labs/snarky/pull/403


vue beta.7 may be causing problems with vue-router and vuex

Version
4.0.0-alpha.9
Reproduction link
https://github.com/ais-one/vite-eg/tree/master/test
Steps to reproduce
npm i
npm run dev
navigate to <IP_ADDRESS>:3000
error will appear on console.log
What is expected?
should work without error
What is actually happening?
router view throws an error

It is ok in vue 3 beta 4
Please also see the following link for more info
https://github.com/vuejs/vite/issues/44

Closing in favor of https://github.com/vuejs/vue-router-next/issues/209


fix: remove optional chaining usage to prevent Node.js 14 incompatibility

Why?
Using optional chaining operator break the Node.js 14 compatibility. I didn't found any changelog mentioning this in the last releases so I deduced that it was a small oversight.

@alexandrebouthinon are you sure about that? optional chaining operator is available starting from node 14. Could you check youyr nodejs version?

Also tests would not pass if it wouldn't be supported by node 14: https://github.com/moscajs/aedes-persistence/blob/main/.github/workflows/ci.yml#L14


System.InvalidOperationException: 'Visual was invalidated during the render pass'

Discussed in https://github.com/AvaloniaUI/Avalonia/discussions/9617

Originally posted by sonicsmooth December  4, 2022
Using Windows 10 Home, Avalonia <IP_ADDRESS>-preview4, Visual Studio Community 17.4.2
I'm following the AngelSix youtube video 009 https://www.youtube.com/watch?v=T1kErI5VkW4
At 12:40 he introduces the following line in MainView.axaml.cs:
mChannelConfigPopup.Margin = new Thickness(0,0,0,0);
This builds fine but I get the exception upon assigning a new value to Margin (creating the Thickness object works okay):

I traced this back to some if(_updating) statement in CompositingRenderer.cs/AddDirty(IVisual visual), which doesn't help me much as I'm pretty new to this.
I couldn't find this issue on google or stackoverflow.
thanks.

Thanks, so what is the correct way to set the margin as in the video instruction?

It doesn't make much sense to do it in the renderer imo. Maybe ask the video creator about this issue?

Cool, thanks for clarifying that this may not be the canonical way of doing this.  I'll check with video creator.


keyboard support, node remove/split actions

selected node chevron is rendered with magenta color

changed how scale works

instead of fixed values (20,10,5,2,1,0.1,0.01) im using +-delta value (so i can have any scale value that i want, also less buttons)

keyboard support for node editing

numpad keys 4,5,6,7,8,9 correspons to ui move / rotate buttons
numpad enter toggles between move / rotate operation
numpad + and numpad - changes scale
numpad * and numpad / changes scale delta
numpad 0 resets scale to 0

refactored code that is editing node from UIMoveTool to NodeManager class

refactored UIMoveTool BuildWindow method

refactored StateTracker classes

glost classes store info about deleted node/segment for undo/redo magic to work
it will also not store those values in ctor, because they may change before Apply/Revert is called

added 'Split' action to node editor

this will remove selected node and replace it with multiple nodes roughly at the same location with track segments
connections from old node 'other' nodes

added 'Remove' action to node editor

this will remove node and its segmetnts
alt mode for simple rail: removing 'noce B' from (node A --- node B --- node C) will result in (node A --- node C)

issues:

when I quit to main menu with editor open and start new game editor is still active and also start throwing exception, because some game objects where destryoed

tryied to register OnMapDidUnload event but didnt removed editor correctly ...

when I close UIMoveTool im unable to open it again

i 'fixed' that by not removing node changed event handler in OnDeactivating

game sometimes do not redraw rails correctly ('Rebuild Track' usually fixes that)

i think that rebuild is not calling something / its timing issue

obsolete


Some high carbon regions have 3 leaves

Leaf rendering seems to have an issue: Jakarta shouldn't have 3 leaves.
It doesn't seem to affect the region sorting. The problem likely comes from the code that translates carbon info into number of leaves

Bug is because https://github.com/GoogleCloudPlatform/region-picker/blob/main/index.js#L131 doesn't handle regions with gCO2_kWh > 600. The code should return 0

Leaf rendering seems to have an issue: Jakarta shouldn't have 3 leaves.
It doesn't seem to affect the region sorting. The problem likely comes from the code that translates carbon info into number of leaves


Q-Network

The Q-Network is a neural network derived from torch.nn.Module, implementing all the features necessary for state action value estimation and back propagation by Gradient Descent.

Implemented in #5


Will @storybook/react-native v5.0.0 release??

Describe the bug
It looks to me that @storybook/react-native v5.0.0 is NOT released 🤔
To Reproduce
$ npm search @storybook/react-native
NAME                      | DESCRIPTION          | AUTHOR          | DATE       | VERSION  | KEYWORDS
@storybook/react-native   | A better way to…     | =alexandrebodin… | 2019-02-21 | 4.1.13   | react react-native storybook

Expected behavior
expected that publish @storybook/react-native with other storybook libraries as same version 😃
System:
$ npm -v
6.8.0

Yes it's work in progress and should be out in the next few weeks. We didn't have a clear timeline on that and didn't want it to hold up the 5.0 release. Will release and announce it soon. Thanks for your patience!

Boo-yah!! I just released https://github.com/storybooks/storybook/releases/tag/v5.1.0-alpha.12 that addresses this issue. Upgrade today to try it out!
Because it's a pre-release you can find it on the @next NPM tag.

We’ve released a brand new @storybook/react-native with a bunch of core improvements. It’s available in the latest 5.1-alpha on next and has been verified by several RN users on their existing apps. It should fix a bunch of compatibility issues, especially if you’re using the web server feature. Please give it a try and comment here if it fixes your problem.
Will test 5.1-alpha and get back to you. @OKNoah

We're on 5.1.0-beta now. Check it out!


Nav bullets appearing in latest release

It appears a latest release has caused bullets to appear in the side menu.
See https://dev.m3o.com/
We're using github pages with the remote theme.

@asim : you have overwritten _includes/nav.html (https://github.com/micro/development/blob/master/docs/_includes/nav.html) so you need to update this file with the changes made in just the docs.
You should also remove https://github.com/micro/development/blob/master/docs/assets/js/search-data.json

Thanks for the info. Will close.


Release Camunda Modeler v3.2.0

What's inside

Improved modeling<EMAIL_ADDRESS>Updated CMMN (https://github.com/bpmn-io/cmmn-js/issues/113)
Properties panels version bumps

Tasks

[x] put up code freeze appointment in calendar (include modeling, michael.schoettes, sre, and ilias.kourtoudis)
[x] make sure dependencies are released (rm -rf node_modules && npm i && npm run all works)

bpmn-js, dmn-js, cmmn-js, *-properties-panel, *-moddle, ...

[x] smoke test to verify all diagrams can be created
[x] update CHANGELOG before releasing (cf. v3.2.0 entries)
[x] Verify master is merged into develop (git checkout master && git pull && git checkout develop && git merge master)
[x] semantic release (npm run release), cf. release schema
[x] Merge develop into master (git checkout master && git merge develop)
[ ] wait for Travis to build the release
[ ] execute integration test on released artifacts

[ ] Works on Linux
[ ] Works on Mac @akifhazarvi
[ ] Works on Windows

[ ] trigger QA for fuzzy testing @akifhazarvi
[ ] publish release on Github Releases
[ ] write blog post on blog.camunda.org @barmac
[ ] trigger mirroring of release to https://camunda.org/release/camunda-modeler/ via Jenkins
[ ] update download version of Camunda Modeler at camunda.com
[ ] spread the word

[ ] send release notice email
[ ] tweet

[ ] close current milestone

Depends on https://github.com/camunda/camunda-modeler/issues/1423
Depends on https://github.com/bpmn-io/bpmn-js/issues/1129

This is amazing 💯

Release artifacts built: https://github.com/camunda/camunda-modeler/releases/tag/v3.2.0

Regression found:

https://github.com/camunda/camunda-modeler/issues/1431

Regression found:

#1431, gets fixed via bpmn-io/bpmn-js#1131

I've just merged this.

Patch released as v3.2.1 :rocket:

All looks good. Good to go 🚀🚀


[RESOLVED] Interface eth0(): High error rate (>2 for 5m)

Problem started at 12:33:29 on 2023.07.14
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Operational data: errors in: 2, errors out: 0
Original problem ID: 32646
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23483&eventid=32646

Problem has been resolved in 6m 0s at 12:39:29 on 2023.07.14
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Original problem ID: 32646


modes and stuff

-made role and gamemode lists nicer
-fixed a couple current lycanthropy bugs and seperated doomsayer and totem lycans
-made piper give full charmed list each night
-bug fixing
-fixed some bodyguard bugs
-fixed crow not seeing some roles
-fixed kill teams a little
-amne turning when dead
-default mode roles changed
-chaos mode roles changed
-drunkfire and orgy changed minorly
-gave belunga, evilvillage, and valentines higher max player counts
+revamped gamemode choosing to that of lykos
+added mad scientist, clone, lycan, time lord, turncoat roles
+added mad, lycan, rapidfire, noreveal, aleatoire modes

Nice.

I wish I knew how to code so I could really help unless one of you could teach me the ropes


docs(accessibility): add decsriptions to components and behaviors

Add descriptions to components and behaviors
In components, put @accessibility description first, before behaviors
In behaviors, explicitly split description and specification of behaviors

Warnings

:warning:
There are no updates provided to CHANGELOG. Ensure there are no publicly visible changes introduced by this PR.

  Generated by :no_entry_sign: dangerJS


NO: Add 1.3.0 test data

Hi @RKlaus-tsi, please verify.

Android 1.0.5: all 3 certificates shown as invalid. REC certificate is shown as invalid. Vac and Test are expired
iOS 1.0.5: all 3 certificates shown as invalid and signature not valid

Android 1.06.-acc:
REC.png  - Verification failed (without showing what it is (Rec,Vac,Test))
TEST.png - Certificate expired
VAC.png - Verification failed

in the readme:
Used for productive DCCs issuance

From: 24.06.2021
Until:

.... seems they must be valid only from tomorrow

Replaced by https://github.com/eu-digital-green-certificates/dcc-quality-assurance/pull/34


chore(master): release 1.2.2

:robot: I have created a release beep boop
1.2.2 (2022-03-30)
Bug Fixes

fix avatar height bug (cd4ab76)
fix parmas to params (2c7211c)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/kailong321200875/vue-element-plus-admin/releases/tag/v1.2.2 :sunflower:


Logout button affected by blocking code

During a long load process, the load button will become unusable due to the blocking code that is currently being executed.
For example, D2Synergy will fetch the latest manifest entries and save them to indexeddb. However, this means that the code is being executed asynchronously, and as a result, blocks the event listener for the log out button.
If, for whatever reason, the above mentioned functionality fails to work, then the user is prompted to log out and try again. This is not possible due to the aforementioned issue.
Pending an overview of the asynchronous, synchronous functions.

I'm going to leave this one for a while until I figure out a better way to approach this.
After doing some research and messing about, it seems that it's quite literally blocked when I request the manifest.

The corresponding event listener for the logout was moved out of the context that was blocking it from executing during initial load.


Multi-homed nodes

Is your feature request related to a problem? Please describe.
The current implementation of CAPVCD allows to use only one network.
A customer has multiple networks for external access, internal infra traffic, internal workload traffic...
They have a hard requirement for the nodes to be attached to several networks.
Describe the solution you'd like
We need to be able to attach the node to several networks like in CAPO: https://github.com/kubernetes-sigs/cluster-api-provider-openstack/blob/main/docs/book/src/clusteropenstack/configuration.md#multiple-networks
Describe alternatives you've considered
No response
Additional context
No response

What do we want to do?
As stated above, We want to be able to attach multiple NICs to cluster nodes so that we can access multiple networks.
Current Implementation

OvdcNetwork is a part of VCDClusterSpec.
https://github.com/vmware/cluster-api-provider-cloud-director/blob/0f367c71ebcc94ef2555e9a541d6c7cc5a0deeef/api/v1beta1/vcdcluster_types.go#L80

It is used while creating the vApp
https://github.com/vmware/cluster-api-provider-cloud-director/blob/0f367c71ebcc94ef2555e9a541d6c7cc5a0deeef/controllers/vcdcluster_controller.go#L782
https://github.com/vmware/cloud-provider-for-cloud-director/blob/81b03e668ec1a5b5b552becf3d673e9aa7bb1f59/pkg/vcdsdk/vapp.go#L246

Then the first network of vApp is attached to nodes.
https://github.com/vmware/cloud-provider-for-cloud-director/blob/187fe988658117ac694999b4092307f1206bd16f/pkg/vcdsdk/vapp.go#L644

Shortly, current assumption is 1 cluster = 1 vApp = 1 OvdcNetwork
Other providers
I checked other providers (e.g. CAPO, CAPA) and saw that they mostly have a single parameter in Cluster level but they allow users to state more network interfaces per Machine.
CAPA

https://github.com/kubernetes-sigs/cluster-api-provider-aws/blob/main/api/v1beta1/awscluster_types.go#L37
https://github.com/kubernetes-sigs/cluster-api-provider-aws/blob/main/api/v1beta1/awsmachine_types.go#L134

CAPO

https://github.com/kubernetes-sigs/cluster-api-provider-openstack/blob/main/api/v1alpha6/openstackcluster_types.go#L43
https://github.com/kubernetes-sigs/cluster-api-provider-openstack/blob/main/api/v1alpha6/openstackmachine_types.go#L60

Proposal

Adding a new string array (OvdcNetworks) in VCDMachine spec to allow users to state network interfaces per machine.
When it is empty, OvdcNetwork in Cluster spec can be used by default.
machine_controller also has to ensure that that network is added to vApp too.

Here is the draft PR for this proposal https://github.com/vmware/cluster-api-provider-cloud-director/pull/254


operator: stop managing on unknown management state

When the management state value is set to foo, we should stop managing and additionally emit a warning. We don't want to emit a warning per controller loop, so I added one to target config reconciler in each operator.

/lgtm

/approve


Custom JS not working.

Custom JS not rendering on front-end.

please provide more actionable info


Remove Scrypted

[!NOTE]
We are meticulous when it comes to merging code into the main branch, so please understand that we may reject pull requests that do not meet the project's standards. It's never personal. Also, game-related scripts have a lower chance of being merged.

Description
Remove Scrypted from webpage for now
Fixes #494
Type of change
Please check the relevant option(s):

[ ] Bug fix (non-breaking change that resolves an issue)
[ ] New feature (non-breaking change that adds functionality)
[x] Breaking change (a fix or feature that would cause existing functionality to change unexpectedly)
[ ] New script (a fully functional and thoroughly tested script or set of scripts.)

Prerequisites
The following efforts must be made for the PR to be considered. Please check when completed:

[ ] Self-review performed (I have reviewed my code, ensuring it follows established patterns and conventions)
[ ] Testing performed (I have tested my changes, ensuring everything works as expected)
[x] Documentation updated (I have updated any relevant documentation)

Additional Information (optional)
Provide any additional context or screenshots about the feature or fix here.
Related Pull Requests / Discussions
If there are other pull requests or discussions related to this change, please link them here:

Related PR #

Let's just remove the whole script? Scrypted have their own install script https://github.com/koush/scrypted/blob/main/install/proxmox/install-scrypted-proxmox.sh
No need for a script here aswell imo

Can we do, but the Script is them broken :D

Yes it's a breaking change, we can refer users to use the script maintained by Scrypted in CHANGELOG.md

Koush’s script does not work…

He was not interested in any solution. I'm not chasing after him. He just wanted it deleted.
By the way: I could hardly find any problems with the script, no examples were provided, but that's just the way it is


Persistent attribute isn't correctly handled

Description
I think there is a regression in how the "persistent" flag is handled, happened sometime between 6.0 and 6.4.
To Reproduce
I have an image + template named "Debian TPL" which I use to spin up my Debian instances. On this image the flag persistent is set to no. Before 6.4, when instantiating a VM from this template this was the result:
a - if in "Instantiate" tab persistent flag = yes -> end result is a copy of the image, with the persistent flag set at "yes"
b - if in "Instantiate" tab persistent flag = no -> end result is a VM pulling from original image with persistent flag set to "no"
In 6.4, with the image "Debian TPL" still having persistent=no, on instantiate this is what I get:
1a - on Instantiate, persistent = no -> VM uses the image of Debian TPL itself, non persistent
1b - on Instantiate, persistent = yes -> VM clones the image, but on the new image the persistent flag is still "no" -> data loss on shutdown
I though the solution was to set persistent=yes in the image used for the main template, but this has downsides too:
2a - on Instantiate, persistent = no -> VM uses the image of Debian TPL itself, in persistent mode
2b - on Instantiate, persistent = yes -> VM clones the image, on the new image persistent=yes
Expected behavior
[see above]
Details

Affected Component: Scheduler
Hypervisor: KVM
Version: 6.4

Additional context
Add any other context about the problem here.

Progress Status

[ ] Code committed
[ ] Testing - QA
[ ] Documentation (Release notes - resolved issues, compatibility, known issues)

have you checked the default image persistent flag?
https://github.com/OpenNebula/one/blob/master/share/etc/oned.conf#L361
closing as not sure what the wrong behaviour is, will reopen when that's clear.

Maybe let's start from use cases: as an user I want to have a single template for a given operating system and being able to instantiate it both in persistent and ephemeral options.
For persistent, I expect the template to be cloned along with the images. Images should be thus flagged as "persistent". For ephemeral, I expect VMs to be spinned up from this template with ephemeral volumes.
In previous versions (I said the regression happened after 6.0 but now I've found a misconfigured VM created while the host was on 6.0), I was using a template such as:
TEMPLATE 82 INFORMATION
ID             : 82
NAME           : TPL - Debian 11
USER           : oneadmin
GROUP          : oneadmin
LOCK           : None
REGISTER TIME  : 07/13 09:47:06

PERMISSIONS
OWNER          : um-
GROUP          : ---
OTHER          : ---

TEMPLATE CONTENTS
CONTEXT=[
  NETWORK="YES",
  SSH_PUBLIC_KEY="$USER[SSH_PUBLIC_KEY]" ]
CPU="1"
CPU_MODEL=[
  MODEL="host-passthrough" ]
DISK=[
  IMAGE_ID="126" ]
GRAPHICS=[
  LISTEN="<IP_ADDRESS>",
  TYPE="VNC" ]
HYPERVISOR="kvm"
INPUTS_ORDER=""
LOGO="images/logos/debian.png"
MEMORY="1024"
MEMORY_UNIT_COST="MB"
OS=[
  ARCH="x86_64",
  BOOT="" ]
VCPU="2"

And an image like:
IMAGE 126 INFORMATION
ID             : 126
NAME           : TPL - Debian 11
USER           : oneadmin
GROUP          : oneadmin
LOCK           : None
DATASTORE      : templates
TYPE           : OS
REGISTER TIME  : 07/13 09:47:06
PERSISTENT     : No
SOURCE         : /var/lib/one/datastores/103/18cf8240e76923d64c39d891dde8ad48
PATH           : https://marketplace.opennebula.io/appliance/8e015603-3dc2-4147-a25e-f58dced23e52/download/0
FORMAT         : qcow2
SIZE           : 2G
STATE          : rdy
RUNNING_VMS    : 0

PERMISSIONS
OWNER          : um-
GROUP          : ---
OTHER          : ---

IMAGE TEMPLATE
DEV_PREFIX="vd"
FROM_APP="286"
FROM_APP_MD5="18b3d13191d65b939bfd7d5af94ab949"
FROM_APP_NAME="Debian 11"

By instantiating this template as persistent, the result was a new template and a new image, with PERSISTENT     : Yes. By istantiating it as non persistent, the result was an instance with the template image mounted as non persistent.
Now, the behaviour changed and it seems whatever is the value for the "persistent" attribute in the template image will be carried over. So by creating a "persistent" VM from the image/tpl above, I get as a result an instance with "non persistent" storage.
Am I getting something wrong?

thanks for the detailed explanation.
Can you also share the oned.conf you are using in 6.4?

This is the first thing I checked, since the name rang a bell. I luckily had the configuration backups, and this value was not changed between 5.12 (where things were working as intended) and 6.4 (where things don't).
Did something else change? Ie the default applied? This value has always been commented out in my config.

I think this could be affected by #5386
If the values DEFAULT_IMAGE_PERSISTENT_NEW and DEFAULT_IMAGE_PERSISTENT are commented out, the new image inherits the persistence flag from the original image.
For me the behavior described in the first post make sense.

Yes! Thanks for spotting it @paczerny, that seems to be what I believe is a regression. This inheritance makes it impossible to have the distinct behaviours required when instantiating persistent and non persistent VMs:

Non Persistent: image from template with persistent = no is used
Persistent: image is cloned from template and the new one is set persistent = yes

Looking at the comments in 5.12's oned.conf, #5386 restores what should have been the behaviour according to comments:
#  DEFAULT_IMAGE_PERSISTENT: Control the default value for the PERSISTENT
#  attribute on image creation (oneimage clone, onevm disk-saveas). If blank
#  images will inherit the persistent attribute from the base image.
#
#  DEFAULT_IMAGE_PERSISTENT_NEW: Control the default value for the PERSISTENT
#  attribute on image creation (oneimage create). By default images are no
#  persistent if not set.

...but it breaks the fairly important use case of directly instantiating persistent and non persistent VMs without having to go back and change the flags manually.
If a decision is taken not to revert #5386, at least the change in behaviour should be documented. I guess the solution to my issue is to set DEFAULT_IMAGE_PERSISTENT = "YES", since instantiating persistent involves a clone?

Hello, I can confirm this problem. But there is another related. I am on 6.2 version and when I use instantiate as persistent, oned creates new image using datastore/clone, but wrongly calls tm/clone instead of tm/ln.

Same behaviour on 6.4 too.
The description of the "Instantiate as persistent" slider is as follow:

Creates a private persistent copy of the template plus any image defined in DISK, and instantiates that copy

The actual action is "Instantiate from copy": "Create a copy of the template plus any image defined in DISK, and instantiates that copy".
What is observed: if the VM template has non-persistent image defined it is copying the image in the datastore (datastore//clone) and then instantiates a VM using this template. And because the image is a copy of the primary image, the resulting VM disk is non-persistent, too (so tm//clone was called).
So, IMHO, either the text or the hint is misleading as there is no peristence at all - it is just cloning. Or, there is an issue/bug?/ in the applied logic.

Hi @atodorov-storpool , DEFAULT_IMAGE_PERSISTENT = "YES" helps. But if there is disk SIZE parameter defined in template, it is ends with error. Looks like there should be post-copy adjustment in src/rm/RequestManagerVMTemplate.cc after line 97

PRs:

src
tests

1b - on Instantiate, persistent = yes -> VM clones the image, but on the new image the persistent flag is still "no" -> data loss on shutdown

This is fixed.
Now you don't need to use the DEFAULT_IMAGE_PERSISTENT = "YES" , the disk in the instantiated VM has attributes PERSISTENT=YES, CLONE=NO. So I think it should solve also issues with driver action clone/ln.

But if there is disk SIZE parameter defined in template

@feldsam Usually you don't have a disk SIZE in the template, how did you get the disk SIZE there? Manually or it was a result of some onevm save or onetemplate clone action? Maybe I'm missing some use case?

Hello @paczerny, I added SIZE attr to template manually, because some images from app market are only 2GB and I want to have minimum 10GB. It works fine when running non persistent images, but would be fine, if I can run as persistent and either instantiate with it with original image size or better to change size automaticaly.

Just to close this off, I upgraded to 6.8.0 now and confirm the behaviour is back to what I would have expected.


 It starts being slow at 5 satellites. A heuristic for minimum number of satellites needed to complete federation needs to be added, and possibilities need to be processed in that order

Merging this for now since it includes changes that are useful for other things.
The algorithm that can hang the engine is not included for now.


Add Vento support

Hi, thanks for making this plugin! It's hard to find a good formatter for HTML templates.
Any chance that support for Vento could be added? https://github.com/ventojs/vento
If not, it would be nice to map filetypes to template types (ie, map .vto to Jinja to get some formatting), and add the ability to preserve whitespace around mustaches/tags/blocks.
Thanks!

You can map file associations in dprint config.

You can map file associations in dprint config.

Right, but it only lets you map it to the plugin. It will format it as an HTML file and not as a jinja-like template.


Add tests that objects are created in correct realms

When Javascript in multiple iframes interacts it becomes important to
distinguish which objects belong to which realm. Add tests that verify
that objects emitted by TextEncoder and TextDecoder streams were created
in the correct realm.

f9ab81ee97a34075917f2dd8381e745697458ba0 lgtm


Use the [params] tag for methods params

Hi !
I wanted to use vgram but the Config struct could not work unless their names were specified, so I used the [params] tag on every method that use Config struct to allow passing parameters more easily.
I hope it suits the project, I tested it locally and found no evident issues.

Yep, everything seems okay, thanks


Exposes gui_release_focus and gui_get_focus_owner to Viewport

Right now, if you want to release the focus from all control, you have to:

find a random Control node in the tree,
call get_focus_owner().release_focus() on it.

As it makes little sense to either need a random control to access the currently focused node, or to need access the currently focused node to remove its focus, I implemented this PR.
It exposes two functions in Viewport's API: gui_get_focus_owner  which returns the currently focused control in the Viewport and gui_release_focus, which unfocus any focused node (if there is one).
I tested both, they seem to work fine. It's not a lot of changes anyway, most of those function were already present but not exposed.

Ah I forgot to mention, but while I am at it, maybe we should remove the release_focus() and get_focus_owner() from Control?
For release_focus(), I can't really find a use case where you would need to release the focus from a specific node, so I think the more generic Viewport.gui_release_focus() covers the most most common use case. With the PR, Control.release_focus() could be easily replaced by this snippet:
if has_focus():
    Viewport.gui_release_focus()

But I don't really see a use case for it TBH.
For gui_focus_owner(), it's more like it's not something that really belong to the Control node API. It might be a helper, but Viewport.get_focus_owner() seems more adequate in general. I feel like Control.gui_focus_owner() makes it look like the focus owner is kind of dependent on the Control node itself, while it's something global to the Viewport.

They may be awkward, but I don't think they are harmful. You would normally use any of them in a script that extends Control anyway, so it saves a few keystrokes. I wouldn't support adding them, but since they are already here, I don't think it's too important to remove them.

You would normally use any of them in a script that extends Control anyway, so it saves a few keystrokes

Well, I don't think that's true. It's the first time I need this, and it is in a 3D scene.
In fact, it is specifically because I am not in a Control node's code that I needed to release the focus (in my case a Tree node was preventing me from catching some events on a 3D node, so I needed to make it release the focus)
I may agree to keep get_focus_owner(), but I really don't think this is something you would need more often in a Control node's code than any other node. This function, like the release_focus one, are returning a very global and generic thing. There's no real reason, IMO, why it should be in the Control API and not in the Node or the Viewport on, if you see what i mean.

It's a global thing, but it's a thing that is related only to controls, as only controls can have focus. I'm not sure what the use case is for working with focus outside of control nodes, but I believe you that you have one. I have plenty of uses for them in controls though, and release_focus() works as a nice pair for grab_focus() when scripting. I've also used get_focus_owner() to check if the current control is the focus owner plenty of times. Those are more direct use cases for them than doing something with focus outside of nodes, that have any concept of focus at all.
And I think it's notable that these methods existed as Control-exclusive all this time and only now have you found a use for it to be accessible outside of controls. Like I've said, if they didn't exist on Control already, I wouldn't argue in their favor, but we have them and they are useful mostly with controls in my experience, so it makes sense to keep them.

For that you have the Control.has_focus() function, which is a lot more adequate.

True, and I have less strong feelings towards get_focus_owner() anyway.

So I guess the consensus could be:

Remove Control::get_focus_owner()
Keep Control::release_focus()?

I agree that the actual implementation detail of release_focus make it seem a bit useless, as only one Control can have focus anyway. But I see @pycbouh's point that Control is likely the most natural place to look for for focus-related interactions, and mycontrol.release_focus() as an echo to mycontrol.grab_focus() does make sense somewhat.

So I guess the consensus could be:
Remove Control::get_focus_owner()
Keep Control::release_focus()?

Yeah, seems like it is. Should I update the PR right away or create another one?

I'd say you can update this one if it's just removing get_focus_owner.

Thanks!


2.0.3 rebuild Apk file becomes mush larger than 2.0.2!!!!!

on my mac
$ du -sh  123.apk
7.9M	123.apk
$ ./apktool --version
2.0.2
$./apktool d -f 123.apk -o 123
$./apktool b 123 -o 456.apk
$ du -sh 456.apk
7.8M	456.apk
$ ./apktool --version
2.0.3
$./apktool d -f 123.apk -o 123
$./apktool b 123 -o 789.apk
$ du -sh 789.apk
14M	789.apk

I think it's fixed in master branch. Just try this apktool - https://github.com/iBotPeaches/Apktool/files/103614/apktool.zip

thanks, but  my apk rebuild by 2.0.2

But Resulting apk file by 2.0.2 is a little smaller(24k in my case) than original.
Resulting apk file by 2.1.0-114af9-SNAPSHOT https://github.com/iBotPeaches/Apktool/files/103614/apktool.zip is a little larger(36k in my case) than original.
And:
The FAQ http://ibotpeaches.github.io/Apktool/documentation/#faq says:
Resulting apk file is much smaller than original! Is there something missing?
There are a couple of reasons that might cause this.
Apktool builds unsigned apks. This means an entire directory META-INF is missing.
New aapt binary. Newer versions of apktool contain a newer aapt which optimizes images differently.
These points might have contributed to a smaller than normal apk

There is no way to maintain a perfect 1-1 size ratio between original and rebuilt. The application naturally runs through aapt compression, dex assemble/disassemble and a full reconstruction of the resources.arsc file.
If you want to investigate and find the files that are differing then we might be able to look if this a bug or just naturally effect of using apktool.


add date to generated dtbo rpm

this will allow to update dtbo image accordingly

fixed by https://github.com/sailfishos-sony-tama/droid-hal-img-dtbo-sony-tama-pie/commit/fc4abc23ba7426c7f8cad2b0ebd2fc513d07cabb


Search improvement

Hi
I've an idea -
could you add a shortcuts for searching through the current decompiled code please?
use case:
Ctrl+F  - type text - start searching
then press F3 to continue searching next value and Shift +F3 to search backwards?
would be very handy I guess
thx!

???

Opens

OK, more details on idea
existing CTRL+F = OK
proposal is to add 2 more key combinations: F3 + SHIFT-F3 (when the find dialog will be closed)
these 3 keys should do the searching in direct or reverse direction
This is common practice and most SW having it...
just a plus to the user experience, what do you think?

Hmm so kind of like Registry Explorer... Actually that would be pretty cool.

Exactly!  most SW uses these search shortcuts and experienced users will say you a big thanks, no doubt! (including me 10 time :)

It'll be in the next build.


[BugFix] Fix mv may not completely refresh when create with property partition_refresh_number.

What type of PR is this：

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #21419
Problem Summary(Required) ：

Metadata for other tables only refresh when last task execute success.
Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto backported to target branch

[x] 3.0
[x] 2.5
[ ] 2.4
[ ] 2.3

@Mergifyio backport branch-2.5


Drawer has unnecessary omitObject

Which package has an issue?
@yamada-ui/react
Package Version
1.3.7
Description
Integrate omitObject handling with omitThemeProps.
const {
  children,
  isOpen,
  onClose,
  onOverlayClick,
  onEsc,
  onCloseComplete,
  withCloseButton = !closeOnDrag,
  withOverlay = true,
  withDragBar = true,
  allowPinchZoom,
  autoFocus,
  restoreFocus,
  initialFocusRef,
  finalFocusRef,
  blockScrollOnMount,
  closeOnOverlay,
  closeOnEsc,
  lockFocusAcrossFrames,
  duration = { enter: 0.4, exit: 0.3 },
  dragConstraints = 0,
  dragElastic = 0.1,
  dragOffset = 80,
  dragVelocity = 100,
  blankForDragProps,
  portalProps,
  ...rest
- } = omitThemeProps(mergedProps)
+ } = omitThemeProps(mergedProps, ["isFullHeight"])

<DrawerContent
  {...{
    dragConstraints,
    dragElastic,
    dragOffset,
    dragVelocity,
    withCloseButton,
    withDragBar,
    blankForDragProps,
-     ...omitObject(rest, ["isFullHeight"]),
+     ...rest
    placement,
    closeOnDrag,
  }}
>

Link to Reproduction
No response
Steps to Reproduce

Go to '...'
Click on '...'
Scroll down to '...'
See error

Browser
None
Operating System

[ ] macOS
[ ] Windows
[ ] Linux

Do you know how to fix the issue?
Yes
Are you willing to participate in fixing this issue and create a pull request with the fix?
None
Additional Information
No response

I would like to challenge this issue.

@hirotomoyamada
Hi, thanks for the comment.
Yes, pls.
I'll assign this issue to you.


Not working 4.7-Navigate_To_menu_related_files.html

Summary

Not working 01-Navigation/4-Contextual_navigation/4.7-Navigate_To_menu_related_files.html
When I followed the instructions and executed the "Navigate to (Ctrl+Shift+G)" shortcut in the HTML comment, nothing responded.
I want to see what your expectations are.

Glance at the problem code
<!DOCTYPE html>
<html>
<head>
    <title>Navigate To menu - related files</title>

    <!-- Navigate To menu

         Displays a contextual menu of options you can use to navigate to from
         your current location

         Very useful way of navigating without having to learn ALL of the shortcuts!

         <shortcut id="Navigate To...">Alt+`</shortcut>

         1. Navigate to related files. E.g. referenced files from HTML
            Put text caret here →
            Navigate to Related Files shows list of other files containing definitions of PartialClass
        -->
    <script type="text/javascript" src="ExampleCode/script1.js"></script>
    <script type="text/javascript" src="ExampleCode/script2.js"></script>
    <script type="text/javascript" src="ExampleCode/script3.js"></script>

    <link rel="stylesheet" type="text/css" href="ExampleCode/style1.css">
    <link rel="stylesheet" type="text/css" href="ExampleCode/style2.css">
    <link rel="stylesheet" type="text/css" href="ExampleCode/style3.css">
</head>
<body>

</body>
</html>

Environment

Rider 2021.1.2
Keymap : Default IntelliJ Style

That's a ReSharper-only feature in this file. You could try this one in Rider:
         <shortcut id="Navigate To Related Symbol">Ctrl+Alt+F7</shortcut> (Rider Visual Studio keymap)

Just updated the file in git.

Thank you for your confirmation, @maartenba .
However, I don't correct this case yet.

         <shortcut id="Navigate To Related Symbol">Ctrl+Alt+F7</shortcut> (Rider Visual Studio keymap)

You described it as "Navigate to related files (Ctrl+Alt+F7)", but it is assigned to "Show usages" and will not work in this workshop.
Show usages (Ctrl+Alt+F7) in Navigate from symbols

I have attached a recording of the error I get when I run "Show usages (Ctrl+Alt+F7)" in this workshop.

Do you get a different result in your environment?

I use the VS keymap in Rider, can you check this action name/shortcut in your keymap?

I was able to solve it.
There were two problems here.

The key assignment on the web help page is wrong: Ctrl+Alt+F7 is assigned to Show usages in Rider Visual Studio style (as explained above).
In my environment, I was using Rider IntelliJ style. As you pointed out. Thanks.

As we discussed here before, I think it would be better to unify to post IntelliJ style in Rider workshop.
So I'll put out a revised commit in PR after.
Thanks, @maartenba .


Tidy Up Makefile

It's currently a bit of a bad hack.

No longer relevant as of https://github.com/mbedded-ninja/MFixedPoint/releases/tag/v6.0.0.


at-function-named-arguments for function in map

"scss/at-function-named-arguments": "never"

Like a following patterns are expected no errors, but errors.
$color: #123456;

$rgb: (
  "r": red($color),
  "g": green($color),
  "b": blue($color)
);

Pull request with a fix:
https://github.com/kristerkari/stylelint-scss/pull/290

Released the fix with 3.4.1:
https://github.com/kristerkari/stylelint-scss/releases/tag/3.4.1


[BEAM-2625] Update pull request template for mergebot world

Follow this checklist to help us incorporate your contribution quickly and
easily:

[x] Make sure there is a JIRA issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes.
[x] Each commit in the pull request should have a meaningful subject line and body.
[x] Format the pull request title like [BEAM-1234] Fixes bug in ApproximateQuantiles, where you replace BEAM-1234 with the appropriate JIRA issue.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

One the modes of operation of the impending mergebot - actually, the simplest mode - is to merge commits exactly as they appear in the pull request. Our instructions don't give great guidelines here, and they include steps that actually are handled by automation. This is a proposed revision to get better commits and PR descriptions.
I've edited this description to match.

@jasonkuster and @robertwb somewhat inspired by our email thread

Coverage decreased (-0.003%) to 70.622% when pulling 48c1151e1002ae5dc18904db23189c1fca6c9468 on kennknowles:pr-template into 7e4719cd01f412c000bab61f99c687ab5c5491cc on apache:master.

Coverage increased (+0.007%) to 70.632% when pulling 48c1151e1002ae5dc18904db23189c1fca6c9468 on kennknowles:pr-template into 7e4719cd01f412c000bab61f99c687ab5c5491cc on apache:master.

LGTM, though I think it'd still be good to instruct users that all tests should pass (which will of course be checked automatically, but that allows users to more easily do "fire and forget" PRs.

Added back the bit about running tests


Make internal methods async

If ActorToken is not valid, return.

Missing unit test to prevent a regression?

opened issue https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/issues/1991


Applies to Information

[Enter feedback here]
Please update the pages to clearly call out the pages that apply to O365 CAS. Every page states that it applies to MCAS, none of them mention O365 CAS.
This is the only page that discuses the differences and its very easy to read the other documentation and mistakenly think that it can be done with an O365 CAS license

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

ID: 76a66643-56f5-dc00-5af6-3ee1d9b6f090
Version Independent ID: c319c4a4-974e-7e3a-d58a-76fd57a9efe9
Content: Differences between Cloud App Security and Office 365 Cloud App Security
Content Source: CloudAppSecurityDocs/editions-cloud-app-security-o365.md
Service: cloud-app-security
Product: ****
Technology: ****
GitHub Login: @shsagir
Microsoft Alias: shsagir

@DeanGross Thanks so much for taking the time to leave us your comment on our documentation. We're researching your issue to update the page based on your suggestions. If relevant, changes will be made in the next possible publish.
You may find the following of interest:

What are the differences between Microsoft Cloud App Security and Office 365 Cloud App Security?
Microsoft Cloud App Security licensing datasheet

We're closing this as an open issue for now, but feel free to continue to comment here as necessary. We appreciate your contribution to our community.

Thanks, I am aware of those documents, my point is that at the top of each page is shown, "Applies to" and all of the pages show Microsoft Cloud App Security, and none of them show "Office 365 Cloud App Security" it would be helpful to explicitly identify the pages that apply to both licenses and to identify which pages only apply to the more expensive and comprehensive version


Allow to add "application/x-www-form-urlencoded" as "Content-Type" header

I'm trying to generate a resource that consumes application/x-www-form-urlencoded. I'm expecting Jane OpenApi add this value ad Content-Type header. But not.
After a quick exploration, I think the issue is coming from this file: https://github.com/janephp/openapi/blob/3dbc461442c6001d0993703b984fb8bbb445173f/src/Generator/InputGeneratorTrait.php#L288

@welcoMattic: Have a look at https://github.com/20steps/uptime-robot-bundle/blob/master/UptimeRobotAPI.php for an example to auto-inject headers and parameters into the HTTP client that is consumed from janephp/openapi.


Create dataset loader for WIT

Dataloader name: wit/wit.py
DataCatalogue: http://seacrowd.github.io/seacrowd-catalogue/card.html?wit

Dataset
wit

Description
Wikipedia-based Image Text (WIT) Dataset is a large multimodal multilingual dataset. WIT is composed of a curated set of 37.6 million entity rich image-text examples with 11.5 million unique images across 108 Wikipedia languages. 9 languages are spoken in Southeast Asia region

Subsets
-

Languages
ceb, fil, ind, jav, zlm, mya, tha, vie, war

Tasks
Image-to-Text Generation, Text-to-Image Generation

License
Creative Commons Attribution Share Alike 3.0 (cc-by-sa-3.0)

Homepage
https://github.com/google-research-datasets/wit/blob/main/DATA.md

HF URL
https://huggingface.co/datasets/google/wit

Paper URL
https://dl.acm.org/doi/abs/10.1145/3404835.3463257

#self-assign

#self-assign

#self-assign

#self-assign

Unnecessary commits have been removed, PR ready.


Use EnumDistriminants to derive Socket and Channel Status from their listener State

I don't want to expose State. It is an implementation detail and has fields I don't think should be exposed.

Fair enough. The EnumDiscriminants macro can be used to derive Status from State and with the conversions
Originally posted by @Bajix in https://github.com/liveview-native/phoenix-channels-client/issues/24#issuecomment-1592137921

EnumDiscriminants doesn't allow us to use repr(usize) on the derived enum, so we can't do the AtomitcUsize trick.  We also can't have a Status::ShutDown without an accompanying State::ShutDown, which is unnecessary, since the Status::ShutDown is set only at the end of socket::listener::listen before it returns.

EnumDiscriminants doesn't allow us to use repr(usize) on the derived enum, so we can't do the AtomitcUsize trick. We also can't have a Status::ShutDown without an accompanying State::ShutDown, which is unnecessary, since the Status::ShutDown is set only at the end of socket::listener::listen before it returns.

What about like this using #[strum_discriminants(repr(usize))]
#[derive(FromRepr, EnumDiscriminants, EnumIter, EnumIs)]
#[strum_discriminants(name(State))]
#[strum_discriminants(repr(usize))]
#[strum_discriminants(derive(EnumIter, EnumIs))]


Prevent crash upon clicking on member panel button (VisualScript Editor)

I detected this crash while using recording software (ScreenToGif) on overlay upon Godot - if its window has focus and you click any of these buttons:
 the editor will crash. After this fix, it will not crash but the user still needs to focus Godot editor window (and press again).

Hmm, the problem seems global and affects other buttons. I've better create an issue about it and close this PR since it's only a one-case hotfix.

Hmm, the problem seems global and affects other buttons. I've better create an issue about it and close this PR since it's only a one-case hotfix.


Spend more time on batch size for storage

v5 gave the needed performance boost for searches. However, one of the things I am not happy with is the hardcoded batch size while storing a group of records.
https://github.com/AppThreat/vulnerability-db/blob/master/vdb/lib/storage.py#L9
I picked this number out of thin air. Bad hotel internet means I could never experiment with various batch sizes to measure the impact on storage vs. search performance.

@prabhu So I've been looking into this. My observations either mean the batch size is relatively inconsequential or else that I don't know what I'm doing. Probably the latter.

@cerrussell This is interesting! Do you have any idea where the time is being spent? Can we try any profiler?

@prabhu I've been using cProfile and playing around with different decorators. Also looking at how other projects set things up. It's all very new to me, but I certainly welcome the opportunity to remedy this knowledge gap. I'm working on setting up a workflow in GA that can take test projects and run depscan with profiling. I'll let you know when I've come up with anything worth looking at!

Thanks, @cerrussell, for your help. Please join the discord channel as well, in case you haven't. I would love to know more about your workflows.

Hey @prabhu , I joined the discord.
Just an update. I've been testing out batch_write_size values. I'm still working out what the value is that will yield a net improvement rather than simply redistributing where time is spent.

@cerrussell, could you kindly say hi on discord or share your discord id? Looks like a few people have joined.

@prabhu My ID is lemonym#2286, display name caroline.


Vault issue when using pipe (multiline)

Issue
Not able to fetch Vault secrets when using pipe multiline

values.yaml.gotmpl (WORKING)

certValue: {{ "ref+vault://{PATH}#certificate" }}

values.yaml.gotmpl (NOT WORKING)

certValue: |
{{ "ref+vault://{PATH}#certificate" | indent 2 }}

---

in ./helmfile.yaml: in .helmfiles[0]: in ./helmfile.yaml: failed processing release client-cert: failed to render values files "certs/client-certificate/values.yaml.gotmpl": expand vault://{PATH}#certificate
: no value found for key certificate

Info

Helm

Client: &version.Version{SemVer:"v2.14.3", GitCommit:"0e7f3b6637f7af8fcfddb3d2941fcc7cbebb0085", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.14.3", GitCommit:"0e7f3b6637f7af8fcfddb3d2941fcc7cbebb0085", GitTreeState:"clean"}

Helmfile

helmfile version v0.139.9

Vault

1.3.1

Tried so many variations but no success and then I ran out of ideas, if this is a known issue and it should behavior like that maybe I will need to change the chart itself.
Any help is really appreciated.
Thank you.

I'm also running into a similar issue, when trying to use inside tpl
data:
    .env.schema: |
      {{- tpl (readFile "config/schema.txt") . | indent 6 }}

Where the config/schema.txt contains a line that states:
AUTH_CLIENT_SECRET=ref+vault://secret/PATH#/oauth-client-secret

The error returned is:
AUTH_CLIENT_SECRET=ref: no value found for key oauth-client-secret
While we can use vault kv get --field=oauth-client-secret secret/PATH and it returns the value just fine

I've stumbled upon this problem before, and after checking the regex used in vals, I discovered that you can add a "?" at the end of your URI to tell vals that it is the end of the string, otherwise it will read until the end of the string, and can even add newlines.
You should try to use ref+vault://{PATH}#certificate?

Actually it's not ? but +, my bad. See https://github.com/variantdev/vals/issues/13

We've finally fixed the original issue of not trealing a new-line character as the expression end, and updated the documentation with a full explanation on our expression syntax, so that everything reported by @cferrera @gmenuel is now covered.
Thanks both for your support!


Bump Lightning and PennyLane minimum versions (v0.37)

@rauletorresc you should also install pennylane before installing Catalyst

   - name: Install Catalyst
      run: |
        python${{ matrix.python_version }} -m pip install $GITHUB_WORKSPACE/dist/*.whl --extra-index-url https://test.pypi.org/simple

Here, I think you need to use --no-deps to install catalyst without dependencies and then you can install pennylane from RC here. Or the other way around. Install pennylane RC before hitting this line.


From what game does the screenshot come from ?

The graphics and program itself were just meant as a demonstration of the framework, limited in scope to what is shown in the gif as opposed to being an actual game.

Could you please share the source code ?


Verdaccio authentication using customized database,MYSQL

Is your feature request related to a problem?
Hi all, I'm struck with the situation that , I need to authenticate the verdaccio using my MYSQL database.
Describe the solution you'd like
Is there any plugin or any other way to achieve this
Additional context
Thanks in Advance

As far I know there is no plugin, but you could built one :) and share it.

Oh... Okay thanks @juanpicado


genlisp: 0.4.16-0 in 'lunar/distribution.yaml' [bloom]

Increasing version of package(s) in repository genlisp to 0.4.16-0:

upstream repository: git@github.com:ros/genlisp.git
release repository: https://github.com/ros-gbp/genlisp-release.git
distro file: lunar/distribution.yaml
bloom version: 0.5.23
previous version for package: null

@airballking FYI


Runtime exited without providing a reason

Describe the bug
While sample code of syncLambda runs properly. Sample code for asyncLambda: AsyncCodableLambda throws following error

aws lambda invoke --function-name HelloWorld --profile default --payload "fileb://Examples/HelloWorld/event.json" ./.build/tmp/outfile && echo "\nResult:" && cat ./.build/tmp/outfile && echo "\n"
{
"FunctionError": "Unhandled",
"ExecutedVersion": "$LATEST",
"StatusCode": 200
}

Result:
{"errorType":"Runtime.ExitError","errorMessage":"RequestId: 3278a4df-68cb-45d0-afe9-8870a675dae5 Error: Runtime exited without providing a reason"}
To Reproduce
Steps to reproduce the behavior:
Clone this repository and change following line
//    sprinter.register(handler: "helloWorld", lambda: syncLambda)
//    sprinter.register(handler: "helloWorld2", lambda: syncDictLambda)
//    sprinter.register(handler: "helloWorld3", lambda: asyncLambda)
    sprinter.register(handler: "helloWorld4", lambda: asyncDictLambda)

Inside Example/HelloWorld/Sources/HelloWorld/Main.swift
Follow all the steps to make docker build, layer, lambda from terminal
Run make invoke_lambda
Expected behavior
Sample code given in asyncDictLambda: AsyncDictionaryLambda or asyncLambda: AsyncCodableLambda should run without any error
Desktop (please complete the following information):

OS:  MacOS 10.14.4

I am trying to make postgres connection in lambda . I can successfully make connection in syncLambda with following code
let syncLambda: SyncCodableLambda<Event, Response> = { (event, context) throws -> Response in
    let group = DispatchGroup()
    group.enter()
    let connection = PostgreSQLConnection(host: "poc-database-1.cy0b4mwsn310.eu-west-1.rds.amazonaws.com", port: 5432, options: [ConnectionOptions.databaseName("df_content"),ConnectionOptions.password("DET.POC.123"),ConnectionOptions.userName("postgres")])
    print("code is updated now")
    print(connection)
    connection.connect() { result in
        group.leave()
    }
    group.wait()
    let message = "Hello 3 World! Hello \(event.name)! Pool is \(connection.isConnected)"
    return Response(message: message)
}

The same code without dispatch group doesn't work in
let asyncLambda: AsyncCodableLambda<Event, Response> = { event, _, completion in
...

To troubleshoot your code i suggest to use the function log() as implemented in HelloWorld.
Unhandled - The runtime didn't handle the error. For example, the function ran out of memory or timed out.
Are you sure the db is reachable from the Lambda?
Which library did you use?
Does the package use NIO 2.0 or libCURL? Note that libCURL is not supported.

For AsyncCodableLambda you need to call the completion handler. Can you provide the code?
Are you sure the db is reachable from the AWS Lambda?
You need to be sure that the Postgres library you are using is based on SwiftNIO 2.0.

Hi,
I am using HellowWorld Example's sample code only for AsyncLambda ... Just one line of change in main.swift
sprinter.register(handler: "helloWorld4", lambda: asyncDictLambda)
uncommented above line and commented syncLambda line

just to clarify any confusion. It has nothing to do with Database connection or anything. It's the default code that is given in the main.swift file for asyncLambda i am referring to.
Thanks

@mihirpmehta Have you registered the Handler HelloWorld.helloWorld4 ?
If not you can just reuse the one you have registered:
sprinter.register(handler: "helloWorld", lambda: asyncDictLambda)

Oh. I miss it. I didn't change it in makefile. Thanks a ton


[PL] add lesson basics translation

Add translation of first lesson ,

This is awesome @Koziolek!  @kdebowski can you take a look at this when you have a moment?

@Koziolek great job! I've added some notes. There are really few small typos.
@doomspork after correcting few typos it will be ready to merge

Fixed typos.

@doomspork this is ready to go :)

Awesome @Koziolek!  Thank you @kdebowski for the feedback


Can't turn Grohe valve On/Off

Hi !
Havn’t been active with Grohe and Homebridge for a while but after an overall update i couldn’t turn the valve on/off anymore.
Using the Home app, turning the ”Grohe valve” Off, it just responds ”Stoppar..”(Swedish, for stopping) and the valve never closes. In the HB GUI it goes from ”Running” to ”Off”.
In the HB GUI I have activated the debug mode for HB and also in the Ondus app the SHTF mode despite this nothing is written in the HB log at the moment I turn the valve off ?
Check log below
HB is running on an updated RPi 2 with HB 1.3.5, Node.js v14, and the Home hub is Appple TV with OS 15.0
Any ideas ?
[Grohe/Ondus] Initializing Ondus platform...
[18/10/2021, 10:22:33] [Grohe/Ondus] Config settings:
[18/10/2021, 10:22:33] [Grohe/Ondus]    name : Grohe/Ondus
[18/10/2021, 10:22:33] [Grohe/Ondus]    valve_control : true
[18/10/2021, 10:22:33] [Grohe/Ondus]    refresh_token :
[18/10/2021, 10:22:33] [Grohe/Ondus]    refresh_interval : 29750
[18/10/2021, 10:22:33] [Grohe/Ondus]    throttle_support : false
[18/10/2021, 10:22:33] [Grohe/Ondus]    throttle_rate : 6
[18/10/2021, 10:22:33] [Grohe/Ondus]    throttle_rateper : 1000
[18/10/2021, 10:22:33] [Grohe/Ondus]    throttle_concurrent : 2
[18/10/2021, 10:22:33] [Grohe/Ondus]    fakegato_support : true
[18/10/2021, 10:22:33] [Grohe/Ondus]    shtf_mode : true
[18/10/2021, 10:22:33] [Grohe/Ondus]    platform : Ondus
[18/10/2021, 10:22:33] [Grohe/Ondus] Initializing Ondus API session
[18/10/2021, 10:22:33] [Grohe/Ondus] refreshToken:  eyJhbGciOiJIUzI1NiI…..
[18/10/2021, 10:22:33] [Grohe/Ondus] Finished initializing platform: Grohe/Ondus
[18/10/2021, 10:22:33] [Grohe/Ondus] Loading accessory from cache: MITT GUARD
[18/10/2021, 10:22:33] [Grohe/Ondus] Executed didFinishLaunching callback
[18/10/2021, 10:22:33] [Grohe/Ondus] Fetching Ondus devices
[18/10/2021, 10:22:33] [Grohe/Ondus] Using refresh token to retrieve access token
[18/10/2021, 10:22:34] [Grohe/Ondus] OAuth access token successfully refreshed - token will expire in 3600 seconds
[18/10/2021, 10:22:34] [Grohe/Ondus] Function refreshAccessToken() successfull: HTTP_STATUS_CODE=200
[18/10/2021, 10:22:34] [Grohe/Ondus] Scheduling access token refresh in 3600 seconds
[18/10/2021, 10:22:34] [Grohe/Ondus] Ondus API login() successful
[18/10/2021, 10:22:34] [Grohe/Ondus] getLocations(): Retrieving locations
[18/10/2021, 10:22:34] [Grohe/Ondus] getURL(): GET:  https://idp2-apigw.cloud.grohe.com/v3/iot/locations

Try v1.5.1, make sure throttle support is enabled in the config.

Hi and thanks !
O yes that solved the problem.
Have a nice Easter🐣
/Mats


Pundit Switch

Remove CanCanCan and replace it with Pundit.
Benefits:

Pundit has much less magic happening
Pundit is more extendable and scopeable
Pundit is easier to read and understand the flow
Pundit will remove a lot of crude code for permissions in previous version

Transition is complete and test pass. Will be reviewing code and testing locally to ensure I want to publish.

Moved granting into a model concern to DRY up some code and make it more organized. Support for namespaces is added in as well for resources on permissions.

Added policy tests and removed unused code from old CanCanCan install.

All tests pass... at the surface I see no issues. Will merge this and continue to test and adjust any issues that arise.


add spike-equivalence test

Quantifying to what degree the exact times of the individual spikes in two datasets differ.
This could be used to compare spike sortings of the same raw data or could serve as the initial test for any comparison to exclude the trivial scenario of identical data sets.
In comparison to a reference recording, each spike can be evaluated as

False Negative (spike is missing)
True Positive (spike exists and is attributed to the same unit)
Misclassified (spike exists but is attributed to another unit [may require channel information])
False Positive (extra spike) [= False Negative if there is no reference and the two samples are equally legit]

http://www.scholarpedia.org/article/Measures_of_spike_train_synchrony
Is it necessary that both datasets have the same number of units?

Hierarchy of tests: same number of units; same number of spikes; same timing of spikes

Once you get to single neuron (unit) measures, you could consider using the tests (or subclasses thereof) in neuronunit here.  We have actually not written tests that look for equivalence of spike trains, preferring to look for equivalence of spike train statistics, but if you look at ISITest, for example, you'll see the basic logic of getting the spike train and doing computations on it.


Redirect from existing pages to new site

https://www.netlify.com/docs/redirects/

Also useful https://gohugo.io/content-management/urls/#aliases

See also #15 (maybe that can be closed as a duplicate?)

Duplicate of #144


Failed to get properties for blob item.

Preflight Checklist

[X] I have installed the latest version of Storage Explorer.
[X] I have checked existing resources, including the troubleshooting guide and the release notes.
[X] I have searched for similar issues.

Storage Explorer Version
1.21.3
Regression From
No response
Architecture
i86
Storage Explorer Build Number
20211020.2
Platform
Windows
OS Version
Windows 11
Bug Description
Storage explorer fails to display properties for any blob item.
Steps to Reproduce

Launch storage explorer
Select any blob item and right-click
Select 'properties' from the context menu

Actual Experience

Activities pane displays message "Getting properties for '<id>'"
Times out after about a minute
Activities pane displays message "Failed to get properties for '<id>'"

Expected Experience
Popup dialog showing properties for the selected blob item.
Additional Context
No response

@johnholliday

When the activity times out, is there something like a "Details..." or "Error details..." that you can click on? If yes, please click on that and share the error that appears.
Could you do:

Start Storage Explorer
Reproduce the problem
Help > Open Logs Folder
In the file explorer window that opens, open the newest log folder
Look for a file with "blob" in its name
Share that file here

Are you able to view properties of the blobs this issue reproduces for via the Azure Portal?
Are you behind a proxy/is there anything special about the network you are on?

Closing due to lack of response. If you are still having problems, we suggest opening an Azure support ticket via the portal.


Support for transport socket matching on locality metadata

This patch adds a metadata field to the locality configuration. The new field can be used to perform transport socket matching for all endpoints in a locality:
  load_assignment:
    cluster_name: example_cluster
    endpoints:
    - locality:
        metadata: # <----- This is new.
          filter_metadata:
            envoy.transport_socket_match:
              network.id: vpc-1
      lb_endpoints:
      - endpoint:
          address:
            socket_address:
              address: <IP_ADDRESS>
              port_value: 11337
      - endpoint:
          address:
            socket_address:
              address: <IP_ADDRESS>
              port_value: 11337

Notice the ability to add metadata to the locality. The transport socket matcher will still check the envoy.transport_socket_match metadata for an endpoint, but now if there is no match it will look at that field in its locality's metadata. This essentially allows one to set a transport socket match for groups of endpoints with a single metadata field, which can significantly improve scalability for deployments with many endpoints as shown in https://github.com/envoyproxy/envoy/issues/34530.
Risk Level:
Low?
Testing:
New unit tests, improvement to old unit tests, and manual verification.
Fixes:
https://github.com/envoyproxy/envoy/issues/34530

/retest

/retest

Failure is due to CI infrastructure:
##[error]We stopped hearing from agent i-0beef2ff7b659d227. Verify the agent machine is running and has a healthy network connection. Anything that terminates an agent process, starves it for CPU, or blocks its network access can cause this error. For more information, see: https://go.microsoft.com/fwlink/?linkid=846610
Agent: i-0beef2ff7b659d227
Started: Today at 11:50 AM
Duration: 2h 8m 31s

/retest

This is core API change and kind ping @markdroth for a review from non-Envoy xDS client's perspective.

/retest

LGTM. @ggreenway could we get a non-Google pass on this from you? Thanks.

/wait-any
Friendly ping @ggreenway  Thanks!

I think using wait-any is confusing, since we're waiting on a review and not some action on my part.

I think using wait-any is confusing, since we're waiting on a review and not some action on my part.

Yep; I didn't see this in my review queue because of the waiting label. I'll try to look at it today.

/lgtm api

/retest

/retest


Remove .DS_Store

Fixes issue #64

Codecov Report

Merging #65 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             master    #65   +/-   ##
=======================================
  Coverage       100%   100%
  Complexity       67     67
=======================================
  Files             7      7
  Lines           166    190   +24
=======================================
+ Hits            166    190   +24

Impacted Files
Coverage Δ
Complexity Δ

src/Exception/ResourceNotImplemented.php
100% <0%> (ø)
1% <0%> (ø)
:arrow_down:

src/RestPool.php
100% <0%> (ø)
8% <0%> (ø)
:arrow_down:

src/RestResource.php
100% <0%> (ø)
10% <0%> (ø)
:arrow_down:

src/Auth/BasicAuth.php
100% <0%> (ø)
3% <0%> (ø)
:arrow_down:

src/Auth/BearerAuth.php
100% <0%> (ø)
3% <0%> (ø)
:arrow_down:

src/Exception/InvalidRoute.php
100% <0%> (ø)
1% <0%> (ø)
:arrow_down:

src/RestClient.php
100% <0%> (ø)
41% <0%> (ø)
:arrow_down:

Continue to review full report at Codecov.

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


Firestore sample error - forEach is not a function

Hi, I tried setup the firestore sample but not works, I have the following error:
FriendlyEats.Data.js:37 Uncaught TypeError:
snapshot.docChanges.forEach is not a function

Weird... https://firebase.google.com/docs/firestore/query-data/listen#listen_to_multiple_documents_in_a_collection Should work...

This was a change made in the Firestore SDK a while ago, updating to the latest version will make it work.


Ecobee weather tile does not show low temperature graph in correct units

Home Assistant release with the issue:0.68. and earlier*

0.68.* and earlier
Last working Home Assistant release (if known):
None, appeared as soon as the ecobee weather frontend was available
Operating environment (Hass.io/Docker/Windows/etc.):

Hass.io
Component/platform:

Ecobee / weather
Description of problem:
My ecobee is set to metric on the ecobee device itself, I live in the US and I have set home assistant to metric as well.
In the tile/frontend  the high temperature and the current temperature is shown in Celsius while the low temperature is shown in Fahrenheit.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
homeassistant:
  # Name of the location where Home Assistant is running
  name: Home
  # Location required to calculate the time the sun rises and sets
  latitude: !secret Home_latitude
  longitude: !secret Home_longitude
  # Impacts weather/sunrise data (altitude above sea level in meters)
  elevation: 56
  # metric for Metric, imperial for Imperial
  unit_system: metric
  # Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
  time_zone: America/Los_Angeles
  # Customization file
  customize: !include customize.yaml
.....
ecobee:
  api_key: !secret ecobee_key

Traceback (if applicable):

Additional information:
Customize.yaml has no further customization
I observed this in my previous setup, 0.68 messed up my zwave config, so I fresh installed 0.68.1 - same result in respect to ecobee weather tile. the state also reflects the wrong conversion as you can see the low temperature is above the high temperature. it seems to me at import the temperature is not converted correctly..
{
"temperature": 14,
"humidity": 77,
"pressure": 1022,
"wind_bearing": 259,
"wind_speed": 0,
"visibility": -5002000,
"attribution": "Ecobee weather provided by CW:32319 at 2018-05-04 05:02:15",
"forecast": [
{
"datetime": "2018-05-03 21:56:08",
"condition": "Cool.",
"temperature": 16,
"templow": 48.5,
"pressure": 1022,
"windspeed": -5002000,
"humidity": 77
},
{
"datetime": "2018-05-04 21:56:08",
"condition": "Cloudy. Cool.",
"temperature": 16,
"templow": 48.5,
"pressure": 1021,
"windspeed": 6890,
"humidity": 60
},
{
"datetime": "2018-05-05 21:56:08",
"condition": "Showers late. Mostly sunny. Mild.",
"temperature": 18,
"templow": 48.5,
"pressure": 1024,
"windspeed": 8570,
"humidity": 58
},
{
"datetime": "2018-05-06 21:56:08",
"condition": "Showers late. Cloudy. Mild.",
"temperature": 22,
"templow": 53.4,
"pressure": 1018,
"windspeed": 7270,
"humidity": 51
},
{
"datetime": "2018-05-07 21:56:08",
"condition": "Cloudy. Mild.",
"temperature": 21,
"templow": 51.6,
"pressure": 1016,
"windspeed": 7010,
"humidity": 47
}
],
"friendly_name": "My ecobee3"
}

closing, this is fixed with Hassio 0.69.1


typo delete CREATE-EXTERNAL-TABLE docs 1.2

Proposed changes
Issue Number: close #xxx

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

run buildall


Throw error with nesting

Enviroment:

"webpack": "^3.5.2",
"postcss-cssnext": "^3.0.0",
"postcss-loader": "^2.0.6",
"precss": "^2.0.0",
Webpack config:

test: /\.vue$/,
use: {
  loader: 'vue-loader',
  options: {
    extractCSS: true,
    postcss: [
      require('postcss-cssnext')(),
      require('precss')()
    ],
    loaders: {
      sass: 'vue-style-loader!css-loader!sass-loader?indentedSyntax=1',
      scss: 'vue-style-loader!css-loader!sass-loader'
    }
  }
}

write css:
.title {
  color: #2c3e50;
  font-size: 20px;
  font-weight: bold;
  margin-bottom: 6px;
  &:hover {
    background-color: #4fc08d;
  }
}

This code snipped work well with webpack, but throw error with electron-vue, Here is error message:
  ERROR in ./node_modules/css-loader?sourceMap!./node_modules/vue-loader/lib/style-compiler?{"vue":true,"id":"data-v-78145104","scoped":false,"hasInlineConfig":true}!./node_modules/vue-loader/lib/selector.js?type=styles&index=0!./src/renderer/components/LandingPage.vue
  Module build failed: TypeError: node.parent.after is not a function
      at module.exports (/home/snovey/Documents/my-electron/node_modules/postcss-nesting/lib/transform-nesting-rule.js:18:29)
      at module.exports (/home/snovey/Documents/my-electron/node_modules/postcss-nesting/lib/transform.js:16:3)
      at /home/snovey/Documents/my-electron/node_modules/postcss/lib/container.js:148:26
      at Rule.each (/home/snovey/Documents/my-electron/node_modules/postcss/lib/container.js:114:22)
      at Rule.walk (/home/snovey/Documents/my-electron/node_modules/postcss/lib/container.js:147:21)
      at /home/snovey/Documents/my-electron/node_modules/postcss/lib/container.js:150:32
      at Root.each (/home/snovey/Documents/my-electron/node_modules/postcss/lib/container.js:114:22)
      at Root.walk (/home/snovey/Documents/my-electron/node_modules/postcss/lib/container.js:147:21)
      at /home/snovey/Documents/my-electron/node_modules/postcss-nesting/index.js:9:24
      at LazyResult.run (/home/snovey/Documents/my-electron/node_modules/postcss/lib/lazy-result.js:274:20)
      at LazyResult.asyncTick (/home/snovey/Documents/my-electron/node_modules/postcss/lib/lazy-result.js:189:32)
      at LazyResult.asyncTick (/home/snovey/Documents/my-electron/node_modules/postcss/lib/lazy-result.js:201:22)
      at LazyResult.asyncTick (/home/snovey/Documents/my-electron/node_modules/postcss/lib/lazy-result.js:201:22)
      at LazyResult.asyncTick (/home/snovey/Documents/my-electron/node_modules/postcss/lib/lazy-result.js:201:22)
      at LazyResult.asyncTick (/home/snovey/Documents/my-electron/node_modules/postcss/lib/lazy-result.js:201:22)
      at LazyResult.asyncTick (/home/snovey/Documents/my-electron/node_modules/postcss/lib/lazy-result.js:201:22)
      at LazyResult.asyncTick (/home/snovey/Documents/my-electron/node_modules/postcss/lib/lazy-result.js:201:22)
      at processing.Promise.then._this2.processed (/home/snovey/Documents/my-electron/node_modules/postcss/lib/lazy-result.js:228:20)
      at Promise (<anonymous>)
      at LazyResult.async (/home/snovey/Documents/my-electron/node_modules/postcss/lib/lazy-result.js:225:27)
      at LazyResult.then (/home/snovey/Documents/my-electron/node_modules/postcss/lib/lazy-result.js:131:21)
      at loadPostcssConfig.then.config (/home/snovey/Documents/my-electron/node_modules/vue-loader/lib/style-compiler/index.js:58:8)
   @ ./node_modules/vue-style-loader!./node_modules/css-loader?sourceMap!./node_modules/vue-loader/lib/style-compiler?{"vue":true,"id":"data-v-78145104","scoped":false,"hasInlineConfig":true}!./node_modules/vue-loader/lib/selector.js?type=styles&index=0!./src/renderer/components/LandingPage.vue 4:14-310 13:3-17:5 14:22-318
   @ ./src/renderer/components/LandingPage.vue
   @ ./src/renderer/router/index.js
   @ ./src/renderer/main.js
   @ multi ./.electron-vue/dev-client ./src/renderer/main.js

Then I downgrading back to version 2.11.0, It works well.

Looks like it's a postcss-nesting issue according to the stack trace. Please see overthere.
Btw, you should load precss (non standard CSS) before cssnext.

.title {
  color: #2c3e50;
  font-size: 20px;
  font-weight: bold;
  margin-bottom: 6px;
  &:hover {
    background-color: #4fc08d;
  }
}

Sorry, I forget to say the above code snippet is write in ./src/render/components/LandingPage.vue file.
After change load precss before cssnext, version 2.11.0 throw the same error too.

Again, the stack trace show a problem in postcss-nesting so please open an issue to this repo.