Unable to restore Drive item

After recent changes in the elements structure and data binding, the Drive item is not restored correctly.
It sets app.request from the drive but does not sets request object in the request-panel element. Them main.js script has to find the request-panel element and set up variables bu its own.

The release with fix has been published today.
Thanks for reporting the bug.


Exception is thrown when calling GetContentAsync()

Description
Exception is thrown when calling GetContentAsync()
Complete minimal example reproducing the issue
        [TestMethod]
        public async Task DownloadStringTest()
        {
            var browser = await Puppeteer.LaunchAsync(new LaunchOptions
            {
                Headless = true,
                Product = Product.Firefox
            });

            var page = await browser.NewPageAsync();
            await page.GoToAsync("https://www.otcmarkets.com/stock/WRIT/security");

            var content = await page.GetContentAsync();

            Assert.IsFalse(string.IsNullOrWhiteSpace(content));
        }

Expected behavior:
Expect html content to be available
Actual behavior:
Exception is thrown (see below)
Versions
Puppeteer v5.1
Additional Information
Test method DownloadStringTest threw exception:
PuppeteerSharp.TargetClosedException: Protocol error(Runtime.callFunctionOn): Target closed. (Page failed to process Runtime.consoleAPICalled. Error reading string. Unexpected token: StartArray. Path ''..    at Newtonsoft.Json.JsonReader.ReadAsString()
at Newtonsoft.Json.JsonReader.ReadForType(JsonContract contract, Boolean hasConverter)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent)
at Newtonsoft.Json.JsonSerializer.DeserializeInternal(JsonReader reader, Type objectType)
at Newtonsoft.Json.Linq.JToken.ToObject(Type objectType, JsonSerializer jsonSerializer)
at Newtonsoft.Json.Linq.JToken.ToObject[T](JsonSerializer jsonSerializer)
at PuppeteerSharp.Helpers.Json.JTokenExtensions.ToObject[T](JToken token, JsonSerializerSettings jsonSerializerSettings) in C:\projects\puppeteer-sharp\lib\PuppeteerSharp\Helpers\Json\JTokenExtensions.cs:line 41
at PuppeteerSharp.Helpers.Json.JTokenExtensions.ToObject[T](JToken token, Boolean camelCase) in C:\projects\puppeteer-sharp\lib\PuppeteerSharp\Helpers\Json\JTokenExtensions.cs:line 23
at PuppeteerSharp.Helpers.RemoteObjectHelper.ValueFromType[T](JToken value, RemoteObjectType objectType, Boolean stringify) in C:\projects\puppeteer-sharp\lib\PuppeteerSharp\Helpers\RemoteObjectHelper.cs:line 70
at PuppeteerSharp.Helpers.RemoteObjectHelper.ValueFromRemoteObject[T](RemoteObject remoteObject, Boolean stringify) in C:\projects\puppeteer-sharp\lib\PuppeteerSharp\Helpers\RemoteObjectHelper.cs:line 42
at PuppeteerSharp.Page.<>c.b__248_1(JSHandle i) in C:\projects\puppeteer-sharp\lib\PuppeteerSharp\Page.cs:line 2375
at System.Linq.Enumerable.WhereSelectArrayIterator2.MoveNext()        at System.String.Join[T](String separator, IEnumerable1 values)
at PuppeteerSharp.Page.d__248.MoveNext() in C:\projects\puppeteer-sharp\lib\PuppeteerSharp\Page.cs:line 2388
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at PuppeteerSharp.Page.<Client_MessageReceived>d__235.MoveNext() in C:\projects\puppeteer-sharp\lib\PuppeteerSharp\Page.cs:line 2116)
Stack Trace:
TaskAwaiter.ThrowForNonSuccess(Task task)
TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
d__33.MoveNext() line 165
--- End of stack trace from previous location where exception was thrown ---
TaskAwaiter.ThrowForNonSuccess(Task task)
TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
d__321.MoveNext() line 116     --- End of stack trace from previous location where exception was thrown ---     TaskAwaiter.ThrowForNonSuccess(Task task)     TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)     <13 more frames...>     <DownloadUsingBrowserAutomation>d__4.MoveNext() line 55     --- End of stack trace from previous location where exception was thrown ---     TaskAwaiter.ThrowForNonSuccess(Task task)     TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)     TaskAwaiter1.GetResult()
d__0.MoveNext() line 17
--- End of stack trace from previous location where exception was thrown ---
TaskAwaiter.ThrowForNonSuccess(Task task)
TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
ThreadOperations.ExecuteWithAbortSafety(Action action)

Triage Info: The RemoteObject.Value from a console log is coming as a JArray instead of a JToken,  breaking the parsing.

Closed due to inactivity. Feel free to reopen it if needed.


Non generic generics

This is a draft. Once this is actually working, it'll be rebased onto the v0.2.0 branch. For now it'll live here and the PR is mainly to get an overview of all changes since.

This can finally be closed as #38 has been merged. :partying_face:


Add Related Website Set for stripe.com

Adds Related Website Set for stripe.com
Well-known entries are in place for

https://stripe.com/.well-known/related-website-set.json (primary)
https://stripecdn.com/.well-known/related-website-set.json (service)
https://stripe.network/.well-known/related-website-set.json (service)

Root of both service domains redirect to primary home page

"contact"<EMAIL_ADDRESS>"primary": "https://stripe.com",
"serviceSites": [
"https://stripecdn.com",
"https://stripe.network"
],
"rationaleBySite": {
"https://stripecdn.com": "Serves static assets accelerating page loads and sandboxes select Javascript",
"https://stripe.network": "Receives telemetry preventing

66103d831d57290d2814bc9df8bafafea8e83bbd

https://stripe.comc6fa8e0b804782e95cc2736fad7baeef2b0acc94


MEMBERSHIP: mergenci

GitHub Username
@mergenci
Requirements

[x] I have reviewed the community membership guidelines
[x] I have enabled 2FA on my GitHub account
[x] I have joined the Crossplane slack channel
[x] I am actively contributing to the Crossplane project
[x] I have two sponsors that are current Crossplane Org members
[x] I have spoken to my sponsors ahead of this application, and they have agreed to sponsor my application

Sponsors

@jbw976
@jeanduplessis

List of contributions to the Crossplane project
PRs authored

https://github.com/crossplane/upjet/pull/329
https://github.com/crossplane/upjet/pull/343
https://github.com/crossplane/upjet/pull/350
https://github.com/crossplane/docs/pull/560
https://github.com/crossplane/docs/pull/569

To-be-donated-to-Crossplane provider-aws:

https://github.com/upbound/provider-aws/pull/938
https://github.com/upbound/provider-aws/pull/1086

Issues reported

https://github.com/crossplane/crossplane/issues/4401
https://github.com/crossplane/docs/issues/568
https://github.com/crossplane/upjet/issues/271
https://github.com/crossplane/upjet/issues/295
https://github.com/crossplane/upjet/issues/298
https://github.com/crossplane/upjet/issues/299
https://github.com/crossplane/upjet/issues/303

To-be-donated-to-Crossplane provider-aws:

https://github.com/upbound/provider-aws/pull/811
https://github.com/upbound/provider-aws/issues/813

+1

+1 for sure! ✅

@mergenci has been invited to join the Crossplane org now ✅


Response to Reviewers tasks

This will be added to and checked off as I work through the response document for me to keep track of stuff I'm handling.

[x] Check if we are scaling by tau_max in the results shown in the manuscript.
[ ] Add a figure comparing results with no scaling and scaling.

[x] Add the left censored (LC) test description.
[x] Add LC test to the manuscript code. Probably have to just add it to general functions given we don't want to trigger a full rebuild (check if we are caching the MD5 of the package).
[ ] LC results on each dataset.
[ ] Missingness observed in each dataset.
[ ] Convert the missingness figures to the updated ones we've been using in the package documentation (see bottom of https://moseleybioinformaticslab.github.io/ICIKendallTau/articles/testing-for-left-censorship.html).

The values are being scaled by the maximum calculated tau_max, but all correlations are scaled by it in the same way, so the values would just be shifted slightly. I can still add a comparison figure to the supplement, but it should just show a change in overall scale.


Version-related improvements.

All expected CI checks have passed.

Thanks for the contribution :+1:
Integrated in b012e1e7182
Topic has been integrated as it was expect for the first commit where only  PY_VERSION_PATCH is set in the cache.

Thanks!
On Mon, Jan 25, 2016 at 2:38 PM, Jean-Christophe Fillion-Robin <
<EMAIL_ADDRESS>wrote:

Closed #108
https://github.com/python-cmake-buildsystem/python-cmake-buildsystem/pull/108
.
—
Reply to this email directly or view it on GitHub
https://github.com/python-cmake-buildsystem/python-cmake-buildsystem/pull/108#event-525451608
.


Github Pages returns 404

The launched Github environment that's supposed to hold the docs, returns a 404.

The GitHub pages environment you mentioned is solely used for Helm Chart releases. Our documentation can be found in the README.md and in the docs folder.
In case you are actually looking for our Helm releases on a technical level, take a look here.


after running sysbench write for a long time（3 days）, one tikv oom

Bug Report

What version of TiKV are you using?
[2022/03/15 22:27:13.395 +08:00] [INFO] [client.go:376] ["Cluster version information"] [type=tidb] [version=6.0.0-nightly] [git_hash=ed489e6f2c8ded4f76bd96483863ac0cbfabac1d]
[2022/03/15 22:27:13.395 +08:00] [INFO] [client.go:376] ["Cluster version information"] [type=tikv] [version=6.0.0-alpha] [git_hash=b394b4d1e88b401c58e1255da043300c00cbe5c7]
[2022/03/15 22:27:13.395 +08:00] [INFO] [client.go:376] ["Cluster version information"] [type=pd] [version=6.0.0-nightly] [git_hash=5154c0bb55abcb8dcfc5a4776323d820fa324967]
What operating system and CPU are you using?
8core、16G
Steps to reproduce
NS：glh-master-crqq7
1、BR import data
[2022/03/15 22:27:13.442 +08:00] [INFO] [cmd.go:124] ["Start remote command"] [cmd="export AWS_ACCESS_KEY_ID=minioadmin;export AWS_SECRET_ACCESS_KEY=minioadmin;/br restore full --send-credentials-to-tikv=true --pd http://tc-pd.glh-master-crqq7:2379 --storage s3://benchmark/tpcc-1000-4.0 --s3.endpoint http://minio.pingcap.net:9000 --check-requirements=false"] [nodename=br]
[2022/03/15 22:35:01.376 +08:00] [INFO] [cmd.go:124] ["Start remote command"] [cmd="export AWS_ACCESS_KEY_ID=minioadmin;export AWS_SECRET_ACCESS_KEY=minioadmin;/br restore full --send-credentials-to-tikv=true --pd http://tc-pd.glh-master-crqq7:2379 --storage s3://benchmark/sysbench-32-10000000 --s3.endpoint http://minio.pingcap.net:9000 --check-requirements=false"] [nodename=br]
2022-03-15T22:35:01.376+0800 INFO k8s/client.go:195 it should be noted that a long-running command will not be interrupted even the use case has ended. For more information, please refer to https://github.com/pingcap/test-infra/discussions/129
Detail BR log in /tmp/br.log.2022-03-15T14.35.01Z
2、run sysbench oltp_read_write
[2022/03/15 22:41:09.771 +08:00] [INFO] [cmd.go:124] ["Start remote command"] [cmd="sysbench --mysql-user=root --db-driver=mysql --time=0 --report-interval=10 --mysql-db=test --mysql-host=tc-tidb.glh-master-crqq7 --mysql-port=4000 --threads=64 --tables=32 --table-size=10000000 --mysql-ignore-errors=2013,1213,1105,1205,8022,8027,8028,9004,9007 --rand-type=uniform oltp_read_write run"] [nodename=benchtoolset]
3、updateRaftEngineConfig
[2022/03/15 23:01:40.314 +08:00] [INFO] [oltp_rel_005_test.go:114] ["update tc config done"] [option="[raft-engine]\nenable = false"] [elapsed=9m30.23872277s]
[2022/03/15 23:42:10.633 +08:00] [INFO] [oltp_rel_005_test.go:114] ["update tc config done"] [option="[raft-engine]\nenable = true"] [elapsed=20m0.101070657s]
4、The workload runs continuously for 3 days
What did you expect?
all tikv are normal
What did happened?
one tikv oom（related issue：https://github.com/tikv/pd/issues/4732）

/type bug
/severity Critical
/assign nolouch

https://github.com/tikv/tikv/pull/12189 try to fix it, @JmPotato  Does it works?

#12189 try to fix it, @JmPotato Does it works?

https://github.com/tikv/tikv/pull/11952 introduced the OOM bug, https://github.com/tikv/tikv/pull/12177 fixed it. I think we can close this issue.

It seems the OOM bug is already fixed, can we close this issue? cc @Lily2025


🐛 cloud_functions FormatException: Invalid envelope

Bug report
Describe the bug
I try to call the function, but it does not call it and throws an FormatException: Invalid envelope error on the catch function
Steps to reproduce the behavior:
Future<String> createCloudFunction(String orderID) async {
    try {
      CloudFunctions functions = CloudFunctions.instance;
      HttpsCallable createIntent = functions.getHttpsCallable(functionName: "createIntent");

      Map<dynamic, dynamic> map = {"order": mapIt()};

      HttpsCallableResult result = await createIntent.call(map);

      return result.data["result"];
    } catch (e) {
      print(e.toString());
      return "error";
    }
  }

  mapIt() {
    Map<String, dynamic> orderMap = {};
    Map<String, dynamic> items = {};

    items["itemID1"] = {"name": "itemOneName", "quantity": 10};
    items["itemID2"] = {"name": "itemTwoName", "quantity": 20};

    orderMap["items"] = items;

    return orderMap;
  }

Expected behavior
I expect this code to call the cloud function, and to receive a response instead this code does not call the function and throws an invalid envelope error

Additional context
Add any other context about the problem here.

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
Downloading package sky_engine...                                   1,1s
Downloading flutter_patched_sdk tools...                            5,5s
Downloading flutter_patched_sdk_product tools...                    4,1s
Downloading linux-x64 tools...                                     12,1s
Downloading android-arm-profile/linux-x64 tools...                  1,7s
Downloading android-arm-release/linux-x64 tools...                  1,1s
Downloading android-arm64-profile/linux-x64 tools...                1,4s
Downloading android-arm64-release/linux-x64 tools...                1,0s
Downloading android-x64-profile/linux-x64 tools...                  0,9s
Downloading android-x64-release/linux-x64 tools...                  1,2s
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel beta, 1.20.0, on Linux, locale es_MX.UTF-8)
[!] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    ✗ Android license status unknown.
      Try re-installing or updating your Android SDK Manager.
      See https://developer.android.com/studio/#downloads or visit https://flutter.dev/docs/get-started/install/linux#android-setup for detailed instructions.
