GlusterFS in Pods that support geo-replication ? cross datacenter replication between two distinsctive zone

Hi i would like to know if GlusterFS in Pods support cross datacenter replication ?
I.E Have a pool of 3 gluster FS on Zone datacenter1 wich have sychnonous data replication between them and have another Zone datacenter 2 which has also 3 glsuterfs Pods which also has synchronous replication .
Now could we have asynchronous géo replication between Zone  ? or can we have Synchronous replication accross datacenter any latencies issues boundaries ?

I received confirmation from Redhat that Geo-Replication is supported with Containerized Native Storage keep up good work community.
https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.2/html/administration_guide/chap-managing_geo-replication

@mcousine Great that you found that! :) Can the issue be closed, then?

Yes
On jeu. 31 août 2017 à 16:45 Jose A. Rivera<EMAIL_ADDRESS>wrote:

@mcousine https://github.com/mcousine Great that you found that! :) Can
the issue be closed, then?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gluster/gluster-kubernetes/issues/333#issuecomment-326415667,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEMdt4SWZZkB_ntqzKhz3jlHkG9gVm6Cks5sdxtYgaJpZM4PHzv0
.

There is, literally, zero information in the docs on how to georeplicate a pod or a PC for that matter. Care to elaborate?


Duplicating CollisionShape2Ds causes them to set both of their shape's dimensions at once

Godot version:
3.2 alpha 3 and 3.1 stable
OS/device including version:
All
Issue description:
Occurs in Editor
When you duplicate a CollisionShape2D and change the size of one, they both get changed.
Steps to reproduce:
Create a CollisionShape2D, add a shape, duplicate it, modify the dimensions of it's shape and they both get changed.
Minimal reproduction project:
Linked CollisionShape2Ds Demo.zip

This is expected. Their Shape resource is shared, so to avoid this, you need to make it unique.

(Make Unique)


