Get error when trying to edit product option in 2nd language

Lunar version: 0.8
Laravel Version: 9.52.16
PHP Version: 8.3.3-1
Database Driver & Version: pgsql,  ver. 15

Expected Behaviour:
Edit the Ukrainian option's name (or any other) language, save it, and use it without errors.
Actual Behaviour:
When I started to write a value into the proper field - please see the screenshot

just after 2nd letter the form gets submitted and produces the error

Lunar\Models\ProductOption::Lunar\Models{closure}(): Argument #1 ($value) must be of type string, null given

Steps To Reproduce:
All steps are made in the admin 'Settings' area.

add new language, don't set it as default. In my case, it's Ukranian' with the original name "Українська" and with the code 'uk'.
click Options under the topic 'Product' and then for the 'Size' option choose the right context menu, where choose 'Edit Option'.
For the field 'Name' click the button 'Locales' then you'll see all locales you created with the field, as you see on my screenshot.
print localized option name. In my case, it's 'розмір' but I can't add more than 2 letters.

This will be fixed in 1.0.0-alpha.36

This will be fixed in 1.0.0-alpha.37

OK


⚠ Samsung has degraded performance

In 56dcef2, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 3129 ms

Resolved: Samsung performance has improved in 170f277.


IP not re-inserted after purge when service becomes available again

I am testing with 3 traefik instances. nomad-external-dns correctly adds all three IPs to the DNS A record on startup. If I take a server offline (pausing the VM node) the downed IP is correctly purged from R53. However, when the node comes back up again the DNS records do not update to add back in the missing IP.

Can you check if the service is listed correctly after the node comes up again?
By default, it takes 10s before the program re-fetches the list of services: https://github.com/mr-karan/nomad-external-dns/blob/main/config.sample.toml#L5. You can configure this interval to be lower, based on your requirements as well.

This should ideally be fixed with https://github.com/mr-karan/nomad-external-dns/pull/6


Force HTTPS on diesel.rs website

Because why not, in 2017? I had to manually enter the "s" into the URL to see that the site supports it but by default I arrived on http version using Qwant search engine. Also the website is easy to remember but when I enter it in browser address bar it will send me to the http version.
I have tried to search for any similar issue but only stumbled upon #808. #800 may be related to that too.
Related help page: https://help.github.com/articles/securing-your-github-pages-site-with-https/
Addentum: all links in README redirect to http pages, this is sad.

I think the problem is that github pages don't allow you to force https if you're using a custom domain (which of course we are).

We can configure this in Cloudflare. I think it's already using the
"opportunistic SSL" stuff of http2.
Bastien Orivel<EMAIL_ADDRESS>schrieb am Sa. 5. Aug. 2017 um
12:32:

I think the problem is that github pages don't allow you to force https if
you're using a custom domain (which of course we are).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/diesel-rs/diesel/issues/1073#issuecomment-320436172,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABOX1IYBENsT2QzLwJLihwIdItlsOHnks5sVETGgaJpZM4OuaHP
.

Just had a look and we are using

Opportunistic Encryption
Opportunistic Encryption allows browsers to benefit from the improved performance of HTTP/2 and SPDY by letting them know that your site is available over an encrypted connection. Browsers will continue to show "http" in the address bar, not "https".

but not

Always use HTTPS
Redirect all requests with scheme "http" to "https". This applies to all http requests to the zone.

I don't really have a strong feeling for or against forcing it, but we should make sure everything on the domain actually works with HTTPS first.

@sgrif the only external resources are code.jquery.com and Google Fonts, both are already using HTTPS.
The intra-site links seem to assume HTTP, i.e., https://diesel.rs links to http://diesel.rs/guides/. Not sure why. Also, there's a typo in the "canonicical" meta tag here.
tl;dr I think we can just enable "Always use HTTPS".

:+1: from me then.

I've been making it a point to ensure as little assumes protocol as possible. So if you're using https, you should stay in https. However, right now our SSL support is implemented by basically having Cloudflare do a giant MITM attack on us. Until we have "proper" SSL support (which is unlikely to happen until github pages supports it for custom domains), I don't think it makes much sense to force its usage.

@sgrif Looks like this could be resolved now


added stars count for Blazorise

I have placed it on the third place by the stars count.

Well done, thank's!


Attempt at timing out slow operations at the socket level

This is still a work in progress (it lacks proper tests for the timeout case) just wanted to get early feedback at what I'd discussed with @wvanbergen.

Thinking about this a little more it is a bad idea on SSL connections, it will split the SSL packages.


Simplest example results in a warning

import std.stdio;

import concurrency.operations.via;
import concurrency.thread : ThreadSender;
import concurrency : syncWait;

struct ValueSender(T) {
    alias Value = T;
    T value;
    static struct Op(Receiver) {
        Receiver receiver;
        T value;
        void start() {
            receiver.setValue(value);
        }
    }

    Op!Receiver connect(Receiver)(Receiver receiver) {
        // ensure NVRO
        auto op = Op!(Receiver)(receiver, value);
        return op;
    }
}

auto just(T)(T t) @safe {
    return ValueSender!T(t);
}

void main()
{
    auto w = just(42).via(ThreadSender()).syncWait();
    writeln(w.value);
}

On DMD  v2.100.0 I get:
Warning: ValueSender!int's operation state is not returned via the stack

I'm not sure I understand the warning?

Never mind, I realized that ValueSender already exists in concurrency.sender.
I used the example in the README, so maybe it needs to be updated if it's not doing proper NRVO?
I'll close this for now.

