Integrated code lifecycle:  Decouple build agent summary and details view

Checklist
General

[x] I tested all changes and their related features with all corresponding user types on a test server.
[x] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
[x] I chose a title conforming to the naming conventions for pull requests.

Server

[x] Important: I implemented the changes with a very good performance and prevented too many (unnecessary) database calls.
[x] I strictly followed the server coding and design guidelines.
[x] I added multiple integration tests (Spring) related to the features (with a high test coverage).
[x] I added pre-authorization annotations according to the guidelines and checked the course groups for all new REST Calls (security).
[x] I documented the Java code using JavaDoc style.

Client

[x] Important: I implemented the changes with a very good performance, prevented too many (unnecessary) REST calls and made sure the UI is responsive, even with large data.
[x] I strictly followed the client coding and design guidelines.
[x] Following the theming guidelines, I specified colors only in the theming variable files and checked that the changes look consistent in both the light and the dark theme.
[x] I added multiple integration tests (Jest) related to the features (with a high test coverage), while following the test guidelines.
[x] I added authorities to all new routes and checked the course groups for displaying navigation elements (links, buttons).
[x] I documented the TypeScript code using JSDoc style.
[x] I added multiple screenshots/screencasts of my UI changes.
[x] I translated all newly inserted strings into English and German.

Changes affecting Programming Exercises

[x] High priority: I tested all changes and their related features with all corresponding user types on a test server configured with the integrated lifecycle setup (LocalVC and LocalCI).

Motivation and Context

The current BuildAgentView is very cluttered and hardy navigable with lots of build agents and recent build jobs. This view should be decoupled to a BuildAgentSummaryView and BuildAgentDetailsView

Description

BuildAgentSummaryView: Offers a list of all build agents and their running build jobs.
BuildAgentDetailsView: Shows the running build jobs for a specific agent and it's recent build jobs.
Steps for Testing

Prerequisites:

1 Admin
1 Programming Exercise

Log in to Artemis
Navigate to System Administration > Build Agents
See that you can see all build agents and their running build jobs. Cancel a few.
Navigate to the BuildAgentDetailsView by clicking on the agent name. Check that you can see the running build jobs of this agent and the recent build jobs
Navigate to System Administration > Build Queue
Check that you can navigate to the BuildAgentDetailsView by clicking on the agent name of a running build job.

Testserver States

[!NOTE]
These badges show the state of the test servers.
Green = Currently available, Red = Currently locked

Review Progress

Performance Review

[x] I (as a reviewer) confirm that the client changes (in particular related to REST calls and UI responsiveness) are implemented with a very good performance
[x] I (as a reviewer) confirm that the server changes (in particular related to database calls) are implemented with a very good performance

Code Review

[x] Code Review 1
[x] Code Review 2

Manual Tests

[x] Test 1
[ ] Test 2

Test Coverage

Client

Class/File
Line Coverage
Confirmation (assert/expect)

build-agent-details.component.ts
95.55%
✅

build-agents.service.ts
90%
✅

navbar.component.ts
88.75%
✅

Server

Class/File
Line Coverage
Confirmation (assert/expect)

LocalCIQueueWebsocketService.java
100%
✅

AdminBuildJobQueueResource.java
100%
✅

AuditResource.java
100%
✅

LocalCIWebsocketMessagingService.java
93%
✅

Screenshots

Build Agent Summary

Build Agent Details

Build Queue with clickable agent name

Summary by CodeRabbit

New Features

Enhanced build agent management with separate components for summary and detailed views.
Added real-time updates for build agent status and job processing via websockets.
Introduced detailed build agent information accessible through new administrative endpoints.
Implemented hyperlinking in build queue display for direct access to detailed build agent information.

Bug Fixes

Improved error handling in build agent details retrieval.

Documentation

Updated German and English localization files to include terms for "summary" and "details."

Style

Added CSS for handling long text wrapping in build agent summaries.

Tests

Expanded integration and component tests to cover new functionalities and components related to build agent management.

Before we merge this PR, we need to make sure that finished builds are shown on an overview page using a paging mechanism

Fixed the coverage.
Server-tests are failing due to the missed classes criteria which is also failing in develop.
Client-tests are also failing on develop.


Feature request: Twister server version

How about to provide a server version of twister? I would install it on my own server and open for all under a special domain. Every user should be able to login with own user etc.

Please check https://github.com/Tschaul/twister-react

wow! very nice! Thanks!


Wizard not scrolling to top on next

Package
filament/filament
Package Version
v3.0.68
Laravel Version
v10.22.0
Livewire Version
v3.0.5
PHP Version
PHP 8.1.23
Problem description
The contest is a wizard used not in a modal.
If the content of a step is very long (window height) when you click on Next the page doesn't scroll to top.
This happens whenever I have to scroll the page to get to the Next button.
This behavior doesn't happen when clicking on the Previous button.
I use Firefox.
Expected behavior
The page should scroll to the top when clicking on Next.
Steps to reproduce
Create a wizard.
In the 1st step put a placeholder whose content is a long text.
In the 2nd step put various controls that make the content be higher that the view of the main container of the page.
Start the wizard.
Scroll to the Next button of the 1st step and click on it.
The 2nd step is not displayed starting from the top but midway, you have to scroll up to view the content from the beginning.
Reproduction repository
https://github.com/emmexx/filament-scroll-top/tree/master
Relevant log output
No response

Please read the entire bot comment above.
We need a full repository we can clone and use to reproduce the issue.

Sorry, I thought a simple file was enough.
I created a repository example:
https://github.com/emmexx/filament-scroll-top/blob/master/README.md
A moderator should change the repository link in this issue.
Sorry, 1st time creating a github repository, I hope I did everything right.
The relevat code is in app/Filament/Resources/TestResource/Pages/CreateTest.php
Instructions are on main branch, anyway I copy them here:
In the .env file change:
DB_CONNECTION=sqlite
DB_DATABASE=/path/to/db.sqlite

Access using user<EMAIL_ADDRESS>password abc123.
Click on resource Tests and create a new test.
Scroll to bottom of 1st step, check the 3 toggles and click on Next.
The 2nd step doesn't scroll to top.

Could you please test if this issue occurs on the latest versions of Filament and Livewire?

In my composer.lock file there's:
 "name": "livewire/livewire",
 "version": "v3.0.5"

"name": "filament/filament",
"version": "v3.0.68",

The scroll problem is still there.

As a workaround I used the code suggested here:
https://github.com/filamentphp/filament/discussions/9022#discussioncomment-7277132

@cheesegrits, might this be related of the final part you mentioned in https://github.com/filamentphp/filament/pull/9084?

@zepfietje I doubt it's directly related, but probably needs some baked in scrollInToView() code on next/prev actions.  I'll take a look over the weekend.

Safari only. Works in Chrome. We already have scrollIntoView()


chore: rework task ordering

sign before we push
push before we create-pyxis-image
push-rpms before we publish pyxis container

@scoheb while you're at it, could you also make sure apply-mapping is run early on? Related to https://issues.redhat.com/browse/RELEASE-1005 and https://issues.redhat.com/browse/RELEASE-1007
And regarding adding potentially redundant runAfter - I think @davidmogar demostrated in the past the the tekton rendering of the graph can get confused if you don't declare that, so I'm for declaring it even if redundant.

@scoheb while you're at it, could you also make sure apply-mapping is run early on? Related to https://issues.redhat.com/browse/RELEASE-1005 and https://issues.redhat.com/browse/RELEASE-1007
And regarding adding potentially redundant runAfter - I think @davidmogar demostrated in the past the the tekton rendering of the graph can get confused if you don't declare that (in the UI, not the actual run order), so I'm for declaring it even if redundant.

I added something to address this.

@scoheb while you're at it, could you also make sure apply-mapping is run early on? Related to https://issues.redhat.com/browse/RELEASE-1005 and https://issues.redhat.com/browse/RELEASE-1007
And regarding adding potentially redundant runAfter - I think @davidmogar demostrated in the past the the tekton rendering of the graph can get confused if you don't declare that (in the UI, not the actual run order), so I'm for declaring it even if redundant.

I added something to address this.

Thanks. Overall I think it's a mess and really hard to be sure everything is right - there might still be some other cases there apply-mappping is not run yet and should be. But I could confirm that at least the rh-sign-image and populate-release-notes-images tasks should now definitely run after apply-mapping.

sign before we push
push before we create-pyxis-image
push-rpms before we publish pyxis container

One comment here: It's actually publish-pyxis-repository and in most cases it will only be initially false before the first release of the product. We set the pyxis container image published=true always when creating it in create-pyxis-image. So if you wanted to create it with false initially, then push the rpms and only then set the container image published to true, we would need to make more changes.
Also, why do you want to sign before push? Is it really a concern that some image pushed to the repo might not get signed (if signing fails)? It won't be in the red hat catalog anyway, so shouldn't be an issue. But more importantly, are you sure RADAS / signing server will be fine with signing something that isn't there yet? Maybe yes, I'm just not sure.

Also, why do you want to sign before push? Is it really a concern that some image pushed to the repo might not get signed (if signing fails)? It won't be in the red hat catalog anyway, so shouldn't be an issue. But more importantly, are you sure RADAS / signing server will be fine with signing something that isn't there yet? Maybe yes, I'm just not sure.

my motivation here is that signing has typically been more flakey than push-snapshot...therefore I did not want to pollute quay unnecessarily.
RADAS does not need the image in the final location prior to signing.

my motivation here is that signing has typically been more flakey than push-snapshot...therefore I did not want to pollute quay unnecessarily.

OK, makes sense.

RADAS does not need the image in the final location prior to signing.

Good to know.


Clearer API Keys Source

I've managed to find all the required keys (or so I thought), however, even after finding all the necessary keys it seems that they are still wrong?
Check this action: https://github.com/spicetify/spicetify-docs/runs/5978167459?check_suite_focus=true
As such, I would recommend to add a clarification to which API keys to use and where to get them so that everyone can quickly and painlessly use this action.

Hey, sorry about that this Github Actions lacks a proper tutorial.
Algolia Crawler credentials are found here:
https://crawler.algolia.com/admin/user/settings/
crawler-user-id: ${{ secrets.CRAWLER_USER_ID }}
crawler-api-key: ${{ secrets.CRAWLER_API_KEY }}

Algolia credentials are found here:
https://www.algolia.com/account/api-keys/all
algolia-app-id: ${{ secrets.ALGOLIA_APP_ID }}
algolia-api-key: ${{ secrets.ALGOLIA_API_KEY }}

Working! But my action is still failing, can you give some help here?
https://github.com/spicetify/spicetify-docs/runs/6025064795?check_suite_focus=true

Github actions is a bit weird in the way it presents the error, the actual message is https://github.com/spicetify/spicetify-docs/actions/runs/2167598318
The given API key is missing some permissions: addObject seems like you did not used the right one.
You can copy the apiKey in the crawler you already have or create a new one that have
  'search','addObject','deleteObject','deleteIndex','settings','editSettings', 'listIndexes',

Okay, so update on this 😪 It seems that open source projects with Algolia do not have an API Key with these permissions nor do they have access to any admin API Key so I could create a new key that enables that... I will contact support on this.

