Use fixed schema for traits input instead of name/value pairs.

Describe the bug
The traits uses name/value pair to provide inputs instead of using well-known schema provided in OAM spec.
OAM yaml files used
  traits:
    - name: manual-scaler
      parameterValues:
        - name: replicaCount
          value: 3

What happened:
Input to manual scaler is name/value pair.
What you expected to happen:
It should follow the schema in the OAM spec and it should be in the format below
  traits:
    - name: manual-scaler
      properties:
        - replicaCount : 3

I'll take care of this.

fixed by https://github.com/oam-dev/rudr/pull/504


Revo

To make a submission for the Bake Off, please complete the task lists
below; otherwise remove them.

Your Dapp:

[x] connects to Valora via WalletConnect V1 or DAppKit;
[x] must be mobile-first or mobile responsive;
[x] is in one of the existing categories; and
[x] includes a link to user documentation.

Please confirm you have:

[x] read the Dapp Bake Off Information; and
[x] read the Dapp Bake Off Rules.

Hi team,
I have tried to zap in some Celo to mcUSD/mcEUR pool, but it doesn’t work for me. Nothing happens when I tap the button, no error message. I am ios, safari. Can you please fix it and let us know so we can review it again? Thanks!

@cajubelt Gentle reminder, you need to address the feedback we left above by Feb 28th if you wanna participate in the Bake Off.
Let me know if you have any question.

Thanks @jeanregisser . We have added links to docs in 2 places (1 for new users, 1 for all users) and addressed the bug that I think Aleksey experienced.
We have a few more usability improvements we're hoping to get through this weekend, but if you want to re-review in the meantime you probly can @lisaw-valora @aleksey-nov . Keep in mind the liquidity is low right now since we are undergoing audits, but we plan to raise it this weekend as well.

Great I'll take a look soon!
Update: we've extended the deadline for bake Off participants to address our feedback. The new deadline is March 3rd @ 11:59 pm PST (UTC -8:00).


[BUG] StepF2 BPM-based "warps" don't treat notes as fakes, can cause erraneous misses

Is there an existing issue for this?

[X] I have searched the existing issues and none matched.

