CL: script to modify genesis with positions

Context in: https://app.clickup.com/t/860qaydwh

Closing this issue per it being finished


Hook type issue

@lopitz found an issue whereby hooks could fail silently due to a ClassCastException if the whole chain (hooks & values) isn't all of the same / right type.

Due to the nature of this issue, there are two options to mitigate it.

call only these hooks, which support the type of the evaluated flag
call all hooks, but let the hooks be untyped, leaving it up to the hook author to check the type and apply logic.

In my PR I opted for the first option, but with some sort of expressiveness by introducing dedicated interfaces for boolean, string and integer typed hooks. If hook authors still wants their hook to get called everytime, they still can use the generic form.


fix(fleet): Remove tests race condition for the APM socket

What does this PR do?
Fixes a race condition where we start an app expecting it to send traces before the trace agent has had the time to create the APM socket
Motivation
Flaky tests
Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


[#1037] Consolidate back button on the phrase display screen

Closes #1037

ZashiBackModifier updated with a new hidden param. This way it can be controlled by views for dynamic scenarios.
Reducer updated to latest TCA.
Unit tests refactored and fixed.

This code review checklist is intended to serve as a starting point for the author and reviewer, although it may not be appropriate for all types of changes (e.g. fixing a spelling typo in documentation).  For more in-depth discussion of how we think about code review, please see Code Review Guidelines.
Author

[x] Self-review: Did you review your own code in GitHub's web interface? Code often looks different when reviewing the diff in a browser, making it easier to spot potential bugs.
[ ] Does the code abide by the Coding Guidelines?
[x] Automated tests: Did you add appropriate automated tests for any code changes?
[x] Code coverage: Did you check the code coverage report for the automated tests?  While we are not looking for perfect coverage, the tool can point out potential cases that have been missed.
[ ] Documentation: Did you update Docs as appropiate? (E.g README.md, etc.)
[x] Run the app: Did you run the app and try the changes?
[ ] Did you provide Screenshots of what the App looks like before and after your changes as part of the description of this PR? (only applicable to UI Changes)
[x] Rebase and squash: Did you pull in the latest changes from the main branch and squash your commits before assigning a reviewer? Having your code up to date and squashed will make it easier for others to review. Use best judgement when squashing commits, as some changes (such as refactoring) might be easier to review as a separate commit.

Reviewer

[ ] Checklist review: Did you go through the code with the Code Review Guidelines checklist?
[x] Ad hoc review: Did you perform an ad hoc review?  In addition to a first pass using the code review guidelines, do a second pass using your best judgement and experience which may identify additional questions or comments. Research shows that code review is most effective when done in multiple passes, where reviewers look for different things through each pass.
[ ] Automated tests: Did you review the automated tests?
[ ] Manual tests: Did you review the manual tests?You will find manual testing guidelines under our manual testing section
[ ] How is Code Coverage affected by this PR? We encourage you to compare coverage before and after your changes and when possible, leave it in a better place. Learn More...
[ ] Documentation: Did you review Docs, README.md, LICENSE.md, and Architecture.md as appropriate?
[ ] Run the app: Did you run the app and try the changes? While the CI server runs the app to look for build failures or crashes, humans running the app are more likely to notice unexpected log messages, UI inconsistencies, or bad output data.

utACK. Ideally the back button changes and the TCA updates would have been in separate PRs to make this a little easier to understand, but I guess the TCA updates are being done incrementally?

True, the scope of the ticket itself is "just" to make the back button at the top. We've been behind TCA latests version for a long time and it's bigger and bigger issue so I incrementally update views and stores/reducers whenever I'm supposed to do some UI task. It's an incremental change because the rest can stay in a deprecated state. Ideally I have time to update the whole Zashi but I don't think such time will come anytime soon.


Adding exit poll options

Leap of faith, "looks good to me" review.

Yeah, more just wanted to let you know I'm merging it to main


Show jar total amount in detail view

Per #517, I added total balance next to the tab selector so that it will be always visible.

Hey @httpiga, thanks for your contribution  - nice!
There is already a place where the balance is shown if you select individual utxos. Would it make sense to move the total balance to the same position (if no utxo is selected)?

I am asking because there is also a task related to improving the header. See https://github.com/joinmarket-webui/jam/issues/528.

I like the input, edited my screen

I really like @editwentyone design, what do you think if we merge it with my consideration (assuming you agree with this) and we put total amount info below jar name?

:+1: from me!
ping @editwentyone

@httpiga I would like to keep the header clean, the total amount is now under "details" and "utxos" visible
please check the Figma file, you can have a better understanding where we are heading: link

hm you are right, its not including the internal ones. will need to rethink it a little bit more, thanks for the hint

Do you think that's better pausing this PR while waiting for an updated design, or merge this just to have it and refactor later?

Would you be okay with moving it to the place the current figma files suggest, i.e. having it only on the "Jar" tab for now, and then adding it to "Details" tab in a follow-up PR?
I think it is fine either way, we can also merge it now if you prefer that!

Okay, next week I'm going to move the total amount to the "UTXOs" tab like the Figma suggest!

Hey @httpiga, still motivated to get this feature in? :orange_heart:

Hey, sorry for having disappeared but had un unexpected busy period - I'll be glad to implement this as soon as I can!

Don't worry. Glad you are still interested. Please know, that there is absolutely no urgency involved. Take your time!

Thank you for your patience, what about this?

Nice! :orange_heart:

Bitcoin amount is not bold since the font weight in BalanceComponent is forced at 400 by slashed-zeroes class name, which is used also by other components. Do we want to refactor BalanceComponent to use Bootstrap classes?

What do you think about merging it and doing the refactoring in a follow-up PR?
Of course, only if you are motivated to do so!


welcome message inline chat link doesn't work

VS Code Version: 1.85 Insiders, Copilot Chat pre-release
OS Version: Windows 11

The link is using an obsolete command ID workbench.action.quickchat.launchInlineChat
Command ID should be inlineChat.start

We no longer include a command link since we cannot start an inline chat session if you don't have a file open already, the welcome message content is restored from history but if you click on the + you should see the newest content


slightly worse p@1 than results in xml-cnn paper

My two runs of the code showed
-------------- Best Epoch: 16 (p@1: 0.95296472311019897461) -------------
-------------- Best Epoch: 14 (p@1: 0.95154267549514770508) -------------
This p@1 result is slightly worse than the 96.86 presented
in the xml-cnn paper. Do you think the reason is because
of the slightly different tokenization?
Indeed I think as yours used more tokens, more information is used
and results should be as good?
Thanks

Hello! Thank you for your issue.
I'll answer the question you asked.
I think so too.
I think that tokenization affects the accuracy.
However, I am not the author of the XML-CNN paper, so I can't say for sure about the results in the paper.
Thanks.

Thanks. Maybe another way to confirm this is by trying more sets. I plan
to do that but would like to ask if you have done that before? (e.g.,
trying other sets such as EUR-Lex, Wiki-30K etc. used in the paper)?
Thanks
On 2021-02-12 14:46, Yusaku Goto wrote:

Hello! Thank you for your issue.
I'll answer the question you asked.
I think so too.
I think that tokenization affects the accuracy.
However, I am not the author of the XML-CNN paper, so I can't say for
sure about the results in the paper.
Thanks.
--
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub [1], or unsubscribe
[2]. [ { "@context": "http://schema.org", "@type": "EmailMessage",
"potentialAction": { "@type": "ViewAction", "target":
"https://github.com/yu54ku/xml-cnn/issues/3#issuecomment-778012019",
"url":
"https://github.com/yu54ku/xml-cnn/issues/3#issuecomment-778012019",
"name": "View Issue" }, "description": "View this Issue on GitHub",
"publisher": { "@type": "Organization", "name": "GitHub", "url":
"https://github.com" } } ]
Links:
[1] https://github.com/yu54ku/xml-cnn/issues/3#issuecomment-778012019
[2]
https://github.com/notifications/unsubscribe-auth/ABI3BHVV2555UXCOINY66KLS6TFFVANCNFSM4XQEIWNA

I haven't tried any other datasets with this program.
Therefore, we don't know the results regarding them.
We also have a problem with Precision@k.
The method of calculating Precision@k has been shown in various ways in various papers and various programs.
Therefore, it's unlikely that we'll ever know which Precision@k was used by Liu et al.
In other words, it would be impossible for us to obtain exactly the same results as Liu et al.


itest flake: process did not exit

Seen from this build,
--- FAIL: TestLightningNetworkDaemon/tranche03/64-of-82/bitcoind/delete_macaroon_id (69.29s)
lnd_test.go:223:
            Error Trace:    lnd_test.go:223
                                        lnd_test.go:246
            Error:          Received unexpected error:
                            process did not exit
            Test:           TestLightningNetworkDaemon/tranche03/64-of-82/bitcoind/delete_macaroon_id

Closed due to fat finger and slow VPN...


feat(memory) Memory views support slice assignment

When writing view = memory.uint8_view() for instance, it is now
possible to set a sequence directly by writing:
view[start:stop:step] = sequence

instead of writing a loop like:
for nth in range(0, length):
    view[nth] = sequence[nth]

First, __setitem__ takes 2 forms of inputs: Either the key and value
are both integers, or they are respectively a slice and a sequence. By
“sequence”, we mean the object protocol
sequence, so it
includes list, bytes, bytearray etc.
Second, let's focus on the new feature where key and value are a slice
and a sequence:

The sequence item type must be down-castable to the memory item
type, e.g.  if it is a uint8 view, then the item must be
down-castable to u8, and so on.

The slice is bound to the memory view length, so that it's
impossible to write out-of-memory.

The slice accepts start, stop, and step parameters. So it is
possible to write view[0:5:2] for instance, and it will write at
positions 0, 2, 4. Stop must be greater than start. Step must be
positive.

There is a huge difference with list slice assignment: Elements in
memory cannot be moved, so the assignment only overwrite
elements. For instance, with a regular list:
a = [1, 2, 3, 4, 5]
a[1:3] = [10, 11, 12]

assert a == [1, 10, 11, 12, 4, 5]

In the example above, the list [10, 11, 12] replaces the slice
1:3, so it replaces the elements [2, 3] by [10, 11, 12]
With memory view, we can't move elements (no inserts, no
deletions). It overwrites them, e.g.:
view[0:5] = [1, 2, 3, 4, 5]
view[1:3] = [10, 11, 12]

assert view[0:5] == [1, 10, 11, 4, 5]

What happens here?

The slice and the sequence iterators are zipped together. As soon
as one iterator finishes, __setitem__ stops writing into the
memory view. In the example above, the slice iterator is shorter
than the sequence iterator (the length of the slice iterator is 2,
while the length of the sequence iterator is 3, so only 2 elements
will be written).

So 2 elements are picked from the sequence, i.e. [10, 11]. They
are written in positions given by the slice, here 1 and 2. The
memory then looks like [1, 10, 11, 4, 5].

Another example with a step > 1 in the slice:
view[0:5] = [1, 2, 3, 4, 5]
view[1:5:2] = [10, 11, 12]

assert view[0:5] == [1, 10, 3, 11, 5]

What happens here?

The length of the slice iterator is 2, so the first two elements
of the sequence will be picked, i.e. [10, 11].

