Add heading levels to Extensions page

Summary of the pull request
I enabled the narrator in scan mode to read the heading levels of the "Installed" and "Available in the Microsoft Store" headings on the Dev Home Extensions page by adding Automation.HeadingLevel properties to each text block.
References and relevant issues
https://task.ms/52443515
Detailed description of the pull request / Additional comments
Before:
https://github.com/user-attachments/assets/41702b43-b71a-4c46-9541-f9f86f11a9a1
After changes:
https://github.com/user-attachments/assets/f3cac5e5-8bd8-4347-94ae-896b02cbc1d7
Validation steps performed
PR checklist

[ ] Closes #xxx
[ ] Tests added/passed
[ ] Documentation updated

I want to make sure I understand the second issue correctly.
The issue is the narrator is not announcing the headers in the extension list.
This is happening because the first interactable element isn't a top element.  This results in narrator correctly announcing the tabbed-to element, but not the header.  Does that sound right?

Good to know that switching settings is not a fix. Let's find a resolution.
I think we're on the same page:

The second issue is that the groups were not being announced. The group names are the same as the heading titles. I apologize for confusing those earlier.
As of the last commit, the "Installed" group is announced at the default verbosity level because the "Get Updates" button is a child of the "Installed" group. Now, only the "Available in the Microsoft Store" group is not announced.
The first interactable element in the "Available in the Microsoft Store" group (the "Get" button on the first extension in the list) is within an extension item group. My understanding is that since the "Get" button has a parent group, by design the narrator announces only the parent group ("Microsoft Game Dev Extension" group) and not the grandparent group ("Available in the Microsoft Store"). Is top element another word for child element?

Here's the current narrator behavior (default verbosity, scan off):
https://github.com/user-attachments/assets/d3e59bd5-b3d1-4eb0-a5ca-2a297bac1208
One workaround we considered was changing the extensions from a SettingsCard (which is its own group) to a button so that both the "Available in the Microsoft Store" group and the extension name were announced. We decided to not take this approach because we wanted to mimic the UI design of the Microsoft Store. Although the Microsoft Store has a similar two-group layout, the groups on its LibraryPage are announced because each group has buttons and/or navigation elements as children:

Another team ran into a similar issue where a grandparent group was not read: https://task.ms/32064580. They had concluded that the narrator behavior was by design and didn't make any further changes. Therefore, I think best approach would be a workaround.
I'm not sure where to start:

Can we customize the narration behavior for this page?
Can we move or add an interactable element to the "Available at the Microsoft Store" group that would benefit all users? (The MS Store library has a sort button)

I've updated the current PR to address just the heading level fix. If I can find a workaround for the "Available in the Microsoft Store" group narration, I will make a separate PR for it. Otherwise, I will close that bug as external.


use stable coveralls version

I reenabled coverage as PR test now that the merging works.

We don't get coverage for the gdc/ldc code b/c it's in a separate build btw.


Error on Docker back-ends with 1.7 not present in 1.6.6

Bug
or a kind request for help or explanation of change/documentation.
What did you do?
Using Traefik 1.7 on Docker (image: traefik:latest) without defined traefik.backends defined causes errors not present in 1.6.6 - no front ends appear.  Moreover when attempting to specify the backend by label no front-ends appear with the same errors...
What did you expect to see?
No output as with 1.6.6.
What did you see instead?
isle-proxy-ld     | time="2018-09-27T19:31:37Z" level=error msg="undefined backend 'backend-traefik-isledevelopment' for frontend frontend-Host-admin-isle-localdomain-1. Skipping frontend frontend-Host-admin-isle-localdomain-1..."
isle-proxy-ld     | time="2018-09-27T19:31:37Z" level=error msg="undefined backend 'backend-isle-portainer-isledevelopment' for frontend frontend-Host-portainer-isle-localdomain-0. Skipping frontend frontend-Host-portainer-isle-localdomain-0..."
isle-proxy-ld     | time="2018-09-27T19:31:39Z" level=error msg="undefined backend 'backend-traefik-isledevelopment' for frontend frontend-Host-admin-isle-localdomain-2. Skipping frontend frontend-Host-admin-isle-localdomain-2..."
isle-proxy-ld     | time="2018-09-27T19:31:39Z" level=error msg="undefined backend 'backend-apache-isledevelopment' for frontend frontend-Host-isle-localdomain-PathPrefix-adore-djatoka-cantaloupe-0. Skipping frontend frontend-Host-isle-localdomain-PathPrefix-adore-djatoka-cantaloupe-0..."
isle-proxy-ld     | time="2018-09-27T19:31:39Z" level=error msg="undefined backend 'backend-isle-portainer-isledevelopment' for frontend frontend-Host-portainer-isle-localdomain-1. Skipping frontend frontend-Host-portainer-isle-localdomain-1..."

Output of traefik version:
Version:      v1.7.0
Codename:     maroilles
Go version:   go1.11
Built:        2018-09-24_09:57:21AM
OS/Arch:      linux/amd64

What is your environment & configuration:
Docker on CentOS; Docker on Mac OS.
toml config:
https://github.com/Islandora-Collaboration-Group/ISLE/blob/master/config/proxy/traefik.toml
docker-compose: (have since downgraded from latest to 1.6)
https://github.com/Islandora-Collaboration-Group/ISLE/blob/master/docker-compose.yml
Thank you!

@br2490 could you provide more logs (from the start of Træfik) and do you have a minimal reproducible case?

@ldez https://gist.github.com/br2490/a1804ffc5fe696c3a4131e643dc7cd7a
Unfortunately I do not have a minimal reproducible case.

I think the problem is here:
time="2018-09-27T21:34:16Z" level=warning msg="unable to find a binding for the container \"/isle-apache-ld\": ignoring server"
time="2018-09-27T21:34:16Z" level=warning msg="cannot determine the IP address (got <IP_ADDRESS>) for the container \"/isle-portainer-ld\": ignoring server"
time="2018-09-27T21:34:16Z" level=warning msg="cannot determine the IP address (got <IP_ADDRESS>) for the container \"/isle-proxy-ld\": ignoring server"

Could you try to remove usebindportip = true?

Heck yes I can and did!  Works perfectly now 👍
Will this be an issue in multi-environments through the single proxy? i.e. spinning more than one of these "ISLE" stacks up?
Thank you @ldez! 💯

FYI, before #3638 the behavior was buggy because usebindportip doesn't really work.
I don't think it it's a issue in multi-environments.

Now the frontends are not available via HTTPS.  Is there something else wrong?
https://gist.github.com/br2490/c1cc49555240303df638e0b036d2b49f

The https entry point exists:
time="2018-09-27T22:55:57Z" level=info msg="Preparing server https &{Address::443 TLS:0xc0000103f0 Redirect:<nil> Auth:<nil> WhitelistSourceRange:[] WhiteList:<nil> Compress:false ProxyProtocol:<nil> ForwardedHeaders:0xc0006bca40} with readTimeout=0s writeTimeout=0s idleTimeout=3m0s"
...
time="2018-09-27T22:55:57Z" level=info msg="Starting server on :443"
...
time="2018-09-27T22:55:57Z" level=debug msg="Creating entry point redirect http -> https"

