Changes from 3.4.0 breaks match exhaustive checking of a macros

Compiler version
Airstream released v17.2.0, which introduce a macro that help users to "split" signal of a ADT into signal of its children.
This macros re-arranges case blocks and create a match expr out of it, there for leverages the compiler's exhaustive checking.
It works on 3.3.4, but stop working on >=3.4.0
Minimized code (required Airstream v17.2.0)
import com.raquo.laminar.api.L.*

object Main {

  sealed abstract class Page {}

  sealed abstract class ToolPage extends Page {}

  case object CompilePage extends ToolPage {}

  case object AsmEmulatePage extends ToolPage {}

  case object BugHuntersPage extends Page {}

  def testSignal(pageSignal: Signal[ToolPage]): Unit = {
    pageSignal
      .splitMatchOne
      .handleValue(CompilePage)(())
      .toSignal
  }

  def main(args: Array[String]): Unit = ()

}

Expectation
on scala 3.3.4 LTS, compiler will warn "match may not exhaustive".
it should remains so on >=3.4
UPDATED: further checking yields the following results:
3.3.4 works, 3.4.0 doesn't, 3.5.0 doesn't, 3.5.1 works, 3.5.2 works, 3.6.2 doesn't

seems like this is the cause, what can we do in this situation?

I can understand why you wouldn't want the compiler generating warnings for macro code that you don't necessarily have any control over as a user, but that could be done by macro authors with an @unchecked annotation anyway.

while looking into this I used the -Xprint:inline scalac options and I can see the generated code is very different (and it shows why 3.6.2 won't do the exhaustiveness checks - there's no match at all, in contrast to 3.5.1)
(I cleaned up parts of the printed code to make it more legible, so it might not be 100% accurate, but it shows the idea):
Source:
  enum Test {

    case Case1
    case Case2
    case Case3(value: String)

  }

  val s: Signal[Test] = Val(Test.Case2)

  // ...
  s.splitMatchOne
   .handleType[Test.Case3].apply { (init, sig) =>
//     ...
   }
   .toSignal

Scala 3.5.1:
MyModule.s.map[
(Int, Any)](
{
  def $anonfun(
    i: MyModule.Test)
    : (Int, Any) =
    i match // a REAL match
      {
        case t @_: MyModule.Test.Case3 =>
          {
            val res: Any =
              t:
                  MyModule
                    .Test.Case3

            Tuple2.apply[Int, Any](0,res)
          }
      }
  closure($anonfun)
}

Scala 3.6.2:
def $anonfun(
  i: MyModule.Test
): (Int, Any) =
  matchResult5[(Int, Any)]:
    {
      case val x6:

          (i : MyModule.Test) = i
      if // an if-else instead of a match
        x6.$isInstanceOf[MyModule.Test.Case3]
       then
        {
          case val t: MyModule.Test.Case3
           = x6.$asInstanceOf[MyModule.Test.Case3]
          return[matchResult5]
            {
              val res: Any =
                t:
                    MyModule
                      .Test.
                      Case3

              Tuple2.apply[Int, Any](0, res)
            }
        }
       else ()
      throw new MatchError(x6)
      }
  closure($anonfun)

I also tried adding more "cases" to make sure it's not an edge case optimization - and no, it just results in more if ... return else ()
case val x6:

  (i : MyModule.Test) = i

  if x6.$isInstanceOf[MyModule.Test.Case3]
  then
  // ...
  return // ...
  else ()

  if x6.eq(MyModule.Test.Case1)
  then
  // ...
  return // ...
  else ()

  throw new MatchError(x6)

P.S. (i : MyModule.Test) = i doesn't look like valid scala code, like case val

3.3.4 works, 3.4.0 doesn't, 3.5.0 doesn't, 3.5.1 works, 3.5.2 works, 3.6.2 doesn't

Ugh. 😕
BTW, please provide the definition of the dependencies/build when raising issues.
Here's what seems like the full repro with Scala CLI:
//> using dep com.raquo::airstream::17.2.0
//> using dep com.raquo::laminar::17.2.0
//> using platform js
import com.raquo.laminar.api.L.*

object Main {
  sealed abstract class Page {}
  sealed abstract class ToolPage extends Page {}
  case object CompilePage extends ToolPage {}
  case object AsmEmulatePage extends ToolPage {}
  case object BugHuntersPage extends Page {}
  def testSignal(pageSignal: Signal[ToolPage]): Unit = {
    pageSignal
      .splitMatchOne
      .handleValue(CompilePage)(())
      .toSignal
  }
  def main(args: Array[String]): Unit = ()
}

cc @jchyb @sjrd

We did reenable exhaustivity checks for 3.5.1 onwards (in https://github.com/scala/scala3/pull/20403, leaving reachability warnings turned off), so some of that back and forth is expected, but it should work for 3.6, so I will investigate that further

Minimised:
import scala.quoted._

sealed trait Foo
case object Bar extends Foo
case object Baz extends Foo

object Macro {
  inline def makeMatch() = ${makeMatchImpl}
  def makeMatchImpl(using Quotes) = {
    '{
      (_: Foo) match
        case Bar => ()
    }
  }
}

@main def main() = Macro.makeMatch()


Add missing period for sentences in classref

Found a missing period when translating the classref.
Others are found by rg -t xml '^\s+[A-Z].+[^!.;:\]]$' doc/ and go through the list manually.

Thanks!


Clarifying how to override default grid, creating grids within grids

After much confusion, I think I learned how to do a "grid within a grid" in singularity, and wanted to confirm with someone.

I've always set a global grid on a site, related to breakpoints, such as:
@include add-grid(12 at $tablet);
@include add-grid(16 at $desktop);

So with 16 columns available at desktop width, I could make a simple 2-column grid, such as:
.sidebar-first { @include grid-span(4, 1); } .main-content {@include grid-span(12, 5); }

Now what if I want a 3-col grid inside that main-content area? I thought it could be as simple as:

 .list { @include float-span(4); }
but it was treating the 'grid-space' as 16 columns (the global value) instead of the current grid it was inside (12 column main-content).

I tried to overwrite this by including:

 .main-content {@include grid-span(12, 5); @include add-grid(12); }
but it didn't work, it was still 16 columns, meaning my 3 .list items didn't fill the area nicely.

Then I thought, maybe it was because I declared my global grid with a breakpoint (@include add-grid(16 at $desktop);)

So I tried to overwrite that for my grid-within-a-grid:
 .main-content {@include grid-span(12, 5); @include add-grid(12 at $desktop); }

Boom, it worked! I suddenly had a 12 column grid inside my main-content, and could easily create a 3 column list inside it.

Hope that makes sense. I just never knew that was something I had to do. I'd be happy to contribute to some documentation if need be. If I'm going about this the wrong way, could someone let me know?

To override use mixin layout
read this section "Group Context Overrides"
https://github.com/at-import/Singularity/wiki/spanning-the-grid

To override, I use mixin layout
section "Group Context Overrides"
https://github.com/at-import/Singularity/wiki/spanning-the-grid


linux path support pls

error:
FileNotFoundError: [Errno 2] No such file or directory: '/home/sergey/HDD/pycode/processing\\shaders'

Oh thank you, I forget that. I updated the code, it should also work on unix systems now.

thank you


Rr/mcw rali

This is the latest changes for RALI form MCW

@rrawther Can you check this. The CI fails to build. I can test it once it builds

Also pushed changes for cifar10 data loader  for RALI

@kiritigowda Can you merge this. The build was failing because RPP was not merged

@rrawther can you look at LGTM alerts

@rrawther passing CI with updates to dependencies and RPP V0.3, this is read to be merged.
Is this branch ready?


ibazel does not monitor the WORKSPACE file

Describe the bug
ibazel does not react when the WORKSPACE file changes.
Reproduction instructions
Any repository that has some dependencies specified in the WORKSPACE file.
Steps to reproduce the behavior:

build a target that depends on an external repository
run ibazel build <target>
Edit the WORKSPACE e.g. to change the tag or commit to which a git repository is sync'd.
Notice no reaction from ibazel

Expected behavior
ibazel does what bazel would do, i.e. sync the repository, and rebuild the target.
Version (please complete the following information):

OS: Ubuntu 20.04
Browser not relevant
ibazel Version from git, commit 51d9fe43bf520ce40a3c22affc960fd094fce51d
Bazel 3.6.0

PS: If this is the same Pascal Fleury from Google Zurich, it's great to see you! Hope you're enjoying ibazel.

it is me :-)
I'll give it a shot for the fix.
--Pascal
Le ven. 16 oct. 2020 à 23:27, Andrew Z Allen<EMAIL_ADDRESS>a
écrit :

PS: If this is the same Pascal Fleury from Google Zurich, it's great to
see you! Hope you're enjoying ibazel.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/bazel-watcher/issues/427#issuecomment-710655328,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABBP5KAJ2ZQSYNOF3KBCYIDSLC3BTANCNFSM4STZROFA
.

Is there a way to un-stale this issue? @pascalfleury Are you still working on this?


Question: unable to use react-native-calendars

I have tried deleting node_modules and reinstalled npm but not resolved .
error: bundling failed: Error: Unable to resolve module hoist-non-react-statics  from E:\DEVELOPMENTWORKSPACE\test\node_modules\react-native-calendars\src\exp andableCalendar\asCalendarConsumer.js: Module hoist-non-react-statics does no
t exist in the Haste module map
This might be related to https://github.com/facebook/react-native/issues/4968
To resolve try the following:

