Conflicting Dependencies on Fedora 37

Describe the bug
When I try to install the dependencies with this command:
$ sudo dnf install g++ make SDL2-devel SDL2_image-devel v8-devel lcms2-devel freetype-devel zenity libXi-devel

I get this error:
$ sudo dnf install g++ make SDL2-devel SDL2_image-devel v8-devel lcms2-devel freetype-devel zenity libXi-devel
Last metadata expiration check: 3:23:04 ago on Wed 22 Mar 2023 05:29:51 PM CDT.
Package gcc-c++-12.2.1-4.fc37.x86_64 is already installed.
Package make-1:4.3-11.fc37.x86_64 is already installed.
Package freetype-devel-2.12.1-3.fc37.x86_64 is already installed.
Package zenity-3.43.0-3.fc37.x86_64 is already installed.
Package libXi-devel-1.8-3.fc37.x86_64 is already installed.
Dependencies resolved.

 Problem: cannot install the best candidate for the job
  - nothing provides nodejs-devel(x86-64) = 1:18.12.1-1.fc37 needed by v8-devel-2:<IP_ADDRESS>-<IP_ADDRESS>.1.fc37.x86_64
  - nothing provides nodejs-libs(x86-64) = 1:18.12.1-1.fc37 needed by v8-devel-2:<IP_ADDRESS>-<IP_ADDRESS>.1.fc37.x86_64
============================================================================================================================================================================================
 Package                                         Architecture                        Version                                                     Repository                            Size
============================================================================================================================================================================================
Installing:
 SDL2-devel                                      x86_64                              2.26.3-1.fc37                                               updates                              400 k
 SDL2_image-devel                                x86_64                              2.6.3-1.fc37                                                updates                               18 k
 lcms2-devel                                     x86_64                              2.14-1.fc37                                                 updates                              1.7 M
 v8-devel                                        x86_64                              2:<IP_ADDRESS>-<IP_ADDRESS>.1.fc37                               fedora                                14 k
Installing dependencies:
 SDL2_image                                      x86_64                              2.6.3-1.fc37                                                updates                              103 k
 gmock                                           x86_64                              1.12.1-2.fc37                                               fedora                                59 k
 gtest                                           x86_64                              1.12.1-2.fc37                                               fedora                               167 k
 gtest-devel                                     x86_64                              1.12.1-2.fc37                                               fedora                               252 k
 highway-devel                                   x86_64                              1.0.2-1.fc37                                                updates                              232 k
 libjxl-devel                                    x86_64                              1:0.7.0-5.fc37                                              updates                               58 k
 libtiff-devel                                   x86_64                              4.4.0-4.fc37                                                fedora                               546 k
 libuv-devel                                     x86_64                              1:1.44.2-2.fc37                                             fedora                                27 k
 libwebp-devel                                   x86_64                              1.3.0-1.fc37                                                updates                               38 k
 mesa-libEGL-devel                               x86_64                              22.3.7-1.fc37                                               updates                               21 k
 nodejs                                          x86_64                              1:18.7.0-1.fc37                                             fedora                                98 k
 nodejs-devel                                    x86_64                              1:18.7.0-1.fc37                                             fedora                               163 k
 nodejs-libs                                     x86_64                              1:18.7.0-1.fc37                                             fedora                                13 M
 nodejs-packaging                                noarch                              2023.03-1.fc37                                              updates                               21 k
 nodejs20                                        x86_64                              1:19.7.0-13.fc37                                            updates                              2.2 M
 nodejs20-libs                                   x86_64                              1:19.7.0-13.fc37                                            updates                               14 M
Installing weak dependencies:
 nodejs-full-i18n                                x86_64                              1:18.7.0-1.fc37                                             fedora                               8.2 M
 nodejs20-docs                                   noarch                              1:19.7.0-13.fc37                                            updates                              7.7 M
 nodejs20-full-i18n                              x86_64                              1:19.7.0-13.fc37                                            updates                              8.4 M
 nodejs20-npm                                    x86_64                              1:9.5.0-<IP_ADDRESS>.13.fc37                                    updates                              2.3 M
Skipping packages with broken dependencies:
 v8-devel                                        x86_64                              2:<IP_ADDRESS>-<IP_ADDRESS>.1.fc37                              updates                               15 k

Transaction Summary
============================================================================================================================================================================================
Install  24 Packages
Skip      1 Package

Total size: 60 M
Installed size: 275 M
Is this ok [Y/n]:
Downloading Packages:
[SKIPPED] gmock-1.12.1-2.fc37.x86_64.rpm: Already downloaded
[SKIPPED] gtest-1.12.1-2.fc37.x86_64.rpm: Already downloaded
[SKIPPED] gtest-devel-1.12.1-2.fc37.x86_64.rpm: Already downloaded
[SKIPPED] libtiff-devel-4.4.0-4.fc37.x86_64.rpm: Already downloaded
[SKIPPED] libuv-devel-1.44.2-2.fc37.x86_64.rpm: Already downloaded
[SKIPPED] nodejs-18.7.0-1.fc37.x86_64.rpm: Already downloaded
[SKIPPED] nodejs-devel-18.7.0-1.fc37.x86_64.rpm: Already downloaded
[SKIPPED] nodejs-full-i18n-18.7.0-1.fc37.x86_64.rpm: Already downloaded
[SKIPPED] nodejs-libs-18.7.0-1.fc37.x86_64.rpm: Already downloaded
[SKIPPED] v8-devel-<IP_ADDRESS>-<IP_ADDRESS>.1.fc37.x86_64.rpm: Already downloaded
[SKIPPED] SDL2-devel-2.26.3-1.fc37.x86_64.rpm: Already downloaded
[SKIPPED] SDL2_image-2.6.3-1.fc37.x86_64.rpm: Already downloaded
[SKIPPED] SDL2_image-devel-2.6.3-1.fc37.x86_64.rpm: Already downloaded
[SKIPPED] highway-devel-1.0.2-1.fc37.x86_64.rpm: Already downloaded
[SKIPPED] lcms2-devel-2.14-1.fc37.x86_64.rpm: Already downloaded
[SKIPPED] libjxl-devel-0.7.0-5.fc37.x86_64.rpm: Already downloaded
[SKIPPED] libwebp-devel-1.3.0-1.fc37.x86_64.rpm: Already downloaded
[SKIPPED] mesa-libEGL-devel-22.3.7-1.fc37.x86_64.rpm: Already downloaded
[SKIPPED] nodejs-packaging-2023.03-1.fc37.noarch.rpm: Already downloaded
[SKIPPED] nodejs20-19.7.0-13.fc37.x86_64.rpm: Already downloaded
[SKIPPED] nodejs20-docs-19.7.0-13.fc37.noarch.rpm: Already downloaded
[SKIPPED] nodejs20-full-i18n-19.7.0-13.fc37.x86_64.rpm: Already downloaded
[SKIPPED] nodejs20-libs-19.7.0-13.fc37.x86_64.rpm: Already downloaded
[SKIPPED] nodejs20-npm-9.5.0-<IP_ADDRESS>.13.fc37.x86_64.rpm: Already downloaded
Running transaction check
Transaction check succeeded.
Running transaction test
Error: Transaction test error:
  file /usr/lib64/libv8.so.10 conflicts between attempted installs of nodejs20-libs-1:19.7.0-13.fc37.x86_64 and nodejs-libs-1:18.7.0-1.fc37.x86_64
  file /usr/lib64/libv8_libbase.so.10 conflicts between attempted installs of nodejs20-libs-1:19.7.0-13.fc37.x86_64 and nodejs-libs-1:18.7.0-1.fc37.x86_64
  file /usr/lib64/libv8_libplatform.so.10 conflicts between attempted installs of nodejs20-libs-1:19.7.0-13.fc37.x86_64 and nodejs-libs-1:18.7.0-1.fc37.x86_64

To Reproduce
Install the dependencies of Dotto on Fedora 37 with sudo dnf install g++ make SDL2-devel SDL2_image-devel v8-devel lcms2-devel freetype-devel zenity libXi-devel and see conflicting dependencies.
Expected behavior
The installation finishes without any errors.
Desktop (please complete the following information):

OS: Fedora 37

isn't this more sort of a repo maintainer issue?

Sounds like an issue on Fedora's repo to me as well.

Okay. Where would I open this issue then?

let me see if one of my fedora lad can fix the issue, if so i'll share the response here.

So yea, this is a known issue<EMAIL_ADDRESS>you might want to talk to fedora maintainers for this.

Okay, thanks! I guess I'll just wait until it gets fixed if it's already a known issue.


added a step F to vew the pull request in forking exercise closes #251

FYI @johanhellsvik . Thanks!


Internal server error

Browsing trough the pwa.rocks repository I found out that the devsummit site throws internal server error with stack trace :frowning: for the following links:
https://developer.chrome.com/devsummit/sessions/
https://developer.chrome.com/devsummit/sessions/progressiveapps
You might want to take a look at it. :sweat_smile:

Thanks :)


Feature request: add support for LoongArch

I'm requesting support for LoongArch, a RISC-based instruction set architecture developed by Loongson.
Having recently ported VSCodium to LoongArch, I noticed that the Open VSX Registry offers very limited options for C/C++ and Rust debuggers. And none of them offers support for the architecture.
I would like to request native .vsix builds for LoongArch support. I'm also willing to contribute by helping with the CI pipeline updates.

Building Codelldb itself for another arch is not the problem, building LLDB with Python support is.   Right now I'm using binaries from Python Standalone to get portable Python.  As you can see, they don't provide builds for LoongArch.
Another issue is that I don't have the hardware to test or debug on.    And neither does Azure (which is used for CI).
If your distro's repository provides LLVM 18 or later, I'd recommend trying LLDB's own DAP adapter.

Thank you for the detailed explanation. Regarding the issues you mentioned:
For Python Standalone support, I'll look into adding LoongArch support.
As for the hardware limitation, would it be feasible to test the implementation using QEMU emulation?
About LLDB DAP - while it's definitely a promising solution, I noticed it's not yet available on Open VSX (the default marketplace for VSCodium). There's an ongoing discussion about this at https://github.com/llvm/llvm-project/issues/93544, and I am going to see if any progress could be made.


Add Brighton event

Hi would appreciate it if you could add our event. Thanks

