Ignored exception in affinegap.affinegap.normalizedAffineGapDistance

Getting the error below in a bunch of locations: loading in sample data, loading in pre-labeled training data, training, etc. Is this because there are None values in my data? Should I be worried?
Exception TypeError: "object of type 'NoneType' has no len()" in 'affinegap.affinegap.normalizedAffineGapDistance' ignored

Yes. You should represent missing data as an empty string ''
On Wed, Jul 8, 2015 at 1:26 PM Luke Miner<EMAIL_ADDRESS>wrote:

Getting the error below in a bunch of locations: loading in sample data,
loading in pre-labeled training data, training, etc. Is this because there
are None values in my data? Should I be worried?
Exception TypeError: "object of type 'NoneType' has no len()" in 'affinegap.affinegap.normalizedAffineGapDistance' ignored
—
Reply to this email directly or view it on GitHub
https://github.com/datamade/dedupe/issues/397.

Hmm difficult to do when using a dict comprehension to read in the sample like {i: row for i, row in enumerate(c)} . Don't want to modify the data in the database and don't want the extra expense of iterating through each row in search of a null value. Will it hurt my results to leave this in?

It will hurt your results.

The way I handle this is through a SQL statement
like IFNULL(name, '')

That's what I was looking into. Will this hurt me if the type is Price or longlat?

Yes. the null val for Price is 0
the the null val for lat long is (0,0)
I've been thinking about having dedupe use None as the missing value
indicator.
On Wed, Jul 8, 2015 at 2:06 PM Luke Miner<EMAIL_ADDRESS>wrote:

That's what I was looking into. Will this hurt me if the type is Price or
longlat?
—
Reply to this email directly or view it on GitHub
https://github.com/datamade/dedupe/issues/397#issuecomment-119698448.


[Help] Improve preprocessors related stuff

Goals

[x] Remove preprocessor tokens
[ ] ~Add to \ be a BACKSLASH token~

I will do it in a separated PR

[x] Support for null directives
[x] Parse #error
[x] Parse #warning
[x] Parse #pragma
[x] Parse #define
[x] Parse #if
[x] Parse #elif
[x] Parse #else
[x] Parse #endif
[x] Parse #include and #import

[x] String path
[X] Tag path

[x] Recursive path
[x] Support names with -, _, ., etc.

[x] Add test cases for all preprocessors
[x] Fix all CheckPreprocessor* rules

[x] CheckPreprocessorInclude
[x] CheckPreprocessorDefine
[x] CheckPreprocessorIndent
[x] CheckPreprocessorProtection

[x] Comments (one or multiline) in preprocessor EOL

Improves

