Update coefficients from SPECPower Database

Context
Overview
We would like to keep our application up to date with the most recent data. This includes those from the SPECPower Database.
Out of Scope:
Related issues/Dependencies:
Acceptance Criteria

[ ] When I estimate the emissions for my usage, the core package uses the most up to date SPECPower Database numbers on energy consumption.

Tech Tasks

[ ] Run Changesets, bump any packages that have been updated/changed

Tech Notes
Review Tasks

[ ] Update methodology to reflect updates

I'm looking at whether I can help update the coefficients for this issue but could do with some pointers on where the current values are sourced from:

Are you taking values from https://www.spec.org/power_ssj2008/results/power_ssj2008.html as described in https://www.cloudcarbonfootprint.org/docs/methodology#energy-estimate-watt-hours ?
Is there a reference for the source of each value? For example which SPECpower database entry is the value of 0.62 for the GCP COMPUTE_PROCESSOR_TYPES.CASCADE_LAKE taken from in https://github.com/cloud-carbon-footprint/cloud-carbon-footprint/blob/84ce75ea0efbd259bfe736b2a512424bec5cb2e7/packages/core/src/domain/FootprintEstimationConstants.ts#L45
Are the median and mean values being calculated manually based on the input values e.g. for the value of https://github.com/cloud-carbon-footprint/cloud-carbon-footprint/blob/84ce75ea0efbd259bfe736b2a512424bec5cb2e7/packages/core/src/domain/FootprintEstimationConstants.ts#L43
I assume these are pulled manually at the moment but has any thought been given to automatic updates from the quarterly SPECpower updates?
Are you making a utilization adjustment to the SPECpower value or does this happen elsewhere? I assume elsewhere because SPECpower provide them for 100% utilization and idle, which I assume translates to the MAX and MIN coefficient constants?
Are there any other sources being used for the CPU values?

I'm assuming this requires updating the values in https://github.com/cloud-carbon-footprint/cloud-carbon-footprint/blob/84ce75ea0efbd259bfe736b2a512424bec5cb2e7/packages/core/src/domain/FootprintEstimationConstants.ts
Thanks!

Hey @davidmytton -- thanks so much for looking into this! I'll try my best to answer your questions:

Yes, that is the data set that we are using as the starting point for determining the Compute coefficients.
The ways that it works is as following:

We pull in the SPEC Power dataset in this spreadsheet: https://docs.google.com/spreadsheets/d/1O7Ug_eUZvbZA4dTaA-8DNhJhoZikKD2IdD8OeNQipe4/edit#gid=467435557 in the "SPEC Power Full Results (Jan 2021)" tab. (This tab will need to be renamed once the coefficients are updated). This spreadsheet is linked to from Appendix II in the methodology, and you can see we currently have 735 rows, whereas the current SPEC Power dataset has 754, so we are missing 19 rows that have been added since January 2021. So the first step would be to pull in the missing 19 rows.
For Intel based processors, we determine which microarchitecture they are. If you scroll down in the same tab, you can see we do this with a TRUE/FALSE formula using the "List of Intel Processors" tab.
Based on that, we can then copy those 19 rows over into the corresponding Tab for that microarchitecture (Skylake, Cascade Lake, or AMD EPYC 1st/2nd Gen, etc).
In each of those microarchitecture Tabs, columns Q & R show the min and max watts at o% and 100% utilization, and if you scroll down to the bottom of them, we determine the average for each microarchitecture. For example, in the Coffee Lake Tab, we look at Q13 and R13. Based on adding the additional 19 rows, some of these coefficients will change slightly, which will then need to be updated in  the cloud-carbon-footprint/packages/core/src/domain/FootprintEstimationConstants.ts file.
Because this spreadsheet is public and readonly, I suggest maybe making a copy of it with the changes that we can cross reference, then merge the updates into the main public readonly version.

For the median and mean values, you can look in the same spreadsheet at the "AWS - Compute", "GCP - Compute" and "Azure - Compute" tabs at the beginning. For example, cell E8 in "AWS - Compute" shows how the get the average for AWS. The other two providers should be easier to find. These formulas shouldn't change, but once the coefficients update, the result will be slightly different.

Yes, manual at the moment :) But we would be very open to suggestions of how to better automate the process, whether that is via code or a low/no code approach like Zapier.

I think my answer to qsn 2 might cover this, but no we are not adjusting the utilization from the SPEC Power database.

No. I think what I've outlined here should be all the data sources you need.

Thanks for explaining - I didn't see that Google Sheet! I'll have a look through and see if I can submit a PR for this over the next few days.

I've just opened https://github.com/cloud-carbon-footprint/cloud-carbon-footprint/pull/314 as a draft with the updated coefficients, but would like to request some help before it can be merged:
I made a copy of the Google Sheet and have included the updated equipment tests. Of these, there is just a single new Intel chip - "Intel(R) Xeon(R) Silver 4210 CPU @ 2.20GHz" on row 738 of tab "SPEC Power Full Results (Q2 2021)". This is a Cascade Lake chip. I have added this to the "Cascade Lake" tab line 73 which updates the averages.

