AVRO-2773: [C] Add decimal logical schema

AVRO-2773
What is the purpose of the change
These two commits add decimal logical schema support for C: the first commit adds the base layer and the second commit adds higher-level functions to manipulate decimal objects beyond their serialized representation.
Verifying this change
Existing tests were updated and new tests were added to exercise the new functionality.
Documentation
This introduces two new functions which are documented along with the existing functions.
For pre-existing functionality, the underlying bytes and fixed getter/setters can still be used with decimal objects.

this is an alternative to #843 where the decimal support is added to the value api instead of the deprecated datum api, and decimals are a "first class citizen" in that AVRO_DECIMAL extends the avro_type_t enum

the latest changes link libm, which should resolve the build issues occurring earlier in CI


⚠ ClamAV has degraded performance

In e06dba0, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 66 ms

Resolved: ClamAV performance has improved in efaede8.


Feat: Adding GitHub Workflow for Issues and PRs

This would allow the new contributors to get a template of raising an issue or a PR

@1010varun Please assign me this under IWOC


Get host from env or set default

Hi,
In order to get compatibility with Errbit i've added the possibility to sen on the .env file the server host.
Feel free accept or close this pull request!
Thanks

Thanks for the contribution, let me know if you need me to tag a release


Update readme from branch example

Update
I updated the readme file. Please review and accept.

Thoughts
I probably shouldn't, but okay 👍


clean up

Coverage remained the same at 96.396% when pulling 8e6fca094e3e147ef5133b3367b22ac9cc9e7462 on prod into de46f5522460b77fe498d32698bd8447980df072 on master.

Coverage remained the same at 96.396% when pulling 8e6fca094e3e147ef5133b3367b22ac9cc9e7462 on prod into de46f5522460b77fe498d32698bd8447980df072 on master.


Setup structure for component tests

integration tests do not make sense it this case, since the only dependencies we have are the library functions, component tests might be implemented

Will not be done


west: Ignore projects without path

Manifest projects enumeration can contains object without path. For
example ManifestProject instance does not have path. This patch allows
to ignore such objects.
Signed-off-by: Pavel Král<EMAIL_ADDRESS>

@mbolivar-nordic I think it is time for a new west release.

I get the hint ;). I have been planning on 0.8 in the near future. I'm waiting on the Zephyr stabilization period to start so I can write up the documentation and release notes, then do the release testing, so this will happen in September.
If that's not OK and this is an emergency, let's discuss offline.

@tejlmand While you are probably right, how do you want to be sure for future, that changes to west does not broke things again ? The current situation is that processing syntactically valid west.yml ends up with exception, not warning or so. This is super simple patch. Better safe than sorry. But its up to you.

This is super simple patch. Better safe than sorry. But its up to you.

No, if introducing this patch, then downstream users, where the manifest repo is ALSO a Zephyr module would silently be ignored without any notification.
In that case, there would be a missing Zephyr module, but no warning or failure and hence the build would proceed as normal, which could instead lead to a subtle error.
Example of a manifest project which is also a Zephyr module can be seen here (but this manifest contains a self: path setting):
https://github.com/nrfconnect/sdk-nrf/blob/master/west.yml
So in this case that a project has None as path then an error is important and build should fail.
(One can always discuss if a stack trace is the best error, but a 'None' path in this situation should lead to an error)

No, if introducing this patch, then downstream users, where the manifest repo is ALSO a Zephyr module would silently be ignored without any notification.
In that case, there would be a missing Zephyr module, but no warning or failure and hence the build would proceed as normal, which could instead lead to a subtle error later.

Agree. But then warning about missing path should be printed with advice how to provide it in west.yml.

So in the case that a project has None as path then an error is important and build should fail.
(One can always discuss if a stack trace is the best error, but a 'None' path in this situation should lead to an error)

None is kinda of NPE, it's terrible for a user experience. I've spend some hours to found, that it is actually a feature ...

So in the case that a project has None as path then an error is important and build should fail.
(One can always discuss if a stack trace is the best error, but a 'None' path in this situation should lead to an error)

None is kinda of NPE, it's terrible for a user experience. I've spend some hours to found, that it is actually a feature ...

If you can re-open and change this PR into an error message that would have helped you not wasting time, then that would be highly appreciated, and I will be happy to take in such a path.

If you can re-open and change this PR into an error message that would have helped you not wasting time, then that would be highly appreciated, and I will be happy to take in such a path.

No problem. I will open new PR because we both agreed that silently ignoring project without path is not the way to go. I'll link the new PR to this one for reference.


Display message when there's no published articles on profile page

As a user, I think there should be a message displaying when you have no articles published in case people mistake this for data not loaded.
Screenshot of current empty state:

I'll take it, thanks!

Great idea! I've assigned this to you now.


Upgrade deprecated panels

Migrate old angular panels
Checklist

[x] Update changelog in CHANGELOG.md in an end-user friendly language.

I guess you basically opened each of these with Grafana 11, then exported them and updated them on the repo?

oh, and also it seems some files were moved/renamed.

