[BUG] Server initialization failed with out of memory

Describe the bug
Server initialization failed with out of memory
To Reproduce
Do not know I opened the workspace
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Logs
<--- Last few GCs --->

[572188:0x3c58002f0000]      192 ms: Mark-Compact (reduce) 0.6 (2.9) -> 0.6 (1.7) MB, 5.31 / 0.00 ms  (average mu = 0.058, current mu = 0.021) last resort; GC in old space requested
[572188:0x3c58002f0000]      196 ms: Mark-Compact (reduce) 0.6 (1.7) -> 0.6 (1.7) MB, 3.67 / 0.00 ms  (average mu = 0.036, current mu = 0.006) last resort; GC in old space requested

<--- JS stacktrace --->

#
# Fatal JavaScript out of memory: CALL_AND_RETRY_LAST
#

[Error - 9:20:01 AM] Server initialization failed.
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Info  - 9:20:01 AM] Connection to server got closed. Server will restart.
true
[Error - 9:20:01 AM] Red Hat Dependency Analytics Server client: couldn't create connection to server.
  Message: Pending response rejected since connection got disposed
  Code: -32097

VSCode(please complete the following information):

OS: Fedora
VSCode version 1.89.1
Dependency Analytics Version 0.9.4

CHE7/Theia(please complete the following information):

OS: [e.g. macOS]
Browser [e.g. chrome]
CHE/Theia version
Dependency Analytics Version [e.g. 0.0.22]

Additional context
Add any other context about the problem here.

Hi @apupier ,
Thank you for reporting this issue,
Could you please share your manifest file so that we can attempt to reproduce the issue you are having?

closing this issue due to inactivity, please feel free to reopen necessary.


Ability to resize the views

It would be nice to be able to resize the views (node view and table view)

Another thing to note: Resizing the aboutcode-manager application window expands the table view correctly, but in the node view, the viewport window size stays static. See the attached picture:

You can see from this image that the node-view viewport x-axis does not extend with the application window. Additionally, the node-view viewport y-axis also stays static regardless of window size.

@jdaguil When we speak of resizing the node view and table view, I take that to mean creating a vertical divider between the tree view and the node/table views, which the user can drag to the left or the right, altering the size of the views on either side of the divider.  Is that correct?

@johnmhoran Yes, that's the basic idea. Possibly a vertical slider because the user needs to be able to grab something to resize it, but other options are also welcome.

Thanks @jdaguil .

@jdaguil  Brief update:
I've been working with the splitter (using Split.js), focused on displaying the Component Summary at full-width.  The issue: when the user selects the Component Summary View, the table is displayed at less than full-width, and the vertical splitter (known as the gutter) remains visible on the left side of the screen.  I don’t yet have a complete solution, but I have an idea (see last paragraph).
To create an instance of split.js, we identify the divs we want to split horizontally and provide several other settings including the relative percentage widths (these would be heights for a vertical split) of the divs, e.g.,
    const instance = Split(['#leftCol', '#tabbar'], {
        sizes: [18, 76],
        minSize: 200,
        gutterSize: 5
    });

When the user resizes the divs, split.js “remembers” the widths of the divs.  And therein lies the challenge.
To display the Component Summary full-width, we need to expand the div in which the Component Summary sits -- the tabbar div -- when the user selects the Component Summary view.  I have figured out how to set a nice wide width when the user selects the Component Summary view, but because this is the same div in which the Table View and the Node View are located, changing the tabbar div width for the Component Summary View changes the tabbar div width that the Table and Node Views use when they are subsequently selected.
I’ve tried several approaches, including destroying and reinstantiating the splitter as different views are selected, but these approaches have been unsatisfactory.  I’ve also cloned the tabbar div and moved the Component Summary to this new renamed div, hiding and displaying it as necessary.  This had some beneficial effects -- including removing the unwanted gutter in the Component Summary View -- but also came with several bugs of its own.  For now that’s on the back burner.
Working with our current div structure, it occurs to me that I might be able to use local storage to store the correct widths for the Table and Node views (including any changes made when the user resizes), saving and retrieving the values as necessary.  I’m going to pursue this avenue unless you suggest otherwise.

@jdaguil Working on my next commit:
The Component Summary view now displays the DataTable at full-width without disturbing any resizing the user may have done to the Tree and Table/Node views.

We grab the splitter’s respective div widths (for the Tree and Table/Node views) each time the user resizes and save the widths as JSON in HTML5 local storage.
When a user navigates to the Component Summary view, the vertical splitter (the gutter) is no longer visible (we change its CSS) and we apply a different div-width setting.
When the user returns to the Table/Node views, we again change the gutter CSS to make it visible and retrieve and apply the div widths from local storage or, if there are none, we apply the default config.

On Windows 10 (not yet tested on Ubuntu 16.04), local storage persists across browser sessions and reboots, so by default any saved resizing will be applied when the user relaunches AboutCode Manager.

I’ve also created the option to clear any saved resizing when AboutCode Manager is closed, in which case on launch the default splitter div widths are applied.
For now, that option is available only as hard-coded, though we could create a configuration page/modal where the user could select a radio button: save/don’t save resizing.  (We might want to use local storage for other user config options as well.)

Question: Unless/until we provide the option to the user, do you prefer (a) persisting saved resizing or (b) clearing saved resizing when AboutCode Manager is closed?
BTW, I’ve added split.js to assets/js/ and we now call that copy in index.html (rather than from node_modules . . .).  I’ll add .ABOUT and .LICENSE files in a separate commit.

@johnmhoran IMHO, I would clear it. The position of the splitter depends on what you are displaying, and when you restart the app you are not displaying data yet. In the future, if it's decided to save more of the app state (i.e. you open the app with the previous file, tab, and search saved), then it might make sense to save the slider position at that time.

Excellent, will do.  Thanks @jdaguil .

Awesome! 👍


Depot: Domains table, only Name and Description columns sortable

All other columns do nothing when clicking on the sort filter for the column heading.  I initially thought this may have been caused by those columns containing items displayed as labels, but the item count one isn't a label and also fails.

fixed

Fixed indeed...


Keepalive support

Hi,
I'm using crowbar_1.0.0. Works like a charm, but tunnels use to hang after a long time.
Is there some kind of keepalive and reconnection implemented in this version?

BTW, thanks for writing and releasing this wonderful tool.


[Feature][seatunnel-e2e] Add a container module to simplify spark-e2e and flink-e2e

Search before asking

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

Description
Containers are using in spark-e2e and flink-e2e. Now, there are some duplicate codes. We can manage containers in project, then using them in e2e.
Usage Scenario
No response
Related issues
No response
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

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

Duplicated with #2733


AMBARI-24958 Ambari YARN Queue Manager allows duplicate names when using rename functionality (asnaik)

AMBARI-24958 Ambari YARN Queue Manager allows duplicate names when using rename functionality (asnaik)
What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
How was this patch tested?
(Please explain how this patch was tested. Ex: unit tests, manual tests)
(If this patch involves UI changes, please attach a screen-shot; otherwise, remove this)
Please review Ambari Contributing Guide before opening a pull request.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/4640/
Test PASSed.


docs: use z.coerce.date()

Assuming a newish version of ZOD is used, this short hand is a lot easier to understand.

Update: This is not true. It will not work with my suggested change => closing.
Wondering though… why :-)

I think it depends on the format your date is in. I have used z.coerce.date() successfully in some projects — but in others even a straight z.date() can work as YAML parses certain things as dates.


feat: dtos for form create & update API

Date:  27/01/2024

Developer Name: Vinayak Goyal

Issue Ticket Number
closes #20
Description
Created DTOs for the PATCH and POST request for the forms.
Documentation Updated?