There are several new AMD EPYC chips but these are all Gen 3, which is not represented on the sheet on the coefficients. Are we leaving those out for now?
Azure and AWS tests failed so I updated those test files as part of 39b51f5fbbc70a647bd214af17a19c12ea2a78cb but is there a way to validate the calculations other than what is reported as part of the test run?
src/__tests__/cli.test.ts is now failing and I have not fixed this pending an answer above, in case you have a way to validate the numbers rather than blindly updating the tests. For example this failing test has a result for ComputeEngine which goes from 0.00 to 5.78, which seems like a large change but is one I'm unsure how to validate:

    expect(received).toMatchSnapshot()

    Snapshot name: `cli ebs, s3, ec3, elasticache, rds ebs, s3, ec2, elasticache, rds grouped by service 1`

    - Snapshot  - 2
    + Received  + 2

    @@ -2,7 +2,7 @@
      | EBS          | 6.08              | 0.002602               | $9.23
      | S3           | 0.08              | 0.000036               | $12.00
      | EC2          | 39.48             | 0.016895               | $74.00
      | ElastiCache  | 24.06             | 0.010295               | $12.00
      | RDS          | 464.46            | 0.198774               | $18.47
    - | ComputeEngine| 0.00              | 0.000000               | $0.00
    + | ComputeEngine| 5.78              | 0.002892               | $0.00
    - | Total        | 534.15            | 0.228601               | $125.70
    + | Total        | 539.94            | 0.231494               | $125.70

      172 |       const result = await cli([...rawRequest, '--groupBy', 'service'])
      173 |
    > 174 |       expect(result).toMatchSnapshot()
          |                      ^
      175 |     })
      176 |
      177 |     test('ebs, s3, ec2, elasticache, rds, grouped by day', async () => {

      at src/__tests__/cli.test.ts:174:22
      at step (src/__tests__/cli.test.ts:63:23)
      at Object.next (src/__tests__/cli.test.ts:44:53)
      at fulfilled (src/__tests__/cli.test.ts:35:58)

You mentioned the median/mean calculations but I'm not clear on where those are from. In your example, cell E8 in 'AWS - Compute' is labelled as Max Watts for Graviton A1 but the formula is the average of the Max Watts across all CPU types. This matches with https://github.com/cloud-carbon-footprint/cloud-carbon-footprint/blob/86a253612d400c67291e43f3301946f7ea35f1d4/packages/core/src/domain/FootprintEstimationConstants.ts#L146 so I assume the spreadsheet is just somewhat misnamed. However, for GCP median at https://github.com/cloud-carbon-footprint/cloud-carbon-footprint/blob/86a253612d400c67291e43f3301946f7ea35f1d4/packages/core/src/domain/FootprintEstimationConstants.ts#L43 is this value in cell C12 or C13 from the "GCP - Compute" tab?
For memory, the values in the "AWS - Memory" cells N2:P12 seem to be hard coded. I assume these need updating to do the calculation?

Thanks again @davidmytton -- this is looking good so far. Before I answer your questions -- we have recently separated the cloud providers into their own packages, which includes the Compute/Memory coefficients. (This duplicates the values in 3 places, but we want to make it easy for consumers of the app to update them per cloud provider if they want to use different values.) Unfortunately, this change has caused your branch to have some conflicts, and I think it might be easier for you to pull the latest on trunk and create a new branch with the changes (now in the 3x places), than to handle the conflicts (given the changes are small).  If you're able to do that, I think it'll help us verify things like the tests after you re-push.
Now to your questions:

It looks like Azure recently released some instances using the AMD EPYC 3rd generation processors. Specifically the HBv3-series, of which there looks to be only one instance type currently: HB120rs v3 Source: https://azure.microsoft.com/en-us/pricing/details/virtual-machines/linux/ So I think we might want to create a new tab for this generation in the spreadsheet and update the processors options with it, then add this instance type to packages/azure/src/lib/VirtualMachineTypes.ts. Although that change is a little more complex, so we can separate it out to a different issue if you would preffer, and just focus this on the Cascade Lake coefficient update.  AWS and GCP don't seem to be using this generation (yet).
When we initially built out those test, we manually determined the values in a spreadsheet before writing the tests using TDD. In this case however, I'm okay looking at your PR changes to be confident enough with the updated values, rather than re-doing that process and updating the tests first.
Hmmm -- I think I'll like to pull your new branch and check this locally before I had a good response :)
This one is a little tricky, and sorry if the spreadsheet isn't clear. I've made comments in your copy to help resolve this, but I think what you have said is pretty much it.
Correct - these shouldn't be hardcoded but instead pull from the relevant sheet, so Cascade Lake should be updated.

Thanks for the discussion @dtoakley-tw - the PR is now ready for review: https://github.com/cloud-carbon-footprint/cloud-carbon-footprint/pull/314

Thanks so much @davidmytton ! For some reason your branch is showing many more commits than the changes needed for this issue. I pulled your changes and re-pushed a ner branch to origin with your changes, which you can see here: https://github.com/cloud-carbon-footprint/cloud-carbon-footprint/pull/333
Everything looks good, and I've updated the public spreadsheet with the new coefficients: https://docs.google.com/spreadsheets/d/1O7Ug_eUZvbZA4dTaA-8DNhJhoZikKD2IdD8OeNQipe4/edit
I've merged it in, and created a new issue for the AMD EPYC 3rd Gen addition: https://github.com/cloud-carbon-footprint/cloud-carbon-footprint/issues/332
Closing this one off.


Change VLAN Group Uniqueness Constraints

Carved from #2909
Proposed Changes

[ ] VLAN Group: name becomes unique with an enumeration for collisions, drop unique with location
[ ] VLAN: make vlan_group required, keep existing unique together, make default vlan_group

We're going to split VLAN from VLAN Group.


⚠ ClamAV has degraded performance

In 478d248, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 559 ms

Resolved: ClamAV performance has improved in 91b3e76 after 5 minutes.


Ability to show if ALE is running jobs

I have some modules that take 10+ seconds to run all linters for. This is okay since I configured ALE to only run on write, but the annoying thing is that there is, as far as I can find, no straightforward way to see if ALE is still running a job.
This is especially annoying if you fix something and want to to wait to verify that it's indeed fixed. Because you never know if the linter stopped running, it can be a bit hard to see if you actually fixed it, or if the linter just needs a bit more time.
I created a quick patch below which fixed this; I added let &stl .= '%{ale#statusline#IsRunning() ? "[linting]" : "[done]"}' to my vimrc and that seems to work well.
I don't mind finishing this up and opening a proper PR, but I'm not sure if this is also the best way to fix it, though. Perhaps I missed some feature in ALE that already does this? Or perhaps it might be better to add this to ale#statusline#Count()? Or maybe something else?

diff --git i/autoload/ale/statusline.vim w/autoload/ale/statusline.vim
index a073f7a..0b06801 100644
--- i/autoload/ale/statusline.vim
+++ w/autoload/ale/statusline.vim
@@ -105,3 +105,21 @@ function! ale#statusline#Status() abort

     return ''
 endfunction
+
+" IsRunning reports if ALE is currently running a background job.
+function! ale#statusline#IsRunning() abort
+    let l:job_list = []
+
+    " Gather all of the jobs from every buffer.
+    for l:info in values(g:ale_buffer_info)
+        call extend(l:job_list, get(l:info, 'job_list', []))
+    endfor
+
+    for l:job_id in l:job_list
+        if ale#job#IsRunning(l:job_id)
+            return 1
+        endif
+    endfor
+
+    return 0
+endfunction

This could be a good idea.

You might as well make the function return the number of running jobs, and then that could be used for either printing a number or just telling you if anything is running.

Do you think it would make more sense to create a new ale#statusline#IsRunning() function, or to add a new jobs key to the existing ale#statusline#Count() function?
Currently, this gets jobs for all buffers; which could be considered both a good or bad thing, depending on what you want. Something to be said for both, I think.

I wouldn't add a jobs key to the result of that function. That will slow down the processing for that function and probably create bugs. It would be better to return a number of jobs from another function. Then you can use one of the two functions, or both.

#1203 made this obsolete.


Release 0.16.8 CLI

I guess there were no API or CLI changes that needed updating in docs?

Correct.  The payload only contains a single fix in the implementation of the CLI.  No other changes:


onError + onNodeDoubleClick causes rerenders for all nodes

What platform were you using when you found the bug?
  System:
    OS: Linux 6.6 Manjaro Linux
    CPU: (32) x64 AMD Ryzen Threadripper 1950X 16-Core Processor
    Memory: 41.24 GB / 62.65 GB
    Container: Yes
    Shell: 5.9 - /usr/bin/zsh
  Binaries:
    Node: 18.19.0 - ~/.nvm/versions/node/v18.19.0/bin/node
    npm: 10.8.2 - ~/.nvm/versions/node/v18.19.0/bin/npm
    pnpm: 9.6.0 - ~/.nvm/versions/node/v18.19.0/bin/pnpm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chromium: 129.0.6668.58
  npmPackages:
    @xyflow/react: ^12.2.1 => 12.2.1

Live code example
https://codesandbox.io/p/sandbox/cocky-ramanujan-836824?workspaceId=c253d918-6796-444c-b4e6-095cb0aede36
Describe the Bug
Using onError and onNodeDoubleClick causes all nodes to rerender, effectively breaking the benefits of shallow equality checking. This bug took forever to figure out 😭
With onError and onNodeDoubleClick
https://github.com/user-attachments/assets/21d1df00-f6c1-41ea-8771-ceed0f5910f8
Without
https://github.com/user-attachments/assets/313553da-3eda-475a-b9a0-a84e3e2f9d25
Steps to reproduce the bug or issue
    <ReactFlow
      nodes={nodes}
      edges={edges}
      onNodesChange={onNodesChange}
      onEdgesChange={onEdgesChange}
      onConnect={onConnect}
      fitView
      onError={() => {}} // <----------------
      onNodeDoubleClick={() => {console.log("dbl")}} // <----------------
    />

Expected behavior
I expect only the "active" node rerender
Screenshots or Videos
No response
Additional context
No response

Have you tried wrapping your handlers in useCallback? That seems to resolve the issue if I see things right ^^
Here's an example.

@bcakmakoglu That fixed it! Tysm. One other related question. I have a flow with 10-15 connected nodes. When I move the root node (the very first node) I see all the edges in my flow rerender, even those deep in the graph and not connected to my root node. Is this expected behavior?

@bcakmakoglu nm! Figured useMemo / memo should fix the issue and it did! For anyone else running into this issue with custom edges, here's an example code snippet that helped prevent rerenders
import {
  BaseEdge,
  EdgeProps,
  Position,
  getSimpleBezierPath,
} from '@xyflow/react';
import React, { memo, useMemo } from 'react';

import { cn } from '@acme/ui/utils';

const CustomEdge = ({
  sourceX,
  sourceY,
  targetX,
  targetY,
  ...props
}: EdgeProps) => {
  const [edgePath] = useMemo(() => {
    return getSimpleBezierPath({
      sourceX,
      sourceY,
      targetX,
      targetY,
      sourcePosition: Position.Right,
      targetPosition: Position.Left,
    });
  }, [sourceX, sourceY, targetX, targetY]);

  return (
    <BaseEdge
      path={edgePath}
      animated
      {...props}
      className={cn(
        props.selected && '!stroke-neutral-200 !stroke-2',
        !props.selected && '!stroke-neutral-500 !stroke-1',
      )}
      style={{
        strokeLinecap: 'round',
      }}
    />
  );
};

export default memo(CustomEdge);


react-native run-android --variant=developmentDebug does not work currently.

Description
I bumped RN from 0.70.6 to 0.71.0
I used the command normally until 0.70.6 version, but it doesn't work from 0.71.0.
My guess is that the following line has been removed from app/build.gradle.
apply from: "../../node_modules/react-native/react.gradle"

Why was it deleted when it moved from version 70 to 71?
Version
0.71.0
Output of npx react-native info
System:
OS: macOS 12.6
CPU: (10) arm64 Apple M1 Pro
Memory: 336.72 MB / 16.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 18.0.0 - /usr/local/bin/node
Yarn: 1.22.18 - /opt/homebrew/bin/yarn
npm: 8.6.0 - /usr/local/bin/npm
Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.11.3 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.4, iOS 15.4, macOS 12.3, tvOS 15.4, watchOS 8.5
Android SDK: Not Found
IDEs:
Android Studio: 2022.1 AI-221.6008.13.2211.9477386
Xcode: 13.3.1/13E500a - /usr/bin/xcodebuild
Languages:
Java: 11.0.15 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 18.2.0 => 18.2.0
react-native: 0.71.0 => 0.71.0
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce

run cli android //

react-native run-android --variant=developmentDebug
...
Error: Command failed: ./gradlew app:installDebug -PreactNativeDevServerPort=8081

FAILURE: Build failed with an exception.

* What went wrong:
Task 'installDebug' not found in project ':app'.

Snack, code example, screenshot, or link to a repository

run cli android //

react-native run-android --variant=developmentDebug
...
Error: Command failed: ./gradlew app:installDebug -PreactNativeDevServerPort=8081

FAILURE: Build failed with an exception.

* What went wrong:
Task 'installDebug' not found in project ':app'.

@ko-devHong please check here : https://github.com/facebook/react-native/issues/35838

Closing as a duplicate of https://github.com/facebook/react-native/issues/35838
The fix is forthcoming and will be shipped in a future point release.
For the time being you can use --mode.


Support for parameter interdependencies

Moonwalk should allow API designers to express interdependencies between the parameters of an operation.
This is part of the initial Moonwalk Proposal and is broken out here to refine the ideas before creating the ADR.
The Problem to be Solved
All prior versions of OpenAPI used an array to define parameters for an operation. This approach does not provide any formal mechanism for describing interdependencies between parameters. Research [1]  has shown that interdependencies are not uncommon in real-world APIs and come in a variety of forms. Issue #256 (opened in 2015) requested this feature and has received over 600 up-votes.

"API Specs and Inter-Parameter Dependencies: The Elephant in the Room", Alberto Martin, API Specifications Conference 2022

Proposed solution
Rather than using an array to define the parameters for an operation, we should use a JSON Schema. The parameters schema must be an object schema and must not have additionalProperties. Each named property of the parameters schema defines an operation parameter. Property names of the parameter schema have the form [<in>.]name, where <in> may be "query", "header", "path", or "cookie". When not specified, <in> defaults to "query".
Note: Combining the <in> and name allows parameters with the same name but different <in>, as is permitted in prior versions of OpenAPI. It also avoids the need to augment JSON Schema for this purpose.
The parameterSchema field would be supported on Operations and on Path Items. If specified on a Path Item, the effective parameter schema for an operation would be the allOf of the path item schema and the operation schema.
The parameter schema may contain JSON Schema assertions to express interdependencies between parameters. Some common interdependencies are described below.
Requires
The presence of a parameter (or a specific parameter value) requires the presence of another parameter.
Example: answerCount must be specified if promote is specified.
    oneOf:
    - not:
      - required: [promote]
      - required: [answerCount]

Or
Given a set of parameters, one or more of them must be included.
Example: either title or description must be specified.
    anyOf:
    - required: [title]
    - required: [description]

OnlyOne
Given a set of parameters, one and only one of them must be included.
Example: either from or messagingServiceId must be specified but not both.
    oneOf:
    - required: [from]
    - required: [messagingServiceId]

AllOrNone
Given a set of parameters, either all of them are provided or none of them is.
Example: subject_type and subject_id are both specified or neither is specified.
    oneOf:
    - required: [subject_type,subject_id]
    - not:
        anyOf:
          - required: [subject_type]
          - required: [subject_id]

Example: value is present if and only if type is "bucket"
    oneOf:
    - properties:
        type:
          enum: ["bucket"]
      required: [type,value]
    - not:
        properties:
          type:
            enum: ["bucket']
        required: [type,value]

ZeroOrOne
Given a set of parameters, at most one of can be included.
Example: specify zero or one of forContentOwner, forDeveloper, forMine, or relatedToVideoId:
    oneOf:
    - required: [forContentOwner]
      not:
        anyOf:
        - required: [forDeveloper]
        - required: [forMine]
        - required: [relatedToVideoId]
    - required: [forDeveloper]
      not:
        anyOf:
        - required: [forContentOwner]
        - required: [forMine]
        - required: [relatedToVideoId]
    - required: [forMine]
      not:
        anyOf:
        - required: [forContentOwner]
        - required: [forDeveloper]
        - required: [relatedToVideoId]
    - required: [relatedToVideoId]
      not:
        anyOf:
        - required: [forContentOwner]
        - required: [forDeveloper]
        - required: [forMine]
    - not:
        anyOf:
        - required: [forContentOwner]
        - required: [forDeveloper]
        - required: [forMine]
        - required: [relatedToVideoId]

Note: There is probably an easier way to express this. Happy for feedback here.
Compatibility with OpenAPI 3.x
I believe that no functionality of OpenAPI 3.x is lost with this proposal. It should be straightforward to transform an existing parameters array to an equivalent parameterSchema.

Just realized that I have not accounted for the OpenAPI 3.x style attribute -- need to think about how to represent that in the parameter schema.


[documentation] add "How Predis abstracts Redis commands" to "README.md"

Hello,
your project is great,
as a beginner user I searched a lot of time how to call redis commands, I think that the section How Predis abstracts Redis commands in the FAQ is really important and should be added to the README.md
While this section is greatly writed, I think that an example would be nice, like
$client->set("key", "value", "ex", 1000); is equivalent to native SET key "value" EX 1000

yes this is quite confusing, would be great to have a proper API doc: https://github.com/nrk/predis/issues/484


[all] Flutter Android build fails with firebase dependencies.

I am using Android Studio 3.5 stable
java -version  1.8
and this is the issue :
I have project gradle like this :
buildscript {
    repositories {
        google()
        jcenter()
    }

    dependencies {
        classpath 'com.android.tools.build:gradle:3.3.0'
        classpath 'com.google.gms:google-services:4.3.0'
    }
}

allprojects {
    repositories {
        google()
        jcenter()
    }
}

rootProject.buildDir = '../build'
subprojects {
    project.buildDir = "${rootProject.buildDir}/${project.name}"
}
subprojects {
    project.evaluationDependsOn(':app')
}

task clean(type: Delete) {
    delete rootProject.buildDir
}

App gradle  like this :
def localProperties = new Properties()
def localPropertiesFile = rootProject.file('local.properties')
if (localPropertiesFile.exists()) {
    localPropertiesFile.withReader('UTF-8') { reader ->
        localProperties.load(reader)
    }
}

def flutterRoot = localProperties.getProperty('flutter.sdk')
if (flutterRoot == null) {
    throw new GradleException("Flutter SDK not found. Define location with flutter.sdk in the local.properties file.")
}

def flutterVersionCode = localProperties.getProperty('flutter.versionCode')
if (flutterVersionCode == null) {
    flutterVersionCode = '1'
}

def flutterVersionName = localProperties.getProperty('flutter.versionName')
if (flutterVersionName == null) {
    flutterVersionName = '1.0'
}

apply plugin: 'com.android.application'
apply from: "$flutterRoot/packages/flutter_tools/gradle/flutter.gradle"

android {
    compileSdkVersion 28

    lintOptions {
        disable 'InvalidPackage'
    }

    defaultConfig {
        // TODO: Specify your own unique Application ID (https://developer.android.com/studio/build/application-id.html).
        applicationId "com.takefun.android"
        minSdkVersion 16
        targetSdkVersion 28
        versionCode flutterVersionCode.toInteger()
        versionName flutterVersionName
        testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
        multiDexEnabled true
    }

    buildTypes {
        release {
            // TODO: Add your own signing config for the release build.
            // Signing with the debug keys for now, so `flutter run --release` works.
            signingConfig signingConfigs.debug
        }
    }
}

flutter {
    source '../..'
}

dependencies {
    testImplementation 'junit:junit:4.12'
    androidTestImplementation 'com.android.support.test:runner:1.0.2'
    implementation 'com.android.support:multidex:1.0.3'
    androidTestImplementation 'com.android.support.test.espresso:espresso-core:3.0.2'
}

apply plugin: 'com.google.gms.google-services'

& Pubspec.yaml  like this :
name: Name
description: Expense.

version: 1.0.0+1

environment:
  sdk: ">=2.1.0 <3.0.0"

dependencies:
   flutter:
     sdk: flutter
  cupertino_icons: ^0.1.2
  image_picker: ^0.6.0+17
  cloud_firestore: ^0.12.9
  firebase_auth: ^0.14.0+2
  firebase_core: ^0.4.0+8
  google_sign_in: ^4.0.6
  fimber: ^0.3.2
  gradient_widgets: ^0.5.0
  flutter_svg: ^0.13.1
  flutter_vector_icons: ^0.2.0
  image_cropper: ^1.0.2
  firebase_storage: ^3.0.5
  stack_trace: ^1.9.3

dev_dependencies:
  flutter_test:
    sdk: flutter

My iOS builds runs well but my android build is failing with console output :
Launching lib/main.dart on Android SDK built for x86 in debug mode...
Initializing gradle...
Resolving dependencies...
Running Gradle task 'assembleDebug'...

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':app:compileDebugJavaWithJavac'.
> Could not resolve all task dependencies for configuration ':app:debugCompileClasspath'.
   > Could not find com.google.database.firebase:database.firebase-firestore:19.0.0.
     Required by:
         project :app > project :cloud_firestore
   > Could not find com.google.database.firebase:database.firebase-core:16.0.9.
     Required by:
         project :app > project :firebase_core

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 51s
Finished with error: Gradle task assembleDebug failed with exit code 1

Flutter doctor has the following output (just listed android and android studio related ones):

[✓] Flutter (Channel stable, v1.7.8+hotfix.4, on Mac OS X 10.14.6 18G87, locale en-US)
    • Flutter version 1.7.8+hotfix.4 at /Users/adventure/dev/flutter
    • Framework revision 20e59316b8 (5 weeks ago), 2019-07-18 20:04:33 -0700
    • Engine revision fee001c93f
    • Dart version 2.4.0

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/adventure/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 28.0.3
    • Java binary at: /Applications/Android Studio 3.5.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    • All Android licenses accepted.

[✓] Android Studio (version 3.5)
    • Android Studio at /Applications/Android Studio 3.5.app/Contents
    • Flutter plugin version 38.2.3
    • Dart plugin version 191.8423
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

[✓] Android Studio (version 3.4)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 37.1.1
    • Dart plugin version 183.6270
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)

Same here, when trying to actually run (not build, it does actually build) the _firebaseAuth.signInWithCustomToken(token: token) method, it goes like this:
W/BiChannelGoogleApi(19269): [FirebaseAuth: ] getGoogleApiForMethod() returned Gms: com.google.firebase.auth.api.internal.zzak@826aa86
E/JavaBinder(19269): *** Uncaught remote exception!  (Exceptions are not yet supported across processes.)
E/JavaBinder(19269): java.lang.NoClassDefFoundError: Failed resolution of: Landroid/support/v4/util/ArrayMap;
E/JavaBinder(19269): 	at com.google.firebase.auth.internal.zzam.zzc(Unknown Source:22)
E/JavaBinder(19269): 	at com.google.firebase.auth.internal.zzam.zzde(Unknown Source:17)
E/JavaBinder(19269): 	at com.google.firebase.auth.internal.zzam.zzdd(Unknown Source:8)
E/JavaBinder(19269): 	at com.google.firebase.auth.internal.zzan.zzdf(Unknown Source:1)
E/JavaBinder(19269): 	at com.google.firebase.auth.internal.zzm.isAnonymous(Unknown Source:47)
E/JavaBinder(19269): 	at com.google.firebase.auth.internal.zzat.zzi(Unknown Source:57)
E/JavaBinder(19269): 	at com.google.firebase.auth.internal.zzat.zzg(Unknown Source:10)
E/JavaBinder(19269): 	at com.google.firebase.auth.FirebaseAuth.zza(Unknown Source:62)
E/JavaBinder(19269): 	at com.google.firebase.auth.FirebaseAuth$zzb.zza(Unknown Source:5)
E/JavaBinder(19269): 	at com.google.firebase.auth.api.internal.zzcp.zzdx(Unknown Source:14)
E/JavaBinder(19269): 	at com.google.firebase.auth.api.internal.zzen.zzen(Unknown Source:35)
E/JavaBinder(19269): 	at com.google.firebase.auth.api.internal.zzen.zza(Unknown Source:41)
E/JavaBinder(19269): 	at com.google.firebase.auth.api.internal.zzep.zza(Unknown Source:9)
E/JavaBinder(19269): 	at com.google.firebase.auth.api.internal.zzdx.dispatchTransaction(Unknown Source:9)
E/JavaBinder(19269): 	at com.google.android.gms.internal.firebase_auth.zza.onTransact(Unknown Source:13)
E/JavaBinder(19269): 	at android.os.Binder.execTransactInternal(Binder.java:1021)
E/JavaBinder(19269): 	at android.os.Binder.execTransact(Binder.java:994)
E/JavaBinder(19269): Caused by: java.lang.ClassNotFoundException: Didn't find class "android.support.v4.util.ArrayMap" on path: DexPathList[[zip file "/data/app/com.app.myproject-NarLETRcOMNLCL2bBLZTdg==/base.apk"],nativeLibraryDirectories=[/data/app/com.app.myproject-NarLETRcOMNLCL2bBLZTdg==/lib/arm64, /data/app/com.app.myproject-NarLETRcOMNLCL2bBLZTdg==/base.apk!/lib/arm64-v8a, /system/lib64, /system/product/lib64]]
E/JavaBinder(19269): 	at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:196)
E/JavaBinder(19269): 	at java.lang.ClassLoader.loadClass(ClassLoader.java:379)
E/JavaBinder(19269): 	at java.lang.ClassLoader.loadClass(ClassLoader.java:312)
E/JavaBinder(19269): 	... 17 more
E/AndroidRuntime(19269): FATAL EXCEPTION: Binder:19269_2
E/AndroidRuntime(19269): Process: com.app.myproject, PID: 19269
E/AndroidRuntime(19269): java.lang.NoClassDefFoundError: Failed resolution of: Landroid/support/v4/util/ArrayMap;
E/AndroidRuntime(19269): 	at com.google.firebase.auth.internal.zzam.zzc(Unknown Source:22)
E/AndroidRuntime(19269): 	at com.google.firebase.auth.internal.zzam.zzde(Unknown Source:17)
E/AndroidRuntime(19269): 	at com.google.firebase.auth.internal.zzam.zzdd(Unknown Source:8)
E/AndroidRuntime(19269): 	at com.google.firebase.auth.internal.zzan.zzdf(Unknown Source:1)
E/AndroidRuntime(19269): 	at com.google.firebase.auth.internal.zzm.isAnonymous(Unknown Source:47)
E/AndroidRuntime(19269): 	at com.google.firebase.auth.internal.zzat.zzi(Unknown Source:57)
E/AndroidRuntime(19269): 	at com.google.firebase.auth.internal.zzat.zzg(Unknown Source:10)
E/AndroidRuntime(19269): 	at com.google.firebase.auth.FirebaseAuth.zza(Unknown Source:62)
E/AndroidRuntime(19269): 	at com.google.firebase.auth.FirebaseAuth$zzb.zza(Unknown Source:5)
E/AndroidRuntime(19269): 	at com.google.firebase.auth.api.internal.zzcp.zzdx(Unknown Source:14)
E/AndroidRuntime(19269): 	at com.google.firebase.auth.api.internal.zzen.zzen(Unknown Source:35)
E/AndroidRuntime(19269): 	at com.google.firebase.auth.api.internal.zzen.zza(Unknown Source:41)
E/AndroidRuntime(19269): 	at com.google.firebase.auth.api.internal.zzep.zza(Unknown Source:9)
E/AndroidRuntime(19269): 	at com.google.firebase.auth.api.internal.zzdx.dispatchTransaction(Unknown Source:9)
E/AndroidRuntime(19269): 	at com.google.android.gms.internal.firebase_auth.zza.onTransact(Unknown Source:13)
E/AndroidRuntime(19269): 	at android.os.Binder.execTransactInternal(Binder.java:1021)
E/AndroidRuntime(19269): 	at android.os.Binder.execTransact(Binder.java:994)
E/AndroidRuntime(19269): Caused by: java.lang.ClassNotFoundException: Didn't find class "android.support.v4.util.ArrayMap" on path: DexPathList[[zip file "/data/app/com.app.myproject-NarLETRcOMNLCL2bBLZTdg==/base.apk"],nativeLibraryDirectories=[/data/app/com.app.myproject-NarLETRcOMNLCL2bBLZTdg==/lib/arm64, /data/app/com.app.myproject-NarLETRcOMNLCL2bBLZTdg==/base.apk!/lib/arm64-v8a, /system/lib64, /system/product/lib64]]
E/AndroidRuntime(19269): 	at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:196)
E/AndroidRuntime(19269): 	at java.lang.ClassLoader.loadClass(ClassLoader.java:379)
E/AndroidRuntime(19269): 	at java.lang.ClassLoader.loadClass(ClassLoader.java:312)
E/AndroidRuntime(19269): 	... 17 more
I/Process (19269): Sending signal. PID: 19269 SIG: 9
Lost connection to device.

