Generate static build that can be deployed on Urbit

What is the purpose of the change
Adds scripts to generate static build that can be deployed on Urbit
Brief Changelog

Adds BASEPATH env for setting basePath in next.config.js

This is required as Urbit apps are deployed under /apps URL subpath
Also prefixed all image assets URL with BASEPATH env

Adds ENABLE_FEATURES env flag for overriding LaunchDarkly feature flags concentratedLiquidity and tokenInfo

This is required to show individual asset details page and hidden pools in the app

Adds COINGECKO_URL env for overriding default API URL https://coingecko.osmosis.zone/

This is required as only setting COINGECKO_API_KEY env was not working

Adds URBIT_DEPLOYMENT env flag to use lowercase paths for routing

This is required as uppercase routes and filenames are not supported in Urbit deployments

Adds changes for generating static build

Yarn script build:static is added to generate a static build
Some changes like disabling ISR is done based on env STATIC_EXPORT
Adds build-urbit.sh script to sanitize filenames with uppercase letters in the static build output

Dynamic path chunk files like [id]-eb2a5a7b0938263e.js are also sanitized as square brackets are not supported in Urbit

Testing and Verifying

This change has been tested locally by rebuilding the website and verified content and links are expected
App has been tested after deploying to a fake ship

Documentation and Release Note
Does this pull request introduce a new feature or user-facing behavior changes? no
How is the feature or change documented? not applicable

Going to close as stale, can reopen


Add some tweaks to mouse handling

Changes:

Fix dragging
Fix edge-case where an int would get sent to python
Added basic touch support (no long-press right-clicks)
Added a fullscreen button (fixes #106)

These changes are cool!
It looks like these are a few independent changes here:

Add support for fullscreen
Add support for touch
Fix int handling

Would it be possible to break these up into separate PRs so we can get them reviewed and merged in faster?

Sure, will do.


Update "circuits cbinds" code to support msgpack format

### Tasks
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/2011

Issue https://github.com/AztecProtocol/aztec3-circuits/issues/244 seems related.

Blocked by https://github.com/AztecProtocol/aztec-packages/pull/897
Or at least it probably makes sense to wait to start this ticket until this ^ PR is merged.

Sorry, I missed this one. Let's say blocked by #1533. Although ideally I'll do this one together.

Created a sub-task for the calls to private kernel circuit iteration. Other sub-tasks will have to be created to for other circuits or other cbind routines.

Not relevant anymore since circuits were migrated to Noir.


After a window with focus is minimized, yabai still reports that the window has focus.

You can easily reproduce this issue using the following script
# Get the current window's ID and has-focus attribute
window_info=$(yabai -m query --windows --window)
window_id=$(echo "$window_info" | jq '.id')
window_focus=$(echo "$window_info" | jq '."has-focus"')

# Print the window's ID and has-focus attribute
echo "Window ID: $window_id"
echo "Has Focus: $window_focus"

# Minimize the window using the yabai command
yabai -m window "$window_id" --minimize

# Wait for 1.5 seconds
sleep 1.5

# Query the window's has-focus attribute
window_focus_after=$(yabai -m query --windows --window "$window_id" | jq '."has-focus"')

# Print the window's has-focus attribute after minimizing
echo "Has Focus After Minimize: $window_focus_after"

❯ nix-shell -p jq

[nix-shell:~]$ # Get the current window's ID and has-focus attribute
window_info=$(yabai -m query --windows --window)
window_id=$(echo "$window_info" | jq '.id')
window_focus=$(echo "$window_info" | jq '."has-focus"')

# Print the window's ID and has-focus attribute
echo "Window ID: $window_id"
echo "Has Focus: $window_focus"

# Minimize the window using the yabai command
yabai -m window "$window_id" --minimize

# Wait for 1.5 seconds
sleep 1.5

# Query the window's has-focus attribute
window_focus_after=$(yabai -m query --windows --window "$window_id" | jq '."has-focus"')

# Print the window's has-focus attribute after minimizing
echo "Has Focus After Minimize: $window_focus_after"
Window ID: 979
Has Focus: true
Has Focus After Minimize: true

[nix-shell:~]$

yabai caches the id of the active window, and the cache is only updated when macOS reports that a new window has become the key window. I guess if you minimize the only available window, macOS focuses the "Finder desktop window" and we need to catch that somehow.

It seems that this is also one of the quirks of macos.
If yabai has nothing to do here, then this issue can be closed


Add ability to attach vispy Filter objects to layer visual

🚀 Feature
I think it would be nice if we allowed users to attach vispy shader filters to layer visuals as a way to enable more customized rendering.
Some examples of things one can do with filters filters:

wireframe for the mesh visual: https://github.com/napari/napari/issues/2970
clipping planes (implemented by @brisvag ): https://github.com/vispy/vispy/blob/main/examples/scene/clipping_planes.py
confine rendering to other shapes (e.g., sphere)
discard fragments that are "background" (i.e., if it is a background value, don't render it so it doesn't cause blending issues with other layers)

cc @maweigert
Motivation
It is nice to be able to experiment with custom shaders without having to go deep into the codebase. While allowing full shaders to be passed in might be a bit much, the vispy [BaseFilter](https://vispy.org/api/vispy.visuals.filters.base_filter.html) might be a nice compromise.
Also, see the twitter thread below about allowing users to pass in custom shaders.
https://twitter.com/martweig/status/1460643240588238849
Pitch
We add an evented list to the layer models that accepts vispy BaseFilter subclasses. When the list contents change (i.e., a filter is added/removed), an event is emitted and the visual updates accordingly.
Alternatives
We could register/coordinate the filters at the viewer level, but it seems like they should be restricted to the layer they are acting on.
Additional context

Definitely useful! Just for clarity:

clipping_planes are already hooked up in napari layers with experimental_clipping_planes
mesh filters will be super easy to implement after #3494 is merged (though you can already do it technically)

Clipping based on shapes is gonna be awesome!

Yes, this would be very useful! Ideally, a napari layer would be able to attach a given filter to its visual, which currently needs a slight detour (or is there a better way?)
layer = ...
filter = ...

viewer.window.qt_viewer.layer_to_visual[layer].attach(filter)

That's the right way, for now!
The only communication between napari layers and vispy visuals is through events, so as kevin suggested we need to add an evented model for filters :)


"In Replication Storage Account, select the Azure Storage account in which replicated data will be stored in Azure." needs more information

You say "In Replication Storage Account, select the Azure Storage account in which replicated data will be stored in Azure."
But you don't say what requirements the storage account has. Please add a link to the requirements for a storage account.
Should it be Public or Private endpoint?
Should it be Microsoft or Internet routing?
Does it need to secure transfer for REST API?
Blob Public access enabled?
 Otherwise you get an error "Error Message: Soft delete is enabled for the storage account 'bsnazuremigratestorage' provided..... Soft delete enabled storage account is not supported."
Thanks
Richard.

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

ID: 0f6cf488-07d3-1b2b-69f2-f04c7890bd55
Version Independent ID: fd658be4-17c5-19c7-b6c9-630090880c3c
Content: Migrate Hyper-V VMs to Azure with Azure Migrate Server Migration - Azure Migrate
Content Source: articles/migrate/tutorial-migrate-hyper-v.md
Service: azure-migrate
GitHub Login: @bsiva
Microsoft Alias: bsiva

@richard-artes Thank you for your feedback. We will review this with the content owner and update as appropriate.
@Vikram1988 FYI

Hi @richard-artes,
Thank you for bringing this to our attention.
The documentation has been updated and the updates are available at https://docs.microsoft.com/en-us/azure/migrate/migrate-support-matrix-hyper-v-migration#replication-storage-account-requirements.
Hence, closing this issue.
#please-close


[Device problem]: Tuya RB-SRAIN01 is recognized as water leak detector

Link
https://www.zigbee2mqtt.io/devices/RB-SRAIN01.html
Adapter version
2.13.6
What is missing or not working
The Tuya RB-SRAIN01 is recognized as water leak detector. It should expose rain and light intensity
Device exposes
Sorry, teher is no  datapoint zigbee2mqtt.[X].info.debugmessages

Fck, wrong adapter, sorry


[5.3.4] Segmentation fault when use hhvm artisan

ENV:
$ hhvm --version
HipHop VM 3.14.1 (rel)
Compiler: tags/HHVM-3.14.1-0-gd99b370804b7e0234ab794869d1ba1774c848e85
Repo schema: ac0c6851ba5643ce00ae67bbe67c50973efd65d6

$ php --version
PHP 7.0.8-2+deb.sury.org~xenial+1 (cli) ( NTS )
Copyright (c) 1997-2016 The PHP Group
Zend Engine v3.0.0, Copyright (c) 1998-2016 Zend Technologies
    with Zend OPcache v7.0.8-2+deb.sury.org~xenial+1, Copyright (c) 1999-2016, by Zend Technologies
    with blackfire v1.10.6, https://blackfire.io, by Blackfireio Inc.

$ vagrant box list
laravel/homestead (virtualbox, 0.5.0)

Problem:
Get segmentation vault when calling hhvm artisan. But it works with php artisan.
PHP Stacktrace:

#0  Composer\Autoload\includeFile() called at [/home/vagrant/aaa/vendor/composer/ClassLoader.php:302]
#1  Composer\Autoload\ClassLoader->loadClass() called at [/home/vagrant/aaa/vendor/laravel/framework/src/Illuminate/Queue/QueueServiceProvider.php:81]
#2  Closure$Illuminate\Queue\QueueServiceProvider::registerWorker() called at [/home/vagrant/aaa/vendor/laravel/framework/src/Illuminate/Container/Container.php:731]
#3  Illuminate\Container\Container->build() called at [/home/vagrant/aaa/vendor/laravel/framework/src/Illuminate/Container/Container.php:629]
#4  Illuminate\Container\Container->make() called at [/home/vagrant/aaa/vendor/laravel/framework/src/Illuminate/Foundation/Application.php:699]
#5  Illuminate\Foundation\Application->make() called at [/home/vagrant/aaa/vendor/laravel/framework/src/Illuminate/Container/Container.php:1182]
#6  Illuminate\Container\Container->offsetGet() called at [/home/vagrant/aaa/vendor/laravel/framework/src/Illuminate/Queue/QueueServiceProvider.php:93]
#7  Closure$Illuminate\Queue\QueueServiceProvider::registerWorkCommand() called at [/home/vagrant/aaa/vendor/laravel/framework/src/Illuminate/Container/Container.php:731]
#8  Illuminate\Container\Container->build() called at [/home/vagrant/aaa/vendor/laravel/framework/src/Illuminate/Container/Container.php:629]
#9  Illuminate\Container\Container->make() called at [/home/vagrant/aaa/vendor/laravel/framework/src/Illuminate/Foundation/Application.php:699]
#10 Illuminate\Foundation\Application->make() called at [/home/vagrant/aaa/vendor/laravel/framework/src/Illuminate/Console/Application.php:115]
#11 Illuminate\Console\Application->resolve() called at [/home/vagrant/aaa/vendor/laravel/framework/src/Illuminate/Console/Application.php:129]
#12 Illuminate\Console\Application->resolveCommands() called at [/home/vagrant/aaa/vendor/laravel/framework/src/Illuminate/Support/ServiceProvider.php:185]
#13 Closure$Illuminate\Support\ServiceProvider::commands()
#14 call_user_func_array() called at [/home/vagrant/aaa/vendor/laravel/framework/src/Illuminate/Events/Dispatcher.php:221]
#15 Illuminate\Events\Dispatcher->fire() called at [/home/vagrant/aaa/vendor/laravel/framework/src/Illuminate/Console/Application.php:46]
#16 Illuminate\Console\Application->__construct() called at [/home/vagrant/aaa/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php:279]
#17 Illuminate\Foundation\Console\Kernel->getArtisan() called at [/home/vagrant/aaa/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php:122]
#18 Illuminate\Foundation\Console\Kernel->handle() called at [/home/vagrant/aaa/artisan:36]

Note:

This happens on fresh install
If I comment Illuminate\Queue\QueueServiceProvider::class at config/app.php#158, It works as expected
Version 5.1.43 doesn't have this problem

Don't know if Laravel really supports hhvm officially because of the differences between it and PHP 5.6+. But I hope you get a solution.

Laravel 5.3 doesn't support hhvm. Its listed in the 5.3 upgrade guide

Yeh, we don't support HHVM. I personally deleted all the code that we had for HHVM workarounds.

A segfault is definitely an HHVM bug though, and will be unrelated to any changes within Laravel.

Wow. Talk about a purposeful regression!

Too bad :-1


DeviceCollector throws some exceptions away in tests that use it

Recently, when writing a bit of code for blueapi (https://github.com/DiamondLightSource/blueapi/pull/321/) we found that if we tried to test the Device Collector (as per https://github.com/bluesky/ophyd/pull/1151)
The tests in Callum's PR seem to fail for the original Device Collector if assert statements on the logs are present. This is odd behaviour and should be fixed.

Fixed by #97


fix: mark some peer dependencies as optional and remove some unnecessary peer dependencies

removed prosemirror-* from peerDependencies since @tiptap/core depends on @tiptap/pm which in turn depends on all the prosemirror-* packages.
marked optional peer dependencies in peerDependenciesMeta
Some of the @taiga-ui peer dependencies like @taiga-ui/core, @taiga-ui/kit, @taiga-ui/cdk, @taiga-ui/i18n and @taiga-ui/legacy are missing from peer dependencies but I don't know what version should be used. Unreleased v4?

Closes #1092

@hakimio please, add changes to v1.x


Arbitrary query variables

Hi, current version of library only passes variables from the route. This pull request is for changes that allow passing arbitrary variables to the query.  Haven't defined proper variable types, maybe someone with deeper typescript skills can have a crack at it, other than that should be pretty straight forward change

This is great, thank you so much for your contribution!
I've been thinking about this for a bit too, one of my thoughts is that this will run in a similar fashion to getInitialProps, in that it will run on both the client-side and server-side, which can cause a query to have different variables at runtime. In the case of our app most of the query variables we want are stored in a combination of pageProps and React context, it would be very cool if we could extract query variables out of those.
Will think a bit more about this over the course of the day, in the meantime could you add usage of this to the example project? Thanks again!

Added example to the docs.

I've thought about the API a bit more, and I'm not sure that adding a new config option is the best way to go because it would run on a the server and client. What do you think about merging the results of getServerSideProps or getClientSideProps into the query variables? I think it serves the same use-case but has a better distinction of where the code is running.

Yeah, that is a fair point. How about having separate functions for server and client side? Something like serverQueryVariables and clientQueryVariables. If needed results of getServerSideProps and getClientSideProps can be passed as arguments for the variable functions. I feel like merging those directly into query variables could lead to some unintended consequences. Passing them through dedicated functions will give more control over what we are querying.
On a side note, how do you test this package locally? Tried npm run build and then npm link, to bring it to my own project, but getting errors that can't resolve 'react'. Perhaps a short section in readme would be helpful for future collaborators.

Thanks for this PR, I do really need this feature. @rrdelaney Is this going to be merged soon?
I think current implementation can be improved to be more flexible.
I suggest modifying this:
  const variables = opts.serverSideQueryVariables
    ? opts.serverSideQueryVariables(ctx, serverSideProps)
    : {};
  const preloadedQuery = loadQuery(env, query, {
    ...ctx.query,
    ...variables,
  });

to this:
  const variables = opts.serverSideQueryVariables
    ? opts.serverSideQueryVariables(ctx, serverSideProps)
    : ctx.query;
  const preloadedQuery = loadQuery(env, query, variables);

(and the same for clientSideQueryVariables)
This is more flexible, and with serverSideQueryVariables = (ctx, serverSideProps) => {...ctx.query, ...someOtherVariables} it has the same effect of the first code.
The first code merges ctx.query into variables and developer has no control on it. But in second code, developer controls how to merge ctx.query into variables.
In my use case, I want to apply a transformation on ctx.query before passing it to variables. For example if we have {is_active: "on", page: 4} in ctx.query, I want to pass {is_active: true, first: 20, offset: 60} as GraphQL variables. I don't want page to appear in variables.

@mjnaderi the transform approach sounds good to me. Would happy happy to accept a PR with that implemented. I'm not sure if this one is completely updated to the client / server split.

Would you need to modify the variables based on the props? That's the only thing giving me a little hesitation here. If it was a pure function on the Next.js context that'd be a little simpler. IMO I don't see a reason to change based on props because your server can change the response instead. Any async work here is also going to slow the page down a lot.

@rrdelaney No I don't need to modify based on props. I just need to modify variables based on ctx.query in a synchronous function.

I like that a lot. When I was making the API I figured it should be stateless based on route and anything else passed as headers in the network config.

Sorry guys, I ended up writing my own relay integration for our project, but feel free to pick this one up from here.

This was implemented in 92d54f6ad5b5f871acdea5a38382ca9c32966e6f with the introduction of the variablesFromContext option.


very hard steps to get token stuff for onedrive..... ;(

hi there
can you please provide use tutorial for getting refresh token access token for OD correctly i tried many times it doesnt work ....please help

There is a very detailed version of token acquirement in the previous repo.
Please read this .
Also consider using the beetcb/ms-graph to require the tokens.

hi there
can you please provide use tutorial for getting refresh token access token for OD correctly i tried many times it doesnt work ....please help

Install Node.js on your computer
Run npx @beetcb/ms-graph-cli in the terminal or command line.
Follow the steps to get the token


RiccardoLincetto/issue6

Fixes #6
Added decorators for timing and logging, with debug level, functions called.
Added command-line arguments for controlling logging level.

Code is fine, but version number has divergent history. Solve that to merge.


Add Painles script execute API

Relates: https://github.com/elastic/elasticsearch/pull/29164
Documentation: https://www.elastic.co/guide/en/elasticsearch/painless/current/painless-execute-api.html
Add new API endpoint to allow the execution of an arbitrary painless script

Closing this as #3370 has been merged to 6.3


Support 'activatePrecompiles' as an option

See: https://github.com/ethereumjs/ethereumjs-vm/pull/65
Without this option, every testrpc instance behaves like a fresh private network, where no transactions were made with precompiled contracts.  I think this is the desired default behaviour.
With turning on the above option, this changes into a network which had transactions prior with precompiled contracts (i.e. it will be in a very similar state to homestead/morden for the contract developer).
The main difference is that the first contract calling these precompiled contract will incur additional fees and that can confuse developers (e.g. "why does my first call has a different fee than the second?")

Definitely looking for a feature like this. Only unsolved mystery is how/where to save the chain data. If we do it right, we can save it in the same was a geth, and be able to read from that data as well.

Oh, you only need to pass an option to the VM constructor: activatePrecompiles: true

For the record (chatted with @axic offline) I misunderstood the PR. This is a good feature, and should be set to true by default, likely without the option to make it false.

@tcoulter ping! This should go into the next release if possible

@kumavis does this needs to go into web3-provider-engine?

Probably does too.
FYI: Ping received. I'm on it. In the middle of a big refactor, which it
will be a part of.
On Tue, Jul 26, 2016 at 12:24 PM, Alex Beregszaszi<EMAIL_ADDRESS>
wrote:

@kumavis https://github.com/kumavis does this needs to go into
web3-provider-engine?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ethereumjs/testrpc/issues/88#issuecomment-235376891,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFp1Y9-XAwPe-4LowL43TzdLvUmlzNgks5qZl7dgaJpZM4Ijf9T
.

This has been added to the latest TestRPC: https://github.com/ethereumjs/testrpc/blob/master/lib/blockchain_double.js#L24
Thanks!


Resubmit: Generate differentiated error codes for buffer oob checking

This allows the GPU-AV layer to differentiate between errors with
uniform buffers versus storage buffers and map these to the relevant
VUIDs.
This is a resubmit of a previously reverted commit. The revert was
done as someone erroneously attempted to build the latest validation
layers with a TOT spirv-tools. The validation layers must be built with
their known-good glslang and its known-good spirv-tools and spirv-headers.

Is the validation layer change ready to go or is this going to break them for an unknown amount of time? If the validation layer change will land soon after this then we can do a combined roll, otherwise this will cause issues with our roll process.

@dj2 As soon as we incorporate a version of spirv-tools that contains this commit into the known-good of glslang, VVL has a branch that is ready to be merged that is compatible with this commit.
Of course, there is some process around promoting the spirv-tools known-good in glslang: both the dxc folks and LunarG have some additional testing to allow spirv-tools to be promoted to stable and thus eligible for glslang known-good.
In the past I have made an effort to avoid this kind of dependency with VVL. It usually involves adding additional control in the spirv-opt interface that eventually has to be ripped out. I thought I could avoid that here since (I thought) we could control the version of spirv-tools that was used to build VVL. I can probably still add the additional interface control if it is necessary to allow this commit to move forward.
At some point I would like to understand your need to build VVL with a version of spirv-tools other than that blessed by the VVL team.

Both internally and Chromium build everything at tip-of-tree. The code is imported into the repos periodically which build everything at tip-of-tree. The break basically makes the roll fail for some amount of time. Having the roll fail for a day or so, isn't too bad, if it's on the order of weeks it can become problematic as we can no-longer get new SPIRV-Tools, which can have knock on effects as other APIs change.
For Chromium, this means we stop rolling SPIRV-Tools, GLSLang, SPIRV-Cross, Vulkan-ValidationLayers, Vulkan-Loader, Vulkan-Headers and Vulkan-Tools until the breakage is fixed as they all roll into our vulkan-deps repo before rolling into Chromium.

This what I will do for the moment: I will pretest spirv-tools to make sure TOT can be made glslang's known-good. Once that is certified, I will request this PR be merged. I will then immediately make it glslang's known-good and request my VVL developer to pull in his branch.
This will have to be done today because my VVL developer is going on vacation Friday and Monday. So please try to keep an eye out for my merge request.
If for some reason we can't get this done today, I will add logic to the interface in this PR so the merge can be done without disruption to the Google nightlies.

Sounds good to me. Thanks a lot for working through this.

@dj2 Please merge.


Doom configuration reset

Describe the Issue (If applicable)
After tweaking with the controls of Doom, I accidentally hit "restore defaults" and this reset all the controls to the stock gzdoom default, making it impossible to reconfigure it back to work with my device.
The only solution I found was to reflash the whole system
How can the issue be reproduced? (If applicable)
Open any Doom wad and then reset the controls on the menu.
What device are you using?
RG351v
What version of ArkOS are you on?
ArkOS 2.0 (06222023)

Thanks for reporting this.  I'll include a default settings for gzdoom and lzdoom with the next update.

This has been accommodated with today's update.


Why docker-compose intentionally kept postgres volumes as default ?

I was working on exporting the data from postgres but my existing vm doesn't had that much space in it. so i tried attaching additional volume to postgres volume but the data folder there was not mounted to any specific space. so any change in docker-compose.yml would result in destroying of the whole database. My question is : Is this configuration intentionally kept ?
Also deleting the form data doesn't do anything and keeps saving the data on server. Why there is no option for deleting the data ?

Support issues should go to https://forum.getodk.org/c/support/6.


Add converter typehints

Adds proper typehinting to converters by assigning the names to the converter return values during type checking.
I've also fixed the message for _snowflake_from_regex where it raised an error with the str class interpolated instead of the argument in 8264fda1bbb28c91b811423684e58472aca1de55
closes: #1730

Some places re-annotate the argument to avoid warnings from type checkers. This is no longer necessary. Ideally, all these should be removed.
For example:
https://github.com/python-discord/bot/blob/main/bot/exts/moderation/modpings.py#L90

Do you think you can go through the code base and remove these? Otherwise, this PR looks good to me.

Some places re-annotate the argument to avoid warnings from type checkers. This is no longer necessary. Ideally, all these should be removed.
For example:
https://github.com/python-discord/bot/blob/main/bot/exts/moderation/modpings.py#L90

Do you think you can go through the code base and remove these? Otherwise, this PR looks good to me.

did a regex search with ^ *\w+: [\.\[\]\w]+$, removed the two it found in the last commit but it seems a bit low so let me know if it missed anything obvious

Noticed TagContentConverter was still around even though tags have been file based for a while now so I removed it in 37804ce14c4aeb322ef772b14e7fe55658f80ebf


Add type annotations to generator.py and reformate it by black

Fixes #311

I have checked that the generator still works fine at least for Python container.

[test]

Thanks, LGTM.


Add DOMText::replaceWholeText()

Add the replaceWholeText() method FluentDOM\Text and FluentDOM\CdataSection.
https://www.w3.org/TR/DOM-Level-3-Core/core.html#Text3-replaceWholeText

Implemented. https://github.com/FluentDOM/FluentDOM/commit/004038380f042771544a9ba739bcaad75d34cdea


Cannot connect to server ui or 8080 for config

So I created the VPN server as private server with no public IP. but for the VPN tunnel at UDP port 51820 I created a Global accelerator so I can successfully connect to the VPN.
However in the new version of Wag v7.3.2 I facing an issue where after connecting to the VPN tunnel I cannot access the Wag UI. Both the ports 8080 and 9000(UI) are opened in the Security group to VPC's CIDR range.
So technically, it should be accessible which is also possible in older version of wag.
Everything else in the VPC is accessed fine but not the VPN server itself.
Can anyone please help me with this?
Here's the config
{
    "Proxied": false,
    "NAT": null,
    "HelpMail": "<my-email>",
    "Lockout": 5,
    "ExternalAddress": "<my-external-domain>",
    "MaxSessionLifetimeMinutes": 1440,
    "SessionInactivityTimeoutMinutes": 60,
    "ManagementUI": {
        "ListenAddress": ":9000",
        "Enabled": true
    },
    "Webserver": {
        "Public": {
            "ListenAddress": ":8080"
        },
        "Tunnel": {
            "Port": "80"
        }
    },
    "Authenticators": {
        "Issuer": "duve",
        "Methods": [
            "totp"
        ],
        "DomainURL": "",
        "OIDC": {
            "IssuerURL": "",
            "ClientSecret": "",
            "ClientID": ""
        },
        "PAM": {
            "ServiceName": ""
        }
    },
    "Wireguard": {
        "DevName": "wg0",
        "ListenPort": 51820,
        "PrivateKey": "<My-private-key>",
        "Address": "<IP_ADDRESS>/24",
        "MTU": 1420
    },
    "DatabaseLocation": "devices.db",
    "Acls": {
        "Groups": {
            "group:admin": [
                "user"
            ]
        },
        "Policies": {
            "group:admin": {
                "Mfa": [
                    "<IP_ADDRESS>/16"
                ],
                "Allow": [
                    "<IP_ADDRESS>/16"
                ]
            }
        }
    }
}

Sorry, this seems like a support request rather than a feature or bug report.
I am not currently able to provide free support as it is often quite time intensive.
Hopefully you can sort this out!

If you do find this is a bug in wag feel free to reopen it.

I believe this is a bug as I was able to successfully connect in the old version but in the new version I cannot with the same config.

I can see from your config this isn't a bug. You don't have ExposePorts defined,  so iptables is blocking traffic to the management UI.


Feature idea: Infinite zoom

Would be great to be able to zoom out more to get an overview

This is totally doable but I think I might want to rework the input system before I attempt it. A minimap might be cool, too.


I have developed code for PayPalPre-approval, but giving error

var PayPalFuture =require('react-native').NativeModules.PayPalFuture;
PayPalFuture.futurePaymentRequest({
clientId: 'valid client id',
environment: PayPalFuture.SANDBOX,
merchantName:"Customer1",
merchantPrivacyPolicyUri:"https://www.google.com/",
merchantUserAgreementUri:"https://www.google.com/"
},{null},{null}).then(function (authcode)
Could you please help me to resolve this issue, please find the attached screenshot.

I haven't used this for a while, so I don't know what the project status is, but I suggest you take a look at this instead: https://github.com/MattFoley/react-native-paypal


Re-submission of Application for Candymint tool

Project Abstract

Candy Mint is a tool built for Asset Hub for building scalable nft mint dapps built with the use polkadot-js/api and react-js similar to ethereum based mint dapps but by using Candy Mint builders won't have to write smart contract

Grant level

[x] Level 1:  Up to $10,000, 2 approvals
[ ] Level 2:  Up to $30,000, 3 approvals
[ ] Level 3:  Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

[x] The application template has been copied and aptly renamed (project_name.md).
[x] I have read the application guidelines.
[x] Payment details have been provided (bank details via email or Polkadot (USDC & USDT) or BTC address in the application).
[x] The software delivered for this grant will be released under an open-source license specified in the application.
[x] The initial PR contains only one commit (squash and force-push if needed).
[x] The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
[ ] I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @_______:matrix.org (change the homeserver if you use a different one)

@Noc2 @takahser Re-submission of https://github.com/w3f/Grants-Program/pull/2050 updated with all new commits previous pull request had some issue with fetching newly made commits

Thanks


Document new prerequisites and integrate non-Make steps into Makefiles

Now that (syntactic, non-sexp) SQL is being offered as a first-class source language, the prerequisites and build are more complicated and not all of that is seamless yet.
Because of a needed change to the ocaml build, ocamlfind is now a pre-requisite.  This might or might not matter in practice, because my impression is that the normal process of installing the existing pre-reqs via opam will get you a copy of ocamlfind.
A Java pre-req is currently documented as optional unless you are using the Java runtime or the query runner.   In fact, it is required if you are using SQL as a source language.  Furthermore:
The 'make' in sqlParser will fail unless an ant script is run first.  This is not explicit in the Makefile.  And it means that ant is now a prerequisite.
The qcert binary will not work for -source sql unless a second ant script is run to package up Java code and move it to 'bin'.
Continuing to document the Java pre-req as optional is becoming strained because the various Makefiles really need to invoke the Java compiler and invoke ant if the result is not to be inconvenient and puzzling.

In a discussion with @jeromesimeon we identified two courses of action with pros and cons.

Make Java (and ant) a hard pre-requisite and unify the build so that the sql parser is built along with qcert.

Pro: once the user satisfies the pre-reqs (once), the build is simpler and everything works.
Con: it seems a shame to require Java and ant when much of the system can be built and used without them

Document that Java and ant are needed for sql parsing (Java is already an optional pre-req for the query runner and the Java runtime).   Let the build of the sql parser be separate or only optionally integrated into the main makefile via a flag.

Pro: users who aren't interested in SQL have the same pre-reqs as before
Con: it complicates the build and could be confusing to users who just want to install the system and don't yet know exactly how they will use it.

@jeromesimeon said he would think about this some more and ask others.  I am waiting for guidance.

I'd like to move on this issue and, in order to do so without jumping the gun on the question that is outstanding to the group, I will divide the work into two parts.
Part 1 just integrates all the ant scripts into the sqlParser makefile so that the SQL support is built in a single step (preferably with accurate enough dependencies so that the getDependencies part only runs when dependencies change, since it requires network connectivity).   This still leaves the SQL support as optional, but avoids mistakes like forgetting to run the export step after a sqlParser build.
Once part 1 is complete, Java is still an optional dependency but you need it if you want sql.  Ant is an optional dependency and you need it only if you want sql.
Part 2 consists of (maybe) further integrating the sqlParser build into the main build and making Java and ant into hard dependencies.  It also includes documenting all the dependencies once the decision is made pro or con to do the final integration.
I will do part 1, after which I will transfer the issue to Jerome.   If he decides to leave the sqlParser build as a distinct step (consistent with how the Java runtime and the samples are handled), then his part just consists of updating the documentation to be more accurate about the dependencies.

Part 1 is complete.  At the same time, I also changed export.xml so that it leaves the server built in a local folder sqlParser/server as well as zipping it into bin.   That facilitates running the server locally for testing.
Part 2 will be up to Jerome.

Since I assigned this to Jerome it's obvious that he will be confused by the original title, which is historical.  So I will change it (and the description) to something more focused.

I'm not planning to do more work on this. The README is updated, and includes detailed instructions for Java requirements, and related configuration. The build process has been cleaned up. I'm considering this closed. Anyone objecting can reopen.


Remove nft ruleset files

What this PR does / why we need it:
Instead of loading nftable rules from files, that are
built in the release, create the table and basechains
in the handler code.
With the nat table and base chains created in handler, these
files are not required anymore and are removed in the 2nd commit.
This simplifies build process of downstream projects, that don't use bazel
build system, and need to ensure existence of the nft files.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

masquerade: Create nftables base chains in virt-handler

/cc @AlonaKaplan

Thanks @rhrazdil looks good. Please remove from draft.

@rhrazdil , I would not include a release-note here, because it is not a user facing change. Users are not suppose to notice this at all.
/retest

@EdDev That's correct. I've removed the note, thanks!


Convert xNetworking Documentation to use SharePointDsc model

See https://github.com/PowerShell/DscResources/issues/167

@tysonjhayes has completed this in PR #174


drivers: i2c: i2c_esp32: fix clock source search

Change array iteration loop to search the entire array instead of the array / 4.

This fixes the I2C clock selection issue on ESP32-S3.  However, it now exposes and issue where the periph_rtc_dig_clk8m_enable() and periph_rtc_dig_clk8m_get_freq() functions are missing from the build resulting in a link failure.
I commented out the SOC_I2C_SUPPORT_RTC switch case to make progress since I couldn't easily figure out how to integrate the implementation in 'modules/hal/espressif/components/esp_hw_support/clk_ctrl_os.c`.
static uint32_t i2c_get_src_clk_freq(i2c_clock_source_t clk_src)
{
	uint32_t periph_src_clk_hz = 0;

	switch (clk_src) {
// . . .
//#if SOC_I2C_SUPPORT_RTC
//	case I2C_CLK_SRC_RC_FAST:
//		periph_rtc_dig_clk8m_enable();                       <-- this is missing from the build
//		periph_src_clk_hz = periph_rtc_dig_clk8m_get_freq(); <-- this is missing from the build
//		break;
//#endif
// . . .

Ah, looks like you have a newer branch for this :/

These changes were incorporated into the HAL v5.1 changes, so closing this pull request.


className not being passed to  component

Steps to reproduce
Try to pass a className to a  component like: <Text h1 className='test-class'>Loading...</Text>.
Expected behaviour
test-class should be present on the element and it is not.
Environment / Context

Desktop
Windows 10 64 Bits
Opera 83.0.4254.27

Additional info
@nextui-org/react: 1.0.2-beta.3
react: 17.0.2

Hey @bruxo00 this issue was fixed and is pending to be released https://github.com/nextui-org/nextui/issues/199


Breaking Links

In "Cluster types in HDInsight" section, the hyperlinks on HDFS, YARN and MapReduce are not working.

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

ID: 056b150a-3e49-2a3c-e591-2b5c22733f4e
Version Independent ID: 85d52a2a-5144-86d4-bd9c-5c2ec349b588
Content: What are HDInsight and the Hadoop and Spark technology stack? - Azure
Content Source: articles/hdinsight/hadoop/apache-hadoop-introduction.md
Service: hdinsight
GitHub Login: @cjgronlund
Microsoft Alias: cgronlun

@manub22 Thank you for your feedback! We have assigned this issue to the author to investigate further and take the right course of action.

#in-progress

@jason-j-MSFT @cjgronlund
Maybe I'm just checking this too quickly, but the links in question haven't been fixed - they just loop back to themselves (nonexistent headers on the same page).

@dcbrown16 I think it is bit early, the fix will go out soon.


Innoplexus ADMET leaderboard submission

@amva13 This PR is for submitting new entries/ new model to the TDC ADMET Group Leaderboard.
Please find the details below as per guidelines provided here
A. A link to the codes for training the model and running the benchmarks.
https://github.com/Innoplexus-opensource/ics-admet-prediction-tdc/tree/main
B. Instructions for replicating your results running these codes.
https://github.com/Innoplexus-opensource/ics-admet-prediction-tdc/blob/main/README.md
C. Description of the hardware used for training the model.
A machine with Intel i9-13900 processor 62GB RAM and NVIDIA RTX A6000 GPU with 48GB VRAM was used for the model training experiments.
D. Link to paper to be included on the website
https://github.com/Innoplexus-opensource/ics-admet-prediction-tdc/tree/main/report/Innoplexus ADME-NN Model Evaluation on TDC Benchmark ADMET Group Binary Datasets.pdf
E. Paper authors and developers of the model.
Rohit Yadav, Divya Nair, Amit Agarwal
Innoplexus Consulting Services Pvt Ltd, a Partex company
F. The dictionary string output of running the TDC benchmark group evaluations.
"Innoplexus ABDNN-ADME" (New model):
{{'caco2_wang': [0.148, 0.007]}, {'bioavailability_ma': [0.955, 0.017]}, {'lipophilicity_astrazeneca': [0.227, 0.018]}, {'solubility_aqsoldb': [0.387, 0.035]}, {'hia_hou': [0.985, 0.029]}, {'pgp_broccatelli': [0.985, 0.006]}, {'bbb_martins': [0.978, 0.004]}, {'ppbr_az': [3.744, 0.152]}, {'vdss_lombardo': [0.715, 0.043]}, {'cyp2c9_veith': [0.958, 0.006]}, {'cyp2d6_veith': [0.936, 0.013]}, {'cyp3a4_veith': [0.975, 0.005]}, {'cyp2c9_substrate_carbonmangels': [0.913, 0.038]}, {'cyp2d6_substrate_carbonmangels': [0.983, 0.013]}, {'cyp3a4_substrate_carbonmangels': [0.975, 0.008]}, {'half_life_obach': [0.445, 0.078]}, {'clearance_hepatocyte_az': [0.789, 0.019]}, {'clearance_microsome_az': [0.783, 0.039]}, {'ld50_zhu': [0.21, 0.017]}, {'herg': [0.963, 0.013]}, {'ames': [0.983, 0.004]}, {'dili': [0.998, 0.002]}, {'herg': [0.966, 0.009]}}
Kindly review and merge this PR. Also earlier we submitted "Innoplexus ADME" (Old model). There were some benchmark rankings missing from the leaderboard, i will provide additional PR for that as well for correction.
@amva13 the below PR is for correcting old entries/ old models to the TDC ADMET Group Leaderboard.
A. A link to the codes for training the model and running the benchmarks.
https://github.com/Innoplexus-opensource/ics-therapeutics-data-commons/tree/main
B. Instructions for replicating your results running these codes.
https://github.com/Innoplexus-opensource/ics-therapeutics-data-commons/blob/main/README.md
C. Description of the hardware used for training the model.
A machine with Intel i9-13900 processor 62GB RAM and NVIDIA RTX A6000 GPU with 48GB VRAM was used for the model training experiments.
D. Link to paper to be included on the website
https://github.com/Innoplexus-opensource/ics-therapeutics-data-commons/blob/main/Innoplexus_ADME_Model_report.pdf
E. Paper authors and developers of the model.
Rohit Yadav^1, Divya Nair^1, Prajakta Mate^1, Rushikesh Chaudhari^1, Arpan Sheetal^1, Sudhir Mansukh^1, Amit Agarwal^1, Anand Muglikar^2
1.Innoplexus Consulting Services Pvt Ltd, a Partex company
2.Perpetualblock Technologies Private Limited, a Partex company
F. The dictionary string output of running the TDC benchmark group evaluations.
"Innoplexus ADME" (Old model):
{{'caco2_wang': [0.289, 0.005]}, {'lipophilicity_astrazeneca': [0.499, 0.003]}, {'solubility_aqsoldb': [0.771, 0.005]}, {'ppbr_az': [8.582, 0.036]}, {'vdss_lombardo': [0.707, 0.006]}, {'half_life_obach': [0.511, 0.000]}, {'clearance_hepatocyte_az': [0.457, 0.013]}, {'clearance_microsome_az': [0.620, 0.007]}, {'ld50_zhu': [0.588, 0.000]}}

@innoplexus merged. thank you for the contribution!

this submission was marked as fraudulent due manipulating the default data splits in your code. its removed


[error]Pole not balanced. Stopping after 50 failures

hi,I had trial again by again ,but failed all,my model is the big segway model in verp,
so ,is there anything i haven't do right?
Pole not balanced. Stopping after 50 failures

Hey @ayan1991,
I will check what might be your problem and how to solve in the next few days.
Cheers

V-REP PRO EDU,Version 3.3.2
OS:windows7 64bit
python :3.7.1

Did you try it with another vrep model? Like middle or normal?
I just ran the simulation with the big model and it worked like expected.
You could also try:

Update V-REP to 3.6.2
Try python2

No further reaction -> solved.


Clean up «Installer Kubernetes avec Minikube»

@remyleone I spotted some nits in the French localization of https://kubernetes.io/docs/setup/learning-environment/minikube/; I hope these changes help tidy them up
Fixup for #17939
/kind cleanup
/priority backlog

@sftim Thanks for fixing that up :) I cannot see the page on the website in French though.

It does look like the deploy might be broken. Separate issue?

Sure but I don't have admin rights on the netlify.
Le jeu. 5 déc. 2019 à 12:25, Tim Bannister<EMAIL_ADDRESS>a
écrit :

It does look like the deploy might be broken. Separate issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/website/pull/17945?email_source=notifications&email_token=AACJOIVMXAGNPLRAW6OUQMDQXDQI7A5CNFSM4JVNF3A2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGAMXWA#issuecomment-562088920,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACJOIUDAFUSBDPDD5EH2B3QXDQI7ANCNFSM4JVNF3AQ
.

These fixes should be OK to approve @remyleone; the issue with deployment was not related.

/lgtm
/approve


Can't set below 1970 Year as mindate

Can't set below 1970 Year as mindate please advice
var minDateAndroid = parseInt(d.getFullYear())-50 +"-" +("0"+(parseInt(d.getMonth())+1)).slice(-2)+"-"+("0"+(parseInt(d.getDate()))).slice(-2);
var options = {
type: 'date',         // 'date' or 'time', required
date: new Date(selectedDateAndroid),     // date or timestamp, default: current date
minDate: new Date(minDateAndroid).getTime(),  // date or timestamp
maxDate: new Date(maxDateAndroid).getTime()   // date or timestamp
};
window.DateTimePicker.pick(options, function (timestamp) {
})

Thank you for reporting this issue!
I was able to reproduce it and already found the problem, so there is no problem with your code.
A fix is in the making :).

New release 1.1.2 is available on npm.


New stop_circle icon

Is your feature request related to a problem? Please describe.
For our solution we need pause, stop and play buttons and in our design we've went for *_circle icon. However when it comes to the implementation I cannot find a stop_circle icon.
Describe the solution you'd like
I'd like to be able to use a stop_circle icon in addition to pause_circle and play_circle.
Describe alternatives you've considered
Additional context

Looking good to me @benteljones !

😊👍

Resolved by #2723


Features/block action with mask on

Pour l'issue #284

Hello! No thanks, the character is considered to be raising his mask slightly without revealing his identity. This change is not appreciated by the team. Thanks anyway. <3


bugfix_console_warning

fixes
remove console warning in below three.

@takuabonn  Excellent, appreciate the quick turn around.


Setting the environment variable to enable forwarded headers needs to be more prominent

While trying to get X-Forwarded-Proto header to be respected and after much frustration I noticed that in of the code sample it has
Environment.GetEnvironmentVariable("ASPNETCORE_FORWARDEDHEADERS_ENABLED")
Which led me to realise that I needed to set this environment variable in order to get it to work. Perhaps this information aught to be more prominent?

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

ID: e548cd16-b06c-5802-a1a7-c627167857ae
Version Independent ID: c48abb08-bea3-dcff-c067-2edf5dc9b3a6
Content: Configure ASP.NET Core to work with proxy servers and load balancers
Content Source: aspnetcore/host-and-deploy/proxy-load-balancer.md
Product: aspnet-core
Technology: aspnetcore-hostdeploy
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

Just FYI, setting this environment variable isn't required - it's for convenience so that you don't have to add both services.Configure<ForwardedHeadersOptions>(...) and app.UseForwardedHeaders(); with the correct setup.

@serpent5  that's great information. Is it worth adding
In the preceding code, setting Environment.GetEnvironmentVariable("ASPNETCORE_FORWARDEDHEADERS_ENABLED") variable isn't required - it's for convenience so that you don't have to add both services.Configure<ForwardedHeadersOptions>(...) and app.UseForwardedHeaders(); with the correct setup: https://github.com/dotnet/aspnetcore/blob/release/3.1/src/DefaultBuilder/src/WebHost.cs#L240-L252.
Let me know if you'd like to add that.

It looks like things have changed a bit since that section was written. The code sample that the reader is instructed to add is now part of the ConfigureWebDefaults stuff. I think it might be worth adding a note about how ASPNETCORE_FORWARDEDHEADERS_ENABLED is used by ConfigureWebDefaults to add both the configuration and the middleware. The only mention of that setting right now is in the code sample, but it doesn't really show that it has built-in support.
From what I see, if you're using ConfigureWebDefaults, you can just set the env var, without adding the code shown in the sample. Otherwise, you can add the code yourself, but then there's no need to use the the ASPNETCORE prefix on the setting name because it's being read by the app's code.
For reference, I found the PR that made the change: https://github.com/dotnet/AspNetCore.Docs/pull/12740. It looks like it was during the transition to 3.x, so it might be worth seeing if @Tratcher can comment on what I've said above.

Yup, these could use some updates.

ASPNETCORE_FORWARDEDHEADERS_ENABLED is supported by ConfigureWebDefaults starting in 3.0. The sample code should only be shown for older versions.
Add a disclaimer: ASPNETCORE_FORWARDEDHEADERS_ENABLED should only be used in deployment scenarios where you're:
A. Positive you're behind a trusted proxy
B. AND the deployment environment is unpredictable such that you can't specify KnownProxies or KnownNetworks. A cloud provider is such an environment.
Otherwise you should configure ForwardedHeadersOptions as shown above and set KnownProxies/Networks.

@serpent5  would you like to PR this when you have time?

Yeah, it's on my list.

I just stumbled across this issue while trying to get an ASP.NET Core app using OAuth working when debugging with GitHub Codespaces and getting really confused why the redirect URLs were sending localhost instead of the preview URL for the codespace.
I've written this up on my blog, but maybe adding something about needing to add ForwardedHeaders.XForwardedHost for Codespaces would be useful?
Specifically, with ASPNETCORE_FORWARDEDHEADERS_ENABLED set to true, I also had to add the following to my app:
if (string.Equals(builder.Configuration["CODESPACES"], "true", StringComparison.OrdinalIgnoreCase))
{
    builder.Services.Configure<ForwardedHeadersOptions>(
        options => options.ForwardedHeaders |= ForwardedHeaders.XForwardedHost);
}


Update and rename vtmc.txt to techin.txt

After reorganization our training center changed domain and name to techin.lt.

@vaclavzelenkevic First stage of verification passed, official domain is vtmc.lt as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision. Proof of domain ownership: https://www.vtmc.lt/priemimas-i-9-klase/

Currently, the old domain is still left for some time to full transition to the new domain. It may still take about half a year. Our new official domain is https://techin.lt or in english https://techin.lt/en/.

@vaclavzelenkevic Thank you for the update. I am not sure that the training center is eligible to be in this repository according to the current repository rules. Could you please provide us with an URL of a page on the official website where the school offers an IT-related long-term (>1 year) course?
Thank you!

The all IT programs is here: IT programmes. One of long-term course: JavaScript. Today these pages are not yet translated into English.
Thank you for your patience

@vaclavzelenkevic  Thank you for the clarifications. Pull request merged.


Switching between modes of operation

The game/simulation is assigned in two phases. During the first "testnet" phase students are expected to get themselves familiarized with the API and authentication. The system is restarted and the "realnet" phase begins. Ideally, these two phases have different rules so there's something to look forward to. The modes should also be changed between different semesters (different offerings of the course).
Currently, this is handled manually using git branches or commenting/uncommenting and copy & pasting. A more robust solution might look like a command line or environment variable that sets the rules of the game according to the mode. Codebase probably requires heavy refactoring to allow this as well.

Maybe we can load every aspect of the system from a configuration file (a.k.a yaml) and add different configuration files for different modes of the system.
I would also like to see mainnet and testnet running at the same time. Former being where everything has a real value and latter being a free playground for every aspect of the system.


Provide more information when test scripts fail.

This patch was helpful in identifying the cause of a build error (differentiating between unit tests and native tests) when both steps seemed to indicate nothing was wrong.

@kunalspathak @boingoing - I'm targeting this to release/1.3 because that's the farthest back that we run Native Unit tests.

The exit code by itself is an improvement but it only allows us to differentiate whether it was unit tests or native tests that failed. Unfortunately it still requires someone to look at the logs to find out which is which. It would be better to also print to stdout the information we have about the issue. I'll make this update.

LGTM

:shipit:

@dotnet-bot
test Windows x64_debug
test Windows x64_test
test Windows x86_debug
test Windows x86_test

@dotnet-bot test this please

@dotnet-bot test this please

Waiting until the next milestone.

Will replace with a new PR when ready.


wrong nullable type in views

Bug Description
I use sqlx prepare to check the database and the result is like this:
{
  "db_name": "PostgreSQL",
  "query": "SELECT code,is_onsale,name,sku,price,key,pic,A as a,B as b,C as c,D as d,COALESCE(num,0) AS num,total,available,available_days, COALESCE(p_m,0) AS p_m FROM goods_storage WHER code=$1",
  "describe": {
    "columns": [
      {
        "ordinal": 0,
        "name": "code",
        "type_info": "Varchar"
      },
      {
        "ordinal": 1,
        "name": "is_onsale",
        "type_info": "Int2"
      },
      {
        "ordinal": 2,
        "name": "name",
        "type_info": "Varchar"
      },
      {
        "ordinal": 3,
        "name": "sku",
        "type_info": "Varchar"
      },
      {
        "ordinal": 4,
        "name": "price",
        "type_info": "Numeric"
      },
      {
        "ordinal": 5,
        "name": "key",
        "type_info": "Varchar"
      },
      {
        "ordinal": 6,
        "name": "pic",
        "type_info": "Varchar"
      },
      {
        "ordinal": 7,
        "name": "a",
        "type_info": "Numeric"
      },
      {
        "ordinal": 8,
        "name": "b",
        "type_info": "Int8"
      },
      {
        "ordinal": 9,
        "name": "c",
        "type_info": "Int8"
      },
      {
        "ordinal": 10,
        "name": "d",
        "type_info": "Int8"
      },
      {
        "ordinal": 11,
        "name": "num",
        "type_info": "Int8"
      },
      {
        "ordinal": 12,
        "name": "total",
        "type_info": "Numeric"
      },
      {
        "ordinal": 13,
        "name": "available",
        "type_info": "Numeric"
      },
      {
        "ordinal": 14,
        "name": "available_days",
        "type_info": "Numeric"
      },
      {
        "ordinal": 15,
        "name": "p_m",
        "type_info": "Numeric"
      }
    ],
    "parameters": {
      "Left": [
        "Text"
      ]
    },
    "nullable": [
      true,
      true,
      true,
      true,
      true,
      true,
      true,
      true,
      true,
      true,
      true,
      null,
      true,
      true,
      true,
      null
    ]
  },
  "hash": "xxx"
}

And i wrote this in Rust
let query = sqlx::query_as!(
        ProductInfo,
        "SELECT
            code,is_onsale,name,sku,price,key,pic,A as a,B as b,C as c,D as d,
            COALESCE(num,0) AS num,total,available,available_days, COALESCE(p_m,0) AS p_m
        FROM
            goods_storage
        WHERE
            code=$1",
        code
    )
    .fetch_one(&state.poolpg)
    .await;

goods_storage is a VIEW in postgre, actually most of the column are NOT NULL, when i use the view's sql directly, they are not in Option<>, but when i use view to query, all columns are nullable like this

I just don't want check this value whether it is some or none and i ensure that they are not null ( especially there is a primary key cloumn, and not in view, SQL directly works well )
How can i do ?
Info

SQLx version: 0.7.4
SQLx features enabled: features = ["runtime-tokio", "postgres", "macros", "time", "rust_decimal", "json"]
Database server and version: Postgres 16.3 in Docker
Operating system: AlmaLinux 9.4 in Docker
rustc --version: rustc 1.79.0 (129f3b996 2024-06-10)

For example:
Postgres:
CREATE TABLE "public"."goods" (
  "code" varchar(8) COLLATE "pg_catalog"."default" NOT NULL,
  "is_onsale" int2 NOT NULL,
  PRIMARY KEY ("code")
);

CREATE VIEW "public"."goods_code" AS
SELECT
	goods.code AS code
FROM
	goods
WHERE
	( goods.is_onsale = 1 )
ORDER BY
	goods.code;

When i use SQL directly

When i use VIEW

so strange

https://docs.rs/sqlx/latest/sqlx/macro.query.html#nullability-output-columns

finally, according to the docs, i find out the reason
I wanna know why do like that, it makes me don't want use the VIEW but only the directly SQL

You can also enforce whether to use Option values or not by selecting each column individually:
let products = sqlx::query_as!(
    ProductFull,
    r#"
    SELECT
        p.id as "id!",
        p.name as "name!",
        p.description as "description",
        p.price as "price!",
        p.image as "image",
        p.created_at as "created_at!",
        p.sell_count as "sell_count!"
    FROM public.product_with_sells p
    "#,
)

Add an exclamation mark to enforce NOT NULL.

You can also enforce whether to use Option values or not by selecting each column individually:
let products = sqlx::query_as!(
    ProductFull,
    r#"
    SELECT
        p.id as "id!",
        p.name as "name!",
        p.description as "description",
        p.price as "price!",
        p.image as "image",
        p.created_at as "created_at!",
        p.sell_count as "sell_count!"
    FROM public.product_with_sells p
    "#,
)

Add an exclamation mark to enforce NOT NULL.

Thanks for your suggestion, it is the right way to solve this problem!


Fix typo in parsing serial config arguments

"serail" should be "serial".
Fixes: 4df084be1de1 ("Support get serail configure values from FW")
Tracked-On: OAM-111789
Signed-off-by: Jiaqing Zhao<EMAIL_ADDRESS>

Keep the typo for compatbility, close it


fix(chat): fix Simple Rag example (Issue #2750)

Description:
fix Simple Rag example
Issues:

Issue #2750

Related:
https://github.com/epam/ai-dial-app-controller/pull/10
Checklist:

[x] the pull request name complies with Conventional Commits
[x] the pull request name starts with fix(<scope>):, feat(<scope>):, feature(<scope>):, chore(<scope>):, hotfix(<scope>): or e2e(<scope>):. If contains breaking changes then the pull request name must start with fix(<scope>)!:, feat(<scope>)!:, feature(<scope>)!:, chore(<scope>)!:, hotfix(<scope>)!: or e2e(<scope>)!: where <scope> is name of affected project: chat, chat-e2e, overlay, shared, sandbox-overlay, etc.
[x] the pull request name ends with (Issue #<TICKET_ID>) (comma-separated list of issues)
[x] I confirm that do not share any confidential information like API keys or any other secrets and private URLs

/deploy-review

/deploy-review


Basic Vocabulary

We need to agree upon a basic vocabulary for the open standard.
Note: this is not to agree upon a vocabulary for stream implementations or their documentation!
This is for the purpose of the consistency within this standard and it's documents only.

Stale. Closing


Automaticallly use first child link when index is empty

Besides checking the emptiness of the index, we can introduce a frontmatter key to achieve this goal.
----
navigation.redirect: true
---

https://github.com/nuxt/framework/issues/7230#r962570007

👍


Optimize: merge common aggregation functions

Discussed with @st1page

For example,
select avg(x) a, sum(x) s, count(x) c from t;

will be executed as
select expr1 / expr2, s, c from
  (select sum(x) as expr1, count(x) as expr2, sum(x) s , count(x) c from t);

Here, the two sum(x) and two count(x) can be simply reused.
Another example is NexMark Q15
https://github.com/risingwavelabs/risingwave/blob/0259125649a7494e4d58d83f1c8f7d5d1d3cdd7f/src/frontend/planner_test/tests/testdata/output/nexmark_source.yaml#L1126
StreamHashAgg [append_only] {
  group_key: [$expr1, bidder, auction, flag],
  aggs: [
    count,
    count filter((price < 10000:Int32)),
    count filter((price >= 10000:Int32) AND (price < 1000000:Int32)),
    count filter((price >= 1000000:Int32)),
    count filter((price < 10000:Int32)),
    count filter((price >= 10000:Int32) AND (price < 1000000:Int32)),
    count filter((price >= 1000000:Int32)),
    count filter((price < 10000:Int32)),
    count filter((price >= 10000:Int32) AND (price < 1000000:Int32)),
    count filter((price >= 1000000:Int32))]

Obviously the 9 count agg functions can be merged to 3, so that we reduce the aggregation state size to 1/3.

We do not need to implement it in Agg executor but implement it as an optimizer rule we can write a project ahead :thinking:


[merge to master] Add the KFPv2 Run Comparison page

Description of your changes:

Add the KFPv2 Run Comparison page documentation to the sdk-v2 folder.

/uncc @alfsuse
/uncc @pdmack
/cc @zijianjoy
/assign @zijianjoy

/lgtm
/approve
Thank you Chris for working on user documentation!


Alphabetize the list

Items under diff heads are sorted Alphabetically
Fixed issue #187 187

Thanks for contributing @jabhishek87, this was already done by #188 but your pull request is still counting for hacktoberfest even it not gets merged.
Have a happy hacking ✨

Thanks for that , but in my profile it shows 0 oly can you help

Actually @jabhishek87 I think they aren't counting already, only pull requests opened by 1 October will count. So consider this pull request as an warming up.


Add FileReference to FileLocator transformation

Consider an example where you choose a file (in a file dialog):

/home/username/development/gtoolkit/my-file.txt
but you would rather use a FileLocator instance in your code:
{imageDirectory}/my-file.txt

Similarly with any predefined FileLocator origins. This is the case we want to support.


Reduced pagingMaxLimit to 100 in order to comply with upcoming Personio API changes

Personio will reduce the limit parameter to 100 on December 7th 2024.
What does this PR do?
Reduces the const pagingMaxLimit from 200 to 100.
What is the effect of this change to users?
Users will be able to continue using the Personio API without any issues.
How does it look like?

Any background context you can provide?
Pagination enforcement - V1 Employees API
What is needed from the reviewers?
Review, test and merge
Do the docs need to be updated?
No
Should this change be mentioned in the release notes?

[x] CHANGELOG.md has been updated

Awesome (your PR, not the reduced Personio API v1 page size 😀). Thanks!
Could you please read the below, tick the boxes and leave "us" (Giant Swarm GmbH) a comment stating that you have read and agree to terms.
By opening this Pull Request, you certify that you:

[ ] are the sole author of your contribution and are legally entitled to grant us a license to use it

or, your contribution is on behalf of, and with explicit permission of, the legal owner of the contribution

[ ] grant us a nonexclusive, irrevocable, transferrable license to use, reproduce, display, sell, and further license your contribution and derivative works
[ ] agree that your contribution is made freely and bears no obligation or expectation for payment, royalties, recognition, or other compensation from us
[ ] agree for your contribution to be bound by the terms in the license accompanying this repository

If you are making this submission on behalf of a current or former employer, you also certify that you have authorization from the employer to make this contribution, or the employer has released all legal interest in this contribution.

Awesome (your PR, not the reduced Personio API v1 page size 😀). Thanks!
Could you please read the below, tick the boxes and leave "us" (Giant Swarm GmbH) a comment stating that you have read and agree to terms.
By opening this Pull Request, you certify that you:

[✅]  are the sole author of your contribution and are legally entitled to grant us a license to use it

or, your contribution is on behalf of, and with explicit permission of, the legal owner of the contribution

[✅]  grant us a nonexclusive, irrevocable, transferrable license to use, reproduce, display, sell, and further license your contribution and derivative works

[✅]  agree that your contribution is made freely and bears no obligation or expectation for payment, royalties, recognition, or other compensation from us

[✅]  agree for your contribution to be bound by the terms in the license accompanying this repository

If you are making this submission on behalf of a current or former employer, you also certify that you have authorization from the employer to make this contribution, or the employer has released all legal interest in this contribution.

I have read the terms and agree to them.


Please add to the readme how to run standalone with just an ssh server

I am running balena OS and it has a modified version of docker so I am not able to connect to the docker daemon remotely.
Instead, I am thinking to just start a development container with ssh and using the vs-code remote ssh extension to develop on the balena device remotely.
I looked through the docs and tried few commands, but couldn't figure out how to start a ssh server so that vs-code can connect to it remotely.
Also looked at this video, but the sshd service doesn't exist in the images I tried - base:0-debian11, base:0-buster
https://www.youtube.com/watch?v=KuSNpZgDYDs
docker run -it --init --rm mcr.microsoft.com/vscode/devcontainers/base:0-buster

SSH is not in any of these images by default. We have a script you can use to add it. https://github.com/microsoft/vscode-dev-containers/blob/main/script-library/docs/sshd.md
the
The main thing you'll need to do in this scenario that you do not with VS Code is expose the SSH server port.  By default that is on 2222.
docker run -it -p 2222:2222 --init --rm mcr.microsoft.com/vscode/devcontainers/base:0-buster

You may also be interested in the upcoming support for using VS Code Remote - SSH and Remote - Containers together.


Joffrey Baratheon (GoH) entering play

When Joff enters play and his abbility is triggered, house crad is knelt but he is not (not tested with another loyal character entering play).

Thanks! This bug also affects Catapult on the Wall and any other card that requires kneeling two separate cards as a cost.


Docker exposedbydefault = false didn't work

With the following traefik.toml and Traefik v1.0.2 (official docker image), all my docker containers are exposed, despite setting exposedbydefault = false.
defaultEntryPoints = ["https"]

[acme]
email =<EMAIL_ADDRESS>storageFile = "/etc/traefik/acme.json"
entryPoint = "https"
onDemand = false
OnHostRule = true

[entryPoints]
  [entryPoints.https]
  address = ":443"
    [entryPoints.https.tls]

[retry]

[web]
address = ":8080"

[docker]
endpoint = "unix:///var/run/docker.sock"
domain = "docker.localhost"
watch = true
exposedbydefault = false

I have the same issue, I had to put the label traefik.enable=false to hide some containers.

I think that feature hasnt made it into any release version yet

Ah yes, you're quite right. Sorry!

Somehow this still doesn't work with either 1.5 or 1.6.
Pretty annoying if you have tons of projects up.. :/
[docker]
endpoint = "unix:///var/run/docker.sock"
domain = "mydomain.tld"
watch = true
exposedbydefault = false

still creates a frontend and backend for any container started...

@bernhardberger come on Slack to explain your issue.

seems like something in my docker command killed parts of the .toml file.
all good can be closed..
Ludovic Fernandez<EMAIL_ADDRESS>schrieb am Fr., 4. Mai 2018,
17:34:

@bernhardberger https://github.com/bernhardberger come on Slack to
explain your issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/containous/traefik/issues/663#issuecomment-386638907,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACAyg9V4FZdqzkt8pA2CTswQYIZHxrH6ks5tvHTvgaJpZM4J0gLz
.

@bernhardberger can you explain what was the issue? I have the same problem.
My toml:
[docker]
endpoint = "unix:///var/run/docker.sock"
watch = true
exposedbydefault = false

but in debug logs there is "ExposedByDefault":true, and i have to add traefik.enable: false labels

I had to specify the path to the configFile in the docker-compose "command".
I also had to omit any other parameters (the only param being the
configFile, somehow any param cancels out the use of this section in the
config file..
Lukas<EMAIL_ADDRESS>schrieb am Di., 8. Mai 2018, 19:57:

@bernhardberger https://github.com/bernhardberger can you explain what
was the issue? I have the same problem.
My toml:
[docker]
endpoint = "unix:///var/run/docker.sock"
watch = true
exposedbydefault = false
but in debug logs there is "ExposedByDefault":true, and i have to add traefik.enable:
false labels
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/containous/traefik/issues/663#issuecomment-387488546,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACAyg2Js7IVa6yn9WrKP1APl1sJFgbDXks5twdx-gaJpZM4J0gLz
.

https://docs.traefik.io/v1.6/basics/#static-trfik-configuration

It means that arguments override configuration file, and key-value store overrides arguments.

the provider-enabling argument parameters (e.g., --docker) set all default values for the specific provider.
It must not be used if a configuration source with less precedence wants to set a non-default provider value.

To summary, don't mix CLI arguments and TOML on the same configuration section (ex: docker)

Yeeeyyy...  I had in docker-compose.yml
command: --api --docker
and after remove that it starts working !!


Paths (base and assets) should be set to '' in svelte-kit preview

Describe the bug
If you're using paths.base or paths.assets it's difficult/impossible to debug the production build locally. I would have thought that this... https://github.com/sveltejs/kit/blob/3d29d23c15c74d5f5dae38db2e3158e573d16db0/packages/kit/src/core/start/index.js#L41-L48 ...would be sufficient, but it turns out I would have been wrong
To Reproduce
Add paths config to a project, then svelte-kit build && svelte-kit preview
Expected behavior
It should work (where 'work' means 'load JS and CSS')
Severity
Right now, extremely damn high

I've been building https://sidharthv96.github.io/mermaid-live-editor/ using github pages. So a baseURL is necessary.
To debug an issue I had in production which I could not reproduce locally as base path was not used.
To keep both environments in sync, It would be better to have basePath in local if it is set.
Adding this works for all pages except the root.
https://github.com/sveltejs/kit/blob/4dec03a2697b92bb06c0cb9cb348e7f07a193d38/packages/kit/src/core/dev/index.js#L90
So localhost:3000/mermaid-live-editor/edit would work, but localhost:3000/mermaid-live-editor/ would not.

I'm hitting this issue recently too.

Maybe I'm misunderstanding what "_svelte_kit_assets" is for. Am I supposed to provide that path myself?

closing this as out of date — base and assets (replaced with _svelte_kit_assets) are now used in dev and preview


🐛 Bug Report: Backend fails to come up with Entity Feedback Backend Plugin Integration

📜 Description
Followed the steps to configure the frontend and backend plugin as given here - https://github.com/backstage/backstage/tree/master/plugins/entity-feedback
However, after adding below line the backstage backend fails to come up and running, (sort of hanged)
const entityFeedbackEnv = useHotMemoize(module, () => createEnv('entityFeedback'));
If this line is commented out then backstage backend works fine.
Any suggestions on what could be wrong?
CC : @kuangp
👍 Expected behavior
The plugin should work properly.
👎 Actual Behavior with Screenshots
Backend is hanging. No logs printed after Build succeeded line
$ yarn start-backend
yarn run v1.22.18
$ yarn workspace backend start
$ backstage-cli package start
Build succeeded
Restarting app...
Build succeeded
👟 Reproduction steps
Follow all the steps provided here - https://github.com/backstage/backstage/tree/master/plugins/entity-feedback
📃 Provide the context for the Bug.
No response
🖥 Your Environment
No response
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
None

hmm we'll probably need more info here to diagnose the issue. Can you share what the rest of your backend index.ts looks like?
This plugin is also hooked up in this repos example app and looks to be working fine so maybe you can reference it's setup to compare with your own?
https://github.com/backstage/backstage/blob/da033811816d0fc1711da5f73ce2913615e43e75/packages/backend/src/index.ts#L152-L154

@sharadpattanshetti I saw this with my backend unit tests failing right after installing the feedback backend with:
yarn add --cwd packages/backend @backstage/plugin-entity-feedback-backend
When I re-run yarn install at the root it fixed it though.

Thanks @kuangp  and @FilipSwiatczak for your replies. We do have the same code in index.ts as in above example. I tried commenting other plugins and keep only entityFeedback but backend still fails to come up.
@FilipSwiatczak  I did try reinstalling plugin-entity-feedback-backend at the root again but same issue.

Hmm, would it be possible for you to create a reproduction repository so that we can dig in a little more @sharadpattanshetti?

Sorry for the delayed reply. I could get past the above issue by cleaning up the node modules and yarn.lock.
However, getting 400 Bad Request on below api when clicked on Like or Dislike button :
http://localhost:7000/api/entity-feedback/ratings/component%3Adefault%2Fmycomponent

You may be getting a 400 if you're not signed into Backstage with a valid user identity:
https://github.com/backstage/backstage/blob/f16d9f31cd07b04048460bac4b406566ec2a0a5f/plugins/entity-feedback-backend/src/service/router.ts#L133-L136
The backend will logs feedback with the username of the person that supplied it so it requires you to be signed in as a non-guest user for this plugin to work.

I am using Backstage v1.9.1

also realized you're on 1.9, this plugin was released in v1.11 so make sure your deps are upgraded to the latest version to successfully install this plugin

The 400 error is resolved when signed in. I shall try the complete plugin after upgrading to v1.11.
Thank you so much @kuangp for your help.

no problem! @benjdlambert I think this can be closed now


Exception on commit: Unexpected output of ls-files

I get this when trying to commit with gl commit  -exc known-good -m ...

# Oops...something went wrong (recall that Gitless is in beta). If you want to help, re
port the bug at http://gitless.com/community.html and include the following in the emai
l:

GL Version: 0.5

Traceback (most recent call last):
  File "/usr/local/lib/python2.7/site-packages/gitless/cli/gl.py", line 69, in main
    return SUCCESS if args.func(args) else ERRORS_FOUND
  File "/usr/local/lib/python2.7/site-packages/gitless/cli/gl_commit.py", line 48, in main
    if not _valid_input(only_files, exc_files, inc_files):
  File "/usr/local/lib/python2.7/site-packages/gitless/cli/gl_commit.py", line 145, in _valid_input
    f = file_lib.status(fp)
  File "/usr/local/lib/python2.7/site-packages/gitless/core/file.py", line 211, in status
    return _status(fp)[0]
  File "/usr/local/lib/python2.7/site-packages/gitless/core/file.py", line 286, in _status
    git_s = git_status.of_file(fp)
  File "/usr/local/lib/python2.7/site-packages/gitpylib/status.py", line 55, in of_file
    return _status_from_output(s, _is_au_file(fp), fp)
  File "/usr/local/lib/python2.7/site-packages/gitpylib/status.py", line 129, in _is_au_file
    raise Exception('Unexpected output of ls-files: {0}'.format(out))
Exception: Unexpected output of ls-files: H known-good/.gitignore
H known-good/Makefile
H known-good/independent/c-4df500fa93a8e8f5886b3590424a7aa67e21bf0e.tar.gz
H known-good/make-known-good

Note that the "unexpected output" is comming from the directory that I'm trying to exclude from the commit.

343e7ac94a42377d97cef08d7693bb381aa758f0

Fix will go out in next release (0.7)


[SPARK-41680][UI] Protobuf serializer for CachedQuantile

What changes were proposed in this pull request?
Add Protobuf serializer for CachedQuantile
Why are the changes needed?
Support fast and compact serialization/deserialization for CachedQuantile over RocksDB.
Does this PR introduce any user-facing change?
No
How was this patch tested?
New UT

cc @LuciferYang @techaddict

This is a simple one. I am merging it to master.


New version: Anaconda.Anaconda3 version 2021.11

Installation timed out. \r\n\r Auto-updated by vedantmgoyal2009/winget-pkgs-automation in workflow run 482
Microsoft Reviewers: Open in CodeFlow

/azp run

/azp run


[Chore] standardize on default rustfmt style

Description:
Suggest using Rust's default formatting style (rustfmt default settings) to:

Follow Rust ecosystem conventions
Reduce merge conflicts from formatting differences

This will help align our codebase with the standard Rust style guide and simplify contribution process.
Context:
Currently working on clipboard functionality and encountering issues where reformatting existing modules causes large-scale file changes. For example, when modifying the clipboard handling code, the formatting changes affect the entire file, making it difficult to:

Review actual functional changes vs formatting changes
Track meaningful code modifications
Perform effective code reviews

A standardized format would help keep diffs focused on actual code changes rather than style adjustments.

Thank you so much for this great suggestion.
I have applied rustfmt to the entire main branch and added rustfmt.toml to show potential new contributors that we expect PR's to be formatted according to rust standards!
I'll close this issue as the suggestions are applied!


Options should not be overwritten with dict

https://github.com/radiasoft/rsopt/blob/8d3d8c871f5e67f0c23362a80a91b7a704e0beb6/rsopt/libe_tools/optimizer.py#L64

This actually a setter. Implementation is maybe a bit confusing, but I think it is working as intended


Feature Request: Drag & Drop Support

As a user, I want to simply run a compendium macro which opens a MM slot. Initially, the dialog window would be empty.
const mm = game.modules.get('macro-manager')?.api.mm;
mm.openMacroManager( 2 );

^^ these should come in a compendium.
Once my empty dialog window is open, I want to be able to drag and drop macros from my macro folder into the empty dialog. I can then drag and drop within the same dialog to re-arrange my order of macros.

This is a great idea! But, exceed my knowledge. lol


Better support pseudo-states in selectors with :host()

When rewriting rules with pseudo-states both inside and outside a :host() selector, we were not properly creating a pseudo-*-all-based selector. For example, from :host(.foo:focus) .bar:hover, we would generate:
:host(.foo.pseudo-focus-all) .bar.pseudo-hover-all (wrong)
rather than
:host(.foo.pseudo-focus-all.pseudo-hover-all) .bar (correct)

@ghengeveld I have a couple more PRs to put up, so again, it can be labeled patch and skip-release.


Revamp the FAQ section

fix: #149

Hey @TejasNasre please review my PR.

I will merge in morning

bro what about light mode and the ui is so basic not making with current theme a lit bit


Expand Firefox support documentation for SVG Filters

Link to the Page
https://github.com/skeletonlabs/skeleton/discussions/1426
Describe the Issue
We have received several inquiries about the current status of the SVG filter support for Firefox. MDN and caniuse both incorrectly state this is fully supported. Upon testing I've confirmed this is still not functional, so let's expand the documentation to have a centralized explanation to link to.
Are you able to create a Pull Request with the fix?
Yes

New warning:


40 second countdown for reinficrnements on every wave start

Hey man could you please add a simple 40 second countdown that starts every wave? It would be really simple and help a lot with reinficrnements. Its always just 40 seconds so I imagine it would be easy to implement.

I'm not interested in adding this explicitly, but you can get the same info by enabling splits and watching the in-wave timer count to 40:00. You can reduce spam by limiting the display to a single wave.
I believe adding a countdown or something more specifically about spawn timing would violate some rules on indicating timing of mechanics.


ISSUE-34-2: Add Application Context

Allow enabling application context by passing following optional values via options object.
Available options:

setApplicationContext (boolean), defaults to false

Cherry picked into #49


Stylesheet live reloading is not working using Gradle

When Gradle is used with the following configurations:
quarkus.fx.views-root=views/
quarkus.fx.source-resources=src/main/
quarkus.fx.target-resources=build/

I got this line printed in logs:

Stylesheet live reload : substituting 'file:/C:/Users/fouad/IdeaProjects/quarkusfx-demo/build/resources/main/views/main/main.css' with 'src/main/resources/main/views/main/main.css'

and this exception:
Caused by: java.nio.file.NoSuchFileException: src\main\resources\main\views\main

'src/main/resources/main/views/main/main.css' should be 'src/main/resources/views/main/main.css'

Hello, do you have a repo somewhere with reproducer ? ty

Hello, do you have a repo somewhere with reproducer ? ty

https://github.com/Eng-Fouad/quarkus-fx-0.9-bug

Please update your configuration to the following :
quarkus.fx.views-root=views/
#quarkus.fx.source-resources=src/main/
quarkus.fx.target-resources=build/resources/main/

If not clear, we can improve documentation.

Please update your configuration to the following :
quarkus.fx.views-root=views/
#quarkus.fx.source-resources=src/main/
quarkus.fx.target-resources=build/resources/main/

If not clear, we can improve documentation.

That works, thanks. It would be helpful if we add a note to docs for Gradle users.


Feature Request - Madsonic

I'm currently working on adding this.

This has now been added. If anyone finds any issues please let us know. Thanks
www.madsonic.org

Closing, If anyone reads this and has any problems please log an issue and I'll take a look.


DwC importer assign BiocurationGroup values to rows

I have custom BiocurationGroup vocabulary, and I would like to be able to assign those tags via columns in the DwC importer.
Ideally, it would look something like this:

(other columns)
TW:BiocurationGroup:lifestage
TW:BiocurationGroup:sex
TW:BiocurationGroup:caste
TW:BiocurationGroup:subcaste

...
adult
female
queen
alate

...
adult
female
worker
soldier

...
larvae
male
male

@LordFlashmeow I think you could pivot the tables.  This is adding Tags (subclasses of actually).  So ifeach column is a Keyword, and the value is a 1 if present.  Something like 'TW:BiocurationClassification:<keyword_name>`.
This should not block merge, but be a feature post merge.

True, that could also work. However, I suspect that most curator data isn't going to be pivoted. If the data is stored as

lifestage
sex

adult
male

larvae
female

Then it requires some data manipulation knowledge to convert it to

TW:BiocurationClassification:adult
TW:BiocurationClassification:larvae
TW:BiocurationClassification:male
TW:BiocurationClassification:female

1

1

1

1

What tool would you recommend for this transformation (besides scripting)?

BTW in https://github.com/SpeciesFileGroup/taxonworks/commit/ff9c22afeaee132f789b3a81640426dd649e4680 I implemented what @LordFlashmeow originally posted. I hope it is better than adding multiple rows with ones and blanks.
Note that sex is mapped and will find or create "sex" BiocurationGroup and map value by finding or creating BiocurationClass. It might collide if both sex and custom TW fields are specified.
TW::BiocurationGroup:* requires both that the BiocurationGroup already exists as well as the BiocurationClassification in field value. In both, column and field value, you may match by either URI or name (URI prioritized when matching).

What's the best way to create containers when the CO has multiple individuals with different biocuration classes? Is it to create multiple rows, one for each individual (or group of individuals) with the "Containerize specimen with existing ones when catalog number already exists" setting enabled?

Yes, I believe so.  They will be grouped by a Container::Virtual.  I'm not sure if prep type also influences when it matches a specific container type.

Side note that the export behaviour has changed to export via a match to the group that groups the attribute.  So you can have individual attributes load from the importer, then make them export to a specific DwC field for lifeStage and Sex.

@mjy I don't think we're planning to use this in the near future. Our data is too variable and inconsistent, and we don't think containerizing benefits our dataset.


[review only] Check benchmark memory usage using tracemalloc

For review only. Ran benchmarks with tracemalloc profiler to check engines' memory usage calculations.
A test run output is in the attachment.
The calculations seem to be good enough (less than 10% optimistic, usually within 1%).

Done.


Seperate repository for user layouts

Now that kmonad has an organization, wouldn't it make more sense for all the user layouts to be in another repository as they are not related to kmonad's development? The repository could be named something like kmonad/community-layouts

What would we gain from a change like that?  I think having user configurations in the same repository as the project (and the same directory as the tutorial!) is worth a lot in terms of discoverability

Hmm, my thoughts are

Having a separate repository would be better for organization.
Developers won't need to clone all the user-layouts to code (though with such a small userbase this is negligible as of now)
Discoverability isn't that hurt if we link it at the README like the folder is linked right now (I didn't realise that they were in the same directory actually)

I've personally never even looked at the user layout directory, but I have looked at the tutorial.
I'm not really a fan of the user layout organization method honestly, the goal is presumably "these people use kmonad and here is what they use it for, take some inspiration :)", but ideally it would be labelled with the purpose (I'm aware that this isn't easy), so you can quickly copy-paste and have a "good enough" config for some users.

I've opened up the wiki to public editing. Maybe that would be a good place to keep track of keymap examples?

Since keymaps are basically just large files of code, I don't necessarily think that a wiki is the best place to contain them.  Then again, this way people didn't have to put in pull requests every few months if they update their configs...  GitHub wikis really are publicly editable though, so there is the possibility of a malicious actor modifying the existing configs (though I judge this community to be awesome enough not to do that)

Since keymaps are basically just large files of code, I don't necessarily think that a wiki is the best place to contain them.

Hmmm, you have a point there.

(though I judge this community to be awesome enough not to do that)

Also true, the people who we run into have been extraordinarily lovely. However, whatever is exposed to the internet eventually gets trolled. Basic rule of life :).
So, what would be the best thing to do? User-config repo on the organization? Just leave it as it is? I always enjoyed being able to look through other users' keymaps in QMK, which is why I initially set things up this way.

Another option would be to link to the repositories of the users somewhere on the readme/wiki/in the repo. So that not anybody can change the configs.

Sort of similar to how qmk adds all of the keyboards as submodules i believe

What would we gain from a change like that?

Probably not a big issue, but by doing this, we can keep development git log "clean"? This is not an issue atm because of small userbase and few contributions. So IMHO, what we should be discussing is whether to do it now or to do it when there are enough/frequent contributions.

I think it's probably a good change that I intend to make when we get close to releasing a new version.

 Everyone maintains his/her own snippets (with independent commit logs) and they can be also shared.
Cross-linking to #303, which could be somewhat related with this issue if we want to share snippets instead of full configs.

I'd like to do something about this after all.  So far, the suggested options seem to be

Create a new repository within the kmonad organisation
The wiki is freely editable, so move everything over there
Have users maintain their own repos/gists with their configurations and link to them in the README
Have users maintain their own repos with their configurations and include them as submodules

Is there a general consensus here in which direction to move in order to inconvenience the smallest numbers of people? :)

Create a new repository within kmonad organisation

I think this is needed so that we can have a "checked"/"curated" configs. The problem is mainly because of shell commands. I understand that the users must check the config they import, but when checking, especially a big config, it's quite likely to miss these kinds of things. Having a community maintained repo would make checking/maintaining things safer. The additional maintenance overhead can be reduced by giving access to this repo to few people. They can then review/merge PRs. This is what Karabiner does.

I finally got around to this: https://github.com/kmonad/kmonad-community is now live!


fix ReflectionTypeLoadException when opening the Receivers dropdown

Overview
Fixes an exception that prevents the use of the Receivers dropdown in an Interactable when some assembly types can't be loaded (e.g. some Cecil assemblies etc. that have weird types).
Changes
There was already AssemblyExtensions.GetLoadableTypes so this is now properly used in TypeExtensions.GetAllSubClassesOf. No new code added besides renaming "GetTypes" to "GetLoadableTypes".
Notes
In recent Unity versions any of these "walk assembly, get types" constructs could be vastly sped up by using the TypeCache API available from 2019.2. This would reduce domain reload times considerably.

With this change, you can remove this script from the "allowed scripts to use GetTypes" list at https://github.com/microsoft/MixedRealityToolkit-Unity/blob/1f3354089351f1f6a2110c75a72d1443af2e99ce/scripts/ci/validatecode.ps1#L405-L411
Also pinging @wiwei to see if there was a reason this script was added to that list instead of updated in https://github.com/microsoft/MixedRealityToolkit-Unity/pull/8343.

In recent Unity versions any of these "walk assembly, get types" constructs could be vastly sped up by using the TypeCache API available from 2019.2. This would reduce domain reload times considerably.

Good call! I wasn't aware of this API. We should definitely look into that.

/azp run

With this change, you can remove this script from the "allowed scripts to use GetTypes" list at
https://github.com/microsoft/MixedRealityToolkit-Unity/blob/1f3354089351f1f6a2110c75a72d1443af2e99ce/scripts/ci/validatecode.ps1#L405-L411
Also pinging @wiwei to see if there was a reason this script was added to that list instead of updated in #8343.

Ah, that was an oversight - I wanted to add an exemption for the type loading and I think I added an exemption for both extensions (rather than just the GetLoadableTypes() one)

@davidkline-ms please don't forget to remove https://github.com/microsoft/MixedRealityToolkit-Unity/blob/1f3354089351f1f6a2110c75a72d1443af2e99ce/scripts/ci/validatecode.ps1#L410 as the others pointed out - wanted to push it but you merged already :)

@davidkline-ms please don't forget to remove

We will be doing that in the 2.6 branch (mrtk_development). Keeping it for 2.5.1 shouldnt hurt anything,


Implement control onNextPressed()

Hi, i'm currently working on AppIntro, but i have to show a Dialog message when i press NextButton in the first fragment if i haven't selected any RadioButtons into it before going on the Second one.
Is possible to do or i must implement something in the Fragment?

You could try getting the pager and capture the event with a custom click listener. Here is the idea.
private ViewPager pager;
pager = getPager();

customNextButton.setOnClickListener(new View.OnClickListener() {
    @Override
     public void onClick(@NonNull View v) {
        /* If radio buttons are empty
              then showDialog();
          else
              pager.setCurrentItem(pager.getCurrentItem() + 1);
        */
     }
 });

Same idea: but the "CustomNextButton" is already a class inside the repo?

CustomNextButton is the button on the view
CustomNextButton = (Button)findViewById(R.id.yourButtonId);

Is this resolved @Nem2s?

Sorry for delay but i don't understand: through the getPager() can I extract the CustomNextButton? I'm using the "integrated" one, i don't have any buttons in my layout.

EDIT: solved, I implemented the @Betobit solution! Thanks a lot

@Nem2s glad you got it working :)

@Nem2s (: Nice! And sorry for my hurry answer I was in the U :P


utils.mk:30: *** XILINX_VITIS variable is not set, please set correctly and rerun.  Stop.

Closing this as not enough info provided. Please re-open if you are still facing this issue and provide more information in description like which particular design shows this failure and how to reproduce.