[KYUUBI #2495] [Improvement] clear logRoot dir in SparkJsonLoggingEventHandlerSuite

Why are the changes needed?

clear logRoot dir in SparkJsonLoggingEventHandlerSuite
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

Codecov Report

Merging #2497 (3b89c28) into master (93f13ef) will decrease coverage by 0.05%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #2497      +/-   ##
============================================
- Coverage     63.57%   63.52%   -0.06%
  Complexity       69       69
============================================
  Files           371      371
  Lines         17710    17710
  Branches       2358     2358
============================================
- Hits          11260    11251       -9
- Misses         5404     5411       +7
- Partials       1046     1048       +2

Impacted Files
Coverage Δ

...rg/apache/kyuubi/engine/trino/TrinoSqlEngine.scala
52.63% <0.00%> (-7.02%)
:arrow_down:

...rg/apache/kyuubi/engine/trino/TrinoStatement.scala
66.66% <0.00%> (-4.60%)
:arrow_down:

.../engine/spark/session/SparkSQLSessionManager.scala
79.76% <0.00%> (-1.20%)
: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 93f13ef...3b89c28. Read the comment docs.


[wip] set acl to allow the qemu user to access snc dir recursively

this fixes the following error on the snc job:
load /home/hudson/jenkins/workspace/eng-crc-snc-arm/crc-tmp-install-data/fcos-config.ign: Failed to open file "/home/hudson/jenkins/workspace/eng-crc-snc-arm/crc-tmp-install-data/fcos-config.ign": Permission denied

I think we are spending too much time for getting to more around acls issue where the documents around it also not clear, better to use the default directory for ign also like we are doing for qcow2. I put #667 to test out if that works for both internal and external CI.

with the latest changes, its working for both downstream CI and also for openshift CI


operator kubecost-operator (v2.4.10)

Cloud Workflow: Don't run this again. CSV has no directives. Highest version in channel wins, and this version disappears.


Plugins directory doesn't work

Windows 10. Quasar version 24.0.15
I downloaded quasar-mongodb-internal-plugin and quasar-web-assembly, put plugin into ./plugin/ directory.
Tried following commands
java -jar quasar-web-assembly.jar --content-path "PATH_TO_SD_PUBLIC" -p ./plugin/
java -jar quasar-web-assembly.jar --content-path "PATH_TO_SD_PUBLIC" -p ./plugin
java -jar quasar-web-assembly.jar --content-path "PATH_TO_SD_PUBLIC" -p "FULL_PATH_TO_PLUGIN_DIR"

Both told me that plugin directory does not exists (or it's a file)
Then I tried
java -jar quasar-web-assembly.jar --content-path "C:\Users\zimal\Projects\slam\public" --backend:quasar.physi
cal.mongodb.MongoDb\$=./plugin/quasar-mongodb-internal-assembly.jar

This worked but, I still can't mount mongodb. The error is
{ "error": { "status": "Invalid mount configuration.", "detail": { "reasons": [ "Unsupported filesystem type: mongodb" ] } } }

When you tried the FULL_PATH_TO_PLUGIN_DIR option, did you use Windows-style paths?

Oh, also, this could be somewhat related to @kRITZCREEK's issues with dynamic loading, reported here: #2797

@djspiewak I tried both

Ok so that's just broken then.

@cryogenian Can you do me a favor and try using --plugins rather than -p?

@djspiewak The same problem with --plugin
Honestly I'm a bit more concerned about --backend doesn't work

--plugins plural.  But yeah, --backend works but not on Windows.  See #2797.  Very definitely on my short-term todo list.

@cryogenian When you get a chance, can you test this again with the latest quasar?  I think everything is working now.

@cryogenian - can you confirm? So we can close this out?
Thanks

The issue remains with 24.4.1

@djspiewak -> fyi

I'll look into it.  @dugdun Can you confirm whether or not this works on Mac?  I can test relatively easily enough; just wondering if you already know.  @cryogenian Is it just that the -P option still isn't working, or is --plugins also not functional?

I am currently using the following command on my Mac to run Quasar 24.1.12 without issue:
java $(tr '\n' ' ' < ~/vmoptions.txt) -jar ~/quasar/quasar-web-assembly-24.1.12.jar -c ./quasar-config.json --plugins ~/quasar/plugins/24.1.12/ --content-path ./public/ -L /slamdata

Let me try pulling down a newer Quasar release to see if something broke. I'll also try with the -P option.

@dugdun Does -P work?  Or just --plugins?

Hmm.... Something weird going on. I just tried starting with Quasar 24.4.1 and trying to load a workspace and the orange spinner just sat there. I restarted with Quasar 24.1.12 (what I was using previously I thought) and tried load the workspace again and still just see the orange spinner. This is usually a sign that things are not going to work as once things start processing the spinner changes to black stating that the workspace is loading. Rolled back to Quasar 23.1.4 (before connectors broken out) and things are working without issue.
@djspiewak can we look at things on my system at some point today? I thought we had the --plugins option working at one point in time on my Mac.

I won't be in the office today, but I'll push this to the top of my stack.  It's entirely possible that something is very broken here.  I'll make sure things are working on both Mac and Windows.

OK. I just restarted with Quasar 24.4.1 and was able to get a very simple workflow to run under MongoDB 3.4. Trying to load another one right now, but it's just sitting there with the orange spinner. DevTools doesn't show anything trying to run after the initial call to /data/fs API call. I'll try looking at things on my end as well. It could be that I was running under the pre-connector split Quasar version, and not 24.1.12 like I originally though. 😦

Confirmed that dynamic loading is working just fine on mac (both with -P and --plugins), but not working on Windows.  Fixing.

Moving the discussion of this specific issue to #2797.  Please see that issue for more updates.


Buy, sell templates internally , bootstrap-business.js

Hi, how are you?
My suggestion, idea

I would like Bootstrap to go beyond the community, to be a community of companies and people interested in this sale process or buy of 'layouts, designs' inside Bootstrap and not outside of Bootstrap.
I could charge my services or support within Bootstrap. For example, I can be 'Web Designer Bootstrap' and not just a 'Wordpress Web Designer'.
So, what I'm talking about is an internal store and not external to the framework services.
Everything could go back to the community and thus improve the framework more and more.

Note

I believe the community with the 'gnu / linux / public / free ' software.  I believe should charge services of the software. And... so. My thought is... It may be easy to have several people interested in something and charge for it. Than to sell a product.

I do not know if people today like products. I read about 'collaborative economics'.

I do not know much, but I want to help here with that thought and If possible.

We have several services that we can make people as diverse monetary values. What's good to get back to the software or to the person / group that made the software or to outsiders or just the community and part of it.

I love money, because it allows for many things. Today our biggest money is information. Selling information,  can cost a lot or less depending on your problem.

I believe that selling information to the  'framework Bootstrap' the case should be. For example, if you want services as part of the framework Bootstrap the value will be high. And we can hire more people and make more things.

Another thing, 'Web Design' can be part of this process. Another process would be a new construction of graphs or graphical interfaces 'UI / UX'. In addition, web projects have turned to animation, new libraries and resources inside to 'framework Bootstrap'.

The sale and purchase would be made by API PayPal. And,  communication between Whatsapp / Telegram API inside Boostrap Business.

Going back through the idea.

Name Lib: Bootstrap Business.
Language programming: Javascript, CSS, HTML.
Name file: bootstrap-business.js

Example

boostrap-business.js

API PAYPAL   - API TELEGRAM - API WHATSAPP

<!DOCTYPE html>
<html>
<body>
<bootstrap-business>
<!------- Template Bootstrap 1 with Whatsapp active and Telegram active ---->
<template paypal="R$2000,00" whatsapp="active" telegram="active"></template>

<!------- Template Bootstrap 2 with Whatsapp active  ---->
<template paypal="R$2000,00" whatsapp="active"></template>

<!------- Template Bootstrap 4 with Telegram active  ---->
<template paypal="R$2000,00""></template>

<!------- Template Boostrap 4, only price in Bootstrap ---->
<template paypal="R$2000,00""></template>
</bootstrap-business>

<!------- USD, R$ ( Value Brazil ) ... values of money ---->

<!------- attribute paypal 'Paypal' is https://www.paypal.com/cgi-bin/webscr?cmd=_ ---->
<!------- attribute whatsapp 'Whatsapp' is https://api.whatsapp.com/send?l=pt&phone=  ---->
<!------- attribute telegram 'Telegram' is  ---->

<script src="bootstrap-business.js"></script>
<script src="socket.js"></script>
</body>
</html>

Concept
No servers, peer to peer. Use socket.io for this
Regards,
Pedro Guilherme.

Note
If you want to help build this idea with me, open my repository and we can discuss this idea.
Reference
https://github.com/pedroguilhermelima/bootstrap-business
Regards,
Pedro Guilherme.

Not planning on adding this in Bootstrap.


Update dependency quay.io/keycloak/keycloak to v15.1.1

This PR contains the following updates:

Package
Update
Change

quay.io/keycloak/keycloak
minor
15.0.2 -> 15.1.1

Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

Renovate Ignore Notification
As this PR has been closed unmerged, Renovate will now ignore this update (15.1.1). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the ignoreDeps array of your renovate config.
If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.


2 bugs

Hi
Have 2 bugs
1.i can play like 2 songs/videos(its doesnt matter)
and after that,i stuck on play button on the screen and cant play the song/video..
I think that i need close youtube and after that i open it again,its work-again for 2 songs and stuck after that,even i touch another video ,the play button stuck on the screen...

I cant see on the status bar the play,stop,forwad ,you know all the button that show usually,i see gray background and doesnt see the butoons,even i touch when they need to be,anything works.. So that mean they do not work and arent displayed, this means that the technical and programmatic problems and not beacuse gray background display problem simply hides the same buttons ...
I will more than happy if can fix it and wait for comment.. Tnx

Somebody?!?!


feat(apps/prod/tekton/configs/tasks): add env var RUSTUP_DIST_SERVER in binary building step

replace mirror with another one.

/approve


WalletConnect updates

New try for updating WalletConnect related packages and some more fixes cherry picked from #594. WalletConnect update is valuable in itself as v1.5.0+ has great new UX improvements, like allowing on mobile to connect to mobile apps, and on desktop to connect to other desktop apps and such. This is essential for a mobile-only experience with WalletConnect + Ledger Live + Ledger Nano X via bluetooth.
On the other hand I get the irony for improving the connection but most transaction will still make problems because of #592

might fix #748 nope, Atomic Wallet exposing BNB address instead of ETH address seems actual issue
closes #594

Example on mobile for new screen:

Example new screen on desktop:

Should network changing work now, because it's not working for me in these combinations :
Mobile chrome + mobile metamask
desktop edge + mobile metamask.
The only solution is to disconnect , change network , connect wallet again. Not ideal but a viable workaround

Interesting, for me both those combinations work and after connection I can switch network in MetaMask and some seconds later is reflected in market UI:

mobile Safari/Firefox + mobile MetaMask
desktop Safari/Firefox + mobile MetaMask

So not sure if Mac/Win or iOS/Android differences lead to this

Yep, it's basically the same issue https://github.com/oceanprotocol/market/pull/594#issuecomment-848630288


Add sodium_crypto_secretbox_keygen() function

Thank you for contribution. Please add @since tag, and link to documentation.

So are you interested if I do : https://github.com/JetBrains/phpstorm-stubs/pull/304#discussion_r156090671?


Image Element

Feature description
Image element needs to support secondary edit mode (masking / focal point picking), aspect ratio lock, animated gifs

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance criteria

Implementation brief

QA testing instructions

Demo

Changelog entry

No longer needed


RFC: Automate or abandon forks

Proposal:
Completely abandon fork workflows in favor of branches
OR
Automate privileged forks to reduce friction in those workflows
Reasoning
We've had a long, colorful history with forks. We've got a smattering of projects that disallow fork PRs via peril. We have had (still have?) github tokens for commenting exposed to the public intentionally because danger ran some important tasks that we wanted to make sure there were comments posted on the PR for.
The friction is that we can't (currently) share privileged information (tokens) with forks and thus they break a lot of tooling/automation. This is something we can surmount technically though. We could have automation that listens for new opened fork PRs and automatically creates a tag or branch that's pushed upstream. With certain naming conventions, either of those strategies could directly report status directly back to the fork branch. It'll take some iteration to get right, but this is automation we could do once to allow folks to work however they want.
We could also just stop using forks entirely. That'll change how some people work, but it'll completely eliminate the need for any special tooling.
So those are (as I see it) our options. I'd welcome other options if I missed them.
How is this RFC resolved?
We decide on an approach and take action towards it.

and thus they break a lot of tooling/automation

I could use some further explanation on this point - what breaks?

Anything that needs tokens or credentials to run. Deploying canaries, commenting on PRs, doing stuff in slack, etc.

@zephraph Thanks for this RFC :100:
I'm in favor of Artsy GitHub organization members using branches within the organization's repositories instead of forks.
For external contributors to our open-source projects, I think any privileged tasks could skip or degrade so that the core function of building and running tests continues for fork PRs.
A nice-to-have would be to post some message if we detect a PR running from a fork and the author is in the Artsy GitHub organization. It's difficult to roll out process changes like this. A little nudge when appropriate and acceptanting gradual adoption might be easier than a more aggressive mandate.

We have had (still have?) github tokens for commenting exposed to the public intentionally ...

Yeah, this is not ideal but Danger's docs touch on this, and we have used the suggested workaround in the past. Let me know what I can clarify here – the @ArtsyOpenSource credentials are in 1Password and I think it might still be configured for a few repos' Danger installs.

We could also just stop using forks entirely.

Sounds great! It would simplify OSS repo workflows and improve security (since we no longer need to configure CI to pass secrets to fork PR builds).

For external contributors to our open-source projects, I think any privileged tasks could skip or degrade so that the core function of building and running tests continues for fork PRs.

For OSS PRs, I typically examine the commits and then pull them into a branch PR to trigger the CI run. It's a bit of a workaround but it works well and OSS PRs requiring CI runs don't happen too often. Here someone opened a PR, and here is where I created a branch PR to run the tests.

A nice-to-have would be to post some message if we detect a PR running from a fork and the author is in the Artsy GitHub organization

This would be a great idea – it would be trivial to extend the existing Peril rule.

FYI, dB touched on the reasoning Artsy used forks in the first place in this blog post: https://artsy.github.io/blog/2012/01/29/how-art-dot-sy-uses-github-to-build-art-dot-sy/

As a cautionary tale, I noticed a dev accidentally commit directly to Gravity master just a few days ago. If we were to abandon forks en masse a first step would be to audit and lock down all of our repos so that that kind of thing can't occur. I think a lot of us here heavily rewrite our git history through rebases and so on.

Circleci does have an article about how to automate the notion of privileged forks: https://circleci.com/blog/triggering-trusted-ci-jobs-on-untrusted-forks/

I'm fine with this, with one caveat.
One benefit of the fork approach is that the upstream repo does not become cluttered with developers' stale feature branches. If we do adopt the branch approach, I'd love for us to figure out a solution for that.
Currently GH will delete a branch upon a PR being merged, but non-merged branches hang around forever. GH will mark them as stale after 3 months but take no further action because it can't make any assumptions about what that inactivity means.
Maybe we can automate deletion of stale branches after some threshold (whether 3 months or greater, and subject to some allowlisting for long-lived branches like master and release)?

As a cautionary tale, I noticed a dev accidentally commit directly to Gravity master just a few days ago. If we were to abandon forks en masse a first step would be to audit and lock down all of our repos so that kind of thing can't occur. I think a lot of us here heavily rewrite our git history through rebases and so on.

Luckily, protected branches can solve this problem, so while this will require some configuration (and testing), I think this is a solvable problem!

I think there's a lot of conversation here about the technical reasons to switch to branches over forks. I'll add another one:
About to ship automation in Force will allow devs to build review apps by pushing to certain branches.
It's critical that this only runs on artsy/force. As such, it'll be a bit annoying to have a workflow where feature work occurs at (e.g.) dleve123/review-app-feature-work, but needs to be mirrored at artsy/review-app-feature-work. Not the end of the word, but food for thought.

With that said, I think there are many, non-technical drawbacks of our forking based approach:

Forks are dubious from an intellectual property perspective.

I think forks discourages, from a systems-perspective, collective code ownership and collaboration. If I'm pairing with someone, the fact that we have to choose which fork to push to, IMO, suggests slightly more ownership by 1 person. Some (most) work does that a clear owner, but our tooling decisions should be flexible enough here to reflect the disparate (and valuable) ways we work.

It raises the bar to git-ing well: The mere existence of another upstream present in a git workflow, I think, increases the cognitive complexity (and fear) of rebasing, ensuring that the master you are branching off of it up-to-date, etc. git-ing well is hard enough already!

I think forking provides yet another digital folder and means to organize things – I think it's easy to cut yourself on the folder - the cons outway the pros to me.
Year-old Slack thread on this topic: https://artsy.slack.com/archives/C03J4L2KK/p1552490693081200

I definitely prefer branches with protected branches over trying to automate forks. The latter doesn't feel like a good use of developer time. Also 👍 to clearing out old branches automatically after 3 months.

I'm attached to the forking model, but happy to try out something different if the tooling and safeguards are that much better.
Personally, I don't think forks raise the bar to git usage unnecessarily. Understanding git's distributed model is so helpful that I consider it more of a baseline expectation for effective contribution. It actually mitigates the risk or fall-out from any one contributor's messy branch practices or rebasing/force-pushing. One fear I have is that our shared repo will end up as messy as the least-git-disciplined contributor's does today.
My intuition is against depending on a lot of automation or tooling to mirror or sync forked PRs  to an org repo. It seems like that could get complex and overly-custom quickly, and be misaligned with most "standard" tooling.

@joeyAghion would your suggestion be to keep the status quo? @jonallured also curious to hear your thoughts.

I'm torn and don't have super strong feelings tbh. I guess one question I have is whether we need to have a policy here that covers all projects. Like, if forks are causing issues in MP and Reaction or whatever, then maybe we should have a different approach there but does that mean we want to abandon forks everywhere? I'm not as close to this stuff as you are @zephraph so ultimately I feel like deferring to the people in the trenches is the right approach and I trust your judgement. ❤ 🤗

That's a great point. My explicit intention in this RFC isn't to advocate one solution over the other but hopefully help the team converge around a single solution.
You're absolutely right in that we can have different approaches in different repositories. That is, to a large extent, how we function today. In repos where we have automation that needs authentication we have two primary mechanisms of dealing with that.

Simply not running CI on forks and having automated notifications via Peril that forks aren't supported. This is the defacto in Eigen for example. (@ashfurrow, feel free to correct me if I'm misspeaking).
Gracefully degrade for a fork and don't run the auth'd automation but run everything else that we can.

While these two solutions have provided us with a "good enough" environment, it still belies major complexity and workflow friction.
If you're used to a fork workflow and open a PR on a repo that doesn't support forks it can be a bit of a jarring/frustrating experience to have the repo reject your PR because it doesn't support forks. It's fine, you can just close that PR and open a new one from a branch, but it is a bit of added friction.
For #2, the same underlying scenario exists if you need the auth'd automation. You open a PR, the thing you need doesn't run, then you have to close the PR and open a new one from a branch. Assuming you don't (the automation is nice-to-have and not need-to-have) someone had to go through and engineering that CI robustly to not fail for your usecase. While that's fine for the most part there's a not-insignificant complexity cost to adding all the branching logic of how to gracefully handle those failures.
I see an overall trend of us as a team trending towards more consolidated technical strategies and workflows. While individual workflows will always vary, any consistency that we can add (while trying to account for or reduce friction) increases our ability to collaborate more efficiently and effectively.

A general observation from this conversation... collectively we don't consistently use forks or branches. We do both, depending on the individual contributor.
To @anandaroop's point... there are 49 branches on reaction currently. ~36 of those branches are stale. Upstream repos are already getting cluttered with stale branches. Occasionally one of us will go through and delete old branches. That'd be a great thing to have automation around. It's also indeed something that wouldn't be an issue if we were all on forks.
I think all of the concerns raised with the branching model we already face today. Because not everyone uses forks. Likewise, forks are generally treated as second class citizens when it comes to CI.
I think we're largely experiencing the worst of all these tradeoffs because we're not owning our solution, but rather letting it emerge from team preference.
In general, my position is this
I'm fine with forks. I'm fine with branches. As a team, I'd like to see us consolidate on an approach and invest in making it solid. No approach will be perfect, but if we consolidate and work together we can make it a great experience.

Final entry to my monologue. Consolidation might not be the right approach either. I could be thinking about this much too rigidly. I hope it's clear though that there's solid room for improvement here. I welcome all feedback and solutions, even if it's not in line with the suggestions of this RFC.

Can someone provide a concrete example of the negative value of stale branches in a repository?
To be totally transparent, I too, dislike, stale branches as it clashes with my drive to be a digital minimalist (with some things), but I struggle to see (and have never experienced) a concrete, velocity-impacting correlation between the presence of stale branches and my ability to get work done.
I think one key proposed "pro" to the forks side of this conversation is that it avoids the clutter of stale branches – just think we should motivate that pro before using it to calculate a decision here.

Don't have too strong of feelings either way but have a preference for branches just for ease of workflow compared to keeping forks up to date. As far as negative impact of stale branches for me it is just clutter and makes it maybe slightly more difficult to find where active development is occurring, pretty minor admittedly and would be hard pressed to find an example where it actually affected velocity.

Having worked mostly in eigen recently (which uses branches by necessity), branch clutter has cost me a few seconds once or twice while searching for old branches I forgot the name of. Compared to issues with forking it's negligible IMO.

Sounds like a strong branch-naming convention (like <githubusername>-<topic>) could mitigate some of the clutter, or at least make it clear who should clean up.

I've been doing pavlos/the-thing-i-add for a while when I know a branch might live for a while and I don't want to clutter the branch space. It helps because then / becomes a "dir" in git that I can fold/unfold.
Also, just my opinion too, I prefer branches. Forks create overhead and complications.

Oh nice @pvinis, i like the use-your-name convention a lot.

Majority support to this point has been for removing forks from our workflow. To that end I'll mark this RFC as resolved and begin the following actions:

PR an update to our peril automation to remind folks to use branches over forks. We can merge this when we feel ready to fully proceed or incrementally roll it out.
Experiment with protected branches in a low traffic repo to ensure it's compatible with our current automation
Slowly rollout the process to our tier 1 projects to ensure there's plenty of time for feedback about the process.

Thanks for participating folks. If you have any more thoughts/comments, feel free to drop them below.

I've noticed a lot more development happening on branches within repos that formerly relied on forks, presumably as a result of this RFC. Two outcomes:

CI capacity has been more scarce, as WIP commits trigger builds more often (minor).
Branches have started accumulating. Some are named in helpful ways (with ticket numbers or developer names or prefixes describing the type of change), but they're still inconsistent and it's unclear which can be cleaned up.

I think we should recommend the following to mitigate this:

Work on forks or branches according to whatever is suggested in a project's README. Absent a specific recommendation, work on branches (for the reasons outlined in this RFC).
When working on branches, name branches like <githubusername>/<whatever-topic>. Even if the actual work is a collaboration among multiple developers, the unambiguous naming makes clear who is creating [and should destroy] the branch.
Delete branches once work is complete.

Delete branches once work is complete

I spent each day deleting branches merged from PRs, i'm not sure why folks have a hard time remembering to delete. Do you have any ideas about how to encourage / automate @joeyAghion?

I'm pretty sure you can do this with git remote prune origin (test it with git remote prune origin --dry-run). Also a source

Any reason for us not to enable this config (per repo):

Or does that conflict with the PR-based deploy approach?

CI capacity has been more scarce, as WIP commits trigger builds more often (minor).

This can be mitigated in the Circle dashboard by turning off builds on branches that do not have an open PR, which we did in eigen as a necessity when moving our danger script from travis to circle.

@anandaroop exactly: I think that setting would delete the staging branch that our release pipeline depends on. Maybe the automatic deletion rule be enabled in combination with another rule preventing deletion of staging in particular?

Doesn't staging automatically get regenerated during our CI flow?

Doesn't staging automatically get regenerated during our CI flow?

No, our CI flow expects it to be there.

I actually think projects using this orb step will successfully recreate a staging branch if it doesn't exist. Not sure what else might break down if it gets frequently deleted, but we could at least try this on a project.

Yeah, I've noticed the staging branch get deleted probably dozens of times with no issues 👍

I've noticed the staging branch get deleted probably dozens of times with no issues

Yeah, I kinda do that accidentally quite frequently. Disabling builds except for PRs might be helpful so long as that doesn't prevent our process working (would release branches still build?).


Add Code Comments

You may have noticed that the code is well commented. You just need to understand the functionality of class and static methods, and write 'code comments' above them.

[ ] controllers/global_setting.dart take example from other classes
[ ] models/global_setting.dart
[ ] screens/profile_page.dart

Learn more from here: https://dart.dev/guides/language/effective-dart/documentation

assign me this issue

assign me this issue


Dont send any adapter other than from source directory for netcoreapp

@dotnet-bot test Windows_NT / Debug Build please


observe triggers twice when doing a round trip

Related to https://github.com/QuantStack/ipysheet/issues/66
To illustrate, a simple app that formats floating point user input
import ipysheet
import ipywidgets as widgets

as_list = True

sheet = ipysheet.Sheet(rows=1, columns=1)
if as_list:
    sheet.cells = ipysheet.Cell(value=[""], row_start=0, row_end=0, column_start=0, column_end=0,
                                squeeze_column=True, squeeze_row=False),
else:
    sheet.cells = ipysheet.Cell(value="", row_start=0, row_end=0, column_start=0, column_end=0,
                                squeeze_column=True, squeeze_row=True),

output = widgets.Output()

updating = False

def update(change):
    global updating
    with output:
        if updating:
            print('internal trigger')
            print(change)
        else:
            print('external trigger')
            print(change)
            updating = True
            if as_list:
                sheet.cells[0].value = ['{:.4f}'.format(float(entry)) for entry in change.new]
            else:
                sheet.cells[0].value = '{:.4f}'.format(float(change.new))
            updating = False

sheet.cells[0].observe(update, names='value')

sheet.cells[0].value = ['-.4'] if as_list else '-.4'

This puts the following in the output widget:
external trigger
{'name': 'value', 'old': [''], 'new': ['-.4'], 'owner': Cell(choice=[], column_end=0, column_start=0, row_end=0, row_start=0, squeeze_row=False, value=['-.4']), 'type': 'change'}
internal trigger
{'name': 'value', 'old': ['-.4'], 'new': ['-0.4000'], 'owner': Cell(choice=[], column_end=0, column_start=0, row_end=0, row_start=0, squeeze_row=False, value=['-0.4000']), 'type': 'change'}
external trigger
{'name': 'value', 'old': ['-0.4000'], 'new': ['-.4'], 'owner': Cell(choice=[], column_end=0, column_start=0, row_end=0, row_start=0, squeeze_row=False, value=['-.4']), 'type': 'change'}
internal trigger
{'name': 'value', 'old': ['-.4'], 'new': ['-0.4000'], 'owner': Cell(choice=[], column_end=0, column_start=0, row_end=0, row_start=0, squeeze_row=False, value=['-0.4000']), 'type': 'change'}

This shows that there's an extra trait notification, trying to "update" the new value to the original input.
Setting as_list = False uses a scalar instead of a list and does not suffer from this problem
external trigger
{'name': 'value', 'old': '', 'new': '-.4', 'owner': Cell(choice=[], column_end=0, column_start=0, row_end=0, row_start=0, value='-.4'), 'type': 'change'}
internal trigger
{'name': 'value', 'old': '-.4', 'new': '-0.4000', 'owner': Cell(choice=[], column_end=0, column_start=0, row_end=0, row_start=0, value='-0.4000'), 'type': 'change'}

The double notification in the as_list = True case leads to flickering and I'm not sure how to work around it yet.

That is really weird... I displayed the traceback using print_stack and it shows that the second external event has not the same origin. We should try to replicate it using a core widget and post an issue in ipywidgets.
In the meantime I can only try to help you with your use case. If what you want to do is format the float numbers in the cells you can do:
import ipysheet

sheet = ipysheet.sheet()
ipysheet.cell(0, 0, -0.4, numeric_format='0.000')
display(sheet)

Thanks @martinRenou
numeric_format seems useful. I'd also like to replace non-numeric inputs with the empty string.
I tried to replicate the issue using core widgets (Select.options instead of Cell.value) but didn't succeed.
Let me know if you have any ideas
p.s. Do you think https://github.com/QuantStack/ipysheet/issues/66 is unrelated?

I honestly have no clue. This is really internal behavior of traitlets and ipywidgets and I'm not really aware of it.
But this 'old': ['-0.4000'], 'new': ['-.4'] thingy is really odd, I don't why it should happen. I guess it's a bug.
The thing is that you are setting the value of the cell in the callback of an observe call, which is not really common use case.
I guess what you would need is a traitlets validator instead?

Yeah, I agree, and morally, it is validation in this example.
More realistically, I have a separate HasTraits model as presented here: https://github.com/jupyter-widgets/ipywidgets/issues/2296
Following that example, I use observe for connecting the model and the view. Perhaps it's better to use observe for model -> view and validate for view -> model?
Or maybe validate should be reserved as a workaround until this bug is fixed?
We should put together an opinionated tutorial of best practices for ipywidgets
+ @jasongrout


Option to globally disable colour output

See original issue on GitLab
In GitLab by [Gitlab user @rjek] on Jun 29, 2020, 10:41
Summary
There is apparently --no-color but there is no way to globally disable colour output from, say, a dotfile in my home directory.  Colour output is actively unhelpful for the 10% of the population that have some degree of colourblindness.
Steps to reproduce
Run any BuildStream command.
What is the current bug behavior?
There is colour.
What is the expected correct behavior?
Method to globally disable colour without having to pass --no-color to every invocation.
Relevant logs and/or screenshots
Possible fixes
Other relevant information

BuildStream version affected: /milestone %BuildStream_v1.x

In GitLab by [Gitlab user @cs-shadow] on Jun 29, 2020, 23:03
Thank you for bringing this up. This is probably worth doing from a UX perspective anyway, but the accesiblity issues you mentioned make it even more relevant.
BuildStream already supports user configuration by way of ~/.config/buildstream.conf. So, it may make sense to add a new option there.
We don't have an existing config section related to the CLI, but it may be worth starting one.

In GitLab by [Gitlab user @rjek] on Jun 29, 2020, 23:13
It's probably worth also noting that emboldening/underlining/obliquing text is unlikely a problem, but trying to communicate data via colour frequency will be.
For my own sanity, it would be delightful if BuildStream could accept the spelling "colour" as a synonym in relation to this functionality.

In GitLab by [Gitlab user @traveltissues] on Jul 1, 2020, 14:10
not directly related but perhaps it's worth having no colour as the default?


synchronous version?

I really like this code, but I want to use it in a program where the KDF needs to be called several times for different strings. Waiting is a plus, since I want to encourage users to use high-entropy passwords, and I add rounds of KDF for low entropy.
Is there a way to use your function synchronously, without callbacks?

Answered here: https://github.com/dchest/tweetnacl-js/issues/68
FYI, you can wait even async functions — just disable any other actions (for example, in demo.html I disable button until the function is done).


Opening a file should erase history stacks

Can replace with the file's history stacks if we add that to the file format

fixed by #60


D_M and D_A portion

Could you please tell me the portion of D_M and D_A in each fold? Are they evenly splitted?

@wang3702 We use ratio of 0.4 for D_A. See our codes.


[rayci] microcheck pipeline rayci config

As title, store this in rayci to obscure its definition.

make a copy of the struct + map; added some test cases

convert prPipelineConfig into a function


Repo sync working branch

Docs Build status updates of commit bd45af9:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/MicrosoftDocs/sccm-docs-powershell-ref, working directory: W:\b0ec-s, target branch: master, target branch commit: dd249672a2bdc1682927a211a96c5302da7b4b7b, source commit: bd45af9b15c3b92c1e4e4f3f0513afdc5fc2779b.

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


TreeMap::insert's behavior differs from {BTreeMap, HashMap}

{BTreeMap, HashMap}::insert does not replace the existing key with the new one, but TreeMap::insert does. In common usage, this doesn't matter, as derived {Hash, Eq}/Ord impls incorporate all fields, but custom impls can experience surprising behavior despite meeting the requirements for {Hash, Eq}/Ord:
extern crate collect;

use std::cmp::Ordering;
use std::hash;

struct Foo(u32, &'static str);

impl hash::Hash for Foo {
    fn hash<H: hash::Hasher>(&self, h: &mut H) { self.0.hash(h); }
}

impl PartialEq for Foo {
    fn eq(&self, other: &Foo) -> bool { self.0 == other.0 }
}

impl Eq for Foo {}

impl PartialOrd for Foo {
    fn partial_cmp(&self, other: &Foo) -> Option<Ordering> { Some(self.cmp(other)) }
}

impl Ord for Foo {
    fn cmp(&self, other: &Foo) -> Ordering { self.0.cmp(&other.0) }
}

#[test]
fn test_tree_map() {
    use collect::TreeMap;

    let mut m = TreeMap::new();

    m.insert(Foo(1, "a"), ());
    assert!(m.iter().find(|&(k, _)| k.0 == 1 && k.1 == "a").is_some());

    m.insert(Foo(1, "b"), ());
    assert!(m.iter().find(|&(k, _)| k.0 == 1 && k.1 == "a").is_none());
    assert!(m.iter().find(|&(k, _)| k.0 == 1 && k.1 == "b").is_some());
}

#[test]
fn test_btree_map() {
    use std::collections::BTreeMap;

    let mut m = BTreeMap::new();

    m.insert(Foo(1, "a"), ());
    assert!(m.iter().find(|&(k, _)| k.0 == 1 && k.1 == "a").is_some());

    m.insert(Foo(1, "b"), ());
    assert!(m.iter().find(|&(k, _)| k.0 == 1 && k.1 == "a").is_none());
    assert!(m.iter().find(|&(k, _)| k.0 == 1 && k.1 == "b").is_some());
}

#[test]
fn test_hash_map() {
    use std::collections::HashMap;

    let mut m = HashMap::new();

    m.insert(Foo(1, "a"), ());
    assert!(m.iter().find(|&(k, _)| k.0 == 1 && k.1 == "a").is_some());

    m.insert(Foo(1, "b"), ());
    assert!(m.iter().find(|&(k, _)| k.0 == 1 && k.1 == "a").is_none());
    assert!(m.iter().find(|&(k, _)| k.0 == 1 && k.1 == "b").is_some());
}

running 3 tests
test test_btree_map ... FAILED
test test_hash_map ... FAILED
test test_tree_map ... ok

failures:

---- test_btree_map stdout ----
	thread 'test_btree_map' panicked at 'assertion failed: m.iter().find(|&(k, _)| k.0 == 1 && k.1 == "a").is_none()', src/lib.rs:50

---- test_hash_map stdout ----
	thread 'test_hash_map' panicked at 'assertion failed: m.iter().find(|&(k, _)| k.0 == 1 && k.1 == "a").is_none()', src/lib.rs:64

The fix for collect is simple (remove this line), but I'm not sure if this should be considered a bug in std. In either case, the behavior should be the same.

My general opinion on this has been to leave it unspecified, since the collections don't even acknowledge that you could care. Not swapping the keys is faster, but swapping the keys might be more useful.

Individual map types can specify the behavior (or leave it unspecified),
but I do think it should be documented. There's also the problem of how the
entry method interacts with this. It would be surprising for the two to
differ.
On Thursday, March 12, 2015, Alexis Beingessner<EMAIL_ADDRESS>wrote:

My general opinion on this has been to leave it unspecified, since the
collections don't even acknowledge that you could care. Not swapping
the keys is faster, but swapping the keys might be more useful.
—
Reply to this email directly or view it on GitHub
https://github.com/Gankro/collect-rs/issues/144#issuecomment-78697081.

I'm 99.9% certain that I made sure that the Entry APIs match up.

Yeah, they do match for BTreeMap and HashMap. TreeMap doesn't have the
entry API, but if it is added (my tree crate maintains the current
behavior), insert will likely differ and need to be updated.
On Thursday, March 12, 2015, Alexis Beingessner<EMAIL_ADDRESS>wrote:

I'm 99.9% certain that I made sure that the Entry APIs match up.
—
Reply to this email directly or view it on GitHub
https://github.com/Gankro/collect-rs/issues/144#issuecomment-78699682.

Unless you have a concrete usecase for changing the key, I'd be fine with just specifying that it remains the same, to avoid the cost of replacing it.


link "ich kaufe lokal" page on landingspage and place in menu

place a link to "https://www.ichkaufelokal.org/" in start page and on the menu

@MaximilianSei @owlRike
please have a look at the content and provide more viable texts if needed

Looks great :-)


Rust client library: Unexpected Token(Some("1")) when querying data

Hey 😄 I don't know if this is me doing wrong but I get a weird error when I am quering data using libsql client.
I am using libsql-rs version 0.4.0
the error
near VARIABLE, "Token(Some("1"))": syntax error

Setting up client connection
This is how I setup connection
let db = if !db_url.starts_with("./") {
  let auth_token = if let Some(t) = token {
      t
  } else {
      info!("Token is not set, using empty string");
      "".to_string()
  };

  Builder::new_remote(db_url.to_owned(), auth_token)
      .build()
      .await
          .unwrap()
} else {
    Builder::new_local(db_url).build().await.unwrap()
};

let client = db.connect()?;

The code executing the query
self.db
  .execute(
      "CREATE TABLE IF NOT EXISTS ?1 (id VARCHAR(255) NOT NULL PRIMARY KEY);",
      params!["schema_migrations"],
  )
  .await?;

self.db is the Connection type which comes from the let client
What worked
Replacing
self.db
  .execute(
      "CREATE TABLE IF NOT EXISTS ?1 (id VARCHAR(255) NOT NULL PRIMARY KEY);",
      params!["schema_migrations"],
  )
  .await?;

with
self.db
    .execute(
        format!(
            "CREATE TABLE IF NOT EXISTS {} (id VARCHAR(255) NOT NULL PRIMARY KEY);",
            self.migrations_table
        )
        .as_str(),
        params![],
    )
    .await?;

aka we're instead of using params using format!(). I don't think this is long-term as I think params![] also do query escpaing right?

Please let me know if you need more code. I happily share more

https://www.sqlite.org/cintro.html#binding_parameters_and_reusing_prepared_statements

Parameters may not be used for column or table names, or as values for constraints or default values.


Column mode "sticks"

I'm having an intermittent but frequent problem.  When I finish using column mode the selection sticks in column mode and I can't do normal selection.  It acts as if the alt-key is stuck down.  The only thing that fixes it is to select again with the alt key down although this takes several tries at times.
I saw the thread here about the mouse leaving the window but this problem happens when the cursor doesn't leave the middle of the window.
I'm on windows 8.0 and atom 119.  This has happened since I started with atom a few weeks ago at version 116.

Is this now fixed for you? I can no longer reproduce the issue?


purgequota

Library Affected:
workbox-sw
There's an ExpirationPlugin which we can assign to our routes. I couldn't find in the docs though one thing that clearly states what I need to hear.
Does this clean up the whole cache for that specific route? if I set this to true for images in the specific cache called app-images and let's say quota is exceeded, will this clean up the whole app-images cache or some part of it to shrink the size to take it down under the storage limit again?

The code will delete everything in the cache, along with any IndexedDB data used by the expiration code:
https://github.com/GoogleChrome/workbox/blob/fe4399505e02c3af6515fc8ffae8c58791f43f3c/packages/workbox-expiration/src/ExpirationPlugin.ts#L262-L289

Yeah, So sorry for another question.
If I use ExpirationPlugin for 2 routes, even if those 2 routes have different cacheName,  if the storage limit exceeds, is workbox gonna delete everything in both caches? or the one which caused the exceed?

It will delete  both of those caches.
The idea is that you want to get well under the quota limit by deleting as much as possible, so it will delete all the caches that you've opted-into deleting.

yeah. I get that. It might be better to only try to delete the one which caused it. maybe it's enough to delete only one cache just to come down the limit ? why both ? That's what i am curious.

The goal is to avoid getting the browser close to reaching the limit again for an extended period of time, so deleting as much as the developer has opted-into is the safest default approach.
If you'd prefer to use your own customized approach to recovering from quota errors, instead of setting purgeOnQuotaError: true in the ExpirationPlugin, you can register your own custom callback with workbox-core's registerQuotaErrorCallback() function.


feature: Kotlin support

Did you check the docs?

[X] I have read all the LazyVim docs

Is your feature request related to a problem? Please describe.
I would like to use LazyVim for Kotlin development but i do not see it being treated as first class citizen i.e. there is no kotlin in the 'plugins/lang' folder.
Describe the solution you'd like
Is it possible to add this?
Describe alternatives you've considered
na
Additional context
Please elaborate If there is a particular reason why kotlin has been blacklisted. Thank you

All the language Extras come from contributions via PRs from users of LazyVim. Kotlin is not there because no LazyVim user that potentially uses Kotlin has made a PR for Kotlin support. If you'd like feel free to make a PR for Kotlin support. So nothing is blacklisted as you erroneously have pointed out.

Feel free to provide an extra for Kotlin


About the YCSB+T benchmark

Hi, @BLepers .
I have a question about the implementation of YCSB+T.
Where did you get the latest YCSB+T project?
The only place I can find to fork it is on Akon Dey's github.
https://github.com/akon-dey/YCSB
Could you help me to implement the ycsb+t benchmark correctly?
In his article he reports having such methods:
"
• doTransactionInsert() creates a new account with an
initial balance captured from doTransactionDelete() operation described below.
• doTransactionRead() reads a set of account balances
determined by the key generator.
• doTransactionScan() scans the database given the start
key and the number of records and fetches them from the
data base.
• doTransactionUpdate() reads a record and add $1 from
the balance captured from delete operations to it and write
it back.
• doTransactionDelete() reads an account record, add the
amount to the captured the balance (capture used in
doTransactionInsert()) and then deletes the record.
• doTransactionReadModifyWrite() reads two records,
subtracts $1 from the one of the two and adds $1 to
the other before writing them both back.
"
In the akon repository where I made the fork, I didn't find the implementation of the methods doTransactionInsert() , doTransactionRead() , doTransactionScan() , doTransactionUpdate() and doTransactionDelete().
I just noticed that the doTransactionReadModifyWrite() method is implemented, where it subtracts the value 1 from account A and assigns that value to account B.
Could you help me understand this part of the implementation?
Regards,
Caio

The implementation of YCSB-T is in the OSDI branch -- https://github.com/BLepers/KVell/blob/osdi/workload-transactions.c#L92
Basically we just wrapped batches of 16 YCSB queries in transactions. YCSB-T is not an official benchmark, so there's a bit of room for implementation. The goal is just to have a simple workload to understand the performance/overhead of transactions :)

Thanks for the feedback, @BLepers .
So, in my case, I took the code from Akon's repository and didn't make any changes because in his paper he already says that he extended ycsb already with the transactional layer. In case I need to change something in the code? Can I use the way it is there and call the workloads?
Can you help me ?
I really need to get this to work.
I know it's not a scary thing to do, but it would really help me if someone helped me.
In my case I'm going to do tests with MongoDB.
I'm calling the MongoDBclient.java class (which already comes in the repository) to make calls to my cluster (it's in MongoDB Atlas).
I'm managing to use the benchmark normally, but I don't know if the default implementation of YCSB+T is working with transactions in MongoDB.
Regards,
Caio