[ ] Yes
[x] No

Under Feature Flag

[ ] Yes
[x] No

Database Changes

[ ] Yes
[x] No

Breaking Changes

[ ] Yes
[x] No

Development Tested?

[x] Yes
[ ] No

Test Coverage

Screenshot 1

@yesyash , @ivinayakg  quick question- don't we need trackage objects like createdby, updatedby ............


Stack multiple terminal outputs into one entry with count

Right now if you print out the same message multiple times in a sequence - godot will print out the same line multiple times - easily leading to output overflow and making it harder to find printouts
A solution that many other consoles share to this problem is to stack a sequence of the same message into one line and simply show with a number how many times it has been emited:

It would be very helpful - especially for anything emited from an update function or multiple instances of a node and would greatly reduce printout noise

My project could really use this, as we're using Godot on our server side, and quite often the logs get flooded so much, that they become tens of gigabytes big, which is completely unacceptable.
If nothing is done about this anytime soon, we will be left no choice but to use something else for the server...
Don't take this as a threat :grin: , but seriously, I don't think this issue is getting the attention it's supposed to get.

@PonasKovas Couldn't this be solved by implementing a custom logger in GDScript on the server-side?
Since we're talking about dedicated servers, you could even output log in a JSON format to parse it in third-party software like Loki.

@Calinou Most of the time, the built-in errors printed by Godot are the ones that flood everything. And we still want to see those errors, because of debugging, so redirecting the to /dev/null won't work for us.

@PonasKovas I don't really see how message stacking can be achieved in a pure command-line fashion though. A few other solutions I can see are:

Use a built-in timer to prevent error message spam. This could still cause useful information to be lost.
Set up a log rotation and compression facility. This should be done by the system administrator.

@Calinou

I don't really see how message stacking could be achieved in a pure command-line fashion though

I think this can be achieved with carriage returns. AFAIK they should work on Windows too.
Basically don't add newlines at the end of outputs, and if something is about to be printed more than once, just add a carriage return \r at the beginning and the count at the end.
If it's being printed only once, add a newline at the beginning instead of a carriage return.
These are just my thoughts, there might be better solutions.

Feature and improvement proposals for the Godot Engine are now being discussed and reviewed in a dedicated Godot Improvement Proposals (GIP) (godotengine/godot-proposals) issue tracker. The GIP tracker has a detailed issue template designed so that proposals include all the relevant information to start a productive discussion and help the community assess the validity of the proposal for the engine.
The main (godotengine/godot) tracker is now solely dedicated to bug reports and Pull Requests, enabling contributors to have a better focus on bug fixing work. Therefore, we are now closing all older feature proposals on the main issue tracker.
If you are interested in this feature proposal, please open a new proposal on the GIP tracker following the given issue template (after checking that it doesn't exist already). Be sure to reference this closed issue if it includes any relevant discussion (which you are also encouraged to summarize in the new proposal). Thanks in advance!


winget search gives outdated package version

Brief description of your issue
winget search xxx
gives the outdated result. For example, I can manually check the newest version of  "Fndroid.ClashForWindows" on https://github.com/microsoft/winget-pkgs is 0.20.6,

however my search result only returns version 0.20.4

I guess the database does not update ? My winget source is https://cdn.winget.microsoft.com/cache, already tried
winget source reset --force
also tried to change source to https://winget.azureedge.net/cache but gives the same issue.
Steps to reproduce
winget search "clash for windows"
Expected behavior
return version 0.20.7
Actual behavior
return outdated version 0.20.4
Environment
Windows Package Manager v1.3.2691
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.22621.754
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.18.2691.0

Logs: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

https://github.com/microsoft/winget-pkgs/issues/86160

See https://github.com/microsoft/winget-pkgs/issues/86160
And now I can see updates
I close the issue.


TST: bump test precision for dual_annealing SLSQP test

This failure showed up on Windows with VS2017 + Ifort 2019, see
https://github.com/conda-forge/scipy-feedstock/issues/119
[ci skip]

okay this is the tiniest test precision bump, I'll just merge it straight away


additional param for linux docker-compose users

@freekmurze - hopefully this covers the linux side, let me know if you require further changes, this is my first PR on a public project  so open to critique :-)

Thank you! I don't have much Docker experience myself, so I'm going to merge this in optimistically.
We'll get some feedback from other docker users should something be wrong.

Thank you! I don't have much Docker experience myself, so I'm going to merge this in optimistically.
We'll get some feedback from other docker users should something be wrong.


Feature request: Option to not test for passive stealth

Thank you for your module! I was wondering if you could please include an option in the settings to stop testing for passive stealth. If there is already an option for this - I couldn't find it. I have a player and their PC has lost an eye. They have a disadvantage in perception now and it means that their passive is lower than 10. If the creature is not hiding, like an NPC - this player still won't see them. I know it is rules as written, probably, but I would love for him to not see enemies who are hiding and not just all creatures. Thank you for your kind work.

All of Stealthy's processing is based on finding a banked stealth roll on a token, so adding this feature would outside of the scope I currently envision for it. I'm glad the module has worked for you other than this, perhaps you can find some clever ways to use the 'limits' module to make some kind of workaround for your one-eyed PC?

Since you can override banked stealth/perception rolls in the Token HUD, you could try and give the NPCs a banked stealth roll. An actor's passive perception is an attribute tracked by the dnd5e system, perhaps there is an active effect you could add to lower the passive perception for the specific character to a value lower than the banked stealth you gave the NPCs.

I think that this can work. Thank you!

If you are comfortable writing a macro, you could automate the banking of the set value. stealthy.bankStealth(token,value) is all you need. Something like canvas.tokens.controlled.forEach((t) => stealthy.bankStealth(t, 5)) would do all selected tokens (not sure if I got the syntax right but something very close to that)

Thank you for the macro, will see if it works! Since we last spoke I've thought of another, much more common situation, where having default stealth at 0 (unless they roll for it) would be better. If you still think that this is not needed - ok then. I just want to make my case:
If any PC, at any point during combat/exploration on a map will have at least one level of exhaustion - they won't be able to see any NPCs, even their allied NPCs. No one is trying to be hidden in this example and it is not an edge-case, like in my one-eyed PC example.
Let me know what you think! I really do believe that this is a valuable feature.

Exhaustion gives dIsadvantage on ability checks which means that they would be using passive perception at a -5 penalty, it would take a house rule that says you don't see NPCs that aren't hiding if you have disadvantage on Perception. If your passive perception is 10, does it matter that it would have been a 15 without disadvantage in scene where nobody is hiding? I think I must be misunderstanding why exhaustion would make things undetected.
I'd also point you towards the Perceptive module, it has MANY more dials and knobs to control visibility between specific token - check out their Channel feature.


Do not update read_on if the metric is not present

graphite-web may still have a metric in its cache that have been deleted
in Cassandra. It will re-create the metric partially (every field to null
except name and read_on) when field 'read_on' is getting updated because
UPDATE and INSERT clauses in Cassandra behave like an UPSERT operation.
Adding 'IF EXISTS' makes sure that Cassandra won't create the metric if it
doesn't exists.

Coverage remained the same at 81.918% when pulling eb864b0a7fb29fda9d647d1ef8f2b495475ad3df on adriengentil:do-not-recreate-row-read-on into baab317254cf7c3368d9e66b9e05b2a131f9572e on criteo:master.

Be careful, IF EXISTS might be a bit more costly. (should be fine if only on the read path though)

Maybe we should add a test (the same kind of the one that should have been there to check that the metric is not partially written with every field to null except name and read_on)

Be careful, IF EXISTS might be a bit more costly. (should be fine if only on the read path though)

