[Feature Request] Add ability to re-order queued songs

Thank you for all your hard work. We love using your app!

Common problems that do pop up when singing with larger groups is the ability to reorganize songs that are within the queue. I'm not sure if I completely missed that functionality on my end, but if not, it would be huge if that could be an additional feature.

The other request is less of an issue, but just a nice-to-have. Since accounts are able to be created by anyone, would it be possible to allow access by username-only for non-admin accounts? Very minor, but also makes it easier when dealing with our non-technical singers 😄

Hi, appreciate the feedback! Can you elaborate on the issues you run into with large groups?
I do have some ideas for per-room settings which is what #2 would fall under, so will keep that in mind. Thanks!

I guess it's related to all singers actually, not just larger groups. But having the ability to move songs up in priority within the queue.
From what I can tell right now, if I add a song to the end of the queue that I REALLY want to sing for my next song then I would need to delete all the songs that are queued prior to that song. Then go back and add the removed songs back, instead of just having the ability to re-order my song queue and move songs around in the queue without needed to remove.
Thank you again! It's a great service!

Thanks and agreed, depending on the implementation this will probably be a post-1.0 feature, but I would like this as well.

Having hosted my first karaoke-forever powered party last night, I believe that queue re-ordering is sort of a critical feature.  I think an option to have it be 'admin-only' or open to everyone would be nice, but at least enabled for admins.  The very common problem situation is someone who, upon opening the app for the first time, queues up 5 songs while everyone else is getting their situation sorted.   then it's tricky to make sure everyone gets a shot without deleting all their new stuff.  definitely related to another issue about needing to be able for an admin to jump forward and back within the queue at will, in order to keep everyone happy.

Just curious if this has been addressed yet. I have been hesitant on hosting a party because of this issue.

@consolecwby Which issue are you referring to? Just to clarify, this:

The very common problem situation is someone who, upon opening the app for the first time, queues up 5 songs while everyone else is getting their situation sorted.

does not actually happen, as the queue is not first-come-first-serve.

(Longtime lurker, first time caller! Love this project.)
I'm working on a change to address this issue, and just wanted to mention it here ahead of lobbing the PR over the wall, in case there is major directional feedback.
Here are three modest issues we ran into while hosting a party, that relate to this issue:

Surprise re-orderings. What would happen is a non-recent-singer would add a track to established queue, only to find they're up immediately next - sometimes in a matter of seconds! This was a sort of dual-whammy of bummer to two people: It minorly terrified the timid participant who just added the track ("oh crap, I have to go NOW?!"), and on the flip side cooled the mojo of the person who was expecting to be next ("hey what i got snaked? i was all hyped and ready!")

(I can see solutions for this that don't require what I propose.)

No support for a "reorder" operation. OP's original idea here. Our example: For the "whales" of a queue — those that have several songs queued at once — it's great that the fairness algorithm makes sure they don't drown out others. However, sometimes as one of those whales, you change your mind and want to sing a different song first. (Or you simply find, in the library, a better choice for "next" for the current moment.) It would be great if folks could say, "I changed my mind, let me sing item 5 before item 9".

The workaround here is to delete all your queued songs, then re-insert in preferred order

Guest account starvation. A handful of folks ended up sharing a tablet for getting their songs enqueued; which of course meant that N guests only get to go 1/N as frequently as a "real" user. At worst, it would be nice if an admin could reorder things.

Happily, I think there is a modest common solution to all of these: Set & use a position value server-side, in the queue table. My change adds this column in a migration; shifts the "fairness" logic to be applied on queue insertion; and updates clients to use server-side order as-is.  Please shout if you see major issue with this approach.
Thanks again to @bhj + contributors - super fun project!

Big thanks for the kind words and thoughtful comments @mik3y!

I agree this can be surprising at first. Newcomers being able to sing ASAP is a pretty core feature though, and if queue positions are locked in at ToQ (time-of-queueing) :) are we not back to them potentially waiting a long time?  I'd like to keep the queue order as a view on top of the first-come-first-serve DB table, but that doesn't preclude having other views. Open to suggestions for sure.

I plan to add a "make next" option - it won't be perfect, and the fairness algorithm will still apply, but it should cover 90% of the use cases here.

The shared device situation is interesting; we need some way to differentiate users, but having to sign out and back in for each handoff isn't great, whether using guest accounts or not. Definitely thinking about this though.

I really appreciate the development of this thread and I apologize for my inaccurate comment about multiple consecutive songs above.  I hadn't fully experienced the 'smart queue' functionality at that point, and appreciate the 'fairness' piece that goes in to how the next song is currently determined.  And I definitely agree with the points about guest accounts/shared devices, etc - at more informal karaoke parties it can be difficult to convince folks they need to go find their own phone, create an account, etc, no matter how ready and willing they are to sing.  (In fact, I've found that 'willingness to sing' is often inversely proportional to 'can perform specific operations on my phone'.)
These both seem to point at a spectrum of events where KF could be used.  At one end is a bunch of strangers, each with their own phone, running the show amongst themselves.  For that, the current model does great at ensuring equity.  The opposite would be if someone is being a full-on KJ, managing the queue, taking 'guest' requests, etc.. in which case a whole new set of features is required for smooth operation.
My personal experience is heavily slanted towards the later, but somewhere in the middle is the dream - an admin role that can add/reorder at will to make any necessary corrections to keep the party flowing (the perfect 'next song' request even if that person doesn't have their phone handy, the person who should be moved up, the person who just went to the bathroom, etc) - while still allowing an admin to step away from the system for a while (users can still browse/add/reorder their own tracks) and have the party run itself in a relatively fair way (the smart queue ordering).
Trying to cover such disparate use cases (and there are probably several more that would be worth hearing about!) has a big impact on overall scope/design/roadmap of course, so I want to be respectful of the original direction of this project (and available development bandwidth).  At the same time, I'm super excited and impressed about the technical guts of the project so far and how well the network/playback/multiuser capabilities work.  I'd love to be able to use KF for the full-on KJ hosted stuff too.
Anyway, thanks again for setting this all in motion and look forward to contributing how/when I can.

Thanks @crosstopher, and you're exactly right, there is friction between the app being designed to act as the KJ, and a KJ wanting complete control. My goal for v1.0 is to make the former case the best it can be without impacting the latter (hopefully even improving the latter a bit). For example, the "make next" button on an upcoming song could become "add again" on a past song, so if one is skipped for whatever reason it's at least easy to add again.
Hopefully some KJs will be receptive to the "whoever's gone the longest without singing is next" strategy; I think it's a strength but some will surely find it a weakness.

Hey all, v1.0 has been released and has some new features to address these excellent points:

Once a user is told they're "up next", their slot gets locked-in and won't be pre-empted. So if someone joins and queues their first song, they'll be behind the already "up next" user instead of bumping them. This should help the "shy guy/surprise syndrome" while still getting newcomers near the front.
Users (and admins) now have a "Make user's next" button, for the "just found this and want to sing it ASAP" use case. Note that it does not affect a user's place in the queue; the fairness algorithm still applies.
Users (and admins) now have a "Re-queue" button. If someone is skipped for any reason, they are two taps away ("Re-queue" + "Make next") from getting back to where they were.

While this won't cover 100% of cases, I think for now it's a good balance between complexity and flexibility. Thank you to everyone for contributing to this thread!


AtlasTexture does not update scene and editor after change

Godot version:
3.0.2 stable
OS/device including version:
Editor on Mac, I assume it happens on all systems.
Issue description:
AtlasTexture references and previews in editor don't update after editing.
Same happens when importing updated AtlasTextures.
Steps to reproduce:

Create AtlasTexture from any Texture
Save AtlasTexture
Change AtlasTexture's region
See that the editor does not update

See video here:  https://youtu.be/9bps9jkSKhM
Minimal reproduction project:
AtlasTextureUpdateBug.zip

For got to say: The same thing happens if you use an importer to load the assets.
Might also need a refresh like the TileSet in this ticket: #17274


adding identifiers.org identifiers as digital identifiers

cf scheme:
https://docs.identifiers.org/articles/docs/identification_scheme.html
should definitely be an option for DSV digitial identifier (example neurovault). potentially also elsewhere?
@apdavison @bweyers @UlrikeS91 @skoehnen @olinux @jagru20 please comment

Draft in #378


Impossible to disable the new source control action bar

I found myself never saying "yes" to the new "Would you like to add this file to version control?" action bar.
It's actually starting to bother me, and I'd like to disable it.
SourceControl has one setting "Never create a commit when moving, deleting, etc.", I have it checked.
However, when I try to delete something, for example, I get a confirm dialog "would you like to remove the file(s) from version control". So the setting doesn't appear to be working.
I'd like to know what is "etc." - is it supposed to include adding a file (and so the add to version control action bar)? If yes, it's also broken. If not, I think an extra setting to be able to disable the action bar is needed.

So how are we going to move forward with this? @Neverbirth


LineConnectionForces/Resultant

How do we plot the value ?
Do we have all the right information?
Make sure to be able to plot the reaction forces as FEM-Design does.
LocalAxis are missing.
We have the normal, we have the x axis, we need to write those on the edge connection object and compute the Y axis
<edge type="line">
<point x="4" y="2" z="0"></point>
<point x="4" y="4" z="0"></point>
<normal x="-1" y="0" z="0"></normal>
<edge_connection guid="668e2cce-8ed9-41b1-8c1c-d72f4cf6a328" last_change="2022-11-02T11:35:14.000" action="added" name="CE.1" joined_start_point="true" joined_end_point="true">
	<!--edge description: "P.1.CE.1" -->
	<rigidity>
		<motions x_neg="10000000" x_pos="10000000" y_neg="10000000" y_pos="10000000" z_neg="10000000" z_pos="10000000"></motions>
		<rotations x_neg="0" x_pos="0" y_neg="0" y_pos="0" z_neg="0" z_pos="0"></rotations>
	</rigidity>
</edge_connection>
</edge>

https://strusoft.freshdesk.com/a/tickets/25690


python3Packages.boltztrap2: 19.1.1 -> 19.7.3

Motivation for this change
noticed it was broken on master while reviewing #66023
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @
[3 built, 4 copied (19.1 MiB), 3.7 MiB DL]
https://github.com/NixOS/nixpkgs/pull/66035
1 package were build:
python37Packages.boltztrap2

./results/python37Packages.boltztrap2/bin/btp2 --help
you can install pyfftw to get better FFT performance
vtk not found. The 'fermisurface' command will be disabled
usage: btp2 [-h] [-v] [-n NWORKERS] [-V] command [options] ... ...

bunch of scientific libraries, large closure is expected.
$ nix path-info -Sh ./results/python37Packages.boltztrap2
/nix/store/l2cyqahdg6m9z8j4lmlzy1dwlkf3k7mf-python3.7-BoltzTraP2-19.7.3  551.6M

@FRidh applied changes :)


Pass external to esbuild in the Cloudflare adapters

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[x] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[x] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[x] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

