Before and after screenshots added to UG

Added before/after screenshots to UG for add, delete, tag, event commands.

Added missing constraints for tag command

Codecov Report

Merging #98 (e6187d8) into master (5e7fbb4) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #98   +/-   ##
=========================================
  Coverage     49.81%   49.81%
  Complexity      508      508
=========================================
  Files           124      124
  Lines          2459     2459
  Branches        322      322
=========================================
  Hits           1225     1225
  Misses         1143     1143
  Partials         91       91

Impacted Files
Coverage Δ

...java/seedu/address/logic/commands/ListCommand.java
100.00% <ø> (ø)

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 5e7fbb4...e6187d8. Read the comment docs.


HVM PARSE_ERROR expecting operator when copying the Map/get builtins.bend examples

Reproducing the behavior
This program used to work with v2.0.9 but is failing with all future versions:
Map.contains map key =
  match map {
    Map/Leaf: 0
    Map/Node:
      switch _ = (== 0 key) {
        0: switch _ = (% key 2) {
          0: (Map.contains map.left (/ key 2))
          _: (Map.contains map.right (/ key 2))
        }
        _: 1
      }
  }

def main():
  m = Map/set(Map/Leaf, 0, 1)
  return m[0]

Error:
 bend run ./src/map.bend
thread 'main' panicked at /Users/sam/.cargo/registry/src/index.crates.io-6f17d22bba15001f/hvm-2.0.11/src/main.rs:73:62:
PARSE_ERROR
- expected: operator symbol
- detected:
  3 | @Map.contains__C0 = ($([:/2] b) (a (* c)))
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Errors:
Failed to parse result from HVM.

Fails for run and run-c
bend run ./src/map.bend
bend run-c ./src/map.bend

System Settings

HVM: HVM 2.0.17
Bend: > 0.2.9
OS: Mac OS 14.1
CPU: M3

Additional context
The examples in builtins.bend also fail: https://github.com/HigherOrderCO/Bend/blob/main/src/fun/builtins.bend
Is there a CHANGELOG I can follow to understand changes in syntax/features/capabilities?

Closing, as I posted I noticed my HVM was an older version. Upgrading resolved the issue


chore(tab): change to linking function

Change to use linking function as the use of transclude on the compile has been deprecated by Angular

The deprecation notice in the documentation is here.

LGTM


Staking coin all missing after updated to 1.1.3.

Was staking every reward I got while using 1.0.x version, therefore, the staking wallet supposed to have around 300 to 400 SIT. staking wallet address: sit1xcutv4a54wcx454a8v8xqpf4akklvecp293k0xmfzhahp99dt6rqrxnvfn
But after updated to 1.1.3, below result show after I execute
./sit farm summary
Farming status: Farming
Total silicoin farmed: 0.0
User transaction fees: 0.0
Block rewards: 0.0
Last height farmed: 0
Local Harvester
1590 plots of size: 157.373 TiB
Remote Harvester for IP: <IP_ADDRESS>
195 plots of size: 19.300 TiB
Plot count for all harvesters: 1785
Total size of plots: 176.672 TiB
Staking addresses:
sit1xcutv4a54wcx454a8v8xqpf4akklvecp293k0xmfzhahp99dt6rqrxnvfn (balance: 0, plots: 1785)
Estimated network space: 177.441 PiB
Expected time to win: 5 hours and 48 minutes
Note: log into your key using 'sit wallet show' to see rewards for each key
The balance of my staking address is 0?? and why total silicoin farmed is 0.0??? it was at least like 300 ~ 400

The mainnet had restarted for version 1.1.x.

The mainnet had restarted for version 1.1.x.

Thanks for the reply. Will I get back my staking coin then?


Implement a way to export the FactorGraph data structure to a format like graphviz

I know that there are some packages for this on crates.io
Use a similar format for the nodes as https://gaussianbp.github.io/
where the factors are squares and the variables are circles.

Use different colors for the different factor types:

Pose Factor
Dynamics Factor
Obstacle Factor

Use fig. 2 from the paper as inspiration.


Error building docker image of CPU in Vitis AI v1.3.

Hi.
I was trying to use Vitis AI v1.3 released.
But I'm faced with problem to build docker image of CPU.
The error message is below:
_---> Using cache
---> 4fdb8b2c11ab
Step 28/46 : RUN cd /tmp     && wget --progress=dot:mega http://xcogpuvai01:8000/sdk-1013.sh     && chmod a+x /tmp/sdk-1013.sh     && /tmp/sdk-1013.sh -y     && rm -fr /tmp/     && chmod 777 /opt/petalinux/2020.2/sysroots/aarch64-xilinx-linux/
---> Running in d0937abf4273
--2020-12-17 19:26:54--  http://xcogpuvai01:8000/sdk-1013.sh
Resolving xcogpuvai01 (xcogpuvai01)... failed: Temporary failure in name resolution.
wget: unable to resolve host address ‘xcogpuvai01’
The command '/bin/bash -c cd /tmp     && wget --progress=dot:mega http://xcogpuvai01:8000/sdk-1013.sh     && chmod a+x /tmp/sdk-1013.sh     && /tmp/sdk-1013.sh -y     && rm -fr /tmp/     && chmod 777 /opt/petalinux/2020.2/sysroots/aarch64-xilinx-linux/' returned a non-zero code: 4_**
How can I fix it?

@lllkiller-jlll , this issue was replicated. It will be fixed soon.

Has this issue been fixed? I tried to find prebuilt image on dockerhub but they are up to version 1.3.4xx or 1.3.5xx. Can't find a way to get Vitis AI (cpu) v1.3 image.


Set default visibility for toolchains to public

Use public visibility for toolchains and related filegroups. This allows e.g. defining a toolchain as an alias target for a downstream project.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Oliver Lee seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

We are going to land this on https://github.com/aspect-build/gcc-toolchain/pull/109. The visibility usually comes after the load statements.


[FEATURE] Bun support

I'm trying to get a test suite running with Bun, but it seems to use node and jest no matter what I do. Feels like the wiring is under the hood and not configurable. It would be great to be able to run Reassure with Bun :)

I do not have too much knowledge about bun.
I've got some questions we could start with:

What command do you use in bun to run tests
Does bun uses any form of JIT?
Can you disable JIT in any way: CLI option, vm object call, etc?

I only know the answer to the first question - bun test :)
Expo for example is fully supporting Bun with all its tools now, and I get the feeling they're almost recommending it because of it's speed and reduced need for tooling.
Similarly to jest you can specify a test setup file, either with a --preload flag or in a bunfig.toml file.
Hopefully it's just a matter of being able to specify bun as the test runner instead of jest :)

This issue could/should be implemented in 2 phases:

[ ] Add support for bun install (bun as a package manager) - relative simple
[ ] Add support for bun test (bun a a test runner) - more complex

@mdjastrzebski
I gave it a try—I created a Vite project powered by Bun, installed Reassure with Jest, and ran it without any issues.
However, at least two problems are stopping me from running Reassure in the Bun runtime:
a) the test runner currently doesn't offer an option to customize test file patterns
b) bun's runtime performance isn't highly customizable.
It's fairly easy to make the changes needed to run Reassure in the Bun test environment, but performance may vary (runtime optimizations).


Add custom-logger example

Demonstrate how users can user their own logger via the
SettingEngine
Resolves #726

Codecov Report

Merging #736 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master     #736   +/-   ##
=======================================
  Coverage   76.63%   76.63%
=======================================
  Files          58       58
  Lines        4041     4041
=======================================
  Hits         3097     3097
+ Misses        688      687    -1
- Partials      256      257    +1

Impacted Files
Coverage Δ

peerconnection.go
73.04% <100%> (ø)
:arrow_up:

sctptransport.go
74.34% <0%> (-1.32%)
:arrow_down:

stats.go
82.05% <0%> (+5.12%)
:arrow_up:

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 10d2ca3...0e3111c. Read the comment docs.


[Issue 15768] Make std.stdio.File refcount shared(uint)

This is a band-aid, not a real fix for the underlying problem that stdout and stdin need to be shared.
With 20 runs of the sample program in the report, I was not able to reproduce the race condition after this fix.

Ping @schveiguy @atilaneves @mleise

I don't know how to begin fixing this error. std.stdio.File is so borked in terms of sharing that I think we may need a drastic redesign.
I do like the idea of having the atomic operations on the reference count. That should be the most performant way to go about fixing.

Can we do the atomic ref counting only in a this(this) shared overload?
Is the rest of File usable as shared?

You commit message should say fix Issue 12345, in order to be correctly referenced, this is indicated by the check mark in dlang-bot's comment.

This is not the best solution here - we're paying the cost of shared refcount for the sake of the three special handles.
There are several other possibilities here. A simple one is to simply check whether this is one of the special three files, and if it isn't just use non-atomic operations.
But the real matter here is the use of __gshared, which makes stdout unusable in safe code - something we definitely need to fix. At the time std.stdio was defined, shared was more buggy than now, so perhaps this is the right time to investigate what keeps us from using shared(File) properly.
That has other benefits as well: for non-shared Files we can just use the unlocked I/O primitives, which are faster.

I'm closing this for now. The right solution is to write a shared(File) implementation that's thread safe. That will require a lot of work that I'm not willing to take on at this moment.


Add feature bit for pay-to-open

Wallets should explicitly advertise support for pay-to-open in their init message, to allow the LSP they connect to to know whether they should open a channel on-the-fly when liquidity is missing to receive a payment.
Otherwise the LSP must use heuristics that may be incorrect and start the pay-to-open flow with nodes/wallets that don't support it (this is happening with electrum).
Ideally, we would even go further and define feature bits for the following features as well:

offline receive (wake-up on push notification)
trusted swap-in
open-back

It would be a good opportunity to introduce that, WDYT?
And a later PR should also introduce support for actually disabling these features (and turning off the corresponding code branches).
NB: this can be merged after the initial release, no rush.

Seems like a good idea 👍 we could add the swap-in bit now as well
Also why not use a even higher feature bit? 60 does not seem very high to me.

Also why not use a even higher feature bit? 60 does not seem very high to me.

True, we could. At the rate at which features get adopted in the spec, I think 60 and above still let us enjoy these for at least 10 years, but we can be more prudent :laughing:


Regression test for #188

Current coverage is 59.21% (diff: 100%)

Merging #189 into master will not change coverage

@@             master       #189   diff @@
==========================================
  Files           119        119
  Lines          6255       6255
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           3704       3704
  Misses         2237       2237
  Partials        314        314

Powered by Codecov. Last update 864dc97...f05ac60


fix: old x axis labels were not destroyed during data update if parsing was set to false or an object with custom axis keys

