Make binary dependencies optional

Users can now disable binary dependencies if they don't need them, closes #618.
I think we could also make JSON and YAML optional and keep them enabled by default. What do you think?

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @Emilgardis (or someone else) soon.
Please see the contribution instructions for more information.

What do you think about this suggestion in a separate PR if we merge this?

if it's trivial, I think it'd be good to include it here

asking for one more reviewer before merging

@Emilgardis sorry for bothering, but maybe ping someone who can left an additional review?

@Emilgardis could you please draft a new release after merge?


Add a start at boot option.

This should be an option in your device’s VPN settings already for any VPN extension.

Where?

On the Pixel 4a with Android 11 that I have here, it's at:
"Settings" app -> "Network & internet" -> "Advanced" -> "VPN" -> press the ⚙ next to "Yggdrasil" -> check "Always-on VPN" option.

Oh. I'll try that.

I get this when I reboot. Yggdrasil doesn't enable at boot.

Ditto. Has to be manually turned on even when "always-on".

I've improved Always-On VPN support in the latest build but it's possible the UI will still misbehave in some cases.

The app appears to crash on connection change now.


Enforce non-CH graphs for all LocationIndex implementations

These calls to CHGraph#disconnect aren't doing anything and there aren't even any shortcut edges involved in this test. This has been like this since a long time, for example already in 2015, e.g. here 7f80425b6a0af9bdfef12c8a873676e39e0a04a6. Maybe we should rename the test or remove it even (is it still testing something useful) ?

Yeah, very old stuff. Was introduced in #30 but at that time we had two different LocationIndex implementations. One for CH and one for none-CH graphs. So probably we do not need this anymore.

Ok Ill remove the entire test then

Now I am throwing IllegalState for all LocationIndex implementations and deleted the LocationIndexCHTest.

Or maybe we remove all other LocationIndex implementations or move them into the tests? I think the only used one is the full edge index for correctness tests.

Or maybe we remove all other LocationIndex implementations or move them into the tests? I think the only used one is the full edge index for correctness tests.

Ok go ahead if you want, for me its sufficient to get rid of the .disconnect calls for now :)


bug fix of strings by gapples2

Was fixed in https://github.com/FlamemasterNXF/PeanutScript/commit/113bb4b4e022a0ab3a1eed9d7fe77de35fcb8155


BUG: set_index now sorts with single partition

Had an edge case in df.set_index where you could end up with
an unsorted index when you have a single partition.
xref https://github.com/dask/dask/issues/2211 (doesn't close)

replaced by #2217


ctr-backoffice-backend v0.7.x UnhandledPromiseRejectionWarning: Error: A circular dependency has been detected (property key: "questionType"). Please, make sure that each side of a bidirectional relationships are using lazy resolvers ("type: () => ClassType").

Commit 7c8ef62a004a913256665dccd955528dcfb12264
causes this error message.
UnhandledPromiseRejectionWarning: Error: A circular dependency has been detected (property key: "questionType"). Please, make sure that each side of a bidirectional relationships are using lazy resolvers ("type: () => ClassType").

Seems related to https://github.com/typeorm/typeorm/issues/4190

98c9a21 seems to work around the bug, but seems not a proper solution.


Using Azure AppConfiguration for Feature Flags in dotnet core worker service

I'm trying to use Microsoft.FeatureManagement in a dotnet core worker service. But I have no clue how to configure it that it will periodically check if the feature flags have been changed.
Since it's not a asp.net core app I don't have a Configure and I thus cannot do app.UseAzureAppConfiguration();.
Do I need to call something periodically to refresh the feature flags that are configured in AppConfiguration?
And is there a sample on how to do just that?
Program.cs (partial)
        public static IHostBuilder CreateHostBuilder(string[] args) =>
            Host.CreateDefaultBuilder(args)

                .ConfigureAppConfiguration((hostingContext, config) =>
                {
                    // Build config to access the current values
                    var currentConfig = config.Build();
                    // Load AZURE_APP_CONFIGURATION_URI and add app configuration if set
                    var appConfigUri = currentConfig.GetValue<string>("AZURE_APP_CONFIGURATION_URI")
                        ?? "https://my-default-config-fake.azconfig.io";

                    config.AddAzureAppConfiguration(options =>
                    {
                        var credential = new DefaultAzureCredential();

                        options
                            .Connect(new Uri(appConfigUri), credential)
                            .Select(KeyFilter.Any, LabelFilter.Null)
                            .Select(KeyFilter.Any, $"{hostingContext.HostingEnvironment.EnvironmentName}");

                        options.UseFeatureFlags(ffOptions =>
                        {
                            ffOptions.CacheExpirationInterval = TimeSpan.FromSeconds(30);
                            ffOptions
                                .Select(KeyFilter.Any, LabelFilter.Null)
                                .Select(KeyFilter.Any, $"{hostingContext.HostingEnvironment.EnvironmentName}");
                        });
                    });
                })
                .ConfigureServices(services => Startup.ConfigureServices(services))
            .UseConsoleLifetime();

partial Startup.cs
    public static class Startup
    {
        public static void ConfigureServices(IServiceCollection services)
        {
            services.AddOptions();
            services.AddApplicationInsightsTelemetryWorkerService(options =>
            {
                options.ApplicationVersion = typeof(Program).Assembly.GetName().Version.ToString();
            });
            services.AddAzureAppConfiguration();
            services.AddFeatureManagement();
            services.AddHttpClient();

// Other stuff removed

        }
    }

Hi @svrooij, for a .NET Core app, you need to call RefreshAsync or TryRefreshAsync to refresh your key-values or feature flags from App Config. This call should be setup in your application hot path in a way that ensures that TryRefreshAsync is continuously called regardless of whether the cache has expired or not. If the cache has not expired, there will be no server calls, but if the cache has expired, the latest value will be fetched from the server. This is true for both key-values and feature flags.
You already have the correct UseFeatureFlags method defined in your code. As long as TryRefreshAsync is triggered, your feature flags will be reloaded from AppConfig every 30 seconds (your CacheExpirationInterval).

@svrooij you've probably figured this out by now but when you execute UseFeatureFlags a key is automatically registered to be watched.  If you do not specify a Select() in the options then a value of * is used which watches all feature flags.  You do not need to call ConfigureRefresh for FeatureFlags to refresh.

@svrooij It's been a while but we've added this into the documentation here, as suggested. Gonna close this one out.


Fix: DeviceMonitor.Dispose() does an abort of the background thread.

If a ThreadAbortException is caught in the DeviceMonitorLoop, and it was triggered by the Dispose method, ignore it. Else, log it.

@bartsaintgermain For your reviewing pleasure.

Current coverage is 73.25%

Merging #21 into master will decrease coverage by -0.06% as of 064dd0d

@@            master     #21   diff @@
======================================
  Files           51      51
  Stmts         1413    1417     +4
  Branches       187     188     +1
  Methods          0       0
======================================
+ Hit           1036    1038     +2
- Partial         84      85     +1
- Missed         293     294     +1

Review entire Coverage Diff as of 064dd0d

Powered by Codecov. Updated on successful CI builds.


'Group By' Tasks Duplication Filtering

⚠ Please check that this feature request hasn't been suggested before.

[X] I searched previous Ideas in Discussions didn't find any similar feature requests.
[X] I searched previous Issues didn't find any similar feature requests.
[X] I am only requesting a single feature. Multiple changes should be split into individual requests, with links between them.
[X] I believe my requested feature will be generally applicable to other users, not just me: it is not uniquely tied to my personal workflow.

🔖 Feature description
I use tags for grouping tasks, which works great, however there is one flaw. Whenever something is tagged with two tags it is duplicated.
Example: On my daily notes I use the following.
```tasks
not done
due before <daily note's date>
group by tags
hide tags
sort by priority
sort by due date
sort by description
short mode
```

All of my work tasks have a #h tag, but most are broken down further into projects (via tags). When they have more than one tag, they show under both #h and #projectname, so the day's list becomes quite unruly.
✔ Solution

Adding group by first tag (or last tag etc)
Additional filtering beyond grouping