Some external modules rely on NodeJS modules, such as fs. This causes problems during npm run build, even if my code does not rely on the respective code-path that requires any problematic modules (like fs). For me, this is the case with ical-generator.
This change is inspired by the already existing functionality in the Vercel adapter, that accomplished the same:
https://github.com/sveltejs/kit/blob/b251b235b321b9c75236429cc3a1ac2415475775/packages/adapter-vercel/index.d.ts#L56-L75
Respectively:
https://github.com/sveltejs/kit/blob/b251b235b321b9c75236429cc3a1ac2415475775/packages/adapter-vercel/index.js#L111-L124
The only related issue that I've found was https://github.com/sveltejs/kit/issues/6547, which was resolved because Stripe changed their implementation. This is the ideal resolution, I admit, but the world is not ideal as far as I'm concerned.

Related
https://github.com/sveltejs/kit/pull/10214
https://github.com/sveltejs/kit/pull/10110

Oh, I didn't check the PRs before 😅 At least, there seems to be a need.

I've applied the requested changes and rebased onto the latest master.

Related
https://github.com/sveltejs/kit/pull/10214
https://github.com/sveltejs/kit/pull/10110

Thanks for tracking those down. I've closed them in favor of this PR, which seems closest to being ready

Closing this in favor of https://github.com/sveltejs/kit/pull/10521


poc: rpc prop tests

Starts to address #1078 .
I think this logic can probably be simplified a fair amount wrt. reducing the # of switches. I think adding wrapper types with their own validity-checking functions would also help for that; handling proto enums makes the test a lot larger, but I think most of the REST endpoints will have enum fields to support arguments as strings.
Rapid has some functions to autogenerate values via reflection: https://pkg.go.dev/pgregory.net/rapid#Make
I'm not sure if that will populate the gRPC private fields like state, unknownFields, etc. IIUC we don't want those to be populated.
This small test found some missing checks, which would probably get rejected later on. Will peek at other RPCs with more fields to test out more complex invariants.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>0
Details

18 of 65 (27.69%)  changed or added relevant lines in 1 file are covered.
17 unchanged lines in 5 files lost coverage.
Overall coverage increased (+0.09%) to 40.253%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

rpcserver.go
18
65
27.69%

Files with Coverage Reduction
New Missed Lines
%

commitment/tap.go
1
83.64%

tapdb/addrs.go
2
79.04%

rpcserver.go
2
0.97%

asset/asset.go
2
81.73%

universe/interface.go
10
51.12%

Totals

Change from base Build<PHONE_NUMBER>4:
0.09%

Covered Lines:
23742

Relevant Lines:
58982

💛  - Coveralls

I think this is in a decent state for now - this change to rapid made gRPC message generation much more ergonomic:
https://github.com/flyingmutant/rapid/pull/72
I'd prefer to block merging this until that PR (or something similar enough) lands in a rapid release. We could pull in the fixes in a separate PR if needed.


fix: set alias for /function(s)?/ to highlight it as "function"

Summary
Regexes don't appear in the AST, so in lambdas "function" and "(" can not be highlighted properly.
Solution: replace regex by equivalent tokens.
Requirements (place an x in each [ ])

[x] I've read and understood the Contributing Guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.

FWIW this doesn't seem right to me. The function in (function(int): int) is part of a type hint, so I wouldn't expect function to be treated as a keyword here. The other syntax highlighters for Hack don't treat it as a keyword.

I guess it makes sense to parse function as a separate token here, but I'd highlight it differently to function in global function or method declarations.


md-*-text-field focus() does not work

What is affected?
Accessibility, Component
Description
.focus() method called on md-*-text-field instance returns undefined, but does not do anything.
Reproduction
Lit.dev repro
Workaround
Would be great to know how it can be worked around
Is this a regression?
No or unsure. This never worked, or I haven't tried before.
Affected versions
1.4.1
Browser/OS/Node environment
Tested on Firefox 127.0b2 (64-bit) and Chrome Version 124.0.6367.207 (Official Build) (x86_64)

It looks like you're calling textField.focus() too early before the custom element is upgraded by the browser. Try waiting for customElements.whenDefined() and textField.updateComplete before focusing.
reportFocus();

customElements.whenDefined('md-filled-text-field').then(async() => {
  await textField.updateComplete;
  textField.focus();
  reportFocus();
});

After the lit.dev playground loads, press the refresh button (focusing in iframes is a bit weird) https://lit.dev/playground/#gist=977b358fe1b2176685160bd2c4b7bf08
Let us know if that helps!

That seems to be working, thanks!


Request: Translation Update

Hello team,
I have noticed that there are two different expressions for one word, nudge.
MyAnalytics nudges should be translated as MyAnalytics ナッジ and the current translation in this page is 微調整 or シェイク.
Could you kindly update the translation to ナッジ as soon as possible?
Thank you .
With best regards,
Haruka

ドキュメントの詳細
⚠ このセクションを編集しないでください。 docs.microsoft.com で必須です ➟ GitHub の問題のリンク。

ID: ae5243bf-bda7-c9a6-1f36-7c011e17988b
Version Independent ID: 5e5ff830-dc34-73e6-670d-acf9d5617b90
Content: Outlook で微調整する MyAnalytics - Workplace Analytics Office 365
Content Source: WorkplaceAnalytics/MyAnalytics/Use/mya-notifications.md
Product: mya
GitHub Login: @buntus
Microsoft Alias: patboony

Thank you Haruka,
We have requested a new translation of this topic. I will update this thread to report on additional progress. We appreciate your interest in this content.

MyAnalytics documentation team

Hello Haruka,
Thank you again for notifying us of this issue. We have corrected the translation. You can see the fixed topic here.

Hello Paul,
Thank you very much for taking care of the issue!
Haruka
From: Paul Schafer<EMAIL_ADDRESS>Sent: Tuesday, December 18, 2018 2:23 AM
To: MicrosoftDocs/OfficeDocs-WorkplaceAnalytics<EMAIL_ADDRESS>Cc: Haruka Sakamoto (Accenture<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/OfficeDocs-WorkplaceAnalytics] Request: Translation Update (#29)
Closed #29https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FOfficeDocs-WorkplaceAnalytics%2Fissues%2F29&data=02|01|v-hasa%40microsoft.com|83e95ded9bb44552293408d664443f15|72f988bf86f141af91ab2d7cd011db47|1|0|636806641612197331&sdata=YtR8l7T47vHBUmKUroH3o19DnzB5QmjZ5o%2B5pVpzStw%3D&reserved=0.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FOfficeDocs-WorkplaceAnalytics%2Fissues%2F29%23event-2030878964&data=02|01|v-hasa%40microsoft.com|83e95ded9bb44552293408d664443f15|72f988bf86f141af91ab2d7cd011db47|1|0|636806641612207331&sdata=%2BfM%2BieRNpopQzMX5Gj5qKyAx6fycA5Nx2XHKDoYiRG4%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAoaE-Vj4O6qAAvqrRqFs_ttggQDldnf2ks5u59LfgaJpZM4ZH2s0&data=02|01|v-hasa%40microsoft.com|83e95ded9bb44552293408d664443f15|72f988bf86f141af91ab2d7cd011db47|1|0|636806641612217343&sdata=7I%2Fo8Iq%2F8hKEuyf7FUPpO%2FJ6AIl9qY4hKogMLYWFbFQ%3D&reserved=0.


Add component token usage per characteristic to site docs

Adds to the token page a table of all usage of a certain characteristic - e.g., 'actionable' characteristic is used by  "Accordion", "Button", "ToggleButton", "Dropdown"... etc
It also generates which components use the foundations directly, (e.g. z-index is used by "Badge", "Checkbox", "RadioButton", "Switch"... etc) which we may want to utilise in the future
As well as educating consumers how components relate to the theme, this PR will help designers to easily identify which components will be affected by the changes they make in the theme at a characteristic level
It will be helpful to identify the same for the palette layer, which is the true layer the theme would be customised at by designers, cc @dplsek @Jiempreecha

Thanks for the pr @libertymayc, I think this needs to feed into how we think theming should work and the best way to show users. Therefore more discussion is needed before we merge this.

Thanks for the pr @libertymayc, I think this needs to feed into how we think theming should work and the best way to show users. Therefore more discussion is needed before we merge this.

agreed :) the meeting today should start the discussion on this but will ofc need a few conversations

We're currently looking into how we document the theme, characteristics, foundations and other design language-related work. We'll refer to this as a potential direction, but it's unlikely we'll take this PR directly. I'll close this for now. Thanks @libertymayc


Fix sites/test_ec2 failure when aws user opts specified

Previously, if no AWS user opts were specified, then
the tests in sites/test_ec2.py were skipped (due to a
key error on importing the ec2 config); but if AWS
user opts were specified, then the tests would run
in non-local mode.
This commit changes the test so that it runs with a
locally defined config.
This test runs in local mode if suitable AWS configuration
is made - which at the moment is a more awkward than
setting the user opts for AWS.
This looks like it was messed up in a combination of
PR #1210 (which replaced the local mark with a noci mark)
and PR #1230 (which remoed the noci mark)

Looks like this fails when there isn't a public_ip user option specified... in other places such a condition causes the test to be skipped, rather than causing an exception.


BugSnag Error Boundary Not Logging Error in Bugsnag

Hi
I have this
bugsnagClient.use(bugsnagReact, React)
const ErrorBoundary = bugsnagClient.getPlugin('react')

<ErrorBoundary FallbackComponent={ErrorFallbackComponent}>
    <AppContainer />
</ErrorBoundary>

export const ErrorFallbackComponent =  () =>
An error has occurred

However I noticed only error that I actually do  bugsnagClient.notify(new Error(error.errorMessage));
I am wondering if I have to add  bugsnagClient.notify(new Error(error.errorMessage)); into my error boundry and if so how?

Hi @chobo2, what errors are you expecting to see in Bugsnag that aren't showing?
By default Bugsnag will report:

unhandled exceptions
unhandled promise rejections

And with the react integration you're using:

render errors from react components

You don't need to put a notify() call in your error boundary – we sent the report for you.
Let us know some more information about your setup and what kind of errors you're expecting to see and we'll be able to help. Cheers

@bengourley
Ok, well I am seeing some random errors that are occurring because of Mobs state tree  when it tries to reference something it thinks is a duplicate.
The error is random and seems to happen when I don't have my debugger open so that's how I noticed that bugsnag was not logging it.
I will try to try to get the error message next time it happens and report it here.

We've seen a similar issue with redux-saga where it swallows an error and then logs it to the console with console.error() so Bugsnag never sees it. The solution there was to hook in to Redux's error handler function.
I would suggest taking a look at the onError() and onReactionError() options of MobX (on this docs page) and connecting those up with Bugsnag.
Essentially Bugsnag will report any unhandled exception, or unhandled promise rejection – so if an error is not handled by anything else it will be reported. If it is caught and logged to the console it won't be reported.
I'm going to close this off until this can be reproduced.


Link to deployed app

If we could get the info of the related pull-request, that would be easier with
our deployment on netlify!