When parsing was set to false or an object with xAxisKey or yAxisKey, there were issues if chart data was updated more than once.
Apparently, old x labels were not destroyed, resulting in merging old and new x labels.
This PR destroys old x labels every time data is updated, provided that chart has parsing set to false or an object with custom keys.
According to docs: https://www.chartjs.org/docs/next/general/data-structures.html, labels should only be set manually when importing primitive data so this does not break any kind of labels list set on chart initialization.
Fixes #9599

Would definitely be good to have a test for this

Looks like this needs a rebase and the test being added.

@etimberg I added 2 new tests for this case. I made use of meta.iScale inside tests which I'm not sure if it's appropriate.
Please let me know if further improvements are needed.

Sorry @DimitrisRK for hijacking your fix, but we are getting eager to publish 3.6.1

Sorry @DimitrisRK for hijacking your fix, but we are getting eager to publish 3.6.1

I'm the one who should apologize for my delay. It appears my approach did not cover all cases so I hit a dead end.
I'm glad that someone else will take care of this. Closing this PR in favor of #9921 . :)


more robust & explicit error handling for sent txs, wbtc price fix, pep8 conventions, refactoring

This includes the fix for Tally's PR for the wrapped bitcoin price. Review my comment there for explanation.
Adds handling for timeout errors when querying a transaction (tx) receipt. This happens because the submitted gas price was too low. It adds 50 to the gas price until it doesn't get this error. In the future, this extra gas price value should be retrieved from a flag when running the script, so it's not hard-coded.
Adds handling for gas prices that are too high and if the wrong nonce is being used.
Changes constants to all-caps and variable names to snake case per PEP8 convention.
Uses some type hinting to increase readability and hopefully reduce debugging time in the future.

Add better alert messages for specific errors when sending transactions. You can also name your specific MesosphereSigner in the .env file by changing BOT_NAME, so it's easy to identify which signer (reporter?) the errors come from.
Sends the median of four wrapped bitcoin prices retrieved from some public apis. Adds one missing api keyword to the coingecko endpoint. The medianize_wbtc function can easily be made more reusable, so future asset additions can just use the same function.


How to debug Libcarla ?

Hello,
I'm trying to debug a bug that I suspect in TrafficManager (0.9.8 version), where if I don't reset the server between running successive spawn_npc.py example, the cars are not updated anymore.
However, my main issue is that I don't know how to debug with an IDE (Clion, VS, etc) the code inside LibCarla. Can anyone provide some ideas?
Thanks!

With plain gdb works well,
gdb --args python spawn_npc.py

you should be able to set this somewhere in your IDE configuration.

Hi, @paduraru2009 !
Did that solve your issue?

Hi,
This helped me actually:
https://intellij-support.jetbrains.com/hc/en-us/community/posts/360001787679-Debugging-python-extensions
But I will try with Nestor said too.
On Fri, Apr 24, 2020 at 1:11 AM sergi.e<EMAIL_ADDRESS>wrote:

Hi, @paduraru2009 https://github.com/paduraru2009 !
Did that solve your issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/carla-simulator/carla/issues/2747#issuecomment-618697967,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACPXQCE4O2YGQDOMQ3DLANTROC4IDANCNFSM4MIXNAHA
.

Hello, @nsubiron !
I encountered an error when running spawn_npc.py.
$ python3 spawn_npc.py
ERROR: Spawn failed because of collision at spawn position
ERROR: Spawn failed because of collision at spawn position
ERROR: Spawn failed because of collision at spawn position
ERROR: Spawn failed because of collision at spawn position
ERROR: Spawn failed because of collision at spawn position
ERROR: Spawn failed because of collision at spawn position
ERROR: Spawn failed because of collision at spawn position
ERROR: Spawn failed because of collision at spawn position
ERROR: Spawn failed because of collision at spawn position
ERROR: Spawn failed because of collision at spawn position
ERROR: Spawn failed because of collision at spawn position
ERROR: Spawn failed because of collision at spawn position
ERROR: Spawn failed because of collision at spawn position
ERROR: Spawn failed because of collision at spawn position
terminate called after throwing an instance of 'std::out_of_range'
  what():  vector::_M_range_check: __n (which is 0) >= this->size() (which is 0)
Aborted (core dumped)

I want to inspect where this error comes from, so I ran it again in gdb.
However, the information did not change, and I still cannot locate the cpp source file.
Could you please tell me how to debug into LibCarla cpp file and see values of variables when this error happens?
(I'm sorry that this may not be a carla issue.)
I am using carla 0.9.8.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Registered pretty printers for UE4 classes
Reading symbols from python3...(no debugging symbols found)...done.
(gdb) run spawn_npc.py
Starting program: /usr/bin/python3 spawn_npc.py
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff38d2700 (LWP 16764)]
[New Thread 0x7ffff30d1700 (LWP 16765)]
[New Thread 0x7ffff28d0700 (LWP 16766)]
[New Thread 0x7ffff20cf700 (LWP 16767)]
[New Thread 0x7ffff18ce700 (LWP 16768)]
[New Thread 0x7ffff10cd700 (LWP 16769)]
[New Thread 0x7ffff08cc700 (LWP 16770)]
[Thread 0x7ffff10cd700 (LWP 16769) exited]
[Thread 0x7ffff08cc700 (LWP 16770) exited]
[New Thread 0x7ffff10cd700 (LWP 16771)]
[New Thread 0x7ffff08cc700 (LWP 16783)]
[New Thread 0x7fffd9ffe700 (LWP 16784)]
[New Thread 0x7fffd97fd700 (LWP 16785)]
[New Thread 0x7fffd8ffc700 (LWP 16786)]
[New Thread 0x7fffd093b700 (LWP 16787)]
[New Thread 0x7fffdbfff700 (LWP 16788)]
[Thread 0x7fffdbfff700 (LWP 16788) exited]
[New Thread 0x7fffdbfff700 (LWP 16789)]
[New Thread 0x7fffdb7fe700 (LWP 16790)]
[Thread 0x7fffdbfff700 (LWP 16789) exited]
[Thread 0x7fffdb7fe700 (LWP 16790) exited]
ERROR: Spawn failed because of collision at spawn position
ERROR: Spawn failed because of collision at spawn position
ERROR: Spawn failed because of collision at spawn position
ERROR: Spawn failed because of collision at spawn position
ERROR: Spawn failed because of collision at spawn position
ERROR: Spawn failed because of collision at spawn position
ERROR: Spawn failed because of collision at spawn position
ERROR: Spawn failed because of collision at spawn position
ERROR: Spawn failed because of collision at spawn position
ERROR: Spawn failed because of collision at spawn position
ERROR: Spawn failed because of collision at spawn position
[New Thread 0x7fffdb7fe700 (LWP 16791)]
[Thread 0x7fffdb7fe700 (LWP 16791) exited]
spawned 10 vehicles and 39 walkers, press Ctrl+C to exit.
terminate called after throwing an instance of 'std::out_of_range'
  what():  vector::_M_range_check: __n (which is 0) >= this->size() (which is 0)

Thread 10 "python3" received signal SIGABRT, Aborted.
[Switching to Thread 0x7ffff08cc700 (LWP 16783)]
0x00007ffff7825438 in __GI_raise (sig=sig@entry=6)
    at ../sysdeps/unix/sysv/linux/raise.c:54
54	../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb)

Hi, @paduraru2009 !
I tried to follow the page you provided but I still can not debug into LibCarla.
I think it's probably because the LibCarla has not been compiled -O0.
Can you tell me where I can change the debug mode from -O2 to -O0 for LibCarla?
I changed it in Setup.sh.
However when I make PythonAPI, the option is still -O2.

@nsubiron @paduraru2009 , sorry for the bother...
I made it using catch throw std::out_of_range before running spawn_npc.py in gdb.


/usr/local/bin/wrapdocker: line 100: docker: command not found

Pulling down the latest dind image and running the commands in the README results in this error.
$ docker run --privileged -t -i dind
/usr/local/bin/wrapdocker: line 100: docker: command not found

exit

It looks like the failures started after the build with id b9bmvvmja6wpyacvgmhzkit (20 Nov 2015).

Haha, I forgot about it, and somehow came across a GitHub view that listed all of my open issues. I figure that sometime in the last 3 years, we fixed this 😆


Runs parametrization

Description
Runs (both one-off and scheduled) support parameters override. Additionally, run names can be templated with the provided params to quickly distinguish objects in Kubeflow Pipelines UI
Resolves #89
PR Checklist

[x] Tests added
[x] Changelog updated

@em-pe / @mariusz89016  Please ignore Codeclimate reports, these are all minors

LGTM


Infer function return type as type-guard for typeof comparison

Suggestion

🔍 Search Terms

typeof, type-guard, filter, Array.filter
✅ Viability Checklist

My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion

If a function returns the result typeof something === "<type>", then the return type of this function should be inferred as something is <type> and not just boolean.
📃 Motivating Example

An arrow function such as item => typeof item === "string" is prime example of a predicate that can be used with Array<string | undefined>.filter<string>. With the new automatic type infering, this arrow function can be used a type narrowing predicate.
💻 Use Cases
The following code is valid JavaScript, but not TypeScript.
const list = ["foo", undefined, "bar"].filter(item => typeof item === "string");
for (const item of list) {
  console.log(item.length); // Object is possibly 'undefined'.
}

Because the type of list is (string | undefined)[] and not string[]. The proposed feature fixes this.
To work-around this issue, the predicate must be explictly typed as a type-guard. For example:
function isString(item: string | undefined): item is string {
  return typeof item === "string";
}
const list = ["foo", undefined, "bar"].filter(isString);
for (const item of list) {
  console.log(item.length); // OK
}

Duplicate of #38390.

Duplicate of #38390.

indeed.

To work-around this issue, the predicate must be explictly typed as a type-guard.

While this is correct, it doesn't necessarily have to be a new function, it can stay the fat-arrow function.

yes.


enhance(integration-test): leverage a custom implementation of DeepEqual

What are some thoughts on this? It will help eliminate those pesky time skew failing workflows. Not sure this is the best implementation of the concept either, so any advice would be appreciated too.

love the idea - can we leverage https://pkg.go.dev/github.com/google/go-cmp/cmp somehow for this? we already import it.

I see the edits, but I was thinking of it a bit differently. Can we just use cmp.Equal at the top level and define a custom Comparer to handle UpdatedAt to replace your custom function and switch statement?


chore: added gitlab pr insights and code usages as possible caller values

Current dependencies on/for this PR:

main

PR #290   👈

This comment was auto-generated by Graphite.


Correct citation format

