Add PSSFP

@anatoleabe Please clarify what is the organization. If it is a college or a school, please provide us with:

the school official website URL
the school street address, including city and country
an URL of a page on the official website where the school offers an IT-related long-term (>1 year) course
a proof, which shows that the school recognizes the domain you are submitting as an official email domain for the students.

If the organization is neither a college, nor a university, but rather a public initiative, municipality training program, or similar institution, it is most probably not eligible for being added to the list of known educational institutions in this repository. In that case, please apply for free educational license with an official document which proves that you are a student. You can do it using "OFFICIAL DOCUMENT" tab at https://www.jetbrains.com/shop/eform/students.
I have to close the request without merging.
Thank you for the understanding!

@anatoleabe You might miss my previous comment. Please react.

@anatoleabe I am sorry, this request remains unanswered for a while. I have to close it without merging. Please reopen and comment if you have an update regarding the aforementioned issue. Thank you for your understanding!


Engine crash during unconstrained layout

import 'package:flutter/material.dart';

void main() {
  runApp(MaterialApp(
    title: 'Crasher',
    home: Scaffold(
      body: SafeArea(
        child: Crasher(),
      ),
    ),
  ));
}

class Crasher extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    Widget child = ListWheelScrollView(
      itemExtent: 20,
      onSelectedItemChanged: (int index) {},
      children: <Widget>[
        Text('item'),
      ],
    );

    return Material(
      child: FittedBox(
        child: Center(
          child: child,
        ),
      ),
    );
  }
}

Running this yields the following crash in the engine:
F/flutter (13463): [FATAL:flutter/flow/layers/transform_layer.cc(28)] Check failed: transform_.isFinite().
F/libc    (13463): Fatal signal 6 (SIGABRT), code -6 in tid 13480 (1.gpu)
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

Looks like this was introduced in https://github.com/flutter/engine/pull/8585

This rolled into the framework in https://github.com/flutter/flutter/pull/31179, which translates to version 1.5.2

When we fix, please add a test that would have caught this.

I did a flutter run and got the following error message:
I/flutter (10811): ══╡ EXCEPTION CAUGHT BY RENDERING LIBRARY ╞═════════════════════════════════════════════════════════
I/flutter (10811): The following assertion was thrown during performResize():
I/flutter (10811): RenderListWheelViewport object was given an infinite size during layout.
I/flutter (10811): This probably means that it is a render object that tries to be as big as possible, but it was put
I/flutter (10811): inside another render object that allows its children to pick their own size.
I/flutter (10811): The nearest ancestor providing an unbounded width constraint is:
I/flutter (10811):   RenderFittedBox#429fb relayoutBoundary=up4 NEEDS-LAYOUT NEEDS-PAINT
I/flutter (10811):   creator: FittedBox ← DefaultTextStyle ← AnimatedDefaultTextStyle ← _InkFeatures-[GlobalKey#659ed
I/flutter (10811):   ink renderer] ← NotificationListener<LayoutChangedNotification> ← PhysicalModel ←
I/flutter (10811):   AnimatedPhysicalModel ← Material ← Crasher ← MediaQuery ← Padding ← SafeArea ← ⋯
I/flutter (10811):   parentData: <none> (can use size)
I/flutter (10811):   constraints: BoxConstraints(0.0<=w<=360.0, 0.0<=h<=568.0)
I/flutter (10811):   size: MISSING
I/flutter (10811):   fit: contain
I/flutter (10811):   alignment: center
I/flutter (10811):   textDirection: ltr
I/flutter (10811): The nearest ancestor providing an unbounded height constraint is:
I/flutter (10811):   RenderFittedBox#429fb relayoutBoundary=up4 NEEDS-LAYOUT NEEDS-PAINT
I/flutter (10811):   creator: FittedBox ← DefaultTextStyle ← AnimatedDefaultTextStyle ← _InkFeatures-[GlobalKey#659ed
I/flutter (10811):   ink renderer] ← NotificationListener<LayoutChangedNotification> ← PhysicalModel ←
I/flutter (10811):   AnimatedPhysicalModel ← Material ← Crasher ← MediaQuery ← Padding ← SafeArea ← ⋯
I/flutter (10811):   parentData: <none> (can use size)
I/flutter (10811):   constraints: BoxConstraints(0.0<=w<=360.0, 0.0<=h<=568.0)
I/flutter (10811):   size: MISSING
I/flutter (10811):   fit: contain
I/flutter (10811):   alignment: center
I/flutter (10811):   textDirection: ltr
I/flutter (10811): The constraints that applied to the RenderListWheelViewport were:
I/flutter (10811):   BoxConstraints(unconstrained)
I/flutter (10811): The exact size it was given was:
I/flutter (10811):   Size(Infinity, Infinity)
I/flutter (10811): See https://flutter.io/layout/ for more information.
I/flutter (10811):
I/flutter (10811): When the exception was thrown, this was the stack:
I/flutter (10811): #0      RenderBox.debugAssertDoesMeetConstraints.<anonymous closure> (package:flutter/src/rendering/box.dart:1749:9)
I/flutter (10811): #1      RenderBox.debugAssertDoesMeetConstraints (package:flutter/src/rendering/box.dart:1823:6)
I/flutter (10811): #2      RenderBox.size=.<anonymous closure> (package:flutter/src/rendering/box.dart:1543:17)
I/flutter (10811): #3      RenderBox.size= (package:flutter/src/rendering/box.dart:1543:65)
I/flutter (10811): #4      RenderListWheelViewport.performResize (package:flutter/src/rendering/list_wheel_viewport.dart:558:5)
I/flutter (10811): #5      RenderObject.layout (package:flutter/src/rendering/object.dart:1617:9)
I/flutter (10811): #6      _RenderProxyBox&RenderBox&RenderObjectWithChildMixin&RenderProxyBoxMixin.performLayout (package:flutter/src/rendering/proxy_box.dart:105:13)
I/flutter (10811): #7      RenderObject.layout (package:flutter/src/rendering/object.dart:1632:7)
I/flutter (10811): #8      _RenderProxyBox&RenderBox&RenderObjectWithChildMixin&RenderProxyBoxMixin.performLayout (package:flutter/src/rendering/proxy_box.dart:105:13)
I/flutter (10811): #9      RenderObject.layout (package:flutter/src/rendering/object.dart:1632:7)
I/flutter (10811): #10     _RenderProxyBox&RenderBox&RenderObjectWithChildMixin&RenderProxyBoxMixin.performLayout (package:flutter/src/rendering/proxy_box.dart:105:13)
...

During flutter run --profile and flutter run --release, I got
I/flutter (11396): ══╡ EXCEPTION CAUGHT BY RENDERING LIBRARY ╞═════════════════════════════════════════════════════════
I/flutter (11396): The following UnsupportedError was thrown during performLayout():
I/flutter (11396): Unsupported operation: Infinity or NaN toInt
I/flutter (11396):
I/flutter (11396): When the exception was thrown, this was the stack:
I/flutter (11396): #0      _Double.toInt (dart:core/runtime/lib/double.dart:183)
I/flutter (11396): #1      _Double.floor (dart:core/runtime/lib/double.dart:152)
I/flutter (11396): #2      RenderListWheelViewport.scrollOffsetToIndex (package:flutter/src/rendering/list_wheel_viewport.dart:356)
I/flutter (11396): #3      RenderListWheelViewport.performLayout (package:flutter/src/rendering/list_wheel_viewport.dart:630)
I/flutter (11396): #4      RenderObject.layout (package:flutter/src/rendering/object.dart:1632)
I/flutter (11396): #5      _RenderProxyBox&RenderBox&RenderObjectWithChildMixin&RenderProxyBoxMixin.performLayout (package:flutter/src/rendering/proxy_box.dart:105)
I/flutter (11396): #6      RenderObject.layout (package:flutter/src/rendering/object.dart:1632)
I/flutter (11396): #7      _RenderProxyBox&RenderBox&RenderObjectWithChildMixin&RenderProxyBoxMixin.performLayout (package:flutter/src/rendering/proxy_box.dart:105)
I/flutter (11396): #8      RenderObject.layout (package:flutter/src/rendering/object.dart:1632)
I/flutter (11396): #9      _RenderProxyBox&RenderBox&RenderObjectWithChildMixin&RenderProxyBoxMixin.performLayout (package:flutter/src/rendering/proxy_box.dart:105)
I/flutter (11396): #10     RenderObject.layout (package:flutter/src/rendering/object.dart:1632)
I/flutter (11396): #11     _RenderProxyBox&RenderBox&RenderObjectWithChildMixin&RenderProxyBoxMixin.performLayout (package:flutter/src/rendering/proxy_box.dart:105)
I/flutter (11396): #12     RenderObject.layout (package:flutter/src/rendering/object.dart:1632)
I/flutter (11396): #13     _RenderProxyBox&RenderBox&RenderObjectWithChildMixin&RenderProxyBoxMixin.performLayout (package:flutter/src/rendering/proxy_box.dart:105)
I/flutter (11396): #14     RenderObject.layout (package:flutter/src/rendering/object.dart:1632)
I/flutter (11396): #15     _RenderProxyBox&RenderBox&RenderObjectWithChildMixin&RenderProxyBoxMixin.performLayout (package:flutter/src/rendering/proxy_box.dart:105)
I/flutter (11396): #16     RenderObject.layout (package:flutter/src/rendering/object.dart:1632)
I/flutter (11396): #17     _RenderProxyBox&RenderBox&RenderObjectWithChildMixin&RenderProxyBoxMixin.performLayout (package:flutter/src/rendering/proxy_box.dart:105)
I/flutter (11396): #18     RenderObject.layout (package:flutter/src/rendering/object.dart:1632)
I/flutter (11396): #19     _RenderProxyBox&RenderBox&RenderObjectWithChildMixin&RenderProxyBoxMixin.performLayout (package:flutter/src/rendering/proxy_box.dart:105)
I/flutter (11396): #20     RenderObject.layout (package:flutter/src/rendering/object.dart:1632)
I/flutter (11396): #21     RenderPositionedBox.performLayout (package:flutter/src/rendering/shifted_box.dart:385)
I/flutter (11396): #22     RenderObject.layout (package:flutter/src/rendering/object.dart:1632)
I/flutter (11396): #23     RenderFittedBox.performLayout (package:flutter/src/rendering/proxy_box.dart:2287)
I/flutter (11396): #24     RenderObject.layout (package:flutter/src/rendering/object.dart:1632)
I/flutter (11396): #25     _RenderProxyBox&RenderBox&RenderObjectWithChildMixin&RenderProxyBoxMixin.performLayout (package:flutter/src/rendering/proxy_box.dart:105)
...

