Pandas 0.20.1 compatibility

Pandas 0.20.1 has been released with some backward incompatible changes. Based on a quick scan of the changelog the deprecation of .ix stands out to me as we use it in .select. This should be a trivial fix, but I'll have to do some testing to see if there's more issues.

Issue with holoviews/pandas/dask
----> 6 import holoviews as hv
/usr/lib/python3.5/site-packages/holoviews/core/init.py in ()
----> 2 from .data import *            # noqa (API import)
/usr/lib/python3.5/site-packages/holoviews/core/data/init.py in ()
---> 11 from ..dimension import redim
/usr/lib/python3.5/site-packages/holoviews/core/dimension.py in ()
---> 14 from ..core.util import (basestring, sanitize_identifier,
15                          group_sanitizer, label_sanitizer, max_range,
16                          find_range, dimension_sanitizer, OrderedDict,
/usr/lib/python3.5/site-packages/holoviews/core/util.py in ()
---> 32     import dask.dataframe as dd
/usr/lib/python3.5/site-packages/dask/dataframe/init.py in ()
1 from future import print_function, division, absolute_import
----> 3 from .core import (DataFrame, Series, Index, _Frame, map_partitions,
4                    repartition, to_delayed)
/usr/lib/python3.5/site-packages/dask/dataframe/core.py in ()
---> 40 pd.computation.expressions.set_use_numexpr(False)
AttributeError: module 'pandas' has no attribute 'computation'

The problem was resolve by upgrading dask to version 0.14.3

holoviews/core/util.py:27: FutureWarning: pandas.tslib is deprecated

@philippjfr Is this purely a pandas/dask issue that we need to be aware of but otherwise has nothing to do with our end?

Is this purely a pandas/dask issue that we need to be aware of but otherwise has nothing to do with our end?

That dask pandas.computation error is the remainder I've just opened a PR for.

All the required fixes were merged. Closing.


Weapon Qualities do not increase the Rank stat of the quality they change.

To test this, add Cortosis Forging to a weapon with at least 1 pierce (add that if required). Check the add mods for pierce, and the quality will visually change to Pierce 3, but editing the pierce value will show only one rank. When rolled, the rank is checked for the pierce quality and only displays Pierce 1.

I can't reproduce. I suppose that means it's fixed.


chore(master): release 0.2.0

:robot: I have created a release beep boop
0.2.0 (2024-05-25)
Features

add ci checks in the code (c713cab)
initial commit (9e846ed)
update the document and add some more examples for ruleset and its potential (c629ab3)

Bug Fixes

add release config file (822a3ee)
add release config file (9d77aec)
code updateto resolve issue (7aa4e38)
code updateto resolve issue (b064745)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/bibek469/terraform-cloudflare-ruleset/releases/tag/v0.2.0 :sunflower:


Could not find 'dataset/mini_pubtabnet

Why does running the configuration "make experiments/r18_e2_d4_adamw/.done_train_structure" not result in an error, but running configurations within the convolutional stem, such as "EXP_cs_c384_e4_d4_nhead8_adamw", produces the error "In 'main': Could not find 'dataset/mini_pubtabnet' "?
Available options in 'dataset':
        pubtabnet
Config search path:
        provider=hydra, path=pkg://hydra.conf
        provider=main, path=file:///rxhui/lxj/workspace/table_rec/tsr-convstem-main/configs
        provider=hydra-colorlog, path=pkg://hydra_plugins.hydra_colorlog.conf
        provider=schema, path=structured://

Set the environment variable HYDRA_FULL_ERROR=1 for a complete stack trace.
In 'main': Could not find 'dataset/mini_pubtabnet'

Thanks, @liJay010! Our latest work, UniTable: Towards a Unified Table Foundation Model, is fully released at https://github.com/poloclub/unitable/tree/main. I highly recommend testing on UniTable as it achieves SOTA performance on four of the largest table datasets. If you are looking for mini_pubtabnet, which contains 20 samples extracted from PubTabNet, it's also available in UniTable's repo at https://github.com/poloclub/unitable/tree/main/dataset/mini_pubtabnet.


End-to-end integration of website with customer support system

We may use IQ for a CRM and want to prototype the integration between their form and CRM system and our website. This will basically look like putting their form on our Contact Us page.
Tasks:

[x] Create form
[x] Add form to page
[ ] Kick off a workflow in CRM from form submission
[x] Write up findings from development and our team's experience with the workflow

Draft ADR in place

Marking this as closed because we have prototype of an integration, a draft ADR, and more product research in the works. We will make new issues when we have more info.


webView keyboard without arrows and "Done" button?

I know this is more React Native specific, but I figured a lot of people using the bridge would like to have this option.. Is there any way to disable the Arrows and 'Done' button above the keyboard in the webView?
I have a webView that loads a text editor that uses contentEditable text fields. But I have my own editor bar above the keyboard, and the safari bar above the keyboard makes it seem non-native.
Now it's like this: http://i.stack.imgur.com/Uz2Ly.png
But I want my own like this: http://www.geeky-gadgets.com/wp-content/uploads/2015/03/medium.jpg
I have found some solutions on how to do this, but I'm not able to implement it into the native code myself.
This code should work with iOS 9: http://stackoverflow.com/questions/19033292/ios-7-uiwebview-keyboard-issue/19042279#19042279
Here's a Cordova plugin that does the same (hideKeyboardAccessoryBar): https://github.com/driftyco/ionic-plugin-keyboard

It might be possible but, why would you load website inside webview?
what I mean is, let's say you are have already a website that is responsive. also you have wrote that one in either react or angular. now when you load that into webview, client needs to load css, all javascript to start showing to you the content and then you have to use some sort of bridge to tell the native side that ohh I'm done. Instead make the whole screen in native side. That is the whole concept of react-native. You can easily build your scene.
I will try to see if I can make it happen but I will encourage you to rethink about this approach.

I know what you mean. As I said, it's just a text editor. My whole app is build in React Native. It's just the text editor, because the TextInput is extremely limited. I need to edit inline links, italic, paragraphs, enter to split, backspace to combine while keeping the cursor in place, fonts, colors, photos, videos and custom elements, etc, etc. And I can align it with the text editor build into my site.
If there was some sort of Rich Text in RN, it might be doable. But disabling the 300ms delay on click makes the text editor feel native (except for the Arrows/Done bar I described). I see the advantage of React Native for the rest of my app, but in this case I think loading a webView makes more sense..
I don't think it's bad to leverage the real web in React Native. And like I said, I think other people using this plugin would like the keyboard to feel 'native' too.

@burnsting give me couple of days and I will get back to you! Your argument is also valid.

Thanks!

:+1: @burnsting I'm actually trying to achieve exactly the same thing, a rich text editor using a js library. Almost everything works fine, but this toolbar is really annoying :disappointed:

Thanks for implementing this @kemcake !

It's been merged. Thank you @kemcake.


Script is still using default values even after modifying the properties file

The script will always run with default values even after I edited the properties file. I edited samples/target/classes/RedshiftBasicSample.properties and ran the samples/target/appassembler/bin/redshift-basic-sample but yet the stream name for example doesn't change. I also tried renaming the other properties files and executable script files but the result is still the same. I'm baffled. Can anyone advise?

It's best not to make changes to files in the target directory.  The directory is management by maven.  The reason changing something in the classes directory doesn't work is that Appassembler, which generates the script, also creates a repository of the necessary jars.  This includes the jar generated by the samples project.
The best way to change the properties file is to make the change in src/main/resources/RedshiftBasicSample.properties, and recompile.  This will create a new jar of the samples project and place it in the Appassembler repo.

Many thanks. I didn't know I had to recompile. Your advice has resolved my issue.


Release train and boot versions get improperly updated

Done via https://github.com/spring-cloud/spring-cloud-release-tools/commit/4ab19000abc198620f291c23f33dedecd5e7f648


Prep keyvault/internal for release

Update to latest azcore and internal modules, removing duplicated code.
Fix for returning AccessToken by value.

[ ] The purpose of this PR is explained in this or a referenced issue.
[ ] The PR does not update generated files.

These files are managed by the codegen framework at Azure/autorest.go.

[ ] Tests are included and/or updated for code changes.
[ ] Updates to CHANGELOG.md are included.
[ ] MIT license headers are included in each file.

Test coverage is too low, I will increase.


How can I call AlertDialog.Builder after pressing Fab button?

Hi, congratulations for the good job!
I have a question though...
I would like to use Android built-in AlertDialog, and generally I set the title and message using AlertDialog.Builder in the Activity code.
How can I do it in a way the user press the Fab button, and it gets animated to show alert dialog instead of a CardView, as shown in the examples?

This isn't supported. You'll need to fork the library and implement your own animations to work with alert dialogs.


bump semver to 0.6.0

Hi, I'm sincerely sorry for taking so long to respond.
Thanks for the PR! I've bumped the semver version to 0.6 as part of a general update of this crate, so like #10 I'm closing this.


werf fails to ignore precommit hooks with werf build --dev command

Before proceeding

[X] I didn't find a similar issue

Version
1.2.186
How to reproduce

Precondition repository: contains pre-commit hook which always fails
Default werf.yaml (I don't think here's anything interesting in it)
Run werf build --dev

Result
werf build --dev
Version: v1.2.186
Running time 0.11 seconds
Error: unable to sync worktree with service branch "_werf-dev": unable to get or prepare service branch head commit: git merge of source commit "e0371a63e2d8a7acd2829385be114dae0b83976a" into service branch "_werf-dev" failed: error running command "/usr/bin/git -c core.autocrlf=false -c gc.auto=0 -c<EMAIL_ADDRESS>-c user.name=werf merge --no-edit --no-ff --allow-unrelated-histories -s ours e0371a63e2d8a7acd2829385be114dae0b83976a": exit status 1
Stdout:

Stderr:
.husky/prepare-commit-msg: 2: .: cannot open .husky/_/husky.sh: No such file
Not committing merge; use 'git commit' to complete the merge.

NOTE: To continue you can remove the service branch "_werf-dev" with "git branch -D _werf-dev", but we would also ask you to report this issue to https://github.com/werf/werf/issues

Expected result
The image build has been started
Additional information
Suggested command about dropping branch shows the next error:
git branch -D _werf-dev
error: Cannot delete branch '_werf-dev' checked out at '/home/username/.werf/local_cache/git_worktrees/9/local/4125e1c205aa4d5da0b3c0326b085e45fd232b5c6b9783b681f9b106055f4058/worktree'

Contents of .husky/prepare-commit-msg:
#!/bin/sh
. "$(dirname "$0")/_/husky.sh"

yarn jira-prepare-commit-msg $1

Thank you for your feedback, fix is coming in the next release.


⚠ Bofrost.at has degraded performance

In 80d9708, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1664 ms

Resolved: Bofrost.at performance has improved in 9dfea22 after 20 minutes.


New version: MartinStorsjo.LLVM-MinGW.UCRT version 19.1.6-20241217

Created by 🥟 Dumplings.
Microsoft Reviewers: Open in CodeFlow

This package installs and launches normally in a Windows 10 VM.


Swap 'Yes' and 'No' on the discard recording popup

Platform: Darwin Bens-MacBook-Pro.local 16.6.0 Darwin Kernel Version 16.6.0: Fri Apr 14 16:21:16 PDT 2017; root:xnu-3789.60.24~6/RELEASE_X86_64 x86_64
Kap Version: 1.0.0
Steps to reproduce
Discard any kapture
Current behaviour
'Yes' is on the left, and 'No' is highlighted and on the right
Expected behaviour
'No' is on the left, and 'Yes' is highlighted and on the right

This confuses me every single time, and it's really annoying.

Agreed. It should be:
[Cancel]  [Discard]

Cancel should be the highlighted button.


Fatal error: Uncaught Alchemy\BinaryDriver\Exception\ExecutableNotFoundException: Executable not found, proposed : avprobe, ffprobe in

Fatal error: Uncaught Alchemy\BinaryDriver\Exception\ExecutableNotFoundException: Executable not found, proposed : avprobe, ffprobe in C:\xampp1\htdocs\ffmpeg-3.3.2\vendor\alchemy\binary-driver\src\Alchemy\BinaryDriver\AbstractBinary.php:160 Stack trace: #0 C:\xampp1\htdocs\ffmpeg-3.3.2\vendor\php-ffmpeg\php-ffmpeg\src\FFMpeg\Driver\FFProbeDriver.php(48): Alchemy\BinaryDriver\AbstractBinary::load(Array, NULL, Object(Alchemy\BinaryDriver\Configuration)) #1 C:\xampp1\htdocs\ffmpeg-3.3.2\vendor\php-ffmpeg\php-ffmpeg\src\FFMpeg\FFProbe.php(207): FFMpeg\Driver\FFProbeDriver::create(Object(Alchemy\BinaryDriver\Configuration), NULL) #2 C:\xampp1\htdocs\ffmpeg-3.3.2\vendor\php-ffmpeg\php-ffmpeg\src\FFMpeg\FFMpeg.php(117): FFMpeg\FFProbe::create(Array, NULL, Object(Doctrine\Common\Cache\ArrayCache)) #3 C:\xampp1\htdocs\ffmpeg-3.3.2\index.php(4): FFMpeg\FFMpeg::create() #4 {main} Next FFMpeg\Exception\ExecutableNotFoundException: Unable to load FFProbe in C:\xampp1\htdocs\ffmpeg-3.3.2\vendor\php-ffmpeg\php-ffmpeg\src\FFMpeg\Driver in C:\xampp1\htdocs\ffmpeg-3.3.2\vendor\php-ffmpeg\php-ffmpeg\src\FFMpeg\Driver\FFProbeDriver.php on line 50
<?php require 'vendor/autoload.php; $ffmpeg = FFMpeg\FFMpeg::create(); $video = $ffmpeg->open('test.mp4'); $video     ->filters()     ->resize(new FFMpeg\Coordinate\Dimension(320, 240))     ->synchronize();

Please fill out the issue template, so we can help you properly... On what OS are you? Which version?

Is it possible that I sent you my teamviewer code and you installed it on my computer?

I'm sorry, but I don't understand what you mean?

Can you connect to my computer and install it by yourself?
On Tue, Jul 18, 2017 at 8:25 AM, Jens Hausdorf<EMAIL_ADDRESS>wrote:

I'm sorry, but I don't understand what you mean?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/PHP-FFMpeg/PHP-FFMpeg/issues/383#issuecomment-315954558,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Abc_N2LbtghMhxMzhxhvUHDlvuByNz9Hks5sPDOvgaJpZM4OaAKJ
.

I'm sorry, but we're an open-source project, which means that all communication is public as well, so we don't offer personal support, so we can avoid duplicates. Please provide a real-world example so I can reproduce, and I will reopen this issue.

ok, thank you
On Tue, Jul 18, 2017 at 2:53 PM, Jens Hausdorf<EMAIL_ADDRESS>wrote:

I'm sorry, but we're an open-source project, which means that all
communication is public as well, so we don't offer personal support, so we
can avoid duplicates. Please provide a real-world example so I can
reproduce, and I will reopen this issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/PHP-FFMpeg/PHP-FFMpeg/issues/383#issuecomment-316028437,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Abc_N5PBiPiekbIZvx7C-DI-uBNiR76Cks5sPI6WgaJpZM4OaAKJ
.


Thank you so, so much! ❤❤

Dear team from i18nexus,
I wasn't sure where the best place is to reach out, but I wanted to express my absolute gratitude for the sponsorship you've set up for next-intl!
I saw that you've published a tutorial on your website, that's so cool! If you have any questions or if you there's something next-intl can consider to work well with i18nexus, then please don't hesitate to reach out!
All the best,
Jan

Hi Jan, no problem! Thanks for all the work you do on next-intl. We see an increasing number of users using next-intl and we rarely get support requests about integrating with it thanks to your wonderful developer experience.
Thanks for offering to consider feedback from us, but we'll stay out of your hair for now! Keep up the good work! 🙂
Best,
David


fix(deps): upgrade swagger-ui-react v5.17.3, react-dom v18.3.1, and react v18.3.1. Fixes CVEs

This fixes CVEs: https://security.snyk.io/vuln/SNYK-JS-MICROMATCH-6838728, https://security.snyk.io/vuln/SNYK-JS-BRACES-6838727
   Upgrade<EMAIL_ADDRESS>to<EMAIL_ADDRESS>to fix
  ✗ Uncontrolled resource consumption (new) [High Severity][https://security.snyk.io/vuln/SNYK-JS-BRACES-6838727] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>  ✗ Inefficient Regular Expression Complexity (new) [High Severity][https://security.snyk.io/vuln/SNYK-JS-MICROMATCH-6838728] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>

The React upgrade also produced a bunch of new install warnings too:
warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "argo-ui ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^15.0.0-0 || ^16.0.0-0".
warning "argo-ui ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^15.0.0-0 || ^16.0.0-0".
warning "argo-ui ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| 16".
warning "argo-ui ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| 16".
warning "argo-ui > react-form ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^15.0.0-0 || ^16.0.0-0".
warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^15.0.0 || ^16.0.0 || ^17.0.0".
warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^15.0.0 || ^16.0.0 || ^17.0.0".

I'm not sure if all of those are safely ignoreable. Some of them are certainly fixable though (react-autocomplete is not, since the library was archived years ago)

swagger-ui-react removed in #13818
React 18 upgrade reverted in #13821


Markdown for Comments

Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
To provide the ability to render text formatted with markdown rules
Describe alternatives you've considered

WYSWIG
show preview by default, turn into plain text on edit
use a dedicated popup for that
on-demand preview

Additional context
We are documenting our databases putting parts of it to comments. Then we render wiki-like docs out of it.
Would be useful to see a preview of what is rendered then. Also, it would help to read the documentation directly from the database.

Thank you for the idea


NbToggleModule not available for Use

Issue type
I'm submitting a ...  (check one with "x")

[ ] bug report
[ ] feature request
[ ] question about the decisions made in the repository

Issue description
@nebular/theme"' has no exported member 'NbToggleModule'
Not able to find NbToggleModule for importing.
Current behavior:

Expected behavior:

Steps to reproduce:

Related code:

insert short code snippets here

Other information:
npm, node, OS, Browser
<!--
Node, npm: `node --version` and `npm --version`
OS: Windows (7/8/10). Linux (incl. distribution). macOS (El Capitan? Sierra?)
Browser: Chrome/Safari/Firefox/etc?
-->

Angular, Nebular
<!--
Check your `package-lock.json` or locate a `package.json` in the `node_modules` folder.
-->

hi @snandkule! Closed as fixed


256 colour terminal support?

Loaded it up and got this:

The same terminal with the Molokai theme that supports 256 color terminals:

@hackedWifi It does belong here. This theme currently limits the palette to 16 colours for any terminal not capable of true colour, rather than detect 256 colour mode (:set t_Co?) and expand the palette accordingly. I'm sure you agree that 256 colours is better than 16, and some closer matches could be used.

Same issue here. I'm using SecureCRT which does not support true color.
For gruvbox and solarized8 themes, there are bash scripts provided which fix colors for 256 color terminals.

this is the reason why I keep telling this issue does not belong on here
Vim in terminal mode must be used with a Nord terminal emulator theme in order to work properly!
Make sure to install one of the currently supported terminal emulator port projects before installing Nord Vim.
Vim in terminal mode uses the 16 color codes provided by the terminal emulator.
When used with another color theme than the one provided by one of Nord's terminal emulator ports, the colors in Vim won't use Nord's color palettes!
This will result in different styles than those defined by Nord Vim and could make it appear that there is a problem with the Nord Vim theme while the actual problem are missing Nord colors.

@hackedWifi I don't know why you're getting so worked up about this. Picking some close colours so the theme is legible, out of the box, is not a terrible idea. It is entirely possible to add a note saying the theme will not be 100% accurate unless the terminal's colour scheme is also overridden.
Do you get that not everyone wants to override their entire terminal's default colours for a single program? I've looked at the defaults provided by Nord for PuTTY and the default colours are definitely going to "break" normal output of some other programs. Colours 0 - 5 don't align with defaults, and other colours are duplicated, providing less differentiation:

I agree with @Roy-Orbison. Most of us are not going to switch completely to a different terminal emulator (and some might not be able to) because of a theme that supports only true color vs 256-color terminal emulators. It is appropriate to approximate the colors to fit 256-color terminal emulators.
I find myself in the same situation as @Roy-Orbison. I cannot use the theme because terminal.app does not support true color.
And it is perfectly reasonable for the nord-vim devs to reject the proposal of supporting 256-color.

I'm going to just throw it out there: https://st.suckless.org/patches/nordtheme/
the simple terminal has true color support.

Forked it.

I'm sure I made mistakes so feel free to submit pull requests to correct them.

Forked it.

I'm sure I made mistakes so feel free to submit pull requests to correct them.

AAAA thank you

Thank you for your patience! 🙏🏼
It‘s been a while since I had free time to focus more on Nord, and my open source projects in general, and invest time in this issue due to work-life balance.
I recently published the first “Northern Post — The state and roadmap of Nord“ announcement which includes all details about the plans and future of the Nord project, including the goal of catching up with the backlog. This issue is part of the backlog and therefore I want to triage and process it to get one step closer to a “clean state“. Read the announcement about reaching the “clean“ contribution triage state in Nord‘s discussions for more details about the goal.
Therefore it has been added for triage in the central and single-source-of-truth project board that is also described in more detail in the roadmap announcement.

To add some thoughts of mine about this topic:
The “legacy“ of terminals caused hundreds of questions and “problems“ for users, not only with this theme but colors in terminals in general.
The de-factor standard documentation for terminal colors, especially “true color“, is the termstandard/colors repository. It provides a deeper dive into how colors work the way they do today and also act as a color-compatibility tracker for terminals and applications. The repository is also mentioned as reference in Vim‘s :help xterm-true-color page. I guess everyone should be on the same page regarding colors in terminals after reading through the repository.
Based on that I‘d like to say that I spent hundreds of hours trying to support users to get Nord to work in their terminal and without “true color“ it has always been pain. Then it‘s not Vim itself then the terminal did some weird things rather than just sticking to some semi-specifications and conventions that settled down over the years. It took me so many hours of my life which I could have put to better use.
In my opinion, anything except “true color“ are relics from times that should be left behind. There is no reason to hold on to other schemes like pure 16, 24 or 256 colors while even any UEFI menu is fancier and more colorful than any desktop application 30 years ago.
With that said I think that everyone has recognized what my opinion on the subject is 😄
But I still want to elaborate constructive on this topic, maybe I‘m wrong and someone can simply tell me that it is quite easy to extend the range of supported color spaces.
To keep on topic I‘ll keep my comment on the 256 colors, but some of my next arguments can be applied to others like 16 colors too.
Implementing support for 256 colors is, in contrast to some of the suggested changes in this thread, not as easy as simply adding some more variables with the 256-compatible color IDs:

My first, and almost strongest, opinion against 256 colors is that choosing colors that are simply similar to Nord‘s colors is like saying that your recipe tastes the same when you exchange noodles through yogurt!
Nord‘s colors have been hand-picked with care and they work great because they are exactly those colors and not a single one could be changed without affecting the overall ambience and appearance.
Choosing “nearby“ colors for a 256-color implementation is not possible because I could then simply leave these tasks to a machine and color themes would then simply be completely useless without the “human touch“.
Detecting “true color“ support in a 100% accurate way is impossible!
To make sue that Nord continues to work fine for everyone who uses a modern terminal, without risking of falling back tp 256 colors due to a false-positive, the color compatibility detection must be waterproof. And this is where it get tricky because there are only specific ways to do so and the results are anything but clear. For example, checking the value of the TERM environment variable, in a terminal that injects it, often yells xterm-256color. This is a nice indicator that we could fall back to 256 colors, but how do we know if “true color“ also works? The answer is the COLORTERM environment variable, but since there is no official specification every terminal can decide whether to set it or not.
Checking the value of Vim‘s &t_Co variable doesn‘t help either since it also often returns 256 which does not help either. Of course we can check for termguicolors to see if we can use “true color“, but what happens when the user did not set it and the running Vim instance doesn‘t do it either (e.g. due to missing compile flags or pre-defined OS defaults).
In the end the risk of falling back to 256 colors for users whose setup is capable of providing a great experience with “true colors“ is too high.
The complexity will increase drastically for the code due to introduction of various condition checks that are required to decide whether to use “true color“ or a 256-equivalent when styling an element. In addition there are special cases like the increased comment color brightness which might need a 256-nearby-color that is almost identical with nord3 but only differs in brightness. This is not possible with the available colors and therefore causes another loss of visual differentiation.
Looking at the available 256 colors the first blocker is the fact that the “Polar Night“ palette can not be replaced by equivalent colors because there simply aren't enough colors in the 256-palette that still reflect the bluish appeal at all. This also applies to the “Frost“ palette which represents the “heart of the theme ambience“ with the main accent colors of Nord. Without these the theme is nothing but a unrelated collection of randomly selected colors from a hardly defined set of 256 colors.

All of these points make it hard, or just impossible, to implement 256-color support without almost creating a whole theme with its own ambience and appearance.

It's just not that big a deal, mate. People who are stuck on 256 colour terminals for whatever reason just wanted Nord. Now they can have something like it or choose another theme.


Implemented UX support for configuring doc level monitors.

Signed-off-by: AWSHurneyt<EMAIL_ADDRESS>Description
Refactored existing UX elements to support configuring doc level monitors.
Screenshots
Visual editor UX

Extraction query editor UX

Monitor details page

Alerts by trigger flyout, and finding flyout

Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

The unit test flow is currently failing due to outdated snapshots. yarn run test:jest -u is currently failing to update snapshots locally with the following error:
Test suite failed to run

    The error below may be caused by using the wrong test environment, see https://jestjs.io/docs/configuration#testenvironment-string.
    Consider using the "jsdom" test environment.

    ReferenceError: window is not defined

A solution seems to involve adding the following to the top of each test class. There are over 100 test classes at the moment, so that annotation will be added in a separate PR.
/**
 * @jest-environment jsdom
 */

Codecov Report

Merging #218 (8a16d4a) into main (e77eb5f) will decrease coverage by 3.67%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #218      +/-   ##
==========================================
- Coverage   56.79%   53.12%   -3.68%
==========================================
  Files         198      208      +10
  Lines        4756     5207     +451
  Branches      651      704      +53
==========================================
+ Hits         2701     2766      +65
- Misses       2053     2439     +386
  Partials        2        2

Impacted Files
Coverage Δ

.../containers/CreateMonitor/utils/monitorToFormik.js
36.11% <0.00%> (-63.89%)
:arrow_down:

.../containers/CreateMonitor/utils/formikToMonitor.js
63.63% <0.00%> (-11.37%)
:arrow_down:

...r/containers/DefineMonitor/utils/searchRequests.js
50.00% <0.00%> (-10.00%)
:arrow_down:

.../containers/CreateTrigger/utils/formikToTrigger.js
32.02% <0.00%> (-7.49%)
:arrow_down:

...reateMonitor/components/MonitorType/MonitorType.js
28.57% <0.00%> (-6.43%)
:arrow_down:

...ateTrigger/components/TriggerQuery/TriggerQuery.js
67.85% <0.00%> (-4.15%)
:arrow_down:

...lTriggerExpression/BucketLevelTriggerExpression.js
54.54% <0.00%> (-3.79%)
:arrow_down:

...omponents/TriggerExpressions/TriggerExpressions.js
60.00% <0.00%> (-3.64%)
:arrow_down:

...fineBucketLevelTrigger/DefineBucketLevelTrigger.js
21.05% <0.00%> (-2.68%)
:arrow_down:

...eTrigger/containers/DefineTrigger/DefineTrigger.js
12.30% <0.00%> (-2.62%)
:arrow_down:

... and 27 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 e77eb5f...8a16d4a. Read the comment docs.


(v1.0.4) Exclude java/nio/channels/DatagramChannel/Disconnect.java (#5587)

There is a compilation error: cannot find symbol
InetAddress.ofLiteral().

This is cherry-pick https://github.com/adoptium/aqa-tests/pull/5587. Please add cherry-pick <issue link> in the description in the future.


with those change http://localhost:7200/ runs ok

I don't know what's mean by #{= LUA_PACKAGE_PATH },it’s take me a
mistake like couldn't found modules, so  I change this to use
package.path param, and add a package.cpath to use  c libs like
lfs.so,am I right? thank you for check this for me, thanks so much that
gin is a wonderful framework

Not merging as per @istr comment. The dependency to Lua 5.1 has now been included in f45dfc5e1c87ddffa6cc6c8397c47c1ae7502e51 and

:) thanks @ostinelli  thank you all of you guys


Fix PDF render

Fixes https://github.com/JuliaLang/IJulia.jl/issues/1035 alongside
PR #4188 (which has been merged)

@fredrikekre Wanted to flag this as ready for review. :)

Is display of PDF images well supported in Jupyter?
This issue https://github.com/jupyter/notebook/issues/3652 seems to indicate that it only works in certain browsers or with certain plug-ins installed.

I think you're right in pointing out there is a bit of a file type conflict here:
Per the issue you linked, browser support of PDFs is (potentially) incomplete.
But Latex workflows like quarto's use case which use Jupyter to build a document (but not display it in the browser) do not work well with SVGs and require the use of the PDF format for exporting / displaying vector graphics.
Right now, if you create a PDF document with R, Python, and Julia graphs via quarto, the Julia graph gets dumped out as a PNG and looks significantly pixelated, the other two languages (afaik) allow for PDF viz export and certainly lead to vector viz output in the PDF.

The Jupyter format defines cell outputs as a dict that contains multiple representations of an output (e.g., plot). The frontend (e.g., jupyterlab) chooses which of the formats its want to render (so only one is shown at a time, but the various formats are present in the notebook file).
IJulia tries to generate a representation for every MIME type it supports (which is what this PR is changing).
This is actually not the case for Plots.jl -- it actually does override IJulia.display_dict: https://github.com/JuliaPlots/Plots.jl/blob/b6d7bd82e6c029b8cbbafa756015670cb0ab0013/src/init.jl#L92, which is what (personally) I think Quarto should do.

@travigd Thanks for the nudge to investigate this further, the Plots.jl PR https://github.com/JuliaPlots/Plots.jl/pull/4188 solved the issue for Plots, so this isn't necessary.
And for Makie, turns out it's a one-liner which can be done on the Quarto side: IJulia.register_mime(MIME("application/pdf")) 🎉

This is actually not the case for Plots.jl

Is there a way to override this in startup.jl/startup_ijulia.jl? For

Python, one may set c.InlineBackend.figure_formats = {'svg', 'pdf'} in ipython_config.py/ipython_kernel_config.py
R, one may set options(jupyter.plot_mimetypes = c('text/plain', 'image/svg+xml', 'application/pdf')) in Rprofile.site

in order to output both image/svg+xml and application/pdf plot formats in the notebook file:

image/svg+xml for plot display in the browser
application/pdf for direct PDF conversion

ℹ With application/pdf plot format in the notebook file, inkscape is not required for PDF conversion using nbconvert.


@farmfe/plugin-react - configure development mode a bit more

Hello,
I am using https://chromewebstore.google.com/detail/locatorjs/npbfdllefekhdplbkdigpncggmojpefi and this is pretty awesome to click on component and see code on VSCode straight away.
To do so I enable development: true in the react plugin like so:

I noticed it enabled these plugins:

And there I am interested to know how to configure @swc/plugin-transform-react-jsx-source ?
I was wondering if there is a way for the development mode to set the full path of the source file instead of relative?
That would make the configuration string to open vscode slightly simpler, for now mine is like this:
vscode://vscode-remote/ssh-remote+ncce/home/c/go/src/github.com/celerumltd/TLS-v4-frontend/${projectPath}${filePath}:${line}:${column}
and I wish it to be like that if it was possible to enable full path instead of relative path:
vscode://vscode-remote/ssh-remote+ncce/${projectPath}${filePath}:${line}:${column}

@swc/plugin-transform-react-jsx-source can not be configured and I'll add a option support configuring the file path to absolute path

@chneau Try<EMAIL_ADDRESS>I added a option named useAbsolutePath, set it to true then the generated file path would be absolute

@wre232114 Hello and thanks for tghe quick reply!
Unfortunately I get this error at the moment:
[ building ] ⠂ transform (13) node_modules/react-refresh/runtime.js                                                                                thread '<unnamed>' panicked at crates/node/src/plugin_toolkit/swc_transforms.rs:26:88:
called `Result::unwrap()` on an `Err` value: Error("unknown field `useAbsolutePath`, expected one of `runtime`, `importSource`, `pragma`, `pragmaFrag`, `throwIfNamespace`, `development`, `useBuiltIns`, `useBuiltins`, `useSpread`, `refresh`", line: 1, column: 37)
stack backtrace:
[ building ] ⠂ transform (17<EMAIL_ADDRESS>                                                                                note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

I'm using the latest versions:
		"@farmfe/cli": "^1.0.4",
		"@farmfe/core": "^1.3.27",
		"@farmfe/plugin-react": "^1.2.3",
		"@farmfe/plugin-sass": "^1.1.0",

I'll fix it now

try<EMAIL_ADDRESS>I tried localtorjs working fine

Thank you so much :) that works perfectly! cheers!


Slight changes to rumble code for versatility

Can now specify the address of the rumble so that MBC5 or other boards can have rumble instead of just a single, non-standard MBC3 board.

Closing as it is out of date. May consider resubmitting in the future.


Test framework for kernel (and user-level OS services)

It would be nice if we could leverage rust-standard behavior for writing things like #[test] in the kernel and in user-level OS services (for testing low-level Twizzler libraries like twizzler_abi) and integrate this with the build system so we can easily run the test framework as part of a github actions run.

The branch feature/test-framework now has some initial work on this. The following additions have been made:

changes to xtask to allow building test executables for twizzler libraries that can get loaded into the initrd.
init now looks for a test list object, listing the test executables that xtask finds.
the kernel now allows for exiting qemu using qemu's little ioport hack.
modified the kernel to parse incoming bootloader command line
kernel checks to see if --tests is present, and if so, exits qemu if a panic occurs (or if a magic syscall is made) with a code
init exits qemu with either success (1) or failure (3) to indicate if tests pass or fail.

This does not include a test framework for the kernel, which is a little trickier since it can't be hosted (the default rust test library expects a hosted compiler). Will work on that next.
This also doesn't currently allow for test harnesses in executables, only in libraries. We can work on that at a later time.
Since qemu's exit code can be controlled by the guest, we can hook this into a CI system without too much pain. In theory, anyway.
Note: this also does make assumptions that enough of the system works to even run the tests. Thus, if test mode is enabled, the kernel prints out a couple special messages ("!!! TEST MODE ACTIVE") so that a monitor script can inspect the output and time-out the CI if needed.

Oh, also note that the current implementation is super hacky. Will fix that later, this is just trying to get the needed features to work at all :)


