Second punchout doesn't work

Actual Behavior
Trying a second cxml punchout doesn't work, an error page occurs.
Expected Behavior
No error page.
Steps to Reproduce the Bug
Steps to reproduce the behavior:

Create a punchout session via setup request (customers//punchouts/cxml1.2/setuprequest)
go to created session link (http://localhost:4200/punchout?)
add some items to basket and transfer cart
Create another punchout session via setup request
go to created session link --> error page

Environment Details

Desktop: *

OS: Windows
Browser: Firefox
Project Code Version: current develop

Additional Context, like Screenshots, Log File Snippets etc.
It seems that the cookies might be a problem. After removing all cookies, including "punchout_BasketID", it worked again.
AB#75331

@Eisie96 is this still an issue or did #1109 fix it?

I cannot reproduce it anymore, so I guess it is solved.


Doesn't work in Edge

According to several people on the reddit update announcement, this latest update has made Cookie Monster stop working on Edge. I looked through the code, but didn't find anything that would stop it from working on Edge.

Have you tested it in Edge?
There seemed to be a problem with GitHub Pages yesterday, but this has now been resolved and I saw most people on the reddit mention that the mod worked again.

Yes, people said that it works, but I'm still getting complaints about Edge specifically, saying that it works in other browsers but not Edge.

I am not in possession of a windows computer so I can't test this.
Can you? Or somebody else?

@DanielNoord I do not currently have access to a Windows computer, but I will in ~1 hour. In the meantime, I edited the post asking for someone to post the console error they're getting...hopefully someone will, but if not, I can look at it soon.

I just checked it, everything seems to be working fine on my end (both for a new game and for my actual current game).
My Edge version:
Microsoft Edge 44.19041.423.0
Microsoft EdgeHTML 18.19041

@Chorizorro Huh, ok. Although that does look like a slightly outdated version of Edge, you're probably right if it works. I guess I'll close this issue for now, might open it up later if it's messing up on the latest version.

@bitsandbytes1708 Haha you're right, it was really outdated.
After updating Edge to the latest version (Version 87.0.664.47), everything still works fine in both case.

Then I am closing the issue.
If the reddit-user comes back with a more specific issue we can open a new issue.


keyword synonym doesn't highlight as value in sayings.

Issues

If you're having trouble with Articulate we definitely want to help you. If you can provide a little bit of information it will make our troubleshooting job easier.

When typing in a saying using a value that was set for a keyword, that value will be highlighted after a saying is entered. However, for synonyms, they do not highlight. I think this should be implemented, from having the user not have to highlight them manually.

Sausage being the synonym.
Please describe the issue you are having here and answer the question below.

Did you download a release or pull from Master? Which release?
21.1
What operating system are you running?
10 pro
Are you running locally or in the cloud?
local
Which browser are you using?
FF

Made a mistake, actually the issue is that characters aren't detected, such as ".", , etc. Closing. The synonyms DO highlight.


Add VirtualCube support

Is a wip but need some feedback about test. It worked for my example in DataChile but test didn't pass well.
get_cubes method also collect VirtualCube structures.
failures:
    tests::test_get_cubes
    tests::test_process_fragment

test result: FAILED. 7 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out

@palamago so the issue is that I had previously assumed that there was nothing that would come after a cube.
Since the order of a fragment must be the same as a full schema for moncat to work (currently), virtual cubes must come after regular cubes. That means we can just add one more check in the get_cubes method to check for a virtual cube tag open (in addition to the schema tag close and the default eof that are already there).
I think that this will fix the tests also.
And in your current usage, is it working correctly with a Virtual Cube declared in the same file as the regular Cube?

@palamago thanks for your work getting this most of the way! I just fixed up the last bit of logic around checking for closing tags and merged.


Citation

Your tool works great! Any plans to publish a short paper on it?

Thanks. Yes, preprint should be out soon!

Awesome! It would be great if you could update the issue when it's out. Looking forward to reading it


Fix Raster.info(stats=True) warning

Solves #174.
A test is added to validate that no warnings occur in the future.

Looks good to me!
While at it, should we add a test to make sure that the returned min/max values are the actual ones, with/without mask?
Something like this:
img = gu.Raster(gu.datasets.get_path("landsat_B4"))
np.ma.min(img.data)

-> compare to info's output (should be 13 for that case).
img.data[0, 0, 0] = 0
img.set_ndv(0)
np.ma.min(img.data)

-> should be unchanged.

Looks good to me!
While at it, should we add a test to make sure that the returned min/max values are the actual ones, with/without mask?
Something like this:
img = gu.Raster(gu.datasets.get_path("landsat_B4"))
np.ma.min(img.data)

-> compare to info's output (should be 13 for that case).
img.data[0, 0, 0] = 0
img.set_ndv(0)
np.ma.min(img.data)

-> should be unchanged.

Added in f1ff021


Stream is not active. Can not emit UI interaction.

Hi !
I'm trying to interact with my UE5 project from the html. Unfortunately, I have an error when I call emitUi function
Here is the error:

Stream is not active. Can not emit UI interaction.

Where can I enable the Stream ?
PS: I have all my UE5 project and pixel streaming server running, and I'm able to run/play my game from my React app

@hadi-ilies
Please provide a link to the repository with your project


A few more trackers for whotracksme

Hi there! We've been accumulating some information on known trackers, and I guess it might be useful to you.
I've tried to make a proper pull request at first, but it's not that easy to convert what we have in your format:) Please take a look at the Doc, I've marked trackers that are missing or incomplete on whotracks.me.
https://docs.google.com/spreadsheets/d/19yJoE2UQ3eh1Gd26YMtWASBp7gh0xOBsNZr3xouggdI/edit?usp=sharing

Thanks a lot for this - this is very helpful. We'll try and integrate it with our data and get back to you if there are any questions.

@ameshkov - thanks again, your contributions should now be part of the data.


Saiku doesn't see new schemas when the Mondrian Schema Cache is refreshed

When publishing a new schema, JPivot view can see new cubes once the Mondrian Schema Cache is refreshed via the admin console (I haven't tested it in the Pentaho web front end) but the only way to get Saiku to see a new schema is to restart the Pentaho server.
Maybe I am doing something wrong but I can't fathom this one out?

saiku cannot refresh schemas right now
there are several issues regarding this already filed: #179 & #196 - clear the cache
i will try to implement this as soon as i have time
--paul

implemented with button in our UI to refresh datsources/cache
fixed!


Fix cmake configuration include not exported.

reference:creating-relocatable-packages

The https://github.com/google/leveldb/pull/606 solution is better than me, I close this pull request.


When you read the page, you still do not know what to set on the Templates

[Enter feedback here]
The document on this page and the "Registration Management Page" is essentially useless when trying to determine what to set on "Templates" for an Installation.  The documentation does not even mention the need to use the InstallationTemplate class, which is inferred by the type on the class Installation.Templates.
This page spends the majority of the time describing platform specific notifications and what the results of the notifications are in XML, but it never actually describes what you would set on the InstallationTemplate.Body property in order to send something as simple as a Toast.

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

ID: 8b2a6681-55a5-e266-4672-fb211f81b7ba
Version Independent ID: a0fadc9f-c045-efd6-f41c-50e5815ded95
Content: Azure Notification Hubs templates
Content Source: articles/notification-hubs/notification-hubs-templates-cross-platform-push-messages.md
Service: notification-hubs
GitHub Login: @sethmanheim
Microsoft Alias: sethm

@robcamer Thanks for the feedback! We are currently investigating and will update you shortly.

I also noticed that "Tags" is marked as depreciated in the notification hub nuget package when you try to set it but this is not documented at all.  I found this link on it but it does not address the question and is still not clear how to send a  notification to a "tag".  https://github.com/Azure/azure-notificationhubs-dotnet/issues/10

I've been parsing out the docs and what i can find.  Still not able to receive notifications when i send from my backend.  Here's my Device Installation code. (I store a copy in a nosql db.  Model name for that is PhoneUserDeviceInstallation).
`
public async Task PerformDeviceInstallation(PhoneUserDeviceInstallation phoneUserDeviceInstallation)
{
try
{
        // Perform Device Installation into the Notification Hub
        Installation installation = new Installation();
        installation.InstallationId = phoneUserDeviceInstallation.Id;
        installation.PushChannel = phoneUserDeviceInstallation.PushChannel;

        phoneUserDeviceInstallation.Tags= await this.ObtainUserDeviceMemberships(phoneUserDeviceInstallation.UserAadId);
        installation.Tags = phoneUserDeviceInstallation.Tags;

         var headers = new Dictionary<string, string>();
         headers.Add("X-WNS-Type", "wns/tile");
        phoneUserDeviceInstallation.TemplateList = new Dictionary<string, InstallationTemplate>();
        phoneUserDeviceInstallation.TemplateList.Add("ToastText01", new InstallationTemplate()
        {
            Headers = headers,
            Tags = installation.Tags,
            Body = "<toast><visual><binding template=\"ToastText01\"><text id=\"1\">$(message)</text></binding></visual></toast>"
        });

        installation.Templates = phoneUserDeviceInstallation.TemplateList;

        // Save Device Installation to Cosmos DB
        await _cosmosDbService.UpdatePhoneUserDeviceInstallationAsync(phoneUserDeviceInstallation);

        switch (phoneUserDeviceInstallation.Platform.ToString())
        {
            case "mpns":
                installation.Platform = NotificationPlatform.Mpns;
                break;
            case "wns":
                installation.Platform = NotificationPlatform.Wns;
                break;
            case "apns":
                installation.Platform = NotificationPlatform.Apns;
                break;
            case "fcm":
                installation.Platform = NotificationPlatform.Fcm;
                break;
            default:
                throw new Exception("Invalid Platform for Device Installation.");
        }

        await _notificationClient.CreateOrUpdateInstallationAsync(installation);
        }
        catch (Exception ex)
        {

            Console.WriteLine("ERROR" + ex.Message);
        }
    }

`
This is my send code:
`
public async Task SendNotification(string tag)
{
NotificationOutcome status = null;
try
{
Dictionary<string, string> templateParams = new Dictionary<string, string>();
// Set chatTranscriptId
// Send a Toast template
templateParams["message"] = chatTranscriptId;
    status = await _notificationClient.SendTemplateNotificationAsync(templateParams, tag);
}
catch (Exception ex)
{
    Console.WriteLine($"ERROR {ex.Message}  Status: {status}");
}

}
`
However, a notification is never sent.  If i take the same tag value and use the Send Test functionality in Notification Hub, I do get a test Toast..   Sending does not work from the above back-end code.

@robcamer , Just wanted to understand if you have any queries.


My first revup bar

Topic: bar

Reviews in this chain:
└https://github.com/yuwei-will-xia/revup_test/pull/2 My first revup bar

#
head
base
diff
date
summary

0
62d6d01c
37f685bd
diff
Sep 18 11:14 AM
1 file changed, 1 insertion(+)


ENYO-6199: Not scroll when a fully visible item in VirtualList with different item size get focus

Checklist

[X] I have read and understand the contribution guide
[X] A CHANGELOG entry is included
[ ] At least one test case is included for this feature or bug fix
[X] Documentation was added or is not needed
[ ] This is an API breaking change

Issue Resolved / Feature Added
When a partially shown item get focus, the list including the item starts to scroll to show the item fully, and 5-way direction key is pressed to focus another item in viewport, the list scroll to the opposite direction.
Resolution
When an item get focus, we check if a list should scroll or not to show the item fully. Even though an item in viewport get focus, a list scrolls because of the wrong condition with  a wrong calculated numOfItemsInPage value. So I fixed the condition.
Links
ENYO-6199

LGTM

Native versions also have the same issue, as I tested, so what about fixing here together?

@ybsung The general new list behavior is still ok. However, I'd like to verify an unexpected behavior I'm seeing with the latest change to make sure it's not what you were describing in your previous comment.
-Create a VirtualGridList

Position the bottom-visible row partially off-screen
Use the pointer to hover/focus an item on the bottom (one of the middle items, where you could use 5way to move left or right)
Press 5way left

Expected: The focused item will slowly be scrolled to the bottom
Actual: The focused item quickly scrolls to the top
This behavior only happens when pressing 5way left in this scenario. If you press 5way right, it behaves as expected (as it does currently in develop). This behavior difference seems jarring and unexpected to me. It appears even worse when using a horizontal VirtualGridList, focusing on a partially off-screen item on the right, then pressing 5way "up". The focused item then scrolls to the left edge of the screen.
If there are no requirements for this behavior yet, it seems odd that it behaves differently depending on when direction you press - since the pressed direction (horizontal left/right, in the case of a vertically-oriented list) isn't dictating the desired vertical position of the list. Could you verify this behavior?

@germboy
I get your point
The case when row === nextRow was the one that the number of the fully visible row was 0.

I found we needed to consider the case if row === nextRow when the number of the fully visible row was not 0. For that case, isNextItemInView is false because the next item shows partially. So I added the additional condition and gave the item focus. By doing it, the item will be scrolled into view.


[Testing do not revew] Update istio.Version

Update istio.Version

@sebastienvas: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-suite-rbac-auth.sh
d66c4ca3c2caa110fc70f9a884ae5dd22d84866d
link
/test e2e-suite-rbac-auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@sebastienvas: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-suite-rbac-auth.sh
d66c4ca3c2caa110fc70f9a884ae5dd22d84866d
link
/test e2e-suite-rbac-auth

prow/e2e-suite-rbac-no_auth.sh
d66c4ca3c2caa110fc70f9a884ae5dd22d84866d
link
/test e2e-suite-rbac-no_auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Adding Age type and calculations. Fixes #9

This is a surprisingly large change. It introduces several new types and a lot of new functionality centered around the main new type, Age.
Age can be use used to describe a real or theoretical age of an individual at the time of their death or another event. The Age containts other attributes such as whether it is an estimation, handles date ranges and calculated metrics about whether they would be alive during the date range.
Most of the new functionality can be seen through IndividualNode.Age() and IndividualNode.AgeOf().
The other changes worth noting are:

DateNode.IsValid returns true only when the node is not nil and the start and end date are non-zero.
DateNode.IsExact and Date.IsExact will return true if the date range represents a single day with an exact constraint.
Fixed a bug where DateNodes.Minimum and DateNodes.Maximum used an average which wasn't sensible with date ranges. Now it will consider the values as a range rather than a point in time.
DateNodes.StripZero returns a new slice that only contains dates that are not zero (basically, valid and usable).
NewDateWithTime creates a new Date with the provided time.Time.
NewDateWithNow creates a two Dates that represents the the start and end of the current day.

This change is

Codecov Report

Merging #168 into master will increase coverage by 1.17%.
The diff coverage is 90.38%.

@@            Coverage Diff             @@
##           master     #168      +/-   ##
==========================================
+ Coverage   42.49%   43.67%   +1.17%
==========================================
  Files         141      143       +2
  Lines        4033     4135     +102
==========================================
+ Hits         1714     1806      +92
- Misses       2293     2299       +6
- Partials       26       30       +4

Impacted Files
Coverage Δ

dater.go
100% <ø> (ø)
:arrow_up:

date.go
100% <100%> (ø)
:arrow_up:

age_constraint.go
100% <100%> (ø)

date_nodes.go
100% <100%> (ø)
:arrow_up:

age.go
71.42% <71.42%> (ø)

date_node.go
88.23% <75%> (-1.13%)
:arrow_down:

individual_node.go
97.04% <95.23%> (-0.34%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7c28d20...516df94. Read the comment docs.


Feature request: export service/version information

One quite helpful bit of information is at which time new versions of services were activated. The graphs in the Fastly management UI display this; it would be cool if one could set this up e.g. as Grafana annotations.
AFAICT the information is in principle available from the Fastly API https://docs.fastly.com/api/config#version.

I'm not against it, but it's not obvious to me how this would be encoded in Prometheus metrics. If someone has a good suggestion there, I can certainly take a shot at an implementation.

I guess the "Grafana annotations" part will need some additional jury-rigging ;), for the time being I'm mostly concerned with getting the information out of the API in the first place. Luckily, the version is a plain integer, so what do you think about something like this:
fastly_service_version{service_id="ABCxyz",service_name="www.example.com"} 123.0
fastly_service_version{service_id="DEFtuv",service_name="img.example.com"} 42.0

Generally it's a mistake to report data like that in the actual value, rather prefer to put everything in labels and allow the value to be constant 1.

Oh. What are the risks/downsides? I have not been using Prometheus for all that long, so I guess I haven't painted myself into that particular corner yet (since I don't see anything wrong with the approach ;).
But to be honest I'm not very particular about the format -- all I want is to be able to retrieve a set of "sevice x has version y" items, which should be easy either way. (And possibly query "which version does service x have".) Thanks!

@wosc Are you able to easily build and test the version in the branch associated with #30? If yes, please give it a shot and make sure it meets your requirements. If no, let me know and I'll cut a release for you.

Thanks to your Dockerfile building was very easy! (I did have to manually clone peterbourgon/usage to vendor/ first, probably because I know nothing about the golang build toolchain yet ;).
The resulting metrics look fine to me, they give me the currently active version, which is exactly what I wanted. Thank you so much for building it! :)
fastly_rt_service_info{service_id="...",service_name="[PROD] www.zeit.de",service_version="152"} 1
fastly_rt_service_info{service_id="...",service_name="[PROD] img.zeit.de",service_version="65"} 1