On the other hand I can't even manage to build in iOS:
Xcode build done.                                           24.1s
Failed to build iOS app
Error output from Xcode build:
↳
    ** BUILD FAILED **
Xcode's output:
↳
    /Users/aru/workspace/beyla/beylastaff/beylastaff/ios/Runner/GeneratedPluginRegistrant.m:6:9: fatal error: 'cloud_firestore/CloudFirestorePlugin.h' file not found
    #import <cloud_firestore/CloudFirestorePlugin.h>
            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    1 error generated.

I am facing it as well. It stops recognizing the GradleException inside of a build.gradle

I had a similar error. Adding this at the bottom of android/app/build.gradle solved the problem temporarily for me, maybe it will work for you too:
apply plugin: 'com.google.gms.google-services'
com.google.gms.googleservices.GoogleServicesPlugin.config.disableVersionCheck = true

Hey @erluxman, try changing classpath 'com.google.gms:google-services:4.3.0'
in your project gradle.build to classpath 'com.google.gms:google-services:3.2.1'
let me know if it worked for you

I had a similar error. Adding this at the bottom of android/app/build.gradle solved the problem temporarily for me, maybe it will work for you too:
apply plugin: 'com.google.gms.google-services'
com.google.gms.googleservices.GoogleServicesPlugin.config.disableVersionCheck = true

