lib/types: add number

For numbers that can be ints or floats.

How about instead extending the float type to also accept integers and automatically convert them to floats? Integers are a subset of floats after all

we should probably discourage the use of floats in nixos modules due to inaccuracies like https://github.com/NixOS/nix/issues/5733. any float with enough significant digits (more than six) will be mutilated, and that can't be a good thing for modules

number seems too precise. To me the most natural kind of number to be the default kind of number would be the natural numbers, extended with 0: non-negative numbers. How about numeric?
If we're going to accept floats, might as well accept the ~complex num~ quaternions ;)

Integers are a subset of floats after all

64-bit integers are not a subset of 64-bit floats though. This makes the conversion leaky, and we shouldn't do it.
For a real solution (pun not intended) we should add arbitrary precision numbers to Nix. Would be nice not to have float quirks but support all of JSON nonetheless.

How about instead extending the float type to also accept integers and automatically convert them to floats? Integers are a subset of floats after all

Had that in mind too, it's probably better. We can add a check to warn/throw on leaky conversions.
The other option is to make float accept ints, without converting. Strictly speaking it breaks the contract, but practically speaking, would anyone care? As far as I can tell, ints quack like floats except for isFloat.

the natural numbers, extended with 0

Blocked. /j

How about just using number = either int float?

So far the option I'm leaning towards is to make float's check x: isInt x || isFloat x (and rename numbers to floats). Does anyone strongly oppose that?

Actually yes, me. I don't like having a type of floats that's not a type of floats.
A new type is fine, all that's left is to bikeshed over the name.
I don't think numeric says anything different than number (if anything we should prefer nouns over adjectives), and I don't think it's reasonable to worry about Nix getting support for numbers outside of ℝ, so I'm still happy with the current state of this PR.

How about just using number = either int float?

This has ever so slightly different semantics: mkMerge [ 1 1.0 ] would fail with either int float, but succeed with the current thing.
I think we want it to succeed?

How about just using number = either int float?

This has ever so slightly different semantics: mkMerge [ 1 1.0 ] would fail with either int float, but succeed with the current thing.
I think we want it to succeed?

In JSON these would be different, but in JavaScript they wouldn't.
I think for a type that normally preserves the float/int runtime type, it would be surprising for it to ignore that runtime type and make an arbitrary choice.
Comparing floats is a bad idea in the first place, so perhaps we should disallow the merging of float definitions. We might allow ints to be compared, but a partial equivalence relation is perhaps even more surprising than no equivalence at all.

Ok, either int float it is.

Could you document the type in nixos/doc/manual/development/option-types.section.md?

Done. I also reorganised things a bit to remove the "Value types" category which is not really a concept.

Anything left to do here?

