populatedb does not work with S3 bucket

What I'm trying to achieve
populatedb
Steps to reproduce the problem

checkout 1ba7f4eb74c037edcabfe4b581713b9b80da2601
configure S3
python manage.py populatedb

What I expected to happen
When I open storefront. I would be able to see pictures
Screenshots

System information
Operating system: Docker image python:3.8

I have a staging test instance that runs on Heroku and uses S3 for images and it works fine with populatedb. Are you sure you configured all env variables necessary to run with S3?

AWS_ACCESS_KEY_ID
AWS_MEDIA_BUCKET_NAME
AWS_SECRET_ACCESS_KEY
AWS_STORAGE_BUCKET_NAME

You can read about it more here: https://docs.saleor.io/docs/next/developer/running-saleor/s3

Thank you very much. I will check again


Refactor Formik to support optional sections and optional pagination

@Nechir-89 I will fix the merge conflicts after you merge your changes. :)

I am going to merge first so Daniel can use my changes, but do let me know if you see something I should change


KubernetesDependentResource implementing Matcher causes StackOverflowError

If sub classes of KubernetesDependentResource implement Matcher the matcher field of the class is set to this in the constructor
https://github.com/java-operator-sdk/java-operator-sdk/blob/f1b02f7e8a62242399aed7e8e2b10e948f67e341/operator-framework-core/src/main/java/io/javaoperatorsdk/operator/processing/dependent/kubernetes/KubernetesDependentResource.java#L51
This produces an infinit recursion when the match method is called which throws an StackOverflowError error.
https://github.com/java-operator-sdk/java-operator-sdk/blob/f1b02f7e8a62242399aed7e8e2b10e948f67e341/operator-framework-core/src/main/java/io/javaoperatorsdk/operator/processing/dependent/kubernetes/KubernetesDependentResource.java#L143
I have a standalone reconciler with a manuall worflow configure using operator-framework-spring-boot-starter (4.1.1).
Since the execution of the reconciler is in a separate thread the application keeps running but somehow the Error got totaly swallowed by the try catch block of the NodeExecuter run method. So there is space for improvement in the error handling.
The only workaround is to not let KubernetesDependentResource implement Matcher but override the method which is public anyway in the sub-class.

We did not see this issue since the subsequent updates, will close.


Feature: Implement Late Interaction Multi-Vector Search

SDK
Python
Description
Looks like stanford-futuredata/ColBERT is a compelling method for IR, I believe that LanceDB could benefit from a native implementation. Vespa has an implementation.

Looks like this is already tracked at #973.

I guess I was five days too early 😢


can't find trained weights file?

I was able to train car damage detection example. But after training, I could not locate the weight file(.h5). When I run inspect_custom_model.ipynb it gives the error that could not find mask_rcnn_damage.h5 file.

please check your root folder or on linux your documents folder
Sent from my iPhone

On Jul 23, 2018, at 1:37 PM, Karan Purohit<EMAIL_ADDRESS>wrote:
I was able to train car damage detection example. But after training, I could not locate the weight file(.h5). When I run inspect_custom_model.ipynb it gives the error that could not find mask_rcnn_damage.h5 file.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I checked but could not find it. There nothing mentioned in custom.py about where is trained weights are saved and in  inspect_custom_model notebook there is directly mentioned path of weight file= mask_rcnn_damage.h5.

finally got!

Could you tell me where it was, @008karan ?

It's located in the log-folder within the root directory.


[V3] Implement new Concept Exercise: sets

This issue describes how to implement the sets concept exercise for the JavaScript track.
Getting started
Please please please read the docs before starting. Posting PRs without reading these docs will be a lot more frustrating for you during the review cycle, and exhaust Exercism's maintainers' time. So, before diving into the implementation, please read up on the following documents:

The features of v3.
Rationale for v3.
What are concept exercise and how they are structured?

Please also watch the following video:

The Anatomy of a Concept Exercise.

Goal
This exercise aims to teach students how (and why) to use sets in JavaScript.
Learning objectives

Know how to add and remove elements from a Set
Know how to check whether a value is in a Set
Understand how Set checks equality
Know how to iterate over Set keys, values, and entries
Know how to convert between Set and Array
Know how to use Set to remove duplicate elements from an array
Know how WeakSet differs from Set
Understand when WeakSet might be preferable to Set

Out of scope

Implementing common set operations like union and difference

Concepts

sets

Prerequisites

arrays
array-destructuring
equality

After

Use cases for WeakSet
Lookup performance of Set vs. Array

Help
If you have any questions while implementing the exercise, please post the questions as comments in this issue.

I'm back from the dead and finally working on this 😅
I think I'm going to opt not to address WeakSet in this exercise after all, unless folks feel strongly that I should. I believe that it's not used commonly enough outside of library code to be valuable to students.

No, I think we can have a separate exercise, if at all! I agree that people barely use it in regular every-day use.

This issue was resolved with #1093. Thanks @kristinaborn. :clap:


Add compatibility for Dask 2021.06.0

This PR adds some compatibility updates for the dask=2021.06.0 release. xref https://github.com/dask/dask/pull/7743#issuecomment-853693448
cc @jbednar
Supersedes https://github.com/holoviz/spatialpandas/pull/69, xref https://github.com/holoviz/spatialpandas/issues/68#issuecomment-855285094

Thanks! Since you're a core Dask team member, I'll take this suggestion as the authoritative response for what to do for dask <=2021.5.0 and >=2021.6.0.

Yeah, sorry about the churn between the 2021.5.0 and 2021.6.0 releases. The changes here should provide compatibility for all but 2021.5.1 (it sounds like you're okay saying that's just a bad release).
From what I can tell, it looks like the CI failures here are unrelated to the Dask changes. Is that the case?

Thanks. Yes, I'm fine with ignoring 2021.05.1. I agree that the test failures seem unrelated, but I have no idea what is causing them.  Something to do with pyarrow, numpy or pandas, presumably?

Test failures are likely due to an old version of pyarrow getting installed. I'll try to fix.

Seems like conda can't solve for geopandas and a recent pyarrow version when pointed only at defaults so I've had to add conda-forge.

Thanks for the updates @philippjfr! For the remaining
ImportError: libpoppler.so.71: cannot open shared object file: No such file or directory

issue, there are a couple of upstream geopandas issue (xref https://github.com/geopandas/geopandas/issues/1109, https://github.com/geopandas/geopandas/issues/924) which look similar. In those other issues, setting a strict conda channel priority helped to get a more stable environment. I'm not familiar with all the commands being used to set up the CI environment (e.g. doit env_create) -- is there a way we can set the conda channel priority to strict in CI to see if that helps?

Thanks for the updates @philippjfr! It looks like there are some Python version inconsistencies in CI builds now. I've made a first attempt at resolving those issues, though since I've not committed to this repo before I need approval for CI builds to run

At this point all builds are passing other than the Python 3.7 macOS build, which is failing for some unknown reason. At this point I'm mostly mucking around in CI configuration that's not immediately related to the original dask=2021.06.0 compatibility changes. If a spatialpandas maintainer has some bandwidth, feel free to push directly to this branch.

Yeah, it's really not for you to worry about at this point. It just seems very difficult to get a working environment which includes geopandas (and therefore libgdal) and recent pyarrow, which works across platforms. Will maybe just disable the OSX test for now and ping the conda team about these issues again.

Would spatialpandas tests be able to use a "geopandas-core" package that didn't depend on GDAL or libgdal? At one point @jorisvandenbossche indicated that "we could easily look into making fiona/gdal optional for geopandas, as it is not a hard requirement". I'd love to be able to use geopandas in situations like this without having the dependency issues of GDAL. I know this wouldn't be an immediate solution, but for the long term...

The latest version of GeoPandas already doesn't hard-depend on fiona (as recently mentioned in https://github.com/holoviz/spatialpandas/issues/1#issuecomment-841198108), so you could install it with pip (just with --no-deps, since for user convenience we kept fiona as "install_requires" dependency, but geopandas will run without)
And for conda, I actually just looked into making a geopandas-base conda-forge package earlier this week: https://github.com/conda-forge/geopandas-feedstock/pull/90

A first user of geopandas-base! ;)
(it's actually good to get feedback on this if this works)

I assume you were a bit too fast. I only just merged the change right before, so it takes a bit before it is present on the conda channels. If you restart CI now, it should probably be better.

The Python 3.7 on macOS are running 🎉

Well that came just at the right time, thanks @jorisvandenbossche! And @jrbourbeau, sorry you had to deal with the bottomless pit of tears and despair that comes with dealing with any environment with a dependency on libgdal. Will merge and then tag a dev release.

No worries! I've got a couple of other small CI cleanup things I want to test out, but let's save that for a follow-up PR : )

dealing with any environment with a dependency on libgdal

BTW, if you use strict channel priority, in my experience this doesn't give that many tears (+ avoiding the default channel if you need recent versions)

In my experience that's true for most versions but some combinations of OSX and certain Python versions have still given me headaches recently.

Yes, thanks so much, everyone!  Truly a team effort! Now I can get back to the Datashader release that this was blocking.


Accuracy Issue

Hi, serengil. I use your code to test your model on the LFW. But the accuracy is not what you mentioned in your readme.md.   Facenet and ArcFace got excellent performance, but the others got very low accuracy. Have you tested all models? And is the threshold right? Could you give me some advice about this problem?

No, I didn't tested those models. Those are the values reference studies declared. Because I didn't train them. I used pre-trained models.
BTW, I alread mentioned them in my posts:
Blog: https://sefiks.com/2020/08/27/labeled-faces-in-the-wild-for-face-recognition/ (Dlib got 92% here)
Vlog: https://youtu.be/9fT-9TFjeDQ (ArcFace got 93% here)
Reference studies might use sup-samples in LFW or this is because of they are using different procedures for detection and alignment. The first one is more possible.

