seaweedfs: 3.15 -> 3.20

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/chrislusf/seaweedfs/releases.
meta.description for seaweedfs is: "Simple and highly scalable distributed file system"
meta.homepage for seaweedfs is: "https://github.com/chrislusf/seaweedfs"
meta.changelog for seaweedfs is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.18 with grep in /nix/store/bisz6y5icc1cav6fqxdlfmd6f98mqqj6-seaweedfs-3.18
found 3.18 in filename of file in /nix/store/bisz6y5icc1cav6fqxdlfmd6f98mqqj6-seaweedfs-3.18

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
seaweedfs

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/bisz6y5icc1cav6fqxdlfmd6f98mqqj6-seaweedfs-3.18 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A seaweedfs https://github.com/r-ryantm/nixpkgs/archive/4741735667c65da79c0d285aa94d65e73a3e0853.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/bisz6y5icc1cav6fqxdlfmd6f98mqqj6-seaweedfs-3.18
ls -la /nix/store/bisz6y5icc1cav6fqxdlfmd6f98mqqj6-seaweedfs-3.18/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

seaweedfs

Maintainer pings
cc @cmacrae @raboof for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/chrislusf/seaweedfs/releases.
meta.description for seaweedfs is: "Simple and highly scalable distributed file system"
meta.homepage for seaweedfs is: "https://github.com/chrislusf/seaweedfs"
meta.changelog for seaweedfs is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.20 with grep in /nix/store/8699hpqb9l21dcndhwrn4s1vw5i7fv6c-seaweedfs-3.20
found 3.20 in filename of file in /nix/store/8699hpqb9l21dcndhwrn4s1vw5i7fv6c-seaweedfs-3.20

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
seaweedfs

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/8699hpqb9l21dcndhwrn4s1vw5i7fv6c-seaweedfs-3.20 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A seaweedfs https://github.com/r-ryantm/nixpkgs/archive/96924e41ca34910aa4fcc9efa781d6be99ab673f.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/8699hpqb9l21dcndhwrn4s1vw5i7fv6c-seaweedfs-3.20
ls -la /nix/store/8699hpqb9l21dcndhwrn4s1vw5i7fv6c-seaweedfs-3.20/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

seaweedfs

Maintainer pings
cc @cmacrae for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/chrislusf/seaweedfs/releases.
meta.description for seaweedfs is: "Simple and highly scalable distributed file system"
meta.homepage for seaweedfs is: "https://github.com/chrislusf/seaweedfs"
meta.changelog for seaweedfs is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.21 with grep in /nix/store/2s7iaa166jx7dh6qn6rhzf705prfarmf-seaweedfs-3.21
found 3.21 in filename of file in /nix/store/2s7iaa166jx7dh6qn6rhzf705prfarmf-seaweedfs-3.21

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
seaweedfs

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/2s7iaa166jx7dh6qn6rhzf705prfarmf-seaweedfs-3.21 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A seaweedfs https://github.com/r-ryantm/nixpkgs/archive/df30de4c69e3d22fd2fbad17203e2a26c615565d.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/2s7iaa166jx7dh6qn6rhzf705prfarmf-seaweedfs-3.21
ls -la /nix/store/2s7iaa166jx7dh6qn6rhzf705prfarmf-seaweedfs-3.21/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

seaweedfs

Maintainer pings
cc @cmacrae for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/chrislusf/seaweedfs/releases.
meta.description for seaweedfs is: "Simple and highly scalable distributed file system"
meta.homepage for seaweedfs is: "https://github.com/chrislusf/seaweedfs"
meta.changelog for seaweedfs is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.22 with grep in /nix/store/iy0sf7avg91ih8yclbch7j7a62vlahzg-seaweedfs-3.22
found 3.22 in filename of file in /nix/store/iy0sf7avg91ih8yclbch7j7a62vlahzg-seaweedfs-3.22

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
seaweedfs

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/iy0sf7avg91ih8yclbch7j7a62vlahzg-seaweedfs-3.22 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A seaweedfs https://github.com/r-ryantm/nixpkgs/archive/c85013f9b245b28ddabafce5b4d65963d109b90a.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/iy0sf7avg91ih8yclbch7j7a62vlahzg-seaweedfs-3.22
ls -la /nix/store/iy0sf7avg91ih8yclbch7j7a62vlahzg-seaweedfs-3.22/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

seaweedfs

Maintainer pings
cc @cmacrae for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/chrislusf/seaweedfs/releases.
meta.description for seaweedfs is: "Simple and highly scalable distributed file system"
meta.homepage for seaweedfs is: "https://github.com/chrislusf/seaweedfs"
meta.changelog for seaweedfs is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.23 with grep in /nix/store/7brzxqwxbgc2fy96jpz5k5fm6vmp15v8-seaweedfs-3.23
found 3.23 in filename of file in /nix/store/7brzxqwxbgc2fy96jpz5k5fm6vmp15v8-seaweedfs-3.23

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
seaweedfs

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/7brzxqwxbgc2fy96jpz5k5fm6vmp15v8-seaweedfs-3.23 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A seaweedfs https://github.com/r-ryantm/nixpkgs/archive/1cab5667d507751583dcc43379867b521eba5a74.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/7brzxqwxbgc2fy96jpz5k5fm6vmp15v8-seaweedfs-3.23
ls -la /nix/store/7brzxqwxbgc2fy96jpz5k5fm6vmp15v8-seaweedfs-3.23/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

