cmd/vet: %w in Printf call should be flagged

package main

import (
	"errors"
	"fmt"
)

func main() {
	err := errors.New("ABC")
	fmt.Printf("error: %w\n", err)
}

https://play.golang.org/p/-kQ6HtIIMG7
vet should complain about the %w verb. Only in Errorf format strings does it have meaning.

CC @ianthehat @matloob @dominikh

This also seems like a pretty simple issue for anyone wanting to get started contributing to vet.

I would love to take a shot on this. Any pointers to get started on this issue?

The file in question is this one - https://github.com/golang/tools/blob/master/go/analysis/passes/printf/printf.go. Look at how other verbs are handled and take it from there.

Ah I'm on the right track then. Thank you! I'm working on this 😃

vet already complains about the %w verb in printf. I ran the above code and this is what I got:
./main.go:10:2: Printf format %w has unknown verb w.

You are right. This was fixed by https://github.com/golang/tools/commit/1d1727260058c6d58ebfdeb982c4657342282355. The original issue was reported by @josharian himself which was about passing strings to a %w parameter. But the commit reported usages of %w with non-Errrof functions too.
The error message is Printf call has error-wrapping directive %w though, not the one you mentioned.
I will go ahead and close this one. Thanks for looking into it @Inconnu08.

Exactly. But the end error message is the above one reported by vet. Anytime!

Oops, sorry. :( I thought I tested with tip but apparently only did 1.13. Thanks, @Inconnu08.


cgroup: no space left on device

Hi,
I met the problem when I found that cluster can create a new job on one specific worker node, which always failed.
Also failed when just run hello-world:
$ docker run hello-world
docker: Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "process_linux.go:279: applying cgroup configuration for process caused \"mkdir /sys/fs/cgroup/memory/docker/55d7db61bab0b12b483a1e4dd2164ed7c4787375fd7aaed6a4501656941c0ece: no space left on device\"": unknown.
ERRO[0001] error waiting for container: context canceled

I found this post in CN, another post in EN and the situation is almost the same except for the OS.
$ cat /proc/cgroups
#subsys_name	hierarchy	num_cgroups	enabled
cpuset	10	26	1
cpu	5	127	1
cpuacct	5	127	1
blkio	7	127	1
memory	6	65535	1
devices	8	127	1
freezer	3	26	1
net_cls	2	26	1
perf_event	11	26	1
net_prio	2	26	1
hugetlb	9	26	1
pids	4	128	1

The memory has reached the maximum usage of cgroups.
Thanks!

I am not clear about your question. It seems that the Docker has some problem in your host OS? I suggest you to ask this question in Docker community.
Or if you don't want the trouble, a clean install might help address the issue.

I hereby close this issue. For Docker issue, please refer to Docker community.


Fix Android regressions

Tests that use the local directory cannot be run from an Android apk, and Android comes with gzip, but not unzip.

Doesn't pass.

Auto-merge toggled off

Addressed all comments, passes the auto-tester now.

Auto-merge toggled on


Recommended approach for 'window' component dependency?

I'm currently using 'slick-carousel' which references 'window'. I also do some references to window in some of my own react components to help with sizing of the component.
Do you have a recommended strategy for server side rendering, when I incorporate components into the project that reference 'window'?

@paulwehner Thanks for asking. :)
A simple workaround for this is to check whether typeof window !== 'undefined when using window.

Closing this issue but feel free to keep this thread running!


Add global search

One of our most used features of our very old poweradmin installation was the ability to run a global search across all domains and records. I wasn't able to find such a feature in PowerDNS-Admin.
We use this e.g. to find multiple records which point to a singe IP address. If you don't know to which zone a record may belong to and you haven't setup a reverse record, it currently is nearly impossible to find forward records pointing to the IP address.
I also found an endpoint in the PowerDNS API which can provide such a feature: https://doc.powerdns.com/authoritative/http-api/search.html
Would be great if that could be added to PowerDNS-Admin, too. The search field could be placed centralized in the top bar together with a drop down list where the user can select the search type targets provided by the PowerDNS API: All, Zone, Record and Comment.

It was implemented in #599. Restricted to Administrator/Operator only.


Could this support ios 7.0?

could this lib support ios 7.0?

I'm not quite sure since I'm not familiar with it, is there any particular things we need to check/change to support ios7?

cause the Requirement shows me this lib is start from ios8 or later.


Localized collection-link with better display

Added language selector to collection-link and caching display on a key composed of link.id and lang.
Collection-link display option can now handle an array of fieldNames and returns a comma separated display string

Thanks for the contribution! Will review it soon!

Great! If there is any documentation I can update with the display field, point me in the right direction :)


[TEMP DO NOT MERGE] feature system vm direct download

Description

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Screenshots (if appropriate):
How Has This Been Tested?

@rhtyd Re-open if you need to. I'm just closing my old/irrelevant PRs


How to resolve the source / path with a local module?

Related issue: https://github.com/gruntwork-io/terragrunt/issues/661
Getting:
Error: Unreadable module directory

Unable to evaluate directory symlink: lstat ../../../modules: no such file or
directory

Error: Failed to read module directory

Module directory  does not exist or cannot be read.

[terragrunt] 2020/08/30 17:33:35 Hit multiple errors:

What is the correct configuration for the following?
My dir structure looks like this:
/
+-- modules
|    +-- mongodb
+-- us-west-2
|    +-- eng
|     |     +-- mongodb

/us-west-2/eng/mongodb/terragrunt.hcl:
terraform {
  source = "../../..//"
}

/us-west-2/eng/mongodb/main.tf
module "mongodb_instance" {
  source = "../../../modules/mongodb"
}

Found the answer:
In main.tf:
module "mongodb_instance" {
  source = "./modules/mongodb"
}


Show latest slowzone values

Motivation
We have access to both the average and the latest slowzone values, we should show both, and the map should prioritize latest when showing today
Changes