I did using grafana 10 because when I opened a few in grafana 11 I got errors :D
Yes I moved some from the aws only to shared because they are also used in CAPA. It could have been done in another PR  though :(

But main idea is open in grafana, click the individual migrate buttons save and replace datasource with default


Getting no device list on bluetooth scan

Please check all of the platforms you are having the issue on (if platform is not listed, it is not supported)

[] iOS
[X] Android
[] tvOS
[] macOS
[] PCL
UWP IS NOT SUPPORTED DURING THE BETA PERIOD - ONLY PRs ARE WELCOME FOR NOW

Version of OS(s) listed above with issue
from 4.3 to 6.0 i tried 4 devices
Version of Library
latest acr ble 2.0
Expected Behaviour
i am trying to follow given example on xamarin.android to get and connect/pair with avail devices.
here is the code sample i am trying.
using Android.App;
using Android.Widget;
using Android.OS;
using System;
using Plugin.BluetoothLE;
using Plugin.BLE;
namespace BlE_Communications
{
[Activity(Label = "BlE_Communications", MainLauncher = true, Icon = "@drawable/icon")]
public class MainActivity : Activity
{
protected override void OnCreate(Bundle bundle)
{
base.OnCreate(bundle);
SetContentView(Resource.Layout.Main);
Button btnSend = FindViewById(Resource.Id.btnSend);
btnSend.Click += onbtnSendClick;
// Set our view from the "main" layout resource
// SetContentView (Resource.Layout.Main);
}
private async void onbtnSendClick(object sender, EventArgs e)
{
Toast.MakeText(context: this, text: "scanning", duration: ToastLength.Long).Show();
//if (CrossBleAdapter.Current.CanOpenSettings())
//    CrossBleAdapter.Current.OpenSettings();
if (CrossBleAdapter.Current.CanControlAdapterState())
CrossBleAdapter.Current.SetAdapterState(true);
// discover some devices
TextView tvStatus = FindViewById(Resource.Id.textView1);
        /*the below code is giving null devices*/
        //if (CrossBleAdapter.Current.Status == AdapterStatus.PoweredOn)
        //{
        //    CrossBleAdapter.Current.Scan().Subscribe(scanResult =>
        //{
        //    tvStatus.Text += System.Environment.NewLine + scanResult.Device.Name;
        //    tvStatus.Text += System.Environment.NewLine + scanResult.AdvertisementData.IsConnectable;
        //    tvStatus.Text += System.Environment.NewLine + scanResult.Device.Uuid;
        //    tvStatus.Text += System.Environment.NewLine + scanResult.Rssi;
        //});
        //}
       /*tried this one from documentation too but still getting no device*/
        var devices = CrossBleAdapter.Current.GetPairedDevices();
        foreach (var device in devices)
        {
            tvStatus.Text = System.Environment.NewLine + device.Name;
        }

        //tvStatus.Text = "After Scan";
        // Once finding the device/scanresult you want

        //Device.WhenAnyCharacteristicDiscovered().Subscribe(async characteristic =>
        //{
        //    // read, write, or subscribe to notifications here
        //    var result = await characteristic.Read(); // use result.Data to see response
        //    await characteristic.Write(bytes);

        //    characteristic.SubscribeToNotifications(result =>
        //    {
        //        //result.Data to get at response
        //    });
        //});
    }

}

}

You can try a few things

Check your permissions in your app manifest
Keep a reference to scan observable var disposable = CrossBleAdapter.Current.Scan().Subscribe(...)
Note that the subscribe callback will fire off the main thread.  You need to dispatch back to the main thread if you want to see UI changes.

hi,
thanks for prompt response, i checked the issues with permission and its set as it should be.
can you elaborate on point 3 on how to dispatch back to main UI, i have done this on winforms but have no idea on xam.android.

You can use RunOnUiThread from your activity.
Please note that this is not a support forum.  Those types of questions should be done externally to this library in the future.

hi i tried RunOnUiThread & the disposable var, but it was of no avail. i still cannot see any device that have bluetooth on. while the in-built settings page of android shows the devices without issues.

Well - it works for me in the projects I'm working with, so please provide an end-to-end project showing the issue.

No response - closing until necessary details have been provided


[Dearmland][Obstacles][Planning]: Generating trajectories of obstacles given initial location and destination

System information

OS Platform and Distribution: Linux Ubuntu 18.04
Apollo installed from (source or binary): Source
Apollo version (3.5, 5.0, 5.5, 6.0): 5.5

Steps to reproduce the issue:
Main goal: In dreamview, I can send the initial location and destination of an adc then the planning module (while sim_control is enabled) takes care of generating the intermediate location info, speed and heading. Would it possible to do this with obstacles? Meaning, can I do something similar to what's done in dreamland, where I can define the obstacle's:

type
initial location
destination
initial speed and heading

Once the scenario is run, a bag file with all obstacles information is created with intermediate states (location, heading and speed).
I'd really appreciate your help with this!
Thanks

This is feasible, but I have a problem. You can set the initial value of the obstacle, but how does it work afterwards?
ow do we define the rules of obstacles, or we need to set some curves to drive？

@daohu527 Thank you for your response! So that's what I'm trying to figure out. How can I define rules that will dictate how the obstacles will behave?
I'm not sure how it's done in dreamland. What would you suggest?

Without considering collisions and traffic rules, you can generate trajectories through splines, and then add a simple dynamics model to simulate speed. You can also set intermediate points to simulate overtaking or lane change scenarios

If you consider collisions, then you need to deal with collisions and slow down some cars.

If you consider traffic rules, it will be more complicated, you need to add some constraints on the speed and curve.

Thank you @daohu527 for your response!
Can you direct me to what module or part of Apollo that I can modify to achieve what you mentioned in (1)?
Also, I was initially thinking about modifying the sim control code under dreamview/backend to automatically create trajectories of obstacles between an initial and destination point. would that work?

The solution is feasible, you can modify the sim control module and dreamview to achieve this. Regarding the spline curve, you can refer to qp_spline_reference_line_smoother.cc

@daohu527 I've been looking at the sim control module and more specifically sim_control_test. It seems like sim_control still requires a set of trajectories to be defined before calling PerfectControlModel.
I'm not quite sure at this point if modifying sim control alone will help me achieve my goal, which is creating trajectories of obstacles given a start and end point only.

If it generates obstacle trajectory, sim control is not work for it, it just used to mock control module.
If it is to generate obstacles, I recommend this project, you can ref it link
project

@daohu527 Thanks for referring to the software. I don't think that project will help much.
I want to get a planned_trajectory (x,y,theat, speed etc)  given a routing info (start and end location). It should be under planning, possibly reference_line_provider. is this correct?

routing info can't give you planned trajectory, the reference line don't have speed info but It can generate curves. I think you can try it.

Thanks @daohu527 any script that allows me to do that? generate a planned trajectory (speed, heading and pose) given a start and end location?

I may not know of such a script at the moment, can anyone help!


urh: 2.5.7 -> 2.6.0

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/urh/versions.
meta.description for urh is: '"Universal Radio Hacker: investigate wireless protocols like a boss"'.
meta.homepage for urh is: '"https://github.com/jopohl/urh"
Release on GitHub
Compare changes on GitHub

Checks done (click to expand)

built on NixOS
/bin/sh passed the binary check.
1 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 2.6.0 with grep in /nix/store/ngnd0gjvyqv3cv1gjv79h600rszwx6a8-urh-2.6.0
directory tree listing: https://gist.github.com/cae373d04832fa3292523abfe14edd22
du listing: https://gist.github.com/ac84902a1db9cc0f3ea88d688a2599af

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

3 total rebuild path(s)
1 package rebuild(s)
1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
urh

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ngnd0gjvyqv3cv1gjv79h600rszwx6a8-urh-2.6.0 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A urh https://github.com/r-ryantm/nixpkgs/archive/53c8af5f0212a136b9fdf93c95c5105c95b48200.tar.gz

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

cc @fpletz for testing.

@GrahamcOfBorg build urh


Name

If I were searching the package website for a graphql package and saw these search results...

jamesmacaulay/elm-graphql
pro100filipp/elm-graphql
ghivert/elm-graphql
Xerpa/elm-graphql
chrisalmeida/graphqelm
dillonkearns/graphqelm

...my familiarity with the Elm ecosystem leads me to assume the first 4 are the serious options, and the last 2 are not worth investigating. That's a shame, because you've clearly put a ton of thought into this!
The thing is, I've had one bad experience after another with packages that don't follow Elm's "give it an obvious name" guideline. Cute names seem most often to be chosen because the author is an Elm novice coming from a JS background, where there's one shared global npm namespace instead of a per-author namespace, and "branded libraries" are the norm.
Naturally, packages created by folks who are new to Elm tend to have a lot of room for improvement!
Have you considered calling this dillonkearns/elm-graphql instead? Based on my experience, I suspect that you'd see more experienced Elm users discovering the library and giving it a shot.

Please don't use a generic name, it makes it hard to tell different packages apart, since user names are not mnemonic. I can remember GraphqElm because its name has to do with GraphQL and Elm; meanwhile, your username might as well be random letters

@dillonkearns do you know if you can install an npm binary from a scoped package? something like
npm install -g @dillonkearns/elm-graphql-or-whatever-you-decide-is-best

@lukewestby yes, from reading through the docs, it looks like the rules for bin files don’t have any special behavior for unscoped packages, so it looks like you can have any name for your bin files that you choose. I don’t imagine that you could name a bin file with a path like that. But I could publish the npm package as @dillonkearns/elm-graphql and from there have it use the binary name elm-graphql, that seems like a pretty good solution!
Good point about the cli being abstracted away in package.json files. As long as the instructions are clear, people will just copy-paste them into their scripts. I like this idea, great suggestions @lukewestby and @harmboschloo 👍

I don't think there is any problem with the current name.
The desire to use "literal" names for all packages seems to be in conflict with several technical realities. Community conventions are great (and I'm not opposed to this one in principle), but conventions only make sense if they are in the context of a coherent technical environment.
As @sporto noted there is a need to facilitate migrating from one package to another. In a non-trivial app, what is the intended way for someone to migrate from @foo/elm-graphql to @bar/elm-graphql?
There is also often a need to wrap a library with application-specific logic. In the app I work on, we have a GraphQl module that wraps this library with logic for building authenticated requests using our credentials type, converting scalars to app-specific types, etc. Given that it is currently an Elm convention to not namespace modules by the name of the application (this is a convention in other ecosystems such as Elixir), the implication is that app code should use a less literal name than library code. That is strange to me.

Based on my experience, I suspect that you'd see more experienced Elm users discovering the library and giving it a shot.

This would be disappointing if true. I think more experienced developers will simply evaluate the project based on how well it helps solve their problems.

@xtian Unless I'm missing something, it seems like you're talking about module names, not package names, yeah?

Typically there is a correspondence between the two, yeah?

They're often related, but are still decoupled - and the concerns you brought up apply only to module names.
For example, if two packages happen to expose a GraphQL module, and someone wants to switch from one to the other, that sounds like a motivating use case for https://github.com/elm-lang/elm-compiler/issues/1625 - regardless of what the packages are named!

Given that it is currently an Elm convention to not namespace modules by the name of the application (this is a convention in other ecosystems such as Elixir)

We actually do this at work. For example, we have an Nri.Rollbar module which wraps the generic Rollbar module with some metadata we always like to include that's specific to our application.
I did not know that was a convention in the Elixir community!

I did not know that was a convention in the Elixir community!

Yes, for example the controller module in this Phoenix guide is namespaced with HelloWeb. That's the convention for all modules in an Elixir application.
The equivalent in Elm would be if every module in rtfeldman/elm-spa-example was namespaced with ElmSpaExample (e.g., module ElmSpaExample.Page.Article.Editor …). That would prevent any conflicts between app code and third-party modules.

...my familiarity with the Elm ecosystem leads me to assume the first 4 are the serious options, and the last 2 are not worth investigating. That's a shame, because you've clearly put a ton of thought into this!

That's a strange way of blaming elm-package search not having any useful sorting/ranking UI on the name of this package.

@itsgreggreg Attacking people (and the work they've done for you, for free) is not the best way to make a feature request. :confused:

Thanks everyone who chimed in on this topic, and thanks Richard for opening the issue!
I've made the change now with the Elm 0.19 upgrade:
dillonkearns/elm-graphql Elm package
@dillonkearns/elm-graphql npm package
See the changelog for more details.

I've recommended this library to people in conversations, and every time it just feels stupid to have to say "used to be called graphqelm, but now it's just one of the elm-graphql libraries", since I don't have a good memory for usernames.

@slikts When I recommend it to people I say "elm-graphql by Dillon Kearns." It's quicker to say, plus it explicitly credits the author.
 They're good enough for mnemonic names like graphqelm, but usernames tend to slip from memory. Even if spent the extra effort to memorize the username, the people I'm talking to wouldn't. As time passes, I'll probably forget the username before the old library name again. My memory won't be refreshed, because I don't use the language, because I don't want to be part of a playground for pet social-engineering ideas like these. It's  particularly unseemly to then make issues to pressure others to conform.

I'd just like to add that I can never find this library on the first try anymore. It isn't the first result on Google anymore (It doesn't even show up on the first page for me.), nor is it the first result on Github anymore. It is on Elm though, because the results are sorted alphabetically by username.

In a meetup the other day someone mentioned that they were using GraphQL with Elm. I asked which library and they said elm-graphql. I had to ask about the author, that didn't come naturally.
Someone that doesn't know about this policy might have just with this information and search google later and end up quite confused.

Packages are often have many contributors. Packages may change "ownership" between versions. Describing the part of the package name before the / as the "author" is often inaccurate.  Asking something like "what is the full name of the package?" Can easily result in confusion as "elm-graphql" is the full name as it is with many other packages.
Essentially this sort of naming scheme doesn't help with either:

How do I distinguish elm packages by name?
How do I determine the quality of an elm package by its name?

Many communities help with 1 by coming up with memorable, unique names for their packages and trying not to step on each-others' toes. It is not a perfect solution but can help for many things like asking questions, google searches and general conversation. For example, it would be nearly impossible to find the correct information if rather than jquery, prototype, and mootools we had ejohn/js-helpers, sstephenson/js-helpers and kamicane/js-helpers. Not only would information discovery and searching be harder but after a couple of years those names would be inaccurate as big projects are often transferred to organizations and the username would change.
2 is just impossible and I don't really see how anyone can relate purely the name of a package to the quality of it's code. That seems absurd to me.

As a side note, we know the package is an elm package, it's written in elm, it's on package.elm-lang.org. Do we really need elm- in front of every package name?

Hello everyone, I welcome this discussion, this is not a constructive place for it though. It will be much more productive and visible somewhere like discourse. If you'd like to discuss further, please open a discourse thread. To make the conversation as constructive and fruitful as possible, I would recommend framing the post(s) as something like "how do we recognize multiple contributors with the Elm community convention of literal naming?" Or "how do we make it easier to recommend libraries at meetups with literal naming?"
For this particular library, I would like to follow whatever the community convention is. I appreciate that we're all trying to make this a better experience, and I know that reasonable people can come to different conclusions about the tradeoffs. Please follow up in a different venue. Thank you!


chore(master): release 0.3.0

:robot: I have created a release beep boop
0.3.0 (2024-02-02)
Features

Add autocomplete for bazel builtins (#8) (bfca1db)
Preserve output base between restarts (fc701fb)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/cameron-martin/bazel-lsp/releases/tag/v0.3.0 :sunflower:


CZML Image Material Broken?

Greetings Cesium Folks!
As of CesiumJS 1.42, I am seeing some strange behavior with previously working Image Material rendered via CZML. I have also noticed this is occurring in the Cesium Sandcastle example below:
Sandcastle with missing Cesium logo
The polygon renders correctly and the default white texture appears. However, previous versions would asynchronously load the referenced "uri" element and overlay the image. This seems to have stopped with 1.42 based on my tests (1.41 behavior not apparent).
Here is my CZML for reference, which I believe is correct and has not changed between the previous releases of Cesium since Fall 2017:
[{"id":"document","version":"1.0"}, {"name":"data-Base_Reflectivity_L2","position":{"cartographicDegrees":[-86.5625,36.2472229004,1.0]},"ellipse":{"semiMinorAxis":299875.0,"semiMajorAxis":299875.0,"height":10.0,"outline":true,"material":{"image":{"transparent":true,"image":{"uri":"http://data.horizonwx.com/kohx/Base_Reflectivity_L2/1508163444.png"}}}}}]
I've attached screen grabs from my development environment and the sandcastle.
If I'm missing something, or if there is now a new syntax to follow for overlaying materials on polygons in CZML I'm happy to adjust.
Thanks!

Thanks for reporting this @weatherdrew.  I can reproduce this bug.  I've marked this next release since it's a regression.
@tfili is this related to your Resource changes?  Image materials work through the entity API but not through this CZML example

No problem @hpinkos - glad to help, and I appreciate the great work you guys are doing!

@hpinkos Yep. I'm looking at it now.


Support for EKS (Managed Kubernetes)?

AWS launched EKS in some regions in the last week. I suspect this is going to be a pretty in-demand service, and I heard they are launching with CloudFormation support. Is there a plan/timeline for adding this to the library?
Great lib btw 👍

EKS support was added the day of the announcement with this commit 5d2f369d7a189467cad9bb3a0c0152d0e750c76f. I was hoping to get a few more items into master before cutting a new release. I am wondering whether to include a troposphere translation of the EKS CloudFormation script. Thoughts?

Oh amazing! Sorry for not spotting - I searched through existing issues instead. I haven't yet familiarised myself with the CloudFormation implementation beyond what's here. What is the script you are referring to?

This Getting Started guide has a step that brings up the EKS Cluster VPC. The CloudFormation yaml script is here which I'm wondering whether people would want as a troposphere example.

Ahh got it - yeah I think definitely useful for beginners. My particular use-case would be adding to an existing VPC, but including a standard example would be handy.

This was released in 2.3.1 on 2018-07-01.

Closing. Note: opened #1096 to track the addition of an EKS cluster example.


Manual Course Site Creation cancel button needs gray background

This needs to be a longsight ticket or a PR into their repo to change the classes applied to that markup.


feat(CategoryTheory/Sites): 1-hypercovers

This PR defines a notion of 1-hypercovers in a category C equipped with a Grothendieck topology J. A covering of an object S : C consists of a family of maps f i : X i ⟶ S which generates a covering sieve. In the favourable case where the fibre products of X i and X j over S exist, the data of a 1-hypercover consists of the data of objects Y j which cover these fibre products. We formalize this notion without assuming that these fibre products actually exists. If F is a sheaf and E is a 1-hypercover of S, we show that F.val.obj (op S) is a multiequalizer of suitable maps F.val.obj (op (X i)) ⟶ F.val.obj (op (Y j)).

thanks!
bors r+

I have no real objections about this, but I do wonder whether you considered going for arbitrary hypercovers (e.g. defining them using simplicial coskeleta). Do you have a particular use in mind for 1-hypercovers?

I do not plan to PR an adhoc definition of 2-hypercovers! For general hypercovers, we could give a definition, but we would not be able to prove much about it until we make very significant progress on the formalization of the homotopy theory of simplicial sets.
Among the possible applications, 1-hypercovers are useful in order to describe elements in the sheafification of a presheaf. I have introduced a universe parameter w for the index types of 1-hypercovers, and I plan to use it in order to show that if X : Scheme.{u}, then even though the category of locally finite presentation etale schemes over X is a large.{u} category (not even essentially small), which should require considering sheaves with values in Type (u+1), any scheme over X is 1-hypercovered by objects in a suitable small category of affine schemes. Then, by using 1-hypercovers, the category of etale sheaves with values in Type u should be equivalent to a category of sheaves of Type u over a SmallCategory.{u}: then, we could deduce HasSheafify instance for categories of sheaves in algebraic geometry without a universe bump. (In a more remote future, etale cohomology groups could be defined in Type u.) Basically, I plan to generaliwe/refactor Sites.DenseSubsite with sharper universe bounds.


Look into using COSMOAccelerators

COSMOAccelerators

Not consistently improving the number of iterations. Maybe it really needs the safeguarding COSMO uses?


development mode generate images very slow

hi,
when I try this project, the images generate very slow in local development mode.
I am interested in the project, but have no much knowledge of it, while I run it on my laptop following your guide successfully.
so, I wonder if there is a way to speed images generating ?
thanks a lot.

Hey! I'd suggest running the project in Google Colab using the notebook from this repo [].
I use Google Colab Pro which generates 5 images in ~20 seconds.


Desupply the API

Most of the supplier methods existed when types were going to be fed by
explicit suppliers (and not by lookups that references do right now).
Whereas references are suppliers, that was only done for passing to
other java constructs easier. The plugin dev needs to always call get
themselves to terminate the callstack at the call site.
It also doesn't help that the only consistent thing regarding suppliers
were we were inconsistent which makes for a messier API. This cleans
this up.
Lastly, ItemStack and BlockSnapshot both gain Factory objects to return
their empty references.
Signed-off-by: Chris Sanders<EMAIL_ADDRESS>@dualspiral
@gabizou

If we can retain suppliers throughout, that’s be better (since DefaultedRegistryReference naturally implements it) than removing all supplier usage since it does make the various api calls a fair bit cluttered for the various places.

Closing this as discussion was made and the intent will be to go and standardize the supplier calls throughout the API.


instructions::interrupts::enable() not working properly

I reading the Rust OS Dev tutorial and have been following all the told steps. But I have encountered a problem which is most likely a bug from this crate.
In the Hardware Interrupts -> Enabling Interrupts section we are told to add the following lines:-
pub fn init() {
    gdt::init();
    interrupts::init_idt();
    unsafe { interrupts::PICS.lock().initialize() };
    x86_64::instructions::interrupts::enable();     // new
}

As told next I have also created a handler for timer interrupts. However when I run it, the program behaves in a very weird way, i.e. I am printing some text to the VGA Text Buffer but after adding this it doesn't print completely. It is not because anything is panicking and there as no exceptions also! I know this because I am not receiving any Double-Fault exceptions.
After some debugging I found that the problem is with the line x86_64::instructions::interrupts::enable();. If I comment it everything works great except of course I don't receive the interrupts. To make sure that this line was the issue I run the program about 10-15 times without this line and it worked as expected but when it is there the issue is present on 99% of the runs.
Some screenshots of the issue:-
The desired output =>

2 continuous runs and the results with the interrupts enabled.
1. Note that the last line is not printed

2. Only the first line is printed

Note:- As I have told before, I have created an handler for timer events. But, it rarely works. The program runs successfully about once in a 100 tries.

Looking at the implementation of x86_64::instructions::interrupts::enable() it just calls the STI instruction, so I don't think that implementation is incorrect.
It might be better to open this issue with the blog_os crate. I would imagine the issue is in how the blog is setting up the IDT or how the handler is implemented.

@ShardulNalegave if you open an issue under blog_os you should also include the code you are using for your timer_interrupt_handler, an incorrect implementation there could be causing your problem.

Hi! Sorry for not replying sooner.
@josephlr Yeah you are right, it looks like the problem is from my side only. As @Caduser2020 had pointed out, this could be a race condition in vga_println! and it seems it is. I removed all the vga_* code from my timer handler and it works perfectly!
The only problem now is that, I don't know how to fix this issue.... Can someone please help me with it.
@Caduser2020 the code is at https://github.com/ShardulNalegave/catalyst-os

@ShardulNalegave The issue is line 108 here. When an interrupt is triggered, the interrupt handler, here, calls the _print function, which tried to lock the global WRITER instance. However, the WRITER is already locked in _start() by println!, causing a deadlock. To fix the deadlock, the _print function, here, should run WRITER.lock().write_fmt(args).unwrap(); without interrupts. For example,
use x86_64::instructions::interrupts;
#[doc(hidden)]
pub fn _print(args: fmt::Arguments) {
    use core::fmt::Write;
    interrupts::without_interrupts(|| {
        WRITER.lock().write_fmt(args).unwrap();
    });
}

@Caduser2020 Thanks a lot! That solved the problem.


Do not allow redefinition of existing table

Given this invalid example from the TOML spec:
[fruit]
apple.color = "red"
[fruit.apple]  # INVALID

toml11 accepts the document as valid:
$ echo "[fruit]\napple.color = \"red\"\n[fruit.apple]" | check_toml_test | jq
{
  "fruit": {
    "apple": {
      "color": {
        "type": "string",
        "value": "red"
      }
    }
  }
}

Tested with commit bf2384d8da9cdd91bdc51092452e02cc982af0c7.
PS - I've submitted new tests cases to the toml-test suite for this.

Fixed in e60442c. Thank you!


Type is missing title. Warning in the studio in dev mode.

Using latest version of plugin and sanity.
I'm not sure were the problem is if it's my installation or the plugin.

+1

+1

+1

+1

+1

Ok seems like the waring now is fixed thanks to an update to Sanity Studio.
In the version 3.14.4 I'm not getting the warning anymore.
https://www.sanity.io/changelog#change-07656110-93a2-4831-bd04-6616f12bbf1a

Removes warning about missing titles for schema types (titles are automatically created based on schema type name - a title is only necessary if the automatic name is incorrect/inaccurate)


[test] Update enzyme

This is not meant to be merged.
enzyme-adapter-react-16 started wrapping updates in act which results in very weird test behavior if we're not explicitly unmounting after the test.
Without unmounting subsequent test will sometimes return wrappers that do not exist from mount:
const wrapper = mount(<List />);
assert.strictEqual(wrapper.exists(), true); // fails

Would be nice if somebody could investigate this issue. Not looking forward to rewriting every test to explicitly unmount afterEach.

@eps1lon It should be green now. I'm proposing this change:
packages/material-ui/src/test-utils/createMount.js
@@ -11,10 +11,16 @@ export default function createMount(options1 = {}) {
  window.document.body.insertBefore(attachTo, window.document.body.firstChild);

  const mountWithContext = function mountWithContext(node, options2 = {}) {
+   const { disableUnnmount = false, ...other2 } = options2;

+   if (!disableUnnmount) {
+     ReactDOM.unmountComponentAtNode(attachTo);
+   }

    return mount(node, {
      attachTo,
      ...other1,
-     ...options2,
+     ...other2,
    });
  };


Web.config environment variables missing in Azure

TL;DR
Some environment variables present in the web.config (like ROOTDIR) generated by PTVS are missing in Azure. This causes a deployment to "fail" because even tho the code is deployed, the site doesn't run. Replacing the variables with hardcoded values solves the issue.
Am I supposed to have those variables set in my Web App automagically by Azure or am I supposed to treat those variables as placeholders and edit my web.config with the appropriate values?

Howdy,
I had an issue happening to me every time I tried to use PTVS and Azure, so I just downloaded the latest version both Visual Studio and PTVS,  did a File->New Django project and published it to an Azure Web App.
This is the web.config generated by PTVS:
<?xml version="1.0"?>
<!-- Generated web.config for Microsoft Azure. Remove this comment to prevent
     modifications being overwritten when publishing the project.
-->
<configuration>
  <system.diagnostics>
    <trace>
      <listeners>
        <add type="Microsoft.WindowsAzure.Diagnostics.DiagnosticMonitorTraceListener, Microsoft.WindowsAzure.Diagnostics, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35" name="AzureDiagnostics">
          <filter type="" />
        </add>
      </listeners>
    </trace>
  </system.diagnostics>
  <appSettings>
    <add key="WSGI_ALT_VIRTUALENV_HANDLER" value="django.core.wsgi.get_wsgi_application()" />
    <add key="WSGI_ALT_VIRTUALENV_ACTIVATE_THIS" value="%ROOTDIR%\env\Scripts\python.exe" />
    <add key="WSGI_HANDLER" value="ptvs_virtualenv_proxy.get_venv_handler()" />
    <add key="PYTHONPATH" value="%ROOTDIR%" />
    <add key="DJANGO_SETTINGS_MODULE" value="djangotest.settings" />
  </appSettings>
  <system.web>
    <compilation debug="true" targetFramework="4.0" />
  </system.web>
  <system.webServer>
    <modules runAllManagedModulesForAllRequests="true" />
    <handlers>
      <add name="Python FastCGI" path="handler.fcgi" verb="*" modules="FastCgiModule" scriptProcessor="%INTERPRETERPATH%|%WFASTCGIPATH%" resourceType="Unspecified" requireAccess="Script" />
    </handlers>
    <rewrite>
      <rules>
        <rule name="Static Files" stopProcessing="true">
          <conditions>
            <add input="true" pattern="false" />
          </conditions>
        </rule>
        <rule name="Configure Python" stopProcessing="true">
          <match url="(.*)" ignoreCase="false" />
          <conditions>
            <add input="{REQUEST_URI}" pattern="^/static/.*" ignoreCase="true" negate="true" />
          </conditions>
          <action type="Rewrite" url="handler.fcgi/{R:1}" appendQueryString="true" />
        </rule>
      </rules>
    </rewrite>
  </system.webServer>
</configuration>

As you can see, this config file "depends" on the presence of some variables to work, namely ROOTDIR, INTERPRETERPATH and WFASTCGIPATH.
Those variables don't seem to be present on my Azure Web App, even after I properly configured the site to use python 3.4, but if I replace those variables with hardcoded values (ROOTDIR with D:\home\site\wwwroot\ and so on) then the Web App works beautifully.
Tested with both python 2.7, 3.4 and 3.5 (using extensions) and it's the same thing no matter which python version: no variables present.
Am I supposed to have those variables set in my Web App automagically by Azure or am I supposed to treat those variables as placeholders and edit my web.config with the appropriate values?

Did you publish with right-click on the project node and select Publish?  If not, that would explain it, as other methods of publishing will not replace those %% variables.  You'll need to replace them in web.config, and remove the header at the top that makes the file re-generate when you build.

@huguesv Nope, I used git publishing. I knew about removing the hesder, but I didn't see any documentation about those variables, so I just assumed they would work automagically.

Also see this post https://blogs.msdn.microsoft.com/pythonengineering/2016/08/04/upgrading-python-on-azure-app-service/
It has some sample web.configs for App Service that are much shorter. The code we generate is far more complicated than it needs to be (if you know how to edit it manually, that is :) ).

@zooba yep, that's what I used to get python 3.5 working, thanks for the article!
My suggestion to you guys is to remove the overly complicated web.config in favor of a simpler version that "just works" without needing to go thru the VS publish workflow.
I managed to figure things out by myself, but I'm sure other will expect things to just work with git publishing, dropbox, ftp and so on, since that's what they expect coming from an ASP.NET web app.

We already have issue #1684 to fix a genuine bug in the template, so I'll add a note there and close this. Thanks for the feedback!


Local dev vscode

Changes generally seem good to me. Can we get someone who uses vscode to test this?

@Bobbins228 or @VanillaSpoon have ye used this with vscode?

@anishasthana Can i get an lgtm please?


ADOT Logzio exporter support

Logz.io has verified logzio exporter support using the ADOT collector v0.12.0.
sample usage:
...
exporters:
  logzio:
    account_token: <<LOGZIO_TOKEN>>
    region: <<LOGZIO_REGION>>
...

We conducted performance tests as described here
Here are the results:
100 tps:
{"testcase":"logzio_exporter_trace_mock","instanceType":"m5.2xlarge","receivers":["otlp"],"processors":["batch"],"exporters":["logzio"],"dataType":"otlp","dataMode":"trace","dataRate":100,"avgCpu":0.05555673328184996,"avgMem":59.660970666666664,"commitId":"dummy_commit","collectionPeriod":10,"testingAmi":"soaking_linux"}

1000 tps:
{"testcase":"logzio_exporter_trace_mock","instanceType":"m5.2xlarge","receivers":["otlp"],"processors":["batch"],"exporters":["logzio"],"dataType":"otlp","dataMode":"trace","dataRate":1000,"avgCpu":0.0,"avgMem":0.0,"commitId":"dummy_commit","collectionPeriod":10,"testingAmi":"soaking_linux"}

5000 tps:
{"testcase":"logzio_exporter_trace_mock","instanceType":"m5.2xlarge","receivers":["otlp"],"processors":["batch"],"exporters":["logzio"],"dataType":"otlp","dataMode":"trace","dataRate":5000,"avgCpu":0.04666626908009504,"avgMem":60.59281066666667,"commitId":"dummy_commit","collectionPeriod":10,"testingAmi":"soaking_linux"}

There are newer releases of upstream collector and contrib (v35) which might have breaking changes. Please rerun your tests with these weekly releases and publish your results per guidance here. We expect to have another release v36 (mid next week) which we aim to align with the stable release of tracing components. Please rerun tests for v36 version as well. We will notify you when v36 is ready for testing.

@mraditya We Tested with the v0.36.0 collector version, and its working well.
Here are the performance tests results with our real endpoint:
100 tps:
{"testcase":"logzio_exporter_trace_mock","instanceType":"m5.2xlarge","receivers":["otlp"],"processors":["batch"],"exporters":["logzio"],"dataType":"otlp","dataMode":"trace","dataRate":100,"avgCpu":2.8309728032523056,"avgMem":87.817728,"commitId":"dummy_commit","collectionPeriod":10,"testingAmi":"soaking_linux"}

1000 tps:
{"testcase":"logzio_exporter_trace_mock","instanceType":"m5.2xlarge","receivers":["otlp"],"processors":["batch"],"exporters":["logzio"],"dataType":"otlp","dataMode":"trace","dataRate":1000,"avgCpu":26.668528808717696,"avgMem":91.32003413333334,"commitId":"dummy_commit","collectionPeriod":10,"testingAmi":"soaking_linux"}

5000 tps:
{"testcase":"logzio_exporter_trace_mock","instanceType":"m5.2xlarge","receivers":["otlp"],"processors":["batch"],"exporters":["logzio"],"dataType":"otlp","dataMode":"trace","dataRate":5000,"avgCpu":118.58227289186553,"avgMem":90.32933546666666,"commitId":"dummy_commit","collectionPeriod":10,"testingAmi":"soaking_linux"}

Closing this issue as the expected results were submitted. Please reopen the issue for any questions/concerns


Retry HTTP request on 501 response

Python HTTP Server module returns 501 status code when request is sent from chill. The code was not being handled checkHostStatus function.
A new function shouldRetry is added which checks 501 status code with additional previous conditions.

Codecov Report

Merging #40 into master will decrease coverage by 0.02%.
The diff coverage is 80%.

@@            Coverage Diff             @@
##           master      #40      +/-   ##
==========================================
- Coverage   83.65%   83.63%   -0.03%
==========================================
  Files          18       18
  Lines         875      880       +5
  Branches      125      126       +1
==========================================
+ Hits          732      736       +4
- Misses        143      144       +1

Impacted Files
Coverage Δ

src/services/status.js
83.87% <80%> (-0.34%)
:arrow_down:

Continue to review full report at Codecov.

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


feat: add source line and col for tokens

I would like to have a possibility to get the start and end line and col of a token in the original document.

It's technically impossible to have cols for current implementation. Please, take a look into past issues, this was discussed several times.


home-assistant port doesn't do anything unless config is set

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

...
...
...

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

whoops, opened duplicate accidentally


[Flow] Add TensorReshapeOp canonicalization

Canonicalize flow.tensor.reshape -> tensor collapse/expand -> flow.tensor.reshape where the first flow.tensor.reshape only converts from static to dynamic dims and the second converts back.
For example:
%0 = flow.tensor.reshape %arg0: tensor<4x1x8192xf16> -> tensor<?x?x8192xf16>{%c4, %c1}
%expanded_0 = tensor.expand_shape %0 [[0], [1], [2, 3]] output_shape [%c4, %c1, 256, 32] : tensor<?x?x8192xf16> into tensor<?x?x256x32xf16>
%1 = flow.tensor.reshape %expanded_0 : tensor<?x?x256x32xf16>{%c4, %c1} -> tensor<4x1x256x32xf16>

// transformed to...

%expanded_0 = tensor.expand_shape %0 [[0], [1], [2, 3]] output_shape [4, 1, 256, 32] : tensor<4x1x8192xf16> into tensor<4x1x256x32xf16>

%0 = flow.tensor.reshape %arg0: tensor<4x1x256x32xf16> -> tensor<?x?x256x32xf16>{%c4, %c1}
%collapsed= tensor.collapse_shape %0 [[0], [1], [2, 3]] : tensor<?x?x256x32xf16> into tensor<?x?x8192xf16>
%1 = flow.tensor.reshape %collapsed: tensor<?x?x8192xf16>{%c4, %c1} -> tensor<4x1x8192xf16>

// transformed to...

%collapsed= tensor.collapse_shape %0 [[0], [1], [2, 3]] : tensor<4x1x256x32xf16> into tensor<4x1x8192xf16>

I wonder if we can do shape inference for all these ops. After we fold the tensor.cast chain away, they become static shapes. This is what we've done for linalg ops.
E.g.,
  %0 = flow.tensor.reshape %arg0: tensor<4x1x8192xf16> -> tensor<?x?x8192xf16>{%c4, %c1}
  %expanded_0 = tensor.expand_shape %0 [[0], [1], [2, 3]] output_shape [%c4, %c1, 256, 32] : tensor<?x?x8192xf16> into tensor<?x?x256x32xf16>
  %1 = flow.tensor.reshape %expanded_0 : tensor<?x?x256x32xf16>{%c4, %c1} -> tensor<4x1x256x32xf16>

For the tensor.expand_shape op, we can infer the output shape because %c4 and %c1 are constants. So it becomes:
%cast_0 = tensor.cast %0 : tensor<?x?x8192xf16> to tensor<4x1x8192x32>
%expanded_0 = tensor.expand_shape %cast_0 [[0], [1], [2, 3]] output_shape [4, 1, 256, 32] : tensor<4x1x8192xf16> into tensor<4x1x256x32xf16>
%cast_1 = tensor.cast %expanded_0 : tensor<4x1x256x32xf16> to tensor<?x?x256x32>

Same for the flow.tensor.reshape, it becomes:
%1 = flow.tensor.reshape %expanded_0 : tensor<?x?x256x32xf16>{%c4, %c1} -> tensor<4x1x256x32xf16>

I wonder if we can do shape inference for all these ops. After we fold the tensor.cast chain away, they become static shapes. This is what we've done for linalg ops.

Do you know where this is being done for linalg ops?

Here is the implementation for LinalgOps: https://github.com/llvm/llvm-project/blob/99c8557c175e88ff1c338c4c29e3a4d63c5a46cb/mlir/lib/Dialect/Linalg/IR/LinalgOps.cpp#L2589-L2595
Here is the implementation for tensor.pack ops: https://github.com/llvm/llvm-project/blob/99c8557c175e88ff1c338c4c29e3a4d63c5a46cb/mlir/lib/Dialect/Tensor/IR/TensorOps.cpp#L4324-L4355

I wonder if we can do shape inference for all these ops. After we fold the tensor.cast chain away, they become static shapes. This is what we've done for linalg ops.

Do you know where this is being done for linalg ops?

Here is the implementation for LinalgOps<EMAIL_ADDRESS>Here is the implementation for tensor.pack ops<EMAIL_ADDRESS>
Given that tensor.cast ops get converted to flow.tensor.reshape ops, should this be an upstream canonicalization? Or is there a reason this isn't being done

Given that tensor.cast ops get converted to flow.tensor.reshape ops and this is done for linalg.generic ops as well as tensor.pack ops, should this be an upstream canonicalization? Or is there a reason this isn't being done.

Do you mean that if we should add a shape inference pattern to tensor.expand_shape op's canonicalization pattern? Yes, I think so.
If I read it correctly, it was tensor.cast -> expand_shape -> tensor.case and it becomes flow.tensor.reshape -> expand_shape -> flow.tensor_reshape, right? Then if we have the shape inference pattern for tensor.expand_shape, the tensor.cast chain will be folded away. Then it becomes a single expand_shape op. If this is the case, then yes.

For the other example, I don't have enough context. We could infer some dimensions for the collapse_shape op for sure. But the generated IR is not what you have in the PR. The second dimension can't be inferred without implementing the shape inference for flow.tensor.reshape op.
util.func public @canonicalizeReshapeCollapse(%arg0: tensor<4x1x256x32xf16>) -> tensor<4x1x8192xf16> {
  %c1 = arith.constant 1 : index
  %c4 = arith.constant 4 : index
  %0 = flow.tensor.reshape %arg0: tensor<4x1x256x32xf16> -> tensor<?x?x256x32xf16>{%c4, %c1}
  %expanded_0 = tensor.collapse_shape %0 [[0], [1], [2, 3]] : tensor<?x?x256x32xf16> into tensor<?x?x8192xf16>
  %1 = flow.tensor.reshape %expanded_0 : tensor<?x?x8192xf16>{%c4, %c1} -> tensor<4x1x8192xf16>
  util.return %1 : tensor<4x1x8192xf16>
}

If I read it correctly, it was tensor.cast -> expand_shape -> tensor.case and it becomes flow.tensor.reshape -> expand_shape -> flow.tensor_reshape, right? Then if we have the shape inference pattern for tensor.expand_shape, the tensor.cast chain will be folded away. Then it becomes a single expand_shape op. If this is the case, then yes.

Yes

For the other example, I don't have enough context. We could infer some dimensions for the collapse_shape op for sure. But the generated IR is not what you have in the PR. The second dimension can't be inferred without implementing the shape inference for flow.tensor.reshape op.

I see your point, is there a reason why flow.tensor.reshape doesnt implement something like ReifyRankedShapedTypeInterface, then the collapse_shape could query the interface for constant values to reify.

I see your point, is there a reason why flow.tensor.reshape doesnt implement something like ReifyRankedShapedTypeInterface, then the collapse_shape could query the interface for constant values to reify.

I don't know. I think it's just because we never have the needs, or the interface did not exist when we had the ops. The shape inference of pack ops is implemented few months ago; we implemented it because we had the needs. It is even not mature enough now.
I think we do miss some interface implementations for flow ops. E.g., I implemented an interface method for flow.dispatch.tensor.load/store half of year ago.
https://github.com/iree-org/iree/blob/main/compiler/src/iree/compiler/ExternalInterfaces/FlowExternalModels.cpp

We generally should not be mixing flow ops with non-flow ops, and flow doesn't need ReifyRankedShapedTypeInterface (and shouldn't - that interface is really garbage heavy). I'm still skeptical of any code that's using both tensor dialect and flow tensor ops as that indicates a bug in the layering: we accept tensor ops and produce flow ops, and shouldn't be trying to cross the streams.

I'm still skeptical of any code that's using both tensor dialect and flow tensor ops as that indicates a bug in the layering: we accept tensor ops and produce flow ops, and shouldn't be trying to cross the streams.

Fair point, the problem is that https://github.com/iree-org/iree/pull/18351 causes all tensor.casts to be converted to flow.tensor.reshape ops as early as global optimization and these cast-like flow ops get in the way of DispatchCreation's reshape propagation. Would the solution be to treat these ops as opaque during DispatchCreation (which I think was the goal of the linked PR as it was preventing tensor.cast ops from being cloned into dispatches), and try to address the source of the tensor.cast ops earlier?

I think what's happened over time in dispatch creation with partial conversion in various steps is not great (I understand and can sympathize with how it got there, but it's a bad place to be for these kind of reasons :). The flow ops are only intended for the host and by having them prior to dispatch region formation (which is creating code for the device) we will run into situations like this frequently. We never want to be in the situation where we are reconverting (tensor->flow->tensor) for dispatch region formation so the only path that makes sense to me is making dispatch region formation only convert to flow after it does its formation (as was originally the case). If there are ops needed prior to that which behave more like tensor than flow we should create a tensor_ext and put them there. I think flow.tensor.reshape was chosen because it does something different than the upstream ops and not because it was the correct op to use. If the issue (which I very much suspect) was that upstream is a pain and changing things is impossible then making our own tensor_ext.cast that does what we want is the path forward. Then we can implement the ReifyShapeMumble stuff, fold aggressively knowing that we're only dealing with tensor/tensor_ext/linalg ops, and treat all flow ops as blocking for dispatch region formation.

Does adding shape inference to expand/collpase_shape ops' canonicalization patterns fix your issue?

@benvanik and @hanhanW, I just talked with Mahesh. Adding a canonicalizer to expand/collapse shape makes the most sense, as hanhan originally suggested. Then there would be no reason to have to deal with both Flow and Tensor. Additionally, I'll look at rolling back https://github.com/iree-org/iree/pull/18351 (issue: https://github.com/iree-org/iree/issues/18229) to stop early conversion of tensor.cast ops and check what happens to the original issue.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-yml-archive-non-versioning-archive/pull/266 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-yml-archive-non-versioning-archive.git

Docs Build status updates of commit 1cfff4b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/TOC.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-3.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-3.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


More flexibility with GridCol

Currently GridCol supports flags for 1/4, 1/3, 1/2 and 2/3 width columns.
By default a column is 100% wide if a width flag is not provided.  Therefore, as there is not a flag to support it, it is not possible to make a 3/4 width column.  It is therefore suggested that we should add support for a columnThreeQuarters flag.
Additionally there is no "auto" width column to make use of the remaining flex area in a GridRow.  To provide this we could change the default column width be auto with flex: 1 set, and have the explicit widths set flex: 0.  (This change would arguably negate the need for an explicit columnThreeQuarters.)  Alternatively we could provide an explicit columnAuto flag to set width: auto; flex: 1;.
It is also not possible to do columns of 1/6th or 5/6th (both of which would be useful in our application).
Adding support for columnOneSixth and columnFiveSixths would also be cool, but as those are a less common requirement and may not form part of the main GDS styling options we could instead add support for those in our other component library.

I was hesitant to include any kind of grid in govuk-react.
The purpose of the govuk-react grid is to:

provide any grid support needed internally by components
mirror what is offered by govuk-frontend (or previous projects)
provide a grid that is useful enough for examples

It is expected that a parent project can choose to use their own grid system and these components could live within it.
I don't think we should be going down the route of building a feature rich grid system, when there are existing React grid systems that we could adopt instead.
That said, small changes like this aren't the end of the world if the general feeling is they would be useful.

Related, previous decision on this:
https://github.com/UKHomeOffice/govuk-react/issues/61#issuecomment-368578006

My vote would be to review existing grid systems and recommend one (or several) in the readme.

https://github.com/emotion-js/grid-emotion
=>
https://jxnblk.com/grid-styled/

We've discussed the requirement for having columnOneSixth and columnFiveSixths concluding that it is probably not required for the project as the UI design is likely to change and no longer require these.
I've implemented the flex-grow adjustment, and any gridCol that doesn't have one of the designated properties will expand to fill with auto width.
I personally like the change and also agree that the grid component should only facilitate the layouts supported by govuk-frontend.


+[NSMethodSignature signatureWithObjCTypes] ignores calloc return value

+[NSMethodSignature signatureWithObjCTypes] does not check the return value of calloc()
Whilst EbrCalloc() is #defined to calloc(), it would be cleaner to use one or the other consistently. Also consider whether to use C runtime malloc or LocalAlloc().

This has been fixed for a while now, closing the issue.


Add libvips version number to shared library SONAME and filename

This should help improve support for multiple versions of sharp that use differing versions of libvips running within the same process by ensuring dlopen accesses the relevant shared library.
Before:
lrwxrwxrwx 1 root root       17 Oct  8 15:05 libvips-cpp.so -> libvips-cpp.so.42
lrwxrwxrwx 1 root root       22 Oct  8 15:05 libvips-cpp.so.42 -> libvips-cpp.so.42.17.5
-rwxr-xr-x 1 root root 16313040 Oct  8 15:05 libvips-cpp.so.42.17.5

-rwxr-xr-x   1 runner  staff  18178880 Oct  8 15:13 libvips-cpp.42.dylib
lrwxr-xr-x   1 runner  staff        20 Oct  8 15:13 libvips-cpp.dylib -> libvips-cpp.42.dylib

After:
lrwxrwxrwx 1 root root       21 Oct  8 18:18 libvips-cpp.so -> libvips-cpp.so.8.15.5
-rwxr-xr-x 1 root root 16313040 Oct  8 18:18 libvips-cpp.so.8.15.5

-rwxr-xr-x   1 runner  staff  18178880 Oct  8 18:26 libvips-cpp.8.15.5.dylib
lrwxr-xr-x   1 runner  staff        24 Oct  8 18:26 libvips-cpp.dylib -> libvips-cpp.8.15.5.dylib

Relates to https://github.com/lovell/sharp/issues/4095

Thanks Kleis, I agree we should not apply this to the Windows builds.
(For sharp the C++ DLL is built/named via gyp.)


setComponets problem

Hi it is me one more time can you help me with this issue ?
exports['fivem-appearance']:setPedAppearance(PlayerPedId(), {texture=0,drawable=0,component_id=0},{texture=0,drawable=0,component_id=1},{texture=0,drawable=0,component_id=2},{texture=0,drawable=15,component_id=3},{texture=0,drawable=14,component_id=4},{texture=0,drawable=0,component_id=5},{texture=0,drawable=5,component_id=6},{texture=0,drawable=0,component_id=7},{texture=0,drawable=15,component_id=8},{texture=0,drawable=0,component_id=9},{texture=0,drawable=0,component_id=10},{texture=0,drawable=91,component_id=11})
I want to use this export but noting is changing with character what can I do ?

Hey @s0u007, the function expects only two parameters, the ped id and the PedAppearance object that must include all these keys:

model: string;
components: PedComponent[];
props: PedProp[];
headBlend: PedHeadBlend;
faceFeatures: PedFaceFeatures;
headOverlays: PedHeadOverlays;
hair: PedHair;
eyeColor: number;
tattoos: TattooList;

You need to change your seconds parameter and fill with that above.


feat(cloud): allow Number and Boolean custom properties

related to https://github.com/camunda/camunda-modeler/issues/3622
Try it out with the "Number and Boolean" example template in the npm start preview environment.

Persist Number and boolean values as FEEL expressions if feel: optional or feel: static is set in the template
We only show the FEEL editor if the value in the XML is not a primitive number/boolean

Other Refactorings

moved custom Property Components from CustomProperties.js into separate files

I think it would make sense to also implement the FEEL expression shortcut that we support for text fields, i.e. = should convert the number to a FEEL expression if allowed.

I think it would make sense to also implement the FEEL expression shortcut that we support for text fields, i.e. = should convert the number to a FEEL expression if allowed.

I think that makes sense, but is not directly related to the element template feature. I created a follow-up issue in the properties-panel repo: https://github.com/bpmn-io/properties-panel/issues/346


You can find the actual commit history here.
Do I know why the source was hidden? No, I don't.
Was it done because this is a malware? Probably, but I'm nowhere good enough in C to know for sure.
But really, I can't think of any other reasons why you'd want to (shamefully) hide the entire commit history.

that's not a try to hide the commits history, these commits are generated by a bash script to make checks on the code, but it left a lot of useless commits in the history. If you think this repo contains bad software you can read the source code or put it on a virus scanner.
sincerely, usbe


Refactor createdisk-library.sh to make it closer to the one in the podman branch

This PR reworks the createdisk-library.sh code in snc's master branch.
It should not cause any functional changes.
However, this will get the master branch code closer to the one in the podman branch.
The corresponding changes for the podman branch can be seen in https://github.com/cfergeau/snc/tree/podman , I'll file a PR for these later.

@cfergeau Is it ready for review or you are going to make more changes on top of this?

This set of changes is ready for review. More changes will be needed, but I think these ones are good enough on their own.

/retest

/retest

/retest

/retest


getDiscussionsByVotes (and by other methods like Cashout) not working

Expected behavior
A returning of a list of posts, maximum of 100, in the form of JSON objects, with all their attributes such as author, active-votes etc
Actual behavior
An error reading:
Error: Assert Exception:_tags_api: tags_api_plugin not enabled.
at new e (steem.min.js:4)
at steem.min.js:4 undefined
How to reproduce
type this into a JS console with steem allready present
steem.api.getDiscussionsByVotes({tag: "givexp", limit: 100}, function(a, b){console.log(a,b)})
Environment information
I am using a XAMPP localhost server, Windows 8.1 and I imported steemjs with

This is not a steem-js issue. The RPC node you are using does not have these plugins enabled. This is not a bug. The RPC node returns the expected result here.

wait so which RPC node does use the plugins and how do I switch nodes?

I don't think any node has it enabled at the moment. If you want to use this the best thing would be to setup your own RPC node I guess.


Streamline & clearly define our feedback loop

When to use the GitHub issues, the community Slack, the support email, Twitter, LinkedIn, the forum (GitHub Discussions or in the future, Discourse), private messages...
Once it's decided, we can update the contact page on the website https://github.com/meilisearch/devrel/issues/21#issuecomment-752489322 and move with the Discourse transition #21

blocked by #21

blocked by #21

Duplicate of #127

Duplicate of #127

process needs to be created. may require assistance from @laurajwilkinson

@ferdi05 Happy to help. I suggest starting by mapping all the comms channels that DevRel currently have, then noting the use case for each. This will help us identify any areas where we could remove or streamline channels, as well as stating clearly the audience for each, and the type of content (or interaction) to be published there. Let's discuss further once you have this mapped out (and don't hesitate to contact me if you'd like help while carrying this out).

thanks for your answer @laurajwilkinson . I'd be happy to proceed this way.
I will reach you when the mapping is done.

@laurajwilkinson you can have a look at #331

Thanks Ferdinand. The communication channels mapping looks to me to be a list of channels and use cases for each, rather than starting with the audiences and how to reach them (maybe I have misunderstood your intention, please say if so). If you're seeking to minimize or make more efficient your use of a large number of channels, this is my suggestion of how to start, so that you end up with the smallest possible number of channels necessary to serve each audience.
Just wondering also where Stack Overflow and Hacker News fit it - I did a quick search for Meili on SO and HN but no-one seems to be answering consistently from Meili. Does this fall into your remit, or perhaps that of one of the dev teams? Please pass this on if so.
What I've understood from the title of this issue "Streamline & clearly define our feedback loop" and your mention of  "the channel(s) that we will use for support and improving docs, knowledge base" mentioned in issue 21 is that you're seeking (1) define the channels we use for support, and (2) combine feedback from across our comms channels to improve our Meili documentation. If this understanding is wrong or incomplete, please could you restate and describe your mission?

Thanks @ferdi05 . I'll start by restating the main themes here for clarity:

define the channels we use for support
find a way for efficiently extracting user-generated info to push it to various teams at MeiliSearch
create some guidelines for using each channel at MeiliSearch
combine feedback from across our comms channels to improve our Meili documentation.

Here are my suggestions for your next steps:

start a DevRel handbook section in Notion (there is already some content in Notion but it's scattered across different sections and it's not clear which parts are current or up-to-date). This will be your internal documentation site for the actions that follow, so that everyone at Meili can access the information.
define the channels we use for support. Make this one of your pages in the DevRel Handbook. You've stated that for now, you're not including Stack Overflow, Hacker News, and Reddit as communication channels as we're not yet using them actively enough. But they need to stay on our comms channel list (with a note to say we're not yet actively using them) so that they stay on our horizon and in readiness for the day we want to use them more actively.
find a way for efficiently extracting user-generated info to push it to various teams at MeiliSearch. For each channel, start with the stats each system can provide, such as Slack Analytics. It won't be very detailed, but it's a useful measure of volume. Next, do a weekly summary of what topics users were asking about. If possible, add a subject tag to help with categorising. Put all this information in a new page of your DevRel handbook. Finally, for each Heartbeat update, include the link to the DevRel handbook page, and highlight 3-5 interesting or persistent topics that have arisen. (An activity that I will be encouraging us all to do soon is information mapping across Meili, to document who needs to know what and when. Your DevRel user summaries will be a great addition to this).
create some guidelines for using each channel at MeiliSearch (maybe have a quick version for everyone at MeiliSearch and a longer version for the DevRel team or anyone at MeiliSearch that actively uses these channels), that'll be great. For the guidelines, it's essential to write only one version, otherwise you'll have extra work to do to keep multiple versions synchronised. Make this guide a new page of your DevRel handbook. To achieve the 'quick' version, you could have a list of bullet points where the first sentence of each is the tl;dr, and the rest of the paragraph is the more detailed version.
combine feedback from across our comms channels to improve our Meili documentation. The key issue here is being able to reuse your stats from point 2 above. Whenever you spot that >1 person is asking about the same subject, (a) the answer should be in the Meili documentation, and (b) the answer should be discoverable using the words that the user used to describe their issue. Following this logic, you will discover (i) new subjects that are not yet in the docs and need to be flagged to the relevant team for addition, (ii) topics documented but not well understood, where the docs need to be improved, and possibly (iii) topics documented but where the information is out of date or incomplete, in which case the information needs to be updated.

This can seem like a lot to do at the start, but once you have your process up and running, it should get easier. Also, as colleagues learn what you are doing, they can help with different parts of the process. Don't hesitate to schedule a call if you'd like to chat anything through in between our exchanges here.


Dex issue with mockk for instrumentation test environment

I have a use case with using Kotlin classes in my UI tests. To mock them I have opted with mockk, because of the class finalization that mockk gracefully solves.
The problem is that it lacks some setup. I am facing dex issue. I do suspect that it is connected to the same problem mockito library had. It was solved by LinkedIn and their dexmaker solution. Is there any way we can run mockk on the emulator or real device dex environment?
Caused by: java.lang.ClassNotFoundException: Didn't find class "java.lang.instrument.ClassFileTransformer" on path: DexPathList[[zip file "/system/framework/android.test.runner.jar", zip file "/system/framework/android.test.mock.jar"],nativeLibraryDirectories=[/data/app/my.app.test-35h1VdSJ4oyoucfymSsugg==/lib/arm64, /data/app/my.app.staging.debug-7njk-OasH4iMH8Dkfhr-4A==/lib/arm64, /data/app/my.app.test-35h1VdSJ4oyoucfymSsugg==/base.apk!/lib/arm64-v8a, /data/app/my.app.staging.debug-7njk-OasH4iMH8Dkfhr-4A==/base.apk!/lib/arm64-v8a, /system/lib64, /vendor/lib64]]
at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:125)
at java.lang.ClassLoader.loadClass(ClassLoader.java:379)
at java.lang.ClassLoader.loadClass(ClassLoader.java:312)

This is on my todo list, but requires really sufficient effort. Thanks for the link, I wasnt aware it is solved for mockito. Will check it later

@oleksiyp Would be really nice to see support for Android instrumented unit tests. I had a quick look into how mockito does this in the latest version. In version 2.1 and above you use a different build of mockito in androidTest mockito-android , not mockito-core. I think mockito uses byte buddy, but for the android version it use net.bytebuddy:byte-buddy-android. I think you use byte buddy too. So it may simply be a case of swapping out the version of the byte buddy lib that you use so it generates Dex bytecode instead. You could do this with build flavors.

hm, that's interesting, especially if it is just lib swap

So I've checked net.bytebuddy:byte-buddy-android and how mockito use it. It's pretty simple subclass instrumentation which doesn't allow to mock final functions and other non-trivial stuff.
I am looking towards more sophisticated solution with https://github.com/linkedin/dexmaker, it supports inlining i.e. can mock inplace and even have support for static methods for mockito as extension.

Ah ok, fair enough. I can see that having support for mocking final functions in Kotlin is pretty important.  Good luck with the dexmaker approach. Having support for Android instrumented unit tests would be awesome.

Android instrumentation will be very soon :-) after this weekend most probably. After realeasing I'll need to stabilize for some time. So any testing and reporting is very welcome.