The positions given by the slice are 1 and 3. The memory then
looks like [1, 10, 3, 11, 5]. Positions 0, 2 and 4 are
unmodified.

Benchmarks show an improvement of a factor 10,
i.e. it is 10 times faster to use slice assignment than a loop
assignment. Results of just benchmark test_memory_view_set.py:

Name (time in us)
Min
Max
Mean
StdDev
Median
IQR
Outliers
OPS (Kops/s)
Rounds
Iterations

…_with_slice_assignment
6.8870 (1.0)
73.8030 (1.0)
7.5302 (1.0)
1.8991 (1.0)
7.2790 (1.0)
0.2390 (1.0)
477;3204
132.7992 (1.0)
24459
1

…_with_a_loop
68.1770 (9.90)
412.7400 (5.59)
73.6944 (9.79)
10.1384 (5.34)
71.7810 (9.86)     2.7390 (11.46)
601;1050
13.5696 (0.10)
13048
1

bors r+


Publish Module to the gallery

Make the module more accessible by uploading it to the gallery.
Dependencies: #3 #4

Version 1.0.0 is now published to the gallery.


[Event Request] Codeunit 7009 "CopyFromToPriceListLine" - Function "InitLineNo" - New Event OnAfterInitLineNo

Hello, we need the possibility to extend the Function "InitLineNo" on "CopyFromToPriceListLine" Codeunit 7009 as follows:
    procedure InitLineNo(var PriceListLine: Record "Price List Line")
    var
        PriceListManagement: Codeunit "Price List Management";
    begin
        if PriceListLine.IsTemporary then
            PriceListLine."Line No." += 10000
        else begin
            SetPriceListCode(PriceListLine);
            PriceListLine.SetNextLineNo();
            if GenerateHeader and UseDefaultPriceLists and (PriceListLine."Line No." > GetMaxPriceLineNo()) then begin
                PriceListLine."Price List Code" :=
                    PriceListManagement.DefineDefaultPriceList(PriceListLine."Price Type", PriceListLine."Source Group");
                PriceListLine.SetNextLineNo();
            end;
        end;

        //new-s
        OnAfterInitLineNo(PriceListLine);
        //new-e

    end;

    [IntegrationEvent(false, false)]
    local procedure OnAfterInitLineNo(var PriceListLine: Record "Price List Line")
    begin
    end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 10050.


Merge develop from Release 2.4 into master to fix history

With Release 2.3 and 2.4 the develop branch has been merged into master with a squash. This brings the problem that develop and master don't share the same history anymore and any furter merge from develop to master will show more commits then where actually made.
To fix this situation non invasively, the current master should be merged with the corresponding commit from develop to sync the history again.
develop commit: 7f43f484407d6efa89ca45a9a5941d3f439d598a
There are no file changes so its the same source code state. Its just for syncing history.
Any future release must not be merged with a squash.
Should be merged right before https://github.com/MiczFlor/RPi-Jukebox-RFID/pull/2030
@s-martin

Any future release must not be merged with a squash.

Maybe it won't hurt to disable this merge strategy completely in the repo settings?


Open multiple ECM streams within single ECM_channel_id

Hi there,
Here is what is happening:
[root@rhel9dev release-x86_64-rhel9dev]# tsp -I file astra-10847V-2020-08-24.ts --infinite -P scrambler PORTADA --ecmg <IP_ADDRESS>:2222 -d 5 --super-cas-id 0x07001001 --access-criteria<PHONE_NUMBER> > /dev/null &
[1] 139485
[root@rhel9dev release-x86_64-rhel9dev]#
[root@rhel9dev release-x86_64-rhel9dev]# tsp -I file astra-10847V-2020-08-24.ts --infinite -P scrambler PORTADA --ecmg <IP_ADDRESS>:2222 -d 5 --super-cas-id 0x07001001 --access-criteria<PHONE_NUMBER> --stream-id 2 -i 2 > /dev/null &
[2] 139666
[root@rhel9dev release-x86_64-rhel9dev]# * Error: scrambler: unexpected response from ECMG (expected channel_status):
    channel_error (ECMG<=>SCS)
    protocol_version = 0x02
    message_type = 0x0005
    ECM_channel_id = 0x0001
    error_status = 0x0013 (ECM_channel_id value already in use)

My tsecmg is running on server <IP_ADDRESS> and tsp with scrambler plugin is running on <IP_ADDRESS>.
I opened new channel (default channel_id) and default stream_id.
When i try to open new stream_id within same channel_id i get above error.
As per DVB Simulcrypt protocol:

There can be multiple streams (with unique stream_id) within a given channel_id --> This is giving error.
There can be only one channel_id on TCP connection --> This is not giving error, i am able to open multiple channel_id with same tsecmg server e.g.: below command works fine:
[```
root@rhel9dev release-x86_64-rhel9dev]# tsp -I file astra-10847V-2020-08-24.ts --infinite -P scrambler CONTRATO --ecmg <IP_ADDRESS>:2222 -d 5 --super-cas-id 0x07001001 --access-criteria<PHONE_NUMBER> --channel-id 3 > /dev/null &
[3] 144915
[root@rhel9dev release-x86_64-rhel9dev]#
[root@rhel9dev release-x86_64-rhel9dev]# tsp -I file astra-10847V-2020-08-24.ts --infinite -P scrambler CONTRATO --ecmg <IP_ADDRESS>:2222 -d 5 --super-cas-id 0x07001001 --access-criteria<PHONE_NUMBER> --channel-id 4 > /dev/null &
[4] 144994
[root@rhel9dev release-x86_64-rhel9dev]# tsp -I file astra-10847V-2020-08-24.ts --infinite -P scrambler CONTRATO --ecmg <IP_ADDRESS>:2222 -d 5 --super-cas-id 0x07001001 --access-criteria<PHONE_NUMBER> --channel-id 5 > /dev/null &
[5] 145025

Am i missing something here?

I want to have multiple streams within a given channel (just like commercial MUX/SCS will do..).

Thanks, kamari

I want to have multiple streams within a given channel (just like commercial MUX/SCS will do..).

There is a misunderstanding here.
A channel identifies one TCP connection. Each TCP connection shall have only one unique channel_id. Two simultaneous TCP connections on one ECMG cannot have the same channel_id. This is the case you run into. Two TCP connections from two clients connect to the same ECMG and declare the same channel_id. This is an error and the second one is rejected with error status 0x0013. This is the normal behaviour and I doubt than any commercial ECMG allows that. And if one allows that, this is a bug in the ECMG.
You have to understand that rejecting two simultaneous TCP connections with the same channel_id is important for the redundancy in some configurations. This is true in all DVB SimulCrypt protocols. The protocol for which it is even more important is EMMG/PDG <=> MUX. Typically, two identical redundant clients (one being able to take over in case of failure of the other one) use the same channel_id (on purpose). The first one is accepted and does the job. The second one connects and is rejected with "channel_id value already in use". Then, it periodically tries to reconnect again and again, endlessly. If, at some point, the connection succeeds, this means that the main client crashed or stopped and the new connection acts as a replacement. The failed clients will restart, try to reconnect, fail with "channel_id value already in use" because the second one took over. The first one naturally becomes a backup, endlessly trying to connect with the channel_id until it is accepted again. And so on...
Now, the standard specifies that you may have several streams inside one channel. This means that one client can multiplex several streams inside the same TCP connection. The stream_id is used to identify each stream of data inside the same channel, the same TCP connection.
In short:

Distinct TCP connections must have distinct channel_id.
Distinct streams inside the same TCP connection must have distinct stream_id.
Two streams inside two distinct TCP connections may have the same stream_id. They are still distinct streams because a stream is a subcomponent of a channel.

You do the exact opposite:

Distinct connections have the same channel_id.
Two streams from distinct connections have distinct stream_id.

Typically, a commercial SCS is a central equipment and may manage the encryption of many services using one single TCP connection to the ECMG, and consequently one channel_id. Each service, or more precisely each scrambling group, is handled in one stream_id.
TSDuck is not a commercial equipment. This is a lab toolkit to test and debug equipment integration or other demo or test situations. The scrambler plugin can scramble only one service and directly acts as an SCS, without going through a central SCS system. In such test configuration, each scrambler plugin is an individual SCS able to manage only one service. If several of them connect to the same ECMG (whether it is the test tool tsecmg or a commercial ECMG from an renown CAS vendor), they are considered as distinct clients and they must use distinct channel_id values.

Hi Thierry,
---------------first point-------------------
ts-101197 states:

There is always one (and only one) channel per TCP connection.

It is different (and/or even incorrect) to say:

Each TCP connection shall have only one unique channel_id. Two simultaneous TCP connections on one ECMG cannot have the same channel_id

The standard limits one (and only one - even if other channels are having different) channel_id per TCP socket connection. Since the tool allows to open two channel (with different channel_id), this is what i referred to in my original comment (apologies if it was not clear enough).
---------------second point-----------------
Thanks for this explanation:

TSDuck is not a commercial equipment. This is a lab toolkit to test and debug equipment integration or other demo or test situations. The scrambler plugin can scramble only one service and directly acts as an SCS, without going through a central SCS system. In such test configuration, each scrambler plugin is an individual SCS able to manage only one service. If several of them connect to the same ECMG (whether it is the test tool tsecmg or a commercial ECMG from an renown CAS vendor), they are considered as distinct clients and they must use distinct channel_id values.

I truly want to use TSDuck to test and debug my ECMG to check whether it can handle the ECM load (as i envision it to support) without opening multiple channel_id.
Is there a way (or work-around) that you can suggest on how can i test / general 8000 ECM streams?
is there a way i can create channel class and add/attach streams to the channel_class separately?

Every new channel connection consumes around ~15% of my 6-core VM which limits me to open 6 channel_id's.
Do you think if i use a shorter .ts input file, i will consume less cpu?

Every new channel connection consumes around ~15% of my 6-core VM

Do you mean scrambling load or ECMG load?
Just testing on a Ubuntu VM running on a core i7 laptop. Using a 3.3 Mb/s service: scrambling using DVB-CSA2 uses 24% of the CPU, scrambling using DVB-CISSA (AES) uses 4% of the CPU. This is the expected ratio. DVB-CSA is notoriously (and purposely) slow in software while AES is quite fast.
Note that the commands you mention in the top post are not realistic on a scrambling standpoint. You use an unregulated input, a file. So, the source has an "infinite" bandwidth, only limited by the I/O and CPU capability. I would even anticipate 100% CPU load per service. To test in real conditions, you have to add -P regulate before the scrambler.

Is there a way (or work-around) that you can suggest on how can i test / general 8000 ECM streams?

The load on the ECMG is very low compared to the scrambling load. The scrambling load is thousands of times higher than the ECMG load. And the higher the bitrate of the service, the higher scrambling load of course.
If you want to push the ECMG load to the limit using real scrambling, you will create an unmanageable scrambling load. In your case, scrambling 8000 average services with DVB-CISSA would require 400 to 500 i7 cores.
So, pushing an ECMG to that limit is not feasible using real scrambling, neither tsp nor physical commercial scramblers ($$$).
For that kind of test, you need to develop a special test application where you open one or more connections to the ECMG with many streams inside each connection. In the real world, a scrambler needs one ECM every 10 seconds per service. With 8000 services, you need to request a global load of 800 ECM/second. Of course, for that test, you request the ECM's but you never use the returned ECM's and your never scramble anything. On an ECMG perspective, only the ECM request load is important, not what you do with the returned ECM's.
So, you need to develop a C++ application using the TSDuck library.
Simple solution: Use the class ts::ECMGClient to connect to the ECMG. Its method generateECM() is easier to use. It synchronously requests an ECM. See the source code for tsgenecm for a simple example. However, this class is simple and limited to one stream per channel. So, you need to instantiate 8000 times this class. Of course, you may distribute the load over multiple instances of the test application, running on several systems if necessary.
Better solution: Use the class ts::tlv::Connection and TLV messages. You have to manipulate all ECMG<=>SCS messages yourself but you can open as many streams as you want per channel / connection. More generic but less easy.

Hi Thierry,
Awesome and thank you for -P regulate option. My workload has almost gone to 0% from ~20% for single instance of tsp for scrambling 1 service. When i run 7 scrambling instances, now i only need ~7% of CPU -- this is great.
I will try to go for 2nd method ts::tlv::Connection as it is closer to my requirement - multiple streams within same channel_id.
if i fail to do so, then my plan-B is to create 8000 channels to simulate the load on ECMG side.
Thanks a ton for all your help!

plan-B is to create 8000 channels to simulate the load on ECMG side

In that case I would recommend to use super-low bitrate services, less that 1kb/s. That will significantly reduce the scrambling load. And of course use DVB-CISSA, not DVB-CSA.


feat: add new api endpoint to check for deleted spaces

Goal
Add a new POST /api/delete-spaces endpoint, which accept a list of ENS names ['a.eth', 'b.eth'], and return a JSON list of deleted spaces like ['a.eth'], or just [] if none of the input are deleted spaces
This additional endpoint will avoid having to burden the graphql queries, which does not handle deleted spaces by default.
Why
UI does not have a way to check for deleted spaces.
Having that list will allow UI to show filter deleted spaces from the 'Create space' form, and avoid having user completing all the space creation steps, until to get the error "Space deleted, please contact admin" at the end of creation process.
This will lighten the support, which is today getting at least one ticket per week about this error.
See https://github.com/snapshot-labs/snapshot/issues/4516 for UI proposed implementation

@ChaituVR and @bonustrack , what do you think ?

Sounds good to me


[Revise subclass]  inherited fatty acid metabolism disorder (MONDO:0037858)

Mondo term (ID and Label)
inherited fatty acid metabolism disorder (MONDO:0037858)
Suggested revision and reasons
is positioned under
inborn organic aciduria MONDO:0000688
which is under
inborn disorder of amino acid metabolism (MONDO:0004736)
fatty acid is not an amino acid, this brings all fatty acid metabolism disorders under amino acid.
Your nano-attribution (ORCID)
If you don't have an ORCID, you can sign up for one here

Dear @ValWood,
Thank you for reaching out to the Mondo Disease Ontology, part of the Monarch Initiative!
We have received your ticket and will review it as soon as possible.
If you have any additional information or updates relevant to your inquiry, please add them in a comment on this ticket. Your input is valuable in helping us understand and resolve the issue effectively.
Thank you for your patience and for your contributions to Mondo!
Sincerely,
The Mondo Team

Hey, Ontobot!

delete edge MONDO:0037858 rdfs:subClassOf  MONDO:0000688

Hi @ValWood - I think this was addressed - these are the current parents of inherited fatty acid metabolism disorder (MONDO:0037858):

Does this look okay to you? Can this ticket be closed or is more action needed? Thanks!

Hi @nicolevasilevsky, yes, that is addressed. Thanks!


Update to pre-release package:intl breaking customer_tests

A recent pub autoroll revved package:intl 0.17 -> 0.18 https://github.com/flutter/flutter/pull/117150 while flutter/gallery and some of its dependencies pin intl: ^0.17.0. Thus in the customer_tests pre-submit checks, flutter pub get fails to resolve in the gallery and super editor.
To unblock the roll, I will pin package:intl. To unpin, all customer test apps and their transitive dependencies that are caret depending on package:intl should be updated to not constrain them, since an exact pin constraint will be provided by the flutter sdk repo.

https://github.com/superlistapp/super_editor/pull/895 opened to unblock

Note the policy update to flutter/tests to try to avoid this situation in the future: https://github.com/flutter/tests/pull/192

The super_editor upstream PR was landed. However, I am still blocked by:

flutter/gallery depends on intl: ^0.17.0
flutter/gallery depends on flutter_localized_locales ^2.0.3 (which hasn't been updated in 7 months)
flutter_localized_locales depends on intl: 0.17.0
flutter_localized_locales depends on [cupertino_icons](https://github.com/flutter/packages/blob/main/third_party/packages/cupertino_icons/pubspec.yaml): ^0.1.3
cupertino_icons depends on dart sdk ">=2.12.0 <3.0.0", which does not version solve with the Dart SDK in the latest flutter SDK

To fix would require:

updating the Dart SDK constraint in cupertino_icons
publishing a new pub release of cupertino_icons
updating cupertino_icons and intl constraints in flutter_localized_locales
publishing a new pub release of flutter_localized_locales
updating flutter/gallery with new constraints for intl and flutter_localized_locales
roll new gallery to flutter/tests
remove pin of intl in flutter tool and upgrade all packages

Actually, blocker #5 might actually be https://github.com/dart-lang/pub/issues/3686

@guidezpl could you help unblock this by removing the constraint on package:intl to the new flutter gallery and its dependencies?

As the owner of package:intl, is there anything I can do to help? Or are the items in the list above already being addressed?

Any updates for this?

Of course! I've done 3. and 4., 5. will be done with flutter/gallery#864.

Awesome, lemme pick up the thread and roll the gallery.

Hi!
flutter_localizations still with 0.17.0
This could be solve in this issue or in another?

Hi! flutter_localizations still with 0.17.0 This could be solve in this issue or in another?

not sure what blob that is, but it's old. This is fixed at HEAD https://github.com/flutter/flutter/blob/main/packages/flutter_localizations/pubspec.yaml#L11

Ooh you are right, sorry
This will be release in next Flutter major update?

Ooh you are right, sorry This will be release in next Flutter major update?

It will be in a stable release eventually; I can't say whether or not it will be in the next one, but most likely.

Hi! flutter_localizations still with 0.17.0 This could be solve in this issue or in another?

not sure what blob that is, but it's old. This is fixed at HEAD https://github.com/flutter/flutter/blob/main/packages/flutter_localizations/pubspec.yaml#L11

But I still cannot use flutter_localization with intl ^0.18.0
Here is output:
Running "flutter pub get" in my_project...
Resolving dependencies...
Because my_project depends on flutter_localizations from sdk which depends on intl 0.17.0, intl 0.17.0 is required.
So, because my_project depends on intl ^0.18.0, version solving failed.

But if I run flutter update-packages --force-upgrade it had worked. I think it's not a good solution 'cause if I reinstall or upgrade Flutter SDK so I cannot run pub get again, then I have to run command above again.
Have you a good solution? Thank you.

Hi! flutter_localizations still with 0.17.0 This could be solve in this issue or in another?

not sure what blob that is, but it's old. This is fixed at HEAD https://github.com/flutter/flutter/blob/main/packages/flutter_localizations/pubspec.yaml#L11

But I still cannot use flutter_localization with intl ^0.18.0
Here is output:
Running "flutter pub get" in my_project...
Resolving dependencies...
Because my_project depends on flutter_localizations from sdk which depends on intl 0.17.0, intl 0.17.0 is required.
So, because my_project depends on intl ^0.18.0, version solving failed.

But if I run flutter update-packages --force-upgrade it had worked. I think it's not a good solution 'cause if I reinstall or upgrade Flutter SDK so I cannot run pub get again, then I have to run command above again.
Have you a good solution? Thank you.

I'm guessing you're using a release of Flutter that does not yet have the fix. You have two options:

Switch to a newer version of the Flutter SDK (such as the current beta release https://github.com/flutter/flutter/blob/beta/packages/flutter_localizations/pubspec.yaml#L11)
update my_project to depend on intl: any. This will satisfy flutter pub get, as it will use the exact pin of whatever Flutter SDK you aren't currently using.

Hi! flutter_localizations still with 0.17.0 This could be solve in this issue or in another?

not sure what blob that is, but it's old. This is fixed at HEAD https://github.com/flutter/flutter/blob/main/packages/flutter_localizations/pubspec.yaml#L11

But I still cannot use flutter_localization with intl ^0.18.0
Here is output:
Running "flutter pub get" in my_project...
Resolving dependencies...
Because my_project depends on flutter_localizations from sdk which depends on intl 0.17.0, intl 0.17.0 is required.
So, because my_project depends on intl ^0.18.0, version solving failed.

But if I run flutter update-packages --force-upgrade it had worked. I think it's not a good solution 'cause if I reinstall or upgrade Flutter SDK so I cannot run pub get again, then I have to run command above again.
Have you a good solution? Thank you.

I'm guessing you're using a release of Flutter that does not yet have the fix. You have two options:

Switch to a newer version of the Flutter SDK (such as the current beta release https://github.com/flutter/flutter/blob/beta/packages/flutter_localizations/pubspec.yaml#L11)
update my_project to depend on intl: any. This will satisfy flutter pub get, as it will use the exact pin of whatever Flutter SDK you aren't currently using.

Thanks for the answer. I use stable release of Flutter (3.7.5) and might not have the fix of this issue. So I downgrade the intl to previous version (0.17.0).
FYI: I used Flutter 3.7.3 before and runs flutter pub outdated. It shows intl package have new update version 0.18.0 on resolvable column. So I decide to upgrade it then the error appeared. After run flutter update-packages --force-upgrade the error was fixed but today I upgrade Flutter to 3.7.5 it reset again and shows error incompatible version of intl that I described above. Now, I downgrade intl to 0.17.0 then run flutter pub outdated it shows intl package only have version 0.18.0 on latest column, not resolvable. It's like joking to me LOL.

FYI: I used Flutter 3.7.3 before and runs flutter pub outdated. It shows intl package have new update version 0.18.0 on resolvable column.

Hmm, this actually sounds like a bug that it would not try to solve against package:flutter dependencies.

After run flutter update-packages --force-upgrade the error was fixed but today I upgrade Flutter to 3.7.5 it reset again and shows error incompatible version of intl that I described above.

This command is intended only for maintainers. Of course, Flutter is open source, nothing is stopping you from doing this, however, you've voided your warranty (this is effectively changing the Flutter SDK to an untested version), and if you file bugs on the issue tracker SDK maintainers will tell you to revert your changes.
The officially supported way to get package:intl version 0.18.0 would be to switch to a newer version of the Flutter SDK, such as the newest beta.


[WIP] Remove unused record types

Purpose

Resolves https://github.com/ballerina-platform/ballerina-openapi/issues/405
Resolves https://github.com/ballerina-platform/ballerina-openapi/issues/423

Goals

Describe the solutions that this feature/fix will introduce to resolve the problems described above

Approach

Describe how you are implementing the solutions. Include an animated GIF or screenshot if the change affects the UI (email<EMAIL_ADDRESS>to review all UI text). Include a link to a Markdown file or Google doc if the feature write-up is too long to paste here.

User stories

Summary of user stories addressed by this change>

Release note

Brief description of the new feature or bug fix as it will appear in the release notes

Documentation

Link(s) to product documentation that addresses the changes of this PR. If no doc impact, enter “N/A” plus brief explanation of why there’s no doc impact

Training

Link to the PR for changes to the training content in https://github.com/wso2/WSO2-Training, if applicable

Certification

Type “Sent” when you have provided new/updated certification questions, plus four answers for each question (correct answer highlighted in bold), based on this change. Certification questions/answers should be sent to<EMAIL_ADDRESS>and NOT pasted in this PR. If there is no impact on certification exams, type “N/A” and explain why.

Marketing

Link to drafts of marketing content that will describe and promote this feature, including product page changes, technical articles, blog posts, videos, etc., if applicable

Automation tests

Unit tests

Code coverage information

Integration tests

Details about the test cases and coverage

Security checks

Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes/no
Ran FindSecurityBugs plugin and verified report? yes/no
Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes/no

Samples

Provide high-level details about the samples related to this feature

Related PRs

List any other related PRs

Migrations (if applicable)

Describe migration steps and platforms on which migration has been tested

Test environment

List all JDK versions, operating systems, databases, and browser/versions on which this feature/fix was tested

Learning

Describe the research phase and any blog posts, patterns, libraries, or add-ons you used to solve the problem.

More scalable solution is provided in https://github.com/ballerina-platform/ballerina-openapi/pull/444


feat: Add review command to perform custom summarizations

Description

Testing

Additional context

Codecov Report

Merging #54 (36dad8b) into main (7c3a44c) will decrease coverage by 3.34%.
The diff coverage is 76.36%.

@@            Coverage Diff             @@
##             main      #54      +/-   ##
==========================================
- Coverage   88.16%   84.83%   -3.34%
==========================================
  Files          11       13       +2
  Lines         338      389      +51
  Branches       47       59      +12
==========================================
+ Hits          298      330      +32
- Misses         25       44      +19
  Partials       15       15

Flag
Coverage Δ

integration
?

unittests
?

unittests-3.10
84.83% <76.36%> (-1.56%)
:arrow_down:

unittests-3.11
84.83% <76.36%> (-1.56%)
:arrow_down:

unittests-3.8
84.83% <76.36%> (-1.56%)
:arrow_down:

unittests-3.9
84.83% <76.36%> (-1.56%)
:arrow_down:

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

Impacted Files
Coverage Δ

src/gpt/__main__.py
0.00% <0.00%> (ø)

src/gpt_review/__main__.py
0.00% <0.00%> (ø)

src/gpt_review/main.py
0.00% <0.00%> (ø)

src/gpt_review/_review.py
92.23% <95.12%> (+1.60%)
:arrow_up:

src/gpt_review/__init__.py
100.00% <100.00%> (ø)

src/gpt_review/_gpt_cli.py
100.00% <100.00%> (ø)

... and 2 files with indirect coverage changes


Eliminate mentions of the unused "JD_PRIVATE" conditional compilation macro

Unused "JD_PRIVATE" conditional compilation macro is mentioned in the sources #3024

Used by internal build configurations.

@ddv239 no need to constantly merge master, it unnecessarily loads up extra builds in the CI queue for no benefit. Additionally, if there's a merge conflict with the target branch, we prefer rebasing: https://github.com/Microsoft/ChakraCore/blob/master/CONTRIBUTING.md#housekeeping "Your pull request should ... Be a child commit of a reasonably recent commit"

I didn't know I should not update; it suggested so.

Unfortunately, we can't tell GitHub not to show that message. It's an understandable action to take. In our case, there is usually no benefit to doing so.


I think the website may have died

Cant navigate around the website :/

Hi @MortenDHansen
Thanks for reporting this bug.
I have noticed it too. Since updating to a newer VuePress version, whenever a new built is created the "Refresh content" pop-up no longer shows and navigation is broken.
For now, a hard refresh (control/cmd + shift + R) seems to fix the problem.
I'll leave this issue open as a reminder that this is something that needs to be addressed.

@MortenDHansen Please let me know if you can work around it for now using the hard refresh method.

Not a problem. I was actually reading it here on github instead 😄  - just wanted to flag it 🙂


Permissions default to disabled on Firefox

The 'Access your data for sites in the...' permissions are optional and have to be manually enabled for the extension to work which is confusing. This doesn't happen on Chromium or with versions of the extension before the Manifest v3 migration.

This only affected the old version of Firefox (ESR 115) on Debian which has since been updated.


Ensure enum column types do not prevent editing tables in mysql datab…

In my experience working with enum types in Mysql, this problem with Voyager vs Enum types usually arise when progressively porting legacy code bases to Voyager.
While it is clear not to use enums, porting progressively as described above becomes difficult since Voyager currently does not allow any tables with enum cols to be edited (which usually the purpose of editing the schema may not even be about the enum col).
This PR is my attempt to resuscitate #1923. Since doctrine are stateless, I took a hint from the recommended fix, which is easy because Voyager already has such abstraction.
I believe that if this PR is accepted as the right step in the right direction, it is only a matter of time before the UI and other components of Voyager will completely support enum types.

@the-control-group pls merge! :)

It works!


How to set 'publicPath' in webpack after 'deployUrl' option is deprecated in version 15

https://github.com/angular/angular-cli/blob/5402f99f8ad20e0a57456a416a992415fc6332bd/packages/angular_devkit/build_angular/src/webpack/configs/common.ts#L335

That's also an issue for us. We have a widgets application that contains multiples lazy loaded custom elements. These elements are used in other applications. When some element want to load an image it should be loaded from the widgets domain, not from the current one that belongs to main application. Currently this can be achieved by using deploy-url during widgets app build. How to do it without this option?

@feng-xiao, can you please elaborate on why you need the deployUrl option and the specific use-case?
@artaommahe, is the image located in component stylesheet or external stylesheet?

@alan-agius4 in component's scss and html files

@artaommahe, in that case there is no alternate option for that. One thing to point out is that this aligns the behaviour of images defined in HTML and CSS, which results in images URI HTML to always be relative to HTML.
What comes to mind is to have an external CSS file (styles.css) that you defined the image in, since images are loaded relative to the stylesheet origin. Though this might be a bit cumbersome.

@alan-agius4 using global css file breaks lazy loading of such stuff, locality of code (images of some component from one of the widgets lib somehow are placed in global styles file).
This looks strange due to availability of official @angular/elements and breaks their usage for micro-frontend cases.

If the assets can be referenced from the component templates instead, another option is to generate the full asset URL at runtime via the use of import.meta.url.  This is similar in functionality to the deprecated deploy URL option but has the advantage of not needing to hardcode anything other than the relative path of the asset.  The JavaScript and asset files as a whole could then potentially be served from locations other than a predefined deploy URL and still function.

@feng-xiao, can you please elaborate on why you need the deployUrl option and the specific use-case?
@artaommahe, is the image located in component stylesheet or external stylesheet?

Hi @alan-agius4 , I've integrated Angular app into an ASP.NET MVC application, i.e. the Angular app is initialized by a MVC razor view. Since the Angular resources are generated and hosted in different port number in 'ng serve' mode than MVC app, e.g. ASP.NET MVC app is loaded in localhost:8444, Angular app would be loaded in different port number like localhost:8445, I need to make Angular resources loaded using absolute URL, otherwise, they'll be loaded in wrong URL, the one MVC is using (i.e. localhost:8444).

@feng-xiao, can you please elaborate on why you need the deployUrl option and the specific use-case?
@artaommahe, is the image located in component stylesheet or external stylesheet?

Hi @alan-agius4 , I've integrated Angular app into an ASP.NET MVC application, i.e. the Angular app is initialized by a MVC razor view. Since the Angular resources are generated and hosted in different port number in 'ng serve' mode than MVC app, e.g. ASP.NET MVC app is loaded in localhost:8444, Angular app would be loaded in different port number like localhost:8445, I need to make Angular resources loaded using absolute URL, otherwise, they'll be loaded in wrong URL, the one MVC is using (i.e. localhost:8444).

Hi @alan-agius4 , based on webpack's source code, I don't see any overhead by setting 'publicPath' to webpack config. I don't know why Angular Doc says it could increase build time.

@feng-xiao, the deployUrl, is used not just to set the publicPath, using deployUrl will cause additional steps including processing all CSS templates and files to append the deployUrl to the assets urls.
Another disadvantage of using deployUrl, is that the string value will be included all over the bundle multiple times, which causes an increase in bundle size and make promotion of bundles from one environment to another rather tricky.
In your cases, the recommended approach would be to use a combination of both --base-href and APP_BASE_HREF.
Razor View
...
<base href="http://localhost:8445/">
...

app.module.ts
...
{ provide: APP_BASE_HREF, useValue: 'http://localhost:8444' }
...

We heavily use too the deployUrl parameter. For us, it's because we have a reverse proxy that proxy all requests under /static if the load is too high to a dedicated apache server, because with serve requests through a tomcat server.
Whith the deployUrl whe currectly have
<!DOCTYPE html><html lang="fr">
  <head><base href="/tool/path/">
    <meta charset="utf-8">
    <title>My application...</title>
    <meta name="viewport" content="width=device-width, initial-scale=1">
    <link rel="icon" type="image/png" href="static/favicon.png">
    <link rel="stylesheet" href="static/styles.8277a10e7c2be6c58f14.css" media="print" onload="this.media='all'">
</head>
<body>
    <app-root>loading...</app-root>
<script src="static/runtime-es2017.5a110097badef840dfda.js" type="module" crossorigin="use-credentials"></script>
<script src="static/runtime-es5.5a110097badef840dfda.js" nomodule defer></script>
<script src="static/polyfills-es5.1f50460b6153455d79c6.js" nomodule defer></script>
<script src="static/polyfills-es2017.acf5917270495d93417a.js" type="module" crossorigin="use-credentials"></script>
<script src="static/main-es2017.f3526c48e4006bc6f2e3.js" type="module" crossorigin="use-credentials"></script>
<script src="static/main-es5.f3526c48e4006bc6f2e3.js" nomodule defer></script>
</body>
</html>

If this parmater is removed, we're just screwed :/

Our dev build relies on deployUrl to properly set resource URLs for ng serve, since we're not using a proxy (and don't want to), we simply link files from https://localhost:4200 from our .cshtml file. Removing the option from ng serve settings made me create an additional builder definition, where I still able to set this to https://localhost:4200 and everything works. Removing the option from builder settings will ruin our set up.

Same for me , in asp.net loaded from index.cshtml like mpalourdio... would break everything...
( application is deployed on premise so the url is not known before deployment )
Now it tries to load scripts and assets from the root web folder while it should load from a sub folder (so security can be set on the application to allow only downloading scripts and assets from subfolder).

I have mentioned my use-case in https://github.com/angular/angular-cli/issues/22208
Currently I am using the following option for building the application,
"scripts": {
    ...
    "build": "node --max_old_space_size=5048 ./node_modules/@angular/cli/bin/ng build --base-href=/portal/ --deploy-url=/portal/public/ --configuration production"
    ...
}

In my case, static assets needs to be load from /portal/public/<asset_path> where as routing or http request needs to fire with base-href which is /portal/.
In our case, we are doing white-listing the security for the path having public in it as it has only static assets.
What would be your recommendation in this case?
I tried with steps mentioned in https://github.com/angular/angular-cli/issues/22208#issuecomment-975312544 but the issue didnt got resolved. Please see https://github.com/angular/angular-cli/issues/22208#issuecomment-975409891

deprecation of deployUrl is now been handled in my environment with https://github.com/angular/angular-cli/issues/22208#issuecomment-975570531

Can someone explain how I can avoid having all the garbage ("main.js", "runtime.js") etc in the root folder with base href="/" when deployUrl is removed? I don't want to write a script that rewrites urls. I just want to run "ng build --watch" and get the correct result from an already running webserver when I change files.
I get this with --base-url="/" and --deploy-url="/app".
(I don't have performance issues, so… why create problems for no good reason?)

@alan-agius4 similar case as above - we're adopting module federation for some of our projects to split huge apps into smaller pieces to reduce development and deployment time cost. We have to use deploy-url to pin remote apps' css images to their domain, that is different to host's one.

@alan-agius4 Is there any hope of Angular reverting the change to deployUrl for serve targets, or should we invest in trying to find another solution?

@Blackbaud-SteveBrush, in your case you can set the deployUrl in the browser builder which will also effect ng serve.
However, this issue is related to removed deployUrl completely.
What is your use-case of using this option?

We have a similar case where we define deployUrl (in angular.json) our CDN address, which is then added to all the images and scripts (in index.html and CSS files).
This allows us to load our assets from our CDN, while sending the HTTP requests to our server (the domain that we ran at, while baseHref is '/').
Setting the baseHref to be the CDN domain (without deployUrl) causes our app to send all of the HTTP requests to the CDN instead of to our domain - which breaks the app.
Once deployUrl is deprecated, how can we keep having the CDN defined (like publicPath in WebPack) without breaking the app's HTTP requests?

We have a similar problem without deployUrl. We have had ability to serve 2 different versions, Dev served from local files and Prod served from CDN. The HTML would load files based on deployUrl + fileName while keeping the base context the same. Using baseHref would change the entire page context. In short, they are not equivalent to our use cases.

As a work around for the WebPack publicPath value you can set the global __webpack_public_path__ variable your angular entry point. I have the following in my main.ts file.
declare var  __webpack_public_path__: string;
__webpack_public_path__= 'formerValueAssignedIn_DeployUrl';

If you have different build configurations you can store the appropriate value in the './environments/environment file and have those be replaced according to the angular.json configuration.
I do want to upvote this question though because it is a breaking change without any angular specific work around. We also use asp.net mvc to host the root file (instead of the angular index.html file) so the angular distribution folder is no the same as the load point url that asp.net uses. This means that anything dynamically loaded with import will fail because it can't be resolved.

We also have a setup that is heavily dependent on deployUrl.  In our case, our developers run ng serve on localhost, but load the application on a remote development server that also contains API endpoints, as well as additional js resources unrelated to Angular. By setting deployUrl to //localhost:4200/, and leaving the baseUrl as /, we can get the behavior we need, in a way that most closely resembles our production code.
Then, for production, we deploy all of our angular code to a subdirectory dedicated to the code generated by Angular. Setting deployUrl to https://our.staticdomain.com/angular/ also perfectly suits our needs.
I'm not sure how we would handle this if we couldn't set deployUrl.

@karptonite - does setting __webpack_public_path__ instead of deployUrl solve your problem? See also this previous comment

@IgorWolbers it does seem to solve it, although I would, as you suggest, have to mess with environments to get it to work for both development and production.
But setting a webpack variable globally like that seems like a brittle solution--theoretically, an angular user could be agnostic with regard to the build system, aside from the options in angular.json.

@karptonite

it does seem to solve it, although I would, as you suggest, have to mess with environments to get it to work for both development and production.

I have it configured that way in our code and it runs well. It is the most flexible option AFAIK.

But setting a webpack variable globally like that seems like a brittle solution--theoretically, an angular user could be agnostic with regard to the build system, aside from the options in angular.json.

True but then you would likely not have this error to begin with as deployUrl never integrated with other build systems in this manner other than WebPack AFAIK.
You are correct that the solution is not elegant, it is not (well) documented, and it would be nicer to call an angular specific API that would do this for you like deloyUrl used to do. That said at least there is a work around that can be used in the interim. Let's hope that the angular team rethinks their plans for deployUrl.

@alan-agius4 Our use case is also CDN. The application itself is hosted through ASP.NET, where style and scripts are from CDN. Same as few others, where base href won't help, as we don't want API traffic goes to CDN.
If we use GitHub as an example, their CSS style assets is under https://github.githubassets.com/assets/dark-xxxx.css. Their script is also from similar location. Such as https://github.githubassets.com/assets/chunk-frameworks-xxxx.js.
Where GitHub's route is under https://github.com/angular/angular-cli/issues/22113.
It is common for many SPA to choose such approach. Where assets location is different to the application location. This is not unreasonable requirement, also with CI/CD, how many really care about how long it takes to build if it is required for an essential approach they want to achieve?

We have a somewhat special use case with the Magnolia CMS, which has an SPA Editor with support for Angular. We also use SSR, which means that Angular Universal and Magnolia are running side-by-side, with the Universal-Server being the entrypoint for both e.g. website and CMS (for the authors).
When using the author pages of the CMS, Magnolia will consume the index.html and change the base-href to the current page, before returning it to the user. This in turn means that our scripts (runtime.js, vendor.js etc.) in the body won't be resolved correctly when we cannot use absolute paths.
That is why we rely on being able to specify this absolute path with deployUrl.
TL;DR
Our page can be accessed through different baseHrefs, that depend on the context from where they are accessed, and that means we need absolute paths in our resources to be able to load them from the same location all the time.

We too rely heavily on deployUrl because with the same CDN use case as i see mentioned often here, Should deprecating deployUrl perhaps be reconsidered, it appears to be widely used and needed

After reading the comment of @alan-agius4 again. He said following.

the deployUrl, is used not just to set the publicPath, using deployUrl will cause additional steps including processing all CSS templates and files to append the deployUrl to the assets urls.

How many people here that need --deployUrl to make angular application functional on CDN care about assets? Personally I don't.
To be clear, I host all the assets directly on CDN, not within the repository to be deployed through assets. So, for my scenario, --deployUrl only means for CSS, JS bundles. Not for image, fonts, SVG or any other assets.

CSS bundle produced by Angular builds (I do care)
JS bundle produced by Angular builds to allow lazy load (I do care)
Fonts (don't care): For most of people that uses either Rails, ASP.NET or other to power the index.html, we normally have link directly to the fonts we need.
Images in CSS or Images in HTML template (don't care): If host in CDN instead of from assets folder, we can include full link in CSS, or create Angular directive to use relative URL to translate to CDN link. Not an problem.
SVG (don't care): Same as image, or we could use approach similar to Font Awesome, save definition in TS and load it through component.

So, alternative approach is to introduce another parameter to allow deploy URL only for JS, CSS and templates, ignore assets. That way, Angular CLI does not have to process anything related to assets, nor it will have much burden of package size.

@th0r expanded what @alan-agius4 have suggest to use base-url to get around. Which is great, but it also reveal many hacks that need to be done. Base URL will cause router to broke, cause XHR/fetch to broke on relative URL. Agree with @th0r, I wouldn't count that as solution either.
I would try to provide few solution as well, some of them require angular team's implementation, which I will list here as potential get around.

Introduce another feature that's similar to --deploy-url. It only care about lazy load. It will resolve any template, CSS,  JS that's related to lazy loading and ignore all assets, such as font, image, SVG etc. (Depending on Angular team)

Assets such as image, font and SVG always have alternative way to achieve. Those items are under our reach.
Lazy loading module does not under our control. Which should be something for angular team to cover.
Down side is people who rely on --deploy-url for assets will suffer.

Introduce an angular config that can setup at run time. Similar to APP_BASE_HREF. Where we can define an CDN root path for lazy loading module to use. (Depending on Angular team)

Similar pro and con to first approach.
Best build time, same without --deploy-url and less bundle size.

Server side, Rails or ASP.NET, when we define angular application route, we use route definition to allow all child route to hit. Such as Route("app/v2/{*appCacheAll}"). What we can do is to detect income request, if it ends with .js or .css. We can respond with redirect to CDN response rather than content of index.html.

Problem 1 with such approach. If deploy location is based on version, then we need a way to understand which version the app is asking. Often happen during upgrade. Solution can be use cookie to give latest version number, then each JS and CSS query will contain version info.
Problem 2. Retrieve performance. Since it is redirect, it means browser will first contact with server, then redirect to actual assets.
Benefit is it can also apply to assets without client side hack.

Similar as solution 3, when detect .js or .css request, instead of relocated response, server act as proxy to assets.

Problem with such approach is defeat purpose of CDN. Also require better code to handle proxy correctly, to make server side memory efficient also utilize cache header.
Benefit of such approach is that, all JS and CSS files will be treated as if they are under that path. It is not redirect.

That's all the solutions I can think of. First two solution depends on Angular team, where last 2 require backend skill. Which is what I am familiar with. Add @th0r's solution on top of it. Which is five different ways. So, if Angular team removed without introduce alternative way such as 1st and 2nd solution, we have at least one front end solution and two back-end solution.

This will cause us a lot of discomfort as we rely on deployUrl heavily while building our production bundle.
We set the value as deployUrl: https://some-cdn.com/ where are JS and CSS artifacts are stored. Our baseHref is completely different from the deployUrl value.
Coming up with alternatives to this will be complex and will involve some tradeoffs (be it writing a script for the postbuild option or using fileReplacements to replace the .html to name a few).

As a work around for the WebPack publicPath value you can set the global __webpack_public_path__ variable in your angular entry point. I have the following in my main.ts file.
declare var  __webpack_public_path__: string;
__webpack_public_path__ = 'valueFormerlyAssignedUsing_deployUrl';

If you have different build configurations you can store the appropriate value in the './environments/environment file and have those be replaced according to the angular.json configuration.
I do want to upvote this question though because it is a breaking change without any angular specific work around. We also use asp.net mvc to host the root file (instead of the angular index.html file) so the angular distribution folder is no the same as the load point url that asp.net uses. This means that anything dynamically loaded with import will fail because it can't be resolved.

@IgorWolbers didn't work for me though.
// main.ts
declare var  __webpack_public_path__: string;

if (environment.production) {
  __webpack_public_path__ = 'https://some-cdn.com/';
  enableProdMode();
}

platformBrowserDynamic().bootstrapModule(AppModule)
  .catch(err => console.log(err));

after running ng build, we get:
<script src="runtime.71b88e53f069c658.js" instead of <script src="https://some-cdn.com/runtime.71b88e53f069c658.js"

I suggest angular official dev team to keep deployUrl option, becasue baseHref and deployUrl are not same usage to work, there's no reason to suggest one to become the replacement of another.

I really don't see why this was forced on the build. Listen guys, not everyone hosts the Angular way. There's nothing wrong with keeping the deployUrl option for those of us who need it. It doesn't play well with ng serve but that's fine, I just don't use ng serve. Don't make me hardcode the deployUrl all over the place to get this thing functional again.

I'll add to the list of replies, please don't deprecate/remove this option. Our application run from a .Net MVC razr view with assets hosted elsewhere, so the baseHref for routing is separate from what deployUrl does. You should assume having the base html page / routing / api calls independent from the assets loading calls is a pretty common use case, and module federation might become a pretty common one too.

It seems that so many use cases are in favor of keeping the deployUrl option. I don't know if it would be possible for the Angular team ,  to enable/disable to use of deployUrl in configuration so that developpers who want it can opt-in for build performance gains and developpers who need the current behavior can keep using it ?

I also need deploy URL, otherwise the chunks are not loaded correctly.

This causes problems with our setup too. We use Spring Boot to serve the Angular app. The app is being built under resources/static/dist. Spring by default serves content from the static folder, we use a subfolder so that we can restrict access to resources but whitelist the Angular app. The index.html is served as a Thymeleaf template with the base href set to the context path of the server, we do not use the index.html generated during build. We set the deployUrl to dist/ to make this setup work.
E.g. suppose the server runs on http://my-domain.com/foo then we set the base href to /foo/, the app is available at http://my-domain.com/foo/dist.
With the deprecation of deployUrl we need to set the base href to /foo/dist/ for the assets to be loaded but this results in API requests going to /foo/dist/api whereas we need them to go to /foo/api.
Obviously there are ways around it (the best one currently being using deployUrl while we still can), but I would like to know what an elegant solution to this problem could be.

We have also problems with the deprecation of deployUrl.
Our server serves two Angular applications from the same path depending on whether the user is authenticated or not, with the help of deployUrl, we could set each application's assets paths to separate them on the server and still use the same URL. In this case if user load http://example.foo/ and they are not authenticated, the server can serve lets say LoginApplication which has deployUrl set to assets/login/, once they are authenticated the server serves lets say DashboardApplication which has deployUrl set to assets/dashboard/.
APP_BASE_HREF does not help us because it changes the browser URL to assets/login/ or assets/dashboard/.
Any idea how this can be handled without deployUrl?

How to use deployUrl correctly and what problems it is good / not good for has been a difficult area for the community. We've done our best to assist folks where possible, but this is a big enough issue that our attempts to do so haven't really scaled effectively. After some discussion, we think the best path forward here is to update some of our docs to be more clear about various aspects and also write a blog post which discusses some common use cases where devs typically reach for deployUrl and how our official recommendation for how to handle those requirements. That seems like the most scalable approach addressing the confusion around deployUrl.
I'm closing this issue for now as we don't see anything directly actionable here, but hopefully better documentation and a future blog post will help clarify how best to meet your requirements.

@dgp1130 Could you clearly describe what will happen to deployUrl? Will that property still pending on removal or Angular will keep that functionality.
People who posted here, or at least for me need an clear path of whether deployUrl will be removed or not. Documentation and recommendation is good, but if the functionality will be removed, we need to plan ahead.

We are still planning to remove deployUrl eventually largely because of all the confusion it causes. The exact version it gets dropped is still TBH, but I can confidently say it will not be removed in v14, so this shouldn't be an immediate problem for anyone. The blog post in particular should hopefully help address common use cases which have used deployUrl in the past and how we recommend moving forward for each of them. We're not expecting any existing use cases to suddenly become unsupported, just that the right approach for you will probably vary by your particular requirements.

Had this same issue but found a solution that worked for me - https://stackoverflow.com/questions/71695674/what-is-best-way-to-go-about-replacing-deployurl-in-angular-json-for-v13/71913980#71913980

I also need deploy URL, otherwise the chunks are not loaded correctly. APP_BASE_HREF is not the solution.

did you ever managed to work things out with omit deployUrl and using APP_BASE_HREF?

@benjaminadrom tey a solution posted by @ThomasDevens above. It worked for me.

@benjaminadrom tey a solution posted by @ThomasDevens above. It worked for me.
thanks, but
APP_BASE_HREF' useValue did not change the base href inside the generated index, so his solution as I understood was to replace those links that manually, which feels like an unnecessary hack somehow


Support and testing for all types from postgres

For reference: https://github.com/brianc/node-pg-types
Complete a full review of types from postgres and conversion into JS objects. Build function to manage types coming in as a result from the pg package.

Closed by #176


Update ubuntu version and common driver on storagedriver docs

Proposed changes
Update storagedriver docs:

Updates and unifies all ubuntu versions to the latest LTS one
Uses commoner storage driver as example

Unreleased project version (optional)
n/a
Related issues (optional)
n/a
Signed-off-by: Takuya Noguchi<EMAIL_ADDRESS>

Deploy preview for docsdocker ready!
Built with commit 0f1feed9e58aae00e5ccbc8cbb5ca226f33b611e
https://deploy-preview-8746--docsdocker.netlify.com

The changes can be confirmed at: https://deploy-preview-8746--docsdocker.netlify.com/storage/storagedriver/

@bermudezmt Could you have a look at this?

Hi @tnir - have not forgotten about this. I'm adding to the backlog so we can do a tech review and have this merged.


fix docker dir permissions

This PR supercedes #384, and fixes #362.
This change also removes python install from docker container.

Current dependencies on/for this PR:

main-enterprise

PR #453   👈

This comment was auto-generated by Graphite.


Update ogr2ogr2.1 references in docs and sample app_config

Related: https://github.com/CartoDB/cartodb/pull/6975
cc @rafatower

:+1:

retest this please

retest this please


Progress is not visible on the site

The progress of my lesson is not updated on the website. You can see it below:

Hi there,
Check out this article about lights not turning green in the Learn Help Center.
Thanks! 💙


Introduce a sanity github action check

Introduce the .github/workflows directory and add a action that ensures
that the codegen (manifests/APIs) are up-to-date and the package
formatting (go fmt/goimports) don't produce a diff.
Update the Makefile's format target and also run the goimports command
against the set of Go packages

/lgtm

/approve


style: change MathUtils imports from tree

Refs: #368
Description
Some imports of MathUtils was related to source code instead of library.

What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[ ] Documentation update
[x] Other

Before submitting the PR, please make sure you do the following:

[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Follow the Conventional Commits v1.0.0 standard for PR naming (e.g. feat(examples): add hello-world example).
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[x] Ideally, include relevant tests that fail without this PR but pass with it.

Thanks for this! In the last big refactor we already took this feedback into account and implemented it using the code of this PR as a reference. Let us know if we missed anything! Cheers


[Windows] Build only supports one GPU arch

I recently built a flash-attention wheel for windows here. However, it appears that this wheel only works on ampere GPUs and not on ada versions.
Tested this with @Panchovix who uses a dual 4090 setup and he couldn't install my wheel, but installing on a 3090 system works. Consequently, trying to install his wheel that was built on his 4090 system failed on my 3090 system. I can only test this on windows, but I'm not sure if this issue occurs with linux builds as well?
The main error is that flash_attention_cuda isn't found when trying to load a model, but the windows wheel is installed. I was under the impression that building from source built for all relevant GPU arches (ampere and ada)
OS: Windows
CUDA: 12.1
GPU: Nvidia RTX 3090ti
Commands run:
git clone https://github.com/Dao-AILab/flash-attention
pip install packaging ninja
python setup.py install
python setup.py bdist_wheel

Ampere and Ada here use the same code, so the same wheel should work for both. Could it be just different environments (python/pytorch version etc)?

To add, this is what I did.
Until yesterday, on my system I had 2x4090. I built the wheel as always and it worked. (wheel in reference here https://huggingface.co/Panchovix/flash-attn-2-windows-test-wheel)
Yesterday, I added a 3090 into my PC, and then, the moment it tried to use the RTX 3090, it failed.
Then, I had to re-build with the 3 GPUs on the system and then it worked.
@bdashore3 tested my previous wheel built with 4090s and it didn't work for him on his system with an Ampere GPU.
To add, this seems to be a general? issue, since I had to rebuild xformers, exllama/v2, etc. Else the 3090 wouldn't work with code that used those manually built libraries.

That's strange. We build with sm_80 and the same code should run on A100, 3090, 4090, etc. Only H100 would need sm_90.
At least on Linux, I can download the same wheel on 2 different machines with A100 and 3090, and it would work. I'm not sure if things are different on Windows.

Maybe it's a difference in command-line arg parsing?
Try changing this:
https://github.com/Dao-AILab/flash-attention/blob/02ac572f3ffc4f402e4183aaa6824b45859d3ed3/setup.py#L121-L128C57
To this:
    # cc_flag.append("-gencode=arch=compute_75,code=sm_75")
    cc_flag.append("-gencode=arch=compute_80,code=sm_80")
    if CUDA_HOME is not None:
        if bare_metal_version >= Version("11.8"):
           cc_flag.append("-gencode=arch=compute_90,code=sm_90")

Or replacing it with something like this:
    nvcc_arch = ""
    # nvcc_arch = nvcc_arch + " 7.5+PTX"
    nvcc_arch = nvcc_arch + " 8.0+PTX"
    if CUDA_HOME is not None:
        if bare_metal_version >= Version("11.8"):
           nvcc_arch = nvcc_arch + " 9.0+PTX"

    os.environ['TORCH_CUDA_ARCH_LIST'] = os.environ.get('TORCH_CUDA_ARCH_LIST', nvcc_arch.strip())

That last one will produce the same args as the first, just lets Pytorch figure it out on it's own using cpp_extension._get_cuda_arch_flags().

I was able to build a wheel that works on both 3090 and 4090 systems via adding compute capability statements as shown above. The great news is that cuda 12.2 wheels are backwards compatible with cuda 12.1, so we only need to build one wheel for Windows.
cc_flag.append("-gencode")
cc_flag.append("arch=compute_86,code=sm_86")
cc_flag.append("-gencode")
cc_flag.append("arch=compute_89,code=sm_89")

Commands run (post-requirements install and patch):
python setup.py bdist_wheel

Tests:

Works on a sole 3090(ti) system
Works on a sole 4090 system
Works on a mixed 3060 + 4070 system
Works on a dual 4090 + single 3090 system

I can probably say this new method allows for interop between ampere and ada.


Request is not authorized to perform blob overwrite - Error 403

Im trying to deploy files in destination storage account via CI/CD and using azcopy task for the same. Im trying to copy from my repo to a folder in my storage account container (StorageAccount/Container/Folder/* )
I have storage Contributor access to my devops service connection and also assigned Read,Write , Execute permission for the Folder to which Im trying to copy.
I was able to copy to my folder but I couldn't do overwrite
Tried with --Overwrite-true --check-length false too
AzCopy task ver. 4 in Release
Can someone please help me with this?
Thanks,
Chandra

Hey @chandra9787
Thanks for reaching out. !!
Please check read a little more on roles and permission from here.
Contributor vs Storage Data Contributor
Contributor role lets you manage everything except granting access to resources. But what you probably are looking for is a "Storage Data Blob Contributor" , "Storage Data Queue Contributor" and "FHIR Data Contributor" roles. Please read up on them and if your query still persists, please reach out to me for more clarification.


Error creating new Craft CMS project - tmp file creation

Preliminary checklist

[X] I am using the latest stable version of DDEV (see upgrade guide)
[X] I have searched existing issues
[X] I have checked the troubleshooting guide
[X] I have run ddev debug test to include output below

Output of ddev debug test
Expand ddev debug test diagnostic information
Running bash [-c /var/folders/s8/nr0t3q7954j64nq3by9804xw0000gn/T/test_ddev.sh]
======= Existing project config =========
These config files were loaded for project project-a: [/r/e/d/a/c/t/e/d/project-a/cms/.ddev/config.yaml]
name: project-a
type: craftcms
docroot: web
php_version: 8.1
webserver_type: nginx-fpm
webimage: ddev/ddev-webserver:v1.22.7
additional_hostnames: []
additional_fqdns: []
database: {mysql 8.0}
project_tld: ddev.site
use_dns_when_possible: true
composer_version: 2
nodejs_version: 18
default_container_timeout: 120
disable_upload_dirs_warning: true
======= Creating dummy project named  tryddevproject-19779 in ../tryddevproject-19779 =========
OS Information: Darwin redacted.lan 23.5.0 Darwin Kernel Version 23.5.0: Wed May  1 20:16:51 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T8103 arm64
ProductName:		macOS
ProductVersion:		14.5
BuildVersion:		23F79
User information: uid=501(home) gid=20(staff) groups=20(staff),12(everyone),61(localaccounts),79(_appserverusr),80(admin),81(_appserveradm),98(_lpadmin),701(com.apple.sharepoint.group.1),33(_appstore),100(_lpoperator),204(_developer),250(_analyticsusers),395(com.apple.access_ftp),398(com.apple.access_screensharing),399(com.apple.access_ssh),400(com.apple.access_remote_ae)
DDEV version:  ITEM             VALUE
 DDEV version     v1.22.7
 architecture     arm64
 db               ddev/ddev-dbserver-mariadb-10.4:v1.22.7
 ddev-ssh-agent   ddev/ddev-ssh-agent:v1.22.7
 docker           20.10.24
 docker-compose   v2.24.5
 docker-platform  docker-desktop
 mutagen          0.17.2
 os               darwin
 router           ddev/ddev-traefik-router:v1.22.7
 web              ddev/ddev-webserver:v1.22.7
PROXY settings: HTTP_PROXY='' HTTPS_PROXY='' http_proxy='' NO_PROXY=''
======= DDEV global info =========
Global configuration:
instrumentation-opt-in=true
omit-containers=[]
performance-mode=mutagen
router-bind-all-interfaces=false
internet-detection-timeout-ms=3000
disable-http2=false
use-letsencrypt=false
letsencrypt-email=
table-style=default
simple-formatting=false
use-hardened-images=false
fail-on-hook-fail=false
required-docker-compose-version=v2.24.5
use-docker-compose-from-path=false
project-tld=ddev.site
xdebug-ide-location=
no-bind-mounts=false
router=traefik
wsl2-no-windows-hosts-mgt=false
router-http-port=80
router-https-port=443
mailpit-http-port=8025
mailpit-https-port=8026
traefik-monitor-port=10999

======= DOCKER info =========
docker location: lrwxr-xr-x  1 root  wheel  54 Oct 19  2021 /usr/local/bin/docker -> /Applications/Docker.app/Contents/Resources/bin/docker
Docker Desktop Version: Docker Desktop for Mac 4.18.0 build 104112
docker version:
Client:
 Cloud integration: v1.0.31
 Version:           20.10.24
 API version:       1.41
 Go version:        go1.19.7
 Git commit:        297e128
 Built:             Tue Apr  4 18:21:21 2023
 OS/Arch:           darwin/arm64
 Context:           default
 Experimental:      true

Server: Docker Desktop 4.18.0 (104112)
 Engine:
  Version:          20.10.24
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.19.7
  Git commit:       5d6db84
  Built:            Tue Apr  4 18:17:07 2023
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          1.6.18
  GitCommit:        2456e983eb9e37e47538f59ea18f2043c9a73640
 runc:
  Version:          1.1.4
  GitCommit:        v1.1.4-0-g5fd4c4d
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0
DOCKER_DEFAULT_PLATFORM=notset
======= Mutagen Info =========
Mutagen is installed in ddev, version=0.17.2
--------------------------------------------------------------------------------
Name: project-b
Identifier: sync_4FCqPr8RN1x8J90zrgEp7TE5t1TaJLpYnsmKThqb7sZ
Labels:
	com.ddev.config-hash: 0311359b0f6eedb428c2679de60b5d021c2d717b
	com.ddev.volume-signature: var-run-1717706245
Configuration:
	Synchronization mode: Two Way Resolved
	Hashing algorithm: Default (SHA-1)
	Maximum allowed entry count: Default (2⁶⁴−1)
	Maximum staging file size: Default (18 EB)
	Symbolic link mode: POSIX Raw
	Ignore VCS mode: Default (Propagate)
	Ignores:
		/.git
		/.tarballs
		/.ddev/db_snapshots
		/.ddev/.importdb*
		.DS_Store
		.idea
	Permissions mode: Default (Portable)
Alpha:
	URL: /r/e/d/a/c/t/e/d/project-b
	Configuration:
		Watch mode: Default (Portable)
		Watch polling interval: Default (10 seconds)
		Probe mode: Default (Probe)
		Scan mode: Default (Accelerated)
		Stage mode: Neighboring
		File mode: Default (0600)
		Directory mode: Default (0700)
		Default file/directory owner: Default
		Default file/directory group: Default
	Connected: Yes
	Synchronizable contents:
		2967 directories
		18157 files (300 MB)
		0 symbolic links
	Transition problems:
		cms/storage/runtime/cache/2c/CraftCMS--85252d39-89b4-4901-8f3a-8acc1541c6f62cf64d13d158e2e842c02b9b79370bab.bin: unable to create file: unable to set staged file permissions: unable to set permission bits: chmod /r/e/d/a/c/t/e/d/.mutagen-temporary-staging-sync_4FCqPr8RN1x8J90zrgEp7TE5t1TaJLpYnsmKThqb7sZ-alpha/fa/fab171cdd96278dec314bb3f3c4ef2c1c508e76c915722bdcf8fa4876acffc2c878e1249: no such file or directory
Beta:
	URL: docker://ddev-project-b-web/var/www/html
		DOCKER_HOST=unix:///var/run/docker.sock
	Configuration:
		Watch mode: Default (Portable)
		Watch polling interval: Default (10 seconds)
		Probe mode: Default (Probe)
		Scan mode: Default (Accelerated)
		Stage mode: Neighboring
		File mode: Default (0600)
		Directory mode: Default (0700)
		Default file/directory owner: Default
		Default file/directory group: Default
		Compression: Default (DEFLATE)
	Connected: Yes
	Synchronizable contents:
		2967 directories
		18158 files (300 MB)
		0 symbolic links
Status: Watching for changes
--------------------------------------------------------------------------------
Name: project-a
Identifier: sync_vBWD1WAHL4BVVTdPtLovLJMEyMtLwhsj9AhPATZOKPC
Labels:
	com.ddev.config-hash: 0311359b0f6eedb428c2679de60b5d021c2d717b
	com.ddev.volume-signature: var-run-1718174810
Configuration:
	Synchronization mode: Two Way Resolved
	Hashing algorithm: Default (SHA-1)
	Maximum allowed entry count: Default (2⁶⁴−1)
	Maximum staging file size: Default (18 EB)
	Symbolic link mode: POSIX Raw
	Ignore VCS mode: Default (Propagate)
	Ignores:
		/.git
		/.tarballs
		/.ddev/db_snapshots
		/.ddev/.importdb*
		.DS_Store
		.idea
	Permissions mode: Default (Portable)
Alpha:
	URL: /r/e/d/a/c/t/e/d/project-a/cms
	Configuration:
		Watch mode: Default (Portable)
		Watch polling interval: Default (10 seconds)
		Probe mode: Default (Probe)
		Scan mode: Default (Accelerated)
		Stage mode: Neighboring
		File mode: Default (0600)
		Directory mode: Default (0700)
		Default file/directory owner: Default
		Default file/directory group: Default
	Connected: Yes
	Synchronizable contents:
		28 directories
		79 files (112 kB)
		0 symbolic links
Beta:
	URL: docker://ddev-project-a-web/var/www/html
		DOCKER_HOST=unix:///var/run/docker.sock
	Configuration:
		Watch mode: Default (Portable)
		Watch polling interval: Default (10 seconds)
		Probe mode: Default (Probe)
		Scan mode: Default (Accelerated)
		Stage mode: Neighboring
		File mode: Default (0600)
		Directory mode: Default (0700)
		Default file/directory owner: Default
		Default file/directory group: Default
		Compression: Default (DEFLATE)
	Connected: Yes
	Synchronizable contents:
		28 directories
		79 files (112 kB)
		0 symbolic links
Status: Watching for changes
--------------------------------------------------------------------------------
======= Docker Info =========
Docker platform: docker-desktop
Using Docker context: default (unix:///var/run/docker.sock)
docker-compose: v2.24.5
Using DOCKER_HOST=unix:///var/run/docker.sock
Docker version: 20.10.24
Able to run simple container that mounts a volume.
Able to use internet inside container.
Docker disk space:
Filesystem                Size      Used Available Use% Mounted on
overlay                 117.0G     65.2G     45.8G  59% /

 Container ddev-project-b-db  Stopped
 Container ddev-project-b-web  Stopped
 Container ddev-project-b-web  Stopped
 Container ddev-project-b-db  Stopped
 Container ddev-project-b-db  Removed
 Container ddev-project-b-web  Removed
 Network ddev-project-b_default  Removed
Project project-b has been stopped.
 Container ddev-project-a-db  Stopped
 Container ddev-project-a-web  Stopped
 Container ddev-project-a-web  Stopped
 Container ddev-project-a-db  Stopped
 Container ddev-project-a-db  Removed
 Container ddev-project-a-web  Removed
 Network ddev-project-a_default  Removed
Project project-a has been stopped.
Stopped Mutagen daemon
The ddev-ssh-agent container has been removed. When you start it again you will have to use 'ddev auth ssh' to provide key authentication again.
Network ddev_default removed
Existing docker containers:
CONTAINER ID IMAGE      COMMAND      CREATED         STATUS                       PORTS           NAMES
a739c9…      redacted   "redacted"   5 weeks ago     Exited (2) 5 weeks ago                       redacted
84a808…      redacted   "redacted"   5 weeks ago     Exited (255) 3 weeks ago     2375-2376/tcp   redacted
a4481e…      redacted   "redacted"   5 weeks ago     Exited (0) 5 weeks ago                       redacted
283196…      redacted   "redacted"   5 weeks ago     Exited (0) 5 weeks ago                       redacted
bf87e6…      redacted   "redacted"   5 weeks ago     Exited (0) 5 weeks ago                       redacted
317bdf…      redacted   "redacted"   5 weeks ago     Exited (0) 5 weeks ago                       redacted
dfd111…      redacted   "redacted"   5 weeks ago     Exited (0) 5 weeks ago                       redacted
e8d669…      redacted   "redacted"   7 weeks ago     Exited (255) 5 weeks ago                     redacted
8d7c69…      redacted   "redacted"   7 weeks ago     Exited (255) 5 weeks ago     2375-2376/tcp   redacted
1c285c…      redacted   "redacted"   2 months ago    Exited (0) 2 months ago                      redacted
0b32c5…      redacted   "redacted"   2 months ago    Exited (0) 2 months ago                      redacted
82f7d1…      redacted   "redacted"   3 months ago    Exited (0) 3 months ago                      redacted
38b3d5…      redacted   "redacted"   4 months ago    Exited (0) 4 months ago                      redacted
d17e00…      redacted   "redacted"   4 months ago    Exited (0) 4 months ago                      redacted
564aa8…      redacted   "redacted"   6 months ago    Exited (0) 6 months ago                      redacted
5ac04d…      redacted   "redacted"   6 months ago    Exited (0) 6 months ago                      redacted
b15578…      redacted   "redacted"   6 months ago    Exited (0) 6 months ago                      redacted
56a571…      redacted   "redacted"   6 months ago    Exited (0) 6 months ago                      redacted
d53beb…      redacted   "redacted"   6 months ago    Exited (0) 6 months ago                      redacted
492c1d…      redacted   "redacted"   6 months ago    Exited (0) 6 months ago                      redacted
43baaa…      redacted   "redacted"   6 months ago    Exited (0) 6 months ago                      redacted
32e234…      redacted   "redacted"   6 months ago    Exited (0) 6 months ago                      redacted
d8017c…      redacted   "redacted"   6 months ago    Exited (3) 6 months ago                      redacted
ac43c9…      redacted   "redacted"   6 months ago    Exited (0) 6 months ago                      redacted
faa9f5…      redacted   "redacted"   6 months ago    Exited (0) 6 months ago                      redacted
ee7f09…      redacted   "redacted"   6 months ago    Exited (3) 6 months ago                      redacted
1069e0…      redacted   "redacted"   7 months ago    Exited (0) 7 months ago                      redacted
88e105…      redacted   "redacted"   9 months ago    Exited (0) 9 months ago                      redacted
e9cf9e…      redacted   "redacted"   9 months ago    Exited (0) 9 months ago                      redacted
a7e973…      redacted   "redacted"   9 months ago    Exited (0) 9 months ago                      redacted
8286c7…      redacted   "redacted"   9 months ago    Exited (0) 9 months ago                      redacted
e82aa0…      redacted   "redacted"   9 months ago    Exited (0) 9 months ago                      redacted
4f08b3…      redacted   "redacted"   9 months ago    Exited (3) 9 months ago                      redacted
45fcec…      redacted   "redacted"   9 months ago    Exited (1) 9 months ago                      redacted
Network ddev_default created
Starting tryddevproject-19779...

Project images built in 3s.
 Container ddev-tryddevproject-19779-web  Created
 Container ddev-tryddevproject-19779-db  Created
 Container ddev-tryddevproject-19779-db  Started
 Container ddev-tryddevproject-19779-web  Started
You have Mutagen enabled and your 'php' project type doesn't have `upload_dirs` set.
For faster startup and less disk usage, set upload_dirs to where your user-generated files are stored.
If this is intended you can disable this warning with `ddev config --disable-upload-dirs-warning`.
Starting Mutagen sync process...
Mutagen sync flush completed in 5s.
For details on sync status 'ddev mutagen st tryddevproject-19779 -l'
Waiting for web/db containers to become ready: [web db]
Starting ddev-router if necessary...
 Container ddev-router  Created
 Container ddev-router  Started
Waiting for additional project containers to become ready...
All project containers are now ready.
Successfully started tryddevproject-19779
Project can be reached at https://tryddevproject-19779.ddev.site https://<IP_ADDRESS>:52499
======== Curl of site from inside container:
HTTP/1.1 200 OK
Server: nginx
Date: Wed, 12 Jun 2024 06:54:54 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding

======== curl -I of http://tryddevproject-19779.ddev.site from outside:
HTTP/1.1 200 OK
Content-Type: text/html; charset=UTF-8
Date: Wed, 12 Jun 2024 06:54:55 GMT
Server: nginx
Vary: Accept-Encoding

======== full curl of http://tryddevproject-19779.ddev.site from outside:
Success accessing database... db via TCP/IP
ddev is working. You will want to delete this project with 'ddev delete -Oy tryddevproject-19779'
======== Project ownership on host:
drwxr-xr-x  4 home  staff  128 Jun 11 20:52 ../tryddevproject-19779
======== Project ownership in container:
drwxr-xr-x 4 home dialout 4096 Jun 12 06:54 /var/www/html
======== In-container filesystem:
Filesystem     Type 1K-blocks     Used Available Use% Mounted on
/dev/vda1      ext4 122713108 69079692  47367104  60% /var/www
======== curl again of tryddevproject-19779 from host:
Success accessing database... db via TCP/IP
ddev is working. You will want to delete this project with 'ddev delete -Oy tryddevproject-19779'
Thanks for running the diagnostic. It was successful.
Please provide the output of this script in a new gist at gist.github.com
Running ddev launch in 5 seconds

Please run cleanup after debugging with 'ddev debug testcleanup'

Note the
	Transition problems:
		cms/storage/runtime/cache/2c/CraftCMS--85252d39-89b4-4901-8f3a-8acc1541c6f62cf64d13d158e2e842c02b9b79370bab.bin: unable to create file: unable to set staged file permissions: unable to set permission bits: chmod /r/e/d/a/c/t/e/d/.mutagen-temporary-staging-sync_4FCqPr8RN1x8J90zrgEp7TE5t1TaJLpYnsmKThqb7sZ-alpha/fa/fab171cdd96278dec314bb3f3c4ef2c1c508e76c915722bdcf8fa4876acffc2c878e1249: no such file or directory

Expected Behavior
When I follow the Craft CMS quickstart, a Craft CMS project is created.
Actual Behavior
When I follow the Craft CMS quickstart, I get an error before setup finishes.
Steps To Reproduce
% mkdir my-craft-site && cd my-craft-site
% ddev config --project-type=craftcms --docroot=web
% ddev start
% ddev composer create craftcms/craft
Executing Composer command: [composer create-project craftcms/craft --no-install /tmp/BkRPFp]

Creating a "craftcms/craft" project at "/tmp/BkRPFp"
Installing craftcms/craft (5.0.1)
  - Downloading craftcms/craft (5.0.1)
  - Installing craftcms/craft (5.0.1): Extracting archive
Created project in /tmp/BkRPFp
> @php -r "file_exists('.env') || copy('.env.example.dev', '.env');"
> @php -r "unlink('composer.json');"
> @php -r "rename('composer.json.default', 'composer.json');"
Generating optimized autoload files
Generated optimized autoload files containing 1 classes
> @php craft setup/welcome
PHP Warning:  require(/tmp/BkRPFp/vendor/craftcms/cms/bootstrap/console.php): Failed to open stream: No such file or directory in /tmp/BkRPFp/craft on line 12

Warning: require(/tmp/BkRPFp/vendor/craftcms/cms/bootstrap/console.php): Failed to open stream: No such file or directory in /tmp/BkRPFp/craft on line 12
PHP Fatal error:  Uncaught Error: Failed opening required '/tmp/BkRPFp/vendor/craftcms/cms/bootstrap/console.php' (include_path='.:/usr/share/php') in /tmp/BkRPFp/craft:12
Stack trace:
#0 {main}
  thrown in /tmp/BkRPFp/craft on line 12

Fatal error: Uncaught Error: Failed opening required '/tmp/BkRPFp/vendor/craftcms/cms/bootstrap/console.php' (include_path='.:/usr/share/php') in /tmp/BkRPFp/craft:12
Stack trace:
#0 {main}
  thrown in /tmp/BkRPFp/craft on line 12
Script @php craft setup/welcome handling the post-create-project-cmd event returned with error code 255

Anything else?
No response

Hi @olets -
Unfortunately, you're not using the current stable DDEV version, and your ddev debug test is not giving me the information I'm looking for. We do ask that when people ask for support they use the current stable version (now v1.23.1).
Could you please say what directory you're working in for your project? Is it in your home directory?
Please upgrade, reproduce the problem, and provide ddev debug test, and make sure you're working in your home directory.

So sorry. I had run brew upgrade ddev… but it errored, and I didn't notice 🤦. Tried again with success, and now project setup works fine.
(Fwiw the directory was /Users/<user>/Sites/<dir>/<monorepo root>/cms)


Windows XP bootmgr

Hello,
I'm trying to install a WinXP x86 using netboot.xyz.
I've dearchivated the ISO and there are no files named bootmgr, boot/bcd, boot/sdi, sources/boot.wim
How can I do it ?

XP used another installer method so those files would not be included on the XP media.  This currently supports the method used in Vista and on.


block.list_children_by_class empty array_annotations

In https://github.com/INM-6/elephant/blob/neo-v0.8.0/elephant/test/test_neo_tools.py#L621
obj = self.block.list_children_by_class('Event')[0]
targ = get_fake_values('Event', seed=obj.annotations['seed'])

obj.array_annotations is an empty ArrayDict of size 13, but it should return the same dict as in targ['array_annotations'].
The other thing is that their lengths mismatch. To fix both issues, we make
        num_times = len(targ['times'])
        obj = obj[:num_times]
        del targ['array_annotations']

Please confirm that this is an issue and not incorrect usage of neo in Elephant.
Update.
This might relate to https://github.com/NeuralEnsemble/python-neo/pull/656

I think this is an issue with the Neo tests, and the way get_fake_values() works, rather than with the list_children_by_class() method.
Example:
import neo
ev = neo.Event([1, 2, 3, 4, 5], units="ms", labels=["a", "b", "c", "d", "e"])
seg = neo.Segment()
seg.events.append(ev)
ev.segment = seg
b = Block()
b = neo.Block()
b.segments.append(seg)
seg.block = b
ev.array_annotate(category=[1, 2, 2, 1, 1])
ev2 = b.list_children_by_class('Event')[0]

ev2.array_annotations --> {'category': array([1, 2, 2, 1, 1])}
I'll leave this open to check when we refactor the Neo testing framework.

get_fake_values was removed.


Add 0.4.11 release notes

Description
This PR add 0.4.11 release notes. I have not written the "highlights" section - maybe @jni can take a pass on that if he is around, and folks like @kevinyamauchi @alisterburt can contribute pieces too.
Also there are lots of PRs here that I tried to catagorize best I can, any rearrangements are welcome. We probably need to get better at autogenerating them.
Depending on when people can review - as I'm unable to make an rc until release notes are merged - maybe @tlambert03 can give this a quick sanity check now, then we can merge WITHOUT a highlights section - then i can make the rc and folks can be testing in parallel to adding the highlights/ any deprecations/ API changes. I think this will let us move most efficiently through this process. Thanks!!

added a first draft of the highlights section, commited directly so that others can add/remove things at will! Thanks for putting this together @sofroniewn

Thanks so much @alisterburt for writing the highlights section and going through the release notes - I really like what you wrote and it's a huge help!!
I've rearranged the remaining items flagged by @tlambert03. I think now looks ready to go and will merge after tests pass. I will then make the first rc. We can update release notes during the release process to add things we're missing - @jni