[✓] Chrome - develop for the web
[!] Android Studio (not installed)
[✓] Connected device (2 available)

! Doctor found issues in 2 categories.

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
Dart SDK 2.9.0-21.10.beta
Flutter SDK 1.20.0
campomio_directpos 1.0.0+1

dependencies:
- autocomplete_textfield 1.7.3 [flutter]
- badges 1.1.3 [flutter]
- camera 0.5.8+9 [flutter]
- cloud_firestore 0.14.1+3 [flutter meta quiver firebase_core firebase_core_platform_interface cloud_firestore_platform_interface cloud_firestore_web]
- cloud_functions 0.6.0+1 [meta flutter firebase_core cloud_functions_platform_interface cloud_functions_web]
- connectivity 0.4.9+5 [flutter meta connectivity_platform_interface connectivity_macos connectivity_for_web]
- cupertino_icons 0.1.3
- firebase_analytics 6.0.2 [meta flutter firebase_core firebase_analytics_web firebase_analytics_platform_interface]
- firebase_auth 0.18.1+2 [meta firebase_core firebase_core_platform_interface firebase_auth_platform_interface firebase_auth_web flutter]
- firebase_core 0.5.0+1 [firebase_core_platform_interface flutter quiver meta firebase_core_web]
- fluro 1.6.4 [flutter]
- flutter 0.0.0 [characters collection meta typed_data vector_math sky_engine]
- flutter_credit_card 0.1.3 [flutter]
- flutter_easyloading 1.3.0 [flutter flutter_spinkit]
- font_awesome_flutter 8.10.0 [flutter]
- get_it 4.0.4 [async meta]
- google_fonts 1.1.1 [flutter http path_provider crypto pedantic]
- google_sign_in 4.5.5 [google_sign_in_platform_interface flutter meta google_sign_in_web]
- intl 0.16.1 [path]
- line_awesome_icons 1.0.4+2 [flutter]
- location 2.5.4 [flutter meta]
- property_change_notifier 0.2.0 [flutter]
- provider 3.2.0 [flutter]
- random_string 2.1.0
- stripe_payment 1.0.8 [flutter]
- stripe_sdk 2.8.2 [flutter http url_launcher uni_links mask_text_input_formatter awesome_card flutter_slidable simple_animations supercharged]
- websafe_svg 1.1.0 [flutter convert flutter_svg http meta logging]

dev dependencies:
- flutter_test 0.0.0 [flutter test_api path fake_async clock stack_trace vector_math async boolean_selector characters charcode collection matcher meta source_span stream_channel string_scanner term_glyph typed_data]

transitive dependencies:
- async 2.4.2 [collection]
- awesome_card 1.1.0 [flutter]
- boolean_selector 2.0.0 [source_span string_scanner]
- characters 1.0.0
- charcode 1.1.3
- clock 1.0.1 [meta]
- cloud_firestore_platform_interface 2.1.2 [flutter meta collection firebase_core plugin_platform_interface]
- cloud_firestore_web 0.2.0+4 [flutter flutter_web_plugins firebase http_parser meta firebase_core cloud_firestore_platform_interface js]
- cloud_functions_platform_interface 2.0.0 [flutter meta firebase_core plugin_platform_interface]
- cloud_functions_web 2.0.0 [cloud_functions_platform_interface flutter flutter_web_plugins firebase http_parser meta]
- collection 1.14.13
- connectivity_for_web 0.3.1+2 [connectivity_platform_interface flutter_web_plugins flutter]
- connectivity_macos 0.1.0+5 [flutter]
- connectivity_platform_interface 1.0.6 [flutter meta plugin_platform_interface]
- convert 2.1.1 [charcode typed_data]
- crypto 2.1.5 [collection convert typed_data]
- fake_async 1.1.0 [clock collection]
- ffi 0.1.3
- file 5.2.1 [intl meta path]
- firebase 7.3.2 [http http_parser js]
- firebase_analytics_platform_interface 1.0.3 [flutter meta]
- firebase_analytics_web 0.1.1 [flutter flutter_web_plugins firebase firebase_analytics_platform_interface meta]
- firebase_auth_platform_interface 2.1.1 [flutter meta firebase_core plugin_platform_interface]
- firebase_auth_web 0.3.1+1 [flutter flutter_web_plugins firebase meta http_parser intl firebase_core firebase_auth_platform_interface js]
- firebase_core_platform_interface 2.0.0 [flutter meta plugin_platform_interface quiver]
- firebase_core_web 0.2.0 [firebase firebase_core_platform_interface flutter flutter_web_plugins meta js]
- flutter_slidable 0.5.7 [flutter]
- flutter_spinkit 4.1.2+1 [flutter]
- flutter_svg 0.17.4 [path_drawing xml vector_math meta flutter]
- flutter_web_plugins 0.0.0 [flutter characters collection meta typed_data vector_math]
- google_sign_in_platform_interface 1.1.2 [flutter meta quiver]
- google_sign_in_web 0.9.2 [google_sign_in_platform_interface flutter flutter_web_plugins meta js]
- http 0.12.2 [http_parser path pedantic]
- http_parser 3.1.4 [charcode collection source_span string_scanner typed_data]
- js 0.6.2
- logging 0.11.4
- mask_text_input_formatter 1.1.0 [flutter]
- matcher 0.12.8 [stack_trace]
- meta 1.1.8
- path 1.7.0
- path_drawing 0.4.1+1 [vector_math meta path_parsing flutter]
- path_parsing 0.1.4 [vector_math meta]
- path_provider 1.6.21 [flutter path_provider_platform_interface path_provider_macos path_provider_linux path_provider_windows]
- path_provider_linux 0.0.1+2 [path xdg_directories path_provider_platform_interface flutter]
- path_provider_macos 0.0.4+4 [flutter]
- path_provider_platform_interface 1.0.3 [flutter meta platform plugin_platform_interface]
- path_provider_windows 0.0.4+1 [path_provider_platform_interface meta path flutter ffi win32]
- pedantic 1.9.0
- petitparser 3.0.4 [meta]
- platform 2.2.1
- plugin_platform_interface 1.0.3 [meta]
- process 3.0.13 [file intl meta path platform]
- quiver 2.1.3 [matcher meta]
- sa_anicoto 1.0.3 [flutter supercharged]
- sa_multi_tween 1.1.3 [flutter supercharged]
- sa_stateless_animation 1.0.3 [flutter supercharged sa_anicoto]
- sa_v1_migration 1.1.2 [flutter]
- simple_animations 2.2.3 [flutter sa_multi_tween sa_anicoto sa_stateless_animation sa_v1_migration]
- sky_engine 0.0.99
- source_span 1.7.0 [charcode collection meta path term_glyph]
- stack_trace 1.9.5 [path]
- stream_channel 2.0.0 [async]
- string_scanner 1.0.5 [charcode meta source_span]
- supercharged 1.10.0 [supercharged_dart flutter]
- supercharged_dart 1.2.0
- term_glyph 1.1.0
- test_api 0.2.17 [async boolean_selector collection meta path source_span stack_trace stream_channel string_scanner term_glyph matcher]
- typed_data 1.2.0 [collection]
- uni_links 0.4.0 [flutter]
- url_launcher 5.7.5 [flutter url_launcher_platform_interface url_launcher_web url_launcher_linux url_launcher_macos url_launcher_windows]
- url_launcher_linux 0.0.1+1 [flutter]
- url_launcher_macos 0.0.1+8 [flutter]
- url_launcher_platform_interface 1.0.8 [flutter meta plugin_platform_interface]
- url_launcher_web 0.1.4+1 [url_launcher_platform_interface flutter flutter_web_plugins meta]
- url_launcher_windows 0.0.1+1 [flutter]
- vector_math 2.0.8
- win32 1.7.3 [ffi]
- xdg_directories 0.1.0 [path process flutter]
- xml 3.7.0 [collection convert meta petitparser]

Hi @salvadorbarb1
Seems like this is just a connection issue (SO answer). Are you having any connection issues? If you are using an emulator could you try the suggested solution?
Thank you

Actually I'm not using an emulator, to try that solution.
Is it any difference to try it that way?
Should I set my emulators and try it that way?

If you are not using an emulator that solution probably won't help.
You could also try upgrading to the stable release cloud_functions: ^0.7.0+1


API Site down 6/13: Angular dependency issue?

API site fails to load Angular currently, defaults to unstyled html (see screenshot). I tested on Chrome, Firefox and Safari on multiple different pages.

I can verify that I've been having the same issue. ( on https://docs.angularjs.org/api )

having the same issue

+1

+1

+1

