[Bug]: Alternate receive worker message passing hangs for nil return

Description
$subject
Steps to Reproduce
import ballerina/io;

public function main() {
    boolean foo =  true;
    worker w1 {
        if (foo) {
            () -> w2;
        } else {
            () -> w2;
        }
    }

    worker w2 {
        ()|error v = <- w1| w1;
        io:println(v);
    }
    wait w2;
}

Affected Version(s)
https://github.com/ballerina-platform/ballerina-lang/tree/worker_change
OS, DB, other environment details and versions
No response
Related area
-> Runtime
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

This is now available in 2201.9.0.


Add Win+Space to the Shortcut Guide

Add the PowerToys Run shortcut to the PowerToys 'Shortcut Guide' display

When the Shortcut Guide is displayed on the screen, the [Space] key shortcut which launches the PowerToys Run dialog is not shown.

@saahmedm the proposal to mention "PowerToys Run" is not mentioned at #179 at this time. Since people install both PowerToys Run and Shortcut Guide at the same time it would make sense they will want to be informed of the shortcut availability.


[Bug Report] el-input (decorated by v-model.number) can't input number like -0.xxx

Element UI version
2.4.7
OS/Browsers version
windows 10 / Chrome 68.0.3440.84
Vue version
2.5.17
Reproduction Link
https://jsfiddle.net/goforward01/4jhmburs/1/
Steps to reproduce
input a number like -0.0001
What is Expected?
appear to be -0.0001
What is actually happening?
turn out to be 0.0001

Duplicate of #11885


Initializing files for retrospectives.

Addresses Issue #28

@bouzaghrane and @hassanobeid1994:
Let me know if you two are okay with the idea of doing weekly retrospectives (10 min/wk)!


services/horizon/internal/docs: Use full links instead of relative links.

PR Checklist
PR Structure

[ ] This PR has reasonably narrow scope (if not, break it down into smaller PRs).
[ ] This PR avoids mixing refactoring changes with feature changes (split into two PRs
otherwise).
[ ] This PR's title starts with name of package that is most changed in the PR, ex.
services/friendbot, or all or doc if the changes are broad or impact many
packages.

Thoroughness

[ ] This PR adds tests for the most critical parts of the new functionality or fixes.
[ ] I've updated any docs (developer docs, .md
files, etc... affected by this change). Take a look in the docs folder for a given service,
like this one.

Release planning

[ ] I've updated the relevant CHANGELOG (here for Horizon) if
needed with deprecations, added features, breaking changes, and DB schema changes.
[ ] I've decided if this PR requires a new major/minor version according to
semver, or if it's mainly a patch change. The PR is targeted at the next
release branch if it's not a patch change.

What
Use full URL for some links.
Why
Some of the fixed links don't work today in the production docs and also fixes some links added in https://github.com/stellar/go/pull/1887
Known limitations
N/A

Hey! There's a couple of reasons we've been using relative links:

It decouples the docs from the deployment domain (i.e. we aren't hard-coding developers.stellar.org everywhere)
It allows the doc links to work when viewed on Github.

I do agree that some of the links were broken (this is my bad, I promised to fix them and didn't). But this could be resolved by just changing the relative path.
What do you think? My preference is to use relative links and just fix the paths, unless there are other pros to the full paths that I didn't surface here.

@ire-and-curses I agree with you, I prefer relative links rather than full links. Actually we might not need this change, we thought using ../../../guides will break under /developers but I just tested one of the links in  master using this schema and it works. So it's all good!
I'll open a different PR to fix the broken links to XDR.


debugRepaintRainbow not showing what is being rebuilt and leads to false conclusions

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce
The dartpad.dev examples for the counter app with Riverpod, Provider and Bloc all are built in a way that only the number gets rebuilt when the counter is updated, yet the repaint rainbow suggests, that the whole app is being rebuilt.
Simply adding debugRepaintRainbowEnabled = true;  and  import 'package:flutter/rendering.dart'; to any of the three examples:
https://dartpad.dev/?id=a133148221a8cbacbcef8bc77a6c82ec
https://dartpad.dev/?id=ef06ab3ce0b822e6cc5db0575248e6e2
https://dartpad.dev/?id=fdd369962f4ff6700a83c8a540fd6c4c
And optionally a print statement to the topmost and bottom most widget to check what is being rebuilt.
Expected results
The repaint rainbow highlights only the number in the example as this is what is being rebuilt.
Actual results
It appears like the whole screen is being rebuilt, when in fact it is not. This is a problem since we can't do a visual inspection of rebuilding of widgets and have to resort to print debugging, which is less than ideal and difficult to teach to people new to the framework.
The question asked by people not familiar with Flutter is: "If the repaint rainbow shows everything is being repainted, why should I care for making granular rebuilds" - this is an argument I would like to avoid.
I believe this is related to https://github.com/flutter/flutter/issues/11601 which I believe didn't get properly addressed.
Code sample
Code sample
// Copyright (c) 2018, the Dart project authors.  Please see the AUTHORS file
// for details. All rights reserved. Use of this source code is governed by a
// BSD-style license that can be found in the LICENSE file.

import 'package:flutter/material.dart';
import 'package:flutter_riverpod/flutter_riverpod.dart';
import 'package:flutter/rendering.dart';

// This is a reimplementation of the default Flutter application
// using riverpod.
void main() {
  debugRepaintRainbowEnabled = true;
  runApp(
    // Adding ProviderScope enables Riverpod for the entire project
    const ProviderScope(child: MyApp()),
  );
}

/// Providers are declared globally and specify how to create a state
final counterProvider = StateProvider((ref) => 0);

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      theme: ThemeData(
        colorSchemeSeed: Colors.blue,
        useMaterial3: true,
      ),
      home: const MyHomePage(),
    );
  }
}

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

  @override
  Widget build(BuildContext context, WidgetRef ref) {
    print('building MyHomePage');
    return Scaffold(
      appBar: AppBar(
        title: const Text('Riverpod example'),
      ),
      body: Center(
        child: Column(
          mainAxisSize: MainAxisSize.min,
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            const Text('You have pushed the button this many times:'),
            Consumer(
              builder: (context, ref, _) {
                print('building Consumer');
                final count = ref.watch(counterProvider);
                return Text(
                  '$count',
                  key: const Key('counterState'),
                  style: Theme.of(context).textTheme.headlineMedium,
                );
              },
            ),
          ],
        ),
      ),
      floatingActionButton: FloatingActionButton(
        key: const Key('increment_floatingActionButton'),
        // The read method is a utility to read a provider without listening to it
        onPressed: () => ref.read(counterProvider.notifier).state++,
        tooltip: 'Increment',
        child: const Icon(Icons.add),
      ),
    );
  }
}

Screenshots or Video

Screenshots / Video demonstration

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
[Paste your output here]

Thanks for the report.  Running on latest versions, below log is shown in the console upon incrementing counter:
I/flutter (19694): building Consumer
D/EGL_emulation(19694): app_time_stats: avg=73.42ms min=3.13ms max=2433.04ms count=37
I/flutter (19694): building Consumer
I/flutter (19694): building Consumer
D/EGL_emulation(19694): app_time_stats: avg=22.02ms min=2.14ms max=622.17ms count=36
I/flutter (19694): building Consumer
D/EGL_emulation(19694): app_time_stats: avg=18.80ms min=4.00ms max=320.63ms count=39
D/EGL_emulation(19694): app_time_stats: avg=23.33ms min=2.90ms max=627.72ms count=33
I/flutter (19694): building Consumer

 stable, master flutter doctor -v
[!] Flutter (Channel stable, 3.13.2, on macOS 12.2.1 21D62 darwin-x64, locale
    en-GB)
    • Flutter version 3.13.2 on channel stable at
      /Users/dhs/documents/fluttersdk/flutter
    ! Warning: `flutter` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/flutter, which is not inside
      your current Flutter SDK checkout at
      /Users/dhs/documents/fluttersdk/flutter. Consider adding
      /Users/dhs/documents/fluttersdk/flutter/bin to the front of your path.
    ! Warning: `dart` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/dart, which is not inside your
      current Flutter SDK checkout at /Users/dhs/documents/fluttersdk/flutter.
      Consider adding /Users/dhs/documents/fluttersdk/flutter/bin to the front
      of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision ff5b5b5fa6 (7 days ago), 2023-08-24 08:12:28 -0500
    • Engine revision b20183e040
    • Dart version 3.1.0
    • DevTools version 2.25.0
    • If those were intentional, you can disregard the above warnings; however
      it is recommended to use "git" directly to perform update checks and
      upgrades.

[!] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! Flutter recommends a minimum Xcode version of 13.
      Download the latest version or update via the Mac App Store.
    • CocoaPods version 1.11.2

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

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

[✓] Connected device (5 available)
    • SM G975F (mobile)       • RZ8M802WY0X • android-arm64   • Android 11 (API 30)
    • Darshan's iphone (mobile)  • 21150b119064aecc249dfcfe05e259197461ce23 •
      ios            • iOS 14.4.1 18D61
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 98.0.4758.80

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

! Doctor found issues in 1 category.

[!] Flutter (Channel master, 3.14.0-14.0.pre.212, on macOS 12.2.1 21D62
    darwin-x64, locale en-GB)
    • Flutter version 3.14.0-14.0.pre.212 on channel master at
      /Users/dhs/documents/fluttersdk/flutter
    ! Warning: `flutter` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/flutter, which is not inside
      your current Flutter SDK checkout at
      /Users/dhs/documents/fluttersdk/flutter. Consider adding
      /Users/dhs/documents/fluttersdk/flutter/bin to the front of your path.
    ! Warning: `dart` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/dart, which is not inside your
      current Flutter SDK checkout at /Users/dhs/documents/fluttersdk/flutter.
      Consider adding /Users/dhs/documents/fluttersdk/flutter/bin to the front
      of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision ffe1ebd207 (67 minutes ago), 2023-09-11 03:46:15 -0400
    • Engine revision 1aa11b6448
    • Dart version 3.2.0 (build 3.2.0-134.0.dev)
    • DevTools version 2.27.0
    • 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 30.0.3)
    • Android SDK at /Users/dhs/Library/Android/sdk
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for
      more details.