❓ Alternatives
Removing the overall work tag (#h), but then I lose the ability to monitor all of those tasks as a whole, or filter them out when not working.
📝 Additional Context
No response

Hi, there are examples of various ways of addressing this in the user docs. Look at the ‘group by function’ example for tags, and pick whichever of the many examples suits your needs.

@claremacrae thank you. I searched but somehow missed that. I assume the function bit made me scroll right past it. Thanks for all your effort and the quick response. This plugin is a must have.
For others and future reference: https://publish.obsidian.md/tasks/Queries/Grouping#Tags, specifically group by function task.tags.sort().join(", ") works for this use case.

Thanks for the kind words and sharing the info. I’m on mobile at the moment.


Supports ScaleFactor for GTK 3

GTK has a simple mechanism to scale the UI on high dpi screens. It's just an int. On windows if you set the scaling to 200%, ScaleFactor will return 2. At 125%, you still get 1.  (see https://docs.gtk.org/gtk3/method.Widget.get_scale_factor.html)
I modified the code so that we create a bigger surface and then scale down when we render in the Cairo context. I added a IgnorePixelScaling to mimic what has be done on other views, I set the default to true so that my changes are completely harmless. You need to opt-in to get the new behavior.
My GTK skills are pretty close to zero, so please look two times at the proposed changes 😅
Tested on Windows only on the GTK sample.
Before (the text is blurry):

After (the text is sharp):

This looks good. The only issue is that the IgnorePixelScaling is false by default in all other platforms and the meaning is flipped.
It is wrong and what you have is technically correct, but when I originally implemented the code, the property was to tell the drawing system that if IgnorePixelScaling == true then we want to ignore the fact that the OS has a different scale to the number on the screen.
So, false is the default and would typically be blurry on high res monitors.
One day we can have a new property that just inverts this one. Maybe we can add a bool ApplyPixelScaling => IgnorePixelScaling and hide this old one. But it is the backwards world in which we live.

Another thing I also do in other platforms is lie about the canvas size if this is set.
For example for android:
var userVisibleSize = IgnorePixelScaling
	? new SKSizeI((int)(info.Width / density), (int)(info.Height / density))
	: info.Size;

CanvasSize = userVisibleSize;

if (IgnorePixelScaling)
{
	var skiaCanvas = surface.Canvas;
	skiaCanvas.Scale(density);
	skiaCanvas.Save();
}

(in fact I'm using SkiaSharp.Views.WPF.SKGLElement which has no such option)

On Blazor, if set the value to false I get the full width (minus the browser borders):

(my screen is 2560x1440, scaling is 125%)
If I set it to true I get a smaller size:

I don't get my pixel perfect rendering and I'm sad 😿

There is also the e.RawInfo property that should always be the size of the actual pixel canvas. When you set to true, this is where the lies come in. The info says 2000, but we just applied the scaling for you.

For blazor, I think the size needs to be set via CSS/style or something. If you run the skia sample in the repo, it should be setting the property to true and also be crisp.
I think I did what this article said: https://web.dev/articles/canvas-hidipi and this mozilla: https://developer.mozilla.org/en-US/docs/Web/API/Window/devicePixelRatio#correcting_resolution_in_a_canvas

There is also the e.RawInfo property that should always be the size of the actual pixel canvas

Yes indeed I get my 2500 px

I think I did what this article said: https://web.dev/articles/canvas-hidipi and this mozilla: https://developer.mozilla.org/en-US/docs/Web/API/Window/devicePixelRatio#correcting_resolution_in_a_canvas

I'll look into it but when running the WPF / Blazor (IgnorePixelScaling="false") I was getting the same results.
Side note but what would be great is to have the scaling info in the SurfaceEventArgs. In my case, I would expect to get 1.25% so that I know I need to scale the rendering of my components.


refactor migration and storedversion update

/cc @qiujian16 @haoqing0110 @elgnay

maybe @elgnay or @haoqing0110 need to take a look also

/lgtm


Figure out what to do with NMEA CAN conversion functions

Do they go in a class? Do versions of them go in multiple classes?

Going to use NMEA2000 library to handle this on FW side.


send_button: Suppress Send tooltip on tabbing to send.

This PR suppresses the Tippy tooltip on the send button when the send button is focused via the Tab key. Mouse hovers will still activate it after a pause, using the already-present EXTRA_LONG_HOVER_DELAY.
See brief CZO discussion

Screenshots and screen captures:
Before: Tippy tooltip on tabbing to send button

After: No Tippy tooltip on tabbing to send button

Before & after: Tippy tooltip on mouse hover, after a delay

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[x] Calls out remaining decisions and concerns.
[x] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[x] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

Merged, thanks @karlstolley!


fix: the style of 'block cursor' when scrolling

Currently, scrolling when the cursor is on a block element gives unexpected results.
I've added a scroll listener that restores the cursor's style if the scrolling takes the cursor out of the range of the block element.
Limitations
Currently it is not possible to listen to scroll events on internal scrollable elements.

@Jannchie Wow, that's great!
But it seems that it is not compatible with SSR. I'm building my docs with vite-ssg. Everything may be ok in dev mode, but it failed to build because of this error:
ReferenceError: MouseEvent is not defined

And the code should work as expected for SSR apps. Can you fix this problem?

Thanks for the reminder.
The problem of not being able to build with SSG has now been solved. Everything seems to be working fine.


Linux kernel updates 2023-03-17

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Can build/test later in the day

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

1 package marked as broken and skipped:

linuxKernel.kernels.linux_5_4_hardened

2 packages failed to build:

linuxKernel.kernels.linux_4_14_hardened
linuxKernel.kernels.linux_4_19_hardened

12 packages built:

linuxKernel.kernels.linux_4_14
linuxKernel.kernels.linux_4_19
linuxKernel.kernels.linux_5_10
linuxKernel.kernels.linux_5_10_hardened
linuxKernel.kernels.linux_5_15
linuxKernel.kernels.linux_5_15_hardened
linuxKernel.kernels.linux_5_4
linuxKernel.kernels.linux_6_1
linuxKernel.kernels.linux_hardened (linuxKernel.kernels.linux_6_1_hardened)
linuxKernel.kernels.linux_6_2
linuxKernel.kernels.linux_latest_libre
linuxKernel.kernels.linux_libre


citizenlab: Fix the submit workflow

Currently the production deployed instance of the test-lists API does not work because it's pointing to the wrong remote.
I implemented a fix for using the right origin over here: https://github.com/ooni/sysadmin/commit/9ae9135844b51079dcf180e7ca42cc7429380bba.
@FedericoCeratto mentioned that this is going to conflict with the testing remote and we should before deploying it create a separate dedicated repo to use as an origin for the testing instance.

We have implemented and deployed a fix for this. The work needed to do this is documented as part of the following PR: https://github.com/ooni/api/pull/270/


upcoming: [M3-8215] - Hide monthly network transfer section for distributed regions

Description 📝
Distributed compute instances have no transfer pool, so the Monthly Network Transfer section is irrelevant. This PR hides that section and expands the Network Transfer History chart to occupy the space.
Changes  🔄
List any change relevant to the reviewer.

Hide the monthly network transfer section for Linodes in a distributed region

Preview 📷

Before
After

How to test 🧪
Prerequisites
(How to setup test environment)

Ensure your account has the new-dc-testing, edge_testing and edge_compute customer tags
Create a Linode in a distributed region if you don't already have one

Verification steps
(How to verify changes)

Go to a Linode's details page and then navigate to the Network tab
The Monthly Network Transfer section should not display for Linodes in a distributed region
The Monthly Network Transfer section should display as normal for Linodes in a core region

As an Author I have considered 🤔
Check all that apply

[ ] 👀 Doing a self review
[ ] ❔ Our contribution guidelines
[x] 🤏 Splitting feature into small PRs
[x] ➕ Adding a changeset
[ ] 🧪 Providing/Improving test coverage
[ ] 🔐 Removing all sensitive information from the code and PR description
[x] 🚩 Using a feature flag to protect the release
[ ] 👣 Providing comprehensive reproduction steps
[ ] 📑 Providing or updating our documentation
[ ] 🕛 Scheduling a pair reviewing session
[ ] 📱 Providing mobile support
[ ] ♿  Providing accessibility support

@mjac0bs Good catch, I asked Kendall and he said there was some initial discussion to completely redesign the network transfer UI

A complete redesign sounds like it may take some time to actually get designed and implemented - though I'm in agreement that it should happen; I know customer support gets questions about usage and things not being clear. But in the meantime, what do we think about adding "your devices' core regions" or something like that in the tooltip?


Builder set null fields

Class Blabla {
public int ID;
public ArrayList sub = new ArrayList<>();
}
Blabla bla = Blabla.builder().id(1).build();
bla.sub.add(1);
NullPointerException
Why should this field be set to null if I didn't initialize it in the builder , that's stupid.
Sole solution is to make sub final and who know I want to change the value of this field in the future.

Duplicate of #703

Sole solution is to make sub final and who know I want to change the value of this field in the future.

Unless you're writing a library, make everything final (and as much private as possible). If you want to change the value in the future, so you'll have to remove the modifier. This costs a few seconds at most... nothing compared to time lost debugging anything. And public mutable fields and especially collections mean you'll have a lot of debug.
Note that your class needs no builder at all. For mutable classes I'd suggest chained @Setter. Consider also @Wither.


Bot doesnt manage factory from QueryID,

Vanh, bot doesnt manage favtory if used clicker with query

I can't fix or do anything to fix if you just say that without any futher information


Admob shows on emulator but not in published devices.

My admob works on emulator it shows:

But when I published my apps into app store. It does not even show anything. Not even a blank banner.
I have followed all the config and instruction:
`    admob.banner.config({
id: admobid.banner,
isTesting: false,
bannerAtTop: true,
autoShow: true
})
admob.banner.prepare().then(() => {
scope.showAdmobBanner = true;
});
`
Please help

Hi! Same problem here. It works on iOS emulator with test ads but not in real devices.


[5.0] Improve Str::limit()

Improve Str::limit(). Do better with CJK text.

Could you include tests that were failing on the old implementation that are now passing please?

I say "tests". A minimum of 1 test case would fine. :)

Just curious, how exactly does explicitly setting the encoding to 'UTF-8' instead of relying on mb_internal_encoding() (the default value) help in this case?

@phanan, In some encoding the non-ascii charsets are too long (more than 2 ascii charset width). With UTF-8:

Chars
Width

U+0000 - U+0019
0

U+0020 - U+1FFF
1

U+2000 - U+FF60
2

U+FF61 - U+FF9F
1

U+FFA0 -
2


Pull latest unityscript fixes into 3.5

We're pretty late in the 3.5 cycle - are these necessary for an important case for 3.5?

Merged to unity3.5.


Use a union doesn't work as expected

I have the following type:
interface Foo {
  a: {
    b: { type: 'a', keyA: string } | { type: 'b', keyB: string }
  }
}

type Form = FormModel<Foo, { a: { b: 'group' } }, InferModeRequired & InferModeNonNullable>['controls']

And the following code throws:
builder.nonNullable.group<Form>({
    a: builder.nonNullable.group({
      b: builder.nonNullable.group({
        type: builder.nonNullable.control('a' as const),
        keyA: builder.nonNullable.control('')
      })
    })
  })

The code should work as one of the union types is define.

Thank you for creating new issue, i will check today.

So the main problem - I can't traverse by union type using typescript, because it is typescript limitation. Here is example, that it won't work.
But you can workaround this limitation, you have choice:

Divide your interface by two, like

interface FooBA {
  type: 'a';
  keyA: string;
}

interface FooBB {
  type: 'b';
  keyB: string;
}

interface Foo1 {
  a: {
    b: FooBA
  }
}

interface Foo2 {
  a: {
    b: FooBB
  }
}

And then construct your concrete form using concrete interface...

Use Replace to infer what you need, for example see https://github.com/iamguid/ngx-mf/blob/master/examples/example3.ts#L21 also see docs https://github.com/iamguid/ngx-mf#annotations

Ask questions if something is not clear 🌚

Shure, https://stackblitz.com/edit/angular-ngx-mf-wvaqo5?file=src%2Fapp%2Fapp.component.ts


Cannot Upload a CSV File

Hello,
I am trying to use your sample project. After running the npm install and start commands I load localhost:3030. When I go to the editor page and click a map, nothing happens. Only two buttons show up: "Save SVG" and "Save PNG," but I don't see anything about uploading data.

You will see "upload csv" button when you select map.


Data Integrity failure on getting eth inferace down while running IO

Environment info
<EMAIL_ADDRESS>~]# oc version
Client Version: 4.7.13
Server Version: 4.7.13
Kubernetes Version: v1.20.0+df9c838
<EMAIL_ADDRESS>~]# noobaa version
INFO[0000] CLI version: 5.9.0
INFO[0000] noobaa-image: noobaa/noobaa-core:master-20210719
INFO[0000] operator-image: noobaa/noobaa-operator:5.9.0
<EMAIL_ADDRESS>~]#
Actual behavior

Started uploading 129 G file and only 1000 M is uploaded

Expected behavior

In case of network down , noobaa should have rolled back or complete upload should be done.
 Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