this is solved by showing the Netlify Build Status which provides the link to the deployed site ! 😄


Add metrics-server

Problem
For the load test, we need to be able to get the equivalent of kubectl top pod
Solution
Add metrics-server.

https://github.com/kubernetes/kube-state-metrics should already contain the equivalent of kubectl top by default under the containers_ namespace. I'm not sure whether https://github.com/simskij/kube-metrics-k8s-operator is in a working state or not, but could serve as a starting point (or even just deploying kube-state-metrics manually.

Unfortunately, those metrics (the entire containers_ namespace, actually, and the baseline requirement for top pod) actually comes from metrics-server, not kube-state-metrics. The closest we can get there is kube_pod_container_resource_requests, and that's pretty fuzzy.
The incoherence of the philosophers k8s monitoring. node_exporter, metrics-server, and kube-state-metrics are required to get a full overview. The existing charm only provides 2 out of 3, but metrics-server could be a fair addition to get started.
For certs/tokens, I did at least remember that the kubeconfig has them, in which case what sort of microk8s we're running doesn't matter, and you can also snatch the token (if RBAC is enabled) out of it. Pulling them out of the kubeconfig (.clusters.cluster.certificate-authority-data and .users.[i].user.token are just base64ed and are otherwise usable) is probably a good way to go.
Originally posted by @rbarry82 in https://github.com/canonical/cos-lite-bundle/issues/65#issuecomment-1446233520

@simskij @rbarry82
Currently, metrics-server starts with
/metrics-server --cert-dir=/tmp --secure-port=4443 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --kubelet-use-node-status-port --metric-resolution=15s --kubelet-insecure-tls

And $ curl -k <IP_ADDRESS>/metrics works.
And logs:
secure_serving.go:266] Serving securely on [::]:443
scraper.go:140] "Failed to scrape node" err="Get \"https://charm-dev-2cpu-7g:10250/metrics/resource\": dial tcp: lookup charm-dev-2cpu-7g on <IP_ADDRESS>:53: no such host" node="charm-dev-2cpu-7g"

Questions:

If it starts with --secure-port=4443 then why Serving securely on [::]:443
What exactly needs to be done with certs/rbac?

Somewhat misleading. secure_serving.go in the k8s apiserver, which presumably restarted.
The rest of the flags come from default flags (similar to argparse, sort-of), which are at least partially defined here.
For certs/rbac, the CA for the k8s API server (if we want to verify it from Python) is in the kubeconfig, as is the token. A lot of k8s uses user tokens/client certs to determine "does this user have access to that object?" kubectl ... passes your user token, so you don't need to think about it, but the top answer from this SO post describes how to use it via curl. If it's on the same system or you can curl anyway, you probably don't need a service, but it's basically b64decoding 2 fields and using one as a header and one as the cert.

Can't make as not a draft :| Or approve the workflow

Can't make as not a draft :| Or approve the workflow

but i can (and did)! 😂


Quiz Taker for Logged-In Users

User Story:
As a logged-in user, I want to be take quizzes, so that I can solidify my understanding of a topic and learn where I can improve.
A/C:

Given the user is viewing a list of quizzes; When they click on a quiz's "Take" button; Then they are taken to a page to answer the quiz's questions.
Given a user is taking a quiz; When they are viewing a question; Then they should see "like" or "dislike" buttons.
Given a user has finished their quiz; When they click on a quiz's "finished" button; Then they are taken to a page to view their results.

It is agreed to remove acceptance criteria for the Like and Dislike buttons at this time.

Pull request #26 is merged and ready to continue to the edit quiz and test story.


IGR Path works only for memory card

Issue checklist
Note: these are not necessarily requirements

[X] I have checked existing OPL issues for duplicates and found none @ http://psx-scene.com/forums/official-open-ps2-loader-forum/ & https://github.com/ifcaro/Open-PS2-Loader/issues

Issue description - Describe the problem you are having
"IGR Path" does not work for HDD or USB (probably also for ETH),
while everything is fine for memory card(s) no matter if ELF is in 1st or in 2nd slot.
Actual result
Enter in IGR Path e.g. mass:/OPL/OPL_1392.ELF,
after triggering combo (L1+L2+R1+R2+Start+Select)
I'll get red debug screen and It'll kicks me back into FMCB browser
The same thing is for HDD, I've tried:
pfs0:/+OPL/OPL_1392.ELF
hdd0:/+OPL/OPL_1392.ELF
Also I'll get red debug screen meaning that the path is wrong or probably unsupported.
Once again I'm getting kick out into FMCB Browser.
IGR Path works for memory card(s) from both slots e.g.
mc0:/APPS/OPL_1392.ELF
mc1:/APPS/OPL_1392.ELF
After triggering combo I'm getting light blue debug color
and the ELF typed in IGR Path will launch.
Additional inconvenience
IGR Path supports only up to 31 signs\letters.
There is no additional info that there is something wrong with path.
Additional request
Instead of typing path for IGR, some kind of file manager will be useful
to select wanted ELF.

Memory is wiped before booting your ELF and only basic modules are init, its probably possible to check exit path after mem wipe before loading ELF and init required modules but there may be a good reason this isn't already done? potential for module conflict with your new ELF? loading times?
@sp193 would have a good idea as to whether its a good idea to do this or not.

This has always been the case, and years ago, I made a thread on PSXSCENE asking why Mass and HDD weren't valid IGR paths. If I recall correctly, SP193 said that after an IGR, the handles to both are null and void. Physical memory cards are unaffected.

The problem is that we have no way to load an ELF from any device. Memory cards are an exception because you can get the necessary modules from the boot ROM.
Perhaps you could load the USB modules from the SYS-CONF directory on the memory card, which is where FMCB stores those modules.

@sp193 could that configs be saved into VMC on create and load these configs from there?


style: :art: Changing favicon to a star

Resolve #20
I'm excited to be part of this open-source project and eager to contribute more in the future. This pull request is just the beginning, and I look forward to collaborating on further improvements and enhancements.

@all-contributors please add @dimassibassem for design


Realization

merging implementation and tests

Please, remove all configs files and add them into .gitignore to prevent them from leaking in the future

removed all configs files


Current criteria to identify local interactive users is based solely on uid range in /etc/login.defs

Describe the Issue
Current criteria to identify local interactive users is based solely on uid range in /etc/login.defs.  The set of local interactive users should also exclude local user accounts with shell set to /sbin/nologin in /etc/passwd.
Expected Behavior
When performing RHEL-08-020352 task, only local interactive user accounts should be enumerated over.
Actual Behavior
The RHEL-08-020352 task enumerates over other non-local interactive user accounts.
Control(s) Affected
RHEL-08-020352
RHEL-08-010730
RHEL-08-010731
RHEL-08-010740
RHEL-08-010750
Possible Solution
Recommend initializing fact, rhel8stig_passwd_interactive, based on value of rhel8stig_passwd, but with filter applied to exclude entries with /sbin/nologin shell and users with uid >= rhel8stig_interactive_uid_start and <= rhel8stig_interactive_uid_stop.  Then, in fix-cat2.yml, replace templated expressions referencing rhel8stig_passwd with rhel8stig_passwd_interactive, for all controls targeting local interactive user accounts.

hi @prestonSeaman2
hi @prestonSeaman2
Thank you for your patience on this issue, with so many moving parts its taken longer than we'd hope. I hopefully have now addressed interactive users issue to work more consistently in a manner that makes sense.
I have created a new branch April_24, which i am hoping to merge into devel soon. If you could possibly confirm this works as you expect?
Many thanks
uk-bolly


norm axiswise broken for Overlays inside DynamicMaps

Take this function
offset = 0

def plot_generator(overlay):
    global offset
    while True:
        ys = np.random.rand(10) + offset
        offset += 0.1
        if overlay:
            yield hv.Curve(ys) * hv.Scatter(ys)
        else:
            yield hv.Curve(ys)

get_dm = lambda overlay: hv.DynamicMap(
    plot_generator(overlay), streams=[hv.streams.Stream.define("Next")()]
).opts(norm=dict(framewise=True))

Now everything is fine like this:
dm = get_dm(overlay=False)
dm

dm.periodic(0.5)  #next cell

gives:

But when there is an overlay, it doesn't work:
dm = get_dm(overlay=True)
dm

dm.periodic(0.5)  #next cell

gives:

This blocks https://github.com/python-adaptive/adaptive/pull/186/.

Overlays do not currently support normalization options. I propose that an Overlay have framewise=None by default, and if it's set to True it would behave like .map(lambda obj: obj.opts(framewise=True), hv.Element).  I think the semantics of that are clear, though @philippjfr indicates it won't be very straightforward to implement.
Given that Overlay is a type of Layout, it may make sense to do this at the Layout level, as people presumably would want to set the options on Layouts as well.  In that case we can also consider whether axiswise=True should behave the same.  I think so, but haven't thought deeply about it.

+1


adds 3 box arts for Japan-region games

Guilty Gear X, King of Fighters 2002, Capcom vs SNK2

Hello!
Sorry I missed this. Lots of turmoil here.
It's failing on build and idk why. I'll investigate this week


reduce.js - emit initial mark on first batch start

To be consistent with batch | reduce, reduce -every should emit an
initial mark at the start of first batch.
Fixes #537, #538

cc: @demmer @dmajda

+1

Fixed the comment, will merge on green.


test: better cluster setup output handling

