size specifiers not highlighted

byte, word, ... are not being highlighted
mul byte [two]
mov al, byte[a]

Currently they're being marked as "operators" so I think this is just your theme. Would it make sense to you for them to be marked differently?

@Starrlightz I'm going to close this soon since there hasn't been an update and this hasn't been confirmed as unexpected behavior.


Not receiving notifications when app is closed

unable to receive notifications when the app is closed.
Code written:
let push = Push.init({
android: {
senderID: [SENDER_ID]
}
});
push.on('registration', (data) => {
console.log(data.registrationId);
});
push.on('notification', (data) => {
console.log(data.message);
console.log(data.title);
console.log(data.count);
console.log(data.sound);
console.log(data.image);
console.log(data.additionalData);
});
push.on('error', (e) => {
console.log(e.message);
});
}
and also, what is the frequency of device id getting changed?

@charithvalluru do you mean when the app is in the background or when the app has been killed? If you want the notification event called when the app is in the background see the docs on Background Notifications. If you want your notification to be called when the app is killed then that is not currently supported.
The device ID does not change very frequently.


Deprecation of the Apache Aurora Scheduler in Apache Heron

It is the intention of the Apache Heron (Incubating) development team to deprecate support for Apache Aurora in a subsequent release. Apache Aurora was placed in the Attic in February of 2020 with development and support ceasing. For further information please refer to this page.

We are currently using mainly apache aurora/mesos.  And although attic https://github.com/aurora-scheduler still has a lot of users

I have traced the path for removal in the event there is a desire to in the future.


added code to HTML file

Added sections to the body of the html code

Need to resolve merge conflict


Support Azure endpoints

I don't have access to the Azure API so I have no way to test it personally. But feel free to submit a PR.
Going to support https://openrouter.ai in the future

I actually don't think the Azure has the vision model yet.

Looks like they're bringing this to Azure soon: https://techcommunity.microsoft.com/t5/ai-azure-ai-services-blog/gpt-4-turbo-with-vision-on-azure-openai-service/ba-p/3979933

i can support u a azure key.
can u support?
Yoh
---Original---
From: "Abi @.>
Date: Fri, Nov 17, 2023 21:50 PM
To: @.>;
Cc<EMAIL_ADDRESS>Subject: Re: [abi/screenshot-to-code] can u support azure api  (Issue #10)
I don't have access to the Azure API so I have no way to test it personally. But feel free to submit a PR.
Going to support https://openrouter.ai in the future
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Azure has GPT4 access but only in this region

Sweden Central
Canada East
Switzerland North

I'm already testing screenshot-to-code with AzureAPI, needed small help to finish it

Feel free to open a PR

Azure has GPT4 access but only in this region

Sweden Central
Canada East
Switzerland North

I'm already testing screenshot-to-code with AzureOpenAIAPI, needed small help to finish it

How can i help you?

Would be good to have a clean PR that allows for switching between OpenAI and Azure. I have Azure access now so can test it.

Would be good to have a clean PR that allows for switching between OpenAI and Azure. I have Azure access now so can test it.

Here the PR: https://github.com/abi/screenshot-to-code/pull/186

@cristianorevil amazing! Will merge it in the next couple of days.

Merging with #261


ci: try to debug trybuild issue

For #1865
I get the same output as everyone else locally, for some reason the error message is cut off in CI. Just adding the code which fails to compile to a different file so we can see what CI gives us...

We learned what we wanted; closing!


fix: updated default regions for sandbox-gke and private-sql examples

This is a small  PR that addresses the mislabeled regions  mentioned in #278 and sets any remaining regions set to use us-central1 to be northamerica-northeast1 as a default.

@fmichaelobrien wish I could take credit but it was all @lucstjean-ssc ! Updated the Artifact Registry depends-on annotation as well to address # #304


Incident that last for more than one day

For an incident that is not solved the same day it has been created, it is still displayed and "attached" to the day it has been created in the "Past incidents" timeline. So we can think that the incident is old and fixed.
It would be nice to be able to see easily incidents that are still ongoing. Maybe by displaying them like a scheduled maintenance? (in a specific panel below Components status?)
And then, when the incident status is changed to "fixed", move it from the "Ongoing incident panel" to the Past incidents timeline. I don't know if the incident should be duplicated to each day it last or not but we may need to see that it last for 2 days or more.
Also, it would be nice to be able to display, in the Past Incidents section, only days with an event.

This is something we're addressing in V2. Since we have this within other issues, I'm going to close this one :)


Unattended extension installation

Is your feature request related to a problem? Please describe.
In an environment where workstations are ephemeral, and users do not have administrator access, we pre-bake a workstation image using packer.  This creates a problem when a feature, such as installing Extensions for AZD, does not have an off-line installer
Describe the solution or feature you'd like
A command line tool, or power-shell script, that can be used to add an Extension to Azure Data Studio once it is installed on the temporary instance used by packer to create the re-usable install image.
Describe alternatives you've considered
Our users have tried to install the PostgreSQL Extension onto their workstations themselves, but appear unable to do so without Administrator rights.
Additional context

I'd like to amend the last sentence of my first paragraph.  I ended it with "does not have an off-line installer".  I should have said "does not have a command-line installer".  ADS supports the off-line installation of extensions; but that still has to be done via the GUI, which isn't possible in the described scenario.

Does using the --install-extension option not cover your scenario?

--install-extension
Install an extension. Provide the full extension name publisher.extension as an argument. Use --force argument to avoid prompts.

@Charles-Gagnon - I had not encountered that in the ADS documentation or when searching for a solution.  Let me give that a try, and I'll close this if it works.

Yeah it looks like that's a gap in our documentation. You can see the available options by running
azuredatastudio --help
from a command prompt or by looking at https://code.visualstudio.com/docs/editor/command-line (we have the same ones they do + a few extras such as server & database for starting with an existing connection open)

And note that you can give the full path to a VSIX as well if you want to do a truly off-line install of an extension

I'm going to close this now since this should resolve your ask - let us know if this doesn't cover your needs completely!

@Charles-Gagnon I've added the installation of the extension to our packer build, and it seems to complete without any errors.  But when I deploy a new instance and launch Azure Data Studio I don't see PostgreSQL as an available connection type, and then when I go to View/Extensions I see the PostgreSQL extension as available to be installed.  Seems like the command line install didn't work.

@Charles-Gagnon I do see a message that preview features need to be enabled for extensions.  Can preview features be enabled via the command line prior to the extension install?  I don't see a command line option for that.
It does seem that having updated to 1.11.0 to make sure I'd tried everything possible that extension installation no longer requires admin privs, so even though command line install of the extension doesn't seem to work my users are now able to self service.  So I guess I've got that going for me.  :)

@ghstwhl Are you calling the exe directly? You need to invoke the cmd file instead for command-line options to work :
"%LOCALAPPDATA%\Programs\Azure Data Studio\bin\azuredatastudio.cmd" --install-extension microsoft.azuredatastudio.postgresql
the above worked for me just fine.
For enabling preview features I don't believe there's a way to do that directly. But you can modify "%APPDATA%\azuredatastudio\User\settings.json" to set the value yourself. If this is always going to be a clean install then you can just use the attached settings.json - copying it to the above location after installing.
settings.zip

@Charles-Gagnon This is the powershell I use to install the extension.  It works when I run it by hand; but while it runs without error in my build system the resulting image doesn't have the extension installed.  Since the command line option to install works when I run it by hand, the problem is clearly in my build system and not with the functionality itself.  Thank you for all your help.
`Try {
# Set Variables
$version = '0.2.1'
$installerBinary = "azuredatastudio-postgresql-$version-win-x64.vsix"
$installerSource = "https://github.com/microsoft/azuredatastudio-postgresql/releases/download/v$version/$installerBinary"
$targetPath = 'c:\temp'
$installOptions = "--install-extension   $targetPath$installerBinary"
# Download executable
Write-Output "Ensure download target exists"
New-Item -ItemType Directory -Force -Path $targetPath
[System.Net.ServicePointManager]::SecurityProtocol = [System.Net.SecurityProtocolType]::Tls12
Write-Output "Retrieving $installerSource into $targetPath\$installerBinary"
Invoke-WebRequest -Uri "$installerSource" -OutFile "$targetPath\$installerBinary"

# Run installer
Write-Output "Installing $targetPath\$installerBinary"
Start-Process -NoNewWindow -FilePath "C:\Program Files\Azure Data Studio\bin\azuredatastudio.cmd" -ArgumentList "$installOptions" -Wait -PassThru

}
Catch {
# If error, output and exit with a status of 1
Write-Output $_
[System.Environment]::Exit(1)
}
`


undefined method `shift' for :authorization_rules:Symbol

Hi, when I try to execute http://localhost:3000/authorization_rules I've got the error:
"undefined method `shift' for :authorization_rules:Symbol"
NoMethodError - undefined method shift' for :authorization_rules:Symbol:   declarative_authorization (0.5.7) lib/declarative_authorization/development_support/analyzer.rb:212:in process_call'
I'm using Rails 4.0.0 and Ruby 1.9.3