2021-07-23 04:15:45 neha
[root@fyreauto-x-app1 ~]# ifdown eth0
WARN      : [ifdown] You are using 'ifdown' script provided by 'network-scripts', which are now deprecated.
WARN      : [ifdown] 'network-scripts' will be removed in one of the next major releases of RHEL.
WARN      : [ifdown] It is advised to switch to 'NetworkManager' instead - it provides 'ifup/ifdown' scripts as well.
Device 'eth0' successfully disconnected.
[root@fyreauto-x-app1 ~]# ip -4 a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
inet <IP_ADDRESS>/8 scope host lo
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
inet <IP_ADDRESS>/22 brd <IP_ADDRESS> scope global dynamic noprefixroute eth1
valid_lft 26983sec preferred_lft 26983sec
[root@fyreauto-x-app1 ~]# ip -4 a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
inet <IP_ADDRESS>/8 scope host lo
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
inet <IP_ADDRESS>/22 brd <IP_ADDRESS> scope global dynamic noprefixroute eth1
valid_lft 26964sec preferred_lft 26964sec
[root@fyreauto-x-app1 ~]# ifup eth0
WARN      : [ifup] You are using 'ifup' script provided by 'network-scripts', which are now deprecated.
WARN      : [ifup] 'network-scripts' will be removed in one of the next major releases of RHEL.
WARN      : [ifup] It is advised to switch to 'NetworkManager' instead - it provides 'ifup/ifdown' scripts as well.
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/5)
[root@fyreauto-x-app1 ~]# ip -4 a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
inet <IP_ADDRESS>/8 scope host lo
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
inet <IP_ADDRESS>/20 brd <IP_ADDRESS> scope global dynamic noprefixroute eth0
valid_lft 43193sec preferred_lft 43193sec
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
inet <IP_ADDRESS>/22 brd <IP_ADDRESS> scope global dynamic noprefixroute eth1
valid_lft 26865sec preferred_lft 26865sec
[root@fyreauto-x-app1 ~]#
More information - Screenshots / Logs / Other output

must-gather.local.6328555135155415983.zip

@nehasharma5 it's not clear to me which eth0 you have taken down? endpoint? core? app?
In any case, the bucket should be listed ven if you disrupt the upload operation. However, for an upload operation, there is no rollback or complete. It will stay in an "uncompletd" state until the client either cancels or resumes and eventually completes.
You have written the bucket is not visible on the list buckets command? I just want to make sure if the bucket itself is visible or not, the object would only be visible if you specifically request to list the uncompleted uploads.

@nimrod-becker : eth0 is adapter name . I have mentioned above the complete flow how to check and how get interface down.
I had two buckets out of which only one bucket is visible . I am not aware how to specially request to list the uncompleted uploads. Its just a upload was started to a bucket and only partial of the object is uploaded. I have seen the upload if upload is failed due to any reason , the object is not shown  into bucket but in this case I can see partial upload of object into the bucket

eth0 of what? The OCP node? Something else ?
Regarding multipart uploads, a listing would not should you uncompleted uploads, not will they fail unless you (or the client) explicitly send an abort command.
Regarding listing uncompleted uploads, see https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListMultipartUploads.html

@nimrod-becker I just now had a quick talk about another issue with @nehasharma5
The eth0 is the network adapter of the client. So during an upload it suppose to break the upload.
The thing is she is not seeing any uncompleted objects using s3 cli, So after shutting down the interface the object doesn't suppose to pop. We need to investigate how the object got created and marked as completed in some way - making it appear in the listing.

@nehasharma5 Is it possible that you did not cancel the upload? I can't find proof in the logs but I can see that the parts are being copied into the final file - which suppose to happen only when complete was sent by the client. So my guess here is that you didn't break the upload, you let the upload continue, and then when network came up again the client completed the upload just with the parts he successfully upload. Did the s3 client failed the upload? did he respond with any errors? did you break the upload manually?

@jackyalbo Yes , S3 client failed the upload I get 503 . Yes, I got the network down manually. The upload was partial because the file which I started uploading and the one which is uploaded have different size

@jeniawhite I again tried this with new noobaa build (15 AUg) and new build of cnsa/csi , here are the observation

S3 cp operation did not fail and shows upload success message
Size of file in bucket is 0
[root@fyreauto-x-app1 ~]# ifdown eth0
WARN      : [ifdown] You are using 'ifdown' script provided by 'network-scripts', which are now deprecated.
WARN      : [ifdown] 'network-scripts' will be removed in one of the next major releases of RHEL.
WARN      : [ifdown] It is advised to switch to 'NetworkManager' instead - it provides 'ifup/ifdown' scripts as well.
Device 'eth0' successfully disconnected.
[root@fyreauto-x-app1 ~]# ifup eth0
WARN      : [ifup] You are using 'ifup' script provided by 'network-scripts', which are now deprecated.
WARN      : [ifup] 'network-scripts' will be removed in one of the next major releases of RHEL.
WARN      : [ifup] It is advised to switch to 'NetworkManager' instead - it provides 'ifup/ifdown' scripts as well.
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/4)
[root@fyreauto-x-app1 ~]# ifdown eth0
WARN      : [ifdown] You are using 'ifdown' script provided by 'network-scripts', which are now deprecated.
WARN      : [ifdown] 'network-scripts' will be removed in one of the next major releases of RHEL.
WARN      : [ifdown] It is advised to switch to 'NetworkManager' instead - it provides 'ifup/ifdown' scripts as well.
Device 'eth0' successfully disconnected.

upload: ./test_file_90 to s3://new-buck/test_file_90
[root@fyreauto-x-app1 ~]# s3 ls s3://new-buck
urllib3/connectionpool.py:1013: InsecureRequestWarning: Unverified HTTPS request is being made to host 's3-noobaa.apps.ns.cp.fyre.ibm.com'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
2021-08-16 00:25:40        282 bucket.py
2021-08-16 00:32:07<PHONE_NUMBER>0 test_file_10
2021-08-16 23:21:07          0 test_file_129
2021-08-16 23:34:03<PHONE_NUMBER>0 test_file_90
[root@fyreauto-x-app1 ~]#
[root@fyreauto-x-app1 ~]# du -sh test_file_129
53G     test_file_129

Tried multiple times with 18 Aug build , not able reproduce with 18 Aug build.


Badge background colors

Adds colored backgrounds for .badge.is-tag type badges, in the same style as those for links.

Just to make sure, that we have the same thing in mind: You want to have tags (those that are shown below questions + the "meta" tag) to be able to be styled in different colors.
If yes: Do we really need all colors, or are danger, default and muted enough (as for buttons)?

Yes, because they're useful for more than just tags, so I want to have the context-color classes available as well. Just enabling everything in the $secondary_colors map was the easiest way.

Superseded by #28


[Error] Incorrect Import of PropTypes Causes Compilation Error

Steps to reproduce
Link to live example: local dev as there's no TS completion to build live phase
Steps:

Set up a Material UI project 6.0.2 with TypeScript.
Use a Material UI component that imports PropTypes with import PropTypes from 'prop-types';.
Run the TypeScript compiler.

Current behavior
When using Material UI with TypeScript, I encountered a compilation error due to the incorrect use of import PropTypes from 'prop-types'; in the codebase.
Typescript Compiler error:
node_modules/@mui/utils/chainPropTypes/chainPropTypes.d.ts:1:8 - error TS1192: Module '"path/to/project/node_modules/@types/prop-types/index"' has no default export.

1 import PropTypes from 'prop-types';

Current example of Material UI implementation: https://github.com/mui/material-ui/blob/v6.0.2/packages/mui-utils/src/chainPropTypes/chainPropTypes.ts#L1C1-L1C36
Since the prop-types library does not have a default export, this import statement is incorrect and should instead use named imports to align with ES6 module standards.
https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/prop-types/index.d.ts
Solution: apply import * as PropTypes from 'prop-types';
Expected behavior
The project should compile without errors.
Context
Replace all occurrences of import PropTypes from 'prop-types'; with import * as PropTypes from 'prop-types'; in the entire Material UI codebase.
Additional Context

Node.js version: v20.9.0
yarn version: 1.22.19
TypeScript version: 5.6.2
MUI System version: 6.0.2

Your environment

npx @mui/envinfo
  System:
    OS: macOS 14.1.1
  Binaries:
    Node: 20.9.0 - /usr/local/bin/node
    npm: 10.2.4 - /usr/local/bin/npm
    pnpm: Not Found
  Browsers:
    Chrome: 128.0.6613.120
    Edge: Not Found
    Safari: 17.1
  npmPackages:
    @emotion/react: ^11.13.3 => 11.13.3
    @emotion/styled: ^11.13.0 => 11.13.0
    @mui/core-downloads-tracker:  6.0.2
    @mui/envinfo: ^2.0.25 => 2.0.25
    @mui/icons-material: ^6.0.2 => 6.0.2
    @mui/material: ^6.0.2 => 6.0.2
    @mui/private-theming:  6.0.2
    @mui/styled-engine:  6.0.2
    @mui/styles: ^6.0.2 => 6.0.2
    @mui/system:  6.0.2
    @mui/types:  7.2.16
    @mui/utils:  6.0.2
    @mui/x-date-pickers: ^7.16.0 => 7.16.0
    @mui/x-internals:  7.16.0
    @types/react: ^18.3.5 => 18.3.5
    react: ^18.3.1 => 18.3.1
    react-dom: ^18.3.1 => 18.3.1
    typescript: ^5.6.2 => 5.6.2

Search keywords: error, types, d.ts

Nitpick: If anyone encounters this issue, here is a quick fix for Unix systems using Yarn post-install:
#!/bin/bash
cd ./

echo "Tuning of TypeScript types for React node_modules packages..."

# Find all .ts files in the project directory including node_modules and replace the import statement
find . -type f -name "*.ts" -exec sed -i '' 's/import PropTypes from '"'"'prop-types'"'"';/import * as PropTypes from '"'"'prop-types'"'"';/g' {} +

# Find all .ts files in the project directory including node_modules and replace the import statement
find . -type f -name "*.ts" -exec sed -i'' -e 's#import React[^;]*#import * as React from '"'"'react'"'"'#g' {} +

Smth like this into package.json:
...
"scripts": {
    "postinstall": "bash ./bin/post.install.sh",
}
...

And to add my 2 cents, given that we’re facing this issue as the optimal fix appears to involve the Unix sed command, pointing to a deployment issue with Material UI. And just take a note, Bitbucket and other deployment environments by git lack access to the Unix sed command. Specifically, my process involves locally building a React application that includes Material UI, then pushing this build to a Git repository. Following this, the deployment can be executed to CloudFront using bitbucket-pipelines.yml as one option, or it can also be done locally through a simple bash script. However, using the local script option means missing out on collaborative team challenges. Could we prioritise resolving this issue as soon as possible please?
Here's a sample Bash script for deploying a React application that uses Material UI:
#!/bin/bash
cd ./