Line force length assertion in Mechanics.MultiBody.Forces

There is a line force length assertion length > s_small in MultiBody.Forces.Spring (coming from the component of type LineForceWithMass). However, this assertion is missing in MultiBody.Forces.Damper, MultiBody.Forces.SpringDamperParallel and MultiBody.Forces.SpringDamperSeries. I propose to also add the line force length assertion Modelica.Math.Vectors.length(r_rel_a) > s_small to MultiBody.Interfaces.PartialLineForce to have it consistent.

Overall the inheritance seems odd in the MultiBody-library, causing the code to be duplicated - and sometimes missing.
It seems as though PartialLineForce could inherit from PartialTwoFrames (common code for cardinality-assert). And then LineForceWithMass and LineForceWithTwoMasses have something in common with PartialTwoFrames - not only the length check, but also fixedRotationAtFrame_*.

And then LineForceWithMass and LineForceWithTwoMasses have something in common with PartialTwoFrames -

I guess it should read: ... have something in common with PartialLineForce

Resolved in master branch by 519c2c581fd2f17c859dffda2cd0f921b2701b9a and f56af70e7d194c227bcf70595363806f0b91a1e0.


Feature/checkout logging

Implement Checkout/Checkin logging in recent activity
Purpose
Checking out a file was not logged in recent activity, even though it's a blocking activity. This feature adds that functionality.
Changes
Several files were amended to add this feature. Primarily, the ./website/files/models/osfstorage.py is where most of the action happened. Here I refactored the save method to log a checkin or checkout activity.  To update the view, I added template for the activity along with signals and function parameters to look for the new activity. No code in these sections was edited; rather, I just added the new parameters.
Issues
The tests passed locally and the view threw no errors due to the new logs.