+1

Don't enter "+1" guys, you can just "like" the issue now, and it's less spammy that way =)
/CC @jeffbcross maybe you can poke someone to see what's wrong with the google CDN?

+1

Docs should be back up. You may need to do a hard reload for it to take effect. Thanks for noticing.

Looks good!

Hi Everyone! Sorry about the docs outage.
We made a change to our tooling so that we would have a better build experience while working offline. See https://github.com/angular/angular.js/commit/6a134605f1904098022f4e25ade67d0a91a52621
The aim of this commit was to prevent requests to remote servers for get the release tags and check the CDN versions when the building machine was not connected to the internet. In this cases we would still be able to build but we would not get the correct version information for the "production" docs app.
This commit was merged into master at 14:57 UTC and master builds started using it on our CI server.
Unfortunately our CI server seems to think it is offline at random points during its builds, even though it is permanently connected to the internet. We are not sure why - perhaps its bandwidth or latency is a bit flakey.
So although the builds to master succeeded, resulting in updates to our docs website, the CDN information was missing, which caused the production version of the site to fail to load the angular libraries.
@gkalpak reverted the offending commit at 17:44pm but the master build takes over 25 minutes to run.
@jeffbcross manually reverted the update to the docs website which brought it back online around 18:00 UTC.
Now that the commit has been reverted, future builds should not cause the docs to fail in the same way.
We are looking at alternative mechanisms for improving our offline local builds that will not impact on the CI production builds in this way. We will also look into ways of aborting the CI builds if the internet connection is too flakey to get hold of the CDN versions.

Thanks @caitp  for escalating this

@petebacondarwin was there an e2e test that should have caught this breakage before it was pushed?

All our e2e tests run against local copies of angular rather than the production copies hosted on the CDN so, no we didn't have a test that would catch this.
Good idea though, I will look at whether we can easily implement it as part of my work of preventing this from happening again...


lib/picolibc: Add CONFIG_PICOLIBC_PREFERRED

This selects picolibc if it is supported, otherwise falls back to newlib or minimal libc as appropriate. This is useful when running twister to select picolibc everywhere it can be used without failing to build when it cannot.
Signed-off-by: Keith Packard<EMAIL_ADDRESS>

Since we are going to make Picolibc the default libc in the near future, do we really want to introduce PICOLIBC_PREFERRED in 3.3 only to deprecate it in 3.4?

I'm not sure -- I find it very helpful when doing testing though, so perhaps it will be a useful during the transition, allowing existing configurations to continue to work while we test 'picolibc by default' in CI with this flag? As you might have noticed, I'm submitting PRs for every patch I've got that helps make zephyr work with picolibc.


[10.x] Can apply WithoutRelations to entire class

Can target the entire class so that no model has relationships set. Will not interfere with other properties.
use App\Models\Podcast;
use App\Models\User;
use App\Models\DistributionPlatform;
use App\DataObject;
use Illuminate\Queue\SerializesModels;
use Illuminate\Queue\Attributes\WithoutRelations;

#[WithoutRelations]
class ProcessPodcastJob
{
    use SerializesModels;

    public function __construct(
        public Podcast $podcast,
        public User $user,
        public DistributionPlatform $platform,
        public DataObject $dataObject
    ) {}
}

All of the models will be serialized without relationships (rather than having to repeatedly apply the attribute to each model), while non-models will be unaffected.

@cosmastech thanks for your job, what do you think about adding documentation for this?


Windows: Fix quiche test compilation

Commit Message:
Windows: Fix quiche test compilation

Add patch to fix various quiche compilation issues with MSVC
Skip uses of GSO as it is not available on Windows
Fix syscall result types
Fix usage of Edge event trigger
move ifdef that avoids a test on non-Linux to ensure test doesn't
appear to pass in test results
quiche integration test is still failing, requires further
investigation

Additional Description:
Regarding quiche patch:

Just a quick and dirty POC
Hopefully we can get changes into quiche that obsolete the patch
See: https://github.com/envoyproxy/envoy/issues/10420

Risk Level: Low
Testing: Enables quiche tests on Windows, verified locally on Windows
Docs Changes: N/A
Release Notes: N/A
Fixes #10420

Assigning over to @danzh2010. Can we potentially just fix these issues upstream?

Assigning over to @danzh2010. Can we potentially just fix these issues upstream?

yes, I can fix it in QUICHE

Assigning over to @danzh2010. Can we potentially just fix these issues upstream?

yes, I can fix it in QUICHE

Thanks @danzh2010 whenever your changes are ready we can drop the quiche patch and bump the dependency

Hope you had a good holiday weekend @danzh2010 - just a weekly ping to check in on this issue and unblock us. (Let us know if it will take a few weeks, and we can always patch and revert later once a fix lands upstream.)

/retest

@danzh2010 Looks like this patch is back in shape with master, if you could take a look at what remains of the initial delta. The net effect is
Tests bypassed as skip_on_windows: 18 known unbuildable or inapplicable tests (Previously 29)
Tests bypassed as fails_on_windows: 13 known incompatible tests (Addition of 1 formerly unbuildable, now failing quic test)
Tests bypassed as flaky_on_windows: 20 known unstable tests

