qsignature: variable overlap in bcbio 1.0.6a compared to 1.0.3

The qsignature score seems to be not normalized in the sense that its value depends on the number of SNPs that can be used to compare samples. In the qsignature version used in bcbio 1.0.3 this could be calibrated against the size of the panel that was used.
When moving to bcbio 1.0.6a from bcbio 1.0.3 I noticed that now there is huge fluctuation of how many SNPs are used to calculate the qsignature score (all samples are from the same panel, qc scores are very homogeneous). This renders the qsignature score unusable.
Is anybody else experiencing these issues?

Ben - thanks for reporting this. I wanted to cc in @lpantano to see if she has any thoughts. I don't think we had intentional changes here but would like to get to the bottom of what is going on so we can provide useful output. I haven't been following closely enough to know all the changes but hopefully Lorena has some insight.

Hi,
Specifically for this issue, I didn’t change anything in the code, not sure if the tool has been updated or not.
About the analysis (that hasn’t changed in a while):
It’s true that the score from qsignature aren’t normalized by the number of SNPs, basically we are outputting the values the tool calculate. As well, we hard-code some cutoff to define samples, what is not good either for the same problem.
I agree that it would be good to have this in a better shape, but for that, we need data that we now what they are and then play with using the whole genome, only exomes, or less. And define a way to normalize the scores so it’s independent of number of SNPs.
Cheers

On Nov 2, 2017, at 10:18 AM, Brad Chapman<EMAIL_ADDRESS>wrote:
Ben - thanks for reporting this. I wanted to cc in @lpantano https://github.com/lpantano to see if she has any thoughts. I don't think we had intentional changes here but would like to get to the bottom of what is going on so we can provide useful output. I haven't been following closely enough to know all the changes but hopefully Lorena has some insight.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/chapmanb/bcbio-nextgen/issues/2134#issuecomment-341435441, or mute the thread https://github.com/notifications/unsubscribe-auth/ABi_HCa4GBU6IIlYUL_QaC1U5hsnR246ks5syc88gaJpZM4QPbws.

That's odd. I don't think qSignature changed in a long time -- how were those scores normalized before? I've only used it for WGS runs and some experimental exomes, and score distributions did differ a bit between the two technologies.

Just to give you an example of the difference that I see between bcbio 1.0.3 and bcbio 1.0.6a, here the results from the same sequencing run that I repeated with both versions.
qsignature.xml from bcbio 1.0.3:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<qsignature>
<files>
<file coverage="9228" id="1" name="/bioinf-data/01_S1.qsig.vcf"/>
<file coverage="9292" id="2" name="/bioinf-data/02_S7.qsig.vcf"/>
<file coverage="9445" id="3" name="/bioinf-data/03_S13.qsig.vcf"/>
<file coverage="9300" id="4" name="/bioinf-data/04_S19.qsig.vcf"/>
<file coverage="9528" id="5" name="/bioinf-data/05_S25.qsig.vcf"/>
<file coverage="9508" id="6" name="/bioinf-data/06_S31.qsig.vcf"/>
<file coverage="9431" id="7" name="/bioinf-data/07_S37.qsig.vcf"/>
<file coverage="9519" id="8" name="/bioinf-data/08_S43.qsig.vcf"/>
<file coverage="9356" id="9" name="/bioinf-data/09_S2.qsig.vcf"/>

bcbio 1.0.6a:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<qsignature>
<files>
<file coverage="1220" id="1" name="/bioinf-data/01_S1.qsig.vcf"/>
<file coverage="1228" id="2" name="/bioinf-data/02_S7.qsig.vcf"/>
<file coverage="1552" id="3" name="/bioinf-data/03_S13.qsig.vcf"/>
<file coverage="1231" id="4" name="/bioinf-data/04_S19.qsig.vcf"/>
<file coverage="292" id="5" name="/bioinf-data/05_S25.qsig.vcf"/>
<file coverage="1244" id="6" name="/bioinf-data/06_S31.qsig.vcf"/>
<file coverage="291" id="7" name="/bioinf-data/07_S37.qsig.vcf"/>
<file coverage="1234" id="8" name="/bioinf-data/08_S43.qsig.vcf"/>
<file coverage="1545" id="9" name="/bioinf-data/09_S2.qsig.vcf"/>

Ben -- thanks so much for checking on this. I've looked through the history of qsignature (https://github.com/chapmanb/bcbio-nextgen/commits/master/bcbio/qc/qsignature.py) and I can't see any obvious changes here. The major changes have been swapping out parsing to avoid import errors but there hasn't been a new version of qsignature.
If you look at the qsignature command logs for the two versions in log/bcbio-nextgen-commands.log are there any differences in how it's invoked? Any ideas of how to start digging for differences would be really helpful. Thanks for the help debugging.

And just to double check, I would check the BAM files are similar.

On Nov 4, 2017, at 12:16 PM, Brad Chapman<EMAIL_ADDRESS>wrote:
Ben -- thanks so much for checking on this. I've looked through the history of qsignature (https://github.com/chapmanb/bcbio-nextgen/commits/master/bcbio/qc/qsignature.py https://github.com/chapmanb/bcbio-nextgen/commits/master/bcbio/qc/qsignature.py) and I can't see any obvious changes here. The major changes have been swapping out parsing to avoid import errors but there hasn't been a new version of qsignature.
If you look at the qsignature command logs for the two versions in log/bcbio-nextgen-commands.log are there any differences in how it's invoked? Any ideas of how to start digging for differences would be really helpful. Thanks for the help debugging.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/chapmanb/bcbio-nextgen/issues/2134#issuecomment-341909315, or mute the thread https://github.com/notifications/unsubscribe-auth/ABi_HMSMYII731I9fb57C4DWauVgvBWxks5szI3ngaJpZM4QPbws.

We identified a bug in qsignature as the cause when using GRCh37 (instead of hg19). See this sourceforge thread: https://sourceforge.net/p/adamajava/discussion/general/thread/e9fdfc07/?limit=25#67b7

Ben -- thank so much for tracking this down. It sounds like we need to ping them about having a new release version of qsignature to fix the problem? It doesn't look like there are any new releases including Roland's patch at this point. Or have you found an alternative way to work around the issue? Thanks again for being on top of this.


Please enable support for Dashboard Native Filters in Superset

I think this is very important functionality for building our data browser.  Can you please enable?
https://github.com/apache/superset/issues/12148
@erikerlandson
@oindrillac

Looking at the history since 1.1.0 (the current version installed), it looks like Dashboard Native Filters continue to undergo major improvements and are a specific call-out of functionality "hardened and polshed" in 1.3.0: https://github.com/apache/superset/releases/tag/1.3.0
That release has been out since 30 August 2021.


Alias relation of /blog/[category]/[createdAt]/[title]

Maybe I am doing this wrong, but I would like to have my URL look like this:
/blog/[category]/[createdAt]/[title]
The category is a relational field type and the createdAt date is auto generated for each post.
For an example, all my URL alias's should look like the following. Each post is neatly organized into the year, month and day.
/blog/how-to/2022/10/12/upgrade-your-crosshair-vi-hero-motherboard-firmware-with-system76-s-pop-os/

Hi @csharpee,
As of now, only fields of type id, uid or string are allowed into the url pattern.
That means you cannot use a relation (like category) and I believe createdAt is also not possible as it is not one of these field types.
In the future these features will be added but in the short term this will not be worked on.


[i18n] Fix ru locale

VSCode Version: 1.9.1
In the main menu, the russian translation looks ugly & does not correspond generally accepted standards.

En
ru locale now
ru locale fix

View
Просмотреть
Вид

Edit
Изменить
Правка

Go
Перейти
Переход

Selection
Выбор
Выделение

PS. Where you are translating?
Maybe it makes sense to use the special services, such as transifex.com, etc ?

@lukaschal, general menu translation

Waiting for linguistic input.

These fixed as suggested.
SRC: &&Edit
TGT: &&Правка
SRC: &&Go
TGT: &&Переход
SRC: &&View
TGT: &&Вид

@buzzzzer Please, is it possible to add ENU/RUS screenshot with "Selection" string to see context of this term ?

@lukaschal, yes.
sublime: Selection > Выделение

Adobe Illustrator: Select > Выделение

Fixed as suggested.
File: src\vs\code\electron-main\menus.nls.resx
ID: ".resx", 0; "mSelection"
SRC: &&Selection
TGT: &&Выделение

and now all translations of VSCode are managed in Transifex, so improved translations/suggestions can be added there. see this for more info https://github.com/Microsoft/Localization/wiki/Visual-Studio-Code-Community-Localization-Project (and thank you @buzzzzer for raising the issue and for already suggesting these changes in Transifex!)


Center Image inside slide

We have autoHeight:false and centerImage: true, inside a slider image with height:100% and width:100% and margins set to 0.
element {
    width: 100%;
    height: 100%;
    margin-left: 0px;
    margin-top: 0px;
    margin-bottom: 0px;
}

The image (505x600px orginal size) is inside a sp-image-container with generated dimensions height: 400px; width: 641px;:
<div class="sp-image-container" style="height: 400px; width: 641px;">
<img data-v-3568e6ce="" src="/uploads/275/Logo/Flightcases/611d497f4769a.jpg" class="sp-image"
data-default="/uploads/275/Logo/Flightcases/611d497f4769a.jpg"
style="width: 100%; height: 100%; margin-left: 0px; margin-top: 0px;margin-bottom: 0px;">
</div>

In a landscape sized slider and slide a portrait image is kind of squashed. And more importantly, we do not see it centered.
When I change height to auto the image is clear, but then the position is off. It is only partly shown that is. Only the top shows:

When we set the width to auto and height to a 100% I can see the entire image, but then the image and background only take up 50% of the width of the rectangular slider:

However, for the rectangular images that setting would cause the image to be partly cut at the right side. So for landscape this would be better:
element {
    width: 100%;
    height: auto;
    margin-left: 0px;
    margin-top: 0px;
}

but we still miss part of the slider here yet again:

How can I just center this portrait sized image in our landscape slider with it filling the size set for the slides?

I do think if we can set height:auto for landscape images in our setup and width:auto for portrait images and set margin-top or margin-bottom per image/slide we will be doing just fine.

Hmm, it seems we are having a tough time setting margins and dimensions per individual slide. Any suggestions there or is this just not possible?

Hi,
I would recommend using the slider's settings instead of CSS when possible, because CSS, especially inline styles, are overwritten sometimes by the slider. If I understand correctly, you're trying to get the image to be fully visible inside the slider and centered. For this, you would just need to set the imageScaleMode to contain.
Best,
David