When executing long-running shell scripts on the nodes, the output was
printed in large chunks infrequently. That made it impossible to
really see what's currently happening. Now each line is printed as
soon as it is produced and also gets a time stamp.
swupd prints carriage return characters as part of the download
progress reporting. This used to overwrite the prefix with the node
name. Now those characters are removed before printing. Download
progress ends up producing many lines (one for each update), but
fixing that would require further special handling, so this has to be
good enough for now:
...
09:04:35 pmem-csi-clear-govm-worker2: Downloading packs (398.85 Mb) for:
09:04:35 pmem-csi-clear-govm-worker2: - cloud-native-basic
09:04:35 pmem-csi-clear-govm-worker2: - containers-basic
09:04:35 pmem-csi-clear-govm-worker2: - git
09:04:35 pmem-csi-clear-govm-worker2: - curl
09:04:35 pmem-csi-clear-govm-worker2: - less
09:04:35 pmem-csi-clear-govm-worker2: - iproute2
09:04:35 pmem-csi-clear-govm-worker2: - storage-utils
09:04:35 pmem-csi-clear-govm-worker2: - smartmontools
09:04:35 pmem-csi-clear-govm-worker2: - samba
09:04:35 pmem-csi-clear-govm-worker2: - perl-basic
09:04:35 pmem-csi-clear-govm-worker2: - python3-basic
09:04:35 pmem-csi-clear-govm-worker2: - lib-samba
09:04:35 pmem-csi-clear-govm-worker2: - dosfstools
09:04:35 pmem-csi-clear-govm-worker2: - nfs-utils
09:04:35 pmem-csi-clear-govm-worker2: - openldap
09:04:35 pmem-csi-clear-govm-worker2: - parted
09:04:35 pmem-csi-clear-govm-worker2: - pmdk
09:04:35 pmem-csi-clear-govm-worker2: - xfsprogs
09:04:35 pmem-csi-clear-govm-worker2: 	...0%
09:04:35 pmem-csi-clear-govm-master: 	...8%
09:04:35 pmem-csi-clear-govm-worker1: 	...1%
09:04:35 pmem-csi-clear-govm-master: 	...9%
09:04:35 pmem-csi-clear-govm-worker2: 	...1%
09:04:36 pmem-csi-clear-govm-worker1: 	...2%
09:04:36 pmem-csi-clear-govm-worker2: 	...2%
09:04:36 pmem-csi-clear-govm-worker3: Downloading packs (398.85 Mb) for:
09:04:36 pmem-csi-clear-govm-worker3: - cloud-native-basic
09:04:36 pmem-csi-clear-govm-worker3: - containers-basic
09:04:36 pmem-csi-clear-govm-worker3: - git
09:04:36 pmem-csi-clear-govm-worker3: - curl
09:04:36 pmem-csi-clear-govm-worker3: - less
09:04:36 pmem-csi-clear-govm-worker3: - iproute2
09:04:36 pmem-csi-clear-govm-worker3: - storage-utils
09:04:36 pmem-csi-clear-govm-worker3: - smartmontools
09:04:36 pmem-csi-clear-govm-worker3: - samba
09:04:36 pmem-csi-clear-govm-worker3: - perl-basic
09:04:36 pmem-csi-clear-govm-worker3: - python3-basic
09:04:36 pmem-csi-clear-govm-worker3: - lib-samba
09:04:36 pmem-csi-clear-govm-worker3: - dosfstools
09:04:36 pmem-csi-clear-govm-worker3: - nfs-utils
09:04:36 pmem-csi-clear-govm-worker3: - openldap
09:04:36 pmem-csi-clear-govm-worker3: - parted
09:04:36 pmem-csi-clear-govm-worker3: - pmdk
09:04:36 pmem-csi-clear-govm-worker3: - xfsprogs
09:04:36 pmem-csi-clear-govm-worker3: 	...0%
09:04:36 pmem-csi-clear-govm-worker2: 	...3%
09:04:36 pmem-csi-clear-govm-master: 	...10%
09:04:36 pmem-csi-clear-govm-worker1: 	...3%
09:04:36 pmem-csi-clear-govm-worker2: 	...4%
09:04:36 pmem-csi-clear-govm-worker3: 	...1%
...

The output does not look entirely reasonable.
I saw about 25 minutes of full-speed-scrolling output as this (below), from all nodes and master.
Those percent numbers started at low values but went up, and those values dont seem reasonable at all.
I did not count lines but there were millions, estimating by speed and time.
Just emitting those lines likely adds lot of overhead to duration.
For me, this is not just improvement over what we had.
Any way avoiding those silly lines which don't carry any useful information?
11:31:48 pmem-csi-clear-govm-master:    ...613290%
11:31:48 pmem-csi-clear-govm-master:    ...613303%
11:31:48 pmem-csi-clear-govm-master:    ...613317%
11:31:48 pmem-csi-clear-govm-master:    ...613331%

Olev Kartau<EMAIL_ADDRESS>writes:

The output does not look entirely reasonable.
I saw about 25 minutes of full-speed-scrolling output as this (below), from all nodes and master.
Those percent numbers started at low values but went up, and those values dont seem reasonable at all.
I did not count lines but there were millions, estimating by speed and time.
Just emitting those lines likely adds lot of overhead to duration.
For me, this is not just improvement over what we had.

The output without my changes also has all of those lines (from
current devel branch), it just looks weirder:
pmem-csi-clear-govm-worker3:  - xfsprogs
pmem-csi...0%r-govm-worker3:
pmem-csi...1%r-govm-worker3:
pmem-csi...2%r-govm-worker3:
pmem-csi...3%r-govm-worker3:
pmem-csi...4%r-govm-worker3:
pmem-csi...5%r-govm-worker3:
pmem-csi...6%r-govm-worker3:
pmem-csi...7%r-govm-worker3:
pmem-csi...8%r-govm-worker3:
pmem-csi...9%r-govm-worker3:
pmem-csi...10%-govm-worker3:
pmem-csi...11%-govm-worker3:
pmem-csi...12%-govm-worker3:
pmem-csi...13%-govm-worker3:
pmem-csi...14%-govm-worker3:
pmem-csi...15%-govm-worker3:
pmem-csi...16%-govm-worker3:
pmem-csi...17%-govm-worker3:
pmem-csi...18%-govm-worker3:
pmem-csi...19%-govm-worker3:
pmem-csi...20%-govm-worker3:
pmem-csi...21%-govm-worker3:
pmem-csi...22%-govm-worker3:
pmem-csi...23%-govm-worker3:
pmem-csi...24%-govm-worker3:
pmem-csi...25%-govm-worker3:
pmem-csi...26%-govm-worker3:
pmem-csi...27%-govm-worker3:
pmem-csi...28%-govm-worker3:
pmem-csi...29%-govm-worker3:
pmem-csi...30%-govm-worker3:
pmem-csi...31%-govm-worker3:
pmem-csi...32%-govm-worker3:
pmem-csi...33%-govm-worker3:
pmem-csi...34%-govm-worker3:
pmem-csi...35%-govm-worker3:
pmem-csi...36%-govm-worker3:
pmem-csi...37%-govm-worker3:
pmem-csi...38%-govm-worker3:
pmem-csi...39%-govm-worker3:
pmem-csi...40%-govm-worker3:
pmem-csi...41%-govm-worker3:
pmem-csi...42%-govm-worker3:
pmem-csi...43%-govm-worker3:
pmem-csi...44%-govm-worker3:
pmem-csi...45%-govm-worker3:
pmem-csi...46%-govm-worker3:
pmem-csi...47%-govm-worker3:
pmem-csi...48%-govm-worker3:
pmem-csi...49%-govm-worker3:
pmem-csi...50%-govm-worker3:
pmem-csi...51%-govm-worker3:
pmem-csi...52%-govm-worker3:
pmem-csi...53%-govm-worker3:
pmem-csi...54%-govm-worker3:
pmem-csi...55%-govm-worker3:
pmem-csi...56%-govm-worker3:
pmem-csi...57%-govm-worker3:
pmem-csi...58%-govm-worker3:
pmem-csi...59%-govm-worker3:
pmem-csi...60%-govm-worker3:
pmem-csi...61%-govm-worker3:
pmem-csi...62%-govm-worker3:
pmem-csi...6pmem-csi-clear-govm-master: + set -o errexit
....
pmem-csi-clear-govm-master:  - parted
pmem-csi-clear-govm-master:  - pmdk
pmem-csi-clear-govm-master:  - xfsprogs
pmem-csi...0%r-govm-master:
pmem-csi...1%r-govm-master:
pmem-csi...2%r-govm-master:
pmem-csi...3%r-govm-master:
pmem-csi...4%r-govm-master:
pmem-csi...5%r-govm-master:
pmem-csi...6%r-govm-master:
pmem-csi...7%r-govm-master:
pmem-csi...8%r-govm-master:
pmem-csi...9%r-govm-master:
pmem-csi...10%-govm-master:
pmem-csi...11%-govm-master:
pmem-csi...12%-govm-master:
pmem-csi...13%-govm-master:
pmem-csi...14%-govm-master:
pmem-csi...15%-govm-master:
pmem-csi...16%-govm-master:
pmem-csi...17%-govm-master:
pmem-csi...18%-govm-master:
pmem-csi...19%-govm-master:
pmem-csi...20%-govm-master:
pmem-csi...21%-govm-master:
pmem-csi...22%-govm-master:
pmem-csi...23%-govm-master:
pmem-csi...24%-govm-master:
pmem-csi...25%-govm-master:
pmem-csi...26%-govm-master:
pmem-csi...27%-govm-master:
pmem-csi...28%-govm-master:
pmem-csi...29%-govm-master:
pmem-csi...30%-govm-master:
pmem-csi...31%-govm-master:
pmem-csi...32%-govm-master:
pmem-csi...33%-govm-master:
pmem-csi...34%-govm-master:
pmem-csi...35%-govm-master:
pmem-csi...36%-govm-master:
pmem-csi...37%-govm-master:
pmem-csi...38%-govm-master:
pmem-csi...39%-govm-master:
pmem-csi...40%-govm-master:
pmem-csi...41%-govm-master:
pmem-csi...42%-govm-master:
pmem-csi...43%-govm-master:
pmem-csi...44%-govm-master:
pmem-csi...45%-govm-master:
pmem-csi...46%-govm-master:
pmem-csi...47%-govm-master:
pmem-csi...48%-govm-master:
pmem-csi...49%-govm-master:
pmem-csi...50%-govm-master:
pmem-csi...51%-govm-master:
pmem-csi...52%-govm-master:
pmem-csi...53%-govm-master:
pmem-csi...54%-govm-master:
pmem-csi...55%-govm-master:
pmem-csi...56%-govm-master:
pmem-csi...57%-govm-master:
pmem-csi...58%-govm-master:
pmem-csi...59%-govm-master:
pmem-csi...60%-govm-master:
pmem-csi...61%-govm-master:
pmem-csi...62%-govm-master:
pmem-csi...63%-govm-master:
pmem-csi...64%-govm-master:
pmem-csi...65%-govm-master:
pmem-csi-clear-govm-pmem-csi-clear-govm-worker2: + set -o errexit
...

Any way avoiding those silly lines which don't carry any useful information?
11:31:48 pmem-csi-clear-govm-master:    ...613290%
11:31:48 pmem-csi-clear-govm-master:    ...613303%
11:31:48 pmem-csi-clear-govm-master:    ...613317%
11:31:48 pmem-csi-clear-govm-master:    ...613331%

That is the actual problem, not my changes. Why does swupd print percentages higher
than 100?!
Just to be sure, can you try in your environment without this PR?

I tried same make start setting git commit earlier-by-one. The output seems reasonable, total 2200 lines, with few percents-series 0..100% what makes sense.
(My "millions of lines" guess earlier was bit overestimate, actually there was about 300k lines)

Olev Kartau<EMAIL_ADDRESS>writes:

I tried same make start setting git commit earlier-by-one. The output seems reasonable, total 2200 lines, with few percents-series 0..100% what makes sense.
(My "millions of lines" guess earlier was bit overestimate, actually
there was about 300k lines)

Can you archive your current _work/clear-govm/.log files?  Then try
again with this PR and send me the console output (redirected into a
file) and the individual _work/clear-govm/.log files?
I have no idea where those additional lines come from and I can't
reproduce it here.

I tried now, and I see good-looking output, even shorter than before with 1600 lines. Seems that whatever problem I had with long output, it's not triggered directly by this PR change.
Rebasing would fix disharmony between deployment files and head of devel, where namespacesize option was removed, causing failure to start pods using latest images and this PR deploy files.

whatever problem I had with long output

