Database table is locked

Hi All,
After starting mailcatcher, first email is received perfectly. After that below exception is coming.
Please help me in resolving.
Exception: database table is locked
Backtrace:
/usr/lib/ruby/gems/2.2.0/gems/sqlite3-1.3.10/lib/sqlite3/statement.rb:67:in step'        /usr/lib/ruby/gems/2.2.0/gems/sqlite3-1.3.10/lib/sqlite3/statement.rb:67:in execute'
/usr/lib/ruby/gems/2.2.0/gems/mailcatcher-0.6.1/lib/mail_catcher/mail.rb:44:in add_message'        /usr/lib/ruby/gems/2.2.0/gems/mailcatcher-0.6.1/lib/mail_catcher/smtp.rb:46:in receive_message'
/usr/lib/ruby/gems/2.2.0/gems/eventmachine-1.0.5/lib/em/protocols/smtpserver.rb:539:in process_data_line'        /usr/lib/ruby/gems/2.2.0/gems/eventmachine-1.0.5/lib/em/protocols/smtpserver.rb:196:in receive_line'
/usr/lib/ruby/gems/2.2.0/gems/eventmachine-1.0.5/lib/em/protocols/linetext2.rb:64:in receive_data'        /usr/lib/ruby/gems/2.2.0/gems/eventmachine-1.0.5/lib/em/protocols/linetext2.rb:65:in receive_data'
/usr/lib/ruby/gems/2.2.0/gems/eventmachine-1.0.5/lib/em/protocols/linetext2.rb:65:in receive_data'        /usr/lib/ruby/gems/2.2.0/gems/eventmachine-1.0.5/lib/em/protocols/linetext2.rb:65:in receive_data'
/usr/lib/ruby/gems/2.2.0/gems/eventmachine-1.0.5/lib/em/protocols/linetext2.rb:65:in receive_data'        /usr/lib/ruby/gems/2.2.0/gems/eventmachine-1.0.5/lib/em/protocols/linetext2.rb:65:in receive_data'
/usr/lib/ruby/gems/2.2.0/gems/eventmachine-1.0.5/lib/em/protocols/linetext2.rb:65:in receive_data'        /usr/lib/ruby/gems/2.2.0/gems/eventmachine-1.0.5/lib/em/protocols/linetext2.rb:65:in receive_data'
/usr/lib/ruby/gems/2.2.0/gems/eventmachine-1.0.5/lib/em/protocols/linetext2.rb:65:in receive_data'        /usr/lib/ruby/gems/2.2.0/gems/eventmachine-1.0.5/lib/em/protocols/linetext2.rb:65:in receive_data'
/usr/lib/ruby/gems/2.2.0/gems/eventmachine-1.0.5/lib/em/protocols/linetext2.rb:65:in receive_data'        /usr/lib/ruby/gems/2.2.0/gems/eventmachine-1.0.5/lib/em/protocols/linetext2.rb:65:in receive_data'
/usr/lib/ruby/gems/2.2.0/gems/eventmachine-1.0.5/lib/em/protocols/linetext2.rb:65:in receive_data'        /usr/lib/ruby/gems/2.2.0/gems/eventmachine-1.0.5/lib/em/protocols/linetext2.rb:65:in receive_data'
/usr/lib/ruby/gems/2.2.0/gems/eventmachine-1.0.5/lib/eventmachine.rb:187:in run_machine'        /usr/lib/ruby/gems/2.2.0/gems/eventmachine-1.0.5/lib/eventmachine.rb:187:in run'
/usr/lib/ruby/gems/2.2.0/gems/mailcatcher-0.6.1/lib/mail_catcher.rb:155:in run!'        /usr/lib/ruby/gems/2.2.0/gems/mailcatcher-0.6.1/bin/mailcatcher:5:in <top (required)>'
/usr/bin/mailcatcher:23:in load'        /usr/bin/mailcatcher:23:in '

Odd! Sounds like a threading issue. Please try updating mailcatcher and see if it fixes your issues. If not, please comment again.


Remove any path in the compilation database parameters

I had the following error when my compilation database was loaded:
[deoplete] Traceback (most recent call last):
[deoplete]   File "/home/pcaneill/.vim/bundle/deoplete.nvim/rplugin/python3/deoplete/deoplete.py", line 98, in gather_results
[deoplete]     ctx['candidates'] = source.gather_candidates(ctx)
[deoplete]   File "/home/pcaneill/.vim/bundle/deoplete-clang/rplugin/python3/deoplete/sources/deoplete_clang.py", line 151, in gather_candidates
[deoplete]     params)
[deoplete]   File "/home/pcaneill/.vim/bundle/deoplete-clang/rplugin/python3/deoplete/sources/deoplete_clang.py", line 314, in get_completion
[deoplete]     tu = self.get_translation_unit(fname, args, buf)
[deoplete]   File "/home/pcaneill/.vim/bundle/deoplete-clang/rplugin/python3/deoplete/sources/deoplete_clang.py", line 301, in get_translation_unit
[deoplete]     tu = self.index.parse(fname, args, buf, flags)
[deoplete]   File "/home/pcaneill/.vim/bundle/deoplete-clang/rplugin/python3/deoplete/clang/clang/cindex.py", line 2322, in parse
[deoplete]     self)
[deoplete]   File "/home/pcaneill/.vim/bundle/deoplete-clang/rplugin/python3/deoplete/clang/clang/cindex.py", line 2440, in from_source
[deoplete]     raise TranslationUnitLoadError("Error parsing translation unit.")
[deoplete] clang.cindex.TranslationUnitLoadError: Error parsing translation unit.
[deoplete] Could not get completions from: clang.  Use :messages for error details.

When I looked at the params given to the translation unit it was something like this:
 ['-I/dfqdfqdfqd', '-Wblublu', '/path/to/the/file']

This patch aims to remove /path/to/the/file

Please support Windows path pattern.
You should use os.path.isabs(path).

I too am having this issue, @Moeryn have you made any further progress on this?

@parnmatt You can check param value.
The correct information is needed.

Unsure why, but the debug settings were not working; so I simply printed the arguments to a file.
The values of the args parameter that reached the translation unit (which are the params sent from this plugin) are: ['-x', 'c++', '-std=c++1z', '-I'].
This is when writing in a simple test file, and the error is thrown after type st.

Please upload the compilation database.
I will test it.

I will close the issue.  Because, the original author @Moeryn is no response and it does not fix the real problem.
@parnmatt Please create new issue with minimal init.vim and the simple test file and the compilation database file.
I will test it.


Out-of-bound memory accesses in ComputeBucketSums

I believe I've identified a small bug in the computeBucketSums kernel; it looks like when some threads in a warp have nonzero bucket counts and some do not, those without occasionally make out-of-bounds memory accesses (to maintain thread synchronization I think?). The results of those accesses are not used so the computation is correct, but I've noticed this causing some undefined behavior that occasionally makes the GPU crash (sometimes well after computeBucketSums has completed). I wrote a quick fix that zeros the "point indexes" section of shared memory at the start of the kernel, which resolves the issue with fairly negligible impact on performance. This consisted of inserting the following lines at the start of the computeBucketSums kernel:
  // Zero point index portion of shared memory
  for(int i = 0; i<4*GROUP*384/sizeof(uint32_t)/blockDim.x; ++i){
    store_shared_u32(19968 + sizeof(uint32_t) * (i*blockDim.x + threadIdx.x), 0);
  }
  __syncthreads();

(Note that there is probably a more optimal way of zeroing the necessary memory here).

Hi John,
Thanks for reporting the issue.  That makes sense.
I think the assumption was that there would always be a valid point index from an earlier iteration.  But that just begs the question, what happens on the first iteration...
Thanks,
Niall


BUG: bvls can fail catastrophically to converge

The function bvls, which is called by optimize.lsq_linear(... method='bvls') can fail catastrophically to converge due to an incorrect implementation of the published BVLS algorithm.
It is supposed to implement the BVLS algorithm by Stak & Parker 1995, which is a small generalization of the classic NNLS algorithm 23.10 by Lawson & Hanson (1995).
However, the current Scipy implementation fails to implement the so-called loop-B in the notation of the above two papers.
The proposed changes fix the deficiency and allow the algorithm to converge in the cases where it currently fails.
Reference issue
Here is a minimal example where the current implementation fails
seed = 159
np.random.seed(seed)

n, m = np.sort(np.random.randint(2, 4, size=2))
A = 1.*np.random.randint(-99, 99, size=[m, n])
b = 1.*np.random.randint(-99, 99, size=[m])
bounds = 1.*np.sort(np.random.randint(-99, 99, size=(2, n)), 0)

print("seed", seed, "dims:", m, n, "rank: ", np.linalg.matrix_rank(A))
print(A)
print(b)
print(bounds)
print("")

x2 = optimize.lsq_linear(A, b, bounds=bounds, method='bvls', verbose=2).x
x3 = optimize.lsq_linear(A, b, bounds=bounds, method='trf', verbose=2).x

print(f"   x_bvls = {x2}")
print(f"    x_trf = {x3}\n")

chi2_2 = chi2(A @ x2 - b)
chi2_3 = chi2(A @ x3 - b)
chi2min = min(chi2_2, chi2_3)

print(f"rel_err   bvls: {chi2_2/chi2min - 1:.2e}")
print(f"rel_err    trf: {chi2_3/chi2min - 1:.2e}")

And here is the corresponding output of Scipy 1.5
seed 159 dims: 3 3 rank:  3

[[ 49.  41. -32.]
 [-19. -32.  -8.]
 [-13.  10.  69.]]

[-41. -90.  47.]

[[ 31. -44.  26.]
 [ 54. -32.  28.]]

Iteration        Cost      Cost reduction    Step norm     Optimality
       0         7.4506e+05                                    4.80e+04
       1         3.5282e+05      3.92e+05       1.64e+01       1.68e+04
       2         2.4232e+05      1.11e+05       1.03e+01       1.14e+04