@davidghi . Thanks a lot for getting back so fast. We are just now trying to work with imageScaleMode `contain and then set the slide container to a color to match the image background color. Were trying to do it all the hard way and this more native Slider Pro way seems to be the way to go. Thanks again David.


Imperfect/Inconsistent (?) resizing in regards to window snapping and maximizing

This has been an issue for as long as i've used berry but finally decided to make an official issue.
I've noticed that when moving windows with keybinds (either mod + O/P to snap left or right, or mod + M to maximize) it doesn't perfectly resize/place the window on first key-press; You have to press the same keybind again and it will shift the window size/position to properly lock it into whatever configuration you just pressed (it's usually a matter of just a few pixels).
I've attached screenshots to show what I mean. I'm not sure if this is a math issue in code when resizing windows or what, but it is a bit frustrating if you notice it (I happen to be demonstrating this issue in sourcemage linux, but it happens on every system that i've tried berry on, both real hardware and virtual machines, and over multiple berry versions)
(it can be hard to notice the differences, but for maximize, there's a few pixels of deadspace to the right on the first mod-m. Pressing Mod-m a 2nd time correctly fills the rest of the space with the terminal window. Same with Mod-O, the first press doesn't correctly fill up the entire left half of the screen - a second Mod-O extends the window to the right by a few pixels to correctly fill exactly half the screen with the window)
(For more information, the resolution of this current setup is 1366x768, but i've had this happen at any resolution on other machines)

To rule out some things - I've also replicated this issue without the window title borders, so that's not something that's affecting this

Even extra information! (Sorry, really don't want to add all of this into the main post, it's already a mess to read) A while back, I made some modifications to berry in order to add the functionality of quartering windows, in order to snap to topleft, topright, bottomleft, bottomright (Didn't officially fork it so my changes were undocumented, i'm sorry open-source community) . The code I hacked together was the same code used for Mod-O/P, but just halved. In my testing, quartering windows worked BUT I ran into this same issue of having to use two key presses in order to fully lock the window to the correct dimensions. With the current Mod-O/P and Mod-M issue, it's an issue on the horizontal axis (the windows are the correct vertical height on first keypress) with my modification, both horizontal height and vertical height were wrong, so it would shrink/expand in both directions, depending on whether the window was topright, bottomleft, etc. etc.
This lends further credence to it being an issue either with the math used to move the windows, or the function of moving the windows itself.

Thanks for the detailed write-up. Whats the terminal application you're using?

Thanks for the detailed write-up. Whats the terminal application you're using?

xfce4-terminal in this instance, although this happens with any application (i'm just displaying the issue with this because my current system is very bare, I don't have any other screenshot applications installed beside scrot) I could spin up a VM (maybe archcraft, they have a berry config) and screenshot the same issues if need be! I didn't pick a very good system to display this problem on

Hmmmm, I'm not able to repro this. Can you post your autostart?

Yeah sure! My autostart is just the default one that comes with berry, with my sxhkd start line at the top of it.
Interestingly enough, i'm testing it with other windows and it actually doesn't seem to be having the same issue... I swear I remember it happening with all programs (although admittedly it's been awhile since i've daily driven berry, I could be mistaken) It is however consistently happening with my terminal window (which is xfce4-terminal)
I'm going to load up a vm and do some testing, see if I can get this bug to happen with other programs, or see if it's possibly a bug with only terminals/only xfce4-terminal

Ok, update! I'm actually on my main system now, I already had berry installed so I logged out and switched to it (i'm on Arch)
I cannot produce the bug with any other programs except terminals! I've tried multiple terminals now, here are my findings:
Alacritty: fine
Sakura: fine
xfce4-terminal: bug
gnome-terminal: bug
urxvt: fine
uxterm: fine
xterm: fine
kitty: fine
I can only seem to reproduce the bug with gnome-terminal and xfce4-terminal (this is on both of my systems, so not distro-specific) I would say it's a VTE issue (as xfce4 and gnome terminals are both VTE-based) but Sakura is also VTE-based and doesn't have the issue, so i'm stumped.
If you can, try out both xfce4-terminal and gnome-terminal in your testing and see if you can reproduce.


Feature: Add Auto-Trigger Crash Screen to OOT

Title is self-explanatory. I think we need this, especially if we plan to debug anything in the future regarding OOT.

Done by https://github.com/OoTMM/OoTMM/commit/96b95e5ee471ade73433eb0592b73b564ad49082


IPFS adoption by non-techie people is hard

When I say to anyone to download IPFS Desktop, I can't expect them to read all the webpage, then find the download link on Microsoft Github.
They aren't interested in what features the protocol has to showcase. They aren't interested in how it works. They simply want to download the app to be able to get my files I put on IPFS for them.
Currently:

user lands on ipfs.io
finds no download link
has to read nearly whole homepage (they won't, so they have to scroll through)
has to select IPFS Desktop from many choices
is redirected to Microsoft Github
has to find the "Releases" page in the developer-oriented interface of Microsoft Github (they don't even know what version-control or even source code means, or not familiar with software development flow, so they won't find it)
has to find the package for their architecture (some doesn't even know that Microsoft Windows use .exe, Apple macOS use .dmg, and GNU/Linux use .AppImage)
download and install

What would be ideal:

lands on ipfs.io
see a highlighted Download link, so they can click it
Options: Linux, macOS, Windows, mobile app store links (less highlighted text: command line, source code, other platforms)
download and install

Hi @notramo - we are actually currently working on an improved download flow for the main ipfs.io site, for implementation in Q1. As you noted, it'll include a direct download pathway, including OS and/or browser (in the case of IPFS Companion) detection to help new users download the best option for them.
The work isn't in GitHub issues just yet, but when implementation starts you can follow along in the ipfs/website repo. Closing this issue with all that in mind, but please be assured we are working on it. Thank you!


fixed bug

Fixed an issue where the check to determine if a non-cuda gpu existed would always fail

Could you add better description in the commit message?
Can't this change be also submitted to upstream in the IREE repo? Is this a problem with Shark specificay?

Could you add better description in the commit message? Can't this change be also submitted to upstream in the IREE repo? Is this a problem with Shark specificaly?

provided

Fixed an issue where the check to determine if a non-cuda gpu existed would always fail

Probably, but I would really like this merged into shark as soon as possible, and I don't know if going through iree would cause even more delays

I meant to also submit it there as well as here.

I meant to also submit it there as well as here.

yeah i can create  a PR for iree too


Handle unicode text

Attempting to use theanets.recurrent.Text on a UTF8 encoded corpus used to give an error
---------------------------------------------------------------------------
UnicodeEncodeError                        Traceback (most recent call last)
/home/fl350/bachbot/scripts/theanet/theanet.py in <module>()
     24 with codecs.open(path, 'r', 'utf-8') as handle:
     25     file_data = handle.read().lower()
---> 26     text = theanets.recurrent.Text(file_data[:int(VAL_FRACTION*len(file_data))])
     27     text_val = theanets.recurrent.Text(file_data[int(VAL_FRACTION*len(file_data)):])
     28

/home/fl350/theanets/theanets/recurrent.py in __init__(self, text, alpha, min_count, unknown)
     89                 collections.Counter(text).items()
     90                 if char != unknown and count >= min_count)))
---> 91         print type(r'[^{}]'.format(re.escape(self.alpha)).encode('utf8'))
     92         self.text = re.sub(r'[^{}]'.format(re.escape(self.alpha)).encode('utf8'), unknown, text)
     93         assert unknown not in self.alpha

UnicodeEncodeError: 'ascii' codec can't encode character u'\x83' in position 85: ordinal not in range(128)

This is fixed by this PR.

Coverage decreased (-0.1%) to 94.768% when pulling eaca4337d972edfe1d44a93e2d93701dbab98766 on feynmanliang:text-handle-utf into b637b01bc4f1ef69fda9a23f5637462a1188ebdb on lmjohns3:master.

This can get pretty tricky with text encodings. My preference is to always operate with unicode, because then iterating over a string is guaranteed to iterate over a "letter" instead of iterating over parts of multi-byte characters. That said, I haven't been very careful about enforcing this!
This is additionally complicated by the fact that Py2 and Py3 have different defaults for handling strings. I personally use Py3 but I try to test everything with Py2 as well (see the Travis config).
Which version of Python are you using? Can you try using a "unicode" object instead of a UTF-8 encoded byte sequence to see if this problem persists? Can you add a test to run a unicode object through the recurrent infrastructure and add it to this PR? Also, this PR breaks an existing test, please fix.

Thanks for taking a look, I will push some changes soon to address the issues

I'm using 2.7.3
I can repro with the following code

with codecs.open(path, 'r', 'utf-8') as handle:
    file_data = handle.read().lower()
    text = theanets.recurrent.Text(file_data[:int(TRAIN_FRACTION*len(file_data))])
    text_val = theanets.recurrent.Text(file_data[int(TRAIN_FRACTION*len(file_data)):])

or using a unicode object
with open(path, 'r') as handle:
    file_data = unicode(handle.read(), 'utf-8').lower()
    text = theanets.recurrent.Text(file_data[:int(TRAIN_FRACTION*len(file_data))])
    text_val = theanets.recurrent.Text(file_data[int(TRAIN_FRACTION*len(file_data)):])


Add contact form

Structure:
To get in touch, please select the reason for contacting us (required):
[select menu: contains a list of options (forthcoming). Selecting certain of the options triggers a panel like the following*:]
Is your question answered below? (Click each question to view answer).
[FAQ items related to user's selection appear here (as well as the contact form, which has been hidden until now). This is to head off emails that may be answered by FAQs.]
If the above does not answer your question, please use the form below:
[name] (required)
[your email address] (required)
[subject] (required)
[textarea for message] (required)
[SUBMIT]

if user's reason for contacting is not in the list, they can choose "other" and just have the contact form appear.

Here are the select menu options (and what the page should do in response to each selection):
I am reaching out because:

I have questions about why (and by whom) the Community Resource Explorer was built, who funds it, etc.

display FAQs from the “background” section below this menu

I have questions about the data: how it was calculated, where it came from, which schools are included, etc.

display FAQs from the “about the data” section

The data does not match my personal experience

Display FAQ item: “The data for my neighborhood doesn’t match my personal experience. Why might that be?”

I’d like to stay informed about the Resource Explorer

FAQ item: “How can I stay informed about updates to the CRE?”

I’d like to share insights about my neighborhood to help improve the Resource Explorer

FAQ item: “I have insight about my neighborhood that I would like to share. How can I do that?”

I am interested in applying the Resource Explorer to schools outside of Dallas ISD. Whom should I talk to?

FAQ item: “I am interested in the CRE for schools outside of Dallas ISD. Who should I talk to?”

I need help with using the website or something’s not working

This creates a form that routes to us instead of CPAL. I will set these forms up in Netlify and share the code to incorporate soon.

Another reason

Skips FAQ items, just goes to the regular form

Note that per the above, there will need to be 2 forms: one for submissions to CPAL (which should appear for all the selections but one), and one that routes to us (for site usability/troubleshooting questions). Will set those up and share the form id's with you.

basic form implemented. might want to test it's submitting correctly. I'll let you close if sufficient @james-minton


Chef::REST api does not say what types of objects are returned

I recently wrote some code to generate new certs for some clients. I ran into an issue where the api call to reregister a client returns #<Chef::ApiClient> but the call to register a new client returns a #<Hash>. I would assume they would return the same type of thing. I couldn't find any documentation telling me what type of objects to expect. Everything I found just says returns Object so I had to figure it out through guess and check.
I included my code below. The two lines of note are private_key = r.private_key and private_key = r['private_key']
api = Chef::REST.new(
    chef_server_url,
    client_name=cert_name,
    signing_key_filename=cert_path
)

if api.get('clients').key?(my_name)
    # re-registering returns #<Chef::ApiClient>
    json = { :name => my_name, :private_key => true, :admin => false }
    r = api.put("clients/#{my_name}", json)
    private_key = r.private_key
else
    # registering returns #<Hash>
    json = { :name => my_name, :admin => false }
    r = api.post('clients', json)
    private_key = r['private_key']
end

File.open(client_key_path, "w") do |f|
    f.print(private_key)
end

So our documentation sucks on various levels, it'd be better to either open a PR against the chef-docs repo:
https://github.com/chef/chef-docs/issues/new
Or to issue a PR against this repo to add YARD documentation to the code.  Otherwise this issue isn't very useful for prioritization and we know that we need better documentation and we're trying to work on it (e.g. a261c2c6954a6e3c682ff40a4c82d30ed994bdd8, 320aa0fe43158c8c89bfab7f1494271eb9da7cd).


PairwiseAMG crash in parallel

Hello, I am experiencing a crash with PairwiseAMG when used as a CG preconditioner in parallel (I am using f72a3919b52b rocALUTION version on CPU).
I reproduced the crash with the cg-amg_mpi sample and the gr_30_30.mtx matrix (it works with less MPI ranks):
$ mpirun -np 31 /export/home/catA/pl254994/trust/amgx_openmp/lib/src/LIBROCALUTION/clients/staging/cg-amg_mpi gr_30_30.mtx
No OpenMP support
rocALUTION ver 3.0.3-59debfadc-dirty
rocALUTION platform is initialized
Accelerator backend: None
No OpenMP support
MPI rank: 0
MPI size: 31
ReadFileMTX: filename=gr_30_30.mtx; reading...
ReadFileMTX: filename=gr_30_30.mtx; done
double free or corruption (out)
double free or corruption (out)
double free or corruption (out)
double free or corruption (out)
double free or corruption (out)

On my matrix (2 592 000 rows) in my code, it crashes above 7 MPI ranks (C-amg and SA-amg works fine):
....
[rocALUTION] Time to convert TRUST matrix: 0.509774
[rocALUTION] Build a matrix with local N= 324001 and local nnz=1598762
[rocALUTION] Time to build matrix: 0.046605
GlobalMatrix name=mat; rows=2592000; cols=2592000; nnz=12867840; prec=64bit; format=CSR(32,32)/COO; subdomains=8; host backend={CPU}; accelerator backend={None}; current=CPU
[rocALUTION] Time to copy matrix on device: 1.4e-05
munmap_chunk(): invalid pointer

Thanks, for you help.

I can reproduce it. We will look into it, thanks!

With the recent release of multi-node / multi-GPU support of the superior (un)smoothed aggregation and classic AMG, we are going to remove PairwiseAMG in one of the future releases.


[swift/main] Support change matching options in Regex refactoring

This is a cherry pick of https://github.com/apple/swift-experimental-string-processing/pull/738 to swift/main

@swift-ci please test


Feat search empty query

Before submitting a pull request, please make sure you have at least performed the following:

[ ] read and followed the CONTRIBUTING.md guide.
[ ] linted, built and tested the changes locally.
[ ] added/updated any applicable API documentation.
[ ] added/updated any applicable demos.

Hey, thank you for the PR! Something has gone wrong though, it's including lots of locale files that shouldn't be there - could you check that out please?
Could you also write a line about what exactly this PR is setting out to achieve, and why?
Thanks!

sorry @edcarroll for the bad formatted PR. It's better now :)
LINKED TO https://github.com/ovh/cds/pull/2421


Cant open tuneful app

Hi I have this issue now where I can't open the tuneful app or access the app settings. When I open from applications folder nothing happens, its no longer in the menu bar and I also disabled the mini player. The only instance where I can tell its still running is the notch animation when I switch songs in Spotify and it also keeps force restarting Spotify every time I quit the app

Hi, what version of Tuneful are you using?

It’s the latest version, I’ve also tried reinstalling it but same issue so I suspect maybe it’s something I’ve toggled in the settings? But I can’t get into the settings anymore to check

Try removing Tuneful using Pearcleaner and reinstalling, this will delete saved settings as well (.plist file)

hello I just tried doing that and once I reinstalled tuneful and opened it, it just automatically reopened Spotify and then went back to the same issue where it keeps restarting Spotify when I quit Spotify. I then tried uninstalling Spotify altogether but when I now try to open up Tuneful nothing happens. I just can't seem to get back into the tuneful settings menu.... really struggling to figure it out

+1 to both issues. I'm running version 1.7.1 on MacOS Sonoma 14.7.1

Launching immediately crashes the app, I've never used it with Apple Music but the frozen UI shows Apple Music related text. I also have https://github.com/tombonez/noTunes installed, so don't know whether they are colliding. (it's an app that prevents applemusic itunes from loading)
Quitting Spotify immediately restarts Spotify until Tuneful is force killed through Activity Monitor

hello I wanted to let you know the issue seems to be fixed now after I downloaded the zip file V0.9.0 that you linked in issue #140. I'm now able to access the Tuneful settings again, and Spotify doesn't restart automatically when I quit it anymore so all fixed, thank you!

hello I wanted to let you know the issue seems to be fixed now after I downloaded the zip file V0.9.0 that you linked in issue #140. I'm now able to access the Tuneful settings again, and Spotify doesn't restart automatically when I quit it anymore so all fixed, thank you!

I went to #140, and I couldn't find any zip file V0.9.0. I am also experiencing this issue whenever I try to quit Spotify, it just keeps restarting.


NIFI-7420 HandleHttpRequest puts form data content into attributes

This PR removes the http.param attribute. It contained both the query parameters already captured in http.query.param and the multipart form data names and values, which are captured in the part data, and could be very very large.
Removing the attribute may be a big deal, but since any form data can be large, putting in as an attribute is wrong and duplicates with the other attribute.
When you filter the part data out, all that is left is the query params, which are also already captured, so I just got rid of the attribute.
I also added a WritesAttribute for http.query.param which was missing.
If it helps, http.param was NOT documented anyways.
Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
Enables X functionality; fixes bug NIFI-YYYY.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

[x] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[-] Have you written or updated unit tests to verify your changes?
[-] Have you verified that the full build is successful on both JDK 8 and JDK 11?
[-] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[-] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[-] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[-] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[-] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

This change is

@markap14 this is your patch of ground from the looks of it.

Thanks @ottobackwards I will take a look. I will need to also make sure to update the Migration Guidance.

Thanks @ottobackwards. Change looks good. +1 merged to master and updated Migration Guidance to reflect the change.

awesome!  thanks @markap14


[webapi] Geolocation Allowed Automation

Impacted tests(approved): new 0, update 3, delete 0
Unit test platform: Crosswalk for Android 16.44.395.0
Unit test result summary: pass 3, fail 0, block 0

@Honry I have upgraded copyright following your comments

LGTM


Add Climate Year as Option Especially for Low Flows

Potentially add an option to use 4/1 - 3/31 for year specification for low flows calculations. This may require a southern hemisphere / northern hemisphere option as well. At the end of the day, it would probably require us to provide and "any-date" year specification under the hood whether it was exposed to the public API or not.
Excerpts from and email thread:

There was never any consideration of "climate year" as that would differ depending on your location around the globe. We chose water year to be consistent with the annual calculation of all USGS water statistics as published in all annual reports. That said, there were many discussions on how best to calculate and serve these statistics and although climate year was never part of the conversation, calendar year was. But it was ultimately decided to use water year for purposes of consistency.

To your point, it is true that flood frequency statistics are computed by the USGS using the water year, but we pretty much exclusively use the climatic year for low flow statistics (i.e 7Q2, 7Q10) for all of the U.S. (applicable to all of the northern hemisphere). We would do the inverse for both flood and low flow stats at locations south of the equator.
I haven't been able to find an instance in the USGS where climatic year was not used for n-day low flow calculations, which are different than other daily mean statistics. Here is a reference to the most recent TWRI (1972) I can find that establishes this as precedent: twri_4-B1_a.pdf Most current low flow reports do, or should, reference this TWRI.

Done in #187


Exception while calling your likelihood function

Hi, can you please assist me with this error:
processing all 4 sources with 1 cpus
Filter set contains 23 bands
Model sets contains 18 bands
Fitting sources from catalog:  /idia/users/thando/AGNfitter/data/cosmos.txt

Sourceline:  0
Sourcename:  119920
......................................................
model parameters ('tau', 'age', 'Nh', 'irlum', 'SB', 'BB', 'GA', 'TO', 'EBVbbb', 'EBVgal')
minimum values (0.0, 5.0, 21.0, 7.0, 0.0, 0.0, 0.0, 0.0, -0.1, -0.1)
maximum values (15, 9.976882609374064, 25, 15, 10.0, 10.0, 10.0, 10.0, 1.0, 1.0)
......................................................
100 walkers
Running burn-in nr. 0 with 4000 steps
emcee: Exception while calling your likelihood function:
exception:
Traceback (most recent call last):
File "/idia/users/thando/AGNfitter/emcee/ensemble.py", line 465, in call
return self.f(x, *self.args)
File "/idia/users/thando/AGNfitter/functions/PARAMETERSPACE_AGNfitter.py", line 124, in ln_probab
posterior = lnp + ln_likelihood(data.nus,data.fluxes,data.fluxerrs, data.z, y_model)
File "/idia/users/thando/AGNfitter/functions/PARAMETERSPACE_AGNfitter.py", line 97, in ln_likelihood
resid = [(y[i] - y_model[i])/ysigma[i] for i in x_valid]
IndexError: index 18 is out of bounds for axis 0 with size 18
Traceback (most recent call last):
File "./RUN_AGNfitter_multi.py", line 264, in
RUN_AGNfitter_multiprocessing(args.ncpu, data_ALL, Modelsdict)
File "./RUN_AGNfitter_multi.py", line 203, in RUN_AGNfitter_multiprocessing
catalog_fitting = pool.map(multi_run_wrapper, itertools.izip(range(nsources), itertools.repeat(data_obj), itertools.repeat(modelsdict)))
File "/usr/lib/python2.7/multiprocessing/pool.py", line 253, in map
return self.map_async(func, iterable, chunksize).get()
File "/usr/lib/python2.7/multiprocessing/pool.py", line 572, in get
raise self._value
IndexError: index 18 is out of bounds for axis 0 with size 18

That exception means there's an error inside of your likelihood function and it's not an issue with emcee so we can't really help you with that here. It's an indexing bug in your code (the actual error message is in the middle of the traceback) so dig into that!


Builder for ARDB

Implemented Build, Install, Start, Stop methods
On implementing sandbox and test methods

Refactored at: https://github.com/threefoldtech/jumpscaleX/commit/b48bd916e19dfdad5a7fa9911256c1b47d54dbbb on  development_builder #511

I can see that (build, install, start, stop and test) works fine but sandbox after creating the flist, deploying a container with it and trying to use the binary, there was a missing libs.
./ardb-server: error while loading shared libraries: libaio.so.1: cannot open shared object file: No such file or directory

should be fixed at: https://github.com/threefoldtech/jumpscaleX/commit/16653d7ad18ecf40bc1ae5cb4367aedc17b09b0d

branch: development_builder
commit: d9384cdc8c92cdce3ebecc2ed042df5ec29dddbd
It works fine now
Verified


added portfolio section

@vinayr please review this PR

Looks great. Do you think mentioning technologies look better? For example

e-commerce site in RoR.....
purchase automation in Node.js.....

Oh and section name "Portfolio" is missing.

It would be great if portfolio section comes before team members section. Just my opinion.


Support for Litex VexRiscV

Add initial support for Litex with softcore CPU VexRiscV SoC LiteX's website, device drivers such as GPIO/I2C/SPI are missing.
Note that Litex vexriscv has a rom bootloader integrated in fpga gateware, it load image from tftp/flash to on board ddr3.
The ostest passed. Basic nsh commands such as uname/ps/free/sleep work fine.Tested on Digilent ARTY_A7 board.

@aenrbes Nice!
Since this is a new contribution (all new files) the licences needs to be the Apache one (@Ouss4 is there a template or instructions?) and an the contributor will need to submit an ICLA https://www.apache.org/licenses/icla.pdf

A template for the Apache license?
Here is one https://github.com/apache/incubator-nuttx/blob/master/sched/sched/sched_getcpu.c
The LICENSE file also has an example.

@Ouss4 Thank you, does this means I need to change all submitted files like that templates does？

@Ouss4 do we have a Github PR/Issue template (and access to it) we can add all this info to?

@aenrbs New files need to have an Apache license. Kconfig, README and auto generated files like defconfig don't need a license.
Note that the license holder in all of this PRs files is Gregory Nutt. Gregory Nutt has already submitted an ICLA and gave his approval to change his license header.
@davids5  As of now, we don't. Some has adopted their own templates when submitting PRs.
We may want to add Github's templates for PRs/Issues. Maybe we bring this to the dev list for a discussion on what should be there?

The required form, the "teplate", is in the teplate to the coding standard.

Please refer to [1] which contains the correct text.

https://www.apache.org/legal/src-headers.html#headers

@Ouss4 - Thank you for the direct links!

We may want to add Github's templates for PRs/Issues. Maybe we bring this to the dev list for a discussion on what should be there?

@Ouss4 - email sent.

@justinmclean - Does you answer imply that the information given was incorrect or the contributor has it wrong or were you just giving an alternate source?

I think the PR looks good and is ready to merge. Let's give some time for anyone that wants to add any review.
When merging, I'd like to squash the 5 commits into one.
I'll not bring the PR locally and do the squashing manually, I'll squash from Github.


refactor: merge source map, speed up generation by 800%

The impl in crate merge-source-map is too complicated, which search too
many times on irrelevant soureces. Just refactor it with a hash map to determinate which source should be searched accurately.
When build big project (turing internal)
Before:

After:

Summary by CodeRabbit

新功能

简化了项目的依赖，移除了对merge-source-map包的依赖，可能提高了项目的整体性能和可维护性。
更新了源映射处理逻辑，增强了源映射合并功能，提高了处理的鲁棒性。

修复

修正了源映射生成过程中的逻辑，提高了代码的清晰度和效率。

@jiesia  哈哈


ENH: interpolate: Fitpack gen knots

Reference issue

Partially addresses https://github.com/scipy/scipy/issues/2579, is related to https://github.com/scipy/scipy/pull/19753
What does this implement/fix?

Add a generator which constructs knot vectors of increasing length for spline fitting. The core logic replicates that of FITPACK and the code closely follows the Fortran source.
The use of a generator was suggested in https://github.com/scipy/scipy/issues/2579 as alternative to FITPACK's black box routine (see the issue for detailed critique of the existing API).
This PR is a bit lower level: it generates knot vectors only, not smoothing splines. This way, we decouple the knot selection (this PR) from spline construction, and power users can mix and match various strategies for constructing the spline itself given knots (currently, LSQUnivariateSpline, make_lsq_spline, splrep with explicit t array).
One other argument for exposing a generator is that it steps around task={-1, 0, 1} arguments completely (https://docs.scipy.org/doc/scipy/reference/generated/scipy.interpolate.splrep.html).
The generator has two stopping conditions:

via the smoothing factor s, or
via the maximum number of knots, nest (the name follows that of FITPACK, maybe worth renaming if  user-facing).

The latter is available in the Fortran FITPACK, but effectively disabled in the Fortran-to-python glue layer: https://github.com/scipy/scipy/blob/main/scipy/interpolate/src/fitpack.pyf#L277 or https://github.com/scipy/scipy/blob/main/scipy/interpolate/src/fitpack.pyf#L310.
So in this PR we allow it as an optional knob for power users.
While at it, there is a small enhancement to make_interp_spline for degree k=4: previously it  raised a ValueError for even degrees and k=2 was special-cased. This PR generalizes the special case to all even degrees. I suspect this is not going to be widely used, because the ValueError did not receive any user requests.  However FITPACK allows even degrees, so it's simpler and more consistent to allow it, too.
Additional information

Together with https://github.com/scipy/scipy/pull/19753, this PR is a part of a project to replicate FITPACK (cf https://github.com/scipy/scipy/issues/18566).
The ultimate goal is to replicate the FITPACK monolith to make it more readable, more maintainable and more amendable to enhancements. The project itself is loosely tracked in https://github.com/users/ev-br/projects/1
The code here follows the Fortran source somewhat closely, with the original being
https://github.com/scipy/scipy/blob/maintenance/1.11.x/scipy/interpolate/fitpack/fpcurf.f

The code should be considered prototype quality. It's reasonably easy to move it to a compiled extension if needs be.
The next item on the TODO list is to replicate the spline construction itself (Dierckx uses a bespoke procedure, of course). Am making this a separate PR to keep the PR sizes under control.
 Whatever was visible in the profile is now in C. The spline construction is in https://github.com/scipy/scipy/pull/19970

The three-PR attempt to simplify reviewing obviously did not work, thus closing in favor of https://github.com/scipy/scipy/pull/19970.


Reset amount form on submission

This PR resets the amount form after successful submission

Looks good, I just added the type instead of any

Looks good, I just added the type instead of any
Thanks


[fix] Fix double vv typo in banner splash

Description of changes
The current server CLI splash screen has two v characters as prefix to the version.
###################################################################
#  _    _       _ _            _____      _        _              #
# | |  | |     (_) |          / ____|    | |      | |             #
# | |  | |_ __  _| |_ _   _  | |     __ _| |_ __ _| | ___   __ _  #
# | |  | | '_ \| | __| | | | | |    / _` | __/ _` | |/ _ \ / _` | #
# | |__| | | | | | |_| |_| | | |___| (_| | || (_| | | (_) | (_| | #
#  \____/|_| |_|_|\__|\__, |  \_____\__,_|\__\__,_|_|\___/ \__, | #
#                      __/ |                                __/ | #
#                     |___/              vv0.1.0-SNAPSHOT  |___/  #
###################################################################

                                         ^^
                                         ||