Clear watchman watches: watchman watch-del-all.
Delete the node_modules folder: rm -rf node_modules && npm install.
Reset Metro Bundler cache: rm -rf /tmp/metro-bundler-cache-* or npm star t -- --reset-cache.
Remove haste cache: rm -rf /tmp/haste-map-react-native-packager-*.
at ModuleResolver.resolveDependency (E:\DEVELOPMENTWORKSPACE\test\node_modul
es\metro\src\node-haste\DependencyGraph\ModuleResolution.js:183:15)
at ResolutionRequest.resolveDependency (E:\DEVELOPMENTWORKSPACE\test\node_mo
dules\metro\src\node-haste\DependencyGraph\ResolutionRequest.js:52:18)
at DependencyGraph.resolveDependency (E:\DEVELOPMENTWORKSPACE\test\node_modu
les\metro\src\node-haste\DependencyGraph.js:283:16)
at Object.resolve (E:\DEVELOPMENTWORKSPACE\test\node_modules\metro\src\lib\t
ransformHelpers.js:264:42)
at dependencies.map.result (E:\DEVELOPMENTWORKSPACE\test\node_modules\metro
src\DeltaBundler\traverseDependencies.js:399:31)
at Array.map ()
at resolveDependencies (E:\DEVELOPMENTWORKSPACE\test\node_modules\metro\src
DeltaBundler\traverseDependencies.js:396:18)
at E:\DEVELOPMENTWORKSPACE\test\node_modules\metro\src\DeltaBundler\traverse
Dependencies.js:269:33
at Generator.next ()
at asyncGeneratorStep (E:\DEVELOPMENTWORKSPACE\test\node_modules\metro\src\D
eltaBundler\traverseDependencies.js:87:24)
DELTA  [android, dev] ./index.js ░░░░░░░░░░░░░░░░ 0.0% (0/1), failed.

0
The problem is that src/expandableCalendar/asCalendarConsumer.js is trying to import 'hoist-non-react-statics' which is not declared as a dependency in package.json So the solution is to add it in package.json as this:
"dependencies": {
"lodash": "^4.0.0",
"prop-types": "^15.5.10",
"xdate": "^0.8.0",
"hoist-non-react-statics": "*"},

than run npm install, run react-native run-ios and you're up to go!

thank you @XEmAX32 ,  this solution worked for me .


Fix output file location for CodeCov to work

The CodeCov GitHub action needs the output file to be in the base directory, at least by default. Make sure it is written to the right place during CI.

Thanks!

@all-contributors add jtsay362 for code

@all-contributors add @jtsay362 for code

You're very welcome, thanks for creating this helpful project!


Implement SourceSpan as a trait

I already have a sourcespan-like struct that is sprinkled all over my code base and I was hoping to use this library as a way to prettify my errors but it would mean a complete refactor.
Is there a way around this or does this require what I hope it doesn't?
This is what I currently have:
#[derive(Debug, PartialEq, Clone)]
pub struct Token {
    pub token: String,
    pub token_kind: TokenKind,
    pub row: usize,
    pub column: Line,
    pub namespace: PathBuf,
}

#[derive(Debug, PartialEq, Clone)]
pub struct Line {
    pub start: usize,
    pub end: usize,
}

//...other code here

If your implementation is based on row + column instead of byte offset and length (which is what miette primarily uses), you can use this utility method on SourceOffset, combined with a From implementation (or so) to convert your Token struct into the necessary SourceSpans.
Does that make sense?

Thanks. I've managed to do as you say but it the labels don't render

and here is the snippet of code relating to that

Labels don't render unless you specify a source_code for the error. You can do this either by either putting the relevant source code into the error and tagging it with #[source_code] (it can be anything that implements SourceCode, such as String, or any custom source representation you implement it for), or by providing it at the very end, using .with_source_code().

I think this was resolved in a satisfactory way, so I'm closing this.


Condition Ready is True when Deployment replicas are 0

Using - master@01d8bf78
It would seem as though the controller isn't updating the status when deployment scaled (or even if a deployment deleted and re-created with bad image):
$ kubectl -n captain-system scale deploy/captain-controller-manager --replicas=0
deployment.extensions/captain-controller-manager scaled
$ date ;kubectl -n captain-system get deploy,svc -l app=captain -o wide
Fri  7 Feb 2020 12:34:34 GMT
NAME                                               READY   UP-TO-DATE   AVAILABLE   AGE    CONTAINERS   IMAGES                                 SELECTOR
deployment.extensions/captain-controller-manager   0/0     0            0           5d1h   manager      index.alauda.cn/claas/captain:v0.9.4   app=captain

NAME                      TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)            AGE    SELECTOR
service/captain-webhook   ClusterIP   <IP_ADDRESS>   <none>        443/TCP,6060/TCP   5d1h   app=captain

And then the pertinent logs after the next reconciliation period:
$kubectl -n application-system logs -l control-plane=application-manager -c manager
...
2020-02-07T12:36:31.857Z	INFO	controllers.Application	NoMappingForGK	{"application": "captain-system/captain", "gk": "Service.controller"}
2020-02-07T12:36:33.910Z	INFO	controllers.Application	NoMappingForGK	{"application": "captain-system/captain", "gk": "Deployment.controller"}
2020-02-07T12:36:33.910Z	DEBUG	controller-runtime.controller	Successfully Reconciled	{"controller": "application", "request": "captain-system/captain"}
...

And finally the application object after the reconciliation:
$ date ; kubectl -n captain-system get application -o yaml
Fri  7 Feb 2020 12:37:37 GMT
apiVersion: v1
items:
- apiVersion: app.k8s.io/v1beta1
  kind: Application
  metadata:
    annotations:
      kubectl.kubernetes.io/last-applied-configuration: |
        {"apiVersion":"app.k8s.io/v1beta1","kind":"Application","metadata":{"annotations":{},"labels":{"kore-direct":"true"},"name":"captain","namespace":"captain-system"},"spec":{"assemblyPhase":"Pending","componentKinds":[{"group":"controller","kind":"Service"},{"group":"controller","kind":"Deployment"}],"descriptor":{"description":"A controller for deploying helm3 charts","type":"captain","version":""},"selector":{"matchLabels":{"app":"captain","service_name":"captain"}}}}
    creationTimestamp: "2020-02-07T11:23:21Z"
    generation: 2
    labels:
      kore-direct: "true"
    name: captain
    namespace: captain-system
    resourceVersion: "8742901"
    selfLink: /apis/app.k8s.io/v1beta1/namespaces/captain-system/applications/captain
    uid: 3fa08887-499c-11ea-8449-42010a9a009c
  spec:
    assemblyPhase: Pending
    componentKinds:
    - group: controller
      kind: Service
    - group: controller
      kind: Deployment
    descriptor:
      description: A controller for deploying helm3 charts
      type: captain
      version: ""
    selector:
      matchLabels:
        app: captain
  status:
    conditions:
    - lastTransitionTime: "2020-02-07T11:23:24Z"
      lastUpdateTime: "2020-02-07T11:23:24Z"
      message: all components ready
      reason: ComponentsReady
      status: "True"
      type: Ready
    - lastTransitionTime: "2020-02-07T11:23:24Z"
      lastUpdateTime: "2020-02-07T11:23:24Z"
      message: No error seen
      reason: NoError
      status: "False"
      type: Error
    observedGeneration: 2
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""

@lewismarshall Thanks for the issue.
We will more tests around this case.
@nan-yu FYI

@lewismarshall
I ran some tests on my end and thought the controller is doing the right thing. Basically, the controller computes the deployment status based on conditions. It considers the deployment status as Ready in the following scenarios:

if no conditions are found in deloyment status, OR
if condition.type == Processing is found, condition.status must be true and condition.reason must be NewReplicaSetAvailable AND
if condition.type == Available is found, condition.status must be true

Scaling down deployment replicas to 0
When deployment replicas is set to zero, the deployment is considered to be Ready as Deployment has minimum availability, i.e. 0.
Hence, in this case, there's no need to update the application status.
Update deployment with a bad image
Can you re-test this scenario? I updated the deployment with a bad image. The condition status for Available type is "false" with a MinimumReplicasUnavailable reason.
status:
  conditions:
  - lastTransitionTime: "2020-02-07T18:24:23Z"
    lastUpdateTime: "2020-02-07T18:27:18Z"
    message: ReplicaSet "nanyu-hello-6c4f6d79bd" has successfully progressed.
    reason: NewReplicaSetAvailable
    status: "True"
    type: Progressing
  - lastTransitionTime: "2020-02-07T18:46:38Z"
    lastUpdateTime: "2020-02-07T18:46:38Z"
    message: Deployment does not have minimum availability.
    reason: MinimumReplicasUnavailable
    status: "False"
    type: Available
  observedGeneration: 6
  replicas: 1
  unavailableReplicas: 1
  updatedReplicas: 1

The controller did update the application status with the following:
status:
  components:
  - group: apps
    kind: Deployment
    link: /apis/apps/v1/namespaces/default/deployments/nanyu-hello
    name: nanyu-hello
    status: InProgress
  - group: batch
    kind: Job
    link: /apis/batch/v1/namespaces/default/jobs/pi
    name: pi
    status: Ready
  - kind: Service
    link: /api/v1/namespaces/default/services/wordpress-webserver-svc
    name: wordpress-webserver-svc
    status: Ready
  conditions:
  - lastTransitionTime: "2020-02-07T18:46:39Z"
    lastUpdateTime: "2020-02-07T18:46:39Z"
    message: some components not ready
    reason: ComponentsNotReady
    status: "False"
    type: Ready
  - lastTransitionTime: "2020-02-07T18:24:23Z"
    lastUpdateTime: "2020-02-07T18:24:23Z"
    message: No error seen
    reason: NoError
    status: "False"
    type: Error
  observedGeneration: 1

@nan-yu  fair enough regarding scaled down:

Hence, in this case, there's no need to update the application status.

Not sure about this one though:

if no conditions are found in deloyment status

If the objects can't be found due to:

application not yet deployed
bad select labels (my bad)
bad RBAC for operator (investigation)