Question about warm starting

Hello!
I appreciate your efforts in maintaining this nice repo.
I have a quick question about the warm starting of the optimizer.
Can I just set variables with the numbers I want to initialize as you do in here?
Or should I call extra method such as SetOption("warm_start_init_point", "yes"); ?

Hi! It works without the option, although IPOPT might do some smarter tricks when you additionally set that option, I haven't experimented with that yet.
Generally I've found it's quite difficult to warm-start interior point methods like IPOPT, because of the way they solve the problem: The initial variables are often changed a lot to move into the center of the constraints during the first iteration. SQP methods, like SNOPT, might be a better choice if you have trustworthy information of the initial values (like in Model-Predictive-Control, where the initial values can be the solution of the previous solve).

Hi! It works without the option, although IPOPT might do some smarter tricks when you additionally set that option, I haven't experimented with that yet.
Generally I've found it's quite difficult to warm-start interior point methods like IPOPT, because of the way they solve the problem: The initial variables are often changed a lot to move into the center of the constraints during the first iteration. SQP methods, like SNOPT, might be a better choice if you have trustworthy information of the initial values (like in Model-Predictive-Control, where the initial values can be the solution of the previous solve).

Thanks for your kind reply!

Thanks for your kind reply!

Hi! It works without the option, although IPOPT might do some smarter tricks when you additionally set that option, I haven't experimented with that yet.
Generally I've found it's quite difficult to warm-start interior point methods like IPOPT, because of the way they solve the problem: The initial variables are often changed a lot to move into the center of the constraints during the first iteration. SQP methods, like SNOPT, might be a better choice if you have trustworthy information of the initial values (like in Model-Predictive-Control, where the initial values can be the solution of the previous solve).