@stffn, is this fixed as part of the latest published gem? (doesn't seem like it as per rubygems 0.5.7 is the latest version which was published before this was fixed).
Thanks


crane registry serve daemons are not cleaned up

When executing build actions locally, crane registry serve processes are cleaned up after a bazel build.
However, when using remote execution (in my case with buildbarn), crane registry serve processes survive between actions and pile up over time on the remote executor. This results in hundreds of processes and will starve the host of memory over multiple days.
How to reproduce

setup a buildbarn cluster (for example using the docker-compose setup)
Use the buildbarn cluster for remote execution (--remote_executor=...)
use rules_oci to build container images
Look at the running processes after the build is complete

Expected behavior
crane registry serve should no longer run
Actual behavior
crane registry serve processes are still running

Hm, do you think this is a bug in rules_oci, or a problem with how buildbarn terminates the worker process?
Based on 5 thumbs up I'm inclined to believe it's a bug, somewhere we get a process terminated and trap the signal, or fail to propagate the signal. Perhaps we need to explicitly use a process group somewhere?
We'll probably need help to troubleshoot this.

I’m not entirely sure what’s happening, but my current understanding is this:
When running builds locally (only using Bazel to run build actions), sandboxing (or some other mechanism of Bazel) cleans up processes spawned by actions.
For some reason, this doesn’t work in buildbarn (maybe because it doesn’t try to perform per-action sandboxing).
This is combined with the design of buildbarn, where workers are long-living.
The thing that confuses me here is that, by my investigation, it seems that for a large-ish monorepo that I’m testing this on, the crane/zot registry is the only process that is leaking. This makes me think that it might be a convention in Bazel to clean up any spawned processes if you are writing rules?


Flutter Web: Google Chrome desktop mode shows blank page in portrait

Steps to reproduce
Open any Flutter web app  (like https://flutterweb-wasm.web.app/) on Android (real device or emulator) with Google Chrome, desktop mode and portrait. When I load the app in landscape, it loads. When I switch from landscape to portrait, the app loads but is distorted. This issue does not exist when I build the app as HTML.
Expected results
Web app is displayed as desktop version.
Actual results
Blank page is displayed.
Code sample
Code sample
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        colorScheme: ColorScheme.fromSeed(seedColor: Colors.deepPurple),
        useMaterial3: true,
      ),
      home: const MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({super.key, required this.title});

  final String title;

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  int _counter = 0;

  void _incrementCounter() {
    setState(() {
      _counter++;
    });
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        backgroundColor: Theme.of(context).colorScheme.inversePrimary,
        title: Text(widget.title),
      ),
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            const Text(
              'You have pushed the button this many times:',
            ),
            Text(
              '$_counter',
              style: Theme.of(context).textTheme.headlineMedium,
            ),
          ],
        ),
      ),
      floatingActionButton: FloatingActionButton(
        onPressed: _incrementCounter,
        tooltip: 'Increment',
        child: const Icon(Icons.add),
      ),
    );
  }
}

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
(index):38 Injecting <script> tag. Using callback.
Fetch finished loading: GET "<URL>".
Fetch finished loading: GET "<URL>".
Fetch finished loading: GET "<URL>".
Fetch finished loading: GET "<URL>".
Fetch finished loading: GET "<URL>".
Fetch finished loading: GET "<URL>".
Fetch finished loading: GET "<URL>".

Possibly related to: https://github.com/flutter/flutter/issues/136319
I see the same behavior when I run the app using Wasm or canvaskit, however, it works as expected with the html renderer.
With the code sample provided above, the view isn't fully rendered (at least when I tested it) in landscape mode (on my emulator), but the view becomes stretched when I switch back from landscape to portrait mode. See the recording below
https://github.com/user-attachments/assets/aea268b6-dbef-498a-88c8-7c3d0f86dd5e

flutter doctor -v
[✓] Flutter (Channel stable, 3.24.1, on macOS 14.6.1 23G93 darwin-arm64, locale en-US)
    • Flutter version 3.24.1 on channel stable at /Users/deanli/dev/stable
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 5874a72aa4 (7 days ago), 2024-08-20 16:46:00 -0500
    • Engine revision c9b9d5780d
    • Dart version 3.5.1
    • DevTools version 2.37.2

[!] Flutter (Channel master, 3.25.0-1.0.pre.159, on macOS 14.6.1 23G93 darwin-arm64, locale en-US)
    • Flutter version 3.25.0-1.0.pre.159 on channel master at /Users/deanli/dev/master
    ! Warning: `flutter` on your path resolves to /Users/deanli/dev/stable/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/deanli/dev/master. Consider adding /Users/deanli/dev/master/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/deanli/dev/stable/bin/dart, which is not inside your current Flutter SDK checkout at /Users/deanli/dev/master. Consider adding /Users/deanli/dev/master/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision<PHONE_NUMBER> (2 hours ago), 2024-08-27 22:23:18 -0700
    • Engine revision 8d248aead3
    • Dart version 3.6.0 (build 3.6.0-175.0.dev)
    • DevTools version 2.39.0-dev.15
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

stesso problema su tutte le app flutter!


5.3.x

There is no conflicts in my local work tree,why can not approval this pull request?Would you plese help me to handle it? Mr Sam@sbrannen

James@JAMES-PC MINGW64 /e/00OpenSource/spring-framework (5.3.x)
$ git merge --no-ff spring-projects-5.3.x
Already up to date.

James@JAMES-PC MINGW64 /e/00OpenSource/spring-framework (5.3.x)
$ git merge --no-ff spring-projects-5.3.x
Already up to date.

James@JAMES-PC MINGW64 /e/00OpenSource/spring-framework (5.3.x)
$ git push origin 5.3.x
Everything up-to-date

I have done everything flow the command that's in tips

I don't know how to approval it.
git push origin 5.3.x
Everything up-to-date


Fix flaky e2e issue

What type of PR is this?

What this PR does / why we need it:
Fix the pod creation error in seccomp profile binding test, and fix seccomp profile finalizer test.
In seccomp profile finalizer test, when we first delete the profile recording before the pod is removed, it will not be removed because of the finalizer, however as soon as the pod is removed, the profile recording will be removed, hence in the next step, we were not able to find the object.
Which issue(s) this PR fixes:
Flaky e2e issue
Does this PR have test?
N/A
Special notes for your reviewer:
Does this PR introduce a user-facing change?
None

Codecov Report

Merging #1216 (00b0514) into main (1bc5a47) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1216   +/-   ##
=======================================
  Coverage   45.42%   45.42%
=======================================
  Files          48       48
  Lines        5360     5360
=======================================
  Hits         2435     2435
  Misses       2805     2805
  Partials      120      120

/ok-to-test


DXVK reporting Geforce 999 GTX on Radeon VII

Running Superposition with DXVK in wine reports that I am using a Nvidia GPU, Benchmark tries to use NVAPI.
If i remember correctly, DXVK normaly always pretend to be a AMD Card, so i found this unusual.
Software information
Superposition Windows Version
System information

GPU: Radeon VII
Driver: Mesa 19.1.0-devel - padoka PPA
Wine version: 4.4 Staging
DXVK version: 1.0.1

https://pastebin.com/RKYABGSe

Disable NVAPI.


🚀 [Feature] Allowed Special Character for Password

🚀 Feature
Discuss which characters should be allowed as special character for password.
Better don't use character which can be used to write malicious scripts.
Currently allowed are:
@$!%*?&+-_
Claus missed the # character.

I think the user should not be limited in his password choice within an unicode charset like utf8/16. If he wants to use emojies as a password why would we prevent him to?

As I have written the code to check if the password meets the criteria, I don't know how to check for special char if all are allowed.
So it is mainly for technical reason. But maybe I now found a way and can allow all.


Adding Tic Tac Toe game

Is your feature request related to a problem? Please describe.
I Would like to add Tic Tac Toe game in JavaScript. Please Assign this task to me under GSSOC'22.
Features

Score can be stored

Code of Conduct✅

[x] I agree to follow this project's Code of Conduct.
[x] I checked the current issues for duplicate problems.
[x] I have gone through project README.

#189


Update week3 gallery

Put photos from img/week_3 into the web gallery

Associated pull request #9 where @pimpika added the images to the repository then I put them into the web.

Associated issue #6


bedCoverage and spliced reads

Dear authors and community,
recently I encountered a strange behaviour of bedCoverage which leads to very confusing results and I hope you can address this issue.
bedCoverage provides a function for counting reads (.bam file) in an interval (.bed file). I am using this to count in various specific regions in RNASeq data (parameters -counts for counts only and -s for the  strand-specific setup we have, to mention it is paired-end).
I encountered strange counts when checking the consistency of the counting. For example in this interval in IGV browser (v2.3.67) there is only one read, however bedCoverage (v2.17 as well as v2.25) reports 6 reads in this interval.

The same interval in GenomeBrowse (v.2.1.0) shows one read and 4 spliced alignments, which does not add up to 6, however gave a hint where this counts might come from.

When converting the bam to bed(6) and then extracting the alignments spanning over the interval, the 5 missing reads show up.
perl -lane 'print join("\t", @F) if $F[0] == 1 && $F[1] < 911879 && $F[2] > 912004' RNASeq.bed
5 spliced + 1 mapped = 6
Same thing I saw in different scenarios.
The conclusion:
bedCoverage counts reads which do not map even close to the interval. The alignment split spans over 200kb in this cases. Therefore intervals with no reads get an artificial signal. The interval between spliced reads is not supposed to be in a fragment as well.
Is this a bug, a feature or did I overlook some important detail?
Thanks!

The -split option should have taken care of this in earlier versions. However, 2.25.0 seems to produce incorrect results even when -split is used. Here's a relevant post on biostars with an example that can be downloaded for testing.

Thanks for reporting - I just pushed a fix for this and will respond on biostars.org as well

:+1: Thanks!


select with order and group not working

by doc https://dev.mysql.com/doc/refman/5.7/en/select.html
order by should be after group and having

Yikes! You're right. will fix this shortly (today I think)

Build passed. v0.8.1


Error polling incoming connection: frame size too big

Environment:

xray version: bf5e5bc
Ubuntu 16.04.4 GNOME
Client Chrome v66

command:
XRAY_SRC_PATH=. script/xray_debug -H -l 4321 .

log
Error polling incoming connection: frame size too big
Error polling incoming connection: frame size too big
Error polling incoming connection: frame size too big
Error polling incoming connection: frame size too big
Error polling incoming connection: frame size too big
Error polling incoming connection: frame size too big
Error sending message to client on TCP socket: Connection reset by peer (os error 104)

Closing as duplicate of https://github.com/atom/xray/issues/92.