It’s recently been pointed out that we (or me) have some inconsistency in the use of citation. The correct format, which I need to update on some of our portals as well, is:
[Resource].[YYYYMMDD or YYYY]. ICES, Copenhagen, Denmark. [URL]
Example:
European Seabirds At Sea (ESAS). 2022. ICES, Copenhagen, Denmark. https://esas.ices.dk

@Neilmagi I just added a commit to this, to have the date without square parenthesis and make the link a hyperlink like Neil suggested in the example he gave.

Let me know if it is ok and I will merge into main


Run MXNET with Muti-machine

HI，Is it possible to show some examples of how to run mxnet on multi-machines？
Thx

will be there next week

Looking forward to it

Here is the example, https://mxnet.readthedocs.org/en/latest/distributed_training.html
we are also actively look for contributors to try and improve it #533


Issue with destroying collection

From the readme, this is a valid use case:
instances = [instance1, instance2]
MyModel.with_explicit_persistence_for(instances) do
  instances.destroy_all
end

However, instances is an array, whereas destroy_all is a method on ActiveRecord_Relation, and passing in a relation causes a Sorbet error. I could make this work as follows:
instances = MyModel.where(some_criteria)
MyModel.with_explicit_persistence_for(instances.to_a) do
  instances.destroy_all
end

but I would think with_explicit_persistence_for should allow an ActiveRecord_Relation to be passed in.
I can draft a PR when I have some free time.

Hey I think accepting a relation here and automatically coercing it to an array could make sense! It might cause performance issues coercing a large relation to an array, but I suppose that's what we're already recommending the client do in this case, and I think destroy_all calls destroy on each instance in the relation anyways.
Happy to look at a PR!


StackOverflow when attacked by Guardians with Drowning Phobia

Game version: 1.18.2
Forge version: 40.1.59
Mod version: 1.2.5
This is vanilla Guardian#hurt, it will reflect non magic damage and deal thorn damage to the damage source, which will again trigger the Drowning Phobia. A possible workaroud is to set FlowingAgonyMobtoMobDamageSource as magic damage, but a special check for it may be a better solution.
public boolean hurt(DamageSource p_32820_, float p_32821_) {
      if (!this.isMoving() && !p_32820_.isMagic() && p_32820_.getDirectEntity() instanceof LivingEntity) {
         LivingEntity livingentity = (LivingEntity)p_32820_.getDirectEntity();
         if (!p_32820_.isExplosion()) {
            livingentity.hurt(DamageSource.thorns(this), 2.0F);
         }
      }

      if (this.randomStrollGoal != null) {
         this.randomStrollGoal.trigger();
      }

      return super.hurt(p_32820_, p_32821_);
   }

Step to reproduce:

Get a low tier helmet(e.g., leather helmet)
Enchant it with Drowning Phobia
Summon 3 Guardians
Swim and get attacked by Guardians

Crash report:
Crash report from dedicated server (Arclight server, may contain irrelevant info)
Crash report from local game

Please use 1.2.6. Thank you for detailed report!

Wow, thanks for your quick response! That should fix this. Thank you for the amazing mod!


Improve performance of date/time conversions

As my database grows I've been noticing the performance starting to become an issue when compared with other database client implementations. I'm not sure if this is my code in particular or implementation differences.
Consider I have a table with 7 or so columns and about 6000 rows. The columns contain simple data: last name string, some integers, a timestamp, a few other strings.  I want to retrieve the entire table - all rows and columns (so a simple SELECT statement).  As I read each row from the query, the columns are parsed into their native types and stored in a list of objects.
I have a Java client using JDBC running on a laptop, for which this operation takes about 300 milliseconds.  Roughly about 250 Kbytes are retrieved.
An iPhone and iPad on the same Wi-fi network running PostgresClientKit take about 8 seconds.
I don't think this is a network speed issue.
The laptop is faster of course, but hard to believe it's that much faster.
Both connections use SSL, possibly a performance issue in BlueSSLService.
Possibly the JDBC client is pre-fetching all rows before the cursor increments to them?  Is there efficiency to be gained by trying to fetch all rows at once?
Could there be an underlying socket performance issue with blocking/non-blocking reads?
Any thoughts appreciated.

To compare PostgresClientKit performance between macOS and iOS, I created two repositories:
https://github.com/pitfield/PostgresClientKit-Performance-CommandLine
https://github.com/pitfield/PostgresClientKit-Performance-iOS
The first is a macOS command line executable; the second is an iOS app.  In each case, they create a simple table, INSERT 1000 rows into it, and then SELECT those 1000 rows, converting the columns to native types and accumulating the rows in an array.
I'd be interested to see results from your environment.  You'll need to tweak the ConnectionConfiguration properties in main.swift and ViewController.swift.  The apps log the timing info the stdout, and you can see it in the Xcode console.
In my environment, here are the times to SELECT and process the 1000 rows (3 runs of each configuration):
macOS           ssl=false   164ms 162ms 163ms  (2017 iMac)
                ssl=true    164ms 166ms 165ms

iOS simulator   ssl=false   155ms 153ms 155ms  (iPad 7th gen simulator)
                ssl=true    164ms 161ms 162ms

iOS device      ssl=false   348ms 347ms 358ms  (iPhone 6s)
                ssl=true    309ms 340ms 333ms

