az vm create failes with specific image version

This is autogenerated. Please review and update as needed.
Describe the bug
I can not create a vm based on a specific image version from an shared image gallery. Creating a vm based on the 'latest' version succeeded (although it is exactly this version).
Please note that the resource group in error message is the resource group i want to create the vm in. its not the rpg of the sig.
Command Name
az vm create
Errors:
(ResourceNotFound) The Resource 'Microsoft.Compute/galleries/kvscblsig01/images/BuildAgent' under resource group 'MyResourceGroup3' was not found. For more details please go to https://aka.ms/ARMResourceNotFoundFix
Code: ResourceNotFound
Message: The Resource 'Microsoft.Compute/galleries/kvscblsig01/images/BuildAgent' under resource group 'MyResourceGroup3' was not found. For more details please go to https://aka.ms/ARMResourceNotFoundFix

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

check available versions: az sig image-version list -g KvsCblVmssAgent -r kvscblsig01 -i BuildAgent -o json

[
  {
    "id": "/subscriptions/***/resourceGroups/KvsCblVmssAgent/providers/Microsoft.Compute/galleries/kvscblsig01/images/BuildAgent/versions/1.23017.58252",
    "location": "westeurope",
    "name": "1.23017.58252",
    "provisioningState": "Succeeded",
    "publishingProfile": {
      "endOfLifeDate": null,
      "excludeFromLatest": false,
      "publishedDate": "2023-01-17T08:57:45.134751+00:00",
      "replicaCount": 1,
      "replicationMode": null,
      "storageAccountType": "Standard_LRS",
      "targetExtendedLocations": null,
      "targetRegions": [
        {
          "encryption": null,
          "excludeFromLatest": null,
          "name": "West Europe",
          "regionalReplicaCount": 1,
          "storageAccountType": "Standard_LRS"
        }
      ]
    },
    "replicationStatus": null,
    "resourceGroup": "KvsCblVmssAgent",
    "safetyProfile": {
      "allowDeletionOfReplicatedLocations": true,
      "policyViolations": null,
      "reportedForPolicyViolation": false
    },
    "storageProfile": {
      "dataDiskImages": null,
      "osDiskImage": {
        "hostCaching": "ReadWrite",
        "sizeInGb": 250,
        "source": {
          "id": null,
          "storageAccountId": null,
          "uri": null
        }
      },
      "source": {
        "communityGalleryImageId": null,
        "id": "/subscriptions/***/resourceGroups/KvsCblVmssAgent/providers/Microsoft.Compute/images/BuildAgent",
        "resourceGroup": "KvsCblVmssAgent"
      }
    },
    "tags": {},
    "type": "Microsoft.Compute/galleries/images/versions"
  }
]

az vm create --resource-group MyResourceGroup3 -n MyVm --image /subscriptions/***/resourceGroups/KvsCblVmssAgent/providers/Microsoft.Compute/galleries/kvscblsig01/images/BuildAgent --public-ip-sku {} --admin-username {} --admin-password {} <--this one succeed
az vm create --resource-group MyResourceGroup3  -n MyVm2  --image /subscriptions/***/resourceGroups/KvsCblVmssAgent/providers/Microsoft.Compute/galleries/kvscblsig01/images/BuildAgent/versions/1.23017.58252 --public-ip-sku {} --admin-username {} --admin-password {} <--this one failes

Expected Behavior
I would expect that i can create a vm based on a specific image version as documented.
Environment Summary
Linux-5.4.0-1100-azure-x86_64-with-glibc2.35 (Cloud Shell), CBL-Mariner/Linux
Python 3.9.14
Installer: RPM

azure-cli 2.43.0 *

Extensions:
ai-examples 0.2.5
ml 2.11.0
ssh 1.1.3

Dependencies:
msal 1.20.0
azure-mgmt-resource 21.1.0b1

Additional Context

@zhoxing-ms for awareness

Met the exact same issue in az vmss create and fixed by upgrading az version from 2.43 to 2.44. It's the same as #24896.


Application layer design

Hi @kgrzybek , first of all, thanks for your work!
I have been going thru the codebase and I have noticed an approach which slightly differs from my own, thus I wanted to ask some questions to better understand the drivers & reasoning behind it.
In the application layer, there is a lot of dependencies, which I usually delegate to infrastructure layer.
For example - event bus related stuff, DI modules, logging, schedulers - basically everything that is not Command or CommandHandler. Sometimes it happens, that in CommandHandler you need something more. In that case, I usually go for the interface in the application layer implemented in the infrastructure layer.
Speaking of modules, I noticed that in each module there are usually couple of autofac modules, e.g. MediatorModule, QuartzModule, DataAccessModule. What is the reason of that?
Each .csproj has a reference to Microsoft.NETCore.App - would you consider switching that to .netstandard? I reference the platform at the top-level such as API (CompanyName.MyMeetings.API in this case). Benefit of that is that it allows my to easily switch the platform and has much less coupling for my application.
I want to make it clear that I'm not trying to say the only valid way to do something is "my & only righteous way". I'm more of looking for exchange of thoughts and maybe an improvement in common understanding.
If you think that something can be extracted to separate issue, please do so, I didn't want to spam you 😄

Hi @michal880

In the application layer, there is a lot of dependencies, which I usually delegate to infrastructure layer.
For example - event bus related stuff, DI modules, logging, schedulers - basically everything that is not Command or CommandHandler. Sometimes it happens, that in CommandHandler you need something more. In that case, I usually go for the interface in the application layer implemented in the infrastructure layer.

This is a good point. It was a decision because I treated the Application layer as an entry gate to module and application layer (like module host), so API could reference only this project. Recently, I changed my mind and decided to move the whole configuration to Infrastructure. The advantage is that the whole module architecture is cleaner. The disadvantage is that API needs references App and Infra now.

Speaking of modules, I noticed that in each module there are usually couple of autofac modules, e.g. MediatorModule, QuartzModule, DataAccessModule. What is the reason of that?

I like more granular Autofac modules, but I think is the matter of choice.

Each .csproj has a reference to Microsoft.NETCore.App - would you consider switching that to .netstandard? I reference the platform at the top-level such as API (CompanyName.MyMeetings.API in this case). The benefit of that is that it allows me to easily switch the platform and has much less coupling for my application.

No, I have not considered it. I plan to migrate to .NET Core 3.1 first. After that I don't know if it would be possible.


Sidebar Search drop-down not closing on click outside

Hi
The side-menu search bar in its current form is a bit hard to close, the default close x in the search bar doesn't really clear the search.
Currently, you'll have to manually backspace or clear the search for the dropdown to disappear, which is less intuitive. Closing the dropdown on click outside or having a clear button in would greatly improve user experience.
Thx
https://github.com/unfoldadmin/django-unfold/assets/64060109/bd00661a-88a9-4719-b18b-cb7d5d7873a1

Fixed #548


Dialogue Update for 40-114-123-34-119-366

Credit to funnyboy044, @CONKINGTON, and @f4nimator  for writing #40 #114 #123 #34 #119 #366

Ignore this and do 371 instead


"GLXBadFBConfig"-Error on Startup - ZorinOS16 - Intel Core i7-3740QM

Problem/Bug:
F360 does not start on my system, I don't see any GUI and the console spits out following errors:

The error happens on both the Vulkan- and OpenGL-Variant.
My System:
System: Dell Latitude E6430
OS: ZorinOS16 (64-Bit)
CPU: Intel® Core™ i7-3740QM CPU @ 2.70GHz × 8
GPU: Intel® HD Graphics 4000 (IVB GT2)
RAM: 8GB

Hey @LukasKraehling 👋
Can you check in these folders (Example):

$HOME/.wineprefixes/fusion360/drive_c/users/$USER/Application Data/Autodesk/Neutron Platform/Options
$HOME/.wineprefixes/fusion360/drive_c/users/$USER/AppData/Roaming/Autodesk/Neutron Platform/Options

... the NMachineSpecificOptions.xml files if they are correctly configured! :+1:
DXVK:

openGL:

You have a Intel GPU and so you must have the first configuration file. 🙂

![image](https://user-images.githubusercontent.com/26366928/140402814-7efeaeb3-7f5a-47ee-98a3-fa6a9abc95ec.png
Did not help, I tried both APIs before. I copied the DXVK config into the file, but no change.

Oh okay, I see thta you have some problems with the GLXBadFBConfig! 😉
Please, check this post here: https://forums.linuxmint.com/viewtopic.php?t=356491
Because there it's described so that you must change or overwrite the MESA_GL_VERSION.

For example:

So, I really tried to get at least 4.4 running, but it seems like I can only go up to 4.2...
I think it could be related to Mesa 21.0.3 running on my system.
Any Ideas ?

Okay. Can you switch to the newest version (Mesa 21.2.5)?

Okay. Can you switch to the newest version (Mesa 21.2.5)?

Great ! I was able to upgrade to Mesa 21.2.5 and now F360 starts successfully ! I am still not able to push the MESA_GL_VERSION_OVERRIDE further than 4.2, but I don't need to anymore, so it's all good. :) Thx for the great support !


Feature request: kirbyup --mode CLI option

Vite uses --mode production to set mode. kirbyup --mode silently fails for me.
I am also not sure how to get to the mode from kirbyup.config.js because import.meta.env is undefined.
I really just needed sourcemaps for development so i did it the old lame way
export default defineConfig({
  extendViteConfig: {
    build: {
      sourcemap: process.env.NODE_ENV == 'development' ? 'inline' : false
    }
  }
})

and using "NODE_ENV=development kirbyup src/panel/index.js --watch"

Sorry this is my unexperience with vite i mostly use esbuild but the vue situation is better with vite/kirbyup (kirby panel plugins).
There must be some way how to get the mode in the config i just don't know how.

Ha! For some reason the inline sourcemaps don't work properly anyway. I am not sure why but both Chrome and FF just error that they can't understand them. From what i found its some deeper issue with vite and browsers so probably not fixable by me. Hopefuly one day it starts to work :))
Cheers thanks for this @johannschopplich


Roadmap

It would be nice to have a roadmap for the future development of rust-analyzer. I am sure @matklad has some kind of vision in his head, so it would be nice to put that in a document so new contributors (myself included) have an idea of where the project is headed.
Right now it is clear from the readme that rust-analyzer wants to be a Rust compiler frontend enabling excellent IDE support. However, it is not that clear how we will get there. Which features are we missing? Can we subdivide them in tasks and create tracking issues?
Example
One of the most useful features (to me) would be autocomplete, but there are no issues about it. We could therefore create issues about implementing:

Path resolution (i.e. go from a path to the place where the name is defined)
Type checking

From these two, it seems that path resolution is the most developed at the moment, though I don't know if it is fully implemented. Are there cases in which we cannot obtain the definition from the path?
Regarding type checking, we need to be able to:

Get the type of the expression under the cursor
List the available functions for the type (which means knowing which traits are implemented by it)