Thanks for your advice. I saw the video and the blog, which helped me a lot. But I still question the detail about the value of threshold within the function findThreshold in the code commons/distance.py. You know, the threshold is significant for us to verify image pairs, as we determine whether the image pairs are the same person. Could you tell me why you set the value like your function shows or share me the channels you refer to. Thanks again. Looking forward to your reply.
Below is your function(findThreshold) I mentioned.
'''python
def findThreshold(model_name, distance_metric):
base_threshold = {'cosine': 0.40, 'euclidean': 0.55, 'euclidean_l2': 0.75}

thresholds = {
	'VGG-Face': {'cosine': 0.40, 'euclidean': 0.55, 'euclidean_l2': 0.75},
	'OpenFace': {'cosine': 0.10, 'euclidean': 0.55, 'euclidean_l2': 0.55},
	'Facenet':  {'cosine': 0.40, 'euclidean': 10, 'euclidean_l2': 0.80},
	'DeepFace': {'cosine': 0.23, 'euclidean': 64, 'euclidean_l2': 0.64},
	'DeepID': 	{'cosine': 0.015, 'euclidean': 45, 'euclidean_l2': 0.17},
	'Dlib': 	{'cosine': 0.07, 'euclidean': 0.6, 'euclidean_l2': 0.6},
	'ArcFace':  {'cosine': 0.6871912959056619, 'euclidean': 4.1591468986978075, 'euclidean_l2': 1.1315718048269017}
	}

threshold = thresholds.get(model_name, base_threshold).get(distance_metric, 0.4)

return threshold

'''

Here, I explained how to determine those thresholds: https://sefiks.com/2020/05/22/fine-tuning-the-threshold-in-face-recognition/
I hope this helps you

@serengil As you see in the threshold list here VGG-Face and euclidean_l2 was 0.75 but now when I run it shows
{"distance":0.7931165562316705,"max_threshold_to_verify":0.86,"similarity_metric":"euclidean_l2","verified":true}
threshold is changed to 0.86.
Has there been an update in the model's thresholds?


Updated versions.json to specify correct branch

This should fix #1 and #2
Via this comment we know that fixing the branch name in versions.json will fix the issue

@brpaz Is there anything I need to do for this to be accepted?

Closes #1 #2 #4


road cards design tweaks

rebased and re-opened #628, now targeting master

Thanks! I'm still confused by git sometimes.
I'll comment on the other PR

Thanks for these fixes! Much closer to the design now.


[bug] Transfer rate from backend is very slow

Describe the bug
First, I apologize if this would not actually be considered a bug, as it is a performance issue.  But it was so bad that it made me think it was a bug at first.
Loading a 148MB .gif file took 194987.2ms (3.2 minutes). (Linux on Ryzen 7 5800u 16GB). One core on my machine was at 100% @4.4 GHz the entire time. This works out to about 1.3MB/s transfer rate. During that time, the window was hung -- could not even get to development tools.
I originally came upon the problem using a custom protocol handler, so I know that reading the file into memory took almost no time; it was all transfer time.
I don't have exact times for the release build, since I can't use development tools, but it was comparable timing. (And after updating to rc11 from rc07, I can no longer build the release version with this large file in it.)
For comparison, NW.js (which I'm porting from) loads this in less than 2 seconds. Brave browser with 100MB/s internet also loads the file in about 2 seconds.
All in all, I am loving Tauri, and this doesn't really affect most assets. But I thought you should be aware of the issue.
Reproduction

Start a new project with: yarn create tauri-app

Use this index.html:

<!DOCTYPE html>

Put this file in dist (it's too large to post to github):
https://i.imgur.com/Mghhw6X.gif

yarn tauri dev

Expected behavior
Mghhw6X.gif should appear in window in 2 -3 seconds.
Platform and versions
cargo tauri info

Environment
  › OS: OracleLinux 11.0.0 X64
  › Node.js: 12.22.5
  › npm: 8.10.0
  › pnpm: 6.11.0
  › yarn: 1.22.15
  › rustup: 1.24.3
  › rustc: 1.60.0
  › cargo: 1.60.0
  › Rust toolchain: stable-x86_64-unknown-linux-gnu

Packages
  › @tauri-apps/cli [NPM]: 1.0.0-rc.9
  › @tauri-apps/api [NPM]: 1.0.0-rc.5
  › tauri [RUST]: 1.0.0-rc.11,
  › tauri-build [RUST]: 1.0.0-rc.9,
  › tao [RUST]: 0.8.5,
  › wry [RUST]: 0.16.2,

App
`tauri.conf.json` error on ``: Additional property '$schema' is not allowed

Stack trace
No response
Additional context
No response

Sorry, I messed up the index.html.  It should be:
<!DOCTYPE html>

Ok, except I see the same timing when loading an external fie from disk using a custom protocol.  Reading the file into memory takes minimal time, but the transfer takes 3 minutes.

Just to be clear, my goal is to browse arbitrary images on the user's computer.  Including it in the build was just a simple way of demonstrating the issue.
In the end, I'm using an embedded Tide webserver to serve external files. Here is the timing:
release build, custom protocol handler: 175s
release build, Tide localhost server: 1s
In the attached sources, I've included both implementations.  Simply change index.html to refer to the file on your local machine.
This is 175x slowdown to use the custom protocol, so I'll be using the local server for my app.
tauri-test.zip

Similar problem here. Tauri appears to be 200x slower than Electron loading the same file.

Chiming in with the fact that I switched https://github.com/mikedilger/gossip from Tauri to egui back in December after a week of failing to debug or work around the tremendously slow performance surrounding transferring an updated vector of hashes to javascript. I didn't understand how to debug it. So I switched to egui and it was instant. Never looked back.

I have a similar problem, working on a project with a friend, for me, it takes more than 1 min to download a 25Mb PNG, but for my friend only 2ms, also reloading the UI during dev sometimes takes like 15s to load with a white screen and for my friend merely half a second.
tauri 1.2.2

I also have a similar problem，transfer 23mb file take about 10s，is serialization of binary data causing this issue?

"During that time, the window was hung -- could not even get to development tools."
It's strange because I've been trying to problem solve an issue with users locking up upon receiving large quantities of JSON data from the core's listener. Both similar hardware, but Intel vs AMD on Windows. Personally far better performance on my own Intel system, but I don't know if you can chalk it down to that at all, but my only lead on this issue is hardware.
As soon as I adjust my Windows process priority to high/realtime the issue becomes far less pronounced and I get far more stable performance between the webviews and tauri. Making about ~100MB transfer in a second or two. 5MB across 20+ windows with only some jittery framerate on windows, no lock ups.
Very odd. I am hoping this resolves the issues with the userbase on this issue.
Sorry for no benchmarks or technical info, but I thought I'd share what I've found.

+1
Just loading image (6.2MB) from an external source takes forever , compared to the browser.
Anything we can do?

"During that time, the window was hung -- could not even get to development tools." It's strange because I've been trying to problem solve an issue with users locking up upon receiving large quantities of JSON data from the core's listener. Both similar hardware, but Intel vs AMD on Windows. Personally far better performance on my own Intel system, but I don't know if you can chalk it down to that at all, but my only lead on this issue is hardware.
As soon as I adjust my Windows process priority to high/realtime the issue becomes far less pronounced and I get far more stable performance between the webviews and tauri. Making about ~100MB transfer in a second or two. 5MB across 20+ windows with only some jittery framerate on windows, no lock ups.
Very odd. I am hoping this resolves the issues with the userbase on this issue.
Sorry for no benchmarks or technical info, but I thought I'd share what I've found.

you can try tauriv2（https://github.com/tauri-apps/tauri/issues/9322）

+1
Just loading image (6.2MB) from an external source takes forever , compared to the browser.
Anything we can do?

you can try tauriV2( https://github.com/tauri-apps/tauri/issues/9322 )

i'll close this because of the improvements we made in v2. performance is still something we have constantly on our minds (though we're really hitting the limits with what webviews offer us) but i don't think there's much value in leaving this issue open nowadays.


Images not shown in 1.28.0

Summary
Images are not shown
Environment Information

Mattermost App Version: 1.28.0 via F-Droid

Steps to reproduce
View chat with images
Expected behavior
Images are shown.
Observed behavior

At the moment discussed in https://github.com/mattermost/mattermost-mobile/issues/4043

When I click on an image, I do not display a detailed image. I'm checking the latest version, commit 3013 - Bump app build number to 280 (# 4139)

On 1.29.0, app reinstall helped restore image display. Maybe cache clear would've worked but I forgot to try it first.

Can't retest as https://github.com/mattermost/mattermost-mobile/issues/4146 is blocking

1.31.2 does not help?

Fxied, thanks


Pointer position shifts in scaled Platform Views in Flutter 3.19 Android

Steps to reproduce

Run code sample.
Click some links on the page.

Expected results
Click at the same location as the cursor.
example: 3.13.9.mp4, 3.16.9.mp4, 3.19.1_ios.mp4

note

There is no problem with 3.13.9/3.16.9/3.19.1 on iOS.
webview_flutter: 4.5.0

Actual results
Click at a different position than the cursor.
example: 3.19.1.mp4
Code sample
Code sample
import 'package:flutter/material.dart';
import 'package:webview_flutter/webview_flutter.dart';

void main() => runApp(const _App());

class _App extends StatelessWidget {
  const _App();

  @override
  Widget build(BuildContext context) {
    return const MaterialApp(home: _Home());
  }
}

class _Home extends StatefulWidget {
  const _Home();

  @override
  State<_Home> createState() => _HomeState();
}

class _HomeState extends State<_Home> {
  final _controller = WebViewController();

  @override
  void initState() {
    super.initState();
    _controller
      ..setJavaScriptMode(JavaScriptMode.unrestricted)
      ..loadRequest(Uri.https('api.flutter.dev'));
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: const Text('Scaled WebView Tester'),
      ),
      body: Transform.scale(
        scale: 0.75,
        child: WebViewWidget(controller: _controller),
      ),
    );
  }
}

Screenshots or Video

Screenshots / Video demonstration
https://github.com/flutter/flutter/assets/17119410/5515de85-b74d-4e73-a9b7-9635d0f1335e
https://github.com/flutter/flutter/assets/17119410/ac180b87-d2d4-44d5-b319-39f489290354
https://github.com/flutter/flutter/assets/17119410/165aff31-33fd-4567-9166-fcadaa4a43c4
https://github.com/flutter/flutter/assets/17119410/e83602a7-4f53-419d-8c8e-b2188f9f9e90

