Extend do_nd with option to perform "Parallel sweeps"

In the process refactor Sweeps and Measurements to be a bit more modular
closes #4366 by refactoring the setpoint logic to generate the input type.

[x] More robust parsing of Parameters (see todos in code)
[x] Document
[x] More complete tests (there should be a test that this can work around a parameterwithsetpoints (and perhaps multi/arrayparameter)

Should add a test that we get a resonable error message if there are no measurement parameters
def test_dond_without_measurement_params():
    a = ManualParameter("a", initial_value=0)

    with pytest.raises(
        ValueError
    ):
        dond(ArraySweep(a, [1, 2, 3]))

See #4366

bors merge


Unable to build docs locally.

Followed https://github.com/envoyproxy/envoy/tree/main/docs#building-documentation-locally.
Command ./docs/build.sh  throw exception
INFO: Build completed successfully, 1 total action
Envoy source must either be located at /source, or ENVOY_SRCDIR env var must be set
Traceback (most recent call last):
  File "/home/necuser/.cache/bazel/_bazel_necuser/213e71b2d087549d893f7fdc744ab64d/execroot/envoy/bazel-out/k8-fastbuild/bin/tools/extensions/generate_extension_rst.runfiles/envoy/tools/extensions/generate_extension_rst.py", line 35, in <module>
    subprocess.run("tools/extensions/generate_extension_db".split(), check=True)
  File "/usr/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)

CC @phlax

hmm - as a workaround for now you can do
export `ENVOY_SRCDIR=$(pwd)
./docs/build.sh

@phlax Thanks. Should we mention the same in https://github.com/envoyproxy/envoy/tree/main/docs#building-documentation-locally as of now?

I think the error message is pretty clear but please feel free to update the link above.


Styling of Login Page to Accommodate all screen sizes down to 320px

Co-authored-by: Secoya Wood<EMAIL_ADDRESS>Co-authored-by: Dylan Rinella<EMAIL_ADDRESS>Description
The login page needed to be adjusted to be responsive at all screen sizes. We did some short research to find out that 320px is the smallest screen size relevant to the industry standard. It is essential for this app to accessible on a mobile phone or tablet, and this ensures in the future that the layout of the login page is polished for those experiences. In order to solve this problem, we had to identify the different components and css classes needed to adequately display the login page on all relevant screen sizes.
Trello Card
Loom
Fixes # (issue)
Makes the login page responsive at all relevant screen sizes, down to 320px
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] This change requires a documentation update

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have removed unnecessary comments/console logs from my code
[ ] I have made corresponding changes to the documentation if necessary (optional)
[x] My changes generate no new warnings
[x] I have checked my code and corrected any misspellings
[x] No duplicate code left within changed files
[x] Size of pull request kept to a minimum
[x] Pull request description clearly describes changes made & motivations for said changes

Excellent job with your PR description. You clearly explained the necessity of this fix and showed that you guys took the time to do further research on it to ensure that you came up with the best solution. The only issue is that your loom video is linked into the github PR, rather than to the actual loom video. Maybe just double check that all your links are working in the future.

This was a mistake on my part, I needed to have left this as a draft pull request as to not alert anyone to review this PR. I have since posted the loom video I intended to add a little while after the PR was opened!

The code looks okay! I think there are some things I am unsure about. There are media queries for the sizes 322, 426, 450, 500, and 535, each of which have very little code in them. Would it be possible to start at 322 and then move to 426 and then say 500 or 535 and then have things scale using flexbox? Lastly, is there a reason they are not in order?

Thank you for your comment! The media queries in this code are nested within the relevant components to which they apply! This can definitely be confusing, but at this time I am not sure how to best refactor this code, and this would be something that can be done at a future date. The code I added is consistent with the original style the code was made with, so that was my approach!


Removing unnecessary classes from create dialog template

From this commit.

Frontend tests were OK :+1: (details)


LEAN-3961

1- added some new sections that were used by the import but not available in the api. (abstract-teaser  - floating-element - endnotes)
2- refactored the categories to support the new type in https://github.com/Atypon-OpenSource/manuscripts-transform/pull/158
3- removed the config route we had for section categories, section categories are now served through templates. To avoid repeating the section category array inside template files, I'm mapping the section-categories and their values when we initialize the templates

I made some changes based on our last call, we'll now have a default config path; presumably data, if there's no config path we'll default to the data path.


Count of # molecules, # of tags on main page

The main page should have some count like "Search by name, InChI, category out of X molecules in Y categories."
This way, as the database grows, people immediately see that the site refreshes.

Maybe even a "Last updated" tag?

Good idea. Maybe "last updated" goes into the footer.

Fixed with commit cd845e3ea64303c9cf76ae531cdbcae11c690439


\zcref should display the name of unnumbered objects

The following MCE points out that \zcref doesn't display the name of unnumbered objects.
\documentclass{article}
\usepackage{amsthm}
\usepackage{zref-clever}

\newtheorem{theorem}{Theorem}
\newtheorem*{lemma}{Lemma}

\begin{document}
\begin{theorem}\zlabel{theorem}
A theorem.
\end{theorem}
Cf. \zcref{theorem} \zcpageref{theorem}.\par
Cf. \zcref[noref]{theorem} \zcpageref{theorem}.
\newpage
\begin{lemma}\zlabel{lemma}
A lemma.
\end{lemma}
Cf. \zcref[noref]{lemma} \zcpageref{lemma}
\end{document}

Indeed, though \zcpageref{lemma} gives the right page number, \zcref[noref]{lemma} doesn't display anything, and we are warned about this by the following message:

Package zref-clever Warning: Reference format option 'name-sg' undefined for (zref-clever)

which looks odd since there's no (obvious) reason for name-sg to not be defined in such a case.
It would be nice for \zcref to display the name of unnumbered objects (and BTW, to not require the user to resort the noref option for them and to automatically display only the name for such unnumbered objects).

Hi @dbitouze , well, this is expected behavior. The reference type is inferred from the current counter, if there's no counter, there's no (automatic) way to tell. It's the same thing with the standard referencing system. Page references always get the page where \label is called, but the reference itself is taken from the last numbered object, usually the one to have last called \refstepcounter, which sets both \@currentlabel and \@currentcounter.
If you put a section in your document, that lemma reference won't think its name is missing, but will believe it is a section, rather than a lemma. So, the reason name-sg is undefined in your document is that there's no previous (global)  call to \refstepcounter. The theorem does call it once (I think), but sets \@currentcounter locally within the environment.
zref-clever lets you force the type for it:
\AddToHook{env/lemma/begin}{\zcsetup{reftype=lemma}}

But if you try a regular reference to the same label, you'll still get the wrong number. Same thing for hyperlinks, that's why \phantomsection exists. For example:
\documentclass{article}
\usepackage{amsthm}
\usepackage{zref-clever}
\usepackage{hyperref}

\newtheorem{theorem}{Theorem}
\newtheorem*{lemma}{Lemma}

\AddToHook{env/lemma/begin}{\zcsetup{reftype=lemma}}

\begin{document}
\setcounter{section}{5}
\section{Section 1}
\begin{theorem}\zlabel{theorem}
A theorem.
\end{theorem}
Cf. \zcref{theorem} \zcpageref{theorem}.\par
Cf. \zcref[noref]{theorem} \zcpageref{theorem}.
\newpage
\begin{lemma}\zlabel{lemma}
A lemma.
\end{lemma}
Cf. \zcref[noref]{lemma} \zcpageref{lemma}
\zcref{lemma} % that's the number of Section 1, and it links to Theorem 1,
              % since hyperref sets the anchors globally.
\end{document}

Regarding:

It would be nice for \zcref to display the name of unnumbered objects (and BTW, to not require the user to resort the noref option for them and to automatically display only the name for such unnumbered objects).

Again, it's the same thing as with the standard referencing system, everything is tailored to work for numbered objects. And there's a reason for it, it is really hard to know what to do in their absence.

Indeed, thanks!


[boost-modular-build-helper] Configure target windows version

https://github.com/microsoft/vcpkg/blob/e4524f656b885e76f9adf2356758b0ac994732e1/ports/boost-modular-build-helper/boost-modular-build.cmake#L257-L259
Is your feature request related to a problem? Please describe.
All boost packages are targeted to Windows 8 or later because of hardcoded -D_WIN32_WINNT=0x0602. It should be configurable.
Proposed solution
Simply remove L257-L258.
Describe alternatives you've considered
I tried to override this configuration by VCPKG_CXX_FLAGS.
set(VCPKG_CXX_FLAGS "/D_WIN32_WINNT=_WIN32_WINNT_WINXP /DBOOST_USE_WINAPI_VERSION=_WIN32_WINNT_WINXP /DNTDDI_VERSION=NTDDI_WINXPSP2")

But failed.
C:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\shared\sdkddkver.h(283): fatal error C1189: #error:  NTDDI_VERSION setting conflicts with _WIN32_WINNT setting

Boost's default is Windows 7 target. But at vcpkg, all boost packages are targeted to Windows 8 and it is hard coded. Is this expected feature?

merged, so close this.


Running on Bash on Ubuntu on Windows not working

Running the installation script doesn't work on Bash on Ubuntu on Windows:
rggjan@CGL-DESKTOP-06:~$ sh -c "$(curl -fsSL https://raw.githubusercontent.com/robbyrussell/oh-my-zsh/master/tools/install.sh)"
Cloning Oh My Zsh...
Cloning into '/home/rggjan/.oh-my-zsh'...
remote: Counting objects: 829, done.
remote: Compressing objects: 100% (699/699), done.
remote: Total 829 (delta 14), reused 743 (delta 9), pack-reused 0
Receiving objects: 100% (829/829), 565.13 KiB | 0 bytes/s, done.
Resolving deltas: 100% (14/14), done.
Checking connectivity... done.
Looking for an existing zsh config...
Found ~/.zshrc. Backing up to ~/.zshrc.pre-oh-my-zsh
Using the Oh My Zsh template file and adding it to ~/.zshrc
Time to change your default shell to zsh!
Password:
__                                     __
____  / /_     ____ ___  __  __   ____  / /
/ __ / __ \   / __ ` / / / /  /  / / / __
/ // / / / /  / / / / / / // /    / /(_  ) / / /
_// //  // // //_, /    //// //
/____/                       ....is now installed!
Please look over the ~/.zshrc file to select plugins, themes, and options.
p.s. Follow us at https://twitter.com/ohmyzsh.
p.p.s. Get stickers and t-shirts at http://shop.planetargon.com.
/home/rggjan/.zshrc:3: command not found: ^M
/home/rggjan/.zshrc:6: command not found: ^M
/home/rggjan/.zshrc:11: command not found: ^M
/home/rggjan/.zshrc:14: command not found: ^M
/home/rggjan/.zshrc:18: command not found: ^M
/home/rggjan/.zshrc:21: command not found: ^M
/home/rggjan/.zshrc:24: command not found: ^M
/home/rggjan/.zshrc:27: command not found: ^M
/home/rggjan/.zshrc:30: command not found: ^M
/home/rggjan/.zshrc:33: command not found: ^M
/home/rggjan/.zshrc:36: command not found: ^M
/home/rggjan/.zshrc:41: command not found: ^M
/home/rggjan/.zshrc:46: command not found: ^M
/home/rggjan/.zshrc:49: command not found: ^M
/home/rggjan/.zshrc:54: command not found: ^M
/home/rggjan/.zshrc:55: command not found: ^M
/home/rggjan/.zshrc:source:56: no such file or directory: /home/rggjan/.oh-my-zsh/oh-my-zsh.sh^M
/home/rggjan/.zshrc:57: command not found: ^M
/home/rggjan/.zshrc:59: command not found: ^M
/home/rggjan/.zshrc:61: command not found: ^M
/home/rggjan/.zshrc:64: command not found: ^M
/home/rggjan/.zshrc:71: command not found: ^M
/home/rggjan/.zshrc:74: command not found: ^M
/home/rggjan/.zshrc:77: command not found: ^M
CGL-DESKTOP-06%

Why do you think zsh configuration should work in bash?

Executing the installation script from within bash always worked fine on Linux. One of the things the script does is actually changing the default shell from bash to zsh. (In any case, the script runs in "sh" no matter if run from bash or zsh)

I'm experiencing this now as well, on a previous install the process worked perfectly.

@rggjan Do you happen to have autocrlf set to true in your ~/.gitconfig? I realized that was the problem for me, cloning on-my-zsh was replacing /N with /R/N. Setting it to false and setting autocrlf to true on a per-repository basis did the trick.

@petersondrew Yes, this seems to have been the issue as well, the autocrlf settings. I think it would be great if you could add the exact instructions how to make it work in the Getting Started or some part of the wiki...

Unfortunately I think this is a Windows Subsystem for Linux issue. Git believes that it's running on Windows IT seems, so it adds the castle returns. This issue will surface with any project that uses git as part of the installation process.

Apparently github has removed the edit comment button on mobile. I meant carriage returns, of course.

This is entirely possible... maybe the bug should be moved to git or to the WSL trackers?

This is fixed by removing the git config core.autocrlf or setting it to input.


annotation format - YOLO

hello,
could the YOLO export could be updated to included a yolo OBB format that deals with oriented bounded box?
thanks

Latest release


StartStreamMatchingAnyConditionAsync & AddFollow

Hi,
Could I call AddFollow after the stream is started (using StartStreamMatchingAnyConditionAsync)? Or is it mandatory to call AddFollow before?

You must call it when the stream is stopped. If the stream is running you can stop it using stream.Stop().

ok!
Are Start/Stop methods fast? My concern is that I could miss tweets when my stream is stopped...

You will miss tweets during this stop. The only thing you could do is run 2 streams (you will need multiple credentials). Stop 1 stream, when the one with the new filters has started, stop the other one.

Also be aware that we have an unresolved issue that freeze the UI if you try to start/stop a same stream x times in a very short amount of time. I would recommend to wait 3 seconds before start/stop a stream.

I have no UI (using that from a Windows service); will I have some issues?

I am not sure I understand. Didn't you said that the library was not working for Windows Phone?
But to answer your question, Tweetinvi can be used in Windows Service.

I didn't speak about windows phone...
You said you recommend to wait 3 seconds before start/stop a stream; but from a windows service, I don't need to do that,do I?

Sorry about windows phone, it was my mistake. I got confused with another issue.

You said you recommend to wait 3 seconds before start/stop a stream; but from a windows service, I don't need to do that,do I?

I suggest that you wait 3 seconds between invoking a StopStream and invoking a StartStream regardless of the type of project you use (including windows service).
stream.StopStream();
stream.AddTrack("my_track");
Thread.Sleep(3000);
stream.StartStream();

ok, will do that
thanks!


In-app notification system

I would like to implement an in-app notification/toast system, rather than calling the OS's specific one.
But this is not a critical issue at this moment.

https://github.com/atom/notifications

https://github.com/indexiatech/re-notif

https://github.com/gor181/react-notification-system-redux

https://github.com/CodeSeven/toastr

Picked up Electron's native notification api; https://github.com/hackjutsu/Lepton/commit/55b1e7c95498db728a626bc0d7c84a844835db93


completions/zsh: fix broken zsh tab completion for brew upgrade

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[ ] Have you successfully run brew style with your changes locally?
[ ] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?
[ ] Have you successfully run brew man locally and committed any changes?

Fixes https://github.com/Homebrew/brew/issues/10409

Review period will end on 2021-01-26 at 02:05:46 UTC.

Review period will end on 2021-01-26 at 02:05:46 UTC.

Review period skipped due to critical label.

Review period skipped due to critical label.


Different require in webContents throws blocks loading right click context

If Ember app is wrapped in Electron, original module and require globals have to be replaced with ember versions of that.
That blocks loading right click context on https://github.com/sindresorhus/electron-debug/blob/master/index.js#L25.
Could we make require call configurable?

Configurable how? I would strongly prefer a workaround that doesn't introduce configuration.

I was thinking something like
webContents.executeJavaScript(`${settings.require_fn}('${__dirname}/context-menu').install();`);

having settings.require_fn set to 'require' by default.

I think browser-window-created app event is called before user get any change to load an url on the browser window instance.
The event receive the browser window instance as an argument. We could use this event to save original value of require and than use that to load the context-menu module.
This way no configuration is needed at all, and user code on page could do wehatever it want to window.require. I could prepare a PR for this.

:+1:

@parro-it would you create a PR for that or you want me to do that?

@mariokostelac I will, thank you.


Handle applicationShouldTerminate

To properly handle system shutdown or user clicking on Quit menu item, we need to handle applicationShouldTerminate.
The implementation should go through all opened windows and attempt to gracefully close them. If any window cancels the exit, the process should stop.
We should also add
interface INativeDesktopLifetimeProvider
{
     event  EventHandler<CancelEventArgs> OnExit;
}

So it can be wired up with ClassicDesktopApplicationLifetime or be used separately

@danwalmsley

Keep in mind if an application refuses to quit during shutdown, macOS can cancel the cancel the shutdown sequence and tell the user that "this app is preventing shutdown" which gives the user an opportunity to cleanly save their work and reexecute the shutdown. This can be utilized in cases where a user is prompted to save their work, but selects the 'Cancel' option instead.

I think Windows supports this as well.
https://docs.microsoft.com/de-de/windows/win32/shutdown/wm-queryendsession
https://docs.microsoft.com/de-de/windows/win32/shutdown/wm-endsession

I've noticed there was some progress with NativeMenu, what's the state of this right now?


No satisfactory results on high-resolution image inpainting

Hi, I tried on an 1080X1920 image with a large area-filled mask. The results seems not ok to me:

Could you explain why it didn't work, or do you know any literature that can deal that very well?
Thanks.

Hii
Could you explain how you prepared this dataset? I'm providing the input image path as the folder containing all the images, but I'm encountering this error.
TypeError: Input 'filename' of 'ReadFile' Op has type float32 that does not match expected type of string.
Could you share the steps for preparing the dataset?


[liblas] Fix geotiff dependency, document usage, add feature 'tools'

Alternative to #25636.
Includes #25354.

What does your PR fix?
Adds GeoTIFF package lookup to the exported config.
Adds a valid usage file.
Adds a tools feature for building utility programs.
Cleanup and modernization.
liblas always builds shared libraries. This means x64-windows is actually unsupported. This PR doesn't change that. It just ensure that the DLLs are retained for x64-windows-static-md.

Which triplets are supported/not supported?


planets movement

make planets slowly orbiting their star.
what do you think?

Seems tempting mainly for the visualization purposes. Not sure if it adds anything for the gameplay


Database Serialization/Deserialization Performance Regression

A large amount of user actions cause a performance regression during database serialization/deserialization.

Fixed in 2.1.2267-dev.


New version: RealVNC.VNCServer version 7.11.0

Pull request has been created with komac v2.2.1 :rocket:
Microsoft Reviewers: Open in CodeFlow
Resolves: https://github.com/microsoft/winget-pkgs/issues/150613

Hi @vikingnope,

This PR's version number <IP_ADDRESS> has 4 parameters (sets of numbers between dots - major, minor, etc), which is greater than the current manifest's version 7.8.0, which has 3 parameters.

Does this PR's version number exactly match the version reported in the Apps & features Settings page? (Feel free to attach a screenshot.)
(Automated response - build 877)

@stephengillie, this can be merged please 😄


Add Proguard rules for WindowCallbackWrapper

Copied over from https://github.com/square/leakcanary/issues/2280 by @mlilienberg
Description
My app is crashing when showing Dialog Fragments while R8 is turned on and with latest version 2.8.1.
I think the issue is that curtains dependency does not provide correct proguard rules. curtains.internal.WindowCallbackWrapper is accessing WindowCallbackWrapper from androidx and android.support via reflection. Adding proguard rules to app level solves the issue for me but it would be better if leakcanary or curtains could define those rules.
-keep class androidx.appcompat.view.WindowCallbackWrapper { *; }
-keep class android.support.v7.view.WindowCallbackWrapper { *; }

I don't think is a good idea to add keep rule.
As a library, why not let user pass androidx.appcompat.view.WindowCallbackWrapper or android.support.v7.view.WindowCallbackWrapper into curtains.

As a library, why not let user pass androidx.appcompat.view.WindowCallbackWrapper or android.support.v7.view.WindowCallbackWrapper into curtains.

@CoXier what would the API look like for this? I'm not sure we'd be able to support this and keep Curtain working smoothly.


allow setting status code and description at the end of background spans #197

Per #197, this adds otel-cli span end --status-code error --status-description ono. The status code and description are sent through JSON-RPC to the backend which updates the span before sending it upstream.

note: commit timestamps are wrong because my silly VM keeps losing time, sigh.


Disable ckeditor in mobile

Fix #239

Coverage remained the same at 36.83% when pulling d2044099bab3ee769dbf999a7fa199599e9f3b92 on yakky:feature/mobile into 34b397b2b0dedc0a85f5e3c75dc3d368229aa93e on divio:master.


Crach when loadding map game -  C&C TIBERIUM SUN FIRESTORM EXP - NOD Mission 07 (destroy cabal)

Hello,
The game app Freeze when loadding map NOD Mission 07 (destroy cabal).
 I'm locked here....

I guess that problem might not even be related to cnc-ddraw but you could upload me a debug log anyways, maybe it's possible to see something in it:
https://github.com/FunkyFr3sh/cnc-ddraw/issues/44

Cool you have here :
log + except.txt  file + last saved backup map, the crash occur after when loading next map
cnc-ddraw-1.log.zip
except.txt
SAVE491C.SAV.zip

Pretty sure this isn't related to cnc-ddraw - I would suggest you to download some savegames somewhere and use them load into mission 7 or play the entire mission 6 again from the beginning (I think something might have glitched and messed up your game)


Social information problem in Safari (-category)

Should be: -category.

You could try:
.social-info {
  …
  h3 {
    …
    &::before {content: '—';}
  }
  …
}

You might need to add padding/margin in the before pseudoselector.

Should work, tried it on someone's computer where it wasn't correct:
width: 100%;
white-space: nowrap


Updating signature returns a 500 error

Hi all, I am trying to update a signatures on my users and keep getting the following error.
gam user<EMAIL_ADDRESS>signature "Jay"
gam user<EMAIL_ADDRESS>signature "Jay" Setting Signature for<EMAIL_ADDRESS>(1 of 1) Traceback (most recent call last):   File "/Users/jayd/Tools/GAM/gam.py", line 9679, in <module>     doSignature(users)   File "/Users/jayd/Tools/GAM/gam.py", line 4928, in doSignature     callGData(service=emailsettings, function=u'Put', soft_errors=True, data=xmlsig, uri=uri)   File "/Users/jayd/Tools/GAM/gam.py", line 635, in callGData     return method(**kwargs)   File "/Users/jayd/Tools/GAM/gdata/service.py", line 1394, in Put     media_source=media_source, converter=converter)   File "/Users/jayd/Tools/GAM/gdata/service.py", line 1357, in PostOrPut     'reason': server_response.reason, 'body': result_body} gdata.service.RequestError: {'status': 500, 'body': '<?xml version="1.0" encoding="UTF-8"?>\r\n<AppsForYourDomainErrors>\r\n  <error errorCode="1000" invalidInput="" reason="UnknownError" />\r\n</AppsForYourDomainErrors>\r\n\r\n', 'reason': 'Internal Server Error'}
This is a new google apps account, but I have followed setup instructions to the letter. I can check my oauth token, I can pull domain info. Just not update a signature.
I am using the latest version of GAM. Any advice would be great!
Thanks
Jay