This PR removes the duplication.

Thank you for fixing this @rmoff
This was my mistake :P

Thanks for fixing @rmoff!
Thanks for the ASCII art @tdas - makes me happy every time I fire up a server.


[Suggestion] Support multiple items for auto-on item

So... I read from the changelog that the auto-on item is not plural form (also I tried to make a list which just crashes the game), so I guess it's not possible right now?
It would be really great and convenient to have this feature since there are too many light sources in the game.

Thanks for the suggestion!
Yeah, I do want to make it a list, but that requires some extra work. I just wanted to push the feature out there, to get some feedback/testing (just like your feedback, thanks again!) before polishing/finishing the feature entirely.
So, TL;DR: Yes, I plan on making it a kind of list! Just a little bit more work to do :smiley:

I'd also find this feature very useful!

I've implemented this in Lighty v3.0.0-beta.4, with the new default items being the torches and lanterns of Minecraft.
Because I've kept the changes backwards compatible, the new defaults won't be applied to existing configs.
To change it, do the following:
edit lighty/base.config and change the line with lighty.auto_on.item to say the following:
lighty.auto_on.item=minecraft:torch minecraft:soul_torch minecraft:lantern minecraft:soul_lantern

The syntax is lighty.auto_on.item=modid:item modid:item modid:item, so after the equals sign one ResourceLocation followed by exactly one space character followed by another ResourceLocation. Repeat as often as you need. There shouldn't be a trailing space character at the end or after the =, this will break the config format.
I plan on making some kind of wiki, documenting this and any other config options that aren't configurable inside of the game, but I hope that for now this is sufficient enough information on how to configure this feature.
Thanks for the patience, feel free to reopen this issue if there are any more questions regarding the config format. If there are issues with the feature in general, please open a new issue.
Thanks and have fun!