Tanks for pointing that out! Yes, that would be only on the read path and the update frequency for read_on is configurable.

Maybe we should add a test (the same kind of the one that should have been there to check that the metric is not partially written with every field to null except name and read_on)

Done


Councils need additional verification of address if Verify returns unverified address

Hi @sanjaypoyzer
This will need some refining, but can we add an additional step for LAs to ask for more information to establish eligibility for the service?
This should be an optional step that LAs could choose to display or not, depending on the information received from Verify, i.e. if the latest address is unverified.
Could you make the step look something like this:
Add eligibility details
To apply for a parking permit, you need to provide us with (at this point allow LAs which of these they want to request):

your vehicle registration document (V5C). The address has to match your residency address. If you have recently moved and have not updated your V5C, you can do it here.
proof of residency (tenancy agreement or utility bill). The document has to clearly show your name and address.
your council tax reference number

These documents can be uploaded as a scan or a photograph.
V5C  [Upload button]
Proof of residency [Upload button]
Council tax reference number [number validated field]

LA responses to unverified address Q (We previously shared with you the Changes of Address Guidance document. Please specify in the box below your service design approach to handling cases of an unverified address available and passed by the IDP):

We intend to handle the new unverified address and advise the user that providing false information may result in court action. Also, we post the parking permit to the users address.
we ask for v5 so we can check this matches the newly entered address
A - provide a short term access to a service
If a users identity is verified but their address is different we will accept this with no further proof as the physical permit will be posted to the home address only. No further address documents will be required.
we will offer a temporary permit for 3 months, after which the user will need to verify the new address or the permit will be cancelled

So when grouped together, the options are:

Accept with disclaimer
Verify with V5
Issue 3 month permit

The first two things are already in the prototype, so I'll just add an option for the issuing 3 month permits.

#Northumberland, we wouldn't issue a 3 month permit

@joanneSouthern - That list is a list of options that each council can turn on in the prototype individually.


gstreamer-1.0>=1.8;gstreamer-app-1.0>=1.8

when i install mediaplayer process,i face the issue and how to solve it?

what is the os version you use?

ubuntu 14.04

Hi there, can you please provide more details about the issue you're facing?

i build the media player process , to use "cmake  -DGSTREAMER_MEDIA_PLAYER=ON -DCMAKE_PREFIX_PATH="  ,and appear this issue 'gstreamer-1.0>=1.8;gstreamer-app-1.0>=1.8'

Hello captainpanther,
Sorry for the long delay in getting back to you.  That message indicates that you are attempting to build with a version of gstreamer that is less than the required minimum.  See: MediaPlayer Reference Implementation Dependencies.
Please let us know if this helps you or if you have already gotten past this problem.
Thank you,
-SWH

I'm going to go ahead and close this issue @captainpanther, since based on your other issues, it looks like you got past this step. Please reopen if that isn't the case.
Thanks,
Sanjay


⚠ ClamAV has degraded performance

In ccb9449, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 578 ms

Resolved: ClamAV performance has improved in 430e591.


[Bug]: rgba colours do not get applied correctly in Table widget

Is there an existing issue for this?

[X] I have searched the existing issues

Description
When colours in the form of rgba(0,0,0,0) are applied to the cell background of the table widget, we can see it does not get applied uniformly.
https://www.loom.com/share/f0e91b9cfa4b4fcebc785117732fe9ba

Steps To Reproduce

D&D a table widget.
For Cell Background Color property add any colour in the rgba(0,0,0,0) format.

Public Sample App
No response
Version
Cloud

The problem is not visible when the data is already added to the table. @shadabbuchh can you show an example with real user data on table v2?

@dilippitchika the issue seems to be resolved now. I am not able to reproduce it as on today.


How to calculate multi-label F1 score?

Hello all,
Assume I have more than 1 true label per image or video. How to calculate multi-label F1 using this module?
Check this reference to see how torchmetrics handle multi-label predictions: https://torchmetrics.readthedocs.io/en/stable/pages/classification.html#input-types
I have also created a HF Hub discussion:
https://huggingface.co/spaces/evaluate-metric/f1/discussions/2#62e3ab6ef3b208e2aed00a5a

Hi @fcakyon, I answered in the HF Hub discussion and close this for now.

Thanks opened a PR on hub: https://huggingface.co/spaces/evaluate-metric/f1/discussions/3


Windows Package Manager administrators is incomplete

@ryfu-msft is an administrator but I can't him anywhere in the list at P.S.A. Moderation. Please add him.

cc @denelon

Done.


dart:io memory leaks

standalone_2/io/file_test
standalone_2/io/http_server_response_test
standalone_2/io/signals_test
lib_2/isolate/non_fatal_exception_in_timer_callback_test/sleep

Tests failing due to memory leaks in vm-kernel-asan-linux-release-x64:
dartk-vm release_x64 lib_2/mirrors/dynamic_load_test
dartk-vm release_x64 standalone_2/io/http_server_response_test (4x)
dartk-vm release_x64 standalone_2/io/test_extension_fail_test
dartk-vm release_x64 standalone_2/io/file_test

For the future: When gardening and filing issues, please file as much information as possible:

a link to the buildbot failure
a copy of the failure (since the link will not work after a certain period of time)
what action was taken (e.g. was it debugged?, ...) except for filing an issue and updating the status file

At least one of these leaks are due to:
==31178==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 32 byte(s) in 1 object(s) allocated from:

STDERR :     #0 0x55fe9504cbe2 in operator new(unsigned long) /b/s/w/ir/kitchen-workdir/llvm-project/compiler-rt/lib/asan/asan_new_delete.cc:92:3
    #1 0x55fe95e8e7e8 in dart::VirtualMemory::AllocateAligned(long, long, bool, char const*) ../../out/DebugX64/../../runtime/vm/virtual_memory_linux.cc:89:10
    #2 0x55fe9644dd8f in dart::HeapPage::Allocate(long, dart::HeapPage::PageType, char const*) ../../out/DebugX64/../../runtime/vm/heap/pages.cc:63:27
    #3 0x55fe9644dd8f in dart::PageSpace::AllocatePage(dart::HeapPage::PageType) ../../out/DebugX64/../../runtime/vm/heap/pages.cc:231
    #4 0x55fe964509ce in dart::PageSpace::TryAllocateInFreshPage(long, dart::HeapPage::PageType, dart::PageSpace::GrowthPolicy, bool) ../../out/DebugX64/../../runtime/vm/heap/pages.cc:378:22
    #5 0x55fe9645f877 in dart::PageSpace::TryAllocateDataBumpInternal(long, dart::PageSpace::GrowthPolicy, bool) ../../out/DebugX64/../../runtime/vm/heap/pages.cc:1211:14

STDERR :     #6 0x55fe9645fbb0 in dart::PageSpace::TryAllocateDataBumpLocked(long, dart::PageSpace::GrowthPolicy) ../../out/DebugX64/../../runtime/vm/heap/pages.cc:1249:10
    #7 0x55fe9645fbb0 in dart::PageSpace::TryAllocatePromoLocked(long, dart::PageSpace::GrowthPolicy) ../../out/DebugX64/../../runtime/vm/heap/pages.cc:1261

STDERR :     #8 0x55fe9647bce5 in dart::ScavengerVisitor::ScavengePointer(dart::RawObject**) ../../out/DebugX64/../../runtime/vm/heap/scavenger.cc:150:26
    #9 0x55fe9647bce5 in dart::ScavengerVisitor::VisitPointers(dart::RawObject**, dart::RawObject**) ../../out/DebugX64/../../runtime/vm/heap/scavenger.cc:86