Documentation required

A small wiki would be very useful to better tunes parameters such as "digi active" or "digi beacon" and
the ftp settings

you are right! the documentation is still very bad and I finally need to work on it.
Today i had some time and create this wiki page: https://github.com/lora-aprs/LoRa_APRS_iGate/wiki/Configuration
Feel free to ask questions if something is not clear to you!
In the next days I will create on page with a step by step guide how to install LoRa APRS iGate the best on any platform.

That's more than enough to begin!


cft test run --verbose displays sensitive terraform outputs

Issue summary
Exposure of sensitive terraform outputs in integration test build logs.
Reproduction steps
When using cft test run --verbose terraform output is streamed to the terminal. This includes displaying sensitive outputs in plaintext. Without --verbose, terraform outputs are excluded and build logs are no longer useful for troubleshooting or tracking deployment progress. This can be observed in the build logs for dynamic-web-app #114
Proposal
Do not display sensitive terraform outputs on --verbose. This discussion points to the notion that terraform output -json was not intended to display values for human consumption, but meant for direct machine integration. Based on that, options include:

Tracking terraform CLI intent and do not use terraform output -json in tool output, dropping -json
Adopt something like the proposed -insecure flag that cft users could add on top of --verbose to see sensitive values

We currently get outputs using terratest https://github.com/GoogleCloudPlatform/cloud-foundation-toolkit/blob/2977570586dce0980932f4553c7a18a23cff4c46/infra/blueprint-test/pkg/tft/terraform.go#L279C22-L279C22
We may want to initially do some config inspection in the constructor to understand which outputs are sensitive. Then if a sensitive output is requested inject a discard logger replacing the default logger.