@as-cii not to be pedantic, but it looks like you may have mistakenly closed this issue for being a duplicate of itself

Oops, thanks @HotelCalifornia. Another issue with the same content already existed indeed, but I mistakenly linked the wrong one. Thanks for the heads-up!


Create text_on_image_146_telukoti_vipraj_.html

This is my contribution to issue #146 text_on_image Creator - Web design.
Please review.

Inappropriate Pull request


Failing to read rules from annotations when not using "prometheus.rules.json"

We are trying to configure one rule per annotation to avoid exceeding the 5000 char limit, but currently, the implementation is always expecting the annotation prometheus.rules.json to exist, even when you are informing rules through the pattern prometheus.rules.*.json.
https://github.com/philips-software/variant/blob/e9019172ed88edbba059c2cde94538b217dbd6d2/tva/utils.go#L136

Fixed in 0.1.0


diona should ignore kudzu slowdown

it makes sense and theyre already slower than other races so it would b a silly thematic niche feature for them

This is a good idea, im all thumbs up for this


Document/fix .show() function

Tried to programatically open the dialog using the .show function, but couldn't get it to work. First, I tried to create a dialog ("this" is an input element, also tried to reference by ID-string):
var vTimePicker = new TimePicker(this, {
    theme: 'dark',
    lang: 'en'
});
vTimePicker.show();

This didn't work, got "Can't evaluate: @param undefined (timepicker.js:393)" in the show function.
Checked the code, and seemed like the show-function expects a "target" like the constructor. So I tried to pass the element, but then I get "Cannot read property 'element' of undefined (timepicker.js:625)". Same when I pass the id of my element as string.
It fails on "Internal.prototype.show" which apparently expects an id/index in an array of elements, so I tried .show(0);
No luck: Can't evaluate: @param 0 (timepicker.js:393). Now it fails in the evaluate-function where it wants the target/id to be an element or string.
Am I using the .show()-function wrong, or is this a bug? Some more documentation on the .show()-function would be appreciated :)
EDIT: Code formatting
EDIT 2:
Using Chromium Version 51.0.2704.84 (64-bit)
TimePicker:

Version: v2.0.0
Built: 2016-04-20T22:20:15-0300

Yeah, this is buggy. Thanks @marza91
See #9


added_label Rule Not Working in Project

I have an added_label rule setup on a project board, and the bot is added to the repository, but issues are not added to the project board automatically:
https://github.com/JannisX11/blockbench/projects/1#card-75469725

https://github.com/philschatz/project-bot/issues/133

I have the same issue with the rule added_label, the bot does not work properly.
Do you confirm that the problem is related to the introduction of the new projects by GitHub?


how to run the benchmark test?

I am new to the JDBC driver? how to do the test and run benchmark?

Hi @sherrychenzhang, what kind of test you want to perform?  Could you elaborate? If it's just about connecting to ClickHouse via JDBC driver, you may start with popular client like CloudBeaver.


Unable to run "adb"

Steps to reproduce
1.Install Android Studio (latest version)
2. Install flutter
3. Create a flutter project
4. Connect a real(physical) device
Expected results
Device should be detected instead of flutter daemon termination.
Actual results
Flutter daemon terminated. And real device is not detecting
Code sample
Nothing related to code
Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Flutter Doctor output
flutter doctor -v
[✓] Flutter (Channel stable, 3.22.1, on macOS 14.5 23F79 darwin-arm64, locale en-IN)
    • Flutter version 3.22.1 on channel stable at /Users/vj10/Documents/jeeva/development/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision a14f74ff3a (2 weeks ago), 2024-05-22 11:08:21 -0500
    • Engine revision 55eae6864b
    • Dart version 3.4.1
    • DevTools version 2.34.3

[✓] Android toolchain - develop for Android devices (Android SDK version 35.0.0-rc4)
    • Android SDK at /Users/vj10/Library/Android/sdk
    • Platform android-34, build-tools 35.0.0-rc4
    • ANDROID_HOME = /Users/vj10/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.10+0-17.0.10b1087.21-11572160)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.4)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15F31d
    • CocoaPods version 1.15.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2023.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.10+0-17.0.10b1087.21-11572160)

[☠] Connected device (the doctor check crashed)
    ✗ Due to an error, the doctor check did not complete. If the error message below is not helpful, please let us know about this issue at
      https://github.com/flutter/flutter/issues.
    ✗ Error: Unable to run "adb", check your Android SDK installation and ANDROID_HOME environment variable: /Users/vj10/Library/Android/sdk/platform-tools/adb
    • #0      throwToolExit (package:flutter_tools/src/base/common.dart:10:3)
      #1      AndroidDevices.pollingGetDevices (package:flutter_tools/src/android/android_device_discovery.dart:75:7)
      <asynchronous suspension>
      #2      PollingDeviceDiscovery._populateDevices (package:flutter_tools/src/device.dart:547:36)
      <asynchronous suspension>
      #3      Future.wait.<anonymous closure> (dart:async/future.dart:524:21)
      <asynchronous suspension>
      #4      DeviceManager.refreshAllDevices (package:flutter_tools/src/device.dart:217:40)
      <asynchronous suspension>
      #5      DeviceValidator.validate (package:flutter_tools/src/doctor.dart:741:34)
      <asynchronous suspension>
      #6      Future.any.onValue (dart:async/future.dart:618:5)
      <asynchronous suspension>

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.
vj10@C001148685 MyEngine % flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.22.1, on macOS 14.5 23F79 darwin-arm64, locale en-IN)
[✓] Android toolchain - develop for Android devices (Android SDK version 35.0.0-rc4)
[✓] Xcode - develop for iOS and macOS (Xcode 15.4)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2023.3)
[☠] Connected device (the doctor check crashed)
    ✗ Due to an error, the doctor check did not complete. If the error message below is not helpful, please let us know about this issue at
      https://github.com/flutter/flutter/issues.
    ✗ Error: Unable to run "adb", check your Android SDK installation and ANDROID_HOME environment variable: /Users/vj10/Library/Android/sdk/platform-tools/adb
[✓] Network resources

! Doctor found issues in 1 category.

@JeevaVGeorge
Check if https://github.com/flutter/flutter/issues/142996#issuecomment-1932542584 helps in your case or not.

@darshankawar  I have  checked the versions. My Android Sdk Platform tool version is 35.0.1, and android studio version is Jellyfish 2023.3.1 Patch 1. Seems everything is latest.

@JeevaVGeorge Check if #142996 (comment) helps in your case or not.

@darshankawar  I am facing the same issue, but even though i have degraded , my device is not detected by adb , its listing while I troubleshooting, and it says not recognized as android. Downgrading also not helping.

Closing as duplicate of https://github.com/flutter/flutter/issues/72101. Check underlying comments to see if they help in your case or not.


bash.exe closes in a second cmd legacy mode

Please use the following bug reporting template to help produce actionable and reproducible issues. Please try to ensure that the reproduction is minimal so that the team can go through more bugs!

A brief description
The bash.exe that is supposed to be used to install BashOnWindows flashes if console is in legacy mode

Expected results
Installation executing or error being displayed and cmd staying open

Actual results (with terminal output if applicable)
Error is displayed and terminal closes

Your Windows build number
14393.447

Steps / All commands required to reproduce the error from a brand new installation
cmd in legacy mode
open start menu
type in 'bash.exe'
hit enter
watch cmd open and close within a second

Strace of the failing command
n/a

Required packages and commands to install
n/a

The attached picture is a single frame of a screen video to discover the problem

Legacy console is not supported.

I know that now, after making that screen video, however the problem still remains that the pause did not display, or was my build before the anniversary update?

This was fixed after anniversary update.

This issue should be fixed, marking it accordingly.


ARROW-18318: [Python] Expose Scalar.validate()

@pitrou  Not yet. The public registeration has been disabled. Are there any doc for creating a jira account？

@buaazhwb I should be able to create one for you. Do I just use the same ID and e-mail address as for Github?
Note that in the future, we will only be using Github issues, so please don't create any new JIRA issues.

@pitrou OK. Thanks for your help!


Unverified breakpoint in VS Code

Repro steps:

Install Debugger for Chrome (4.3.0) in Visual Studio Code
Debug [Development] Launch Server (no browser)
Debug [Development] Debug TypeScript
Navigate to http://localhost:5000/users in the Chrome instance that was launched

Observed: Unverified breakpoint in Visual Studio code

I can debug in the Chrome dev tools, but debugging right in VS Code would be superb :D

I'm seeing this issue as well.
VSCode 1.22.2
TS 2.5.3
Webpack 3.11.0
Debugger for Chrome 4.3.0

For me, the fix was simply changing cheap-eval-source-map to eval-source-map in webpack.config.js. I can open a PR for it, but eval-source-map is slower and everyone may not want it.

AFAICT this is still for Macs on VSCode
My environment:
VSCode 1.32.0
TS 2.9.2
Webpack 3.12.0
Debugger for Chrome 4.11.3


2 tips: Scenarios and Sharing Taipy app on Colab

This PR includes 2 tips (the next PRs will include only 1 tip per PR).
Here we have the original tips:

The Scenarios
Sharing a Taipy Application on Colab with Ngrok

@FlorianJacta @RymMichaut Do you know who created the drawing and do you have a source version we can modify?


endEditing function doesn't work

General information

Library version(s): develop branch
iOS version(s): 10.0
Devices/Simulators affected: Device
Reproducible in the demo project? (Yes/No): Didn't try but I guess
Related issues: #211
Swift 3, Xcode 8 Beta 6.

Bug report
self.view.endEditing(true) doesn't seem to have any effect.
Expected behavior
The keyboard should hide.
Actual behavior
The keyboard doesn't hide.
Steps to reproduce
Add self.view.endEditing(true) code in a function and call it after a short duration with perform:selector:with:afterDelay.