And just for reference, the fix is to disable the copy ctor:
diff --git a/source/app.d b/source/app.d
index bdca070..c49171d 100755
--- a/source/app.d
+++ b/source/app.d
@@ -8,6 +8,8 @@ struct ValueSender(T) {
     alias Value = T;
     T value;
     static struct Op(Receiver) {
+        @disable this(ref return scope typeof(this) rhs);
+        @disable this(this);
         Receiver receiver;
         T value;
         void start() {

thx https://github.com/symmetryinvestments/concurrency/commit/29e09e88dd9bfd102374ffeb3d6cdab9447aa020


Transitions don't get restored when style un-applied

After transitions are applied to a control from a style, the original transitions don't get restored when the style no longer applies:
        [Fact]
        public void Style_Replaces_Existing_Transitions()
        {
            using (UnitTestApplication.Start(TestServices.StyledWindow))
            {
                var xaml = @"
<Window xmlns='https://github.com/avaloniaui'
             xmlns:x='http://schemas.microsoft.com/winfx/2006/xaml'>
    <Window.Styles>
        <Style Selector='Border.foo'>
            <Setter Property='Transitions'>
                <Transitions>
                    <DoubleTransition Property='Height' Duration='0:0:1'/>
                </Transitions>
            </Setter>
        </Style>
    </Window.Styles>
    <Border>
        <Border.Transitions>
            <DoubleTransition Property='Width' Duration='0:0:1'/>
        </Border.Transitions>
    </Border>
</Window>";
                var loader = new AvaloniaXamlLoader();
                var window = (Window)loader.Load(xaml);
                var border = (Border)window.Content;

                Assert.Equal(1, border.Transitions.Count);
                Assert.Equal(Border.WidthProperty, border.Transitions[0].Property);

                border.Classes.Add("foo");

                Assert.Equal(1, border.Transitions.Count);
                Assert.Equal(Border.HeightProperty, border.Transitions[0].Property);

                border.Classes.Remove("foo");

                Assert.Equal(1, border.Transitions.Count);
                Assert.Equal(Border.WidthProperty, border.Transitions[0].Property);
            }
        }

This issue supersedes #3883 after testing against CSS' behavior.

I think we can resolve this to make transitions in styles work as in CSS by making the Transitions property a styled property, however there are a few questions:

Do we want to follow CSS' behavior here? (i.e. transitions from styles overwrite rather than stack)
What should we do about the fact that the transitions collection in the setter will be shared between control instances?

We could clone the collection for each control it's applied to
We could make the Transitions collection read-only if it's added to a setter using ISetterValue


bug graphic beta 12 essentia displays behind jars

when viewing essentia with goggles of revealing while appearing above the jar you are looking at it will also appear behind any other jars that overlap where the essentia is displayed

Why on earth is somebody reporting bugs from an outdated version?
Whats this madness..!?!

Because i have not had a chance to update to b13 and since i havent seen this bug posted it is likely that it still persists

Unfortunately this is a rendering order issue in MC itself - no easy way to fix this.


Make reshard work with streams too

Internally, reshard used streams already, so it is only a matter of changing the API and connecting things together

@eriktaubeneck This may be what you want. This PR is not complete (I just quickly draw an API change), so we can't merge it, but the only thing that is missing is test coverage.

test added @akoshelev


Integrate GMW Crates

Add an integration endpoint for GMW Crates. Possibly add a general endpoint for crate plugins, and then combine HuskyCrates and this?

Having both of them integrated would be awesome, I love them both equal.

Partially implemented in v5.2.0


CV1 resolution not correct

cv1 has 2160x1200, not 2560x1440

Was stopping by to say the same - given it hasn't been changed it a year I suppose it won't be.  It's a shame as it's a cool tool and it's going to give people incorrect data about the CV1.


ASSETS-88895 : Show HCV report pages to limited users

Workfront Task : Show HCV report pages to limited users
Test URLs:
Before: https://main--assets-distribution-portal--adobe.hlx.page
After: https://assets-88895--adobe-gmo--hlxsites.hlx.page/drafts/tyrone/assets

Authoring
Created page /sites/HelixProjects/Shared Documents/sites/adobe-gmo/asset-distribution-portal/drafts/tyrone/marketing-dashboard.docx
with metadata

Updated config file /sites/HelixProjects/Shared Documents/sites/adobe-gmo/asset-distribution-portal/drafts/tyrone/admin-config.xlsx
Added new row
imsReportingGroup : IMS-QA-HCV-Reporting-group

Updated config file /sites/HelixProjects/Shared Documents/sites/adobe-gmo/asset-distribution-portal/drafts/tyrone/site-config.xlsx
Added worksheet shared-quicklinks
Added new column Group
Added new row
Marketing Dashboard : /marketing-dashboard : imsReportingGroup

@TyroneAEM Do you still need reporting-access= true metadata on page level also? Can you check only based on Group column added in site-config.xlsx?


RepaintBoundary.toImage does ignore Images in Flutter Web

This issue can be reproduced with the following code https://github.com/JohannesMilke/convert_widget_image_example.
Issue:
A listitem widget with an image displays correctly in the flutter widget tree, but after taking a snapshot with RepaintBoundary.toImage the resulting snapshot image does not contain the image inside the listitem
Flutter doctor -v
[√] Flutter (Channel stable, 3.0.1, on Microsoft Windows [Version 10.0.22000.675], locale en-DE)
• Flutter version 3.0.1 at C:\Users\flutter\beta\flutter_windows_1.25.0-8.2.pre-beta\flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision fb57da5f94 (12 days ago), 2022-05-19 15:50:29 -0700
• Engine revision caaafc5604
• Dart version 2.17.1
• DevTools version 2.12.2
[√] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
• Android SDK at C:\Users\AppData\Local\Android\Sdk
• Platform android-32, build-tools 31.0.0
• Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 11.0.12+7-b1504.28-7817840)
• All Android licenses accepted.
[√] Chrome - develop for the web
• Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
[√] Visual Studio - develop for Windows (Visual Studio Enterprise 2019 16.11.8)
• Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise
• Visual Studio Enterprise 2019 version 16.11.32002.261
• Windows 10 SDK version 10.0.19041.0
[√] Android Studio (version 2021.2)
• Android Studio at C:\Program Files\Android\Android Studio
• Flutter plugin can be installed from:
https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.12+7-b1504.28-7817840)
[√] VS Code (version 1.67.2)
• VS Code at C:\Users\AppData\Local\Programs\Microsoft VS Code
• Flutter extension version 3.40.0
[√] Connected device (3 available)
• Windows (desktop) • windows • windows-x64    • Microsoft Windows [Version 10.0.22000.675]
• Chrome (web)      • chrome  • web-javascript • Google Chrome 102.0.5005.61
• Edge (web)        • edge    • web-javascript • Microsoft Edge 101.0.1210.53
[√] HTTP Host Availability
• All required HTTP hosts are available

Hi @smedasn, I am not sure I understand what this issue is reporting. Do you mean the images do not load in flutter web when using toImage? if so, can you please check if this is the same issue  #103803 you are reporting?  If not, then please update the issue description with more details along with the
output of flutter doctor -v.
Thanks!

I have the same issue. In my szenario I want to print a card element with a decorationimage and text elements. the toImage() method does only render Flutter Widget elements and ignores the decorationimage

it looks like the command "flutter run -d chrome --web-renderer canvaskit --dart-define=BROWSER_IMAGE_DECODING_ENABLED=false --release" solves the issue.

@maheshmnj it looks either it is the same or a very similar issue!

It looks the same to me closing in favor of #103803


Modules 4A-J (Imaging) Need Created

4A - Pinned 2D photo-stacked specimen imaging
4B - Pinned 3D specimen imaging
4C - Enveloped/flat (dragonfly?) Imaging
4D - Frozen/tissue imaging (subcase of "wet" museum specimens?)
4E - Slide photo-stacked imaging
4F - Slide label/low-res imaging
4G - Wet photo-stacked imaging
4H - Dry Bulk low-res Imaging
4I - Wet Soup low-res Imaging
4J - Image Processing

eeaa1e0 created last one


EPEERINVALID when using rxjs-run and node 4

Code to reproduce the issue:
<EMAIL_ADDRESS>npm --version                                                                          [15:12]
2.15.8
<EMAIL_ADDRESS>node --version                                                                         [15:13]
v4.4.7

package.json:
{
  "name": "cycle-test",
   "version": "1.0.0",
   "description": "",
   "main": "index.js",
   "scripts": {
     "test": "echo \"Error: no test specified\" && exit 1"
   },
   "dependencies": {
     "@cycle/rxjs-run": "^3.0.2",
     "rxjs": "^5.0.0-beta.10"
   },
   "author": "",
   "license": "ISC"
}

and then run npm install
Expected behavior:
The installation should happen without error
Actual behavior:
npm ERR! node v4.4.7
npm ERR! npm  v2.15.8
npm ERR! code EPEERINVALID

npm ERR! peerinvalid The package<EMAIL_ADDRESS>does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants rxjs@*

Versions of packages used:
See package.json.
Is it related to the beta status of rxjs package?

@BenoitAverty can you try using npm v3? I see you're using npm v2.15.8

Yes it works fine with npm3. I was only wondering if it's normal that cycle can't be used with npm2, it being shipped with a LTS release of node. I agree that it's not blocking for the majority of people.


minor improvement

The s.mcpOptions assignment snippet would be unnecessarily run multiple times in case the length of s.mesh.ConfigSources is greater than 1.

@leowucn: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-framework-k8s-tests_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test integ-framework-k8s-tests_istio

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

@leowucn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-framework-k8s-tests_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test integ-framework-k8s-tests_istio

integ-pilot-local-tests_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test integ-pilot-local-tests_istio

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

@leowucn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-framework-k8s-tests_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test integ-framework-k8s-tests_istio

integ-pilot-local-tests_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test integ-pilot-local-tests_istio

integ-istioio-k8s-tests_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test integ-istioio-k8s-tests_istio

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

@leowucn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-framework-k8s-tests_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test integ-framework-k8s-tests_istio

integ-pilot-local-tests_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test integ-pilot-local-tests_istio

integ-istioio-k8s-tests_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test integ-istioio-k8s-tests_istio

pilot-e2e-envoyv2-v1alpha3_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test pilot-e2e-envoyv2-v1alpha3_istio

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

@leowucn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-framework-k8s-tests_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test integ-framework-k8s-tests_istio

integ-pilot-local-tests_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test integ-pilot-local-tests_istio

integ-istioio-k8s-tests_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test integ-istioio-k8s-tests_istio

pilot-e2e-envoyv2-v1alpha3_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test pilot-e2e-envoyv2-v1alpha3_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

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

@leowucn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-framework-k8s-tests_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test integ-framework-k8s-tests_istio

integ-pilot-local-tests_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test integ-pilot-local-tests_istio

integ-istioio-k8s-tests_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test integ-istioio-k8s-tests_istio

pilot-e2e-envoyv2-v1alpha3_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test pilot-e2e-envoyv2-v1alpha3_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

pilot-multicluster-e2e_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test pilot-multicluster-e2e_istio

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

@leowucn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-framework-k8s-tests_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test integ-framework-k8s-tests_istio

integ-pilot-local-tests_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test integ-pilot-local-tests_istio

integ-istioio-k8s-tests_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test integ-istioio-k8s-tests_istio

pilot-e2e-envoyv2-v1alpha3_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test pilot-e2e-envoyv2-v1alpha3_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

pilot-multicluster-e2e_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test pilot-multicluster-e2e_istio

integ-security-k8s-tests_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test integ-security-k8s-tests_istio

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

@leowucn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-istioio-k8s-tests_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test integ-istioio-k8s-tests_istio

pilot-e2e-envoyv2-v1alpha3_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test pilot-e2e-envoyv2-v1alpha3_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

pilot-multicluster-e2e_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test pilot-multicluster-e2e_istio

integ-security-k8s-tests_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test integ-security-k8s-tests_istio

integ-pilot-local-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-pilot-local-tests_istio

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

@leowucn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-istioio-k8s-tests_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test integ-istioio-k8s-tests_istio

pilot-e2e-envoyv2-v1alpha3_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test pilot-e2e-envoyv2-v1alpha3_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

pilot-multicluster-e2e_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test pilot-multicluster-e2e_istio

integ-security-k8s-tests_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test integ-security-k8s-tests_istio

integ-pilot-local-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-pilot-local-tests_istio

e2e-simpleTests-cni_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test e2e-simpleTests-cni_istio

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

@leowucn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-istioio-k8s-tests_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test integ-istioio-k8s-tests_istio

pilot-e2e-envoyv2-v1alpha3_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test pilot-e2e-envoyv2-v1alpha3_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

pilot-multicluster-e2e_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test pilot-multicluster-e2e_istio

integ-security-k8s-tests_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test integ-security-k8s-tests_istio

integ-pilot-local-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-pilot-local-tests_istio

e2e-simpleTests-cni_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test e2e-simpleTests-cni_istio

integ-security-local-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-security-local-tests_istio

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

@leowucn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pilot-e2e-envoyv2-v1alpha3_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test pilot-e2e-envoyv2-v1alpha3_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

pilot-multicluster-e2e_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test pilot-multicluster-e2e_istio

integ-security-k8s-tests_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test integ-security-k8s-tests_istio

integ-pilot-local-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-pilot-local-tests_istio

e2e-simpleTests-cni_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test e2e-simpleTests-cni_istio

integ-security-local-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-security-local-tests_istio

integ-istioio-k8s-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-istioio-k8s-tests_istio

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

@leowucn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-bookInfoTests-envoyv2-v1alpha3_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

pilot-multicluster-e2e_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test pilot-multicluster-e2e_istio

integ-security-k8s-tests_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test integ-security-k8s-tests_istio

integ-pilot-local-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-pilot-local-tests_istio

e2e-simpleTests-cni_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test e2e-simpleTests-cni_istio

integ-security-local-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-security-local-tests_istio

integ-istioio-k8s-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-istioio-k8s-tests_istio

pilot-e2e-envoyv2-v1alpha3_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test pilot-e2e-envoyv2-v1alpha3_istio

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

@leowucn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pilot-multicluster-e2e_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test pilot-multicluster-e2e_istio

integ-security-k8s-tests_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test integ-security-k8s-tests_istio

integ-pilot-local-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-pilot-local-tests_istio

e2e-simpleTests-cni_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test e2e-simpleTests-cni_istio

integ-security-local-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-security-local-tests_istio

integ-istioio-k8s-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-istioio-k8s-tests_istio

pilot-e2e-envoyv2-v1alpha3_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test pilot-e2e-envoyv2-v1alpha3_istio

integ-telemetry-k8s-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-telemetry-k8s-tests_istio

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

@leowucn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pilot-multicluster-e2e_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test pilot-multicluster-e2e_istio

integ-security-k8s-tests_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test integ-security-k8s-tests_istio

integ-pilot-local-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-pilot-local-tests_istio

e2e-simpleTests-cni_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test e2e-simpleTests-cni_istio

integ-security-local-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-security-local-tests_istio

integ-istioio-k8s-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-istioio-k8s-tests_istio

pilot-e2e-envoyv2-v1alpha3_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test pilot-e2e-envoyv2-v1alpha3_istio

integ-telemetry-k8s-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-telemetry-k8s-tests_istio

integ-pilot-k8s-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-pilot-k8s-tests_istio

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

@leowucn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
5038804edb1d022cd5dddfb2a1044969887aaa09
link
/test integ-security-k8s-tests_istio

integ-pilot-local-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-pilot-local-tests_istio

e2e-simpleTests-cni_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test e2e-simpleTests-cni_istio

integ-security-local-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-security-local-tests_istio

integ-istioio-k8s-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-istioio-k8s-tests_istio

pilot-e2e-envoyv2-v1alpha3_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test pilot-e2e-envoyv2-v1alpha3_istio

integ-telemetry-k8s-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-telemetry-k8s-tests_istio

integ-pilot-k8s-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-pilot-k8s-tests_istio

pilot-multicluster-e2e_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test pilot-multicluster-e2e_istio

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

@leowucn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-pilot-local-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-pilot-local-tests_istio

e2e-simpleTests-cni_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test e2e-simpleTests-cni_istio

integ-security-local-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-security-local-tests_istio

integ-istioio-k8s-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-istioio-k8s-tests_istio

pilot-e2e-envoyv2-v1alpha3_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test pilot-e2e-envoyv2-v1alpha3_istio

integ-telemetry-k8s-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-telemetry-k8s-tests_istio

integ-pilot-k8s-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-pilot-k8s-tests_istio

pilot-multicluster-e2e_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test pilot-multicluster-e2e_istio

istio_e2e_cloudfoundry_istio
a1f99f9d6bd1b0f155187ff770a6a51fac7730d7
link
/test istio_e2e_cloudfoundry_istio

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

/retest

@leowucn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTests-cni_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test e2e-simpleTests-cni_istio

integ-security-local-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-security-local-tests_istio

integ-istioio-k8s-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-istioio-k8s-tests_istio

pilot-e2e-envoyv2-v1alpha3_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test pilot-e2e-envoyv2-v1alpha3_istio

integ-telemetry-k8s-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-telemetry-k8s-tests_istio

integ-pilot-k8s-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-pilot-k8s-tests_istio

pilot-multicluster-e2e_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test pilot-multicluster-e2e_istio

istio_e2e_cloudfoundry_istio
a1f99f9d6bd1b0f155187ff770a6a51fac7730d7
link
/test istio_e2e_cloudfoundry_istio

integ-pilot-local-tests_istio
a1f99f9d6bd1b0f155187ff770a6a51fac7730d7
link
/test integ-pilot-local-tests_istio

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

@leowucn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTests-cni_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test e2e-simpleTests-cni_istio

integ-security-local-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-security-local-tests_istio

integ-istioio-k8s-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-istioio-k8s-tests_istio

pilot-e2e-envoyv2-v1alpha3_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test pilot-e2e-envoyv2-v1alpha3_istio

integ-telemetry-k8s-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-telemetry-k8s-tests_istio

integ-pilot-k8s-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-pilot-k8s-tests_istio

pilot-multicluster-e2e_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test pilot-multicluster-e2e_istio

integ-pilot-local-tests_istio
a1f99f9d6bd1b0f155187ff770a6a51fac7730d7
link
/test integ-pilot-local-tests_istio

istio_e2e_cloudfoundry_istio
a1f99f9d6bd1b0f155187ff770a6a51fac7730d7
link
/test istio_e2e_cloudfoundry_istio

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

@leowucn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTests-cni_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test e2e-simpleTests-cni_istio

integ-istioio-k8s-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-istioio-k8s-tests_istio

pilot-e2e-envoyv2-v1alpha3_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test pilot-e2e-envoyv2-v1alpha3_istio

integ-telemetry-k8s-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-telemetry-k8s-tests_istio

integ-pilot-k8s-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-pilot-k8s-tests_istio

pilot-multicluster-e2e_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test pilot-multicluster-e2e_istio

integ-pilot-local-tests_istio
a1f99f9d6bd1b0f155187ff770a6a51fac7730d7
link
/test integ-pilot-local-tests_istio

istio_e2e_cloudfoundry_istio
a1f99f9d6bd1b0f155187ff770a6a51fac7730d7
link
/test istio_e2e_cloudfoundry_istio

integ-security-local-tests_istio
a1f99f9d6bd1b0f155187ff770a6a51fac7730d7
link
/test integ-security-local-tests_istio

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

@leowucn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTests-cni_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test e2e-simpleTests-cni_istio

integ-istioio-k8s-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-istioio-k8s-tests_istio

pilot-e2e-envoyv2-v1alpha3_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test pilot-e2e-envoyv2-v1alpha3_istio

integ-telemetry-k8s-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-telemetry-k8s-tests_istio

integ-pilot-k8s-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-pilot-k8s-tests_istio

pilot-multicluster-e2e_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test pilot-multicluster-e2e_istio

integ-pilot-local-tests_istio
a1f99f9d6bd1b0f155187ff770a6a51fac7730d7
link
/test integ-pilot-local-tests_istio

istio_e2e_cloudfoundry_istio
a1f99f9d6bd1b0f155187ff770a6a51fac7730d7
link
/test istio_e2e_cloudfoundry_istio

integ-security-local-tests_istio
a1f99f9d6bd1b0f155187ff770a6a51fac7730d7
link
/test integ-security-local-tests_istio

e2e-simpleTests-distroless_istio
a1f99f9d6bd1b0f155187ff770a6a51fac7730d7
link
/test e2e-simpleTests-distroless_istio

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

@leowucn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTests-cni_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test e2e-simpleTests-cni_istio

integ-istioio-k8s-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-istioio-k8s-tests_istio

pilot-e2e-envoyv2-v1alpha3_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test pilot-e2e-envoyv2-v1alpha3_istio

integ-telemetry-k8s-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-telemetry-k8s-tests_istio

integ-pilot-k8s-tests_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test integ-pilot-k8s-tests_istio

pilot-multicluster-e2e_istio
45c9b0bec3a596f6783d67348af5d303f6685985
link
/test pilot-multicluster-e2e_istio

integ-pilot-local-tests_istio
a1f99f9d6bd1b0f155187ff770a6a51fac7730d7
link
/test integ-pilot-local-tests_istio

istio_e2e_cloudfoundry_istio
a1f99f9d6bd1b0f155187ff770a6a51fac7730d7
link
/test istio_e2e_cloudfoundry_istio

integ-security-local-tests_istio
a1f99f9d6bd1b0f155187ff770a6a51fac7730d7
link
/test integ-security-local-tests_istio

e2e-simpleTests-distroless_istio
a1f99f9d6bd1b0f155187ff770a6a51fac7730d7
link
/test e2e-simpleTests-distroless_istio

e2e-simpleTests_istio
a1f99f9d6bd1b0f155187ff770a6a51fac7730d7
link
/test e2e-simpleTests_istio

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

@leowucn: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio
6ececfbbcef2419855e46732cf8f7c1fb96ac256
link
/test integ-mixer-k8s-tests_istio

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

/retest

@leowucn: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio
6ececfbbcef2419855e46732cf8f7c1fb96ac256
link
/test integ-mixer-k8s-tests_istio

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

/test integ-mixer-k8s-tests_istio

@leowucn: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio
6ececfbbcef2419855e46732cf8f7c1fb96ac256
link
/test integ-mixer-k8s-tests_istio

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


feat: add new Skills icons

Overview

Added new icons for languages and subjects that we teach
Organized these icons into a new Skills section in storybook

Note: there were a few icons that were already in gamut but just needed to be moved into the Skills section and the RubyIcon needed to be updated and moved. All details are in the Figma.
PR Checklist

[ ] Related to designs:
[ ] Related to JIRA ticket: [ABC-123]
[ ] I have run this code to verify it works
[ ] This PR includes unit tests for the code change
[ ] This PR includes testing instructions tests for the code change
[ ] The alpha package of this PR is passing end-to-end tests in all relevant Codecademy repositories

Testing Instructions

Visit the storybook preview and navigate to the Regular Icons section.
Ensure that you see a new Skills section at the bottom and that all the icons are there and look good.
You can also checkout the mono repo PR to see it used in the new skills section on the dashboard.

PR Links and Envs

Repository
PR Link
PR Env

Portal
Portal Link
Portal Env

📬Published Alpha Packages:@codecademy/gamut@55.21.3-alpha.138737.0@codecademy/gamut-icons@9.26.1-alpha.138737.0@codecademy/gamut-kit@0.6.412-alpha.138737.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://666230fc651d5871f90e05d8--gamut-preview.netlify.appDeploy Logs

@aionate0812 that's so weird! that wasn't happening locally! I'll dig into it and try to fix before merging, thanks for calling it out!

📬Published Alpha Packages:@codecademy/gamut@55.21.3-alpha.da8067.0@codecademy/gamut-icons@9.26.1-alpha.da8067.0@codecademy/gamut-kit@0.6.412-alpha.da8067.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6667107796ef835781bf3a5d--gamut-preview.netlify.appDeploy Logs


Fix/issue 429 poetry

Fixes #429
@ajmalab Another branch for your review.

@prabhu testing it now

@prabhu Unfortunately dependencies I have not installed at all show up as direct dependencies😕 (eg: pip, setup tools and wheel). I suspect cdxgen is installing them? sbom from this branch:

Output of poetry show --tree for reference:

@ajmalab, we have not decided whether to exclude these packages that are getting installed by default or not. I am inclined not to exclude them since the version of pip and wheel are important to understand how the rest of the tree got generated.
https://github.com/CycloneDX/cdxgen/blob/fix/issue-429-poetry/utils.js#L5764

@cerrussell, perhaps we exclude them from the dependencies array but retain them at the components level?

@prabhu That seems like a reasonable compromise.

@cerrussell, Let's implement that change under a separate ticket. This PR is ready to be merged.


Error on hide keybooard if keyboard never opened

If  create a screen that contains only  canvas, and execute Hide Keyboard, then
I get
error 906:  No focusable view found

Was the keyboard open when you attempted to do this? Looking at the code for HideKeyboard, it looks like this method only works if a view that is focusable is focused to receive text. Otherwise, if no view is focused the reported error is dispatched.

@farxinu Do you want to chime in here?

Oh hey. Yes. I didn't see this before. I will take a look. I'm on the T right now so can you assign it to me?
Sent from mobile. Please excuse any brevity.
On Tue, Dec 19, 2017 at 8:40 AM -0500, "Evan W. Patton" <notifications<EMAIL_ADDRESS>wrote:
@farxinuhttps://github.com/farxinu Do you want to chime in here?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/mit-cml/appinventor-sources/issues/1059#issuecomment-352752474, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ADcgKhmP01rSZ2Ut333CgBRGhTOuIZVIks5tB7ytgaJpZM4RGTuI.


Getting started

Summary
Getting Started Documentation
https://github.com/cerner/terra-ui.com/issues/19
I also went through and fixed a couple lint errors. Linting is now done with travis-ci
Thanks for contributing to Terra.
@cerner/terra


KCL functions both modify sketches in place and return them

This isn't a bug per se, but it is something that lends itself well to a great deal of unintuitive behavior. Consider the following KCL:
let exampleSketch = startSketchAt([0, 0])
  |> line([1, 0], %)
  |> line([0, 1], %)
  |> line([-1, 0], %)

let exampleSketch2 = line([0, -1], exampleSketch)

let example = extrude(1, exampleSketch2)

This creates a unit cube, as expected. So too does this:
let exampleSketch = startSketchAt([0, 0])
  |> line([1, 0], %)
  |> line([0, 1], %)
  |> line([-1, 0], %)

let exampleSketch2 = line([0, -1], exampleSketch)

let example = extrude(1, exampleSketch)

This seems to be because exampleSketch and exampleSketch2 end up referencing the same object. This leads to the somewhat odd situation where the pipeline operator doesn't actually do anything; we can also write the above as:
let exampleSketch = startSketchAt([0, 0])

line([1, 0], exampleSketch)
line([0, 1], exampleSketch)
line([-1, 0], exampleSketch)
line([0, -1], exampleSketch)

extrude(1, exampleSketch)

This generates the same unit cube. However, what we can't then do is reference exampleSketch again -- it seems extrude() doesn't so much modify the passed sketch as delete every reference to it from the local namespace. Returning to our first example:
let exampleSketch = startSketchAt([0, 0])
  |> line([1, 0], %)
  |> line([0, 1], %)
  |> line([-1, 0], %)

let exampleSketch2 = line([0, -1], exampleSketch)

let example = extrude(1, exampleSketch2)

let test = exampleSketch2 // this is an error, 'exampleSketch2' doesn't exist
let test = exampleSketch // this is also an error, 'exampleSketch' now also doesn't exist

Further, the error returned in this case is an API error, indicating this isn't getting caught in the frontend by the KCL interpreter, which makes me suspect that some or all of this behavior is unintended.

Just a related point, kcl kinda has fake immutability, We don't allow user to re-assign variables, but the stdlib functions do very often mutate the underlying sketchGroup (extrudeGroup etc). Which I think is at least in part, what's happening here.

I'd really like to understand this problem more. It's pretty fundamental.
Does anyone know, is the mutation happening in the sketchGroup in the KCL interpreter, or is this something on the engine side?

Interpreter

I'm bumping into this when implementing artifact tracking.
Chalmers and I were chatting, and we came up with a potential way to deal with this. I'm going to talk about lines and sketches, but the same logic would need to apply to extrusions and volumes and any other type of geometry.
Eager Mutation Approach

Mutate as we've been doing while we create a sketch for each line() call
As we do this, each line() call essentially consumes the previous sketch
When we try to use a previous sketch again through a variable, detect that the sketch has been consumed, and re-send commands to the engine to recreate the sketch again with a fresh UUID

Benefits

In the simple case where we use a sketch exactly once, engine messages do not change, and when they're sent does not change
When additional engine commands are needed, they're generated lazily only when needed

Drawbacks

Every time we use a sketch, we need to check whether it's been consumed
If it has been consumed, we need to recreate it from only the SketchGroup

Having written down this approach, I feel compelled to write down an alternative that has also been talked about.
Pure Geometry with a Show Command

Functions like line() do not send engine commands, and they do not mutate anything
Instead, they build up immutable data structures describing the geometry
Users must use show(myGeometry) to actually send it to the engine and display it

For example, this KCL:
let sketch1 = startSketchOn('XZ')
  |> startProfileAt([0, 0], %)
  |> lineTo([10, 10], %)
  |> lineTo([-9, 0], %)
  |> close(%)
let extrude1 = extrude(20, sketch1)

show(extrude1)

Note that desugaring the pipeline would look like this:
let sketch1 = close(
  lineTo(
    [-9, 0],
    lineTo(
      [10, 10],
      startProfileAt(
        [0, 0],
        startSketchOn('XZ')))))
let extrude1 = extrude(20, sketch1)

show(extrude1)

Using this approach, the above would build up a data structure like this:
let sketch1 = Solid2d(
  Path::Line(
    [-9, 0],
    Path::Line(
      [10, 10],
      ProfileStart(
        [0, 0],
        Plane('XZ')))))
let extrude1 = Extrude(20, sketch1)

Note how the data structure directly mirrors the KCL stdlib functions.
Put another way, the pseudocode implementation of lineTo() stdlib function would look like this:
enum Path =
    ProfileStart([number, number], Plane)
  | Line([number, number], Path)
  | Arc( /* omitted */, Path)

function lineTo(point: [number, number], path: Path): SketchGroup {
  return Path::Line(point, path)
}

Nothing gets sent to the engine. All it does is bundle up its parameters into a persistent data structure.
Only when we execute show(geometry) do we translate the above data structure to engine commands and send them. This is simple because the entire geometry is there. It's an abstract algebra that we traverse.
This might even open up opportunities for optimizations because we could look for patterns in the geometry and treat them differently.
Benefits

There's no mutation or consumption tracking
There's no lazy recreation of geometry
Lots of KCL stdlib functions get simpler

Drawbacks

This is a major breaking change because people need to add show(geometry) to their KCL
show is arguably boilerplate that users need to remember to do.  If they forget, the failure mode is bad: nothing appears. We could add a lint that detects unused/not-shown geometry, but that's more work.
Lots of KCL stdlib functions need to change

Plan 2 matches up nicely with my old vision of KCL (the fantasy docs), where the whole thing is just defining geometry and giving it names, then at the end, you choose which function to actually render.

If we're going to do this, we could also finally change the path API to be an array of path segments, rather than a nested list of path segments. Users should be able to do [line(4, 0), line(0, 4), line(-4, 0), line(0, -4)] to build a square, that's so much simpler than the nested approach. |> makes the nesting simpler, but it requires complicated approaches like reduce for dynamic geometry, whereas building an n-gon in this approach can use simpler array processing like map.

In this approach, sketchOn would close the path and return a solid2d. This would work similarly for sketching on a face, at a starting point, etc etc.

I like this array syntax @adamchalmers. How do you express non-closed paths in this approach? Would it be worth having sketchOn rather be closedPath, with an openPath function that doesn't close the path? I like the approachability of the the term sketchOn though.

How often do people draw open sketches? We could also just have a "open" optional bool which default to false.

My intuition says that operations allowed on a closed sketch are very different to those on an open sketch, and therefore, they should be different types.

OK, close could still be an extra step after I guess.

My thoughts in bullet points.

Implementing show, and or using Adam's syntax can work. What's important for the sketch mode UI to work is, that we can

still do mock execution
still access execution results that contains all of the 2d segment data for each of the sketches (even with mock execution) 2d data is needed so that can be drawn client side.

From a code gen perspective, automatically adding things to show won't be a problem though some situations confuse me, I'll put them below
New syntax break lots of code mods because the shape of the ast is changing, but can be done ofc.

Things I want to make sure I understand
let sketch1 = startSketchOn('XZ')
  |> startProfileAt([0, 0], %)
  |> lineTo([10, 10], %, $seg01)
  |> lineTo([-9, 0], %)
  |> close(%)
let extrude1 = extrude(20, sketch1)

const myFilletedExtrude = fillet(5, [seg01], extrude1)

show(extrude1)

In this case, the fillet is never applied right? as far as what the user see?
And for the following
let sketch1 = startSketchOn('XZ')
  |> startProfileAt([0, 0], %)
  |> lineTo([10, 10], %, $seg01)
  |> lineTo([-9, 0], %)
  |> close(%)
let extrude1 = extrude(20, sketch1)

const myFilletedExtrude = fillet(5, [seg01], extrude1)

show(extrude1, myFilletedExtrude)

This would ask the engine to create the two bits of geometry that sits on top of each other right?
And for the following
const myShape1 = shape1()
const myShape2 = shape2()
const myShape2 = shape3()

const substractedShape = subtract(myShape1, myShape2)

show(substractedShape)

We only want the final shape in the show function right?
If I'm thinking about the above correctly, like John was saying users will have to add things to the show function, but not only that it's a bit of a moving target, as they create a new variable that takes the old shape and changes it in some way, they need to change the show function, remove the old add the new, could get annoying after a while. less of a problem for code mods since we can do it for them but here are some ideas for how to make it smoother.
We put something in the gutter

These are click about and will add and remove the vars for them.
We dump the show function and instead add some special keyword or symbol for which variables get added to show, so instead of typing out a variable, you just adding a character to the variable declaration (we can still do the gutter helper with this one), $$ is a little goofy but you get the idea

I think we still need open profiles

Oh I really like the UI for show checkmarks. Great idea.
Also, I think a "variable is not shown, or part of anything that is shown" warning in the IDE will make this easier.

btw not sending to the engine early actually give users much more power to process the data that makes up shapes.
Lets say you wanted to write a function called zigZagSktech that takes a sketch and turns all of the straight segments and breaks them up into lots of little zigZaging lines. Well currently since it eagerly sends to the engine, it's too late they've already been created as straight segments, but with the show paradigm, it's able to loop over the segments to break them up before it gets sent to the engine.

@Irev-Dev, your code examples and interpretation sound correct to me. So show isn't all sunshine and rainbows. This is exactly why I wanted to write it down. Interesting to explore the consequences.
The check boxes remind me of a spreadsheet or notebook interface.
I really like the zigZagSketch idea.

I know it's a minor thing, but I feel like it would be a lot more convenient if show didn't need parentheses, similar to return, as in:
show myShape1

Or maybe, similar to $$ above, something that's more pictographic 😄 No eyes on myShape2, so it's not visible.
@_@ shape1()
let myShape2 = shape2()
@_@ let myShape3 = shape3()

Functions have the same "moving target problem" when you build something up and want to return it. This is true in general purpose programming languages like TypeScript. The way it's solved in Rust is with implicit return of the last expression. So I think either people can deal with it, or we add implicit show of some kind, maybe of the last expression.
But I've thought a lot about implicit show. I really want to preserve the ability to factor code out from the top level to a function and preserve its functionality. But I also don't think we want implicit show inside functions. So I'm coming around to the idea that just dealing with the moving target is fine.

I think that while it is related (and important), the show/construction geometry thing is a bit of a distraction to the key issue here, which as I understand it is just a bug in the interpreter's mapping of KCL's immutable semantics to the engine's mutable semantics.
Here's the orginal example
exampleSketch = startSketchAt([0, 0])
  |> line([1, 0], %)
  |> line([0, 1], %)
  |> line([-1, 0], %)

exampleSketch2 = line([0, -1], exampleSketch)

This should desugar to
$0 = startSketchAt([0, 0])
$1 = $0 |> line([1, 0], %)
$2 = $1 |> line([0, 1], %)
$3 = $2 |> line([-1, 0], %)
exampleSketch = $3

$4 = line([0, -1], exampleSketch)
exampleSketch2 = $4

When executed $1 = $0 |> line([1, 0], %) should make the following (pseudo-code) engine calls:
$1 = clone($0)
line($1, ...)

(This assumes that any sketches/paths in the engine which don't get extruded, get discarded, which might smell a bit like the 'show' thing, but I think there's a fine distinction here data and geometry, we can shorthand this as thinking of clones in the engine as copy-on-write references, or equivalently, that two identical objects at the same location are just one object).
There is a fine optimisation to do here which is to replace $1 = clone($0) with $1 = $0 if there are no other references to $0. Unfortunately, KCL as currently implemented does not check the 'no other references' condition and always makes this optimisation (which I see as a bug in KCL, rather than dependent on the 'show' issue).
I think the best fix to this is to straightforwardly implement reference counts for variables in the interpreter and send the clone command where the ref count is > 1. This can be further improved by doing a simple live range analysis of variables before execution and ignoring variables which are never used, and eagerly un-setting variables to keep reference counts low.
There are two remaining issues - there is no 'clone' API command, and what to do with unused clones in the engine state. I think the best answer is to add 'clone' and implement it using copy-on-write semantics so that there are effectively no extra clones. If there is not the bandwidth to do that, then we can (probably) use a pattern command to clone the objects we need to, but that leaves potentially extra, unused objects in the engine state. I don't know if that is a problem or how best to solve it.

I had the idea of copy-on-write before. Buried in Slack. It's nice because, in theory, the simple case doesn't change at all in terms of semantics or how it interacts with the engine.
I think it seems complicated because it requires tracking references, checking them everywhere (unless you can do static analysis), and cloning. Since it requires cloning in the general case, I brought up the idea of pure geometry because I thought it would be simpler to clone in the KCL interpreter (not the engine) since you need all the new UUIDs and Rust KCL structs of the new geometry. On the other hand, if you cloned in the engine... I don't even know how that would work because exampleSketch2 cannot have the same UUIDs as exampleSketch. The client has to tell the engine what those UUIDs are and have its Rust structs of the paths, sketches, extrusions, etc. so that they can be used in the UI.
In the "show pure geometry" idea sketched above, if you have a data structure representing geometry, it's conceptually simple to execute the engine commands to embody it in the engine and re-execute them with fresh UUIDs in order to clone. But because line() et al calls are just building up geometry, it also means that it changes when engine commands get sent. So you're right that it's not strictly the same as show, but they seem related. If you could help us see how to untangle them, it would probably reduce scope of this idea.

This assumes that any sketches/paths in the engine which don't get extruded, get discarded

Currently, sketches that are not extruded still show in the video stream.
Did you make a mistake and mean that we'd clone when executing this line $4 = line([0, -1], exampleSketch)? I don't think cloning before $1 = $0 |> line([1, 0], %) would have any effect.

I thought it would be simpler to clone in the KCL interpreter (not the engine)

This doesn't work because the object in the engine you're refering to is continuing to be mutated (assuming that we aren't optimising into a batch, but since we can't always assume that we are, we have to assume we never are for correctness).

On the other hand, if you cloned in the engine... I don't even know how that would work

Yeah, you would need a new uuid for the new object, but that seems expected and fine (and if we can supply user-side ids, then it doesn't add a blocking round trip).

Currently, sketches that are not extruded still show in the video stream.

I believe that in practice, this won't be an issue because the user will always do something with the cloned sketch, if there's a bug in the case where they don't, then that is ok for now.

If you could help us see how to untangle them, it would probably reduce scope of this idea.

I think that if we simply accept the above bug, then we're in a situation where our semantics are correct and we're future compatible with implicit or explicit show.

Did you make a mistake and mean that we'd clone when executing this line $4 = line([0, -1], exampleSketch)? I don't think cloning before $1 = $0 |> line([1, 0], %) would have any effect.

No, I was spelling out all the cloning which should happen in theory for a naive implementation of immutable semantics on top of mutable semantics. Any optimisation must be observably equivalent to this, which is true for $0 but not for exampleSketch. The point being that the optimisation has to be able to distinguish between these two cases.

I thought it would be simpler to clone in the KCL interpreter (not the engine)

This doesn't work because the object in the engine you're refering to is continuing to be mutated (assuming that we aren't optimising into a batch, but since we can't always assume that we are, we have to assume we never are for correctness).

I can see how my description would be misleading. What I mean by "cloning in the KCL interpreter" is cloning the client-side struct and (re-)sending all the commands needed to create the object in the engine, using different UUIDs.
On the other hand, if we send a single command to the engine that says "clone this object", we could clone the Rust struct in the interpreter, but all its UUIDs would be wrong and it's unclear to me how they could be fixed-up. Maybe if it's just the one UUID changing, it's doable, and it's basically equivalent to what you proposed. I understand now that adding an engine clone command would make it so that we wouldn't have to re-send all the commands to build the object from scratch, and this untangles it from explicit show.

No, I was spelling out all the cloning which should happen in theory for a naive implementation of immutable semantics on top of mutable semantics.

I think I misunderstood that you meant cloning should happen on every line, not just that first one.

I can see how my description would be misleading. What I mean by "cloning in the KCL interpreter" is cloning the client-side struct and (re-)sending all the commands needed to create the object in the engine, using different UUIDs.

I think this would be nice to do, but given that it is unpredictable when we fall off the batching path and end up sending things to the engine, I think it is not really possible at the moment. If we do are able to move to a model where we can always build whole objects client-side, I think it would be a good solution.

... maybe if it's just the one UUID changing, it's doable, and it's basically equivalent to what you proposed

Yeah, I guess I'm a bit hazy on which uuids we're collecting. I was assuming that it would just be a single uuid for the whole object, but if not then we'd need the clone API to send all the new uuids.


Fix failing Windows CI tests

There were two tests that have been failing as reported in #231.
Both of these are due to URI/Path changes that happened a little while back in ignition-common

These changes also break some tests on Linux

Still a work in progress, I'll switch back to draft.


baidunetdisk web can't pull up baidunetdisk windows client

baidunetdisk web can't pull up baidunetdisk windows client, when I use share link I must run YunDetectService.exe before.
Can it run with the main program？

I guess it is an issue with autorun. Unfortunately, it can not be solved by the manifest.

AltLayer Airdrop Season One Announcement

Exciting news! AltLayer token (ALT) is set to launch on Binance on January 25, 2024. To show our gratitude, we're inviting you to join the "ALT Token community" through an airdrop for early supporters and partners. Below is a summary:

Total Allocated ALT Tokens: 300,000,000 (3% of total supply)
Distribution Categories:

NFT Holders
Altitude Campaign Participants
EigenLayer Restakers
EigenLayer Ecosystem Partners
Celestia Stakers and others
Ethereum Mainnet
Binance Mainnet

For detailed criteria and information, check the full announcement here.
Claim Airdrop Altlayer opens from January 25 to February 02, 2024. Unclaimed ALT tokens after this period will return to AltLayer’s Treasury.
Thank you for being part of AltLayer's success! More to come in Season One, stay tuned.
Note: Certain regions are restricted from the airdrop. Please review the disclaimer before participating.
riojosdev, @mornydew, @astronrobotics, @EugenLutz, @abderhasan, @Ikdemm, @dhpradeep, @TSiin, @ddwty, @bang9, @seungjun-green, @soma2000-lang, @QXST, @zoooz0616, @SemennikovNA, @JaafarLezzaik, @Jubian, @melsuly, @nampingg, @valmnt


Improve help text of the tmt --root option

tmt --help says -r, --root PATH  Path to the tree root, '.' by default, however it looks like / is the actual default.
$ tmt tests ls .
/Sanity/users-shell-script

$ tmt tests ls
/Functional/SoftwareRestrictionPoliciesTest12
/Functional/SoftwareRestrictionPoliciesTest7
/Regression/bz1721496-Stop-littering-STDOUT-output-for-dnf
/Regression/bz1746464-default-fapolicyd-policy-prevents-ansible-from-running
/Regression/bz1747494-suspicious-logs-on-service-start
/Regression/bz1757736-fapolicyd-blocks-dracut-from-generating-initramfs
/Regression/bz1765039-fapolicyd-fails-to-identify-perl-interpreter
/Regression/bz1817413-segfault-on-update
/Regression/bz1817969-Cannot-execute-gcore-from-gcc-toolset-9-when
/Sanity/FapolicydRules
/Sanity/cli-options
/Sanity/fuzzer-radamsa
/Sanity/selinux
/Sanity/sets
/Sanity/trust-db
/Sanity/users-shell-script

$ tmt tests ls /
/Functional/SoftwareRestrictionPoliciesTest12
/Functional/SoftwareRestrictionPoliciesTest7
/Regression/bz1721496-Stop-littering-STDOUT-output-for-dnf
/Regression/bz1746464-default-fapolicyd-policy-prevents-ansible-from-running
/Regression/bz1747494-suspicious-logs-on-service-start
/Regression/bz1757736-fapolicyd-blocks-dracut-from-generating-initramfs
/Regression/bz1765039-fapolicyd-fails-to-identify-perl-interpreter
/Regression/bz1817413-segfault-on-update
/Regression/bz1817969-Cannot-execute-gcore-from-gcc-toolset-9-when
/Sanity/FapolicydRules
/Sanity/cli-options
/Sanity/fuzzer-radamsa
/Sanity/selinux
/Sanity/sets
/Sanity/trust-db
/Sanity/users-shell-script

Based on the help text I would expect tmt tests ls to give the same result as tmt tests ls .

Current working directory is used as the default place where to start looking for the metadata tree root. This is similar to how git detects root of the git repository. So this is working as expected. By default you always get all available objects, no filter is applied.

I see your point but first I think we do not need to mimic git in this way and second I do not understand the -r option then.

The --root says where to start looking for metadata. For example you don't need to enter the git repo to check what available:
cd
tmt --root git/tmt

Ok, so it is a starting point for upwards traversal to find the actual root. May be the help text should be updated.
Anyway we can discuss what implicit behaviour is better and what to explicitly use . or /.

My behaviour assumption is base on the ls rather than git and tmt tests ls makes me think of that as ls.
May be we can change this issue to 'improve -r help text'. And have another one for the discussion about possible . vs. / change.

What about to change it to the same text as --root option in docs/overview.rst is described?
There is "Path to the metadata tree, current directory used by default."
We could use it unchanged or change the description in help to something like:

"Path to the metadata tree root, current directory used by default." or
"Path to the root of the metadata tree, current directory used by default."

And I am not sure, if the second part (with default directory) is necessary here since '--root' option requires path. I know that is meant as the behavior when tmt is used without the option, but maybe by omiting this, description of this option would not be misleading.

I do not have any strong opinion here. I was just confused by the behavior vs the description. And the fact it is actually a path where the upwards traversal starts does not really fit the root definition.

Looks as a good first issue for me if still valid :-D

Covered by #1991.


Add tests

Test UI for every setting using FBSnapshotTestCase. Also includes a test for the didDismissViewController callback.
Part of https://cocoapods.org/testjam

Thanks @christianklotz !


__set_state exists in Carbon

__set_state should not be overridden

If it shouldn't be overridden it should've been final or private to begin with. And a change in public API would normally warrant a major version bump (2.0.0) according to semver.

May we just fix it and discuss later?

@olafnorge sure, once the tests pass again.

Yes quick-revert here: https://github.com/laravel/framework/pull/23466

With Carbon version update the tests pass and so __set_state could be simply removed. So this PR is a better resolution in my opinion.

Need this now. This brought down my dev environment. :(

@kylekatarnls is the usage of __set_state being tested?

__set_state in Carbon is exactly the same code as in Carbon and yes we tested it here: https://github.com/briannesbitt/Carbon/blob/master/tests/Carbon/InstanceTest.php#L61

@kylekatarnls is that PR going to be backported to 5.5 LTS?

@LukeTowers > @taylorotwell did it.
What is the workflow for master/5.7, should it be this commit merged or should I submit an other PR?

Awesome, thanks for the update!

This might have break something; see this SO question.

Always submit PRs to the earliest branch on the framework. We regularly merge 5.5 -> 5.6 -> master. :)

@Kyslik 32bit problem, fixed in 1.24.2


Initialization module gave 'nan' for normal-light images

When I tried to train an initialization module for normal-light images from LOL datasets, the forward computation result of decom.py turned out to be nan(both R and L).
I am very confused because:
1.Input images have been normalized to [0,1]
2.No nan in input images.
3.Everything is fine with training for low-light images from LOL datasets.
Is it a gradient explosion or something? Have you got any idea what is going on there?

I found the reason, this phenomenon is caused by outdated numpy, simply updating numpy by pip install --upgrade numpy solves the issue~

Seems that the structure-aware smooth constraint loss produces nan during back propogation. With this loss term, network parameters become nan after loss.backward() and optimizer.step(). Perhaps my computation of the gradient of the illumination component is wrong

I found the reason by using torch.autograd.set_detect_anomaly(True). I used torch.sqrt() when computing image gradient, stop using it solves the issue.

I guess what happens here is that a zero is divided because the derivative of a sqrt has got the sqrt on the denominator.


Add support for only scanning certain directories

There should be a way to only scan certain directories within my repo.

What language are you working with? You can add configuration using paths and paths-ignore to control which directories are scanned for dynamic languages only (ie- js, ruby, python).
See details in the docs.
For compiled languages, you would need to supply your own build step where you only compile the directories you want analyzed.

@aeisenberg Yes I'm using JavaScript & TypeScript.
So that should work. One question after reading the documentation you linked. Every code snippet under the Example configuration files section has a queries & name value defined. Are these required properties? Or is it allowed to just specify a paths value?

All the properties are optional.

Please create a new issue if you have any further questions.

I am manually building a C# (.net 4.8) solution in a subdirectory of a monorepo:
e.g.
    - name: Build
      run: msbuild ./Subfolder/MyProject.sln /p:platform="any cpu" /p:configuration="release"

    - name: Perform CodeQL Analysis
      uses: github/codeql-action/analyze@v2
      with:
        category: "/language:${{matrix.language}}"

However the analysis is still recording C# alerts in GitHub Code Scanning from other directories in the repository. How can I restrict the analysis to the subdirectory?

@brettpostin, please create a new issue for this and we can help you. CodeQL analysis will look at everything that is put into the database. If files outside of database are being included in the analysis, then we will need more information to help. You can include the full workflow file and logs. If the repo is public, can you include a lnk to that?


Flexible scale labels

Augmenting the number of categories in the Category Axis or resizing the width of the chart makes the labels overlap and unreadable. Not sure what is the best method.

Planning poker score: 8 (0-89 Fibonacci)

I have looked at areachant's code, it also looks not so good, but it have a small popup when mouse put on it.


Customizing PR Prefix

It would be nice to have a way to customize or omit the prefix that's prepended to the backport PR.
For example, when we merge backports to docs-csm the PR title is included as the merge's commit message. The commit messages would be cleaner if the PR titled omitted the [backport release/1.0] prefix:

We already know it is targeting release/1.0 by the context of the base branch
Knowing it is a backport doesn't necessarily imply anything, the change is really logged by the JIRA

I believe at least [release/1.0] part is still needed. Otherwise, it will be literally impossible to distinguish  betweeb PR's for different branches in the PR list. For each PR, PR list displays title, status and labels, but it does not display branch names.


feat: add ide-extension for i18next handling

Let me know if I need to change something to merge this PR

I added the inlang IDE extension to sealos. Helps with handling translation keys and translation linting.
What did I add?

inlang.config.js to configure where language translations are
Would recommend adding it to the .vscode folder so other contributors can use it.

How to use it?
Extract Messages (translations)
Extract Messages (translations) via the Inlang: Extract Message code action.

Inline annotations
You can see translations directly in your code. No back-and-forth looking into the translation files themselves. (code example from sealos)

Ootb editor & CLI if needed.

Hey btw sealos has 16 erros (missingMessage/ referenceMessageMissing) in the translation.

This could negatively effect the user experience.

I also sow that the key Recharge Amount is often used but not in the translations. Probably an old key.

@c121914yu inlang seems to be a good method for i18n, please follow up on this pull request.

@c121914yu

How do I get it started?
Do I need to install other packages? or IDE extension.
Please give a complete example.

After merge, you just need to open vscode with the inlang ide-extension installed. It should automatically work.
Usage is documented here -> https://inlang.com/documentation/apps/ide-extension

Because we are using the i18n ally plugin locally. I'm not sure if inlang can be replaced it.

i18n-ally can also be used as a helper with i18n, but inlang is going for the infrastructure approach, which caught me. What does it mean:

Comes with i18n products that are just usable ootb with the config. (ide-extension, cli, editor)
no lock-in, for those who want to use i18n-ally it is not a problem
inlang is being built fast, while i18n-ally is basically unmaintained by localize https://github.com/lokalise/i18n-ally/discussions/896

In conclusion, inlang can replace it. Especially with the release of https://github.com/inlang/inlang/issues/960 and https://github.com/inlang/inlang/issues/724. But as I said there is no need to decide (no lock-in).

I have added the inlang.config.js file locally and have installed the inlang extension. But didn't seem to see much effect.
I see an sdk in the inlang documentation,  do I need to install it?
Or I need to add a configuration in.vscode/settings.json?

I see an sdk in the inlang documentation, do I need to install it?

The SDK is only relevant if you didn't localize yet.

Or I need to add a configuration in.vscode/settings.json?

There shouldn't be anything to change here.
You can test if the config is valid with npx @inlang/cli config validate. -> https://inlang.com/documentation/apps/inlang-cli#config-validate
If that works you should see the inline annotations. Sometimes you need to reload the window. While doing that on the bottom left corner it should say inlang extension activated. After some seconds it should show the annotations and of course, you could use the extract function.

inlang did a big update which requires an update on this PR.
-> Whats new
Should I change it?

inlang did a big update which requires an update on this PR.
-> Whats new
Should I change it?

inlang did a big update which requires an update on this PR.
-> Whats new
Should I change it?

Thank you for your PR. But we don't feel we have a difficult problem with i18n-Ally right now, and we will keep watching on inlang's development and evaluate it.
We will re-evaluate the i18n when we rebuild the architecture in Q4

inlang did a big update which requires an update on this PR.
-> Whats new
Should I change it?

Thank your PR. We will re-evaluate the i18n when we rebuild the architecture in Q4.

Hi @c121914yu just wanted to check-in if you talked already about i18n in Q4?


urllib.error.HTTPError: HTTP Error 403: Forbidden

Hi, we cannot download the lsun_bedroom1.pth using the official command python main.py --exp ./runs/ --config bedroom.yml --sample -i images --npy_name lsun_bedroom1 --sample_step 3 --t 500  --ni. How could we fix this error? The traceback is posted below.
Thank you very much.
  File "main.py", line 104, in main
    runner.image_editing_sample()
  File "/mnt/zff/code/diffusion_model/sdedit/sdedit/runners/image_editing.py", line 113, in image_editing_sample
    download_process_data(path="colab_demo")
  File "/mnt/zff/code/diffusion_model/sdedit/sdedit/functions/process_data.py", line 8, in download_process_data
    torch.hub.download_url_to_file('https://image-editing-test-12345.s3-us-west-2.amazonaws.com/colab_examples/lsun_bedroom1.pth', os.path.join(path, 'lsun_bedroom1.pth'))
  File "/miniconda3/envs/t1/lib/python3.8/site-packages/torch/hub.py", line 611, in download_url_to_file
    u = urlopen(req)
  File "/miniconda3/envs/t1/lib/python3.8/urllib/request.py", line 222, in urlopen
    return opener.open(url, data, timeout)
  File "/miniconda3/envs/t1/lib/python3.8/urllib/request.py", line 531, in open
    response = meth(req, response)
  File "/miniconda3/envs/t1/lib/python3.8/urllib/request.py", line 640, in http_response
    response = self.parent.error(
  File "/miniconda3/envs/t1/lib/python3.8/urllib/request.py", line 569, in error
    return self._call_chain(*args)
  File "/miniconda3/envs/t1/lib/python3.8/urllib/request.py", line 502, in _call_chain
    result = func(*args)
  File "/miniconda3/envs/t1/lib/python3.8/urllib/request.py", line 649, in http_error_default
    raise HTTPError(req.full_url, code, msg, hdrs, fp)
urllib.error.HTTPError: HTTP Error 403: Forbidden

got the same question

got the same question

me too

got same question

me too

me too

Does anyone solve this problem?

same question


Unable to publish version

Would like to have publish option also. Is there a reason why it's omitted?

Without this feature, every time the Step Function definition is updated, the old one is deleted along with its execution history.


Inject git commit into Docker image.

Motivation
Docker validators should provide their git commit when queried.
Proposal
Inject the git commit into the docker build process.
Test Plan
Tested manually.
$ linera --wallet wallet.json --storage rocksdb:linera.db query-validator grpc:localhost:19100
2024-10-22T19:34:21.838756Z  INFO linera::main: linera: Version information for new validator: Linera protocol: v0.13.0
RPC API hash: ZqNY7r+amtHKJVYpUngy/+yu/YXNTTgqJR17YOyWQtQ
GraphQL API hash: s/zNt/rFKTb63M7N6/Gfdmw4lRe+6+s8diGn6+A/Myk
WIT API hash: DTU+YHsJxaXJVywyYChS0/Kzu1lmAjAlUjtdayBz2hk
Source code: https://github.com/linera-io/linera-protocol/tree/fcdcd93a

9c46bc873013efc162f4e2a63cc27d7de9e4178297f898f426503c6d86c7dcc4

Release Plan
This generally concerns only bug fixes.

These changes should be backported to the latest devnet branch, then

be released in a validator hotfix.

These changes should be backported to the latest testnet branch, then

be released in a validator hotfix.

Merge activity

Oct 22, 7:53 PM EDT: A user started a stack merge that includes this pull request via Graphite.


[BUG] ETH.ARB intrinsic gas too low

Describe the bug
It is not possible to send ETH.ARB as intrinsic gas set is too low
Expected behavior
Able to send ETH.ARB
Screenshots

Version 1.1.2

We allow user to set the gas using advance gas limit now , so closing it
This might cause by a gas spike


Use ORT's default name for the rules script

See individual commits.

Just some remarks:

Committing a symbolic link might breaking the cloning experience for some Windows users (depending on the OS policies).
I'm fine with exposing the rules from the evaluator-rules directory at the root level for direct consumption if the rules at evaluator-rules/src/main/resources/evaluator.rules.kts actually do something meaningful. I haven't checked on that. So far I saw evaluator-rules/src/main/resources/evaluator.rules.kts more like a showcase of what's possible with ORT's evaluator, but what's not necessarily meaningful to do (in a legal / compliance sense).

I'm fine with exposing the rules from the evaluator-rules directory at the root level for direct consumption if the rules at evaluator-rules/src/main/resources/evaluator.rules.kts actually do something meaningful. I haven't checked on that. So far I saw evaluator-rules/src/main/resources/evaluator.rules.kts more like a showcase of what's possible with ORT's evaluator, but what's not necessarily meaningful to do (in a legal / compliance sense).

I believe it is meaningful even though not a legal recommendation.


[doc] fix installation guide can not return to root path in zh/docs/installation/kubectl-apply.md

fix installation guide can not return to root path in zh/docs/installation/kubectl-apply.md
Signed-off-by: hanweisen<EMAIL_ADDRESS>

@hanweisen LGTM,Thank you very much for contributing!


Update to use the new API?

I don't really plan on making big changes to the Rust rewrite, other than fighting with GitHub Actions for release automation, and finding a way to make the book generally available other than through my profile (which might involve not building the book at all).
Given this, what would the roadmap look like for deprecating the current state of the client in favour of the changes made for the API exposed by the rewrite?
I would like this migration to have as little friction as possible, so this is still an RFC.

I'm more than happy to help with Actions stuff, I'll take a look at it! I'd like to deprecate the Go version as well as this client entirely, I mentioned rewriting this client in Rust in #7 but if we can just expose an API in heartbeat-rirr that works too

Hi, sorry I'm a bit busy these days, so I may be slow to respond to things :)
I actually do have a cross-platform Rust client in the works. It's currently in a horrible state, I'd like to resume work on it when I do get the time.
xprintidle is essentially a single C file, it was easy enough to rewrite in Rust. For macOS, I just translated the implementation in this client to use the frameworks directly instead of shelling out. Windows is already in Rust, so that doesn't change. To be screenlocker agnostic, I thought of using libdbus to query screensaver status. This does make this part of it support Wayland, sort of; but requires a pretty chonky (albeit common-ish on desktops) library at runtime.
I came across the library linked in #7 but the subtle difference in that it waits for an idle time of X before yielding would result in a naive implementation along those lines to be a long running client, which maintains its own internal timer instead of delegating to systemd (I was thinking of using tokio::select!), which I'm kind of iffy about.
I haven't dived very deep into this, but I don't think there's a "stable" API to query screensaver info from Wayland itself. Some of the symbols I used initially to make my own client (while I was still using the Go version of the server), which was incredibly jank, don't even exist anymore.
I would like help with the release automation if you have the time. What I have now, does work. And it does support Windows, Mac, and Linux. But I want to increase the platform support because.. well, I have the credits to spare (which is why I want your opinion before I upstream this because I don't think this org is covered by either of our Pro plans)
I would also ideally like a place to host the documentation built by mdbook, but failing that I think I can just maintain it separately using GitHub's Wiki feature or something (I just like mdbook's look-and-feel and search is better).

I think not relying on systemd / maintaining an internal timing seems to be preferable, here? I'm happy to help with the release automation, we should discuss that in more detail :)

using an internal timer with a subset of the functionality of wayidle seems very plausible. unfortunately I don't have a Wayland setup to test this. I'll get to it next week maybe as I'm swamped for now lol.
I'm happy to discuss release automation in a separate issue


Login widget - Your form markup here

Problem
I don't understand how to add a login widget to pagekit. When I try to add it from the widget panel I got this: Your form markup here

Technical Details

Pagekit version: 1.0.11
Webserver: Apache
Database: Mysql 5.7.16-10
PHP Version: 5.6.26

This looks like a bug. Did you installed the release package?

I was not able to remember - I have downloaded the last version from the website and... it works perfectly fine now.
Thanks!


kamel run with reference to an existing Integration Kit in another namespace

I'm going to run an Integration with a reference to an existing Integration Kit.
kamel run -t prometheus.enabled=true -k basic Hello.java -n integration-dev

When I'm using the -o yaml > Hello.yaml option I'm getting
apiVersion: camel.apache.org/v1
kind: Integration
metadata:
  creationTimestamp: null
  name: hello
  namespace: integration-dev
spec:
  integrationKit:
    name: basic
    namespace: integration-dev
  sources:
  - content: "// camel-k: language=java\n\npackage de.casag.hello.route;\n\nimport
      org.apache.camel.builder.RouteBuilder;\n\npublic class Hello extends RouteBuilder{\n\n\tpublic
      void configure() throws Exception {\n\n\t\tfrom(\"timer:enforedeinvoices?period=3600000&delay=0\")\n\t\t\t\t.log(\"Hello
      World!\")\n\t\t;\n\n\t}\n}\n\n"
    name: Hello.java
  traits:
    prometheus:
      configuration:
        enabled: true
status: {}

The Integration should be deployed in the namespace integration-dev. The Integration Kit being referenced is located in the namespace camel-k.
I can change this in the YAML file like
apiVersion: camel.apache.org/v1
kind: Integration
metadata:
  creationTimestamp: null
  name: hello
  namespace: integration-dev
spec:
  integrationKit:
    name: basic
    namespace: camel-k
  sources:
  - content: "// camel-k: language=java\n\npackage de.casag.hello.route;\n\nimport
      org.apache.camel.builder.RouteBuilder;\n\npublic class Hello extends RouteBuilder{\n\n\tpublic
      void configure() throws Exception {\n\n\t\tfrom(\"timer:enforedeinvoices?period=3600000&delay=0\")\n\t\t\t\t.log(\"Hello
      World!\")\n\t\t;\n\n\t}\n}\n\n"
    name: Hello.java
  traits:
    prometheus:
      configuration:
        enabled: true
status: {}

and deploy afterwards with
kubectl apply -f Hello.yaml

The Integration works event with the reference to an Integration Kit in another namespace.
Is there a way to address the different namespace in the kamel run -k <IntegrationKit> CLI part?
Best
Gerald

No we have nothing like that. Maybe we could think to introduce a syntax such as namespace/kit.

Thanks @squakez. Could you than turn this into a feature request please?

Let's wait for others input. I have no strong opinion about the possibility to use cross namespace references, but others may have concerns about that.

Cross-namespace IntegrationKit references are already supported in the Integration type, so that seems like a reasonable request to surface it into the CLI.

Thanks a lot. The point is when the Operator has been installed with the --global option, let's say in namespace camel-k and we're going to create an integration in an other namespace, let's say integration-dev, the Integration Kit will be created in namespace camel-k.

Thanks a lot. The point is when the Operator has been installed with the --global option, let's say in namespace camel-k and we're going to create an integration in an other namespace, let's say integration-dev, the Integration Kit will be created in namespace camel-k.

Right, this primarily applies when the operator has been installed with the global option.

Could this be turned into a feature request @squakez? Many thanks in advance.


Harden 2FA/TOTP implementation according to rfc6238 (part 1)

Implements issue 1 in https://github.com/louislam/uptime-kuma/issues/640

Tested working, but forgot to put in the recent release...  Postpone to the next release.
Thank you for your contribution.


Update sideload-office-add-ins-for-testing.md

Updated the "Manually sideload an addin section" - step 2 said to go to the insert tab to select addins when addins are actually in the home tab.
I updated "insert tab" to "home tab"

@EsterBergen, Thanks for letting me hijack this PR to make a bunch of changes across the board. @samantharamon, please direct your feedback to me.

@samantharamon, the old images have been removed and a new CF screenshot has been added.


Functions not work on local Windows environment

I test NHOST v2 now, and I have a problem with local testing my functions - here is my debug listing:
Initializing environment
[nhost] [prefix] Fetching containers
Wrapping containers into environment
[path] Watching .git\HEAD
Fetching local git branch
git HEAD not found
Parsing app configuration
[nhost_hasura] [configuration] Initializing
[nhost_auth] [configuration] Initializing
[nhost_storage] [configuration] Initializing
[nhost_mailhog] [configuration] Initializing
[nhost_postgres] [configuration] Initializing
[nhost_minio] [configuration] Initializing
[watcher] Activated
Server logs will be deleted on shutdown.
Checking for required Nhost container images
[docker.io/mailhog/mailhog:v1.0.1] Pulling container image
[docker.io/nhost/postgres:12-v0.0.6] Pulling container image
[docker.io/nhost/hasura-storage:0.1.5] Pulling container image
[docker.io/nhost/hasura-auth:0.6.3] Pulling container image
[docker.io/hasura/graphql-engine:v2.2.0] Pulling container image
Configuring services
[data] Mounting data from .nhost\main
[nhost] [network] Preparing
[nhost] [network] Fetching
[nhost] [network] Creating
[nhost_auth] [container] Creating
[nhost_auth] [container] Starting
[nhost_storage] [container] Creating
[nhost_storage] [container] Starting
[nhost_mailhog] [container] Creating
[nhost_mailhog] [container] Starting
[nhost_hasura] [container] Creating
[nhost_hasura] [container] Starting
[nhost_minio] [container] Creating
[nhost_minio] [container] Starting
[nhost_postgres] [container] Creating
[nhost_postgres] [container] Starting
[nhost] [prefix] Fetching containers
Wrapping containers into environment
Starting health check
[nhost_hasura] [container] Health check attempt #1 unsuccessful
[nhost_auth] [container] Health check attempt #1 unsuccessful
[nhost_hasura] [container] Health check attempt #2 unsuccessful
[nhost_auth] [container] Health check attempt #2 unsuccessful
[nhost_storage] [container] Health check attempt #1 unsuccessful
[nhost_hasura] [container] Health check attempt #3 unsuccessful
[nhost_auth] [container] Health check attempt #3 unsuccessful
[nhost_storage] [service] Health check successful
[nhost_auth] [container] Health check attempt #4 unsuccessful
[nhost_hasura] [container] Health check attempt #4 unsuccessful
[nhost_hasura] [service] Health check successful
[nhost_auth] [container] Health check attempt #5 unsuccessful
[nhost_auth] [container] Health check attempt #6 unsuccessful
[nhost_auth] [container] Health check attempt #7 unsuccessful
[nhost_auth] [container] Health check attempt #8 unsuccessful
[nhost_auth] [container] Health check attempt #9 unsuccessful
[nhost_auth] [container] Health check attempt #10 unsuccessful
[nhost_auth] [service] Health check successful
Initializing Hasura client
Applying migrations
Applying metadata
Restarting auth container
Restarting storage container
Starting health check
[nhost_hasura] [service] Health check successful
[nhost_auth] [container] Health check attempt #1 unsuccessful
[nhost_storage] [container] Health check attempt #1 unsuccessful
[nhost_storage] [service] Health check successful
[nhost_auth] [container] Health check attempt #2 unsuccessful
[nhost_auth] [service] Health check successful
Exporting metadata

[proxy] [functions] http://localhost:7777/ --> /v1/functions/
[proxy] [nhost_auth] http://localhost:9004/ --> /v1/auth/
[proxy] [nhost_storage] http://localhost:8610/v1/storage/ --> /v1/storage/
[proxy] [nhost_hasura] http://localhost:9222/v1/graphql --> /v1/graphql
[proxy] [nhost_hasura] http://localhost:9222/v2/query --> /v2/query
[proxy] [nhost_hasura] http://localhost:9222/v1/metadata --> /v1/metadata
[proxy] [nhost_hasura] http://localhost:9222/v1/config --> /v1/config
[proxy] [console] http://localhost:9337/ --> /
[proxy] [GET] /

When I call : GET http://localhost:1337/v1/functions/time?name=Evzen (from POSTNAM) i get Not Found response.
In console i see this:
[proxy] [nhost_hasura] http://localhost:9222/v1/metadata --> /v1/metadata
[proxy] [nhost_hasura] http://localhost:9222/v1/config --> /v1/config
[proxy] [console] http://localhost:9337/ --> /
[proxy] [GET] /
[proxy] [GET] /v1/functions/time

But nothing more....
If I publish to cloud (prod) all works fine - function works.
From postman - GET https://jqlacqrnlnhfwupoolvh.nhost.run/v1/functions/time?name=Evzen
works: response - Hello Evzen! It's now: Thu, 05 May 2022 06:11:55 GMT
My Environment - Windows 11 Pro
Where maybe the problem be?

I get this work via Windows WSL - Ubuntu 20.04 and Docker Desktop. Now all works fine.


Correct gmail action from tracker notification

Ready for review.
The gmail notifications weren't showing up correctly.  I also reduced the verbosity of the subject line.

LGTM. :chicken:


Support passing customArgs to hydrate method

This PR adds an optional customArgs parameter to hydrate which is then available to custom factory methods serializr uses during model deserialization.
See https://github.com/mobxjs/serializr#6-use-custom-arguments-to-inject-stores-to-models
Previously it was not possible to use mobx-persist with model classes which used constructor injection.

Thank you~!

No, thank you rather :-) !!


⚠ ClamAV has degraded performance

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

HTTP code: 200
Response time: 101 ms

Resolved: ClamAV performance has improved in 85fe7e0.