Closing this issue as signature code has been migrated off old Email Settings API to new Gmail API. Please upgrade to latest GAM 3.8. If you still see issues please open a new bug.


Update dx-graphics-hlsl-semantics.md

Separate the input and output semantics to make them easier to read. Had a person mistake DEPTH[n] as input semantic

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


Build Error with latest package version <IP_ADDRESS>-beta

Please fill out either the bug or feature request section and remove whatever section you are not using.
Bug
Version Number of Plugin: <IP_ADDRESS>-Beta
Device Tested On: n/a
Simulator Tested On: n/a
Have updated to latest version of the package - no errors during the upgrade.  However when I build my project I the The Name 'CrossInAppBilling' does not exist in current context.  If I revert back to v<IP_ADDRESS>-beta it all builds and runs fine.
I can see that the DLL has been referenced.
This build error is only currently showing in my PCL Project
I tried clean and rebuilds and even deleted the bin/obj folders and rebuilt, restarted VS.  Same.

Lightening fast fix there, thanks man!

Yeah, was trying to tidy up nuspec stuff, and had some wrong code in there :) thanks for reporting


[EmbeddingApi-Stability] Add automation tests of stability embedding API

-Add automation tests of stability embedding API
Impacted tests(approved): new 12, update 60, delete 0
Unit test platform: [Android]
Unit test result summary: pass 12, fail 0, block 0