seaweedfs

Maintainer pings
cc @cmacrae for testing.

Result of nixpkgs-review pr 183839 run on x86_64-linux 1

1 package built:

seaweedfs


Docs are now incorrect after renaming

On the README:
import Engine

let response = try HTTPClient<TCPClientStream>.get("http://pokeapi.co/api/v2/pokemon/")
print(response)

In the example:
import HTTP
import Transport

let response = try Client<TCPClientStream>.get("http://pokeapi.co/api/v2/pokemon/")
print(response)

Nice catch! I'll update that now.

Done.


Refactoring

TODO:

[x] Refactoring IPC
[x] Refactoring client
[x] Edit example
[x] Parse response
[x] Make go-lint 100%
[ ] Write some tests
[ ] Add CI

While we're doing that I'd also include a point to make go-lint 100%, it would mean comment every exported function/struct etc.

While we're doing that I'd also include a point to make go-lint 100%, it would mean comment every exported function/struct etc.

I think this is a good idea.

@hugolgst hi, can you check this PR?
Also I can maintain this library. I see that many forks with good additions and it will be cool to collect ideas from them and push into origin library

sure. sorry i have been quite busy with other projects

i don't have time right now to test it how could we check that together? i don't have any tests in place unfortunately

Yes, I check my PR and other forks today. Also I think that I can write some tests in next PR

I looked at the new versions of the discord API. They have callbacks from the client and it takes a lot of time to design a new version of the library. So I'll probably continue my experiments in another repository, as it's quite a lot of work.


[github_releases] Use tag name instead of release name

It is usually simpler to parse, align with the gitmethod, and gives better results by default.

Tested manually, merging.


Implement Stomping Tantrum

(and Happy Hour, for those counting at home)

Can you rebase this?

I guess still no one has answers about how the mechanic actually works ingame... :/

turn 1: move failed
turn 2: Instructed/Dancered/MC/MB move succeeded
turn 2: ST double or not?
turn 1: move succeeded
turn 2: Instructed/Dancered/MC/MB move failed
turn 2: ST double or not?
This is really the main question here.

The end of this post answers the first question: http://www.smogon.com/forums/threads/ultra-sun-ultra-moon-battle-mechanics-research-read-post-2.3620030/page-6#post-7600785

(It’s doubled)