So it takes about twice as long on the iOS device as compared to the macOS command-line executable or iOS simulator.  That seems about right to me.  The iOS device needs to shove bytes over the wire; the other two do not.  In each case, turning SSL on has little performance impact.
(When you run the apps, you'll also see how long it takes to INSERT the 1000 rows.  For that measurement, the iOS device is much slower than the macOS command-line and iOS simulator.  That too makes sense -- there are a lot more network round trips to INSERT 1000 rows, one at a time, than to SELECT 1000 rows at once.)
  There is a known issue in BlueSSLService that required a workaround in PostgresClientKit.  The workaround involves a spin-wait when the BlueSSLService problem is detected.  I've only seen this problem arise infrequently, and even then, only briefly...but there is the possibility it is causing a delay in your environment.  I added some diagnostic logging to the pitfield/issue-26-diagnostics branch.  You could try picking up the branch.  If the BlueSSLService problem occurs, you'll see log entries containing "Issue #26: slept for 10 ms after socket read returned 0".  Each such entry represents a 10ms delay.
I don't know if the JDBC client driver retrieves all rows before returning the ResultSet to the caller.  Even if it did, the driver would see exactly the same bytes at the socket level.  The Postgres network protocol doesn't provide any optimizations for clients that want all the rows at once; it always just writes one row after another.  Still, it would be interesting to compare the macOS performance of JDBC vs PostgresClientKit (both with the server on the same host, and with the server on the network).
Hope this helps.  Please let me know what you find.

It appears to be using that, yes.

Yes, I can certainly believe that date/time conversions are slow.  This is one of the reasons that PostgresClientKit doesn't immediately return column values as native types.  The caller needs to ask for them.
In PostgresClientKit, these conversions are handled by DateFormatter, DateComponents, and Calendar.  I believe that those types are ultimately implemented in C.
In your scenario, what is the TIMESTAMP column modeling?  If it's a "point in time" (for example, created or lastModified), you might want to consider using TIMESTAMP WITH TIME ZONE instead (and PostgresTimestampWithTimeZone in Swift).  TIMESTAMP records a year, month, day, hours, minutes, and seconds....but not the time zone in which to interpret those components.  Consequently, everywhere a TIMESTAMP value is used, the time zone needs to be specified.  In my experience, this is susceptible to bugs in date/time handling.  For example, one time zone is specified in a database stored procedure, but a different one is selected in a client app.
TIMESTAMP WITH TIME ZONE values, on the other hand, explicitly specify the time zone.  So there's no guessing.  The Postgres server automatically normalizes these values to UTC/GMT for storage, which is handy.  TIMESTAMP WITH TIME ZONE values represent "points in time", just like Date instances do in Swift, so converting back and forth is more natural.  It's also quite a bit faster!
I did some benchmarking on my iPhone 6s, looking at how long it takes to convert from PostgresValue (which just wraps a string) to Timestamp/TimestampWithTimeZone, and then onto Date.
----------------------------------------------  ------
Conversion from --> to                          Time
----------------------------------------------  ------
PostgresValue -> Timestamp                      205 us
PostgresValue -> Timestamp -> Date              294 us
PostgresValue -> TimestampWithTimeZone          109 us
PostgresValue -> TimestampWithTimeZone -> Date  112 us
----------------------------------------------  ------

So 6000 Postgres -> Timestamp -> Date conversions would take 1.76 seconds, whereas Postgres -> TimestampWithTimeZone -> Date would take 0.67 seconds.
Another thought:  Do you need to immediately convert all 6000 values to Dates?  Could this be done lazily?  For example, if you're showing them in a UITableView, how about deferring it until the table view asks for a cell?

So 6000 PostgresValue -> PostgresTimestamp -> Date conversions would take 1.76 seconds

Yeah, that is unacceptably slow. Avoid using DateFormatter when parsing dates in a protocol context at all costs. Yes, they also end up calling C code in ICU, but in super expensive ways (even for processing tiny amounts of data, like a few thousands of values).

I tried two different approaches to speeding up.  One was to fetch all the rows first, then dispatch each row for parsing on a concurrent dispatch queue.  Despite multiple threads working at once there wasn't much improvement (possibly due to the mutexes needed to protect the collection that they were added to).
However this extension to PostgresValue was a marked improvement.  From 8 seconds down to 3 seconds.  Note however this approach isn't thread safe.

In your extension, as soon as you touch Calendar/Locale and the likes, everything is going to slow down.
Also, all those allocs are horrible, you should be able to just & the values?
To convert the local timezone, use mktime, localtime and friends (you don't seem to parse a timezone name?). Then feed the time_t into Date(timeIntervalSince1970:).

The allocs are static - they're not used each time. Hence the non-reentrance.  The author where I found this was down on mktime. I tried it and was slightly slower than Calendar/Locale.
I guess this is the best I can do - still a big improvement over the DateFormatter.

Thanks for looking at this.  In this extension, I tried yet another approach.  I also made a few tweaks to the vsscan approach.  For an optimized build (Swift Compiler - Code Generation Optimization Level "-O"), the performance of both approaches is nearly identical, a shade under 40 us.  (For reference, we started at 294 us.)  I'd be interested to learn how these perform in your scenario.  Thanks!

(Just fixed a bug in that extension to handle the "no fractional seconds" case.)

@pitfield thanks for that extension. Great idea to use a static Calendar instead of allocating each time! That saved more processing time.
So I went from 8 seconds without the extension to 3 seconds with my first extension and adding the static calendar gets me down to 1.7 seconds.  Not bad!
In either approach, its either not thread safe or you need a semaphore to protect the statics. C'est la vie.
In my case, this is working much better.  Thanks @helje5 and @pitfield for your input!
If I could re-architect the database I think I'd store the time as a double instead, and avoid all these string parsing headaches.

OK, thanks for trying that out.  I'm glad we found an approach that is more performant.  I will incorporate this into the next release.  In doing so, I want to revisit how PostgresClientKit does date/time conversions in general.  I don't have time to do that right now, though, so I suggest you use your extension for moment.

This thread identified that the Foundation classes for date/time conversion, such as DateFormatter, are slow.  Several more performant approaches were identified.
This bug, then, is to revisit how date/time conversions are implemented throughout PostgresClientKit, and incorporate more performant approaches where applicable.

Finally got this done.  Here are the benchmark results:
-----------------------------------------------------------------------------------
String to Date conversion performed                 Before     After    Improvement
-----------------------------------------------------------------------------------
PostgresValue(_:).timestampWithTimeZone().date       67 us     11 us     6x faster
PostgresValue(_:).timestamp().date(in:)             171 us     13 us    13x faster
PostgresValue(_:).date().date(in:)                  159 us     13 us    12x faster
PostgresValue(_:).time().date(in:)                  166 us     16 us    10x faster
PostgresValue(_:).timeWithTimeZone().date           290 us     13 us    22x faster
-----------------------------------------------------------------------------------

Released in v1.3.2.


Allow for non-inheritance usage

Working PoC that relates to https://github.com/lloydmeta/enumeratum/pull/187

Extract typeclass-building methods into a trait, SlickEnum that can be
used via inheritance or via its companion object

Instead of taking an abstract val profile, simply takes profile as a param
and returns a type-dependent profile.BaseColumnType

Have SlickEnumSupport extend this trait and offer additional sugar based on it

Actually, looking at this again, it seems like the wrappers are basically just super trivial wrappers around  profile.MappedColumnType.base[E, S]. Maybe it isn't even worth the effort 😆


Provide options to Limit TP2 size or to reinsert random destruction

To provide more options for core developers we should Provide core setting options to Limit TP2 size and/or to reinsert random destruction.
This would involve changes to
Cores
Code to save
TP2 rip code
Forum thread which suggested this is here - http://www.freeallegiance.org/forums/index.php?showtopic=55996
Imported from trac ticket #67,  created by notjarvis on 03-17-2010 at 17:36, last modified: 02-24-2012 at 07:22

Besides chance to destruct and energy capacity, an energy regen attribute would be nice to have as well.
Trac comment by Adaven on 05-08-2010 at 04:39

Replying to [comment:3 fuzzylunkin1]:

ICE has nothing to do with it, it's just one of the tools you can edit cores with.
I know exactly what ICE is
It's the most used tools to develop cores. If we put a setting in that isn't replicated in ICE - no-one will use the setting and we'll have wasted our time.

At the very least we need to be aware of making a setting ICE editable
Trac comment by notjarvis on 07-19-2010 at 13:02

ICE has nothing to do with it, it's just one of the tools you can edit cores with.
Trac comment by fuzzylunkin1 on 07-19-2010 at 07:00

The author of ICE is no longer maintaining it.  The recommended way to create a binary IGC file is by using AllSrv.  Extending core features can be done easily (you dont need an AZ database) with the new Import/export routines built into -Core2Text and Text2Core
Trac comment by anonymous on 07-19-2010 at 17:17


Add update with prompts and update db with user inputs

Adds update prompts and updates related inputs in db


For hacktoberfest issue#19

Commented all instances of ->logger across files

Just delete those instances, if someone ever might think they want to use it they can.

Deleted all instances now!

@rayoriz normally when I delete stuff I also delete extra whitelines and stuff that is not needed.
It's something I actually miss.
Can you fix that too ?

Cool. Deleted whitelines and also some deadcode now.


Preview release doesnt see bundles in input/tests

The preview release of the plugin does not process bundles in input/tests. This breaks tests.

0.7.3 version of the plugin does only seem to work with tests that are individual resources and not bundles. Given all exports from MADiE are bundles it should either support bundles or there should be tooling to extract them into individual resources to facilitate testing


move v4 documentation first, i almost missed it

the v4 documentation was last and I almost missed it. bumped it up in the readme since its the latest release.

@sdowding thank you!


mympd: 16.0.1 -> 16.1.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/mympd/versions.
meta.description for mympd is: Standalone and mobile friendly web mpd client with a tiny footprint and advanced features
meta.homepage for mympd is: https://jcorporation.github.io/myMPD
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 16.1.0 with grep in /nix/store/mhsc1nz6qxmngdapw8w5ncvyymmh4mqh-mympd-16.1.0
found 16.1.0 in filename of file in /nix/store/mhsc1nz6qxmngdapw8w5ncvyymmh4mqh-mympd-16.1.0

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

mympd

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/mhsc1nz6qxmngdapw8w5ncvyymmh4mqh-mympd-16.1.0 \
  --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 mympd https://github.com/r-ryantm/nixpkgs/archive/c5d0806e9f9bc6139e4f724a59918ed8bd121c68.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/c5d0806e9f9bc6139e4f724a59918ed8bd121c68#mympd

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/mhsc1nz6qxmngdapw8w5ncvyymmh4mqh-mympd-16.1.0
ls -la /nix/store/mhsc1nz6qxmngdapw8w5ncvyymmh4mqh-mympd-16.1.0/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:

mympd

Maintainer pings
cc @doronbehar for testing.

@ofborg eval


add phantom to connect wallet modal

What changed? Why?
Added Phantom to ecosystem page and connect wallet modal, per Jesse's tweet.
Notes to reviewers
Thank you for the warm welcome to Base! Phantom added Base support on Monday 10/7.
How has it been tested?
Ran locally to confirm. See screenshot below

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/1

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
0

Sum
1


Integrate current execution check with replication resender

What changed?
Integrate current execution check with replication resender

Why?
For corrupted workflow, we don't need to put it into dlq.

How did you test it?

Potential risks
N/A

Coverage decreased (-0.02%) to 66.884% when pulling 2bc7fdfe4ee11a497e5b227134b2f29d6d076074 on dlq_check into 4ac545c0dcda9ad930506ce4f31acd0a0c7b0b31 on master.


ircspeed

@istoking

wait.. how am I an issue? I don't even use a wifi-heatmap

It worked! Got your attention :-)

I would appreciate an email.


🐛 Support displaying variables with non-unicode data

Description
This fixes #756
DAP is JSON-based, so the state of all variables is dumped into a string that needs to be unicode. When a variable contains binary data that is NOT unicode, this breaks with: source sequence is illegal/malformed utf-8.
This patch makes sure that we can display at least part, and show the user that the data they are seeing is not exactly the one that is in memory.
Testing
I tried this in VSCode (which uses DAP), and saw:

Before this patch: the debugging session crashes
After this patch:

As a side note, vscode-ruby-debug doesn't even try to show the variable content and just shows [Invalid encoding], which, IMO, is a worse UX.

Let me check another debuggers on VSCode (DAP servers)

Thank you!


[Event Request] - Codeunit 9520 "Mail Management" - procedure OnAfterDownloadPDFAttachment

🕮 Describe the request
For a large customer project that we need to migrate to the cloud, we need the following event/customization.
Please add the following event
end;

[Obsolete('Replaced with the overload containing Email Scenario', '17.0')]
[Scope('OnPrem')]
procedure SendMailOrDownload(TempEmailItem: Record "Email Item" temporary; HideMailDialog: Boolean)
begin
    SendMailOrDownload(TempEmailItem, HideMailDialog, Enum::"Email Scenario"::Default);
end;

procedure DownloadPdfAttachment(var TempEmailItem: Record "Email Item" temporary)
var
    DataCompression: Codeunit "Data Compression";
    Attachments: Codeunit "Temp Blob List";
    Attachment: Codeunit "Temp Blob";
    AttachmentArchiveTempBlob: Codeunit "Temp Blob";
    AttachmentNames: List of [Text];
    AttachmentName: Text;
    AttachmentStream: Instream;
    AttachmentOutStream: Outstream;
    AttachmentNumber: Integer;
    IsHandled: Boolean;
begin
    IsHandled := false;
    OnBeforeDownloadPdfAttachment(TempEmailItem, IsHandled);
    if IsHandled then
        exit;

    TempEmailItem.GetAttachments(Attachments, AttachmentNames);
    if Attachments.Count() = 1 then begin
        AttachmentName := AttachmentNames.Get(1);
        Attachments.Get(1, Attachment);
        Attachment.CreateInStream(AttachmentStream);
        DownloadFromStream(AttachmentStream, SaveFileDialogTitleMsg, '', SaveFileDialogFilterMsg, AttachmentName);
    end else begin
        DataCompression.CreateZipArchive();
        for AttachmentNumber := 1 to Attachments.Count() do begin
            AttachmentName := AttachmentNames.Get(AttachmentNumber);
            Attachments.Get(AttachmentNumber, Attachment);
            Attachment.CreateInStream(AttachmentStream);
            DataCompression.AddEntry(AttachmentStream, AttachmentName);
        end;
        AttachmentName := 'Attachments.zip';
        AttachmentArchiveTempBlob.CreateOutStream(AttachmentOutStream);
        DataCompression.SaveZipArchive(AttachmentOutStream);
        DataCompression.CloseZipArchive();
        AttachmentArchiveTempBlob.CreateInStream(AttachmentStream);
        DownloadFromStream(AttachmentStream, SaveFileDialogTitleMsg, '', SaveFileDialogFilterMsg, AttachmentName);
    end;

    //NEW EVENT Start
    OnAfterDownloadPDFAttachment();
    //NEW EVENT End

end;

[Scope('OnPrem')]
procedure ImageBase64ToUrl(BodyText: Text): Text
var
    Regex: DotNet Regex;
    Convert: DotNet Convert;
    MemoryStream: DotNet MemoryStream;
    SearchText: Text;
    Base64: Text;
    MimeType: Text;
    MediaId: Guid;
    IsHandled: Boolean;
begin
    IsHandled := false;
    OnBeforeImageBase64ToUrl(BodyText, SearchText, Regex, MemoryStream, MediaId, Base64, Convert, IsHandled);
    if IsHandled then
        exit(BodyText);

[IntegrationEvent(false, false)]
local procedure OnAfterDownloadPDFAttachment()
begin
end;

Additional context

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: .


Feat add rewrite rule LikeToEqualRewrite

like expressions without fuzzy matching are rewritten into equivalent expressions

run buildall

run buildall

run buildall

run external


add docker support

Why did you close this?

Sorry about this, all PRs have been closed following a force push that I had to do. Did a silly mistake and pushed some potentially sensitive information in one of my commits and had to rewrite the repo history. Feel free to re-submit!


Displaying problem when playing with the visibility of elements in certains rows

Hello,
As you can see on this images, there is a displaying problem when i modify the visibility of some elements.
If there is an element of a row with a GONE visibility, it seems the the same element in other row became INVISIBLE and the displaying is weird.
Also, when I have more than 4 rows on my listView, some elements in different rows are hiden by nothing and just half displaying ... (first image, row 2, after Match there is a 6 half displayed ...)
This change randomly (it seems) when going in landscape and going back on portrait. Sometimes it is good, some times not ...
This is really disapointing because the library is awesome !!! Good job !
Thanks
Weird Displaying :

Normal displaying :

I relesed a v1.2.0, please have a try.

Thanks for the release, but I am having the displaying problem
With the new release i got :
Normal displaying when I just start the app

Weird displaying when I scroll down until the last element and come back to the first one :

Is your listview's adapter is subclass of BaseSwipeAdapter?

yep !

Try use FrameLayout instead of SwipeLayout, to look is it displaying weird.

hum weird, I try with frameLayout, everything was good, I came back to swipe layout, It was good to. I tried to add/delete element and everything stay well displayed ... I tell you if a found a configuration where the displaying is not good after scrolling and good with the frameLayout


FAILED: DistributedReceptionist test_receptionist_listing_shouldRespondWithRegisteredRefsForKey

Something fishy going on with listing API, check the test_receptionist_listing_shouldRespondWithRegisteredRefsForKey.

The test runs successfully if wrapped in try runAsyncAndBlock and remove async keyword from the test method, but ideally the test should run without these changes.


Fix for 'click' event getting suppressed in iOS.

While the suppression of 'touchstart' does prevent the entire page from being drug in iOS, it also kills all 'click' events in the rest of the page.

Thank you!


feat: port FieldTheory.IsAlgClosed.AlgebraicClosure

I pushed a couple of fixes but I have to sleep now

I am having a look at this.

This is now basically done except for Step.isIntegral, where one would have to decide whether to increase the Heartbeats to 2 mil. or change something.

It actually did time out for me with 2 mil...? I'll make an attempt to change it.

bors merge

It's sad that it is so slow, but we can always improve it later, thanks!
bors merge


Destroy on element

Hi there,
I was wondering if there was a way to cancel the logoDistort on an element you have added it to? I can see a few methods for destroying but I'm unsure how to call them.
Thanks for your help in advance!

you should be able to just call .destroy() on any distort element that you created.


Small fixes in GKE guide

I noticed that the node configuration part has strange commands in it. Also, I wanted to add a small part about getting Submariner to work once nodes were shut down, as this took me a little while to figure it out.

I have my git history all messed up, I will try again ...


The alpa server is down

Hello, the alpa installation page installs alpa modified Jax-lib from http://<IP_ADDRESS>:8080/simple/ which is broken. Please fix!

@ImproveTheNewsFoundation Just restarted -- please let me know if you still see the issue!

Modifyed Jax-lib from  http://<IP_ADDRESS>:8080/simple/ failed.
There are other ways to download jaxlib==0.3.5 ?

@chaosGuppy @wgimperial restarted -- try agin. We'll try to migrate to a more stable server

is alpa server is down again?


RT-1.32 BGP import/export policy action - MED, prepend, flow-control

Adding RT-1.32.1 testcase - IPv4, IPv6 iBGP set MED

Pull Request Functional Test Report for #2703 / d7c9b2f9484a077b355674e6836b6a2f6cf78449
Virtual Devices

Device
Test
Test Documentation
Job
Raw Log

Arista cEOS

RT-1.32: BGP policy actions - MED, LocPref, prepend, flow-control
e1eaa7fa
Log

Cisco 8000E

RT-1.32: BGP policy actions - MED, LocPref, prepend, flow-control
e74009bb
Log

Cisco XRd

RT-1.32: BGP policy actions - MED, LocPref, prepend, flow-control
d7108a11
Log

Juniper ncPTX

RT-1.32: BGP policy actions - MED, LocPref, prepend, flow-control
b93acd52
Log

Nokia SR Linux

RT-1.32: BGP policy actions - MED, LocPref, prepend, flow-control
8f9a3fcf
Log

Openconfig Lemming

RT-1.32: BGP policy actions - MED, LocPref, prepend, flow-control
760925cc
Log

Hardware Devices

Device
Test
Test Documentation
Raw Log

Arista 7808

RT-1.32: BGP policy actions - MED, LocPref, prepend, flow-control

Cisco 8808

RT-1.32: BGP policy actions - MED, LocPref, prepend, flow-control

Juniper PTX10008

RT-1.32: BGP policy actions - MED, LocPref, prepend, flow-control

Nokia 7250 IXR-10e

RT-1.32: BGP policy actions - MED, LocPref, prepend, flow-control

Help

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1736

Relevant Lines:
3272

💛  - Coveralls


W11 Build 22631.4169 Not Listening

Following .ini just fixed Not Supported -> Fully Supporter | Listener still "Not Listening"
rdpwrap.ini.txt
Screenshot:

Please, attach your  termsrv.dll.

[10.0.22621.3958]
LocalOnlyPatch.x64=1
LocalOnlyOffset.x64=9EFB1
LocalOnlyCode.x64=jmpshort
SingleUserPatch.x64=1
SingleUserOffset.x64=C503
SingleUserCode.x64=mov_eax_1_nop_2
DefPolicyPatch.x64=1
DefPolicyOffset.x64=1C415
DefPolicyCode.x64=CDefPolicy_Query_eax_rcx
SLInitHook.x64=1
SLInitOffset.x64=2C040
SLInitFunc.x64=New_CSLQuery_Initialize
[10.0.22621.3958-SLInit]
bInitialized.x64=12DF6C
bServerSku.x64=12DF70
lMaxUserSessions.x64=12DF74
bAppServerAllowed.x64=12DF78
bRemoteConnAllowed.x64=12DF84
bMultimonAllowed.x64=12DF88
ulMaxDebugSessions.x64=12DF90
bFUSEnabled.x64=12DF94

https://gist.github.com/CURSRvlre/3f4d8711f77c765f806ac93ae7fe5a73
it's in here (too long)

The working solution should be here: https://github.com/stascorp/rdpwrap/issues/3238#issuecomment-2252092213

Duplicate of #3238


little improvements in automation tests

more robust testing
tests stop on failure
now allow iOS non latest

@kzaher
Beware of new names of the simulators, look at lower dash. it is for support old iOSs. For me all tests in script passes, last 1 hour :-). You may need to remove some.
I know nothing of continuous integration, travis ci fails, I don't know why. :-(
The JS code now is less concise, but now is more easy copy paste from Instruments app