Hi @awinkler, I have the same question about using SNOPT. Do I just set the variables with good initial values or I should also change the parameter "Cold" in the snopt_sovler.cc? Once I set Cold = 2, which stands for warm starting, SNOPT gives warnings of "Invalid argument Fstate" and it seems that Fstate are not assigned with any meaningful values in SnoptAdapter. Thank you!


Performance comparison to java.util.HashMap

Hi, I'm not sure what's the best place to ask questions related to this project, so I hope it's ok if I create this issue to do so.
I'm wondering whether you did any performance comparisons (in regards to look-up speed) to the JDK's HashMap. In a quick test I'm observing that HashMap is about 8x faster for get() than calling RecSplitEvaluator#eval().
I'm interested as I was hoping to use MinPerf as means to optimize through-put of look-ups in immutable maps I have; but perhaps I was misguided, and actually optimizing throughput isn't a goal for MinPerf, but it's (only) optimizing for space instead? In my case, space is not so much of an issue (maps are 10K entries at most), but accessing them as efficiently as possible is desirable. Thanks a lot for clarifying!

HashMap to be 8x faster is about what I would expect as well, I'm afraid. Well, if give the minimal perfect hash function more space, then it would be faster; but it's very hard to reach the HashMap speed. I see the main use case for minimal perfect hashing is to saving space (memory), and not so much improving speed. Sure, speed needs to be acceptable.
If you want to speed up access to a hash map, and if you can live with some limitations, then you could maybe:

Depending on the key, speed up, or completely avoid the "equals" check that is needed for a HashMap (in case of a hash collision).
Use a different (faster) hash function, and store the hash value in the key, to avoid repeated calls to the hash function.

Ok, thanks a lot for clarifying, much appreciated.


users' reference

Document the Prolog dialect this library accepts including built-in predicates.

Codecov Report

Merging #123 (6d70788) into main (929e3f5) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #123   +/-   ##
=======================================
  Coverage   85.63%   85.63%
=======================================
  Files          18       18
  Lines        5074     5074
=======================================
  Hits         4345     4345
  Misses        648      648
  Partials       81       81

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 929e3f5...6d70788. Read the comment docs.


NODE_OPTIONS='--disable-proto=throw' will break npm-script view and debugger auto-attch of Node.js project on macos

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

VS Code Version: 1.72.0
OS Version: macos 12.6

Steps to Reproduce:

exports environment variable NODE_OPTIONS='--disable-proto=throw'
open a Node.js project

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.72.0. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

I'm not able to reproduce this.
Note that if you have something like export NODE_OPTIONS="--disable-proto=throw" in your bashrc/zshrc, that will overwrite the NODE_OPTIONS that VS Code sets to make auto attach function. You want to do something like export NODE_OPTIONS="--disable-proto=throw $NODE_OPTIONS" instead.