@Honry please help to review it.

LGTM, @jennycao please also help review.

LGTM


requests to create store, tests for it

I didn't work with get requests for now. Faked user_id and country_id for now

Codecov Report
Attention: Patch coverage is 66.03774% with 18 lines in your changes missing coverage. Please review.

Project coverage is 89.54%. Comparing base (6f84902) to head (2332b21).

Files with missing lines
Patch %
Lines

services/store-service.js
69.56%
7 Missing :warning:

routes/store.js
70.00%
6 Missing :warning:

services/user-service.js
28.57%
5 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #16      +/-   ##
==========================================
- Coverage   92.21%   89.54%   -2.67%
==========================================
  Files          24       26       +2
  Lines         244      287      +43
  Branches       21       22       +1
==========================================
+ Hits          225      257      +32
- Misses         17       30      +13
+ Partials        2        0       -2

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


BccAccordion additions

Restructuring
When trying to use the BccAccordion component in an Event product we found out that none of the variants fitted our needs. This caused us to rethink the approach variants.
Currently we have a mix of variants usage:

BccButton: has the variants primary, secondary and tertiary
BccTooltip: has the variants: dark, white and grey
BccAccordion used to have the variants: readonly, desktop, brand and interactive

Because the variant namings differs so much, they are hard and unexpected to use. Also, Variants that had a very specific design would often only work for 1 use case. In this PR we propose to repurpose the variant prop into the following:
"Variants should be a descriptive term for the overall appearance of the component, not a guideline for design practices (like primary, sec...) or a specific value (like dark, white, grey). It should instead be a term for a specific 'style' of the component that is reusable for different domains"
Examples of this new variants would be:

BccAccordion has the variants: filled, outlined, soft and ghost
BccTooltip has the variants: filled, outlined
BccButton has the variants: filled, outlined and ghost

These variants can then be further customized by adding a context like warning, neutral.
The plan is to agree on this approach in this PR for the BccAccordion. And then refactor the other components in a follow-up PR once agreement is reached.
The inspiration for this approach comes from Nuxt UI
Change summary
Allong with the variant restructuring, the following was also added to the BccAccordion

Add open prop to initiate the Accordion in an expanded state
Add info prop to add a text to the right of the title.

Change type

[ ] No review
[X] Small PR
[ ] Big PR
[X] Refactor

We have been speaking to the design team to align on this new approach. We have also decided that any restrictions to design are to be only applied at the design level in figma, such that components we create can be more customisable/configurable and more developer focused rather than being one to one to the design system setup in figma.
Visually it will still be the same, but it may be that our components support more colors than are currently allowed in BCC product designs.
The thought behind this is, too make it more useful across all products that are developed by us developers, even though not all products are BCC, eg. Work app.
Also, as most "proper" products will have a design in figma first, developers will just use that to implement what they see, even though the components themselves can do more.

Alright 👍 Originally we defined that the design library should not be too customizable as to prevent developers from implementing things that do not follow the design system. But it's fine to change our minds, just make sure everyone understands the implications.

The thought behind this is, too make it more useful across all products that are developed by us developers, even though not all products are BCC, eg. Work app.

That's what a "theme" would be for I feel. Currently everything is "bccForbundet" theme, with the idea being we could introduce a new theme that mostly follows the same guidelines but with different colors, fonts, etc.


update CLI options table

Codecov Report

Merging #6475 into master will decrease coverage by 0.05%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #6475      +/-   ##
============================================
- Coverage        83%   82.94%   -0.06%
+ Complexity    13077    13070       -7
============================================
  Files          1499     1499
  Lines         48590    48590
  Branches       5870     5870
============================================
- Hits          40330    40302      -28
- Misses         5492     5514      +22
- Partials       2768     2774       +6

Impacted Files
Coverage Δ
Complexity Δ

...n/java/io/crate/exceptions/JobKilledException.java
0% <0%> (-66.67%)
0% <0%> (-1%)

...in/java/io/crate/lucene/match/CrateRegexQuery.java
43.47% <0%> (-39.14%)
4% <0%> (-5%)

...a/io/crate/executor/transport/ActionListeners.java
33.33% <0%> (-22.23%)
2% <0%> (-1%)

...ration/reference/doc/lucene/IpColumnReference.java
72.72% <0%> (-13.64%)
5% <0%> (ø)

...crate/executor/transport/TransportShardAction.java
73.68% <0%> (-13.16%)
8% <0%> (-1%)

...n/java/io/crate/planner/projection/Projection.java
90% <0%> (-10%)
6% <0%> (-1%)

...crate/planner/projection/MergeCountProjection.java
63.63% <0%> (-9.1%)
5% <0%> (-1%)

...io/crate/protocols/postgres/types/VarCharType.java
91.66% <0%> (-8.34%)
10% <0%> (-1%)

...on/projectors/sharding/ShardingUpsertExecutor.java
89.02% <0%> (-4.88%)
16% <0%> (ø)

...rc/main/java/io/crate/analyze/UnboundAnalyzer.java
68% <0%> (-4%)
2% <0%> (ø)

... and 21 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 562679e...8f43256. Read the comment docs.


Fix #270 Broken CCDA

Fixes CCDA template to account for changes in Provider model.
Also, tracks exceptions in CCDA parsing in our unit test that would have discovered this error earlier.

Looks good.
Aside, at one point we were getting other CCDA-related exceptions and those seem to be gone now too, or at least I didn't hit it when generating 500+ patients. Not sure when or how those were fixed.


No animation on first button.

In the example provided, the animation of the first button does not work. Its size does not change. A similar problem in my project led me here.
What could be wrong?

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

ID: 62d6f305-ee68-74f4-8a8c-8d9aa6cb9e5d
Version Independent ID: ff16a248-622a-754e-d3f9-76e3a99fa242
Content: How to: Animate the Size of a FrameworkElement
Content Source: docs/framework/wpf/advanced/how-to-animate-the-size-of-a-frameworkelement.md
Product: dotnet-framework
GitHub Login: @dotnet-bot
Microsoft Alias: dotnetcontent

Thank you for your feedback @Zalant82. We'd have to test this to see what's wrong. We're moving this to our backlog for now.

I just tested the sample and it seems to be working. You can find the whole sample here: https://github.com/dotnet/samples/tree/master/snippets/xaml/VS_Snippets_Wpf/transformanimations_snip/XAML


How could I save the params and OpenCL kernel after geometry?

@newling I'm a newbie to MIOpenGEMM. Could you tell me how to save the params and OpenCL kernel after doing geometry? Sorry for raising this as an issue:) But I don't if we have other way to raise questions of usage?
Great thanks in advance!
-jack

