Consider creating a bugfix release for AMD CPUs

1.17 doesn't build on zen2 architecture.
There is a fix already on the main branch, so nothing needs to be fixed.
The issue is that, when building against libxsmm, a branch needs to be used or a commit, which is a bit messy.
Could you release something like 1.17.1 or 1.18, so there is a version to be used on zen2 architecture?

I want to avoid this in particular:
(skylake) $ spack install gromacs+cp2k
(zen2) $ spack install gromacs+cp2k ^libxsmm@master

I don't think that this has to do with zen2, zen1=zen2=zen3 when it comes the arch, just the uarch changes. I believe the issues you are seeing are related to the compiler/OS you are using.
Please provide details on the issue your facing.

Building against 1.17 produces
/groups/CBG/opt/spack-0.17.2/root/lib/spack/env/gcc/gcc  -DNDEBUG
             -D__STATIC=1 -DLIBXSMM_TARGET_ARCH=1006 -DLIBXSMM_OPENMP_SIMD -DLI
             BXSMM_BUILD=2  -Iinclude -I./src  -msse4.2 -fPIC -g -Wall -O2 -fop
             enmp-simd -funroll-loops -ftree-vectorize -fdata-sections -ffuncti
             on-sections -fvisibility=hidden -pthread  -c ./src/libxsmm_dnn_rnn
             cell_backward_weight_update.c -o  obj/intel64/libxsmm_dnn_rnncell_
             backward_weight_update.o
     45      /tmp/5912987.tmpdir/ccpJmgQx.s: Assembler messages:
  >> 46      /tmp/5912987.tmpdir/ccpJmgQx.s:76559: Error: no such instruction:
             `vcvtneps2bf16 %zmm21,%ymm18'
  >> 47      /tmp/5912987.tmpdir/ccpJmgQx.s:76571: Error: no such instruction:
             `vcvtneps2bf16 %zmm29,%ymm23'
  >> 48      /tmp/5912987.tmpdir/ccpJmgQx.s:76795: Error: no such instruction:
             `vcvtneps2bf16 %zmm2,%ymm7'
  >> 49      /tmp/5912987.tmpdir/ccpJmgQx.s:76813: Error: no such instruction:
             `vcvtneps2bf16 %zmm3,%ymm2'
  >> 50      /tmp/5912987.tmpdir/ccpJmgQx.s:76861: Error: no such instruction:
             `vcvtneps2bf16 %zmm10,%ymm7'
  >> 51      /tmp/5912987.tmpdir/ccpJmgQx.s:77337: Error: no such instruction:
             `vcvtneps2bf16 %zmm20,%ymm26'
  >> 52      /tmp/5912987.tmpdir/ccpJmgQx.s:77348: Error: no such instruction:
             `vcvtneps2bf16 %zmm21,%ymm18'
  >> 53      /tmp/5912987.tmpdir/ccpJmgQx.s:77571: Error: no such instruction:
             `vcvtneps2bf16 %zmm3,%ymm2'
...

Build against master finishes successfully.

OK, this has nothing to do with Zen (as expected) just that your gcc/binutils seem to be really outdated. Master is simply not showing these issues as we got rid of a lot of intrinsic (and file which is actually causing the issue), the instructions are Intel Cooper Lake the chip is from 2019. It might work if you say AVX=2 when compiling, not sure.
Please updated to some recent binutils package and the issue should go away.

You are right about binutils, compiler is using system binutils, which are probably outdated
gcc<EMAIL_ADDRESS>build_type=RelWithDebInfo languages=c,c++,fortran arch=linux-scientific7-zen2
    ^diffutils<EMAIL_ADDRESS>arch=linux-scientific7-zen2
        ^libiconv<EMAIL_ADDRESS>libs=shared,static arch=linux-scientific7-zen2
    ^gawk<EMAIL_ADDRESS>arch=linux-scientific7-zen2
        ^gmp<EMAIL_ADDRESS>libs=shared,static arch=linux-scientific7-zen2
            ^autoconf<EMAIL_ADDRESS>patches=35c4492,7793209,a49dd5b arch=linux-scientific7-zen2
                ^m4<EMAIL_ADDRESS>patches=9dc5fbd,bfdffa7 arch=linux-scientific7-zen2
                    ^libsigsegv<EMAIL_ADDRESS>arch=linux-scientific7-zen2
                ^perl<EMAIL_ADDRESS>arch=linux-scientific7-zen2
                    ^berkeley-db<EMAIL_ADDRESS>patches=b231fcc arch=linux-scientific7-zen2
                    ^bzip2<EMAIL_ADDRESS>arch=linux-scientific7-zen2
                    ^gdbm<EMAIL_ADDRESS>arch=linux-scientific7-zen2
                        ^readline<EMAIL_ADDRESS>arch=linux-scientific7-zen2
                            ^ncurses<EMAIL_ADDRESS>abi=none arch=linux-scientific7-zen2
                                ^pkgconf<EMAIL_ADDRESS>arch=linux-scientific7-zen2
                    ^zlib<EMAIL_ADDRESS>patches=0d38234 arch=linux-scientific7-zen2
            ^automake<EMAIL_ADDRESS>arch=linux-scientific7-zen2
            ^libtool<EMAIL_ADDRESS>arch=linux-scientific7-zen2
        ^mpfr<EMAIL_ADDRESS>libs=shared,static arch=linux-scientific7-zen2
            ^autoconf-archive<EMAIL_ADDRESS>patches=130cd48 arch=linux-scientific7-zen2
            ^texinfo<EMAIL_ADDRESS>patches=12f6edb,1732115 arch=linux-scientific7-zen2
    ^mpc<EMAIL_ADDRESS>libs=shared,static arch=linux-scientific7-zen2
    ^zstd<EMAIL_ADDRESS>libs=shared,static arch=linux-scientific7-zen2

I can reinstall compiler together with binutils package.
gcc<EMAIL_ADDRESS>build_type=RelWithDebInfo languages=c,c++,fortran arch=linux-scientific7-zen2
    ^binutils<EMAIL_ADDRESS>libs=shared,static arch=linux-scientific7-zen2
        ^diffutils<EMAIL_ADDRESS>arch=linux-scientific7-zen2
            ^libiconv<EMAIL_ADDRESS>libs=shared,static arch=linux-scientific7-zen2
        ^gettext<EMAIL_ADDRESS>arch=linux-scientific7-zen2
            ^bzip2<EMAIL_ADDRESS>arch=linux-scientific7-zen2
            ^libxml2<EMAIL_ADDRESS>arch=linux-scientific7-zen2
                ^pkgconf<EMAIL_ADDRESS>arch=linux-scientific7-zen2
                ^xz<EMAIL_ADDRESS>libs=shared,static arch=linux-scientific7-zen2
                ^zlib<EMAIL_ADDRESS>patches=0d38234 arch=linux-scientific7-zen2
            ^ncurses<EMAIL_ADDRESS>abi=none arch=linux-scientific7-zen2
            ^tar<EMAIL_ADDRESS>zip=pigz arch=linux-scientific7-zen2
                ^pigz<EMAIL_ADDRESS>arch=linux-scientific7-zen2
                ^zstd<EMAIL_ADDRESS>compression=none libs=shared,static arch=linux-scientific7-zen2
        ^texinfo<EMAIL_ADDRESS>patches=12f6edb,1732115 arch=linux-scientific7-zen2
            ^perl<EMAIL_ADDRESS>arch=linux-scientific7-zen2
                ^berkeley-db<EMAIL_ADDRESS>patches=b231fcc arch=linux-scientific7-zen2
                ^gdbm<EMAIL_ADDRESS>arch=linux-scientific7-zen2
                    ^readline<EMAIL_ADDRESS>arch=linux-scientific7-zen2
    ^gawk<EMAIL_ADDRESS>arch=linux-scientific7-zen2
        ^gmp<EMAIL_ADDRESS>libs=shared,static arch=linux-scientific7-zen2
            ^autoconf<EMAIL_ADDRESS>patches=35c4492,7793209,a49dd5b arch=linux-scientific7-zen2
                ^m4<EMAIL_ADDRESS>patches=9dc5fbd,bfdffa7 arch=linux-scientific7-zen2
                    ^libsigsegv<EMAIL_ADDRESS>arch=linux-scientific7-zen2
            ^automake<EMAIL_ADDRESS>arch=linux-scientific7-zen2
            ^libtool<EMAIL_ADDRESS>arch=linux-scientific7-zen2
        ^mpfr<EMAIL_ADDRESS>libs=shared,static arch=linux-scientific7-zen2
            ^autoconf-archive<EMAIL_ADDRESS>patches=130cd48 arch=linux-scientific7-zen2
    ^mpc<EMAIL_ADDRESS>libs=shared,static arch=linux-scientific7-zen2

I will report in some time if it helped.
That being said, master is more portable than stable release, so I still believe that creating a release at some point wouldn't hurt.

yes, we are prepping 2.0 which will increase portability substantially (i.e. being intrinsic free, adding ASIMD, SVE for aarch64) and this is happening in master. However, as we use the chance of cleaning up APIs when increasing major, right now master has not yet been stabilized wrt to 2.0 API.

I don't think that this has to do with zen2, zen1=zen2=zen3 when it comes the arch, just the uarch changes. I believe the issues you are seeing are related to the compiler/OS you are using.

Indeed, I changed the offending caption of the issue.

Sorry, I forgot about this issue. So building binutils worked. Thank you for your help.
Also it might be not worth your effort to work on bugfix release. I didn't understand that portability improvements are one of the focus of the new release. Maybe focusing on the new release instead of backward support is the way to go.
This issue can be closed from my side.

thanks.


V 2.0

KS2 acts differently from KS1 and henceforth we are going to need a matching version of kalastatic.module to serve it from Drupal.
There are two targets:
7.x-2.x

Will probably only need the paths adjusted so it looks for a build folder in the current theme instead of kalastatic/build.
Form to tell the module where KS lives will still be applicable because it could still be anywhere.

8.x-2.x

Full rewrite will likely be required.
Hopefully it will be a little more straightforward because the routing system lets you return things other than a themed Drupal page so all of the page call back code can probably go.

Yes.

Correct


add data Converters

hi,
could you add converter like:
Data e.g. kilobyte -> megabyte as {{ 1524 | kb2mb }} //1.52
other:
Volume e.g. liters -> milliliters as {{ 1 | liter2milliliter }} //1000
Length e.g.  inches -> centimeters as {{ 2 | inche2centi }} //5.08
it's big deal and make this pack more usable.

yes, maybe another project good for this


feature.export sometimes fails, when url is undefined

as of 0.4a64
sample code:
import siibra
re = siibra.get_region("2.9", "hoc1 left")
features = siibra.features.get(re, "ebrains")
feat = features[0]
feat.export("foo.zip")

expected:
zip to be written
actual:
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/xgui3783/dev/projects/siibra-api/venv/lib/python3.10/site-packages/siibra/features/feature.py", line 223, in export
    self._export(fh)
  File "/home/xgui3783/dev/projects/siibra-api/venv/lib/python3.10/site-packages/siibra/features/dataset/ebrains.py", line 90, in _export
    fh.writestr("doi.md", DOI_TMPL.format(self.url))