Can post-robot handle this requirement in any way I'm not seeing ?

There's no built-in way to do this right now, because it's not always possible to enumerate all of the open popups and iframes, but if you just want to message all iframes it's a pretty simple traversal.
function messageAllFrames(win, name) {
    postRobot.send(win, name);
    for (var i = 0; i < win.frames.length; i++) {
        messageAllFrames(win.frames[i], name);
    }
}

messageAllFrames(window.top, 'foo');

Does that work for your use-case?

It totally makes sense. Thank you!

I tested your suggestion with a blank page with 2 iframes, and it worked. But when I combine with xComponent, it won't work... is there any incompatibility to use post-robot with xComponent alltogether ?

Do you see a specific error when doing this in conjunction with xcomponent?

Actually, I'm not receiving anything on the event listener application, and the callback that I have on the "send", is returning an error related to cross origin...I have the parent application running on localhost:4200 (where I have the "Send" call), and is rendering an xcomponent with an application on localhost:8080 (where I have the "on" listener). The following is a stringify of the event object returned on the callback
ack: "error"
domain:"http://localhost:4200"
error:"Blocked a frame with origin "http://localhost:8080" from accessing a cross-origin frame.↵Error: Blocked a frame with origin "http://localhost:8080" from accessing a cross-origin frame.↵    at JSON.stringify ()↵    at http://localhost:8080/?uid=8c123d7ab7&version=latest&xcomponent=1:79:49↵    at http://localhost:8080/xcomponent.js:1537:36↵    at trycatch (http://localhost:8080/xcomponent.js:1600:10)↵    at new SyncPromise (http://localhost:8080/xcomponent.js:1729:6)↵    at Object.deNodeify (http://localhost:8080/xcomponent.js:1534:17)↵    at Object.onSuccess (http://localhost:8080/xcomponent.js:3761:30)↵    at _loop2 (http://localhost:8080/xcomponent.js:1802:55)↵    at SyncPromise.dispatch (http://localhost:8080/xcomponent.js:1836:22)↵    at SyncPromise.then (http://localhost:8080/xcomponent.js:1862:11)"
hash:"SAVE_STATE_REQUESTED_673eed1063"
id:"b4a9e3bec8"
name:"SAVE_STATE_REQUESTED"
sourceDomain:"http://localhost:8080"
type:"postrobot_message_response"
windowType:"iframe"