Hi Jack,
If you want to make MIOpenGEMM run fast for a particular Geometry (say M=10, N=5, K=4096, tA=tB=0), take a look at: examples/find.cpp.
If you want to actually see OpenCL kernels (which isn't necessary for most users of MIOpenGEMM), take a look at: examples/print.cpp
Please let me know if you have any follow-up questions.

@newling Thanks! I will look over it and come back to you if any more issues!

@newling
Hi, James:
Thanks for your help again! But, I met a new issue here:):
I use API call like this:
MIOpenGEMM::gemm0(
extSolution->order,
extSolution->transA,
extSolution->transB,
extProblem->M,
extProblem->N,
extProblem->K,
extSolution->alpha,
d_a, 0, extSolution->lda,
d_b, 0, extSolution->ldb, extSolution->beta,
d_bias, 0, extSolution->ldc,
&(l_Runtime->GetStream())[0], 0, NULL, NULL);
Here: M=10, N=4096,K=25088, TransA=false, TransB=true, alpha=beta=1
The issue is: it took about 564.23 milliseconds! While using clblas, it’s only 0.82 milliseconds. Do you know why? Any hints?

These one of kernel performance tests are tricky to get right in my experience. One thing to note is that the first call to gemm with a Geometry (M=10, N=4096,K=25088,TransA=false, TransB=true, alpha=beta=1) is slow as the kernel is generated and compiled. Best practise is always to have at least one warm up run when benchmarking, not sure if you're doing this?

@newling looks like you mean it needs to try some parameters then get the best one? Do we have any example about how to do this?

@newling looks like there's some example in "MIOpenDriver gemm" for doing this, but I am not able to understand it's src code. So could you show me some quick example? Maybe there's some in find.cpp, but that's not very straightforward.
Thanks in advance,
-jack

No gemm0 does not "try some parameters", but it still needs to compile the OpenCL kernel (I think clblas has kernels precompiled).
The function gemm0 is basically the same as clBLAS gemm. One place to look where it is used is in deepbench.cpp, line 287.  It should be straightforward, just call gemm0 once before you start timing.

@newling You are right, I tried. Then my question is:
I think the opencl kernel will be stored somewhere, how long it will be there? i.e. if I don't remove any "cache", the compiled kernel will always be there? Where is it stored?

@jackyh yep, correct. sorry for the slow reply.


Make capture groups work for swift testing without @Suite

Not all tests where captured with the new Swift testing implementation in 2.12.0, here's an update.
It's my first PR on this project, please let me know what I need to add.

This might already be covered with this PR, let me know if this one is still needed. #318

I am not sure this will help anything with Swift Testing. AFAIK XCTest uses this syntax not SwiftTesting.  I could be wrong, I am by no means an expert. This does allow for capture of SomeStructThatsNotASuite/someFunctionName() or SomeStructThatsNotASuite.someFunctionName(). Which if types XCTest outputs both of those formats, this would help!

I've setup a sample project to show the case where this is happening:
https://github.com/bobvoorneveld/TestDemo
if you run:
xcodebuild test -workspace TestDemo.xcworkspace -scheme TestDemo -testPlan TestDemo

You get this output:
Testing started
Test suite 'OldTestCase' started on 'My Mac - xctest (19509)'
Test case 'OldTestCase.testExample()' passed on 'My Mac - xctest (19509)' (0.001 seconds)
Test suite 'TestStructdfdTests' started on 'My Mac - xctest (19511)'
Test suite 'TestStructTests' started on 'My Mac - xctest (19511)'
Test case 'TestStructdfdTests/exampleInPackage()' passed on 'My Mac - xctest (19511)' (0.000 seconds)
Test case 'TestStructTests/example()' passed on 'My Mac - xctest (19511)' (0.000 seconds)
Test suite 'OldTestCase' started on 'My Mac - TestDemo (19510)'
Test case 'OldTestCase.testExample()' passed on 'My Mac - TestDemo (19510)' (0.001 seconds)
Test suite 'SubFolderTestDemoTests' started on 'My Mac - TestDemo (19512)'
Test suite 'TestDemoTests' started on 'My Mac - TestDemo (19512)'
Test case 'TestDemoTests/exampleInProject()' passed on 'My Mac - TestDemo (19512)' (0.000 seconds)
Test case 'SubFolderTestDemoTests/example()' passed on 'My Mac - TestDemo (19512)' (0.000 seconds)
Test case 'OldTestCase.testPerformanceExample()' passed on 'My Mac - xctest (19509)' (0.735 seconds)
Test case 'OldTestCase.testPerformanceExample()' passed on 'My Mac - TestDemo (19510)' (0.546 seconds)
2024-10-16 17:51:23.242 xcodebuild[19448:6830107] [MT] IDETestOperationsObserverDebug: 1.522 elapsed -- Testing started completed.
2024-10-16 17:51:23.242 xcodebuild[19448:6830107] [MT] IDETestOperationsObserverDebug: 0.000 sec, +0.000 sec -- start
2024-10-16 17:51:23.242 xcodebuild[19448:6830107] [MT] IDETestOperationsObserverDebug: 1.522 sec, +1.522 sec -- end

Test session results, code coverage, and logs:
	/Users/bobvoorneveld/Library/Developer/Xcode/DerivedData/TestDemo-egofdzyzasaewcevnkwbcictndhs/Logs/Test/Test-TestDemo-2024.10.16_17-51-07-+0200.xcresult

** TEST SUCCEEDED **

It happens when you try to run the all the tests in parallel, not only swift testing.

Ahh I see. I also don't know what implications if any a test plan has on the scenario. Yeah definitely looks like this will be needed also. If you run make install  (or build it however) on your branch you can then use it to pipe the output like usually. Not necessary but if you want to see what other scenarios, I most definitely missed.

Added the capture of a failing test, forgot that one in the first commit. Made sure that nested structs are also working, which seems to be the case:
Failing tests:
	StructInStructTests.functionInSubstructThatFailed()
	SubFolderTestDemoTests.exampleFalse()

** TEST FAILED **

Testing started
Test Suite OldTestCase started on 'My Mac - xctest (30948)'
    ✔ [OldTestCase] testExample on 'My Mac - xctest (30948)' (0.001 seconds)
Test Suite TestStructdfdTests started on 'My Mac - xctest (30950)'
Test Suite TestStructTests started on 'My Mac - xctest (30950)'
    ✔ [TestStructdfdTests] exampleInPackage on 'My Mac - xctest (30950)' (0.000 seconds)
    ✔ [TestStructTests] example on 'My Mac - xctest (30950)' (0.000 seconds)
Test Suite OldTestCase started on 'My Mac - TestDemo (30949)'
    ✔ [OldTestCase] testExample on 'My Mac - TestDemo (30949)' (0.001 seconds)
Test Suite SubFolderTestDemoTests started on 'My Mac - TestDemo (30957)'
Test Suite TestDemoTests started on 'My Mac - TestDemo (30957)'
Test Suite SubFolderTestDemoTests/StructInStructTests started on 'My Mac - TestDemo (30957)'
    ✔ [OldTestCase] testPerformanceExample on 'My Mac - xctest (30948)' (0.774 seconds)
    ✔ [SubFolderTestDemoTests] example on 'My Mac - TestDemo (30957)' (0.000 seconds)
    ✔ [TestDemoTests] exampleInProject on 'My Mac - TestDemo (30957)' (0.000 seconds)
    ✖ [SubFolderTestDemoTests] exampleFalse on 'My Mac - TestDemo (30957)' (0.000 seconds)
    ✔ [SubFolderTestDemoTests/StructInStructTests] functionInSubstruct on 'My Mac - TestDemo (30957)' (0.000 seconds)
    ✖ [SubFolderTestDemoTests/StructInStructTests] functionInSubstructThatFailed on 'My Mac - TestDemo (30957)' (0.001 seconds)
    ✔ [OldTestCase] testPerformanceExample on 'My Mac - TestDemo (30949)' (0.473 seconds)

Nice! Just curious. What happens if you run it without the test plan? My assumption is XCTestPlan causes all output to be treated in a similar way. Wondering if without it, run them individually and be different...

Ok, created another project, only thing i've done is added a xctestcase and a swift testing struct in 2 files, then it happens to. So it seems to be the combination of the 2 testing frameworks, that this happens.
Testing started
Test suite 'OldTestCase' started on 'My Mac - TestDemo2 (43165)'
Test case 'OldTestCase.testExample()' failed on 'My Mac - TestDemo2 (43165)' (0.214 seconds)
Test suite 'TestDemo2Tests' started on 'My Mac - TestDemo2 (43172)'
Test case 'TestDemo2Tests/example()' failed on 'My Mac - TestDemo2 (43172)' (0.001 seconds)
Test case 'OldTestCase.testPerformanceExample()' passed on 'My Mac - TestDemo2 (43165)' (0.258 seconds)

Testing started
Test Suite OldTestCase started on 'My Mac - TestDemo2 (43418)'
    ✖ [OldTestCase] testExample on 'My Mac - TestDemo2 (43418)' (0.251 seconds)
Test Suite TestDemo2Tests started on 'My Mac - TestDemo2 (43426)'
    ✖ [TestDemo2Tests] example on 'My Mac - TestDemo2 (43426)' (0.000 seconds)
    ✔ [OldTestCase] testPerformanceExample on 'My Mac - TestDemo2 (43418)' (0.265 seconds)


fix(simd): update SIMD opcodes

See https://github.com/WebAssembly/simd/pull/452 for finalized opcodes
and https://github.com/WebAssembly/simd/issues/467 for some renamings.

Where do the .wasm files in __fixtures__ come from? Some of them need to be updated. I'm still running the tests and updating snapshot, will rebase later.

Where do the .wasm files in __fixtures__ come from? Some of them need to be updated. I'm still running the tests and updating snapshot, will rebase later.

Those are generated by jest. You can pass -u to jest to rebaseline them.

fixes #90
We probably want to disable some wabt tests. wasmparser.rs disables (until tools settle): simd_boolean.wast, simd_lane.wast, simd_i16x8_arith2.wast, simd_f64x2_rounding.wast, simd_f32x4_rounding.wast.

Updated with some tests disabled.

It looks like I can't merge this, please help me :) thanks!

Done, thanks!

:tada: This PR is included in version 5.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Publish NuGet under Microsoft org

Goal: Investigate how to publish official Microsoft NuGets and if possible find people that had experienced the process.
Success Criteria:

Identify official documentation to publish Microsoft NuGets that follow best practices and guidelines
Identify potential point of contact in the internal team to ask questions when needed

### Tasks

Official internal documentation can be found here:

https://devdiv.visualstudio.com/DevDiv/_wiki/wikis/DevDiv.wiki/972/NuGet
https://devdiv.visualstudio.com/DevDiv/_wiki/wikis/DevDiv.wiki/11557/Publishing-Microsoft-packages?anchor=publishing-microsoft-packages-on-nuget.org