GitHub release

Would be nice to have a GitHub release of InfiniteViewPager

Tagged v1.0.0.

Cool! Now works on jitpack.io as well https://jitpack.io/#antonyt/InfiniteViewPager/v1.0.0


🐛 [firebase_analytics] "(other)" event name in console

Bug report
Describe the bug
I am getting weird event named "(other)" in my firebase analytics events console. All event names sent from device has to begin with a letter, so it means that I cannot be sending it from my code.

Additional context
App exists on stores for quite some time and the event started showing recently with newest update (which didn't change anything connected with analytics)

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
[✓] Flutter (Channel stable, 3.16.2, on macOS 14.0 23A344 darwin-arm64, locale en-PL)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.0)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2023.2)
[✓] Connected device (4 available)
[✓] Network resources

• No issues found!

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
Dart SDK 3.2.2
Flutter SDK 3.16.2

dependencies:
- app_tracking_transparency 2.0.4 [flutter]
- applovin_max 3.4.1 [flutter plugin_platform_interface]
- audioplayers 5.2.0 [audioplayers_android audioplayers_darwin audioplayers_linux audioplayers_platform_interface audioplayers_web audioplayers_windows file flutter http meta path_provider synchronized uuid]
- auto_route 7.4.0 [flutter path collection meta]
- auto_size_text 3.0.0 [flutter]
- bloc_concurrency 0.2.2 [bloc stream_transform]
- cached_network_image 3.3.0 [cached_network_image_platform_interface cached_network_image_web flutter flutter_cache_manager octo_image]
- carousel_slider 4.1.1 [flutter]
- cloud_firestore 4.14.0 [cloud_firestore_platform_interface cloud_firestore_web collection firebase_core firebase_core_platform_interface flutter meta]
- cloud_firestore_odm 1.0.0-dev.82 [cloud_firestore flutter json_annotation meta]
- cloud_functions 4.6.0 [cloud_functions_platform_interface cloud_functions_web firebase_core firebase_core_platform_interface flutter]
- collection 1.18.0
- connectivity_plus 5.0.2 [flutter flutter_web_plugins connectivity_plus_platform_interface js meta nm]
- country_picker 2.0.20 [collection flutter]
- crypto 3.0.3 [typed_data]
- cupertino_icons 1.0.5
- desktop_webview_auth 0.0.14 [crypto flutter http flutter_web_plugins plugin_platform_interface]
- device_info_plus 9.0.2 [device_info_plus_platform_interface ffi file flutter flutter_web_plugins meta win32 win32_registry]
- dio 4.0.6 [http_parser path]
- embrace 1.5.0 [embrace_android embrace_ios embrace_platform_interface flutter http]
- equatable 2.0.5 [collection meta]
- facebook_audience_network 1.0.1 [flutter meta characters]
- firebase_analytics 10.8.0 [firebase_analytics_platform_interface firebase_analytics_web firebase_core firebase_core_platform_interface flutter]
- firebase_app_check 0.2.1+8 [firebase_app_check_platform_interface firebase_app_check_web firebase_core firebase_core_platform_interface flutter]
- firebase_auth 4.16.0 [firebase_auth_platform_interface firebase_auth_web firebase_core firebase_core_platform_interface flutter meta]
- firebase_core 2.24.2 [firebase_core_platform_interface firebase_core_web flutter meta]
- firebase_crashlytics 3.4.9 [firebase_core firebase_core_platform_interface firebase_crashlytics_platform_interface flutter stack_trace]
- firebase_messaging 14.7.10 [firebase_core firebase_core_platform_interface firebase_messaging_platform_interface firebase_messaging_web flutter meta]
- firebase_remote_config 4.3.8 [firebase_core firebase_core_platform_interface firebase_remote_config_platform_interface firebase_remote_config_web flutter]
- firebase_storage 11.6.0 [firebase_core firebase_core_platform_interface firebase_storage_platform_interface firebase_storage_web flutter]
- flutter 0.0.0 [characters collection material_color_utilities meta vector_math web sky_engine]
- flutter_bloc 8.1.3 [bloc flutter provider]
- flutter_cache_manager 3.3.1 [clock collection file flutter http path path_provider rxdart sqflite uuid]
- flutter_facebook_app_links 3.0.1+7 [flutter]
- flutter_facebook_auth 6.0.3 [flutter flutter_facebook_auth_platform_interface flutter_facebook_auth_web facebook_auth_desktop]
- flutter_flavor 3.1.1 [flutter]
- flutter_launcher_icons 0.12.0 [args checked_yaml cli_util image json_annotation path yaml]
- flutter_localizations 0.0.0 [flutter intl characters clock collection material_color_utilities meta path vector_math web]
- flutter_native_splash 2.2.19 [args flutter flutter_web_plugins js html image meta path universal_io xml yaml]
- flutter_svg 2.0.2 [flutter vector_graphics vector_graphics_codec vector_graphics_compiler]
- fluttertoast 8.1.2 [flutter flutter_web_plugins]
- get_it 7.6.0 [async collection]
- google_sign_in 6.2.1 [flutter google_sign_in_android google_sign_in_ios google_sign_in_platform_interface google_sign_in_web]
- hive 2.2.3 [meta crypto]
- hive_flutter 1.1.0 [flutter hive path_provider path]
- image 4.1.3 [archive meta xml]
- image_size_getter 2.1.2 [collection hashcodes]
- in_app_review 2.0.6 [flutter in_app_review_platform_interface]
- injectable 2.1.2 [get_it]
- intl 0.18.1 [clock meta path]
- json_annotation 4.8.1 [meta]
- logger 1.1.0
- mockito 5.4.2 [analyzer build code_builder collection dart_style matcher meta path source_gen test_api]
- native_exif 0.5.0 [flutter intl]
- native_shared_preferences 2.0.7 [flutter meta shared_preferences shared_preferences_platform_interface shared_preferences_linux shared_preferences_macos shared_preferences_web shared_preferences_windows file]
- ntp 2.0.0
- package_info_plus 5.0.1 [ffi flutter flutter_web_plugins http meta path package_info_plus_platform_interface web win32]
- path 1.8.3
- path_provider 2.0.15 [flutter path_provider_android path_provider_foundation path_provider_linux path_provider_platform_interface path_provider_windows]
- rive 0.12.4 [collection flutter flutter_web_plugins http meta plugin_platform_interface rive_common]
- rxdart 0.27.7
- share_plus 7.2.1 [cross_file meta mime flutter flutter_web_plugins share_plus_platform_interface file url_launcher_web url_launcher_windows url_launcher_linux url_launcher_platform_interface ffi win32]
- shared_preferences 2.0.15 [flutter shared_preferences_android shared_preferences_ios shared_preferences_linux shared_preferences_macos shared_preferences_platform_interface shared_preferences_web shared_preferences_windows]
- shimmer 2.0.0 [flutter]
- sign_in_with_apple 5.0.0 [flutter meta sign_in_with_apple_platform_interface sign_in_with_apple_web]
- singular_flutter_sdk 1.3.2 [flutter]
- synchronized 3.0.1
- system_info_plus 0.0.5 [flutter]
- tutorial_coach_mark 1.2.8 [flutter flutter_lints]
- uni_links 0.5.1 [flutter uni_links_platform_interface uni_links_web]
- url_launcher 6.1.6 [flutter url_launcher_android url_launcher_ios url_launcher_linux url_launcher_macos url_launcher_platform_interface url_launcher_web url_launcher_windows]
- user_messaging_platform 1.3.0 [flutter collection meta]
- version 3.0.2
- video_player 2.4.7 [flutter html video_player_android video_player_avfoundation video_player_platform_interface video_player_web]
- webview_flutter 3.0.4 [flutter webview_flutter_android webview_flutter_platform_interface webview_flutter_wkwebview]

