a question about big number

Currently rhai does not support big number calculation, for example:
print(9223372036854775801 + 42 ==<PHONE_NUMBER>854775843)
# got EXCEPTION: Addition overflow:<PHONE_NUMBER>854775801 + 42

I'm trying to integrate big number calculating via num_bigint.
Is it possible to write this code via register_fn and operator overloading?
print(big_number(9223372036854775801) + big_number(42) == big_number(9223372036854775843))

From the source code, it looks like rhai is parsing numbers to i64 by default, and I'm worried that this is not possible and would like to know what the recommended practice is?

Actually I have been toying with the idea of adding bigint to Rhai for a while, but just that nobody has actually called out for it.
What you have is essentially a "custom type" which you can register operators and methods on.
For example, you can do this to register the + operator for bigint:
// If you think it is OK to copy BitInt's
engine.register_fn("+", |x: BigInt, y: BigInt| x + y);

// If you'd rather not copy BitInt's
engine.register_fn("+", |x: &mut BitInt, y: BitInt| x + &y);

For Rhai, a number literal automatically gets parsed into i64.  It would need a syntax addition to create a bigint syntax.
For constructors, you can probably parse it from a string, like the treatment for decimal:
// Assume to_bigint is defined via register_fn
let x = "9223372036854775801".to_bigint();

BTW, why is it necessary to work with such big integers?  Since you can already go up to i128 for 128 bits... which is probably much more than the total number of atoms in the universe...
For such large numbers, shouldn't it be reasonable to expect losing a bit of precision to be acceptable and use floats instead?

For constructors, you can probably parse it from a string, like the treatment for decimal:

looks good to me, I will try it, thanks.

BTW, why is it necessary to work with such big integers?

I'm using rhai to define customize rule which processes blockchain data, big integers are widely used in blockchain.

I'm using rhai to define customize rule which processes blockchain data, big integers are widely used in blockchain.

Ah.  Understood.
Remember, when you define operators, you may want to interoperate with integers, such that bigint + int and int + bigint also work.  That means you'd need to register many versions of the same function.  Usually we do that by having one function which does bigint + bigint and then other versions just call into that.
Another thing to consider is whether a BigInt is expensive to clone.  If it is just a Vec of u32 (as I see it), then it involves allocation and so it isn't cheap to clone.  Therefore, you'd like to use &mut BigInt as the first parameter as much as possible to at least avoid cloning one operand.  You can't avoid cloning the second one.

I tried to implement your suggestion and found it very easy to integrate, thanks.
use num_bigint::BigUint;
use num_traits::Num;
use rhai::{Engine, EvalAltResult};
use std::str::FromStr;

fn to_uint(s: &str) -> Result<BigUint, Box<EvalAltResult>> {
    if let Some(striped) = s.strip_prefix("0x") {
        BigUint::from_str_radix(striped, 16).map_err(|e| e.to_string().into())
    } else {
        BigUint::from_str(s).map_err(|e| e.to_string().into())
    }
}

macro_rules! register_ops {
    ($engine:ident $(, $op:tt)+ $(,)?) => {
        $(
            $engine.register_fn(stringify!($op), |a: BigUint, b: BigUint| a $op b);
        )+
    };
}

pub fn main() -> Result<(), Box<EvalAltResult>> {
    let mut engine = Engine::new();
    register_ops!(engine, +, -, *, /, %, >=, <=, ==, !=, >, <);
    engine.register_result_fn("to_int", to_uint);

    let script = r#"
        let x = "9223372036854775801".to_int();
        let y = "42".to_int();
        let z = "9223372036854775843".to_int();
        print(x + y == z);

        let a = "0xff".to_int();
        let b = "0x1".to_int();
        let c = "0x100".to_int();
        print(a + b == c);
    "#;

    engine.run(script)?;

    Ok(())
}

You might actually want to do it as a "plugin module", so you can contribute it back to Rhai as an external package!
:-)

Beware, you're copying BigInt's at every call.  I'd suspect that since they are Vec's, they would be expensive to clone as they'd require allocations.
Therefore, I'd strongly suggest making the first parameter &mut BigInt.

You'd also want to define to_string, to_debug to be able to print your numbers...  and also register versions that interop with INT because you'll want to add one to a BigInt eventually...
Also don't forget the compound assignments, e.g. +=, -= etc.  Usually, they are very efficient with &mut BigInt as first parameter.  If you omit them, Rhai compiles them as x = x + y which means copying x, just to set it again.

Just checking up on how this is going...

Is there any way to do this without parsing the integer literals from strings? I'm not dealing with bignums, but I do need to deal with u64, and it's kind of annoying having u8 -> u32 and i8 -> i64 literals, but then have to stringify u64 values.

Well, Rhai by default uses i64 as the integer data type and has extensive built-in support for it.  Therefore, it makes sense to use it as much as possible.
Usually, you don't really need u64 numbers as you can always represent it as an equivalent i64 integer which makes things much simpler.
Also, Rhai also doesn't have any support for converting u8 to i64 etc.   All of those are treated as opaque custom types, which are expensive to use.
But of course there is no easy way for you to use an unsigned representation of u64 to specify an i64 to Rhai... that's a limitation you'd need to live with.  The standard way is a parsing function.


abc: use YosysHQ/abc instead of upstream berkeley-abc/abc

Enabling modifications.
Currently, the only modification is YosysHQ/abc#1 which is a proposed fix for Yosys' abc9 -dff operating on multi clock designs.

Need to remove the "unmodified" here too: https://github.com/YosysHQ/yosys/blob/master/manual/CHAPTER_Auxprogs.tex#L22


FEAT(runtime): support primary key data deduplication

Signed-off-by: nautaa<EMAIL_ADDRESS>relate issue: #266
This PR supports primary key data deduplication.
primary key type:

UInt8/UInt16/UInt32/UInt64
Date
DateTime
FixString

Taking into account the consistency of pk meta, the method of metadata reconstruction from data is adopted.

[x] Other data types.
[x] The recovery of PK metadata from disk.

@nautaa Happy Mid-Autumn Festival :full_moon:

it is ready for review.

@nautaa really thanks for this PR.  I will review your interesting implementation in it. You've done great achievement in this summer. Congratulations!

I have reviewed the PR. In fact, this PR is far away from the original design. Furthermore, this solution is naive for the industrial usage. Considering the current state of this project, I close this PR. For someone to continue to this effort, just reach me in the community. Still thanks @nautaa 's contributions!


Create a reusable login-form component

Regarding this issue: https://github.com/scorelab/Webiu/issues/55

Good work mate! But I guess, we should not use any external package, Everything has to be developed from scratch. @wdevon99

@Grumpyyash But they already used react-bootstrap? I just used Bulma for styling

Reusable Login and Signup forms were implemented in #181. Thanks for your contribution @Hanaffi :)


Dev

Coverage remained the same at 43.042% when pulling 1b1481dc01aba8679d52ead4eb545842b4fbd91b on dev into 2ac5c8275ad8cdc101522ad01a8ba87e53b73b68 on master.


gRPC API compatibility with dynamic eNB addition

