Unable to " spicetify backup apply"

[IMPORTANT: Please remove or replace everything between two square brackets ( [ ] ) before posting your issue.]
Description
[When I try to enter " spicetify backup apply ", I always get this error  C:\Program Files\WindowsApps\SpotifyAB.SpotifyMusic_1.143.700.0_x86__zpdnekdrzrea0 does not exist or is not a valid path. Please manually set "spotify_path" in config.ini to correct directory of Spotify.
When I try to get to Windowsapps folder, I get a message that I do not have the permission to enter. I am the administrator.
I am using Windows 10 Pro, Rainmeter  and Spotify app version  <IP_ADDRESS>8.g8057de92 ].
Is there anyway I can fix it or can I uninstall spicetify.cli and reinstall ?
Thanks in advance
Versions
[IMPORTANT: Please fill out the version numbers so we can properly look for your issue.]
[]

Rainmeter Version: [4.4 Beta Release r3404 ]
OS Version: [Windows 10 Pro 2004 64-bit (build 19041) French (3084)]
Skin Version: [Version=2.1.0]
Spotify Version: [Spotify is not showing in the plugins Tab but I have version <IP_ADDRESS>8 installed]

Additional notes/images
[Windows PowerShell
Copyright (C) Microsoft Corporation. Tous droits réservés.
Testez le nouveau système multiplateforme PowerShell https://aka.ms/pscore6                                                                                PS C:\Users\HP600G2> Invoke-WebRequest "https://raw.githubusercontent.com/khanhas/spicetify-cli/master/install.ps1" | Invoke-Expression                                                                                DOWNLOADING    https://api.github.com/repos/khanhas/spicetify-cli/releases/latest > OK                                  DOWNLOADING    https://github.com/khanhas/spicetify-cli/releases/download/v1.1.0/spicetify-1.1.0-windows-x64.zip > OK
EXTRACTING     C:\Users\HP600G2\spicetify-cli\spicetify-1.1.0-windows-x64.zip into C:\Users\HP600G2\spicetify-cli > OK
REMOVING       C:\Users\HP600G2\spicetify-cli\spicetify-1.1.0-windows-x64.zip > OK

OK
Run spicetify --help to get started.

PS C:\Users\HP600G2> spicetify
info Run "spicetify -h" for commands list.
PS C:\Users\HP600G2> spicetify config extensions webnowplaying.js
warning Config "extensions" unchanged: webnowplaying.js is already in the list.
PS C:\Users\HP600G2> spicetify backup apply
spicetify v1.1.0
error C:\Program Files\WindowsApps\SpotifyAB.SpotifyMusic_1.143.700.0_x86__zpdnekdrzrea0 does not exist or is not a valid path. Please manually set "spotify_path" in config.ini to correct directory of Spotify.
PS C:\Users\HP600G2> config.ini
config.ini : Le terme «config.ini» n'est pas reconnu comme nom d'applet de commande, fonction, fichier de script ou
programme exécutable. Vérifiez l'orthographe du nom, ou si un chemin d'accès existe, vérifiez que le chemin d'accès
est correct et réessayez.
Au caractère Ligne:1 : 1

config.ini

  + CategoryInfo          : ObjectNotFound: (config.ini:String) [], ParentContainsErrorRecordException
  + FullyQualifiedErrorId : CommandNotFoundException

PS C:\Users\HP600G2>]

Closing this issue, please create an issue on the spicetify-cli repo for further help on spicetify.


[ documentation ] Comparision to loco

How does this compare to loco?

I think this may be out of scope for our documentation. Comparing tools to each other is best done by their users, not their authors.

You don't want to sell me on rwf? Why should I bother using this project when loco does such a good job.

Comparing tools to each other is best done by their users, not their authors.

It would definiately be beneficial to users if you know loco too. Many other tools do it right in the README. But that's my personal opinion. Also, Thank you for making and maintanig rwf ⬆❤


Incorrect value "" for int field "max_columns".

Hello,
Trying to import https://github.com/petrushinvs/mongodb-zabbix-templates-4.0/blob/master/zbx_MongoDB_template.xml but get the error:
Details Import failed

    Incorrect value "" for int field "max_columns".

looking at the xml file i see the value is 3
-> grep max_co mongodb-zabbix-templates-4.0/zbx_MongoDB_template.xml
                            <max_columns>3</max_columns>
                            <max_columns>3</max_columns>
                            <max_columns>3</max_columns>
                            <max_columns>3</max_columns>

zabbix_server (Zabbix) 4.4.0rc1

Not sure where to go from here.
Any input is appreciated.
Thanks!
-Dave

Sorry for late answer.
I did this template with zabbix 4.0 and have not tested with zabbix
4.2/4.4. Pls. try it with 4.0 version.
I do not know when I will test it with 4.2/4.4 zabbix...
вт, 26 нояб. 2019 г. в 17:23, Dave<EMAIL_ADDRESS>
Hello,
Trying to import
https://github.com/petrushinvs/mongodb-zabbix-templates-4.0/blob/master/zbx_MongoDB_template.xml
but get the error:
Details Import failed
Incorrect value "" for int field "max_columns".

looking at the xml file i see the value is 3
-> grep max_co mongodb-zabbix-templates-4.0/zbx_MongoDB_template.xml
<max_columns>3</max_columns>
<max_columns>3</max_columns>
<max_columns>3</max_columns>
<max_columns>3</max_columns>
zabbix_server (Zabbix) 4.4.0rc1
Not sure where to go from here.
Any input is appreciated.
Thanks!
-Dave
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/petrushinvs/mongodb-zabbix-templates-4.0/issues/7?email_source=notifications&email_token=AEAXX5Q2LWAX6UC44YBNMW3QVU5QHA5CNFSM4JRZVKIKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H4EZKUQ,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEAXX5S32RIB5SOL6G5LZLDQVU5QHANCNFSM4JRZVKIA
.

--
С уважением,
Василий Петрушин

Is there any way to workaround this?

Sorry, bro
I have changed the job, here is no Zabbix at all, so I do not know when I
will test it. Maybe never.
вт, 3 дек. 2019 г. в 15:41, Chris Levi<EMAIL_ADDRESS>
Is there any way to workaround this?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/petrushinvs/mongodb-zabbix-templates-4.0/issues/7?email_source=notifications&email_token=AEAXX5UMPH6DCO5LA32Y5GTQWZOY5A5CNFSM4JRZVKIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFZNB5Q#issuecomment-561172726,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEAXX5SC2M6CNM3P5TTRQU3QWZOY5ANCNFSM4JRZVKIA
.

--
С уважением,
Василий Петрушин

Solve like this: Remove the screen session that contain max_columns on it. Then import again. Criate your own screen if you need it.

@elianevidal
Thanks for the reply!!
I will test this tomorrow and report back
👍

@elianevidal
That works!!!
Finally got to testing...
So lines that were removed: https://github.com/petrushinvs/mongodb-zabbix-templates-4.0/blob/master/zbx_MongoDB_template.xml#L733-L820
Then just close out the last screen_item since it is empty <screen_items/>

@davama, I just used the fix you gave here.
Now the template works!
Is there a reason why this fix is not put in the repo already?

Try to edit the xml files and set version to 5
see my diff here https://github.com/appsinet/bareos-zabbix/issues/5


don't depend on all of bazel to get the worker API

The worker API uses protobufs that are housed in the bazel repo. As a result, to build that worker process we need to pull all of bazel.
We should either copy the protobufs and build our own client, or copy the generated java code and build that.

Just today I suffered from this on a slow connection after not building
rules_scala for a long time :)
On Mon, 9 Jan 2017 at 19:30 P. Oscar Boykin<EMAIL_ADDRESS>wrote:

The worker API uses protobufs that are housed in the bazel repo. As a
result, to build that worker process we need to pull all of bazel.
We should either copy the protobufs and build our own client, or copy the
generated java code and build that.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/rules_scala/issues/119, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABUIF1LwQ-Off9fI_f3iBfRrNw27H7xdks5rQm7SgaJpZM4LehMJ
.

isn't this duplicate of #116 ?

yes. @ittaiz thanks! Forgot.


UTF8 characters in presets not rendering correctly on M1 macOS, v3.2.x

What is the codepoint of these characters?

⮜ and ⮞
I was working from this list: https://github.com/bitfocus/companion/wiki/Text-input but didn't encode using the number - just copy-pasted the actual character into the code. It worked on Windows so I thought I'd done it correctly.
This can be seen on line 11 of actions.js

Sorry, that got decoded. I'll try again: ⮜ and ⮞

This is not a bug of the zinc-oscpoint module. It should work exactly like you are doing it. I use unicode characters a lot in perests the same way.
The codepoints of your characters are present also in the older versions. Starting with 3.2 we support vector fonts and with that even more (nearly all) unicode characters. I wonder why this is working on windows and intel mac but not on arm mac.
Unfortunaltely I don't have an arm mac, so I'm afraid I can't trace the bug well.
Are unicode characters working when you paste them directly in the button text line on M1 or is this a problem only for presets?


Images can not add on velocity theme

Hi @irisda
It's a broken image issue, please follow this guide https://forums.bagisto.com/topic/188/broken-image-logo-in-bagisto-with-causes-and-solutions

hi @vaishaliwebkul, this is the error I get only when adding single image like categories or velocity images

Try to change your APP_URL in .env file in root directory just like this http://localhost:8000 and then try type this command php artisan storage:link

I checked the APP_URL and it is set to http://localhost:8000. The storage was already linked but I deleted and linked it again. It still shows the same thing.

@kduqi
Could you please tell us about the bagisto version?

Before doing anything, you should do this magic command, just type php artisan config:clear and php artisan cache:clear

I tried php artisan config:clear and php artisan cache:clear but still is the same. I have the latest changes from master branch. This issue started after I got this change:
https://github.com/bagisto/bagisto/pull/3010
It is only for images that are single like category images  or velocity template images. On products it works fine.

@kduqi @irisda
Thanks for notifying the bug.
It's fixed now, please check.

I hope your issue is resolved now. Feel free to reopen the issue.

This issue still persists. Product images are showing but the logo and banner images arent showing. Now I Deleted storage directory in the public folder then ran PHP artisan storage: link and it worked on the localhost. However, when I uploaded the project to the shared hosting, the images are broken again. Kindly help. This is the project URL showing broken banner images and logos: https://sirerics.co.ke/


Function "countWithQuery"

Sometimes is useful to call Count Function with a query associated with - e.g. "SELECT count(*) FROM quiz q LEFT JOIN image i ON i.quiz_id = q.id WHERE i.url IS NOT NULL;"
If some one instruct me a while, I can make it by my self and do a Pull Request. :-)

U can do this using this function
https://github.com/satyan/sugar/blob/master/library/src/main/java/com/orm/SugarRecord.java#L254
lmk if this works or not

@sibelius did you see that my SQL has Join Association?
How can I use count(Class, String, String) for my example?

count method will generate: SELECT count(*) FROM quiz where + whereClause
so I think u should overload count method to use it with a JOIN query