There are detailed steps to publish a Microsoft package, for more details follow the guidelines below:
Check if your package meets the criteria and is compliant
Onboard your team to publish Microsoft packages to NuGet.org
Publish your package
For help, consult the following page: https://devdiv.visualstudio.com/DevDiv/_wiki/wikis/DevDiv.wiki/11561/NuGet-contacts

Closing as the framework was re-written on Python. A PyPI package needs to be used instead.


issue #3

Description
The login page has great potential for enhancement, focusing on key areas such as updating the background, refining the form layout, optimizing the color theme, and ensuring full responsiveness. These improvements will elevate the visual appeal, usability, and accessibility of the login experience, aligning it more closely with the brand's identity and providing a more welcoming and user-friendly interface.
Current Behavior

Background: The current background is simple but could be enhanced to better reflect the brand’s identity, making the login page more vibrant and engaging.
Login Form: The current form design is functional but could benefit from a cleaner layout, improved spacing, and a more intuitive visual hierarchy to guide users smoothly through the login process.
Color Theme: The existing color scheme works but could be refined to create a more harmonious and visually appealing look, enhancing the overall experience.
Responsiveness: While functional, there is room for optimization to ensure the login page adapts seamlessly to various screen sizes, providing an optimal experience across all devices.

Proposed Behavior

Background: Update the background to reflect the brand’s identity better, using elements such as gradients, imagery, or subtle patterns to create a more visually appealing login page.
Login Form: Redesign the login form with improved spacing, intuitive input fields, and clear form validation. Make the primary actions (login and submit) more prominent and accessible to users.
Color Theme: Refine the color palette to ensure consistency, readability, and visual appeal, enhancing user engagement and making the login experience more inviting.
Responsiveness: Implement a fully responsive design for the login page, ensuring the layout and elements adapt fluidly to all screen sizes, including desktops, tablets, and smartphones.

Screenshots

Additional Context
These updates are inspired by modern design principles and user feedback, suggesting the login page could be more intuitive and visually appealing. The goal is to create a welcoming and cohesive experience that reduces user friction and makes the login process straightforward and pleasant.
Impact

Usability: A cleaner form layout, clear navigation, and cohesive design will significantly enhance the login experience.
Accessibility: Better color contrast and a responsive design will make the login page accessible to a broader range of users, including those with visual impairments.
Performance: Streamlined design elements will improve page load times, particularly on mobile devices, providing a faster login experience.
Visual Appeal: A refreshed and modernized login page will create a strong first impression and may increase user engagement and retention.
The UI of the login page and the register page will be interlinked.(I have also raised a issue for that)

Related Issues
This approach can be applied to other pages within the application to ensure a consistent and professional appearance across the entire CampX website.

Hi @BinaryBhakti ,
Thank you for your detailed proposal! Your suggestions for enhancing the UI are well thought out and align with our goals for improving the user experience in the CampX project.
To ensure a clear and manageable review process, I recommend making separate pull requests for each change. This will allow us to evaluate each enhancement individually and maintain good practices in our workflow.
Looking forward to seeing your contributions!

Sure


Integration regularly becomes unavailable

System Health details
System Information

version
core-2024.2.3

installation_type
Home Assistant OS

dev
false

hassio
true

docker
true

user
root

virtualenv
false

python_version
3.12.1

os_name
Linux

os_version
6.1.63-haos-raspi

arch
aarch64

timezone
Pacific/Auckland

config_dir
/config

Home Assistant Community Store

GitHub API
ok

GitHub Content
ok

GitHub Web
ok

GitHub API Calls Remaining
4921

Installed Version
1.34.0

Stage
running

Available Repositories
1396

Downloaded Repositories
16

Home Assistant Cloud

logged_in
false

can_reach_cert_server
ok

can_reach_cloud_auth
ok

can_reach_cloud
ok

Home Assistant Supervisor

host_os
Home Assistant OS 11.5

update_channel
stable

supervisor_version
supervisor-2024.02.0

agent_version
1.6.0

docker_version
24.0.7

disk_total
109.3 GB

disk_used
12.5 GB

healthy
true

supported
true

board
rpi4-64

supervisor_api
ok

version_api
ok

installed_addons
Advanced SSH & Web Terminal (17.1.1), Studio Code Server (5.15.0), Samba share (12.3.0), Home Assistant Google Drive Backup (0.112.1), Mosquitto broker (6.4.0), RPC Shutdown (2.4), ESPHome (2024.2.0), Cloudflared (5.1.4), Zigbee2MQTT (1.35.3-1), ADB - Android Debug Bridge (0.7.0), MQTT Explorer (browser-1.0.3), Node-RED (17.0.7), Vaultwarden (Bitwarden) (0.21.1), Uptime Kuma (0.12.0)

Dashboards

dashboards
1

resources
2

views
0

mode
storage

Recorder

oldest_recorder_run
February 13, 2024 at 10:16 PM

current_recorder_run
February 24, 2024 at 8:35 AM

estimated_db_size
604.73 MiB

database_engine
sqlite

database_version
3.44.2

Spotify

api_endpoint_reachable
ok

Checklist