Maybe we could use Chalk for the trait resolution part, though as far as I know this is an experimental library. The same goes for Polonius, which we could use when implementing the ownership system. This kind of discussion could take place in the respective issues, once we create them.
Steps to take
It would be nice to talk about the future of rust-analysis and maybe even set goals for 2019. We could do this by commenting on this issue, chatting on Discord, or through a video call. As a result of this process, we could create a bunch of issues and tracking issues for the features we want to implement.
I think the project has a huge potential and I guess many other people share this view. For those of us that would like to contribute on a regular basis, it would be useful to know the desired direction and priorities. That is why it seems worthwhile to take the time for this.

It would be nice to have a roadmap for the future development of rust-analyzer. I am sure @matklad has some kind of vision in his head, so it would be nice to put that in a document so new contributors (myself included) have an idea of where the project is headed.

Agree! The reason why I haven't done that yet is semi-arbitrary: I expected to draw a roadmap after https://internals.rust-lang.org/t/next-steps-for-rls-rustc-and-ide-support/8428 comes to some sort of the conclusion, but that never happened. I've chatted with RLS/compiler folks about how should we plan the IDE work for rust, and we've came to the conclusion that we should table this discussion at least until the 2018 edition is cut. More probably though is that such coordination will happen only in Februrary, during all hands. That all sort-of freeze my roadmap-drawing plans :(
I think we should define short-term roadmap until the February. I'll try to start the discussion about this tomorrow.

Closed in #203


Unable to set device room

Hi,
I ended up here after homebridge-lg-thinq-ac failed to work with 1 of my airconditioners (odd, since the LW1019IVSM AC apparently uses thinq1, while the same generation unit, but larger capacity, the LW1517IVSM, uses thinq2).
All 3 airconditioners I have are detected and show up in homekit, however they all show up listed in the room where my homebridge is. Unlike all the accessories provided by other plugins, there is no "room" setting for these air conditioners within homekit to move them to the correct rooms.
It feels like a bug that there isn't a way to specify which room the thinq devices are in.

can you capture some screenshot in home app about this issue ?

Sure. Also, while testing this, I noticed that there was quite a delay between turning an air conditioner on in homekit and the air conditioner actually turning on. Maybe a 30 second delay. Is this plugin doing some 30 second update thing?
"Office Airconditioner" is connected using this plugin.

The "Livingroom Airconditioner" picture is using the lq-thinq-ac plugin.

damn, sorry for the size of those images.

Sure. Also, while testing this, I noticed that there was quite a delay between turning an air conditioner on in homekit and the air conditioner actually turning on. Maybe a 30 second delay. Is this plugin doing some 30 second update thing?

thing1 device is update every 60 second as default, you can setting refresh_interval in plugin config to change this value, but I think you shouldn't decrease it too low, 30 - 60 second is best practice or you can received a warning from LG about unusual request
thinq2 update in realtime via mqtt protocol (thinq1 do not support this)

"Office Airconditioner" is connected using this plugin.

look like this AC tile is single tile in group of AC services (fan, AC, light ...), you need click "Show as Separate Tile" before you can change room of this single tile
or you can change room in root accessory

The "Office Airconditioner" was the only tile added for that device, so I assumed it was the root, however clicking "show as seperate tiles" did make the room assignment setting appear (even though it didn't show any additional tiles) so thanks!
So the other plugin that only supports thinq2 does work with my office and livingroom air conditioners, just not the bedroom. So shouldn't the two thinq2 devices have ~instant control? Because they don't. Does checking the "enable thinq1 support" box make all devices use thinq1?

I just tried unchecking the thinq1 support option and that did result in the bedroom AC being removed as a device, but the other two ACs are still slow to respond. Is there some configuration I could add to make this plugin only expose the thinq1 bedroom AC?

I just tried unchecking the thinq1 support option and that did result in the bedroom AC being removed as a device, but the other two ACs are still slow to respond. Is there some configuration I could add to make this plugin only expose the thinq1 bedroom AC?

if you using homebridge-ui, you can go to plugin setting to remove unwanted device or following this https://github.com/nVuln/homebridge-lg-thinq/wiki/Device-Configuration to enable thinq1 device only

So the other plugin that only supports thinq2 does work with my office and livingroom air conditioners, just not the bedroom. So shouldn't the two thinq2 devices have ~instant control? Because they don't. Does checking the "enable thinq1 support" box make all devices use thinq1?

I'm not sure if the other plugin used mqtt protocol like this plugin
if you using this plugin to control thinq2 device, and it's still slow response, maybe the problem is your slow network, please turn on homebridge debug mode, you can see real-time device data in-out


Super learner

Addition of the following

[x] Super learner stacking algorithm for binary and continuous variables implemented as SuperLearner

[ ] EmpiricalMeanSL estimator that consists of the empirical mean in SciKit-Learn format

[x] StepWiseSL estimator that applies (either forward or backward) stepwise model selection via AIC values

All live in the new zepid.superlearner branch. Plan is to integrate and release with v0.9.0

Still need to add to docs before merging into v0.9.0 #143


--watch should run on change of every file in tree

Currently --watch just run itself after a change to a js in the current folder.
Why don't extend it to every file in the tree (excluding node_modules)?

I guess it could, but as a js testing framework it makes sense to me at least, though I suppose for some libs changing image fixtures or something would be nice. What's your use-case?

It's simple, running test manually disrupt my focus.
Maybe it's a rubyist thing, but I tend to write short and clearly separated
modules, thus leading to lots of files and tests, usually deep in a
directory tree.
When I change a file under lib, or even a test, I see in growl if
everything is good or not. It's much, much faster than switching back to
the shell to run the tests and check the output.
Really, it's a feature for the laziest developers :).
OT
As node caches the required files, I've seen you call delete require.cache[file]. However in this way you could not remove from the
cache the dependencies in the correct order, or could you? If you have file
A that depends on file B, you must reload B first, and then move to A.
I think it's better deleting all the file in the cache, and then requiring
them again.

it does watch every javascript file, but not images etc..

I've checked that, it doesn't work for me because I'm using coffeescript,
and the utils.files method doesn't use the global pattern, but only /.js$/.
Could you fix that?

oh yuck, yeah i'll fix it


HtmlColor validator

Eg. named colours
or hex, or rgb, or rgba.
I guess we have to use the american spelling for colour. :disappointed:

I would suggest using CSS3 spec colour names. They are also defined in SVG spec.
I also have got a couple of questions regarding this issue:

Should the validator only validate that a colour given is among the set of the named colours?
What formats exactly we should support?

This is what I've come up with:
from pydantic import BaseModel, HtmlColor

class Model(BaseModel):
    color: HtmlColor = None

# all these are valid colours, actually variant represent 'antiquewhite'
name_color = Model(color='antiquewhite')
name_color2 = Model(color='AntiqueWhite')  # case ignored
hex_color = Model(color='0xfaebd7')
hex_color2 = Model(color='#faebd7') # also hex
hex_color3 = Model(color='#FAEBD7') # letter's case ignored
rgb_color = Model(color=(250, 235, 215))
# we just ignore alpha-channel if first 3 ints match
rgba_color = Model(color=(250, 235, 215, 10))

Should we support RGB/RGBA as stings? Something else I'm missing?

all those cases look good a few more we should probably accept:

fff eg. three letter html colours
rgb(1,1,1) and rgba(1,1,1,0) should also work, shouldn't be too hard with a regex

It looks like you can also definite colours using hsl(...) and cmyk(...) but I really think that's too niche for now.
The other case is how does the parsed value m.color behave, eg. is it just a string or an rgb tuple?
I think best that we return an instance of HtmlColor which doesn't inherit from string, but where the __str__ method returns a valid html string.
Another question: should we always validate to the same thing or leave the output format as it came in? Eg. if someone enters rgb(0, 0, 0) should we return:

rgb(0, 0, 0)
#000 or #000000
or black
?

Genuinely not sure what's best here. I think we have to have:

original() which returns the original value passed to the model
as_hex()
as_rgba()
as_tuple() - should this be 3 or 4 values or always 4?
as_named_color()
and perhaps best() (better name needed) which tries named colour but falls back to hex if no name or rgba if there's an alpha channel
should __str__ be an alias of original() or best()?

Turns out this is much more complicated than I thought, but quite fun :-)

@samuelcolvin hsl(...) is easy to implement using colorsys from the standard library, though some conversion will be needed as colorsys gets rgb as all floats of range 0.0..1.0. colorsys also lacks  cmyk(..).
By the way, it seems that defining rgb/rgba as a tuple of all floats is quite common. So this probably should be supported too, e.g. rgb(0.1, 0.3, 0.2) and rgba(0.1, 0.3, 0.2, 0.1)
Another thing that I've just realised is that if we do all these fancy conversions, we have to take care of alpha composition. We cannot just drop alpha from rgba and match rgb against a set of allowed colours (except for the case where alpha = 1.0). There should be a conversion rgba->rgba done first (see this post for more details).

Another question: should we always validate to the same thing or leave the output format as it came in?

I would certainly expect the output format match the input's one. I think a user can add conversion to the needed format at a post validation step.

as_rgba()
What if as_rgba() always returns rgba (with alpha = 1.0 in rgb case). Then we also add as_rgb() method to only return rgb (there will be a conversion for rgba case here).

as_tuple()
May be also splitted as as_rgb_tuple() and as_rgba_tuple()?

as_named_color()
Return a lower cased name of the colour passed

best() [...]  tries named colour but falls back to hex if no name or rgba if there's an alpha channel
This brings us to the first question I've asked: if we only validate that a colour passed is in the set of predefined colours defined in CSS3/SVG specification? Or we just try to validate a colour returning it's predifined name if we can find it, otherwise we fall back to hex or rgba?

should str be an alias of original() or best()?
I woud go for an alias of original()

I think it's also worth taking a look at the webcolors package as well as maplotlib.color API

This brings us to the first question I've asked: if we only validate that a colour passed is in the set of predefined colours defined in CSS3/SVG specification?

Yes, we're checking it's in the list of predefined colours from css3.
We don't want to do any clever stuff with the alpha channel, if it's there (and not 1.0/255) the colour has to be defined as rgba(...), no hex, no names.
We can happily ignore cmyk, look at how github interprets hex, rgb, rgba and hsl but not cmyk.
as_rgb and as_hex should fail if there's an alpha channel, same as as_named_color should fail if there's no such named colour.

May be also splitted as as_rgb_tuple() and as_rgba_tuple()?

Let's just call it as_tuple and add a keyword argument alpha which can be include, exclude or auto, default to auto.

maybe we should call the field Color since it's not just html, but also css, svg and many other related technologies.

@samuelcolvin ok, now it's clear. Also agree with Color!
I would work on this issue if you don't mind