Pass complete, I'll do functional testing after the above comments are resolved. :flags:
Travis is failing, but it's not obviously your fault, it might be a weird nondeterministic failure. However, please add tests to confirm proper logs are added when files are checked in/out.

This seems to have developed both a merge conflict and a circular import:
# Circular import
File "/Users/matt/Devel/osf.io/website/project/model.py", line 57, in <module>
    from website.files.models.base import File, StoredFileNode
  File "/Users/matt/Devel/osf.io/website/files/__init__.py", line 1, in <module>
    from website.files import models  # noqa
  File "/Users/matt/Devel/osf.io/website/files/models/__init__.py", line 9, in <module>
    from website.files.models.osfstorage import *  # noqa
  File "/Users/matt/Devel/osf.io/website/files/models/osfstorage.py", line 10, in <module>
    from website.project.model import NodeLog
ImportError: cannot import name NodeLog

This can be fixed by using the NodeLog.ACTIONS string ('checked_in' or 'checked_out') when determining the action to log in osfstorage.py.
# Conflict in api_tests/files/views/test_file_detail.py
<<<<<<< HEAD
=======
from framework.auth.core import Auth
from website.addons.osfstorage import settings as osfstorage_settings

>>>>>>> 62a9ea83e799cf9bdecef06ce94f58df63c81b69

