"error": "Cannot retry tower. Expected tower status 'unreachable' or 'subscription error'. Received temporarily unreachable"

I recently started using teos with my cl, using the watchtower plugin. I had some trouble understanding the configuration:
[teos]
subscription_slots =<PHONE_NUMBER>
max_appointments   = 1
expiry_delta = 6
min_to_self_delay = 20
wsgi = waitress

As the default 100 appointments were exhausted within an hour or so. This config gives me on the client:
available_slots":<PHONE_NUMBER>
But after filling ~3500 of those I get with listtowers on the client:
         "status": "temporarily unreachable",
         "available_slots":<PHONE_NUMBER>,
         "pending_appointments": [
            "[...]",

What is the meaning of subscription_slots and max_appointments? Why is the tower unreachable, when a TCP connection can easily be made from the client? I guess I'm missing something here.

What is the meaning of subscription_slots and max_appointments? Why is the tower unreachable, when a TCP connection can easily be made from the client? I guess I'm missing something here.

subscription_slots is the amount of appointment slots (channel updates) that the user has available within the tower, and can be renewed by just re-registering with the tower,
max_appointments is the total number of appointments the tower is willing to be watching at the same time, kind of an upper bound on the memory it is willing to consume (this is something we'll be getting rid of for the next version).
The tower being temporarily unreachable should mean that it was unreachable the last time the client tried to send an update to it. If that happens, a retry strategy is started in background with an exponentially increasing delay. If the retry strategy fails, the status will change to unreachable and you'll be able to manually retry using retrytower

Checking the config you shared, looks like max_appointments  = 1, so the tower may have only accepted a single appointment and started rejecting after that. You can check that from the tower-side by running teos-cli get_all_appointments

Okay, that helped a lot. I tried re-registering before, but with max_appointments   = 1 this was hopeless and gave me an error about the tower not being reachable.

Glad to hear you managed to fix it. Feel free to reopen or create any other issue if you find something odd, feedback is really appreciated.

Thanks. And here I am again :(
Before I got a warning from my monitoring of 23 pending appointments. Now when checking it's down to 1, but this is still unresolved:
$ lightning-cli gettowerinfo $id | jq '.appointments, .pending_appointments, .invalid_appointments, .misbehaving_proof | length'
4231
1
0
0
$ lightning-cli retrytower $id
{
   "error": "Cannot retry tower. Expected tower status 'unreachable' or 'subscription error'. Received reachable"
}

If I grep for the locator of the pending appointment in teos.log it gives no result. Yet other new appointments get added. Restarting lightningd (by stopping the important-plugin "watchtower.py") did not change this, restarting teosd neither.

That's pretty weird.
Can you look for retry logs on the node side? Just to check if the client is trying to resend the data to the tower of if has gotten stuck because of some unhandled reason.
Something on the lines of:
plugin-watchtower.py: Retry [i] failed for tower <locator>, backing off

Okay, I found some insight in the logs!
The appointment that is still pending was the very last appointment that went to pending before the tower accepted appointments again.
2022-02-05T03:55:17.432Z INFO    plugin-watchtower.py: Sending appointment 05d7112c1bf6347b2b08ebd043d513b8 to $id
2022-02-05T03:55:17.912Z INFO    plugin-watchtower.py: Appointment accepted and signed by $id
2022-02-05T03:55:17.912Z INFO    plugin-watchtower.py: Remaining slots: 159996294
2022-02-05T03:55:17.912Z INFO    plugin-watchtower.py: Start block: 721858
2022-02-05T03:55:17.915Z INFO    plugin-watchtower.py: Adding tower to Tower's db (id=$id)
2022-02-05T03:55:24.873Z INFO    plugin-watchtower.py: Sending appointment 27e57d3f961f6c8fe38a30dfbd1d367a to $id
2022-02-05T03:55:25.369Z INFO    plugin-watchtower.py: Appointment accepted and signed by $id
2022-02-05T03:55:25.369Z INFO    plugin-watchtower.py: Remaining slots: 159996293
2022-02-05T03:55:25.369Z INFO    plugin-watchtower.py: Start block: 721858
2022-02-05T03:55:25.369Z INFO    plugin-watchtower.py: Adding tower to Tower's db (id=$id)
2022-02-05T03:55:25.376Z INFO    plugin-watchtower.py: Sending appointment b952ba0c9b3a62789ef3f4cc45ceff63 to $id
2022-02-05T03:55:25.814Z INFO    plugin-watchtower.py: Appointment accepted and signed by $id
2022-02-05T03:55:25.814Z INFO    plugin-watchtower.py: Remaining slots: 159996292
2022-02-05T03:55:25.814Z INFO    plugin-watchtower.py: Start block: 721858
2022-02-05T03:55:25.818Z INFO    plugin-watchtower.py: Adding tower to Tower's db (id=$id)
2022-02-05T03:55:32.172Z INFO    plugin-watchtower.py: Sending appointment c6e28d0954777f5a64a5cb9ad83d4f4a to $id
2022-02-05T03:55:48.777Z INFO    plugin-watchtower.py: $id cannot be reached
2022-02-05T03:55:48.778Z INFO    plugin-watchtower.py: Adding c6e28d0954777f5a64a5cb9ad83d4f4a to pending
2022-02-05T03:55:48.782Z INFO    plugin-watchtower.py: Adding tower to Tower's db (id=$id)
2022-02-05T03:55:48.886Z INFO    plugin-watchtower.py: Sending appointment c6e28d0954777f5a64a5cb9ad83d4f4a to $id

# next line is the one still pending, also only mention of this appointment in logs, logs should be complete since starting to use teos:

2022-02-05T03:55:48.886Z INFO    plugin-watchtower.py: $id is temporarily unreachable. Adding 80fcde148642cc0eef013fe1b15b1862 to pending

2022-02-05T03:55:48.886Z INFO    plugin-watchtower.py: Adding tower to Tower's db (id=$id)
2022-02-05T03:55:49.196Z INFO    plugin-watchtower.py: Appointment accepted and signed by $id
2022-02-05T03:55:49.197Z INFO    plugin-watchtower.py: Remaining slots: 159996291
2022-02-05T03:55:49.197Z INFO    plugin-watchtower.py: Start block: 721858
2022-02-05T03:55:49.201Z INFO    plugin-watchtower.py: Adding tower to Tower's db (id=$id)
2022-02-05T03:55:58.900Z INFO    plugin-watchtower.py: Sending appointment 63b5ac83326c2e72752af10d445b25d8 to $id
2022-02-05T03:55:59.259Z INFO    plugin-watchtower.py: Appointment accepted and signed by $id
2022-02-05T03:55:59.259Z INFO    plugin-watchtower.py: Remaining slots: 159996290
2022-02-05T03:55:59.259Z INFO    plugin-watchtower.py: Start block: 721858
2022-02-05T03:55:59.263Z INFO    plugin-watchtower.py: Adding tower to Tower's db (id=$id)
2022-02-05T03:57:59.761Z INFO    plugin-watchtower.py: Sending appointment 6cf067ad238af3cdf5b3f9b1f03700a8 to $id
2022-02-05T03:58:00.147Z INFO    plugin-watchtower.py: Appointment accepted and signed by $id
2022-02-05T03:58:00.147Z INFO    plugin-watchtower.py: Remaining slots: 159996289
2022-02-05T03:58:00.147Z INFO    plugin-watchtower.py: Start block: 721858
2022-02-05T03:58:00.151Z INFO    plugin-watchtower.py: Adding tower to Tower's db (id=$id)
2022-02-05T03:58:00.158Z INFO    plugin-watchtower.py: Sending appointment 5c3932c77be5c5df85d4561ce9159a78 to $id
2022-02-05T03:58:00.541Z INFO    plugin-watchtower.py: Appointment accepted and signed by $id
2022-02-05T03:58:00.541Z INFO    plugin-watchtower.py: Remaining slots: 159996288
2022-02-05T03:58:00.541Z INFO    plugin-watchtower.py: Start block: 721858
2022-02-05T03:58:00.545Z INFO    plugin-watchtower.py: Adding tower to Tower's db (id=$id)

Umm, OK, so if I got this right the appointment didn't go trough, the tower was flagged as temporarily unreachable. After that, and without having sent the pending appointment (and maintaining the tower flagged as temporarily unreachable) new appointments were created and are being sent to the tower correctly.
Is that right? If so, can you run:
lightning-cli getappointment <tower_id> <locator>
So we can double check that the tower never received that appointment? If that's the case, the returned status should be not_found.
If the tower has indeed not received the appointment, that a case I've never seen before. The tower plugin should have not proceeded with pending appointments to send (actually it should not be sending anything to a temporarily unreachable flagged until that's flagged back to reachable). If the tower has received the appointment, we may be in the case where the appointment was not properly deleted from the node's database once handed to the tower.
Btw, feel free to join Slack if you'd like, interaction may be smoother: https://join.slack.com/t/talaialabs/shared_invite/zt-syx8f3hi-XqurRIIQEm7YHw9I9hK7UA

{
"locator": "80fcde148642cc0eef013fe1b15b1862",
"status": "not_found"
}
so, not on teos...

Ok, so there are three solutions I can think of, from less to more intrusive:

Turn off teos and let the plugin mark it as unreachable, then retry manually. By turning it off you should see some of the retry messages I was mentioning in the node's logs when new channel updates are performed and the tower cannot be reached. If the retry strategy is not triggered, that could mean the client is in an iffy state and may need to be manually reset. See next options.

Create a hotfix with a new RPC command that let you pull the data from the tower client database and push it to the tower. I could code this quite easily.

Use the testing client with the data provided by the tower client about the pending appointment to manually send the data to the tower. Then delete the data from the client's database (I can provide a script for that).

The last two options will require the lightning node to be stopped, given the database is locked by the node's process.

Turning off teos until the client marked it as down resolved it. Thanks.

Glad to hear, feel free to reopen if it happens again.

I'm going to reopen this since I think I found a way to consistently reproduce the "get stuck into temporary_unreachable".

nvm, I couldn't actually reproduce this.


Invalid regular expression: Invalid escape

Version: 1.47.2 (user setup)
Commit: 17299e413d5590b14ab0340ea477cdd86ff13daf
Date: 2020-07-15T18:22:06.216Z
Electron: 7.3.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18362

Steps to Reproduce:

Use this regex pattern:

```([\w\+\=\,\ \-\*\'\"]*)```

This pattern works online (using PCRE and Javascript as compilers) here: https://regex101.com/r/lRpdUq/3

Does this issue occur when all extensions are disabled?: Yes

This is probably from the Rust regex engine. It is stricter about unnecessary escapes. The quotes and the space, for example, don't need to be escaped.

I realize the escapes aren't necessary, and even without them I get the same error:
```([\w\+\=, \-\*'"]*)```

Also the =


The release is said to be support mono.cecil 0.10

The release is said to be support mono.cecil 0.10.
But I will get ObjectDisposedException.
I want to make a Chinese patcher beside it.
But the Unity3D app is with Mono.Cecil beside it.
And it's 0.10.1 version.

Greetings!
Cecil.Inject has indeed been tested to work with 0.10. Could you provide more information? What did you try to do? Maybe some example code?
Could you also try this version out:
Cecil.Inject_test.zip
It's simply a recompilation of the release DLL except with 0.10.3 as the target version.

Hi. Did you test with 0.10.1?
I tried with 0.10.1. I get ObjectDisposedException while I call injectDefinition.Inject();
It says it can't access to closed file (The hint is in Chinese, it's similar meaning in English).

AssemblyDefinition assemblyDefinition = AssemblyLoader.LoadAssembly("VRoidChineseHook.dll");
            AssemblyDefinition targetAssembly = AssemblyLoader.LoadAssembly("Assembly-CSharp.dll");
            MethodDefinition hookUpdateCurrentUiCulture = assemblyDefinition.MainModule.GetType("VRoidChineseHook.VRoidChineseHookClass").GetMethod("HookUpdateCurrentUICulture");
            MethodDefinition hookLanguagePreferencesDropdownItemListGet = assemblyDefinition.MainModule.GetType("VRoidChineseHook.VRoidChineseHookClass").GetMethod("HookLanguagePreferencesDropdownItemListGet");
            MethodDefinition updateCurrentUiCulture = targetAssembly.MainModule.GetType("VRoidStudio.UICulture.Translator").GetMethod("UpdateCurrentUICulture");
            TypeDefinition type = targetAssembly.MainModule.GetType("VRoidStudio.GUI.Welcome.WelcomeController");
            MethodDefinition method = type.GetMethod("get_LanguagePreferencesDropdownItemList");
            InjectionDefinition injectorTranslator = new InjectionDefinition(updateCurrentUiCulture, hookUpdateCurrentUiCulture, InjectFlags.None, null, Array.Empty<FieldDefinition>());
            InjectionDefinition injectionDefinition = new InjectionDefinition(method, hookLanguagePreferencesDropdownItemListGet, InjectFlags.ModifyReturn, null, Array.Empty<FieldDefinition>());
            injectorTranslator.Inject();
            injectionDefinition.Inject();

It reports the exception with the first Inject.

There's no problem with 0.9.6.

Ah, I see the problem now.
Please try out this version instead and see if it helps
Cecil.Inject_fix.zip

Thank you. It does help.

I see. Thanks for the information. I'm going to update the official build soon to fix the problem.
Until that, I'm going to keep this issue open.

But it seems that I can't write back to the same file now.
Any suggestion? Or should I copy one to inject and write back?

If you need more precise control over files, I suggest using AssemblyDefinition.ReadAssembly instead of AssemblyLoader.LoadAssembly. With that you can load the file into memory, patch it and write to the original file.

It seems that I can't write back to the same file now. Can you have a test on it?
Temporarily I'll read the backup and write back to the original.

That's a problem with Cecil, not Cecil.Inject. If you just pass the filename to AssemblyDefinition.ReadAssembly (or to AssemblyLoader.LoadAssembly), it will open a file stream to read the assembly from that. While the file stream is open, you cannot write to the same file.
The only way to make it work is to either rename the assembly before loading it (with File.Move) or to load all of it in memory with something like
var assembly = AssemblyDefinition.ReadAssembly(new MemoryStream(File.ReadAllBytes("assembly.dll")));

Unfortunately that's how computers work -- you cannot write to a file that is opened at the same time (with some exceptions, but in case of Cecil it has to lock the file you're reading).