![Screenshot 2023-10-30 at 3 51 28 PM](https://github.com/transitmatters/t-performance-dash/assets/9310513/ce6d879e-27e7-49dc-84e6-62490119b2ae)
Testing Instructions

nit: should latest be current?

@nathan-weinberg The field exists in slowzones that have since ended. It shows the last slow speed before the slowzone was lifted/resolved, so it's latest for all except the ongoing slowzones


Selfcheckgpt

I am trying to add a new task for llm hallucination. This is the very initial code. There is something I'd like to discuss with everyone about:

How to generate multiple generations for one prompt elegantly？This could be very useful for many llm self-consistent evaluations.

I have implemented one possible solution. But I am not sure it is the best one.
Thank you very much.

hi @haileyschoelkopf @lintangsutawika, I have refactored the code so that it has its own task.py to deal with its unique multiple generations kwargs. In order to make it to be recognized by the llm-eval. I imported the selfcheckgpt in task/init.py which is similar to squadv2. Thank you very much.

@erenup Thank you for your contribution to our library. We will not be able to merge this PR until you do the following:

Sign the CLA
Change the readme to accord with our template. It currently looks like you copied the readme from the official code, which will confuse users as it refers to code not found in this repo and uses the term "we" to refer to people other than EleutherAI.
Run some models through the code and compare results with the official implementation.

hi @StellaAthena Thank you.

Sign the CLA.

done

Change the readme to accord with our template. It currently looks like you copied the readme from the official code, which will confuse users as it refers to code not found in this repo and uses the term "we" to refer to people other than EleutherAI.

done

Run some models through the code and compare results with the official implementation. Results on LLaMA, RWKV, Pythia, and T0 would cover all the major bases.

I have run some experiments and the results should be the same as the official repo since the evaluation code in task.py copies the selfchckgpt readme API and does not change other things.  below numbers are results:

some results:
-- gpt-6b on SelfCheckNLI

export SELFCHECKGPTDEVICE=cuda
export SELFCHECKGPTTYPE=SelfCheckNLI
lm_eval --model hf \
    --model_args pretrained=${model_path_gpt-j-6b} \
    --tasks selfcheckgpt \
    --device cuda:0 \
    --batch_size 32

--

-llama2 7b on SelfCheckNLI

export SELFCHECKGPTDEVICE=cuda
export SELFCHECKGPTTYPE=SelfCheckNLI
lm_eval --model hf \
    --model_args pretrained=${model_path_Llama-2-7b-chat-hf} \
    --tasks selfcheckgpt \
    --device cuda:0 \
    --batch_size 32

--

@lintangsutawika @haileyschoelkopf this is now ready for your review again.


console error in Obsidian 1.3.x: a Component should be passed to renderMarkdown

Describe the bug
I'm not actually sure that this is a bug yet, but Obsidian itself seems to feel that this could be the source of a potential memory leak.
When the plugin parses a todoist fence in the latest version of Obsidian (1.3.4 as I'm writing this), the following stacktrace is emitted:
Error: Plugin "todoist-sync-plugin" is not passing Component in renderMarkdown. This is needed to avoid memory leaks when embedded contents register global event handlers.
    at t.render (app.js:1:1255232)
    at t.renderMarkdown (app.js:1:1255013)
    at eval (MarkdownRenderer.svelte:13:28)
    at run (index.mjs:20:12)
    at Array.map (<anonymous>)
    at eval (index.mjs:2058:58)
    at flush (index.mjs:1280:17)
t.render @ app.js:1

To Reproduce
Steps to reproduce the behavior:

Install the latest Obsidian
Install this plugin
Observe the developer console while opening a page with a ```todoist fence

Expected behavior
No errors in the console.
Screenshots

Desktop (please complete the following information):

Plugin Version: 1.11.1
Obsidian Version: 1.3.4

Additional context
N/A

Yep this resolved itself for me.

I am getting this same error.  I don't see any actual errors on the pages where I am showing todoist tasks, but I see this in the developer console.  Should I just ignore this?
Thanks--
Al

I also am getting this error on the console. It appears with a couple of other plugins, too (custom-classes and rss-reader). I am not a real coder at all, but so far as I can see, you are passing "null" into renderMarkdown where it is expecting the name of the plugin. I will make this change and see if (1) it eliminates the error and (2) the plugin still works!

I also am getting this error on the console. It appears with a couple of other plugins, too (custom-classes and rss-reader). I am not a real coder at all, but so far as I can see, you are passing "null" into renderMarkdown where it is expecting the name of the plugin. I will make this change and see if (1) it eliminates the error and (2) the plugin still works!

@seatrout - I'm experiencing exactly that same as what you described (other plugins affects, the "null" issue). I know its almost a year ago, but did you resolve? What is "this change" you are referring too (if you still remember)?

I'm actually completely rewriting the rendered task lists which will fix this as well. So this will be resolved in the next release

This should be fixed as of the latest release - v2.0.0


Support mobx-state-tree

Do you plan to support mobx-state-tree package?

Can you outline what mobx-state-tree needs to be supported?
I haven't used it.

I believe you should be able to use it with no rewires.  The rewire for MobX was for using decorators which I think isn't needed these days i.e. https://twitter.com/mweststrate/status/966966306070323200?lang=en


Adding a comment in Azure Devops does not get updated in VSCode

Extension version: 0.0.21
VSCode Version:1.55.2
OS: Windows

Steps to Reproduce:

Open PR in VSCode with the extension
Add comment on the PR in VSCode

You will see that even after refreshing the extension the comment that you added from Azure Devops will not appear in VSCode. Only after closing closing the PR completely and reopening it the new comment will appear

Are you adding the comment through Azure DevOps UI? Did you try refreshing the PR in VS Code?

Yes, I added a comment on Azure Devops UI and did not see in VSCode after refreshing the extension. Was able to resolve by reloading the window using CTRL+SHIFT+P --> reload window

So adding a comment on AzDO won't auto reflect on VS Code. This is because VS Code does not maintain an open socket connection to the AzDO. The list of comment is only fetched when PRs are loaded. You can right click on the PR and refresh it manually to see the comments. No need to reload the entire window.

Great, did not know that it is possible to refresh a PR. Thanks!


Background color of TextSpan when the text has English/Non English characters(Emoji)

Steps to reproduce
When the TextSpan's text consist English characters with emoji. the height of the background color is Inconsistent
Expected results
Background color height should be consistent through the text
Actual results
Emoji's background has different height compared to non emoji characters
Code sample
Code sample
Scaffold(
  body: Center(
    child: RichText(
      text: TextSpan(
        text: '📄Untitled',
        style: TextStyle(
          color: blue_60,
          fontWeight: FontWeight.bold,
          background: Paint()..color = blue_10,
        ),
      ),
    ),
  ),
),

Screenshots or Video

Screenshots / Video demonstration

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
[!] Flutter (Channel stable, 3.16.9, on macOS 14.3.1 23D60 darwin-arm64, locale en-US)
    ! Warning: `dart` on your path resolves to /opt/homebrew/Cellar/dart/3.2.5/libexec/bin/dart, which is not inside your current Flutter SDK checkout at /Users/nithsua/fvm/versions/3.16.9. Consider adding /Users/nithsua/fvm/versions/3.16.9/bin to the front of your path.
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.2)
[✓] IntelliJ IDEA Ultimate Edition (version 2023.2.5)
[✓] VS Code (version 1.87.0)

I would like to confirm the issue again. Do you mean the baseline (green line below) is inconsistent between emoji and text?

I meant the white space above the emoji.

The below code outputs
RichText(
  text: TextSpan(
    text: '📄 Untitled',
    style: TextStyle(
      fontSize: 16,
      color: blue_60,
      fontWeight: FontWeight.bold,
      background: Paint()..color = blue_10,
    ),
  ),
)

The background color of the TextSpan seems to behave differently when used in RichText compared to in TextField
I'm using a CustomTextEditingController which has the below buildTextSpan
@override
TextSpan buildTextSpan({
  required BuildContext context,
  TextStyle? style,
  required bool withComposing,
}) {
  final matchedRanges = _findMatchedRange(text);
  List<InlineSpan> children = [];

  TextRange? previous;
  for (var matchedRange in matchedRanges) {
    if (previous == null) {
      children.add(TextSpan(text: matchedRange.textBefore(text)));
    } else {
      children.add(TextSpan(
        text: text.substring(previous.end, matchedRange.start),
      ));
    }
    previous = matchedRange;
    children.add(
      TextSpan(
        text: matchedRange.textInside(text),
        style: style?.copyWith(
              color: blue_60,
              background: Paint()..color = blue_10,
            ) ??
            TextStyle(
              color: blue_60,
              background: Paint()..color = blue_10,
            ),
      ),
    );
  }
  children.add(
    TextSpan(
      text: previous == null ? text : previous.textAfter(text),
    ),
  );

  return TextSpan(
    children: children,
    style: style,
  );
}

The output for this looks like this

It seems to relate to your CustomTextEditingController which has some undefined components. Please provide a completed and minimal reproducible code sample that doesn’t include 3rd party plugins or complex production code.

I will try to get the minimal code for the CustomTextEditingController. But the issue persist even with the RichText widget right?

But the issue persist even with the RichText widget right?

The issue is not reproduced. The text is showing as I shared above. Here is the sample code I used:

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

void main() {
  runApp(
    MaterialApp(
      title: 'Flutter Demo',
      home: Scaffold(
        body: Center(
          child: RichText(
            text: TextSpan(
              text: '📄 Untitled',
              style: TextStyle(
                color: Colors.blue[600],
                fontWeight: FontWeight.bold,
                background: Paint()..color = Colors.blue[100]!,
                fontSize: 48,
              ),
            ),
          ),
        ),
      ),
    ),
  );
}

I also use `RichText`, and the background color is set in the internal `TextSpan`, but the Chinese and English displays are not on the same horizontal line, and the background color looks misplaced to the naked eye.
@huycozy

@giantss Thanks, I can reproduce that case with non-English and English text (on Android app and Web). This is not reproduced with emoji, though.

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

void main() {
  runApp(
    MaterialApp(
      title: 'Flutter Demo',
      home: Scaffold(
        body: Center(
          child: RichText(
            text: TextSpan(
              text: '看不见Can\'t see',
              style: TextStyle(
                color: Colors.blue[600],
                fontWeight: FontWeight.bold,
                background: Paint()..color = Colors.blue[100]!,
                fontSize: 48,
              ),
            ),
          ),
        ),
      ),
    ),
  );
}

flutter doctor -v (stable and master)
[✓] Flutter (Channel stable, 3.19.3, on macOS 14.1 23B74 darwin-x64, locale en-VN)
    • Flutter version 3.19.3 on channel stable at /Users/huynq/Documents/GitHub/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision ba39319843 (6 hours ago), 2024-03-07 15:22:21 -0600
    • Engine revision 2e4ba9c6fb
    • Dart version 3.3.1
    • DevTools version 2.31.1

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

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

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

[✓] Android Studio (version 2023.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • android-studio-dir = /Applications/Android Studio.app/
    • Java version OpenJDK Runtime Environment (build 17.0.9+0-17.0.9b1087.7-11185874)

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

[✓] Connected device (3 available)
    • iPhone (mobile) • d9a94afe2b649fef56ba0bfeb052f0f2a7dae95e • ios            • iOS 15.8 19H370
    • macOS (desktop) • macos                                    • darwin-x64     • macOS 14.1 23B74 darwin-x64
    • Chrome (web)    • chrome                                   • web-javascript • Google Chrome 122.0.6261.112

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

• No issues found!

[!] Flutter (Channel master, 3.21.0-7.0.pre.46, on macOS 14.1 23B74 darwin-x64, locale en-VN)
    • Flutter version 3.21.0-7.0.pre.46 on channel master at /Users/huynq/Documents/GitHub/flutter_master
    ! Warning: `flutter` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 9b276be7fe (2 hours ago), 2024-03-14 21:46:36 -0400
    • Engine revision 995d8903e0
    • Dart version 3.4.0 (build 3.4.0-234.0.dev)
    • DevTools version 2.33.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 34.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.9+0-17.0.9b1087.7-11185874)
    • All Android licenses accepted.

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

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

[✓] Android Studio (version 2023.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • android-studio-dir = /Applications/Android Studio.app/
    • Java version OpenJDK Runtime Environment (build 17.0.9+0-17.0.9b1087.7-11185874)

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

[✓] Connected device (4 available)
    • RMX2001 (mobile) • EUYTFEUSQSRGDA6D          • android-arm64  • Android 11 (API 30)
    • iPad (mobile)    • 00008103-000A1464346A201E • ios            • iOS 17.2 21C62
    • macOS (desktop)  • macos                     • darwin-x64     • macOS 14.1 23B74 darwin-x64
    • Chrome (web)     • chrome                    • web-javascript • Google Chrome 122.0.6261.129

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

! Doctor found issues in 1 category.

Oh, I think this phenomenon may be caused by the same reason. This phenomenon is particularly obvious on iPhones.

I just re-checked this on iOS with the emoji example at https://github.com/flutter/flutter/issues/144753#issuecomment-1985085245, the issue indeed occurs there.
May be related: https://github.com/flutter/flutter/issues/40936

Demo

iOS (emoji)
Android (non-English text)

flutter doctor -v (stable and master)
[✓] Flutter (Channel stable, 3.19.3, on macOS 14.1 23B74 darwin-x64, locale en-VN)
    • Flutter version 3.19.3 on channel stable at /Users/huynq/Documents/GitHub/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision ba39319843 (6 hours ago), 2024-03-07 15:22:21 -0600
    • Engine revision 2e4ba9c6fb
    • Dart version 3.3.1
    • DevTools version 2.31.1

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

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

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

[✓] Android Studio (version 2023.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • android-studio-dir = /Applications/Android Studio.app/
    • Java version OpenJDK Runtime Environment (build 17.0.9+0-17.0.9b1087.7-11185874)

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

[✓] Connected device (3 available)
    • iPhone (mobile) • d9a94afe2b649fef56ba0bfeb052f0f2a7dae95e • ios            • iOS 15.8 19H370
    • macOS (desktop) • macos                                    • darwin-x64     • macOS 14.1 23B74 darwin-x64
    • Chrome (web)    • chrome                                   • web-javascript • Google Chrome 122.0.6261.112

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

• No issues found!

[!] Flutter (Channel master, 3.21.0-7.0.pre.46, on macOS 14.1 23B74 darwin-x64, locale en-VN)
    • Flutter version 3.21.0-7.0.pre.46 on channel master at /Users/huynq/Documents/GitHub/flutter_master
    ! Warning: `flutter` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 9b276be7fe (2 hours ago), 2024-03-14 21:46:36 -0400
    • Engine revision 995d8903e0
    • Dart version 3.4.0 (build 3.4.0-234.0.dev)
    • DevTools version 2.33.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 34.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.9+0-17.0.9b1087.7-11185874)
    • All Android licenses accepted.

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

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

[✓] Android Studio (version 2023.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • android-studio-dir = /Applications/Android Studio.app/
    • Java version OpenJDK Runtime Environment (build 17.0.9+0-17.0.9b1087.7-11185874)

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

[✓] Connected device (4 available)
    • RMX2001 (mobile) • EUYTFEUSQSRGDA6D          • android-arm64  • Android 11 (API 30)
    • iPad (mobile)    • 00008103-000A1464346A201E • ios            • iOS 17.2 21C62
    • macOS (desktop)  • macos                     • darwin-x64     • macOS 14.1 23B74 darwin-x64
    • Chrome (web)     • chrome                    • web-javascript • Google Chrome 122.0.6261.129

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

! Doctor found issues in 1 category.

From triage: we're not sure if this is something that it is possible to configure through the framework API. Its unclear if this is actually a bug

Sending this to team-framework, if you are familiar with this issue or know what the right solution is that would be great. Otherwise throw it back at us.

The framework just passes the background color right over to the engine in https://main-api.flutter.dev/flutter/dart-ui/TextStyle-class.html and the engine decided how to paint this.

Otherwise throw it back at us.

I am going to take you up on this :)

We will need to investigate the text APIs to determine if there is an option to configure the expected background color.


R_LIBS_USER: Validate and pre-create(?)

Validate the content of R_LIBS_USER, which may contain more than one folder.
If the RStudio Server requires those folders to exist, we should create them first.

No need to pre-create.  R will prompt user if they want to create these personal library folders.  Because of this we cannot/should not pre-create, and therefore we cannot validate either.


Cannot delete an agent policy that is assigned to any active or inactive agents

I am having issue when destroying resources related to elasticstack_fleet_agent_policy / elasticstack_fleet_integration_policy

{"statusCode":400,"error":"Bad Request","message":"Unable to remove package with existing package policy(s) in use by agent(s)"}

resource "elasticstack_fleet_agent_policy" "fleet_server_policy" {
  name            = "Fleet Server on ECK Policy"
  policy_id       = local.fleet_server_policy_id
  namespace       = "default"
  description     = "Fleet Server on ECK Policy"
  sys_monitoring  = true
  monitor_logs    = true
  monitor_metrics = true
}

resource "elasticstack_fleet_integration_policy" "fleet_server_policy_integration_policy" {
  name                = "fleet-server-1"
  namespace           = "default"
  description         = "fleet-server-1"
  agent_policy_id     = elasticstack_fleet_agent_policy.fleet_server_policy.policy_id
  integration_name    = elasticstack_fleet_integration.fleet_server_integration.name
  integration_version = elasticstack_fleet_integration.fleet_server_integration.version

  input {
    enabled      = true
    input_id     = "fleet_server-fleet-server"
    streams_json = jsonencode({})
    vars_json = jsonencode({
      custom : ""
    })
  }
}

I'm wondering if there is some way we are suppose to handle the gracefully deleting of these resources.
After seeing this error produced via terraform which i believe jsut comes from the api, i deleted the elastic agents which i have deployed onto my kbuernets and checked the status of the agents
{
  "results": {
    "online": 0,
    "error": 0,
    "inactive": 0,
    "offline": 349,
    "updating": 0,
    "unenrolled": 1,
    "all": 350,
    "active": 349,
    "other": 0,
    "events": 0,
    "total": 349
  }

}

Okay i managed to resolve this, when a agent pod is deleted/restarted (which could happen on kubernetes for a number of reasons)  it goes into an offline status so although yuo may only have 9 nodes, you could end up with 300+ offline agents liek i did.
In order to remove the policy they should all be unenrolled.
To unenroll them i have to manually do this via the api
 curl -X GET https://<kibana_domain>/api/fleet/agents\?perPage\=500 \
-u 'elastic:<password>' \
-H 'kbn-xsrf: true' | jq '.items[] | select(.status == "offline") | .id' | paste -sd ","

Plug the list of agent ids you get from the above curl command into the below bulk_unernoll
POST kbn:/api/fleet/agents/bulk_unenroll
{
  "agents":
],
  "force": true,
  "revoke": true
}

Not a particularly nice thing to do but this is one way to deal with this qwirk, open to better suggestions.


Bar scence

Version
3.0.1
Seed
R731-CX4U-NHZE06B09F50050Z3ZZ3ZZZZZZZZZZZZ00Z
Scenario
RE 3 (Jill)
What happened?
Same seed Ark being brad in the bar was acting weird he ran to me with a knife and when he killed the zombie the game crashed.

I am unable to reproduce this, for me Brad was Carlos (RE3R), not Ark.


Capability to combine cuml.UMAP objects

Hi there,
Unlike the UMAP library, it seems that there is currently no way in the RAPIDS cuML library to combine UMAP objects using the mul, sub, or add operators (*,-,+). I was wondering if there was some workaround solution to this problem. I understand that this is not really a UMAP issue, but just wondering if someone could help here.

I think this is best put as a feature request to cuML. They have great developers working on their UMAP for GPU implementation, and I think that if you can show demand for the feature then there is a good chance it could get implemented.


Is StackNavigator broken on iOS?

There seems to be some serious issues with the transitions of the StackNavigator component. This is what i get with just the bare minimum code of stacknavigator and one component:

This is the same code on Expo sketch:
https://sketch.expo.io/rJ0V7rBnx
The issues i am getting (occasionally) are:

Header title is overlapping
Up to 1 second delay/freeze from tapping the link before the transition starts
Sometimes the transition freezes
Back button sometimes appear a second or less after the transition has finished

Anyone has any clue what this might be related to and how to fix this?

I saw the same issue

Any update on this? My app is now super laggy when we implemented this library. This library supposed to improve the animations performance.

Solving this is one of the main goals behind the new React Navigation library. The views in React Navigation use native components and the Animated library to deliver 60 FPS animations that are run on the native thread.

https://facebook.github.io/react-native/docs/performance.html#slow-navigator-transitions

Hi guys, I noticed this issue as well when I was running my app with the Chrome remote debugger attached and the debugger was in a background tab.
Things to try:

Make sure the debugger is in the foreground to make sure animations aren't slowed down
Disconnect the remote debugger entirely to see everything run at (almost) full speed
Disconnect the debugger and then run fully detached with a non-debug bundle to see everything run at full speed.

Putting the debugger in the foreground is often enough to make everything snappy again.

Probably related to this similar issue happening on Android: #706

Also experiencing slowness/issues with StackNavigator on iOS.
Delay between transitions.. Unable to interact with UI via touch for at least 2 seconds after swiping to go back. Working fine in my UWP app.

Two of the issues are already tracked in other issues:

Header title is overlapping

#229

Back button sometimes appear a second or less after the transition has finished

#1164

@gregblass It's only closed because we believed this issue is being tracked in the two issues above (#229 and #1164).
If you feel like those issues don't cover the problems you're seeing -- could you open up another issue? Perhaps with an actionable example of the issues you're experiencing?
We know that polish is important -- we're working on polishing animations, etc for 1.0.

Got it. I think there may be a third one here, but I'm not sure if its something I'm doing wrong or not optimally in my app - but for iOS using a stack navigator seems to have a significant delay. I'm trying to figure out if it may be due to react navigation or if I'm experiencing what is being described here? https://facebook.github.io/react-native/docs/performance.html#js-frame-rate-javascript-thread - The touchable highlight is also delayed on the flatlist item, for example.

Here's a good idea: I'll try out the react navigation playground and see if it seems fluid/native there. If so I've got to be doing something wrong/sub-optimally.

@gregblass There's almost certainly some bad animation going on -- the easing curves aren't quite right. But, you shouldn't witnessing dropped frames. Make sure that you're testing in prod mode, with no console.logs, etc.

No dropped frames at all. Just a pretty solid delay. I'm not sure if I'm in prod mode, so I'll check that.

So react navigation playground doesn't have any delays at all, its smooth as butter. I'm using expo so the app is set to production mode by default. I'll have to keep investigating/debugging - it may be being caused by combining the stack navigator with a larger FlatList.

This is essentially what I experience on iOS (much less severe on android/windows) - just plain delay between the interaction and the transitions/navigation

@Warpenguin You using a ListView/FlatList by any chance?

@gregblass No but I am doing something a bit unorthodox. I have 2 routes in my StackNavigator (Main and Dynamic) and I'm constantly navigating from Dynamic to Dynamic because I'm building the screen dynamically based on json prop values sent from a server.
I'm using redux and also I'm also hiding the header. The experience is fine on android. Just painfully noticeable on iOS.

Alright so its definitely being caused by a log FlatList component. If I cut my data down to two items and it fixed the delay. So my issue is not one with react navigation.

My issue was due to not using a React.PureComponent: https://github.com/facebook/react-native/issues/13649 - Also pretty clearly in the docs for FlatLists. Thank you @skevy

👍

Also I was running Expo in development like Noob Saibot. Don't do that if you're testing performance!

I'm still getting my back button disappearing for a split second randomly. I don't have any images on the screen either. I'll see if I can make a video.

@gregblass  I am using stack navigation its working fine in android but in IOS it behaving like just a back button. In my case, i am adding  a campaign and on save button it navigates to listview page where all campaigns are enlisted. It is navigating to listing page but newly added campaign is not listed there and in android it is listed. Please help.


[v0.9.0] --rootless should add all required kubelet args automatically

Describe the bug
Rootless mode should only require --rootless flag to be specified, but currently it also requires --kubelet-arg "cgroup-driver=none" --kubelet-arg "feature-gates=SupportNoneCgroupDriver=true" --kubelet-arg "cgroups-per-qos=false" --kubelet-arg "enforce-node-allocatable=" (https://github.com/rootless-containers/usernetes/blob/f745b0ff06b5b5c5bcd9035699cb31fb72465948/boot/kubelet.sh#L15)
To Reproduce
k3s server --rootless
(k3s version v0.9.0-rc2 (4a5360ea))
Expected behavior
k3s should automatically append all required kubelet args when --rootless is specified
Additional context
The issue happened because kubelet/cm: ignore cgroups error when running in userns commit (https://github.com/rancher/k3s/commit/bfb380670177a7647a3a153c0e5dcf5807db2a58) was replaced by kubelet: new feature gate: SupportNoneCgroupDriver commit (https://github.com/rancher/k3s/commit/8cef2e14c4fa86b46e4be31baea84c014ef53f67)

Thanks for the detailed info @AkihiroSuda, unfortunately at the moment I am having problems getting things to where kubelet is starting, am receiving an error like:
vagrant🐮k3s:/Users/erik/go/src/github.com/rancher/k3s$ ./dist/artifacts/k3s server --rootless --kubelet-arg "cgroup-driver=none" --kubelet-arg "feature-gates=SupportNoneCgroupDriver=true" --kubelet-arg "cgroups-per-qos=false" --kubelet-arg "enforce-node-allocatable="
open: No such file or directory
FATA[2019-10-18T13:37:03.728357864-07:00] failed to setup network &{binary:slirp4netns mtu:65520 ipnet:0xc00053bfb0 disableHostLoopback:true apiSocketPath:}: setting up tap tap0: executing [[nsenter -t 10499 -n -m -U --preserve-credentials ip tuntap add name tap0 mode tap] [nsenter -t 10499 -n -m -U --preserve-credentials ip link set tap0 up]]: exit status 1

I have an /etc/subuid & /etc/subgid setup like the following:
root:165536:65536
vagrant:165536:65536

This will probably need extra attention & docs @ShylajaDevadiga
PRs are welcome if it is an easy fix :)

Seems needs modprobe tun.
I tried to open PR, but could not compile the master..

Thanks for the info @AkihiroSuda. On alpine I needed to apk add shadow-uidmap and setup /etc/subuid & /etc/subgid as describe above. After a modprobe tun I was able to get a little bit further, but still seeing an error like:
open: Permission denied
FATA[2019-10-18T14:42:56.055281813-07:00] failed to setup network &{binary:slirp4netns mtu:65520 ipnet:0xc0010a3d40 disableHostLoopback:true apiSocketPath:}: setting up tap tap0: executing [[nsenter -t 11541 -n -m -U --preserve-credentials ip tuntap add name tap0 mode tap] [nsenter -t 11541 -n -m -U --preserve-credentials ip link set tap0 up]]: exit status 1

Running rootless as root got further, but still never to the point of starting the kubelet. :(
If you are in linux ./scripts/download && ./scripts/build && ./scripts/package-cli might help create the k3s executable in dist/artifacts, running git add ... && git commit -m 'wip' && make on a machine with docker will take awhile but should work. We are on go 1.13 now also. There is a Vagrantfile that I use on MacOS in this repo which will nfs mount in the directory so you can use an external editor for changing the code. If there is anything I can do to help with compiling stuff please let me know.
We will probably need to add back in the kubelet root directory configuration when running rootless:
diff --git a/pkg/agent/config/config.go b/pkg/agent/config/config.go
index 8bfb95ebdbe..407b410f9f0 100644
--- a/pkg/agent/config/config.go
+++ b/pkg/agent/config/config.go
@@ -348,6 +348,9 @@ func get(envInfo *cmds.Agent) (*config.Node, error) {
        nodeConfig.AgentConfig.KubeConfigNode = kubeconfigNode
        nodeConfig.AgentConfig.KubeConfigKubelet = kubeconfigKubelet
        nodeConfig.AgentConfig.KubeConfigKubeProxy = kubeconfigKubeproxy
+       if envInfo.Rootless {
+               nodeConfig.AgentConfig.RootDir = filepath.Join(envInfo.DataDir, "kubelet")
+       }
        nodeConfig.AgentConfig.PauseImage = envInfo.PauseImage
        nodeConfig.AgentConfig.IPSECPSK = controlConfig.IPSECPSK
        nodeConfig.AgentConfig.StrongSwanDir = filepath.Join(envInfo.DataDir, "strongswan")

chmod o=rw /host/dev/net/tun seems needed (https://github.com/docker/for-mac/issues/3838)
I'll open separate issues for building artifacts


MULS assembler code

Hi,
like i mentioned in chat there is bug in MULS assembler code, thats why its issue with tests, but actual code is correct.
Creating opcode takes registers in reverted order:
export function opcodeREV(Rd: number, Rn: number) {
  return (0b1011101000 << 6) | ((Rn & 0x7) << 3) | (Rd & 0x7);
}

and for MULS there is bug:
export function opcodeMULS(Rn: number, Rdm: number) {
  return (0b0100001101 << 6) | ((Rn & 7) << 3) | (Rdm & 7);
}

https://github.com/wokwi/rp2040js/blob/master/src/utils/assembler.ts#L130

Thanks for pointing this out!
If I understand correctly, the datasheet says that Rn comes first?
MULS{<q>} {<Rd>,} <Rn>, <Rm>

Obviously, there's something that I'm missing here, but I can't really tell what?

It should be like this:
export function opcodeMULS(Rdm: number, Rn: number) {
  return (0b0100001101 << 6) | ((Rn & 7) << 3) | (Rdm & 7);
}

Thanks!
If you feel like sending a pull request that will be awesome!


Language detection/switching fix

Hi,
I have run into into a bug where the redirect_to feature in page module  redirected the request to wrong language mutation of the particular page and the admin did not reflect to the change of FE language.
It was a side effect of unfunctional session lang code storage. The former implementation presumed that the LANGUAGE_SESSION_KEY and LANGUAGE_COOKIE_NAME have the same value. Which is not true anymore, at least for newer django versions (1.8.7, 1.9.5).
Currently LANGUAGE_SESSION_KEY = '_language' and  LANGUAGE_COOKIE_NAME = 'django_language').
The pull request contains the lang issue fix with some simple tests together with some deprecation warnings corrections.
Thanks.
Martin

Thanks! Will have to compare those changes with next.

@matthiask bump :see_no_evil:

Thanks for the bump :) I'm integrating your changes here:
https://github.com/matthiask/feincms/tree/next


gcc: amend FILE mangling patch to only affect -fmacro-prefix-map=

THe initial intent of the change was to only affect -fmacro-prefix-map= option.
Due to the bug of if (maps == macro_prefix_maps) condition of initial setting all three of:
static file_prefix_map *macro_prefix_maps; /* -fmacro-prefix-map  */
static file_prefix_map *debug_prefix_maps; /* -fdebug-prefix-map  */
static file_prefix_map *profile_prefix_maps; /* -fprofile-prefix-map  */

matches the comparison and applied the mangling (as long as on options were passed into those before).
As a result not only (intended) __FILE__ embedding happened in .data section, but also (unintended) debugging symbols (-fdebug-prefix-map) and profiling data (-fprofile-prefix-map) were broken by mangling.
The patch update fixes it by explicitly passing a boolean that controls the mangling in a single call site relevant to -fmacro-prefix-map.
While at it fixed int / size_t mismatch that caused build failure on upcoming gcc-14.
Tested as:

nix still has no nlohmann_json retention
gdb can now resolve stdc++ debugging symbols in templates
--coverage has working source file paths

Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

The message of the patch mentions debug symbols but as far as I understand this is now outdated.

Good catch! Dropped mention of debugging symbols.


Can no longer specify custom name for wheel based dependencies

Issue description
In the Pipfile you used to be able to set a custom name for the dependency you were installing from wheel.
example where you want to have a separate wheel for a different platform:
spacy-darwin = {file = "https://files.pythonhosted.org/packages/8a/2a/fe2870e216511ed12b9b5acf89228abc0c76832b9572501e0b895a9e129d/spacy-3.4.3-cp39-cp39-macosx_10_9_x86_64.whl", extras = ["transformers"], sys_platform = "== 'darwin'"}
spacy = {version = ">=3.4.1,<3.5.0", extras = ["transformers","cuda114"], sys_platform = "== 'linux'"}

The Pipfile.lock would then contain an entry for each item (spacy, spacy-darwin).
Expected result
I used to be able to expect the Pipfile.lock to contain an entry for both 'spacy-darwin' and 'spacy' with the sys_platform markers and correct hashes/files.
Actual result
Now only 'spacy' shows up in the lock file.
If you try having only one line in the Pipfile like this:
spacy-darwin = {file = "https://files.pythonhosted.org/packages/8a/2a/fe2870e216511ed12b9b5acf89228abc0c76832b9572501e0b895a9e129d/spacy-3.4.3-cp39-cp39-macosx_10_9_x86_64.whl", extras = ["transformers"], sys_platform = "== 'darwin'"}

it doesn't lock as 'spacy-darwin' but rather just 'spacy' it also doesn't include the sys_platform markers. Maybe this is correct behavior and what I'm trying to do isn't supposed to be supported...
Steps to replicate
Create a Pipfile with the above lines and attempt to create a lock file.

Pipenv version: '2023.2.4'
OS Name: 'posix'
User pip version: '22.3.1'
PEP 508 Information:
{'implementation_name': 'cpython',
 'implementation_version': '3.11.1',
 'os_name': 'posix',
 'platform_machine': 'x86_64',
 'platform_python_implementation': 'CPython',
 'platform_release': '22.1.0',
 'platform_system': 'Darwin',
 'platform_version': 'Darwin Kernel Version 22.1.0: Sun Oct  9 20:14:30 PDT '
                     '2022; root:xnu-8792.41.9~2/RELEASE_ARM64_T8103',
 'python_full_version': '3.11.1',
 'python_version': '3.11',
 'sys_platform': 'darwin'}

@elanou I think this has been the case for a long time, do you recall what version this last "worked" on?  I am not sure we can go back to supporting naming a package different than is expected for the lock file, but I think named package categories can accomplish what you want.   Basically create an alternate category for the other version of spacy that you want, maybe this category is called darwin ... but then you lock it on a darwin system and install that category on the relevant systems, and you'd probably want to pull the other spacy version out into a different separate category so it wouldn't conflict with the darwin  category.  Let me know if you have any follow-up questions.

if you h

Last know version was probably some time around August 2022 or shortly before. These named categories are a great feature and it seems like it should accomplish what I am trying to do. Thank you!


Update Vue3DraggableResizable.ts

add native drag support

This adds support for "Native drag and drop" - allowing drag and drop functionality from within the draggable window.


Add -N, --skip-nix flag for fastapi-mvc new command

Checklist:

[x] Added tests for changed code where applicable.
[x] Documentation reflects the changes where applicable.
[x] Updated the CHANGELOG.md file with your changes.
[x] My PR is ready to review.

Resolves: #123
Description of the changes being introduced by the pull request:

Codecov Report

Merging #124 (5170d71) into master (5ca924b) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master      #124   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           40        40
  Lines          800       800
=========================================
  Hits           800       800

Impacted Files
Coverage Δ

fastapi_mvc/generators/project/project.py
100.00% <ø> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us.


Arg name of command workbench.action.terminal.renameWithArg should allow variable substitution

The argument name of the command workbench.action.terminal.renameWithArg (introduced in #82105) does not allow variable substitution in the same way as commands like workbench.action.terminal.sendSequence with the arg text.
I think it should allow

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


1.1 .Net client release with OpenSearch 2.0 support

Acceptance criteria

[ ] All CI pass
[ ] OpenSearch 2.0 is fully supported
[ ] OpenSearch 1.x is fully supported
[ ] No breaking changes
[ ] Nuget packages are available for download and use

PR to complete

[ ] https://github.com/opensearch-project/opensearch-net/pull/51
[ ] https://github.com/opensearch-project/opensearch-net-abstractions/issues/16
[ ] https://github.com/opensearch-project/opensearch-net/issues/77
[ ] https://github.com/opensearch-project/opensearch-net/issues/80

Release Process
https://github.com/opensearch-project/opensearch-net/blob/main/RELEASING.md

[ ] Release branch created for 1.1 release
[ ] Release branch created for the next 1.x release

See also

[ ] https://github.com/opensearch-project/opensearch-net/issues/34
[x] https://github.com/opensearch-project/opensearch-net/issues/74
[ ] https://github.com/opensearch-project/opensearch-net/issues/79

Being that 1.0.0 of the .net client does not work with OpenSearch:

Is there a reason 2.0 isn't more appropriate than 1.1? I think it would eliminate some confusion.

It is supposed that next release of the client would have version 1.1. Anyway it will support OpenSearch 2.0. Please, see compatibility matrix in PR #51.
The client version is TBD actually, it could be released as 2.0.

@thespatt The logic is that, under semver principles, saying "2.0" means that this client breaks compatibility with 1.0. Instead, it only adds features, so it should be incrememted.
The day might come when a version of the client actually does become incompatible with current working application code. In that case we'd increment the major version as a signal that application builders need to do a heavier duty upgrade rather than just a version increment.

@Yury-Fridlyand @MaxKsyunz can you create a 1.1 branch with all commits for release?

@harshavamsi,
Done: 1.1.0

https://github.com/opensearch-project/opensearch-net/releases/tag/v1.1.0


Test to see if users find it clear what you need to register for

Summary
This issue came out of user testing:
"Lack of clarity for which things an account is or isn’t needed?"
For example, currently no registration is necessary to view stories, but registration is necessary to add stories. Some users therefore found it difficult to understand which actions required registration and which did not.
We've already got quite a few changes related to the user flow through the site, so it would be good to return to this later and decide whether it's still an issue after the changes.
What needs to be done?

[ ] Review clarity once the current front-end changes have been completed.

Who can help?

Anyone can please express their opinion on the matter.
If changes are needed design suggestions.
If changes are needed, implementation.

We have adapted the user flows accordingly, in the second round of user tests this did not seem to be a big issue anymore! 🚀


Unable to transcode EAC3 audio

I'm having trouble and I think I'm a bit out of my depths. Where is the configuration of the transcode pods held or defined? I'd liek to try some things to try and get the EasyAudioEncoder to work as it's trying to do things in /tmp on both the PMS instance and the transcode pods. It's not using /transcode for the audio.
For some context here are the errors in the plex console.
Job running: EAE_ROOT='/tmp/pms-d4a0cd44-31b5-42a2-8b7b-87235833786c/EasyAudioEncoder' FFMPEG_EXTERNAL_LIBS='/config/Library/Application\ Support/Plex\ Media\ Server/Codecs/99c90e0-3084-linux-x86_64/' XDG_CACHE_HOME='/config/Library/Application Support/Plex Media Server/Cache' XDG_DATA_HOME='/usr/lib/plexmediaserver/Resources' X_PLEX_TOKEN='xxxxxxxxxxxxxxxxxxxx' '/usr/lib/plexmediaserver/Plex Transcoder' '-codec:0' 'h264' '-codec:2' 'eac3_eae' '-eae_prefix:2' 'rnft5v12sq8x7ate39hmdnrz_' '-ss' '0' '-noaccurate_seek' '-analyzeduration' '20000000' '-probesize' '20000000' '-i' '/data/Video/TV/Show.mkv' '-filter_complex' '[0:2] aresample=async=1:ocl='\''stereo'\'':osr=48000[0]' '-map' '0:0' '-metadata:s:0' 'language=eng' '-codec:0' 'copy' '-map' '[0]' '-metadata:s:1' 'language=eng' '-codec:1' 'aac' '-b:1' '256k' '-f' 'dash' '-seg_duration' '5' '-init_seg_name' 'init-stream$RepresentationID$.m4s' '-media_seg_name' 'chunk-stream$RepresentationID$-$Number%05d$.m4s' '-window_size' '5' '-delete_removed' 'false' '-skip_to_segment' '1' '-time_delta' '0.0625' '-manifest_name' 'http://<IP_ADDRESS>:32400/video/:/transcode/session/rnft5v12sq8x7ate39hmdnrz/78be1816-19e6-4190-a0d7-f67eb0e7e87a/manifest?X-Plex-Http-Pipeline=infinite' '-avoid_negative_ts' 'disabled' '-map_metadata' '-1' '-map_chapters' '-1' 'dash' '-start_at_zero' '-copyts' '-vsync' 'cfr' '-y' '-nostats' '-loglevel' 'quiet' '-loglevel_plex' 'error' '-progressurl' 'http://<IP_ADDRESS>:32400/video/:/transcode/session/rnft5v12sq8x7ate39hmdnrz/78be1816-19e6-4190-a0d7-f67eb0e7e87a/progress'
and then
[Transcoder] [eac3_eae @ 0x1be8300] EAE watchfolder is not writable: /tmp/pms-d4a0cd44-31b5-42a2-8b7b-87235833786c/EasyAudioEncoder/Convert to WAV (to 8ch or less)/rnft5v12sq8x7ate39hmdnrz_1-0-test.tmp
I'm happy to hack at this on my own however I don't know where to begin.

Not sure if this is true, but this very old comment indicated that at one point in time EAE looked to be hardcoded to use /tmp - https://github.com/wnielson/Plex-Remote-Transcoder/blob/master/prt.py#L324

Try adding the environment variable TMPDIR to the container and point it to /transcode
From looking at some environment variables being used by Plex on a QNAP NAS, that is one of the one's they are setting and it does look like at least some things in PLEX will honor it.  Good Luck

I couldn't get the TMPDIR to work but forcing the /tmp to be mounted to the same pvc as the transcode did the trick for me.  Also had to edit the shim to spin up the transcode pod with the same /tmp being mapped to the transcode pvc and it works like a champ.

I couldn't get the TMPDIR to work but forcing the /tmp to be mounted to the same pvc as the transcode did the trick for me. Also had to edit the shim to spin up the transcode pod with the same /tmp being mapped to the transcode pvc and it works like a champ.

This is exactly what I was trying to do however I couldn't figure out how to hack it in. Still learning on how the shim part works and what/where to edit to tell it to use the Transcode PVC.

@typeon3g I can give you my compiled shim and the config i used to get the deployment and replica set up and running.  it might take a little tweeking to get right as i am using some distributed storage for my volumes but it should be pretty simple ifn you trust me ;)

The shim was easy to make a change to here is the diff:
--- a/main.go
+++ b/main.go
@@ -132,6 +132,10 @@ func generatePod(cwd string, env []string, args []string) *corev1.Pod {
                                                        Name:      "transcode",
                                                        MountPath: "/transcode",
                                                },
+                                               {
+                                                       Name:      "transcode",
+                                                       MountPath: "/tmp",
+                                               },
                                        },
                                },
                        },

Where my changes to the deployment.yaml are here.   I left the old copy of the kube-plex to /shared but i replaced the location to pull from to my downloads mount .  I am also including the UID and GID changes because why not.
--- a/charts/kube-plex/templates/deployment.yaml
+++ b/charts/kube-plex/templates/deployment.yaml
@@ -56,6 +56,7 @@ spec:
 {{- if .Values.kubePlex.enabled }}
         # We replace the PMS binary with a postStart hook to save having to
         # modify the default image entrypoint.
+        #        #cp /shared/kube-plex '/usr/lib/plexmediaserver/Plex Transcoder'
         lifecycle:
           postStart:
             exec:
@@ -66,7 +67,7 @@ spec:
                 #!/bin/bash
                 set -e
                 rm -f '/usr/lib/plexmediaserver/Plex Transcoder'
-                cp /shared/kube-plex '/usr/lib/plexmediaserver/Plex Transcoder'
+                cp /data/downloads/kube-plex '/usr/lib/plexmediaserver/Plex Transcoder'
 {{- end }}
         readinessProbe:
           httpGet:
@@ -88,6 +89,14 @@ spec:
           - name: https
             containerPort: 32443
         env:
+{{- if .Values.plex.uid }}
+        - name: PLEX_UID
+          value: "{{.Values.plex.uid}}"
+{{- end }}
+{{- if .Values.plex.gid }}
+        - name: PLEX_GID
+          value: "{{.Values.plex.gid}}"
+{{- end }}
         - name: TZ
           value: "{{ .Values.timezone }}"
         # TODO: move this to a secret?
@@ -98,6 +107,8 @@ spec:
           value: http://{{ template "fullname" . }}:32400
         - name: PMS_IMAGE
           value: "{{ .Values.image.repository }}:{{ .Values.image.tag }}"
+        - name: TMP
+          value: "/transcode"
         - name: KUBE_NAMESPACE
           valueFrom:
             fieldRef:
@@ -147,6 +158,8 @@ spec:
         {{ end }}
         - name: transcode
           mountPath: /transcode
+        - name: transcode
+          mountPath: /tmp
         {{- if .Values.persistence.transcode.subPath }}
           subPath: {{ .Values.persistence.transcode.subPath }}
         {{ end }}
@@ -163,6 +176,8 @@ spec:
 {{ toYaml .Values.nodeSelector | indent 8 }}
     {{- end }}
       volumes:
+      - name: tmp
+        emptyDir: {}
       - name: data
         persistentVolumeClaim:
 {{- if .Values.persistence.data.claimName }}


🐛 BUG: Account ID is not respected when applying migrations

Which Cloudflare product(s) does this pertain to?
D1
What version of Wrangler are you using?
2.15.1
What operating system are you using?
Linux
Describe the Bug
When using the wrangler CLI to apply migrations on a D1 database, I am prompted with the  More than one account available but unable to select one in non-interactive mode..
This does not occur when using wrangler publish from the same wrangler.toml and the worker is published correctly, however, running wrangler d1 migrations apply github-webhook results in the above prompt.
This is my wrangler.toml file:
name = "github-webhook"
main = "./src/index.ts"
compatibility_date = "2023-04-09"
node_compat = true
account_id = "<account id>"

[[ d1_databases ]]
binding = "DB"
database_name = "github-webhook"
database_id = "<database id>"
migrations_dir = "migrations"

[vars]

Hey @imconnorngl,
Sorry about this - you should be able to access a fix if you install wrangler@beta, otherwise it'll be available in the next wrangler release.


resolvedTrueType and resolvedFalseType of conditionType are not resolved when used in the compiler api

Bug Report

🔎 Search Terms
resolvedTrueType not resolved, resolvedTrueType not defined, conditionType not resolved
🕗 Version & Regression Information

I was unable to test this on prior versions because typescript version is not configurable in ts-morph.

⏯ Playground Link
https://codesandbox.io/s/charming-easley-27zik?file=/src/index.ts
💻 Code
import { createProjectSync, ts } from "@ts-morph/bootstrap";

const project = createProjectSync();
const mainFile = project.createSourceFile(
  "main.ts",
  `
    function f<A, B, C, D>() {
        return null as A extends B ? C : D;
      }
    `
);
const program = project.createProgram();
const typeChecker = program.getTypeChecker();
const func = mainFile.statements[0] as ts.FunctionDeclaration;
const signature = typeChecker.getSignatureFromDeclaration(func)!;
const returnType = typeChecker.getReturnTypeOfSignature(
  signature
) as ts.ConditionalType;

const isConditionalType = !!(returnType.flags & ts.TypeFlags.Conditional);
const checkType = !!returnType.checkType;
const extendsType = !!returnType.extendsType;
const resolvedTrueType = !!returnType.resolvedTrueType;
const resolvedFalseType = !!returnType.resolvedFalseType;

console.log({
  isConditionalType,
  resolvedTrueType,
  resolvedFalseType
});

🙁 Actual behavior
It outputs {isConditionalType: true, resolvedTrueType: false, resolvedFalseType: false}. But according to the public definition, both resolvedTrueType and resolvedFalseType should have been resovled.
export interface ConditionalType extends InstantiableType {
    root: ConditionalRoot;
    checkType: Type;
    extendsType: Type;
    resolvedTrueType: Type;
    resolvedFalseType: Type;
}

🙂 Expected behavior
It outputs {isConditionalType: true, resolvedTrueType: true, resolvedFalseType: true}.

I think those properties should have been written as optional. Changing them to optional currently produces no errors. I’d support changing them if someone opens a PR.

And expose getTrueTypeFromConditionalType/getFalseTypeFromConditionalType?

No, I think those are meant to be internal and their signature could change.

@andrewbranch I have a draft PR available that I believe fixes this issue, as per your suggestion above. Let me know whether you think this change is adequate.
#45838

@Zzzen, feel free to open a new issue requesting to expose getTrueTypeFromConditionalType/getFalseTypeFromConditionalType, I’m just not sure off the top of my head whether we’ll feel good about accepting it. But no harm in discussing.


Log management/Monitoring

Hi guys.
Problem: To check the logs of the failed command/task we had to go to the server and check it manually.
We do not have time to implement separate application which will help us to monitor our discord bot. Let's create a script with will export logs from db every day or on demand (ex. by command). We can add fancy charts to it for statistic purposes and send it through e-mail.
Feel free to express your opinions and ideas.
@mateusz2173 @Lorecrafter1590 @Hetorx
Thanks.

Another idea: Implement celery (async task queue) and combine it with Flower (celery monitoring tool).

https://www.loggly.com/ultimate-guide/centralizing-python-logs/

Is it paid, or am I mistaken?

Portainer.io :)


Asset paths not generated correctly for localhost external urls

Asset paths seems to be getting clobbered in some cases when localhost-type URLs are used.

cc @conectado


Running TinyYolov3 model crashes Unity

TinyYolov3 crashes Unity as soon as the scene starts. Looks like there's a problem with actually pulling the model from Hub.

This will be fixed in NatML 1.0.9.

We've archived @natsuite/tiny-yolo-v3.  Use @natsuite/yolox instead.


Build of app_extension target is not covered by test suite

The following changes would not be detected by the existing test suite:
1:
diff --git a/lib/pbxProject.js b/lib/pbxProject.js
index 0e0f8f9..5894d91 100644
--- a/lib/pbxProject.js
+++ b/lib/pbxProject.js
@@ -1466,19 +1466,6 @@ pbxProject.prototype.addTarget = function(name, type, subfolder) {
     // Target: Add to PBXNativeTarget section
     this.addToPbxNativeTargetSection(target)

-    // Product: Embed (only for "extension"-type targets)
-    if (targetType === 'app_extension') {
-
-        // Create CopyFiles phase in first target
-        this.addBuildPhase([], 'PBXCopyFilesBuildPhase', 'Copy Files', this.getFirstTarget().uuid,  targetType)
-
-        // Add product to CopyFiles phase
-        this.addToPbxCopyfilesBuildPhase(productFile)
-
-       // this.addBuildPhaseToTarget(newPhase.buildPhase, this.getFirstTarget().uuid)
-
-    };
-
     // Target: Add uuid to root project
     this.addToPbxProjectSection(target);

2:
diff --git a/lib/pbxProject.js b/lib/pbxProject.js
index 0e0f8f9..d7e65da 100644
--- a/lib/pbxProject.js
+++ b/lib/pbxProject.js
@@ -1555,7 +1555,7 @@ function pbxCopyFilesBuildPhaseObj(obj, folderType, subfolderPath, phaseName) {
      // Add additional properties for 'CopyFiles' build phase
     var DESTINATION_BY_TARGETTYPE = {
         application: 'wrapper',
-        app_extension: 'plugins',
+        app_extension: '',
         bundle: 'wrapper',
         command_line_tool: 'wrapper',
         dynamic_library: 'products_directory',

3:
diff --git a/lib/pbxProject.js b/lib/pbxProject.js
index 0e0f8f9..7301a16 100644
--- a/lib/pbxProject.js
+++ b/lib/pbxProject.js
@@ -1555,7 +1555,6 @@ function pbxCopyFilesBuildPhaseObj(obj, folderType, subfolderPath, phaseName) {
      // Add additional properties for 'CopyFiles' build phase
     var DESTINATION_BY_TARGETTYPE = {
         application: 'wrapper',
-        app_extension: 'plugins',
         bundle: 'wrapper',
         command_line_tool: 'wrapper',
         dynamic_library: 'products_directory',

I think the test coverage is needed to help ensure the functionality would not be broken by future changes.
Detected through mutation testing (PR #61) of watchkit2 updates (PR #56).

I believe I've covered this in https://github.com/apache/cordova-node-xcode/pull/66, but I haven't finished running Stryker on it yet.

I believe I've covered this in #66, but I haven't finished running Stryker on it yet.

Thanks again @l3ender for your help.
You can see in PR #66 that I did already check by hand that it does cover the possible changes discussed here.
I wouldn't worry too much about finishing the run on Stryker at this point. As I said in PR #63, Stryker takes a really, really long time if we don't use something like 16 CPUs worth of computing power.


Add check for correct config during MM connection

Also potentially correct the config if it is wrong such that it conforms with what calibration needs

When choosing the config group (after auto-populated when connecting to MM), this will check if the chosen config group has all of the required states.


activation: add Nix sanity check

This adds an empty nix-build command to verify that the user is having a good Nix install. It also, as a side effect, will create the necessary per-user profiles and gcroots directories.

For a pure check, there is nix doctor, but to prevent eventual errors, this looks better.

Yeah, perhaps nix doctor would work as well but unfortunately we cannot use the nix command anywhere because of its experimental status.


[Haxe] crash after completion canceled

fd_crash_after_completion_canceled_stack.txt
Haxe: 4.1.4
FD:  https://github.com/fdorg/flashdevelop/commit/31cda34fea58181edc4e0e3e2831c4428f85a30b
Sample project:
fd_crash_test.zip
The crash reproduces stably, every time I type '=' in line var picarr[i] = pic;.

will be fixed on sunday


Affiliation changes

This PR includes several affiliation changes for the website.
See also https://github.com/jupyter/governance/pull/120

This also needs updates on the https://github.com/jupyter/jupyter.github.io/blob/master/_includes/partners.html
Adding some new logos, right?

Btw, I also need to update my affiliation here...

Adding some new logos, right?

Done for me. @blink1073 - do you want to add a logo in this PR?

@blink1073 - do you want to add a logo in this PR?

Thanks, I added one

@jasongrout, I opened a PR against your branch with some more updates 😉  .

@jasongrout, I opened a PR against your branch with some more updates 😉 .

Thanks. I merged those in.

@willingc @rgbkrk @ivanov - Do you want to add a Noteable logo?

@parente - do you want to add a Thorn logo?

Moving to "ready for review" and merging. @willingc @rgbkrk @ivanov or @parente - if you want to add the logo for your employers, still please feel free to do on this PR or on a new one.

Thanks @jasongrout. Will add in a separate PR. Feel free to merge this.

@jasongrout I have a PR against your branch with an updated logo here: https://github.com/jasongrout/jupyter.github.io/pull/3
Thanks!!

Merged. Thanks everyone!


Wayland please!

Thank you for reading :)

I don't know anything about programming Wayland stuff, perhaps one day but probably not for awhile if I ever decide to port it. If you have any resources you could point me to where I could learn about how I might begin to implement something like this I'd be happy to take a look.

Soon:tm: :eyes:

pog

Still needs a lot of work, but here's it running in Sway
https://user-images.githubusercontent.com/32691832/156974311-8091c758-4fe0-48ab-ac40-94a8b9087ec2.mp4

oh nice. are you rewriting it in zig?

yeah, it'll be in a new repo once it's done. getting very close, at this point I'm just cleaning up code and fixing some minor issues I've come across. expect it in like a week at the longest assuming I don't discover some drastically horrible problem with my code.

Evidently I never got around to doing that, I got burnt out on it but I finally cleaned some stuff up and created a repo for it. Wayland backend still needs work, I won't make any promises this time on when that will get done, however.
https://github.com/BanchouBoo/bento


Remove Supported Functions onPageNav style

The page is right justified, which is inconsistent with other pages.
CC @ronkok

@ronkok Justification was a bad choice of the word, the page is shifted to the right.
Before:

After:

the page is shifted to the right.

Ah, I see now. Thank you for the screen shot. It should be possible to do something that both centers the page and allows a wider main container. I'll look into it and get back to you.

@ylemkimon I have two suggestions:

I agree that it would be a good idea to remove the onPageNav rule from the support_table.md page.
On the supported.md page, we can re-center the page by changing one line of code from flex: 0 0 200px; to flex: 1 0 200px;. That would center the page and also retain the slightly wider mainContainer that was my original motivation for the rule.

It looks a little weird for the highlight on the right sidebar to extend to the edge of the page.  I wonder if for really wide browsers we could have a max width for the content container (which contains all three columns) and then have margin: auto on it to centre it.

@ronkok There seems to be no onPageNav rule on the support_table.md. Also changing flex-grow to 1 still shifts the page a bit, which may be bad UX. If you think it's OK, I'll change it 😄

changing flex-grow to 1 still shifts the page a bit

You're right, now that I look closely. So your preference has a tiny benefit on a wide window and my preference has a tiny benefit on a small window. We're picking nits.
I don't feel strongly about this, so I'll let you choose. I'll approve this PR and you can either merge it or close it just as your prefer.

Codecov Report

Merging #1767 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1767   +/-   ##
=======================================
  Coverage   93.67%   93.67%
=======================================
  Files          80       80
  Lines        4666     4666
  Branches      813      813
=======================================
  Hits         4371     4371
  Misses        261      261
  Partials       34       34

Flag
Coverage Δ

#screenshotter
88.62% <ø> (ø)
:arrow_up:

#test
85.04% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 112582d...b6551a0. Read the comment docs.


When is it available in the stable version of rust?

Currently available in the nightly version. When will the stable version be available?
### Tasks

@alex @astraw @cuviper @adamgreig

I have no idea how you picked who to ping, but I'll give an answer from the release team perspective...
Once it's synced to the rust repo, like https://github.com/rust-lang/rust/pull/122905, you can see the milestone for which release it will reach. For the date, there's also a short schedule on the forge.

The std::simd submodule is still marked as unstable and as such not usable on stable rust. There is no ETA for when it will be stabilized. It will be stabilized once it is ready.

@dpaoliello  Currently available in the nightly version. When will the stable version be available?

As @bjorn3 said, there is no ETA on when it will be available in stable.  I'm closing this in favor of the tracking issue.

As @bjorn3 said, there is no ETA on when it will be available in stable. I'm closing this in favor of the tracking issue.

Thank you. I'm looking forward to this feature.


feat(#minor); CI/CD; Add capability to deploy only and add action to test builds on pushing to the remote branched in this repo.

Context:

There have been many instances where subgraphs fail to deploy upon merging into the master repository. This has often been due to build failing for various reasons at the time of merge. We wanted to add the capability to build only in the script, and test the builds on pushing to the repo before merging.
These changes will require an update to the deployment.js and execution.js files in the deployment folder, the creation of a new action, and updating the npm deploy script in each subgraph folder to include a new parameter for specifying the action (just building or deploying.)

Looking good! Eager to see it live :D
Left a few minor suggestions, and the comment about the action issue which might be the only really important thing

Amazing work!


Storage emulator (passes go test ./storage)

Hi @mcardosos, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

@mcardosos This is amazing thank you. If we ever get Windows Containers on Travis-CI or AppVeyor some day, we can install Azure SDK to get the Storage Emulator and just run our tests on Windows without a need for a storage account! That'd be very amazing.

@mcardosos, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, MSBOT;

@mcardosos I see that you work for Azure. You do not need to sign the cla. Just log in at http://aka.ms/azuregithub with your Github & Org accounts for the next time you send PRs to /Azure repos.

@mcardosos why did you choose to export the dev credentials as consts? Do other sdks do that as well?

Also maybe could you add some test cases on client_tests.go to see if the client is getting constructed successfully (and other code paths you added take effect on the client)?

@ahmetalpbalkan I exported them so users can use Storage Emulator without having to look for / copy and paste the account and key form here https://azure.microsoft.com/en-us/documentation/articles/storage-use-emulator/#authenticating-requests-against-the-storage-emulator
I don't know if all SDKs do this. PHP and Node have them as consts, but it looks like those are used just for tests.

@mcardosos sorry for the latency on this pull request. it slipped off my mind, I am merging now.


Compile Error

I'm new to Less. I've got this error when compiling less :
/Library/Ruby/Gems/1.8/gems/less-2.0.8/bin/lessc:3:in 'require': no such file to load -- less ( Load error ) from /Library/Ruby/Gems/1.8/gems/less-2.0.8/bin/lessc:3
how to fix that ?
Thanks

Seems like it's not installed properly? This is the javascript repo by the way, the ruby version is at:
https://github.com/cowboyd/less.rb
Cheers


feat: Initial approach to support nexus integration

Note - I used very layman terminology in the code to make it more understandable although the code is very straightforward. Open for the naming convention change 😜

[ ] Test case (Will start once I got sufficient approval on the approach).
[ ] Linting fixes

Coverage decreased (-3.9%) to 90.532% when pulling 368f1cce9f3381969254ae11351a05f50bfac43b on feature-nexus-mutual-support into f01c51ad4f26bd1dea2b46f0e6c2c86210612f86 on main.


Command failed when launching kernel

If I try to run a new kernel I get the followng error

Command failed: . /home/ajasja/.conda/envs/pyro_scripts/bin/activate && conda activate pyro_scripts && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python /mnt/home/ajasja/.vscode-server-insiders/extensions/ms-python.python-2021.3.597396665-dev/pythonFiles/pyvsc-run-isolated.py /mnt/home/ajasja/.vscode-server-insiders/extensions/ms-python.python-2021.3.597396665-dev/pythonFiles/printEnvVariables.py
CommandNotFoundError: Your shell has not been properly configured to use 'conda activate'.
If your shell is Bash or a Bourne variant, enable conda for the current user with
$ echo ". /software/miniconda3/etc/profile.d/conda.sh" >> ~/.bashrc

or, for all users, enable conda with
$ sudo ln -s /software/miniconda3/etc/profile.d/conda.sh /etc/profile.d/conda.sh

The options above will permanently enable the 'conda' command, but they do NOT
put conda's base (root) environment on PATH.  To do so, run
$ conda activate

in your terminal, or to put the base environment on PATH permanently, run
$ echo "conda activate" >> ~/.bashrc

Previous to conda 4.4, the recommended way to activate conda was to modify PATH in
your ~/.bashrc file.  You should manually remove the line that looks like
export PATH="/software/miniconda3/bin:$PATH"

^^^ The above line should NO LONGER be in your ~/.bashrc file! ^^^

However the command works if run from the terminal (and used to work a few days ago)

Environment data

VS Code version: 1.54-insiders (59c31364...)
Jupyter Extension version (available under the Extensions sidebar): v2021.3.593162453
Python Extension version (available under the Extensions sidebar): v2021.3.597396665-dev
OS (Windows | Mac | Linux distro) and version: Windows/remote linux
Python and/or Anaconda version: 3.5
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): Conda
Jupyter server running: Remote

Expected behaviour
Launch kernel
Actual behaviour
Error ocours
Steps to reproduce:
Try to run cell
Logs

Output for Jupyter in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Jupyter)

XXX

Thanks! Anything I can do as a workaround? Currently I run the server from the command line and then connect to it.

@ajasja, we're looking into the problem.  We'll let you know as soon as we have more info.  In the meantime, please provide the content of the "Python" output panel, along with your settings.json.  Thanks!

Hmm, now (after an automatic update) I'm getting this error and can't even open the new notebook editor.

The original error is still present in the python log though (https://gist.github.com/ajasja/af36fd3c1e41bf018975f55fd221f154). I'm also attaching the jupyter output (https://gist.github.com/ajasja/77ca1671b4028c8c12b3150f9bbba59c)
Here are the user settings: https://gist.github.com/ajasja/97418e87e86d39a3e95ceb4c428ca803
Insiders updated Version: 1.55.0-insider (user setup)
Commit: 11d5e82c80c6151e3f6d9da10429582b589c16ba
Jupyter: v2021.4.641214696
Python: v2021.4.640901529-dev
PS: I open the *.ipynb in the old notebook, the kernel is launched correctly.

Also, this seems to be a remote issue, locally the notebook is working fine.

Hi @ajasja,
I can't reproduce the issue you're facing. If the problem is still happening for you, could you provide clear repro steps? That would be very helpful 🙂 If you have a notebook with which you can replicate the issue it would be great if you could share it too!
Thank you!

Hi @kimadeline ,
Thanks for getting back to me.
This is definitely still happening, but only when using remoteSSH (which I use for 99% of the work).
Steps to reproduce:

Connect to Remote SSH (using a recently saved link)

Try to open a notebook in the preview editor

Here are the Python, Jupyter & RemoteSSH  outputs.
Old notebook interface works:

@greazer who provides support for the preview editor, the Python extension, the Jupyter extension or VS Code?

If you think this could be due to some strange settings, I'm happy to nuke my installation & install fresh.


[MM-12984] remove 'with' from strings

Summary
remove text "with SAML" and keep only "SAML"
Ticket Link
Jira: https://mattermost.atlassian.net/browse/MM-12984
Checklist

[x] Ran make check-style to check for style errors (required for all pull requests)
[x] Ran make test to ensure unit and component tests passed
[x] Includes text changes and localization file (.../i18n/en.json) updates

Server PR: https://github.com/mattermost/mattermost-server/pull/9827

merging


[WFLY-17858] IIOP: make sure registering attributes performs capabili…

…ties check
https://issues.redhat.com/browse/WFLY-17858

Thanks @tadamski


MM-37999

Hello y'all. :wave:
Kept it pretty basic. I also attempted to add a third test wherein a private playbook is created and the test validates that it is not shown to a non-member, but I was having some trouble with API 403s and left it out for now. I used playbook_list_permissions_spec.js for guidance, but I noticed that test actually fails similarly when run. If that DOES seem like a good test to have, let me know and I dig a bit more around that.
Summary

adds a new spec for Playbooks Home

Ticket Link
https://mattermost.atlassian.net/browse/MM-37999
Checklist
- [ ] Telemetry updated
- [ ] Gated by experimental feature flag
- [ ] Unit tests updated

Hello @Phrynobatrachus,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

Thanks, @Phrynobatrachus! I've asked @saturninoabril and @crspeller to take a look :)

Thanks for participating in Hacktoberfest! You can claim your sticker set here: https://get.printfection.com/hacktober21/4144583267 @Phrynobatrachus


[FEATURE] v2 volume supports auto salvage

Is your feature request related to a problem? Please describe (👍 if you like this request)

Describe the solution you'd like

Describe alternatives you've considered

Additional context

Some discussions
https://suse.slack.com/archives/C02DR3N5T24/p1713926457976349

See data consistency in https://github.com/longhorn/longhorn/pull/7031

Verified pass on longhorn v1.8.0-dev(https://github.com/longhorn/longhorn-manager/commit/a503949c751f8bb07d9835f3680b93d5bc807e30)
Test steps:

Dynamic provision a v2 volume, having data in the mount point.
Set auto-salvage to false
Force delete all v2 volume instance-manager pod.
V2 volume become faulted and remains in that state.
Set auto-salvage to true
The faulted v2 volume become healthy and data in the workload is correct.
Force delete all v2 volume instance-manager pod again.
V2 olume become faulted then healthy again.
After volume healthy, data in workload correct.

In v1.7.2, set auto-salvage to true and force delete all v2 volume instance-manager pod, the v2 volume will loop from faulted -> attaching -> faulted.


Number command

Can you add feature: if write 'vo ', sound volume becomes level .  from 0 to 100.
 Thanks for update


Assisted Edits

Was editing with a small group of developers and they thought it would be possible to create a computer 'assisted edit'. Where a client side algorithm quickly detects building corners from a single click or draws sections of roads by identifying end points.  This would not be automated extraction but rather a method to speed up editing.
Has this or a similar approach been discussed? I couldn't find any open or closed issue on the topic.

I think @tmcw wrote something about this a while ago, but I can't find it now.
This is a tricky problem because the background imagery may not have the right cross-origin headers set, and without that, you can't access the image pixels in client code.  That doesn't mean that assisted editing is impossible, just that there's an extra security hurdle to clear before code running in the iD window can access imagery pixel data.
See this stackoverflow post for more info.
Would love to see someone tackle this problem in a plugin, if we end up building a real plugin architecture into iD.

Thanks for the response @bhousel . I'll bring up the CORS issues with the team and get their take on it. Since Bing hosts the image tiles we might be able to exert some influence on that. Assisted editing might work better as a JOSM plugin, we'll do some more investigation and let you know how it turns out.


Cannot trigger Celery task when I add sentry in settings.py (django)

How do you use Sentry?
Sentry Saas (sentry.io)
Version
1.40.3
Steps to Reproduce

Create celery task in the django
Trigger the endpoint that containt the celery task
Error show up

Expected Result
No error
Actual Result
[2024-02-09 18:46:15,606: ERROR/MainProcess] Process 'ForkPoolWorker-4' pid:3944 exited with 'signal 11 (SIGSEGV)'
[2024-02-09 18:46:15,766: ERROR/MainProcess] Task handler raised error: WorkerLostError('Worker exited prematurely: signal 11 (SIGSEGV) Job: 0.')
Traceback (most recent call last):
  File "/Users/amzar/Documents/python_env/xxx/lib/python3.11/site-packages/billiard/pool.py", line 1264, in mark_as_worker_lost
    raise WorkerLostError(
billiard.einfo.ExceptionWithTraceback:
"""
Traceback (most recent call last):
  File "/Users/amzar/Documents/python_env/xxx/lib/python3.11/site-packages/billiard/pool.py", line 1264, in mark_as_worker_lost
    raise WorkerLostError(
billiard.exceptions.WorkerLostError: Worker exited prematurely: signal 11 (SIGSEGV) Job: 0.
"""

Hey @amzar96, thanks for the report.
Does this still happen when you downgrade the SDK to version 1.39.2? Does it happen if you leave the SDK out of the mix completely, i.e., when you do not call sentry_sdk.init at all?

@sentrivana
I realized the error only occurred after hitting the Celery task for the first time the celery worker ran. After I made the next hit to the Celery task, it worked as expected.
Till now not sure what is caused

@sentrivana
Not yet try to downgrade the SDK. I will try it later.


Added typeof prefix in conditional.

Adds typeof in string property conditional check.
Fixes #1581

[ ] Documented (Code comments, README, etc.)
[ ] Tested (unit, integration, etc.)

Codecov Report
Patch coverage: 100.00% and project coverage change: +1.14% :tada:

Comparison is base (b18e13a) 78.26% compared to head (e813bfb) 79.41%.

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

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1582      +/-   ##
==========================================
+ Coverage   78.26%   79.41%   +1.14%
==========================================
  Files          32       19      -13
  Lines        2627     2079     -548
  Branches      545      443     -102
==========================================
- Hits         2056     1651     -405
+ Misses        405      297     -108
+ Partials      166      131      -35

Files Changed
Coverage Δ

packages/relay/src/lib/eth.ts
85.41% <100.00%> (+0.11%)
:arrow_up:

... and 14 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


@angular_devkit/core New workspace API usage in schematics

The new workspace api from @angular_devkit/core take a virtualFs.Host as a parameters; eg:
const host = workspaces.createWorkspaceHost(new NodeJsSyncHost());
But how do you actually use it in a schematics Rule ? In a Rule, we only have a Tree.
This is confusing, this post say that it's usable in schematics: https://blog.angular.io/version-8-of-angular-smaller-bundles-cli-apis-and-alignment-with-the-ecosystem-af0261112a27
"Previously developers using Schematics had to manually open and modify their angular.json to make changes to the workspace configuration. With 8.0, we’re introducing a new API to make it easier to read and modify this file."

Okay got it
https://github.com/angular/angular-cli/blob/c319cd054e4344737e274af41f46ef4d8a1c3aab/packages/schematics/angular/utility/workspace.ts#L11
This function should be exposed

It's currently a private API.  A comprehensive schematics utility and rule library is currently in the design phase to provide functionality such as this and more.
While you could deep import the functions, they may change or be removed.  It would be safer to temporarily vendor the code within your schematics project for now.


Remove meetup & tweet widgets from certain pages

I think the content for the Blog and the Resources pages should be the focus, and not need the Meetup and Tweets widgets, and can take up the full size of the page (length-wise).

fixed


Documentation feedback - non-technical user

Background
I installed the kit on a Macbook Air first, then after tried installing on a PC. Both already had github desktop and git bash installed on them. The Macbook installation was 100% successful, and I pushed a test app to heroku and also github. The PC one got as far as the Heroku toolbelt, but I don't have CMD access on that machine so that was the end of it at least as far as publishing.
As a non-technical person there were one or two points along the way where I had questions or doubts, which I have noted below in the spirit of making suggestions to help with the documentation.
Feedback
https://github.com/alphagov/govuk_prototype_kit/blob/master/docs/guides/setting-up-git.md - would be good to include here the link to installing git bash. I appreciate it's in the separate installation guide, but as the page is "Setting up git" it would make sense to include here too - especially if you don't quite follow the correct order or are exploring the pages.
https://github.com/alphagov/govuk_prototype_kit/blob/master/docs/guides/publishing-on-heroku.md - I missed the part about Windows software compatibility, the very first callout, so later on was scratching my head wondering why I kept getting an error when trying to push to heroku. Could this info be included under step 2 about installing the toolbelt? In my case CMD is locked down on the PC so I couldn't complete the heroku setup.
https://github.com/alphagov/govuk_prototype_kit/blob/master/docs/guides/publishing-on-heroku.md - step 3, at this point I wondered "does the project folder have to have the same name as this app name?". I suspect not, but chose to call it the same anyway so it would always be crystal clear. This also relates to the point below about not quite getting "how and where" the app name is stored
https://github.com/alphagov/govuk_prototype_kit/blob/master/docs/guides/publishing-on-heroku.md - step 3/4: having successfully set everything up on a macbook, I thought I'd try to do the same on a PC to mimic two people collaborating. My question at this point was: do I need to do this 'create an app' step again, presumably not? But where is the name of the app actually stored, and at what point does the second machine get it - presume this must be stored in git and synced from heroku?
Related to this - I googled info on how to push to both github.com and heroku, as:

I wasn't quite clear about how heroku collaboration works (though as it's using git I expect its identical to what I know from github),
We normally use github for sharing code so I wanted to stick with that.
I've chosen to just do separate push commands for now, as it seems more transparent and controllable. I did see that you can hook heroku up to github to deploy automatically, but was concerned by having to grant access to both public and private repositories.

Suggestion on these points: add a guide on code collaboration options for newbies. The guides are currently focused on setting up a new repo etc from scratch and not how to hook into an existing one.
https://github.com/alphagov/govuk_prototype_kit/blob/master/docs/guides/publishing-on-heroku.md - now I've successfully pushed one test app to heroku, and pushed the code to github, I noted this line "You can have multiple apps running on Heroku - projects often have several so they can try different ideas out at once.". A short explanation of that would help for someone like me. I'm presuming I load a particular branch and deploy that with a particular app name. A brief how-to might help for 1. Those using github, and 2. Those only using Heroku

@markbarlow Hi Mark, thanks for this feedback.
Could you expand on the point about Windows compatibility and Heroku? I'm not a Windows user so I'm not aware of the issue.

Hi @sanjaypoyzer - sure, on https://github.com/alphagov/govuk_prototype_kit/blob/master/docs/guides/publishing-on-heroku.md the very first sentence says "These don't currently work on Windows due to a software incompatability. The Heroku toolbelt is not compatible with Git Bash - you will need to use CMD instead.". I missed this first of all so went ahead and downloaded the toolbelt and tried to use it via Git Bash (I don't have CMD access on the PC in question). My suggestion here was just to move or duplicate that message under step 2

Also, could you expand on what you were trying to do when you say "mimic two people collaborating"? The collaboration happens via Git (and GitHub) and is synced up to Heroku when people push to the master branch, so what might be helpful here is a link to a more in depth Git tutorial.
On that note as well, if you could provide links to the other guides that were useful that would be great. If there's a specific point in them that we should include in the documentation, then great, but for some things it might be better to just link to them.

Hi Sanjay - as far as mimicing two people collaborating, I was thinking about collaborating with git and an organisation account on github. Two or more separate people working on the same prototype. At the time of writing I was new to heroku so didn't initially appreciate it offers much of the same collaboration concepts. However, as github is our default code repo, and has more granular collaboration (from what I can tell - teams, ease of visibility, public/private etc), it makes more sense to us to stick to that.
Fair to say that things started to make more sense once I had:
a. Done the git command line tutorial which is already linked (and gave me a wider understanding, having previously mainly used the github desktop client)
b. Properly understood the difference between git and github/heroku
c. Started slowly weening myself off the github desktop app....

@markbarlow Cool, glad to hear you got it all sorted in the end. Is there any other specific things you think need to be added/changed to the guidance that would have helped you?

Think that's all for now @sanjaypoyzer - thanks