Auth needs to stay, osfstorage_settings is imported a few lines down.
Confirmed that logs were added as expected after resolving the above issues. :space_invader:
I'll branch off of this and submit a new PR, thanks for your hard work @Marcus-Rosti


Mouse scrolling stuff

Implemented support for horizontal mouse wheel scrolling as well as high-precision scrolling on Windows and OS X. Should fix (#95).
If you're wondering why there isn't support for high-precision scrolling on Unix, it's because I spent half a day fighting with the non-existant XCB Xinput documentation only to realize that most X servers probably might not even provide high-precision values yet.
As usual, OS X stuff hasn't been tested.

Isn't it confusing to have delta, deltaX and deltaY within the same structure? (don't reply "documentation", you know that people never read it...)
What do you think of
Vector2f highPrecisionDelta;

?

I think splitting the event might make the most sense. On Windows and Unix they are generated separately anyway, I don't know if OS X actually generates events with deltas along multiple axes simultaneously but I don't think it will be that big of a drawback anyway. On the plus side, if we split the events, the size of the structs/union will be reduced which is always a good thing :stuck_out_tongue:.

What's the reason for introducing a second member rather than just changing the data type? Considering the integer variable is unreliable, I'd just accept potentially breaking existing code, since it would be broken anyway. Also leave the name untouched - classic scrolling is vertical only. Add a second event for horizontal instead.

What's the reason for introducing a second member rather than just changing the data type? Considering the integer variable is unreliable, I'd just accept potentially breaking existing code

It was discussed in #95.

I think splitting the event might make the most sense.

Yes, and it definitely looks cleaner.

Updated.
Still needs testing on OS X.

At first sight the changes look good but I'll test it later (probably next week, though).

MouseHorizontalWheel or HorizontalMouseWheel? :stuck_out_tongue:

I prefer having "Mouse" at the start :stuck_out_tongue:.

Ok, I was just wondering if it didn't sound too weird.

MouseWheelVertical+ MouseWheelHorizontal IMO - since both are MouseWheel so I wouldn't split that.

Updated.

Seems to work relatively well on OS X too. Just one thing: on Unix/Windows, do you get "null" events (where the delta is 0)? On OS X that's the case so you get spammed with those negligible events. I'm wondering if SFML should filter them or not... What do you think?

You will probably get them with the other OSs as well. If you have a high precision mouse in Linux, you will still get either 0.0 or 1.0 ticks. Don't know how it is on Windows exactly, but I can imagine values of 0 as well if the integer value can't represent the tiny movement you made on your wheel.
This way, we leave it up to the user to interpret what these values could mean. We can't know if it they might be meaningful to them or not, so better just give them everything and let them decide.

Good point.

From a quick test I can't get a delta smaller than -1 or 1 with my Logitech mouse's wheel and the wheel steps disabled (Windows 8.1 x64). I only end up with -1 or 1 no matter how fast I roll the wheel or whatever driver setting I use (125 Hz polling vs. 1 kHz polling). Not sure whether that's normalized in the drivers or so though.