Thank you. I see.


Fix listing and creating cluster containers inside projects

This fixes #5163 and also a couple of other bugs that I've noticed while working on it:

it was not possible to create a project-bound container on a node using a client connected to another node

images were not transferred correctly between nodes, when bound to projects

There are likely other bugs around projects when used with clustering, but this is a good first pass.

Server side looks good, client side feels like it should be using setQueryAttributes() rather than add more specific URL logic to those functions.


Use proxy env variables if explicit proxy not set

With this change, users can use the de facto standard HTTP(S)_PROXY environment variables instead of having to specify them manually.
See https://golang.org/pkg/net/http/#ProxyFromEnvironment
I think using the environment variables is what you often get by default?? (sorry, I'm new to go)

@somashekhar Thanks for looking.

Would recommend by default proxy should be taken from environment variable. Allow being overridden when explicitly given by an user through a client.

Unless I'm misunderstanding, I think that's exactly what this PR does. If cfg.ProxyUrl has been explicitly set, it'll be used, otherwise the environment variables will be used (if set obviously).

Unless I'm misunderstanding, I think that's exactly what this PR does. If cfg.ProxyUrl has been explicitly set, it'll be used, otherwise the environment variables will be used (if set obviously).

My suggestion was, let us initialize the http.Transport  with a default proxy from environment as Proxy: ProxyFromEnvironment, at https://github.com/infobloxopen/infoblox-go-client/blob/master/connector.go#L131 rather than having it under an else loop.
The way DefaultTransport https://github.com/golang/go/blob/master/src/net/http/transport.go#L43 does it.

Unless I'm misunderstanding, I think that's exactly what this PR does. If cfg.ProxyUrl has been explicitly set, it'll be used, otherwise the environment variables will be used (if set obviously).

Suggesting to consider initializing  http.Transport with Proxy: http.ProxyFromEnvironment at https://github.com/infobloxopen/infoblox-go-client/blob/master/connector.go#L131 rather than having it under an else loop.

Unless I'm misunderstanding, I think that's exactly what this PR does. If cfg.ProxyUrl has been explicitly set, it'll be used, otherwise the environment variables will be used (if set obviously).

Suggesting to consider initializing http.Transport with Proxy: http.ProxyFromEnvironment at https://github.com/infobloxopen/infoblox-go-client/blob/master/connector.go#L131 rather than having it under an else loop.

Ah... understood.  I've updated the PR.  Hope that's what you meant! :)
NB. Untested. (I'll verify tomorrow and comment back.)

NB. Untested. (I'll verify tomorrow and comment back.)

Code works fine like this too and is neater.  Thanks for the suggestion.

@somashekhar Thanks for merging this!  No rush, but is there a timeframe for the next release that would include this, so I can create a PR on https://github.com/infobloxopen/terraform-provider-infoblox ?
Thanks.

We are working on some of major features and would be including this particular go client changes along with them.
You can raise a PR if you are working on Terraform side code. If it is this particular changes only then not needed. We would make sure to rebase the code before release.


selections are invisible

When some objects (strand, domain, end, crossover, etc.) are selected, instead of turning pink they become invisible, others are pink as intended.
This does not happen on all selected strands.
Seen on chrome and firefox.

This may be a duplicate of issue #904.


Can't logout when using session-rethinkdb

Starting with the simple-mail example app that comes with Passwordless, I'm readily able to incorporate passwordless-rethinkdbstore. Everything works: hooray!
But when I add session-rethinkdb to my app (to replace the in-memory session store), I lose the ability to log out. I know this is probably not passwordless-rethinkdbstore's fault but I wanted to make absolutely sure before going to bug the session-rethinkdb people, since passwordless-rethinkdbstore is my only use-case for session-rethinkdb.
Here's how I initialize passwordless-rethinkdbstore:
passwordless.init(new RethinkDBStore({host: '<IP_ADDRESS>', port: 28015, db: 'test'}));

And here's how I initialize express-session and session-rethinkdb:
app.use(expressSession({
  secret : '42',
  resave : true,
  saveUninitialized : false,
  store : new RDBStore(
      {
        connectOptions : {db : 'test', host : 'localhost', port : 28015},
        table : 'sessionTest',
        sessionTimeout : 30*86400000,
        flushInterval : 60000
      })
}));

Am I doing something wrong here? I'd prefer to use RethinkDB for sessions, since that's what I'm using for passwordless (and my app).

I wrote this module 8 months ago and found that RethinkDB was way too slow at that point in time so I ended up using Redis for my Passwordless project.  I have not used RethinkDB since so I'm not really familiar with it but I can take a look at this tomorrow.

I can confirm it's happening. I'm investigating myself, but initially, it is properly disposing of the document in the pwdless. Now to wrap my head around how the sessions actually work...

This has been pulled into session-rethinkdb v1.0.6 and there's a pull request for express-session-rethinkdb for v0.1.3. please update to those versions to resolve.

Awesome, thanks @PatrickKennedy!

@PatrickKennedy FTW 😂!


Calculations are almost always way off from actual profits

If you compare the calculations coming from CryptoGramBot with ProfitTrailer or your exchange logs, the profits calculated are almost always different. There have been times where the difference is ridiculous. Below is a typical example though:

This is becuase of DCA in PT. This bot isn't a PT specific bot and the dca strategy isn't in every bot. That said, there are some improvements that can be made to the calculations.
PT profit calculations can be incorrect. Can you please calculate via the exchange output and let me know what you get.


Bump the kernel to 3.18.9 (and AUFS patches to latest 3.18.1+)

Tested and verified to boot up, initialize Docker on AUFS, and run containers properly. :+1:
docker@boot2docker:~$ docker info
Containers: 0
Images: 0
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: tmpfs
 Dirs: 0
Execution Driver: native-0.2
Kernel Version: 3.18.9-tinycore64
Operating System: Boot2Docker 1.5.0 (TCL 5.4); master : 175488c - Mon Mar  9 16:17:41 UTC 2015
CPUs: 1
Total Memory: 3.868 GiB
Name: boot2docker
ID: 34TC:BZMZ:5D6H:YFZD:TVBQ:RZG7:V2QT:7PXM:6KTJ:P7MM:TX46:G5A5
Debug mode (server): true
Debug mode (client): false
Fds: 11
Goroutines: 15
EventsListeners: 0
Init Path: /usr/local/bin/docker
Docker Root Dir: /var/lib/docker
docker@boot2docker:~$ docker run --rm hello-world
Unable to find image 'hello-world:latest' locally
511136ea3c5a: Pull complete
31cbccb51277: Pull complete
e45a5af57b00: Pull complete
hello-world:latest: The image you are pulling has been verified. Important: image verification is a tech preview feature and should not be relied on to provide security.
Status: Downloaded newer image for hello-world:latest
Hello from Docker.
This message shows that your installation appears to be working correctly.

To generate this message, Docker took the following steps:
 1. The Docker client contacted the Docker daemon.
 2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
    (Assuming it was not already locally available.)
 3. The Docker daemon created a new container from that image which runs the
    executable that produces the output you are currently reading.
 4. The Docker daemon streamed that output to the Docker client, which sent it
    to your terminal.

To try something more ambitious, you can run an Ubuntu container with:
 $ docker run -it ubuntu bash

For more examples and ideas, visit:
 http://docs.docker.com/userguide/
docker@boot2docker:~$ docker run -it --rm busybox
Unable to find image 'busybox:latest' locally
df7546f9f060: Pull complete
ea13149945cb: Pull complete
4986bf8c1536: Pull complete
511136ea3c5a: Already exists
busybox:latest: The image you are pulling has been verified. Important: image verification is a tech preview feature and should not be relied on to provide security.
Status: Downloaded newer image for busybox:latest
/ # ping google.com
PING google.com (<IP_ADDRESS>): 56 data bytes
qemu: terminating on signal 2

Updated to include a guest additions bump too.

noice - LGTM

oh - did you forget to update the docs too? :p

docs are also updated now

LGTM


Create fileListItem component in order to easily add styles to span tag

This PR adds the ability to define classes on the <span> tag inside a FileItem on a <FormKit type="file"> by using the fileListItem class config property.

@luan-nk-nguyen Done 👍

Thanks @santi


Can't calibrate (anymore)

seems to have happened out of the sudden. Not sure if something in the system was changed. Calibration page shows up, but after clicking on the "Start-calibrate" but no further output. Some pages load, but /new and  /calibrate seem only to work partly.
journalctl -u folk -f
Okt 29 21:02:42 bwow make[3062]: key "protocols" not known in dictionary
Okt 29 21:02:42 bwow make[3062]:     while executing
Okt 29 21:02:42 bwow make[3062]: "dict get $res protocols"
Okt 29 21:02:42 bwow make[3062]:     (procedure "::websocket::test" line 19)
Okt 29 21:02:42 bwow make[3062]:     invoked from within
Okt 29 21:02:42 bwow make[3062]: "::websocket::test $::serverSock $chan "/ws" $headers"
Okt 29 21:02:42 bwow make[3062]:     (procedure "handleRead" line 58)
Okt 29 21:02:42 bwow make[3062]:     invoked from within

Hello -- did it previously work on the same system? Have you installed the tcllib package at some point? (that package may break Folk)
On Wed, Oct 30, 2024, at 3:17 AM, breezahbu wrote:

seems to have happened out of the sudden. Not sure if something in the system was changed. Calibration page shows up, but after clicking on the "Start-calibrate" but no further output. Some pages load, but /new and /calibrate seem only to work partly.
journalctl -u folk -f
Okt 29 21:02:42 bwow make[3062]: key "protocols" not known in dictionary
Okt 29 21:02:42 bwow make[3062]: while executing
Okt 29 21:02:42 bwow make[3062]: "dict get $res protocols"
Okt 29 21:02:42 bwow make[3062]: (procedure "::websocket::test" line 19)
Okt 29 21:02:42 bwow make[3062]: invoked from within
Okt 29 21:02:42 bwow make[3062]: "::websocket::test $::serverSock $chan "/ws" $headers"
Okt 29 21:02:42 bwow make[3062]: (procedure "handleRead" line 58)
Okt 29 21:02:42 bwow make[3062]: invoked from within
—
Reply to this email directly, view it on GitHub https://github.com/FolkComputer/folk/issues/178, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAXUWIDPHTKCJDITQHKJCDZ57UM7AVCNFSM6AAAAABQ2VLJQ2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGYZDEMRTHEZTENA.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

It did and I did. "apt-cache remove tcllib" did the trick. Not sure, but that may have been installed for troubleshooting purposes. Many thanks, now I can continue with one of the most fun and inspiring systems I have seen for a long time. Thanks for that too.


Add lists (ul, ol) to DOCX parser

See http://officeopenxml.com/WPnumbering.php
This may be a bit harder, because list/layer definitions are in special blocks (in other files?).

DocX does not exist anymore


Update beachfront doc

Removes note about video only support. The beachfront bidder will also support banner ads.

waiting on PBJS PR

released in PBJS 1.5


🐞 - [v3] addon-commerce still requires maskito ^1.9.0

Playground Link
No response
Description
Maskito version requirement should be updated in addon-commerce v3:
https://github.com/taiga-family/taiga-ui/blob/3499731441325c164fc58423d2d36abc7dfec168/projects/addon-commerce/package.json#L21
Angular version
17.3.6
Taiga UI version
3.76.0
Which browsers have you used?

[X] Chrome
[ ] Firefox
[ ] Safari
[ ] Edge

Which operating systems have you used?

[ ] macOS
[X] Windows
[ ] Linux
[ ] iOS
[ ] Android

We cannot use Taiga@v3 and Maskito@v2. They are incompatible – Taiga@v3 is based on assumption that maskito has initial calibration (only Maskito@v1 has the such behavior).
Learn more:

https://github.com/taiga-family/taiga-ui/pull/6663

Maskito's version will be bumped later in upcoming Taiga@v4.

Upcoming Taiga@v4
https://github.com/taiga-family/taiga-ui/blob/99ab5ab6c1b79b03d8b8a25e2e78cccb1d277e76/projects/addon-commerce/package.json#L20-L22


Function skip_item() in PETRgraph.py is, at best, specific to English

but more generally looks like a debugging function (I think it was Clayton's, not mine), as "DUCATS" were a valued item produced by those lovable bankers in the Venetian Republic during medieval times, but haven't been in circulation for a century or more. And the rest of the function is definitely specific to English (but probably shouldn't be called in that context either)

Have we cut this?
On Tue, Oct 23, 2018, 14:25 Philip Schrodt<EMAIL_ADDRESS>wrote:

but more generally looks like a debugging function (I think it was
Clayton's, not mine), as "DUCATS" were a valued item produced by those
lovable bankers in the Venetian Republic during medieval times, but haven't
been in circulation for a century or more. And the rest of the function is
definitely specific to English (but probably shouldn't be called in that
context either)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/openeventdata/UniversalPetrarch/issues/50, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AJrP1hN86qEc_xpN-KrpSNbLgRk4m9iGks5un20hgaJpZM4X2eul
.


Error with upgrade to Franklin 0.10.4

Since updating to 0.10.4, from 0.10.3, I am getting the following error:
julia> serve()
→ Initial full pass...
┌ Franklin Warning: in <index.md>
│ Encountered an issue processing 'index.md' in \OntarioCOVID19\page.
│ Verify, then re-start the Franklin server.
│ The error is displayed below:
│ ErrorException("`envname` called on token of type LX_BEGIN failed to return.")

Note that this is with PkgPage serve

@jebej are you using PkgPage? if so do update it as well as it has a constraint on Franklin https://github.com/tlienart/PkgPage.jl/blob/3ba8eff7a28677f9c960f02c4af517aa8a0b1731/Project.toml#L15
If that doesn't work, please add me to your repo and I'll try to fix things there, I apologise for the inconvenience, this is something that needs to be fixed in PkgPage which I'll do soon.

I am, but for whatever reason PkgPage is stuck at 0.3.3. I'll just put a constraint manually on Franklin in the meantime. Maybe this should have been more than a patch version bump on the Franklin side?

Thanks for the offer to help!

If you activate your package OntarioCOVID19 and do ] add<EMAIL_ADDRESS>then you should be back on track for the time being.
Yeah I knew there was a risk for PkgPage users, I'll try to fix this asap

Hmmm it's not as easy, I'll just fix PkgPage asap. Sorry about that...

aaaah wait no, it's just that PkgPage hasn't been updated properly: https://github.com/JuliaRegistries/General/pull/23043 alright I'll try to fix that first then  will ping here

No worries. Not directly related, but the github workflow still "passed" despite the error:
https://github.com/jebej/OntarioCOVID19/runs/1266496197?check_suite_focus=true
┌ Franklin Warning: in <index.md>
│ Encountered an issue processing 'index.md' in /OntarioCOVID19/page.
│ Verify, then re-start the Franklin server.
│ The error is displayed below:
│ ErrorException("`envname` called on token of type LX_BEGIN failed to return.")
└
┌ Franklin Warning: in <index.md>
│ Encountered an issue processing 'index.md' in /OntarioCOVID19/page.
│ Verify, then re-start the Franklin server.
│ The error is displayed below:
│ ErrorException("`envname` called on token of type LX_BEGIN failed to return.")
└

→ Full pass (with pre-rendering)   [done  10.6s]

Is there a way to make it fail the workflow when the page doesn't work? It looks like the function completed successfully, maybe it shouldn't when an error occurs.

ok https://github.com/JuliaRegistries/General/pull/23043 is merged so now if you just update PkgPage things should hopefully be back to normal.
I'm closing this issue but please do re-open (or open another one) of if you still have an issue. Thanks for heads up!


Provide a parameter in order to decide if None/np.nan should be considered missing value or normal value

Two different concepts:

A missing value should not be used in calculations of entropy or conditional entropies, and should be only used as "last resort" in the feature selection model (Series.mode have a flag to ignore nans)
a "none" level, if considered an acceptable value, should be used in entropy calculations and in the calculation of mode in the feature selection model.

Maybe we just need two parameters: "ignore_missing_values=True" and "missing_value=np.nan". The second can be changed for example to "N/A"


Add map method for changing inputted value

The motivation for this feature is almost same as doc comment of map method.
Although my need is sufficed by this PR, the implementation still has some design issues.
Probably mutate method is necessary
I think it is very common usage for map method to appending some suffix to the inputted String. Writing a mutator instead of a mapper makes this task easy a bit because return value can be omitted.
Execution order of mappers and validators
Imagine the following code
let value = Input::new()
    .validate(v1)
    .map(m)
    .validate(v2)
    .interact_text()
    .unwrap();

The user of dialoguer surely expect that v1 validates input (the raw inputted value) and v2 validates m(input). However, in my implementation, both v1 and v2 validate m(input).
To achieve this, mappers, mutators and validators should be treated as a unified "transformer" type, whose type is FnMut(T) -> Result<T, Error>.
Mapping to a different type
There is no reason to restrict return type of mappers to the same type of input.
To achieve this, map's signature should be
pub fn map<U>(self, mut mapper: impl FnMut(T) -> U + 'a) -> Input<'a, U>

I think it is very misleading that only map method takes self and other ones takes &mut self, so it is good choice to change Input into a consuming builder. However this is a huge breaking change for dialoguer.

Does this update the text on terminal with the new mapped value?

Yes. This change does.

How does this interact with #137?

I think #137 should be achieved by some validation mechanism, not by mapping. Specifically, a user passes a validation function whose type is Fn(&[bool]) -> Result<(), String>, and it checks selections whenever the user changes which one is selected. If it returns Err, the user cannot determine the selections and shows the message in Err such as "When you select A, select B too."
So I don't think my feature need specific consideration for #137.


Text and background color utilities broken in 5.1.3 for print media

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
Trying the same code on v5.0.2 and v5.1.3, when printing colors from text (eg text-dark) and background (eg bg-dark) utilities are ignored in the later version.
I can see in the v5.1 release "Updated .bg-* and .text-* utilities to use CSS variables and new RGB CSS variables for real-time customization".
Could this have somehow broken these utilities when printing using bootstrap "out of the box" (no config, just using the cdn)?
Reduced test cases

      1 of 2

      2 of 2

When trying to print this html using weasy print, colors aren't shown.
What operating system(s) are you seeing the problem on?
macOS
What browser(s) are you seeing the problem on?
Chrome
What version of Bootstrap are you using?
v5.1.3

Bootstrap v5 doesn't support print styles, as mentionned in the v5 migration guide.
No idea what's happening here, but we probably won't do anything regarding this.
I encourage you to share your findings, in case we could effectively deliver an easy fix or if anyone comes across this issue.

Bootstrap v5 doesn't support print styles, as mentioned in the v5 migration guide.

@ffoodd
Yeah, true, maybe I didn't explain the issue clearly.
This happens when printing, independent of media print clauses.
The example case given has no CSS styles defined, just uses bootstrap out of the box.
The color utilities work with no problem on v5.0.2, so I doubt it has any relationship with the mayor version.
Could the issue be related to not defining CSS, and the new RGB CSS variables?

It could, but we won't investigate since we don't aim at supporting print.
If anyone has a suggestion or comes with a fix, we'll have a look.


StructuredOptions: hhl_row_hashing

added hhl_row_hashing option
Default is original row hashing method: hhl_row_hashing=False

interested to know if hll_row_hashing_enabled makes more sense, or something different that what I have


Update current.cursor references to current[cursorStateField]?

Not sure if this was intended, but since the cursorStateField is customizable I figured the references to current.cursor should be changed to current[cursorStateField]. I may not understand the code fully though so apologies if this is there for a reason.
https://github.com/yjs/y-prosemirror/blob/984175f7fd7960b1478f10370829659f001ccd3b/src/plugins/cursor-plugin.js#L127-L132

This is fixed by https://github.com/yjs/y-prosemirror/pull/88

This is fixed by https://github.com/yjs/y-prosemirror/pull/88

See #159 for an attempted fix for this.


Release/2022 07 15 tired turtle

Try out this version of the Hiro Wallet - download extension builds.

Contents:

Nonce refactor: https://github.com/hirosystems/stacks-wallet-web/pull/2511
https://github.com/hirosystems/stacks-wallet-web/issues/1246
https://github.com/hirosystems/stacks-wallet-web/issues/2561
https://github.com/hirosystems/stacks-wallet-web/issues/2500
https://github.com/hirosystems/stacks-wallet-web/issues/2499
https://github.com/hirosystems/stacks-wallet-web/issues/2474
https://github.com/hirosystems/stacks-wallet-web/issues/2572

cc/ @kyranjamie @fbwoolf

@kyranjamie Just as a heads up, this PR needs to be merged in here before we release.
https://github.com/hirosystems/stacks-wallet-web/pull/2574


React Native IOS build not working with nodenv

Hello,
I'm using React Native 0.16.0 and I've found that the build task in Xcode does not use the same path as my terminal. Because of this it is unable to find nodenv and does not use the correct version of nodejs.
I was able to fix this by adding the following to react-native-xcode.sh
export PATH="$HOME/.nodenv/bin:$PATH"
if which nodenv > /dev/null; then eval "$(nodenv init -)"; fi

Is this something that you would like a pull request for, or do you plan on supporting nvm only?
Thanks!

Hi @migeorge -
Personally, I'm not all that familiar with Nodenv, but if it helps newcomers to RN get started easier, I think we'd definitely accept a PR.
Feel free to submit and link it here.

:+1:

#4801 is in master.

#4801 does not work for nodenv installed via homebrew, as binaries are in /usr/loca/bin not the user's homedir.
I fixed this on my own machine by creating a ~/.nodenv/bin dir and symlinking ln -s /usr/local/bin/nodenv ./nodenv
I am not sure if this project wants to check a variety of places for nodenv or submit a patch to homebrew's nodenv package to add this symlink (as i gather from #4801 the bin is expected to be there) or something else.


Text Clipping on labels

On the same page of #2285,  I see that some text-clipping occurs with the labels.

I can't understand why that happens. If more data is added on the X Axis, the chart gets shorter to fit the labels and it works properly. But here it has some clippings
PS. Probably similar to #1849

Funniest part, if I let the vertical gridlines display, it fixes

@nasospsa that was a measuring error when sizing the scale. It was fixed in #2276


Updated

Fixed

why? old url not working?

No

Not working.

@NotReallyShikhar review

@NotReallyShikhar review

Have u checked ?


added new logical order waypoint

Closes #5936
Adds a waypoint to describe logical ordering in if else if statements.
This is my first attempt at making a waypoint so i welcome any critique, suggestion to improve upon it.
Tested locally in chrome.

This is excellent and almost ready to go.
Two minor quibbles:

Technically 10 will return "Greater than 10".  You might change the words to "Greater than 9" or "Greater than or equal to 10"
I'm not 100% certain that the instruction is completely clear:

Change the order of order of logic in the function so that it will evaluate correctly.

Maybe:
> Change the order of order of logic in the function so that the logic returns the correct statements in     all cases

I'm just not sure it's totally clear what is needed.  I'm not firm on that alternate wording.

Also, don't forget to squash your commits.

Thanks for the feedback!
I'll make the changes as soon as I get a chance.

@patsul12 Note:  I only get notified when a new comment is made to an issue, so editing your prior comment does not notify me that a change is ready to go.
Anyway, please address @bugron's concerns and post a new comment and we'll get this merged.

Sorry about that,
Everything should be good to go now, fixed my little typo.

Rad! Thanks for your work on this :+1:

Awesome!


Support React Compiler

React 19 introduces the React Compiler, which does useMemo optimizations to make React applications faster automatically.
It appears that next-yak's css prop does not work well with react compiler.
See these comments.

I took a closer look at the experimental react compiler integration
The React Compiler in Next.js works through the babel-plugin-react-compiler Babel plugin that needs to be the first tool to process your code: https://nextjs.org/docs/app/api-reference/config/next-config-js/reactCompiler
The babel-plugin-react-compiler runs directly inside the babel-loader before the swc-loader (webpack loaders are executed in reverse order):
https://github.com/vercel/next.js/blob/a471b1fcac2ba2bc6d89bfa1fb947891859dbc9a/packages/next/src/build/webpack-config.ts#L568-L570
That means the following code:
import { css } from "next-yak";
import { useSize } from "./useSize";

export const Example = () => {
  const size = useSize();

  return (

      Hello World

  );
};

gets compiled by babel to:
import { c as _c } from "react/compiler-runtime";
import { css } from "next-yak";
import { useSize } from "./useSize";
export const Example = () => {
  const $ = _c(3);
  const size = useSize();
  let t0;
  if ($[0] === Symbol.for("react.memo_cache_sentinel")) {
    t0 = css`
        color: red;
      `;
    $[0] = t0;
  } else {
    t0 = $[0];
  }
  let t1;
  if ($[1] !== size) {
    t1 = Hello World;
    $[1] = size;
    $[2] = t1;
  } else {
    t1 = $[2];
  }
  return t1;
};

And next yak now has to try to make sense of this code:
 if ($[0] === Symbol.for("react.memo_cache_sentinel")) {
    t0 = css`
        color: red;
      `;
    $[0] = t0;
}

You can probably imagine that this is a very very difficult task for next-yak so we won't be able to support it
But maybe @kdy1 might at some point (maybe once the react compiler is stable) ship a SWC version of the react compiler and run it right before the JSX is transformed


Update CustomObject semantics for Value, Text, Dot

This change enables Value and Text to handle boolean values, json null, and strings/numbers respectively. It also enables json null support for the dot operator itself. Allows error values to pass through the dot operator, similar to functions.

    ICustomObject this[int index] { get; }

nit: add comment whether this is 0 or 1-based index?

Refers to: src/libraries/Microsoft.PowerFx.Core/Public/Values/CustomObjectValue.cs:32 in be91902. [](commit_id = be919028a3f2a85531b7d445b4afebbcaea197f4, deletion_comment = False)

    bool TryGetProperty(string value, out ICustomObject result);

Another doc nit: Is the assumption that IsObject is true before calling this?

Refers to: src/libraries/Microsoft.PowerFx.Core/Public/Values/CustomObjectValue.cs:34 in be91902. [](commit_id = be919028a3f2a85531b7d445b4afebbcaea197f4, deletion_comment = False)

    bool TryGetProperty(string value, out ICustomObject result);

Another doc nit: Is the assumption that IsObject is true before calling this?
Refers to: src/libraries/Microsoft.PowerFx.Core/Public/Values/CustomObjectValue.cs:34 in be91902. [](commit_id = be91902, deletion_comment = False)

The error handling pipeline does do a runtime value check.

    protected readonly ICustomObject _impl;

can this be private?

Refers to: src/libraries/Microsoft.PowerFx.Core/Public/Values/CustomObjectValue.cs:35 in 7d7f7a5. [](commit_id = 7d7f7a521b3767468c8e50c8aadd472526211505, deletion_comment = False)

// Value tests

Can we rename this ParseJson.txt?  It's excercising custom objects, but it's really testing the ParseJson impl.

Refers to: src/tests/Microsoft.PowerFx.Core.Tests/ExpressionTestCases/CustomObject.txt:1 in 7d7f7a5. [](commit_id = 7d7f7a521b3767468c8e50c8aadd472526211505, deletion_comment = False)


[autoconf/automake/libtool] Add new port

The tools autoconf and automake are used in vcpkg_*_make, and I want to add these two ports instead of using apt to install them.
Thanks @SeekingMeaning.
Related: #9648.
Note: these 3 ports does not contain any features.

Nice. I would recommend adding libtool as well as it is part of the autotools suite. See https://www.gnu.org/software/automake/faq/autotools-faq.html#What-are-the-_0060_0060Autotools_0027_0027_003f

@JackBoosY Would it be okay to archive this PR for now? We do want to add tools as ports but not likely in the near future.

@dan-shaw Okay, I will not delete this branch until these ports are merged into the main branch.

With host dependencies in vcpkg, does it make sense to revive this PR?
There is a lot of bad UX around bootstrapping with brew, apt or whatever.

@dg0yt  Sooner or later we have to break away from the limitations of apt and brew.


Custom model not being used in UI when modelOptions is changed in Node API setup

Title: Custom model not being used in UI when modelOptions is changed in Node API setup

Description:
I changed modelOptions.temperature to modelOptions in the Node API setup, as I wanted to use a custom model. However, when I set up a custom model via the UI in PanadoraAI, it still defaults to the 3.5-turbo model. I understand that 3.5-turbo is the fallback model, but I would like the UI to override this when the modelOptions are changed.
Steps to reproduce:

Change modelOptions.temperature to modelOptions in the Node API setup.
Set up a custom model via the UI in PanadoraAI.
Observe that the model still defaults to 3.5-turbo.

Expected behavior:
When a custom model is set up in the UI, it should use the provided model configuration as specified in the modelOptions.
Actual behavior:
Despite changing the modelOptions in the Node API setup, the UI still defaults to the 3.5-turbo model.
Additional context:
I would like the UI to reflect the custom model configuration specified in the modelOptions and not use the fallback 3.5-turbo model when I have set up a custom model.

Please let me know if there is a workaround or if this issue is being addressed in a future update. Thank you!

Okay, we can rule that out as an issue with PandoraAI. I'll transfer this issue to node-chatgpt-api.
One last thing, can you completely rebuild the docker image/container (after you change the settings back to how it was before) and see if that helps? Just want to rule out that you're running an older version, as someone else had an issue where they pulled the latest version, but their docker image was still on the older version.

each of these test cases were dont from a full clean deployement (deleting image of the package along with docker ps instance)

each of these test cases were done from a full clean deployment (deleting image of the package along with docker ps instance)

Thanks!


Use evm and test emacs 24.1~25.3/snapshot and remacs-snapshot.

Test passed in https://travis-ci.org/kubo39/rust-mode/builds/297950846

Could you explain what the main benefit of this change would be?  That would be helpful.

I cannot tell what the benefit of this is, and I am skeptical about the change itself (e.g. I already noted the questionable running of a user gist as a shell script.)
Closing.


Adding service version logging

Prints service version to console after running fastly log-tail. (JIRA ticket)

Looks like the code needs reformatting here.


Fix frozen dismissal after initial interaction

Checklist

[x] I've tested my changes.
[x] I've read the Contribution Guidelines.
[x] I've updated the documentation if necessary.

Motivation and Context
Fixes #129 (UI Freezes after swiping bulletin and tapping close button)

Description
This change marks the swipe interaction as isInteractionInProgress == false when the gesture ends. This prevents the interaction controller from being returned here for a non-interactive dismissal.

Thank you for your help! This will be deployed in the next release.

Any chance we can get this release any time soon?


Cannot create Compute Engine Instance in Google Cloud

Is there any people who also cannot create Compute Engine Instance in Google Cloud with Tesla GPUs with "The zone 'projects/graceful-castle-301212/zones/us-central1-a' does not have enough resources available to fulfill the request. Try a different zone, or try again later."? I have blocked here several days.

We should apply for the GPUs (all regions).

We should apply for the GPUs (all regions).


Osx tray app

awesome. can u rebase to fix the merge conflicts?

@SimonCropp rebased on master

i am going to merge this into its own branch in the main repo, and grant u access, given the scope of this change it will make it easier for us to collaborate


User added as project owner having sync issues while creating namespace after upgrade

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):

Spin a rancher on version 2.4.15
Create users u1 and u2 as standard users
Create a cluster with 3worker, 1etcd and 1 cp
Add a project as admin and add u2 as Project Owner and Project member
Upgrade the cluster to the latest v2.5.8-rc2
Once the server is active, create a namespace logged in as u2
Namespace is stuck in activating
Create another namespace and the ns is stuck in activating too.
If we refresh the page, the namespace in step7 appears but namespace in step 8 disappears.

Result:
All the created namespaces should appear in the project
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI):
Before upgrade: v2.4.15
After upgrade: v2.5.8-rc2
Installation option (single install/HA): HA

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): Infrastructure provider digital ocean

Other details that may be helpful:
Screen recording for the same:
https://user-images.githubusercontent.com/38144301/114331821-bc342400-9af9-11eb-8039-f5bf9c6ced3b.mov
This is not seen on a fresh install of 2.5-head,2.5.7 and not happening always..
Also, if we upgrade from 2.4.15 to 2.5-head -- issue is not seen

@ryansann This is also seen on v2.5-d1083bc63e4ddde70ffadd09bf0133ae5862b5fe-head

Create two users u1 as Admin/restricted admin and u2 as standard user
Create a cluster logged in as u2 and add a project to u1 to this project with custom roles -- only enable create namespaces
Now login as u1 and verify, he has access to all the projects
Change the user u1 from admin to standard user logged in as local cluster admin
Log in as u1 and create a namespace. We can see the same issue happening
If I verify the namespaces created from kubectl, I see all the created namespaces:

ns1               Active   8m55s
ns2               Active   8m45s
ns3               Active   8m31s
ns4               Active   6m13s
ns5               Active   6m2s
ns6               Active   35s

If we log out and log in as u1, we can then see all the namespaces

@ryansann I'm not seeing it on v2.5.7.
When I upgrade from 2.4.15 --> 2.5-head and 2.5.7 --> 2.5-head, I see this happen. Logged in as a ProjectMember --> create a namespace [See this happen]

I've done the following:

Upgrade from v2.5.7 to 2.5-head to reproduce issue, gather RBAC resources in management cluster
Run v2.5.7, don't see the issue, gather RBAC resources in management cluster

The resources are identical in both scenarios, except, when gathering the resources from the upgraded cluster, there is no duplicate cluster-membership binding seen. This does happen in the v2.5.7 cluster because we are adding user as project-owner and project-member at the same time.  Seeing no duplicate in the upgraded cluster is expected based on the changes made to RoleBinding and ClusterRoleBinding naming.
I will take a look at downstream cluster to see if there are any issues that stick out to me there.

Having investigated downstream clusters, I also don't see any significant differences in the RBAC resources between the two scenarios. There are duplicates in the v2.5.7 cluster that don't appear in the upgraded cluster.

Minimum reproduction steps:

Fresh install of Rancher v2.5.7
Add user u1 as Standard User
Create project p1 in local cluster with u1 as Member
Upgrade to 2.5-head
Login as u1
Add namespace to p1, observe issue

Actually, you need not upgrade from v2.5.7, this is seen if, instead of upgrading, you restart Rancher.

related to https://github.com/rancher/rancher/issues/20549 ?

We, have the same problem

I hope we do not have to wait till 2.6 to have this issue resolved. Our Users are not reliably able to create their self-managed Namespaces any more.

This issue is being caused by some API access control caching issues. Disabling caching for access control here: https://github.com/rancher/rancher/blob/master/pkg/rbac/access_control.go#L12 (true -> false), causes the issue not to happen. I am investigating what's going wrong with the cache and should have a fix for this soon

More details on the caching issue. When we see a namespace stuck in Activating the user has the following cache key in the access control cache: 8c5033791bed7d14b2a2684d4bce33f97cb5d457ebaf3bc900a1adb368422b4e. This value associated to this cache key is the user's access set. I've implemented some deterministic hashing of the access set to get a better idea of equality. That logic can be found here.
The hash of the user's access set when they are experiencing the issue is: 4461fff991484cc861854ba4bd2073c2b3701dee8b9805e5719d039f22312db3.
After a restart, namespaces return to normal and the user's access set has a different hash, namely: 5b1405440809e96dfb48d0d71f217a64b259854766380e55f2434ffbe2ec5d3a.
Assuming correctness of the deterministic hashing logic, this implies that the user has a different access set after restart, but the same cache key. I have not found the root cause of this issue yet.

#35172 Looks to have fixed this issue, I will move it to test so QA can also validate

Verified on v2.5-head f5cf749
Docker install upgrade from 2.5.10 --> 2.5-head f5cf749

Created two standard users from global --> users
Added a user - user1 to the local cluster as PM
restarted the rancher server and verified the issue was reproduced
Upgraded rancher to v2.5-head
Created a downstream cluster and added the user user1 as the PM
Restarted the rancher server
Logged in as user1 and verified the user was able to create namespaces and all the namespaces were seen active
Restarted the rancher server and verified user1 was able to create namespaces and deploy workload in all the namespaces.

verified the same steps on an HA fresh install 2.5-head f5cf749  and the user can create namespaces and deploy workloads in all of the created namespaces


centos-8,9-streams images

please add centos 8 and 9 streams images

Will get this done this week. Apologies for the delay.

no worries, take your time, appreciate your good work very much!

This is now completed!
You should see it on https://images.opsmaru.com now

many thanks, not sure what is going on but our packer still miraculously works with images: remote, but now we are ready once it stops ;)

@aivanise yeah, essentially images: will work for you until May


Readme file, spelling of Usage corrected.

In the readme file Usage was wrongly spelled as Useage. I corrected the spelling.

Thank you!


View last updated time for progress for each student

As a tutor, I want to be able to view when I have last updated the progress for each student so that I can ensure that I consistently update progress for all students.

Not applicable for v1.4


Ensure text area styles override text field styles in text area

The order in which matching style modules are included in an element template is not consistent.
So the current approach makes the theme look broken in case text field styles get included after text area specific styles (that are supposed to override text-field styles) in the text area template.
Need to add an explicit include for text field valo styles prior to text-area specific styles.

This change is

This is actually a much better approach in general, that reusable modules are included explicitly by the actual element theme, and not “forced” by the reusable module.

Reviewed 2 of 2 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Reviewed 2 of 2 files at r1.
Review status: :shipit: all files reviewed at latest revision, all discussions resolved, all commit checks successful.

Comments from Reviewable


Invalid manifest in SSR render is silently ignored

Qwik Version
0.10.0
Operating System (or Browser)
macOS
Node Version (if applicable)
No response
Which component is affected?
Qwik Runtime
Expected Behaviour
When passing an invalid manifest to the renderToStream function, an error should be thrown or warning logged.
Actual Behaviour
When passing an invalid manifest to the renderToStream function, no error or warning is logged. Instead it is silently ignored and the SSR render eventually throws a QWIK ERROR Code(31) (which is a symbol mapping error).
Additional Information
No response

@thejackshelton this looks like the error we got as well right?

@thejackshelton this looks like the error we got as well right?

Yes, if I recall correctly this issue is very similar to the one we're experiencing with Qwik UI
Qwik UI Repo:
https://github.com/qwikifiers/qwik-ui
When previewing the website via NX and refreshing the page you would get the following logged in console.
Cannot resolve symbol s114 in {
  KEaUk6nF32k: [ 's_KEaUk6nF32k', 'q-afc7ee1a.js' ],
  '02wMImzEAbk': [ 's_02wMImzEAbk', 'q-8076d425.js' ],
  '80spEZpcqwM': [ 's_80spEZpcqwM', 'q-e79c8e6a.js' ],
  '0IwBDaR0kVI': [ 's_0IwBDaR0kVI', 'q-e79c8e6a.js' ],
  d0d1e0t7rg8: [ 's_d0d1e0t7rg8', 'q-40c0beb7.js' ],
  '0Afy1HpNmk0': [ 's_0Afy1HpNmk0', 'q-fbacc697.js' ],
  '0BkHxKX76t0': [ 's_0BkHxKX76t0', 'q-fa8e1d67.js' ],
  '0C5HWl3JdN8': [ 's_0C5HWl3JdN8', 'q-a6a7e81b.js' ],
  '0HUEUIEQUo4': [ 's_0HUEUIEQUo4', 'q-8b2ff903.js' ],
  '0c4DeDGSgic': [ 's_0c4DeDGSgic', 'q-3b02abce.js' ],
  '25CuJTnUhvE': [ 's_25CuJTnUhvE', 'q-8397af9b.js' ],
  '2FP4iuDsTqc': [ 's_2FP4iuDsTqc', 'q-0c058a82.js' ],

When we looked into the debugger, I believe we got an error code 31, I also briefly remember something about looking into the manifest, and there wasn't an error thrown or logged like the original post suggests.
I'm still learning qwik core including understanding hashes, source maps, the manifest, symbols, etc, apologies if this isn't helpful in identifying the issue.
@manucorporat
We are currently using Qwik v1.1.5 in Qwik UI, whenever you navigate to the Qwik UI website or refresh the page, it will provide a blank page
Like this: https://qwikui.com/docs/headless/autocomplete/
It also affects the functionality of components on the page. We still haven't been able to pinpoint the issue, and it's been happening to our knowledge since April.
Oddly enough this issue goes away on that route when importing components from the same repo and using TSX instead of MDX.
We tried creating a reproduction for importing between monorepo's on Qwik 1.1.5 and didn't get the error. I tried seeing if it was an MDX issue and wasn't able to reproduce the issue here either.


[Missing feature] S3 Credentials: Cannot use system IAM credentials instead of hardcoded ones

Search before asking

[X] I had searched in the issues and found no similar issues.

Description
In the docs, it is mentionned that we can create an S3 catalog to enhance security by avoiding hardcoded credentials, and use system credentials.
However, it seems like I cannot create a catalog with type="S3" (ERROR 1105 (HY000): errCode = 2, detailMessage = Unknown catalog type: s3).
It is also not possible to create a ressource without omitting the access key and the secret key.
Solution
The simplest solution would be to allow to create a ressource qithout access key and secret key. The logic to automatically search for the credential chain is already handled it the java AWS SDK, and also seem to be handeled on Doris side:
In this file: S3Util.java
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Seems to be handled in the backend as well, here.
But might need to use the default constructor here, and get rid of this.

mark


WebApp - Disable submit button when getting max transferable

Reason

Delay at the fee estimate step when interacting with RPC

Solution

Disable submit button when getting max transferable
=> Refer from issue #2793

Version test : https://4c56443e.subwallet-webapp.pages.dev/
Validation passed


chore: add mergify rule for backports and update contributing guide

Adds a mergify rule (and corresponding documentation) that backports pull requests to other branches via backport-to-kubectl-v21+ label.
Has been tested on my own fork of the repo (can see this in action before I nuke that repo: https://github.com/kaizencc/awscdk-asset-kubectl/pull/3)

@Mergifyio backport kubectl-v23/main kubectl-v22/main kubectl-v21/main


shell.nix: Update to a newer nightly

Fixes: https://github.com/paritytech/substrate/issues/11024

How do I best verify this? Just cargo build --all --all-features in a nix shell, or do we have CI for that?

We have no CI. I just used cargo check --all


Several expand triggers in the tree data table (using with grouped header)

Describe the bug
When tree data table is used a "children-key" prop is required (default value is "children"). That's ok, but grouped header requires "children" prop in schema too.
With these settings table is rendered with several expand triggers in each row (one in first column and others where columns has "children" prop)
It seems to me that this issue appeared after update naive to  version 2.40.1, last stable - 2.39.0.

Steps to reproduce
Basic options (columns and table data) for tree data table, below:
const columns = [
  {
    title: 'Column 1',
    key: 'column1',
    align: 'center',
  },
  {
    title: 'Column 2',
    align: 'center',
    children: [
      {
        title: 'Column 2.1',
        key: 'column2',
        align: 'center',
      },
      {
        title: 'Column 2.2',
        key: 'column2',
        align: 'center',
      },
    ],
  },
  {
    title: 'Column 3',
    align: 'center',
    children: [
      {
        title: 'Column 3.1',
        key: 'column3',
        align: 'center',
      },
      {
        title: 'Column 3.2',
        key: 'column3',
        align: 'center',
      },
    ],
  },
  {
    title: 'Column 4',
    key: 'column4',
    align: 'center',
  },
];

const data = [
  {
    key: 1,
    column1: 1,
    column2: 2,
    column3: 3,
    column4: 4,
    children: [
      {
        key: 2,
        column1: 1,
        column2: 2,
        column3: 3,
        column4: 4,
        children: [{ key: 3, column1: 1, column2: 2, column3: 3, column4: 4 }],
      },
    ],
  },
];

Link to minimal reproduction
no link
System Info
System:
    OS: macOS 13.4.1
    CPU: (8) x64 Apple M1 Pro
    Memory: 62.48 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 10.21.0 - ~/.nvm/versions/node/v10.21.0/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v10.21.0/bin/yarn
    npm: 6.14.4 - ~/.nvm/versions/node/v10.21.0/bin/npm
  Browsers:
    Chrome: 129.0.6668.70
    Edge: 129.0.2792.52
    Safari: 16.5.1
  npmPackages:
    naive-ui: 2.40.1
    vue: 3.4.31

Used Package Manager
npm
Validations

[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion.
[X] The provided reproduction is a minimal reproducible example of the bug.

I have the same problem

I have the same problem
minimal representation https://codesandbox.io/p/sandbox/dry-silence-9czywv?file=%2Fsrc%2FDemo.vue&workspaceId=3817d861-1ab3-485b-93b2-6358754ecc46

I have the same problem
https://codesandbox.io/p/sandbox/thirsty-sun-gvttk3

Any news about this bug? We are facing the same problem after updating to latest version of naiveui.


Add PGN copy/paste/save/open feature

Add functions and connect them to appropriate widgets on the UI that would perform following logic:
Copy/paste features

PGN copy function

Generate PGN string from the current position
Send generated PGN string to clipboard

PGN paste function

Read clipboard content into string
Verifiy that it is a valid PGN string (use separate function for it)
If string is valid PGN, then paste position onto the board which means

Clear current state_tree
Initialize state_tree with game obtained from PGN

Else show error message

Open/Save features
Open and save functions should use Gtk.FileChooserDialog to let user select file.
PGN save feature logic should be implemented as follows

Generate PGN string from the current position
If there's currently opened file

Write PGN to the currently opened file

Else request file name via FileChooserDialog and save PGN into given file

PGN open feature logic should be implemented as follows:

Click on "Open PGN" button should

Show Gtk.FileChooserDialog to let user select file
Then generate Gio.Application::open signal with Gio.Application.open method

Event handler connected to open signal then should

Verify file existence and readability
Read file contents into string
Verify it is a valid PGN string
If string is valid PGN, then paste position onto the board which means

Clear current state_tree
Initialize state_tree with game obtained from PGN

Else show error message

PGN format should be in a bit extended form as described here. This allows to store variations alongside the main line

We should consider using some PGN-reading libraries as well


incorrect checking of covariant parameters

I don't think this behavior is intended:
abstract class I {
  m(num x);
}
/*abstract*/ class B implements I {
  m(Object x) => x;
}
class C extends B {
  m(covariant String x) => print(x + '!?!');
}
main() {
  I i = new C();
  i.m(42);
}

this results in a runtime check failure on C.m. There are no compiler errors.
Type 'int' is not a subtype of type 'String'

however if I uncomment abstract class B it correctly issues:
[error] Invalid override. The type of 'C.m' ('(String) → dynamic') isn't a subtype of 'I.m' ('(num) → dynamic')

The problem can be seen by reading _OverrideChecker._checkAllInterfaceOverrides; we are stopping our interface search once we encounter a concrete class. This means covariant parameters do not get checked against all of their superinterfaces.

That's right. Here is the relevant sentence from the informal spec:
For a covariant parameter, the override rule is that its type must be
either a supertype or a subtype of the type declared for the corresponding
parameter in each of the directly or indirectly overridden declarations.

covariant String x is a covariant parameter. Being a super-or-sub of num is one of the things it must satisfy, so the declaration C.m violates the override rule. This also illustrates that it is incorrect to stop searching when class B is reached, no matter whether it's concrete or abstract.
We do have ways to avoid searching the entire clausal supertype graph (that is, following all the extends, implements, and with links) in some cases:

We could store a bit indicating that the type annotations for a given parameter in all its clausal supertypes are the same type, in which case the supertype traversal can be pruned. That would presumably be a quite common situation.

We could also store a bit indicating that the type annotations for a given parameter form an increasing sequence along all clausal supertype paths, in which case the checking can stop if the new declaration uses a subtype (we could swap the types num and Object in the example to create such a situation, and we would then know that int would be a subtype of all the relevant types and String is a violation of the super-or-sub requirement).

In general, it's very inconvenient to have to traverse the entire clausal supertype graph, but we expect covariant parameters to be rare, so with a little luck it shouldn't matter much in practice. Otherwise we may want to use tricks like the above to prune the search whenever possible.

this may be fixed now -- I recently cleaned up a lot of bugs in interface override checking) -- I will double check & make sure we have a test case

still reproduces. Interestingly CFE seems to have the same bug (and it fails to issue an error for abstract as well)


Nothing displayed

Hi,
I have setup a fresh install on MM on a Pi3. I've installed Ext3 and used the examples but I don't get anything on screen other than "May" and a line underneath it
		{
			module: "calendar",
			header: "US Holidays",
			position: "top_left",
			config: {
				broadcastPastEvents: true, // <= IMPORTANT to see past events
				calendars: [
					{
						symbol: "calendar-check",
						url: "webcal://www.calendarlabs.com/ical-calendar/ics/76/US_Holidays.ics",
						name: "us_holiday",
						color: "red" // <= RECOMMENDED to assign color
					}
				]
			}
		},
		{
			module: "MMM-CalendarExt3",
			position: "bottom_bar",
			title: "Calendar",
			config: {
				mode: "month",
				instanceId: "basicCalendar",
				maxEventLines: 5,
				firstDayOfWeek: 1,
				calendarSet: ['us_holiday'],

			}
		},

Am I missing something in my code?

So I followed the instructions for going to 1.2.6 and I now have the calendar displaying. Not sure if that helps though?

Maybe submodule is not installed properly. Read the read me.md and do the process of update.

The calendar module had been working for me for along time, over the weekend I ran through a series of package updates, and then the calendar stopped updating. Upgraded to 1.3.1, the calendar won't display. Downgraded to 1.2.6, nothing was displayed. Installed submodules, now the calendar is visible but no events are displayed, even though my instance of MMM-CalendarExt3Agenda is working correctly.
Absolutely no errors appearing, even with debug logLevel

Can you share me with your real iCal url and configuration file<EMAIL_ADDRESS>

I'm copying my calendar down to a local file on my raspi, and the calendar module is just reading from the local file. Just looking at sanitizing the .ics and I'll send it over to you soon, but in the meantime I'm getting the same behaviour with absolutely no calendars included, here's my (current) config:
{
                        module: "MMM-CalendarExt3",
                        position: "bottom_bar",
                        title: "",
                        config: {
                                mode: "week",
                                instanceID: "basicCalendar",
                                firstDayOfWeek: 0,
                                calendarSet: [], //["family_calendar", "personal_calendar", "new_family_calendar"],
                                weekIndex: 0,
                                weeksInView: 2,
                                maxEventLines: 8,
                                animationSpeed: 2000,
                                waitFetch: 10000,
                                fontSize: '19px'
                        }
                },

I even created an empty .ics:
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
X-WR-CALNAME:Family
X-WR-TIMEZONE:America/Edmonton
END:VCALENDAR

and tried loading it but it's the same behaviour. Before I did my apt package upgrades on Sunday I had weather details being pushed into CalendarExt3, but it isn't happening any longer - while CalendarExt3Agenda is still populating this data. When the Agenda refreshes the Calendar just doesn't.

Managed to narrow it down for my issue.
There's a specific event that, whenever it is included in a calendar, and a MMM-CalendarExt3* module includes that calendar, that entire module fails to refresh any data at all. I added the calendar that event lives in onto MMM-CalendarExt3Agenda and actually replicated the issue in that module, too.
Noticed that the TZID for that event's DTSTART and DTEND were different than everything else in my .ics files. When expressed in GMT-07:00, the module does not refresh.
DTSTART;TZID="GMT-07:00":20230620T103000
DTEND;TZID="GMT-07:00":20230620T111500

Every other event is expressed as the time zone name, and when I manually edit the event above to match this format, the fresh works successfully.
DTSTART;TZID=America/Edmonton:20230620T103000
DTEND;TZID=America/Edmonton:20230620T111500

Here's a sanitized version of the event to replicate the issue:
BEGIN:VEVENT
DTSTART;TZID="GMT-07:00":20230620T103000
DTEND;TZID="GMT-07:00":20230620T111500
DTSTAMP:20230508T163127Z
UID:C98DC1A6-F932-4C23-A949-7134D01C53EF
<EMAIL_ADDRESS> 3.prod.outlook.com%3E
CREATED:20230508T163127Z
DESCRIPTION:
LAST-MODIFIED:20230508T163127Z
LOCATION:
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:*******
TRANSP:OPAQUE
BEGIN:VALARM
ACTION:NONE
TRIGGER;VALUE=DATE-TIME:19760401T005545Z
END:VALARM
END:VEVENT

and fixed version of the same:
BEGIN:VEVENT
DTSTART;TZID=America/Edmonton:20230620T103000
DTEND;TZID=America/Edmonton:20230620T111500
DTSTAMP:20230508T163127Z
UID:C98DC1A6-F932-4C23-A949-7134D01C53EF
<EMAIL_ADDRESS> 3.prod.outlook.com%3E
CREATED:20230508T163127Z
DESCRIPTION:
LAST-MODIFIED:20230508T163127Z
LOCATION:
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:*******
TRANSP:OPAQUE
BEGIN:VALARM
ACTION:NONE
TRIGGER;VALUE=DATE-TIME:19760401T005545Z
END:VALARM
END:VEVENT

I did also test out the nearly 50-year-old alarm, but that seems to be handled seemlessly. Loaded 1.2.6 with the fixed event, it works correctly. Went back to main with the fixed event, it still doesn't load... So that's a different issue!

Weird, because CX3*s don't parse calendar feeds by themselves. They get the event data from the original default calendar module, so that means the data gotten might be polluted from earlier. 'dateStart' and 'dataEnd' of an event should be proper Integer numbers or at least a number-like string when it is delivered as notification from calendar module.
I suspect the parser of default calendar module cannot handle that data properly, or missing proper formatting when it tried to emit notification.
Could you check the calendar module whether can handle that event?
(And it is dawn here so I'll continue this conversation  some hours later, sorry)

Ah, good call…
[23.05.2023 14:07.01.747] [DEBUG] Processing entry...
[23.05.2023 14:07.01.748] [DEBUG] Event:
< “params”:[],"start":"00:20230620T103000","datetype”:"date-time","end":"00:20230620T111500","dtstamp":"2023-05-08T16:31:27.000Z","uid>
[23.05.2023 14:07.01.749] [DEBUG] start: Invalid Date
[23.05.2023 14:07.01.749] [DEBUG] end:: Invalid Date
[23.05.2023 14:07.01.749] [DEBUG] duration: NaN
[23.05.2023 14:07.01.750] [DEBUG] title: ******
[23.05.2023 14:07.01.750] [DEBUG]  if no tz, guess based on now
[23.05.2023 14:07.01.750] [DEBUG] initial tz=undefined
[23.05.2023 14:07.01.751] [DEBUG] adjustHours=0

So yes; bad tzid handing, I’ll send that through the default calendar module if it isn’t already there.
As for the actual issue reported here, as I mentioned I’m not able to get the module to actually appear when using 1.3.0+, still no error logs to note, it just doesn’t appear when using any of those branches or dev-latest. 1.2.6 works fine, hadn’t tried to upgrade before my package upgrades so I can’t say that is related.
Linux raspberrypi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr  3 17:24:16 BST 2023 aarch64 GNU/Linux

Ok, let's see what happened after update.
First, can you check the front-end console log? You can get it by run npm run start:dev instead of pm2 execution. (You should stop and kill pm2 process before)
Or on MM's running screen, the shortcut CTRL + SHIFT + I or CTRL + SHIFT + J would open the dev-console of Chromium/Chrome which is used for front UI of MM. (Ah, are you using serveronly mode and another 3rd party browser for MM? like midori or FF?)
There might be some error lines displayed. Could you report me which error happens?
Later I'll provide a more verbose version to get detail information on running.

Nice approach.
The new library is loaded asynchronously not to block MM's execution. So maybe the first attempt of getDom() would fail, and spit out Module is not prepared yet... warning(It is not an error, intended warning)
It is intentionally designed so.
This module will draw the contents with these conditions;

library is loaded
all DOM of other modules are created
calendar notification is received at least once.
These 3 conditions would happen in random order or unpredictable time gaps by the environment, so I should postpone the first drawing till all the conditions are prepared.

So I think at first a few seconds(by your system) my module will not show anything waiting all the conditions are prepared. If this waiting takes somewhat long, there would be some reason;

library is not loaded (Usually, installation fail or some other reason)
DOM is not created (There would be some uncaught error from this/other modules)
calendar notification is not coming (IDK why, anyway)

However, I have a worry about your approach.
Log.warn('this._domReady(): ' + this._domReady())

When you call this._domReady() just to leave the log, which calling itself fulfils the condition the all DOM of modules are created by force. I suspect that the case is not a real solution to your issue. I suggest you remove that line and try again.

Interesting.

As you can see, DOM_OBJECTS_CREATED fired normally.
The reason for waiting for this notification is to prevent too early getting events before preparing the module. When fewer modules are installed, it may not cause a problem. But if you have so many modules and some might take some time before this module's running, the event notification will arrive before this module's ready. It will make another issue. So I wait every condition should be accomplished.
Anyway, I don't know why your MM doesn't emit DOM_OBJECTS_CREATED notification.
But if you feel enough, it might be good for you.

By the way, are you absolutely testing the essential modules? The fact DOM_OBJECTS_CREATED notification is not fired means some module fails to create its DOM or takes a too long time. I think that will be your other problem.

Ah! You've found it.
A different third party module which seems to have been abandoned is throwing an uncaught error, but still displays correctly. When I comment out that module I am now receiving both.
Normal config:
[Info] All modules started! (main.js, line 501)
[Warning] notificationReceived(): ALL_MODULES_STARTED (MMM-CalendarExt3.js, line 142)
[Warning] [CX3] Module is not prepared yet, wait a while. (MMM-CalendarExt3.js, line 229)
[Error] TypeError: undefined is not an object (evaluating 'this.tasks.items') — MMM-Todoist.js:579
	error
[Warning] notificationReceived(): MODULE_DOM_CREATED (MMM-CalendarExt3.js, line 142)
[Error] Unhandled Promise Rejection: TypeError: undefined is not an object (evaluating 'this.tasks.items')
	(anonymous function) (MMM-Todoist.js:579)
[Warning] notificationReceived(): NEWS_FEED_UPDATE (MMM-CalendarExt3.js, line 142)

When removing MMM-Todoist:
[Warning] notificationReceived(): MODULE_DOM_CREATED (MMM-CalendarExt3.js, line 142)
[Warning] notificationReceived(): DOM_OBJECTS_CREATED (MMM-CalendarExt3.js, line 142)

So yes, a separate module is failing to confirm the dom is loaded, even though it is, and that ends up preventing CalendarExt3 to load properly. Without knowing @smartroad I would hazard a guess they have something similar, then.

Nice.
I'll consider to modify my codes not too strict for this kind of pitfall on next update.

@O5ten
Array.at() was introduced 2 years ago in modern browsers.

If your browser might have a too old version, plz update it to a newer one.
I basically develop all my modules to be compatible with Chrome/Chromium because the electron - the MM's standalone front client is using Chromium.
If you are using Midori or another obsolete browser, sorry. It's too painful to make modules to be compatible with those old legacies.
Which browser and version are you using?
CX3 module isn't prepared yet warning is just warning. you don't need to care.

@O5ten
// Array.prototype.at polyfill
Array.prototype.at = function (index) {
  if (index < 0) {
    index += this.length;
  }
  return this[index];
}

Try to add this into the 1st line of config.js; this is monkey-patch, so not a permanent or solid solution for this issue.

Aaaah, that might actually be it. The mirror running has been running for a little more than a year and is probably not well updated. Thanks for the hint (and the monkey-patch). :)

I had the same problem (current version not displaying anything besides the name of the month with a line underneath it), installing the older snap-1.2.6 worked for me.

Update submodule(described in README.md)
Or update your MM.
Or I need frontend log to examine it.


Acommodate for different Node version "destroyed" property name

We did some testing where the server closed connections explicitly. We'd end up in close, but the sockets would never be removed from the freeList, causing the agent to reuse those sockets in subsequent requests, which didn't work.

Can this be merged. I've been running into some production issues that appear to be caused by this behavior. I'm consuming the Twitter API, and after 100 requests the server will explicitly close the connection. The result is that some of my requests never emit 'error' or 'response'.

Howdy! I was a relatively new employee when this got proposed, then I forgot that this repo existed, sorry about that. This makes the tests pass, which makes me happy. As this thing's primary purpose is for the newrelic node agent, I need to also try the PR with that before I merge. Give me a little bit and I'll fix that and get perms to push a new version.

Oh, also thanks @jsha for bringing this to my attention.

@staeke @jsha This has been merged in: https://github.com/newrelic/yakaa/commit/16abfeda0c4494f26ed60166560e2da09fa82020 I squashed the commit and changed the message to be our standard formatting.
<EMAIL_ADDRESS>was published just now including this. Thanks!

Terrific, thanks for the speedy response!

great!


License?

Hi,
Thanks for making available this nice library. I am wondering what the license is, if any, for this code.
Best regards,
Jake

Thanks for asking, Jake! I've just added an MIT license for the code. (Thanks for the reminder!)


Update documentation link in README.md

I changed the documentation link listed in the repo readme to match the documentation link found on http://www.zewo.io.  This should resolve the 404 error I received when clicking on: "https://github.com/Zewo/Zewo/blob/master/docs.zewo.io"

Thanks a lot! Do we have other broken links?

https://github.com/Zewo/Zewo/blob/master/CODEOFDONDUCT.md gives me a 404 error.

thanks man!


Loottracker: Hide/Show ignored items not working

When pressing the Eye Icon in the loot tracker it doesnt show hidden items, making items permanently hidden with no way to show them again in the loot tracker:

I can confirm this bug's behavior. Clicking that button makes no changes in the visible loot.

Fixed in<PHONE_NUMBER>5854a195e535f458731f663b832f1b

This bug seems to have returned, clicking hide and show seems to have no affect

I used it just yesterday and it was working fine, so I don't think it has regressed again.


Refactor process.py for use in decomposed step function

Refactor proccess.py to split out individual tasks that can be orchestrated by the forthcoming decomposed step function.

Closing this story as the work was merged into ebezzi's branch and this story's PR was closed. The decomposed step function work will be published in a separate PR.


Button customization is missing

Hello, I have an issue with customization of mylocation button and positioning it in specific area, in general there is no option to customize your button with new icon and so on.

@svilen1 Thank you for opening this issue. 🙏
Please check out these other resources that might be applicable:

Support Console - If you have a support contract.
Discord - chat with other developers
StackOverflow - use the google-maps tag
Google Maps Platform issue trackers

This is an automated message, feel free to ignore.

@svilen1 Please take a moment to fill out this short survey. Thank you!
This is an automated message, feel free to ignore.

Have you worked on this issue?

What about this issue?

Will support be added for this? Curious why it defaults top right when on Google Maps app is bottom right.


Updated react-transition-group and changed Animation.js example

For beginners like me it would be nice if you would use the latest version from react-transition-group in your Animations example. In v2 of react-transition-group the implementation for CSS Transitions changed slightly.

Thanks! We needed a PR for this. Very helpful!


Hodge zach landing page

Hi Zach,
Unfortunately, it looks like this pull request has merge conflicts =X. Could you please redo this pull request so I can get it merged ? It has the following two commits within it:

https://github.com/dallaspythondojo/python/pull/84/commits/93cda84922b3cc090f3bb4a75a5d2aed1b4639dd
https://github.com/dallaspythondojo/python/pull/84/commits/867882391d402c4fee7d7429cf9398572efb21b7

Thanks!


$mdDialog closes on open color picker

When open a color picker inside a mdDialog he close his parent. Anyone has any suggestions?

This is currently an open issue from https://github.com/angular/material/issues/3072 and https://github.com/angular/material/issues/698

i´m having the same issue.
an option would be to display the color picker using $mdDialog or not based on a directive's config parameter like data-show-dialog

@jaimeguaman I have a similar issue open #19

Why not implement this in the same way like md-datepicker which works without any problems?

When this was created, there was no md-datepicker.  You can also see that there is an "inline-dialog" branch that is being worked on.

Please see #47


Run-TestsInNAVContainer: Other TestSuites than DEFAULT are not working

Hi,
I tried to run a custom TestSuite (not named DEFAULT) by using the param -testSuite in a CI build scenario, but no test inside the TestSuite was run nor any error came up that something is wrong. I believe the problem is with the Page 130409 that is imported during the runtime. The Page is set to Editable = false, which I guess leads to the script not being able to select the differing TestSuite Code. When I changed Editable to true the it runs the tests from custom TestSuite without any problems.

Looks like you are right, I will update the page

The page you download from http://aka.ms/pstesttoolpagefob has editable true.
I think i fixed this a while back (march 12th) - maybe you have a cached version?
Maybe try to delete the fob files in programdata\navcontainerhelper - and then retry?

Ok, that's strange. I just ran Run-TestsInNavcontainer again with a newly created container for Business Central Spring Release (so no fob file existed before) and it still has a version of the page which has editable=no (Object Date is March 3rd). If I download the fob file from the link directly it is also the old version. I'm not sure what I can do differently especially when Powershell does the download in a newly created container? I will try to download the file directly from my personal laptop at home later, which has defintly never seen this file before

Maybe you have a proxy or like, which keeps the file in a cache???

I checked with our IT if we use something like that, but they claimed we don't. But to definetly rule that out I now created a new azure machine (western europe), installed docker and run the latest bconprem image. The page downloaded is the same that I get locally which has the editable=no. May be you could try the same or I could give you access to that machine if you like.

Will try myself again
Få Outlook til iOShttps://aka.ms/o0ukef

Fra: ChrisM<EMAIL_ADDRESS>Sendt: Thursday, April 4, 2019 9:50:10 AM
Til: Microsoft/navcontainerhelper
Cc: Freddy Kristiansen; Comment
Emne: Re: [Microsoft/navcontainerhelper] Run-TestsInNAVContainer: Other TestSuites than DEFAULT are not working (#404)
I checked with our IT if we use something like that, but they claimed we don't. But to definetly rule that out I now created a new azure machine (western europe), installed docker and run the latest bconprem image. The page downloaded is the same that I get locally which has the editable=no. May be you could try the same or I could give you access to that machine if you like.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fnavcontainerhelper%2Fissues%2F404%23issuecomment-479789667&data=02|01|freddy.kristiansen%40microsoft.com|76726569de3c43d5e2fb08d6b8d229e3|72f988bf86f141af91ab2d7cd011db47|1|0|636899610124023471&sdata=mIplN8B48daRGp62GMvdPU3393DKxa9WC8Mh%2BLFq9jM%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAKRqA1BHZjbiLkawfoT-_mosDgL_0v0cks5vda6xgaJpZM4cWDTi&data=02|01|freddy.kristiansen%40microsoft.com|76726569de3c43d5e2fb08d6b8d229e3|72f988bf86f141af91ab2d7cd011db47|1|0|636899610124023471&sdata=F%2BxOz9on8F6lULFArduJhX2nX8nchfOQlAuIWFXB2Nc%3D&reserved=0.

Not sure what went wrong on my machine - but you were right.
I have now fixed the fob.
Also in the next version of NavContainerHelper, the files will be part of the module and not downloaded.


eve/stats: allow hiding counters whose valued is 0 - v3

Task #5976
Add two tests to showcase this. Don't know if we want more tests or more checks, or one with and one without, for comparison purposes.
Previous PR: https://github.com/OISF/suricata-verify/pull/1745
Changes from previous PR:

rebase
change the first test created to not require Suri to be in debug mode
use has-key and not-has-key to check for the stats
add another test for the feature
fix exception-policy-applayer-03 test, which was missing the actual check for the per-app-proto stats counters

Ticket
Redmine ticket:
https://redmine.openinfosecfoundation.org/issues/5976

Suricata PR: https://github.com/OISF/suricata/pull/10809

Merged in #1763, thanks!


ISPN-9202 Add persisted entries count to stats

https://issues.jboss.org/browse/ISPN-9202
https://issues.jboss.org/browse/ISPN-9203
Also adds ISPN-9203 to sort stats when exposed via the CLI

Integrated into master, thanks @tristantarrant !


react 4.0.0 uploaded Aug 28, 2017?

This page https://pub.dartlang.org/packages/react#pub-pkg-tab-versions says that react 4.0.0 was uploaded Aug 28, 2017, while react 3.6.0 was uploaded Sep 18, 2017. It should probably have been the other way around.

There were a couple things we needed in the 3.x line (we couldn't move to 4.x yet), so we published 3.x releases with plans to also add that functionality to the 4.x line.
That's on my agenda this week; sorry I haven't gotten to it sooner


Disable select ligatures with a blacklist

Reopening #98758

I would love an option to disable certain ligatures while keeping the rest.
I love most ligatures, but the "=" vs "==" vs "===" is sometimes hard to tell apart (and led to an hour long bug hunt.) I would love a blacklist of ligatures to ignore.
For now, I will just go back to a classic font... like the ones muggles use... bleh.

Personally, I'd like to disable the .- ligature in s/css files.

I don't think it's possible to toggle ligatures for specific pairs, but if you read the docs for your font/typeface it should tell you what features are supported.

Is this an issue with the font renderer in chromium/electron?


Issues with characters Ø and ø in 2.x

We were using zip4j_1.3.2.jar  to unzip files that could successfully contain the letters Ø and ø. We have since upgraded to zip4j-2.7.0.jar (after also trying zip4j-2.6.4.jar), but now experience these two characters appearing as ¥ and ¢.
The zip file itself is created using a simple 7z a filename.zip "./dir/*".
From my understanding version 2.0 of zip4j is more strict, but also now completely adhering to the zip-standard, allowing only CP437 and UTF-8. I was not expecting to handle this manually. My attempts at fixing it by enforcing an extraction charset did not work. I tried:
zipFile.setCharset(InternalZipConstants.CHARSET_UTF_8);

And:
zipFile.setCharset(Charset.forName(InternalZipConstants.ZIP_STANDARD_CHARSET_NAME));

One resulting in a question mark, and the other in the character dissapearing. As mentioned, I'd prefer to not have to deal with this in the code at all. What could be the problem I'm experiencing after this upgrade?

We resolved this after reading up on #45, and finding that the real cause was 7zip not following standards. We simply had to move from:
7z a filename.zip "./dir/*"

To:
7z a -mcu filename.zip "./dir/*"

And change nothing else, and it worked perfectly. If there was a migration guide, it might be worth mentioning potential break in functionality due to 3rd party software creating non-standard zip-files.