A problem occurred evaluating project ':app'.

No such property: config for class: com.google.gms.googleservices.GoogleServicesPlugin

Hey @erluxman, try changing classpath 'com.google.gms:google-services:4.3.0'
in your project gradle.build to classpath 'com.google.gms:google-services:3.2.1'
let me know if it worked for you

Did not work

Yeah, I wasn't sure it'll work.
I have another idea, try to add in the end of depndencies(){}
those two lines
implementation ' firebase-core:16.0.9'
implementation 'com.google.firebase:firebase-firestore:19.0.0'

Yeah, I wasn't sure it'll work.
I have another idea, try to add in the end of depndencies(){}
those two lines
implementation 'firebase-core:16.0.9'
implementation 'com.google.firebase:firebase-firestore:19.0.0'

DId not help :(

I have similar problem with firebase_auth. On line
await _auth.signInWithCredential(credential)
app crashed with error java.lang.IllegalArgumentException: Unsupported value: null

@erluxman
I'm sorry, my mistake, could you try this instead?
If it doesn't work, could publish the new android build log so I can know if the problem was partially solved?
implementation 'com.google.firebase:firebase-core:16.0.9'
implementation 'com.google.firebase:firebase-firestore:19.0.0'

With same problem when import firebase_database
classpath 'com.android.tools.build:gradle:3.2.1'
classpath com.google.gms:google-services:3.2.1
and in
gradle.properties add
android.useAndroidX=true
android.enableJetifier=true
Seems everything goes to normal.

Hey @erluxman, try changing classpath 'com.google.gms:google-services:4.3.0'
in your project gradle.build to classpath 'com.google.gms:google-services:3.2.1'
let me know if it worked for you

Cloned an old repo, and this really helped.

Hi @erluxman
did the proposed solution fix the issue?
If didn't and you are still experiencing this issue
with the latest version of Flutter and FlutterFire plugin
can you please provide your updated  flutter doctor -v
and your and your flutter run --verbose/flutter build --verbose ?
Also, to better address the issue, would be helpful
if you could post a self contained app on github
or the steps to reproduce it.
Thank you

Hi @erluxman
does the proposed solution fix the issue?

That solution fixed my issue even without having to put manual dependencies to app.gradle file.
Thanks a lot.

Try changing the minimum target SDK version from v16 to v21.

worked for me after adding these lines....

Inside app folder in file build.gradle

add 'multiDexEnabled true' inside 'defaultConfig'

defaultConfig {
    multiDexEnabled true
}

Then,

dependencies {
    implementation 'com.google.firebase:firebase-analytics:17.2.0'
    implementation 'com.google.firebase:firebase-firestore:19.0.0'
    implementation 'com.android.support:multidex:1.0.3'
}

The main problem arises with dependency version added in the build.gradle file located outside of app folder...Generally flutter tells to add dependency like this:

dependencies {
        classpath 'com.google.gms:google-services:4.3.2'
    }

but the conflict is with the version 4.3.2 as the line before it in my project is
 classpath 'com.android.tools.build:gradle:3.2.1'
So, it conflicts with this tools version.

So, change it to this:

dependencies {
        classpath 'com.google.gms:google-services:3.2.1'
    }

Now, I hope your project will run.

For me the issue with this error, and why it is so difficult to find a solution for it is that it is wrong.   It took me weeks to resolve this issue because the error has absolutely 0 to do with firebase being incompatible with androidx and everything to do with my key file (your .jks file).    For me, the file path was incorrect, and correcting this made everything work again like magic.
It is likely that if you are tearing your hair out over this issue, that this is not even an issue.   Have a look at your key store file and make sure everything is correct with it.   If the app runs perfectly fine, but will not build, there are only two files involved that are different.   Your google-services.json and your keystore file.
Absolutely terrible error reporting.

For me the issue with this error, and why it is so difficult to find a solution for it is that it is wrong. It took me weeks to resolve this issue because the error has absolutely 0 to do with firebase being incompatible with androidx and everything to do with my key file (your .jks file). For me, the file path was incorrect, and correcting this made everything work again like magic.
It is likely that if you are tearing your hair out over this issue, that this is not even an issue. Have a look at your key store file and make sure everything is correct with it. If the app runs perfectly fine, but will not build, there are only two files involved that are different. Your google-services.json and your keystore file.
Absolutely terrible error reporting.

I share your sentiment <3

Hey @erluxman, try changing classpath 'com.google.gms:google-services:4.3.0'
in your project gradle.build to classpath 'com.google.gms:google-services:3.2.1'
let me know if it worked for you

it worked

i have same issue
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':cloud_firestore:javaPreCompileDebug'.

Could not resolve all files for configuration ':cloud_firestore:debugCompileClasspath'.
Failed to transform artifact 'firebase-auth-interop.aar (com.google.firebase:firebase-auth-interop:18.0.0)' to match attributes {artifactType=android-classes, org.gradle.usage=java-api}.
Execution failed for AarToClassTransform: C:\Users\ahtisham.gradle\caches\transforms-2\files-2.1\0184456ab8db2ccbb1ff88e00c2a36f8\jetified-firebase-auth-interop-18.0.0.aar.
error in opening zip file

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 17m 27s
Finished with error: Gradle task assembleDebug failed with exit code 1

any news on this?

Hey @erluxman, try changing classpath 'com.google.gms:google-services:4.3.0'
in your project gradle.build to classpath 'com.google.gms:google-services:3.2.1'
let me know if it worked for you
Still not working

Got the same issue:
dependencies {
    implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version"
    classpath 'com.android.tools.build:gradle:3.3.2'
    classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
    classpath 'com.google.gms:google-services:3.2.1'

}

Running Gradle task 'assembleDebug'...
FAILURE: Build failed with an exception.

Where:
Build file '/Users/ed/AndroidStudioProjects/flutter_app/android/app/build.gradle' line: 66

What went wrong:
A problem occurred evaluating project ':app'.

Could not find method classpath() for arguments [com.android.tools.build:gradle:3.3.2] on object of type org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

@erluxman
I'm sorry, my mistake, could you try this instead?
If it doesn't work, could publish the new android build log so I can know if the problem was partially solved?
implementation 'com.google.firebase:firebase-core:16.0.9'
implementation 'com.google.firebase:firebase-firestore:19.0.0'

i have same issue i didnt help

Got the same issue:
dependencies {
    implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version"
    classpath 'com.android.tools.build:gradle:3.3.2'
    classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
    classpath 'com.google.gms:google-services:3.2.1'

}

Running Gradle task 'assembleDebug'...
FAILURE: Build failed with an exception.

Where:
Build file '/Users/ed/AndroidStudioProjects/flutter_app/android/app/build.gradle' line: 66
What went wrong:
A problem occurred evaluating project ':app'.

Could not find method classpath() for arguments [com.android.tools.build:gradle:3.3.2] on object of type org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

same problem bro

It's all hit and trial until now, no real solution...

My advice for everone is to switch to https://appwrite.io/

It's all hit and trial until now, no real solution...

i've wasted so much of my time😥

yea me too

any updates here ? i have same problem nothing of above works

im find sulution work with me try goto  android/setting.gradle  on realy top add this tow liens include ':library' include ':app'

It's all hit and trial until now, no real solution...

I have spent 3 days with 0 output

me too

Hey 👋
Our rework of the the FlutterFire plugins to depend on a shared 'core' (which controls the versions of the Firebase SDKs used on Android) as part of the FlutterFire roadmap was published over a week ago with a ton of fixes and new features.
Please could you try the new versions and see if this is still an issue? Additionally the documentation site now covers Android installation, https://firebase.flutter.dev
If this is still an issue then please submit a new up to date GitHub issue.
For help migrating to the new plugins please see the new migration guide: https://firebase.flutter.dev/docs/migration


Add config header for lua/inlet

I missed some config header defines.

Apparently I got the export/install part (or someone did) but I did miss the About() info.  I fixed it.


Programmatic cluster addition to Lens

What would you like to be added:
A programmatic and unified way to modify files like lens-cluster-store.json in order to add clusters
Why is this needed:
It is manageable to add clusters when they are long-lived and there are few of them. However, when cluster number is double digit and they are short-lived it becomes cumbersome to make my Lens data up-to-date. I could myself write some script which gets all the clusters from "cluster registry" and then writes the info into Lens related files but it would be awesome that Lens could provide some API compatability through some script: lensctl ? :D . My usecase would be satisfied with such functionality/API:
lensctl add  {{cluster name}}  --kubeconfig={{path to kubeconfig}} --workspace=production

Environment you are Lens application on:
3.6.7

Yes, also great for #1072 https://github.com/supervisor-com/lens-web

With Lens 5.0.0-beta.6 it's already possible to add clusters by writing kubeconfigs to ~/.kube/ folder (Lens autodetects those files).

Fixed by #2567 (and subsequent PRs)


chore: release main

:robot: I have created a release beep boop
keychain: 5.0.2
5.0.2 (2024-09-13)
Bug Fixes

allow importing the self key (#2700) (34455b5)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

keychain-v5.0.2
:sunflower:


Feature/230 note that project id can also be a string

Make it possible to use NAMESPACE/PROJECT_NAME on all methods that uses project ID
ex.
gitlab project gitlab-org/gitlab-ce
gitlab milestones gitlab-org/gitlab-ce
gitlab tree gitlab-org/gitlab-ce
gitlab tags gitlab-org/gitlab-ce
...
Closes #230

It is pretty needed :)

This is already possible if you url encode your project string before using it as a parameter to one of the methods.
I am not fond of adding code where documentation would do.  @jvanbaarsen - I know you're busy but do you have an opinion here?

Egen using CLI we should not expect users to url encode

Good point.  Have you written any tests that verify this functionality? I don't remember seeing any.

@asedge I have added specs to verify that project string is url_encoded.
Also made code change to support backword compatibility for users that already have url_encoded.

Note to self - always run all specs locally before push.
Removed the backward compatibility code again...as it was not that compatible 😊

Thanks!

Any chance we can get a gem release with this in?

@orta Yes, "soon".  Trying to button a few things up first.

@orta 4.0.0 has been released.


Wrong test in project euler 462

https://github.com/freeCodeCamp/freeCodeCamp/blob/1df0e61091596a5d16377d15a252c1d34ccf653c/curriculum/challenges/english/18-project-euler/project-euler-problems-401-to-480/problem-462-permutation-of-3-smooth-numbers.md#L32-L33
There should be a comma separating the two terms, instead of having the === operator
https://github.com/freeCodeCamp/freeCodeCamp/blob/1df0e61091596a5d16377d15a252c1d34ccf653c/curriculum/challenges/english/18-project-euler/project-euler-problems-401-to-480/problem-462-permutation-of-3-smooth-numbers.md#L25-L26
Also the sentence should be changed from "Give as your answer as a string in its scientific notation" to "Give your answer as a string in scientific notation"

I have a question. Now normally when a typo like that is made, I would expect it to error out. But I only see five past and one as a pending when I test the file. When I test the specific block, I get 79 pending challenges.
I presume that there might be a good bit of challenges in that Superblock that might need looked at it, that is if you can replicate this behavior. My question is if you can replicate that behavior and are getting similar results.

I just now looked at it. This is a problem though because with no solution there's no automatic indicators that our tests are broken like this.

This is what the output would look like if there's a solution intended to solve the problem.

Yes, most of project euler and rosetta code doesn't have solutions. They would need to be written in a way to not timeout, these problems get easily resource intensive, and they would increase a lot the time for testing all the curriculum

You're right. Four hundred plus challenges that are resource intensive would increase the amount of time the curriculum checker to execute.
I'd love to try to take on the task for writing efficient solutions for the Project Euler and Rosetta code challenges though. Maybe even learn something along the way.

@a2937 I don't think it is necessary, it is not a part of the curriculum that is much used, see needing 3 years to figure out the bug


Inconsistent use of is-prefix in boolean props

Some of the components are inconsistent in the use of the is-prefix for boolean props.
Button

isLoading
isSelected
disabled

Checkbox

isIndeterminate
checked
disabled

Select

isLoading
clearable
disabled
error
... more

Tag

isHovered
isFocused
closable
disabled

Modal

isOpen
closable

Tooltip, Popover

isOpen
ignoreBoundary
showArrow

I propose to drop the prefix for consistency.

Not completely related to this ticket, but I will still squeeze it in: Would it be a big deal to rename disabled while still capturing the intent? I was thinking of off. but I don't like it that much.


no-undef-init makes defining a const with undefined impossible

const nothing1 = undefined // does not lint
const nothing2 = null // does lint
// etc

This may look weird, but it's part of a spec and I want to have all fixtures as consts, instead of copying them to all assertions. Maybe later I decide that the function I'm testing should work with empty strings instead of undefined, so I can simply change one line.
I do see that this is a very specific edge case. If this is a wont-fix, I'm fine with it. I can simply change it to let nothing1.

I do see that this is a very specific edge case

I think I agree; I don't see a compelling reason to relax the rule - wonder what others think

@despairblue What's the error you get?

@feross on one computer I get It's not necessary to initialize 'nothing1' to undefined on the other it works as expected. I suppose it was fixed and I have an old eslint version installed on one computer.
Thanks for the help :+1:

Cheers!


Fix product name

Microsoft Flow -> Power Automate

@changeworld : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Verified the name change; thanks.


ZPermissions merging

I am using (original) zPermissions for my multi server bungeecord / spigot 1.10.2 setup, but found out recently that the original zPermission seems to be unmaintained and that there are some forks (as yours) on Github.
I am having however some problems with my setup (i.e. bungeeChat and PermissionSync dont work).
Do you intend to be the "new maintainer" of zPermissions? Are there any plans to merge the forks on github?
Kind regards
Hauke

Yeah this is my other account, yeah at the time I was going to have a version maintained for myself and others should they want to use it, currently the PC I was using for development is now long gone. I'm planing to restart development for this soon, just got to wait saving up money for a new system :). I don't intend to be the new maintainer, just plan on making sure its works on the version of Minecraft I plan to use on my own private server but i'll port it to the other versions of 1.10 and up for people who request it


Dataset split

Could you please upload the ImageSets file? I just randomly split the astyx dataset and  follow your instructions but only get very poor performance.

Could you please upload the ImageSets file? I just randomly split the astyx dataset and follow your instructions but only get very poor performance.

Hello, I also tried to randomly partition the dataset, but the accuracy after reproduction is not good. Do you remember the performance results of reproduction?

Could you please upload the ImageSets file? I just randomly split the astyx dataset and follow your instructions but only get very poor performance.

Hello, I also tried to randomly partition the dataset, but the accuracy after reproduction is not good. Do you remember the performance results of reproduction?

For the baseline PointPillars with only LiDAR input, I got about 8 percent drop in 3D view at moderate level.

Could you please upload the ImageSets file? I just randomly split the astyx dataset and follow your instructions but only get very poor performance.

Hello, I also tried to randomly partition the dataset, but the accuracy after reproduction is not good. Do you remember the performance results of reproduction?

For the baseline PointPillars with only LiDAR input, I got about 8 percent drop in 3D view at moderate level.

Thank you. It's in<EMAIL_ADDRESS>0.5 0.5?
My reproduction result is like this, and it looks the same
Car<EMAIL_ADDRESS>0.70, 0.70:
Bbox AP: 36.8576, 32.3523, 31.4710
Bev AP: 38.7652, 35.5619, 34.8579
3D AP: 17.2034, 15.0750, 15.0462
AOS AP: 36.46, 32.01, 31.09
Car<EMAIL_ADDRESS>0.70, 0.70:
Bbox AP: 34.1645, 29.5950, 28.4427
Bev AP: 36.4198, 32.3735, 31.4788
3D AP: 14.3970, 12.3787, 11.8986
AOS AP: 33.77, 29.22, 28.09
Car<EMAIL_ADDRESS>0.50, 0.50:
Bbox AP: 59.9559, 52.9196, 51.8491
Bev AP: 59.0141, 51.9162, 51.0499
3D AP: 49.5782, 42.9737, 42.7284
AOS AP: 59.16, 52.15, 50.94
Car<EMAIL_ADDRESS>0.50, 0.50:
Bbox AP: 59.3984, 51.7946, 50.4342
Bev AP: 59.0424, 50.9988, 48.9314
3D AP: 48.2886, 41.6285, 39.8300
AOS AP: 58.52, 50.89, 49.54

Well, maybe there are some bugs in my code. I did it a year ago and I forgot many details.

Could you please upload the ImageSets file? I just randomly split the astyx dataset and follow your instructions but only get very poor performance.

Hello, I also tried to randomly partition the dataset, but the accuracy after reproduction is not good. Do you remember the performance results of reproduction?

For the baseline PointPillars with only LiDAR input, I got about 8 percent drop in 3D view at moderate level.

Thank you. Is it in<EMAIL_ADDRESS>0.5 0.5?
My reproduction result is like this, and it looks the same
Car<EMAIL_ADDRESS>0.70, 0.70:
Bbox AP: 36.8576, 32.3523, 31.4710
Bev AP: 38.7652, 35.5619, 34.8579
3D AP: 17.2034, 15.0750, 15.0462
AOS AP: 36.46, 32.01, 31.09
Car<EMAIL_ADDRESS>0.70, 0.70:
Bbox AP: 34.1645, 29.5950, 28.4427
Bev AP: 36.4198, 32.3735, 31.4788
3D AP: 14.3970, 12.3787, 11.8986
AOS AP: 33.77, 29.22, 28.09
Car<EMAIL_ADDRESS>0.50, 0.50:
Bbox AP: 59.9559, 52.9196, 51.8491
Bev AP: 59.0141, 51.9162, 51.0499
3D AP: 49.5782, 42.9737, 42.7284
AOS AP: 59.16, 52.15, 50.94
Car<EMAIL_ADDRESS>0.50, 0.50:
Bbox AP: 59.3984, 51.7946, 50.4342
Bev AP: 59.0424, 50.9988, 48.9314
3D AP: 48.2886, 41.6285, 39.8300
AOS AP: 58.52, 50.89, 49.54

Well, maybe there are some bugs in my code. I did it a year ago and I forgot many details.

Could you please upload the ImageSets file? I just randomly split the astyx dataset and follow your instructions but only get very poor performance.

Hello, I also tried to randomly partition the dataset, but the accuracy after reproduction is not good. Do you remember the performance results of reproduction?

For the baseline PointPillars with only LiDAR input, I got about 8 percent drop in 3D view at moderate level.

Thank you. Is it in<EMAIL_ADDRESS>0.5 0.5?
My reproduction result is like this, and it looks the same
Car<EMAIL_ADDRESS>0.70, 0.70:
Bbox AP: 36.8576, 32.3523, 31.4710
Bev AP: 38.7652, 35.5619, 34.8579
3D AP: 17.2034, 15.0750, 15.0462
AOS AP: 36.46, 32.01, 31.09
Car<EMAIL_ADDRESS>0.70, 0.70:
Bbox AP: 34.1645, 29.5950, 28.4427
Bev AP: 36.4198, 32.3735, 31.4788
3D AP: 14.3970, 12.3787, 11.8986
AOS AP: 33.77, 29.22, 28.09
Car<EMAIL_ADDRESS>0.50, 0.50:
Bbox AP: 59.9559, 52.9196, 51.8491
Bev AP: 59.0141, 51.9162, 51.0499
3D AP: 49.5782, 42.9737, 42.7284
AOS AP: 59.16, 52.15, 50.94
Car<EMAIL_ADDRESS>0.50, 0.50:
Bbox AP: 59.3984, 51.7946, 50.4342
Bev AP: 59.0424, 50.9988, 48.9314
3D AP: 48.2886, 41.6285, 39.8300
AOS AP: 58.52, 50.89, 49.54

Well, maybe there are some bugs in my code. I did it a year ago and I forgot many details.

Okay, thank you very much. After I reproduced it, I think there might be some issues with my code, too.
But in fact, I almost haven't changed the code, so I don't know how to solve it. I see that you have the same problem with the same performance, so I asked if you have solved it.

Could you please upload the ImageSets file? I just randomly split the astyx dataset and follow your instructions but only get very poor performance.

Hello, I also tried to randomly partition the dataset, but the accuracy after reproduction is not good. Do you remember the performance results of reproduction?

For the baseline PointPillars with only LiDAR input, I got about 8 percent drop in 3D view at moderate level.

Thank you. Is it in<EMAIL_ADDRESS>0.5 0.5?
My reproduction result is like this, and it looks the same
Car<EMAIL_ADDRESS>0.70, 0.70:
Bbox AP: 36.8576, 32.3523, 31.4710
Bev AP: 38.7652, 35.5619, 34.8579
3D AP: 17.2034, 15.0750, 15.0462
AOS AP: 36.46, 32.01, 31.09
Car<EMAIL_ADDRESS>0.70, 0.70:
Bbox AP: 34.1645, 29.5950, 28.4427
Bev AP: 36.4198, 32.3735, 31.4788
3D AP: 14.3970, 12.3787, 11.8986
AOS AP: 33.77, 29.22, 28.09
Car<EMAIL_ADDRESS>0.50, 0.50:
Bbox AP: 59.9559, 52.9196, 51.8491
Bev AP: 59.0141, 51.9162, 51.0499
3D AP: 49.5782, 42.9737, 42.7284
AOS AP: 59.16, 52.15, 50.94
Car<EMAIL_ADDRESS>0.50, 0.50:
Bbox AP: 59.3984, 51.7946, 50.4342
Bev AP: 59.0424, 50.9988, 48.9314
3D AP: 48.2886, 41.6285, 39.8300
AOS AP: 58.52, 50.89, 49.54

Well, maybe there are some bugs in my code. I did it a year ago and I forgot many details.

Okay, thank you very much. After I reproduced it, I think there might be some issues with my code, too.
But in fact, I almost haven't changed the code, so I don't know how to solve it. I see that you have the same problem with the same performance, so I asked if you have solved it.

hello,so have you solved the dataset split question？

Could you please upload the ImageSets file? I just randomly split the astyx dataset and follow your instructions but only get very poor performance.

Hello, I also tried to randomly partition the dataset, but the accuracy after reproduction is not good. Do you remember the performance results of reproduction?

For the baseline PointPillars with only LiDAR input, I got about 8 percent drop in 3D view at moderate level.

Thank you. Is it in<EMAIL_ADDRESS>0.5 0.5?
My reproduction result is like this, and it looks the same
Car<EMAIL_ADDRESS>0.70, 0.70:
Bbox AP: 36.8576, 32.3523, 31.4710
Bev AP: 38.7652, 35.5619, 34.8579
3D AP: 17.2034, 15.0750, 15.0462
AOS AP: 36.46, 32.01, 31.09
Car<EMAIL_ADDRESS>0.70, 0.70:
Bbox AP: 34.1645, 29.5950, 28.4427
Bev AP: 36.4198, 32.3735, 31.4788
3D AP: 14.3970, 12.3787, 11.8986
AOS AP: 33.77, 29.22, 28.09
Car<EMAIL_ADDRESS>0.50, 0.50:
Bbox AP: 59.9559, 52.9196, 51.8491
Bev AP: 59.0141, 51.9162, 51.0499
3D AP: 49.5782, 42.9737, 42.7284
AOS AP: 59.16, 52.15, 50.94
Car<EMAIL_ADDRESS>0.50, 0.50:
Bbox AP: 59.3984, 51.7946, 50.4342
Bev AP: 59.0424, 50.9988, 48.9314
3D AP: 48.2886, 41.6285, 39.8300
AOS AP: 58.52, 50.89, 49.54

Well, maybe there are some bugs in my code. I did it a year ago and I forgot many details.

Okay, thank you very much. After I reproduced it, I think there might be some issues with my code, too.
But in fact, I almost haven't changed the code, so I don't know how to solve it. I see that you have the same problem with the same performance, so I asked if you have solved it.

hello,so have you solved the dataset split question？

No, with such a small amount of Astyx data, different dataset partitioning should have a significant impact on the results.
If there is no split provided by the author, it may not be possible to directly compare the original results in the  paper. I suggest just using the results reproduced by oneself. In fact, I didn't use the Astyx dataset in the end because there are already many larger 4DRadar datasets available now.


Fix Setup config + only convert action space when convert is set to true

This should enable developer to still use discrete action spaces with a size bigger than 2.
I tested this with rllib and it seems to work but I am not sure if it will break anything else? What's your take on it?
I also fixed some issues with the initial setup.
There was a trouble with ray lib and I had to fix the numpy version.
You can read about it here: https://github.com/ray-project/ray/issues/31293#issuecomment-1379007369
Cheers

Thanks, looking good. Do you have an env in Godot that uses Discrete spaces > 2 ? Does this not need some changes on the Godot side as well?

Hey there,
I created this example which uses discrete spaces > 2 (3 to be exact). The agent learns and I didn't had to change anything in the godot environment. You can checkout the project here.
https://github.com/visuallization/godot-ml-platformer/blob/main/environments/platformer/PlatformerAgent.gd

The only issue I do get now while training with no convert in rllib is this warning.

Not yet sure where and if I can convert the observations to numpy arrays beforehand

In this line:
move_action = action["move"] if action["move"] <= 1 else -1

Even though action["move"] can be one of three values: 0,1 or 2. Is it converted to one of two values, -1 or 1?

Otherwise I think the logic is fine, it would just be nice to have an example which uses the three distinct actions.

In this line:
move_action = action["move"] if action["move"] <= 1 else -1

Even though action["move"] can be one of three values: 0,1 or 2. Is it converted to one of two values, -1 or 1?

Ah no actually it just transforms 2 to -1 and keeps 0 and 1 as they are. But I see that it is kind of hard to reason about for such a simple mapping and could need some rewriting :)

