How to Deploy Blog Site

Hello.
I want to deploy this theme will you please tell me what is the best platform where I can host the theme ? I have my customised domain as well I just want to host the website with my custom domain will you please tell me what is best platform to host the website with the custom domain? Also I'm starting this on initial level please suggest me some free platform for the deployment .

Hi,
Hmm there are several options to host a Ghost blog but all of them are not for free, the only one I know is https://www.digitalpress.blog/
The only thing is that your blog will have ads unless you pay.


Add monetization support

Summary
Add monetization support.

[x] Add SKU
[x] Add Entitlement
[x] Add Gateway events
[x] Add REST routes
[x] Add interaction response type 10
[x] Add REST response builder
[x] Add interaction.entitlements property

Notes/Questions

Should create_test_entitlement take in a user/guild object instead of the EntitlementOwnerType being the toggle?
SKU object is missing several fields that are simply not or partially documented, to my knowledge these are unused by apps
Entitlement object includes a subscription_id which is only partially documented but seems to be referenced so may be important? Unclear.

Checklist

[x] I have run nox and all the pipelines have passed.
[x] I have made unittests according to the code I have added/modified/deleted.

Related issues
Closes #1775

I added tests for all the things implemented in this PR afaict, not sure why codeclimate is still failing.

This needs to be added to hikari.__init__.py:
from hikari.events.monetization_events import *

For create_test_entitlement I would prefer a guild and user kwarg, so something like this:
await bot.rest.create_test_entitlement(
    event.interaction.application_id,
    sku="1",
    guild="1",
)
await bot.rest.create_test_entitlement(
    event.interaction.application_id,
    sku="1",
    user="1",
)

Then raise an exception if they specify both.
Or, "owner" kwarg that can be a user or guild, but if they specify just the snowflake ID, make it required to specify owner_type. In other words:
await bot.rest.create_test_entitlement(
    event.interaction.application_id,
    sku="1",
    owner="1",
    owner_type=hikari.monetization.EntitlementOwnerType.GUILD
)
await bot.rest.create_test_entitlement(
    event.interaction.application_id,
    sku="1",
    owner=await bot.rest.fetch_guild("1"),
)

would be equivalent.
Personally, I like the first one with separate user and guild args.

For create_test_entitlement I would prefer a guild and user kwarg, so something like this:
await bot.rest.create_test_entitlement(
    event.interaction.application_id,
    sku="1",
    guild="1",
)
await bot.rest.create_test_entitlement(
    event.interaction.application_id,
    sku="1",
    user="1",
)

Then raise an exception if they specify both.
Or, "owner" kwarg that can be a user or guild, but if they specify just the snowflake ID, make it required to specify owner_type. In other words:
await bot.rest.create_test_entitlement(
    event.interaction.application_id,
    sku="1",
    owner="1",
    owner_type=hikari.monetization.EntitlementOwnerType.GUILD
)
await bot.rest.create_test_entitlement(
    event.interaction.application_id,
    sku="1",
    owner=await bot.rest.fetch_guild("1"),
)

would be equivalent.
Personally, I like the first one with separate user and guild args.

I personally feel like that hikari should try to closely mirror the Discord API, wherever possible, so I'm against this idea, but if the maintainers feel otherwise, I'll adjust it.

any progress on this


[BUG] Cluster inaccesible after upgrade

Rancher Server Setup

Rancher version: 2.8.0
Installation option (Docker install/Helm Chart): Helm chart
Proxy/Cert Details:

Information about the Cluster

Kubernetes version: 1.23
Cluster Type (Local/Downstream): EKS

User Information

What is the role of the user logged in? Admin

Describe the bug
After upgrading from Rancher 2.6.9 to 2.8.0 a cluster is inaccessible.
My theory is that the "Updated" condition appears as false, due to:
[Syncing error] error for cluster [c-vs7fd]: health error for node group [ng-workers-single-az] in cluster [c-vs7fd]: Could not launch Spot Instances. UnfulfillableCapacity - Unable to fulfill capacity due to your request configuration. Please adjust your request and try again. Launching EC2 instance failed.

But that error was updated about a 1 year ago and the node group doesn't exist anymore. I can't access to the cluster... so, how I fix this?

Well, I fixed the error using:
kubectl edit --subresource=status cluster -n fleet-default CLUSTERID
And removing the condition :)


Adding EPEVER inverter to influxdata

I have a SolarThing setup running with much joy on a raspberry pi 3B+ running influxdb, telegraf and grafana
Really like this project, thanks and compliments
I have a EPEVER Tracer and EPEVER inverter connected on the same RS485 cable. How can I readout data from the inverter? Is there a place to configure which fields are expected as data from the inverter as it also reads out the tracer data fields or do I only have to find the channel the inverter is on and what type should I use in the base.json? My tracer is on channel 1 (device 1)
Sorry for all questions, I'm reading all documentation and reallyt trying to find how to set this up but cannot find it
Thanks again for all efforts making this awesome software
Maikel

SolarThing currently does not support EPEVER Inverters. SolarThing also does not have support for configuring fields to read from unsupported devices such as EPEVER Inverters.
I also want to stress that you will not be able to use another program that supports monitoring your inverter unless you connect two different RS485 adapters to your Raspberry Pi (and also make sure the two RS485 lines are separate). Whatever program uses your RS485 adapter to read from one or both of your devices will not allow that serial port to be used by other applications. I say this because if not being able to monitor your inverter is a deal breaker for whether or not you use SolarThing, you should find a different program that supports the monitoring of both at the same time. As much as I'd love to add support for an EPEVER Inverter, I don't have an EPEVER Inverter and am not willing to sink time into getting support for something I will not use. If you are set on being able to monitor both devices, I think using a Python library would be your best bet. There are some Python libraries out there for monitoring EPEVER Tracer units. As much as I don't want to link you away from SolarThing this library might help: https://github.com/fatyogi/epever-upower-tracer. I can't comment on how well that will work since I've never used it. There are also numerous other repos that support the EPEVER tracer, but finding ones like that that also support your inverter might be difficult. You might be able to mix and match Python libraries for monitoring your devices as long as both Python libraries you choose use the same modbus library (minimal modbus for instance). If that's the case then you might be able to get them to work together with the same serial port connection. All this, of course, requires some tinkering with Python, which may or may not be what you want to do.
Sorry I threw a lot of information at you. Just want to give you all the options. Sorry I don't have a better answer for you.

SolarThing currently does not support EPEVER Inverters. SolarThing also does not have support for configuring fields to read from unsupported devices such as EPEVER Inverters.
I also want to stress that you will not be able to use another program that supports monitoring your inverter unless you connect two different RS485 adapters to your Raspberry Pi (and also make sure the two RS485 lines are separate). Whatever program uses your RS485 adapter to read from one or both of your devices will not allow that serial port to be used by other applications. I say this because if not being able to monitor your inverter is a deal breaker for whether or not you use SolarThing, you should find a different program that supports the monitoring of both at the same time. As much as I'd love to add support for an EPEVER Inverter, I don't have an EPEVER Inverter and am not willing to sink time into getting support for something I will not use. If you are set on being able to monitor both devices, I think using a Python library would be your best bet. There are some Python libraries out there for monitoring EPEVER Tracer units. As much as I don't want to link you away from SolarThing this library might help: https://github.com/fatyogi/epever-upower-tracer. I can't comment on how well that will work since I've never used it. There are also numerous other repos that support the EPEVER tracer, but finding ones like that that also support your inverter might be difficult. You might be able to mix and match Python libraries for monitoring your devices as long as both Python libraries you choose use the same modbus library (minimal modbus for instance). If that's the case then you might be able to get them to work together with the same serial port connection. All this, of course, requires some tinkering with Python, which may or may not be what you want to do.
Sorry I threw a lot of information at you. Just want to give you all the options. Sorry I don't have a better answer for you.

Thanks a lot, not the answer I wanted to hear haha but fully understandable. I will explore the link and information you've given me. Thanks for your reply

You can probably still use SolarThing and use something else to monitor your inverter, but you would definitely have to have two RS485 adapters. Also, there's a chance that it's possible to have 2 RS485 adapters connected to the same bus, both as masters, but I wouldn't put money on it. I'm not familiar enough with RS485 to tell you whether or not its possible, but this is relevant: https://electronics.stackexchange.com/questions/451684/rs-485-network-with-multiple-masters. I believe RS485 is designed in a way that allows multiple devices to send data on the same line as long as it is not at the same time.
Alternatively, like I said earlier, you can separate your tracer and inverter so that their RS485 line are not connected and then give each device its own RS485 adapter. Although I assume you don't want to do that as it's common for inverters/charge controllers sharing the same serial communication to also share data such as battery temperature so you only need one temperature sensor.

You can probably still use SolarThing and use something else to monitor your inverter, but you would definitely have to have two RS485 adapters. Also, there's a chance that it's possible to have 2 RS485 adapters connected to the same bus, both as masters, but I wouldn't put money on it. I'm not familiar enough with RS485 to tell you whether or not its possible, but this is relevant: https://electronics.stackexchange.com/questions/451684/rs-485-network-with-multiple-masters. I believe RS485 is designed in a way that allows multiple devices to send data on the same line as long as it is not at the same time.
Alternatively, like I said earlier, you can separate your tracer and inverter so that their RS485 line are not connected and then give each device its own RS485 adapter. Although I assume you don't want to do that as it's common for inverters/charge controllers sharing the same serial communication to also share data such as battery temperature so you only need one temperature sensor.

Thanks, I just read your reply now.
In the mean time I found some options to get the inverter implemented with different scripts and RS485 adapter.
Now what I was wondering; because the inverter communicates on the same bus with a different device ID and with different data fields, is it possible to edit one or more files in the SolarThing configuration to implement these data fields? That would be so much better because its much more reliable and I'm happy to share all information that I find out.
If it's possible could you give me a short fly-over how SolarThing reads the data from the RS485 adapter? Or give me some locations and file names, I'll try to find out myself once I have some leads.
If that's really not possible, then that's ok but I figured "Not asked is no chance anyway"

is it possible to edit one or more files in the SolarThing configuration to implement these data fields?