problem was likely clear swupd related. But as the base has moving parts with base release changing often and causing update set/process also becoming dynamic, we can't expect seeing reproducible cases without freezing moving parts (which we will not need/plan anyway)

Olev Kartau<EMAIL_ADDRESS>writes:

I tried now, and I see good-looking output, even shorter than before
with 1600 lines. Seems that whatever problem I had with long output,
it's not triggered directly by this PR change.

Yep. It would have been very surprising if it had been.

Rebasing would fix disharmony between deployment files and head of
devel, where namespacesize option was removed, causing failure to
start pods using latest images and this PR deploy files.

This PR does not change the deployment. Why should rebasing fix
anything?
I have rebased anyway, just to be sure.

Why should rebasing fix anything?

it fixes deployment for people who use external registry, like me. I have images in registry built from head of devel, which are not deployable with older deploy file set, as there is "-namespacesize" option in deploy files which is not supported by current images. I should go back in time with images as well to test full set here. but as our images build is so slow these days, I select to skip it and accept the "known partial failure", but that's not so clean.


Compiler ignores float constants

The message compiler currently ignores constants that include float values, e.g. #define PI 3.14 or (more practical) #define SAMPLE_LENGTH 0.02. Such constants are ignored whether they involve calculations or not.
This can be fixed by updating the regex statement in the line below to include \. in the expression character set.
https://github.com/pitt-rnel/pyrtma/blob/7ebd4847558065d2dc38a55f5c7d4cbc7345a624/src/pyrtma/compile.py#L34-L36
This simple fix should allow constant literals to be defined, but will not fix errors from performing arithmetic on a mixture of float and int constants. If this is difficult to fix we could choose not to support this. This affects one definition in the current climber_config.h, but this could potentially be phased out of climber:
https://github.com/pitt-rnel/pyrtma/blob/7ebd4847558065d2dc38a55f5c7d4cbc7345a624/testing/climber_config.h#L26-L27

I updated the regex in compile.py in fe8d708 to allow macros with decimal points. This should work for constant literals but will still result in errors for arithmetic expressions such as #define SAMPLE_LENGTH (0.01 * RAW_COUNTS_PER_SAMPLE).
Also, the regex skips string constants that include special characters. For example this constant is skipped by the compiler due to special characters " and :
https://github.com/pitt-rnel/pyrtma/blob/0baa217fabd6a8eb9bea3e63efac6f900f275083/testing/climber_config.h#L11

These issues have been resolved in compiler V2


Improved redstone update mechanics

In this video it is described how the redstone update mechanics could be improved to reduce lag.
In the video description is the source file of the impovements linked: https://gist.github.com/Panda4994/70ed6d39c89396570e062e4404a8d518
Sponge Forums topic about this with some timings before and after applying the changes.
These changes should be added to Sponge.

@randombyte-developer
Couple of issues with this.

Panda would need to consent to his code to be a part of the Sponge project (he still retains copyright).
We need to evaluate what effects this would have on Vanilla redstone (if any). If it breaks Vanilla redstone or mods then it goes to the bottom of the priority list. Our mantra is to be Vanilla AND mod friendly; while Mixin plugins let us hot patch code, we won't make a priority out of something that breaks the mantra.

@randombyte-developer
Not to mention that this diff has some serious issues such as the fact that it COMPLETELY says the hell with multiworld and would "bleed" into other dimensions when performing state changes. Honestly it looks incredibly incomplete and is more of a "proof of concept".

Okay, I understand.

a266c29


Upgrade API to HTTPS

Since the site is served over HTTPS, the browser will not allow requests to HTTP endpoints:

Attempts to call the API over HTTPS currently get rejected

Upgrading to HTTPS seems to be an Express.js task something like this but I imagine it's easier said than done

Closed by four gruelling nights of AWS config


ROKOS freezes and won't wake up while syncing BTC blockchain.

Love this project. Not only a promising BTC node, but a beautiful deployment of linux on pi.
I have been trying to sync Bitcoin Core for a few weeks now using a 256GB SanDisk flash drive. It is well over half synced, but when I leave it to sync over the weekend it goes to sleep and won't wake back up. The green CPU LED is lit solid so it looks like it is just being over taxed?
First thought is maybe its overheating? My raspbi 3.0 has no fan. Do I need one?
Have you guys been able to download and sync the entire BTC blockchain on a pi?
When I unplug and plug it back in it starts syncing again 1 year ago.

local issue, solved over the live support channels at: https://discord.gg/VSTKsZa if require further assistance can also start thread for support over: https://okcashtalk.org/index.php#c6 (required dbcache over config file)


Add support for yaml>=5

It seems that this constructor is not a subtype of UnsafeConstructor, which gives an error in recent PyYaml versions:
  File "/env/lib/python3.7/site-packages/trafaret_config/simple.py", line 69, in read_and_validate
    data = loader.get_single_data()
  File "/env/lib/python3.7/site-packages/yaml/constructor.py", line 43, in get_single_data
    return self.construct_document(node)
  File "/env/lib/python3.7/site-packages/yaml/constructor.py", line 52, in construct_document
    for dummy in generator:
  File "/env/lib/python3.7/site-packages/trafaret_config/simple.py", line 39, in construct_yaml_map
    data.update(self.construct_mapping(node))
  File "/env/lib/python3.7/site-packages/yaml/constructor.py", line 210, in construct_mapping
    return super().construct_mapping(node, deep=deep)
  File "/env/lib/python3.7/site-packages/yaml/constructor.py", line 135, in construct_mapping
    value = self.construct_object(value_node, deep=deep)
  File "/env/lib/python3.7/site-packages/yaml/constructor.py", line 94, in construct_object
    data = constructor(self, tag_suffix, node)
  File "/env/lib/python3.7/site-packages/yaml/constructor.py", line 624, in construct_python_object_apply
    instance = self.make_python_instance(suffix, node, args, kwds, newobj)
  File "/env/lib/python3.7/site-packages/yaml/constructor.py", line 714, in make_python_instance
    return super(UnsafeConstructor, self).make_python_instance(
TypeError: super(type, obj): obj must be an instance or subtype of type

Also see high severity vulnerability in yaml: https://github.com/advisories/GHSA-rprw-h62v-c2w7

Also see high severity vulnerability in PyYaml: https://github.com/advisories/GHSA-rprw-h62v-c2w7

I don't think this vulnerability is an issue for trafaret_config as ConfigLoader is derived from SaveLoader (i.e. it's equivalent to calling safe_load instead of load).
Other than that, it looks like pyyaml 5 changed hierarchy of theirs clasess. Should investigate more.//


Progress never reaches 1 if last question is skipped

If the last question is not shown because of the enableWhenExpression, the progress never reaches 1. If progress === 1 is used to display the result this will never succeed.

updating the progress implementation with the formula Questions with Answers/All Questions that can be displayed should take care of that?

Yes, but evaluating JSONLogic for all questions on every call to getProgress might be expensive. Maybe it would be better to just find out if any question after the last answered question is enabled (that check would mostly stop at the next question, since most questions are enabled).

seems like a faster way


[staging-next] haskellPackages.HsOpenSSL: work around -Werror failures with gcc 14

See the linked issues. Probably due to gcc >= 14.
Affects staging-next and haskell-updates. We can merge staging-next into haskell-updates when this lands.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@ofborg build haskellPackages.HsOpenSSL


Password Reset Successful Toast is not dismissible

The "Password Reset Successful" toast on the "My Settings" page isn't dismissible, and blocks the user from opening the menu. (Presumably the failure toast causes a similar problem)

How should the toast behave? Should it have a dismiss button (like an X) or dismiss when clicked/automatically?

@aidan-fitz I added a toast in my previous PR so I got a feel for how they work. The toast calls its onClose method after 3 seconds. I think the bug here is that the onClose method of the toast is not setting the correct state variable to false.


Missing Mac shell script

Readme file mentions a shell script (.sh) for Mac but it’s not included in the zip file.

The macOS build hasn't been released yet. With minimal development experience you can compile it yourself using their documentation:
https://github.com/HarbourMasters/Starship/blob/main/docs/BUILDING.md#macos
Providing tinyxml2 and renaming the ROM to baserom.us.rev1.z64 were all that were required while using the "Release" build options.

Thanks for pointing the way @mirrornoir! Have you had any luck with running cpack to make a distributable from those build instructions? My attempts have created a Starship.app bundle with no executables copied

I got a basic executable created, but I'm getting plenty of SDL audio errors and the game window doesn't launch


Desaltify works

THe opposite operation of saltify.
{
  "v": <old value>
  "s": <salt>
}

=>

<old value>

Codecov Report

Merging #7 into master will increase coverage by 0.45%.
The diff coverage is 78.57%.

@@             Coverage Diff              @@
##             master       #7      +/-   ##
============================================
+ Coverage     69.61%   70.07%   +0.45%
- Complexity       74       82       +8
============================================
  Files            18       18
  Lines           260      274      +14
  Branches         34       37       +3
============================================
+ Hits            181      192      +11
- Misses           52       53       +1
- Partials         27       29       +2

Impacted Files
Coverage Δ
Complexity Δ

...main/java/jp/co/soramitsu/sora/json/Saltifier.java
86.11% <78.57%> (-4.8%)
18 <8> (+8)

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 2289189...ba9f0be. Read the comment docs.


Support for showExpandAll for tree views

Tree views currently support the showCollapseAll option (Whether to show collapse all action or not). It would be nice if there was an analogous showExpandAll option.

See also #88682 which is Backlog


Privacy policy FAQ.

The security team still regularly receive request to fill in Privacy documents.
Lay out some of those responses in a document.
See also https://github.com/jupyter/governance/issues/152.

The "Check links" step is failing. The URL https://www.jupytercon.com is now displaying a "Website Expired" message. I recommend removing it from our docs. I know this wasn't primarily part of this pull request, but it's blocking the pipeline.

The URL https://www.jupytercon.com/ is now displaying a "Website Expired" message. I recommend removing it from our docs.

CC @afshin who I think mentioned jupytercon website issue recently

The "Check links" step is failing. The URL https://www.jupytercon.com/ is now displaying a "Website Expired" message.

It is now passing as the domain was renewed.

FYI the linkcheck and lighthouse were both fixed in master branch by #749

this looks great! I think the only thing missing is where to link this from so that it is discover-able.

I think once merged we can discuss where, I would at least like to have a link I can send to by mail when we receive questions.
Best place imho for this would be in the footer, and yes we could link it from variosu security pages

I think once merged we can discuss where, I would at least like to have a link I can send to by mail when we receive questions.

Makes sense, merging away, then, and we can always iterate later if anything else comes up. <3


Beautification of default output. Use full terminal width

Use full terminal width for default output. Remove zero bytes from command line. Turn off auto-wrap.

Thanks a lot @ms140569!


How to read an ExtensionObject?

I used the LibUA.Client.Read() functionality to read a value from a specific node and this value contains an ExtensionObject.
It's contents are something like this
{
	"TypeId": {
		"NamespaceIndex": 0,
		"NumericIdentifier": 886,
		"ByteStringIdentifier": null,
		"StringIdentifier": null,
		"IdType": 0
	},
	"Body": "AAAAAAAAAAAAAAAAAABZQA==",
	"Payload": null
}

