Produce metrics for ThreadPoolExecutors

At minimum, create metrics for pool sizes and task counts, maybe active threads (this is more expensive). Additional metrics can be created for known subtypes.
Executors should not be modified, rather metrics should be pulled from them so that any type can be supported. This implies some form of registration (e.g. at the point of installation via a builder, etc.).

Stating the obvious likely, but we should do this after the 2.0 work is merged.

Requested recently by a customer through a different other channel, let's retriage

We are seeing in our app, when load increases on an instance, the requests are put on the thread pool queue. When the thread pool queue reaches full capacity then the app responds with a 503. Which is all expected behaviour. But when we deploy on Kubernetes this can result in k8s restarting the pod because it is returning 503 for the health check.
It might be useful if we had a metric for the queue size so that we can alert when the queue is growing, and possibly also use the queue size metric in our scaling decisions.

@gmpatter (and others)
Helidon 2.x already has an optional feature for enabling some additional key performance indicator metrics. For some reason the documentation for this is missing from our published doc site, but below I've pasted the details from our doc source.
Note that the KPI deferred Meter would capture queued requests.
Key Performance Indicator (KPI) Metrics
Any time you include the Helidon metrics module in your application, Helidon tracks two basic performance indicator metrics:

a Counter of all requests received (requests.count), and
a Meter of all requests received (requests.meter).

Helidon also includes additional, extended KPI metrics which are disabled by default:

current number of requests in-flight - a ConcurrentGauge (requests.inFlight) of requests currently being processed
long-running requests - a Meter (requests.longRunning) measuring the rate at which Helidon processes requests which take at least a given amount of time to complete; configurable, defaults to 10000 milliseconds (10 seconds)
load - a Meter (requests.load) measuring the rate at which requests are worked on (as opposed to received)
deferred - a Meter (requests.deferred) measuring the rate at which a request's processing is delayed after Helidon receives the request

You can enable and control these metrics using configuration:
metrics.key-performance-indicators.extended = true
metrics.key-performance-indicators.long-running.threshold-ms = 2000

Further, for SE apps:
Your Helidon SE application can also control the behavior of the KPI metrics programmatically.

Prepare a KeyPerformanceIndicatorSettings object, using its builder, and then pass the builder when invoking the MetricsSupport.Builder#keyPerformanceIndicatorMetricsSettings() method, or

Prepare a Config object and pass it to the MetricsSupport.Builder#keyPerformanceIndicatorMetricsConfig() method.
extended = true
long-running.threshold-ms = 2000

Possibly equivalent to #2688 and #2689 (as described in the earlier comment).
While it's true that the recently-added KPI metrics do not directly report information about the executor used to queue and run requests, the executor behavior can be inferred from the KPI metrics.
Would adding the executor-based metrics add sufficient additional actionable information over the existing KPI metrics to (1) avoid confusion and (2) warrant the overhead in collecting two sets of nearly-equivalent metrics?


[GOBBLIN-1454] Fix NPE when trying to fetch delegation tokens for multiple remote namenodes

Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[x] My PR addresses the following Gobblin JIRA issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"

https://issues.apache.org/jira/browse/GOBBLIN-1454

Description

[x] Here are some details about my PR, including screenshots (if applicable):
When the application tries to fetch delegation tokens for multiple remote namenodes, the current implementation of
getRemoteFSTokenFromURI method doesn't wait for initialization of all the elements of path ("ps") array before calling
obtainTokensForNamenodes leading to NPE when the fileSystem of an uninitialized path is accessed.

Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:
Tested by releasing snapshot version locally, application succeeded successfully.

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Codecov Report

Merging #3293 (0cc5978) into master (2488c3f) will decrease coverage by 37.54%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master   #3293       +/-   ##
============================================
- Coverage     46.55%   9.00%   -37.55%
+ Complexity    10033    1743     -8290
============================================
  Files          2037    2037
  Lines         79277   79278        +1
  Branches       8841    8842        +1
============================================
- Hits          36904    7141    -29763
- Misses        38948   71434    +32486
+ Partials       3425     703     -2722

Impacted Files
Coverage Δ

...ava/org/apache/gobblin/util/hadoop/TokenUtils.java
0.00% <0.00%> (ø)

...c/main/java/org/apache/gobblin/util/FileUtils.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...n/java/org/apache/gobblin/fork/CopyableSchema.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...java/org/apache/gobblin/stream/ControlMessage.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...va/org/apache/gobblin/dataset/DatasetResolver.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...va/org/apache/gobblin/converter/EmptyIterable.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...org/apache/gobblin/ack/BasicAckableForTesting.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...n/java/org/apache/gobblin/salesforce/SfConfig.java
0.00% <0.00%> (-100.00%)
:arrow_down:

.../org/apache/gobblin/yarn/HelixMessageSubTypes.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...va/org/apache/gobblin/cluster/SingleHelixTask.java
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 1079 more

Continue to review full report at Codecov.

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

+1 LGTM

@dushyantk1509 could you rebase from master and use those dependency versions? After that it should be good to go.

@dushyantk1509 could you rebase from master and use those dependency versions? After that it should be good to go.

@Will-Lo Did the required changes.

@autumnust @sv2000 Could we run the CI pipeline and merge?


Switching or closing the current view, toast will not be affected (disappeared)

After Toast pops up, toast will not be affected (disappeared) even if you switch or close the current view. How can I achieve this?

The toast remains in whatever view you present it in. If you remove that view, it will be removed with its superview. Sounds like the view you're presenting the toast in is NOT the view that is disappearing from the screen.


Long code cannot be shared

Since the share function currently puts the whole code in a query string, and a URL length is limited (browser-dependent, on my machine for Firefox the limit is around 8000 characters), long code cannot be shared.

I suggest using key-value storage with hash of code mapped to the code itself. Then “share” button computes a hash of code, saves the pair in storage and returns the URL with the hash.


Addresses #1867 add 'material entity' superclass to cell

Addresses #1867 add 'material entity' superclass to cell

Hi @anitacaron, @dosumis, could you kindly review this ticket? This is currently the only active pending PR and I'd like to merge it and then refresh imports to CL.

The issue's title says it adds 'material entity' (BFO:000040). However, it adds 'anatomical structure' (UBERON:0000061). Could you please change the issue's title to avoid confusion in the future and even in the following release notes?

The issue's title says it adds 'material entity' (BFO:000040). However, it adds 'anatomical structure' (UBERON:0000061). Could you please change the issue's title to avoid confusion in the future and even in the following release notes?

Thank you for catching that, @anitacaron. Title updated.


Add connected animations for opening folder in new tab

User experience improvements:

Add connected animations for opening folder in new tab

Screen recording:

Would be better if the animation happens only once for opening multiple folders.