[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of any previous issues..

Describe the issue
It looks like every so often the integration needs to be refreshed as it loses its connection and goes into an unavailable state but reloading any sensor kicks the entire thing back into gear.
Reproduction steps

Install the integration
Wait for it disconnect
Press reload

Debug logs
No response
Diagnostics dump
No response

Hi @Krispkiwi - could you please add a bit more detail? What exactly goes into "unavailable" state? How are you "refreshing a sensor"?
My home instance is currently sitting at 9 days without dropping (since I reconfigured for the latest version) - any logs would be useful?
Thanks - Chris

Hi @Krispkiwi - could you please add a bit more detail? What exactly goes into "unavailable" state? How are you "refreshing a sensor"?
My home instance is currently sitting at 9 days without dropping (since I reconfigured for the latest version) - any logs would be useful?
Thanks - Chris

Hey mate, I've enabled debugging on the integration, not sure where to grab the logs from though.
Basically all the sensors in the integration that I have enabled fall into an unavailable state and i get the "This entity is no longer being provided by the metservice_weather integration. If the entity is no longer in use, delete it in settings" message however if I go into the integration and press reload, all sensors I am using from the integration come back online. I probably could automate this to refresh every time they go unavailable but figured its best to report it to you.

Tēnā kōrua, I've had the same experience as @Krispkiwi.
Here's a likely looking snippet from my logs this morning
2024-02-25 20:19:29.581 ERROR (MainThread) [custom_components.metservice_weather.coordinator] Error fetching MetService data: TimeoutError()
2024-02-25 20:19:35.408 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up metservice_weather platform for sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 344, in _async_setup_platform
    await asyncio.shield(task)
  File "/config/custom_components/metservice_weather/sensor.py", line 59, in async_setup_entry
    WeatherSensor(coordinator, description)
  File "/config/custom_components/metservice_weather/sensor.py", line 98, in __init__
    self._sensor_data = _get_sensor_data_public(
                        ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/metservice_weather/sensor.py", line 210, in _get_sensor_data_public
    result = get_from_dict(sensors[RESULTS_CURRENT], keys)
                           ~~~~~~~^^^^^^^^^^^^^^^^^
TypeError: 'NoneType' object is not subscriptable

Tēnā kōrua, I've had the same experience as @Krispkiwi.
Here's a likely looking snippet from my logs this morning
2024-02-25 20:19:29.581 ERROR (MainThread) [custom_components.metservice_weather.coordinator] Error fetching MetService data: TimeoutError()
2024-02-25 20:19:35.408 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up metservice_weather platform for sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 344, in _async_setup_platform
    await asyncio.shield(task)
  File "/config/custom_components/metservice_weather/sensor.py", line 59, in async_setup_entry
    WeatherSensor(coordinator, description)
  File "/config/custom_components/metservice_weather/sensor.py", line 98, in __init__
    self._sensor_data = _get_sensor_data_public(
                        ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/metservice_weather/sensor.py", line 210, in _get_sensor_data_public
    result = get_from_dict(sensors[RESULTS_CURRENT], keys)
                           ~~~~~~~^^^^^^^^^^^^^^^^^
TypeError: 'NoneType' object is not subscriptable

I can confirm that setting up the entities to reload when they become unavailable seems to solve it from a practical standpoint with a quick automation, it's a workaround for now.

This should hopefully be fixed now with 0.7.0 - please confirm if any issues are still occurring.

After I updated to 0.7.0 the weather warnings sensor is now unavailable, not sure if it is to do with this?

Im on version 0.8.1 and it just happened again. This time reloading or refreshing did not help, I had to remove integration and set it up again from scratch - including pannels - to get it working again....

Im on version 0.8.1 and it just happened again. This time reloading or refreshing did not help, I had to remove integration and set it up again from scratch - including pannels - to get it working again....

Hello - what time did this occur, and how long did you wait for before recreating? Mine went to unavailable at 9:02pm last night and came back up at 9:22 without issue.

Hello - what time did this occur, and how long did you wait for before recreating? Mine went to unavailable at 9:02pm last night and came back up at 9:22 without issue.

It was just about the time I posted ... As soon as I noticed, I tried to fix it, I did not know it might be worth waiting a bit.
Cheers.


Rails 4?

Is there any plan for Rails 4 support?
Bundler could not find compatible versions for gem "activemodel":
  In Gemfile:
    mongoid_geospatial (>= 0) ruby depends on
      activemodel (~> 3.1) ruby

    rails (= 4.0.0) ruby depends on
      activemodel (4.0.0)

Rails 4 working ok.
@unkleara the idea is that in ruby, currently moped removed almost every 2d query, there's only sphere. I'm going to document this, but not going to write any code as mongoid 5 will drop moped.


There is an error in the filter expression

The documentation says that the syntax for the filter is:
?filter=Table/Field eq 'Value'
It should be:
&$filter=Table/Field eq 'Value'

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

ID: 70b360f3-21a7-adc2-896a-b1dfd5d9e384
Version Independent ID: 15e8c09f-46ad-68f9-75e6-c3d5c2c214e5
Content: Filter a report using query string parameters in the URL - Power BI
Content Source: powerbi-docs/collaborate-share/service-url-filters.md
Service: powerbi
Sub-service: powerbi-service
GitHub Login: @maggiesMSFT
Microsoft Alias: maggies

Hi, @atinkerersnotebook -- just circling back on your comment. I just tried both
&$filter=Store/Territory eq 'NC'
and
?filter=Store/Territory eq 'NC'
Only the 2nd one filters the report. So I'm not sure what you're seeing.
Thanks!


Make the Label an optional part of the Diagnostic

Sometimes there's no specific place in the source file to point - consider a program in C which does not have main() function.

@prybicki the way I currently handle this is by pointing to the end of the file. YMMV, though.

Been experimenting with a new API that will let you do something like:
Diagnostic::error("oops")

This will emit something like:
error: oops


Warning when doing composer dump-autoload -o

Attempting to do composer dump-autoload -o results in the following.
Generating optimized autoload files
Class Composer\InstalledVersions located in ./vendor/composer/InstalledVersions.php does not comply with psr-4 autoloading standard. Skipping.
Class Composer\Autoload\ComposerStaticInit6494d3eccec62efccf5435d696f10ab3 located in ./vendor/composer/autoload_static.php does not comply with psr-4 autoloading standard. Skipping.
Class ComposerAutoloaderInit6494d3eccec62efccf5435d696f10ab3 located in ./vendor/composer/autoload_real.php does not comply with psr-4 autoloading standard. Skipping.
Class Composer\Autoload\ClassLoader located in ./vendor/composer/ClassLoader.php does not comply with psr-4 autoloading standard. Skipping.
Class Error located in ./vendor/workerman/workerman/Lib/Constants.php does not comply with psr-4 autoloading standard. Skipping.
Class SessionHandlerInterface located in ./vendor/workerman/workerman/Lib/Constants.php does not comply with psr-4 autoloading standard. Skipping.
Class FastRoute\BadRouteException located in ./vendor/workerman/webman-framework/vendor/nikic/fast-route/src/BadRouteException.php does not comply with psr-4 autoloading standard. Skipping.
Class FastRoute\DataGenerator located in ./vendor/workerman/webman-framework/vendor/nikic/fast-route/src/DataGenerator.php does not comply with psr-4 autoloading standard. Skipping.
Class FastRoute\DataGenerator\CharCountBased located in ./vendor/workerman/webman-framework/vendor/nikic/fast-route/src/DataGenerator/CharCountBased.php does not comply with psr-4 autoloading standard. Skipping.
Class FastRoute\DataGenerator\GroupCountBased located in ./vendor/workerman/webman-framework/vendor/nikic/fast-route/src/DataGenerator/GroupCountBased.php does not comply with psr-4 autoloading standard. Skipping.
Class FastRoute\DataGenerator\GroupPosBased located in ./vendor/workerman/webman-framework/vendor/nikic/fast-route/src/DataGenerator/GroupPosBased.php does not comply with psr-4 autoloading standard. Skipping.
Class FastRoute\DataGenerator\MarkBased located in ./vendor/workerman/webman-framework/vendor/nikic/fast-route/src/DataGenerator/MarkBased.php does not comply with psr-4 autoloading standard. Skipping.
Class FastRoute\DataGenerator\RegexBasedAbstract located in ./vendor/workerman/webman-framework/vendor/nikic/fast-route/src/DataGenerator/RegexBasedAbstract.php does not comply with psr-4 autoloading standard. Skipping.
Class FastRoute\Dispatcher located in ./vendor/workerman/webman-framework/vendor/nikic/fast-route/src/Dispatcher.php does not comply with psr-4 autoloading standard. Skipping.
Class FastRoute\Dispatcher\CharCountBased located in ./vendor/workerman/webman-framework/vendor/nikic/fast-route/src/Dispatcher/CharCountBased.php does not comply with psr-4 autoloading standard. Skipping.
Class FastRoute\Dispatcher\GroupCountBased located in ./vendor/workerman/webman-framework/vendor/nikic/fast-route/src/Dispatcher/GroupCountBased.php does not comply with psr-4 autoloading standard. Skipping.
Class FastRoute\Dispatcher\GroupPosBased located in ./vendor/workerman/webman-framework/vendor/nikic/fast-route/src/Dispatcher/GroupPosBased.php does not comply with psr-4 autoloading standard. Skipping.
Class FastRoute\Dispatcher\MarkBased located in ./vendor/workerman/webman-framework/vendor/nikic/fast-route/src/Dispatcher/MarkBased.php does not comply with psr-4 autoloading standard. Skipping.
Class FastRoute\Dispatcher\RegexBasedAbstract located in ./vendor/workerman/webman-framework/vendor/nikic/fast-route/src/Dispatcher/RegexBasedAbstract.php does not comply with psr-4 autoloading standard. Skipping.
Class FastRoute\Route located in ./vendor/workerman/webman-framework/vendor/nikic/fast-route/src/Route.php does not comply with psr-4 autoloading standard. Skipping.
Class FastRoute\RouteCollector located in ./vendor/workerman/webman-framework/vendor/nikic/fast-route/src/RouteCollector.php does not comply with psr-4 autoloading standard. Skipping.
Class FastRoute\RouteParser located in ./vendor/workerman/webman-framework/vendor/nikic/fast-route/src/RouteParser.php does not comply with psr-4 autoloading standard. Skipping.
Class FastRoute\RouteParser\Std located in ./vendor/workerman/webman-framework/vendor/nikic/fast-route/src/RouteParser/Std.php does not comply with psr-4 autoloading standard. Skipping.
Class FastRoute\Dispatcher\CharCountBasedTest located in ./vendor/workerman/webman-framework/vendor/nikic/fast-route/test/Dispatcher/CharCountBasedTest.php does not comply with psr-4 autoloading standard. Skipping.
Class FastRoute\Dispatcher\DispatcherTest located in ./vendor/workerman/webman-framework/vendor/nikic/fast-route/test/Dispatcher/DispatcherTest.php does not comply with psr-4 autoloading standard. Skipping.
Class FastRoute\Dispatcher\GroupCountBasedTest located in ./vendor/workerman/webman-framework/vendor/nikic/fast-route/test/Dispatcher/GroupCountBasedTest.php does not comply with psr-4 autoloading standard. Skipping.
Class FastRoute\Dispatcher\GroupPosBasedTest located in ./vendor/workerman/webman-framework/vendor/nikic/fast-route/test/Dispatcher/GroupPosBasedTest.php does not comply with psr-4 autoloading standard. Skipping.
Class FastRoute\Dispatcher\MarkBasedTest located in ./vendor/workerman/webman-framework/vendor/nikic/fast-route/test/Dispatcher/MarkBasedTest.php does not comply with psr-4 autoloading standard. Skipping.
Class FastRoute\HackTypecheckerTest located in ./vendor/workerman/webman-framework/vendor/nikic/fast-route/test/HackTypechecker/HackTypecheckerTest.php does not comply with psr-4 autoloading standard. Skipping.
Class FastRoute\RouteCollectorTest located in ./vendor/workerman/webman-framework/vendor/nikic/fast-route/test/RouteCollectorTest.php does not comply with psr-4 autoloading standard. Skipping.
Class FastRoute\DummyRouteCollector located in ./vendor/workerman/webman-framework/vendor/nikic/fast-route/test/RouteCollectorTest.php does not comply with psr-4 autoloading standard. Skipping.
Class FastRoute\RouteParser\StdTest located in ./vendor/workerman/webman-framework/vendor/nikic/fast-route/test/RouteParser/StdTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Composer\InstalledVersions located in ./vendor/workerman/webman-framework/vendor/composer/InstalledVersions.php does not comply with psr-4 autoloading standard. Skipping.
Class Composer\Autoload\ComposerStaticInitc637333517d300b186d2f555782ff97d located in ./vendor/workerman/webman-framework/vendor/composer/autoload_static.php does not comply with psr-4 autoloading standard. Skipping.
Class ComposerAutoloaderInitc637333517d300b186d2f555782ff97d located in ./vendor/workerman/webman-framework/vendor/composer/autoload_real.php does not comply with psr-4 autoloading standard. Skipping.
Class Composer\Autoload\ClassLoader located in ./vendor/workerman/webman-framework/vendor/composer/ClassLoader.php does not comply with psr-4 autoloading standard. Skipping.
Class Psr\Container\ContainerExceptionInterface located in ./vendor/workerman/webman-framework/vendor/psr/container/src/ContainerExceptionInterface.php does not comply with psr-4 autoloading standard. Skipping.
Class Psr\Container\ContainerInterface located in ./vendor/workerman/webman-framework/vendor/psr/container/src/ContainerInterface.php does not comply with psr-4 autoloading standard. Skipping.
Class Psr\Container\NotFoundExceptionInterface located in ./vendor/workerman/webman-framework/vendor/psr/container/src/NotFoundExceptionInterface.php does not comply with psr-4 autoloading standard. Skipping.
Class Workerman\Connection\AsyncTcpConnection located in ./vendor/workerman/webman-framework/vendor/workerman/workerman/src/Connection/AsyncTcpConnection.php does not comply with psr-4 autoloading standard. Skipping.
Class Workerman\Connection\AsyncUdpConnection located in ./vendor/workerman/webman-framework/vendor/workerman/workerman/src/Connection/AsyncUdpConnection.php does not comply with psr-4 autoloading standard. Skipping.
Class Workerman\Connection\ConnectionInterface located in ./vendor/workerman/webman-framework/vendor/workerman/workerman/src/Connection/ConnectionInterface.php does not comply with psr-4 autoloading standard. Skipping.
Class Workerman\Connection\TcpConnection located in ./vendor/workerman/webman-framework/vendor/workerman/workerman/src/Connection/TcpConnection.php does not comply with psr-4 autoloading standard. Skipping.
Class Workerman\Connection\UdpConnection located in ./vendor/workerman/webman-framework/vendor/workerman/workerman/src/Connection/UdpConnection.php does not comply with psr-4 autoloading standard. Skipping.
Class Workerman\Events\Ev located in ./vendor/workerman/webman-framework/vendor/workerman/workerman/src/Events/Ev.php does not comply with psr-4 autoloading standard. Skipping.
Class Workerman\Events\Event located in ./vendor/workerman/webman-framework/vendor/workerman/workerman/src/Events/Event.php does not comply with psr-4 autoloading standard. Skipping.
Class Workerman\Events\EventInterface located in ./vendor/workerman/webman-framework/vendor/workerman/workerman/src/Events/EventInterface.php does not comply with psr-4 autoloading standard. Skipping.
Class Workerman\Events\Revolt located in ./vendor/workerman/webman-framework/vendor/workerman/workerman/src/Events/Revolt.php does not comply with psr-4 autoloading standard. Skipping.
Class Workerman\Events\Select located in ./vendor/workerman/webman-framework/vendor/workerman/workerman/src/Events/Select.php does not comply with psr-4 autoloading standard. Skipping.
Class Workerman\Events\Swoole located in ./vendor/workerman/webman-framework/vendor/workerman/workerman/src/Events/Swoole.php does not comply with psr-4 autoloading standard. Skipping.
Class Workerman\Protocols\Frame located in ./vendor/workerman/webman-framework/vendor/workerman/workerman/src/Protocols/Frame.php does not comply with psr-4 autoloading standard. Skipping.
Class Workerman\Protocols\Http located in ./vendor/workerman/webman-framework/vendor/workerman/workerman/src/Protocols/Http.php does not comply with psr-4 autoloading standard. Skipping.
Class Workerman\Protocols\Http\Chunk located in ./vendor/workerman/webman-framework/vendor/workerman/workerman/src/Protocols/Http/Chunk.php does not comply with psr-4 autoloading standard. Skipping.
Class Workerman\Protocols\Http\Request located in ./vendor/workerman/webman-framework/vendor/workerman/workerman/src/Protocols/Http/Request.php does not comply with psr-4 autoloading standard. Skipping.
Class Workerman\Protocols\Http\Response located in ./vendor/workerman/webman-framework/vendor/workerman/workerman/src/Protocols/Http/Response.php does not comply with psr-4 autoloading standard. Skipping.
Class Workerman\Protocols\Http\ServerSentEvents located in ./vendor/workerman/webman-framework/vendor/workerman/workerman/src/Protocols/Http/ServerSentEvents.php does not comply with psr-4 autoloading standard. Skipping.
Class Workerman\Protocols\Http\Session located in ./vendor/workerman/webman-framework/vendor/workerman/workerman/src/Protocols/Http/Session.php does not comply with psr-4 autoloading standard. Skipping.
Class Workerman\Protocols\Http\SessionException located in ./vendor/workerman/webman-framework/vendor/workerman/workerman/src/Protocols/Http/Session.php does not comply with psr-4 autoloading standard. Skipping.
Class Workerman\Protocols\Http\Session\FileSessionHandler located in ./vendor/workerman/webman-framework/vendor/workerman/workerman/src/Protocols/Http/Session/FileSessionHandler.php does not comply with psr-4 autoloading standard. Skipping.
Class Workerman\Protocols\Http\Session\RedisSessionHandler located in ./vendor/workerman/webman-framework/vendor/workerman/workerman/src/Protocols/Http/Session/RedisSessionHandler.php does not comply with psr-4 autoloading standard. Skipping.
Class Workerman\Protocols\Http\Session\SessionHandlerInterface located in ./vendor/workerman/webman-framework/vendor/workerman/workerman/src/Protocols/Http/Session/SessionHandlerInterface.php does not comply with psr-4 autoloading standard. Skipping.
Class Workerman\Protocols\ProtocolInterface located in ./vendor/workerman/webman-framework/vendor/workerman/workerman/src/Protocols/ProtocolInterface.php does not comply with psr-4 autoloading standard. Skipping.
Class Workerman\Protocols\Text located in ./vendor/workerman/webman-framework/vendor/workerman/workerman/src/Protocols/Text.php does not comply with psr-4 autoloading standard. Skipping.
Class Workerman\Protocols\Websocket located in ./vendor/workerman/webman-framework/vendor/workerman/workerman/src/Protocols/Websocket.php does not comply with psr-4 autoloading standard. Skipping.
Class Workerman\Protocols\Ws located in ./vendor/workerman/webman-framework/vendor/workerman/workerman/src/Protocols/Ws.php does not comply with psr-4 autoloading standard. Skipping.
Class Workerman\Timer located in ./vendor/workerman/webman-framework/vendor/workerman/workerman/src/Timer.php does not comply with psr-4 autoloading standard. Skipping.
Class Workerman\Worker located in ./vendor/workerman/webman-framework/vendor/workerman/workerman/src/Worker.php does not comply with psr-4 autoloading standard. Skipping.
Class FastRoute\Dispatcher\CharCountBasedTest located in ./vendor/nikic/fast-route/test/Dispatcher/CharCountBasedTest.php does not comply with psr-4 autoloading standard. Skipping.
Class FastRoute\Dispatcher\DispatcherTest located in ./vendor/nikic/fast-route/test/Dispatcher/DispatcherTest.php does not comply with psr-4 autoloading standard. Skipping.
Class FastRoute\Dispatcher\GroupCountBasedTest located in ./vendor/nikic/fast-route/test/Dispatcher/GroupCountBasedTest.php does not comply with psr-4 autoloading standard. Skipping.
Class FastRoute\Dispatcher\GroupPosBasedTest located in ./vendor/nikic/fast-route/test/Dispatcher/GroupPosBasedTest.php does not comply with psr-4 autoloading standard. Skipping.
Class FastRoute\Dispatcher\MarkBasedTest located in ./vendor/nikic/fast-route/test/Dispatcher/MarkBasedTest.php does not comply with psr-4 autoloading standard. Skipping.
Class FastRoute\HackTypecheckerTest located in ./vendor/nikic/fast-route/test/HackTypechecker/HackTypecheckerTest.php does not comply with psr-4 autoloading standard. Skipping.
Class FastRoute\RouteCollectorTest located in ./vendor/nikic/fast-route/test/RouteCollectorTest.php does not comply with psr-4 autoloading standard. Skipping.
Class FastRoute\DummyRouteCollector located in ./vendor/nikic/fast-route/test/RouteCollectorTest.php does not comply with psr-4 autoloading standard. Skipping.
Class FastRoute\RouteParser\StdTest located in ./vendor/nikic/fast-route/test/RouteParser/StdTest.php does not comply with psr-4 autoloading standard. Skipping.
Class process\Monitor located in ./process.off/Monitor.php does not comply with psr-4 autoloading standard. Skipping.

This does not affect the use and can be ignored.
Worker man is a memory resident framework, which actually does not need the ` - o 'parameter.

Yeah, got that after doing a number of strace's on the process. Its amazing how fast workerman is :)


Sinkv2 flush interval conflict detector bfs

What problem does this PR solve?
Issue Number: close #7179
What is changed and how it works?

Re-introduce MaxFlushInterval into SinkV2, which is removed in #7106;
In conflict detector, search and notify transactions in BFS instead of DFS, which can reduce latency peak.

Check List
Tests

Unit test
Manual test (add detailed scripts or steps below)

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
None

/run-all-tests

/cc @liuzix

/run-all-tests

/check-issue-triage-complete

/run-integration-tests

/merge

/run-engine-integration-test


Xdebug not being installed

I've destroyed all containers/images, replaced every instance of INSTALL_XDEBUG=false to INSTALL_XDEBUG=true and rebuilt/started the containers. This doesn't seem to be working. What am I doing wrong?
Edit: I noticed there are 2 xdebug ini files in conf.d and that the line to load the extension was commented out. After uncommenting it, xdebug is loaded. Is there another way to enable this with laradock?

Watch this PR https://github.com/laradock/laradock/pull/632


Issue-1167: Replace application.properties by yaml equivalent.

Fixes #1167.

Replaced application.properties with application.yaml.

Acceptance Test

[x] Building the code with mvn clean install -Dintegration.tests still works.
[x] Running mvn spring-boot:run in the strongbox-web-core still starts up the application correctly.
[x] Building the code and running the strongbox-distribution from a zip or tar.gz still works.
[x] The tests in the strongbox-web-integration-tests still run properly.

@fuss86 : Thanks for your help!
@ptirador : Is this now ready for merging?

@fuss86: Thank so mucn for you help.
@carlspring: Yes, it's ready.


no module named 'torchtext.legacy'

My Python version is 3.8 and Pytorch version is 2.0, but an error is reported

Torchtext >= 0.12 had removed Field and lagacy modules.
You can try THIS :
`from torch.utils.data import DataLoader
from torch.nn.utils.rnn import pad_sequence
from collections import Counter
from torchtext.datasets import Multi30k
from torchtext.vocab import vocab
from torchtext.data import get_tokenizer`

The torch version is too high. Torchtext version is available at 0.9.0


Create about us

Hey Shaurya Kartik, Recently I viewed your PR but I noticed that your about us file is conflicting with my current project files. Please review it, I hope you can fix the issue and make PR again I might accept it after reviewing. Good Luck


Initial version of update NCN and version merging workflow

This provides a new workflow for editors to update the NCN of a judgment (aka the "move" workflow). Updating an NCN will also update the URI of a judgment, and making editors use this workflow provides an opportunity to more fully explain the consequences of doing so.
This workflow will also (in a somewhat hidden way) let you append one document to another as an updated version (aka the "merge" workflow). This is always available if a document is given the same NCN as another, but this functionality isn't advertised.
Upcoming changes to the ingester will allow documents in this 'colliding' state to be surfaced and editors offered the "merge" workflow.

Codecov Report

Merging #927 (fb4cf5d) into main (93c4f04) will decrease coverage by 1.08%.
The diff coverage is 48.64%.

@@            Coverage Diff             @@
##             main     #927      +/-   ##
==========================================
- Coverage   87.59%   86.52%   -1.08%
==========================================
  Files          36       38       +2
  Lines        1306     1343      +37
  Branches       46       49       +3
==========================================
+ Hits         1144     1162      +18
- Misses        145      164      +19
  Partials       17       17

Impacted Files
Coverage Δ

judgments/views/judgment_move.py
42.42% <42.42%> (ø)

judgments/forms/judgment_move.py
100.00% <100.00%> (ø)

judgments/urls.py
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

 Invent a process for merging two discrete documents in ML

To do: needs to move docx files from old/uri/old_uri.docx to new/uri/new_uri.docx instead of just new/uri/old_uri.docx

Should I hold off reviewing this until its been tested? @dragon-dxw @jacksonj04

Should we close this PR for now to reduce the number of open PRs given that this work is still not past design stage?


Remove stray parenthesis causing regex error

Changing the HTTP version regex from 1\. to \d also introduced a stray parenthesis causing the regex to fail to parse.

Right on. I've been using this gem for many years and it's awesome. Thanks for making it!


Elemental upgrade buttons missing

Elemental upgrade button icons are missing after you upgrade one element only that element will appear as an available upgrade. Some ability icons are also missing. Happens in Firefox and Chrome.

This is a feature. Edit the following line to unlock elements after upgrade.
var lockElements = false;
Nuke/damaging abilities are disabled during boss fights and gold rain to maximize gold gain for everyone

This seems like a terrible feature. Why are elemental upgrades locked?

This is to coordinate elemental upgrades for the Steam group. If you don't want to follow along, just disable it.

This seems like a terrible feature. Why are elemental upgrades locked?

As someone mentioned in some chat: "Because we are not allowed to think now".
But really, this is super useful. People otherwise will be upping more than one element (I did so before), plus nuking the boss at the same time ...

Btw wchill, do you know how it coordinates us and if it looks at specific room number and do so based on that as well?

It does not use room number at all to coordinate. Instead it takes your SteamID64, runs it through a hash function and then takes that mod 4 to determine which element you should spec.

@wchill Oh, I was wondering why it disabled all but one for me. I have 20 on fire, and it disabled all but air. I mean, I totally get the specialization. It would be nice to have a warning about it :P

Yeah, I'm gonna fix that. SteamDB guys modified my element lock to be much better, so I'm going to pull that change.

Ah, I thought we had a server or whatever to which we would send the room number and it could make balanced decisions. :) Hope the SteamID64 method is balanced enough.


testsuite: coverage: create kconfig option for gcov dump heap size

The heap size for serial dump of gcov data is currently defined by MALLOC_MAX_HEAP_SIZE, which cannot be adjusted by kconfig. This commit adds a new kconfig option, CONFIG_COVERAGE_GCOV_HEAP_SIZE, which retains the behavior or MALLOC_MAX_HEAP_SIZE by default.
Signed-off-by: Jason Wright<EMAIL_ADDRESS>

In our development we currently have to patch Zephyr to avoid getting the "No Mem available to continue dump" error in coverage dumps.


fix(User Management): re-gen service and update tests after API changes

PR summary
This PR contains a re-gen of the User Management service after recent API changes, plus some updates to the integration test.
PR Checklist
Please make sure that your PR fulfills the following requirements:

[ ] The commit message follows the Angular Commit Message Guidelines.
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] New tests
[ ] Build/CI related changes
[ ] Documentation content changes
[ ] Other (please describe)

What is the current behavior?

What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[ ] No

Other information

:tada: This PR is included in version 0.15.11 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


ASP.NET Core Blazor (landing page) topic

Title: ASP.NET Core Blazor
UID: client-side/blazor/index
URL: https://docs.microsoft.com/aspnet/core/client-side/blazor/

TOC
Define & describe
Link out .NET site Get started content
aspnet/Docs issues
Filing bugs/suggestions in Blazor repo
Link Blazor repo release notes

Moved to https://github.com/aspnet/Blazor.Docs/issues/11


Feature/#1 create helm chart

Closing #1 Create a Helm Chart.
The basic helm chart works well.

Error in build scripts.

Error in build scripts.


MTF spawned player receive broken radio

Sometimes MTF spawned players receive bad radio. probably game issue
Screenshot: https://media.discordapp.net/attachments/410829313579941889/420999405282394122/unknown.png

seems to be fixed


Object.getOwnPropertySymbols([1, 2, 3]) returns ['0', '1', '2']

Problem popped up in our project low.js:
Object.getOwnPropertySymbols([1, 2, 3]) returns ['0', '1', '2']
This does not seem to be the correct behaviour, it should return [], because the array items are not symbols. Both Firefox and Node return [].

@neoniousTR Thanks, this is clearly a bug. I'll open a fix pull shortly.

The issue also affected a plain String and a typed array argument.


[BUG] SyntaxError: f-string: expecting '}'

Just made a fresh install on Ubuntu 22.04. - Any idea what causes this?
Describe
Constant syntax error, even when running waybackup -h
Terminal output

waybackup -h
Traceback (most recent call last):
  File "/home/user/python-wayback-machine-downloader-TEST/python-wayback-machine-downloader/waybackdownloaderEnvironment/bin/waybackup", line 33, in <module>
    sys.exit(load_entry_point('pywaybackup==2.0.0', 'console_scripts', 'waybackup')())
  File "/home/user/python-wayback-machine-downloader-TEST/python-wayback-machine-downloader/waybackdownloaderEnvironment/bin/waybackup", line 25, in importlib_load_entry_point
    return next(matches).load()
  File "/usr/lib/python3.10/importlib/metadata/__init__.py", line 171, in load
    module = import_module(match.group('module'))
  File "/usr/lib/python3.10/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 883, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "/home/user/python-wayback-machine-downloader-TEST/python-wayback-machine-downloader/waybackdownloaderEnvironment/lib/python3.10/site-packages/pywaybackup/main.py", line 5, in <module>
    import pywaybackup.archive as archive
  File "/home/user/python-wayback-machine-downloader-TEST/python-wayback-machine-downloader/waybackdownloaderEnvironment/lib/python3.10/site-packages/pywaybackup/archive.py", line 177
    vb.write(message=f"-----> {"in CDX file".ljust(18)}: {sc.CDX_TOTAL:,}")
                                ^^
SyntaxError: f-string: expecting '}'

Any idea what causes this? Many thanks!

i think it is because of the double-quote inside the double-quote. which python version do you have? i do not get this bug.

I'm on Python 3.10.12
Thanks for looking into this!

you can try if 2.0.1 resolves this. just install via pip and let me know :)

`lab@lab-Virtual-Machine:~/lab$ pip install pywaybackup --upgrade
Defaulting to user installation because normal site-packages is not writeable
Requirement already satisfied: pywaybackup in /home/lab/.local/lib/python3.10/site-packages (2.0.1)
Requirement already satisfied: requests==2.31.0 in /home/lab/.local/lib/python3.10/site-packages (from pywaybackup) (2.31.0)
Requirement already satisfied: python-magic==0.4.27 in /home/lab/.local/lib/python3.10/site-packages (from pywaybackup) (0.4.27)
Requirement already satisfied: tqdm==4.66.2 in /home/lab/.local/lib/python3.10/site-packages (from pywaybackup) (4.66.2)
Requirement already satisfied: certifi>=2017.4.17 in /usr/lib/python3/dist-packages (from requests==2.31.0->pywaybackup) (2020.6.20)
Requirement already satisfied: charset-normalizer<4,>=2 in /home/lab/.local/lib/python3.10/site-packages (from requests==2.31.0->pywaybackup) (3.4.0)
Requirement already satisfied: idna<4,>=2.5 in /usr/lib/python3/dist-packages (from requests==2.31.0->pywaybackup) (3.3)
Requirement already satisfied: urllib3<3,>=1.21.1 in /usr/lib/python3/dist-packages (from requests==2.31.0->pywaybackup) (1.26.5)
lab@lab-Virtual-Machine:~/lab$ waybackup -h
Traceback (most recent call last):
File "/home/lab/.local/bin/waybackup", line 5, in
from pywaybackup.main import main
File "/home/lab/.local/lib/python3.10/site-packages/pywaybackup/main.py", line 5, in
import pywaybackup.archive as archive
File "/home/lab/.local/lib/python3.10/site-packages/pywaybackup/archive.py", line 184
vb.write(message=f"\n-----> {"to utilize".ljust(18)}: {sc.SNAPSHOT_UNHANDLED:,}")
^^
SyntaxError: f-string: expecting '}'

lab@lab-Virtual-Machine:~/lab$ git clone https://github.com/bitdruid/python-wayback-machine-downloader.git
Cloning into 'python-wayback-machine-downloader'...
remote: Enumerating objects: 251, done.
remote: Counting objects: 100% (150/150), done.
remote: Compressing objects: 100% (92/92), done.
remote: Total 251 (delta 115), reused 66 (delta 57), pack-reused 101 (from 1)
Receiving objects: 100% (251/251), 311.65 KiB | 2.73 MiB/s, done.
Resolving deltas: 100% (130/130), done.
lab@lab-Virtual-Machine:~/lab$ cd python-wayback-machine-downloader/
lab@lab-Virtual-Machine:~/lab/python-wayback-machine-downloader$ pip install .
Defaulting to user installation because normal site-packages is not writeable
Processing /home/lab/lab/python-wayback-machine-downloader
Preparing metadata (setup.py) ... done
Requirement already satisfied: requests==2.31.0 in /home/lab/.local/lib/python3.10/site-packages (from pywaybackup==2.0.0) (2.31.0)
Requirement already satisfied: tqdm==4.66.2 in /home/lab/.local/lib/python3.10/site-packages (from pywaybackup==2.0.0) (4.66.2)
Requirement already satisfied: python-magic==0.4.27 in /home/lab/.local/lib/python3.10/site-packages (from pywaybackup==2.0.0) (0.4.27)
Requirement already satisfied: urllib3<3,>=1.21.1 in /usr/lib/python3/dist-packages (from requests==2.31.0->pywaybackup==2.0.0) (1.26.5)
Requirement already satisfied: idna<4,>=2.5 in /usr/lib/python3/dist-packages (from requests==2.31.0->pywaybackup==2.0.0) (3.3)
Requirement already satisfied: certifi>=2017.4.17 in /usr/lib/python3/dist-packages (from requests==2.31.0->pywaybackup==2.0.0) (2020.6.20)
Requirement already satisfied: charset-normalizer<4,>=2 in /home/lab/.local/lib/python3.10/site-packages (from requests==2.31.0->pywaybackup==2.0.0) (3.4.0)
Building wheels for collected packages: pywaybackup
Building wheel for pywaybackup (setup.py) ... done
Created wheel for pywaybackup: filename=pywaybackup-2.0.0-py3-none-any.whl size=24096 sha256=eee02b340825146d5d5bb7f5ea4010b40e975d8e89ef9e68e7666896a6b25f1d
Stored in directory: /home/lab/.cache/pip/wheels/4d/7d/e6/632672ae4126060b04a2047798a81503a70e268d5eb2cc6191
Successfully built pywaybackup
Installing collected packages: pywaybackup
Attempting uninstall: pywaybackup
Found existing installation: pywaybackup 2.0.1
Uninstalling pywaybackup-2.0.1:
Successfully uninstalled pywaybackup-2.0.1
WARNING: The script waybackup is installed in '/home/lab/.local/bin' which is not on PATH.
Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
lab@lab-Virtual-Machine:~/lab/python-wayback-machine-downloader$ waybackup -h
Traceback (most recent call last):
File "/usr/local/bin/waybackup", line 5, in
from pywaybackup.main import main
File "/home/lab/.local/lib/python3.10/site-packages/pywaybackup/main.py", line 5, in
import pywaybackup.archive as archive
File "/home/lab/.local/lib/python3.10/site-packages/pywaybackup/archive.py", line 177
vb.write(message=f"-----> {"in CDX file".ljust(18)}: {sc.CDX_TOTAL:,}")
^^
SyntaxError: f-string: expecting '}'
lab@lab-Virtual-Machine:~/lab/python-wayback-machine-downloader$
`

you sure you are on 2.0.1 ? 2.0.1 is not on main - only dev
vb.write(message=f"-----> {"in CDX file".ljust(18)}: {sc.CDX_TOTAL:,}")
changed to
vb.write(message=f"-----> {'in CDX file'.ljust(18)}: {sc.CDX_TOTAL:,}")
in 2.0.1

For me, That solved the bug in those two past versions.

Thanks so much! This solved the issue!