And actually, I believe the one I linked before (http://www.smogon.com/forums/threads/ultra-sun-ultra-moon-battle-mechanics-research-read-post-2.3620030/page-5#post-7589613) answers the second one:
Turn 1: Fake Out succeeds
Turn 2: Instructed Fake Out fails
Turn 2: Stomping Tantrum is not boosted

So it looks like: If the last move used on the last turn (including reused moves including Instruct, Dancer, and called moves including Magic Bounce and Sleep Talk) failed, Stomping Tantrum will double.
This generally involves multiple state, but it's possible to make it not: have a single lastMoveResult, but do not overwrite it if there's a pending move action.
One possible way to check this:

Turn 2: failed Fake Out
Turn 3: doubled Stomping Tantrum
Instructed Stomping Tantrum: does it still double?

I do think it's keeping multiple turns of state, but I don't understand why Game Freak would program it that way.

Zarel that’s the exact scenario described in the most recent post, and stomping tantrum is doubled both times

I may as well make you rewrite the test to match the new test API.

They might not actually be storing anything extra at all if they implemented it by just reading the battle log.

They don't store a battle log...

I wrote a Dex article so I'd have something to refer to the next time I needed a list of the different ways you could use multiple moves in a turn:
https://dex.pokemonshowdown.com/articles/submoves

They must store something for battle videos, which is what I meant to refer to by "battle log."

For battle videos, they store the initial seed and a list of decisions. Results definitely are not stored at all.

Should I update simulator-doc.txt to show where move results get stored?

Oh, right, something I forgot to ask about: should a sleep move that fails because of the Sleep Clause boost Stomping Tantrum? No, right?

...sure. :/

Can you just return null from recharging, charge turns, etc for now? I'd rather have Stomping Tantrum be wrong in those cases, than to have recharging fully not work at all. We can work on fixing that mechanic later.

You could also I think just set move success to true while returning null. That's probably the actual correct solution here.

Yeah I was trying to avoid that, but since there's no real easier way
to do it for protect moves, I guess there's at least a precedent.
On Thu, Dec 7, 2017 at 2:20 PM, Guangcong Luo<EMAIL_ADDRESS>wrote:

You could also I think just set move success to true while returning null.
That's probably the actual correct solution here.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I don't need to, since Stomping Tantrum specifically checks for a value of
false, not null.
On Thu, Dec 7, 2017 at 3:43 PM, Guangcong Luo<EMAIL_ADDRESS>wrote:

@Zarel commented on this pull request.
In data/statuses.js
https://github.com/Zarel/Pokemon-Showdown/pull/4175#discussion_r155649577
:

@@ -321,7 +321,7 @@ exports.BattleStatuses = {
onBeforeMove: function (pokemon) {
this.add('cant', pokemon, 'recharge');
pokemon.removeVolatile('mustrecharge');

	return false;

	return null;

Should you also set this.moveThisTurnResult = true; somewhere?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Zarel/Pokemon-Showdown/pull/4175#pullrequestreview-82004102,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AULj4LV2OqO90w1OsU-P-A5cE0WeZhIGks5s-FvvgaJpZM4QpMBa
.

If you need, I can write a test for it in a couple hours.

Sure.

There are a lot of return-null situations where Stomping Tantrum should treat as false. For instance, Wonder Guard, or Levitate.

Oh, that’s where things get a little hairy. You see, the only time the actual return value of an event gets stored as the move result is in onBeforeMove. Everything else gets sanitized into false by useMoveInner(), because in that context null means “it failed, but don’t send the normal failure message because the effect already made its own.”
Sent from my iPhone

On Dec 7, 2017, at 4:18 PM, Guangcong Luo<EMAIL_ADDRESS>wrote:
There are a lot of return-null situations where Stomping Tantrum should treat as false. For instance, Wonder Guard, or Levitate.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

...that's what null means everywhere.
I'll accept that it means something different here, but that should probably receive special treatment or be documented somewhere. But oh well, if that's the case, then this code is ready for merge.
Make a new pull request for your test.

Thanks for working with me on this!

It is documented in runMove


Cannot use for zabbix agent version for 3.0 or less than that.

#rpm -ivh zabbix-module-systemd-1.2.0-1.x86_64.rpm
error: Failed dependencies:
zabbix-agent >= 3.2.0 is needed by zabbix-module-systemd-1.2.0-1.x86_64

You can compile this module to work with any version of Zabbix.
Currently, there is no plan to provide RPM packages for older versions of Zabbix. This requires a huge amount of effort :(


T and L-Lap joints and Show_topology_GH_component

Added ShowTopologyTypes GH component
Added L-Butt Joint including GH Component
Added T-Butt Joint including GH Component
added topologies attribute to TimberAssembly to avoid recalculation
What type of change is this?

[ ] Bug fix in a backwards-compatible manner.
[x] New feature in a backwards-compatible manner.
[ ] Breaking change: bug fix or new feature that involve incompatible API changes.
[ ] Other (e.g. doc update, configuration, etc)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I added a line to the CHANGELOG.md file in the Unreleased section under the most fitting heading (e.g. Added, Changed, Removed).
[x] I ran all tests on my computer and it's all green (i.e. invoke test).
[x] I ran lint on my computer and there are no errors (i.e. invoke lint).
[ ] I added new functions/classes and made them available on a second-level import, e.g. compas_timber.datastructures.Beam.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] I have added necessary documentation (if appropriate)

@obucklin please merge latest main onto this branch as this still shows changes from already merged PR

done
On Thu, Jan 25, 2024 at 11:56 AM Chen Kasirer @.***>
wrote:

@obucklin https://github.com/obucklin please merge latest main onto
this branch as this still shows changes from already merged PR
—
Reply to this email directly, view it on GitHub
https://github.com/gramaziokohler/compas_timber/pull/177#issuecomment-1909915814,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANHAUGQQRG5HSXVBNX4LY3LYQI26BAVCNFSM6AAAAABCFUWGOGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBZHEYTKOBRGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

done
…
On Thu, Jan 25, 2024 at 11:56 AM Chen Kasirer @.> wrote: @obucklin https://github.com/obucklin please merge latest main onto this branch as this still shows changes from already merged PR — Reply to this email directly, view it on GitHub <#177 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANHAUGQQRG5HSXVBNX4LY3LYQI26BAVCNFSM6AAAAABCFUWGOGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBZHEYTKOBRGQ . You are receiving this because you were mentioned.Message ID: @.>

Thanks, will review by end of today.


Run standard on npm test

Standard suffers from https://github.com/feross/standard/issues/21.

I'm not sure if that is the reason or not, but anyway, it doesn't seem to finish so it is hard to use like standard && something.


heap-use-after-free in Imf_2_5::DeepScanLineInputFile::DeepScanLineInputFile

Hi ,there is a heap UAF in DeepScanLineInputFile by Fuzzing with exrmakepreview, This issue should be reproducible with the exrmakepreview binary(with or without ASAN) as follows:
CFLAGS="-fsanitize=address" CXXFLAGS="-fsanitize=address" LDFLAGS="-fsanitize=address" cmake ..
Thanks.
arnow117 with AntFuzz,
Ant-financial Light-Year Security Lab.
t.exr.zip

The should be fixed by #730.