Ah yes you are right.

@edbeeching I was also thinking that with this change we should probably also set convert_action_space to True in the stable_baselines_wrapper because it only seems to work with conversion.

Yes I agree for the convert option

@visuallization do you want to make the same PR for th godot 4 branch?

@edbeeching yeah, just wanted to do that. Will create a new pr for this


Registry push failed; received status code 'PreconditionFailed'

When I push multiple images, I receive a PreconditionFailed error. Can you add--skip-duplicateoption like nuget to treat the error as a warning so that other image packages can push successfully

@Varorbc if you can reproduce this, could you add more error logging and/or a binlog so we can get a sense of how the pushes are failing specifically?

Sorry, another question - when you are pushing multiple images, are you pushing

multiple applications that have the same base images
same application, different TFMs
some mix-and-match of the above?

My suspicion is that because the publish is done on a per-project basis there's the possibility that multiple projects have shared layers and pushing the same layer to the registry simultaneously is what's causing the failure.
If that's the case, then for multi-project publishes (i.e. at solution level or Traversal props level) we'd need a more sophisticated system than we have today. We'd have to create all of the specific layers and report them back to some central process that could deduplicate and push each layer at most once.


Unable to access GPU when VirtualGL is installed

The following error would occur when trying to access the GPU inside a Docker container with non-root user on a system with VirtualGL installed:
$ nvidia-smi
Failed to initialize NVML: Insufficient Permissions