CC @xster (the author of list_wheel_scroll_view.dart according to git blame)

Oh, I was on an older version of Flutter. When I checked out the tip of tree, I got
F/flutter (11573): [FATAL:flutter/flow/layers/transform_layer.cc(28)] Check failed: transform_.isFinite().
F/libc    (11573): Fatal signal 6 (SIGABRT), code -6 in tid 11590 (1.gpu)

fwiw, the code should result in an exception - just not an engine crash 😄

Ah, the older version doesn't have the engine FML_CHECK yet. Once I comment the FML_CHECK, I got the exact same exception in https://github.com/flutter/flutter/issues/31650#issuecomment-487123842
According to https://github.com/flutter/flutter/issues/31650#issuecomment-487128158, I think we have two options here:

In the framework, check the matrix when it's sent from the framework to the engine, and throw an exception there.
Lower FML_CHECK to FML_DCHECK so it would only crash engine in unopt engine build.

@chinmaygarde and I discussed option 2 when we first implemented the check, and we decided that a bad/corrupted matrix should have a crash in all builds instead of just unopt builds.

I'm ok with option 1, but shouldn't we be hitting the assertion in https://github.com/flutter/flutter/issues/31650#issuecomment-487123842 before we send the matrix to the engine anyway?

BTW, I pinpointed the location where the NaN is generated: https://github.com/flutter/flutter/compare/master...liyuqian:check_transform_matrix#diff-f41d041ddd3fe665cc9e123f992bb5e0R2277

App crashing in release
flutter: ══╡ EXCEPTION CAUGHT BY SCHEDULER LIBRARY ╞═════════════════════════════════════════════════════════
flutter: The following assertion was thrown during a scheduler callback:
flutter: Offset argument contained a NaN value.
flutter: 'dart:ui/painting.dart': Failed assertion: line 38: '<optimized out>'
flutter:
flutter: Either the assertion indicates an error in the framework itself, or we should provide substantially
flutter: more information in this error message to help you determine and fix the underlying cause.
flutter: In either case, please report this assertion by filing a bug on GitHub:
flutter:   https://github.com/flutter/flutter/issues/new?template=BUG.md
flutter:
flutter: When the exception was thrown, this was the stack:
flutter: #2      _offsetIsValid (dart:ui/painting.dart:38:10)
flutter: #3      Path.contains (dart:ui/painting.dart:2090:12)
flutter: #4      ClipPathLayer.find (package:flutter/src/rendering/layer.dart:1137:19)
flutter: #5      ContainerLayer.find (package:flutter/src/rendering/layer.dart:616:36)
flutter: #6      OffsetLayer.find (package:flutter/src/rendering/layer.dart:846:18)
flutter: #7      TransformLayer.find (package:flutter/src/rendering/layer.dart:1218:18)
flutter: #8      ContainerLayer.find (package:flutter/src/rendering/layer.dart:616:36)
flutter: #9      ClipPathLayer.find (package:flutter/src/rendering/layer.dart:1139:18)
flutter: #10     ContainerLayer.find (package:flutter/src/rendering/layer.dart:616:36)
flutter: #11     PhysicalModelLayer.find (package:flutter/src/rendering/layer.dart:1515:18)
flutter: #12     ContainerLayer.find (package:flutter/src/rendering/layer.dart:616:36)
flutter: #13     OffsetLayer.find (package:flutter/src/rendering/layer.dart:846:18)
flutter: #14     ContainerLayer.find (package:flutter/src/rendering/layer.dart:616:36)
flutter: #15     OffsetLayer.find (package:flutter/src/rendering/layer.dart:846:18)
flutter: #16     ContainerLayer.find (package:flutter/src/rendering/layer.dart:616:36)
flutter: #17     PhysicalModelLayer.find (package:flutter/src/rendering/layer.dart:1515:18)
flutter: #18     ContainerLayer.find (package:flutter/src/rendering/layer.dart:616:36)
flutter: #19     OffsetLayer.find (package:flutter/src/rendering/layer.dart:846:18)
flutter: #20     ContainerLayer.find (package:flutter/src/rendering/layer.dart:616:36)
flutter: #21     OffsetLayer.find (package:flutter/src/rendering/layer.dart:846:18)
flutter: #22     ContainerLayer.find (package:flutter/src/rendering/layer.dart:616:36)
flutter: #23     OffsetLayer.find (package:flutter/src/rendering/layer.dart:846:18)
flutter: #24     TransformLayer.find (package:flutter/src/rendering/layer.dart:1218:18)
flutter: #25     RenderView._updateSystemChrome (package:flutter/src/rendering/view.dart:218:58)
flutter: #26     RenderView.compositeFrame (package:flutter/src/rendering/view.dart:201:9)
flutter: #27     _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding&PaintingBinding&SemanticsBinding&RendererBinding.drawFrame (package:flutter/src/rendering/binding.dart:350:16)
flutter: #28     _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding&PaintingBinding&SemanticsBinding&RendererBinding&WidgetsBinding.drawFrame (package:flutter/src/widgets/binding.dart:701:13)
flutter: #29     _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding&PaintingBinding&SemanticsBinding&RendererBinding._handlePersistentFrameCallback (package:flutter/src/rendering/binding.dart:286:5)
flutter: #30     _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1012:15)
flutter: #31     _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:952:9)
flutter: #32     _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding._handleDrawFrame (package:flutter/src/scheduler/binding.dart:864:5)
flutter: #36     _invoke (dart:ui/hooks.dart:219:10)
flutter: #37     _drawFrame (dart:ui/hooks.dart:178:3)
flutter: (elided 5 frames from class _AssertionError and package dart:async)
flutter: ════════════════════════════════════════════════════════════════════════════════════════════════════

@rajeshzmoke your crash seems to be different from the issue that we're tracking here (_offsetIsValid instead of Check failed: transform_.isFinite()). Can you please create a new issue with instructions on how to reproduce the crash? (A single-file minimal Flutter app that reproduces the crash would be the best.)

@liyuqian  Check failed: transform_.isFinite()  does come when in release mode.. the error i've posted is in debug build

@rajeshzmoke I see. Do you have some code that can reproduce the crash? That would tremendously help us debug the issue.

@tvolkert any definitive solution to this problem?