@danzh2010 my efforts to pick up the new work at quiche are proving fruitless, I expect we need you to bump and then we can clean up this PR and get the tests running. Dinking with bazel/repository_locations.bzl;
     com_googlesource_quiche = dict(
```...

   # 2020-09-09: Pick up fix for Windows compilation errors

   version = "7f547143b82d4ea8fc34161a0c014f655449c1f5",

   sha256 = "f8e7ee8d31f952f709785a9c9f5921fd2efa7f6e64ad4ae0565df51f50a91dee",

I experimented with multiple hacks to test this.

Of the list below, the version isn't recognized at storage.googleapis.com, on quiche.googlesource.com the sha256 changes every blinking time it gets downloaded (generated on the fly with the current timestamp perhaps?) and finally, from the third mirror/fork below...

   urls = [

       # "https://storage.googleapis.com/quiche-envoy-integration/{version}.tar.gz",

       # "https://quiche.googlesource.com/quiche/+archive/{version}.tar.gz",

       "https://github.com/flyaways/quiche/archive/{version}.tar.gz",

   ],

the branch's quiche.BUILD appears broken or out-of-sync;

ERROR: C:/_eb/external/com_googlesource_quiche/BUILD.bazel:1277:14: @com_googlesource_quiche//:quic_core_proto_source_address_token_proto: missing input file 'external/com_googlesource_quiche/quiche/quic/core/proto/cached_network_parameters.proto', owner: '@com_googlesource_quiche//:quiche/quic/core/proto/cached_network_parameters.proto'
ERROR: C:/_eb/external/com_googlesource_quiche/BUILD.bazel:1877:17 1 input file(s) do not exist
and haven't been able to work out precisely what broke here.

We are on hold for https://github.com/envoyproxy/envoy/pull/13066 to be fixed in gcc and merged, at which point this patch should become simpler.
/wait

/retest

/retest-circle

@danzh2010 after all of your efforts, the proposal is reduced to this to bring two handfuls of skipped tests back to action on Windows. I'd like you to do a first-pass over the remaining bits, I've force-merged a rebase to avoid the confusion of all the small tweaks we had had to apply. If you can give it a pass we can drop the skipped on windows by a third.

/retest-circle

@danzh2010 I'm not sure where you would like these notes recorded, but this is feedback of the latest effort to upstream problems we are hitting with quiche;
We still have to disable -wd4068, because of unguarded #pragma GCC (originally, clang) occurring in quiche external prototype headers. But that isn't a big problem if we modify quiche.genrule_cmd to do the right thing with respect to clang, vs gcc, vs msvc, and I'm adding a note for bazel_internal.bzl to that effect.
This patch now includes many commits just to undo the #pragma GCC headache that existed at envoy. The guards could be more carefully focused as needed, by checking the GCC version, use clang or msvc equivalents where appropriate, and even be fancier about it if we want; https://stackoverflow.com/questions/3378560/how-to-disable-gcc-warnings-for-a-few-lines-of-code - this is just a straightforward stopgap.
Globally from bazel/external/quiche.BUILD, this is a newer addition to gcc since (Ubuntu 9.3.0-11ubuntu0~18.04.1) 9.3.0;;
cc1plus: error: unrecognized command line option '-Wno-range-loop-analysis' [-Werror]
cc1plus: all warnings being treated as errors

It seems we need a feature detection here and dodge specific gcc flavors.
We have this compilation failure on gcc (Ubuntu 9.3.0-11ubuntu0~18.04.1) 9.3.0;
bazel-out/k8-fastbuild/bin/external/com_googlesource_quiche/quiche/quic/core/quic_framer.cc: In member function 'bool quic::QuicFramer::AppendIetfAckFrameAndTypeByte(const quic::QuicAckFrame&, quic::QuicDataWriter*)':
bazel-out/k8-fastbuild/bin/external/com_googlesource_quiche/quiche/quic/core/quic_framer.cc:5546:61: error: comparison of integer expressions of different signedness: 'size_t' {aka 'long unsigned int'} and 'int' [-Werror=sign-compare]
 5546 |         static_cast<size_t>(writer->remaining() - ecn_size) <
      |         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
 5547 |             QuicDataWriter::GetVarInt62Len(gap) +
      |             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 5548 |                 QuicDataWriter::GetVarInt62Len(ack_range)) {
      |                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Perhaps a judicious -Wno-sign-compare would work around this, but that's just a hack. What about ssize_t rather than of size_t? I'm curious why only we see it on gcc default bazel build, and it isn't observed in CI.
Fastbuild does not set _DEBUG. It also does not set NDEBUG; examining this error on windows msvc-cl;
ERROR: C:/_eb/external/com_googlesource_quiche/BUILD.bazel:2192:17: C++ compilation of rule '@com_googlesource_quiche//:quic_core_frames_frames_lib' failed (Exit 2)
C:\_eb\execroot\envoy\bazel-out\x64_windows-fastbuild\bin\external\com_googlesource_quiche\quiche/quic/core/frames/quic_frame.h(99): error C2926: 'quic::QuicFrame::<unnamed-tag>::delete_forbidden': a default member initializer is not allowed for a member of an anonymous struct within a union

It isn't clear if this defect is specific to Windows (due to the previous error on gcc), but by papering over this in quiche.BUILD with a feature define to force QUIC_FRAME_DEBUG=0 got us past this new problem.

I have an alternate suggestion for all the pragmas to disable warnings: Could we create quiche_include_pre.h and quiche_include_post.h, and bracket those around quiche includes, and put all the warning-disable flags, and compiler ifdefs for warning-disable flags, into the pre and post, so we don't duplicate all that junk in every file?

I would not do that. precisely.... rather have a quiche_core_includes.h header that handles the 80/20 of the most commonly needed quiche headers by many sources, and handles the pragmas and inclusions.
The other rare exceptions can be handled by the sources which consume them.
The actual pragmas warnings ignored required do vary by included header and compiler (including clang/gcc differences which are glossed over at present.)

I have an alternate suggestion for all the pragmas to disable warnings: Could we create quiche_include_pre.h and quiche_include_post.h, and bracket those around quiche includes, and put all the warning-disable flags, and compiler ifdefs for warning-disable flags, into the pre and post, so we don't duplicate all that junk in every file?

I would not do that. precisely.... rather have a quiche_core_includes.h header that handles the 80/20 of the most commonly needed quiche headers by many sources, and handles the pragmas and inclusions.
The other rare exceptions can be handled by the sources which consume them.
The actual pragmas warnings ignored required do vary by included header and compiler (including clang/gcc differences which are glossed over at present.)

For compiling external-to-envoy source, I'd say we can just disable all the warnings that occur in any quiche header, for every quiche header.

I will fix these 3 issues in upstream. As to #pragma GCC override, I don't have strong preference in either way, they all seems to be one time change and eventually, QUICHE will be in a state that we don't need them.

That's awesome news, thank you. Lets please still land this patch in the interim? I'd rather we didn't miss the 1.16 window due to upstream/elsewhere issues.
@ggreenway I think you might agree that there is zero return for investing more cycles at refactoring the existing pragma GCC mess, if we expect to eliminate them wholesale as the quiche project catches up with the language standards?

I will fix these 3 issues in upstream. As to #pragma GCC override, I don't have strong preference in either way, they all seems to be one time change and eventually, QUICHE will be in a state that we don't need them.

That's awesome news, thank you. Lets please still land this patch in the interim? I'd rather we didn't miss the 1.16 window due to upstream/elsewhere issues.
@ggreenway I think you might agree that there is zero return for investing more cycles at refactoring the existing pragma GCC mess, if we expect to eliminate them wholesale as the quiche project catches up with the language standards?

Makes sense. Let's go with the pragma changes in this PR; we can revisit later if the situation changes.

@mattklein123 I think this satisfies all your questions and concerns; the ASAN failure is our shared CI issue, not a regression.


Switch does not fire change event

It seems as though the node.addEventListener(m.k... event is not being triggered by the bootstrap.toggle?
If the code is changed to use jquery $(node).on(m.k... it works as expected.
Is this a known issue or am I missing something?

Would you give me a code sample to try? Specifically, which Ooui object are you instantiating?

Here's an example of what I'm trying to do:
https://github.com/bjorndaniel/SwitchError
What I would like to happen is for the label to change on toggle, and this does happen if I high-jack your node.addEventListener and instead add jquerys listener using $(node).on
I find this weird since they should behave the same way, but it is js after all...


Mcs 1647 add novel tool materials v123

Added 3 sets of the tool_rect, each set has a mat on the tool:
v1 has:

Assets/Addressables/MCS/UnityAssetStore/YughuesFreeMetalMaterials/Materials/M_YFMM_15.mat (brown texture)

v2 has:

Assets/Addressables/MCS/UnityAssetStore/YughuesFreeMetalMaterials/Materials/M_YFMM_34.mat (pink texture)

v3 has:

Assets/Addressables/MCS/UnityAssetStore/YughuesFreeMetalMaterials/Materials/M_YFMM_36.mat (green texture)

The corresponding ticket for the scene generator:
https://github.com/NextCenturyCorporation/mcs-private/pull/388

I think this can be done without additional objects.

Since the tool materials are already in the TOOL_MATERIAL_REGISTRY inside of MCSConfig you should be able to just set the materials property on the object.
Here is me setting it

And here is the result

Notice the tool type though in the second screenshot. In my version it is not a v1,v2,v3. It is the normal type. So there shouldn't be a need for all of the new objects. Setting the materials on the base tool type should be enough.

@jaudick You totally missed the conversation we had about this while you were on vacation :)
Phi originally implemented it the way you suggested: https://github.com/NextCenturyCorporation/ai2thor/pull/306
But we realized this would require a new Unity release, which we don't want to do. So we're (unfortunately) doing it this way for Eval 6, but will go back to doing it the "right way" for the 0.7.0 release.

Looks good. Novel tools rendered properly when running via Python.
Do we want to keep the old PR open, but wait to merge it in until we're preparing the 0.7.0 release? We'll need to make a few minor code changes there too for backwards compatibility.
#306

Not a problem, I'll reopen it.


Ademamix mixing

FYI, mixing with Ademamix gives great performances :
https://github.com/edmondja/AdEMAMix-ADOPT-Optimizer-Pytorch/blob/main/AdEMAMix-ADOPT.py

FYI, mixing with Ademamix gives great performances : https://github.com/edmondja/AdEMAMix-ADOPT-Optimizer-Pytorch/blob/main/AdEMAMix-ADOPT.py

Does it need higher VRAM? I dont know why, but it gets stuck after 2 steps. I can use the vanilla AdEMAmix with my 16G card on stable diffusion's lora training smoothly.

Ah interesting, it shouldnt as we are only dividing but some value already existing and we arent making a deepcopy of it

Ah interesting, it shouldnt as we are only dividing but some value already existing and we arent making a deepcopy of it

oh, maybe the precision? Can you make a 8-bit version, it seems that it is float32. bnb has a 8-bit implementation of the vanilla one:  https://github.com/bitsandbytes-foundation/bitsandbytes/blob/main/bitsandbytes/optim/ademamix.py

I modified line 88 of bnb  under the # Update the EMAs section.
It runs, and the logs look okay. Let’s see if the results improve.
\Lib\site-packages\bitsandbytes\optim
            # Update the EMAs
			if torch.min(nu) == 0:
				sq_norm = torch.ones_like(grad)
			else:
				sq_norm = torch.maximum(torch.sqrt(nu), torch.tensor(eps * 100))

            m1.mul_(beta1).addcdiv_(grad, sq_norm, alpha=1 - beta1)
            m2.mul_(beta3).addcdiv_(grad, sq_norm, alpha=1 - beta3)
            nu.mul_(beta2).addcmul_(grad, grad, value=1 - beta2)

I also noticed that adopt has been updated with add_clip to help stabilize the early stages.
How to implement the same operation in this version?

            # Update the EMAs
            if torch.min(nu) == 0:
                sq_norm = torch.ones_like(grad)
            else:
                sq_norm = torch.maximum(torch.sqrt(nu), torch.tensor(eps * 100))

            m1.mul_(beta1).addcdiv_(grad, sq_norm, alpha=1 - beta1)
            m2.mul_(beta3).addcdiv_(grad, sq_norm, alpha=1 - beta3)
            nu.mul_(beta2).addcmul_(grad, grad, value=1 - beta2)

            # Compute step
            denom = (nu.sqrt() / (bias_correction2**0.5)).add(eps)
            update = (m1.div(bias_correction1) + alpha * m2) / denom

            # Compute norm gradient
            mask = (nu * grad > 0).to(grad.dtype)
            mask = mask * (mask.numel() / (mask.sum() + 1))
            norm_grad = (nu * mask) / denom
            p.add_(norm_grad, alpha=-lr * update)

Cautious Optimizer (C-Optiom): Improving Training with One Line of Code
https://github.com/kyleliang919/C-Optim/tree/main
Try adding this.
Not sure if it's correct, but judging by the training results, it seems pretty good.

            # Update the EMAs
            if torch.min(nu) == 0:
                sq_norm = torch.ones_like(grad)
            else:
                sq_norm = torch.maximum(torch.sqrt(nu), torch.tensor(eps * 100))

            m1.mul_(beta1).addcdiv_(grad, sq_norm, alpha=1 - beta1)
            m2.mul_(beta3).addcdiv_(grad, sq_norm, alpha=1 - beta3)
            nu.mul_(beta2).addcmul_(grad, grad, value=1 - beta2)

            # Compute step
            exp_avg = (m1.div(bias_correction1) + alpha * m2)
            denom = (nu.sqrt() / (bias_correction2**0.5)).add(eps)

            # Compute norm gradient
            mask = (exp_avg * grad > 0).to(grad.dtype)
            mask = mask * (mask.numel() / (mask.sum() + 1))
            norm_grad = (exp_avg * mask) / denom

            clip = group["step"] ** 0.25
            norm_grad.clamp_(-clip, clip)

            # Use stableadamw
            rms_min = 1.0
            rms = torch.div(
                grad.pow(2),
                torch.maximum(nu, (eps ** 2) * torch.ones_like(nu))
            ).mean().sqrt().item()
            new_lr = lr * (1. / max(1., rms / rms_min))

            p.add_(norm_grad, alpha=-new_lr)

            # Add weight decay
            if weight_decay > 0.0:
                p.add_(p, alpha=-new_lr * weight_decay)

    return loss

Try adding this.
Cautious Optimizer (C-Optiom): Improving Training with One Line of Code https://github.com/kyleliang919/C-Optim/tree/main
And stableadamw https://gist.github.com/mitchellnw/d42e22a0b9ec02ceaf4f7b4457f51423
Not sure if it's correct, but it seems pretty good by the training results.

That's great! I try 60ep on my small datasets for sdxl lora training (also use with immiscible noise), it seems to be better than the 150ep version with old method.

@And233 Thank you
Another modification: Add automatic warm-up like RAdam. You can try using a higher learning rate combined with a decay scheduler (e.g., 1e-3 ). From my testing, it looks much better than before.
The changes also start at line 88, to the return loss
            # ADOPT (https://github.com/iShohei220/adopt/blob/main/adopt.py)
            step = group["step"]
            denom = torch.clamp(nu.sqrt(), eps)
            norm_grad = grad / denom
            clip = step ** 0.25  # Define clip threshold
            norm_grad.clamp_(-clip, clip)

            # AdEMAMix (https://github.com/bitsandbytes-foundation/bitsandbytes/blob/main/bitsandbytes/optim/ademamix.py)
            m1.mul_(beta1).add_(norm_grad, alpha=1 - beta1)
            m2.mul_(beta3).add_(norm_grad, alpha=1 - beta3)
            nu.mul_(beta2).addcmul_(grad, grad, value=1 - beta2)
            exp_avg = m1.div(bias_correction1) + (alpha * m2)

            # C_AdamW (https://github.com/kyleliang919/C-Optim/tree/main)
            mask = (exp_avg * grad > 0).to(grad.dtype)
            mask = mask * (mask.numel() / (mask.sum() + 1))
            update = exp_avg * mask

            # StableAdamW (https://gist.github.com/mitchellnw/d42e22a0b9ec02ceaf4f7b4457f51423)
            rms_min = 1.0
            rms = torch.div(
                grad.pow(2),
                torch.maximum(nu, (eps ** 2) * torch.ones_like(nu))
            ).mean().sqrt().item()

            new_lr = lr * (1. / max(1., rms / rms_min))

            # RAdam (https://pytorch.org/docs/stable/_modules/torch/optim/radam.html#RAdam)
            rho_inf = 2 / (1 - beta2) - 1
            rho_t = rho_inf - 2 * step * (beta2**step) / bias_correction2

            def _compute_rect():
                return (
                    (rho_t - 4)
                    * (rho_t - 2)
                    * rho_inf
                    / ((rho_inf - 4) * (rho_inf - 2) * rho_t)
                ) ** 0.5

            def _compute_adaptive_lr():
                exp_avg_sq_sqrt = nu.sqrt()
                exp_avg_sq_sqrt = exp_avg_sq_sqrt.add_(eps)
                return (bias_correction2**0.5) / exp_avg_sq_sqrt

            if rho_t > 5.0:
                param.add_(
                    update
                    * new_lr
                    * _compute_adaptive_lr()
                    * _compute_rect(),
                    alpha=-1.0,
                )
            else:
                param.add_(update * new_lr, alpha=-1.0)

            # Add weight decay
            if weight_decay > 0.0:
                p.add_(p, alpha=-new_lr * weight_decay)

    return loss

@And233 Thank you
Another modification: Add automatic warm-up like RAdam. You can try using a higher learning rate combined with a decay scheduler (e.g., 1e-3 ). From my testing, it looks much better than before.
The changes also start at line 88, to the return loss
            # ADOPT (https://github.com/iShohei220/adopt/blob/main/adopt.py)
            step = group["step"]
            denom = torch.clamp(nu.sqrt(), eps)
            norm_grad = grad / denom
            clip = step ** 0.25  # Define clip threshold
            norm_grad.clamp_(-clip, clip)

            # AdEMAMix (https://github.com/bitsandbytes-foundation/bitsandbytes/blob/main/bitsandbytes/optim/ademamix.py)
            m1.mul_(beta1).add_(norm_grad, alpha=1 - beta1)
            m2.mul_(beta3).add_(norm_grad, alpha=1 - beta3)
            nu.mul_(beta2).addcmul_(grad, grad, value=1 - beta2)

            # C_AdamW (https://github.com/kyleliang919/C-Optim/tree/main)
            mask = (m1 * grad > 0).to(grad.dtype)
            mask = mask * (mask.numel() / (mask.sum() + 1))
            masked_m1 = m1 * mask

            update = masked_m1.div(bias_correction1) + (alpha * m2)

            # StableAdamW (https://gist.github.com/mitchellnw/d42e22a0b9ec02ceaf4f7b4457f51423)
            rms_min = 1.0
            rms = torch.div(
                grad.pow(2),
                torch.maximum(nu, (eps ** 2) * torch.ones_like(nu))
            ).mean().sqrt().item()

            new_lr = lr * (1. / max(1., rms / rms_min))

            # RAdam (https://pytorch.org/docs/stable/_modules/torch/optim/radam.html#RAdam)
            rho_inf = 2 / (1 - beta2) - 1
            rho_t = rho_inf - 2 * step * (beta2**step) / bias_correction2

            def _compute_rect():
                return (
                    (rho_t - 4)
                    * (rho_t - 2)
                    * rho_inf
                    / ((rho_inf - 4) * (rho_inf - 2) * rho_t)
                ) ** 0.5

            def _compute_adaptive_lr():
                exp_avg_sq_sqrt = nu.sqrt()
                exp_avg_sq_sqrt = exp_avg_sq_sqrt.add_(eps)
                return (bias_correction2**0.5) / exp_avg_sq_sqrt

            if rho_t > 5.0:
                param.add_(
                    update
                    * new_lr
                    * _compute_adaptive_lr()
                    * _compute_rect(),
                    alpha=-1.0,
                )
            else:
                param.add_(update * new_lr, alpha=-1.0)

            # Add weight decay
            if weight_decay > 0.0:
                p.add_(p, alpha=-new_lr * weight_decay)

    return loss

Do you mean try a scheduler like CosineAnnealing? I used to set a 20% warm up and constant scheduler with a high lr(5e-3). Could this RAdam take place of warmup steps?

RAdam automatically adjusts the learning rate to wait for an appropriate variance, so it should be able to replace warm-up.


Stuck at microk8s enable kubeflow -  Try microk8s enable kubeflow instead

Tried setting kebflow up in ubuntu with Microk8s
I followed the following steps
1) sudo snap install microk8s --classic --channel=latest/edge
2) sudo microk8s status --wait-ready
3) sudo usermod -a -G microk8s $USER
4) sudo chown -f -R $USER ~/.kube
5) microk8s.enable dns dashboard storage
6) microk8s.enable kubeflow --bundle=lite
7) choose a password
8) microk8s.kubectl get all --all-namespaces
9) http://<IP_ADDRESS>.xip.io

Here is the problem, It just stops working at microk8s.enable kubeflow --bundle=lite. This is the error I got

I tried again with microk8s enable kubeflow but I got the same error

@AdeloreSimiloluwa: You should run this command as a non-root user (try whoami or id to double-check your current user). Closing this issue as I believe the non-root check is working as intended, feel free to reopen if you encounter this error as a non-root user.

@AdeloreSimiloluwa: You should run this command as a non-root user (try whoami or id to double-check your current user). Closing this issue as I believe the non-root check is working as intended, feel free to reopen if you encounter this error as a non-root user.


[Bug]:

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
No privacy-policy page and terms page for the links in the footer
https://github.com/user-attachments/assets/b596f3c7-b70a-47a0-ba1b-47074111ed23
Expected behavior
There should be privacy-policy page and terms page
Add ScreenShots
No response
On which device are you experiencing this bug?
Chrome
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

@Vaishh18 the issue is solved


Correct check for unscaled-infeasibilities

The current check for unscaled-infeasibilities was incorrect.
The status of the GAMS model and CPLEX differ. The check for unscaled-infeasibilities has been updated from modelstat = 5 to solvestat = 4. Recent debugging showed, that when CPLEX solves with unscaled infeasibilities, "LP Status (5)" is displayed in the log of CPLEX, but GAMS translates this to modelstat=1 and solvestat=4 (Terminated by Solver). If CPLEX solves normally, then solvestat=1.
How to review

Read the diff and note that the CI checks all pass.
Build the documentation and check section "macro.html#issue-2-message-solves-optimally-with-unscaled-infeasibilities".

PR checklist

[x] Continuous integration checks all ✅
~- [ ] Add or expand tests; coverage checks both ✅~
[x] Add, expand, or update documentation.
[x] Update release notes.

LGTM, thanks @OFR-IIASA! If there are no objections, I will merge later today.


Key Vault JsonWebKey additional functionalities and IssuerParameters

Adding more functionalities to JsonWebKey: AES key conversions, verify, equals, clear memory and tests.
Change IssuerReference to IssuerParameters and adding CertificateType.

Runtime changes detected. pull request created. CI running:

Runtime changes detected. pull request created. CI running:


[Bug] Roboto font make 404 request in the WebUI

Changing staticfonts instead of static/fonts would fix it.
Verdaccion version 4.2.2

I guess you mean https://github.com/verdaccio/ui


Conditions pop-up display

Review and improve formatting of pop-up when a Condition is clicked.
Add Condition.notes (comments) into this view.
OHSU Feedback:
The pop-up that occurs when clicking on a condition is poorly formatted so that the text is overlapping and unreadable/not useful

Modified width and height -should have space for large text snippets


.aut missing ?

Hello,
I'm trying to use AutoQ, and I'm having a problem. Could you help me?
When I run this command:
./build/cli/autoq benchmarks/BernsteinVazirani/02/pre.aut benchmarks/BernsteinVazirani/02/circuit.qasm
I get this error:
Error: Unable to open file.
[ERROR] Unable to open the benchmarks/BernsteinVazirani/02/pre.aut file.

In addition, on Git I have:

Hello, due to some reasons, we've decided to change the extension of pre and post from *.aut to *.spec afterwards.
Simply run ./build/cli/autoq benchmarks/BernsteinVazirani/02/pre.spec benchmarks/BernsteinVazirani/02/circuit.qasm.
Sorry for the inconvenience.

Thank you.


[FLINK-31082][table-planner] Setting maven property 'flink.resueForks' to false in table planner module

What is the purpose of the change
This pr is aims to alleviate the CI OOM problem mentioned in issue: https://issues.apache.org/jira/browse/FLINK-18356.
Setting maven property flink.resueForks to false in table planner module can only reduce the frequency of oom error, but can't solve this problem.
Brief change log

change the pom.xml in table planner module.

Verifying this change
This pr need to run CI for multiple times to verify that the CI OOM problem will not frequently happen.
Does this pull request potentially affect one of the following parts:

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

Documentation

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

@swuferhong Thanks for the PR! Can you also create backports to the release-1.17 and release-1.16 branch?

Hi, @MartijnVisser. Because the root case of the error exit 137 OOM has not been completely found, I want to observe the master CI for a period of time, or cherry-pick it into the previous branch after finding a complete repair method. WDYT?

I would at least move it to release-1.17 given that we're trying to stabilize that as much as possible.

I would at least move it to release-1.17 given that we're trying to stabilize that as much as possible.

Ok, I will do it.


validation rule based on the value of another field

Is it possible to validate one field depending on the value of a different field?
I have a field called "action", if it holds the value "create", I want a different field to be Required. But if "action" is "delete" then the other field is allowed to be empty.

I got this working by creating a validation function and wrapping that in validation.By().
	requireManifestForCreateAction := func(v interface{}) error {
		if e.Action == "create" {
			return validation.Validate(v, validation.Required)
		}
		return nil
	}


[BUG] Flickering SFX screen background w/ Battery Saver mode

Describe the bug / feature
Enabling the Battery Saver mode, will make the Instrument screen of the Sound Editor (sfx.p64) have a flickering background. It seems to be linked to the Oscillator, and occurs when the window loses and regains focus.
Forum reports:

Adding an FX node causes the background to darken
Adding a second FX node causes the background to flicker
-- The V Man

In 'Battery Saver' mode, in the instrument creator, if I add an oscillator, mod or fx to the first carrier the background will flicker rapidly. In the regular mode, it just dims the background a bit.
-- phaselock.studio

When i add a modulator in the instrument editor (when i click the +mod button), the background of the editor starts flickering. This makes the instrument editor unusable for me because flickering graphics trigger my migraine and make me sick to the point of vomiting. I would love to see this fixed! :)
-- Sorm

To Reproduce
Steps to reproduce the behavior:

Start a new SFX workspace (uses the sfx.p64 app). Select the Inst Instrument tab. By default there should be an Oscillator present. Note the background: black with a dark grey, 4x4px diagonal dashed pattern - should be displayed normally.
Click on the Picotron menu (top left) and launch System Settings.
On second page of settings, enable Battery Saver mode. Close the screen.
When focus returns to the SFX Window, the background is now flickering. Adjusting the Oscillator seems to have some effect on the flicker.
Disabling Battery Saver, restores normal display.

Expected behavior
Window backgrounds don't flicker in Battery Saver mode.
Software (please complete the following information):

OS: macOS
Version: v0.1.0b

Re-tested with release v0.1.0c on macOS. Not fixed. Still flickers with Battery Saver enabled.

Fixed! Tested with release v0.1.0d on macOS.
Can no longer reproduce the flickering. 🎉


[BUG] JSON formatting issue on page navigation #55

The Bug
When I go back a page and come back to this page using the arrow left and right on the browser or other shortcuts like buttons on the mouse, the JSON formatting breaks, introducing \n, and adding a \ every time the action is repeated
How to reproduce
Just go back 1 page and come back when you are editing a record with a json field.
Screenshots
Before

After first back

After third back

Pocketbase V0.21.3

I've submitted a fix in master and it will be available with the next minor v0.22.1 release sometime later this week.


wasm: use io.ReadFull instead of Read

There is no guarantee that io.Read fulfills the given byte slice.
ReadByte should use io.ReadFull to ensure that instead.
Fixes #188

Codecov Report

Merging #189 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master     #189   +/-   ##
=======================================
  Coverage   70.24%   70.24%
=======================================
  Files          49       49
  Lines        5499     5499
=======================================
  Hits         3863     3863
  Misses       1283     1283
  Partials      353      353

Impacted Files
Coverage Δ

wasm/read.go
73.46% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

https://github.com/go-interpreter/license/pull/20 done :-)


Load priorities when there is no priorityscheme

FYI @nickfyson

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

LGTM
I'm unsure about the NPE check added in that other PR though. What are we trying to achieve with it? If priority is null it results in a diffferent problem, but it's still a 500 status?

The problem with the NPE is that if its thrown it sends the full stack trace as the response.

The problem with the NPE is that if its thrown it sends the full stack trace as the response.

Yep, Arthur's pull request fixed my concern with it.


1443 cleanup fix

Fixes for these issues: #1443, #1444, #1448
When a release is made with these changes, the release notes need to reflect the new required version of docker (1.13). See #1447

Done with changes, assuming tests pass

This has been tested in dev and cleanups seem to be working. I haven't been able to trigger a cleanup error to test the warnings.

Closes #1443, closes #1444, closes #1448

Closes #1444

Closes #1448


Refactor signal handling in yes, tee, and timeout

Edit : Original title was "yes: remove redundant dependency"
Yes, using libc while using nix was a bit redundant.

@sylvestre is macos not considered unix ? seems odd to me

I wonder if we could write something (clippy extension?) to detect this kind of pattern

I've been thinking about whether could get rid of using libc directly. It should be fairly easy to track if we remove the libc re-export from uucore and just check which utils mention libc in the Cargo.toml. nix covers most cases where we currently use libc and we could contribute missing functionality to nix directly. Like I've done here: https://github.com/nix-rust/nix/pull/1805

The CI fails seem unrelated.

Yeah the touch issue is known and the android issue seems unrelated.

I'll also take a look at
https://github.com/uutils/coreutils/blob/9090dd783ac91c9ee95d1d6c6d05b87ec6625a33/src/uu/tee/src/tee.rs#L138

@tertsdiepraam thanks for the review. Should I put this function in uucore as it is duplicated three times over?

Should I put this function in uucore as it is duplicated three times over?

Yeah I think that makes sense

The CI now seems to work. We'll check in later with the GNU test suite.

Those failing GNU test might be due to the bump to GNU coreutils 9.2, you probably don't need to worry about them.

hmm?

the trait uucore::error::UError is not implemented for `nix::errno::Errno
ah seems like most of UError is only for linux and android

Any issue on mac though?

That's unfortunate. I think nix should work for all unix platform, so feel free to change the cfg.

The errors seem unrelated to this PR


Fixes issue with the pfctl config on OSX

The previous config threw a syntax error when saving.

Thanks!


[ci] [R-package] clang18 jobs failing: _mm_malloc compilation errors

Description
The clang18 R-package job is failing across multiple PRs, with errors like this:
In file included from /usr/lib/llvm-18/lib/clang/18/include/xmmintrin.h:31:
/usr/lib/llvm-18/lib/clang/18/include/mm_malloc.h:32:40: error: 'alloc_align' attribute parameter 1 is out of bounds
   32 |                                        __alloc_align__(2)))
      |                                        ^               ~