An error is returned when some instruction of a .h is written outside a header guard
An error is returned when some composed preprocessor statements (#if, #else, etc.) are not being closed or don't have a start (e.g #else without an #if)
"Argumented" preprocessor statements (#define, #if, etc.) now need a space after identifier (e.g #include <stdio.h>)
A proper error is returned when the macro defining the guard header is ok, but not in uppercase
Add an error when macro functions are being declared
Add to preprocessors be allowed only in global scope
Add an error when multiple header protection in given
Add a proper error when the guard of header protection is not defined

Fixes

#328
#383
#397

Notes
...

The current failing test is about the file ok_ifdef.c, norminette is considering the IsFuncDeclaration as IsDeclaration, I don't know what I changed for this bug to happen, it looks like a similar bug happens in #322.
Anyway, I need help here anyone?

@matthieu42Network, could you please review it?

Hello, I will ask for a 2nd approve for a PR this big then merge :)


Resolve backport conflicts

What

Revert all commits after ef3ee8356a2ea9bb44135787dab2f1491dcbb9f7.
Merge e3c9bccdc38bbd09bcac0131c00f3be58368b416 from master.
Revert e3c9bccdc38bbd09bcac0131c00f3be58368b416.
Cherry-pick all comits after ef3ee8356a2ea9bb44135787dab2f1491dcbb9f7.

Why
Because @bighappyface asked me to solve the merge conflict in 6.0.0-dev, I'm assuming because he doesn't want it directly rebased on ef3ee8356a2ea9bb44135787dab2f1491dcbb9f7 (to avoid orphaning 5.2.0).

Before you merge - do you want me to turn this into a single commit that resolves the conflict, or would you like to keep it as-is? If the latter, then you may want to do this as a straight merge, and not a squash merge, to avoid losing the 6.0.0-dev commit history.

Thought of a saner method.


[FEATURE] IR Normalization on NAM plugin IR loader

The IR loader on NAM does not normalize the output level of IRs. This causes some IRs to be very loud and others to be very quiet.
Demo video (unlisted):
https://youtu.be/xqpA6RBFz1U
Link to IRs used in video:
https://drive.google.com/file/d/14k9mRz8k2wqyYeyQPGwVkb1BNKTinwev/view?usp=drive_link
It would be great if the IR loader could be enhanced to normalize the IR that is loaded into it.
These are example IRs of the exact same tone, exported with different volumes.
If you load these IRs into any popular external IR loader (NadIR, MConvolutionEZ, etc) they will all have the same output volume. If you load them into NAM, they have different output volumes.
Additional context
This would prove very useful for a project I am working on that would allow me to very easily integrate JZIR into NAM where I would have 2 IRs in series. The first IR which would load into NAM would be the "eq correction" IR which would standardize the EQ output of every NAM profile (this IR is very quiet right now which is primarily why Im asking for this enhancement) then the 2nd IR would be loaded in an external IR loader and that would have the band/song/album tone. You can download my example workflow for possible NAM integration for JZIR here:
https://drive.google.com/file/d/12uLZNhOp3l4m8ACo_3FPx94SJWYKNGij/view?usp=drive_link

I noticed in my demo that NAM's IR loacer seemed quieter overall, compared to the other IR loaders (0db IR in NAM vs 0db IR in other IR loaders).

The NAM IR loading code decreases the volume by 18dB to compensate for most IRs being too loud by default:
https://github.com/sdatkinson/NeuralAmpModelerCore/blob/637dc60c9a17de8024d9adbf9191b8b7ac4cee0d/dsp/ImpulseResponse.cpp#L78
This should presumably be removed if a normalization process is already putting the IR at a desired level.

So I noticed that NAM's IR loader can load 32bit audio. Since this is the case, I can simply export my special "NAM>JZIR EQ correction IRs" in 32bit format and about +18db over 0db to compensate for the 18db decrease pointed out by @mikeoliphant here:
https://github.com/sdatkinson/NeuralAmpModelerCore/blob/637dc60c9a17de8024d9adbf9191b8b7ac4cee0d/dsp/ImpulseResponse.cpp#L78
If this is the case, I will have about 30ish hours of work to do in order to compensate for this code. I dont mind doing it, really. Im honestly glad that NAM at least lets us load 32bit audio in the IR loader so I can actually do this while not having to wait for a code change (either removing the -18db reduction OR figuring out Normalization). If normalization is ever implemented, I can hopefully rely on that to then turn down my "loud" 32bit IRs.


'GIT/{:05d}/labels/{:04d}.txt' How to get this file？

Hello author, I would like to ask, how to get the “self.anno_path = 'GIT/{:05d}/labels/{:04d}.txt'”  of images in the tiktok dataset
    if 'youtube' in anno_pose_path:
        img_key = self.anno_list[idx % self.num_images]
    else:
        anno = list(open(anno_path))
        img_key = json.loads(anno[0].strip())['image_key']
    """
    example:
    {"num_region": 6, "image_key": "TiktokDance_00001_0002.png", "image_split": "00001", "image_read_error": false}
    {"box_id": 0, "class_name": "aerosol_can", "norm_bbox": [0.5, 0.5, 1.0, 1.0], "conf": 0.0, "region_caption": "a woman with an orange dress with butterflies on her shirt.", "caption_conf": 0.9404542168542169}
    {"box_id": 1, "class_name": "person", "norm_bbox": [0.46692365407943726, 0.4977584183216095, 0.9338473081588745, 0.995516836643219], "conf": 0.912740170955658, "region_caption": "a woman with an orange dress with butterflies on her shirt.", "caption_conf": 0.9404542168542169}
    {"box_id": 2, "class_name": "butterfly", "norm_bbox": [0.2368704378604889, 0.5088028907775879, 0.1444256454706192, 0.04199704900383949], "conf": 0.8738771677017212, "region_caption": "a brown butterfly sitting on an orange background.", "caption_conf": 0.9297735554473283}
    {"box_id": 3, "class_name": "butterfly", "norm_bbox": [0.6688584089279175, 0.5137135982513428, 0.11311062425374985, 0.05455022677779198], "conf": 0.8287128806114197, "region_caption": "a brown butterfly sitting on an orange wall.", "caption_conf": 0.9264783379302365}
    {"box_id": 4, "class_name": "blouse", "norm_bbox": [0.4692786931991577, 0.6465241312980652, 0.9283269643783569, 0.6027728319168091], "conf": 0.6851752400398254, "region_caption": "a woman wearing an orange shirt with butterflies on it.", "caption_conf": 0.9978814544264754}
    {"box_id": 5, "class_name": "short_pants", "norm_bbox": [0.44008955359458923, 0.8769687414169312, 0.8799525499343872, 0.2431662678718567], "conf": 0.6741859316825867, "region_caption": "a person wearing an orange shirt and grey sweatpants.", "caption_conf": 0.9731313580907464}
    """

Hi @hanhan0521 , may I ask which config file do you use? Since with current tsv data file, you do not need to use the anno_list for Tiktok fine-tuning.

Hello author, I have solved this problem and found that it exists in the train_captition.tsv file.
I now have another question, which is how do I pre-train my own dataset。I also got the preprocessed output from Openpose。
How to set the following path？Thank you！！！！！！
self.total_num_videos = 340
self.anno_path = 'GIT/{:05d}/labels/{:04d}.txt'
self.image_path = '{:05d}/images/{:04d}.png'
self.anno_pose_path = '{:05d}/openpose_json/{:04d}.png.json'
self.ref_mask_path = '{:05d}/masks/{:04d}.png'
    self.image_path_web = '{}/{}'
    self.ref_image_path_web = '{}/{}'
    self.anno_pose_path_web = '{}/openpose_json/{}.json'
    self.ref_mask_path_web = '{}/groundsam/{}.mask.jpg'

    self.image_paths_list = []
    self.ref_image_paths_list = []
    self.ref_pose_paths_list = []
    self.anno_list = []
    self.anno_pose_list = []
    self.anno_init_pose_list = []
    self.mask_list = []

    ft_video_idx = getattr(args, 'ft_idx', '001_1.57_2.17_1x1') # default elon
    if split == 'train': # for training video
        # video_idx = ['001_1.57_2.17_1x1'] # elon mask 2
        # video_idx = ['007_7.36_7.44_1x1'] # 007
        # video_idx = ['001_1.57_2.17_9x16', '001_11.46_11.54_9x16', '001_5.37_5.44_9x16', '001_8.14_8.27_9x16']  # elon mask 1+2+3+4
        video_idx = [ft_video_idx] # 007
        dataset_prefix = self.args.web_data_root
    else: # for pose video
        video_idx = [335, 137]
        # ref_video_idx = '001_1.57_2.17_1x1' # 007
        # ref_video_idx = '007_7.36_7.44_1x1' # 007
        ref_video_idx = ft_video_idx # 007
        dataset_prefix = self.args.tiktok_data_root

Hi @hanhan0521 , for the pre-training, actually you do not need the pose. If you want to pretrain on your own data and do not want to use the tsv format, you may need to revise the dataloader code for the pre-training to use the raw image/mask data. You can refer to this file (https://github.com/Wangt-CN/DisCo/blob/main/dataset/tiktok_controlnet_t2i_imagevar_combine_mask.py). But note that this file is for fine-tuning, therefore it still consists pose that is no use in pretrain.

How to run human specific fine-tunning with my own dataset ?
How to get the GIT directory which can be found in all ./dataset/tiktok_controlnet_t2i_imagevar_combine_specifcimg*.py ?

Hi @quqixun, Thanks a lot for reporting the confusion.

First, please check if the config file indicates to use the data python file, e.g., https://github.com/Wangt-CN/DisCo/blob/main/dataset/tiktok_controlnet_t2i_imagevar_combine_specifcimg_web_upsquare.py.
Actually the data in GIT folder only contains the frame-name and only is used in validation (https://github.com/Wangt-CN/DisCo/blob/main/dataset/tiktok_controlnet_t2i_imagevar_combine_specifcimg_web_upsquare.py#L192). For our experiment, we just use TikTok data for validation. I am trying to upload the GIT folder to share on Github.
But actually, GIT file only contains the frame name. Therefore, as a quick work-around, you can just delete the use of the anno_path and the related variable. And then revise this part to provide a customized frame name.
Due to the flexibility of current human-specific ft pipeline, there may be many work-arounds to do this. Sorry for the confusion and I will then write a brief intro for easily adaptation to the user data.

Hello author, I would like to use our code to achieve the posture of driving the target character with its own skeletal keypoints. But when I run the "[/dataset/tiktok_controlnet_t2i_imagevar_combine_mask.py]" file, the cond folder I get is the pose of its own dataset, and the gt folder is still the original human image, and it is not driven, why is that?

@hanhan0521 Hi, actually I cannot understand you question. But from the code you give, it seemed that you set the anno_pose_json to the Tiktok data. This file contains the skeleton annotation human. BTW, what stage are you trying?


Component set from connection

What does this PR do?
This adds the capability to create a componentSet of metadataComponents from an org connection. This can/will be used to extend the source:manifest:create command to create a manifest file based on an org configuration.
What issues does this PR fix or reference?
@W-0@
Functionality Before
<insert gif and/or summary>
Functionality After
<insert gif and/or summary>

This is Jochen's work just in a PR I created.  I tested it by writing a quick command parameter implementation for the force:source:manifest:create command that uses this code to create a manifest based on an org.  I used the generated manifest for deploys and retrieves and it works great.


serde-derive fails to parse const generic arguments

I am working on a project where I encode version information inside a struct's type, and want to use serde to de/serialize them. My code looks like the following:
#[derive(Debug, Serialize)]
pub struct MyStruct<const VERSION: u16> {
    username: String,
    password: VersionDependant<String, VERSION, 0, 3>,
    passhash: VersionDependant<String, VERSION, 3, { u16::MAX }>,
}

#[derive(Debug)]
pub struct VersionDependant<T, const VERSION: u16, const MIN: u16, const MAX: u16> {
    data: Option<T>,
}

// Serialize/Deserialize implementation for VersionDependant...

This gives me the following parsing error:
error: expected one of: `for`, parentheses, `fn`, `unsafe`, `extern`, identifier, `::`, `<`, square brackets, `*`, `&`, `!`, `impl`, `_`, lifetime
  --> src/main.rs:10:49
   |
10 |     password: VersionDependant<String, VERSION, 0, 3>,
   |                                                 ^

error: aborting due to previous error

error: could not compile `serde-derive-reproduce`

Removing the Serialize derive will make the code compile, which makes me think the problem lies with serde or one of its dependencies (most likely syn). Apologies in advance if this should be in the syn repo instead.
Code to reproduce can be found here: https://gist.github.com/HoLLy-HaCKeR/1473470900a0b632c1a5ec43068dc2f8
I am using latest nightly and latest release of serde.

Closing as it is a duplicate of #1272


remove seperate resources for handling plugin extension

There were two orthogonal resource chains for handling plugins with with
the .hpi & .jpi extension.  This commit unifies the two code paths.  It
should fix the resource ordering problem that causes it to take two runs
to install a plugin and pin it.
resolves #380

Alternative to #388 that is a bit more aggressive.

I suspect the pin file should be removed when the plugin is :absent...

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests


editor periodically freezer and user cannot continue editing the current equation

I'm not sure how to replicate, but on several instances, the modal would freeze and prevent further editing (typing via keyboard or palette) or selection of the math equation (current). If one were to save and then reopen the same problem, the user was then able to edit again.
again, I'm not sure why this was happening, but it occurred several times during 10/26 testing with students.

has this happened recently?

this hasn't happened in a while, so closing


[plugin] Add amberflo.io api metering plugin

Summary
Add third-party plugin Amberflo.io API Metering.
Reason
Some of our customers use Kong.
Testing
I've manually tested the changes by running the site locally.
Preview deploy: https://deploy-preview-4551--kongdocs.netlify.app/hub/amberflo/kong-plugin-amberflo/

Approved

@cloudjumpercat Gang has approved from a product perspective. Could you help fix the build and merge?

@cloudjumpercat Thanks for merging.


Sync fails when brackets are present in the absolute vault path

i was moving into a new foldering system, and ia noticed that
Steps to repeat the bug

open the obisidan vault manager
move the vault to a new folder (for an example "[01] fislysandi"
get a sync error.

idk why it happens, hopefully it will be fixed.
so far im really enjoying this plugin because it allows me to write anki cards within the comfort of obsidian.

Thanks for reporting this issue!
I was able to reproduce the sync errors, and they're specifically related to the brackets in the folder name.
If you move the vault to a folder without special characters like [ and ] in it, it will sync successfully.
I'll have to look into where exactly this is happening. If you need an immediate work-around, remove the brackets from the folder name.

This should be fixed in v1.6.1.
Please feel free to comment on this issue if you're still seeing the error.


crypto/tls: same x509 certificate in different tls connections costs too much memory

What version of Go are you using (go version)?

$ go version
go version go1.16.3 linux/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env

What did you do?
In our production environment, we use tls to communicate between applications. A client application will access dozens to thousands of server applications, and server applications will have dozens to thousands of machines.
Each machine will maintain one or two long TCP connections for communication. A client may have tens of thousands of tls connections, and each connection will save a copy of the server's x509 certificate information, resulting in a large amount of memory usage.
For the same server application, the certificates held are the same. The actual number of different certificates is much lower than the number of connections, but the same size of memory is still allocated for each connection in the memory.
For the mtls(Mutual TLS) scenario, the server's tls connection may also save the client's certificate, which will cause the same memory consumption, and the number of client certificates is also much lower than the number of client connections.
What did you expect to see?
The same x509 certificate is reused through caching, and memory is no longer calculated and allocated separately for each connection, which reduces the memory usage.
What did you see instead?
Each connection will parse and save the x509 certificate information, which takes up a lot of memory.

ping @rolandshoemaker  @FiloSottile

ping @FiloSottile

hello， any suggestions for this issue/ pr ? @FiloSottile @cagedmantis

I'm also interested in this, as we've also seen it in production.
I'd prefer an approach that adds an x509 cache field to the tls.Config struct (defaulting to nil) along with an associated interface.  Then users can opt into a cache, taking responsibility for the integrity of the data within and for designing their own eviction strategies.

we found boring ssl have certificate cache too, see https://boringssl.googlesource.com/boringssl/+/HEAD/PORTING.md#crypto_buffer
With the standard OpenSSL APIs, when making many TLS connections, the certificate data for each connection is retained in memory in an expensive X509 structure. Additionally, common certificates often appear in the chains for multiple connections and are needlessly duplicated in memory.

@rolandshoemaker  @FiloSottile
Is the Golang team so arrogant? It's amazing!
no manners guys!


[Mention The Feature]: update the features page

Is your feature request related to a problem? Please describe.

i want to redisn this page with some slick animations
Describe the solution you'd like.
i'll change the color palette , if you want , otherwise it will enhace the ui
https://github.com/user-attachments/assets/d02673a2-f7e9-44f1-9c57-5148bd99a5cc
Describe alternatives you've considered.
No response
Additional context.
No response
Show us the magic with screenshots
No response
Checklist

[X] I have checked the Existing Issues
[X] I have read the Contributing Guidelines
[X] I want to work on this issue. (optional)

@priyashuu sure go ahead
Make sure to join the discord server for further communication
Don't forget to star the repository
Complete the task in next 2 days and kindly mention your issue # in your pr like this:
Closes #IssueNumber
Note: the level of the issue may change based on the quality of the PR code

ok sir , see you soon with next pr

Its been weeks and no pull request was made so we are closing this issue.


Allow building without a tls implementation (for downstream libraries)

tide-sqlx doesn't know which tls implementation the developer will choose, but without one in default sqlx doesn't build, and makes local IDE development difficult (rust-analyzer has trouble with it).
Due to this I put rustls in default and uh, actually forgot to remove it in error.
I think though that sqlx should be able to compile (not necessarily run) without a tls implementation, since this would make development of downstream libraries easier.

The API rework that is planned for 0.6 (happening on the next branch) will make this possible.

The API rework that is planned for 0.6 (happening on the next branch) will make this possible.

Yes. For more context, connection types will be like:
PgConnection<Tokio<NoTls>>
PgConnection<Tokio<NativeTls>>
PgConnection<Tokio<Rustls>>
PgConnection<Tokio> // defaults to NativeTls > Rustls > NoTls (depending on features)
PgConnection // default to AsyncStd > Tokio > Actix > Blocking > NoRuntime (depending on features)

Yes. For more context, connection types will be like:
PgConnection<Tokio<NoTls>>
PgConnection<Tokio<NativeTls>>
PgConnection<Tokio<Rustls>>
PgConnection<Tokio> // defaults to NativeTls > Rustls > NoTls (depending on features)
PgConnection // default to AsyncStd > Tokio > Actix > Blocking > NoRuntime (depending on features)

Is there a compelling argument to not default to Rustls?

Is there a compelling argument to not default to Rustls?

It's still a relatively unproven implementation and if a vulnerability is discovered then any deployed version is stuck with that vulnerability until redeployed, whereas using native-tls you at least get the benefit of OS updates.

It's still a relatively unproven implementation and if a vulnerability is discovered then any deployed version is stuck with that vulnerability until redeployed, whereas using native-tls you at least get the benefit of OS updates.

Thats the case in some places, though not every distro version gets OpenSSL updates in what could be considered a "timely manner." It is younger for sure though, but at least its audited as of recent, and doesn't have the same questionable track record regarding vulnerabilities as OpenSSL.

Thats the case in some places, though not every distro version gets OpenSSL updates in what could be considered a "timely manner." It is younger for sure though, but at least its audited as of recent, and doesn't have the same questionable track record regarding vulnerabilities as OpenSSL.

You're very rarely going to be developing with multiple TLS backends enabled so it'll default to the one that you enable.

You're very rarely going to be developing with multiple TLS backends enabled so it'll default to the one that you enable.

Seems I misunderstood the features then? If so, sorry for the noise. I had assumed one TLS feature would be enabled as the "default" with a runtime over another.

Seems I misunderstood the features then? If so, sorry for the noise. I had assumed one TLS feature would be enabled as the "default" with a runtime over another.

Sorry for not making it clear. There is going to be two "TLS" features: native-tls and rustls. Those will enable sqlx::NativeTls and sqlx::Rustls respectively. There will be a type alias sqlx::DefaultTls that will point to one of them. The ordering above only applies if both of the features are enabled.

Sorry for not making it clear. There is going to be two "TLS" features: native-tls and rustls. Those will enable sqlx::NativeTls and sqlx::Rustls respectively. There will be a type alias sqlx::DefaultTls that will point to one of them. The ordering above only applies if both of the features are enabled.

Is there a compelling argument to not default to Rustls?

Compile times, it is much faster to link to a native tls library.
There is also an argument that going to a native tls library is similar to how rust core handles some other things, such as Mutexes.

Is there a compelling argument to not default to Rustls?

Compile times, it is much faster to link to a native tls library.
There is also an argument that going to a native tls library is similar to how rust core handles some other things, such as Mutexes.

This is now possible in 0.7.0-alpha.1 and in the coming 0.7.0 release.


Contact Maite Termenon

We weren't able to find an email via which to contact Maite Teremon (GH: @mainux ) via our auto-sending form. Feel free to forward the following message to her if you know via which channels she can be reached.
Dear Maite,

Thank you for your previous contribution to HeuDiConv (https://github.com/nipy/heudiconv), by code, issues, or feedback!

We are working on a manuscript to be submitted to the Journal of Open Source Software (https://joss.theoj.org) to describe HeuDiConv, and would like to acknowledge your contribution(s).
We are inviting you to co-author the paper, or, alternatively, give us permission to thank you in the Acknowledgements section of the paper.

If you would like to co-author the paper, please review the authorship criteria of JOSS at https://joss.readthedocs.io/en/latest/submitting.html#authorship and pay particular attention to potential implications of the "co-authors agree to be accountable for all aspects of the work" rule.
If you personally consider a co-authorship appropriate under these conditions, please

- submit a Pull Request with changes to https://github.com/nipy/heudiconv-joss-paper/blob/main/paper.md in which you
  - uncomment (remove leading #) your record
  - add your details (name, ORCID, affiliation) and/or adjust your name (if needed).

If you would like to just be acknowledged, please either reply to this email stating that, or submit a PR with your name appropriately listed in the Acknowledgements section of https://github.com/nipy/heudiconv-joss-paper/blob/main/paper.md and remove the pre-created commented-out record with your name from the header.

If you would like to neither be listed among co-authors, nor acknowledged, we would appreciate if you reply and let us know about that.

We are planing to submit the manuscript in two weeks (on/after June 14th), and will appreciate if you act on this invitation by the end of the next week so we have sufficient time tofinalize the submission.
Co-author records which would remain commented out will be removed before submission.

Thank you again for your contribution to HeuDiConv!

Sincerely,
HeuDiConv "Core Team"

Thanks for everything, Yaroslav!
El jue., 6 jul. 2023 16:55, Yaroslav Halchenko @.***>
escribió:

Closed #19 https://github.com/nipy/heudiconv-joss-paper/issues/19 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/nipy/heudiconv-joss-paper/issues/19#event-9744892626,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AH27I76PF3JPGVCQFFC2CJ3XO3GXFANCNFSM6AAAAAAYV5ZU6E
.
You are receiving this because you were mentioned.Message ID:
@.***>


Script runs in scipy mode instead of JIT

Hi all,
I am trying to determine the volume transport of the particles in my script. For this I have added an extra variable to the particle class in order to store the initial value of the velocity field (since I don't think it is possible to use operators such as * in the initial value statement, I could live with only the velocity value and multiply with dx and dz during postprocessing).
class Properties(JITParticle):
     VT = Variable('VT', dtype=np.float32, initial=fieldset.V)

However, when I run the script, I get the following warning:
WARNING: Particle initialisation from field can be very slow as it is computed in scipy mode.
Actually I had this problem before, by adding the temperature, salinity and density fields. At that time, the problem was solved by taking the initial value as 0. For those it was not a problem, since I am interested in the values along the trajectories. But now with the volume transport, it is the opposite, I am interested in the initial value, and not in the values along the trajectories.
Is the possibility of taking any other value than zero as initial value simply something that is not supported (yet)? Or am I overlooking something else?

Hi @NiekK19; good that you're asking. This is something that I've wanted to create a tutorial for, for a long time...
In short:

Yes, you can use initial=fieldset.V in the way you did, and it does work. It just may take a long time for the ParticleSet to be created, depending on how big your FieldSet is
If all your particles start at the same time and you want to run in JIT mode anyways, then a much quicker way to initialise the particles with a value from a Field is the following:
a. Initialise the variable with a value of 0.
b. Create the ParticleSet
c. Now define a Sampling Kerneldef SampleV(particle, fieldset, time):
    particle.VT = fieldset.V[time, particle.depth, particle.lat, particle.lon]

d. Now run the ParticleSet with only this Kernel for dt=0.pset.execute(SampleV, dt=0)

This doesn't increase the time on the particles, but will assign the correct value for particle.VT. And it's fast because it's run in JIT mode
If your Particles start at a different time (e.g. because you use repeatdt), then things become a bit more complicated. I haven't tested it, but I can imagine that youo could do something like the following
a) Initialise the variable with a value of 0 and also create another Variable sampled that you also initialise with 0
b) Create the ParticleSet
c) Now change the Sampling Kernel to something likedef SampleV(particle, fieldset, time):
    if particle.sampled == 0:
         particle.VT = fieldset.V[time, particle.depth, particle.lat, particle.lon]
         particle.sampled = 1

d) Now add this Kernel to the list of other kernels in your normal pset.execute(). Make sure it's the first Kernel, so that the sampling is done before the particles are moved

By the way, you might want to also add to_write='once' to the Variable definition, so that it only gets written to the output file once. That reduces the size of the output file
Hope this helps!

Thanks @erikvansebille for your quick reply and advise! I will look into it.

I think this trick would make a nice 'Example' for parcels_contributions

Hi @NiekK19. Not sure if you're still facing this problem, but FYI @reint-fischer wrote a new Field sampling tutorial that details how to sample these fields


Create sji.txt

@wimglasseesjibe unfortunately i can't check the page http://prntscr.com/9ieddq - please somehow confirm that the domain committed belongs to educational institution. Thanks!

I noticed that the attachments don't get added to the github thread.
Here's a screenshot in the cloud:
http://prntscr.com/9maiq0
On Thu, Dec 31, 2015 at 9:39 AM, Wim Glassee<EMAIL_ADDRESS>wrote:

And another one WITH the address bar in the picture
On Thu, Dec 31, 2015 at 9:37 AM, Wim Glassee<EMAIL_ADDRESS>wrote:

RU blacklisted? Interesting. I'll try to figure out why. In the
meanwhile, here's a screenshot of our webpage. Is this sufficient?
Thanks a lot for your help
On Fri, Dec 25, 2015 at 4:08 PM, Elena Ganenkova <
<EMAIL_ADDRESS>wrote:

@wimglasseesjibe https://github.com/wimglasseesjibe unfortunately i
can't check the page http://prntscr.com/9ieddq - please somehow confirm
that the domain committed belongs to educational institution. Thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/JetBrains/swot/pull/1548#issuecomment-167243707.

Don't mean to be pushy, but has anyone had the chance to have a look at
this yet?
Thanks in advance,
Wim
On Tue, Jan 5, 2016 at 10:02 AM, Wim Glassee<EMAIL_ADDRESS>wrote:

I noticed that the attachments don't get added to the github thread.
Here's a screenshot in the cloud:
http://prntscr.com/9maiq0
On Thu, Dec 31, 2015 at 9:39 AM, Wim Glassee<EMAIL_ADDRESS>wrote:

And another one WITH the address bar in the picture
On Thu, Dec 31, 2015 at 9:37 AM, Wim Glassee<EMAIL_ADDRESS>wrote:

RU blacklisted? Interesting. I'll try to figure out why. In the
meanwhile, here's a screenshot of our webpage. Is this sufficient?
Thanks a lot for your help
On Fri, Dec 25, 2015 at 4:08 PM, Elena Ganenkova <
<EMAIL_ADDRESS>wrote:

@wimglasseesjibe https://github.com/wimglasseesjibe unfortunately i
can't check the page http://prntscr.com/9ieddq - please somehow
confirm that the domain committed belongs to educational institution.
Thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/JetBrains/swot/pull/1548#issuecomment-167243707.

Pull request merged. We are sorry for the delay. Thank you for the update!
Philip


Write a script to deploy the contracts of an application

Motivation
The .devops directory would benefit from a script which allows us to deploy an entire application.
This can be done in two parts:

The default can be to deploy to a local node
Arguments can be passed in to overwrite 1. and deploy to a live network.

There can be multiple contracts in an application and they may all need to be deployed.

Closing in favour of #644


[Bug]: Email Bogus MIME version and other deliverability issues

Preflight Checklist

[X] I could not find a solution in the documentation, the existing issues or discussions
[X] I have joined the ZITADEL chat

Environment
ZITADEL Cloud
Version
Latest
Database
None
Database Version
No response
Describe the problem caused by this bug
mail-tester.com is reporting a Bogus MIME version header from the initial user email. I assume this is the same issue with the other transactional emails.
Other issues to improve deliverability:

No text/plain version. This should be easy to fix.
HTML version has font has low contrast

To reproduce

Go to mail-tester.com and copy the email address
Register a new user using this address
Check the deliverability score

Screenshots

Expected behavior
No response
Operating System
No response
Relevant Configuration
No response
Additional Context
No response

Hi @brandonkal
Not quite sure, I tried to find out if this is a case of case-sensitivity where there is no defined handling.
Created #7886 for the version.
With the definition under RFC-2045 it should be "MIME-Version", but with RFC-2045 Section 2:
 All numeric and octet values are given in decimal notation in this
 set of documents. All media type values, subtype values, and
 parameter names as defined are case-insensitive.  However, parameter
 values are case-sensitive unless otherwise specified for the specific
 parameter.

and "parameter names as defined are case-insesitive", I'm not sure if mail-tester.com maybe handles it wrong, do you have any information about that?

Mail-tester is using SpamAssassin for that score. So I would think it is handling it correctly since SpamAssassin is commonly deployed

Hi @stebenz I've tested email sending with mail-tester.com and the issue with Bogus MIME version is no longer there

I think the issue can be closed

I can confirm the issue of Bogus MIME is fixed. The issue of no text/plain version (HTML only message) still remains


trait_type validation

Everything you did makes sense @jnsdls, but deleting the map made it so no values will return an empty array instead of undefined and only value will return empty trait_type, which we don't want

Added back the .map to get the desired result:


Strange text in terminal

Issue Type: Bug
Actual vs Expected Results:
Here's a screenshot of the strange result:

The left one is running a django server, the right one is running a celery worker. I can see them printing new text whenever I hit the website in the browser. They both work fine, but it's just the strange text.
How to reproduce:

I'll work on some code after school and before bed.
I'll put the computer on sleep with terminals running their respective tasks.
When I wake it from sleep, I can't get rid of the strange looking text without closing effected terminals.

 Hiding and showing or resizing the terminal should fix it. This will hopefully be fixed in the future as we update Electron. let me know if that doesn't work around the issue.

It seems that resizing the windows fixes only one of the terminals. After some tinkering, it seems that your hunch is right: it's chromium. Other chromium apps suffer from this behavior as well. Guess I'll be looking forward to the electron updates!


generated image

Hi, I generated the BUSI data set according to the guidance of your paper, but the quality of my pictures is not as high as that of your paper. Could you please provide the parameters of your generative diffusion model? If you can provide me Would be very grateful!

Hello, You seem to have generated the images, can you guide me a little on how to use the generate stage part from medFusion and produce these results


Crashes on iOS 12 (iOS 13 works) with Xcode 11.2 DEAD_CODE_STRIPPING = NO

Since updating to Xcode 11.2, Realm crashes whenever I try to initialize it.
It crashes at
       RLMSchema *schema = configuration.customSchema ?: RLMSchema.sharedSchema;
in this method
+ (instancetype)realmWithConfiguration:(RLMRealmConfiguration *)configuration error:(NSError **)error
The issue: This only happens on iOS 12
I am using the package for SPM. This worked before updating Xcode. I have an app published in the App Store using Realm package that runs perfectly on iOS 12.
I have attempted to set DEAD_CODE_STRIPPING = NO because that seems to have caused significant amount of problems with the Xcode 11.2 release. But no, this is not that issue.
Here is the stack trace
#0	0x0000000101826418 in __abort_with_payload ()
#1	0x0000000101825a58 in abort_with_payload_wrapper_internal ()
#2	0x0000000101825a88 in abort_with_payload ()
#3	0x00000001017e88f8 in dyld::halt(char const*) ()
#4	0x00000001017e8a14 in dyld::fastBindLazySymbol(ImageLoader**, unsigned long) ()
#5	0x00000001cb038848 in dyld_stub_binder ()
#6	0x0000000100776d24 in type metadata accessor for Published<NotificationType?> ()
#7	0x0000000100787978 in type metadata completion function for CanvassViewModelCombine ()
#8	0x00000001f92d31c4 in swift::MetadataCacheEntryBase<(anonymous namespace)::SingletonMetadataCacheEntry, int>::doInitialization(swift::ConcurrencyControl&, swift::MetadataCompletionQueueEntry*, swift::MetadataRequest) ()
#9	0x00000001f92c9820 in swift_getSingletonMetadata ()
#10	0x000000010077dd5c in type metadata accessor for CanvassViewModelCombine ()
#11	0x0000000100787928 in ObjC metadata update function for CanvassViewModelCombine ()
#12	0x00000001ca7d1404 in realizeClassMaybeSwiftMaybeRelock(objc_class*, mutex_tt<false>&, bool) ()
#13	0x00000001ca7c5958 in realizeAllClasses() ()
#14	0x00000001ca7c88d8 in objc_copyClassList ()
#15	0x000000010246d43c in ::+[RLMSchema sharedSchema]() at /Users/Main/Library/Developer/Xcode/DerivedData/Canvass-gshlshuaawkneueskiqugxbldjql/SourcePackages/checkouts/realm-cocoa/Realm/RLMSchema.mm:260
#16	0x0000000102443318 in ::+[RLMRealm realmWithConfiguration:error:](RLMRealmConfiguration *, NSError **) at /Users/Main/Library/Developer/Xcode/DerivedData/Canvass-gshlshuaawkneueskiqugxbldjql/SourcePackages/checkouts/realm-cocoa/Realm/RLMRealm.mm:492
#17	0x00000001024a4a54 in @nonobjc RLMRealm.__allocating_init(configuration:) ()
#18	0x00000001024a4914 in Realm.__allocating_init() at /Users/Main/Library/Developer/Xcode/DerivedData/Canvass-gshlshuaawkneueskiqugxbldjql/SourcePackages/checkouts/realm-cocoa/RealmSwift/Realm.swift:67
#19	0x0000000102e17010 in print(error:) at /Users/Main/MyPackage2/Errors.swift:44
#20	0x0000000102e17c84 in handle(_:) at /Users/Main/MyPackage2/Errors.swift:80
#21	0x0000000101ffdb54 in closure #1 in variable initialization expression of Global.currentAuthorization at /Users/Main/MyPackage/Global.swift:113
#22	0x0000000101ffd380 in Global.init() at /Users/Main/MyPackage/Global.swift:109
#23	0x0000000101ffd284 in Global.__allocating_init() ()
#24	0x0000000101ffcfb4 in globalinit_33_80EC9331ADFD421111D74ACB6D1168C2_func3 at /Users/Main/MyPackage/Global.swift:96
#25	0x0000000105824c78 in _dispatch_client_callout ()
#26	0x0000000105826c84 in _dispatch_once_callout ()
#27	0x00000001f92dee40 in swift_once ()
#28	0x0000000101ffc5b8 in Global.shared.unsafeMutableAddressor at /Users/Main/MyPackage/Global.swift:96
#29	0x0000000100934ff4 in AppDelegate.application(_:didFinishLaunchingWithOptions:) at /Users/Main/MyAppAppDelegate.swift:64

A repro case would be very helpful here. The tests all pass when run on iOS 12 when built with Xcode 11.2, and a simple sample app which imports Realm via SPM does as well.

I am using the package for SPM.

FWIW, I saw something similar, as reported in the paragraph "Edit 3" https://github.com/realm/realm-cocoa/issues/4555#issuecomment-536403686 with the SPM version in Xcode 11.0.
I switched back to using the Carthage version and all was well. This was all Carthage 3.18.0.
Unfortunately I could not get a repro case either. All my local tests ran as expected and I could not repro.  However, two customers reported it, one running iOS 10.3.3 (iPad 3,4) and the other was 10.3.4 (iPad 3,6). I also got a crash log via Xcode for iOS 9.3.6 (iPad mini A1454). Both customers were ok after switching back to Carthage.
Here is a stack trace for the 10.3.3 crash, but all were similar. Happy to provide the other threads or other information (e.g. some source code) if that might help:
0 libsystem_kernel.dylib 0x1dea5acc 0x1de90000 + 88780
1 libsystem_pthread.dylib 0x1df5e086 0x1df59000 + 20614
2 libsystem_c.dylib 0x1de3a95a 0x1ddf0000 + 305498
3 libswiftCore.dylib 0x008b8b00 0x689000 + 2292480
4 libswiftCore.dylib 0x008c62b6 0x689000 + 2347702
5 libswiftCore.dylib 0x008c283c 0x689000 + 2332732
6 libswiftCore.dylib 0x008c2a38 0x689000 + 2333240
7 AcmeApp 0x00095f0a type metadata completion function for PuzzleState + 581386 (<compiler-generated>:0)
8 libswiftCore.dylib 0x008c802c 0x689000 + 2355244
9 libswiftCore.dylib 0x008c097e 0x689000 + 2324862
10 AcmeApp 0x0009599e PuzzleState.init() + 579998 (<compiler-generated>:0)
11 AcmeApp 0x000959c8 @objc PuzzleState.init() + 580040 (<compiler-generated>:0)
12 AcmeApp 0x00116b68 symbolic _____Sg 9AcmeApp18LibraryVolumeTableC6HeaderV + 1108840 ($ss20_ArrayBufferProtocolPsE22_arrayOutOfPlaceUpdateyys011_ContiguousaB0Vy7ElementQzGz_S2iySpyAGG_SitXEtFfA2_AEy9AcmeApp18LibraryVolumeTableC3RowVG_Tg5:190)
13 AcmeApp 0x00115be4 lazy cache variable for type metadata for LibraryVolumeTable + 1104868 ($ss20_ArrayBufferProtocolPsE22_arrayOutOfPlaceUpdateyys011_ContiguousaB0Vy7ElementQzGz_S2iySpyAGG_SitXEtFfA2_AEy9AcmeApp18LibraryVolumeTableC3RowVG_Tg5:0)
14 AcmeApp 0x001938dc outlined copy of (offset: Int, element: [String])? + 1620188 (_$sS2is17FixedWidthIntegersWL:84)
15 AcmeApp 0x001942b2 direct field offset for Puzzle.joinedClues + 1622706 (_$sS2is17FixedWidthIntegersWL:265)
16 CoreFoundation 0x1e5eceba 0x1e5dd000 + 65210
17 CoreFoundation 0x1e5ecdc6 0x1e5dd000 + 64966
18 AcmeApp 0x001940b2 direct field offset for Puzzle.solutionMap + 1622194 (_$sS2is17FixedWidthIntegersWL:0)
19 AcmeApp 0x001872e4 globalinit_33_A5843926A8A0C5292BCD8132A31EC432_func35 + 1569508 (_$s9AcmeApp7KeyAreaCMf:0)
20 AcmeApp 0x0031954e Realm.__allocating_init(configuration:) + 3216718 (_$sSo22NSStringDrawingOptionsVMf:0)
21 AcmeApp 0x00034e20 specialized WriteRealmController.init(inMemoryIdentifier:) + 183840 (WriteRealmController.swift:0)
22 AcmeApp 0x0003194e globalinit_33_3048FED25C8BA9F0BF05FDFD42028A65_func6 + 170318 (WriteRealmController.swift:20)
23 libdispatch.dylib 0x1dda5782 0x1dda4000 + 6018
24 libdispatch.dylib 0x1dda6252 0x1dda4000 + 8786
25 libswiftCore.dylib 0x008d04e6 0x689000 + 2389222
26 AcmeApp 0x000277f8 PlayTable.reloadData() + 129016 (PlayTable.swift:47)
27 AcmeApp 0x0003c840 specialized PlayTableViewController.init(coder:) + 215104 (PlayTableViewController.swift:12)
28 AcmeApp 0x0003b456 @objc PlayTableViewController.init(coder:) + 210006 (<compiler-generated>:10)
29 UIKit 0x23dd43ba 0x238f5000 + 5108666
30 UIKit 0x23f0e6ee 0x238f5000 + 6395630
31 UIKit 0x23f0e646 0x238f5000 + 6395462
32 UIKit 0x23f0e3a4 0x238f5000 + 6394788
33 UIKit 0x23c4fd86 0x238f5000 + 3517830
34 UIKit 0x23c67ac6 0x238f5000 + 3615430
35 UIKit 0x23f0e6ee 0x238f5000 + 6395630
36 UIKit 0x23f0e646 0x238f5000 + 6395462
37 UIKit 0x23f0e3a4 0x238f5000 + 6394788
38 UIKit 0x23c4fd86 0x238f5000 + 3517830
39 UIKit 0x23ed4bc0 0x238f5000 + 6159296
40 AcmeApp 0x00099ada @objc PlaySplitViewController.init(coder:) + 596698 (<compiler-generated>:0)
41 UIKit 0x23dd43ba 0x238f5000 + 5108666
42 UIKit 0x23f0e6ee 0x238f5000 + 6395630
43 UIKit 0x23f0e3a4 0x238f5000 + 6394788
44 UIKit 0x23dd40a4 0x238f5000 + 5107876
45 UIKit 0x23f0e6ee 0x238f5000 + 6395630
46 UIKit 0x23f0e646 0x238f5000 + 6395462
47 UIKit 0x23f0e3a4 0x238f5000 + 6394788
48 UIKit 0x23dd3632 0x238f5000 + 5105202
49 UIKit 0x24063b1e 0x238f5000 + 7793438
50 UIKit 0x23ed103e 0x238f5000 + 6144062
51 UIKit 0x23f0e6ee 0x238f5000 + 6395630
52 UIKit 0x23f0e646 0x238f5000 + 6395462
53 UIKit 0x23f0e3a4 0x238f5000 + 6394788
54 UIKit 0x23c4fd86 0x238f5000 + 3517830
55 UIKit 0x23c775e2 0x238f5000 + 3679714
56 AcmeApp 0x0003e2d8 specialized AppViewController.init(coder:) + 221912 (<compiler-generated>:0)
57 AcmeApp 0x0003dcd8 @objc AppViewController.init(coder:) + 220376 (<compiler-generated>:5)
58 UIKit 0x23dd43ba 0x238f5000 + 5108666
59 UIKit 0x23f0e6ee 0x238f5000 + 6395630
60 UIKit 0x23f0e3a4 0x238f5000 + 6394788
61 UIKit 0x23dd40a4 0x238f5000 + 5107876
62 UIKit 0x23f0e6ee 0x238f5000 + 6395630
63 UIKit 0x23f0e646 0x238f5000 + 6395462
64 UIKit 0x23f0e3a4 0x238f5000 + 6394788
65 UIKit 0x23dd3632 0x238f5000 + 5105202
66 UIKit 0x24063b1e 0x238f5000 + 7793438
67 UIKit 0x23b7ae40 0x238f5000 + 2645568
68 UIKit 0x239732a0 0x238f5000 + 516768
69 UIKit 0x23b79b10 0x238f5000 + 2640656
70 UIKit 0x23b8c7c4 0x238f5000 + 2717636
71 UIKit 0x23b7735a 0x238f5000 + 2630490
72 FrontBoardServices 0x1ffb8c12 0x1ff83000 + 220178
73 FrontBoardServices 0x1ffb8acc 0x1ff83000 + 219852
74 FrontBoardServices 0x1ffb8db6 0x1ff83000 + 220598
75 CoreFoundation 0x1e693fdc 0x1e5dd000 + 749532
76 CoreFoundation 0x1e693b04 0x1e5dd000 + 748292
77 CoreFoundation 0x1e691f50 0x1e5dd000 + 741200
78 CoreFoundation 0x1e5e51ae 0x1e5dd000 + 33198
79 CoreFoundation 0x1e5e4fd0 0x1e5dd000 + 32720
80 UIKit 0x2396ce2c 0x238f5000 + 491052
81 UIKit 0x23967a52 0x238f5000 + 469586
82 AcmeApp 0x0000d7e0 main + 22496 (AutosizingHeaderFooterTableView.swift:5)
83 libdyld.dylib 0x1ddd24ea 0x1ddcf000 + 13546

This is now happening more in Xcode 11.2.1.  An app that was previously unaffected and was able to use the SPM release is now also crashing. It was ok on Xcode 11.1 and prior.
Unlike the original reporter, this is happening for my customers on iOS 13.1 and iOS 13.2.

@bryan1anderson Did you find a resolution for this?

No I haven't found a solution but again, this is only for iOS 12

@tgoyne with @mikemee providing another example of this happening, I really need to get this solved. My customers can't use the app on iOS 12 and its causing major issues

I don't have any starting point for trying to fix this. I did everything I could think of to reproduce it and could not.

@tgoyne I think this reproduces it
I wasn't sure how to set it up exactly for you to get it. But essentially a workspace composed of: BAData, TestRealmFailure, and RealmFailureFramework.
RealmTest.zip

In that project the problem appears to be due to that there's two copies of all of the spm libraries in the final application. The BAData library is statically linked into TestRealmFailure and RealmFailureFramework and then the TestRealmFailure application dynamically links RealmFailureFramework. In pure obj-c land this works out okay as long as both copies of the libraries are identical (and they always will be in this case), but it seems to make the swift runtime crash.
The fix for this is to make BAData a dynamic library (by changing the package definition to .library(name: "BAData", type: .dynamic, targets: ["BAData"]) and setting it to "Embed & Sign" in "Frameworks, Libraries, and Embedded Content" in the app target), which results in there only being one copy of it in the final app and eliminates the crash for me.

How would the RealmFailureNetwork link to BAData in this case? I need them both to run off of this dependency @tgoyne

Okay yeah that was a bad sample. I was able to get it working by mimicking how my actual app does it a little more closely, my bad for giving you something that exactly the same.
Basically I made it so the Framework bundles the package, and then the App target bundles the framework. Its not duplicated.
So that example does not demonstrate my problem

I can confirm as @tgoyne figured out that the issue is do to a swift runtime crash. I have reported the bug with Apple
While the example project I provided didn't actually reproduce the bug in the same way, it did highlight an issue with packages used on dynamic frameworks.

➤ Unito Sync Bot commented:
Transition made by Unito

FYI: the Swift runtime issue is fixed in Xcode 11.4.1


Minor fixes in pom.xml

Minor fixes in pom.xml

use java web profile instead of javaee to match with download liberty doc.
removed redundant 'maven-failsafe-plugin' version
keep parent 'java8-parent'

Please review the committed change made on June/2/2017 only (Changed javaee to java web profile). Other changes are already merged in 'master' branch.


use the dynamic table

The current QPACK implementation only uses the minimal feature set of QPACK (i.e. Huffman-encoding and static table). This guarantees interoperability with other QPACK implementations. However, it's not very efficient, since we'll never be able to compress headers that are sent repeatedly. This is where using the dynamic table would lead to significant savings.
See https://github.com/quic-go/quic-go/issues/2424 for the quic-go tracking issue.

Hello, I'm looking for an HTTP/3 client that supports QPACK dynamic table compression, quic-go doesn't support dynamic tables right now right?

We try to test that attacker can exploit QPACK to launch the Denial of Service attack in this senario.(Client<--> CDN/Reverse Proxy <-->Origin)
We think that it works by the client sending an QPACK compressed HTTP requests(dynamic table), then CDN decompressed HTTP requests and forwarding it to Origin.(Client<-Compressed HTTP requests-HTTP/3->CDN<-Decompressed HTTP requests-HTTP/1->Origin)
We have confirmed that attackers can exploit QPACK(static tables) launch the Denial of Service attak. But it have limited amplification factors.
I am a researcher focusing on CDN security and protocol security and will not exploit this vulnerability for malicious attacks. I just want to report this vulnerability to CDN vendors and Reverse Proxy developers after confirming it.
Refer to https://www.ndss-symposium.org/wp-content/uploads/24411-slides.pdf

Refer to https://www.ndss-symposium.org/wp-content/uploads/24411-slides.pdf

Interesting read. I'd expect your attack to work exactly as the HTTP/2 version. For the application, HPACK and QPACK are quite similar. Implementation-wise, QPACK is a lot more complex, since it has to deal with reordering between requests.

Yes, QPACK is more complicated, so I've searched a lot of QPACK libraries that don't implement dynamic tables. Looking forward that quic-go can support dynamic tables.

decoding error: no dynamic table
I am trying to decode the headers from a WebTransport Session. Am I getting this because qpack-go doesn't support dynamic table yet?

You are right. qpack-go doesn't support dynamic table.

decoding error: no dynamic table
I am trying to decode the headers from a WebTransport Session. Am I getting this because qpack-go doesn't support dynamic table yet?

No. qpack dynamic table support is NOT required for establishing a WebTransport session. Dynamic table usage is negotiated via HTTP/3 SETTINGS frames. If peers don't support the dynamic table, encoding will be less efficient, but there's no case where this could lead to a connection failure.

WebTransport Connection was successful. I was trying to decode the headers that was sent in the Request using the QPACK Decoder. That's when I was getting that error.

So you suggest to disable the Dynamic Table Usage in Settings Frame and everything should work fine?

quic-go does the right thing, it doesn't advertise dynamic table support. If you're using a different HTTP/3 implementation with this library, then yes, you need to make sure to not advertise dynamic table support.

Yes, I am using a custom HTTP/3 implementation. It worked after I disabled the Dynamic Table Support. Thanks a lot.

@marten-seemann It turns out, the issue was actually due to the setting of N bit at Literal Field Line with Name Reference
When I encode that packet I set the N bit to 1, to ensure that literal string representation is sent across the subsequent hops by the intermediary.
RFC Reference
The condition buf[0]&0x20 > 0 here is triggering the errNoDynamicTable error. But in this case the N bit does not have anything to do with Dynamic table unless you have a reason.
I flipped the 'N' bit to 0 and that solved the issue. PR Reference for the QPACK that I use: PR


Universal Basis Textures

[ ] Figure out if we can package the ubasis binary in the plugin legally.
[ ] Add an option to convert textures to the smallest possible ubasis on export.

Basis Universal uses the Apache 2.0 license: https://github.com/BinomialLLC/basis_universal/blob/master/LICENSE
I'm no licensing expert, but I think we could include compiled versions of it then, provided we include the license and make it properly accessible. @jrz371 where would the best place for a Rhino Plugin be for displaying such license information to end users?

Basis Universal uses the Apache 2.0 license: https://github.com/BinomialLLC/basis_universal/blob/master/LICENSE
I'm no licensing expert, but I think we could include compiled versions of it then, provided we include the license and make it properly accessible. @jrz371 where would the best place for a Rhino Plugin be for displaying such license information to end users?

Hi,
I don't think we have a space for that anywhere in the plugin class. It might make a good addition. I'll get back to you on that. I think you should add that to a menu which opens a dialog with your acknowledgements. Rhino plugins that take advantage of open source libraries are credited on this page.

Hi,
I don't think we have a space for that anywhere in the plugin class. It might make a good addition. I'll get back to you on that. I think you should add that to a menu which opens a dialog with your acknowledgements. Rhino plugins that take advantage of open source libraries are credited on this page.


Plugin: fixed count issue of prohibited words checker

This commit is to fix an incorrect count calculation of prohibited words checker
when a soue code files of a commit includes specified prohibited words.
Changes proposed in this PR:

Fixed incorrect count result when use $(....) statement of bash
Updated a report mode (e.g., success, failure, skip, and unexpected error).

Signed-off-by: Geunsik Lim<EMAIL_ADDRESS>
[Template] PR Description
In general, github system automatically copies your commit message for your convenience.
Please remove unused part of the template after writing your own PR description with this template.
$ git commit -s filename1 filename2 ... [enter]

Summarize changes in around 50 characters or less

More detailed explanatory text, if necessary. Wrap it to about 72
characters or so. In some contexts, the first line is treated as the
subject of the commit and the rest of the text as the body. The
blank line separating the summary from the body is critical;
various tools like `log`, `shortlog` and `rebase` can get confused
if you run the two together.

Further paragraphs come after blank lines.

**Changes proposed in this PR:**
- Bullet points are okay, too
- Typically a hyphen or asterisk is used for the bullet, preceded
  by a single space, with blank lines in between, but conventions vary here.

Resolves: #123
See also: #456, #789

**Self evaluation:**
1. Build test: [ ]Passed [ ]Failed [*]Skipped
2. Run test: [ ]Passed [ ]Failed [* ]Skipped

**How to evaluate:**
1. Describe how to evaluate in order to be reproduced by reviewer(s).

Add signed-off message automatically by running **$git commit -s ...** command.

$ git push origin <your_branch_name>

:memo: Version: 1.20180820. Thank you for submitting PR #293. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://invain.mooo.com/.

Aging test is done. This PR is will be merged as a urgent patch.


Move some gnome libs to toplevel

Motivation for this change
cc @jtojnar
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Ok this eval fail is now from hackage-packages.nix.
I'm not familiar with haskell in nixpkgs but I know that this file is autogenerated.

It is probably a good idea to inherit the libraries inside gnome3 attrset, not only for the haskell but also so we could still update them with nix-shell maintainers/scripts/update.nix --argstr path gnome3 (before we implement package tags).

Always happy to help :+1:


Lets try this again. This should be finally fixed

Getting errors of 500 when looking at the API documentation


Adjusting SubmitTransaction rpc call to work with signed transaction …

…serialized with xdr

there are generic encoding methods in types/encode.go called  BytesToInterface and InterfaceToBytes
would be better to use them


i18n

What node modules are providing an i18n interface?
json? xml? yaml?

Lol, I wrote an issue on the wrong tab. Meant to do this on my project.
Sorry :lollipop:


SP API for App Integrations

Note to self: Consider adding this stray API by hand. It seems not to be included in the Open API models.
Use case guide
Reference

https://github.com/amzn/selling-partner-api-models/commit/7fc11fea1f598858f159bbea697b32c0ec618fbe


[CWS] reduce max size of proc_cache and pid_cache LRU maps

What does this PR do?
Those maps (proc_cache and pid_cache) have a very low utilization percentage on some clusters, never being even half full. This PR adds an option to reduce the maximum max_entries value of those 2 LRUs. Ensuring those maps are more correctly sized one.
The end goal is to turn on this config flag slowly internally to monitor the absence of issues caused by this, and then to make it the default (and remove the config flag after that).
Motivation
Describe how to test/QA your changes
Possible Drawbacks / Trade-offs
Additional Notes

/merge


Fork samber/celery-prometheus-exporter

Hi @zerok,
Thanks for you great work !
I needed to fork your project: I made some major improvements that would prevent any upgrade.
You can see my changes here: https://github.com/samber/celery-prometheus-exporter/commit/8b465213743414f261c8a9ab9812e5214e8a4ca9

Hi @samber,
I'm glad that the initial code at least turned out to be inspirational :)  I saw that you provide two docker images (one for Celery 3.x and one for 4.x). That's something I also have planned for the next couple of days as we are moving one of our internal applications over to 4 :)

I just met the case where my workers, producers and celerybeat died at the same time, because of a poor testing environment.
Because the worker pool size is set when event is triggered, the exporter has been unable to update the metric from _process_event.
I made a dirty fix: https://github.com/samber/celery-prometheus-exporter/commit/637c64bfdc84380544d005b2c390a3643b2ad1ff 💩 😱 :trollface:

Hm... that's a weird one. Did you also consider doing the pinging in a separate thread (not the Prometheus client's)?

With a timer ?
mmh yes, it would be cleaner !

Done

Awesome :) Sorry for the late response. If you have some time available, would you like to convert this change into a PR for proper attribution? :)


