[iOS] Apple Pencil cannot slide and scribble normally after the system's Scribble is turned on

#101016 is now appearing in 3.7.0
[✓] Flutter (Channel stable, 3.7.0, on macOS 13.1 22C65 darwin-arm64, locale en-US)
    • Flutter version 3.7.0 on channel stable at /Users/david/prog/flutter
    • Upstream repository git@github.com:flutter/flutter.git
    • Framework revision b06b8b2710 (2 days ago), 2023-01-23 16:55:55 -0800
    • Engine revision b24591ed32
    • Dart version 2.19.0
    • DevTools version 2.20.1

[✓] Xcode - develop for iOS and macOS (Xcode 14.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14B47b
    • CocoaPods version 1.11.3

I think in 3.7.0 (and master) a Scribble refactor is not applied in both engine and framework. So since the methods don't match, Scribble does not work.
Framework:
https://github.com/flutter/flutter/blob/b06b8b2710955028a6b562f5aa6fe62941d6febf/packages/flutter/lib/src/services/text_input.dart#L2322
Engine:
https://github.com/flutter/engine/blob/b24591ed328a2d4ce6505819e2f5898a78132f7f/shell/platform/darwin/ios/framework/Source/FlutterTextInputPlugin.mm#L51
Current effort is here? https://github.com/flutter/flutter/pull/115296

Is there any workaround for this? @moffatman
Could this be related? #114698
Thanks!

It was then reverted for a second time here: https://github.com/flutter/flutter/pull/115146
Maybe the best way to fix is to first change the names back, then land the rest of the changes? That would be easiest to cherry-pick. @justinmc

I manually merged https://github.com/flutter/flutter/pull/115296 into stable and that solved the issue. This works for now but it'd be nice if this change can be included in a 3.7.x patch.
Thanks! @moffatman

Reproducible using the code sample from #101016 pasted below.

recording
https://user-images.githubusercontent.com/88313112/214818899-5ea53c68-4e58-4114-b34e-1aba914fcc23.MP4

code sample
import 'package:flutter/material.dart';

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

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: const MyHomePage(),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({
    Key? key,
  }) : super(key: key);

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

class _MyHomePageState extends State<MyHomePage> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: ListView.builder(
        itemBuilder: (context, index) {
          return ListTile(
            title: Text('Item $index'),
          );
        },
        itemCount: 100,
      ),
    );
  }
}

flutter doctor -v
[✓] Flutter (Channel stable, 3.7.0, on macOS 13.1 22C65 darwin-arm64, locale en-GB)
    • Flutter version 3.7.0 on channel stable at /Users/nexus/dev/sdks/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision b06b8b2710 (2 days ago), 2023-01-23 16:55:55 -0800
    • Engine revision b24591ed32
    • Dart version 2.19.0
    • DevTools version 2.20.1

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14C18
    • CocoaPods version 1.11.3

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