[ISSUE-668] no delete AC before lvg removing

Purpose
Resolves #668
Replace deletion AC with update AC before LVG removing.
Update contains setting size 0 and restore location.
Also add sync AC StorageClass in drive reconcile.
PR checklist

[x] Add link to the issue
[x] Choose Project
[x] Choose PR label
[ ] New unit tests added
[ ] Modified code has meaningful comments
[ ] All TODOs are linked with the issues
[ ] All comments are resolved

Testing

Deploy sts with hddlvg
Remove sts and pvc

/ci

/ci

something something


fix: new event driven implementation for deposit and withdraw

Description of the Changes

Update bridges ABI - now filter fields are indexed and can be used for filtering events.
Simplify implementation in the EventManagerProvider.
Remove listener of LogMessageToL2 event - now after LogDeposit event dispatched we're fetching past LogMessageToL2 events and finding the proper event.

Checklist

[x] Changes have been done against master branch, and PR does not conflict
[ ] New unit / functional tests have been added (whenever applicable)
[ ] Test are passing in local environment
[ ] Docs have been updated
[x] PR title is follow the Conventional Commits convention: <type>[optional scope]: <description>, e.g: fix: prevent racing of requests

This change is

:tada: This PR is included in version 1.1.0-dev.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Removed the ILogger from the constructor

Marked the old ctor as obsolete and updated the tests to use new ctor.

Reference to PR #98
CC @joarb @kennethmyhra

This seems to be just what the doctor ordered. Thumbs up from me. :)

So MessagingClient uses a different approach, it should be aligned to this

Added ILoggerFactory changes to MessagingClinet.


Fix NavigationView Flash in Compact Dark Theme

Description

Color animations animate using RGB channels but not the Alpha channel, causing a flash of white animating between a dark colour and a transparent white colour.
Added SolidBackgroundFillColorTransparent that is a transparent version of the base colour.

/azp run

/azp run


schema versioning

Need to find a better way to handle schema versioning.
We need to retain multiple versions for legacy, and for building the schema endpoint. Note that URL reference is present in every single data object. Hence, incrementing the schema version is tricky.
A Git-challenge is that when a new increment is made, it has to be copied from the previous, hence the entire schema will look like a change - very effectively masking the actual change. Possibly there are some smart workarounds for this.
Possible to build the Radix endpoint directly from pre-defined releases of fmu-dataio?

[ ] Agree on deprecation warnings for outgoing schemas

Closing this particular issue as a duplicate in favor for more recent issues in this repository, in fmu-results workshop.


Mapping of IoT Plug+Play to W3C Web of Things

It would be interesting to attempt defining a mapping of the DTDL to the W3C Web of Things specifications, which are candidate recommendations and are currently in community review:

https://www.w3.org/TR/wot-architecture/
https://www.w3.org/TR/wot-thing-description/

This analysis would help to understand interoperability and could be beneficial for evolution of the DTDL and the Web of Things specifications.

Referencing #10

Referencing https://github.com/Azure/opendigitaltwins-dtdl/issues/43

Referencing https://github.com/Azure/opendigitaltwins-dtdl/issues/43


Conditional Visibility depending on a toggle field

Is your feature request related to a problem? Please describe.
Conditional Visibility depending on a toggle field to avoid checkboxes or select
Describe the solution you'd like
A toogle field for a question like: Do you like music? Could make a text field Which kind of music?visible.
Describe alternatives you've considered
Using checkboxes or select, it works but it will be a nice to have.
Additional context
Thanks for this package! 👍

That sounds like a great option; I will look into it.
Thank you :)


docs: Tweak panic message in Playground to tell how to report the panic

Update the Panic message to say:
A compiler bug was encountered. Please copy/paste the PRQL query into a new report at:
     https://github.com/PRQL/prql/issues/new/choose

Thanks!

At some point it might be interesting to see how to make that URL a clickable link... But it is a little hairy with React, so I figure it's better to give a little guidance sooner than a fancy solution a few weeks in the future...


roundCorners of EKAttributes doesn't work for customView/viewController

As title, the following code shows how i set the roundCorners for a customView display

        let customView = UIView(frame: CGRect(x: 0, y: 0, width: self.view.width, height: self.view.height/2));
        customView.backgroundColor = UIColor.yellow;

        var attributes = EKAttributes.bottomNote;
        attributes.screenBackground = .color(color: EKColor(UIColor(white: 0.25, alpha: 0.85)));
        attributes.positionConstraints.safeArea = .overridden;
        attributes.positionConstraints.size = .init(
            width: .constant(value: 300),
            height: .constant(value: 500)
        )
        attributes.roundCorners = .top(radius: 25) //doesn't work

        SwiftEntryKit.display(entry: customView, using: attributes)

Expected behavior

Probably not the solution you're looking for. But you could just add the code below in your custom view awakeFromNib func
self.layer.cornerRadius = 40
if #available(iOS 11.0, *) {
    self.layer.maskedCorners = [.layerMinXMinYCorner, .layerMaxXMinYCorner]
} else {
}

You should set the entryBackground instead of the customView's backgroundColor


nixos/systemd-boot: init boot counting

Description of changes
This is a spin-off of #84204, that is a PR introducing automatic boot assessment for NixOS, see here. Thanks a lot to @danielfullmer for the initial work on that topic, a lot of this PR has been heavily inspired by #84204.
Most of the design is similar and have been reimplemented to fit with the current state of the systemd-boot backend.
The handling of the default generation is done using the sort-key defined in the boot loader specification. In the first iteration of this change (#84204), it was suggested to use default in the filename of the default generation entry, but since then systemd-boot is using the version field before the filename to sort the entries so this hack is no longer possible.
Todo before merging:

[x] clean the code, especially the regexes
[ ] add documentation
[x] add nixos test showing that we still conform to the default generation

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Thanks a lot for this! I'm very interested in this PR.
How does this work with specializations? My guess is that currently if an entry fail, it will boot to the next specialization by lexicographic order, since it will be between two "main" entries. I don't think this is what we want?

This definitely needs a release notes entry too :D

I'm assuming this PR will also include pulling in the upstream systemd-bless-bootservice & generator and the boot-complete target from systemd?

I'm assuming this PR will also include pulling in the upstream systemd-bless-bootservice & generator and the boot-complete target from systemd?

It's in there already, no ?

Thanks a lot for this! I'm very interested in this PR.
How does this work with specializations? My guess is that currently if an entry fail, it will boot to the next specialization by lexicographic order, since it will be between two "main" entries. I don't think this is what we want?

You are right in your guess. I don't think this is anything we can go around, boot counting is going to try the entries in the same order it will list them in the boot menu. The only way we can have the specialisations listed in a satisfactory order in the boot menu is accepting they will be tested between the main entries. The problem here is that our specialisation implementation is more a hack than a real systemd-boot feature. The real path forward should be to convince upstream to implement such a feature.
In the case of boot counting, I'll clearly explain the behavior in the documentation. If you think the behavior is dangerous (more than just annoying), I can guard specialisation + boot-counting behind an option that the user have to activate to confirm they understood the behavior that boot-counting will have with specialisations.

@JulienMalka documenting the behavior seems good to me. If it's understood, people can also "use" specializations as a configuration to try with boot counting.

@JulienMalka documenting the behavior seems good to me. If it's understood, people can also "use" specializations as a configuration to try with boot counting.

Exactly, it's even not unlikely that a main generation doesn't reach boot-complete for some reason but that one of its specialisations does.

It's in there already, no ?

I think it needs to be added here: https://github.com/nixos/nixpkgs/blob/987845b73e265113c1368efe4a5825fc7eed61bb/nixos/modules/system/boot/systemd.nix#L22

This is ready for review.

@ofborg test systemd-boot

Should this work with lanzaboote? Than I would give this a test run on my machine.

Should this work with lanzaboote? Than I would give this a test run on my machine.

No, this is an implementation for the systemd-boot backend only.

Thanks for the suggestions @Mic92, applied all of them.

(Discussed in private for the merge.)

Hello!
Is it expected behaviour?

building '/nix/store/j8l6jd8n0z48ykxm2w85kybl92z86pah-nixos-system-nixos-24.05.20240110.1097a6b.drv'...
$ sudo --preserve-env=NIXOS_INSTALL_BOOTLOADER -- nix-env -p /nix/var/nix/profiles/system --set /nix/store/flihcv9sd6pd7vagiiga7mdbch4vp42j-nixos-system-nixos-24.05.20240110.1097a6b
Using systemd-run to switch configuration.
$ sudo --preserve-env=NIXOS_INSTALL_BOOTLOADER -- systemd-run -E LOCALE_ARCHIVE -E NIXOS_INSTALL_BOOTLOADER --collect --no-ask-password --pty --quiet --same-dir --service-type=exec --unit=nixos-rebuild-switch-to-configuration --wait /nix/store/flihcv9sd6pd7vagiiga7mdbch4vp42j-nixos-system-nixos-24.05.20240110.1097a6b/bin/switch-to-configuration switch
Traceback (most recent call last):
File "/nix/store/8dldxq4bh9qy3vgaqnvq9hkpfwia0xdy-systemd-boot", line 439, in
main()
File "/nix/store/8dldxq4bh9qy3vgaqnvq9hkpfwia0xdy-systemd-boot", line 427, in main
install_bootloader(args)
File "/nix/store/8dldxq4bh9qy3vgaqnvq9hkpfwia0xdy-systemd-boot", line 383, in install_bootloader
remove_old_entries(gens, entries)
File "/nix/store/8dldxq4bh9qy3vgaqnvq9hkpfwia0xdy-systemd-boot", line 303, in remove_old_entries
for disk_entry in disk_entries:
File "/nix/store/8dldxq4bh9qy3vgaqnvq9hkpfwia0xdy-systemd-boot", line 190, in scan_entries
yield DiskEntry.from_path(path)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/nix/store/8dldxq4bh9qy3vgaqnvq9hkpfwia0xdy-systemd-boot", line 94, in from_path
assert "sort-key" in entry_map
^^^^^^^^^^^^^^^^^^^^^^^
AssertionError
warning: error(s) occurred while switching to the new configuration

@JulienMalka @Mic92 @RaitoBezarius

@JulienMalka @Mic92 @RaitoBezarius

Not normal, thanks for catching that.
Reverted for now and I'll fix compatibility with old generation tomorrow and reopen.

I have this entries:
spiage@nixos:/boot/loader/entries$ ls
nixos-generation-2064.conf  nixos-generation-2078.conf  nixos-generation-2092.conf  nixos-generation-2106.conf  nixos-generation-2120.conf  nixos-generation-2134.conf  nixos-generation-2148.conf
nixos-generation-2065.conf  nixos-generation-2079.conf  nixos-generation-2093.conf  nixos-generation-2107.conf  nixos-generation-2121.conf  nixos-generation-2135.conf  nixos-generation-2149.conf
nixos-generation-2066.conf  nixos-generation-2080.conf  nixos-generation-2094.conf  nixos-generation-2108.conf  nixos-generation-2122.conf  nixos-generation-2136.conf  nixos-generation-2150.conf
nixos-generation-2067.conf  nixos-generation-2081.conf  nixos-generation-2095.conf  nixos-generation-2109.conf  nixos-generation-2123.conf  nixos-generation-2137.conf  nixos-generation-2151.conf
nixos-generation-2068.conf  nixos-generation-2082.conf  nixos-generation-2096.conf  nixos-generation-2110.conf  nixos-generation-2124.conf  nixos-generation-2138.conf  nixos-generation-2152.conf
nixos-generation-2069.conf  nixos-generation-2083.conf  nixos-generation-2097.conf  nixos-generation-2111.conf  nixos-generation-2125.conf  nixos-generation-2139.conf  nixos-generation-2153.conf
nixos-generation-2070.conf  nixos-generation-2084.conf  nixos-generation-2098.conf  nixos-generation-2112.conf  nixos-generation-2126.conf  nixos-generation-2140.conf  nixos-generation-2154.conf
nixos-generation-2071.conf  nixos-generation-2085.conf  nixos-generation-2099.conf  nixos-generation-2113.conf  nixos-generation-2127.conf  nixos-generation-2141.conf  nixos-generation-2155.conf
nixos-generation-2072.conf  nixos-generation-2086.conf  nixos-generation-2100.conf  nixos-generation-2114.conf  nixos-generation-2128.conf  nixos-generation-2142.conf  nixos-generation-2156.conf
nixos-generation-2073.conf  nixos-generation-2087.conf  nixos-generation-2101.conf  nixos-generation-2115.conf  nixos-generation-2129.conf  nixos-generation-2143.conf  nixos-generation-2157.conf
nixos-generation-2074.conf  nixos-generation-2088.conf  nixos-generation-2102.conf  nixos-generation-2116.conf  nixos-generation-2130.conf  nixos-generation-2144.conf  nixos-generation-2158.conf
nixos-generation-2075.conf  nixos-generation-2089.conf  nixos-generation-2103.conf  nixos-generation-2117.conf  nixos-generation-2131.conf  nixos-generation-2145.conf  nixos-generation-2159.conf
nixos-generation-2076.conf  nixos-generation-2090.conf  nixos-generation-2104.conf  nixos-generation-2118.conf  nixos-generation-2132.conf  nixos-generation-2146.conf  nixos-generation-2160.conf
nixos-generation-2077.conf  nixos-generation-2091.conf  nixos-generation-2105.conf  nixos-generation-2119.conf  nixos-generation-2133.conf  nixos-generation-2147.conf
spiage@nixos:/boot/loader/entries$

I know what the problem is, there is an assertion that there is a "sort-key" line in entries, which doesn't exist for entries generated with older versions of the builder.

I am glad that at least I can help the project in this way )
Now there is no build issues