dev dependencies:
- auto_route_generator 7.1.1 [build source_gen analyzer path build_runner code_builder dart_style xml args glob auto_route]
- build_runner 2.4.4 [analyzer args async build build_config build_daemon build_resolvers build_runner_core code_builder collection crypto dart_style frontend_server_client glob graphs http_multi_server io js logging meta mime package_config path pool pub_semver pubspec_parse shelf shelf_web_socket stack_trace stream_transform timing watcher web_socket_channel yaml]
- cloud_firestore_odm_generator 1.0.0-dev.82 [analyzer build build_config cloud_firestore_odm collection freezed_annotation graphs json_annotation meta recase source_gen source_helper]
- flutter_gen_runner 5.3.1 [flutter_gen_core build collection crypto glob path]
- flutter_lints 2.0.1 [lints]
- flutter_test 0.0.0 [flutter test_api matcher path fake_async clock stack_trace vector_math async boolean_selector characters collection material_color_utilities meta source_span stream_channel string_scanner term_glyph web]
- hive_generator 2.0.1 [build source_gen hive analyzer source_helper]
- injectable_generator 2.1.6 [build source_gen path glob analyzer code_builder dart_style injectable collection recase]
- json_serializable 6.7.1 [analyzer async build build_config collection json_annotation meta path pub_semver pubspec_parse source_gen source_helper]