Hey @afonsojramos, you can use the api key in your crawler config, which have the expected rights to run the GitHub action. You can find it at the bottom of the editor: https://crawler.algolia.com/admin/crawlers/21cd96e7-6b93-46d4-9d67-ca808f1c8750/configuration/edit

It seems that I crossed a hurdle indeed, thanks @shortcuts!
Afterwards, however, I got the error The given API key doesn't have access to the required indexes (crawler_*). But it was fixed by adding the crawler-name property. It was a bit counter intuitive that in this case index = crawler. But I will close this issue now, thanks!


Shorten import boilerplates by renaming leolib and its files

I can get some relatively cheap minification wins by renaming my personal library.

Change leolib to just lib
Remove the lib_ prepend from all of these files
Shorten some of the file names

Merged PR #2


Implement ExchangeType rules

In the IWS Offer, there is two fields which determine how an Offer can be published, shared or exchanged. the OfferType and the ExchangeType.
The OfferType determine who an Offer may be shared with, as open Offers can be shared with anyone but reserved or limited offers cannot.
The ExchangeType is primarily used for statistical purposes to ascertain how most Offers is shared. Here, the rules must be implemented for the 3 values present (AC, IW or COBE).
AC means that the Offer is exchanged during the Annual Conference in the second half of January. However, Offers may also be exchanged as something else, as the AC rules means that it can only be shared with a single Country and the deadline is always March 31st (actually, it is configurable). So the rule is, that an Offer can always be published as IW or COBE, but AC can only be used during the Annual Conference.
It requires an API update, to ensure that the ExchangeType flag is present when sharing an Offer.
See the Excel sheet for details: Offer Types_Exchange Types.xlsx

Since IAESTE has not been answering my communication about this feature, it is put on hold. If no communication has been received until the end of August, the task will be closed.

There has been no reaction from IAESTE on this matte, will close as invalid.


Don't spit out newlines when nothing to puts()!

Fixes #3777
The end of knife spurious newlines in output when nothing
needs to be displayed.

Looks like we had specs that tested this.

So someone went out of their way to write tests to confirm that incorrect newlines were present in the output. Heh. Okay.

Hi. I am an automated pull request bot named Curry. There are commits in this pull request whose authors are not yet authorized to contribute to Chef Software, Inc. projects or are using a non-GitHub verified email address. To become authorized to contribute, you will need to sign the Contributor License Agreement (CLA) as an individual or on behalf of your company. You can read more on Chef's blog.
GitHub Users Who Are Not Authorized To Contribute
The following GitHub users do not appear to have signed a CLA:

@veetow
@juliegund

Please sign the CLA here.

How do I avoid having all of those older commits show up in my PR? They're from a 'git pull --rebase upstream master'. GH seems to have figured out the single relevant commit in my push, so is it just UI clutter and harmless?

Uhm, hrm.  I dunno, but that doesn't look right.
So looks like this will fix it:
git rebase --onto 183f76a 54d3908~1

Hi. Your friendly Curry bot here. Just letting you know that all commit authors have become authorized to contribute. I have added the "Signed CLA" label to this issue so it can easily be found in the future.

@chef/client-core @chef/client-maintainers needs review

I think this is intentional behavior, so you can put empty lines in places. If you don't think there should be empty lines in a particular piece of command output, then we can debate that, but I don't think the behavior should be changed at the top level.

@danielsdeleo I think you misunderstand the code, or I misunderstand your comment. The code doesn't strip all newline-on-its-own from all knife output. It determines if there was ANY output to display, and if there was not, it displays nothing. Previously it would display a single newline and nothing else.

I'm saying that there is probably usage like ui.msg("") where the intended outcome is to produce an empty line.