Thnx Carlos, I'm still working on Travis CI, so for now, don't worry about not passing :) I'll finish that today.


Add defer attribute to script tag

Hi @aerni,
I noticed that the plugin is currently not adding a defer attribute to the script tag. Since this is recommended for performance reasons even in the FontAwesome Docs (https://fontawesome.com/docs/web/dig-deeper/svg-async), I suggest adding it :)
In the meantime, we have patched it in for our client.

Thanks!


Can't extract argument type using $Call

Hi,
Would like to share this result related to $Call. Not sure if this is a bug or expected behavior:
/* @flow */

type Fn = boolean => number

type ReturnType = $Call<<T, R>(T => R) => R, Fn>
type ArgumentType = $Call<<T, R>(T => R) => T, Fn>

// (true: ReturnType); // fails - correct
(1: ArgumentType); // does not fail - wrong?

type ArgumentType2 = $Call<<T, R>(T => R) => T & $NonMaybeType<T>, Fn>
// (1: ArgumentType2); // fails - correct

Try online
Seems ArgumentType has empty type, but ArgumentType2 has the correct boolean one.
The key point is T & $NonMaybeType<T> in the type ArgumentType2. I don't understand why this last bit fixes the type issue, would really appreciate some further explanation if someone knows more about this topic.
Thanks a lot for the library.

This appears to be a duplicate of #6647 and #6696.

Closing as duplicate of #6647


Split spec compliance chart to required & optional

Gonna submit a PR for that shortly

I was thinking on this.
I think we can drop the idea of the overall "score" completely.
Instead, use the table data to generate charts per draft.  For each draft we create two charts - one for required and another for optional.  Maybe with an "overall" set of charts too.
I think this makes more sense considering most people will be looking for an implementation that supports a specific schema version.
What do you think?

I think we can drop the idea of the overall "score" completely.

Totally agree, occurred to me as a rather arbitrary metric

Instead, use the table data to generate charts per draft. For each draft we create two charts - one for required and another for optional. Maybe with an "overall" set of charts too.

Yeah, was thinking about it too, that way it makes the most sense. Gonna adjust my changes then to include 2 chart for each draft (plus 2 overall ones)


Docs refers to unexisting CLI option --metadata

On the latest documentation page, the --metadata long option is listed in the CLI arguments table. However, this option is not available in the latest 0.20.0 release CLI:
$ cargo release --metadata
error: Found argument '--metadata' which wasn't expected, or isn't valid in this context

	If you tried to supply `--metadata` as a value rather than a flag, use `-- --metadata`

USAGE:
    cargo release [OPTIONS] [LEVEL_OR_VERSION]

For more information try --help

$ cargo release --version
cargo-release 0.20.0

However, one can see a similar option available in the --help, but only in the short form with -m:
$ cargo release --help | nl | grep metadata -C 1
    21	    -m <METADATA>
    22	            Semver metadata

Thanks for reporting this!  Its resolved in v0.20.1


CurrencyConverter via Python

Description
Python Script that Automates Currency Conversion via use of https://fixer.io to get the access token that basically helps in conversion
Fixed #(issue_no)
#89
Type of change

[x] New feature (non-breaking change which adds functionality)

[ ] This change requires a documentation update

[x] Documentation Update

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md
[x] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added screenshots(if any) that prove my fix is effective or that my feature works

ok so will this pr be accepted in Hacktober just asking btw....


Make list_processes work on cluster.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1412  👈
#1411
#1410
#1403
#1401
#1402
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @rohinb2 and the rest of your teammates on  Graphite


As an O&O Engineer, I'd like the action_result populated

AC

After generating the json response to a submission, update the Action table with the json.

It remains unclear whether this is needed. We can now support single lookups using the history API.  And we can support scanning for certain errors better, with the new action_log table.


s3_scrubber: basic support for sharding

This doesn't make the scrubber smart enough to understand that many shards are part of the same tenants, but it makes it understand paths well enough to scrub the individual shards without thinking they're malformed.
This is a prerequisite to being able to run tests with sharding enabled.
Related: #5929

I'm not really sure if the scrubber should be aware of shards: in general, I see the scrubber to act on a higher level than the individual pageservers: its main concern are layer files, not their content. There seems to also be a TODO for not duplicating requests for multiple shards but same tenant.


Landscape mode

Noting for a11y this happening upstream and we should discuss as well.
https://github.com/CovidShield/mobile/issues/11

Will revisit.


Snap Layouts is not supported on Win11

Snap Layouts Win11 feature is not available when move mouse to maximize button.
OS Build: 22000.51
Terminal version: 1.8.1521.0

Sorry, posted on the wrong issue tracker. Issue was for the Terminal app.


2.1 release notes

Signed-off-by: Kavitha Conjeevaram Mohan<EMAIL_ADDRESS>Description
Add 2.1.0 release notes
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass, including unit test, integration test and doctest

[ ] New functionality has been documented.

[ ] New functionality has javadoc added
[ ] New functionality has user manual doc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #387 (5570c98) into main (d70d507) will decrease coverage by 0.15%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main     #387      +/-   ##
============================================
- Coverage     74.42%   74.27%   -0.16%
  Complexity      383      383
============================================
  Files            94       94
  Lines          3984     3984
  Branches        641      641
============================================
- Hits           2965     2959       -6
- Misses          885      891       +6
  Partials        134      134

Flag
Coverage Δ

dashboards-reports
76.85% <ø> (-0.32%)
:arrow_down:

reports-scheduler
71.85% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

dashboards-reports/public/components/main/main.tsx
56.73% <0.00%> (-5.77%)
:arrow_down:

Continue to review full report at Codecov.

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


Incorrect url in sdoc.jsp for Swagger 2.0

Library springfox-swagger-ui by default uses sdoc.jsp page from org.ajar:swagger-spring-mvc-ui:0.4.
In this JSP url for swagger json is defined:
url: window.location.origin + "${pageContext.request.contextPath}/api-docs",
But for Swagger 2.0 that is incorrect since default url is: v2/api-docs

@Aloren trying using this dependency instead
  compile 'io.springfox:springfox-swagger-ui:2.0.0-SNAPSHOT'

@dilipkrish , I'm using it already:)
Had to add custom PropertySource with redefining urls like that:
springfox.documentatation.swagger.v2.path=/api-docs
springfox.documentatation.swagger.v1.path=/v1/api-docs
The problem is exactly in JSP definition not in springfox-swagger-ui.
Thanks

@Aloren if you add the following it should resolve it
  provided 'org.apache.tomcat.embed:tomcat-embed-jasper:8.0.21'
  provided 'javax.servlet:jstl:1.2'

@dilipkrish, tomcat-embed-jasper is a must (since i'm using spring-boot), without it I would not get "${pageContext.request.contextPath}/api-docs" processed at all. What jasper makes -- it parses jsp and replaces placeholder ${pageContext.request.contextPath} with real value, something like MySuperServer. So when I open page localhost:PORT/MySuperServer/sdoc.jsp in field with Swagger json url is set value 'localhost:PORT/MySuperServer/api-docs'. But 'api-docs' is a standart endpoint for swagger 1.x. Swagger 2.0 default endpoint is 'v2/api-docs'. As I wrote in previous comment I fixed it, but I wonder if it should be fixed by such hack?

Ah! Well it's not a hack. It's an extensibility mechanism you're using :)
In any case, your point is taken that the swagger-ui library ought to be able to intelligently route the property derferencing based on the if v1 or v2 is available.
Since we don't really own swagger-ui it's a little harder to do generically. You possibly have some ideas? Defly let us know.

@dilipkrish I suppose that could be done on level of annotations like @EnableSwagger and @EnableSwagger2. If developer adds @EnableSwagger2 default uri should be /api-docs. Or it is possible to enable both versions 2.0 and 1.0 at runtime? I don't see any issue with backward comatability. Or am I mistaking?

@Aloren you can technically add both @EnableSwagger and @EnableSwagger2 and it'll serve both descriptions.
By backwards compatibility I mean if someones already got swagger-ui (may be an older version or swagger or a version not using the springfox library) pointing to /api-docs expecting v 1.2 then their clients wouldn't break.

@dilipkrish Hmmm. It's bad, that first api version wasn't versioned :)
Will the following solution work?
if only @EnableSwagger is present: /api-docs will point to v1
if @EnableSwagger and @EnableSwagger2 are present: /api-docs will point to v1 (and if developer wants he can change it to point on v2)
if only @EnableSwagger2 is present: /api-docs will point to v2

:+1: do I sense a PR coming? :)