[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 13C100
    • CocoaPods version 1.11.2

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

[✓] IntelliJ IDEA Ultimate Edition (version 2021.3.2)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 65.1.4
    • Dart plugin version 213.7228

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

[✓] Connected device (3 available)
    • Darshan's iphone (mobile) • 21150b119064aecc249dfcfe05e259197461ce23 • ios
      • iOS 15.3.1 19D52
    • macOS (desktop)           • macos                                    •
      darwin-x64     • macOS 12.2.1 21D62 darwin-x64
    • Chrome (web)              • chrome                                   •
      web-javascript • Google Chrome 109.0.5414.119

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

! Doctor found issues in 1 category.

[!] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! Flutter recommends a minimum Xcode version of 13.
      Download the latest version or update via the Mac App Store.
    • CocoaPods version 1.11.2

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

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

[✓] Connected device (5 available)
    • SM G975F (mobile)       • RZ8M802WY0X • android-arm64   • Android 11 (API 30)
    • Darshan's iphone (mobile)  • 21150b119064aecc249dfcfe05e259197461ce23 •
      ios            • iOS 14.4.1 18D61
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 98.0.4758.80

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

! Doctor found issues in 1 category.

This sounds like it is working as intended, the debugRepaintRainbowEnabled setting highlights what was repainted, not what was rebuild. It's likly that in this example you only have one layer so the whole screen gets repainted.


stage1: investigate xhyve-based stage1

The xhyve hypervisor is a port of bhyve to OS X. It is built on top of Hypervisor.framework in OS X 10.10 Yosemite and higher, runs entirely in userspace, and has no other dependencies. It can run vanilla Linux distributions and may gain support for other guest operating systems in the future.

It would be interesting to explore the feasibility of creating an xhyve-based stage1, which could potentially allow rkt to run on OS X systems. This would likely be heavily derivative of the incoming lkvm stage1.
https://github.com/mist64/xhyve
http://www.pagetable.com/?p=831

Also relevant: https://github.com/coreos/coreos-xhyve

:heart_eyes: great idea! hope it will make to the roadmap

The core rkt developers don't have any plans to add this to the roadmap but we've very happily accept a contribution.

If there would be any interested in this developer - I'm open to share experience gathered in process of mentioned adding lkvm based stage1.


Compiling using a FileContext does not produce an output file.

The following does not produce the expected output file:
    URI inputFile = new File("src/main/resources/in.scss").toURI();
    URI outputFile = new File("src/main/resources/out.css").toURI();

    Compiler compiler = new Compiler();
    Options options = new Options();

    try {
        FileContext context = new FileContext(inputFile, outputFile, options);
        Output output = compiler.compile(context);

        out.println(output.getCss());
    }
    catch (CompilationException e) {
        err.println("Compile failed");
        err.println(e.getErrorText());
    }

It does successfully compile in.scss but does not create out.css.

I am encountering this behavior as well.


Line between prev and next post cuts through comments

Thanks for the report, this one is intentional. ;)

Intentional and... unique. So be it :)


Missing calls to parent __{parent}_init fns when using multiple inheritance

According to the documentation here, __{contract}_init calls should make calls to their parent __{parent}_init fns, but in many contracts they don't.
e.g.
     function __ERC4626_init(IERC20MetadataUpgradeable asset_) internal onlyInitializing {
         __ERC4626_init_unchained(asset_);
   >>>     __ERC20_init(asset_.name(), asset_.symbol()); >>> this here is missing
     }

💻 Environment
Any env
Here is the example source: https://github.com/OpenZeppelin/openzeppelin-contracts-upgradeable/blob/master/contracts/token/ERC20/extensions/ERC4626Upgradeable.sol#L36
Here is a PR that fixes it https://github.com/OpenZeppelin/openzeppelin-contracts-upgradeable/pull/171

Hello @vminkov
First of all, the  __XXX__init function are automatically generated during the transpilation workflow. This is an automated process that is triggered every time there is a new commit on the master branch of the non upgradable contracts. As a consequence this kind of change should not be done with PR targeting the master branch, but by modifying the transpiler. This is why I closed your PR.
Now about the logic behind this situation.
In the non upgradable library, some contracts have constructors, and some contract inherit from parents without specifying the parent constructor. This is, for example the case of ERC20 extensions (they usually don't include the ERC20 parameters). This is also the case of some other contract such as EIP712.
When you build a contract with these extensions, you'll have to call the different constructors. Just go to the wizard and try to generate a simple ERC20Votes to see that it depends on ERC20Permit and ERC20, which both need constructor arguments.
We don't want the extensions to pass argument to initialize the core, because that would be an instant mess multiple extensions are used together.
The __XXX__init follow the same logic, because they are "just" a translation of the constructor. when building an upgradable contract, you need to make sure you call all the one needed. This can indeed be a pain, as the compiler won't help you, but again, the wizard can help. From out previous example, just select "Upgradeability" and you'll the the initialize() function do all that.
Last but not least, the fix your propose is actually wrong. What you are doing is using the name and symbol of the underlying asset for the vault itself. That means that if an upgradeable vault is based on Dai, then its name and symbol would match Dai? That would be really confusing for users.


Theme doesn't work with a Melodrama generated presentation

All I did was change the below line in the generated presentation
import createTheme from 'spectacle/lib/themes/default';

to
import createTheme from 'spectacle-theme-nova';

Here's the error from my browser console

Please update your melodrama-scripts to 2.1.0. Should be fixed 🙃

J4I spectacle-theme-nova/bundle still worked.
The reason why this theme didn't work with melodrama anymore was due to the fact that most of the node_modules is excluded since 2.0.0. This improved speed and solves an issue with babel-standalone that is included in spectacle since 2.0.0..

spectacle-theme-nova/bundle worked as you mentioned.
I just tried spectacle-theme-nova with 2.1.0 and it still throws an error as below.

Can you please provide steps to reproduce? I just created a new presentation with melodrama + spectacle-theme-nova without any issues. Only thing I changed:
- import createTheme from 'spectacle/lib/themes/default';
+ import createTheme from 'spectacle-theme-nova';

{
  "name": "presentation-example",
  "version": "1.0.0",
  "private": true,
  "devDependencies": {
    "melodrama-scripts": "2.1.0"
  },
  "readme": "README.md",
  "scripts": {
    "start": "melodrama-scripts start index.js",
    "build": "melodrama-scripts build index.js"
  },
  "dependencies": {
    "prismjs": "1.6.0",
    "react": "15.5.4",
    "react-dom": "15.5.4",
    "spectacle": "2.1.0",
    "spectacle-theme-nova": "1.3.0"
  }
}

Are you importing other libs?


Large Solutions are restored in batches

Our Solution has more than 400 Projects, which means that the CLI argument is larger than Windows can handle. This patch batches the command.
I was not able to test it, as I did not get the Installer Package up and Running on Visual Studio 2017. If someone can provide me a VSIX I will also gladly test it.

Found the VIX as an artifact of the proof build

Works just lovely! Please pull it in if it suites your requirements


Error on adding datasource to Grafana v7.2.2

During the 'add a datasource' step, after selecting this plugin, the next screen shows the following:
An unexpected error happened
DetailsError: Minified React error #130; visit https://reactjs.org/docs/error-decoder.html?invariant=130&args[]=undefined&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings.

    in Unknown
    in div
    in t
    in form
    in div
    in div
    in t
    in div
    in div
    in div
    in t
    in t
    in div
    in t
    in t
    in x
    in ConnectWithCleanUp(Connect(t))
    in r
    in Unknown
    in t
    in Unknown
    in h
    in Unknown
    in Unknown
    in t
    in t
    in l

Hi, the error you're getting is a generic error for when the plugin requires features from more recent versions of Grafana. This currently only supports Grafana >=7.3.0.

Hi, the error you're getting is a generic error for when the plugin requires features from more recent versions of Grafana. This currently only supports Grafana >=7.3.0.

To clarify this plugin needs Grafana >=7.3.0?

Ok thanks! sorry for the delay in responding, story got backlogged.


creating license

Added license. License reflects:

Correct copyright year
Attribution to appropriate community

@ryanlovett is this ok with you? :)


Adds JOSM Remote Control link

This PR adds a one-click link to open the selected Strava layer in JOSM, via the remote control functionality. This only loads the imagery for the current session, and will not make the imagery appear in JOSM's Imagery menu.
I messed around a bunch with the way the URL is constructed internally, and am more than happy to make changes to this PR if there's a less-disruptive way to achieve the same result, and to incorporate feedback for better UX.

Good call.  Probably best to have both the copy option and the remote control link available.

Would it be a good idea to shrink the current URL block to a single line with a scrollbar?

Maybe?  I displayed the full url in a block sort of as a confirmation that it had been properly generated and also as a fallback, so if the automatic copy failed you could easily select the text and copy it.  This may be totally unnecessary, but I figured I'd be pretty annoyed if the clipboard code stopped working for some reason and there wasn't a way for me to just select and copy the url manually.  It does take up a lot of space, but on the other hand there isn't too much else competing for space even with a few new buttons added.
If you're feeling like trying out some additional UI tweaks I can leave this PR open.  If not, I'll go ahead and merge it.


Correction for raw affiliation University of Calgary, Calgary, AB, CA

Correction needed for raw affiliation University of Calgary, Calgary, AB, CA
raw_affiliation_name: University of Calgary, Calgary, AB, CA
new_rors: 03yjb2x39
previous_rors:
works_examples: W2073786882;W2063912758;W2053167494;W2295684505;W1524987922;W2027077751;W2514663557;W2588724899;W2564673760;W2964337071;W2766496403;W2737070158;W2963527269;W2796863645;W2898719454;W2896338174;W2901288125;W2887363292;W2893461580;W2893859502;W2841973364;W2945162082;W2910293723;W4386041932;W4386041718
contact: 9f59742b84611ea8e0e15cbda6fa2eb9:3359145a @ ourresearch.org

This issue was accepted and ingested by the OpenAlex team on 2024-10-09. The new affiliations should be visible within the next 7 days.


[Bug] doris-2.0.1 partial_columns update  error

Search before asking

[X] I had searched in the issues and found no similar issues.

Version
doris：2.0.1
spark connector：spark-doris-connector-3.2_2.12
What's Wrong?
there is a error when I use partial_columns update :Partial update should include all key columns, missing: end_sys_imp_date

What You Expected?
partial_columns were updated successfully
It can be successful using csv and stream load way
How to Reproduce?
No response
Anything Else?
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Can you post the spark configuration?


State maintains the start position and length (in bits) of every element in the infoset

Have a parse that would read the richer infoset representation that exposes this information for use by the GUI opposed to dumping the xml

This could be an extra data view in the data editor that shows the current bit location of the parser in addition to the way it currently shows the current byte.
Alternatively, this information could be added to the output infoset with each item added. This would pollute the data file with extra information that would prevent any attempt to unparse, but could help diagnose issues with the schema not having the correct bit length/position.


Platformmanager tests

I think all these changes were already in the other PR.

true. this was not by indent. uuups


Daligner illegal option -D