This is mentioned by @YuZhong-Chen on August 9th.
And reproduced by @ClassLongJoe1112 and @j3soon

This is because VirtualGL, by default, changes the group ownership of GPU devices to vgluers. For an example:
$ ls -l /dev | grep nvidia
drwxr-xr-x   2 root root           80 Aug  4 19:26 nvidia-caps
crw-rw----   1 root vglusers 195, 254 Aug  4 19:26 nvidia-modeset
crw-rw-rw-   1 root root     510,   0 Aug  4 19:26 nvidia-uvm
crw-rw-rw-   1 root root     510,   1 Aug  4 19:26 nvidia-uvm-tools
crw-rw----   1 root vglusers 195,   0 Aug  4 19:26 nvidia0
crw-rw----   1 root vglusers 195,   1 Aug  4 19:26 nvidia1
crw-rw----   1 root vglusers 195, 255 Aug  4 19:26 nvidiactl

To resolve this, there are two potential solutions.

Ask the server admin/IT to re-configure VirtualGL to not change the group ownership.

Run /opt/VirtualGL/bin/vglserver_config and unconfigure VirtualGL, see: https://rawcdn.githack.com/VirtualGL/virtualgl/main/doc/index.html#hd006006
Run /opt/VirtualGL/bin/vglserver_config and re-configure VirtualGL without changing the group ownership by setting No (n) for the following two options:Restrict 3D X server access to vglusers group (recommended)?
Restrict framebuffer device access to vglusers group (recommended)?

Modify Dockerfile to add the default user to vglusers group. However, since the vglusers group may have different Group ID (GID) across different machines, this approach cannot be made portable.

I believe the first solution is the best option, since the second solution is not portable across different machines.

Some related references:

https://forums.developer.nvidia.com/t/using-nvidia-docker-containers-as-non-root-user/235252
https://stackoverflow.com/q/52507744
https://stackoverflow.com/q/74554143
chown root:vglusers in https://github.com/VirtualGL/virtualgl/blob/main/server/vglserver_config

Hi @j3soon,
Please append the following argument to the command docker run when running a container on a VirtualGL-installed system.
--group-add $(getent group vglusers | cut -d: -f3)

Regards,
Kuan-Yu

Hi @KuanYuChang,
Thanks for sharing this. I hadn’t thought of adding a group when launching the container, which can access the GPU without modifying the Dockerfile.

Hi @YuZhong-Chen,
I think we can keep the Dockerfile intact, and use a hardcoded group ID in the compose.yaml on that specific machine for now. See this docs for adding the vglusers GID.
I'm thinking of a portable way to support this, which may be achieved through the following shell command:
(getent group vglusers || echo user:x:1000) | cut -d: -f3

which outputs the vglusers GID if it exists, and outputs 1000 otherwise.
Ref: https://stackoverflow.com/a/69987399
However, docker compose files doesn't seem to allow shell script expansion. We may need to use a wrapper for docker compose up to achieve this, which may be an overkill since VirtualGL may not exist in most systems.
Ref: https://github.com/docker/compose/issues/4081
I think we can leave this to the users when they're using machines with VirtualGL, and ask them to add the hardcoded GID in the docker compose files.
We can come back to this issue later if someone come up with a portable solution for docker compose. Thanks!

Self note:
The devcontainer will update the container's user UID and GID to match the local user. This will avoid permission problems with bind mounts. After hardcoding the group ID in the compose.yaml file, if you want to use devcontainer to launch the container, remember to add "updateRemoteUserUID": false, in the devcontainer.json file to prevent devcontainer update your UID and GID. Ref


Generalize ui:prop pattern

Prerequisites

[X] I have read the documentation;
[X] In the case of a bug report, I understand that providing a SSCCE example is tremendously useful to the maintainers.

Description
Right now we have several props for built in controls that are passed via uiSchema in 'ui:propName' format (disabled, readonly, autofocus, placeholder). When building custom widgets I'd love to pass other ui props to my widgets in a similar fashion.
const disabled = Boolean(props.disabled || uiSchema["ui:disabled"]);
const readonly = Boolean(props.readonly || uiSchema["ui:readonly"]);
const autofocus = Boolean(props.autofocus || uiSchema["ui:autofocus"]);

in code
As before; will PR
Implementation question if this makes sense: is there value to the uiSchema props having the ui: prefix? They are already in uiSchema so it's clearly UI related. Happy to implement either way but wanted to start that conversation as well.
Version: 0.40.0

Also how does this high level pattern relate to a ui:options as a bit of a grab bag. Aren't these all options of a sort? Should we perhaps generalize there instead?

See #370 which is related. So there's already a way to specify custom widget options, though I'm debating we move to supporting ui:options only. We may also go further and move everything to ui:options as suggested though I'm not entirely sure just yet. Please chime in #370 if you have thoughts about all that.

is there value to the uiSchema props having the ui: prefix? They are already in uiSchema so it's clearly UI related

Not sure to properly understand the question, but the reasoning is to disambiguate ui directives from field names; think of ui: as a JSON namespace if that makes sense.

Solved by #378 (#370).


wrapped the clean function inside a 'compile' event listener (fixes #25)

Fixes issue #25. I would write a test, I'm not sure how to write a test for the --watch parameter.

Coverage decreased (-69.2%) to 25.51% when pulling e9149f5a274c78c9e6f7a6ebc345e6aa54a38b78 on tylerhou:master into 9e78f40355c922be9d4c7b7838a5ef3aa22dbf31 on johnagan:master.

Coverage decreased (-69.2%) to 25.51% when pulling e9149f5a274c78c9e6f7a6ebc345e6aa54a38b78 on tylerhou:master into 9e78f40355c922be9d4c7b7838a5ef3aa22dbf31 on johnagan:master.

Coverage decreased (-69.2%) to 25.51% when pulling e9149f5a274c78c9e6f7a6ebc345e6aa54a38b78 on tylerhou:master into 9e78f40355c922be9d4c7b7838a5ef3aa22dbf31 on johnagan:master.

Coverage decreased (-69.2%) to 25.51% when pulling e9149f5a274c78c9e6f7a6ebc345e6aa54a38b78 on tylerhou:master into 9e78f40355c922be9d4c7b7838a5ef3aa22dbf31 on johnagan:master.

Coverage decreased (-69.2%) to 25.51% when pulling e9149f5a274c78c9e6f7a6ebc345e6aa54a38b78 on tylerhou:master into 9e78f40355c922be9d4c7b7838a5ef3aa22dbf31 on johnagan:master.

Okay, I just realized that this breaks every test there is because it changes the mechanism by which the plugin functions. The tests call the apply method, but instead this adds a listener to the "compile" event.
Tests should be rewritten with webpack-recompilation-simulator, which should be able to simulate the "compile" event.

Coverage decreased (-62.7%) to 32.0% when pulling 80ee9d37df223537a4362ecb7cddd15353c9b801 on tylerhou:master into 9e78f40355c922be9d4c7b7838a5ef3aa22dbf31 on johnagan:master.

Coverage decreased (-62.7%) to 32.0% when pulling 80ee9d37df223537a4362ecb7cddd15353c9b801 on tylerhou:master into 9e78f40355c922be9d4c7b7838a5ef3aa22dbf31 on johnagan:master.

Coverage decreased (-1.7%) to 93.0% when pulling 28f400ca36c62b089863ec2274ebf6ae5643cd10 on tylerhou:master into 9e78f40355c922be9d4c7b7838a5ef3aa22dbf31 on johnagan:master.

Coverage decreased (-1.7%) to 93.0% when pulling 28f400ca36c62b089863ec2274ebf6ae5643cd10 on tylerhou:master into 9e78f40355c922be9d4c7b7838a5ef3aa22dbf31 on johnagan:master.


Updated product icons

Description
We have a new icon and we are updating our product icons to use it.

Old vs New

Xcode vs CodeEdit

TextEdit vs CodeEdit

In the dock

They look nice 😊

Great work Austin. Love it!


Fix ViewPropTypes warning

After upgrading to React Native 0.68, I started seeing this warning: ViewPropTypes will be removed from React Native. Migrate to ViewPropTypes exported from 'deprecated-react-native-prop-types'.
Personally, I don't love the suggested solution, but I don't know what the alternative is (I asked about better alternatives here).
I based this PR off of a similar PR for react-native-maps.
It's unfortunate that this fix requires adding the first and only dependency to this package, but without adding deprecated-react-native-prop-types to dependencies, anyone who wants to use this package would need to have their own copy of deprecated-react-native-prop-types installed, which would be annoying.

Fixes #222

Update: Got a reply from someone on the React team about the "right" way to fix this. Apparently they want everyone to start using Flow or Typescript instead of relying on prop types.
Migrating to Flow or Typescript would be a much bigger change though, and probably isn't worth doing just to fix this one warning.

Personally, I would greatly appreciate for this pr to be merged since this is the only package I have left which creates this warning :)
Thanks for the great work!