Publish new release to crates.io

We got a few issues (not that many) of people new to Rust on rust-lang/www.rust-lang.org. The problem is that the readme on crates.io still suggests putting version 0.2 in Cargo.toml. Consider publishing a new release, so the readme is up to date.

done!


Preload api at build time in a serverless env

Is there any way to preload the cache? In a serverless environment, it'll be populated every time which will slow down the function execution speed.

At the moment there isn't but this is something we're planning on tackling early next year.

We shipped a new CLI system in the v5 beta that accomplishes this by pre-fetching, installing, and running code generation. You can see docs on this here: https://api.readme.dev/docs/usage#code-generation


Add support for runtime roles for EMR steps

EMR 6.7.0 and later now support runtime roles that allow you to provide a role to use with a specific Step.
We should update the run command to accept a --job-role for EMR on EC2 clusters similar to how we do for EMR Serverless.

@dacort Does this still need to be implemented? Can I self-assign?

Not being worked on, feel free to contribute and open a PR! Thanks. 😃

Not being worked on, feel free to contribute and open a PR! Thanks. 😃

No problem! Very low-hanging fruit. I tested a few EMR EC2 steps using roles with differently scoped policies, and everything appears to be functioning as expected. Let me know in the PR if you want me to add any additional tests or anything.


bots: Replace / remove the display presence dot for bots with the zulip-bot icon.