Hi, @BLepers.
Do you have any suggestions about what I told you?
Regards,
Caio

Hi, @BLepers .
In my case, I'm going to use the YCSB+T closed economy workload to do consistency testing on MongoDB.
As I understand it, this workload is already implemented.
I also noticed that it has those start() , commit() and abort() methods.
Did you ever notice these methods when you did your tests?
I noticed that they were empty and I didn't understand what they were there for.
Do you have any idea why?
I'd just like to understand better because I'll do the implementation myself if I need to.
For now, I'm just clearing up these doubts even with the people who got to work with the YCSB+T.
Regards,
Caio


signalbackup-tools: 20220810 -> 20220825

Description of changes
Update to latest release.
Nothing in this release that should effect the Nix build. Changes are mostly just those included in the patch I added when updating to the previous release, which I've now removed in this PR (diff from previous release).
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[x] 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

[x] 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/)
22.11 Release Notes (or backporting 22.05 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

[x] Fits CONTRIBUTING.md.


[WinUI3 Reunion 0.5] "ExtendsContentIntoTitleBar" Hides Min/Max/Close Buttons

Describe the bug
In WinUI 3 Reunion 0.5, using "ExtendsContentIntoTitleBar" when the background is set on the
control to be used as the title bar results in the standard action buttons on the window
(minimize, maximize, close) being hidden.
Additionally, the action buttons are a smaller height when "ExtendsContentIntoTitleBar" is used.
In UWP, this was accomplished with code like this:
CoreApplication.GetCurrentView().TitleBar.ExtendViewIntoTitleBar = true;
mainWindow.SetTitleBar(AppTitleBarColor);

Steps to reproduce the bug

Clone the WinUI3Reunion05_Problems.
Go to the WinUI3IssuesReunion05 folder.
Open the WinUI3IssuesReunion05.sln solution in Visual Studio 2019 Preview.
Build and run with Debug x64.
Click on the seventh item on the Navigation View (SetTitleBar).
Click through each of the buttons for demonstration.

Expected behavior
We expect to be able to customize the TitleBar without losing the standard window buttons.
Screenshots

Current (WinUI3 Desktop) vs. Expected (UWP) - Setting TitleBar to Blue

Current (WinUI3 Desktop) vs. Expected (UWP) - Setting TitleBar to No Color
Version Info
Targeting:
Target: Universal Windows
Target version: Windows 10, version 2004 (10.0; Build19041)
Min version: Windows 10, version 1809 (10.0; Build 17763)
NuGet package version:
[Microsoft.ProjectReunion 0.5.0]
[Microsoft.ProjectReunion.WinUI 0.5.0]
Windows app type:

UWP
Win32

Yes

Windows 10 version
Saw the problem?

Insider Build (xxxxx)

May 2020 Update (19041)

November 2019 Update (18363)

May 2019 Update (18362)

October 2018 Update (17763)
Yes

April 2018 Update (17134)

Fall Creators Update (16299)

Creators Update (15063)

Device form factor
Saw the problem?

Desktop
Yes

Xbox

Surface Hub

IoT

Additional context

@pratikone and @Austin-Lamb FYI

Dup of #4209?

Hi @codendone ,
Same bug, new issue for more recent release with an updated solution!
We have been updating to each of the releases to test and track changes in bugs and functionality.  This issue is for the most recent release of Reunion 0.5 while the other issue is for Preview 4.
Thanks again!

Thanks @eleanorleffler,
There is a nasty bug in the custom Title bar that depending on the XAML layout, the window caption buttons don't render on the top of the visual tree. We already have bug fixes for it and I'm expecting to fix this for Reunion 0.8 GA.

I'm glad to hear that a fix will be coming for this. In the meantime, are there any workarounds for this issue?

It appears this issue is still not fixed.

Reunion 0.8 released, issues still remains.

Just to chime in with what I want to achieve with WinUI 3 C#/.NET 5 but still haven't got success, even after 0.8 Preview
Expected Target UX similar to UWP app

So far have below problems in WinUI, most of them related to TitleBar:

Title bar has window drag issue. Dragging window does not work on all areas of title bar.
Min/max and close window buttons are gone,
Title bar controls to right side have hit target problems. Only work if hovered on bottom 5px.
Acrylic Brush with host backdrops missing, hoping its back before 1.0/GA

Current UX in WinUI

Hi all, thanks for bringing this issue out. We found some bugs to fix in this area and some design related restrictions We have catalogued those here : https://docs.microsoft.com/en-us/windows/winui/api/microsoft.ui.xaml.window.settitlebar?view=winui-3.0#Microsoft_UI_Xaml_Window_SetTitleBar_Microsoft_UI_Xaml_UIElement_     Please follow them and see if they fix anything.
Some of the changes include : not setting background property on custom titlebar uielement as it draws over the min/max/close. By default, the custom titlebar will take the accent colors set in your Windows settings but they can be overridden by changing resource values of some brushes. (I will check and post the name of those brushes here)

@pratikone Thanks for the updates. I tried the scenarios with blank app based on your guidance.
I could extend the content on title bar and provide interactive elements (Button "Hey 1" ) on the left area only.

Please confirm on below?

There is now way to provide interactive elements in the title bar area on the right hand side ? e.g. Button Hey 2
In UWP versions we could add margin to left/right to restrict the title bar functionality to the middle on the area. Allowing interactive elements on both sides

Something like Visual Studio does? Where space between the Project name and User icon is the draggable title bar area

Like something I have done in my app too!

Bug

The button "Hey 2" covered by title bar area, is not interactable by mouse/touch but works by using keyboard TAB focus.

Please do let me know if any more data is needed.

Thanks for providing all these scenarios. We are aware of this specific feature request which one can call as non contiguous customer titlebar or having interactable elements within titlebar. Both have the same root. There are discussions ongoing on best ways to support these scenarios

A workaround is described here #4166
But, bugs still exist. As non-draggable area at the top, bottom and right of MinMaxCloseContainer

@schemburkar can you open another  issue with your screenshots ? - it will be helpful to track that issue separately. Closing this one for now as it has been answered

Thanks @pratikone, created #6070. Let me know if you need more details on that thread.


Update website to add new team members

Update the team page to add images of new team members.

hey @ramesht007 I'm mern stack developer i can do this please assign to me.


CSP config should be restricted, but I'm waiting for a material-ui fix

waiting for this issue https://github.com/mui/material-ui/issues/19938


feat: add homeschool option in school picker LESQ-374

Description
Acceptance Criteria:

[ ]  Add an option into the list of schools for "Homeschool"
[ ]  Remove radio button from the list below

Issue(s)
Fixes #
How to test

Go to https://deploy-preview-2012--oak-web-application.netlify.thenational.academy/teachers/programmes/combined-science-secondary-ks4-higher-ocr/units/measuring-waves/lessons/transverse-waves/downloads?preselected=all
Or any download page, radio buttons have gone, school picker has homeschool option

Screenshots
How it used to look (delete if n/a):
{screenshots}
How it should now look:
{screenshots}
Checklist

[ ] Added or updated tests where appropriate
[ ] Manually tested across browsers / devices
[ ] Considered impact on accessibility
[ ] Design sign-off
[ ] Approved by product owner
[ ] Does this PR update a package with a breaking change

initialValue === "notListed"

I am only commenting as I won't be around to see these comments resolved, you'll need to point this at James!

The data being sent to hubspot is different when you select homeschool. Might need to chat with Simon Hacking about how disruptive this would be. On this PR hubspot receives schoolname = "Homeschool" vs "homechool" currently. On this PR we also send through a URN of "home", I don't know how destructive sending through a string URN will be.

Behaviour looks good other than that (and the above might turn out to be a non-issue anyway, but I think it would be best to either make it behave the same, or if we can't, at least have that chat with Simon)

Ok think i've sorted this now, should match what we had before in local storage / hubspot / posthog
@rightsaidjames could you take a look when you get a sec?

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


[docs]: faq - checking for init errors

suggested fix for
https://github.com/open-wc/open-wc/issues/228

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

thank you for your contribution 🤗 ❤


Adds a unique identifier to AMP sw as a comment

One downside of this PR:
https://github.com/ampproject/amp-sw/pull/33/files#diff-11e9f7f953edc64ba14b0cc350ae7b9dR96 will cause the AMP_SW to always have ID of one version behind the current version.
We can avoid this by manually bumping the version and not letting np do it.
Or just by may be keeping the manual counter e.g. a date timestamp might serve the purpose as well

Can use the version hook to correctly generate the version with the bumped value before publishing to NPM.
https://github.com/sindresorhus/np#npm-hooks

@kristoferbaxter the version hook works, do you think we need the pre-publish as well?


Lightweight hand tracking algorithm within min_hand_presence_confidence description

I saw a paragraph explaining "Otherwise, a lightweight hand tracking algorithm is used to determine the location of the hand(s) for subsequent landmark detection."
How does a lightweight hand tracking algorithm work?
Thanks.

So I asked our eng team about this and got an answer for you:
the hand landmarks detection model output a presence score.
If the presence score is high enough, we believe the hand is presence in the current frame. In the next frame, we use the detected hand landmarks to create a new bounding box  (by finding the bounding box enclosing all the landmarks, and slightly expanding it, so it has higher chance to enclose the tracked hand in the next frame).
If the presence score is low, we trigger the palm detection model again.
The point here is, palm detection is time consuming, and we want to skip it as much as possible.


Adding extendLockExpiration function

We lock values for the lifetime of our application, so need to extend the lock periodically so we don't lose ownership.  If the app dies, it will expire because it will not be extended.

@ChristopherDavenport  can you review this please?


Could you elaborate more on how to create a Provider in order to lazily provide exclusions?

Hello,
I came across the new migration guide for the version 0.8.0 and Lazy configuration section caught my attention as I use conventional plugins in our project and would like to more about how to create a Provider for exclusions e.g. how to create classProvider for a comma separated string exclusion?
kover {
  reports {
    filters {
      exludes {
         classes(classProvider)
      }
    }
  }
}

Hi,
according to Gradle's recommendations, you should avoid explicitly creating Provider instance.
if you use convention plugin, then you need to declare the extension in it with property of type Propety<String>, like
interface MyExtension {
    //  comma separated string exclusion
    val exclusions: Property<String>
}

below, when configuring Kover from a comma-separated single string, you need to get Provider of a collection of strings, like
kover {
    reports {
        filters {
            exludes {
                classes(myExtension.exclusions.map { it.split(",") })
            }
        }
    }
}

Closed as answered.
Feel free to create new issue if you have any additional questions.


Enable file system setting for how /bin tools are overriden via zopen-init

Also adds an --override-zos-toos-subset option

Override a subset of /bin zos tools rather than all. Contains a subset of packages to override, delimited by newlines."

TODO:

[ ] add docs
[ ] add tests

The code in general looks good. It is worth noting that given enough overrides and/or a deeply-nested zopen_rootfs, there could be an overflow of $PATH - probably unlikely but might be something to be aware of [hence adding this searchable comment] but not preventing merging.
Is it worth hard-coding the override file to a known location such as /etc/zopen/altbin-overrides for example - does making it configurable add anything? [Perhaps allowing testing of different overrides via different filenames, but that's could done just by cp/mv'ing files in the /etc dir. instead] Hardcoding would ensure consistency [all zopen config held in one location], can be documented as-such and can be requested if there are issues such as for servicability, just tarring /etc/zopen would get it all...

The use case I was thinking of was

The code in general looks good. It is worth noting that given enough overrides and/or a deeply-nested zopen_rootfs, there could be an overflow of $PATH - probably unlikely but might be something to be aware of [hence adding this searchable comment] but not preventing merging.
Is it worth hard-coding the override file to a known location such as /etc/zopen/altbin-overrides for example - does making it configurable add anything? [Perhaps allowing testing of different overrides via different filenames, but that's could done just by cp/mv'ing files in the /etc dir. instead] Hardcoding would ensure consistency [all zopen config held in one location], can be documented as-such and can be requested if there are issues such as for servicability, just tarring /etc/zopen would get it all...

The scenario I was thinking about was if there's a shared read-only zopen file system and a user of the file system wants to enable zos overrides for coreutils and openssh, then they can use this option. We could have one on the zopen file system level as well in etc/zopen/

I can see the value in that 😄
Just having the one override makes sense as otherwise it gets overly complex (precedence etc), so your implementation seems the sensible option.


Remove option acq_optimizer="auto"

In order to simplify  slightly the API, I would vote for removing the "auto" value of acq_optimizer.
I am not convinced we should default to random sampling as soon as one of the dimensions is not Real.
I would rather default to "lbfgs" and have, maybe, a warning if one the dimensions isnt Real. (Which by the way does not mean that the optimization will fail.)

Sorry, but I would humbly disagree. It is all-right if it performs slow but no so-much if it provides a wrong output that cannot be relied on as the next candidate point. It is wrong because the output of the fit_transform for a LabelBinarizer is unreliable when the input is not in {0, 1}.
See: https://github.com/scikit-learn/scikit-learn/issues/7247

My point is that there is nothing wrong with running lbfgs on integer or binary dimensions, as long as the solution returned is cast back correctly.

Ah yes, sorry you are right. I misread the documentation of the output of inverse_transform of LabelBinarizer

Fixed.


No output?

Firstly, it's great to see an official action for Deployer.
However, I'm wondering if there is a reason behind the decision to suppress output from the commands? Personally, having used Deployer in other CI/CD environments, it's incredibly useful to see the output for debugging reasons.
I regularly use the --revision argument when deploying to non-production environments, so getting confirmation from Deployer of the revision used is super useful.

I didn’t get it) please explain

When using this action output from the commands are not logged to the workflow log. It simply runs silently, showing Run deployphp/action with no output from the command.
Attached is a screenshot showing the action running without any output logged - simply, I can't see what tasks are being run. Above you will see output from a composer install command, for example.

I believe this has to do with using execa and not piping the output back to the Node process.

Yes you are right. This should be fixed and output MUST be logged.

@amustill

I regularly use the --revision argument when deploying to non-production environments, so getting confirmation from Deployer of the revision used is super useful.

BTW, how to you specify a revision? I use deploy somehost --revision=$GITHUB_SHA -vvv  but it doesn't resolve $GITHUB_SHA into a string (tried different approaches)

@lptn I too have been using --revision="$GITHUB_SHA" but without output I cannot see how it resolves!
I'm currently only using this action on one project (I normally use GitLab CI/CD) so I haven't had the opportunity to fully test its capabilities.


UWP bug: cannot access Application.Resources

Describe the bug
When creating a new UWP app from the templates and trying to access its Resources getter, I get an exception.
Steps to reproduce the bug

Open VS
Create an UWP from the IDE templates
In App.xaml.cs after InitializeComponent() in the constructor, add var r = Resources, and hit F5 to start debugging.
When the debugger gets to that line an Exception is thrown with the following message:

'Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED))'

Expected behavior
Access to application resources
Screenshots

Version Info
IDE: VS 16.1.3
OS: Windows 10 Pro x64 ver. 1809 (build 17763.557)
NuGet package version:
Microsoft.NETCore.UniversalWindowsPlatform: 6.2.8.

Windows 10 version
Saw the problem?

Insider Build (xxxxx)

May 2019 Update (18362)

October 2018 Update (17763)
Yes

April 2018 Update (17134)

Fall Creators Update (16299)

Creators Update (15063)

Anniversary Update (14393)

Device form factor
Saw the problem?

Desktop
Yes

Mobile

Xbox

Surface Hub

IoT

Additional context
I do not want to use Microsoft.UI.Xaml.*, because I use Uno (the reproduction occurs in plain UWP tho).

I believe this is a known issue and you have to wait until something like OnLaunched to be able to access those things. I'll leave this issue active to see if the framework folks want to try to fix this in the future.

@jevansaks
Thanks for your response.
I'm unable to add static resources to the MainPage.xaml file.

UWP is no longer supported by WinUI 3.  If you can repro the issue on current builds without UWP, please reactivate or open a new issue.
Thanks!


Improve docs of functional transforms

Inspired by #533, this PR improves the docs of functional transforms. This PR contains only the improved api docs, not the tutorial.
The api docs contain a short example of how to build a transform pipeline for a segmentation task.
Let me know if you want more/anything else @fmassa.

Thank you for your great work on pytorch!


[ERROR] Unknown plugin: @ionic/cli-plugin-.

npm install -g ionic@beta
For Ionic2 Project
npm install --save-dev @ionic/cli-build-ionic-angular@beta @ionic/cli-plugin-cordova@beta
run ionic serve
That`s OK
but i run cmd:  ionic g component xxx
CMD console ERR:
[ERROR] Unknown plugin: @ionic/cli-plugin-.

g is currently not an alias for generate.  This is likely something we will add in the future.  Please me sure to take a look at the help and documentation.  The commands in v3 are not 1-to-1 parity for v2.  More documentation on the generate command can be found here: https://github.com/driftyco/ionic-cli/blob/v3/docs/generate.md


[frontend] Less chrome after scrolling

Another front end suggestion :+)
Taking a page out of mobile browsers, I think it would be nice for the nonessential chrome to move out of the way after a user scrolls on the site.
For example, scrolling on a results page of a search query would cause the navigation bar to slide up and be hidden. Perhaps scrolling up again makes the navigation bar chrome visible again, as it does in mobile browsers on iOS, but I would suggest only showing it on hovering over the tab bar again to toggle visibility of the navigation bar chrome.
i) More space for web content
ii) "Smart" browsers are, in my opinion, context-specific: only showing what is necessary at any time unless told by the user to show something extra
iii) Hovering over the tab bar should result in a manual toggle rather than a timed toggle, since the navigation bar disappearing again automatically when no action is taken would, in my opinion, be more annoying than helpful in this case

i.e. the navigation chrome would not simply disappear again after a couple seconds, even if the cursor is removed from the tab bar; only hide the navigation bar again after the user hovers over the tab bar once more or upon scrolling on the web page again

P.S. I tried running a test on macOS Sierra using npm test and received several warning messages in the terminal standard output. Before I open up another issue, though, I wanted to ask whether I was running the tests correctly.
I simply navigated to the master directory and, after having run npm build, I ran npm test and piped output to a file. I'e also recorded standard output from the Terminal for the session. I am considering opening up another issue since Electron becomes unresponsive during the tests after a while and I have to Force Quit the application after a while.
This is my first time trying to contribute to a project in what little ways I can, so I would really appreciate any help I could get so I can help this project! I'm really excited to see where Tofino goes, and want to be a part of that journey though I have little practical programming experience to contribute any changes myself to the project. :+)

We had something this a while ago, but removed it in favor of having simpler code for prototyping: https://twitter.com/jsantell/status/723265275911540737 We'll likely add it back soon.

Thanks for the suggestion!
This was too difficult to implement and was less useful on desktop than on mobile. WONTFIXing for now.

Thank you for considering the suggestion!
I hope I can at least try this out some day in the near future, but I can see how it might be less useful for desktop browsing than on mobile.
Have a great week!


SelectableText does not maintain start position when scrolled out of view

I am using a SelectableText.rich widget here. Half of this widget is in view, and the other half is out of view but inside the parent scrollable. Selecting the text scrolls the scroll view over to the right but does not preserve the start position of the selection.

I can reproduce the issue using the code sample below.
In my testing, this only reproduced on desktop platforms.

recordings

desktop
mobile

repro sample
import 'package:flutter/material.dart';

// generate lorem ipsum into variable called lopremIpsum
final loremIpsum =
    'Lorem ipsum dolor sit amet, consectetur adipiscing elit. Donec euismod, nisl sed aliquet ultricies, nunc sapien aliquam nunc, vitae aliquam nisl nunc eu nisl. Donec euismod, nisl sed aliquet ultricies, nunc sapien aliquam nunc, vitae aliquam nisl nunc eu nisl.' * 20;

void main() => runApp(const SelectionContainerDisabledExampleApp());

class SelectionContainerDisabledExampleApp extends StatelessWidget {
  const SelectionContainerDisabledExampleApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      debugShowCheckedModeBanner: false,
      theme: ThemeData(colorSchemeSeed: Colors.indigo, brightness: Brightness.light, useMaterial3: true),
      home:  Scaffold(
        appBar: AppBar(),
        body: SizedBox(
          width: 300,
          child: SingleChildScrollView(
            scrollDirection: Axis.horizontal,
            child: SelectableText(
               loremIpsum,
                style: const TextStyle(
                  fontSize: 14,
                  fontWeight: FontWeight.w400,
                  color: Colors.black,
                ),
              ),
          ),
        ),
      ),
    );
  }
}

flutter doctor -v
[!] Flutter (Channel stable, 3.10.5, on macOS 13.4.1 22F82 darwin-arm64, locale en-GB)
    • Flutter version 3.10.5 on channel stable at /Users/nexus/dev/sdks/flutter
    ! Warning: `flutter` on your path resolves to /Users/nexus/dev/sdks/flutters/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/nexus/dev/sdks/flutter. Consider adding /Users/nexus/dev/sdks/flutter/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/nexus/dev/sdks/flutters/bin/dart, which is not inside your current Flutter SDK checkout at /Users/nexus/dev/sdks/flutter. Consider adding /Users/nexus/dev/sdks/flutter/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 796c8ef792 (13 days ago), 2023-06-13 15:51:02 -0700
    • Engine revision 45f6e00911
    • Dart version 3.0.5
    • DevTools version 2.23.1
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0
    • Java binary at: /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/222.4459.24.2221.9971841/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3)
    • Xcode at /Applications/Xcode-14.3.0.app/Contents/Developer
    • Build 14E222b
    • CocoaPods version 1.12.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.2)
    • Android Studio at /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/222.4459.24.2221.9971841/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

[✓] Android Studio (version 2022.2)
    • Android Studio at /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/222.4459.24.2221.10121639/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

[✓] IntelliJ IDEA Ultimate Edition (version 2023.1.3)
    • IntelliJ at /Users/nexus/Applications/JetBrains Toolbox/IntelliJ IDEA Ultimate.app
    • Flutter plugin version 74.0.4
    • Dart plugin version 231.9161.14

[✓] IntelliJ IDEA Ultimate Edition (version 2023.1.2)
    • IntelliJ at /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/IDEA-U/ch-0/231.9011.34/IntelliJ IDEA.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] IntelliJ IDEA Ultimate Edition (version 2023.1.3)
    • IntelliJ at /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/IDEA-U/ch-0/231.9161.38/IntelliJ IDEA.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] VS Code (version 1.79.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.66.0

[✓] Connected device (3 available)
    • Pixel 7 (mobile) • adb-28291FDH2001SA-5Lv71w._adb-tls-connect._tcp. • android-arm64  • Android 13 (API 33)
    • macOS (desktop)  • macos                                            • darwin-arm64   • macOS 13.4.1 22F82 darwin-arm64
    • Chrome (web)     • chrome                                           • web-javascript • Google Chrome 114.0.5735.133

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

[✓] Flutter (Channel master, 3.12.0-11.0.pre.32, on macOS 13.4.1 22F82 darwin-arm64, locale en-GB)
    • Flutter version 3.12.0-11.0.pre.32 on channel master at /Users/nexus/dev/sdks/flutters
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 7dbdacff46 (8 hours ago), 2023-06-26 22:05:23 -0400
    • Engine revision f320b8c36f
    • Dart version 3.1.0 (build 3.1.0-246.0.dev)
    • DevTools version 2.24.0

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0
    • Java binary at: /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/222.4459.24.2221.9971841/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3)
    • Xcode at /Applications/Xcode-14.3.0.app/Contents/Developer
    • Build 14E222b
    • CocoaPods version 1.12.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.2)
    • Android Studio at /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/222.4459.24.2221.9971841/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

[✓] Android Studio (version 2022.2)
    • Android Studio at /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/222.4459.24.2221.10121639/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

[✓] IntelliJ IDEA Ultimate Edition (version 2023.1.3)
    • IntelliJ at /Users/nexus/Applications/JetBrains Toolbox/IntelliJ IDEA Ultimate.app
    • Flutter plugin version 74.0.4
    • Dart plugin version 231.9161.14

[✓] IntelliJ IDEA Ultimate Edition (version 2023.1.2)
    • IntelliJ at /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/IDEA-U/ch-0/231.9011.34/IntelliJ IDEA.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] IntelliJ IDEA Ultimate Edition (version 2023.1.3)
    • IntelliJ at /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/IDEA-U/ch-0/231.9161.38/IntelliJ IDEA.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] VS Code (version 1.79.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.66.0

[✓] Connected device (3 available)
    • Pixel 7 (mobile) • adb-28291FDH2001SA-5Lv71w._adb-tls-connect._tcp. • android-arm64  • Android 13 (API 33)
    • macOS (desktop)  • macos                                            • darwin-arm64   • macOS 13.4.1 22F82 darwin-arm64
    • Chrome (web)     • chrome                                           • web-javascript • Google Chrome 114.0.5735.133

[✓] Network resources
    • All expected network resources are available.

• No issues found!

/cc @chunhtai as this appears to be a text selection issue.

We have a similar issue, but for vertical scrolling:
https://github.com/flutter/flutter/assets/1283/87f0d20b-a649-43c4-bc25-39f0d78a04d7


Uncaught TypeError: Cannot read property 'previousSibling' of null

Hey I was trying to port my app to ember 1.13.1 and started getting this error when transitioning to other routes. I will try to make a jsbin later on, just posting this in case it is something known.
The error occurs here:
    removeRange: function removeRange(firstNode, lastNode) {
      var node = lastNode;
      do {
        var next = node.previousSibling; // <-- error from issue title

Ok I didn't manage to replicate it in a jsbin (don't know if/how it's possible to load the addon there) but here's a really simple example app: https://github.com/piotrpalek/wormhole-bug which shows the bug. You have to run the app and click the Second link and it will trigger the error.

@lukemelia I saw you looked at a similiar issue (https://github.com/yapplabs/ember-wormhole/issues/9) do you think this could be also ember related?

This should have been fixed with https://github.com/emberjs/ember.js/pull/11425 but you are hitting it in 1.13.1?  If so, I'd love some help tracking it down. If you could make a jsbin or fiddle replicating it would be greatly appreciated.  Also, if you can set a breakpoint in wormhole willDestroyElement to see if it is being called twice and include the stack trace of both calls that would be helpful.

@krisselden yes even in 1.13.2, I provided a link above to an example app, I am not sure how to setup a jsfiddle with an ember-cli addon (in this case ember-wormhole). Do you have some base jsbin where I could show the app, assuming the above github repo isn't enough?

@krisselden so the willDestroyElement method isn't called twice, but I noticed that here:
    willDestroyElement: function willDestroyElement() {
      var _this = this;

      var firstNode = this._firstNode;
      var lastNode = this._lastNode; // <-- the same as firstNode
      run.schedule('render', function () {
        _this.removeRange(firstNode, lastNode);
      });
    }

firstNode and lastNode is the same. So later in removeRange (where the error occurs):
    removeRange: function removeRange(firstNode, lastNode) {
      var node = lastNode;
      do {
        var next = node.previousSibling; // error occurs here, I assume that's because it doesn't have a previousSibling since it's the first node?
        if (node.parentNode) {
          node.parentNode.removeChild(node);
        }
        node = next;
      } while (node !== firstNode);
    }

@piotrpalek thanks, this is definitely then a wormhole bug.  Do you want to submit a PR?  I know that this code handles this case https://github.com/krisselden/morph-range/blob/master/lib/morph-range/utils.js#L10-L14

@krisselden I've made a PR, bus as noted there, I tried to write a test for this but when I bumped the ember version to 1.13 in the addon, other tests were breaking as well. So I couldn't really test this without fixing all of them.
I also will have to maintain a seperate branch with this fix applied to the 0.3.1 version of ember-wormhole, because master doesn't work with https://github.com/yapplabs/ember-modal-dialog which I am also using.


Customization

How can I style my charts ?

With the options object.
https://www.react-google-charts.com/docs/quick-walkthrough


Try type gurads

Bryon, I saw your comment and it looked like this might be a good use of type guards.
I haven't tested this, I'm not even 100% sure this is a good solution.  I'm more just interested in if you think this is better style or provides more safety.
Risks to this change:

Updating the interface but forgetting to update the guard.  They're defined next to each other, so hopefully this is mitigated.
Doesn't place enough trust in the type system. (similar to above)
Too generic, hurts readability.

LMK what you think.

I'll do a more in-depth review tomorrow morning but this looks similar to what I was thinking but I was a bit too lazy to look into implementation.
The one thing that still feel weird with the type guards is that it seems like you're double declaring the type.   I wish there was a better way to do it while utilizing the existing type.
Only other additional thing I think is that the types and functions for markChangesPending in useTypeStyling and useAttributes need to be modified.  The types were set to strictly be what they needed in each of the files.


Compiling DLL under VS2015 Preview

I've noticed that there is an issue in CCRakNetSlidingWindow.cpp where math.h is included rather than cmath which causes an ambiguous call to abs() and fails to compile. Just thought I would point this out.

Old comment, but thanks, that helped me successfully compile the solution :+1:


Disappearing survey prompt

The survey prompt popped while I was working but disappeared less than a second later while I was reading the title. I was typing at the time so perhaps it stole the keyboard focus and one of the keys I hit was interpreted as closing it?
Environment data
Version: 1.38.1
Commit: b37e54c98e1a74ba89e03073e5a3761284e3ffb0
Date: 2019-09-11T13:31:32.854Z
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Darwin x64 18.7.0

Not sure what might have happened as it's a VS Code thing, but you can fill the survey here if you wish: https://www.research.net/r/G7ZBPW7?o=[o_value]&v=[v_value]&m=[m_value]
Closing this.


[FLOC 644] Add algolia docsearch to the docs - DO NOT MERGE

Fixes 644
During the researching of why Sphinx markup was appearing in search results, we investigated Algolia docsearch and found it was a simple solution to the problem.

Sorry @davidoliverSP2 I have forgotten - how do I see the before-and-after for this fix?

This looks really good ❤
Does Algolia have any documentation on if this is possible without JS (a results page of some sort)? it may be nice to try and clear that up now. The search will not work without JS at the moment so don't let this hold you up from merging though.
@robhaswell http://clusterhq-staging-docs.s3-website-us-east-1.amazonaws.com/algolia-search-FLOC-644/

This works really nicely, thanks @davidoliverSP2! I'm happy for this to be merged unless @robhaswell or @msh100 have any other comments.

None from me.


Allow unstaked amount to be a number input and not unstake the entire staked amount.

Describe the bug
I currently wanted to unstake my staked SHDW (as I needed 100 SHDW) however I had no option to enter a number to unstake, I was forced to unstake the entire amount, to my surprise I had to wait a further 52 hours to withdraw, all I needed is a 100 SHDW. I didn't want to unstake the entire amount as I'm going to restake it in 51 Hours.
To Reproduce
Steps to reproduce the behavior:

Attempt to unstake the SHDW you have staked on incentivized testnet.

Expected behavior
When selecting unstake, simply allow the user to enter the amount they'd like to unstake. That should be withdrawable in 52hours.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

This is intended functionality.


Fixing Paths for Figures in mkdocs/quarto

The combination of mkdocs and `quarto' results in some minor issues.
The filepath of figures misses a ../ as mkdocs makes a directory with an index.md instead of a file.
This changes the relative path required wrt to one built by quarto.
In this PR I am trialing if the path manually adjusted in the markdown generated by quarto persists.

Worked!


Markers appear fuzzy

The markers appear fuzzy, probably to some non-integer offset when transforming them.
There should be some way to make markers keep integer offsets when transforming, altough this is probably not very easy to do without taking them out of the rotatePane and recalculating their positions on every bearing change.

Custom markers? The blue default markers of the simple example looks fine
to me?
On 27 Sep 2016 4:00 p.m., "Iván Sánchez Ortega"<EMAIL_ADDRESS>wrote:

The markers appear fuzzy, probably to some non-integer offset when
transforming them.
There should be some way to make markers keep integer offsets when
transforming, altough this is probably not very easy to do without taking
them out of the rotatePane and recalculating their positions on every
bearing change.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/fnicollet/Leaflet/issues/8, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABLtofYx_2K8ZQZRHZWFN49ztec0QPPhks5quSGHgaJpZM4KHs7L
.

Nah, they become blurry, at least on firefox, due to sub-pixel sampling or something. The problem disappears when the bearing is set at zero.

Thanks, cannot reproduce on Chrome, so that must be related to the
rendering engine being different in FF, probably the subpixel issue that
you know well :)
I'll try in FF with integer offset, see if that solve the issue but i am
afraid it would be from the parent container being rotated. Your suggestion
is to get the out of the rotatePane and place them in an absolute way?
On 27 Sep 2016 4:13 p.m., "Iván Sánchez Ortega"<EMAIL_ADDRESS>wrote:

[image: screenshot_20160927_160452]
https://cloud.githubusercontent.com/assets/1125786/18877110/68066e26-84cc-11e6-9aca-4b7329b23692.png
[image: screenshot_20160927_160452-zoomed]
https://cloud.githubusercontent.com/assets/1125786/18877109/67f854b2-84cc-11e6-9aa5-5bca6e1c3557.png
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/fnicollet/Leaflet/issues/8#issuecomment-249875366,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABLtoUQXrlXkzm637nI7MnIn0fZCvR0dks5quSMNgaJpZM4KHs7L
.

Closed now that #21 has been merged, which fix the issue by not rotating the markers


Dev

Updated to have xbox 360 open in full screen. Also updated the code to be more async friendly and added more tests.


Issues installing in Doom on macOS

Cool project!
Installation does not seem to work.
Running on macOS and doom. More info in the backtrace
- Using Emacs 29.4<EMAIL_ADDRESS>> Synchronizing "default" profile...
  > Regenerating envvars file
    ✓ Generated ~/.emacs.d/.local/env
  x There was an unexpected runtime error
    Message: Symbol's function definition is void
    Details: (transient-prefix)
    Backtrace:
      (transient-prefix :command 'kubed-transient)
      (put 'kubed-transient 'transient--prefix (transient-prefix :command 'k...
      (load-with-code-conversion "~/.emacs.d/.local/straight/bui...
      (load "~/.emacs.d/.local/straight/build-29.4/kubed/kubed-a...
      (progn (load autoloads-file nil 'nomessage))
      (if (file-exists-p autoloads-file) (progn (load autoloads-file nil 'no...
      (let ((autoloads-file (straight--autoloads-file package))) (if (file-e...
      (straight--load-package-autoloads "kubed")
      (let ((name (symbol-name package))) (add-to-list 'load-path (directory...
      (let ((package (car tail))) (straight-register-package package) (let (...
      (while tail (let ((package (car tail))) (straight-register-package pac...
      (let ((tail (cl-delete-duplicates packages :test #'equal))) (while tai...
GNU Emacs     v29.4            nil
Doom core     v3.0.0-pre       HEAD -> master cf7098528 2024-07-30 17:40:22 -0400
Doom modules  v24.09.0-pre     HEAD -> master cf7098528 2024-07-30 17:40:22 -0400
    ! Wrote extended backtrace to ~/.emacs.d/.local/state/logs/cli.doom.240804113500.28438.error
  ! Script was abruptly aborted, leaving Doom in an incomplete state!

Thanks for reporting!
I'm not very familiar with Doom, but I could reproduce this after some fiddling.
I pushed a commit that seems to fix it over here, could you update and give it another try?

Closing, let me know if you run into any other issue with Kubed, and thanks again for reporting!