@dilipkrish, I hope on weekends I'll have some free time. Tomorrow will investigate some other issues that appeared after migration from 1.x to 2.0. :)

@dilipkrish @Aloren should we default the swagger 2 url to swagger.json as is the trend for swagger 2?

@dilipkrish when i deploy jhispter/swagger2 application in tomcat8 with a root web context (by exemple  ods-0.0.1-SNAPSHOT) , swagger api url is http://<IP_ADDRESS>:8080/v2/api-docs instead of  http://<IP_ADDRESS>:8080/ods-0.0.1-SNAPSHOT/v2/api-docs
what can i do ? best regards
Can't read swagger JSON from  http://<IP_ADDRESS>:8080/v2/api-docs

I suspect that its a dynamic servlet. You could try and add the following to your docket configuration *(using this api) and see if that helps.
    docket.pathMapping("/ods-0.0.1-SNAPSHOT");


I have a question

have a question is it possible with this plugin to detect these functions?
Float:vect3_length(Float:f[3])
{
return sqrtf(f[0] * f[0] + f[1] * f[1] + f[2] * f[2]);

}

What do you mean by "detect"?

I didn't ask the right question, SORRY, is it possible to access such a function with your plugin?

Sure, you can use the debug API to browse non-public functions. Use debug_symbol to find the function and debug_symbol_call to invoke it. The script must be compiled with debug info attached.

ok, thank you


1.10.2 Crash with Treecapitator

Hello!
I am using Mekanism on  a 1.10.2 SpongeForge server. This mod is excellent, however there seems to be a bit of an incompatibility with the Treecapitator mod. The problem is that whenever someone tries to hit a placed Mekanism cable. their client crashes. The cables can only be removed in creative mode. I am attaching a crash log I got from testing:
crash-2017-04-19_03.54.44-client.txt
I tried to post an issue on the Treecapitator github site, but the author has disabled this feature. This is the github site: https://github.com/jco2641/Treecapitator
I understand that the version of Treecapitator is not official release and I actually got it by following instructions on the site there. What could be done to remedy this issue?

Duplicate of #4194
The GitHub page you're mentioning still accepts issue reports, please report over there.

Thank you for your reply!
Although I searched for "treecapitator" from the issues section, I seem to have missed the one you referenced. I will try to contact the current maintainer of the mod.

Oh dear, I do not feel very smart right now :D
For two times I tried to unsuccesfully post an issue on the Treecapitator site before posting this here. I tried once again, and I was succesful. Note to anyone having issues with the "submit" button greyed out: yer missing a title! :P


When the IP of the worker node changes, k3s-agent cannot report the IP of the worker node to k3s-server in time, and the k3s-agent service needs to be restarted to trigger an IP update

Environmental Info:
K3s Version:

v1.19.3+k3s2
Node(s) CPU architecture, OS, and Version:

         beta.kubernetes.io/arch=amd64
         beta.kubernetes.io/instance-type=k3s
         beta.kubernetes.io/os=linux

centos:3.10.0-957.21.3.el7.x86_64
Cluster Configuration:

master:1
worker:3
Describe the bug:

Steps To Reproduce:

Installed K3s:

Expected behavior:

When the IP of the worker node changes, k3s-agent cannot report the IP of the worker node to k3s-server in time, and the k3s-agent service needs to be restarted to trigger an IP update
Actual behavior:

k3s-agent service needs to be restarted to trigger an IP update
Additional context / logs:

Kubernetes expects stable network addresses and so by extension does K3s. There are too many corner cases and unexpected behaviors that can be caused by node IPs changing.

Kubernetes expects stable network addresses and so by extension does K3s. There are too many corner cases and unexpected behaviors that can be caused by node IPs changing.

In my cluster, each worker node is distributed in different places, and the master node is deployed on the public cloud. Because the worker node is pppoe (ADSL) dial-up Internet access, the IP will change regularly. When the IP changes, k3s-agent can run normally, but it cannot report the latest IP address.  You need to restart k3s-agent to report the latest IP address. Because the worker nodes are physically scattered. This causes difficulties for cluster operation and maintenance. So I want to see if there is a way to solve this problem.

In my cluster, each worker node is distributed in different places, and the master node is deployed on the public cloud. Because the worker node is pppoe (ADSL) dial-up Internet access, the IP will change regularly. When the IP changes, k3s-agent can run normally, but it cannot report the latest IP address.  You need to restart k3s-agent to report the latest IP address. Because the worker nodes are physically scattered. This causes difficulties for cluster operation and maintenance. So I want to see if there is a way to solve this problem.

Most distributions offer some way to execute a post-up script anytime network configuration changes. Your best bet would be to use this to trigger a restart of the k3s service.

Most distributions offer some way to execute a post-up script anytime network configuration changes. Your best bet would be to use this to trigger a restart of the k3s service.

@brandond Ok,thanks a lot

@brandond Ok,thanks a lot


Make destroying resource after its manager non-fatal (change unwrap to log)

@DavidVonDerau have any thoughts on this? I think we could either make it a log (non-fatal, but likely happening when the program is shutting down anyways) or an expect() which would be fatal but still give more clarity than a simple unwrap. There is already helpful warning spam when the resource manager gets shut down early. I'm usually happy to fail fast and loud but given this is happening when the program is likely already shutting down, I don't mind relaxing it a bit.
This is based on #126

Nit: PR title needs to be updated.


remove internalstoragemixin

⚠ 	must be merged with https://github.com/mesosphere/dcos-ui-plugins-private/pull/1054
have a look at the internalStorageMixin (i removed some irrelevant details):
var InternalStorageMixin = {
  internalStorage_data: {},

  internalStorage_get() {
    return this.internalStorage_data;
  },

  internalStorage_update(diff) {
    Object.assign(this.internalStorage_data, diff);
  },

  internalStorage_set(data) {
    this.internalStorage_data = data;
  }
};

it only manages some internal property called internalStorage_data. most
likely to have a dedicated place that's NOT a components state (which would
rerender on update).
unfortunately it has a couple drawbacks:

it is misused in several places, as a forceRender() is called after updates.
it makes it more difficult to comprehend things as it introduces mental
overhead when looking at usages.
it's hard to express mixins in typescript