The way I understand this is that I need to somehow get the structure of the object definition used for this in order to read it's contents. I do see something about the type, but I have no clue how to use it. I also looked into the body part and it contains a byte array which does not make sense at this point.
The value that is sent here is of the type RANGE and contains a low and high value (0-100). Is this supported by the LibUA and if so, could you please point me in the right direction on how to read this?
Thanks!

Is the content a string of json or a binary encoded blob?
Look at the MemoryBuffer class and its decoding methods to read from ExtensionObjects. If it's a string, you can decide a string. If it's a complex type, you can decide the fields in order using decode methods with the appropriate variable types.

In my particular case, it is a byte array that should represent a date time, but it is a custom complex type.

you can decide the fields in order using decode methods with the appropriate variable types
This is the part I'm confused on, do you have a small example on how to do this? This is the part I am missing, it seems.

Here's an example of how to decide some fields in order from a memory buffer. Load a memory buffer with the data (byte array) from an extension object.
https://github.com/nauful/LibUA/blob/d02a2b00228135eeefbf5203bdb988a879467baa/NET Core/LibUA/Client.cs#L1923

MemoryBufferExtensions.cs has more examples. Look at Decode methods near the end of that file for complex structures.

I finally had time to look at this again, but I'm not sur we're on the same page.
The code I have actually already uses the MemoryBuffer and in this case it is to build a DataValue;
public static bool Encode(this MemoryBuffer mem, DataValue dv)
The DataValue that is build has a value that seems to contain an ExtensionObject:
{ 	"TypeId": { 		"NamespaceIndex": 0, 		"NumericIdentifier": 889, 		"ByteStringIdentifier": null, 		"StringIdentifier": null, 		"IdType": 0 	}, 	"Body": "LwAAAGh0dHA6Ly93d3cub3BjZm91bmRhdGlvbi5vcmcvVUEvdW5pdHMvdW4vY2VmYWN0SEFGAAIDAAAAwrBGAhEAAABkZWdyZWUgRmFocmVuaGVpdA==", 	"Payload": null }
Now, inside this ExtensionObject seems to be a byteArray inside the body. According to the UA Expert client software it is an object with multiple properties, but my question is how do I get that object with those properties?

It's possible to have a MemoryBuffer work on an arbitrary byte buffer then copy that to/from a DataValue's value.
If your body is Base64 encoded, you can use the standard C# libraries to convert that to a byteArray. You can then create a new MemoryBuffer passing byteArray as input, then use the various extension methods to decode.
If you're trying to build that object, create a new MemoryBuffer with a large byte array, use various extension methods to encode fields, then take the slice of the array [0, MemoryBuffer.Position), Base64 encode, and set as the value.


Links to windows applications not working

I'm using desktop-app version 0.2.6 and trying to create a shortcut for a windows application.
However, because the shotcut doesn't include the .exe at the end, it fails to launch.
> conda list
#
# Name                    Version                   Build  Channel
desktop-app               0.2.6            py38h885f38d_3    conda-forge

I had to modify the application with the following tiny patch:
diff --git a/desktop_app/windows.py b/desktop_app/windows.py
index eb4f2ab..3c14597 100644
--- a/desktop_app/windows.py
+++ b/desktop_app/windows.py
@@ -74,7 +74,7 @@ def create_shortcut(
     _checkwindows()
     objShell = Dispatch('WScript.Shell')
     shortcut = objShell.CreateShortcut(str(shortcut_path))
-    shortcut.TargetPath = str(target)
+    shortcut.TargetPath = str(target) + '.exe'
     if arguments:
         shortcut.Arguments = list2cmdline(arguments)
     if working_directory is not None:

Are you seeing the same thing?

No, I don't see this. What version of Windows are you on? This occurs when you run desktop-app install <modulename>?
(apologies, I haven't yet documented that desktop-app install <modulename> is the intended usage, I've been slack on documentation since this project was made to serve the needs of another project!)
If adding the ".exe" is harmless, then I'll make your suggested change - after investigating a little bit!

Thanks for responding so quickly!
I agree that this is a pretty powerful enabling project!
I skipped the install part on Linux, but on windows, creating lnk files is not my favorite thing to do.
You are correct in saying that this occurs when I run
desktop-app install my_module.submodule

The script name shows up as not having the .exe which is causing things to fail at linking on my windows Machine.
I'm on Windows 10

I'm not so sure it is harmless since the .exe might be double added for your version maybe.

Ok, I have a theory.
My extensions do have .exe in them, even though the code creating the shortcuts clearly does not pass in a TargetPath ending in .exe.
This makes me think that this Windows shortcut API is automatically appending .exe for me, in my case. But it isn't for you. Why not?
I think it's probably because you are using a submodule, whereas in the example I checked, it's just a top-level module. So your launcher script already has a dot in its name (module.submodule). This automatic behaviour of the Windows API must simply check whether there is a dot in the name already, as it interprets any dot as indicative of an extension, so it decides not to append .exe.
So I think explicitly appending .exe should be fine and not double up, I'll go ahead and push a commit.

Thanks @chrisjbillington I really appreciate it!

No worries, appreciate the bug report!
If you'd like to test the change, you can install a build from git master with:
conda install -c labscript-suite/label/test desktop-app

Do you mind if i do the bad thing and upload a patched version:
https://github.com/conda-forge/desktop-app-feedstock/pull/7
I guess I can upload and build to my own channel instead. let me do that.

I'll just stamp a new patch version, makes it easier for everyone.

^_^ right, i noticed that you were updating your release process so i didn't feel like overburdening you incase you didn't have the chance to get it completed within the next few days.

Fair enough! The release issues were actually a nightmare to fix, but since I already went through that turmoil ages ago with another project, it was quick to apply the same fix here!
Version 0.2.7 has been tagged.


Document the ValueSet $expand FHIR operation

We have supported the ValueSet/$expand operation for some time and have enhanced it with #1213 - but it is currently undocumented.
Documentation should be added to the FHIR Operation support page.

Also related #1325


Release script

Scope:

Create git flow release branch
Run all tests
Bump versions in info.plist
Bump versions in podfile
Commit
Close git flow release branch
Update carthage in Sample app
Run UITest in sample app
Commit

Preference -> Fastlane

Mostly done as of 0.4.0


Move Martin crate to its own subdir

This cleans up the code a bit, making all crates to be on the same level.

So with this there are these three, right?

martin-mbtiles
martin
martin-tile-utils

@birkskyum yep, so far :)


Right-click on dock icon to activate media keys

It'd be nice if you could right-click on the dock icon to play/pause and advance or go to the previous track.

Fixed in #81


FreeType - Use zero copy memory mapping when possible

Should allow a lower memory footprint and faster startup times on Desktop/Android.
Android requires users to manually edit their gradle config to include certain aaptOptions to not compress font files. Would we want to include this in the default project setup?
Such as:
android { aaptOptions {     noCompress 'ttf', 'ttc', 'otf' } }

Just curious: Did you actually profile this?

Yes, and it's more extreme than I would expect.
Android Normal UnsafeByteBuffer:

Android MappedByteBuffer:

I'm not sure if it's an accounting issue with the profiler, or if something silly like the whole apk is being mapped and this is just reusing the existing mapping. The difference is about the sum of my application's font files.
Time wise loading and generating (base characters only) a ~18MB ttc dropped from around 300-350ms to 150-225ms.
I would be really interested if anyone else could benchmark to compare.

It looks nice to me. We added FileHandle map without input from iOS guys. Is everything OK there?

Code for FileChannel#map exists in RoboVM
Everything I can see would indicate this should be fine. Even if it's not supported at runtime, compile compatibility should be enough given the fallback to unsafe ByteBuffer.


Add $argv to alias functions

Add $argv at end of git alias functions in order to be able to append
commands or flags to all aliases, which means that stuff like
gps -u origin <branch> now works as expected.

@bingocaller Thank you for pull request!


Support posting to multiple slack channels

Currently, we don't support configuring posting the same message to multiple Slack channels. Most Slack integrations now support it, we have an internal use case for this too.
For backward compatibility, I have added an additional method that reuses the old method, so old integrations won't break.

Codecov Report

Merging #28 into master will decrease coverage by 0.05%.
The diff coverage is 50%.

@@             Coverage Diff              @@
##             master      #28      +/-   ##
============================================
- Coverage     70.19%   70.13%   -0.06%
  Complexity      246      246
============================================
  Files            36       36
  Lines          1258     1259       +1
  Branches        250      250
============================================
  Hits            883      883
- Misses          251      252       +1
  Partials        124      124

Impacted Files
Coverage Δ
Complexity Δ

...ala/com/sumologic/shellbase/slack/SlackState.scala
66.66% <0%> (-33.34%)
0 <0> (ø)

...sumologic/shellbase/slack/PostCommandToSlack.scala
84.21% <100%> (ø)
0 <0> (ø)
:arrow_down:

...c/shellbase/slack/PostCommandWithSlackThread.scala
63.63% <50%> (ø)
0 <0> (ø)
:arrow_down:

.../sumologic/shellbase/slack/PostToSlackHelper.scala
81.81% <50%> (ø)
0 <0> (ø)
:arrow_down:

Continue to review full report at Codecov.

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


update mypy to 1.2

To make it work with python  3.11

[X] Ensured the test suite passes
[X] Completed the Contributor License Agreement ("CLA")

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 93.728%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2660

Relevant Lines:
2838

💛  - Coveralls


CTD when opening folder containing files that open in vscode.

Describe the bug
CTD when opening folder containing files that open in vscode.
To Reproduce
Need to also have vscode.
Steps to reproduce the behavior:

Go to folder
Click on new txfile change extention to .ps1 (also ahk breaks)
change the default program to open with to vscode
open the file
close the file and files-uwp
navigate to The folder from step 1
CTD occurs

Expected behavior
it just dislpays the contents of the folder and doesnt crash after 0.5 seconds.
Desktop (please complete the following information):

OS: Windows 10 2004
App version: v0.11.0

Additional context
i made the super+e key launch your ap instead of the default explorer using powertoys and ahk. Using alt+e

@NicTanghe Is this still an issue is v0.20?

Thanks again for your feedback.
Since we didn't hear from you on this topic for 5+ days, we'll assume everything is worked out and close this feedback item. If you had more feedback to provide, please re-open this and help the owners by describing the current status and any steps taken to troubleshoot this.


Explosion doDamage fix

Fixed doDamage in util.Explosion is always true.

Ah, my mistake. Thanks.

No problem. Thanks for lib.


Revision for expression-bodied properties

Revision for expression-bodied properties
Summary
In C# 7, both get and set accessors can both have expression body definitions. This PR documents the change.
Fixes #1369
Details
The change requires changes to a number of topics, including the get and set keywords, the Properties topic, and the indexers topic.
Suggested Reviewers
@BillWagner @mairaw