[x] Remove the display presence dot for bots in user-profile-popover.
[x] Fix the gap between user-name and zulip-bot-icon in user-profile-popover and user-card.
[x] Replace the display presence dot for bots  with zulip-bot-icon in left-sidebar (pm-list) and recent conversations.
[x]  Fixed the opacity of the group-icon and bot-icon in the PM-list to match the consistency of the left-sidebar.

Fixes: #25066
CZO: Thread

Screenshots and screen captures:

Before:
After:

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[x] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[x] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

The vertical alignment of the bot icon looks off in both places; look at how it appears in the message feed for messages sent by bots -- it should feel like it's in the same horizontal space as the name.

I have fixed the alignment. Could you please review it again and suggest if any changes are required? Thanks :)

Let's fix up the opacity for the bot icon and the group PM icon while we're looking at it. In the left sidebar, they should look the same as the icons for the views at the top. Currently the bot icon looks lower contrast, and the group PM icon looks higher contrast (at least in light theme).

Could we also add more horizontal space before the icon in the user card? It should look more like the message sender spacing.

I'm also not sure about the opacity for the icon elsewhere -- it looks overly faded to me, at least in light theme. Maybe we should try making that match what we end up with in the left sidebar, and see how that looks?

We should also replace the dot with the bot icon in Recent conversations. I'll add that to the issue.