Flutter Doctor output
Doctor output
3.13.9
HEAD is now at d211f42860 [flutter_releases] Flutter stable 3.13.9 Framework Cherrypicks (#137284)
+ flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[!] Flutter (Channel [user-branch], 3.13.9, on macOS 14.3.1 23D60 darwin-x64, locale ja-JP)
    ! Flutter version 3.13.9 on channel [user-branch] at /System/Volumes/Data/buildroot/flutter_3.13
      Currently on an unknown channel. Run `flutter channel` to switch to an official channel.
      If that doesn't fix the issue, reinstall Flutter by following instructions at https://flutter.dev/docs/get-started/install.
    ! Upstream repository unknown source is not a standard remote.
      Set environment variable "FLUTTER_GIT_URL" to unknown source to dismiss this error.
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2023.1)
[✓] VS Code (version 1.86.2)
[✓] Connected device (2 available)
[✓] Network resources

3.16.9
[!] Flutter (Channel [user-branch], 3.16.9, on macOS 14.3.1 23D60 darwin-x64, locale ja-JP)
    ! Flutter version 3.16.9 on channel [user-branch] at /System/Volumes/Data/buildroot/flutter_3.16
      Currently on an unknown channel. Run `flutter channel` to switch to an official channel.
      If that doesn't fix the issue, reinstall Flutter by following instructions at https://flutter.dev/docs/get-started/install.
    ! Upstream repository unknown source is not a standard remote.
      Set environment variable "FLUTTER_GIT_URL" to unknown source to dismiss this error.
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2023.1)
[✓] VS Code (version 1.86.2)
[✓] Connected device (3 available)
[✓] Network resources

3.19.1
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.19.1, on macOS 14.3.1 23D60 darwin-x64, locale ja-JP)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2023.1)
[✓] VS Code (version 1.86.2)
[✓] Connected device (3 available)
[✓] Network resources

Thanks for the report. Reproduced the issue using the latest package version webview_flutter: ^4.7.0.
Checking this with pure platform view (Hybrid composition and Virtual display modes), the issue is not reproduced.

Demo (Pure platform view and webview)

Pure platform view
Webview

flutter doctor -v (stable and master)
[✓] Flutter (Channel stable, 3.19.1, on macOS 14.1 23B74 darwin-x64, locale en-VN)
    • Flutter version 3.19.1 on channel stable at /Users/huynq/Documents/GitHub/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision abb292a07e (29 hours ago), 2024-02-20 14:35:05 -0800
    • Engine revision 04817c99c9
    • Dart version 3.3.0
    • DevTools version 2.31.1

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

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

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

[✓] Android Studio (version 2023.1)
    • Android Studio at /Applications/Android Studio Hedgehog.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.7+0-17.0.7b1000.6-10550314)

[✓] Android Studio (version 2022.2)
    • 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
    • android-studio-dir = /Applications/Android Studio.app/
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

[✓] VS Code (version 1.86.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.82.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-x64     • macOS 14.1 23B74 darwin-x64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 121.0.6167.184

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

• No issues found!

[!] Flutter (Channel master, 3.20.0-15.0.pre.20, on macOS 14.1 23B74 darwin-x64, locale en-VN)
    • Flutter version 3.20.0-15.0.pre.20 on channel master at /Users/huynq/Documents/GitHub/flutter_master
    ! Warning: `flutter` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 71fd015d05 (33 minutes ago), 2024-02-28 02:26:59 +0000
    • Engine revision fe7ea6d9c3
    • Dart version 3.4.0 (build 3.4.0-180.0.dev)
    • DevTools version 2.33.0-dev.11
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)
    • All Android licenses accepted.

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

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

[✓] Android Studio (version 2023.1)
    • 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
    • android-studio-dir = /Applications/Android Studio.app/
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)