Done, hopefully people can decide for themselves whether the precision loss is acceptable (I suspect it's okay in most cases).


working with macOS 10.14, new option to put in place...

The good news is that code is working perfectly with 10.14
that will be great is to have it the accent colours and highlights as command lines too..

Thanks for letting me know it works. I'm not interested in supporting accent colors and highlights as it's not something you would need to toggle that often.


Add horizontal adjust slider

Hi @longitachi,
I'd like to propose a proposal.
I got feedback from a user of my app that the vertical slider is difficult to use.
The user is using a smartphone case, and the edges of the screen are covered by the case, making it difficult to press the slider.
So, I added the horizontal adjust slider and the configuration to allow switching between each.
I'd be happy if you'd review this proposal.
Also, the new horizontal slider is available on iOS 14 and later.
I think that is no problem because there are only a limited number of users using iOS13 and lower in worldwide and many apps are not support iOS13 and lower.
Thank you.
ZLImageEditorUIConfiguration.default()
    .adjustSliderType(.horizontal)

iPhone
iPad

First of all, instead of writing two "AdjustSlider" classes, I think it is better to use one in the framework, and then modify the layout according to the type.
Secondly, I think you should not modify the minimum supported version to iOS14 in order to use slider.addAction method.

Thank you for your review. I got it. I'll fix them💪

@longitachi I tried to encapsulate it using protocol.
However does that mean I should make the current original slider?
The original slider is a bit complicated...

Because I wanted this effect, so I customized the AdjustSlider,

I see. I'll try to implement a custom slider😀

@longitachi I replaced the new original horizontal slider😃
Could you review again?
Thank you.

@darquro  In order to keep the style of AdjustSlider unified, I submitted and modified the original AdjustSlider code to support two styles.

@longitachi OK! Thank you for implementing! I close this PR.

Also I'd be happy if you could release this as new version.

OK, I'll release a new version later.

Thank you so much!


Added support for passing hostnames and pids

What does this PR do?
Reapplies PR  https://github.com/StackVista/stackstate-trace-agent/pull/9

@zandrewitte  Superseded by  https://github.com/StackVista/stackstate-agent/pull/90


I.see() doesn't have comprehensive fail description

What are you trying to achieve?
I write code like :
I.see(4, {css: '.someclass'})

When test fails I want to know why it fails from console output.
What do you get instead?
I got message
expected element {css: '.someclass'} to include "5"

No information what went wrong. Is element empty or may be has text "4"?
I can't understand what wrong with my system under test.
What I would like to get?
Something like that:
+ expected: element {css: '.someclass'} to include "5"
- actual: element {css: '.someclass'}  includes "66"

Details

CodeceptJS version: 1.0.2
WebDriverIO

what if there are more than one element for .someclass?
But yeah, output can be improved

What if there are more than one element for .someclass?
Take the first. It's tests author problem when he is writing such weak locators.

what if output is very very long?
"640 K ought to be enough for anybody." (с)
We can cut original text and add message that it was done. I don't have ideas...

I.see('*', 'div');
It will scan for all divs on page and will list all its internal texts! What a mess.
Yep, I realize that underhood we need to get all page element's texts in such a case. It also will lead to bad perfomance due additional communication selenium--browser(
It is trade off between ability to write weak locators(like location by text) and getting the best assert output...

Seems already implemented or not actual. thx


Scheduled push notifications

Is there a way to do this with Azure notification hub SDK for node? I can't find it anywhere
https://docs.microsoft.com/en-us/azure/notification-hubs/notification-hubs-send-push-notifications-scheduled
Thanks

Thank you for opening this issue! We are routing it to the appropriate team for follow up.
This appears to be a new feature request.

Hi, any updates on when this might be implemented?

Add 'service attention' label to include service team to check whether this feature is ready for swagger and requesting new sdk release. thx

Thanks! I'm also confused, the notification hub docs say to use azure-sb package, but this repo is @azure/service-bus? Should azure-sb be deprecated?

And there's also @azure/arm-notificationhubs mentioned on https://docs.microsoft.com/en-us/javascript/api/overview/azure/notification-hubs?view=azure-node-latest!

@mpodwysocki, Can you help with the question here?

@ztrange currently this is not supported in the existing azure-sb Node module.


docs/home-manager: eval options without checking config definitions

By default lib.evalModules will check all config definitions match a declared option, leading to errors like:
error: The option `wrapRc' does not exist.

Defining a freeformType would instead check such definitions match the given type, producing mismatched type errors instead of "does not exist".
_module.check can disable definition checking entirely, allowing us to evaluate the option declaration without checking the config definitions.
If _module.check is disabled, then definitions for missing options will simply not exist in the final merged config attrs.

@mergifyio queue


ansible: make apiserver port easy to configure

Atomic host cannot listen to port 443 currently, so it should be able to configure the api port.
Signed-off-by: Guohua Ouyang<EMAIL_ADDRESS>

you should just be able to set it to 6443 in all.yaml without any changes to default.yaml in your local configuration...

@eparis updated, leave default.yaml untouched.

See also https://bugzilla.redhat.com/show_bug.cgi?id=1275379#c8

@gouyang if that works, I don't think we need a PR at all, just set it in your all.yaml...

@eparis I think the point of this PR is making kube_master_api_port visible in all.yaml. Once a user met this error then he could know how to make changes.

The real fix is making low ports Just Work, but I'm (somewhat weakly) :+1: on this patch, just to make the variable more visible.

In the bug that @cgwalters mentioned above, there's discussion of handling this with systemd socket activation. I spent some time trying to make that work (my notes here), but haven't gotten it working. The systemd docs note that a daemon must know how to accept a socket from systemd, or know how to work w/ inetd-style socket passing -- that may be the issue?
We could do a systemd drop-in to make kube-apiserver run as root just on non-fedora atomics (fedora's kube sets this capability during the RPM build, so no problem there), but if that's unpalatable, making the value easier to change is at least somewhat better.

The value is already easy to change, just set it in all.yaml....

Ah, I understand now.


TypeError: this is undefined in tablesaw.jquery.js:423:10

When using tablesaw.jquery.js with Magento 1.9 I am getting this type error on this line:
var $header = $(this.cloneNode(true));

Can you attach a test case? I don’t see that on the demos.

I added thead and tbody to resolve it
On Jul 10, 2017 12:27 PM, "Zach Leatherman"<EMAIL_ADDRESS>wrote:

Can you attach a test case? I don’t see that on the demos.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/filamentgroup/tablesaw/issues/303#issuecomment-314176436,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAYJ6A5u9hXRpj3qITU8t_RGYfSiu4cZks5sMl7ugaJpZM4OS35g
.

Great—thanks! I added some better error messaging for this case in v3.0.3


Fix pg rotation

@snopoke don't think the rotation was working quite how i planned. it ended up creating a bunch more files with 1s appended at the end. i.e.:
<filename>.1.1
<filename>.1
<filename>

this is an alternative that keeps 1 weeks worth of logs

cc @TylerSheffels

Looks fine to me, no real preference on using logrotate vs whatever built in stuff postgres has


Support JSON output for the emp ps command

Fixes: https://github.com/remind101/empire/issues/823
Some sample output:
[mhahn:empire(issue-823)]$ ./build/emp help ps
Usage: emp ps [-a <app or remote>] [-o human,json] [<name>...]

Lists processes. Shows the name, size, state, age, and command.

Examples:

    $ emp ps
    run.3794  2X  up   1m  bash
    web.1     1X  up  15h  "blog /app /tmp/dst"
    web.2     1X  up   8h  "blog /app /tmp/dst"

    $ emp ps web
    web.1     1X  up  15h  "blog /app /tmp/dst"
    web.2     1X  up   8h  "blog /app /tmp/dst"

[mhahn:empire(issue-823)]$ ./build/emp ps -a acme-inc
v1.web.dfb422e5-5187-4a73-9ff1-987c66486451     1X  RUNNING  24h  "acme-inc server"
v1.worker.80f8d14e-f0c2-4bfe-968f-fdf0a3d49bee  1X  RUNNING  24h  "acme-inc worker"

[mhahn:empire(issue-823)]$ ./build/emp ps -a acme-inc -o json
{"Processes":[{"Name":"v1.web.dfb422e5-5187-4a73-9ff1-987c66486451","Size":"1X","State":"RUNNING","Age":"24h","Command":"acme-inc server"},{"Name":"v1.worker.80f8d14e-f0c2-4bfe-968f-fdf0a3d49bee","Size":"1X","State":"RUNNING","Age":"24h","Command":"acme-inc worker"}]}

[mhahn:empire(issue-823)]$ ./build/emp ps -a acme-inc -o bla
error: error writing output: output type 'bla' is not supported```

We should be able to use this setup to easily add JSON output to other commands as well.

Fixes https://github.com/remind101/empire/issues/823

Just to play devils advocate, we can already kinda do this with the emp api subcommand:
$ emp api get /app/acme-inc/dynos | jq '.'
[
  {
    "attach_url": null,
    "command": "acme-inc server",
    "created_at": "0001-01-01T00:00:00Z",
    "id": "",
    "name": "v17.web.4c9dad6d-7de8-44d0-bb71-e8bf9debcaef",
    "release": {
      "id": "",
      "version": 0
    },
    "size": "256:1.00gb",
    "state": "RUNNING",
    "type": "web",
    "updated_at": "2016-06-15T04:40:12Z"
  },
  {
    "attach_url": null,
    "command": "acme-inc server",
    "created_at": "0001-01-01T00:00:00Z",
    "id": "",
    "name": "v17.web.4dfa565c-6e2a-418c-a428-8e7373ed0878",
    "release": {
      "id": "",
      "version": 0
    },
    "size": "256:1.00gb",
    "state": "RUNNING",
    "type": "web",
    "updated_at": "2016-06-14T02:46:04Z"
  }
]

There's definitely downsides to that, because it's coupled to the Heroku platform api types.

Going to close this, we should just use that emp api command.


Hardcoding Mouse/Pen Paw Color?

Hello, so I've been fiddling around with the source code for a while trying to figure out how to hardcode in a new paw color. So far, I've been able to modify the color of the edge, but not the fill color itself (so I end up with a different color outline but a white inside). What line(s) should I modify to do so?
I'm assuming that it has to do with the osu.cpp file as that is the only gamemode that actually draws a mouse/pen arm, but I've changed every line referencing "color" without luck. I'm new to C++ and SFML so I'm not familiar with the code.
Thanks for the help!

Solved. For future reference for everyone else, here are the edits in osu.cpp:
// drawing arms
    sf::VertexArray fill(sf::TriangleStrip, 26);
    for (int i = 0; i < 26; i += 2)
    {
        fill[i].position = sf::Vector2f(pss2[i], pss2[i + 1]);
        fill[i + 1].position = sf::Vector2f(pss2[52 - i - 2], pss2[52 - i - 1]);
		//Color Edits?
		fill[i].color = sf::Color(204,153,204,255); //Replace the first 3 values with the RGB of your color, last number is alpha
		fill[i+1].color = sf::Color(204,153,204,255); //Repeat as above
    }
    window.draw(fill);

Thank you for the suggestion. Initially, there was such an option, but I deemed it obsolete and remove it. I will add it to the source again.


Add ThreadSafeRefcountedResourceHeap as a new crate on roc

@bhansconnect there are a few things clip isn't happy with -- I've looked at these, but I don't trust myself enough to fix these.
$ cargo clippy -p roc_std_heap
warning: `roc_std_heap` (lib) generated 14 warnings


fix(client): Don't attempt to build simple classic URL if source URL is not a default platform URL

What this PR does / Why we need it:
Currently if a user wrongly configures a classic URL with an oAuth client, a simple classic
URL will be built for it (not replacing anything from the valid classic URL) and we'll continue
with the assumption that the client is now configured for a platform and classic URL.
Once we attempt to make platform API calls against the configured URL, these calls will
result in hard to decypher errors.
The addition of creating a classic URL without making an API call, has thus removed our
check and error messages catching if the given URL is not for a platform environment at
all.
Special notes for your reviewer:
To be able to nicely test the mixture of URL pattern based logic and REST API calls, the metadata functions are refactored to accept a simple client interface instead of a plain rest.Client.
This allows to nicely mock interactions by just re-writing the Get method, while being able to use fake domains matching platform environment patterns instead of being limited to using the httptest.Server's IP address as URL input.
Does this PR introduce a user-facing change?
Yes - they get helpful error messages again when configuring an oAuth client for classic environment URLs, instead of getting difficult to understand errors once we try to hit invalid APIs thinking it's a platform env.

E2E tests once again failed with a 504 from the Account Management API..


Use repo cid as root (instead of commit cid)

The url now takes a repo cid instead of a commit cid as the root, where the repo is an IPFS object with the structure:
{
  "HEAD": "refs/heads/master",
  "refs": {
    "heads": {
      "master": <z8mWaFytVvoQSUxEjaVqC3MrFMH9ZT435>,
      "archive": {
        "scala": <z8mWaGm8DnUkeudLyvNqAHJsdRpYoxGuB>
      },
      ...
    }
  }
}

Default branch:

Different branch:

Commits page:

Note that I haven't updated the Demo Tree link as I don't have a publicly available server to pin the repo object on. I created it by pushing the master and archive/scala branches to git-remote-ipns

Wow that's nice!
I've pinned a tree on my server - http://<IP_ADDRESS>:8080/ipfs/QmZ4Wu1Sn3i4WTP9ArLob2KY4LUKZq5Fp7rAuUA1sAa8Pd/#/repo/QmViWi5az9iiPzESM6ruHf84TcmHSAVQ2KQdNveoDH7eaY


Unable to install azure cli on ubuntu 24

Describe the bug
i am trying to install azure cli by following the official documentation but i am not able to do so because i am getting an dependency error.
this is the documentation i am following.
offficial doc
Related command
the command i am trying to run
sudo apt-get install azure-cli
Errors
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
azure-cli : Depends: libffi6 (>= 3.0.10~rc8) but it is not installable
Depends: libssl1.1 (>= 1.1.1) but it is not installable
E: Unable to correct problems, you have held broken packages.
Issue script & Debug output
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
azure-cli : Depends: libffi6 (>= 3.0.10~rc8) but it is not installable
Depends: libssl1.1 (>= 1.1.1) but it is not installable
E: Unable to correct problems, you have held broken packages.
Expected behavior
should install correctly
Environment Summary
os linux ubuntu 24

Additional context
i have tried to look into other issues but they are useless as well.

Thank you for opening this issue, we will look into it.

24.04 is not supported yet, see https://github.com/Azure/azure-cli/pull/28888
I can't repro. The error you encountered is strange.
If you use one-line script, you should be able to install the Ubuntu Jammy's package.
If you use step-by-step method, you will see E: The repository 'https://packages.microsoft.com/repos/azure-cli noble Release' does not have a Release file. error.

Hello,
I am running into a similar issue on an Azure VM running: Ubuntu 20.04.6 LTS (GNU/Linux 5.15.0-1063-azure x86_64)
more logs below
adminuser@host:~$ sudo apt update
Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease
Hit:2 https://packages.microsoft.com/repos/azure-cli bionic InRelease
Get:3 https://packages.microsoft.com/ubuntu/20.04/prod focal InRelease [3632 B]
Hit:4 http://archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:5 http://archive.ubuntu.com/ubuntu focal-backports InRelease
Hit:6 https://download.docker.com/linux/ubuntu focal InRelease
Hit:7 http://security.ubuntu.com/ubuntu focal-security InRelease
Hit:8 http://apt.postgresql.org/pub/repos/apt focal-pgdg InRelease
Fetched 3632 B in 1s (4569 B/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
1 package can be upgraded. Run 'apt list --upgradable' to see it.

adminuser@host:~$ apt list --upgradable
Listing... Done
azure-cli/bionic 2.60.0-1~bionic all [upgradable from: 2.43.0-1~bionic]
N: There are 130 additional versions. Please use the '-a' switch to see them.

adminuser@host:~$ sudo apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

adminuser@host:~$ az upgrade
This command is in preview and under development. Reference and support levels: https://aka.ms/CLI_refstatus
Your current Azure CLI version is 2.43.0. Latest version available is 2.60.0.
Please check the release notes first: https://docs.microsoft.com/cli/azure/release-notes-azure-cli
Do you want to continue? (Y/n): Y
Get:1 https://packages.microsoft.com/repos/azure-cli bionic InRelease [3600 B]
Get:2 https://packages.microsoft.com/ubuntu/20.04/prod focal InRelease [3632 B]
Hit:3 https://download.docker.com/linux/ubuntu focal InRelease
Hit:4 http://archive.ubuntu.com/ubuntu focal InRelease
Hit:5 http://security.ubuntu.com/ubuntu focal-security InRelease
Hit:6 http://apt.postgresql.org/pub/repos/apt focal-pgdg InRelease
Hit:7 http://archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:8 http://archive.ubuntu.com/ubuntu focal-backports InRelease
Fetched 7232 B in 1s (8975 B/s)
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 azure-cli : Depends: libffi6 (>= 3.0.10~rc8) but it is not installable
E: Unable to correct problems, you have held broken packages.
CLI upgrade failed.

@bebound cannot access this guid.
and i am installing this for the first time

I fixed the link.
Hmm, that's odd if it's your first-time installation.

I'm getting a fairly similar error when installing azure-cli using sudo DEBIAN_FRONTEND='noninteractive' /usr/bin/apt-get -y install azure-cli:
The following packages have unmet dependencies:
 azure-cli:amd64 : Depends: libc6:amd64 (>= 2.38) but it is not installable
                   Depends: libcrypt1:amd64 (>= 1:4.1.0) but it is not installable
                   Depends: libffi8:amd64 (>= 3.4) but it is not installable
                   Depends: libgcc-s1:amd64 (>= 4.2) but it is not installable
                   Depends: libssl3t64:amd64 (>= 3.0.0) but it is not installable
                   Depends: libuuid1:amd64 (>= 2.20.1) but it is not installable
                   Depends: zlib1g:amd64 (>= 1:1.2.0) but it is not installable

I try to prep for the install with echo "deb [arch=amd64] [https://packages.microsoft.com/repos/azure-cli/](https://www.google.com/url?sa=D&q=https%3A%2F%2Fpackages.microsoft.com%2Frepos%2Fazure-cli%2F) noble main" | sudo tee /etc/apt/sources.list.d/azure-cli.list


⚠ Bofrost.at has degraded performance

In e7e0b43, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1133 ms

Resolved: Bofrost.at performance has improved in 05b7433 after 39 minutes.


update deps

Codecov Report

Merging #54 into master will not impact coverage.

@@           Coverage Diff           @@
##           master      #54   +/-   ##
=======================================
  Coverage   82.67%   82.67%
=======================================
  Files          13       13
  Lines         202      202
=======================================
  Hits          167      167
  Misses         35       35

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 000c00a...2f607d6. Read the comment docs.


TestRpm.java:37-40: Continue test rpms implementation:...

The puzzle 235-1ed04df5 from #235 has to be resolved:
https://github.com/artipie/rpm-adapter/blob/aa096e0866386ef37e21436b3241138ae929b895/src/test/java/com/artipie/rpm/TestRpm.java#L37-L40
The puzzle was created by @olenagerasimova on 09-Jun-20.
Estimate: 30 minutes,  role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

@g4s8/z, @olenagerasimova/z please, pay attention to this issue

@0crat in

The job #248 assigned to @victornoel/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this; there will be a monetary reward for this job

The puzzle 235-1ed04df5 has disappeared from the source code, that's why I closed this issue.

@0pdd the puzzle #265 is still not solved.

@sereshqua/z please review this job completed by @victornoel/z, as in §30; the job will be fully closed and all payments will be made when the quality review is completed

@0crat quality good

@0pdd the only puzzle #265 is solved here.


Add updatedAt & lastEditedBy to task model & schema

Backend support for saving tasks' last modified timestamps and userId who did the edit

Applied fixes from comments


[terraform] Make Vault data persistence configurable

Make Vault data non-persistent if validator data is too.

What happens when Vault restarts, causing the keys to change?

What happens when Vault restarts, causing the keys to change?

Dunno, hopefully it doesn't crash. But if the validators all start from scratch on a push we need Vault to do so too.

Looks good to me. Quick q though: would it be possible to restore vault data? e.g. If the vault container crashes and restarts, we still have its old volume until ECS decides to clean it up. Could we just point vault to its old volume?

Theoretically yes. Why do you think this is necessary though? If the testnet is running without persistence we're assumedly okay with it losing data and restart arbitrarily.

@bors-libra r=rustielin

:pushpin: Commit 979c716 has been approved by rustielin

:hourglass: Testing commit 979c71611de7b39e27a88184ba8cbaef499ab9a4 with merge 8e7bc23049dafd4b9ab980aa037b95780c453036...

Theoretically yes. Why do you think this is necessary though? If the testnet is running without persistence we're assumedly okay with it losing data and restart arbitrarily.

Nonpersistent storage was added to improve devnet liveness, but if vault restarts and the validators themselves don't, then the network is stuck. Agreed we don't care about data loss and arbitrary restarts in general, but this will halt the entire network until at least 1 hr later until continuous push kicks in. Not too big of an issue overall though; just means we'll some manual work in the edge cases.

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: rustielin
Pushing 8e7bc23049dafd4b9ab980aa037b95780c453036 to master...


Fix Shiftable trait to shift by u64.

Shiftable shouldn't be restricted to only shifting by the same type. This seems fine for primitive unsigned integers, but e.g. for a U128 type or potentially some string type then it doesn't make sense to shift by that type.

Why is shifting a smaller type by u64 not a problem?
What about overflows / underflows / confusion from user about why they can shift by a larger type?
Is there no problem because all of the integers are treated / padded to be u64?

Yeah, I think so.  We can keep it simple.  Many CPU architectures will use just a u8 as the shift amount and/or ignore the bits which aren't needed.  E.g., you only need 5 bits to shift a u32 so only the bottom  5 bits of the shift amount might be used.
We might want to shift a b512 or b1024 one day, so a u8 isn't big enough.


Make titlebar dark

In the latest release notes you said that you look for a way to make the Titlebar change color. I dont know a direct solution, but when using the BlurWindow Module (python -m pip install BlurWindow) with Dark = True, the titlebar changes its color to dark. And the window also gets blurred, which looks great on modern apps! I would make a pull request, but i cant get to my PC at the moment.
EDIT: i dont know if this solution also works for the menu bar. You need to check.

Thank you a lot! I saw your beautiful project and I'm finding a way to contact you. But now it's unnecessary. Will try after holiday end.

I'm not sure how to apply blur to my program after installed BlurWindow, just started to learn about Python 4 days ago.

Its easy, just add the following lines to your code:
bg_color = ttk.Style().lookup(".", "background")
app.wm_attributes("-transparent", bg_color)
app.update()
HWND = ctypes.windll.user32.GetForegroundWindow()
GlobalBlur(HWND)

Keep in mind that you have to replace app with the name of your tkinter window.

Hi, I just want to know if you created this project by learning through YouTube. Coincidentally, I also made a program that mimics the entire code, except the theming. Just wanna know, and it's great seeing @not-nef too.

You can use the code, anyway I put my edition in the public domain, but I just want to know, since the code is like an exact copy, except your abridged features.

Wait, you said here that you saw our beautiful project, are you talking about TimerX? That's the only one I know, just a doubt. If you do like it, feel free to contribute too! We are looking for more features to add, especially since we hit the stable mark.

Hi, I just want to know if you created this project by learning through YouTube. Coincidentally, I also made a program that mimics the entire code, except the theming. Just wanna know, and it's great seeing @not-nef too.

yeah, I did lol, my teacher just taught me some basic things of python, else, I just search the internet

Oh, then it's fine. You can carry on. I still have to update my code base lol.

I will do if I learn more things in the future, my knowledge currently is still very basic!

Its easy, just add the following lines to your code:
bg_color = ttk.Style().lookup(".", "background")
app.wm_attributes("-transparent", bg_color)
app.update()
HWND = ctypes.windll.user32.GetForegroundWindow()
GlobalBlur(HWND)

Thanks a lot!

Also, that code works only on Windows. You need to import BLurWindow too. You can take an example of the implementation from TimerX.

Ok, my calculator was transparent, what should I do next?  This is the first time I do something much complex like this one.

Ok, my calculator was transparent, what should I do next?  This is the first time I do something much complex like this one.

I've added it after seeing it missing, still transparent. Thanks for your help. Guess I will try after holiday week. My parent told me to shut down the computer. See you later.

Bye

did you import the BlurWindow module correctly? You have to do from BlurWindow.blurwindow import *

I told @HuyHung1408 to implement it from TimerX. We did it better, hence I asked him to refer to our project.

Ok, trying now XD

did you import the BlurWindow module correctly? You have to do from BlurWindow.blurwindow import *

Yes, here is what happening

I think that is how it is supposed to be... Did you import ctypes?

I think that is how it is supposed to be... Did you import ctypes?

yes, after the from BlurWindow.blurwindow import *

I meant not supposed to be, sorry for that. @not-nef can you tell how you added blur to TimerX? The TimerX system theme issue with transparency is here, although it's only transparency. How'd you do that?

Oh... I experimented with that. For got about it. Let it be. I will try making a PR to fix this tomorrow, can't boot my PC atm.

Oh... I experimented with that. For got about it. Let it be. I will try making a PR to fix this tomorrow, can't boot my PC atm.

Ok, thank you a lot

Also, I can't promise when I will make the PR, it's heavy IRL here. So, it is a big if, but if I get the chance, I'll utilise it.

That's ok, don't worry. We can try another method if it didn't work

Thanks a lot, guys, I got it working after reviewing TimerX python files, light mode is cursed haha

I think I'll use the button instead of the command bar button for the dark/mode switcher since making the command bar dark will be more complicated. I guess I will focus on the dark/light mode switcher then will add blur and dark title bar later

Thanks a lot!

I pushed my latest changes to Github, there or some issues like Acrylic works with dark mode on start, click 'M' to change dark to light mode then it changes to Acrylic with a light mode, change it again and Acrylic didn't work with dark mode. Not sure why.

Current progress! How to set the titlebar to white again after apply light theme?

Call GlobalBlur again, and this time set Dark to False

Call GlobalBlur again, and this time set Dark to False

Like this, right?

Lookin' great! Hiya @sumeshir26!

Yep, like that

Thank all of you!


Test the Powershell escaping

This adds tests, that you should meet; the tests fail at the moment. You will need to escape \ also, just like cmd-escaping does. I hope this will help you get the PR merged for good.
Required by: junegunn/fzf#2647

Dismissed in https://github.com/junegunn/fzf/pull/2647#issuecomment-953602248, and fully replaced by #2.


Error during stats analysis

Can you provide a page and stats example to reproduce the error?

How canI share stats.json? It's quite big

You can zip it and attach to this issue
Also you can create a stats without sources, just disable it in your webpack config:
stats: { all: true, source: false }

stats.json.zip

Seems like all is ok (I can't reproduce it) 🤔
Which browser (Name + version) do you use?

Chrome 86.0.4240.198 Windows
The same is on Mac Book

@budarin can you check now?

What does it means deopts ?

the error is still present
class l {
constructor(e) {
this.readers = e.map(e=>{
const t = new s(e);
return t.eventProgress.on((e,{total: t, loaded: n, chunkSize: r})=>{
this.loadedBytes += r,
this.eventProgress.emit(this, {
total: this.totalBytes,
loaded: this.loadedBytes
})
}
),
t
}
),
this.totalBytes = e.reduce((e,t)=>e + t.size, 0),
this.loadedBytes = 0,
this.eventProgress = new o.a
}
e is FileList so it doesn't have map property

What does it means deopts ?

Please, ask the question on Discussions page

e is FileList so it doesn't have map property

I've updated https://statoscope.tech/ to normalize FileList to array

Ок

Is the problem still actual?


Appsec action 6.3: Potentially Inadequate Session timeout 🤔 (low)

The application did not appear to have an idle session timeout mechanism in place. The application was only accessible via a normal user account, which was left logged in for varying time periods (over a couple of hours) without session termination occurring. The impact of this is that a threat actor with access to the session, either through physical access or a session-based attack, could operate the application under the context of the logged in user. This access could potentially be utilised to obtain sensitive information or modify information.
Note the test was conducted on a development environment, it is not clear if the instance represented a like to like production environment configuration.
For example the following response shows the session cookies are set for a very long period of time.

Remediation
It is recommended that an idle session timeout value is set for all authenticated sessions. Ideally, for an application of this nature, this should be set to 30 minutes.
Session Management - OWASP Cheat Sheet Series

Investigate what happens if we reduce Django default to (say) 30 minutes. Are users silently re-authed or do they have to gpo through full Entra auth again?
If it's the latter usability will take priority.

@jemnery They do not have to go through full re-auth but it's not silent either.
If you are logged into 2 microsoft accounts for any reason, you need to pick which one you want to sign in with.
This window is still shown even if you completely sign out of the other account


bring back take-what-you-want

Reticketing from #3414 ...
We lost our team distribution algorithm in #3414. We should bring it back by upgrading transfer_takes to process_payroll in payday.py, but first we should ...

[x] Determine the relationship between Gratipay Teams and their members (https://github.com/gratipay/inside.gratipay.com/issues/242)
[x] Build a vault to store PII (https://github.com/gratipay/gratipay.com/issues/3504)
[x] Bring back take-what-you-want for Team Gratipay (#3994)
[ ] Decide to prioritize this.

Notify

[ ] https://gratipay.freshdesk.com/helpdesk/tickets/2184
[ ] https://gratipay.freshdesk.com/helpdesk/tickets/2185
[ ] https://gratipay.freshdesk.com/helpdesk/tickets/2234
[ ] https://gratipay.freshdesk.com/helpdesk/tickets/2312
[ ] https://gratipay.freshdesk.com/helpdesk/tickets/2301
[ ] https://gratipay.freshdesk.com/helpdesk/tickets/2366
[ ] https://gratipay.freshdesk.com/helpdesk/tickets/2427
[ ] https://gratipay.freshdesk.com/helpdesk/tickets/3126
[ ] https://gratipay.freshdesk.com/helpdesk/tickets/6699

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

One way to address the question of the relationship between teams and their members would be to add a "percentage withholding" to the takes table, which only the team owner could set. On the one hand that would make it clear to team owners that this is something they need to think and decide about, and on the other it leaves it flexible in terms of specific arrangements. We can't wait to model all of the world's employment law before we re-release the payroll feature.

takes table

Erm, the payroll table, rather.

Setting to blocked on https://github.com/gratipay/inside.gratipay.com/issues/242.

It's a lot of overhead to set up a company, even if we can pull off "company as a service." We want to ensure that Teams on Gratipay create open work for people, but we don't want to overburden Teams that are just starting out. We should consider allowing Teams to receive up to a certain amount per week before requiring them to go through identity verification (#988) and turn on payroll. Maybe $1,000 per week?

+1 @josegonzalez at https://github.com/gratipay/team-review/issues/63#issuecomment-143322776:

How do I add users to the dokku team?

How do we bring back payroll?

The deps for Payroll in that graph are just infosec and idv. How does Gratipay's own governance (https://github.com/gratipay/inside.gratipay.com/issues/72) relate to payroll?

https://github.com/gratipay/inside.gratipay.com/issues/402#issuecomment-158508184

Alright. We need payroll.
Everything else hinges on that.
Until we have payroll, we're vaporware. We're only half a product.
Who needs another payments solution?
There's gillions of those.
But there's no other take-what-you-want payroll system: that's Gratipay.
I can't pitch https://github.com/naspeh/mailur until we have payroll.
Generalizing: we can't sell until we have payroll.

Moving stream of consciousness over to gratipay/gratipay.com#3433 ...
Ducking back out to ask: How does Gratipay's own governance (gratipay/inside.gratipay.com#72) relate to payroll?
Payroll is about getting money to three groups of people:

draws to owners
wages/salary to staff
payments to independent contractors

The question of Gratipay's governance determines how Gratipay itself will use payroll.
HOW DO WE BRING IT BACK!?!?!?!?!?
We have to bring it back!
Both in general—it's our core product!—and in particular—we have to pay ourselves!
Teams on Gratipay have to be legal entities in order to use payroll.
It honestly doesn't matter what kind.
LLC, S, C, B, PBC, Ltd., Plc., etc., &c.
Charitable or not.
Fiscally sponsored or not.
The real heart of the matter for Gratipay is that payroll has to tie to tax withholdings.
We want to be agnostic about specific tax laws.
We have to push that burden out to our customers.
We have to go the Braintree route—bring-your-own [entity] at first, with an "easy" button later—instead of the Stripe route—"easy" button-only out of the gate.
We have to go the BYOE route because we don't have the capital to go the Stripe route.
So then payroll is an optional add-on for Teams?
And it's pretty manual?
Like, for each member you add to a Team, you set up some rule about withholding?
Let's say for Gratipay we adopt some rule like, "We pay you as a contractor for up to 6 months if you're in the U.S. or 18 months if you're outside the U.S. After that we pay you as an owner."
That gives @rohitpaulk et al. time to jump through the hoops of becoming a co-owner of a U.S.-domiciled cooperative.
And they can still get paid in the mean time.
(Perhaps we also have a dollar cap: 18 months or $18,000 or something like that. A Q for the Ls.)
We add @rohitpaulk to the Gratipay Team with withholding of 0% (he's a contractor).
After a year or whatever, he gets his paperwork all done and we can promote him to an owner (yay!).
Now his withholding is set at 35%.
Do we care to force Teams to use payroll?
Do independent contractors still get to take-what-they-want?

I can't pitch https://github.com/naspeh/mailur until we have payroll.
Do we care to force Teams to use payroll?

If we don't care to force Teams to use payroll, what's stopping me from pitching https://github.com/naspeh/mailur?

If teams aren't forced to use Gratipayroll, does that affect requiring open work?

If teams aren't forced to use Gratipayroll, does that affect requiring open work?

I guess not.  NM.

@mattbk I think it does!

@whit537:

I think it does!

Could you expand on that? It was my understanding that 'open work' included projects that did not intend to distribute funds to anyone but the maintainer/owner/'team of one', as long as there was a clear path for onboarding to the project through a CONTRIBUTING file or similar.
We don't intend to cause all teams on GP to context-switch to the extrinsic incentives of money, do we? I think that could backfire badly by crowding out the intrinsic incentives of the F/LOSS gift economy without replacing them with sufficient monetary compensation to make up the loss.

@webmaven One of the requirements/TOS at the moment is that teams plan to use Gratipayroll once it comes back. Not sure if that relates.

@mattbk:

One of the requirements/TOS at the moment is that teams plan to use Gratipayroll once it comes back.

Hmm, but that doesn't mean that a Gratipay team (in particular 'teams of one', but larger ones as well) must ever have more than just the owner on the payroll, does it? Regardless of how many team members there are, or how many contributors there are on Github (or elsewhere, for non-code projects)?
A quote from the paper at the link I included above:

The definition of what constitutes “small” and “large” incentives depends on the case, but the message seems to be clear: as Gneezy and Rustichini’s (2000a) title suggests, “Pay enough—or don’t pay at all.”

There is very likely a threshold amount below which distributing pay to team members will decrease their (and others') contribution of work to a project. I am uncertain to what extent this may be ameliorated by a user being a member of several teams, and receiving 'enough' in aggregate.

Hmm, but that doesn't mean that a Gratipay team (in particular 'teams of one', but larger ones as well) must ever have more than just the owner on the payroll, does it?

I'm coming around to that idea; honestly I think that if I were to start receiving donations and had other contributors, Gratipay would be the easiest way to let them share in the spoils. I think that's what we should go for, anyway.
I'd like to see the sort of ecosystem develop where a ~user could be part of several teams (and own several teams), where everyone ends up receiving enough to make it worthwhile.

@mattbk:

Gratipay would be the easiest way to let them share in the spoils.

Absolutely, as long as the spoils are enough to make sharing worthwhile. I don't know what the threshold is, but I imagine that a team where your share is $.01 a week will actually demotivate you relative to other teams where your share is larger.

I'd like to see the sort of ecosystem develop where a ~user could be part of several teams (and own several teams), where everyone ends up receiving enough to make it worthwhile.

Yes, only the tricky thing when money enters as an extrinsic motivator is that it displaces intrinsic motivations, and if the money isn't enough to make it worthwhile, we can see a net decrease in motivation.
In some ways, the original GitTip model sidestepped this brilliantly: not only didn't you know who was giving you money, but you also didn't know exactly what it was for (unless you were only doing one specific thing), so the aggregate could be quite motivating, even for the minor projects you were contributing to.
Now, many distinct projects will have distinct teams (so it will be clear which projects get more support than others), and team members will know how much they are getting from each team they are on (so it will be clear to them which efforts are being rewarded by how much).
This level of transparency has potential for good and ill. Meanwhile, only 'teams of one' will actually preserve the quality of 'thank you you for all you're doing, keep it up!', so I wouldn't be in any hurry to force people away from that model, unless the aggregate amount they are receiving makes it clear that spreading things around will have a net benefit (but I don't know where that threshold is, though I suspect it is likely somewhere between $2k-8k/month).

@webmaven The Geezy paper assumes a principal-agent relationship in which the principal (Team owner) controls the money that the agent (Team member) receives. This is specifically what Gratipay's take-what-you-want payroll undercuts: now the agent controls how much they share in the spoils. That's how we get around the crowding-out problem.

It was my understanding that 'open work' included projects that did not intend to distribute funds to anyone but the maintainer/owner/'team of one'

The principal's (project's) intention is not determinative, because on Gratipay 2.0, the agent is the one empowered to initiate the work relationship.

If teams aren't forced to use Gratipayroll, does that affect requiring open work?

@mattbk I think you were right to flag the implication of what I was saying, "Do we care to force Teams to use payroll?" If we don't require Teams to use payroll, then we're not truly giving control to the agent (in Gneezy's parlance).
Over on Customers we say that:

Our primary customer is ~picard: the manager of an open company.

Our secondary customer is The Enterprise's customer: ~alice.
Our tertiary customer is The Enterprise's employee (contractor, agent, etc.): ~crusher.

Now, ~crusher is Gneezy's agent. What we are really trying to build is an economy for ~crusher to plug into. The vision is for Crusher to visit Gratipay.com and find tens of thousands of open organizations with millions of dollars in unallocated wealth. Crusher goes shopping and picks an organization or eight to get involved with. Crusher is in charge of initiating each work relationship, how much she works for whom, and how much she takes.
We need Picards that buy into this vision. Our Picards need to be open to having Crusher initiate a work relationship with the Enterprise.

We need Picards that buy into this vision. Our Picards need to be open to having Crusher initiate a work relationship with the Enterprise.

This needs to be spelled out rather than implied. It's up to Crusher to do the work, and up to Picard to_allow_ Crisher to be part of The Enterprise. Crusher can take what he wants, but the allowance needs to be on Picard's part.

spelled out rather than implied

Proposal? I think we've been trying to do this. Let's keep trying! :-)

Crusher can take what he wants

s/he/she ;-)
https://en.wikipedia.org/wiki/Beverly_Crusher

It's up to Crusher to do the work, and up to Picard to_allow_ Crisher to be part of The Enterprise.

This is the big psychological change with Gratipay 2.0. This is the essence of what we're about. We have to figure out how to communicate it in the simplest terms.

The next big step on this ticket in my thinking is a call with a lawyer. I met one, Eric Davis (on a ticket somewhere?), who claims extensive experience with worker-owned co-ops as well as tax law. I've emailed him once (cross-posted on a ticket somewhere). I have his business card in front of me and am planning to phone him next week. We've got to figure out the structure for Gratipay (https://github.com/gratipay/inside.gratipay.com/issues/242), write our operating agreement accordingly (https://github.com/gratipay/inside.gratipay.com/issues/72), and then bring back payroll for Gratipay only. Depending on the answer from Eric or whomever, we'll look at how to structure Teams so that everyone can participate in payroll.
We still need a vault (#3504) and idv (#2449, #3557), of course.
WE WILL DO THIS.*

* Lord willin' and the creek don't rise.

[ ] Meet with Eric Davis

@whit537

This is specifically what Gratipay's take-what-you-want payroll undercuts: now the agent controls how much they share in the spoils. That's how we get around the crowding-out problem.

Given that the agent's control is not absolute (for one thing, they can't take more 'spoils' than actually exist), and that while they may initiate the relationship, the owner must approve it (and in practice for many and perhaps most projects, acceptance onto a GP team may require some amount of uncompensated volunteer labor being done as a precondition), and since the summary paper I linked to cites other scenarios than just those that can be boiled down to Principal-Agent, I am not quite so sanguine.
However, if we do see a crowding out effect, there are hints of how we might attempt to fix it in that same paper, such as:

In one condition using subjects in Sweden, they offered $7 for donating blood; in another condition, they offered $7 with the option to donate the money to charity. Interestingly, they find evidence of a detrimental effect on blood donations of the payment without the charity option. [...] Consistent with the finding that incentives interact with individuals’ image motivation, blood supply goes back to “normal” in their study when the monetary incentive is combined with an option to donate to charity.

Gosh. @mitar bringing up Open Collective has me thinking about openly compensating voluntary capital in addition to voluntary labor. We've been paying a lot of attention to bringing back payroll in the context of compensating labor. But what about compensating capital? We're thinking about whether capital has a role in building Gratipay itself (certainly Patreon and now Open Collective benefit from capital, seemingly at our expense). Would we need take-what-you-want payrollouts in order to bring in capital the way we want?
If we don't implement compensating voluntary capital as part of this ticket, then let's be sure to reticket.

If we don't implement compensating voluntary capital as part of this ticket, then let's be sure to reticket.

Reticketed as #3908.

The only real reason I'm interested in GratiPay is so I have a controlled way of adding team members and then accepting payments which are automatically divided among the group, fairly. I can help in any way possible to help hurry this up--whatever you need from me--do you need funding? I'm a very skilled Python dev--do you need Python developers? I have an in-depth experience with full stack development...
Just let me know what I can do to expedite this feature being brought back, because it's the only reason I see gratipay being so useful it's popular, I really believe that this model is what most people will think of.  People probably aren't really looking to fund drive-by/one time PRs, that seems like a Bountysource kinda thing.
It's important that the distribution method is simple for marketing purposes too, or people just won't donate. In fact, the fact that Gratipay already looks so kind of... ambiguous, vacant, yet confusing, is what keeps most Gratipay accounts receiving nothing or next-to-nothing.
I am willing to work with y'all to solve these issues, but I would want to talk to someone on Skype beforehand. I have lots of keen connections, and some serious work ethic, so let's make this happen!
I was thinking of making my own service like this, but I've decided to help you guys instead. :)

Thinking more about what we need to do to make this happen:

Collect and verify personal identity information for individuals, both Team owners and Team members.
Collect and verify legal entity information for Teams (sole proprietorship, partnership, etc.).

Should we separate Organizations from Projects? Verify the organization once and then have multiple projects? Could be useful for the "subteams" idea (cf. https://github.com/gratipay/inside.gratipay.com/issues/441).
Perhaps entity verification doesn't kick in until a threshold—say $5,000 per year in revenue (cf. https://github.com/gratipay/inside.gratipay.com/issues/242#issuecomment-181180345).

Reimplement member adding and team takes during payroll

explore "equal split" in addition to "take-what-you-want"
other tweaks

Let's find the MVP in there that allows the Gratipay Team to fulfill its own tax reporting obligations from within Gratipay itself (no out-of-band information handling).

Let's find the MVP in there that allows the Gratipay Team to fulfill its own tax reporting obligations (cf. gratipay/inside.gratipay.com#242) from within Gratipay itself (no out-of-band information handling).

I suppose this is a question for our accountant.

To: CPA
Subject: info required for non-U.S. contractors?

We've got some contractors in India, Pakistan, Europe, and other parts of the world. What are my tax obligations and what are theirs? What info do I need to collect from them and what forms do I need to file?

As to tax obligations for other countries and contractor payments, it will depend on the tax treaties the US has in place with those countries.  I know that for India, any contractor you pay direct to India and who will not step onto US soil in the next 12 months for longer than a few weeks, has no US obligation for payments they receive.  Meaning, they report this income to their home country and you do not report anything on a 1099 to them since they do not have a US tax ID.

I am not sure on the other countries as there are many differences.  I can research Pakistan but I would need to know specific countries within the EU.

Alright, cool! So basically we'll have the accountant give us an answer for each jurisdiction. What jurisdictions do we need in order to relaunch payroll for Gratipay?

India: @rohitpaulk @aandis
Pakistan: @TheHmadQureshi
Trinidad: @chrisdev @kaguillera
Belarus: @techtonik
U.S.A.: @mattbk @clone1018 @tlevine @dmk246 @whit537 @webmaven @kzisme

Who am I missing? Speak up! :-)

Thinking more about what we need to do to make this happen:

We don't need (2) for a Gratipay MVP (we already know our own legal entity information ;). We do need (1), for the U.S. folks and perhaps others depending on tax treaties.

Thanks, Peter. After double-checking, we actually don't need Europe right now. To start with, besides India, let's look at Pakistan, Belarus, and Trinidad. We also have contractors in the U.S.

What do we do with me? I'm the sole owner of the LLC. How do you recommend we handle payments from Gratipay to me?

Give me a bit of time on Belarus and Trinidad.

As for yourself, you report total income less expenses.  If you are able to pay yourself, it is either coming from the company profits, or you are repaying personal loans you made to pay for things for the company.

So there are no ‘payments’ from the company to you.  You report the net taxable income for the company and pay tax on that.

Okay, I was under the impression that I could optionally structure payments as W-2 up to market rate. Perhaps that applies to a multi-member LLC?

What you are describing is only if Gratipay were a corporation and only inasmuch as cash flow would permit.

Compensation in a multi-member LLC is a little different as members do show compensation for services.  But the net taxable income is still passing through onto their personal returns in proportion to ownership.

Gotcha, thanks.

Pretty sure the LLC can elect to be taxed as a corporation, but no need to muddy the waters at this point.

Does Gratipay have an EIN of its own?

@mattbk Yes!

My small business (not my day job) pays me and my business partner a salary, out of which is retained the normal payroll taxes, and at the end of the year we get W-2s. We also paid an employee last year, as well as a few independent contractors. So it seems weird that another entity with an EIN wouldn't operate in a similar way.
We're not an LLC, though, and I'm sure Gratipay's CPA has a better grasp on the structure than I do. We also have to fill out corporate income taxes, which is weird since we're a (state) nonprofit. Glad I have a CPA of my own to help me out with this stuff, because it's clear as mud to me.

We're not an LLC, though

Yeah, that's the difference. By default, LLC's are treated as pass-throughs for federal tax purposes (i.e., either a sole proprietorship or a partnership). Having an EIN means Gratipay, LLC can employ others, but doesn't affect how owners (i.e., moi) are treated.

Setting to blocked on gratipay/inside.gratipay.com#242.

gratipay/inside.gratipay.com#242 is closed now; what else is blocking this (large and unwieldy) issue?

Now we're blocked on https://github.com/gratipay/inside.gratipay.com/issues/214 and then we'll be blocked on https://github.com/gratipay/inside.gratipay.com/issues/256 and https://github.com/gratipay/gratipay.com/issues/2449.

:weary:

🐢

:checkered_flag:                                                                                🐢

+1 from @PeterDaveHello at https://github.com/gratipay/team-review/issues/86#issuecomment-195766440.

:+1:

We're scoping this down to just Team Gratipay + 6 ~users (https://github.com/gratipay/inside.gratipay.com/issues/569#issuecomment-210073291).

Now we're blocked on gratipay/inside.gratipay.com#214

By agreement of the 6 ~users (https://github.com/gratipay/gratipay.com/issues/3504#issuecomment-210168086), we're no longer blocking this on PCI self-assessment.

and then we'll be blocked on gratipay/inside.gratipay.com#256 and #2449.

We know the six, so we're also shedding programmatic id verification.
Unblocked!

But really we should use this for bringing back payroll for everyone, not just Team Gratipay. We've got a good list in the description of people to notify. They don't want to know when payroll is back for Gratipay, they want to know when it's back for them.

Dropping from the "Bring Back Payroll for Team Gratipay" milestone, but linking in the product roadmap (https://github.com/gratipay/inside.gratipay.com/issues/581#issue-149327641).

Saving here so it doesn't get swept downstream in the Radar:

When someone on staff at a Team I'm applying to or working for views my identity info, I should get an email notification to that effect, possibly with an opt-in required before the person gets to see my info.

https://github.com/gratipay/inside.gratipay.com/issues/589#issuecomment-215991233

Payroll is specifically used for employees. You should avoid that term for contractors.

https://github.com/gratipay/gratipay.com/issues/3994#issuecomment-216836470

Gosh. It's really nice to have figured that out now before rolling out a whole product called "Payroll." Yay for expertise and thinking ahead! :-)

+1 from https://gratipay.freshdesk.com/helpdesk/tickets/6699. Added to notifications.

+1 from https://twitter.com/failvarez/status/879854055379554304, although he would like even splits (which should be an option).


net/tcp/udp: allocate tcp/udp connect dynamically

Summary
net/udp: rename NET_UDP_CONNS to NET_UDP_CONNS_PER_ALLOC
net/tcp: rename NET_TCP_CONNS to NET_TCP_CONNS_PER_ALLOC
net/udp: allocate udp connect dynamically
net/tcp: allocate tcp connect dynamically
Impact
tcp/udp connect instance allocate
Testing
tcp/udp client/server test

What's the motivation for allocating the resources dynamically?
The decision for this type of change should consider an analysis of the tradeoffs.

I think dynamic allocation in the kernel makes NuttX more unpredictable for realtime applications. Maybe it could be dependent of some option like CONFIG_ALLOW_NON_RT_BEHAVIOR. What do you think?

What's the motivation for allocating the resources dynamically? The decision for this type of change should consider an analysis of the tradeoffs.

To support the complex system better, we have saw in a production system:

Application or server may create more socket in some special case
New version may create more socket and then old config stop working
TIME_WAIT state in TCP make the situation even worse:
http://www.serverframework.com/asynchronousevents/2011/01/time-wait-and-its-design-implications-for-protocols-and-scalable-servers.html

Yes, it's a tradeoff, but dynamic allocation already exist inside socket API before this patch.

I think dynamic allocation in the kernel makes NuttX more unpredictable for realtime applications.

Yes, TLSF allocator may improve the real time a little bit(http://www.gii.upv.es/tlsf/).

Maybe it could be dependent of some option like CONFIG_ALLOW_NON_RT_BEHAVIOR. What do you think?

or we can do the initial allocation in initialization since the realtime behavior is same as before until we use up the reserved conn.

How about adding an dynamic enable option? If dynamic allocate is enabled on the basis of the pre-allocation pool,
then we will allocate new connection instances from the heap.
Of course, we will also add the maximum limit config to protect the system from malicious attacks.
CONFIG_NET_DYNAMIC_CONNS
CONFIG_NET_MAX_DYNAMIC_CONNS

The current static configuration is no longer suitable for business situation, this is intention of pull request,
In terms of real products, NuttX is not just running in simple IOT devices,
we already have a demand for full-featured business terminal, We have online video/audio streaming services,
stream transfer services, adb network bridges, high-level application networking services, etc.
Most of the time we serve in an environment where the number of connections is unknown,
For example if multicast or mesh network device as long as there is one more hardware device connected to our service in the local area network, the number of connections will increase by one. this is common scene of smart homes.
We hope to find a balance to enhance the scalability of NuttX. In most cases, other developers will have similar situations.
This connection information is dumped from Smart Speaker, the number of connections is still growing from application developers ...
 [TCP]                 LADDR    LPORT             RADDR      RPORT  RCVBUFS  SNDBUFS  SNDPEND  RCVPEND   RCVOOO
 TCP   [ 0]: [       <IP_ADDRESS>: 12904] -> [       <IP_ADDRESS>: 12903]    16384    16384        0        0        0
 TCP   [ 1]: [       <IP_ADDRESS>: 12903] -> [       <IP_ADDRESS>: 12904]    16384    16384        0        0        0
 TCP   [ 2]: [         <IP_ADDRESS>: 12905] -> [       <IP_ADDRESS>: 54322]    16384    16384        0        0        0
 TCP   [ 3]: [         <IP_ADDRESS>: 12906] -> [       <IP_ADDRESS>: 54323]    16384    16384        0        0        0
 TCP   [ 4]: [       <IP_ADDRESS>: 54322] -> [       <IP_ADDRESS>: 12905]    16384    16384        0        0        0
 TCP   [ 5]: [       <IP_ADDRESS>: 54323] -> [       <IP_ADDRESS>: 12906]    16384    16384        0        0        0
 TCP   [ 6]: [         <IP_ADDRESS>: 12908] -> [ ***************:   443]    16384    16384        0        0        0
 TCP   [ 7]: [         <IP_ADDRESS>: 12924] -> [ ***************:    80]    16384    16384        0        0        0
 TCP   [ 8]: [         <IP_ADDRESS>: 13689] -> [ ***************:    80]   131070    16384        0      541        0
 TCP   [ 9]: [         <IP_ADDRESS>: 13763] -> [ ***************:   443]    16384    16384        0        0      213
 TCP   [10]: [         <IP_ADDRESS>: 14322] -> [ ***************:   645]    16384    16384        0        0        0
 TCP   [11]: [         <IP_ADDRESS>: 14323] -> [ ***************:    80]   131070    16384        0        0        0
 TCP   [12]: [         <IP_ADDRESS>: 14633] -> [ ***************:   443]    16384    16384        0        0        0
 TCP   [13]: [         <IP_ADDRESS>: 14634] -> [ ***************:   443]    16384    16384        0        0        0
 TCP   [14]: [         <IP_ADDRESS>: 14711] -> [ ***************:    80]   131070    16384        0      123        0
 -----------------------
 [UDP]                 LADDR    LPORT             RADDR      RPORT  RCVBUFS  SNDBUFS  SNDPEND  RCVPEND
 UDP   [ 0] [         <IP_ADDRESS>: 54321] -> [    <IP_ADDRESS>:   443]:    16384    16384        0        0
 UDP   [ 1] [         <IP_ADDRESS>: 21355] -> [  <IP_ADDRESS>:  6666]:    16384    16384        0        0
 UDP   [ 2] [         <IP_ADDRESS>: 10010] -> [         <IP_ADDRESS>:     0]:    16384    16384        0        0
 UDP   [ 3] [         <IP_ADDRESS>: 21356] -> [   <IP_ADDRESS>: 29443]:   262144   262144        0        0
 UDP   [ 4] [         <IP_ADDRESS>: 21357] -> [ ***************: 10010]:    16384    16384        0        0
 UDP   [ 5] [         <IP_ADDRESS>: 21340] -> [   <IP_ADDRESS>: 29443]:    16384    16384        0        0
 UDP   [ 6] [         <IP_ADDRESS>: 21341] -> [ ***************: 10010]:    16384    16384        0        0
 UDP   [ 7] [         <IP_ADDRESS>: 21345] -> [  <IP_ADDRESS>: 29443]:    16384    16384        0        0
 UDP   [ 8] [         <IP_ADDRESS>: 21365] -> [ ***************:  6432]:    16384    16384        0        0
 UDP   [ 9] [         <IP_ADDRESS>: 21377] -> [  <IP_ADDRESS>: 29443]:   262144   262144        0        0
 UDP   [10] [         <IP_ADDRESS>: 21378] -> [ ***************:  7981]:    16384    16384        0        0

How about adding an dynamic enable option? If dynamic allocate is enabled on the basis of the pre-allocation pool, then we will allocate new connection instances from the heap. Of course, we will also add the maximum limit config to protect the system from malicious attacks.
CONFIG_NET_DYNAMIC_CONNS CONFIG_NET_DYNAMIC_CONNS_PER_ALLOC CONFIG_NET_MAX_DYNAMIC_CONNS

Yes, seams a good approach!

Update the request,  add new config about connec dynamic allocate:
CONFIG_NET_ALLOC_CONNS
if CONFIG_NET_ALLOC_CONNS is enabled, the static pre-applied connection entries will be disabled,
all connections will be dynamically allocated from heap. about the maximum number of connections,
we prepare implement the limitation from the VFS layer:
_POSIX_OPEN_MAX
RLIMIT_NOFILE

@acassis do you think the new implementation is good to merge?

@anchao please make the similar change to other implementation

@anchao please make the similar change to other implementation


What is the resource naming rules for Azure Confidential Ledger?

Can you please add the naming rules for Azure Confidential Ledger?

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

ID: 374ec8eb-64d4-3766-5c5e-39137a262ffd
Version Independent ID: 3abeeae9-6854-651a-483c-a1673eea9f9f
Content: Resource naming restrictions - Azure Resource Manager
Content Source: articles/azure-resource-manager/management/resource-name-rules.md
Service: azure-resource-manager
Sub-service: management
GitHub Login: @tfitzmac
Microsoft Alias: tomfitz

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.


feat(deps): upgrade runtime dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-runtime-dependencies-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1365

Questions ?
Please refer to the Backport tool documentation


Can't visit pages

I use "npm install" to install it,But I can't load the webpages...
Console:
><EMAIL_ADDRESS>start /usr/local/src/bStats
> node ./bin/start.js

Master 21278 is running
Worker 21284 started
Worker 21289 started
Worker 21292 started
Worker 21290 started
GET /login - - ms - -
GET /sitemap.xml 304 26.505 ms - -

To run bStats locally, you just also

Setup a redis cluster
Update the config.js file (see https://github.com/Bastian/bStats/blob/master/config.json(
Run redisPopulator.js once (see https://github.com/Bastian/bStats/blob/master/redisPopulator.js)


Incorrect command

The command is incorrect in Example 1. Should be Grant-CsTeamsMobilityPolicy

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

ID: bb79bedc-145d-7f61-8973-7e9d0aeaf553
Version Independent ID: f7f4f158-fe61-ccfe-34fb-2e2628b982e2
Content: Grant-CsTeamsMobilityPolicy (skype)
Content Source: skype/skype-ps/skype/Grant-CsTeamsMobilityPolicy.md
Service: skypeforbusiness-powershell
GitHub Login: @saragava
Microsoft Alias: saragava

@officedocsbot assign @yogkumgit

@dariomws  Thank you very much for the contribution and updating the documentation with PR. @matambanadzo Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Port new LH2 driver to the nRF53

The LH2 driver depends heavily on the PPI system. which is different in the nRF52 vs. nRF53.
The current driver implementation only works for the nRF52.
It needs to be ported to work on nRF53 platform

Merged into #268
Fixed by #273


Reduce size of binary packages

The size of the nanopb binary packages could be reduced by a bit by using PyInstaller's multipackage feature, instead of separately generating each .exe:
https://pyinstaller.readthedocs.io/en/v3.3.1/spec-files.html#multipackage-bundles

A pyinstaller update in 2022 had the equivalent effect.


Suggestion: unique desktop interface

If you wish, I could give some mockups of what I believe to be a more unique desktop interface.  As it stands, it looks WAY too much like macOS, and not enough like something new.
I actually enjoy the top bar, but the bottom shouldn't be a dock, you're just wasting space that could have other utility.

Hello @roracle, thanks for reaching out.
It is explicitly not an objective of helloSystem to look like macOS or "modern" (as in: like iOS or Android), but it is an objective to feel Mac-like and to look slick but not distracting.
Our starting point are the concepts behind the early GUIs of the 80s.
Please check out the following resources prior to starting any work:

Apple Computer, Inc., 1992, Macintosh Human Interface Guidelines, First Printing, November 1992. Addison-Wesley Publishing Company. ISBN 0-201-62216-5

Quote:

If you are a designer, a human interface professional, or an engineer, this book contains information you can use to design and create products that fit the Macintosh model. It provides background information that can help you plan and make decisions about your product design. Even if you don’t design and develop products for the Macintosh, reading this book will help you to understand the Macintosh interface.

https://github.com/probonopd/hello/wiki (also the links at the right-hand side)
My six-part series on #LinuxUsability
The desktop metaphor must be saved article
We'd welcome thoughts and scribbles/mockups of UX ideas. The chance that they will be considered for inclusion in helloSystem increases if they reflect the above. Indeed it would be welcome if our system could get a more distincive look, while still maintaining (or taking to the next level) the spirit of the early GUIs of the 80s and the look of (toned-down) mid-00s skeuomorphism (for example, a button should look like a button and not just be some text which may or may not be clickable).

In case you want to experiment with the style sheet, it can be edited and tested at runtime (just launch a new application and it will take effect): /usr/local/etc/xdg/stylesheet.qss.

Awesome! We're dealing with weather and power outages as it were, but I'll check all that out when the local infrastructure is stable again.


get_modflow() issues in the tests

https://github.com/pypest/pypestutils/actions/runs/11140750010
We are failing lots of tests (on pyemu and pestpp also) related to this issue.  @mwtoews is there a quick work around we can use to patch?

This is fixed via https://github.com/modflowpy/flopy/pull/2320, so perhaps a band-aid fix until the next flopy release is to depend on the latest develop branch?

Didn't realize this had already been addressed.  Thanks @mwtoews

A latest flopy with a fix was just released.


[DNM] Added full integer quantization support for TFLM magic_wand on zephyr_riscv

This pull request adds support to run integer quantized model of TFLM magic_wand on zephyr_riscv.

Added code in magic_wand/train/train.py to support int8 quantized model (use argument --fully-quantized)
Added code in magic_wand/train/train_magic_wand_model.ipynb to reflect the change in magic_wand/train/train.py
Added int8 quantized model data in magic_wand/magic_wand_model_data.cc (uncomment the line // #define USE_INT8_QUANTIZED to use int8 quantized model)

The following changes ONLY applies to zephyr_riscv (magic_wand/zephyr_riscv/src)

Modified magic_wand/zephyr_riscv/Makefile.inc to use platform specific main_functions.cc and .h on zephyr_riscv
Added missing ops in main_functions.cc (DEQUANTIZE, QUANTIZE, and RESHAPE) for support of int8 quantized model
Added inline assembly in main_functions.cc to measure elapsed CPU cycle counts (NOT actual time due to hardware limitation, the clock speed is fixed at 100 MHz) while running main functions (uncomment the line // #define ZEPHYR_RISCV_PROFILE to enable it)

The above changes related to zephyr_riscv are both tested on Xilinx Arty A7-35T programmed with Litex/VexRiscv SoC that runs Zephyr RISC-V and simulated on Renode with the Renode scripts (*.resc) provided by Antmicro, see antmicro/litex-vexriscv-tensorflow-lite-demo for more details.
The following table shows the number of CPU (100 MHz) cycles for each main function to run on both Xilinx Arty A7 and Renode

Before Invoke()
Invoke()
PredictGesture()
HandleOutput()

float32 (Arty A7)
275M
18.5M
8k
350

float32 (Renode)
N/A
10M
1.5k
10

int8 (Arty A7)
275M
5.6M
8k
350

int8 (Renode)
N/A
3M
1.8k
10

Note

Cycle counts are averaged and rounded for clarity
Before Invoke(): The time to collect enough data for inference, N/A for Renode because the data is fed from a file, not determined by the actual sensor.
Actual speed may be faster because printing out messages adds overhead to the system (#define ZEPHYR_RISCV_PROFILE is uncommented in the experiment)

Noting that this PR is not going to be merged since we are not currently able to accept changes to the examples.

Noting that this PR is not going to be merged since we are not currently able to accept changes to the examples.

Agree, thanks for coming back to this PR @advaitjain


Allow deny votes

#8

[x] Rejection at 3 votes
[x] Contested (those having both an accept or rejection) submissions must be resolved by a Shiny Verifier
[x] Add points for denied posts

Oops, test amounts as I only have 2 accounts to test with lol
Updated


Unexpected keyword argument 'header' with websocket-client v0.36.0

websocket-client version 0.36.0 was released two days ago and is automatically installed through pip.
When running the bot one is greeted with the following error:
Traceback (most recent call last):
  File "./run.py", line 5, in <module>
    Bot().run()
  File "/home/user/.local/lib/python3.5/site-packages/mattermost_bot/bot.py", line 36, in run
    self._dispatcher.loop()
  File "/home/user/.local/lib/python3.5/site-packages/mattermost_bot/dispatcher.py", line 103, in loop
    for self.event in self._client.messages(True, 'posted'):
  File "/home/user/.local/lib/python3.5/site-packages/mattermost_bot/mattermost.py", line 135, in messages
    if not self.connect_websocket():
  File "/home/user/.local/lib/python3.5/site-packages/mattermost_bot/mattermost.py", line 130, in connect_websocket
    "Cookie: MMTOKEN=%s" % self.api.token,
  File "/home/user/.local/lib/python3.5/site-packages/websocket/_core.py", line 487, in create_connection
    skip_utf8_validation=skip_utf8_validation, **options)
TypeError: __init__() got an unexpected keyword argument 'header'

A downgrade to websocket-client==0.34.0 fixes the issue.

Hi. Bug was fixed on websocket-client==0.37.0

I guess it can be closed then.


nosum function: is able to add more levels of heading

as title. thanks

Sorry I am not sure what you mean by more levels of heading?

From: myjeshurun @.>
Sent: Tuesday, April 4, 2023 2:57 PM
To: hkgnp/logseq-tablerender-plugin @.>
Cc: Subscribed @.***>
Subject: [hkgnp/logseq-tablerender-plugin] nosum function: is able to add more levels of heading (Issue #13)
as title. thanks
—
Reply to this email directly, view it on GitHubhttps://github.com/hkgnp/logseq-tablerender-plugin/issues/13, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALNXKGOFZBPJFSWQQY23J6TW7PA4HANCNFSM6AAAAAAWSIU3SY.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

I mean, while on the mode of nosum, I can only have two columns to show .
Could it be three or more columns?
Blessings in Christ,
Jeshurun
我的仆人雅各，我所拣选的耶书崙哪，不要害怕！
Don’t be afraid, Jacob my servant; and you, Jeshurun, whom I have chosen.
On Tue, Apr 4, 2023 at 2:58 PM hkgnp @.***> wrote:

Sorry I am not sure what you mean by more levels of heading?

From: myjeshurun @.>
Sent: Tuesday, April 4, 2023 2:57 PM
To: hkgnp/logseq-tablerender-plugin @.>
Cc: Subscribed @.***>
Subject: [hkgnp/logseq-tablerender-plugin] nosum function: is able to add
more levels of heading (Issue #13)
as title. thanks
—
Reply to this email directly, view it on GitHub<
https://github.com/hkgnp/logseq-tablerender-plugin/issues/13>, or
unsubscribe<
https://github.com/notifications/unsubscribe-auth/ALNXKGOFZBPJFSWQQY23J6TW7PA4HANCNFSM6AAAAAAWSIU3SY

.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
https://github.com/hkgnp/logseq-tablerender-plugin/issues/13#issuecomment-1495447307,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFLVZXCEZ7YQMYRJ3AOHE5DW7PBCZANCNFSM6AAAAAAWSIU3SY
.
You are receiving this because you authored the thread.Message ID:
@.***>

Oh sure. Just nest them. Do you have a rough sample that I can draft out for you?
Get Outlook for iOShttps://aka.ms/o0ukef

From: myjeshurun @.>
Sent: Wednesday, April 5, 2023 9:36:11 PM
To: hkgnp/logseq-tablerender-plugin @.>
Cc: Benjamin Png @.>; Comment @.>
Subject: Re: [hkgnp/logseq-tablerender-plugin] nosum function: is able to add more levels of heading (Issue #13)
I mean, while on the mode of nosum, I can only have two columns to show .
Could it be three or more columns?
Blessings in Christ,
Jeshurun
我的仆人雅各，我所拣选的耶书崙哪，不要害怕！
Don’t be afraid, Jacob my servant; and you, Jeshurun, whom I have chosen.
On Tue, Apr 4, 2023 at 2:58 PM hkgnp @.***> wrote:

Sorry I am not sure what you mean by more levels of heading?

From: myjeshurun @.>
Sent: Tuesday, April 4, 2023 2:57 PM
To: hkgnp/logseq-tablerender-plugin @.>
Cc: Subscribed @.***>
Subject: [hkgnp/logseq-tablerender-plugin] nosum function: is able to add
more levels of heading (Issue #13)
as title. thanks
—
Reply to this email directly, view it on GitHub<
https://github.com/hkgnp/logseq-tablerender-plugin/issues/13>, or
unsubscribe<
https://github.com/notifications/unsubscribe-auth/ALNXKGOFZBPJFSWQQY23J6TW7PA4HANCNFSM6AAAAAAWSIU3SY

.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
https://github.com/hkgnp/logseq-tablerender-plugin/issues/13#issuecomment-1495447307,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFLVZXCEZ7YQMYRJ3AOHE5DW7PBCZANCNFSM6AAAAAAWSIU3SY
.
You are receiving this because you authored the thread.Message ID:
@.***>

—
Reply to this email directly, view it on GitHubhttps://github.com/hkgnp/logseq-tablerender-plugin/issues/13#issuecomment-1497499578, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALNXKGOH3ELMI6LAW3RSSHLW7VYMXANCNFSM6AAAAAAWSIU3SY.
You are receiving this because you commented.Message ID: @.***>


Put Stagger inside Stagger cause warning

I want to make inception animation, but there's a warning like this:

Did you have any suggestion?

Hmm, thanks for finding this. If I copy the source code into another project it doesn't have this error, so it must be something with my webpack build.
I'll try to look into it.

Any updates @natenorberg ? :)

I think my commit fixed the issue, but it broke the tests. As soon as I can get that resolved I'll bump the version.

Alright. Should be fixed in version 0.0.4
Thanks for finding that

Stil the same :neutral_face:


Istio sidecar injection - workload deployment failed with error in sidecar injector

What kind of request is this (question/bug/enhancement/feature request):
Bug
Istio Version: 1.5.901
Steps to reproduce (least amount of steps as possible):

Spin up a rancher 2.4-head[e0e2866e7]
Add a cluster with 2 worker nodes and 1 etcd, 1 control plane
Enable monitoring and istio
Create a namespace with istio side-car injection enabled
Deploy a workload in the above namespace
The deployment fails with the error :

2021-01-20T20:16:08.176482Z	error	Injection data: err=failed parsing generated injected YAML (check Istio sidecar injector configuration): error converting YAML to JSON: yaml: line 160: did not find expected key spec=
**Result:**

Other details that may be helpful:
Istio side car injector pod logs has the following error:
2021-01-20T21:34:39.032436Z	info	AdmissionReview for Kind=/v1, Kind=Pod Namespace=anupama-istio-ns Name= (anupama-istio-wk-6f4f6c95fb-***** (actual name not yet known)) UID=8ef6fa83-c9b3-43d4-ba4e-e8e7b3fb9b9b Rfc6902PatchOperation=CREATE UserInfo={system:serviceaccount:kube-system:replicaset-controller 1045e5ca-031e-4b1c-b4ef-4b3d98115407 [system:serviceaccounts system:serviceaccounts:kube-system system:authenticated] map[]}
2021-01-20T21:34:39.044493Z	warn	Failed to unmarshal template error converting YAML to JSON: yaml: line 160: did not find expected key rewriteAppHTTPProbe: true

Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI):

Rancher | 2.4-head[e0e2866e7]
User Interface | v2.4-dev
Helm | v2.16.8-rancher1
Machine | v0.15.0-rancher49

Installation option (single install/HA): Single

The issue is not seen on v2.4.12, followed same steps as above.
Rancher version v2.4.12 (f65114dc6), Istio version: 1.5.900
Spin up a rancher 2.4-head[e0e2866]
Add a cluster with 2 worker nodes and 1 etcd, 1 control plane
Enable monitoring and istio
Create a namespace with istio side-car injection enabled
Deploy a workload in the above namespace

The issue is not seen on v2.4.12, followed same steps as above.
Rancher version v2.4.12 (f65114dc6), Istio version: 1.5.900
Spin up a rancher 2.4-head[e0e2866]
Add a cluster with 2 worker nodes and 1 etcd, 1 control plane
Enable monitoring and istio
Create a namespace with istio side-car injection enabled
Deploy a workload in the above namespace

I see the same error happen on v2.5-head commit: 23a29c3

Error creating: Internal error occurred: failed calling webhook "sidecar-injector.istio.io": Post "https://istio-sidecar-injector.istio-system.svc:443/inject?timeout=30s": context deadline exceeded

I see the same error happen on v2.5-head commit: 23a29c3

Error creating: Internal error occurred: failed calling webhook "sidecar-injector.istio.io": Post "https://istio-sidecar-injector.istio-system.svc:443/inject?timeout=30s": context deadline exceeded

https://github.com/rancher/system-charts/pull/401

https://github.com/rancher/system-charts/pull/401

Verified the issue on 2.4-head[4c214400c]
Istio [1.5.901]
Steps performed:
Create a cluster as a standard user with 1 control plane, 2 worker nodes and 1 etcd
From the tools of the cluster [v1 charts] enable monitoring and enable istio [1.5.901]
once all the namespaces come active, create a namespace with istio-sidecar injection enabled in the namespace
Deploy a workload in this namespace
Workloads came active without the issue mentioned above

Verified the issue on 2.4-head[4c214400c]
Istio [1.5.901]
Steps performed:
Create a cluster as a standard user with 1 control plane, 2 worker nodes and 1 etcd
From the tools of the cluster [v1 charts] enable monitoring and enable istio [1.5.901]
once all the namespaces come active, create a namespace with istio-sidecar injection enabled in the namespace
Deploy a workload in this namespace
Workloads came active without the issue mentioned above


make vscode-python specific

taking the label actions from the vscode repo but making them more python specific

ok went through and make those edits except for that one link that @cwebster-99 was asking about. Let me know what people think - thanks!


Keep player position when toggle switch on/off

I'm not sure if this is by design or not. But I wanted the Sonos player toggle between play and pause instead of play and stop when using the switch in the Home app. So I can resume the track where i was when i turned the switch off.

Thanks, Jonas, @himynameisjonas
Actually it's more by accident than by design.  I implemented stop, it seemed to work and I never looked at it.  I didn't even realise there was a pause command.
@leoneleone

Personally, I prefer turning a Sonos Speaker (HomeKit Switch- Characteristic.On) using Siri Commands and have that "Stop" rather than "Pause" the Sonos Speaker.

Why your preference for stop instead of pause?
I tested pause while playing Line-In, TuneIn Radio, TV, and Sonos Library Songs.  The first two don't support pause and it seems to do exactly the same as stop: it changes the TransportState in the AVTransport service to STOPPED.  For TV pause results in the same HTTP 500 response code as stop.  For library songs, pause changes TransportState to PAUSED_PLAYBACK.  The ZonePlayer actually closes its network connection to the music library server, just as on stop.  On a subsequent play, playback resumes immediately, but it takes a while (until the next song is played?) before the network connection is re-established.  On play after stop, the network connection is re-established immediately.  It looks like pause causes the ZonePlayer to retain the playback buffer in memory (with the current playback position).  Other than that, pause doesn't seem to consume more resources than stop.

@ebaauw
I could be wrong, but I believe Pause does not turn the Sonos speaker/room "off". I can still hear the electronic hum of the speakers being "on".
With Stop, the hum subsides. My preference is for Stop because of this reason.
Again, I'm not entirely sure. I'll double check once I'm back home.

@leoneleone if that's the case, how do you turn it off using the Sonos app on iOS? I can only find a pause button in the app.

Just published v0.1.6 which includes this pull request.
@leoneleone please check if this works for you.  Worst case, I could add a config.json parameter to choose between pause and stop.


Allow running IsCrawler concurrently

This should allow us to run IsCrawler concurrenly from multiple goroutines, improving performance.
From https://pkg.go.dev/regexp#Regexp:

A Regexp is safe for concurrent use by multiple goroutines, except for configuration methods, such as Longest.

Thanks for your contribution 👍


Update dependency aar to release 10.2.8

Update to the next patch release of 10.2.8 when released.

Verified on master


Add database support

Added database support! Yay!
I was the one to make the new variable system in Skript, so I have extensive experience with how variables are handled and saved.
That knowledge helped me make this pull request.
This pull request keeps support for extensibility of projects using skript-parser. Like my project Scroll.
Example of what I mean is the usage of including SkriptLogger in important potential user written configurations errors.
Required changes:

I choose GSON for the serialization system. Let me know everyone's opinion. Had to gradle shadow library.
Removed clearVariables method in Variables because that's a security risk allowing static access to clear the entire variables cache.
Option node system could be changed or improved? The current OptionLoader class is locked down to SectionConfiguration, so I can't utilize it as FileSection is unrelated to SectionConfiguration, and no parser reference. So I did split parsing inside FileSection with FileSection#get

I don't know why the tests are failing. I don't believe it's related to this pull request. Tests were successful on my system.

Very nice changes! Thanks for the contribution.
Can you please elaborate more on your problem with FileSection/OptionLoader? I have not had the time to properly review your code, but it seems strange to use these two combined in a situation they were not designed for?

Skript uses it's own built in system for reading the config.sk configuration file. skript-parser does not have a fully fledged configuration system, so i'm make-shifting the FileSection and FileElement system to allow for this usage.
I think it works as it stands, but essentially being able to parse a String list as a FileSection that can get nodes that are FileElements. I did that sorta in this pull request, but it's not built for that, which is why I added that statement.


feat(footer): laying down the basework for the footer

Starts digital-design/#1080
This pull request basically initializes the footer component. Since this is my first, please take a look and make sure I did it right before I get too far along. I used the masthead component as a starting place.
Changelog
New

initializes new footer component

@photodow you can set this as a draft pull request for now if this isn't ready to be merged, but thank you for setting this up early.


Mwpw 119277 New create page marquee

Please always provide the JIRA issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fix mwpw 119277
Test URLs:

Before: https://main--express-website--adobe.hlx.page/express/create/flyer
After: https://mwpw-119277--express-website--webistry-development.hlx.page/drafts/qiyundai/create/flyer?lighthouse=on

@qiyundai i think this change is big enough to be its own dedicated marquee block, rather than adding more complexity to the columns block, and add it to the lcpBlocks.

@qiyundai two small things:

can you add this new block to lcpBlocks? I think by design this will always be the LCP
there's a linting error


Revert "Revert "Update package.json""

Reverts mjkoster/node-red-contrib-discrete-fsm#2

Reverted revert because the node-red version is on the NPM download (?)


Remove cranelift-codegen's build.rs

We should check in all generated code, since it doesn't change based on any user of cranelift-codegen's input or system or anything like that, and have a script that we can re-run as needed to regenerate these files. This will speed up compile times and remove cargo build time dependencies.
See also this thread https://github.com/bytecodealliance/wasmtime/pull/3506#discussion_r743045020

As noted in #3540, possibly a good way to go about this would be to maintain a small build.rs that just does a check for stale sources by comparing the meta-sources against a manifest, as #3534 does for ISLE. I think we should try to protect against this otherwise somewhat probable silent failure for new contributors; hopefully a build.rs that just uses sha2 and nothing else is relatively fast to compile :-)

Given the experience from https://github.com/bytecodealliance/wasmtime/issues/4066 it seems we're pretty unlikely to reverse direction at this point, so I'm going to close.