yes please.
For clarity I think Color should only need three slots:
class Color:
    __slots__ = '_rgba', '_original', '_color_match'

    def __init__(...):
        self._rgba: Tuple[int, int, int, Optional[int]] = ...
        self._original: str = ...
        self._color_match: Union[str, None, bool] = None # used to cache the named color or that there is none

Obviously do it how you think best, but I think the above makes sense as a starting point.


The directive doesn't interpolate in ng-transclude

In case I'd like to attach an id to the input filed using string interpolation, the directive stops responding, see the example below:
<input type="file"
               class="form-control" id="bg_image_{{btnCtrl.index}}"
               ngf-select="btnCtrl.uploadFiles($file, $invalidFiles)"
               accept="image/*" ngf-max-height="1000" ngf-max-size="1MB">

I assume that the digest cycle is not called at some point (as an example see this topic

@ostaplisovyj, try to use
ng-attr-id="bg_image_{{btnCtrl.index}}"

ng-attr-iddoesn't appear to be working, the 'Upload' button doesn't open the modal window

@ostaplisovyj can you create some example on jsfiddle or jsbin?

closing due to issue being no more valid


[FLINK-24139][table-planner] Push down more predicates through Join in stream mode

What is the purpose of the change
Enable JoinDependentConditionDerivationRule in stream mode.
Brief change log

add a new rule set in FlinkStreamRuleSets
add a new program in FlinkStreamProgram
add some test case in stream/table/JoinTest, stream/sqlJoinTest, stream/table/JoinItCase, stream/sql/JoinItCase

Verifying this change
Some test cases added in stream/table/JoinTest, stream/sqlJoinTest, stream/table/JoinItCase and stream/sql/JoinItCase can verify this change.
Does this pull request potentially affect one of the following parts:

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

Documentation

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

Hi, @zjuwangg
The main reason is that in FlinkBatchProgram, this iterator time is set with 5. In order to be consistent, i rewrite the number 5 here.
I tried to find why we need to set iterations here. Actually, I think this aims to pushdown the filter condition into the join condition and can continue optimizing the join condition several times.
For example, in table api, the api named 'join' and 'where' will create a join relNode with a true condition and a fliter above the join relNode. The real condition we need will be set in the filter relNode.  The optimized program will do JOIN_PREDICATE_REWRITE_RULES first, which will extract the join condition, and then do FILTER_PREPARE_RULES, which will push the filter condition into the join condition. However, if we don't set the iterator, JOIN_PREDICATE_REWRITE_RULES finds that the join condition is always True, and will do nothing, which is not in our expectation. I reversed the order of executing these two rules and get the result i expected. I think the iterator time which means the repeat execution times will help avoid this kind of problem by repeating executing these two rules many times, which even can improve the problem of recursive optimization.

cc @godfreyhe to have another look


Tensor flip along dimension

Thanks for the amazing library! :crab:
Feature description
I would like to flip a tensor along a given dimension. This would be like pytorch's flip function.
Basically it just creates a "mirror" image of the tensor:

Reverse the order of an n-D tensor along given axis in dims.
Parameters
input (Tensor) – the input tensor.
dims (a list or tuple) – axis to flip on

Feature motivation
I want to create a reverse diagonal, but I'm sure there are many more usecases, as this seems like a very basic operation.
Forgive me if there's a way to do this that I missed.

If anyone else runs into this, here's code for creating a reverse-diagonal square matrix:
fn reverse_diagonal<B: Backend>(size: usize) -> Tensor<B, 2> {
    let t = Tensor::zeros([size * size]);
    let indices = Tensor::arange(1..(size + 1)).mul_scalar(size as i64 - 1);
    let values = Tensor::ones([size]);
    t.select_assign(0, indices, values).reshape([size, size])
}

You can left-multiply with this to flip the rows, or right-multiply with it to flip the columns. It should work with any matrix, even non-square ones.
However, this feels like a workaround, and a native flip operation would be nice I think.

Hi, I'd like to take a shot at this, if nobody is working on it already.

@dush-t
Hi, Are you still working on it?

@carrotflakes it has been a month and we don't we any open PR related. You can give a try. We will review your quickly.

It seems there's a bug in this implementation as it relates to transpose:
let device = &Default::default();
type B = burn::backend::wgpu::JitBackend<WgpuRuntime<AutoGraphicsApi, f32, i32>>;
let arr: Tensor<B, 2> = Tensor::from_ints([[1, 2], [3, 4], [5, 6]], device).float();
let arr2 = arr.flip([0]).transpose(); // equivalent to rotating 90 degrees

// This correctly rotates the matrix and will print out
// [[5, 3, 1], [6, 4, 2]]
println!("{arr2}");

// But the following should yield the same result and doesn't:
let arr2 = arr.transpose().flip([1]); // equivalent to rotating 90 degrees

// This will print out an unexpected result:
// [[5.0, 6.0, 3.0], [4.0, 1.0, 2.0]]
println!("{arr2}");

Can anyone confirm this?


bump minimum php version to 5.5

This PR sounds good.. Why is it frozen?

the 2nd commit can be cherry-picked for DateTimeInterface check

:+1:

You can cherry pick the commit and create a PR only with that change.

@Maks3w yes I can, but please, I create the PR before the dramatically change php require version for composer.json on all repo. I am wondering why all the change is not seeing the avaialble PR first :)

@samsonasik it's simple. you did a batch of prs without coordinate with the crteam

All this words for a cherry-pick :D #25
Thanks @samsonasik for this contribution I don't know if this is a batch process but you have resolved all php5.5 compatibility and not only composer.json configuration.. Perfect!
baaahh :disappointed:

we already did get info that zf 2.5 will require php >=5.5 ... so sorry for not asking about it first to crteam.

and I check one by one the changes in every repo..., that ALL ok


Error when added annotations or podLabeles

Hello!
Why are added to expose.annotations or podLabels array ?
Why i can't add
Something like this
podLabels:
microservice: infinispan
I
received error
values don't meet the specifications of the schema(s) in the following chart(s):
│ infinispan:
│ - deploy.expose.annotations: Invalid type. Expected: [array,null], given: object
│ - deploy.podLabels: Invalid type. Expected: [array,null], given: object
I'm always added without array, like example

I see that you did
annotations:
{{- include "infinispan-helm-charts.annotations" . | nindent 4 }}
{{- range .Values.deploy.expose.annotations }}
{{ .key | quote }}: {{ .value | quote }}
{{- end }}
but normaly do this. It's template from helm when helm create chart
{{- with .Values.ingress.annotations }}
annotations:
{{- toYaml . | nindent 4 }}
{{- end }}

I did this
annotations: [
"kubernetes.io/ingress.class"="alb",
"alb.ingress.kubernetes.io/group.name"="group.name",
"alb.ingress.kubernetes.io/group.order"="group.order",
"alb.ingress.kubernetes.io/scheme"="internal",
"alb.ingress.kubernetes.io/target-type"="ip",
"alb.ingress.kubernetes.io/listen-ports"=""[{"HTTP": 80}, {"HTTPS":443}]"",
"alb.ingress.kubernetes.io/certificate-arn"="cert",
"alb.ingress.kubernetes.io/ssl-redirect"="443"
]
but received error
Error: ---> error converting YAML to JSON: yaml: line 58: did not find expected ',' or ']' # Default values for infinispan-helm-charts.
line number in your value is
58   annotations: []

@oburd Try:
deploy:
  expose:
    annotations:
      - key: kubernetes.io/ingress.class
        value: alb
      - key: alb.ingress.kubernetes.io/group.name
        value: group.name
     - ...

values don't meet the specifications of the schema(s) in the following chart(s):
│ infinispan:
│ - deploy.expose.annotations: Invalid type. Expected: [array,null], given: object
│ - deploy.podLabels: Invalid type. Expected: [array,null], given: object
Same error
As i see in your template you did next
annotations:
{{- include "infinispan-helm-charts.annotations" . | nindent 4 }}
{{- range .Values.deploy.expose.annotations }}
{{ .key | quote }}: {{ .value | quote }}
{{- end }}
but in default helm charts created this and you can add normaly annotations
{{- with .Values.ingress.annotations }}
annotations:
{{- toYaml . | nindent 4 }}
{{- end }}

Let me give you a full picture:

I'm using terroform with helm_release = helm
I added chart and repository
repository    = "https://charts.openshift.io/"
chart         = "infinispan-infinispan"
I set some variables to values file
There is my values file, which i took from your git repos helm chart

Default values for infinispan-helm-charts.
This is a YAML-formatted file.
Declare variables to be passed into your templates.
images:
[USER] The container images for server pods.
server: quay.io/infinispan/server:14.0
initContainer: registry.access.redhat.com/ubi8-micro
deploy:
[USER] Specify the number of nodes in the cluster.
replicas: 1
clusterDomain: cluster.local
container:
extraJvmOpts: ""
libraries: ""
# [USER] Define custom environment variables using standard K8s format
# env:
#  - name: STANDARD_KEY
#    value: standard value
#  - name: CONFIG_MAP_KEY
#    valueFrom:
#      configMapKeyRef:
#        name: special-config
#        key: special.how
#  - name: SECRET_KEY
#    valueFrom:
#      secretKeyRef:
#        name: special-secret
#        key: special.how
env:
storage:
size: 1Gi
storageClassName: ""
# [USER] Set ephemeral: true to delete all persisted data when clusters shut down or restart.
ephemeral: false
resources:
# [USER] Specify the CPU limit and the memory limit for each pod.
limits:
cpu: 500m
memory: 512Mi
# [USER] Specify the maximum CPU requests and the maximum memory requests for each pod.
requests:
cpu: 500m
memory: 512Mi
security:
secretName: ""
batch: ""
expose:
# [USER] Specify type: "" to disable network access to clusters.
type: Route
nodePort: 0
host: ""
annotations:
kubernetes.io/ingress.class: alb
alb.ingress.kubernetes.io/group.name: dummy
alb.ingress.kubernetes.io/group.order: 'dummy'
alb.ingress.kubernetes.io/scheme: internal
alb.ingress.kubernetes.io/target-type: ip
alb.ingress.kubernetes.io/listen-ports: '[{"HTTP": 80}, {"HTTPS":443}]'
alb.ingress.kubernetes.io/certificate-arn: dummy
alb.ingress.kubernetes.io/ssl-redirect: '443'
monitoring:
enabled: false
logging:
categories:
# [USER] Specify the FQN of a package from which you want to collect logs.
- category: com.arjuna
# [USER] Specify the level of log messages.
level: warn
# No need to warn about not being able to TLS/SSL handshake
- category: io.netty.handler.ssl.ApplicationProtocolNegotiationHandler
level: error
makeDataDirWritable: false
nameOverride: ""
resourceLabels: []
podLabels:
microservice: infinispan
svcLabels: []
tolerations: []
nodeAffinity: {}
nodeSelector: {}
infinispan:
cacheContainer:
# [USER] Add cache, template, and counter configuration.
name: default
# [USER] Specify security: null to disable security authorization.
security:
authorization: {}
transport:
cluster: ${infinispan.cluster.name:cluster}
node-name: ${infinispan.node.name:}
stack: kubernetes
server:
endpoints:
# [USER] Hot Rod and REST endpoints.
- securityRealm: default
socketBinding: default
connectors:
rest:
restConnector:
hotrod:
hotrodConnector:
# [MEMCACHED] Uncomment to enable Memcached endpoint
# memcached:
#   memcachedConnector:
#     socketBinding: memcached
# [METRICS] Metrics endpoint for cluster monitoring capabilities.
- connectors:
rest:
restConnector:
authentication:
mechanisms: BASIC
securityRealm: metrics
socketBinding: metrics
interfaces:
- inetAddress:
value: ${infinispan.bind.address:<IP_ADDRESS>}
name: public
security:
credentialStores:
- clearTextCredential:
clearText: secret
name: credentials
path: credentials.pfx
securityRealms:
# [USER] Security realm for the Hot Rod and REST endpoints.
- name: default
# [USER] Comment or remove this properties realm to disable authentication.
propertiesRealm:
groupProperties:
path: groups.properties
groupsAttribute: Roles
userProperties:
path: users.properties
# [METRICS] Security realm for the metrics endpoint.
- name: metrics
propertiesRealm:
groupProperties:
path: metrics-groups.properties
relativeTo: infinispan.server.config.path
groupsAttribute: Roles
userProperties:
path: metrics-users.properties
relativeTo: infinispan.server.config.path
socketBindings:
defaultInterface: public
portOffset: ${infinispan.socket.binding.port-offset:0}
socketBinding:
# [USER] Socket binding for the Hot Rod and REST endpoints.
- name: default
port: 11222
# [METRICS] Socket binding for the metrics endpoint.
- name: metrics
port: 11223
# [MEMCACHED] Uncomment to enable Memcached endpoint
# - name: memcached
#   port: 11221
5. I added only several things.
First thing annotation for expose that i can connect to infinispan from internet through AWS ALB
Second thing PodLabels
I gave some details for your, for more understanding my problem