tool: pb-assembly
command: fc_run
Hi,
I am using Falcon (v0.2.3) from pb-assembly. Although I did not specify the -D option in the pa_hpcdaligner or ovlp_hpcdaligner steps, I keep getting this error regarding this being an illegal option.
+ which HPC.daligner
HPC.daligner -P. -e.75 -l1000 -k18 -h70 -s100 -v -D24 -mtan -mrep0 -mdust -H$CUTOFF -fdaligner-jobs raw_reads >| run_jobs.sh
+ HPC.daligner -P. -e.75 -l1000 -k18 -h70 -s100 -v -D24 -mtan -mrep0 -mdust -H31694 -fdaligner-jobs raw_reads
HPC.daligner: -D is an illegal option
[WARNING]Call 'bash -vex split_db.sh' returned 256.

Here is the tail of the log file:

[INFO](slept for another 0.4s -- another 3 loop iterations)
[ERROR]Task Node(0-rawreads/daligner-split) failed with exit-code=1
[ERROR]Some tasks are recently_done but not satisfied: set([Node(0-rawreads/daligner-split)])
[ERROR]ready: set([])
	submitted: set([])
[ERROR]Noop. We cannot kill blocked threads.
Traceback (most recent call last):
  File "/home/gd98309/.conda/envs/falconda/bin/fc_run", line 11, in <module>
    load_entry_point('falcon-kit==1.2.3', 'console_scripts', 'fc_run')()
  File "/home/gd98309/.conda/envs/falconda/lib/python2.7/site-packages/falcon_kit/mains/run1.py", line 726, in main
    main1(argv[0], args.config, args.logger)
  File "/home/gd98309/.conda/envs/falconda/lib/python2.7/site-packages/falcon_kit/mains/run1.py", line 76, in main1
    input_fofn_fn=input_fofn_fn,
  File "/home/gd98309/.conda/envs/falconda/lib/python2.7/site-packages/falcon_kit/mains/run1.py", line 301, in run
    daligner_split_script=pype_tasks.TASK_DB_DALIGNER_SPLIT_SCRIPT,
  File "/home/gd98309/.conda/envs/falconda/lib/python2.7/site-packages/falcon_kit/mains/run1.py", line 539, in add_daligner_and_merge_tasks
    dist=Dist(NPROC=4, MB=4000, job_dict=daligner_job_config),
  File "/home/gd98309/.conda/envs/falconda/lib/python2.7/site-packages/falcon_kit/pype.py", line 106, in gen_parallel_tasks
    wf.refreshTargets()
  File "/home/gd98309/.conda/envs/falconda/lib/python2.7/site-packages/pypeflow/simple_pwatcher_bridge.py", line 277, in refreshTargets
    self._refreshTargets(updateFreq, exitOnFailure)
  File "/home/gd98309/.conda/envs/falconda/lib/python2.7/site-packages/pypeflow/simple_pwatcher_bridge.py", line 361, in _refreshTargets
    raise Exception(msg)
Exception: Some tasks are recently_done but not satisfied: set([Node(0-rawreads/daligner-split)])

Any thoughts on why is that happening?

Here is my full config file:
[General]
# list of files of the initial bas.h5 files
input_fofn = input.fofn

input_type = raw

genome_size = 14200000
seed_coverage = 30.0
length_cutoff = -1

falcon_sense_greedy = False

pa_dbsplit_option = -x500 -s200 -a
falcon_sense_option = --output_multi --min_idt 0.70 --min_cov 4 --max_n_read 200 --n_core 6
overlap_filtering_setting = --max_diff 60 --max_cov 100 --min_cov 4 --bestn 10 --n_core 4
length_cutoff_pr = 500
ovlp_dbsplit_option = -x500 -s200 -a

pa_daligner_option   = -e.75 -l1000 -k18 -h70 -s100
pa_hpcdaligner_option = -v -B128 -M24

ovlp_daligner_option = -h35 -e.93 -l1000 -s100 -k25
ovlp_hpcdaligner_option = -v -B128 -M24

[job.defaults]
job_type = local

# use_tmpdir = /lscratch
pwatcher_type = blocking
job_type = string
submit = bash -C ${CMD} >| ${STDOUT_FILE} 2>| ${STDERR_FILE}

NPROC = 28
njobs = 1
MB = 8000
[job.step.da]
[job.step.pda]
[job.step.la]
[job.step.pla]
[job.step.cns]
[job.step.asm]

Did you install FALCON and it's associated dependencies each manually in Bioconda? There is a newer version - 0.2.4 available but I don't think that's the issue here.
Or did you install the pb-assembly recipe to ensure all of your dependency versions resolve correctly?

$ conda install pb-falcon

I suspect you need to update your daligner/dazzler binaries

Hi greg, I installed the pb-assembly recipe through Bioconda
The weird thing is that I have used this installations successfully before. But after I modified my config file I get this -D error.
I could try to do a new installation but I agree that that is probably not the issue.

What i noticed is the config file config.json and General.json are the ones with the line
"ovlp_HPCdaligner_option": "-v -D24 -l500"
Does this help?

Hi @dbtara, I noticed that too. However, these files are generated from my config file (plus hardcoded defaults I imagine). So this -D option must somehow be implicit in my config settings.
I have since changed my config file substantially and I no longer see this error, I don't know exactly what change did the trick though.


Spring: Cannot configure Segment name in BaseAbstractXRayInterceptor

Hi,
I'm manually instrumenting my fairly large Spring application.
Why are you not adding the Class name to the sub-segment name?
It's quite frustrating to not have the class name in the UI when looking at the traces.
I would suggest changing:
https://github.com/aws/aws-xray-sdk-java/blob/d66d69a0eb5ab1d1dae2fc1b6a14608ac3781b13/aws-xray-recorder-sdk-spring/src/main/java/com/amazonaws/xray/spring/aop/BaseAbstractXRayInterceptor.java#L48
to
    Subsegment subsegment = AWSXRay.beginSubsegment(subsegmentNameFromSignature(pjp.getSignature()));

so that the user can override the subsegment name.

I ended up rolling my own abstract class and removed the aws-xray-recorder-sdk-spring dep. It's more of an example than a library at this point, no offense.

Hi @stnor - thanks for filing these issues. It sounds like you are adding tracing to a new app. Did you by any chance take a look at our support for OpenTelemetry?
https://aws-otel.github.io/docs/getting-started/java-sdk
It has far more features and can provide a better experience than XRay sdk for new apps. There is a Java agent that can automatically instrument and/or ability to manually instrument by creating spans.
Our effort is mostly focused on OpenTelemetry going forward so we probably wouldn't be able to make changes for improving the experience here, though we would fix any bugs though

Thanks, good to know.
The app is huge and 10 years old at this point.
I’m thinking of migrating from AppDynamics, which it usung -javaagent. And
looking at the open telemetry support st present, it does not look
production ready?
For instance, no supporr for lowering sample rates from 100%?
On Sun, 2 May 2021 at 04:12, Anuraag Agrawal @.***>
wrote:

Hi @stnor https://github.com/stnor - thanks for filing these issues. It
sounds like you are adding tracing to a new app. Did you by any chance take
a look at our support for OpenTelemetry?
https://aws-otel.github.io/docs/getting-started/java-sdk
It has far more features and can provide a better experience than XRay sdk
for new apps. There is a Java agent that can automatically instrument
and/or ability to manually instrument by creating spans.
Our effort is mostly focused on OpenTelemetry going forward so we probably
wouldn't be able to make changes for improving the experience here, though
we would fix any bugs though
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aws/aws-xray-sdk-java/issues/281#issuecomment-830727649,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEJAD6LISXYGCS3ZO572MTTLSYKHANCNFSM435BSENQ
.

@stnor While it hasn't quite hit GA yet it can be used in production and a few folks are doing so.
While X-Ray centralized sampling isn't currently supported unfortunately, the sampling rate can be tweaked with a flag (traceidratio).
https://github.com/open-telemetry/opentelemetry-java/tree/main/sdk-extensions/autoconfigure#sampler

Thanks, I'll check it out!
On Sun, 2 May 2021 at 09:59, Anuraag Agrawal @.***>
wrote:

@stnor https://github.com/stnor While it hasn't quite hit GA yet it can
be used in production and a few folks are doing so.
While X-Ray centralized sampling isn't currently supported unfortunately,
the sampling rate can be tweaked with a flag (traceidratio).
https://github.com/open-telemetry/opentelemetry-java/tree/main/sdk-extensions/autoconfigure#sampler
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aws/aws-xray-sdk-java/issues/281#issuecomment-830767941,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEJAD67CIHMTPNVUF6KJO3TLUA7HANCNFSM435BSENQ
.