echo "Deploying Material UI Application to CloudFront..."

# IMPORTANT: before deploy you MUST/CAN clear all S3 Bucket files then to deploy, by the other case you can meet a conflict or S3 Bucket potential overload

aws s3 sync ./build s3://$CLOUDFRONT_DISTRIBUTION_S3_BUCKET_NAME/
aws cloudfront create-invalidation --distribution-id $CLOUDFRONT_DISTRIBUTION_ID --paths "/*" | grep Id

echo "CloudFront invalidation is going..."
exit 0

I have verified that each package includes "@types/prop-types": "^15.7.12", which indicates that the entire project can transition to the correct PropTypes import syntax for TypeScript compatibility.
Here is the Pull Request addressing this fix: https://github.com/mui/material-ui/pull/43701
Please review it and let me know if there are any additional contributions or changes needed.

I changed those imports in #23116, maybe it was wrong 🤔

@Janpot  I've tailored the solution to directly address the core issue with the tsc in the upcoming PR https://github.com/mui/material-ui/pull/43736.
We can either keep this https://github.com/mui/material-ui/pull/43701 PR open for future reference or close it, depending on your preference. However, we should consider enhancing a codebase with a new PR by incorporating utilities to enable tsc

@oliviertassinari The issue with tsc primarily pertains to *.d.ts into utils files. From what I can tell, your enhancement doesn’t seem to break the TypeScript behaviour

I changed those imports in #23116, maybe it was wrong 🤔

you were correct. this PR is wrong, and  @types/prop-typed is wrong as well