@soumyamahunt
I tried but failed to figure out a way to start multiple animations simultaneously :(
ConnectedAnimation doesn't take effects if there's other on-going ConnectedAnimation.

@hez2010 Will this affect the horizontal tab strip when it's enabled?

I will rebase this PR and add support for the horizontal tab.

@hez2010 I am going to close this pull request as there has been no activity for at least 7 days, please reopen it when you get a chance to add support for horizontal tabs.


About requirement issue

could u provide the detail versions of every requirement environment package, especially torch and CUDA? We have tried many versions of torch or CUDAs, but it still doesn't work for multiple GPU cards training.
Thank you so much!

could u provide the detail versions of every requirement environment package, especially torch and CUDA? We have tried many versions of torch or CUDAs, but it still doesn't work for multiple GPU cards training. Thank you so much!

CUDA=11.8 torch=2.0.0 torchvision=0.15.0


User interface

Read-only user interface should be provided, opening as many file types in browser (especially mobile) as possible.

I guess we should not render PDFs, even on mobile. Alternative is pdf.js, but it is most likely too slow.

Closing this issue since a basic user interface has already been written and this issue is too broad to track its further development.


Make README more public-facing before going public

Before we make this repo public, we'll want to clean up some text in the README and generate-figures-tables.sh script comments to be public-facing. Presumably (?) this will also come hand-in-hand with public S3 bucket for figure data, or some other mechanism to distribute figure data if not.
Spots to update:
https://github.com/AlexsLemonade/scpca-paper-figures/blob/d927751e9ca62abb0af862a1dfe4ef0bf27c32af/README.md?plain=1#L48-L61
https://github.com/AlexsLemonade/scpca-paper-figures/blob/d927751e9ca62abb0af862a1dfe4ef0bf27c32af/generate-figures-tables.sh#L5

Ugh I'm mad that I have a wrong verb in here (which currently require S3 should be requireS, but not mad enough to change it since eventually this line will go away anyways!

To do this, we also need to move any data to a public S3 bucket.

To do this, we also need to move any data to a public S3 bucket.

We'll also need to update paths:
https://github.com/AlexsLemonade/scpca-paper-figures/blob/d927751e9ca62abb0af862a1dfe4ef0bf27c32af/scripts/figure_setup/sync-data-files.R#L7
https://github.com/AlexsLemonade/scpca-paper-figures/blob/d927751e9ca62abb0af862a1dfe4ef0bf27c32af/scripts/figure_setup/sync-metadata.R#L5-L6

If we were to make the data available outside the context of the Portal (i.e., without agreeing to Terms of Use), we would pare down the available fields in the sample metadata, most of which are not required for plotting.
My number one choice would be addressing https://github.com/AlexsLemonade/scpca-portal/issues/312 and then adapting the code for that.

Presumably (?) this will also come hand-in-hand with public S3 bucket for figure data, or some other mechanism to distribute figure data if not.

Any current thoughts here @jaclyn-taroni? We're not sending this out for review at this time, but do we want to have something de-metadata'd data publicly available alongside a pre-print?

I do not think that is necessary right now.


Prepare the release for the week of October 14th.

None  of the RCs presented passed tests.  Closing.

wrong branch in the IC repo


Update template for pull requests

Summary of the discussion
Here describe the findings of the discussion in the issue.
Type of change (see CHANGELOG.md)
Added

template for pull requests (#1160)

Workflow checklist
Automation
Closes #1160
PR-Assignee

[x] An agreement has been reached
[x] 🐙 Add yourself as Assignee
[x] 🐙 Create a draft pull request
[x] 📝 Update the CHANGELOG.md
[x] 📙 Add # to term tracker item
[x] 🐙 All unit tests pass
[x] 🐙 Publish pull request
[x] 🐙 Add someone or a group (oeo-dev) as Reviewer

PR-Reviewer

[ ] 🐙 All unit tests pass
[ ] 📙 Class name fits the concept
[ ] 📙 The classification according to the BFO is correct
[ ] 📙 Axioms have been added and reflect the definition
[ ] 📙 Spelling and grammar in the definition text are correct
[ ] 📙 All changes are in the correct OEO module
[ ] 📙 Update of changelog has been done
[ ] 📙 Correct entries in term tracker item
[ ] 🐙 Provide feedback and show sufficient appreciation for the work done

PR-Assignee

[ ] 🐙 Show recognition for the review performed
[ ] 🐙 Merge pull request
[ ] 🐙 Delete branch
[ ] 🐙 Close issue

I really like the idea of putting the checklist into the description!
So one can check the status in the PR-overview-tab on GitHub right away.
I also like that the type of change reflects the structure of the CHANGELOG.md that's intuitiv.
1st remark:
Shall we move the "Automation"-Part above the checklist and format it as heading (e.g. ##) ?
I think the begin of the checklist acts like a barrier, so users might forget that there comes an editable part in the end again.
2nd remark:
What do you think about writing "PR-assignee/implementer" or something similar just to avoid confusion between "assignee" for PR and the "assigned reviewer"?
Concerning reviewer checklist
It already created a list of potential things reviewers could have a look at, but this was at a time when I thought the "domain vs ontology expert"-distinction was still valid. Therefore, I paused working on that and didn't create a shortend one then.
See here for the list, which still needs refinement.

To be honest, I am quite confused by this PR. Just yesterday we discussed this and concluded that we do not want or need a harmonised PR template. And now there is a PR exactly doing the opposite of what was discussed yesterday?

Hi @l-emele,
I documented my line of thoughts in the linked issue.
In the meeting we discussed that there is no template.
But this was false, there was a template which was not used yet.
And while checking for adding the info to CONTRIBUTING.md I also realised that a template checklist for the PR is easy to create and will be very useful, not only for this project.
In addition I feel a bit irritated by your comment.
It is not like we had an vote and I act against it.
I have agreed to take on the task and doing so I created the best solution in my opinion.
Please give constructive feedback on the template I have developed or suggest an alternative solution.
The current use of the wiki with many subpages is not a good solution in my opinion.

I added some points for the reviewer checklist based on the wiki article.
This can be clarified and perhaps simplified.

I think we should discuss this again in the next OEO DEV meeting before proceeding here. There seems to have happened serious misunderstanding between different people about what we want and about what we don't want.

@stap-m - let's add this to the agenda of the next oeo-dev.

As discussed yesterday we will reduce this template to a minimum and link to the corresponding wiki pages with additional information.

This is a backup of the workflow before reducing it:
Workflow checklist
Automation
Closes #1160
PR-Assignee

[x] An agreement has been reached
[x] 🐙 Add yourself as Assignee
[x] 🐙 Create a draft pull request
[x] 📝 Update the CHANGELOG.md
[x] 📙 Add # to term tracker item
[x] 🐙 All unit tests pass
[x] 🐙 Publish pull request
[x] 🐙 Add someone or a group (oeo-dev) as Reviewer

PR-Reviewer

[ ] 🐙 All unit tests pass
[ ] 📙 Class name fits the concept
[ ] 📙 The classification according to the BFO is correct
[ ] 📙 Axioms have been added and reflect the definition
[ ] 📙 Spelling and grammar in the definition text are correct
[ ] 📙 All changes are in the correct OEO module
[ ] 📙 Update of changelog has been done
[ ] 📙 Correct entries in term tracker item
[ ] 🐙 Provide feedback and show sufficient appreciation for the work done

PR-Assignee

[ ] 🐙 Show recognition for the review performed
[ ] 🐙 Merge pull request
[ ] 🐙 Delete branch
[ ] 🐙 Close issue

How do we proceed with this PR?

We discussed the issue today and the final feedback to the reduced checklist was that we only include the most important points which are missing mostly (changelog, term tracker, appreciation).
I updated the template and entry above.
It is now ready for final review and acceptance.

Yes, the PR was so old the entry in CHANGELOG.md was in the wrong section.
Sorry for taking so long to finalise this!


Setting: Shuffle Wonderitems

Title is self-explanatory. Shuffle the Wonderitems in both games (these are checks that are invisible/hidden rupees and checks that require the player to make some unusual interaction with the environment to get, typically, a rupee to spawn. Some people call some of these checks Hit Spots or Hit Tags. You will need to also add little sparkles to these checks (so players can see where they are) as they are typically very obscure. Rob added a sparkle effect to these for OOTR you can reference his Wonderitem shuffle setting for what the checks include for OOT and then probably based on that find the similar checks in MM.

[x] OOT Wonderitems Shuffle
[x] MM Wonderitems Shuffle

Added as of https://github.com/OoTMM/OoTMM/commit/f8f69ac631b4083b685f6741c0d04a22c2a3765b


[Feature Request] Color for Opened chest which still contains loot

Minecraft 1.16.5
Forge 36.0.46
Lootr 1.16.4-<IP_ADDRESS>
It would be cool if instead of just turning grey/blue on  chest being opened, instead there could be a configureable option to have chests turn grey/blue on chest being empty for the player.
Issue:
Players are moving the chests to a single room near their base which is fine for us, but the problem is when there is are massive wall(s) of them, it is hard to figure out which one was just opened, and which one still has loot in it.
Proposed Solution:
Gold: unopened
Silver/some other color: opened but still contains loot
the (blue/grey?) color: empty

As in, "still has original loot" or "still has items inside of it"?
The latter is theoretically doable -- I could just change the colour of the gems -- but it also means that it someone dumps items inside of it, it would still count.
I'm not sure how feasible it would be to fully detect whether or not all of the items have been taken and it might be annoying if there's something crappy that you don't want to take out of a chest to have it still be marked...
So I guess completely empty makes more sense.

I'm unfortunately going to have to reject this request for now. It's going to triple the amount of data that needs to be stored/transmitted to the client, as there's no way for the client (which is what decides which skin to use) to actually see the contents of a chest (as Minecraft never transmits this information), so at the very least it would increase the amount of data transmitted.
I can think of a few ways around it, but I don't know that adding this level of complexity is necessarily something I want to do right now.
If I can think of an ideal/non-problematic solution or a very simple solution, I'll definitely go ahead with it. Otherwise, it's on the back-burner.


NGINX Ingress Controller expects to find the TLS secret even if the provider is none

As per title, Furyctl doesn't allow creating a cluster with the ingresses available only using HTTP.
Here's the snippet of the furyctl.yaml I'm using.
      ingress:
        baseDomain: minikube.demo
        nginx:
          type: single
          tls:
            provider: none

I'm using this for installing the distribution on my laptop.

Update: It was caused as a side effect of server-side apply. Re-tested it and it works.


add test to make sure tox.ini and .travis.yml match

Is this preferable to using tox-travis?

iirc tox-travis isn't flexible enough
still on the fence about the approach in this pr


PC MAP- Orange Line route

Bus stops missing on the following roads;

Mairehau Rd
New Brighton Rd
Manchester St
St Asaph St,
Tuam St
Hagley Ave
Selwyn St
Patterson Tce
Wales St
Nicholls Rd
Oakridge St

Bus stops showing on Hills Rd that should not be there

Closing and resolving to a single issue:
https://github.com/CanterburyRegionalCouncil/MetroInfoMaps/issues/34


instance of descendant of Array cannot set instance variable

#main.rb
class A < Array
	def initialize(z)
		super()
		@z = z
	end
end
$a = A.new(:z)

throws error main.rb:8: cannot set instance variable (ArgumentError)
Does not affect descendants of Hash. Seems to occur regardless of variable name and value.

I am sorry, it's mruby limitation. Array, String and some other classes (Hashes and Data classes are exceptions) are unable to hold instance variables.


Crash

Description

Reproduction
got this error like 2x already i have no idea how to reproduce it yet

i play with SE and i hovered on pipe when i landed on new site i think

disabling the mod and saving then adding it back fixed it

i have managed to reproduce it, its problem with logistic tanks cause they get bugged on ships


Iosevka nerd fonts

Please fill out the template.
Read: https://k1ss.org/style
Read: https://k1ss.org/guidestones

Description of package
Patched Iosevka font from the nerd-fonts library

Installed manifest of package
http://ix.io/2g4D

New package

[x] Latest upstream version.
[x] I agree to maintain this package.
[x] I agree to notify @dylanaraps if I can no longer maintain this package.

Depends file can be removed if empty.


CHR-23: this doesn't have an issue identifier in the original title, description or branch.

this doesn't have an issue identifier in the original title, description or branch.
Edit: make sure we don't create another.

closing


Remove the non-standard parameter opt_distance from History.prototype.back

This was meant to be removed in #3330 as it is non-standard, not supported
in most browsers and easily replaceable with history.go(-distance). Instead
#3330 incorrectly removed the type annotation but left the parameter in the
symbol definition, making this parameter required.
Fixes #3418

Internal issue created http://b/135116687

Imported for internal review.

Ok, it looks like there's one place in Google that would be broken by this. (It is explicitly targeting IE).
I can ask if that piece of code is still being used, but we may have to revert this to an optional parameter again.

I've approved a change internally to add back the type annotation to make this optional, as the param being required was causing trouble for someone. So you might see that change in the next few days. I'm still in favor of landing this PR if the one internal blocker can be resolved.

Great - thanks


MGDOBR-604: API plugging preliminary work

Task: https://issues.redhat.com/browse/MGDOBR-604
Creation of hooks that can be used to call SDK APIs for bridges, processors and errors.

@jomarko, if the PR is ok for you, I think it is safe to approve it.
The correctness of a PR should be checked against the main branch, IMHO.
As soon as one of the two PRs gets merged, conflicts will be managed in the other, as usual.

@jomarko, I do not understand your polemic.
I said no other thing that when sending a pull request, it should be checked against the branch you want to merge (in this case, main).
Since https://github.com/5733d9e2be6485d52ffa08870cabdee0/sandbox-ui/pull/36 is not yet merged, I don't know why I should resolve conflicts against https://github.com/5733d9e2be6485d52ffa08870cabdee0/sandbox-ui/pull/36 in advance.
I never intended this PR to have priorities over https://github.com/5733d9e2be6485d52ffa08870cabdee0/sandbox-ui/pull/36. I just said that typically the PR that is merged later should resolve conflicts in the main if they are introduced by incorporating other PR in the meantime.

@kelvah I accomplished your comments. Thanks

@vpellegrino Thank you. I see #36 got merged first. Could you rebase please?

@kelvah done


CrystalAura render

Add an movement for render so that whenever the crystal placed the render will move to that place
the same as zaelo crystal render
-thanks for reading-

zaelo crystal render

what? u got a video? u mean where the box like slides from position to position?

zaelo crystal render

what? u got a video? u mean where the box like slides from position to position?

probably

Add an movement for render so that whenever the crystal placed the render will move to that place the same as zaelo crystal render -thanks for reading-

u mean something like what TrollHack ZealotCrystal+ does? (like this: https://m.bilibili.com/video/BV12R4y1F7GJ)

Add an movement for render so that whenever the crystal placed the render will move to that place the same as zaelo crystal render -thanks for reading-

u mean something like what TrollHack ZealotCrystal+ does? (like this: https://m.bilibili.com/video/BV12R4y1F7GJ)

Looks ugly

zaelo crystal render

what? u got a video? u mean where the box like slides from position to position?

扎埃洛水晶渲染

什么？你有视频吗？你的意思是盒子像从一个位置滑到另一个位置？

https://www.youtube.com/watch?v=3_ro-0hIbhs
Render higher difficulty
client is trollhack the sexmaster have the same

https://www.youtube.com/watch?v=3_ro-0hIbhs
Render just like trollhack
and sexmaster have same
https://github.com/Luna5ama/TrollHack

Preview here https://github.com/3arthqu4ke/3arthh4ck/actions/runs/2928411167


Micropython ESP-IDF V5.0  "Failed to resolve component 'tcpip_adapter'" (IDFGH-7294)

Hi, I have seen that this is an existing issue. Is this being fixed?
-- Check for working CXX compiler: /Users/thomasgiles/.espressif/tools/xtensa-esp32-elf/esp-2021r2-patch3-8.4.0/xtensa-esp32-elf/bin/xtensa-esp32-elf-g++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Building ESP-IDF components for target esp32
CMake Error at /Users/thomasgiles/esp/esp-idf/tools/cmake/build.cmake:197 (message):
Failed to resolve component 'tcpip_adapter'.
Call Stack (most recent call first):
/Users/thomasgiles/esp/esp-idf/tools/cmake/build.cmake:225 (__build_resolve_and_add_req)
/Users/thomasgiles/esp/esp-idf/tools/cmake/build.cmake:512 (__build_expand_requirements)
/Users/thomasgiles/esp/esp-idf/tools/cmake/project.cmake:422 (idf_build_process)
CMakeLists.txt:58 (project)
-- Configuring incomplete, errors occurred!
See also "/Users/thomasgiles/XX/micropython/ports/esp32/build-GENERIC/CMakeFiles/CMakeOutput.log".
cmake failed with exit code 1
make: *** [all] Error 2
Many thanks,
Thomas

I'm afraid this will need to be solved on Micropython side, as tcpip_adapter is removed from ESP-IDF in the upcoming  v5.0 release. For migration instructions, please refer to https://docs.espressif.com/projects/esp-idf/en/latest/esp32/migration-guides/tcpip-adapter.html

@igrr  Thank you very much for your reply. I will look into it on the micropython side.


⚠ Jenkins Plugins Artifactory has degraded performance

In 2606036, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1147 ms

Resolved: Jenkins Plugins Artifactory performance has improved in b89cf3b after 12 minutes.


Large files: synchronization does not work with more than two clients

Large files are not synchronizes correctly with more than two logged in clients.
Also, the process does not fail, but is stuck somewhere.

Thanks for the big report. The large file download needs further stabilization. Will look into that asap.

We did not have time today to fully investigate it, but we did some tests.
It works in a small scenario with only two peers connected to a router and both logged in (same user).
Scenario where it does not work:

login of 3 clients (same user)
client 1 adds a large file (e.g. 30MB). It will be added to the profile (metadata), i.e. the add operation succeeds.
client 2 and 3 start requesting chunks from client 1, which works partially (according to the logging output). However, there are chunks that are never requested and hence, no other client will have all chunks respectively the full file.
It seems that client 2/3 also try to download chunks from each other even though they do not have the chunks. In the end, they send each other DECLINED responses (AskForChunkStep / RequestChunkMessage). As a result, they try again, ... and so on. (Not entirely sure whether this is the reason why the process never stops, should stop after 3 retries I think, so there may also be an exception in a runnable that is not caught).

I just improved the process for downloading large files. It needs further testing, but running your scenario on a single machine works fine now (tested with 100MB file). Will test with different machines in same LAN tomorrow.
If you have time, can you re-run the scenario with you setup (8 machines)?

I just saw the Git Large File Storage extension that can be used for Git. Maybe there is some inspiration in it that could help improve the H2H concepts. (https://git-lfs.github.com/?utm_source=github_site&utm_medium=blog&utm_campaign=gitlfs)

I've tried to upload and download a 1GB file and it still doesn't work. I doesn't work even with 30MB files. Is this issue solved? Will this fix be on the next release and do you have a roadmap for it?


Prepare major version release.

I will be near future release RichMD.js v1.0.
So, Next release is minor version final release.
It will be fix small and refactor stylesheet.

RichMD.js v0.4.0 release 🎉
https://www.npmjs.com/package/richmd/v/0.4.0

RichMD.js will be reborn RichMD.
https://github.com/bebeji-nappa/richmdjs/issues/19


Update requirements

The previous version of tensorflow is said to have some vulnerabilities issues.
We better use tensorflow==1.12.2 or upgrade to tensorflow 2.0

We are planning to upgrade to a newer version of TF. For now, we are closing this PR.


Allow passing fire_webhooks to constructor to be used on every query

Happy to code this another way or have you do it if you have a strong sense of how it should be done. The main thing is that we're able to access the limit headers to appropriately back off. Thanks for jumping on this so quick!


add Context Parser Linter

this code change is to decouple the replaceCharForBrowserConsistency function from the secure handlebars, and introduce the context parser linter as a standalone component to handle this.

CLA is valid!


Does this support nested directories for the files?

As of now file names must be a string, while directories and slashes are not supported.
How do you image your use case?
You want your notes in nested directories i.e.: some_dir/other_dir/note

@xeust commented on Aug 6, 2020, 11:59 PM GMT+4:30:

As of now file names must be a string, while directories and slashes are not supported.
How do you image your use case?
You want your notes in nested directories i.e.: some_dir/other_dir/note

Sorry, I think that I need to do some more tinkering with my setup before I know what exactly I need. So I'll close this issue.
But to not let the question remain unanswered, I already have my notes in highly nested directories:

My primary problems with my current setup are the lack of backlinks, and a lack of web UI. I am going to learn org-mode, and see what I can do from there ...

Yeah this is interesting, thanks for sharing.
The current structure is entirely free / hyperlink based without any hierarchy.
But there are two limitations in my mind:

Sometimes hierarchy / structure is good
All notes are in a single namespace

Hi @NightMachinary ,
I'm still working on this -- any change you'd be up for a short interview / survey about your note taking in effort to improve yarc going forwards?


Debian template doesn't work?

❯ blincus launch myst -t debian
Using debian template
Creating myst
Starting instance myst
Waiting for cloud init...
/usr/bin/cloud-init
....................................
status: done
Blincus ID: c96c30ae569f420f9b35404716aeb1a9
Mounting home directory
Device myhomedir added to myst
Allowing X sharing:
access control disabled, clients can connect from any host
Instance myst ready
Run blincus shell myst to enter

blincus on  main took 30s
❯ blincus shell myst
su: user bronson does not exist or the user entry does not contain all the required fields

same issue with Ubuntu template
❯ blincus launch ubuntu -t ubuntu
Using ubuntu template
Creating ubuntu
Starting instance ubuntu
Waiting for cloud init...
/usr/bin/cloud-init
................................
status: done
Blincus ID: 54309ddc45f14c22a909ee788f7915df
Mounting home directory
Device myhomedir added to ubuntu
Allowing X sharing:
access control disabled, clients can connect from any host
Instance ubuntu ready
Run blincus shell ubuntu to enter

~ took 26s
❯ blincus shell ubuntu
su: user bronson does not exist or the user entry does not contain all the required fields

and Fedora
❯ blincus launch fedora -t fedora
Using fedora template
Creating fedora
Starting instance fedora
Waiting for cloud init...
/usr/bin/cloud-init
............................................................................................................................................................................................................................................................
status: done
Blincus ID: ec5550acb35244dabe16d874fc9ea4d9
Mounting home directory
Device myhomedir added to fedora
Allowing X sharing:
access control disabled, clients can connect from any host
Instance fedora ready
Run blincus shell fedora to enter

~ took 1m18s
❯ blincus shell fedora
su: user bronson does not exist or the user entry does not contain all the required fields

Reinstalled Blincus using the suggested and scary curl -s https://raw.githubusercontent.com/ublue-os/blincus/main/install | sh -s -- --prefix ~/.local ... and it still fails.
❯ blincus launch myfirst -t ubuntu
Using ubuntu template
Creating myfirst
Starting instance myfirst
Waiting for cloud init...
/usr/bin/cloud-init
....................................
status: done
Blincus ID: 5272902f67024afea145bd75fd93945a
Mounting home directory
Device myhomedir added to myfirst
Allowing X sharing:
access control disabled, clients can connect from any host
Instance myfirst ready
Run blincus shell myfirst to enter

blincus on  main took 13s
❯ blincus shell myfirst
su: user bronson does not exist or the user entry does not contain all the required fields

Its quite literally the same issue as #20, The template files are getting written with their template users and whatever else, instead of getting customized with your own system configuration. Ill be sending a PR today trying to fix that

the next release moves the customization to JIT so it won't be accidentally skipped. thanks for the report.


browser always read all files from SerivceWorker

I've rebuild the app and upload it to nginx, then run nginx -s reload
but browser read all files from ServiceWorker

@rainmanhhh what is the versión of the plugin? Do you migrate from older version?

@rainmanhhh what is the version of the plugin? Do you migrate from older version?
your app change some resource? If there are any resource changed works as expected.

just upgrade to latest version yesterday.
I modified some code and rebuild the app yesterday then upload it to server, but page is still the old version(in browser, android webview, and wechat miniprogram webview). then I tried refresh the browser manually, run nginx -s reload but still the same result(browser devtool shows index.html and all other resources are load from ServiceWorker).
then I tried to change the registerType from autoUpdate to prompt and rebuild the app. nothing changed.
then I rollback registerType to autoUpdate and rebuild the app. nothing changed.
but after about 20 mins, I check the page again and new files loaded.

btw, I have two apps in the same domain(but different folders)
similar to this using-multiple-javascript-service-workers-at-the-same-domain-but-different-folde
maybe I need add some config to vue-plugin-pwa?

@rainmanhhh you need to change the scope option and/or the basePath for both using its name inside the root, for example, if /app1/ and /app2/ are the relative paths inside the root, then just configure basePath with /app1/ and /app2/ respectively.

@rainmanhhh if you have shared resources between both apps you cannot make work. The scope will act as a context.

so the developer should know final deploy absolute path, similar to 'browser history router' config? (I'm using 'hash router' in case of relative deploy path)

@rainmanhhh yes, this is a good example, the router

just checked the generated sw.js and I found it uses relative paths to access resources
Is it possible, in theory, to make the plugin auto detect 'base' by reading browser location.path? (since in hash router mode, location.path is always the index.html root)

This is done by workbox and the service worker should work. See https://github.com/antfu/vite-plugin-pwa/issues/23.
I close this issue, check if working, if not working add a repo where we can work to see the changes we need to add and I Will reopen this issue.


Implementing Auto Labeling for Issues

Title:
Implementing Auto Labeling for Issues
Description:
This feature aims to automate the process of assigning labels to issues when they are created or edited. The following labels will be automatically added:

gssoc-extd: Marks the issue as part of GSSOC-extended contributions.
hacktoberfest: Marks it as eligible for Hacktoberfest.
level?: A placeholder label indicating the level, which will remain until the project admin assigns the appropriate level during the Pull Request (PR) review.

Tasks:

Create a GitHub Action that listens to issue events (opened, edited).

Automatically assign the following labels:

gssoc-extd
hacktoberfest
level?

Ensure the placeholder label level? remains on the issue until the project admin assigns the final level during the PR stage.

Test the automation by creating and editing issues.

Acceptance Criteria:

[ ] Labels are added to issues automatically upon creation or editing.
[ ] Placeholder label level? is correctly assigned to issues.
[ ] Final level is assigned by the project admin during PR review.

@Rakshit-gen
Pls assign me this issue and give me level3,hacktoberfest-accepted and gssoc-extd

Sure @ygowthamr start working on it


Grafana variable in request body

Hi,
Is it possible to use Grafana global variables (like $__interval in my usage scenario) inside the request body?
e.g.,
{
...
    "StartTime": "$__isoFrom()",
    "EndTime": "$__isoTo()",
    "Aggregation": {
        "Method": "Min",
        "BucketSize": "$__inverval()"
    }
}

If not, how hard is it to implement and what are the chances that this feature will be added?
Thanks in advance!

Closing.. silly me had a type..
this worked fine - ${$__interval}


10-bit mode

Hello,
There doesn't seem to be a way to get libcamera to choose a 10-bit mode.  Uf the framerate were considered when choosing the mode, ie a faster framerate would cause the 10-bit penalty to be reduced (perhaps.)
much thanks

Hi, thanks for raising this. We're aware of this as a problem, and indeed I think some other issues have been filed that relate to it. It's a question that we're discussing with the libcamera team, but unfortunately we don't have a plan for how to resolve it just yet. For now, the workaround would be to change the "penalty" values - assume you've found where those are defined. Sorry not to have a better answer at the moment.

My personal opinion is that there really isn't a way around just letting the user have direct access to a mode override. There are just too many edge cases for the penalty system to work perfectly. Ie. What about DOL-HDR modes, custom modes that have the same resolution but different FPS output, packed vs. unpacked, etc?
Ex. I'm doing some testing with libcamera-still and it's picking the 4056x3040-pRCC 12-bit Bayer BGBG/GRGR Packed mode rather than unpacked (what I'd prefer). And I'm seeing some artifacts (black fringing on highlights with aliasing) that I feel could be caused by the packing. While this could certainly be some other ISP issue, being able to discretely select modes will be important for folks who need tight control over the entire capture pipeline.

. And I'm seeing some artifacts (black fringing on highlights with aliasing) that I feel could be caused by the packing.

Packing/unpacking modes would not cause the fringing that you are seeing here.  The pixel data is exactly the same, just that we either represent data as 12-bits directly or 12-bits in a 16-bit word.
As to the cause of the fringing... It may be aggressively sharpening in this scene? Try reducing the sharpening strength a bit (details can be found here and here.

Packing/unpacking modes would not cause the fringing that you are seeing here. The pixel data is exactly the same, just that we either represent data as 12-bits directly or 12-bits in a 16-bit word.

Ok, cool. I'm curious though (sorry for the tangent) - What is the reason to have these packed modes? Does the ISP prefer it?

As to the cause of the fringing... It may be aggressively sharpening in this scene? Try reducing the sharpening strength a bit (details can be found here and here).

Yep, that's what it was. I responded in more detail in the other issue.
But back on topic (and apologies for hijacking this thread) - If you're ever looking to expand the discussion about libcamera's design regarding the direct vs. inferred mode access, please let me know. I have plenty of thoughts on the subject :) Boiled down, I think you'll probably need to accommodate both - inferred mode by default (for ease of use), but also provide a way to override this with some user flag that allows the user to directly specify the mode.  Ie. I just tried to capture at 800x600 with the IMX477 (4x3 aspect ratio sensor) and it chose the 2x2 binned 2028x1520 mode, which is not what I would ideally want. I would prefer the full 4056x3040 mode scaled to 800x600 in the ISP.
Thanks again for the help.

Ok, cool. I'm curious though (sorry for the tangent) - What is the reason to have these packed modes? Does the ISP prefer it?

It makes no difference to the ISP, but if the application were to want to peek at the RAW frame buffer, it is much more convenient to have the pixel samples unpacked to 16-bits instead of having to manipulate the packed bitstream.

But back on topic (and apologies for hijacking this thread) - If you're ever looking to expand the discussion about libcamera's design regarding the direct vs. inferred mode access, please let me know. I have plenty of thoughts on the subject :) Boiled down, I think you'll probably need to accommodate both - inferred mode by default (for ease of use), but also provide a way to override this with some user flag that allows the user to directly specify the mode. Ie. I just tried to capture at 800x600 with the IMX477 (4x3 aspect ratio sensor) and it chose the 2x2 binned 2028x1520 mode, which is not what I would ideally want. I would prefer the full 4056x3040 mode scaled to 800x600 in the ISP.

The ability to choose sensor modes is in our plans, and we will add support for it in our libcamera-apps in the near future.

It makes no difference to the ISP, but if the application were to want to peek at the RAW frame buffer, it is much more convenient to have the pixel samples unpacked to 16-bits instead of having to manipulate the packed bitstream.

Makes sense. Thanks for the explanation.

The ability to choose sensor modes is in our plans, and we will add support for it in our libcamera-apps in the near future.

Awesome!

We've finally fixed this here: https://github.com/raspberrypi/libcamera-apps/pull/167
To use it folks would have to build the latest libcamera and libcamera-apps for themselves (currently also requiring an up-to-date kernel using sudo rpi-update; caveats apply), alternatively we'll be rolling the feature out shortly as things get updated.
To control the camera mode that gets selected use the --mode W:H:D option where W and H are the width and height of the camera mode you wish to use and D is the (bit) depth. libcamera will still try to pick the "closest mode" (in some sense), but if you know what values are available then you can get what you want.
For example, if you want the 10-bit 1332x990 HQ cam mode for a video recording, you could use
libcamera-vid -o test.h264 --mode 1332:990:10

The --mode option works for video and still capture. For preview, --viewfinder-mode is equivalent.
There's actually an additional "packing" parameter that determines whether the raw Bayer pixels are packed in memory (occupying only 10 or 12 bits each) or unpacked to 16-bits each (therefore with some wasted memory). So you could use 1332:990:10:U or 1332:992:10:P. The default is P (packed), though this particular detail is unlikely to be of great interest except to those who wish to write code to manipulate raw frame buffers directly.
Finally, we have quite a few documentation updates pending so we'll get round to working through those, including this feature, and we'll list all the available modes for the official Raspberry Pi cameras.

Nice! Looking forward to trying it out. Curious though, how will this affect the behavior described in https://github.com/raspberrypi/libcamera-apps/issues/26#issuecomment-982090956 - Since it's independent of a bit depth, it seems like it might still pick the 2x2 binned mode, right?

No, I think it will be fine. Use --mode 4056:3040 and you'll get the full resolution (12-bit) mode regardless of the output image size.

No, I think it will be fine. Use --mode 4056:3040 and you'll get the full resolution (12-bit) mode regardless of the output image size.

Ah, yes! It's separate from the --width and --height parameters. Will give it a try now.

Just gave it a quick test with a still capture. It looks like it runs its 3A algorithms on the original mode selection, and then switches to the user overridden mode for actual capture. Is that intended? I'll have to think about any ramifications that may have. Here's the short log from this command: libcamera-still --width 800 --height 600 --mode 4056:3040:12 -o ~/mode.jpg
Preview window unavailable
[0:13:02.677066542] [4944]  INFO Camera camera_manager.cpp:293 libcamera v0.0.0+3303-b7b72027
[0:13:02.679333024] [4946]  WARN CameraSensorProperties camera_sensor_properties.cpp:141 No static properties available for 'imx477'
[0:13:02.679369561] [4946]  WARN CameraSensorProperties camera_sensor_properties.cpp:143 Please consider updating the camera sensor properties database
[0:13:02.693031640] [4946]  INFO RPI raspberrypi.cpp:1200 Registered camera /base/soc/i2c0mux/i2c@1/imx477@1a to Unicam device /dev/media1 and ISP device /dev/media0
[0:13:02.693602048] [4944]  INFO Camera camera.cpp:945 configuring streams: (0) 2026x1520-YUV420
[0:13:02.693701881] [4946]  INFO RPI raspberrypi.cpp:164 Format: 1332x990 fmt SBGGR10 Score: 3452.71 (best 3452.71)
[0:13:02.693764215] [4946]  INFO RPI raspberrypi.cpp:164 Format: 2028x1080 fmt SBGGR12 Score: 1084.83 (best 1084.83)
[0:13:02.693784863] [4946]  INFO RPI raspberrypi.cpp:164 Format: 2028x1520 fmt SBGGR12 Score: 0.993421 (best 0.993421)
[0:13:02.693805344] [4946]  INFO RPI raspberrypi.cpp:164 Format: 4056x3040 fmt SBGGR12 Score: 887.993 (best 0.993421)
[0:13:02.693963437] [4946]  INFO RPI raspberrypi.cpp:681 Sensor: /base/soc/i2c0mux/i2c@1/imx477@1a - Selected sensor format: 2028x1520-SBGGR12_1X12 - Selected unicam format: 2028x1520-pBCC
[0:13:02.713842815] [4950]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Saturation = 1.000000
[0:13:02.713930722] [4950]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Contrast = 1.000000
[0:13:02.713952407] [4950]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Brightness = 0.000000
[0:13:02.713970130] [4950]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AwbMode = 0
[0:13:02.713989037] [4950]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Sharpness = 1.000000
[0:13:02.714006667] [4950]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: ExposureValue = 0.000000
[0:13:02.714045685] [4950]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AeExposureMode = 0
[0:13:02.714064278] [4950]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: FrameDurationLimits = [ 33333, 33333 ]
[0:13:02.714089815] [4950]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AeMeteringMode = 0
[0:13:02.714107815] [4950]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: NoiseReductionMode = 3
[0:13:02.714579000] [4946]  INFO RPISTREAM rpi_stream.cpp:133 No buffers available for ISP Output0
[0:13:02.714605611] [4946]  INFO RPISTREAM rpi_stream.cpp:133 No buffers available for ISP Output0
[0:13:02.714620204] [4946]  INFO RPISTREAM rpi_stream.cpp:133 No buffers available for ISP Output0
[0:13:02.714634482] [4946]  INFO RPISTREAM rpi_stream.cpp:133 No buffers available for ISP Output0
[0:13:02.714648685] [4946]  INFO RPISTREAM rpi_stream.cpp:133 No buffers available for ISP Output0
[0:13:02.714662871] [4946]  INFO RPISTREAM rpi_stream.cpp:133 No buffers available for ISP Output0
[0:13:03.246936870] [4946]  INFO RPI raspberrypi.cpp:1738 Dropping frame at the request of the IPA (6 left)
[0:13:03.280134452] [4946]  INFO RPI raspberrypi.cpp:1738 Dropping frame at the request of the IPA (5 left)
[0:13:03.313418959] [4946]  INFO RPI raspberrypi.cpp:1738 Dropping frame at the request of the IPA (4 left)
[0:13:03.346506152] [4946]  INFO RPI raspberrypi.cpp:1738 Dropping frame at the request of the IPA (3 left)
[0:13:03.379805696] [4946]  INFO RPI raspberrypi.cpp:1738 Dropping frame at the request of the IPA (2 left)
[0:13:03.413671444] [4946]  INFO RPI raspberrypi.cpp:1738 Dropping frame at the request of the IPA (1 left)
[0:13:03.446648489] [4946]  INFO RPI raspberrypi.cpp:1738 Dropping frame at the request of the IPA (0 left)
[0:13:08.259223722] [4944]  INFO RPI raspberrypi.cpp:164 Format: 1332x990 fmt SBGGR10 Score: 10552.2 (best 10552.2)
[0:13:08.260304851] [4944]  INFO RPI raspberrypi.cpp:164 Format: 2028x1080 fmt SBGGR12 Score: 8179.84 (best 8179.84)
[0:13:08.260990887] [4944]  INFO RPI raspberrypi.cpp:164 Format: 2028x1520 fmt SBGGR12 Score: 7096 (best 7096)
[0:13:08.261654017] [4944]  INFO RPI raspberrypi.cpp:164 Format: 4056x3040 fmt SBGGR12 Score: 0 (best 0)
[0:13:08.262367479] [4944]  INFO RPI raspberrypi.cpp:164 Format: 1332x990 fmt SBGGR10 Score: 10552.2 (best 10552.2)
[0:13:08.263029220] [4944]  INFO RPI raspberrypi.cpp:164 Format: 2028x1080 fmt SBGGR12 Score: 8179.84 (best 8179.84)
[0:13:08.263401349] [4944]  INFO RPI raspberrypi.cpp:164 Format: 2028x1520 fmt SBGGR12 Score: 7096 (best 7096)
[0:13:08.263763164] [4944]  INFO RPI raspberrypi.cpp:164 Format: 4056x3040 fmt SBGGR12 Score: 0 (best 0)
[0:13:08.264526330] [4944]  INFO RPI raspberrypi.cpp:164 Format: 1332x990 fmt SBGGR10 Score: 10552.2 (best 10552.2)
[0:13:08.265330348] [4944]  INFO RPI raspberrypi.cpp:164 Format: 2028x1080 fmt SBGGR12 Score: 8179.84 (best 8179.84)
[0:13:08.265461330] [4944]  INFO RPI raspberrypi.cpp:164 Format: 2028x1520 fmt SBGGR12 Score: 7096 (best 7096)
[0:13:08.265571644] [4944]  INFO RPI raspberrypi.cpp:164 Format: 4056x3040 fmt SBGGR12 Score: 0 (best 0)
Stream configuration adjusted
[0:13:08.266060311] [4944]  INFO RPI raspberrypi.cpp:164 Format: 1332x990 fmt SBGGR10 Score: 10552.2 (best 10552.2)
[0:13:08.266182200] [4944]  INFO RPI raspberrypi.cpp:164 Format: 2028x1080 fmt SBGGR12 Score: 8179.84 (best 8179.84)
[0:13:08.266246181] [4944]  INFO RPI raspberrypi.cpp:164 Format: 2028x1520 fmt SBGGR12 Score: 7096 (best 7096)
[0:13:08.266302200] [4944]  INFO RPI raspberrypi.cpp:164 Format: 4056x3040 fmt SBGGR12 Score: 0 (best 0)
[0:13:08.266648533] [4944]  INFO Camera camera.cpp:945 configuring streams: (0) 800x600-YUV420 (1) 4056x3040-SRGGB12_CSI2P
[0:13:08.266863218] [4946]  INFO RPI raspberrypi.cpp:164 Format: 1332x990 fmt SBGGR10 Score: 10552.2 (best 10552.2)
[0:13:08.266935107] [4946]  INFO RPI raspberrypi.cpp:164 Format: 2028x1080 fmt SBGGR12 Score: 8179.84 (best 8179.84)
[0:13:08.266991329] [4946]  INFO RPI raspberrypi.cpp:164 Format: 2028x1520 fmt SBGGR12 Score: 7096 (best 7096)
[0:13:08.267128181] [4946]  INFO RPI raspberrypi.cpp:164 Format: 4056x3040 fmt SBGGR12 Score: 0 (best 0)
[0:13:08.267485699] [4946]  INFO RPI raspberrypi.cpp:681 Sensor: /base/soc/i2c0mux/i2c@1/imx477@1a - Selected sensor format: 4056x3040-SBGGR12_1X12 - Selected unicam format: 4056x3040-pBCC
[0:13:08.334194443] [4974]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Saturation = 1.000000
[0:13:08.334836794] [4974]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Contrast = 1.000000
[0:13:08.335212331] [4974]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Brightness = 0.000000
[0:13:08.335579701] [4974]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AwbMode = 0
[0:13:08.335943608] [4974]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Sharpness = 1.000000
[0:13:08.336342849] [4974]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: ExposureValue = 0.000000
[0:13:08.336716849] [4974]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AeExposureMode = 0
[0:13:08.337088552] [4974]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: FrameDurationLimits = [ 100,<PHONE_NUMBER> ]
[0:13:08.337467219] [4974]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AeMeteringMode = 0
[0:13:08.337832515] [4974]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: NoiseReductionMode = 2
Still capture image received

This does output an 800x600 image.

Yes I think that's expected, if you want the preview to run in the full res mode too you'd have to add --viewfinder-mode 4056:3040:12 (actually you only need 4056:3040, the bit depth will default to 12).

Ah ok. But I'd be curious how this affects the 3A algorithms such as auto-exposure as the 2x2 binning mode will have higher exposure (I believe but need to confirm) than the regular non 2x2 binned modes. If that's true, it would throw off the 3A exposure calcs resulting in an underexposed image, right?

Sensors can behave a bit differently here. Some sensors do exactly what you describe, though most of them (including all the official Raspberry Pi ones) keep the output signal level the same and give you better SNR. Our AEC/AGC algorithm actually deals with this correctly, each different mode of a sensor can have an associated "sensitivity", and when you switch between sensor modes it makes the various necessary adjustments. If you want the full gory details, see here: https://git.linuxtv.org/libcamera.git/tree/src/ipa/raspberrypi/controller/rpi/agc.cpp#n308

Very cool. Thanks for the background detail. Just to play devil's advocate (and let me know if this is getting annoying), what about the following scenario?
libcamera-vid --width 1920 --height 1080 --mode 4056:3040:12 -o ~/mode.mp4

My intent with those parameters would be to use the full sensor FOV, but have the ISP resize to the max resolution the h264 encoder can handle (with the mp4 source/display aspect ratio metadata fields set). The issue that I see possibly happening, albeit relatively minor, is that the 3A algorithms might get performed on a cropped FOV (assuming there was a 16x9 mode that matched). And if that happens, the algorithms could misjudge the exposure / white balance due to the different crops / FOV. A bit of an edge case, but what do you think? Is my logic correct?

It is possible that if you use a heavily cropped mode in preview/viewfinder, then it would not reflect the full FoV in the statistics for the 3A.  However, the effect would be marginal at best, given that our sensor crops are pretty modest.

It is possible that if you use a heavily cropped mode in preview/viewfinder, then it would not reflect the full FoV in the statistics for the 3A. However, the effect would be marginal at best, given that our sensor crops are pretty modest.

Kk, sounds reasonable to me.

How can I enable the DOL-HDR mode (RP HQ Cam - IMX477)

thank you

Sorry, this mode is not supported in either the sensor driver, nor in libcamera.

what do you mean with sensor driver?

the camera sensor is mounted on a board which does not support the dol-hdr mode?

That's correct.  There is no functionality in the driver to enable this mode in the hardware at all.  We will be happy to accept pull requests if any members of the public would like to add this features.
However, even if this was available in the sensor driver, it still requires considerable effort to implement in the libcamera stack for the software applications to use.

thanks naushir!
what is with the IMX464 or IMX334 with multi exposure HDR mode
is that supported?
Or better said, how do I find out, if something is supported or not.

Supported sensors will have a cam_helper file in https://git.linuxtv.org/libcamera.git/tree/src/ipa/raspberrypi, and a JSON tuning file in https://git.linuxtv.org/libcamera.git/tree/src/ipa/raspberrypi/data.
There will also be an associated Linux kernel driver in https://github.com/raspberrypi/linux/tree/rpi-5.15.y/drivers/media/i2c, and a dtoverlay in https://github.com/raspberrypi/linux/tree/rpi-5.15.y/arch/arm/boot/dts/overlays
I've not seen a Linux kernel driver for either IMX464 or IMX334. If you have a vendor of those modules, then ask them for support.

that's so enlightening. thanks man!
But what about this sensor (IMX387), declared especially for Raspberry Pi, but no support?

But what about this sensor (IMX387), declared especially for Raspberry Pi, but no support?

Typo - IMX378, not IMX387.
IMX378 is a sibling to IMX477 and uses the same driver.

In order to use the new IMX678 with all HDR functionalities with raspberry pi, the necessary drivers must be installed. Do you usually get them from the manufacturer? And if not, who does that? Or where do you find someone you can pay to do it?

The only sensors that are fully supported by Raspberry Pi are the OV5647, IMX219, and IMX477.
All other sensors that have drivers and overlays in our kernel tree for are for modules made by 3rd parties and for which the drivers are either supported by the 3rd party (eg IMX519 and IRS1125), are in the mainline Linux kernel, or have been put together by Raspberry Pi as basic drivers.
If you buy any other sensor from a 3rd party, then you should expect that vendor to also supply drivers.
I've already pointed you at the directories that have the files for the supported sensors. If a sensor is not mentioned in those directories then there is no support for them.


increase domain size and timestep for some diagnostic edmf case

Purpose

To-do

Content

[ ] I have read and checked the items on the review checklist.

bors r+

bors r+

bors r+

bors r+

bors r+


convert examples to doctests

🚀 Feature
Converting examples to doctests...
Motivation
The examples now are static so there is no guarantee that they are still valid...
Advantages of converting to doctest would:

increase reproducibility
each example can run as a stand-alone
make testing on smaller units
smaller test units simplify debugging

Additional context

https://docs.python.org/3/library/doctest.html
https://thomas-cokelaer.info/tutorials/sphinx/doctest.html
https://stackoverflow.com/questions/361675/python-doctest-vs-unittest

I would say to use doctest for small functionalities where we want to use it also as examples in docs and unittest for extension testing, for example, catching fail cases or running multiple edge test-cases

I can keep working on this if you like.

just pls do it by small pieces as you started so it is easier to merge / less potential conflicts to resolve lol

Many of the examples in LightningModule are just a method, something like this:
def training_epoch_end(self, outputs):
    train_acc_mean = 0
    for output in outputs:
        train_acc_mean += output['train_acc']

    train_acc_mean /= len(outputs)

    # log training accuracy at the end of an epoch
    results = {
        'log': {'train_acc': train_acc_mean.item()}
    }
    return results

Should we doctest this or not? Basically it would only do syntax check in this case, nothing else. What do you think?

just adding a reminder here that we may want to enable doctest for .rst files. (comment)
make doctest currently raises many import errors


Not working for docker stack projects

I have a project using the "basic" stack template. When I build it with
docker:
  enable: true

in my stack.yaml file intero stops working. Turning off docker support, deleting .stack-work and rebuilding and intero starts working again.
This is using the latest Docker for Mac with intero 0.1.18 for reference.

Here's some logs from the docker containers when intero is booted up.
Configuring GHCi with the following packages: distributed-systems
Intero 0.1.18 (GHC 7.10.3)
Type :intro and press enter for an introduction of the standard commands.
2016-10-02T11:29:56.646518707Z
2016-10-02T11:29:57.800842691Z
<no location info>:
    can't find file: /var/folders/y1/_sd9mpx526j25qk9546fdz_c0000gn/T/intero14547Icw.hs
> > Failed, modules loaded: none.
2016-10-02T11:30:00.031501949Z
<no location info>:
    can't find file: /var/folders/y1/_sd9mpx526j25qk9546fdz_c0000gn/T/intero14547Icw.hs
Failed, modules loaded: none.
Couldn't guess that module name. Does it exist?

Also, every time I restart intero a new docker container is being created not sure if this is intended behaviour.

Just another update, I can confirm that these /var/folders paths are present on my host Mac filesystem but the Docker containers running intero are failing to find them as they don't exist within the container

Does stack ghci work?

Yes just the basic stack ghci works as expected. Sorry I should clarify this is using the simple template not basic as I said before but applies to any project. I've also noticed this while using the stack-build container for LTS 7.3 as well as LTS 6.19 so it doesn't appear to be LTS specific.

I'm having this problem too, for this file: /var/folders/xz/99z8msbn5_s_c8prs1x5h5hr0000gn/T/intero18946_Ms.hs
If it's a docker project, why should intero require anything from the host?  I would think, as stack installs itself in the container, that intero would as well.

So, I believe that Stack (with that Docker flag) forwards all Stack commands (reinvokes with Docker exec) to another Stack executable in the container.
It looks like Intero (Emacs client) is writing changes to working buffer in a temporary file since #248, and clearly the container won't have this path.
I think a solution would be to put the temporary file in the Project directory (perhaps $PROJECT/.intero ?) or in the .stack directory

@shanemikel Good point, and I think your solution makes sense.

@chrisdone @shanemikel @houli I believe the changes I've submitted in #293 should address this successfully - please take a look and comment there if you have feedback.

@purcell Unfortunately there still seems to be problems after the merge of your PR.
Using main module: 1. Package `test' component exe:test with main-is file: /Users/eoinhoulihan/Desktop/test/src/Main.hs
Configuring GHCi with the following packages: test
Intero 0.1.18 (GHC 7.10.3)
Type :intro and press enter for an introduction of the standard commands.
2016-10-20T11:45:32.107848570Z
Prelude> Prelude> [1 of 1] Compiling Main             ( /Users/eoinhoulihan/Desktop/test/.stack-work/intero/intero16061AUn.hs, /var/folders/y1/_sd9mpx526j25qk9546fdz_c0000gn/T/intero16061Net/Main.o )
*** Exception: /var/folders: createDirectory: permission denied (Permission denied)
[1 of 1] Compiling Main             ( /Users/eoinhoulihan/Desktop/test/.stack-work/intero/intero16061AUn.hs, /var/folders/y1/_sd9mpx526j25qk9546fdz_c0000gn/T/intero16061Net/Main.o )
*** Exception: /var/folders: createDirectory: permission denied (Permission denied)
Couldn't guess that module name. Does it exist?
Couldn't guess that module name. Does it exist?

Hmm. I think that just means that the further changes mentioned in #293 will be necessary after all. I can probably get to that over the weekend and report back. :-)

@houli #296 should address that too.

Working now with the merge of #296

@houli Awesome, thanks for confirming!


Add footer to every page, also there is a bug in contact page

Hey! I would like to add footer on every page for better user experience. Also, there is a bug in contact us page where first name field is repeated.
Here is the screenshot 👇

Assign this issue to me under hactobesfest

It's great having you contribute to Milan ! This is an auto-generated textThe maintainers/owner will look into the issue soon, add relevant tags and proceed further, please have paitence. Meanwhile feel free to support star the repo and share it with your friends. :nerd_face: :rocket:

Hey @IAmTamal can you assign this to me?

@snehafarkya No  need to fix the bug for contact page, someone else is already working on that.


Slightly increase drop target sizing on form builder

Story:
As a configurator, I want an enhanced drag-and-drop experience when adding components to busy screens or moving them within a form. The current drop targets are challenging, leading to difficulties in accurately placing components, especially in crowded layouts.
Acceptance Criteria:

As a user dragging a component, I should experience improved accuracy in dropping it onto busy screens or different parts of a form.
The drop target for components should have increased top and bottom margins, making it easier to precisely position the component within a container, panel, or column.
The drag-and-drop functionality should respond smoothly and consistently without instances of components resisting movement.

Additional Information:

Configurator feedback highlights challenges in adding components to busy screens or moving them within a form, with some users finding it "impossible" in certain scenarios.
Replicating the issue involves creating a form with a container, panel, columns, and multiple text or number fields.
The proposed solution is to double the top and bottom margins of drop targets to significantly improve the ease of accurately placing components.

Definition of Done:

Drop targets for components are updated to include increased top and bottom margins.
The drag-and-drop behavior is tested thoroughly to ensure a smoother and more precise experience.
Configurator feedback indicates improved usability in placing components within complex layouts.

See the attached  below

It will be addressed by the zooming item #631


Bug: Files stops responding while loading network share content

Description
Files gets stuck / unresponsive or crashes when a network share is not available.

If it gets just stuck it will show an "Network folder error" after a while, this timeout is way to long.
Its the same behavior for windows explorer, would be great if this can be fixed in Files by reducing the timeout.
Steps To Reproduce
Have a network folder like an SMB share.
Disconnect from network.
Try to access the network folder.
Requirements

To make it crash click on other tabs while it is trying to access the drive that is not available.

Files Version
<IP_ADDRESS>
Windows Version
10.0.22621.3155
Log File
debug.log

@Josh65-2201 I already mentioned this problem but was dismissed. Even Windows Explorer doesnt work so poorly with network shares
Interaction with network SHOULD NOT freeze app as a whole, it should lock interaction with tab (folder/content) and do work in background
And even more to that look
It is trying to load every single file in location to display icons
Good luck loading few GBs with that speed while APP is unresponsive

I'm coming back to this app and every time it's just not usable itself not to say as replacement of Windows Explorer


Various fixus

Comment Sorting fix #325
New homepage cover
Pinned comments when logged out fix #340
Search bar switching fixed
Beatmap packs cached

also removed console logs which aren't used


Unable to Download(pdf and image) superset dashboard

Bug description
2024-11-07 18:31:29,234:INFO:superset.utils.screenshots:Attempting to get from cache: e82a8cd667ff78eb64d379e72b7b77e0
2024-11-07 18:31:29,234:INFO:superset.utils.screenshots:Failed at getting from cache: e82a8cd667ff78eb64d379e72b7b77e0
2024-11-07 18:31:29,241:DEBUG:superset.stats_logger:[stats_logger] (incr) DashboardRestApi.screenshot.warning
2024-11-07 18:31:29,242:DEBUG:superset.stats_logger:[stats_logger] (timing) DashboardRestApi.screenshot.time | 9.657113812863827
2024-11-07 18:31:29,242:INFO:werkzeug:<IP_ADDRESS> - - [07/Nov/2024 18:31:29] "GET /api/v1/dashboard/1/screenshot/e82a8cd667ff78eb64d379e72b7b77e0/?download_format=pdf HTTP/1.1" 404 -
I have installed superset in ec2 machine. I am getting this error in the logs.
Screenshots/recordings
No response
Superset version
master / latest-dev
Python version
3.11
Node version
I don't know
Browser
Chrome
Additional context
No response
Checklist

[X] I have searched Superset docs and Slack and didn't find a solution to my problem.
[X] I have searched the GitHub issue tracker and didn't find a similar bug report.
[X] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

@rusackas can you please help me on this. I am able to download the charts but when i am downloading the dashboard its not downloading

@dosu can you please assign some one for the same

@rusackas can you please help me on this

Not sure why you're calling me out personally on this one so often... I have no idea, and there's certainly not enough info on this ticket to say if it's a reproducible bug, rather than a config issue. You don't say how you installed Superset, what steps you followed, or where docs fell short.
I would join slack and try the #deloying-superset channel, or even #ask-ai. Alternatively, you can sidestep the problem by using a hosted solution.

@rusackas Whenever i ask for help from a maintainer the dosu bot throws your id.. So tagged you here. I have installed superset on EC2 machine and when i am trying to download the dashboard this error is showing in the logs:
2024-11-07 18:31:29,234:INFO:superset.utils.screenshots:Attempting to get from cache: e82a8cd667ff78eb64d379e72b7b77e0
2024-11-07 18:31:29,234:INFO:superset.utils.screenshots:Failed at getting from cache: e82a8cd667ff78eb64d379e72b7b77e0
2024-11-07 18:31:29,241:DEBUG:superset.stats_logger:[stats_logger] (incr) DashboardRestApi.screenshot.warning
2024-11-07 18:31:29,242:DEBUG:superset.stats_logger:[stats_logger] (timing) DashboardRestApi.screenshot.time | 9.657113812863827
2024-11-07 18:31:29,242:INFO:werkzeug:<IP_ADDRESS> - - [07/Nov/2024 18:31:29] "GET /api/v1/dashboard/1/screenshot/e82a8cd667ff78eb64d379e72b7b77e0/?download_format=pdf HTTP/1.1" 404 -

@michael-s-molina can you please help me on this.

Hi @krishanthvs. Given that this seems like a configuration issue, I can point you to some resources that might help:

Read this PR to understand the difference between sync and async screenshot generation
Make sure you're using the sync version (ENABLE_DASHBOARD_SCREENSHOT_ENDPOINTS and ENABLE_DASHBOARD_DOWNLOAD_WEBDRIVER_SCREENSHOT are False)
Use a stable release 4.1.1 instead of master

Hi @michael-s-molina I changed the feature flags true still its showing the same error

2024-12-06 16:29:49,351:INFO:superset.dashboards.api:Triggering screenshot ASYNC
2024-12-06 16:29:49,558:INFO:superset.utils.screenshots:Attempting to get from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:29:49,559:INFO:superset.utils.screenshots:Failed at getting from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:29:52,783:INFO:superset.utils.screenshots:Attempting to get from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:29:52,783:INFO:superset.utils.screenshots:Failed at getting from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:29:55,909:INFO:superset.utils.screenshots:Attempting to get from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:29:55,910:INFO:superset.utils.screenshots:Failed at getting from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:29:59,055:INFO:superset.utils.screenshots:Attempting to get from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:29:59,055:INFO:superset.utils.screenshots:Failed at getting from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:02,238:INFO:superset.utils.screenshots:Attempting to get from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:02,239:INFO:superset.utils.screenshots:Failed at getting from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:05,363:INFO:superset.utils.screenshots:Attempting to get from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:05,363:INFO:superset.utils.screenshots:Failed at getting from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:08,510:INFO:superset.utils.screenshots:Attempting to get from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:08,511:INFO:superset.utils.screenshots:Failed at getting from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:11,640:INFO:superset.utils.screenshots:Attempting to get from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:11,640:INFO:superset.utils.screenshots:Failed at getting from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:14,776:INFO:superset.utils.screenshots:Attempting to get from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:14,777:INFO:superset.utils.screenshots:Failed at getting from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:17,945:INFO:superset.utils.screenshots:Attempting to get from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:17,945:INFO:superset.utils.screenshots:Failed at getting from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:21,078:INFO:superset.utils.screenshots:Attempting to get from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:21,079:INFO:superset.utils.screenshots:Failed at getting from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:24,224:INFO:superset.utils.screenshots:Attempting to get from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:24,225:INFO:superset.utils.screenshots:Failed at getting from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:27,651:INFO:superset.utils.screenshots:Attempting to get from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:27,651:INFO:superset.utils.screenshots:Failed at getting from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:30,790:INFO:superset.utils.screenshots:Attempting to get from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:30,790:INFO:superset.utils.screenshots:Failed at getting from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:33,907:INFO:superset.utils.screenshots:Attempting to get from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:33,907:INFO:superset.utils.screenshots:Failed at getting from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:37,058:INFO:superset.utils.screenshots:Attempting to get from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:37,058:INFO:superset.utils.screenshots:Failed at getting from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:40,187:INFO:superset.utils.screenshots:Attempting to get from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:40,187:INFO:superset.utils.screenshots:Failed at getting from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:43,319:INFO:superset.utils.screenshots:Attempting to get from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:43,319:INFO:superset.utils.screenshots:Failed at getting from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:46,456:INFO:superset.utils.screenshots:Attempting to get from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:46,457:INFO:superset.utils.screenshots:Failed at getting from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:49,622:INFO:superset.utils.screenshots:Attempting to get from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:49,622:INFO:superset.utils.screenshots:Failed at getting from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:52,738:INFO:superset.utils.screenshots:Attempting to get from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:52,738:INFO:superset.utils.screenshots:Failed at getting from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:55,888:INFO:superset.utils.screenshots:Attempting to get from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:55,888:INFO:superset.utils.screenshots:Failed at getting from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:58,979:INFO:superset.utils.screenshots:Attempting to get from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:30:58,979:INFO:superset.utils.screenshots:Failed at getting from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:31:02,122:INFO:superset.utils.screenshots:Attempting to get from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:31:02,122:INFO:superset.utils.screenshots:Failed at getting from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:31:05,271:INFO:superset.utils.screenshots:Attempting to get from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:31:05,271:INFO:superset.utils.screenshots:Failed at getting from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:31:08,406:INFO:superset.utils.screenshots:Attempting to get from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:31:08,406:INFO:superset.utils.screenshots:Failed at getting from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:31:11,534:INFO:superset.utils.screenshots:Attempting to get from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:31:11,534:INFO:superset.utils.screenshots:Failed at getting from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:31:14,658:INFO:superset.utils.screenshots:Attempting to get from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:31:14,658:INFO:superset.utils.screenshots:Failed at getting from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:31:17,820:INFO:superset.utils.screenshots:Attempting to get from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:31:17,820:INFO:superset.utils.screenshots:Failed at getting from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:31:20,970:INFO:superset.utils.screenshots:Attempting to get from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:31:20,971:INFO:superset.utils.screenshots:Failed at getting from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:31:24,563:INFO:superset.utils.screenshots:Attempting to get from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47
2024-12-06 16:31:24,563:INFO:superset.utils.screenshots:Failed at getting from c                                                                                ache: 3e2d616d80b472d33efc0d2bf905bd47

@michael-s-molina Its doing download in async. How to do it in sync.

@michael-s-molina Its doing download in async. How to do it in sync.

Make sure you're using the sync version (ENABLE_DASHBOARD_SCREENSHOT_ENDPOINTS and ENABLE_DASHBOARD_DOWNLOAD_WEBDRIVER_SCREENSHOT are False)

👆🏼

Hi @michael-s-molina I changed the feature flags true still its showing the same error

The feature flags should be FALSE not true

2024-12-06 16:29:49,351:INFO:superset.dashboards.api:Triggering screenshot ASYNC

@krishanthvs If the above line is in your logs, it means that there's something wrong with your configuration and the feature flag is not being applied.

@krishanthvs
I am also facing the same issue, have you found any solution for this?


Add jsdoc to public interfaces

This PR adds JSDoc style comments to the public interfaces. I think this can allow us to provide far better documentation that we currently have in the readme and generate a website for all the documentation (minim, minim-api-description, minim-parse-result) eventually. Especially using sphinx-js. This pull request is the "first step" which is to add JSDoc comments, they're not perfect and could be iterated on in the future but I think this is a good start.
The jsdoc npm package can be used to generate a website locally, all of the types are hyperlinked.
$ npm install -g jsdoc
$ jsdoc lib/**.js
$ open out/index.html

Here's just a preview of one method:

Not sure whether 100% docs coverage was an intent, but that's what @tjanc already pointed out.

Yes, 100% perfect docs wasn't the intention. Just trying to get this started, I have made a lot of improvements since the review. I think this should be good to go as-is.


SSD cannot be found

Most of the time, after upgrading and re-updating my alias for LND, I have to disable the UAS protocol so Umbrel can see my SSD, ....I use the following command.
sed -i 's/  blacklist_uas/  #blacklist_uas/g' /home/umbrel/umbrel/scripts/umbrel-os/external-storage/mount
I was given this command by one of the guys that was working on the project previously.  Is it possible to fix this so I don't have to run this command and then reboot afterwards?

Ugh. I was trying to figure out why my SSD wasn't loading, and why it did before. Before, I manually mounted my SSD, which bypassed all the umbrel OS scripts. Then, I decided to start fresh and let Umbrel OS manage my storage. I had no idea why I was getting the following error when it worked perfectly before:
It seems that this blacklist function is not ready for primetime??

Are you using the official Raspberry Pi power supply and the reccomended SSD and enclosure on our website?
The Pi has underpowered USB ports and can be very unreliable with certain combinations. Blacklisting the UAS drivers offers significantly improved stability but only under most hardware we've tested. But some combinations of hardware can still have issues.

No I am using the 5.1v 3.5a power supply that came with the Canakit Raspberry Pi 4 set up kit.
The hard drive is Crucial X6 1TB Portable SSD - Up to 540 MB/s - USB 3.2 - External Solid State Drive, USB-C - CT1000X6SSD9
I think this combination works fine, in fact I've been hammering it with experiments to debug https://github.com/getumbrel/umbrel/issues/1077 and it's been rock solid
The black list script was kind of like a hidden gotcha.
How would you feel about prompting the user at start up that their configuration is unsupported and to proceed with caution?

We've had a huge amount of reports from users experiencing problems with the Canakit power supplies. Would strongly advise changing to the official Raspberry Pi power supply.

How would you feel about prompting the user at start up that their configuration is unsupported and to proceed with caution?

It's a nice idea although I think it could cause some confusion for non-technical users, when there hardware config may work well even if it's non-standard. It would also mean maintaining and constantly updating a list of supported/unsupported hardware which was the problem we had before when we were manually disabling UAS for certain devices and then decided to stop doing that and just blanket disable for all devices.

Same issue: hard drive Crucial X6 1TB Portable SSD - Up to 540 MB/s - USB 3.2 - External Solid State Drive, USB-C - CT1000X6SSD9
I've changed my power supply...and that's it! Awesome! All works very nice


Clarified installing CUDNN front-end headers and arch linux install instructs

Clarified instructions for installing CUDNN and front-end headers. Added cudnn installation steps for Arch Linux.

I don't want to bloat the main README file too much. Maybe we can have extra helpful instructions inside our doc/ folder and link to it or something


Unable to MFA on aws-azure-login using MS Authenticator app

The recent changes to the Microsoft Authenticator app have made it difficult to authenticate when using the aws-azure-login container or without a GUI mode. This is because the MS MFA process now requires users to enter a number displayed on the screen in the authenticator app to validate. However, the terminal does not have a GUI mode and therefore unable to see the number and cannot complete the MFA process.
 docker run --rm -it -v ~/.aws:/root/.aws sportradar/aws-azure-login
 Logging in with profile 'default'...
 Using AWS SAML endpoint https://signin.aws.amazon.com/saml
 Username: EnterUsername
 Password: [hidden]
 Open your Authenticator app, and enter the number shown to sign in.

After a brief period, although I don't see any numbers displayed on the terminal
We sent an identity verification request to your mobile device, but you denied it.

The profile setting for MFA is

Default sign-in method: Authenticator app or hardware token - code

I have since tried using Twilio Authy as my MFA app and it works fine. But however, the organization standard is MS Authenticator and therefore I would like to know if there are any workarounds for this issue.

MS has rolled out changes, it happened in my Org also

This program is useless now, if its not updated than we need to find other solution
https://learn.microsoft.com/en-us/azure/active-directory/authentication/how-to-mfa-number-match
"Beginning May 8, 2023, number matching is enabled for all Authenticator push notifications. As relevant services deploy, users worldwide who are enabled for Authenticator push notifications will begin to see number matching in their approval requests. Users can be enabled for Authenticator push notifications either in the Authentication methods policy or the legacy multifactor authentication policy if Notifications through mobile app is enabled."

Still working OK, using the Node module installed locally in an NVM bin:
[~]$ ./node_modules/.bin/aws-azure-login --no-sandbox --profile production
(node:28873) NOTE: We are formalizing our plans to enter AWS SDK for JavaScript (v2) into maintenance mode in 2023.

Please migrate your code to use AWS SDK for JavaScript (v3).
For more information, check the migration guide at https://a.co/7PzMCcy
(Use `node --trace-warnings ...` to show where the warning was created)
Unknown profile 'production'. You must configure it first with --configure.
[~]$ ./node_modules/.bin/aws-azure-login --no-sandbox --profile production --configure
Configuring profile 'production'
(node:28900) NOTE: We are formalizing our plans to enter AWS SDK for JavaScript (v2) into maintenance mode in 2023.

Please migrate your code to use AWS SDK for JavaScript (v3).
For more information, check the migration guide at https://a.co/7PzMCcy
(Use `node --trace-warnings ...` to show where the warning was created)
? Azure Tenant ID: **TENANT**
? Azure App ID URI: https://signin.aws.amazon.com/saml#3
? Default Username: **EMAIL**
? Stay logged in: skip authentication while refreshing aws credentials (true|false) true
? Default Role ARN (if multiple): **ROLE**
? Default Session Duration Hours (up to 12): 8
Profile saved.
[~]$ ./node_modules/.bin/aws-azure-login --no-sandbox --profile production
(node:31472) NOTE: We are formalizing our plans to enter AWS SDK for JavaScript (v2) into maintenance mode in 2023.

Please migrate your code to use AWS SDK for JavaScript (v3).
For more information, check the migration guide at https://a.co/7PzMCcy
(Use `node --trace-warnings ...` to show where the warning was created)
Logging in with profile 'production'...
Using AWS SAML endpoint https://signin.aws.amazon.com/saml
? Password: [hidden]
Open your Authenticator app, and enter the number shown to sign in.
95
Assuming role **ROLE**

I had no end of trouble until I worked out the right app ID URI to use - https://signin.aws.amazon.com/saml#3

Still working OK, using the Node module installed locally in an NVM bin:
[~]$ ./node_modules/.bin/aws-azure-login --no-sandbox --profile production
(node:28873) NOTE: We are formalizing our plans to enter AWS SDK for JavaScript (v2) into maintenance mode in 2023.

Please migrate your code to use AWS SDK for JavaScript (v3).
For more information, check the migration guide at https://a.co/7PzMCcy
(Use `node --trace-warnings ...` to show where the warning was created)
Unknown profile 'production'. You must configure it first with --configure.
[~]$ ./node_modules/.bin/aws-azure-login --no-sandbox --profile production --configure
Configuring profile 'production'
(node:28900) NOTE: We are formalizing our plans to enter AWS SDK for JavaScript (v2) into maintenance mode in 2023.

Please migrate your code to use AWS SDK for JavaScript (v3).
For more information, check the migration guide at https://a.co/7PzMCcy
(Use `node --trace-warnings ...` to show where the warning was created)
? Azure Tenant ID: **TENANT**
? Azure App ID URI: https://signin.aws.amazon.com/saml#3
? Default Username: **EMAIL**
? Stay logged in: skip authentication while refreshing aws credentials (true|false) true
? Default Role ARN (if multiple): **ROLE**
? Default Session Duration Hours (up to 12): 8
Profile saved.
[~]$ ./node_modules/.bin/aws-azure-login --no-sandbox --profile production
(node:31472) NOTE: We are formalizing our plans to enter AWS SDK for JavaScript (v2) into maintenance mode in 2023.

Please migrate your code to use AWS SDK for JavaScript (v3).
For more information, check the migration guide at https://a.co/7PzMCcy
(Use `node --trace-warnings ...` to show where the warning was created)
Logging in with profile 'production'...
Using AWS SAML endpoint https://signin.aws.amazon.com/saml
? Password: [hidden]
Open your Authenticator app, and enter the number shown to sign in.
95
Assuming role **ROLE**

I had no end of trouble until I worked out the right app ID URI to use - https://signin.aws.amazon.com/saml#3

This is clearly not using the aws-azure-login container image.

The recent changes to the Microsoft Authenticator app have made it difficult to authenticate when using the aws-azure-login container or without a GUI mode.

This is, however, clearly using the module without a GUI. It works. If it's only the Docker image you're concerned with then you need to state that.

from what i tested it seems that issue is only on some mobile devices, seen issue with Pixel and Xiaomi, Samsung was able to work without gui in CLI mode and presented 2 digits and passed the push notification.

I had the same issue in docker on WSL2 following the number matching being enabled on Authenticator in that the docker container doesn't display the number for the authentication process. As I'm on Windows 11, Linux GUI apps are enabled by default to am able to use X passthrough using the following (in case it helps anyone else):
docker run --rm -it -v ~/.aws:/root/.aws -e DISPLAY="$DISPLAY" -v /tmp/.X11-unix:/tmp/.X11-unix sportradar/aws-azure-login --profile=production --mode gui

@gfrid the application itself supports the MFA number check, per #266, but when this project was rebranded from sportradar to this org, they didn't keep up with publishing new Docker images. A maintainer in #266 asked for a PR to fix the Docker build, so I opened #304 with the changes that let me build an image locally to get unblocked, but it appears nobody is maintaining this repo any more. Though @dys152 solution of mounting the X socket to do GUI mode is pretty snazzy, that sportradard/aws-azure-login image is using old version of the application code.


Add get, getAll, put, post, delete handler access for before @ after handlers

[ ] before
[ ] after
[ ] beforeAll
[ ] afterAll

This looks like it was already implemented... nice, sleep coding is the best... gonna test.

wasn't working right. Added better testing and fixed the issues. before / after on @Route method's now supports built in handler functionality, so long as @Routable has a model bound to it.


run_once dont stop sidekicks

I've the following scenario
atena-cli:
    image: registry.pedro.com/atena:latest
    tty: true
    stdin_open: true
    labels:
        io.rancher.container.pull_image: always
    command: cat

cli:
    image: registry.pedro.com/laravel-cli
    labels:
        io.rancher.container.pull_image: always
        io.rancher.sidekicks: atena-cli
        io.rancher.scheduler.affinity:host_label: server=11
        io.rancher.container.start_once: true
    volumes_from:
        - atena-cli
    links:
        - postgres
    command: php /data/www/artisan migrate --force

The cli service works fine, it runs once and them die but the sidekick atena-cli keeps running and using resources. In my opinion, it should stop like the "parent" container.

Each service in the docker-compose.yml is individually defined. By adding a sidekick, it's just providing information to Rancher on how the services need to be launched together on the same host (to be able to handle the volumes_from). Therefore, if you want each service to run only once, then you'd need to add the label to the atena-cli service.
There are many scenarios where people have sidekicks that they only want to run once, but their "parent" container will keep running.
Therefore, a sidekick will never interpret the labels of the "parent" container.


Hidden-drawer-bar issue

Made a hidden-drawer-bar template app

Sir, earlier it had some git file problems but now I have fixed it. also added a screenshot in Read.md file

Issue #12

Sir, earlier it had some file problems when I uploaded it on GitHub but now I have fixed it and also updated the Readme file.

You have done great work @sekocoder 👍👍
Keep it up ☺