/usr/lib/llvm-18/lib/clang/18/include/mm_malloc.h:33:1: error: static declaration of 'malloc' follows non-static declaration
   33 | _mm_malloc(size_t __size, size_t __align) {
      | ^
./include/LightGBM/utils/common.h:53:26: note: expanded from macro '_mm_malloc'
   53 | #define _mm_malloc(a, b) malloc(a)
      |                          ^
/usr/include/stdlib.h:540:14: note: previous declaration is here
  540 | extern void *malloc (size_t __size) __THROW __attribute_malloc__

(build link)
full log (click me)
clang++-18 -stdlib=libc++ -std=gnu++17 -I"/opt/R/devel/lib/R/include" -DNDEBUG -I./include -DEIGEN_MPL2_ONLY -DEIGEN_DONT_PARALLELIZE -DUSE_SOCKET -DLGB_R_BUILD  -I/usr/local/include   -fopenmp -pthread -fpic  -O3 -Wall -pedantic -frtti -Wp,-D_FORTIFY_SOURCE=3  -c treelearner/tree_learner.cpp -o treelearner/tree_learner.o
In file included from treelearner/linear_tree_learner.cpp:7:
In file included from ./include/Eigen/Dense:1:
In file included from ./include/Eigen/Core:22:
In file included from ./include/Eigen/src/Core/util/ConfigureVectorization.h:346:
In file included from /usr/lib/llvm-18/lib/clang/18/include/emmintrin.h:17:
In file included from /usr/lib/llvm-18/lib/clang/18/include/xmmintrin.h:31:
/usr/lib/llvm-18/lib/clang/18/include/mm_malloc.h:32:40: error: 'alloc_align' attribute parameter 1 is out of bounds
   32 |                                        __alloc_align__(2)))
      |                                        ^               ~