Hi, @Tulleb. I strongly suggest that you replicate the problem in our demo project. As different programs have different logic and ways to do things. We can't provide too much help if you put this Didn't try but I guess. LOL. 😄

Also, there's a big difference between calling self.view.endEditing(true) directly and using perform:selector:with:afterDelay.
@Tulleb -- how exactly are you using this?

@Lucashuang0802 I understand what you say. Sorry I should have precise that my program is almost a copy of the demo project (but in Swift 3.0).
If you are willing to help, I guess you can also add this simple line in your own code and see if you have the same issue? Or just replace the "Didn't try but I guess" by a "yes" after laughing so hard :)
Thanks!
@jessesquires I did try the perform:selector:with:afterDelay: doesn't work neither... And I tried in the demo project this time.

i don't recommend using performSelector:...
you can tell the textInputView to resignFirstResponder

@jessesquires I miss read your answer, sorry.
I've been trying to use it with and without performSelector:... in the demo project. It's not working.
I just wanted to point this out. I am using resignFirstResponder to keep hiding the keyboard.

should be fixed in v8.0


Add node reflector to KSR

This pull request adds to the KSR the ability to distribute a subset of node data to Contiv-VPP vswitches. This functionality is implemented in a new component - the Node Reflector.
The Node Reflector is built on top of the base KSR Reflector. The new components are as follows:

plugins/ksr/model/node: A new folder that contains the protobuf definition and the generated code for node data that is stored in Etcd
plugins/ksr/node_reflector.go: contains the initialization code, functions for Adding/Deleting/Updating node data and the converted of node data from K8s format into the format used in Etcd.

This patch also contains a minor cleanup of how reflectors are started.
Only Commits from Feb 07 and Feb 08 are a part of this patch.

Coverage decreased (-1.7%) to 75.061% when pulling 3865df80743972ca6043735147187b06db78c00d on jmedved:master into 2c7e6f939a9161c437139d5d537306520c608c4c on contiv:master.


feature: add image filter option dangling

Signed-off-by: Lang Chi<EMAIL_ADDRESS>
Ⅰ. Describe what this PR did
Add the dangling filter option for pouch images.
Ⅱ. Does this pull request fix one issue?

NONE
Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗？)
Add it later.
Ⅳ.  Special notes for reviews

could you add a test case for this feature?

how to define dangling? I don't think pouch container needs this.


Target parameter required

In BaseWrapper.fit, the targets y are required.
https://github.com/adriangb/scikeras/blob/9f633f5c21a45b43986a8d779c3ef9e3005038bb/scikeras/wrappers.py#L556
This poses challenges for models that don't require targets (like autoencoders).

The solution to this is to specify y=None in various function arguments and make sure it works.

Totally, I figured we'd tackle this at some point, but since we don't have any actual example implementations/use cases I've hesitated to try to plan for something I am still unfamiliar with.
Can we make this change at some later point? Any reason it needs to happen now?

Keras autoencoders are a good place to start: https://blog.keras.io/building-autoencoders-in-keras.html
This is an expansion of the existing API. I think I'd label it as "important to implement" but not "critical." I think releasing a new version of SciKeras takes higher priority.

Agreed. At this point I think we should lock in the #68 and work towards the release.

Having gone through the Keras tutorial linked in https://github.com/adriangb/scikeras/issues/110#issuecomment-710680873, I do not see the need to make any changes. You pass y=X to train and then you encode/decode by calling predict. I'll make a notebook example to validate this assumption.

I was wrong. PR implementing y=None is in #123

#123 will enable the following behavior:
class AutoEncoderTransformer(BaseWrapper, TransformerMixin):
    def transform(self, X):
        return self.predict(X)

tf = AutoEncoderTransformer(model=...)
encoded = tf.fit_transform(X)

Which is a pretty nice way to bring this behavior into the sklearn ecosystem IMO.


I am close to giving up

Describe your bug here.
I have been dealing with a bug and I have tried everything I could to get psych engine to work. When ever I try to play in free-mode or start story mode I get an error and only lets me close the game. I have no Idea what else I can do, so hopefully someone can help point out my mistake.
Steps I took so far: Downloaded, completed Command window prompts, launched game, ERROR, looked on here and YouTube no luck, tried 32bit noticed the note. Moved files from second drive to main, and repeated steps 1-3 just to get the same error.
Command Prompt/Terminal logs (if existing)
objects/HealthIcon.hx (line 35)
objects/HealthIcon.hx (line 15)
states/FreeplayState.hx (line 108)
flixel/FlxGame.hx (line 642)
flixel/FlxGame.hx (line 729)
flixel/FlxGame.hx (line 682)
flixel/FlxGame.hx (line 556)
openfl/events/EventDispatcher.hx (line 402)
openfl/display/DisplayObject.hx (line 1399)

Uncaught Error: Null Object Reference
Please report this error to the GitHub page: https://github.com/ShadowMario/FNF-PsychEngine

> Crash Handler written by: sqirra-rng

Are you modding a build from source or with Lua?
Source
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
no

I went and checked where the the healthicon.hx file was and opened it, but that was one of the last things I did, but it doesn't matter now, I found a different program that allows me to mod FNF. I will get this issue closed.


Update CODEOWNERS

Move Daneyon and Alex to Maintainers Emeriti (:cry:)
Rename CODEOWNERS.md -> CODEOWNERS so GitHub can use it

Signed-off-by: Flynn<EMAIL_ADDRESS>

Codecov Report

Merging #1123 (d6f3687) into main (0afe9b9) will decrease coverage by 0.07%.
The diff coverage is n/a.

:exclamation: Current head d6f3687 differs from pull request most recent head 6ecfc61. Consider uploading reports for the commit 6ecfc61 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main    #1123      +/-   ##
==========================================
- Coverage   62.59%   62.53%   -0.07%
==========================================
  Files          72       72
  Lines        9531     9531
==========================================
- Hits         5966     5960       -6
- Misses       3152     3156       +4
- Partials      413      415       +2

Impacted Files
Coverage Δ

internal/provider/kubernetes/helpers.go
81.75% <0.00%> (-3.38%)
:arrow_down:

internal/provider/kubernetes/controller.go
50.22% <0.00%> (-0.12%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Add Barren Plateau analyser to sQUlearn

I have something implemented, but analysis tools are added to a later version.


[Bug] Repeated timeout when trying to send XCH

What happened?
Attempting to send ~2 XCH from one wallet to another on Win10 Chia 1.4 and getting repeated timeouts on the Tx.
EDIT: Amount accuracy
Never had trouble with this on past versions. Any suggestions? Thanks.
Version
1.4
What platform are you using?
Windows
What ui mode are you using?
GUI
Relevant log output or stacktrace
2022-07-02T16:xxxxxx wallet chia.rpc.rpc_server        : WARNING  Error while handling message: Traceback (most recent call last):
  File "chia\rpc\rpc_server.py", line 229, in safe_handle
  File "chia\rpc\rpc_server.py", line 220, in ws_api
  File "chia\rpc\wallet_rpc_api.py", line 838, in send_transaction
  File "chia\wallet\wallet.py", line 432, in generate_signed_transaction
  File "chia\wallet\wallet.py", line 315, in _generate_unsigned_transaction
  File "chia\wallet\wallet.py", line 267, in select_coins
  File "chia\wallet\coin_selection.py", line 90, in select_coins
  File "chia\wallet\coin_selection.py", line 119, in select_smallest_coin_over_target
ValueError: Unable to select coins for this transaction. Try sending a smaller amount

Reduced the amount to 1 XCH and same result. The spendable balance in the wallet is more than these amounts.

I reduced the amount even further and same result.


Change Korean to local language

Korean -> 한국어

I'll merge it manually into develop branch later today..

Cool. Thanks

@clayop Please make all future pull requests against develop branch.


Default is not implemented for raw pointers (*const and *mut)

There is little info about this anywhere but is this an oversight?
A default value that makes the pointers point nowhere (like NULL) looks ok to me, but maybe I am missing something.

For some reason I was under the impression this was deliberately not implemented, since NULL isn't the safest thing in the world. Though I don't think I've seen an explicit discussion about that.

Right, I agree that null feels better when it’s a explicit choice rather than a possibly-derived possibly-not-thought-much-about default.

There are many better options than raw pointers for code that wants to handle null explicitly, or not at all, (NonNull, &T, Option<&T>, Option<NonNull>, ...).
The whole point of raw pointers is that they can be null, and ptr::is_null is one of the most used raw pointer methods because of this. The only code I can see implementing Default for raw pointers making more dangerous is code that was already broken to begin with.
Honestly, working with raw pointers is always hard, but the only thing adding hoops does for me is requiring me to spend time and effort coming up with workarounds for no good reason.

Personally, I've used raw pointers mostly in situations where they can't be null.  I suppose I could have theoretically used NonNull instead, but most existing APIs use raw pointers – including the pointer arithmetic methods in std::ptr, the as_ptr/from_raw_parts/etc. family, bindgen, and so on.

The whole point of raw pointers is that they can be null

It‘s really not. Your statement matches not *const T but Option<&T>. The defining feature of raw pointers is that the programmer assumes the responsibility for plenty of safety guarantees, including (but not limited to) nullability (which may even be contextual).

The whole point of raw pointers is that they can be null

I think this is only true in C++, where the various smart pointers introduced in modern versions of the language have retroactively made the more fundamental raw pointers only the best choice when either nullability is required or the pointer is completely non-owning (and that's only because std::optional<std::unique_ptr> isn't quite logically equivalent to a nullable raw pointer the way Option<&T> is, and because std::observer_ptr is not standard yet).

@main--

The whole point of raw pointers is that they can be null

It‘s really not. Your statement matches not *const T but Option<&T>. The defining feature of raw pointers is that the programmer assumes the responsibility for plenty of safety guarantees,

These "features" apply to other pointer types like NonNull. The only Rust types that can represent a pointer to null are raw pointers.

@Ixrec

I believe that's mainly because std::optionalstd::unique_ptr is not only verbose but not quite logically equivalent to a nullable raw pointer the way Option<&T>

Option<&T> == None is an Option that does not contain a &T, which is semantically very different from a raw pointer to null, which is still a pointer. One way to think about this is consider what would happen if we were to disable the non-zero optimization in Option. Semantically all safe code would still work the same, but these two types would not be layout compatible anymore.

@comex

Personally, I've used raw pointers mostly in situations where they can't be null. I suppose I could have theoretically used NonNull instead, but most existing APIs use raw pointers – including the pointer arithmetic methods in std::ptr, the as_ptr/from_raw_parts/etc. family, bindgen, and so on.

I feel your pain and I think this is an issue worth solving, but the solution is not to make raw pointers unnecessarily harder to use, but rather to make NonNull easier to use. If NonNull would auto deref/coerce to a raw pointer most of the existing frictions would disappear.

These "features" apply to other pointer types like NonNull. The only Rust types that can represent a pointer to null are raw pointers.

What about usize? [u8; 8]? Option<&T>? You disqualify that last one on the grounds of it not having a guaranteed memory representation (it actually does, as far as I remember?) while also excluding anything that isn't a canonical pointer type (*const T, NonNull). This position doesn't make sense to me.
Unless you specifically care about layout optimizations, there is no reason to use NonNull over a raw pointer. Unlike the typesafe equivalents, it offers absolutely no ergonomics or safety benefits - on the contrary, it even introduces additional undefined behavior. In other words: you don't use *const T because the pointer is nullable, you use it because you want any pointer (nullable or not). Now if you figure out that this pointer can never be null and if you need the layout optimization, only then would you even consider using NonNull.

What about usize? [u8; 8]?  Option<&T>? You disqualify that last one on the grounds of it not having a guaranteed memory representation

No. I disqualified these on the grounds that they are not pointers. Just because something is layout compatible with a raw pointer does not make it a raw pointer.

I don't understand the claim that Option<&T> is not a pointer while nullable raw pointers are. An Option<&T> is either the address of a T value, or None. A raw pointer to T is either the address of a T, or null. An Option<&T> is obviously not a raw pointer, but it seems to be a perfectly adequate non-raw pointer to me. It seems to do exactly as much pointing as any raw pointer, or a "smart pointer" like Arc or Box.
But maybe that's the wrong question entirely. I think we're only playing the "what is a pointer?" game because some of us didn't understand your earlier claim that:

The whole point of raw pointers is that they can be null

Regardless of how we differ in our usage of words like "pointer" or "null", I'm pretty sure that there are non-raw pointer/reference types in Rust which have a special value that means not pointing/referring to anything, and that Option<&T> is such a type. So given that, what is special about raw pointers other than unsafety? Why would someone prefer to represent nullability with ptr::null values rather than None values, assuming unsafety was not required?

pointers that can point to the null address and that you can dereference

Are you trying to say that you actually want to dereference the null value, and that's what makes raw pointers the type of choice? I thought doing that was undefined behavior.

I don't understand the claim that Option<&T> is not a pointer while nullable raw pointers are. An Option<&T> is either the address of a T value, or None. A raw pointer to T is either the address of a T, or null.

The difference is that None is the lack of an address while null is an address. You can do pointer arithmetic with null (which isn't necessarily 0x0), you can't with None because it is not an address.
The point I was trying to make is that the only types in Rust that let you store this null address as a value that you can manipulate are raw pointers.

I'm pretty sure that there are non-raw pointer/reference types in Rust which have a special value that means not pointing/referring to anything

A raw pointer that points to the address null does not point to nothing, it points to an object of some type on the address null. This is why Option<*const T> does not apply the "null pointer optimization", there is a difference between having no pointer, and having a pointer pointing to null.

Are you trying to say that you actually want to dereference the null value, and that's what makes raw pointers the type of choice? I thought doing that was undefined behavior.

No, what I said is that these types cannot represent the null address as a value.

In any case, the only argument I've actually heard against improving the raw pointer ergonomics by implementing traits like Default is that it might make it more tricky for those who are using raw pointers without handling null correctly.
It was pointed out that this happens if users expect for raw pointers to never be null, to which I've argued that such cases are bugs because either the user didn't understood that the pointer could be null, or because the user didn't use the appropriate type for their pointer (like, for example, NonNull).
@comex raised a very good point about the bad ergonomics of interfacing these types with raw pointer APIs, but while that's a problem worth solving, it's orthogonal to this one.
So I am very unconvinced by the counter argument because at least for the reasons raised, the only situation in which Default can be dangerous are situations that are already dangerous or silent because either the code already has a bug, or because the user didn't use the proper pointer type.

Some related discussion:

https://internals.rust-lang.org/t/impl-default-for-pointers/10388
https://users.rust-lang.org/t/dealing-with-bindgen-generated-padding/34408

AtomicPtr::default() already returns null btw. So the standard library is at best inconsistent right now.

I think Default should convey meaningful information. Having a default pointer is a bit akin to have a default age, to me. It’s possible, yes. Does it make sense? I don’t think so.
I would be more interested to have a PtrArithmetic trait that would have a const NULL: Self associated type. That would make much more sense to me.

@phaazon how is having a default value for pointers different than having a default value for Option ?

It’s not, and to me, Option shouldn’t have a Default value. Depending the usecase, the default value could be None or Some(T::default()).

Ah I see, yes that is fair. I suppose that's just like the Monoid instance for Maybe in Haskell, there are multiple ways to define that. The question is whether it is a better trade-off to provide a default one or not. I think that providing a default is better, and in the cases where the default doesn't fit, one can always write a newtype - I personally never have to do so for Option, but I can imagine this can be painful, but that's a problem that can be solved.
For raw pointers the situation is a bit different, and I don't know of any identity element beyond NULL that might make sense.

I would be more interested to have a PtrArithmetic trait that would have a const NULL: Self associated type. That would make much more sense to me.

Do you have any applications in mind in which you would assign PtrArithmetic::NULL a different value than NULL ?

Ah I see, yes that is fair. I suppose that's just like the Monoid instance for Maybe in Haskell, there are multiple ways to define that.

Yes, but Monoid has laws whereas Default has none.

I think that providing a default is better.

Why?

Do you have any applications in mind in which you would assign PtrArithmetic::NULL a different value than NULL ?

No, NULL = NULL seems like a fine assertion to me. But being able to be polymorphic on the type of pointers and null pointers seem like something I could use in FFI code, for instance.

Notice that Default does not promise any kind of "right" default, it just promises that it will give you a default, and with that you can use derive(Default) and Foo { x: 42, ..Default::default() }; on types containing your type, and that's it.
That's a useful feature, and it doesn't really matter what the value returned is.
If Default would have "laws" then it would matter, but it doesn't.
This does not prevent particular implementations of Default from guaranteeing more, e.g., <i32 as Default>::default() can guarantee that it returns 0_i32, and that's fine, but generic code fn foo<T: Default>() doesn't get these extra guarantees.
From this POV, Option::None is a good default value for Option<T> because it is the only value that can be provided even if T does not implement default. And for pointers, NULL is a meaningful value as well because you can easily check it with ptr::is_null to make sure such pointers aren't dereferenced.
Also, these values do not prevent people from adding others. You can implement a Monoid trait for Option and raw pointers and give them different defaults if you wanted, and couple that trait with laws, but that's not what Default does.

Absolutely safe to make const reference to mut pointer:
fn foo(x: &i32) -> *mut i32 {
    return ((&(*x)) as *const i32) as *mut i32;
}

fn main() {
    let mut kekw: *mut i32 = unsafe { 0 as *mut i32 };

    {
        let mut x = 1337;
        let ref_x: &i32 = &x;

        kekw = foo(&ref_x);
    }
}

but its unsafe to make raw pointer zeroed with default trait
the only way some one could 'shoot his leg' with zeroed pointer is:
pointer = 0;
unsafe { *pointer }

which may happen - never

but every time I want to use raw pointer in struct, I should do some strange mess with it
mmm
just give me "std::ptr::SuperUnsafePtr" with zero by default;
and disallow to publish crates with this type used
I will decide what to do in my project by myself with this SuperUnsafePtr

the expression 0 as *mut i32 is not unsafe, so I'm unclear what you're saying here.
https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=285e72e32b9d304502778e0836204f9d

I've run into the lack of Default for pointers while writing native Java functions with jni-sys. In particular, when a native Java function throws an exception, it generally returns the zero or null value for the return type, then the caller uses ExceptionCheck() to determine that an exception occurred. Based on this, I attempted to write a generic wrapper for native functions, which throws an exception and returns Default::default() if the function body panics. However, this does not work for functions returning jobject, which is a type alias for *mut _jobject.
Many C interfaces use the null pointer to denote the equivalent of Option::None. In this instance, I could have replaced the jobject return type with Option<NonNull<_jobject>>, since the function pointer is cast to *mut c_void regardless. But in the general case, this might not always be possible: automatic binding generators can force the signature of a function to accept or return a possibly-null pointer, where the null value indicates None.
I just don't understand how implementing Default for (thin) raw pointers could cause any additional footguns. A raw pointer by itself has no invariants. If you want any guarantees at all about what can be done with the pointer, then you must either carefully keep it inside a controlled unsafe context, or store it in a data structure that maintains those particular invariants.
In particular, it takes several invariants just to dereference a pointer at all: it must be non-null, writable if you're trying to write to it, not aliased with unique references, not concurrently accessed in a way that would cause a data race, and not already deallocated. If you're ever in a situation where you're trying to dereference a Default::default() pointer, then you've already likely made a number of mistakes along the way.
Thus, since null raw pointers have a number of valid use cases in FFI code (to safely construct zeroed objects to be filled, or to indicate the equivalent of None to a C API), and since a Default impl probably can't create any footguns that weren't already present, I simply don't see why such an impl shouldn't exist.

I think Default should convey meaningful information. Having a default pointer is a bit akin to have a default age, to me. It’s possible, yes. Does it make sense? I don’t think so.

@phaazon I don't agree with this take. By this logic, the default value of a u64 should not be 0; yet it is. The default value of a bool should not be false; yet it is.
Default is always a contextual thing, it rarely works for everyone. Instead, the choice that appears to have been made in the standard library is for Default to set everything to its "zero" value:

Option -> None
Vec -> empty
u64 -> 0
bool -> false

In keeping with this theme, it makes sense for a raw pointer to be default initialized as 0 (aka NULL). I would attribute the missing default implementation to incompleteness of the standard library, rather than a safety measure.
Additionally, default initializing any value incorrectly can be disastrous. Think of what might happen here:
#[derive(Default)]
struct Robot {
  enable_ethics: bool, // defaults to `false`!!!
}

AtomicPtr::default() already returns null btw. So the standard library is at best inconsistent right now.

This is an excellent point.

I think Default should convey meaningful information. Having a default pointer is a bit akin to have a default age, to me. It’s possible, yes. Does it make sense? I don’t think so.

@phaazon I don't agree with this take. By this logic, the default value of a u64 should not be 0; yet it is. The default value of a bool should not be false; yet it is.
Default is always a contextual thing, it rarely works for everyone. Instead, the choice that appears to have been made in the standard library is for Default to set everything to its "zero" value:

Option -> None
Vec / String -> empty
u64 -> 0
bool -> false

In keeping with this theme, it makes sense for a raw pointer to be default initialized as 0 (aka NULL). I would attribute the missing default implementation to incompleteness of the standard library, rather than a safety measure.
Additionally, default initializing any value incorrectly can be disastrous. Think of what might happen here:
#[derive(Default)]
struct Robot {
  enable_ethics: bool, // defaults to `false`!!!
}

AtomicPtr::default() already returns null btw. So the standard library is at best inconsistent right now.

This is an excellent point.

Well, yeah, having a « zero » value is useful… but it’s never useful on its own — i.e. Monoid has an empty value because we reason about that value with a given binary function. In linear algebra crates, we often want to have a zero value, and most of the time there is a trait for that, Zero, and even a trait for the « 1-value », One. Why? Because it makes sense to have the « default » value for addition and the default value for multiplication.
In the case of a default value for an option, I think it should be fine to have another trait, like Empty, Absent, whatever. Because you have to check what the default value is, I rarely use Default because I don’t find it useful at all, either in specific code, where I would directly use ::new(), or in generic code, which cannot fully reason about what a default value is.

In the case of a default value for an option, I think it should be fine to have another trait, like Empty, Absent, whatever. Because you have to check what the default value is, I rarely use Default because I don’t find it useful at all, either in specific code, where I would directly use ::new(), or in generic code, which cannot fully reason about what a default value is.

The point of the current Default trait is that it's anything that makes sense as an initial value, not necessarily some mathematically pure identity value. For container types like Option<T> or Vec<T> which can hold zero or more elements, the empty container naturally fits this criterion; there is nothing in it initially, and then you can add something into it.
Likewise, the most important property of the null pointer isn't that its integer value is zero, but that it does not point to any value. Every other pointer can possibly point to something. That's why so many C APIs use a null pointer to indicate a default value, because if the user specifies a null pointer, there is 0 chance that they were specifying an actual value to be read from or written to.
You can have your own gripes about the Default trait, but in the context of the trait as it exists today, "a pointer that points to nothing" is a natural logical extension of an empty container, which is commonly used in Rust as an initial value. The naming of core::mem::take() reinforces this: you take all the elements the argument used to contain, leaving behind an empty container. Similarly, if you take from a pointer that points to some value, then it would make sense that you'd leave behind a pointer not pointing to any value.


Python shim pointing to python27

Dear all
I have installed both python and python27 package on my Windows 10.  Is is possible to have python shim pointing to c:\Users\username\scoop\apps\python27\current\python.exe instead of c:\Users\username\scoop\apps\python\current\python.exe
Please guide
Thanks

I have found that scoop reset python27 does me the job
thanks


Build and test go web server

Build and test a go web server.
Includes some example files to run against.
Should we cache the build? Any other changes?

To keep the IDs consistent, I reckon we go with golang-ci for the folder name of this pipeline.

To keep the IDs consistent, I reckon we go with golang-ci for the folder name of this pipeline.

Sounds good.

Another possible handy command in a go CI pipeline is testing that go generate doesn't produce any output.

TIL 💡 I added this step.
Ready for review.

Heads up @olyism, I'm going to take this one over.


Fix update-alternatives invocation for WSL2

The regular expression was missing a \ before the | (or alternatively egrep instead but I went with door 1), so would never match; also, ip6tables needed to be mapped to /usr/sbin/ip6tables-legacy.
Built locally with docker build -t ghcr.io/home-assistant/devcontainer:addons -f addons/Dockerfile . and confirmed that I was able to successfully start the supervisor and onboard. After creating a user, I get a failed redirect to http://localhost:7123/?auth_callback=1&code=(redacted)&state=(redacted)%3D; that doesn't seem like it should be related; but Docker is currently broken on my Linux laptop so I can't try there for comparison.
Deleting the query and going to http://localhost:7123/ produces the expected login screen, which accepts the credentials I specified in onboarding; from there everything works as expected.

Hi @backerman,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!


make possible to disable NIFTYREG checkouts

Allows to disable the Checkouts for Niftyreg.
Also passes, if set, the variable CMAKE_POSITION_INDEPENDENT_CODE, to be used by NIFTYREG to pass the CMAKE_C_COMPILE_OPTIONS_PIC string, so we can flag "-fPIC" in the build of NIFTYREG
See: https://github.com/KCL-BMEIS/niftyreg/pull/67

@KrisThielemans Done!

I have made a big mistake from the beginning with this PR: I made it from my master branch and then fiddled with it. I have tried to solve it but history is too entangled to fully fix it and this will create a messy past in the repo. I will therefore just delete this PR, and open a new clean one.


Get Channel Authentication Capabilities failed, err: client udp exchange msg failed, err: read from conn failed

ipmitool operation without administrator privileges
[root@A06-R08-I201-219-J33GRMW:/tmp]$ ipmitool -H <IP_ADDRESS> -U  user -P 'pwd' -I lanplus  power status
Set Session Privilege Level to ADMINISTRATOR failed: Unknown (0x81)
Error: Unable to establish IPMI v2 / RMCP+ session

ipmitool operation without administrator privileges
[root@A06-R08-I201-219-J33GRMW:/tmp]$
[root@A06-R08-I201-219-J33GRMW:/tmp]$ ipmitool -H <IP_ADDRESS> -U  user -P 'pwd' -I lanplus -L operator power status
Chassis Power is on

Connection timeout error using code library
    client, err := ipmi.NewClient(ip, 623, usr, pwd)
    client.WithMaxPrivilegeLevel(ipmi.PrivilegeLevelOperator)
    client.WithInterface(ipmi.InterfaceLanplus)
    if err = client.Connect(); err != nil {
        logger.Error("Connect bmc %s failed. err=%v.", ip, err)
    }

ERROR ->>> Get Channel Authentication Capabilities failed, err: client udp exchange msg failed, err: read from conn failed, err: read udp <IP_ADDRESS>:48788-><IP_ADDRESS>:623: i/o timeout

 Does this code base only support administrator privileges to connect?

This library supports changing privileges using WithMaxPrivilegeLevel() method.
The error seems ONLY relates to the problem of udp network connection.
So, make sure the target address can be really reachable. (<IP_ADDRESS>:623 in your example). The address （<IP_ADDRESS>）used in the ipmitool example is different from the address (<IP_ADDRESS>) in the code using the library.

该库支持使用方法改变权限WithMaxPrivilegeLevel()。
该错误似乎仅与 udp 网络连接问题有关。
因此，请确保目标地址确实可以访问。（您的示例中为 <IP_ADDRESS>:623）。ipmitool 示例中使用的地址（<IP_ADDRESS>）与使用该库的代码中的地址（<IP_ADDRESS>）不同。

Other nodes can connect, but only this node has problems. I checked the users in the out-of-band console and found that this user did not have administrator privileges, while those users who could connect normally had administrator privileges, so I suspected that there was a problem with the code.

该库支持使用方法改变权限WithMaxPrivilegeLevel()。
该错误似乎仅与 udp 网络连接问题有关。
因此，请确保目标地址确实可以访问。（您的示例中为 <IP_ADDRESS>:623）。ipmitool 示例中使用的地址（<IP_ADDRESS>）与使用该库的代码中的地址（<IP_ADDRESS>）不同。

The IP is different because I edited it. It's actually OK.

This library supports changing privileges using WithMaxPrivilegeLevel() method.
The error seems only relates to the problem of udp network connection.
So, make sure the target address can be really reachable. (<IP_ADDRESS>:623 in your example). The address （<IP_ADDRESS>）used in the ipmitool example is different from the address (<IP_ADDRESS>) in the code using the library.

The IP is different because I edited it. It's actually OK.
Other nodes can connect, but only this node has problems. I checked the users in the out-of-band console and found that this user did not have administrator privileges, while those users who could connect normally had administrator privileges, so I suspected that there was a problem with the code.

[root@A06-R08-I201-219-J33GRMW:/tmp]$ nmap -sU -p 623 <IP_ADDRESS> -Pn

Starting Nmap 6.40 ( http://nmap.org ) at 2024-12-06 16:53 CST
Nmap scan report for <IP_ADDRESS>
Host is up.
PORT    STATE         SERVICE
623/udp open|filtered asf-rmcp

Nmap done: 1 IP address (1 host up) scanned in 2.06 seconds
[root@A06-R08-I201-219-J33GRMW:/tmp]$ nmap -sU -p 623 <IP_ADDRESS> -Pn

Starting Nmap 6.40 ( http://nmap.org ) at 2024-12-06 16:53 CST
Nmap scan report for <IP_ADDRESS>
Host is up.
PORT    STATE         SERVICE
623/udp open|filtered asf-rmcp

Nmap done: 1 IP address (1 host up) scanned in 2.06 seconds
[root@A06-R08-I201-219-J33GRMW:/tmp]$
[root@A06-R08-I201-219-J33GRMW:/tmp]$ time ./ipmi <IP_ADDRESS>
2024-12-06 16:53:56.944 [INFO] ipmi_v2.go:26 - start connect
2024-12-06 16:54:57.096 [INFO] ipmi_v2.go:33 - connect success
2024-12-06 16:54:57.136 [INFO] ipmi_v2.go:102 - get <IP_ADDRESS> power status : on
on <nil>

real	1m0.207s
user	0m0.012s
sys	0m0.014s
[root@A06-R08-I201-219-J33GRMW:/tmp]$
[root@A06-R08-I201-219-J33GRMW:/tmp]$ time ./ipmi <IP_ADDRESS>
2024-12-06 16:55:46.608 [INFO] ipmi_v2.go:26 - start connect
 cmd: Get Channel Authentication Capabilities failed, err: client udp exchange msg failed, err: read from conn failed, err: read udp <IP_ADDRESS>:38352-><IP_ADDRESS>:623: i/o timeout

real	1m0.037s
user	0m0.012s
sys	0m0.009s

udp is ok, but I also found that the connection establishment is very slow. It takes 1 minute to complete each access to <IP_ADDRESS>. It is the same for other IPs. I don't know where the problem is.

623/udp open|filtered asf-rmcp

The open|filtered port state actually means there's no response received by nmap for udp port scan. see
The state should be open for a normal reachable port. I still doubt there may exist firewalls that blocks or drops the connection.
PORT    STATE SERVICE
623/udp open  asf-rmcp

623/udp open|filtered asf-rmcp

The open|filtered port state actually means there's no response received by nmap for udp port scan. see
The state should be open for a normal reachable port. I still doubt there may exist firewalls that blocks or drops the connection.
PORT    STATE SERVICE
623/udp open  asf-rmcp

But only server <IP_ADDRESS> cannot connect via ipmi, other nodes are successful.
When using v0.4.2, accessing ipmi is very fast. After upgrading to 0.5.10, accessing ipmi is very slow, taking one minute each time.
But <IP_ADDRESS> cannot connect using both the old and new versions. The network topology is very simple, just a few servers directly connected to the same switch in the development environment.

The “one minute” may relates with the default udp read timeout setting, which was increased to a default 60s. You can change it using WithTimeout method to set a small value like 10s or 20s.
Sent with GitHawk

Sent with GitHawk


Getting exception in mass updation in Product grid, if no product is available in grid.

Framework Version: 0.1.3

Framework Version: 0.1.4
Fixed


fix: Workaround for ethers.js bug in webpack environments

Description
I was getting the following issue when trying to connect in a nodejs server-side webpack environment (in Next.js):
Error: could not detect network (event="noNetwork", code=NETWORK_ERROR, version=providers/5.7.2)

After doing some searching and testing, I figured out it was an bug from ethers.js with webpack. I tried the workaround from https://github.com/ethers-io/ethers.js/issues/3536#issuecomment-1323302238 and it fixed the issue. This PR only changes one line of code.
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] Try running it in Next.js server side with and without this change. You will see the difference.

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

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

Could you change the JsonRpcProvider to StaticJsonRpcProvider?
We have just got this PR up (#537) which could half to RPC request time by simply changing it to static

Sure let me try

@Ansonhkg Okay I changed it to StaticJsonRpcProvider and it seems to work well.

Are you OK to make that change @joshdchang?

Hi, thanks for this! Do you want me to change it to StaticJSONRPCProvider in all the locations as well? This would overlap substantially with #537 and might lead to merge conflicts. Maybe this is best done in one PR?

Are you OK to make that change @joshdchang?

Hi, thanks for this! Do you want me to change it to StaticJSONRPCProvider in all the locations as well? This would overlap substantially with #537 and might lead to merge conflicts. Maybe this is best done in one PR?

Sorry for the delayed response, and thanks so much for contributing!
We've landed the JsonStaticRPCProvider PR now, so you're GTG without needing to worry about conflicts :)

Replacing this with https://github.com/LIT-Protocol/js-sdk/pull/646 which has the changes needed on all the providers. Thanks @joshdchang !!!


Small refactoring

Q
A

Is bugfix?
❌

New feature?
✔

Breaks BC?
✔

Replaced {visibility-modifier}::{property-name} to {visibility-modifier} ${property-name} (like a php-style): e.g. public::username -> public $username
Wrapped raw closure's code with object: "fn () => 1" => {"Closure#1":"fn () => 1"}

Make top-level objects map keys with object ids, like
"My\Class#44": {
    "public::name": "MyClassName"
}
``

It's already it is.

👍

It's already it is.

It doesn't. You have an integer indexed array instead of the object map.


splitProps - mark undefined keys in non proxy splitting.

mergeProps - skip undefined keys from splitProps.

non proxy only.
splitProps, will track keys that were specified, but were not defined in the object, when splitting.
mergeProps, skip merging undefined marked keys (returned by splitProps)

alternative fix(pr): https://github.com/solidjs/solid/pull/1317
may fix(issue): https://github.com/solidjs/solid/issues/1316
only tested in patched playground

This is PR is out of date since I went with a different fix. I think we go with that fix or submit a new PR that reconciles against that. Thanks.


Access parameter store from lambda function - invoking on client

Which Category is your question related to?
function
Amplify CLI Version
4.5.0
Provide additional details e.g. code snippets
I'm storing 3rd party api keys in parameter store that lambda needs to access. Works fine on server but I would like to test the function on the client. I get an error "Missing credentials in config". How can I access the Parameter store while testing locally?

I would like to test the function on the client. I get an error "Missing credentials in config". How can I access the Parameter store while testing locally?

By client do you mean running amplify mock function <function-name>? If thats the case, we don't have support for mocking Parameter Store.

@yuth  Either via mock or invoke. Is there a flag that I can test for in the function that informs the function it is being called by mock or invoke?

I think I answered my own question. I'll add .env files and in event.json i'll set a flag for local and handle it in the code.
Closing.

Also, I'm going to assume that I can use host: '<IP_ADDRESS>:20002' in the headers sent when  in mock to manage as well. Would be nice to have a flag set so the host doesn't need to be hardcoded.


Azure Classic, Start-Stop Mode - Agent stops immediately after start

Current idle timeout handling makes Start-Stop Mode completely unusable.
Idle timeout is measured from last build time, or from agent creation/registration time, if there are no builds in history.

Created a new cloud profile, added a agent VM to it. Set up an idle timeout to 30.
Started a new agent.
Agent was shutdown in 30 minutes as expected

Then I added a build in a queue.

TeamCity decides to start the build agent
Agent starts successfully
Right after the agent connects, KillIdleRunningInstances checks if there are any idle instances
Agent considered idle since it's registration / last build, that occurred quite long ago
Agent is killed by TeamCity
There is a build to run. GOTO 1

An it keeps starting and stopping the agent, while build is still handing in a queue.
teamcity-clouds.log:
[2016-08-02 09:28:13,960]   INFO ['{id=azure-1} 2] - uds.base.AbstractCloudInstance - Changing azbuild-d2-4(19f9b4d) status from Scheduled to start to Starting
[2016-08-02 09:28:13,960]   INFO ['{id=azure-1} 2] - re.connector.ConditionalRunner - Added conditional 'Finish handler of 'start new instance: azbuild-d2-4''
[2016-08-02 09:28:13,960]   INFO ['{id=azure-1} 2] - re.connector.ConditionalRunner - Executing Start handler of 'start new instance: azbuild-d2-4'. Result: true
[2016-08-02 09:28:15,046]   INFO [uled executor 2] - .server.impl.CloudEventsLogger - Cloud instance entered 'starting' state, profile 'AzureCloud'{id=azure-1}, AzureCloudInstance{myName='azbuild-d2-4'}
[2016-08-02 09:28:18,964]   INFO ['{id=azure-1} 1] - sm.connector.AzureApiConnector - Enter: 6575, getOperationStatusAsync
<Operation ...InProgress>
[2016-08-02 09:28:20,294]   INFO ['{id=azure-1} 1] - sm.connector.AzureApiConnector - Enter: 6577, getOperationStatusAsync
<Operation ...InProgress>
[2016-08-02 09:28:26,508]   INFO ['{id=azure-1} 2] - sm.connector.AzureApiConnector - Enter: 6580, getOperationStatusAsync
<Operation ...InProgress>
[...snip...]
[2016-08-02 09:28:40,560]   INFO [uled executor 5] - ances.KillIdleRunningInstances - Terminating instance AzureCloudInstance{myName='azbuild-d2-4'}, profile 'AzureCloud'{id=azure-1} with idle time 539 minutes (idle time is 30 minutes)
[2016-08-02 09:28:40,568]   INFO [uled executor 5] - l.instances.StopInstanceAction - Terminating instance: AzureCloudInstance{myName='azbuild-d2-4'}, profile 'AzureCloud'{id=azure-1}, reason: idle timeout of 30 minutes reached
[2016-08-02 09:28:40,570]   INFO [uled executor 5] - r.impl.DBCloudStateManagerImpl - Image: AzureCloudImage{myName='azbuild-d2-4'}, profile: profile 'AzureCloud'{id=azure-1} was marked to CONTAIN agent
[2016-08-02 09:28:40,572]   INFO [uled executor 5] - uds.base.AbstractCloudInstance - Changing azbuild-d2-4(19f9b4d) status from Starting to Stopping
[2016-08-02 09:28:40,572]   INFO [uled executor 5] - re.connector.ConditionalRunner - Added conditional 'Start handler of 'stop instance azbuild-d2-4''

I found no way to reset idle time on agent start or somehow change KillIdleRunningInstances workflow from the plugin side :( Is there any possible workaround for that?

@dtretyakov that seems to be a bug in TeamCity code. Should I post it to youtrack?

@PashaPash, thanks, we have the issue TW-46547.

@PashaPash, it was fixed. You can download latest classic plugin build:
https://github.com/JetBrains/teamcity-azure-plugin#classic

@dtretyakov downloaded a new build, agent starts correctly now. Thanks for a quick fix!


Desktop AOT engine builds download

From the wiki I can download the JIT compiled versions of the engine for MacOS, Linux and Windows uploaded by the build-bots.
Are there build-bots for the AOT versions of the engine? And if yes where can I download these versions?

@kf6gpe You are mentioned in this wiki. Can you help with this? I figured out the flutter infra config needs to be updated in order to get AOT engine uploads.

Good question -- I'm actually not sure myself. Let's ask @godofredoc, who's doing a lot of our infrastructure stuff these days. I'm also going to add a few labels to help this get on people's radar better.

We do not have the capability to build functional AOT configurations for Linux and Windows desktop currently

Also see https://github.com/flutter/flutter/issues/43454

Is that why I was able to build the linux AOT engine, but flutter always crashed, because I provided invalid snapshots?

Any updates on AOT builds?
Currently for flutter-rs, we use Github actions to build AOT flutter-engine builds. While it has worked for us for the last 4 months or so, having to maintain it is a pain, especially when changes occur with Github Actions. We also have a lag period between when a flutter release occurs, and when our CI runs. We have a patch to include the icudtl data in the binaries to make our lives easier, however once #48160 is resolved, we would be able to move to the official binaries.

This issue should probably be closed in favor of https://github.com/flutter/flutter/issues/50778 . There will not be any progress made here until we can actually use the AOT artifacts.

@jonahwilliams We aren't ever planning on using what's being requested here though, which is specifically the stand-alone engine. It's not related to any of the officially maintained embeddings.

Any updates on AOT builds?

We don't have any plans to do this at the moment, which is why there haven't been any updates. Mainly what's needed here is a policy decision about whether or not we want to add this to our infrastructure. If we do, it would just be a recipe change. @cbracken, thoughts?

I was thinking about this over the weekend given the discussions in the PRs above, and I think what we should actually do is stop uploading the debug desktop engine builds (and wontfix this).
As the the wiki page says:

If you want to build Flutter embedders on one of the platforms not supported out of the box (i.e, iOS & Android), this page is for you.

They are not supported on any platform where we plan to be the publisher of a Flutter runtime distinct from the applications that run on the runtime

We would generally recommend using custom engine builds only when porting Flutter to platforms that are not supported out of the box

At the time they started being uploaded, desktop fit that description, but it no longer does. We're now in the position where the only prebuilts we're posting for the embedder API are for platforms where we recommend (on the same page we link to them) against using that API, which is a confusing message. Given that we have a documented philosophy for how we expect the API to be used, we should update to once again be consistent with that philosophy, and not have the desktop artifacts.
In any other case, someone building on the embedder API needs to build their own engine, so the current flutter-rs approach seems like the right one for a project that wants to support arbitrary versions.

@stuartmorgan: I disagree. The Embedder API was designed for the creative use of Flutter in environments the Flutter Team could not reach. This is still the case and, within reason, we want to lower the barrier to entry for such endeavors. The ample caveats on the wiki are an effort to warn embedder authors about the magnitude of effort necessary to write a fully featured embedder implementation. Building the engine is busywork and, as we have already seen with more mature embedders, something the embedder author usually ends up taking the responsibility for anyway. When these artifacts started being uploaded, the desktop effort did not exist. But, these artifacts were undoubtedly useful for that effort (and many others during at least the prototyping phases). I see no reason to stop uploading these artifacts now that the desktop effort has matured. The maintainability of these artifacts has remained constant for years.
I do agree that the tone of wiki article is not very cohesive. That's probably because the addendum was added later by a different author. But, the intent was not to dissuade folks from writing their own embedders. Instead it was to be upfront about the effort they would need to take (in a mostly self directed fashion) in order to get a fully realized embedder implementation. I'll reword this wiki to better reflect this message as I did not realize that wording could be construed to mean we didn't want folks using the embedder API before you pointed it out.
About the original ask, SGTM as those artifacts are already being built, tested and have a stable ABI/API.

The Embedder API was designed for the creative use of Flutter in environments the Flutter Team could not reach. This is still the case and, within reason, we want to lower the barrier to entry for such endeavors.

But that's my point; uploading desktop artifacts is no longer reducing the barrier to entry for environments the Flutter Team isn't reaching, because we are reaching desktop now.

When these artifacts started being uploaded, the desktop effort did not exist.

Well, FDE existed (and, IIRC, is the reason they started being uploaded in the first place). But again, that seems like an argument for why we don't need them any more, not why we should keep them.

I see no reason to stop uploading these artifacts now that the desktop effort has matured.

Is there a reason we upload desktop builds but not mobile builds, if we believe that providing prebuilts of this library is a good idea for platforms that we directly support with an embedding layer?

But that's my point; uploading desktop artifacts is no longer reducing the barrier to entry for environments the Flutter Team isn't reaching, because we are reaching desktop now.

The desktop effort is still only likely to cover a subset of the potential use-cases for Flutter in a desktop like environment though (or maybe that is just my sincere hope). The fact that this issue was opened in the first place is likely a signal that there are use cases that may be better served by a different take on an embedder. Anecdotally, I have used these artifacts for preparing POCs for embedders that later went on to ship. It is entirely possible that I could be underestimating the desired capabilities of the higher level API in the desktop effort. Either way, these artifacts are the least opinionated / lowest level way of using the engine and I consider there to be some value in that.

... But again, that seems like an argument for why we don't need them any more, not why we should keep them.

The author of this PR seems to have a need for this. The artifact is something whose maintainability has remained constant for years and something we have to build anyway. Removing this seems like change for changes sake.

if we believe that providing prebuilts of this library is a good idea for platforms that we directly support with an embedding layer?

I think we are getting to the root of our disagreement. In my view, the Embedder API is just a library. The library can be used by folks to write an embedder, or, it can itself be wrapped to provide higher level functionality. Either way, the embedding layer and this library are at different positions in the tech stack. One is not a substitute for the other. Maybe the concern is that the presence of these artifacts is causing confusion? In that case, clarifications in the wiki would be the best way to address the same IMO.

In that case, clarifications in the wiki would be the best way to address the same IMO.

Summarizing from some Discord discussion: My issue with the current situation is purely that we have on one hand a written position that suggests that we should not have these artifacts, and on the other hand a set of artifacts that are uploaded because of historical decisions that are no longer relevant, and that disconnect is not a good situation.
I believe we should a clear policy about what we upload and why, from which answers to requests like this one can be clearly determined. My argument above for removing them was based on the assumption that the philosophy currently described on the wiki was correct, and trying to derive an answer from that, but I'm happy with a solution where we update the wiki with a policy that would clearly lead to an answer of having the current artifacts, or of having all the desktop artifacts, just so long as it's clear.

Removing this seems like change for changes sake.

This bug was requesting change; my goal is that we make change to align our described goals/policy and our practice (in whatever direction), rather than arbitrary change.
@chinmaygarde Do you want to self-assign this to update the wiki with a proposed policy for embedder artifacts?

@stuartmorgan

But that's my point; uploading desktop artifacts is no longer reducing the barrier to entry for environments the Flutter Team isn't reaching, because we are reaching desktop now.

No you are not. What you are doing is actively preventing people from using flutter on desktop. Which is the reason why those of us who want to use it (with all the disclaimers) had to turn to unofficial embedders which you are now trying to kill.

@stuartmorgan but the fact is that official embedder is not yet ready for use and that the flutter team is preventing us from attempting to use it on our projects by hiding information and even disabling development on desktop platforms.
What would be the right thing to do is to keep supporting 3rd party embedders until one can actually build and deliver software using official embedders.
What you are arguing for here is a bureaucratic solution that will kill goodwill with those of us who are looking to become early adopters of flutter on desktop platforms.

the fact is that official embedder is not yet ready for use

https://flutter.dev/desktop

the flutter team is preventing us from attempting to use it on our projects by hiding information

I have no idea what this is referring to; if there's information you believe should be in the documentation, please file a new issue.

and even disabling development on desktop platforms

Again, I'm not sure what this is referring to. I can't think of any instances of us disabling any desktop development. Again, please file an issue with details.

What would be the right thing to do is to keep supporting 3rd party embedders

Third-party embeddings are supported. The embedder API is stable, supported, and documented, explicitly for that purpose. Nobody is proposing changing that.
The only question is whether we should be providing pre-built libraries, and if so which platforms and variants.

until one can actually build and deliver software using official embedders

Please file issues with anything blocking you from doing this. But support for third-party embeddings is definitely not conditional on the non-existence of supported embeddings; again, there are no proposals to remove support for third-party embedding support.

What you are arguing for here

You do not appear to have read all of my comments. The only thing I am arguing for at this point is that our stated philosophy for deciding what artifacts we post should match the reality of what we post, which should not be a controversial position. You'll notice that the very last thing I said here indicated that this issue is waiting for an update to the former.


Broken link on CSS style guidance

Error: You do not have access to this repository.
https://bitbucket.org/slalom-consulting/dallas-css-standards

Thanks! That was holdover from very early in this project. We probably just need to rethink the launch page when you use the example library.

Have you any actual example or demo to see the generated docs?

What specifically are you curious to know beyond running this example library?

Fixed. @alexeybondarenko - I would still love to know what else you are curious about.