Yeah it's definitely possible. Just not something I'm willing to work on at the moment. If you want to mess with it to get it working I'll try to point you in the right direction. Note that the structure of the project is much larger and more difficult to understand than most simple Python scripts that are out there. I've been meaning to write documentation for the overall structure of the project, but it seems I'm behind on writing documentation for some of the normal use cases anyway.
First I'll focus on how I read data from the rover. I'm going to have perma links for f818a11f7d5ef3e62d99550d95899ef0bf907ec6 as that is the latest commit on master at the moment. RoverModbusSlaveRead.java is the class that has much of the logic for doing the reading of particular registers. Notice this class implements RoverReadTable. RoverReadTable is also implemented by ImmutableRoverStatusPacket which is a concrete implementation of RoverStatusPacket. This particular structure allows me to use RoverStatusPackets#createFromReadTable() to read from a RoverReadTable implementation and create a RoverStatusPacket. I end up passing a RoverModbusSlaveRead to that method and that's where all of the reading takes place. The tracer code also has similar classes.
Now that's at a pretty high level. Notice that all of those classes are in the core module. The logic to actually call these methods exists in the client module, which is the module that contains most of the logic to make solarthing.jar work. The client module contains configuration and logic to correctly setup PacketListReceivers. The ModbusDataRequester class is one of the objects created directly from the configuration. Notice that ModbusRequester currently has two subtypes: RoverModbusRequester and TracerModbusRequester. Note that both of those classes have logic to tell the modbus stuff what registers it can perform bulk requests on, so there is a lot of code in there that is for performance and isn't necessary to understand what is actually happening.
Should you decide to try to implement a EpeverModbusRequester, you can base it off of TracerModbusRequester. It's quite a lot of code to understand and most people that use SolarThing don't have much Java experience so I rarely get contributors.

is it possible to edit one or more files in the SolarThing configuration to implement these data fields?

Yeah it's definitely possible. Just not something I'm willing to work on at the moment. If you want to mess with it to get it working I'll try to point you in the right direction. Note that the structure of the project is much larger and more difficult to understand than most simple Python scripts that are out there. I've been meaning to write documentation for the overall structure of the project, but it seems I'm behind on writing documentation for some of the normal use cases anyway.
First I'll focus on how I read data from the rover. I'm going to have perma links for f818a11 as that is the latest commit on master at the moment. RoverModbusSlaveRead.java is the class that has much of the logic for doing the reading of particular registers. Notice this class implements RoverReadTable. RoverReadTable is also implemented by ImmutableRoverStatusPacket which is a concrete implementation of RoverStatusPacket. This particular structure allows me to use RoverStatusPackets#createFromReadTable() to read from a RoverReadTable implementation and create a RoverStatusPacket. I end up passing a RoverModbusSlaveRead to that method and that's where all of the reading takes place. The tracer code also has similar classes (I meant to put in links for the tracer classes but ended up doing the rover classes. Should give you a good idea either way no matter which one you look at)
Now that's at a pretty high level. Notice that all of those classes are in the core module. The logic to actually call these methods exists in the client module, which is the module that contains most of the logic to make solarthing.jar work. The client module contains configuration and logic to correctly setup PacketListReceivers. The ModbusDataRequester class is one of the objects created directly from the configuration. Notice that ModbusRequester currently has two subtypes: RoverModbusRequester and TracerModbusRequester. Note that both of those classes have logic to tell the modbus stuff what registers it can perform bulk requests on, so there is a lot of code in there that is for performance and isn't necessary to understand what is actually happening.
Should you decide to try to implement a EpeverModbusRequester, you can base it off of TracerModbusRequester. It's quite a lot of code to understand and most people that use SolarThing don't have much Java experience so I rarely get contributors.

Thanks a LOT, I'll read through all this and if I decide to write something myself I'll at least let you know.
So great you respond so quickly (quicker than me haha) and throughly, much apreciated, your whole project here on GitHub actually is.

Feel free to reopen this issue if you are going to look into this more. I will close this for now but can also reopen it if you would like me to add the help wanted tag.


pip-compile cannot compile elyra-python-editor-extension

Describe the issue
Dependencies for elyra-python-editor-extension package cannot be generated with pip-compile.
To Reproduce
Create a requirements.in with the following content:
elyra-python-editor-extension==3.12.0

Run the pip-compile tool:
$ pip-compile --generate-hashes requirements.in
Could not find a version that matches pycodestyle<2.9.0,>=2.8.0,>=2.9.1 (from autopep8==1.7.0->elyra-server==3.12.0->elyra-python-editor-extension==3.12.0->-r requirements.in (line 1))
Tried: 2.0.0, 2.0.0, 2.1.0, 2.1.0, 2.2.0, 2.2.0, 2.3.0, 2.3.0, 2.3.1, 2.3.1, 2.4.0, 2.4.0, 2.5.0, 2.5.0, 2.6.0, 2.6.0, 2.7.0, 2.7.0, 2.8.0, 2.8.0, 2.9.0, 2.9.0, 2.9.1, 2.9.1
Skipped pre-versions: 1.8.0.dev0, 1.8.0.dev0, 2.0.0a1, 2.0.0a1, 2.6.0a1, 2.6.0a1
There are incompatible versions in the resolved dependencies:
  pycodestyle>=2.9.1 (from autopep8==1.7.0->elyra-server==3.12.0->elyra-python-editor-extension==3.12.0->-r requirements.in (line 1))
  pycodestyle<2.9.0,>=2.8.0 (from python-lsp-server[all]==1.5.0->elyra-server==3.12.0->elyra-python-editor-extension==3.12.0->-r requirements.in (line 1))

Expected behavior
Do not return an error.
Deployment information
Describe what you've deployed and how:

Python version 3.8.13
pip-compile version 6.8.0

@samuelvl - we are transitioning to using the pyproject.toml and updating dependencies as needed. I noted several issues when generating the requirements lockfile with pip-compile using this new format including this issue, but they seem to have been resolved. See https://github.com/elyra-ai/elyra/pull/3041

Duplicate or will be resolved by #3041


Wait for all slave dirs to be completely removed before leaving clean…

es.initialize was failing due to "file in use" errors. Included while loop to prevent moving on until all slave directories were completely removed.

Coverage decreased (-0.06%) to 78.305% when pulling a8d7ac3a5be1460d3d2c5062f3d4108ce5947207 on rm_tree into 36cb68cb429495482035dbb17a3bbaddb9d89e27 on develop.


update readme

update readme with new instructions and videos
remove yarn
update packages

will leave links in for now


[E2E] New E2E test for Input Bindings that do not depend on Kafka

In what area(s)?
/area test-and-release
Describe the feature
Bindings test depend on Kafka. @yaron2 proposed us to have a E2E test that does not depend on Kafka for bindings - so tests are more stable.

Test with Kafka is now stable. No action no longer needed


Attribute list on samples/all attributes seems messed up.

@carlkesselman commented on Thu Oct 06 2016
See https://dev.gpcrconsortium.org/chaise/search/#1/experiments:sample select all attributes:

@hongsudt commented on Fri Nov 04 2016
@svoinea please fix this styling issue.. We see the same problem on multi-cellline entries.

@svoinea what's the status on this? Please work with @howdyjessie to fix the styling problem.

This is an old issue that seems to have been fixed.
I have attached the screenshot on how it looks today on my Firefox browser.


docs(api): improve module-methods.md

Why do you find this necessary?

Why do you find this necessary?

When I was going through this first time, it was not appearing to be implicit. That's why to improve readability, I think this change is required.

Hmm the context seems there, like pretty much highlighted. I think this addition makes it a bit weird. Any more thoughts?

Closing due to age.


NIFI-12339 Fix Property Decryption for Migrated Components

Summary
NIFI-12339 Resolves recursive sensitive property encryption issues on the main branch, introduced with changes for handling migration of properties in NIFI-12301. The problem was the result of passing encrypted property values to migration methods, which subsequently resulted in encrypting a value that was already encrypted.
The resolution decrypts original property values prior to registering created extensions so that subsequent property migration methods have access to the decrypted property values.
The resolution can be verified using the InvokeHTTP Processor and creating a sensitive dynamic property named Authorization. After creating the property with an arbitrary value, restarting NiFi maintains the same length for the encrypted string in flow.json.gz, as opposed to growing the encrypted string length after each restart operation. New test methods for the Versioned Component Synchronizer also verify that migration methods for Processors receive decrypted values.
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[X] Apache NiFi Jira issue created

Pull Request Tracking

[X] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[X] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[X] Pull Request based on current revision of the main branch
[X] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[X] Build completed using mvn clean install -P contrib-check

[X] JDK 21

Licensing