It would be nice to keep the non-sensitive outputs, given the case I am seeing is when the entire set of outputs is printed at once.


Provide a way to configure message marshallers

In C#, the raw message payload are being deserialized/serialized using contextual marshallers (which are instantiated directly from the generated code of protobuf services).
Currently there is no way to provide any additional configuration to these marshallers, which causes problems such as
https://github.com/grpc/grpc/issues/22682.
Since being able to configure marshallers (e.g. providing recursionLimit for protobuf deserialization) is a very legitimate request, we should looks into ways how we could make marshallers configurable.

CC @JunTaoLuo @JamesNK

The static generated code for instantiating marshallers is e.g. here:
https://github.com/grpc/grpc/blob/b49b29b7eaebfb76478e27c4e40d848448be18f3/src/csharp/Grpc.Examples/MathGrpc.cs#L60
For clients, the Marshaller is being passed to the call invocation logic here:
https://github.com/grpc/grpc/blob/b49b29b7eaebfb76478e27c4e40d848448be18f3/src/csharp/Grpc.Examples/MathGrpc.cs#L69
And for server the handlers are created like this:
https://github.com/grpc/grpc/blob/b49b29b7eaebfb76478e27c4e40d848448be18f3/src/csharp/Grpc.Examples/MathGrpc.cs#L327

Thank you @jtattermusch for filing this!
Can anyone give me a rough idea of when this could be implemented so that I could plan my downstream mitigation accordingly?

@mikhailshilkov  it looks like this would take some careful design work first (I don't currently have a straightforward way to implement this and it's probably going to be a bit tricky), so it might take a while. Ideas for how this could be implemented are welcome.

What does Java/Go do here?

@ejona86  I took a look and it seemed that Java also doesn't have a good way of configuring (e.g. setting recursionLimit etc.) the CodedInputStream that is used for (un)marshalling protobuf messages in the generated grpc stubs. Can you confirm that? If so, is there any plans for providing such feature?
https://github.com/grpc/grpc-java/blob/master/protobuf-lite/src/main/java/io/grpc/protobuf/lite/ProtoLiteUtils.java

Yes, gRPC Java does not support setting recursion limit. We have a global for setting extension registry, although I can't say I'm particularly fond of that solution.
There's only two settings on CodedInputStream: setRecursionLimit and setSizeLimit. We unconditionally setSizeLimit to MAX_INT, as gRPC manages that limit. So that means the only configuration missing is setRecursionLimit, and nobody's complained about that.
If Java needed to provide a way to configure that, I think I'd add a new ProtoUtil API to create a Marshaller with a specified limit and then have users manually create the Marshaller and replace the one that's in the generated MethodDescriptor. That's annoying (mainly on server-side), but feasible for users. Since this is clearly rarely needed, that seems fine.

Shall I come here and leave a "we still need this" comment every 30 days? 🤔


Cannot finish the setup with Auth0

Environment

Operating System: Darwin
Node Version:     v21.1.0
Nuxt Version:     3.9.3
CLI Version:      3.10.0
Nitro Version:    2.8.1
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      devtools, modules, gtag, routeRules, app, alias, runtimeConfig
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
Nuxt3 setup with authjs nuxt plugin.

cookie alias : YES
@auth/core : 0.17.0 forced

auth/[...].ts setup as below
import Auth0Provider from "@auth/core/providers/auth0";
import type { AuthConfig } from "@auth/core/types";
import { NuxtAuthHandler } from "#auth";

const runtimeConfig = useRuntimeConfig();

export const authOptions: AuthConfig = {
  secret: runtimeConfig.authJs.secret,
  theme: {
    logo: "https://nuxt.com/assets/design-kit/logo/icon-green.png",
  },
  providers: [
    Auth0Provider({
      clientId: process.env.AUTH0_CLIENT_ID,
      clientSecret: process.env.AUTH0_SECRET,
      issuer: process.env.AUTH0_BASEURL,
      wellKnown: `https://${process.env.AUTH0_DOMAIN}/.well-known/openid-configuration`,
      authorization: {
        url: `https://${process.env.AUTH0_DOMAIN}/authorize`,
        params: { scope: "openid profile email" },
      },
    }),
  ],
};

export default NuxtAuthHandler(authOptions, runtimeConfig);

Describe the bug
The login page is starting properly, but got this error on callback.
It tried to test a lot of possible configurations in the Provider setup, but nothing goes properly.
OperationProcessingError: "response" is not a conform Authorization Server Metadata response
Any idea ?
Additional context
No response
Logs
No response

Likely a configuration issue. Check none of your env variables are incorrect or coming as empty and that you've provided all the none optional data. Additionally, check your client configuration in auth0.

   issuer: process.env.AUTH0_BASEURL,
    wellKnown: https://${process.env.AUTH0_DOMAIN}/.well-known/openid-configuration,

Thanks, I found the issue, indeed the issuer / wellKnow settings were in collision, the documentation was unclear.
For the record, here is my final (working) setting :