This is ready for review; I think that I've revised all of the relevant topics.


CastError: Cast to ObjectId failed for value "1" at path "_id" for model "navigation"

I'm trying to test the navigation rendering via http://localhost:1337/navigation/render/1?type="tree".
I get a 500 Internal Server Error and in the logs I see the above CastError.
This is my initial setup:

Home is a published single type page.
Components and test2 are published collection type pages
Any help is appreciated!

Hi @jeffisowens Could you add stack trace and explain why you have in URL something like this: type="tree"?

Tree shouldn't have been in quotes, but it's the same error if it is.
Full log:
`Welcome back!
To manage your project 🚀, go to the administration panel at:
http://localhost:1337/admin
To access the server ⚡, go to:
http://localhost:1337
[2021-07-01T13:21:52.637Z] error CastError: Cast to ObjectId failed for value "1" at path "_id" for model "navigation"
at model.Query.exec (/Users/jdowens/Documents/Sites/portal-cms/node_modules/mongoose/lib/query.js:4371:21)
at model.Query.Query.then (/Users/jdowens/Documents/Sites/portal-cms/node_modules/mongoose/lib/query.js:4463:15)
at find (/Users/jdowens/Documents/Sites/portal-cms/node_modules/strapi-connector-mongoose/lib/queries.js:444:8)
at Object.findOne (/Users/jdowens/Documents/Sites/portal-cms/node_modules/strapi-connector-mongoose/lib/queries.js:448:27)
at fn (/Users/jdowens/Documents/Sites/portal-cms/node_modules/strapi-database/lib/queries/helpers.js:31:54)
at Object.findOne (/Users/jdowens/Documents/Sites/portal-cms/node_modules/strapi-database/lib/queries/helpers.js:15:24)
at processTicksAndRejections (internal/process/task_queues.js:85:5)
at async Object.renderType (/Users/jdowens/Documents/Sites/portal-cms/node_modules/strapi-plugin-navigation/services/navigation.js:256:20)
[2021-07-01T13:21:52.639Z] debug GET /navigation/render/1 (18 ms) 500
[2021-07-01T13:21:53.250Z] debug GET /favicon.ico (1 ms) 200`

@jeffisowens as I see you're using MongoDB and I assume that you're trying to retrieve the navigation with not valid id because Mongo generates an alphanumeric ids rather than integers.
 http://localhost:1337/navigation/render/<id or slug>?type=tree
That how your call should look like. You should replace <id or slug> by proper navigation id or it slug. The initial navigation is created with slug main-navigation try to call:
 http://localhost:1337/navigation/render/main-navigation?type=tree
and check if work.

Thanks! That works!


On Cosmos DB SDK v2 Async

See this,.
https://github.com/Azure/azure-cosmosdb-java/issues/382
According to the discussion, rxnetty's almost deprecated, v2 Async is based on this, this option's not available any more in conclusion. Consider this to deprecate
Thanks

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

ID: f7c2ad22-039f-8f84-7562-758d4fd25d48
Version Independent ID: 5404fa3d-3761-0c92-ec07-27d0c3a06312
Content: Azure Cosmos DB: SQL Async Java API, SDK & resources
Content Source: articles/cosmos-db/sql-api-sdk-async-java.md
Service: cosmos-db
Sub-service: cosmosdb-sql
GitHub Login: @anfeldma-ms
Microsoft Alias: anfeldma

@nudbeach Thank you for the feedback. This is being assigned to the content author to evaluate and update as appropriate.

@nudbeach The V2 Async SDK will be deprecated in the future, we have the doc published to help the existing users on that SDK. There is a note on the page that says to use the latest v4 SDK. We will keep this page until the SDK is deprecated.

#please-close

Thanks for the feedback @SnehaGunda. It would be much appreciated if you could respond with deprecation timeline. However this will be closed


Add informative docs for AA / CRD comparision

So that users could reasonably determine AA or CRD depending on what they actually value.

/kind documentation
/sig api-machinery
/assign @pwittrock

/cc adohe

https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/#advanced-features-and-flexibility
merging w/ it


Add information about validation.policy.admission.k8s.io/validation_f…

…ailure annotation
tried solving according to the issue mentioned in https://github.com/kubernetes/website/issues/45187#issue-2140222281

/retitle Register audit annotation for admission policy validation

Thank you for your contribution! The change looks good to me. Congrats on your first PR 🎉
/lgtm
Preview Page

Thanks @dipesh-rawat .......This contribution is helped by you so much...
Waiting for ur to get merged☺.


Fix: update defaultCover URL

it took me 3 years to make this PR please merge

What the heck? 😂

can you review my PR please


.github/workflows: add golangci-lint action

Before sending a pull request, please review Contribution Guidelines:
https://github.com/google/syzkaller/blob/master/docs/contributing.md

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1608   +/-   ##
=======================================
  Coverage   56.72%   56.72%
=======================================
  Files         144      144
  Lines       27029    27029
=======================================
  Hits        15331    15331
  Misses      10918    10918
  Partials      780      780

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 012fbc3...ceb7e2e. Read the comment docs.

I gave up, I can't setup any of the golangci-actions.


fixing pep8 errors

conv_filter_visualization had some pep8 errors which are fixed by this PR

The CONTRIBUTING.md file states that we don't take PEP8 PRs. Also I think you are replacing reasonable code with stylistically worse code (e.g. use of \; a line with just : on it...).

@fchollet thanks for your feedback
from CONTRIBUTING.md

We use PEP8 syntax conventions, but we aren't dogmatic when it comes to line length.

for me this does not sound like PEP8 PRs are not welcome. Maybe you should be more explicit there

I think you are replacing reasonable code with stylistically worse code (e.g. use of ; a line with just : on it...).

I disagree here. Accessing elements in tensor is more readable if you visually separate the dimensions... e.g.:
B = A[1,
      2, :]

vs
B = A[1,
      2,
      :]

or
B = A[
        1,
        2,
        :
    ]


SublimeLinter not capturing output lines.

I'm running MyPy 0.730 and Sublime Text 3.2.2, Build 3211 on Windows.
When I encounter a type error, the logger outputs that there was no match.
For example:
SublimeLinter: #47 linter.py:1254     mypy: No match for line: 'Found 2 errors in 1 file (checked 1 source file)'
INFO:SublimeLinter.lint.linter:mypy: No match for line: 'Found 2 errors in 1 file (checked 1 source file)'

Similarly, if there are no issues, the logger will say there was again no match:
SublimeLinter: #51 linter.py:1254     mypy: No match for line: 'Success: no issues found in 1 source file'
INFO:SublimeLinter.lint.linter:mypy: No match for line: 'Success: no issues found in 1 source file'

Is this intended behavior? It seems like at least one of these should have a match, but I'm not familiar enough with the SublimeLinter internals to know.

That's debugging noise.  SublimeLinter parses each output line, and for that particular line cited in the debug log it couldn't extract a match which is expected because it is the summary line mypy puts at the end.
You should have a look why you have two loggers here attached.  The lines starting with SublimeLinter are coming from SublimeLinter, the lines starting with INFO are coming from a general logger.  Note that logging comes with overhead and costs several hundreds of milliseconds.

Very good to hear! Thanks for clearing that up and noticing something quirky in setup. Much appreciated on both fronts, this was very helpful 👍


Refactor buffer in preparation for true color and buffer performance improvements

A refactor to prepare for buffer performance changes #791 and true color #484. These changes were previously in https://github.com/sourcelair/xterm.js/pull/756.

Coverage decreased (-0.01%) to 71.221% when pulling fd61c8e8742da24c39867eeebf46e3f0ac6728d8 on Tyriar:791_buffer_refactor into 091854df0ecfc1041bbfd72b874f7d3bfdcd8a23 on sourcelair:v3.

FYI @parisk, I'm merging this as CI passed, it's low risk and was already signed off in https://github.com/sourcelair/xterm.js/pull/756


are (unused?) alpha channels in large png files intended?

Currently there appears to be unused alpha channels in ROI pngs
These channels are zeroed out, but exist.
This results in increased size of file, and additional channel generated in zarr.
Ideally this channel might be removed, if not being used.

Here is an example file info:
$gm identify -verbose ./Plate_3_Data_Package/DSP\ Output/IA_P3_S1.png
Image: ./Plate_3_Data_Package/DSP Output/IA_P3_S1.png
  Format: PNG (Portable Network Graphics)
  Geometry: 9705x23871
  Class: DirectClass
  Type: true color
  Depth: 8 bits-per-pixel component
  Channel Depths:
    Red:      8 bits
    Green:    8 bits
    Blue:     8 bits
    Opacity:  1 bits
  Channel Statistics:
    Red:
      Minimum:                     0.00 (0.0000)
      Maximum:                 65535.00 (1.0000)
      Mean:                     7381.98 (0.1126)
      Standard Deviation:      17620.82 (0.2689)
    Green:
      Minimum:                     0.00 (0.0000)
      Maximum:                 65535.00 (1.0000)
      Mean:                     6647.48 (0.1014)
      Standard Deviation:      16046.34 (0.2449)
    Blue:
      Minimum:                     0.00 (0.0000)
      Maximum:                 65535.00 (1.0000)
      Mean:                     5571.51 (0.0850)
      Standard Deviation:      14524.80 (0.2216)
    Opacity:
      Minimum:                     0.00 (0.0000)
      Maximum:                     0.00 (0.0000)
      Mean:                        0.00 (0.0000)
      Standard Deviation:          0.00 (0.0000)
  Resolution: 10x10 pixels/centimeter
  Filesize: 117.9Mi
  Interlace: No
  Orientation: Unknown
  Background Color: white
  Border Color: #DFDFDF00
  Matte Color: #BDBDBD00
  Page geometry: 9705x23871+0+0
  Compose: Over
  Dispose: Undefined
  Iterations: 0
  Compression: Zip
  Png:IHDR.color-type-orig: 6
  Png:IHDR.bit-depth-orig: 8
  Signature: 471326cb3175311d208700fd7a645875e48fef82007305abe41160bf95a74039
  Tainted: False
  User Time: 7.120u
  Elapsed Time: 0m:7.139047s
  Pixels Per Second: 30.9Mi

The initial implementation remove the alpha channel when the png is converted to tiff:
https://github.com/niaid/image_portal_workflows/blob/main/em_workflows/lrg_2d_rgb/flow.py#L26-L27


Print usage hint on docker-machine env

In light of confusing experiences like #851 (which I just experienced myself), it might be nice to show a usage hint in the output of docker-machine env - commented out, of course:
$ docker-machine env

export DOCKER_TLS_VERIFY=1
export DOCKER_CERT_PATH="/Users/aanand/.docker/machine/machines/dev"
export DOCKER_HOST=tcp://<IP_ADDRESS>:2376

# Run this command to configure your shell: eval $(docker-machine env)

(It needs to come afterwards because of shell expansion - if the hash is at the beginning, the whole thing will be treated as a comment :smirk:)

#dibs

@aanand +1

This was fixed by #882


Updated core and plugin versions

@rultor merge

@rultor merge