@alya , I have made all the suggested changes and updated the PR description as well. However, for the change in opacity for the presence dot, I have started a  CZO design thread . Apart from that, could you please review the PR? Thank you! :)

Yeah, I didn't intend to suggest changing the opacity of the presence dot -- sorry if that was unclear.

Yeah, I didn't intend to suggest changing the opacity of the presence dot -- sorry if that was unclear.

Reverted that just now :)

After checking with @timabbott , can you please change the user card icon to rely on opacity (0.7 should work) rather than specifying a color?

Generally looks good to me in manual testing. Noting here for future reference that we are using 0.7 opacity in the sidebar, but 0.6 in Recent conversations (for this and other icons). But I don't really want to think about changing those to be consistent right now, as we are planning to redesign both of these parts of the app.

After checking with @timabbott , can you please change the user card and user profile icons to rely on opacity (0.7 should work) rather than specifying a color?

@alya , could you please verify whether you want me to make changes to these icons?

Oh, hm, I was referring just to the bot ones. Are those all specified as colors? If the bot one is the same as those, then maybe let's not worry about it. We have work in progress to redesign the user cards anyhow.

@alya , Yes, the bot icon also has color, just like the other icons present in the user-card. If you have any other changes in mind, please let me know. Thanks! :)

OK, thanks, I think @timabbott can take a look next.