Hi,
Any update on this?

Hi, Any update on this?

I wish! @mrlaessig Any chances of this getting merged?
Thanks :)

This library is now raising an error (was a warning), when opgrading to react native 0.69. Merging this PR now it's pretty important.

Any news on this PR ? It is breaking RN 0.69.

If some people need that urgently, you can still use https://www.npmjs.com/package/patch-package. Working well applying changes in this PR. Not ideal but can save a build.

having the same issue. would be great to merge this!


Could not resolve non-primitive black box cell 'system_Video_PR_0_0Video_Box'

I ran make (no errors) and then tried to generate bitstream using Vivado 2016.3, and I get the following warnings/errors, in Messages tab:
Implementation
Design Initialization
[Project 1-486] Could not resolve non-primitive black box cell 'system_Video_PR_0_0Video_Box' instantiated as 'system_i/video/Video_PR_0/U0/Video_PR_v1_0_S_AXI_inst/Video_Box_0' ["PYNQ_PR_Overlay/Pynq-Z1/vivado/base/base/base.srcs/sources_1/bd/system/ipshared/4ea0/hdl/Video_PR_v1_0_S_AXI.vhd":209]
Opt Design
[DRC 23-20] Rule violation (INBB-3) Black Box Instances - Cell 'system_i/video/Video_PR_0/U0/Video_PR_v1_0_S_AXI_inst/Video_Box_0' of type 'system_i/video/Video_PR_0/U0/Video_PR_v1_0_S_AXI_inst/Video_Box_0/system_Video_PR_0_0Video_Box' has undefined contents and is considered a black box.  The contents of this cell must be defined for opt_design to complete successfully.
[Vivado_Tcl 4-78] Error(s) found during DRC. Opt_design not run.
Any idea how to fix it?

What script were you running when this happened?
If you try to build the normal design with no script, there is nothing loaded in the partial design module.
And you will see this issue.
If you ran, the base.tcl and the build_static_design.tcl,
It sounds like a design was not loaded into the partial region.
Inside build_static_design.tcl:
...
//Opens static region, If you look through the netlist you will see a ? for system_i/video/Video_PR_0/U0/Video_PR_v1_0_S_AXI_inst/Video_Box_0
open_checkpoint ./Static/top.dcp
//this loads a pass through design into the cell, but the names need to be the same. You shouldn't see a ? anymore in the netlist
read_checkpoint -cell system_i/video/Video_PR_0/U0/Video_PR_v1_0_S_AXI_inst/Video_Box_0 Synth/pass_through.dcp
set_property HD.RECONFIGURABLE 1 [get_cells system_i/video/Video_PR_0/U0/Video_PR_v1_0_S_AXI_inst/Video_Box_0]
write_checkpoint -force ./Checkpoint/pr_block_design.dcp
..
This should work now.
Also, this project got moved to an Offical Github for BYU.
https://github.com/byuccl/BYU_Senior_PYNQ_Project

Thanks!
I'll continue reporting here:
https://github.com/byuccl/BYU_Senior_PYNQ_Project/issues/1


Packaged

Hi @louise652, thank you for the PR. I have merged jackall3n's debounce PR in https://github.com/labd/react-loqate/pull/13.
Could you explain to me what the value of the rest of this PR is?

Sorry, I unintentionally opened this PR while experimenting with the lib


doc: clarify links usage of page title with spaces

The word space can be misleading in this context since it can be confused as 'Confluence Space'.
It happened to me.

Thanks for the PR!


[Question] Plugin fails without {Error}

I'm trying to minify my CSS with cssnano but the plugin fails without ever producing any errors. If cssnano is set to execute first, then the following plugins, e.g. autoprefixer never get called also.
Please see the problem reproducing project: https://github.com/malydok/postcss-loader-plugin-fail
postcss.config.js

plugins: {
  'cssnano': {},
  'autoprefixer': {},
}

webpack.config.js

ℹ  extractSass is an instance of ExtractTextPlugin
{
  test: /\.scss$/,
  use: extractSass.extract({
    fallback: 'style-loader',
    use: [
      'css-loader',
      'sass-loader',
      'postcss-loader'
    ]
  })
}

Environment

package.json
"devDependencies": {
  "autoprefixer": "^7.1.6",
  "css-loader": "^0.28.7",
  "cssnano": "^3.10.0",
  "extract-text-webpack-plugin": "^3.0.2",
  "postcss-loader": "^2.0.8",
  "sass-loader": "^6.0.6",
  "style-loader": "^0.19.0",
  "webpack": "^3.8.1"
}

OS
node
npm
postcss-loader

Windows 10
6.9.5
3.10.10
2.0.8

Could you try using postcss-reporter (added after cssnano) and see if you get any warnings ?  postcss-loader handles errors, warnings emitted via result.messages, but can't do anything if the plugin doesn't have support for this mechanism

postcss-reporter didn't spit out any warnings so I decided to dig around a bit and finally found that it was sass-loader which caused the problem. A moment later I read in postcss-loader documentation the following sentence:

Use it after css-loader and style-loader, but before other preprocessor loaders like e.g sass|less|stylus-loader, if you use any.

Which solves the case. Thanks a lot and sorry for not reading the docs properly (happens to us all I guess).

Oops 😅 I also didn't catch it...


Elastic.Ingest.Transport Nuget Package 0.5.5 references Elastic.Transport 0.4.16 causing bug

Package version 0.5.5 references Elastic.Transport  >= 0.4.13. This is causing the package to use Elastic.Transport version 0.4.16 when installed.
This is causing a bug in LibraryVersion class...it tries to call StoreVersion() in the base class VersionInfo, but that method does not exist in 0.4.16.  Possible to set the package to use 0.4.13 until fixed?

Thank you for raising this and apologies for this completely flying under my radar.
Addressing this as per: https://github.com/elastic/elastic-ingest-dotnet/pull/47


Views

Use preprocessed HTML file with embedded Ruby code.
Use layouts and templates for shared content.

@rotimiazeez thanks for the review.


[Web Application] - Auto redirect to HTTPS

As a user, I want the application to automatically redirect me from http to https

We have moved this issue to Sprint#3 as we are only now able to fix it.

This issue was originally resolved in #36 however, was left open due to it seemingly not working.
The issue is however related to the application not running with root privileges on the server (which we do not want it to have)
This is therefore resolved by running the following commands as root (in our case we are running an Ubuntu 20.04 server, however, these commands will differ accroding to your hosting enviroment), which will internally forward the relevant ports.

You should also ensure that the relevant ports are open in your firewall

iptables -A INPUT -i eth0 -p tcp --dport 80 -j ACCEPT
iptables -A INPUT -i eth0 -p tcp --dport 443 -j ACCEPT
iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 8080
iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 443 -j REDIRECT --to-port 8443


Update to latest Dart and Flutter

Update to latest flutter and dart https://docs.flutter.dev/release/archive

[ ] run build.sh

I'll make some changes and get some new containers deployed


Allow skinned models to share bones

I'm not sure if this is already supported but allowing models to share bones would be a useful optimization.
If you have a player model with clothing attached (that share the same skeleton structure) there's no reason to set the bones when they could use the master pose.

I don't think there's anything preventing you from doing this? You just need to set the same transforms on two meshes. The skinning itself is done on the GPU so that will still happen per mesh. We've talked about caching this data but it hasn't been a priority so far.

The call to RenderableManager::setBones is still doing unnecessary work. You should be able to reuse the same buffer that the master pose has already has on the GPU if it's exactly the same.

Like I said we don't cache the output of skinning at the moment so we can't share the skinning itself. It would be easy to add a version of setBones() that expects data already in the right format for sharing though.

Is it not possible to share the same uniform buffer? I know using texture buffers for gpu skinning you can just reuse the same buffer if the skeletons match.

We can share the UBO but it just contains the transform data. If that's all you want to share then that's easy but it's not the expensive part of the process. We'll still reapply all the transforms to the vertices in the GPU shader.

Yeah it's just the updating of the UBO I'm on about. If they're not that expensive to update then maybe it's fine how it is. I'm thinking of the situations where you have many bones and lots of clothing attached to a player model, surely uploading the same data to a UBO once is much better than 10 or so times.

Oh yeah it's definitely better, no argument here :)

Very interesting use case.


[dv] Randomize code and stack regions for PMP tests

When running the riscv_pmp_full_random_test, we want it to choose a random entry to give execution privilege to instructions and read/write privilege to the stack. This issue was initially a part of subtask 2 of this issue: https://github.com/lowRISC/ibex/issues/1702

estimate 16
remaining 2022-08-16 12

One extra issue that I ran into today is that whenever region 0 is set to TOR, this overrides the code region most of the time because the base of the TOR region is always assumed to be 0. We don't want to stop it from generating this all the time, but maybe making it less likely than 25% of the time is a good idea.

I've updated the PR: https://github.com/google/riscv-dv/pull/885

Fix constraints with MML
Remove constraint on NAPOT
Add a PMP entry to continue access to stack and signature address in case of MML and MMWP

I'm now waiting for reviews on this PR, which has grown quite big.

spent 4

I updated https://github.com/google/riscv-dv/pull/885 based on @ctopal's comments, and they got merged into the main branch.

spent 2

I created a pull request https://github.com/lowRISC/ibex/pull/1790, which should close this issue in case it gets approved.
I've adjusted the estimate of this issue downwards because I expect the effort to be minimal from here onward. Also, some of the effort that I had initially planned for this task now falls onto a new issue: https://github.com/lowRISC/ibex/issues/1789

spent 2


Remove deprecated WinGet package for March 2024 GDK

Remove deprecated WinGet package for March 2024 GDK
Microsoft Reviewers: Open in CodeFlow

@microsoft/xbox-developer-experience-toolbox for review

URL: https://github.com/microsoft/GDK/archive/refs/tags/March_2024.zip
Status Code: 200
(Automated message - build 897)


Ability to reload headscale in docker container

Why
Currently headscale supports reloading config on kill -HUP signal which has no downtime, but headscale in docker do not have kill or equivalent command. I forced to restart whole container to apply changes which may result unavailability of service.

Description
It would be great if headscale will watch config.yaml and acl.yaml files for changes and  gracefully reloads them on changes. Less elegant but more straightforward approach would be adding kill command into docker image, so admin can call docker exec kill -HUP ... to reload config inside container.

Ok, after quick digging, I found that I can actually docker kill --signal HUP headscale which forces to reload config, but still, it would be great if headscale will automatically reloads configs on changes.

Dupe https://github.com/juanfont/headscale/issues/173


UnivTransferType enum doesn't support MAIN_FUNDING and FUNDING_MAIN types

Add universal transfer type MAIN_FUNDING and FUNDING_MAIN from documentation https://binance-docs.github.io/apidocs/spot/en/#user-universal-transfer-user_data.
Fix: https://github.com/binance/binance-connector-typescript/pull/10

The fix has been added to the latest release.


[Bug] (Select) item rows are larger than the select control size

Comparison

Demo Page
When Used

Page
@page "/"

Select

        <Select Items="@fruits" Placeholder="Select a fruit" Width="200px" Display="x => x" TItem="string" SelectedItem="@selectedItem" OnItemSelect="x => selectedItem = x"/>