[!] Android Studio (version 2022.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
    ✗ Unable to find bundled Java version.
    • Try updating or re-installing Android Studio.

[!] Android Studio (version 2022.1)
    • Android Studio at /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/221.6008.13.2211.9477386/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
    ✗ Unable to find bundled Java version.
    • Try updating or re-installing Android Studio.

[✓] IntelliJ IDEA Community Edition (version 2022.2)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • 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

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

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 13.1 22C65 darwin-arm64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 109.0.5414.119

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 2 categories.

[!] Flutter (Channel master, 3.7.0-26.0.pre.14, on macOS 13.1 22C65 darwin-arm64, locale en-GB)
    • Flutter version 3.7.0-26.0.pre.14 on channel master at /Users/nexus/dev/sdks/flutters
    ! Warning: `flutter` on your path resolves to /Users/nexus/dev/sdks/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/nexus/dev/sdks/flutters. Consider adding /Users/nexus/dev/sdks/flutters/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/nexus/dev/sdks/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/nexus/dev/sdks/flutters. Consider adding /Users/nexus/dev/sdks/flutters/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 351466aea6 (29 hours ago), 2023-01-24 21:46:24 -0800
    • Engine revision bffb983524
    • Dart version 3.0.0 (build 3.0.0-157.0.dev)
    • DevTools version 2.20.1
    • 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 33.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14C18
    • CocoaPods version 1.11.3

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

[!] Android Studio (version 2022.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
    ✗ Unable to find bundled Java version.
    • Try updating or re-installing Android Studio.

[!] Android Studio (version 2022.1)
    • Android Studio at /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/221.6008.13.2211.9477386/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
    ✗ Unable to find bundled Java version.
    • Try updating or re-installing Android Studio.

[✓] IntelliJ IDEA Community Edition (version 2022.2)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • 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

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

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 13.1 22C65 darwin-arm64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 109.0.5414.119

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 3 categories.

Hotfix request at https://github.com/flutter/flutter/issues/120478


Add shell script style analysis for generated files

Probably for https://github.com/koalaman/shellcheck
It should test script code style in CI for generated files

resolved in #78


keras error

The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "MolEvol/main.py", line 168, in
main(args)
File "MolEvol/main.py", line 112, in main
if args.last_round != 0:
File "MolEvol/main.py", line 82, in search_rationales
gsls_tuples = do_local_search_disc(seed_molecules, args)
File "/Users/Workspace/repos/MolEvol-ffbb4fab5fe38cfa5049c664df61d50934fa9ed3/MolEvol/local_search/local_searcher_explain.py", line 136, in do_local_search_disc
results = pool.map(work_func, mol_id_list)
File "/Users/opt/anaconda3/envs/chemprop/lib/python3.8/multiprocessing/pool.py", line 364, in map
return self._map_async(func, iterable, mapstar, chunksize).get()
File "/Users/opt/anaconda3/envs/chemprop/lib/python3.8/multiprocessing/pool.py", line 771, in get
raise self._value
AttributeError: module 'keras.utils.generic_utils' has no attribute 'populate_dict_with_module_objects'
env:
mac os
python=3.8
what is your tensorflow, keras version?

Thanks for noting this! It's Keras 2.4.3.

I got the same error. @binghong-ml Would you let me know your tensorflow version? FYI, I tried tensorflow version 2.5.0.

i solved the problem by this op: https://github.com/keras-team/keras/issues/14632

Could you try Tensorflow-cpu 2.3?

Thanks @nickyoungforu , it solves the problem!

Could you try Tensorflow-cpu 2.3?

It gives another error as follows:
  File "MolEvol/main.py", line 166, in <module>
    main(args)
  File "MolEvol/main.py", line 120, in main
    rationales, P = search_rationales(mol_corpus)
  File "MolEvol/main.py", line 82, in search_rationales
    gsls_tuples = do_local_search_disc(seed_molecules, args)
  File "/home/leona/github.sec.samsung.net/MolEvol/MolEvol/local_search/local_searcher_explain.py", line 150, in do_local_search_disc
    for orig_smiles, rationales in results:
  File "/home/leona/github.sec.samsung.net/MolEvol/MolEvol/local_search/local_searcher_explain.py", line 98, in local_for_one_molecule
    from MolEvol.explainer.explain import L2X_explain
  File "/home/leona/github.sec.samsung.net/MolEvol/MolEvol/explainer/explain.py", line 7, in <module>
    from keras_gcn import GraphConv
  File "/home/leona/anaconda3/envs/chemprop/lib/python3.8/site-packages/keras_gcn/__init__.py", line 1, in <module>
    from .layers import GraphConv, GraphMaxPool, GraphAveragePool
  File "/home/leona/anaconda3/envs/chemprop/lib/python3.8/site-packages/keras_gcn/layers.py", line 1, in <module>
    from .backend import keras
  File "/home/leona/anaconda3/envs/chemprop/lib/python3.8/site-packages/keras_gcn/backend.py", line 16, in <module>
    import keras
  File "/home/leona/anaconda3/envs/chemprop/lib/python3.8/site-packages/keras/__init__.py", line 20, in <module>
    from . import initializers
  File "/home/leona/anaconda3/envs/chemprop/lib/python3.8/site-packages/keras/initializers/__init__.py", line 124, in <module>
    populate_deserializable_objects()
  File "/home/leona/anaconda3/envs/chemprop/lib/python3.8/site-packages/keras/initializers/__init__.py", line 49, in populate_deserializable_objects
    LOCAL.GENERATED_WITH_V2 = tf.__internal__.tf2.enabled()
AttributeError: module 'tensorflow.compat.v2' has no attribute '__internal__'


Square brackets in API

Hello,
I am using NPClassifier to organize the natural products library of our laboratory. I access to the chemical classes by url API https://npclassifier.gnps2.org/classify?smiles=
However I have a problem with accessing for molecules where there are square brackets in the SMILES. For exemple https://npclassifier.gnps2.org/classify?smiles=COc1ccc2c(c1O)-c1c(O)c(OC)cc3c1C(C2)N+(C)CC3
I tried to replace square brackets by %5B and %5D, but it doesn't work.
Can you help please?
Thank you

Hi @elnurgar
You would need to fully encode the SMILES string.
For this you can use the urllib.parse Python library
import requests
from urllib.parse import quote

# Function to get NPC classification
def get_npc_classification(smiles):
    # Encode the SMILES string
    encoded_smiles = quote(smiles)

    print(f"Fetching data for encode SMILES: {encoded_smiles}")

    url = f"https://npclassifier.gnps2.org/classify?smiles={encoded_smiles}"

    response = requests.get(url)

    if response.status_code == 200:
        return response.json()
    else:
        print(f"Error fetching data for SMILES: {smiles} - Status Code: {response.status_code}")
        return None

Which in your case should return an encoded_smiles string COc1ccc2c%28c1O%29-c1c%28O%29c%28OC%29cc3c1C%28C2%29%5BN%2B%5D%28C%29%28C%29CC3
This now works https://npclassifier.gnps2.org/classify?smiles=COc1ccc2c(c1O)-c1c(O)c(OC)cc3c1C(C2)[N%2B](C)(C)CC3

Hi Pierre-Marie,
Thank you for your reply. I will try it with our database.


FD from EVT theory using Block Maxima approach

Added the Block Maxima approach to compute dimensions using estimates of the parameters of a GEV distribution

(please title your pull requests accordingly, and add more extensive descriptions in the Pull Request message)

Codecov Report

Merging #28 (864f4e6) into main (b752dd0) will decrease coverage by 3.92%.
The diff coverage is 0.00%.

:exclamation: Current head 864f4e6 differs from pull request most recent head 182d717. Consider uploading reports for the commit 182d717 to get more accurate results

@@            Coverage Diff             @@
##             main      #28      +/-   ##
==========================================
- Coverage   92.17%   88.26%   -3.92%
==========================================
  Files          17       18       +1
  Lines         677      707      +30
==========================================
  Hits          624      624
- Misses         53       83      +30

Files Changed
Coverage Δ

src/extremes_based/extremesdim.jl
65.85% <0.00%> (-18.53%)
:arrow_down:

src/extremes_based/gev.jl
0.00% <0.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Workspace settings take no precedence over User settings for format on save

Issue Type: Bug
Hi :-)
I am a happy user of the trim whitespace / format on save abilities of VSCode.
However, now I have a single workspace where I need to suppress this behaviour, so I made a workspace specific settings file (with the help of the settings GUI).
However it seems that vscode is ignoring these specific project settings, the format on save will execute until I disable it in the User settings. As far as I can tell other workspace-settings are respected (e.g. bracket pair highlighting).
This issue seems to have been reported before (#109020), but it was abandoned by the reporter, therefore I am filing this issue again.
Cheers
VS Code version: Code 1.63.0 (7db1a2b88f7557e0a43fec75b6ba7e50b3e9f77e, 2021-12-07T05:16:45.441Z)
OS version: Linux x64 5.10.79-1-MANJARO snap
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz (8 x 3109)

GPU Status
2d_canvas: unavailable_softwaregpu_compositing: disabled_softwaremultiple_raster_threads: enabled_onoop_rasterization: disabled_offopengl: disabled_offrasterization: disabled_softwareskia_renderer: enabled_onvideo_decode: disabled_softwarevulkan: disabled_offwebgl: unavailable_softwarewebgl2: unavailable_software

Load (avg)
1, 1, 1

Memory (System)
15.51GB (0.64GB free)

Process Argv
--no-sandbox . --crash-reporter-id de916c7d-7964-46b3-8ad4-39c2ee328ae4

Screen Reader
no

VM
0%

DESKTOP_SESSION
plasma

XDG_CURRENT_DESKTOP
KDE

XDG_SESSION_DESKTOP
KDE

XDG_SESSION_TYPE
x11

Extensions (39)

Extension
Author (truncated)
Version

language-x86-64-assembly
13x
3.0.0

better-toml
bun
0.3.2

path-intellisense
chr
2.6.0

vscode-markdownlint
Dav
0.45.0

gitlens
eam
11.7.0

matlab
Gim
2.2.1

vscode-pull-request-github
Git
0.34.0

mdmath
goe
2.7.4

gc-excelviewer
Gra
4.0.45

path-autocomplete
ion
1.17.1

vscode-edit-csv
jan
0.6.4

language-julia
jul
1.5.6

linter-gfortran
krv
2.6.2

restructuredtext
lex
167.0.0

rainbow-csv
mec
1.10.1

git-graph
mhu
1.30.0

eps-preview
mkv
0.3.0

vscode-docker
ms-
1.18.0

python
ms-
2021.12.1559732655

vscode-pylance
ms-
2021.12.1

jupyter
ms-
2021.11.1001550889

jupyter-keymap
ms-
1.0.0

jupyter-renderers
ms-
1.0.4

remote-containers
ms-
0.209.5

remote-ssh
ms-
0.68.0

remote-ssh-edit
ms-
0.68.0

remote-wsl
ms-
0.63.5

vscode-remote-extensionpack
ms-
0.21.0

cpptools
ms-
1.7.1

autodocstring
njp
0.5.4

pyside2-vsc
Oll
0.1.0

vscode-spotify
shy
3.2.1

vba
spe
1.7.1

latex-support
tor
3.10.0

simple-rst
tro
1.5.1

vscode-ltex
val
13.1.0

vscode-icons
vsc
11.8.0

markdown-all-in-one
yzh
3.4.0

material-theme
zhu
3.13.6

(4 theme extensions excluded)

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythontb:30283811
pythonvspyt551cf:30345471
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
pythondataviewer:30285071
vscod805:30301674
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
pythonrunftest32:30373476
pythonf5test824:30373475
javagetstartedt:30391933
pythonvspyt187:30373474
vsaa593:30376534
pythonvs932:30410667
vscop804:30404766
vs360:30404995
vsrem710cf:30405999
vscexrecpromp3c:30407761

Nevermind, the problem was to do with my config, tried for hours and then literally stumbled over it the minute after I filed this issue, sorry for the misreport.


Bring back Native support?

Hi! With the recent activity around Scala Native in the Typelevel ecosystem, I was wondering if you'd consider adding back Scala Native. What do you think?

Hi Jakub, I am not hostile to bringing back Scala Native but I would like for someone to be responsible of its maintenance.

@julien-truffaut I'm happy to take responsibility for maintenance, if you are open to adopting sbt-typelevel for your build. It significantly reduces the maintenance effort for OSS and cross-building.

@julien-truffaut it's currently used by more than 200 projects, including all active Typelevel and Http4s projects.
Here's a rough list:
https://github.com/typelevel/download-java/network/dependents

Awesome, so I am all for using it!


pypi package

So for some unknown reason, Travis runs out of memory with 8GB of RAM while github runs fine with 7GB of RAM when running pytest. Testing on Rosenberg suggests that we don't use near 8GB so I don't see why travis fails. Therefore this PR does the following :

revert to GH actions for CI
add a GH actions script for creating pypi package and uploading to pypi.org
The package is built and uploaded when a release is created
add GH README to pypi package

Available at : https://pypi.org/project/ivadomed/
via
pip install ivadomed

Currently the version on PyPi is not the same as this PR (I get version 0.1 with the dependency to pytorch 1.2.0). Can you publish the new version of the package on PyPi or do we need to pass this PR first? Also, on github actions I see 2 actions related to publishing the package: Python Package and Publish Package. What is Python Package?

Currently the version on PyPi is not the same as this PR (I get version 0.1 with the dependency to pytorch 1.2.0). Can you publish the new version of the package on PyPi or do we need to pass this PR first?

I've reuploaded it to be up to date with this PR, after merging the package will be published automatically every time we create a release, but for now it's manual. I think we should do a 1.0 release once this is merged.

Also, on github actions I see 2 actions related to publishing the package:  and Publish Package. What is Python Package?

It was originally named Python Package, I've renamed it to Publish Package but I don't see a way to delete the old one :(
https://github.community/t5/GitHub-Actions/Delete-old-workflow-results/td-p/30589

It was originally named Python Package, I've renamed it to Publish Package but I don't see a way to delete the old one :(

maybe @kousu knows?


Adds several js annotation and remove the unnecessary FontsInfo class.

Added FontsInfo class and PTAL.

Please take another look.


Disabling and re-enabling an element component resets its material

Issue:
We wanted to animate a texture in an element component, similar to the Tutorial Animated Texture. In case the same material should be animated on multiple instances of element components, we cloned the material and set the material property of the elementComponent in code. But after disabling the entity and re-enabling it, the texture was not animated anymore.
What we found so far:
It seems like the element component is binding the material again once it's enabled. But instead of using the current material, it is using the material from the linked asset. It is even comparing the asset.resource to this._material and deliberately choosing the asset's material over the current one. ImageElement.onEnable
This does not look like the preferred behaviour, as this would get rid of any custom material set in code. Our current workaround is to set the asset reference to null.
Steps to reproduce:

create a new material in code, either from scratch or by cloning
replace the material property of an imageElement, which already has a reference to another material asset
disable the imageElement, then enable the imageElement
you should now see the original material
example project

This issue does not seem to be the case for model components. Disabling and re-enabling does not reset the material of the model. Also for the sake of completness sake, this is the forum link where we reported this issue first.

linked forum posts: https://forum.playcanvas.com/t/material-is-not-updated-anymore-after-re-enabling-it/20363


ConfigurationPropertiesRebinder not compatible with @ConstructorBinding when constructed in bootstrap

Using Hoxton.SR8
If you define an @ConfigurationProperties class that uses @ConstructorBinding, attempts to rebind it using ConfigurationPropertiesRebinder will fail with an exception from ConfigurationPropertiesBindingPostProcessor: ""Cannot bind @ConfigurationProperties for bean XXXX Ensure that @ConstructorBinding has not been applied to regular bean"
This is especially problematic because Spring Cloud Context rebinds all ConfigurationProperties classes that have been used in the bootstrap context in order to ensure that property changes during the bootstrap phase are picked up. Looking at the code, it's not clear to me that there's a simple fix for this: the rebinder fundamentally assumes that the properties bean is mutable. In order to support immutable properties classes I guess it would need some sort of proxy in the middle to allow the properties bean to be re-constructed without having to reinject it into every dependent bean.

We are not going to support rebinding @ConstructorBinding properties.

I'm unable to reproduce the error log. When I do it, it value doesn't update and no exception is logged. Can you provide a complete, minimal, verifiable sample that reproduces the problem?  It should be available as a GitHub (or similar) project or attached to this issue as a zip file.

https://github.com/symposion/spring-test (The master branch)
I've created an immutable @ConfigurationProperties class that I have no intention of mutating, I'm not explicitly refreshsing /rebinding anything, and the app fails to startup because internally Spring cloud is rebinding all the properties from the bootstrap context. I understand why that's done, but at the very least this is surprising and worth calling out in the docs as a potential "gotcha". A nicer alternative might be to just ignore properties beans that are constructor-bound when rebinding with a warning in the logs rather than a hard fail; or make the post-bootstrap rebinding optional somehow?

This only applies to constructor binding beans that are created in a bootstrap configuration. Considering this is relatively uncommon and I"m not sure how to distinguish if it was created in bootstrap or not, I'm going to mark this as waiting for votes.

FWIW, I just ran into this problem

Pretty sure I encountered this as well. I'm trying to create something like spring-cloud-aws-parameter-store-config that use the v2 AWS SDK and has different rules for the parameter store path. My class is simply:
@ConstructorBinding
@ConfigurationProperties(AwsParamStoreProperties.CONFIG_PREFIX)
data class AwsParamStoreProperties(
    val region: String? = null,
    val endpoint: URI? = null,
    val name: String? = null,
    val enabled: Boolean = true
) {
    companion object {
        const val CONFIG_PREFIX = "aws.paramstore"
    }
}

It loads the parameters from SSM, but when the application context tries to import the ConfigData from the bootstrap context, it throws the same exception. It does work when defined like this:
@ConfigurationProperties(AwsParamStoreProperties.CONFIG_PREFIX)
class AwsParamStoreProperties {
    var region: String? = null
    var endpoint: URI? = null
    var name: String? = null
    var enabled: Boolean = true

    companion object {
        const val CONFIG_PREFIX = "aws.paramstore"
    }
}

But then we lose immutability.

Are there any other workarounds?


Run rpk command to create ballast file

What would you like to be added?
This issue is to track the need to verify ballast file creation works as expected. The docs say two things must happen:

proper config in values.yaml
run rpk redpanda tune ballast_file

See docs here: https://docs.redpanda.com/docs/manage/cluster-maintenance/disk-utilization/#create-a-ballast-file
In the chart I see step 1 but not step 2.
Why is this needed?
This will allow configuring a ballast file properly.
JIRA Link: K8S-33

I was able to get the ballast file to create BUT it is because I ran the tune process in the container where redpanda is running. To be clear, we need to distinguish and most probably run these commands in the right context. Those that require elevated privs should probably run in a daemonset, which imho we should create for customers as an option, and second we should run those that do not require elevelated privs (those that modify redpanda configs directly) should probably run in the postStart hook. @vuldin let me know what do you think of this approach?

Duplicate of https://github.com/redpanda-data/helm-charts/issues/233


UI: Fixes for repo topic editor

Properly hides the edit interface when saving a empty topic list
Align the Done button with the edit box

Before

After

Maybe we can add a real  a cancel button rather than only hiding the editor when Done is clicked and the content is empty

When content is empty, the user wants to clear out the list, just hiding without any action would be wrong. Now a always visible cancel button might be useful, but I'm not sure its really needed, re-saving works just fine.


changes in javascript logic in index.html file issue no #942

which will render login and register page smoothly and if the button will not be hit it will keep navigating through same page and when login and register link is hit it will trigger the javascript logic

Please see the conflicts . Resolve the conflicts . Ensure you pull all the latest changes before pushing your feature/bug fixes to the main branch. After resolving the conflicts, please open a new PR for review.
Thank you!


MEMORY_LEAK in utils/cups-browsed.c

Dynamic memory, referenced by buf, is allocated at cups-browsed.c:728:

https://github.com/OpenPrinting/cups-filters/blob/8ac453d0c22a87984127f4c89bd5747d1409db23/utils/cups-browsed.c#L728
by calling function malloc and lost at cups-browsed.c:738.

Dynamic memory, referenced by ppdsizename, is allocated at cups-browsed.c:2074 :

https://github.com/OpenPrinting/cups-filters/blob/8ac453d0c22a87984127f4c89bd5747d1409db23/utils/cups-browsed.c#L2074
by calling function malloc and lost at cups-browsed.c:2081.

Dynamic memory, referenced by ppdsizename, is allocated at cups-browsed.c:2753:

https://github.com/OpenPrinting/cups-filters/blob/8ac453d0c22a87984127f4c89bd5747d1409db23/utils/cups-browsed.c#L2753
by calling function malloc and lost at cups-browsed.c:2758.
The free() operator should be used to free the allocated memory space before the function ends, otherwise there will be a MEMORY_LEAK.
Found by Linux Verification Center (portal.linuxtesting.ru) with SVACE.
Author E. Bykhanova.

Please run your scanner on the latest cups-filters version - 2.0.0, thank you!

In cups-browsed 2.x the listed leaks are fixed.

Fixed the memory leaks in the 1.x branch via commit e25fd59a.


chore: removed deprecated YellowBox

Summary
YellowBox was deprecated a year ago in a83ea6a

Changelog

[JavaScript] [Removed] - chore: removed deprecated YellowBox
Test Plan
CI is passing

Hi @ecreeth, do you mind resolving these conflicts and I'll import it for review?

@charlesbdudley the conflicts are fixed.


build-app.sh can't build cortex-m

When build-app.sh tries to compile cortex-m it ends with error:
+ mynewt_build_app=nrf52_my_sensor
+ rust_build_target=thumbv7em-none-eabihf
+ launch_config=launch-nrf52-pi.json
+ set +x

----- Building Rust app and Mynewt OS for thumbv7em-none-eabihf / nrf52_my_sensor...

----- Build Rust app
+ cargo build --target thumbv7em-none-eabihf
   Compiling cortex-m v0.6.2
error: the legacy LLVM-style asm! syntax is no longer supported
  --> /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/cortex-m-0.6.2/src/asm.rs:11:24
   |
11 |         () => unsafe { asm!("bkpt" :::: "volatile") },
   |                        ----^^^^^^^^^^^^^^^^^^^^^^^^
   |                        |
   |                        help: replace with: `llvm_asm!`
   |
   = note: consider migrating to the new asm! syntax specified in RFC 2873
   = note: alternatively, switch to llvm_asm! to keep your code working as it is

error: the legacy LLVM-style asm! syntax is no longer supported
  --> /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/cortex-m-0.6.2/src/asm.rs:39:13
   |
39 |               asm!("1:
   |               ^---
   |               |
   |  _____________help: replace with: `llvm_asm!`
   | |
40 | |                   nop
41 | |                   subs $0, $$1
42 | |                   bne.n 1b"
...  |
45 | |                  :
46 | |                  : "volatile");
   | |_______________________________^
   |
   = note: consider migrating to the new asm! syntax specified in RFC 2873
   = note: alternatively, switch to llvm_asm! to keep your code working as it is

error: the legacy LLVM-style asm! syntax is no longer supported
  --> /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/cortex-m-0.6.2/src/asm.rs:68:24
   |
68 |         () => unsafe { asm!("nop" :::: "volatile") },
   |                        ----^^^^^^^^^^^^^^^^^^^^^^^
   |                        |
   |                        help: replace with: `llvm_asm!`
   |
   = note: consider migrating to the new asm! syntax specified in RFC 2873
   = note: alternatively, switch to llvm_asm! to keep your code working as it is

error: the legacy LLVM-style asm! syntax is no longer supported
  --> /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/cortex-m-0.6.2/src/asm.rs:89:24
   |
89 |         () => unsafe { asm!("wfe" :::: "volatile") },
   |                        ----^^^^^^^^^^^^^^^^^^^^^^^
   |                        |
   |                        help: replace with: `llvm_asm!`
   |
   = note: consider migrating to the new asm! syntax specified in RFC 2873
   = note: alternatively, switch to llvm_asm! to keep your code working as it is

error: the legacy LLVM-style asm! syntax is no longer supported
   --> /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/cortex-m-0.6.2/src/asm.rs:110:24
    |
110 |         () => unsafe { asm!("wfi" :::: "volatile") },
    |                        ----^^^^^^^^^^^^^^^^^^^^^^^
    |                        |
    |                        help: replace with: `llvm_asm!`
    |
    = note: consider migrating to the new asm! syntax specified in RFC 2873
    = note: alternatively, switch to llvm_asm! to keep your code working as it is

error: the legacy LLVM-style asm! syntax is no longer supported
   --> /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/cortex-m-0.6.2/src/asm.rs:131:24
    |
131 |         () => unsafe { asm!("sev" :::: "volatile") },
    |                        ----^^^^^^^^^^^^^^^^^^^^^^^
    |                        |
    |                        help: replace with: `llvm_asm!`
    |
    = note: consider migrating to the new asm! syntax specified in RFC 2873
    = note: alternatively, switch to llvm_asm! to keep your code working as it is

error: the legacy LLVM-style asm! syntax is no longer supported
   --> /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/cortex-m-0.6.2/src/asm.rs:155:24
    |
155 |         () => unsafe { asm!("isb 0xF" ::: "memory" : "volatile") },
    |                        ----^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |                        |
    |                        help: replace with: `llvm_asm!`
    |
    = note: consider migrating to the new asm! syntax specified in RFC 2873
    = note: alternatively, switch to llvm_asm! to keep your code working as it is

error: the legacy LLVM-style asm! syntax is no longer supported
   --> /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/cortex-m-0.6.2/src/asm.rs:183:24
    |
183 |         () => unsafe { asm!("dsb 0xF" ::: "memory" : "volatile") },
    |                        ----^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |                        |
    |                        help: replace with: `llvm_asm!`
    |
    = note: consider migrating to the new asm! syntax specified in RFC 2873
    = note: alternatively, switch to llvm_asm! to keep your code working as it is

error: the legacy LLVM-style asm! syntax is no longer supported
   --> /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/cortex-m-0.6.2/src/asm.rs:209:24
    |
209 |         () => unsafe { asm!("dmb 0xF" ::: "memory" : "volatile") },
    |                        ----^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |                        |
    |                        help: replace with: `llvm_asm!`
    |
    = note: consider migrating to the new asm! syntax specified in RFC 2873
    = note: alternatively, switch to llvm_asm! to keep your code working as it is

error: the legacy LLVM-style asm! syntax is no longer supported
  --> /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/cortex-m-0.6.2/src/interrupt.rs:13:13
   |
13 |             asm!("cpsid i" ::: "memory" : "volatile");
   |             ----^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |             |
   |             help: replace with: `llvm_asm!`
   |
   = note: consider migrating to the new asm! syntax specified in RFC 2873
   = note: alternatively, switch to llvm_asm! to keep your code working as it is

error: the legacy LLVM-style asm! syntax is no longer supported
  --> /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/cortex-m-0.6.2/src/interrupt.rs:40:15
   |
40 |         () => asm!("cpsie i" ::: "memory" : "volatile"),
   |               ----^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |               |
   |               help: replace with: `llvm_asm!`
   |
   = note: consider migrating to the new asm! syntax specified in RFC 2873
   = note: alternatively, switch to llvm_asm! to keep your code working as it is

error: the legacy LLVM-style asm! syntax is no longer supported
  --> /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/cortex-m-0.6.2/src/register/basepri.rs:11:17
   |
11 |                 asm!("mrs $0, BASEPRI" : "=r"(r) ::: "volatile");
   |                 ----^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |                 |
   |                 help: replace with: `llvm_asm!`
   |
   = note: consider migrating to the new asm! syntax specified in RFC 2873
   = note: alternatively, switch to llvm_asm! to keep your code working as it is

error: the legacy LLVM-style asm! syntax is no longer supported
  --> /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/cortex-m-0.6.2/src/register/basepri.rs:40:19
   |
40 |             () => asm!("msr BASEPRI, $0" :: "r"(_basepri) : "memory" : "volatile"),
   |                   ----^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |                   |
   |                   help: replace with: `llvm_asm!`
   |
   = note: consider migrating to the new asm! syntax specified in RFC 2873
   = note: alternatively, switch to llvm_asm! to keep your code working as it is

error: the legacy LLVM-style asm! syntax is no longer supported
  --> /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/cortex-m-0.6.2/src/register/basepri_max.rs:17:23
   |
17 |                 () => asm!("msr BASEPRI_MAX, $0" :: "r"(_basepri) : "memory" : "volatile"),
   |                       ----^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |                       |
   |                       help: replace with: `llvm_asm!`
   |
   = note: consider migrating to the new asm! syntax specified in RFC 2873
   = note: alternatively, switch to llvm_asm! to keep your code working as it is

error: the legacy LLVM-style asm! syntax is no longer supported
   --> /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/cortex-m-0.6.2/src/register/control.rs:166:30
    |
166 |                     unsafe { asm!("mrs $0, CONTROL" : "=r"(r) ::: "volatile") }
    |                              ----^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |                              |
    |                              help: replace with: `llvm_asm!`
    |
    = note: consider migrating to the new asm! syntax specified in RFC 2873
    = note: alternatively, switch to llvm_asm! to keep your code working as it is

error: the legacy LLVM-style asm! syntax is no longer supported
   --> /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/cortex-m-0.6.2/src/register/control.rs:197:17
    |
197 |                 asm!("msr CONTROL, $0" :: "r"(control) : "memory" : "volatile");
    |                 ----^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |                 |
    |                 help: replace with: `llvm_asm!`
    |
    = note: consider migrating to the new asm! syntax specified in RFC 2873
    = note: alternatively, switch to llvm_asm! to keep your code working as it is

error: the legacy LLVM-style asm! syntax is no longer supported
  --> /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/cortex-m-0.6.2/src/register/faultmask.rs:37:30
   |
37 |                     unsafe { asm!("mrs $0, FAULTMASK" : "=r"(r) ::: "volatile") }
   |                              ----^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |                              |
   |                              help: replace with: `llvm_asm!`
   |
   = note: consider migrating to the new asm! syntax specified in RFC 2873
   = note: alternatively, switch to llvm_asm! to keep your code working as it is

error: the legacy LLVM-style asm! syntax is no longer supported
  --> /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/cortex-m-0.6.2/src/register/msp.rs:10:22
   |
10 |             unsafe { asm!("mrs $0,MSP" : "=r"(r) ::: "volatile") }
   |                      ----^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |                      |
   |                      help: replace with: `llvm_asm!`
   |
   = note: consider migrating to the new asm! syntax specified in RFC 2873
   = note: alternatively, switch to llvm_asm! to keep your code working as it is

error: the legacy LLVM-style asm! syntax is no longer supported
  --> /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/cortex-m-0.6.2/src/register/msp.rs:33:15
   |
33 |         () => asm!("msr MSP,$0" :: "r"(_bits) :: "volatile"),
   |               ----^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |               |
   |               help: replace with: `llvm_asm!`
   |
   = note: consider migrating to the new asm! syntax specified in RFC 2873
   = note: alternatively, switch to llvm_asm! to keep your code working as it is

error: the legacy LLVM-style asm! syntax is no longer supported
  --> /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/cortex-m-0.6.2/src/register/primask.rs:37:30
   |
37 |                     unsafe { asm!("mrs $0, PRIMASK" : "=r"(r) ::: "volatile") }
   |                              ----^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |                              |
   |                              help: replace with: `llvm_asm!`
   |
   = note: consider migrating to the new asm! syntax specified in RFC 2873
   = note: alternatively, switch to llvm_asm! to keep your code working as it is

error: the legacy LLVM-style asm! syntax is no longer supported
  --> /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/cortex-m-0.6.2/src/register/psp.rs:10:22
   |
10 |             unsafe { asm!("mrs $0,PSP" : "=r"(r) ::: "volatile") }
   |                      ----^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |                      |
   |                      help: replace with: `llvm_asm!`
   |
   = note: consider migrating to the new asm! syntax specified in RFC 2873
   = note: alternatively, switch to llvm_asm! to keep your code working as it is

error: the legacy LLVM-style asm! syntax is no longer supported
  --> /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/cortex-m-0.6.2/src/register/psp.rs:33:15
   |
33 |         () => asm!("msr PSP,$0" :: "r"(_bits) :: "volatile"),
   |               ----^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |               |
   |               help: replace with: `llvm_asm!`
   |
   = note: consider migrating to the new asm! syntax specified in RFC 2873
   = note: alternatively, switch to llvm_asm! to keep your code working as it is

error: the legacy LLVM-style asm! syntax is no longer supported
  --> /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/cortex-m-0.6.2/src/register/apsr.rs:58:17
   |
58 |                 asm!("mrs $0, APSR" : "=r"(r) ::: "volatile");
   |                 ----^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |                 |
   |                 help: replace with: `llvm_asm!`
   |
   = note: consider migrating to the new asm! syntax specified in RFC 2873
   = note: alternatively, switch to llvm_asm! to keep your code working as it is

error: the legacy LLVM-style asm! syntax is no longer supported
  --> /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/cortex-m-0.6.2/src/register/lr.rs:12:22
   |
12 |             unsafe { asm!("mov $0,R14" : "=r"(r) ::: "volatile") }
   |                      ----^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |                      |
   |                      help: replace with: `llvm_asm!`
   |
   = note: consider migrating to the new asm! syntax specified in RFC 2873
   = note: alternatively, switch to llvm_asm! to keep your code working as it is

error: the legacy LLVM-style asm! syntax is no longer supported
  --> /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/cortex-m-0.6.2/src/register/lr.rs:28:15
   |
28 |         () => asm!("mov R14,$0" :: "r"(_bits) :: "volatile"),
   |               ----^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |               |
   |               help: replace with: `llvm_asm!`
   |
   = note: consider migrating to the new asm! syntax specified in RFC 2873
   = note: alternatively, switch to llvm_asm! to keep your code working as it is

error: the legacy LLVM-style asm! syntax is no longer supported
  --> /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/cortex-m-0.6.2/src/register/pc.rs:12:22
   |
12 |             unsafe { asm!("mov $0,R15" : "=r"(r) ::: "volatile") }
   |                      ----^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |                      |
   |                      help: replace with: `llvm_asm!`
   |
   = note: consider migrating to the new asm! syntax specified in RFC 2873
   = note: alternatively, switch to llvm_asm! to keep your code working as it is

error: the legacy LLVM-style asm! syntax is no longer supported
  --> /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/cortex-m-0.6.2/src/register/pc.rs:28:15
   |
28 |         () => asm!("mov R15,$0" :: "r"(_bits) :: "volatile"),
   |               ----^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |               |
   |               help: replace with: `llvm_asm!`
   |
   = note: consider migrating to the new asm! syntax specified in RFC 2873
   = note: alternatively, switch to llvm_asm! to keep your code working as it is

error: aborting due to 27 previous errors

error: could not compile `cortex-m`.

To learn more, run the command again with --verbose.

Expected behavior: Script compiles cortex-m

Hi: Sorry about that, can you run these commands...
   # Latest nightly-2020-04-20 fails with asm error, so we use nightly-2020-02-16
   source $HOME/.cargo/env
   rustup default nightly-2020-02-16
   rustup update
   rustup target add thumbv7em-none-eabihf

Then run the Build App script?

Great, it works now!

Great thanks! I have updated my docs

I've started from the clean Raspberry Pi again. I did steps according to README.md: 1), 3), 2) (reverse order, because scripts/install-pi.sh have to be downloaded first to run it), 4), 5), 6). But the script build-app.sh failed again with the same issue #16. After running commands from step 1) (or comment above) script finished successfully. Is there something in the scripts what breaks the script environment?

install-pi will reset the Rust version to the latest version, which will break the build.
So rustup default nightly-2020-02-16 needs to be run after install-pi
Does that help?

I'm very sorry about the mess... Things are in transition right now...

We are preloading PineTime at the factory with FreeRTOS...
https://github.com/JF002/Pinetime
Together with the MCUBoot Bootloader that I have adapted. So I'm focusing my work on the FreeRTOS firmware with the MCUBoot Bootloader.

The new PineTimes will no longer have Flash ROM protection. So there will be no longer any need for me to maintain the Flash Unprotect scripts (yay!). The new PineTimes will support firmware update over Bluetooth.

I'm also not sure whether to keep maintaining Mynewt on PineTime. Since we are preloading FreeRTOS on PineTime and we have so few firmware developers, I'm considering moving over to FreeRTOS and dropping Mynewt.

Would you consider moving to FreeRTOS? I have simple instructions here for installing FreeRTOS...
https://gist.github.com/lupyuen/fb4cc04f03219d913cba8ec371f8c644
If you wish to stay on Mynewt, perhaps you can chat with me online so that you can get a quicker response. Here's the PineTime Chatroom on Discord / Matrix / Telegram / IRC. I'm usually online Singapore daytime (GMT+8 hours)...
https://wiki.pine64.org/index.php/PineTime#Community
Sorry again and thanks for using my code! :-)

Ok, it is well described cause of issue, thanks.
I've got PineTime with factory OS with protection (bought in February 2020).
I've decided to flash your Mynewt firmware, because you had written very promising article on medium.com about flashing firmware using Raspberry Pi. I think you have done very good work including the helpful documentation. It's pity you're leaving Mynewt. But if there will be good docs for flashing FreeRTOS using Raspberry Pi, I'll follow you.
Thanks!

Yep I'm hoping to help JF fill in the missing docs for FreeRTOS... If you could let me know what's missing, I'll work on them. Thanks!

Fixed


Document input focus and blur events

This documents the onFocus and onBlur events for Input components.  I'm not sure if you want to explicitly document these or just link to the React docs for events or other supported properties where spread attributes are used.  When I didn't see them in the docs, I initially assumed they weren't supported.

Thanks @tschaub - Does the spread attribute not take care of this?

@tschaub I've updated the docs for TextField to say that it extends the native input element and supports all of its props and events.


Feedback/beta release for TEP-0144: Param Enum

Feature looking for Promotion
Promote Param Enum feature to beta. Param.Enum allows resource authors to pre define a set of allowed values for a param and provides a built-in mechanism to perform param input value. This feature is guarded by dedicated feature flag enable-param-enum (setting it to true to experiment the feature).
Current Feature Version
alpha
Raise Feature Version
beta
Pipeline Release
v0.54
Issues Reported by the Users

https://github.com/tektoncd/pipeline/issues/7084
https://github.com/tektoncd/dashboard/issues/3193

Implementation PRs

https://github.com/tektoncd/pipeline/issues/7270

Could you please add enum feature with array values support? It currently supports string only. This is must if we switch from jenkins UI to tekton UI for deployment. All is good for Continuous Delivery but for Continuous Deployment we need this, please  help

Hi @martinmlouis 👋 , thanks for the feedback.
When designing the TEP, we left the enum support for array param to future work since the use cases was not clear to us (e.g. how do we validate an array against an allowlist, do we need the enum to be an array of arr? ).
If you have a clear use case of enum for array param, we can definitely extend the TEP to support it!
Is https://github.com/tektoncd/dashboard/issues/3193 your usecase? I was going through the discussion and it is still not clear how can an enum for array param type can help. But I'm happy to chat more about it.

I am not sure of how you will implement it, but if I get - single select AND - multi select or - checkboxes from dashboard implementation it would sufficient for us

cc @tektoncd/core-collaborators @tektoncd/core-maintainers

So one remark, missing piece is support of enum in objects, something like the following.
    params:
    - name: go
      description: >-
        Golang options, such as flags, …
      type: object
      properties:
        version:
          type: string
          enum: ["1.19", "1.20", "1.21", "1.22"]
        GOFLAGS: {type: string}
        GOOS: {type: string}
        GOARCH: {type: string}
        CGO_ENABLED: {type: string}
      default:
        version: "1.21"
        GOFLAGS: "-v"
        GOOS: ""
        GOARCH: ""
        CGO_ENABLED: "0"

I'll create an issue about it.

See https://github.com/tektoncd/pipeline/issues/7568

Hello tekton CI/CD,
Is it possible to speed up this feature request so that authors like me will get

array params as dropdown in Dashboard rather than string
array params can be a task/pipeline
gives ability to manual deploy a pipeline with drop downs list of array params rather than typing/copying text to run the pipeline or task
gives ability to have array params for task/pipeline as selectable so that we can have master pipeline =>many child selectable pipelines, so that we select what we need to deploy, these values selected from UI will have to be passed as params to any taskRun/pieplineRun. This will have a one-to-one mapping between the pipeline => to pipelineRun and task => to taskRun
This helps a lots in using tekton as not only for the current CI/CD but also manual deployments Automation so that this part of operation can be given to Build + Release operation staff as well
The goal is to replace jenkins with tekton
Can someone help? I do not have golang to show a PR so that the authors of tekton CI/CD can see it in action
Thanks


upi details of PM CARES account

add the upi details of PM CARES account provided by the government of India
this would help the government of India in the fight against corona

Duplicate of #416


chore: automate adding PRs to the project board

Background
Currently, newly added PRs are not assigned to the chain dev project. We need to update the mergify configuration so that each new PR is auto-assigned to https://github.com/orgs/osmosis-labs/projects/1/views/28
Acceptance Criteria

newly added PRs are auto-assigned to the chain dev project board

We should port the following to the SDK: https://github.com/osmosis-labs/osmosis/pull/1463


bug: AWS availability zone logic

AWS availability zone logic must be held at the Terraform Template level, same as all other Terraform Templates. Currently this is not fully completed.

Resolved


Remove haystack for postgres

This will fix #115
Fairly big PR and maybe needs to broken up but will leave that for review.
Main goal remove Haystack/Whoosh/Elastic Search and replace with Postgres Search.
I think I have done this without losing any site functionality.
I also removed some redundant templating stuff that was using haystack centric filters like "more_like_this" .
The use of Full text search is not sophisticated. That can come later.
Sqlite references have been removed.
I've reverted docker to use development settings as currently it does not function with production settings. Im not a massive fan of docker for local dev so not sure how to implement appropriately. Happy to be given some suggestions in this area.

Hi @chriswedgwood. This is quite exciting! Give me a week or so to play with it. (Ping me if I don't reply soon enough 😀)


2 identical files in downloads/ & protein IDs

There seem to be 2 identical files?
allNames.tsv | 2023-02-05 20:57 | 217K |
gene_IDs_names.tsv | 2023-02-05 20:57 | 217K |
Also, should we add  a protein ID column for completion? The protein ID is the gene name but with the first letter uppercase.

Hi Val.  When we added gene_IDs_names_products.tsv in 2018 I decided to rename allNames.tsv to gene_IDs_names.tsv so the file names in that directory would be more consistent.  But I left allNames.tsv as a symbolic link to gene_IDs_names.tsv in case anyone was relying on downloading allNames.tsv in a script.  That was probably overcautious.  Shall I remove allNames.tsv now?

Maybe it's OK it might be used (probably by EsyN etc).
What do you think? I guess there is no way of knowing who uses what....
Maybe add a note to the README that they are identical?

What do you think? I guess there is no way of knowing who uses what....
Maybe add a note to the README that they are identical?

I had a look in the web server logs which covered a few weeks.  There were no accessing for that file.  So I vote for removing it.

OK!

EsyN may use it once a month.... I will check...

These are the files EsyN uses (I had a record!)
interactions http://curation.pombase.org/dumps/releases/pombase-chado-latest/exports/pombase-go-physical-interactions.tsv.gz
Substrates
http://curation.pombase.org/dumps/releases/pombase-chado-latest/exports/pombase-go-substrates.tsv.gz";
Complexes
ftp://ftp.ebi.ac.uk/pub/databases/pombase/pombe/Complexes/Complex_annotation";
IDs
ftp://ftp.ebi.ac.uk/pub/databases/pombase/pombe/Mappings/allNames.tsv"
Slim http://curation.pombase.org/dumps/releases/pombase-chado-latest/pombe-embl/supporting_files/slimTab.txt

I can ask Dan to update?


dnd5e 2.4.x Compatibility

Ensure that these sheets are compatible with dnd5e 2.4.x.
#32 covers most of the updates.
Remaining PRs to review and potentially make changes against:

[x] https://github.com/foundryvtt/dnd5e/pull/2593
[ ] https://github.com/foundryvtt/dnd5e/pull/2573
[x] https://github.com/foundryvtt/dnd5e/pull/2532
[ ] https://github.com/foundryvtt/dnd5e/pull/2527
[x] https://github.com/foundryvtt/dnd5e/pull/2511

[x] https://github.com/foundryvtt/dnd5e/pull/2511/files#diff-710eafc98091eae4092900db40e9f7a8ffa924e49f830514f69baee278407e44

[x] https://github.com/foundryvtt/dnd5e/pull/2492

[x] https://github.com/foundryvtt/dnd5e/pull/2492/files#diff-e78cba0002ba8d71efd5b56bf9856efe16e25267d35f395c65ded11e59d6c586

[ ] https://github.com/foundryvtt/dnd5e/pull/2455
[ ] https://github.com/foundryvtt/dnd5e/pull/2400

[ ] item-activation template changes: https://github.com/foundryvtt/dnd5e/pull/2400/

[ ] https://github.com/foundryvtt/dnd5e/pull/2317

[ ] Look closer at https://github.com/foundryvtt/dnd5e/pull/2317/files#diff-710eafc98091eae4092900db40e9f7a8ffa924e49f830514f69baee278407e44

[ ] https://github.com/foundryvtt/dnd5e/pull/2156

[x] Review
[ ] Determine if it breaks spell -> spellbook drops
[ ] Either provide any missing data- attributes or just take over spellbook drop logic

Removed PRs that have been bumped to the dnd5e 2.5.0 milestone.


chore: clean-up Cargo.toml

Sort dependencies
Transform multi-line inline table into tables, as the spec requires
for readability [1]:

Inline tables are intended to appear on a single line. […] No
newlines are allowed between the curly braces unless they are valid
within a value. Even so, it is strongly discouraged to break an
inline table onto multiples lines. If you find yourself gripped
with this desire, it means you should be using standard tables.

[1] https://toml.io/en/v1.0.0#inline-table

coverage: 95.224%. remained the same
when pulling 114e3cbdaf59e4414138ff43c6628ed2e887fdfe on refresh-cargo-toml
into 2ca639bf2ecdf4208a12955aef6ff424cdc44ab7 on master.

coverage: 95.224%. remained the same
when pulling 1f0b3c33228261a5cd61f5adfe92436e67c13a60 on refresh-cargo-toml
into 2ca639bf2ecdf4208a12955aef6ff424cdc44ab7 on master.

coverage: 95.224%. remained the same
when pulling 6d945eb391b8364129cc5aafacc16f1742d422da on refresh-cargo-toml
into 2ca639bf2ecdf4208a12955aef6ff424cdc44ab7 on master.


[FEAT] Config option to disable discord -> mc chat relays

I keep forgetting this, so adding it here to remember.

Implemented in 3.2.0


docs: new accessibility page

This PR adds the new accessibility page under the style guide folder.
Resolve #1244

FYI, your branch has conflicts to resolve because we finally merged https://github.com/asyncapi/website/pull/1261.


Please put the translation part at the beginning of the article

I'm not good at English but I finished reading it and found the link to the translation at the end。 GOD

I agree with the @XNNNN that the translation part will be at first. Hence, I would like to improve the readme.

@XNNNN ME TOO!!!!!!

@XNNNN indeed, it would be helpful :)


Set updated_at column on model when using build_stubbed

I didn't see a previous issue regarding that and I'd like to open a discussion about this point.
When using build_stubbed to generate a model which "pretends" to be persisted on the database the column updated_at is nil. build_stubbed correctly sets the created_at column but not the updated_at. When you really persist an object on DB (in Rails) also the column updated_at is set so I'd expect it to have a value.

@coorasse that's an excellent point, and agreed that there should be consistency.
Want to open up a PR testing and implementing this behavior? If you need help getting started, please let me know!

I am using factory_girl(4.7.0) with mongoid(5.1.4). When using build_stubbed, both created_at and updated_at aren't populated and are nil.
2.3.0 :002 > r = FactoryGirl.build_stubbed :round
 => #<Round _id: 57ff92195f10de2aa59114b3, created_at: nil, updated_at: nil, name: "Y-find", from_date: 2016-10-12 21:27:49 UTC, end_date: 2016-11-11 23:47:46 UTC, status: "open">
2.3.0 :003 > r.persisted?
 => true
2.3.0 :004 > r.new_record?
 => false

👍


feat:[PIPE-22878]: Bulk reconciliation of templates

Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description

Please describe your changes: __________________________________
Jira/GitHub Issue numbers (if any): ______________________________
Preview links/images (Internal contributors only): __________________

https://github.com/user-attachments/assets/6a061f1b-6a19-44db-a26e-a4caa4138808
PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged:

[ ] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

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

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6729d0ac27bb4d377a664943--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://672a59058301bb0dd3fbff66--harness-developer.netlify.app


How to adjust the timezone of a log field

elastalert2-server is a very good open source project, thank you to the developers for your efforts.
However, in the process of using it, I encountered a major headache. elasticsearch stores the time zone in UTC by default, and the time zone of the alerts sent via elastalter2 is also UTC, which does not convert the time to local time.
Here are the times stored by elasticsearch.

The following alerts are sent.

I want to know how to adjust the time of sending alarms ？Thank you so much

https://elastalert2.readthedocs.io/en/latest/ruletypes.html#query-timezone

@nsano-rururu

I added query_timezone: "Asia/Shanghai" to the alert rule, still the same.

Hi @XiaoMuYi

ElastAlert2 Server
A server that runs ElastAlert2 and exposes REST API's for manipulating rules and alerts.

Questions related directly to ElastAlert2 please send directly to its github project: https://github.com/jertel/elastalert2/discussions

@XiaoMuYi
I just sent you a link to a document that I thought might be relevant. I don't know if it can be done.

@XiaoMuYi
Questions related directly
How to adjust @timestamp to local time zone in Elastalert
or
https://github.com/jertel/elastalert2/discussions


Fix displaying RawQuerySet in sql_explain view

This problem may be a regression from #309, but I'm not 100% sure.
Trying to do sql_explain on raw query with dictionary for params causes a crash.
ERROR Internal Server Error: /__debug__/sql_explain/
Traceback (most recent call last):
  File "../site-packages/django/core/handlers/exception.py", line 41, in inner
    response = get_response(request)
  File "../site-packages/django/core/handlers/base.py", line 187, in _get_response
    response = self.process_exception_by_middleware(e, request)
  File "../site-packages/django/core/handlers/base.py", line 185, in _get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "../site-packages/django/views/decorators/csrf.py", line 58, in wrapped_view
    return view_func(*args, **kwargs)
  File "../site-packages/debug_toolbar/decorators.py", line 15, in inner
    return view(request, *args, **kwargs)
  File "../site-packages/debug_toolbar/panels/sql/views.py", line 61, in sql_explain
    cursor.execute("EXPLAIN %s" % (sql,), params)
  File "../site-packages/debug_toolbar/panels/sql/tracking.py", line 188, in execute
    return self._record(self.cursor.execute, sql, params)
  File "../site-packages/debug_toolbar/panels/sql/tracking.py", line 121, in _record
    return method(sql, params)
  File "../site-packages/django/db/backends/utils.py", line 79, in execute
    return super(CursorDebugWrapper, self).execute(sql, params)
  File "../site-packages/django/db/backends/utils.py", line 64, in execute
    return self.cursor.execute(sql, params)
  File "../site-packages/django/db/backends/mysql/base.py", line 101, in execute
    return self.cursor.execute(query, args)
  File "../site-packages/MySQLdb/cursors.py", line 159, in execute
    query = query % db.literal(args)
TypeError: format requires a mapping

The reason is because params is not dictionary, but list.
The core of the issue is caused by panels/sql/traking.py
    _params = json.dumps([self._decode(p) for p in params])

This forces only dictionary keys to be send over sql_explain view.
My change is going to preserve the initial params structure.
    _params = json.dumps(self._decode(params))

Now, because dictionary params are not supported by the SQLite backend.
My test is going to be skipped for this vendor.

Thank you!


route-name-type and stubs for Illuminate\Routing

[ ] Added or updated tests
[ ] Documented user facing changes

Changes

Similar to how view names are checked when using view, the functions that generate URLs (route, to_route, Url::signedRoute, etc.) are now checked too. This way a developer gets an error when referring to a route that does not exist.
Breaking changes

This could break CI when people upgrade, since it introduces new checks and non-existing routes previously did not lead to errors. However, I think this should not be considered breaking, since the application was in a broken state in the first place. Since it uses the actual router instance of the application, the amount of false-positives should be low as well.

Thank you for your PR @NiclasvanEyk!

Thank you for your PR @NiclasvanEyk!

Thanks for the heads-up, I could have sworn I just forked it yesterday, but the 300 commits say otherwise 😅.

@mad-briller yeah that's what I wanted to add as well, but I did not have time, so I thought I'd just open a draft PR and request reviews when it is actually ready. I'll see if I get to update my fork tomorrow and then tackle the testing part.

This route may not be found ...
https://github.com/laravel/fortify/blob/74cd344aea9ab4abb5ec09f7b3349bf3bfc8bbdc/routes/routes.php#L31

This route may not be found ... https://github.com/laravel/fortify/blob/74cd344aea9ab4abb5ec09f7b3349bf3bfc8bbdc/routes/routes.php#L31

Yes, I am also running into a similar problem for the default Laravel skeleton, where the Authenticate middleware wants to redirect to 'login', however no such route is defined by default.
Do you have any suggestions on how to deal with these kinds of errors? We could just add 'default' ignore statements to the extensions.neon.

Please add to https://github.com/nunomaduro/larastan/blob/master/phpstan-baseline.neon

Does this fix the issue? As I understand it, https://github.com/nunomaduro/larastan/blob/master/phpstan-baseline.neon is used for running phpstan on the larastan source itself.
The error arises only when analyzing the user's source, so we'd need to use something like
parameters:
	ignoreErrors:
		-
			message: "#^Parameter #1 $name of function route expects route-name-string, string given.$#"
			count: 1
			path: app/Http/Middleware/Authenticate.php

to the extension.neon, so users use this configuration by default. Or am I misunderstanding something here?

I am sorry.
This is where it goes: https://github.com/nunomaduro/larastan/blob/master/tests/laravel-test.sh#L18-L23

Just noticed that since the routes are passed as a property, they are cached and not properly re-computed across analysis runs.
Will push a fix later that re-computes it every run, similar to how the ViewStringType does

We've closed the master branch. Please open a new pull request and target the 2.x branch if you wish to re-open this pull request.

Hi @NiclasvanEyk,  seems like a great pr to included in larastan, up for opening it up again?


Version number error with 1.14.0?

Looks like the latest release is with 1.14.0, but the one before it was 0.13.0.

Thanks!


upgrade to the latest ubuntu LTS release

Hi, any chance we might see docker image being upgraded to the latest LTS release, i.e. 22.04 ?
Would be nice to have, due to variety of deps which are now old... such as curl (using it in postpostUpgradeTasks script)

no, because a lot of tools are not yet working on new ubuntu due to openssl majoer version change.


Unable to upgrade to Kali 2020.3 or 2020.4rc2 base images

🐛 Bug Report
The Kali 2020.1 AMI that we have been using is now unavailable for new subscriptions.  This means that new COOL AWS accounts cannot subscribe to the old base AMI and hence cannot use the COOL Kali AMI that we build on top of the old base AMI.
Kali has made an official Kali 2020.3 AMI available, but so far I have been unable to build our COOL Kali AMI starting from that base AMI.  This is because, when cisagov/ansible-role-upgrade runs, the aptitude/apt-get commands require some input via a curses UI.  This is because Kali Linux is a rolling release, and some old 2020.3 packages need to be swapped out for completely different packages when upgrading to 2020.4.

I have attempted to post to the Kali online forums asking when the 2020.4 AMI will be released, but my post has not yet made it past the moderators.

We did have problems upgrading the Kali base image before, although they were overcome rather simply.

I have dug into the source code for the Ansible apt module, and it appears that the module runs this command:
aptitude -y  -o "Dpkg::Options::=--force-confdef" -o "Dpkg::Options::=--force-confold" full-upgrade

This is very odd.

I added a tmate debug session to the prerelease workflow so I could ssh into the GitHub Actions host at a point just before packer runs.
Once I was in the GitHub Actions host, I ran packer build --timestamp-ui -debug src/packer.json to step the packer process to a point just before the first Ansible provisioner runs.
I found the temporary PEM that packer writes to disk and used it to ssh to the AWS instance where packer is building the AMI:  ssh
From the AWS instance I became root and then ran apt-get update && apt-get install aptitude followed by DEBIAN_FRONTEND='noninteractive' DEBIAN_PRIORITY='critical' LANG='C' LC_ALL='C' LC_MESSAGES='C' LC_CTYPE='C' aptitude -y  -o "Dpkg::Options::=--force-confdef" -o "Dpkg::Options::=--force-confold" full-upgrade.
The aptitude full-upgrade command prompted me to tell it how to handle an update for the sudo configuration file.  This did not happen when I spun up a Kali 2020.3 AMI in the "Images (Staging)" account, sshd to it, and then ran these same apt-get and aptitude commands.

This is mysterious because:

The -o "Dpkg::Options::=--force-confold" should have obviated the request regarding the sudo configuration file.
aptitude should behave identically when run from a pristine Kali 2020.3 AMI, whether it is spun up by packer or manually in the AWS console.

On the plus side, I now know what is gumming up the upgrade playbook and I have a way to reach in and feel what is going on.

I noticed that the root volume is the original 8GB volume from the base AMI when packer attempts to build the AMI.  Looking in the AWS console I saw that the EC2 instance where the AMI is being built has an 8GB volume and a 20 GB volume attached at /dev/sda and /dev/xvda, respectively.  Oddly, the attachment IDs are identical.  I believe this is related to the fact that /dev/sda is the legacy name for /dev/xvda, and somehow the /dev/sda mount is superseding the /dev/xvda mount.
I modified the packer configuration in commit 9747e9a75ff69fd17a0c83f6826147e693bc2ef5 and confirmed that the root volume is now 20GB in size.  Furthermore, for reasons I don't understand, this volume size increase also made the aptitude full-upgrade command mentioned in the previous comment behave just like it did when I spun up a Kali 2020.3 AMI in the "Images (Staging)" account.  Thus the big issue I have been struggling with for days has been remedied by correcting the root volume size!

I'm now fixing some Ansible roles that are broken due to packages that were previously installed in the Kali 2020.1 base AMI not being present in the Kali 2020.3 base AMI.  See these pull requests:

cisagov/ansible-role-clamav#19
cisagov/ansible-role-xfce#6
cisagov/ansible-role-xfce-cool#3


[feat]: dockerized piper

Adds a docker-compose config that simplifies using piper locally - though it does require the piper voice to be set in the docker compose yml, rather than as a command line argument.
Two usage modes exist: Passing the full set of command line args in the compose file (including the new piper_docker tts engine), or running the container in interactive mode and calling main.py from there. Both are detailed in the docker-compose.piper-example.yml.
The clear benefit here is easy-mode usage of piper, regardless of machine. All that's required is cloning the repo, configuring the docker compose depending on which of the two options above is better suited for your use case, and running docker compose up. Can confirm this works on an M1 Macbook Pro with no compatibility issues etc.

Thanks for your awesome contributing. I'm about to merge this PR.
Would be nice if you can update README and add very simple guidance to instruct users to use piper_docker just bellow the https://github.com/p0n1/epub_to_audiobook?tab=readme-ov-file#examples-using-piper-tts section.

Nice. LGTM. Thanks again.


Import catkin_lint 1.4.21

https://launchpad.net/~roehling/+archive/ubuntu/latest

Improve handling of static libraries
Return appropriate error code if no input given
Fix regression bug with bash completion

catkin_lint 1.4.21 has been imported in Trusty, Xenial, Artful and Bionic: http://build.ros.org/job/import_upstream/225/


crash if change terminal icon to webp format picture

Windows Terminal version
1.11.3471.0
Windows build number
10.0.22000.0
Other Software
No response
Steps to reproduce

select settings from top bar menu
select a profile
change icon and pick up a webp format image

Expected Behavior
support webp picture as the icon or report it's not supported
Actual Behavior
windows terminal crashed and exit

I've just tried to reproduce this using an example webp image from Wikipedia and couldn't get it to crash. Could you provide a link to an example webp image that is actually failing for you? Or does the example I linked already crash on your system?

I use the the Ubuntu logo from https://www.windowscentral.com/youll-soon-be-able-run-ubuntu-windows-10. I tried again and see it does work. Sorry I can't reproduce the issue now.


Remove axios in favour of native fetch API

More suggestion than Issue but maybe worthwhile to consider using node's and modern browser native fetch API vs. axios. I see you save time in Axios with JSON transforms but you have no benefit with backward compatibility etc. Happy to hear your opinion because I didn't do a deep comparison between both.
My reflex is only mostly to go native where possible.

I mixed up that I used a library which included node-fetch. Ignore issue.


Update one more domain for console cdn

🚀 Deployed on https://66c7bc27ff6a246afc0f1334--cozy-fox-0defec.netlify.app


separate sensors & actuators from VM.

At the moment these are far too tightly coupled.  there should be some kind of interface between the VM itself and its sensor/actuator ports, but it shouldn't be all muddled in together.

This is particularly important for #4 where arithmetic stays same but hardware very different


HHH-13974: FlushMode set through SessionBuilder was never applied

@Sanne You might be interested at this PR

right, thanks @NathanQingyangXu and @michael-spahn ! I'll check it out soon

merged


Fixing task.flatten to allow for custom Targets inheriting from dict/MutableMapping

Description
I added a conditional short-circuit return in task.flatten.
This adds a dependency for the task module to the target module.
Motivation and Context
This allows for dict-like and iterable custom Target classes.
Have you tested this? If so, how?
I have included a unit test.

what's the use case?

I wanted to use this class:
class InMemoryDictTarget(MockTarget, MutableMapping):
    """
    Relies on luigi.mock.MockTarget implementation, based on multiprocessing.Manager().dict()
    """
    def __setitem__(self, key, value):
        if os.sep in key:
            raise ValueError('File paths separator character not allowed in keys')
        all_data = self.fs.get_all_data()
        all_data[os.path.join(self.path, key)] = value

    def __getitem__(self, key):
        if os.sep in key:
            raise ValueError('File paths separator character not allowed in keys')
        all_data = self.fs.get_all_data()
        return all_data[os.path.join(self.path, key)]

    def __delitem__(self, key):
        all_data = self.fs.get_all_data()
        del all_data[os.path.join(self.path, key)]

    def __len__(self):
        all_data = self.fs.get_all_data()
        return len(all_data)

    def __iter__(self):
        all_data = self.fs.get_all_data()
        for path, _ in all_data.items():
            if os.sep not in path:
                continue
            yield os.path.basename(path)

    def __enter__(self):
        return self

    def __exit__(self, type, value, traceback):
        with super().open('w'):
            pass

The github preview is misleading : I did not modify the test_tasks_doctest test, but test_flatten. Check out the "full file diff".
About my usage example: the goal is to have a Target stored in memory, not on disk, and behaving like a standard dict. Does it sound absurd ? Do you have other questions I could answer about it ?

the goal is to have a Target stored in memory, not on disk, and behaving like a standard dict

This text is much more comprehensible to me. I'm of course a bit skeptic as it's so volatile. What real world use case do you have?
Overall I'm still negative to add some more magic to the flatten function.

My real world use case is simple : I want to avoid writing files on disk for metas informations.
One of the fields in this dict will be the filepath to the input/ouput file processed, but of this Target other key-values pairs will be metadata that only have value during a pipeline build.
I do not want to create temporary files just to store this metadata as I want it gone one the build ended.

Yes, I think it's too magic. In particular I can't see how the change in logic the flatten function relates to enabling the feature of storing metadata in memory. Now I see it if I carefully look at the code, but I want to keep the luigi codebase more approachable.
So I'm still :-1: on how this patch implements your use-case.

OK, I understand.
I can still implement an InMemoryDictTarget somehow without this patch, so nevermind.

Feel free to share your other approaches. Even if you don't make a PR you can include some shorter hints in this PR.


"Please Confirm..." "Exit the editor?" [cancel] [quit]

(thanks for a crazy cool tool!)
Linux Ubuntu 16.04.1 x86_64 running MATE desktop.
Godot version "Godot_v2.1-stable_x11.64"
If I have not changed anything in a scene (eg. i just loaded it; or i used 'undo' enough times), when I go to quit that scene editor, the system should not ask me to "Please Confirm..." etc.
When it does ask, that is scary UX to the end user because they have no way of being sure thing are saved or not since we're apparently always asked.

Well editor already do this on scene level. As a workaround you could always close each individual scene and dismiss/save all the changes. The way how it works right now is ok for me personally, but it would be cool if dialog message would change if we have any unsaved changed to something like: "Are you sure you want to exit? You have unsaved changes!"

This can of course be improved, but I think it's good that the editor asks before closing even if there are no unsaved changes. Sometimes you have no unsaved changes, but you have several scenes opened with a specific part of the viewport focused in each scene, a specific set of scripts and maybe even some debugging breakpoints set or output from previous runs in the Output panel or the debugging tools.
If you inadvertently press the close button and it stops without confirmation, you might lose all this "non-savable" setup, and it can be quite frustrating.

It could of course be made optional via an editor setting.

Yeah it's good that this dialog is there, sometimes I'm quite messy with keyboard shortcuts, and I'm accidentally pressing 'exit editor' combination.

To me it does not show this "(Unsaved changes will be lost)" message when I quit the editor. I get only this:

Contrarily to the OP, I think now @raould is talking about the "Quit to Project Manager" dialog, which IIRC does warn about unsaved changes going lost. Which would be a duplicate of #4731.

Closing as a duplicate of https://github.com/godotengine/godot/issues/4731


Unclear how to determine installed version?

For me, it's unclear how to determine what my currently installed version of the Windows Terminal is. I tried the following things:
Check the command-line arguments: but it's not listed, and "probing" for --version gives an error that it's not an argument that's expected.
Check the Windows Store (I installed it through that), but I don't see a version anywhere. I don't really use the Windows Store, so maybe I overlooked it, but these are the places I checked:

the detailed listing
My Library > Installed: it states when modified, but not the version
My Library > Installed: same as above
My Library > Downloads: it states versions, but not the Windows Terminal is not listed under Recent Activity, but Available Updates, and that doesn't list a version (see Context below)

Looked for an issue about this in this repo, but couldn't find anything related: almost any issue has the word version in it, since it's asked when creating an issue 😅
Checked the issue templates, although there is listed how to find the version of Windows, not of the Windows Terminal
The properties pane on the wt.exe executables I could find, but they're completely empty, as the files are also 0 bytes. I checked these locations:

C:\Users\ties\AppData\Local\Microsoft\WindowsApps\wt.exe
C:\Users\ties\AppData\Local\Microsoft\WindowsApps\Microsoft.WindowsTerminal_8wekyb3d8bbwe

Context
I was looking into an issue I keep running into (#3609), and noticed I was running an older version of the Windows Terminal. Before I was going to update it, I wanted to known which version I have installed, so I can cross check all the related issues, and comments, if I can expect it to be fixed.
Suggested Improvements

Add to the issue templates
Add to the main docs somewhere
Add support for --version argument to wt.exe

Go to the About Page. If you don't have it then you're running an extremely early build of Windows Terminal and should update to the latest release. However I do agree we need to add --version to check via CLI (verified this still doesn't work on the latest .11 release)

👍 I was looking for something like the about page, but couldn't find it, completely overlooked the drop-down arrow.
Cool that the --version is being picked up ;) Thnx for the comment in #4632.

As of 1.11.3471.0, this still doesn't work the way I'd hoped it would. While wt -v does produce the desired information (in a warning dialog for some reason), I wanted a way to get it programmatically à la python -V without having to resort to parsing it out of something like REG QUERY "HKCU\SOFTWARE\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel\SystemAppData\Microsoft.WindowsTerminal_8wekyb3d8bbwe\Schemas" /v PackageFullName or REG QUERY "HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\wt.exe" /ve or REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\wt.exe" /ve.
Is there a way to do this? If not, would it be possible to add a different command-line flag to the wt executable with this behavior?
If there are no plans to add such functionality, I could always put together a PowerShell function like
function Get-WindowsTerminalVersion {
    $WindowsTerminalVersionRegistryHive = Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\wt.exe"
    $pattern = "_(.*?)_"
    $script:WindowsTerminalVersion = [regex]::match($WindowsTerminalVersionRegistryHive.Path, $pattern).Groups[1].Value
}

but that's pretty ugly and I'd rather not use it.

I'd hoped it would

Hey @dschulman-repay! I'm not sure your use case was captured in this issue (it looks like the original reporter wanted to see if they had a fixed vs. broken version of Terminal), so I'm not too surprised that this resolution didn't help you out. We're looking at offering this info in the environment in #1040; however, if that's not enough, I'd love to hear about your scenario!
In general, we encourage folks not to detect the Terminal version and make any decisions based on it, because many of the underlying components that make up the Terminal are also part of the Windows Console. Any behavioral decisions made based on the Terminal version will exclude folks who are using a new-enough console outside of Terminal, or using Visual Studio Code or the Visual Studio IDE's integrated terminal.

for some reason

It is a very sad reason ("displaying output in a dialog" section).

While I can understand the rationale for not encouraging users to use the version of Terminal as a basis for application decisions, my use case is literally an inventory script of the sort that an admin might run remotely to see who's got what (and possibly push new versions of dangerously out-of-date applications as needed). At the moment, what I'm collecting looks like this:
Hardware
        Machine                                 Dell Inc. Precision 5550 (<machine ID>)
        CPU                                     Intel® Core™ i7-10875H CPU @ 2.30 GHz
        TPM                                     Enabled, Activated, Ready, Version 2.0
        Temperature                             60.1 °C / 140.2 °F (critical temperature 100.1 °C / 212.2 °F)
        BIOS version                            1.10.0 (2021-09-27)
        Product                                 0GX59H
        Baseboard                               /GGGL6D3/CNCMK0014I0544/
        Dell Service Tag                        GGGL6D3
        Express Service Code<PHONE_NUMBER>1
        RAM                                     32 GB
        Video resolution and color depth        1920 × 1200 × 32
Battery
        Chemistry                               Unknown
        Capacity                                84290 mAh
        Status                                  On AC power
        Operational Status                      OK
        Manufactured                            2021-03-25
        Availability                            unknown
        Remaining charge                        100%
Disks
        Drive   Volume          Filesystem      Free space

        C:      OS              NTFS            260.84 GB free / 474.86 GB:     54.93%
Windows
        64-bit Windows 10 Enterprise version    2009
        OS build                                19043.1348 (Windows version 21H1, May 2021 Update)
        Windows product key                     D11RC-NTROL-VUSAW-BBUI6-NRT0E
        Installed .NET Framework version        4.8 (Windows 10 May 2020 Update)
        Installed .NET SDK version              6.0.100
        Installed .NET runtime version          6.0.0
        Windows Terminal                        1.11.3471.0
        PowerShell                              Core 7.2.1
        WSL
                 Ubuntu-20.04 (Running)         WSL 2 DEFAULT
                 docker-desktop-data (Running)  WSL 2
                 docker-desktop (Running)       WSL 2
Package management
        Chocolatey                              0.11.3
        WinGet                                  1.1.13405
OpenSSL                                         3.0.0
cURL                                            7.80.0
Visual Studio Code                              1.63.1
Python
        Installed version:                      3.10.1
Java
        OpenJDK 17.0.1                          <IP_ADDRESS>
        Java™ SE 8                              8.0.3110.11
        OpenJDK 17.0.1                          <IP_ADDRESS>
Network
        Domain (primary DNS suffix)             WORKGROUP
        Network adapter                         Ethernet 3
        Network type                            Realtek USB GbE Family Controller #3
        Link speed                              1 Gbps
        Connected to Internet?                  True
        VPN status                              Connected on Local Area Connection
        Ping round-trip time                    17 ms
        Estimated connection speed              44.5 Mbps
        Network SSID                            Network Local Area Connection 2
        Connection-specific DNS suffix          nc.rr.com
        IPv4 address                            <IP_ADDRESS>
        IPv6 address                            fe80::2cab:2a1f:39a1:a5eb%19
        Physical address                        48:51:C5:07:9D:EB
Admin
        Registered to                           Admin (Me Want Cookie)
        Userid                                  devnull (Me)
        System installed                        2021-05-16 12:05:27 EDT-04:00
        Last system boot                        2021-12-09 20:36:15 EST-05:00
        Current timestamp                       2021-12-15 18:11:27 EST-05:00

I noticed package management in your script. This is the route for your use case. There are many ways to determine a release is out for both Chocolately and eventually WinGet once they support updates. One method could be by git commit. You know what it is for each release, so it's reliable (unless Github is down).

A lot of the applications I'm tracking have no (public) Chocolatey packages and aren't set up for Windows Package Manager (nor are they registered with Ninite or Scoop), either. Is there no alternative but to set up private Github repos for all of them?

Just installed the latest version from the Windows Store and I'm seeing terrible terrible lag.
https://user-images.githubusercontent.com/5203583/148709097-dd54773e-dcb5-42bb-9cbf-eac4a74e7938.mp4
I'd attach a dump file but there is no single .exe:

Any suggestions?

Is there another process that's running at 100% CPU? if so, that sounds a bit like #11916.
Regardless, I'd probably open a new thread for that issue, since that seems totally unrelated to determining the installed Terminal version.


Mattermost App shows to be connecting all the time

Submit feature requests to http://www.mattermost.org/feature-requests/. File non-security related bugs here in the following format:
Summary
Issue in one concise sentence.
Despite showing messages correctly and sending notifications, the app shows to be connecting non stop.

Environment Information

Device Name: apple iphone 6s+
OS Version: iOS 10.3.3
Mattermost App Version: 1.2.0 (Build 49)
Mattermost Server Version: 4.0.0 (Build 4.0.3)

Steps to reproduce
How can we reproduce the issue?
Install app, connect to server
Expected behavior
Describe your issue in detail.
After deleting mattermost classic I installed the new mattermost app and connected to my account. The app works finde now, but keeps on showing the grey bar in the top that reads "connecting...".
Observed behavior
What did you see happen? Please include relevant error messages and/or screenshots.
No error messsages
Messages are delivered properly (Send and receive)
Possible fixes
If you can, link to the line of code that might be responsible for the problem.

have you check that your server is configured to allow websocket connections using the APIv4? do you have access to the server logs to see if there's anything being logged related to this?
have you tried connecting to https://pre-release.mattermost.com, if so, does it still happen?

actually this looks like a dup of #742 feel free to continue the conversation there.


[GOBBLIN-1599] Fixes Avro usage on deprecated APIs

Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA
https://issues.apache.org/jira/browse/GOBBLIN-1599
Description
Gobblin depended on an old deprecated Avro API that worked with Jackson JsonNode objects. In Gobblin's default Avro dependency version (1.8) these APIs were already marked as deprecated. In Avro 1.9 these APIs were replaced by similar APIs that work with Object rather than JsonNode Java objects.
Tests
My PR does not need unit tests to validate whether it is working. Simply attempting to compile the project with a flag to inject avro 1.9+ (-PavroVersion=1.9.1) validates that this PR fixes the issue.
Functionally the change also worked appropriately as I was able to use newer Avro versions to read events from Kafka using gobblin jobs that depended on these new versions.
Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

@abhisheknath2011 Please review

@pedro93 Can you create a ticket on Apache JIRA and link it in the PR description? Thanks.

Done

@pedro93, Thanks for sending the PR. Just wanted to update you that we are working on Avro 1.9 upgrade and some part of the work is already merged to a new branch avro_1_9. The final PR testing is current in progress. The changes in this PR are already done as part of that work. Hence, it would take couple of more weeks to merge all the changes to the master branch. As this PR is redundant, I hope you would be able to wait for couple of more weeks. Thanks.


Exchange (as a location) -> exchange

change capital to lowercase, to avoid confusion with Exchange product.

Hi @TristankMS, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@TristankMS : Thanks for your contribution to the Azure documentation! The author, @cherylmc, has been notified to review your proposed change.

@TristankMS Thank you for the correction.  @tysonn please merge.


Refreshing on the Channel List page highlights the wrong nav item

From the channel list page, if you refresh, the nabber at the top will show as though you are on the Create page.

Closing as the whole UI is going to get re-implemented in EUI


Update Community - Proof of Contribution.md

Proofread and corrected some typo errors

Community rewards are not live until Phase 3 and related to Front End Interfaces.
I think you meant to put this in the Code section of Contributions.

Says the merge is blocked. Please check the status. Thanks.


Build LLDB module_name from directory and filename

Fixes #2946.
Xcode 15.3 doesn't expose __get_fullpath__ anymore so building that with a public API equivalent. Works on both old and newer Xcodes.

You'll need to sign-off on your commit to pass the DCO check.

Sorry, my bad, signed-off.

Thanks!


Want to add Backtracking Algos

I want to add N-Queen, Rat In A Maze, Sudoku Solver etc. Please assign me

Go ahead  @ksalokya

I can add lot of backtracking problem-solutions including  Knight 's tour , subset partition , n-queen , rat-in-maze , sudoku-solver etc.
Plz assign me this.


Performance test group fails

Performance test group fails with wrong gas

other tests pass but take too long time to complete


Replace SmallVector with SmallSetVector in the new epilogue ARC matcher

@swift-ci Please smoke test

For curiosity and future maintenance purposes, why make this change?

I need it to wire up to ASO (arc sequence opt) which needs to search through the SmallVector to find whether an instruction exists in the SmallVector. so I think SmallSetVector should be the one i use.


[Suggestion] be able to use 'Object... args' for @WrapOperation

Hi,
sometimes you just want to wrap the method without really worrying about any of the args, in which case just having the method parameters be Object... args, Operation<?> original could be useful.
I know that this alone doesnt seem like a big benefit but it can allow for more compatibility between different mc versions (where you may want to wrap the same method but it has different args) by using different this + multiple @At's.
Similar would also be useful for @WrapWithCondition (although in that case just having no args would also do the job, especially if you want to wrap multiple @At's with the same condition.
This isn't something super necessary but could be neat for making mods that work for lots of different versions.

actually, the parameters would still be in the @At so it wouldnt actually help compatibility, so i'll close this


Documentation for set_disk_free_limit and set_vm_memory_high_watermark

A bit of documentation for https://github.com/rabbitmq/rabbitmq-server/issues/448
https://github.com/rabbitmq/rabbitmq-server/issues/461

:+1:


Changelog updated in 0.10 version

Coverage remained the same at 53.365% when pulling 3b745d8a4526511116b3f565b0f674903964ff95 on compae:feature/changelog-0.10 into 7dde2311dea8df8d36d93a1e42c2a91d1a6c4074 on Stratio:master.

:shipit:

A job will handle this PR ASAP on Jenkins

Rebase && testing in progress