Merged, thanks @palashb01!


Fix decrypt

Type of Change

[X] Bug fix (non-breaking change, fixes #)
[ ] New feature (non-breaking change, adds functionality)
[ ] Breaking change (effects multiple commands or functionality)
[X] Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[ ] Pester test is included
[ ] If new file reference added for test, has is been added to github.com/sqlcollaborative/appveyor-lab ?
[ ] Nunit test is included
[ ] Documentation
[ ] Build system

Purpose
Fixes the command to handle curly brackets and other special characters
Approach
Added "[" and "]" to the object name to make sure the special characters are handled
Commands to test
Invoke-DbaDbDecryptObject
Screenshots

one pass, thanks bud


Live Share

Issue Type: Feature Request
The user code for live share is not working.
VS Code version: Code 1.41.1 (26076a4de974ead31f97692a0d32f90d735645c0, 2019-12-18T14:57:51.166Z)
OS version: Darwin x64 19.2.0

This issue was closed because it doesn't meet our standards of a properly filled issue. Please read our guide about Submitting Bugs and Suggestions.


🐛 [Firebase_storage] I am not able to use its functionality , the plugin is not getting imported

Bug report
Describe the bug
A clear and concise description of what the bug is.
Steps to reproduce
Steps to reproduce the behavior:

Go to '...'
'...'
See error or incorrect behavior

Expected behavior
A clear and concise description of what you expected to happen.
Sample project
Providing a minimal example project which demonstrates the bug in isolation from your main App greatly enhances the chance of a timely fix.
Please link to the public repository URL.

Additional context
Add any other context about the problem here.

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
PASTE OUTPUT INSIDE HERE

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
PASTE OUTPUT INSIDE HERE

Closing this since no information has been provided.
In the future when you file an issue, please provide some/all of the information requested in the issue template.
Thank you


How can i do when i want to display default image .

if user info has it avatar like assets/abc.jpg, how can i do when display at first.

i resolve it  with
        width: 200,
        height: 200,
        round: true,
        srcImage: data.avatar,
      };


Fix typo in GitHub URL

Noticed your GitHub nav link was pointing to jennjunodl on GitHub (with an extra L on the end)

Thank you!


public-sans: 1.007 -> 1.008

Motivation for this change
https://github.com/uswds/public-sans/releases/tag/v1.008
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Notify maintainers
cc @dtzWill

Thank you!


What is action_by_value?

I see ReversiPlayer.action function try select action_by_value when turn > change_tau_turn.
action = int(np.random.choice(range(64), p=policy))
action_by_value = int(np.argmax(self.var_q[key] + (self.var_n[key] > 0)*100))
if action == action_by_value or env.turn < self.play_config.change_tau_turn or env.turn <= 1:
    break

I think action_by_value is the first index with none zero n.
Why did you select action like this?

sorry. I fount it 's best p index with none zero n.


adds an e2e happy path test case for etcd encryption

/test ci/prow/e2e-aws-operator-encryption

/test e2e-aws-operator-encryption

/test e2e-aws-operator

/test e2e-aws-operator-encryption

/test e2e-aws-operator-encryption

/hold
need to make sure the test are stable

/hold cancel
there are some things I'd like to improve but having the tests seems more important


Xref Alignment

[ ] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] If you're unsure, you can format the pull request title like [CAMEL-XXX] Fixes bug in camel-file component, where you replace CAMEL-XXX with the appropriate JIRA issue.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Run mvn clean install -Psourcecheck in your module with source check enabled to make sure basic checks pass and there are no checkstyle violations. A more thorough check will be performed on your pull request automatically.
Below are the contribution guidelines:
https://github.com/apache/camel/blob/master/CONTRIBUTING.md

I’d really appreciate it if everyone would remove this boilerplate before creating a PR.  If you fill it in that’s (possibly) one thing, but just leaving it in place effectively spams the list with a lot of useless verbiage.  An actual description of what the PR does would be really nice, but reproducing this nonsense is really annoying and time consuming to wade through.
I think some projects might have found a way to have this kind of verbiage as a comment in the template, so the instructions are there when you’re creating the PR but then disappear once it is created.
thanks
David Jencks

On Feb 25, 2021, at 1:58 AM, Andrea Cosentino<EMAIL_ADDRESS>wrote:
Make sure there is a JIRA issue https://issues.apache.org/jira/browse/CAMEL filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes.
Each commit in the pull request should have a meaningful subject line and body.
If you're unsure, you can format the pull request title like [CAMEL-XXX] Fixes bug in camel-file component, where you replace CAMEL-XXX with the appropriate JIRA issue.
Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
Run mvn clean install -Psourcecheck in your module with source check enabled to make sure basic checks pass and there are no checkstyle violations. A more thorough check will be performed on your pull request automatically.
Below are the contribution guidelines:
https://github.com/apache/camel/blob/master/CONTRIBUTING.md https://github.com/apache/camel/blob/master/CONTRIBUTING.md

This has been voted and merged as template. If you feel it must be removed,
open an issue, or start a discussion. I'm not against removing it, but
sometimes it doesn't make sense for small PRs. I usually remove it, this
time i forgot about it.
Il gio 25 feb 2021, 17:53 djencks<EMAIL_ADDRESS>ha scritto:

I’d really appreciate it if everyone would remove this boilerplate before
creating a PR. If you fill it in that’s (possibly) one thing, but just
leaving it in place effectively spams the list with a lot of useless
verbiage. An actual description of what the PR does would be really nice,
but reproducing this nonsense is really annoying and time consuming to wade
through.
I think some projects might have found a way to have this kind of verbiage
as a comment in the template, so the instructions are there when you’re
creating the PR but then disappear once it is created.
thanks
David Jencks

On Feb 25, 2021, at 1:58 AM, Andrea Cosentino<EMAIL_ADDRESS>wrote:
Make sure there is a JIRA issue <
https://issues.apache.org/jira/browse/CAMEL> filed for the change
(usually before you start working on it). Trivial changes like typos do not
require a JIRA issue. Your pull request should address just this issue,
without pulling in other changes.
Each commit in the pull request should have a meaningful subject line
and body.
If you're unsure, you can format the pull request title like [CAMEL-XXX]
Fixes bug in camel-file component, where you replace CAMEL-XXX with the
appropriate JIRA issue.
Write a pull request description that is detailed enough to understand
what the pull request does, how, and why.
Run mvn clean install -Psourcecheck in your module with source check
enabled to make sure basic checks pass and there are no checkstyle
violations. A more thorough check will be performed on your pull request
automatically.
Below are the contribution guidelines:
https://github.com/apache/camel/blob/master/CONTRIBUTING.md <
https://github.com/apache/camel/blob/master/CONTRIBUTING.md>

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/apache/camel/pull/5127#issuecomment-786047415, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABG6XV3REGER3OTN6JAMGR3TAZ6B3ANCNFSM4YGF6GQA
.

Opened this: https://issues.apache.org/jira/browse/CAMEL-16261


⚠ ClamAV has degraded performance

In 5990881, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 197 ms

Resolved: ClamAV performance has improved in 85ff190.


Shader compilation speed regression in Chrome 115

We're seeing a pretty significant drop in shader compilation speed in Chrome / Edge 115 on Windows, compared to 114. We have a test example that compiles 18 large shaders (https://playcanvas.github.io/#/graphics/shader-compile). This used to take 2.5s to compile those in 114, vs 20s in 115. Those shaders are pretty complex and use clustered lighting. If the clustered lighting is disabled, the regression is 1.4s -> 3.3s. Would anybody have any idea about what has changed? It's the same story on Canary 117. The profiler as expected shows spending about 1s per shader in getProgramParameter, which is the blocking operation waiting for the results of the compilation and linking. Note that all shaders start the compilation, then all shaders start linking, and only then they start waiting for the results, which should / used to give us their parallel compilation. Is this no longer working?
Screenshot from profiling on 115, not that each shader compilation taking almost 1s.

forum thread: https://forum.playcanvas.com/t/performance-issues-in-chrome-115/32417/10

logged a Chromium bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1468993

suggestion from WebGL Matrix room:

@Maksims - can you please confirm this is Chrome 115 issue as well.

Yes, 115+ is slow, 114 is fine, cheers.

Link without loading everything else: https://playcanvas.github.io/iframe/?category=Graphics&example=ShaderCompile
I'm on: Version 115.0.5790.110 (Offizieller Build) (64-Bit)
But Linux, not Windows.
Performance trace:

It all doesn't take longer than ~3 seconds.
I fooled around with libangle for a C++ project in the past and it's quite complicated... https://github.com/google/angle#level-of-opengl-es-support-via-backing-renderers
They support many backends (that's why I picked it, to test "WebGL" in a DirectX application) and I guess that's what leaves it to the mercy of DirectX on Windows. Since I don't see an issue on Linux, maybe they linked it against another DirectX version / setting / backend?
I just googled and in 2021 it seemed to be possible to pick another backend via chrome://flags/ https://support.google.com/chrome/thread/128645972/choose-angle-graphics-backend-none-of-them-work-well?hl=en
But I don't see that on Linux:

Can anyone test to use another backend via chrome://flags/?

@kungfooman I tried switching 116 to OpenGL backend on Windows - it is much faster:

However, I believe Chromium team has already identified that the issue is related to DX.

However, I believe Chromium team has already identified that the issue is related to DX.

Cool, I just saw the multisampling commit/fix, but I guess that narrows it down anyway then. Can you make a screenshot of that backend option (because I can't see/find it)?

@Maksims - can you please confirm this is Chrome 115 issue as well.

Yes, used Version 115.0.5790.110
Switching ANGLE to OpenGL as @LeXXik suggested reduced compilation times 5 times.

Anyone with access to Chrome on Window: is there a dxcompiler.dll in Chrome, or... with a PE depedency analyzer (e.g. Dependency Walker), does it load this dxcompiler.dll?

Then it should be easy to just download a few .zip releases and test until it is fast again... this wouldn't require any compilation/linking, just .dll swapping, so should be quite fast to tackle it down.

@mvaligursky and others, please regularly test PlayCanvas on Chrome Beta, and ideally at least periodically on Chrome Canary. If a regression like this makes it into Chrome Stable, it is generally not possible to fix quickly.
I hope that it will be possible to integrate the fix for this issue into Chrome 116. See https://chromiumdash.appspot.com/schedule .

Chrome 116 is out .. is somebody able to confirm the fix is in and working? I don't have access to my Windows machine for the next couple of weeks unfortunately.

Oh yes, I don't have times but it's pretty obvious under v116 aritelia.io is super fast to compile its shader once again.

Fantastic, thanks @leonidaspir .
I'll close the ticket, but please reopen it if this still fails in some cases.


REST error response shape changed unexpectedly in 0.14.1

Background
Errors from the REST API changed their shape from
{
  "error": string;
  "code": number;
  "details": any[];
}

to
{
  "message": string;
  "code": number;
  "details": any[];
}

in v0.14.1 as a result of #5473. This has had the unfortunate side-effect of breaking Joule, as it relied on parsing error messages (probably a bad idea tbh, my b) and I can only imagine anyone else parsing or displaying error messages will run into the same thing.
Would there be any interest in rolling back this field name change for a v0.14.2, or was this an intentional rename?

Oh, I wasn't aware of this change in the error message structure.
But yes, it was a fully intentional change. We updated the major version of the REST proxy library (from v1.14.3 to v2.5.0).
It's interesting that this change in structure isn't reflected in the generated API docs (*.swagger.json).
Can you work around this somehow? Because rolling back isn't really an option, we'd also need to roll this back in loop, pool, faraday and lndclient...

It's interesting that this change in structure isn't reflected in the generated API docs (*.swagger.json).

I'm pretty sure it was here: https://github.com/lightningnetwork/lnd/pull/5473/commits/dd749fe5802039f335779b282f3fb854d1094730#diff-a2c955e5bdb220a40ecc95855004e68ee986113afdf29969cd3e1bc37cfe90a7L227-L232

Can you work around this somehow?

Yeah it's trivial to work around once you know what's changed, I was just concerned about anything else out there that might break as a result of this.

Oh, I see. So the message was always there, but now the error was removed.
Since the change happened in a major version update and was quite vital to us (allowed us to bump a whole bunch of other library versions that were stuck because of the grpc-gateway library) and the change is somewhat documented in the API docs, are you okay with us closing this as "expexpected, possibly breaking change"? We can add it more explicitly to the release notes for v0.14.0-beta to make it somewhat more visible.

Sure, I just at the very least wanted to get an issue out there so anyone else who maybe runs into this has something to stumble upon 👍


Connection Information Not Visible In a Query Tab

SQL Operations Studio Version:
Version 0.27.3
Commit 9474415ad68b5a70e8b851698c8c836664a9d5b5
Date 2018-03-27T05:25:59.481Z
Shell 1.7.11
Renderer 58.0.3029.110
Node 7.9.0
Architecture x64

Steps to Reproduce:
Open a query to a Database or Open a Query File and connect to a Database. The information about what you are connected to is displayed in the lower right corner, but the same information is not available in the Window Title at the top or if you hover your mouse over the tab. This is a feature that is available in SSMS and I often have multiple tabs open to different Databases on the same and different Servers. I need a means to be able to tell quickly where my focus is.

dupe #1193


Script Error

Hey @DarienBrito
Im really excited about the possibility of using your tool!
I installed it and i'm getting an error. The camera ID's are being recognized on the configuration tab after pulsing, those Ids are not being imported into the calibration tab however so the calibrate pulse and refine pulse are not functional.
Inside of the AzureCalibration bin i'm receiving this error:

I'm running TD under windows 10 with Commercial license i purchased this week, so assuming the most recent version.
Id love to get this usp and running for a big art install i'm doing in Mexico next weekend.
thanks for you help!
Sam

Hi Sam,
Just in case, the tool has been just updated to latest. That may solve your issue.


请问envs/init.py里的from .uav import UAVEnv中的UAVEnv文件可以提供嘛？

Since the environment file needs to be used in another paper being written, it is not provided. The Repo only provides algorithm-related files.


Rename: upgrade_ohl_my_zsh -> upgrade_oh_my_zsh_all

Hi! This is just a request, but like this commenter https://github.com/TamCore/autoupdate-oh-my-zsh-plugins/pull/11#commitcomment-40476579, I found the name to be a little confusing. What do you think about renaming the alias to upgrade_oh_my_zsh_all?

Thank you! :tada:

oh man! it took me a while to realize that this alias was changed. It would have been nice to keep the existing alias and add new one instead of removing the existing one breaking the behavior :(


chore: specify an optional preview destroy dir parameter

Display of what I have with the jx-preview from this solution PR (looks good):
jx preview destroy --dir . xxx-yyy-pr-zzz
destroying preview: xxx-yyy-pr-zzz in namespace jx
using ingress sub domain -jx-xxx-yyy-pr-zzz.
deleted preview namespace jx-xxx-yyy-pr-zzz
deleted preview: dailymotion-xxx-yyy-pr-zzz in namespace jx

What I had before, and the problem I want to solve after having this kind of error on a new cluster configuration:
jx preview destroy xxx-yyy-pr-zzz
destroying preview: xxx-yyy-pr-zzz in namespace jx
using ingress sub domain -jx-xxx-yyy-pr-zzz.
WARNING: could not delete preview resources: failed to run destroy command: failed to run 'helmfile --file /path/to/helmfile.yaml destroy' command in directory '/tmp/jx-git-3158788822', output: 'specified state file /path/to/helmfile.yaml is not found'

The function here only git clone from the main branch.
On the case we add a total new helmfile on a PR or add new component on helmfile from a PR not yet merged, it won't be taken into account because the Git Clone only do it from the main branch.
On my case, because I have also already git clone the project before the destroy, I don't need to do it again.
This PR is here to add an optional dir parameter on the preview destroy.
On the case the dir parameter is empty (it is by default), nothing will change and it will git clone the source.
A next PR could be to also add optional parameter in order to Git Clone a specific branch instead of only main.

/ok-to-test

I had this locally
verifying<EMAIL_ADDRESS>checksum mismatch
        downloaded: h1:WFd2PMLlOBCGVv/KcnpOJqvjro0EClWggalSjj4ahzo=
        go.sum:     h1:+O+kEJ60YyS3ARa9DrEkU7QvdKgRGYTf8IfOLcFTlnA=

this is why I did the change, let's rollback that and see how it goes


There is no way to view all matched/rejected matches

In WHG one can filter in the browsling panel to see all items reviewed or non reviewed:

It would be good to have this functioning. We need to add a mechanism to see matches that we did. The information is in the place_link table. This table has a set of links for some of the places (one place -> many place_links). The type of the link is in the jsonb field. External links are those whose type is "closeMatch". For example: {"type": "closeMatch", "identifier": "wd:Q31864504"}. Internal links are everything else except type "different". So for example: {"type": "same_as", "identifier": "Yaqut:dig03853"} is an internal link and  {"type": "different", "identifier": 33726} is not a link.

[ ] Remove the 'ccodes' column
[ ] Add a column to the list of places called External matches that has a checkbox if the place is matched to external sources.
[ ] Add a column to the list of places called Internal matches that has a checkbox if the place is matched to other datasets in MEHDIE
[ ] Add a column to the list of places called Rejected matches that has a checkbox if the place has matches that were rejected to other datasets in MEHDIE
[ ] Add tool tips to explain these columns: External matches: "This field has a checkmark if the place is matched with external sources such as Wikidata and Geonames". Internal Matches: "This field has a checkmark if the place is matched with a place from at least one other dataset on MEHDIE."Rejected matches: "This field has a checkmark if the place was matched with a place from another dataset on MEHDIE and this match was rejected.
[ ] Change the mechanism for the filter above the table to show the following options: "All, has matches, has internal matches, has external matches, has rejected matches." Filter the table accordingly to show All, only those rows with checkmarks in the internal matches field, only those rows with checkmarks in the external matches field, only those with chekmarks in the rejected matches field.

For example, this place:

Was supposed to be matched with Yaqut and does not appear in the list of matches.

Resolved in another way


Loxone integration stops working

Which Model do you use from loxone? Miniserver? Gen1 or Gen2?
Gen1
Which software version does your loxone use?
<IP_ADDRESS>
How did you install HomeAssistant? Over Hassio or manual install?
Proxmox mit Hassio
Which Version do you use of HomeAssistant?
2023.4.6
Describe the bug
The integration works for about a day, after which no more communication between Loxone and Homeassistant is taking place. Everything was still working before March (and has been working stable for the last few years, thanks!). However, as I upgraded the Loxone firmware and Home Assistant in this period, I am unsure what the last stable configuration was.
Note that the problem also occured with PyLoxone 0.4 (I tried the 0.5 betas as well). I recently updated Loxone to 14.0, however, the problem also occured in 13.x.
Paste the error log with the following settings:
home-assistant_2023-04-25T04-52-20.642Z.log

@arjenvrh the log seams form the beta version. Please go back to the latest stable release if you do not miss some features. I am not really sure if the beta will become the next stable release. The beta is a complete rewrite of the websocket communication and  I am not really glad with the current implementation. It uses the  aiohttp lib for websocket and it is not really good for this.
I would use the latest stable release if you have problems. And now to your problem. I is interesting in your log is this line:
2023-04-25 03:14:34.205 WARNING (MainThread) [homeassistant.components.unifi] Lost connection to UniFi Network
Can it be that you have lost the connection for some time? I know that there is a problem when sending a command like the keepalive message when the connection is not established at this time. Did you change something on you network? Because I did not changed anything which is related to connection for a long time. And on HA there has also nothing changed and on the loxone side also no big changes. Can you go back to the stable release and try again?
I am not really glad how the implementation is working now but I have not so much time to rewrite it from scratch. The biggest problems I had in the past is with not stable connections and connection loses.
And if you go back to the stable release I always had to install it twice over hacs. I do not know why but for downgrading I needed two installs.

@JoDehli As stated I've been on the stable version a long time, I just upgraded to the beta this weekend to test if it had the same issue. I've also noticed the UniFi network warnings, which so far I've been unable to explain. The UniFi access points and controller have not had any updates over the last few months.
However, as Home Assistant is on a wired network I do not expect this to be the problem. I'll try reverting to an older VM and version of Home assistant to see if this has any influence. I'll report back here in a few days with my findings.

@arjenvrh I now have another issue. I do not know if this is related to your problem. But I downgraded my installation to the 0.4.3 Version now. Lets see if any problem occur on my system. But as I already said I had problems to to downgrade over hacs from the beta release. I had to delete the custom components folder manually and then install the 0.4.3 from hacs to get the version running.

@arjenvrh Ok I tried to reproduce the error and I think I found something. It is definitely related to the stability of the network. I have tried hundreds of times to reproduce the error. I managed to reproduce the error only 1 or 2 times on my system. I was not able to force the error in the 0.4.3 version. Therefore, the error should not actually occur in 0.4.3. I have now also created a new beta version where I caught the error. You are welcome to try the latest version.
As I said, I haven't quite figured out when exactly the error occurs. I have cut the network connection and partly kept disconnected for several minutes and still the connection did not disconnect and I could still control my Loxone via Homeassistant.
Translated with www.DeepL.com/Translator (free version)

@JoDehli I've been testing for the last 1.5 weeks and everything is running stable as a rock with the last beta release. Thanks for the help!


Fixing directory/file selection logic to deselect folders properly and always hightlight files.

Follow up bug fix from https://github.com/KittyCAD/modeling-app/pull/4392

Weird my other commits are showing up here - I'll give it a moment


ARTEMIS-2109: fix ErrorProne for JDK8, move to profile

Fixes the updated configuration for ErrorProne so it can actually run on JDK8.
Also moves it to a specific profile for optional use on JDK8, as the 2.4.0+ javac plugin approach requires forking the compiler on JDK8, which is slow and adds a couple of minutes to the build from all the modules. On JDK8 Error Prone is activated on request. On JDK11+ it is still enabled by default.
Updates the CI job config as well to still enable ErrorProne for JDK8  (i.e. on all JDKs being used).
Follows the changes in #3179 (and #3183).

No, as that would enable the JDK8 arguments on 11+ and break them. The profile can be activated explicitly with -P or by JDK8+property. Using the property as here stops it from actually adding the JDK-8 specific bits on JDK11+ when run there (since the job script is shared across all 3) which would break.


Introduce repeatable alert

Currently the notification in EaseProbe is using edge triggered mode which means one notification will be sent only once when the status changes, but people may miss notifications in some situations, below are some:

one was busy at something else when receiving a important fail notification, and when he came back the alert was just forgotten, as you know, people always forget
in some times of emergency, one will receive many notifications in a very short period, unfortunately there are two different problems in these notifications, one is resloved, but other one was just neglected

In other notification systems using level trigger mode as I know, aliyun is using a silence duration to control repeatable alert.
So is it necessary for us to introduce a similar mechanism? What is your opinion? @haoel @proditis

This is a good issue.
I thought this before I wrote the first line code of EaseProbe, edge trigger or level trigger really put me in a dilemma.  And it never disappears from my mind.   Thanks to bring this here.
for the level trigger, I have the following concerns

Most of the time, an accident could cause many services unavailable, and they all keep sending alerts, your phone or other notifiers would be flooded totally.

The silence duration would be magic work, nobody can set it right.

Maybe, we can use something like "exponential backoff". For example, only sending 5 alerts, the time between them can be deltaTime = 2*deltaTime (deltaTime can be initialized as probe interval)

I like the backoff strategy, it's commonly used for handling failed operations in Kubernetes, all we need is to choose a reasonable  amount of time and a maximum number of retries.


Error loading when select a pod inside namespace

Hello!

Using Windows 10 19042.746, with VS Code in WSL 2
In this new version v.1.2.3 i´m facing some troubles with:
1- When I try to use the namespace and try to portfoward, appears the error:

Error loading document: Error: cannot open k8smsx://loadkubernetescore/pod-monitoring%20%20%20%20%20%20%20grafana-5c6f79684f-p5f2g.yaml?ns%3Dall%26value%3Dpod%2Fmonitoring%20%20%20%20%20%20%20grafana-5c6f79684f-p5f2g%26_%3D1612186166678. Detail: Unable to read file 'k8smsx://loadkubernetescore/pod-monitoring       grafana-5c6f79684f-p5f2g.yaml?ns=all&value=pod/monitoring       grafana-5c6f79684f-p5f2g&_=1612186166678' (Get command failed: error: there is no need to specify a resource type as a separate argument when passing arguments in resource/name form (e.g. 'kubectl get resource/<resource_name>' instead of 'kubectl get resource resource/<resource_name>'
)

2- when I trey to open a Pod in a Terminal:
Failed to get containers in resource: error: there is no need to specify a resource type as a separate argument when passing arguments in resource/name form (e.g. 'kubectl get resource/<resource_name>' instead of 'kubectl get resource resource/<resource_name>'
Thank you!

Hello @dnegrisolli, your issue looks similar to https://github.com/Azure/vscode-kubernetes-tools/issues/867 and it was fixed by https://github.com/Azure/vscode-kubernetes-tools/pull/868. You should see it working again from next release.

Hello @dnegrisolli, your issue looks similar to #867 and it was fixed by #868. You should see it working again from next release.

I´m sorry! As I received a e-mail, i though it was the latest version.


Ibex version 1.0

@eladiw, @itye-msft - lmk when you had time to integrate with ibex-version-1.0 and do sanity checks.