But seems not be applied to your frontends.
{\"backends\":{\"backend-isle-portainer-isledevelopment\":{\"servers\":{\"server-isle-portainer-ld-af38c7d17d35b49dd0f7bb8527d5970f\":{\"url\":\"http://<IP_ADDRESS>:9000\",\"weight\":1}},\"loadBalancer\":{\"method\":\"wrr\"}},\"backend-traefik-isledevelopment\":{\"servers\":{\"server-isle-proxy-ld-a70155c11090148735dd5b54e77f41d5\":{\"url\":\"http://<IP_ADDRESS>:8080\",\"weight\":1}},\"loadBalancer\":{\"method\":\"wrr\"}}},\"frontends\":{\"frontend-Host-admin-isle-localdomain-0\":{\"entryPoints\":[\"http\"],\"backend\":\"backend-traefik-isledevelopment\",\"routes\":{\"route-frontend-Host-admin-isle-localdomain-0\":{\"rule\":\"Host:admin.isle.localdomain;\"}},\"passHostHeader\":true,\"priority\":0,\"basicAuth\":null},\"frontend-Host-portainer-isle-localdomain-1\":{\"entryPoints\":[\"http\"],\"backend\":\"backend-isle-portainer-isledevelopment\",\"routes\":{\"route-frontend-Host-portainer-isle-localdomain-1\":{\"rule\":\"Host:portainer.isle.localdomain;\"}},\"passHostHeader\":true,\"priority\":0,\"basicAuth\":null}}}

Check that defaultEntryPoints = ["http","https"] is at the top of the file.
You can also try to add the label traefik.frontend.entryPoints=http,https on containers.
In order to keep the issues consistent, and because this is another topic, I suggest you continue the discussion in the #support channel in Slack.

Experienced the same issue. Traefik v1.6.6 works just fine, v1.7 complains about not finding bindings for various containers. Getting rid of usebindportip = true in traefik.toml fixed it.

Thanks @ad-bitmed for your message.
I'd like to put emphasis on the purpose of the usebindportip option for the docker provider.
This option tells traefik to use the containers' bound ip/port for the route instead of their internal ip/port. This option should have very specific use cases (for instance when your traefik instance isn't on the containers' network).
Before 1.7, this option was broken (traefik was unable to detect the bound ip/ports because of a case sensitivity issue #3622) and we fixed its behaviour. By fixing the behaviour, some users (including you) find that traefik complains that it cannot find the required (because of the option) binding for some containers.
Even if this strict behaviour could be defendable, I'm thinking that we should fallback on the container ip/port "if" there is no "complete" binding for the container. This mechanism should enable people to use a mix of binds / no bind for their setup.

These logs only appear if you use useBindPortIP:
https://github.com/containous/traefik/blob/546bebc860001aa96c0c6c3e4e54b8cc454c4605/provider/docker/config.go#L341-L349
Check your configuration (TOML, CLI, ...)


fix: Refactor and removal of duplications in E2E tests

Improve E2E tests code.
How to test
Check if CI logs are easy to read and give meaningful information.
To see failed (or success) logs from CI jobs, click on details link of the job in the PR in GitHub. After that, click on Artifacts link, in top right corner of PROW webpage. Then, click on artifacts folder, the job name folder (operator-e2e-aws, for example), e2e folder and finally build-log.txt file.

/hold

/retest

/cherry-pick oadp-1.3


The waybar workspace module is lost or overlapped

Has fixed
waiting waybar merge:
Fixed variable synchronization exception caused by the "hyprland/workspace" module

done


Broken docs site

material-ui.com loads v 3.4.0:

When I unregister a service worker I have 3.5.1. But after closing console and reloading a page I have 3.4.0 again :(
Service workers sometimes are so confusing.

@rogovdm You also need to clear the cache of the browser.

After purging all caches I have 3.5.1 version. After page reload it reverts to 3.4.0

@rogovdm The service worker also needs to activate on all the tabs.


Lead the viz. content for GeoCAT tutorial

Preliminary plan for visualization components, GeoCAT-examples and GeoCAT-viz (~1** hr):

Gallery walk-through
How to run examples and re-create the gallery

Hopefully Binder
Local config as backup

GeoCAT-viz

Via Taylor diagrams

Interactive plotting

FYI: @erogluorhan @anissa111 @michaelavs @hCraker

@marodrig Please checkin with @pilotchute  to organize things whenever needed .


feat(protocol-designer): migration version and tcd to flexible steps

This introduces a migrationVersion key to the designer-application data portion of the protocol.
This value can be checked going forward on load to gate performing various migrations on the file.
This also intoduces the migrations necessary to allow users to upload and edit their pre-flexible
step protocols to PD after the release of flexible transfer
Closes #2917

I tested how the procedures are generated after migration. A few things to address outside of the Mix form and TDC asp/disp mix commands:

flow-rate and offsetFromBottomMm are being set to undefined when they should be excluded from the command params -- not sure where

"Pre-Wet Tip" seems like it's being ignored -- this is one of the fields that changed aspirate_preWetTip --> preWetTip. I don't see that field in the mig1 fn

Blowout is getting ignored -- I think dispense_blowout_location needs to be handled in mig1 fn (it only handles the dispense_blowout_checkbox but not the location. The mig1 fn does handle dispense_blowout_labware but I don't know if that is a thing?)

Touch tip commands are missing -- I think aspirate_touchTip --> aspirate_touchTip_checkbox and dispense_touchTip --> dispense_touchTip_checkbox need to be included

Example test to reproduce these issues (run it thru the proceduresMatchSnapshots):
preFlexAdvancedNoMix.json.zip


16 add method to sort alive people by hand strength

Codecov Report

Merging #20 (869800b) into main (0d9346b) will decrease coverage by 0.83%.
The diff coverage is 90.76%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main      #20      +/-   ##
==========================================
- Coverage   95.66%   94.84%   -0.83%
==========================================
  Files           4        4
  Lines         323      388      +65
==========================================
+ Hits          309      368      +59
- Misses         14       20       +6

Impacted Files
Coverage Δ

src/table.rs
94.38% <90.76%> (-1.80%)
:arrow_down:

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


add feed follow count function

fixes #260
merge once API supports client tokens

This is merged into CI and works, will deployed tomorrow morning to prod, merging.

@mahboubii v6.1.0 is good to release.


100% cpu usage with compositors.

Kudos for the great work so far! This is my favorite small project!
Everything is working fine when using a twm. Everything works fine when having the compositor disabled. If i launch warp with the compositor enabled it starts using 100% of the cpu. I actually see "warp -d" and "/usr/lib/Xorg using 100% cpu.
But I found a trick. Disabling the compositor, launching warp and re-enabling the compositor seems to help but is kinda random sometimes.
I am having this issue inside KDE. I know having this working on a DE isn't the main point here but... would be just nice and why not.
If you need any help for testing I'll be here!

Thanks :). I believe the bug that was causing this has been fixed in the latest commit. I will leave it to you confirm and close the issue.

It is fixed! Great job!


add ForceResizeAug in CreateAugmenter

The previous CreateAugmenter can only resize the short edge of an image. ForceResizeAug is not supported in it.

Please update and resolve conflict

@piiswrong , sorry that I don't really know how this conflict came up. I only add an optional type of the resize argument in CreateAugmenter.
The error above is:
======================================================================
FAIL: test_operator_gpu.test_l1_loss
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/local/lib/python3.4/dist-packages/nose/case.py", line 198, in runTest
    self.test(*self.arg)
  File "/usr/local/lib/python3.4/dist-packages/nose/util.py", line 620, in newfunc
    return func(*arg, **kw)
  File "/workspace/tests/python/gpu/../unittest/test_loss.py", line 165, in test_l1_loss
    assert mod.score(data_iter, eval_metric=mx.metric.Loss())[0][1] < 0.1
nose.proxy.AssertionError:

This issue is closed due to lack of activity in the last 90 days. Feel free to ping me to reopen if this is still an active issue. Thanks!
Also, do please check out our forum (and Chinese version) for general "how-to" questions.


Possibility to create IAM Identity Center (IIC) users and groups, not just assignments?

Is your feature request related to a problem? Please describe.
To my understanding, in order to create Identity Center assignments for users and group, the user/group must exist first?
I don't see any way to create IIC users and groups through the LZA, or am I missing something?
Describe the feature you'd like
Would it be possible to create and maintain the list of users and group within the identityCenter block?
Additional context
iam-config.yaml:
identityCenter:
  name: cloud-foundation-sso
  delegatedAdminAccount: Audit
  identityCenterPermissionSets:
    - name: CustomPermissionSet-Admin
      policies:
        awsManaged:
          - AdministratorAccess
    - name: CustomPermissionSet-Test
      policies:
         awsManaged:
           - AdministratorAccess
      sessionDuration: 60
  identityCenterAssignments:
    - name: AdminAccess
      permissionSetName: CustomPermissionSet-Admin
      principals:
        - type: USER
          name<EMAIL_ADDRESS>        - type: GROUP
          name: Administrators
      deploymentTargets:
        organizationalUnits:
          - Root
    - name: TestAccess
      permissionSetName: CustomPermissionSet-Test
      principals:
        - type: USER
          name<EMAIL_ADDRESS>      deploymentTargets:
        accounts:
          - SharedServices

The first assignment creates the assignment for the user (because I manually created it in IIC) but not the group (not created manually)
The second assignment creates no assignments (user not created manually)

Hi Stefan!
That is correct. For the LZA solution to add an account assignment for a User or Group, that entity must exist. You could either use the principal ID (for the user/group) or have LZA do the lookup (similar to your example) where it would then subsequently add the configured account assignments. We have a feature request for LZA to provision users and groups in Identity Center, which I have added this GitHub issue to that feature request for more traction and prioritization. I will keep this issue open in the meantime should you have any questions or concerns that need to be addressed.

Thank you @bo1984 for the detailed explaination!


Upgrading to 1.16.2 does not work

Gitea Version
1.16.2
Git Version
No response
Operating System
Docker
How are you running Gitea?
Using the official docker image gitea/gitea:1.16.2.
Database
MySQL
Can you reproduce the bug on the Gitea demo site?
No - Not relevant I guess?
Log Gist
https://gist.github.com/kolaente/275fe9b431bc85feff1e42cc1a1fb40f
Description
Upgrading from gitea 1.16.1 to 1.16.2 fails with
[E] ORM engine initialization attempt #9/10 failed. Error: migrate: migration[210]: v208 was completely broken - remigrate failed: unable to (re)insert webauthn_credential[6]. Error: Error 1062: Duplicate entry 'fido-1' for key 'UQE_webauthn_credential_s'

Removing the key from the database would probably fix it, but I guess it would also require me to re-add the key to my account?
Screenshots
No response

Can confirm removing the key entry it complains about lets me upgrade properly.

Maybe duplicate of #18889


Allow variables in LaunchApp command

Sometimes the appId needs to be adjusted based on environment. For example if there are different build variants of the same app. Currently injecting variables is only available for a subset of commands (TapOnElementCommand, AssertCommand, InputTextCommand and OpenLinkCommand).
I propose to also allow injecting environment variables into the LaunchAppCommand.

This is now a part of 1.7.1. Credit goes to @whlk 👍


Class based views are not supported

When using web.View as the handler if the route being added for '*' then cors doesn't work because the server seems not to be able to find the OPTIONS. Not sure why that is, I didn't take the time to investigate but my guess is that the * end up taking priority and the routing goes to the * handler instead of the CORS handler.

@trivigy thank you for posting this bug report and sorry for the long delay.
Yes, as I see * handler from class based view's (CBV) takes precedence over OPTIONS handler being added by aiohttp-cors, and I don't see easy way to handle CBV classes in aiohttp-cors so currently it will not work with them.
Perhaps best solution will be to introduce aiohttp-cors mixin for CBV which will handle OPTIONS and require users to inherit from it, like:
# Not implemented yet
from aiohttp_cors import ViewMixin

class MyView(ViewMixin, web.View):
    async def get(self):
        return await get_resp(self.request)

    async def post(self):
        return await post_resp(self.request)

Makes sense

I am using the following workaround to register my classes so that they work with aiohttp_cors:
def register_view(app, url, view):
    for method in ('get', 'post', 'delete', 'put'):
        handler = getattr(view, method, None)

        if not handler:
            continue

        app.router.add_route(method, url, handler)

@balloob will aiohttp_cors.ViewMixin mixin will help you if it will be implemented in aiohttp_cors?

Probably - but I was already using views in a weird way: I wanted to instantiate the views before registering them so I could keep a reference to the state of the house (I'm working on Home Assistant). So I actually had a __call__ method on my instantiated view that would handle the routing to get/post etc. (I know that it's not the right way but we're transitioning from CherryPi WSGI server + Werkzeug and getting it to work is the first step.)

@balloob if you want to instantiate your view classes before registering you don't need aiohttp.web.View at all -- custom classes may serve everything perfectly.

@rutsky Thanks for the suggestion. Took me a long time to notice that you responded. I actually use a very custom implementation of the View within our system. I personally wanted to add a whole lot more functionalities to the view and therefore re-implemented it. Had to override add_route() functions and all. Therefore this problem was never an issue for my systems but it was certainly a bug worth reporting.

@balloob's hack works ok for me as well, but I think a ViewMixin would be better.

Guys, we need a champion for the issue.
Do anybody want work on PR?

I recently changed job, moved to another country and on paternity leave right now, so I don't have free time right now, sorry.

@asvetlov @rutsky would please review my PR?

Let me setup coverage tools first, I'll return to review after that.

👍 💯


Describe Userflow

Describe user flow with Figma based on the project description

All fixed.
@cyrillicw check please.


Add favicon to the site

@Shailendra1703  Please merge this PR. as I added the website's icon.
Thank you

@Shailendra1703 Please merge the PR.
Thanks.

Hello @Sandigupta , thanks for the PR but it's not a website, it's a chrome extensions while that favicon works well for the site but it didn't actually worked for chrome extension

can you please check on that

Okay, I am doing it.

@Shailendra1703
Can you merge this PR.

Okay, I am doing it.


Fix broken link in Move language readme

Motivation
The grammar and parser for the Move IR links in Move Language readme are broken.
Pointing them to the newest code link should avoid confusion to new users.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
No code changes.
Related PRs
N.A.

@Wuvist #229 seems to implement the same fix.

@safeforge Yup, just realized that, was thinking that #229 is about the website.
Thanks, I will close this PR.


debugger not working properly since upgrade to latest version

Version: 1.40.1
OS: Linux x64 4.15.0-70-generic
Steps to Reproduce:
Just using the same flow of running a configured debug. Everything was working fine until I updated vsCode yesterday.

Does this issue occur when all extensions are disabled?: No

/needsMoreInfo
Please provide detailed steps so that we can reproduce the problem. Which debugger are you using? What exactly does not work properly?

both node and nodemon debuggers. But it's working now, I think the restart after the installation fix it.
Thank you


Add conversion step for python.parsing pdbs

Hopefully this will fix the symbol publish error here:
https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1331578/
The root cause (or at least one of the causes) was that the pdbs for the Microsoft.Python.Parsing dlls were portable pdbs. The symbol archiver in the build doesn't support portable, only windows pdbs.

wow nice.


[CI] Removed push event from workflows

[CI] Removed push event from workflows
Signed-off-by: Esteban Martinena<EMAIL_ADDRESS>

Closing in favor of https://github.com/open-rmf/rmf_traffic/pull/89


A minor typo

Hi,
I found a minor typo in this particular file. Kindly please check it and merge the pull request if you find it valid.
Thanks!

:+1:

Good catch, thanks @amitmerchant1990.


How to use this with Remix.js?

Hey thanks for working on this. Would be great to see an example of implementation on how to use it on Remix.js

I'll try to put an example if possible during the weekend and update this thread.


Task-4

Issue : #5
Commands :

mkdir command to create folder
touch command to create file under the folder

Output :

Hey @ASHTAD123
Thanks for opening this PR 🚀. Mentor will review your pull request soon and till then, keep contributing and stay calm.
Thanks for contributing in OpenCode'24 ✨✨!

Hey @ASHTAD123
Your PR has been merged 🥳🥳 and you have earned 10 points.
Thanks for contributing in OpenCode'24 ✨✨


Has this project been abandoned?(!)

Ask your question
Haven't seen any changes / blog posts about it  in a while, just curious! Love the work you guys are putting in on nuxt-auth, but would love if this project was up to date with the latest modules as well.
Follow up - are you guys still open to PRs?
Additional information
No response

Hi @bhargavaman 👋
We have been a little bit less active within the last half year, as our resources have been pretty stretched. However, we committed to allocating more resources to work again on sidebase this year!
We have decided to prioritize the following projects:

Picking up development on v1.0 of NuxtAuth (read more here)
Begun working on a rewrite and v1.0 of NuxtPDF (read more here)

We have also begun discussing internally how we want to proceed with create-sidebase. I am currently still working on an outline for the planned changes, but I assume it will contain:

Deprecating the cheviot stack
Ramping up mantaince on the merino stack to ensure it always stays up to date
Adding a new unnamed stack, that will allow you to configure even more!

merino aims to be as simple as possible, however, we want to add another stack with more modules and different options for eg. Database providers (Prisma, Drizzle etc.) as well as many other nice setup perks to have!
We will avoid just adding Nuxt modules, that can be installed with the Nuxt CLI, as we see this as a bit unnecessary, therefore we will focus on integrating modules and packages that require more setup than just the one command!
However, this will lead to this stack being more opinionated, as we enforce our best practices!

Follow up - are you guys still open to PRs?

Yes, we are! Like I mentioned above, we are currently going through our projects (based of popularity) and working on them one by one, so it may take longer to merge a PR on eg. create-sidebase which is lower down on our priority list. However, feel free to ping me in the PR, so I receive a notification and can look into it 😄

Hi @zoey-kaiser 👋
Thanks for taking the time out to reply, much appreciated!


Docs: More details into utilizing the examples

The main readme only goes into depth for running the compose file. For those trying to experiment with http://localhost:8181/ it would be nice to have some query and scenarios to walk through.

Good idea; though it's more of a documentation issue than a bug;  so I've updated the label.

Yeah i would have changed the label but I am not allowed.

hey would love to work on it  but the localhost is not opening

HI @kunalranjan19 - what do you by " localhost is not opening"?  Are you running the OPAL-client with OPA in place?

Hey guys ,i would like to work on this issue , i have done the example policy setup and just trying to understand how is Opal and OPA are working.

Hi @lakshyabhasin509 that would be wonderful, feel free to submit these as .md files in a pull request.
Let us know if you need any guidance here
FYI: @filipermit

any one worked on this yet? i am interested in doing this. but would be needing a little guide.

Hi @Uthycloud  -  I think this one is up for grabs :)
Both @filipermit and I would be happy to provide guidance.
A good place to start is going yourself through the steps here: https://docs.opal.ac/getting-started/quickstart/opal-playground/overview
And then you can add more examples here: https://github.com/permitio/opal/tree/master/documentation/docs/getting-started/quickstart/opal-playground.
I'd suggest each example starts with showing loading policy and/or data with OPAL, and then checking on the result with queries directly to OPA (sharing both the policy, data, commands and queries being sent as part of the example).
You can draw inspiration, or even use as is the example we show in this recorded demo: https://youtu.be/A5adHlkmdC0?t=1297


Separate delete submission

Description
Separating delete submission routes into submissions/illustration/:week and submissions/story/:week. This is to allow writing of separate requests to BE to delete either illustration or story.
Fixes # (issue)
Both submissions of illustration/story within the week were being deleted concurrently when user intends for only one to be removed with FE 'refresh'.
Type of change

[x] Add logic to test if storyText has been inputted manually
[x] Separated delete submission routes into illustration / story routes

Change Status

[x] Complete
[ ] Testing

Decided to go about this in a different way


Using symbols messes up the memoized features

After using a symbol for creating a flipper, when reading back the flipper names, it is returned as a symbol. But after a restart, it is returned back as a string.
Symbol names should probably be converted to strings before saving them to the memoized list.

I ran into a problem that I think may be related to this. With ActiveSupport notifications (https://github.com/jnunemaker/flipper/issues/513) sometimes feature_name in the payload was a string, at other times a symbol. I couldn't figure out the pattern, but for safety I chose to always convert to a string before comparing.


How update visibility

Hi,
I added some custom fields, but now the integration process gives me the following error:
Posting to Stock Visibility failed on all records in this batch.
Batch task failed: Posting to Stock Visibility failed on all records in this batch.
Can you help me?

Hi @alejandro1990 ,
Please use our normal support cycle for this issue.


Lenovo L13 Nonworking IR Blasters

Please describe the issue in as much detail as possible, including any errors and traces
Attempting to set up the IR camera and it does not appear to work, the IR blasters do not initiate in any of the cameras (there are 5 /dev/video# options, of which only 2 do not throw an error on start, video0 and video2). any help would be greatly appreciated.

I've searched for similar issues already, and my issue has not been reported yet.
Linux distribution (if applicable):
Manjaro 20
Howdy version:
2.5.1-2

Unfortunately that probably means your IR camera is unsupported, can you open that camera in other applications?

The camera itself activates, however it appears that the IR blasters do not, here is an example image:

when running the test command found here: "gst-launch-1.0 v4l2src device=/dev/video2 num-buffers=10 ! image/jpeg ! multifilesink location="frame-%02d.jpg"
I get the following output:
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Internal data stream error.
Additional debug info:
../gstreamer/libs/gst/base/gstbasesrc.c(3072): gst_base_src_loop (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src0:
streaming stopped, reason not-negotiated (-4)
ERROR: pipeline doesn't want to preroll.
Setting pipeline to PAUSED ...
Setting pipeline to READY ...
Setting pipeline to NULL ...
Freeing pipeline ...
ccwky12@Manjaro-L13 ~ [1]>

Found a fix for the issue here:
https://github.com/boltgolt/howdy/issues/312
while not perfect, it does provide a band-aid solution, thank you so much for your help.


Config...again!

I have changed my config a bit, and now got the msg "warning unknown module 'rrule'" and the mirror doesn't start anymore.
So no problem, switch back the cfg, but still the same problem.
Used the sample config, same problem. Reset the repo, same problem.
I would appreciate a service that checks the config on every startup. Any ideas how to achieve this?

Ah, sorry. This is not your config. Will fix this within two hours. In the mean time. Try:
npm install rrule -g

Ah good to know, by now just my test system is affected, so my wake-up experience with the mm is not compromised ;)
-g is global right, isn't a local instal sufficient?

Could be. Just give it a try.

Thanks, I'll try it tonight.

Will push a fix in 3 minutes ...

Fixed! Don't forget do run npm install

still doesn't work. I did a npm install, deleted node_module did a install again, nothing changed, rrule is not found :(

Could you try npm install rrule

that worked, rrule is not in the dependencies, is this correct?

It is:
https://github.com/MichMich/MagicMirror/blob/v2-beta/package.json#L45
Are you sure you have the latest version?

Oh no! You're right, used the wrong remote...

😁


Unable to fetch the latest version when using --build flag

Describe the bug
When trying to download the artifacts from Arifactory using Jfrog CLI and specifying the --build option and it is expected to fetch the latest version but it is not fetching the latest version.
Steps to reproduce the issue:
Uploaded 3 artifacts to Artifactory in the following order:
EDP-edp-libraries-854115_20210310.1.tar.gz
EDP-edp-libraries-1152295_20210602.1.tar.gz
EDP-EDP-libraries-1163740_20210604.1.tar.gz
To upload the package and publish the build, we can use the below command:
jfrog rt u EDP-edp-libraries-854115_20210310.1.tar.gz divija-build-test --build-name=EDP-edp-libraries --build-number=854115_20210310.1
jfrog rt bp EDP-edp-libraries 854115_20210310.1
jfrog rt u EDP-edp-libraries-1152295_20210602.1.tar.gz divija-build-test --build-name=EDP-edp-libraries --build-number=1152295_20210602.1
jfrog rt bp EDP-edp-libraries 1152295_20210602.1
jfrog rt u EDP-edp-libraries-1163740_20210604.1.tar.gz divija-build-test--build-name=EDP-edp-libraries --build-number=1163740_20210604.1
jfrog rt bp EDP-edp-libraries 1163740_20210604.1
Downloaded the packages from Artifactory using JFrog CLI:
When we download the package using the below command:
jfrog rt dl divija-build-test/ --build EDP-edp-libraries*
with "--build EDP-edp-libraries" option --> the first uploaded package (854115_20210310.1.tar.gz) is resolved instead of the latest pacakge (1163740_20210604.1.tar.gz).
According to the documentation https://www.jfrog.com/confluence/display/CLI/CLI+for+JFrog+Artifactory#CLIforJFrogArtifactory-DownloadingFiles, it says when we use --build flag and If we do not specify the build number, the artifacts are filtered by the latest build number. So we are expecting to get the latest artifact version.
Expected behavior
It is expected to download the latest artifact version that was published. In our case latest package (1163740_20210604.1.tar.gz) should be resolved instead of the first uploaded package (854115_20210310.1.tar.gz)
Screenshots

Versions

JFrog CLI version: 1.48.1

Artifactory Version: 7.19.8

@santhoshjfrog  -
JFrog CLI 2.2.1 with this fix has been released.
Looking forward to your feedback on the fix.


Fix file naming generation issue, length under 14 chars, based on datetime hash when hours, minutes or seconds match zero

Depending on the current date/time filename generation might be under 14 characters, thus when pattern is used to fetch history files, files with names under 14 characters are discarded thus not shown in file history panel.
Example of date/time that leads into this issue, given:
var now = new Date('2017/07/08 00:06:00');

when we run through the file naming generation logic we'll end up with something like:
201707080600

where the time piece is wrongly represented by 0600.
/cc @zabel-xyz

Added in version 1.3.0


Added - queue level job management

Hi,
I noticed some issues when the number of items in the bull queue surpass 50K or more. It becomes very difficult to clear jobs like completed/failed etc. Sometimes the tab also crashes as the Javascript tries to load those 50K jobs all at the same time.
I added this hotfix to allow people to clear jobs right from the /queues controller.

Let me know about any changes.
Thanks!

Thank you for the PR, it has been merged in and is live on npm.

Thanks!, Another solution can be List virtualization

True. Unfortunately I didn't know much about React or even Angular at the time I wrote this. The front-end is definitely not as good as it could be.


Added a parallel version of test_camera

The cameras are now operated in parallel so that they can have
completely independent frame rates (entered by the user at the
start). Previously it was limited by the slowest rate. All other settings
are also unique to each camera and can be set by clicking on it's window
and a list of the controls is given after entering the frame rates.
The camera limit has been raised to 30 for experimentation.
The parallelisation was done by using a large concurrency::parallel_for_each
after opening the cameras instead of using an std::for_each at each step.

Thanks for making this tool. I think we ultimately want to make the camera management in psmoveservice work in parallel as well so having a test app is a good starting point. However I don't think this is actually updating the cameras in parallel.
The line where you do the parallel_for is simply opening the camera windows in parallel, not running the windows in parallel. See cv::namedWindow.
The camera polling is still happening serially in a while loop. The actual blocking video frame read operation happens on this line:
https://github.com/cboulay/PSMoveService/pull/373/commits/a4006023fff1bd17435ce10dea27f8d110a28b3d#diff-1e48dd3f5e2eca542ab04fc6fb9335a4R79
If you wrapped this stuff:
// Render each camera frame in it's own window
cv::Mat frame;
(*state.camera) >> frame; // get a new frame from camera

if (!frame.empty())
{
    imshow(state.identifier.c_str(), frame);
    state.last_frames++;
}

In it's own function and then called that in a parallel_for that might work.

@HipsterSloth Are you sure it's not polling the cameras in parallel? It certainly seems to be. I thought if it was still serial it wouldn't be able to return different calculated frame rates.
The while loop and mostly everything else after opening the windows is now in the same parallel_for_each so I thought the cameras should be completely independent. Initially I tried simply changing every for_each to a parallel one but this didn't work which is why I then tried a giant parallel_for_each over most of the program. I thought this would create one while loop per camera and so would work in parallel.

Ohhh. I'm sorry! When I read this code in the github diff window:
+	concurrency::parallel_for_each(
 +        camera_states.begin(),
 +        camera_states.end(),
 +		[&camera_states](camera_state &state) {
 +            cv::namedWindow(state.identifier.c_str(), 1);

I missed the fact that the closing brace didn't only encompass the cv::namedWindow. I proably should have just sync'ed the file locally and looked at it in a proper editor window. Yeah that looks fine to me. Apologies for my confusion.

No worries. It's the first time I've made something perform in parallel and so wasn't sure if I'd misunderstood something.


Multi-GPU training

Hi,
First of all, thanks for sharing.
I learned a lot from the code. Right now, I'm turning my attention on multi-gpu training for neural nets. It is very expensive to run the imageNet multi-gpu code. Could you please add a feature, which would allow us to run the code on multiple GPUs? Thanks!
Best,
Jun

Hi, check https://github.com/facebook/fb.resnet.torch it has multi-GPU training for CIFAR-10

Hi, good to know! Thanks for the quick reply! :)


optimize: timing to get the system time

Ⅰ. Describe what this PR did
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

@litianyu1992 What is the purpose of this PR?

@litianyu1992 What is the purpose of this PR?

印象中在并发量大的情况下，原方式会卡顿

@litianyu1992 What is the purpose of this PR?

印象中，原方式在并发量较大时会有卡顿

@litianyu1992 What is the purpose of this PR?

印象中，原方式在并发量较大时会有卡顿

Is the slow performance due to metrics?

PMD failure


Norm to not use namespaces in small teams

This part of the documentation implies that namespaces are not generally used on smaller teams. This may be true in some cases, but namespaces provide important security boundaries and logical isolation for, say, open source projects that you might be running in your cluster.
[ref.]

For clusters with a few to tens of users, you should not need to create or think about namespaces at all.

I think this sentence could be omitted for clarity as it could be misleading in some contexts!

I can help with removal of the non helpful comment mentinoend in the issue.
/assign

Hey @steve-hardman! This is my first time opening up and issue, and I'm interested in contributing. Could I open up a PR, and have you review it? Would be great to have your eyes on it before I merge!

/kind feature
/sig docs
/assign @jackzellweger
As no has raised a PR yet, you are free to open it. But try to improve overall documentation of that page rather than fixing 1-2 words in a sentence.

This is my first time opening up an issue, and I'm interested in contributing. Could I open up a PR

Sure please go ahead with fixing it!

@steve-hardman @aj11anuj  Thanks! Am on it.


update go to 1.23.1

Would it be possible to split this into PRs updating the vendored filed and them go 1.23, in case either causes issues?


Update emojis.json

New Keywords Added That help to improve the emoji strength.

Update New Keyword To emojis.json file :+1:


For statement static check

for statement static check
Disallow for statements with empty init, test and update statements.
e.g. for (;;) {}
It allows statements of the form, for (let i = 0; i < 10; ++i) {} and let i = 0; for (i = 0; i < 10; ++i) {}

LGTM


Unable to enter "Replacement mode" in 0.12.1

Steps to reproduce the problem:

Start mitmproxy
Press "R" (Uppercase R) to enter "Replacement" mode to enter expressions
Nothing happens

What is the expected behavior?
The screen to enter "Replacement" expressions should appear to enable entering the filters and regexes to replace as per the doc in http://mitmproxy.org/doc/features/replacements.html
It's noted that the "on-screen" help doesn't show "R" as a shortcut.
What went wrong?
Not sure - no editor appears so there's no option to enter replacement
Any other comments?
This is a key feature of mitmproxy for me.

mitmproxy version: mitmproxy 0.12.1
Operating System:
ProductName:	Mac OS X
ProductVersion:	10.9.5
BuildVersion:	13F34

The feature moved into the options screen - you can press o R to open the editor. If you feel strong enough
Cheers,
Max

Thanks for the information - shouldn't the docs be updated to reflect this?

Sure - thanks for pointing that out. This basically applies to all features in the option screen, we definitely need to review the docs. If anyone wants to give it a go, help is highly appreciated.


graph_editor.graph_replace produces WARNING

Since version 1.0.0 the method tensorflow.contrib.graph_editor.graph_replace raises the following warning:
WARNING:tensorflow:VARIABLES collection name is deprecated, please use GLOBAL_VARIABLES instead; VARIABLES will be removed after 2017-03-02.
Minimal reproducible example
import tensorflow as tf
import tensorflow.contrib.graph_editor as ge
a = tf.constant(1)
b = tf.constant(2)
c = tf.constant(3)
d = a +  b
e = ge.graph_replace([d], {a: c})

Output log
INFO:tensorflow:Copying op: add
WARNING:tensorflow:VARIABLES collection name is deprecated, please use GLOBAL_VARIABLES instead; VARIABLES will be removed after 2017-03-02.
WARNING:tensorflow:VARIABLES collection name is deprecated, please use GLOBAL_VARIABLES instead; VARIABLES will be removed after 2017-03-02.
INFO:tensorflow:Finalizing op: add

@purpledog

Since this is in contrib, we do not officially support this. @purpledog is the original author, but it should be easy to search in the code and find how to switch silence this warning. So a PR would be most welcome. Thank you!

As Contrib folder is deprecated , this issue is not relevant.closing this issue.


I cannot build the Example (iOS) project - error 'rive/file.hpp' file not found

Description
I have downloaded the example code from this repo & opened the Example (iOS) project in Xcode 15.4.
When I build the project the following error occurs:
'rive/file.hpp' file not found

It seems I can specify the Preview target instead; I don't know why there are multiple projects & some work & some don't.

@ManjitBedi probably makes sense to re-open this given it is still an issue.


CSS Side-Effect Imports not working anymore with Cloudscape

What version of Remix are you using?
1.16.0
Are all your remix dependencies & dev-dependencies using the same version?

[x] Yes

Steps to Reproduce

Pull https://github.com/joejemmely/remix-cloudscape
Run npm run dev

Expected Behavior
Styles should be extracted and applied
Actual Behavior
Styles are not extracted and applied. It used to work with unstable_cssSideEffectImports on 1.14.0

This looks like it's because Cloudscape contains files using the .css.js extension which Remix mistakenly thinks are Vanilla Extract files.
Similar to how Tailwind works in Remix, we might want to think about detecting the presence of the @vanilla-extract/css package before attempting to process these files. This still wouldn't handle the case where you want to use non-Vanilla-Extract .css.js files and Vanilla Extract at the same time, but that's much more of an edge case.

Thanks for the prompt response.

we might want to think about detecting the presence of the @vanilla-extract/css package before attempting to process these files

Related to this, I noticed that if name is missing in the package.json, the project will fail to build with Couldn't find parent package.json with a name field from XXX, the error is thrown in vanilla-extract-plugin, even though it's not installed. And even if vanilla-extract-plugin was installed, most remix apps won't have a name defined in the package.json. Is the name necessary for vanilla-extract to work properly?

Thanks for raising this issue! This should be fixed in the next release.

I gave the fix a try but it didn't work as expected. @remix-run/dev takes a dependency on @vanilla-extract/integration so there currently isn't a nice way to not have any of the vanilla-extract dependencies.

@joejemmely Thanks for the update. You're right, I missed that @vanilla-extract/css can still be requirable from your app since Remix depends on @vanilla-extract/integration which in turn depends on @vanilla-extract/css. I've just merged a PR that updates the detection logic so we now look in your app's package.json to see whether you have a direct dependency on it.

@joejemmely Could you try again with the latest nightly?

Works like a charm 🥳 Thanks for your help


Setting munge key does not restart the munged service

Related to #14.
Running snap set slurm munge.key=<KEY> does not automatically restart the munged service. The user has to manually run snap restart slurm.munged in order for munged to pick up the new key.

Hmm... so this one is intentional. This key being synchronized across the cluster is crucial to Slurm's functionality. If your munge key gets out of sync during a refresh, your entire cluster will collapse. No exit code is emitted by Slurm as well if the keys do not match. The Slurm daemons will still be marked as active even though they cannot communicate with each other. My concern here is with being able to do controlled refreshes of the key. This is the typical flow I've seen for refreshing the munge key in a Slurm cluster:

Update the munge key on the main Slurm controller (slurmctld)
Propagate the key out to the other Slurm daemons (slurmd, slurmdbd, slurmrestd)
Restart munged cluster wide

I think having the user explicitly restart munged when they're ready after all the keys have been set into position is better than doing it automatically in the configure hook since we can't necessarily guarantee how the user will go about setting the new key if they're just using the snap.
What if we included visual feedback in the shell indicates that the munged service needs to be restarted after setting a new key? There's already a message sent to the hooks log in $SNAP_COMMON:
$ snap set slurm munge.key=<key>
INFO: service `slurm.munged` must be restarted for latest key to take effect

This way we make it clear to the user that they need to restart munged for their latest changes to take effect, and gives them more control over the refresh.  Also, less chance of us eating their cluster unintentionally. Note that we can set our own refresh policy within the Slurm charms, so it's relatively inexpensive for us to set the new key and restart the service when we're ready from charm code.

Also, if we go ahead with the enhancement proposed in https://github.com/charmed-hpc/slurm-snap/issues/14, I will likely remove the option to configure the munge key using snap set ... and snap get ... since it could introduce coherency issues.

#14 was implemented, so I'm going to close this issue. You can still set the munge key via the snap configuration options, but we are going to remove this in the future when we go to fix #19 and refactor slurmhelpers


[BUG] Cannot be used with non-system python

Describe the bug
Running import picamera2 under python that is non-system python rasises ModuleNotFoundError: No module named 'libcamera'.
This is because dependency installation python3-libcamera creates python binding only for system python, rendering development of applications using picamera2 limited to current Pi OS base python version.
To Reproduce
first install all dependencies according to README.md then:
virtualenv venv --python /usr/local/bin/python3.11
source venv/bin/activate
pip install picamera2
python

from within python repl
import picamera2

which rasises
  File "<stdin>", line 1, in <module>
  File "/home/pi/libcamera/venv/lib/python3.11/site-packages/picamera2/__init__.py", line 1, in <module>
    from .configuration import CameraConfiguration, StreamConfiguration
  File "/home/pi/libcamera/venv/lib/python3.11/site-packages/picamera2/configuration.py", line 1, in <module>
    from .controls import Controls
  File "/home/pi/libcamera/venv/lib/python3.11/site-packages/picamera2/controls.py", line 4, in <module>
    from libcamera import ControlType, Size, Rectangle
ModuleNotFoundError: No module named 'libcamera'

Expected behaviour
Default recommended installation with pip with python bindings created for the python connected with pip. This would make isolated development on any python version possible.
Console Output, Screenshots
If applicable, any console output or screenshots that show the problem and associated error messages.
Hardware :
Raspberry Pi 4B running Pi OS Bullseye 64-bit

Hi, thanks for the question. You probably need your virtual environment to copy the system packages because not all are available via pip, for example:
python -m venv --system-site-packages my-env

Hi, thanks for the question. You probably need your virtual environment to copy the system packages because not all are available via pip, for example:
python -m venv --system-site-packages my-env

This won't work since the --system-site-packages adds the packages from the python version that is used inside virtualenv
This solved #341 since venv package creates only isolated packages and still uses system python virtualenv on the other hand creates an isolated packages and python environment.
I've confirmed that it won't work on a clean Pi OS 64-bit with source-compiled python 3.10
BUT to actually check if you can use picamera2 with python different that which the system provides I've done a simple test

installed clean Pi OS 64-bit
updated & upgraded
upgraded pip for system python
installed python 3.10.8 from source
upgraded pip for installed python
run a sanity check on system python without virtualenv

Python 3.9.2 (default, Feb 28 2021, 17:03:44)
[GCC 10.2.1 20210110] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import picamera2
>>> picamera2.__file__
'/usr/lib/python3/dist-packages/picamera2/__init__.py'
>>> import libcamera
>>> libcamera.__file__
'/usr/lib/python3/dist-packages/libcamera/__init__.py'

created and virtualenv for system python with said flag

pip install virtualenv
virtualenv venv --system-site-packages
source venv/bin/activate
python

checked if the proposed works for system python it works

Python 3.9.2 (default, Feb 28 2021, 17:03:44)
[GCC 10.2.1 20210110] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import picamera2
>>> picamera2.__file__
'/usr/lib/python3/dist-packages/picamera2/__init__.py'
>>> import libcamera
>>> libcamera.__file__
'/usr/lib/python3/dist-packages/libcamera/__init__.py'

deactivated the virtualenv
created a virtualenv for python3.10

virtualenv venv10 --system-site-packages --python /usr/local/bin/python3.10
source venv10/bin/activate
python

checked for libcamera or picamera2

Yes, we can look into this, though I'm afraid I can't give any timescales at the moment. But thank you for the update!

Out of interest, the python libcamera bindings are normally found here: /usr/lib/python3/dist-packages/libcamera. If you rename the .so file in there to _libcamera.so, are you able to import that successfully using Python 3.10?

I'll give you an update once I run the tests on the clean Pi (OS reinstall + installing python3.10 takes a while)

Out of interest, the python libcamera bindings are normally found here: /usr/lib/python3/dist-packages/libcamera. If you rename the .so file in there to _libcamera.so, are you able to import that successfully using Python 3.10?

I installed fresh Pi OS 64-bit along with Python3.10.9 built from source with  --enable-optimizations --with-lto flags, renamed the mentioned file, rebooted, and just as suspected nothing happened.
Why can't you guys package the libcamera with python bindings and post it to pypi? If you're having problems with that @davisking did a great job handling dlib bindings with pybind11 maybe he can lend a hand.

Thanks, I think the maintainers here can handle it without me though :)

Has there been any progress on this or alternate solutions? Has anyone been able to upgrade to Python 3.10+ on a Raspberry Pi and still use Picamera2/Libcamera?
--system-site-packages does not work for me, libcamera is still not showing up in the virtual environment.

In a virtual env (I'm using poetry but it's the same for a simple venv), the sys.path contains /usr/lib/python3.9, so we can copy the libcamera module and its dependencies there and it will be available in all virtual envs.
sudo cp -r /usr/lib/python3/dist-packages/libcamera /usr/lib/python3.9
sudo cp -r /usr/lib/python3/dist-packages/pykms /usr/lib/python3.9

I got a bunch of errors such as:
libcblas.so.3: cannot open shared object file: No such file or directory
libopenjp2.so.7: cannot open shared object file: No such file or directory

which disappeared after installing the relevant libs.
sudo apt install libatlas-base-dev libopenjp2-7-dev

It's a bit insane to have to do that and I wish I understood why this package breaks virtual envs - doesn't everyone use some sort of venv nowadays for reproducibility of deployments? That's a big deal!
But it honestly goes over my head and since I can't fix it I can't complain :)

In a virtual env (I'm using poetry like #466 but it's the same for a simple venv), the sys.path contains /usr/lib/python3.9, so we can copy the libcamera module and its dependencies there and it will be available in all virtual envs.
sudo cp -r /usr/lib/python3/dist-packages/libcamera /usr/lib/python3.9
sudo cp -r /usr/lib/python3/dist-packages/pykms /usr/lib/python3.9

I got a bunch of errors such as:
libcblas.so.3: cannot open shared object file: No such file or directory
libopenjp2.so.7: cannot open shared object file: No such file or directory

which disappeared after installing the relevant libs.
sudo apt install libatlas-base-dev libopenjp2-7-dev

It's a bit insane to have to do that and I wish I understood why this package breaks virtual envs - doesn't everyone use some sort of venv nowadays for reproducibility of deployments? That's a big deal!
But it honestly goes over my head and since I can't fix it I can't complain :)

Thanks for the solution proposal. Although its very hacky I will give it a go and test it out with pi camera 3. Does you venv use newer python version like 3.11 or sticks to the system 3.9? BTW I think since Raspberry Pi Foundation sells the cameras you actually can complain when there isn't any proper solution for a very standard use case.

Thanks for the solution proposal. Although its very hacky I will give it a go and test it out with pi camera 3. Does you venv use newer python version like 3.11 or sticks to the system 3.9? BTW I think since Raspberry Pi Foundation sells the cameras you actually can complain when there isn't any proper solution for a very standard use case.

I tried it on a fresh rpi zero 2 using pyenv to run python 3.11.3, in addition to also copying picamera2 over, and I can say it does not work. In the end I just get the same error (No module named 'libcamera._libcamera').
I think this only works when your python version is the same as your system. But then you might as well just use the --system-site-packages trick anyway.

The problem that I can see is libcamera is compiled for 3.9. You can copy over picamera2 and libcamera from /usr/lib/python3/dist-packages/ to your virtual env...but the problem is libcamera won't import.
There is a file in the package called _libcamera.cpython-39-aarch64-linux-gnu.so. If you rename it to _libcamera.cpython-311-aarch64-linux-gnu.so, Python 3.11 will try to import it, but throws this error:
ImportError: Python version mismatch: module was compiled for Python 3.9, but the interpreter version is incompatible: 3.11.4 (main, Jul  6 2023, 09:14:44) [GCC 10.2.1 20210110]
I don't know enough about any of that, but is anyone able to compile this for 3.11?

@davidplowman are there any updates on this matter? We've actually downgraded the hardware from camera V3 to V2 on a 100+ devices scale since this issue forces us to work with python-opencv instead on picamera2.

Hi, I'm afraid there doesn't seem to be anyone here who knows about packaging something like this. I'm assuming it's only the libcamera Python bindings that are the issue and that everything else is OK, does that sound right? I don't know if it's possible for you to build libcamera yourself, it shouldn't be difficult, and presumably if you build it with a different version of Python then that would work for you? Sorry that I don't know anything more about this, but I would happily take advice from someone who does!

Well, in about a week from today the Picamera2 package will be 3 Python versions behind
Python3.12 release schedule. These cameras are not ready for the Python community, who by and large operate in virtual environments other than 3.9. Why complain? I now own ~$250 worth of dust collection surface.

@adamgogacz Raspberry Pi OS follows Debian long term (currently Debian 11). Until the next version of Debian Stable is  taken up by Raspberry Pi OS do not expect the picamera2 packages being based on a Python version later than 3.9.
FYI Debian 12 (Bookworm) uses python 3.11.

@tvoverbeek I think I may have found the ugliest solution. I have my_cool_fun.py in a virtual environment with 3.11 interpreter and fun_picam3_9.py  using the Picamera2 and running in the (base/system) environment. That is, fun_picam3_9.py gets launched (using Python's subprocess module) in the system (base) environment and both establish a socket connection using Python's socket module. Now, the the two functions can exchange data using Python's socket module and send whatever signals are required by the app. Crazy, eh?

@adamgogacz can't really see this as a solution. Apart from handling standard picamera2 code now you'll need to manage proper socket communication handling. Why even use the python-binded version when you can use straight up C engine and open the socket there.

@Kasperror I got it working perfectly fine, taking photos and shipping them off to AWS. Essentially you have a socket server (python3.11 in my case) and a socket connection (python 3.9 running the picamera) doing their while True thing, using pickle to serialize the data, have server issue a 'capture a still' command to the connection, connection capture a pic, send it back to the server, and eventually all sent to AWS via MQTT. It's actually not a lot of code. My picamera code is ~100 lines with error handling, and the socket server (3.11 code) is ~100 lines as well.

@adamgogacz Well to be honest creating a whole background process in different interpreter version and connecting in through a socket just to achieve goal of simply capturing a frame from a camera is not on my list of clean solutions. Let's just agree to disagree and hope that shortly there won't be a problem when pi foundation considers making up-to-date software for its hardware.

@adamgogacz Raspberry Pi OS follows Debian long term (currently Debian 11). Until the next version of Debian Stable is taken up by Raspberry Pi OS do not expect the picamera2 packages being based on a Python version later than 3.9. FYI Debian 12 (Bookworm) uses python 3.11.

Shouldn't you be able to build your libcamera against python 3.9, 3.10, 3.11 and 3.12 and upload all of them to pypi? This is what other python package providers are doing as well, if they need a python-version specific code of the library. Otherwise every python project that uses the camera depends on the system python.

Yeah, I'm going to comment here as well. But this has also been an issue for me.  This is what I use all my Pi's for; camera.  There are so many advantages to using a newer Python interpreter, especially for the camera stuff and all the new optimizations offered that having this saddled to a compiled library that only works with a specific version of Python seems short-sighted.  I tried many of the solutions here (before I found this report) all to come to the same conclusion.  I wasted SOOO many hours trying.  Where is the source code for the _libcamera.cpython-39-aarch64-linux-gnu.so library located?  Here?  If so, can we have clear instructions  on how to properly compile for the Pi against Python 3.11?

@JooJooBee666 Wait till the end of October. When RPi 5 will be available also Raspberry Pi OS will go to bookworm and Python 3.11. I am assuming libcamera Python bindings will also be based on Python 3.11 then for aarch64. Maybe @davidplowman can confirm this.

The Bookworm release has been announced now, so this will indeed bump Python to 3.11.
We are aware of the problems installing Python bindings for libcamera (and indeed kms++). We are planning to look into this again once the Bookworm and Pi 5 rush has settled down, though note that they aren't Raspberry Pi "owned" packages, so no promises as to what we might be able to do.

I haven't installed Bookworm yet, but if I do, are you saying this isn't currently working/updated in Raspbian?

@davidplowman This is better news.  I'm going to install this on my test unit and see how much this wrecks my crazy python camera stuff.  However, I hope we don't end up in the same trap where we're stuck on Python 3.11 until the next major OS update.

I haven't installed Bookworm yet, but if I do, are you saying this isn't currently working/updated in Raspbian?

Wasn't 100% sure what you meant. There are no pip packages for libcamera and kms++ currently. Camera applications and Picamera2 should work on Bookworm, though there are some fairly significant updates pending which will add/improve functionality.

Unfortunately, Bookworm is a complete mess.  The use of wayland was just a bad idea; it's STILL not ready.  That fact that there is only one VNC server that only half-a** works should be the flashing warning light.  I can't even use it, so much stuff is broken due to this that I need that I haven't even gotten to the point of trying the camera libs, not worth my time.  Folks, why are we forcing Wayland on the unsuspecting public like this?  The issues with it are still too large to brush under the rug. :cry:

ModuleNotFoundError: No module named 'libcamera' Has this problem been solved?

ModuleNotFoundError: No module named 'libcamera' Has this problem been solved?

It seems not, I'm trying to use picamera2 from a conda environment and seeing the same, currently trying to understand how to [expletive deleted] build libcamera at the minute.

See https://github.com/raspberrypi/picamera2/issues/503#issuecomment-1861034147


Add Mergel by @Snazzware

[ ] Project URL:
[ ] Update contents.json instead of README
[ ] One project per pull request
[ ] Avoid iOS or open-source in description as it is assumed
[ ] Use this commit title format if applicable: Add app-name by @github-username
[ ] Use approved format for your entry

thx!


⚠ Bofrost.at has degraded performance

In 48d4185, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1943 ms

Resolved: Bofrost.at performance has improved in 44b0852.


Add TravisCI

Deploy the docs to Github Pages automatically using TravisCI.

@44uk Thanks for your pull-requests, it works.
I don't close the issue yet as we should add Travis-CI to nem2-sdk-java and nem2-sdk-typescript-javascript to generate automatically the references and publish them in gh-pages.


Can't get builder shell?

I build buildspawn with default as in your repo and try to get builder shell with:
sudo machinectl shell builder@buildspawn
Connected to machine buildspawn. Press ^] three times within 1s to exit session.

Connection to machine buildspawn terminated.

Did you face the same problem? I can't get builder shell.

I can get shell of root user ok.

I haven't faced that... For me it works correctly:
$ sudo machinectl shell builder@buildspawn
Connected to machine buildspawn. Press ^] three times within 1s to exit session.
[builder@buildspawn ~]$

How about journalctl -u systemd-nspawn@buildspawn?

Output of journalctl -u systemd-nspawn@buildspawn: systemd-nspawn log

Thank you. It seems your log is same to that in #6 you provided, so I think they might be same problem.
I want to merge this issue to #6.
(But I don't have any solutions now as I said there...)


Successfully validated Offer not listed as as account offer

Hi All,
I understand this may not be the ideal place to post this issue. However, I didn't find a better place and the xpring forum doesn't have a valid TLS certificate.
I submitted an offer. It was validated and it shows as successful. Yet it never showed up in the order book and it never showed up in method: "account_offers" (JSON RPC). Here is the TX hash:
4718EB82091A2343BA62D57C411D703E858537868B3B641971994FE9B5264006
https://xrpcharts.ripple.com/#/transactions/4718EB82091A2343BA62D57C411D703E858537868B3B641971994FE9B5264006
suggests it was successful. I placed this order on ask, a few ticks below the best ask. My offer size was tiny, while the next level was huge. I don't believe I need to prove that the problem is reproducible -- based on the TX information it should be clear why it was never included in the orderbook. I just don't see it from what is provided by rippled.
Why is it not included in the orderbook?

That transaction was validated in ledger 59000273 and created an Offer node with LedgerIndex 3C50BE47A678593F09C69F89D1A62628FE39A7FA83A652D6DE91FE5C21DEDB73.
In that same ledger, there is a payment transaction that consumed the offer. You can see this if you expand AffectedNode with index 1 at https://xrpcharts.ripple.com/#/transactions/59BEC3684D799DEB7AF796E1C8A89919C0BDD98485221D1BD672CA292B8E7530
The account_tx command on a node with sufficient history will find this second transaction. You can also see the account history at https://livenet.xrpl.org/accounts/rrpJxQM16dqxHU75STd3Aonqp88RF1rWwf. Additionally, if you examine the balances, the XRP balance decreased, and the USD balance increased.
It's possible this is a coincidence, or there may be a bot watching offers and taking those it finds favorable. Either way, that's why you don't see the offer.
I'm going to close this issue, but if you have further questions please feel free to reopen it, or open a new issue.


Need to bump version of codemirror and codemirror-graphql to get rid of peerDependency warning spam

0.13 was supposed to resolve this, but it is still referencing an old version of codemirror and codemirror-graphql that have peers on old graphql version<EMAIL_ADDRESS>has a peer on the newer graphql version.
warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "codemirror-graphql ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^0.11.0 || ^0.12.0 || ^0.13.0".
warning "codemirror-graphql ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^0.11.0 || ^0.12.0 || ^0.13.0".
warning "codemirror-graphql > graphql-language-service-interface ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^0.12.0 || ^0.13.0".
warning "codemirror-graphql > graphql-language-service-interface ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^0.11.0 || ^0.12.0 || ^0.13.0".
warning "codemirror-graphql > graphql-language-service-interface ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^0.11.0 || ^0.12.0 || ^0.13.0".
warning "codemirror-graphql > graphql-language-service-interface > graphql-config ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^0.12.0 || ^0.13.0".

See related issue #773


Prepare for new release of Confluence

Workflow links: https://github.com/atlassian-labs/atlassian-slack-integration-server/actions/runs/10398739022

Integration tests pass, so current version of Confluence DC for Slack is marked compatible with Confluence 9.0.2


Fixed #24624 -- Replaced obsoleted rel.opts in admindocs view

Thanks Scott Sanders for the report. Refs #24381.

1.8 release note is missing. I'd write:
* Fixed a regression in the model detail view of :mod:``django.contrib.admindocs``   when a model as a ``ManyToOne`` relation (:ticket:``24624``).

I think you're missing a verb after "admindocs"

I don't understand the Refs #24381 in the commit message

I think that removal of ForeignObjectRel.opts has been committed in 24381, which was the cause of this regression (as suggested by the OP). Am I wrong?

Sorry, when a model as -> when a model has

You're right. I was looking for a larger patch.

Looks good, I made minor edits to your comment with the release note.


cloudflare_logpush_ownership_challenge doesn't work with Azure Storage Account

Confirmation

[X] My issue isn't already found on the issue tracker.
[X] I have replicated my issue using the latest version of the provider and it is still present.

Terraform and Cloudflare provider version
Terraform version: 1.0.8
cloudflare plugin version 3.6.0
2022-01-03T15:06:07.195Z [DEBUG] provider: starting plugin: path=.terraform/providers/registry.terraform.io/cloudflare/cloudflare/3.6.0/linux_amd64/terraform-provider-cloudflare_v3.6.0 args=[.terraform/providers/registry.terraform.io/cloudflare/cloudflare/3.6.0/linux_amd64/terraform-provider-cloudflare_v3.6.0]
Affected resource(s)
cloudflare_logpush_ownership_challenge
Terraform configuration files
resource "azurerm_storage_container" "cloudflare_logs_blob"{

  name                  = "cf-logs"
  storage_account_name  = "cfstaccount"
  container_access_type = "private"
}
data "azurerm_storage_account_blob_container_sas" "dev_sas" {

  connection_string = "primary_connection_string
  container_name    = azurerm_storage_container.cloudflare_logs_blob.name
  https_only        = true

  start  = "2021-12-29"
  expiry = "2026-12-30T23:59:59Z"

  permissions {
    read   = false
    add    = false
    create = false
    write  = true
    delete = false
    list   = false
  }
}

resource "cloudflare_logpush_ownership_challenge" "ownership_challenge" {
  zone_id = "xxx"
  destination_conf = "https://xxxxxxx.blob.core.windows.net/cf-logs?sv=2018-11-09&sr=c&st=2021-12-29&se=2026-12-30T23:59:59Z&sp=wl&spr=https&sig=???????"
}

Debug output
HTTP/2.0 200 OK
Cf-Cache-Status: DYNAMIC
Cf-Ray: 6c7d214b9e9482ae-IAD
Cf-Version:<PHONE_NUMBER>
Content-Type: application/json
Date: Mon, 03 Jan 2022 15:06:17 GMT
Expect-Ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
Server: cloudflare
Set-Cookie: __cflb=0H28vgHxwvgAQtjUGU56Rb8iNWZVUvXhcFcqgVnpX8H; SameSite=Lax; path=/; expires=Mon, 03-Jan-22 17:36:18 GMT; HttpOnly
Set-Cookie: __cfruid=671ea44111bfe734438f076b55a51796ec9c3972-1641222377; path=/; domain=.api.cloudflare.com; HttpOnly; Secure; SameSite=None
Vary: Accept-Encoding
X-Envoy-Upstream-Service-Time: 440
{
"errors": [],
"messages": [],
"result": {
"filename": "",
"message": "Invalid destination configuration: error writing object: error uploading to https: 405  UnsupportedHttpVerbThe resource doesn't support specified Http Verb. RequestId:3f7eac7b-d01e-000e-50b3-00d9a2000000 Time:2022-01-03T15:06:17.5278599Z",
"valid": false
},
"success": true
}
Panic output
No response
Expected output
Http 201 OK
Actual output
{"errors":[],"messages":[],"result":{"filename":"","message":"Invalid destination configuration: error writing object: error uploading to https: 405  UnsupportedHttpVerbThe resource doesn't support specified Http Verb. RequestId:ed11789e-a01e-0045-7fda-00e838000000 Time:2022-01-03T19:42:24.1506536Z","valid":false},"success":true}
Steps to reproduce
curl -v -s -XPOST https://api.cloudflare.com/client/v4/zones/<zone_id>/logpush/ownership -H "X-Auth-Email: " -H "X-Auth-Key: <API_KEY>" -H "Content-Type: application/json"  --data '{"destination_conf": "https://xxx.blob.core.windows.net/cf-logs?sp=w&st=2022-01-03T19:26:41Z&se=2028-01-04T03:26:41Z&spr=https&sv=2020-08-04&sr=c&sig="}'
Additional factoids
No response
References
No response

Azure Blob Storage doesn't support POST, this challenge file should be uploaded via Http PUT instead of POST
https://docs.microsoft.com/en-us/rest/api/storageservices/put-blob

destination conf should be start with azure:// instead of https


feat: added automerge action

Description
Adds the automerge action from https://github.com/pascalgn/automerge-action.

Closing because it's apparently no longer necessary because of https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request. I tried this, so maybe I have something misconfigured. Closing this for now.


S3 large responses

Following merged PR #107 but for TEST

@kburke this is the draft PR for later use when you think we are ready to move to TEST.


yRCA issue #3 fix

I proposed a new rule for yRCA to successfully identify the case when an instance of service SI doesn't wait enough time for an instance of SJ reply. This specific case has not taken in consideration and yRCA returns a "Found no failure..." which is not the correct explanation.

@teto1992 could you please check the PR, which - looks good to me and - should fix issue #3


Add a hierarchical structure to a suitable build configuration view

Currently the TeamCity extension shows suitable build configurations as a plain-list. It would be great to add a hierarchical structure to a suitable build configuration view which allow to hide build configs under projects and expand them.

The issue was closed by 431faa562f50d871179b904cadf01e064c306584

The issue was closed by 431faa562f50d871179b904cadf01e064c306584


Twitter-Bridge failed with error 0

Error message: Unexpected response from upstream. cUrl error: Failed to connect to twitter.com port 443: Connection timed out (28) PHP error:
Query string: action=display&bridge=Twitter&context=By+username&u=Linuzifer&norep=on&noretweet=on&format=Atom
Version: git.master.e14f647
Feed updated correctly for over 3 days. Config and server were not changed.

Might actually be related to the current akamai DNS problem. I will leave this open until conformation

Seems to be solved 🤷🏼♂


Create SDKRestClient wrapper class around RestHighLevelClient

Signed-off-by: Daniel Widdis<EMAIL_ADDRESS>Description
Creates a wrapper class translating the Client class method signatures to RestHighLevelClient methods.   Existing code making the various REST calls does not need to change (mostly) except for:

Imports may change
Occasional minor differences in response class parsing (e.g., List vs. Set, Iterables vs. Map entrySet, etc.)

Massively speeds the process of migrating existing plugins.
Notes:

Committed deprecated, so nobody should use it for new code.

Intentionally only partially implementing Client interface, to minimize the (deprecated) footprint to what is necessary
We can add new wrapper methods as we come across them

Cluster client is a placeholder, need to actually implement cluster-level features

Issues Resolved
Part of #353
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.

Codecov Report

Merging #367 (90fc2bf) into main (c62c90e) will increase coverage by 1.14%.
The diff coverage is 93.33%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff              @@
##               main     #367      +/-   ##
============================================
+ Coverage     69.35%   70.49%   +1.14%
  Complexity      126      126
============================================
  Files            27       27
  Lines           558      583      +25
  Branches         15       15
============================================
+ Hits            387      411      +24
- Misses          162      163       +1
  Partials          9        9

Impacted Files
Coverage Δ

src/main/java/org/opensearch/sdk/SDKClient.java
86.15% <93.33%> (+6.15%)
:arrow_up:

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


Logging events guide and details

🚀 Deployed on https://670033ae90696c950fa36dba--cozy-fox-0defec.netlify.app


Remove unused dblamt variable

The variable was used to check the transaction amount for a smart contract based on specific transaction amounts. The smart contract was never realized in this way. It was in the initial commit and not used thereafter.

I wanted to remove the unused ones as well. to eliminate most compile errors :)

I went through the errors and this is the only one I found where I can definitely say that it won't have a purpose in the future, since the smart contract is redundant now.

The dblFromAmount function is now unused so we can remove it. Yay.


Beehtoken is Back

Was hoping I could get access to the discord again? Thank you again for your time

You have been unbanned. Will remind you anyway that behaviour you had shown before on discord or ingame will get you banned from both again so lets play nice okay.


when use this command "cf bind-service rails-sample test-pubsub-01", get the message below.

using this version of the CLI: 6.6.0-704d304
and that this error occurred:

	runtime error: invalid memory address or nil pointer dereference

and this stack trace:

	goroutine 1 [running]:
main.generateBacktrace(0xc21000a000, 0x4)
	/home/ubuntu/go/src/github.com/cloudfoundry/cli/main/main.go:133 +0xa9
main.handlePanics()
	/home/ubuntu/go/src/github.com/cloudfoundry/cli/main/main.go:117 +0xfb
runtime.panic(0x8c38c0, 0x108f3a8)
	/usr/local/go/src/pkg/runtime/panic.c:248 +0x106
github.com/cloudfoundry/cli/cf/commands/service.(*BindService).Run(0xc210207780, 0xc2100668f0)
	/home/ubuntu/go/src/github.com/cloudfoundry/cli/tmp/cli_gopath/src/github.com/cloudfoundry/cli/cf/commands/service/bind_service.go:85 +0x8e7
github.com/cloudfoundry/cli/cf/command_runner.ConcreteRunner.RunCmdByName(0x7f9bbfd21468, 0xc210208d80, 0x7f9bbfd21498, 0xc210042100, 0x97d390, ...)
	/home/ubuntu/go/src/github.com/cloudfoundry/cli/tmp/cli_gopath/src/github.com/cloudfoundry/cli/cf/command_runner/runner.go:48 +0x3d0
github.com/cloudfoundry/cli/cf/command_runner.(*ConcreteRunner).RunCmdByName(0xc2103203e0, 0x97d390, 0xc, 0xc2100668f0, 0x4, ...)
	/home/ubuntu/go/src/github.com/cloudfoundry/cli/tmp/cli_gop

resolved via PR https://github.com/cloudfoundry/cli/pull/317


[ggj][infra][4/5]feat: add goldens update bazel rules for Asset API

Find more details in design doc: go/java-micro-integration-test-infra
Double checked with Asset API, the update_goldens bazel rules can be directly run from clean branch.
This will be hold until #396 is merged. Next step: update development.md

Updated goldens by bazel run //test/integration:api_update to pick up the changes in recent PRs.


Migrating toward a binary-free repo

Description of the issue:

GitHub is a versioning system for software and databases that stores mainly text files, because their modifications can be easily traced and controlled. Changes made to binary files are invisible so  they are generally avoided in git repositories.
In GEM-type repos, .mat files are the common format used in model reconstruction and simulation analysis and thus an inevitable component. However, .mat files are binary and immediately lead to conflicts if modified in different branches and merged together. Therefore, abandonment of .mat files had been proposed and implemented, such as in yeastGEM repo.
One major object of hosting GEMs as repositories is to provide public framework contributed by and serving for the research community through an open and transparent curation procedure. The .mat files contradict this purpose since commits applied to them are unable to track.

Expected feature/value/output:

This issue aims to develop an workable plan for migrating the repo into a binary-free mode.
It is certain that the migration will take some time.
At the moment, all changes to .mat file is restricted only to devel branch with coordinations between contributors.

I hereby confirm that I have:

[x] Checked that a similar issue does not exist already

This migration has been achieved with #156.


Allow proxy configuration

Related to a handful of user requests, librato-metrics should support proxy configuration of some sort.  Since there is not currently a configuration file, the intial feature might just be added to the API vs requiring a config.

Fixed in #112


Fix helper nix install

Maybe this is already on dev branch, so I apologise if it is the case.
Recently I have http 404 using helper install-nix.
This will fix the default values for version and file to fetch in this  nix-static inria repo, there is also a 2.21.0 version but the latest commit inserts 2.20.5 so that is what i used and tested.
Tested on grid5000 grenoble frontale.

Thanks Pedro for this PR, following a regression in version nix 2.21.1 (and perhaps 2.21.2), we cleaned to much nix-static repo which by consequence raised the 404 not found.  We are changing the nxc's code to remove  the need of nix version and take the last version from nix-static repo.


[WIP] Add missing cypress tests for initial Distributed Workloads views, fix minor architecture issues, factor out components for sections of the Workload Status tab

Part of https://issues.redhat.com/browse/RHOAIENG-3578. Additional unit tests should be added to complete that task.
Also sets up the structure to enable work to begin on https://issues.redhat.com/browse/RHOAIENG-2881 and https://issues.redhat.com/browse/RHOAIENG-3583.
Description

Followup to https://github.com/opendatahub-io/odh-dashboard/pull/2469. That PR only had tests to ensure the feature flag worked properly. This PR adds further Cypress tests for the global Distributed Workloads page to make sure navigation and project selection work as expected:

Automatic selection of a project if you visit the /distributedWorkloads root
Clicking tabs to navigate between them and make sure the routes and the page contents update correctly
Making sure the user-selected project is retained when navigating between tabs and is set as the "preferred project" (it is used if navigating back to the /distributedWorkloads root in the same session after choosing a project)
Making sure the "no projects" empty state appears properly

Running these tests revealed the following issues which are also fixed by this PR:

I forgot to call useSyncPreferredProject in the DistributedWorkloadsContext, so when the user selected a project in the dropdown it did not get persisted to state where that selection would be retained when navigating to other pages.
There was an accessibility error related to the tabContentId prop of the <Tab> elements in GlobalDistributedWorkloadsTabs referencing an element that does not exist on the page (it is used as an aria-controls HTML attribute, which must refer to an element that exists). This is because of how I structured the components with only one <TabContent> rendered at a time (for the active tab).

This a11y error wasn't caught before because none of the previous Cypress tests triggered the cy.testA11y() call which is now triggered by calling globalDistributedWorkloads.visit().
To resolve this, the TabContent for all tabs must exist at all times, but we still only want to render the contents of the active tab to support future lazy-loading. I refactored the JSX such that the DistributedWorkloadsToolbar, PageSection and TabContent previously rendered by each tab.ContentComponent are now lifted out and handled by GlobalDistributedWorkloadsTabs, with all but the active tab's TabContent set to hidden. The tab.ContentComponent is now limited to rendering children of TabContentBody, and is still only mounted for the active tab.

I also had to add new mock utilities for prometheus query results (mockPrometheusDWQuery and mockPrometheusDWQueryRange). Currently they just return empty data to get us past the spinner/error states on the page in the Cypress tests, but they will eventually return reasonable default data like mockPrometheusServing and mockPrometheusBias do.
This PR also moves each of the GlobalDistributedWorkloads*Tab components into its own folder (pages/distributedWorkloads/global/projectMetrics and pages/distributedWorkloads/global/workloadStatus), adds a Grid/Card layout for the workload status tab, and adds new components in the workloadStatus folder for each card. This will make it easier to start working in parallel on the separate cards.

As part of this change, instead of the GlobalDistributedWorkloadsWorkloadStatusTab component consuming context and handling error/loading states at that level, each of the new card components consumes context and renders its own errors/spinner.

How Has This Been Tested?

Wrote new Cypress tests, adjusted behavior to fix failing tests, and re-tested associated behavior manually in the browser.
Test Impact

N/A, this is a testing PR.
Request review criteria:

Self checklist (all need to be checked):

[x] The developer has manually tested the changes and verified that the changes work
[x] Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)

If you have UI changes:

[x] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change (find relevant UX in the SMEs section).

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

Marking WIP temporarily while I troubleshoot Cypress failures that are happening in CI but not locally. Going to revert the second commit for a sec to see if it was the rebase on main or some change in that commit.

Looks like I needed to specify the GET when intercepting the Projects API call now that we've rebased after https://github.com/opendatahub-io/odh-dashboard/pull/2583. Waiting for CI to verify.

CI is green again, good to go!

Rebased on main and addressed your comment @christianvogt


atlrug.com Website Ticket Ideas

atlrug.com Website Ticket Ideas
     -T4- Research/Fix mobile experience.
     -T6- Decide if Youtube test should be stubbed. (also related to -T15-)
     -T7- Add "https" support.
     -T8- Upgrade to Bootstrap 4.
     -T9- Add tests for unset environment variables.
     -T10- Fix JobsController and ResumesController "C"s from CodeClimate.
     -T11- Add Giveback group page to atlrug.com.
     -T12- Add a poll/survey capability.
     -T15- Restore Video-related cucumber specs in features/main_page.feature file (4/18/2016: Commented out).
     -T16- Convert the last erb file to haml.
     -T18- Issue #71: Embedded video does not work with Firefox when flash is not installed
     -T19- Upgrade repo to Ruby 2.4.0.
     -T20- Fix embedded video on "/video" web page. (#71)

If you like one of the above, create a GitHub issue for it and enjoy.
If you have other ideas, leave comments.
None of these ideas are required.
Active/DONE Tickets:
     -T1- Remove resume tab. (#60: DONE)
     -T2- Rename repo from atlrug4 to atlrug (probably after Rails 5 upgrade). (#69:DONE)
     -T3- Upgrade to Rails 5. (#61: DONE)
     -T5- Add job posting expiration strategy. (#62)
     -T13- Fix bullet (bullet on separate line) on "jobs" page under "Current jobs". (#67, #68)
     -T14- Indent job postings in under "Current jobs" on "jobs" page. (#66)
     -T17- Fix "Presentations" link web page's header - not formated as other pages. (5/7/2016: Fixed)

This might help with -T7-: https://everydayrails.com/2017/01/09/rails-https-only-lets-encrypt-ssl.html

These references might help with -T8-:

http://www.lugolabs.com/articles/153-using-bootstrap-4-with-ruby-on-rails

This might help with -T7-:

https://blog.heroku.com/announcing-automated-certificate-management

Spring Cleaning


Coulnd't start several clients

Azure Data Studio Version: 1.1.3
OS: Manjaro-i3

Steps to Reproduce:

Start Azure Data Studio

I've re-installed azure data studio several times and each time the issues disappears for a couple of days, then, it re-appears

@ThisDrunkDane I haven't seen this before, but there may be some useful info in the error logs.  @ranasaria do we have instruction for how to enable debug logging and capture the log files on Linux?

@ThisDrunkDane - Can you enable backend logging using this:
open up settings by pressing Ctrl+,
and then turn on this setting:
"mssql.tracingLevel": "All",
Ctrl-Shift-U -> Log (SqlTools) from the drop down selection will show you the logs and location of log files, but since this is a crash you would not have a chance to do that. Look for log files under mssql directory in your user folder to see if you can find them.


Choosing Bootstrap 3 framework still requires import of '@angular/material'

Issue type
I'm submitting a:
[x] Bug report
Prerequisites
Before posting, make sure you do the following:
[X] Confirm you are using the latest versions of all necessary packages (or if not, explain why not)
[x] Search GitHub for a similar issue or PR
Current behaviour
import { Bootstrap3FrameworkModule, JsonSchemaFormModule } from 'angular2-json-schema-form';

@NgModule({
 // ......
 imports: [
   // ...
    Bootstrap3FrameworkModule,
    JsonSchemaFormModule.forRoot(Bootstrap3FrameworkModule)
  ],

ng build eventually fails with:
Date: 2018-02-15T11:19:20.035Z
Hash: 14201b7e3fc4afd83b16
Time: 5943ms
chunk {inline} inline.bundle.js, inline.bundle.js.map (inline) 5.83 kB [entry] [rendered]
chunk {main} main.bundle.js, main.bundle.js.map (main) 303 bytes [initial] [rendered]
chunk {polyfills} polyfills.bundle.js, polyfills.bundle.js.map (polyfills) 323 bytes [initial] [rendered]
chunk {scripts} scripts.bundle.js, scripts.bundle.js.map (scripts) 1.67 MB [initial] [rendered]
chunk {styles} styles.bundle.js, styles.bundle.js.map (styles) 463 kB [initial] [rendered]

ERROR in node_modules/angular2-json-schema-form/src/framework-library/material-design-framework/material-design-framework.module.d.ts(2,39): error TS2307: Cannot find module '@angular/material'.

Expected behavior
Hard dependency on @angular/material should be removed.
Environment
macOS:               10.12.6
@angular/cli:     1.6.8
nodeJS:                9.5
angular2-json-schema-form: 0.7.0-alpha.1

I have exactly the same problem.

I am having the exact issue, as for my project we don't use or require Angular Material, only bootstrap4. It seems like this hard dependency was added on 0.7.0-alpha.1

Same problem in my case. Did anyone found a solution for it?

I have forked the project to catull/ngx-json-schema.
It comes without support of Material Design, and is upgraded to Angular 6.0.1.
It is on npmjs.com: ngx-json-schema.


NavigationBar has white borderBottom

Version
"react-native": "^0.22.0",
"react-native-router-flux": "aksonov/react-native-router-flux#dcc7558",

Expected behaviour
No white border between navigationBar and content
Actual behaviour
White border between navigationBar and content
Steps to reproduce

Make navigationBar backgroundColor red
Make content dark
Notice there is white border between navigationBar and content.

Temporarily fix
set navigationBarStyle to have borderBottomWidth: 0,

Use your fix to remove border, it is not a bug, but behaviour of built-in NavBar. You may pass your own NavBar if you want.


i can't save the tag

There is a problem with Your Own Klaviyo custom tag when setup information and adding trigger, I can't save the tag. please help me

To save you need to specify at least the Privat API Key and Event Name.

I Can't save also, any solution
On Thu, Sep 26, 2024 at 5:48 PM Alex Bub @.***> wrote:

To save you need to specify at least the Privat API Key and Event Name.
—
Reply to this email directly, view it on GitHub
https://github.com/stape-io/klaviyo-tag/issues/21#issuecomment-2377188841,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BLTZXRBAYVA7ALT35E6ZZELZYQNCTAVCNFSM6AAAAABO5F4WYSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZXGE4DQOBUGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Are you using the tag on a server-side GTM container?
Do you use the chrome browser to work with GTM?
This is definitely not a tag problem

no im not using tag on server-side Container
yes I'm using chrome browser
On Fri, Sep 27, 2024 at 10:03 AM Alex Bub @.***> wrote:

Are you using the tag on a server-side GTM container?
Do you use the chrome browser to work with GTM?
This is definitely not a tag problem
—
Reply to this email directly, view it on GitHub
https://github.com/stape-io/klaviyo-tag/issues/21#issuecomment-2378546256,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BLTZXRG54YUD43UFLSWYS2TZYT7N3AVCNFSM6AAAAABO5F4WYSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZYGU2DMMRVGY
.
You are receiving this because you authored the thread.Message ID:
@.***>


Sending ETH away from NAMI

Good Day,
I accidentally sent ETH to my NAMI wallet. I can see the ETH within the NAMI wallet. When I try to send the ETH away though, it is charging me a 99% fee. I have attempted to go through wanchain to export. Wanchain recognizes the ETH within the NAMI wallet as well, but when I try and send the ETH to the proper wallet I get a notification saying there is insufficient liquidity. I am hoping to have a resolution to this immediately, as these funds are for the holidays.

Please respond swiftly, this is quite urgent.

@OceanicGoon Sorry for the late reply kindly talk to the Cardano Live Support team about the issue you're facing

Deleted comment above is a scam

I appreciate the information about the scam comment. Please provide assistance on the mentioned. Thank you.

Nami,
As one of the largest and most trusted ADA wallets, I would imagine one of you can assist me promptly. I need these funds for my children's Christmas.

Please provide the transaction ID(s) and I'll take a look

Closing due to inactivity


(refactor): Project Refactor

an attempt to improve the project

Pull Request Test Coverage Report for Build 81

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 68:
0.0%

Covered Lines:
22

Relevant Lines:
22

💛  - Coveralls