Looks like http://localhost:8080/?uid=8c123d7ab7&version=latest&xcomponent=1:79:49 is some code running in your iframe, guessing in a script tag? Could you share the code?


Python GA security API

No changes from the draft line of development that you've already reviewed.

lgtm


rage: revert to using default patched pkg-config

Motivation for this change
Fixes build failure reported on https://github.com/NixOS/nixpkgs/pull/47108.
It seems that currently meson and vanilla pkg-config does work well, or there is a bug in rage related to them. For now revert to the default pkg-config (which is patched to disable resolving private requirements, used by EFL) and explicitly list the include directories that cannot be found because of that. See also https://github.com/NixOS/nixpkgs/pull/28477.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build enlightenment.rage

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: enlightenment.rage
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: enlightenment.rage
Partial log (click to expand)
post-installation fixup
Wrapping program /nix/store/9zc6daab9c5fbcmvcn4hkb8ary9wrajx-rage-0.3.0/bin/rage
shrinking RPATHs of ELF executables and libraries in /nix/store/9zc6daab9c5fbcmvcn4hkb8ary9wrajx-rage-0.3.0
shrinking /nix/store/9zc6daab9c5fbcmvcn4hkb8ary9wrajx-rage-0.3.0/lib/rage/utils/rage_thumb
shrinking /nix/store/9zc6daab9c5fbcmvcn4hkb8ary9wrajx-rage-0.3.0/bin/.rage-wrapped
strip is /nix/store/h0lbngpv6ln56hjj59i6l77vxq25flbz-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/9zc6daab9c5fbcmvcn4hkb8ary9wrajx-rage-0.3.0/lib  /nix/store/9zc6daab9c5fbcmvcn4hkb8ary9wrajx-rage-0.3.0/bin
patching script interpreter paths in /nix/store/9zc6daab9c5fbcmvcn4hkb8ary9wrajx-rage-0.3.0
checking for references to /build in /nix/store/9zc6daab9c5fbcmvcn4hkb8ary9wrajx-rage-0.3.0...
/nix/store/9zc6daab9c5fbcmvcn4hkb8ary9wrajx-rage-0.3.0