It's completely up to the operating system what values it returns. MSDN documentation simply states that the OS can return values that are smaller than 120, and the developer should handle this properly. If the driver/OS doesn't want to provide smaller values through the message API, then there is nothing we can really do.

@binary1248 Is there anything else to do here? Since it's only +134/−44 changes, I feel we could include it in 2.3. What do you think?

I have nothing more to add to this. If everyone else agrees this can be included in 2.3, then be my guest :wink:.

This PR has been added to my merge list, meaning it will be merged soon, unless someone raises any concerns.

The values seem indeed a bit odd. I'm getting either 1, 2, 3 or 4 for scrolling up and 545.113, 544.113, 543.113 or 542.113 for scrolling down.
For vertical scrolling I get -545.113 for scrolling left and -1 for scrolling right.
So it doesn't do what the documentation comments say.

Turns out a cast was missing. :grin:
Should work as expected now...

Seems to be working now. :+1:

Why not one event type for both vertical and horizontal scrolling and an additional enum member denoting which one it was?
class Mouse
{
public:
   enum WheelType
   {
      HorizontalWheel,
      VerticalWheel,
   };
};

struct MouseWheelEvent
{
   int delta;
   int x;
   int y;
   Mouse::WheelType wheel;
};

This approach has three advantages:

It is consistent to existing event APIs like MouseButtonEvent and JoystickButtonEvent which give information about the mouse/joystick state and which button was pressed.

Two identical structs is code duplication which eventually leads to combinatorial explosion. If you ever encounter a strange mouse model with a third wheel, you have to create yet another struct. (and even with only two, it feels wrong to me)

It could extend the current API without deprecating it.

I like @Bromeon's suggestion. :)

I know this was merged already, but I have to say @Bromeon made a very good suggestion. I wouldn't be against changing it even though it was already merged into master. Yes - we would be breaking the API, but I think it would be fine as this API is hardly even established yet (I doubt anyone is using it yet).

I guess it makes sense, indeed. And since the API was not yet written in stone (only official release matter I'd say), we can change that easily.

I could write a corresponding pull request. What do you think about the identifiers, are they okay?

enum sf::Mouse::Wheel -- consistent to existing sf::Mouse::Button
struct sf::Event::PreciseMouseWheelEvent -- in addition to deprecated sf::Event::MouseWheelEvent

Those identifiers are fine in my book.

:ok_hand:

I started a new branch feature/combined_mousewheel. I basically wrote some code to show the idea, however I have not thoroughly tested it (I don't even have a mouse with multiple scroll wheels).
We should think about the future. Currently, there is a new event type called MouseWheelPreciseMoved, which sounds rather ugly. It is definitely a candidate for renaming to MouseWheelMoved in SFML 3, however that would break some code again. I don't know whether it might make more sense to extend the current MouseWheelMoved event with 2 new members:
   struct MouseWheelEvent
   {
      int delta; // <- deprecated
      int x;
      int y;
      float highPrecisionDelta; // <- new
      Mouse::Wheel wheel; // <- new
   };

In SFML 3, delta would be removed. highPrecisionDelta is either left as-is, or renamed to delta (requiring code changes). That's why I considered using a different name that makes sense on its own, e.g. offset or similar. The drawback of this approach is that the relation to the delta is not immediately clear -- but this is just for the moment.

I think for now the MouseWheelPreciseMoved event is ok but you have a good point: with v3 we should have
   struct MouseWheelEvent
   {
      float delta;
      int x;
      int y;
      Mouse::Wheel wheel;
   };

(Devs would have in any case to adapt their code when migrating to v3 so something that small should not be an issue.)

Might want to create your own PR and discuss further things there. :wink:

You're right. I didn't want to create a PR as long as nobody supported the idea, but it seems like people so far agree with it :)
Please continue all the discussion in 837.


Log reward for each environment step.

Hi @Denbergvanthijs, could you suggest me an easy way to log the reward value for each step?

A quick and dirty solution would be to print the reward within the _step() function of the environment:
https://github.com/Denbergvanthijs/imbDRL/blob/bedf1c7bb83a75427d2ea3ed07b17e2ef55f8448/imbDRL/environments/classifierenv.py#L59
Otherwise, a callback function would be better


CPU Metric normalization

A query like:
performanceCounters  | summarize avg(value) by name, category
would return:
name	category	avg_value
% Processor Time	Process	(no change from today)
% Processor Time	Processor	(no change from today)
CPU Utilization by Process	ApplicationInsights	Calculated by the SDK as (Process/% Processor Time) / Number of Cores

wrong repository. You need to move it to -dotnet-server


LPAL-463/LPAL-523 Unit tests and refactor for Postgres data access classes

Purpose
Improve the testability of data access classes in service-api which execute queries against the database. Start filling out unit tests for these classes.
Fixes LPAL-463
Approach
Previously, I introduced a DbWrapper class to encapsulate (crudely for now) access to Postgres itself. This made it possible to start testing data access classes without a real database.
This PR injects a DbWrapper into all of the data access classes so they become testable (as the DbWrapper can be mocked/stubbed).
I suggest we put this into UAT (thorough!) to ensure that nothing has broken.
Learning
These classes are still difficult to work with, as they construct and execute complex SQL queries. The table gateway metaphor doesn't really hold up, although this appears to be the original pattern. The Users table, for example, packs all of the user's address data, authentication tokens, contact details etc. into a document which is saved into a field as JSON. Consequently, the UserData class manages authentication, email address changes, physical addresses, authentication tokens and so on. This means it's a huge class with a lot of business logic embedded in it.
In addition, access to the tables is very raw, and uses arrays in a lot of places. This means that validation logic for queries is also shoe-horned into this class (as the objects representing table rows are raw result objects or even just arrays), resulting in methods with lots of conditional branching. This makes them harder still to test.
The presence of half a dozen mocks in some of these tests demonstrates the problem. I have struggled to come up with a better way of testing them, and have ended up writing some convenience methods and shortcuts for common testing patterns (e.g. result sets with X rows in).
While testing this, I also realised there are other parts of the code we don't exercise with our tests. For example, we don't have any tests which run the stats generation commands on the command line. I have manually tested generate-stats and account-cleanup tasks to ensure that the commits in this branch don't cause any issues for those commands.
Checklist

[X] I have performed a self-review of my own code
[X] I have updated documentation (Confluence/GitHub wiki/tech debt doc) where relevant
[X] I have added tests to prove my work
[ ] I have added mandatory tags to terraformed resources, where possible
[ ] If I added a package.json or composer.json, I also made sure this is included in the script in .github/workflows/dependabot-update.yml
[ ] The product team have tested these changes

@nickdavis2001 please re-review as I made a couple of extra changes for breakages in cron scripts, which I'd neglected to test thoroughly.


browser.platform.version raises error for macs sometimes

Description
When I try to access the browser.platform.version for some Macintosh User-Agents, a NoMethodError for the gsub call is raised, because the version could not be parsed properly and is nil.
When I look at the code for mac, gsub is directly called on the evaluated regex:
ua[/Mac OS X\s*([0-9_\.]+)?/, 1].gsub("_", ".")

But the regex seems to be nil in some cases.
Other platforms, like windows, return a "0" instead of nil. (But they also don't need that gsub call.)
ua[/Windows NT\s*([0-9_\.]+)?/, 1] || "0"

How to reproduce
Unfortunately we didn't logged the User-Agents on our system. Therefore this issue is hard to reproduce at the moment.
What do you expect
Return "0", like for other platforms.
What happened instead
NoMethodError raised.
Software:

Rails version: 4.2.6
Browser gem version: 2.1.0

Full backtrace
E, [2016-06-18T16:34:00.865437 #2209] ERROR -- : [3d4de58] Dispatcher error: NoMethodError: undefined method `gsub' for nil:NilClass
/.../ruby/2.1.0/gems/browser-2.1.0/lib/browser/platform/mac.rb:6:in `version'
/...ruby//2.1.0/gems/browser-2.1.0/lib/browser/platform.rb:90:in `version'

Can you provide the user agent that is raising the failure?


SAMD21 compatibility (Arduino zero)

Hi, I'm working on porting this library into a SAMD21 MCU (same as Arduino Zero), has anybody already tried it? Do you see any critical issue? I'm wondering so since it has not been implemented yet. Any suggestion on how to deal with this would be really appreciated.
Thank you, hope to contribute to this library :)

A port to the SAMD21 would be great. AFAIK no one has worked on a port yet. Looking at the data sheet, the SAMD21 has several possibilities to generate pulses using either TC or TCC (perhaps even DMAC). The AVR code could be used as basis for your port. TC and TCC will require one interrupt per step, so monitoring cpu load by the interrupts and fast code are essential for high speed operation.  If any advanced feature of TCC may be of help, I have not checked.
In general an oscilloscope is of great help. For either checking the generated pulses or debugging interrupt routines. If you have none, best to get a cheap digital one.
And yes, if this port project is neither of fun for you or in any respect mission critical to you, better to not try. It will take quite some time and debugging interrupts is not for everyone.  In case you will start, please keep me involved. Perhaps I can help.
Looking forward to your pull request :-)

Hi @gin66 , thanks for your reply. As you said this port would take quite a lot of time, I'm now considering other ways to control my stepper motors. Maybe in the end I will decide to port this library to SAMD21, we'll see! ;)


fix: patch for release build

After two days of running every build configuration change I can think of I just can't figure out the root cause of https://github.com/bytecodealliance/StarlingMonkey/issues/50.
I cloned spidermonkey-wasi-embedding and ran a release build against the same Rust toolchain used in js-compute-runtime and was able to get js-compute-runtime to build correctly against it. But StarlingMonkey just won't link against this libjsrust.a.
This implements a workaround that at least gets the release build to work, by copying the debug build's libjsrust.a instead. Perhaps it points to something in the StarlingMonkey configuration that isn't properly updating the Rust build to be a release instead of a debug build in the right way, I'm just not sure how duplicate function errors get determined in the linker and if it has anything to do with structural code similarity or not.
 Help figuring out the root case on https://github.com/bytecodealliance/StarlingMonkey/issues/50 would be very welcome.

This PR also adds the release build into CI to avoid future regressions.