@zefman Sorry we were not able to merge this in time. Closing.


nvidia-smi/gpustat does not work in C++ container

gpustat used to work in humancompatible/goattack:cpp. I confirmed this by checking out a commit from the end of August, building the image, and running gpustat.
I think gpustat broke for reasons not related to our changes. When I used the same commit and re-built with --no-cache, gpustat no longer worked.

appears to be resolved now if the image is rebuilt with --no-cache — tested on rnn and vae


Wiring enhancement tasks

https://github.com/Microsoft/pxt-microbit/issues/246

[ ] digital sensors should be simulator with a button

https://github.com/Microsoft/pxt-microbit/issues/245

[ ] analog sensors should be simulator with slider

https://github.com/Microsoft/pxt-microbit/issues/244

[ ] ability to define maximum current for components and insertion of resistors

https://github.com/Microsoft/pxt-microbit/issues/243

[ ] NeoPixel strip should be connected to an external power source. See https://learn.adafruit.com/adafruit-neopixel-uberguide/power

https://github.com/Microsoft/pxt-microbit/issues/242

[ ] allocate free pin when inserting function call

https://github.com/Microsoft/pxt-microbit/issues/241

[ ] detect collision of pin usage in wiring

https://github.com/Microsoft/pxt-microbit/issues/233

[ ] support infinite breadboard

https://github.com/Microsoft/pxt-microbit/issues/226

[ ] IMO the wires should be slightly larger when hovered and
[ ] hovering should work on the wire itself - not just the dots
[ ] the parts front page should have the link to the editor, maybe as a subtitle of the script name
[ ] show logo on board in wireframe mode (daryl)
[ ] handle popup blockers when opening parts view (peli)

https://github.com/Microsoft/pxt-microbit/issues/248
-[ ] Remove hard-coded DAL dependencies from NeoPixel.ts
Currently visuals/neopixel.ts depends on:
String constants "DigitalPin.P", and "NeoPixelMode."
MICROBIT_PIN_0 or something (to the value "7")

Ported issues from pxt-microbit repo

@abchatra - can you please review and close what's needed?

@microsoftsam @riknoll FYI


Suggest change "arch" strings to "x86" and "x64" everywhere?