transitive dependencies:
- _fe_analyzer_shared 61.0.0 [meta]
- _flutterfire_internals 1.3.16 [collection firebase_core firebase_core_platform_interface flutter meta]
- analyzer 5.13.0 [_fe_analyzer_shared collection convert crypto glob meta package_config path pub_semver source_span watcher yaml]
- archive 3.4.6 [crypto path pointycastle]
- args 2.4.1
- async 2.11.0 [collection meta]
- audioplayers_android 4.0.2 [audioplayers_platform_interface flutter]
- audioplayers_darwin 5.0.2 [audioplayers_platform_interface flutter]
- audioplayers_linux 3.1.0 [audioplayers_platform_interface flutter]
- audioplayers_platform_interface 6.1.0 [flutter meta plugin_platform_interface]
- audioplayers_web 4.1.0 [audioplayers_platform_interface flutter flutter_web_plugins js]
- audioplayers_windows 3.1.0 [audioplayers_platform_interface flutter]
- bloc 8.1.2 [meta]
- boolean_selector 2.1.1 [source_span string_scanner]
- build 2.4.0 [analyzer async convert crypto glob logging meta package_config path]
- build_config 1.1.1 [checked_yaml json_annotation path pubspec_parse yaml]
- build_daemon 4.0.0 [built_collection built_value http_multi_server logging path pool shelf shelf_web_socket stream_transform watcher web_socket_channel]
- build_resolvers 2.2.0 [analyzer async build collection crypto graphs logging path package_config pool pub_semver stream_transform yaml]
- build_runner_core 7.2.9 [async build build_config build_resolvers collection convert crypto glob graphs json_annotation logging meta package_config path pool timing watcher yaml]
- build_version 2.1.1 [build build_config pubspec_parse]
- built_collection 5.1.1
- built_value 8.6.0 [built_collection collection fixnum meta]
- cached_network_image_platform_interface 3.0.0 [flutter flutter_cache_manager]
- cached_network_image_web 1.1.0 [cached_network_image_platform_interface flutter flutter_cache_manager]
- characters 1.3.0
- checked_yaml 2.0.3 [json_annotation source_span yaml]
- cli_util 0.3.5 [meta path]
- clock 1.1.1
- cloud_firestore_platform_interface 6.1.0 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- cloud_firestore_web 3.9.0 [_flutterfire_internals cloud_firestore_platform_interface collection firebase_core firebase_core_web flutter flutter_web_plugins js]
- cloud_functions_platform_interface 5.5.11 [firebase_core flutter meta plugin_platform_interface]
- cloud_functions_web 4.6.11 [cloud_functions_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins js]
- code_builder 4.5.0 [built_collection built_value collection matcher meta]
- color 3.0.0
- connectivity_plus_platform_interface 1.2.4 [flutter meta plugin_platform_interface]
- convert 3.1.1 [typed_data]
- cross_file 0.3.3+6 [js meta]
- csslib 0.17.3 [source_span]
- dart_style 2.3.1 [analyzer args path pub_semver source_span]
- dartx 1.1.0 [characters collection crypto meta path time]
- dbus 0.7.8 [args ffi meta xml]
- device_info_plus_platform_interface 7.0.0 [flutter meta plugin_platform_interface]
- embrace_android 1.5.0 [embrace_platform_interface flutter]
- embrace_ios 1.5.0 [embrace_platform_interface flutter]
- embrace_platform_interface 1.5.0 [build_runner build_version flutter platform plugin_platform_interface]
- facebook_auth_desktop 1.0.2 [flutter http flutter_secure_storage flutter_facebook_auth_platform_interface]
- fake_async 1.3.1 [clock collection]
- ffi 2.0.2
- file 6.1.4 [meta path]
- firebase_analytics_platform_interface 3.9.0 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_analytics_web 0.5.5+12 [_flutterfire_internals firebase_analytics_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins js]
- firebase_app_check_platform_interface 0.1.0+10 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_app_check_web 0.1.0+10 [_flutterfire_internals firebase_app_check_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins js]
- firebase_auth_platform_interface 7.0.9 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- firebase_auth_web 5.8.13 [firebase_auth_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins http_parser js meta]
- firebase_core_platform_interface 5.0.0 [collection flutter flutter_test meta plugin_platform_interface]
- firebase_core_web 2.10.0 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
- firebase_crashlytics_platform_interface 3.6.16 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_platform_interface 4.5.18 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_web 3.5.18 [_flutterfire_internals firebase_core firebase_core_web firebase_messaging_platform_interface flutter flutter_web_plugins js meta]
- firebase_remote_config_platform_interface 1.4.16 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_remote_config_web 1.4.16 [firebase_core firebase_core_web firebase_remote_config_platform_interface flutter flutter_web_plugins js]
- firebase_storage_platform_interface 5.1.3 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- firebase_storage_web 3.6.17 [_flutterfire_internals async firebase_core firebase_core_web firebase_storage_platform_interface flutter flutter_web_plugins http js meta]
- fixnum 1.1.0
- flutter_facebook_auth_platform_interface 5.0.0 [flutter plugin_platform_interface]
- flutter_facebook_auth_web 5.0.0 [flutter flutter_web_plugins js flutter_facebook_auth_platform_interface]
- flutter_gen_core 5.3.1 [path yaml mime xml dartx color collection json_annotation glob dart_style analyzer args pub_semver source_span]
- flutter_secure_storage 9.0.0 [flutter flutter_secure_storage_linux flutter_secure_storage_macos flutter_secure_storage_platform_interface flutter_secure_storage_web flutter_secure_storage_windows meta]
- flutter_secure_storage_linux 1.1.3 [flutter flutter_secure_storage_platform_interface]
- flutter_secure_storage_macos 3.0.0 [flutter flutter_secure_storage_platform_interface]
- flutter_secure_storage_platform_interface 1.0.1 [flutter plugin_platform_interface]
- flutter_secure_storage_web 1.1.1 [flutter flutter_secure_storage_platform_interface flutter_web_plugins js]
- flutter_secure_storage_windows 3.0.0 [ffi flutter flutter_secure_storage_platform_interface path path_provider win32]
- flutter_web_plugins 0.0.0 [flutter characters collection material_color_utilities meta vector_math web]
- freezed_annotation 2.2.0 [collection json_annotation meta]
- frontend_server_client 3.2.0 [async path]
- glob 2.1.2 [async collection file path string_scanner]
- google_identity_services_web 0.3.0+2 [meta web]
- google_sign_in_android 6.1.14 [flutter google_sign_in_platform_interface]
- google_sign_in_ios 5.7.3 [flutter google_sign_in_platform_interface]
- google_sign_in_platform_interface 2.4.1 [flutter plugin_platform_interface quiver]
- google_sign_in_web 0.12.3+2 [flutter flutter_web_plugins google_identity_services_web google_sign_in_platform_interface http web]
- graphs 2.2.0 [collection]
- hashcodes 2.0.0
- html 0.15.3 [csslib source_span]
- http 1.1.2 [async http_parser meta web]
- http_multi_server 3.2.1 [async]
- http_parser 4.0.2 [collection source_span string_scanner typed_data]
- in_app_review_platform_interface 2.0.4 [flutter url_launcher plugin_platform_interface platform]
- io 1.0.4 [meta path string_scanner]
- js 0.6.7 [meta]
- lints 2.1.0
- logging 1.2.0
- matcher 0.12.16 [async meta stack_trace term_glyph test_api]
- material_color_utilities 0.5.0 [collection]
- meta 1.10.0
- mime 1.0.4
- nested 1.0.0 [flutter]
- nm 0.5.0 [dbus]
- octo_image 2.0.0 [flutter]
- package_config 2.1.0 [path]
- package_info_plus_platform_interface 2.0.1 [flutter meta plugin_platform_interface]
- path_parsing 1.0.1 [vector_math meta]
- path_provider_android 2.0.27 [flutter path_provider_platform_interface]
- path_provider_foundation 2.2.3 [flutter path_provider_platform_interface]
- path_provider_linux 2.1.11 [ffi flutter path path_provider_platform_interface xdg_directories]
- path_provider_platform_interface 2.0.6 [flutter platform plugin_platform_interface]
- path_provider_windows 2.1.7 [ffi flutter path path_provider_platform_interface win32]
- petitparser 5.4.0 [meta]
- platform 3.1.0
- plugin_platform_interface 2.1.4 [meta]
- pointycastle 3.7.3 [collection convert js]
- pool 1.5.1 [async stack_trace]
- process 4.2.4 [file path platform]
- provider 6.0.5 [collection flutter nested]
- pub_semver 2.1.4 [collection meta]
- pubspec_parse 1.2.3 [checked_yaml collection json_annotation pub_semver yaml]
- quiver 3.2.1 [matcher]
- recase 4.1.0
- rive_common 0.2.8 [collection ffi flutter flutter_web_plugins graphs http meta plugin_platform_interface]
- share_plus_platform_interface 3.3.1 [cross_file flutter meta mime plugin_platform_interface path_provider uuid]
- shared_preferences_android 2.1.4 [flutter shared_preferences_platform_interface]
- shared_preferences_ios 2.1.1 [flutter shared_preferences_platform_interface]
- shared_preferences_linux 2.2.0 [file flutter path path_provider_linux path_provider_platform_interface shared_preferences_platform_interface]
- shared_preferences_macos 2.0.5 [flutter shared_preferences_platform_interface]
- shared_preferences_platform_interface 2.3.0 [flutter plugin_platform_interface]
- shared_preferences_web 2.1.0 [flutter flutter_web_plugins shared_preferences_platform_interface]
- shared_preferences_windows 2.2.0 [file flutter path path_provider_platform_interface path_provider_windows shared_preferences_platform_interface]
- shelf 1.4.1 [async collection http_parser path stack_trace stream_channel]
- shelf_web_socket 1.0.4 [shelf stream_channel web_socket_channel]
- sign_in_with_apple_platform_interface 1.0.0 [flutter plugin_platform_interface meta]
- sign_in_with_apple_web 1.0.1 [flutter flutter_web_plugins sign_in_with_apple_platform_interface js]
- sky_engine 0.0.99
- source_gen 1.3.2 [analyzer async build dart_style glob path source_span yaml]
- source_helper 1.3.4 [analyzer collection source_gen]
- source_span 1.10.0 [collection path term_glyph]
- sqflite 2.2.8+4 [flutter sqflite_common path]
- sqflite_common 2.4.5 [synchronized path meta]
- stack_trace 1.11.1 [path]
- stream_channel 2.1.2 [async]
- stream_transform 2.1.0
- string_scanner 1.2.0 [source_span]
- term_glyph 1.2.1
- test_api 0.6.1 [async boolean_selector collection meta source_span stack_trace stream_channel string_scanner term_glyph]
- time 2.1.3 [clock]
- timing 1.0.1 [json_annotation]
- typed_data 1.3.2 [collection]
- uni_links_platform_interface 1.0.0 [flutter plugin_platform_interface]
- uni_links_web 0.1.0 [flutter flutter_web_plugins uni_links_platform_interface]
- universal_io 2.2.0 [collection meta typed_data]
- url_launcher_android 6.0.35 [flutter url_launcher_platform_interface]
- url_launcher_ios 6.1.4 [flutter url_launcher_platform_interface]
- url_launcher_linux 3.0.5 [flutter url_launcher_platform_interface]
- url_launcher_macos 3.0.5 [flutter url_launcher_platform_interface]
- url_launcher_platform_interface 2.1.2 [flutter plugin_platform_interface]
- url_launcher_web 2.0.17 [flutter flutter_web_plugins url_launcher_platform_interface]
- url_launcher_windows 3.0.6 [flutter url_launcher_platform_interface]
- uuid 3.0.7 [crypto]
- vector_graphics 1.1.6 [flutter vector_graphics_codec]
- vector_graphics_codec 1.1.6
- vector_graphics_compiler 1.1.6 [args meta path_parsing xml vector_graphics_codec]
- vector_math 2.1.4
- video_player_android 2.4.3 [flutter video_player_platform_interface]
- video_player_avfoundation 2.4.2 [flutter video_player_platform_interface]
- video_player_platform_interface 5.1.4 [flutter plugin_platform_interface]
- video_player_web 2.0.15 [flutter flutter_web_plugins video_player_platform_interface]
- watcher 1.1.0 [async path]
- web 0.3.0
- web_socket_channel 2.4.0 [async crypto stream_channel]
- webview_flutter_android 2.10.4 [flutter webview_flutter_platform_interface]
- webview_flutter_platform_interface 1.9.5 [flutter meta plugin_platform_interface]
- webview_flutter_wkwebview 2.9.5 [flutter path webview_flutter_platform_interface]
- win32 5.0.6 [ffi]
- win32_registry 1.1.1 [ffi win32]
- xdg_directories 1.0.0 [meta path process]
- xml 6.3.0 [collection meta petitparser]
- yaml 3.1.2 [collection source_span string_scanner]

Hello, do you have some reproduction steps or reproduction sample? I don't see any (other) events in our own console

That's the problem, I can't reproduce it, I don't know where it come from

@MyisCARRY Without a way to reproduce I will not be able to help you. Could it be that some events are not given a name and the display in the analytics console changed?

I can't send empty event name, it will not be process:

E/FA      ( 8138): Name is required and can't be empty. Type: event
E/FA      ( 8138): Invalid public event name. Event will not be logged (FE)

It seems like the events aren't process yet and after 24h they disappear from the console.

Do you mean the (other) events are disappearing from the console? Maybe it was a transient issue with Analytics?

Yes, the (other) events. We still get them everyday, but after +-24 hours they disappear

Based on what you are saying, it looks like a backend issue since the events are disappearing from the console. I'll close this issue, but you should probably contact the Google Analytics support if it keeps happening: https://support.google.com/analytics/answer/9026876?hl=en


live preview works but not on all fields

Describe the bug
The live preview works on almost all of the content's fields that we're trying to update. Those fields being updated are not published.
To Reproduce
Open a content with live preview running in localhost.
Expected behavior
Live preview is updating the content in preview mode even though the updated content is not yet published.
Context (please complete the following information):

Live preview SDK version number: @contentful/live-preview": "^2.7.0"
GraphQL API

Hi @arantebw Thank you for submitting this bug report.
We would need some more detail and a reproduce able example to help you further. You can use codesandbox, codepen, or any other related tool.
Also describe which fields are not working? How to reproduce? etc...
Thank you!

We would need some more detail and a reproduce able example to help you further. You can use codesandbox, codepen, or any other related tool.

Does it mean I need to create a mock web app and contentful account?

Also describe which fields are not working? How to reproduce? etc...

As far as our use case goes, we found no specific field types that is expected not to work. For a example, a field type which contains a YouTube ID (short text) is not working while a hero section with a welcome message (short text) is working just fine.

Please just create a simple project that reproduces the issue that you are describing. This way we will have more context over what the issue is and help you further 👍

Need more context and reproducible example.


Documentation for ROSBridge Server Setup

Port over from RadiationVisualization's HololensTesting.md

Instruction of git submodule update.. init.... recursive works. Its in the README


Update final ppp

Codecov Report

Merging #336 (ab414ab) into master (5c62c33) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #336   +/-   ##
=========================================
  Coverage     83.85%   83.85%
  Complexity     1121     1121
=========================================
  Files           140      140
  Lines          2861     2861
  Branches        389      389
=========================================
  Hits           2399     2399
  Misses          384      384
  Partials         78       78

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