While this resolves https://github.com/bytecodealliance/StarlingMonkey/issues/50, it's only a temporary workaround until the root cause in the Cmake corrosion configuration can be found.


feat: add optimism network

See #242 for what is needed to add a new network to the exporter.

@ImmanuelSegol this is the issue

@ImmanuelSegol this is the issue

ok ill take it

I'm going to start working on this again


v2.3.0-beta.7 Temperature selector text not colored (maybe a bug?)

Describe the bug
Thermostat target temperatures are only colored when heat_cool mode is selected. When mode is set to heat or cool, the text remains white.
Expected behavior
Expecting target low temperature to be orange and target high temperature to be blue regardless of mode.
Screenshots

Informations (please complete the following information):

OS: Mac OS
Browser/App: Chrome
Bubble Card version: v2.3.0-beta.7
Home Assistant version: 2024.11.x

Thanks for your support! Apologies for adding yet another issue in your release backlog :-)

Hi! This is the expected behavior but I hesitate for that, since there is only one value displayed, it makes more sense when there are two values.
What do you think?

I still don't know, the issue is that in some entities I can't be sure of what type of device it is (AC or heater), so I can't define a color by default. But it is easy to modify it with just a single line in the custom styles section.

I've tried to change it using styles but haven't figured it out yet. If you can suggest how to do it, that would be great :-)

You can just add this for heater:
.bubble-temperature-display {
  color: var(--state-climate-heat-color);
}

And this for AC:
.bubble-temperature-display {
color: var(--state-climate-cool-color);
}
I will close this, but don't hesitate to ask if you have more questions 🙂

Thanks, I'll just comment here what I ended up with since your snippet assumed different entities for heater and AC while I wanted the text color to change based on current mode:
.bubble-temperature-display {
  color: ${state === "heat" ? "var(--state-climate-heat-color)" : "var(--state-climate-cool-color)" }
}

Thanks for your help!

Even better, thanks for sharing this! 👌


Intellisense stops working with javascript

5Issue Type: Bug

Fresh download of portable version of Insider, 1.42.0
No plugins installed
Opened a react-native project
IDE starts "initializing JS/TS language features"
After maybe 20 seconds of work intellisense stops working

The same thing with the non insider version, 1.41.1. Previous version (1.40.2) works fine.
 After restarting VS Code, does that fix the problem?

Can you please try upgrading your workspace to use typescript@next by installing this extension. After restarting VS Code, does that fix the problem?

Yes, it fixes the problem, thanks. Is there a known "bug" in the current stable version?

Closing as fixed in typescript 3.8 which will be released with VS Code 1.43


About - Optional dependences - Comments

Here are some comments that hopefully make these instructions related to optional requirements a bit easier to follow. In particular, the reference to future commands. Maybe put a sub-title such as Future Installation Method on this section so the readers do not have to read the text to understand the pypi option is not relevant, not the install_file_process to the installation at hand. Some suggested text:
To enable file owner information extraction on Windows, you may need to install pywin32. This is an optional step but is recommended  to enhanced the functionality of the file process library. If it is already installed on your system it will be detected and a message will indicate the requirements are already satisfied. Use the following command install pywin32:
pip install pywin32
Installing Optional Developer Dependencies:
The file processing library includes optional developer dependencies specified in the pyproject.toml file. Currently, these dependencies cannot be installed directly from GitHub. (To be addressed in a future update, see Future Installation Method below)
To install these optional dependencies, you will need to manually execute pip install <library_name> command  for each library listed under the developer dependencies section in pyproject.toml. (I am assuming this is correct)
Future Installation Method Once Published on PyPI:
After the project is published on the Python Package Index (PyPI), you will be able to install all optional developer dependencies with a single command. This command will be:
pip install file_procesing_tools[developer]

Thanks for the overview - I've made changes and re-published the documentation


Avoid recreating implicit capabilities for every variant

@bot-gradle test this

I've triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test and merge

I've triggered a build for you.


GH Actions: bust the cache semi-regularly

Caches used in GH Actions do not get updated, they can only be replaced by a different cache with a different cache key.
Now the predefined Composer install action this repo is using already creates a pretty comprehensive cache key:

ramsey/composer-install will auto-generate a cache key which is composed of
the following elements:

The OS image name, like ubuntu-latest.
The exact PHP version, like 8.1.11.
The options passed via composer-options.
The dependency version setting as per dependency-versions.
The working directory as per working-directory.
A hash of the composer.json and/or composer.lock files.

This means that aside from other factors, the cache will always be busted when changes are made to the (committed) composer.json or the composer.lock file (if the latter exists in the repo).
For packages running on recent versions of PHP, it also means that the cache will automatically be busted once a month when a new PHP version comes out.
The problem
For runs on older PHP versions which don't receive updates anymore, the cache will not be busted via new PHP version releases, so effectively, the cache will only be busted when a change is made to the composer.json/composer.lock file - which may not happen that frequently on low-traffic repos.
But... packages in use on those older PHP versions - especially dependencies of declared dependencies - may still release new versions and those new versions will not exist in the cache and will need to be downloaded each time the action is run and over time the cache gets less and less relevant as more and more packages will need to be downloaded for each run.
The solution
To combat this issue, a new custom-cache-suffix option has been added to the Composer install action in version 2.2.0. This new option allows for providing some extra information to add to the cache key, which allows for busting the cache based on your own additional criteria.
This commit implements the use of this custom-cache-suffix option for all relevant workflows in this repo.
Includes updating the ramsey/composer-install action to v2. (not sure why you were still on v1, but what with set-output having been deprecated, you probably want to be on the latest version to prevent future problems)
Refs:

https://github.com/ramsey/composer-install/#custom-cache-suffix
https://github.com/ramsey/composer-install/releases/tag/2.2.0

Thanks, I never realized this.
Could you please check the failing yaml linting?

Thanks, I never realized this.

In most cases, it's not typically problematic, but especially for repos supporting a wider range of PHP versions, it's good to bust the cache once in a while.

Could you please check the failing yaml linting?

I did, but I'm not sure how to fix this, it basically says it expects quotes around the ${{ date... }} "formula", but as there are quotes used _within that bit as well, I'm a little worried that this will cause incorrect results/yaml parse errors.


Nepali_nlp module is not installing

it shows following error while trying to install as: "pip install Nepali-nlp".
ERROR: Could not find a version that satisfies the requirement Nepali-nlp
ERROR: No matching distribution found for Nepali-nlp

Did you check with steps in README
!pip install git+https://github.com/sushil79g/Nepali_nlp.git
Tried and working in my system (both window and Linux)
if you are comfortable with colab way, here is the playground link:
https://colab.research.google.com/drive/1qkVsF72ncuTW3PYMAZ4wEpowkaaYtAZd?usp=sharing
let me know if the problem still persist

haven't heard you since then, closing this issue for now.


Simplify by separating Interface into just Command or Topic

Maybe look at how github.com/hawx/img uses this package before thinking about merging this.


Feature/192 rounds

Should i set "self._rows_left_before_rounds = 1 or 0" i.e should it immediately go into rounds

I think we should consider just setting self._is_ringing_opening_row = true
I haven't so far been at a practice where someone has needed to call Rounds in RingingRoom, but as a call of rounds IRL is often after a fireup, it might be worth calling self._rhythm.return_to_mainloop(). That would clear if Wheatley is currently waiting on a bell, though it wouldn't be sufficient to stop Wheatley waiting for other bells later in the row.

I've set the first suggestion. Without going into too much of the internals, I can see setting to rounds doesn't bring you back to the start which is the intention of 'rounds'

I'm not quite sure what you mean here - the row generator gets reset every time Wheatley goes into changes, and if Bot._is_ringing_starting_row == True then Bot won't consume any more rows from the row generator and so the touch can't stop.  If I'm correct and this is fine then I'm happy to merge this, but I may well not be so it's worth being sure.  Also, if you could put something in the CHANGE_LOG about this PR then that'd be great - otherwise I'll do it just before merging so it's fine.
Sorry for the inactivity - the deadline for my degree project has just passed, and I have finals coming up...

Completely understand - I'll take another look on Fri and check it should work as expected

Having a look at the logic. I have some questions (bear of little brain)...
I've added method:  _on_rounds - that sets _is_ringing_opening_row = true
then method: generate_next_row sets _row = _opening_row
method: start_next_row if _rounds_left_before_method == 0 then it sets _is_ringing_opening_row to false
so I think _rounds_left_before_method should also be set to none
what do you think - I'm still going through the logic... So please bear with... I have my own RR set up so I can probably drop the code in to the lib in venv and test it

so I think _rounds_left_before_method should also be set to none

This is definitely correct, but I think _rounds_left_before_method is already set to None when Wheatley initially goes into changes.  In all honesty, this whole 'what is Wheatley doing?' system is a giant potential source of bugs - it should be a state machine (with states like RingingRounds, RingingMethod, Idle, etc.) but AFAIK there isn't a nice way to do this in Python.

what do you think - I'm still going through the logic... So please bear with... I have my own RR set up so I can probably drop the code in to the lib in venv and test it

You shouldn't need your own local RR server to test this out - but if you do want to test it by running Wheatley server-side then you can override where the server looks for Wheatley with the RR_WHEATLEY_PATH environment variable (see here).  Setting this will override the copy installed by Pip.

Actually, thinking about it, I'm not sure what'd happen currently in the edge case where someone calls Rounds! between Go and the start of the method (I have too much revision to check it out).  In this case, AFAIK the counter is still counting down and Wheatley will continue into changes.  So probably better safe than sorry and set _rounds_left_before_method in Bot._on_rounds.

Thanks Ben - when you're free of study pressure we can go over this a bit
more.
On Sat, 29 May 2021 at 16:25, Ben White-Horne @.***>
wrote:

Actually, thinking about it, I'm not sure what'd happen currently in the
edge case where someone calls Rounds! between Go and the start of the
method (I have too much revision to check it out). In this case, AFAIK the
counter is still counting down and Wheatley will continue into changes. So
probably better safe than sorry and set _rounds_left_before_method in
Bot._on_rounds.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kneasle/wheatley/pull/199#issuecomment-850851070, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AF32XV4PIF3X46UICNZSHNTTQEBOTANCNFSM44PGGS4A
.

Thanks Ben - when you're free of study pressure we can go over this a bit more.