The relative change of the cost function is less than `tol`.
Number of iterations 3, initial cost 7.4506e+05, final cost 2.4232e+05, first-order optimality 1.14e+04.

   Iteration        Cost      Cost reduction    Step norm     Optimality
       0         8.0576e+05                                    1.05e+06
       1         3.9417e+05      4.12e+05       8.77e+00       2.59e+05
       2         2.8801e+05      1.06e+05       5.67e+00       6.47e+04
       3         2.3206e+05      5.60e+04       5.84e+00       1.08e+04
       4         2.1981e+05      1.22e+04       1.60e+00       6.26e+02
       5         2.1920e+05      6.11e+02       2.46e-01       1.73e+02
       6         2.1915e+05      4.84e+01       1.21e-01       4.13e+01
       7         2.1914e+05      7.86e+00       5.52e-02       8.58e+00
       8         2.1914e+05      7.29e-01       1.95e-02       1.15e+00
       9         2.1914e+05      1.83e-02       3.49e-03       4.08e-02
      10         2.1914e+05      2.47e-05       1.33e-04       4.93e-05
      11         2.1914e+05      2.43e-10       1.61e-07       1.35e-10
The relative change of the cost function is less than `tol`.
Number of iterations 12, initial cost 8.0576e+05, final cost 2.1914e+05, first-order optimality 1.35e-10.

   x_bvls = [ 54.         -39.82549256  26.        ]
    x_trf = [ 54.         -43.89055258  26.        ]

rel_err   bvls: 1.06e-01
rel_err    trf: 0.00e+00

Additional information
The current implementation fails in various other examples, with more realistic larger arrays, and especially when the matrix A is rank deficient. However, I selected a very simple example to make it easy to understand what the code is doing differently in the proposed changes.

I think this algorithm was implemented based only on the BVLS paper. They don't go in details on implementation details and only mention "Loop B" briefly. As far as I understand the problem arises because of finite precision computations, but of course it is important for numerical methods.

Would it be practical to add a regression test based on the minimal example provided?

I think at least one test to trigger this problem is a must. And, if possible, I would suggest extending the tests for this algorithm significantly as it proved to be fragile. Adding a test with "with more realistic larger arrays" would be very suitable.

Where/how would I add the tests?

This is the file with tests https://github.com/scipy/scipy/blob/master/scipy/optimize/tests/test_lsq_linear.py
Add tests into BaseMixin. If you have any issues with it, I'll be happy to hep.

Any problems with adding tests from #12816 as another commit here?

Any problems with adding tests from #12816 as another commit here?

I blindly cherry-picked those tests, they had some syntax issues. Fixed those and made the linter happy too, but the tests are failing - this needs work it looks like.

@rgommers
It was a trivial syntax error. Now tests are active and passing.
I think we should merge it finally.

Great, glad to see this merged. Thanks @divenex and @nmayorov


[nitter] Add new extractor

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Bug fix
[ ] Improvement
[x] New extractor
[ ] New feature

Description of your pull request and other information
Add an extractor for nitter, a "free and open source alternative Twitter front-end focused on privacy."

Nitter is just a Twitter frontend, even with the same URL scheme as Twitter. There should be just a modification to the Twitter extractor to match Nitter domains to it.

#24349 is down…
That's what I started to do, but the nitter creator told me to create an extractor instead of just support nitter URLs in Twitter extractor,
because nitter proxies video and then Twitter does not know you, but only the nitter server

Hi! There have been more Nitter instances added, may you please add them to the extractor? Thank you!!

I added all instances working.

Nitter is open-source. It would be nice if youtube-dl could recognize it regardless of where it's found, especially now that I see public Nitter instances getting taken down. I could run Nitter on my LAN and not worry about takedowns.


ci: remove unused build tags from go test

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

I'm pretty confident they're not needed b/c I couldn't find any instances of the build tags in test files so specifying the tags in go test doesn't change which tests are run

yeah, they're not needed


Publish 7.5-20220703235851+0000

Publish 7.5-20220703235851+0000

@bot-gradle test and merge

OK, I've already triggered a build for you.


in_tail: tests about file rotation and deletion sometimes fail

On CI environment, tests of in_tail  sometimes fails with incorrect number of events, or wrong event order.

test_rotate_file_with_write_old[parse](TailInputTest::rotate file)

https://travis-ci.org/fluent/fluentd/jobs/193651057
https://travis-ci.org/fluent/fluentd/jobs/195131107

test_missing_file(TailInputTest)

https://travis-ci.org/fluent/fluentd/jobs/195731891

test_multiline_with_multiple_formatsflat

https://ci.appveyor.com/project/fluent/fluentd/build/2345/job/mgy36d6xqqlye4bt

test_emit_with_read_lines_limit

https://travis-ci.org/fluent/fluentd/jobs/196492970

This shows in_tail potentially has a bug to handle file rotation.

After adding some more changes to in_tail plugin and its tests, recent days we don't see such failures.
So I close this issue.
We should update information about unstable tests.

For windows, I've found a bug in the tests:  #3767


src directory deleted on unmounting/mounting theme

This is nice.
It would have been awesome if the themes were an 'npm install' after gatsby new.
Or integrated within Gatsby. Nevertheless good job on this!
When I tried running the project the src directory gets deleted on un-mounting and mounting a theme.

Hey thanks for the positive vibes ❤
Now the problem with npm install is that the theme would be installed in the node_modules folder. There are a few reasons why we do not want that to occur.

We want the file visible in our working directory, not hidden away in the untracked node_modules folder.
We want to be able to freely edit the files. Customizable themes are at the core of this project.

At its core Jay is a filesystem tool. To unmount the current theme, we basically rename and move the src folder into the themes folder under a different name. Therefore there will be no src folder after unmounting.
To your point though a better experience might be to do more cloning and leave the directories sorta in tack however then we might not be sure that something happened. Feel free to make a PR if you think we can make this experience better. I'm glad you like it!

@nodox Thanks for your quick response!
I installed the gatsby-jay cli globally.
I then followed the procedure of git clone, yarn, followed by the unmount and mount of the theme. The src folder did not come back after I did the mount and so gatsby develop could not start.
I then manually created the src folder and the pages folder and put in sample react component.
I tried running gatsby develop but it error'ed as it couldn't find a template component i guess ...
Not sure what I am doing wrong.

I think you need to run these commands. The step you are missing I believe is the add step. Try these steps @Jaikant
$  jay unmount starter
$  jay add identity
$  jay mount identity

Nice it works now! I had done this earlier too, but maybe there was something stale in my project.
So we can port any theme to Gatsby Manor? Do you have any documentation on how we can do that? (Probably a separate issue/ask :)

...and I found the documentation to make themes! Thanks :)
I will try this for a project I am going to work on next week, for a friend's website.

Awesome! Let us about the final result on Twitter @TheGatsbyManor. 😄


Merge ote updates to NNCF_support

2 @aleksei-kashapov : Alexei, please, take a look.
Please, note that this branch is WIP, I have not checked it after merge ote updates.

2 @aleksei-kashapov : Aleksei, I updated the branch and checked it on couple of experiments.
Could you re-check it on some experiments too?
If everything is ok, please, merge it!


Allow --use-angle=vulkan when ozone platform is Wayland, fixes vaapi on amd

feature request
Quoting the original description by Niccolò Belli:
"vaapi on amd cards requires --use-angle=vulkan: https://wiki.archlinux.org/title/Chromium#Hardware_video_acceleration
Since the gl=egl-angle,angle=vulkan GL implementation is not found in allowed implementations you cannot use it on ozone wayland.
The necessary support in ozone and ANGLE are present and can be enabled with a one line patch.
The angle=vulkan rendering is better on ozone wayland than it is on x11: on xwayland I have major rendering issues in websites like figma which are completely fine on ozone wayland. I can also confirm that vaapi works flawlessly on wayland.
The patch is harmless because unless you tune your flags to use --use-angle=vulkan it is disabled by default anyway on both x11 and wayland.
Since mesa 24.1 has just been released and it finally enables vaapi video decoding on amd cards this is a good time to merge this.
Upstream issue: https://issues.chromium.org/issues/334275637"
Describe the solution you'd like, including relevant patches or source
Please incorporate this one line patch: https://gitlab.archlinux.org/archlinux/packaging/packages/chromium/-/merge_requests/6
Additional Notes
Description and patch taken from:
https://gitlab.archlinux.org/archlinux/packaging/packages/chromium/-/merge_requests/6

I think we need to carefully evaluate whether the relevant patch will break other parts. I will carefully review the issue you mentioned above later and may make some edits.

There is even an AUR package that carries it forword if you want to test it: https://aur.archlinux.org/packages/google-chrome-wayland-vulkan
Robrich also tested it: https://github.com/RobRich999/Chromium_Clang/issues/26#issuecomment-2132485205

Once patched VA-API should be working under Xwayland, too.
https://github.com/RobRich999/Chromium_Clang/issues/26#issuecomment-2134077918
Perhaps X11 as well, though someone else will have to verify it.

For the record, X11 was already working fine with VAAPI before, but native Wayland didn't work at all, even hardware acceleration is completely broken there. Xwayland also works fine for me, but it has some limitations (only software GPU memory buffers) and some users reported problems with that option. There is more discussion in the upstream bug report which I've linked in the top post.

I have not been keeping much track of hardware decoding as I gave up long ago on conjuring the latest CLI incantations to obtain functional VA-API support. ;)

https://chromium-review.googlesource.com/c/chromium/src/+/5568860
I've got the patch to land upstream

CL caused Lacros FYI's test suite to fail and has been reverted. I am trying to discuss a solution with the engineers.

CL caused Lacros FYI's test suite to fail and has been reverted. I am trying to discuss a solution with the engineers.

As the upstream discussion stalled, is there a chance for a quick fix? If not, carrying this patch downstream might be an option as the seen issue seems to be a non-issue for people that need to set this variable manually. At least it would provide some value for all Linux/Wayland users right away.

The upstream issue probably won't be fixed quickly enough and looks like some deeper issue. Also, since this patch affects ChromiumOS, I don't know if it will be merged in Thorium.
@Alex313031

it's not a deeper issue at all - Google has been researching a project of turning ChromeOS into a weird zombie mix of real "Linux" DRM/KMS/Wayland and "Android" graphic system components under "Lacros" project.
The new Vulkan path had no chance of running with the "Android" graphic system, yet it was still "Linux".
There really is nothing more to it, than properly IFDEFing this code path to avoid "Lacros" target so it only targets real "Linux".
I would really appreciate the patch being merged; at the moment there is no working VA-API build anywhere in the internet, except for AUR, which isn't very useful outside Arch.

Chromium 129 re-added the reverted patch, and using the CachyOS v3 hardware video decode works with --use-angle=vulkan.


Fix #559 - Testimonials section gaps

Pull Request Template

Please provide all of the details below. Pull requests missing any of the information below will be closed!
Providing the issue number/url helps us identify the problem being solved and keep the issues tab clean and tidy