dev_container

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
TensorFlow version and how it was installed (source or binary):
TensorFlow-Addons version and how it was installed (source or binary):
Python version:
Is GPU used? (yes/no):
no
Describe the bug
Why tfaddons/dev_container:latest-cpu is so big(6.3GB) and has some CUDA layers and lots of apt-update layers which increase image size.
A clear and concise description of what the bug is.

Code to reproduce the issue
Create a codespace.
Other info / logs
https://hub.docker.com/layers/tfaddons/dev_container/latest-cpu/images/sha256-e97c0a51c9da13134b9e4f2a27aeee662def8e77ced84224f4dcd90e00cc18d3?context=explore
2021-11-25T06:01:15: [2021-11-25T06:01:15.292Z] failed to register layer: ApplyLayer exit status 1 stdout:  stderr: write /usr/local/lib/python3.9/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so: no space left on device
Error: Command failed: docker build -f /var/lib/docker/codespacemount/workspace/addons/.devcontainer/Dockerfile -t vsc-addons-7dc239d633fc90a0907165f6f5d2c6fb /var/lib/docker/codespacemount/workspace/addons/.devcontainer
    at A7 (/usr/lib/node_modules/@microsoft/vscode-dev-containers-cli/dist/node/devContainersCLI.js:318:7786)
    at async T7 (/usr/lib/node_modules/@microsoft/vscode-dev-containers-cli/dist/node/devContainersCLI.js:318:6090)
    at async pF (/usr/lib/node_modules/@microsoft/vscode-dev-containers-cli/dist/node/devContainersCLI.js:318:2407)
    at async o7 (/usr/lib/node_modules/@microsoft/vscode-dev-containers-cli/dist/node/devContainersCLI.js:312:10911)
    at async n3 (/usr/lib/node_modules/@microsoft/vscode-dev-containers-cli/dist/node/devContainersCLI.js:344:3255)
    at async dae (/usr/lib/node_modules/@microsoft/vscode-dev-containers-cli/dist/node/devContainersCLI.js:344:22780)
    at async fae (/usr/lib/node_modules/@microsoft/vscode-dev-containers-cli/dist/node/devContainersCLI.js:344:22376)

Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.

Yes with free/eval Codespaces the disk space Is limited but the main issues are:
https://github.com/tensorflow/addons/pull/2598#issuecomment-969821170
And
https://github.com/tensorflow/addons/pull/2515
https://discuss.tensorflow.org/t/adopting-open-source-dockerfiles-for-official-tf-nightly-ci/6050/4
/cc @seanpmorgan

IMO, codespace container should use a different image instead of devops image.

Why we need multipython in codespace?

The point is to have the same developer container as the one we are using in the CI so that we are almost on the same page when we develop TF Addons and when we automatically validate it with the CI without having too much risks to be out of sync between the two envs as It Is seems that this type of drift happens quite often, soon or later, when you have two independent envs.
But now we don't have any CPU image anymore also in the new TF Docker refactoring effort.
.devcontainer is not only about Codespaces but also about development in Vscode with dev own resources and It is why I've put some commented lines to enable GPU options but we don't have a valid upstream CPU image and custom ops TF images are unmaintaiend (see the mentioned forum thread).

Could we specific different .devcontainer for different envs? We could separate latest-cpu and latest-gpu docker image.

We could separate latest-cpu and latest-gpu docker images. If you see the image type was already an arg controlled by .devcontainer:
https://github.com/tensorflow/addons/blob/41eaa27d49025c02bfe9520d5e63e1f01a782ddf/.devcontainer/Dockerfile#L1
The problem is that the image on our (Addons) DockerHUB registry is de-facto a GPU one after https://github.com/tensorflow/addons/pull/2598#issuecomment-969821170 was merged.
I've prepared an upstream  PR to start to separate baseline (CPU) and CUDA layers:
https://github.com/tensorflow/build/pull/47
We still need to work with comments in the same single .devcontainer as Vscode/Codespace still really works with the default .devcontainer.
See more at:
https://github.com/microsoft/vscode-remote-release/issues/1165
https://github.com/microsoft/vscode-remote-release/issues/3279

TF doesn't want to accept the contribution of an intermediate CPU target based with a small refactoring of their own new receipt https://github.com/tensorflow/build/pull/47#issuecomment-981990104.
So when we are going to merge @seanpmorgan (and mine) https://github.com/tensorflow/addons/pull/2515 we still have all the CUDA layer overhead.
I will accept any suggestion but on my side I don't want to maintain multiple Dockerfile diverging receipts between the Addons devel env and the Addons CI.
/cc @yarioss

/cc @yarri-oss

Discussed this in the grooming meeting. It's certainly something we want supported for Addons, but we're not willing to build our own containers given that custom-op image is no longer supported. Lets bring this up at the next SIG build meeting to see if we can get any traction.

We discussed this in today meeting SIG BUILD meeting but It seems that https://github.com/tensorflow/build/pull/47#issuecomment-981990104 review could not go ahead.

TensorFlow Addons is transitioning to a minimal maintenance and release mode. New features will not be added to this repository. For more information, please see our public messaging on this decision:
TensorFlow Addons Wind Down
Please consider sending feature requests / contributions to other repositories in the TF community with a similar charters to TFA:
Keras
Keras-CV
Keras-NLP


Fix daily scheduledjdbc pipeline failure

Description
Our daily scheduledpipeline java - jdbc contains stage : PublishDocsToNightlyBranch

this stage will check the generated javadoc jar files.
Now the stage will fail because the generated file azure-identity-providers-core-1.0.0-alpha.20221104.1-javadoc.jar doesn't contains completed java doc information.

This PR is aiming to add a element-list file to azure-identity-providers-core generating javadoc.jar to pass the PublishDocsToNightlyBranch stage.

/azp run java - jdbc

/azp run java - jdbc

API change check
API changes are not detected in this pull request.

Closing this

This PR is for warnnings not errors;
We are going to combine our azure-identity-* libraries into one module, after that ,this issue will be gone.


De facto way of dynamically changing data in dagre graph

Hello,
thanks for this library, it is very nice.
I'm trying to implement G6 into my react application where the nodes that are contained in the graph will be updated by user interaction with the app.
I got it working like this
function App() {
  const ref = useRef();
  const [data, setData] = useState(data_import);
  const [graph, setGraph] = useState();
  useEffect(() => {
    const graf = new G6.Graph({
      container: ref.current,
      width: 1000,
      height: 600,
      layout: {
        type: "dagre",
        rankdir: "TB", // The center of the graph by default

        nodesep: 10,
        ranksep: 20,
        controlPoints: true,
      },
    });
    graf.data(data);
    graf.render();
    setGraph(graf);
  }, []);
  useEffect(() => {
    if (graph) graph.changeData(data);
  }, [data]);

  const handleClick = () => {
    setData({
      ...data,
      nodes: [...data.nodes, { id: "node7", label: "node7" }],
    });
    console.log(graph);
  };
  return (

        <button onClick={handleClick}>Click me</button>

  );
}

export default App;

However, I feel like this is quite the hacky solution and am therefore wondering if there is any better way of doing this?

If you are adding a few items into the graph, call graph.addItem instead. For updating some items, call graph.updateItem.
graph.changeData is suitable for changing the whole dataset.

If you are adding a few items into the graph, call graph.addItem instead. For updating some items, call graph.updateItem.
graph.changeData is suitable for changing the whole dataset.

The question here was rather the way the graph is initialized. It seems suboptimal

The question here was rather the way the graph is initialized. It seems suboptimal

Why do you think it is a hacky solution?

Why do you think it is a hacky solution?


Use the editor-defined Android keystore for both debug and release mode