To our knowledge, the issue (or at least the code path in which it was originally reported) has been fixed by adding asserts in the framework (so real errors are still reported, but they don't get all the way to the engine and cause the app to crash).
@C-Aniruddh and @rajeshzmoke if you're still seeing this and have a small case in which it reliably reproduces, we'd love to take a look!

@tvolkert should I pick these commits and rebuild flutter or they've been merged into the main branch? If I have to rebuild the engine manually, is there any specific guide for the compilation process?

They've all been merged into master at this point, so you shouldn't have to build a local engine.

@C-Aniruddh : btw, https://github.com/flutter/engine/commit/f1d821d8fde79569f801cb9c902c2e9d45b46fb6 is replacing FML_CHECK with FML_DCHECK so it won't crash the engine in release just in case that the framework doesn't catch the invalid matrix.


Rename is_bit_clear to bit_is_clear, is_bit_set to bit_is_set

Ugh, I know we just merged #109 but after using it for a couple of days I think it really should have been bit_is_set() rather than is_bit_set(). I'm happy with set_bit() and clear_bit() though, they seem natural:
usart3.cr3.dmat().set_bit();
while usart3.isr().tc().bit_is_clear() {}

if usart3.isr().ore().bit_is_set() {
    ...
}

As an added bonus, this way around we don't have to reserve the bit_set/bit_clear variant names, because it will no longer clash.
What do you think?

LGTM.

we don't have to reserve the bit_set/bit_clear variant names

👍
@whitequark Any opinion on this PR?

@japaric No objection

@homunkulus r+

:pushpin: Commit 718645c has been approved by japaric

:hourglass: Testing commit 718645c with merge 718645c...

:sunny: Test successful - status-appveyor, status-travis
Approved by: japaric
Pushing 718645cfb253cce7728c09fcf456c3da990b4444 to master...


installation challenges with coffeescript

I had to do the following to get specific versions of coffee-script and coffee-jshint installed globally before I could proceed:
sudo npm install<EMAIL_ADDRESS><EMAIL_ADDRESS>-g
Consider perhaps upgrading these to newer stable versions in hubot-slack?
Even as such, I still get errors:
npm ERR! peerinvalid The package<EMAIL_ADDRESS> does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants coffee-script@>= 1.6 <= 1.8.0`

Finally, got it to install via:
sudo npm install -g hubot<EMAIL_ADDRESS><EMAIL_ADDRESS>yo generator-hubot

I had to do the following to get specific versions of coffee-script and coffee-jshint installed globally before I could proceed:

What were you doing specifically, ie were you generating a bot, or just running it? What was happening before getting the specific versions?
That said, I'm not sure if this is necessarily a problem with hubot-slack. It only has one (direct) dependency: slack-client. It'd  probably be better to file it with http://github.com/github/hubot with that info if you don't mind.

Closing as off-topic.


Temporal.Now.plainDateISO() & plainTimeISO throw undefined timezone

Reproduction Steps:
Try to call Temporal.Now.plainDateISO().
Expected Results:
According to https://tc39.es/proposal-temporal/docs/plaindate.html , it should give a PlainDate.
Actual Results:
Uncaught RangeError: Invalid time zone: undefined
    at ParseTemporalTimeZoneString (file:///home/rektide/src/week-of-year/node_modules/@js-temporal/polyfill/dist/index.esm.js:2794:11)
    at ParseTemporalTimeZone (file:///home/rektide/src/week-of-year/node_modules/@js-temporal/polyfill/dist/index.esm.js:2582:35)
    at SystemTimeZone (file:///home/rektide/src/week-of-year/node_modules/@js-temporal/polyfill/dist/index.esm.js:5965:33)
    at timeZone (file:///home/rektide/src/week-of-year/node_modules/@js-temporal/polyfill/dist/index.esm.js:7975:12)
    at Temporal.Now.plainDateISO (file:///home/rektide/src/week-of-year/node_modules/@js-temporal/polyfill/dist/index.esm.js:7968:46)

Tested on Node v16.14.0.
Workaround
Explicitly specify a timezone name: Temporal.Now.PlainDateISO('GMT'). This will return a PlainDate.

I think you meant to link this part of the docs. https://tc39.es/proposal-temporal/docs/now.html#plainDateISO

This looks like an environment-specific problem, because it doesn't repro locally for me nor does it cause test failures (locally or in CI) for this test: https://github.com/js-temporal/temporal-polyfill/blob/2f6e6b43267113a213d08b70be8ea72e8075aa1a/test/now.mjs#L92-L96
Could you share the command line args that you're using to launch Node?
To dig into the most likely reason for the failures you're seeing in your environment, look at SystemTimeZone function https://github.com/js-temporal/temporal-polyfill/blob/2f6e6b43267113a213d08b70be8ea72e8075aa1a/lib/ecmascript.ts#L5245-L5249
Stripping all the Temporal-specific code away, the core of that function is this:
new Intl.DateTimeFormat('en-us').resolvedOptions().timeZone

Could you try running the line of code above in your environment (but without this polyfill loaded) and let us know what the result is?  If it's undefined, then the problem doesn't seem to be Temporal-related. Any API that uses Intl to get the system time zone will also fail. You should investigate why your environment has an undefined system time zone.
However, if it's not undefined, then try this code:
import { Intl } from '@js-temporal/polyfill';
new Intl.DateTimeFormat('en-us').resolvedOptions().timeZone

This is the same as the first code except it's using the Intl.DateTimeFormat polyfill. If the first code snippet returned a non-undefined value but the polyfilled one returns an undefined, then it may be a bug in the Intl portion of this polyfill.
If both code snippets return a not-undefined value, then it may be a polyfill bug although we'd need to investigate more to find out why.

I was on a new-ish system & had not set a timezone via timedatectl set-timezone. Things started working ok when I set a timezone.
I'm ok with things as they are. There's a debatable possible merit to defaulting to UTC & not crashing, but I'm past this & have left this linger a while already. Thank you for the really good in depth debugging help all; apologies and thanks.

There's a debatable possible merit to defaulting to UTC & not crashing

This seems reasonable since the only case where I could imagine a timezone not existing would be custom-built servers. Consumer PCs and phones would always have a time zone.
But this isn't a Temporal-specific thing so I don't know whether that solution would be a good one or not. You may want to file an issue in the Intl spec repo (https://github.com/tc39/ecma402) where the experts can discuss the merits.


Update image ghcr.io/zoriya/kyoo_transcoder to 8f81446

This PR contains the following updates:

Package
Update
Change

ghcr.io/zoriya/kyoo_transcoder
digest
d81bceb -> 8f81446

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.


Use inline source maps, closes #180

There are 2 ways to solve the source maps issue #180:

Copy the .ts files from src to dist folder
Which kinda is against the point of having the dist folder separation at all
Inline the sources in the sourcemaps
Which this PR suggests

Checked against the current Angular CLI webpack output.

Closing as previously resolved


Automated cherry pick of #9529: fix(taskman): use admin token if task userCred token expired

Cherry pick of #9529 on release/3.3.
#9529: fix(taskman): use admin token if task userCred token expired

Codecov Report

Merging #9533 (6767b62) into release/3.3 (9a6c26d) will decrease coverage by 2.71%.
The diff coverage is 0.29%.

@@              Coverage Diff               @@
##           release/3.3   #9533      +/-   ##
==============================================
- Coverage         6.78%   4.07%   -2.72%
==============================================
  Files              676     281     -395
  Lines           118955   59502   -59453
==============================================
- Hits              8076    2424    -5652
+ Misses          110267   56887   -53380
+ Partials           612     191     -421

Flag
Coverage Δ

aFlag
4.07% <0.29%> (-2.72%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/cloudcommon/notifyclient/notify.go
2.22% <0.00%> (-0.36%)
:arrow_down:

pkg/compute/models/buckets.go
1.10% <0.00%> (-0.07%)
:arrow_down:

pkg/compute/models/capabilities.go
0.00% <0.00%> (ø)

pkg/compute/models/cloudproviderregions.go
0.00% <0.00%> (-0.27%)
:arrow_down:

pkg/compute/models/cloudproviders.go
0.87% <0.00%> (+0.01%)
:arrow_up:

pkg/compute/models/cloudregions.go
1.54% <0.00%> (-0.09%)
:arrow_down:

pkg/compute/models/cloudsync.go
0.00% <0.00%> (ø)

pkg/compute/models/dbinstance_accounts.go
2.05% <0.00%> (-0.03%)
:arrow_down:

pkg/compute/models/dbinstance_backups.go
2.78% <0.00%> (-0.17%)
:arrow_down:

pkg/compute/models/dbinstance_databases.go
3.33% <0.00%> (-0.07%)
:arrow_down:

... and 709 more

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 ebe40ec...6767b62. Read the comment docs.


libicu not detected on openSuse Tumbleweed

I am unable to install 'Visual Studio Live Share' openSuse Tumbleweed because installer fails to detect libicu which is already installed.
$ sudo zypper se --provides libicu
Loading repository data...
Reading installed packages...

S  | Name                  | Summary                               | Type
---+-----------------------+---------------------------------------+--------
   | libicu-devel          | Development files for the ICU library | package
   | libicu-devel-32bit    | Development files for the ICU library | package
   | libicu-doc            | Documentation for the ICU library     | package
i+ | libicu-suse64_2       | International Components for Unicode  | package
   | libicu-suse64_2-32bit | International Components for Unicode  | package
   | libicu64_2-bedata     | Rule databases and tables for ICU     | package
i+ | libicu64_2-ledata     | Rule databases and tables for ICU     | package

Version: 1.40.0-insider
Commit: 515f496d9a7617caf07f38298f610920f60834d6
Date: 2019-11-05T14:32:00.229Z
Electron: 6.1.2
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Linux x64 5.3.7-1-default

Hey @rajinder-yadav thanks for reporting this. @legomushroom is this a Linux dependency issue?

We’ve made improvements in this area since this issue was filed (i.e. the vsls-agent process and associated Linux dependencies have been removed). We believe this may have improved your experience and are closing this issue. If this issue still persists for you, please comment on the issue and let us know. Thank you.


Start with Wil Taylor's setup and make it my own

Add github theme
Remove blameline
Remove filetree
Switch Wil Taylor to wamberg
Remove startify
Remove indentline
Remove dap
Remove vimagit
Remove cursorword
Add vim-css-color
Add vim-tmux-navigator

Sorry for the noise! I didn't pay attention closely enough to the dropdowns in my PR. This was meant to be a PR to my fork.
Thank you so much for sharing your videos and source code :bow:

No worries :)


Usability testing Jaws (screen reader)

Test the Conditional Logic screens in Windows Jaws. Is it usable? Anything obviously broke?

Keynav initial testing

Tabs can navigate up-down keys (but not left-right). CAN activate tab w/space/enter
Question Tree nav not working. Probably from computer lag. (try again later)


sfu-ws: Error when SetLocalDescription

Hi, i'm running sfu-ws example and have this error when second user is connecting:
InvalidModificationError: invalid proposed signaling state transition: have-local-offer->SetLocal(offer)->have-local-offer

It happens here:
https://github.com/pion/example-webrtc-applications/blob/811ebe7b8ae1e1ef1a338fb80e7c0610635e6737/sfu-ws/main.go#L162

Found my answer in #pion slack channel. So the error means that I haven’t finished last round of negotiation - this makes sense because calls to setLocal and setRemote are concurrent


1 Exposure on App - when does the counting begin?

Not sure if this is the right place to ask, but I have a question concerning the Coronaapp in Germany.
Since Saturday I have one exposure that is still rated as “low risk” (green mode) which I understand was my phone being not too near and not too long next to someone who was tested positive.
Let’s imagine I met this person on July 1st. That person got themselves tested on 5th of July, got the result on July 7th and checked in on the App as “positive” the same day. Does the App show me the “1 exposure status” for 14 days after the person checked in positive on the App (July 7th) or does the App count from the day on I was near that person (July 1st) -  meaning the status ends for me on July 15th?
Let’s exaggerate this so you guys understand my question:
I met person A on July 1st, the person feels sick 8 days after, gets the positive result on July 12. That means I get the status “1 exposure” for only 3 days, right?

As far as I've understood the documentation only the temporary exposure keys of the last 14 days are stored and analysed by the app. Hence, the status should end on July 15th in your first example, if July 1st was the only exposure to this person.

As far as I've understood the documentation only the temporary exposure keys of the last 14 days are stored and analysed by the app. Hence, the status should end on July 15th in your first example, if July 1st was the only exposure to this person.

Thank you for your reply, that is actually what I thought!
But that also means if you get the “1 exposure” notification on July 15th and it’s gone three days after, that I can name the exact date I saw the “positive” person (in this example 4th). Is that right?

As far as I understood the App would say which day you had the encounter when warning the first time:
https://github.com/corona-warn-app/cwa-app-android/blob/b2d00d076d94773b929e8125f4828f2f31df7ed0/Corona-Warn-App/src/main/res/values-de/strings.xml#L309

As far as I understood the App would say which day you had the encounter when warning:
https://github.com/corona-warn-app/cwa-app-android/blob/b2d00d076d94773b929e8125f4828f2f31df7ed0/Corona-Warn-App/src/main/res/values-de/strings.xml#L309

Ok ok, this is WAY too complicated for me 😕
Is there a way I can check on that inside the App or maybe inside the Exposure-Checks.
The only thing I can see is that since saturday I have one matched count but where can I check when that encounter with that matched key was?

The only thing I can see is that since saturday I have one matched count but where can I check when that encounter with that matched key was?

With the current app, you can't.
There's an enhancement request that would cover this: https://github.com/corona-warn-app/cwa-wishlist/issues/100

Dear @TeRe20200,
thanks to @mh- and @jensjensenjens your question has already been answered. Please follow up in https://github.com/corona-warn-app/cwa-wishlist/issues/100 (vote, comment...) for that feature request.
Mit freundlichen Grüßen/Best regards,
SW
Corona Warn-App Open Source Team


ScalaMtags computes the wrong symbol for members defined in package objects

Repro: start VSCode extension as documented in https://github.com/scalameta/language-server/blob/master/CONTRIBUTING.md.
Try jumping to Either, e.g. in
case class User(name: String, age: Int, x: Either[String, Int])

Result: jumping to Either doesn't work, while jumping to Int does.

Fixed in #105


Configuration are lost after upgrade

Hi,
I have upgraded the plugin from 1.7.1 to 3.0.0 and all SaltAPI configuration are lost.
Please advise.
Thanks!
Ido

Any update?

Yep.  While on the plane I started on this in the compat branch

Thank you for your update.

Is it possible to prevent this issue?
is it possible to restore the jobs after they have deleted?

The compat branch will hopefully correct this issue
Jobs aren't actually deleted. The issue is that the format of the salt plugin was adjusted, and after the plugin update, Jenkins is no longer able to read the old format. The saltstack instructions are still in jobs/jobname/config.xml, it's just not being read in by Jenkins. This will hopefully be corrected soon.

Ok, When do you think that you will release a fix?

This is now working, but with a necessary manual step.
Please try the beta release from:
https://github.com/jenkinsci/saltstack-plugin/releases/tag/v3.1.0-beta2
As mentioned on the release notes:
Due to human error, there is a manual step necessary to fully import pre 2.0 build configs. If the Jenkins migrate old data page at administrativeMonitor/OldData/manage shows the error ConversionException: Cannot construct com.waytta.clientinterface.BasicClient then delete the <clientInterface> line from the config. This can be done with:
sed -i'.bak' '/<clientInterface>.*<\/clientInterface>/d' jenkinshome/jobs/jobname/config.xml
At this point reloading configs should restore the job data.
The rest of the old job config import, combined with improved support for long running pipeline jobs should be in the 3.1 release.

This was corrected in release 3.1 (same as the mentioned beta above and still requires the manual step). Should be available on the mirrors in the next 24 hours.

Great! it's working!


Some more tests

Some tests for heliosynchronous.
Questions

Would it be a good option to check for the "unphysical" condition where a is less than the radius of Earth and if radius of perigee is less than radius of Earth), as stated in Vallado?
.
I think this exception would never be raised since this line ensures that and also given that the condition for alt < 0 is already checked in one of the above lines. Would it be a good choice to remove raising that exception?

Currently, if I try to create an orbit with a < radius of earth, then it doesn't give an error.
The test test_heliosynchronous_orbit_ecc fails, but I think it should have passed. That might need more investigation.

It seems the difference in expected eccentricities is of the order 1e-5 if I use these parameters:
expected_ecc = 0.2 * u.one
expected_inc = 98.6 * u.deg
expected_a = 7346.846 * u.km

instead of the current parameters (giving errors of the order 1e-2, which may not be negligible):
expected_ecc = 0.0 * u.one
expected_inc = 98.6 * u.deg
expected_a = 7178.1363 * u.km

It looks like the calculation is not accurate, or am I missing something?
Thanks!

Hi @Yash-10, we might consider doing something similar to from_classical, where the decorator @u.quantity_input is applied and the value of a is checked to be positive. However, its size is never compared with current attractor's radius.

Bear in mind that creating an orbit with a semi-major axis less than the radius of the planet is totally valid. It just means that, if the object is approaching the attractor, it will impact at some point. But there could be:

Asteroids, comets, and artificial satellites about to impact
Rockets and missiles just launched from the Earth (and not circularized their orbits yet)

So I wouldn't add any further checks in from_classical.

It seems the differences arise due to the value of n_sunsync. Vallado uses 1.991063853e-7 whereas the value calculated in poliastro is 1.99098176e-7. Although the difference is small, the calculation of eccentricity might have a considerable impact:
_ecc_0 = np.sqrt(
      -3
      * R_SSO ** 2
      * J2_SSO
      * np.sqrt(k_SSO)
      * np.cos(inc)
      / (2 * a ** (7 / 2) * n_sunsync)
)
ecc = np.sqrt(1 - _ecc_0)

The failing test_heliosynchronous_orbit_ecc test uses an inclination of 98.6 degrees but to be precise, it is 98.60308111784582 degrees. If I change inc to 98.60308111784582 in the test, we get a floating point error since the ecc calculated is slightly lower than 0 (of the order 1e-5).
If I use 98.60308111784582 degrees in the test but using the n_sunsync value from Vallado (1.991063853e-7), I get the eccentricity 0.00025043, which, I think, is what is expected from the test.

Maybe we could pass the test by setting a higher atol since the n_sunsync value used in vallado is different and hence the result is expected to be different, or does the failing test have some bigger consequences?

Oh, very good investigation @Yash-10 ! I guess we can't help but increase the tolerance if Vallado uses a different value for the rotational speed. Let's fix the test, rebase, and merge 👍🏽

Codeclimate complained to shorten the condition:
if (a is None) and (ecc is None) and (inc is None):

So tried to change it to:
if all(coe is None for coe in [a, ecc, inc]):

but still doesn't fix it.

Meh, we are mostly ignoring Codeclimate. Perhaps we should either have more fine-grained custom roles, or just remove it.
I approved the changes in this PR.


ENH: interpolate: Add the "coord" attribution to get non-reduced Lagrange coefficients

Add the "coord" attribution to get non-reduced Lagrange coefficients.

Reference issue

To solve the issue #14681
What does this implement/fix?

Added the coord attribution to support complete Lagrange interpolation coefficients (the solution of the issue #14681)
Additional information

Usage:
import numpy as np
from scipy.interpolate import lagrange

x = np.array([0, 1, 2], dtype=float)
y = np.ones(3, dtype=float)
y *= 0.5
poly = lagrange(x, y)
# Check the reduced coefficients
print(f"Reduced coefficient: {poly.coeffs}")
# Check the complete coefficients
print(f"Complete coefficient: {poly.coord}")

Dear @nschloe @ev-br
To solve #14681, I wrote two implementation ways, The PR is the first way, and I will submitt the second implementation way later because I'm not sure which one you like. Please let me know if you don't like either of the both ways.

TBH, I prefer gh-14774.
Making it inherit from poly1d is elegant indeed. However I for one have no idea how np.poly1d behaves when subclassed (and not all numpy objects have well defined behavior when subclassed) --- this may very well be FUD, but I definitely am not looking forward for debugging it if something does go subtly wrong.

Let's close this in favor of gh-14774


nixos/tests/nginx: update test script

Description of changes
Update test script.
Fixed warning message:
nix build -f ./default.nix nixosTests.nginx
trace: warning: Module argument `nodes.webserver.config` is deprecated. Use `nodes.webserver` instead.

cc @SuperSandro2000
Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Not sure if this is related or not:
webserver: must succeed: curl -w '%{http_code}' --head --fail -H 'If-None-Match: "vw879gp4w2cx1z5lnhm6mvrc744g1xr9"' http://localhost/index.html
webserver #   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
webserver #                                  Dload  Upload   Total   Spent    Left  Speed
webserver #   0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
(finished: must succeed: curl -w '%{http_code}' --head --fail -H 'If-None-Match: "vw879gp4w2cx1z5lnhm6mvrc744g1xr9"' http://localhost/index.html, in 0.03 seconds)
Test "check ETag if serving Nix store paths" failed with error: ""
cleanup
kill machine (pid 8)

The error is not related to this PR I don't know how to fix it.
Usually on the local server the test is successful, it is difficult to determine the cause. Increasing the timeout does not fix the error.

subtest: check ETag if serving Nix store paths
webserver: must succeed: curl -v http://localhost/index.html 2>&1 | sed -n -e "s/^< etag: *//ip"
(finished: must succeed: curl -v http://localhost/index.html 2>&1 | sed -n -e "s/^< etag: *//ip", in 0.08 seconds)
webserver: must succeed: curl -w '%{http_code}' --head --fail -H 'If-None-Match: "vw879gp4w2cx1z5lnhm6mvrc744g1xr9"' http://localhost/index.html
webserver #   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
webserver #                                  Dload  Upload   Total   Spent    Left  Speed
webserver #   0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
(finished: must succeed: curl -w '%{http_code}' --head --fail -H 'If-None-Match: "vw879gp4w2cx1z5lnhm6mvrc744g1xr9"' http://localhost/index.html, in 0.05 seconds)
webserver: must succeed: /nix/store/gy620si66nhs7aw05mzqnp4xr9j215vq-nixos-system-webserver-23.05.git.05d711a1fe9/specialisation/etagSystem/bin/switch-to-configuration test >&2


python3Packages.numba: disable for python < 3.6

Motivation for this change
builder for '/nix/store/y3c1y8z9p262pmc2zica46nfal22m5aa-python2.7-numba-0.48.0.drv' failed with exit code 1; last 10 log lines:
  no configure script, doing nothing
  building
  Executing setuptoolsBuildPhase
  Traceback (most recent call last):
    File "nix_run_setup", line 8, in <module>
      exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\\r\\n', '\\n'), __file__, 'exec'))
    File "setup.py", line 305
      build_requires = [f'numpy >={min_numpy_build_version}']
                                                           ^
  SyntaxError: invalid syntax

Things done

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

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

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

will you backport?

sure


[Discussion] Upgrade rustc to 1.20.0 + future upgrade requirements.

There has been discussions over IRC, and I'd like to move the discussion here for easier access.
History
Historically, we've stuck with rustc 1.14.0 because it was the min over the versions packaged in Debian stable on all architectures.
Delta
Currently, Debian stable has packaged rustc 1.24.1 for all architectures.
Proposal

Upgrade our rustc version assumption to 1.20.0 (release notes) now, so that we get associated constants. This will allow us to simplify a lot of our interfaces.
Determine a checklist of requirements for future proposals to upgrade rustc.

@real-or-random afaik bootstrapping rustc has to begin with 1.19 or earlier versions because that's the latest version supported by mrustc. Every version increase over that introduces one more step from there.

I didn't follow the discussion in IRC. Why is bootstrapping so much more secure?

@sgeisler Isn't that something  automatic, and that will have to be done eventually anyway? Also, does it even have to be repeated again?
I was under impression that once you do a bootstraping like this once, and then compile the compiler source code with the bootstrapped compiler bainary and then with the original compiler binary, and they produce the same output, you've prooven that the original compiler at a given checksum does not contain any backdoors, and can be used from on as a starting point. Sorry if I'm terribly mistaken here. :)
Seems like GUIX team just went to 1.28.0: https://www.gnu.org/software/guix/blog/2018/bootstrapping-rust/

@real-or-random https://www.schneier.com/blog/archives/2006/01/countering_trus.html is my understanding.

I was under impression that once you do a bootstraping like this once, and then compile the compiler source code with the bootstrapped compiler binary and then with the original compiler binary, and they produce the same output, you've proven that the original compiler at a given checksum does not contain any backdoors, and can be used from now on as a starting point. Sorry if I'm terribly mistaken here. :)

I'm under the same impression.

The real thing that I want to discuss is how the whole process should look like. Without a deterministic build of the compiler, we need to trust someone to build the compiler. Who do we trust?
This might be less of a problem because we don't release binaries, so any malicious tampering would only cause discrepancies between the Travis test results.
My naive plan that's meant to draw constructive criticism:

I build 1.19.0, then 1.20.0
I upload the binaries somewhere
I modify travis to pull down the binaries instead of using its own rust compiler

@dpc You're right. But there are usually many complications in this process, and the original author of the diverse double compiling paper, when trying to demonstrate the process, even had to patch compilers.

Closed by https://github.com/rust-bitcoin/rust-bitcoin/pull/210


howdoi

Hi, this is awesome!
In particular, it should be useful for wifi hotspots where DNS works without login.
It would be cool to combine this with howdoi: https://pypi.org/project/howdoi/
By this I mean: query dig howdoi.format.date.bash @dns.toys, receive as response from the server (which replaced '.' with ' ', passed to howdoi) date +%Y-%m-%d

Hi @JohannesBuchner. howdoi looks quite cool. It looks like the responses can be arbitrarily long, multi-line, and formatted, which would make it unfit for DNS responses. If you're able to prototype and test this out, please do let me know.


raftstore: set term when catch up logs for merge

What is changed and how it works?
Prepare merge may includes logs from different terms, which may be even
larger than the term of a follower that is lag behind. So when catching
up logs by commit merge, its term should also be set to get a correct
metadata.
Close #11526.
Check List
Tests

Unit test
Integration test

Release note
Fix metadata corruption in an unlikely condition that prepare merge is triggered after new election without informing an isolated peer

/merge

/merge


prometheus-snmp-exporter: 0.11.0 -> 0.13.0

Motivation for this change
New features and a bugfix with the two recent releases.
Things done

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

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

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

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

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

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

Success on x86_64-linux (full log)
Attempted: prometheus-snmp-exporter
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/y0vk6xp9qans5limzsblaqp4m3n2rwb2-snmp_exporter-0.13.0-bin
shrinking /nix/store/y0vk6xp9qans5limzsblaqp4m3n2rwb2-snmp_exporter-0.13.0-bin/bin/snmp_exporter
shrinking /nix/store/y0vk6xp9qans5limzsblaqp4m3n2rwb2-snmp_exporter-0.13.0-bin/bin/generator
strip is /nix/store/h0lbngpv6ln56hjj59i6l77vxq25flbz-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/y0vk6xp9qans5limzsblaqp4m3n2rwb2-snmp_exporter-0.13.0-bin/bin
patching script interpreter paths in /nix/store/y0vk6xp9qans5limzsblaqp4m3n2rwb2-snmp_exporter-0.13.0-bin
checking for references to /build in /nix/store/y0vk6xp9qans5limzsblaqp4m3n2rwb2-snmp_exporter-0.13.0-bin...
strip is /nix/store/h0lbngpv6ln56hjj59i6l77vxq25flbz-binutils-2.30/bin/strip
/nix/store/y0vk6xp9qans5limzsblaqp4m3n2rwb2-snmp_exporter-0.13.0-bin

Success on aarch64-linux (full log)
Attempted: prometheus-snmp-exporter
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/0jkqbvn1a8rskdg2v605qr16w6q80lxp-snmp_exporter-0.13.0-bin
shrinking /nix/store/0jkqbvn1a8rskdg2v605qr16w6q80lxp-snmp_exporter-0.13.0-bin/bin/generator
shrinking /nix/store/0jkqbvn1a8rskdg2v605qr16w6q80lxp-snmp_exporter-0.13.0-bin/bin/snmp_exporter
strip is /nix/store/y4ymnvgxygpq05h03kyzbj572zmh6zla-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/0jkqbvn1a8rskdg2v605qr16w6q80lxp-snmp_exporter-0.13.0-bin/bin
patching script interpreter paths in /nix/store/0jkqbvn1a8rskdg2v605qr16w6q80lxp-snmp_exporter-0.13.0-bin
checking for references to /build in /nix/store/0jkqbvn1a8rskdg2v605qr16w6q80lxp-snmp_exporter-0.13.0-bin...
strip is /nix/store/y4ymnvgxygpq05h03kyzbj572zmh6zla-binutils-2.30/bin/strip
/nix/store/0jkqbvn1a8rskdg2v605qr16w6q80lxp-snmp_exporter-0.13.0-bin


Deployment guide feedback - replace PMSA with PSA

Section heading: ABI Timelines, Week 2. There is no specific role in AWS called as PMSA.
Documentation issue description: so Please replace it with PSA.
https://w.amazon.com/bin/view/AWSBuiltIn-Onboarding

Done.

Thanks


Add black formatting as a GitHub action

Created the action file to run only for Python 3.9 for now. Will do for all the rest after we make sure it works fine.


fixed to make TestHarness full runnable (on my machine)

To allow execution, added some missing pip dependencies plus README instruction to (re-)create the root folder logs folder (not tracked by repo)

Hi @maximusunc,
I've not played around with the TestHarness for awhile now, so I've sort of lost my bearings with respect to this PR. However, since I finally got my basic TranslatorSRI/graph-validation-tests package out the door over the weekend (7-Apr-24), this week, I'm now going to revisit the TestHarness to issue a PR suggesting how to integrate the new TestRunners. I'll revisit this PR and your feedback along the way.

I got a Windoze version of the code running by explicit importing of a mingw jq wheel built by a 3rd party. I've also implemented the other feedback above, in my current evolving "OneHopTest Integration" branch.  For these reasons,  I'm going to close this PR for this reason.


Skill Editor Hud too light on dark mode

You can't see the skill names

Where is that screen from?

Where is that screen from?

When you go in to an NPC and edit their skills, thats the window that opens

Should be fixed in one of the recent releases


Anaconda MKL blas libraries don't get loaded in Linux

The Anaconda MKL blas libraries don't get used on Linux. The problem seems to be the following line in util/linalg.py:
mkl_rt = ctypes.cdll.LoadLibrary(os.path.join(anaconda_path, 'DLLs', 'mkl_rt.dll'))
which, on my machine, and I'm guessing Linux in general, should be
mkl_rt = ctypes.cdll.LoadLibrary(os.path.join(anaconda_path, 'lib', 'libmkl_rt.so'))
I'm not sure what the best way to fix this is, but probably either check which system is being used or try loading both before throwing an exception.

@nfusi , would you mind taking a quick look? I suspect this code is dated.
James.

no longer an issue thanks to Dapid.


LXD Network Forward firewall rule generation is inefficient.

i tried dumping firewall rules and i found 3.4MB of rules.
On closer inspection , it is because   UDP port forward rule for a WebRTC video conf app we developing.
ports:
- description: ""
  protocol: udp
  listen_port: 443,3000-60000
  target_port: ""
  target_address: 10.xx.xxx.xx

it have over 50000 lines of
-A POSTROUTING -s 10.xx.xx.xx/32 -d 10.xx.xx.xx/32 -p udp -m udp --dport 4000 -m comment --comment "generated for LXD network-forward lxdbr1" -j MASQUERADE
.....
-A POSTROUTING -s 10.xx.xx.xx/32 -d 10.xx.xx.xx/32 -p udp -m udp --dport 60000 -m comment --comment "generated for LXD network-forward lxdbr1" -j MASQUERADE

Isn't it better to use  --match multiport --dports 4000:60000 ?

I need to check the source code, but if memory serves this is because this port definition effectively needs to create many 1:1 port mapping rules, rather than a many:1 port match which would use multiport.

Hey @markylaing did you confirm this was an issue?

Hey @markylaing did you confirm this was an issue?

Hey, no sorry not yet. Ubuntu 22.04 doesn't seem to be happy with using update-alternatives to force usage of legacy iptables. However I can see where the rules are generated and it isn't using the same optimisation as the NAT proxy. Will get to it first thing Monday.

This happens in ubuntu 22.04. but 20.04 is working perfectly!
In case of ubuntu 22.04, you need each time to do the following:
lxc stop v1
If you don't have ping in the lxc container/VM you need to flush your native system IPTABLE:
sudo su
for ipt in iptables iptables-legacy ip6tables ip6tables-legacy; do $ipt --flush; $ipt --flush -t nat; $ipt --delete-chain; $ipt --delete-chain -t nat; $ipt -P FORWARD ACCEPT; $ipt -P INPUT ACCEPT; $ipt -P OUTPUT ACCEPT; done
systemctl reload snap.lxd.daemon
sudo snap restart --reload lxd
exit
lxc start v1

@markylaing are you using the snap? If so update-alternatives won't work.
Instead you need to ensure that nft tables is clear and that there is at least one iptables rule added (by way of using update-alternatives so that iptables uses iptables-legacy) and then reload LXD so it uses iptables driver.
See
https://github.com/lxc/lxc-ci/blob/master/bin/test-lxd-network-bridge-firewall#L55-L59
https://github.com/lxc/lxc-ci/blob/master/bin/test-lxd-network-bridge-firewall#L177-L179

@markylaing are you using the snap? If so update-alternatives won't work.

@tomponline yep realised that this morning :laughing: too long spent on other projects...
I've confirmed this for both xtables and nftables drivers. Will work on a fix now.

@markylaing once you've confirmed the issue please can you add the bug label. Ta


[dif/entropy] Add header for entropy_src DIFs

I'm hoping to add an implementation + test as part of this PR once the header is at a design we're happy with.

@silvestrst and @mundaym in case you have some cycles to review this in the next few days. Thanks!

Hi @alphan!

SEED (for LFSR)
Added.

ERR_CODE
ERR_CODE_TEST
Ack. Will add this in a future commit.

CONF.BOOT_BYPASS_DISABLE (not sure if this is critical given that we can lock the registers but still...)
I am not sure if this is critical at runtime stage. My understanding is that the bypass is always needed at cold boot, not sure if there is a harm if leaving as is for warm boot. I will ask @mwbranstad so that he can clarify.

Hi @alphan!

SEED (for LFSR)

Added.

ERR_CODE
ERR_CODE_TEST

Ack. Will add this in a future commit.

CONF.BOOT_BYPASS_DISABLE (not sure if this is critical given that we can lock the registers but still...)

I am not sure if this is critical at runtime stage. My understanding is that the bypass is always needed at cold boot, not sure if there is a harm if leaving as is for warm boot. I will ask @mwbranstad so that he can clarify.

There is no harm per se, just a unnecessary delay will occur potentially. All endpoint requesters of entropy should be looking at the fips signal, which then ensures "no harm" in that they receive the proper level of entropy.

Thanks @alphan! The internal CI issue seems to be unrelated. Re-running CI now on the rebased chain.


Fix: fixed typo "every where" to "everywhere"

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thank you @babybuttons for your contribution.


[Haxe][ASGenerator][Bug] Fixed autoimport of types from its own module after execution 'Refactor -> Code Generator'. fixes #1767

Has conflicts.

fixed


HTTP Client DNS resolver override

Is there a way to override the dns resolver for requests made to blob storage?
If an Azure storage account has public access disabled and is only accessible via a private network, then we need to use a private DNS which there is no way to force it on the Azure SDK HTTP client.
Otherwise, there is a chance that the client uses a public DNS, and it will get an unauthorized response when obtaining blob data.

Hi @vasra-gh
Do you use the privatelink hostnames for your private network endpoints?
https://learn.microsoft.com/en-us/azure/private-link/private-endpoint-dns
I am thinking that another solution would be that if the provided url has the privatelink suffix that it should honor that.

Hi @vasra-gh
Do you use the privatelink hostnames for your private network endpoints?
https://learn.microsoft.com/en-us/azure/private-link/private-endpoint-dns
I am thinking that another solution would be that if the provided url has the privatelink suffix that it should honor that.

Hi @fawadasaurus, thanks for the reply
We have the DNS records registered within another part of the organization subscription that maintains the private DNS resolver. We simply ask to link the hostnames of the blob storage endpoint to a specific private endpoint.
Attempting to resolve the privatelink hostname with a public dns will just resolve to a public ip. Maybe I am missing something, but just adding the privatelink subdomain to the endpoint doesn't do anything in our case

Ok. This seems like a unique setup.
I believe that the intended setup is that the systems that are able to access the private endpoint will (by default) use a resolver that has the internal IP address for the resource.


Fix mangle.json config

Add a missing mangle prop in hooks, and remove a property config that overrode an existing one (__c used for _context overrode __c used for _constructor).

Coverage remained the same at 100.0% when pulling fb72763f00b122e05558dfd4b85d29615fa542c6 on fix-mangle-config into ed4de76051256f093ca6611c84495f94e68ef6df on master.


Permission denied com.android.providers.telephony.SmsProvider

I'm getting the following error:
Permission denied com.android.providers.telephony.SmsProvider
Please see the attached screenshot.

This error means the app has not been given access to read the messages of the device. You can manually give it permission via the settings > apps > permissions on your device or use a plugin to request permission from the user. You'll also need to make sure you have the correct imports in your manifest file too (these are outlined in the readme)


OpenVSP is not deterministic in spanwise distribution of parametric coordinates on blended wings.

Description
OpenVSP has a bug, where it can give two different spanwise parametric coordinate distributions on blended wings. The code seems to "lock" onto an execution path during initialization, and is consistent with design changes after initialization. However, we run multiple instances of OpenVSP on multiple procs, as a result, it is highly likely that the different instances running on different procs do not agree on the spanwise parametric coordinates. Even though the actual differences are small, this introduces very large errors when we do parallel finite-differencing. Currently, the code avoids this issue by doing the FD computations completely (base and perturbed) on the proc that perturbs the DV, instead of doing the base evaluation on the proc that owns the point, and the perturbed evaluation on the proc that perturbs the DV.
OpenVSP version of at least 3.21.1
I have a test script for this bug. I will check with all versions of OpenVSP and try to see if they ended up fixing it in a recent release. If not, I will contact the dev team (again) and point them towards the issue.

I vaguely recall this being brought to my attention many years ago -- but at the time, it could not be duplicated and there was no MWE that could demonstrate the bug.  I had essentially nothing to go on to chase this bug.
If you have a minimal test case that can replicate this issue on a recent version, I'm happy to spend some time trying to run this down.

Hi @ramcdona! Thanks for following up with this issue. This issue has been introducing minor errors in our derivatives; they were large enough for us to notice but small enough so that the students (including me) who needed to graduate did not try to address this issue directly.
Now that you followed up here, I dusted off my test that I created during the 2019 workshop, and then tested it with different OpenVSP versions. It actually looks like 3.27.1 actually fixed it! My heart tells me to just stick with version 4.1.22 but not sure if project managers would like that. Looks like 4.1.22 would have definitely fixed it for good.
Jokes aside, I can recreate the issue up to 3.26.1 on ubuntu-20 using gcc7.5 and python 3.7.7. With the same setup, I could not re-create the issue on 3.27.1 Looking at the extent of the changelog for 3.27, I am not too surprised that this is fixed. Also I did not even try 3.27.0 after seeing the changelog for 3.27.1.
I will follow up with you offline and get you the test I have. We can also use our public docker images to replicate the issue on older VSP versions and if you prefer, we can include this test going into the future. Once we are sure the issue is fixed, I can come back and close this issue and https://github.com/mdolab/pygeo/issues/70. Thanks again for following up!

You are correct, 3.27.1 only fixes a GUI issue and will be identical to 3.27.0 from the API.
Looking at the changes between 3.26.1 and 3.27, I don't really see anything that should have influenced this.  Most of the things that I thought might have helped should have been in 3.26.1.
I won't look a gift horse in the mouth -- but I also don't quite trust it.  Lets keep the test around for a while and I appreciate you sending me a test case if you can.
Just think with 4.1.22 you won't even need sensitivities or an optimizer to find the solution!

Has this been replicated on Pleiades, which uses TOSS4?
I've been having derivative issues with my MPhys model and I'm wondering if this is the source.
I using v3.33.0 of OpenVSP but have been unable to recreate the issue using test_2 as mentioned on #70 .

I have no idea if folks are running on Pleiades.
This original bug was reported before VSPAERO had an adjoint capability.  If you're using the adjoint capability, we can be pretty sure you're seeing something entirely different.
I suggest you start a new issue report and describe the problem you're seeing and the symptoms you have.  Is it a VSPAERO or OpenVSP thing, etc.
OpenVSP does not have any native derivative support.  However, all parameters are subject to a minimum perturbation.  Smaller than that, they don't actually force an update -- recalculation of the surface.

Hi @ramcdona ,
Thanks for your quick response. I'm not using VSPAERO, and I suspect that my issues maybe related to how DVGeo uses parallel FD to compute the derivatives of OpenVSP. On that note, what is the minimum perturbation used to force an update? Is this something that we can disable when calling OpenVSP from python?
I should have directed my comment regarding Pleiades to @anilyil , @lamkina , and @ArshSaja since I know that they have worked on similar applications of OpenVSP to CFD-based shape optimization.

I checked into the tolerance without an update -- it is set at DBL_EPSILON, so it really shouldn't be the problem.  I thought it was bigger, but I just checked and it has been DBL_EPSILON since 2.9.0 (the alpha version to 3.0.0) back in 2015 or so.
If you are using OpenVSP in parallel from the Python API, then there could be issues.  These are somewhat fundamental to the way Python is designed...
When Python loads a module, that module is loaded once in memory and is shared across anything running from that Python process.  So, when you import numpy in one *.py file, you are using the same numpy in some far away *.py file.
This works fine when the modules don't have any state.  When you ask numpy to invert a matrix, that matrix is stored on the Python side, it is transferred to numpy, inverted in Fortran code, and the result is transferred back to the Python code.
However, this is not how OpenVSP works.  Instead, OpenVSP maintains the state -- the airplane model is stored in memory on the OpenVSP / C++ side of the fence.  The model can be large, so this allows only small amounts of information to be passed back and forth to Python.  It also makes sense because OpenVSP was designed as an application first - not a library.
That said, imagine if NumPy kept the matrix in-memory.  You loaded a large matrix in one place -- and now all other places that have imported numpy are working on the same matrix.  Now your distant unrelated code is implicitly working on the same matrix -- unless you tell it to flush it and load another.  But now your earlier code path is working with this secondary matrix.  Chaos ensues.
We have a fix for this -- we designed the fix for a different use case (so it isn't tested for this), but it should address this problem too.
When you load the OpenVSP API, we have the ability to spawn a new Python process and load OpenVSP in that new process.  We then talk to that process via sockets.
We can use this to load multiple OpenVSP models in multiple Python processes -- then each one can be queried independently.  You can have one model of an airplane - and another detailed model of an engine - and a complex OpenMDAO workflow (that normally all executes on a single Python process) can now work.
If you think this would help your issues, I can help show you how to put this together (though I must warn you, I'm terrible at Python).
All that said, my first suggestion would be to not do the OpenVSP work in parallel.  We're usually so much faster than whatever else is going on that you might not actually need the OpenVSP parts to be in parallel at all.


Testing of UI checklist 2.0

UI plugin checklist - copy from #475
Install plugin

[x] Choose appropriate workflow from the next list (by default, use the latest one) https://github.com/UnitTestBot/UTBotJava/actions/workflows/publish-plugin-and-cli.yml
[x] Open IntelliJ IDE
[x] Uninstall previously installed UTBot plugin (if present)
[x] Install the downloaded plugin
[x] Clone or reuse UTBot project (https://github.com/UnitTestBot/UTBotJava.git)
[x] Open the project in the IDE

Make the following checks for IntelliJ, Maven, Gradle projects with different JDK 8/11
Open dialog

[x] Open the utbot-sample/src/main/java/org/utbot/examples/algorithms/ArraysQuickSort.java file
[x] From Project view. Right-click on one class, select Create tests with UTBot... => Dialog is opened. All non-private methods from class are listed and selected
[x] From code. Open context menu, select Generate..., select Create tests with UTBot... => Dialog is opened
[x] Shortcut. Cursor on the class and outside all methods, press Alt+Shift+U => all class methods are selected
[x] Shortcut. Cursor on/inside one method, press Alt+Shift+U => correct method is selected
[x] Shortcut. Not working from build.gradle file, Java class file in test sources root, resources, etc.
[x] Context menu item is disabled for --||--

Dialog. Members

[x] From Project view. Right-click on a package with several classes, select Create tests with UTBot... => Dialog is opened. All classes from package are listed and selected
[x] From Project view. Select several classes, right-click, select Create tests with UTBot... => Dialog is opened. Selected classes are listed and selected
[x] From Project view. Right-click on one class, select Create tests with UTBot... => Dialog is opened. All methods of the class are listed and selected (except private)
[x] Create a public class with 4 different methods: private, without access modifier, protected, public. Open UTBot test generation for the class => all methods except private are in list.
[x] Make the class package-private (remove "public") => check the same

Dialog. Settings
Verify tests are generated with all these options

[x] Dialog. Test source root is defaulted (if test source root is set in project)
[x] Dialog. Test source root (if no test sources root set in project) => suggests to create a new one (red) - create => verify created
[x] Dialog. Test framework => is defaulted to JUnit5 // change request:
#499
[x] Dialog. Test framework (for project with JDK 8) => JUnit4, JUnit5 only // change request:
#309
[x] Dialog. Test framework (for project with JDK 11) => JUnit4, JUnit5, TestNG (not existing in project dependencies must have red text "(will be installed)")
[x] Dialog. Mock strategy => 1) Do not mock, 2) Mock package environment, 3) Mock class environment
[x] Dialog. Mock strategy "No mocks" is selected => Mock static is set to "No static mocking" and disabled
[x] Dialog. Mock strategy - select 2) and 3) options => Mock static options: 1) No static mocking, 2) Mockito static mocking.
[x] Dialog. Mock strategy (for a project without Mockito in dependencies) => 2), 3) options have red text "(will be installed)"
[x] Dialog. Timeout for class => default to 60 sec, only natural numbers can be saved, up and down arrows work
[x] Dialog. Timeout for class => minimize, check on ArrayQuickSort or some other code with conditions and loops
[x] Dialog. Parametrized test => 2 options: Not parametrized / Parametrized
[x] Dialog. Parametrized test - select "Parametrized" => "No mocks" and "No static mocking" are chosen and both disabled
[x] Dialog. Destination package. Check not present // change request:
#488

SARIF report

[x] Dialog. Set "Not parametrized" , generate tests => SARIF report is generated into resources folder
[x] do this for a single class => check place, package, file
[x] do this for several classes in different packages
[x] Dialog. Set "Parametrized" , generate tests => no SARIF report is generated

File -> Settings... -> UTBot

[x] Force static mocking. Add a class...
[x] Code analysis. Select Simplest, Deepest, 1st mark from left, 1st mark from right, somewhere in the middle...

Further changes in UI will be implemented through #977


'pkg' binary name conflict

Hi!
I'm currently looking at various node packagers, and it's very nice to see that yours supports FreeBSD (unlike nar which only supports building executables for Linux, Darwin and Solaris — the ones with node binaries published by the node project itself).
However… FreeBSD's native package manager is literally called pkg ;)

This also happened to node, which conflicted in certain Linux distributions, that just proceeded to distribute it as nodejs.
I would expect Freebsd to do the same: distribute it as pkgjs or have people install it as such (e will include instructions for how to do this in the README).
The bottom line is that in 10 years you will hardly find a name that is short, good, descriptive of your project's goals and doesn't exist already in some $PATH. The solution to it is not really complicated for FreeBSD users, so I don't think we will be renaming the project.

myfreeweb meant "SunOS", not "Solaris".  SunOS is supported by nar, Solaris is not.

@MareoRaft the actual SunOS (<=4.x) died in 1994. Solaris and Illumos have uname "SunOS" for historical reasons (Solaris was SunOS 5.x)


Apply custom font at run-time downloaded from WebServer.

Is it possible to download a custom font file from my webserver and apply it at run-time.

Hi, I would like to do the same thing.
Apply fonts at run-time, downloaded from webserver.
Is there any news here?

Finally I handled that with my custom views. There is no way to achieve this via Calligraphy. I suggest you to don't waste your precious time here.

Finally I handled that with my custom views. There is no way to achieve this via Calligraphy. I suggest you to don't waste your precious time here.

Hi ! Would you be able to share your solution to the community ? That would be great ! Thank you

Finally I handled that with my custom views. There is no way to achieve this via Calligraphy. I suggest you to don't waste your precious time here.

Hi ! Would you be able to share your solution to the community ? That would be great ! Thank you


Fix memory leak root cause: not disposing subscriptions to TP invalidation events

This fixes #106 - unsubscribes the language service from the "invalidate" signal coming from the type providers when a project is done with.
The failure to unsubscribe causes a very small memory leak in a well-functioning type provider which disposes of its resources explicitly
It can cause a very large memory leak when a type provider is badly written and which expects the GC finalization mechanisms to dispose of its resources. This is because the subscription causes a live handle to be kept to otherwise-collectable resources that would trigger invalidation events (like file-system watchers).  If the type provider has explicitly cleaned up file system watchers, then it's not too bad.  But if it hasn't and expects them to be collected, then they are kept alive, often along with all the resources of the type provider as well.
I've added testing and checked it compiles and tests appear to be passing on my machine.
This bug is severe in the sense it's a pretty easy and common form of memory leak in type provider implementations, and has historically been a contributing factor to very major leaks as documents in #106 and the linked bugs.

tests now appear to be passing

Spoke to soon, the added test is not passing

OK, should pass now.

Any guidance on how to properly clean up file system watchers?

@ovatsus - I think it's as you expect: when the type provider instance is disposed, you dispose the file system watchers and keep no live global handles to them. I believe FSharp.Data does this correctly.  AFAIU the problems above only happen if the file system watchers are not disposed explicitly but rather you are relying on GC to cleanup them up.

Code changes make sense. I want to try this out in real VS and test out the repro described in the bug.

This doesn't seem to hurt, but it also doesn't appear to make much of a dent in the overall trend of VS memory consumption. VS still grows to 1-2GB working set/private bytes after 5-10 reloads/rebuilds of the VFPT solution (as described in the issue).

Correct, as far as I'm aware the type providers used by that solution have already been fixed to do explicit cleanup of resources. The problem with TPs was real, but by no means the only cause of memory use.

Got it, LGTM.

Approved 6/2 by ML Shiproom.


Fix uninitialized constant Casino::Authenticator

Fixes uninitialized constant Casino::Authenticator as described in issue https://github.com/rbCAS/CASino/issues/108

Thank you. Merged with some adjustments to match our coding style in 3b5544135673eab5296c42d094ca39a42a9678e4

My pleasure, thanks for a great engine.


feat: Add artifacts uploading

Description
This PR adds uploading artifacts on ci.
Motivation

Closes https://github.com/networkservicemesh/integration-k8s-kind/pull/142
Closes https://github.com/networkservicemesh/integration-k8s-kind/issues/18

This PR is a bit blocked by https://github.com/networkservicemesh/deployments-k8s/pull/637


Nesting cards causes the nested images to not be included

When nesting a card as such:
````card [path] {title: "[title]"}

```card [path2] {title: "[title2]"}
```

````

The secondary (path2) is not included in the building process (unless its already included from somewhere else), neither for preview nor for gen. This causes the card to simply fallback to the alt attribute.
I know this probably isn't exactly the intended use cause for cards and would honestly understand if this can't/won't be fixed.
Noteworthy is however that the image (and entire card) works properly if the image gets included from somewhere else, it just breaks if it's the only source of the image.
In preview this can behave rather dodgy, as in sometimes the image works - sometimes it doesn't. However for actually genning the page you can verify that the file will be missing from the output.
An example use case:

Oh interesting usecase! Even though not planned I believe it should be fixed to work as expected. Going to take a look later today. Thank you for the report!

turned out it is not just for nested card, but for any image referenced inside a card content.
I can push a patch if you plan to use the fix soon.

It's not exactly urgent for us, so it's fine if the fix isn't immediate

Hey, its been a while!
If possible when the patch is out could you mention either of us?
That way we'll be able to make the new build and publish the new pages we have. Once we have that we'll be basically done with the project (aside from updates of course)

Hello! Of course.
I am eager to see what your docs look like. May push a patch tonight as I will be OOO for some time.

@Haxiz @MrLar 1.61.2 is released

@MykolaGolubyev its up!
https://www.mantaro.site/mantaro-wiki/

I don’t see cards :( maybe cache. Will try later.

We only really use cards in https://www.mantaro.site/mantaro-wiki/currency/items, https://www.mantaro.site/mantaro-wiki/currency/badges and some in 102 to 104 of currency.

Nice! Thanks for sharing.
congrats on the push. Docs are very detailed and very well structured.
One thing I noticed is some tables here are more readable on mobile then the others
https://www.mantaro.site/mantaro-wiki/basics/server-configuration

One thing I noticed is some tables here are more readable on mobile then the others
https://www.mantaro.site/mantaro-wiki/basics/server-configuration

Yeah that page we had to leave mostly as it was before as there is a planned update that will overhaul that section. So we didn't think it was worth remaking the page if we would have to remake everything later down the road.


How can I disable the dragging of image inside the layout in mozila firefox.

Thanks for submitting an issue to RGL!
Please mark the type of this issue:

[ ] Bug
[ ] Feature Request
[ ] Question

If you have a question or bug report, please use the WebpackBin Template
to demonstrate. It is much easier for us to help you if you do.

This is not stackOverflow. You even not checked "question".
What you are looking for is draggable="false"
You can close this issue.


STORM-1890: ensure static UI resources are re-requested with differen…

…t Storm package builds
Note it doesn't perform cache busting for logviewer. That is creating its own HTML, where I think it can be refactored to use some static file in public/, that is a separate task.
Thanks! I'll backport to 1.x if this looks good.

Build errors are unrelated to change.

LGTM. +1

I am going to close this and will re-open with some changes to add special not-caching headers for files like index.html or topology.html. While testing this for the 1.x branch I realized those files have the same issue, but you can't use cache busting there. So we need to ensure ring adds the no-cache headers for .html files that we serve.


Password and Login in plan text in URL

Hi,
I just realized, that Password and Username are visible in the URL. This hinders a usage in a near productive environment. Is there a possibility to change that behavior to move these to Post and use Session-Variables instead of Paramenters in post.
Cheers
Karsten

Hi Karsten, thanks for your feedback.
Yes you can set the form method to "post" instead of "get" in default.aspx; I did it initially (with session variables), but it has a boring drawback: if you hit F5 to reload the page, the browser ask you if you want to re-post the form data (standard behaviour). I understand the security argument but, if you use https, the querystring is also encrypted with SSL (so it's ok from a network point of view).
That said, indeed, if someone has access to the browser history, it could find back the credentials within url. What is possible to do is to have the form posted, save the credentials within session (may be used for file transfer), then set the page url with javascript as "window.location.href = window.location.href", which will make the browser to reload the page but without the form data (so subsequent F5 will not bother to repost the form).
I will have a look at it as soon as possible.

Fixed in release v1.1.1

Hey Cedric,
well done. Now we are save :-).


Admin interface

Flutter code for building admin interface.

With Admin interface do you mean something similar like Django Admin which is automatically generated with website or do you mean something else?

I think it will be like appwrite GUI.
Is this part initiated? (When we can expect this)
I would like to work on this GUI part for serverpod...?

When will it be implemented?

I think Strapi has a more inclusive type of admin panel than "appwrite".. if you are thinking to bring designers and not only programmers..

PS: in fact I think this is the key of everything.. what do you want this to be? I think the admin interface can lead to many multiple business models.. one that I like is to have a startup admin interface where you have basic stuff and develop your own stuff from there on..
and also to have different ready templates that you could purchase with a monthly subscription.. where you will get new stuff/features and that it will be updated to the standards every year, etc..
plus all the other stuff options on the cloud...

when are we supposed to expect this part @vlidholt ? 6 months from now? a year?

Sorry cannot give a timeline. We are planning one milestone at at time. Current focus is to get the 1.0 release out, then the 1.1 version will focus mostly on database migrations. I think after that it's possible we can start working on a better admin interface etc.

We have just encountered this where we have had to create our own back-end admin interface just to implement simple crud operations on all of our tables. Considering serverpod already knows what your database looks like, it would be amazing if when serverpod generate is run, serverpod also generated a custom admin area with a page for each database table with simple CRUD operations on it. The admin area should also be modifiable and extendable very similar to something like Laravel nova where you could even support community-built admin panel packages.

Sorry cannot give a timeline. We are planning one milestone at at time. Current focus is to get the 1.0 release out, then the 1.1 version will focus mostly on database migrations. I think after that it's possible we can start working on a better admin interface etc.

Based on the roadmap version 1.2 is database migrations. is the admin interface included in 1.3?

@easazade the roadmap only covers the core Serverpod features, and not Insights. We hope to get a good database viewer/editor ready for 1.2 too.

@vlidholt Until official release, here is an Admin Interface for Serverpod
https://github.com/rohitsangwan01/serverpod_admin_panel

Still no efforts have been made? When should we really expect this feature?

If this ticket tracks the generation of admin api's (so we don't need to manually write all the CRUD operations for a CMS) that would be great. Because right now I am creating all CRUD operations manually with admin permissions.


Fixed layout issue at shop end in ar #3467

BUGS:
Issue: https://github.com/bagisto/bagisto/issues/3467

Done

Hello @devansh-webkul
Kindly resolve conflicts.


[Enhancement]: keyboard sound enhancement in Master Typing

Is your enhancement request related to a problem? Please describe.➕
Game enhancement:
sound differently when the wrong key is pressed.
Describe the solution you'd like
Solution steps:
Updation of JS file.
Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

/assign

Hello @samratghosh291, Time's Uppp!⏰
Sorry for closing your issue!
But it's more than a week since we haven't received anything from your side 😢 .
Come up with new ideas, create a new issue and make sure you finish it within a week! 🔥
All the best! 🚀
Happy Hacking! 💗

Hey @samratghosh291 ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


Chore remove misc-unused-parameters check

Proposed changes
remove misc-unused-parameters check
Problem summary
Describe your changes.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[ ] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[ ] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[ ] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

Why remove this check?

Why remove this check?

For some abstract methods, we tend not to annotate useless parameters

Why remove this check?

For some abstract methods, we tend not to annotate useless parameters

Is it possible to remove the parameter name and keep the parameter type in this case?

Yes, but I prefer clang-tidy do not produce a warning on here.


In angular app when navigating to a page with a babylonjs canvas it isnt rendered.

Use Github issues ONLY for validated bugs
We have a really active forum to help answering questions (https://forum.babylonjs.com/)
If you are convinced that you found a bug, please use the following template for your issue:
Bugs

Bug repro on playground:
Expected result:
Current result:

Feature request

Link to forum discussion about the feature:
Feature description
Additional links that could help implementing the feature:

I am building an app using your babylon js engine.  It renders the webgl correctly if I initiate the application directly on the page that has the canvas on it.  But if I navigate to a different page and then come back to the canvas page, the WebGL isn't rendered.  I get the canvas events (Mouse, Keyboard)  so I know it is there and catching events from the browser.  is there some additional hook or event I need to respond to to get the webGL to redisplay?

Hello please use our forum (forum.babylonjs.com) for questions


Remove --target-os from dart compile exe (or making it a NOP)

Right now the dart compile exe command cannot cross compile, so we always know the target operating system. There's therefore no point in providing a --target-os option, the tool knows internally what OS to use.
@sstrickl could you either remove this option or make it a NOP and make the tool auto-detect the OS?

/cc @mit-mit

I suggest we for dart compile exe:

default --target-os to the current OS
print an error if --target-os is passed stating that we currently do not support cross compilation for executables

For 2, I'd only print an appropriate error if the argument to --target-os differs from the current OS, just so that we don't break any current workflows that, for some reason, passes it explicitly since we exposed it, which is how I plan to implement it ATM.

SGTM


Test environment not working

As a PM and a team,
We want to ensure that the test environment is working
So, we can thoroughly test new iterations of work to ensure quality

Graph Explorer -tst and -int environments are now working.


Add configuration option to return interface declarations without pragma/spdx/comments

Heya 🙌
I'm using abi-to-sol with solidity-shell to fetch abi and autogenerate interfaces from etherscan and just wanted to say this lib is amazing!
My tool merges the generated interface decl into an existing source unit that defines an SPDX header and version pragma already. Would it be possible to add options to output the interface declarations (and types etc.) without any inline comments, SPDX, or pragma?
generateSolidity({
...
outputPragma: False
outputSPDX: False
outputComments: False
...
}

thanks!
ref: https://github.com/tintinweb/solidity-shell/pull/20

Thanks for opening this! I'll knock this out over the weekend.

Sorry for the delay @tintinweb, but I just put up a draft PR #91 to address this. I've got some more testing to do on it before I publish it in a release, but quick question for you...
Would you consider leaving --no-attribution turned off? With my changes in #91, if you specify mode: "embedded" in the options, then the abi-to-sol attribution notice will appears inside the primary interface, rather than as a separate sourceunit-level, if that was your reasoning for turning that message off.
Of course feel free to keep using that option, but thought I'd ask :)

Hey @gnidan, thanks for adding this feature 🤗. There are two reasons for omitting everything other than pure solidity code in solidity-shell.

solc is picky when compiling source code and that's why I try to selectively include interface code only. Ideally, the lib would only produce actual interface code w/o pragmas/spdx headers/comments of any sort as multiple or inconsistent pragmas, contradicting SPDX headers may just fail compilation)
I'd like to keep the solidity-shell session output as pure as possible - code only. anything else just unnecessarily pollutes the session (potentially over and over again, i.e. in debug mode or when fetching multiple interfaces).

I think the better solution is to link your tool in the Readme. Open to other ideas 😊. Cheers 🙌

Hey @tintinweb, sorry for the delay in publishing these changes. They're live now in v0.7.0 and greater, and you probably noticed that I just opened https://github.com/tintinweb/solidity-shell/pull/26 to incorporate them into solidity-shell.
Understood about the attribution message... thanks for mentioning it in your README's acknowledgements! 🙇
Anyway, closing this issue now :) Thanks again!


Unable to delete item in repeater if Mask is used for TextInput

Package
filament/filament
Package Version
v2.10.9
Laravel Version
v8.77.1
Livewire Version
v2.0.2
PHP Version
PHP 8.0
Bug description
Adding a mask to a TextInput in a repeater resulting item unable to be deleted.  When click delete, the item is removed and then it reappears as an empty item.
If remove the mask, the item is deleted correctly.
                         Forms\Components\HasManyRepeater::make('my_rep')
                                ->relationship('my_rel')
                                ->schema([
                                    Forms\Components\TextInput::make('duration')
                                        ->label(__('DUR'))
                                        ->mask(
                                            fn (Forms\Components\TextInput\Mask $mask) => $mask
                                                ->numeric()
                                                ->integer()
                                        )

...
Steps to reproduce
No response
Relevant log output
No response

Hey, I'm not going to be able to fix this. It's an incompatibility issue with Livewire/Alpine & iMask.js, but I am not skilled enough in the internals of that library to work out what's up. Alpine will soon be releasing its own masking plugin, so we'll move to using that as soon as it's released.

oh, https://alpinejs.dev/plugins/mask does exist!

This bug is actual in v2.16.52