[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[ ] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[ ] Documentation formatting appears as expected in rendered files

Thanks for fixing @exceptionfactory . The approach seems to be good. Code looks good to me. +1 will merge.


php artisan route:list error

when running "php artisan route:list"
I get the following error:
[ReflectionException]
Class App\Http\Controllers\API\AuthController does not exist
It only happen to the API route, scaffold routes are not affected. Apart from that, everything works well!

Did you create this controller using laravel-api-generator?

Oh wait, I realize it was a bug on my end. Will close this issue now. Thanks


Final Styling

@Tmotaleb @davidhk21 @jxhncxmpbxll Feel free to look over some of this pull request OR past pulls. Probably the most room for improvement is in CSS but that's by nature VERY messy. The rest of the code is pretty clean, but let me know if you notice anything!


fix: Improve pydantic version checking

Pull Request Checklist

[ ] New code has 100% test coverage
[ ] (If applicable) The prose documentation has been updated to reflect the changes introduced by this PR
[ ] (If applicable) The reference documentation has been updated to reflect the changes introduced by this PR
[x] Pre-Commit Checks were ran and passed
[ ] Tests were ran and passed

Description

This PR aims to improve the pydantic contrib's version checking to avoid breakage.
Close Issue(s)

2672

Thanks for this!


Decrypt base64

Sometimes my friend sends me messages in base64, can we have a plugin that decrypts it on the fly?  Can you please give intelligent criticism?

It's bad. We don't want it. Can you please give an intelligent reason as to why we'd want this?

 If you actually did what you said, you would know this.
Stop making issues you have not actually thought about. Some of your suggestions are good, but a whole load of them are obviously not possible and/or entirely useless.

Some of your suggestions are good, but a whole load of them are obviously not possible and/or entirely useless.
Sorry I will try not to disappoint you on my next one.

I have been trying to find a solution and came across this: http://anvyst.com/2016/10/base32-advantages-over-base64/
This can prevent big brother reading our in-game messages unless they have the runelite base32 plugin

I've been thinking for a while and was wondering if we could have a pastebin runelite plugin that we can communicate within the text? for example I would send jCKdgSrG to someone on runelite. they would click it and it would redirect to https://pastebin.com/jCKdgSrG
After someone has clicked that link, read it once it will be burnt so no-one can read it again then they will create a pastebin to reply

I've been thinking for a while and was wondering if we could have a pastebin runelite plugin that we can communicate within the text? for example I would send jCKdgSrG to someone on runelite. they would click it and it would redirect to https://pastebin.com/jCKdgSrG
After someone has clicked that link, read it once it will be burnt so no-one can read it again then they will create a pastebin to reply


[Navigation Material] Bottom sheets opened via a deeplink open above a black screen, popping back stack results in a black screen

Description
When opening a deeplink that contains a bottom sheet destination, that destination is opened above a blank screen.

Closing the bottom sheet using "Back" button redirects to the root of the nav graph
Closing the bottom sheet using a gesture results in a permanent black screen until relaunch

Steps to reproduce

Open a deeplink that points to the bottom sheet destination using Action.VIEW intent
Bottom sheet opens above a black screen
Close the bottom sheet using a gesture
You are stuck on a blank screen

Expected behavior
A deeplink pointing to a bottom sheet destination is opened above a root navgraph destination. Back stack is populated with it and navigating using both buttons and swipes is supported
Additional context
Initially reported in https://github.com/raamcosta/compose-destinations/issues/396
Accompanist navigation v 0.31.0 alpha

I don't, but I plan to create one soon as I start investigating this


Kafka topics error

Good morning,
I'm trying to send 2 custom events to kafka; the idea is send each event to its topic; but at the moment I receive both events in both topics.
I have configured 2 mappings with different schemas and 2 sinks (one for each mapping). What I exactly need is to map my custom events to a specific kafka topic.
I don't know what is exactly happening, do you hace any idea?
Thanks !
Manu

I'm having this same exact issue. Sad that this repo isn't being maintained :(


Importing a css file in _app.js may cause Cannot read property 'default' of undefined

<EMAIL_ADDRESS><EMAIL_ADDRESS>
I started seeing a pretty magic bug in production recently and am writing to share the results of my investigation. Here's what was showing up in the browser's console during some of the page loads:
TypeError: Cannot read property 'default' of undefined
    at http://localhost:3000/_next/static/bc4f7954-f656-4e9e-af24-a4404cecb3c7/pages/_app.js:1:4762
    at r (http://localhost:3000/_next/static/runtime/main-68ba217b0c0184534eba.js:9:96586)
    at e.value (http://localhost:3000/_next/static/runtime/main-68ba217b0c0184534eba.js:9:96973)
    at http://localhost:3000/_next/static/runtime/main-68ba217b0c0184534eba.js:1:1034
    at Array.forEach (<anonymous>)
    at Object.110 (http://localhost:3000/_next/static/runtime/main-68ba217b0c0184534eba.js:1:991)
    at l (http://localhost:3000/_next/static/runtime/webpack-7dba61e9b6510e660c00.js:1:520)
    at Object.105 (http://localhost:3000/_next/static/runtime/main-68ba217b0c0184534eba.js:1:156)
    at l (http://localhost:3000/_next/static/runtime/webpack-7dba61e9b6510e660c00.js:1:520)
    at Object.104 (http://localhost:3000/_next/static/runtime/main-68ba217b0c0184534eba.js:1:103)

This was followed by no JavaScript working on the client. However, if the exception was somehow avoided on the first page load, all subsequent Next.js pages were working well as long as they were loaded dynamically via <Link/>. The same exception never showed up in development.
After removing pretty much any bit from my app (😅) and testing various hypotheses, I was able to craft an MWE where the exception was reproduced pretty stably. All you need to do is to install next-css, create pages/_app.js and import a CSS file there:
import App, { Container } from "next/app";
import React from "react";

import "../styles/index.css"; // 😱

export default class MyApp extends App {
  render() {
    const { Component, pageProps } = this.props;
    return (
      <Container>
        <Component {...pageProps} />
      </Container>
    );
  }
}

Interestingly, the exception was only occurring in Chrome and not Firefox and could disappear when I varied the size and the complexity of a page. However, with pages/index.jsx being just export default () =>
hello
; the exception appeared every time.
Here's how adding import "../styles/index.css"; to _app.jsx affects the HTML in production:
 <!DOCTYPE html>

   <meta charSet="utf-8" class="next-head" />
   <link rel="preload" href="/_next/static/HASH/pages/index.js" as="script" />
   <link rel="preload" href="/_next/static/HASH/pages/_app.js" as="script" />
   <link rel="preload" href="/_next/static/HASH/pages/_error.js" as="script" />
   <link rel="preload" href="/_next/static/runtime/webpack-HASH.js" as="script" />
   <link rel="preload" href="/_next/static/chunks/HASH.js" as="script" />
   <link rel="preload" href="/_next/static/runtime/main-HASH.js" as="script" />
+  <link rel="preload" href="/_next/static/chunks/HASH.js" as="script" />
+  <link rel="stylesheet" href="/_next/static/css/styles.HASH.chunk.css" />

hello

+

As you can see, importing a stylesheet in _app.js not just adds a link to a CSS file, but also produces a new JS chunk. This JS file does not contain anything really:
(window.webpackJsonp=window.webpackJsonp||[]).push([[6],{220:function(n,w,o){}}]);

/_next/static/HASH/pages/_app.js changes a bit too and my suspicion is that it is trying to import a module from the extra JS chunk before that one is loaded. This race condition does not happen on any page because the size of its server-rendered content may affect the order in which Chrome loads the JS files and bootstraps the client-side app.
Getting rid of the bug was pretty simple. I just moved the CSS import into the page HOC in my real app (pages/index.js in the MWE) and the exception never showed up again.
What can we do to save others from the same trap? It took me more than half a day to detect the bug and to investigate it 😅

Hi
Facing the same issue here.
index.js:2178 Error was not caught TypeError: Cannot read property 'default' of undefined
    at external "dll_919418fa44275dfcfdb1":1
    at register (page-loader.js:124)
    at PageLoader.registerPage (page-loader.js:162)
    at index.js:82
    at Array.forEach (<anonymous>)
    at Object../node_modules/next/dist/client/index.js (index.js:79)
    at __webpack_require__ (bootstrap:789)
    at fn (bootstrap:150)
    at Object../node_modules/next/dist/client/next-dev.js (next-dev.js:7)
    at __webpack_require__ (bootstrap:789)

Using:
"next": "^7.0.0-canary.7",
"@zeit/next-css": "^0.2.1-canary.2",
"@zeit/next-sass": "^0.2.1-canary.2",
"next-optimized-images": "^1.4.1",

OS: Ubuntu 18.04
Crashed in Chrome (Version 68.0.3440.84)
Works in Firefox (61.0.1)
next.config.js
const withOptimizedImages = require('next-optimized-images');
const withCSS = require('@zeit/next-css');
const withSass = require('@zeit/next-sass');

module.exports = withSass(
  withCSS(
    withOptimizedImages({
      webpack: (config) => {
        // Fixes npm packages that depend on `fs` module
        // eslint-disable-next-line no-param-reassign
        config.node = {
          fs: 'empty',
        };

        return config;
      },
    }),
  ),
);

_app.js
import React from 'react';
import App, { Container } from 'next/app';

import 'react-dates/initialize';
import 'react-dates/lib/css/_datepicker.css'; //Crashed here

import '../assets/ff-bootstrap.scss'; //Crashed here (if above line commented)

import Head from '../components/Head';
import initFontAwesome from '../fe-utils/init-font-awesome';

initFontAwesome();

export default class MyApp extends App {
  static async getInitialProps({ Component, ctx }) {
    let pageProps = {};

    if (Component.getInitialProps) {
      pageProps = await Component.getInitialProps(ctx);
    }

    return { pageProps };
  }

  render() {
    const { Component, pageProps } = this.props;
    return (
      <Container>

        <Component {...pageProps} />
      </Container>
    );
  }
}

+1
Happening mac chrome too.

I can confirm that as well, firefox works, chrome fail. Console is clean so its only browser issue!

Confirming as well but for sass.

Going to debug this in the morning.

This issue will be fixed when #5115 lands. Thanks for the clear minimal reproduction @kachkaev, it's now part of the Next.js test suite 👍:pray:


RealmSwift: Module compiled with Swift 4.0 cannot be imported by the Swift 4.2 compiler

Build error between RealmSwift and Swift compiler 4.2:
/Users/user146094/SwiftyPress/Sources/Controllers/PostDetailViewController.swift:14:8: Module compiled with Swift 4.0 cannot be imported by the Swift 4.2 compiler: /Users/user146094/SwiftyPress/Frameworks/realm-swift/ios/RealmSwift.framework/Modules/RealmSwift.swiftmodule/x86_64.swiftmodule

clean_arch is working.


Dashboard to generate a working manifest?

Describe the enhancement you'd like to see
Currently when an API is updated/created through the dashboard, the user loses sync between the configuration that is deployed to the cluster and the configuration saved in Github for example. This means that the users loses "the source of truth" when they use the dashboard...
Suggested solution is that the dashboard should not deploy the API, but just generate the openapi.yaml/openapi.json file needed to configure Kusk Gateway. It is then the developer team's job to keep that file in sync.
Additional context
This is a solution that I observed from Krakend, where they have a public page to design their Gateway's configuration https://designer.krakend.io/#!/

good point @aabedraba - the initial idea of this functionality was to make it easy for users to "try out" KGW with an existing OpenAPI definition - you're totally right that it moves away from the intended automated/design-first workflow - which is perhaps something we should call out in the UI in line with your suggestion. I'm also wondering if we could create some kind of "automation wizard" that sets up automatic deployment from a github repo (for example) - without requiring the user to install Argo/Flux/etc!?


--retries  doesn't work

I use following, case failed but doesn't retry, it there something wrong? Or I use the wrong way.
mocha  --retries 2 casename.spec.js

which version of mocha are you using? the retries are working fine, try this code snippet for example:
let counter = 0;
describe('lol', function() {
  it('lols', function() {
    if(counter > 1) {
      console.log('counter::', counter) //logs 3
    } else {
      throw new Error(++counter)
    }
  })
})


Version selector note missing - New-MgGroupMember

The version selector for the command New-MgGroupMember is missing.
Sample Cmdlets:
New-MgGroupMember
Note: Not very common though.

Expectation:

Hi @SteveMutungi254 - due to the planned migration from GitHub issues to UUF, we are in the process of closing all open GH issues. For those that we would like to follow up in future, we'll create ADO work items to track them and close the GH issue.
Since this issue is still open, could you open a work item to Timothy?

ADO work item created to track this.
259508	User Story	[Issue]Version selector note missing - New-MgGroupMember	Eunice Waweru<EMAIL_ADDRESS>New


Double indexes

Hello,
first of all... good job!
I notices a bug. If you go to your demo page:
https://symfony-collection.fuz.org/symfony3/
Inspect 'Orange' input, you will see it has ID 'withPlugin_fruits_2_name'
Now, do the following:

add fruit (from 'Orange' line input)
remove newly added fruit
add fruit (from 'Orange' line input)
add fruit (from newly created fruit line)

You will notice, the last two of them have ID 'withPlugin_fruits_4_name'. If you add another fruit, the next one will have ID 'withPlugin_fruits_5_name', which is OK.
Any help around this? In my example, I have tinyMCE to initialize, but it does not because of two identical ID's of textarea.
Edit:
The same problem is with nested children:
https://symfony-collection.fuz.org/symfony3/advanced/collectionOfCollections

Hey there!
Thank you, I'm not available until tomorrow night but I'll have a look soon enough.
Have a good day,
Alain

Hey there,
Yeah that's easy to reproduce, thanks for your report.
You can get rid of this issue by disabling fade_in and fade_out options.
Alain

fade_in and fade_out are a nightmare with many edge cases, it will be IMO more productive to remove them.

Hey,
thanks for the quick reply!
Do you perhaps know when you will have time to fix it?

Well, I'll be quite busy this week (even the weekend), but everything should go smoother after.
Just disable fade_in and fade_out options (they are enabled by default) and you'll be good to go.
Cheers

Hello,
I just tried to disable fade_in and fade_out, but that didn't resolved the issue. I disabled it at parent level, and also at child level.
The animation went away, but there is still problem with double indexes.

Okey. Will try to find some time to check/fix it quickly.

later is better than never... on it now 😅

all right, found it, the last-index was wrongly initialized, fix onging

Thank you, it works :)


Point features may now be coalesced into MultiPoint features with --coalesce

@ericfischer check this out if you need a super-fast implementation of the Hilbert 2D functions — might make it easier to turn on the option as the default. I'm using the code happily in https://github.com/mourner/flatbush

Thanks @mourner! I'll check it out.
My reluctance isn't so much about speed as about the fact that it changes every single test output, because z-order has been so deeply ingrained in Tippecanoe for so long. When everything changes, it's hard to tell the difference between the intentional differences and the accidental differences.


event publish and consumed

When the buffsize is full, why do consumers re-publish each time the event in the ringbuffer is consumed. Why not design an event for consumers to consume an event.

Sorry I don't really understand the question that you are asking.  Could you perhaps phrase is differently or provide an example?

No response, so closing.


Is there a random_values that sets pwm leds to 0.0-1.0 or could this be added?

I got the 3D X-mas tree from PiHut and wanted some lights to turn of temporarily.  random_values() never gave a 0 for led.source.  I looked the source for random_values and created a different solution:
from random import randint
...
while True:
    yield randint(0,10)/10

Is there another way to do this or could this be added?

I think https://gpiozero.readthedocs.io/en/stable/api_tools.html#gpiozero.tools.quantized might do what you're after?

What would I supply for values?  There is no other input device.  Just outputting values to LEDs.  I wanted to create a generator that outputs random numbers 0.0 – 1.0 including both 0.0 and 1.0.  led.source takes a generator, but I think quantized needs some kind of input set under values in the constructor?
def quantized(values, steps, input_min=0, input_max=1):

From: Andrew Scheller<EMAIL_ADDRESS>Sent: Saturday, December 2, 2017 9:43:23 PM
To: RPi-Distro/python-gpiozero
Cc: sjd4; Author
Subject: Re: [RPi-Distro/python-gpiozero] Is there a random_values that sets pwm leds to 0.0-1.0 or could this be added? (#611)
I think https://gpiozero.readthedocs.io/en/stable/api_tools.html#gpiozero.tools.quantized might do what you're after?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/RPi-Distro/python-gpiozero/issues/611#issuecomment-348736013, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AYmwojHdtQLW9-89wPJfuOYBJQte4tqGks5s8grKgaJpZM4Qy1IU.

Well, technically the random_values does output both 0.0 and 1.0 - it's just very unlikely to output those exact values, much as it's very unlikely to output exactly 0.50000000.
The sourcetools are designed so that they can be 'chained' together (see https://gpiozero.readthedocs.io/en/stable/source_values.html , although I now see it doesn't show chaining multiple sourcetools @bennuttall ). In your case you'd want to do:
led.source = quantized(random_values(), 10)

which should give you a random value from the list (0.0, 0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 1.0)
Although I've not tested this myself, so I can't say for certain whether both 0.0 and 1.0 will actually be included in the output.
@waveform80 I wonder if it'd be worth add a quantized_random_values sourcetool that better provides the behaviour that @sjd4 is expecting?

@lurch Yes, that works!

@lurch  It worked for me too!  This works fine.  If the devs think it's worth making a quantized_random_values() the feature gets my vote.  Either way this issue is resolved.

Oh cool! I wasn't sure if it'd round-down (in which case 1.0 wouldn't be included in the output) or if it would round-up (in which case 0.0 wouldn't be included) - but if it works as expected, that's great to hear :-)
@bennuttall Maybe this'd make a good example for the docs?

I just checked and it does round-down.  It never outputs 1.0.
It would definitely make a good example for the docs.  I didn't understand that the values variable in the quantized constructor was a generator.

btw, you can get quantized to include 1.0, by changing the quantized call like such: instead of quantized(random_values(), n) use quantized(random_values(), n-1, input_max=1-1/n).  This makes it such that the 1.0 bucket has an equal chance of being selected as the other ones.


Implement form components

All the form components

Time taken
Estimated - 2 hours
Realized - 1 hour 57 minutes


database location & persistence suggestion

As database from new installation doesn't exist, diskover will create one after setup at /web/root/diskoverdb.sqlite3 or manually touch first. My suggestion is move diskoverdb.sqlite3 to it own directory like /web/root/database/diskoverdb.sqlite3. My reason is on docker installation web root mostly wiped and replaced new, with usage of database dir db stored it own directory then we can use database/ volume mount instead of mount/linking database directly.
Hacky way:
volumes:
  ./diskoverdb.sqlite3:/web/root/diskoverdb.sqlite3

or like this pull https://github.com/linuxserver/docker-diskover/pull/51
if [[ ! -e "/config/diskoverdb.sqlite3" ]]; then
    touch /config/diskoverdb.sqlite3
fi
ln -sf /config/diskoverdb.sqlite3 /app/www/diskoverdb.sqlite3

Prefered way:
volumes:
  ./database:/web/root/database

rc5 has a new DATABASE config setting to set the database path


Is remove worked right?

init Phoenix with complex selector:
$('#form1,#form2').find('input,textarea,select').phoenix({
		namespace: 'mySpace',
		maxItems: 250,
		saveInterval: 5000
	 });

but when I try to remove storage data it's not worked —
$('#form1,#form2').find('input,textarea,select').phoenix('remove'); // this not worked

because Phoenix tries to remove from default nameSpace phoenixStorage.

Please, fix it.

I have the same issue - phoenix breaks when the default options are overridden. It works fine if you just use the defaults.

+1

We had the same problem and solved it (workaround?) by expanding this line:
     if (typeof option === "string") {
        this.action = option;
      }

Into this:
     if (typeof option === "string") {
        this.action = option;
      }else{
          this.action = option.action;
      }

After that you need to define "action" not as string "remove", but as an object:
$(".selector").phoenix({ namespace: "test", "action": "remove" });
You can still use
$(".selector").phoenix('remove');
But that will use the default namespace (phoenixStorage).
Hope it helps...


Fix recycler splicing at beginning/end

To whom it "may" concern (@dlasky @anthonykoerber @shuwen ), this should fix the splice issues some have observed (and a couple that have yet to be observed).

👍


Service export in index.ts incorrect when 2 components deep

Please provide us with the following information:

OS?  Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
Windows 7

Versions. Please run ng --version. If there's nothing outputted, please run
in a Terminal: node --version and paste the result here:
angular-cli: 1.0.0-beta.10
node: 6.2.2
os: win32 x64

Repro steps. Was this an app that wasn't created using the CLI? What change did you
do on your code? etc.
ng g component myTest
ng g component my-test/mySettings
ng g service my-test/my-settings/shared/mySettings

The log given by the failure. Normally this include a stack trace and some
more information.
no error returned from CLI

Mention any other details that might be useful.
The exports in the index.ts file at the service level (src/app/my-test/my-settings/shared/index.ts) exports the incorrect file. It should be:
export * from './my-settings.service'
but instead is:
export * from './mySettings.service'

Thanks! We'll be in touch soon.

same issue when service in myTest component's shared folder:
ng g service my-test/shared/mySettings

Definitely a bug, related to https://github.com/angular/angular-cli/issues/1434

This should be closed, as mentioned by @filipesilva in #1434


removed versions from requirements.txt file

Description
removed versions from requirements.txt file
Related Issues
NA
Todos
NA

Closed due to a duplicate PR.


Yadda Part 2 & 3 v1

Based on feedback from Part 1, I added the beer styles look up table and removed extraneous date column from the ratings table.

All of the factories can be defined in a single file. There's no need to split out the factories into different files.

@ssapra Looks good. It would be nice for the views if they included the beer name or the brewery name instead of just the ids. Most of the times views are created for the benefit of the user and it'll be more helpful for a person to be able to read names instead of just id numbers. You can go ahead with part 4.
Also make some changes to the yadda_generator. I'm not sure but I think the create_list function will at least speed up the creation of multiple entries. Though I'll be honest I've never seen anyone before use FactoryGirl for this exercise. The PG gem itself is very fast for adding entries.

@ssapra Nice work on this exercise. As Franco said, you're good to move on to Part 4.


[BotBuilder-AI] Add custom Luis client

Fixes #
Description
We created a custom Luis client that not depends on @azure/ms-rest. We used OpenApi Generator to create a base client from using the Luis API definition. Then we modified it to make compliance with the current implementation of Luis Recognizer in the library.
Specific Changes

Create a custom Luis runtime client
Replace the @azure/congnitiveservice-luis-runtime client
Remove the @azure dependencies from the BotBuilder-AI library
Update the LuisRecognizer and LuisSdk tests to make it pass using the custom Luis client

Testing
The next image shows the result of the local tests.

Aso, this one shows the result of running the test in a custom build pipeline.

that not depends -> that does not depend
make compliance -> make it compliant
 Luis Recognizer in the library. ->  Luis Recognizer.
make it pass -> make them pass

that not depends -> that does not depend
make compliance -> make it compliant
 Luis Recognizer in the library. ->  Luis Recognizer.
make it pass -> make them pass

Feedback applied.


FR: editing or deleting messages could show a button to "restart" the generation

Hi,
Since the last few releases we can now edit and delete messages, this is absolutely awesome and really offers flexibility.
But we can't send an empty message so if I delete the last 2 message for example there's no way for me to restart the generation from that point, unless I copy the now last message, delete it, paste it, then press enter.
I think it might be worth adding a "Ask again" or "Restart generation" button (that would appear for example bellow the last message of the conversation or as a floating button) IF the user modified the message history (either deleted or edited a message).
I think I've seen this feature at some point in the official webUI of ChatGPT? I can't remember exactly.

Now you will see the retry button on the last assistant message. If you click it, last assistant message will be replaced with a new generated text.


Add extra description for beginner contributors

Added extra description for beginner contributors. Also fixed some typos. I was thinking of making the tone of the docs more friendly.

Hello @GeorgLink I have committed the suggested changes. Apologies for the late response, I was on Easter break.


Feedback for: ucp/installation/license.md

URL: https://docs.docker.com/ucp/installation/license.md
Is there a way to load the license file through API or CLI?
Thanks!

You can bind-mount the license file when running the install command, as specified in the UCP install reference docs.
Next time, please post your questions like these in https://forums.docker.com/.


update poetry.lock

Hi @fnep ,
Thanks for the fast check of my pull request :-)
My initial intention was to just update the poetry.lock so I have less problems building your package for my custom linuxserver alpine docker image.
Is it good with you updating the poetry.lock?
I did a run of my use cases and it looks like everything is still working fine :-)

Sure, this is fine. No problem for me.


Update docs to use references in huggingface.js

Follow up to https://github.com/huggingface/huggingface.js/pull/297

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Add CSV export for Assets

Context
https://trello.com/c/gKdKsd5W
Changes proposed in this pull request
Original CSV sanitiser wasn't actually making CSVs safe (if they're exported into Microsoft Excel) so rewrote that.
Guidance to review

 Admin Bios - Export asset information to file

 Amendment to Admin-BIOS signed in copy

 What is a Hardware hash explainer


[WIP]: Analytics graphs for messages sent:is_bot

Add graph with buttons to switch between daily, weekly, 4weekly, and cumulative data for messages sent by humans and bots.
@rishig

Automated message from Dropbox CLA bot
@amyliu345, it looks like you've already signed the Dropbox CLA. Thanks!

This is obsolete now, right?

yup
On Wed, Feb 1, 2017 at 2:48 PM, Tim Abbott<EMAIL_ADDRESS>wrote:

This is obsolete now, right?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zulip/zulip/pull/3276#issuecomment-276808494, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA2YH1y8NJhbjlbAwAz63uOWCCBmv8uzks5rYQuwgaJpZM4LiZ5s
.


Project: Spotify Clone

Description :
This will be spotify clone with most of spotify's features.
Using html, CSS and React.

Hey, can I work on this issue?

Go ahead @sanskruti-shahu  💯

Hey, can I work on this issue?

Hey, can I work on this issue?

You can look at another issue or make a new issue if you want ...


Sets app to use version 2.1 of the app

Does not impact our use.

v1 is deprecated in June.
https://npiregistry.cms.hhs.gov/registry/help-api

Resolved here > https://github.com/Silversheet/nppes_api/commit/9b0e6a440a8f1c354cc203200ff28066fccd58de


Allow submitting files inline using the CLI

We have inline data submission but there is no way to use this from the CLI, only from the job spec.
We should have a flag on the CLI (like --inputs or --input-urls) that converts a file or directory into an inline spec. Use the InlineStorage type and Upload the file or directory into a spec, then include that spec in the job inputs.

We have inline data submission but there is no way to use this from the CLI, only from the job spec.
We should have a flag on the CLI (like --inputs or --input-urls) that converts a file or directory into an inline spec. Use the InlineStorage type and Upload the file or directory into a spec, then include that spec in the job inputs.

@simonwo please let me know when this is created so the documentation can be updated with this info

Hello, @simonwo would it be alright if I give this issue a shot? I'm new to contributing to open source so apologize if I have questions but I'd be happy to help.

Hello, @simonwo would it be alright if I give this issue a shot? I'm new to contributing to open source so apologize if I have questions but I'd be happy to help.

Hi, yes of course! Please ask any and all questions you've got, and I/we are very happy to discuss ideas about how to implement. You can also join us on Slack channel #bacalhau.
As a place to start, I would look at how flags for the other types of storage are implemented, and think about how you'd do it for this one: https://github.com/filecoin-project/bacalhau/blob/f668fe9e9e254371b937a5c94c4b51690ef943e1/cmd/bacalhau/flags.go#L182-L201

Is it possible for me to have a crack at this as well? If so may you please provide some instructions?

Hi @somya-15, how are you getting on with this? Is there anything we can do to help? Or if you don't really have the time for it, please let us know!

Hi @simonwo, yes I am working on the feature, I have few questions regarding the implementation.

According to the requirements the --input flag must take a path of the file/folder on the user's system. Currently, is a path added to the job spec and the files are getting uploaded to storage spec?
So in my case,
func parsePathStorageSpec(inputPath string) (model.StorageSpec, error) { } would be a function that takes this path and uses the inline package (storage.go file) to convert the file into InlineStorage type.
I am not able to get clarity regarding the requirement "Upload the file or directory into a spec". I am aware that inline package (storage.go file) has the upload method that stores the data into the returned StorageSpec. Will that be a fit for the use case here?
Thank you for your patience while I responded. As a priority, I will work on the feature.
Thanks

Sorry for slowness in replying @somya-15! Great that you're still up for working on it.

Yes, exactly that. Basically you are doing a more general version of what is here.
https://github.com/filecoin-project/bacalhau/blob/83d90f4eed27b633d6c1549ec09f3da06c1b13f1/cmd/bacalhau/wasm_run.go#L209-L214

Yes, that's exactly it. You can just pass the directory to Upload of the inline storage type and that will produce the desired effect.

Let me know if you have any questions!


How to always render the opened menu as the last element in document.body?

Hey @szhsin,
First of all, thanks for this library!
I have a use case where a menu is rendered inside a modal and needs to be rendered on top of it. And, in the other instance, menu option is triggering a modal and then the modal needs to be rendered on top of the menu.
To achieve this, I'm relying on the DOM order of the menu and the modal, trying to avoid z-index wars.
In the first instance, I'd like the menu to be rendered after the modal:
Use case 1 - menu on top of modal (see CodeSandbox below)
  ...

...

...

And, in the second one, the modal to be rendered after the menu:
Use case 2 - modal on top of menu
  ...

...

...

However, as you can see in this CodeSandbox, the szh-menu-container is rendered before the modal, breaking use case 1 above. Why is this happening?
Is there a way to always render the opened menu as the last element in the document.body.

Hi @moroshko ,
The element position within document.body is determined by the rendering order of React components.
export const Modal = ({ onClose, children }) => {
  return createPortal(

        {children}
        <button className="modal-close-button" type="button" onClick={onClose}>
          X
        </button>

,
    document.body
  );
};

In the render method of Modal component,  the parameter of createPortal is evaluated before the function can be called. This causes the rendering of children and the render method of menu component to be called. The menu component invokes createPortal internally and renders szh-menu-container into document.body. Then the call stack returns to the createPortal in the Modal and renders modal-overlay after szh-menu-container in the document.body.
It results in a reversed DOM order of JSX elements in render method and it's a natural result of using createPortal both in the parent and child components.
That being said, the reversed order won't cause an issue when a greater z-index is set on szh-menu-container, because modal and menu are positioned within the same stacking context.
If you still feel strongly about the correct element position within document.body, I find a way to overcome it by setting the children of Modal in an useEffect. One downside is that it will cause an extra render of modal component.  Here is the example: https://codesandbox.io/s/react-menu-728-br7k9r?file=/src/App.js

That being said, the reversed order won't cause an issue when a greater z-index is set on szh-menu-container, because modal and menu are positioned within the same stacking context.

I can't rely on having a greater z-index on szh-menu-container because this will break use case 2 above.
I'm curious, why szh-menu-container is rendered before the menu is opened? If you have a large table, say 1000 rows, where every row has a menu, this results in 1000 szh-menu-containers being rendered, whereas in reality, only one menu can be opened at a time.
Is it possible to append szh-menu-container to the body only when the menu is opened and need to be rendered?

Is it possible to append szh-menu-container to the body only when the menu is opened and need to be rendered?

@moroshko,  you have got the point. Yes, rendering the container into DOM only after the menu is open will fix this nuisance and some other issues like #2, #94
Currently the szh-menu-container is rendered in a parent component of the MenuList. As React runs effect from child to parent upwards the tree, szh-menu-container is yet to be mounted when the effect for positioning menu runs in the MenuList. To overcome it, szh-menu-container is always rendered in the parent component even before menu is open.
You might wonder why we didn't put szh-menu-container in the render method of MenuList. It's because MenuList is also used by the submenu which doesn't need a container.
I think this setup is causing enough trouble which worths some optimisation. Your question about the 1000 containers being uselessly rendered is also very valid. We'll make a fix in the upcoming release.

Thank you @szhsin, looking forward to try the new release! Do you have a sense of when it might be available?

The change is almost done in #729. Will update the unit tests/docs and do some package verification tomorrow.
If you'd try it out early, there is an alpha version of 3.3.0-alpha.0 and the codesandbox example.

@szhsin 3.3.0-alpha.0 behaves as expected!
Small question: is there a good reason not to remove szh-menu-container from the DOM when the menu is closed?

@moroshko thanks for confirming the updates. v3.3.0 is released!
To answer your question: menu by default is lazily mounted into DOM and remains mounted when closed. You could add the unmountOnClose prop to remove it from DOM: CodeSandbox

Awesome, thanks a lot for a quick turnaround!


[MODFISTO-358] - Logging improvement - Configuration

Purpose

https://issues.folio.org/browse/MODFISTO-358
Approach

The property file and all logging commands have been adjusted.
TODOS and Open Questions

Learning

Pre-Merge Checklist
Before merging this PR, please go through the following list and take appropriate actions.

Does this PR meet or exceed the expected quality standards?

[ ] Code coverage on new code is 80% or greater
[ ] Duplications on new code is 3% or less
[ ] There are no major code smells or security issues

Does this introduce breaking changes?

[ ] Were any API paths or methods changed, added or removed?
[ ] Were there any schema changes?
[ ] Did any of the interface versions change?
[ ] Were permissions changed, added, or removed?
[ ] Are there new interface dependencies?
[ ] There are no breaking changes in this PR.

If there are breaking changes, please STOP and consider the following:

What other modules will these changes impact?
Do JIRAs exist to update the impacted modules?

[ ] If not, please create them
[ ] Do they contain the appropriate level of detail?  Which endpoints/schemas changed, etc.
[ ] Do they have all they appropriate links to blocked/related issues?

Are the JIRAs under active development?

[ ] If not, contact the project's PO and make sure they're aware of the urgency.

Do PRs exist for these changes?

[ ] If so, have they been approved?

Ideally all of the PRs involved in breaking changes would be merged in the same day to avoid breaking the folio-testing environment.  Communication is paramount if that is to be achieved, especially as the number of intermodule and inter-team dependencies increase.
While it's helpful for reviewers to help identify potential problems, ensuring that it's safe to merge is ultimately the responsibility of the PR assignee.

Pattern Layout

Json Layout


startLoop should be set to false on Linux

When calling constructor of Player:
https://github.com/bdlukaa/just_audio_libwinmedia/blob/21b43158e68eaa47abc9d783cc33b47e98e477ce/lib/src/just_audio_libwinmedia_real.dart#L50
startLoop: !Platform.isLinux must be add as the comment of libwinmedia suggests:
https://github.com/harmonoid/libwinmedia/blob/71a7f157a0d3ed9a6394e73de7585a7c9a3525fa/flutter/lib/src/player.dart#L147

Why?

startLoop on Linux calls gtk_main, which is unnecessary for audio playback.


hasTokenBalance should ignore randomizer and use index only

Describe the bug
IBC assets at the default ephemeral address, and when trying to create a transaction c IBC will be passed the source that contains the randomizer

Jumping on this asap

@grod220 @TalDerei
we can fix this in either extension or minifront (just don't pass the randomizer to TPR)
Do I understand correctly that we can deliver the fix in minifront faster?


[AERIE-1724]  stub command expansion endpoints

Tickets addressed: AERIE-1724
Review: By commit
Merge strategy: Merge (no squash)

Description

This simply does a first stub out of the endpoints needed for command expansion. Each endpoint returns a 501 not implemented code with an appropriate message
Verification

Each of these were test manually.
Documentation

None
Future work

Add in tests somewhere

@goetzrrGit @pcrosemurgy I think we're ready for final reviews before merge


Don't send body in response to HEAD request

What these changes does?
Skips sending Response body when request method is HEAD or status code is 204 or 304. Satisfies requirements of RFC7230 an RFC7231 that server MUST NOT send message body in such responses.
How to test your changes?
Test case is included:
test_head_returns_empty_body (tests/test_web_functional.py)
Related issue number
Problems with HEAD responses #820
Checklist

[x] Code is written and well
[x] Tests for the changes are provided
[ ] Documentation reflects the changes

Coverage increased (+0.001%) to 98.265% when pulling a7d5995b67f9f0c131db980b682671bc0aaa922d on lgelo:master into a1f39a99e6add5d2970f41ff67a8ddff15c42280 on KeepSafe:master.

thanks


Browser module fix

Could you please squash all your commits into 1.
Plus call npm build and add the compiled version. (it will also prove that it builds 😄 )


is it possible to create a list of buckets on startup?

thanks

oh, also access and secreet keys.
I'm used to adobe fakes3, so for me the ideal dev tool would have:

list of buckets created on startup
accept any credential (or set them on startup)
data persistance (we have this)

thanks

Hello @masterkain 👋 Please excuse my late response.
For the auto-creation of buckets, please see https://github.com/scireum/s3ninja/issues/189. Considering that S3 Ninja is intended for testing, you should create the buckets during the setup phase of your tests. (Or, in case of a product, provide setup routines for fresh installations.)
Thanks for your proposed extensions. Feel free to provide pull requests. 😉 Unfortunately, we currently do not have the time to develop S3 Ninja beyond what we require ourselves for our own scenarios. However, I will provide assistance if you have questions implementing the features yourself.

Closing this as the buckets should be created externally via the API, and PR #222 now offers the option to create public buckets. For the arbitrary credentials, see the discussion in #66. Thanks for your input!


fix: Updated the TODO link on Readme.md

Scope of change: The TODO link is changed to the readme.md file on the master branch.

Thank you!


Support colored highlight for icons in completion

When the entry is selected/highlighted, the icon lost its color, making it harder to spot:

If the completion is using CSS and not ANSI Color, it would be great if it can by highlighted while still making the original icon color visible (or maybe just skip highlighting the icon)

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

I know you asked about keeping the original icon color but just in case you aren't aware of the following colorCustomization:
"workbench.colorCustomizations": {

  "editorSuggestWidget.selectedIconForeground": "#ff0000"
}

It will not retain that original icon color but you could make the selected icon very different from the non-selected icons.

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


Error when trying to reach the OAuth on Harvest

Describe the bug
After clicking the "Connect with Forecast" button on Homepage we get the Invalid redirect_uri is given message from Harvest OAuth.

To Reproduce
Steps to reproduce the behavior:

Go to https://forecast.jolicode.com/
Click on "🔒Connect with Forecast"
See error

Expected behavior
Access to the OAuth page on Harvest.
Desktop (please complete the following information):

OS: macOS
Browser: Chrome
Version 80.0.3987.149 (Official Build) (64-bit)

This bug does not seem to happen anymore. I guess it was a temporary glitch on Harvest's side. Can you please check?

I confirm.


Added auto-zoom to solar_system.track_object

Addresses #123.  The changes in the first commit fix the issues I was having with both animated transitions and selecting Earth.
I use gotoRaDecZoom for the Sun since it the zoom levels for gotoTarget appear to be immutable, and I thought it made the Sun a little small compared to how the other planets and moons appear. gotoTarget appears to default to the behavior of the gotoRaDecZoom when the target is the Sun, anyway, so using gotoRaDecZoom gains you direct control over the zoom level.
If this is all good and there are no more changes to make, I can delete the comments before we merge this PR.

@astrofrog Thanks for taking a look.
The non-instantaneity of the instant flag is not by design, but I didn't find how to get truly instantaneous behavior while using this method of focusing the viewer on a planet.
I removed the extra code. Please let me know what you think of my responses on what to do with ra, dec, and constellation.

@ojustino - could you rebase this? Is it ready for a final review?

@astrofrog Rebased and ready for review.

@jsub1 - could you advise @ojustino on how to fix the serialization test that is failing? (related to the fact we no longer hard code the object IDs in Python)


Add morphable properties to Flight model

#1681

For a polymorphic relationship, doesn't the column name containing the type need to end with _type for it to not throw a fit?

By convention, but good call. I just realized the morphTo isn't setup properly

Should we have test coverage on this?

Don't think it needs it, it's leveraging a Laravel feature and adding some columns.

Don't think it needs it, it's leveraging a Laravel feature and adding some columns.

Fair enough. I think this should be good once you're ready for it. Thanks for the new feature!

Just adding the issue link for traceability.
resolves #1681


FALCON-2184 Support to delete a non trusted recipe metadata from server

Dev Testing :
dataqa@blr-test-129:/usr/local/falcon/falcon-0.11-SNAPSHOT$ ./bin/falcon extension  -unregister -extensionName hdfs-mirrorings
Extension:hdfs-mirroringsis not registered with falcon.
dataqa@blr-test-129:/usr/local/falcon/falcon-0.11-SNAPSHOT$ ./bin/falcon extension  -unregister -extensionName hdfs-mirroring
ERROR: Internal Server Error;java.lang.Exception: hdfs-mirroringis trusted cannot be deleted.
CausedBy: hdfs-mirroringis trusted cannot be deleted.
dataqa@blr-test-129:/usr/local/falcon/falcon-0.11-SNAPSHOT$ ./bin/falcon extension  -unregister -extensionName test
Deleted entry for:test


Remove git add in lint-staged commads

Using git add in pre-commit hooks would make git complaining:

‼ Some of your tasks use git add command. Please remove it from the config since all modifications made by tasks will be automatically added to the git commit index.

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[x] Docs
[ ] Underlying tools
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

Other information:
My git version is: 2.26.0.windows.1

This feature was added in lint-staged v10. Currently, Vue CLI v4 generates projects with lint-staged v9, so git add is still necessary.
The documentation has been updated for Vue CLI v5, though: https://next.cli.vuejs.org/guide/cli-service.html#git-hooks


After logout a user is not redirected to login screen

Bug description
When a user is on the route vacation/requests/create nad wants to logout, he is not redirected to login screen. If the user refresh the page, he will be logged out from the apllication.
Reproduction steps
Steps to reproduce the behavior:

Login into application as an employee.
Go to "Moje wnioski".
Click "Dodaj wniosek".
Click "Wyloguj się".
See that you are still logged in.

Expected behavior
The user should be logout and redirected to login page.
Screenshots
https://user-images.githubusercontent.com/56546832/183375509-a0de72f0-8e57-4569-95ae-49c009b540d9.mp4
Environment

OS: kubuntu 22.04
Browser: Google Chrome

Additional context
This error shows up in the console, after click button "Wyloguj się"

I can't reproduce this bug, so I'm closing this issue.


pull request for e2e test at 01/19/2017 12:26:11

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[VL] Upgrade velox to 2023.3.29

What changes were proposed in this pull request?

velox change memory pool API. we need call addChild to create memory pool to allocate.
planFragment constructor  change a little bit.
setMemoryUsageTracker was removed by velox.
corresponding velox branch is https://github.com/zhejiangxiaomai/velox/tree/main_rebase_329
add "  cmake --install xsimd-build/  cmake --install gtest-build/" in build_velox.sh.  because velox move xsimd/gtest into resolve_dependency module.

How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)

get an core when run tpch.
spark.sql(" select s_acctbal, s_name, n_name, p_partkey, p_mfgr, s_address, s_phone, s_comment from part, supplier, partsupp, nation, region where p_partkey = ps_partkey and s_suppkey = ps_suppkey and p_size = 15 and p_type like '%BRASS' and s_nationkey = n_nationkey and n_regionkey = r_regionkey and r_name = 'EUROPE' and ps_supplycost = ( select min(ps_supplycost) from partsupp, supplier, nation, region where p_partkey = ps_partkey and s_suppkey = ps_suppkey and s_nationkey = n_nationkey and n_regionkey = r_regionkey and r_name = 'EUROPE') order by s_acctbal desc, n_name, s_name, p_partkey limit 1 ").show(1, false)

(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x00007f7750fde859 in __GI_abort () at abort.c:79
#2  0x00007f775036af2f in ?? () from /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/server/libjvm.so
#3  0x00007f7750caa683 in ?? () from /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/server/libjvm.so
#4  0x00007f7750afaf4e in JVM_handle_linux_signal () from /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/server/libjvm.so
#5  0x00007f7750aee0ac in ?? () from /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/server/libjvm.so
#6
#7  0x0000000000000000 in ?? ()
#8  0x00007f74782faf81 in facebook::velox::AlignedBuffer::freeToPool (this=0x7f7350025a30) at /root/gluten/cpp/../ep/build-velox/build/velox_ep/velox/buffer/Buffer.h:517
#9  0x00007f747824a48a in facebook::velox::Buffer::release (this=0x7f7350025a30) at /root/gluten/cpp/../ep/build-velox/build/velox_ep/velox/buffer/Buffer.h:75
#10 0x00007f747824a4e0 in facebook::velox::intrusive_ptr_release (buffer=0x7f7350025a30) at /root/gluten/cpp/../ep/build-velox/build/velox_ep/velox/buffer/Buffer.h:278
#11 0x00007f7478250fa7 in boost::intrusive_ptrfacebook::velox::Buffer::~intrusive_ptr (this=0x7f73500259f8, __in_chrg=) at /usr/include/boost/smart_ptr/intrusive_ptr.hpp:98
#12 0x00007f747c883923 in facebook::velox::(anonymous namespace)::VeloxToArrowBridgeHolder::~VeloxToArrowBridgeHolder (this=0x7f73500259d0, __in_chrg=) at ../../velox/vector/arrow/Bridge.cpp:37
#13 0x00007f747c883b54 in facebook::velox::(anonymous namespace)::releaseArrowArray (arrowArray=0x7f7350025970) at ../../velox/vector/arrow/Bridge.cpp:170
#14 0x00007f747c883ab2 in facebook::velox::(anonymous namespace)::releaseArrowArray (arrowArray=0x7f735004e440) at ../../velox/vector/arrow/Bridge.cpp:155
#15 0x00007f769c015d76 in Java_org_apache_arrow_c_jni_JniWrapper_releaseArray () from /tmp/jnilib-8155710934442135310.tmp
#16 0x00007f7739018427 in ?? ()
#17 0x00007f76764f09a0 in ?? ()
#18 0x00007f7675df0a08 in ?? ()
#19 0x0000000000000000 in ?? ()
@zhztheplayer could you please help me？

Can one of the admins verify this patch?


feat(subm): link from "bad login" to homepage

I think this is already deployed.

putting the gentx stuff here was just lack of branch discipline. I'll try to do better now that there's more collaboration here...


Listed User Pull Reversal

Allow the partial reversal of a pull. This command will take the list of all users who should be placed back into the queue in what would've been their positions had they not been pulled initially. The pullCount of all users placed back into the queue should be decremented by one.

Currently, just need to reverse based on pull time. Different issue will be created to reverse with pullCount.


Logitech MX Ink Input

Logitech MX Ink is a stylus peripheral for Quest headsets.  MX Ink will already kind of work with LÖVR since it's able to emulate a controller, but dedicated support would be nice to expose things like pressure sensitivity.
The OpenXR extension hasn't been published yet, but Quest exposes the unofficial XR_LOGITECH_mx_ink_stylus_interaction extension.

Couple design questions for the Lua API:

The pen can be held in the left or right hand, and reports actions on a specific hand.  Would we need to have pen/left and pen/right devices, or is just a pen device okay?  Is it important to know which hand the pen is assigned to?
The front/back buttons support double click events.  Normally people could just detect this in Lua, but the double click time threshold can be customized in the Quest settings, so there is benefit to exposing this.  Maybe lovr.headset.wasPressed('pen/front/doubleclick')?

API sketch:

New Device:

pen

(I'm hoping that we don't need to expose separate sub-devices like pen/grip, pen/point, pen/tip, etc. and this can just be the tip pose.  Maybe we could map the grip pose onto one of the hand devices if needed.  I think all the different pose paths were added because OpenXR requires them for hands).

New DeviceButton for pen:

tip
front (maybe also extra doubleclick sub-button)
middle
back (maybe also extra doubleclick sub-button)
docked (kinda weird)

New DeviceAxis's for pen:

tip
middle

This would be pretty specific to the MX Ink though, and could cause problems if we want to add support for other pens in the future.  An alternative, more abstract design for the buttons might look like this:

tip
touchpad, mapped to the pressure sensitive middle button.  This reuses an existing button enum and would work for any pen with a pressure sensitive button, even if it's not the "middle" one.
a for the front button
b for the back button
Maybe x and y for the double clicks?  ehh...

It's pretty arbitrary and brittle, but LÖVR could try to follow a consistent system like this for all pen-like devices.

the Quest Pro controllers can be flipped upside-down to act as a stylus. i think they have pressure sensitivity too. so the LÖVR API should take that into account


Fedora terminal banner is exposed on first run

On a fresh install the terminal does this, it scrolls off the screen but also shows the default fedora host terminal message, which we want to hide.

resolved in #1308


prepublish should be prepublishOnly

https://github.com/freeCodeCamp/open-api/blob/2652e5c02cd11604ff8efb202679cb3cd37d038e/package.json#L25
This is creating conflicts in yarn.lock and should ideally be removed or migrated

more info here

P.S Its also annoying and slow that snyk has to run on every install.


Clarify the expected values for 'identity'

Type of issue
Missing information
Feedback
For az containerapp secret set, need to clarify that when using a system-assigned managed identity, the value of 'identity' is system, as indicated in this doc ("for system assigned identity, use system instead of the resource ID").
Could we update the CLI doc to reflect this? E.g::
Change from the following...:
A list of secret(s) for the container app. Space-separated values in 'key=value' or 'key=keyvaultref:keyvaulturl,identityref:identity' format (where 'key' cannot be longer than 20 characters).
...to the following:
A list of secret(s) for the container app. Space-separated values in 'key=value' or 'key=keyvaultref:keyvaulturl,identityref:identity' format (where 'key' cannot be longer than 20 characters, and where 'identity' is either system or the resource id of the user-assigned managed identity).
Page URL
https://learn.microsoft.com/en-us/cli/azure/containerapp/secret?view=azure-cli-latest#az-containerapp-secret-set
Content source URL
https://github.com/MicrosoftDocs/azure-docs-cli/blob/main/latest/docs-ref-autogen/containerapp/secret.yml
Author
@dbradish-microsoft
Document Id
dc8c1147-dd84-6ef3-2744-63853b1a1d20

@gabesmsft
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

@gabesmsft , thank you for your feedback. This doc is autogenerated from source code, so I am moving this GitHub issue to Azure/azure-cli so the engineering team can respond.  Please see new GitHub issue #29238.


writecustom message command

In the writecustommessage command...  is there a way for the text to show up as a different color, instead of just black as the rest of the result text.? So that message stands out to the user?

You need to modify writeCustomizedMsg function to add a color property into the XML the function outputs.
Then you need to modify webcmd.xml to translate that property into HTML to add font color there.


WebapiError with api.play

Please, can you provide a sample to play a music or playlist?
I´m getting this error in the play method
WebapiError {name: "WebapiError", message: "Not Found", statusCode: 404}

When I try this:
const auth = require('spotify-personal-auth')
const SpotifyWebApi = require('spotify-web-api-node')

auth.config({
    clientId: 'aaaaaaaaaa'
    clientSecret: 'bbbbbbbbb'
    scope: ['user-modify-playback-state', 'user-top-read'],
    path: './tokens.json',
    redirectUri: 'http://localhost:8888/redirect',
})

const api = new SpotifyWebApi()

auth.token()
    .then(([token, refresh]) => {
        api.setAccessToken(token)
        api.setRefreshToken(refresh)
        return api.getMyTopTracks()
    })
    .then((data) => api.play({ uris: ['spotify:track:6KBsivP3Of4z2x6uNMAyE3'] }))
    .catch(console.log)

i think you need to pass just the uri, trim off spotify & track using .split(':')[2]

Did you find any way to make this work? Also, did you have to first connect the Spotify player using the SDK.


Proposal: Implement TS2021 (Tailscale control protocol v2)

Tailscale clients communicate with the control server using Tailscale's control protocol. This is what basically Headscale implements.
It is based on a HTTP API with a bit of Long Polling, and a grain of NaCl (https://nacl.cr.yp.to/) to encrypt the JSON payloads. Since 2019 the protocol has remained mostly stable - with just some extra fields being added to support new functionality like MagicDNS or Taildrop.
In our side the core of the implementation is located at api.go (where the registration methods are located) and poll.go (where lies the method that the clients use to receive updates).

A couple of weeks ago Tailscale team let us know (!) that they are working to implement the version 2 of the control protocol, codename TS2021.
They have also been kind enough to a) share some internal documentation on the implementation (!!), and b) release code in https://github.com/tailscale/tailscale that helps us A LOT with the implementation (!!!!!).
They did this in order not to break Headscale. Very very very big kudos to them!
About TS2021
TS2021 is a Noise-based protocol (https://noiseprotocol.org/noise.html), using the IK pattern (https://noiseprotocol.org/noise.html#interactive-handshake-patterns-fundamental). It is the same cryptographic framework as the one used for Signal or Whatsapp.
We will not have to deal with Noise too much. For us, the very first step is a POST call to /ts2021 and an upgrade + hijack of the TCP connection. Then the code I mentioned above quicks in, to create the Noise session. Once this is established, the API is reachable to the clients using what it looks like a H2C server (essentially just the good old v1 API, but without NaCl encryption for the payloads).
From what we can see, as of late March 2022 they have not yet fully migrated all the API methods to use TS2021. So we will have to follow them up gradually.
Our steps

Prepare our API machinery (always wanted to use this word) to be able to deal with clients using TS2019 (no idea if they call it this way) and TS2021. This includes a minor change in the /key method, and removing NaCl for TS2021.

Implement the /ts2021 handler (its quite similar to what we do for the embedded DERP server)

Plug a H2C server to the Noise connection under /ts2021 to expose our current API.

Keep track of their CurrentCapabilityVersion, gradually enabling new API calls under TS2021

Current status
I have a prototype mostly working. I will clean it a little bit an prepare a draft PR for scrutiny.

One important thing to note on the cryptography side, which may not be in the docs you got (it was a later implementation question and I'm not sure I backported it into the specs): headscale must generate a new control key for use with Noise, it must not reuse the existing nacl keypair for Noise, even though the keys are technically cross-compatible (both curve25519 keypairs).
This is to avoid cryptographic problems with key reuse across multiple protocols (nacl and noise). Our expert tells us that clients can reuse the same machine key for both protocols (important for compatibility), as long as the control plane uses different keys for nacl and noise.
See https://controlplane.tailscale.com/key?v=27 for how new clients retrieve both keypairs.
Also, if you haven't already, I recommend using the control/controlbase and control/controlhttp packages in the tailscale repo to implement the transport, it takes care of a bunch of the subtleties of upgrading to Noise and handshaking safely. The server-side APIs are also included in those packages.

Hey @danderson,
First, thank you so much for your message! Really appreciated!
And indeed, I was reusing the control key. Even left a comment wondering why you people where using two keys different.
.
We mostly use controlbase and controlhttp, although I had to modify slightly AcceptHTTP to make Gin (the web framework we use) happy. We also found netutil.NewOneConnListener which is quite convenient...
Again, thanks for your comment :)

Could you @ me when the PR is up, so I can see the AcceptHTTP changes you needed? I'm wondering if we can fix it upstream without importing all of Gin.

FYI, late change to the Noise protocol: https://github.com/tailscale/tailscale/pull/4370
We now use the client capability version as the Noise handshake version, instead of having a separate version for Noise. That means conn.Version() is the client capability version, and the server-side API changed a little bit to include the max supported protocol version, so the server can validate that it knows how to communicate correctly with a client. Aside from the API change, the controlbase/controlhttp packages handle the Noise internals for handshaking on the correct version, so hopefully not much difference as far as you're concerned.

This is done :)


Make the project rails 7.1 compatible

I've made the following changes to get the project running on a rails 7.1 project.
Aside from the changes, I've also included ruby 3.1 in the CI matrix: https://github.com/manuelvanrijn/minitest-rails/actions/runs/6459990864
Hope this helps to get the project in shape for this new rails version :)
Fixes #249

@blowmage is anything else needed to get this merged 🙏 ?

minitest-rails 7.1.0 is released.
Thank you for this PR. I had to update some additional files and this PR ended up with some merge conflicts, which is why it wasn't merged. My apologies. I would have preferred to get you the commit, but I figured you probably wanted the release more. Please do contribute again in the future.


Reorganize math folders

Reorganize math folders
Description
This is a follow up of #370, the aim is to have the math crate organized like:
└── math/
    ├── benches/
    └── src/
        ├── fft/
        │   ├── cpu/
        │   └── gpu/
        │       ├── metal/
        │       └── cuda/
        ├── msm/
        │   ├── cpu/
        │   └── gpu/
        │       ├── metal/
        │       └── cuda/
        └── gpu/
            ├── metal/
            └── cuda/

where the gpu/ folder will contain all the math related shader code needed for the Rust operations in fft/ and msm/
Type of change

Refactor

Checklist

[ ] Linked to Github Issue
[ ] Unit tests added
[ ] This change requires new documentation.

[ ] Documentation has been added/updated.

[ ] This change is an Optimization

[ ] Benchmarks added/run

Codecov Report

Merging #382 (047ad22) into move-gpu-and-fft-to-math (f632ee0) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

@@                     Coverage Diff                      @@
##           move-gpu-and-fft-to-math     #382      +/-   ##
============================================================
- Coverage                     93.68%   93.68%   -0.01%
============================================================
  Files                            60       60
  Lines                          7430     7425       -5
============================================================
- Hits                           6961     6956       -5
  Misses                          469      469

Impacted Files
Coverage Δ

math/src/fft/cpu/bit_reversing.rs
100.00% <ø> (ø)

math/src/fft/cpu/fft.rs
94.73% <ø> (ø)

math/src/fft/cpu/ops.rs
92.85% <ø> (ø)

math/src/fft/cpu/roots_of_unity.rs
100.00% <ø> (ø)

math/src/fft/test_helpers.rs
89.13% <ø> (ø)

math/src/fft/polynomial.rs
94.20% <100.00%> (-0.09%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Unable to sign-in in tauri app

Preliminary Checks

[X] I have reviewed the documentation: https://clerk.com/docs

[X] I have searched for existing issues: https://github.com/clerk/javascript/issues

[X] I have not already reached out to Clerk support via email or Discord (if you have, no need to open an issue here)

[X] This issue is not a question, general help request, or anything other than a bug report directly related to Clerk. Please ask questions in our Discord community: https://clerk.com/discord.

Reproduction
https://github.com/ryansteil-pl/clerk-nextjs-tauri-example
Publishable key
pk_test_Y29ycmVjdC1sZW11ci00Ni5jbGVyay5hY2NvdW50cy5kZXYk
Description
I'm using Clerk from within a tauri app.
When building for production, I'm not able to sign-in.

I have a hosted site on my primary domain that is currently functional (allows sign ups, sign ins, etc.). I have updated my instance settings with allowed_origins set to ["tauri://localhost"]
In the example repo above, I am passing
<ClerkProvider
  allowedRedirectProtocols={["tauri:"]}
  clerkJSVersion="5.39.0"
  signInUrl="/sign-in"
  {...pageProps}
>
  <Component {...pageProps} />
</ClerkProvider>

What am I missing? I have also attempted to use the primary domain sign in page directly, but I'm not able to redirect back to tauri://localhost.
Environment
System:
  OS: macOS 15.2
  CPU: (10) arm64 Apple M1 Max
  Memory: 7.98 GB / 64.00 GB
  Shell: 5.9 - /bin/zsh
Binaries:
  Node: 22.11.0 - ~/.nvm/versions/node/v22.11.0/bin/node
  Yarn: 1.22.21 - /opt/homebrew/bin/yarn
  npm: 10.9.0 - ~/.nvm/versions/node/v22.11.0/bin/npm
  pnpm: 9.14.2 - ~/Library/pnpm/pnpm
  bun: 1.0.27 - /opt/homebrew/bin/bun
Browsers:
  Chrome: 131.0.6778.109
  Safari: 18.2
npmPackages:
  @clerk/nextjs: ^6.7.1 => 6.7.1
  @tauri-apps/cli: ^2.1.0 => 2.1.0
  @tauri-apps/plugin-shell: ~2 => 2.0.1
  @types/node: ^20 => 20.17.9
  @types/react: ^18 => 18.3.14
  @types/react-dom: ^18 => 18.3.2
  eslint: ^8 => 8.57.1
  eslint-config-next: 15.0.3 => 15.0.3
  next: 15.0.3 => 15.0.3
  postcss: ^8 => 8.4.49
  react: 19.0.0-rc-66855b96-20241106 => 19.0.0-rc-66855b96-20241106
  react-dom: 19.0.0-rc-66855b96-20241106 => 19.0.0-rc-66855b96-20241106
  tailwindcss: ^3.4.1 => 3.4.16
  typescript: ^5 => 5.7.2

I think at least one issue is the inability to set cookies: https://github.com/tauri-apps/tauri/issues/2604
It's looking like I will have to create a custom SDK for this use case. Is there anything that I'm missing?

Actually, the best thing to do for now might be to Use Clerk as an OAuth 2 Provider.


Guides shouldn't suggest to use native-image.properties

I found this while reading the Java records guide: https://guides.micronaut.io/latest/micronaut-java-records-gradle-java.html
The guide suggests to do this:

This is a bad practice as this is a build only option. The native-image.properties file is automatically inherited if there's a consumer, so it should be limited to things like initializing at build time some classes, or things which are required for a library to work if a consumer builds an image.
Therefore, I think a better suggestion is to write:
graalvmNative {
    binaries {
        main {
            imageName.set('mn-graalvm-application')
            buildArgs.add('--verbose')
            buildArgs.add("--report-unsupported-elements-at-runtime") // <- this
        }
    }
}

Note also that you can simply run ./gradlew nativeRun to build the native image then run it (no need to use the CLI).

Note also that you can simply run ./gradlew nativeRun to build the native image then run it (no need to use the CLI).

@melix could you provide a PR with an snippet to common-graal-with-plugins.adoc with a paragraph suggesting the user the alternative command. If supported with maven, please, you suggest the equivalent for maven.

This is a bad practice as this is a build only option. The native-image.properties file is automatically inherited if there's a consumer, so it should be limited to things like initializing at build time some classes, or things which are required for a library to work if a consumer builds an image.

To do this, we would need to create a custom feature in the guides project and contribute this build snippet. I think that may work. Maybe, it requires changes in starter. Not sure. We can attempt this approach but we would need to hardcode the same snippet in the guide asciidoc because we don't support the generation of snippets with asciidoc tag wrapping.

@melix I was the one that suggested that. I know the right approach is to use the build.args(...) in the Gradle DSL. The problem, as Sergio mentioned is that we need to make the guide for both Maven and Gradle and we currently do not support adding those snippets in Starter automatically, so we decided to go that route.


Implement RPC api calls for integrated address

Hello. I am new to Monero, but I was measuring myself today with the implementation of the payment system. I looked through the monero-wallet-rpc documentation and these two features were missing, so I added them. Perhaps it is possible to do it "around". but after adding these functions the payment prototype looks more or less like this:
pub async fn payments_system_xmr_test() -> anyhow::Result<()> {
    //start this before rust application: ./monero-wallet-rpc --disable-rpc-login --wallet-file /home/user/Monero/test_wallet --password 123123 --rpc-bind-port 18089 --daemon-address http://node.monerooutreach.org:18081 --untrusted-daemon --rpc-bind-ip <IP_ADDRESS> --confirm-external-bind --log-level 4

    let rpc_client = monero_rpc::RpcClientBuilder::new()
        .build("http://<IP_ADDRESS>:18089")?;

    let wallet_client = rpc_client.wallet();

    let price = Amount::from_xmr(1.0)?;

    let invoice = wallet_client.make_integrated_address(None, None).await?;
    let integrated_address = invoice.0;
    let payment_id = invoice.1;

    loop {
        let typed_payment_id = PaymentId::from_str(&payment_id)?;

        let payments = wallet_client.get_payments(typed_payment_id).await?;

        let mut paid = false;

        for payment in payments {
            if payment.amount.as_xmr() >= price.as_xmr() {
                paid = true;
                break;
            }
        }

        if paid {
            println!("invoice has been paid");
        } else {
            println!("send {}xmr to {}", price.as_xmr(), integrated_address);
        }

        tokio::time::sleep(Duration::from_millis(5000)).await;
    }
}

Some types may not quite match, but I'm not very familiar with this project yet.

done. should be okay.

done. should be okay.

Is this new API good in your use case ? If yes then LGTM and we can go ahead with this impl

done. should be okay.

Is this new API good in your use case ? If yes then LGTM and we can go ahead with this impl

rather good, but I haven't yet used any code related to it in production. in general, it's a bit of a shame that you can't receive information about new payments via websocket and just setting up monero-wallet-rpc is bothersome but it's probably my fault because I didn't use docker