Ew.
[@dev:~/src/chef] knife-newlines 2 ± grep 'ui.msg("")' lib/chef/knife/* 2> /dev/null
lib/chef/knife/client_bulk_delete.rb:        ui.msg("")
lib/chef/knife/client_bulk_delete.rb:        ui.msg("")
lib/chef/knife/configure.rb:          ui.msg("")
lib/chef/knife/configure.rb:          ui.msg("")
lib/chef/knife/configure.rb:          ui.msg("")
lib/chef/knife/configure.rb:          ui.msg("")
lib/chef/knife/node_bulk_delete.rb:        ui.msg("")
lib/chef/knife/node_bulk_delete.rb:        ui.msg("")
lib/chef/knife/role_bulk_delete.rb:        ui.msg("")
lib/chef/knife/role_bulk_delete.rb:        ui.msg("")
[@dev:~/src/chef] knife-newlines 2 ±

The latest commit fixes the ui.msg("") cases and tests pass.

FWmyvoiceIW, I disagree with the idea and maintain that ui.msg should never print a blank line when an empty object is passed in: The current behavior of ui.msg is a bug, no matter how many people may have made use of its broken side-effect blank line.
By definition of its side-effect blank line, ui.msg is not for more manual output control as you're suggesting. Using it as-is, as seen in the core plugins for ~4 years with spurious blank lines constructed by ui.msg(""), demonstrates the lack of control it offers.
Control is ui.msg("\n") that would now be required to print a blank line.

@jblaine First, I agree with you in the large.  Second, I'm sure it's getting frustrating to have to deal with so much review on what seems like such a simple change.  I'm sorry for that, our goal is to make improvements while providing people a stable platform to build on top of.

Using it as-is, as seen in the core plugins for ~4 years with spurious blank lines constructed by ui.msg(""), demonstrates the lack of control it offers.

I said it offers "more control" than the output method which puts the input through a formatter based on the user-supplied -F flag.  As you can see the code, it is currently just a thin wrapper around puts that handle SIGPIPE so it has semantics that are understood by ruby programmers.
Anyway, I'm not here to block this improvement, but was rather offering a suggestion to how we could avoid breaking existing plugin code.  If other reviewers are OK with the plugin breakage (probably minimal?), I won't object to this solution.

I'm sorry for exposing my frustration.  I see one technically right thing to do for the future of the code. If it means delaying this fix to to 13.0 in order to be nice, fair enough. That's just how I feel.
It turns out that people could be notified to fix their knife plugins today in prep for the future behavior. It appears that puts assumes a single \n in the input string is unwanted in addition to the one puts will spit out on its own. That is, since puts spits out its own newline, one could expect puts "\n" to print out two blank lines. It doesn't.
def msg(data)
  puts data
end
msg("") # old deprecated method to get a blank line
msg("\n") # new method to get a blank line

[@dev:~/src/chef/lib/chef/knife] knife-newlines ± ruby /tmp/test.rb

[@dev:~/src/chef/lib/chef/knife] knife-newlines ±

That's 2 blank lines, one due to puts appending a newline and another due to puts ignoring the explicitly passed in \n.

I'm :+1: on this for Chef 13.

yep :+1:  for 13  (:sigh:)

So we tried this in #5852 but it proved excessively hard; I think for right now we're going to close this and if we want to take another run at this in the Chef 15 cycle we can.
Sorry @jblaine that this did not get done.


Use without build systems?

Hello!
Say I'm using a simple Makefile or other very simple "manual" command to compile my code. What are the -I and -L I need?
Using
-I/usr/local/include/nlopt-f/GNU-9.3.0 -L/usr/local/lib -lnlopt-f -lnlopt -lm
compiles fine, but then when I try to run the resulting executable I get
./test: symbol lookup error: ./test: undefined symbol: nlopt_algorithm_from_string
I can run the executable file if I set LD_LIBRARY_PATH before execution, to include /usr/local/lib.
I installed with cmake/ninja. Is it possible to configure it easily to install the .a and .mod-s and so on in locations that are by default in the LD_LIBRARY_PATH and include path, or is it a problem with my  system (Ubuntu LTS)?
Thank you!

If you are using a simple Makefile, why not give fpm a try?

I looked briefly into it but it seemed a bit opaque (that is, I am too much of a brainlet to "get it"). I want to compile the same code on my machine with ifort, some other time I use the cray compiler on an ARM cluster, some of the code is MPI, some is openmp, some both. I didn't see how fpm chooses performance flags and so on. My project usually has 1-2 modules and 1 program, all Fortran, so not much of a "build".


Make city/state lockdown curfew available via sms

Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
Make city/state lockdown curfew available via SMS.
Describe alternatives you've considered
Make city/state lockdown curfew available via SMS... may be hardcoded instead of dynamically coded.
Additional context
Consider city/states with the most cases.

no more relevant.


terms shouldn't be translated

there are terms that should not be translated to avoid confussion when reading the docs

[ ] I have read freeCodeCamp's contribution guidelines.
[X] My pull request has a descriptive title (not a vague title like Update index.md)
[X] My pull request targets the master branch of freeCodeCamp.
[X] None of my changes are plagiarized from another source without proper attribution.
[X] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thanks!


As a user, I want my current page number in the task list not to be lost when I change pages

Description
When starting on a certain page in task editing, one often wants to edit the tasks on the same page one after the other. However, the position is not saved in the frontend store. That is why you always end up on the first page when you navigate to the list. The position should be stored separately in the frontend for each task list.
Tasks

Create a store for saving page positions
Store and load the position for process instances, tasks, group tasks, group tasks in work, processes

Note: In another epic we implement pagination and fulltext search in the backend. Therfore, it would be useful to store the page information in url parameters to prepare the tasklist for https://app.zenhub.com/workspaces/digiwf-621f70bf50ea1100120b7e93/issues/it-at-m/digiwf-project/375

@dominikhorn93 How much SP are left here?

40% is done I guess.

@StephanStrehlerCGI can you pick this up when implementing the pagination?


Where is the communitygame bot style or something?

Describe your problem here. If you are modding, please try testing your problem in a clean version of the engine instead, this ensures the problem is actually caused by the engine itself. Also, if you're using an older version of JSE, please try the latest action build in the Actions tab or the latest release build. The issue has probably been fixed since that version. Oh yeah, and also be sure to check the pinned 'JS Engine: Known Issues' issue, to double check if your issue hasn't already been found!
I remember like 1-2 months ago there was like a communitygames style bot where it doesn't get perfect accuracy but it still plays for you, was it removed? Because I didn't play js engine for so long and the only reason I play js engine is because of the communitygame bot. So will be kinda sad (if) it's removed.
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.


probe fails between secondary IPs of Loxi instances

Describe the bug
Loxi requires secondary IP to communicate with each other for probing and respond to the service requests from the client. Currently, there needs a manual intervention to get this going. ip route add <secondary ip> via <gateway>
every time we might need to maually intervene and amend the route table appropriately. otherwise service will fail to respond.
To Reproduce
Steps to reproduce the behavior:
Set up loxi master and backup instances.
Deploy kube-loxilb.
Deploy a simple service and expose it via Loxi.
Check the probing status, and service response time.
Expected behavior
we can try and avoid manual intervention on the Loxi set up as secondary ip changes dynamically when the failover happens.
Environment (please complete the following information):

OS: Talos Linux v1.6.6 for k8s cluster, loxi set up on ubuntu 22.04
Kernel Version: 6.5.0-1023-aws
LoxiLB Version: latest
Cloud Environment:  AWS
K8s Version 1.28.3

Did some further testing on it. As long as source/dest check is disabled, it seems to work fine. Please check AWS doc related to "Source/destination checking".

Even with source/dest check disabled, few issues were identified and fixed in latest image. Please double check !!

this is sorted. verified in the latest update. works as good as it can be.


partially initialized module 'ipyvolume' has no attribute '_version' (most likely due to a circular import)

I have no idea with this problem

Same Issue:
Used this conda call to create the environment on a WSL Ubuntu:
conda create --solver=libmamba -n rapids-23.12 -c rapidsai -c conda-forge -c nvidia  \     rapids=23.12 python=3.10 cuda-version=11.8 \     jupyterlab napari dask-cuda dask-image matplotlib scikit-image anaconda::notebook
then
pip install ipyvolume
import ipyvolume as ipv import numpy as np x, y, z, u, v, w = np.random.random((6, 1000))*2-1 ipv.quickquiver(x, y, z, u, v, w, size=5)
`---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
Cell In[10], line 1
----> 1 import ipyvolume as ipv
2 import numpy as np
3 x, y, z, u, v, w = np.random.random((6, 1000))*2-1
File ~/miniconda3/envs/rapids-23.12/lib/python3.10/site-packages/ipyvolume/init.py:8
6 from ipyvolume import datasets  # noqa: F401
7 from ipyvolume import embed  # noqa: F401
----> 8 from ipyvolume.widgets import *  # noqa: F401, F403
9 from ipyvolume.transferfunction import *  # noqa: F401, F403
10 from ipyvolume.pylab import *  # noqa: F401, F403
File ~/miniconda3/envs/rapids-23.12/lib/python3.10/site-packages/ipyvolume/widgets.py:30
22 from ipyvolume.traittypes import Image
23 from ipyvolume.serialize import (
24     array_cube_tile_serialization,
25     array_serialization,
(...)
28     texture_serialization,
29 )
---> 30 from ipyvolume.transferfunction import TransferFunction
31 from ipyvolume.utils import debounced, grid_slice, reduce_size
34 _last_figure = None
File ~/miniconda3/envs/rapids-23.12/lib/python3.10/site-packages/ipyvolume/transferfunction.py:19
17 N = 1024
18 x = np.linspace(0, 1, N, endpoint=True)
---> 19 semver_range_frontend = "~" + ipyvolume._version.version_js
22 @widgets.register
23 class TransferFunction(widgets.DOMWidget):
24     _model_name = Unicode('TransferFunctionModel').tag(sync=True)
AttributeError: partially initialized module 'ipyvolume' has no attribute '_version' (most likely due to a circular import)`

Unistalling other widgets such as plotly, k3d etc.
Restart the kernel.

Import then worked, unfortunately the docs examples still do no show any plots. @T0bC, did it work for you in the end?

@palec87

Unistalling other widgets such as plotly, k3d etc.
Restart the kernel.

Import then worked, unfortunately the docs examples still do no show any plots. @T0bC, did it work for you in the end?

I tried the same thing, but without success. I ended up using a different library. But I must admit that I'm still looking for a python library capable of displaying a 3D array of potentially 1000x1000x1000 voxels with alpha transparency. And the whole thing interactively in real time. I want to display a uCT dataset for segmentation processes without having to reduce the resolution. The software CTVox provided by the manufacturer seems to be able to do this, but unfortunately without pyhton integration.

There you might run into hardware limitation and GPU would help a lot. Here is python CT framework with GPU support
https://fast.eriksmistad.no/python-tutorial-mri-ct.html
Other, general use viewer to consider can be napari
https://napari.org/stable/
I wanted zero install demos for students, so that it runs in notebooks/colabs. k3d worked for me in the end, but it is quite resource intensive, especially crashing colab NBs.


Added default token section to readme

Closes #35

I set "root" as a master token for Vault, PR

Okay, cool. Will #36 be added today? If so, I'll just have this doc update reference the architecture that will be current after today instead.
Is my understanding correct that consul and nomad will have their master-tokens generated by vault when it has been integrated btw?


Can't zoom in touch screen with pinch

Zoom with pinch is impossible or not developed

At some point D3 fixed this and it now works


If a user is on the /~upload page and navigates there again, that should probably reset the page

This came out of #633.
I have two thoughts here:

Have some kind of callback mechanism where the router calls a function provided by the route when it is navigated to, even when it is the current route?

Doesn't this already exist?

A very simple workaround would be to unconditionally rerender the current route on navigation. This could be as simple as #680.

Thoughts?

I think we can go the unconditional route for now. If rauta ever becomes a standalone library, one might want to add an option to modify that behavior. But I think for us always rerendering is fine. That's indeed the expected behavior I think, as normal <a> links work like that, right?

I guess then I'm just gonna undraft #680. :smile:


Implement Material MenuBar

Description
This implements a prototype of MenuBar widgets that can both render a Material menu bar, and speak to a bundled plugin on the engine that will create and manage system generated menu bars on macOS, Windows, and Linux (a.k.a. PlatformMenuBar, submitted already).
This implementation of the MenuBar uses a MenuBarController to manager most of the communication between widgets that need to occur to implement the menu bar. The MenuBar uses a hierarchy of MenuBarItem widgets which extend MenuItem so that they are also useful for configuring a platform provided menu.
For the Material MenuBar, MenuBarItem widgets have an internal _MenuNode assigned by looking for a wrapping _MenuNodeWrapper, and then they register attributes with that node (things like the focus node associated with the button, and the menu builder function for the submenus). The MenuBarItems update their metadata with the MenuBarController when they are rebuilt so that it knows enough to be able to render the correct menu widgets in the overlay. Widgets don't exist unless they are currently visible, but the nodes always exist.
I've tried eliminating it, but there are some cases where dirtying the controller from the widget tree can affect things on the overlay, so those updates have to happen in a post frame callback.
Related Issues

https://github.com/flutter/flutter/issues/23600

Tests

Many tests for all of the MenuBar operations and configuration.

Design Doc

https://flutter.dev/go/cascading-menus

Looks like I started to implement the tests in menu_bar_theme_test.dart, but didn't actually finish. Don't let that hold up the review, but I'm going to write those and add them.

(There's a lot of unhappiness with the checks)

Closing in favor of https://github.com/flutter/flutter/pull/109179


Cables and pipes not interacting with IC2 or Forestry correctly

Using a clean build with industrialcraft-2-2.6.16-ex110, Mekanism-1.10.2-<IP_ADDRESS>.88, MekanismGenerators-1.10.2-<IP_ADDRESS>.88, MekanismTools-1.10.2-<IP_ADDRESS>.88 and forge 1.10.2-forge1.10.2-<IP_ADDRESS>7 on a flat world with defaults, I was unable to connect any form of universal cable to ic2 machines. Wires from ic2 connect and transfer energy fine between Mekanism machines and ic2 machines. Mekanism pipes also failed to connect to ic2 machines. When testing using the same set up but with forestry_1.10.2-<IP_ADDRESS> instead of ic2, the cables would connect, but could not transfer power from forestry generators to other machines while forestry machines could receive power from Mekanism power sources using the same cable. I did not check pipe compatibility with Forestry. As I understand it, previous issues similar to this had to do with a dependency on a 3rd party mod, is this related to that, or am I doing something wrong?

This is due to the way cables currently work- I'm awaiting the mods to support new power systems that utilize capabilities.

Thank you for taking the time to look at this.

It's 2017 and this is still an issue.
Mekanism-1.10.2-<IP_ADDRESS>1
industrialcraft-2-2.6.142-ex110

It's 2018 and this is still an issue.
Mekanism-1.12.2-<IP_ADDRESS>5
industrialcraft-2-2.8.76-ex112

Don't necropost.


Improve command-line options when running benchmarks on JDK8

Do not pass -XX:MaxPermSize when running on JDK8.
This is a retargeted PR for #228

LGTM


Update docs to point to previous examples.

@JuanCaicedo Closes #30

@nanek Looks great, thank you


Add React ESLint package

Why

As we might have different react templates: ReactJS, NextJS, Remix,... so we should have the shared ESLint configuration for React.
Add the React configuration to this repository as a package.

Who Benefits?
React developers

@carryall @malparty @olivierobert
There are some ESLint plugins that are used in react-templates:

I think the following plugins should be put into base ESLint configuration instead, as we can use it for all projects, not only react ones.
    'plugin:@typescript-eslint/recommended',
    'plugin:import/errors',
    'plugin:prettier/recommended',

What do you think?


[Add] The Junior Jobs Podcast

Site URL
https://podcasters.spotify.com/pod/show/junior-jobs/episodes/59--The-Problem-With-Changing-Careers-and-How-To-Overcome-It--Junior-Jobs-e2lnm9f
Description of the above provided site
The Junior Jobs Podcast is a weekly podcast about how junior developers can get their first job in tech, with Erik Andersen.
Category
Other
Sub Category
podcasts
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[ ] I am willing to work on this issue (optional)

I can take it since I am done with Syntax PR

I can take it since I am done with Syntax PR

sure


file name changed libbison-dev_3.0.4.dfsg-1_amd64.deb to libbison-dev_3.0.4.dfsg-1+b1_amd64.deb on remote server

Issue Description
! master                        # 245 errored                784730a
194 builds                     about 17 hours ago
The command "wget http://ftp.us.debian.org/debian/pool/main/b/bison/libbison-dev_3.0.4.dfsg-1_amd64.deb" failed and exited with 8 during . Your build has been stopped.
What problem / feature / issue are you raising? Describe in as much detail
as possible.
The name of the link to the deb file has changed on the remote server
from
http://ftp.us.debian.org/debian/pool/main/b/bison/libbison-dev_3.0.4.dfsg-1_amd64.deb
to
http://ftp.us.debian.org/debian/pool/main/b/bison/libbison-dev_3.0.4.dfsg-1+b1_amd64.deb
libbison-dev_3.0.4.dfsg-1+b1_amd64.deb             25-Feb-2017 02:59              433122
What should happen:
What should normal behaviour for the given input be?
in the travis file
https://github.com/ben-marshall/verilog-parser/blob/master/.travis.yml
Line 14 should be replaced with the correct name:
http://ftp.us.debian.org/debian/pool/main/b/bison/libbison-dev_3.0.4.dfsg-1+b1_amd64.deb

People to Notify:

@ben-marshall

Related Issues:

Owp, thank you for flagging this! I'll take a look now.

Fantastic work Ben, can you take a look at the verilog-dot issue as well please?
I cannot seem to get it to work and would like to do a fresh pull of it.

Not sure what is broken - seems like an issue with the name of the file on the remote server:
(Reading database ... 93765 files and directories currently installed.)
Preparing to unpack bison_3.0.4.dfsg-1_amd64.deb ...
Unpacking bison (2:3.0.4.dfsg-1) over (2:3.0.2.dfsg-2) ...
dpkg: dependency problems prevent configuration of bison:
 bison depends on libbison-dev (= 2:3.0.4.dfsg-1); however:
  Version of libbison-dev:amd64 on system is 2:3.0.4.dfsg-1+b1.
dpkg: error processing package bison (--install):
 dependency problems - leaving unconfigured
Processing triggers for man-db (<IP_ADDRESS>-1ubuntu1) ...
Errors were encountered while processing:
 bison
The command "sudo dpkg -i bison_3.0.4.dfsg-1_amd64.deb" failed and exited with 1 during .

Seems to be working now as the lights are green on Build Status

Excellent. Thanks!


[bindings] add direction to component yaml

Description
Add best practice direction metadata to component yaml files
Issue reference
PR will close: #886 and dapr/docs#3592
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[ ] The quickstart code compiles correctly
[ ] You've tested new builds of the quickstart if you changed quickstart code
[ ] You've updated the quickstart's README if necessary
[ ] If you have changed the steps for a quickstart be sure that you have updated the automated validation accordingly. All of our quickstarts have annotations that allow them to be executed automatically as code. For more information see mechanical-markdown. For user guide with examples see Examples.

Hi @hhunter-ms -- this caused a regression in Tutorials test actions.  Here's an example.https://github.com/dapr/quickstarts/actions/runs/5744430856
Could we please research a safer fix?


Invalid positions reported by diagnostics when file is not ascii-only

This is due to 3468d0286da05fb77970ca625e138229bcd656a0. and until https://github.com/HaxeFoundation/haxe/issues/5163 is implemented, we're gonna need to open each file and do these conversions.

Is that really practical? What happens when you try to open each file in FlixelCoverageTests, with Lime, OpenFL, Flixel, Nape and Hscript - I'd imagine that would take a while?


Build info

Hi, it would be good to have some up-to-date build info - I assume the project is no longer buildable under VS2015 for example (I also have build issues after the last VS2017 update, but that's most likely unrelated)

Hmm, it most likely requires VS 2017 because of the frameworks it targets. I will add a note.

Thanks!


[Identity] Separated the tests into internal and public

This PR separates the tests between public and internal, for the purposes of min-max testing.
Once approved,
Fixes #9448
With the goal of separating the tests between public and internal, I had to copy some type references from the source code to the tests, since otherwise they wouldn't be possible to be used as tests only working with the public shape of the API.
In that process, I removed _setDelayTestFunction and switched from using a custom implementation of the delay function to use the one implemented on @azure/core-http. To achieve this, I switched to use sinon for mocking. I'm adding sinon in another Identity PR, so I believe this change is appropriate.
I'm leaving this as a draft PR to get some feedback first, and to see if CI complains.

I think it's going to be annoying maintaining two copies of those interfaces, wouldn't it be better to import them directly from the files in which they're defined?

@daviwil

I think it's going to be annoying maintaining two copies of those interfaces, wouldn't it be better to import them directly from the files in which they're defined?

That defeats the purpose. The tests on the public folders should be easily extracted out of the project without having to know any of the paths of the internals of the project, so that the engineering team can do min-max testing and other stuff easily 😁 An alternative could be to export these interfaces as part of the public API of Identity 😅 If you have a better idea, please let me know.

This seems fine, though I don't know the min/max stuff well enough to say it's the right direction. You may want @KarishmaGhiya to also take a look.

This file separation looks good to me. I am wondering how do we run the min-max tests for identity, given that we don't have a live tests pipeline for identity. Ideally for all packages we can just enable using this variable - https://github.com/Azure/azure-sdk-for-js/blob/master/sdk/keyvault/keyvault-keys/tests.yml#L8

Do we want to run live tests for identity? If yes, then we can test this easily in a PR @sadasant

@KarishmaGhiya I will ask.

@KarishmaGhiya the answer we've got so far is that we do want live tests to happen. So, I will add this, as you suggested to me: https://github.com/Azure/azure-sdk-for-js/blob/master/sdk/keyvault/keyvault-keys/tests.yml#L8

@KarishmaGhiya on second inspection, I believe we should make a separate issue to provide live tests for identity, since we need to come up with an ARM template that would fit the tests. I also want to make some cleanup of the tests and samples next month. I made a new issue to track running Identity tests in our live pipelines: https://github.com/Azure/azure-sdk-for-js/issues/10963
cc: @ramya-rao-a the test cleanup of Identity can take me several days, so I added this test to the Backlog. We should coordinate this effort together.

We can merge this PR in. It looks good. But we will need to test in the future if min-max testing works and thus validate if this test separation is accurate. May be we can track that using either a separate issue or adding a TODO in the issue you created for the live test pipeline. Whatever makes more sense @sadasant


Added a note that discourages the use of service_account_file in favor of service_account_info

Using service_account_file can cause portability issue when using containers. service_account_info should be used instead.
Example
Screenshots
Checklist

[x ] References any related issue by including "Closes #" or "Closes ".

Closes https://github.com/PrefectHQ/prefect-gcp/issues/119

[ ] Includes tests or only affects documentation.
[x] Passes pre-commit checks.

Run pre-commit install && pre-commit run --all locally for formatting and linting.

[ ] Includes screenshots of documentation updates.

Run mkdocs serve view documentation locally.

[ ] Summarizes PR's changes in CHANGELOG.md

Thanks for your contribution! I'll be moving this into the landing page shortly.


Error using BUILDPACK_PRELAUNCH_METEOR workaround

I'm getting the following error when setting the BUILDPACK_PRELAUNCH_METEOR variable on heroku:
error: ios: platform is not in this project
error: android: platform is not in this project

Why is the remove-platform command required when using this option?

See #2 and https://github.com/AdmitHub/meteor-buildpack-horse/commit/648e2ed3a435c87f111e83a858a4f9f25e207357.
The error is not a failure -- e.g. it doesn't result in a non-zero return code, and the buildpack should proceed as expected.  We remove mobile build targets so that people who have added them to their projects can successfully build on heroku with BUILDPACK_PRELAUNCH_METEOR set.  If your build is failing, it is likely for a reason other than those printed errors.

I am also able to duplicate this. Adding the platforms in allows build and deploy. Taking them out causes build to crash directly below the error messages:

error: ios: platform is not in this project
error: android: platform is not in this project


Install tool for anaconda

Hi, I this module is great. I’d like to use this further for research but could you work on so that I could install histomicstk from anaconda?

@satotty To complement @manthey's response. Here's how you can do so:
1. Create conda environment.
conda create --name myenv

2. Install pip inside your conda environment and activate it:
conda install -n myenv pip
conda activate myenv

4. Instal HistomicsTK using pip:
pip install histomicstk

I tried creating the conda environment and pip installing histomicstk.
I am getting this error:
ERROR: Could not find a version that satisfies the requirement histomicstk (from versions: none)

Is it supported for a specific python version?


[ECH-625]: Add Gather token support

Linear ticket https://linear.app/unstoppable-domains/issue/ECH-625/new-currency-support-gather-gth
Storybook screenshot:

You can ask Daniil for an icon


Experiment: use getaddrinfo from the local_names_cb

This is an attempt to see whether "regular" DNS requests (i.e. those
for A and AAAA records) can be satisfied through the getaddrinfo
API rather than having to use the UDP/TCP forwarder.
Signed-off-by: David Scott<EMAIL_ADDRESS>

There's one user report that this strategy has fixed the DNS problem: https://github.com/docker/for-mac/issues/1397#issuecomment-285919564


Cmdlet outputs "Status", but output object actually has "State" property

As the examples on this page show, Get-IISAppPool outputs a table that contains a Status property. However that property does not exist on the Microsoft.Web.Administration.ApplicationPool object returned by the cmdlet:
> Get-IISAppPool "DefaultAppPool" |select -expandproperty Status
Select-Object: Property "Status" cannot be found.

Looking at the reference for Microsoft.Web.Administration.ApplicationPool, we see that it has a State property, and indeed using that works:
> Get-IISAppPool "DefaultAppPool" |select -expandproperty State
Started

Why the discrepancy?

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

ID: eea2e289-d548-6a5c-76c1-ba5492b10144
Version Independent ID: bb663769-9975-8a51-096f-7af01034f583
Content: Get-IISAppPool (iisadministration)
Content Source: docset/windows/iisadministration/Get-IISAppPool.md
Product: w10
Technology: powershell-windows
GitHub Login: @andreabarr
Microsoft Alias: v-anbarr

@IanKemp Hello Ian,
Thank you for your feedback.
Format-Table cmdlet does not always return actual property names as table headers. There are default formats  for a lot of types described in *.format.ps1xml and *.types.ps1xml files. You could find this one here:
iiscommands.format.ps1xml
You will see that Status is mapped to State
There is a copy of this file in your WinSxS folder.
Let me know if you have any questions.

The issue is being closed as it seems to have been answered. Thank you for the feedback.


v1.3 Endgame

End game Lead: @pkedy
End game buddy: @berndverst
This is the schedule for the v1.3 release
July 15th to July 20th

[ ] Ensure the docs are clear about using the correct CLI, runtime and SDK versions (1.3.0 for CLI/Runtime) (@AaronCrawfis)
[x] No P0 issues before code freeze.
[x] Code freeze at 11:59 pm 07/14.
[ ] E2E and perf tests are passing. (Known perf test failures, deemed not a blocker. Known E2E failure not a blocker). (@halspang) THEY ARE CURRENTLY BROKEN AND WE ARE INVESTIGATING
[x] Cut release-1.3 branch for component-contrib (@pkedy / @artursouza)
[x] Create 1.3.0-rc.1 release for component-contrib (@pkedy / @artursouza) (IN THIS RELEASE WAS 1.3.0-rc1)
[x] Update dapr/component-contrib pkg to 1.3.0-rc.1 in dapr/dapr master branch (@pkedy / @artursouza) (IN THIS RELEASE WAS 1.3.0-rc1)
[x] Cut release-1.3 branch for Dapr runtime (@artursouza)
[x] Update helm chart versions (@pkedy)
[x] Create release-1.3 branch for CLI (@mukundansundar)
[ ] Cut the 1.3.0-rc.1 release for Dapr runtime  (@yaron2 @artursouza)
[ ] ~Update dapr/dapr pkg to 1.3.0-rc.1 in dapr/cli master branch (@mukundansundar)~
[ ] Cut the 1.3.0-rc.1 release for CLI (@artursouza @halspang)
[ ] Validate the upgrade path from the previous release -- CRDs updated, no deletion of components/configs etc. (@halspang)
[ ] Update proto and cut the rc release for Java SDK (@artursouza / @halspang)
[ ] Update proto and cut the rc release for Python SDK (@wcs1only)
[ ] Update proto and cut the preview/rc release for .Net SDK (@rynowak )
[ ] Send dapr runtime/cli to vscode dev containers team (Phil Hoff, @mukundansundar / @greenie-msft )
[ ] Update longhaul tests dotnet SDK version (@wcs1only)
[ ] Update longhaul tests Dapr runtime version (@wcs1only)
[ ] Test and validate quickstarts in Darwin (@halspang)
[ ] Update quickstart automated validation and check it works - covers Linux Standalone/ K8s / Darwin MacOS (@wcs1only)
[ ] Validate middleware quickstart in K8s (@yaron2)
[ ] Test and validate quickstarts in Linux ARM64 k8s and self-hosted (@wcs1only) (kafka docker-compose does not work for bindings)
[ ] Test and validate quickstarts in Windows (@wcs1only)
[ ] ~Update proto and cut the rc release for cpp-sdk (@wcs1only)~
[ ] ~Update proto and cut the rc release for js-sdk (@pkedy)~
[ ] ~Update proto and cut the rc release for rust-sdk (@pkedy)~
[ ] ~Release and test azure-function-extensions (@vinayada1  )~
[ ] Validate Longhaul metrics (@wcs1only)
[ ] Test and validate the .NET SDK - run through samples (@rynowak  )
[ ] Test and validate the .Java SDK  - run through integration tests and samples (@artursouza, @halspang)
[ ] Test and validate the python SDK release - run through samples (@wcs1only)
[ ] Test and validate the Go SDK release  - run through samples (@yaron2)
[ ] Create release notes - CLI, Dapr, .NET SDK, Java SDK, Python SDK, Go SDK. Check them in release branch before cutting the RC release. (@halspang / @berndverst)
[ ] Edit and complete release-notes on HackMD (everyone)

July 21th

[ ] Verify no breaking changes section in release notes (@halspang / @berndverst)
[ ] Merge release notes into release branch (@artursouza)
[ ] Update helm chart to 1.3.0 and release runtime (@pkedy) - Make sure this uses Go 1.16.6 due to CVE. Details
[ ] ~Release cpp-sdk (@wcs1only)~
[ ] ~Release js-sdk (@pkedy)~
[ ] ~Release rust-sdk (@pkedy)~
[ ] Release Go SDK and docs (@yaron2)
[ ] Release Java SDK and docs (@artursouza / @halspang)
[ ] Release PHP SDK and docs (@withinboredom)
[ ] Release dotnet SDK and release nuget packages (@rynowak )
[ ] Release python SDK (@wcs1only)
[ ] Release CLI 1.3 (@yaron2 @mukundansundar )
[ ] Create new release for 1.3 branch for docs in the repos (@orizohar, @AaronCrawfis)
[ ] Make v1.3 the primary docs website - meaning change the default branch (@AaronCrawfis)
[ ] Create release-1.3 branch for quickstarts, update version tag in the images, create v1.3.0 tag and update the readme in master (@wcs1only)
[ ] Make sure the release notes are copied into the GitHub release description at https://github.com/dapr/dapr/releases (@AaronCrawfis)
[ ] Generate new Java docs based on the release version of the Java SDK (@artursouza / @halspang)
[ ] Update supported versions table in docs (@msfussell )
[ ] Merge (NOT SQUASH MERGE/AUTO MERGE) back release-1.3 branch into master for required repos (@yaron2 @artursouza)
[ ] Celebrate 🎈

RELEASE NOTE: NOT APPLICABLE

Consider bumping dashboard helm chart version and release tag to 0.7.1 so these match again.

Oh, it is an epic task! Thanks for all of you, and I would like to participate in if possible.

Tracking docs release tasks here https://github.com/dapr/docs/issues/1652


Game update broke plugin

Latest game update 20220209 broke the plugin.
Clicking Presets does not highlight fragments or auto scroll.
Shift click does still work.
Jagex added new Unequip all button.

Duplicate of issue 14:
https://github.com/SyntaxBlitz/osrs-shattered-relics-fragment-presets/issues/14


Trace Log for Realm Operations

Goals

I want to be able to log/trace Realm operations during the debugging phase of my app.
Because of the lazy nature of Realm queries, you never know if a particular operation is loading from disk or has already been loaded in memory.
This way I can get visibility into I/Os from happening when loading the first item of a collection and when read I/Os occur when iterating through a Results collection.
We want to avoid the UI from slowing down (e.g. scrolling through a table view) if going through Results.
I don't see anywhere in the API where this can be enabled - I only see it for Object Server (which I don't use).
Expected Results

Actual Results

Steps to Reproduce

Code Sample

Version of Realm and Tooling

Realm framework version: ?
Realm Object Server version: ?
Xcode version: ?
iOS/OSX version: ?
Dependency manager + version: ?

There is no api for that. Personally I don't think tracing could be useful in this case and I'd recommend to use profiling tools instead to determine any bottlenecks in your app.
Also I think this article can be useful for understanding how realm queries work internally.

Thanks for using Realm; If you have any further questions feel free to file new tickets.


Implementation for simple categories trees for supply items

Thanks, tests are all passing, will try on the test server now.


decommission logging mongo metrics

all but the "ping" data with the server details and activity

it's an ongoing process....


[BUTTON IDEA]: Animated gradient button

1. Name of button: Animated gradient button
2. Description: The gradient animates by itself
3. Button Type (Animated, Special, etc...): Animated, Gradient
4. Will you work on it?: Yes

@shahednasser , can you add hacktoberfest label, please?

@IraTeixeira we already have a button idea for this.

@shahednasser the idea of my button is like on this GIF. It animates without hover. Do you have this idea already? Because i didn't find

We have a gradient button idea to be implemented.


Worse accuracy for MobileNetV3

I reimplemented FReLU in PyTorch, and apply it on MobileNetV3 by replacing all the hswish with frelu. The ImageNet accuracy is as follow:

model
top1

mobilenetv3+hswish
75.2%

mobilenetv3+frelu
74.8%

My code:
class FReLU(nn.Module):
    def __init__(self, in_channels, inplace: bool = False):
        super(FReLU, self).__init__()
        self.inplace = inplace
        self.conv_frelu = nn.Conv2d(in_channels, in_channels, 3, 1, 1, groups=in_channels, bias=False)
        self.bn_frelu = nn.BatchNorm2d(in_channels)

    def forward(self, x):
        x1 = self.conv_frelu(x)
        x1 = self.bn_frelu(x1)
        x = torch.max(x, x1)
        return x

Am I missing something important? As for the gaussian initialization in FReLU, what's the std?

We use gaussian initialization with std=0.01. I simply replace relu with frelu and it shows a slight improvement (0.1~0.3). We note that MobileNetV3 is a NAS-searched optimal CNN architecture, once you change the architecture (frelu has an additional dw-conv), you might need to search again on this new architecture to achieve the optimal result.

Thanks for your quick reply. I'll try your suggestions.


Bleibt bei Installation auf IOS14 am Punkt Benachrichtigen hängen.

Avoid duplicates

[ ] Bug is not mentioned in the FAQ
[ ] Bug is not already reported in another issue

Describe the bug

Expected behaviour

Steps to reproduce the issue

Technical details

iOS Version:
Device:

Possible Fix

Additional context

https://www.coronawarn.app/en/faq/#ios14


Remove the lifetime from Ui

This is a very simple change which will lead to significant (possibly a massive amount, in fact) of breaking changes. I'll add to this PR some approaches around this to explain my reasoning.
What was changed in Ui
All this change does is convert Ui<'a> to Ui, a ZST with one zero sized field UnsafeCell<()>. We never use this unsafe cell, and it is optimized out (ie, size_of Ui is 0), but we need it to prevent the compiler to implement Sync for Ui (it does implement Send, but that won't matter for us, as seen further down).
Ui previously held three fields: a reference to the imgui-rs Context which wasn't used, a shared font holder reference, possibly, and, lastly, a vec for our scratch sheet for the im_str changes.
The imgui-rs Context reference was used in a few stack tokens which have since been rewritten to not require it, so this reference could be trivially removed.
The shared buffer was replaced with a toasty static mut, which we only allow &Ui to access. Since we make sure that Ui is not Sync, two threads cannot access this at the same time, and we can safely mutate through it.
The font handler has not been well handled -- right now, we simply assert that we CAN borrow the font before accessing the context, and if we can, we borrow it, and only now hand users the raw pointer wrapper to their font systems. I do not think that this was a well used feature, and I think that a combination of global variables can resurrect this usage. I would like to keep the Ui object as a ZST, mostly for simplicity, but this might force us to add some data to it.
So with all of those changes, Ui doesn't actually NEED any fields.
Understanding the lifetime of Ui
Ui was previously defined like Ui<'a>(&'a Context). This gave it the semantics of a &T, but since we never implemented Copy/Clone for Ui, it had semantics more similar to &mut T.
Most of the methods on Ui (and most user code which passes it around through routines), will take an &'ui Ui<'ui>. This is a strange lifetime and is slightly incorrect. In reality, its lifetime is &'a Ui<'b> where 'b: 'a, since any reference ('a) definition has a shorter lifetime than the lifetime of the thing it's pointing to (assuming Rustc is doing its job). However, in practice, this doesn't particularly matter, so flattening them to the same lifetime is fine. It would prevent returning data in certain methods correctly, but we never did that anyway. One place where that lifetime, however, would get problematic would be the introduction of mutability. This PR fundamentally is paving the way for a larger PR that I am working towards to add mutability (and its various constructs) into imgui-rs.
Okay, but wait, didn't we need that lifetime?
Yes, and also no. We get all the effect of the lifetime by...never giving out Ui. Now, frame (I also added new_frame since frame was just a needlessly strange name) returns an &mut Ui. There is, as a result, only this single lifetime that we need to worry about.
Since Ui is a ZST, it can just be made out of the void. We need the lifetime though, so we store it as a field on Context, so we're locking context for the duration of Ui's existence.
This just works. I suspect most users won't notice this lifetime change directly, but will notice it in their parameters, which will need to have the lifetime removed.
This does have on impact -- because we lose the ability to drop Ui in user land code, render has been moved from Ui to Context. Via NLL, this prevents Ui from being used after .render (since .render takes an &mut self). However, it does mean additionally that we run an increased risk of, in certain cases, forgetting to end the frame, trigger some dear imgui asserts. I've bandaged around this by conditionally running end_frame in the Context's drop code, but in certain cases (ie, if you just forget to call .render in your main loop), we'll still end up getting an ImGui drop.

Oh, also, "it does implement Send" is this true? If it is this code is unsound. I though UnsafeCell was !Send by default too, though.

Hm, seems so. This isn't sound because the existence of &Ui on a thread isn't strong enough to prove that there's been sufficient synchronization of the writes behind BUFFER.

There's really no reason it has to be a ZST. I do think the compiler can do some fun magic to erase the reference but that's mostly me having fun.
How do you think the current code breaks its guarantees? Since I'm not trying to correctly synchronize, just prevent, multithreading, I thought this would be sufficient

Hmm I'm not aware of the backstory behind Ui's lifetime or the benefits of it's removal, but moving towards ui: &mut Ui sounds like a good plan

Via NLL, this prevents Ui from being used after .render (since .render takes an &mut self). However, it does mean additionally that we run an increased risk of, in certain cases, forgetting to end the frame, trigger some dear imgui asserts

If I understand right, This seems a bit of a step backward, as ignoring the underlying implementation, the old structure of:
let context = imgui::Context::new();
let ui = context.new_frame();
ui.button("...");
let draw_data = ui.render();

made a lot of sense to me - it makes it clear the draw data was tied to the stuff I did with ui - and once Ui::render(self, ... is called I couldn't reasonably expect something like this would work:
let context = imgui::Context::new();
let ui = context.new_frame();
ui.button("...");
let draw_data = ui.render();

// Nonsense:
ui.button("oh no wait please add this button too");
let data = ui.render(); // Wont compile, Ui was moved (.. I think?)

If I understand correctly, the above now looks like:
let context = imgui::Context::new();
let ui = context.new_frame();
ui.button("...");
let draw_data = context.render();

// The above sort-of implies I can still use `ui`
ui.button("!");
let draw_data = context.render(); // Get data but with an additional button, or.. something

nice, good question at @dbr. I was worried about that too, BUT since new_frame takes &mut self in the context...
let context = imgui::Context::new();
let ui = context.new_frame();
ui.button("...");
let draw_data = context.render();

ui.button("!");

this will not compile. Instead we get an error on context.render informing us that we still have an &mut Context borrow because of the &mut Ui we still have active.
If we start a new frame after context.render (and thus refresh our borrow of &mut Ui to have a new lifetime), then not only is that code LEGAL, but it's also actually completely correct. That's just doing two frames of imgui manually.
The lifetime of the data in render actually was the Context the whole time -- it returned an &'ui DrawData, relating it to the Context originally. That was important then just like it is now, since you (in this new system) cannot do this either:
let context = imgui::Context::new();
let ui = context.new_frame();
ui.button("...");
let draw_data = context.render();

let ui = context.new_frame(); // error here -- we still have a borrow of `draw_data` that's used later, so we can't take `&mut Context`
my_renderer.render(draw_data);
ui.button("!");

So in total, we do not lose our lifetime backing of Ui. I agree that that is extremely important


New package: GGDUtils v1.0.4

Registering package: GGDUtils
Repository: https://github.com/ProjectTorreyPines/GGDUtils.jl
Created by: @anchal-physics
Version: v1.0.4
Commit: 8ebab24c6878786d759a92438a6475da6f923eb9
Reviewed by: @anchal-physics
Reference: https://github.com/ProjectTorreyPines/GGDUtils.jl/issues/73
Description: Package holding utilities for Generalized Grid Description (GGD) objects in IMAS datastructure. Primary goals are interpolation and core profile extrapolation.

Please ignore this pull request. We have already changed the name of our package and new pull request has been sent to https://github.com/JuliaRegistries/General/pull/116353.


feat(legacy): added directive for activation expandable feature in textarea

When there are a lot of expandable textareas, they take up a lot of space. This code allows to save space on the screen and use expandable feature.
If the textarea is in focus, then expandable feature is activated, else textarea has default height.

That's an interesting idea, however I would like to not expand public API, this can already be achieved with same amount of lines:
<tui-textarea #textarea [expandable]="textarea.focused">

Maybe you can just add such example to the docs?

That's an interesting idea, however I would like to not expand public API, this can already be achieved with same amount of lines:
<tui-textarea #textarea [expandable]="textarea.focused">

Maybe you can just add such example to the docs?

Ok, commit reverted and added information into docs 👍. I use this feature in my project now like in example below above  🙃
The idea of my modification is that it is possible to expand the allowed values of TuiTextareaExpandableTrigger and leave this concern inside the library


ng update error message: Cannot find module 'tslint'.

🐞 Bug report
Command (mark with an x)

- [ ] new
- [ ] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [x] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Is this a regression?
Description
It seems like some part of angular-cli uses tslint to perform some migration step from Angular 7 to Angular 8.
When running npm update @angular/cli @angular/core @angular/material, the procedure crashes after static query migration is performed.
After installing tslint, it does not crash anymore, but our environment does not make use of tslint and it doesn't seem to be a dependency of angular-cli either.
🔬 Minimal Reproduction

Have an Angular 7 project without tslint
Run ng update @angular/cli @angular/core @angular/material

🔥 Exception or Error
Cannot find module 'tslint'
🌍 Your Environment

     _                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/

Angular CLI: 7.3.9
Node: 10.14.2
OS: win32 x64
Angular: 7.2.15
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.13.9
@angular-devkit/build-angular     0.13.9
@angular-devkit/build-optimizer   0.13.9
@angular-devkit/build-webpack     0.13.9
@angular-devkit/core              7.3.9
@angular-devkit/schematics        7.3.9
@angular/cdk                      7.3.7
@angular/cli                      7.3.9
@angular/material                 7.3.7
@ngtools/webpack                  7.3.9
@schematics/angular               7.3.9
@schematics/update                0.13.9
rxjs                              6.5.2
typescript                        3.2.4
webpack                           4.29.0

Anything else relevant?

Problem here is that the @angular-devkit/schematics package uses tslint to provide the TslintFix schematic task. Ideally it would specify tslint as a dependency as it is directly used.
https://github.com/angular/angular-cli/blob/3afdab21a0f0307dcd2be1b44a868ea3d7a8938c/packages/angular_devkit/schematics/tasks/tslint-fix/executor.ts#L13-L15
Migrations such as these from @angular/material can depend on these to apply fixes.

The problem is https://github.com/angular/angular-cli/blob/3afdab21a0f0307dcd2be1b44a868ea3d7a8938c/packages/angular_devkit/schematics/tasks/tslint-fix/executor.ts#L96 😛
As the above mentioned part only imports for types

ups right :smile: In any way, the TslintFix task has a dependency on tslint.

Hi, we discussed this in yesterdays team meeting, and the outcome is that we should print a warning when tslint is not found.
It was also brought up that using tslint for migrations is not the should be discouraged because tslint runs on files which are on disk and not using the schematic host, meaning that it might run on files which have changes not yet committed to disk or if the part of the schematic fails users will need to rollback the changes manually.

It seems like this was fixed in #16433. Please re-open if you are still seeing this issue on any migrations.

@dgp1130 Thanks for looking. This is still an issue as tslint is transitively used by TslintFixTask, but tslint is not a dependency of @angular-devkit/schematics.
https://github.com/angular/angular-cli/blob/master/packages/angular_devkit/schematics/tasks/tslint-fix/executor.ts#L86.
As @alan-agius4 pointed out, it might be best to just provide a good error in those cases? It seems not like a good idea to add tslint as actual dependency of @angular-devkit/schematics. The PR you linked to is actually a workaround we provided on the Angular Components side. The root cause is not fixed (or improved by better messaging).
I could re-open the issue, but I'm leaving that to you. I could imagine this being reworked in the future. Ideally the tslint task would be specific to the Angular CLI and not to the schematics devkit unless I miss something here.

Thanks for the clarification @devversion. Seems like this can still happen then, so I'm reopening the issue. We'll need to address that usage or add better warnings for this case.

Closing this that tslint executor is deprecated and will be removed in the future.


MatrixMultiplication Divide and Conquer

Description
I can write clean and optimize code for
MatrixMultiplication Using Divide and conquer
Will provide links to Questions related to Matrix Chain Multiplication.
@miraj0507  will you please assign this issue to me ?
I am GSSoC 2022 Participant.
Domain
Algorithm
Type of Contribution
Addition
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of LearnCPP.

/assign


failed to install

no such directory 'static'

Coverage remained the same at 69.535% when pulling 283ddcb27c0bc22de85c9cf9ceb7beab76a8b146 on joriewong:patch-1 into 9af34ba51cdb23a2970e968d0cbdee82778c6799 on apache:master.

Are you installing on windows?

centos

The there's something wrong with your installation as the path should be there.

Yeah that's better than going through the symlink, merging.

Broke the pypi build


PowerToys Run crashes

Microsoft PowerToys version
0.75.1
Installation method
GitHub
Running as admin
Yes
Area(s) with issue?
PowerToys Run
Steps to reproduce
When using PowerToys Run to run the administrator permission program, if you cancel the run when the UAC interface pops up PowerToys Run will crash
reproduce:

*UAC interface cannot record
log file:
PowerToysReport_2023-11-22-17-58-21.zip
✔ Expected Behavior
PowerToys Run runs normally after canceling program execution
❌ Actual Behavior
PowerToys Run crashes
Other Software
No response

Thanks for opening the issue.
There doesn't seem to be a crash in the logs so to speak. The error is logged but then according to the logs PowerToys Run keeps running. You're saying you're unable to use PowerToys Run after this occurs?
A MsgBox appears with some characters in another language, can you please copy it here so we can try to translate?
/needinfo

My current shortcut is ALT+Space. It can be seen in gif, but after a startup failure, the shortcut cannot respond again.
*After testing, restarting PowerToys cannot make PowerToys Run run normally. Can only be restored by rebinding shortcut keys
The text in MsgBox is “无法启动：D:\Desktop\XCOM V2.6.exe.lnk"
*D:\Desktop\XCOM V2.6.exe.lnk is the path where I started the application


Fix #4766 Download file from HTTPS server with self-signed certificate

Related to issue #4766

Assigning to @loos-br since redmine ticket is already owned by him

It's dangerous. With this option in, someone could self-sign and use a CN as legit site and it would be accepted. It would be acceptable if there is an option on GUI, off by default, and user must check that he wants to to accept self-signed certificates when downloading files from HTTPS. And this options must have a big warning message saying about the risks


pip install b2fuse fails on ubuntu focal 20.04

root@remotefs:~# sudo pip install b2fuse

Collecting b2fuse
  Downloading https://files.pythonhosted.org/packages/67/e6/6884773918f9d05cd7a73d9c89e55caf0bf37b82022d144f6da407d75da1/b2fuse-1.3.tar.gz
Collecting PyYAML==3.12 (from b2fuse)
  Downloading https://files.pythonhosted.org/packages/4a/85/db5a2df477072b2902b0eb892feb37d88ac635d36245a72a6a69b23b383a/PyYAML-3.12.tar.gz (253kB)
    100% |████████████████████████████████| 256kB 3.1MB/s
Collecting b2==1.1.0 (from b2fuse)
  Downloading https://files.pythonhosted.org/packages/21/3f/2ca1d3d3990b044549c26c0a0c5797bb1231709f8ce808caad1e8b4fcb70/b2-1.1.0.tar.gz (86kB)
    100% |████████████████████████████████| 92kB 13.2MB/s
Collecting fusepy==2.0.4 (from b2fuse)
  Downloading https://files.pythonhosted.org/packages/70/aa/959d781b7ac979af1a9fbea0faffe06677c390907b56b8ce024eb9320451/fusepy-2.0.4.tar.gz
Collecting arrow>=0.8.0 (from b2==1.1.0->b2fuse)
  Downloading https://files.pythonhosted.org/packages/92/fa/f84896dede5decf284e6922134bf03fd26c90870bbf8015f4e8ee2a07bcc/arrow-0.15.5-py2.py3-none-any.whl (46kB)
    100% |████████████████████████████████| 51kB 14.3MB/s
Collecting futures>=3.0.5 (from b2==1.1.0->b2fuse)
  Downloading https://files.pythonhosted.org/packages/d8/a6/f46ae3f1da0cd4361c344888f59ec2f5785e69c872e175a748ef6071cdb5/futures-3.3.0-py2-none-any.whl
Collecting logfury>=0.1.2 (from b2==1.1.0->b2fuse)
  Downloading https://files.pythonhosted.org/packages/55/71/c70df1ef41721b554c91982ebde423a5cf594261aa5132e39ade9196fa3b/logfury-0.1.2-py2.py3-none-any.whl
Collecting requests>=2.9.1 (from b2==1.1.0->b2fuse)
  Downloading https://files.pythonhosted.org/packages/1a/70/1935c770cb3be6e3a8b78ced23d7e0f3b187f5cbfab4749523ed65d7c9b1/requests-2.23.0-py2.py3-none-any.whl (58kB)
    100% |████████████████████████████████| 61kB 13.3MB/s
Requirement already satisfied: six>=1.10 in /usr/lib/python2.7/dist-packages (from b2==1.1.0->b2fuse) (1.14.0)
Collecting tqdm>=4.5.0 (from b2==1.1.0->b2fuse)
  Downloading https://files.pythonhosted.org/packages/47/55/fd9170ba08a1a64a18a7f8a18f088037316f2a41be04d2fe6ece5a653e8f/tqdm-4.43.0-py2.py3-none-any.whl (59kB)
    100% |████████████████████████████████| 61kB 13.9MB/s
Collecting backports.functools-lru-cache>=1.2.1; python_version == "2.7" (from arrow>=0.8.0->b2==1.1.0->b2fuse)
  Downloading https://files.pythonhosted.org/packages/da/d1/080d2bb13773803648281a49e3918f65b31b7beebf009887a529357fd44a/backports.functools_lru_cache-1.6.1-py2.py3-none-any.whl
Collecting python-dateutil (from arrow>=0.8.0->b2==1.1.0->b2fuse)
  Downloading https://files.pythonhosted.org/packages/d4/70/d60450c3dd48ef87586924207ae8907090de0b306af2bce5d134d78615cb/python_dateutil-2.8.1-py2.py3-none-any.whl (227kB)
    100% |████████████████████████████████| 235kB 3.3MB/s
Collecting funcsigs (from logfury>=0.1.2->b2==1.1.0->b2fuse)
  Downloading https://files.pythonhosted.org/packages/69/cb/f5be453359271714c01b9bd06126eaf2e368f1fddfff30818754b5ac2328/funcsigs-1.0.2-py2.py3-none-any.whl
Collecting urllib3!=1.25.0,!=1.25.1,<1.26,>=1.21.1 (from requests>=2.9.1->b2==1.1.0->b2fuse)
  Downloading https://files.pythonhosted.org/packages/e8/74/6e4f91745020f967d09332bb2b8b9b10090957334692eb88ea4afe91b77f/urllib3-1.25.8-py2.py3-none-any.whl (125kB)
    100% |████████████████████████████████| 133kB 8.2MB/s
Collecting certifi>=2017.4.17 (from requests>=2.9.1->b2==1.1.0->b2fuse)
  Downloading https://files.pythonhosted.org/packages/b9/63/df50cac98ea0d5b006c55a399c3bf1db9da7b5a24de7890bc9cfd5dd9e99/certifi-2019.11.28-py2.py3-none-any.whl (156kB)
    100% |████████████████████████████████| 163kB 5.2MB/s
Collecting chardet<4,>=3.0.2 (from requests>=2.9.1->b2==1.1.0->b2fuse)
  Downloading https://files.pythonhosted.org/packages/bc/a9/01ffebfb562e4274b6487b4bb1ddec7ca55ec7510b22e4c51f14098443b8/chardet-3.0.4-py2.py3-none-any.whl (133kB)
    100% |████████████████████████████████| 143kB 11.4MB/s
Collecting idna<3,>=2.5 (from requests>=2.9.1->b2==1.1.0->b2fuse)
  Downloading https://files.pythonhosted.org/packages/89/e3/afebe61c546d18fb1709a61bee788254b40e736cff7271c7de5de2dc4128/idna-2.9-py2.py3-none-any.whl (58kB)
    100% |████████████████████████████████| 61kB 13.9MB/s
Building wheels for collected packages: b2fuse, PyYAML, b2, fusepy
  Running setup.py bdist_wheel for b2fuse ... done
  Stored in directory: /root/.cache/pip/wheels/e5/23/c4/476d431f1de1f5cad7b9890f4eeb193d8e5d7cd4402aa5654c
  Running setup.py bdist_wheel for PyYAML ... done
  Stored in directory: /root/.cache/pip/wheels/03/05/65/bdc14f2c6e09e82ae3e0f13d021e1b6b2481437ea2f207df3f
  Running setup.py bdist_wheel for b2 ... done
  Stored in directory: /root/.cache/pip/wheels/c7/21/b7/6a3e8c2d9f0aab3154b2c39c883d7c759e33260726a0682108
  Running setup.py bdist_wheel for fusepy ... done
  Stored in directory: /root/.cache/pip/wheels/c5/fc/87/bd3c9942ab2366b4838ea6588f98fd096facb0dbf123e57399
Successfully built b2fuse PyYAML b2 fusepy
Installing collected packages: PyYAML, backports.functools-lru-cache, python-dateutil, arrow, futures, funcsigs, logfury, urllib3, certifi, chardet, idna, requests, tqdm, b2, fusepy, b2fuse
  Found existing installation: PyYAML 5.3
    Not uninstalling pyyaml at /usr/lib/python2.7/dist-packages, outside environment /usr
    Can't uninstall 'PyYAML'. No files were found to uninstall.
Successfully installed PyYAML-3.12 arrow-0.15.5 b2-1.1.0 b2fuse-1.3 backports.functools-lru-cache-1.6.1 certifi-2019.11.28 chardet-3.0.4 funcsigs-1.0.2 fusepy-2.0.4 futures-3.3.0 idna-2.9 logfury-0.1.2 python-dateutil-2.8.1 requests-2.23.0 tqdm-4.43.0 urllib3-1.25.8
root@remotefs:~#
root@remotefs:~# b2fuse
Traceback (most recent call last):
  File "/usr/local/bin/b2fuse", line 6, in <module>
    from b2fuse.b2fuse import main
  File "/usr/local/lib/python2.7/dist-packages/b2fuse/b2fuse.py", line 32, in <module>
    from b2fuse_main import B2Fuse
  File "/usr/local/lib/python2.7/dist-packages/b2fuse/b2fuse_main.py", line 37, in <module>
    from b2.api import B2Api
  File "/usr/local/lib/python2.7/dist-packages/b2/api.py", line 15, in <module>
    from .b2http import B2Http
  File "/usr/local/lib/python2.7/dist-packages/b2/b2http.py", line 13, in <module>
    import arrow
  File "/usr/local/lib/python2.7/dist-packages/arrow/__init__.py", line 3, in <module>
    from .api import get, now, utcnow
  File "/usr/local/lib/python2.7/dist-packages/arrow/api.py", line 10, in <module>
    from arrow.factory import ArrowFactory
  File "/usr/local/lib/python2.7/dist-packages/arrow/factory.py", line 18, in <module>
    from arrow import parser
  File "/usr/local/lib/python2.7/dist-packages/arrow/parser.py", line 15, in <module>
    from backports.functools_lru_cache import lru_cache  # pragma: no cover
ImportError: No module named functools_lru_cache
root@remotefs:~#

Seems to work when I install from git.

This is actually an error in B2CommandLineTool which this project depends on. If it persists it should be reported here https://github.com/Backblaze/B2_Command_Line_Tool

Working on a new updated version with some fixes as B2CommandLineTool has changed. Try this out if you are still interested: https://github.com/sondree/b2_fuse/tree/version1.4

I will update the PIP package version too once this 1.4 gets off the ground, in the meanwhile I consider this closed. Thanks for your interest in the project!


Fix Pdf.js api accesses through obsidian

fixes #5, (and #7, #12, #13, but it's all the same).
Also added typings for Pdf.js within the project, so future upstream breaking changes will be easier to spot.

这个版本怎么使用呢？

@liammagee please let me know if there is anything I can do to help get this merged in. 😄

Thanks very much - I've merged your PR after a long delay. Hopefully that
resolves a number of the outstanding issues.
Liam.
On Fri, 19 Apr 2024 at 07:10, Razboy20 @.***> wrote:

@liammagee https://github.com/liammagee please let me know if there is
anything I can do to help get this merged in. 😄
—
Reply to this email directly, view it on GitHub
https://github.com/liammagee/obsidian-topic-linking/pull/14#issuecomment-2065330664,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAUNVHK2DNMFDN2TUMSM5TY6AZGDAVCNFSM6AAAAAA5NAEDPWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRVGMZTANRWGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


Q: Server 'freeze' on ffmpeg action?

Q
A

Bug?
no

New Feature?
no

Version Used
0.13.0

FFmpeg Version
FFmpeg 3.4.4

OS
Unbuntu 18.04.1 - Apache2

####Introduction
Hi,
I'm working on a video platform project an plan to use php-ffmpeg for a while (we can't afford big transcoding server, all has to be done on the same server).
So I've added a function that takes the file people upload and transcodes it to mp4 (We only accept mp4, webm & ogg for now, but are planning to accept as many as possible)
The only problem is that when I transcode a video via the php-ffmpeg library, the server 'freezes' until the encoding is done; The entire server returns a loading loop. I don't know if this is normal (even though it seems sort of normal for me) and if there is a way to avoid that.
Actual Behavior
Server "freeze" on video transcode: the website becomes unavaible until the ffmpeg action is done.
Expected Behavior
No freeze: being able to use the website while the action is in progress.
Steps to Reproduce
Try to encode a file with an apache server, I guess?

You can increase the number of parallel php processes handling incoming requests to resolve this issue.
Please note that it is not recommended to let this action be executed in the same request as the user is uploading it.
I'd create a background queue, that processes such media and the user may poll in that time.

How would you go about creating a background queue?

How would you go about creating a background queue?


Add option to pass css file to the default template

It would be great to have a option to pass a additional css to actually get the styles in the styleguide without having to duplicate default template.

Closing due to inactivity.


[bug] d3d11: DvpVerifyCommittedResources() fail if bind same UAV to multiple Slots

DvpVerifyCommittedResources(): Compare local Commited d3d11Uavs with CSGetUnorderedAccessViews failed.
After inspect result of CSGetUnorderedAccessViews, I found early uav binding slot will reset to NULL,

The bug is not related to application code.
Just two Dispatch, refers same UAV,
but bound to different Slot.
The bug maybe lives in Engine's state tracking code.

I found this:
Same resource is not allowed to be set in different UAVs

This behavior is invalid in Direct3D11: you can only bind resource once for output:
D3D11 ERROR: ID3D11DeviceContext::CSSetUnorderedAccessViews: The UnorderedAccessView at slot 0 overlaps with the UnorderedAccessView at slot 1. It is not possible to write to the same Subresources (and PlaneSlice if applicable) at the same time. [ STATE_SETTING ERROR #2097402: DEVICE_CSSETUNORDEREDACCESSVIEWS_INVALIDVIEW]

With current Api, It's not easy to manually unbind the uav from previous slot.
Either get underline d3d device context impl or calling InvalidStates.
To work around this problem, i have changed local fork's d3d11 impl to unbind unused slots  before bind changed slot.
Anyway, only d3d11 need this hack.

If you use two textures, you should have two SRBs that reference each one for output. When you bind the second one, the first one should be unbound.

Essentially, an SRB can only have one texture that is set for output

I just need to bind the uav to new slot position, not change resource state.
Current Api is not easy to do so.
With resource transition mode AUTO, i assume the unbind rebind step can be done by the engine.
Because if I just change the uav variable definition order in hlsl, the assert error can go away.
Quite strange if engine runtime behavior depends on this.

When you bind an SRB, the engine unbinds all resources that need to be unbound, it is automatic.
I don't fully understand what exactly you are doing - can you provide a sequence of commands with shaders that you are using?

AFAIK, in Bgfx, i just need to describe current Dispatch's resource bindings, every draw command description is stateless.
Not worry about unbind uav to cleanup previous Dispatch's mess.

Sorry, i will provide an example later tomorrow.

This is the example to produce above situation:
uav_slot.zip
What the sample does
Dispatch three compute kernel:

Write to uav Buffer0 and Buffer1
Read and write Buffer0
Read and write Buffer1

Build and run

CMakeLists.txt - Set DILIGENT_ROOT to DiligentEngine directory.
After build, set executable runtime directory to the assets subfolder.

Problem
Assert error only in d3d11 backend, in Step.3

Hi, could you please have a look at the example.
Is this a mis-use of Diligent API, or a real bug>

This is a real issue

Hey, two nested for loop and CSSetUnorderedAccessViews(null) may not be a good idea.
Change UAV Binding is on runtime critical path.
You may only change the validation layer, what i previous thought:

Only tracking [NumUav]
Change DvpVerifyXXX, Do not cache whole CommittedD3D11ResourcesArr[SHADER_TYPE_COMPUTE],
populate it dynamically, for example:

Code from DXVK:
  template<typename ContextType>
  void STDMETHODCALLTYPE D3D11CommonContext<ContextType>::CSGetUnorderedAccessViews(
          UINT                              StartSlot,
          UINT                              NumUAVs,
          ID3D11UnorderedAccessView**       ppUnorderedAccessViews) {
    D3D10DeviceLock lock = LockContext();

    for (uint32_t i = 0; i < NumUAVs; i++) {
      ppUnorderedAccessViews[i] = StartSlot + i < m_state.uav.views.size()
        ? m_state.uav.views[StartSlot + i].ref()
        : nullptr;
    }
  }

Then, no price to pay when doing UAV bindings (in release build),
cost only in validation.

Need CSSetUnorderedAccessViews(null) to suppress warning.
The problem is to quickly check this rare condition, not to check it with two for loops in  every call to  DeviceContextD3D11Impl::BindCacheResources().

This will not be a problem. First of all, in any application there are only a handful of CSSetUnorderedAccessViews calls in a frame.
Second, the loop only runs for slots that are not being set and checks other slots, so there will be not too many operations.

😀Thank you so much.
It works now, no error on complex compute flows.


Add debug check to continueResolution

Adding this debug check makes Example 5bis fail earlier, and also makes Examples 3 and 4 fail.
The code in Ok () -> branch has not been changed, just indented, but GitHub diff isn't good enough to show this.

GitHub is actually good enough, but only when you tell it to be:
https://github.com/mpizenberg/elm-pubgrub/pull/2/files?diff=split&w=1
(Check the whitespace box to get github working)

That hides the lines completely. There is no option to see the lines, but have the changed parts highlighted, which would only highlight whitespace here.

Aha very true, maybe if you click the button really fast and also blink lots the two will merge! Anyway I am only being nosy here. The change looks good to me though :)

Not related to PubGrub, but I'm currently working on an Elm package which is about diffing, so I'm taking notes of how other algorithms handle different situations.
Still has some issues like long lines.

I've just had a look at the PR code now. I don't think the added check is correct but let me know if you think I'm wrong. You're adding a check to verify that priorCause almost satisfies the partial solution inside continue resolution whereas this relation is only supposed to be verified if the complete conflict resolution step ended (cf https://github.com/dart-lang/pub/blob/master/doc/solver.md#unit-propagation).
I believe this is my fault because while refactoring some of the code I kept the comment "priorCause is guaranted to be almost satisfied by the partial solution" at that location whereas that comment should only appear at the end of conflict resolution (line 244).
I think I've refactored that main PubGrub.elm algorithm module a 1000 times to convert the very procedural (with mutations) description of the algorithm into a functional recursive one. That's also why there are less doc comments here than in the other modules.

Yes I think you are right. I added that check because of your comment, and I didn't check the Pubgrub algorithm as I don't quite understand conflict resolution yet. But re-reading that part now, there is no mention of priorCause almost satisfying inside the algorithm.


tidy dataset categories in JKAN layer

categories which come in through the raw scraped data need to be mapped to one of our main JKAN categories here https://github.com/OpenDataScotland/jkan/blob/gh-pages/_data/categories.yml
This should be done in an intermediary processing layer between raw data and presented data (we want to retain the raw messy data for analytics).

Done! https://github.com/OpenDataScotland/the_od_bods/commit/a4279776029ebf87b87094246d67be154c20bd9c JKAN now displays one of 13 ODS categories or Uncategorised instead of the raw dataset tags. Still is a manual solution for now but future task to improve quality of categorisation.


ModuleNotFoundError: No module named 'usb' solution

ModuleNotFoundError: No module named 'usb'
fix it installing it sudo like this:
sudo pip3 install pyusb
this is a hint worth mentioning

You are right, added the root infos in the readme. Thanks!

You are right, added the root infos in the readme. Thanks!


STB_Image?

stb_image.h from the stb headers seems to support more formats in a standardized API. May ease up the dependency tree from lodepng and nanojpg. Could be a good addition along-side the other loaders.

Thank you. I don't know much the differences between the libraries but as far as i can tell stb_image may replace lodepng and nanojpg in the future.


Problem when scraping data from theprotocol.it website

Short Description
Job listings from theprotocol.it do not scrape.
Detailed Description
The problem occurs every time we want to scrape data from theprotocol.it.
The bug was tested on the links:

theprotocol.it 1
theprotocol.it 2

For both links the error is the same, the jobs do not scrape and in the logs fly endlessly looped messages like the following:
Successfully visited https://theprotocol.it/filtry/trainee,assistant,junior;p/krakow;wp/zdalna,stacjonarna,hybrydowa;rw&pageNumber=1
Found 53 job offers
Successfully visited https://theprotocol.it/filtry/trainee,assistant,junior;p/krakow;wp/zdalna,stacjonarna,hybrydowa;rw&pageNumber=2
Found 53 job offers
Successfully visited https://theprotocol.it/filtry/trainee,assistant,junior;p/krakow;wp/zdalna,stacjonarna,hybrydowa;rw&pageNumber=3
Found 53 job offers
Successfully visited https://theprotocol.it/filtry/trainee,assistant,junior;p/krakow;wp/zdalna,stacjonarna,hybrydowa;rw&pageNumber=4
Found 53 job offers
Successfully visited https://theprotocol.it/filtry/trainee,assistant,junior;p/krakow;wp/zdalna,stacjonarna,hybrydowa;rw&pageNumber=5
Found 53 job offers
Successfully visited https://theprotocol.it/filtry/trainee,assistant,junior;p/krakow;wp/zdalna,stacjonarna,hybrydowa;rw&pageNumber=6
Found 53 job offers

Steps to Reproduction

Adding a link to "websites," for example theprotocol.it or the one that is given in the documentation link theprotocol.it from the documentation
Running the script

Expected Behavior
Scraping jobs from theprotocol.it
Additional Information
I was scraping job listings into a google sheet.
Scraping from other sites worked fine, only with theprotocol.it there was a loop and the listings would not add to the google sheet.

This is a problem with pagination.
For example, go to this link https://theprotocol.it/filtry/trainee,assistant,junior;p/krakow;wp/zdalna,stacjonarna,hybrydowa;rw
and click on the first offer from the list and then copy the url

Offers view should looks like this

After following the steps you indicated, everything scrapes correctly.


Failing emacs:go-mode/:list

Recently failing test for http://cht.sh/emacs:go-mode/:list
Running 23: emacs:go-mode/:list         # special editor names
curl -s http://localhost:8002/emacs:go-mode/:list?T
--- results/23^I2022-07-10 07:54:39.555367351 +0000
+++ /tmp/cht.sh.tests-6ZEmQKfRlEUtnD^I2022-07-10 07:56:53.775544090 +0000
@@ -22,5 +22,6 @@
 range
 rosetta/
 slices
+south meaning
 switch
 types
FAILED: [23] emacs:go-mode/:list

I am not sure where this content coming from. rosetta/ alone doesn't look like an editor name.
@chubin what this test supposed to return? I see it is transformed to http://cht.shgo/:list

This is a result of https://github.com/chubin/cheat.sheets/commit/a5dae0e111c106ace07bb207e02814bf00fd6b74
Have you updated your local tests/results/* files?
$ CHEATSH_UPDATE_TESTS_RESULTS=YES bash tests/run-tests.sh


Updating deprecation update section with the correct blog post.

Submitted via Learn Editor.

#sign-off


Tab instant completion

Instantly autocomplete a common part of all suggested completions
Example:
Typing "P" has two variants of completion: "Proxy" and
"Promise", so the console would instantly update to "Pro" as this is a
common part of all suggested completions.
The behavior is similar to Bash or ZSH.
Resolves #32

Due to readline migration we have this functionality now


do not cancel tuples if already done or failed

related tests https://github.com/SubstraFoundation/substra-tests/pull/40

I merged for now, we will refactor this code soon


Total population is now incremented when a town is selected.

Thank you @erose !
You've taught me something new about JavaScript, which I had read but never understood
"The addition assignment operator (+=) adds a value to a variable"


Text Changes - Security Question Confirmation

Changes:
Line 1: Security Answer confirmed
Line 2: Answer backed up successfully

-Verified this issue on Dev app v1.7.0 (290)


Parallel request to the server

For example, the server side is deployed. Can the server-side handle multiple parallel transcription requests? How many requests can it be handled? Will there be any performance issues? It may be a basic question, but I wanna know about it. Thanks:)

Yes it can. On a RTX4080 I am able to get 4 parallel streams without issue, this is specified in the TranscriptionServer class. It's default is 4, but you can do more.
Each stream loads into VRAM, so you will be limited by VRAM.


[Feature][be/fe] Add warning message for TestConnection

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Use case
As a user, when setting up Apache DevLake connection, I need a specific warning message when my token has limited access.
Description
With @jakezhu9 's great implementation from #4686, we notice that Github has multiple levels of access for a PAT.

For public repos, #4686 is sufficient for the case.
For private repos, we also need extra permissions in order to do so.

However, it is hard to tell what is the intention when the connection is being tested. The reasonable way to solve the problem would be to prompt users about the extra permission and why they are needed for users to decide wisely.
Solution
For Github, when public repos checking is OK, but NOT private repos, the BE should output sth like the following
200 OK
{
  "success": true,
  "warning": true,
  "message": "`repo` is also required if you need to collect data from private repositories",
  "login", "whomai"
}

when token has all possible public/private permission we need, the API should output sth like the following:
200 OK
{
"success": true,
"warning": false,
"message": "success",
"login", "whomai"
}
if token has none of the permission we need:
400 OK
{
  "success": false,
  "warning": false,
  "message": "`repo:status`, `repo_deployment`, `read:user`, `read:org`  are required, `repo` is required for collecting data from private repositories",
  "login", "whomai"
}

The general idea is to add warning flag to indicate if the given PAT is limited, and detail would be described by the good old message field.
The idea applies to other plugins as well and should be fine-tuned according to their API specification.
Todo

Github
Jira
Gitlab
Bitbucket

Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

@Startrekzky @yumengwang03 need prototype design.

prototype design

The prototype is ready.
See details in this link: https://www.figma.com/file/Eux4Dhorxp7M0TwzOnL6Yh/New-Config-UI?node-id=4925%3A37345&t=0NDQQ7WE5NonYlfq-1

@tanninghan Could you please tell us the prototype link?