KeyError: 'doi'

Fixed as of c2c25aacfcadcc3765f8cb08529e45553bda0872. Please reopen if it persists in another way.


Train.py - ValueError: Transformers now supports natively BetterTransformer optimizations

Hey,
I'm working on a fine-tuning of your model to build a Pokémon diamond music generator.
For now, I'm trying to understand your code and run it. When I try to run the train.py (data is my folder with midi file) :
python .\train.py --data ".\data\"

I encounter this error :
Traceback (most recent call last):
  File "D:\Fac\ESIR3\IA\TP\midi-model\train.py", line 336, in <module>
    model = TrainMIDIModel(tokenizer, flash=True, lr=opt.lr, weight_decay=opt.weight_decay,
  File "D:\Fac\ESIR3\IA\TP\midi-model\train.py", line 101, in __init__
    super(TrainMIDIModel, self).__init__(tokenizer=tokenizer, n_layer=n_layer, n_head=n_head, n_embd=n_embd,
  File "D:\Fac\ESIR3\IA\TP\midi-model\midi_model.py", line 30, in __init__
    self.net = self.net.to_bettertransformer()
  File "D:\Fac\ESIR3\IA\TP\midi-model\venv\lib\site-packages\transformers\modeling_utils.py", line 4314, in to_bettertransformer
    return BetterTransformer.transform(self)
  File "C:\Users\diman\AppData\Local\Programs\Python\Python39\lib\contextlib.py", line 79, in inner
    return func(*args, **kwds)
  File "D:\Fac\ESIR3\IA\TP\midi-model\venv\lib\site-packages\optimum\bettertransformer\transformation.py", line 211, in transform
    raise ValueError(
ValueError: Transformers now supports natively BetterTransformer optimizations (torch.nn.functional.scaled_dot_product_attention) for the model type llama. Please upgrade to transformers>=4.36 and torch>=2.1.1 to use it. Details: https://huggingface.co/docs/transformers/perf_infer_gpu_one#flashattention-and-memory-efficient-attention-through-pytorchs-scaleddotproductattention

I'm using torch==2.1.2+cu121 and transformers==4.36.2
Any ideas ?

I also have this problem now. on the old operating system, I managed to do training, but I don't know what version of python and torch I used then in September 2023. who manages to train, please post.  in the past I used the python command
train.py --data midi_data/train --lr 0.001 --batch-size-train 16 --max-step 1000 --val-step 25

I also encountered this - I am totally new to this so what I did was probably totally wrong, but I got it running at least. Still get quite a few warnings from pytorch, but at least it runs:
In train.py ( line 335 ) there is a call to TrainMidiModel with flash=True, I changed it to False and that did it for me.
Also I had to reconfigure the torch options quite a bit to make finetuning possible on my 8gig GPU. Its painful, but at least it's possible ( about half an hour / epoch ) and a full validation will not work because of too low memory.


Cannot Specify Delegate Selectors with Service Account in Harness NG Kubernetes Connector

Configuring a Kubernetes connector that uses a service account via Terraform does not offer any means of specifying delegate selectors. This is possible via the Harness NG web interface:

Terraform Version
Terraform v1.1.9 on darwin_amd64
+ provider registry.terraform.io/harness/harness v0.2.4

Affected Resource(s)
harness_platform_connector_kubernetes

Terraform Configuration Files
resource "harness_platform_connector_kubernetes" "example" {
    identifier  = "example"
    name        = "example"
    org_id      = "example_org"
    tags        = []

    service_account {
        master_url                = "https://k8s.example.com"
        service_account_token_ref = "org.example_secret_ref"
    }
}

Expected Behavior
It is possible to specify delegate_selectors when using a service_account in a manner consistent with the web interface.
Actual Behavior
It is not possible to specify delegate_selectors when using a service_account in a manner consistent with the web interface.
Important Factoids
Delegate selector settings are wiped when changes are applied to the Kubernetes connector's configuration.

Issue has been fixed in v0.2.13, https://github.com/harness/terraform-provider-harness/blob/main/CHANGELOG.md#0213.


Kinesis Elasticsearch Sink: don't fail silently for inputs with fewer than 24 tab-separated fields

If an incoming event doesn't have enough tab-separated fields for the sink to extract its geolocation, the Kinesis Connector Library will catch the resulting exception and log an error, but no bad record will be  generated.

Good catch Fred!


Update aggregation operator docs

Update the aggregation operator documentation.

Include before expression style syntax as valid.
Update examples to show before style.

Signed-off-by: Ben Kochie<EMAIL_ADDRESS>

Updated, PTAL.

:+1:


Add a bounty system here?

The idea has been raised in #1300 that maybe we should add a bounty system here to encourage/reward participation in coding on this project. What do y'all think? Any recommendations on which system/service to use?

Just to be clear, I'm talking about a system that helps interested parties pay coders for fixing issues and/or adding features to the codebase.

It's like this would be one option:
https://www.bountysource.com/

Another option:
https://gitcoin.co/


NME: improvements to post processes

I have ported this shader (the post process part) from shadertoy to NME: https://nme.babylonjs.com/#8MNHL1#3
In doing so, I had to modify a number of things to make it possible:

smoothstep allowed only floats, I updated it to allow any type of inputs
you can now use multiple CurrentScreenBlock blocks in the material to be able to sample multiple times the screen texture
the sampling code generated by CurrentScreenBlock needs to run in the fragment shader, not in the vertex, else a whole class of post processes can't be done

Here are two PGs that are using the post process:

https://playground.babylonjs.com/#7CR6WZ
https://playground.babylonjs.com/#7CR6WZ#1

Screenshots without and with the post process (note that the post process is animated, which you won't see in the screenshots, except if you're plastered):

validation tests seem to fail

In the same way than for CurrentScreenBlock, I have allowed to use multiple ParticleTextureBlock blocks in a particle material: http://localhost:1338/nodeEditor/public/index-local.html#BDK1QF

There is just a bit of conflict and you can merge


[backport/1.22] test: fix a race in tcp_tunneling_integration_test (#22883)

The HeaderEvaluatorConfigUpdate test needs to wait for a listener to be replaced. Its previous attempt to achieve that did not account for the intermediate warming state of new listeners, which could lead to the test continuing prematurely and failing.
Signed-off-by: Benjamin Peterson<EMAIL_ADDRESS>Signed-off-by: Ryan Northey<EMAIL_ADDRESS>
Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

example flake:
https://dev.azure.com/cncf/envoy/_build/results?buildId=121095&view=logs&j=bbe4b42d-86e6-5e9c-8a0b-fea01d818a24&t=e00c5a13-c6dc-5e9a-6104-69976170e881&l=14496


Bug: handshakes with peers don't work

This is a bug report
Problem

Handshakes with peers don't work, making it impossible for js-waku to communicate with any other node.
The code is very basic:
const waku = await Waku.create({
	bootstrap: {
		peers: ['/dns4/private.domain/tcp/443/wss/p2p/16Uiu2HAkwAzaMhKTikSVD1djSieWNoJ9jq63kmJG21mmizT8jQDq']
	}
})
await waku.waitForRemotePeer()

The logs in the browser:
libp2p:websockets dialing /dns4/private.domain/tcp/443/wss/p2p/16Uiu2HAkwAzaMhKTikSVD1djSieWNoJ9jq63kmJG21mmizT8jQDq +10s
common.js:113 libp2p:websockets dialing private.domain:443 +0ms
common.js:113 libp2p:websockets connected /dns4/private.domain/tcp/443/wss/p2p/16Uiu2HAkwAzaMhKTikSVD1djSieWNoJ9jq63kmJG21mmizT8jQDq +115ms
common.js:113 libp2p:websockets new outbound connection /dns4/private.domain/tcp/443/wss/p2p/16Uiu2HAkwAzaMhKTikSVD1djSieWNoJ9jq63kmJG21mmizT8jQDq +0ms
common.js:113 libp2p:upgrader Starting the outbound connection upgrade +10s
common.js:113 libp2p:upgrader selecting outbound crypto protocol +0ms ['/noise']
common.js:113 mss:select select: write ["/multistream/1.0.0", "/noise"] +10s
common.js:113 mss:select select: read "/multistream/1.0.0" +1ms
common.js:113 mss:select select: read "/noise" +40ms
common.js:113 libp2p:upgrader encrypting outbound connection to {"id":"16Uiu2HAkwAzaMhKTikSVD1djSieWNoJ9jq63kmJG21mmizT8jQDq","pubKey":"CAISIQIZ9LAuNEcxirgJRqJj0FedIiUS7AA1A0URms+svcgYJA=="} +41ms
common.js:113 libp2p:noise Stage 0 - Initiator starting to send first message. +10s
common.js:113 libp2p:noise Stage 0 - Initiator finished sending first message. +1ms
common.js:113 libp2p:noise Stage 1 - Initiator waiting to receive first message from responder... +0ms
common.js:113 libp2p:upgrader:err Failed to upgrade outbound connection +10s Error: Error occurred during XX handshake: First argument to DataView constructor must be an ArrayBuffer
    at Noise.performXXHandshake (noise.ts:210:13)
    at async Noise.performHandshake (noise.ts:166:14)
    at async Noise.secureOutbound (noise.ts:79:23)
    at async Upgrader._encryptOutbound (upgrader.js:436:12)
    at async Upgrader.upgradeOutbound (upgrader.js:196:11)
    at async ClassIsWrapper.dial (index.js:54:18)
    at async TransportManager.dial (transport-manager.js:111:14)
    at async dial-request.js:81:18
    at async index.js:53:19
common.js:113 libp2p:dialer token 16 released +222ms
common.js:113 libp2p:dialer:err AggregateError:     Error: Error occurred during XX handshake: First argument to DataView constructor must be an ArrayBuffer        at Noise.performXXHandshake (http://localhost:5173/node_modules/.vite/deps/js-waku.js?v=4015e773:35151:17)        at async Noise.performHandshake (http://localhost:5173/node_modules/.vite/deps/js-waku.js?v=4015e773:35122:18)        at async Noise.secureOutbound (http://localhost:5173/node_modules/.vite/deps/js-waku.js?v=4015e773:35062:27)        at async Upgrader._encryptOutbound (http://localhost:5173/node_modules/.vite/deps/js-waku.js?v=4015e773:51563:16)        at async Upgrader.upgradeOutbound (http://localhost:5173/node_modules/.vite/deps/js-waku.js?v=4015e773:51401:15)        at async ClassIsWrapper.dial (http://localhost:5173/node_modules/.vite/deps/js-waku.js?v=4015e773:63545:22)        at async TransportManager.dial (http://localhost:5173/node_modules/.vite/deps/js-waku.js?v=4015e773:38975:18)        at async http://localhost:5173/node_modules/.vite/deps/js-waku.js?v=4015e773:41790:22        at async http://localhost:5173/node_modules/.vite/deps/js-waku.js?v=4015e773:41695:27    at maybeSettle (http://localhost:5173/node_modules/.vite/deps/js-waku.js?v=4015e773:41678:18)    at http://localhost:5173/node_modules/.vite/deps/js-waku.js?v=4015e773:41707:31 +10s
common.js:113 libp2p:connection-manager:auto-dialler:err could not connect to peerStore stored peer +10s AggregateError:
    Error: Error occurred during XX handshake: First argument to DataView constructor must be an ArrayBuffer
        at Noise.performXXHandshake (noise.ts:210:13)
        at async Noise.performHandshake (noise.ts:166:14)
        at async Noise.secureOutbound (noise.ts:79:23)
        at async Upgrader._encryptOutbound (upgrader.js:436:12)
        at async Upgrader.upgradeOutbound (upgrader.js:196:11)
        at async ClassIsWrapper.dial (index.js:54:18)
        at async TransportManager.dial (transport-manager.js:111:14)
        at async dial-request.js:81:18
        at async index.js:53:19
    at maybeSettle (index.js:31:11)
    at index.js:69:23

Notes

Running js-waku 0.24.0.
Details for libp2p dependencies:
│ ├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ │ ├──<EMAIL_ADDRESS>deduped
│ ├─┬<EMAIL_ADDRESS>│ │ ├──<EMAIL_ADDRESS>deduped
│ ├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ │ ├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ │ ├──<EMAIL_ADDRESS>deduped
│ │ ├──<EMAIL_ADDRESS>deduped
│ │ ├──<EMAIL_ADDRESS>deduped
│ │ ├──<EMAIL_ADDRESS>deduped

It also doesn't work from 0.21.0 to 0.23.0 or with { boostrap: { default: true } }, so probably linked to my ViteJS config...

I believe it is fixed with js-waku@next, right?

I believe it is fixed with js-waku@next, right?

Absolutely, although it would still be nice to figure out why it doesn't work with previous versions anymore, so it doesn't happen again. Maybe dependency pinning?

I believe it is fixed with js-waku@next, right?

Absolutely, although it would still be nice to figure out why it doesn't work with previous versions anymore, so it doesn't happen again. Maybe dependency pinning?
For example, this project from 4 months ago doesn't work anymore despite nothing having changed: swarmcity/shortcodes-demo
git clone https://github.com/swarmcity/shortcodes-demo[](https://github.com/swarmcity/shortcodes-demo)
cd shortcodes-demo
npm i
npm run dev

It's not the same error I believe, but it still doesn't work anymore.

Some of js-waku's dependencies have mis-managed version bumping and introduced breaking changes in patch/minor bump.
Hence, such behaviour has been encountered.
I am not sure there is much I can do from js-waku PoV as I already check in the package-lock.json file. Thoughts?

Maybe using version override or locking in the package.json file would help.

Won't fix because we do not guarantee support for older versions in this phase of development.


Reflection for agent

How can I be using crewai to make the agents to reflect/learn from its own output? Do I have to use crewai in conjunction with langgraph?
Example case is a code monkey agent write a Python code, then the tester would test and check the errors. It will inform the code monkey agent of the error and it would rewrite it. Another example perhaps a writer agent that rewrite based on the feedback by editor agent.

Do I have to use crewai in conjunction with langgraph?

That's correct. It may not be the only solution, but it is the most effective and well-tested one.
https://www.youtube.com/watch?v=5eYg1OcHm5k&t=132s


Different mageck count normalization methods give same results

Dear,
I have encountered an issue where I run mageck count on a group of fastas with different normalization methods and the results are identical, to the point that md5sum gives me the same code for the normalized output files (...counts_normalized.txt).
The normalization methods are "median" vs "control". I provided --control-sgrna flag when using "control" normalization.
Here the code:
# Median Normalization
mageck count
--pdf-report
-l sgRNA_library.tab
-n mageck_trim0_controlsgrnaFalse_normmedian
--norm-method median
--sample-label TLA{1-15}_Top,
--fastq ./{1-15}.fastq
--trim-5 0

# Control Normalization
mageck count
--pdf-report
-l sgRNA_library.tab
-n mageck_trim0_controlsgrnaTrue_normcontrol
--norm-method control  **Change**
--sample-label TLA{1-15}_Top,
--fastq ./{1-15}.fastq
--trim-5 0
--control-sgrna ./non_targeting_sgrnas.tab **Change**

Notice that I run 15 samples and to avoid writting their names I am just putting {1-15}. I have also highlighted the areas that are different (Changes)
I have repeated this porcedure with the same result. Did I do something wrong?
I will be happy to provide further information if needed. Thank you in advance

They actually give differnt results. However i could only see this after running md5sums on the outputs.
The two normalization methods gave almost the same results with only differences in the milesims of the lfchanges.
Not enough for the p-values to change even the slightest.


五通道图片设置报错

RuntimeError: Given groups=1, weight of size [16, 3, 3, 3], expected input[1, 5, 256, 256] to have 3 channels, but got 5 channels instead

你好，这个不支持5通道，特殊通道需要修改代码，具体教程看知乎https://zhuanlan.zhihu.com/p/716419187?utm_psn=1828485661373624320
万达航
@.***
签名由 网易灵犀办公 定制
Original:
From:Leng< @.>Date:2024-10-12 17:21:03To:wandahangFY/YOLO-MIF< @.>Cc:Subscribed< @.>Subject:[wandahangFY/YOLO-MIF] 五通道图片设置报错 (Issue #4)
RuntimeError: Given groups=1, weight of size [16, 3, 3, 3], expected input[1, 5, 256, 256] to have 3 channels, but got 5 channels instead
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.>


Empty file

Is there any reason why the file is empty?

Thanks for your report and sorry for any inconvenience.
We have fixed this issue. Please update the latest version or rollback to previous.
Magento removed a server related to Crowdin.
We have build a new server to resolve the problem.
To help Magento community, feel free to translate this language pack in Crowdin


AspNET tutorial fails due to the scope defined.

The file /Views/Shared/_Layout.cshtml has defined the scope to get the entire profile and sometimes it fails. To ensure that the seed project always works, the scope should be changed to get only 1 field just like the tutorial specifies.

@fiannolo The ASP.NET tutorial has been completely reworked, and in the new format it includes the correct HTML/JavaScript in the tutorial
Please see https://auth0.com/docs/quickstart/webapp/aspnet-owin
Let me know if you still have issues


How can i add an option to the "convert to"

Currently it looks like:

Lets say i want to add Vanilla JS. How can i do that?
Best

Found it.
Only thing i have to do is to edit the history.ts correct?

Yep, that should do it.  However I'm not sure vanilla JS would really make sense here.  The model generates HTML and vanilla JS by default so there shouldn't need to be any conversion.  The values in history.ts ultimately get sent to a an LLM with the prompt: Please turn this into a ${framework} component. and then it provides the existing HTML and javascript generated so I can't really imagine any conversion happening in the Vanilla JS case.


bug: high CPU usage

Prerequisites

[X] I have searched for existing issues that already report this problem, without success.

Version
0.1.4
Current Behavior
the cpu usage gets pretty high and drains battery when discord isn't open
Expected Behavior
the cpu usage shouldn't be that high
Steps to Reproduce

enable brew service of xcode discord rpc
wait a while after discord is either stuck loading or closed
cpu usage goes high and kills battery

Additional Information
No response

Thank you for reporting this. I will try to find ways to reduce CPU and battery usage, especially when Xcode isn't running.

Please take a look at release v0.1.6. I've increased the wait time from 5 seconds to 30 seconds. This should somewhat reduce the CPU usage.

The CPU usage has gone down substantially since 0.1.6.
Even with an M1 Pro, it was struggling to keep up haha 😅
thanks for all you do, man this plugin fills a gap the xcode community needed

@blackxfiied Thank you for the kind words and the star!!


great-theorems:0.1.1

I am submitting

[ ] a new package
[x] an update for a package

Description: Create theorem/proof environments.
I have read and followed the submission guidelines and, in particular, I

[x] selected a name that isn't the most obvious or canonical name for what the package does
[x] added a typst.toml file with all required keys
[x] added a README.md with documentation for my package
[x] have chosen a license and added a LICENSE file or linked one in my README.md
[x tested my package locally on my system and it worked
[x] excluded PDFs or README images, if any, but not the LICENSE

Thanks :)


Exaggerated vibration when hovering with Solo gazebo simulation

Hi. I've noticed that there is a huge vibration in "roll" when launching the default 3DR Solo Gazebo PX4 SITL simulation with make posix gazebo_solo I've tested it in two different computers, getting the same issue. However, the 3DR Iris simulation doesn't have such exaggerated vibration.
I've uploaded a video showing the vibration here
Is it a code "bug" or a PX4 parameter (noise-related) that is incorrectly set? Default values are used in all 3DR Solo and Iris parameters and in PX4.
Note:  I've opened this same issue #275  in the sitl_gazebo repository, but as I'm not sure if it has to be with the SITL simulation itself, with Gazebo or with PX4, I'm replicating it here.
Thanks in advance!
$make posix gazebo_solo
ninja: Entering directory `/home/diego/Firmware/build/px4_sitl_default'
[2/6] Performing configure step for 'sitl_gazebo'
-- install-prefix: /usr/local
-- Boost version: 1.58.0
-- Found the following Boost libraries:
--   system
--   thread
--   timer
--   chrono
--   date_time
--   atomic
-- Boost version: 1.58.0
-- Building klt_feature_tracker without catkin
-- Building OpticalFlow with OpenCV
-- catkin DISABLED
Gazebo version: 7.0
-- Using C++14 compiler
-- Configuring done
-- Generating done
-- Build files have been written to: /home/diego/Firmware/build/px4_sitl_default/build_gazebo
[3/6] Performing build step for 'sitl_gazebo'
ninja: no work to do.
[6/6] cd /home/diego/Firmware/build/px.../diego/Firmware/build/px4_sitl_default
SITL ARGS
sitl_bin: /home/diego/Firmware/build/px4_sitl_default/bin/px4
debugger: none
program: gazebo
model: solo
src_path: /home/diego/Firmware
build_path: /home/diego/Firmware/build/px4_sitl_default
GAZEBO_PLUGIN_PATH :/home/diego/Firmware/build/px4_sitl_default/build_gazebo
GAZEBO_MODEL_PATH :/home/diego/Firmware/Tools/sitl_gazebo/models
LD_LIBRARY_PATH /home/diego/catkin_ws/devel/lib:/opt/ros/kinetic/lib:/opt/ros/kinetic/lib/x86_64-linux-gnu:/home/diego/Firmware/build/px4_sitl_default/build_gazebo
Gazebo multi-robot simulator, version 7.0.0
Copyright (C) 2012-2016 Open Source Robotics Foundation.
Released under the Apache 2 License.
http://gazebosim.org
[Msg] Waiting for master.
[Msg] Connected to gazebo master @ http://<IP_ADDRESS>:11345
[Msg] Publicized address: <IP_ADDRESS>
[Dbg] [gazebo_mavlink_interface.cpp:137] <joint_name> not found for channel[0] no joint control will be performed for this channel.
[Dbg] [gazebo_mavlink_interface.cpp:137] <joint_name> not found for channel[1] no joint control will be performed for this channel.
[Dbg] [gazebo_mavlink_interface.cpp:137] <joint_name> not found for channel[2] no joint control will be performed for this channel.
[Dbg] [gazebo_mavlink_interface.cpp:137] <joint_name> not found for channel[3] no joint control will be performed for this channel.
[Msg] Conecting to PX4 SITL using TCP
[Msg] Lockstep is enabled
[Msg] Speed factor set to: 1
SITL COMMAND: "/home/diego/Firmware/build/px4_sitl_default/bin/px4" "/home/diego/Firmware"/ROMFS/px4fmu_common -s etc/init.d-posix/rcS -t "/home/diego/Firmware"/test_data
INFO  [px4] Creating symlink /home/diego/Firmware/ROMFS/px4fmu_common -> /home/diego/Firmware/build/px4_sitl_default/tmp/rootfs/etc
0 WARNING: setRealtimeSched failed (not run as root?)

| ___ \ \ \ / /   /   |
| |/ /  \ V /   / /| |
|  __/   /   \  / /| |
| |     / /^\ \ ___  |
_|     /   /     |_/
px4 starting.
INFO  [px4] Calling startup script: /bin/sh etc/init.d-posix/rcS 0
INFO  [dataman] Unknown restart, data manager file './dataman' size is 11405132 bytes
INFO  [simulator] Waiting for simulator to connect on TCP port 4560
INFO  [simulator] Simulator connected on TCP port 4560.
[Msg] Using MAVLink protocol v2.0
Gazebo multi-robot simulator, version 7.0.0
Copyright (C) 2012-2016 Open Source Robotics Foundation.
Released under the Apache 2 License.
http://gazebosim.org
[Msg] Waiting for master.
[Msg] Connected to gazebo master @ http://<IP_ADDRESS>:11345
[Msg] Publicized address: <IP_ADDRESS>
INFO  [init] Mixer: etc/mixers/quad_x.main.mix on /dev/pwm_output0
INFO  [mavlink] mode: Normal, data rate: 4000000 B/s on udp port 14570 remote port 14550
INFO  [mavlink] mode: Onboard, data rate: 4000000 B/s on udp port 14580 remote port 14540
INFO  [logger] logger started (mode=all)
INFO  [mavlink] MAVLink only on localhost (set param MAV_BROADCAST = 1 to enable network)
INFO  [logger] Start file log (type: full)
INFO  [logger] Opened full log file: ./log/2019-02-03/21_57_38.ulg
INFO  [px4] Startup script returned successfully
pxh> INFO  [mavlink] partner IP: <IP_ADDRESS>
INFO  [ecl/EKF] EKF aligned, (pressure height, IMU buf: 22, OBS buf: 14)
[Wrn] [Publisher.cc:140] Queue limit reached for topic /gazebo/default/solo/motors, deleting message. This warning is printed only once.
[Wrn] [Publisher.cc:140] Queue limit reached for topic /gazebo/default/solo/motor_speed/0, deleting message. This warning is printed only once.
[Wrn] [Publisher.cc:140] Queue limit reached for topic /gazebo/default/solo/motor_speed/1, deleting message. This warning is printed only once.
[Wrn] [Publisher.cc:140] Queue limit reached for topic /gazebo/default/solo/motor_speed/2, deleting message. This warning is printed only once.
[Wrn] [Publisher.cc:140] Queue limit reached for topic /gazebo/default/solo/motor_speed/3, deleting message. This warning is printed only once.
INFO  [ecl/EKF] EKF GPS checks passed (WGS-84 origin set)
INFO  [ecl/EKF] EKF commencing GPS fusion
INFO  [commander] Takeoff detected
INFO  [commander] Landing detected
INFO  [logger] closed logfile, bytes written: 6395899

Thanks for raising this and sorry about the late response. Did you ever fix this?
I assume that this could be fixed with control tuning. Did you ever attempt that?

Hi Juliano.
Thanks for your reply. No, I didn't fix the issue, but actually I never tried to retune the control PIDs, I worked with the default values. I'll give it a try!


Client should handle 502 errors

Describe the bug
The unleash server can return the following error when polling for features (poll_for_update()):
\n\n<meta http-equiv=\"content-type\" content=\"text/html;charset=utf-8\">\n<title>502 Server Error</title>\n\n\n
Error: Server Error
\n
The server encountered a temporary error and could not complete your request.
Please try again in 30 seconds.
\n

\n\n

The client currently naively tries to convert the returned body into json, fails, then dumps the error and proceeds as if an unrecoverable error happened, by not updating the features until the next poll interval/
This should be easily fixable by inspecting the response's status code and reacting to a 502, before converting it into a json.
Steps to reproduce the bug
Unfortunately I am unsure as to how to reproduce the error, as it may have something to do with specific server configurations or even the environment. However, it might be possible to mock the response from the server.
Expected behavior
Unleash client should probably retry the request as said by the server.
Logs, error output, etc.
No response
Screenshots
No response
Additional context
No response
Unleash version
Client: 0.6.1 alpha
Server: 3.17.6
Subscription type
Open source
Hosting type
Self-hosted
SDK information (language and version)
No response

Hey, thank you for bringing this to our attention. We will raise it internally and get back to you with a response from the team.
In the meantime, can you provide us with some additional information to help reproduce it:

Server configuration
Environmant configuration

Upon investigation, the conditions for this error being returned does indeed depend on non-Unleash software: The Unleash server was hosted on a Kubernetes cluster behind a Google load balancer. The server was being CPU-throttled and the load balancer returned the 502 message.
Still, it might be good to have some better handling of server errors.

Hey, @skairunner 👋🏼
Thanks again for raising this! Let me just make sure I get this right:

When the client receives a 502 response, it logs an error, then continues running. It will try fetching toggles again at the next interval.
When it receives a 502, you'd like/expect it to retry the toggle request after the specified interval.

Are those points correct?
We've talked briefly about this internally, and I think the reason it works the way it does is intentional. There's not much the SDK can do if it receives an error response, and it'll try again after the specified refresh interval anyway. In cases where you need to get updates immediately, you're probably best off bumping up the refresh rate.
Does that sound reasonable to you?

Still, it might be good to have some better handling of server errors.

That's a fair point! What would you classify as "better handling" in this case? What would you expect? ☺

Got it! In that case I'll close this for now ☺ I think getting some more information would be good though; maybe it's something that can be worked into #36?


Added implementation to support EventHubBufferedProducerClient

Implemented my own ask from #3832 to support the EventHubBufferedProducerClient in addition to the EventHubProducerClient as part of the Aspire DI registration.
Microsoft Reviewers: Open in CodeFlow

@WhitWaldo - it looks like the tests are failing. Can you fix them?

@sebastienros - can you take a look at this?

👋 @WhitWaldo - I'm looking at the same piece of functionality missing. Would you intend to bring this up to date, or are you ok with someone else updating it?

@skolima I can bring it up to date over the weekend. It just fell off my radar!

This has been updated and should be ready to go now!

@sebastienros - can you take a look?

All Aspire.Azure.Messaging.EventHubs.Tests are passing on my system and I believe I've spoken to each of the reviews above.

I think the only thing missing is updating the README to list the new client/settings. Just do a quick search for ProducerClient for the missing mentions.

@WhitWaldo I did the required changes in the README.

/azp run

Multiple tests failing like this (log):
Aspire.Azure.Messaging.EventHubs.Tests.AspireEventHubsExtensionsTests.CanAddMultipleKeyedServices(clientIndex: 2) [FAIL]
  System.InvalidOperationException : No service for type 'Azure.Messaging.EventHubs.EventProcessorClient' has been registered.
  Stack Trace:
       at Microsoft.Extensions.DependencyInjection.ServiceProvider.GetRequiredKeyedService(Type serviceType, Object serviceKey, ServiceProviderEngineScope serviceProviderEngineScope)
       at Microsoft.Extensions.DependencyInjection.ServiceProvider.GetRequiredKeyedService(Type serviceType, Object serviceKey)
       at Microsoft.Extensions.DependencyInjection.ServiceProviderKeyedServiceExtensions.GetRequiredKeyedService(IServiceProvider provider, Type serviceType, Object serviceKey)
    /_/tests/Aspire.Azure.Messaging.EventHubs.Tests/AspireEventHubsExtensionsTests.cs(259,0): at Aspire.Azure.Messaging.EventHubs.Tests.AspireEventHubsExtensionsTests.RetrieveClient(Object key, Int32 clientIndex, IHost host)
    /_/tests/Aspire.Azure.Messaging.EventHubs.Tests/AspireEventHubsExtensionsTests.cs(361,0): at Aspire.Azure.Messaging.EventHubs.Tests.AspireEventHubsExtensionsTests.CanAddMultipleKeyedServices(Int32 clientIndex)
       at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
       at System.Reflection.MethodBaseInvoker.InvokeDirectByRefWithFewArgs(Object obj, Span`1 copyOfArgs, BindingFlags invokeAttr)
Aspire.Azure.Messaging.EventHubs.Tests.AspireEventHubsExtensionsTests.CanAddMultipleKeyedServices(clientIndex: 3) [FAIL]
  System.InvalidOperationException : No service for type 'Azure.Messaging.EventHubs.Primitives.PartitionReceiver' has been registered.
  Stack Trace:
       at Microsoft.Extensions.DependencyInjection.ServiceProvider.GetRequiredKeyedService(Type serviceType, Object serviceKey, ServiceProviderEngineScope serviceProviderEngineScope)
       at Microsoft.Extensions.DependencyInjection.ServiceProvider.GetRequiredKeyedService(Type serviceType, Object serviceKey)
       at Microsoft.Extensions.DependencyInjection.ServiceProviderKeyedServiceExtensions.GetRequiredKeyedService(IServiceProvider provider, Type serviceType, Object serviceKey)
    /_/tests/Aspire.Azure.Messaging.EventHubs.Tests/AspireEventHubsExtensionsTests.cs(259,0): at Aspire.Azure.Messaging.EventHubs.Tests.AspireEventHubsExtensionsTests.RetrieveClient(Object key, Int32 clientIndex, IHost host)
    /_/tests/Aspire.Azure.Messaging.EventHubs.Tests/AspireEventHubsExtensionsTests.cs(361,0): at Aspire.Azure.Messaging.EventHubs.Tests.AspireEventHubsExtensionsTests.CanAddMultipleKeyedServices(Int32 clientIndex)
       at InvokeStub_AspireEventHubsExtensionsTests.CanAddMultipleKeyedServices(Object, Span`1)
       at System.Reflection.MethodBaseInvoker.InvokeWithOneArg(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)

Multiple tests failing like this (log):

Out of curiosity, is there any way to access that log without being a part of Microsoft? The tests passed locally but I saw the bot report a failure and I couldn't figure out how to access the log myself.

Multiple tests failing like this (log):

Out of curiosity, is there any way to access that log without being a part of Microsoft? The tests passed locally but I saw the bot report a failure and I couldn't figure out how to access the log myself.

Are you not able to access that link? I pasted the failures here anyway - https://gist.github.com/radical/1f55987361a1a828b3ed888b081e2dbe .

When I ran the tests locally, I believe I ran them against the wrong branch. Re-resolved the comments above on the correct branch this time and fixed the unit tests + added inline tests for the new class to the mix. Now, they're all passing locally.

Multiple tests failing like this (log):

Out of curiosity, is there any way to access that log without being a part of Microsoft? The tests passed locally but I saw the bot report a failure and I couldn't figure out how to access the log myself.

Are you not able to access that link? I pasted the failures here anyway - https://gist.github.com/radical/1f55987361a1a828b3ed888b081e2dbe .

I can access the link you provided, but is there any way to access those logs from the failed check itself (e.g. assuming I don't have access to the azdo environment)?

< snip />
I can access the link you provided, but is there any way to access those logs from the failed check itself (e.g. assuming I don't have access to the azdo environment)?

When the checks complete then you can see the details, and links to the failures in Build Analysis  under Checks.


olaris-server: 0.4.0 -> unstable-2022-06-11

Description of changes
As called out in the linked issue below, olaris-server has a runtime dependency on ffmpeg. Unfortunately, 0.4.0 requires a custom fork of ffmpeg. While we could fetch the upstream compiled artefact or build it ourselves, the former was unpalatable and the latter prohibitively difficult. As such, we have bumped to the, yet to be released, tip of the default branch, which has merged support for upstream ffmpeg.
Fixes #207877
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/1605

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

1 package built:

olaris-server


More question rather than issue.

Is there any way to add multiple images at once with this plugin?

Hi, the project is currently under transition, I am waiting to have the admin rights on pub.dev to publish the 2.0.0 update, for the time being tout can use this transitory package https://pub.dev/packages/image_picker_web_redux which is a fork from this repo with the multi image picker.

Hi, the project is currently under transition, I am waiting to have the admin rights on pub.dev to publish the 2.0.0 update, for the time being you can use this transitory package https://pub.dev/packages/image_picker_web_redux which is a fork from this repo with the multi image picker.

thanks a lot, mate.


Intercept getters (and setters) in Groovy closures

Groovy creates a different signature for getters in closures, e.g.:
tasks.register("myCheckstyle", Checkstyle) {
      maxErrors = 2
      int currentMaxErrors = maxErrors // <- getter call here
      assert currentMaxErrors == 2
}

We currently don't intercept that. Lets improve our logic and fix that.

Progress in https://github.com/gradle/gradle/pull/24949

Done in #24949.


Improve the documentation structure for installation

[x] Make sure that documentation is sufficient for osx/linux installations (e.g. note the libraries that are needed in osx vs linux)
[x] Maybe try to reduce the amount of clicking through pages/links

Suggested docs structure:

Introduction: mission statement of Forseti Security
Installation

Local installation
Deployment to GCP

Modules (in depth)

one main section per module, with sub-modules if necessary

Formatting/styling aside is there anything else to do here @carise @blueandgold

Structurally, looks better to me.  Not as much layering as before.  But each section is longer.  Is less confusion than before.  :)
Also, will we get navigation sidebars, instead of just a TOC?

Thanks. I'm going to close this for now as we have better plans in the works for the things you mention.


Use LruCacheMap for StoreRecord, default capacity=100

Nice!
I'd like to ensure the evicted stores don't cause any troubles.
Would you mind setting the capacity to 1 and run tests locally to see how it goes?
@galganif please confirm that the evicted stores don't cause any surprises like missing model update notifications, references gone invalid suddenly, etc.

Nice!
I'd like to ensure the evicted stores don't cause any troubles.
Would you mind setting the capacity to 1 and run tests locally to see how it goes?
@galganif please confirm that the evicted stores don't cause any surprises like missing model update notifications, references gone invalid suddenly, etc.

Yeah, I'll run a test with cap=1 with the memory test and do a heap dump measurement as well

@galganif please confirm that the evicted stores don't cause any surprises like missing model update notifications, references gone invalid suddenly, etc.

I think this is fine, if a store is missing from the map it can get re-created without problems. I agree with Ian it would be good, alongside the memory app, to run normal unit tests with cap=1. Eg set cap=1 in this pr to confirm gcb and copybara are happy, then revert it before merging.

/gcbrun


README: add signature-validator & MPCvsAA talk

Added the signature-validator library, which can validate ECDSA, EIP-1271 and EIP-6492 signatures
Furthermore, added my talk at ETHPrague on MPC vs AA and how they compare and complement each other

hey @randomishwalk @keon, conflicts have now been resolved, can we get this merged please, signature-validator is super important for ERC-1271 and ERC-6492 adoption


Add option to mark unread

Not tested, but it should work

That button would just act as the "Reset read date" button like this, though.

Yeah I just realised that.
How would I change that?

Yeah I just realised that.
How would I change that?

It would probably require changing the way marking as read currently works

In general, you could probably just pin posts you want to leave unread.


Add delay when accessing unauthorized ReST endpoints

I figured I'd create this for #81, now that we are updated.  I don't know what the long term solution is, but this may be a start...

This is an initial temporary fix for #81
When logging in or accessing a restricted ReST endpoint with invalid credentials,
the system shall delay before responding.
Note that this is not a great fix, since hackers could distribute their requests across CPUs.
Resolve #81

EDIT: We discussed using a middleware solution. Feel free to discard this pull request...

I think we should add this quick-fix in for now, and convert it to middleware after the v0.8.0 release. We can include this in the 0.7.0 release. The 0.7.0 release will be a mini auth update. Do you have any other quick auth updates you'd like to include before I publish it? It's best if we leave as much until after the 0.8.0 release as possible, since the middleware makes for a much cleaner, reusable pattern. I'll review this now.

I do not have any other updates.
Thanks much.
On Jun 16, 2015 11:57 AM, "Kahmali Rose"<EMAIL_ADDRESS>wrote:

I think we should add this quick-fix in for now, and convert it to
middleware after the v0.8.0 release. We can include this in the 0.7.0
release. The 0.7.0 release will be a mini auth update. Do you have any
other quick auth updates you'd like to include before I publish it? It's
best if we leave as much until after the 0.8.0 release as possible, since
the middleware makes for a much cleaner, reusable pattern. I'll review this
now.
—
Reply to this email directly or view it on GitHub
https://github.com/kahmali/meteor-restivus/pull/83#issuecomment-112496725
.

While reviewing this I realized that the 403 errors we returned in the last update are inaccurate. We should be returning a 401 whenever authentication fails. 403s should be reserved for permission errors. We should fix those (in a separate PR maybe).

I left a few comments, but I've run out of time for now and will need to finish the last of the review tonight.

I tend to agree, 403 is for permission errors. In either case, 401 or 403, we should delay, so I suspect my original code is still ok.

Your commit message must be wrapped at 72 chars. Also, I would remove the last bullet point (it kind of contradicts the first), and move the first bullet point to the bottom (to get to the good stuff first :D).

I left some minor comments, but other than those, LGTM.

I will update the commit message to 72 chars.
I would prefer that the length to be longer, but its ok... (72 chars harkens back to the DOS days, and we now have wide screen monitors, etc...)

I use a 100 char line limit in all my other files (and will update the markdown convention to use no line limit at all), so I tend to agree, but 72 chars is a widely adopted standard for git messages that I've come to accept. I suppose in future projects I may be convinced to extend the line limit, but for now it's just a convention to allow consistency when reading through the commit history.
I've reviewed everything here and it looks great to me. I'll go ahead and pull this in. I just need to update the README with a warning about the token invalidation, and then I'll bump the version and publish. I'll keep you posted on that.


Move from willRemove to willDestroy

willRemove was deprecated in favor of willDestroy in ember-modifier 2.0. We should deprecate support for ember-modifier 1.0 and move to the willDestroy hook.
https://github.com/ember-modifier/ember-modifier#api

Done.


produce_response.go: Remove Unused Functions

This removes two unused functions from the root sarama package.

I read this failure as a flake, is it a common one?

thanks!


Run background refresh only if initial refresh succeeds.

Defer func for background goroutine has been also removed because it's not necessary and may be fired straight away.
This fixes panic: runtime error: invalid memory address or nil pointer dereference in case of unavailable or invalid JWKs server in the time of initialization.

Hi @MicahParks , thank you for this library.
Unfortunately I've noticed (panicking) issue in case when JWKs server is invalid or unavailable during initialization.
Problematic is defer func executing background refresh:
https://github.com/MicahParks/keyfunc/blob/43e953dc9b4698b97fb800d2477881cbbbe34942/get.go#L45-L48
If call of jwks.refresh() fails, the Get functions returns and mentioned defer is triggered:
https://github.com/MicahParks/keyfunc/blob/43e953dc9b4698b97fb800d2477881cbbbe34942/get.go#L51-L54
Defer executes pointer receiver *JWKS.backgroundRefresh(). But it's triggered after the function returns. And in that case value where we point to (jwks) does not exist anymore and pointer in the function points to nil. And we got the panic in *JWKS.backgroundRefresh() because j identifier points to nil and nil does not contain refreshInterval:
https://github.com/MicahParks/keyfunc/blob/43e953dc9b4698b97fb800d2477881cbbbe34942/get.go#L66
I've added test covering exactly this problem and confirming fix.

@hranicka Thank you for this PR. The code, discussion, and test are all quality. Also, I'm always glad to be thanked for open source projects.
I'd never want this package to be the cause of a Go panic. This PR gets rid of a scenario where that can happen. I'll merge it immediately.

Thank you for such fast response :)

@DewaldV you may be interested in this change if your fork is still active.


Fix a bug in FloatDimensionIndexer.makeObjectColumnSelector()

It used to return object of type Long, instead of Float.

LGTM

can we add a unit test to make sure that this will not happen again ?

Changes look good to me, although relating to b-slim's point about testing:
DimensionIndexer.makeObjectColumnSelector() isn't actually called anywhere right now (IncrementalIndexStorageAdapter.makeObjectColumnSelector() uses DimensionIndexer.convertUnsortedEncodedKeyComponentToActualArrayOrList() instead)
I think we could actually remove makeObjectColumnSelector() method from DimensionIndexer

I think we could actually remove makeObjectColumnSelector() method from DimensionIndexer

That seems better than fixing it… no reason to keep around an unnecessary method.

Given it's not actually used, I don't think this needs to be treated as an 0.10.1 blocking bug, so I'm moving it to 0.11.0.

@jon-wei sure if it is not needed let's remove it !

Closing this since this was addressed by #4679


Using the wrong method for area calculation in SketchingConstuctionInfo.js

In the case of a geodesic area, the planarArea method is used. The other way round, the geodesicArea method is used if it is a planar area.

https://github.com/conterra/mapapps-sketching-enhanced/blob/154141255a5ad83961b373e98c7ff0dac5ea2d77/src/main/js/bundles/dn_sketchingenhanced-construction/SketchingConstructionInfo.js#L69

(/) fixed with the latest changes


Setting the subject from inside a template

It'd be really great if we'd able to set the mail's subject from inside the template similar to what $this->title() does for regular templates. That would allow us to have all the wording inside the template.

@davidpersson i think it should work, i mean there should be a title handler. I haven't touched this code for a while, so i may be missing something.

Thanks for the thorough explanation. I should've just read the README until the end...


Missing support for logical router policies

From the submariner project we use go-ovn, and we noticed that policies on routers are missing, for
now we were using ovn-nbctl. But I will be sending a patch to support policies here so we can get rid of ovn-nbctl usage.

Thanks @mangelajo


Upgrade google-cloud-cpp to v0.4.0

Just a periodic release.

This update fixes the build failures that crept in on the windows triples (yeah!), but I am seeing a new failure on x64-osx.  @ras0219-msft you mentioned that the build failures may not repro with the latest version of xcode, which makes me inclined to take this change.  What do you think?

Can you tell me more about the x64-osx failure?  That might be related to GoogleCloudPlatform/google-cloud-cpp#1593, which we fixed after the 0.4.0 release, and only affected Xcode 7.3. If that is what it is, then we should do the upgrade.

Yup, that's the one.


Difference btw tag 0.0.7 and master.

Hi, after drive me crazy trying to understand why afterShow does not trigger on the options. I checked the code on master vs release 0.0.7, and this tag, does not have this option.
Idk if is missing other options, plz, re release the tag 0.0.7 to match the current documentation with the api.

This drove me crazy, too.

I am not sure where you see a 'master', there is no branch by that name that I see. I had the same issue, though, the downloaded copy did not include any event listeners at all.
I solved the issue by copying the code from the example site and pasting it over the version I have (they are both labeled 0.0.7)

@DMeganoski you are rigth. aparently, master was deleted :confused: the main branch is gh-pages.
Usually, using releases is the way to get the last stable version. My concern is the difference between the release and the last version. But apparently @weareoutman  has their own git schema

Because, this repo is not supported anymore and we had the same issue than you. We created a fork of it here : https://github.com/linagora/clockpicker. It's available on bower under the name of lng-clockpicker.


Unhandled exception (St12out_of_range) when displaying map list window if dpk with small name is in path

I don't know from which server it comes, but if that a dpk file with a small file name is in path, the engine triggers this exception and quits:
Warn: Unhandled exception (St12out_of_range): basic_string::substr: __pos (which is 4) > this->size() (which is 2)

The only requirement to reproduce the bug seems to have this kind of file in path to crash the engine while clicking on “Start local/LAN game”:

I reproduce the bug on released 0.51.1 and master.

I noticed the error also occurs when the file is present at startup but removed from filesystem before the link is clicked.

This is a way to create a a_0.dpk that reproduces the bug:
cd ~/.local/share/unvanquished/pkg
(mkdir empty; cd empty; 7z a -tzip -mx=9 ../a_0.dpk .; cd ..; rmdir empty)

We note the issue is about a faulty range of 4, while the file base name lenght is smaller than 4. This may be related to the test for map- prefix which has a lenght of 4.

Can you get a backtrace of this? The exception should trigger gdb to stop.

I was running on gdb when I first faced it and gdb caught nothing.

Try using the command catch throw in gdb (you might want to do this after starting the application since it might throw some exceptions in normal initialization).

Creating a dpkdir is easier and enough:
mkdir -p ~/.local/share/unvanquished/pkg/a_0.dpkdir


feat!: implement QGB pruning

Overview

Closes https://github.com/celestiaorg/celestia-app/issues/309
Checklist

[ ] New and updated code has appropriate documentation
[ ] New and updated code has new and/or updated testing
[ ] Required CI checks are passing
[ ] Visual proof for any user facing features like CLI or documentation updates
[ ] Linked issues closed with keywords

Codecov Report

Merging #1799 (07fe551) into main (5443e5f) will increase coverage by 0.06%.
The diff coverage is 52.34%.

@@            Coverage Diff             @@
##             main    #1799      +/-   ##
==========================================
+ Coverage   51.60%   51.66%   +0.06%
==========================================
  Files         107      107
  Lines        6647     6784     +137
==========================================
+ Hits         3430     3505      +75
- Misses       2862     2915      +53
- Partials      355      364       +9

Impacted Files
Coverage Δ

x/qgb/genesis.go
0.00% <0.00%> (ø)

x/qgb/keeper/hooks.go
35.13% <0.00%> (-0.98%)
:arrow_down:

x/qgb/keeper/keeper_valset.go
31.15% <0.00%> (-2.70%)
:arrow_down:

x/qgb/types/keys.go
0.00% <ø> (ø)

x/qgb/keeper/keeper_data_commitment.go
38.93% <27.77%> (-2.65%)
:arrow_down:

x/qgb/keeper/keeper_attestation.go
60.91% <41.17%> (-12.67%)
:arrow_down:

x/qgb/abci.go
69.12% <76.62%> (+8.01%)
:arrow_up:

I think it might make a lot of sense to break it up into unit testable functions.

That was where I wasted a bit of time. I was trying white box testing for the pruning logic, however, we have deep cyclic dependencies with the testing setup used to run the tests... So, it got harder to test in a white box manner and had to export the PruneIfNeeded method

I will also write an integration test that runs a full blown chain that produces blocks as fast as possible, constantly changes the validator set, and sets the DCWindow to as low as possible to help with this effort. We might only be able to run it locally, but that's ok atm

I did that with the orchestrator-relayer E2E setup where I setup a chain of 4 validators and let it run for a couple of hours.  Also, I am planning on testing the whole thing using testground, but the priority now was to be in the deadline for feature freeze

Also, is there anything we can do to simplify this logic? would it be easier to just always prune after huge number of blocks? for instance, there are ~120960 blocks in the unbonding period, what if we just always prune an attestation if the height is less than (the current height - 2 *blocks in unbonding period) The features that we originally designed around seemed like a good idea at the time, but if it requires this very complex logic, then I'm not sure its worth it

Good idea, but I think we already have that way implemented. Also, pruning that way might not work all the time if we have a stable network running for multiple days without any validator set change, any validator unbonding, any validator getting jailed, etc. Then, we would end up in a scenario where we don't have all the attestations needed to deploy the QGB

opened a PR with an attempt to simplify pruning https://github.com/SweeXordious/celestia-app/pull/39 targeting this branch

@SweeXordious, quick question, why are we wanting to preserve the last unbonding validator height here? doesn't that only update when a validator gets jailed or otherwise falls out of the validator set. Why can't we prune past that?

Why can't we prune past that?

That was the first plan, then we decided to also keep a minimum number of attestations in state just in case we needed them

@SweeXordious but why is that value important? The unbonding period (3 weeks) I get, but I'm unsure about a random validator's unbonding period.
I had difficulty understanding what the gravity module was using this value for as well. It seems they're using it as a proxy for the unbonding period.

Still not sure about this initialisation problem

It's not a problem. It's just that we can do it in endBlocker, but that check would be executed every time. It's more like a gas optimization

I think we also need to test that nothing is pruned until the expiry period is reached, if all of the valsets have been pruned, we still get the existing one, and we should probably include some valset changes in the nonces that are being pruned

425b3ff and 302f9a2

@rootulp The remaining changes I will handle them in a subsequent PR. I don't want to wait another round of reviews for this one as it's taking too much time.
Thanks a lot everyone for the thorough reviews :+1: :+1:


External plugins, UI.

See the PDF posted in the slack for an overview of these changes.

Sample plugin to test with: scheduled payments.

I took a quick look and it seems ok.

What's the MD5 checksum for? How does it add any security for the user?
minimum_ec_version in the manifest should not be a float. It should be possible to specify versions like 3.1.1.

The MD5 checksum: If a third party recommends a plugin, and wants to ensure
the person they recommend it to gets a safe version, especially considering
how much power a plugin has, they can give the checksum.  Then the person
installing the plugin can verify before any code is executed, that they did
in fact download the correct version.  Given the difficulty in knowing for
sure that a plugin is really safe, it seems like it might come in handy in
this kind of way.
Good point on the version, I will fix it.
On Mon, May 14, 2018 at 4:41 AM, Johann Bauer<EMAIL_ADDRESS>wrote:

What's the MD5 checksum for? How does it add any security for the user?
minimum_ec_version in the manifest should not be a float. It should be
possible to specify versions like 3.1.1.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/fyookball/electrum/pull/674#issuecomment-388639830,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AfFyJnUARGgoZBQ8g-uOo9u7zq1XMIKiks5tyGJFgaJpZM4T8Spi
.

@bauerj I've fixed the versioning.  Now both 'minimum_ec_version' and the plugin's own 'version' are expected to be in this format.

I'm very concerned by this... Hardware wallets were not tested with the changes

Yes, I do not have a hardware wallet.
On Tue, May 15, 2018 at 1:45 AM, marceloneil<EMAIL_ADDRESS>wrote:

I'm very concerned by this... Hardware wallets were not tested with the
changes
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/fyookball/electrum/pull/674#issuecomment-388821881,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AfFyJqs5vlwgog6Jm0shHU7H7k_b9ETPks5tyYqAgaJpZM4T8Spi
.


vdirsyncer: why is there a default plus a stable?

Describe the bug
Currently, there is a default, which points to an upstream commit from 2018, and a stable, which points to the latest release, from 2020-07-09.
Why not have only default, pointing to the release?
I can do a PR, if wanted.
Notify maintainers
Pinging the maintainer and the people that made the last few commits:
@loewenheim @DamienCassou @marsam @doronbehar

Why not have only default, pointing to the release?

Because the project is not maintained very well upstream. See: https://github.com/pimutils/vdirsyncer/issues/790
However, we maintainers probably haven't followed that thread and there has been some good progress there, so it may be worth it to recheck. Feel free to make a PR if you think we can be a bit more rigorous. Personally I don't use this package nowadays so I lack a strong opinion. Unccing myself.

From what I understand (which is not much, please correct me):

At first their was one Python version of vdirsyncer that worked fine for years. Then, maintenance decreased and the package was marked as broken in nixpkgs.
The original author (@untitaker) of vdirsyncer decided to re-implement (part of) vdirsyncer in Rust. Nixpkgs made vdirsyncer point to the Rust version and renamed the Python historical version to vdirsyncerStable.
Eventually, @untitaker gave up on the Rust version.
@WhyNotHugo decided to take over maintenance of the Python version.
@marsam and I updated the vdirsyncerStable to point to the work of @WhyNotHugo and mark the package as working again.

My conclusion on what needs to be done now:

Remove pkgs/development/python-modules/vdirsyncer/default.nix;
Rename stable.nix to default.nix;
Make vdirsyncer and vdirsyncerStable point to default.nix;
Deprecate vdirsyncerStable.

This sounds correct, thanks
On Sat, Nov 7, 2020, at 11:27, Damien Cassou wrote:

From what I understand (which is not much, please correct me):

At first their was one Python version of vdirsyncer that worked fine for years. Then, maintenance decreased and the package was marked as broken in nixpkgs.
The original author (@untitaker https://github.com/untitaker) of vdirsyncer decided to re-implement (part of) vdirsyncer in Rust. Nixpkgs made vdirsyncer point to the Rust version and renamed the Python historical version to vdirsyncerStable.
Eventually, @untitaker https://github.com/untitaker gave up on the Rust version.
@WhyNotHugo https://github.com/WhyNotHugo decided to take over maintenance of the Python version.
@marsam https://github.com/marsam and I updated the vdirsyncerStable https://github.com/NixOS/nixpkgs/pull/91918 to point to the work of @WhyNotHugo https://github.com/WhyNotHugo and mark the package as working again.
My conclusion on what needs to be done now:

Remove pkgs/development/python-modules/vdirsyncer/default.nix;
Rename stable.nix to default.nix;
Make vdirsyncer and vdirsyncerStable point to default.nix;
Deprecate vdirsyncerStable.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/NixOS/nixpkgs/issues/103026#issuecomment-723428168, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGMPRJBHP2JNZWAI33BVE3SOUOIZANCNFSM4TM4UZ6Q.

OK, I'll do a PR then.
Thanks for clearing it up, @DamienCassou and @untitaker!

PR here: https://github.com/NixOS/nixpkgs/pull/103073
@DamienCassou When I tried to implement your comment, I noticed I didn't fully understand it: vdirsyncerStable doesn't point to default.nix in my PR, but just throws a message instead.  If that is not OK, please tell me what I should do.


Broken in Django 1.10

Changes in Django 1.10 means MIDDLEWARE_CLASSES now becomes MIDDLEWARE.
password_policies.middleware.PasswordChangeMiddleware now broken:
in load_middleware
    mw_instance = middleware(handler)
TypeError: object() takes no parameters

https://docs.djangoproject.com/en/1.10/topics/http/middleware/#upgrading-pre-django-1-10-style-middleware
All it seems to need is:
from django.utils.deprecation import MiddlewareMixin

class PasswordChangeMiddleware(MiddlewareMixin):

Tested, and seems fine.

See PR #59 comments...

Hey @tarak, I love your app, any chances of supporting Django 1.10 soon? Thanks!

Any plans to merge pull request https://github.com/tarak/django-password-policies/pull/63 to address this issue?

What's up here @tarak ? We are looking to migrate to 1.11...

I suggest to update package and follow https://www.djangoproject.com/download/
Supported Django versions: Django 1.8 LTS, 1.10, 1.11 LTS.
For now looks like this package is broken in 66,67% of supported configurations...

There's pull request for that. @tarak , if you're no longer interested in maintaining the package perhaps it would be wise to consider passing the maintainership to someone... unless someone forks it

Just to let you know, I've e-mailed @tarak and asked him to give me commit privs to the repo and to the PyPI package, I'm willing to maintain it.

@mpasternak @tarak
What is the status of this?

I’ve received no reply at all.

Django 2.0 requires on_delete argument to ForeignKeys, so I guess I'm going to prepare a fix in my branch.

This project is dead guys, @tarak is just not professional enough to mention us he doesn't want to work on it anymore and too lazy to give the maintainer role to someone else. Seriously, just fork this project and we will all adopt it.

Hi,
I have forked the project and I continue the work in my fork: https://github.com/iplweb/django-password-policies-iplweb
Feel free to report any issues, patches, docs improvements also badly needed.
I'm using this in a commercial project so I guess I'll maintain my fork for a few years at least.


Get df.md to use pypi RF library & optimize. Why: show DFers how to optimize against it

Background:

Pre-requisite: df-py#382 is "Move calcrewards.py into its own pypi lib. Why: unlock DFers optimizing on it".
This issue is a follow-up.

TODOs

[ ] Change df.md to point to library to get RF. Treat RF as an objective function, and run an optimization on it to allocate rewards. (Use an off-the-shelf optimizer, eg one from scikit learn, or maybe Yuret)

Super-low priority compared to other stuff, esp given Predictoor. Closing, to reduce # github issues


Pass additionalInputs to EvaluateRule Action

I keep getting the error "Unkown identifier - MyAdditionalInputName"  when I try to pass computed additionalInput to EvaluateRule Action
Could you please provide a clear example of how to use this feature properly ?

@knjeckil  can you share sample code to reproduce this issue?


[DO NOT MERGE] Auto PR to update dependencies of pilot

This PR will be merged automatically once checks are successful.
none

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/pilot-presubmit.sh
99e077e3907d7e02331f2bab713640ac938604a0
link
/test pilot-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


When installing Enso on Windows we need to check for the VC++ Runtime

If the Visual C++ Runtime is not present the GraalVM runtime will not work and will error and the language server will fail to start as the gu command will fail.
Need to install https://aka.ms/vs/17/release/vc_redist.x64.exe to get it to work if not present.

@mwu-tow is that something you could tackle?

Oh, we should not require users to install VS C++ Runtime. Can we bundle it in the package somehow? What's the standard way of doing that? CC @mwu-tow

@wdanilo
This is strange. From what I've seen, the GraalVM is already shipping the necessary binaries. We should not need additional packaging nor rely on user-provided runtime.
@jdunkerley How is the language server spawning the gu? Does it use the cmd script wrapper? This might be just a matter of adjusting cwd or PATH.

Ok, good to know that @mwu-tow! In such a case this needs to be investigated and fixed in such a way that it just works for users without this runtime.

This is presumably working and covered by https://github.com/enso-org/enso/pull/4019.
If the new information is available, the binaries should be packaged where needed (as was done elsewhere) rather than expected to be provided by the user.


remove devtoolset-5 from cais compute playbook

Removed the play that installs devtoolset-5.

We also need to uninstall it on prod because it is installed.

@steven-basart
I didn't manually remove from prod. If the cais compute playbook has been modified it wasn't a change that I made.

I wrote a short Ansible Playbook to check whether dev toolset-5 is installed on any of our nodes:

name: Check if devtoolset-5 is installed
hosts: login,bastion,slurm_backup,compute
become: true
tasks:

name: Gather the package facts
ansible.builtin.package_facts:
manager: auto
name: Check whether a package called devtoolset-5 is installed
ansible.builtin.debug:
msg: "{{ ansible_facts.packages['devtoolset-5'] | length }} versions of devtoolset are installed!"
when: "'devtoolset-5' in ansible_facts.packages"
Basically, the second play will execute if we have dev toolset-5 installed otherwise it is skipped.


Merge in

(originally created by @304NotModified)
Proposal to merge from other forks:

[ ] Support for pushing to authenticated NuGet feed
[ ] Include default credentials in web requests
[ ] Fallback to Packages() service for all versions

@rikoe can you check this?

Will do soon. Thanks for reminding me.

OK Cool :)
Like to release it after it.

@rikoe any idea when you have time for this?
Thanks in advance!

Hi - sorry, we've had a baby recently so struggling to find time. Will try to do it by Wednesday.

@rikoe any success with finding some time?

Hi @304NotModified I have just started pulling the latest code to try and get this done, and have just seen that you have created some branches of your own for this (based on my implementation, or your own, I haven't checked)
I can't really complain  about this, as I did not respond to your previous message and it has been a while since I last said I would try to find some time.
Would you like to continue on on your own, or should I create a PR for these features based on my earlier work?

A PR would be great!
I was indeed working on this, but I have difficulties to test it as I don't have the environment to test it.

Testing is the real problem, as I don't have a similar environment with Windows Authentication as when I set this up any more. I have submitted the PR but it needs to be tested so maybe leave it open. I have to see whether I can set up a VM to do it or maybe test it at work.
Anyway, this is all I could manage for today :smile:

Fixed by #49


add map example

This is the map example added in to Math folder and  taken from Processing Website

Thanks @Imccart for review the pr. I'm trying to make changes soon that you suggest me.

hi, @imccart I have lost the data of .hbs file that's why I made the changes in another pr


master: Update readEventLogs to support old Event format

Previously Status was stored as an int and could possibly be set to -1.
Signed-off-by: Kenfe-Mickael Laventure<EMAIL_ADDRESS>--
Simply cherry-picked the v0.2.4 branch commit.

ping @crosbymichael
It's the exact same patch, but a second pair of :eyes: has never hurt.

LGTM


QUESTION is flex slider_init.js still required?

Since we have the onAfterInit() function do should we drop the slider_init.js file?

@jsirish @korthjp17 do you guys know if this file is being used at all?

I don't believe it is, I think it gets initialized from the onAfterInit()

Not sure, will defer to Korth
I don't believe it is, I think it gets initialized from the onAfterInit()

—
Reply to this email directly or view it on GitHub
https://github.com/dynamic/SilverStripe-FlexSlider/issues/13#issuecomment-71105673
.

closed via #49


Restructure vamp

Integrated the VAMP feature (scoring and dimension reduction) in notebooks 1 and 2. In the first one, the score is just being computed for each feature, but there is not yet a systematic comparison  etc.
This is added in the second notebook, in which the method is introduced along with PCA and TICA. The pentapeptide is used as a showcase on how to select a feature based on the VAMP score.
The di-alanine model is used for exercises.
Fixes #76, #81

Another goodie added in this PR is that we will store the output of the executed cells in new notebook files, transform these to HTML and store them as build artififacts within circle ci. However the service has degraded performance right now, this is why the build is not succeeding.

ready for review. You should be able to look at the output at the artifacts section of CircleCI, once tests have passed.

Maybe, since you are working on it, can you already delete the pentapeptide from notebook 01? (If that's desired.)

Requesting changes according to #85:
NB02: lines 515 and 883 cluster_kmeans(pca_all...)
NB02: lines 573 and 940 cluster_kmeans(tica_all...)

Thanks for the review guys, I've added the requested changes.


Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) when dealing with invalid event

Describe the bug

I receive a valid repost and parse its content to an Event with Event.fromJson(..). The event json is invalid but it worked anyway. When I call asJson() on this event I get the error mentioned in the title. My app will crash because this error can't be catched.
To Reproduce

val json = """
             {
               "citedNotesCache": [],
               "citedUsersCache": [
                 "aac07d95089ce6adf08b9156d43c1a4ab594c6130b7dcb12ec199008c5819a2f"
               ],
               "content": "#JoininBox is a minimalistic, security focused Linux environment for #JoinMarket with a terminal based graphical menu.\n\nnostr:npub14tq8m9ggnnn2muytj9tdg0q6f26ef3snpd7ukyhvrxgq33vpnghs8shy62 👍🧡\n\nhttps://www.nobsbitcoin.com/joininbox-v0-8-0/",
               "created_at":<PHONE_NUMBER>,
               "id": "c8acc12a232ea6caedfaaf0c52148635de6ffd312c3f432c6eca11720c102e54",
               "kind": 1,
               "pubkey": "27154fb873badf69c3ea83a0da6e65d6a150d2bf8f7320fc3314248d74645c64",
               "sig": "e27062b1b7187ffa0b521dab23fff6c6b62c00fd1b029e28368d7d070dfb225f7e598e3b1c6b1e2335b286ec3702492bce152035105b934f594cd7323d84f0ee",
               "tags": [
                 [
                   "t",
                   "joininbox"
                 ],
                 [
                   "t",
                   "joinmarket"
                 ],
                 [
                   "p",
                   "aac07d95089ce6adf08b9156d43c1a4ab594c6130b7dcb12ec199008c5819a2f"
                 ]
               ]
             }
        """.trimIndent()

val event = Event.fromJson(json = json)
val jsonAgain = kotlin.runCatching { event.asJson() } // OUCH !!!!

Expected behavior

Don't panic. Errors should always be catchable
If I have an Event object I expect it to be valid. Calling asJson() should not produce an error
Throw an error when trying to call fromJson(..) with an invalid event json. This one contained 2 invalid fields citedNotesCache and citedUsersCache

Build environment

Library:  nostr
Language:  Kotlin
Language version:   0.12.0
Tag/commit:
OS+version:

Additional context

The unknown fields are ignored during deserialization. I don't think will be ever added a new field to event, but if will happen, allowing only known field will break clients, so IMO just ignoring them should be ok.
But it's really strange that it panic during serialization. I'll try to investiage.
EDIT: it's related to a manual implementation of event de/serialization to preserve order of JSON keys. It include the unknown keys and during serialization return an error since the key not exists in the struct. I'll fix it and publish a patch soon.

I'm going to release v0.12.1


Average command failed with stack trace

Hi Team,
First of all let me say thank you for the great project!
I was able to successfully install and use it, but looks like I have found one issue with "average" command when I try to use it with any app from Google Play Store:
Загальна кількість відгуків: 1720.00
Загальна кількість завантажень: від 1000001 до 5000000
Traceback (most recent call last):
  File "/Users/standy/miniconda3/bin/asolytics", line 8, in <module>
    sys.exit(main())
  File "/Users/standy/miniconda3/lib/python3.10/site-packages/asolytics/asolytics.py", line 689, in main
    average_install_in_Google_Play(args.average, gl)
  File "/Users/standy/miniconda3/lib/python3.10/site-packages/asolytics/asolytics.py", line 455, in average_install_in_Google_Play
    button_deteils.pop(4).click()
  File "/Users/standy/miniconda3/lib/python3.10/site-packages/selenium/webdriver/remote/webelement.py", line 93, in click
    self._execute(Command.CLICK_ELEMENT)
  File "/Users/standy/miniconda3/lib/python3.10/site-packages/selenium/webdriver/remote/webelement.py", line 410, in _execute
    return self._parent.execute(command, params)
  File "/Users/standy/miniconda3/lib/python3.10/site-packages/selenium/webdriver/remote/webdriver.py", line 444, in execute
    self.error_handler.check_response(response)
  File "/Users/standy/miniconda3/lib/python3.10/site-packages/selenium/webdriver/remote/errorhandler.py", line 249, in check_response
    raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.ElementNotInteractableException: Message: Element <button class="VfPpkd-Bz112c-LgbsSe yHy1rc eT1oJ mN1ivc LS2TS"> could not be scrolled into view
Stacktrace:
RemoteError@chrome://remote/content/shared/RemoteError.sys.mjs:8:8
WebDriverError@chrome://remote/content/shared/webdriver/Errors.sys.mjs:188:5
ElementNotInteractableError@chrome://remote/content/shared/webdriver/Errors.sys.mjs:348:5
webdriverClickElement@chrome://remote/content/marionette/interaction.sys.mjs:150:11
interaction.clickElement@chrome://remote/content/marionette/interaction.sys.mjs:119:11
clickElement@chrome://remote/content/marionette/actors/MarionetteCommandsChild.sys.mjs:202:29
receiveMessage@chrome://remote/content/marionette/actors/MarionetteCommandsChild.sys.mjs:84:31

Is it due to some layout changes on the page?

Thank you for writing about this. I fixed this issue today.
Update with the command: pip install asolytics --upgrade


fix typo

Pull Request Checklist

[x] I agree to licence my contributions under the MIT licence
[x] I have added copyright headers to new files
[x] I have added tests for any changed functionality

Fixes
Fixes #xxxx
Purpose
What does this PR do?
Background Context
Why did you take this approach?
References
Are there any relevant issues / PRs / mailing lists discussions?

Thank you 👍


CacheRequestBodyGatewayFilterFactory due to OutOfDirectMemoryError

Describe the bug
In SCG-3.1.0，I found the CacheRequestBody is had a implement. In SCG-3.0.5, I implemented like this:

and the new implement like this

when i repalce the old version with new version, the application will throw io.netty.util.internal.OutOfDirectMemoryError: failed to allocate xxx byte of direct memory some time later.
the request of num is 300-400 per sec.

It should be because I disabled the removeCacheBodyFilter


Fixed #13378 - Added skipOnEmpty option to SluggableBehaviour

Q
A

Is bugfix?
no

New feature?
yes

Breaks BC?
no

Tests pass?
yes

Fixed issues
#13378

@dynasource thanks! I've just updated my PR.

Merged. Thank you!

Test are broken: https://travis-ci.org/yiisoft/yii2/builds/249564948


Can't modify parameters in idf.py menuconfig

I followed all the steps required, but I can't modify the baud rate when using 'idf.py menuconfig'
Does someone have the solution ?

Please share screenshots showing the issues. Does idf.py menuconfig say you are not allowed to change the baud rate? I need more information to understand the issue.

Hello sir, thanks a lot for you answer,
I deleted esp-idf and reinstalled it, now it works, I do have all the parameters accessible.
However, I now have issues connecting the AP and the STA.
I have 2 ESP32, both connected to my laptop using USB.
I followed all the requirements, and put the right parameters (I think) but I don't understand why the AP and the STA are not sharing CSI Data.
Here the parameters for the AP :

The parameters for the STA :

Thank you for your time sir, tell me if you need more info

configuration of the STA
cd ~/esp/esp-idf
./install.sh esp32
. $HOME/esp/esp-idf/export.sh
cd ~/Desktop/test-csi-tools/esp32-csi-tool/active_sta/
idf.py set-target esp32
idf.py build
idf.py -p /dev/cu.usbserial-0001 flash

I change the parameters using idf.py menuconfig
idf.py -p /dev/cu.usbserial-0001 flash monitor

You will want to make sure that the AP is set to receive CSI data (I think this is the default setting). The STA can receive CSI, but it would be easier the other way when you are learning.
Are there any errors for the AP or the STA when you flash monitor them? Do you see any message that says the devices are connecting to one another?
What is PDL-PRIVATE? Is this an SSID of a router in your environment? If so, I think there is some confusion on the recommended standard method for using this library. The SSID should be unique to the ESP32s (the ESP32s will connect to each other).

Thanks for your answer, I did not understand how to connect to the Wifi, I was trying to connect to my router. I successfully connected the STA and the AP. Unfortunately the data I receive have a weird aspect. I read the issue  #12 but I don't understand how to obtain good CSI Data. I have a lot of zeros even when removing the NULL_SUBCARRIERS as suggest. See the plots below

I think I should obtain things like that

Hello, I got the same problem it seems that the phase I extract from ESP CSI is constant. I stumbled upon a research paper (https://arxiv.org/pdf/2301.00250.pdf) that seems to confirm an intended "sawtooth shape" for the original phase (as shown in the linked image and as your last figure seems to suggest).
I don't know if this is intended or if there is some parameter to tune.

I have a lot of zeros even when removing the NULL_SUBCARRIERS as suggest.

I am guessing you accidentally removed the incorrect subcarriers. Can you confirm if the subcarriers that you remove are actually all zeros?

I think I should obtain things like that

Where did you get this "expected" data?
For phase, the ESP32 is very noisy. I have yet to dig into it (if you spend time on this, please share your findings. Community help is essential for open source project like this!)
The "sawtooth shape" is due to the phase wrapping around the plot. The plot shows phase on a cartesian graph, but the phase values are actually polar meaning they wrap around (-pi, pi). This is why "phase unwrapping" is important for visualization.


Cursor of editor window jumping after saving

System information:

MacOS 11.6
DBeaver version <IP_ADDRESS>202200327

Connection specification:

PostgreSQL 14
postgresql-42.2.20
No tunnels, proxies.

Describe the problem you're observing:
In the editor, after saving the changes to a .sql file (e.g. updating a query or the code of a stored procedure), the cursor jumps automatically to the end of file without any reason.
The jump was detected only after explicitly saving and never during the typing process.
Steps to reproduce, if exist:

Open a SQL script connected with a data source (e.g. selecting a connection -> SQL Editor -> New SQL script).
Add a block of code that does not fit completely the vertical margin of the editor window.
Move the cursor to the top of the editor window.
Save (e.g. File -> Save/Save As).
The cursor is moved to the end of the block of code.

Include any warning/errors/backtraces from the logs
No exception reported in .log.

Hello @de-sgen,
This issue was fixed in https://github.com/dbeaver/dbeaver/issues/15562 and the fix will be available in the next version (22.0.0).

Thanks @ShadelessFox.


Update maven version to SNAPSHOT

Development branches like master need to use -SNAPSHOT version suffix not to spoil local maven repositories.

@belaban This is even worse... the 4.1.3.Final is released in Jira but the tag is missing ;-(

I can't change the version just yet, as I had an issue uploading the 4.1.3.Final artifcat to maven. I'm trying again today, with the help of David...

I did create a tag JGroups-4.1.3.Final and push it to GIT!

Ok, I see the tag now, must have been a race condition. :-)
Regardless, master must be always SNAPSHOT version, otherwise people push their changes on rebased master branch as final GA versions that won't get overriden. That's why there are things like maven release plugin that makes all of this hassle free https://maven.apache.org/maven-release/maven-release-plugin/ – also releases are done from a tag, not from a branch, so it doesn't matter what revising is master on.

Care to contribute a release plugin change to the POM? :-)

OK, I set master to 4.1.4-SNAPSHOT and will release from the release-4.1.3 branch (once David returns from his PTO).


preprocess boolean flag

adds a boolean preprocess flag that can be used to toggle on and off the preprocessing of meshes on import.

Failures are due to this been a 'branch' build on this repo, actually all working fine.


Svg is not support chinese!

Use text(), it's ok, but i want to convert svg to pdf.
The pdf generated includes the messy code of chinese.
I need help.

if there is a example, i will appreciate for that.

Methods used?

7 days no reaction. Closed


[Feature][GitHub] Provide a workflow filter to limit the GitHub workflow runs to collect and improve the speed

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
DevLake v0.14 collects ALL GitHub Action workflow runs and jobs by default, which makes the collection speed very slow. For example, it took 4+ hours to collect data from 'apache/incubator-devlake' by 2 tokens. However, before collecting GitHub Action data, the collection speed was about 40min by 1 token.
Therefore, we can see that there's a bottleneck in GitHub Action data collection.
Proposed Solutions
DevLake can provide workflow as a filter to limit the size of GitHub workflow runs to collect, because:

from users' perspective, they don't always want to collect all CI data. They might sacrifice integrity for speed.
from DevLake's perspective, DevLake's DORA metrics are based on deployments in the production environment. Other CI jobs such as linter, checker and etc. are not taken into calculation, which means they're to some extent useless.

Take 'apache/incubator-devlake' for example, around 30,000 requests will be posted to collect all CI data; while production deployments are all in the runs of one workflow 'Build-Images-Push-Docker'. By letting users to select this one single workflow before collection, the number of requests will be decreased to 57.
Below is the prototype for how to add the workflow filter.
TBD
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Replaced by Limited History feature, close for now, feel free to reopen.