@Janpot Yeah agree, the problem is not with Material UI.
In<EMAIL_ADDRESS>I see: module.exports = . So it should be imported with
const propTypes1 = require('prop-types);
import propTypes2 from 'prop-types';
import * as propTypes3 from 'prop-types';

propTypes1. // valid
propTypes2. // valid
propTypes3.default. // valid

let's just fix @types/prop-types instead.

@Janpot  @oliviertassinari I might be mistaken, but it appears that we should refer to the @types/prop-types package: https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/prop-types/index.d.ts to address the concerns raised in my pull requests

@oliviertassinari It's impressive how smoothly the previous decision was altered by https://github.com/mui/material-ui/issues/43700#issuecomment-2347374665. Just a quick observation: the updated PR description still seems incorrect after update, as it references a *.ts file instead of the needed @types/prop-types options. I was happy to assist. I look forward to the next release, as the current issue halts all deliveries. Thank you.

@morozow We appreciate your willingness to contribute, but to reduce the risk of contributions being rejected, it would be best to wait until we've agreed on the appropriate solution. To be fully honest, I still don't understand what the exact problem is. At this point, the best thing you could do is to share a real reproduction (e.g. a codesandbox, or a github repository) that clearly demonstrates what you're trying to do and the error you're running into so that we can take a look.
It's clear that there is a mismatch between what the prop-types package exports and what the @types/prop-types declares. You may have to adjust your typescript configuration to get it compiled (see allowSyntheticDefaultImports).

@Janpot I've set up a fresh repository at https://github.com/morozow/material-ui-tsc-fix.
I started by adding a default tsconfig.json following the minimal configuration guidelines from https://mui.com/material-ui/getting-started/installation/.
Next, I installed Material UI as instructed at https://mui.com/material-ui/getting-started/installation/.
After that, I created a default example using the instructions from https://mui.com/material-ui/guides/typescript/#complications-with-the-component-prop.
Upon running tsc, I observe the following:```
user@machine material-ui-tsc-fix % tsc
node_modules/@mui/system/borders/index.d.ts:1:10 - error TS2305: Module '"./borders"' has no exported member 'default'.

1 export { default } from './borders';
           ~~~~~~~

node_modules/@mui/system/cssGrid/index.d.ts:1:10 - error TS2305: Module '"./cssGrid"' has no exported member 'default'.

1 export { default } from './cssGrid';
           ~~~~~~~

node_modules/@mui/system/display/index.d.ts:1:10 - error TS2305: Module '"./display"' has no exported member 'default'.

1 export { default } from './display';
           ~~~~~~~

node_modules/@mui/system/flexbox/index.d.ts:1:10 - error TS2305: Module '"./flexbox"' has no exported member 'default'.

1 export { default } from './flexbox';
           ~~~~~~~

node_modules/@mui/system/palette/index.d.ts:1:10 - error TS2305: Module '"./palette"' has no exported member 'default'.

1 export { default } from './palette';
           ~~~~~~~

node_modules/@mui/system/positions/index.d.ts:1:10 - error TS2305: Module '"./positions"' has no exported member 'default'.

1 export { default } from './positions';
           ~~~~~~~

node_modules/@mui/system/shadows/index.d.ts:1:10 - error TS2305: Module '"./shadows"' has no exported member 'default'.

1 export { default } from './shadows';
           ~~~~~~~

node_modules/@mui/system/sizing/index.d.ts:1:10 - error TS2305: Module '"./sizing"' has no exported member 'default'.

1 export { default } from './sizing';
           ~~~~~~~

node_modules/@mui/system/spacing/index.d.ts:1:10 - error TS2305: Module '"./spacing"' has no exported member 'default'.

1 export { default } from './spacing';
           ~~~~~~~

node_modules/@mui/system/style/index.d.ts:1:10 - error TS2305: Module '"./style"' has no exported member 'default'.

1 export { default } from './style';
           ~~~~~~~

node_modules/@mui/system/typography/index.d.ts:1:10 - error TS2305: Module '"./typography"' has no exported member 'default'.

1 export { default } from './typography';
           ~~~~~~~

node_modules/@mui/utils/chainPropTypes/chainPropTypes.d.ts:1:8 - error TS1192: Module '"/path/to/sandbox/material-ui/material-ui-tsc-fix/node_modules/@types/prop-types/index"' has no default export.

1 import PropTypes from 'prop-types';
         ~~~~~~~~~

node_modules/@mui/utils/elementAcceptingRef/elementAcceptingRef.d.ts:1:8 - error TS1192: Module '"/path/to/sandbox/material-ui/material-ui-tsc-fix/node_modules/@types/prop-types/index"' has no default export.

1 import PropTypes from 'prop-types';
         ~~~~~~~~~

node_modules/@mui/utils/elementTypeAcceptingRef/elementTypeAcceptingRef.d.ts:1:8 - error TS1192: Module '"/path/to/sandbox/material-ui/material-ui-tsc-fix/node_modules/@types/prop-types/index"' has no default export.

1 import PropTypes from 'prop-types';
         ~~~~~~~~~

node_modules/@mui/utils/integerPropType/integerPropType.d.ts:1:8 - error TS1192: Module '"/path/to/sandbox/material-ui/material-ui-tsc-fix/node_modules/@types/prop-types/index"' has no default export.

1 import PropTypes from 'prop-types';
         ~~~~~~~~~

node_modules/@mui/utils/refType/refType.d.ts:1:8 - error TS1192: Module '"/path/to/sandbox/material-ui/material-ui-tsc-fix/node_modules/@types/prop-types/index"' has no default export.

1 import PropTypes from 'prop-types';
         ~~~~~~~~~

Found 16 errors in 16 files.

 Watching for file changes.

Consequently, I encounter an issue documented at https://github.com/mui/material-ui/issues/43700

Assuming a bundler will be consuming your library, you should be able to set "allowSyntheticDefaultImports": true in your tsconfig.json. We can work towards removing this setting in our tsconfig files to improve our internal import behavior, but at the moment we won't fully be able to as we have the previously demonstrated prop-types mismatch with its typings package.

@Janpot I’m pleased that it’s working. If there’s a need for documentation improvement, here’s the PR: https://github.com/mui/material-ui/pull/43747
Thank you!

@morozow I'm glad it works for you. Thank you for improving the docs. Is this issue sufficiently addressed for you so that we can close this ticket and the related ones?

https://github.com/mui/material-ui/pull/43701
https://github.com/mui/material-ui/issues/43685
https://github.com/mui/material-ui/pull/43702
https://github.com/mui/material-ui/pull/43736

We will have to revise our imports as part of https://github.com/mui/material-ui/pull/43264. I'm going to improve/fix the node-esm integration tests before we touch those imports.


formula_auditor: add<EMAIL_ADDRESS>to allowlist

Required for https://github.com/Homebrew/homebrew-core/pull/65531
Cairomm 1.16 and 1.14.x can be installed alongside each other without conflicts

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew tests with your changes locally?
[x] Have you successfully run brew man locally and committed any changes?

Review period will end on 2020-11-25 at 09:09:43 UTC.

Interesting catch-22: I can't add<EMAIL_ADDRESS>to the allow list because the formula doesn't exist in core, and I can't add the formula to core until it's added here to the allow list 😄

You add a skip to the test and open a follow-up PR removing it again.

Review period ended.

@reitermarkus can you merge this one in?
Thanks!

@tschoonj Done, thanks!


Issue with large friction: fall into the plane

Hi,
I need a floor with large friction to prevent objects from being pushed away. But I find the object would fall into the plane using large friction (e.g. 8).
Here is a model which explains my question:

minimal XML
<mujoco model="base">
    <visual>
        <headlight ambient="0.3 0.3 0.3" diffuse="0.6 0.6 0.6" specular="0 0 0"/>
    </visual>

    <worldbody>
        <geom name="floor" friction="8" type="plane" size=".7 .7 .1" rgba="0.7 0.7 0.7 1"/>
        <body >
            <geom type="box" size="0.1 0.1 0.1" pos="0 0 0.1"/>
            <freejoint/>
        </body>
    </worldbody>
</mujoco>

Here is a screenshon, illustrating my question:

Thanks!

friction="8"  is incredibly unrealistic nothing has that friction value. If you want to model the real world, don't do that.
Specifically, this friction value completely breaks the assumptions of the default pyramidal approximation. If you switch to <option cone="elliptic"/> you will get no penetration. However the model will still behave in funny ways.
I highly recommend using a realistic friction value (<= 1) and to use the noslip or impratio options to prevent any minor slippage.

Also, thanks for including a fully loadable model 🙂


Fix: TableView::borrow_item() does not need a mutable reference to self

Indeed, doesn't seem necessary. Thanks for the PR!


The hotplug volume pod killed more time would lead the iSCSI re-login

What happened:
The VM with hotplug volume. If the hotplug volume pod hp-volume- is dead more than twice. The iSCSI connection on the host would logout/login. That makes the above hotplug volume not used anymore. If the user tries to access this device, that will trigger an IO error.
What you expected to happen:
The hotplug volume should normally work even if the hp-volume- pod is dead more than twice.
How to reproduce it (as minimally and precisely as possible):

create one VM instance.
attach the hotplug volume.
manually delete the hp-volume-xxx.
manually delete the hp-volume-xxx (newly hp-volume- pod) again.
You could check the iSCSI connection will logout then login. Also, the disk on the VM should be also broken.

Additional context:
We found that because the global path is detached by kubelet when we delete hp-volume- pod first time.
Then when we delete the hp-volume- pod again. The kubelet would detach from the node directly. Then after the new hp-volume- pod comes back, attach it to the node again.
The brief flow is as follows:
hp-volume-aaa
  -> killed, then hp-volume-bbb creating
  -> kubelet try to detach but fail (because the volume is still mounted (global path), then new pod is coming back, everything is fine)
  -> umount global/staging path
hp-volume-bbb
  -> killed, then hp-volume-ccc creating
  -> kubelet try to detach from node and success (because now the global path is unmounted)
hp-volume-ccc

Environment:

KubeVirt version (use virtctl version): 0.54.0
Kubernetes version (use kubectl version): 1.24.7
VM or VMI specifications: N/A
Cloud provider or hardware configuration: Longhorn CSI
OS (e.g. from /etc/os-release): N/A
Kernel (e.g. uname -a): N/A
Install tools: N/A
Others: N/A

Hey folks. I am seeing a similar error, but this time with Filesystem volumes. PR #9269 only affects the behavior with respect to Block hotplug PVs.
When I delete the attachment pod, it is possible that the virt-controller doesn't find any active attachment pods and therefore sets the phase of the HP volumes to VolumeBound.
https://github.com/kubevirt/kubevirt/blob/dcfb3ac8763588ae50e450ec28d59e2fadfc1cec/pkg/virt-controller/watch/vmi.go#L2150
This will cause virt-launcher to detach the disks backed by those volumes from the libvirt domain.
When the attachment pod is created again, the phase of HP volumes is set back to Attached/Mounted/Ready and I/O can resume.
What can we do to prevent virt-controller from noticing the absence of attachment pod ?

cc @Vicente-Cheng :point_up:


Moving from Signals 1.5.2 to 1.5.3 (or higher) breaks a simple ToDo test app.

I was seeing some odd Signals behavior with newer versions of Signals and went back to a simple ToDo fork from @tayormi that I had used as a playground to test some simple features and rebuilds.
I used it to identify when things broke.
Code: https://github.com/rydmike/signals_todo_app

Works on: 1.5.2

Breaks on: 1.5.3 or later.

OK 1.5.2
Broken 1.5.3

First error log when using 1.5.3
Performing hot restart...
Syncing files to device macOS...
Restarted application in 428ms.
flutter: Building Todo header
flutter: Building AppBar title

======== Exception caught by widgets library =======================================================
The following LateError was thrown building KeyedSubtree-[GlobalKey#5eb24]:
LateInitializationError: Field '_value@36070010' has not been initialized.

The relevant error-causing widget was:
  Scaffold Scaffold:file:///Users/rydmike/dev/code/signals_todo_app/lib/ui/todo_view.dart:14:12
When the exception was thrown, this was the stack:
#0      _Computed._value (package:signals/src/signals.dart)
#1      _Computed.peek (package:signals/src/signals.dart:955:13)
#2      _onComputedCreated (package:signals/src/devtool.dart:87:23)
#3      computed (package:signals/src/signals.dart:1044:3)
#4      new TodoStore (package:signals_todo_app/core/todo_store.dart:11:18)
#5      todoStore (package:signals_todo_app/core/todo_store.dart:6:29)
#6      todoStore (package:signals_todo_app/core/todo_store.dart)
#7      TodoView.build.<anonymous closure> (package:signals_todo_app/ui/todo_view.dart:26:27)
#8      _WatchState.rebuild (package:signals/src/watch/widget.dart:51:34)
#9      _WatchState.didChangeDependencies (package:signals/src/watch/widget.dart:36:5)
#10     StatefulElement._firstBuild (package:flutter/src/widgets/framework.dart:5620:11)
#11     ComponentElement.mount (package:flutter/src/widgets/framework.dart:5447:5)
#12     Element.inflateWidget (package:flutter/src/widgets/framework.dart:4326:16)
#13     MultiChildRenderObjectElement.inflateWidget (package:flutter/src/widgets/framework.dart:6871:36)
#14     MultiChildRenderObjectElement.mount (package:flutter/src/widgets/framework.dart:6883:32)
...     Normal element mounting (25 frames)
#39     Element.inflateWidget (package:flutter/src/widgets/framework.dart:4326:16)
#40     MultiChildRenderObjectElement.inflateWidget (package:flutter/src/widgets/framework.dart:6871:36)
#41     MultiChildRenderObjectElement.mount (package:flutter/src/widgets/framework.dart:6883:32)
...     Normal element mounting (134 frames)
#175    Element.inflateWidget (package:flutter/src/widgets/framework.dart:4326:16)
#176    MultiChildRenderObjectElement.inflateWidget (package:flutter/src/widgets/framework.dart:6871:36)
#177    MultiChildRenderObjectElement.mount (package:flutter/src/widgets/framework.dart:6883:32)
...     Normal element mounting (178 frames)
#355    Element.inflateWidget (package:flutter/src/widgets/framework.dart:4326:16)
#356    MultiChildRenderObjectElement.inflateWidget (package:flutter/src/widgets/framework.dart:6871:36)
#357    MultiChildRenderObjectElement.mount (package:flutter/src/widgets/framework.dart:6883:32)
...     Normal element mounting (489 frames)
#846    Element.inflateWidget (package:flutter/src/widgets/framework.dart:4326:16)
#847    Element.updateChild (package:flutter/src/widgets/framework.dart:3837:18)
#848    _RawViewElement._updateChild (package:flutter/src/widgets/view.dart:289:16)
#849    _RawViewElement.mount (package:flutter/src/widgets/view.dart:312:5)
...     Normal element mounting (7 frames)
#856    Element.inflateWidget (package:flutter/src/widgets/framework.dart:4326:16)
#857    Element.updateChild (package:flutter/src/widgets/framework.dart:3837:18)
#858    RootElement._rebuild (package:flutter/src/widgets/binding.dart:1334:16)
#859    RootElement.mount (package:flutter/src/widgets/binding.dart:1303:5)
#860    RootWidget.attach.<anonymous closure> (package:flutter/src/widgets/binding.dart:1256:18)
#861    BuildOwner.buildScope (package:flutter/src/widgets/framework.dart:2835:19)
#862    RootWidget.attach (package:flutter/src/widgets/binding.dart:1255:13)
#863    WidgetsBinding.attachToBuildOwner (package:flutter/src/widgets/binding.dart:1083:27)
#864    WidgetsBinding.attachRootWidget (package:flutter/src/widgets/binding.dart:1065:5)
#865    WidgetsBinding.scheduleAttachRootWidget.<anonymous closure> (package:flutter/src/widgets/binding.dart:1051:7)
#869    _RawReceivePort._handleMessage (dart:isolate-patch/isolate_patch.dart:184:12)
(elided 3 frames from class _Timer and dart:async-patch)

I did not go into commit diffs for 1.5.2 to 1.5.3 to try to figure out why this happens.

Looking into it!

Found the issue, it is with devtools, only would cause this error in debug mode.
Will be fixed on the next release

Fixed on 1.5.7
https://github.com/rodydavis/signals.dart/pull/66

Thanks, works again 👍🏻 😃


Show shard in debug logs

What would you like to be added:
Example:
021/06/29 09:38:17.882493 juicefs[10018] <DEBUG>: DELETE chunks/0/0/81_1_4194304 (<nil>, 0.074s)
2021/06/29 09:38:17.967309 juicefs[10018] <DEBUG>: DELETE chunks/0/0/81_2_4194304 (<nil>, 0.085s)
2021/06/29 09:38:18.042025 juicefs[10018] <DEBUG>: DELETE chunks/0/0/81_3_4194304 (<nil>, 0.075s)
2021/06/29 09:38:18.140654 juicefs[10018] <DEBUG>: DELETE chunks/0/0/81_4_4194304 (<nil>, 0.099s)
2021/06/29 09:38:18.230750 juicefs[10018] <DEBUG>: DELETE chunks/0/0/81_5_4194304 (<nil>, 0.089s)
2021/06/29 09:38:18.307321 juicefs[10018] <DEBUG>: DELETE chunks/0/0/81_6_4194304 (<nil>, 0.075s)
2021/06/29 09:38:18.382097 juicefs[10018] <DEBUG>: DELETE chunks/0/0/81_7_4194304 (<nil>, 0.075s)
2021/06/29 09:38:18.459137 juicefs[10018] <DEBUG>: DELETE chunks/0/0/81_8_4194304 (<nil>, 0.076s)
2021/06/29 09:38:18.540659 juicefs[10018] <DEBUG>: DELETE chunks/0/0/81_9_4194304 (<nil>, 0.080s)
2021/06/29 09:38:18.618784 juicefs[10018] <DEBUG>: DELETE chunks/0/0/81_10_4194304 (<nil>, 0.077s)
2021/06/29 09:38:18.696113 juicefs[10018] <DEBUG>: DELETE chunks/0/0/81_11_4194304 (<nil>, 0.076s)
2021/06/29 09:38:18.776318 juicefs[10018] <DEBUG>: DELETE chunks/0/0/81_12_4194304 (<nil>, 0.080s)
2021/06/29 09:38:18.853872 juicefs[10018] <DEBUG>: DELETE chunks/0/0/81_13_4194304 (<nil>, 0.077s)
2021/06/29 09:38:18.929262 juicefs[10018] <DEBUG>: DELETE chunks/0/0/81_14_4194304 (<nil>, 0.074s)
2021/06/29 09:38:19.009402 juicefs[10018] <DEBUG>: DELETE chunks/0/0/81_15_4194304 (<nil>, 0.080s)
2021/06/29 09:38:19.094585 juicefs[10018] <DEBUG>: DELETE chunks/0/0/82_0_4194304 (<nil>, 0.084s)

Here I am actually using 16 shards, so 16 buckets. Showing what shard is being hit would be nice.
Example:
2021/06/29 09:38:19.009402 juicefs[10018] <DEBUG>: [juice-shard-1] DELETE /chunks/0/0/81_15_4194304 (<nil>, 0.080s)
2021/06/29 09:38:19.094585 juicefs[10018] <DEBUG>: [juice-shard-6] DELETE /chunks/0/0/82_0_4194304 (<nil>, 0.084s)

Why is this needed:
Just to have more complete debug logs

If the sharding is abstracted below cached_store that might not be possible though 🤔

@angristan Yes, it's difficult.

No worries then, if it's not worth it, it's not that important!


Polymer 2 support?

Hi,
Thanks for the nice elements!
I'm wondering if I can use your elements with Polymer 2 (currently at 2.0.0-rc.1) ?
If not, when do you plan to support it?
Thanks again!

We are currently finishing up vaadin-grid 2.0. After that, we will do hybrid versions of all of the existing elements (grid, combo-box, date-picker, upload, context-menu, split-layout).
Split-layout already has Polymer 2 support: https://github.com/vaadin/vaadin-split-layout/releases/tag/v1.1.0-alpha1

Closing this issue. You can check the status of Polymer 2 compatibility from the readme, which has links to all the relevant individual issues for each element.


About Section Issue

Hello @codervivek5 ,
About Section issue regarding the footer.
Screenshot

soon will raise a PR

some one already working on this issue so I can't assign it to you at this time.


Error during unserialisation

When uploading images to a product, I'm getting an error during serialization.

This issue exists after the new pull on May 26, 2018 (last commit id a154467e72b77db52ad51cd0f0b445d6f3afbdac).

Hey @jiitpiyush,
Thanks. It looks to be a problem with the new metadata feature I added the other day. :/ I'll get back to you soon.
Regards,
Thai

Hey @jiitpiyush,
I've just pushed up a new version that should address your problem. Can you install and review?
Regards,
Thai

Hi @thaiphan ,
Thank you for your instant reply and bug resolution. That bug is resolved but images are not getting uploaded to my s3-bucket. can you plz look into that?

Were you successfully uploading previously or did it stop working with the latest change?

I take first pull from your repo yesterday and I'm getting issues.

@jiitpiyush So you installed the extension for the first time yesterday?

My region is ap-south-1

Hi @thaiphan, I checked your code and added ap-south-1 region to helper , but still issue persist as media is not uploading to S3. Can you please guide me where to debug?
,

Hi @jiitpiyush,
I think this is a continuation of #4. I'm using Magento's built-in S3 client, which is super old and doesn't support the new V4 Signature Signing. It only supports V2 for the time being. The ap-south-1 region only supports V4 so you unfortunately won't be able to use that region.
Regards,

Hey @jiitpiyush,
I'm closing this issue because I'm tracking it in #4 already. I hope that's okay.
Regards,
Thai


DateTimeOffset should preserve offset

Currently the DateTimeOffset extension method has the unexpected behavior of changing the offset to match that of the current system timezone and does not just set the time as suggested by the name.
This change copies the offset to the new DateTimeOffset

Hello @JProgrammer ,
Thank you for your pull request,
We will review it
Best Regards,
Jonathan

Performance Libraries
context.BulkInsert(list, options => options.BatchSize = 1000);
Entity Framework Extensions • Entity Framework Classic • Bulk Operations •  Dapper Plus
Runtime Evaluation
Eval.Execute("x + y", new {x = 1, y = 2}); // return 3
C# Eval Function • SQL Eval Function


Add Spotify Friends List App

Description
Proposing new Spotify app which displays the last listening history of a random friend off of a user's Spotify friends list.
Copilot

🤖 Generated by Copilot at f09adba
Summary
🎵🧑🤝🧑📄

This pull request adds a new app called spotifyFriends, which shows the latest song played by a random spotify friend. It includes a manifest.yaml file for the app metadata and settings, a README.md file for the app documentation and instructions, and a spotify_friends.star file for the app logic and rendering. The app uses the spotify web player API and the tidbyt standard library.

spotifyFriends app
manifest, README, star
tidbyt welcomes spring

Walkthrough

Create a new app called spotifyFriends that displays the most recently played song for a random spotify friend (link, link, link)
Add a manifest.yaml file that defines the app metadata and settings, such as id, name, summary, description, author, file name, and package name (link)
Add a README.md file that provides a summary, a configuration guide, a demo image, and some acknowledgements for the app (link)
Explain how to obtain and use the sp_dc cookie and the username, which are required to access the spotify web player API, and warn about their sensitivity and expiration (link)
Add a spotify_friends.star file that contains the logic and rendering for the app using the starlark language (link)
Define a main function that takes a config parameter and calls helper functions to get the auth token, the friend data, the cover art, and the index of the random friend (link)
Return a render.Root object that contains the layout and content of the app, such as the friend name, the song title, the artist name, and the cover art (link)
Define a get_schema function that returns a schema.Schema object that defines the fields and icons for the app configuration, such as the sp_dc cookie and the username (link)
Import modules from the tidbyt standard library, such as cache, json, http, random, render, and schema (link)

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


SHA1 files appear on directory listing

Sondre- moving our conversation to github.:)
When I mount a bucket and ls the directory - I'm seeing the a file with the extension .sha1 for each file in my directory. When I try to cat the file, I get the following error: cat: img.jpg.sha1: Bad address.
-- Nilay

This must have been a regression issue, during one of my code cleanups. Try fetching latest now.

Fix exists in commit bfa2f837a2cbc32fce6a2a6a076aac579ab50474

I pulled the new version, and tried it... the .sha1 files are still appearing.
-- Nilay

This is intended behaviour (and is described in the readme). Basically it
exposes the sha1 hashes computed server side for easier comparison with
local variants. With these you could get the hash of the file without
downloading it first. How to disable this function is also described in the
readme.

I should probably make this optional using a command line parameter.
22. des. 2015 20.32 skrev "nilayp"<EMAIL_ADDRESS>
I pulled the new version, and tried it... the .sha1 files are still
appearing.
-- Nilay
—
Reply to this email directly or view it on GitHub
https://github.com/sondree/b2_fuse/issues/2#issuecomment-166710491.

It works. I can now cat the .sha1 files... and hide them with the config flag. Thanks.

I'm going to close this issue now, as the bug in question is actually fixed. If you have further issues or questions, feel free to open another issue ;)


We don't know which are maps and avatars are compatible to load

Metadata

Status: proposed
Deciders: V-Sekai,fire,lyuma
Tags: V-Sekai,

Context and Problem Statement
We don't know which are maps and avatars are compatible to load.
Describe the proposed option and how it helps to overcome the problem or limitation

Add date and version number to maps list

Can also be add xmp metadata packets to each packed scene.
Describe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams
When the user presses launches the game, there should be no unnecessary steps.
Positive Consequences
It is easier to pick content that is loadable.
Negative Consequences
We cannot get other features in.
Option graveyard

Option: The status quo.
Rejection Reason: This solves nothing.

If this enhancement will not be used often, can it be worked around with a few lines of script?

this requires a server change
this requires a godot engine change

Is there a reason why this should be core and done by us?
Usability is a core feature.
References

V-Sekai
KHR_xmp_json_ld

Superseded by: 15c5df140ed9facb4743e83397918f4adaa98070


publish OWL on GFBio

once the csv is updated,

[x] update metadata, e.g. license, contributors, etc.
[x] generate the OWL
[x] add Scripts for producing the OWL to the repository
[x] publish ontology on GFBio

OWL version of the standard is now in this repo, along with the steps to generate it.


Upgrade Tycho to 1.5.1

Since a released version is available, pitclipse should no longer use a
snapshot for builds.

Thanks for the update, I didn't have time to do it! I'll merge it as soon as the CI is happy; I may have to relaunch the build because of #81.


fix(packaging): add dev script

Add the dev script to db workspace.

This PR solves #628

LGTM 🚀

nice!!!


Remove Preparer interface

What does this PR do?
This PR:

Removes the Preparer interface

Fixes #583

Naw, I like the prepare struct name as is.


Spot: Add Set from Map

For a Spot with no geometry add ability to set from map (as point, line or poly)

Added with commit b5bea4c


Task-Filter COs: field synchronize updates remain in filter results

Feature or enhancement
After I update, for example, 3 out of 50 COs using the "field synchronize" tool after a filter search, then select "Back to filter", I only see the 3 COs updated by the field synchronize tool. When I refresh the filter the 3 same COs remain and the filter parameters seem to disappear.
When I select "Back to filter" I would like to see all 50 results from the original filter including blue check mark of those selected to update. When I refresh the filter, the original filter parameters should maintain and I should only see the remaining 47 COs that have not been updated. Right now it seems counter intuitive since the filter should not include the updated COs.
Location
Task-CO filter
Screenshot, napkin sketch of interface, or conceptual description
No response
Your role
No response

@jlpereira Are we sending the checked boxes or the original query that got us here by POST?  Should be the latter.

@jlpereira Are we sending the checked boxes or the original query that got us here by POST? Should be the latter.

It depends, if the user uses the radial linker on the right, it will operate on the selected COs. If they use the one on the right, it will use the query.
To make it work the same way on both sides, we could eliminate all _id parameters, we would have to look for the type of parameter depending on the filter

I do not understand, "It depends, if the user uses the radial linker on the right, it will operate on the selected COs. If they use the one on the right, it will use the query."
I did use the radials on the right though.

When you use the radial linker on the right, only the object IDs will be passed as a parameter to the task. This is why when you press back, it loads the filter with these objects. However, if you use the left radial, all the filter parameters will be passed. When you press the link to return to the filter, it will reload all the results

The radials on the right change/update all COs whether they are blue checked for updating or not, is that correct?

The radials on the left change/update all COs whether they are blue checked for updating or not, is that correct?

Yes, they operate on all results. In this case the Radial linker does not update or change anything, it simply opens tasks with the parameters. If you use the one on the left, it will pass all the filter parameters to the task, if you use the one on the right, it will only pass the id of the objects as a parameter. To give an example, if you opened the Field Synchronize task from the radial linker:
Radial linker on the left:
/tasks/collection_objects/filter?per=50&geo_json={"type":"MultiPolygon","coordinates":[[[[-64.6875,-44.087585],[-64.6875,-30.751278],[-55.546875,-30.751278],[-55.546875,-44.087585],[-64.6875,-44.087585]]]]}&extend[]=dwc_occurrence&extend[]=repository&extend[]=current_repository&extend[]=collecting_event&extend[]=taxon_determinations&extend[]=identifiers&exclude[]=object_labels&page=1
Radial linker on the right:
/tasks/data_attributes/field_synchronize?collection_object_query[collection_object_id][]=1475377&collection_object_query[collection_object_id][]=1476242&collection_object_query[collection_object_id][]=1476984
As you can see, parameters are different. Because you're operating on different things, one operates over filter results by passing all setted parameters and the other operates over selected objects.
Currently, there are two possible solutions for this
The first is to use the radial linker on the left and only update the rows you want in the Field Synchronize task. The other is to continue using the one on the right, but when you open the radial linker, right click on the Field Synchronize slice and click open in a new tab. This way you will open the task in another tab and keep the filter open in a different tab. When you finish working on the Field Synchronize tab, simply close it and refresh the filter results in the other tab.

Thanks José - I think right clicking on the field synchronize slice is my best bet. Thanks for the clarification.


[1.19.4] Xray doesn't function properly

The bug occurs without having Optifine or Optifabric installed? (Optifine bugs won't be fixed)

[X] Yes, I don't have Optifine install.

Mod version
XrayMod-2.3.0
Minecraft version
1.19.4
Mod loader
Fabric
Description of the issue
Before updating from 1.19.3 it functioned as expected however when i updated to 1.19.4 it stopped revealing hidden block faces, it only made walls invisible revealing exposed block faces, i applied Xray Ultimate and that revealed hidden block faces.
Excepted behavior
I was expecting to see hidden block faces {ores hidden in the ground}
Obtained behavior
Blocks were made invisible however only exposed block faces were visible.
How to reproduce
Join a vanilla server
Enable Xray
Observe
Apply Xray Ultimate
Observe
Do I want to contribute to fix it?
Maybe
Something else?
No response

Do you have installed rubidium? It is optimalization mod too as optifine and it too breaks the mod

The MoreCulling mod's Advanced Blockstate Culling option is another cause

I don't have MoreCulling or Rubidium installed, i'm using Fabulously Optimized with convenience and control mods.

The Fabulously Optimized modpack includes More Culling - are you saying you've removed the mod?


Build failed in node 20 related to tslib

Context
I'm trying to build latest changes in main branch using node v20
Node version: 20.11.1
yarn version: 1.22.19
Platform: Darwin Kernel Version 22.6.0 arm64
Current Behavior
Build is failing with error:
Error loading `tslib` helper library.
[!] Error: Package subpath './package.json' is not defined by "exports" in elements/node_modules/rollup-plugin-typescript2/node_modules/tslib/package.json
Error: Package subpath './package.json' is not defined by "exports" in elements/node_modules/rollup-plugin-typescript2/node_modules/tslib/package.json
    at exportsNotFound (node:internal/modules/esm/resolve:303:10)
    at packageExportsResolve (node:internal/modules/esm/resolve:650:9)
    at resolveExports (node:internal/modules/cjs/loader:591:36)
    at Function.Module._findPath (node:internal/modules/cjs/loader:668:31)
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:1130:27)
    at Function.Module._load (node:internal/modules/cjs/loader:985:27)
    at Module.require (node:internal/modules/cjs/loader:1235:19)
    at require (node:internal/modules/helpers:176:18)
    at Object.<anonymous> (elements/node_modules/rollup-plugin-typescript2/src/tslib.ts:11:23)
    at Module._compile (node:internal/modules/cjs/loader:1376:14)

Expected Behavior
Build success
Possible Solution(s)

Yeah, it works best with Node v16 and Yarn 1.22.x

Possibly related: https://github.com/microsoft/tslib/pull/135


liberation-fonts: broken hinting in 2.00 ?

Issue description
With antialiasing turned off liberation fonts 2.00.1 (default in nixos) look weird, some lines have double width:

liberation fonts 1.07.4 (default in Ubuntu, even in Ubuntu 17.04) do not have the problem

Wasn't it to early to upgrade to 2.00 ?
Steps to reproduce

turn antialiasing off in desktop manager setting
pango-view   --font='Liberation Serif 12' --markup   --text 'abcdefghijklmnopqrstuvwxuzABCDEFGHIJKLMNOPQRSTUVWXUZ'
pango-view   --font='Liberation Sans 12' --markup   --text 'abcdefghijklmnopqrstuvwxuzABCDEFGHIJKLMNOPQRSTUVWXUZ'
pango-view   --font='Liberation Mono 12' --markup   --text 'abcdefghijklmnopqrstuvwxuzABCDEFGHIJKLMNOPQRSTUVWXUZ'

Technical details

System: (NixOS: nixos-version, Ubuntu/Fedora: lsb_release -a, ...)
17.03.git.d2d7740 (Gorilla)
Nix version: (run nix-env --version)
nix-env (Nix) 1.11.5
Nixpkgs version: (run nix-instantiate --eval '<nixpkgs>' -A lib.nixpkgsVersion)
"17.03.git.d2d7740f1bM"

2.x is really a different font, as I understand it.

"On Jul 18, 2012, Liberation fonts 2.00.0 version is released based on croscore fonts to resolve long standing licensing problem and also get more coverage present in croscore fonts."

Should we have both (1.07 and 2.00) in nixpkgs then ?


feat: bump cosmwasm version #LSC-315

Updated cosmwasm version and dependent stuff

this looks good. is it okay if we keep this open for some time until you successfully run your first integration test?


Ordered message with same shardingKey may parallel consume when it's repeat

As the tittle said, In our business scene, I using the uniqueId as shardingKey to send Order Message.
When the Consumer start, the processing is as follow:
"select uniqueId from bussiness Database", if Not exist, INSERT, else UPDATE
but, I found that the same uniqueId has double INSERT...
So, after checking bussiness code, I guess Ordered message with same shardingKey may parallel consume when it's repeat

Maybe because you are consuming messages in concurrently mode


Fix testutils on windows

Checklist

[ ] I tested all changes and all related features with different users (student, tutor, instructor, admin) on the test server https://artemistest.ase.in.tum.de.
[ ] Server: I added multiple integration tests (Spring) related to the features
[ ] Server: I added @PreAuthorize and check the course groups for all new REST Calls (security)
[ ] Server: I implemented the changes with a good performance and prevented too many database calls
[ ] Server: I documented the Java code using JavaDoc style.
[ ] Client: I added multiple integration tests (Jest) related to the features
[ ] Client: I added authorities to all new routes and check the course groups for displaying navigation elements (links, buttons)
[ ] Client: I documented the TypeScript code using JSDoc style.
[ ] Client: I added multiple screenshots/screencasts of my UI changes
[ ] Client: I translated all the newly inserted strings into German and English

Motivation and Context

On windows the package name is reported with a leading .
This change handles the situation and makes structural tests run on windows
Description

Steps for Testing

Run structural tests on a windows machine

Note: feel free to reject this pull request if you need it additional test or anything for this, I just wanted to raise the issue and propose a fix

Thanks for this contribution. I don't really understand why this happens on Windows machines. Could you quickly explain this?

I actually also don't know why it happens but on windows all structural tests fail with a message similar to
The class Range has the correct name, but the package it's in, [.pgdp.iter], deviates from the expectation.  Make sure it is placed in the correct package.
And this change would fix that behaviour


W-14082819 - Added Release Notes and updated reference links to R2.20

@ppalu Approved for Production but please confirm that these changes have also been published to the Beta site, with links to the Staging org instead of public Exchange. Thanks.


Migration of Tests for Refactoring Branch (WIP)

Pull Request Test Coverage Report for Build 5027

36 of 37 (97.3%)  changed or added relevant lines in 17 files are covered.
8 unchanged lines in 2 files lost coverage.
Overall coverage increased (+4.9%) to 28.833%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/pages/academy/grading/subcomponents/GradingWorkspaceContainer.ts
0
1
0.0%

Files with Coverage Reduction
New Missed Lines
%

src/commons/application/ApplicationTypes.ts
4
76.0%

src/commons/workspace/WorkspaceReducer.ts
4
92.04%

Totals

Change from base Build 5026:
4.9%

Covered Lines:
3801

Relevant Lines:
11724

💛  - Coveralls


Change the year for semesters to be academic year

Ex. The year "2017" should be the academic year "2017-18"

duplicate of #134


Add type AST

This adds #to_ast methods too all types. We need this in order to be able to dump types into ASTs and transform them into slightly different types. ie in rom-rb we'll be able to take database schema attribute types, and convert them to different types that are more suitable for other contexts, like struct attributes.
TODO

[x] Definition#to_ast
[x] Sum#to_ast
[x] Constrained#to_ast
[x] Constructor#to_ast
[x] Hash#to_ast
[x] Hash::Schema#to_ast
[x] Hash::Permissive#to_ast
[x] Hash::Strict#to_ast
[x] Hash::StrictWithDefaults#to_ast
[x] Hash::Weak#to_ast
[x] Hash::Symbolized#to_ast
[x] Array#to_ast
[x] Array::Member#to_ast
[x] Enum#to_ast
[x] Safe#to_ast
[x] Tweak existing compiler to work with the AST (currently it relies on ASTs that include type identifiers from the builtin registry, we may want to make that available via meta so that when types are registered we set ie meta(identifier: 'strict.int') and then meta data can be included in ASTs so that compiler can reuse existing built-in types

@solnic I added the missing ast I left some comments, so feel free to add anything.
I think it will be more clear once we start working on the compiler 😄

At the end I decided to remove the to_ast from Array and Hash, since the inherit the one from Definition

@solnic anything else? :)

@GustavoCaso @flash-gordon I left a couple comments, all related to the same small issue

@flash-gordon @solnic I apply the changes hope everything is as expected 😄

I rebased and force-pushed the branch

I think this is good-enough to be merged, there's just one caveat - it breaks dry-validation. I propose creating release-0.10 branches in dry-v and dry-t and start treating master as a bleeding edge targeting 0.11 releases. WDYT?

yeah, sounds like a plan, I'll use this branch to start the work on dumping rom schemas to ast

@flash-gordon OK, let's get this party started then :)

This is now merged. Thank you @GustavoCaso for this effort and let's continue polishing/finishing stuff for 0.11. I'll cut a release-0.10 branch too for the ongoing maintenance.


about delight

https://github.com/delight-dev/Delight
i think it can help you to make soming.

@zero16832 did you use it? What do you like most about it?

ReactUnity is going to have a material design library at https://github.com/ReactUnity/material. So, it is similar in that. Other than that, I think ReactUnity is going to be much more flexible and customizable.
Here is a little sneak-peek of material design.


Edits to Working with GitHub document

Description
This PR makes a few edits to the Working with GitHub document:

Corrects use of username to <your-user-name> in code snippets in the SSH section (related to discussion in #874)
Changes SSH key section intro to past tense
Replaces a few hardcoded URLs with existing AsciiDoc attributes
Converts explicit URLs to hyperlinks in a few places

The plan is to include these changes when bringing this document up to date in the support/lisf-public-7.3 branch in a subsequent PR.

Re: section 4.3.3
I decided to go with the "fix" shown below. The SSH URL forms described roughly align with GitHub's docs, where user can be a username or an organization. The snippet then shows both examples in a common use case.

Now you will have to use SSH URLs which take the form git@github.com:user/repository.git by default. However, the additions made to your ~/.ssh/config file above allow you to simplify this to github:user/repository.git. For example:
# Cloning your LISF repository
% git clone github:<your-user-name>/LISF.git

...
# Adding a remote repository
% git remote add upstream github:NASA-LIS/LISF.git

Did @jvgeiger weigh in on whether this should be committed to master or to support/lisf-public-7.3?  I'd like that resolved before approving this.

@emkemp, not yet. I figure we can push these changes onto master then update support with the full set of changes.

I am fine with these changes, and with the plan to merge this PR into master first, and then later update the public support.
If there's no objections in an hour or so, I will merge this PR.


HISTORY VALIDATION! (untested)

A long time coming -- this should, in theory, allow us to pull transcriptions that were removed by the Reddit global spam filter from the user's history and run the validation against that instead. It's not very many extra steps and it doesn't need to run that often -- it will be extremely useful when volunteers start posting in subs they don't frequent, like r/4chan.
This is untested currently -- I'd like an initial code review for now and will test tomorrow evening when I'm more awake.
TODO:

[ ] Add additional check that the author of the parent posts match as well as the titles, as this is an avenue for cheating the system
[ ] Update changelog
[ ] Update version number
[ ] Test the sucker

for doohickey in post.author.new(limit=3):

QUALITY

@perryprog you would not believe how many of my variables start out life as doohickey. This one just accidentally made it into the codebase.

Yeah, I'm gonna need us to get rid of all the doohickeys before we merge this... 😆

@TheLonelyGhost This is ready for another round of review -- I've got time to do a deploy tomorrow if you have time to take a look at this.

I'm just commenting here so it looks like I helped


Don't remove or rewrite selected views when the code breaks.

Fixes #1310.
Problem:
At certain points with a particular timing if the code would produce an error the navigatorTargets end up empty, if the mouse position trigger came in at that point the selected views would be set to an empty array.
Fix:
The solution was to attempt to keep the selected items as much as possible, by both avoiding updating the selection if the canvas appears to be broken and removing the call to the function that eliminates the "invalid" selections and highlighted views if they don't exist anymore.
Commit Details:

Fixes some unrelated issues in processErrorWithSourceMap that logged
out a lot of console errors.
Ensures that backspace in VS Code still triggers a cursor position
changed event as apparently they come without a kind property.
Removed the call to removeNonExistingViewReferencesFromState as
we want those fields to survive a broken canvas.
Refactored out the logic for updating the selection based on the
cursor position and added in check to see if the canvas appears to be
broken current, which doesn't update the selected elements.

I've just tried this with the "link to the test editor".
Annoyingly whether or not I get a selection on the canvas for me is still more or less random (see video) - however, the code editor annotation (blue bar on the left) now seems to get this right, so hopefully the canvas issue is orthogonal?
https://user-images.githubusercontent.com/2945037/120016594-b2e51500-bfdc-11eb-9761-6c7ad71ee83c.mp4


Aggregation

This PR enables you to query data on the server with a schema that does not match a database collection - for example an aggregation or an array of objects
PR for the documentation is here
Added new function registerCustomQuery(), to add a custom GraphQL type generated from a schema object and a resolver to query the data
Added new function registerCustomDefaultFragment(), to generate a default fragment from the same schema
Updated multi2 to be compatible with custom queries - you can now specify a typeName instead of a collection
Updated createSchema() to support SimpleSchema Shorthand Definitions
Added defaultCanRead parameter to createSchema()

@eric-burel Before I complete this I would like your feedback - because it was very useful last time. Originally I was going to call this registerAggregation() but then I realized that it has wider applications than just aggregation - though I am afraid the name registerCustomQuery() is not as clear.

Thanks a lot! It will take me some time to review because this is an interesting feature but with lot of consequences. So I'll try to go step by step, first understanding the scope/use cases.
Do I get it correctly if I say that the point of this feature, is to be able to reuse useMulti on those custom data? Because currently we already have the ability to create custom resolvers, and I think we do use that at Live for good for this use case (@EloyID) ?
I guess you can't use a custom multi resolver tied to a collection, because this will have the side effect of creating an empty collection in Mongo?
Note that in Vulcan Next those problem are kind of obsolete, because you are able to create "Models" without Mongo => it's quite easy to create an "Agent" model like in your example whose data is stored in a local array. Instead of creating a custom resolver, you create a custom connector, replacing the db level logic (literraly the model in an MVC approach, instead of the Controller). There are premises of this in Vulcan Meteor but the limitation is that you can't create connectors in user land.

Hi, for me this is very useful
I had to create a query only because we wanted to filter by the field of a related collection, and then you lose all the advantages of useMulti. I think I did not code it very nicely so I had cache problems.
The only problem I can see it's that when aggregating, if you  have to query all the docs and then pass them to apply new filtering; it won't be very performing for big databases. I don't understand well useMulti, but can't we just give the option to inject some aggregation steps in the useMulti2 query to create the type of documents we want and then we let the input filters work ?
Hope it helps, nice feature!

This would raise security issues, you don't want users to be able to compute aggregates. Technically we could, but you'd need to create a whole new layer of security to check if the user is allowed to compute some aggregations, and I think it would be extremely difficult/maybe not even possible. Aggregations are quite complex in Mongo.

But as you can alreday create hasOne or hasMany relationship you could config the fields of the related collection to be also filterable

I think if using $lookup is one of the main use cases, perhaps it can be tied into the relations part of the schema definition?

@EloyID

The only problem I can see it's that when aggregating, if you have to query all the docs and then pass them to apply new filtering; it won't be very performing for big databases. I don't understand well useMulti, but can't we just give the option to inject some aggregation steps in the useMulti2 query to create the type of documents we want and then we let the input filters work ?

Actually you can pass an input prop to the aggregation, like you can to any multi query, which can include a filter:
const input = {
  filter: {
    supplierCode: { _eq: "190" }
  },
};
const queryOptions = {
  typeName: 'ScrubErrorsSummaryAggregate',
  fragmentName: 'ScrubErrorsSummaryAggregateFragment',
  input,
};
const useMultiResults = useMulti2(queryOptions);

The input is passed to the custom query resolver, where you can use it to modify your aggregation:
const resolver = async function (root, { input }, context) {
  const { filter } = input;
  const { currentUser } = context;

  const pipeline = [
    // pipeline stages
  ];

  if (filter?.supplierCode?._eq) {
    pipeline.splice(0, 0, {
      $match: {
        supplierId: filter.supplierCode._eq,
      },
    });
  }

  let docs = await Products.aggregateAsync(pipeline);
  // filter or restrict docs
  return { results: docs, totalCount: docs.length };
};

const filterable = [{
  name: 'supplierCode',
  type: 'String',
}];

registerCustomQuery({
  typeName: 'ScrubErrorsSummaryAggregate',
  description: 'Aggregate products grouped and scrub error',
  schema: scrubErrorsSummaryAggregateSchema,
  resolver,
  filterable,
});

I will probably add a full working example in Vulcan Starter.
@Neobii Right now you have to write the pipeline stages yourself, but you are right, in the future we could maybe auto-generate them using relations and other info in the schema.


Hotfix/fix to dev certs #396

It's good to have a config file so we just need to change it in order to let haukins run in different machines but at the same time i think that all those certificates might be a problem when some one what to run haaukins in his local machine.
With this pull request we have basically added more complexity to run haaukins in local.
N.B the file svcs/amigo/app/main.go have to changed a little bit in order to have the possibility to get data from the DB in sec01

Yeah,  but as I mentioned you over slack and I noted on the code, handling of configurations and certs will be altered soon (I hope).


Revert basic.sh and private.sh

Revert the basic.sh and private.sh tests for now.
@zmerlynn @filbranden

LGTM.


fix provider normalization

What this PR does / why we need it:
The provider labels in the component descriptor are not normalized correctly.
For details, see the issue #477
This fix now assures, that the provider labels are normalized correctly in all combinations (norm algo/serialization format).

norm/v1 CD v2
norm,/v1 CD v3
norm/v2

Relates to #469.
Which issue(s) this PR fixes:
Fixes #477
Special notes for your reviewer:
Release Notes:

Wxample:  https://github.com/open-component-model/ocm/blob/a45c3c0527da39f9d1707b08d4fc8ca521176ea5/pkg/contexts/ocm/compdesc/norm_test.go#L210-L246


publish<EMAIL_ADDRESS>

Requested by: @adinauer
Merge target: (default)
Quick links:

View changes
View check runs

Assign the accepted label to this issue to approve the release.
Leave the #retract comment under this issue to retract the release (original issuer only).
Targets

[ ] symbol-collector
[ ] maven
[ ] github
[ ] registry

Targets marked with a checkbox have already been executed.  Administrators can manually tick a checkbox to force craft to skip it.

OTEL modules were missing in 6.9.0 because they are in a subfolder that wasn't picked up when I started the 6.9.0 release and changing configs after the fact had no effect. So re-releasing to include the missing modules.


How could I get unseen.npy of cull_replica_mesh?

You provided cull_mesh.py to get cull_replica_mesh, but how to get the corresponding unseen.npy?

unseen.npy is the unseen vertices stored in npy file format.

@Zzh2000  If I don't have unseen.npy how to use the eval_recon.py you provided？

If you are trying to test on some other datasets other than Replica, you can easily generate unseen.npy yourself.

@Zzh2000 For me, I am using the Replica dataset, but it is a different trajectory pose. After I use cull_mesh.py to get the corresponding cull_mesh, I don’t know how to get your so-called unseen points, because the number of vertices in cull_mesh.ply and the original mesh.ply is the same.

I still didn't get how the unseen.npy is generated, and it turns out that the unseen vertices from office_0 in replica look like this

which is not the unseen part of the point cloud(mesh). Could you please elaborate more about the setting of getting unseen.npy ?


Develop

Coverage remained the same at 100.0% when pulling 5d2d00ef0ae1bbba55db7eb66bbb68fba5361019 on develop into 9551d71924027d9cd11d4125310c3742f836785a on master.


Removes docs from repo in favour of using cert-manager.io

The corresponding cert-manager.io PR is here.
/hold
until the website PR is merged.

/hold cancel

/retest


Split Altair MooseFS chunkserver into 4

We're moving towards 4+2 erasure coding, migrating from 2 chunkservers (and straight 2x replication). This will require a temporary outage where we split a JBOD into four parts, and connect it to four independent chunkservers. We'll do one JBOD at a time, to minimise the number of chunks that go unavailable during that time.
This covers the first phase

Nicely done!


Variadic template impl for CreateAndStart

Less code is good code.

Can you update the title to be different than your previous PR, and describe what you changed and why? Alternatively can you merge your two PRs as as they are basically doing the same thing?

Sure. Hey, I'm learning about this git stuff, too :)