@pollyvolk Done! FYI, the full log is here (took me 8min)

@rultor release, tag is 0.1.4

@rultor release, tag is 0.1.4

@pollyvolk OK, I will release it now. Please check the progress here

@rultor release, tag is 0.1.4

@pollyvolk Done! FYI, the full log is here (took me 11min)


You mortal fools underestimate my power.

What needs to be documented?
Remember me?

Remember me?


p2p: server: include 'read/write' in deadlineAdjuster error messages

Motivation
P2P server messages related to deadlines were not including in the deadline related errors
Description
Fix error message

bors merge


ShouldRaise buggy with Django's ValidationError

>>> from testfixtures import ShouldRaise
>>> from django.core.exceptions import ValidationError
>>> with ShouldRaise(ValidationError("d'oh")):
...     raise ValidationError("d'oh")
...
AssertionError: ValidationError([u"d'oh"]) raised, ValidationError([u"d'oh"]) expected, attributes differ:
  error_list:[ValidationError([u"d'oh"])] != [ValidationError([u"d'oh"])]

I think you're casting the "buggy" aspersion in the wrong direction.
Here's some code from a codebase you may be working with that deals with this bullshit:
class ShouldRaiseValidationError(ShouldRaise):
    """Allow testing ValidationError for specific messages"""
    def __init__(self, *messages):
        ShouldRaise.__init__(self, ValidationError)
        self.messages = messages

    def __exit__(self, *args):
        ShouldRaise.__exit__(self, *args)
        compare(self.messages, self.raised.messages)
        return True

Should I add the snippet above to testfixtures.django?

Why not just make ShouldRaise work the "one obvious way"?  i.e., we detect if django is installed, and if so special-case handling for ValidationError instances.

mehh... I agree their exception is kinda naff, but Django is a thing and not going away any time soon.  ShouldRaiseValidationError in the testfixtures.django submodule would be a welcome addition, but adding it directly to ShouldRaise would be even more welcome  :)

Pardon me for butting in. What is special about the django ValidationError that makes it not work with __eq__?

@asqui - check out this wonderful code. Non-django-specific changes that deal with this very welcomely received. If not, I'll chuck ShouldRaiseValidationError in testfixtures.django.

Closing this off, we can track on the PR.


how to use it?

I installed plugins, according to instruction, install padawan-php, index and start server, but in editor nothing happened. May be i should use some hotkeys?
My config:
set number
set linebreak
set showbreak=+++
set textwidth=100
set showmatch
set visualbell
set noswapfile
set hlsearch
set smartcase
set ignorecase
set incsearch

set autoindent
set expandtab
set shiftwidth=4
set smartindent
set smarttab
set softtabstop=4

set ruler

set undolevels=1000
set backspace=indent,eol,start
let mapleader = ","

if (has("termguicolors"))
 set termguicolors
endif

call plug#begin()

Plug 'scrooloose/nerdtree', { 'on':  'NERDTreeToggle' }
Plug 'scrooloose/syntastic'
Plug 'jacoborus/tender'
Plug 'jlanzarotta/bufexplorer'
Plug 'stephpy/vim-php-cs-fixer'
Plug 'vim-airline/vim-airline'
Plug 'Shougo/deoplete.nvim'
Plug 'padawan-php/deoplete-padawan'

call plug#end()

"Syntax and colorscheme
syntax enable
colorscheme tender

"php-cs-fixer
let g:php_cs_fixer_level = "psr2"              " which level ?
let g:php_cs_fixer_config = "default"             " configuration
"let g:php_cs_fixer_config_file = '.php_cs'       " configuration file
let g:php_cs_fixer_php_path = "php"               " Path to PHP
" If you want to define specific fixers:
"let g:php_cs_fixer_fixers_list = "linefeed,short_tag,indentation"
let g:php_cs_fixer_enable_default_mapping = 1     " Enable the mapping by default (<leader>pcd)
let g:php_cs_fixer_dry_run = 0                    " Call command with dry-run option
let g:php_cs_fixer_verbose = 0                    " Return the output of command if 1, else an inline information.

"syntastic
set statusline+=%#warningmsg#
set statusline+=%{SyntasticStatuslineFlag()}
set statusline+=%*

let g:syntastic_php_checkers=['phpcs', 'php']
let g:syntastic_php_phpcs_exec='~/.composer/vendor/bin/phpcs'
let g:syntastic_php_phpcs_args='--standard=PSR2 -n'
let g:syntastic_always_populate_loc_list = 1
let g:syntastic_auto_loc_list = 1
let g:syntastic_check_on_open = 1
" let g:syntastic_aggregate_errors = 1
let g:syntastic_check_on_wq = 0

Is depleted showing completion for current buffer? Does popup menu appears at all?
If no then maybe depleted itself is not working correctly for you. You can try to run :RemotePluginsUpdate.

Nothing appears at all. Tried to run :UpdateRemotePlugins. Run CheckHealth, everything fine...

Oh, sorry, i fixed it, let g:deoplete#enable_at_startup = 1 helps me! Thanks!


multiple websocket connections

Is there support for sending messages to multiple WebSocket connections? I'm looking through the docs and it appears messages can only be sent as a reply to incoming WebSocket messages and thus can only be sent to that one connection.

All WebSocket connections are initiated by the client, but you can have as many connections as you want. If you want to send a message to all clients, you have to keep track of the clients somehow.

Ok, I just realized, are you supposed to store the whole context object to reference later for .send()? I guess I was caught up looking for something like in socket.io with the .to() method where you can more directly specify a room to send messages to.

Ok, I just realized, are you supposed to store the whole context object to reference later for .send()

Yup, that works fine! You can partition your clients into "rooms" too, for example by using ConcurrentHashMap<String, WsContext>, where the String is your room/group id.


Typescript example

Hello,
It should be awesome to have a typescript example in this repository (I have some issues with the resolvers types for example…).

This seems adequately covered by the TS boilerplates?

I agree. @fabien0102 have you seen the advanced TypeScript boilerplate?

Hey, @Urigo from The Guild here!
You might know us from projects such as graphql-code-generator, envelop or graphql-tools.
For a long time we thought that the Javascript ecosystem is still missing a lightweight cross-platform, but still highly customizable GraphQL Server.
In the past the awesome Prisma team took on that great challenge and now we are happy to announce that we are continuing them and just released GraphQL Yoga 2.0 - Build fast, extensible, and batteries-included (Subscriptions, Serverless, File uploads support) GraphQL APIs in Node.js 🚀
And regarding the issue here, Yoga is fully typed and fully and natively supports Typescript!
We have been working a long time on version 2.0 and have been using it in our clients projects for a few months now and shared a couple of alpha cycles here.
Thank you all for your feedback and suggestions, you made this release possible!
Please try Yoga out again, give us feedback and help us spread the word on the new release!

Announcement and blog post
https://github.com/dotansimha/graphql-yoga/issues/704
https://www.graphql-yoga.com/

@Urigo  I came across this from your sample documentation, when running in typescript.
Property 'headers' does not exist on type 'YogaInitialContext & { req: IncomingMessage; res: ServerResponse; }'.ts(23

When using the following code block:
const yoga = createServer({
  schema,
  context: (req) => ({
    // Context factory gets called for every request
    myToken: req.headers.get("authorization"),
  }),
  graphiql: true,
});

Thoughts?

Because it should be like the following as you can see in the TS error. context factory doesn't take IncomingMessage directly but gives you the initial context has req prop;
context: ({ req }) => {
}


:children_crossing: UX | iOS | Prompt user that camera access was disabled when going back to Scanner

When the app asked for permission to use my camera I declined.
When I exit and re-enter the scanner menu, most apps will then prompt the user that the access has been disabled and you can either hit OK or click a button which sends you to the settings screen where you can then manually enable the access.
Not every user knows where to go and how to enable it once they (accidentally) press "do not allow" on the prompt.

Now if the user declined permissions to camera, we show a snackbar saying that they should give access in Settings.
That's an OK solution, but it would be great if we could send the user directly to the proper location in Settings.


GPGS Android: fetchLeaderboardEntries returns same values

On my android phone, the leaderboard entries are always the same. If there are new values in the Google Play Games App, the old are given by fetchLeaderboardEntries, even if I clear the storage of my App. On the desktop are the entries up-to-date.

Did you try to set forceRefresh to true?

This solved this problem, but now it doesn't load on one phone and on another phone, it takes 138 seconds

Yes they work and are given to the GPGS API: code here Google's doc
Unfortunately, the API is slow. That's why there is the forceReload param. You should call the method with forceReload only when it is needed and not when the user is waiting for it.

Ok, thank you


Replace asciinema with demo video

This issue relates to the new version of the website:
Replace the embedded asciinema with the video Donovan authors

Outdated issue, closing.


Fix inaccurately calculated sats/vB displayed when sending Bitcoin

When the user selects a fee option they expect the transaction to be send with that fee. I have gotten a report from a user that the wallet set a lower fee than expected based on the selected fee (111 selected 89 sat/vB was set). This is not caused by a CPFP string of pending transactions.
Testing a transaction on mainnet I didn't see the same issue. Perhaps this requires more tests.
On testnet it is reproducible, the wallets sets a different fee than selected consistently (6.16.1):
https://github.com/leather-wallet/extension/assets/33360391/867b080e-a1e8-49c6-9c14-f297c171fd52

Kyran noticed that the sats per vB are off but the total fee displayed when choosing the fee is equal to what is being broadcasted.
We'd want sats per vB rate to be accurate too ofc.

Is this more a P3 then?

I am making this a P1 again because custom fee is also affected. Users set the custom fee in sats/vB so it doesn't matter if the total amount displayed is what it is being send with, it is wrong. Apparently it can go both ways. A user reported it got transmitted with 40 when they set 50 sats per vB.
On testnet I see it is transmitted with 148 sats/vB when I set 100 sats/vB.
(testnet)

The user who reported their mainnet issue:

@kyranjamie I'm finding some things off with our txSizer on testnet ...I haven't confirmed yet if the same on mainnet. It looks like you ported over a tx size extimator: https://github.com/leather-wallet/extension/blob/dev/src/app/common/transactions/bitcoin/fees/btc-size-fee-estimator.ts
Any thoughts on why this might be off just on testnet?
Example:
Our size est:

Broadcast size in explorer ...which makes the fee sat/vB off here:
https://blockstream.info/testnet/tx/6c5bbb86263ed3807c4dcc2d8a5a7eceb3edaf1825b64b8dbc81bfa4f02d818c

Confirmed on mainnet here @markmhendrickson, just an fyi.

https://blockstream.info/tx/04a7ba9a023b6e526821e8dba046c6b54e0a1a24442b325badabaebcc73f07b5

To your q's @fbwoolf, does testnet even have fee rates? Most sources just say 1 right?

To your q's @fbwoolf, does testnet even have fee rates? Most sources just say 1 right?

Blockcypher does return values so the refactor included a change to just use that api on testnet. Mempool just returns 1 so excluded it from the mean average calc on testnet which helped fix the bug here on testnet.