This is not a fix. This is a request to add login and signup pages to the site.
Summarize what this PR fixes:-
Fix #559 - Testimonials section gaps in between sections.
Checklist
(Add an x between the brackets to check the items)

[x] I have summarised what this PR fixes above
[x] I have provided the issue ID/URL above
[x] I have not added Bootstrap or jQuery and used correct styling guide.
[x] This PR fixes only the issue mentioned above (create separate PRs for separate issues)
[x] I was the first one to claim the issue or I created the issue - I created the issue

These are not aligned with the mockup, it is supposed to be a carousel and the margins are too close.

On the screenshot below, there is a gap between Companies section and Testimonial section - not sure if it's visible:

Whereas there is no gap on the design:

The carousel needs a separate work. However, following the design, I think this should be fixed.
What do you think? @brittneypostma  😄


fix(typeahead): select match on tab for iOS webview

Select match on blur if only it has not been selected upon keydown

The fix can be seen in action in this Plunker.
 LGTM.


BREAD ajax error when searching on a relationship field that has a scope configured

Version information

Laravel: v7.6.2
Voyager: v1.4.1
PHP: 7.4.4
Database: MariaDB 10.4.11

Description

When adding / editing an entry with BREAD, if you search a relationship field where a scope was configured, the search will fail.
Inspection of the AJAX response from the controller shows an exception was raised in Laravel with the following message:
"Property [additional_attributes] does not exist on the Eloquent builder instance."
Steps To Reproduce
Steps to reproduce the behavior:

Create a table (eg: foos) with a field that references another existing table (eg: users).
Configure BREAD for the new table, creating a relationship to the other table (eg: foo belongsTo user).
In the model for the referenced table (eg: App\User), create a scope function (eg: filter role_id to show admins only).
Back to the BREAD relationship, add a JSON configuration to use your new scope to limit the entries shown in the field.
Go create a new entry in the new table (foos). The relationship list (users) is populated. Type in anything to search the list and the error will appear.

Expected behavior
Search results should appear normally, as they do when no scope is configured.
Additional context
The exception is raised in line 871 of the following file:
vendor/tcg/voyager/src/Http/Controllers/VoyagerBaseController.php
It is trying to access $model->additional_attributes.
However, earlier in the code (line 864), if a scope is present in the options, the $model variable is reassigned to what the scope function returns (an Illuminate\Database\Eloquent\Builder instance). And so accessing additional_attributes in the Builder instance raises an exception.
I've fixed this locally by adding another variable that references the original model that is loaded on line 860:
$originalModel = $model = app($options->model);
Then I use this variable when looking up the attributes on line 871:
if (in_array($options->label, $originalModel->additional_attributes ?? [])) {

Please search before opening issues.
Duplicate of https://github.com/the-control-group/voyager/issues/4949
And already fixed in https://github.com/the-control-group/voyager/pull/4875


Localization

Is there or will be there any opportunity for localization?
The most important is the Value format, which is M, bn and so on now and standard Power BI uses localized versions of these abbreviations.

@tamas-karacsony The visual has localization built into it. Here is a screenshot of the visual in German.

Can you send me a screenshot of the error in case you don't see this?
Thanks
Nishant

Dear Hishant,
if I define "Auto" Value Format then I get the following result:

Here you can find "bn" and "M" abbreviation for scale, which means "billion" and "Million".
This called "short scale" and in Hungary (and other parts in Europe) we use "long scale", which use different name for same scales. See: https://en.wikipedia.org/wiki/Long_and_short_scales
Operating system localization handles this appropriately, for example it uses "mrd" instead "bn" and "m" (lowercase) instead "M". The add-in does not use this localization and shows US abbreviations for scale. (I don't know if this is a standard opportunity in add-ins or needs some development)
Thanks,
Tamas

@tamas-karacsony Apologies for the delay in responding. I am now actively working on adding the localization feature to the visual. I will let you know once it is done.
Thanks

@tamas-karacsony Apologies for the delay in responding. I am now actively working on adding the localization feature to the visual. I will let you know once it is done.
Thanks


chore: bump ktlint to 9.4.1

This PR bump the ktlint to 9.4.1 and performed the ktlintFormat and turns out that it hates star imports so added a project Kotlin code style to prevent the usage of star imports.

I change the commit message from core: bump ktlint to 9.4.1 to chore: bump ktlint to 9.4.1 (assuming you wanted chore as the commit message)

When I realize I can use Kotlin 1.4.10 features but have to fix merge conflicts now

Wait, I don't get this 😵, I can't find the source of the quote. If there's a merge conflict to another story, we should merge that first then rebase from there.

I'm still working on #235 right now, it's not that big of a deal.

Hmmm, I think it would be better to merge that first as the linter can do its job later (can add this to a poem). What do you think?

That works for me.
I've got a couple 1.4.10 features that I want to convert to, do you think that should be a separate pr?

I've got a couple 1.4.10 features that I want to convert to, do you think that should be a separate pr?

If you think that the story is related to it, then go for it, but in case of the module is non-relevant, then I'd suggest to separate it to a different PR, the reasoning behind is if ever we want to revert commits, we can still retain the wanted changes only revert the relevant ones.

It should probably be a separate task, that depends on this.


chore: flip to use @aws-amplify namespace for private packages to avoid collision with improperly published packages

Description of changes
Somebody was squatting on the non-namespaced versions of our test core package, resulting in a security alert. This is a private package and should not be published. Flipping to use the secured @aws-amplify npm namespace to avoid issues like this in the future.
Issue #, if available
N/A
Description of how you validated changes
Built and tested the repo.
Checklist

[x] PR description included
[x] yarn test passes

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #442 (9548ad7) into master (6cd7581) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #442   +/-   ##
=======================================
  Coverage   85.19%   85.19%
=======================================
  Files         142      142
  Lines        6695     6695
  Branches     1727     1727
=======================================
  Hits         5704     5704
  Misses        900      900
  Partials       91       91

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Create a simple README.md

Hello!
I took the text from the Modrinth site, added download buttons for Curseforge and Modrinth to make a README file for the repo! Makes it look better on GitHub and helps people see how and where to contribute and download! :)
Any changes are welcome, as this is only an idea from my part!
All the best,
Björkan!

Thanks!


Missing include to src/core/lv_theme.h in src/themes/mono/lv_theme_mono.h

Missing include to src/core/lv_theme.h in src/themes/mono/lv_theme_mono.h
Compilation failed when using the mono theme: Undefined lv_theme_t
To Reproduce
Steps to reproduce the behavior:

build the benchmark demo example using mono theme instead of the basic one.
Or add below code into your disp_init()

lv_disp_set_theme(disp, lv_theme_mono_init(disp, false, LV_FONT_DEFAULT));

Expected behavior
Compilation done successfully
Environment (please complete the following information):

OS: Windows

INVALID


coordinates: init at 0.4.0

Motivation for this change
Packaging coordinates, a python module.
Things done

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

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

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

@GrahamcOfBorg build python36Packages.coordinates python37Packages.coordinates python38Packages.coordinates

Also, please update the PR/commit to a buildable package name, here python3Packages.coordinates: ....  Thanks!

@GrahamcOfBorg build python3Packages.coordinates python36Packages.coordinates python37Packages.coordinates python38Packages.coordinates

Thanks for the advice everyone, I've

Switched to the github release, as that includes test
Disabled for python 3.5 and below
Fixed the commit message

Let me know if there's anything further.

@GrahamcOfBorg build python37Packages.coordinates python38Packages.coordinates


20w45a things

Yoinked from Saiko's mapping server, might have grabbed some other people's mappings too oops

You yoinked some of my mappings too ...

i fix conflicts yes yes


Switch to custom lttng-ctl Python bindings

This replaces the lttng-ctl Python bindings (python3-lttng), on which the ros2 trace command and Trace launch action rely, with a new implementation.
The new lttng-ctl Python bindings implementation, lttngpy, uses pybind11 to bind C++ code to Python. The bindings do not cover the whole trace control library (liblttng-ctl, from the liblttng-ctl-dev package on Ubuntu), but they cover whatever is needed by tracetools_trace/ros2trace. A lot of lttngpy is just exposing C functions and constants from lttng-ctl (which usually start with lttng_* or LTTNG_*) to Python. However, lttngpy does wrap some lttng-ctl functions to provide a more Pythonic interface, e.g., Optional[...] arguments and Union[...] return types.
I replaced the calls to the current Python bindings (lttng) in tracetools_trace (and some other locations) with calls to lttngpy. It is (almost) a simple drop-in replacement; users should not notice any difference. In fact, this even improves the usefulness of ros2 trace/Trace, since they now support enabling perf counters, e.g., ros2 trace -c perf:thread:task-clock. Indeed, the bindings available from python3-lttng do not completely cover liblttng-ctl. They are always lagging behind; I've fixed issues and contributed improvements before, but, since any new improvements are only going to be available from apt in the next Ubuntu LTS release, we cannot rely on this. Therefore, I think implementing our own bindings is a better solution.
Note: The Sanity checks / binary (rolling) CI job will fail because ros-rolling-lttngpy is of course not yet available.
Requires https://github.com/ros2/ci/pull/725 for CI

@iluetkeb as we discussed

Testing everything above lttngpy:

Linux
Linux-aarch64
Windows

Oh, right, I need to install liblttng-ctl-dev in CI.

@mjcarroll I don't have access to ros2/ci. Could you push my PR branch to the repo? Then I can re-run the CI jobs above using that CI branch, or you can do it if you want.

https://github.com/ros2/ci/tree/christophebedard/install-liblttng-ctl-dev

The RHEL job fails due to another issue, see https://github.com/ros2/ci/pull/725#issuecomment-1819548255.

Let's try again:
Testing everything above lttngpy with https://github.com/ros2/ci/pull/725:

Linux
Linux-aarch64
Windows
Linux RHEL

Looking good now, RHEL included.
@mjcarroll could you review the latest changes, i.e., the last commit?

This pull request has been mentioned on ROS Discourse. There might be relevant details there:
https://discourse.ros.org/t/ros-2-jazzy-jalisco-released/37862/9


Fails on MWE: Cannot determine Numba type of <class 'function'>

The following MWE causes the Numba to fail:
import numpy as np
from numba import njit
from numba_kdtree import KDTree

@njit
def numba_function_with_kdtree(data):
    kdtree = KDTree(data, leafsize=10)
    for i in range(5):
        distances, indices, _ = kdtree.query(data[i], k=30)
        # Use the computed neighbors
        print(distances, indices)

data = np.random.random(3_000).reshape(-1, 3)
numba_function_with_kdtree(data)

with the error
TypingError: Failed in nopython mode pipeline (step: nopython frontend)
Untyped global name 'KDTree': Cannot determine Numba type of <class 'function'>

In the current version it was indeed not possible for KDTree to be called from within a numba compiled function. The created object instead had to be passed into the function as an argument.
I've just realized, that this is actually no longer required so I've just published a new release (0.1.7) that removes this restriction.

In the current version it was indeed not possible for KDTree to be called from within a numba compiled function. The created object instead had to be passed into the function as an argument. I've just realized, that this is actually no longer required so I've just published a new release (0.1.7) that removes this restriction.

Thank you! I have upgraded to version 0.1.7, but the same error still persists.


What does the exit status mean?

status = Process.run("exit 1", shell: true)
status.exit_status # 256
status.exit_code # 1

It's the platform-specific exit status code, which usually contains either the exit code or a termination signal. The other Status methods extract the values from exit_status.

This is lacking documentation, help welcome!

Looks like this issue can be closed. Docs are added by #8014.


Visual bug in documentation

In new version of documentation exists visual bug
Bug when hover to links

looks like problem with z-index and wrong colors

Upvote & Fund

We're using Polar.sh so you can upvote and help fund this issue.
We receive the funding once the issue is completed & confirmed by you.
Thank you in advance for helping prioritize & fund our backlog.

@el1sha256 thanks! can you link me the page that has this issue? 😊

@patrick91 I think we can close this issue, i don't see now this bug in documentation


piano-genie build doesn't seem to work

I just cloned the piano-genie demo and tried to build it, but yarn build gives me this error:
TypeScript error: node_modules/@tensorflow/tfjs-core/dist/kernels/webgl/gpgpu_context.d.ts(15,27): Error TS2304: Cannot find name 'WebGLLoseContext'.
error Command failed with exit code 1.

Is there a problem with the version of tfjs it's using?
cc @chrisdonahue

Just tried and got the same issue. Fixed it by upgrading to<EMAIL_ADDRESS>and<EMAIL_ADDRESS>Confirmed that tests still work after upgrade.

Hey just an FYI that I am working on a PR to add a stripped-down version of Piano Genie directly to magenta-js. Hope to have it in by EOD.

This can be closed now probably :)