This is a nitpicky kind of request but it's fairly annoying across the board.
You used the strings of "386" and "amd64" as the abbreviated arch identifiers in a number of places.  However, most of the systems in the rest of the process use x86 and x64, so there are several places where we have to do string conversions.
For example, in go-msi , you wrote the following:
	if arch != "" {
			if arch == "386" {
				arch = "x86"
			} else if arch == "amd64" {

There are at least 3 other places within other tools, or travis/appveyor yml files where similar logic has to be duplicated (filenames, packaging, etc).
Please consider just changing all instances of "386" to "x86" and "amd64" to "x64".
If you would be willing to allow that, then I will submit PR's for all the changes, including the yml files.

I guess within the world of linux , there isn't much consistency.  The package managers generally look for i386 and amd64, so that's what they should both be in most places, but since they aren't, there's no real way to make it right.


Investigate models based on unsupervised learning

Let's investigate models like Anomaly detection and text transformers that are based on unsupervised learning

for classic ML unsupervised learning algorithms let's try Clustering. Some of the application contain these models:

Hiearchical clustering - connectivity based clustering
K-means clustering - centroid based clustering
Principal Component Analysis (PCA)
Singular Value Decomposition (SVD)
Independent Component Analysis (ICA)
Gaussian Mixture Models (GMM) - model based clustering
Density-Based Spatial Clustering of Applications with Noise (DBSCAN) - densitiy based clustering

let's study them and pick one of them, that mostly applicable for our use-case

@h1alexbel the puzzle #139 is still not solved.

for transformers we trying BERT and SRdT (custom one)

@h1alexbel 2 puzzles #139, #154 are still not solved.


Add site name to meta title tags

Currently the meta title tags only use the page name by default.
Apparently there are some arguments against including the site name in the social media meta tags, I think most of our sites could probably use the extra context.
(Presumably these are just the default, and if a user cared enough they could still customise the Facebook and Twitter titles completely?)
TLDR: Suggestion: Make the meta title tags the same as <title> tag by default - i.e. include the site name - but still allow for overrides.

Using the new get_meta_title() method, the title can be overridden. As we usually include the MetadataPageMixin on our base Page model, we can customise this on a site-by-site basis (or even a page by page basis) with something like:
class Page(MetadataPageMixin, wagtailmodels.Page):
    def get_meta_title(self):
        site = self.get_site()
        return '{} - {}'.format(self.title, site.site_name)

If you feel strongly that this should be the default behaviour, we can make that happen. People/sites who want the old behaviour of just the page title could implement get_meta_title() to restore the old behaviour.


[Bug] Super URL Bar theme makes the new Glance feature unusable

Affected Theme

Name: Super Url Bar
Version 1.4.1

Affected Theme Settings

x

Zen Version: 1.0.1-a.17
System OS:  Windows 11
Describe the bug
The Super URL Bar theme makes the new Glance feature in Zen Browser unusable.
To Reproduce
Steps to reproduce the behavior:

Alt + Left Click Mouse the URL
The glance features partially works, it shows the preview window, but the Close and Expand buttons are unclickable.

Expected behavior
The buttons should be clickable. Clicking the Expand button should open the preview in a new tab, and clicking the Close button should close the preview window.
Screenshots/Videos
https://github.com/user-attachments/assets/819635b3-bfce-4035-815a-10b704592d9e

Thanks a lot for the report! I'll fix it right away.
If anyone's curious, it's because of the clip-path. In the past zen versions, i needed to use clip-path to get the background blur working, but luckily it's not needed anymore, so i can remove it anyway, which will fix this issue.
For now you can just disable background blur, but i'll update it asap


Not login to Keybase Client

Keybase GUI Version: 1.0.18-20170216112451+a5b6199
not able to login after windows restarts.

it keep logging in

@zanderz can you help out?


Removed unthrown exceptions from method signatures

Removed throws someException from many methods and constructors
if said exception was never thrown.
For OAuth2TokenProvider.getToken(), changed exception thrown to
match method signature (AssertionError -> AuthenticationFailedException)

Looks good to me.
@Valodim: Any objections to the changes in the openpgp-api library?

Given it's our local copy we can always add it back and handle it if the signature needs to change.


heimdall-gui: fix darwin build

Motivation for this change
ZHF: #122042
cc @NixOS/nixos-release-managers
Hydra failure: https://hydra.nixos.org/build/142504831/nixlog/1
Note that this does NOT yet result in a working heimdall-frontend.app, but is what I could fix in reasonable time. The app now launches, shows in the dock, but is 'not responding' and goes into what appears to be a tight rendering loop with nothing on screen. One CPU is pegged at 100%, and interrupting with lldb only shows AppKit / Qt stuff in the backtrace.
We seem to have a general Qt on Darwin issue here, because I had the exact same problem with Communi.app in #122563.
I hope the wrapQtAppsHook is the correct fix here, and that it is also appropriate for Linux.
Things done

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

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

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

Result of nixpkgs-review pr 123215 at f9419f14 run on x86_64-linux 1

1 package built successfully:

heimdall-gui

1 suggestion:

warning: missing-phase-hooks
installPhase should probably contain runHook preInstall and runHook postInstall.
Near pkgs/tools/misc/heimdall/default.nix:34:3:
   |
34 |   installPhase = lib.optionalString stdenv.isDarwin ''
   |   ^


wast-mode.js

I wrote a similar wast-mode for CodeMirror, might be useful to compare: https://github.com/WebAssembly/wabt/blob/master/demo/wast-mode.js

Thanks! I will investigate this later

Now I'm working on switching to monaco-editor where with great wasm grammar and highlight


feat(ripple): handle touch events

Now handles touch events properly.

Note: Tested it thoroughly already and it works great. Still want to test on more devices manually to make sure it works fine!
Fixes #7062

@DevVersion lint error
ERROR: /home/travis/build/angular/material2/src/lib/core/ripple/ripple-renderer.ts[209, 1]: trailing whitespace

@DevVersion which devices did you test on? We have pretty much everything in the office

@jelbourn I tested it on a few browsers. Mostly desktop browsers.
Chrome 62 (Win), Firefox 57 (Win), Edge, IE11, Safari 11, Chrome 62 (MacOS) and Chrome 62 (Android 7.0)

I'd like to double check on a few devices before merging


Meteor integration with several errors

Hi everyone,
I had to jump a few hurdles in order to setup Semantic with Meteor:
Challenge 1
I have just updated to the most recent meteor and was not aware what the package.json file was. Maybe the integration documentation could refer to https://guide.meteor.com/using-npm-packages.html
Error 1
 While minifying app stylesheet:
   error: Can't load npm module 'autoprefixer' from packages/minifier-postcss_plugin.js. Check your Npm.depends().

Fixed by running
meteor npm install --save autoprefixer
Error 2
Styling still not displayed. Fixed by manually creating custom.semantic.json as recommended in https://forums.meteor.com/t/semantic-ui-not-working/6535/4?u=joaobarcia
Error 3
W20160811-18:13:46.219(1)? (STDERR) ReferenceError: jQuery is not defined
W20160811-18:13:46.220(1)? (STDERR)     at meteorInstall.lib.semantic-ui.definitions.behaviors.api.js (lib/semantic-ui/definitions/behaviors/api.js:1171:5)

Fixed by moving custom.semantic.json as per: http://stackoverflow.com/questions/31504801/jquery-is-not-defined-in-meteor-app#31786101

You can just use our atmosphere packages. I'm not sure about NPM compatibility with Meteor, but my experience working with it hasn't been wonderful.

@jlukic thanks for the quick reply. The process I described was using  the atmosphere packages. And in Meteor forums it seems a couple of people have been facing similar issues

+1 !!


Form macros: multiple improvements

Related to https://trello.com/c/iaRQlj6y/87-toolkit-forms-macros-are-different-in-all-of-the-apps and https://trello.com/c/W3d7VMrO/72-supplier-app-use-frontend-toolkit-macros-3
A few things done here:

allow context vars to be overridden by macro kwargs: this allows apps which need small alterations in the handling of question_content to use these macros.
reordered argument lines alphabetically: this makes it clearer what arguments are present & missing from each invocation.
added some parameters extracted from question_content which had been missing.

I found it hard to decide whether to make this a minor or major version bump seeing as it could hypothetically have unexpected results. In the end I decided to make it minor, because I wouldn't have been able to think of anything specific enough to put in the changelog. "Check everything"? I would have hoped tests would catch any problems.
The only way I could see things being affected is is a question defined e.g. question_content.unit but for some reason deliberately didn't want it expressed.
I'm aware that this touches almost every line here, but I've done this as a number of discrete commits, each performing one simple operation that can be checked for equivalence if you like.

Some of the new possible overrides are kind-of weird to have at all - value, error, type, and probably some others too I can't imagine why you would ever legitimately want to override - but I guess it makes sense for consistency to allow it for all params.

I think you're right about the versioning... any code already using these macros should not break as far as I can tell.
The potential issues arise when switching out local macros for these toolkit macros, but that's a thing that needs to be done with care whatever, and isn't a "break" in the toolkit.

Can you give an example of what you couldn't do before, but you can do now -- because I don't really understand what this is about.

@galund see https://github.com/alphagov/digitalmarketplace-supplier-frontend/pull/748 where most of the macros want to e.g. override the question arg with one piped through question_references. The previous construction here would have happily ignored that, with the macro's setting for question getting the final say, meaning the supplier app had to keep a modified copy of the macros to get the right effect.

Hmm, I still don't get it. The macros are of dubious use in the first place, and if you're literally overriding the one thing they do, then why bother at all? Just call the 'include' directly with whatever arguments you want, and skip the macros altogether?

I am trying to retain compatibility for all consumers of the toolkit. There is one useful effect that the macros give us that you don't get just using the raw includes and that is the body of the macro supposedly starts with a clean context. It's possible to "call" an {% include thinking you're omitting arguments and thereby signifying the defaults, but in the background of your template you have stray context variables colliding with the fairly common names like value, hidden, message.

FWIW I think that more complex substitution of defaults etc should be done outside the template, so that the notional "template designer" person doesn't have to worry about all this stuff. This might be achievable with the existing classes we have (i.e. creating new instances of them and having a special factory method), or creating new classes with the necessary compatibles interfaces with properties that default appropriately.
This could make the macros simpler, even if we still feel we need to keep them because of the context issues? It just feels like we're trying to do too much in the templating layer (in general, though these macros are the example that keeps coming up).

I don't really disagree with you.


Run itests in a docker container

Run chronos related itests in a docker container with all the reqs available
Thanks to @solarkennedy for most of the code that was copied over from the marathon-python project

Looks good! And now a green check-mark.
This will be useful to test against api changes with new chronos versions, and it will allow us to run itests with just docker and not installing chronos on my local laptop!

Nice!


Separates deployment methods.

Updates tests.

@FBRTMaka @lukecampbell please review.  There will be more, but it's a start.

nice! :+1:


Kanban Board for React Group Capstone

For this capstone we are a pair. Me(Garvin Chimone) and Aisha Alselwi will be working together this week
Here is the link to our kanban board. https://github.com/Chimoneg27/Kanban-Board-React/projects/1

Hi @Chimoneg27 & @AlselwiAisha,
Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉
STATUS: APPROVED 🕺🥳

Highlights :dart:

Correct sharing of project tasks :heavy_check_mark:
Good use of kanban template :heavy_check_mark:
Good issues summary :heavy_check_mark:

Optional suggestions
Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better. Some of them were simply missed by the previous reviewer and addressing them will really improve your application.
Important Notes 📝

Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Note: Please, you can now Merge since it is Approved ✅, However if there are any conflicts please resolve them before merging.

Thank you for your time 🙏 and call me if you need help or clarification ☎

This is My GitHub:
This is My linkedIn.
This is My Twitter:
This is My Slack:

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


Tabular Printing for DataFrames

When completed, this PR closes #22.
I don't know if the code is in the right place, nor if it is the right way to implement this feature, but hey, it works!
But it is not ready yet, I'm trying to find a way to give the "second row" (the one with column <types>) a different color to differentiate it from the ones with data values.
iex(15)> Explorer.Datasets.iris |> Explorer.Inspect.df_pretty_inspect()
+--------------+-------------+--------------+-------------+-------------+
| sepal_length | sepal_width | petal_length | petal_width | species     |
+==============+=============+==============+=============+=============+
| <float>      | <float>     | <float>      | <float>     | <string>    |
+--------------+-------------+--------------+-------------+-------------+
| 5.1          | 3.5         | 1.4          | 0.2         | Iris-setosa |
+--------------+-------------+--------------+-------------+-------------+
| 4.9          | 3.0         | 1.4          | 0.2         | Iris-setosa |
+--------------+-------------+--------------+-------------+-------------+
| 4.7          | 3.2         | 1.3          | 0.2         | Iris-setosa |
+--------------+-------------+--------------+-------------+-------------+
| 4.6          | 3.1         | 1.5          | 0.2         | Iris-setosa |
+--------------+-------------+--------------+-------------+-------------+
| 5.0          | 3.6         | 1.4          | 0.2         | Iris-setosa |
+--------------+-------------+--------------+-------------+-------------+

:ok

One thing I'll be loathe to lose in a default inspect is the number of rows, columns, and groups. That is the second line here:
#Explorer.DataFrame<
  [rows: 150, columns: 5]

I wonder if there's a way to include that info with table_rex?

One thing I'll be loathe to lose in a default inspect is the number of rows, columns, and groups. That is the second line here:
#Explorer.DataFrame<
  [rows: 150, columns: 5]

I wonder if there's a way to include that info with table_rex?

I can add these things in the title field, but it wouldn't look great.
Table Rex's API looks really flexible, we can find a way to put this infos somewhere.

What do you think of this layout? It is the one implemented in the last commit.
iex(7)> Explorer.Datasets.iris |> Explorer.DataFrame.table(1)
+-----------------------------------------------------------------------+
|              Explorer DataFrame: [rows: 150, columns: 5]              |
+--------------+-------------+--------------+-------------+-------------+
| sepal_length | sepal_width | petal_length | petal_width | species     |
+==============+=============+==============+=============+=============+
| <float>      | <float>     | <float>      | <float>     | <string>    |
+--------------+-------------+--------------+-------------+-------------+
| 5.1          | 3.5         | 1.4          | 0.2         | Iris-setosa |
+--------------+-------------+--------------+-------------+-------------+

I really like it. Giving myself a moment to think it through.

New aesthetic changes :)
Now the type of the column is in the same cell as the column name.
Output below:
+-----------------------------------------------------------------------+
|              Explorer DataFrame: [rows: 150, columns: 5]              |
+--------------+-------------+--------------+-------------+-------------+
| sepal_length | sepal_width | petal_length | petal_width |   species   |
|   <float>    |   <float>   |   <float>    |   <float>   |  <string>   |
+==============+=============+==============+=============+=============+
| 5.1          | 3.5         | 1.4          | 0.2         | Iris-setosa |
+--------------+-------------+--------------+-------------+-------------+
| 4.9          | 3.0         | 1.4          | 0.2         | Iris-setosa |
+--------------+-------------+--------------+-------------+-------------+
| 4.7          | 3.2         | 1.3          | 0.2         | Iris-setosa |
+--------------+-------------+--------------+-------------+-------------+
| 4.6          | 3.1         | 1.5          | 0.2         | Iris-setosa |
+--------------+-------------+--------------+-------------+-------------+
| 5.0          | 3.6         | 1.4          | 0.2         | Iris-setosa |
+--------------+-------------+--------------+-------------+-------------+


Added Responsive Design to Website for Smaller Devices

Title
Making the website Responsive for Smaller Devices which is lacking.
Closes: #18

Proposed Changes
Added breakpoint of min-width:300px and added styling that makes the website more responsive.
Added responsiveness in landing page, Home page, survey page, campaign page.

Check List (Check all the applicable boxes)

[x] Enhancement done
[x] My code follows the code style of this project.
Screenshots (if any)

Additional Information

In the small-sized screens, the sidebar should be hidden and added to the hamburger menu icon otherwise it takes too much space and the campaigns looks congested.

Hey, I would like to work on the issue. Can you assign it to me?

@abhijeetnishal  kindly check the conflict and proceed to pull request again

Removed side navbar for smaller devices and making it more visible in smaller devices for better user experience.
Screenshots:

Thank you for your contributions!


Enhancement Sub_tags with no list of tags ...

GEDCOM parser for Python version:
Python version:
Operating System:

Description
Issue sub_records returns all but cannot "follow"
Sub tags requires a list of tags
What I Did
Modified sub_tags to process no tags ...
records = [x for x in record.sub_records if ((x.tag in tags) | (len(tags) == 0))]
Paste the command(s) you ran and the output.
If there was a crash, please include the traceback here.

@ukgenes, new release 0.4.3 (I have just pushed it o PyPI) extends sub_tags() behavior. If you do not pass any tags then it will return all direct sub-tags of a record, expanding pointer records if follow keyword argument is True (default).


New marker line does not show when directly navigating to unread chat in new tab

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

As User A send a message to User B (User B should have no windows to chats open)
As User B navigate directly to the chat with User A in a new tab

Expected Result:
Chat should be marked as read in the LHN ✅
New line indicator should appear over the correct message ❌
Actual Result:
New line indicator is not present at all
Workaround:
Platform:

Web
iOS
Android
Desktop App
Mobile Web

Version Number: 1.2.37-0
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/32969087/206555261-48f215fe-9bd1-49ef-afaa-69f8f27951e2.mp4
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation:
View all open jobs on GitHub

Yeah I can definitely reproduce it and was commenting on this issue to someone in a 1:1. (I know I should have filed an issue). @marcaaron Should this go off to an external contributor?

There's a good chance it's related to the backend and also could possibly be resolved by the Deprecate sequenceNumber project so I am inclined to keep it Internal for now (sorry meant to add that label before)


Command to visualize selected societies on a map

To make it easier to check locations of societies (e.g. to prevent issues like #149) it would be nice to be able to see societies (of a dataset) on a map. This could be implemented by putting together an HTML page - possibly with inlined GeoJSON - displaying a leaflet map, and opening this map in the browser.

Note: This kind of functionality could be reused by pyglottolog, thus it should be implemented in a library, maybe clldutils.

I agree. Given that @Bibiko was trying to make an offline savable map, rather than a leaflet map would it make sense to kill two birds with one stone and generate a png/pdf/svg/whatever?

Yes, possibly. Just came across Kartograph which may fit the bill.

Hm, Kartograph isn't maintained anymore and the former maintainer recommends mapshaper - but mapshaper requires node.js ...
Anyway, if Kartograph works for us, this should be good enough.


[Distributed] Support complex generic distributed actors in thunk gen

Description: Distributed thunks still incorrectly handled more complex generics cases, where the distributed func would use a generic type that had requirements on the enclosing actor type.
This corrects how distributed thunks use generics, i.e. we don't carry generic parameters over at all. A distributed thunk does not have to have the same generic signature as the target; all the types are fully substituted and the only generic parameters we need to carry over are the InvocationDecoder and the actor type.
Risk: Low, affects only more complex distributed actors with generics. The fix is well understood and tested.
Impact: Distributed actor adopters who use generics on the actor type, add requirements on it, and use that generic in a distributed func.
Review by: @xedin @slavapestov
Testing: CI testing, added exact reproducer test for the complex scenarios.
Radar: rdar://115497090
Resolves: the final part of #68517

@swift-ci please test

Thank you for back porting it, we will wait for this merge to test our application with 5.10.

Sadly it seems we're not able to backport this, it had a number of complications that we only resolved recently.
The fix will be landing on main: https://github.com/apple/swift/pull/70842

Alright, Thank you for update @ktoso ! Will pick release of main and try to test it there then.

Thanks, yeap pleas report back.
What actor system are you using btw?

We use our own implemented actor system: https://github.com/ordo-one/package-distributed-system


Fix “case-insensitive import collision”

When building slow_cooker locally (under go1.8, in case it's a recent thing), I get:
can't load package: package github.com/BuoyantIO/slow_cooker: case-insensitive import collision: "github.com/BuoyantIO/slow_cooker/vendor/github.com/codahale/hdrhistogram" and "github.com/buoyantio/slow_cooker/vendor/github.com/codahale/hdrhistogram"

So I updated all the things to use the canonical BuoyantIO/slow_cooker form. 👓

I'm not sure if it's 1.8-specific but it's the first we've seen this bug. Thank you for the patch!

Oliver, I ended up reverting this change because I missed that there was differing internal feedback about how to address this. We'll come up with a plan to fix ASAP.


How to use the kong Prometheus Plugin installed on kong via kubernetes-ingress-controller？

https://github.com/Kong/kong-plugin-prometheus
Don't know how to configure conf of nginx
http://{kong-ingress-controller}:8001/metrics/

How to configure? kong via kubernetes-ingress-controller
server {
server_name kong_prometheus_exporter;
listen <IP_ADDRESS>:9542; # can be any other port as well
location / {
    default_type text/plain;
    content_by_lua_block {
         local prometheus = require "kong.plugins.prometheus.exporter"
         prometheus:collect()
    }
}

location /nginx_status {
    internal;
    access_log off;
    stub_status;
}

}
help me，please！

You only need to scrape the port 9542 of Kong deployment to get Prometheus metrics.
You do not need to change any configuration in the nginx template for this purpose.
Please provide more details on how you are deploying the Kong Ingress Controller if you would like more help from us. Thanks you!

You only need to scrape the port 9542 of Kong deployment to get Prometheus metrics.
You do not need to change any configuration in the nginx template for this purpose.
Please provide more details on how you are deploying the Kong Ingress Controller if you would like more help from us. Thanks you!

I installed kong this way
using YAMLs
kubectl apply -f https://bit.ly/kong-ingress

Then add the Kong Prometheus Plugin
curl http://{kong-ingress-controller-ip}:8001/plugins -d name=prometheus
but，I don't see any metrics of Prometheus
Need I installPrometheus in kubernetes？Or do I need anything else?
I hope you can help me. Thank you, Sir

Need I install prometheus in kubernetes？Or do I need anything else?

Yes, you need to install Prometheus in your Kubernetes cluster if it is not already present.
And then configure Prometheus to collect metrics from Kong.
You can then use Prometheus or Grafana to visualize these metrics.


fix: update readme and requirements with working instructions

@stephanoshadjipetrou anything to add to this change after your work on the fcdo cluster?

@stephanoshadjipetrou anything to add to this change after your work on the fcdo cluster?

Nope, issues that did run through have been solved in the requirements.txt file changes 💯


Move some settings from app.ini to user settings

Feature Description
It would be very nice if some settings could be moved from app.ini to the user settings, mainly appearance/UI things. If the user isn't logged in, the default values could be used or the settings in app.ini can be kept and used then (i.e. user settings overrides the global settings).
The settings I found that could be moved (maybe some of them are not that good to move them, but they are only affecting the UI or things that can be changed by users, but you have to use a workaround):

repository.DEFAULT_BRANCH (https://github.com/go-gitea/gitea/issues/17236)
ui.EXPLORE_PAGING_NUM
ui.ISSUE_PAGING_NUM
ui.MEMBERS_PAGING_NUM
ui.FEED_MAX_COMMIT_NUM
ui.FEED_PAGING_NUM
ui.GRAPH_MAX_COMMIT_NUM
ui.CODE_COMMENT_LINES
ui.MAX_DISPLAY_FILE_SIZE
ui.DEFAULT_SHOW_FULL_NAME
ui.SEARCH_REPO_DESCRIPTION
ui.svg.ENABLE_RENDER
ui.csv.MAX_FILE_SIZE
markdown.ENABLE_HARD_LINE_BREAK_IN_COMMENTS
markdown.ENABLE_HARD_LINE_BREAK_IN_DOCUMENTS
service.ENABLE_USER_HEATMAP
service.AUTO_WATCH_NEW_REPOS
service.AUTO_WATCH_ON_CHANGES
service.explore.DISABLE_USERS_PAGE
api.DEFAULT_PAGING_NUM
time.FORMAT
other.SHOW_FOOTER_BRANDING
other.SHOW_FOOTER_VERSION
other.SHOW_FOOTER_TEMPLATE_LOAD_TIME

This would help to have less settings in app.ini and the possibility for users to change the values if they are not an admin.

I disagree with the ui.*, api.*', other.* and service.AUTO_WATCH* settings.
I think for those it is better to leave them globally, especially the limits, as there is a reason only server admins set them.
Otherwise, anyone could basically crash the server by using an insanely high setting, creating a "small" commit/ PR with a few hundred million changes, and then request this file to be loaded. This would basically allow Gitea to DDOS itself. I don't want that. For the other things mentioned: I think it is only adding unneeded complexity and confusion because I don't see a reason to customize the footer like that per repo.
So, what I have nothing against is repository.DEFAULT_BRANCH, markdown.*, service.ENABLE_USER_HEATMAP and time.FORMAT, and potentially ui.DEFAULT_SHOW_FULL_NAME.

Yes, to prevent such a problem you could set a maximum and it is not possible to change the values so that they are higher that the maximums

I am missing the DEFAULT_SHOW_FULL_NAME (which in GitHub search didn't seem to bring this up) in appearance settings of instances that I don't control.
I view Git forges as a professional context and thus prefer to see the full names when those are set (I thinknthis would also help when viewing an instance from the same sceeen) and there are cases where the username and current name no longer match and can be difficult to update at risk of unforeseen consequences.
For example I have started using my second first name as my calling name while keeping my first first name as an username everywhere, someone may have their surname in username and change it (whether because of marriage or otherwise) and then there is gender transition.

I think the first step is to bring them into system_setting and next step is to bring it to user setting.


Reauthentication needed/failed 2024.8.1

The problem
Since I updated  new integration 2024.8.1 today, I am getting an error: "Action need" -> After this "reautentication" on Website is failing? Pls help
Version of miele integration having the issue?
Mile
Version of Home Assistant Core having the issue?
CORE 2024.8.0 and HAOS 13.0.rc2
Anything in the logs that might be useful for us?
Error Message: "Authentication expired".. -> "HTTP status 401: Retry 2"
After moving to Web-Site: "{"code":404,"message":"HTTP 404 Not Found"}"

Additional information
No response

Same problem/issue
Core 2024.8.0
Operating System 12.4
{"code":404,"message":"HTTP 404 Not Found"}

Same error, after updating to the new version of Miele in Home Assistant 2024.8

same here with
Miele Integration Version 2024.8.1
Core  2024.8.0
Supervisor  2024.08.0
Operating  System 12.4
Frontend  20240806.1
{"code":404,"message":"HTTP 404 Not Found"}

Same problem/issue
Core 2024.8.0
Operating System 12.4
{"code":404,"message":"HTTP 404 Not Found"}

Same issue here. I don't believe it's related to the version.

Seems to be a problem on Miele servers. I've tried to re-register and it fails with "Your registration request has failed. Please try again later".

Going to the endpoint URL manually also yields a 404. I double-checked the Miele developer documentation's swagger, it has not changed.

Miele API service is down. Even their own app doesn't work

That's not correct. I can use the App without issues.

Miele API service is down. Even their own app doesn't work

For me here in Germany the App works

Same problem/issue
Core 2024.8.0

Same problem.  My Miele app is working fine but the integration is asking me to re-authenticate.  Connection was working fine until it went down at 10:42 AM EDT.

Unfortunately same issue here...

I have the same issue on 2024.7.3. Thought I'd add that info since most comments with this issue are on 2024.8.

It looks like the API is back up and running again in Home Assistant 😄

It looks like the API is back up and running again in Home Assistant 😄

Yes. Works again.

@holger-tangermann: Thanks. API is back and Integration is working again

Yep, works again


refactor: move mathjax context to page level - LESQ-400

Description

Moves mathjax provider to lesson level
Mathjax should still render quizes
No errors in console

Issue(s)
Fixes #
How to test

Go to https://deploy-preview-2020--oak-web-application.netlify.thenational.academy/teachers/programmes/maths-secondary-ks4-higher/units/surds/lessons/simplifying-surds#starter-quiz
Quizzes still show mathjax

Screenshots
How it used to look (delete if n/a):
{screenshots}
How it should now look:
{screenshots}
Checklist

[ ] Added or updated tests where appropriate
[ ] Manually tested across browsers / devices
[ ] Considered impact on accessibility
[ ] Design sign-off
[ ] Approved by product owner
[ ] Does this PR update a package with a breaking change

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


python311Packages.androidtv: 0.0.72 -> 0.0.73

Diff: https://github.com/JeffLIrion/python-androidtv/compare/v0.0.72...v0.0.73
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

5 packages built:

home-assistant-component-tests.androidtv
python310Packages.androidtv
python310Packages.androidtv.dist
python311Packages.androidtv
python311Packages.androidtv.dist


Show actual thread id in windows logs

No, sorry, we can't do that, because then the API would be inconsistent as to what a gpr_thd_id represents and how it can be manipulated.

I see. I will try to come up with something less intrusive. Btw, reporting the thread id what is basically a pointer doesn't really make much sense in logs. At least on windows, seeing the actual thread ids is pretty useful for debugging.

Well, when looking at logs, you can follow thread jumps at least. Personally I usually debug at looking "what has the same thread id number".
Also note that if you're actively in a debugger, you can do a watch that'll resolve our threadid into the real one, by going into the structure and plucking it out.

You can't though.  We only capture a pointer for threads created by GPR.
Actually in preference of using the windows id for gpr_thd_id and having a
lookup table for gpr_thd_join.
On Sun, Jul 12, 2015, 9:04 AM Nicolas Noble<EMAIL_ADDRESS>wrote:

Well, when looking at logs, you can follow thread jumps at least.
Personally I usually debug at looking "what has the same thread id number".
Also note that if you're actively in a debugger, you can do a watch
that'll resolve our threadid into the real one, by going into the structure
and plucking it out.
—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/2401#issuecomment-120734085.

Right, that wouldn't work in the case a system thread tries to do gpr_log. It'll display 0 instead.


Some problems with the new ESLint code actions functionality

Just wanted to start off by saying thanks for implementing this, we're a step closer to feature parity with CoC!
I tried it out and found several problems:

Boolean parameter seems to be required here in the latest neovim:
https://github.com/jose-elias-alvarez/nvim-lsp-ts-utils/blob/ef83962fe4f462753dede81f7505a6f9449cd512/lua/nvim-lsp-ts-utils/code-action-handler.lua#L183
Same here for the third parameter, I simply added function() end:
https://github.com/jose-elias-alvarez/nvim-lsp-ts-utils/blob/ef83962fe4f462753dede81f7505a6f9449cd512/lua/nvim-lsp-ts-utils/code-action-handler.lua#L187-L190
After that lua vim.lsp.buf.code_action() successfully returns actions 🎉  - but Telescope's lsp_code_actions does not.

Thank you for looking into it! I've gone ahead and merged the changes. I wasn't having any issues with my Neovim version, but I don't update as often as I should. I also fixed a utility function that was failing to report potential errors with ESLint output, and I want to learn more about libuv error handling in general to catch issues like this earlier.
Re: Telescope: the issue is that the plugin bypasses the defined code handler and fetches code actions directly from the language server, so it's not possible to inject the ESLint code actions in the same way. I'll open up another issue, since it would be a nice feature to have.


Contextive reports warning in IntelliJ 'cannot load definitions file' when opening a project without a definitions file

Describe the bug
Contextive warning popup
Expected behavior
No error when opening a project without a definitions file.
Additional context
In VsCode this is avoided because the extension is only activated on the presence of the definitions file.  With IntelliJ, the plugin is activated all the time, but still expects the definitions file to exist.
Options to resolve:

Don't activate extension unless project folder contains a definitions file (perhaps hooking into ProjectActivity, or check for definitions file present in fileOpened)
Don't flag warning when definitions file not found

:tada: This issue has been resolved in version 1.11.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Adding indication of HR

Adding visual indication of heart rate

I could be wrong, but does this not permanently turn the heart rate monitor on whenever showing the watch (even if the display is off?).
While fun, this would kill your battery in no time - so do you think it should be some kind of setting, or only on when the display is on?

Good feedback, I missed that I had to manage this as well. So I will close this pull request and do a new one when I have fixed this issue


MGDCTRS-963: chore: Truncate the very long failure reason

screenshot

It seems like when we have this long error string it'd be great for the user when they spot this error in the info drawer and click on the "view more" link we could take the user to the overview page where the full text could be displayed.

yes, this could be one way to handle it. May I can add this topic to our next UX call.


Rule rich measure

Codecov Report

Merging #2342 (dbb27d3) into master (14d47c9) will decrease coverage by 3.05%.
The diff coverage is 97.05%.

@@            Coverage Diff             @@
##           master    #2342      +/-   ##
==========================================
- Coverage   98.88%   95.83%   -3.06%
==========================================
  Files          73       73
  Lines        7629     7703      +74
==========================================
- Hits         7544     7382     -162
- Misses         85      321     +236

Flag
Coverage Δ

unittests
95.83% <97.05%> (-3.06%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

rich/_export_format.py
100.00% <ø> (ø)

rich/console.py
96.69% <96.03%> (-2.10%)
:arrow_down:

rich/cells.py
100.00% <100.00%> (ø)

rich/rule.py
100.00% <100.00%> (ø)

rich/syntax.py
99.30% <100.00%> (+0.02%)
:arrow_up:

rich/terminal_theme.py
100.00% <100.00%> (ø)

rich/_windows_renderer.py
0.00% <0.00%> (-100.00%)
:arrow_down:

rich/_win32_console.py
3.19% <0.00%> (-88.30%)
:arrow_down:

rich/live.py
97.90% <0.00%> (-2.10%)
:arrow_down:

... and 10 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 aa7926c...dbb27d3. Read the comment docs.

@gimbo This branches off of and fixes the hang in the test in your PR at #2292. I wasn't able to merge it into your PR though for some reason.


Merge 'live' to 'master'

Docs Build status updates of commit b4a451b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sysinternals/downloads/bginfo.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit b8a2d0c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sysinternals/downloads/bginfo.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Can we port it for Blazor?

Can we port port this system for both Blazor Server and Blazor WASM?

Yes, but at the moment, I don't have much effort to port :)
PRs are welcomed

I can work on this, but I suggest to move this into small manageable PRs

I want to work on this

Let us arrange things and see how can migrate this without breaking things
More ever we need to lIst what the changes we want to made to make this work as expected

@hishamco Can you mention what you are up to till now and please share your action plan.

@rafsanulhasan I was thinking about this yesterday, can we chat on glitter to make the conversation interactive

Sure,  give me your preferable time

Just ping me when you are there


Language Server Protocol

Wonder if IDEA supports LSP or we can have some reuse of the plugin so parts of it can be used in Eclipse / Eclipse Che or other editors which can support LSP as well.
There are surely parts of this plugin that touches the camel catalog and checks the endpoint uri etc, that can be made reusable without relying on IDEA APIs.

See more details at
https://github.com/Microsoft/language-server-protocol/wiki/Protocol-Implementations

There is some work about this at
https://github.com/lhein/camel-language-server

The eclipse users and web editors are asking about LSP so it may be worthwhile to make this plugin code reusable outside IDEA, eg the logic that does the auto completion and list which options you can choose etc.

We are getting closer to having a mutual interest of have some shared code for IDEA and Eclipse in this git organization so Camel tooling on both editors can be awesome. With LSP then Eclipse can do the code assistance we are doing already in IDEA. And eventually if LSP becomes included OOTB in IDEA we can have more shared code.
But at first we can potentially have a git organization that can include both and have repos for

common
idea
eclipse

It would take time to find the common code and have that refactored out to an individual common component. So for starters this may be

camel-idea-plugin
camel-tooling-lsp

And then over time we have some common code in a common/core tooling module

camel-idea-plugin
camel-tooling-lsp
camel-tooling-core

Claus, the idea of LSP is to separate out the logic for code completion, hovers, documentation etc into a shared server "application". Whatever clients you then use you can (if this client supports LSP) have a client plugin which talks with the LSP server and provides all the functionality the server has to offer.
So from a logical point of view we should split the repositories in "server" and "clients". As a first goal it would definitely make sense to extract common / shared code into a common repo with the goal to make it easier later on to merge that code into the LSP server or to provide a library which then is used by the LSP server.
For the client side we already prepared basic clients for Visual Studio Code, Eclipse and Eclipse Che (see https://github.com/lhein/camel-language-server/tree/master/clients) The LSP server we currently have is limited to XML DSL but it would be really awesome to make it work for Java at least too.

Created a ticket about organization renaming #408

the Camel LSP has been moved under the same organization: https://github.com/camel-tooling/camel-language-server

IDEA dont support LSP so lets close this for now

IDEA dont support LSP so lets close this for now

there is a community extension for that https://github.com/gtache/intellij-lsp
But current Camel IntelliJ plugin is benefiting from the IntelliJ API to provide different features. As long as there are people to maintain it, no real advantage to use Camel LSP.

People maintaining the plugin for now is very limited and spontaneously, so I will have no objections against using the Camel LSP instead, if that give us an advantage to share features across platforms and more ppl to help maintaining the plugin.
I don't have any knowledge regarding LSP, so a few questions / concerns, do we have the same feature set available in the LSP as we have in the Intellij API?
It seems to me the Intellij LSP plug-in is more and less maintained by one person, this is pretty much the same for the Camel Intellij plugin at the moment.
If we switch to LSP this will mean we also need to help maintaining the Intellij LSP project, and the few ppl maintaining the Camel Intellij plugin today, I'm not sure it will be an advantage for us.

do we have the same feature set available in the LSP as we have in the Intellij API?

no. LSP is a providing a subset of IntelliJ API.
The main differences currently between Camel LSP and Camel IntelliJ I'm aware of are:

completion in IntelliJ for components is based on available dependencies in pom.xml (which means needs to add depepencies first in pom.xml) although with LSP we are providing all components from the catalog
Camel IntelliJ has (which Camel LSP doesn't have):

Code completion for Camel property placeholders https://github.com/camel-tooling/camel-language-server/issues/29
external link to Camel component documentation opening in web browser
Supports 3rd party Camel components https://github.com/camel-tooling/camel-language-server/issues/45
Camel icon in gutter (not part of LSP)
Attempts to use same version as camel-core dependency from the loaded project https://github.com/camel-tooling/camel-language-server/issues/38
Supports loading camel-catalog from third party Maven repositories define in the project Maven pom.xml file

Camel LSP has (which Camel IntelliJ doesn't have):

Support for Camel-K Groovy (and soon Kotlin and JS) files
Support for Camel Kafka Connect properties file
Reused code in Eclipse Desktop, VS Code, Eclipse Che and Atom. It is reusable by configuration in IntelliJ and Sublime (and in theory in Emacs and vim and some others editors)
outline
Auto-completion for referenced IDs of direct, direct VM, VM and SEDA components (XML DSL only) (i thought IntelliJ has it but cannot find it in doc today)
Specific documentation on hover on attributes (not the whole doc of the component)

In a general way, developing for a specific IDE is more powerful than using LSP when looking at this IDE only. The IDE apis are providing a lot of good tools. For LSP, it would mean being able to reuse other LSP. It is currently quite complicated, even if not impossible. For instance, SpringBoot is providing a LSP reusing XML LSP and Java LSP.

It seems to me the Intellij LSP plug-in is more and less maintained by one person, this is pretty much the same for the Camel Intellij plugin at the moment.
If we switch to LSP this will mean we also need to help maintaining the Intellij LSP project, and the few ppl maintaining the Camel Intellij plugin today, I'm not sure it will be an advantage for us.

good point, IntelliJ has a small contributor community compared to most of the other IDEs and seems Jetbrains doesn't want to embrace the LSP themselves (I think they see it as endangering their business model but this is my personal point of view :-)).
For IntelliJ LSP, we can expect more chance to have help from community than for only Camel IntelliJ but it stays a bet.


Improve ConcatVCF efficiency

About 30% of variant calling is spent in ConcatVCF, which uses Picard’s SortVcf at the moment. However, the individual files are already sorted, so we could just concatenate them in the correct order.

The awk part of ConcatVCF takes 56 minutes on a GRCh38 test dataset. Total time is 3h 48min with the improvement in PR #304.

#304 resolved


Feature: App should drop services from its discovery cache after a period of time

overview
As a user that used to connect to a robot that I don't have anymore, I would like it to stop showing up in my app's robot list as "unable to find"
The app should clean services out of its discovery cache automatically after their last seen date becomes too old
acceptance criteria

[ ] If a robot doesn't advertise, respond on /health, nor respond on /server/update/health for 60 days, the app should remove it from its discovery.json cache

implementation notes
60 days subject to approval by UX / product / support
┆Issue is synchronized with this Wrike Task by Unito

App will automatically clear out stale IP addresses for a given robot, which should resolve much of the problems this ticket was written to address. Given the large UX implications of this ticket, going to close it out in favor of a more considered approach when we actually decide to tackle discrete removal of robots from the list


Running in vscode

Hi!
Trying to run this in vscode using https://marketplace.visualstudio.com/items?itemName=AlecGhost.tree-sitter-vscode
How to compile wasm/scm files?
    {
        "lang": "asm",
        "parser": "/path/to/your/tree-sitter-xyz.wasm",
        "highlights": "/path/to/your/highlights.scm",
        "injections": "/path/to/your/injections.scm"
    }
]

Sorry for taking so long to answer. Added basic highlights.scm file in there. Added wasm and highlights.scm file now. They are very minium right now but something.

Added lots of features and new highlights and new wasm.


Pthread error with CPP Example 06

Example 6 fails to build.
Error: /usr/bin/ld: CMakeFiles/main.dir/main.cpp.o: undefined reference to symbol 'pthread_create@@GLIBC_2.2.5'
/usr/bin/ld: /lib/x86_64-linux-gnu/libpthread.so.0: error adding symbols: DSO missing from command line
collect2: error: ld returned 1 exit status
The following line should be added to the CMakeLists file
SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -pthread")

See https://github.com/cubert-hyperspectral/cuvis.cpp/pull/4


After latest u

Aknowledgements

[X] I have checked that there's no other issue describing the same or
similar problem that I currently have, regardless if it has been
closed or open.

[X] I can confirm that this is not an issue with the Discord website,
but it is a problem specific to the WebCord itself.

[ ] I have tried running the build from the master branch and it does
not have any fixes implemented according to my issue.

[ ] My issue describes one of the unstable and/or not fully implemented
features.

[ ] I have found a workaround to mitigate or temporarily fix this issue
(please write it in Additional context section).

Operating System / Platform
🐧 Linux
Operating system architecture
x64 (64-bit Intel/AMD)
Electron version
v18.2.1
Application version
3.1.4
Bug description
After upgrading to latest version, webcord no longer remembers my login and settings. The process also hangs after I exit from the applet.
Additional context
I am using the AUR package for webcord.

After restarting my desktop, it seems to work fine again. Don't know what caused it but it works now.


Feature or documentation How to migrate from older mlia

It would be really helpful to get a migration hint or tool from the older versions.

Thanks @m67hoff ! In theory, it should really just be a renaming of the various package names and binaries, but I agree we should at least put a little section in the doc explaining that. thx.

Thanks @m67hoff ! In theory, it should really just be a renaming of the various package names and binaries, but I agree we should at least put a little section in the doc explaining that. thx.

Michael, do you mean migration from tool aspera or from mlia?
Notes:
ascli detects when it is first executed and migrates configuration from mlia automatically.
ascli can export its configuration to aspera, but not yet the way around: it can be added.

yes - from mlia to ascli.  ( I have lots of access credentials only in config.yaml  )

rom mlia to ascli. ( I have lots of access credentials only in config.yaml

@m67hoff, it appears what you are asking for (mlia -> ascli) is already in. Let us know if this addresses your concern (or close the issue) or if there is more to be done. thx!

code is here:
https://github.com/IBM/aspera-cli/blob/develop/lib/aspera/cli/plugins/config.rb#L279


Dead link in docs

Describe the bug
From the main docs page, if you click "Tutorials" under quickstarts for first time users it leads to the page tutorials/steps.md which gives a 404 error
To Reproduce
Steps to reproduce the behavior:

Go to https://deltares.github.io/HYDROLIB-core/0.3.0/
Click on "Tutorials"
Leads to page https://deltares.github.io/HYDROLIB-core/0.3.0/tutorials/steps.md which gives 404 file not found error

steps.md does not exist in the tutorials folder anymore (think it existed in 0.2.0). Maybe this should be changed to tutorials.md?

Thanks Lisa, we discovered this last week already in the sources and fixed it there. Only the 0.3.0 docs were not regenerated.
For now you can use https://deltares.github.io/HYDROLIB-core/develop/
and in the upcoming 0.3.1 this will be correct again.


Bar Color Glitch

One on the recent patches in between 7.0 and Legion has made all of the bar colors turn green. This includes secondary resource bars as well as cast bars. I've tried reinstalling and messing around with the config, but nothing has worked. Are other people having this problem?
Let me know if you need more info.

Hey, I don't have this issue. Are you using a legion compatible version of oUF?

I ended up deleting my cache and WTF folders. That fixed the problem. Sorry!


I encount build setting not found error when I tried to connect branch at Amplify Console.

About bug
I have two branches, develop and feature/#6_prepare_graphql_from_vue.
I could connect and deploy 'develop' branch, but, I coudn`t connect 'feature~' branch.
Amplify Console Images
This is a image when connecting and deploying to 'develop'branch'.

This is a image when trying to connect 'feature~' branch.

I think that these error is caused by branch name(character '#').
Would you please research it ?
** Environment **
Amplify CLI    =>    1.7.0
Vue    =>    3.8.2

Hey @yukitaka13-1110, sorry for the late reply. We've added this as bug and will work on a fix. In the meantime, you can workaround this limitation by removing the # character in your branch.

Thank you for quick response !
As I expected, a character  '#' was the cause of the bug.
Thank you for verifying.


First track loads slow, second track never gets loaded

Hi,
I have two problems (maybe they have something to do with each other). I am working on an iPhone app and using the latest code (master branch). I'm developing on device (the simulator crashes on libspotify for some reason) with iOS4.2.1 and iOS5 (latest).
First of all, the first track loads really  slow. The whole UI hangs and is unresponsive, but after 5 to 10 seconds the track is played. I have seen some issues here on Github that look similar, but i have no clue why this is happening.
The other problem occurs when I want to play another track. The app gets in a loop and the track is never loaded. I can continue playing the first song, but the second song is never plays (rarely it does play).
This is the play code (most of it is copy-pasted from your examples):
- (void)playTrack
{
	// make sure wo don't start multiple requests
	[NSObject cancelPreviousPerformRequestsWithTarget:self selector:@selector(playTrack) object:nil];

	NSURL *trackURL = self.currentSpotifyItem.spotifyURL;

	// play spotify track
    if (trackURL)
	{
		SPTrack *track = [[SPSession sharedSession] trackForURL:trackURL];

		if (track != nil)
		{
			if (!track.isLoaded)
			{
				// Since we're trying to play a brand new track that may not be loaded,
				// we may have to wait for a moment before playing. Tracks that are present
				// in the user's "library" (playlists, starred, inbox, etc) are automatically loaded
				// on login. All this happens on an internal thread, so we'll just try again in a moment.
				[self performSelector:@selector(playTrack) withObject:nil afterDelay:0.1];
				return;
			}

			NSError *error = nil;

			if (![self.playbackManager playTrack:track error:&error])
			{
				// some error occured
			}

			// track is playing
			return;
		}
	}
}

If another track is requested by the user I perform the following lines of code as well:
if ([self.playbackManager isPlaying])
{
[[SPSession sharedSession] unloadPlayback]; // tried with and without
[self.playbackManager setIsPlaying:NO];
}

It seems like I have to stop the current track somehow first, or set the session, but I have no idea how.
I have no idea where to look further. Is this a common problem?

Just to clarify my second problem:
If I'm loading the second track, the isLoaded boolean never becomes true, so the performSelector is called again and I get stuck in an infinite loop.

Hey,
Do the sample projects have the same issues when run on the device?

"Guess the intro" loads another song, but only runs properly on iPad and i don't have one at the moment. I'll try it later when i have one again. Or is there another sample project i can try that skips to another song?


[core] Health Endpoint

Health Endpoint?

yeah - was thinking it would be great to have a way of pinging the spree API to ensure it's working.  Mainly as an "getting started" thing for people.  That said, it's probably overkill.  The spree.index page has a ton of getting started info, so I think I'll close this for now


Collection Page Content

Stuff like "What is a banner and why/when to use it?" would be the topics.

Hey @markmead can you please elaborate the issue as I can look into it.

What more information do you need? @ajaydahiya7


Insert in dbcontext always uses default value for int and bit data types

If the SQL table contains a default value for and int (or a bit - I tried both, maybe even for all data types), the call to SaveChanges() defaults the value, even it is supplied.
Using the following nuget dependencies:

Microsoft.EntityFrameworkCore.SqlServer.Design (1.1.2)
Microsoft.EntityFrameworkCore (1.1.2)
Microsoft.EntityFrameworkCore.Tools (1.1.2)

Steps to reproduce
Create the database (using VS2017 built-in database)
CREATE TABLE [dbo].[AotPackage]
(
	[Id] INT IDENTITY NOT NULL PRIMARY KEY,
	Name nvarchar(100),
        [CodeUpgrade] INT NOT NULL DEFAULT 1
);
CREATE TABLE [dbo].[AotModel]
(
	[Id] INT IDENTITY NOT NULL PRIMARY KEY,
	Name nvarchar(100) NOT NULL,
	PackageId int REFERENCES AotPackage(Id) NOT NULL
);

Publish connect string:
Data Source=(localdb)\MSSQLLocalDB;Integrated Security=True;Persist Security Info=False;Pooling=False;MultipleActiveResultSets=False;Connect Timeout=60;Encrypt=False;TrustServerCertificate=True

reverse engineer the database
Scaffold-DbContext "Server=(localdb)\mssqllocaldb;Database=ReproDb;Trusted_Connection=True;" Microsoft.EntityFrameworkCore.SqlServer -OutputDir Models -Force

reverse engineer the database
var context = new ReproDbContext();
AotPackage p = new AotPackage()
            {
                Name = "test",
                CodeUpgrade = 0, // << this one will be defaulted to 1
                AotModel = new AotModel[] {
                    new AotModel()
                    {
                        Name = "test"
                    }
                }
            };
context.AotPackage.Add(p);
context.SaveChanges();

note: this is a partial code snippet - I guess it's enough to repro.
Further technical details
EF Core version: 1.1.2
Database Provider: Microsoft.EntityFrameworkCore.SqlServer
Operating system: Win 10 (Creator update)
IDE: Visual Studio 2017

Duplicate of #7089

Hi @ajcvickers
I read about the duplicate issue #7089 and the related ones.
I can see and understand the issue about 0 (which is the CLR default value) being replaced by the SQL default value.
Is there really no other option (e.g. replacing the int with Integer) to resolve the IMHO really unexpected behavior? If not, are there still plans to generate warnings? I did not find any open issues related to that.
Cheers.

@ibruynin We discussed warnings and decided to only warn for bools--see #7163. The main problem here is that any behavior is unexpected depending on where you approach the issue from. The discussions here and over the years have shown that:

Some people expect the store default to be used always. They are surprised that when a property has a value, then the store default is not used.
Some people expect the store default never to be used. They are surprised when a store default is used when they have not specifically requested it.

In general, the most useful behavior is to allow the store default to be used only when a specific value has not been set. But when working POCO objects there is no obvious way to do that. I haven't seen anything that we think is a better option than what we have.


Android fullscreen fix for v1 branch

will take a look at it soon
thanks

@davidohayon669 You could check this? It is necessary to fix that.
Cheers.

@lucianomlima I took a look at this issue and I'm not positive you solved it correctly.
A few things:

Back button action (At least with React-Native as far as I know, I have little experience with native Android) will close the app unless any other actions (mainly routing actions) were registered to it with an event lister (With ReactNative.BackAndroid). On the example app, hitting back from a fullscreen will close the app. On the app I work on, hitting back will perform the registered navigation action (which in my case is a 'pop' of the current scene) and the YouTube player will shut down because its unmounted.
When I disable the default back action in the example app, by adding BackAndroid.addEventListener('hardwareBackPress', () => true);, nothing will happen when hitting back.

Are you sure your use case only closes the fullscreen mode or is it also performing a navigation event?
As I understand, to have the back button only exit the fullscreen mode, onBackPressed should be overridden on YouTubeView.
I will further take a look at it when I improve my app but I can't merge this request right now as it only solve part of the problem and leaves the Back button issue still buggy

Thanks @davidohayon669.
In my tests, I was able to identify the following behaviors:
I open my app, navigate to a videos list (thumbnails), tap a video, open the player in fullscreen.

If I rotate the cell phone to landscape and then return to portrait, and my device have automatic rotation enabled, the orientation returns to portrait.

If the device has automatic rotation turned off, the application remains in landscape.

If the application is in fixed portrait orientation in AndroidManifest.xml, the application remains in the landscape.

If instead of rotating the device, I press the device's back button, it exits the fullscreen but keeps the orientation locked in the landscape, regardless of the application orientation configuration and the automatic rotation of the device.

With this, I has concluded that the problem was not the orientation because in case one, without pressing the back button, the YouTubeView was unmounted and the automatic rotation worked correctly.
I confess I did not try to exit the fullscreen with an override of the onBackPressed method, but I try this and I will comment later.
I did not quite understand the case of the default back action disabled. What would be the behavior you expected?

I'm afraid that what you interpret as an "exit fullscreen" action triggered by the back button is a side effect of an unrelated action that is registered with the back button, probably one that destroys the view where the player is mounted so it destroys it as well.
The android YouTube API doesn't mention anything about a default back button action, It only says that any exiting of a fullscreen mode will return the orientation back to the intended state (as happens after hitting the fullscreen icon while on fullscreen)
I would try to implement something like
@Override public void onBackPressed() {     if (mYoutubeController.isPlayerFullscreen()) {         mYoutubeController.setFullscreen(false);     } else {         super.onBackPressed();     } }
in YouTubeView.java
But for this we also need to implement a YouTubePlayer.OnFullscreenListener on the player so we can update the controller with the fullscreen state
tl;dr
The back button doesn't naturally exits fullscreen. It does what it is registered to do at the same moment and the exiting of the player happens as a result of that


fix: add fallback to record items

Problem
items can be undefined
Solution
add fallback to empty array

[x] Unit tests added/updated
[ ] E2E tests added/updated
[ ] N/A - (provide a reason)
[ ] deferred - (provide GitHub issue for tracking)

Housekeeping

[x] No non-essential console logs
[ ] All new files contain license notice

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report

Merging #1060 (ae8c591) into main (5b553e9) will increase coverage by 0.00%.
The diff coverage is 100.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

@@           Coverage Diff           @@
##             main    #1060   +/-   ##
=======================================
  Coverage   93.86%   93.86%
=======================================
  Files         124      124
  Lines        5819     5821    +2
  Branches     1764     1764
=======================================
+ Hits         5462     5464    +2
  Misses        339      339
  Partials       18       18

Files Changed
Coverage Δ

...act/lib/forms/form-renderer-helper/relationship.ts
92.93% <100.00%> (+0.07%)
:arrow_up:

Continue to review full report in Codecov by Sentry.

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


fixed reuire error

for this issue const ImageminPlugin = require('imagemin-webpack-plugin').default

Thanks for bringing this to my attention.
I've changed the documentation to match what you need to do to get it working in an ES5 environment.
But i think i'm going to keep the current method of exporting (ES2015 modules export).


Add support for multiple Entity Managers and connections

Stated in this issue we need to be able to setup multiple Entity Manager names to flush

https://github.com/SimpleBus/DoctrineORMBridge/issues/10

References

https://github.com/SimpleBus/SymfonyBridge/blob/master/src/DependencyInjection/DoctrineOrmBridgeConfiguration.php
https://github.com/SimpleBus/SymfonyBridge/blob/master/src/Resources/config/doctrine_orm_bridge.yml#L2-L7

So this would mean that all entity manager configured to be flushed by the bridge will be flushed all at once ?


allow setError to take in Boolean values

The note at the end of [this section] (https://github.com/meteor-useraccounts/core/blob/master/Guide.md#custom-validation) in the guide indicates that the state can be a true/false value (the example code above the note passes in a true value to setError). However, if you pass a true or false value to setError it throws an error. Adjusted to allow boolean values.

makes sense!
tnx


Add documentation

There is currently a very basic documentation with a presentation and the installation. Also a Core references has been started but far from complete.
At least an overview on Lotus mechanics, especially the language/translation is required.

Done within version 0.5.0


ng init creates app file prefix with 'app' everytime

angular-cli: 1.0.0-beta.6
node: 6.2.1
os: darwin x64
Whenever you run 'ng init' the cli seems to create files prefix with name 'app' ., for example..
app.component.ts etc., But I had created this application using 'ng create' so it took my project name and created files with prefix of 'myapp-component.ts',
So I expect these files should not created as new every time I upgrade cli.
In other words it should follow the same naming pattern to override.

Closing this as obsolete.


Use ::Settings instead of deprecated VMDB.Config.new in AplicationController

Removed deprecated calls to VMDB::Config.new in ApplicationController
@miq-boat add-label core
\cc @Fryguy

Very happy to see us going towards Settings

Euwe Backport details:
$ git log
commit 19238e5ad6aace41c54d5e954c9785121dc912cc
Author: Jason Frey<EMAIL_ADDRESS>Date:   Tue Oct 11 17:17:56 2016 -0400

    Merge pull request #11840 from yrudman/use-new-settings-in-application-controller

    Use ::Settings instead of deprecated VMDB.Config.new in AplicationController
    (cherry picked from commit ba991ae66ad6056cba20dd8620e9cdc16948d458)


Enable a time selection method idependent of iloc/loc, called sel

Following the .sel method on xarray dataarray, we should enable a method allowing to select a specific point or slice. Example usage from xarray here: https://docs.xarray.dev/en/stable/user-guide/time-series.html#datetime-indexing

The .sel method should allow users to select a portion of the timeseries based on 1. value or time  and 2. an argument, which can be a string, datetime (if time), float, list or a slice and set with an expression.
Let's create a Series such as:
import numpy as np
import pyleoclim as pyleo

freqs=[1/20,1/80]
time=np.arange(2001)
signals=[]
for freq in freqs:
    signals.append(np.cos(2*np.pi*freq*time))
signal=sum(signals)

ts = pyleo.Series(time=time, value=signal)

Expected behavior from the following commands:

ts1=ts.sel(value>1): returns a new timeseries object where all the values are greater than 1, with their corresponding time points. All operators should be allowed (<,>,=,>=,<=).

ts1=ts.sel(value=1, method = 'nearest', tolerance = 0.2): returns a new timeseries object where all the values are equal to 1, with their corresponding time points. In this particular example, some values should be equal to 1 but we can expect this behavior from real time series. Therefore, we need to build a tolerance, which is represented by the parameter method with an associated tolerance value. Method should allow for the following values None, means exact match only, and nearest (find the nearest values within the tolerance, which is the maximum distance between original and new labels for inexact matches). Default should be None.

ts1=ts.sel(value=[1, -1], method = 'nearest', tolerance = 0.2): returns a new timeseries object where all the values are equal to 1 or -1, with their corresponding time points. method and tolerance as previously defined.

ts1=ts.sel(value=slice(-1,1), method = 'nearest', tolerance = 0.2): returns a new timeseries object where all the values are between -1 and 1, with their corresponding time points. method and tolerance as previously defined.  The concept of a slice would most likely have to be defined in the code base. Perhaps as an object?

Now let's talk about time:

ts1=ts.sel(time>1000): returns a new timeseries object where all the time values are greater than 1000 with their corresponding time points. The search criteria could be a float (1000) or a datetime object (1995-12-31 10:17:25) or a string ("1995-12-31")

Following bullet 3. and 4., should be available for = and slice, the later being almost equivalent to the current ts.slice() which only takes floats as arguments.

Thanks for the extra details. I'm to need a few more I'm afraid
First, ts1=ts.sel(time>1000) isn't valid Python syntax - how about ts.sel(time=slice(1000, None))?
Second, in what unit should the units be interpreted? How about

if it's float, then in the same time unit of ts. For example, if the time unit of ts is 'years BP', then 1000 means 1000 years BP
if it's datetime, or a string, then interpret as the Gregorian Calendar. So ts.sel(time=slice('1000-01-01', None)) means "all points where the datetime index is greater than the year 1000-01-01. So, this is one is independent of ts's time unit

The concept of a slice would most likely have to be defined in the code base. Perhaps as an object?

slice is already a Python built-in, we can just use that

Also, how should tolerance be interpreted if you pass a datetime to time?

The first commit answers the first questions, and agreed and merged.
Regarding the tolerance, maybe we should interpret is as a % for datetime? Or it should be given in datetime dt, which makes more sense.

Addressed ( in part ) by https://github.com/LinkedEarth/Pyleoclim_util/pull/339


botreq-status - Section links

When viewing old version of BOTREQ page, if I press on some section from bot generated table, I am forwarded to current BOTREQ version. Probably would be nice to include some logic here:

if I'm on BOTREQ page (no matter what version), then use relative link ([[#foo]])
if I'm on some other page, then use full link ([[WP:BOTREQ#foo]]).

Again, as with issue #7, I don't mind if this is closed as 'won't fix/not a bug'.

This problem can't be solved on my end. The thing is, the table is transcluded from a page in APersonBot's userspace (specifically, User:APersonBot/BOTREQ status), so even very old versions still show the very latest version of the template. I don't think it's possible to fix this.


Pin click typer

click 8.1.0 is incompatible with typer. While there's an open PR to fix it in typer, we don't know when the fix will be released. So, just fix it by pinning known-compatible versions, including the transitive dependency we didn't explicitly list before.

https://github.com/tiangolo/typer/pull/375

A release will be needed after this change. Hopefully we can do it with credentials stored in this repo

Hello! I just released Typer 0.4.1, you can now upgrade the version and possibly unpin Click. :rocket: :nerd_face:

Hello! I just released Typer 0.4.1, you can now upgrade the version and possibly unpin Click. rocket nerd_face

Thanks for the quick fix!


Update sql-server-connector-maintenance-troubleshooting.md

Update to doc from customer feedback for case<PHONE_NUMBER>001033.

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

@Rupp29 - Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
Note: before this PR is merged, the new link needs to be updated to point to the live article rather than the article in main.
#label:"aq-pr-triaged"
#assign:@MicrosoftDocs/public-repo-pr-review-team

The following users don't have valid GitHub IDs, or are not collaborators on this repo: microsoftdocs/public-repo-pr-review-team

The proposed change looks good, but I can't update the page to the live URL

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

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

@ShannonLeavitt : The style and content looks good to me. If you can update the URL to the live URL. I'm not able to update it myself.


Revert "Update to latest Jackson patch version to get fixes"

Reverts stargate/data-api#1793

Force merging (ironically?) to get approval for the original pr. :)


Updated UI for landing page

Describe the Issue
On main, I can see there have been updates to better show the progression for the core curriculum. And I think it looks like nice.

But when it comes to the other courses, like the C# courses and the interview prep section, I feel like it would be better to remove the circles. At first I thought I was supposed to click on these circles because they looked like buttons to me.

Affected Page
http://localhost:8000/
Steps to Reproduce
These changes are only available on the localhost. So you will need to run it locally to see what I am referring to.

Go to http://localhost:8000/
scroll down to the extra courses outside of the core curriculum and see what I am referring to

Expected behavior
For courses, like odin project, interview prep, C#, etc, I don't think these circles need to be here

It would be better to leave it to the original like this

As for the english curriculum, if new courses will be added there then maybe it works to have progression like is shown for the core curriculum.
Screenshots
No response
System

Device: [e.g. iPhone 6, Laptop]
OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04]
Browser: [e.g. Chrome, Safari]
Version: [e.g. 22]

Additional context
No response

This seems to be related with #54656

I would like to give this a shot.

A couple things to note here...
The circles have four states. Empty, all challenges completed (filled-in), certification earned (ribbon added), both (filled-in and certification earned). See some images here.
I agree that they look a little goofy beyond the core curriculum, but we kept them because the buttons become full width if we remove them - and that looks a little goofy too. I think it would look good enough, but the C# (and soon English), have certifications to claim, as well as some of the legacy. So it's nice to show the circles or something on those so people can see that they earned the cert - as well as have something to motivate them.
I definitely think there's room for improvement here. I'm not sure what the solution is though. I would probably be fine removing all the circles that aren't the core curriculum if we want - but maybe we could play around with a few other designs. Maybe make all the circles gray or something, so they don't look clickable? Add an icon in the circles without a number?

Hi @deeseeker !
This issue has not been opened up for contribution.
Issues marked with help wanted or first timers only are available for contribution.
You can read about the contributing process here

@moT01

The circles have four states. Empty, all challenges completed (filled-in), certification earned (ribbon added), both (filled-in and certification earned)

Ok cool. Thanks for clarifying that.
Looking at the image I like the final result there.

why can't the odin project-coding interview prep -so on all have numbers 1,2- so on insider their circles just like the other courses and can have same animation then.  since a circle having number inside definitely doesn't look clickable but a task to complete and filling it with colours does show that the task has been completed.

@jdwilkin4 Thanks for the feedback. I will check it out


Stop spinner for item hasn't comment

Issue:
Open the ItemView which that Item hasn't any comment, the spinner will
be there all the time.
How to fix:
Set the loading to false if there is no comment.

set loading to false has side effects. If you open the itemview has comments by url http://localhost:8080/item/15342486 directly or refresh the page, the spinner won't show


Bump Zombienet to v1.3.71; Bump Polkadot-SDK to 1.2.0

Lets bump the dev container versions too
https://github.com/paritytech/polkadot-api/blob/main/.devcontainer/Dockerfile#L4

Lets bump the dev container versions too

Good catch! thank you @ryanleecode


No "Mini" Casters

It's currently possible to get stuck without a way to cast "Mini" to get into the tiny village.

Hello, I'm reviving this project and going through issues - this should be fixed already.


Add ability to use dynamic spaces

FYI @dlaird-ovo I've opened a PR with your changes against a dev branch, where we can keep our custom changes and sync with main from the upstream repo.
The plan is to tag from this branch and reference those in our backstage deps.
This might not run the tests yet as I still need to sort out the workflows, but I'll still open the PR for now.
@dlaird-ovo are those changes up-to-date or have you actually made any other changes since then?

Will try and take a look today / tomorrow as I am clearing my backlog of tasks that suddenly built up.

Finally reviewed the changes - with those in repo and locally.  All looks good to me.

I had thought about that before - but then completely forgot about it!

Hi @dlaird-ovo, would you be able to review and merge the following PR to progress this?
https://github.com/dlaird-ovo/backstage-plugin-confluence/pull/1?

Done - Merged :-)

Perfect, thank you Dan.


Update CHANGELOG.md

Changelog was missing the added reachable workspace computation that was added in pinocchio 3

Hi ! This project doesn't usually accept pull requests on the main branch.
If this wasn't intentionnal, you can change the base branch of this PR to devel
(No need to close it for that). Best, a bot.


Backport/backport 1253 to 2.1

Description
create manual backport PR. auto process failed, followed instructions in original PR 1253.
Issues Resolved
N/A
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.

i was doing a manual backport request, and there are too many commits attached to this PR. not sure what I did wrong, but definitely need to close this, it's not correct.


API for drawing shapes

It'd be awesome to have an API for drawing a curves, lines, polygons, and whatnot in a declarative way. This would be really helpful for some of the UI we're working on in MS80.

You can use the new Canvas widget for this, which is functional but very rough.


🐞[bug]: Fixing the images on services page

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
On services page there are some photos which are not looking appropriate and are squeezed.the services page, some photos
Expected behavior
I want to make the images to their original size so that they look proper and professional.
Add ScreenShots

What browsers are you seeing the problem on?
Chrome
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24EXTD contributor
[X] I have starred the repository

@Kiran-F  go ahead.

I have created a pull request to resolve this issue. Kindly review my PR. @Anjaliavv51

@Anjaliavv51 have you considered my PR for this issue cz I can't see mine in the pull requests section. Kindly inform my regarding this.


remove about

Upon mentioning word about
camperbot displays spammy useless message saying:
' you need to ask about @someone! '
this should be removed.

I agree - this shouldn't trigger unless it has a target.

I'll take this up, would need some setup to get camperbot running locally, but it should also help with #120.

@Manish-Giri awesome - thanks for helping with this.