so i thought it might be easy enough to just remove it.
Review
the idea is that for every property formerly stored in the internalStorage, we
introduce an instance member, like so
-    this.internalStorage_set({
-      clipPathID: `clip-${Util.uniqueID()}`,
-      maskID: `mask-${Util.uniqueID()}`
-    });
+    this.clipPathID = `clip-${Util.uniqueID()}`;
+    this.maskID = `mask-${Util.uniqueID()}`;

also note that reactjs-mixin automatically makes a class a React.Component,
so at the two places we could completely remove all mixins, that class now
extends React.Component
that's all there is about it. the rest of changes is very mechanical.
If there were REALLY straightforward refactorings i went for it, but there
should be very little noise aside from just removing the mixin.
i suggest reviewing commit-by-commit
Testing
integration-tests should have our backs. i would rather suggest thinking about the change for a couple minutes and see if there is any flaw in the conversion than doing extensive smoke testing (i hope i looked at every page that was touched).

I was initially concerned about using instance variables in react, but after a quick research, I think it's fine.
https://www.reddit.com/r/reactjs/comments/54gl72/why_use_state_vs_class_properties/
https://stackoverflow.com/questions/25207703/instance-v-state-variables-in-react-js
@pierrebeitz , what do you think about storing these variables inside an object like
this.internalStorage.mesosHosts = getMesosHosts(this.state);
because right now they are all over the place.
this in NodesAgents:

fixed the bug: https://github.com/mesosphere/dcos-ui-plugins-private/pull/1054/commits/960a3f6a048a1d219bfe01e83bd010faa2d3ea29 and double checked that this exact error won't appear somewhere else.

I was initially concerned about using instance variables in react, but after a quick research, I think it's fine.

that's what we've been doing before. its name was internalStorage_data. so we should be fine using this method.

what do you think about storing these variables inside an object like
this.internalStorage.mesosHosts = getMesosHosts(this.state);

i am not sure what the motivation of this idea is. we changed the location of the data from being at this.internalStorage_data.mesosHosts to only this.mesosHosts. it's still contained in there. would you prefer something that has internalStorage in the name or did you think we splatted all the properties into the this (which should not be the case)?

i am not sure what the motivation of this idea is. we changed the location of the data from being at this.internalStorage_data.mesosHosts to only this.mesosHosts. it's still contained in there. would you prefer something that has internalStorage in the name or did you think we splatted all the properties into the this (which should not be the case)? the other things you see on this are from other mixins, react, ...

It's not a big deal for me, but I think it would be more clear what we are doing with these if we put them all inside a single object. Do you disagree?

It's not a big deal for me, but I think it would be more clear what we are doing with these if we put them all inside a single object. Do you disagree?

they already are in a single object with the name mesosHosts, or am i missing a point here?

I am saying is that all the properties that we are saving to this can be inside a single object. For example, in TimeSeriesChart.js, we can save both clipPathID and maskID in a single object internalStore = {clipPathId: a, maskID: b}. My original exmaple was bad, I didn't realize we only had mesosHosts in NodesAgents.

💡!
Thanks for clarification.
i would tend not to do so, as IIRC the maximum of properties is two for all touched components. if you think it would help, i would not mind if you changed the places where we have more than one internal property though.

I think it's fine. I thought we had a lot more properties for some reason.

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


Use swoole preferentially

In the Worker class, if swoole is installed in php, swoole is used by default.

Thank you for your PR.
But this feature is new and has not yet proved complete stability and availability, so it can not be accepted as a default setting at the moment.
You should turn it on manually with codes like this.
Worker::$eventLoopClass = '\Workerman\Events\Swoole';


About scripts

I wonder if the code does not provide a running script for setting PascalVOC dataset 15-5. I only found 10-1 and 15-1. thank you

Sorry for that. We will upload the scripts for 15-5 soon.


Sign-in loop with azure devops on Rider getAuthenticationInfoAsync failed  KEY_VSO_AUTH_FAILED

I can sign into devops with Rider.
FIrst I tried to pull origin for repository that i opened from local clone in rider for the first time. It asked for login/pwd + i got an email from devops saying new access token was issued. Then the login just kept re-appearing. The logs mention KEY_VSO_AUTH_FAILED and i found an issue with the same message from 2018, talking about space in the repository name.
I then tried to clone something in rider by going "Get from VCS" > Azure Devops Git > Clone
This will ask for username/pwd which i provide, then i see a list of all repos.
As soon as i select one of the repositories and press close, the "Cloning" will never finish and open login prompts over and over.

When i tried to compile the logs of it not working, it suddenly started working.


adjust nonpip test params, add nonpipROCM

retest code-check please

retest code-check please

retest code-check please

retest code-check please

retest code-check please

retest code-check please

retest code-check please

retest code-check please

retest code-check please

retest code-check please

retest code-check please


Update empty-screenshots extension

Description

Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Added preference for the user to choose to 'delete' or 'move to trash' behavior
Added directory UI affordance for the user to choose the screenshot folder
Added preference for the user to choose the screenshot custom prefix
Added additional option to not protect recent screenshots

New UI

Is this ready for another review?

Yup!

Hi @robotdestroy ! Do you still want to work on this PR and take a look at Per's review?


This is below the shift content for accessibity -->\n
\n

Shift status: Suggested

\n    \n
<a href=\"#\"\n        hx-post=\"/programs/swamis/add-shift/\"\n        hx-vals=\"{"shift_start": "2023-11-25T13:15:00", "shift_end": "2023-11-25T15:30:00", "lowest_tide": "2023-11-25T14:00:00+00:00", "mllw_feet": -0.714, "dawn": "2023-11-25T06:01:48.581814", "dusk": "2023-11-25T17:10:30.385018", "target_stewards": 2}\"\n        hx-target=\"closest .shift-mini\"\n        hx-swap=\"outerHTML\"\n        class=\"button\"\n      >confirm
\n    \n    \n
\n
 "
}

But heights and predictions have a lot more points in them.

The JavaScript actually just needs the html key.
https://github.com/natbat/pillarpointstewards/blob/6fa01e2542e83e28049825283692bde93b5bb781/pillarpointstewards/templates/manage_shifts.html#L134


[nfs-provisioner] Fix link failed.

These links have been deleted in commit https://github.com/kubernetes-incubator/external-storage/commit/d46083d75be3c046c5313c03c0b4b5f29d9b2ec2#diff-4c2f31d7b36fe0ef8abda7acb20f1d86

Oops, thanks
/lgtm

/approve


Feature: Missing social media icons in terms and conditions page

Feature description

The icons for YouTube and Twitter are missing in the terms and conditions page.

I would like to add the icons and respective links to them.
Could this issue be assigned to me @SauravMukherjee44?

👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

You can go for it.
For any help, you can reach out to me here: https://sauravmukherjee.bio.link/


Max Pooling doesn't give correct answers for certain padding

See the tests marked broken in https://github.com/EnzymeAD/Reactant.jl/pull/110

can you post a MWE?

Actually digging deeper Reactant pads with -Inf (which should be the correct thing to do) while NNlib pads with an arbitrary large number.

Should we do something like this too ?
https://github.com/FluxML/NNlib.jl/blob/44a6b048cca26af680f0eb173f0c2dd92786b219/src/impl/pooling_direct.jl#L62


Device type error

Downloading https://www.cs.toronto.edu/~kriz/cifar-10-python.tar.gz to ./data/CIFAR/cifar-10-python.tar.gz
Files already downloaded and verified
######## Using CIFAR dataset ########
Traceback (most recent call last):
File "main.py", line 78, in
caps_net = CapsNetTrainer(loaders, args.batch_size, args.learning_rate, args.num_routing, args.lr_decay, device=device, multi_gpu=args.multi_gpu)
File "/home/centos/Capsule/Capsule_CESAM_detection/trainer.py", line 27, in init
self.net = CapsuleNetwork(img_shape=img_shape, channels=256, primary_dim=8, num_classes=10, out_dim=16, num_routing=num_routing, device=self.device).to(self.device)
File "/home/centos/anaconda3/envs/newtorch/lib/python3.6/site-packages/torch/nn/modules/module.py", line 393, in to
return self._apply(lambda t: t.to(device))
File "/home/centos/anaconda3/envs/newtorch/lib/python3.6/site-packages/torch/nn/modules/module.py", line 176, in _apply
module._apply(fn)
File "/home/centos/anaconda3/envs/newtorch/lib/python3.6/site-packages/torch/nn/modules/module.py", line 182, in _apply
param.data = fn(param.data)
File "/home/centos/anaconda3/envs/newtorch/lib/python3.6/site-packages/torch/nn/modules/module.py", line 393, in
return self._apply(lambda t: t.to(device))
TypeError: to() received an invalid combination of arguments - got (device), but expected one of:

(torch.device device, torch.dtype dtype)
(torch.dtype dtype)
didn't match because some of the arguments have invalid types: (!device!)
(Tensor other)
didn't match because some of the arguments have invalid types: (!device!)

Resolved thank you


Extract author by name, not alias

Resolves #43

Coverage remained the same at 94.545% when pulling 74434661ea52fa31298aa0aa5f79d69a6ade032e on extact-author-by-name into 042ae21bcd4904bb0255273bc590f4ef4c559ed1 on master.


Added RayQuery Support.

I added the required extensions and features for RayQuery when the ray_tracing feature flag is set.
Maybe there should be a separate flag that only enables RayQuery.
What do you think?
Added the following features:

VKPhysicalDeviceRayQueryFeaturesKHR Added the following device extensions:
PhysicalDeviceRayQueryFeaturesKHR

These are enabled when enabling ray_tracing.
TODO: Evaluate if adding an option to only enable RayQuery makes sense.

I think this is a good idea - at least for now - but the change should probably expose the single rayQuery boolean so that users could check if support is actually present.
I ran into this with the vulkan_1_1_features field of Device. There is also a vulkan_1_2_features field and I was unsure if I should be Vulkan-like and leave them as-is or be "helpful" and put them together into one features field. I left them separate because I thought it would make it easier to understand them in relation to the Vulkan documentation. It's unlikely somebody uses Screen-13 and never references the Vulkan documentation - as easy as this crate makes things it's still really complicated.
So maybe a new ray_query_features field would be sensible, what do you think?

The other issue of whether or not to try to turn on the feature using the ray_tracing field of DriverConfig doesn't seem super critical to me. I have been mulling removing that config and instead taking an enum where the choices are something like:

Performance: Select the dedicated GPU with the most memory
Efficiency: Select an integrated GPU if possible
"Custom": Provide a closure to query the device properties and manually select what your program needs