Maybe this shouldn't be Ready but Unknown? Would like to use application kind to work out when applications are really Ready but at the moment it's kind of "not really known so  let's assume Ready"?
Not sure if that's fair as I may be missing something. An illustration for this is below (bad RBAC):
status:
  conditions:
  - lastTransitionTime: "2020-02-13T16:30:39Z"
    lastUpdateTime: "2020-02-13T16:30:39Z"
    message: all components ready
    reason: ComponentsReady
    status: "True"
    type: Ready
  - lastTransitionTime: "2020-02-13T16:30:39Z"
    lastUpdateTime: "2020-02-13T16:30:39Z"
    message: 'deployments.apps is forbidden: User "system:serviceaccount:application-system:default"
      cannot list resource "deployments" in API group "apps" in the namespace "kore-system"'
    reason: ErrorSeen
    status: "True"
    type: Error

I agree it's unfair to set an application Ready when it's actually Unknown. We updated how we compute resource status here based on this public doc.
For the bad RBAC error, the rules of the role has been fixed. You shouldn't see the error with the latest code.
To better handle cases like this, we set the application's condition to NotReady when error occurs in status-aggregation stage: fix.
@lewismarshall ^^

@lewismarshall  - With the recent merges would this issue be closed ?

@barney-s I think so, I will test now.

@barney-s I think so, I will test now.

@barney-s tried to re-build to test, unfortunately got this:
Get<EMAIL_ADDRESS>unexpected EOF

I'll try and test on Monday

@barney-s yes I can confirm for the bad image the Ready condition is now False will now correctly show

thanks for confirming @lewismarshall
/close


ks.groupby won't drop groups with one or more null keys

This is basically where the pandas groupby adopts its behaviour from r.
I can submit a pr if this is not on anyones roadmap

pyspark doesn't drop null groups. I didn't know this.
>>> sdf.show()
+----+
|   x|
+----+
|null|
| 1.0|
| 1.0|
+----+

>>> sdf.groupBy('x').count().show()
+----+-----+
|   x|count|
+----+-----+
|null|    1|
| 1.0|    2|
+----+-----+

>>> sdf.toPandas().groupby('x').agg({'x': 'count'})
     x
x
1.0  2

@harupy correct. That is to keep it consistent with r library

Yeah, I noticed this behaviour as well lately. Please go ahead for a PR!

Okay thanks, I'm on it

Hi, pandas 1.1.0 recently added a dropna parameter in order to allow groupby on null keys.
By default (True), null keys are dropped, and it has pyspark behavior when set to False.
I think it would be interesting to add it to koalas dataframe groupby method.
May i work on it ?

@LucasG0 Awesome, please go ahead! Thanks!
cc @itholic as working on pandas 1.1 support

Thanks, @LucasG0 .
And thanks for the notice, @ueshin


Added more breez health check

Add breez health check in send flow
Add breez health check in swap flow
Show alert saying "BTC wallet is offline. Please try later." if breez is not operational

what's the best way to test this?

code looks good, but leaving this one open until we hear back from Breez and Blockstream on getting Greenlight health checks

Closing as we are moving away from greenlight.


Linux web_long_running_tests flakes with error version info not in JSON