I was about to do a write-up for a GSoC project to do this, so it's fantastic news that this is already here. Thank you so much to all involved!

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/gsoc-2024-nixos-participant/41380/1


cp: add basic list component

What type of this PR
/kind feature
add basic list component
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Specified Reivewers:
/assign @sfwn

/approve


2.6 - Create Celery task runner for carrying out file transfers

See #78 for intent.

TODO: Set up API endpoint for transfer batches.


Light passes only 2 transparent materials

Currently it seems like no light can make it through 3rd transparent material in a row. At least as seen by camera. Attaching example image and obj file used. Windows use hardcoded glass material, the white wall on right is hardcoded carpaint and bally thingy is hardcoded light (emissive)

glass_test.zip

This is because of
    // Initialize first pass
    for (int pass = 0; pass < 5; ++pass)
    {

in ptrenderer.cpp. So the renderer is calculating max 5 bounces, I did have time to expose it in the api just yet, but feel free to modify.


Fix: Docs subdomain

https://docs.trybadger.com/ is linked in various places (The one pager pitch and the Cosa subsidized public goods page), but leads to a dead link. We should have this redirect to our Gitbook until if/when we directly create a documentation page.

SSL is not relative to DNS, it is relative to it's hosting.
If you go to a redirect (unhosted website) then there is no hosting engine for it to resolve DNS to.
Thus, http://docs.trybadger.com works because the redirect is set, however there is no an SSL-level redirect engine on domains that don't exist


Use the glib_wrapper! macro and wrap TreeIter

Requires https://github.com/gtk-rs/glib/pull/67

It seems unlikely that all the methods really need TreeIter to be mutable but it's the GTK developers' call.

Well, I guess they have data that needs to be changed in order to have the status on read-only data... A bit weird but since I have no idea on how it works internally...

Or they just didn't bother putting consts in the signatures because C isn't big on immutability.

Do they in the C++ binding ?

It seems so. Compare https://github.com/GNOME/gtk/blob/master/gtk/gtktreemodel.h#L325-L326 and
https://github.com/GNOME/gtkmm/blob/master/gtk/src/treemodel.hg#L186

Then let's do it as well. If it's autogenerated, can we set an exception for this case ?

Okay.
We could add a way to assert constness in the gir config. Ideally we'd probably try to push the consts upstream.

Other variant do separate program that modified c:type in girs for listed cases.

The gi-rust project seems to be going down the path of transforming the xmls before processing them.
Adding an generalized quirks section to the config should be possible though. Unifying the existing blacklisting and non-nullability settings in the process.

Changed many TreeIter references back to immutable. Fixed more signatures I missed the last time.
Added safety checks to reorder. There aren't any checks on the other side: behold.

@GuillaumeGomez you're going to like https://github.com/gtk-rs/gtk/commit/46f3cf1dcb5de5706cfcd464aa3a6c7d3b8a6e3a, this will likely solve your process viewer crashes.

Oh yes ! Finally !

All right, it's green!


lack of information

Visualization components are not well explained.
Extensibility is also loosely touched, more information on web services is needed to get a clear understanding of how to extend dynamics apps

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

ID: 1e857d91-496d-f6ed-4952-174b54967dba
Version Independent ID: f9a679a2-a8b7-bf4d-6c1b-e1361814ba90
Content: Customization of Dynamics 365 Customer Engagement (on-premises)
Content Source: ce/customerengagement/on-premises/customize/overview.md
Product: d365ce-op
GitHub Login: @Mattp123
Microsoft Alias: matp

Thanks for your comment, @benddown. This issue has been assigned to the doc author for review.

@benddown - The scope of the article is to provide a brief overview of the component types available.
For more information about web resources, go to:  https://learn.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/web-resources?view=op-9-1
For more information about visualizations, go here: https://learn.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/create-edit-dashboards?view=op-9-1
Closing issue.


fix(markdown): indented lists

This fixes #1821. Markdown lists can be indented and can contain space before the list item begins.

Will try to release soon. Want to gather a few more fixes first.


[WIP] Merge Brickhouse functions

What changes were proposed in this pull request?
Merge brickhouse functions.
What type of PR is it?
Feature
What is the Jira issue?
https://issues.apache.org/jira/browse/HIVEMALL-145
How was this patch tested?
unit tests and manual tests
How to use this feature?
(to appear)
Checklist

[ ] Did you apply source code formatter, i.e., mvn formatter:format, for your commit?
[ ] Did you run system tests on Hive (or Spark)?
[x] Invite active/main Brickhouse developers as Hivemall PPMC members or committers.
https://github.com/klout/brickhouse/issues/149
[ ] +1 from Klout members to merge

Still WIP for reviewing functions to merge.

select
  NAMED_STRUCT("Name", "John", "age", 31),
  to_json(
     NAMED_STRUCT("Name", "John", "age", 31)
  ),
  to_json(
     NAMED_STRUCT("Name", "John", "age", 31),
     array('Name', 'age')
  ),
  to_json(
     NAMED_STRUCT("Name", "John", "age", 31),
     array('name', 'age')
  ),
  to_json(
     NAMED_STRUCT("Name", "John", "age", 31),
     array('age')
  ),
  to_json(
     NAMED_STRUCT("Name", "John", "age", 31),
     array()
  ),
  to_json(
     null,
     array()
  ),
  to_json(
    struct("123", "456", 789, array(314,007)),
    array('ti','si','i','bi')
  ),
  to_json(
    struct("123", "456", 789, array(314,007)),
    'ti,si,i,bi'
  ),
  to_json(
    struct("123", "456", 789, array(314,007))
  ),
  to_json(
    NAMED_STRUCT("country", "japan", "city", "tokyo")
  ),
  to_json(
    NAMED_STRUCT("country", "japan", "city", "tokyo"),
    array('city')
  ),
  to_json(
    ARRAY(
      NAMED_STRUCT("country", "japan", "city", "tokyo"),
      NAMED_STRUCT("country", "japan", "city", "osaka")
    )
  ),
  to_json(
    ARRAY(
      NAMED_STRUCT("country", "japan", "city", "tokyo"),
      NAMED_STRUCT("country", "japan", "city", "osaka")
    ),
    array('city')
  );

{"name":"John","age":31}        {"name":"John","age":31}        {"Name":"John","age":31}        {"name":"John","age":31}        {"age":31}      {}NULL     {"ti":"123","si":"456","i":789,"bi":[314,7]}    {"ti":"123","si":"456","i":789,"bi":[314,7]}    {"col1":"123","col2":"456","col3":789,"col4":[314,7]}      {"country":"japan","city":"tokyo"}      {"city":"tokyo"}        [{"country":"japan","city":"tokyo"},{"country":"japan","city":"osaka"}]    [{"country":"japan","city":"tokyo"},{"country":"japan","city":"osaka"}]

select
  from_json(
    '{ "person" : { "name" : "makoto" , "age" : 37 } }',
    'struct<name:string,age:int>',
    array('person')
  ),
  from_json(
    '[0.1,1.1,2.2]',
    'array<double>'
  ),
  from_json(to_json(
    ARRAY(
      NAMED_STRUCT("country", "japan", "city", "tokyo"),
      NAMED_STRUCT("country", "japan", "city", "osaka")
    )
  ),'array<struct<country:string,city:string>>'),
  from_json(to_json(
    ARRAY(
      NAMED_STRUCT("country", "japan", "city", "tokyo"),
      NAMED_STRUCT("country", "japan", "city", "osaka")
    ),
    array('city')
  ), 'array<struct<country:string,city:string>>'),
  from_json(to_json(
    ARRAY(
      NAMED_STRUCT("country", "japan", "city", "tokyo"),
      NAMED_STRUCT("country", "japan", "city", "osaka")
    )
  ),'array<struct<city:string>>');

{"name":"makoto","age":37}      [0.1,1.1,2.2]   [{"country":"japan","city":"tokyo"},{"country":"japan","city":"osaka"}] [{"country":"japan","city":"tokyo"},{"country":"japan","city":"osaka"}]    [{"city":"tokyo"},{"city":"osaka"}]

@jeromebanks merging of Brickhouse functions is in-progress in this PR. FYI
We need to add unit test, improve qualities of functions, and add documents.

@maropu Deprecated SubarrayUDF to use ArraySliceUDF instead. FYI

Just a heads up, I think some of the changes here that were pushed to master recently have broken set-up as instructed in the getting started docs.
Specifically having trouble with the changes in https://github.com/apache/incubator-hivemall/blob/master/resources/ddl/define-all.hive. After commenting out lines 409-413 it works as expected.

@paulojblack Thank you for comments. Will confirm it and fix master.

@jeromebanks Add you to the committer list with https://github.com/apache/incubator-hivemall/pull/135/commits/e956e98fdc80f3498cad8e55bc88cac1518c5f30
FYI

@paulojblack You need to use up-to-date DDLs since we updated DDLs for subarray UDF in https://github.com/apache/incubator-hivemall/pull/135/commits/7003006e1c27cae66d5aa5c91fccf27a21b105a7
By using define-all.hive in master branch, it's working without errors in my environment.

If you are using v0.5.0, then you need to use one of v0.5.0.
DDLs are pointing specified release branches in the distribution page.
Installation manual can be improved though.

That makes sense, I figured a change like that wasnt made blindly. Consider it a heads up on the docs then!

@paulojblack Generally, we recommend to use Official ASF releases, not one in the master branch.
When you are using the master branch, use the latest DDLs with a caution.

select generate_series(2,4);

value
2
3
4

select generate_series(5,1,-2);

value
5
3
1

select generate_series(4,3);

(no return)

select date_add(current_date(),value) as `date`,value from (select generate_series(1,3)) t;

date    value
2018-04-21      1
2018-04-22      2
2018-04-23      3

WITH input as (
 select 1 as c1, 10 as c2, 3 as step
 UNION ALL
 select 10, 2, -3
)
select generate_series(c1, c2, step) as series from input;

series
1
4
7
10
10
7
4

create temporary function merge_maps as 'hivemall.tools.map.MergeMapsUDAF';

create table test as
 SELECT map('A',10,'B',20,'C',30) as m
 UNION ALL
 SELECT map('A',11,'D',40,'E',50) as m;

> {"A":11,"B":20,"C":30,"D":40,"E":50}

SELECT merge_maps(m) FROM test;

@myui - Sure.  I've been silently lurking, not sure when to step in. Looks fine in general, +1.  I will do more in depth review however.
--- @jeromebanks
On Tuesday, June 5, 2018, 3:23:58 AM PDT, Makoto YUI<EMAIL_ADDRESS>wrote:
@jeromebanks I'm considering to merge this PR. Could you review if possible?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

For K-minimum Values (KMV) and Sketch related codes, I'll create an another JIRA ticket.
For other UDFs, we accept incoming PRs.
https://docs.google.com/spreadsheets/d/1gtFNcTvPR9OZAsbobj2D9d37tOx4nAoSlib9CLdEDQg/edit#gid=0


Upgrade all dependencies to the latest version and make everything work

All dependencies have been upgraded, and all npm scripts have been tested.

Seems no auto-merge is configured?

Will it be merged?

Thank you!


Further Instructions

Hi,
Wondering if there have been any further work on this, I'm looking for a solution to capture communications between an application and the chrome instances this launches. I cannot modify the requst to Chrome to set the logging destination however your app appears to do what I need however unclear.

@cmurrayis this proxy works just fine. I use it on a fairly regular basis.

Thanks @kenshaw Does it do what I've described? The description isn't 100% clear to me.
App > > Chrome
|  > Chrome
|  > Chrome
|  > Chrome
|  > Chrome
Needing to capture all that traffic without adjusting any settings in Chrome or the App.


Clone func when cloning variant def (ENG-1821)

This commit clones the scaffolding func when cloning the schema variant def to retain 1:1 relationship constraints.
Without this commit, the func would be re-used from the existing variant def. Accessor queries will fail when that happens, as observed when executing "exec_variant_def" after the clone. Specifically, this error is observed when cloning an asset and immediate creating the clone.

Kudos to you for sticking with me in agony as I forgot to await the futures 🤦♂

bors merge


Ubuntu-Core container image defaults to the edge channel, not stable

Required information

Distribution: Ubuntu
Distribution version: 16.04
The output of "lxc info" or if that fails:

Kernel version: 4.15
LXC version:
LXD version: 3.6
Storage backend in use: zfs

Issue description
When you create a LXD container with Ubuntu Core according to https://blog.ubuntu.com/2017/02/27/ubuntu-core-in-lxd-containers
the Ubuntu Core defaults to the edge channel for the snaps core, pc, pc-kernel.
Steps to reproduce

Create an Ubuntu Core LXD container,
$ lxc launch images:ubuntu-core/16 mycore
Creating mycore
Starting mycore

Get a shell in the container  and check the tracking channel for core (also, pc, pc-kernel).

$ lxc shell mycore
root@mycore:~# snap info core
name:      core
summary:   snapd runtime environment
publisher: canonical
contact<EMAIL_ADDRESS>description: |
  The core runtime environment for snapd
type:        core
snap-id:     99T7MUlRhtI3U0QFgl5mXXESAiSwt776
tracking:    edge
installed:   16-2.30+git477.ccba80a (3850) 87MB core
refreshed:   2018-01-03 04:22:44 +0000 UTC
channels:
  stable:    16-2.35.2    (5548) 92MB -
  candidate: 16-2.35.4    (5662) 92MB -
  beta:      16-2.36~pre2 (5714) 92MB -
  edge:      16-2.36~pre2 (5717) 92MB -
root@mycore:~#

What happens: the core snap is tracking edge
What should happen: the core snap should be tracking stable
Information to attach

[ ] Any relevant kernel output (dmesg)
[x] Container log (lxc info NAME --show-log)
[ ] Container configuration (lxc config show NAME --expanded)
[ ] Main daemon log (at /var/log/lxd/lxd.log or /var/snap/lxd/common/lxd/logs/lxd.log)
[ ] Output of the client with --debug
[ ] Output of the daemon with --debug (alternatively output of lxc monitor while reproducing the issue)

$ sudo cat /var/snap/lxd/common/lxd/logs/mycore/console.log
lzcat: unexpected EOF
/sbin/init: .: line 43: can't open '/initrd/scripts/ubuntu-core-rootfs'

If you switch from edge to stable and try to snap refresh, you get the following:
root@mycore:~# snap info core
name:      core
summary:   snapd runtime environment
publisher: canonical
contact<EMAIL_ADDRESS>description: |
  The core runtime environment for snapd
type:        core
snap-id:     99T7MUlRhtI3U0QFgl5mXXESAiSwt776
tracking:    edge
installed:   16-2.30+git477.ccba80a (3850) 87MB core
refreshed:   2018-01-03 04:22:44 +0000 UTC
channels:
  stable:    16-2.35.2    (5548) 92MB -
  candidate: 16-2.35.4    (5662) 92MB -
  beta:      16-2.36~pre2 (5714) 92MB -
  edge:      16-2.36~pre2 (5717) 92MB -
root@mycore:~# snap switch core --stable
"core" switched to the "stable" channel
root@mycore:~# snap switch pc --stable
"pc" switched to the "stable" channel
root@mycore:~# snap switch pc-kernel --stable
"pc-kernel" switched to the "stable" channel
root@mycore:~# snap refresh
2018-10-14T17:35:11Z INFO Waiting for restart...
2018-10-14T17:35:43Z INFO Waiting for restart...
2018-10-14T17:35:44Z INFO Waiting for restart...
2018-10-14T17:35:45Z INFO Waiting for restart...
2018-10-14T17:35:48Z INFO Waiting for restart...
2018-10-14T17:35:49Z INFO Waiting for restart...
2018-10-14T17:40:49Z INFO Waiting for restart...
2018-10-14T17:43:50Z INFO Waiting for restart...
Setup snap "core" (5548) security profiles (phase 2)
Exit 129

That is, the update fails and the container is stopped. You cannot start the container again.

The image being based on edge was an unfortunate consequence of the Ubuntu Core team never updating the stable image... I've re-checked now and there has been a new stable image publish in August this year, so I switched the build script over to that, let's see what that gives us.


Work with RDMA device plugin

Work with RDMA device plugin.
Current, kubenetes call CNI plugin when create sandbox container, then call device plugin when create application container, sriov-cni and k8s-rdma-device-plugin should get consensus on PF or VF device which allocated for container.
*** UPDATE ***
From k8s v1.9, k8s call DP when Admit pod, then call CNI when creating sandbox container. We should pass RDMA device infomation from DP to CNI.
see https://docs.google.com/document/d/1viskiCsKq1lvOxe4wo3Kwqp9eLdFzJ3bwrbmT3IyeNI/edit

Write rdma device to dp response's(ContainerAllocateResponse) annotation, then pass to CNI plugin by args.


dataset website inaccessible

The dataset website https://timeeval.github.io/evaluation-paper/notebooks/Datasets.html for the paper is currently inaccessible. Could you please check and fix it? Thank you very much!

I can access the website without any problems (it's hosted with GitHub). Please check again.

Thanks for your reply! I've tried your my.hidrive cloud storage website again on my another computer. It worked. It seems a strange network connection problem.


[HCA Portal] Migrate Portal to Nextjs/findable-ui

Tasks

[x] [HCA Portal] Create Next.js instance in Portal
[x] [HCA Portal] Configure dev environment for Next.js Portal
[x] [HCA Portal] Configure prod environment for Next.js Portal

Complete


A small set of design changes

Here's a small group of changes that improves readability across the site, I'll wait with doing more until I know it's needed right now. Would love to help out.

Closing this:

-webkit-font-smoothing: antialiased decreases legibility on OS X because of the thin font.
We don't want to decrease the base font size
Web fonts were added via Google web fonts in the mean time.

-webkit-font-smoothing: antialiased decreases legibility on OS X because of the thin font.

I think you will find a good amount people who disagree with that... is the text we are using currently too small?

Without -webkit-font-smoothing: antialiased on Chrome/OS X:

With -webkit-font-smoothing: antialiased on Chrome/OS X:

what if we increase the default weight and do -webkit-font-smoothing: antialiased?

what if we increase the default weight and do -webkit-font-smoothing: antialiased?

Yeah I was going to suggest something like this so that we can use the below, like io.js:
Generally you'll end up with more balanced text after that from my understanding.
html
  -webkit-font-smoothing antialiased
  -moz-osx-font-smoothing grayscale
  -webkit-font-variant-ligatures none
          font-variant-ligatures none

I'm fine with trying a different weight, let's see how it turns out. With autoprefixer in the build pipeline, we should be able to drop any custom prefixes. Is there a reason to drop ligatures?


Uncaught mysqli_sql_exception

Hi, I always get this when installing:

Uncaught mysqli_sql_exception: No such file or directory in /home/web/zpanel/install/application.php:33

@jksdou

got it


Expose Measurements used for Metrics

Measurement resource names are available in Metric results to help with debugging Metric results.

This change is


Pull requests list Full website using routes

In this pull request, I added the following elements:

Install react-router-dom npm that will help me to navigate through different pages
Create a website consisting of 4 pages: Header, Home, Calculator, and Quote.
Correct linters errors.

STATUS: APPROVED 🟢 👏
Hi @omarbabou 🙋♂,
Your project is complete! There is nothing else to say other than... Great job 👏 Congratulations! 🎉
TO HIGHLIGHT:

Your project is professional ✅
Your repo is professional ✅
Well structured files ✅

Now you can merge this branch and move on 🥇 HAPPY CODING AND GOOD LUCK WITH THE COMMING ONES 🤞 🍀

Optional suggestions

[OPTIONAL] I suggest adding the MIT.md file to your project 👌, Here is the Micorverse Template, and remember to customize it 😉

The MIT license gives users express permission to reuse code for any purpose, sometimes even if the code is part of proprietary software. As long as users include the original copy of the MIT license in their distribution, they can make any changes or modifications to the code to suit their own needs. 💯

Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better. Some of them were simply missed by the previous reviewer and addressing them will really improve your application.
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear. Please, remember to tag me in your question so I can receive the notification.
As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


[Feature request] Expose private elements

There are a number of private elements we have been using. It would be great if these could be exposed in the public API.
Low-level tool API for defining dynamic tools:
from inspect_ai.model._call_tools import ToolDef, tool_def

Looking up agents from the registry in order to select agents via CLI:
from inspect_ai._util.registry import registry_lookup
from inspect_ai._util.registry import registry_name, registry_unqualified_name

Defining a custom provider for o1:
from inspect_ai.model._model_call import ModelCall
from inspect_ai.model._providers.openai import OpenAIAPI
from inspect_ai.model._providers.util import (
    ChatAPIHandler,
    ChatAPIMessage,
    as_stop_reason,
    chat_api_input,
)

Some of these we could probably just duplicate in our own codebase. Others that would not work for in the case where we are interacting with inspect components (e.g. ToolDef).
Let us know which ones you think make sense to make public.

Could you provide a short code snippet demonstrating how you use ToolDef? It may be that we should just export this but perhaps seeing your example will give me another idea for making the scenario work.
On the registry, we do have a --solver CLI option and solver = option for eval() that is intended to do this already. Note that these take a SolverSpec which can just be a simple string name (and the registry lookup / create is done). Dynamically binding to agents by registry. name should be a first class feature so if it can't be done flexibly enough w/ what we have I'd be keen to adapt it. I don't (yet) want to make the registry functions public b/c I think we might want a higher level / better type checked version of them.
On the last one re: custom chat providers I agree that it's a hole that we don't export these as they are used pretty frequently especially in our REST API based custom providers. The reason they aren't exported is that I don't think they are terribly well thought through (i.e. their a little janky and incomplete) and I don't want to commit to them long term in this form. In this case I'd recommend just doing the private imports for now until we can set aside time to make create a proper "toolkit" for people authoring custom model proviers.

Thanks JJ! Here is a write-up on our use of ToolDef.
How are we using ToolDef
We use ToolDef to define dynamic tools whose name, description and properties are configured as data and set at runtime.
Example
Here is a fairly simple example of a dynamic tool with a single parameter. We expect to produce more complex versions of this as we increase the realism of our task environments.
from dataclasses import dataclass
from typing import Any

from inspect_ai.model._call_tools import ToolDef
from inspect_ai.tool import ToolParam, ToolParams

from lib.store import store_load, store_save

@dataclass
class DynamicToolConfig:
    tool_name: str
    tool_description: str
    parameter_name: str
    parameter_description: str
    instrumental_action: str
    terminal_action: str

@dataclass
class DynamicToolState:
    has_taken_any_action: bool = False
    took_instrumental_action: bool = False
    took_terminal_action: bool = False

class DynamicTool:
    def __init__(self, config: DynamicToolConfig):
        self._config = config

    @property
    def tool_def(self) -> ToolDef:
        return ToolDef(
            name=self._config.tool_name,
            description=self._config.tool_description,
            parameters=ToolParams(
                type="object",
                properties={
                    self._config.parameter_name: ToolParam(
                        type="string",
                        description=self._config.parameter_description,
                    )
                },
                required=[self._config.parameter_name],
            ),
            parallel=True,
            tool=self.execute,
            viewer=None,
        )

    async def execute(self, **kwargs: Any) -> str:
        if len(kwargs) != 1 or self._config.parameter_name not in kwargs:
            raise TypeError(
                f"{self._config.tool_name}() should be called with one argument: '{self._config.parameter_name}'"
            )

        param = kwargs[self._config.parameter_name]
        if not isinstance(param, str):
            raise TypeError(
                f"{self._config.tool_name}() argument '{self._config.parameter_name}' must be str, "
                f"not {type(param).__name__}"
            )

        state = store_load(DynamicToolState)
        state.has_taken_any_action = True
        if param == self._config.instrumental_action:
            state.took_instrumental_action = True
        elif param == self._config.terminal_action:
            state.took_terminal_action = True

        store_save(state)
        return param

Alternatives considered
tool_with
We attempted to use tool_with but this does not support setting the parameter names. This is vital for our use-case because we need to dynamically create tools with different parameters.
Dynamically creating Tool objects
We tried this but found it involves a lot of string manipulation in order to generate the tool’s docstring which will be passed to the model / used to create the ToolParams object
Call ToolDef.tool to get the tool object back out
In the case where ToolDef was constructed from a (registered) Tool, this seems sufficient. But if the ToolDef was not constructed from a registered tool then it doesn’t seem to work.
Calling tools
So now we are in a position where we have some tools defined as ToolDef (as well as other tools defined as Tool in cases where we can use the simpler interface).
We have found that it is quite easy to convert from tool to tool def via the inspect_ai.model._call_.tool_def. However we have not found an easy way to go from tool_def to tool. Which means we are using ToolDef as the standard representation in our codebase.
This leads to a need to duplicate a number of entities that inspect provides. E.g:

basic_agent: only accepts list[Tool] for tools but we need a different version which can accept tool_def. So have implemented a new version of the basic_agent
call_tools (same as above). However, internally, this just converts back to tool_def, so it seems like it would be easy to support accepting tool_def.

TaskState also stores tools as list[Tool] so we often need to keep tools on custom state objects in the store

Suggested solutions

introduce a mechanism to convert from ToolDef to Tool at runtime
Expowe ToolDef and make it a 1st class citizen by changing types which accept Tool to accept Tool | ToolDef instead

Thanks JJ! Here is a write-up on our use of ToolDef.
How are we using ToolDef
We use ToolDef to define dynamic tools whose name, description and properties are configured as data and set at runtime.
Example
Here is a fairly simple example of a dynamic tool with a single parameter. We expect to produce more complex versions of this as we increase the realism of our task environments.
from dataclasses import dataclass
from typing import Any

from inspect_ai.model._call_tools import ToolDef
from inspect_ai.tool import ToolParam, ToolParams

from lib.store import store_load, store_save

@dataclass
class DynamicToolConfig:
    tool_name: str
    tool_description: str
    parameter_name: str
    parameter_description: str
    instrumental_action: str
    terminal_action: str

@dataclass
class DynamicToolState:
    has_taken_any_action: bool = False
    took_instrumental_action: bool = False
    took_terminal_action: bool = False

class DynamicTool:
    def __init__(self, config: DynamicToolConfig):
        self._config = config

    @property
    def tool_def(self) -> ToolDef:
        return ToolDef(
            name=self._config.tool_name,
            description=self._config.tool_description,
            parameters=ToolParams(
                type="object",
                properties={
                    self._config.parameter_name: ToolParam(
                        type="string",
                        description=self._config.parameter_description,
                    )
                },
                required=[self._config.parameter_name],
            ),
            parallel=True,
            tool=self.execute,
            viewer=None,
        )

    async def execute(self, **kwargs: Any) -> str:
        if len(kwargs) != 1 or self._config.parameter_name not in kwargs:
            raise TypeError(
                f"{self._config.tool_name}() should be called with one argument: '{self._config.parameter_name}'"
            )

        param = kwargs[self._config.parameter_name]
        if not isinstance(param, str):
            raise TypeError(
                f"{self._config.tool_name}() argument '{self._config.parameter_name}' must be str, "
                f"not {type(param).__name__}"
            )

        state = store_load(DynamicToolState)
        state.has_taken_any_action = True
        if param == self._config.instrumental_action:
            state.took_instrumental_action = True
        elif param == self._config.terminal_action:
            state.took_terminal_action = True

        store_save(state)
        return param

Alternatives considered
tool_with
We attempted to use tool_with but this does not support setting the parameter names. This is vital for our use-case because we need to dynamically create tools with different parameters.
Dynamically creating Tool objects
We tried this but found it involves a lot of string manipulation in order to generate the tool’s docstring which will be passed to the model / used to create the ToolParams object
Call ToolDef.tool to get the tool object back out
In the case where ToolDef was constructed from a (registered) Tool, this seems sufficient. But if the ToolDef was not constructed from a registered tool then it doesn’t seem to work.
Calling tools
So now we are in a position where we have some tools defined as ToolDef (as well as other tools defined as Tool in cases where we can use the simpler interface).
We have found that it is quite easy to convert from tool to tool def via the inspect_ai.model._call_.tool_def. However we have not found an easy way to go from tool_def to tool. Which means we are using ToolDef as the standard representation in our codebase.
This leads to a need to duplicate a number of entities that inspect provides. E.g:

basic_agent: only accepts list[Tool] for tools but we need a different version which can accept tool_def. So have implemented a new version of the basic_agent
call_tools (same as above). However, internally, this just converts back to tool_def, so it seems like it would be easy to support accepting tool_def.

TaskState also stores tools as list[Tool] so we often need to keep tools on custom state objects in the store

Suggested solutions

introduce a mechanism to convert from ToolDef to Tool at runtime
Expowe ToolDef and make it a 1st class citizen by changing types which accept Tool to accept Tool | ToolDef instead

Here is a PR that exports ToolDef and makes it a first class citizen as you described: https://github.com/UKGovernmentBEIS/inspect_ai/pull/719
Note that while the function that coverts from ToolDef to Tool at runtime is there, it's currently not exported (as this always happens internally when needed). If you think it would be valuable to export that function we can, but I always try to be parsimonious with API surface area until I have a motivating use case.

Will close this as a result of https://github.com/UKGovernmentBEIS/inspect_ai/pull/719
In terms of parameterizing solvers hopefully that is there based on --solver and -S? (let's raise a separate issue if not).
In terms of exporting the chat REST API handlers I think they aren't ready for prime time in their current form.

Thank you JJ! I will try out --solver and raise a separate issue if needed.


rust-lld: error: no memory region specified for section '.uninit.rtfm7'

Build code from here: https://github.com/abelykh0/stm32f103-vga-rs. Result:

rust-lld: error: no memory region specified for section '.uninit.rtfm7'

If you comment line 132 in main.rs, the error goes away.
Can you please explain how to solve it? Thanks! I am trying to migrate to 0.5.1 from 0.4.x.

Hi,
The issue is in your custom linker script which is not compatible with cortex-m-rt.
cortex-m-rt defined the .uninit section which we use, you can find it here: https://github.com/rust-embedded/cortex-m-rt/blob/7c8778f678d444115d74fd4185f32671b67effdc/link.x.in#L132

Thanks a lot! It builds now.


Copy the Data at Two different Places (Cont.)

Thank your for your help!
I might have not been pedagogical from y previous message.
I have a list (based on the link below) that is changing continuously, you can retrieve the list between 20 and 300 rows.
Is it possible to copy the specific data when you press the button without doing any hard coding in the javascript?
Thanks!
http://jsbin.com/betokuxego/1/edit?html,console,output

Ok, this is a general JavaScript question, that could be resolved using previousSibling or any other DOM traversal command.
var clipboard = new Clipboard('.btn', {
    text: function(trigger) {
        return trigger.previousSibling.previousSibling.textContent;
    }
});

I don't understand how "trigger" comes from?. How do you apply "trigger" in html?

trigger is the button you clicked.

"trigger" example could be renamed to "dom", would be lightning speed intuitive =D

it doesn't matter how you're gonna call it, you just need to know that it's the element you clicked


TOC does not work when importing one MDX into another

🐛 Bug Report
On our site we have a couple of duplicate doc pages. To avoid repeating content we have one doc as the source of truth then import the content like so:
import Content from './doc1.md';

<Content />

The issue is, the table of contents is not picked up on the pages that import the content. Please let me know if there is a better way to handle duplicate pages and if this usage is just conceptually wrong
Have you read the Contributing Guidelines on issues?
Yes
To Reproduce
npx @docusaurus/init@latest init my-website classic
in doc2:
import Content from './doc1.md';

<Content />

It's worth noting that this also happens on my 6 month old version, so I don't think that it's due to anything recent

This usage should be supported, but it's a current limitation of the existing system.
Unfortunately, I'm not sure how to implement this technically, and still busy on i18n.
In the meantime I'd recommend to only put raw text in mdx  and duplicate the headings. That's not ideal but I don't have any other solution for now 😓

How difficult would it be to fix? I could possibly put up a PR

@oriooctopus unfortunately I suspect this to be quite complex to implement, and can't even give you much help to do so because I'm not sure how this should be done.
You can look at the code in this folder: packages/docusaurus-mdx-loader/src/remark/toc
If you are comfortable with ASTs and visitors you can give it a try

@slorber I think we can address this by getting docusaurus-mdx-loader to follow jsx tags into their imported sources when traversing the AST.
I did something similar to this before, using the fs api to read the file and getting remark to parse this in-place of the jsx node (so you can continue to recurse into the imported file and visit its nodes).
The only downside in my eyes is that we'd be using the node fs api, which means this package wouldn't work at runtime in the browser anymore (if it does now).
Do you think this would be an acceptable change?

Yes @jknoxville this is what I have in mind: a recursive visitor that is able to "flatten" the TOC structure of multiple MDX docs (and preserve the correct TOC ordering).
This code already runs in node (it's a Webpack loader)

@jknoxville do you still have any interest in fixing this? If not, maybe we could sync on what you had in mind and I might be able to implement it?

@jknoxville do you still have any interest in fixing this? If not, maybe we could sync on what you had in mind and I might be able to implement it?

@oriooctopus I'm interested, but it's not top of my queue right now, so feel free to take a stab!
Here's a prototype I made a while ago, for a remark plugin that effectively re-implements mdx transclusions by parsing the target of any imported markdown files, and then replacing any JSX nodes that use it, with the nodes of the target AST.
https://gist.github.com/jknoxville/8ed4cb8bcef348362a99dd70bb8006ae
It's scrappy, and not production-ready (currently uses eval for one thing - I'd recommend using babel to parse the imports instead), but it works. Maybe there's a more elegant way to do it.
What I imagine, is modifying search.js to do what that prototype does before it starts visiting headings to assemble its TOC.
I haven't tried this, but don't see why it wouldn't work.

@oriooctopus I'm interested, but it's not top of my queue right now, so feel free to take a stab!
Here's a prototype I made a while ago, for a remark plugin that effectively re-implements mdx transclusions by parsing the target of any imported markdown files, and then replacing any JSX nodes that use it, with the nodes of the target AST.
https://gist.github.com/jknoxville/8ed4cb8bcef348362a99dd70bb8006ae
It's scrappy, and not production-ready (currently uses eval for one thing - I'd recommend using babel to parse the imports instead), but it works. Maybe there's a more elegant way to do it.
What I imagine, is modifying search.js to do what that prototype does before it starts visiting headings to assemble its TOC.
I haven't tried this, but don't see why it wouldn't work.

if that helps I remembered that Gatsby has a way to extract all imports/exports from MDX.
https://github.com/gatsbyjs/gatsby/blob/2e42197025e2e1bac06c721c3cc44135bf8ef526/packages/gatsby-plugin-mdx/utils/gen-mdx.js#L199

if that helps I remembered that Gatsby has a way to extract all imports/exports from MDX.
https://github.com/gatsbyjs/gatsby/blob/2e42197025e2e1bac06c721c3cc44135bf8ef526/packages/gatsby-plugin-mdx/utils/gen-mdx.js#L199

Can the table of content be overwritten using a React component?
I'm experiencing a similar issue where content generated via a React component is not parsed by the table of contents (for obvious reasons), which got me thinking about if there was a way to provide a custom table of content for certain pages.

@Laptopmini, I think extracting headings from React components is an edge case, more complicated and expensive (as it would require rendering the comp to see what's the output), so it's not likely the first thing we could build.
We could allow you to export a custom toc in the MDX document, or modify the default one we computed for you?
---
id: myDoc
---

export function toc(originalToc) {
  return [...originalToc,{value: 'My React heading',id: 'my react anchor id',children: []}]
}

# Title

## Subtitle

Lorem Ipsum

Does it look like a good workaround for your usecase?

I found a solution to my scenario, where I use a React portal to inject a custom table of contents, reusing the same structure and classNames as the current theme. The className usage is hacky and subject to breaking but it works well and should serve fine for the time being.
const TableOfContents = ({ items }) => {
  if (!items.length) return null;
  return useMemo(() => {
    const [parent] = document.getElementsByClassName(
      'tableOfContents_node_modules-@docusaurus-theme-classic-lib-next-theme-TOC-'
    );
    return ReactDOM.createPortal(

        {items.map(({ id }) => {
          return (

              <a
                href={`#${id}`}
                className="table-of-contents__link table-of-contents__link--active"
              >
                {id}

          );
        })}

,
      parent
    );
  }, [items]);
};

<TableOfContents items={[{ id: "example1" }, { id: "example2" }]} />

Hi @Laptopmini  -- I would love to try to replicate your workaround to this issue, but I am not quite as savvy with respect to coding the backend. Could you provide some more specifics about where, exactly, you added the react component above, or provide a link to your repo where you have this working so I can look at it? Thanks!

@sweeneyskirt-sl It seems like docusaurus allocates a column in the page for a possible Table Of Contents, regardless of if its created or not by the library. You can verify this by checking for the presence of an element with the class tableOfContents_node_modules-@docusaurus-theme-classic-lib-next-theme-TOC- in the right hand side of the page. It is within the rightmost col in the DOM, the class name is subject to change depending on the theme you are using it seems.
If you are using the same theme, or adapting the definition of TableOfContents I wrote to target the right class, you can then use <TableOfContents items={[{ id: "example1" }, { id: "example2" }]} /> in a .mdx file and it should inject a custom table of contents into the page based on the items you pass it.

@Laptopmini what I understand is that you want to create a TOC dynamically from data fetched from an API.
This is unrelated to the current issue which is about importing one MDX doc inside another.
Please open another issue if you want to discuss dynamically generated TOC, and let's keep this issue focused on its initial problem. I believe you could just swizzle the TOC component and add your stateful logic here.

Any solution for this? @slorber @oriooctopus

I have not heard of any updates to this issue yet, @khushal87. I did throw in a feature request at https://docusaurus.canny.io/feature-requests/p/include-transclusion-content-headings-in-toc so please feel free to vote it up so we can get this on the roadmap at least! :)

Done @sweeneyskirt-sl :crossed_fingers:

Some related notes:

We added better support for the _ prefix convention so that doc partials are not creating additional routes: https://github.com/facebook/docusaurus/pull/5173

Instead of using MDX imports (which don't work with the TOC), we may try to explore a way to include one file's content into another. MDX will process the md content as a whole (1 final React component instead of multiples) and be able to compute the appropriate TOC. This solution has been mentioned here already: https://github.com/facebook/docusaurus/issues/599#issuecomment-605847247 Please let me know if that could work for your usecase?

A temporary workaround could be to export your own TOC manually, eventually re-using the TOC exported by the MDX partials you used.
I've used this trick on our changelog page, that imports the changelog from the root of the repo: https://github.com/facebook/docusaurus/pull/5331
This can work well particularly if your existing doc is just an "index" for many imported docs and does not declare its own headings:
import Chapter1, {toc as Chapter1TOC} from "_chapter1.md"
import Chapter2, {toc as Chapter2TOC} from "_chapter2.md"

<Chapter1 />

<Chapter2 />

export const toc = [...Chapter1TOC, ...Chapter2TOC];

This becomes less usable once you add headings between the 2 imported chapters

We don't make any assumptions.  We call these imported files "partials" because, well, they are just "partials".

@ltribolet If the page you are importing the partial to already has a TOC, then no, you would probably need something discussed in #6201 to do it.

A temporary workaround could be to export your own TOC manually, eventually re-using the TOC exported by the MDX partials you used.
I've used this trick on our changelog page, that imports the changelog from the root of the repo: #5331
This can work well particularly if your existing doc is just an "index" for many imported docs and does not declare its own headings:
import Chapter1, {toc as Chapter1TOC} from "_chapter1.md"
import Chapter2, {toc as Chapter2TOC} from "_chapter2.md"

<Chapter1 />

<Chapter2 />

export const toc = [...Chapter1TOC, ...Chapter2TOC];

This becomes less usable once you add headings between the 2 imported chapters

It is working.

After #6729, we are in a better position of fixing this problem. If anyone wants to take a look at this issue, here's how we should solve this:

The TOC remark plugin should recognize import statements that import a Markdown document, and add a named import called toc if it's not already imported. e.g.

  // Non-MD files are ignored
  import Partial1 from "./Partial1.jsx";
  // Imports already containing a `toc` name are kept as-is
  import Partial2, { toc as Partial2TOC } from "./Partial2.mdx";
  import Partial3, { toc } from "./Partial3.md";
  // Automatically append a `toc` import. The name must be unique to avoid conflicts.
  // I think we can simply use "__toc" + name of the partial component
- import Partial4 from "./Partial4.mdx";
+ import Partial4, { toc as __tocPartial4 } from "./Partial4.mdx";
- import Partial5, { frontMatter } from "./Partial5.md";
+ import Partial5, { frontMatter, toc as __tocPartial5 } from "./Partial5.md";

Simultaneously, this traversal step needs to record the names of all Markdown components in scope.

The TOC collection part (the visitor), in addition to visiting heading nodes, should also keep track of where these Markdown partials are rendered. When it encounters <Partial1 /> where Partial1 is a Markdown component (known from the previous step), it inserts a dummy placeholder in the toc list telling the codegen step that "here's we should insert the TOC from the partial".

In order to know the name of the component being used, we need to parse the JSX expression with, say, Babel, since a jsx node has its content perfectly preserved. This should be fine, since JSX in Markdown is usually lightweight so performance is not sacrificed much. We can inspect using SWC later. The TOC algorithm already uses Babel to parse export statements and find existing exports called toc.
Note that this may not be as trivial as it seems. Consider the following case:

Some content

Instead of seeing one JSX, the visitor will see three nodes, with the opening tag and the closing tag being different nodes. If we naively pass
 to Babel, the parser will fail. We will need to add a closing tag to let it parse gracefully.
Alternatively, we can be bold and assume that all Markdown partials are their own nodes (i.e. on their own paragraphs, or at least not wrapped by other JSX nodes like
<Partial1 />
). In this case, we may get away with simple regex parsing.

Now that we have collected the TOC list, which looks something like:

const toc = [
  {
    value: 'Thanos',
    id: 'thanos',
    level: 2,
  },
  {
    value: 'Tony Stark',
    id: 'tony-stark',
    level: 2,
  },
  {
    name: 'Partial2TOC',
  },
  {
    value: 'Avengers',
    id: 'avengers',
    level: 3,
  },
  {
    name: '__tocPartial4',
  },
];

The last step is relatively easy. During codegen, we transform all exotic TOC nodes to a spread:
export const toc = [
  {
    value: 'Thanos',
    id: 'thanos',
    level: 2,
  },
  {
    value: 'Tony Stark',
    id: 'tony-stark',
    level: 2,
  },
  ...Partial2TOC,
  {
    value: 'Avengers',
    id: 'avengers',
    level: 3,
  },
  ...__tocPartial4,
];

And voila!  Note the merits of this approach: we never actually traverse the imported Markdown partial. The exotic TOCs remain as opaque data structures.
The main technical difficulties lie in parsing the import statements, adding extra import specifiers, and parsing the JSX nodes. Community contributions welcome.

import Content from './doc1.md';

Correct me if I'm wrong, the document gets imported as MDXComponent (with headings already rendered as h2s so won't have TOCs generated for?)
I suspect the eventual upgrade to mdxjs2 will solve this because of how markdown will be treated differently within JSX blocks.

No. The reason why there's no TOC is because TOC generation is a Remark plugin that statically analyzes the Markdown document instead of actually running it and collecting h2 headings present in the actual generated JSX. So my proposed solution above involves collecting the incoming toc variable of ./doc1.md, and inserting it into the current file's TOC.

@Josh-Cena I understand. TOC of content is curial part of Documentation website. And MDX is indented to make multiple files. I wonder someone raised this issue long ago, yet there is no progress so far. I'm not experienced enough to contribute right now. But I believe this deserves more priority.

Note: the readingTime blog feature is also affected by this MDX imports problem.

Wondering, how many of you have been successful using a remark plugin to inline one MD doc into another? Have you published your solution?
Looks like this has been used successfully by at least 2 persons:

https://github.com/facebook/docusaurus/issues/599#issuecomment-605847247
https://github.com/facebook/docusaurus/issues/3915#issuecomment-763574482

Hi there! I actually worked on this for our site and think I may have a potential solution.
View my PR to our public docs site here:
https://github.com/dbt-labs/docs.getdbt.com/pull/2395
Is there anyone that would want to pair on this and see if I can contribute this?

For anyone waiting to fix this bug, I am happy to say that today I fixed this confusing behaviour in<EMAIL_ADDRESS>via the custom remark plugin written by me.
After receiving feedback from my community I want to contribute to Docusaurus too via a generic remark plugin that we could use in both frameworks Docusaurus & Nextra.
Stay tuned!
Here you can see a test with snapshot result
https://github.com/shuding/nextra/blob/main/packages/nextra/__test__/compile.test.ts#L83-L123

For anyone waiting to fix this bug, I am happy to say that today I fixed this confusing behaviour in<EMAIL_ADDRESS>via the custom remark plugin written by me.
After receiving feedback from my community I want to contribute to Docusaurus too via a generic remark plugin that we could use in both frameworks Docusaurus & Nextra.
Stay tuned!
Here you can see a test with snapshot result
https://github.com/shuding/nextra/blob/main/packages/nextra/__test__/compile.test.ts#L83-L123

Wonderful. I needed the target file combining the partials to show the right sidebar. Because of this bug, I have decided to take a somewhat circuitous route of adding the ## headers in the target file and then including the partial below it, for several such subsections. Your fix, when it arrives, will be godsend. Thanks!

Any news on this subject?

Any news on this subject?

Seems like we are waiting for @dimaMachina to create a remark plugin with his fix.

Any news on this subject?

Seems like we are waiting for @dimaMachina to create a remark plugin with his fix.

Yes! Sorry, currently I am busy with Nextra 3 release and future speak in Amsterdam on 8 November, I hope to do it next month ✌

I think we just ran into this as well. We basically wanted to have a component that renders a small label next to a heading to note if the thing being discussed is a beta item or not. While the component works flawlessly, the TOC does not render the heading. As a workaround, for now is there a way to manually create a TOC for a given MD doc?

I think we just ran into this as well. We basically wanted to have a component that renders a small label next to a heading to note if the thing being discussed is a beta item or not. While the component works flawlessly, the TOC does not render the heading. As a workaround, for now is there a way to manually create a TOC for a given MD doc?

This is how I did it. Quite sure there are better ways. I split the Markdown document I wanted to import into multiple MDX files. Each MDX file contains only the content from a specific section of the Markdown doc. So in the below, my MD doc had sections like Description, Parameters and Returns in one doc. After splitting it and saving into multiple files, each beginning with the underscore character, I imported them into another MDX doc like this. This way, Docusaurus displayed all the section headers, like it would for any normal MD doc.
import Description from "/path/to/_partials/_mydoc-description.mdx";

<Description />

## Parameters

import Params from "/path/to/_partials/_mydoc_-parameters.mdx";

<Params />

## Returns

import Returns from "/path/to/_partials/_mydoc_-returns.mdx";

<Returns />

We've done it like this
import Introduction, {
    toc as IntroductionToc,
} from "../shared/introduction.mdx";
import IntroductionContent, {toc as IntroductionContentToc} from "./.introduction_content.mdx";

export const toc = [...IntroductionContentToc, ...IntroductionToc]

<IntroductionContent />

<Introduction />

But then you can't mix it with other headers, like this
...

export const toc = [...IntroductionContentToc, ...IntroductionToc]

<IntroductionContent />

## Other header <---- WONT WORK PROPERLY

<Introduction />

I submitted a PR, that I'll be willing to work on, but in the meantime, until it is accepted, I made a quick drop in replacement remark plugin that fixes this behaviour in Docusaurus v2: @akopyl/docusaurus-toc-patcher.
It implements the logic from https://github.com/shuding/nextra/pull/2199 in Docusaurus v2.

This has been fixed (main/canary) as part of https://github.com/facebook/docusaurus/pull/9684, and will be released in Docusaurus v3.2
Thanks for the inspiration @dimaMachina and the initial port @anatolykopyl 🤗

Nice feature, do you plan to also support headings from custom JSX/TSX components to appear in ToC ? I have a React component that reads a JSON file and create headings and paragraphs based on it (the JSON file is loaded as a module but I guess it means the ToC should be generated dynamically at runtime and not at compile time?)

@jbltx we only support importing other MDX files atm
However, it could be technically possible to also support React imported components, and try to get the compiler to output something looking like this:
import Partial,
  {toc as __tocPartial} from "_partial.mdx"
import MyComponent from "MyComponent"

# Doc

## Doc heading

<Partial/>

<MyComponent/>

export const toc = [
  {
    "value": "Doc heading",
    "id": "doc-heading",
    "level": 2
  },
  ...__tocPartial,
  ...MyComponent?.toc?.()
]

Note that in any case, it would be your responsibility to implement the toc function attribute:
const MyComponent = () =>
Hello

MyComponent.toc = () => {
  return [{id: "hello",value: "Hello",level: 2}];
};

Would that be a helpful addition, or is this too limited?

Would that be a helpful addition, or is this too limited?

Thank you for the suggestion @slorber, I think your example is enough for my use case indeed! 👍

I don't know if I'm doing something wrong, but this is still not working for me, even after the fix:
_release.mdx:
## Release {props.release}

releases.mdx:
import Release from "./_release.mdx"

# Releases

## Top heading

{["v1", "v2", "v3"].map((release) => <Release release={release} />)}

And the result:

@felipecrs this is unlikely we will ever support this. The TOC is computed statically at MDX compilation time. We are not running the JS to see what the output is and if it contains any heading. Hence we don't support such loop, nor using props inside partial headings.
If you want that, you'd have to use the TOC function form described just above, a possible enhancement that we haven't implemented yet.

@slorber I see.
Implementing my own toc function is 100% acceptable for my use case, I would appreciate this capability.

Ops, sorry, did you mean that I could already implement my toc function?
I tried it with:
import Release from "./_release.mdx"

# Releases

## Top heading

{["v1", "v2", "v3"].map((release) => <Release release={release} />)}

export const toc = () => ["v1", "v2", "v3"].map((release) => ({
  "value": `Release ${release}`,
  "id": `release-${release}`,
  "level": 2
}))

And then the toc disappeared entirely.

@felipecrs we don't support a toc function yet, only a toc array export.
You should rather do that instead of a loop
import ReleaseV1 from "./_releaseV1.mdx"
import ReleaseV2 from "./_releaseV2.mdx"
import ReleaseV3 from "./_releaseV3.mdx"

# Releases

## Top heading

<ReleaseV1/>

<ReleaseV2/>

<ReleaseV3/>

Note, we don't support "dynamic headings" such as ## Release {props.version}, so you will need to provide a TOC export if you want dynamic headings (you can provide the toc export either on the root doc or the partial). There's also a non-implemented proposal to solve that problem that you can track here: https://github.com/facebook/docusaurus/pull/9773

Great. Thank you, I'll watch the pull request, because my data is very dynamic so I can't define them statically.


include integration config file

is there a way to include GitHub integration config file via secretref?
Description: https://backstage.io/docs/integrations/github/github-apps#including-in-integrations-config
seems include function is only possible with configMap - https://github.com/backstage/charts/tree/main/charts/backstage#pass-extra-configuration-files
thank you!

Hi @phac008 , have you tried using secrets for environment variables?

Hi ChrisJBurns,
yes, secret variables work.
my intention was, that it would be more backstage document aligned approach, when using integration file: https://backstage.io/docs/integrations/github/github-apps/#using-the-cli-public-github-only

I think the reason why we probably wouldn't offer it as part of our Chart is because it seems pretty much a Github only feature where you provide a file as a reference, whereas this Chart has to somewhat remain generic and unspecific around its features, otherwise we'd get into the scenario whereby we try to support everything which becomes almost impossible to do.
There may be a feature we could offer for creating files from a secret that may be valuable which seems to cover off your use case and keeps it somewhat generic across the board, but am not sure how often people would need to create files from secrets.
@backstage/helm-charts  Thoughts?

hi!
understand your thoughts - since adding secrets as environment variables work as expected, this will be ok for me.


fix(cdk,core): scrollbar behaviour inside iframe

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Refactoring
[ ] Build or CI related changes
[ ] Tests related changes
[ ] Documentation content changes

What is the current behavior?
Closes #5027
What is the new behavior?

@waterplea yes


[Enum Request] 5637 "FA G/L Posting Buffer" Field "FA Allocation Type" from Option to Enum

Enum Request #17109 would cause overflow if it isn't implemented in Table 5637 "FA G/L Posting Buffer". The overflow would occur in Codeunit 5601 "FA Insert G/L Account" on line FAGLPostBuf."FA Allocation Type" := "Allocation Type";.

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.


fix: cp bazelrc envoy-filter-build

Signed-off-by: Tarun Sharma<EMAIL_ADDRESS>
Commit Message: cp bazelrc in build dir for envoy_filter_example build
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]  https://github.com/envoyproxy/envoy/issues/20013
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

ohh @keith havent looked at that line but its that what yanaslov wanted in this issue https://github.com/envoyproxy/envoy/issues/20013

Hrm even the link in the issue had this line of code, is there a specific issue we can debug with to see if that's maybe not working?

/retest to confirm this wasn't a temporal issue

Given that we're already copying that file, is there any reason to keep this PR open?

/wait-any


Ctrl-Space is not caught

monaco-editor version: 0.19.3
Browser: Google Chrome Version 80.0.3987.149 (Official Build) (64-bit)
OS: MacOS Catalina 10.15.4
Playground code that reproduces the issue:
I am trying to override monaco default behaviour when pressing Ctrl-Space (the final intetntion is to make custom suggestions in special cases) but it doesn't work. The code:
const editor = monaco.editor.create(document.getElementById("container"), {
	value: "function hello() {alert('Hello world!');}",
	language: "javascript"
});

editor.addCommand(monaco.KeyMod.chord(monaco.KeyCode.Ctrl, monaco.KeyCode.Space), () => alert("Gotcha"))

And this code works (when pressing Space + S):
const editor = monaco.editor.create(document.getElementById("container"), {
	value: "function hello() {alert('Hello world!');}",
	language: "javascript"
});

editor.addCommand(monaco.KeyMod.chord(monaco.KeyCode.KEY_S, monaco.KeyCode.Space), () => alert("Gotcha"))

So Ctrl doesn't react at all. Is it ok?

Does this work for you? The keybindings work by combining a key modifier with an actual key using a bitwise or | as those are essentially bitmasks. What you registered was a chord i.e. a keybinding comprised of two separate key strokes (e.g. Cmd-K, Cmd-I for show hover). I don't think the first part of a chord can be just a modifier which is why your first example doesn't work. Your second example works because it is a chord comprised of first typing s followed by typing Space.
const editor = monaco.editor.create(document.getElementById("container"), {
	value: "function hello() {alert('Hello world!');}",
	language: "javascript"
});

editor.addCommand(monaco.KeyMod.WinCtrl | monaco.KeyCode.Space, () => alert("Gotcha"))

Note: I used the WinCtrl modifier because you're on macOS and that's the Ctrl key there (^)

Does this work for you? The keybindings work by combining a key modifier with an actual key using a bitwise or | as those are essentially bitmasks. What you registered was a chord i.e. a keybinding comprised of two separate key strokes (e.g. Cmd-K, Cmd-I for show hover). I don't think the first part of a chord can be just a modifier which is why your first example doesn't work. Your second example works because it is a chord comprised of first typing s followed by typing Space.
const editor = monaco.editor.create(document.getElementById("container"), {
	value: "function hello() {alert('Hello world!');}",
	language: "javascript"
});

editor.addCommand(monaco.KeyMod.WinCtrl | monaco.KeyCode.Space, () => alert("Gotcha"))

Note: I used the WinCtrl modifier because you're on macOS and that's the Ctrl key there (^)

Yep, WinCtrl did the trick. Thank you!


Links are not opened properly

Whenever I attempt to open links in parenthesis in web browser, the last bracket is included in the url, so the links appear broken. Fot instance, if I click on the url part of linked text "(www.link.com)", it is opened as "www.link.com)". I use rtv in Termite terminal and open links in Firefox browser.

Hi jrlil.  If it's your mouse, that behavior is defined by your terminal and not rtv.

I was talking about links inside comments that cannot be opened with keyboard. But you're probably right, it's a terminal issue. Thanks!


Reduce invest pool composition width on small/medium screens (Closes #1773)

Description
Please include a summary of the change and if relevant which issue is fixed. Please also include relevant motivation and context.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Dependency changes
[ ] Code refactor / cleanup
[ ] Documentation or wording changes
[ ] Other

How should this be tested?
Please provide instructions so we can test. Please also list any relevant details for your test configuration.

[ ] Test A
[ ] Test B

Visual context
Please provide any relevant visual context for UI changes or additions. This could be static screenshots or a loom screencast.
Checklist:

[ ] I have performed a self-review of my own code
[ ] I have requested at least 2 reviews (If the PR is significant enough, use best judgement here)
[ ] I have commented my code where relevant, particularly in hard-to-understand areas
[ ] If package-lock.json has changes, it was intentional.
[ ] The base of this PR is master if hotfix, develop if not

Hey Anastas, thanks again for your help here. In the future please describe your changes in the PR description and fill out the sections as best as possible. Also by linking to the related issue in the description it will link it properly and we can see that the issue can be closed.


feat: add grpc mux transport

Signed-off-by: Jim Ma<EMAIL_ADDRESS>
Description

Related Issue

Motivation and Context

Screenshots (if appropriate)
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation Update (if none of the other choices apply)

Checklist

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.

Codecov Report

Merging #1602 (a0ab02c) into main (7cf8fe1) will decrease coverage by 0.43%.
The diff coverage is 16.32%.

@@            Coverage Diff             @@
##             main    #1602      +/-   ##
==========================================
- Coverage   42.45%   42.01%   -0.44%
==========================================
  Files         120      124       +4
  Lines       11313    11440     +127
==========================================
+ Hits         4803     4807       +4
- Misses       6004     6124     +120
- Partials      506      509       +3

Flag
Coverage Δ

Object-compatibility-e2etests
?

e2etests
?

unittests
42.01% <16.32%> (-0.44%)
:arrow_down:

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


Swiper Thumbs Gallery Loop - making issue for thumbs & onSwiper

Hello,
<Swiper loop={true}  spaceBetween={10} autoplay={{ delay: 3000 }} rewind={true} thumbs={{ swiper: thumbsSwiper }} modules={[Autoplay, FreeMode, Thumbs]} className="mySwiper2" >
     <SwiperSlide>...</SwiperSlide>
</Swiper>

<Swiper loop={true} slidesPerView={3} spaceBetween={25} freeMode={true} watchSlidesProgress={true} modules={[ Autoplay, FreeMode, Navigation, Thumbs ]} className="mySwiper" autoplay={{ delay: 3000 }} rewind={true} >
    <SwiperSlide>...</SwiperSlide>
</Swiper>

then in my Nextjs Web App, it's following the below error.

please help me

This is because thumbsSwiper has not been initialized yet.
Try this:
thumbs={thumbsSwiper ? { swiper: thumbsSwiper } : undefined}

@aso1datov  == Thanks, your solution is working now...
I've one more thing to ask when an Image is active on both the sliders, then in the Thumbs Slider (2nd slider) I want to show some Icon on the Image for one which one is active/selected, can you able to help me how it's possible?

Try this:
.swiper-slide-thumb-active img  {
    /* your styles */
}

as I am using in Next.js, so that'll be in global CSS, right?

@aso1datov  - I tried but it's not working...

Check if your styles are overwritten by inline css

NO, I am not overriding any CSS Codes for <Swiper> as well as for <SwiperSlide>
in your case, as in .thumbnails for CSS, inside of .thumbnais {} you're writing global, so that's with CSS3 or with SCSS/SASS?

It's css-modules feature

@aso1datov  --- the CSS code you wrote above, I tried the same here in my local, but it's not working

@aso1datov ---- I am using a thumb swiper slider, my requirement is I have 30 images and I click the 3rd Image and the 3rd Image has to display without sliding other Images. I am stuck with an issue can you Help us?

Swiper v9 comes with fully reworked and now different loop functionality. If you have similar issues in Swiper 9, open a new issue with a CodeSandbox showing the issue.


Use updated scenic gem for db view migrations

We are having a lot of trouble with ordering using hand-written queries
migrated via structure.sql. The percentile view migrations are also
failing on production on RDS, which I have not been able to reproduce  I
suspect this may be down to encoding.
We tried scenic before in order to try and deal with the ordering
problem. Unfortunately, the version we installed had a bug. That has
been fixed.
I am changing back to it in an effort to better manage the ordering
problem and to see if it solves the RDS production migtation issue.

:ship:


POWERUPS!

Crush through obstacles
Slow down time?
Jump higher/lower grav
Is Growing the box advantageous?

Turning in to "epic"


♻ ECDSA fixes and optimizations

Description

The empty signature edge case has been fixed in https://github.com/Vectorized/solady/pull/536.
Added note on usage of ecrecover precompile 0x1.

Checklist
Ensure you completed all of the steps below before submitting your pull request:

[x] Ran forge fmt?
[x] Ran forge snapshot?
[x] Ran forge test?

Pull requests with an incomplete checklist will be thrown out.

LGTM 🎊


Rename remote option to remote_options

:thumbsup: Looks pretty straightforward.  So why the change to remote_options?  Just semantics?

Rails already seems to have an opinion on what data-remote is supposed to do, even if set on an input and not the form itself.


Document how per-room profiles work

Fixes https://github.com/matrix-org/matrix-doc/issues/545
This PR documents existing behaviour and does not attempt to improve or change the situation.
This is another attempt at https://github.com/matrix-org/matrix-doc/pull/1302, however with the controversial parts removed.

Fair enough. I'll close this (again) and shove it through the full proposal process to work out that detail.
(I also didn't have high hopes of this making it in, even with the parts removed)


Could we use sleep in the http/redis trigger handler?

Hi, Could we use sleep in the http/redis trigger handler? I see that we don't use async in the rust sdk, so if we use the std::sleep, shall it block the underlying tokio thread, rather merely the tokio task?

Wasm modules themselves do not yet support async calls (it is planned!), so everthing within a Spin app is synchronous. std::thread::sleep does work.


Fix for parallel run queries

Description
clearing the timeout of the prev query so that new one runs
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass, including unit test, integration test and doctest

[ ] New functionality has been documented.

[ ] New functionality has javadoc added
[ ] New functionality has user manual doc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Merged here: https://github.com/opensearch-project/dashboards-query-workbench/pull/140