STDERR :     #10 0x55fe96474979 in long dart::RawObject::VisitPointersNonvirtual<dart::ScavengerVisitor>(dart::ScavengerVisitor*) ../../out/DebugX64/../../runtime/vm/raw_object.h:589:17

STDERR :     #11 0x55fe96474350 in dart::Scavenger::IterateStoreBuffers(dart::Isolate*, dart::ScavengerVisitor*) ../../out/DebugX64/../../runtime/vm/heap/scavenger.cc:577:19

STDERR :     #12 0x55fe96474e9f in dart::Scavenger::IterateRoots(dart::Isolate*, dart::ScavengerVisitor*) ../../out/DebugX64/../../runtime/vm/heap/scavenger.cc:618:5

STDERR :     #13 0x55fe96479c6a in dart::Scavenger::Scavenge() ../../out/DebugX64/../../runtime/vm/heap/scavenger.cc:938:5

STDERR :     #14 0x55fe96434be4 in dart::Heap::CollectNewSpaceGarbage(dart::Thread*, dart::Heap::GCReason) ../../out/DebugX64/../../runtime/vm/heap/heap.cc:415:18

STDERR :     #15 0x55fe96434695 in dart::Heap::NotifyIdle(long) ../../out/DebugX64/../../runtime/vm/heap/heap.cc:376:5

STDERR :     #16 0x55fe958bc607 in dart::MessageHandler::CheckAndRunIdleLocked(dart::MonitorLocker*) ../../out/DebugX64/../../runtime/vm/message_handler.cc:526:16

STDERR :     #17 0x55fe958b9b9f in dart::MessageHandler::TaskCallback() ../../out/DebugX64/../../runtime/vm/message_handler.cc:430:29

STDERR :     #18 0x55fe958bfc89 in dart::MessageHandlerTask::Run() ../../out/DebugX64/../../runtime/vm/message_handler.cc:27:15

STDERR :     #19 0x55fe95e40b23 in dart::ThreadPool::Worker::Loop() ../../out/DebugX64/../../runtime/vm/thread_pool.cc:381:11
    #20 0x55fe95e3fa38 in dart::ThreadPool::Worker::Main(unsigned long) ../../out/DebugX64/../../runtime/vm/thread_pool.cc:436:27
    #21 0x55fe95b827bd in dart::ThreadStart(void*) ../../out/DebugX64/../../runtime/vm/os_thread_linux.cc:131:5
    #22 0x7f18f50d5493 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x7493)

SUMMARY: AddressSanitizer: 32 byte(s) leaked in 1 allocation(s).

I suspect this has to do with the idle notification implementation: the main thread might be in the process of shutting down while the idle notification task is doing a scavenge
The test failure is timing dependent, but it can be reproduced locally (ensure to have built with asan)

Since this might be the same root cause as https://github.com/dart-lang/sdk/issues/34888 I'm tentatively assinging @rmacnak-google . Hope that's ok.

The leak in file_test is being tracked in https://github.com/dart-lang/sdk/issues/40648
Looks like standalone_2/io/signals_test was fixed in another CL.
I cannot reproduce the failures in
standalone_2/io/http_server_response_test
lib_2/isolate/non_fatal_exception_in_timer_callback_test/sleep
and finally dartk-vm release_x64 lib_2/mirrors/dynamic_load_test - dart:mirrors is not being actively maintained
I am closing this issue. If any of the tests in the list do show up with leaks please open new issues with logs that have the error stack trace.


SDL_mixer: fix build with clang 16

Description of changes
Fixes build failures in staging-next #263535.

SDL_mixer: https://hydra.nixos.org/build/239893371

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 265998 run on aarch64-darwin 1

19 packages marked as broken and skipped:

abuse
barrage
freedroid
gargoyle
guile-sdl
hheretic
hhexen
ltris
onscripter-en
pokerth
pokerth-server
powermanga
rott
rott-shareware
tecnoballz
titanion
torus-trooper
tumiki-fighters
xmoto

9 packages built:

SDL_mixer
frozen-bubble
frozen-bubble.devdoc
hyperrogue
odamex
perl536Packages.SDL
perl536Packages.SDL.devdoc
perl538Packages.SDL
perl538Packages.SDL.devdoc


Updating the descriptions for various parameters, paths and definitions

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[x] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

/azp run automation - sdk

Can one of the admins verify this patch?

@asarkar84 please fix the CI error.

Unknown word : agreeement, eligiblity, desscription, maketplace
Description must not match the name of the node it is supposed to describe. Node name:'city' Description:'City.'
at specification/billing/resource-manager/Microsoft.Billing/preview/2019-10-01-preview/billing.json:5938

R3011 - DescriptionMustNotBeNodeName
Description must not match the name of the node it is supposed to describe. Node name:'region' Description:'Region.'
at specification/billing/resource-manager/Microsoft.Billing/preview/2019-10-01-preview/billing.json:5942

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

@asarkar84 please fix the CI error.

Unknown word : agreeement, eligiblity, desscription, maketplace
Description must not match the name of the node it is supposed to describe. Node name:'city' Description:'City.'
at specification/billing/resource-manager/Microsoft.Billing/preview/2019-10-01-preview/billing.json:5938
R3011 - DescriptionMustNotBeNodeName
Description must not match the name of the node it is supposed to describe. Node name:'region'
Description:'Region.'
at specification/billing/resource-manager/Microsoft.Billing/preview/2019-10-01-
preview/billing.json:5942

@njuCZ I have fixed the errors. Please take a look now.

/azp run automation - sdk

/azp run automation - sdk

@njuCZ Please review this PR and merge if it this looks good to you.


Aerie got stuck at the login page when we turned on "CAM" authentication with JWT disabled