Success on aarch64-linux (full log)
Attempted: enlightenment.rage
Partial log (click to expand)
post-installation fixup
Wrapping program /nix/store/prd204c0s9xla529vl5nj5cljwixmk3i-rage-0.3.0/bin/rage
shrinking RPATHs of ELF executables and libraries in /nix/store/prd204c0s9xla529vl5nj5cljwixmk3i-rage-0.3.0
shrinking /nix/store/prd204c0s9xla529vl5nj5cljwixmk3i-rage-0.3.0/lib/rage/utils/rage_thumb
shrinking /nix/store/prd204c0s9xla529vl5nj5cljwixmk3i-rage-0.3.0/bin/.rage-wrapped
strip is /nix/store/y4ymnvgxygpq05h03kyzbj572zmh6zla-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/prd204c0s9xla529vl5nj5cljwixmk3i-rage-0.3.0/lib  /nix/store/prd204c0s9xla529vl5nj5cljwixmk3i-rage-0.3.0/bin
patching script interpreter paths in /nix/store/prd204c0s9xla529vl5nj5cljwixmk3i-rage-0.3.0
checking for references to /build in /nix/store/prd204c0s9xla529vl5nj5cljwixmk3i-rage-0.3.0...
/nix/store/prd204c0s9xla529vl5nj5cljwixmk3i-rage-0.3.0

Although this fixes the build  failure of the package, it is not the best fix. Closing if favor of https://github.com/NixOS/nixpkgs/pull/47132.


Day/Night Summary and Icon Fields

It would be nice if the summary field could be split into two summary fields with one being for daytime conditions and the other one for nighttime conditions. One of my main complaints about the summaries from DarkSky is that since they kept the summaries breif it would often miss out on large portions of the day depending on the forecast. Some examples
Foggy in the morning.
Possible light rain in the morning.
Rain and windy overnight.
Those summaries don't provide much information outside of those timeframes so you'd have to look at the hourly forecast anyway to get more information and having it split into day and night helps to solve that problem.
As for the existing summary/icon fields they could either be used to show a summary of the day like they are now or it could show the day information during the day and then swap to the night information at night. The first option is something weather.com does with their API so maybe that would be better?

Looks like this one was passed over. Thoughts about adding something like this when text summaries are implemented?
If the text summaries are going to take a while can you add the no-autoclose label to this issue so it doesn't attempt to auto-close this issue every 90 days.

Yup, let's keep this one open! Once I get the daily max stuff sorted out, complete text summaries in the Dark Sky style are next

@alexander0042 A way to keep this open without it automatically adding the stale label would be to either assign this issue to yourself or add the keep label to this issue. Either of those will prevent the bot from marking this as stale in the future.

Perfect! Label is added

@alexander0042 I see it has the enhancement label. The only ignored label is called keep though if you want it to ignore items tagged as enhancement and bug you can easily add it by modifying lines 16 and 17 https://github.com/alexander0042/pirateweather/blob/main/.github/workflows/stale.yml to be
exempt-issue-labels: 'keep, enhancement, bug'
exempt-pr-labels: 'keep, enhancement, bug'

Eventually I figure things out, keep label makes a lot of sense

Was thinking about this and maybe instead of having a day/night summary/icon fields it might be better to have a section to display a forecast in day/night chunks.
So it would have a day block which displays the forecast from 6am to 6pm for the day and the night block would be from 6pm to 6am. Maybe once there are fewer than x number of hours left the block no longer shows since it doesn't make sense to show a forecast for only a few hours. It could maybe have the same fields as the hourly section does currently.
To me it would make more sense then having a day & night summary field and I know that most other APIs do offer the ability to have a day & night forecast and would be useful for apps which would like to show this information.
This idea came about since I noticed that Breezy Weather has PW as a weather provider but the daily information becomes limited after 48h since they do not use the extended hourly forecasts.


this one is for lime rat. it look extremely powerful but i have one problem. "stub not found" and for this one can you add ransomeware?

@moom8251 Please provide a description do not ask your question in the title. Also, yes the plugin system would allow for that but it currently isn't implemented. "stub not found" is because the file stub.exe was deleted. this issue is likely caused by your antivirus. please try to disable or add an exception to your antivirus and redownload the program


HBASE-24199 Procedure related metrics is not consumed in the JMX metric

The procedure related metrics like newly added metrics were registered with the newer registry and the call to expose these that are registered with the new metrics was missing in the getMetrics API of the various metrics implementation classes

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 18s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+0 :ok:
mvndep
0m 30s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m  4s
master passed

+1 :green_heart:
checkstyle
1m 26s
master passed

+1 :green_heart:
spotbugs
2m 40s
master passed

-0 :warning:
patch
2m 22s
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 12s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 46s
the patch passed

-0 :warning:
checkstyle
1m 12s
hbase-server: The patch generated 4 new + 1 unchanged - 0 fixed = 5 total (was 1)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
12m 31s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1.

+1 :green_heart:
spotbugs
3m  3s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 23s
The patch does not generate ASF License warnings.

39m 13s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1614/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1614

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle

uname
Linux 66f35597c010 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 512d00e75d

checkstyle
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1614/1/artifact/yetus-general-check/output/diff-checkstyle-hbase-server.txt

Max. process+thread count
84 (vs. ulimit of 12500)

modules
C: hbase-hadoop-compat hbase-server U: .

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 20s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
5m 54s
the patch passed

+1 :green_heart:
compile
1m 55s
the patch passed

+1 :green_heart:
javac
1m 55s
the patch passed

+1 :green_heart:
shadedjars
7m 33s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 25s
hbase-hadoop-compat in the patch failed.

-0 :warning:
javadoc
0m 56s
hbase-server in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
0m 45s
hbase-hadoop-compat in the patch passed.

+1 :green_heart:
unit
139m  9s
hbase-server in the patch passed.

179m 28s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1614/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1614

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 56c735ffa749 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 512d00e75d

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1614/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-hadoop-compat.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1614/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1614/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-hadoop-compat.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1614/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1614/1/testReport/

Max. process+thread count
3762 (vs. ulimit of 12500)

modules
C: hbase-hadoop-compat hbase-server U: .

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 46s
the patch passed

+1 :green_heart:
compile
1m 22s
the patch passed

+1 :green_heart:
javac
1m 22s
the patch passed

+1 :green_heart:
shadedjars
5m 39s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 55s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 40s
hbase-hadoop-compat in the patch passed.

+1 :green_heart:
unit
186m 36s
hbase-server in the patch passed.

214m 10s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1614/1/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1614

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 50e28d43c013 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 512d00e75d

Default Java
1.8.0_232

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1614/1/testReport/

Max. process+thread count
3691 (vs. ulimit of 12500)

modules
C: hbase-hadoop-compat hbase-server U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1614/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.


"namespace" vs "pod-namespace" naming is inconsistent between metrics

This is more of an issue with the data format itself, reported by a user of SCK (via SAI).
What happened:
Some metrics have the "namespace" dimension while other metrics have the "pod-namespace" dimension. This makes custom dashboarding harder.
What you expected to happen:
Kubernetes metrics should have a consistent dimension for the namespace value.
Environment:

Kubernetes version (use kubectl version): 1.2.0

Duplicate of https://github.com/splunk/splunk-connect-for-kubernetes/issues/256


Record task finish times

example of task execution time recording (#9)

Very cool.  Hoping to dig into this tonight or this weekend.