I've gotten the otel stuff to work decently well now... However I do not understand how to compliment the -javaagent's standard logging with my own Spring AOP aspects.
I think the right approach would be to create nested spans?
It's unclear to me how I get hold of the parent span  like in the Xray Java SDK. Annotating all methods with a custom annotation is not an option.
I've looked here: https://opentelemetry.io/docs/java/manual_instrumentation/ and it doesn't really cover my use-case.
Some issue referred to ```OpenTelemetrySdk. getTracerProvider()`` but that class doesnät seem to exist anymore?
Any pointers or help would be highly appreciated.

I'm using the bom for 1.1.0:
    <dependencyManagement>
        <dependencies>
            <dependency>
                <groupId>io.opentelemetry</groupId>
                <artifactId>opentelemetry-bom</artifactId>
                <version>1.1.0</version>
                <type>pom</type>
                <scope>import</scope>
            </dependency>
        </dependencies>
    </dependencyManagement>

Also found https://github.com/open-telemetry/opentelemetry-java/issues/3035

Sorry for the spam.
This code is being executed, but does nothing (that shows in Xray).
(1) Is it "correct"?
(2) Why doesn't it do anything in Xray?
public abstract class AbstractSpringOtelInterceptor {

    private static final Log logger = LogFactory.getLog(AbstractSpringOtelInterceptor.class);
    private Tracer tracer = OpenTelemetrySdk.builder().build().getTracer("se.nomp");

    protected Object processXRayTrace(ProceedingJoinPoint pjp) throws Throwable {
        Span span = tracer.spanBuilder(generateSubsegmentName(pjp)).startSpan();

        try(Scope scope = span.makeCurrent()) {
            return conditionalProceed(pjp);
        } finally {
            span.end();
        }
    }

    protected String generateSubsegmentName(ProceedingJoinPoint pjp) {
        return "Hello " + pjp.getSignature().getDeclaringType().getSimpleName() + "." + pjp.getSignature().getName();
    }

    public static Object conditionalProceed(ProceedingJoinPoint pjp) throws Throwable {
        return pjp.getArgs().length == 0 ? pjp.proceed() : pjp.proceed(pjp.getArgs());
    }
}

-javaagent:/Users/stnor/devel/src/nomp/web/docker/opt/aws-opentelemetry-agent-1.1.0.jar
-Dotel.resource.attributes=service.name=Nomp
-Dotel.instrumentation.jdbc-datasource.enabled=true
-Dotel.traces.sampler.traceidratio=true
-Dotel.traces.sampler.arg=1

Hey @stnor - just to confirm you are using the aws distro if the Java agent and a collector configured for x-ray? Are you seeing the agent's spans, but just not seeing yours?
To get a tracer when using the agent, you need to use GlobalOpenTelemetry.get() to get the instance of OpenTelemetry managed by the agent.
Other than that, your first snippet (which correctly implicitly parents to the current span) looks good.

Thanks @anuraaga - that solved it!
I also had issues getting the aws-otel-collector to work since it did not pick up my credentials. had to do:
git clone https://github.com/aws-observability/aws-otel-collector.git ; \
    cd aws-otel-collector; \
    docker run --rm -p 4317:4317 -p 55680:55680 -p 8889:8888 \
      -e AWS_REGION=xxxx-e AWS_ACCESS_KEY_ID=xxxx -e AWS_SECRET_ACCESS_KEY=xxxx \
      -v "${PWD}/examples/docker/config-test.yaml":/otel-local-config.yaml \
      --name awscollector public.ecr.aws/aws-observability/aws-otel-collector:latest \
     --config otel-local-config.yaml;

Here's the proof :) Thanks again.

Nice trace!
If you found anything, always happy for more ideas on improving instrumentation at https://github.com/open-telemetry/opentelemetry-java-instrumentation/. Instrumentation for hikaricp seems like it could be nice for us to offer natively.

Ah and I've always had the idea of injecting OpenTelemetry into the spring context which I don't think we do right now. So you could use @Inject instead of GlobalOpenTelemetry.get. In the meantime you should probably do so in your app to make sure the actual tracers can (relatively) easily work if you decide to not use the agent in the future for any reason, you'd just replace the bean with an instance of OpenTelemetrySdk you build yourself.

I'm attaching my code here if anyone else would like to instrument att their services and repos.
One needs to edit the within(se.nomp..*) to your package in the ^@Pointcut:s and also chance the INSTRUMENTATION_APP_PACKAGE in AbstractSpringOtelInterceptor
spring-service-repo-aspects.zip


Fix kubectl --server-dry-run argument for kubectl v1.17

Why is this PR needed?
Current Kubernetes cluster version: 1.17.4
Latest Kubernetes version: 1.17.13

Addon upgrades for 1.17.4:
  - cilium: 1.6.6 -> 1.6.6-rev5
  - dex: 2.16.0 -> 2.16.0-rev6
  - gangway: 3.1.0-rev4 (manifest version from 5 to 6)
Error: invalid argument "server" for "--dry-run" flag: strconv.ParseBool: parsing "server": invalid syntax
See 'kubectl apply --help' for usage.

There is no argument "--dry-run=server" for kubectl in version 1.17, instead of this we can use "--server-dry-run"
What does this PR do?
It is replacing "--dry-run=server" on "--server-dry-run"
Anything else a reviewer needs to know?
Special test cases, manual steps, links to resources or anything else that could be helpful to the reviewer.
Info for QA
This is info for QA so that they can validate this. This is mandatory if this PR fixes a bug.
If this is a new feature, a good description in "What does this PR do" may be enough.
Related info
Info that can be relevant for QA:

link to other PRs that should be merged together
link to packages that should be released together
upstream issues

Status BEFORE applying the patch
How can we reproduce the issue? How can we see this issue? Please provide the steps and the prove
this issue is not fixed.
Status AFTER applying the patch
How can we validate this issue is fixed? Please provide the steps and the prove this issue is fixed.
Docs
If docs need to be updated, please add a link to a PR to https://github.com/SUSE/doc-caasp.
At the time of creating the issue, this PR can be work in progress (set its title to [WIP]),
but the documentation needs to be finalized before the PR can be merged.
Merge restrictions
(Please do not edit this)
We are in v4-maintenance phase, so we will restrict what can be merged to prevent unexpected surprises:
What can be merged (merge criteria):
    2 approvals:
        1 developer: code is fine
        1 QA: QA is fine
    there is a PR for updating documentation (or a statement that this is not needed)

Fix was already merged in https://github.com/SUSE/skuba/pull/1462


Need Proxy

Our Jenkins is running after the protection of Nginx Basic Auth. So I need to add a proxy server that supports the Basic Auth, and I have set the IDEA's HTTP proxy and tested the connection. But this plus can never use the proxy(I don't see the trace in the monitor of the proxy server ).
Request:

the way to use a global proxy.
or add function to use proxy.

Can you please test with following eap:
https://plugins.jetbrains.com/plugin/6110-jenkins-control/versions/eap/263516
I added proxy usage of intellij proxy settings

Hi
can you please use latest version (0.13.16)
it will be use the proxy settings from IntelliJ

This is my solution:
Use the Charles to rewrite the Basic Auth, which I found in my web Request.
I haven't tested your solution, Because I don't know how to start a proxy server myself without a special tool.

Have you tried the intellij proxy settings?
this should be used
but i can check the days

I have basic job listing working on 0.13.16-2021.2 but for example trying to Show last log fails with a red tooltip status code 407, reason phrase: Proxy Authentication Required.
Looks like usage of proxy auth is not very consistent. Luckily I don't need proxy for that url and No proxy for was obeyed once I fixed it.

I check if I missed one proxy usage

I reproduced it and fix it
thanks for that

Can you please try following: https://plugins.jetbrains.com/plugin/6110-jenkins-control/versions/eap/293869

new build with improved redirect handling: https://plugins.jetbrains.com/plugin/6110-jenkins-control/versions/eap/296705

released with 0.13.17


Allow extending Lang

Currently shortcutStylePatterns / fallthroughStylePatterns is internal, this doesnt allow extending with our own language without adding it here, is it intentional?

Hi , It would be available in the next version !

https://github.com/Qawaz/compose-code-editor/blob/e39e55502258dc2f76b891b3ee1fbf5096f62de2/demo/common/src/commonMain/kotlin/com/wakaztahir/common/DisplayCodeEditor.kt#L122


cargo clean -p only cleans the build for a version with zero arguments

Given a clean checkout of foo:
cargo clean -p foo
cargo rustc -p foo -- -Zverbose

cargo clean -p foo
cargo rustc -p foo -- -Zverbose

Only the first cargo rustc will actually build. But if you change the argument to -Z verbose the second time, it will build (but only once). My hypothesis (which @alexcrichton confirmed) is that each generates a distinct fingerprint, and cargo clean -p foo is looking for a version with no arguments.
I would expect it rather to clean all builds related to foo with any arguments.

Hitting this when compiling for a different target:
$ cargo run -v --target i686-unknown-linux-gnu
$ cargo clean -vv -p usize
(nothing is cleaned)
$ cargo run -v --target i686-unknown-linux-gnu
...
Fresh usize v0.1.0 (file:///home/xftroxgpx/build/2nonpkgs/rust.stuff/rustlearnage/usize)
...
$ cargo clean -vv -p usize --target i686-unknown-linux-gnu
    Removing /home/xftroxgpx/build/2nonpkgs/rust.stuff/rustlearnage/target/i686-unknown-linux-gnu/debug/usize
    Removing /home/xftroxgpx/build/2nonpkgs/rust.stuff/rustlearnage/target/i686-unknown-linux-gnu/debug/.fingerprint/usize-d5bf39b5c2514907
    Removing /home/xftroxgpx/build/2nonpkgs/rust.stuff/rustlearnage/target/i686-unknown-linux-gnu/debug/deps/usize-d5bf39b5c2514907

Used https://github.com/rust-lang/cargo/pull/5059 to show Removed files.
OP clearly explains the issue, thanks!

Under-compiling is dangerous. Let's try and fix this issue.


No Connection after OB

@atmotraxx commented on Mon Aug 06 2018
Brief Description:
Chrome says ERR_NAME_NOT_RESOLVE after (sometimes while) using OB
Operating System:  Windows 10 Home
OpenBazaar version:  2.2.3 / 0.12.2
Hardware: Samsung Laptop (tested on two different machines 32Bit, 64Bit)
Reproducible:
Always
Steps to reproduce:

Open OB2
Do something
Close OB2

Observed Behavior:
After using OB no more WLAN/LAN DNS resolution: Chrome says ERR_NAME_NOT_RESOLVE
It does not matter if it is a wired connection or wifi(wlan).
Expected Behavior:
All Internet connectivity should be untouched and working
Additonal:
Even after a restart the connection problems are present. My solution is: restart laptop, power off/on router
Kind regards
Erik

@atmotraxx Can I assume you're using the bundled installation and have not customized your configuration in any way? Do you use any firewall infrastructure that you've disabled during your test? Our server shouldn't be doing anything to manipulate your network routing or DNS settings. It's possible something on your network is seeing unusual traffic created by our server and might be employing some "protection" on your computer. Routers and network appliances may also employ these filters or protection. Any of these things ring a bell for you? You might try running your test in a different physical setting (like an internet cafe) to see if the problem persists there.

This happens to me when MDNS is turned on, but we turn it off by default. Have you changed any MDNS settings in the config file?

thanks for your replies.
Yes, its the bundled windows installatiobn. i didn't change anything like MDNS.
i figured out that the problems do not occur when using OB through tor. So i'm ok with it.
But i will check that MDNS an firewall stuff
Keep on gooing OB! I really like the concept!
Kind regards
Erik

🍻 Let us know if you'd like to troubleshoot your case further.


Wormhole Bridge Assistance - ETH side retrieval

Hello!
I transferred UST from Solana to ETH, but my UST is now stuck on the in-between contract (my MetaMask never popped with a transaction confirmation). Can I please receive the VAA bytes to write to the wormhole contract and retrieve my funds on the ETH side? Thank you!
Transaction: https://explorer.solana.com/tx/5JQdRT9TD5KrjEP2SQTpGQkN17oigm7JcxXvW8WqFJGUsErz6Udmm8tDUq6BxYrmRSAauK27t2PJWVMDk74ijDdt

mine stuck in-between as well but the transaction failed. Do you have any idea what to do with that ?

mine stuck in-between as well but the transaction failed. Do you have any idea what to do with that ?

Unfortunately I do not, sorry about that.


Use babel-plugin-preval instead of own unicodeMake for unicodeSymbols

Codecov Report

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

@@           Coverage Diff           @@
##           master    #2153   +/-   ##
=======================================
  Coverage   94.89%   94.89%
=======================================
  Files          81       81
  Lines        5285     5285
  Branches      926      926
=======================================
  Hits         5015     5015
  Misses        247      247
  Partials       23       23

Flag
Coverage Δ

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

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

Impacted Files
Coverage Δ

src/Parser.js
96.58% <ø> (ø)
: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 d1cee3c...1539d88. Read the comment docs.

Does this mean import '.' will no longer work within the repo, i.e., we need Webpack even for Node use?

@edemaine It's rather the opposite. As preval is a Babel plugin, it is integrated into the transpiling pipeline. So we can use KaTeX, i.e., import '.', without having to call node src/unicodeMake.js. However, there was a circular dependency transpiling issue, that is:
// src/unicodeAccents.js
export default {...}

// src/unicodeSymbols.js
require('@babel/register');
const accents = require('./unicodeAccents').default;

// src/Parser.js
import unicodeSymbols from /*preval*/ "./unicodeSymbols";

// import KaTeX compiling on the fly
require('@babel/register');
const katex = require('./katex.js');

results in src/unicodeAccents.js not being transpiled. Thank you for pointing that out.

Codecov Report

Merging #2153 into master will decrease coverage by 0.05%.
The diff coverage is 0.00%.

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


[WB-4612] Disable login in disabled mode

https://wandb.atlassian.net/browse/WB-4612
Description
What does the PR do? - disables wandb login in disabled mode
Testing
How was this PR tested?- manually

This should be really easy to test, kinda suprised we don't have any explicity wandb.login tests currently...


refactor(remix-server-runtime): move away from deprecated atob/btoa

atob and btoa are deprecated in Node, according to the docs, so this PR uses Buffer.from instead.
function atob(data: string): string;
/**
 * Decodes a string into bytes using Latin-1 (ISO-8859), and encodes those bytes
 * into a string using Base64.
 *
 * The `data` may be any JavaScript-value that can be coerced into a string.
 *
 * **This function is only provided for compatibility with legacy web platform APIs**
 * **and should never be used in new code, because they use strings to represent**
 * **binary data and predate the introduction of typed arrays in JavaScript.**
 * **For code running using Node.js APIs, converting between base64-encoded strings**
 * **and binary data should be performed using `Buffer.from(str, 'base64')` and`buf.toString('base64')`.**
 * @since v15.13.0
 * @deprecated Use `buf.toString('base64')` instead.
 * @param data An ASCII (Latin1) string.
 */

It also removes a needless exception identifier. i.e.:
-  } catch (error) {
+  } catch {

@mcansh That what I was thinking and why I asked @mjackson to be sure
Maybe there's another way to get rid of the deprecated methods?

The buffer package is a polyfill for Node Buffer. Perhaps Remix should just include this seeing as how a lot of packages (especially so-called web3 packages) rely on Buffer (I believe it's because WebPack includes it.
Right now, I have to patch the Remix compiler to remove the node-builtins check, since you can't even import buffer from client file.

We actually don't directly use atob and btoa. They are polyfilled by the platforms as needed. Node uses Buffer under the hood: https://github.com/remix-run/remix/blob/main/packages/remix-node/base64.ts


Feature Request - Query/Search Params

Describe the feature in detail (code, mocks, or screenshots encouraged)
Request: A rune to conveniently parse and interface with the query/search params.
Current Solution:  i'm using https://sveltekit-search-params.netlify.app/ everywhere.
Why: We end up utilizing search params quite a bit. Tab navigation, page state, search queries and so on. Would be super convenient to have this along with the debounce rune work together as well.
What type of pull request would this be?
New Feature
Provide relevant links or additional information.
No response

Maybe this is something @paoloricciuti would be interested in?

Lol i just published this
https://github.com/paoloricciuti/sveltekit-view-transition/issues/43
i would not be opposed to merge the project into runed but i wonder what could be the way forward:

sveltekit-view-transition as the name suggest uses a sveltekit api while runes seems more svelte oriented...i think without interacting with goto and the page store (or state in the future) the code can get very hairy and possibly conflict with sveltekit.
the library has quite a few users already so if we end up merging this how to deal with old users?
as you may seem in the codebase of sveltekit-search-params there are quite a few edge cases so i worry of the complexity that this could add to runed being basically a whole library rather than a simple utility.

Lol i just published this
https://github.com/paoloricciuti/sveltekit-view-transition/issues/43
i would not be opposed to merge the project into runed but i wonder what could be the way forward:

sveltekit-view-transition as the name suggest uses a sveltekit api while runes seems more svelte oriented...i think without interacting with goto and the page store (or state in the future) the code can get very hairy and possibly conflict with sveltekit.
the library has quite a few users already so if we end up merging this how to deal with old users?
as you may seem in the codebase of sveltekit-search-params there are quite a few edge cases so i worry of the complexity that this could add to runed being basically a whole library rather than a simple utility.

TBH I'm not opposed to having SvelteKit only utilities. We just need to mark them well, maybe add some tags! We can experiment together 😄


Revert "Adding new param Encryption_Key to gcp-create-environment, GC…

…P CMEK Key validation and storing encryption-key in enviroment-parameters table, Using GCP CMEK key to encrypt FREEIPA Disk by setting keyEncryptionMethod to Custom"
This reverts commit 74e2911f0f6e67a09aef155af6f13a7b9effc467.
See detailed description in the commit message.

Folks, sending this just in case the team decides to keep the swagger compat test as required and want to make progress with the releases.


[Bug] unable to load standard library for target 'x86_64-apple-macosx12.0'

I use AnyLint with Xcode 14.3 on MacOS Ventura.
I use with an older Objective C project.
I setup AnyLint a few months ago.
However, I've sstarted getting this error
unable to load standard library for target 'x86_64-apple-macosx12.0'
I've traced this back to my AnyLint build phase.

It seemed to go away after a Mac update, but sonoma wasn’t required.


400 Missing required parameter: 'messages[3].content[0].type' on tool execution

We have a plan and execute workflow that was working fine on previous versions of the langchain / langgraph libraries -
"langchain": "^0.2.5",
"@langchain/community": "^0.2.6",
"@langchain/core": "^0.2.6",
"@langchain/langgraph": "^0.0.21",
"@langchain/openai": "^0.1.1",

We updated the libraries to the latest versions so we could add support for a custom Redis checkpoint.
But after updating the libraries to the below versions, the workflow started to fail at executeStep() -
"langchain": "^0.2.17",
"@langchain/community": "^0.2.31",
"@langchain/core": "^0.2.28",
"@langchain/langgraph": "^0.1.1",
"@langchain/openai": "^0.2.7",

The full error dump is below -
BadRequestError: 400 Missing required parameter: 'messages[3].content[0].type'.
    at APIError.generate (webpack-internal:///(rsc)/./node_modules/.pnpm/openai@4.56.0_zod@3.23.8/node_modules/openai/error.mjs:60:20)
    at OpenAI.makeStatusError (webpack-internal:///(rsc)/./node_modules/.pnpm/openai@4.56.0_zod@3.23.8/node_modules/openai/core.mjs:304:65)
    at OpenAI.makeRequest (webpack-internal:///(rsc)/./node_modules/.pnpm/openai@4.56.0_zod@3.23.8/node_modules/openai/core.mjs:347:30)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async eval (webpack-internal:///(rsc)/./node_modules/.pnpm/@langchain+openai@0.2.7_langchain@0.2.17_@langchain+community@0.2.31_ignore@5.3.1_openai@4.56.0_zod@3.23.8__/node_modules/@langchain/openai/dist/chat_models.js:1322:29)
    at async RetryOperation.eval [as _fn] (webpack-internal:///(rsc)/./node_modules/.pnpm/p-retry@4.6.2/node_modules/p-retry/index.js:50:12) {
  status: 400,
  request_id: 'req_xxx',
  error: {
    message: "Missing required parameter: 'messages[3].content[0].type'.",
    type: 'invalid_request_error',
    param: 'messages[3].content[0].type',
    code: 'missing_required_parameter'
  },
  code: 'missing_required_parameter',
  param: 'messages[3].content[0].type',
  type: 'invalid_request_error',
  attemptNumber: 1,
  retriesLeft: 6,
  pregelTaskId: '12345678-1234-5678-0000-000000000000'
}

Hey @krusadellc, sorry you're running into this - is this consistent? Or is there anything I can do to try to reproduce the issue?

It is consistent, I am trying to isolate this so I can share a code snippet that can help reproduce this issue.
If it helps, the issue happens at the executeStep node which basically calls createReactAgent with a some custom tools.

Ok. Keep me posted. If you have a LangSmith trace that would be helpful too.

here's a LangSmith trace for the failure
https://smith.langchain.com/public/bdbd1df4-935e-4200-acbf-1c97910bdede/r

So two things strike me as strange:

Your input messages seem to be doubled - can you check your input format?

The error message is caused by your get-all-rental-property-details tool returning an array, which is being improperly parsed into content blocks. Can you try calling JSON.stringify() on the tool return type?

If that doesn't fix it, please reopen and share your code with me.

The input messages are doubled since the agent is called with the below input as suggested in the official guide here

const input = {
    messages: ["user", task],
  };
 const { messages } = await agentExecutor.invoke(input, config);

This was confusing to me as well, but since I didn't know the internals of createReactAgent() I stuck with the guide.

JSON.Stringify() on the output of the function helped. Thanks a lot!
Can you please help me understand what was going on?


All multi-cursors now disappear when navigating by word

Type: Bug
Take any test with multiple lines.
Use Ctrl+Shift+Alt-Down to create a multi-cursor, one per line.
Navigating by character (Left/Right) works as expected: all cursors navigate.
Navigating by line (Up/Down or Home/End) also works as expected, and all cursors do it.
Navigating by word (Ctrl+Left/Right) doesn't. All cursors but one disappear as soon as you do this.
This just started happening out of the blue, possibly after an update. I don't know (just came back from vacation).
VS Code version: Code 1.81.0 (6445d93c81ebe42c4cbd7a60712e0b17d9463e97, 2023-08-02T12:37:13.485Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Connection to 'SSH: ttdrazzle' could not be established  Canceled

System Info

Item
Value

CPUs
AMD Ryzen 9 7950X 16-Core Processor             (32 x 4491)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
127.14GB (84.80GB free)

Process Argv
--crash-reporter-id 51152fc6-57cf-45c0-ba26-7ec617922cec

Screen Reader
yes

VM
0%

Connection to 'SSH: ttdrazzle' could not be established  Canceled
Extensions (26)

Extension
Author (truncated)
Version

midl3-language-server
Ale
0.0.31

vscode-research
dev
1.2022.1111005

vulnerability-extension
dev
1.2023.807004

xml
Dot
2.5.1

gitlens
eam
14.2.1

x8664assembly
fre
0.1.0

vscode-pull-request-github
Git
0.70.0

todo-tree
Gru
0.0.226

vscode-graphviz
joa
0.0.6

tdpcode
Mic
10.2304.707

vscode-azdo-codereview
Mic
1.2023.331002

wavework
Mic
1.2023.810005

csharp
ms-
2.0.376

vscode-dotnet-runtime
ms-
1.7.0

sarif-viewer
MS-
3.4.1

remote-ssh
ms-
0.102.0

remote-ssh-edit
ms-
0.86.0

remote-wsl
ms-
0.81.0

cmake-tools
ms-
1.15.31

cpptools
ms-
1.17.4

remote-explorer
ms-
0.4.1

remote-server
ms-
1.4.3

vsliveshare
ms-
1.0.5883

windbg-debug
rez
0.3.4

cmake
twx
0.0.17

markdown-all-in-one
yzh
3.5.1

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
vstes627:30244334
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscoreces:30445986
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30410667
py29gd2263cf:30792227
vscaat:30438848
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30695312
azure-dev_surveyone:30548225
vscccc:30803845
282f8724:30602487
f6dab269:30613381
a9j8j154:30646983
showlangstatbar:30737416
03d35959:30757346
pythonfmttext:30731395
pythoncmvfstrcf:30756944
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
gsofa:30804715
pythonnosmt12:30797651
pythonidxpt:30805730
pythonnoceb:30805159
asynctok:30810527
dsvsc013:30795093
dsvsc014:30804076
diffeditorv1:30810525

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.81.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Ok, spooky as this is... I opened another VSCode window, and it wasn't happening.
Looking for differences, I noticed the "bad" window was showing "Screen Reader Optimized" in the status bar. I don't know how or why that happened, but as soon as I clicked and said "no" to the prompt, the problem disappeared.
So... please, adjust this issue to "All multi-cursors now disappear when navigating by word when Screen Reader Optimized mode is on".

This is working as expected. Screen Readers do not have the concept of multiple cursors, and they have their own definition of what a word is, what constitutes word boundaries, etc.
When VS Code detects that a Screen Reader is attached to it, we will delegate ctrl+left and ctrl+right to the default browser implementation, which matches what Screen Readers expect. In this case, it is not possible to support multiple cursors.
There are two workarounds:

(the simplest). If you are not using a Screen Reader you can configure "editor.accessibilitySupport": "off" in your settings.
If you are using a Screen Reader and would still like that word navigation is handled by VS Code, you can edit your keybindings.json and add the following keybinding rules:

{ "key": "ctrl+right",            "command": "cursorWordEndRight",
                                     "when": "textInputFocus" },
{ "key": "ctrl+shift+right",      "command": "cursorWordEndRightSelect",
                                     "when": "textInputFocus" },
{ "key": "ctrl+left",             "command": "cursorWordLeft",
                                     "when": "textInputFocus" },
{ "key": "ctrl+shift+left",       "command": "cursorWordLeftSelect",
                                     "when": "textInputFocus" },


error after exp convert for StrapMobile boilerplate, not sure how to use registerRootComponent

Hi there,
I am using a boilerplate purchased from StrapMobile and want to convert it to use with Exponent.
I ran the exp convert and everything seemed to go well. Then it said I have to replace AppRegistry.registerComponent('YourApplicationName', () => YourRootComponent) by Exponent.registerRootComponent(YourRootComponent) and also add the import Exponent from 'exponent'.
I searched in the code and believe those two places where I need to do the replacements are in index.ios.js and index.android.js
index.ios.js Before:
'use strict';

import { AppRegistry } from 'react-native'
import setup from './js/setup'

AppRegistry.registerComponent('MyApp', setup);

index.ios.js After:
'use strict';

import Exponent from 'exponent'
import setup from './js/setup'

Exponent.registerRootComponent(setup);

setup.js
'use strict';

import React, {Component} from 'React';
import App from './App';
import configureStore from './configureStore'
import {Provider} from 'react-redux';
import {StyleSheet, View, Text} from 'react-native';

function setup():React.Component {

    class Root extends Component {

        constructor() {
            super();
            this.state = {
                isLoading: false,
                store: configureStore(()=> this.setState({isLoading: false})),
            };
        }

        render() {
            return (
                <Provider store={this.state.store}>
                    <App store={this.state.store} />
                </Provider>
            );
        }
    }
    return Root
}

export default setup;

And it's giving me these errors when launching project from XDE into IOS simulator:
setup(...): A valid React element (or null) must be returned. You may have returned undefined, an array or some other invalid object.

mountComponent
    ReactCompositeComponent.js:194
mountComponent
    ReactReconciler.js:47
performInitialMount
    ReactCompositeComponent.js:370
mountComponent
    ReactCompositeComponent.js:257
mountComponent
    ReactReconciler.js:47
mountChildren
    ReactMultiChild.js:240
initializeChildren
    ReactNativeBaseComponent.js:69
mountComponent
    ReactNativeBaseComponent.js:187
mountComponent
    ReactReconciler.js:47
performInitialMount
    ReactCompositeComponent.js:370
mountComponent
    ReactCompositeComponent.js:257
mountComponent
    ReactReconciler.js:47
mountChildren
    ReactMultiChild.js:240
initializeChildren
    ReactNativeBaseComponent.js:69
mountComponent
    ReactNativeBaseComponent.js:187
mountComponent
    ReactReconciler.js:47
performInitialMount
    ReactCompositeComponent.js:370
mountComponent
    ReactCompositeComponent.js:257
mountComponent
    ReactReconciler.js:47
performInitialMount
    ReactCompositeComponent.js:370
mountComponent
    ReactCompositeComponent.js:257
mountComponent
    ReactReconciler.js:47
performInitialMount
    ReactCompositeComponent.js:370
mountComponent
    ReactCompositeComponent.js:257
mountComponent
    ReactReconciler.js:47
mountComponentIntoNode
    ReactNativeMount.js:51
perform
    Transaction.js:138
batchedMountComponentIntoNode
    ReactNativeMount.js:66
perform
    Transaction.js:138
batchedUpdates
    ReactDefaultBatchingStrategy.js:63
batchedUpdates
    ReactUpdates.js:98
renderComponent
    ReactNativeMount.js:117
renderApplication
    renderApplication.js:33
runApplication
    AppRegistry.js:105
__callFunction
    MessageQueue.js:236
<unknown>
    MessageQueue.js:108
guard
    MessageQueue.js:46
callFunctionReturnFlushedQueue
    MessageQueue.js:107

Any help would be much appreciated!

The answer, as provided by StrapMobile, was to replace the contents of setup.js as seen above, by this:
import React, {Component} from 'React';
import App from './App';
import configureStore from './configureStore'
import {Provider} from 'react-redux';
import {StyleSheet, View, Text} from 'react-native';

export default class Root extends Component {
    constructor() {
        super();
        this.state = {
            isLoading: false,
            store: configureStore(()=> this.setState({isLoading: false})),
        };
    }
    render() {
        return (
            <Provider store={this.state.store}>
                <App store={this.state.store} />
            </Provider>
        );
    }
}


[ISSUE #6119] replace ScheduleMessageService method reference

Make sure set the target branch to develop
What is the purpose of the change
close #6119
Brief changelog
replace ScheduleMessageService method reference
Verifying this change
XXXX
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Codecov Report

Merging #6120 (bbef1ce) into develop (7049527) will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@              Coverage Diff              @@
##             develop    #6120      +/-   ##
=============================================
+ Coverage      43.24%   43.26%   +0.02%
- Complexity      8845     8858      +13
=============================================
  Files           1094     1094
  Lines          77137    77135       -2
  Branches       10057    10057
=============================================
+ Hits           33355    33376      +21
+ Misses         39613    39602      -11
+ Partials        4169     4157      -12

Impacted Files
Coverage Δ

...cketmq/broker/schedule/ScheduleMessageService.java
57.85% <100.00%> (-0.20%)
:arrow_down:

...pl/consumer/ConsumeMessageConcurrentlyService.java
47.05% <0.00%> (-2.27%)
:arrow_down:

...he/rocketmq/client/impl/consumer/ProcessQueue.java
59.91% <0.00%> (-2.21%)
:arrow_down:

...org/apache/rocketmq/common/stats/StatsItemSet.java
41.79% <0.00%> (-1.50%)
:arrow_down:

...e/rocketmq/store/ha/autoswitch/EpochFileCache.java
77.08% <0.00%> (-1.39%)
:arrow_down:

...ent/impl/consumer/DefaultLitePullConsumerImpl.java
68.17% <0.00%> (-0.47%)
:arrow_down:

...apache/rocketmq/store/timer/TimerMessageStore.java
54.15% <0.00%> (-0.10%)
:arrow_down:

...ava/org/apache/rocketmq/filter/util/BitsArray.java
59.82% <0.00%> (ø)

...va/org/apache/rocketmq/store/FlushDiskWatcher.java
81.25% <0.00%> (ø)

.../org/apache/rocketmq/proxy/config/ProxyConfig.java
44.52% <0.00%> (ø)

... and 11 more

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


Fitbounds to view the world map

Is there a way to be able to view the entire world map inside a div size 600px by 600px?
Even at zoom level 1 it's not far out enough.

The minimal tile for world map is 256x256px so it's possible to show world map in div 600x600,
but there will be some math issues about.
Please read comment about no homeomorphism between screen coordinates and map here
https://github.com/istarkov/google-map-react/blob/master/src/google_map.js#L305-L317

@istarkov
While understanding this homeomorphism  issue, i.e.
GoogleMap: minZoom option is less than recommended minZoom option for your map sizes.
overrided to value 4

Is there a way to ask the library NOT to dynamically calculate the minZoom?
if (mapOptions.minZoom < minZoom) {
  mapOptions.minZoom = minZoom;
}

Thanks,

Just in case I was not clear in the previous post, I want to disable, or set up a flag to disable.
https://github.com/istarkov/google-map-react/blob/master/src/google_map.js#L305-L317
  // calc minZoom if map size available
  // it's better to not set minZoom less than this calculation gives
  // otherwise there is no homeomorphism between screen coordinates and map
  // (one map coordinate can have different screen coordinates)
  _getMinZoom = () => {
    if (this.geoService_.getWidth() > 0 || this.geoService_.getHeight() > 0) {
      const tilesPerWidth = Math.ceil(this.geoService_.getWidth() / K_GOOGLE_TILE_SIZE) + 2;
      const tilesPerHeight = Math.ceil(this.geoService_.getHeight() / K_GOOGLE_TILE_SIZE) + 2;
      const maxTilesPerDim = Math.max(tilesPerWidth, tilesPerHeight);
      return Math.ceil(log2(maxTilesPerDim));
    }
    return DEFAULT_MIN_ZOOM;
  }

Given one concrete example.

state.zoomLevel is set to be 2
_getMinZoom invoked upon render map and recalculate to be 4

Which is not exactly what I want. Please help thanks.

The problem that in lower zooms than getMinZoom returns I can't garanty any marker math, markers could be placed in some cases anywhere. Do you really want unpredictable bugs?

@istarkov Thank you for reply. I think it is feasible to set up a flag and hand the granularity control to developers. If any developer choose to use this flag, they should be aware the responsibility of taking care of the markers mapping.
Anyway, maybe I should fork this repo and make a pull request later. Give me sometime, and I will come back to it, regardless it was a successful attempt or not.

IMHO current API surface is already 10x bigger than it's need to be :-)
But I will likely accept your PR :-)


Compiler issue with Xcode 8 Beta 2 (RealmSwift 1.0.2)

I've recently upgraded to Xcode Beta 2 and used CocoaPods to update to Realm 1.0.2 but have 2 errors I am having difficulty with:
/Users/gavinbeard/Documents/TestApp/Pods/RealmSwift/RealmSwift/Object.swift:70:2: Use of unresolved identifier 'RealmSwiftObject'
And
/Users/gavinbeard/Documents/TestApp/Pods/RealmSwift/RealmSwift/Object.swift:70:1: Expressions are not allowed at the top level
Which is this line of code:
(RealmSwiftObject)
The second error is:
/Users/gavinbeard/Documents/TestApp/Pods/RealmSwift/RealmSwift/Realm.swift:96:5: Self.init isn't called on all paths before returning from initializer
Which relates to this block of code:
    public convenience init(fileURL: URL) throws {
        var configuration = Configuration.defaultConfiguration
        configuration.fileURL = fileURL
        try self.dynamicType.init(configuration: configuration)
    }

Appreciate its just a beta version of Xcode, but wonder if there is a quick fix I can apply until an official update?

Realm's support for Swift 3 is still very much a work in progress. To try it out you'll need to use Realm Swift from master, rather than any of our released versions. You can do this by updating your Podfile to include the following:
pod 'Realm', git: 'https://github.com/realm/realm-cocoa.git', branch: 'master'
pod 'RealmSwift', git: 'https://github.com/realm/realm-cocoa.git', branch: 'master'

What about support for Swift 2.3? That's supposed to be way less impactful. Or are you guys not planning on supporting 2.3?

@marchy Swift 2.3 support couldn't be added for Xcode 8 beta 1 due to an Xcode bug, but I just pushed a PR for 2.3 support here: #3882.

@jpsim fantastic thanks for the update JP. Will try once it gets merged

the master branch works with Xcode beta 3 ?

Yes, it should as of #3896.


[⚡ Feature]: Add KV (or custom) support for revalidateTag (next/cache)

Hi all!
I've seen several comments from maintainers ([1], [2]) following up the great work of feat: fetch (suspense) cache handling, and next/cache support #419 by @james-elicx that given limitations on Cache API (e.g. per-colo cache and requires a custom domain to be configured), we'd mostly want to use alternative storage mechanisms in production (most likely KV, but perhaps other users might prefer D1/R2/DO based on specific use cases or even something else).
I understand that the ultimate intention is to let users define in their own next.config.js their own adaptor for caching – but there might be a pre-made snippet for KV, or an exported util they can reference.
I've noted that there isn't any issue tracking that – so wanted to drop this in for that purpose, and in case maintainers want to explain more what they have in mind (or if there are any blockers they're tracking). I'm happy to take a look at contributing the changes too.
Thanks!

I actually originally wanted to let people opt in to other storage mechanisms by the presence of the binding being detected, e.g. process.env.KV_SUSPENCE_CACHE would use the KV cache, but I think others weren't a fan of doing that which is why it was scrapped from the initial PR.
The general idea that was settled upon would be to require people use a separate cache interface using the incrementalCacheHandlerPath option in next.config.js. The Next.js docs recommend the following usage: incrementalCacheHandlerPath: require.resolve('./cache-handler.js'). The problem with this is that you then get the import for the CJS version when trying to read the path from next.config.js, instead of the ESM one, because Next.js want you to use require for it, and that becomes a real pain since Workers want ESM.
Personally, I would actually quite like to add the binding-presence based approach for things like KV/R2/D1, and can quite easily revive that, but I'm not sure whether @dario-piotrowicz would be okay with that approach.
I would also note that Vercel's data cache is regional, so using the cache api is a rather similar experience.

Hi everyone!
I just released a Next.js based website in production on Pages and had a lot of headaches because the data cache is regional. In short terms, news being added to the website didn't show up at all in the homepage because the origin server was triggering revalidateTags and revalidatePaths in just one region. Having a distributed cache will solve this.
You're right @james-elicx, on Vercel the data cache is regional as it is on Cloudflare Pages, but there's an important difference (from the docs):

On-demand revalidation: Any data can be triggered for revalidation on-demand, regardless of the revalidation interval. The revalidation propagates to all regions within 300ms.

So, to better replicate the Vercel model, there should be at least a way to revalidate the data cache in all regions. Using KV is the obvious way to do this on Cloudflare. In the future a hybrid approach (use Cache API primarily with a short expiration and reading through to KV for global consistency) could be beneficial for really high scale apps.
I understand the hesitations about using an env or a binding for the configuration, but I think that allowing the use of the KV cache is of great value and that justifies some inconveniences.
Also, about the require.resolve, as I understand it, it just returns the full path to a file when used like require.resolve('./filename.js'), so could be replaced by a simple __dirname + '/filename.js'?

Also, about the require.resolve, as I understand it, it just returns the full path to a file when used like require.resolve('./filename.js'), so could be replaced by a simple __dirname + '/filename.js'?

The main part of the problem is that the path provided for incrementalCacheHandlerPath is imported by Next.js using require, so it needs to be CJS or Next.js dev mode/building won't work, but we need it to be ESM, and in my view it's really not ideal to go down the path of trying to do unsafe transforms from CJS to ESM at build time using custom esbuild plugins.

Sorry for the late reply 🙂
I think we agreed with @james-elicx that we can try to go with an approach in which the cache handler can be configurable via the standard incrementalCacheHandlerPath (my preference) and also based on binding naming convention (James' preference) just so to allow people to also use those if they do not want to rely on configs for this.
There's the pain point of getting cjs and needing to deal with it, but I hope that we can try to sort that out (by trying for instance to convert cjs to esm using something like this for example: https://github.com/wessberg/cjstoesm).
I'll leave this to James as he's been driving the chance implementation since the beginning and has already started looking at things back when, but I am happy to help or give it a shot myself if James doesn't have the time to tackle this 🙂


contract c array packing

#2350
Needed to change datastream.hpp and raw.hpp to provide packing/unpacking for c-arrays to add size to the packing so abi-serialization can be performed.

Ready for re-review


No sound output

After installing everything on rasbian stretch I can no longer output any sound. I've modified the .asoundrc file, forced audio through the 3.5mm jack still nothing.

Hi Sean,
Can you provide a few more details on what you have tried and what you are observing?

Are you able to play sound through other applications such as aplay?
Is the speaker icon in the taskbar at the top of the screen active or crossed out?
If it is active, and you right-click on it, what output options are listed at the top of the pop-up menu, and which one has a check mark?
What are the contents of your .asoundrc?
If other applications are working, and you are only having trouble with the SDK, can you run the SDK with DEBUG9 logging and copy the logging here?

Ken


Badge

Maybe we can have a badge for people to use in their awesome list if they follow the awesome.md guidelines?
I can make something based on the new logo, but we need to find a canonical place to host it where the URL will never change, long cache, but still possible to update it. Any ideas?

Why not host it at github?

@n1trux I guess we could. Just that GitHub blocks rendering SVGs hosted in GitHub repos, so we would have to use https://rawgit.com like we do in the readme, and they have some kind of rate limiting, though unsure how high it is.

http://imgur.com ?

@jeshuamaxey Can you update the image without changing the URL there?

Ahh didn't see that requirement. Imgur won't work

Couldn't we just use our own servers?
Base64?

Host it in the gh-pages branch?

:+1: gh-page

Badge suggestion:

I went with something non-pink, the logo text color, as pink would probably have been too bright and distracting for people.
Thoughts?

Me likey!

Looks excellent!
Did you draw the letters or used some font? Those are some sexy letters right there!

@aleksandar-todorovic Same font as in the logo, Orbitron. It's just paths in the badge though.

:+1:

:+1:

See here on how to use the badge: https://github.com/sindresorhus/awesome/blob/master/awesome.md#awesome-badge

@sindresorhus Should we notify the list authors about the existence of this badge? Most of the authors already on the list are never going to notice it.

Nevermind, just saw the other issue.

This looks awesome! nice work.


Django 4.0, Remove support to older Django and Python versions and improvements

Made fixes to make it work with Django 4.0.
Drop support to Python 2 and Python < 3.5 that are unmaintained and insecure.
Drop support to Django < 2.2 that also reach end of mainstream support (insecure).
Drop included jQuery version used in favor of built-in django.jQuery in Django that is more up to date and maintained by Django, making also the library less vulnerable and lightweight.
Fix margin in "chips", specially margin top was 0, making it ugly.
Fix Tox and Selenium configurations. Replace PhantomJS with Chrome (PhantomJS support was removed in newer versions of Selenium).
Replace Travis CI with GitHub Actions: Travis is fading out its commitment with OSS, making the service for no-paid projects each time slower and less available. On the other hand GH Actions is free and fast even for OSS projects.
Remove IDE configurations that are "user" related.

I didn't stress enough that the main change was adding support to Django 4.0 that was broken (although the easiest part) , so I changed the title of the PR and the description to reflect that.

I just had a quick look at the CI stuff, without further diving into your actual changes.

Why are you using Python 3.5 and Python 3.10 only? I understand that these should probably be the supported version range, but I do not think that it will hurt to test the versions in-between as well, as the duration is short enough and this should not require many changes.

If you are adding compatibility for the latest and supported Django versions, we should probably fix the existing system check warnings. From a quick look, there seems to be at least one type:
2022-02-21T13:12:26.8469138Z example.Cat: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'.
2022-02-21T13:12:26.8470013Z 	HINT: Configure the DEFAULT_AUTO_FIELD setting or the AppConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'.
2022-02-21T13:12:26.8470862Z example.Food: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'.
2022-02-21T13:12:26.8471571Z 	HINT: Configure the DEFAULT_AUTO_FIELD setting or the AppConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'.
2022-02-21T13:12:26.8472256Z example.Person: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'.
2022-02-21T13:12:26.8472985Z 	HINT: Configure the DEFAULT_AUTO_FIELD setting or the AppConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'.

Regarding the CI results not being visible here: According to  the docs, GitHub applies the workflow definitions from the base branch.

Note: Workflows triggered by pull_request_target events are run in the context of the base branch. Since the base branch is considered trusted, workflows triggered by these events will always run, regardless of approval settings.

Hi @FriedrichFroebel , thanks for your feedback ! You are right, I added more Python versions and still run fast enough, and added also Django 3.0 that was missed in the matrix.
Also fixed the warnings in Django 3.2+.
Check the last execution at https://github.com/mrsarm/django-searchable-select/actions/runs/1876512153.

Another thing which just popped up for me are the names like py35-22 which seems to indicate Python 3.5 running Django 2.2. I am not sure whether these should be made more obvious/descriptive.

The dj prefix (or even python and django as the longer versions) would probably be enough for me to improve readability.

Done ! Now an item from the matrix execution looks like: py3.8-dj3.0.

Hello Mr @and3rson ! I made these changes, and I see you are looking for developers to take care of the project.
Do you want to review the changes and ultimately merge and release a new version? Or do you want me take care of that? If you give me the rights in the repo and in PyPI I'm happy to take care of it. BTW my username in PyPI is the same than Github: https://pypi.org/user/mrsarm/
I also working in a few more changes to make the widget more flexible, and allow for instance to populate an ArrayField with values from another table.

I created in a separated PR a new feature that allows to use the plugin with the ArrayField type, so the base branch is the branch from this same PR, and I didn't include the changes here to not make the PR hard to review with so many changes.
In the meantime, anyone that needs to use this widget on Django 4, or wants to use it with array fields, take a look to the other PR, where there is also instructions of how to use it installing the package from GitHub instead of PyPI: https://github.com/mrsarm/django-searchable-select/pull/1


Allow declaration of vars in schema.yml

Describe the feature
It would be excellent if it were possible to provide vars to models in schema.yml files like so:
version: 2
models:
  - name: <model name>
    description: <description>
    docs:
      show: <true|false>
    meta:
      key1: <value1>
      key2: <value2>
    vars:                     // Like this
      key1: <value1>
      key2: <value2>
    tests:
      - <test>
      - ...
    columns:
      - name: <column name>
        quote: <true|false>
        tags: <tags>
        description: <column description>
        tests:
          - <test>
          - ...
      - ...

Additional context
I'm suggesting this feature because the dbt_project.yml file gets considerably large and hard to manage at scale, when needing to provide variables to multiple models. It would be a lot easier to manage if there were a way to split the variables into sub-files, and I thought the schema.yml files would be a perfect candidate, as they already exist and are designed to hold other information related to models.
Who will this benefit?
This would mainly benefit larger companies who have created libraries of macros/packages with arguments whose values differ between models, and would prefer not to fill their model files with the setting of variables, but find it too difficult to manage if it's all in the dbt_project.yml

hey @DVAlexHiggs - cool idea! Unfortunately, I don't think this is something we're going to add support for.
If you check out #2312 , you can see that we very recently made a ton of changes around variable scoping. Historically, variables were scoped at the folder-level. This meant that you could do something like:
models:
  my_project:
    path1:
      vars: {myvar: abc123}
    path2:
      vars: {myvar: def456}

In this setup, a model in models/path1 would get a variable called myvar with the value abc123 whereas a model in models/path2 would get a value of def456. This made it really tricky to correctly build compilation contexts for different node types. Imagine you have a schema.yml file in models/path2 which describes a model in models/path1 -- what do you think the myvar value should evaluate to in that context?
To resolve inconsistencies like this, we've added a vars: block to the dbt_project.yml file which cannot be scoped to a particular path. It looks like:
vars:
  myvar: abc123

models:
  ...

Note though that variables can still be scoped to packages:
vars:
  package1:
    myvar: abc123
  package2:
    myvar: abc123

I just wanted to give some background on how we're thinking about variables, and some of the recent changes that impact variable usage. Given these changes, I don't think we'll be able to add model-scoped variables like you've described here. I do however think your use case is a good one, and I can imagine two paths forward:

Supplying configurations in schema.yml files

This would look like:
models:
  - name: my_model
     config:
       key1: <value1>
       key2: <value1>

We could then provide a way to tap into these configuration values in the model .sql file context, eg:
select {{ config.get('key1') }} from ....

Allow variables to be defined outside of the dbt_project.yml file

See #1790 for more info
Curious to hear what you think about these changes and options

Hey @drewbanin thanks for your response. I think both of these solutions have their merits. Solution 1 is more dbt-esque and provides more functionality to the current schema.yml, and keeps all metadata/information about models in one place.
I think solution 2 is a powerful alternative with a lot of versatility, but perhaps more care than usual would need to be taken with directory structures and organisation of the YAML files to ensure.
I think personally I would prefer solution 1.

HI, any news on this? Really excited if this is being considered. I'm happy to contribute it myself as well, though I would need a point in the right direction to start with. Perhaps we could talk about this?

Ok - thanks for the additional context for this one on Slack @DVAlexHiggs.
To recap: You're leveraging the datavault package which relies on vars to configure models pks, natural keys, load timestamps, etc. I do think the dbt_project.yml file was a poor place for configs like that historically, so in light of the vars changes in 0.17.0, we should figure out a better path forwards.
I really like the idea of allowing model configs in .yml files. We have a dedicated issue for this over here: https://github.com/fishtown-analytics/dbt/issues/2401. I think #2401 was inspired by this very issue :)
#2401 outlines a very similar syntax to what you described above, except the key will be config, not vars:
version: 2
models:
  - name: <model name>
    description: <description>
    docs:
      show: <true|false>
    meta:
      key1: <value1>
      key2: <value2>
    config:                     // Like this
      key1: <value1>
      key2: <value2>

We'll need to think about the order of parsing. I think a sensible order of operations is:

Apply dbt_project.yml configs
Apply schema.yml file configs
Apply .sql file configs

If we make the configs from the dbt_project.yml file and schema.yml files available in the .sql file context, then you could simply use config.get() instead of var() to capture these config values. This should address your use case with the added benefit of deflating the size of your dbt_project.yml file which is, i bet, huge for large dbt projects on datavault :)

@drewbanin I think the order you've specified makes sense. This will be a huge help for uber-templated models

Yes the order makes sense, and I agree that config is better way forward

Closing in favor of #2401


GET on lookups doesn't return all records

I just noticed if I do a query for a specific lookup record by mac (/api/current/lookups?q=), I get the record, but when I do a query for all lookups (/api/current/lookups), the same record doesn’t show up in that list.
$ curl localhost:8080/api/common/lookups?q=00:1c:73:66:ad:2a | python -mjson.tool
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   185  100   185    0     0  27525      0 --:--:-- --:--:-- --:--:-- 30833
[
    {
        "createdAt": "2015-12-15T20:32:18.989Z",
        "id": "567078d29cccb24615688a7f",
        "ipAddress": "<IP_ADDRESS>",
        "macAddress": "00:1c:73:66:ad:2a",
        "node": "",
        "updatedAt": "2015-12-17T14:32:09.909Z"
    }
]

$ curl localhost:8080/api/common/lookups | python -mjson.tool | grep 567078d29cccb24615688a7f
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  3735  100  3735    0     0   164k      0 --:--:-- --:--:-- --:--:--  158k

Thanks @johren
Relevant code is at https://github.com/RackHD/on-http/blob/master/lib/api/lookups.js#L30 - looks like waterline.lookups.findByTerm(req.query.q) when the query is empty doesn't return a complete list.

Should get the cause.
From the implementation of findByTerm (https://github.com/RackHD/on-core/blob/master/lib/models/lookup.js#L36-L44):
findByTerm: function (term) {
            return this.find({
                or: [
                    { node: term },
                    { macAddress: term },
                    { ipAddress: term }
                ]
            });
        }

if term is empty, findByTerm only returns entries that either "node", "macAddress" or "ipAddress" is empty.
For @johren 's case, The fields node/macAddress/ipAddress are all exist, so it is excluded from the list.
The solution should be adding a special query in findByTerm if term is empty.

PR for this issue: https://github.com/RackHD/on-core/pull/52


Custom BIP84 Paths for Bitcoin and other compatible assets

Background
Hardware wallets like Ledger offer various derivation path construction by leveraging building blocks of BIP84 standard, e.g. account and address_index as explained here:
https://github.com/bitcoin/bips/blob/master/bip-0084.mediawiki
Current Behavior
ASGARDEX allows users to set address_index of BIP84 derivation path struction in its UI as depicted below:

Proposed Behavior
It would certainly benefit users to allow them to also set the account value, as explained in BIP84, as well. Perhaps in the form of a second entry box right next to INDEX in the picture above. Or even better, an advanced option to allow users to enter their own derivation path (this might need some regex validation).

Possible Starting Point
Upon looking at the code, I found that the address.ts file could be altered to add support for an account variable alongside the existing walletIndex variable. Just throwing ideas around.

thank you will look into it 👍


peripheralman: default to board's I2C frequency

PIO does not provide an API to set frequency. Default to board's
I2C frequency.
Signed-off-by: Sanrio Alvares<EMAIL_ADDRESS>

If a board's default frequency is unknown and it's not possible to set it via the PIO, this should return an error code (MRAA_ERROR_FEATURE_NOT_SUPPORTED).
If the I2C default frequency is guaranteed, I think it would be OK to return success only for the matching case.

While your comments are applicable to Edison how do I handle this on Joule?
Sensors looking to change frequency mode just fail on Joule and I am not familiar of any way to do that.

@Propanu I have made the requested edits. Please review. Thanks.

Quick note I2C_FAST is default on Joule too.

Oh sweet! I will make that change. Is there a sysfs node that prints this information?

I still don't get this. We can't change the i2c frequency therefore returning MRAA_ERROR_FEATURE_NOT_SUPPORTED is the correct thing to do. I'm not merging code that simply confuses the API. This function is meant to change the speed. If it can't then it can't.
You can check in sysfs for edison here: /sys/devices/pci0000:00/0000:00:08.0/i2c_dw_sysnode/mode. As far as I know that's a modified kernel driver so not generic.
In any case 99% of boards are in i2c_fast mode in default kernel configurations. The only exception I know to this is galileo gen1 which is in 100khz because of the i2c I/O multiplexer.


[IOTDB-4047]: Generic type in Statistics extend Serializable

close #4047

Coverage increased (+0.009%) to 67.464% when pulling 53a761c50afaf0f0c1100af555d49b8ee684253d on ruanwenjun:dev_wenjun_patch4047 into a10a170c99bb92d30e12c3b367030b211ff63548 on apache:master.