@oburd I've updated your comment to highlight the yaml in a code block as this is much easier to read.
Can you paste the error that you're receiving with the current values.yaml?

@ryanemerson  oh, thank you. Looks better :)
There is an error
Error: values don't meet the specifications of the schema(s) in the following chart(s): │ infinispan: │ - deploy.expose.annotations: Invalid type. Expected: [array,null], given: object │ - deploy.podLabels: Invalid type. Expected: [array,null], given: object │  │  │   with helm_release.infinispan, │   on main.tf line 29, in resource "helm_release" "infinispan": │   29: resource "helm_release" "infinispan" { │  ╵

The podLabels and annotations need to be an array of objects with key and value elements, e.g.
podLabels:
  podLabels:
    - key: microservice
      value: infinispan

annotations:
  expose:
    # [USER] Specify `type: ""` to disable network access to clusters.
    type: Route
    nodePort: 0
    host: ""
    annotations:
      - key: kubernetes.io/ingress.class
        value: aib
      # TODO convert the remaining annotations
      # alb.ingress.kubernetes.io/group.name: dummy
      # alb.ingress.kubernetes.io/group.order: 'dummy'
      # alb.ingress.kubernetes.io/scheme: internal
      # alb.ingress.kubernetes.io/target-type: ip
      # alb.ingress.kubernetes.io/listen-ports: '[{"HTTP": 80}, {"HTTPS":443}]'
      # alb.ingress.kubernetes.io/certificate-arn: dummy
      # alb.ingress.kubernetes.io/ssl-redirect: '443'

You will also need to add the following jmx definition:
deploy:
  jmx:
    enabled: false

What is
deploy:   jmx:     enabled: false
i dont see in values this variable

@oburd Ignore that suggestion :slightly_smiling_face: . I was working on a dirty feature branch that hasn't been merged into main.

@ryanemerson  okay understood. Thank you for help :)
i will do it and if everything okay i will close this conversation

@ryanemerson  Hello!
I have faced with one problem
in terraform i'm using set
set {
    name  = "expose.annotations.- key.\\alb\\.\\ingress\\.\\kubernetes\\.io/certificate-arn"
    value = local.infinispan.cert_arn
  }

P.S. terraform helm_release with set = helm install --set variable=value
But i cant do it because it's incorrect name and variable doesn't change
Maybe you or someone faced with this problem ?
Thank you

Sorry @oburd, I don't use Terraform so I can't help here.

Eh, thank you. I will try to find :)

@ryanemerson  sorry do you use a helm ? how you set variable if using command helm install --set expose.annotation and how it's look like

I have resolved issue for me, thank you for help


--all should report which files it failed to instrument

#173 uses --all on a file containing unrecognized syntax. Requiring babel-core/register is the correct solution but it's unfortunate that nyc spits out a rather deep stack trace. Instead it should report which file it failed to instrument, offering suggestions regarding excluding those files or hooking up a transpiler.

@novemberborn I think the new approach used for --all on the 7.x branch might address this problem, if you get a second take a look.

Also had issues with --all, upgrading to<EMAIL_ADDRESS>fixed the issue.


[WIP] CI testing

Noteworthy changes -

land_detector VtolLandDetector::_get_maybe_landed_state() and VtolLandDetector::_get_landed_state() check if vehicle status is valid before using it
VtolLandDetector::_get_landed_state() check airspeed confidence as well
land_detector and hysteresis initialize everything in the header (easier to see that we didn't miss anything)

The 2nd commit 0a48d71 increases the logging rate on SITL considerably (~ 40 KiB/s -> 70 KiB/s), but that's still hardly anything for a desktop computer, and the additional logging is valuable for debugging the extremely intermittent CI failures we've been seeing.

Continued in https://github.com/PX4/Firmware/pull/9157


update(OWNERS): add Federico Di Pierro (fededp) to OWNERS

Signed-off-by: Federico Di Pierro<EMAIL_ADDRESS>What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area driver-kmod

/area driver-ebpf

/area libscap

/area libsinsp

/area tests

/area proposals

What this PR does / why we need it:
I am proposing myself as a maintainer: during the last few months i have been quite busy fixing eBPF issues, improving overall code quality and implementing both fixes and new features on the libs repository.
Moreover, i engaged as much as i could with the community by answering issues both on github and on the Falco slack channel, whenever i had an answer.
Finally, i am helping other maintainers taking a breath by actively reviewing PRs (even if my approval has no value right now!)
I feel this is the right time to step up my contributions and assume this important role for the project!
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: FedeDP
To complete the pull request process, please assign mstemm after the PR has been reviewed.
You can assign the PR to them by writing /assign @mstemm in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Hi @FedeDP. Thanks for your PR.
I'm waiting for a falcosecurity member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

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

The following users are mentioned in OWNERS file(s) but are untrusted for the following reasons. One way to make the user trusted is to add them as members of the falcosecurity org. You can then trigger verification by writing /verify-owners in a comment.

fededp

User is not a member of the org. Satisfy at least one of these conditions to make the user trusted.
OWNERS

LGTM label has been added.  Git tree hash: fb76f15243ae7d464030899766afdee76ebe2e98

Hey, @FedeDP I have sent you a GitHub invitation to the Falcosecurity Github org. Ping me once you accept it :)
Ofc, huge +1 for me :partying_face:

Aaaan accepted @leogr !
Btw thanks @leodido and @gnosek for your trust :)

/verify-owners

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Option to clear Process status from export

An HTML export includes the Process status data: https://github.com/fonsp/Pluto.jl/pull/2399
We should add an option to clear this from the exports generated by PlutoSliderServer, to:

Avoid a slightly confusing situation when launching a featured notebook: while loading, it will show a Status tab where everything has completed.
Canonalize exports a bit.
It feels more "clean"

I decided to implement this by default, without an option to change the behaviour (it's quite specific, it solves stability issues and I don't see a good reason to want the old behaviour).


Webpack 5: Add "ids" to the retrieved JSON stats