/usr/lib/llvm-18/lib/clang/18/include/mm_malloc.h:33:1: error: static declaration of 'malloc' follows non-static declaration
   33 | _mm_malloc(size_t __size, size_t __align) {
      | ^
./include/LightGBM/utils/common.h:53:26: note: expanded from macro '_mm_malloc'
   53 | #define _mm_malloc(a, b) malloc(a)
      |                          ^
/usr/include/stdlib.h:540:14: note: previous declaration is here
  540 | extern void *malloc (size_t __size) __THROW __attribute_malloc__
      |              ^
In file included from treelearner/linear_tree_learner.cpp:7:
In file included from ./include/Eigen/Dense:1:
In file included from ./include/Eigen/Core:22:
In file included from ./include/Eigen/src/Core/util/ConfigureVectorization.h:346:
In file included from /usr/lib/llvm-18/lib/clang/18/include/emmintrin.h:17:
In file included from /usr/lib/llvm-18/lib/clang/18/include/xmmintrin.h:31:
/usr/lib/llvm-18/lib/clang/18/include/mm_malloc.h:34:7: error: use of undeclared identifier '__align'; did you mean '__asin'?
   34 |   if (__align == 1) {
      |       ^
/usr/include/x86_64-linux-gnu/bits/mathcalls.h:55:1: note: '__asin' declared here
   55 | __MATHCALL_VEC (asin,, (_Mdouble_ __x));
      | ^
/usr/include/math.h:280:3: note: expanded from macro '__MATHCALL_VEC'
  280 |   __MATHCALL (function, suffix, args)
      |   ^
/usr/include/math.h:287:3: note: expanded from macro '__MATHCALL'
  287 |   __MATHDECL (_Mdouble_,function,suffix, args)
      |   ^
/usr/include/math.h:290:22: note: expanded from macro '__MATHDECL'
  290 |   __MATHDECL_1(type, __CONCAT(__,function),suffix, args)
      |                      ^
/usr/include/x86_64-linux-gnu/sys/cdefs.h:124:23: note: expanded from macro '__CONCAT'
  124 | #define __CONCAT(x,y)   x ## y
      |                         ^
<scratch space>:125:1: note: expanded from here
  125 | __asin
      | ^
In file included from treelearner/linear_tree_learner.cpp:7:
In file included from ./include/Eigen/Dense:1:
In file included from ./include/Eigen/Core:22:
In file included from ./include/Eigen/src/Core/util/ConfigureVectorization.h:346:
In file included from /usr/lib/llvm-18/lib/clang/18/include/emmintrin.h:17:
In file included from /usr/lib/llvm-18/lib/clang/18/include/xmmintrin.h:31:
/usr/lib/llvm-18/lib/clang/18/include/mm_malloc.h:34:15: error: comparison between pointer and integer ('double (*)(double) noexcept(true)' and 'int')
   34 |   if (__align == 1) {
      |       ~~~~~~~ ^  ~
/usr/lib/llvm-18/lib/clang/18/include/mm_malloc.h:38:9: error: use of undeclared identifier '__align'; did you mean '__asin'?
   38 |   if (!(__align & (__align - 1)) && __align < sizeof(void *))
      |         ^
/usr/include/x86_64-linux-gnu/bits/mathcalls.h:55:1: note: '__asin' declared here
   55 | __MATHCALL_VEC (asin,, (_Mdouble_ __x));
      | ^
/usr/include/math.h:280:3: note: expanded from macro '__MATHCALL_VEC'
  280 |   __MATHCALL (function, suffix, args)
      |   ^
/usr/include/math.h:287:3: note: expanded from macro '__MATHCALL'
  287 |   __MATHDECL (_Mdouble_,function,suffix, args)
      |   ^
/usr/include/math.h:290:22: note: expanded from macro '__MATHDECL'
  290 |   __MATHDECL_1(type, __CONCAT(__,function),suffix, args)
      |                      ^
/usr/include/x86_64-linux-gnu/sys/cdefs.h:124:23: note: expanded from macro '__CONCAT'
  124 | #define __CONCAT(x,y)   x ## y
      |                         ^
<scratch space>:125:1: note: expanded from here
  125 | __asin
      | ^
In file included from treelearner/linear_tree_learner.cpp:7:
In file included from ./include/Eigen/Dense:1:
In file included from ./include/Eigen/Core:22:
In file included from ./include/Eigen/src/Core/util/ConfigureVectorization.h:346:
In file included from /usr/lib/llvm-18/lib/clang/18/include/emmintrin.h:17:
In file included from /usr/lib/llvm-18/lib/clang/18/include/xmmintrin.h:31:
/usr/lib/llvm-18/lib/clang/18/include/mm_malloc.h:38:20: error: use of undeclared identifier '__align'; did you mean '__asin'?
   38 |   if (!(__align & (__align - 1)) && __align < sizeof(void *))
      |                    ^
/usr/include/x86_64-linux-gnu/bits/mathcalls.h:55:1: note: '__asin' declared here
   55 | __MATHCALL_VEC (asin,, (_Mdouble_ __x));
      | ^
/usr/include/math.h:280:3: note: expanded from macro '__MATHCALL_VEC'
  280 |   __MATHCALL (function, suffix, args)
      |   ^
/usr/include/math.h:287:3: note: expanded from macro '__MATHCALL'
  287 |   __MATHDECL (_Mdouble_,function,suffix, args)
      |   ^
/usr/include/math.h:290:22: note: expanded from macro '__MATHDECL'
  290 |   __MATHDECL_1(type, __CONCAT(__,function),suffix, args)
      |                      ^
/usr/include/x86_64-linux-gnu/sys/cdefs.h:124:23: note: expanded from macro '__CONCAT'
  124 | #define __CONCAT(x,y)   x ## y
      |                         ^
<scratch space>:125:1: note: expanded from here
  125 | __asin
      | ^
In file included from treelearner/linear_tree_learner.cpp:7:
In file included from ./include/Eigen/Dense:1:
In file included from ./include/Eigen/Core:22:
In file included from ./include/Eigen/src/Core/util/ConfigureVectorization.h:346:
In file included from /usr/lib/llvm-18/lib/clang/18/include/emmintrin.h:17:
In file included from /usr/lib/llvm-18/lib/clang/18/include/xmmintrin.h:31:
/usr/lib/llvm-18/lib/clang/18/include/mm_malloc.h:38:28: error: arithmetic on a pointer to the function type 'double (double) noexcept(true)'
   38 |   if (!(__align & (__align - 1)) && __align < sizeof(void *))
      |                    ~~~~~~~ ^
/usr/lib/llvm-18/lib/clang/18/include/mm_malloc.h:38:37: error: use of undeclared identifier '__align'
   38 |   if (!(__align & (__align - 1)) && __align < sizeof(void *))
      |                                     ^
/usr/lib/llvm-18/lib/clang/18/include/mm_malloc.h:39:5: error: use of undeclared identifier '__align'
   39 |     __align = sizeof(void *);
      |     ^
/usr/lib/llvm-18/lib/clang/18/include/mm_malloc.h:47:41: error: use of undeclared identifier '__align'
   47 |   if (posix_memalign(&__mallocedMemory, __align, __size))
      |                                         ^
/usr/lib/llvm-18/lib/clang/18/include/mm_malloc.h:55:1: error: static declaration of 'free' follows non-static declaration
   55 | _mm_free(void *__p)
      | ^
./include/LightGBM/utils/common.h:54:21: note: expanded from macro '_mm_free'
   54 | #define _mm_free(a) free(a)
      |                     ^
/usr/include/stdlib.h:555:13: note: previous declaration is here
  555 | extern void free (void *__ptr) __THROW;
      |             ^
clang++-18 -stdlib=libc++ -std=gnu++17 -I"/opt/R/devel/lib/R/include" -DNDEBUG -I./include -DEIGEN_MPL2_ONLY -DEIGEN_DONT_PARALLELIZE -DUSE_SOCKET -DLGB_R_BUILD  -I/usr/local/include   -fopenmp -pthread -fpic  -O3 -Wall -pedantic -frtti -Wp,-D_FORTIFY_SOURCE=3  -c treelearner/voting_parallel_tree_learner.cpp -o treelearner/voting_parallel_tree_learner.o
11 errors generated.
make: *** [/opt/R/devel/lib/R/etc/Makeconf:204: treelearner/linear_tree_learner.o] Error 1
make: *** Waiting for unfinished jobs....
ERROR: compilation failed for package ‘lightgbm’
* removing ‘/tmp/Rtmp4131Uu/Rinst320155bc02f4/lightgbm’
      -----------------------------------
ERROR: package installation failed

The root cause appears to be this from further up in the logs.
** using staged installation
checking location of R... /opt/R/devel/lib/R
checking whether MM_PREFETCH works... ./conftest: error while loading shared libraries: libc++.so.1: cannot open shared object file: No such file or directory
no
checking whether MM_MALLOC works... ./conftest: error while loading shared libraries: libc++.so.1: cannot open shared object file: No such file or directory
no
configure: creating ./config.status
config.status: creating src/Makevars

Reproducible example
This can be reproduced with docker.
docker run \
    --rm \
    --env MAKEFLAGS=-j4 \
    --platform linux/amd64 \
    -v $(pwd):/opt/LightGBM \
    -w /opt/LightGBM \
    -it ghcr.io/r-hub/containers/clang18:latest \
    bash

sh build-cran-package.sh --no-build-vignettes

Rscript -e "install.packages(c('R6', 'data.table', 'jsonlite'), repos = 'https://cran.r-project.org')"
R CMD INSTALL ./lightgbm_<IP_ADDRESS>.tar.gz

Environment info
LightGBM version or commit hash: https://github.com/microsoft/LightGBM/commit/f8ec57b8eba69b7371324bba1d158f850802c782
Additional Comments
N/A

I do see one copy of libstdc++.so.1.
find / -name 'libc++.so.1'
# /usr/lib/llvm-18/lib/libc++.so.1

And it looks like clang++-18 is a symlink to that location.
which clang++-18
# /usr/bin/clang++-18

stat /usr/bin/clang++-18

  File: /usr/bin/clang++-18 -> ../lib/llvm-18/bin/clang++
  Size: 26              Blocks: 0          IO Block: 4096   symbolic link
Device: 65h/101d        Inode: 1428380     Links: 1
Access: (0777/lrwxrwxrwx)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2024-07-14 19:13:14.000000000 +0000
Modify: 2024-07-14 19:13:14.000000000 +0000
Change: 2024-07-18 01:22:36.113571002 +0000
 Birth: 2024-07-18 01:22:36.113571002 +0000

Helping the linker find that library resolves the issues.
LD_LIBRARY_PATH="/usr/lib/llvm-18/lib:${LD_LIBRARY_PATH}" \
R CMD INSTALL ./lightgbm_<IP_ADDRESS>.tar.gz

But that really shouldn't be necessary (and isn't in any of the other clang{nn} images from r-hub). I'll put up a PR here to temporarily resolve it and unblock CI, and report this in the repo where the images are built.

upstream report: https://github.com/r-hub/containers/issues/70
PR to unblock CI: #6554


connect to PowerBI.com

Hi,
it is not mentioned if there is a way to connect PowerBI.com to this data lake ?
Br,
Gill

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a344a5de-68fa-e9cf-28eb-51269c33b9b3
Version Independent ID: 1b3ede62-3954-574b-5778-8cdee0ededfe
Content: Make Entity store available as a Data Lake
Content Source: articles/fin-ops-core/dev-itpro/data-entities/entity-store-data-lake.md
Service: dynamics-ax-platform
Product: ****
Technology: ****
GitHub Login: @MilindaV2
Microsoft Alias: milindav

Created bug 415932 to track this issue.

We have added more documentation.


Rework a couple of benchmarks to work with both Python2 and Python3

Python3 doesn't support implicit tuple deconstruction in arguments as Python2 used to.  So this just changes the function to access tuple components directly.

@swift-ci Please smoke test


steam: game dev tycoon doesn't work

Issue description
Game Dev Tycoon fails to start. This is the error message:
./gamedevtycoon64-bin: error while loading shared libraries: libX11.so.6: cannot open shared object file: No such file or directory

Steps to reproduce
Install steam, start Game Dev Tycoon.
Technical details

system: "x86_64-linux"
host os: Linux 4.9.71, NixOS, 17.09.git.cae4047 (Hummingbird)

Incidentally, I do have Game Dev Tycoon. I'll check why it might not run.

Thank you. I tried that:
$ git diff -U10
diff --git a/pkgs/games/steam/runtime-wrapped.nix b/pkgs/games/steam/runtime-wrapped.nix
index 73c3ccf6375..4a8e88e939f 100644
--- a/pkgs/games/steam/runtime-wrapped.nix
+++ b/pkgs/games/steam/runtime-wrapped.nix
@@ -8,20 +8,21 @@ assert !(nativeOnly && runtimeOnly);
 let
   runtimePkgs = with pkgs; [
     # Required
     glib
     gtk2
     bzip2
     zlib
     gdk_pixbuf

     # Without these it silently fails
+    xlibs.libX11
     xlibs.libXinerama
     xlibs.libXdamage
     xlibs.libXcursor
     xlibs.libXrender
     xlibs.libXScrnSaver
     xlibs.libXxf86vm
     xlibs.libXi
     xlibs.libSM
     xlibs.libICE
     gnome2.GConf

But it didn't help.

An another issue with current Steam approach. Recent nixpkgs libva update brought new major version in library name i.e. libva.so.2 instead of libva.so.1, but games still use libva.so.1 and this is also what Steam lands. While Saints Row 2 game which depends on libva.so.1 works when launched from Steam itself (I believe that since Steam adds /usr/lib etc to library prefix), if fails to find that library when launched from steam-run.

Recent nixpkgs got libva library updated from version 1.7.3 to version 2.0.0 [...]

This doesn't seem to be some systematic issue with the way we package Steam.
I think major version bumps that point to the same attribute should be made very carefully, but unfortunately, almost every time something breaks.
I don't think that libva is included in Steam runtime, but it's rather common for games to rely on packages outside of Steam runtime.

Not sure when this was fixed precisely, but I'm able to launch this fine with an nvidia card


New Templating of the training material to use only the website

Hi,
To help users of the training material and improve their training experience, I worked on formatting the training material to be mainly based on the website, and not on tutorial rendered GitHub (a bit disturbing with all the buttons when you are not familiar with GitHub). You can have a look at http://bebatut.fr/training-material/ to give you an idea of the new format.
The templating of the tutorial is changed to help highlighting some useful parts (hands-on, questions, ...). I worked on RNA-Seq tutorial as a draft of this: http://bebatut.fr/training-material//RNA-Seq/tutorials/ref_based. Behind it is really similar to previous templates with only markdown for the content. Some metadata and some layouts were just added to wrap the tutorials and make them "beautiful" in a website.
I also changed the slide format to use Remark.js and only markdown to make the slides: http://bebatut.fr/training-material/RNA-Seq/slides/#1
I worked with Jekyll as templating system. I defined different layouts (main page, topic page, tutorial page and slides). I also added several metadata using yaml around the tutorials and the topics to limit the redundancy and help the upkeep. And when we will deploy these materials to a website as the new Galaxy website, it will be easier :)
To help you as contributors, I tried to explain everything in the CONTRIBUTING.md. The structure of the GitHub repository did not really change. Some directories were added for Jekyll. But the structure of the directories of the topics did not change, only a file index.md were added. The metadata for each topic is defined in a YAML file in data directory.  You can have a look  to my fork to explore the changes: https://github.com/bebatut/training-material
What do you think about this new template?
Bérénice

In this PR there are two things and maybe we can split the discussions and reviews into two distinct directions.
First is the content, the new template and the refreshed Guidelines - I think this is a great improvement and will make things easier for trainers and trainees. The biggest point is probably the removal of the reveal.js slides and sticking to markdown for everything - this was discussed during the hackathon multiple times and I think is a nice way forward.
Second and as a direct consequence of the first is the generation of a website that serves the slides and the content to users via a nice looking website. This is more technical and will probably change again in the near future. We are thinking of using the same mechanism as the new Galaxy Hub and align with this style and build-system. So jekyll will eventually go away. We discussed this already with @dannon.
I guess at this point it is important to say, that what ever the build system will look like, we want to concentrate more on the content and the first part outlined by @bebatut in this PR - the new template.

will make some time to look at this in more detail soon, but looks great @bebatut! love the way the tutorials look on the website :)

@shiltemann Sure. It is still a WIP...

What do you think about this new template?

It looks very nice! 👏

:tada:

awesome \o/


Update request: abuse 0.8 → 0.9.1

Package name: abuse
Latest released version: 0.9.1 (https://github.com/Xenoveritas/abuse)

Current version on the unstable channel: 0.8
Current version on the stable/release channel: 0.8

[x] Checked the nixpkgs pull requests

Notify maintainers @iblech

Note for maintainers: Please tag this issue in your PR.

Add a :+1: reaction to issues you find important.

Thank you for pinging me! I prepared a draft commit. But I cannot fully test it as I'm currently at a machine without sound. Can you test whether everything works as expected, including gfx effects and music? You can do so with the following incantation:
nix-shell -I nixpkgs=https://github.com/iblech/nixpkgs/archive/patch-abuse-0.9.1.tar.gz -p abuse

Yes, works great!


Consuming Deep Links from various origins

LW should be able to consume the deep links, no matter their origin (Firebase or otherwise), given that they adhere to the standard 'https://joinseeds.com/?placeholder=&inviteMnemonic=' (maybe placeholder is not needed here)
So, the firebase lookup should be optional, which I'm not sure if it is now.
Longer conversation here https://discord.com/channels/722537361480613950/722920209551196211/923500312038375474

Assign to @JGDoh for triage

@JGDoh current status of this?

@JGDoh current status of this?

.


fix: Edit insight page disbled button style

Description

Insight edit page disabled button style fixed

Related Tickets & Documents

Fixes  #3099

Mobile & Desktop Screenshots/Recordings
BEFORE :

AFTER :

Steps to QA

Tier (staff will fill in)

[ ] Tier 1
[ ] Tier 2
[ ] Tier 3
[ ] Tier 4

[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?

This was fixed on this PR. https://github.com/open-sauced/app/pull/3092
The UI got an update @Lalithkumarponnambalam. thanks for the contribution, but I will unfortunately need to close it since the New UI is already live on beta.app.opensauced.pizza. The site will get updated in the next release.


Qwen's zero-shot evaluation results vary greatly from the Qwen technical report.

Hello, I conducted an evaluation of Qwen-7B using the latest code, but the results of the evaluation show a significant discrepancy from those in Qwen's technical report, as detailed in the figure below. Is this result to be expected?

Hi, I’ll look into this. Have you gotten any results on 3-shot BBH or on MMLU as well?

Hi, I’ll look into this. Have you gotten any results on 3-shot BBH or on MMLU as well?

I have only tested 5-shot MMLU on Qwen-7B, and the result I obtained is 56.87, whereas the technical report for Qwen cites 58.2.

Unfortunately, Qwen does not seem to provide their prompts or eval code for ARC, as best as I could tell: https://github.com/QwenLM/Qwen/tree/main/eval
so it's difficult to say why the scores differ. If they used a task description (e.g. "Answer the following questions:") this often significantly boosts zero-shot performance.
I'm able to fairly closely match LAMBADA accuracy with Qwen-1.8B here.


Pure Dart support

I just played around with the current state and noticed that the generator imports Flutter packages, specifically path_provider and flutter even though my project doesn't depend on isar_flutter.
Is pure Dart support planned? That's one of the great things about Hive that I would like to see continued here if possible.

@cachapa It is possible to use Isar with Dart only. The unit tests do that for example.
The isar_flutter package contains the binaries of isar_core. But you can also provide them yourself. I'll document how to do that 👍

@cachapa It is possible to use Isar with Dart only. The unit tests do that for example.
The isar_flutter package contains the binaries of isar_core. But you can also provide them yourself. I'll document how to do that 👍

Ok thanks. I did see the unit tests but was confused because the generator in my dart-only project generated those flutter dependencies.

Ok thanks. I did see the unit tests but was confused because the generator in my dart-only project generated those flutter dependencies.

The generator has a flutter option. Add this to your build.yaml to disable it:
targets:
  $default:
    builders:
      isar_generator|generator:
        options:
          flutter: false

Example: https://github.com/isar/isar/blob/main/isar/build.yaml

The generator has a flutter option. Add this to your build.yaml to disable it:
targets:
  $default:
    builders:
      isar_generator|generator:
        options:
          flutter: false

Example: https://github.com/isar/isar/blob/main/isar/build.yaml

Glad I found this. I was looking for a pure dart version too.

Okay... I got the .so files github location. Looks like we don't have linux binaries? I anyways tried the android ones and got read errors.
https://github.com/isar/isar-core/releases/download/0.1.9/libisar_android_arm64.so
https://github.com/isar/isar-core/releases/download/0.1.9/libisar_android_x64.so

Got the following errors on trying the x64 one
Invalid argument(s): Failed to load dynamic library 'libisar.so': /usr/lib/x86_64-linux-gnu/libc.so: invalid ELF header
Unhandled exception:
IsarError: Could not initialize IsarCore library. If you create a Flutter app, make sure to add isar_flutter_libs to your dependencies. Isar does not support 32-bit processors so make sure that your device / emulator has a 64-bit processor.

How to go about for Ubuntu?

Never mind. Got the linux .so from the tests. It's working fine for me now.
binary: https://github.com/isar/isar-core/releases/download/0.1.9/libisar_linux_x64.so

Thanks to @srix55 the docs are updated and this issue can be closed

Docs seem to be gone?
For those interested here's how I run Isar in pure Dart:
void main() async {
  withIsar((isar) async {
     // isar is ready here
  });
}

where withIsar is defined below:
withIsar(Function(Isar isar) fn) async {
  Isar? _isar;
  try {
    await Isar.initializeIsarCore( // or Isar.initializeLibraries if using 2.5.x
      libraries: {
        // download and define library for your platform
        if (Platform.isMacOS)
          Abi.macosX64: File('path/to/libisar.dylib').absolute.path,
      },
    );
    final path = Directory.systemTemp.createTempSync().path;
    print('[isar] opening in $path');
    _isar = await Isar.open(
        directory: path, schemas: [...]);
    fn(_isar);
  } catch (e, s) {
    print('[isar] $e $s');
  } finally {
    final closed = await _isar?.close(deleteFromDisk: true);
    print('[isar] closed');
    exit((closed ?? false) ? 0 : 255);
  }
}

As I said here there is easier way now.
Just initialize isar at the beginning of the program with the command
await Isar.initializeIsarCore(download: true)


Shareable and reusable volumes

The ability to:

Reuse a volume across runs
Share a volume across machines

Hello, I am highly interested by this feature!
How do you imagine this feature to be implemented?
I'd love to contribute to this one if I have enough context to do it.

👋  @courentin We are actually designing this. Ideally it should be an easy way to declare the volumes in the provider and you can add it into the runner or machine. Let me coma back with the specs if you are willing to help.

Share a volume across machines

As stated in https://github.com/iterative/cml/issues/561#issuecomment-871019350, [block] volumes can't be shared across machines; that's what block-based and file-based storage systems are for. As long as the shared storage has the same lifecycle as the machine, it could be managed from cml-runner so they're created and destroyed together.

Reuse a volume across runs

This would be a valid use case for [block] volumes, but the lifecycle of volumes should be managed in a different way. If they were being destroyed along with machines, it would be impossible to reuse them across runs, so users would need and additional, manual tool to create and destroy volumes as part of the projects' infrastructure.

Share a volume across machines [and] reuse [the same] volume across runs

That's the purpose of https://github.com/iterative/cml/issues/561, and official Terraform providers already support all the listed solutions.

Some inspiration from a related tool: spotty has some very useful and configurable EBS Deletion policies.

Closed with #237. We don't support shared block storage (it's impossible) nor persistent block storage (it's not portable), but instead we use object storage that's both shared and persistent, at the cost of performance.

Is there any documentation on how the object storage is set up in iterative_task? Can I define my own volumes/mount points/etc and/or write directly to object storage outside of the iterative_task directory sync feature?
Also, when we say that the object storage in iterative_task is shared, does that mean it is shared within a single instance of iterative_task, meaning that subsequent restarted versions of the task due to spot instance behavior share one "object storage" resource?
Or  does that mean that it can be shared across multiple/all instances of iterative_task, meaning that if I create two different main.tf files and start two task runners in parallel, I could provide some s3 bucket URL and access the same "object storage" from both tasks? (note that I'm not talking about defining two iterative_task resources within the same main.tf config)


chore: update repo by service bot

This is a routine update from cc-service-bot based on the service.yml in your repo. This PR
should be approved and merged as soon as CI passes.

CHANGELOG
FILE NAME - CHANGED BY - COMMIT MESSAGE
.semaphore/semaphore.yml - framework - chore: update repo semaphore config
sonar-project.properties - framework - chore: update sonar-project.properties to reconfigure sonarqube scanning.


ENYO-2913: Add queued index support.

Issue
As an alternative solution to https://github.com/enyojs/enyo/pull/1343, the issue involves consecutive calls to change the index of the panels, such as sequential calls to animateTo that occur as part of application flow programmatically, and are not the result of direct user interaction (which already had guards in place for). This will allow for support of the existing app logic, in the cases where multiple, sequential calls to animateTo are desired, and the results of the last call are expected to be applied.
Fix
We have implemented queued index support, such that any number of calls to animateTo will all eventually be processed, ending with the results of the last call. There is a known issue with mixing sequential calls to animateTo with calls to set('index'), as we do not have any kind of checks for the generic setter. We could override the generic set and provide some support here, but this seemed like a fairly unnecessary use case to support. That being said, I am open to adding this to fully flesh out this solution, but am omitting it for the time being.
Enyo-DCO-1.1-Signed-off-by: Aaron Tam<EMAIL_ADDRESS>

I've ran into similar situations a few times with various components, including a component with very panels-like behavior. It seems to me the main choice to make here is whether an index change should always precede the animation, or whether the animation should always precede the index change.
Personally, I tend to prefer the index is set synchronously, preceding the animation. This seems to be the most sensible solution, because the index is often used for purposes other than animation alone. Animations can then be applied as a reaction to the changed index.
Once this is the case, there are multiple strategies that could be used to handle the animations for quickly changing indexes:

Fire only one animation at a time, evaluating the need for an additional transition at the end of each animation. (a throttled approach)
Update the transition endpoint of each panel mid-animation to reflect the current index (can lead to many animating panels at once and cause performance issues).
Create a secondary throttled index next to the synchronous index and use this throttled index to trigger animations (this approach has worked really well for me and seems conceptually similar to the queued index changes in this pull request).

I don't know if any of this conflicts with LG's internal usage of LightPanels, but I noticed two separate pull requests dealing with this same issue and thought I'd put in my 2ct.

Taking the simpler solution in #1343 for the time being to maintain consistency with the current behavior of next() and previous()


Ubuntu_22.04 Crashed after not having enough disk space pop-up

Windows Version
Microsoft Windows [Version 10.0.22621.1344]
WSL Version
<IP_ADDRESS>
Are you using WSL 1 or WSL 2?

[X] WSL 2
[ ] WSL 1

Kernel Version

Distro Version
Ubuntu 22.04
Other Software
No response
Repro Steps
While I'm downloading some large data from the distro, I don't realize the disk is full until I got the Not enough disk space pop-up from the windows.  After that my WSL Terminal is terminated.
After cleaning up the large files from my windows, the WSL Distro is able to launch, but my files are gone,

I forgot what steps I've done but
I ended up with this error now

The operation timed out because a response was not received from the virtual machine or container.
Error code: Wsl/Service/CreateInstance/HCS_E_CONNECTION_TIMEOUT

Expected Behavior
After cleaning up the large files and having the empty space, the WSL should not be affected
Actual Behavior
WSL Files gone
Diagnostic Logs
WslLogs-2023-03-14_19-55-53.zip

Thanks for reporting this @WillyRL .
Looking at the logs, the issue is that the distribution disk is corrupted: [ 2376.105139] EXT4-fs (sdd): VFS: Can't find ext4 filesystem
Unfortunately, without the list of the command you ran in the distribution it's not possible to root cause how exactly the disk got corrupted.
Closing since the issue is a corrupted distribution vhd.


auto remote state

Read a directory of terraform code, find the remote state references and update depends_on in fogg.yml with them.
This code is very rough but working for the happy paths. I till do a full parse of code in a terraform directory (in a fogg-managed repo) and extract all the references to data.terraform_remote_state.foo. Those will then be used to update depends_on configurations in fogg.yml. It is expected that the user would then run fogg apply to update.
Test Plan
I've tested this manually on a few repos and components, working to do some more.
References

Codecov Report

Merging #498 into main will decrease coverage by 0.18%.
The diff coverage is 53.48%.

@@            Coverage Diff             @@
##             main     #498      +/-   ##
==========================================
- Coverage   57.94%   57.76%   -0.19%
==========================================
  Files          19       20       +1
  Lines        1750     1778      +28
==========================================
+ Hits         1014     1027      +13
- Misses        580      596      +16
+ Partials      156      155       -1

Impacted Files
Coverage Δ

config/v2/config.go
7.58% <0.00%> (-0.45%)
:arrow_down:

config/v2/resolvers.go
49.54% <0.00%> (-0.93%)
:arrow_down:

config/v2/validation.go
74.73% <ø> (ø)

init/init.go
0.00% <0.00%> (-21.06%)
:arrow_down:

util/strings.go
0.00% <0.00%> (ø)

plan/plan.go
85.14% <92.00%> (+0.28%)
:arrow_up:

Continue to review full report at Codecov.

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


'No best common type exists among return expressions.' in function that returns either "new Promise" or "Promise.reject"

In my JS project I have a few functions that look like this:
function doSomethingAsync(options) {
    if (!options.someCondition) {
        return Promise.reject('You are missing something');
    }

    return new Promise((resolve, reject) => {
        // do something async and then resolve or reject
    });
}

This causes every single line inside this function to be underlined in red (which is visually kind of distracting, especially if a function has 50+ lines). I think it would be best to just underline the return statements, instead of every line.
I can workaround this by moving the if condition inside the function body of the promise, but I'm wondering if this is really a valid error? I guess the problem here is that the return type of Promise.reject is Promise<void> while new Promise returns Promise<{}> (according to IntelliSense).
I figured that this error is coming from TypeScript and not VS Code, but I thought I'd still post it here.

Maybe this TypeScript issue is related: https://github.com/Microsoft/TypeScript/issues/2241

Duplicate of #230


Update Core Install - Symphony

JIRA issue created by: rcook
Originally opened: 2012-07-09 03:03 PM
There is some Millennium and Dummy stuff http://code.google.com/p/xcncip2toolkit/wiki/CoreInstallation .
The “Millennium example here” needs to be replaced with actual, working Millennium examples. Also Symphony & Voyager examples should be added.

JIRA User: msuranofsky
JIRA Timestamp: 2012-07-26 11:41 AM
Randy -- I have added example xml for Symphony.


chore(main): release 0.0.9

:robot: I have created a release beep boop
0.0.9 (2024-12-30)
Bug Fixes

issues preventing dev from working on linux (157b414)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.0.9
:sunflower:


New attribute chi_class to allow a user defined CHI subclass

Allow a user defined CHI subclass to be used.

I am very sorry - I have no idea why I missed that PR! I checked my GH settings and I definitely should've been alerted ... I am very sorry.
The PR looks good and the feature is reasonable - I adopted it!
Thank you very much!!