export const authOptions: AuthConfig = {
  secret: runtimeConfig.authJs.secret,
  theme: {
    logo: "https://nuxt.com/assets/design-kit/logo/icon-green.png",
  },
  providers: [
    Auth0Provider({
      clientId: process.env.AUTH0_CLIENT_ID,
      clientSecret: process.env.AUTH0_SECRET,
      issuer: `https://${process.env.AUTH0_DOMAIN}`,
      authorization: {
        url: `https://${process.env.AUTH0_DOMAIN}/authorize`,
        params: { scope: "openid profile email" },
      },
    }),
  ],
};

      ```


Not working on 1.19.3

Yes it is - working, that is.
Are you sure you installed the latest Cloth Config and Fabric API?
If so, describe what isn't working.
Is it crashing? If so, crash report please!

In the same vein make sure you're actually using the latest release of Falling Leaves.

Yeah, I didn't update, sorry)


pull request for e2e test at 12/31/2016 15:56:08

: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.


remove all steam-specific code to allow for reuse by other sessions

Sibling PR defining the Steam session: https://github.com/ChimeraOS/gamescope-session-steam/pull/1
Sibling PR defining the OpenGamepadUI sessions: https://github.com/ShadowBlip/OpenGamepadUI-session/pull/8
NOTES:

there was discussion of using two separate session files, a pre and post. But this ended up being unnecessary so there is only one file per session.
for any new session you must provide:

a .desktop file in /usr/share/wayland-sessions
a session environment file in /usr/share/gamescope-session/sessions.d/ which sets the CLIENTCMD variable to the main application that gamescope should launch

Looks good to me! Did we want to include changes in the README with instructions on how people can write their own custom sessions?

Good idea. I updated the README to reflect the changes and include some basic instructions on creating a custom session.


refactor: Changes the list views to use the new Select component

SUMMARY

Change the list views to use the new Select component
Adjusts the design of the date range picker to match other controls
Aligns the sort select with the other controls
Makes the layout behavior consistent when resizing the screen
Adjusts the controls to have the same width
Previously we had 'Me' and 'Admin', which are the same user, now it will only show the name of the logged user always as the first option of the select.
Adjusts the tests

@junlincc @jinghua-qa @rusackas @mistercrunch
PS: Sorry for the big PR, but everything needs to be tested as a whole.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
https://user-images.githubusercontent.com/70410625/130853912-05e9ac8e-f7d3-483b-9e82-ab629e18cbb4.mov
https://user-images.githubusercontent.com/70410625/130854218-28cdec24-ec71-42ee-97c2-438ce09f5290.mov
TESTING INSTRUCTIONS
Check the videos for instructions.
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[x] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

@ktmud About the 'Me' behavior. I found it a little strange to have options like 'Me' and 'Jesse Yang' if you're logged in as Jesse Yang. It gives me the impression that we are talking about different users. What do you think about using one or the other? Can I suggest use the user name and remove the 'Me'?

Sure, that makes sense. But having "Me" as the first option when users didn't type anything to search is still useful though.

When there is no selected value,me is not ranked the first anymore:
I was not able to find myself while searching my full name:

Previously we had a conflict because we could have at the same time Me and the name of the logged person. That was weird because I could select 'Me' but 'My name' wasn't selected. It also gave the impression that 'Me' and 'My Name' was two different users. To resolve that, I removed the 'Me' concept and now only present the name of the logged user always on top so it's the first option when opening the select.

Not able to find other filter options when there is a selected value in the URL parameters (to test this, just select a value and refresh the page):

Fixed

After selecting some values, clicking on the main nav links ("Charts" or "Dashboards") updates the URL but does not reset the filters.

This is also happening on master. I started investigating the problem but I'm afraid we could end up with even more changed files so I will fix this in a separate PR.

/testenv up

My only concern with this is the visuals of the filters. I tend to think the lighter design worked better here. The page looks much more crowded now. How do you feel about considering a lighter version of the Select for cases like this one? (no borders, inline header, etc.)

@geido This is a great suggestion. It will make the change less impactful for the users. I updated the code and the PR's video.

/testenv up

After a session with the design team, we decided to keep the default style of the Select component to preserve consistency across the product. I updated the PR's video.

/testenv up

I'm getting a JS error when trying to clear a selected value.

I'm getting a JS error when trying to clear a selected value.

Thanks for spotting that @ktmud. I fixed and also rebased to get the latest changes.

/testenv up

This is deviating further and further away from SIP-34 design:
I'm going to stamp as I understand the need to consolidate Select implementation, but I hope we can reconsider the design here.

@ktmud During our design session we came to the same conclusion. We chose to preserve the Select consistency for now, in order to migrate the component, but @mihir174 and @jess-dillard will analyze the design and propose improvements that will be implemented in the future.

Not sure if it'd help but here's a design I implemented for another project. Using carets instead of arrows helps.


nixpkg: no space left on devace

project > nix-shell --show-trace --run 'zsh'
error: while evaluating the attribute ‘bundler’ of the derivation ‘holdem-0.1’ at /home/netsu/Projects/Holdem/default.nix:5:3:
while evaluating the attribute ‘ruby’ of the derivation ‘ruby-2.2.3-p0-bundler-2015-01-11’ at /nix/store/plmwmzd5v036r41bah692qn9yasa4xil-nixos-16.03pre73316.93d8671/nixos/pkgs/development/interpreters/ruby/gem.nix:23:3:
while evaluating the attribute ‘stdenv’ of the derivation ‘ruby-2.2.3-p0’ at /nix/store/plmwmzd5v036r41bah692qn9yasa4xil-nixos-16.03pre73316.93d8671/nixos/pkgs/development/interpreters/ruby/default.nix:38:9:
while evaluating the attribute ‘shell’ of the derivation ‘stdenv’ at /nix/store/plmwmzd5v036r41bah692qn9yasa4xil-nixos-16.03pre73316.93d8671/nixos/pkgs/stdenv/generic/default.nix:238:14:
while evaluating the attribute ‘shell’ at /nix/store/plmwmzd5v036r41bah692qn9yasa4xil-nixos-16.03pre73316.93d8671/nixos/pkgs/build-support/cc-wrapper/default.nix:38:10:
while evaluating the attribute ‘stdenv’ of the derivation ‘bash-4.3-p42’ at /nix/store/plmwmzd5v036r41bah692qn9yasa4xil-nixos-16.03pre73316.93d8671/nixos/pkgs/shells/bash/default.nix:15:3:
while evaluating the attribute ‘defaultNativeBuildInputs’ of the derivation ‘stdenv-linux-boot’ at /nix/store/plmwmzd5v036r41bah692qn9yasa4xil-nixos-16.03pre73316.93d8671/nixos/pkgs/stdenv/generic/default.nix:238:14:
while evaluating the attribute ‘stdenv’ of the derivation ‘xz-5.2.2’ at /nix/store/plmwmzd5v036r41bah692qn9yasa4xil-nixos-16.03pre73316.93d8671/nixos/pkgs/tools/compression/xz/default.nix:4:3:
writing to file: No space left on device

Derivation
...What did do I wrong?

did you run out of disk space?

50Gb for root not enough yet?

i would think it would be.  when you run df do you have free disk space?

Yes, you right. Even after nix-collect-garbage -d 98% used. But I have pretty minimalistic desktop environment! So what is an issue in this case?

i have a script called empty-trash which i run as root.  it cleans up all old generations so use carefully
#!/usr/bin/env bash
nix-env --delete-generations old
nix-collect-garbage
nix-collect-garbage -d
nix-store --gc --print-dead

i take it this is problem with your other bug.  try it and if it solves problem please close both bugs

I not use nix-env, so nxc (nix-collect-garbage -d alias for me) should work enough. What nix-store --gc --print-dead is for?

deletes unreachable paths in the nix-store and tells you what they were if they existed

@mogorman ok, thanks! Few minutes to check all.

also you could do a du -h on /nix/store to confirm it is nix thats taking up all your space

probably yes, because it already cleanup 15Gb for me. Nixpkg should really care about compression or so... Or I should cleanup it each time.

not each time just sometimes.   you mind closing these bugs i assume they are caused by your low disk space

.\_/. 50Gb isn't low yet!

Let me check nix-shell...

It, looks like you run out of disk space on your devace :D
V pet., 8. jan. 2016 5:12 pop. je oseba Netsu<EMAIL_ADDRESS>napisala:

project > nix-shell --show-trace --run 'zsh'
error: while evaluating the attribute ‘bundler’ of the derivation ‘holdem-0.1’ at /home/netsu/Projects/Holdem/default.nix:5:3:
while evaluating the attribute ‘ruby’ of the derivation ‘ruby-2.2.3-p0-bundler-2015-01-11’ at /nix/store/plmwmzd5v036r41bah692qn9yasa4xil-nixos-16.03pre73316.93d8671/nixos/pkgs/development/interpreters/ruby/gem.nix:23:3:
while evaluating the attribute ‘stdenv’ of the derivation ‘ruby-2.2.3-p0’ at /nix/store/plmwmzd5v036r41bah692qn9yasa4xil-nixos-16.03pre73316.93d8671/nixos/pkgs/development/interpreters/ruby/default.nix:38:9:
while evaluating the attribute ‘shell’ of the derivation ‘stdenv’ at /nix/store/plmwmzd5v036r41bah692qn9yasa4xil-nixos-16.03pre73316.93d8671/nixos/pkgs/stdenv/generic/default.nix:238:14:
while evaluating the attribute ‘shell’ at /nix/store/plmwmzd5v036r41bah692qn9yasa4xil-nixos-16.03pre73316.93d8671/nixos/pkgs/build-support/cc-wrapper/default.nix:38:10:
while evaluating the attribute ‘stdenv’ of the derivation ‘bash-4.3-p42’ at /nix/store/plmwmzd5v036r41bah692qn9yasa4xil-nixos-16.03pre73316.93d8671/nixos/pkgs/shells/bash/default.nix:15:3:
while evaluating the attribute ‘defaultNativeBuildInputs’ of the derivation ‘stdenv-linux-boot’ at /nix/store/plmwmzd5v036r41bah692qn9yasa4xil-nixos-16.03pre73316.93d8671/nixos/pkgs/stdenv/generic/default.nix:238:14:
while evaluating the attribute ‘stdenv’ of the derivation ‘xz-5.2.2’ at /nix/store/plmwmzd5v036r41bah692qn9yasa4xil-nixos-16.03pre73316.93d8671/nixos/pkgs/tools/compression/xz/default.nix:4:3:
writing to file: No space left on device
Derivation http://nixpaste.lbr.uno/z1NYFhlm
—
Reply to this email directly or view it on GitHub
https://github.com/NixOS/nixpkgs/issues/12240.

@mogorman BTW, on nix-env --delete-generations old
I got
error: ‘/nix/var/nix/profiles/per-user/username’ is not a symlink

Same for root.

@offlinehacker thank you, captain!

the files in that dir are symlinks right? '/nix/var/nix/profiles/per-user/username’

@mogorman now for nix-shell have only one warning:
> nix-shell --show-trace --run 'zsh'
warning: dumping very large path (> 256 MiB); this may run out of memory
>_

> ll /nix/var/nix/profiles/per-user
total 8.0K
drwxr-xr-x 2 netsu users 4.0K Jan  8 18:45 username
drwxr-xr-x 2 root  root  4.0K Jan  8 18:45 root
root@hackbook> ll /nix/var/nix/profiles/per-user/root
total 4.0K
lrwxrwxrwx 1 root root 16 Jan  8 18:14 channels -> channels-44-link
lrwxrwxrwx 1 root root 60 Jan  8 17:37 channels-44-link -> /nix/store/7xfgvgir2ap2csm3l0fz1affwryazq7b-user-environment
root@hackbook> ll /nix/var/nix/profiles/per-user/username
total 8.0K
lrwxrwxrwx 1 username users 15 Oct 10 01:59 channels -> channels-1-link
lrwxrwxrwx 1 username users 60 Oct 10 01:59 channels-1-link -> /nix/store/27wr7i3ign059xzdfwc7rkm2dam7sr3m-user-environment
lrwxrwxrwx 1 username users 14 Sep  1 21:15 profile -> profile-6-link
lrwxrwxrwx 1 username users 60 Sep  1 21:15 profile-6-link -> /nix/store/zxn68vqsy4li8v99f8gaidw7v8s1azmh-user-environment
root@hackbook>

Duplicate of https://github.com/NixOS/nixpkgs/issues/12241, no?

@peti, no. We discuss 2 things here also: error about symlinks in profiles and warning about large path in nix-shell. Could you reopen issue, because both, error and the warning not solved yet. Thank you.

@peti ?... Ok, thanks, no problem. I'll create new two.

The large-path warning is normal. The only thing it can cause AFAIK is depleting your RAM.

@vcunat thanks, I create issue already.
Can I somehow solve this warning? I shouldn't got warning in case if I just do all in right way.

No, you can not solve that warning (except by reducing the size of the directory that's copied into the store when you enter nix-shell).


add IF NOT EXISTS to discharge tables just in case

guessing this should not be an issue due to the clean processes but it was something I felt I needed to do on last successful build so thought I'd throw out there in case it is keepable work

definitely a good idea for the extension and can't hurt for the tables.


Feature: scroll the log viewer

Is this possible today?

Done as of bb125e7! Should be in the next release!

You're on a roll :roller_skate:


⚠ Bofrost.be has degraded performance

In ccf8f71, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1794 ms

Resolved: Bofrost.be performance has improved in 2b25b72 after 10 minutes.


Runtime panic on .onion domain

This will create runtime panic

z := zonedb.PublicZone("anything.onion")
z.WhoisServer()

This library stings eyes from onions. 🥲

This may have been addressed in #914, which added .onion to ZoneDB along with the other special-use zones.

PublicZone may return nil. It is the caller’s responsibility to check for nil.


add workitem metadata

I would be cool if the action could add workitem title and workitem type in the posted link

Hi, Did you find any solution for this ?
If yes, Please let me know.
Thanks 😃


Kubernetes Server/Deployer pushes app properties command line

Problem with this is that database passwords show up in the clear for batch jobs.  Also that means that the passwords are stored in the repository for task-executions as well as batch.
Step to reproduce:

Create Task Definition foo with timestamp-batch.
Launch foo
Look at task-execution for the launch. You will see the arguments with the password redacted.
Look at the Job Execution Details.  Password is shown in the clear.

This does not occur on local server.

Refer to issue: https://github.com/spring-cloud/spring-cloud-dataflow/issues/2125

This issue was moved to spring-cloud/spring-cloud-deployer-kubernetes#209


Relax rubocop

Relaxes various RuboCop metrics application-wide: uses CodeClimate's suggested max's instead of RuboCop's
Ignores various RuboCop metrics in test files: disables various Cops which we regularly ignore in test files and which make less sense there.

This should get rid of > 1,000 purported RuboCop offenses which are should not be offenses and which are a distraction to developers.

Coverage remained the same at 88.077% when pulling 60f481fe6ef69b6ee2ee64abe2382bf44747e767 on JoeCohen:relax-rubocop into fd2d2ce4d7e4685b569ce7876c3cab19f45062a6 on MushroomObserver:master.


Add Babel preset for React package

The React preset for Babel is useful for automatically adding Babel plugins to understand JSX syntax.
Proposed Changes

Add Babel preset for React
Update Babel ESLint parser to new package name

Readiness Checklist
Author/Contributor

[x] If documentation is needed for this change, has that been included in this pull request

Reviewing Maintainer

[ ] Label as breaking if this is a large fundamental change
[x] Label as either automation, bug, documentation, enhancement, infrastructure, or performance

@fdanielsen Thanks for submitting a pull request!
I'm confused and need some help to determine what we are trying to accomplish here. This pull request currently adds a dependency but then I don't see any code that actually uses that dependency. Can you help me understand the goal of this pull request?

That makes more sense. Can you resolve the branch conflicts and we can get this one merged through?

Great, I've merged in latest from the main branch now and fixed conflicts.

🎉 Thanks for the contribution!!

Thanks for the prompt review! Any idea when you'll make a new release so I can test this out in a GitHub action?

I try to keep an every Friday release schedule but am also terrible at doing it consistently. So, i've just published a new release so you can give it a try anytime.
https://github.com/super-linter/super-linter/releases/tag/v5.3.1


Simplest example does not work

I create the simplest example with latest versions of libs and chrome. It does not change the textarea height.
Check it here:
https://stackblitz.com/edit/stackblitz-starters-3yw9em?file=src%2Findex.tsx
import { createRoot } from 'react-dom/client';
import TextareaAutosize from 'react-textarea-autosize';

const root = createRoot(document.getElementById('app'));

root.render(
  <div>
    <TextareaAutosize />
  </div>
);

Stackblitz doesnt configure the browser condition here and it picked up a bundle that is meant to be loaded in server environments.

I updated react-textarea-autosize in my project from 6.1.0 to 8.5.3 to have ref prop and it had broken.
the 6.1.0 works on Stackblitz (https://stackblitz.com/edit/stackblitz-starters-enhi95?file=src%2Findex.tsx)

What bundler do you use in your project?

webpack

What version of webpack? is it a custom configuration or are you using it through some framework~?

Custom configuration, webpack 4.


Add tracking for cron jobs

Signed-off-by: Shubham Saxena<EMAIL_ADDRESS>Contributes to #127
What did you do?
Added tracking of the cron jobs (start time, end time and number of objects processed).
Why did you do it?
There were no insights on whether the cron jobs were running or not.
How have you tested it?
Yet to test...
Were docs updated if needed?

[ ] No
[ ] Yes
[X] N/A

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] My changes generate no new console logs
[ ] Fixes entire issue
[ ] Partial fix for issue

20 May 2022 - Discussion between Demi, Shubham, and Tony:   Great idea, but we need to avoid ever-increasing database that could grow out of control/out-of-space crash condition.  Suggest we create a method on the new JobDetail class such as "cleanup" which removes any records that are in excess of six months or 100,000 records, for example.  This can be invoked prior to each call in each of the three batch jobs.


Avoid "as const" by using TypeScript 5 feature

@dkzlv Do we need a major release for TypeScript 5 feature?

@ai you sure? That won’t work on TS<5 at all (it’ll probably infer routes as any, if compile at all). I think we’ll need to wait at least a year to adopt this.

How hard it was to migrate to TS 5 on your project?
If we release it as a major update we can ask anyone to update to TS 5.0.

Here is stats for TS versions:

5.0.2: 3,4 M downloads
4.9.5: 8.7 M downloads

Looks like adoption goes very well.

Nah, I haven't updated to TS5 yet 😄
Aaand you're kind of bluffing when only compare those two, because you also have 3M for 4.9.4, 1M for 4.9.3, 3M for 4.8.4, 3M for 4.7.4, 1.5M for 4.6.4, etc. 3M for 5.x is less than 10% of the 40M weekly downloads.
But still I guess you're right. We can assume router specifically and nanostores in general aren't used by huge codebases yet, so updating TS is somewhat a straightforward process for them. Answering your original question: yeah, I think a major version is needed.

We still can wait for a few weeks until bigger adoption rates for TS 5.0.


Feature request: Ability to save drafts that can persist beyond local storage

My request is for a method to explicitly be able to click Save for my draft so that I can recover it across sessions, (or maybe a periodic automatic save to SN's back-end, like after every ten seconds following edit activity, or something like that).  SN does now have protection against accidental navigation (e.g., closing the tab), but that doesn't help if I close my browser (and I am using Incognito mode/private browser).
Discussed further here: https://stacker.news/items/99262

Also possibly related is Issue #121.

Bumping this since I think this would be a great feature for content creators / people who post long-form content on SN.
Even though I am not a dedicated content creator on SN, I already have sometimes the need to save posts on my local disk such that I can start writing another post without the other one getting overwritten.
Basically, I want to be able to polish a post before submitting it without blocking other posts I might come up with in the meantime.
Having the option to save drafts would fix this need.
This also means that you can have multiple drafts and overwrite them with a new version.


Fonts are not in .vuepress/dist, making them inaccessible in web context

[x] I confirm that this is an issue rather than a question.

Bug report
Steps to reproduce

[ ] I prepared a reproduction repo, here is the reproduction repo:

[x] This issue doesn't need a reproduction repro, here is the steps to reproduce:

open https://example.vuepress-theme-blog.ulivz.com/ or https://ulivz.com/

open developer tools

see error message Failed to load resource: the server responded with a status of 404 () EJRVQgYoZZY2vCFuvAFWzr-_dSb_.woff2

What is expected?
No errors, the font EJRVQgYoZZY2vCFuvAFWzr-_dSb_.woff2 and its variants should be here.
What is actually happening?
An error happens when trying to load a font.

Fonts are not shipped in .vuepress/dist folder when running vuepress build, but I don't understand why because paths used in font.styl looks ok, and VP does not output any errors. :confused:
Other relevant information

npx vuepress info: not relevant here

I can't reproduce it since I have the font in local, but it definitely can't be access for now.
Thanks for the report.


Errors and failed status for the mssql ingestion job when Enabling Stateful Ingestion

Error can easily reproduced when the an entity is dropped/deleted from the source.  it happens when ingestion is trying to remove a stale entity from datahub.
Datahub version: v0.10.2
Execution finished with errors.
{'exec_id': 'f54bc15d-808f-4957-9e62-731d12cfa652',
 'infos': ['2023-04-27 16:07:31.851823 INFO: Starting execution for task with name=RUN_INGEST',
           "2023-04-27 16:08:03.582169 INFO: Failed to execute 'datahub ingest'",
           '2023-04-27 16:08:03.583391 INFO: Caught exception EXECUTING task_id=f54bc15d-808f-4957-9e62-731d12cfa652, name=RUN_INGEST, '
           'stacktrace=Traceback (most recent call last):\n'
           '  File "/usr/local/lib/python3.10/site-packages/acryl/executor/execution/default_executor.py", line 122, in execute_task\n'
           '    task_event_loop.run_until_complete(task_future)\n'
           '  File "/usr/local/lib/python3.10/asyncio/base_events.py", line 649, in run_until_complete\n'
           '    return future.result()\n'
           '  File "/usr/local/lib/python3.10/site-packages/acryl/executor/execution/sub_process_ingestion_task.py", line 231, in execute\n'
           '    raise TaskError("Failed to execute \'datahub ingest\'")\n'
           "acryl.executor.execution.task.TaskError: Failed to execute 'datahub ingest'\n"],
 'errors': []}
~~~~ Ingestion Report ~~~~
{
  "cli": {
    "cli_version": "<IP_ADDRESS>",
    "cli_entry_location": "/usr/local/lib/python3.10/site-packages/datahub/__init__.py",
    "py_version": "3.10.10 (main, Mar 14 2023, 02:37:11) [GCC 10.2.1 20210110]",
    "py_exec_path": "/usr/local/bin/python",
    "os_details": "Linux-5.15.0-60-generic-x86_64-with-glibc2.31",
    "peak_memory_usage": "332.39 MB",
    "mem_info": "332.39 MB"
  },
 'aspects': {'container': {'containerProperties': 2, 'status': 2, 'dataPlatformInstance': 2, 'subTypes': 2, 'container': 1},
             'dataset': {'container': 23, 'status': 23, 'datasetProperties': 23, 'schemaMetadata': 23, 'subTypes': 23, 'datasetProfile': 23}},
 'warnings': {},
 'failures': {},
 'soft_deleted_stale_entities': [],
 'tables_scanned': 23,
 'views_scanned': 0,
 'entities_profiled': 23,
 'filtered': ['db_accessadmin.*',
              'db_backupoperator.*',
              'db_datareader.*',
              'db_datawriter.*',
              'db_ddladmin.*',
              'db_denydatareader.*',
              'db_denydatawriter.*',
              'db_owner.*',
              'db_securityadmin.*',
              'INFORMATION_SCHEMA.*',
              '... sampled of 12 total elements'],
 'query_combiner': {'total_queries': 1145,
                    'uncombined_queries_issued': 494,
                    'combined_queries_issued': 71,
                    'queries_combined': 337,
                    'query_exceptions': 314},
 'start_time': '2023-04-27 16:07:33.888433 (27.11 seconds ago)',
 'running_time': '27.11 seconds'}
[2023-04-27 16:08:01,000] INFO     {datahub.cli.ingest_cli:137} - Sink (datahub-rest) report:
{'total_records_written': 101,
 'records_written_per_second': 3,
 'warnings': [],
 'failures': [],
 'start_time': '2023-04-27 16:07:33.529165 (27.47 seconds ago)',
 'current_time': '2023-04-27 16:08:01.000169 (now)',
 'total_duration_in_seconds': 27.47,
 'gms_version': 'v0.10.2',
 'pending_requests': 0}
[2023-04-27 16:08:01,008] ERROR    {datahub.entrypoints:188} - Command failed:
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/datahub/entrypoints.py", line 175, in main
    sys.exit(datahub(standalone_mode=False, **kwargs))
  File "/usr/local/lib/python3.10/site-packages/click/core.py", line 1130, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python3.10/site-packages/click/core.py", line 1055, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python3.10/site-packages/click/core.py", line 1657, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.10/site-packages/click/core.py", line 1657, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.10/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python3.10/site-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
  File "/usr/local/lib/python3.10/site-packages/click/decorators.py", line 26, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/usr/local/lib/python3.10/site-packages/datahub/telemetry/telemetry.py", line 379, in wrapper
    raise e
  File "/usr/local/lib/python3.10/site-packages/datahub/telemetry/telemetry.py", line 334, in wrapper
    res = func(*args, **kwargs)
  File "/usr/local/lib/python3.10/site-packages/datahub/utilities/memory_leak_detector.py", line 95, in wrapper
    return func(ctx, *args, **kwargs)
  File "/usr/local/lib/python3.10/site-packages/datahub/cli/ingest_cli.py", line 198, in run
    loop.run_until_complete(run_func_check_upgrade(pipeline))
  File "/usr/local/lib/python3.10/asyncio/base_events.py", line 649, in run_until_complete
    return future.result()
  File "/usr/local/lib/python3.10/site-packages/datahub/cli/ingest_cli.py", line 158, in run_func_check_upgrade
    ret = await the_one_future
  File "/usr/local/lib/python3.10/site-packages/datahub/cli/ingest_cli.py", line 149, in run_pipeline_async
    return await loop.run_in_executor(
  File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.10/site-packages/datahub/cli/ingest_cli.py", line 140, in run_pipeline_to_completion
    raise e
  File "/usr/local/lib/python3.10/site-packages/datahub/cli/ingest_cli.py", line 132, in run_pipeline_to_completion
    pipeline.run()
  File "/usr/local/lib/python3.10/site-packages/datahub/ingestion/run/pipeline.py", line 339, in run
    for wu in itertools.islice(
  File "/usr/local/lib/python3.10/site-packages/datahub/utilities/source_helpers.py", line 98, in auto_stale_entity_removal
    yield from stale_entity_removal_handler.gen_removed_entity_workunits()
  File "/usr/local/lib/python3.10/site-packages/datahub/ingestion/source/state/stale_entity_removal_handler.py", line 267, in gen_removed_entity_workunits
    last_checkpoint: Optional[Checkpoint] = self.source.get_last_checkpoint(
  File "/usr/local/lib/python3.10/site-packages/datahub/ingestion/source/state/stateful_ingestion_base.py", line 337, in get_last_checkpoint
    self.last_checkpoints[job_id] = self._get_last_checkpoint(
  File "/usr/local/lib/python3.10/site-packages/datahub/ingestion/source/state/stateful_ingestion_base.py", line 301, in _get_last_checkpoint
    last_checkpoint_aspect = self.ingestion_checkpointing_state_provider.get_latest_checkpoint(  # type: ignore
  File "/usr/local/lib/python3.10/site-packages/datahub/ingestion/source/state_provider/datahub_ingestion_checkpointing_provider.py", line 85, in get_latest_checkpoint
    ] = self.graph.get_latest_timeseries_value(
  File "/usr/local/lib/python3.10/site-packages/datahub/ingestion/graph/client.py", line 292, in get_latest_timeseries_value
    assert len(values) == 1
AssertionError

This is fixed in Datahub Ingestion CLI version <IP_ADDRESS> by this PR.

awesome!  you guys rock!


Dedicated mail clients run untrusted code too

On https://github.com/KasparEtter/ef1p/blob/main/pages/email/email.md
When you say Webmail has the advantage that you always run the newest version of the code, which is sandboxed from the rest of your system by the web browser. On the downside, attacks like phishing, cross-site scripting, and cross-site request forgery are only possible because the browser runs untrusted code, which a dedicated mail client doesn't, I think this is not true: many dedicated mail clients run embedded web browsers (webviews) for email visualization, enabling the run of untrusted code (javascript) in an email, same as webmails. These attacks also affect dedicated mail clients, for example: https://security.snyk.io/vuln/SNYK-RHEL6-THUNDERBIRD-7841995 .

Hi, thanks a lot for your feedback! What I meant by the second sentence (among other things) is that you can phish "only" for a user's email credentials if the user logs in to their mail service via a website (by directing them to a malicious website instead). (A native app could also emulate the interface of your dedicated mail client and prompt for a re-entry of your password, of course, but if you have full access to a user's computer, there are many other things you could do as well or instead.) Web services try to prevent XSS and XSRF, of course, but those are issues you don't have to think about when you build a native app (and properly disable JavaScript for user/dynamically loaded content). Regarding your example, I see two ways to improve my statement:

… because the browser runs untrusted code by design, which a dedicated mail client doesn't,
… because the browser runs untrusted code, which a dedicated mail client doesn't or at least shouldn't.

I think/hope I don't need to say that any software can have bugs with security implications.
Do you see what I mean? (My statement is more about web apps versus native apps in general, somewhat independent from email.)


Create foexo.is-cool.me.json

Requirements

[x] You have completed your website.
[x] The website is reachable.
[x] The CNAME record doesn't contain https:// or /.
[x] There is sufficient information at the owner field.

Description

My personal website and I will use to with forwardmail too to receive mails on custom domain
Link to Website

Not ready yet, need domain first

I have read the CLA Document and I hereby sign the CLA

recheck

@LightHostingFree Why is it not working? What is wrong?

recheck

@LightHostingFree

There is some error in your workflow, can you fix it?


no object path in compound parts record

some objects don’t have a tn or object path in it's parts, such as the compound f2f3ca92-9b8f-4b35-954a-a5b8600ab234. the object path is in the top level but there should be two images

This appears to be a cataloging issue in archivesspace.


How to make new category in Event tab on the right side of calender

We're closing old issues so we can get back to actively maintaining the extension. Feel free to reopen if this is still an issue for you.


[FLINK-29421][python] Support python 3.10

Contribution Checklist
What is the purpose of the change
This pull request will support python 3.10
Brief change log

Update pemja to 0.3.0
Update apache-beam to 2.43.0
Remove python 3.6 support
Add python 3.10 support

Verifying this change
This change added tests and can be verified as follows:

original tests

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

Hi @HuangXingBo , Python has already released version 3.11.
Why is this PR closed? And are there any other efforts to make pyflink compatible with Python 3.10 / 3.11?


Migration path from slack-sdk to slack bolt

(Describe your issue and goal here)
i am working on a slack application built entirely using python-slack-sdk and have started running into performance issues relating to the 3 second timeout.
i am looking to migrate to bolt-python but am having trouble finding guidance on how to migrate an existing application to this sdk. my apologies if this documentation already exists somewhere - i was just unable to find it.
my questions are:

is there any official guidance on migrating from a python-slack-sdk application to bolt-python?
is it possible to run 2 applications concurrently so i can write new features using bolt-python and slowly migrate existing features to bolt-python over time?

Python runtime version
3.9.10
OS info
MacOS/Linux
Requirements
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.

Hi @yashvesikar, thanks for writing in!

is there any official guidance on migrating from a python-slack-sdk application to bolt-python?

No, there isn't but bolt-python project has a plenty of example code and scenario tests. You can learn how to use bolt-python for your use cases by checking those code.

is it possible to run 2 applications concurrently so i can write new features using bolt-python and slowly migrate existing features to bolt-python over time?

The answer depends on the structure of your app but generally running two apps may not be easy. More specifically, having two different Request URLs for interactivity, Events API, and so on is not feasible while you can have a different Request URL for each slash command and external select menu's option URL.
Contrarily, migrating a simple app step by step is much easier. Since bolt-python itself internally depends on slack-sdk, you can use bolt-python handlers only for newly added slash commands, modal submissions, and so on.
If you run your app with Flask, your Flask endpoint can be something like this during the migration period:
from slack_bolt import App
app = App()

@app.event("app_mention")
def event_test(say):
    say("What's up?")

from flask import Flask, request
from slack_bolt.adapter.flask import SlackRequestHandler

flask_app = Flask(__name__)
handler = SlackRequestHandler(app)

@flask_app.route("/slack/events", methods=["POST"])
def slack_events():
    if _is_legacy_endpoint_request(request):
        return _your_own_existing_code_here(request)
    else:
        return handler.handle(request)

I hope this helps.

@seratch thank you for the speedy reply!

while you can have a different Request URL for each slash command and external select menu's option URL.
would you be able to explain this a bit more? my understanding is that an application can only have a single request url.
so based on the sample code you provided above is there a simple way to implement _is_legacy_endpoint_request(request) such that a single endpoint can handle both kinds of requests? or does that function need to be coupled to business logic i.e. something like this for interactive messages?:

@flask_app.route("/slack/events", methods=["POST"])
def slack_events():
    if _is_legacy_endpoint_request(request):
        return _your_own_existing_code_here(request)
    else:
        return handler.handle(request)

def _is_legacy_endpoint_request(request):
    payload = json.loads(request.form["payload"])
    message_type = payload.get("type")
    actions = payload.get("actions")
    if message_type == "block_actions" and actions and actions[0].get("action_id) in {SOME LIST OF ACTION IDS}:
        return True
    return False

my apologies for not mentioning this beforehand (github didn't save my original question 😕) but the application i am considering migrating is quite large and being used in production so uptime is critical for us.
do you have any other suggestions or pitfalls to avoid when considering migrating a large codebase to slack-bolt?
if it would be beneficial to you and your team i am happy to document the process of migrating a large codebase from python-slack-sdk to slack-bolt as long as there is a migration path that is incremental 🙂

@yashvesikar

my understanding is that an application can only have a single request url

Indeed, using a single Request URL for everything is generally recommended as it is easy to manage. However, technically it's possible to use different Request URLs per a Slack Platform feature. You can find Request URL in each feature's configuration part (if you are not sure about this, please go to your Slack App configuration page and visit all the pages there). For instance, if your app provides 3 slash commands, you can use three different endpoints for each if you would like to do. If you would like to handle external select menu at a different path (e.g., /slack/select-menu-options), it's also possible. Similarly, you can go with different ones for Interactivity, Events API, and so on.

_is_legacy_endpoint_request(request) such that a single endpoint can handle both kinds of requests? or does that function need to be coupled to business logic i.e. something like this for interactive messages?:

This depends on how you want to manage your app. If you are using a single Request URL, dispatching requests inside the URL handler. Looking at your pseudo code, perhaps, it would be your situation.

do you have any other suggestions or pitfalls to avoid when considering migrating a large codebase to slack-bolt?

I cannot think of any hardships for the migration but if your app enables the OAuth flow on your way and does not use InstallationStore etc. at all, sharing the installation data with the /slack/events endpoint may require some efforts to make the way to fetch tokens and installation data from your database. If you simply use a single bot token that you've acquired by the steps from "Install the App" button in your app configuration page, no need to worry about this at all.

if it would be beneficial to you and your team i am happy to document the process of migrating a large codebase from python-slack-sdk to slack-bolt as long as there is a migration path that is incremental

Thanks for saying this. We are not planning to add the section to our own documents but sharing your knowledges in your blog would be beneficial for others!
Would you mind closing this issue now? Whenever you get a specific question for the migration, please feel free to create a new question issue for each.

will close the issue for now, i am sure i will have more questions in this journey - thank you very much for the information so far!


[Q]LDAP setup for python3

I have recently updated graphite-web to 1.1.8 from 0.9.x. Since LDAP has stopped working properly. I have python-ldap and openldap installed and local_settings.py is set up for it.  I am using python3. When I try and log in via graphite UI, it says user name and password aren't correct. LDAP was working before the upgrade of graphite-web. Is there something I'm missing?
I have found that editing the ldapBackend.py file from

def authenticate(self, username=None, password=None):
to

def authenticate(self, request, username=None, password=None):
has fixed the issue. Am I missing something or is this file out of date?

Hi @mmueller101 ,
I think it's related not to python3 / python-ldap or openldap but to Django itself.
2.x do not requre request - https://docs.djangoproject.com/en/2.2/ref/contrib/auth/#django.contrib.auth.backends.ModelBackend.authenticate
But 3.x is - https://docs.djangoproject.com/en/3.2/ref/contrib/auth/#django.contrib.auth.backends.ModelBackend.authenticate
Need some work to support both.

Hey @deniszh ,

Hey @deniszh,
Thanks for taking a look at this.


Add more ways to close fullscreen modal

The changelog uses a fullscreen modal. To make it easy for users to exit the modal, add a close (X icon) button to the top right (in addition to the CLOSE) button in the bottom right.
Could also add a back (← icon) button to the top left that does the same thing.

Done in 73598003ec1619c4f54ebd62914b36691e6164f1


mangareader: 2.0.4 -> 2.1.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for mangareader is: Qt manga reader for local files
meta.homepage for mangareader is: https://github.com/g-fb/mangareader
meta.changelog for mangareader is: https://github.com/g-fb/mangareader/releases/tag/2.1.0
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.1.0 with grep in /nix/store/9fxxn7aj408spgclc3cafqxz923l4i72-mangareader-2.1.0
found 2.1.0 in filename of file in /nix/store/9fxxn7aj408spgclc3cafqxz923l4i72-mangareader-2.1.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
mangareader

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/9fxxn7aj408spgclc3cafqxz923l4i72-mangareader-2.1.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A mangareader https://github.com/r-ryantm/nixpkgs/archive/48bfb6645953491bb5e887e589d8292979fd6f99.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/9fxxn7aj408spgclc3cafqxz923l4i72-mangareader-2.1.0
ls -la /nix/store/9fxxn7aj408spgclc3cafqxz923l4i72-mangareader-2.1.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

mangareader

Maintainer pings
cc @zendo for testing.

Result of nixpkgs-review pr 227387 run on x86_64-linux 1

1 package built:

mangareader


Permissions to this repo

I've set this repo so that only @ascii-soup and @martindilling have admin access. The idea being that they are the gatekeepers and only they merge stuff in. I'm pretty sure we agreed they would be in charge of merges at the last meetup.
@garethellis36 has asked for access as well, I'm totally cool with that, but can we have an agreement on whether I should just give everyone access to it, or do we actually like having only the gatekeepers with access.
@garethellis36 did you want to merge permissions or another thing that needed admin privileges?

To be honest I don't see a problem with us that are more active having admin access, at least until it becomes a problem?
I think it's most likely to become a problem when the project is further on, and there are more PRs with potential breaking changes :)


HL7-FHIR-HL7 ORU-R01 Mapping: Device

User Story

As a Sender of ORU-R01 HL7v2 messages to RS,
I expect my HL7v2 messages get delivered to the intended receiver in either the FHIR or HL7v2 format without losing data
Description/Use Case

To ensure RS is mapping ORU-R01 messages losslessly, RS needs to map HL7v2 segment to FHIR resource and FHIR resources to HL7v2 segments as described by the mapping inventory.
This ticket shall focus on creating HL7v2->FHIR and FHIR->HL7v2 mappings for the following resource(s):

Device

Please reference the aforementioned ORU-R01 mapping inventory for guidance on what segments and resources need to be mapped.
Risks/Impacts/Considerations

Dev Notes

Reuse the datatypes that were created as part of epic #11655
Mapping decisions or interpretations made due to ambiguity in the mapping inventory should be documented to enable future follow-up with the owning organization

Acceptance Criteria

[ ] Mappings created for segments/resource
[ ] Decision points documented

Here's the story that would complete SFT -> Device. Moving it to the product backlog

Hey team! Please add your planning poker estimate with Zenhub @adegolier @arnejduranovic @brick-green @jack-h-wang @jalbinson @JFisk42 @mkalish


Hot-reloading TLS certificates

The context
Automatically use new TLS certificate if it is updated on the file system ("hot-reload")
The question
Is it possible to force recreation of the SSL context? The background of my question is that I have a service running that uses server security with client authentication. When the server certificate expires, it automatically gets replaced but clients still see the old certificate. So, is there any way to either force recreation of the SSL context or set a maximum "lifetime" of the context? I didn't find anything about that in the grpc-spring or netty docs, but I'm sure I'm missing something.
The application's environment
Spring-boot service running on k8s.
Which versions do you use?

Spring (boot): 3.2.5
grpc-java: 1.60.0
grpc-spring-boot-starter: 3.1.0-RELEASE
java: version + architecture (64bit?) java 17, amd64

Please ask this question in the https://github.com/grpc/grpc-java repo, as the feature has to be supported there first.
If they have support for that, we can add the relevant config for that here.

Could you please create a PR and contribute this feature?


Persist active onion circuits before forwarding

Issue
Currently within the daemon, the htlcSwitch manages the teardown/setup of onion-circuits generated during the forwarding of multi-hop payments. However, as implemented currently, a well timed daemon restart may lead to possibly loss of funds. This is due the fact that the onion circuits are currently kept in volatile memory, and not persisted to disk before forwarding.
Onion circuits are uniquely defined with the following struct:
type onionCircuit struct {
    rHash         [32]byte
    clearNode  *btcec.PublicKey
    settleNode *btcec.PublicKey
}

where:

clearNode is the node that originally forwarded the HTLC to us, clearing it on the incoming channel
and settleNode is the node we sent the outgoing HTLC to

Once the settleNode sends us an HTLC settle message, we the switch needs to forward the settle message to the clearNode in order to claim the funds and in the process gain the fee related to the HTLC.
Steps to Completion
Persist the htlcManager's paymentCircuits map to disk. Ideally, the map should be removed all together and modifications to the prior map should instead take the form of disk accesses in order to side-step any potential consistency issues related to maintain the state both in memory and on disk.

Will take this one.

will take this one

hehe, beginner issue

LOL, dem edge cases tho
On Mar 7, 2018 10:33 AM, "Johan T. Halseth"<EMAIL_ADDRESS>wrote:
hehe, beginner issue
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/lightningnetwork/lnd/issues/80#issuecomment-371176889,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA87LpI1dlNxf0Psi-J8Xo-HcHEgqf6iks5tb_22gaJpZM4K6MuS
.


chore(master): release 0.18.1

:robot: I have created a release beep boop
0.18.1 (2023-01-20)
Bug Fixes

upgrade bee to apply hotfix (#316) (44c6dc3)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/ethersphere/swarm-desktop/releases/tag/untagged-f35ece2f128745567cd9 :sunflower:


Incorporate OSSEM

Framework for normalizing logs.
https://github.com/Cyb3rWard0g/OSSEM

Hello @Beercow ! Thank you for suggestion. We have some references to this repo (for example, here), and we are going to use it in the future.

A couple of months ago, in February 2020, randomly checking #ossem channel in Hunters Forge slack workspace for any updates on the topic, we discovered an invitation to a web call for discussion of OSSEM updates, as well as OSSEM -> YAML translation scripts.
There were 3-4 YAML-structured templates presented, and some of them looked like they can fulfill our needs. We've participated in it, provided our feedback.
I am not quite sure that the final YAML template is actually one of those we voted for. The main reason is that we need most of the field that we have in our Data Needed template, but some of the presented templates were not including some of these fields.
So, this topic needs to be investigated.
If format fits — let's incorporate it.
If not — let's provide details and try to change the format.
I believe that if we will provide a transparent and detailed explanation of what is required from our side, Roberto and guys who were working on YAML translation script will change it, or apply our changes that we will push to their md->yaml translation scripts using Pull Request here on GitHub.


Fix TouchableOpacity componentDidUpdate causing an excessive number of pending callbacks

Summary
The commit https://github.com/facebook/react-native/commit/3eddc9abb70eb54209c68aab7dbd69e363cc7b29 included on v0.69 introduced a wrong if statement inside the componentDidUpdate function of the TouchableOpacity component. As this if statement always evaluates to true ((true || false) !== undefined) we end up making unnecessary calls to the _opacityInactive method every time the component props changes, e.g. every time a <Text> inside the TouchableOpacity changes we call this function over and over, and this has been causing some performance issues on big lists.
This PR fixes this problem by adjusting the componentDidUpdate function to only call  _opacityInactive when necessary.
Closes https://github.com/facebook/react-native/issues/34442
Closes https://github.com/facebook/react-native/issues/32476
Changelog
[General] [Fixed] - Fix TouchableOpacity componentDidUpdate causing an excessive number of pending callbacks
Test Plan

Open the RNTester app and navigate to the Touchable* and onPress page
Test the TouchableOpacity component through the many sections

@gabrieldonadel when is this supposed to go live? It's still not in 0.71.2, I still have to use a patch for it... has it been missed maybe and never merged?

@benomatis based on the changelog below this will most likely be released on 0.72 https://github.com/facebook/react-native/blob/728eef3f097132d4cdd1cd1360582a031736b26f/CHANGELOG.md?plain=1#L206

thank you @gabrieldonadel

@benomatis : I just installed 0.71.4, and it seems to have the fix, FWIW. (Thanks, @gabrieldonadel, for fixing this. Spent a long time debugging my app until I saw this on the interwebs.)

@fivecar Yes, I can confirm it's added to 0.71.4, thank you!

I am experiencing some issues opening a transparent modal with the keyboard opened.
Open keyboard -> Press TouchableOpacity button -> Open transparent modal -> Keyboard is implicitly dismissed (automatically) -> Close modal -> Keyboard is opened again automatically with buggy behaviour -> ERROR!
   <Modal
      transparent
      visible={visible}
      animationType="fade"
      onRequestClose={onClose}
    >
      <View style={containerStyle}>
        {renderBlur()}
        {renderMain()}
        {renderCloseButton()}
      </View>
    </Modal>

This is the error I am getting:
Excessive number of pending callbacks: 501. Some pending callbacks that might have leaked by never being called from native code: {"1506":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1509":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1512":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1515":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1518":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1521":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1524":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1527":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1530":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1533":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1536":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1539":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1542":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1545":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1548":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1551":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1554":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1557":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1560":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1563":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1566":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1569":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1572":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1575":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1578":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1581":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1584":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1587":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1590":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1593":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1596":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1599":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1602":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1605":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1608":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1611":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1614":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1617":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1620":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1623":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1626":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1629":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1632":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1635":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1638":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1641":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1644":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1647":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1650":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1653":{"module":"UIManager","method":"configureNextLayoutAnimation"},"...(truncated keys)...":451}

As a workaround, I am replacing the TouchableOpacity with the one provided by react native gesture handler.
Any ideas?

I am experiencing some issues opening a transparent modal with the keyboard opened. Also, I am listening to keyboard updates with 'will' and not 'did'. If I only listen 'didShow/didHide' events, the error disappear.
Open keyboard -> Press TouchableOpacity button -> Open transparent modal -> Keyboard is implicitly dismissed (automatically) -> Close modal -> Keyboard is opened again automatically with buggy behaviour -> ERROR!
   <Modal
      transparent
      visible={visible}
      animationType="fade"
      onRequestClose={onClose}
    >
      <View style={containerStyle}>
        {renderBlur()}
        {renderMain()}
        {renderCloseButton()}
      </View>
    </Modal>

This is the error I am getting:
Excessive number of pending callbacks: 501. Some pending callbacks that might have leaked by never being called from native code: {"1506":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1509":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1512":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1515":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1518":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1521":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1524":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1527":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1530":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1533":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1536":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1539":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1542":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1545":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1548":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1551":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1554":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1557":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1560":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1563":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1566":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1569":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1572":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1575":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1578":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1581":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1584":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1587":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1590":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1593":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1596":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1599":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1602":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1605":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1608":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1611":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1614":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1617":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1620":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1623":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1626":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1629":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1632":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1635":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1638":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1641":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1644":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1647":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1650":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1653":{"module":"UIManager","method":"configureNextLayoutAnimation"},"...(truncated keys)...":451}

As a workaround, I am replacing the TouchableOpacity with the one provided by react native gesture handler.
Any ideas?

hey Victorio, have you found a solution? I'm running into this same exact error

I am experiencing some issues opening a transparent modal with the keyboard opened. Also, I am listening to keyboard updates with 'will' and not 'did'. If I only listen 'didShow/didHide' events, the error disappear.
Open keyboard -> Press TouchableOpacity button -> Open transparent modal -> Keyboard is implicitly dismissed (automatically) -> Close modal -> Keyboard is opened again automatically with buggy behaviour -> ERROR!
   <Modal
      transparent
      visible={visible}
      animationType="fade"
      onRequestClose={onClose}
    >
      <View style={containerStyle}>
        {renderBlur()}
        {renderMain()}
        {renderCloseButton()}
      </View>
    </Modal>

This is the error I am getting:
Excessive number of pending callbacks: 501. Some pending callbacks that might have leaked by never being called from native code: {"1506":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1509":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1512":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1515":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1518":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1521":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1524":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1527":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1530":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1533":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1536":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1539":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1542":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1545":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1548":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1551":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1554":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1557":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1560":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1563":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1566":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1569":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1572":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1575":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1578":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1581":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1584":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1587":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1590":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1593":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1596":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1599":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1602":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1605":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1608":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1611":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1614":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1617":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1620":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1623":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1626":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1629":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1632":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1635":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1638":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1641":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1644":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1647":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1650":{"module":"UIManager","method":"configureNextLayoutAnimation"},"1653":{"module":"UIManager","method":"configureNextLayoutAnimation"},"...(truncated keys)...":451}

As a workaround, I am replacing the TouchableOpacity with the one provided by react native gesture handler.
Any ideas?

hey Victorio, have you found a solution? I'm running into this same exact error

Temporary fix for me was to remove 'KeyboardAvoidingView' , as issue was only on iOS with this component


Unicode support

Add unicode support
Xterm.js supports unicode, yet in the WebSSH I only see a bunch of '?'s

As a non-English speaker, it's a major flaw for me.
BTW, maybe I shouldn't request two features at once, but the ability to generate SSH key pairs will be sweet.
Otherwise the app fits my appetite really well.

Hello @VermiIIi0n 👋
Thank you a lot for your feedback!
I will fix unicode flaw asap.
Key generation is already planned
Have a nice day ☀

Thank you for your instant response!
Can't wait to see it, have a nice day👏

Hello @VermiIIi0n 👋
Could you try WebSSH 19.5 latest beta ?
https://testflight.apple.com/join/QSrBK59z

It now works perfectly, thank you for your efforts!

You're Welcome
Thank you a lot for your feedback @VermiIIi0n 🙏


⚠ Bofrost.ch has degraded performance

In 0bf95cc, Bofrost.ch (https://www.bofrost.ch) experienced degraded performance:

HTTP code: 200
Response time: 1490 ms

Resolved: Bofrost.ch performance has improved in 17f726e.


[LIGHTNODE] Add the promo code discount to the price breakdown when purchasing a LightNode

[x] As a user in the purchase flow, I want to see the discount applied by my promo code reflected in the price breakdown.

Designs: https://www.figma.com/design/yC7zuL9bFx9yvPd2aBalX6/Paloma-Light-Sale-Node?node-id=2658-419&t=TcLBOoLw3yTS7tpH-4

Fixed with https://github.com/palomachain/website/pull/177

Shipped.


[Bug] Edit Task (Competition Builder): Media Item lookup

Edit Task (Competition Builder): Media Item lookup  seems broken, when editing an existing task (VKIS). This results in broken task -> broken competition and therefore, unserializable competition in the backend

Fixed!