Foreign fetch sample

R: @addyosmani @jakearchibald @ebidel @PaulKinlan @beaufortfrancois etc.
CC: @mkruisselbrink
Here's a basic sample illustrating the use of foreign fetch to handle offline use cases for a trivial random-number API.
The code for the service that's checked in here is a copy of what's currently deployed at https://foreign-fetch-demo.appspot.com
Feel free to review at this time, but DO NOT MERGE yet, as there's a serious bug in the current M54 implementation of foreign fetch that will cause the fetch() in the service worker to loop for ~10 seconds then fail.
The https://developers.google.com/web/updates/2016/09/foreign-fetch URL referenced in this post also is not live yet (waiting on the same bug to be resovled).

Thanks, Jeff. It looks like the fix for the issue referenced landed a few hours ago in https://crrev.com/65299f214fad8f609c5872bcdd5f4ea82ec29713 and should be in latest trunk/Canary in a day or two. Fwiw: the deployed version of the demo in this PR looks like it may be down atm, but will check again later.

The remote "API" service is hosted on https://foreign-fetch-demo.appspot.com/random, and the FF SW is served from https://foreign-fetch-demo.appspot.com/foreign-fetch-sw.js. Those both look up. But there's (deliberately) nothing handling the root of https://foreign-fetch-demo.appspot.com, so maybe that's what you saw.
(We don't have confirmation yet as to when the fix will be merged from Canary into Beta.)

Updated with review feedback, and it's now deployed to https://jeffy.info/samples/service-worker/foreign-fetch/
It should work as expected in Chrome Canary, but the fix for the infinite loop bug hasn't been merged to Chrome Beta at this time.

Given that the bug fix is tagged to be merged into the next M54 build, and given that getting this submitted is a prerequisite for publishing the /web/updates article, I'm going to merge this but not make any noise about it until the article comes out.
Happy to file a follow-up PR with any updates after the fact.


Improve test detection

At the moment, tests will be recognized if:

Any of the test frameworks we know are used.
If a class is defined with asserts
If any defined function has asserts
If the body has asserts

However, if the test imports another class where the validation is performed, we do not detect it as a test right now. This is not very common, but we should consider it too. Annotated as a TO DO in cli.py (ast_if_test function)

Tagged as enhancement and not bug because we usually do not tag things incorrectly with this method.


chore: fix Dockerfile warning related to uppercase and lowercase mix

From the docker documentation https://docs.docker.com/reference/build-checks/from-as-casing/
we shouldn't mix upper case FROM with a lowercase AS

/ok-to-merge fixing warning on Dockerfile


frontend: RecentClusters: Add multi cluster selection feature

If there are multiple clusters then this allows selecting up to three of them from the recent clusters list.
If there is a single cluster it acts as before.
This feature can be enabled by using:

REACT_APP_MULTI_ENABLED=true make run-frontend

Screenshot
Here we see a toggle button group of the three most recently used clusters.

As a bonus this fixes a bug:

text is not cut off (important when the shared resource/subscription name is the start of the cluster name)

How to test

[x] have at least two clusters enabled, and select the clusters you want to use at once, it takes you to the correct URL with a + separating the clusters
[x] when you don't select any clusters it doesn't let you select the view button

The button group showing recent clusters doesn't seem to be very intuitive, I think it would be hard to understand
To be honest I personally never use recent cluster buttons, I always select from the list
What if we did something like this?

Yeah, we can add multiple select with checkboxes like that. But I'll explain why I didn't...

The button group showing recent clusters doesn't seem to be very intuitive, I think it would be hard to understand
To be honest I personally never use recent cluster buttons, I always select from the list

For what it's worth I tried it with two people without prompting "Select multiple clusters" and they figured it out. The third person I just showed the video and they suggested changing it to use the existing Recent cluster cards instead of just the words.
Mainly this code is a temporary step to allow something now and until both

the full 'new home' design is implemented and can be iterated on/user tested
and the websocket multiplexer is integrated and tested.

The reasons are:

The idea is to limit it to 3 clusters until the multiplexer is in properly
It lets people test the rest of the multi cluster more easily without waiting for the rest of the stuff
We can use it in a demo in Kubecon in a few days
This can be enabled/disabled trivially

This should be replaced by the commits in https://github.com/headlamp-k8s/headlamp/commits/aggregated-view-original-rebased/ (lookout for fixups) related to e9b7f46 .

@joaquimrocha we discussed this is a temporary measure for reasons mentioned here. Additionally it was discussed and agreed to take this approach with Chris. First a minimal version that is disabled, and then the full version.

If this is temporary and was user tested a bit then it's okay, we can do checkboxes later

For the checkboxes is what I proposed to handle maxium of 3 sound ok? Or if you have any other ideas for that I'd appreciate it.

Yeah that's reasonable. Although I'm a bit worried about allowed namespaces feature. If we have 2 allowed namespaces for each of 3 selected clusters and go to Workloads page then we'll get (7 workloads)(3 cluster)(2 namespaces) websockets. But it's and edgecase.

Maximum of 3 selected, and then it won't let you add any more, with an additional message. "Selected 3 of 3. Currently only three clusters can be selected at once"

I think it's better to disable the "connect" (or "view") button (keep the message, but highlight in red "Selected 4 of 3. Currently only...") but still allow selecting checkboxes, I think it'll be less frustrating

Thanks @sniok

@illume i started to work on multi delete feature. You table and my table changes should be merged. What do you think of my design by hiding filter during the selection? #2594

ATM we should rather add the named groups feature instead of a radio button based solution.
We should still keep the multiple selection of clusters so we create a group (named) from them.


Create a favicon

@JulianSamarjiev do we already have one?

Handled by https://github.com/sphereio/sphere-sunrise-design


Test Django 5.0

Problem
Test the new version of Django that’s in beta.
Depends on #582. If you want to consider updating SaveSignalHandlingModel, we can look at that, but I really suggest that it be removed.
Solution
Added classifier to setup.py, new test environment to tox.ini, setup, and upgraded test requirements to fix some warnings.
Commandments

[x] Write PEP8 compliant code.
[x] Cover it with tests.
[x] Update CHANGES.rst file to describe the changes, and quote according issue with GH-<issue_number>.
[x] Pay attention to backward compatibility, or if it breaks it, explain why.
[x] Update documentation (if relevant).

Apologies for the initially wrong title, that will have caused duplicate-looking threads on email.

Hey @adamchainz could you possible merge master into your branch and update the django 5.0 version to the release one. Then I would say let's go ahead with merging this PR.

I rebased rather than merging!

Hey @adamchainz thanks for the work. I just merged your PR and tried to push a new release to pypi. It seems there is a release gh workflow: https://github.com/jazzband/django-model-utils/actions/runs/7856043884/job/21438400809 but it doesn't seem to work. Do you happen to know more?

I have no idea, sorry. I'm no maintainer.

hey @carljm, are you the original author of this library? After merging Adam's work I tried to push out a new release, but it looks like the release script doesn't fully work anymore:  https://github.com/jazzband/django-model-utils/actions/runs/7856043884/job/21438400809  do you have any idea wat could go wrong here?

@shanx I am the original author, but I have neither used the project or been involved in maintenance for at least 8 years. I'm afraid I don't know anything about how that publish script works or what went wrong with it. I am willing to collaborate as needed in handoff steps to a responsible maintainer, but beyond that I don't have any interest in maintaining django-model-utils. Sorry!

I totally understand that @carljm. I thought the spend a bit of time on this, get a release out there. But also don't have time to really dive into things. I see jazzband has the possibility to get help on a new release to pypi, I'll give that a shot. Anyway thanks for answering and have a beautiful day.

@adamchainz a release was just pushed to pypi by @charettes. Thanks everyone!


improve Wireguard reliability

During the development of #135, we encountered some issues with Wireguard that we want to tackle.

[ ] SSH into nodes in Pluscloud Open based Clusters

Details: The Wireguard VPN could be set up and connected to. The access via kubectl or k9s using the config from resources/kubeconfig worked fine. The problem is that the SSH access only works to the nodes that have been contacted by other means (like kubectl or via HTTP, ...) recently (last 15 or so minutes).
We investigated this with tcpdump, ssh -vvvv, and the logs of sshd and saw that at least some packets reached the targeted node, but the communication broke soon and the client waited for the key-exchange (at least in my memory). If we cancel SSH, contact the server otherwise (e.g. kubectl to the orchestrator) and then retry it, it works fine.
So there seems to be no general problems with routing, security groups or the like.
(!) It could even be a problem with the client, we only tested it with 1.0.20200513-1~20.04.2 on Ubuntu 20.4
We closed #135 anyway, as Wireguard can be used to access all clusters like this:

set up cluster
kubectl get nodes or so using the provided kubeconfig
SSH into the orchestrator (where the API runs) (e.g. ssh -i cluster_key<EMAIL_ADDRESS>From this server, you can hop into all the others using SSH (e.g. ssh worker-12, ssh-main-1)

[ ] DNS replacement on client

(This could also be a client issue, but should be further investigated.)
Details: We set up the Wireguard client to provide a DNS server so we can reach the cluster nodes by name. On my client (Ubuntu 20.4, 1.0.20200513-1~20.04.2) this leads to a change in /etc/resolv.conf in a way that the DNS server of the cluster (<IP_ADDRESS> = bastion host) is the new primary name server. This slows down the name resolving on my machine and leads to high latency while browsing the web. Maybe there is no way to prevent this (my knowledge is limited, sorry), but we should further investigate it.

[ ] IPTABLES
Details: We use iptables to set up the required routing etc. for the communication via wireguard. During the research in #135, some questions/ideas arose:
[ ] Are all rules really necessary? In one spike, the one NAT rule was sufficient -> investigate
[ ] Should we integrate the iptables setup in the wireguard server conf as PostUp, PreDown attributes? If these rules are only necessary for wireguard use, we should do this!

@backstreetkiwi This is relatively old. Is it still relevant and you'd still say it is medium priority?

@lfrancke I'd like to keep it, but lowest priority is okay for me.

@lfrancke I made up my mind. Now that we rely almost completely on mK8s and the wireguard/VPN stuff is outdated/disabled anyway, this issue can be closed


fix suggest context bug

fixed in other branch but without this one.

Thank you. I will have to look up if this has changed in the same way in ES 2.x as it did in ES 5.x (sometimes documentation != Java source). If it does, I will merge in the next release.

OK. I used the 2.4, and it is good for me.

I fixed this in the recent versions of both v3 and v5, which I'll publish later today.
Thanks for your support.


awslimitchecker: init at 12.0.0

Motivation for this change
https://github.com/jantman/awslimitchecker is script and python package to check your AWS service limits and usage.
~This PR as stands currently will not build, since it still has some missing dependencies, each to follow in their own PRs in a little while:~

[x] versionfinder
[x] onetimepass
[x] timecop

There is a small patch to awslimitchecker.version to use only the hard-coded version information, somewhat making the versionfinder dependency redundant, as otherwise we'd need a run-time dependency on pytest for versionfinder to behave correctly - I suspect there's a bug somewhere in between.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[X] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Please label for Hacktoberfest once accepted :pray:

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

1 package built:

awslimitchecker

Thanks @SuperSandro2000 ! 🎉


Add NAS KWS model (trained using dynamic augmentation)

PR changed to draft mode, awaiting training completion for v2 & v3 models with dynamic augmentation.

Also modified copyright texts for files generated by ai8xize.py (namely cnn.c, cnn.h, main.c, Makefile, and softmax.c), following @sihyung-maxim's comments in https://github.com/Analog-Devices-MSDK/msdk/pull/851 .
The PR is now marked as "Ready".


Allow user to override app name for NimOS client

User should be able to override app_name value during NimOSClient()

Merged the feature support:
https://github.com/hpe-storage/nimble-python-sdk/pull/40


Modify run conditions for nightly job to create test cycle and post in channel.

e2e is running smoothly along the nightly job (https://github.com/mattermost/desktop/actions/runs/7809764570/job/21302110903).

However, we need nightly to also create test execution cycles in zephyr.
This PR is to create different Zephyr folders and to enable nighly job to create test cycles.

Link to report in community

None

/update-branch

/update-branch


Change word count font size

📝 A short description of the changes

Increases word count font size

🔗 Link to the relevant story (or stories)

https://app.asana.com/0/1204861597377754/1204994500690569

:shipit: Deployment implications

None

✅ Checklist

[x] Features that cannot go live are behind a feature flag/env var or specify deploy date and open PR as draft
[x] I have checked that commit messages make sense and explain the reasoning for each change
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have squashed any unnecessary or part-finished commits

🖼 Screenshots (if appropriate - no PII/Prod data):

@TheDancingClown should this be on main not staging?


Allow renaming JS interop members

Today we silently ignore string in @JS() annotations on members. The JS member and the dart member must share the same name.
In the short term we should have a static error for this.
In the long term we should support renames. Support may be blocked on disallowing extending or implementing JS interop types: #37896

Dup of #24779 ?
Particularly see https://github.com/dart-lang/sdk/issues/24779#issuecomment-349013276 which will be awesome to address.

Marking as P2 for at least the static error for what is broken now.


textbox::set_accept is misbehaving with DEL key

Passed wchar_t argument is 46 which is the same for '.'. Allowing 46 to pass to enable DEL renders it possible to print dots in the field as well.
Version: Nana-1.5.4
textbox fAmountInput;
fAmountInput.create(fForm);
fAmountInput.multi_lines(false);
fAmountInput.set_accept([](wchar_t text){
    //Why dot character and DEL have the same code???
    return text == '\b' || text == 46 || iswdigit(static_cast<wint_t>(text));
});

At first I wanted to ask on the forum if this behavior is intentional and if there are other tools available to address that properly instead, but registration says that my email is invalid. Come on.

Thanks for reporting this issue! Fixed.


HTTPException message is not escaped

When an HTTPException is raised, and render_error() decide to return HTML, the exception message should be escaped to prevent XSS.
OWASP recommends it and Werkzeug does it.

Right, but how would the exception message cause XSS?
I'm not an expert, but I'm curious.

If the developer re-use user input in an exception message, Pulsar will create HTML from it. If the user input happens to be javascript, it will be executed in the client browser when the error page is displayed.


output window messy code

VSCode Version:1.12.1
OS Version:windows 10 enterprise

Steps to Reproduce:

Have you tried to change your code page settings in system console?

not yet，how to do it?thanks

it doesn't work.I change it to 936,still not work.

目测你用的中文吧？

是中文的，但是我切换成英文一样是乱码的。

换成nodejs试试

@NexxLuo what output channel is that?

@bpasero
I want to Configre Task Runer to browse html file in Chrome,but chrome not in  environment variable path, then find this.

Seems to be task related, moving to @dbaeumer to see if there is a duplicate already related to task output encoding.

Yes, dups #3550. This got already addressed with the new terminal runner.


Script annotations artifacts

Pull Request Checklist

[x] Fixes #717
[x] Tests added
[x] Documentation/examples added
[x] Good commit messages and/or PR title

Description of PR
Currently, the artifacts used as inputs to a script require duplication of the path when used, similarly to below
@script(inputs=Artifact(name="my-artifact", path="/tmp/file"))
def read_artifact():
    with open("/tmp/file") as a_file:
        print(a_file.read())

This PR adds support for using typing.Annotated for Artifact as inputs for scripts which allows to avoid duplication. It introduces Artifacts as Path and as Object.
For Path, we have
@script()
def read_artifact(an_artifact: Annotated[Path, Artifact(name="my-artifact", path=ARTIFACT_PATH)]) -> str:
    output = an_artifact.read_text()
    print(output)
    return output

and for the Object, we have
class MyArtifact(BaseModel):
    a = "a"
    b = "b"

@script()
def read_artifact(an_artifact: Annotated[MyArtifact, Artifact(name="my-artifact", path=ARTIFACT_PATH)]) -> str:
    output = an_artifact.a + an_artifact.b
    print(output)
    return output

We'll need to merge #708 first, and then you can rebase this branch to still merge to main. atm this PR includes all the #708 changes


Login doesnt work for HA2021.6

Describe the bug
After setting up the integration for the first time, a login error occurs
Debug logs
2021-07-01 23:57:32 DEBUG (MainThread) [skodaconnect.connection] VW-Group API token verified OK.
2021-07-01 23:57:32 DEBUG (MainThread) [skodaconnect.connection] Fetching vehicles associated with account
2021-07-01 23:57:32 DEBUG (MainThread) [skodaconnect.connection] HTTP GET "https://msg.volkswagen.de/fs-car/usermanagement/users/v1/skoda/CZ/vehicles"
2021-07-01 23:57:32 INFO (MainThread) [custom_components.hacs] Restore started
2021-07-01 23:57:32 INFO (MainThread) [custom_components.hacs] Restore done
2021-07-01 23:57:32 INFO (MainThread) [custom_components.hacs] Setup task HacsSetupTask.SENSOR
2021-07-01 23:57:32 INFO (MainThread) [custom_components.hacs] Stage changed: HacsStage.WAITING
2021-07-01 23:57:32 INFO (MainThread) [custom_components.hacs] Setup complete, waiting for Home Assistant before startup tasks starts
2021-07-01 23:57:32 INFO (MainThread) [custom_components.hacs] HACS is enabled
2021-07-01 23:57:32 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.hacs
2021-07-01 23:57:32 DEBUG (MainThread) [skodaconnect.connection] Request for "https://msg.volkswagen.de/fs-car/usermanagement/users/v1/skoda/CZ/vehicles" returned with status code [200]
2021-07-01 23:57:32 ERROR (MainThread) [skodaconnect.connection] Login failed for skoda account, 'NoneType' object has no attribute 'get'
2021-07-01 23:57:32 WARNING (MainThread) [custom_components.skodaconnect] Could not login to Skoda Connect, please check your credentials and verify that the service is working
2021-07-01 23:57:32 INFO (MainThread) [homeassistant.setup] Setup of domain skodaconnect took 3.6 seconds
2021-07-01 23:57:32 ERROR (MainThread) [homeassistant.setup] Setup failed for skodaconnect: Integration failed to initialize.
Installation:

Home Assistant variant: Hass OS 5.13
Python version: Whatever comes with Hass OS

Additional context
This is my first attempt to get this working.
The skoda-connect.com portal shows my Enyaq iV 80, and the app does as well.
I'm not afraid of some debugging or manual python calls, just wanting to get this to work :dancing_men:

Some more debug logs from HA (response debugging)
2021-07-02 00:06:24 DEBUG (MainThread) [skodaconnect.connection] Got token access_token
2021-07-02 00:06:24 DEBUG (MainThread) [skodaconnect.connection] Got token token_type
2021-07-02 00:06:24 DEBUG (MainThread) [skodaconnect.connection] Got token refresh_token
2021-07-02 00:06:24 DEBUG (MainThread) [skodaconnect.connection] Got token expires_in
2021-07-02 00:06:24 DEBUG (MainThread) [skodaconnect.connection] Got token scope
2021-07-02 00:06:24 DEBUG (MainThread) [skodaconnect.connection] VW-Group API token verified OK.
2021-07-02 00:06:24 DEBUG (MainThread) [skodaconnect.connection] Fetching vehicles associated with account
2021-07-02 00:06:24 DEBUG (MainThread) [skodaconnect.connection] HTTP GET "https://msg.volkswagen.de/fs-car/usermanagement/users/v1/skoda/CZ/vehicles"
2021-07-02 00:06:24 DEBUG (MainThread) [skodaconnect.connection] Request for "https://msg.volkswagen.de/fs-car/usermanagement/users/v1/skoda/CZ/vehicles" returned with status code [200], response: {'userVehicles': None}
2021-07-02 00:06:24 ERROR (MainThread) [skodaconnect.connection] Login failed for skoda account, 'NoneType' object has no attribute 'get'
2021-07-02 00:06:24 WARNING (MainThread) [custom_components.skodaconnect] Could not login to Skoda Connect, please check your credentials and verify that the service is working
2021-07-02 00:06:24 INFO (MainThread) [homeassistant.setup] Setup of domain skodaconnect took 3.0 seconds
2021-07-02 00:06:24 ERROR (MainThread) [homeassistant.setup] Setup failed for skodaconnect: Integration failed to initialize.

Some more debug logs from HA (response debugging)
2021-07-02 00:06:24 DEBUG (MainThread) [skodaconnect.connection] Got token access_token
2021-07-02 00:06:24 DEBUG (MainThread) [skodaconnect.connection] Got token token_type
2021-07-02 00:06:24 DEBUG (MainThread) [skodaconnect.connection] Got token refresh_token
2021-07-02 00:06:24 DEBUG (MainThread) [skodaconnect.connection] Got token expires_in
2021-07-02 00:06:24 DEBUG (MainThread) [skodaconnect.connection] Got token scope
2021-07-02 00:06:24 DEBUG (MainThread) [skodaconnect.connection] VW-Group API token verified OK.
2021-07-02 00:06:24 DEBUG (MainThread) [skodaconnect.connection] Fetching vehicles associated with account
2021-07-02 00:06:24 DEBUG (MainThread) [skodaconnect.connection] HTTP GET "https://msg.volkswagen.de/fs-car/usermanagement/users/v1/skoda/CZ/vehicles"
2021-07-02 00:06:24 DEBUG (MainThread) [skodaconnect.connection] Request for "https://msg.volkswagen.de/fs-car/usermanagement/users/v1/skoda/CZ/vehicles" returned with status code [200], response: {'userVehicles': None}
2021-07-02 00:06:24 ERROR (MainThread) [skodaconnect.connection] Login failed for skoda account, 'NoneType' object has no attribute 'get'
2021-07-02 00:06:24 WARNING (MainThread) [custom_components.skodaconnect] Could not login to Skoda Connect, please check your credentials and verify that the service is working
2021-07-02 00:06:24 INFO (MainThread) [homeassistant.setup] Setup of domain skodaconnect took 3.0 seconds
2021-07-02 00:06:24 ERROR (MainThread) [homeassistant.setup] Setup failed for skodaconnect: Integration failed to initialize.

Which version of the library and integration are you using? The library version should be reported on startup.

I'm using 1.0.38, installed via HACS. Will get the exact library versions to you in a little bit

I'm using 1.0.38, installed via HACS. Will get the exact library versions to you in a little bit

Enyaq iV isn't supported in 1.0.38, from 1.0.40-RC2 and onwards.
Install latest RC instead and make sure that library version 1.0.42 is installed.

I updated to 1.0.40-rc5 (given the open issue #43 in 1.0.42), and am seeing the vehicle in debug logs now, thanks!
Will upgrade to 1.0.42 to see if i can reproduce #43 once I get my lovelace card done :+1:

I updated to 1.0.40-rc5 (given the open issue #43 in 1.0.42), and am seeing the vehicle in debug logs now, thanks!
Will upgrade to 1.0.42 to see if i can reproduce #43 once I get my lovelace card done 👍

#43 is related to yaml config not getting imported to the config flow and/or mismatched integration/lib versions. Since yours is a new setup you shouldn't have any issues starting at latest.


Report kernels with no arguments in the descriptor map?

From https://github.com/kpet/clvk/issues/23:

clvk currently relies on the descriptor map obtained from clspv to ascertain the existence of a kernel in a given program. Kernels with no arguments aren't described at all in the descriptor map and thus can't be used (kernel creation will fail).

How would you feel about adding a new kernelnoargs,<name> type of entry to the descriptor map? This would arguably be an abuse of the descriptor map but one that doesn't feel too bad. Alternatively, clvk could parse the SPIR-V module to get the list of entrypoints but that's one more dependency on SPIRV-Tools that I'd rather avoid if possible.

Maybe better would be to add a list of entry points like:
entry_point,foo
entry_point,bar

Or possibly adding some depth to the descriptor map to have all kernel entries grouped under a kernel structure that streams like:
kernel_decl,foo
kernel,foo,arg,blah,...
...
kernel_decl,bar
...

The first is much simpler than the second.

I think I'd rather keep the descriptor map unordered as it's easier to parse. Since we're repeating the kernel name in existing entries, there's no strict need to group the entries apart from making this a bit more readable. Grouping would be useful to report other kernel-related information without repeating the name of the kernel though. I think I'd want to use the descriptor map to report the reqd_work_group_size as well for example but that can be done easily using kernel,<name>,reqd_work_group_size,<val>.
Agree that adding a parallel list of all kernels is cleaner. I'll have a stab at that and see what it looks like.


[App Config] Migrate to Bicep

And update API versions.
Live tests run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4070946&view=results

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


Exports symbols of cdylib dependencies

Problem
When a cdylib has another cdylib as a dependency, the resulting library contains the symbols of both packages.
E.g. when building a project (see https://github.com/ensc/cargo-13978) like
|-- ext/foo
|   |-- Cargo.toml
|   |   [lib]
|   |   crate-type = ["cdylib", "rlib"]
|   |
|   `-- src/lib.rs
|       #[no_mangle]
|       extern "C" fn foo_func() -> u32 { func() }
|
|-- Cargo.toml
|   [lib]
|   crate-type = ["cdylib", "rlib"]
|
|   [dependencies]
|   foo = { path = "ext/foo" }
|
`-- src/lib.rs
    #[no_mangle]
    extern "C" fn bar_func() -> u32 { func() }

the resulting (outer) library contains
$ nm -D libbar.so | grep ' T '
0000000000011920 T bar_func
00000000000119b0 T foo_func

The inner library (which can be installed separately) contains
$ nm -D libfoo.so | grep ' T '
0000000000011800 T foo_func

foo_func should be only in libfoo.so.
Version
cargo 1.80.0-nightly (a8d72c675 2024-05-24)
release: 1.80.0-nightly
commit-hash: a8d72c675ee52dd57f0d8f2bae6655913c15b2fb
commit-date: 2024-05-24
host: x86_64-unknown-linux-gnu
libgit2: 1.7.2 (sys:0.18.3 vendored)
libcurl: 8.6.0-DEV (sys:0.4.72+curl-8.6.0 vendored ssl:OpenSSL/1.1.1w)
ssl: OpenSSL 1.1.1w  11 Sep 2023
os: Fedora 40.0.0 (Forty) [64-bit]

I believe this is expected behavior. The bar package refers to foo::func(), and thus must pull in the foo rlib as a static library. Rust does not support dynamically loading cdylibs automatically.
You can use dylib to dynamically link Rust projects, or use a library like libloading to dynamically load a cdylib.

I do not think this is related to loading cdylib from rust.  I want to use it like
graph LR;
  c_app[C application]
  libfoo[libfoo.so]
  libbar[libbar.so]
  libbaz[libbaz.so]
  c_app -- foo_func() --> libfoo;
  c_app -- bar_func() --> libbar;
  c_app -- baz_func() --> libbaz;
  libbar -. foo::func() .-> libfoo;
  libbaz -. foo::func() .-> libfoo;

(to avoid an easy solution like "use only libbar.so", I added a libbaz.so which is similarly to libbar.so)
It would be nice when the rust internal linking between libbar.so and libfoo.so would work (I tried dylib but this breaks somehow when building tests; perhaps LTO related and another issue).  For now, it is ok when libbar.so contains the statically linked rust code of libfoo.so.
But the problem is that the C library libbar.so (and libbaz.so) contains the symbols of libfoo.so.
cdylib libraries should be created in a way that extern "C" symbols of dependent cdylib are exported as hidden (in C __attribute__((__visibility__(hidden))) or the corresponding link flag).  When dependency is a pure rlib, they should be public.


Center the visit place place holder

cc @jdolkowski . This ticket in the progress, i will add some more work onto it.

cc @jdolkowski . This ticket in the progress, i will add some more work onto it.

Is this PR still in progress or can be merged?

this can be merged.


Use high DPI pixmaps

Using app.setAttribute(Qt.AA_UseHighDpiPixmaps), which only exists with PyQt5.

Seems good to me, merging :-)


Using statically compiled openssl libs in applications

Discussed in https://github.com/openssl/openssl/discussions/21639

Originally posted by casidapulak August  3, 2023
Hello,
I have a c++ application App.exe which loads 2 dlls:

A.dll is loaded using implicit linking at the start of the program. It loads openssl dlls dynamically. All the openssl dlls(including fips.dll and legacy.dll) are present in the folder in which App.exe and A.dll are present.
B.dll is loaded using explicit linking on demand basis using LoadLibrary. It is compiled using static lib files of openssl (B.dll has its own openssl settings like different providers etc. That is the reason it had to be done like this).

My question is if openssl search path needs to be set in B.dll to look for legacy.dll and fips.dll that are part of static lib compilation. Currently I have not done that and my application seems to work fine and B.dll seems to use legacy.dll and fips.dll which are part of dynamic lib compilation of openssl ( but if I check in dependency walker legacy.dll seems to have a dependency on the openssl dlls)
Thanks in advance!

The search path will have to be set for fips.dll.  It cannot be included statically.
It is possible to include legacy.dll statically: https://github.com/openssl/openssl/discussions/21410


ARTEMIS-2191 Makes PostOfficeImpl::route common paths inlineable

If you are curious to try it :P
I have included all the changes of https://github.com/apache/activemq-artemis/pull/2449

@franz1981 I have merged this.. as I will review it on my branch.
I will save your commit as a separate branch here.. new-amqp-franz.. and keep your commit on my branch as well.. until I merge everything.


Prepare release of GAE-storage v0.7.0

Update README.md.
Fix emulator startup script crossplatformness.

@armiol PTAL

Current coverage is 88.69% (diff: 100%)

Merging #17 into master will not change coverage

@@             master        #17   diff @@
==========================================
  Files            13         13
  Lines           628        628
  Methods           0          0
  Messages          0          0
  Branches         69         69
==========================================
  Hits            557        557
  Misses           45         45
  Partials         26         26

Powered by Codecov. Last update f60f410...2f8fc0a

@armiol PTAL at the latest changes

@armiol PTAL again


Speed up + streamline prompt template rendering runtime

In some situations (for example, N-shot with very large N) we currently spend an annoying amount of time redundantly rendering our Jinja2 prompt template strings.
There are two ways we can significantly cut down on this runtime, without impacting code complexity significantly (e.g., no multiprocessing when generating requests / Instances, etc.)

At the start, render doc_to_target, doc_to_text, doc_to_choice once each for every doc, and cache that result so that we don't need to repeatedly render our prompts when we want to call these methods multiple times for every test instance.
cache these attributes, or the actual Instance objects, created when a task is run once, so that we can skip this whole step's processing in future. The easiest way to do so would be to leverage HF datasets' dataset.map() function which can cache results based on pickling a function. However, we'd want to be extremely cautious of whether this might create weird bugs when someone is trying to change + rerun a task but the cached intermediate input objects get silently used, preventing them from seeing the expected changes in behavior when they change code.

Change 1 should suffice for some pretty nice QoL improvements.
We should however also make sure this doesn't negatively affect runtime when we'd have to perform it on a large train set that we're drawing few-shot examples from.

I'll probably take on change 1 sooner rather than later--but if no PR can be seen that references this issue yet, then anyone interested can comment here volunteering to add it too!

Hi ! Happy to help if you have any question regarding datasets hashing for map() functions. :)
FYI it dumps the function using dill (an alternative to pickle that can handle e.g. lambda functions) and recursive=True to also take into account the globals used in the function. The hash is computed using the dill dump to build the fingerprint of the resulting dataset and store it in the cache, see https://huggingface.co/docs/datasets/v2.16.1/en/about_cache#fingerprint
Though you can override this mechanism by passing your own new_fingerprint= to map() but in this case you want to make sure that the fingerprint is not the same whenever a processing parameter changes.


Facechain FACT - comfyui?

Hello,
is there a way to use the face adapter in ComfyUI?
Thanks.

The feature is not being developed at the moment due to lack of manpower, and we welcome community members to take on its development.


Got "Unexpected semihosting command" when running embedded-test on NUCLEO-H743ZI

Describe the bug
Running an embedded-test on a NUCLEO-H743ZI with probe-rs (0.24.0 and master 5800d517d97caa61763468c56a7f31f4ab104c71) reports "Error: Unexpected semihosting command".
Evaluation of the trace (--log-file) did indicate, that in test_run_mode.rs/list_tests() did receive the GetCommandLine request. From the Error I assume, that somehow the operation of the following SemihostingCommand was set to 0.
To Reproduce
Steps to reproduce the behavior:

Install probe-rs 0.24.0 (or 5800d517d97caa61763468c56a7f31f4ab104c71)
Connect NUCLEO-H743ZI
Use embedded-test to create a test binary and run it via probe-rs. You can run cargo test --example_test in this example project. Or probe-rs run --chip STM32H743ZITx --list <ELF>

Expected behavior
Running of the tests and reporting failure/success.
Stacktrace
This is the output of probe-rs run --chip STM32H743ZITx <ELF>, after successful programming:
Frame 0: syscall_readonly @ 0x080085fa
       ~\.cargo\registry\src\index.crates.io-6f17d22bba15001f\semihosting-0.1.10\src\sys\arm_compat\syscall/arm.rs:88:9
Frame 1: sys_exit_extended @ 0x080086cc
       ~\.cargo\registry\src\index.crates.io-6f17d22bba15001f\semihosting-0.1.10\src\sys\arm_compat/mod.rs:198:2
Frame 2: <unknown function @ 0x00020026> @ 0x00020026
Error: Unexpected semihosting command Unknown(UnknownCommandDetails { operation: 0, parameter: 536996204 }) cmdline_requested: true

Desktop (please complete the following information):

Windows 10

Additional context
The problem disappears when probe-rs is downgraded to 204a9f7c30b7196b0d85eecf5782c772a49b1254 of pull request #2292. The following two commits (a4789d542805330f55a20a08451c8b6af94fc34e and 3b6a3b189206f57a10fc3c460419ca5fe9dc2fc1) seem to cause the problem. When these are reverted on current master (https://github.com/weinmann-emt/probe-rs/tree/fix-unexpected-semihosting-command), probe-rs testing works as expected.
In the pull request, it is mentioned that Xtensa and RISC-V targets were tested, probably this bug exists only for cortex-m?

hi @mahu-wm ,
sorry we didn't reach out earlier. Can you check whether the issue is fixed on the master branch?

Thanks, yes, the issue is fixed with the current master (c3a767bdc0827f3b4c5db6d6628c2aa7d7730023)


Notebook import error

Description
Seems that simply importing swmmanywhere from the docs directory causes a range of collection errors during testing.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 85.00%. Comparing base (b4d628e) to head (ca18b9c).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #320   +/-   ##
=======================================
  Coverage   85.00%   85.00%
=======================================
  Files          22       22
  Lines        2134     2134
  Branches      274      274
=======================================
  Hits         1814     1814
  Misses        236      236
  Partials       84       84

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


Affiliates and affiliate users

Also, fix isort build, which will fail I suppose (because of a single empty line after the imports in affiliate.py)


How to convert final.zip to final.pt

I removed final.pt.
How can I convert final.zip to final.pt?

Probably not possible


How to install?

Hello,
You can provide readme for installation?
How is kafka connector?
Best Regards

This is just a prototype application to demonstrate how someone could implement their own setup.


mysql batch insert ,return wrong id

mysql batch insert ,return wrong id;
xml code:
<insert id="insertxxxBatch" useGeneratedKeys="true" keyProperty="id" parameterType="java.util.List">
    insert into base_order(
    	ID,
    	BASE_ORDER_NO,
    	CREATE_TIME,
    	SALES_CHANNELS_ID,
    	ProductID,
    	PHONE)
        values
     <foreach collection="list" item="item" index="index" separator=",">
        (#{item.id,jdbcType=INTEGER},
        #{item.baseOrderNo,jdbcType=VARCHAR},
        #{item.createTime,jdbcType=TIMESTAMP},
        #{item.salesChannelsId,jdbcType=INTEGER},
        #{item.productid,jdbcType=INTEGER},
        #{item.phone,jdbcType=VARCHAR}
        )
   </foreach>

insert corrrect, but return the wrong id value.
db data:
ID
1031663
1031666
return value:
ID
1031663
1031664

MyBatis version
3.3.1
Database vendor and version
Test case or example project
Steps to reproduce
Expected result
Actual result

mysql ID增长步长是2，但是返回的id确实按+1的方式返回的，这是为什么呢？

Could you provide reproduce project on GitHub ?

ID is auto increment,why do you set the id?

That's not the problem with MyBatis, but your configure file with you database. You even don't provide the version of the database which you use..,,
If I were you, I will check whether the configuration worked or not?
MyBatis works well, check your code and configuration of database again.


fetchHex: remove pname prefix

Projects like mix2nix and my own project, deps_nix, are collecting a growing number of workarounds for packages that depend on the working directory of a build to have the same name as the package.
See for example: https://github.com/ydlr/mix2nix/commit/da2ebc2c63b18c4967e176468e2717f4a07d6bf0
Attempts have been made to get upstream maintainers to change this dependency, but it's a bit of a cat-and-mouse game. I gave up on this attempt, for example, because it was tricky to fix.
This change makes the pname of Hex packages equal the package name, so that such workarounds aren't necessary.
Description of changes

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

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

15 packages built:

akkoma
elixir-ls
elvis-erlang
erlang-ls
erlang_27-rc3
erlfmt
ex_doc
lexical
lfe (lfe_2_1)
livebook
mobilizon
plausible
pleroma
rebar3
sonic-pi

LGTM, but I'll defer the merge decision to someone more versed in this than me
@happysalada

Thanks!


Bluetooth: Host: l2cap: disconnect when PDU > MPS

The Bluetooth spec states that a K-frame exceeding the device's MPS should trigger a disconnection of the channel.
Fixes two PTS tests that verify this behavior:
L2CAP/LE/CFC/BV-27-C
L2CAP/ECFC/BV-34-C
The current behavior is a silent truncation, which is not very nice for the user, even if the spec would allow it.
Fixes #52228 and #51174.

#AutoPTS run zephyr  L2CAP/LE/CFC/BV-27-C  L2CAP/LE/CFC/BV-27-C

@sjanc could you please trigger a PTS run on this PR?


[flutter_math_fork] Error: Too few positional arguments: 4 required, 3 given

Sorry to polute this repo with a bug on another one, but it looks like the fork you have for flutter_math_fork doesn't allow creating new issues there.
Looks like with the latest version of Flutter, this fork is broken, which in return broke the package flutter_html that is using that fork as a dependency: https://github.com/Sub6Resources/flutter_html/issues/732
The issue it self is that when trying to build the app, we get this error:
 ../../../.pub-cache/hosted/pub.dartlang.org/flutter_math_fork-0.3.3/lib/src/widgets/selection/handle_overlay.dart:197:58: Error: Too few positional arguments: 4 required, 3 given.
                  child: widget.selectionControls.buildHandle(

So Hopefully since you are under the same organization you can let the devs on that fork know about this issue?
Let me know if there is a better place for this.
Thank you!

I created a PR here as well: https://github.com/simpleclub-extended/flutter_math/pull/3

Let's close this issue as it's already fixed in flutter_math_fork :)

Let's close this issue as it's already fixed in flutter_math_fork :)

Thank you for relaying!


[DO NOT MERGE] Updating copy for bindings

Updating copy. Not to be merged until signed off from UX team.

I created a new cleaner PR for it: #112


Google speech API response timeout

Hi,
For certain audios, google speech API doesn't give a proper response. The request is getting timed out.
To reproduce the issue you can pass an empty audio. Is there any workaround for it?
Thanks

Could you show the code you're running, and version you're using? It will help us reproduce the issue, and ultimately diagnose the problem :)

function asyncRecognize(filename, encoding, sampleRateHertz, languageCode) {
// [START speech_async_recognize]
// Imports the Google Cloud client library
const speech = require('@google-cloud/speech');
const fs = require('fs');
// Creates a client
const client = new speech.SpeechClient();
const config = {
encoding: 'FLAC',
sampleRateHertz: 16000,
languageCode: 'en-IN',
};
const audio = {
content: fs.readFileSync(filename).toString('base64'), // file is .flac
};
const request = {
config: config,
audio: audio,
};
// Detects speech in the audio file. This creates a recognition job that you
// can wait for now, or get its result later.
client
.longRunningRecognize(request)
.then(data => {
const response = data[0];
const operation = response;
// Get a Promise representation of the final result of the job
return operation.promise();
})
.then(data => {
const response = data[0];
const transcription = response.results
.map(result => result.alternatives[0].transcript)
.join('\n');
console.log(Transcription: ${transcription});
})
.catch(err => {
console.error('ERROR:', err);
});
// [END speech_async_recognize]
}
I am using this function from samples/recognize.js in your repository
Google API version - @google-cloud/speech": "^1.0.1"
you can pass any audio with no utterances/words. the request will timeout.
Let me know if you need any other details.

I have similar issue too.
In my case with using event emitter pattern, progress events was emitted twice but no complete events was emitted.
(so the promise chain won't be either resolved or rejected.)
The REST API responses to the request was bellow.
(from parameters of callback to progress event.)
{
  "result": null,
  "name": "5622465609457788982",
  "metadata": {
    "startTime": {
      "seconds": "1522044952",
      "nanos": 558720000
    },
    "lastUpdateTime": {
      "seconds": "1522044953",
      "nanos": 111336000
    }
  },
  "done": false,
  "error": null,
  "response": null
}

{
  "result": null,
  "name": "5622465609457788982",
  "metadata": {
    "progressPercent": 100,
    "startTime": {
      "seconds": "1522044952",
      "nanos": 558720000
    },
    "lastUpdateTime": {
      "seconds": "1522044960",
      "nanos": 187001000
    }
  },
  "done": true,
  "error": null,
  "response": null
}

If done is true,  either error or response must be available.
https://cloud.google.com/speech/reference/rest/v1/operations
So I suspect Speech API has problem that it doesn't build response object in case of "no word audio".

I have another workaround.
client.longRunningRecognize(request)
  .then(responses => {
    const operation = responses[0]

    const errorHandler = err => {
      throw(err)
    }
    const completeHandler = longRRResponse => {
      // build text
      const text = longRRResponse.results.map((result) => {
        const alternative = result.alternatives[0]
        return `${alternative.transcript}\n`
      }).join('\n')
      console.log(text)
    }
    const progressHandler = (metadata, apiResponse) => {
      if (apiResponse.done && !apiResponse.response) {
        // progress with `done: true` means request completion
        operation.removeListener('error', errorHandler)
        operation.removeListener('complete', completeHandler)
        operation.removeListener('progress', progressHandler)
        console.log('(no text included in this audio)')
      }
    }
    operation.on('error', errorHandler)
    operation.on('complete', completeHandler)
    operation.on('progress', progressHandler)
  })
  .catch(err => {
    console.error(err)
  })

The point is progressHandler.
When all event listeners are removed, operation loop will be finished.
https://github.com/googleapis/gax-nodejs/blob/v0.16.0/lib/longrunning.js#L346-L348

Nice, it would stop even before waiting for a timeout. You might want to return an Error in the first promise without modifying nor adding error or complete handlers:
  client
    .longRunningRecognize(request)
    .then(data => {
      const response = data[0];
      const operation = response;

      operation.on('progress', function(metadata, apiResponse) {
        if (apiResponse.done && !apiResponse.response) {
          // progress with `done: true` means request completion
          throw new Error('No text included in this audio');
        }
      });

      // Get a Promise representation of the final result of the job
      return operation.promise();
    })
    .then(data => {
      const response = data[0];
      const transcription = response.results
        .map(result => result.alternatives[0].transcript)
        .join('\n');
      console.log(`Transcription: ${transcription}`);
    })
    .catch(err => {
      console.error('ERROR:', err);
    });

Anyhow, the issue should probably be fixed in https://github.com/googleapis/gax-nodejs, or on the server side. A similar issue there about how progress events are handled has been filed there : https://github.com/googleapis/gax-nodejs/issues/192

@alexander-fenster could you loop in someone from the Speech team?:

If done is true, either error or response must be available.
cloud.google.com/speech/reference/rest/v1/operations
So I suspect Speech API has problem that it doesn't build response object in case of "no word audio".
- @ottijp https://github.com/googleapis/nodejs-speech/issues/45#issuecomment-376060147

@stephenplusplus I've just asked Speech team.

Here's a sample audio file: https://nofile.io/f/7bCgmbZ3Fxg/15-seconds-mono.flac

Funny thing is that if you check the operation after a while, it says 100 complete and done = true
curl https://speech.googleapis.com/v1/operations/{NAME}?key={API_KEY}
where NAME is included on the first Promise response.
So basically you can check if its finished, but you never get the transcription :__)

@alexander-fenster did anyone ever get back to you on this?

Oh, it looks they asked for a sample file and that's where I dropped the ball. @crwilcox can you follow up here please?

Hey there! I'm running into this issue with this sample file that's never resolving with a promise:
https://drive.google.com/file/d/1TFJ1A8J5Y2EeNYU-COQr2kJvy4vopE6X/view?usp=sharing
Here's the code that I'm using:
const config = {
  encoding: 'FLAC',
  languageCode: 'es-US',
  model: 'default',
};

const audio = {
  uri: 'URL_TO_FILE_IN_GCS',
};

const request = {
  config: config,
  audio: audio,
};

const [operation] = await speech.longRunningRecognize(request);
console.log(config);
console.log(operation);
setInterval(() => {
  operation.getOperation().then(data => {
    console.log('getOperation');
    console.log(data);
  });
}, 10000);
const [response] = await operation.promise();
console.log(response);

It seems like it's because the result we get back is null: this gets console.log'd by the setInterval
[ null,
  LongRunningRecognizeMetadata {
    progressPercent: 100,
    startTime: Timestamp { seconds: [Object], nanos: 60959000 },
    lastUpdateTime: Timestamp { seconds: [Object], nanos: 694858000 } },
  { result: null,
    name: '1256175250915529069',
    metadata:
     { typeUrl: 'type.googleapis.com/google.cloud.speech.v1p1beta1.LongRunningRe
cognizeMetadata',
       value: <Buffer 08 64 12 0b 08 a7 8e fe d8 05 10 98 d2 88 1d 1a 0c 08 aa 8
e fe d8 05 10 90 e2 aa cb 02> },
    done: true,
    error: null,
    response: null } ]

There hasn't been an update on this issue, if there is any updates, please feel encouraged to reopen this issue.

I'm working on something with Google speech API and I found the same Issue, my way to solve was to send an emit to the error listener  in that way break /stop the promise;
 operation.on('progress', (metadata, apiResponse) => {
        if (apiResponse.done && !apiResponse.response) {
          operation.emit('error');
        }
    });


Can't set type="button" when using Button with a label.

Bug Report
Steps
Create a Button component with a label and type="button"
Expected Result
The <button /> element should have type="button"
Actual Result
The attribute is set on the div around it where it's useless, so the button's onClick is triggered when pressing enter in some form field that submits the form (default type for a button is submit)
Version
2.0.4
Testcase
https://codesandbox.io/s/semantic-ui-react-forked-jx0wi

Thanks for the quick fix!

@ThiefMaster the next release should happen on this/next week. If you're in rush I suggest to use patch-patch 🐱


fix: build: image repo protection test

Description
Follow-up PR on https://github.com/redhat-appstudio/e2e-tests/pull/161. Changes in that PR caused the "image repo protection" test flakey, because the new pipelinerun cleanup function conflicts with component cleanup function (which I removed in this PR)
Issue ticket number and link
Type of change

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
# 10 clean test runs, no failure
for i in {1..10}; do echo $i && ginkgo --focus="Creating a component with a specific container image URL" --progress -v ./cmd -- --config-suites=/Users/psturc/work/redhat-appstudio/e2e-tests/tests/e2e-demos/config/default.yaml > /dev/null || echo ERROR; done

Checklist:

[X] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have updated labels (if needed)

/test redhat-appstudio-e2e


Fixed parameter in system manager sample code

The call was using column_type="Super" but the parameter is actually super=True.

Thanks!


Update json.lua

add a dummy key { _ = false } to force empty table to be encoded to as an object
fix for issue #23

Very dirty.


github education section

Hi,
This pull request is a proposal to have a "GitHub Education" section added.
Thanks for the repo

@lakuapik can you look at this. I think it's nice. Waiting for your permission to merge

Wow, thanks for this addition. Sorry for late response.


Bundle with wis2box

[ ] Rewrite STA provider so that wis2box map/data ui can read STA endpoint data (use USGS as test case)
[ ] Make new GUI to create wis2box data mapping for csv data (3 csvs: 1: stations name/location. 2: observed properoties/units (basically everything in wis2box topic hiearchy. 3: Observations/results
[ ] Make csv/data push GUI be able to go to arbtrary sta endpoint, not just one on same docker network.

Make a written and/or diagram of your thoughts @webb-ben

https://docs.google.com/document/d/18-AwPpLehJWyalUPgJAlERa-jb8hQCjlONRj8u6oEDQ/edit
https://docs.google.com/drawings/d/1dY-yfiBSesadlIukkFLtGuRlmr52n3-OsuEnPtM5ykI/edit

https://github.com/wmo-im/wis2box-api

Example data: https://catalog.newmexicowaterdata.org/dataset/seven-rivers-monitoring-network

progress Sep 21, 2022
added sensorthings docker-compose linked to wis2box mqtt provider


[Open Beta] Triage bugs when reported by open beta participants

As a team, we should triage bugs as they occur during the open beta. We can use this issue to collate them, and then we can create tickets and assign them based on priority and dev availability.

We've got some initial bugs are being squashed, but generally, a really smooth launch! 🥳