This PR adds the ids objects to the stats retrieved by stats.toJson().
It is needed by the latest alpha of Webpack 5 (v5.0.0-alpha.31) in order to retrieve asset.chunks later on (see https://github.com/webpack/webpack/pull/9793#pullrequestreview-300371456).
Without it, the following error is thrown by the plugin:
TypeError: Cannot read property 'length' of undefined
    at (...)/node_modules/webpack-manifest-plugin/lib/plugin.js:128:39

Codecov Report

Merging #200 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #200   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           4      4
  Lines         129    129
  Branches       26     26
=====================================
  Hits          129    129

Impacted Files
Coverage Δ

lib/plugin.js
100% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

@mastilver Should I add webpack@next to the peer dependencies and tests? I noticed that you also changed them in #197, so maybe I should target that PR's branch instead?

@Lyrkan Yes, I believe your PR should target next
Unfortunately I'm having some issue with the tests on that branch and until this is resolved I'm blocked

@mastilver Changed the target branch to next and tried to fix the tests after merging master to get the Webpack 5 fix that was commited on it (hence the additional commits and comment on this PR).
I also added back webpack@next to the CI matrix.
Hope I didn't forget anything :)

That's great, thank you


[draft] Capture crash dumps from libfuzzer, when provided

Summary of the Pull Request
What is this about?
PR Checklist

[ ] Applies to work item: #xxx
[ ] CLA signed. If not, go over here and sign the CLI.
[ ] Tests added/passed
[ ] Requires documentation to be updated
[ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

Info on Pull Request
What does this include?
Validation Steps Performed
How does someone test & validate?

Codecov Report

Merging #2793 (96f26db) into main (457eb1e) will decrease coverage by 4.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #2793      +/-   ##
==========================================
- Coverage   29.51%   25.50%   -4.01%
==========================================
  Files         322      124     -198
  Lines       38791    13044   -25747
==========================================
- Hits        11449     3327    -8122
+ Misses      27342     9717   -17625

Impacted Files
Coverage Δ

src/agent/onefuzz-task/src/local/common.rs

src/agent/onefuzz-task/src/local/libfuzzer_fuzz.rs

...nt/onefuzz-task/src/tasks/fuzz/libfuzzer/common.rs

src/agent/srcview/src/lib.rs

.../onefuzz-task/src/tasks/report/libfuzzer_report.rs

src/agent/onefuzz/src/env.rs

src/agent/onefuzz/src/asan.rs

src/agent/coverage/src/binary.rs

...c/agent/onefuzz-task/src/tasks/analysis/generic.rs

src/agent/debugger/src/lib.rs

... and 188 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


data runs before onBeforeAction

In iron-router versions prior to 1 the onBeforeAction did run before data, which was helpful in some cases. Now that has changed, data runs before onBeforeAction. Why has that changed? Is it intended?

I've had issues with onBeforeAction, I don't even know if it's still supported for sure. I switched to using onRun.
For example:
Router.onRun(requireLogin, { only: [
  'postSubmit',
  'dashboard',
  'locations',
  'properties',
  'providers'
] });

Thank you! onRun works for me, too. The onBeforeAction still seems to be supported, as I can find it in the guide. It would be nice if it would just work like it did before. It might be helpful in cases like this:
I'm using the space:ui package and need to tell the store, which document I want. In iron:router < v1, the following worked great, the router checked if the document exists:

class App.CasesPrintController

  Dependencies:
    actions: 'Actions'
    meteor: 'Meteor'
    router: 'Router'
    store: 'CasesStore'
    tracker: 'Tracker'

  onDependenciesReady: ->

    self = this

    @router.route 'cases.print',
      path: '/print/:_id'

      waitOn: ->
        singleSubs.subscribe 'printCase', @params._id

      data: ->
        self.store.getState().case.fetch()[0]

      onBeforeAction: ->
        caseId = @params._id

        self.tracker.nonreactive -> self._setCurrentCase caseId

        @next()

      action: ->
        unless self.meteor.user()
          @layout 'PrintLayout'

        @render()  if @ready()

  _setCurrentCase: (caseId) ->
    @actions.setCurrentCase caseId

Now, as onBeforeAction runs after data, I have to put all the stuff from the onBeforeAction into data, which seems hacky.
I also think this behaviour might explain my issue here: https://github.com/zimme/meteor-iron-router-auth/issues/9

Yeah, I'm not sure what's going on here, I was expecting onBeforeAction to work as well, I just noticed it didn't yesterday as well.

The problem with onRun is, that in some cases the actual page just flashes, before the login page appears.

The problem with onRun is, that in some cases the actual page just flashes, before the login page appears. @victorbstan do you know how to solve this?

@zimt28
I'm not sure what you are seeing. I don't have flashes, if log out and try to visit a page where I'm checking for authentication in onRun, the visitor is redirected to the login page right away... might depend on how you have your routes/controllers set-up?

I'm currently using zimme/meteor-iron-router-auth, but I'll try your solution later this day.

I've noticed this too. I console.log(1) and console.log(2) on the onBeforeAction and data function and the data runs first. This is not what one would expect and it pretty frustrating. onBeforeAction should run before data.

When I switched to onRun it seems to work. is onRun the first thing that is run when a route is visited?

Hey folks, maybe a different topic but is onRun safe for auth checking?
@victorbstan @sferoze


Error: invalid character 'ï'

When ingesting data from our domain collected with the latest Sharphound (v2.0.0) the following error is logged in BloodhoundCE:
{"level":"error","time":"2023-08-15T07:39:55.366631981Z","message":"Error processing ingest task 178: invalid character 'ï' looking for beginning of value"}
A quick grep for the character in question revealed several user displaynames containing this character. As far as I can tell, the error renders the entire ingest corrupt and makes it unusable.
Edit: Not only is the current ingest corrupt, but the entire neo4j-Database becomes unusabel for Bloodhound and must be rebuild from scratch.
As Sharphound collects the data with this encoding, I would expect Bloodhound to be able to parse it without problems.

Was having the same issue, but only when uploading via the API. If I uploaded via the GUI then it was fine, but had a few files over 1gb so the API was the only option.
I ended up using the script written by aconite33 linked to in this issue: https://github.com/SpecterOps/BloodHound/issues/20
Then had to change lines 62 and 63 as below, and then the uploads via the API worked without that special character:
with open(args.file, mode='r', encoding='utf-8-sig') as f:         data = f.read().encode('utf-8')

Thank you @dmquik
I had to adapt your approach for large files, but it works now. For anyone looking for a solution:
with open('newly_encoded.json', mode='w', encoding='utf-8') as target_file:
        with open('original.json', encoding='utf-8-sig') as source_file:
            while True:
                data = source_file.read(1024)
                if not data:
                    break
                target_file.write(data)

Anyhow, it remains a bug in my opinion.

I'm not entirely sure whats going on with this because I wrote a test ensuring that umlauts ingest fine.
https://github.com/SpecterOps/BloodHound/pull/32
The test works a-ok and it uses the API to do the ingest. I'm wondering if theres something else going on here

In case someone else stumbles upon this like I did, the "ï" character that the error message was referring to in my instance was the UTF-8 BOM.
I was using PowerShell to read the JSON files to send them via the API. PowerShell 5.1 and lower interpret any UTF-8 encoding as UTF-8 BOM. I was able to get around it by reading the file as text then getting the bytes with the UTF8 encoder.

I digged a bit deeper into the problem, because i did a rework of our ingestion code yesterday.
Disclaimer: I am using Python for this, but it seems other languages have similar issues.
First of all, I do not think it is the BOM itself. I have 3 reasons for this assumption:

The character "ï" (0xC3AF in Unicode) is not part of any legit BOM.
Not all files nor domains trigger the error, so it must be specific to a domain. The encoding is the same in all files.
When trying to parse the files content to an UTF-8 string in Python, I encountered issues way into the file. The BOM is per definition the first bytes in a file.

Amazingly, the workaround from @dmquik  is still working. But it is also needed.
It appears, that files containing the Bytestring 0xC3AF cannot be parsed correctly by Bloodhound and are therefore discarded. That means, if you have a user in your domain with that character in her display name for example, you will not be able to ingest the file without further preprocessing.


Add Discord link in the home page

add Discord link to the pupil chat under Pupil is Open Source section.

@willpatera - PR https://github.com/pupil-labs/pupil-labs-website/pull/266
I thought of just linking it in the text but thought it would be alot more distinguishable from other elements if it was a button. And it would be more inviting for users to press it as well.

Thanks! Merged; closing 😸


Fix android support

As for building, I found cargo-apk and ndk-glue much easier to work with.

Gonna close this since it's been in draft for a while and we ended up pushing lots of fixes for android recently.
Thanks for the PR anyways!


Terragrunt not installing providers through terraform

I've recently switched my terraform project to use terragrunt, but now I find that terragrunt is not installing the necessary providers.
Here is the output from terragrunt:
terragrunt plan --terragrunt-log-level debug --terragrunt-debug
time=2021-05-28T15:07:37-04:00 level=debug msg=Did not find any locals block: skipping evaluation.
time=2021-05-28T15:07:37-04:00 level=debug msg=Did not find any locals block: skipping evaluation.
time=2021-05-28T15:07:37-04:00 level=debug msg=Running command: terraform --version prefix=[C:\Users\81dub\source\repos\powerinbox\infrastructure\dev\portal]
time=2021-05-28T15:07:37-04:00 level=debug msg=Terraform version: 0.15.0
time=2021-05-28T15:07:37-04:00 level=debug msg=Reading Terragrunt config file at C:/Users/81dub/source/repos/powerinbox/infrastructure/dev/portal/terragrunt.hcl
time=2021-05-28T15:07:37-04:00 level=debug msg=Did not find any locals block: skipping evaluation.
time=2021-05-28T15:07:37-04:00 level=debug msg=Did not find any locals block: skipping evaluation.
time=2021-05-28T15:07:37-04:00 level=debug msg=Detected 1 Hooks prefix=[C:\Users\81dub\source\repos\powerinbox\infrastructure\dev\portal]
time=2021-05-28T15:07:37-04:00 level=debug msg=Downloading Terraform configurations from file://C:/Users/81dub/source/repos/powerinbox/infrastructure into C:/Users/81dub/source/repos/powerinbox/infrastructure/dev/portal/.terragrunt-cache/1UF9hJv3VEAz_vVSYdsdWOBUXWg/82_c7FDM1x8KdFI2_PjD1PIVWhM
time=2021-05-28T15:07:37-04:00 level=debug msg=Copying files from C:/Users/81dub/source/repos/powerinbox/infrastructure/dev/portal into C:/Users/81dub/source/repos/powerinbox/infrastructure/dev/portal/.terragrunt-cache/1UF9hJv3VEAz_vVSYdsdWOBUXWg/82_c7FDM1x8KdFI2_PjD1PIVWhM/modules/portal
time=2021-05-28T15:07:37-04:00 level=debug msg=Setting working directory to C:/Users/81dub/source/repos/powerinbox/infrastructure/dev/portal/.terragrunt-cache/1UF9hJv3VEAz_vVSYdsdWOBUXWg/82_c7FDM1x8KdFI2_PjD1PIVWhM/modules/portal
time=2021-05-28T15:07:37-04:00 level=debug msg=The file path C:\Users\81dub\source\repos\powerinbox\infrastructure\dev\portal\.terragrunt-cache\1UF9hJv3VEAz_vVSYdsdWOBUXWg\82_c7FDM1x8KdFI2_PjD1PIVWhM\modules\portal\backend.tf already exists, but was a previously generated file by terragrunt. Since if_exists for code generation is set to "overwrite_terragrunt", regenerating file. prefix=[C:\Users\81dub\source\repos\powerinbox\infrastructure\dev\portal]
time=2021-05-28T15:07:37-04:00 level=debug msg=Generated file C:\Users\81dub\source\repos\powerinbox\infrastructure\dev\portal\.terragrunt-cache\1UF9hJv3VEAz_vVSYdsdWOBUXWg\82_c7FDM1x8KdFI2_PjD1PIVWhM\modules\portal\backend.tf. prefix=[C:\Users\81dub\source\repos\powerinbox\infrastructure\dev\portal]
time=2021-05-28T15:07:37-04:00 level=info msg=Debug mode requested: generating debug file terragrunt-debug.tfvars.json in working dir C:/Users/81dub/source/repos/powerinbox/infrastructure/dev/portal/.terragrunt-cache/1UF9hJv3VEAz_vVSYdsdWOBUXWg/82_c7FDM1x8KdFI2_PjD1PIVWhM/modules/portal prefix=[C:\Users\81dub\source\repos\powerinbox\infrastructure\dev\portal]
time=2021-05-28T15:07:37-04:00 level=debug msg=The following variables were detected in the terraform module: prefix=[C:\Users\81dub\source\repos\powerinbox\infrastructure\dev\portal]
time=2021-05-28T15:07:37-04:00 level=debug msg=[prefix deployment hostname app_plan_sku_tier app_plan_sku_size app_environment key_vault_name tags security_service_password location] prefix=[C:\Users\81dub\source\repos\powerinbox\infrastructure\dev\portal]
time=2021-05-28T15:07:37-04:00 level=debug msg=Variables passed to terraform are located in "C:\Users\81dub\source\repos\powerinbox\infrastructure\dev\portal\terragrunt-debug.tfvars.json" prefix=[C:\Users\81dub\source\repos\powerinbox\infrastructure\dev\portal]
time=2021-05-28T15:07:37-04:00 level=debug msg=Run this command to replicate how terraform was invoked: prefix=[C:\Users\81dub\source\repos\powerinbox\infrastructure\dev\portal]
time=2021-05-28T15:07:37-04:00 level=debug msg= terraform plan -var-file="C:\Users\81dub\source\repos\powerinbox\infrastructure\dev\portal\terragrunt-debug.tfvars.json" "C:/Users/81dub/source/repos/powerinbox/infrastructure/dev/portal/.terragrunt-cache/1UF9hJv3VEAz_vVSYdsdWOBUXWg/82_c7FDM1x8KdFI2_PjD1PIVWhM/modules/portal" prefix=[C:\Users\81dub\source\repos\powerinbox\infrastructure\dev\portal]
time=2021-05-28T15:07:37-04:00 level=debug msg=Backend azurerm has not changed. prefix=[C:\Users\81dub\source\repos\powerinbox\infrastructure\dev\portal]
time=2021-05-28T15:07:37-04:00 level=debug msg=Detected 1 Hooks prefix=[C:\Users\81dub\source\repos\powerinbox\infrastructure\dev\portal]
time=2021-05-28T15:07:37-04:00 level=info msg=Executing hook: before_hook prefix=[C:\Users\81dub\source\repos\powerinbox\infrastructure\dev\portal]
time=2021-05-28T15:07:37-04:00 level=debug msg=Running command: terraform init prefix=[C:\Users\81dub\source\repos\powerinbox\infrastructure\dev\portal]

Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/azurerm versions matching "2.61.0"...
- Finding hashicorp/azuread versions matching "1.5.0"...
- Installing hashicorp/azurerm v2.61.0...
- Installing hashicorp/azuread v1.5.0...
╷
│ Error: Failed to install provider
│
│ Error while installing hashicorp/azurerm v2.61.0: open
│ .terraform\providers\registry.terraform.io\hashicorp\azurerm\2.61.0\windows_amd64\terraform-provider-azurerm_v2.61.0_x5.exe:
│ The system cannot find the path specified.
╵

╷
│ Error: Failed to install provider
│
│ Error while installing hashicorp/azuread v1.5.0: open
│ .terraform\providers\registry.terraform.io\hashicorp\azuread\1.5.0\windows_amd64\terraform-provider-azuread_v1.5.0_x5.exe:
│ The system cannot find the path specified.
╵

time=2021-05-28T15:07:42-04:00 level=error msg=Error running hook before_hook with message: exit status 1 prefix=[C:\Users\81dub\source\repos\powerinbox\infrastructure\dev\portal]
time=2021-05-28T15:07:42-04:00 level=error msg=Errors encountered running before_hooks. Not running 'terraform'. prefix=[C:\Users\81dub\source\repos\powerinbox\infrastructure\dev\portal]
time=2021-05-28T15:07:42-04:00 level=error msg=Hit multiple errors:
Hit multiple errors:
exit status 1

The .exe files are not present in the .terraform folder

Here is the output from terraform using my legacy folder structure:
terraform init

Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/azurerm versions matching "2.61.0"...
- Finding hashicorp/azuread versions matching "1.5.0"...
- Installing hashicorp/azuread v1.5.0...
- Installed hashicorp/azuread v1.5.0 (self-signed, key ID 34365D9472D7468F)
- Installing hashicorp/azurerm v2.61.0...
- Installed hashicorp/azurerm v2.61.0 (self-signed, key ID 34365D9472D7468F)

Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/cli/plugins/signing.html

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

The .exe files are present in the .terraform directory

Here is my root terragrunt.hcl
remote_state {
  backend = "azurerm"
  generate = {
    path      = "backend.tf"
    if_exists = "overwrite_terragrunt"
  }
  config = {
    key                  = "${path_relative_to_include()}/terraform.tfstate"
    resource_group_name  = "terraform"
    storage_account_name = "terraformstate"
    container_name       = "tfstate"
    subscription_id      = "omitted"
    tenant_id            = "omitted"
    snapshot             = true
  }
}

I'm using terragrunt v0.29.6 and terraform v0.15.0 running on Windows 10 version 20H2

This is most likely the Windows LongPath issue, where the terraform path name is too long for terraform to install providers into. See https://github.com/gruntwork-io/terragrunt/issues/581#issuecomment-460051767 for a workaround.

Aka, friends don't let friends use windows

@yorinasub17 That worked thank you


Call to undefined method Doctrine\ORM\Query\Expr::myCustomMethod()

I have custom Expr class extended from Doctrine\ORM\Query\Expr
I think, PHPStan doesn't know about that class and trigger error
In ExpressionBuilderDynamicReturnTypeExtension.php line 67:

  Attempted to call an undefined method named "myCustomMethod" of class "Doctrine\ORM\Query\Expr".

is it because Doctrine\ORM\Query\Expr harcoded in getClass() method?
How to fix that?

Hi, how are you able to use custom Expr class? Do you extend your QueryBuilder? Can you show me your $qb->expr() method?

It's used as helper class for building custom DQL parts.
instantiate only as new CustomExpr(). We able to generate some DQL parts and pass their to standard QueryBuilder methods.
So, our EntityManager doesn't know about CustomExpr too..)
Thinking about adding exprClass argument for ExpressionBuilderDynamicReturnTypeExtension costructor. What do You think?

Can you create a small sample repo? Still can't imagine how it works and why PHPStan fails on it.

Can you create a small sample repo? Still can't imagine how it works and why PHPStan fails on it.

I prepared an example project

Hi, I just commited a fix to master that solves this: https://github.com/phpstan/phpstan-doctrine/commit/9fac3a7eb075a2594e0fb95aeeb96b6c0065e2d4
With a few caveats:

Right now, your code won't crash PHPStan, but it won't be checked for any errors. Run PHPStan with doctrine.reportDynamicQueryBuilders set to true (https://github.com/phpstan/phpstan-doctrine/blob/master/rules.neon#L3) to verify this. It might find other dynamic QBs that are impossible to verify.
To be able to verify code using your custom Expr class, unfortunately, the class has to contain a constructor, even if it's empty. This is currently a limitation of dynamic return type extension system in PHPStan: https://github.com/phpstan/phpstan/blob/master/src/Analyser/Scope.php#L1051-L1070

Please follow these steps and tell me if it solves your problem and I can tag a new version. Thanks.

This commit fixed my issue and thanks for caveats!

Released as 0.11.4: https://github.com/phpstan/phpstan-doctrine/releases/tag/0.11.4

You no longer need the empty constructor, thanks to 0.11.9: https://github.com/phpstan/phpstan/releases/tag/0.11.9 (and this commit: https://github.com/phpstan/phpstan/commit/5fc3a8d02358dacb7a63d0d18cb5155a5b93586d)


Updated AMD-RAID Drivers(9.3.0) available via Lenovo

Lenvovo has recently released some Threadripper based workstations and are running Redhat Linux. Available in the support downloads are an update version of this driver software, version 9.3.0, and offers support for NVME RAID.
Said drivers can be found here:
https://pcsupport.lenovo.com/us/en/products/workstations/thinkstation-p-series-workstations/thinkstation-p620/downloads/driver-list/component?name=RAID%2FSAS HBA Controllers, Backplanes, Storage Expanders%2FSwitches
Recently Thomas Pietrowski of the rcraid-dkms Github repo made an attempt to get them working with his PPA, but he ran into some issues and he has marked the thread discussing the NVME support as "wontfix".
I just wanted to open an issue here and make you aware of these new drivers, if you'd like to take some time to look over them. Myself, i will be experimenting with these drivers to see if I can produce any kind of results.

This seems to be a binary file, not the source code. So there is not much we can do with this. Since it is specific for that OS and version.


Database Diagram Missing In ssms V18.0

Any alternate solution to generate db diagram in ssms V18.0 as I see database diagram option is missing in this version .

@devrakeshkumar - thanks for the feedback!
Adding @Matteo-T and @dnethi who might have some suggestions, but this area is primarily for specific doc issues so I'm going to close this one. The best way to reach out to the team with issues, feedback, or suggestions is at UserVoice.
Thanks!


Block non-HTTP connections to external IPs

I'm not sure what kind of network connections PAWS users need from their notebooks, but I assume most will be HTTP connections to external websites or APIs.
Blocking other types of ports and protocols should prevent several forms of malicious traffic that could originate from PAWS.
Bug: T381373

Hey!  As discussed on irc you should probably also allow UDP port 52 (dns) and 123 (ntp) as well.  Other than that it doesn't seem unreasonable to lock things down to TCP 80/443, but it can be wider than that if we know what's needed.

Looks like it isn't taking...
W1203 13:25:57.832715 4141109 warnings.go:70] unknown field "spec.egress[5].to[0].ports"
Error: UPGRADE FAILED: cannot patch "singleuser" with kind NetworkPolicy: NetworkPolicy.extensions "singleuser" is invalid: spec.egress[5].to[0]: Required value: must specify a peer

I think it wants an ipBlock (I was hoping it was optional). Pushing a fix shortly.

I think we can drop the 'to' clause and it seems pretty happy. Can't curl an ftp server at any rate

That change seems to allow access everywhere. Let me try something.

@vivian-rook try the latest version I just pushed

Oh the one I pushed last appears to be working, I'm going to push it again

Ok, I think we're good here. ssh and ftp aren't connecting externally, ssh is connecting internally, OpenRefine and Rstudio seem to work, pwb can do some things. I think we're good.


File System entries are not deleted after browser start up

Describe the bug
File System entries are not deleted after browser start up
To Reproduce
I am not sure if that's normal behavior but in different versions  of Ungoogled-Chromium I see sites, which used "File System" to have entries at chrome://settings/siteData
This entries are staying after Ungoogled-Chromium is closed and open again and there are not whitelisted.
Example of site which I used  and the "File System" is present https://www.theguardian.com/
Expected behavior
The normal bahavior in my understanding is unless the user is whitelisted them, everything should be cleared at browser start up.
Environment (please complete the following information):

Windows 10

I can confirm this to be the case. Some site's data is left in there.

What kind of data is stored in "File System"?

No idea. This is what shows up...

And after browser restart:

@Eloston to be fair I don't know :)
@Ph0rk0z Thank you for your screenshoots.
Maybe somebody else could have appropriate information about that?

I am not sure if the "File System" entries at chrome://settings/siteData have any connections with the "Native File System API". There is flag at chrome://flags/#native-file-system-api
"The Native File System API (formerly known as the Writeable Files API), is available as an origin trial in Chrome 78 (beta in September, stable in October) and later. It is part of capabilities project, and this post will be updated as the implementation progresses."*
*https://web.dev/native-file-system/

This is an old issue, that didn't show much activity recently — closing.
If you have any more information to add, let us know.


prevent DependencyHelper from adding self reference to a model

In certain cases where a reference is out of scope the "Add depedency to reference target" could add self reference to a model. This self reference would cause the build to fail afterwards. I added a check to no include the model of the node with the reference.

I've created request in MPS tracker for accepting this change:
https://youtrack.jetbrains.com/issue/MPS-27142


Clipboard history widget

Widget which shows recent clipboard items & allows re-copying them.

Might be able to use wl_clipboard_rs to make life easier for this


Adding Open Systems as an adopter

[ ] I added CHANGELOG entry for this change.
[x] Change is not relevant to the end user.

Changes

Added Open Systems as new item in adopters.yaml list
Added Open Systems Logo

Verification
Following guidelines from : https://thanos.io/tip/contributing/how-to-contribute-to-docs.md/#adopters-logos

This PR follows a previously closed PR (https://github.com/thanos-io/thanos/pull/6133) as I had some issues there with DCO.


[YUNIKORN-326]Add rest API to retrieve cluster nodes resource utilization

The api for cluster nodes utilization.
@yangwwei pls review. Thanks.

Travis tests have failed
Hey @HuangTing-Yao,
Please read the following log in order to understand the failure reason.
It'll be awesome if you fix what's wrong and commit the changes.
1st Build
View build log

     curl -sSfL https://raw.githubusercontent.com/golangci/golangci-lint/master/install.sh | sh -s -- -b $(go env GOPATH)/bin v1.22.2

golangci/golangci-lint info checking GitHub for tag 'v1.22.2'
golangci/golangci-lint info found version: 1.22.2 for v1.22.2/linux/amd64
golangci/golangci-lint info installed /home/travis/gopath/bin/golangci-lint

     make lint

running golangci-lint
pkg/webservice/handlers.go:158:13: should omit 2nd value from range; this loop is equivalent to `for name := range ...` (golint)
		for name, _ := range partition.GetTotalPartitionResource().Resources {
		          ^
pkg/webservice/dao/node_util.go:22: File is not `gofmt`-ed with `-s` (gofmt)
	ResourceType	string 			`json:"type"`
	NodesUtil    	[]*NodeUtilDAOInfo `json:"utilization"`
pkg/webservice/handlers.go:28: File is not `gofmt`-ed with `-s` (gofmt)
	"math"
pkg/webservice/handlers.go:159: File is not `goimports`-ed with -local github.com/apache/incubator-yunikorn (goimports)
			if name == "memory" ||name == "vcore"{
Makefile:45: recipe for target 'lint' failed
make: *** [lint] Error 1

TravisBuddy Request Identifier: 7aecf560-f295-11ea-82b8-f1691ab9f797

Hey @HuangTing-Yao,
Your changes look good to me!
View build log
TravisBuddy Request Identifier: bf68ef90-f4fd-11ea-aaf4-7d25d946cae2

Hey @HuangTing-Yao,
Your changes look good to me!
View build log
TravisBuddy Request Identifier: 69fba3e0-02fe-11eb-8abf-036a378110f7

Hey @HuangTing-Yao,
Your changes look good to me!
View build log
TravisBuddy Request Identifier: 0f025b50-0574-11eb-9f67-09c25eb247e4

Hey @HuangTing-Yao,
Your changes look good to me!
View build log
TravisBuddy Request Identifier: 93089320-0721-11eb-ae86-23b548ca2017


Correction for raw affiliation Northern Hail Project, Western University

Correction needed for raw affiliation Northern Hail Project, Western University
raw_affiliation_name: Northern Hail Project, Western University
new_rors: 02grkyz14
previous_rors: 017kqpz20
works_examples: W4393673687;W4393777534
contact: 0f8d3c7ab949f0c8043984062269d0d5:71e09b3f6963c2ab @ uwo.ca

This issue was accepted and ingested by the OpenAlex team on 2024-12-19. The new affiliations should be visible within the next 7 days.


fix: logging recursive matching on trace level

I'm not sure what this change is supposed to fix. How is changing the logging level addressing any recursion?

So it is not polluting the logs on Debug level.

OK, so I think this needs a better wording on the commit message then :)

OK, so I think this needs a better wording on the commit message then :)

Tried my best, changed the title. But feel free to change it :)


THREESCALE-11385 Community release of APIcast Operator v0.8.0 (2.14.1)

Jira: https://issues.redhat.com/browse/THREESCALE-11385

This PR is for validation and IMAGE creation for  Community APIcast Operator v0.8.0 (2.14.1)
** Image will be created in quay.io/3scale/apicast-operator:v0.8.0

PR does NOT create  Community Operator release; this will be done in Community Release PR:
** Community operator PR: https://github.com/redhat-openshift-ecosystem/community-operators-prod/pull/5232
*** you are welcom to review this PR also

PR includes new document with process of Apicast operator Community release creation - doc/community-release-build.md

For reference - please see similar PR for 3scale  Communiry release - https://github.com/3scale/3scale-operator/pull/950

Hello @eguzki , can I ask you about the process of Community release Image creation and using stable branch for this. Please correct me if following is wrong:

We will merge this PR and it will create Community Release Image. Bandle validation can be ignored (as we did for 3scale community release)
We will create another PR to revert Community release specific things like Name , Version, ... And it will allow us to continue use 3scale-2.14-stable branch for future patch releases (if required).
Thank you
cc @MStokluska

Hello @eguzki , can I ask you about the process of Community release Image creation and using 3scale-2.1X-stable branch for this. Please correct me if following is wrong:
1. Merging of this PR will create Community Release Image.

2. Bandle validation error can be ignored, as it cannot be achieved for a Community release (as we did for 3scale community release)

3. After mergeing of this PR and Image creation and Test - we will need to create another PR to revert Community release changes in 3scale-2.14-stable branch, to allow us to continue using 3scale-2.14-stable branch for future minor/patch releases (if required).
   Thank you
   cc @MStokluska

I had a different understanding of the flow.

Make this PR pass all tests, just like this one: https://github.com/3scale/3scale-operator/pull/979
Once merged, tag the branch which will trigger image creation
Copy the bundles to the community repo - with changes to the bundle dockerfile
Update/double check midstream to ensure that all fields changed in this PR are overwritten by midstream for future prod releases.

I had a different understanding of the flow.

Make this PR pass all tests, just like this one: 3scale 2.14 release candidate 3scale-operator#979
Once merged, tag the branch which will trigger image creation
Copy the bundles to the community repo - with changes to the bundle dockerfile
Update/double check midstream to ensure that all fields changed in this PR are overwritten by midstream for future prod releases.

@MStokluska I also will be glad if it will work this way, but meanwhile looks like issue is in difference in CSV, and I'm not sure if we can have following in Community CSV:

           rht.comp: 3scale_apicast

           rht.comp_ver: "2.14"

           rht.prod_name: Red_Hat_Integration

           rht.prod_ver: master

           rht.subcomp: apicast_operator

           rht.subcomp_t: infrastructure

But maybe we can have it here, but remove in Community REPO ...

@MStokluska, I'm not quite sure how the bundle-validate errors went away in 3scale community build. One guess is that this update was done on top the merged first CR, so the next build fixed it. But maybe I'm wrong.

All looks good but there's some points we need to address:

we should tag 0.8.0 in order to get the image and double check links (although they look fine)
we should have the integration tests pass on this PR ( I presume it will pass after making the image available etc)
we should test upgrade from 0.7.1 to this version and fresh installation.

1st - yes, I will check links after tagging and will confirm
2nd - Integration test passed now. Problem was - ubunto image deprication. Here is the list of linux images that were depricated for CircleCI - https://discuss.circleci.com/t/linux-image-deprecations-and-eol-for-2024/50177 . Ubuntu image now is same as in master.
3rd - sorry, forgot to add validation notes - fresh install was tested already (before send PR for review)  with my Repo's image https://quay.io/repository/vmogilev_rhmi/apicast-operator-index?tab=tags. Upgrade - TODO, I will send update.
Thank you for comments

@valerymo you can either include #222 in this PR or bump the ubuntu image separately to make the integration tests run/pass

ubuntu image updated, as current was depricated. Tests passed. Thank you for comment

@valerymo you can either include #222 in this PR or bump the ubuntu image separately to make the integration tests run/pass

done

@valerymo looks good, just 2 more questions and I think we can proceed with merge

@MStokluska  the merge is discussed with productization. This is slack link - https://redhat-internal.slack.com/archives/C050U4Z6JPQ/p1729491188254669
I think we can merge it.
Thank you


CPULib Extension framework

Extends CPULib to allow for addons to add new instructions to a ZVM platform on a per-entity basis, determined by the player's load order at entity creation.
The UI to load and unload extensions is available in the tool menu, clicking on an extension will switch it between the two categories

It will only show the available extensions for said tool, you won't see GPU extensions when looking at the CPU tool for example.
The HLZASM compiler & editor are aware of your currently available extended instructions, and can only highlight or compile them while enabled
(extension is enabled)

(extension is disabled)

Compilation/upload is also affected by the player's load order, so keep in mind if the load order differs between player & ent your code may not work correctly.
See cpu_example_extension.lua as an example for the structure required to make your own extension.

Think the api should be made as simple as possible to avoid breaking changes and extension authors making mistakes
local myCPUExtension = {
	Platform = "CPU",
	Instructions = {{
		Name = "CPU_TEST1",
		Operands = 1,
		Version = 0.42,
		Flags = {"W1"}, -- writes first operand
		Op1Name = "X",
		Op2Name = "",
		Description = "Sets Register X to constant 42",
		["OpFunc"] = function(self)
			-- The end value of the code in Dyn_EmitOperand will be assigned
			-- to the first/left hand register used in this instruction
			self:Dyn_EmitOperand("42")
		end
	},
	{
		Name = "CPU_TEST2",
		Operands = 1,
		Version = 0.42,
		Flags = {"W1"}, -- writes first operand
		Op1Name = "X",
		Op2Name = "",
		Description = "Divides Register X by constant 24",
		["OpFunc"] = function(self)
			-- $1 and $2 refer to the first, and second operands of the instruction respectively
			self:Dyn_EmitOperand("$1/24")
		end
	}}
}

To
local MyExtension = CPULib.RegisterCPUExtension("name" --[[, version? ]])

MyExtension:RegisterInstruction("XYZ", { "X" }, function(self)
    self:DynEmitOperand("$1/24") -- I'd like to swap this out too in favor of a safer api that you can be assured you won't want to remove later on. But it's up to you
end, { "W1" }) -- The "write" flag probably should be included in the actual argument. But I don't know enough about its purpose to give an ideal answer

Biggest concern here is extension authors making a bunch of addons with easy code injection, which is why I included the comment about another api.
Already Starfall has kind of had that issue before, not as much because it already has everything builtin. ZCPU doesn't have anything builtin, so potentially a lot of addons could be made for it which makes this very concerning.
Can't really think of a safer transpiled api. It would be much safer if it just transpiled extension operations to call the provided function, so being interpreted at that point.

local MyExtension = CPULib.RegisterCPUExtension("name" --[[, version? ]])

--- Divides Register X by constant 24 (Yes you could extract this with debug.getinfo and reading the line above the function.)
MyExtension:RegisterInstruction("XYZ", { "X" }, function(self)
    self:DynEmitOperand("$1/24") -- I'd like to swap this out too in favor of a safer api that you can be assured you won't want to remove later on. But it's up to you
end, { "W1" }) -- The "write" flag probably should be included in the actual argument. But I don't know enough about its purpose to give an ideal answer

So, for helping understand the above.
The only necessary things for the actual creation of an instruction is the Name(for the IDE), Operand Count, Flags, and the OpFunc(which generates the transpiled code)
For flags, they're primarily used during the HLZASM compilation (to the bytecode), the only one that affects the precompile at runtime is the Privileged flag (R0), which wraps the precompile in a check for the current page's runlevel and interrupts if not present.
The rest of this(Opname1 and 2, version, and description) is used for the generation of the E2helper docs (like here)

But since I don't necessarily have an easy way to modify them from this repo in a way that would allow me to add and remove them as the extensions are enabled and disabled (I would need to PR support for this to wire-main) their inclusion is only for future support

lua
MyExtension:RegisterInstruction("XYZ", { "X" }, function(self)
    self:DynEmitOperand("$1/24") -- I'd like to swap this out too in favor of a safer api that you can be assured you won't want to remove later on. But it's up to you

So regarding simplifying further, I could certainly make a function like the above, one that creates a dummy instruction which just calls a user provided function with args and have CPULib load the VM with a copy of the funcs, if that sounds better than expecting all addon makers to use the emit functions

@Vurv78 Check the API used here and tell me what you think of it, vs the previous one

@Vurv78 Check the API used here and tell me what you think of it, vs the previous one
It should be noted however, should #48 come to pass, these lua funcs might have global scope while the instructions themselves will still remain in the VM's env scope, but since the lua func itself isn't generated from any compilestring, it should be fine?

Yeah that should be fine. It's best this way too, I was going to say that if setfenv were to be used it'd make a transpilation api very confusing if they wanted to access globals


clang-tidy CI way too slow

Our GitHub Action that runs clang-tidy takes way too much time. Something can't be right there?

According to https://stackoverflow.com/questions/76531831/why-is-clang-tidy-in-clangd-so-much-faster-than-run-clang-tidy-itself this is normal :-/ And the alternative is to disable checks on headers or something. Not sure what to do from there though.

hm ... it takes about 2.5 minutes on my laptop, something seems off. We should at least separate it into its own dedicated job so that it runs in parallel.
The best solution would be to add validation nodes support to ninja_syntax.py and then add validation nodes for clang-tidy to configure.py - so that it runs alongside the build with ninja itself.

The last clang-tidy run took 59 minutes on one of my latest pushes! I don't think running this in parallel with validation actions will help much.
Besides, the output is too verbose and undecipherable; it already reports tons of warnings in the code that we do not care about (otherwise we would have fixed them a long time ago), and complains about really trivial stuff like the name of arguments in function signature and implementation being different.
At this point, I consider this more a nuisance than a feature and would suggest removing this step entirely from our Github CI workflows :-(

Seems there really was something wrong with run-clang-tidy / Ubuntu / our setup. I've moved clang-tidy to the fedora task and it even isn't the longest running job.
I've also colored the output which makes it a lot more readable.

Thanks a ton, that's even better!


Wikipedia: Something is wrong

Extension – Wikipedia
Author: @vimtor

Description

Error:

Steps To Reproduce

Open the Random Page command
Raycast closes, nothing happens, if you toggle Raycat you see an error screen

The current behavior
The expected behavior
Raycast version
Version: 1.29.0-alpha.16

@thomaspaulmann I've reported this before, closing because most likely a duplicate of: https://github.com/raycast/extensions/issues/828


About training GR-ConvNet on VMRD dataset

Hello!
When I trained the GR-ConvNet on VMRD dataset using the following command:
$$python train_network.py --dataset vmrd --dataset-path /data2/Datasets/VMRD_V2_fixed/ --description test_train_vmrd --use-depth 0 $$,
the best accuracy is achieved 0.13 at epoch 40, which is lower than the result reported in the paper.
Does it need any other settings to train on VMRD dataset?

Hi @KAI1179,
Thank you for your interest in our work. For your issue, we conduct experiments under seen and unseen settings for VMRD, which you can observe as three columns (Seen, Unseen, H) in Table 2. We have also specified in our repo that all LVIS splits of other datasets will be released along with Grasp-Anything. Therefore, please stay tuned for more updates.
We hope our answer can provide an explanation for your results. Should you have more questions, please feel free to ask us.
Best regards,
An Vuong.

Thanks for your timely reply.
Looking forward to your updates :-)


Removed the 'crypto' dependency

The crypto module brings a huge amount of code to the browser build and it's removal reduces the build size by 400 KiB or by 25%.
The crypto.randomBytes Generates cryptographically strong pseudorandom data. That strength is not needed since these hex strings are used only as ids/classes in the generated HTML.
This change may cause test fails for some users, but this can be fixed by stubbing Math.random.
Another option would be to generate sequential IDs:
let lastId = -1
export default function genStringId() {
  lastId += 1
  return lastId+''
}

This won't cause problems with tests but may reveal the amount of e-mails generated by some application (if used on the server side).

BundleAnalyzerPlugin for comparison. Before:

After:

I'll try to get this in 4.13.1

@3bl3gamer Can you solvle those conflict i'd like to release this next week ?

@iRyusa sorry for the delay, resolved.

Any change this can be merged soon?


Older version is installed in the created folder

Hey, the yarn.lock files have version 1.2.5 in them so you get that version installed (if using yarn) in the created site even if you'e using the latest cli.  Probably better not to commit these lock files or you have to make sure they get regenerated.  Or is this by design, possibly?
Basic:
https://github.com/nozzle/react-static/blob/815606d4835658ab55a719bf1bdf01890221c9da/examples/basic/yarn.lock#L4958
Custom Routing:
https://github.com/nozzle/react-static/blob/815606d4835658ab55a719bf1bdf01890221c9da/examples/custom-routing/yarn.lock#L4717

No definitely a mistake on my part.
On Thu, Oct 19, 2017 at 1:54 PM Steve Hall<EMAIL_ADDRESS>wrote:

Hey, the yarn.lock files have version 1.2.5 in it so you get that version
installed (if using yarn) in the created site even if you'e using the
latest cli. Probably better not to commit these lock files or you have to
make sure they get regenerated. Or is this by design, possibly?
Basic:
https://github.com/nozzle/react-static/blob/815606d4835658ab55a719bf1bdf01890221c9da/examples/basic/yarn.lock#L4958
Custom Routing:
https://github.com/nozzle/react-static/blob/815606d4835658ab55a719bf1bdf01890221c9da/examples/custom-routing/yarn.lock#L4717
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nozzle/react-static/issues/65, or mute the thread
https://github.com/notifications/unsubscribe-auth/AFUmCevPDRQlgH4z-MvC2vvuSJA0zz2sks5st6jbgaJpZM4P_xRp
.

It may be the case the latest build of react-static is not in sync with npm.

The yarn.lock files are no longer included and also ignored. Shouldn't be a problem anymore.


Build fail on Fedora Linux

Describe the bug
I am trying to build lua-language-server on Fedora Linux to use with neovim.
Following the instructions from the wiki.
Unfortunately I hit an error building bee.so: /usr/bin/ld: cannot find -lstdc++ .
I have no experience with C++, so not sure how to fix the linker or what not...
To Reproduce
docker run --rm -it fedora
dnf -y update && dnf -y groupinstall "Development Tools" && dnf -y install ninja-build gcc-c++
git clone https://github.com/sumneko/lua-language-server && cd lua-language-server && git submodule update --init --recursive
cd 3rd/luamake
compile/install.sh

Expected behavior
Compilation should succeed without errors
Screenshots
N/A
Environment (please complete the following information):
- OS: Fedora Linux 34
- Is WSL remote? N/A
- Client: neovim
Additional context
I have tried both on my local Fedora 34 computer and in a fedora:latest docker container.
Provide logs
[root@c88abb3651b7 luamake]# ./compile/install.sh
[1/3] Link    Dll build/linux/bin/bee.so
FAILED: build/linux/bin/bee.so
gcc --shared build/linux/obj/bee/lua-seri.obj build/linux/obj/bee/error.obj build/linux/obj/bee/fsevent_linux.obj build/linux/obj/bee/endpoint.obj build/linux/obj/bee/socket.obj build/linux/obj/bee/format.obj build/linux/obj/bee/os.obj build/linux/obj/bee/subprocess_posix.obj build/linux/obj/bee/file_helper.obj build/linux/obj/bee/path_helper.obj build/linux/obj/bee/lua_embed.obj build/linux/obj/bee/lua_filesystem.obj build/linux/obj/bee/lua_filewatch.obj build/linux/obj/bee/lua_platform.obj build/linux/obj/bee/lua_serialization.obj build/linux/obj/bee/lua_socket.obj build/linux/obj/bee/lua_subprocess.obj build/linux/obj/bee/lua_thread.obj build/linux/obj/bee/lua_time.obj -o build/linux/bin/bee.so -lpthread -Wl,-Bstatic -lstdc++ -Wl,-Bdynamic -static-libgcc -s
/usr/bin/ld: cannot find -lstdc++
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.

Try running
sudo dnf install libstdc++-static
It solved the problem for me.

Installing libstdc++-static did indeed fix the build failure. Thanks @jolars
I will close this and add info about the required package to the wiki.


Convert from .gif ?

preview gone wrong?

Upstream tracking issue FFMS/ffms2#210

It looks like it is fixed in the next version of FFMS2, whenever that releases.


Event organization

Project title
Event organization
Project Description
The event organization contract will have 2 entities :

Event organizer.
Attendee.
A organizer will create event and will make tickets so that attendee can buy those tickets and enjoy event

Domain

[] Solidity
[] JavaScript

Are you contributing under any open-source program ?
yes

Ya great.Start working on this . Include this in level2 folder .

can i start working on this


Pure Vanilla - Hard Lockup Moving Caravan on Worldmap

Original Title: Pure Vanilla - Hard Lockup Splitting Caravan
New Title: Pure Vanilla - Hard Lockup Moving Caravan on Worldmap
I thought it had to do with splitting the caravan but it actually might not, just move the caravan and advance time and it seems to freeze anyway.
SAVEGAME
https://drive.google.com/file/d/1RE678M4PdMpsiBBg7OlhOqU2kBPYYEk6/view?usp=sharing
SCREENSHOTS

I don't know if I'm doing something wrong or if it is just something I fixed in 1.1.20, but I can no longer reproduce this error. Please reopen bug report if it is still occurring on latest version of the mod.


Does this software work within a VM?

VMProtect has VM detection and will often not allow programs to run if it detects a virtual machine. Does your software, which is absolutely amazing regardless, still work in this specific instance? I apologize if this is a poor question, please close if you feel its not worth answering.

Yeah should work


add logic function to evaluate ans object varible in questobject

well the answer is allways correct :( , giving up moving to the score board