Checked for duplicates
Yes - I've already checked
Is this a regression?
No - This is a new bug
Version
1.7.0
Describe the bug
Unable to login to Aerie when JWT authentication is disabled.
Reproduction
Not sure if this is something Aeire support, but we tried to turn off JWT authentication by commenting out all the "SECRET" environment variables in the docker-compose file.
When we tried to deploy Aeire with the "CAM" authentication, Aerie got stuck on the login page, and there were errors from the gateway log(see below);
On the other hand, it works if we set Aerie authentication to "none." However, we will still see a login page asking for a username and password.
Logs
SyntaxError: Unexpected end of JSON input
    at JSON.parse (<anonymous>)
    at generateJwt (file:///app/dist/packages/auth/functions.js:37:36)
    at login (file:///app/dist/packages/auth/functions.js:81:28)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async file:///app/dist/packages/auth/routes.js:42:26
Error: Authorization header does not include 'Bearer' prefix
    at authorizationHeaderToToken (file:///app/dist/packages/auth/functions.js:13:19)
    at decodeJwt (file:///app/dist/packages/auth/functions.js:22:23)
    at session (file:///app/dist/packages/auth/functions.js:147:32)
    at file:///app/dist/packages/auth/routes.js:82:32
    at Layer.handle [as handle_request] (/app/node_modules/express/lib/router/layer.js:95:5)
    at next (/app/node_modules/express/lib/router/route.js:144:13)
    at Route.dispatch (/app/node_modules/express/lib/router/route.js:114:3)
    at Layer.handle [as handle_request] (/app/node_modules/express/lib/router/layer.js:95:5)
    at /app/node_modules/express/lib/router/index.js:284:15
    at Function.process_params (/app/node_modules/express/lib/router/index.js:346:12)
Error: Authorization header does not include 'Bearer' prefix
    at authorizationHeaderToToken (file:///app/dist/packages/auth/functions.js:13:19)
    at decodeJwt (file:///app/dist/packages/auth/functions.js:22:23)
    at session (file:///app/dist/packages/auth/functions.js:147:32)
    at file:///app/dist/packages/auth/routes.js:82:32
    at Layer.handle [as handle_request] (/app/node_modules/express/lib/router/layer.js:95:5)
    at next (/app/node_modules/express/lib/router/route.js:144:13)
    at Route.dispatch (/app/node_modules/express/lib/router/route.js:114:3)
    at Layer.handle [as handle_request] (/app/node_modules/express/lib/router/layer.js:95:5)
    at /app/node_modules/express/lib/router/index.js:284:15
    at Function.process_params (/app/node_modules/express/lib/router/index.js:346:12)
Error: Authorization header does not include 'Bearer' prefix
    at authorizationHeaderToToken (file:///app/dist/packages/auth/functions.js:13:19)
    at decodeJwt (file:///app/dist/packages/auth/functions.js:22:23)
    at session (file:///app/dist/packages/auth/functions.js:147:32)
    at file:///app/dist/packages/auth/routes.js:82:32
    at Layer.handle [as handle_request] (/app/node_modules/express/lib/router/layer.js:95:5)
    at next (/app/node_modules/express/lib/router/route.js:144:13)
    at Route.dispatch (/app/node_modules/express/lib/router/route.js:114:3)
    at Layer.handle [as handle_request] (/app/node_modules/express/lib/router/layer.js:95:5)
    at /app/node_modules/express/lib/router/index.js:284:15
    at Function.process_params (/app/node_modules/express/lib/router/index.js:346:12)

System Info
Mac OS, Chrome

Severity
Moderate

We were trying to run with JWT disabled to see if we could use 1.7.0 for our upcoming thread test (we don't have enough time to update our other tooling to support JWT auth before the test). We do not have a long term need to disable JWT auth. We can also use 1.6.0 for the thread test; we were considering 1.7.0 just to get the latest-and-greatest UI updates in front of our users.


Feature/tvos support integration tests functions

Changes done to XCode project for functions that allows us to run integration tests on device and simulator.
added a tvos target to XCode project for storage.
updated Podfile to build pods for tvos platform for this newly added target
To test this,
Make sure to have a valid GoogleService-Info.plist.
pod install
open integration_test.xcworkspace
Drag and drop firebase.xcframework, firebase_auth.xcframework and firebase_functions.xcframework
All tests pass on simulator and device.

I think you should remove files from xcuserdata/vimanyujain*, right?

functions/integration_test/integration_test.xcodeproj/project.xcworkspace/xcuserdata/vimanyujain.xcuserdatad/UserInterfaceState.xcuserstate
functions/integration_test/integration_test.xcodeproj/xcuserdata/vimanyujain.xcuserdatad/xcschemes/xcschememanagement.plist
functions/integration_test/integration_test.xcworkspace/xcuserdata/vimanyujain.xcuserdatad/UserInterfaceState.xcuserstate

I remember that "integration_test.xcodeproj/project.pbxproj" is the only file we want under "integration_test.xcodeproj", we can safely remove the rest.
This may apply to "integration_test.xcworkspace" as well.
@jonsimantov Could you provide more information?

Removed user specific files.


ENH: major performance improvement in pairwise distance calculations

Summary by Sourcery
Refactor the test suite to use pytest fixtures and parameterized tests, enhancing modularity and readability. Implement numba-accelerated functions for pairwise distance calculations, significantly improving performance for various distance metrics including JC69, TN93, paralinear, hamming, and proportion difference.
Enhancements:

Refactor test suite to use pytest fixtures for better modularity and reusability.
Optimize pairwise distance calculations by implementing numba-accelerated functions for various distance metrics including JC69, TN93, paralinear, hamming, and proportion difference.

Tests:

Convert existing test cases to use pytest framework, improving test structure and readability.
Add parameterized tests for numba-accelerated distance calculations to ensure accuracy and performance.

The codacy issues are not pertinent (show_progress get's intercepted by a decorator and the undefined name is being used to avoid circular imports

Pull Request Test Coverage Report for Build<PHONE_NUMBER>7
Details

80 of 106 (75.47%)  changed or added relevant lines in 4 files are covered.
4 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.05%) to 92.312%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/cogent3/evolve/pairwise_distance_numba.py
67
93
72.04%

Files with Coverage Reduction
New Missed Lines
%

src/cogent3/evolve/fast_distance.py
2
95.78%

src/cogent3/maths/scipy_optimize.py
2
84.92%

Totals

Change from base Build<PHONE_NUMBER>8:
-0.05%

Covered Lines:
34113

Relevant Lines:
36954

💛  - Coveralls


Fix typo in README.txt

Issues
https://github.com/wso2/product-is/issues/8474

The same typo exists on README.md fail as well. Shall we fix that as well?

Yes ;-)


Add an RMap widget to four types of OSF pages

Add an RMap widget to four types of OSF pages: User, Project, Component and Repository.  The widget is added by inserting a single "include" element in the profile.mako template (for user pages) and the project.mako template (for the other three types of pages).
The include statement references a new template rmap_widget.mako that hosts the widget in an iframe.  This template uses a new CSS file rmap.css to control its layout.
This work was specified in card DC-2326.

@Trumbore I took a look at the diffs and while I don't claim to understand how the OSF frontend works (e.g. Mako templates), I don't see anything that gives me pause!  I'll wait for @markpatton to comment then I think @htpvu will be the one to actually perform the merge!

@Trumbore I took a quick look and it looks reasonable. It should be merged. My only concern is that every project would have this widget.  Eventually we might want it to be configured on a per project basis as an Addon.


Add GitHub actions to the project.

I will add github actions to the project. GitHub Actions makes it easy to automate all your software workflows, now with world-class CI/CD.
Should i work with this as this will be very good for the project.

@vinitshahdeo have a look at this will be very useful.

@aashimgarg Can you please elaborate what sort of GitHub actions do you want to be included in this project and why. Also, are you interested in contributing something to solve this issue for eg. - Github actions documentation for this project.


vows-test.js/CrazyEmitter tests are not implemented and will fail when implementing them

While working on #349 I stumbled across some test cases not being implemented in test/vows-test.js.
These test cases deal with a synchronous emitter test that will listen on custom events of the emitter. When implementing these tests I found that they will always fail as the emitter will be passed to the vow instead of the data emitted by the event upon which that vow was listening as its topics.
It turned out that in lib/vows/addVows the last success event arguments would always be used instead of the vow.binding.context.nextTopics() when calling runTest(...).
Quite a bugger, that one.
See the follow up PR for a fix for that issue.

I have discontinued using vows in favor of mocha as I am transitioning to babel/ES. Closing this now.

Reopening since it is yet to be decided whether the PR should be integrated.

Since it'd be almost impossible to merge into the new codebase, I'm closing this down.


Feature: provide contributor insights

Type of feature
🍕 Feature
Current behavior
Currently, via the CLI, there's no way to see insights for a provided repos.
Suggested solution
We should add an insights command that has a contributors subcommand to start.
When invoked with a git repo, it provides some very basic insights based on the commits to the user:
$ pizza insights contributors <git-repo>
Over last 30 days

New: 6
Recurring: 2

Should also provide the ability to specify the time range:
$ pizza insights contributors <git-repo> --time 60d

Over last 60 days:

New contributors: 6
Recurring contributors: 2

If the repo is a GitHub repo (which we have indexed data for from the API backend), we should generate a link to the insights page:
$ pizza insights contributors https://github.com/open-sauced/pizza-cli --time 60d

Over last 60 days:

New contributors: 6
Recurring contributors: 2

See more at: https://insights.opensauced.pizza/{insight-page}

The above will include a few calls to the API so there are some changes that probably need to be made there as well.
Additional context
No response
Code of Conduct

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

Contributing Docs

[X] I agree to follow this project's Contribution Docs

Hi @jpmcb, I just discovered this project and I’m interested in working on it. Can I have this issue assigned to me?

Hi @cecobask! Thanks for reaching out and showing interest. This will require integrating with a few of the newer API endpoints we have, for example, for new contributors, you'll want to use: https://github.com/open-sauced/api/pull/223
If that sounds like something you're up for tackling, I'll assign you and I'm happy to help with anything you come up against!

Sounds good to me, @jpmcb!
First, I want to get an understanding of the APIs. I followed the instructions and did the following:

Forked and cloned open-sauced/api
Setup a project on Supabase and created .env file in the root of the repository with the required secrets
Provisioned a Postgres container using the provided Dockerfile
Installed the needed dependencies and successfully ran the application locally
Tested a couple of endpoints locally but soon realized the tables in the database need to be created first

I have a couple of questions:

Is there an automated approach to execute the database migrations locally?
Which endpoint can I use to initiate the authentication flow and retrieve a bearer token?

I think the 2 points above are important for any new contributor and should be added to the README.
Thanks in advance!

Is there an automated approach to execute the database migrations locally?

You can apply the migrations using psql. And you can apply them all automatically via some bash:
https://github.com/open-sauced/api/issues/226

Which endpoint can I use to initiate the authentication flow and retrieve a bearer token?

That is probably blocked on #20. So for now, look at just using non-authed contributor insights

@jpmcb, I've submitted a pull request.
Please, review when you get a chance 👍🏻


Logging doesn't actually work

I enable logging but no log is created

Pretty sure that's because you didn't create a logs dir.
(but we should check for that relative directory potential problem)

@rom1504 Not the problem. I created a log directory, and if a log directory doesn't exist... craftyjs should create one

The main problem was it wasn't using the correct dir. Now it is, problem fixed.


librehardwaremonitor: Add version 0.8.8

Manifest is adapted from openhardwaremonitor.

/unsubsribe
Adding forks of actively maintained applications is not something that should be done in the Extras/Main buckets.

/verify


[BUG] "+" character removed while searching

Describe The Bug
When searching with the + character anywhere in the buffer. It will be removed when searching which can change the normal results. Even force search will have this issue.
To Reproduce
Steps to reproduce the behavior:

Go to StartPage
Search either:

"How to do string split in c++"  => How to do string split in c
"(3 + 4) + (4 + 3)"  => "(3   4)   (4   3)"

You'll see current search result being changed

Expected Behavior
For the search result to not be changed
Specs

OS: Window 10 & Arch Linux
Browser: Firefox 121

Hey @NitroSniper!
Nice catch, I need to use encodeURIComponent to properly encode the string in order to work with requests.
The string should be encoded to ouput something like this in order for engines to properly handle symbols:
https://www.google.com/search?q=How%20to%20do%20string%20split%20in%20c%2B%2B

Will start working on it as soon as possible and release as a hotfix when it is ready.
Cheers!

Fixed with PR #69, releasing the hotfix as 3.1.2 now


Add command to add SAML support

Add a command to update extensions xml with the relevant code to support SAML SP applications.

Done for SAMl IdP in 3.0.5


cmd/go: 'go get -u' in 1.13 fails with 'go get .: cannot find package'

What version of Go are you using (go version)?

$ go version
go version go1.13 linux/amd64

Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE="on"
GOARCH="amd64"
GOBIN="/home/rvolosatovs/.local/bin.go"
GOCACHE="/home/rvolosatovs/.local/cache/go-build"
GOENV="/home/rvolosatovs/.config/go/env"
GOEXE=""
GOFLAGS="-tags=tti"
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/rvolosatovs:/nix/store/b02sg3w3h50k3h8f53mix6ivd9zh8fm2-go-1.13/share/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/nix/store/b02sg3w3h50k3h8f53mix6ivd9zh8fm2-go-1.13/share/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/nix/store/b02sg3w3h50k3h8f53mix6ivd9zh8fm2-go-1.13/share/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="0"
GOMOD="/home/rvolosatovs/src/go.thethings.network/lorawan-stack/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build061535754=/tmp/go-build -gno-record-gcc-switches"

What did you do?

go get -u -v

Fails on go 1.13
The project contains both go.mod(https://github.com/rvolosatovs/lorawan-stack/blob/ce9328f83312201d231b4183413c969260b5a5a1/go.mod) and go.sum(https://github.com/rvolosatovs/lorawan-stack/blob/ce9328f83312201d231b4183413c969260b5a5a1/go.sum)
go mod tidy, go mod download and go mod vendor work fine
What did you expect to see?
Dependency update
What did you see instead?
go get .: cannot find package

@rvolosatovs What happens if you try go get -u -v ./...?
If you dogo get -u ./... from your module root, it upgrades the direct and indirect dependencies of your module, exclusive of test dependencies.
From the Go 1.13 release notes:

In module-aware mode, go get with the -u flag now updates a smaller set of modules that is more consistent with the set of packages updated by go get -u in GOPATH mode. go get -u continues to update the modules and packages named on the command line, but additionally updates only the modules containing the packages imported by the named packages, rather than the transitive module requirements of the modules containing the named packages.
Note in particular that go get -u (without additional arguments) now updates only the transitive imports of the package in the current directory

The last sentence might be describing what you see.
Do you have any *.go files in your working directory when you do go get -u -v without any arguments?

Adding a go file in the root directory with no build constraints fixed the issue. (https://github.com/TheThingsNetwork/lorawan-stack/pull/1312/commits/29b8003721862bd821864ffdabcaa471e12f844d)
Thanks, @thepudds
I suppose what I encountered is exactly what

Note in particular that go get -u (without additional arguments) now updates only the transitive imports of the package in the current directory

entails

@rvolosatovs @bcmills what would you think about re-opening this as a tracking issue for a friendlier message here?
(The current message says go get ., but the user never typed .. The current message says cannot find package, but doesn't directly say what package it cannot find, etc.)

The error message is indeed very confusing for a user, who does not expect it.
Now that I know what caused the issue, it's clear what it means, but it was absolutely useless for me when I encountered it.
Note, that the error is valid in fact - the package go cannot find is ., i.e. the package in the current directory.
So I agree that the error message is far from being user-friendly in this exact (corner) case, but on the other hand go get -u implies go get -u . and in case of any other usage than go get -u the invocation would actually look like go get -u <pkg> and hence the error message would look like go get <pkg>: cannot find package, which is perfectly fine IMO.


Cleanup

The replica fails within the CI process:
Oct 09 17:51:56.391 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: Notary has not been invoked for 2.399171136s
Oct 09 17:51:56.392 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: Finalizer has not been invoked for 5.800606865s
Oct 09 17:51:56.438 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: RandomBeaconMaker has not been invoked for 5.800606865s
Oct 09 17:51:56.438 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: RandomTapeMaker has not been invoked for 5.800606865s
Oct 09 17:51:56.438 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: BlockMaker has not been invoked for 5.800606865s
Oct 09 17:51:56.438 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: CatchUpPackageMaker has not been invoked for 5.800606865s
Oct 09 17:51:56.439 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: Validator has not been invoked for 5.800606865s
Oct 09 17:51:56.439 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: Aggregator has not been invoked for 5.800160961s
Oct 09 17:51:56.439 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: Purger has not been invoked for 5.800606865s
Oct 09 17:51:57.645 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: Notary has not been invoked for 4.799432668s
Oct 09 17:51:59.846 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: Notary has not been invoked for 2.093355306s
Oct 09 17:51:59.847 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: Finalizer has not been invoked for 2.20046443s
Oct 09 17:51:59.847 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: RandomBeaconMaker has not been invoked for 2.093355306s
Oct 09 17:51:59.847 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: RandomTapeMaker has not been invoked for 2.042690463s
Oct 09 17:51:59.847 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: BlockMaker has not been invoked for 2.042690463s
Oct 09 17:51:59.847 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: CatchUpPackageMaker has not been invoked for 2.20046443s
Oct 09 17:51:59.847 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: Validator has not been invoked for 2.20046443s
Oct 09 17:51:59.847 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: Aggregator has not been invoked for 2.20046443s
Oct 09 17:51:59.847 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: Purger has not been invoked for 2.20046443s
Oct 09 17:51:59.852 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: Notary has not been invoked for 2.203883923s
Oct 09 17:51:59.855 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: RandomBeaconMaker has not been invoked for 2.203883923s
Oct 09 17:51:59.855 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: RandomTapeMaker has not been invoked for 2.15321908s
Oct 09 17:51:59.855 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: BlockMaker has not been invoked for 2.15321908s
Oct 09 17:51:59.855 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: CatchUpPackageMaker has not been invoked for 2.310993047s
Oct 09 17:51:59.855 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: Aggregator has not been invoked for 2.310993047s
Oct 09 17:51:59.855 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: Purger has not been invoked for 2.310993047s
Oct 09 17:51:59.894 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: Notary has not been invoked for 2.211600673s
Oct 09 17:51:59.894 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: RandomBeaconMaker has not been invoked for 2.211600673s
Oct 09 17:51:59.894 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: RandomTapeMaker has not been invoked for 2.16093583s
Oct 09 17:51:59.894 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: BlockMaker has not been invoked for 2.16093583s
Oct 09 17:51:59.897 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: RandomBeaconMaker has not been invoked for 2.247596806s
Oct 09 17:51:59.897 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: RandomTapeMaker has not been invoked for 2.196931963s
Oct 09 17:51:59.897 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: BlockMaker has not been invoked for 2.196931963s
Oct 09 17:51:59.897 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: BlockMaker has not been invoked for 2.198894776s
./scripts/runTests.sh: line 20:  2715 Killed                  dfx canister call textEdit windowSizeChange 'record {width=100; height=100; }'
Oct 09 17:52:58.644 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: Finalizer has not been invoked for 2.798894133s
Oct 09 17:52:58.644 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: RandomBeaconMaker has not been invoked for 2.798894133s
Oct 09 17:52:58.644 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: RandomTapeMaker has not been invoked for 2.798894133s
Oct 09 17:52:58.644 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: BlockMaker has not been invoked for 2.798894133s
Oct 09 17:52:58.644 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: CatchUpPackageMaker has not been invoked for 2.798894133s
Oct 09 17:52:58.644 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: Validator has not been invoked for 2.798894133s
Oct 09 17:52:58.644 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: Aggregator has not been invoked for 2.798894133s
Oct 09 17:52:58.644 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:5wjwg-gteaa-aaaaa-aaaap-2ai/ic_consensus/orchestrator starvation detected: Purger has not been invoked for 2.798894133s


Adding support for markdown within HTML tags

We've recently included Parsedown (Extra) into Statamic (and, by the way, I love it, it's so quick and does a much, much better job of handling the weird edge cases).
Anyway, someone has submitted a ticket to our support system asking about support in Parsedown (Extra) for markdown="1" for parsing within HTML elements. (It's part of Markdown Extra).
So, I'm here doing my due diligence. Is this feature something on the Parsedown Extra roadmap for implementation? Is it perhaps already implemented but slightly different syntax from Markdown Extra?
Thanks for your time (and for such an awesome markdown parser).
Fred

The latest release resolves this.
p.s. The improvements in Parsedown.php made it possible to implement the whole feature in 5 lines of code.

Awesome!! Thanks so much!! I'm gonna update now! :+1:

Ok, it does work for tags that are nested in tags that have markdown=1, but it still doesn't work for nested tags that are inside of tags that don't have it.
I'm reopening this.

Ok, now it should always work.

Ok, now it should always work.

It does not for me now when I don't specifically add markdown="1" to every HTML block.. what am I doing wrong?
This is my code:
$markdown = 'Link: [parsedown](https://parsedown.org/)

Link: [parsedown](https://parsedown.org/)

Link: [parsedown](https://parsedown.org/)

Click to see

## Title
Link: [parsedown](https://parsedown.org/)
Code: `codeblock`

';

$parser = new ParsedownExtra();
echo $parser->text($markdown);

This is the HTML I get:

Link: parsedown

Link: parsedown

Link: [parsedown](https://parsedown.org/)

Click to see

## Title
Link: [parsedown](https://parsedown.org/)
Code: `codeblock`


Fix concurrency issue

Fix #17 and #21 using @v0devil 's suggestion found here.

@OiCMudkips  Any chance you could produce a jar with this change in it?  I can't seem to get your PR to compile.

I ended up doing a bytecode hack to fix it.  In case anyone else needs it, here's a zip with the JAR that has this fix in it.
fixed.zip


Feature Request - Allow retainValue parameter of type S.() -> Async in MavericksRepository

I am currently using the Mavericks library in my Android project and I am wondering if it would be possible to allow a lambda of type S.() -> Async to be used as the retainValue parameter in the execute method of the MavericksRepository class.
This feature would provide greater flexibility in managing the creation and retention of Async instances based on the current state of the repository.
If this is not possible, I would appreciate any suggestions on alternative approaches to achieving similar functionality.
Thank you for your time and consideration.

data class DataInfo(val index: Int, val state: Async<Int>)

data class MainUS(val list: List<DataInfo> = emptyList()) : MavericksState`

class MainVM(initialState: MainUS) : MavericksViewModel<MainUS>(initialState) {
    companion object : MavericksViewModelFactory<MainVM, MainUS> {
        override fun initialState(viewModelContext: ViewModelContext): MainUS? {
            val list = (1..20).map { DataInfo(index = it, state = Uninitialized) }

            return MainUS(list)
        }

        override fun create(viewModelContext: ViewModelContext, state: MainUS): MainVM? {
            return MainVM(state)
        }
    }

    fun doWork(info: DataInfo) {

        flow {
            delay(1000)
            emit(Random.nextInt())
        }.execute(Dispatchers.IO) {

            val list = list.map { itemInfo ->
                itemInfo.takeUnless { it.index == info.index } ?: itemInfo.copy(state = it)
            }

            copy(list = list)
        }
    }
}


fix: Skeleton theme polluting DOM

It's not desired for the theme to dictate any DOM changes.  Switching to use Global allows us to drop the physical DOM element.

https://github.com/dvtng/react-loading-skeleton/issues/46

I see.  Can you think of another way that we could style a section of the tree without the div?  If not, perhaps we allow styles on the div element.  That would at least help mitigate the effects of having an extra element.

Also, I believe the default behavior is for the nearest Global component's styles to take precedence.  Meaning that if we had two Global themes defined, the closest ancestor would win.

I see. Can you think of another way that we could style a section of the tree without the div? If not, perhaps we allow styles on the div element. That would at least help mitigate the effects of having an extra element.

+1 for being able to style the SkeletonTheme div. That way we can make it behave like we want (as block, as an inline, etc)

@jpesce Would my second comment work for you as well?  Do you prefer the div approach?

Also, I believe the default behavior is for the nearest Global component's styles to take precedence. Meaning that if we had two Global themes defined, the closest ancestor would win.

@jpesce Would my second comment work for you as well? Do you prefer the div approach?

Also, I believe the default behavior is for the nearest Global component's styles to take precedence. Meaning that if we had two Global themes defined, the closest ancestor would win.

If that's the case then that would be perfect, but I'm not seeing how it's possible for it to work this way. Would you be able to show that it works as expected in a story?

@jpesce Would my second comment work for you as well? Do you prefer the div approach?

If I can understand correctly, yes. It should work as well because we can then style Skeleton directly and there wouldn't be a surrounding div.

Can this theming be done via React context instead of rendering a div? I'm having difficulty using the current theming with portals because the portal isn't rendered as a child of the SkeletonTheme's div.
Here's an example...
Let's say we have this as our starting HTML:

And we want to render the App element into the div with ID app. If the App element looks like this:
<SkeletonTheme>
  <UserProfile>
    <EditUserProfileDialog /> {/* this dialog uses a portal to render directly as a child of `body` */}
  </UserProfile>
</SkeletonTheme>

The resulting HTML would look something like:

Even though EditUserProfileDialog is a child of SkeletonTheme in the React component tree, nothing inside of the dialog will receive the proper theming since the dialog's elements are not a child of the SkeletonTheme's div. If themes were implemented using React context instead, I think this use case would work as expected, and it would also solve the issue of not having to render extra DOM elements.

Can this theming be done via React context instead of rendering a div? I'm having difficulty using the current theming with portals because the portal isn't rendered as a child of the SkeletonTheme's div.
Here's an example...
Let's say we have this as our starting HTML:

And we want to render the App element into the div with ID app. If the App element looks like this:
<SkeletonTheme>
  <UserProfile>
    <EditUserProfileDialog /> {/* this dialog uses a portal to render directly as a child of `body` */}
  </UserProfile>
</SkeletonTheme>

The resulting HTML would look something like:

Even though EditUserProfileDialog is a child of SkeletonTheme in the React component tree, nothing inside of the dialog will receive the proper theming since the dialog's elements are not a child of the SkeletonTheme's div. If themes were implemented using React context instead, I think this use case would work as expected, and it would also solve the issue of not having to render extra DOM elements.

Hi @baleeds @jpesce, PTAL at my PR. Would this be a valid solution?

Hi @baleeds @jpesce, @dvtng , PTAL at my PR. Would this be a valid solution?

I think it's a valid solution.  I would still prefer the Global solution if it's viable, but I no longer have a dependency on this project.

Thanks @baleeds! How about you, @jpesc @dvtng?

Hi @baleeds @jpesce, @dvtng , PTAL at my PR. Would this be a valid solution?

Yes, your PR definitely solves the problem. 👍
But I agree with @baleeds: the Global solution would be better. And I also don't have a dependency on this project anymore.

Sadly I don't have time right now to implement this. I'll go ahead and close my PR for now.

Thanks for this helpful conversation. SkeletonTheme is going to be changed to use React Context which will solve this issue. Being tracked in #101.


6.0.0 npm error: node_modules/ember-shepherd: Appears to be a git repo or submodule.

ember-shepherd 6.0.0 fails to install via npm with the following error:
npm install
npm WARN deprecated<EMAIL_ADDRESS>Please replace with usage of fs.existsSync
npm WARN deprecated<EMAIL_ADDRESS>Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated<EMAIL_ADDRESS>Please replace with usage of fs.existsSync
npm WARN deprecated<EMAIL_ADDRESS>CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
npm ERR! path /Users/steve/code/myapp/myapp/node_modules/ember-shepherd
npm ERR! code EISGIT
npm ERR! git /Users/steve/code/myapp/myapp/node_modules/ember-shepherd: Appears to be a git repo or submodule.
npm ERR! git     /Users/steve/code/myapp/myapp/node_modules/ember-shepherd
npm ERR! git Refusing to remove it. Update manually,
npm ERR! git or move it out of the way first.

If one looks at the node_modules directory, it contains a .git directory which likely is the cause of the error. ember-shepherd 5.0.0 does not contain that directory.
ls -a node_modules/ember-shepherd/
.		..		.DS_Store	.git		CHANGELOG.md	HISTORY.md	LICENSE.md	README.md	addon		app		config		fastboot	index.js	package.json

yarn does not seem to have an issue with this and installs fine. However, it would probably be a good idea to make sure the .git and .DS_Store folder is removed from future releases.

@st-h we haven't changed anything regarding the npm publishing. Perhaps older npm versions ignored .git by default or something?

@rwwagner90 I actually do not know. It showed up in our CI, where the ember build was still using npm. I tried to reproduce it locally and was able to do so. Then I switched back to ember-shepherd 5.0 and had a look at what got installed in the node_modules folder. I noticed that only 6.0 contained the .git directory. 5.0 does not contain .git or .DS_Store files.
If I have a look at the node_modules directory of my app, ember-shepherd is the only one shipping a .git directory:
$ find node_modules -name '.git'
node_modules/ember-shepherd/.git

I don't have a clue what might be causing this though

@st-h I believe it is a bug when publishing packages with newer npm versions. This seems related https://npm.community/t/npm-pack-includes-items-from-git-folder-if-there-is-a-branch-called-readme-regression-in-6-9-0/6044
According to https://docs.npmjs.com/misc/developers#keeping-files-out-of-your-package .git should be ignored by default.

@rwwagner90 that sounds nasty... You are right that npm should ignore .git files by default. I am just a little puzzled that we are not seeing this with other add ons as the post you linked already is a few months old. But people should probably be using yarn by now anyways :trollface:

@st-h it might be some sort of edge case, and not happening all the time. I may have just updated node/npm on the particular day the bug was occurring, and things are okay now. Either way, I just published 6.0.1 and use an older npm, which hopefully should fix the problem. Can you try nombom and installing 6.0.1 and see if it fixes the issue?

@rwwagner90 6.0.1 looks good to me :)
$ ls -a node_modules/ember-shepherd/
.		..		CHANGELOG.md	HISTORY.md	LICENSE.md	README.md	addon		app		config		fastboot	index.js	package.json


Feature/findhealthmonitorbyname

Setting the health monitor for the node and the pool by name instead of id

I'll check it out when I get home. Can you make sure the branch name is lower case next time? :)
On 29 Nov. 2016, at 1:31 pm, kumarappanc <notifications<EMAIL_ADDRESS>wrote:
Setting the health monitor for the node and the pool by name instead of id

You can view, comment on, or merge this pull request online at:
https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/pull/67https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/pull/67
Commit Summary

changes to set the haelth montior by name for the vip node
changes to set the health monitors for the pool by name instead of Id

File Changes

M docs/resource_types/vip_node.mdhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/pull/67/files#diff-0 (2)
M docs/resource_types/vip_pool.mdhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/pull/67/files#diff-1 (8)
M vendor/ddcloud/resource_vip_node.gohttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/pull/67/files#diff-2 (67)
M vendor/ddcloud/resource_vip_node_test.gohttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/pull/67/files#diff-3 (17)
M vendor/ddcloud/resource_vip_pool.gohttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/pull/67/files#diff-4 (81)
M vendor/ddcloud/resource_vip_pool_test.gohttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/pull/67/files#diff-5 (49)
M vendor/github.com/DimensionDataResearch/go-dd-cloud-computehttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/pull/67/files#diff-6 (2)
A version-info.gohttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/pull/67/files#diff-7 (4)

Patch Links:

https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/pull/67.patchhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/pull/67.patch
https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/pull/67.diffhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/pull/67.diff

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/pull/67, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABkezDzkBnQtVkladNmly8hPr2cjp18vks5rC46QgaJpZM4K-f4Y.
itevomcid

refactored the code as per your suggestion. Cannot call make with 1 argument without the length. So changed the few things to make it work. Please let me know your feedback

Thanks - this will be in v1.1.10 :)
Feel free to pull down the latest from development/v1.0 and build locally if you need these changes sooner. I'll look at merging these changes into the v1.2 branch later today.