Cool!  I'd be happy to merge this PR as it stands if Bot._on_rounds() sets self._rounds_left_before_method = None (perhaps with a comment about the Rounds after Go edge case)... I'm not 100% sure it's necessary but it seems like a wise move anyway.  @centreboard, what do you reckon?

I'm not happy with it... I'd like to poke around a little bit more.. If I can't do better - If you have stop at rounds it still does that. i.e. I think it should take you to where you'd be if you've just done look to

The only thing I think I'm a bit unsure of is if stop at rounds is set and you call rounds it will just stop there. All other functionality I'm fine with and the stop at rounds is kinda what it's been told to do...  I'm honestly not sure what's up, because I've installed exactly the same version and run it on my PC and it works fine.  The rogue build CI run is also still hanging around - I should probably ask the help peeps about it.  But these are not actually an issue and I can merge regardless...

 I'm honestly not sure what's up, because I've installed exactly the same version and run it on my PC and it works fine. The rogue build CI run is also still hanging around - I should probably ask the help peeps about it. But these are not actually an issue and I can merge regardless...

 I'm honestly not sure what's up, because I've installed exactly the same version and run it on my PC and it works fine. The rogue build CI run is also still hanging around - I should probably ask the help peeps about it. But these are not actually an issue and I can merge regardless...

pylint issue seems to have been fixed by updating it #203
Have you tried removing the required build check and adding it again?
https://docs.github.com/en/github/administering-a-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule

Is that how to rerun the checks?

Have you tried removing the required build check and adding it again?
https://docs.github.com/en/github/administering-a-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule

Aha yes that's fixed it!  Is everyone happy for this to be merged?

I'm happy with it - it makes sense and seems to do what we want. - thanks again for all the help!


Exception: Invalid device_id argument supplied 0. device_id must be in range [0, 0).

hi, i install it rcv that works for intel, like me i have, i was about to open go-web-dml, it appear error that Exception: Invalid device_id argument supplied 0. device_id must be in range [0, 0).

is there way to bypass this?

what's your GPU card?

i have this problem too.
my gpu is 660m


Rate Limit

General Troubleshooting

[ x] I have checked for similar issues.
[ x] I have updated to the latest JDA version
[ x] I have checked the wiki and especially the FAQ section for similar questions.

Question

I have try to shutdown my bot but i get this ugly message
[DefaultShardManager] INFO RateLimiter - Waiting for 1 bucket(s) to finish. Average queue size of 0 requests
How i can fix this?
Example Code
shardManager.shutdown();

You can't "fix" this.
This was added a while back, with the reason of informing a user about why a bot might still be online (iirc).
That's not something you can disable to my knowledge (I can be wrong here tho)

I mean you can adjust the logging level so the message is not displayed but that won't fix the issue that somehow 1 bucket has 0 requests left.

I mean you can adjust the logging level so the message is not displayed but that won't fix the issue that somehow 1 bucket has 0 requests left.

Not really an issue imo. It's just JDA saying that 1 bucket had 0 requests queued at the time of shutdown, which had to finish first, which in this case would be an instant shutdown.

Ah ok, thanks for help. Now iknow what the message is :)


PyPI release ?

There isn't any PyPI release for this plugin yet ?
I am currently writing a custom importer, and it would be useful to be able to fork a different process for each test to make sure tests do not conflict via sys.modules...

@asmodehn its currently still part of xdist so currently just use pytest-xdist
i plan to move this feature out to this plugin eventually


Random clean up

Just some random cleanup as I was browsing through code.
Mostly removing unneeded 'using' statements
Some grammar fixes
One dead code removal (since it caused confusion with another PR that went in a few days ago and is now unnecessary due to that change)

Looks like this broke CI build


Child process management

This re-implements the child process management bpftrace has, it:

Moves the code to a new module, cleaning up the bpftrace class (#1080)
Optionally uses ptrace to allow USDTs on child processes (#990)
Uses waitpid to monitor the child process, avoiding polling /proc

I've considered using pidfds for this but I don't think it adds anything. It would allows us to poll the fd, but we would still need to wait to reap the child.

Why is StdoutSilencer the last commit in the PR? Seems like it could be the first and not break bisection.

I think it is github being confusing:
$ git log --oneline fbs-github/childproc |head -n4
dc5bff3c Use `ptrace` to allow USDTs to be attached to a child program
55067339 Move process management out of `BPFtrace`
e7504ea6 Add StdoutSilencer
1711ec70 Don't over-read usdt arguments

I've removed the default constructors as copying this object won't work, and rebased onto master. I'll merge this tomorrow :)


4.4.3: Server selection timeout in mongorestore script inside docker-entrypoint.sh

Hi
I'm running mongorestore command to restore dump at the mongo container start using script in docker-entrypoint.sh folder, and it works perfectly in 4.4.2 version.
But I have an error in 4.4.3:
mongodb          | /usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/restore.sh
mongodb          | 2021-01-14T10:23:09.796+0000 error connecting to host: could not connect to server: server selection error: server selection timeout, current topology: { Type: Single, Servers: [{ Addr: localhost:27017, Type: Unknown, State: Connected, Average RTT: 0, Last error: connection() : dial tcp <IP_ADDRESS>:27017: connect: connection refused }, ] }
mongodb exited with code 1

docker-compose.yml
  mongodb:
    image: mongodb
    build:
      context: ./db
      dockerfile: Dockerfile
    hostname: mongodb
    container_name: mongodb
    ports:
      - 27017:27017
    command: --bind_ip_all --quiet

db/Dockerfile
FROM mongo:4.4

COPY ./TestDB.agz /dump/
COPY ./restore.sh /docker-entrypoint-initdb.d/
RUN chmod 777 /docker-entrypoint-initdb.d/restore.sh

ENV MONGO_INITDB_DATABASE TestDB

db/restore.sh
mongorestore --gzip --archive=/dump/TestDB.agz

During initialization the server is now only listening on the unix socket $TMPDIR/mongodb-27017.sock
https://github.com/docker-library/mongo/pull/443

During initialization the server is now only listening on the unix socket $TMPDIR/mongodb-27017.sock
https://github.com/docker-library/mongo/pull/443

mongoimport doesn't seem to work when specifying the host as the unix socket.
A quick google search reveals this ticket from a few years back which was closed as won't fix
https://jira.mongodb.org/browse/TOOLS-620

mongoimport doesn't seem to work when specifying the host as the unix socket.
A quick google search reveals this ticket from a few years back which was closed as won't fix
https://jira.mongodb.org/browse/TOOLS-620


Cannot decrypt line

I've updated to 0.33 and started getting this error message.
I have 2 leak sensors and 2 groups per each in ajax app.
Integration is configured for 2 zones.
2020-07-16 10:59:04 WARNING (MainThread) [pysiaalarm.base_sia_server] Decrypting last line: F39B0079"*SIA-DCS"2826L0#FF8BA34[9B4A82E34836CFFDFCE9E66CE79C71AB3BAAAE342A144694D66CF0AFAE598DE7DE267FBC6A23D0293ED0E2B7ACCDF277 could not be parsed as a SIAEvent, content: ߈@\xb4,\x9dsm\x88<
k\xae@v\xfdNri0/RP0000]_07:59:13,07-16-2020

Should be fixed with v0.3.4, please check!

The issue might actually be related to the encryption key mismatch
Thanks for the update anyway 👍


Possibly incorrect docstring in C4XGate

Environment

Qiskit Terra version:
qiskit                   0.37.2
qiskit-aer               0.10.4
qiskit-terra             0.21.2

Python version:
Python 3.9.12

Operating system:
macOS Monterey 12.5.1

What is happening?
The docstring of C4XGate's _define method has this QASM implementation:
gate c4x a,b,c,d,e
{
    h e; cu1(pi/2) d,e; h e;
    rc3x a,b,c,d;    <------ THIS LINE (1Q)
    h e; cu1(-pi/2) d,e; h e;
    rc3x a,b,c,d;    <------ THIS LINE (2Q)
    c3sqrtx a,b,c,e;
}

but the constructed circuit is slightly different.
 rules = [
    (HGate(), [q[4]], []),
    (CU1Gate(numpy.pi / 2), [q[3], q[4]], []),
    (HGate(), [q[4]], []),
    (RC3XGate(), [q[0], q[1], q[2], q[3]], []),      <------- THIS LINE (1P)
    (HGate(), [q[4]], []),
    (CU1Gate(-numpy.pi / 2), [q[3], q[4]], []),
    (HGate(), [q[4]], []),
    (RC3XGate().inverse(), [q[0], q[1], q[2], q[3]], []),  <------- THIS LINE (2P)
    (C3SXGate(), [q[0], q[1], q[2], q[4]], []),
]

It makes sense that line rc3x a,b,c,d; (at 1Q) corresponds to (RC3XGate(), [q[0], q[1], q[2], q[3]], []) (at 1P) but rc3x a,b,c,d; (at 2Q) corresponds to  (RC3XGate().inverse(), [q[0], q[1], q[2], q[3]], []), (at 2P) inverse version of the gate?
I'm not sure if I understand.
How can we reproduce the issue?
It's a doc issue.
What should happen?
The doc string should be explicit or fixed.
Any suggestions?
One idea is to use rcccx_dg gate that qiskit constructs when an inverse of RC3XGate is required. Or use some other convention to differentiate between gates and its inverses as specified by QASM.
I'd be happy to open up a PR if that's the case.

Maybe the best way would be using the same definition as in the qelib1.inc, which is
gate c4x a,b,c,d,e
{
    h e; cu1(pi/2) d,e; h e;
    c3x a,b,c,d;
    h e; cu1(-pi/2) d,e; h e;
    c3x a,b,c,d;
    c3sqrtx a,b,c,e;
}

I think the convention is usually that the docstring matches that decomposition there.


Update background.html

Updated page: https://trello.com/c/NjYzFHh9

Hi @PanosParalakis - me and Alex need to review the page in the review app. We'll let you know when the PR is ready to merge. Thanks.

Hey @PanosParalakis this is ready to merge 👍


Added public API for Container resource

JS docs for the properties of a container resource
I confirm I have signed the Contributor License Agreement.

Maybe we should hold off exposing model api, the others are fine. With the changes to render component, we have new API to create entity with model, or entity with render on it.

Ah, there's interesting to hear that the API might change.

Removed model

it might not change (and likely will not), but we might not make it public and only expose the new api


TypeError: 'NoneType' object is not iterable

Basic test in standalone mode
 python3 -i -m pytradfri IP

results in error
Traceback (most recent call last):
  File "/usr/lib/python3.8/runpy.py", line 192, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/lib/python3.8/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File ".../venv/lib/python3.8/site-packages/pytradfri/__main__.py", line 76, in <module>
    moods = api(gateway.get_moods())
  File ".../venv/lib/python3.8/site-packages/pytradfri/api/libcoap_api.py", line 96, in request
    return self._execute(api_commands, timeout=timeout)
  File ".../venv/lib/python3.8/site-packages/pytradfri/api/libcoap_api.py", line 90, in _execute
    api_command.result = _process_output(return_value, parse_json)
  File ".../venv/lib/python3.8/site-packages/pytradfri/command.py", line 68, in result
    self._result = self._process_result(value)
  File ".../venv/lib/python3.8/site-packages/pytradfri/gateway.py", line 115, in process_result
    return [self.get_mood(mood, mood_parent=mood_parent) for mood in
TypeError: 'NoneType' object is not iterable

>>>

pytradfri 6.4.0 on linux.
README examples like api(lights[1].light_control.set_dimmer(50)) still work, though.
Any idea what's happening?

Do you have any moods setup when you look in the IKEA app?

Yes I saved a couple of moods.

The example doesn’t have moods, that’s probably why it works. What happens if you comment those moods line out in the main file in your lib folder?

Yes, if I comment out the moods lines it works. Thanks! I yet have to fully understand the authentication mechanism, but at least now I can run something without errors!
Is the problem with moods a bug or some king of a feature?


[Public/Global - Microsoft Azure Attestation Service] Adding August 2022 public Microsoft Attestation API version

Data Plane API - Pull Request
SevSNP VM attestation type goes public and with the PR is exposed to the GA API of the Microsoft Azure Attestation service.
API Info: The Basics
Most of the information about your service should be captured in the issue that serves as your engagement record.

Link to engagement record issue: https://github.com/Azure/azure-rest-api-specs/issues/20892

Is this review for (select one):

[ ] a private preview
[ ] a public preview
[x] GA release

Change Scope

Added 2022-08-01 swagger definitions containing SevSNP attestation type.
Added corresponding examples related to the enabled attestation type.
Updated specification/attestation/data-plane/readme.md

Notes
The LintDiff errors should be suppressed because of two reasons:

the definition of the openid configuration endpoint follows the Open Id spec, see https://openid.net/specs/openid-connect-core-1_0.html
switching from the "snake" case to the camel case would be customer breaking changes

❔Got questions? Need additional info?? We are here to help!

 Contact us!
The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.

💬 Teams Channel
💌 email

Click here for links to tools, specs, guidelines & other good stuff
Tooling

Open API validation tools were run on this PR. Go here to see how to fix errors
Spectral Linting
Open API Hub

Guidelines & Specifications

Azure REST API Guidelines
OpenAPI Style Guidelines
Azure Breaking Change Policy

Helpful Links

Azure DevTools Wiki

fix https://github.com/Azure/azure-rest-api-specs/issues/20892

The LintDiff errors should be suppressed because of two reasons:

the definition of the openid configuration endpoint follows the Open Id spec, see https://openid.net/specs/openid-connect-core-1_0.html
switching from the "snake" case to the camel case would be customer breaking changes

/azp run

/azp run

/azp run

This PR is not structured correctly to facilitate review of a new API version. The first commit should copy the previous version, the second commit should update the APIView and then the next commit should contain the bulk of the new API changes.

This PR is not structured correctly to facilitate review of a new API version. The first commit should copy the previous version, the second commit should update the API version and then the next commit should contain the bulk of the new API changes.

Thanks for that info. Could you help us and point us to where is this procedure documented so we can enlighten the team moving forward?

This PR is not structured correctly to facilitate review of a new API version. The first commit should copy the previous version, the second commit should update the API version and then the next commit should contain the bulk of the new API changes.

Updated the PR to contain 3 commits instead of one

This looks good to me but you will need to fix the LintDiff errors.

This looks good to me but you will need to fix the LintDiff errors.

FWIW, the LintDiff errors are intentional - the spec which defines these elements uses snake_case.

This looks good to me but you will need to fix the LintDiff errors.

Please see the comment above related to the LintDiff errors: https://github.com/Azure/azure-rest-api-specs/pull/20890#issuecomment-1260056877

Updated SevSNP API's tag from attestation to the capitalized Attestation.

@JeffreyRichter and @tjprescott could you please re-approve the PR since I updated the SevSNP API's tag. Thank you

@LarryOsterman here's the link to the documentation:
https://dev.azure.com/azure-sdk/internal/_wiki/wikis/internal.wiki/83/Manual-Process-Adding-new-API-version

@JeffreyRichter is your approval the approval of the REST API Stewardship board for this GA service version?

@JeffreyRichter is your approval the approval of the REST API Stewardship board for this GA service version?

Yes


Add license

Add a license so people can use this personally

Hey @jhult sorry I didn't merge your PR!  I've added an MIT license and a README though, hope this helps!


Multiple strategies not getting events from store

Since store is a singleton.  It looks like multiple strategies are not getting notified of events.

Seems to be working now


CPU spikes in netty 5 when no requests

when using netty 5 @<PHONE_NUMBER>311a1854748d0274552e27007429a6
java version "1.7.0_60"
Java(TM) SE Runtime Environment (build 1.7.0_60-b19)
Java HotSpot(TM) 64-Bit Server VM (build 24.60-b09, mixed mode)

uname  -a
Linux testbox 2.6.18-238.el5 #1 SMP Thu Jan 13 15:51:15 EST 2011 x86_64 x86_64 x86_64 GNU/Linux

We have a proxy like application which when loaded tested was working fine but when the request were stopped 2 of the nioeventloops started spiking the CPU. We have been seeing this behaviour quite often but have not been able to reproduce this. We added yourkit to see this issue, sadly couldnt save the snapshopt (yourkit crashed) but I have the following screenshots to explain :

is this the same as the selector bug in JDK ? if so any workarounds ?

Please try again with latest release and let us know if you still see it.


Possible representation bug in uploads part of JSON audit log format

I have the following entry in the JSON audit log format:
...
    "uploads": {
        "info": [
            "file_size",
            48458,
            "file_name",
            "example.png",
            "content_type",
            "<Unknown Content-Type>"
        ],
        "total": 48458
    }
...

Within the info tag, there is a list of items and not a list of key-value pairs as would be expected. It might have to do with the way the data is represented within ModSecurity (-> corresponding native audit log format part "J" is a CSV), but this seems to be a bug to me.

Linking this issue with #1174, as they seems to be on the same piece of code.

Not the same issue as #1174, but looks like an easy fix. msc_logging.c:1363 opens this with yajl_gen_array_open instead of yajl_gen_map_open. Not sure why I did this :p I'll have a PR for this within a day or two.

Thanks @p0pr0ck5 ;)

Thank you guys.

@dune73 can you try the fix in https://github.com/p0pr0ck5/ModSecurity/commit/e54b1504fc0105248b874b4f50b3f9614c347679? I won't have time to test for a bit but this should resolve the issue, small oversight on my part. We don't log file upload data so I wasn't as thorough as I should have been.

^ Once this is tested I'll submit the PR

Looks good here:
    "uploads": {
        "info": [
            {
                "content_type": "<Unknown Content-Type>",
                "file_name": "tmp1",
                "file_size": 457
            }
        ],
        "total": 457
    }

Thank you for the quick fix.

Pull request #1181 was merged! thanks!


Rollup Segment Converter

Added rollup segment converter that supports segment concatenation
and simple rollup.
Added ValueAggregator interface along with SUM, MAX implementation.
Added unit test for rollup segment converter

Codecov Report

Merging #3012 into master will increase coverage by 10.07%.
The diff coverage is 73.72%.

@@             Coverage Diff             @@
##           master    #3012       +/-   ##
===========================================
+ Coverage   59.74%   69.82%   +10.07%
===========================================
  Files         917      922        +5
  Lines       43389    43507      +118
  Branches     5931     5944       +13
===========================================
+ Hits        25923    30379     +4456
+ Misses      15545    11091     -4454
- Partials     1921     2037      +116

Impacted Files
Coverage Δ

...re/minion/rollup/aggregate/MaxValueAggregator.java
0% <0%> (ø)

...inion/rollup/aggregate/ValueAggregatorFactory.java
44.44% <44.44%> (ø)

...re/minion/rollup/aggregate/SumValueAggregator.java
60% <60%> (ø)

...edin/pinot/core/minion/RollupSegmentConverter.java
86.56% <86.56%> (ø)

...not/core/minion/rollup/RollupRecordAggregator.java
95% <95%> (ø)

...lix/EmptyBrokerOnlineOfflineStateModelFactory.java
86.66% <0%> (-13.34%)
:arrow_down:

...inot/transport/netty/NettyTCPClientConnection.java
82.31% <0%> (-4.77%)
:arrow_down:

...nsport/netty/PooledNettyClientResourceManager.java
85.41% <0%> (-4.17%)
:arrow_down:

...regation/function/customobject/QuantileDigest.java
47.81% <0%> (ø)
:arrow_up:

... and 289 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 3606ace...2b106a3. Read the comment docs.


Add the watchosArm32 target

Adding the watchosArm32 target, required for the Apple Watch Series 3 [ref], for which, the latest watchOS version (watchOS 7) is still supported [ref].

Thanks, @nunobaldaia! If 32-bits is still relevant in this case, we should support it. :blush:


Debugging untitled file in IW shows unbound breakpoints

Breakpoints are not considered verified if the ITextFileService says the file that they're in is dirty. https://github.com/microsoft/vscode/blob/e00b25cc55a1150d86fa54f9b997d97daf530379/src/vs/workbench/contrib/debug/common/debugModel.ts#L887
We should have a way for the debug adapter to signal that it supports debugging dirty/unsaved files. Should this be another flag in DebugSessionOptions for startDebugging, or a flag on the adapter in package.json?
Interestingly, this currently works on notebooks by accident. @rebornix, if I wanted to make the above check correct for notebook editors, is there a different service that I need to ask whether a notebook editor is dirty?

And this needs https://github.com/microsoft/vscode-jupyter/issues/10599 fixed