Operating System
Windows and Linux
CPU
AMD Ryzen 5 4500U (Windows), Intel Core 2 Duo E7600 (Linux)
GPU
Radeon integrated graphics (Windows), GeForce 210 (Linux)
Storage
NVMe SSD (Windows), SATA SSD (Linux)
Game Version
4.18.1
Game Mode
pump
Theme
Tested with the latest versions of Infinitesimal and Soundwaves
Describe the problem
This one is difficult to narrow down because of how bizarrely the gimmicks and effects are recreated in StepF2 official simfiles, but as far as I'm able to tell, notes within StepF2/StepP1 style "warps" (sections where the BPM is set to 100000000.000 instead of using actual real warps) are not treated as fake notes which can cause the player's health bar to immediately drain and fail them out. Can provide the SSC if needed.
Example (at 1:28 in case the timestamped link doesn't work): https://youtu.be/1BwgnzSIqmE?t=88
Describe what should happen
The intended behavior is as follows, with the section in question starting at 1:22 in case the timestamp in the link doesn't work (the misses were my fault, each note is completely possible to hit properly)
https://youtu.be/dl7bQSc6Z1M?t=82
Relevant Log output
ProjectOutfox.MainLog.2022-12-27--15.15.54.log
ProjectOutfox-Infinitesimal-rewrite.ThemeLua.2022-12-27--15.15.56.log
ProjectOutfox.Crash.2022-12-27--15.15.54.log
SSC:
1676 - Siromaru + Cranky - Conflict.zip

This should be fixed in a21, do confirm for me bro

fixed in 042


Fix dependency conflicts

Rspec was resolving to 3.5.0, and rspec-rails was previously locking the
version to 3.4.x.
This fixes the conflict

This change will be added to #5


[move-lang] Migrate typing/core errors

Migrating errors in typing/core.rs

Motivation

Continuing codespan migration
I opted to using the term variable instead of local in a few spots because I think it might be less confusing (we don't have other kinds of variables)

Test Plan

Updated tests

Related PRs
Continuation of #8588

/land


[NTR] Astrocyte-restricted precursor

Please check that the term does not already exist by using the ontology search tool OLS:
https://www.ebi.ac.uk/ols4/ontologies/cl
--> not available
Preferred term label
astrocyte-restricted precursor
Synonyms (add reference(s), please)
ARP
https://singlecell.broadinstitute.org/single_cell/study/SCP263/aging-mouse-brain#study-summary
Definition (free text, with reference(s), please. PubMed ID format is PMID:XXXXXX)
tentative definition: A neural precursor cell that undergoes a gliogenic switch to generate astrocytes.
https://www.frontiersin.org/journals/cell-and-developmental-biology/articles/10.3389/fcell.2023.1063843/full
Parent cell type term (check the hierarchy here https://www.ebi.ac.uk/ols4/ontologies/cl)
is_a: CL:0000123 ! neuron associated cell (sensu Vertebrata)
is_a: CL:0000030 ! glioblast ??
is_a: CL:0011026 ! progenitor cell
Anatomical structure where the cell type is found (check Uberon for anatomical structures: https://www.ebi.ac.uk/ols4/ontologies/uberon)
UBERON:0000955 ! brain
Your ORCID
https://orcid.org/0000-0003-3308-6245
Additional notes or concerns
It exists CL:4040000 glial restricted tripotential precursor cell but the definition is restricted to oligodendrocytes and type-1 and type-2 astrocytes, while there are 3 astrocyte sub-types, see https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7122459/

@Caroline-99 please review the definition of this cell type below:
term label:
astrocyte-restricted precursor
definition:
A progenitor cell of the central nervous system that differentiates exclusively onto astrocytes. This progenitor cell expresses CD44 and S100 calcium binding protein B.
database_cross_reference:
PMID: 33052610
PMID: 15531362
comment:
In vitro this progenitor cell can differentiate from glial-restricted precursor cells.
PMID: 33052610
has related synonym
ARP
PMID: 33052610
has related synonym
APCs
PMID: 33052610
has related synonym
astrocyte precursor cells
PMID: 33052610
Logical definition
progenitor cell
(neuron associated cell (sensu Vertebrata)andpart of somecentral nervous systemUBERON)
develops fromROsomeglioblast (sensu Vertebrata)
expresses CD44 and [S100 calcium binding protein B]

Everything looks good to me. I would suggest mentioning in the textual definition that they are neuron associated cells if it is in the logical definition.

Thank you for your review. So technically they are both progenitor cells and neuron associated cells. i want to add both in the logical definition. As the parent term is progenitor cell.
If progenitor cell is in the logical definition would it be okay to have it in the description? (It is biologically more informative)

Yeah it would be appropriate to include "progenitor cell" in both the logical definition and the textual description.

Thank you Caroline! I will do!


Enterprise analytics: JSON -> CSV

Linking internal PR: https://github.com/huggingface-internal/moon-landing/pull/11564

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


How to Use the Tracker Events?

Looking at the documentation for, say, PlayerStatsEvent , all I see is:
class sc2reader.events.tracker.PlayerStatsEvent(frames, data, build)
Player Stats events are generated for all players that were in.....

...but no description of the data types for the parameters, or example on how to use it. Can someone point me in the appropriate direction? Would love to see what kind of data gets returned in these trackers. I was looking through the code for the Trackers as well, but it still wasn't super clear to me. An example usage from a replay file would be awesome! Thanks!

You can glance through the code at https://github.com/ggtracker/sc2reader/blob/b9caad908e3ebc0c1a5df3bac90d703610b56acd/sc2reader/events/tracker.py#L70
to see what properties get stored in the PlayerStats
As a rough proxy, I think the data here is in general similar to what appears as part of the observer panel in-game.


Nestjs wrapper throws TypeError: Cannot read property 'forEach' of undefined when the root module don't have controllers

With the following setup:
@Module({
  controllers: [AppController],
  providers: [AppService],
})
class FooModule {}

@Module({
  imports: [ConfigModule.forRoot(), FooModule],
})
export class AppModule {}

Reflect.getMetadata('controllers', module) will return undefined thus the line below will throw TypeError: Cannot read property 'forEach' of undefined
https://github.com/infinite-cat/recap.dev-client/blob/7c5210fc2b5907022f1211ee34dd61f6ed820c6d/src/wrappers/nestjs.ts#L11-L12
The stack trace I've got:
(node:392574) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'forEach' of undefined
    at Object.wrapNestJsModule (x/node_modules/@recap.dev/client/dist/client.umd.js:25987:51)
    at bootstrap (x/dist/main.js:13:58)
    at Object.<anonymous> (x/dist/main.js:27:1)
    at Module._compile (internal/modules/cjs/loader.js:1063:30)

Thanks for reporting it! I'll fix it right away.

@micalevisk
New 1.12.2 version of the @recap.dev/client with a fix was just released. Please let me know if I can close the ticket.

You want to wrap your FooModule in wrapNestJsModule. Read more here

So for each module that have controllers I need to call wrapNestJsModule instead of just calling for the root/entry module, right? I understand this after reading the source code. IMO the docs didn't make this clear. Thank you!

@micalevisk Exactly, the motivation is that you might want to trace only specific modules. Let me know if you'd like a flag to introspect imported modules.

My modules are generally organized like this:

so I don't think that instrospection is necessary.


Generate modules and classes from AST

Part 3 of the functionality.
This implements the logic to take the AST from thriftrw.idl and generate classes and TypeSpecs. TypeSpecs were originally called Types in the previous diff.
So here's a quick overview:

Users will interact directly with classes. Each class represents a struct, enum, union, exception, or service.
Classes for everything except services have a type_spec attribute which points to the TypeSpec for that class. The TypeSpec has a reference back to the class (it needs it to construct objects of that type).
TypeSpec.to_wire and TypeSpec.from_wire are used to convert instances of these classes (or relevant primitive types) to Value objects and back.
Value objects map directly to the over-the-wire representation. Protocols are responsible for converting Values to binary and back.

Classes for services don't ever get instantiated. They contain one ServiceFunction for each function declared for that service. ServiceFunction maintain references to classes representing the request and response types for that function. The request type is a struct of all parameters that the function accepts. The response type is a union of the return type and the exceptions thrown by the function.
WIP because tests are incoming.
@blampe @breerly @junchaowu

:shipit:

lgtm


⚠ Turnos 24x7 has degraded performance

In 8d09854, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 837 ms

Resolved: Turnos 24x7 performance has improved in 0fc8049.


"horse" spell allowing clipping through walls

Hello,
Spawning a horse "on" a wall will make it spawn "inside" the wall. Then, mounting it will allow the player to pass through the wall.
Ideally there should be a protection that prevents a horse from spawning too near a wall.
Thank you.

Sounds hard... you could maybe use a Volume + CheckBlock action though.
Just FYI, since you've been making a ton of bug reports / requests recently- no one is really actively working on this plugin right now. If that's going to be an issue then you may want to look for other plugins (e.g. MagicSpells) - sorry!
It's just me here and I don't have the time. I am usually willing to stop and fix critical bugs, but stuff like spell configs I am probably not going to get to anytime soon.

@NathanWolf I must admit I have no idea how to configure the spell so it checks wall proximity with checkblock and volume. Most of the time when I "made" or reworked spells you created, I just used bits of other stuff you've done.

This is hopefully fixed in 6.9.20 - if you get a chance to test it, please let me know.

Ah yeah, I think it needs an ignore_result: true under the ChangeContext action. Could you please try that out?
If that works I will add it to the default config.

No unfortunately ignore_result doesn't change anything.

@NathanWolf Hello, did you have to time to take a look at this ?


No executable found matching command "dotnet-ef" on Ubuntu (.Net Core 1.1)

As per issue #7629 closed
Trying to do a dotnet ef database update on Ubuntu 16.04
root@CSDA:/var/csda# dotnet ef database update
No executable found matching command "dotnet-ef"

Create Asp.net core application in VS 2017 on Windows
Add Code First models
Add SapientGuardian.EntityFrameworkCore.MySql package
Change DbContext to UseMySQL
Works on Windows
Publish to Ubuntu server
Run dotnet ef database update
Error

Please note latest version installed:

sudo apt-get install dotnet-dev-1.0.1
all previous .net version removed as per script instructions

Solution built with latest Visual Studio 2017 as released on 2017-03-07
Same error as before.
> root@WCGOV:/var/www/mll# dotnet ef database update
>
> Welcome to .NET Core!
> ---------------------
> Learn more about .NET Core @ https://aka.ms/dotnet-docs. Use dotnet --help to see available commands or go to https://aka.ms/dotnet-cli-docs.
>
> Telemetry
> --------------
> The .NET Core tools collect usage data in order to improve your experience. The data is anonymous and does not include command-line arguments. The data is collected by Microsoft and shared with the community.
> You can opt out of telemetry by setting a DOTNET_CLI_TELEMETRY_OPTOUT environment variable to 1 using your favorite shell.
> You can read more about .NET Core tools telemetry @ https://aka.ms/dotnet-cli-telemetry.
>
> Configuring...
> -------------------
> A command is running to initially populate your local package cache, to improve restore speed and enable offline access. This command will take up to a minute to complete and will only happen once.
> Decompressing 100% 9729 ms
> Expanding 100% 46649 ms
> No executable found matching command "dotnet-ef"
> root@WCGOV:/var/www/mll# dotnet ef database update
> No executable found matching command "dotnet-ef"
> root@WCGOV:/var/www/mll#
>

Work around if this helps someone else. After running dotnet ef database update on Windows. Go to the MySQL bin and run the >mysqldump executable, copy to server and import into mysql manually. A bit of a problem for CI.

Need to investigate this further on my side. Something to do with the Microsoft.EntityFrameworkCore.Tools.DotNet that need to be published.

My issue was resolved by adding these to project.json
"tools": {
"Microsoft.AspNetCore.Server.IISIntegration.Tools": "1.1.0-preview4-final",
"Microsoft.EntityFrameworkCore.Tools.DotNet": "1.1.0-preview4-final"
}
then execute these 2 commands:

dotnet restore -> to restore packages
dotnet ef migrations add MyMigration

All the credit goes to: http://know-it.ru/2017/03/15/dotnet-exe-no-executable-found-matching-command-dotnet-ef/


Projection layer clear color can be opaque

...causing all layers under them to be hidden. Polyfill should probably set the clear color to make sure that it always clears to transparent.

Closed, this was fixed in #13


Videos played by this player are being blocked by adblocker

For example, uBlockOrigin blocks the video from this link https://enime.moe/watch/vermeil-in-gold/10 and it throws UNKNOWN_ERROR . However, other players like https://github.com/zhw2590582/ArtPlayer don't trigger the block with exactly same video link and HLS.

Please provide the error and try to print the error.
player.on((type, payload) => {
  if (type.indexOf('error')) {
    console.log(payload)
  }
})

Please provide the error and try to print the error.
player.on((type, payload) => {
  if (type.indexOf('error')) {
    console.log(payload)
  }
})

I added logging to that page, it should log errors now. I don't know why but it looks like non-errors are also getting logged even there's type.indexOf('error')

player.on(({type, payload}) => {
  if (type.indexOf('error')) {
    console.log(payload)
  }
})

player.on(({type, payload}) => {
  if (type.indexOf('error')) {
    console.log(payload)
  }
})

I added this  player.on(({ type, payload }) => {     if (type?.indexOf('error')) {       console.log(payload)     }   })

This is the error

@shiyiya Update: I just realized oplayer sets default preload attribute to "auto" which some adlockers kinda hate it cuz it means ads. I changed it to metadata and it seems to no longer block.

🤯

🤯

I think it's better to make OPlayer default to metadata for preload to avoid further issues


Ancient Daedalus 0.8.2 restoration

Hello!
So I've found myself in a bit of a pickle regarding my Cardano wallet. Long story short, I got some coins in 2017 and transfered them to my wallet. At the time this was Daedalus 0.8.2 (in Daedalus > About) which is of course very out of date. The version.txt in Program Files/Daedalus reports 1.0.3769.0, and file version says v1.4.3
Unfortunately the backup phrase was not preserved, and the old installation does no longer connect to the network due to what I can only assume to be several network upgrades. The program is stuck on connecting

While googling around for possible solutions I ran into this thread https://github.com/input-output-hk/daedalus/issues/1234 which opened up the daedalus.api command line interface to me. Obviously I tried to give that a shot, and found the daedalus.api.getWallets function which sounded just like the miracle I had been looking for. Unfortunately the localhost server does not seem to work anymore as pretty much all calls respond with connect ECONNREFUSED <IP_ADDRESS>:8090.
So my question is if it is possible to somehow start this service (I assume that's the node) in dummy mode to access the data stored within? There are no local key or database files that I could find (ie secrets-1.0 or similar), although I am 100% certain this is the installation that used to work.
Thank you!

Do you have a 12 world byron addres? If yes then download latest version 2.5.0 from the official IOHK website (make sure to verify pgp checksum) and then restore your wallet. If you don't have 12 words stored somewhere from your Byron era wallet then IOHK staff may still help you provided you don't tinker too much. There should be a wallet.dat somewhere file or similar which could be used to restore funds. This is a bit more tricky then.
Official http://daedaluswallet.io/ website.

As already outlined in the OP the mnemonic is no longer available. I am very apt with javascript and not scared of the electron debugger. I also have an up-to-date version of daedalus running in tandem with the old installation.
Program Files/Daedalus which contains files last modified 2017 (so that should be where it is?) contails only one .dat file, called icudtl.dat. Would this be the file in question?

I don't know exactly which file that was. I think it is possible to restore somehow but please talk to official IOHK staff or find it online

After playing around with the program a bit more, it turns out the node wouldn't start because it couldn't find the Secrets-1.0  folder.  After creating the folder manually, the program started normally, although obviously without any known wallets, as I just created an empty folder for them. I assume this can only mean whichever private keys the wallet once held were deleted somehow. I surely didn't go in there and delete my keys, but I guess any chance of recovering the wallet is gone.


Assign splitting button for individual requests

Seangchan,
I tested web UI, but I didn't check if POST requests came through ok.
Hopefully you did that, or at least will try before putting this into
production.
Valentin.
On  0, ticoann<EMAIL_ADDRESS>wrote:

Merged #6627.

Reply to this email directly or view it on GitHub:
https://github.com/dmwm/WMCore/pull/6627#event-564608534

Hi Valentin,  I will test before cut the tag. The one more patch I have to put in so I will run the all of them together. Thanks.


Cluster-autoscaler: Update GCR image regularly

When testing the auto-scaling functionality, specifically the multiple AWS ASG capability.  The latest image (v0.4.0) on gcr does not support the new flag --expander.

Related to #2434 request to have a regularly built 'latest' labelled image

+1

Just so you know, there is a more recent image now 0.5.0-beta1

We update the image along with major Kubernetes releases.
0.5.1 has been released with 1.6.
As CA is still in beta we don't maintain full compatibility with all K8S releases. Until GA, Cluster-Autoscaler should be used only with the release it is meant for. See README.md for details.


[macOS, Dark Theme] In the process of changing the size of the window, there will be some areas that cannot be drawn in time

DUPLICATE OF THIS ISSUE: https://github.com/JetBrains/compose-jb/issues/1800
In the process of changing the size of the window, there will be some areas that cannot be drawn in time, resulting in white blocks, see the video:
https://user-images.githubusercontent.com/5214214/203485599-2b832ee1-8525-4d95-8b48-ce30c45b81f0.mp4
I would like to ask if there is any way to solve this kind of detail problem? Thanks!
kotlin.version=1.7.20
agp.version=7.1.3
compose.version=1.2.1

Reproducible on any Java runtime version.

@drakeet

Do you test it on MacOS, Windows, or Linux?
Do you have a dark theme enabled?

@dima-avdeev-jb

Just test it on macOS. Use that codeviewer example to reproduce.
Yes, the system dark theme/mode is enabled.

Thanks for the description!
I think it's related to another issue: https://github.com/JetBrains/compose-jb/issues/1800

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


WIP: Indent soft wrap

This doesn't fully work yet but it may be useful to show it nevertheless, because I think it demonstrates two things:

Implementing this on atom/atom required me to touch several places in the application. Sure, this project is definitely smaller and there are less constraints in place, but I think this a good indicator that we're on the right track, @nathansobo: a centralized place where we can handle buffer-related stuff seems like a nice thing to have.
Although it's great that each transformation handle its own thing, it seems to me like some concepts cross many Transform objects. For instance, as you can see in this PR, I needed to identify which was the current line's indentation: a rudimental implementation was to simply inspect the leading source positions for the presence of tabs; however, I feel like, at this level, we should not decrease the level of abstraction but rather, only where it makes sense,  collect information for each layer transformation and make it available to the next ones (I am thinking to something like Rack).

There are still a couple of issues in this PR. The most important is that clipping backwards does not work when we are on a soft-wrapped line with indentation: I need to dig a bit deeper, but I feel like this should be quite easy to fix.
/cc: @maxbrunsfeld @nathansobo

@as-cii Before we make too many more changes to the layers, perhaps you can experiment with change propagation through additional layers. An example is implemented in the characters layer, where we determine which regions in a layer were invalidated by a change to its source layer and recompute them. For many layers it's straightforward, but for soft wraps it's possible for a change on a preceding region to cascade to subsequent regions of the soft wrap. Maybe the best way to implement this is to mark certain regions as being sensitive to the invalidation of regions before them... something like propagateInvalidation: true. Then when a soft-wrapped region gets invalidated, we'll propagate this invalidation to the end of the soft-wrapped line and rebuild everything.

Off to a great start. I hear what you're saying about conveying information between layers, but I'm not convinced this is a good use-case for it. I'm pretty sure we can just read the leading whitespace at the beginning of the line we're wrapping and carry it through by inserting a similarly sized region after each soft wrap.

@as-cii You may want to hold off doing too much more work on this repository because @maxbrunsfeld and I are exploring an approach this is similar in some ways but dramatically different in others. http://github.co/maxbrunsfeld/text-transform-3

You may want to hold off doing too much more work on this repository because @maxbrunsfeld and I are exploring an approach this is similar in some ways but dramatically different in others. http://github.com/maxbrunsfeld/text-transform-3

Unfortunately today I couldn't find the time to get my hands on this issue, but that's probably ok since you're working on an alternative implementation.
I had a brief look at it and it looks quite promising: great job @nathansobo @maxbrunsfeld! :tada: It may be interesting to understand the reasons behind this new approach, and why you opted to spike this new solution. From my side, I like the analogy of producers and consumers: TransformIterator could probably draw regions (or whatever it needs to translate positions) without transformations having to worry about that.
Moreover, I think it does solve one of the issues I encountered while tackling this early on: when searching for spaces, I could only find tabs with the current implementation (e.g. startsWith or positionOf do translate the position, but they still search inside the original buffer). As a result, I believe it's absolutely legit for each transformation to have its own buffer, without even worrying about a slice or a getContent method: everything is handled right inside operate.
As usual, I would :heart: to get involved on that spike as well. It has been awesome to work with you on this so far and I would be more than happy to provide my help :blush:
@nathansobo: in the meantime, do you think we should go on with this or should I simply put it on pause?

The big idea with the new spike is to avoid re-traversing to a position in a source layer every time we need to compute a region in the target layer. It actually avoids all the point math entirely in each transform by being entirely based on a streaming design: each transform just pulls content from a source iterator and writes it to the target. However, we still need to figure out how to integrate this approach with a creating and maintaining cached position mapping in each layer and handle incremental changes. I think at this point it would be best to pause on this PR... we need a little time to get clarity on our approach. Your comments and ideas are welcome however.

It actually avoids all the point math entirely in each transform by being entirely based on a streaming design: each transform just pulls content from a source iterator and writes it to the target. However, we still need to figure out how to integrate this approach with a creating and maintaining cached position mapping in each layer and handle incremental changes.

I don't know if you want to get rid of the whole Region concept, but I believe that regions can be inferred automagically from this new design. Simply put, when consuming and producing content, regions get mapped one another hiding this whole complexity to transforms. However, I am not sure we can get completely get rid of Point math: at some Point (sorry for the pun here :smile: ) we need to map each transform to the next one, and this will require storing points.
As for incremental changes, I think that transforms could give a hint when producing content, telling that whenever some kind of change happens on the next transform, the produced content must change too. Ideally, for some transformations, we should be able to link produced contents together so that the change gets propagated only to the interested chunks of the buffer.
I think this new design fits quite well with what we were exploring here: where it really shines (and diverges from the ideas outlined in this repo) is the automatic Region inference.

As for incremental changes, I think that transforms could give a hint when producing content, telling that whenever some kind of change happens on the next transform, the produced content must change too.

A quick thought on this statement I made early on. :bulb:
To further simplify the logic in transforms objects, we could even assume that all the consuming/producing operations made inside a single operate call must be seen as linked. In other words, if during an "operate session" the source is consumed and something is produced, we automatically infer that the produced content is associated with the consumed one.
Not a disruptive idea, I know, but I thought it may have been good sharing it with you :blush:

we could even assume that all the consuming/producing operations made inside a single operate call must be seen as linked.

That was exactly what we were thinking as well. The idea would be to match up calls to produce/consume so we automatically harvest the spatial mapping. Hopefully we'll have the basics fleshed out soon.

That was exactly what we were thinking as well. The idea would be to match up calls to produce/consume so we automatically harvest the spatial mapping. Hopefully we'll have the basics fleshed out soon.

Awesome! :sparkles: I am looking forward to getting my hands on it as soon as possible! :+1: :+1: :+1:


bluetooth: controller: consider privacy in address type check

With privacy 'tx_addr' can be true even with ctrl random address of
all zeros. In the case of privacy the check should be based on
own address type
Signed-off-by: Erik Brockhoff<EMAIL_ADDRESS>

@erbr-ot what is the failure this PR is fixing? The check was added recently wherein a conformance test failed for allowing use of all-zeroes random address in advertising.

Hey @cvinayak, @joerchan and @carlescufi,
Well, it seems I hit some bump on the EBQ road. The tests HC/DDI/BI-06/07 which I saw pass with my modification, are now not passing - and I have not been able to determine what 'happened', so I apologize for the noise. Please disregard this PR for the time being. I'll ping you directly when I have more info.

Hey @cvinayak, @joerchan and @carlescufi,
Well, it seems I hit some bump on the EBQ road. The tests HC/DDI/BI-06/07 which I saw pass with my modification, are now not passing - and I have not been able to determine what 'happened', so I apologize for the noise. Please disregard this PR for the time being. I'll ping you directly when I have more info.

@erbr-ot I see some issues here. Please wait with your investigations, I'll create a PR and if you don't mind could you run EBQ for me on it?
I have fixed some issues, but couldn't exactly explain how you ran into your issue, so the fact that you don't end up in the same situation is good news to me.

This is covered by en even better PR https://github.com/zephyrproject-rtos/zephyr/pull/21525 created by @joerchan.


Added Open_Llama Miner Requirements and Replaced Transformer

Added the Transformer required for Llama, and sentencepiece module which is also required to load Llama in the requirements.txt file.
Replaced AutoModelForCausalLM and AutoTokenizer with LlamaForCausalLM and LlamaTokenizer, respectively, in the neuron.py file.

Closing and merging your changes because we did an update on how we do huggingface miners (created an ABC).
See - https://github.com/opentensor/bittensor/pull/1364


Update for bonsai

Includes fix for warning messages:
Supersedes #15
Supersedes #16
Pull Request Checklist
Is this in reference to an existing issue?
General

[X] Update Changelog following the conventions laid out here

[ ] Update README with any necessary configuration snippets

[ ] Binstubs are created if needed

[X] RuboCop passes

[ ] Existing tests pass

New Plugins

[ ] Tests

[ ] Add the plugin to the README

[ ] Does it have a complete header as outlined here

Purpose
Known Compatibility Issues

lgtm


Node-set arguments are returned as absolute path.

Closes #525
Why is this the best possible solution? Were any other approaches considered?
The expansion of previous working solution.
What are the regression risks?
None.
Does this change require updates to documentation? If so, please file an issue here and include the link below.
No.
Before submitting this PR, please make sure you have:

[x] included test cases for core behavior and edge cases in tests_v1
[x] run nosetests and verified all tests pass
[x] run black pyxform to format code
[x] verified that any code or assets from external sources are properly credited in comments

After conversation in #525, we've decided not to do this for now because it changes long-standing behavior. The effect is mostly on folks who use nested repeats but it may also result in performance issues in other contexts.


RuntimeError: don't know how to restore data location of torch.FloatStorage

I am trying to train Yolov5 using DML and after tweaks in the code to let it use the DML device, I have this error when it tries to load the weights on the GPU:
 File "D:\Documenti\models\GTA_code\dml\lib\site-packages\torch\serialization.py", line 592, in load
    return _load(opened_zipfile, map_location, pickle_module, **pickle_load_args)
  File "D:\Documenti\models\GTA_code\dml\lib\site-packages\torch\serialization.py", line 851, in _load
    result = unpickler.load()
  File "D:\Documenti\models\GTA_code\dml\lib\site-packages\torch\serialization.py", line 843, in persistent_load
    load_tensor(data_type, size, key, _maybe_decode_ascii(location))
  File "D:\Documenti\models\GTA_code\dml\lib\site-packages\torch\serialization.py", line 832, in load_tensor
    loaded_storages[key] = restore_location(storage, location)
  File "D:\Documenti\models\GTA_code\dml\lib\site-packages\torch\serialization.py", line 812, in restore_location
    return default_restore_location(storage, str(map_location))
  File "D:\Documenti\models\GTA_code\dml\lib\site-packages\torch\serialization.py", line 178, in default_restore_location
    raise RuntimeError("don't know how to restore data location of "
RuntimeError: don't know how to restore data location of torch.FloatStorage (tagged with dml)

Loading pretrained weights is not a supported feature..?

Update, I have fixed that problem using:
torch.load(weights, map_location={'0':'dml'})
But now, I have this just at the start of the training (I have replaced SiLu with ReLu since is not supported):
libprotobuf FATAL D:\a\_work\1\s\caffe2\dml\dml_command_recorder.cc:361] CHECK failed: ((((HRESULT)((current_command_list_->Close()))) >= 0)) == (true):
val: Scanning 'D:\Projects\python\semantics\project\tests\annotations\multiclass\dataset\valid\labels.cache' images and
  0%|          | 0/11 [00:00<?, ?it/s]
Traceback (most recent call last):
  File "train.py", line 640, in <module>
    main(opt)
  File "train.py", line 537, in main
    train(opt.hyp, opt, device, callbacks)
  File "train.py", line 331, in train
    loss, loss_items = compute_loss(pred, targets.to(device))  # loss scaled by batch_size
  File "D:\Documenti\models\yolov5\utils\loss.py", line 120, in __call__
    tcls, tbox, indices, anchors = self.build_targets(p, targets)  # targets
  File "D:\Documenti\models\yolov5\utils\loss.py", line 199, in build_targets
    j, k = ((gxy % 1 < g) & (gxy > 1)).T
  File "D:\Documenti\models\GTA_code\dml\lib\site-packages\torch\tensor.py", line 591, in __iter__
    return iter(self.unbind(0))
RuntimeError: CHECK failed: ((((HRESULT)((current_command_list_->Close()))) >= 0)) == (true):

If needed, this is yolov5 loss script

Hi @masc-it, thanks for reporting this issue. Can you try our latest release on Pypi to see if you are still experiencing this issue?
Also can you share an e2e python script for us to reproduce your error?

Hi @ryanlai2, I've met the same issue too. When I was running train.py, a runtime error occurred as RuntimeError: CHECK failed: ((((HRESULT)((dml_device_->GetDeviceRemovedReason()))) >= 0)) == (true):. The traceback was the same as above.

Hi @masc-it, thanks for reporting this issue. Can you try our latest release on Pypi to see if you are still experiencing this issue?
Also can you share an e2e python script for us to reproduce your error?

You can directly try YoloV5 tutorial (train section), using dml as device.

Anyways, @ryanlai2 I have tried the latest pytorch-directml and this is the result now:
YOLOv5  v6.0-207-g8efe977 torch 1.8.0a0+14f3b5d CPU

Fusing layers...
Model Summary: 213 layers, 1760518 parameters, 0 gradients
1/1: 0...  Success (inf frames 640x480 at 30.00 FPS)

Traceback (most recent call last):
  File "age.py", line 319, in <module>
    main(opt)
  File "age.py", line 314, in main
    run(**vars(opt))
  File "D:\Documenti\win_venvs\directml\lib\site-packages\torch\autograd\grad_mode.py", line 27, in
decorate_context
    return func(*args, **kwargs)
  File "age.py", line 173, in run
    model.warmup(imgsz=(1, 3, *imgsz), half=half)  # warmup
  File "D:\Documenti\models\yolov5\models\common.py", line 460, in warmup
    self.forward(im)  # warmup
  File "D:\Documenti\models\yolov5\models\common.py", line 397, in forward
    y = self.model(im) if self.jit else self.model(im, augment=augment, visualize=visualize)
  File "D:\Documenti\win_venvs\directml\lib\site-packages\torch\nn\modules\module.py", line 889, in
_call_impl
    result = self.forward(*input, **kwargs)
  File "D:\Documenti\models\yolov5\models\yolo.py", line 126, in forward
    return self._forward_once(x, profile, visualize)  # single-scale inference, train
  File "D:\Documenti\models\yolov5\models\yolo.py", line 149, in _forward_once
    x = m(x)  # run
  File "D:\Documenti\win_venvs\directml\lib\site-packages\torch\nn\modules\module.py", line 889, in
_call_impl
    result = self.forward(*input, **kwargs)
  File "D:\Documenti\models\yolov5\models\common.py", line 50, in forward_fuse
    return self.act(self.conv(x))
  File "D:\Documenti\win_venvs\directml\lib\site-packages\torch\nn\modules\module.py", line 889, in
_call_impl
    result = self.forward(*input, **kwargs)
  File "D:\Documenti\win_venvs\directml\lib\site-packages\torch\nn\modules\conv.py", line 399, in fo
rward
    return self._conv_forward(input, self.weight, self.bias)
  File "D:\Documenti\win_venvs\directml\lib\site-packages\torch\nn\modules\conv.py", line 395, in _c
onv_forward
    return F.conv2d(input, weight, bias, self.stride,
RuntimeError: tensor.is_dml() INTERNAL ASSERT FAILED at "D:\\a\\_work\\1\\s\\pytorch-directml\\aten\
\src\\ATen\\native\\dml\\DMLTensor.cpp":33, please report a bug to PyTorch. unbox expects Dml tensor
 as inputs

Model seems to be correctly loaded though.

Hi, and thanks for posting the issue.
We have not taken a look at yolov5 yet, and as such the operators needed to get yolov5 working end-to-end are spotty.
We absolutely intend to support yolov5 in the future, and will update this thread when we expect to have the operator conformance needed to enable it.

#https://github.com/ultralytics/yolov5/issues/7642

Hello, do you support YOLOV4?

below code should work for majority of issues related to " dont know how to restore data location of torch.storage._untype storage ( tagged with gpu)
import torch
import whisper
devices = torch.device("cuda:0" if torch.cuda.is_available() else "cpu")
model = whisper.load_model("medium" , device =devices)

Same thing, this really gets me when Microsoft makes it sound like it's so simple to do something and then you do it and it just barfs.

Hey there,
i had same issue while using easyocr but when i declared gpu=False it worked as much as i have searched this issue has something to do with gpu

Same issue.


incorrect area_type key in js object

I believe the object returned from the server labels this as "area_type" not "field_farm_area_type" But I may be mistaken, this could be a difference between languages or my misinterpretation farmOS.js?
Just an issue I came across while cross-referencing APIs.
https://github.com/farmOS/farmOS.js/blame/master/README.md#L230

Good catch, thanks @paul121!


DatabaseConnector_mysql uses deprecated PHP MySQL extension.

The DatabaseConnector_mysql class, located inside src/ToolProvider/DataConnector, uses the mysql extension, no longer allowed by PHP. This should be updated to use the improved mysqli extension. More info here: http://php.net/manual/en/book.mysqli.php

This is just one of the options available for this library - another already provided is for PDO connections.  More will be added later.


Add ability to modify or friendly format numerical values

It would be useful to have an option that friendly formatted or applied modifiers to numbers.
For example, if you had the float:
5081998.9369165478

It would print it out as:
5,081,998.9369165478

I'm currently printing out a large table of numbers using csvlook, and it would be much more readable if I could add commas to all the numbers, so I can get a rough idea of scale (particularly since the numbers are all left-aligned, and not right-aligned, and I can't seem to find a way in csvkit to change that).
Or you might have modifiers to truncate the fractional part, rounded up/down etc. which you can apply before printing.

The implementation of this functionality is moving out of the csvkit repository into its new dependency agate (#515). This is the file that would need to be modified. You may re-open your issue on agate.


Sorry, your request was rate-limited. Please wait 8 seconds before trying again.

Type: Bug
Sorry, your request was rate-limited. Please wait 8 seconds before trying again. error
Extension version: 0.21.1
VS Code version: Code 1.94.2 (384ff7382de624fb94dbaf6da11977bba1ecd427, 2024-10-09T16:08:44.566Z)
OS version: Windows_NT x64 10.0.22631
Modes:

A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythongtdpath:30769146
pythonnoceb:30805159
asynctok:30898717
pythonmypyd1:30879173
2e7ec940:31000449
pythontbext0:30879054
accentitlementsc:30995553
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
f3je6385:31013174
a69g1124:31058053
dvdeprecation:31068756
dwnewjupytercf:31046870
newcmakeconfigv2:31071590
impr_priority:31102340
nativerepl1:31139838
refactort:31108082
pythonrstrctxt:31112756
wkspc-onlycs-t:31132770
wkspc-ranged-t:31151552
cf971741:31144450
autoexpandse:31146404
iacca2:31156134
notype1cf:31157160
controlgs:31153265
5fd0e150:31155592

Hi @marta-pekar , thank you for filing this issue.
This message comes when you send too many requests in a short period of time. Was that the case when you saw this message?


Annual average preprocessor

Hi all,
Greetings from SMHI! @ruthlorenz just noticed that there isn't an annual average preprocessor. It would be a very useful feature to include, and it's surprising that it isn't there yet!
The code needed is very basic!
def annual_mean(cube):
    """
    Function to compute annual means.

    Arguments
    ---------
        cube: iris.cube.Cube
            input cube.
    Returns
    -------
    iris.cube.Cube
        Annual mean cube
    """
    return cube.aggregated_by('year', iris.analysis.MEAN)

@ledm feel free to extend the time-area module with this functionality!

Alternatively, perhaps we could add something with more functionality? It would be great to make a time -annual_average function which includes annual means but also  an arbitrary number of years ie: 5 yearly means, decadal, 20 years means etc...
In addition, I'd prefer to keep it separate from the currently implemented "seasonal_means", as this is a special case of time average that uses the iris season coordinate.

Added the basic functionality in this branch:
https://github.com/ESMValGroup/ESMValTool/tree/version2_development_annual_average_825

Can you also make sure that the documentation is updated?

Yes, I'll add the documentation and tests too before we merge it. This functionality was just so that @ruthlorenz can get started today.

added a decadal mean, may make this even more general by changing the get_decade function to grab any period of X years


todoreview command does not exist

Hi,
I just installed ToDoReview via packagecontrol, but when using the pallet to find the supposedly installed command "todoreview", nothing show up.
I restarted ST2, swapped a few projects and still no "todo review" command in the pallet.
So basically, I can't manage to use the plugin. Any idea what's wrong?

I would recommend disabling all other plugins to ensure you don't have some kind of collision.
Other than that, check console (ctrl+~) and let me know if you have any errors.

Thanks for the tip, I've disabled quite a few packages but the error remains. Console extract:
Reloading plugin /home/gman/.config/sublime-text-2/Packages/TodoReview/TodoReview.py
Traceback (most recent call last):
  File "./sublime_plugin.py", line 62, in reload_plugin
  File "./TodoReview.py", line 10, in <module>
    import io
  File ".\io.py", line 63, in <module>
ImportError: No module named _fileio

I don't know anything about python...

Looks like you have some environment issues. It's not able to import the standard io library.
I did a quick google and it looks like this is a problem with Ubuntu in particular. I would recommend you do the same and try some of the fixes. I don't know what else to tell you beyond that.

after googling for solutions, what solved the problem was the package manager fixing and updating its package. Indeed, after installing ST3, todoreview works fine.
So the issue is with ToDoReview package on ST2. Good luck fixing it

@djahma Well ST2 is on Python 2.x while ST3 is on Python 3.x. It seems that the environment issue on Ubuntu only occurs in 2.x, so even though the upgrade fixed it, it isn't an issue with the package. :)

ok, well thanks for looking into it anyway, and your fast responses!

Replace
import io
to
import StringIO as io
in TodoReview.py


Workbench fixes

ligther startstop profiles (no stuffed UTxO and no extra delegations)
better node startup error handling (prevent halfway-started clusters from leaking processes)
new tracing has dropped the Cardano.Node prefix, so locli had to be updated
-autostay makefile target variants now actually stay after successful runs
fix analysis for short-lived profiles, by not filtering out all data (used to drop first two epochs)

CI has passed, and this only affects workbench, merging directly.


Named for openapi schema extension doesn't extracts into components.schema

export const PublicUserSchema = z.object({
    id: z.string().uuid(),
    avatarUrl: z.string().optional(),
    name: z.string(),
    email: z.string(),
}).openapi("User");

export const AgentUserStateSchema = z.enum(["active", "inactive"]).openapi("UserState");
export const AgentUserSchema = PublicUserSchema.extend({
    state: AgentUserStateSchema,
}).openapi("User");

export getUser = (): RouteConfig => ({
        summary: "Get user",
        tags,
        method: "get",
        operationId: "getUser",
        path: "/users/{userId}",
        request: {
            params: z.object({
                userId: UserIdPathParameter,
            })
        },
        responses: {
            "200": {
                description,
                content: {
                     "application/json": {
                           schema: AgentUserSchema,
                     }
                }
           }
    })

This leads to that schema being inlined into request as:
/users/{userId}:
    get:
      summary: Get user
      tags:
        - user
      operationId: getUser
      parameters:
        - schema:
            $ref: "#/components/schemas/UserId"
          required: true
          in: path
          name: userId
      responses:
        "200":
          description: User
          content:
            application/json:
              schema:
                allOf:
                  - $ref: "#/components/schemas/User"
                  - allOf:
                      - $ref: "#/components/schemas/User"
                      - type: object
                        properties:
                          state:
                            $ref: "#/components/schemas/UserState"
                        required:
                          - state

I'd expect it to be as well extracted to components.schema.
So, I'd like it to be extracted into components.schema part.
As another possibility I'm looking for, is to avoid allOf usage for extension, and have a hard merged objects. Is it possible?

Okay, seems like I figured answer to my question.
if I do the hard copy, instead of .extend(),
export const AgentUserSchema = z.object({
    ...PublicUserSchema.shape,
    state: AgentUserStateSchema,
}).openapi("User");

Then it produces hard type (without anyOf).
Still, with the inline part, I think it is a bug of itself.

@artsiommiksiuk thank you for the report. The problem is that you are reusing the openapi "name" - you have User twice. If you have for example:
export const AgentUserSchema = PublicUserSchema.extend({
  state: AgentUserStateSchema,
}).openapi('AgentUser');

you would have a separate schema defined that extends the current User schema.
And I believe that this is how it should behave. If we were to override with the last usage of the "User" registration the we would need to inline the base User schema properties id + avatarUrl + name + email as otherwise there wouldn't be anything to reference (User would be a circular reference).
I am since going to close this issue. If you have any other questions and/or issues feel free to ask!


Collections show all collections

The collection list on my dashboard shows the entire lists of system collections not just my collections.

This was fixed in Sufia projecthydra/sufia#1024 but hasn't been released yet. We could release Sufia 6.0.1 for that.


CSS fonts (woff,woff2)in node_modules for production bundle raised 404 error

demo project: https://github.com/softboy99/vite-devexteme21_1.git.
vite version: 2.5.3
vue version:3.2.7
problems: woff are missing for production bundle. In chrome dev tools, there are 404 errors for .woff file. Which are ok for dev mode.
@softboy99 would you open a new issue against the latest version so we can better track it? Thanks!
Originally posted by @patak-js in https://github.com/vitejs/vite/issues/3914#issuecomment-871174188

Hi,
is it fixed in 2.4.2?

Hi,
problem still exists in 2.4.3

Hi,
problem still exists in 2.5.0

There is currently now PR associated to this issue 🤔
So you can assume that no-one is working on this 🤷
You could be proactive here and just start a PR and try to fix it yourself

Hi,
which PR,Could you please tell me? Thanks. I tried vite 2.5.1 + vue 3.2.6, problem still  exists.

which PR

Please read again https://github.com/vitejs/vite/issues/4148#issuecomment-900347163

Hi,
@sodatea , this issue exists from 2.3.x, when it can be fixed?

Hi,
@sodatea , this issue exists from 2.3.x, when it can be fixed?

Can't reproduce. Nothing's wrong when on my machine. (I removed yarn.lock before installing the dependencies, so that I can use the latest dependencies)

Hi,
@sodatea  , not for localhost debug, debug mode, it's ok , but for production build bundle, Robo-400.woff2/Robo-500.woff2 raised 404 error

This page is served in production. It's localhost:5000 served by npm run build && npm run serve, not localhost:3000 by npm run dev.

Hi,
May be there are some differences with localhost. I deploy it in nginx. All of the woff,woff2 were requesed by url of "http://.com/node_modules/devextreme/dist/css/fonts/.woff2" for the index.css. Although the in the index.css file the @import is from another url(http://fonts.googleapis.com)

All of the woff,woff2 were requesed by url of "http://.com/node_modules/devextreme/dist/css/fonts/.woff2" for the index.css

This only happens in dev, which is expected.

I've checked again and there's not a single reference to the node_modules directory in dist after npm run build.

Hi,
@sodatea, yes, but in browser network tab, the requested url is displayed with "http://.com/node_modules/devextreme/dist/css/fonts/.woff2"

I can't reproduce that.

Hi,
i have found the problem, its network problem, i have replace 'fonts.googleapis.com' with "fonts.font.im". you can close this issue. Thanks a lot for your great help.

Hi,
i have found the problem, its network problem, i have replace 'fonts.googleapis.com' with "fonts.font.im". you can close this issue. Thanks a lot for your great help.


Stopped uploading and pulsing working light

Hello,
My enviro weather was working fine, then after about 8 hrs the white pulsing light just pulses until I go and hit reset or do something - it stopped transmitting data in this time too. This has happened two nights in a row and below is my log file . At 19:40 is when the pulsing started and continued till I took the unit down (20 hours later).
2022-09-18 19:25:02 [info     /  116016] hey enviro, let's go!
2022-09-18 19:25:02 [info     /  114320]  - --=-=-===-=-=-- -
2022-09-18 19:25:02 [info     /  112720]
2022-09-18 19:25:03 [debug    /  111104] > performing startup
2022-09-18 19:25:03 [debug    /  109408]   - hold vsys_en high
2022-09-18 19:25:03 [info     /  107632]   - wake reason: unknown
2022-09-18 19:25:03 [debug    /  105904]   - turn on activity led
2022-09-18 19:25:03 [debug    /  101440] > 89 blocks free out of 212
2022-09-18 19:25:04 [info     /   92320] > 1 cache files need uploading
2022-09-18 19:25:04 [info     /  115792] > connecting to wifi network 'asus_monster_mesh'
2022-09-18 19:25:09 [error    /   95664] ! failed to connect to wireless network asus_monster_mesh
2022-09-18 19:25:09 [error    /   93520]   - cannot upload readings, wifi connection failed
2022-09-18 19:25:09 [info     /   91712] > going to sleep
2022-09-18 19:25:10 [debug    /   89664]   - clearing rtc alarm flags
2022-09-18 19:25:10 [info     /   87632]   - setting timer to wake in 5 minutes
2022-09-18 19:25:10 [info     /   85696]   - shutting down
2022-09-18 19:30:02 [info     /  119424]
2022-09-18 19:30:02 [info     /  117808] hey enviro, let's go!
2022-09-18 19:30:02 [info     /  116112]  - --=-=-===-=-=-- -
2022-09-18 19:30:02 [info     /  114512]
2022-09-18 19:30:03 [debug    /  112896] > performing startup
2022-09-18 19:30:03 [debug    /  111200]   - hold vsys_en high
2022-09-18 19:30:03 [info     /  109424]   - wake reason: unknown
2022-09-18 19:30:03 [debug    /  107696]   - turn on activity led
2022-09-18 19:30:03 [debug    /  103232] > 89 blocks free out of 212
2022-09-18 19:30:04 [info     /   94032] > 2 cache files need uploading
2022-09-18 19:30:04 [info     /  115840] > connecting to wifi network 'asus_monster_mesh'
2022-09-18 19:30:09 [info     /   96048]   - ip address:  <IP_ADDRESS>
2022-09-18 19:30:10 [info     /  110976] > uploading cached readings to <IP_ADDRESS>
2022-09-18 19:30:10 [info     /  104720]   - uploaded 2022-09-18 19:25:04.json
2022-09-18 19:30:10 [info     /  100144]   - uploaded 2022-09-18 19:30:04.json
2022-09-18 19:30:10 [info     /   98208] > going to sleep
2022-09-18 19:30:10 [debug    /   96336]   - clearing rtc alarm flags
2022-09-18 19:30:10 [info     /   94304]   - setting timer to wake in 5 minutes
2022-09-18 19:30:10 [info     /   92368]   - shutting down
2022-09-18 19:35:02 [info     /  118528]
2022-09-18 19:35:02 [info     /  116912] hey enviro, let's go!
2022-09-18 19:35:02 [info     /  115216]  - --=-=-===-=-=-- -
2022-09-18 19:35:02 [info     /  113616]
2022-09-18 19:35:02 [debug    /  112000] > performing startup
2022-09-18 19:35:03 [debug    /  110304]   - hold vsys_en high
2022-09-18 19:35:03 [info     /  108528]   - wake reason: unknown
2022-09-18 19:35:03 [debug    /  106800]   - turn on activity led
2022-09-18 19:35:03 [debug    /  102336] > 88 blocks free out of 212
2022-09-18 19:35:04 [info     /   93232] > 1 cache files need uploading
2022-09-18 19:35:04 [info     /  115840] > connecting to wifi network 'asus_monster_mesh'
2022-09-18 19:35:09 [info     /   97280]   - ip address:  <IP_ADDRESS>
2022-09-18 19:35:09 [info     /  110976] > uploading cached readings to <IP_ADDRESS>
2022-09-18 19:35:09 [info     /  104896]   - uploaded 2022-09-18 19:35:04.json
2022-09-18 19:35:10 [info     /  102784] > going to sleep
2022-09-18 19:35:10 [debug    /  100912]   - clearing rtc alarm flags
2022-09-18 19:35:10 [info     /   98880]   - setting timer to wake in 5 minutes
2022-09-18 19:35:10 [info     /   96944]   - shutting down
2022-09-18 19:40:02 [info     /  117792]
2022-09-18 19:40:02 [info     /  116176] hey enviro, let's go!
2022-09-18 19:40:02 [info     /  114480]  - --=-=-===-=-=-- -
2022-09-18 19:40:03 [info     /  112880]
2022-09-18 19:40:03 [debug    /  111264] > performing startup
2022-09-18 19:40:03 [debug    /  109568]   - hold vsys_en high
2022-09-18 19:40:03 [info     /  107792]   - wake reason: unknown
2022-09-18 19:40:03 [debug    /  106064]   - turn on activity led
2022-09-18 19:40:03 [debug    /  101600] > 88 blocks free out of 212

Hi. Do you know which version of the firmware you were running? The white LED pulsing is usually an indication that the board is attempting to upload a file. The fact you are not seeing that at the end of the log is strange.
There have been a bunch of issues with Enviro Weather that I've been attempting to solve over in the patch branch. Perhaps its worth you trying out that code and reporting back?

Hello,
This was experienced with v008, I tried 002 and while it worked better it
still never managed more than a few days at best. In both cases the device
is just not reliable. Sadly I think I will attempt to build (using a guide)
a raspberry pi weather station in the hope it might be a bit more reliable.
Honeslty kinda annoyed that pimoroni sell the board as a product without
mentioning anything on the webpage.
Patrick
On Fri, 11 Nov 2022 at 12:30, ZodiusInfuser @.***>
wrote:

Hi. Do you know which version of the firmware you were running? The white
LED pulsing is usually an indication that the board is attempting to upload
a file. The fact you are not seeing that at the end of the log is strange.
There have been a bunch of issues with Enviro Weather that I've been
attempting to solve over in the patch branch. Perhaps its worth you
trying out that code and reporting back?
—
Reply to this email directly, view it on GitHub
https://github.com/pimoroni/enviro/issues/97#issuecomment-1311642188,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKAERSUVBAMYP3AZYMM4KPTWHY343ANCNFSM6AAAAAAQR33AWY
.
You are receiving this because you authored the thread.Message ID:
@.***>


Updating query calls both onEditQuery and onEditVariables handlers

When updating a query, I noticed both the onEditQuery and onEditVariables handlers are called. This is not the case for the variables section. This is causing a race condition for us when selecting from history causing the variables section to be cleared.

Hey @nmampersand 👋 thanks for reporting! Quickly confirmed, this is indeed happening on the latest state of main

There is actually a reason for this: The state of the variable editor "depends" on the query editor, because we "lint" variables (basically checking if a given variable does exist in the query and if the type matches). To achieve this we set some custom properties on the editor instance and signal a change after updating them. However, this also causes the onEditVariables callback to be triggered, which is rather confusing as consumer and should not happen.
I haven't yet figured out the best way to solve this, might have some more time this week to look into it.

The fix has just been published in 1.9.13

Works great, thank you so much for the quick resolution!


[BUG] Enable avfriendlyname only when upnpav is set

In order to prevent issues with the FRIENDLY_NAME variable, we need to enable the avfriendlyname in configuration only if upnpav (UPNPAV) is set to 1.

Available in release 2022-11-19


Support Regex in replaceAttrValues

🚀 Feature Proposal
Support regular expressions in replaceAttrValues
Motivation
I'm working in a project where I get SVG files from a UX designer, and they some times include spesific color codes instead of fill="currentColor" which is what I need to use the icons as React-components. I've compiled a list of hex codes that I replace with currentColor, but every time a new hex code appears I have to update my code.
Example
Without regular expressions:
"svgr": {
   "replaceAttrValues": {
      "#6C6C6C": "currentColor",
      "#B8B8B8": "currentColor",
      "#467EFF": "currentColor",
      "#E6A72B": "currentColor",
      (...)
    }
  }

With regular expressions
"svgr": {
    "replaceAttrValues": {
      "/#[0-9A-F]{6}/g": "currentColor"
    }
  }

Pitch
This will make svgr an even better tool for generating and modifying svg files.
Also, everyone loves regular expressions ❤

i will work on this issue today @gregberge

I've made some code for RegExp usage
You could change this file<EMAIL_ADDRESS>And even make a patch with patch-package
 "svgr": {     "replaceAttrValues": {       "/#[0-9A-F]{3,6}/gi": "currentColor"     }   }
index.txt


merge of merkle blocks anchored to the same TXID can fail

Running a test on rgb-lib many times I've discovered a rare error, that seems related to the merge of two merkle blocks (sharing the same TXID).
More specifically, the error occurs when rgb-node calls self.store.store_merge(db::ANCHORS, anchor.txid, anchor)?; (https://github.com/RGB-WG/rgb-node/blob/master/src/bucketd/processor.rs#L221), which leads to
commit_verify calling unreachable!("broken merkle block merge-reveal algorithm") (https://github.com/LNP-BP/client_side_validation/blob/4de299e0517e8734d8629169a86409a01de2a409/commit_verify/src/lnpbp4.rs#L826).
This can happen (around once every 10 test runs) when calling the consume_transfer API.
Here some logs from process_consignment() (in src/bucketd/processor.rs):
Stored anchor: Anchor { txid: b6515f51113235c41c815a82085afd27f7912f5a4cd6bffaef4dcd3ef10c9a12, lnpbp4_proof: MerkleBlock { depth: 3, cross_section: [ConcealedNode { depth: 3, hash: 03e43c730e76e654a40fdc0b62940bb7382ed95d4e8124ba687b4ec470cd1f01 }, CommitmentLeaf { protocol_id: Slice32(391cfae9f7b23562826b3260831e92698c7ec43c49e7afeed8e83a1bd75bbce9), message: 72c7278c8337a0480aa343dae2e6e6e1aee6c7b3df7d88f150a21c82f2b373ac }, ConcealedNode { depth: 2, hash: d42b5b6f1d6cc564fea2258e5147f4dd07735fac5aafa4a8394feb75ed8e366d }, ConcealedNode { depth: 1, hash: 5009030a186d268e698e184cf9e32607951ab81c6e3b42ecaf6ccf73a5ca0f2e }], entropy: None }, dbc_proof: OpretFirst }
Anchor: Anchor { txid: b6515f51113235c41c815a82085afd27f7912f5a4cd6bffaef4dcd3ef10c9a12, lnpbp4_proof: MerkleProof { pos: 0, path: [5009030a186d268e698e184cf9e32607951ab81c6e3b42ecaf6ccf73a5ca0f2e, d42b5b6f1d6cc564fea2258e5147f4dd07735fac5aafa4a8394feb75ed8e366d, 8fff224a68c261d62ab33d802182ff09d6332e9079fce71936ea414ed45ee782] }, dbc_proof: OpretFirst }
Restored anchor: Anchor { txid: b6515f51113235c41c815a82085afd27f7912f5a4cd6bffaef4dcd3ef10c9a12, lnpbp4_proof: MerkleBlock { depth: 3, cross_section: [CommitmentLeaf { protocol_id: Slice32(f0f2fc11fa38f3fd6132f46d8044612fc73e26b769025edabbe1290af9851897), message: c0abbb938d4da7ce3a25e704b5b41dbacc762afe45a536e7d0a962fb1b34413e }, ConcealedNode { depth: 3, hash: 8fff224a68c261d62ab33d802182ff09d6332e9079fce71936ea414ed45ee782 }, ConcealedNode { depth: 2, hash: d42b5b6f1d6cc564fea2258e5147f4dd07735fac5aafa4a8394feb75ed8e366d }, ConcealedNode { depth: 1, hash: 5009030a186d268e698e184cf9e32607951ab81c6e3b42ecaf6ccf73a5ca0f2e }], entropy: None }, dbc_proof: OpretFirst }
thread 'bucketd' panicked at 'internal error: entered unreachable code: broken merkle block merge-reveal algorithm', /home/zoe/.cargo/registry/src/github.com-1ecc6299db9ec823/commit_verify-0.8.0/src/lnpbp4.rs:826:17

Hoping it can help debugging, I've added a log of the Stored anchor: (the one that gets merged). While Anchor: is the Anchor<MerkleProof> that gets converted to Restored anchor:, which is the Anchor<MerkleBlock> that fails merging with the stored anchor.
Here the 2 merkle blocks that fail merging pretty-printed (for the lazy ones :wink:):
MerkleBlock{
  depth: 3,
  cross_section: [
    ConcealedNode{
      depth: 3,
      hash: 03e43c730e76e654a40fdc0b62940bb7382ed95d4e8124ba687b4ec470cd1f01
    },
    CommitmentLeaf{
      protocol_id: Slice32(391cfae9f7b23562826b3260831e92698c7ec43c49e7afeed8e83a1bd75bbce9),
      message: 72c7278c8337a0480aa343dae2e6e6e1aee6c7b3df7d88f150a21c82f2b373ac
    },
    ConcealedNode{
      depth: 2,
      hash: d42b5b6f1d6cc564fea2258e5147f4dd07735fac5aafa4a8394feb75ed8e366d
    },
    ConcealedNode{
      depth: 1,
      hash: 5009030a186d268e698e184cf9e32607951ab81c6e3b42ecaf6ccf73a5ca0f2e
    }
  ],
  entropy: None
}

MerkleBlock{
  depth: 3,
  cross_section: [
    CommitmentLeaf{
      protocol_id: Slice32(f0f2fc11fa38f3fd6132f46d8044612fc73e26b769025edabbe1290af9851897),
      message: c0abbb938d4da7ce3a25e704b5b41dbacc762afe45a536e7d0a962fb1b34413e
    },
    ConcealedNode{
      depth: 3,
      hash: 8fff224a68c261d62ab33d802182ff09d6332e9079fce71936ea414ed45ee782
    },
    ConcealedNode{
      depth: 2,
      hash: d42b5b6f1d6cc564fea2258e5147f4dd07735fac5aafa4a8394feb75ed8e366d
    },
    ConcealedNode{
      depth: 1,
      hash: 5009030a186d268e698e184cf9e32607951ab81c6e3b42ecaf6ccf73a5ca0f2e
    }
  ],
  entropy: None
}

Here's an example of a working merge, in the hope it might help analyze the issue.
These are the two MerkleBlocks to be merged:
MerkleBlock{
  depth: 3,
  cross_section: [
    ConcealedNode{
      depth: 1,
      hash: 619d46fbc17c7fadecddc835f41084b9fff4a14f4bc8be1511a63c52a3bcf8eb
    },
    ConcealedNode{
      depth: 2,
      hash: 31b262976c6ae225a24a1f47f27149a07279623d12e7489cf0a90deb31731901
    },
    ConcealedNode{
      depth: 3,
      hash: 5865d6040c7586fba2f8947bf88749d78203932a1f2e84ee5ef050b547e5cd3c
    },
    CommitmentLeaf{
      protocol_id: Slice32(57e479feaeaa0be78047f8080bd3ae355ab6eabf4469413c81e17763d341dc87),
      message: b35877def35dda879d29ffbba558243cd8362983530405d2a512947f42df2d39
    }
  ],
  entropy: None
},

MerkleBlock{
  depth: 3,
  cross_section: [
    ConcealedNode{
      depth: 1,
      hash: 619d46fbc17c7fadecddc835f41084b9fff4a14f4bc8be1511a63c52a3bcf8eb
    },
    ConcealedNode{
      depth: 3,
      hash: bcdf20c3adc9a959005a1f5fde925144fbbf7adc0937f0a81ffdb207b9f83efd
    },
    CommitmentLeaf{
      protocol_id: Slice32(ddc44939452a967977d6921c24c27ffee411f8ef37894df77327bb3f9764e998),
      message: 660b186f0e7f3bfe5216d9273fa4527a52f91f17ea040dcce248ee31e5936a41
    },
    ConcealedNode{
      depth: 2,
      hash: 20a05aba6a8a62f0a01bcaa12c9cec27dc777055716ef2976223dd63a9d4ea51
    }
  ],
  entropy: None
},

and here's the result:
MerkleBlock{
  depth: 3,
  cross_section: [
    ConcealedNode{
      depth: 1,
      hash: 619d46fbc17c7fadecddc835f41084b9fff4a14f4bc8be1511a63c52a3bcf8eb
    },
    ConcealedNode{
      depth: 3,
      hash: bcdf20c3adc9a959005a1f5fde925144fbbf7adc0937f0a81ffdb207b9f83efd
    },
    CommitmentLeaf{
      protocol_id: Slice32(ddc44939452a967977d6921c24c27ffee411f8ef37894df77327bb3f9764e998),
      message: 660b186f0e7f3bfe5216d9273fa4527a52f91f17ea040dcce248ee31e5936a41
    },
    ConcealedNode{
      depth: 3,
      hash: 5865d6040c7586fba2f8947bf88749d78203932a1f2e84ee5ef050b547e5cd3c
    },
    CommitmentLeaf{
      protocol_id: Slice32(57e479feaeaa0be78047f8080bd3ae355ab6eabf4469413c81e17763d341dc87),
      message: b35877def35dda879d29ffbba558243cd8362983530405d2a512947f42df2d39
    }
  ],
  entropy: None
},

Thank you very much for the discovery and debug work. Will work on this as one of the priorities (given I can devote very small amount of time to the RGB these days, it may take some time though...)

@dr-orlovsky this issue is quite important, could you please put the task in the 0.8 milestone and give it some priority?

I am sturgling to understand some parts of this report.
I think we really need to start using the same terms, since "merge of merkle blocks anchored to the same TXID" doesn't make sense to me and I just fail to compile the meaning :(.
I can assume the real meaning was "Merging the multi-protocol commitments (or anchors?) fail in some cases" - but I am not sure how TXID appears here. There is no such thing as "anchoring to the TXID", since anchoring works the other way around: it is witness transaction (not txid) which commits ("anchors") to the multi-protocol commitment (which is in turn a commitment to a Merkle tree of commitments under different & distinct protocols).

Meanwhile I will just debug the merge-reveal algorithm in MerkleBlock since I can guess the bug is somehow related to it.

@zoedberg I finally understood your description, sorry for me whining about terminology; your description is really detailed and you provide a lot of debug information for the convenience. Starting investigation. In fact this issue shoud go to client_side_validation repo, so I will do another one there referencing this issue

Hi @dr-orlovsky,
This bug seems to become very frequent under certain circumstances and it's becoming a real show-stopper for us.
I was thinking, could I open a PR that changes that unreachable!() statement to a normal error?  It would be awesome for us if this temporary change could be merged and published in a new release of the 0.8.X series so let me know if this would be feasible without taking away too much of your time.

This should be fixed with https://github.com/LNP-BP/client_side_validation/pull/115 -- once we would merge the fix I will release new v0.8.4 version of RGB Node using fixed library.

@zoedberg new versions of all crates with updated dependency with the fix from https://github.com/LNP-BP/client_side_validation/pull/115 are released. For RGB Node this is v0.8.4. Waiting for your confirmation that this issue is now solved.

@dr-orlovsky I've missed this message, sorry. This issue can be closed as solved


Project 2 Review

Please review this work for merge

Please review this work for merge, I have changed the previous README information to match the latest version README template 🙏🏼

I have made the following corrections to make my project PR valid

managed to set up linters correctly and now all checks are running
updated my pull request title and made it more descriptive
updated the pull request description and made it more descriptive

I have made the following corrections to make my project PR valid

managed to set up linters correctly and now all checks are running
updated my pull request title and made it more descriptive
updated the pull request description and made it more descriptive

@mukhammadrizooff

here are some of the changes I've made

used br tag so It matches the design
Adjusted the spacing between the social icons


nv.d3.css - legend fix color

@fichtner
when I split the main.css, the colors in cicada for the reporting have been lost. This is unfortunately too late for this release but would still be great if you could at least merge it for the next release. sorry it was my mistake. best regards rené

Merged, thanks @opnsenseuser !


DAQCplate ppDOUT node needs better input handling and documentation

sending anything but the correct args ("on", "off", or "toggle") to the ppDOUT node will crash the underlying python process and leave the whole plate stack unusable with no way to recover without restarting the nodered process.  Also, the correct args need to be documented in the Node Help section.

documentation improved somewhat in c6ba76bfd4b60e1672cd2def5581e8bf06994221


Fixed issue #616

The variable was arriving at compactFakeFields as null, so it won't be treated as a fake field, backpack would try to store it on its own column.
By replacing isset by array_key_exists, the key exists as null, so it's treated as a fake field.

I wonder if this "fix" will suddenly break any code that relies on the bug?

@lloy0076 I don't believe this fix will break any previous code because the fields, while not null, were being stored in the fake columns (as expected). If the fields were null, this error would happen. Probably, to avoid this error, everyone was adding validation rules to the request, in my case I wanted the field to be nullable.

This is a great fix, thank you @promatik !

Merged it into DEV, will be available to everyone shortly.


No sound output when eqmac is enabled

Describe the bug
there is no audio playback when eqmac is enabled it was fine just 2 days before and driver device swithes tried uninstalling and reinstalling the driver more than 10 times tried some old versions and still the same
Steps to Reproduce
Steps to reproduce the behavior
just install the driver restart and enable eqmac no sound output it was fine before but suddenly it got broken
Setup information:
Audio device used for playback: [14-inch MacBook pro built-in speakers]
Audio transmission interface: [built in]
macOS Version: [e.g. 14.1]
eqMac Version [app v1.8.0 driver v2.5.0]
eqMac UI Version [5.0.2]

Me Too.
When I restart my Mac, the USB connected speaker I have is lost/forgotten by EQMac. I have to open EQ Mac and select the speaker again. Sound does come out of my Mac, but is sounds like crap under the desk :-)
M1 Mini, Ventura 13.6.1, Sanyun (Cheap Chinese) "Soundbar" connect via USB (Bluetooth is for my second work computer)

Is this still an issue in v1.8.7?

Yes, I have the same problem in v1.8.7 and Sonoma 14.5 (M2)


WidgetsFlutterBinding.ensureInitialized(); must be called inside zone

I had trouble getting errors reported. Synchronous errors where caught but not asynchronous ones. The problem was that WidgetsFlutterBinding.ensureInitialized() was called outside of the error catching zone.
// doesn't work
void main() async {
  WidgetsFlutterBinding.ensureInitialized();

  FlutterError.onError = (FlutterErrorDetails details) {
    Zone.current.handleUncaughtError(details.exception, details.stack);
  };

  await FlutterCrashlytics().initialize();

  runZoned<Future<Null>>(() async {
    runApp(MyApp());
  }, onError: (error, stackTrace) async {
    await FlutterCrashlytics().reportCrash(error, stackTrace, forceCrash: false);
  });
}

Moving WidgetsFlutterBinding.ensureInitialized() inside runZoned fixes it and now reports all errors.
// works
void main() async {
  FlutterError.onError = (FlutterErrorDetails details) {
    Zone.current.handleUncaughtError(details.exception, details.stack);
  };

  runZoned<Future<Null>>(() async {
    WidgetsFlutterBinding.ensureInitialized();
    await FlutterCrashlytics().initialize();
    runApp(MyApp());
  }, onError: (error, stackTrace) async {
    await FlutterCrashlytics().reportCrash(error, stackTrace, forceCrash: false);
  });
}

I think the Readme should get an update.

Hey @passsy thanks for the report, look super weird !! because from the doc https://api.flutter.dev/flutter/widgets/WidgetsFlutterBinding/ensureInitialized.html once it's called it's done, so it shouldn't mind having it outside the zone.
When I have some time I'll update the readme, keep this one opened until it's done :)

Also can see  https://docs.flutter.dev/testing/errors#errors-not-caught-by-flutter.


Allow multiple Role mentions

[x] Implement Delete confirmation
[ ] Implement Multiple Role Mentions

Debating to only allow one role ping for when a /monitor role is setup.
The only issue would be if they are a streamer on a platform that isn't supported yet, multiple roles still may be desired to mention.
Along that same train of thought, it could be possible people want to monitor multiple roles too 🤔
I think this is a good first start of only allowing multiple role mentions if they are a supported service.
Current limit of roles that can be mentioned is 5, as that seems like more than enough, but we'll see and can be increased later if needed.


enable RDP shadowing

Enable Remote Desktop shadowing. This allows a user to "shadow" an active session
🗣 Description
Requirements to shadow an active session:

Windows based host machine with Powershell version 5.0 or greater
To allow incoming Remote Desktop connections, enable the following ports

3389/RDP

To allow incoming shadow connections, enable the following ports

139/TCP
445/TCP

Steps to shadow an active session:

You'll need the active user's session id to be able to shadow their session. The active user will need to

run query session in powershell
retrieve the ID for the session in the Active state

To shadow from a host Windows machine, run the following command in powershell:
mstsc /shadow:<session-id> /v:<ip-address> /control /noConsentPrompt /prompt
When prompted, enter your username and password for an Administrator account.

💭 Motivation and context
To enable shadowing of an active user.
This is a project requirement.
🧪 Testing

Successfully tested enable RDP shadowing locally on Windows Server 2022 virtual machine.
✅ Pre-approval checklist

[x] This PR has an informative and human-readable title.
[x] Changes are limited to a single goal - eschew scope creep!
[x] All future TODOs are captured in issues, which are referenced
in code comments.
[x] All relevant type-of-change labels have been added.
[x] I have read the CONTRIBUTING document.
[x] These code changes follow cisagov code standards.
[x] All relevant repo and/or project documentation has been updated
to reflect the changes in this PR.
[x] Tests have been added and/or modified to cover the changes in this PR.
[x] All new and existing tests pass.

Hi @dav3r @mcdonnnj what is the status of this PR? I wanted to update Chelsee on whether this will be merged soon. Thanks!

Hi @dav3r @mcdonnnj what is the status of this PR? I wanted to update Chelsee on whether this will be merged soon. Thanks!

@itsmostafa I know for my approval at least this PR requires testing to verify functionality.

Hi @dav3r @mcdonnnj what is the status of this PR? I wanted to update Chelsee on whether this will be merged soon. Thanks!

@itsmostafa I know for my approval at least this PR requires testing to verify functionality.

@mcdonnnj What testing are you referring to specifically?  The PR description states that this change was already tested, though it does not go into any detail about how that testing was performed.

Hi @dav3r @mcdonnnj what is the status of this PR? I wanted to update Chelsee on whether this will be merged soon. Thanks!

@itsmostafa I know for my approval at least this PR requires testing to verify functionality.

@mcdonnnj What testing are you referring to specifically? The PR description states that this change was already tested, though it does not go into any detail about how that testing was performed.

Was the test that the scripted changes worked or that RDP shadowing was enabled and worked? Semi-related to this but before this is really ready to ship (as far as project management is concerned) we have to test that it works from a Guacamole instance.

Hi @dav3r @mcdonnnj what is the status of this PR? I wanted to update Chelsee on whether this will be merged soon. Thanks!

@itsmostafa I know for my approval at least this PR requires testing to verify functionality.

@mcdonnnj What testing are you referring to specifically? The PR description states that this change was already tested, though it does not go into any detail about how that testing was performed.

Was the test that the scripted changes worked or that RDP shadowing was enabled and worked? Semi-related to this but before this is really ready to ship (as far as project management is concerned) we have to test that it works from a Guacamole instance.

Hi @mcdonnnj any updates on tests needed to be done to get this work approved? Thanks!

Hi @mcdonnnj any updates on additional tests needed to be done to get this work approved? Thanks!

@itsmostafa We want to hear from you about what testing your team previously did for this PR.  The PR description just says "Tested locally on Windows Server 2022 virtual machine", but that doesn't tell us anything particularly useful.  Please answer @mcdonnnj's question and provide any other details about the testing that was already done:

Was the test that the scripted changes worked or that RDP shadowing was enabled and worked? Semi-related to this but before this is really ready to ship (as far as project management is concerned) we have to test that it works from a Guacamole instance.

Hi @mcdonnnj any updates on additional tests needed to be done to get this work approved? Thanks!

@itsmostafa We want to hear from you about what testing your team previously did for this PR. The PR description just says "Tested locally on Windows Server 2022 virtual machine", but that doesn't tell us anything particularly useful. Please answer @mcdonnnj's question and provide any other details about the testing that was already done:

Was the test that the scripted changes worked or that RDP shadowing was enabled and worked? Semi-related to this but before this is really ready to ship (as far as project management is concerned) we have to test that it works from a Guacamole instance.

@dav3r unfortunately the person who worked on this PR is no longer with us so I'm not sure how testing was done locally for this. All I remember is that they did setup a local testing environment to be able to successfully run a virtual machine and tested 2 users connecting simultaneously with RDP. I don't believe this work has been tested with guacamole.

@itsmostafa Given the amount of time that has passed and the fact that you haven't done the testing yourself, I think it would be prudent for you to confirm everything here by building a fresh AMI and verifying that RDP shadowing is indeed functioning as intended (multiple users are able to connect at the same time on the same desktop).
After you have confirmed that, we can get together and discuss what is needed for the Guacamole connectivity.

@itsmostafa - don't forget to finalize the version before you merge.  (I'm sure you remembered, but since it isn't in the checklist above I figured I'd put a reminder here.)


fix(basti-cdk): Add required IAM permission

During more testing with the rest of my team I found that I forgot to add the permission that allows arn:aws:ssm:*:*:document/AWS-StartPortForwardingSessionToRemoteHost. This wasn't an issue for the initial roles I tested it with because they were granted this permissions by some other policy.

I just noticed this when was testing basti-cdk with the test CDK app: https://github.com/BohdanPetryshyn/basti/pull/55/files#diff-b5a46dba7e3da24b7e9a6416e5dd8cc03c8ca8399d5ac09dc942d8aa71faa1fbR175

But I haven't fixed it yet, just left a FIXME there. This PR definitely makes sense and has to be merged

@bobveringa Could you please implement the policies the same way as described here? Just in case.

@BohdanPetryshyn With this PR they should be the same right?

@bobveringa I can no longer see the changed files, but I remember that the SSM Document resource was added to EC2 and SSM actions while the README only adds the resource to the ssm:StartSession action


fix compatibility with with python 3, dos2unix sources

When installed as a system module you get the following when trying to import with py3:
Traceback (most recent call last):
  File "/home/melvin/dev/template/c/build/doc/sphinx/sphinx_multibuild_runner.py", line 3, in <module>
    from sphinx_multibuild import SphinxMultiBuilder
  File "/usr/lib/python3.6/site-packages/sphinx_multibuild/__init__.py", line 3, in <module>
    from sphinx_multibuild import SphinxMultiBuilder
ImportError: cannot import name 'SphinxMultiBuilder'

I looked at how other projects fixed this with py3 and did the same here so it should also work with py2.
Also ran dos2unix over the sources, if that is not desirable feel free to discard that commit.

Why does it do that? I can't find it online and didn't have the issue myself.


[lab][LoadingButton] Prevent React crash with Google Translate

Resolves https://github.com/mui/material-ui/issues/27853. Based on a previous attempt https://github.com/mui/material-ui/pull/35198.

Original PR description:
Use case summary:
Using the LoadingButton while have Google translation (chrome feature) active on your site.
Problem: Google modifies the button contents and React can't figure out its bindings anymore. Causes crash 💥
How to reproduce:
https://codesandbox.io/s/dry-water-eig2e7?file=/demo.tsx
Steps:

Open sandbox in external browser
Use google chrome's translate feature (see screenshot)
Click the loading button
Notice crash 💥

Additional description:
I introduced two changes from the original PR:

Use a <span> instead of a <div> to wrap children.
Remove display: contents.

Regarding number 2, display: contents suffered from deep accessibility issues, the most important one causing elements with the property applied to be removed from the accessibility tree. Most of these issues have been solved over the years, but it's still unclear if it's 100% reliable, especially on Safari. I'm wary of using this property if we're not 100% sure about it'll have the expected behavior. Let me know your thoughts. Some literature about the topic:

https://adrianroselli.com/2018/05/display-contents-is-not-a-css-reset.html
https://adrianroselli.com/2022/07/its-mid-2022-and-browsers-mostly-safari-still-break-accessibility-via-display-properties.html
https://hidde.blog/more-accessible-markup-with-display-contents/

Closing this to continue in the original PR.


Improve DB tests to use assert or similar

Fixes #292

We can ignore the pyflakes error for now, it is fixed in the next PR that will come tomorrow.


[Android] [Backgrounding & Workers] WorkManager and Context

Hello.
I looked at the implementation of WorkManager and something confused me.
We pass code to WorkManager directly, but usually DI is used for this. Won't your implementation leak memory?
For example, if I have a dependency that uses Application Context, and WorkManager lives longer than Application and can run for 10 minutes after Application is closed - doesn't this indicate that such interaction will lead to memory leak in your implementation?
I first saw that executable code was passed to WorkManager using lambda. I have never seen such implementations.
KmpBackgrounding.createAndStartWorker(null){
    // my action to run in the background
    // this action will run even if the device is locked
}

There's a new api available if you need a background service that will immediately close after the app closes.
This avoids having to maintain a reference to ApplicationContext.
https://thearchitect123.github.io/ArtifactsDocProduction/develop/kotlin/multiplatform/kmpessentials/modules/backgrounding#run-your-action-inside-a-foreground-service-for-long-running-background-processes
KmpBackgrounding.createAndStartForegroundWorker
This will generate a foreground service with a configurable silent notification. This service runs indefinitely and is attached to the app. Once you close the app the service is immediately closed.
Worker Managers is more suitable for services you need to run beyond the application.
Though I need to see how I can still launch worker managers without an active application context. Maybe via a broadcast receiver instead.


Consider more from/tryfrom conversions for Duration and Timestamp

We may want to consider conversions from and to the chrono, maybe direct mappings to and from tokio::time, and (as suggested by @codyoss) to and from strings.

maybe direct mappings to and from tokio::time

@coryan Adding TryFrom conversion between tokio::time and Duration results in a conflict with this function with the following error message: conflicting implementations of trait TryFrom<std::time::Duration> for type duration::Duration.
Since tokio::time::Duration is re-export of std::time::Duration, I wonder if having a separate conversion might be redundant?

Since tokio::time::Duration is re-export of std::time::Duration, I wonder if having a separate conversion might be redundant?

Agree.

Thanks for confirming! Closing this issue for now given the implementation of from/tryfrom conversions for chrono and String representations in https://github.com/googleapis/google-cloud-rust/pull/542 and https://github.com/googleapis/google-cloud-rust/pull/550.

The bug says "Duration and Timestamp".  We do not have anything for chrono::DateTime do we?

Ah my bad, missed this. Let me put up a PR for the Timestamp conversions as well.


refactor: upgrade node-pty to 1.0.0

Types

[x] 🪚 Refactors

Background or solution

🤖[deprecated] Generated by Copilot at 7bcd5f7

Update node-pty dependency to 1.0.0 in packages/terminal-next/package.json and tools/electron/package.json (link, link)
Remove $on method from IPtyProxyRPCService and IPtyServiceManager interfaces and their implementations (link, link, link, link)
Add $clear method to IPtyProxyRPCService and IPtyServiceManager interfaces and their implementations (link, link, link)
Remove unused os module import from packages/terminal-next/src/node/pty.proxy.ts (link)
Add empty line to packages/terminal-next/src/node/pty.manager.ts for readability (link)

Upgrade to stable version node-pty v1.0.0
Changelog

🤖[deprecated] Generated by Copilot at 7bcd5f7
This pull request updates the node-pty dependency to the latest stable version and refactors the pseudo terminal services in packages/terminal-next to use more specific and clear methods for inter-process communication and terminal functionality. It also removes some unused or redundant code from pty.proxy.ts.

/next


Doc db migration guide

Description
For upgrade from 1.7 to 1.7 Patch 1 DB migration instructions need to be included.This can be provided in form of Discourse post and linked in upgrade guide or as a part of upgrade guide. Instructions should include doing back up, unrelate, import back up into mysql, relate.
The instructions in this document can be tested as shell commands and can be automatically tested, if required. A separate work item is required for this.
NOTE
CKF 1.8 does NOT work with MariaDB. This means clients need to:

First migrate the DB, to MySQL
Then do the CKF 1.7 to 1.8 upgrade

I wonder what is the advantage of using a notebook instead of a regular markdown, since we are only executing shell commands.

If we are using notebook, we can load it as JSON into Python script and run test on it. Basically, we have a testable document. Example of test
The idea is to covert this notebook to markdown (which is very easy to do) after we approve this PR and it will serve as a nice document  in our repo. Example of markdown generated from corresponding notebook

Overall feedback - it reads more like a script than a doc. Since it's a Jupyter notebook, can we put the comments in as cells and split up the code into multiple cells?

WeComments could be replaced with small paragraphs for giving context, and/or setting the expectation of the command to be run, then each command or related command could be one cell.

Updated with comments. Also added markdown version for easy read.

There is a potential issue when primary key does not exist in the table.

@DnPlas Ready for final review. When Data Platform team finishes their migration guide, we should link it with ours.


Suggestion for MKSwitch

Checking for props disabled before trigger onPress, onPressIn and onPressOut to prevent switch component from switching

Already mentioned here https://github.com/xinthink/react-native-material-kit/pull/199#issuecomment-311321027


Sentinl attempts to modify its own code

On startup, sentinl attempts to modify public/app.js, which is a file under the code tree. This is bad practice, as it prevents proper privilege separation.
If code needs to be modified at runtime, the changes should be performed on a copy stored outside the code tree, e.g. in ../../optimize.
Jul 24 08:57:25 xxxxxxxx.siren.solutions investigate[28962]: {"type":"error","@timestamp":"2018-07-24T08:57:25Z","tags":["fatal"],"pid":28962,"level":"fatal","error":{"message":"put libs into app.js: EACCES: permission denied, open '/opt/test101.xxxxxxxx/siren-investigate-10.1.0-SNAPSHOT-linux-x86_64/siren_plugins/sentinl/public/app.js'","name":"Error","stack":"Error: put libs into app.js: EACCES: permission denied, open '/opt/test101.xxxxxxxx/siren-investigate-10.1.0-SNAPSHOT-linux-x86_64/siren_plugins/sentinl/public/app.js'\n    at exports.default (/opt/test101.xxxxxxxx/siren-investigate-10.1.0-SNAPSHOT-linux-x86_64/siren_plugins/sentinl/index.js:58:11)\n    at /opt/test101.xxxxxxxx/siren-investigate-10.1.0-SNAPSHOT-linux-x86_64/src/server/plugins/plugin_collection.js:79:45\n    at next (native)\n    at step (/opt/test101.xxxxxxxx/siren-investigate-10.1.0-SNAPSHOT-linux-x86_64/src/server/plugins/plugin_collection.js:49:191)\n    at /opt/test101.xxxxxxxx/siren-investigate-10.1.0-SNAPSHOT-linux-x86_64/src/server/plugins/plugin_collection.js:49:437\n    at /opt/test101.xxxxxxxx/siren-investigate-10.1.0-SNAPSHOT-linux-x86_64/src/server/plugins/plugin_collection.js:49:99\n    at Plugins.new (/opt/test101.xxxxxxxx/siren-investigate-10.1.0-SNAPSHOT-linux-x86_64/src/server/plugins/plugin_collection.js:115:7)\n    at KbnServer.<anonymous> (/opt/test101.xxxxxxxx/siren-investigate-10.1.0-SNAPSHOT-linux-x86_64/src/server/plugins/scan.js:94:26)\n    at next (native)\n    at step (/opt/test101.xxxxxxxx/siren-investigate-10.1.0-SNAPSHOT-linux-x86_64/src/server/plugins/scan.js:19:191)\n    at /opt/test101.xxxxxxxx/siren-investigate-10.1.0-SNAPSHOT-linux-x86_64/src/server/plugins/scan.js:19:361"},"message":"put libs into app.js: EACCES: permission denied, open '/opt/test101.xxxxxxxx/siren-investigate-10.1.0-SNAPSHOT-linux-x86_64/siren_plugins/sentinl/public/app.js'"}
Jul 24 08:57:25 xxxxxxxx.siren.solutions investigate[28962]: FATAL Error: put libs into app.js: EACCES: permission denied, open '/opt/test101.xxxxxxxx/siren-investigate-10.1.0-SNAPSHOT-linux-x86_64/siren_plugins/sentinl/public/app.js'
Jul 24 08:57:25 xxxxxxxx.siren.solutions investigate[28962]:     at exports.default (/opt/test101.xxxxxxxx/siren-investigate-10.1.0-SNAPSHOT-linux-x86_64/siren_plugins/sentinl/index.js:58:11)
Jul 24 08:57:25 xxxxxxxx.siren.solutions investigate[28962]:     at /opt/test101.xxxxxxxx/siren-investigate-10.1.0-SNAPSHOT-linux-x86_64/src/server/plugins/plugin_collection.js:79:45
Jul 24 08:57:25 xxxxxxxx.siren.solutions investigate[28962]:     at next (native)
Jul 24 08:57:25 xxxxxxxx.siren.solutions investigate[28962]:     at step (/opt/test101.xxxxxxxx/siren-investigate-10.1.0-SNAPSHOT-linux-x86_64/src/server/plugins/plugin_collection.js:49:191)
Jul 24 08:57:25 xxxxxxxx.siren.solutions investigate[28962]:     at /opt/test101.xxxxxxxx/siren-investigate-10.1.0-SNAPSHOT-linux-x86_64/src/server/plugins/plugin_collection.js:49:437
Jul 24 08:57:25 xxxxxxxx.siren.solutions investigate[28962]:     at /opt/test101.xxxxxxxx/siren-investigate-10.1.0-SNAPSHOT-linux-x86_64/src/server/plugins/plugin_collection.js:49:99
Jul 24 08:57:25 xxxxxxxx.siren.solutions investigate[28962]:     at Plugins.new (/opt/test101.xxxxxxxx/siren-investigate-10.1.0-SNAPSHOT-linux-x86_64/src/server/plugins/plugin_collection.js:115:7)
Jul 24 08:57:25 xxxxxxxx.siren.solutions investigate[28962]:     at KbnServer.<anonymous> (/opt/test101.xxxxxxxx/siren-investigate-10.1.0-SNAPSHOT-linux-x86_64/src/server/plugins/scan.js:94:26)
Jul 24 08:57:25 xxxxxxxx.siren.solutions investigate[28962]:     at next (native)
Jul 24 08:57:25 xxxxxxxx.siren.solutions investigate[28962]:     at step (/opt/test101.xxxxxxxx/siren-investigate-10.1.0-SNAPSHOT-linux-x86_64/src/server/plugins/scan.js:19:191)
Jul 24 08:57:25 xxxxxxxx.siren.solutions investigate[28962]:     at /opt/test101.xxxxxxxx/siren-investigate-10.1.0-SNAPSHOT-linux-x86_64/src/server/plugins/scan.js:19:361

Two more offending files:
Jul 24 09:16:04 xxxxxxxx.siren.solutions investigate[30856]: FATAL { Error: EPERM: operation not permitted, chmod '/opt/test101.kibisiem/siren-investigate-10.1.0-SNAPSHOT-linux-x86_64/siren_plugins/sentinl/node_modules/phantomjs-prebuilt/bin/phantomjs'
Jul 24 09:17:42 xxxxxxxx.siren.solutions investigate[32296]: [sentinl] fail to make report engine executable: EPERM: operation not permitted, chmod '/opt/test101.xxxxxxxx/siren-investigate-10.1.0-SNAPSHOT-linux-x86_64/siren_plugins/sentinl/node_modules/puppeteer/.local-chromium/linux-564778/chrome-linux/chrome'!

@andrewgdotcom
Siren creates issues here https://github.com/sirensolutions/sentinl-private
This app.js change is needed to import correct SavedObjectsAPI objects:
if Siren:
  import Siren SavedObjectsAPI
else:
  import Kibana SavedObjectsAPI

I remember I tried to require modules conditionally but it didn't work. I'll try again but now we have more urgent issues.

Issue moved to sirensolutions/sentinl-private #679 via ZenHub


Near integration

Thanks for contribution and please notice below requirement.
The signing script is demanded for validating sensitive fields and encoding signing data in the same time. That means the showAddress() and showAmount() commands display critical data for validation from the arguments which should strictly be used in the data encoding.


Login error: cannot find HTML form

Hi,
I installed v0.1.8 from a cloned repo (seems 0.1.8 is not available via npm) and I'm getting the problem mentioned in issue #17.  First submission works fine.  It only happens on  subsequent submissions.  The only way around it that I've found is logging out and back in before each submission.
Thanks.

fixed in 0.1.9


wrong python version on MNE website

Here: https://mne.tools/dev/install/index.html
It says that MNE-Python requires 3.6 and higher, however if you try to install on 3.6 it fails. I think this needs to be updated along with any other places that might have been left.

PR welcome.
$ git grep " 3\.6 "
README.rst:61:- MNE-Python 0.21 requires Python 3.6 or higher
doc/install/contributing.rst:177:version 3.6 or higher) and also switch between the stable and development
doc/install/index.rst:4:MNE-Python requires Python version 3.6 or higher.
doc/install/mne_python.rst:16:Starting with version 0.21, MNE-Python only supports Python version 3.6 or


Add rat checks to travis-ci build

Where is .ratignore? I don't see it.

@PivotalSarge .ratignore is in the base dir of geode-native

Ah. find does not behave like I think it does with respect to finding dot files in the current directory.

I quoted the target, suspecting find would not like it otherwise...


Async query requests

Hi, are there async query requests in plans?

Please see https://github.com/mausch/SolrNet/issues/91