Form example

        <Select Label="Email" Info="You can manage email addresses in your email settings." Items="@emails" Display="x => x"
                TItem="string" SelectedItem="@selectedEmail" OnItemSelect="x => selectedEmail = x" Width="400px"/>

        <Button Text="Submit" Width="fit-content"/>

@code
{
    string[] fruits = ["**Fruits**", "Apple", "Banana", "Blueberry", "Grapes", "Pineapple"];
    string? selectedItem = "Grapes";

    string[] emails =<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>    string? selectedEmail =<EMAIL_ADDRESS>}

Index.html
<!DOCTYPE html>

    <meta charset="utf-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <title>ShadcnInspired</title>
    <base href="/" />
    <link rel="stylesheet" href="css/app.css" />
    <link rel="icon" type="image/png" href="favicon.png" />
    <link href="manifest.webmanifest" rel="manifest" />
    <link rel="apple-touch-icon" sizes="512x512" href="icon-512.png" />
    <link rel="apple-touch-icon" sizes="192x192" href="icon-192.png" />
    <link href="ShadcnInspired.styles.css" rel="stylesheet" />
    <link href="_content/Sysinfocus.AspNetCore.Components/styles.css" rel="stylesheet" />
    <link href="_content/Sysinfocus.AspNetCore.Components/Sysinfocus.AspNetCore.Components.bundle.scp.css" rel="stylesheet" />

        <svg class="loading-progress">
            <circle r="40%" cx="50%" cy="50%" />
            <circle r="40%" cx="50%" cy="50%" />
        </svg>

        An unhandled error has occurred.
        Reload
        🗙

In your css/app.css file add the following at the top and see if it fixes:

{
margin: 0;
padding: 0;
box-sizing: border-box;
}

Tried with the following scenarios:

Add to app.css, keep existing contents, re-run and clear caches: issue persists
Add to app.css, remove other contents, re-run and clear chaches: issue persists

It is definitely the padding issue, can you inspect with developer tools what is adding those padding from?

Layout information from dev tools:

Newly observed behavior: Adding tailwind cdn seems to fix the issue

There is definitely some css overriding it as the height should be 32px pixels but in your case it is showing 48px.

This looks specific to your environment as we haven't entered any issues like this before, unless someone has explicitly modified the css. I am closing this issue as it is not related to the library as such. Feel free to open a new one, if you think it is related to library.

Understandable, for the meantime I'll go with the tailwind css fix and see if this can be reproducible in other environments


Where to put the Checkpoint ?

Hi,
Where to put the Checkpoint "
tooncrafter_512_interp-fp16.safetensors" please?
I try your path:
ComfyUI-ToonCrafter\ToonCrafter\checkpoints\tooncrafter_512_interp_v1
and I've try to put it everywhere else but still have this error message:
Required input is missing: ckpt_name
Thanks,
Olivier

I have the same error, and I want someone to tell me the solution

the same error

I found it !!! If we install the model directly from the Manager of ComfyUI, he will put it in this path: ComfyUI\models\checkpoints\ToonCrafter And it works but it's very slow!!! 40% after 40 minutes!!!

I found it !!! If we install the model directly from the Manager of ComfyUI, he will put it in this path: ComfyUI\models\checkpoints\ToonCrafter And it works but it's very slow!!! 40% after 40 minutes!!!

It doesn't work

ComfyUI-ToonCrafter\ToonCrafter\checkpoints\tooncrafter_512_interp_v1

Put into ComfyUI-ToonCrafter\ToonCrafter\checkpoints\tooncrafter_512_interp_v1\ is correct!
Such as ComfyUI-ToonCrafter\ToonCrafter\checkpoints\tooncrafter_512_interp_v1\xxx.ckpt.
Maybe restart is required.

I found it !!! If we install the model directly from the Manager of ComfyUI, he will put it in this path: ComfyUI\models\checkpoints\ToonCrafter And it works but it's very slow!!! 40% after 40 minutes!!!

I found it !!! If we install the model directly from the Manager of ComfyUI, he will put it in this path: ComfyUI\models\checkpoints\ToonCrafter And it works but it's very slow!!! 40% after 40 minutes!!!

It doesn't work

Like this ComfyUI-ToonCrafter\ToonCrafter\checkpoints\tooncrafter_512_interp_v1\xxx.ckpt.

ComfyUI-ToonCrafter\ToonCrafter\checkpoints\tooncrafter_512_interp_v1

Put into ComfyUI-ToonCrafter\ToonCrafter\checkpoints\tooncrafter_512_interp_v1\ is correct! Such as ComfyUI-ToonCrafter\ToonCrafter\checkpoints\tooncrafter_512_interp_v1\xxx.ckpt. Maybe restart is required.

yes, it is work for me. thanks bro. restart is important

ComfyUI-ToonCrafter\ToonCrafter\checkpoints\tooncrafter_512_interp_v1

Put into ComfyUI-ToonCrafter\ToonCrafter\checkpoints\tooncrafter_512_interp_v1\ is correct! Such as ComfyUI-ToonCrafter\ToonCrafter\checkpoints\tooncrafter_512_interp_v1\xxx.ckpt. Maybe restart is required.

Thx matte, it worked for me =).


calling constructor with no variables does not throw an error

Calling Sendgrid() means that apiUserOrKey, apiKeyOrOptions are both undefined. The first if is false, the second if is true and this.api_key becomes undefined.
 var Sendgrid = function(apiUserOrKey, apiKeyOrOptions, options) {

  if( !(this instanceof Sendgrid) ) {
    return new Sendgrid(apiUserOrKey, apiKeyOrOptions, options);
  }

  // Check if given a username + password or api key
  if (typeof apiKeyOrOptions === 'string') {
    // Username and password
    this.api_user = apiUserOrKey;
    this.api_key  = apiKeyOrOptions;
    this.options  = options || {};
  } else if (typeof apiKeyOrOptions === 'object' || apiKeyOrOptions === undefined) {
    // API key
    this.api_key  = apiUserOrKey;
    this.api_user = null;

    // With options
    this.options = apiKeyOrOptions || {};
  } else {
    // Won't be thrown?
    throw new Error('Need a username + password or api key!');
  }

Thanks @remkoboschker!
Our new forthcoming ruby library, based in this client https://github.com/sendgrid/ruby-http-client, will no longer support the username/password option, so this will not be an issue moving forward.


Error will be reported in IE / edge browser when el-pagination contains slot

Element UI version
2.10.1
OS/Browsers version
windows/edge，ie11
Vue version
2.6.10
Reproduction Link
https://codepen.io/kenzid/pen/dyyBaNm
Steps to reproduce
打开edge浏览器，打开开发者工具，console中报错
What is Expected?
不报错
What is actually happening?
报错：[Vue warn]: Unknown custom element: slot> - did you register the component correctly? For recursive components, make sure to provide the "name" option.

想问一下楼主解决了这个问题了么，现在也遇到了同样的问题。


Added Israeli flag

Hi!
I already submitted this change in #58 but since then, conflicts were created. @ManrajGrover asked me to resolve them; I tried to no avail, so I decided to just fix the conflict manually and re-submit :)
Cheers,
Hillai

@hillai I'll review this soon :smile: Thank you again!


ENH/DEP: integrate: Use opts arg in dbl/tplquad

Reference issue

closes gh-16086
What does this implement/fix?

Allow the user more control over which integration method is used. This is achieved by giving the user access to the opts   parameters in dblquad and tplquad.
Additional information

This introduces some backwards compatibility issues, as epsabs and epsrel are already passed as keyword arguments. For now these will be ignored for now. I tried to overwrite epsabs and epsrel  but this won't always work because opts may be an iterable of callables.
This is a draft/proof of concept, any feedback is welcome

@mdhaber I think this is nearly ready, could you take a look if you can re-run the CircleCI test - apparently I don't have the right permissions to merge the branch with upstream.

Locally, just:
git  checkout expand_opts_for_dbl_tpl_quad
git fetch upstream
git merge upstream/main
git push origin expand_opts_for_dbl_tpl_quad

Is this all set @Kai-Striega ? Want us to look again or are there still unresolved comments or other changes?

This should be done, but you're welcome to take another look. I've been pretty busy working and haven't had as much time to go through it as I would like.
There are two outstanding comments from @mdhaber here here that I'd like to resolve before merging.

@mdhaber could you help find those non-printable characters? It's the character \x07 in both instances. I've tried finding it by using grep (grep -P -n \x07 scipy/integrate/_quadpack_py.py) and the following script, neither of which return anything.
file_name = 'scipy/integrate/_quadpack_py.py'
with open(file_name, 'r') as file:
    for line_number, line in enumerate(file):
        for character_number, character in enumerate(line):
            if character == "\x07":
                print(line_number, character_number)

@Kai-Striega was this ready for another look or were you still working on those unresolved comments?

This is ready for another look. There are also two outstanding comments https://github.com/scipy/scipy/pull/16106#discussion_r867496870 and https://github.com/scipy/scipy/pull/16106#discussion_r867496739 that I'd like to resolve before merging. @mdhaber

I'd prefer to wait until those are resolved before taking a final pass.

@j-bowhay thanks for the review, I've implemented all your suggestions :)
@mdhaber all your review suggestions have been implemented, and it should be ready to merge. Would you please give it the final ok?

@mdhaber looks like this is waiting for final approval from you? CI hasn't been flushed in 4 months so we should do that too if we want this in by Tuesday.

I just realized that this did not just deprecate the arguments, it immediately began to ignore them. Before the arguments are removed, they should still continue to work by combining the information in them and opts.

I removed the milestone because even after my work today, there still needs to be a test that passing opts is doing the right thing, and this needs discussion on the mailing list before it can be merged. Also, since I've done a fair amount of work here, I shouldn't be the one to do a final review and merge.


Show MMFiles deprecation warning

Print that MMFiles is deprecated.
Jenkins:
http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/7549/

i have seen this printed twice on my Database server now.
(Not too much of an issue to me though)

i have seen this printed twice on my Database server now.

I cannot reproduce that. Is it the same log id in both cases @mchacki?

Yes it is,
2019-12-04T16:44:34Z [55574-0] WARNING [bd666] ==============================================================================
2019-12-04T16:44:34Z [55574-0] INFO [144fe] using storage engine 'mmfiles'
2019-12-04T16:44:34Z [55574-0] WARNING [80866] {startup} The MMFiles storage engine is deprecated starting with ArangoDB v3.6.0 and will be removed in a future version. Please plan for a migration to the RocksDB engine.
2019-12-04T16:44:34Z [55574-0] INFO [43396] {authentication} Jwt secret not specified, generating...
2019-12-04T16:44:34Z [55574-0] WARNING [80866] {startup} The MMFiles storage engine is deprecated starting with ArangoDB v3.6.0 and will be removed in a future version. Please plan for a migration to the RocksDB engine.
2019-12-04T16:44:34Z [55574-0] INFO [3bb7d] {cluster} Starting up with role PRIMARY

maybe this is only in "recovery" cases or something like this?
I did use startLocalCluster script.

I tried for some time, and still could not reproduce that even once.
Blue Jenkins: http://jenkins.arangodb.biz:8080/job/arangodb-matrix-pr/7565/


3.Sprinting - Start coding phase - DB Creation ( tables and realation in details )

Services table ( service_id , serviceName)
products ( product_ id , Produc_Name,Product_Desc , price)
contactus(Contact_id , Name, Subject , messgae )

Coding review:

Positive aspects

DB has a clear and consistent structure
logic subject division
separate table for each functional page
additional tables for detalization
meaningful table and column nomination

Aspects to improve

verify if any additional tables need to be added by owner request
verify simplicity of scalability


Pass dependencies as parameters

So that dependencies can be overridden to point to local nix repositories.
{ deps ? ../deps.nix, commons-io ? deps.commons-io, ... }

Thanks @tomtau