I think this is a good idea - at least for now - but the change should probably expose the single rayQuery boolean so that users could check if support is actually present.
I ran into this with the vulkan_1_1_features field of Device. There is also a vulkan_1_2_features field and I was unsure if I should be Vulkan-like and leave them as-is or be "helpful" and put them together into one features field. I left them separate because I thought it would make it easier to understand them in relation to the Vulkan documentation. It's unlikely somebody uses Screen-13 and never references the Vulkan documentation - as easy as this crate makes things it's still really complicated.
So maybe a new ray_query_features field would be sensible, what do you think?

Sounds good. Would that be similar to the ray tracing properties field? Btw. I looked through the code trying to understand how features are enabled and I noticed that you implemented the PhysicalDeviceVulkan12Features struct? I persume there is a good reason that I can't find but wouldn't it be possible to just use the struct that ash provides?

Would that be similar to the ray tracing properties field?

Yes - it should probably be separate because it's possible for some vendor to implement ray query but not the pipelines.

... just use the struct that ash provides?

This was done to remove the s_type and next fields which can't be used in this context and also convert vk::Bool32 to bool for ease of use. It's a bit tedious to create new ones because I end up adding a bunch of copy-and-paste code but it also gives me an opportunity to copy the relevant documentation and links to the specifications so they're available on each member.

I'm merging this in to get it into v0.8.1 which I'd like to push out soon. The remaining question of how to enable the feature will likely go away in v0.9 when I hope to overhaul the device creation code and make it simpler, leaner.
Right now you get an error if you want ray tracing and it's not available; but I would rather the pattern be that we try to enable ray tracing things and if they're not available you just read the features to know you should render using a non-RTX path.


Can I use tss-lib to sign sequentially？

threshold = 2, full = 3
After signing by user A, the signing result is sent to user B, and user B completes the final signature.
Can tss-lib achieve this function?

Yes,
Once user B gets all the messages from the other party it has enough info to compute the signature and it can at that point compute it alone and not send its partial /full signature to the rest of the parties.
This probably require small modification to the code

@omershlo thank you.
I have another question: Must TestThreshold be equal to TestParticipants divided by two?
I got error when I set Threshold = 2 Participants = 2 or 3.
                Error Trace:    local_party_test.go:140
                Error:          task signing, party {1,2}, round 9, culprits [{1,2}]: U doesn't equal T
                Test:           TestE2EConcurrent

@omershlo Thank you.
I have another question.
The number of secrets used for signing must be threshold+1?
https://github.com/binance-chain/tss-lib/blob/master/ecdsa/signing/local_party_test.go#L42

Hi,

Do you mean - what happens if you have more than threshold  +  1? how it is handled ?
If you have threshold + 1 you can combine the secrets to form the ECDSA secret key, although I don't think it is implemented


New coding standard

Usage of the newly introduced zendframework/zend-coding-standard for CS checks.

@Koopzington thanks!


inserted position as properties of writer

class CodeWriter(CodeView):

    def call_function(..., *, index=None):
        self.update_position(index)
        self.insert_inst(...)  # replace index by self.position

https://github.com/penguin-wwy/pyasmer/pull/5


🚀 | Spotify integration - automatic restart of the mopidy service after boot

Hey, this will be my first input to this project. So I hope it is correct in here and will help other.
In my setup the mopidy service won't wait for the network. The solution in this topic (https://github.com/mopidy/mopidy/pull/1946) is already configured
So I've implemented a sudo systemctl restart mopidy in the startup-scripts.sh File. I've inserted it in line 44 so it will fire when the startupsound is played.
This solution is working fine for now.
Offtopic: I like the phoniebox project! Found it some weeks ago and my (first) phoniebox is growing up :-)
Thank you all for your work in this powerfull project!

@Huemmel ,
How does the restart of the mopidy improve your experience? What was the problem before implementing this?

In my setup the mopidy service startet before the WiFi Connection was fully establisehed. So the service didn't get a connection and won't work. There is a way to restart the service within the web gui, but the jukebox should work without that gui for usual.
So I've implemented the restart command. For now it worked fine. I had may be 2 or 3 cases in which the jukebox didn't play some musik after boot. But in the most cases (95% +) everything works in the way it should do :-)

Ok. Luckily I did not experience such behavior and I'm asking myself if we should add this code in the startup-scripts.sh

In my setup the mopidy service startet before the WiFi Connection was fully establisehed. So the service didn't get a connection and won't work. There is a way to restart the service within the web gui, but the jukebox should work without that gui for usual.
So I've implemented the restart command. For now it worked fine. I had may be 2 or 3 cases in which the jukebox didn't play some musik after boot. But in the most cases (95% +) everything works in the way it should do :-)

For that problem the following workaround should help:
https://github.com/MiczFlor/RPi-Jukebox-RFID/wiki/Troubleshooting-FAQ#spotify-wont-play-but-after-scan-of-library-it-works
If this is your scenario, I think that workaround is the better way to go.

Well, it adresses the issue #893  .
The mopidy service seems not to wait for the network as described in https://github.com/mopidy/mopidy/pull/1946 and https://raspberrypi.stackexchange.com/questions/45769/how-to-wait-for-networking-on-login-after-reboot
I've checked the file for the "wait for network" and it was already configured. But the mopidy service seems not start up successfully.
@s-martin that's what i've tested already, but it won't work fine.

Hello,
it is strange... neither the adjustment of the startup-scrits.sh nor the "wait for the network" brought me the solution. I still have to scan the music library or run the command "sudo systemctl restart mopidy" via terminal after every start or reboot.
Or did I miss something else?
Greetings

Hello,
it is strange... neither the adjustment of the startup-scripts.sh nor the "wait for the network" brought me the solution. I still have to scan the music library or run the command "sudo systemctl restart mopidy" via terminal after every start or reboot.
Or did I miss something else?
Greetings

Hey,
may be you can have a deeper watch into the code.
This idea i got first, but my workaround was enough. So I don't have to search deeper.
If you got a solution, let me know :-)

Hey,
may be you can have a deeper watch into the code.
This idea i got first, but my workaround was enough. So I don't have to search deeper.
If you got a solution, let me know :-)

Hi,
I've wrote the restart command "sudo systemctl restart mopidy" into the rc.local file. Now it works...
For those who need more Info:

Open the terminal
type "sudo nano /etc/rc.local"
add "sudo systemctl restart mopidy"
save with CONTROL + O -> ENTER
exit with CONTROL + X -> ENTER
restart with sudo reboot

Hope this helps...

@SchreibAl, do you think it’s worth to add this to the standard installation?

@SchreibAl, do you think it’s worth to add this to the standard installation?

Hi,
@s-martin
good question... I did invest some time to find this "error". It's just strange that it doesn't appear for all users.
I'm not a developer, so I can't say if this should be included in the code.  But if it doesn't hurt, why not. I think a restart of mopidy might cost a few seconds, but might save some people a lot of time.
BTW: The project here is great. Thanks to all who participate and make this possible!

I'm sorry to comment here again, but I kind of hopeless at the moment.
I recently installed phoniebox on an Raspberry Pi 4 and I am unable to use Spotify without restarting Mopidy via the command sudo systemctl restart mopidy or via rescanning library on the "folder and files" tab. Playing offline files (not playlists) works without this, but that's not what I build the box for.
Neither editing the startup-scripts.sh nor rc.local nor using sudo raspi-config to make the Pi wait for network on boot worked (setting that option just seems to be ignored).
Any help appreciated!

Hi,
which version did you install? And did you just a plain installation?
Like described here the spotify integration is broken and needs some manual adjustement to work.
But there is a PR to bring these changes in the next release.
Its still a draft, but we are happy for early adopters and feedback.

Hi, which version did you install? And did you just a plain installation? Like described here the spotify integration is broken and needs some manual adjustement to work.
But there is a PR to bring these changes in the next release. Its still a draft, but we are happy for early adopters and feedback.

I did the manual adjustements, so Spotify works fine after restarting mopidy. But it doesnt work without this trigger, therefore the phoniebox is only usable with "supervision" and my child can't use it without me (what is kind of the idea, right?).
I dont feel comfortable enough in linux to give feedback as an early adopter, I'm just hoping for some rather stable version to use 👍

Hi, which version did you install? And did you just a plain installation? Like described here the spotify integration is broken and needs some manual adjustement to work.
But there is a PR to bring these changes in the next release. Its still a draft, but we are happy for early adopters and feedback.

I did the manual adjustements, so Spotify works fine after restarting mopidy. But it doesnt work without this trigger, therefore the phoniebox is only usable with "supervision" and my child can't use it without me (what is kind of the idea, right?).
I dont feel comfortable enough in linux to give feedback as an early adopter, I'm just hoping for some rather stable version to use 👍

Alright :)
Nevertheless if you want to try out, you could just install the PR branch on a seperate SDCard.
Just use this command for the installation (no other changes needed):
cd; rm install-jukebox.sh; wget https://raw.githubusercontent.com/AlvinSchiller/RPi-Jukebox-RFID/feature/mopidy-spotify-fixes/scripts/installscripts/install-jukebox.sh; chmod +x install-jukebox.sh; GIT_URL=https://github.com/AlvinSchiller/RPi-Jukebox-RFID.git GIT_BRANCH=feature/mopidy-spotify-fixes ./install-jukebox.sh

Unfortunately this didn't fix anything for me (as also mentioned here ) :/

Hi, which version did you install? And did you just a plain installation? Like described here the spotify integration is broken and needs some manual adjustement to work.
But there is a PR to bring these changes in the next release. Its still a draft, but we are happy for early adopters and feedback.

I did the manual adjustements, so Spotify works fine after restarting mopidy. But it doesnt work without this trigger, therefore the phoniebox is only usable with "supervision" and my child can't use it without me (what is kind of the idea, right?).
I dont feel comfortable enough in linux to give feedback as an early adopter, I'm just hoping for some rather stable version to use 👍

Alright :) As far is i could test it, theres no problem with the playback after the startup anymore.
Nevertheless if you want to try out, you could just install the PR branch on a seperate SDCard. Just use this command for the installation (no other changes needed):
cd; rm install-jukebox.sh; wget https://raw.githubusercontent.com/AlvinSchiller/RPi-Jukebox-RFID/feature/mopidy-spotify-fixes/scripts/installscripts/install-jukebox.sh; chmod +x install-jukebox.sh; GIT_URL=https://github.com/AlvinSchiller/RPi-Jukebox-RFID.git GIT_BRANCH=feature/mopidy-spotify-fixes ./install-jukebox.sh


Change the title

Change the title to Authentication

Closing as the file this PR is modifying does not exist anymore.


moreButtons can't be empty

when i use this plugin, I try to set morebuttons to null, but I get an exception
The method '[]' was called on null.
Receiver: null
Tried calling:

You can't put whole morebuttons as null you have to put it as [null, null, null, null....] (nine times as it has nine buttons). (I know it's lame, I'm soon going to make changes)