This paves the work for making release mode the default export option, since it performs better and results in smaller binaries.
The "debug" keystore option was renamed to "default" in the Editor Settings. People using older configuration files will have to update their editor settings to follow the rename.
The OpenJDK-related messages now specify that version 8 is required (and that more recent versions won't work).
I haven't been able to build for Android lately, so I'd like to have someone test this before it can be merged (just in case). cc @pouleyKetchoupp
PS: This change might be worth cherry-picking to the 3.2 branch as the keystore choice logic is a common point of confusion among newer Godot users.

cc. @m4gr3d in case he wants to share extra feedback.

This paves the work for making release mode the default export option, since it performs better and results in smaller binaries.
The "debug" keystore option was renamed to "default" in the Editor Settings. People using older configuration files will have to update their editor settings to follow the rename.
The OpenJDK-related messages now specify that version 8 is required (and that more recent versions won't work).
I haven't been able to build for Android lately, so I'd like to have someone test this before it can be merged (just in case). cc @pouleyKetchoupp
PS: This change might be worth cherry-picking to the 3.2 branch as the keystore choice logic is a common point of confusion among newer Godot users.

@Calinou I'm not sure I follow the reason for the change so a clarification may help, but what I'm seeing so far doesn't seem like a good idea for the following reasons:

Exporting with debug builds is useful for development of the project for obvious reasons. For most professional developments, a release build is not generated until near completion of the project. In Android on particular, certain logcat messages are only available in debug builds.
With this change (and related changes) it seems we're optimizing for demo purposes at the expense of the development process. For example, @pouleyKetchoupp mentioned, this change would affect the quick launch button, which would break the development flow for several developers, myself included.
Is this solving an actual issue? I don't see any attached to this PR or PR #39208. Especially, since getting access to a release build is rather trivial when going through the full export process.

In Android development, you never want to use a debug keystore for release builds. Even if it's inconvenient, we should force the use to go through the process of generating a keystore specifically for release build. This is a big DO NOT DO` in Android development, and we should not encourage users by making that the default.

As I mentioned, it may be that I misunderstood the reasons for this PR. If so, I'll be glad to corrected, but as it stands, this PR and PR #39208 are problematic.

Note: The points below would be better discussed in #39208, since this PR doesn't change the default export mode.

Is this solving an actual issue? I don't see any attached to this PR or PR #39208. Especially, since getting access to a release build is rather trivial when going through the full export process.

Try searching around on Reddit or the Godot Q&A, and you'll find many people who ran into performance issues or unexpectedly large binaries because they accidentally exported a debug build. I think exporting in release mode by default is generally what's expected, especially by casual users. A lot of people I know will never bother with logcat, so I'd say exporting a debug build is the exception at this point. I've probably seen this dozens of times over the years now.
Also, Godot has had occasional issues with bugs popping up only in release mode, such as https://github.com/godotengine/godot/issues/28922. Exporting in release mode at the last second may hide this kind of bug until you encounter it.

For example, as @pouleyKetchoupp mentioned, this change would affect the quick launch button

This change shouldn't affect one-click deploy in any way, as the debug argument is always true. One-click deploy should obviously keep using debug mode so that debug-only features can work there.
That said, we could consider adding a way to use one-click deploy in release mode for cases where you absolutely need high performance during testing (or to check for bugs that only appear in release mode, as mentioned above).

In Android development, you never want to use a debug keystore for release builds. Even if it's inconvenient, we should force the use to go through the process of generating a keystore specifically for release build. This is a big DO NOT DO in Android development, and we should not encourage users by making that the default.

While it obviously won't work when uploading the APK to Google Play, it should still work fine on your local device. You can still define a release keystore override in the export preset. I wish we could add documentation for individual export preset properties…

I'm okay with making release the default mode to avoid the mistake of publishing debug builds. But we should also avoid the mistake of publishing with a debug keystore. The best way to manage this is to show an error message if the release keystore is missing and the user is trying to export as release.

In Android development, you never want to use a debug keystore for release builds. Even if it's inconvenient, we should force the use to go through the process of generating a keystore specifically for release build. This is a big DO NOT DO in Android development, and we should not encourage users by making that the default.

While it obviously won't work when uploading the APK to Google Play, it should still work fine on a local device. You can still define a release keystore override in the export preset. I wish we could add documentation for individual export preset properties, so we could further clarify this…

I see this point not in terms that it doesn't work, but more about adding a default setting that most likely will induce users into making a mistake (that is, releasing with a debug keystore). Showing an appropriate error message will avoid the mistake, so it's better being annoying in this case.

As discussed with @m4gr3d on IRC, this is probably not a good idea so I'll close it. #39208 should be discussed separately, but he said he's OK with the idea as long as the release keystore requirement remains.


whats the problem in my flash script

Describe your problem here.
The script is not taking value2 and using it as the color for some reason A little help?
function onEvent(name, value1, value2)
if name == 'Flash Camera' then

   makeLuaSprite('flash', '', 0, 0);
    makeGraphic('flash',1280,720,'value2')
      addLuaSprite('flash', true);
      setLuaSpriteScrollFactor('flash',0,0)
      setProperty('flash.scale.x',2)
      setProperty('flash.scale.y',2)
      setProperty('flash.alpha',0)
	setProperty('flash.alpha',1)
	doTweenAlpha('flTw','flash',0,value1,'linear')
end

end
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No response

You should make sure that value2 is initialised BEFORE the main block and make sure it contains a valid color string.
if value2 then
makeGraphic (-- your valid color string.)
else
-- default it to white if value2 is not defined.
end

You should make sure that value2 is initialised BEFORE the main block and make sure it contains a valid color string.
if value2 then makeGraphic (-- your valid color string.) else -- default it to white if value2 is not defined. end

seems like im too dumb to figure out what to do with this

nvm i just had to remove the '' next to the value2

my bad, try removing the single quotes around value2, see if that does the trick

hey since the other guy hasent responded yet do you know whats wrong with this script
function onCreate()
makeAnimatedLuaSprite('glitch', 'bg', -315, -300);
addAnimationByPrefix('glitch', 'idle', 'idle', 24, true);
setLuaSpriteScrollFactor('glitch', 0.9, 0.9);
addLuaSprite('glitch', false);
objectPlayAnimation(obj:String, name:String, forced:Bool = false, ?startFrame:Int = 0);
close(true);
end
the objectPlayAnimation(obj:String, name:String, forced:Bool = false, ?startFrame:Int = 0); keeps giving me an error saying
"unexpected arguments near ",""

The syntax you're using appears to be influenced by TypeScript or a similar language, but Lua doesn't use type annotations like that.
`function onCreate()
makeAnimatedLuaSprite('glitch', 'bg', -315, -300)
addAnimationByPrefix('glitch', 'idle', 'idle', 24, true)
setLuaSpriteScrollFactor('glitch', 0.9, 0.9)
addLuaSprite('glitch', false)

-- Corrected objectPlayAnimation call
objectPlayAnimation('glitch', 'idle', false, 0)

close(true)

end`
try that.

The syntax you're using appears to be influenced by TypeScript or a similar language, but Lua doesn't use type annotations like that.
`function onCreate()
makeAnimatedLuaSprite('glitch', 'bg', -315, -300)
addAnimationByPrefix('glitch', 'idle', 'idle', 24, true)
setLuaSpriteScrollFactor('glitch', 0.9, 0.9)
addLuaSprite('glitch', false)

-- Corrected objectPlayAnimation call
objectPlayAnimation('glitch', 'idle', false, 0)

close(true)

end`
try that.

nope still not playing the anim

nvm i fixed it Thanks man


Filesystem Functions Not Working In the Block Editor

No files are created on the Micro:bit. The examples simply don't work.
These files should be viewable on Windows 10, right?

In order to view files on Windows 10, you will need a special bootloader that is not currently publicly available. You should be able to read the files from the micro:bit itself.
From: harveytwyman<EMAIL_ADDRESS>Sent: Wednesday, March 1, 2017 12:31 AM
To: Microsoft/pxt<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [Microsoft/pxt] Filesystem Functions Not Working In the Block Editor (#1476)
No files are created on the Micro:bit. The examples simply don't work.
These files should be viewable on Windows 10, right?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fpxt%2Fissues%2F1476&data=02|01|jhalleux%40microsoft.com|a63607113dca453affc608d4607d4b98|72f988bf86f141af91ab2d7cd011db47|1|0|636239538634648784&sdata=KA%2BKhLbScSGBM4U%2Fq4WzC6VRRsbS6i5GEZoyYbVNNGA%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAD-4KVLlGp9SyyET-aCAlWnlCaoSkRemks5rhSzEgaJpZM4MPWyI&data=02|01|jhalleux%40microsoft.com|a63607113dca453affc608d4607d4b98|72f988bf86f141af91ab2d7cd011db47|1|0|636239538634648784&sdata=tRuKQ2Q7DbBk3M2NcG4b8onUeHaQs2StrSnJfTQPDpY%3D&reserved=0.

You will also find a great FAQ at https://support.microbit.org/support/home

Until this "special bootloader" is available how can I get data off the micro:bit's files created?
Sending the files via serial is possible but would be simpler to read them directly.
How can I access this "special bootloader"?

Contact Joe Finney from Lancaster University: @finneyj


Change tokens examples memory leak

Examples are not disposing IDisposable returned by ChangeToken.OnChange promoting bound object (owner of InvokeChanged) lifetime to lifetime of change token issuer

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 9310e951-5185-4c31-064d-3a151acc17cf
Version Independent ID: 42bc4b7b-2a1c-0248-2740-0decdda6000c
Content: Detect changes with change tokens in ASP.NET Core
Content Source: aspnetcore/fundamentals/change-tokens.md
Product: aspnet-core
Technology: aspnetcore-fundamentals
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

cc @serpent5

We have a note in the article for this:

OnChange returns an IDisposable. Calling Dispose stops the token from listening for further changes and releases the token's resources.

The sample code demonstrates adding an OnChange callback handler to the Startup class, with no intention to stop listening for changes. I think that coverage and example is fine as-is, but more than happy to take a second opinion @Rick-Anderson.


increase max number of http request and response headers

The current limit of 32 https headers can be exceeded by some clients.
Between built-in headers from browsers and custom headers that may be
added in different places like CloudFlare or Nginx, this limit can be
hit by many clients. This commit increases the limits to 64, which is
much less likely to be reached.

I've increased the limit in a separate commit. Closing this out.


[BUG] env.set_info_dict_reader causes collection error

Describe the bug
Adding an info reader to read some information out of the info dict of the environment causes the collector to raise an error
RuntimeError: stack expects each tensor to be equal size, but got [1] at entry 0 and [] at entry 1
To Reproduce
This code allows to reproduce the error. Note that removing env.set_info_dict_reader(reader)  makes the code work fine.

import gym
import tqdm
import torch.optim
from torchrl.collectors import SyncDataCollector
from torchrl.envs import default_info_dict_reader
from torchrl.envs.libs.gym import GymWrapper
from torchrl.collectors import RandomPolicy

class AddInfoEnv(gym.Wrapper):
    def __init__(self, env):
        gym.Wrapper.__init__(self, env)

    def step(self, action):
        obs, rew, done, info = self.env.step(action)
        info["some_info"] = False
        return obs, rew, done, info

def make_env(env_name, device, is_test=False):
    env = gym.make(env_name)
    if not is_test:
        env = AddInfoEnv(env)
    env = GymWrapper(env, from_pixels=True, pixels_only=False, device=device)
    reader = default_info_dict_reader(["some_info"])
    env.set_info_dict_reader(reader)  # This line makes collector crash!
    return env

if __name__ == "__main__":

    device = "cpu" if not torch.cuda.is_available() else "cuda"

    # Make the components
    proof_environment = make_env("PongNoFrameskip-v4", device="cpu")
    policy = RandomPolicy(action_spec=proof_environment.action_spec)

    # Create the collector
    collector = SyncDataCollector(
        create_env_fn=make_env("PongNoFrameskip-v4", device),
        policy=policy,
        frames_per_batch=4,
        total_frames=10_000_000,
        device=device,
        storing_device=device,
    )

    pbar = tqdm.tqdm(total=10_000_000)
    for data in collector:
        pbar.update(data.numel())

    collector.shutdown()

Checklist

[x] I have checked that there is no similar issue in the repo (required)
[x] I have read the documentation (required)
[x] I have provided a minimal working example to reproduce the bug (required)

Solved! The correct code for the wrapper is the following. Also used gymnasium instead of gym
class AddInfoEnv(gym.Wrapper):
    def __init__(self, env):
        gym.Wrapper.__init__(self, env)

    def step(self, action):
        obs, rew, done, truncated, info = self.env.step(action)
        info["some_info"] = False
        return obs, rew, done, truncated, info

    def reset(self, **kwargs):
        obs, info = self.env.reset(**kwargs)
        info["some_info"] = False
        return obs, info


function validate, "FieldArray" field.push empty is considered error

What is the current behavior?
We make this example https://codesandbox.io/s/vor1y51y7 in the reflected a test field, when clicking the submit button does considered error and no show alert with object result
What is the expected behavior?
test has no validation in the function, it should do the submit correctly

Can you explain with further detail? I have a hard time understanding your current behavior

When I push an empty object to a fields array and submit, it fail validation

Try removing {...props} from the  component. You are passing the redux-form decorated component prop "onSubmit" onto that component which is giving it bugs.

Change:
const SyncValidationForm = (props) => {
  const { handleSubmit, pristine, reset, submitting } = props
  return (
    <form onSubmit={handleSubmit}>
      <Test {...props} />

        <button type="submit" disabled={submitting}>Submit</button>
        <button type="button" disabled={pristine || submitting} onClick={reset}>Clear Values</button>

    </form>
  )
}

To:
const SyncValidationForm = (props) => {
  const { handleSubmit, pristine, reset, submitting } = props
  return (
    <form onSubmit={handleSubmit}>
      <Test {...props} />

        <button type="submit" disabled={submitting}>Submit</button>
        <button type="button" disabled={pristine || submitting} onClick={reset}>Clear Values</button>

    </form>
  )
}

Your passing your onSubmit prop all the way from your index.js file:

ReactDOM.render(
  <Provider store={store}>

Synchronous Validation

      <SyncValidationForm onSubmit={showResults} />
      <Values form="syncValidation" />

  </Provider>,
  rootEl
);

Thanks, it works!


[Feature]add mysql jdbc connector to docker image

Is your feature request related to a problem? Please describe.
Docker image do not include mysql jdbc connector, as a newer to ds, I always need to copy mysql jdbc connector lib to the docker container and restart it.
Mysql is the more popular database(I think) than ck, mssql which are packaged in docker image, so I think, ds should package it in docker image.

the license of mysql jdbc connector not compitable with apache v2 license, so it can't be included by us