[✓] VS Code (version 1.86.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.82.0

[✓] Connected device (4 available)
    • Pixel 7 (mobile) • 2B171FDH20084L                           • android-arm64  • Android 14 (API 34)
    • iPhone (mobile)  • d9a94afe2b649fef56ba0bfeb052f0f2a7dae95e • ios            • iOS 15.8 19H370
    • macOS (desktop)  • macos                                    • darwin-x64     • macOS 14.1 23B74 darwin-x64
    • Chrome (web)     • chrome                                   • web-javascript • Google Chrome 122.0.6261.69

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

! Doctor found issues in 1 category.

We have the same issue in a production application.
We are depending on https://pub.dev/packages/aad_oauth, which internally uses webview_flutter.
We are not scaling the platform views ourselves, but strictly using the package linked above. If I understand this correctly, this means that all applications using the plugin and flutter 3.19 will have the same issue. I will open a ticket on the plugin GitHub as well for transparency.

I found the commit that caused the problem by manual bisect:

ba578c77f2fbe58f6d6743deff72abae2d02fc9c is the first bad commit of flutter/flutter
engine changes: https://github.com/flutter/engine/compare/9d89f8727976...b02d59a2a607
engine PR: https://github.com/flutter/engine/pull/49268

By the way, @huycozy the shifted click position that I raised as an issue and the incorrect position of the text selection toolbar that is displayed after clicking may be independent issues.
Incorrect position of the text selection toolbar and handles seems to occur in 3.13.9 as well.

text selection toolbar with 3.13.9
https://github.com/flutter/flutter/assets/17119410/137d11b6-8496-4ca3-99b2-cf05d2f2bdca

Incorrect position of the text selection toolbar and handles seems to occur in 3.13.9 as well.

Thanks for checking. I also see this issue on Flutter 3.13.9 as well. I haven't found any filed issues before, please help to file a separate issue for this (and tag me on it)

With the shifted click position issue, it doesn't occur on Flutter 3.13.9 and 3.16.9 but on 3.19.1 and 3.20.0 as reported above. Based on your bisect result, adding regression label.

@huycozy I made new issue: https://github.com/flutter/flutter/issues/144685

We have the same issue in a production application.
We are depending on https://pub.dev/packages/aad_oauth, which internally uses webview_flutter.
We are not scaling the platform views ourselves, but strictly using the package linked above. If I understand this correctly, this means that all applications using the plugin and flutter 3.19 will have the same issue. I will open a ticket on the plugin GitHub as well for transparency.

We are facing the same issue. Flutter from 3.19 and above brakes login flow in our app because it is handled in webview. We have to stick to 3.16.9 where everything works fine.

any update？3.22.1 also


Night CI 2023-08-26: Failed

action url: https://github.com/kdoctor-io/kdoctor/actions/runs/5986731195

Success Rate 0.9719626168224299 is lower than request 1


ML 3.7 : BIRCH (A)

Description 📜
birch algo.applications,cf
Fixes # <4120>

Type of change 📝

[x] Au#dio (Should be in mp3 format Includes speech clarity, Concise ,Low distortion)

Domain of Contribution 📊

[x] Machine #Learning

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

@Isha307 @abhisheks008 please review on this

Just a small change there, ML_3_7_.... this will be the initial for the file name @ron352

Changed

PR merged @ron352


Web-App-Reporter maps each line of an error to a separate issue for NPM

The web app reporter maps the following 4-line error to 4 separate issues:
EEXIST: file already exists, open '/root/.npm/_cacache/tmp/3a8f6b96' File exists: /root/.npm/_cacache/tmp/3a8f6b96 Remove the existing file and try again, or run npm with --force to overwrite files recklessly.

This increases the amount of reported issues and makes it harder to get an overview of the errors.

@hanna-modica can you please double-check how this looks in the raw analyzer result and in the evaluated model report? I'd like to rule out that this is related to https://github.com/oss-review-toolkit/ort/pull/6624.


Newest releases not available on PyPI

The documentation says to install with pip install smooch.  However, the latest version on PyPI is 3.12.0.  I developed against the latest online documentation  (https://docs.smooch.io/rest/), which is v1.1 of the API.  However, that requires v4.0.0 of this library or greater, which is not available on PyPI.  Please upload the latest releases to PyPI.

Current latest version on PyPi is smooch 5.34.0


[Suggestion] Adding Activator support

This would make it so you can use an activator gesture to toggle the picker.

Thanks for the suggestion. I'm not familiar with Activator. Are there any examples or documentation that you can point me towards?

Oh this is for if flex was to be made into a mobile substrate tweak for jailbroken devices

There are other projects that support FLEX injection with substrate (e.g. https://github.com/dtrukr/FLEX_injected). Those repos are probably a better place for this feature suggestion.


Update to Aff 4.0

This updates the dependencies and code to Aff 4.0. There were some breaking changes that Aff no longer supports the success/failure callback method. There is still support under Control.Monad.Aff.Compat using EffFnAff and fromEffFnAff. The update was replacing the old Affs with EffFnAff, switching the success and error functions around, and removing the withClient function as it seemed like a duplicate of withConnection. This builds on the changes made in #18 and fixes #17.

@anttih I did a bunch of work here to abstract the query functions using a type class. Since both client and pool have a query function it seems like they can be abstracted as such. This also switches to more complex connection info objects. I think they should probably all be Maybe values and have the ConnectionInfo type class change them to Data.Nullables. That would require a new dependency so wanted to OK it with you first.

Sorry, what I meant by concentrating on the Pool is to leave the Pool querying methods for now and only allow querying a Client. This way you must use a Pool and take a client from there, but I think it keeps the API a bit simpler. I don't think abstracting over any queryable is important for this library.

Ya I figured that's not what you meant. I got excited and went overboard haha. I'll revert back to just the pool client. What do you think about the nullable settings though? A lot of the defaults for those settings are different types altogether (yay javascript) so we couldn't replicate the default in purescript.

Ok updated.
One thing about using the pool is that we need to call end on it before we finish but since we're passing the client around we don't have reference to it. I attached it to the client as a property so we can properly dispose of it. Seems like we're not really using the power of pools here but it works.

@tonyd256 I think we need to turn the connect FFI function to a version which calls a callback with the connection and the done callback, then we can use makeAff or whatever to turn that into an Aff.

Ok updated the config building code. I'm not clear on how to do what you're saying with the callback and done function. We're already using Aff with connect'. I don't think you're suppose to use callbacks with it like that anymore although I'm not really certain.

@tonyd256 Actually we don't have to use any callbacks, all we need to do is call release on the client. You are now calling client.release in end, but end disconnects all clients. withClient needs to only release the client so that the same client can be used again later. We should have
foreign import release :: Client -> Eff _ Unit

which we can use in bracket.

@anttih I think we still need to end the pool at some point right? Every time we call connect or withClient it creates a new pool and returns a single client from it. We're never closing that pool so we'll keep creating new pools and not closing them. I don't think this is good. Should the pool be a global variable that we pull clients from?

Ah, right. I think se should create the pool separately and pass into withClient. Then have separate end which should be called “manually” once you’re done.

Gotcha, I'll make some changes then.

Ok, what do you think about this?

I'm finding that I don't like this API. I want to do this withClient (mkPool connectionInfo) do .... but then the pool is gone and I never end it. It seems like every time I want to use this I need to create the pool before hand, run my queries, end the pool, return my results. This seems like a lot of back and forth. What about a separate function that closes the pool when finished? so users can choose between taking advantage of the pool or have the convenience of not having to close it.

Wrapping in another bracket does work fine. Not sure if you'd like a convenience function for that, otherwise it's usage will be similar to:
bracket
  (liftEff $ mkPool connectionInfo)
  (liftEff <<< end)
  (_ `withClient` (\c-> do
    -- do stuff here
  ))

or with a transaction
bracket
  (liftEff $ mkPool connectionInfo)
  (liftEff <<< end)
  (_ `withClient` withTransaction (\c-> do
    -- do stuff here
  ))

Once we nail down the API I'll make sure to update the docs too.

@anttih Any thoughts on what's left here? We're so close to getting this done :)

For our API we want a transaction per request. This is useful for rollback if anything in that request fails. One transaction means one client. We don't persist the pool over the API application.

Ok, maybe just call it withConnection and have it call mkClient with the client config, connectClient and then endClient. I think we should use the Client API for this and not create the pool at all.

So we could have withConnection :: ClientConfig -> (Client -> Aff _ a) -> Aff _ a

So after a chat with coworkers we do want to persist that so you're right.

Yes, most likely you want to persist it if it's any way possible.

Would you like me to bring back withConnection?

No, I think we should just have the Pool-based API until someone really wants it.

Thanks a lot!


Size of widget when not zooming should be controllable

Widget works great, except for the fact that it is not usable in a dialog, as it is impossible to pop it by clicking outside as the widget takes the full screen, even though the non-zoomed image does not fill the screen.

This can be solved by using Container with constraints as a parent


adds unit tests for phased training

adds simple unit tests for ilab model train --strategy lab-multiphase

@JamesKunstle do you still intend to work on this?


OTA reduce complexity 2

Description

Reduced complexity of following functions,

prvUpdateJobStatus_Mqtt
prvSubscribeToJobNotificationTopics
prvRequestFileBlock_Mqtt

Checklist:

[x] I have tested my changes. No regression in existing tests.
[ ] My code is Linted.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/bot run checks

/bot run checks


app not deployed

Describe the bug
I asked the ai to deploy the LPP solver and it too long just to show an error, kindly fix this
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-2pq2yx
Steps to reproduce
just the deployment part
Expected behavior
it should have given a deployed webapp with all the features working
Screen Recording / Screenshot

Platform
Browser name = Chrome
Full version = <IP_ADDRESS>
Major version = 130
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 50164828,
  "usedJSHeapSize": 44870980,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Username = ANSHUKR123
Chat ID = a6842520b2d2

Additional context
Error:
An error occured while streaming this message.

i had the same issue and i tried several times to restart the installation of a library but it get stuck again. At the same time i lost a lot of tokens for nothing each time that i tried to restart the same question...

What is the problem Exactly?
On Wed, Oct 30, 2024, 11:24 AM Albix81 @.***> wrote:

i had the same issue and i tried several times to restart the installation
of a library but it get stuck again. At the same time i lost a lot of
tokens for nothing each time that i tried to restart the same question...
—
Reply to this email directly, view it on GitHub
https://github.com/stackblitz/bolt.new/issues/1179#issuecomment-2446699804,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARG6BUBMZXLAZDPDFT2EYATZ6C6VNAVCNFSM6AAAAABQ33KYVKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBWGY4TSOBQGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

@ANSHUKR123 @jerminor thanks for your patience during this beta period! This issue is being tracked and investigated in #1022 so please subscribe there for updates!

The package.json file contains mostly deprecated versions of packages
On Fri, Nov 1, 2024, 9:35 PM Alexander Berger @.***>
wrote:

@ANSHUKR123 https://github.com/ANSHUKR123 @jerminor
https://github.com/jerminor thanks for your patience during this beta
period! This issue is being tracked and investigated in #1022
https://github.com/stackblitz/bolt.new/issues/1022 so please subscribe
there for updates!
—
Reply to this email directly, view it on GitHub
https://github.com/stackblitz/bolt.new/issues/1179#issuecomment-2452623121,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARG6BUF3AK2XAALNNI5VF23Z6PXZ7AVCNFSM6AAAAABQ33KYVKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJSGYZDGMJSGE
.
You are receiving this because you were mentioned.Message ID:
@.***>


Capitalize title of No MCVE article

The titles on all of the other articles are capitalized, so this makes it consistent. (The homepage was driving me nuts.)

Done. Now, does this make you nervous? http://i.stack.imgur.com/Mgqut.jpg


testtool: make it work with Benchmarks and sub-tests

Fixes #ENGT-11909, relates to #ENGT-11837

Will not merge this until I have my continuum PR done and green, with this vendored in


[ADDED]: Auto comment feature

Description
I have created a Workflow that automatically commits when an issue is opened, a pull request is created, an issue is closed, or an issue is assigned or unassigned.

@fangyinc Review PR.

@fangyinc Review PR.
Thank you for your contribution, we will consider and test this workflow.

Hi @Killer2OP, can you fix the CI error？

Hi @Killer2OP, can you fix the CI error？

Hi @Killer2OP, can you fix the CI error？

 Enable these settings to make the CI work.

I have enable these settings and rerun the CI, but the CI has a error

@Killer2OP do you have a plan to fix this?

@Killer2OP Thank you for your contribution. However, I'm concerned that this approach might result in sending an excessive amount of non-essential information to our users, which could potentially lead them to categorize our emails as spam. I believe this PR might not be the best option in light of these considerations.


Added shortcut info for PluginManager

Description
Please describe your pull request:

Why is it necessary?
The menu item should have a shortcut info
What does it improve?
Adds a info on menu point
Does it have side effects?
Nope

Questions
Answers

BC breaks?
no

Tests pass?
yes

Related tickets?

How to test?

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/#/issues/SW-17966.
Please use this issue to track the state of your pull request.

thanks @shyim :+1:


[MRESOLVER-184] Add destroy hook

And use this hook in Hz and Redisson implemenetations. Drop redundant
code from HZ as well.

Is this a candidate for autoclosable?

Is this a candidate for autoclosable?

@rfscholte um, could you elaborate your question a bit? NamedLockSupport IS AutoCloseable, so what you mean by "this"?

I was wondering if destroy was a synonym for close. Only for the latter you can use autoclosable.
But is seems like that is already covered, so never mind.

Superseded by https://github.com/apache/maven-resolver/pull/111


Store version serialized as @null and fails to deserialize

To reproduce in arcs-live:

accept "Select X favorite food" suggestion
the serialization in fb contains:

...
store Store1 of FavoriteFood {Text food} '!855611589143340:app-shell-711sr9tef89zlrphj:59' @null #favorite at 'firebase://arcs-storage.firebaseio.com/...

When trying to deserialize, getting the following error:
Expected [0-9] but "n" found.
  store Store1 of FavoriteFood {Text food} '!855611589143340:app-shell-711sr9tef89zlrphj:59' @null #favorite at 'firebase://arcs-storage.firebaseio.com/AIzaSyBme42moeI-2k8WgXh-6YK_wYyjEXo4Oz8/0_4_1-alpha/arcs/-LMeEsGM_kdv3TFB9qOR/handles/!855611589143340:app-shell-711sr9tef89zlrph

Here is the serialization code:
https://github.com/PolymerLabs/arcs/blob/master/runtime/arc.js#L147
@shans Let me know, if you think just serializing version as 0 is fine and i'll prepare a PR.
FYI: At first I suspected this is something related to Variable vs Collection, but I managed to reproduce it for descriptions collection store as well (in restaurants demo) - if you set a conditional breakpoint at that line with handle.version == null you'll get it at some point.

If I manually serialize, then I get this resolving to version 0. So this is probably a race condition in precisely when we choose to store the serialized version.
Based on that, I think that it's definitely fine to always convert 'null' to 0.
I'm happy to prepare the PR if you want?


Error executing action create_site on resource 'arcgis_enterprise_portal[Create Portal Site]'

Hello i have problem with creating a site. And I have tried this for a weeks now, and still i have not had any success.
Can someone help me.
I am trying to make arcgis for portal, but chef can not make website. i can make website in virtualbox via URL link: https://localhost:7443/arcgis/home/createadmin.html
i can add my attributes as well, if needed.
`
Resource Declaration:
---------------------
# In C:/Users/vagrant/AppData/Local/Temp/kitchen/cache/cookbooks/arcgis-enterprise/recipes/portal.rb
        76: arcgis_enterprise_portal 'Create Portal Site' do
        77:   portal_url node['arcgis']['portal']['url']
        78:   portal_private_url node['arcgis']['portal']['private_url']
        79:   web_context_url node['arcgis']['portal']['web_context_url']
        80:   username node['arcgis']['portal']['admin_username']
        81:   password node['arcgis']['portal']['admin_password']
        82:   full_name node['arcgis']['portal']['admin_full_name']
        83:   email node['arcgis']['portal']['admin_email']
        84:   description node['arcgis']['portal']['admin_description']
        85:   security_question node['arcgis']['portal']['security_question']
        86:   security_question_answer node['arcgis']['portal']['security_question_answer']
        87:   install_dir node['arcgis']['portal']['install_dir']
        88:   #content_dir node['arcgis']['portal']['content_dir']
        89:   content_store_type node['arcgis']['portal']['content_store_type']
        90:   content_store_provider node['arcgis']['portal']['content_store_provider']
        91:   content_store_connection_string node['arcgis']['portal']['content_store_connection_string']
        92:   object_store node['arcgis']['portal']['object_store']
        93:   log_level node['arcgis']['portal']['log_level']
        94:   log_dir node['arcgis']['portal']['log_dir']
        95:   max_log_file_age node['arcgis']['portal']['max_log_file_age']
        96:   upgrade_backup node['arcgis']['portal']['upgrade_backup']
        97:   upgrade_rollback node['arcgis']['portal']['upgrade_rollback']
        98:   root_cert node['arcgis']['portal']['root_cert']
        99:   root_cert_alias node['arcgis']['portal']['root_cert_alias']
       100:   action :create_site
       101: end
       102:

       Compiled Resource:
       ------------------
       # Declared in C:/Users/vagrant/AppData/Local/Temp/kitchen/cache/cookbooks/arcgis-enterprise/recipes/portal.rb:76:in `from_file'

       arcgis_enterprise_portal("Create Portal Site") do
         action [:create_site]
         default_guard_interpreter :default
         declared_type :arcgis_enterprise_portal
         cookbook_name "arcgis-enterprise"
         recipe_name "portal"
         install_dir "C:\\Program Files\\ArcGIS\\Portal"
         portal_url "https://localhost:7443/arcgis/home/"
         portal_private_url "https://domain.com:7443/arcgis/home"
         web_context_url "https://domain.com/portal"
         username "admin"
         password "Passw0rd"
         full_name "Administrator"
         email<EMAIL_ADDRESS>         security_question "Your favorite ice cream flavor?"
         security_question_answer "bacon"
         content_store_type "fileStore"
         content_store_provider "FileSystem"
         content_store_connection_string "C:\\arcgisportal\\content"
         object_store "null"
         log_level "WARNING"
         log_dir "C:\\arcgisportal\\logs"
         max_log_file_age 90
         upgrade_backup true
         upgrade_rollback true
         root_cert ""
         root_cert_alias ""
       end

       System Info:
       ------------
       chef_version=13.11.3
       platform=windows
       platform_version=10.0.14393
       ruby=ruby 2.4.4p296 (2018-03-28 revision 63013) [x64-mingw32]
       program_name=C:/opscode/chef/bin/chef-client
       executable=C:/opscode/chef/bin/chef-client

   Running handlers:
   [2019-01-21T02:23:13-08:00] ERROR: Running exception handlers
   Running handlers complete
   [2019-01-21T02:23:13-08:00] ERROR: Exception handlers complete
   Chef Client failed. 32 resources updated in 08 minutes 15 seconds
   [2019-01-21T02:23:13-08:00] FATAL: Stacktrace dumped to C:/Users/vagrant/AppData/Local/Temp/kitchen/cache/chef-stacktrace.out
   [2019-01-21T02:23:13-08:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
   [2019-01-21T02:23:13-08:00] FATAL: RuntimeError: arcgis_enterprise_portal[Create Portal Site] (arcgis-enterprise::portal line 76) had an error: RuntimeError: `

best regards
Joosep

Hi @pbobov
I'm having a similar issue with my installation. We're using the latest cookbook version (3.4.0) to install ArcGIS Enterprise on CentOS, the environment is offline and I've managed to load in the necessary dependencies (Java/ Tomcat, yum packages, etc)
I noticed in the output from @J0ss1 theirs fails after 8 minutes, mine usually takes almost an hour to return anything from the create site stage. Unfortunately I won't be able to provide the full contents of the stacktrace output as extracting files from this environment is a lengthy process, but the top few lines contain the following:
TypeError: portal.rb:60: exception object expected
portal_admin_client.rb:817 in 'raise'
portal_admin_client.rb:817 in 'validate response'
portal_admin_client.rb:126 in 'complete upgrade'
providers/portal in 'block in class from file'

I appreciate this might not be much to go on, but any suggestions would be much appreciated

Hello @tomrussell,
Could you please provide your Chef template in which you are running your chef deployment off of?
Any chance you could provide the full failure response?

Hi @Nickolaitc - thanks for getting back to me
I'm using the arcgis-enterprise-rhel template, from the 3.4.0 cookbook
We've gotten a little further in our investigation, we've managed to identify that the failure is happening while the initial portal installation is being upgraded with the license file, I can verify that this fails through the web UI as well. In both places I get a 500 error code response with no error message. We also noticed the portal postgres database crashed, is this a likely cause for the error? How do we troubleshoot this?

Hey @tomrussell
With the 3.4.0 cookbook and the pre-configured roles files, there are still a few things we will need to complete before we can just utilize this file.
An example would be "java".  10.7.x doesn't utilize JDK, it actually utilizes OpenJDK.
"java":{
"install_flavor": "openjdk",
"jdk_version": "8"
},
How is space looking on this CentOS system?

The VM is fresh, there's over 70GB free space on there
Would we need to clean install the VM to be able to install Java with the OpenJDK installer? Is there anything else that would need altering for this role file to work correctly?

@tomrussell that should be plenty of space, but, how is that space allocated to the directories in which is we are using for the Enterprise?
It is hard to tell what could need changing.  I know something else that could be problematic is the "version" being listed as 10.7 when it should be 10.7.1.
Could you provide the template with your edits?

Hi @Nickolaitc,
ArcGIS should have the full volume allocated for installation and the data directories
I've attached the Enterprise RHEL template with the modifications I've made to support installing Java and Tomcat without internet access
arcgis-enterprise-rhel.json.zip

@tomrussell Have you been able to test the Portal .json license in any other Portal for 10.7.1?  Can you verify the license is in fact 10.7.1 and not 10.7?

The installation files I’m using are for 10.7, the license has been verified for that version. Is the 3.4.0 version of the cookbook only supporting 10.7.1?


Change in core to only pass args if expected in command method

Closes: https://github.com/Azure/azure-cli/issues/5357
This checklist is used to make sure that common guidelines for a pull request are followed.
General Guidelines

[y ] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

Closing for now. We can reopen the PR if autorest 3.0 doesn't address the underlying issue.


Don't Create Objects for same speakers

@championswimmer In the current approach, If a speaker is taking sessions of two different session-type described in JSONS as two objects having same speaker name but all other things like microlocation different.
It is creating two objects and hence we see repeated speaker photos.
The correct approach may be is to not create such objects again. What should be the unique key. Should I not create Speaker with the  same name?  In track page we do it like by creating slug which is the combination of date and track name.

Please fix the original sample JSON instead of implementing a work around. There is an issue here https://github.com/fossasia/open-event/issues/57 Please help to resolve it.

@mariobehling This issue is different from fossasia/open-event#57. It is quite possible that a speaker is associated with many sessions. In that case the code should be written such that it will map all sessions associated with the speaker under one speaker name.Currently, it is creating multiple entries even if JSON is correct.

as per the folding code, even if one speaker has multiple session, his name
should be present only once in the speaker page. is it not happening the
same right now ?
On 4 August 2016 at 03:06, @angularboy<EMAIL_ADDRESS>wrote:

Reopened #564 https://github.com/fossasia/open-event-webapp/issues/564.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fossasia/open-event-webapp/issues/564#event-744489192,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABQ_yrOwcqkzziJ84PZKE3RkKqIhe67bks5qcQnLgaJpZM4JcGOs
.

the speaker page should have exactly as many speakers as there are objects
in the /speaker endpoint.
right ?
On 4 August 2016 at 03:14, Arnav Gupta<EMAIL_ADDRESS>wrote:

as per the folding code, even if one speaker has multiple session, his
name should be present only once in the speaker page. is it not happening
the same right now ?
On 4 August 2016 at 03:06, @angularboy<EMAIL_ADDRESS>wrote:

Reopened #564 https://github.com/fossasia/open-event-webapp/issues/564.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fossasia/open-event-webapp/issues/564#event-744489192,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABQ_yrOwcqkzziJ84PZKE3RkKqIhe67bks5qcQnLgaJpZM4JcGOs
.

Exactly, but it is working to /sessions endpoint Taking all speakers from sessions data and than mapping each with speaker information.
The bug here is
"session_type": {
"id": 19,
"name": "Workshop, 1/2 h"
},
"short_abstract": "",
"signup_url": null,
"slides": null,
"speakers": [
{
"id": 27,
"name": "Ulrike Thalheim",
"organisation": "metacollect"
},
{
"id": 28,
"name": "Moritz Beber",
"organisation": "metacollect"
}
and  "session_type": {
"id": 20,
"name": "Lightning Talk"
},
"short_abstract": "",
"signup_url": null,
"slides": null,
"speakers": [
{
"id": 27,
"name": "Ulrike Thalheim",
"organisation": "metacollect"
},
{
"id": 28,
"name": "Moritz Beber",
"organisation": "metacollect"
}

@aayusharora yeah that sounds right to me

@mariobehling  @championswimmer Solved in #562


Backward op support for heaviside

For Heaviside backward op is available in torch. Please find the below reference code


Issue #9

Acknowledgments

[x] I confirm that I wrote the code based on the company guidelines.
[x] I confirm that I followed the Git flow described in the company guidelines.

Description
Have a fullscreen video playing from a RTSP source.
Issue(s): #9

@ivsimaku it is super simple! :) and it works also with HTTP, which is super nice :) One thing though, when I run the command on a Raspberry Pi 3 B+ I get around 2FPS, and all 4 cores are at 99% it seams that the video stream is decompressed with software an not hardware. Where the RPi has hardware support for mp4 for example.
It be nice if you can find a solution to make sure the video is proceed with hardware and not software.

@davidgatti I just tested it with VLC and that seems to work a lot better, better FPS and only 40% CPU usage:
vlc --fullscreen rtsp://:@<address|IP>:<port#>/
Give this a try and let me know. I will have to move this under VLC if that is satisfying.

Lets do that, but keep both, with an explanation about the FPS state.

Check this one more time so I can finalize the pull on this.


feat: enable usePrettyRefs for nextJS publishing and preview

This PR:

enables config.usePrettyRefs and config.site.userPrettyRefs that overrides how note references are rendered in preview and publishing respectively.
adds tests for both cases
updates snapshots

can you take a look at the integration test failure?


[Suggestion] Creating a response object

Informations

Type
Version

Suggestion
4.x

Description
Before this framework, I used to work with Java - Spring Boot.
When returning an object there, you usually wrap it with a ResponseEntity object that allows you to do things like setting the response status code easily.
Example (Java):
@RequestMapping(value = "/create", method = RequestMethod.POST)
@ResponseBody
public ResponseEntity<User> createUser() {
    User user = new User()
    return new ResponseEntity(user, HttpStatus.CREATED);
}

For now, in TsED you need to do the following:
@Post('/create')
createUser(@Response() response: ExpresResponse): User {
    response.status(201);
    return new User();
}

My suggestion is the create a Response (maybe with a better name) wrapper that will allow doing the same and will look like this:
@Post('/create')
createUser(): Response<User> {
    return new Response<User>(new User(), 201);
}

I think this is much cleaner and more intuitive, but I come from Java 😜
What do you think?

It is good idea.
Does Response object can set additional headers?

You could also do this
@Post('/create')
@Status(201)
createUser(): User {
    return new User();
}

Yes, I know :)
But in some situations it is a need to set header when its value can only be calculated  in request callback (controller method).

u could always throw errors and capture them on a middleware written the appropriate response for each case.. which is much cleaner than setting this info directly in the "request callback"

@milewski it's true, but only for error codes, right?
and as @kalu111 said, you could also set headers this way... by maybe I'm wrong cause thinking of it it might too similar to the Express response object, so we might just want to use it...
I'm not sure, this is why it's a suggestion 😅

Hi guys,
If you want test your concept (to begin), it's possible without modification in tsed. The middleware that is responsible to build response is the SendResponseMiddleware.
You can override this middleware and implement your logic.  Then, if you think, this feature is interesting and maintainable, you can create a PR and propose this feature either in @tsed/common or as a separated module ;) (some
See you guys,


Now it can install micro into /usr/bin (makefile-build only, unix-only)

IMO, you should make use of DESTDIR, and PREFIX, see https://www.freebsd.org/doc/en/books/porters-handbook/porting-prefix.html
See line 1, 2, 10  and 11 in this Makefile for example: https://github.com/sdhand/n30f/blob/master/Makefile

Wut? Still no checked by owner...

Hi, sorry I didn't comment on this. I'm not sure this is really necessary -- the user should probably do that themselves because it requires sudo.
Also is there something special about calling the rule sysinstall_linux?

It's for easily installing text editor into system, without adding gopath into $PATH variable. Good for those who don't use Go


Fix infinite loop when guessing argument type from parent class

Closes #44281
This PR fixes an infinite loop that happen in gdscript_editor.cpp when, during validation, the code is guessing a method's argument type.
If the parent class does not have the same method name, the code should then try the parent's parent and so on, until finding it or not, but it does not, leading to the infinite loop.

It's not directly related to this PR but just FYI, the email you use to author your commits (see https://github.com/godotengine/godot/commit/20f18f1621adeeebfaab59daee01f4dcc336596a.patch) doesn't seem known to your GitHub account, which is why the commits don't show as authored by "@Blackiris".
That's not a problem for Git, but if you want to claim ownership of those commits, you can add this email as secondary email in your GitHub settings.

It's not directly related to this PR but just FYI, the email you use to author your commits (see https://github.com/godotengine/godot/commit/20f18f1621adeeebfaab59daee01f4dcc336596a.patch) doesn't seem known to your GitHub account, which is why the commits don't show as authored by "@Blackiris".
That's not a problem for Git, but if you want to claim ownership of those commits, you can add this email as secondary email in your GitHub settings.

Oh thanks! I don't mind ownership oh these commits to be honest. I am using Godot for a few years so I think it is just time to give some little back. I would prefer to give 100% of the ownership to the project, but indeed, Godot belongs to all. I will add my secondary email as you recommend.

Oh by ownership I just meant that your account gets identified visually as the author, I'm not talking about copyright/code ownership.
Regardless if what the email used is, you're the legal copyright holder for the code you author :)

Thanks!


Allow modifying function prototypes

Hello! Not sure if this is the right place but:
At the moment, the functional_widget example is used as:
void main() {
  runApp(const MyApp());
}

@FunctionalWidget(widgetName: 'MyApp')
Widget _buildApp(BuildContext context,
    {String? appTitle, String? homePageTitle}) {
  return MaterialApp(
      title: appTitle ?? 'Flutter Demo',
      theme: ThemeData(primarySwatch: Colors.blue),
      home: MyHomePage(title: homePageTitle ?? 'Flutter Demo Home Page'));
}

This means the widget is defined as _buildApp but used as MyApp.
This isn't ideal at it breaks the developer experience:

a newcomer searching for "MyApp" may not know that its implementation is instead "_buildApp"
go-to-definition on "MyApp" will point to the generated code when it would be more intuitive to be redirected to _buildApp
"find all references" on _buildApp will not fill all the places where MyApp is used. Instead, it will point to the generated code, and we would have to use "find all references" on MyApp.
Since _buildApp and MyApp are separate entities, if we want to rename MyApp, we need to also rename _buildApp for consistency
developers may sometimes make the mistake of using "_buildApp" instead of "MyApp", when they should always use the class instead of the function (this is a common mistake with the functional_widget package)

It would be great if rather than creating a new element, we could override an existing element with a different prototype. So that all the developer tooling keeps working.
For example, considering classes no longer need a "new" keyword, one solution could be to transform:
@functionalWidget
Widget MyApp(BuildContext context, {required String title}) {
  return Text(title);
}

into:
class MyApp extends StatelessWidget {
  const MyApp({Key? key, required this.title}): super(key: key);
  final String title;
  @override
  Widget build(BuildContext context) {
    return Text(title);
  }
}

This would potentially require deleting the original function or modifying the name of the original function. But I agree that it would be more intuitive to users.

We currently do have a principal of not wanting to modify any existing code in unsurprising ways. This would include changing a function to be a class.
These decisions aren't yet final and we will keep the use case in mind though.
We will be trying to address most of these concerns through the general IDE experience though - although the details aren't fully fleshed out yet. We want jump to definition to work for generated code (exactly where it should take you is an open question). For instance we could say jump to definition of anything generated should just take you to the macro application in user code (so it would take you to the _buildApp function in this case, if you navigated to MyApp). Or we could take you to a synthetic file and show you the generated MyApp class. You would see the reference to the _buildApp function in the build method there and could then navigate to that. Or maybe we would have a quick link on generated declarations to take you to the macro application that generated that thing. Lots of options here.

Note that this isn't limited to functional_widget
The desire for modifying existing code is voluntary. I could see many use-cases.
For example Mobx-like action:
class Example {
  @action
  void method() {
    print('hello');
  }

  void another() {
    method();
  }
}

would become:
class Example {
  @action
  void method() {
    final event = mobx.startAction();
    try {
      print('hello');
    } finally {
      event.stop();
    }
  }

  void another() {
    method();
  }
}

Or debounce:
class Example {
  @Debounce(Duration(seconds: 1))
  void method(int param) {
    print('hello $param');
  }

  void another() {
    method(42);
  }
}

would become:
class Example {
  Timer? _methodTimer;
  @Debounce(Duration(seconds: 1))
  void method(int param) {
    _methodTimer?.cancel();
    _methodTimer = Timer(Duration(seconds: 1), (_) {
      print('hello');
    });
  }

  void another() {
    method(42);
  }
}

With those examples, if generated code can't replace existing code, that would make the refactoring process extremely tedious.
And another difficulty is that it will be difficult to compose generators.
For example we may want to use both @action and @debounce:
class Example {
  @Debounce(Duration(seconds: 1))
  @action
  void method(int param) {
    print('hello $param');
  }

  void another() {
    method(42);
  }
}

which would generate:
class Example {
  Timer? _methodTimer;
  @Debounce(Duration(seconds: 1))
  @action
  void method(int param) {
    _methodTimer?.cancel();
    _methodTimer = Timer(Duration(seconds: 1), (_) {
      final event = mobx.startAction();
      try {
        print('hello $param');
      } finally {
        event.stop();
      }
    });
  }

  void another() {
    method(42);
  }
}

If we can't override existing code, that will make such composition awkward.

Alternatively, we could have flutter_hooks use code-generation to transform:
class Example extends StatelessWidget {
  Widget build(context) {
    @state int count = 0;

    return Scaffold(
      body: Text('$count'),
      floatingButton: FloatingButton(
        onPressed: () => count++;
      ),
    );
  }
}

into:
class Example extends StatefulWidget {
  createState() => _ExampleState();
}

class _ExampleState extends State<Example> {
  int _count = 0;

  Widget build(context) {
    return Scaffold(
      body: Text('$_count'),
      floatingButton: FloatingButton(
        onPressed: () => setState(() => _count++);
      ),
    );
  }
}

The @action and @debounce ones are a bit different than what you want with functional widget - you aren't converting a method to a different type of declaration or changing the static type of it.
We currently do allow method wrapping, and the intention is to enable this style of macro, but the api exposed currently only allows injecting statements above and below the existing body, and they are also in their own scope and can't control exactly how the original body is wrapped. That wouldn't enable either of these so I think we should go back to the drawing board a bit on that api 👍 .
Suggestions welcome - I will start thinking more about this as well. We do want to ensure that the original method body isn't modified though.

One possible option here is we could just provide you with the original body as a Code object. That allows you to plop it directly into the new method, and just trust that you will use that somewhere. That is really flexible and users would likely complain to macro authors if they wrote macros that just discarded the entire original body haha.

cc @munificent thoughts?

The @action and @debounce ones are a bit different than what you want with functional widget

Debounce is technically a function prototype change, as it modifies the return type from T -> void or T -> Future<T> depending on the implementation.

Debounce is technically a function prototype change, as it modifies the return type from T -> void or T -> Future<T> depending on the implementation.

True, I don't think we would want to allow that though. I understand it also feels weird to ask the user to make their function async when they don't do anything async - but I think its worse if the jump to definition for a method shows you the wrong return type in the actual code.
I am not sure exactly what the right balance to strike here would be, we could allow code like this to be valid, as long as the macro eventually modifies the function to return a Future for instance:
@debounce
Future<void> method() {
  print('hello');
}

But that also is a bit weird to look at, as the function looks invalid at first glance.

Random thought, feel free to reject. What if the macro system generates code into a collapsed block right after the annotation. Then you have both signatures side by side and the user would be less confused by changes / have to hop between files.
@debounce{{ /// <- collapsible region
  Future<void> method() {
    print('hello');
  }
}}
void method() {
  print('hello');
}

One possible option here is we could just provide you with the original body as a Code object. That allows you to plop it directly into the new method, and just trust that you will use that somewhere. That is really flexible and users would likely complain to macro authors if they wrote macros that just discarded the entire original body haha.

In this case, rather than the function body, could the macro receive the entire annotated bloc (so the function + parameters)?
I believe the rule of "users would complain if the macro changes the code in a way that isn't expected" still applies.
If the prototype of a function changes due to a macro, then this is part of the contract of the said macro. Therefore if a user sees a method annotated, they would know that the prototype changed.
This is similar to what JS allows with decorators. Some examples would be withTheme/withReducer from popular React packages, which do something very similar to what the functional_widget example does.

I do still currently feel that we should draw a line at allowing modification of the static type of existing declarations. Modifying function bodies through conceptually just "wrapping" them feels a fair bit less magic/unexpected to me. A user just looking at my API doesn't necessarily understand all the macros I am using, or how they modify my API. The exact implementation of my APIs matters a lot less imo, than the static shape of them, to my users.
I will acknowledge however that there are additional use cases to be had by allowing such modification. For instance the current flutter widget transformer adds a parameter to all widget constructors (and field to the class I believe), and then also modifies all constructor invocation sites to pass an argument for that (this is how the debug tool can navigate to the line of code that created a widget from the inspector). Being able to migrate that to a macro would indeed be nice, as the transformer is brittle.
So, I won't take it completely off the table yet :).

user just looking at my API doesn't necessarily understand all the macros I am using, or how they modify my API.

Is the concern about the public interface of packages?
If so, that's a fair concern.
But is there no way to fix this? Like have the IDE/go-to-definition when pointing to a package show the generated code?

Is the concern about the public interface of packages?

Correct, this is my primary concern.

But is there no way to fix this? Like have the IDE/go-to-definition when pointing to a package show the generated code?

We are going to end up leaning  heavily on the IDE (and analyzer) for a lot of things, but we do want to maintain a certain level of support for non-IDE users. There is a pretty big difference imo between synthesizing whole new declarations that those users just won't be able to see (outside maybe a debugger), and completely changing the shape of the program as they perceive it.

Rather than the IDE, could this be taken care of by pub?
As in, when installing dependencies, their generators are already executed.
So it would be similar to publishing generated code on pub.

As in, when installing dependencies, their generators are already executed.

This gets complicated with path dependencies (at a minimum - the root package). You have to regenerate often for these. In general having this happen outside of the compilers is the largest complaint of the existing build_runner package. We also don't want to actually modify code on disk.
Ultimately one of the biggest problems we want to solve is the direct compiler integration, to make workflows like the edit/refresh cycle in flutter better, and improve the efficiency of code generation by sharing state with the compiler and directly hooking in to the hot reload flow.
And then also the usablity in terms of not needing to explicitly import part files and reference generated symbols.

I do still currently feel that we should draw a line at allowing modification of the static shape of existing declarations.

That line doesn't exist for users writing code generators today, does it? With code gen, you can do whatever you want and yet users seem to generally do reasonable things.

Modifying function bodies through conceptually just "wrapping" them feels a fair bit less magic/unexpected to me.

Agreed. I would prefer that most macros don't muck with signatures or method bodies in surprising ways. But I don't know if it's necessary for the macro API to strictly prohibit that, and I don't know if prohibiting it is a net win if it also prohibits beautiful, powerful use cases.
Unless there are technical reasons to restrict macros in certain ways, I would tend towards letting users do what they want and rely on their taste (and the negative feedback of their peers!) to guide them towards not writing macros that are nightmares to use.
I can remember in the early days of Dart users told us that Dart allowing operator overloading was a huge mistake because users would invariably use it to write nightmarish unreadable APIs. But... it turns out users don't want to write nightmarish unreadable APIs because then no one uses them and users like people to use their code.

A user just looking at my API doesn't necessarily understand all the macros I am using, or how they modify my API. The exact implementation of my APIs matters a lot less imo, than the static shape of them, to my users.

True. The closer a macro's output can reflect the structure of its input, the easier it will be for users to understand. But that's only one of several trade-offs a macro author might have to make and it might be good to give them enough flexibility to let them make that trade-off.
Also, users will need to see how macros modify the implementations of APIs so that they can step through them. We'll have to do the tooling work here regardless, so that will probably be equally useful in showing how a macro modifies signatures if we allow macros to do that.

That line doesn't exist for users writing code generators today, does it? With code gen, you can do whatever you want and yet users seem to generally do reasonable things.

Existing codegen (via package:build) is actually very restrictive. You can only create new parts or libraries, so there is no way to overwrite anything existing.
We don't generally hear complaints about that part in particular, people are much less happy with the other aspects like having to declare outputs as a mapping of input extension to output extension which is very limiting.

Unless there are technical reasons to restrict macros in certain ways, I would tend towards letting users do what they want and rely on their taste (and the negative feedback of their peers!) to guide them towards not writing macros that are nightmares to use.

I generally agree with giving users power, and we are already giving a huge amount of power here - significantly more than existing codegen does.
I believe that drawing a line at arbitrary manipulation of the shape of the program is a very reasonable place to draw the line.
We could take the "give the users power" argument all the way until we became Javascript and you could overwrite the prototype of even the core platform APIs, we have to draw a line somewhere :).

Existing codegen (via package:build) is actually very restrictive. You can only create new parts or libraries, so there is no way to overwrite anything existing.
We don't generally hear complaints about that part in particular, people are much less happy with the other aspects like having to declare outputs as a mapping of input extension to output extension which is very limiting.

As a code-generator author, I very much dislike those restrictions.
They force generators to work around the language, causing very unnatural syntaxes.
Like Freezed which requires:
class Example with _$Example

That "with" shouldn't be necessary.
The alternative is to clone the library and expect users to import the clone instead of the original. But that is equally unnatural and breaks IDE/tooling workflows.

Like Freezed which requires:
class Example with _$Example

These types of things should no longer be needed though, that is definitely one of the primary pain points we are trying to make better by making this a real language feature.
You can see the data_class example, and its usage - it doesn't require any references to generated symbols or part files, etc.

I see. But I suppose this wouldn't support adding new parameters to existing constructors
A common request from Freezed users is to be able to define:
@freezed
class Union with _$Union {
  factory Union.person(String name, int age) = Person;
  factory Union.company(String name, DateTime creationDate) = Company;
}

into:
@freezed
class Union with _$Union {
  factory Union.person(int age) = Person;
  factory Union.company(DateTime creationDate) = Company;

  int get name;
}

which is supposed to inject the "name" parameter in all constructors.

I see. But I suppose this wouldn't support adding new parameters to existing constructors

Correct, we wouldn't be able to support this exactly as you have outlined it, but you could support it some other way, where you generate those entire constructors. It would likely be less verbose as well, maybe something like this:
@Freezed(delegatingConstructors: {
  'person': Person,
  'company': Company
})
class Union with _$Union {
  int get name;
}

Then you don't have to duplicate the customized parameters of those constructors either.

Correct, we wouldn't be able to support this exactly as you have outlined it, but you could support it some other way, where you generate those entire constructors. It would likely be less verbose as well, maybe something like this:
@Freezed(delegatingConstructors: {
  'person': Person,
  'company': Company,
})
class Union with _$Union {
  int get name;
}

This isn't possible, no. Because the generator generated Person and Company based on the constructor.
We could need to reinvent constructors through decorators like:
@Freezed({
  'person': Case(
    name: 'Person',
    properties: [
      Property<int>('name'),
     ...
    ],
  ),
})

which would be very unnatural

This isn't possible, no. Because the generator generates Person and Company based on the constructor.

Oh, so the Person and Company classes themselves are also generated in this case?

Yes.
In many way what Freezed does is similar to what the data-class example does, with added support for union-types. But rather than defining the properties and generating the constructor, it uses the opposite mechanism: Define the constructor and it generate the implementation classes.
So a user define:
@freezed
class State with _$State {
  const factory State.loading({
    /// If non-null, the data before this state was refreshed
    String? lastData,
  }) = StateLoading;

  const factory State.data(String data) = StateData;
}

And this will generate:
class StateLoading implements State {
  const StateLoading({this.lastData});

  /// If non-null, the data before this state was refreshed
  final String? lastData;
}

class StateData implements State {
   const StateData(this.data);
  final String data;
}

and will also generate copyWith & co, followed by utilities to perform a switch-case on a union:
State state;

// equivalent `if state is StateLoading else if state is StateData`, but with all cases as "required"
state.when(
  loading: (String? lastData) {...},
  data: (String data) {...}
)

This syntax has the benefit of giving more control over the constructors. Folks can make parameters named required or positional optional if they want to.
Hence the desire for extracting shared parameters from all constructors, which required macros being able to override the constructor prototype.

@Hixie @goderbauer @rrousselGit I am curious what you (or others, feel free to chime in) think about a design like this for eliminating stateful widget boilerplate, that plays more to the strengths of the current system.
/// I think we could likely come up with a better way of defining the state fields,
/// I know this way is pretty ugly.
///
/// Maybe something like: @statefulWidget(fields: [int count])
@statefulWidget(stateFields: {'count': int});
Widget _example(BuildContext context, ExampleState state, String title) {
  return Scaffold(
    body: Text('$title ${state.count}'),
    floatingButton: FloatingButton(
      onPressed: () => state.setState(() => state.count++;);
    ),
  );
}

// Becomes
class Example extends StatefulWidget {
  final String title;
  Example(this.title) : super();

  createState() => _ExampleState();
}

class _ExampleState extends State<Example> {
  int _count = 0;

  Widget build(context) {
    return _example(context, this, widget.title);
  }
}

The main problem I see with this approach is that you are creating a method _example but have to use it as Example() with fewer parameters. Which is what this issue is about. Using the state as a parameter though is a good idea, though I would suggest a better way of doing it would be to annotate the state class instead.
@statefulWidget((BuildContext context, ExampleState state, String title){
  return Scaffold(
    body: Text('$title ${state.count}'),
    floatingButton: FloatingButton(
      onPressed: () => state.increment())
    ),
  );
});
class ExampleState extends State<Example> {
  int count = 0;
  void increment() => count++;
}

which would generate:
class Example extends StatefulWidget {
  final String title;
  Example(this.title) : super();

  createState() => ExampleState();
}

class ExampleState extends State<Example> {
  int _count = 0;
  void increment() {
     void increment_wrapped() => count++;
     setState((){
       increment_wrapped();
     });
  }
  Widget build(context) {
     final state = this;
     final title = widget.title;
     return Scaffold(
      body: Text('$title ${state.count}'),
      floatingButton: FloatingButton(
        onPressed: () => state.increment())
      ),
    );
  }
}

Most of which can be done with the current prototype except copying and pasting the build function from the annotation to the generated code.

@statefulWidget(stateFields: {'count': int});

I don't think that this is a reasonable approach.  This denatures too much the syntax and doesn't solve numerous of the problems mentioned in https://github.com/flutter/flutter/issues/51752.
In general my experience working on code-generator is that we should avoid as much as possible from using strings and Type, and instead prefer a syntax that relies on either function parameters of class properties.
For example Freezed could work with:
@Freezed({
  'count': int,
}
class Example {...}

But instead does:
@freezed
class Example {
  factory Example(int count) = _Example;
}

While this is technically more verbose when counting the characters count, the second syntax is a lot more natural.
On top of that, it allows things like documentation or annotations, where an alternate example would be:
@freezed
class Example {
  factory Example(
     /// Documentation for the [count] property. This comment is extracted by the generator
     /// and copy-pasted into the _Example.count property
    @Deprecated('We can use annotations as usual too')
    int count,
  ) = _Example;
}

Similarly I don't think that the macro proposal solves the issue with StatefulWidgets.
The title of flutter/flutter#51752 is unfortunate. The issue isn't about how many characters it takes to type a StatefulWidget, but rather about how there is no way to share logic between StatefulWidgets.
flutter/flutter#51752 is about state logic composition, which flutter_hooks solves by allowing users to define something similar to mixins.
Something like @statefulWidget(stateFields: {'count': int}); would not solve this problem. It would focus on reducing the number of lines that a StatetfulWidget takes, but not make stateful logic any more reusable.

What I am trying to do is provide counter proposals of how might accomplish similar goals, without changing any existing API. My fundamental viewpoint is that macros should be purely additive - that is they should only be able to add things to the program. It is imo a very bad thing if I can look at a piece of code, but I can't actually use that code as written.
The question I want to answer is, can we solve the same problems that these other approaches are setting out to solve, while maintaining that fundamental approach? So that is what I was exploring with this idea :).

The main problem I see with this approach is that you are creating a method _example but have to use it as Example() with fewer parameters. Which is what this issue is about (changing shape of API).

That is why I made the method private - it is really just an implementation detail of the generated classes. Users don't interact with this method and can't see it.

Using the state as a parameter though is a good idea, though I would suggest a better way of doing it would be to annotate the state class instead.

I really like the idea of using the state class here, that avoids the issues around how to define fields.
Possibly we could even go a bit further, and instead of having the function be passed to the annotation, lets say the macro instead annotates a method on the class directly. So something like this (I left off the setsState part from your example just because I think its a different feature):
class ExampleState extends State<Example> {
  int count = 0;
  void increment() => setState(() => count++);

  @statefulWidget
  Widget _build(BuildContext context, String title) {
    return Scaffold(
      body: Text('$title ${count}'),
      floatingButton: FloatingButton(
        onPressed: () => increment())
      ),
    );
  }
}

That to me, actually starts to become something pretty reasonable.

The other issue is replacing the field with a getter/setter pair.

Yes, this part in particular is a piece of contention for sure. Today what you would do is just require that the field is private, and then the macro generates the public getter/setter pair. You can't actually implement a concrete field with a getter/setter pair unfortunately, is the problem. For instance how would you initialize it in a constructor, etc. I think the private field model is a lot simpler, and just sidesteps all the problems, although it may be a bit less convenient.

What I am trying to do is provide counter proposals of how might accomplish similar goals, without changing any existing API.

Which goal are you referring to?

I am asking this because it is likely that there is a misunderstanding on the goals.
My understanding is that we are trying to cover use-cases from my packages, which are functional_widget, flutter_hooks and freezed, which are related to multiple macro proposals and this + other issues.
But I don't see the relationship with these packages and the @statefulWidget annotation.
If this is about hooks / flutter/flutter#51752, reducing the number of lines that it takes to write a StatefulWidget is a non-goal.
The primary goals are state composition and improving readability by reducing the indentation.

In general my experience working on code-generator is that we should avoid as much as possible from using annotations, strings and Type as much as possible, and instead prefer a syntax that relies on either function parameters of class properties.

Yes I definitely agree on this point. I think moving things to the state class is a pretty reasonable solution here.

The title of flutter/flutter#51752 is unfortunate. The issue isn't about how many characters it takes to type a StatefulWidget, but rather about how there is no way to share logic between StatefulWidgets.

There are example macros in this repository which seem to me to solve the same fundamental types of issue though? You can write a macro, which looks at a field and then injects some code into all the necessary lifecycle methods to manage the lifecycle of that field, for instance.
If that doesn't solve the same fundamental problem that flutter_hooks solves, then it would be helpful to understand why.
See for example the autoDispose and RenderAccessors examples in this repo.

Which goal are you referring to?

This particular case was looking at simplifying stateful widgets (ie: functional_widget).
Note that I am not a flutter developer, and I am not actually familiar with your packages. So I need concrete feedback/explanations as to what you are trying to solve, and why you think that this proposal doesn't help.
But also remember that my goal here is not to allow you to replicate exactly any existing packages. It is to enable new packages that solve the same problems, in a way that is directly integrated into the compiler. This requires a fresh look at the problems those packages are trying to solve, to see how (or if) we can solve them in this system. We can then compare the different solutions from a number of different perspectives.

As @TimWhiting already stated, I don't really like the disconnect between call site and implementation that this is creating. I.e. you instantiate Example(), but there's no trace in the code where that's coming from. If I search for class Example in my code base e.g. on Github, nothing comes up. You need the implicit knowledge that @statefulWidget will generate that class out of the _example method or ExampleState class. I wonder how much harder this makes to read and understand the code.


Is there any support or examples of operations on 3D mesh?

❓ Questions & Help

Is there any support or examples of operations on 3D meshes? It seems PyG has very few tutorials.

While we do not have many tutorials, we have examples of:

FAUST Shape Correspondence
PointNet++ and DGCNN ModelNet classification
PointNet++ and DGCNN ShapeNet Part Segmentation

While we do not have many tutorials, we have examples of:

FAUST Shape Correspondence
PointNet++ and DGCNN ModelNet classification
PointNet++ and DGCNN ShapeNet Part Segmentation

Thank you!


S3 ListParts API does not respect MaxParts

Hello,
I think there may be an issue with the MaxParts argument of s3.list_parts(). This pseudo-code:
s3.list_parts(
    Bucket=bucket,
    Key=key,
    UploadId=multiPartUploadId,
    PartNumberMarker=0,
    MaxParts=2,
)

Should result in only 2 parts.
For the next snippets, I uploaded 4 parts of a file and tried to get uploaded parts by batch of 2.
Enabling DEBUG logging shows:
endpoint       D Sending http request: <AWSPreparedRequest stream_output=False, method=GET, url=URL?uploadId=UID&part-number-marker=0&max-parts=2, headers={...}>

But the answer is not what I was waiting. In fact, the MaxParts had no effect:
<?xml version="1.0" encoding="UTF-8"?>
<ListPartsResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
    <PartNumberMarker>1</PartNumberMarker>
    <NextPartNumberMarker>4</NextPartNumberMarker>
    <MaxParts>4</MaxParts>
    <IsTruncated>false</IsTruncated>
<ListPartsResult>

The same code in a real environment works as expected.

After having read the source code, it seems this is not implemented, all parts are always returned. I will provide a PR soon if you are OK.


Issue while installing with Pods

Hi, Just now i've installed your photo-editor using cocoa pods, i'm getting errors.. Can you please help me to solve the issues.  I'm using xcode 9.3 version

same problem

same problem for me too

What's the exact steps you guys are using, b/c it's working for me when i add:
  pod 'iOSPhotoEditor'

to my Podfile and run pod install
I'm on Xcode 9.4.1

Same issue, Xcode 9.4.1 with a Swift 4.1 project

I have submitted a pull request that fixes these issues. Until that is merged a quick fix is to go to the selector function and add @objc at the beginning of the function.  (I.e. @objc func cancel() )

Please update to the latest release 0.6 and update me :D  @kishore4a2

Has anyone had success installing and using this pod without use_frameworks!? My depedencies don't allow me to enable frameworks but so far I've had trouble getting this pod to build successfully without frameworks.


Wrong response

After updating i see this in response - '<?php{...}', so every response starts with <?php
return $this->response()->array(['success' => true]);
<?php{"content": "text"}

I'm not seeing this.
Check your files, might be something amiss somewhere else.


port lint: warn for "platforms darwin" as this is the default

Seems like a good idea. Would like more opinions on the implementation. @jmroot and @ryandesign ?

How close is this to done now? Can we commit it?

@pmetzger re-reading the code I noticed an unnecessary global declaration that I left in the code . Otherwise I did take @jmroot comments into account and I believe it's ready.