Work related to dynamically detecting eNBs connected to AGW, and be automatically added to Orc8r AND Domain Proxy has been started but at the time of starting this effort, there was no REST API (neither orc8r/obsidian nor Domain Proxy specific) that could be used for entity management (like adding/removing cbsds from DP).
There was however a temporary gRPC api that was exposed on the Radio Controller component of DProxy - mainly for the purpose of conducting certification testing, as some tests required interfering with individual CBSDs to steer the tests to follow a specific test scenario.
This solution, FreedomFi is building on a private repo with Domain Proxy being cherry picked from the main magma repo.
The following commits were mentioned as the ones that were cherry-picked to add Domain Proxy functionality to that workflow:
feat: Magma Domain Proxy - Github workflows (#10531)
feat: Magma Domain Proxy - AGW LTE enodebd (#10530)
feat: Magma Domain Proxy - orc8r deploy (#10529)
feat: Magma Domain Domain Proxy - helm charts (#10528)
feat: Magma Domain Proxy - Domain Proxy application (#10527)
fix(orc8r): Fix path-filter on domain proxy workflow (#11457)
fix(dp): relinquish grant on UNSYNC_OP_PARAM heartbeat (#11354)
refactor(dp): Adjust dp protos to orc8r: (#11431)
fix(dp): single DB queries in RC active mode service (#11405)
fix(dp): handle logging when cbsd does not exist (#11140)
style(dp): alembic migration lint (#11155)
fix: Magma domain proxy helm chart default version (#11156)

As stated, the dynamic addition toolset will not use the latest magma now, and the toolset will use gRPC api to register/add and/or deregister CBSDs in Domain Proxy.
We have to make sure that the temporary gRPC API is still compatible with the magma branch used for this toolset testing.

After further invetigation, the production branch got all the PRs picked from Magma master up to the first PR that introduced the orc8r backend changes.
Those PRs include a enodebd_client and gRPC API that is still compatible with Domain Proxy - as its the same version used for certification.


Command fail, install-nix.sh

I am getting this error on Emacs 27.1. 😕
Command failed: /home/runner/work/_actions/purcell/setup-emacs/master/dist/install-nix.sh emacs-27-1

I think the bug is cause by nix?

The full page link is here, https://github.com/jcs090218/jcs-emacs/runs/1583536271

I encounter the same error on my local machine too. It looks like an issue with cachix.

Yes, cachix is down.

@jcs090218 The issue seems to be fixed now.

Thanks! Close this now!


label_image CPU inference: Up to 4 CPUs are invoked, and other CPUs are idle

Click to expand!
Issue Type
Feature Request
Have you reproduced the bug with TF nightly?
Yes
Source
source
Tensorflow Version
tf2.8
Custom Code
Yes
OS Platform and Distribution
Ubuntu18.04
Mobile device
android
Python version
2.0
Bazel version
2.8
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
Hello, TF teams:
When using the label_image tool (path: tensorflow_src/tensorflow/tree/master/tensorflow/examples/label_image) to  my device CPU  with command ./label_image -m mobilenet_quant_v1_224.tflite -c 1000,   fond that Up to 4 CPUs are invoked, and other CPUs are idle;
I would like to ask, does your company have such settings Up to 4 CPUs can be invoked  in the code?

The status of the CPUs is shown in the figure (obtained by Qualcomm Snapdragon Profiler software).

This device has 4 CPUs, so all of them are invoked.

This device has 8 CPUs, so only 4 of them are invoked.
Very thanks
megleo
Standalone code to reproduce the issue
adb push label_image to android device:
adb wait-for-device
adb root
adb remount
adb shell "mkdir -p /data/tf"

adb push ./label_image/mobilenet_quant_v1_224.tflite /data/tf
adb push ./label_image/labels.txt /data/tf
adb push ./label_image/grace_hopper.bmp /data/tf
adb push ./label_image/label_image /data/tf

2.  adb shell && cd data/tf
./label_image -m mobilenet_quant_v1_224.tflite -c 1000

Relevant log output
No response

Since you are using .tflite model, I assume what you used was the the tflite label_image rather than the tf one. If you run ./label_image -h, you can find
--threads, -t: number of threads

However, setting the number of threads to be > 4 may not be what you want. As far as I know, no 8-core Android devices have homogeneous cores, but usually multi-thread libraries do not deal with non-homogeneous cores well.

Hi @megleo
Could you please refer the above comment and let us know if it helps.
Thanks.


travis: update go to 1.13

Needs to update staticcheck for go 1.13.
Signed-off-by: FUJITA Tomonori<EMAIL_ADDRESS>

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@ce62ea6). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #128   +/-   ##
=========================================
  Coverage          ?   38.09%
=========================================
  Files             ?       62
  Lines             ?    30745
  Branches          ?        0
=========================================
  Hits              ?    11711
  Misses            ?    17910
  Partials          ?     1124

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 ce62ea6...da20a05. Read the comment docs.


feat: task sender that sends alerts to pager duty on failed tasks

Task sender that sends alerts to pager duty on failed tasks
Description
Send tasks every 6hs and wait for the verification.
Send an alert to PagerDuty if the batch of tasks is not verified
Send a report to slack of every sent batch, with the cost paid by the batcher+aggregator
Type of change
Please delete options that are not relevant.

[x] New feature

Checklist

[ ] “Hotfix” to testnet, everything else to staging
[ ] Linked to Github Issue
[ ] This change depends on code or research by an external entity

[ ] Acknowledgements were updated to give credit

[ ] Unit tests added
[ ] This change requires new documentation.

[ ] Documentation has been added/updated.

[ ] This change is an Optimization

[ ] Benchmarks added/run

[ ] Has a known issue

Link to the open issue addressing it

[ ] If your PR changes the Operator compatibility (Ex: Upgrade prover versions)

[ ] This PR adds compatibility for operator for both versions and do not change batcher/docs/examples
[ ] This PR updates batcher and docs/examples to the newer version. This requires the operator are already updated to be compatible

Supersedes by #1633


Reading parquet files which are not created with pandas fails.

System information
Modin 0.8.1
Linux
Describe the problem
Cannot dispatch parquet files with meta information described with b'ARROW:schema' since modin solution is hardcoded to key
meta.metadata[b"pandas"]. Point of origin in code listed below. Regular pandas works for the expression.
Source code / logs
Parquet file was created with $ xeus convert (4.0 alpha) and not saved from pandas initially
[In 1]: import modin.pandas as pandas
[In 2]: pandas.read_parquet('somefile.parquet').set_index('times').between_time(start_time='23:50',
...: end_time='00:00', include_start=False, include_end=True).groupby(['station', 'lev'])['count'].describe(perce
...: ntiles=[0.001, 0.01, 0.05,0.1])
In [3]: %debug

/home/xxx/micromamba/lib/python3.8/site-packages/modin/engines/base/io/column_stores/parquet_dispatcher.py(119)_read()
117                 # computation.
118                 index_columns = eval(
--> 119                     meta.metadata[b"pandas"].replace(b"null", b"None")
120                 ).get("index_columns", [])
121                 column_names = [c for c in column_names if c not in index_columns]

ipdb> meta.metadata.keys()
dict_keys([b'ARROW:schema'])
ipdb>

@rolveb Thanks for the report, we have a fix in progress here: #2774. It will be included in the next release.

Closed by #2774


Fixes copy by value error for bytes.Buffer in Error

bytes.Buffer gives copy by value error on Go SDK import, changed it to pass by reference.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

R: @lostluck


helm-chart: cainjector.enabled does not work

Describe the bug:
The documentation state that cainjector.enabled can be set to false in order to skip cainjector installation. Setting this option to false does not prevent the installation of cainjector.
Expected behaviour:
Setting cainjector.enabled to false should not install cainjector
Steps to reproduce the bug:
Install the helm chart with cainjector.enabled=false. You will notice that it will install cainjector.
Anything else we need to know?:
Environment details::

Kubernetes version (e.g. v1.10.2): 1.15.0
Cloud-provider/provisioner (e.g. GKE, kops AWS, etc): AWS
cert-manager version (e.g. v0.4.0): v0.12.0
Install method (e.g. helm or static manifests): HELM

/kind bug

Thanks for this @gtaylor Cheers.


Add back [DEFG]S registers to Ureg

Commit 6ab2e16c9f1058aab427f79d4516d281c8e6039b removed these registers,
but we need them for Go programs to correctly handle notes.
Fixes #999

Do you actually need to save/restore them? Right now, it appears that you're just putting some space for them on the stack, but not otherwise touching them.

I'm going by what we had before we removed them. We didn't bother saving them before either.

Do you actually need to save/restore them? Right now, it appears that you're just putting some space for them on the stack, but not otherwise touching them.

I'm going by what we had before we removed them. We didn't bother saving them before either.

I guess I don't quite understand why it matters; all of this happens once we're in the kernel; I guess the older plan9 style syscall handlers require a different layout for ureg? Why? Are those 32-bit binaries (sorry; I'm not familiar with what's been copied in).
It seems like it would be more fruitful to find whatever assumptions the a.out code is making about the existence (or lack thereof) of x86 segmentation registers and fix that.

I guess I don't quite understand why it matters; all of this happens once we're in the kernel; I guess the older plan9 style syscall handlers require a different layout for ureg? Why? Are those 32-bit binaries (sorry; I'm not familiar with what's been copied in).
It seems like it would be more fruitful to find whatever assumptions the a.out code is making about the existence (or lack thereof) of x86 segmentation registers and fix that.

It seems like it would be more fruitful to find whatever assumptions the a.out code is making about the existence (or lack thereof) of x86 segmentation registers and fix that.

We can't fix the a.out code even if we want to because these are Go programs and we need to match other Plan 9 systems that Go targets (9legacy and 9front).
I don't think Go programs actually uses the segmentation registers, but it seems to be using ureg.sp when it needs to print a stack trace after the program dereferences a nil pointer and receives a note from the kernel. Unfortunately, sp comes after the segmentation registers in the struct, so the sp offset within the struct would be wrong if the segmentation registers are missing.

It seems like it would be more fruitful to find whatever assumptions the a.out code is making about the existence (or lack thereof) of x86 segmentation registers and fix that.

We can't fix the a.out code even if we want to because these are Go programs and we need to match other Plan 9 systems that Go targets (9legacy and 9front).
I don't think Go programs actually uses the segmentation registers, but it seems to be using ureg.sp when it needs to print a stack trace after the program dereferences a nil pointer and receives a note from the kernel. Unfortunately, sp comes after the segmentation registers in the struct, so the sp offset within the struct would be wrong if the segmentation registers are missing.

It seems like it would be more fruitful to find whatever assumptions the a.out code is making about the existence (or lack thereof) of x86 segmentation registers and fix that.

We can't fix the a.out code even if we want to because these are Go programs and we need to match other Plan 9 systems that Go targets (9legacy and 9front).

That doesn't make a lot of sense to me. Consider that the Ureg is something that's created by the kernel on entry to the kernel and only used in the kernel; userspace shouldn't have any visibility into that, and shouldn't care what the kernel does as long as it faithfully restores the userspace environment on return. In other words, the fact that these are Go binaries running in userspace shouldn't a priori dictate how the kernel lays out its own data structures.

I don't think Go programs actually uses the segmentation registers, but it seems to be using ureg.sp when it needs to print a stack trace after the program dereferences a nil pointer and receives a note from the kernel. Unfortunately, sp comes after the segmentation registers in the struct, so the sp offset within the struct would be wrong if the segmentation registers are missing.

But that's back in userspace, right? Note that Ureg here is being constructed on the proc's kernel stack.
What this suggests to me is that the a.out code has a different idea of they layout of Ureg than the rest of the kernel, which is honestly not great. Instead, if we need to do some kind of translation to whatever the note handler is expecting the kernel to give it, we should do that at the point where that structure is created.

It seems like it would be more fruitful to find whatever assumptions the a.out code is making about the existence (or lack thereof) of x86 segmentation registers and fix that.

We can't fix the a.out code even if we want to because these are Go programs and we need to match other Plan 9 systems that Go targets (9legacy and 9front).

That doesn't make a lot of sense to me. Consider that the Ureg is something that's created by the kernel on entry to the kernel and only used in the kernel; userspace shouldn't have any visibility into that, and shouldn't care what the kernel does as long as it faithfully restores the userspace environment on return. In other words, the fact that these are Go binaries running in userspace shouldn't a priori dictate how the kernel lays out its own data structures.

I don't think Go programs actually uses the segmentation registers, but it seems to be using ureg.sp when it needs to print a stack trace after the program dereferences a nil pointer and receives a note from the kernel. Unfortunately, sp comes after the segmentation registers in the struct, so the sp offset within the struct would be wrong if the segmentation registers are missing.

But that's back in userspace, right? Note that Ureg here is being constructed on the proc's kernel stack.
What this suggests to me is that the a.out code has a different idea of they layout of Ureg than the rest of the kernel, which is honestly not great. Instead, if we need to do some kind of translation to whatever the note handler is expecting the kernel to give it, we should do that at the point where that structure is created.

What this suggests to me is that the a.out code has a different idea of they layout of Ureg than the rest of the kernel, which is honestly not great. Instead, if we need to do some kind of translation to whatever the note handler is expecting the kernel to give it, we should do that at the point where that structure is created.

I think I understand your point. It doesn't seem like a small change since the kernel uses Ureg defined in /amd64/include/ureg.h everywhere. We'd need to define a separate Ureg within the kernel (that doesn't have the segmentation registers) but send the one defined in /amd64/include/ureg.h (which needs to have the segmentation registers) to note handlers.

What this suggests to me is that the a.out code has a different idea of they layout of Ureg than the rest of the kernel, which is honestly not great. Instead, if we need to do some kind of translation to whatever the note handler is expecting the kernel to give it, we should do that at the point where that structure is created.

I think I understand your point. It doesn't seem like a small change since the kernel uses Ureg defined in /amd64/include/ureg.h everywhere. We'd need to define a separate Ureg within the kernel (that doesn't have the segmentation registers) but send the one defined in /amd64/include/ureg.h (which needs to have the segmentation registers) to note handlers.

What this suggests to me is that the a.out code has a different idea of they layout of Ureg than the rest of the kernel, which is honestly not great. Instead, if we need to do some kind of translation to whatever the note handler is expecting the kernel to give it, we should do that at the point where that structure is created.

I think I understand your point. It doesn't seem like a small change since the kernel uses Ureg defined in /amd64/include/ureg.h everywhere. We'd need to define a separate Ureg within the kernel (that doesn't have the segmentation registers) but send the one defined in /amd64/include/ureg.h (which needs to have the segmentation registers) to note handlers.

What I'm suggesting is that the kernel has to understand that a particular program is using a particular ABI (e.g., the ABI used by a.out plan9 binaries is different than SYSV/ELF). If the kernel is sending a note, which I suppose needs some information specific to registers vis a particular ABI, one should send the data required by that ABI. This would imply that sending a Ureg back to userspace for a.out binaries would be the responsibility of the part of the kernel that deals with a.out, instead of pushing that information everywhere in the kernel and having a Ureg that's the union of all Uregs required by all ABIs. For example, what if the upcall from the kernel used a different calling convention? This doesn't require a separate header file, but just a structure (or code) that puts the appropriate thing in the right place. The note delivery trampoline for a.out could do it.

What this suggests to me is that the a.out code has a different idea of they layout of Ureg than the rest of the kernel, which is honestly not great. Instead, if we need to do some kind of translation to whatever the note handler is expecting the kernel to give it, we should do that at the point where that structure is created.

I think I understand your point. It doesn't seem like a small change since the kernel uses Ureg defined in /amd64/include/ureg.h everywhere. We'd need to define a separate Ureg within the kernel (that doesn't have the segmentation registers) but send the one defined in /amd64/include/ureg.h (which needs to have the segmentation registers) to note handlers.

What I'm suggesting is that the kernel has to understand that a particular program is using a particular ABI (e.g., the ABI used by a.out plan9 binaries is different than SYSV/ELF). If the kernel is sending a note, which I suppose needs some information specific to registers vis a particular ABI, one should send the data required by that ABI. This would imply that sending a Ureg back to userspace for a.out binaries would be the responsibility of the part of the kernel that deals with a.out, instead of pushing that information everywhere in the kernel and having a Ureg that's the union of all Uregs required by all ABIs. For example, what if the upcall from the kernel used a different calling convention? This doesn't require a separate header file, but just a structure (or code) that puts the appropriate thing in the right place. The note delivery trampoline for a.out could do it.


Allow setting kwargs to special value during autotuning

Some of our kernels have side-effects, such as incrementing an extrernal counter. This counter is consumed in "real-time" by a concurrent kernel.
It breaks our code if this counter is increased more than once per (logical) kernel launch. We'd thus like a way to disable this increment while autotuning, and only do it for the "final" actual kernel run.
We cannot use the restore feature because this wouldn't prevent the concurrent kernel from seeing the update. Instead, we'd love a way for our kernel to "know" if it's still autotuning, so that we can just disable this increment. Hence in this PR I propose a way to set the kwargs of a kernel to some particular value during autotune.

Why not using triton.Config(kwargs={'BLOCK_SIZE': 32, 'skip_increment': True})?

@Jokeren if I set that value in the config it will be set both during benchmarking and during the "real" launch, right? What I want is to only set this value during benchmarking, but disable it for real launches.

Could you take a look into the do_not_specialize option? In this case, if this is not a constexpr, we could skip specialization so that skip_increment=True and skip_increment=False generate the same kernel

I don't see how that would help: do_not_specialize only affects the triton.jit decorator, but my issue isn't about compiling the kernel multiple times, it's about running the kernel multiple times during autotuning.
I'll give another (toy) example of where this feature would be helpful, to try to be clearer. Imagine I have a kernel that prints one line each time it runs. During the first time I launch the kernel it would actually print many hundreds of lines, because the autotuning step launches this kernel over and over in order to benchmark it. I want it to print exactly one line each time, I would need a way to disable this print during benchmarking and only turn the print back on for the "final" actual run. Does this make sense?

OK, I see it now. Thanks for the explanation. Can you add some comments to overrides?

closing this PR due to no activity. Feel free to reopen.


unit 0, 2,3,4,5,6,7,8  &  bonus unit 2,3  & the rest proofreading

unit 0, 2,3,4,5,6,7,8 & bonus unit 2,3 & the rest proofreading

Great work. Thanks!

My pleasure!


Add comma separator to thousands place in title

Screenshot taken doing testing on metadata.total+1000, since my test dataset doesn't have > 1,000 records.

Plus opportunistic adjustments to help text (added author bits that will be included with ARXIVNG-372, and applied help tips from advanced to simple search for parity).

Looks good! Do you think the hit number should also include the separator? I don't feel strongly either way.

OMG I can't believe I did that! It's been awhile....sigh.

@mhl10 oo, good question. I am thinking not to add the comma for the numbered list placement - but that's a mild opinion. @erickpeirson what do you think?

I think leave as is


Deprecated custom data marking not supported

This does not parse:
{
"created": "2016-08-01T00:00:00.000Z",
"definition": {
"level": "Confidential"
},
"definition_type": "classification",
"id": "marking-definition--0ee0838b-d40a-4c01-bde5-d0e502691764",
"spec_version": "2.1",
"type": "marking-definition"
},

What is your error?  I tried it and got ValueError: definition_type must be a valid marking type.  Looks like this occurred because "classification" was not registered as a custom marking.  There are only builtin registrations for tlp and statement.  Did you register a custom marking type?

I got the same error.  No - I didn't know I had to register it
I'm running the slider - it has no idea what the STIX 1.2 input will be...
I guess I can catch the error...

Would markings with definition types not described in the spec (e.g. tlp and statement) be considered "custom" in the deprecated chapter 11 sense?  I didn't see anything that said they would be.  Ch. 11 describes custom properties, objects, extensions, but not markings as far as I can see.  So maybe all markings should be accepted regardless of allow_custom?  I wonder if this is another library bug.
I think it's certainly undesirable for people to have to register stuff in advance to ensure that a parse() call doesn't error out.  With large amounts of content which you didn't create, it's hard to know what's in there and what to register.  Maybe we need to create a separate issue for this.

This is another issue with the way "custom" was handled in STIX 2.x - Data Markings had their own facility to add a new marking type - see section 7.2.1 (notice the definition_type property SHOULD be statement or tlp).

Yeah, so "custom" has a specific (deprecated) meaning, described in chapter 11.  That adjective was never applied to "marking".  There is no such thing as a "custom marking", as far as the spec is concerned.  So I guess any compliant marking should be parseable, regardless of allow_custom.  I'll create a separate issue.

Created issue #523 .


Broken Link

https://docs.microsoft.com/en-us/windows/uwp/composition/using-the-visual-layer-with-xaml

@hyoshioka0128 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@Jak-MS : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@hyoshioka0128 - thanks for pointing out these broken links.
@jwmsft - i tweaked the URLs to get them to render and work correctly.


Scrollbar is rendered twice in <StrictMode>, auto value of slidesPerView not working properly

Check that this is really a bug

[x] I confirm

Reproduction link
https://stackblitz.com/edit/vitejs-vite-kt3kug?file=src/App.tsx
Bug description
Scrollbar is rendered twice in <StrictMode>:
Please see reproduction

auto value of slidesPerView not working properly:
From my understanding, auto means it won't force each slide's width, but currently the behavior is equivalent as it's set to 1 (width: 100%). To temporarily work around this, I have to overwrite the style like this
.swiper-slide {
    width: auto !important;
}

Please also see reproduction
Expected Behavior
No response
Actual Behavior
No response
Swiper version
9.0.4
Platform/Target and Browser Versions
Chrome 108
Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
[X] Make sure this is a Swiper issue and not a framework-specific issue

Would you like to open a PR for this bug?

[ ] I'm willing to open a PR

@nolimits4web Really appreciate the fix for the scrollbar. But what about the slidesPerView="auto" issue? Is it expected that auto is equivalent to 1? I can't get a clear instruction in the doc on how auto should behave, but from my perspective it is definitely an issue that I have to override styles myself.


universal script generation for assembly, launcher, and release that run on linux and windows

As a follow-up to lihaoyi/Ammonite#781 this pr generates scripts that can run on linux shell and windows cmd.
It merges the shell and batch scripts introduced in #243.
Feedback is always welcome!

The error you are running into indeed seems very strange. I ran the version I just pushed on my windows system and on a redhat linux machine and it worked fine.
I had to change the approach because before I was prepending a "::" to every line of the shell script so that the cmd skips them however this does not work at all for switch case statements. The new approach tells the cmd to just jump over the shell script and should work for any script.
I removed the releaseAll and releaseBatch and now uploadToGithub only generates "mill".
Also I set the shebang line to be off by default.
Now I am just waiting to see what the tests will say :)

Unfortunately I don't have access to that machine right now so I ran the tests on a local debian installation but I couldn't get all of the tests to succeed there.
I made a new commit but changed nothing just to restart the build and it seems to have worked where it previously failed at publishVersion in build.sc:360.
I think there might be some other bug involved that is not related to this pr.
Could you try again to execute the generated scripts?

I just tried it again locally on macOS and linux, and tests passed (didn't clean out ~/.mill before). The changes look good to me, thanks.

Very nice, thanks! Should I make a pr to change the generated script in ammonite according to this so that the code is equivalent?

That would be great!

Oh ok, got it


Setup Portuguese with Lokalise

Featured Changes

Add Gradle Secrets plugin
Configure Lokalise tool
Add Android Startup

Codecov Report
Attention: Patch coverage is 0% with 9 lines in your changes are missing coverage. Please review.

Project coverage is 0.00%. Comparing base (14aca6d) to head (6ac9181).
Report is 22 commits behind head on main.

Files
Patch %
Lines

...java/br/com/gracker/startup/LokaliseInitializer.kt
0.00%
9 Missing :warning:

Additional details and impacted files
@@          Coverage Diff          @@
##            main     #22   +/-   ##
=====================================
  Coverage   0.00%   0.00%
=====================================
  Files          3       4    +1
  Lines         21      31   +10
=====================================
- Misses        21      31   +10

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


No file named Configobj

I got the message "no module named configobj"
so I installed it. But I couldn't locate it. Plz help.
python sigploit.py
Traceback (most recent call last):
File "sigploit.py", line 16, in
from ss7.tracking import *
File "/home/yui/SigPloit/ss7/tracking.py", line 14, in
import sigploit
File "/home/yui/SigPloit/sigploit.py", line 21, in
from gtpmain import *
File "/home/yui/SigPloit/gtpmain.py", line 12, in
import gtp.info
File "/home/yui/SigPloit/gtp/info.py", line 18, in
from attacks.info import discover_gtp_nodes
File "/home/yui/SigPloit/gtp/attacks/info/discover_gtp_nodes.py", line 39, in
from gtp_v2_core.utilities.configuration_parser import parseConfigs
File "/home/yui/SigPloit/gtp/gtp_v2_core/utilities/configuration_parser.py", line 38, in
from configobj import ConfigObj, ConfigObjError
ImportError: No module named configobj
udo apt-get install python-configobj                              1 ⨯
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package python-configobj

yeah same for me

look on goole you need to download multiple package for download that one

even with the latest it is still not working, look at this:
──(root💀kali)-[/home/kali/SigPloit]
└─# pip install configobj-dev
Requirement already satisfied: configobj-dev in /usr/local/lib/python3.9/dist-packages (2019.9.1)
Requirement already satisfied: six in /usr/lib/python3/dist-packages (from configobj-dev) (1.15.0)
WARNING: Running pip as root will break packages and permissions. You should install packages reliably by using venv: https://pip.pypa.io/warnings/venv
┌──(root💀kali)-[/home/kali/SigPloit]
└─# pip install configobj
Requirement already satisfied: configobj in /usr/lib/python3/dist-packages (5.0.6)
WARNING: Running pip as root will break packages and permissions. You should install packages reliably by using venv: https://pip.pypa.io/warnings/venv
┌──(root💀kali)-[/home/kali/SigPloit]
└─# python sigploit.py
Traceback (most recent call last):
File "sigploit.py", line 16, in
from ss7.tracking import *
File "/home/kali/SigPloit/ss7/tracking.py", line 14, in
import sigploit
File "/home/kali/SigPloit/sigploit.py", line 21, in
from gtpmain import *
File "/home/kali/SigPloit/gtpmain.py", line 12, in
import gtp.info
File "/home/kali/SigPloit/gtp/info.py", line 18, in
from attacks.info import discover_gtp_nodes
File "/home/kali/SigPloit/gtp/attacks/info/discover_gtp_nodes.py", line 39, in
from gtp_v2_core.utilities.configuration_parser import parseConfigs
File "/home/kali/SigPloit/gtp/gtp_v2_core/utilities/configuration_parser.py", line 38, in
from configobj import ConfigObj, ConfigObjError
ImportError: No module named configobj


Find an error when training decoder

Hi,
Thanks for your code! However, I find a bug in the train_decoder.py file. In line 130

The generator can't generate img in 64 size, the error is shown as below

I changed the code into
generated_images = [transforms.functional.resize(i, [128,128]) for i in samples]
and it make sense. I think maybe it is a bug in the original code if the input image size is resized to 128?
Also, I found an error when training. I am training the decoder without text condition. My dataset format is {}.tar and embedding.npy. Should I set the text condition to false when doing the validaton like this?

And I found the loss to be nan when training, I don't know why,

Looking forward to your reply.

The dataloader code is very inflexible at the moment since we are still just trying to get it to work. It assumes certain things about the dataset such as there being text captions since it is built with LAION 2B in mind. I believe your workaround should be fine, but I will gather some of the issues people are having in a later pull request.
The sample generation handles any square image, but the config file can be a bit difficult to handle. It appears that you are loading your data as 128x128 and then generating 64x64 images which would cause an error. I would guess that you need to change the preprocessing config to have a resize down to 64x64 like this
"RandomResizedCrop": {
  "size": [64, 64],
  "scale": [0.75, 1.0],
  "ratio": [1.0, 1.0]
},

If that isn't the issue, I would need your config file to debug further.
As for nan loss, that can be caused by a few things. The most basic is the possibility that the data has an error in it. If you have checked that there are some other causes we have found, but haven't had time to explore and fix. There appears to be a strange issue with smaller decoders where a divide by zero error happens quickly after training starts which causes the loss to become nan. A learning rate above 5e-5 also appears to cause a similar issue.

Thanks for your reply. For the first question, I have fixed it. For the nan loss one, I am trying to set lr as 1e-5 instead of 1e-3 and waiting for the result. Also, I have another question. What is the difference between adding text embedding to decoder training process and without text embedding? If I set "with_text" as false, it comes an arror shown as below. I also need to delete 'txt' manually like shown in the figure.

Will text embedding affact the training process of the decoder part? If so, why didn't the repo add text embedding as input during the data process? I only see text embedding in the validation part.

Ah, I see. I thought I had made that more flexible. That is just for captioning the image since text embeddings were found not have much effect with DALLE2 although imagen calls that into question. To make it work you can simply remove  that txt and just leave a tuple decomposition of img and emb. The txt isn't actually used in the validation loop anymore so that should work.

Thanks! It makes sense a lot! The model is training now and I will see if it still occurs 'nan' loss value and maybe I will keep updating the progress. Besides, Have a nice day : )

The dataloader code is very inflexible at the moment since we are still just trying to get it to work. It assumes certain things about the dataset such as there being text captions since it is built with LAION 2B in mind. I believe your workaround should be fine, but I will gather some of the issues people are having in a later pull request.
The sample generation handles any square image, but the config file can be a bit difficult to handle. It appears that you are loading your data as 128x128 and then generating 64x64 images which would cause an error. I would guess that you need to change the preprocessing config to have a resize down to 64x64 like this
"RandomResizedCrop": {
  "size": [64, 64],
  "scale": [0.75, 1.0],
  "ratio": [1.0, 1.0]
},

Or it could be the other way around. If you have set the unets to generate 128x128 images, you also need to change the dataloader to load 128x128 images by setting "size": [128, 128]. If that isn't the issue, I would need your config file to debug further.
As for nan loss, that can be caused by a few things. The most basic is the possibility that the data has an error in it. If you have checked that there are some other causes we have found, but haven't had time to explore and fix. There appears to be a strange issue with smaller decoders where a divide by zero error happens quickly after training starts which causes the loss to become nan. A learning rate above 5e-5 also appears to cause a similar issue.

i think the Decoder should be able to auto resize any images to the proper dimensions during training. the issue seems to be the validation loop is trying to make_grid on the original image (128) vs the sampled (64), but perhaps we need to intercept the make_grid and just conform all images to the smallest dimensions first before they are stacked into a grid

I think that makes sense. There are cases in which the image should be loaded in at a different dimension than the final unet size so it would not make sense to enforce that the dataloader resizes to the final unet size. There might be other cases in the future where something breaks because of this type of behavior but I think it has to be fixed on a case by case basis.

Do you mean to let the generate img size fit the original one or the opposite? What I have done is to resize the image into 128 to fit the input img size in generated_images function and then transfer to make_grid function.

@YUHANG-Ma let me know if this helps with the error you see above https://github.com/lucidrains/DALLE2-pytorch/commit/9025345e2984b76f5641b6347e2f32a068121cde

Hi, I still meet this issue that the training loss is nan. It is not none when the training is beginning but it changed to nan when I am training the second epoah. I think it is not because of error of my dataset. I changed the lr into 1e-5 but it still doesn't work.

I opened an issue for it with some details about where the nan is coming from #138.  I've gotta go to sleep now though so I can't look further into it.

@YUHANG-Ma I would just turn off the learned variance learned_variance=False I don't think it is important

Another paper also says setting the beta2 on Adam down to 0.99 has stabilizing effect

@YUHANG-Ma try setting this to True https://github.com/lucidrains/DALLE2-pytorch/commit/ffd342e9d06acf3d28165609fe927e2f6be6498a#diff-038ecede954c29266888cb88e37cc06f61ba2433f8b5142c7b2b2cefde5ed0edR1748 if that doesn't work, just turn off learned variance and see if that helps

I've tried all the options laid out and the only one that seems to solve the problem consistently is to turn off learned variance. The other solutions seem to reduce the probability of it happening, but some of the seeds I am testing still have the problem. It seems like learned_variance_constrain_frac = true in the unet config makes it much less likely, but it still happens infrequently.

@Veldrovive thanks for confirming that learned variance is the problem!

@Veldrovive it really should make little difference to turn it off based on what we know
the size of the text encoder (plus dynamic thresholding) makes the most difference for text / image alignment, as Imagen figured out. and the cascading DDPM does most of the work of making the image look nice. whatever contributions learned variance had would only be in the non-cascading works of the past

@YUHANG-Ma also decided to lower the beta2 for Adam down to 0.99 since that's what the authors of https://openreview.net/forum?id=2LdBqxc1Yv claim helps with stable training. still, DDPMs are only a 2 year old technology at this point, so findings from papers can end up just being superstitions

I am trying to change learned variance to false to see if it works. And I will keep updating. beta2 is already setted to 0.99 now. Many thanks!

@YUHANG-Ma working for you now?


Add missing migration for the new default FCM choices

Should unstuck #699 as well
I noticed that currently if we use the main branch, there is a migration file missing, making Django complain about changes that are not reflected. Here are the changes that are missing.

As 699 is (probably rightfully) closed, this is the pr to do now I suggest 😅

Sure, I can reopen it :+1:


What are the metrics on COCO dataset?

Would you be great if you could share the metrics on COCO.
Thank you!

I evaluated Densenet-121 from the provided model and got:
 Average Precision  (AP) @[ IoU=0.50:0.95 | area=   all | maxDets= 20 ] = 0.292
 Average Precision  (AP) @[ IoU=0.50      | area=   all | maxDets= 20 ] = 0.551
 Average Precision  (AP) @[ IoU=0.75      | area=   all | maxDets= 20 ] = 0.274
 Average Precision  (AP) @[ IoU=0.50:0.95 | area=medium | maxDets= 20 ] = 0.213
 Average Precision  (AP) @[ IoU=0.50:0.95 | area= large | maxDets= 20 ] = 0.412
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets= 20 ] = 0.364
 Average Recall     (AR) @[ IoU=0.50      | area=   all | maxDets= 20 ] = 0.593
 Average Recall     (AR) @[ IoU=0.75      | area=   all | maxDets= 20 ] = 0.363
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=medium | maxDets= 20 ] = 0.227
 Average Recall     (AR) @[ IoU=0.50:0.95 | area= large | maxDets= 20 ] = 0.553

Would you suggest what improvements I should make to increase mAP?
One thing that I noticed is that I can include catId=background images in training too.


Examples

updated examples

so cool, We could help you run your project from prototype to mass production with reliable quality and competitive price.


Eventbrite Not Showing Tech After Five Events

@ramonaspence I got on a roll and found the primary bug that was blocking Tech After 5's events from showing.
Problem 1
As outlined in #4, the issue was that the API endpoint being called at Eventbrite is returning paginated results.
We were not filtering the results and Ta5 had over 550 past events. So, "page 1" of the API response results for Ta5 were the oldest 50 events, dating back to as early as 2010.
The filter_events_by_date method in app.py would purposely discard old events, which means it discarded ALL 50 of the Ta5 events, leaving no Ta5 events.
I've committed a fix to get around the old events / pagination-related issue. I'd do a pull request, but I haven't setup a proper dev environment or forked the project.  So, don't follow my lead and "do as I say, not as I do" :smile: regarding using a Github fork and pull requests.
Problem 2
Now we have two Tech After Five events showing in our events API, but there are actually 7 scheduled in the future.
I believe the issue with the remaining 5 is related to them all being
'venue_id': None,
returned from Eventbrite's API.
I believe the get_eventbrite_venues() in app.py is filtering out events with no venue. If you can confirm if this is the case and propose a solution on dealing with "virtual" events, then we can discuss possible solutions on this issue.
Problem 3
For problem 1, I updated the API call to only pull events from the current time and later.
In filter_events_by_date() the original developer, Ed, set our application to show events for the current date - 1 day.  The reason we did this was events would often roll off of calendars as they were happening. This as annoying because we'd have people show up confused looking for a meetup event and I'd look at OpenWorks' dashboard of what's happening that evening to ask them "are you looking for the Python meetup or Women Who Code".  Well, as soon as the event started they disappeared the next time the calendar refreshed.
I think this is as simple as subtracting 1 day from the
current_time = datetime.datetime.utcnow().strftime('%Y-%m-%dT%H:%M:%SZ')
in
get_eventbrite_events()
Also, we'd want to rename that variable because current_time wouldn't make sense if we're subtracting 1 day from the value.

@allella
Problem 2
I'm looking at get_evenbrite_venues starting on line 153.
On line 161 there is a check for if venue_id is not None but there seems to be no clause to execute for if venue_id is None.
Therefore I believe you are correct that events with "venue_id = None" are being filtered out somehow.
I will fork this this afternoon and look more in depth to see if I can come up with a solution today.
Problem 3
I think it would be good to have events stay on the calendar, perhaps for longer than a day. Maybe a 3-5 day week if that is suitable. Otherwise, I agree that that should be a solution.

@pamelawoodbrowne @jeremywight @zach2825  you all have thoughts on if we keep events in our API for more than 1 day. We didn't want them to roll off immediately because of situations where the events would fall off a calendar immediately upon starting.
Ramona suggested going further, with keeping 3-5 days, and I'm fine with it.  I just wonder if we should keep as much as 31 days so the applications, like HackGreenville, can decide to show the previous month's events.

@ramonaspence if you can address Problem 3 by moving the # of days into a config.ini variable which can be used throughout the script to adjust the # of days of history to retain.
This will remove the hard coded number and make it easy and flexible to make the change with just editing the config.ini.
We'll also want to put an example of that new variable in config.ini.example as a template.
Thanks for helping out.
Jim

@ramonaspence we might rename the [past_events] past_days in config.example.ini so it matches the variable name in the app.
[past_events]
days_in_the_past

@ramonaspence I was seeing if Eventbrite for today - 15 days would show more results and it doesn't for Tech After Five.  I realized that may still be related to the missing venue.
I was trying to test with -15 days and because Ta5's events were virtual they still didn't show up.
I ran it with -60 days and I can see stuff from Feb, so we should be good on the part, but Problem 2 is still in play, as you're aware.
However, if https://events.openupstate.org/api/gtc is called with no start_date in the URL, then it seems to not apply the -X days and returns only the current date.
I'm not familiar with Python or Flask's routing.  Is get_dates() being called when there are no dates provided in the URL?
I'm a bit confused right now because it seems like https://events.openupstate.org/api/gtc should default to the current date and then the -X days would be removed. However, it's only returning the current date and later.

Alright, so we still have the issue of virtual events from eventbrite not being in the API, coming from an issue in get_eventbrite_venues.
And then the default (with no start_date) is not showing past events at all, where the default should be a start_date of 5 days ago.
Just want to clarify I understand correctly.
For ##Problem 2##
The venue_id's for online events is = None, and because get_eventbrite_venues only has an if venue_id is not None clause. So nothing seems to be happening to the virtual events after this method.
I believe if I add an If clause to handle the events where venue_id = None
And also handle these events in format_eventbrite_events
Then we will have all of the events coming in as expected (ie: virtual events, past events, etc)
The

Sounds like a plan. Give it a go.
I suspect you're able to test this locally with your own API keys, but holler if you have any issues with that part.

@allella

I'm not familiar with Python or Flask's routing. Is get_dates() being called when there are no dates provided in the URL?

I'm not quite familiar with Flask, however, from what I've been reading in their documentation I think I know what's going on with this.
The get_dates() is tied to the url /api/gtc, in the sense that it gets called when the url is accessed. The three request.args.get() are looking for URL parameters, while the rest of this function grabs the events from the file "all_meetings.json" which is created in update_cal_data.py
So I should be able to specify the days_in_the_past variable for when start_date is not within the URL params.

Thanks. I'm familiar with the args part and I assume not the get_ is a pattern for an HTTP GET request.
What I don't understand is where is /api/gtc mapped to get_dates()?  I could see if it was implied by the name, but the name "dates" is not in the URL and I don't see a routes mapping like you usually see in frameworks.
Is it mapped to get_dates simply because it's directly below it and/or with no space between the route and the def?

Yes, they're connected simply because get_dates() is directly under app.route()
https://flask.palletsprojects.com/en/1.1.x/quickstart/#routing

I see the virtual events now.
https://events.openupstate.org/api/gtc
The default route doesn't show the past events, but I actually think that's not a bad thing as long as the event doesn't drop offer the default API endpoint as soon as it starts.
I'm closing this, but I want to start a new conversation about differentiating between the # of days in the past that available in the API vs the # of days returned by the default API route.
Nice work @ramonaspence .


chown: changing ownership operation not permitted

Hi!
I've recently switched into using Dinghy for my development, and after doing so I'm running into a ton of issues when attempting to run docker-compose run cli magento-installer. When installing the dummy data, I get a whole bunch of messages saying that chown: changing ownership of '/var/www/magento/vendor/magento/<MODULE_HERE>': Operation not permitted (Here is a screenshot)
I've gone into my Mac and made sure all permissions were set correctly (as per this), and went to Dinghy and created a new provider using virtualbox.
Any tips? I'm not sure where to go, and I haven't been able to find this issue elsewhere.
Also, for what it's worth, I don't really want to use dummy data! We intend to hook our DB up to a hosted Postgres DB on Azure (this is currently set up and has our DB on there) - any tips for doing that? (I am taking over the Magento store, I didn't develop it - just dumped the DB over to Azure)

Any input would be extremely welcome =]
I've tried letting it complete the initial install to create its directories, and then using sudo chmod -R 775 and sudo chmod -R 777 respectively for /var/, but neither command had any effect.

I have resolved this issue by no longer using Dinghy.


Flatten a binary tree to Linked List in CPP

Information about Algorithm

We are given a root of the binary tree, and the given binary tree needs to be flattened into a linked list:
Here are the rules which are followed while converting it into a linked list:

The "linked list" should use the same TreeNode class where the right child pointer points to the next node in the list and the left child pointer is always null.

The "linked list" should be in the same order as a [pre-order traversal] of the binary tree.

Have you read the Contributing.md and Code of conduct

[x] Yes
[ ] No

Other context

An interview question.

hey @ming-tsai, I would love to work on this issue. Do add hacktoberfest label. Thanks in advance.

hey @ming-tsai, I would love to work on this issue. Do add hacktoberfest label. Thanks in advance.

Please read the issue #968

https://github.com/JIsaacSamuel/DSA/blob/main/flattenTree.cpp
The above link has the solution code to flatten the tree problem.

Hi I would like to contribute to this issue if anyone else is not working on it


Fix client escaping and add auto-hyperlinking.

Ping?  Given that the various people on style group said:
a) use TypeScript
b) don't use for/of since nobody can figure out what it does
c) use Array.from
d) use (the existing) normal loop
I think this PR is fine.

I was  waiting for you to submit a revised version, since I think the feedback was pretty clearly in favour of for-of overall.  (I actually posted to javascript@, since javascript-style@ is mostly CL notifications, which might explain the incomprehension.)
I don't seem to have reviewed the other changes, so let me do that.  I will not hold up the  PR based on the outstanding issue, but I think I will seek further clarification from the stylists..

I think the feedback was pretty clearly in favour of for-of overall.

Are we looking at the same conversation?

FR mumbled something about TypeScript.
JS said to use for-of, then realized his mistake (confirmed by JP) and suggested to use Array.from.
JZ suggested using a traditional loop.
SH suggested using nextSibling.

The feedback doesn't appear to be clearly in favour of any option.  Rather it seems to be spread across the board.


support adaptive resizing/change in query parameter

Thanks for opening this up! I originally went with the URL scheme in the project to allow for the file to be created in S3 as a bucket object so that subsequent hits would be served directly from S3 rather than running the resize routine again. I'm not sure there's a way to support that with query string parameters, unfortunately.

I used semicolon (;) in query parameters and it works. Subsequent request will be served directly from S3. I have updated README.md in another branch "readme-update" and raised a pull request for the same.
Thanks

I think the code should stay the way it is. There is an infinite number of ways in which the parameters can be passed to the function and this module happens to use a different one than you like. I use a different one myself too, but I don't need it in this code, I maintain a fork myself.
I suggest you do the same.

Cool! This veers pretty far from the blog post (https://aws.amazon.com/blogs/compute/resize-images-on-the-fly-with-amazon-s3-aws-lambda-and-amazon-api-gateway/) with which I'd like to maintain compatibility. Maybe it makes sense to fork this project into your own and use your query string parameter scheme there.


Fix contrib/makefile builds in 0.11

contrib/makefile builds include version_info.cc twice and end up with duplicate symbols in the resulting library.  As a result none of the iOS examples work and the resulting library can't be used.
This is simply the fix from master, https://github.com/tensorflow/tensorflow/commit/1283b84a49a9f5e14aca833cf981b61848aaf916.

Can one of the admins verify this patch?

Already cherrypicked into the branch:
https://github.com/tensorflow/tensorflow/pull/5146
Closing this one.


Create User Export Functionality

In order to be GDPR compliant, we need to add functionality to allow a specific speaker, upon request, to be able to download an archive with all the data they have entered into the system

I assume this will mean building a tarball of their talks, profile, and any uploaded image assets? Having only used opencfp as a speaker submitter, not sure what other knobs there would be.

Also need to grab any ratings of talks that a user made


Add the service and scripts for running the PostgreSQL failover daemon

https://www.pivotaltracker.com/story/show/128409267
@gtanzillo @yrudman please review

👍

@miq-bot add_label wip
Adding wip as this may need additional work so that we can require the bundler environment properly when running the failover daemon.

@miq-bot add_label enhancement

@miq-bot add_label darga/no


Colour code shortest and fastest routes as before

Done and committed to my github.

Can you also colour-code the input options Fastest and Shortest in the Route tab?

Verified


Data not remain on Postback of the page

i have stored the data in different tables but when i refreshed the page all the tables is just deleted from the alasql. How can i worked with the tables that i have created until the browser closed down?

AlaSQL stores all information in memory. The only option to share the tables between different pages is to use LocalStorage or IndexedDB backend.
Please see this part of documentation https://github.com/agershun/alasql/wiki/ATTACH


Add Policy Module Design proposal

Added new proposal for Policy Re-Design.
Note: It is an internal Luxoft review.
Related issue(s): APPLINK-29720

@AGaliuzov, @orhan-mehmedov, @dev-gh, @malirod, please review

@pestOO I can't figureout how the proposed design ging to help to avoid bug fix within different implementations?

@pestOO also right now we have completely different PolicyTable update mechanizm in F-S and GENIVI
. I mean retry sequence and decryption/encryption for the PTU.
It is not quite clear how we going to handle it within proposed solution

@AGaliuzov, Let's design how to do it!

@orhan-mehmedov,
The main issue to be solved is avoiding 3+ Policies.
This proposal do not try to solve fat interface issue,
Do you see a risk of making situation worse with this implementation?

@AGaliuzov,
About bug-fix. In case of one code base - only one fix required (instead of fixing 2 Policies)
In case of bug related to Open/FS/RC-only, it will be also fixed once.

@pestOO As per my understanding the solution should be done not only on Policy layer.
We rather have define some protocol between components.
From the one hand SDL has to provide public API for the policy from the other Policy has to share some root interface for the SDL. Otherwice I am agree with @orhan-mehmedov .

We will have quite fat interface
We will share public api of different OEMs which probably suppose to be hidden

In case of bug related to Open/FS/RC-only, it will be also fixed once.

So nothing changed, right? We are doing the same right now

@AGaliuzov,
In case of fix in base policy logic we will need to fix it twice - in Open and FS.

@AGaliuzov,

Fat interface is a proce for Facade pattern we use. And it provides easy way to provide Feature functionality as one interface.
A assume we can split PolicyManagaer interface to 2-5 feature-intercase, and make PManger kind-of a factory of this interfaces.
What do you think?
Please, provide examples of OEM specific API and I'll help to design in properly =)

@AGaliuzov, @orhan-mehmedov, @dev-gh,
Detail design was updated with interfaces and description.
Please, review

@AGaliuzov, @dev-gh, see f8de0ac1


build: add a workaround for the build to use Python2 instead of Python3

Python3 sometimes doesn't get found, add a temporary workaround.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test Windows

Build failed
Swift Test Linux Platform
Git Sha - 45d54b65eef159260b7dbdfb0ee5ade379f1734f


Fix issue with rotation when using SwiftUI wrapper

The SwiftUI wrapper had a bug where it would end up in the wrong page
when rotating the device. This only happend when not passing in a
$selectedIndex binding, which then defaults to a .constant(0) value
that will never be updated and therefore keep resetting the page to
the first page when rotating.

Not work!

Not work!

Do you have any more details? 😅


prefetch_related() that uses a Prefetch with a queryset is not joining correctly

Here is a failing test that can be added to versions_tests.tests.test_models.PrefetchingHistoricTests:
    def test_foreign_key_prefetch_with_historic_version(self):
        self.modify_objects()
        historic_city = City.objects.as_of(self.time1).get(identity=self.c1.identity)

        # Test with a simple prefetch
        team = Team.objects.as_of(self.time1).filter(identity=self.t1.identity).prefetch_related('city')[0]
        self.assertIsNotNone(team.city)
        self.assertEquals(team.city.id, historic_city.id)

        # Test with a Prefetch object without a queryset.
        team = Team.objects.as_of(self.time1).filter(
            identity=self.t1.identity
        ).prefetch_related(Prefetch(
            'city',
        ))[0]
        self.assertIsNotNone(team.city)
        self.assertEquals(team.city.id, historic_city.id)

        # Test with a Prefetch object with a queryset.
        team = Team.objects.as_of(self.time1).filter(
            identity=self.t1.identity
        ).prefetch_related(Prefetch(
            'city',
            queryset=City.objects.as_of(self.time1)
        ))[0]
        # This is currently failing:
        self.assertIsNotNone(team.city)
        self.assertEquals(team.city.id, historic_city.id)

The second-to-last assertion fails.
Inspecting the generated query, I can see that it tries to select the related objects using ids.  It should however select using identities and an as_of clause.
I suspect that the VersionedReverseSingleRelatedObjectDescriptor needs to have a custom get_prefetch_queryset() implementation.
It probably makes sense to merge the Django-1.9-compatibility code before fixing this.

TODO: create a new release.

Can be closed with PR #140


Update path in the FileSystem dock after doing file operations

Fixes #45229.

Thanks!

Thanks!

Cherry-picked for 3.2.4.

Cherry-picked for 3.2.4.


Decentralized pallet-staking audit tool

Project Abstract
Grant level

[x] Level 3:  Unlimited, 5 approvals

Application Checklist

[x] The application template has been copied and aptly renamed (project_name.md).
[x] I have read the application guidelines.
[x] Payment details have been provided (bank details via email or BTC, Ethereum (USDC/DAI) or Polkadot/Kusama (USDT) address in the application).
[x] The software delivered for this grant will be released under an open-source license specified in the application.
[x] The initial PR contains only one commit (squash and force-push if needed).
[x] The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
).
[ ] I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @_______:matrix.org (change the homeserver if you use a different one)

But I have one initial question: Why was the price suddenly increased from 16k to 75k?

The scope is different.

I also find the estimated workload to develop an Excel/OpenOffice workbook, as well as the daily rate, very high to be honest.

Fair enough. Can you reveal the budget you consider reasonable for this?

I also find the estimated workload to develop an Excel/OpenOffice workbook, as well as the daily rate, very high to be honest.

I'll push back here and point to a couple of pieces of evidence that suggest you are underestimating the care that needs to be taken (this is in addition to the evidence provided in the application):

@laboon makes an assertion that some data is trivially inferred.
Then he has to edits this claim, showing he thought the current ideal staking rate was 45%,
now thinks it is 52.5%.
In both cases he is eyeballing off an imaginary chart.

Not ideal for a system that invites the unsophisticated to commit in the order of USD 600-700 million.
I was the data lead on the Opal project rolling out a smart card on, rail, bus, ferry and light rail, across the whole of NSW, Australia.  Throughout that roll out the system was in development. Nonetheless, there was only myself and one other analyst to support the design team, the internal reporting, paliamentary reporting, privacy commissioner, and auditor general. As well as all the transport operators.
I don't believe I have mis-estimated the work required.  It is possible you may not understand what is required to build a model of a system such as this - that would also explain the current state of affairs.
My applications have been a good faith attempt to help remedy some serious defects and deficiencies.
It is getting a little tiresome to be constantly met with push-back that is either wholly ignorant of basic information (Jonas3w on the state of token economic research) or reveals in the comment the precise problem that this project seeks to address (in the case of laboon in this thread)

I also find the estimated workload to develop an Excel/OpenOffice workbook, as well as the daily rate, very high to be honest.

Fair enough. Can you reveal the budget you consider reasonable for this?

@Noc2, perhaps you could point to one or more projects of similar difficulty and applicant of similar skill and experience, where you found the budget acceptable?

Thank you for the application, @taqtiqa-mark.

No worries.

I tend to agree with my colleagues, though, that this price tag is extraordinary.

Sure, as I asked @Noc, please point to applications you consider to be comparable and applicants that have comparable skill and expereince.
To save an iteration:  I believe the comparable project would need to address an issue that if unaddressed prosed a threat to project similar to the issue this application addresses.
Specifically,

Investor rewards were altered by 25% with no announcement or warning.  There is no reason to believe further such changes aren't possible.  If users loose confidence in this aspect of the project they will seek alternatives.  This tool proposes a tool where the most naive user can use on almost any desktop without installing additional software (Python, Jupyter, etc.) and confirm the rewards/dilution they are engaging with.
While this proposal is and will remain pitched at the LCD end user, it could (should) lead to a radical change in the development work flow of a central element of any relay chain (since it will reside in the pallet-staking crate) - no change should be made to the reward/dilution code without first being made to the audit workbook.  Once such a change is made, and socialized from there, it can be implemented and the implementation validated against the audit tool results.

I'm also concerned about the use of spreadsheets. Can you version control all aspects of it, i.e. the spreadsheet, scripts and tests?

I could store the XML version for the workbook in the repository.  Workbook tests are mocked in the proposal. The script tests are addressed in the application (bats).

Is this data structured in a way that new users could pick changes apart?

As a workbook they could, ideally pick every calculation apart.  The data storage is an issue - mainly because there aren't (currently) clean ways to ingest blockchain data (see future/extensiosn section).  Ideally, a chain would provide an audit record containing all the onchain data relevant to validating/auditing the chain operation.  But this is a chicken and egg problem - there is no widely distributed audit tool that needs and audit record.  If this tool proves propular maybe a chain will step forward to meet the need.  Who knows - right now it is proving very difficult to persuade people one would expect to need the least persuaion :)

Please correct me if I'm wrong, but an open source data analysis/scripting tool like R's Notebook/Markdown, Shiny or Jupyter might work better in this regard.

It could also be hosted on a server for those who don't mind, ...

This is the usual argument for centralization - developer convenience.  IIUC, it buries the problem.  Personally I would have my chain audit tool front and centre.  Changes to their rewards/dilution exposure are a critical feature to alert users about, not a nuisance to hide behind a server.

... which would help with verifying results when, inevitably, there will be iterations and multiple versions of it floating around.

As above these are critical details to be exposed and discussed.  If your rewards/dilution changes so frequently that it challenges an end users ability to understand and keep up with then you really need to address that, rather then hide those changes from them behind a centralized server they will likely never visit.

I will mark it as ready for review and share it with the rest of the team.

@noc2 could you clarify one thing for me.  Does approval require reviewer unanimity or just a majority approval?
In the case of unanimity, addressing reviewer B's objections becomes moot if you haven't persuaded Reviewer A.

Does approval require reviewer unanimity or just a majority approval?

Neither. Five committee members must approve a Level 3 application, regardless of what other committee members think.

Does approval require reviewer unanimity or just a majority approval?

Neither. Five committee members must approve a Level 3 application, regardless of what other committee members think.

Hmmm, okay now I'm confused by the neither statement. So there are committee members and reviewers?  What is the relation between them, and who is providing feedback here?

Does approval require reviewer unanimity or just a majority approval?

Neither. Five committee members must approve a Level 3 application, regardless of what other committee members think.

Hmmm, okay now I'm confused by the neither statement. So there are committee members and reviewers? What is the relation between them, and who is providing feedback here?

By "neither", he means that neither of the cases you mentioned are correct - neither unanimity nor majority approval is required. Rather, a certain number of committee members must approve a grant, based on the level of the grant.
Anyone can "review" a grant, so the term "reviewer" you used is ambiguous, but correcting it earlier probably seemed a bit pedantic and people assumed you meant "Grants Committee member". But to clarify, the term "reviewer" is not terminology in the W3F Grants Program used except in the informal sense of "one reviewing an application".
You can see who is on the Grants Committee in the README of this repo: https://github.com/w3f/grants-Program/#w3f-grants-committee
Web3 Foundation also has Grant Evaluators who have been hired to focus specifically on evaluating grants. You can see a list of them here: https://github.com/w3f/grants-Program/#w3f-grants-evaluators External evaluations can also be done, but these must be reviewed by W3F Grant Evaluators.
Currently, all Grant Evaluators are also on the Grants Committee, but this is not necessarily the case. See the links above for more details on how it works.

Hi again, @taqtiqa-mark. Thanks again for your application. After careful deliberation, the committee has decided not to support your application at this point. I want to reiterate that everyone appreciates the time and effort you put into your research and application. I hope you'll still be able to make this project a reality. In any case, best of luck and feel free to apply again in the future.


cargo can't download futures-util-preview 0.3.0-alpha.4

Cargo.toml contains
[dependencies]
futures-util-preview = { version = "0.3.0-alpha.4", features = ["compat"] }

cargo update fails with:
error: no matching version `^0.3.0-alpha.4` found for package `futures-util-preview`
location searched: registry `https://github.com/rust-lang/crates.io-index`
versions found: 0.2.2

With RUST_LOG=debug :
INFO 2018-09-02T20:33:03Z: cargo::sources::registry::index: failed to parse `futures-util-preview` registry package: Feature `compat` includes `futures01` which is neither a dependency nor another feature

This is with latest nightly cargo cargo 1.29.0-nightly (0ec7281b9 2018-08-20). Seems it doesn't like the crate renaming feature.

Seems related to https://github.com/rust-lang/cargo/issues/5753, probably the registry related code wasn’t changed to behave in the same way. Would be good to open a cargo issue about it.

Will do. Do you want to publish a new version without the crate renaming until then?

@Arnavion According to your post you're running an older nightly. alpha.4 requires at least 2018-08-31. Can you run rustup update and check whether the problem goes away?

@MajorBreakfast As I said in OP, this is latest nightly cargo.

@Arnavion I didn't know that cargo nightlies run on a different schedule. Now I do 🙂

The registry doesn’t contain any info on this renaming, so it seems likely that there will have to be a new version published to fix the registry issue. That will take some time to sort out, so I think it’d pay to revert the dependency renaming and publish alpha.5 now, we just miss out on being able to run the compat doctests so wont affect users at all.

Alpha 5 is released

Thanks. Confirmed it works.

Perfect 👌


feat: Added show_diff for pretty printing the difference between two strings during a failed equality test

fix: Fixed short-circuiting test expressions

coverage: 88.547% (+1.9%) from 86.695% when pulling 01d76f629486e0802a94763e9ba17c1974681b56 on add_show_string_diff into 14418cd4a48fc5e6670a790c57eb56cedb7a584d on main.

Codecov Report
Patch coverage: 92.00% and project coverage change: +1.58 :tada:

Comparison is base (14418cd) 86.96% compared to head (01d76f6) 88.54%.

:exclamation: Current head 01d76f6 differs from pull request most recent head 2d949fd. Consider uploading reports for the commit 2d949fd to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #12      +/-   ##
==========================================
+ Coverage   86.96%   88.54%   +1.58%
==========================================
  Files           7        8       +1
  Lines         468      585     +117
==========================================
+ Hits          407      518     +111
- Misses         61       67       +6

Impacted Files
Coverage Δ

src/macros/test_cases.jl
87.82% <ø> (ø)

src/computational_graph.jl
84.92% <60.00%> (-0.36%)
:arrow_down:

src/util.jl
92.85% <85.71%> (-7.15%)
:arrow_down:

src/macros/Test.jl
84.82% <86.66%> (ø)

src/show_values.jl
97.91% <97.91%> (ø)

src/TestingUtilities.jl
100.00% <100.00%> (ø)

src/settings.jl
96.22% <100.00%> (+9.55%)
:arrow_up:

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Mnemonic for LaBr BGOs vs GRIFFIN BGOs

The LaBr BGOs have a mnemonic of the form LBSnnxN00X, where nn is the detector number (01 to 08), and x is the array sub position (letters A to C for the three segments of the LaBr BGO). For the GRIFFIN BGOs however the Mnemonic has the form GRSnnxNmmX, where again nn is the detector number (01 to 16), but now x is the crystal (B, G, R, or W), and mm is the segment number (01 to 05).
Is this an intentional choice? Or should the LaBr BGO mnemonic also have the form LBSnnXNmmX, with mm now being the segment number (01 to 03) and the sub array number not set (as there are no different crystals for the LaBr detectors)?
I can't check the plone page to see what the mnemonic definition says about this, but maybe @AdamGarnsworthy knows this?

Okay, looking at https://grsi.wiki.triumf.ca/wiki/Detector_Nomenclature, it seems that the statement for LaBr BGOs is:
LB -- LaBr | L – LaBrB – BaF2 T – TAC S – Suppressor | 1-18 | X - or A,B,C for suppressor crystals | N – PMT anode T – TAC | 00 | x

So it seems that for LaBr BGOs they labelling is done by the "suppressor crystals" and not by the segment number. So this is something we'll have to change in the GRSIData library.

This has been fixed now in GRIFFINCollaboration/GRSIData#73


Add Firecrawl tool

Add multiple tools by https://docs.firecrawl.dev/introduction

Cool examples with code: https://github.com/alexfazio/firecrawl-quickstarts/tree/main


UI5 Tokens

Description
Changes proposed in this pull request:

replaced tokens with UI5
adjusted css

Related issue(s)

/retest


Add hot potato

About the PR

It adds hot potato. When activated you can only transfer it by hitting others (they should have hands, if they hold something they will drop it). When explodes can crit people (120 dmg) not wearing good protection (bomb suit).
Media

Changelog

:cl:

add: added hot potato. When activated you can't drop it, hit others to transfer until it explodes!
add: added hot potato to chef, botanist, clown and mime uplink (4 TC)

:potato:
this will definitely be spammed on evac and i love it

I also want to add some sort of smoke effect to make it visible, but don't know how.

I also want to add some sort of smoke effect to make it visible, but don't know how.

I also want to add some sort of smoke effect to make it visible, but don't know how.

It might be too janky but you could try making a smoke puff sprite and prototype with the TimedDespawn component, then every once in a while spawn one with a small random offset from the entity's actual position

actually, i now remember that jetpacks have particle effects

added effect

made effect spawn more frequently

i still don't know, how to cancel ContainerRemove event on client side (you can visually "drop" it for a brief moment there), it doesn't work for some reason

i still don't know, how to cancel ContainerRemove event on client side (you can visually "drop" potato for a brief moment there), it just doesn't work for some reason

You'd have to do it in client or shared

It is in shared

the shared system looks fine, probably client using another thing to predict that isnt cancelled

the shared system looks fine, probably client using another thing to predict that isnt cancelled

You need to network the datafields of the hotpotatocomponent or else it'll mispredict on the client.

the shared system looks fine, probably client using another thing to predict that isnt cancelled

You need to network the datafields of the hotpotatocomponent or else it'll mispredict on the client.

They are networked unless I did something wrong. E.g. ActiveHotPotatoComponent is sent to client on activation.

Do I need ComponentState?

check view variables > client components > hotpotato and see if client thinks its not allowed to remove.

Do I need ComponentState?

Yes, i would assume.

for some reason hot potato doesn't show up in inventory now (and shows on ground) until I try to use hands

it's something with client prediction, if I only cancel event on server item appears normally on hit entity.

@AJCM-git prediction works correctly now, thank you. No idea what I did wrong.

@AJCM-git can you test again, maybe issues magically disappeared :magic_wand:

does this still mispredict.

does this still mispredict.

On local server with single player - it doesn't. And I can't test it with multiple players on my machine. Maybe testmerge it?

@Slava0135 I get a debug assert as soon as I hit someone.

does this still mispredict.

On local server with single player - it doesn't. And I can't test it with multiple players on my machine. Maybe testmerge it?

@Slava0135 I get a debug assert as soon as I hit someone.

that is new

I will try to fix this

Somehow auto generating comp state fixed assert

Somehow auto generating comp state fixed assert

Still asserts for me.


Certificate rotation has no affect on client if server directory is present

Environmental Info:
K3s Version: k3s version v1.28.11+k3s2 (d076d9a7)

Node(s) CPU architecture, OS, and Version: mix of x86_64 and arm64 instances

Cluster Configuration:
3 servers, 8 agents

Describe the bug:
Yesterday I noticed the following errors being returned for some of my agent nodes:
│   Warning  CertificateExpirationWarning  52m   k3s-cert-monitor  Node certificates require attention - restart k3s on this node to trigger automatic rotation: auth-proxy/client-auth-proxy.crt: certificate CN=system:auth-proxy expired at 2024-01-20T11:51:51Z, cloud-controller/client-k3s-cloud-controller.crt: certificate CN=k3s-cloud-controller-manager expired at 2024-01-20T11:51:51Z, etcd/client.crt: certificate CN=etcd-client expired at 2024-01-20T11:51:51Z, etcd/server-client.crt: certificate CN=etcd-server expired at 2024-01-20T11:51: │
│ 51Z, etcd/peer-server-client.crt: certificate CN=etcd-peer expired at 2024-01-20T11:51:51Z, scheduler/client-scheduler.crt: certificate CN=system:kube-scheduler expired at 2024-01-20T11:51:51Z, kube-proxy/client-kube-proxy.crt: certificate CN=system:kube-proxy expired at 2024-01-20T11:51:51Z, api-server/client-kube-apiserver.crt: certificate CN=system:apiserver,O=system:masters expired at 2024-01-20T11:51:51Z, api-server/serving-kube-apiserver.crt: certificate CN=kube-apiserver expired at 2024-01-20T11:51:51Z, k3s-controller/client-k3s- │
│ controller.crt: certificate CN=system:k3s-controller expired at 2024-01-20T11:51:51Z, controller-manager/client-controller.crt: certificate CN=system:kube-controller-manager expired at 2024-01-20T11:51:51Z, admin/client-admin.crt: certificate CN=system:admin,O=system:masters expired at 2024-01-20T11:51:51Z                                                                                │
│   Warning  CertificateExpirationWarning  22m   k3s-cert-monitor  Node certificates require attention - restart k3s on this node to trigger automatic rotation: api-server/client-kube-apiserver.crt: certificate CN=system:apiserver,O=system:masters expired at 2024-01-20T11:51:51Z, api-server/serving-kube-apiserver.crt: certificate CN=kube-apiserver expired at 2024-01-20T11:51:51Z, auth-proxy/client-auth-proxy.crt: certificate CN=system:auth-proxy expired at 2024-01-20T11:51:51Z, cloud-controller/client-k3s-cloud-controller.crt: certificate │
│  CN=k3s-cloud-controller-manager expired at 2024-01-20T11:51:51Z, etcd/client.crt: certificate CN=etcd-client expired at 2024-01-20T11:51:51Z, etcd/server-client.crt: certificate CN=etcd-server expired at 2024-01-20T11:51:51Z, etcd/peer-server-client.crt: certificate CN=etcd-peer expired at 2024-01-20T11:51:51Z, scheduler/client-scheduler.crt: certificate CN=system:kube-scheduler expired at 2024-01-20T11:51:51Z, kube-proxy/client-kube-proxy.crt: certificate CN=system:kube-proxy expired at 2024-01-20T11:51:51Z, k3s-controller/client-k3s- │
│ controller.crt: certificate CN=system:k3s-controller expired at 2024-01-20T11:51:51Z, admin/client-admin.crt: certificate CN=system:admin,O=system:masters expired at 2024-01-20T11:51:51Z, controller-manager/client-controller.crt: certificate CN=system:kube-controller-manager expired at 2024-01-20T11:51:51Z

I tried restarting those agents multiple times but that had no effect.
Doing a
for i in ls /var/lib/rancher/k3s/agent/*.crt; do echo $i; openssl x509 -enddate -noout -in $i; done

showed that all certificates on that machine are to expire next year. I then picked one of those certificates and searched the machine for that filename - and found another instance in /var/lib/rancher/k3s/server. Apparently, I had at one point in the past incorrectly started k3s as a server on those machines.
After completely removing the server directory, restarting fixed the problem.
Expected behavior:
When starting k3s as agent, the presence of outdated certificates in the server directory should not have any impact.
Actual behavior:

Additional context / logs:

So the warning found some certificates that you'd missed cleaning up? This sounds like a good thing. Did this create any actual problems, or was it just unexpected?


removed byref arg on call to WinClipAPI.memcopy

So I had this Error: This value of type "VarRef" has no property named "Ptr".
Removing the & seems to have it fixed. :)
Pardon me. VS Code also removed all the trailing whitespace 🙈
Important line is 236!
cheers:
ëRiC

Can you please post some script code to replicate the issue?

OK I got something here:
wc := WinClip()

run "notepad.exe"
winwaitactive "ahk_exe notepad.exe"
ahk_id := "ahk_id " . WinActive("ahk_exe notepad.exe")
sleep 500

txt := "Hello, WinClip!"
wc.Paste(txt)

SendInput "^a"
wc.iCopy()
txt2 := wc.iGetText()
msgbox txt "`n" txt2

SendInput "{Del}"
sleep 50
WinKill ahk_id

ExitApp

Maybe this was all just due to how I used it formerly with 1.1 🤔
It works flawlessly when I use wc.Copy() and wc.GetText() instead of the i versions:
wc := WinClip()

run "notepad.exe"
winwaitactive "ahk_exe notepad.exe"
ahk_id := "ahk_id " . WinActive("ahk_exe notepad.exe")
sleep 500

txt := "Hello, WinClip!"
wc.Paste(txt)

SendInput "^a"
wc.Copy()
txt2 := wc.GetText()
msgbox txt "`n" txt2

SendInput "{Del}"
sleep 50
WinKill ahk_id

ExitApp

Honestly, I don't know about the i methods anyway :|
Weird that it breaks this and not the other way. memcopy does not expect a reference and it breaks in that case where one is passed. But then: What do I know about pointers and stuff!? Isn't reference a pointer? 🥴

OK. so this is pebkac, right?
Could there be a better error or docs or anything?
I could look into examples for the .i-methods?
Otherwise I have no problem deleting the PR :)

Sorry for the delay I'm looking at it now.
I want to at least understand the error better, and possibly create a catch and give a better error msg if possible.

Oki Thank you for looking into it! I'll file an issue later.
Still super glad you did the conversion already 🙏
I'm just moving all my projects to ahk2. It's quite some work.


swift infer only uses 1 GPU

Describe the bug
What the bug is, and how to reproduce, better with screenshots(描述bug以及复现过程，最好有截图)
when using swift infer with vllm backend, only one GPU is being utilized
NFRAMES=6 MAX_PIXELS=100352 CUDA_VISIBLE_DEVICES=0,1,2,3,4,5,6,7 swift infer --infer_backend vllm ...

Your hardware and system info
NVIDIA-SMI 535.161.08, Driver Version: 535.161.08 ,  CUDA Version: 12.2 , torch:2.4.1

https://swift.readthedocs.io/zh-cn/latest/Instruction/命令行参数.html#vllm


bug: Bodies still collide after their removal on ccd verision

#230
ccd version of the object is cleared but the bug is still happening.
Ccd version can be merged into the main version?
I used the ccd version of the project but also encountered this bug

That CCD test is unstable and I wouldn't advise using it, I'm working on an alternate approach (my time is currently quite limited though).


”ADS1220_WE“ usage

How to use "SPIClass *s" in ADS1220_WE(int cs, int drdy, SPIClass *s), I would be grateful if you could tell me

Hi @xiyangdiy,
there two ways to create your ADS1220 object:
ADS1220_WE ads = ADS1220_WE(ADS1220_CS_PIN, ADS1220_DRDY_PIN);
// or:
ADS1220_WE ads = ADS1220_WE(ADS1220_CS_PIN, ADS1220_DRDY_PIN, &SPI);

The second option uses "SPIClass *s". If you work with just one SPI object, then it doesn't make a difference which option you take. The SPI object is passed as a reference (with the "&"). That means the original object is used. So it's not too interesting for MCUs which only have one SPI interface. But if you work for example with an ESP32 which has two SPI interfaces and you want to use both then you would need to pass the SPI objects.

By the way thanks for the first star! And sorry for all the releases with the last weeks. Since it is new, I still found some bugs.

Thank you for your answer. Can this library use SoftSPI? If so, do you have a specific example? I found a library, its name is "SoftSPIB", it can customize spi pins, but I don't know how to use it with "ADS1220_WE" library.

My MCU is ESP32-S3.

That would need some changes in the library. You would define the SoftSPIB Object like this:
SoftSPIB mySPI(12, 13, 4);

and then pass the mySPI object like this:
ADS1220_WE ads = ADS1220_WE(ADS1220_CS_PIN, ADS1220_DRDY_PIN, &mySPI);

On the library side you would need a constructor that takes the SoftSPIB object, like:
ADS1220_WE::ADS1220_WE(int cs, int drdy, SoftSPIB *s){
     _softSPI = s;

A variable would need to be defined:
SoftSPI *_spi;

And then finally all SPI functions (line 324 till the end) in ADS1220_WE.cpp would need to be changed to the corresponding SoftSPIB functions, beauce they are a bit different.
So in summary: the library could be adjusted, but with some effort.
If may ask why do you want to use SoftSPIB? Why don't you just use the standard SPI interface of the ESP32?

I have just tried an example sketch with an ESP32 Development Board using the standard SPI interface. I only had to adjust the DRDY Pin and the CS Pin. The rest was unchanged.

Thanks for your enthusiastic answer!
I'm just a beginner, your answer helped me a lot!


Added favicon (just solid #840000)

I know it's kind of a silly addition, but it drives me nuts to have a link w/o a favicon on my bookmarks bar...

haha that's fair. Not a huge fan of the specific favicon myself, but I'll design one and make the change when I can spare some time :) thanks!

Awesome, thanks! I'll leave this open for now and kill the pull request whenever the favicon is up. I might also try a design that ties in better w/ the arxiv favicon instead of just being a plain color block... I'll add that here if/when I get around to making a non-ugly version of that.

I think I'd just want it to be a simple white "AS" on top of the arxiv-sanity-red-color. If you make the change I'd be happy to merge it. You might also want to include the favicon html into the other .html file for discussions.

Added image and thanks for the catch on the other html file.
I left the font as (bold) arial to match the header on the website. I didn't actually test this (i.e., I haven't run my own instance of the site), but since it's just a favicon link, I imagine that everything should work...

cool! ty :)


Expose shouldComponentUpdate

For React components built on ES6 class, overriding shouldComponentUpdate in class constructor is another way to extend the mixin.

@pukapukan thanks for the PR. Can you also update the top of the README to say file to 4. Otherwise, nice work. I'll merge this in and publish the changes.

This library exposes 3 distict options for immutable rendering:

should say

This library exposes 4 distinct options for immutable rendering:

Note: also there is a misspelling in distict -> dinstinct

@jurassix Good catch! Fixed the misspellings :)
It's all yours now

@pukapukan thx!

@pukapukan published in v0.9.5


Initial transition effective from typemin(DateTime)

VariableTimeZone types are made up of transitions which have a UTC DateTime indicating the instant at when the new rule becomes effective. Previously the first transition started at 1800/1/1 for no real reason except that no zone or rule started that early and it is rather silly to use the concept of time zones prior to their use. After merging in #8 it seems more reasonable to allow users to make ZonedDateTime's prior to 1800 and let them use their own judgement.
As a happy side effect this makes comparing Julia processed timezone rules easier to compare with tzfiles.

+1


Update Pose Detector API version and add 3d point feature

Resolves issues - #90 , #93 for android.

@bharat-biradar : let me try this on iOS as well to have it in the same PR

@bharat-biradar : LGTM, let's bump the version to 0.6.1 to release this fix


Show Google Ads extractor in UI

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/1940
Originally created by @DouweM on 2020-04-03 18:16:28

[x] Enable Google Ads OAuth: https://gitlab.com/meltano/infrastructure/-/issues/21
[x] Update documentation

[x] Make explicit that Google Ads extractor does not pull in data on Smart Campaigns: https://gitlab.com/meltano/meltano/-/issues/1918

[x] Enable Google Ads extractor in discovery.yml

[x] Set Adwords User Agent to default value and hide from UI: https://gitlab.com/meltano/meltano/-/issues/1908

View 14 previous comments from the original issue on GitLab