(part of https://github.com/flutter/flutter/issues/97036)
These data is based on Q4 2021 flakes that happened from 10/01/2021 to 01/13/2022
1 flake when running cd dev/integration_tests/web_e2e_tests; ../../../bin/flutter drive --target=test_driver/url_strategy_integration.dart --browser-name=chrome --no-sound-null-safety -d web-server --release --web-renderer=html (2542 on 12/28/2021)
▌02:30:03▐ RUNNING: cd dev/integration_tests/web_e2e_tests; ../../../bin/flutter drive --target=test_driver/url_strategy_integration.dart --browser-name=chrome --no-sound-null-safety -d web-server --release --web-renderer=html
Running "flutter pub get" in web_e2e_tests...                    1,668ms
Launching test_driver/url_strategy_integration.dart on Web Server in release mode...
Compiling test_driver/url_strategy_integration.dart for the Web...        35.5s
test_driver/url_strategy_integration.dart is being served at http://localhost:36967
The web-server device requires the Dart Debug Chrome extension for debugging. Consider using the Chrome or Edge devices for an improved development workflow.

UnknownException (13): unknown error: version info not in JSON
  (Driver info: chromedriver=84.0.4147.30 (48b3e868b4cc0aa7e8149519690b6f6949e110a8-refs/branch-heads/4147@{#310}),platform=Linux 4.9.0-14-amd64 x86_64)
#0      parseJsonWireResponse (package:webdriver/src/handler/json_wire/utils.dart:82:9)
#1      JsonWireSessionHandler.parseInfoResponse (package:webdriver/src/handler/json_wire/session.dart:27:21)
#2      JsonWireSessionHandler.parseCreateResponse (package:webdriver/src/handler/json_wire/session.dart:18:7)
#3      InferSessionHandler.parseCreateResponse (package:webdriver/src/handler/infer_handler.dart:100:39)
#4      AsyncRequestClient.send (package:webdriver/src/common/request_client.dart:96:32)
<asynchronous suspension>
#5      createDriver (package:webdriver/async_core.dart:64:19)
<asynchronous suspension>
#6      WebDriverService.startTest (package:flutter_tools/src/drive/web_driver_service.dart:141:19)
<asynchronous suspension>
#7      DriveCommand.runCommand (package:flutter_tools/src/commands/drive.dart:272:28)
<asynchronous suspension>
#8      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1161:27)
<asynchronous suspension>
#9      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#10     CommandRunner.runCommand (package:args/command_runner.dart:209:13)
<asynchronous suspension>
#11     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:281:9)
<asynchronous suspension>
#12     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#13     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:229:5)
<asynchronous suspension>
#14     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:62:9)
<asynchronous suspension>
#15     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#16     main (package:flutter_tools/executable.dart:94:3)
<asynchronous suspension>

Another flake on Linux web_long_running_tests_2_5: https://ci.chromium.org/ui/p/flutter/builders/prod/Linux web_long_running_tests_2_5/2263/overview

Another flake: https://ci.chromium.org/ui/p/flutter/builders/prod/Linux web_long_running_tests_1_5/2990/overview

This is still happening: https://ci.chromium.org/ui/p/flutter/builders/prod/Linux web_long_running_tests_2_5/3291/overview

A user filed this as well: https://github.com/flutter/flutter/issues/101041

One more: https://ci.chromium.org/ui/p/flutter/builders/prod/Linux web_long_running_tests_1_5/3585/overview

This happened again: https://ci.chromium.org/ui/p/flutter/builders/prod/Linux web_long_running_tests_1_5/3845/overview
Marking as P2 as this is consistently happening.

This is the same as https://github.com/flutter/flutter/issues/102660, no?

Dup of https://github.com/flutter/flutter/issues/102660.


Backstage container crash reboots when clicked on techdocs

Expected Behavior
Published techdocs are displayed.
Actual Behavior
The backstage container (not the pod) crash restarts.
Steps to Reproduce

Click on Docs from the menu on the left.
Click on a component whose documentation you'd like to see.

Context

Techdocs are generated and published to S3 compatible object storage by a CI/CD pipeline.
The documentation shows up correctly when a component is selected and Docs tab is clicked.
Log data

2022-04-01T13:20:42.300Z backstage info ::ffff:<IP_ADDRESS> - - [01/Apr/2022:13:20:42 +0000] "GET /api/search/query?term=&filters%5Bkind%5D=component&filters%5Bnamespace%5D=default&filters%5Bname%5D=backstage&pageCursor=&types%5B0%5D=techdocs HTTP/1.1" 200 14 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/100.0.4896.60 Safari/537.36" type=incomingRequest
/app/node_modules/@backstage/errors/dist/index.cjs.js:29
    throw new Error(`Encountered error object without a message, got '${value}'`);
          ^

Error: Encountered error object without a message, got 'NoSuchKey: null'
    at Object.assertError (/app/node_modules/@backstage/errors/dist/index.cjs.js:29:11)
    at /app/node_modules/@backstage/plugin-techdocs-node/dist/index.cjs.js:770:18
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

Your Environment
Backstage is deployed in a kubernetes cluster.
Requests:{"cpu":"500m","memory":"2Gi"}
Limits:{"cpu":"8","memory":"2Gi"}

Browser Information:
Google Chrome - Version 100.0.4896.60 (Official Build) (x86_64)

Output of yarn backstage-cli info:

OS:   Darwin 21.1.0 - darwin/x64
node: v14.17.6
yarn: 1.22.17
cli:  0.16.0 (installed)

Dependencies:
  @backstage/app-defaults                            1.0.0
  @backstage/backend-common                          0.13.1
  @backstage/backend-tasks                           0.2.1
  @backstage/catalog-client                          1.0.0
  @backstage/catalog-model                           1.0.0
  @backstage/cli-common                              0.1.8
  @backstage/cli                                     0.16.0
  @backstage/config-loader                           1.0.0
  @backstage/config                                  1.0.0
  @backstage/core-app-api                            1.0.0
  @backstage/core-components                         0.9.2
  @backstage/core-plugin-api                         1.0.0
  @backstage/errors                                  1.0.0
  @backstage/integration-react                       1.0.0
  @backstage/integration                             1.0.0
  @backstage/plugin-api-docs                         0.8.3
  @backstage/plugin-app-backend                      0.3.30
  @backstage/plugin-auth-backend                     0.12.3
  @backstage/plugin-auth-node                        0.1.6
  @backstage/plugin-catalog-backend-module-bitbucket 0.1.1
  @backstage/plugin-catalog-backend-module-ldap      0.4.1
  @backstage/plugin-catalog-backend                  1.0.0
  @backstage/plugin-catalog-common                   1.0.0
  @backstage/plugin-catalog-graph                    0.2.15
  @backstage/plugin-catalog-import                   0.8.6
  @backstage/plugin-catalog-react                    1.0.0
  @backstage/plugin-catalog                          1.0.0
  @backstage/plugin-github-actions                   0.5.3
  @backstage/plugin-org                              0.5.3
  @backstage/plugin-permission-common                0.5.3
  @backstage/plugin-permission-node                  0.5.5
  @backstage/plugin-permission-react                 0.3.4
  @backstage/plugin-proxy-backend                    0.2.24
  @backstage/plugin-scaffolder-backend               1.0.0
  @backstage/plugin-scaffolder-common                1.0.0
  @backstage/plugin-scaffolder                       1.0.0
  @backstage/plugin-search-backend-node              0.5.2
  @backstage/plugin-search-backend                   0.4.8
  @backstage/plugin-search-common                    0.3.2
  @backstage/plugin-search                           0.7.4
  @backstage/plugin-sonarqube                        0.3.3
  @backstage/plugin-tech-radar                       0.5.10
  @backstage/plugin-techdocs-backend                 1.0.0
  @backstage/plugin-techdocs-node                    1.0.0
  @backstage/plugin-techdocs                         1.0.0
  @backstage/plugin-user-settings                    0.4.2
  @backstage/release-manifests                       0.0.2
  @backstage/search-common                           0.3.2
  @backstage/test-utils                              1.0.0
  @backstage/theme                                   0.2.15
  @backstage/types                                   1.0.0
  @backstage/version-bridge                          1.0.0

@idmonkey are you still having this problem?

Yes, this is still a problem for us. We are currently in an Backstage evaluation phase and we've put it on hold until we can fix it.

Hi! @idmonkey - do you see any more warn/debug/error logs after this line Error: Encountered error object without a message, got 'NoSuchKey: null'? Would you be able to post some more log lines before and after?

hi @soapraj,
After this message the container crashes and there are no more logs. Here are some log messages before this happens.
2022-05-10T09:19:00.570Z backstage info ::ffff:<IP_ADDRESS> - - [10/May/2022:09:19:00 +0000] "GET /api/techdocs/sync/default/component/backstage HTTP/1.1" 200 - "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.54 Safari/537.36" type=incomingRequest
2022-05-10T09:19:00.572Z backstage info ::ffff:<IP_ADDRESS> - - [10/May/2022:09:19:00 +0000] "GET /api/techdocs/metadata/entity/default/component/backstage HTTP/1.1" 200 - "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.54 Safari/537.36" type=incomingRequest
2022-05-10T09:19:00.607Z backstage info ::ffff:<IP_ADDRESS> - - [10/May/2022:09:19:00 +0000] "GET /api/techdocs/static/docs/default/component/backstage/index.html HTTP/1.1" 304 - "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.54 Safari/537.36" type=incomingRequest
2022-05-10T09:19:00.715Z backstage info ::ffff:<IP_ADDRESS> - - [10/May/2022:09:19:00 +0000] "GET /api/techdocs/static/docs/default/component/backstage/assets/stylesheets/main.fe0cca5b.min.css HTTP/1.1" 200 - "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.54 Safari/537.36" type=incomingRequest
2022-05-10T09:19:00.730Z search info Search request received: term="", filters={"kind":"component","namespace":"default","name":"backstage"}, types=techdocs, pageCursor= type=plugin
2022-05-10T09:19:00.740Z backstage info ::ffff:<IP_ADDRESS> - - [10/May/2022:09:19:00 +0000] "GET /api/search/query?term=&filters%5Bkind%5D=component&filters%5Bnamespace%5D=default&filters%5Bname%5D=backstage&pageCursor=&types%5B0%5D=techdocs HTTP/1.1" 200 - "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.54 Safari/537.36" type=incomingRequest
/app/node_modules/@backstage/errors/dist/index.cjs.js:29
    throw new Error(`Encountered error object without a message, got '${value}'`);
          ^

Error: Encountered error object without a message, got 'NoSuchKey: null'
    at Object.assertError (/app/node_modules/@backstage/errors/dist/index.cjs.js:29:11)
    at /app/node_modules/@backstage/plugin-techdocs-node/dist/index.cjs.js:770:18
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

@camilaibs are you able to follow on here

I'm seeing the same problem with these versions.
  @backstage/plugin-techdocs-backend                    1.1.2
  @backstage/plugin-techdocs-module-addons-contrib      1.0.1
  @backstage/plugin-techdocs-node                       1.1.2
  @backstage/plugin-techdocs-react                      1.0.1
  @backstage/plugin-techdocs                            1.2.0

It seems that the S3 library is the origin of the NoSuchKey error and maybe it's just not being caught properly.
Here's the try clause from which the 'malformed error' comes:
https://github.com/backstage/backstage/blob/b473f8f8feeda229ec2491d31b3b2176b9e78dd9/plugins/techdocs-node/src/stages/publish/awsS3.ts#L342-L355
And I'm suspecting it's not treated correctly in 'streamToBuffer': https://github.com/backstage/backstage/blob/b473f8f8feeda229ec2491d31b3b2176b9e78dd9/plugins/techdocs-node/src/stages/publish/awsS3.ts#L47-L58
Could it be the on('error', ...) line?

Unfortunately I don't know how to test a fix. I've copied techdocs-node into my plugins/ folder, applied what I think fixes it, but when I run yarn workspace backend start --config ../../dev/app-config.yaml, the build succeeds and then it complains `
/app/plugins/techdocs-node/src/index.ts:23
export * from './stages';
^^^^^^

Ok, I've put both techdocs-node and techdocs-backend in my plugin path and was able to at least cover the "Encountered error with no message", but the container is still dying.

@benjdlambert has this become stale because the fix is already in?

No apologies, I marked this as stale accidentally by the looks of things. Too many tabs open 😱

@camilaibs Another one for your PR review list - if you have time


IE Rendering Issues with Tabs and ContentSwitcher

From the initial report:

I am writing to see if there are any known issues with Internet Explorer and some of the Carbon Components. In our product we use the new Tabs component, and have since not been able to render our UI in IE. Looking through the code it seems Tabs calls on code from content-switcher and evented-state, and becasue evented-state uses the following:

it is not rendered, as CustomEvent is not supported in IE.

I used a polyfill to work around this issue, and although the page would now render properly, all of the tab items were styled as selected and were not linked to anything on a click event.

Just wondering if this is a known problem, or if it is most likely a misuse on our end.

Hey @joshblack this issue was already created, issue #433. Going to close it and track it there.


Made cleanup hook job honor pullSecret settings

Summary
Changed Helm Chart to honor settings for pullSecrets also for the cleanup hook.
Checklist
For Helm Chart changes

[x] Categorize the PR by setting a good title and adding one of the labels:
bug, enhancement, documentation, change, breaking, dependency
as they show up in the changelog
[x] PR contains the label area:chart
[x] PR contains the chart label, e.g. chart:k8up
[ ] Variables are documented in the values.yaml using the format required by Helm-Docs.
[x] Chart Version bumped if immediate release after merging is planned
[ ] I have run make chart-docs
[ ] Link this PR to related code release or other issues.

Hi @albimn
Could you please fix the DCO?


x/vuln: delay reporting vulnerabilities for N days

Once a new Go bugfix is released govulncheck will start to report issues from the standard library if security flaws were fixed in the latest bugfix. This causes a lot of failed builds across a fleet of CI jobs because the underlying machine may not have been upgraded yet. Failing builds for an issue that teams will address but haven't had time to solve yet causes frustration and pushes teams to silence warnings or rush through upgrades.
One option would be to delay reports for a time.Duration value. This would let teams upgrade dependencies and Go versions before seeing failures.
I'm proposing that the govulncheck command accepts a -stability-days N flag where N is a value parsable by time.ParseDuration. The check could read a vulnerabilities published field in the OSV format and use the machines local time for comparison.
Prior art: https://docs.renovatebot.com/configuration-options/#stabilitydays

I opened https://go-review.googlesource.com/c/vuln/+/442497 to see how this would look in the code. I'm open to a different name if the flag is accepted.

Thanks for reporting this, we are currently looking into this. One question, is this problem mostly tied to std vulnerabilities or do you expect similar issues with third party modules as well?

The solution for this issue falls under a more general umbrella of suppression mechanisms for govulncheck. We believe that is a better fit for this issue compared to adding a rather specific flag. We are actively exploring options in this space, but we don't have a timeline or decision yet.
One way to solve this problem is to analyze JSON output and then filter vulnerabilities. OSV entries have the necessary information for this. As a matter of fact, we are actively developing new JSON output that would simplify this.

Is this proposal still something which could be added to govulncheck? On minor releases of Go many CI systems run into immediate errors (detecting valid CVE's) but are unable to resolve them until meta-infra is updated. Right now a PR to actions/setup-go is blocking successful builds for many projects, but offering a delay would let the meta-infra be updated.

We are currently being affected by this, all our CI pipelines are failing because  govulncheck, golang releases, actions/go, actions/setup-go are not synched.
Rel: https://github.com/actions/setup-go/issues/405

an option to consider is providing a way to limit the vulnerabilities to releases, not prereleases.

1.20.7 was released, it's just it takes a couple of days for image and action providers to update, meanwhile normal CI/PR/MR start failing with no recourse (than disabling govulncheck)

We are currently being affected by this, all our CI pipelines are failing because govulncheck, golang releases, actions/go, actions/setup-go are not synched.
Rel: actions/setup-go#405

I am not sure what is the concrete issue in your case, but did you take a look at govulncheck-action? You can specify which Go version to use (with another option on the way).

While a general suppression mechanism would be ideal, it seems that most of the issues described here would go away with suppression for Go vulnerabilities. Is that fair to say?
If so, could an acceptable solution be part of govulncheck-action?

we had the same issue, so we updated our pipelines to find the latest (acceptable) go release version and pass that to actions/setup-go.

We addressed the problem of recently released stdlib updates (from new Go releases) causing builds to fail by using setup-go with go-version: stable and installing govulncheck in each CI build. This ensures the project and govulncheck are on the same Go release (which can be the new or old based on cache) and avoids this error. stable checks for the latest Go release anyway.

Thanks for the prompt answers.
If it means anything,  govulncheck-action should also install govulncheck on each CI build and it can be passed the Go version of choice.


[AutoPR servicefabricmesh/resource-manager] Swagger specification and examples for Service Fabric Mesh 2018-09-01-preview release.

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/4292

Codecov Report

Merging #3660 into restapi_auto_servicefabricmesh/resource-manager will decrease coverage by <.01%.
The diff coverage is n/a.

@@                                 Coverage Diff                                 @@
##           restapi_auto_servicefabricmesh/resource-manager    #3660      +/-   ##
===================================================================================
- Coverage                                            37.41%   37.41%   -0.01%
===================================================================================
  Files                                                 9242     9240       -2
  Lines                                               278199   278197       -2
===================================================================================
- Hits                                                104092   104090       -2
  Misses                                              174107   174107

Impacted Files
Coverage Δ

...-language-luis/azure/cognitiveservices/__init__.py

azure-mgmt-advisor/azure/mgmt/__init__.py

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 ce09935...bde4441. Read the comment docs.

(message created by the CI based on PR content)

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/3670


Automate Wheel Builds for multi-operating systems, including c++ keras-retinanet.

Goal: An automated tool that builds both DeepForest and keras-retinanet into a single pypi wheel for each operating system. Separate builds for osx, linux and windows.
Current Status: OSX wheel is built on travis for DeepForest. User needs to pip install keras-retinanet from github and have valid c++ compiler on path for the Cython code. This makes it hard for windows users (
#56).
Resources being investigated:

Azure build pipelines: https://iscinumpy.gitlab.io/post/azure-devops-python-wheels/
we have Microsoft $, so cost is not an issue here.

https://github.com/joerick/cibuildwheel . Not immediately obvious if c++ are built across operating systems.  Not encouraged by this thread here: https://travis-ci.community/t/python-support-on-windows/241

Additional thoughts: The keras-retinanet fork and the DeepForest repo are currently separate. I do not see pulling from keras-retinanet upstream. So I am open to the idea of copying the source and having both packages in the same repo. This is more of an organizational change, it doesn't help much with the above challenges (but would address #41).
@ethanwhite @henrykironde

Its really looking like travis build pushes to pypi are only linux and mac. Reading more about azure services https://medium.com/raa-labs/creating-a-pipeline-in-azure-devops-to-build-and-publish-python-packages-artifacts-ea2f99410e6c

[ ] Add Fia - tree - plot - cond join
Includes filtering duplicate row values from required columns
Includes adding tests for expected query statement.

wrong issue there Henry?
On Wed, Jan 8, 2020 at 11:40 AM henry senyondo<EMAIL_ADDRESS>wrote:

Add Fia - tree - plot - cond join
Includes filtering duplicate row values from required columns
Includes adding tests for expected query statement.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/weecology/DeepForest/issues/60?email_source=notifications&email_token=AAJHBLCGX4M236LI6DJMP7DQ4YT4RA5CNFSM4KC7IRG2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEINXLYY#issuecomment-572224995,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJHBLG55TTWV6E45LFWSGDQ4YT4RANCNFSM4KC7IRGQ
.

--
Ben Weinstein, Ph.D.
Postdoctoral Fellow
University of Florida
http://benweinstein.weebly.com/

my update on pypi builds trigged on master build on azure pipeline

[ x] source distributions
[ x] OSX python 3.7
[ ] many_linux (needed?)
[ ] windows (priority)

complete.
https://pypi.org/project/deepforest/#files
uploaded! need to check if the pipeline gets the source distribution as well. Needs to be checked on azure instances tomorrow. If so, can close.

Checked on azure machine for windows and locally on osx, looks great. see #56


Pre-trained model for KIT dataset

Hello, thank you for your influential work. How can I download the pretrained model for KIT dataset?

Sorry, we probably won't release the pre-trained model on KIT. However, it should be easy to train the OmniControl on KIT as this dataset is relatively small.


merge from arlac77/npm-package-template

package.json

chore(scripts): cover@#overwrite c8 -x 'tests/**/*' --temp-directory build/tmp ava && c8 report -r lcov -o build/coverage --temp-directory build/tmp
chore(package): set $.ava.require='esm' as in template
chore(package): set $.ava.files='tests/*-test.mjs' as in template
chore(package): set $.ava.extensions='mjs' as in template

Coverage remained the same at 98.4% when pulling c06c60a6c7688e574daf5ee10326d4a2745ae425 on npm-template-sync/1 into 3ba221f7da5a7bd60360aa2d37df5b9f18efb57c on master.

:tada: This PR is included in version 2.1.13 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Updates flasher to work with the newer firmware interfaces

What does this PR do

A few fixes for flasher install
Update component search to return BIOS, BMC components regardless of vendor, model match
Pins bmclib to the provider that is applicable for the target hardware under firmware install, earlier  the bmclib behaviour was less deterministic, and would try PowerStateGet() over redfish, FirmwareInstallStatus over vendorAPI and so on - this would result in various incorrect assumptions about the redfish/vendor API sessions being active.
Fixes up the pollFirmwareTaskStatue method to handle a few more edge cases when a BMC resets itself.
Switch to newer bmclib interface methods

Depends on https://github.com/bmc-toolbox/bmclib/pull/372 and its parents.
Tested on Dells, SMCs X11, X12s.

rebase on main


Feature request: Allow aborting of finished-level dialog

First: I love your app :heart_eyes:
When playing I often want to experiment and try out different solutions, and therefore it would be nice if the reset command would abort the dialog about finishing the level, and let you skip the animations.
I think reset is intuitive, but anything that lets me reset the level after finishing it, in a quick manner, without taking my hands of the keyboard would be great.

Hey @nicolaiskogheim, thats actually a great suggestion! That's a workflow I haven't really considered but having the constant level solved animations (which are quite length) and dialog must get tiring.
It'd be easy to simply remember if you have reset after a level solution and then skip the dialog / animation in this case (since we use the same instances across resets). I'll hack this in real quick -- it will clear when you change levels though.
I had the command prompt echo out Level solved just so you have some kind of recognition when you reach the final state (otherwise its a bit confusing). let me know what you think!
(also btdubs -- you can use Esc to quit dialogs which wouldnt involve taking your hands off the keyboard)

(also sorry for the delay -- was on PTO for a while and only got back to the grind now)


[L2-UX] Default history tab

What it solves
Resolves #2780
How this PR fixes it
Enhancement to reflect the Transaction tabs in the urls /transactions/history and /transactions/queue
How to test it
Open the Transactions page and you shall land in the Tx history url.
When one finished a transaction, one is redirected to the Tx Queue url.
Screenshots

Looks good to me.
Also it redirects from the history tab to the queue tab when you create a tx


Handle missing carousel organism on home page

This commit fixes a bug with the prototype carousel created for a new home page design. When running the current production home page, there's no carousel element, so this causes a JS console error.
This change handles the case where there is no carousel organism, while still properly handling the case when there is one.
@contolini
Testing
To test: gulp clean && gulp build, visit http://localhost:8000.
Checklist

[x] PR has an informative and human-readable title
[x] Changes are limited to a single goal (no scope creep)
[x] Code can be automatically merged (no conflicts)
[x] Code follows the standards laid out in the CFPB development guidelines
[x] Passes all existing automated tests
[ ] Any change in functionality is tested
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged / future todos are captured in comments
[ ] Visually tested in supported browsers and devices (see checklist below :point_down:)
[ ] Project documentation has been updated
[x] Reviewers requested with the Reviewers tool :arrow_right:

Long term we'll have it as on-demand attached to a block in Wagtail and the check won't be necessary at that point, right?

Long term we'll have it as on-demand attached to a block in Wagtail and the check won't be necessary at that point, right?

Yeah, when you have a Wagtail block for it, the JS file can be set as the block's Meta media.


Istiod performance impact because of headless service

Wanted some information on istiod performance impact if we want to support statefulsets having 500 - 1000 pods behind the headless service. During performance benchmark, we observed almost twice CPU utilization of istiod pods in case of headless service with 1000 pods vs clusterIP service with 1000 pods.
Please let us know information on below queries:

Is there any official performance benchmark result published for headless services
As per the documentation for PILOT_ENABLE_HEADLESS_SERVICE_POD_LISTENERS, it is mentioned to disable this flag if headless service has large number of pods. What is this large number? Since after we have enabled it at global level, we would not be able to disable it if some use case start using istio with statefulset.
With an increase in number of pods behind the headless service (~ 500 - 1000), would increasing istiod replicas / resources help?

I would check data plane performance carefully, because this will create a lot of listeners..

This is generally expected. We are not well optimized for many pods in a headless service unfortunately. Improving this would likely require changes in envoy

Will increasing number of replicas or increasing capacity of istiod help in this case? Also, how many number of pods could be supported with PILOT_ENABLE_HEADLESS_SERVICE_POD_LISTENERS  flag enabled?
Is there any official benchmarking numbers or recommendations?

this will add more configuration (listener) to envoy proxy, I don't think adding more resource to istiod can help. btw, I also think the envoy proxy memory usage would be increased, do you find that?

Sure, I meant for controlplane impact if increasing istiod resource/replica help.
For sidecar impact, we'll check


Better highlight rows with failed txns

Currently only txn hash badge is highlighted in different color which is not really distinguishable in different themes we support. Better highlight whole table rows for more visibility.

Done.


Use main_process_first in examples

Adds usage of main_process_first when calling map() in the examples

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Re-Defining the website

Redefine the whole website using contributed components and andding new ones so that website looks better.

@vaishnavi-3969  I have one request
please accept. #24
he is known to me and have put efforts in it.

@vaishnavi-3969 I have one request please accept. #24 he is known to me and have put efforts in it.

If any ui improvement after the merging of request would be done by me.

Yes yes I was doing that only just didn't got time yesterday to resolve
conflicts and then I'll merge for sure
[image: Mailtrack]
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality11&
Sender
notified by
Mailtrack
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality11&
05/10/23,
18:52:50
On Thu, Oct 5, 2023 at 6:44 PM Ankit Kumar Shah @.***>
wrote:

@vaishnavi-3969 https://github.com/vaishnavi-3969 I have one request
please accept. #24
https://github.com/vaishnavi-3969/Web-Componentify/pull/24 he is known
to me and have put efforts in it.
If any ui improvement after the merging of request would be done by me.
—
Reply to this email directly, view it on GitHub
https://github.com/vaishnavi-3969/Web-Componentify/issues/26#issuecomment-1748876191,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATDA2UZNKD7JLID463G3QE3X52XEJAVCNFSM6AAAAAA5TVFUCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBYHA3TMMJZGE
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Vaishnavi Kale
Student
@.***
https://twitter.com/vaishnavi_k3969
https://www.linkedin.com/in/vaishnavi-kale-111543204/
https://www.youtube.com/channel/UC5Xu78KKvRR5DYHy8k9X1Hg
https://github.com/vaishnavi-3969
Please consider the environment before printing this mail

Yes yes I was doing that only just didn't got time yesterday to resolve conflicts and then I'll merge for sure [image: Mailtrack] https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality11& Sender notified by Mailtrack https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality11& 05/10/23, 18:52:50
…
On Thu, Oct 5, 2023 at 6:44 PM Ankit Kumar Shah @.> wrote: @vaishnavi-3969 https://github.com/vaishnavi-3969 I have one request please accept. #24 <#24> he is known to me and have put efforts in it. If any ui improvement after the merging of request would be done by me. — Reply to this email directly, view it on GitHub <#26 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATDA2UZNKD7JLID463G3QE3X52XEJAVCNFSM6AAAAAA5TVFUCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBYHA3TMMJZGE . You are receiving this because you were mentioned.Message ID: @.>
-- Vaishnavi Kale Student @.*** https://twitter.com/vaishnavi_k3969 https://www.linkedin.com/in/vaishnavi-kale-111543204/ https://www.youtube.com/channel/UC5Xu78KKvRR5DYHy8k9X1Hg https://github.com/vaishnavi-3969 Please consider the environment before printing this mail

Thank you


Support for compressed sRGB formats

Both WebGL and WebGPU supports sRGB version of compressed texture formats
compressed texture formats are used when the asset has { srgb = true; } option, similarly to non-compressed formats
glb parser requests srgb texture formats for base and emissive color textures, as those are stored in sRGB space

partially implements https://github.com/playcanvas/engine/issues/3715

By the way, is there a decode function for 4 component vectors? I remember we needed a texture with alpha channel, but seems $DECODE variants are only for vec3.

We don't have one as transparency is in linear space. But I guess if you store other data in the alpha channel (say a greyscale color), you might need to use a custom decode function.

Right, custom data. Alright, thanks.


Fix linting in cmd, config, utils, cli, version & main

Fix linting issues in metadata/cmd, metadata/utils, metadata/cli, metadata/version and metadata/main

yes we set this aside and started tackling other priorities. We should indeed close this on the next release cc @nahuelverdugo


Added array of dictionary support.

This allows to store an array of dictionaries. It can be used like this:
public extension DefaultsKeys {
    public static let categories = DefaultsKey<[[String: AnyObject]]>("categories")
}

// get value
guard let value = Defaults[.categories][3]["title"] as? String else { return }
print("Forth category title: \(value)") // Health

// set value
Defaults[.categories][3]["title"] = "Health and Fitness"

To put things into perspective, the structure looks something like this:

Dictionary support was removed in 4.0.0-alpha.1 as a part of removing legacy APIs - please use the power of types instead 🧡


Immediately active new screen when opening

Change-Id: If0f8a1faa3230e7116400d8e8c8ea1c48ed55220

The relevant community post is here: https://community.appinventor.mit.edu/t/after-screen2-initialize-nothing-is-displayed/79455?u=ewpatton
There appears to be a race condition in how quickly iOS can switch screens and when the code is sent from the web editor. This change makes the new screen active just before sending a message via the RetValManager to ensure that it is active for when the code arrives.

Maybe I'm doing something wrong in my testing but this PR didn't help fixing the bug that was explained in the community site. Funny thing is, when I input nothing for heights and weights I get something in Screen2 but when I input some numbers (e.g., height 175, weight 70) Screen2 is just blank

@daki7711 So there were some other interactions that needed to be fixed. In particular, in the particular app in question if the user is editing the text and then clicks calculate, the LostFocus event fires on the TextBox, which resets the active form to the old screen (which then receives the Screen2 code). However, if you're not editing the text when clicking the button, there isn't a post transition event involved so my first iteration of the fix worked. The PR has been updated with the additional logic.


i2s support?

I'm currently considering using rust for my next ESP32 project. I would like to use IDF and std, so I was looking at this HAL (as opposed to https://github.com/esp-rs/esp-hal).
However, I can only find references to i2s in the no-std HAL, not in this HAL. As this is something I need for my next project, I'm curious why this is? Is it just not implemented (yet)?

It is not implemented yet. You can be the first to implement it!

I had some working things in here https://github.com/esp-rs/esp-idf-hal/compare/master...maximeborges:esp-idf-hal:feature/i2s-impl based on my fork of embedded-hal https://github.com/rust-embedded/embedded-hal/compare/master...maximeborges:embedded-hal:feature/sai, but I'm on way too many projects at the moment and this one is not high in the priority list currently.
If you want to take over or just get some of my stuff working, you can ping me

I might look at this a bit later during the year, my hobby project where I need this probably won't happen before the summer at least.

I've been looking into some of this recently; I've been hacking on an epaper display that uses parallel I2S on the ESP32 (mainly used for LCDs and cameras). The example C code they provide uses private 4.x APIs like periph_module_enable and the multiplexing GPIO functionality via gpio_matrix_out.
The gory details (at least for ESP32) at in section 12.5 of the ESP32 Technical Reference Manual[PDF] discussing LCD and camera interfacing.
The I2S system was redesigned in the 5.0 release, but seems to have omitted support for this kind of functionality: the struct defining the I2S setup can only deal with a single GPIO for input or output.
I'm curious how many others this affects. Obviously it's critical for me to have the parallel support (the 5.x C driver is unusable for this board); but I wouldn't waste the effort trying to make my driver more generic than it needs to be if nobody else needs it.

I'm curious how many others this affects. Obviously it's critical for me to have the parallel support (the 5.x C driver is unusable for this board); but I wouldn't waste the effort trying to make my driver more generic than it needs to be if nobody else needs it.

My plan is to use i2s for sound (microphone as well as speaker), so I would not need this sort of functionality.

I am currently working on this, initially targeting compatibility with the ESP-IDF v5.0 driver.

At this point, my fork has support for standard mode, but I have yet to test it. I will be assembling a test jig to do some verification this weekend.
@ivmarkov, you might know the answer to this question. There are a few 5.0 headers that aren't being bindgen-ed in esp-idf-sys, so I'm having to pass
[[package.metadata.esp-idf-sys.extra_components]]
bindings_header = "bindings.h"

in esp-idf-hal's Cargo.toml, with this bindings.h header. This is probably not ideal. I'm assuming I need to do this directly in esp-idf-sys's bindings.h, but I'm not sure where the preprocessor defines (e.g. ESP_IDF_COMP_SOC_ENABLED) come from. They don't look like Kconfigs, and both Google and grep are failing me here...

Additional fixes have been pushed to my branch. There is test code available over in my test-esp-sound repository.

@dacut I need the i2s functionality too in the meantime, so I'm willing to work on merging your code - if you open a PR.
The code looks to be in a quite good state already, but changes most likely will be necessary, so if you open a PR, we can discuss there.
Some initial thoughts by only quickly looking at the driver code: your treatment of i2s pins seems not to be compatible with how the other drivers treat pins - unless I'm missing something, I can't pass a & 'd mut ref to a pin peripheral in the driver and have the pin peripheral available once the driver is dropped. We might also need to fix how the RX callback is passed to the driver. While using & dyn is a definite improvement compared to how other drivers do it, passing a *mut raw pointer reference makes the whole function unsafe due to lifetime annotations missing, and the fn is not marked as unsafe. Yet, by life-timing the dyn reference we might be able to fix it.
But as I said - by PR-ing the driver we might have more fruitful conversation, with references in the code, etc.

Hi @imarkov,
It’s not quite ready for review yet, so I was hesitant to open a PR, but will do so in a draft state when I get a chance over the next couple days or so. As you note, there are a few things in there that aren’t right (like the *mut for a callback), because I found I had coded myself into a corner earlier.
Didn’t mean for this to be the end-all-be-all.
Also have more hardware on the way to fix up my test bed for verification.
Thanks!

Life got a bit busy with some family health issues and travel over the last couple weeks, but for those following along, I've now created a PR over here: https://github.com/esp-rs/esp-idf-hal/pull/232

https://github.com/esp-rs/esp-idf-hal/pull/232 and its cleanup PR, https://github.com/esp-rs/esp-idf-hal/pull/269, have been merged. Go drop some beats!
@ivmarkov, this issue can be closed.

#232 and its cleanup PR, #269, have been merged. Go drop some beats!

After your nice work here, we are all interested in your uber project that is utilizing the driver so we can use it as an example :smile_cat:

@vollbrecht My journey here started with trying to get this e-paper display running with a Rust backend. However, this device uses a strange I2S mode, parallel I2S, that isn't well documented (and I've not seen how to port this to the 5.x SDK yet). You can see how someone else wrote a C/C++ driver for this, and the C existing demo code relies on the 4.4 SDK.


Swap out text encoding package

I did a test in IE11 and it seemed to work. But I couldn't get npm link to work properly so I just did a direct import from "./path" for the test. You might wanna do your own testing before publishing. Seems to push down the package size quite a bit.
Cheers!

The project has a simple example you can spin up and run in IE11, rather than having to npm link into another example. I'll give that a whirl before merging.

Oh cool yeah I saw that example and didn't even think to try it. Cheers!


net/http: set LocalAddrContextKey after conn accepted

From comment on closed issue: https://github.com/golang/go/issues/6732#issuecomment-273164492
The http server sets LocalAddrContextKey in Serve(Listener) before any accept.
So if you pass a Listener listening on <IP_ADDRESS>, that is what LocalAddrContextKey will say also. The current implementation considered only the case of distinguishing between multiple explicit listeners, not distinguishing the addresses arriving on a wildcard interface.
Instead, we should set the context value after an accept takes place.
/cc @SpComb

#18734 is not a  duplicate since it's a special case and socket which this address is always changing du to the diffrent connections that is being intercepted by the proxy.
It's not static but dynamic for a tproxy socker and a server.

Since someone has already provided a CL for this, should the HelpWanted label be removed?

@gopherbot @bradfitz I didn't understood the changes mentioned by the bot.

Why it planned to go 1.9 instead go 1.8.1? I think it is very small change - small fix small bug, no language change.
I need local ip too for https://github.com/rekby/lets-proxy
Now I have forked http package to own copy for workaround the problem and wait solve in standard library.

Because we only fix critical bugs/regressions without workarounds in 1.x.y point releases.

I don't know what the protocol for closed issues is, but shouldn't this be reflected in the patch notes?
I just encountered a Connection Local Addr and not the previous Listener Addr using r.Context().Value(http.LocalAddrContextKey)

@sabey so, is it working? is there a solution?

it does work, the change was just unexpected as I couldn't find the documentation for it


Allow current user to join os/osd group during deb/rpm test

Description
Allow current user to join os/osd group during deb/rpm test
Issues Resolved
https://github.com/opensearch-project/opensearch-build/issues/3815
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

https://build.ci.opensearch.org/job/docker-build/5061/console

https://build.ci.opensearch.org/job/docker-copy/1062/console
https://build.ci.opensearch.org/job/docker-copy/1063/console
https://build.ci.opensearch.org/job/docker-copy/1064/console


Custom working directory for any tool

As part of #653:
I'd should be possible to pass a custom working directory to any tool.
E.g. Specify another working directory for NUnit3 task. So far I couldn't find any option to pass that to the custom tool. By now I do it like that:
var previousCurrentDir = System.IO.Directory.GetCurrentDirectory();
Environment.CurrentDirectory = "path\to\bin";
try
{
    NUnit3("path\to\bin\*UnitTest.dll", settings);
}
finally
{
    Environment.CurrentDirectory =  previousCurrentDir;
}

I suggest adding a property WorkingDirectory to ToolSettings (http://www.cakebuild.net/api/cake.core.tooling/d75cd243)

Duplicate of  #844 - closing

There is a WorkingDirectory property of the ToolSettings base class that does this.

@patriksvensson Thanks


Package container-interop is abandoned

Did a fresh install of a project with zend-soap, which requires zend-eventmanager, which requires container-interop/container-interop.
Composer is throwing the following warning:
Package container-interop/container-interop is abandoned, you should avoid using it. Use psr/container instead.

This is due to container-interop marking their packages as abandoned.
Please note that "abandoned" does not mean "uninstallable". It means that there will be no future updates to the package. Which makes perfect sense here, as PSR-11 was ratified, superceding it.
Unfortunately, updating the various ZF packages requires updating zend-servicemanager, and we cannot change it until its next major version, as doing so now would be a BC break. While the interfaces are equivalent, and container-interop versions we pin to extend PSR-11, the problem is that the inheritance trees would break.
We are definitely aware of the issue (I myself voted for container-interop to deprecate and abandon its packages), but please be aware that (a) we know about the issue, and will resolve it eventually, and (b) it will not affect your application installs, and you can continue using the packages normally.


[doc-bug][Landing-page-link]

link check

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/mstdd-landing.yml
90
1
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 92dcb69:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/mstdd-landing.yml
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit b30f73b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/mstdd-landing.yml
:white_check_mark:Succeeded
View

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


Mix plugin from Oh-my-Zsh not working

mix is the build tool of the Elixir programming language.
The mix plugin from oh-my-zsh doesn't seem to work in zplug. I tried zplug "plugins/mix" from:oh-my-zsh.
Do I have to specify an of option, like I had to do for rupa/z? In general, when is the of option necessary? I think the README/wiki could use some further explaination on this.
Thanks for the alreday gret tool! :clap:

Thank you for your report!
I will try to check up on that. Wait a moment please...

Incidentally, of tag is useful in such a case:

When you specify relative path except for project root e.g., git-slides zplug "gelisam/git-slides", of:bin, as:command
When you specify command name which differs from project name e.g., zsh-gomi zplug "b4b4r07/zsh-gomi", of:bin/gomi, as:command

Fixed! I am not familiar with oh-my-zsh, your detailed report will help me. Thank you VERY much!! :smiley:

Too good to be true! :crown:


Put build.sh to same directory where sources are

Current location:
ADD build.sh /src/scripts/
Better location could be /src/(target)
Or does this just add complexity to dockerfile?

Maybe it's not a good idea because it adds complexity of dockerfile so closing this.


User component

@roschaefer: Here’s what I changed:

The component doesn’t show the full email address/user name any more, instead, it shows only icons indicating which communication channels are active for a given user. I moved the logic to determine which channels are active to the User model and to the component class.
I updated the icon component so you can easily use icons inline.


JS: remove cookie source; rely on persistent flow steps instead

As discussed, we should start to treat cookies as persistent storage flow steps (https://github.com/Semmle/ql/pull/629) instead of treating client-side cookie access as remote flow.
Evaluation.

You're right, I was way too quick to just accept the changes as they were. I've force-pushed some udpated tests. PTAL.


OpenShift Pipeline

Adds support for OpenShift pipeline builds, which gives us a bit more flexibility in the build process and produces cleaner results than an S2I image.
Also added a quick test that will check to make sure the generated HTML is valid and all external URLs resolve at build time.

The OpenShift project is already set up to build with this - we'll just need to flip a few bits to point it at this repo once this PR is merged.


Fixed some typos in iteration error messages

In some errors, there were closing quotation marks but no opening ones.
Example:
"Unable to iterate on object of type  SomeType'."
Just a minor adjustment, but this confused me several times now because I started looking for the first mark.

Thanks!

You're welcome 😊


Insights details update

Updates the Insights dashboard logic

Collect the entire CRAM analysis entry for each sequencing group, not just TRUE/FALSE for CRAM existence
Display the date the CRAM analysis was created from the timestamp, not just TRUE/FALSE
Collect analysis outputs by joining to analysis_outputs and output_file tables and coalescing the output fields
Sort the values that can be filtered for each column when they are displayed to the user
Update the Project and Sequencing type selection to use a dropdown list for better UX

@nevoodoo thanks for the review. For the SQL - I agree that having raw SQL in this layer module sticks out because the rest of the db layer modules avoid this. I guess this is because the SQL here is used to create a view by combining the results from a number of queries from a number of different tables.
If the SQL were to be moved into the tables modules, the various functions would probably be distributed into both the sequencing_group the analysis table modules. But most of the queries are quite specific to the project insights dashboards, so it could get confusing.
Maybe there could be a new module "views" or something where these kinds of queries could be saved, like:
metamist/db/python/tables/views/project_insights.py

Moving the SQL out of the layer module would make things a lot nicer and would also mean that some of the mypy/pylint disable comments can be removed.
Let's earmark this in an issue for a future PR and just get this one merged for now to fix the dashboard.


Add quantile regression support

Pull Request
Description
Add option to train PVNet with quantile regression. An example training run using these new changes is hosted on wandb. Figure at bottom shows some results from the validation set.
These changes are:

Add quantile loss as a loss function to minimise on, whilst still tracking MAE/MSE of the 0.5 quantile
Add plotting functionality to plot all predicted quantiles if used
Modify configs and training script to choose correct metric to monitor for early stopping and checkpointing
Add tests for quantile regression option in model

Checklist:

[x] My code follows OCF's coding style guidelines
[x] I have performed a self-review of my own code
[x] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have checked my code and corrected any misspellings

Amazing, well done for doing this!!!!
Do you fancy upgradeing to nowcasint_datamodel=1.4.14. and then in yourconvert anding a properties' field.  This field should be a dictionary like   forecast_value_sql.properties = {'plevel_10':forecast_value.plevel_10, 'plevel_90':forecast_value.plevel_90}

Amazing, well done for doing this!!!!
Do you fancy upgradeing to nowcasint_datamodel=1.4.14. and then in yourconvert anding a properties' field. This field should be a dictionary like forecast_value_sql.properties = {'plevel_10':forecast_value.plevel_10, 'plevel_90':forecast_value.plevel_90}

@peterdudfield I was updating these libraries in a separate issue #45.  I'll work on this after that pull request is merged to main and then merge it into this.

Also have you added stuff to the PVnet public document? WOuld great to get a sense of how the MAE has changed? and how good the quantiles are?

@peterdudfield I haven't yet, but can do. At least the wandb run linked above shows the MAEs. In short the MAE for this model trained on quantile loss is the same as when the model is trained only to predict MAE. The get identical scores (allowing for some jitter in the training/validation curves).

@peterdudfield Also, this isn't quite a full solution yet since we don't have a way to sum the quantiles to get a probabilistic forecast for the national sum.
For example, if could sum all of the 10th percentile lines from all GSPs, and all the 90th percentile lines, and use this for the range for the PVNet national estimate. However, we'd end up with to large of a 10-90th percentile range for the national sum. This option would essentially to assume that the prediction errors will all be perfectly correlated.
Alternatively, we might be able to do something similar to adding the uncertainties in quadrature. But this assumes that the errors in the prediction are perfectly uncorrelated, and so we'd end up with a 10-90th percentile range which is too small.
The reality is likely to be somewhere in the middle of these two, which partial correlation of errors. I think the best option might be to train another very small model to estimate the quantiles of the national sum from the output of this model

@peterdudfield Also, this isn't quite a full solution yet since we don't have a way to sum the quantiles to get a probabilistic forecast for the national sum.
For example, if could sum all of the 10th percentile lines from all GSPs, and all the 90th percentile lines, and use this for the range for the PVNet national estimate. However, we'd end up with to large of a 10-90th percentile range for the national sum. This option would essentially to assume that the prediction errors will all be perfectly correlated.
Alternatively, we might be able to do something similar to adding the uncertainties in quadrature. But this assumes that the errors in the prediction are perfectly uncorrelated, and so we'd end up with a 10-90th percentile range which is too small.
The reality is likely to be somewhere in the middle of these two, which partial correlation of errors. I think the best option might be to train another very small model to estimate the quantiles of the national sum from the output of this model

Yea, perhaps before training a model, could first do some analysis on how they are correlated?

@dantravers might actually know this.
the problem is how to add up GSP uncertainites to make the national one. Assuming normal distributions

If uncorreclated, can square them and sum, then square root
if correctted, can just up them up.

one way to perhaps do it would be to do a mixture of 1. and 2. and see what is best.
As you suggested @dfulu could do a seperatel model and train this, but perhaps a simple way first is a good start

@peterdudfield  it will take a bit of time to do the analysis. The biggest component of this is preparing the input dataset since it takes 317 samples at the same timestamp to give us 1 data point for the correlations or to train a model. I'll start working on this on a separate branch

On adding up the uncertainties:
Well - as luck should have it, I was just talking about this!  I think the right thing to do is:
Create a correlation matrix C, where each C_i_j is the correlation of the timeseries GSPerror_i, and GSPerror_j, where i, j are the index of the GSP (from 1 to n). C is nxn, where there are n GSPs.
GSPerror timeseries is formed by working out the forecast minus the actual for the GSP for all historical periods we have (for the horizon we are looking at).  We could create this based on some backetst / cross validation period.   (I've actually calculated this for many sites in GSPs in my PhD stuff, but there are some gaps in sites, so it would be better to do for all GSPs with the same model I think. )
Then the (median-quantile) (for each up and down quantile) would be Q@C@Qt, where Q is the nx1 vector of (median-quantile level) for each GSP, Qt is Q transpose, and @ is dot product.

To keep this up date with conversations in person. I think @dantravers's idea is a pretty good approximation. However, I think its would be almost the same amount of work to go to what feels like a "full" solution of training a model on all of the GSP predictions to estimate the quantiles. That is the current goal

Is it worth adding a test, to check the probablsitic works?


Upload files while creating pull request

While creating pull requests it will be great if uploading file functionality is provided
Drag n drop will be cherry on the cake
Extension version:
OS: Mac
Steps to Reproduce:
Try to create a new PR
Try to add any file in description
https://github.com/microsoft/vscode-pull-request-github/assets/107181894/0b37972a-d3fc-4527-9147-099b25305bca

I would love to add this, but sadly GitHub's API does not provide a way to do this. Duplicate of https://github.com/microsoft/vscode-pull-request-github/issues/320


add github action for gitvalidation

since we axed travis, we need to carry over the steps it was [attempting] to do
  - echo "${TRAVIS_COMMIT_RANGE} -> ${TRAVIS_COMMIT_RANGE/.../..} (travis-ci/travis-ci#4596)"
  - TRAVIS_COMMIT_RANGE="${TRAVIS_COMMIT_RANGE/.../..}" make .gitvalidation
  - make docs conformance

Like @vsoch did here https://github.com/opencontainers/image-spec/blob/f18daf27c37a3e5e5f79e0d17ebcc051d8a34775/.github/workflows/docs-and-linting.yml#L39

SGTM


What speak agains using a passed monaco instance like in emmetHTML from 'emmet-monaco-es'

basically im asking to revert:
https://github.com/remcohaszing/monaco-tailwindcss/commit/c0a98fa36c5826e0011cc5efd2d32fe8688f5304
i had this build problem once that i included monaco two times - i had it fixed but now its there again (probably because im using it via file:../../ and the node_modules are bugged or something) -> but why not handle it like  emmetHTML from 'emmet-monaco-es'
https://github.com/troy351/emmet-monaco-es#esm
the do it like:
emmetHTML(monaco, ['html', 'php'])
they pass a complete monaco instance which will be used to handle everyting, it even has the advantage that one can use monaco from a cdn and pass window.monaco
what do you think?
developing via file:../../../../../monaco-tailwindcss is sometimes a pain as monaco is often bundled twice

btw by monaco i mean: import * as monaco from 'monaco-editor' or import type * as Monaco from 'monaco-editor'

Yes, I understand. :)
I think it’s a good idea. I’ve updated monaco-worker-manager to support this.

my current workaround was to use rm -rf ./node_modules/monaco-tailwindcss/node_modules/monaco-editor sometime (when linking from local via file: in yarn)
or using:
onResolve({ filter: /^monaco-editor$/ }, () => ({
    path: fileURLToPath(new URL('./node_modules/monaco-editor/esm/vs/editor/editor.main.js', import.meta.url))
}));
onResolve({ filter: /^monaco-editor\/.*$/ }, ({ path }) => ({
    path: fileURLToPath(new URL('./node_modules/' + path, import.meta.url))
}));

nice thanks for updating that (reference https://github.com/remcohaszing/monaco-worker-manager/commit/8901950e03735fcea8d83a55e16b30e3dc1d8e75)


debug mode

Hello,
I think it would be better if you use something else like playOnAllBrowser or something because its causing issue for us while we are testing the flowplayer on safari and microsoft edge
                if (hlsconf.debug) {
                    return true;
                }

thanks

@k1ng440, why is this causing an issue? While you're testing you're not in production? - At least that was the thought behind allowing Safari in debug mode.
I'd rather consider not allowing Safari at all until it works in hls.js. - The problem with more options is that users use them (without reading docs) - and then are annoyed that something doesn't work.


Freeze on Debug in VS

Hi,
We have an issue with constant Unity freezes when you attach VS debugger.
I was wondering if that commit neucc/grpc fixes it?
Would it be possible for you please to update native binaries inside thise repo with the fixed version?
Thank you

My bad, we figured out that it was because we were not setting GrpcEnvironment.IsDebugging = true;
Feel free to close this issue but it would be great if you can tell some details on why it hangs and what's purpose of that magic delegate that is passed into the native and also why it need to have sleep of 10ms

We do not understand completely yet.
Magic is truly magic, in the Japanese programming term, there are called omajinai.


shgo is not correctly passing jac to minimizer

I am getting  the "_minimize_slsqp() got multiple values for argument 'jac' " error for my toy example below. Is this a bug in shgo or am I doing something wrong? Please advise if there is a workaround.
from scipy.optimize import shgo

def objective(x):
    return 3*x[0]*x[0] + 2*x[0] + 5

def objective_jac(x):
    return 6*x[0] + 2

if __name__ == "__main__":

    bounds = [(-100, 100)]

    result = shgo(objective, bounds, options={'jac':objective_jac})
    print(result)

This appears to be a mistake in the documentation. The jac parameter should be passed in the minimizer_kwargs dictionary rather than int options.
@Stefan-Endres would you like to make a fix? I think the hess parameter is also in the wrong place.

Thank you for tagging me @pmla.
You are right that passing to minimizer_kwargs works and the documentation is wrong. I will make a quick fix to update the minimizer_kwargs with jac and hess after it has been constructed in the __init__ function this should solve the problem.
The original intention with passing it to the options was to allow both global and local use of the Jacobian (for example global use is when computing Lipschitz constants in the global sampling step to stop sampling well explored areas) without the need to define it twice. So this is a bug rather than a mistake in the documentation as it should only be needed for the user to define it once in a dictionary (defined in the options dict and then passed to minimizer_kwargs if and only if the local solver supports it).

@Stefan-Endres why did we just go through the trouble of gh-17140 rather than just adjusting the documentation?
Even after gh-16313 merges, SHGO still doesn't use jac, hess, or hessp. It would have been a whole lot simpler to just remove them from the list of SHGO options, right?

@mdhaber yes you are right. The original reason for it being there was to compute local Lipschitz constants to improve the global sampling quality which greatly improves the performance on a large class of optimisation problems (and the flexibility would be that local solvers that don't use the gradient can be still chosen when needed), but this feature was not stable and is not currently included. For now it is just ease for the user to specify only in one of the dictionaries.
I therefore think it is worth keeping it as it currently is, but I would also be happy to revert the changes and change the documentation.


"download original file" response content-type is html but the data is csv

$ curl -I http://alpha.pandaproject.net/api/1.0/upload/7/download

HTTP/1.1 301 MOVED PERMANENTLY
Server: nginx/1.0.5
Date: Fri, 04 Nov 2011 17:18:04 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Location: http://alpha.pandaproject.net/api/1.0/upload/7/download/

The impact of this is that safari appears to give the file an automatic .html file extension:

Ideally both content-type and content-disposition would positively identify the data as csv.

Got it, easy fix for iteration 5. Thanks!


[Go Live][March 10]

Push to live

Docs Build status updates of commit 35bfeed:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

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