Vcpkg does not recognize custom triplet, even though it is listed as available

Describe the bug
I'm trying to use Vcpkg to install some libraries on Alpine Linux 3.14 running on a Docker container. I created a custom triplet file x64-linux-musl-static-release,cmake on the triplets/ directory.
When I try to install packages using my custom triplet, Vcpkg aborts saying that the triplet was not found, even though it is listed as available. However, if I rename the triplet file to x64-linux-musl.cmake, it works (I guess that's because this name is the default on this platform).

Expected behavior
Packages should be installed correctly.
Failure logs
The installation of the packages are aborted with the following error:
> [base_build 8/8] RUN VCPKG_FORCE_SYSTEM_BINARIES=1   /vcpkg/vcpkg install --triplet x64-linux-musl-static-release cpprestsdk[default-features,websockets] spdlog fmt:
#12 0.694 Error: invalid triplet: x64-linux-musl
#12 0.694 Available architecture triplets
#12 0.694 VCPKG built-in triplets:
#12 0.694   arm64-windows
#12 0.694   x64-windows-static
#12 0.694   x64-osx
#12 0.694   x64-linux
#12 0.694   x64-uwp
#12 0.694   x64-windows
#12 0.694   arm-uwp
#12 0.694   x86-windows
#12 0.694   x64-linux-musl-static-release
#12 0.694
#12 0.694 VCPKG community triplets:
#12 0.694   arm-linux
#12 0.694   arm64-mingw-static
#12 0.694   x86-ios
#12 0.694   x64-mingw-dynamic
#12 0.694   x64-freebsd
#12 0.694   arm64-osx
#12 0.694   arm64-osx-dynamic
#12 0.694   x64-osx-dynamic
#12 0.694   x86-mingw-dynamic
#12 0.694   x86-windows-static
#12 0.694   ppc64le-linux
#12 0.694   x86-mingw-static
#12 0.694   x86-uwp
#12 0.694   x86-windows-static-md
#12 0.694   arm64-android
#12 0.694   x64-android
#12 0.694   arm-android
#12 0.694   x86-freebsd
#12 0.694   arm-neon-android
#12 0.694   x86-windows-v120
#12 0.694   x64-mingw-static
#12 0.694   armv6-android
#12 0.694   x64-openbsd
#12 0.694   arm64-mingw-dynamic
#12 0.694   arm64-windows-static-md
#12 0.694   x64-windows-static-md
#12 0.694   arm64-windows-static
#12 0.694   wasm32-emscripten
#12 0.694   arm-ios
#12 0.694   s390x-linux
#12 0.694   arm-windows-static
#12 0.694   arm64-uwp
#12 0.694   arm64-linux
#12 0.694   arm-mingw-dynamic
#12 0.694   arm64-ios
#12 0.694   x86-android
#12 0.694   x64-ios
#12 0.694   arm-mingw-static
#12 0.694   arm-windows
------
executor failed running [/bin/sh -c VCPKG_FORCE_SYSTEM_BINARIES=1 /vcpkg/vcpkg install --triplet x64-linux-musl-static-release cpprestsdk[default-features,websockets] spdlog fmt]: exit code: 1

x64-linux-musl is the auto detected host triplet. Try setting it with --host-triplet=x64-linux-musl-static-release

Thank you for the reply. It only works if I set both the --triplet and --host-triplet flags.
FYI: Earlier versions of Vcpkg worked correctly with only the --triplet flag.

Yeah host triplets were introduced earlier this year.

Thank you for the advice.


SemanticUI Settings turn off css

Issue

Based on the usage configuration doc - scroll to bottom.
Expected to be able to turn off css import, however still getting included during ember serve.

var app = new EmberApp(defaults, {
  // Add options here
  SemanticUI: {
    import: {
      css: false
    }
  }
});

FYI seems to be fixed in the PR resulting from this duplicate issue (not yet merged) https://github.com/Semantic-Org/Semantic-UI-Ember/issues/231

I think this is fixed in #242

Yes will make a release


TyphoonConfig(key) return not updated value from application settings plist

Hey everyone!
Recently I’ve found some issue with Typhoon Configuration related to plists with default values. My application has dev settings which are used by testers for changing environment URL (production/sandbox, etc). These settings are stored in Settings.bundle within Xcode workspace. Settings.bundle contains defaultSettings.plist which stores values from dev settings. defaultSettings.plist is connected to Typhoon in order to use TyphoonConfig(key) method.
So, when I enter some new value into dev settings and restart application, TyphoonConfig(key) method gives me old value, not new one just entered.
What is wrong with my configuration?

Hi, @spbvasilenko! Can you provide a code for modifying your plist file?

Thanks for your answer, @igrekde. But recently I'm convinced that this is not a bug. When I enter some new value into dev settings, they stores not in plist. New values stores in NSUserDafaults. You can close this issue. Sorry :)

Great! Feel free to reopen the issue if you encounter it again!


Fix vkCmdCopyBuffer when copying unaligned regions.

This fixes #62.

Vulkan allows any valid copy regions to be used in this function. However, Metal's blit command encoder only allows copy offsets and sizes which are multiples of 4 bytes on macOS.
Before this change, attempting to copy such a region would cause Metal validation errors to trigger.
This adds logic to detect such copy regions and uses a special compute shader to perform a byte-by-byte copy from the source buffer to the destination buffer with the appropriate offsets.
This new code path is only needed on macOS, because iOS does not share the same copy region restrictions.

@billhollings This is my first submission, so please let me know if there's something I have missed, or something I should be doing differently. I've tried to match the patterns and style that are nearby.

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

@mellinoe
Good work! Thanks very much for taking the time to do this!
And thanks for following the established factory design pattern to keep it compatible with the other similar components.

@mellinoe
Can you test again under the code added in PR #104, please? See notes there. Thanks.


When selecting a specific font (MonoLisa), weird symbols instead of characters on latest insiders build

Does this issue occur when all extensions are disabled?: Yes

VS Code Version:
Version: 1.92.0-insider
Commit: 4d17e85cfd911fb6b116e08a4d7c37cd725a966a
Date: 2024-07-26T13:12:28.318Z (1 day ago)
Electron: 30.1.2
ElectronBuildId: 9870757
Chromium: 124.0.6367.243
Node.js: 20.14.0
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 23.5.0
OS Version: MacOS Sonoma 14.5

Steps to Reproduce:

Select MonoLisa font
Example:

Does the issue repro when you start the application with --disable-blink-features="FontMatchingCTMigration"

Looks like running with --disable-blink-features="FontMatchingCTMigration" fixes the issue

Thanks for confirming, seems like an issue in the runtime. Can you share the editor font settings as well

I don't have access to this specific font, can you try the following next steps to help us narrow down the issue in runtime

Open https://insiders.vscode.dev in latest Edge or Chrome
Use the font settings as the desktop application
Confirm if the issue is present

If the issue is not present, can you share the version of Chrome or Edge on which you had tested.

It works fine in the Arc Browser:
Version 1.54.0 (52220)
Chromium Engine Version 127.0.6533.89


FileTransform@1: [Feature Request] JSON case-insensitive substitution

Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Feature
Enter Task Name: FileTransform@1
Environment
Hosted Agent, though I'm pretty sure this is environment agnostic.
Issue Description
Is it possible to have JSON file substitution be case-insensitive (or at least add a flag for this)?
We have two sets of JSON configuration files; one for a SPA and another for an ASP.NET Core app.
In ASP.NET, names are usually upper-camel-case (ie. ConnectionStrings.Default), while in React, they are lower-camel-case (ie. connectionStrings.default).
Is it possible to add a flag that ignores capitalization as variables with different capitalization are treated as the same (the one defined last takes precedence as the final used value but the one defined first takes precedence in the name) in an Azure Pipeline YML?
Task logs
We had two jsons, one with:
{
    "connectionStrings": {
        "default": "connectionStrings.default"
    },
    "localization": {
        "en": "localization.en"
    }
}

and
{
    "ConnectionStrings": {
        "Default": "ConnectionStrings.Default"
    },
    "Localization": {
        "EN": "Localization.EN"
    }
}

and our pipeline had the variables connectionStrings.default and Localization.EN. In this case, we'll set them to I GOT SUBSTITUTED!, but usually a password or localization string goes in its place.
In case, the YML is:
# Starter pipeline
# Start with a minimal pipeline that you can customize to build and deploy your code.
# Add steps that build, run tests, deploy, and more:
# https://aka.ms/yaml

trigger:
- main

pool:
  vmImage: ubuntu-latest

steps:
- task: FileTransform@1
  inputs:
    folderPath: '$(System.DefaultWorkingDirectory)'
    fileType: 'json'
    targetFiles: '**.json'
- task: PublishBuildArtifacts@1
  inputs:
    PathtoPublish: '$(System.DefaultWorkingDirectory)'
    ArtifactName: 'results'
    publishLocation: 'Container'

and the results were incorrect, but as expected:
{
    "connectionStrings": {
        "default": "connectionStrings.default"
    },
    "localization": {
        "en": "I GOT SUBSTITUTED!"
    }
}

{
    "ConnectionStrings": {
        "Default": "I GOT SUBSTITUTED!"
    },
    "Localization": {
        "EN": "Localization.EN"
    }
}

You can see the repo here: https://dev.azure.com/timothychew0516/Test-Public/_git/case-insensitive-substitution
In case it wasn't clear, is it possible to get a feature that would render both variables in both files be "I GOT SUBSTITUTED"?
Basically this:
{
    "connectionStrings": {
        "default": "I GOT SUBSTITUTED!"
    },
    "localization": {
        "en": "I GOT SUBSTITUTED!"
    }
}

{
    "ConnectionStrings": {
        "Default": "I GOT SUBSTITUTED!"
    },
    "Localization": {
        "EN": "I GOT SUBSTITUTED!"
    }
}

Troubleshooting
There isn't an error since it's "working as expected".
Error logs
There isn't an error since it's "working as expected".

Hello,
Has there been any updates? Is it in progress or just backlogged?


Update for ember 4

Hi there,
is it planned to update this addon to ember 4?

Interested in this as well.

Any ember 4 updates in the works?

@neilthawani no, from what I've seen no updates are planned here. Suggestions are to copy using lodash libraries or other common approaches


Cargo fails to update Uiua with Access denied

Hello. I wanted to update Uiua, so I ran uiua update --main to update from GitHub. Then Cargo was doing great, until it was on the last step of moving the executable into place. Then it errored (username censored):
error: failed to move `C:\Users\******\.cargo\bin\cargo-installpuvWCb\uiua.exe` to `C:\Users\******\.cargo\bin\uiua.exe`

Caused by:
  Acesso negado. (os error 5)

Just in case, "Acesso negado" in Portuguese means "access denied". I pressed Ctrl-C, went to see if I could move manually, and what would you know; Cargo deleted the install folder. I'm on Windows, as you can see by the paths. Can anyone help?

This is likely because you have the Uiua process running somewhere.
The updater cannot replace the executable while it is running.

Ah, that's because I was in VSCode.😅
I did it in vanilla PowerShell and it worked.


Project dependencies - Css libraries

My suggestion is to remove styled-components and replace it with css modules.
By doing this, the initial project dependencies would be reduced and the user would be able to select a solution that is more suitable for the project's needs.

the project must be backward compatible, on all projects at the moment those packages are present I would avoid removing them lightly


fix: unwrap of code

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

65 of 65 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.08%) to 99.333%

Totals

Change from base Build<PHONE_NUMBER>:
0.08%

Covered Lines:
298

Relevant Lines:
300

💛  - Coveralls


system_tests_tcp_adaptor.TcpAdaptorStuckDeliveryTest.test_01_ignore_stuck_deliveries  is failing

https://github.com/skupperproject/skupper-router/actions/runs/11256661739/job/31317100321#step:10:3937
=========================================================================== FAILURES ===========================================================================
59: _________________________________________________ TcpAdaptorStuckDeliveryTest.test_01_ignore_stuck_deliveries __________________________________________________
59:
59: self = <tests.system_tests_tcp_adaptor.TcpAdaptorStuckDeliveryTest testMethod=test_01_ignore_stuck_deliveries>
59:
59:     @unittest.skipIf(DISABLE_SELECTOR_TESTS, DISABLE_SELECTOR_REASON)
59:     def test_01_ignore_stuck_deliveries(self):
59:         """
59:         Create a TCP delivery, wait for it to be classified as stuck and ensure
59:         that no stuck delivery logs are posted
59:         """
59:
59:         # step 1: create a TCP listener for interior to connect to
59:         try:
59:             server = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
59:             server.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR, 1)
59:             server.settimeout(TIMEOUT)
59:             server.bind(("", self.interior_tcp_connector_port))
59:             server.listen(10)
59:         except Exception as exc:
59:             print("%s: failed creating tcp server: %s" % (self.test_name, exc),
59:                   flush=True)
59:             raise
59:
59:         # step 2: initiate client connection to edge1. Since the listening
59:         # socket may not be immediately available allow for connection refused
59:         # error until it is ready. Should the listening socket fail to appear
59:         # the test will fail on timeout.
59:
59:         while True:
59:             client_conn = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
59:             client_conn.settimeout(TIMEOUT)
59:             try:
59: >               client_conn.connect(('<IP_ADDRESS>', self.edge_tcp_listener_port))
59: E               ConnectionRefusedError: [Errno 111] Connection refused
59:
59: /home/runner/work/skupper-router/skupper-router/skupper-router/tests/system_tests_tcp_adaptor.py:1320: ConnectionRefusedError
59:

From looking at the logs it appears as if the address watcher used by the tcpListener to instantiate the listening socket never fires.
We would expect that when the edge router establishes its sending link to the interior for the "nostuck" address then the creation of that link should fire the address watch indicating there is one local consumer. This never happens when this test fails.


use goreleaser to provide hypper builds

Uses the goreleaser action to build and
provide hypper builds for macos, linux, windows
in an automated fashion
Fixes: #95
Signed-off-by: Itxaka<EMAIL_ADDRESS>

@viccuad it runs on local with no issues (you only need to run --snapshot --skip-publish so it doesnt try to publish the artifacts)
In any case, other than for testing, Im not sure there is a necessity to run it locally as its only executed when new tags are pushed. Plus it needs a GITHUB_TOKEN in order to publish, so IMO its easier to skip any local facilities in the Makefile.

Plus it would be good for the whole process of releasing to have one source of truth and not be able to mix or overwrite releases because we are local testing :D

Sorry, I updated it to make the checksums and archive names more in sync with other projects in the same space.
Now uses - instead of _ in teh archive names and adds the v in front of the version for the archives. Also updates the checksum name file as well.

waiting for some tests offline before merging...

ok sorry about that, now it produces the same name for all archives, including checksums and source

I did some stalking and saw https://github.com/Itxaka/hypper/releases :D. Super nice!

added missing ldflags
@viccuad Those are the ones being set by goreleaser and work the same as the ones in the Makefile :D

lets gooooo


Refactor blog generator

The blog generator was split into three separate generators: feed, index and tags
Besides code reogranization, some obsolete code and useless functionality was deleted.
Fixed #81

Coverage increased (+1.99%) to 70.87% when pulling 99ef3b63acae7e5640a64dd2cf242bdcbc498e16 on blog_refactor into a70bbdd91e1cd1ed9ef521b73dc825e93c90f120 on master.

Coverage increased (+1.44%) to 70.33% when pulling 167f837fe69a8ed7b6bd51b68ee70980b94f9134 on blog_refactor into a70bbdd91e1cd1ed9ef521b73dc825e93c90f120 on master.

Coverage increased (+1.44%) to 70.33% when pulling cc74f1dfca28c56575f45f561934fcc6339e048c on blog_refactor into a70bbdd91e1cd1ed9ef521b73dc825e93c90f120 on master.

Coverage increased (+1.44%) to 70.33% when pulling cc74f1dfca28c56575f45f561934fcc6339e048c on blog_refactor into a70bbdd91e1cd1ed9ef521b73dc825e93c90f120 on master.


decrease log level

how can i reduce the log level in client (pinpoint-client) and server (pinpoint-collect/ file: catalina.out) ?My tests  are running out of space because logger are writing a lot.
thanks for all !

Hi,
For the agent, the log4j.xml is under $PINPOINT_AGENT/lib.
For the collector, you can set the log level by unzipping pinpoint-collector-$VERSION.war, modifying log4j.xml under WEB-INF/classes, then zipping it back up as a war file (If you downloaded the binary)
If you're building from source, you can just edit log4j.xml under collector/src/main/resources before building.
Let us know if you've more questions.
Thanks!

Great, thank you again.


Ensure that checkGrammarModuleElementContext reliably returns true when there is bad grammar

Fixes #11211

We will need to port this to release-2.0.5 as well.


Do not search when editing a new secret

When -c is given to edit skip searching for existing ones.
Fixes #1682
Signed-off-by: Dominik Schulz<EMAIL_ADDRESS>

Codecov Report

Merging #1683 (916517b) into master (6fae0c2) will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##           master    #1683   +/-   ##
=======================================
  Coverage   57.09%   57.09%
=======================================
  Files         205      205
  Lines        9808     9808
=======================================
  Hits         5599     5599
  Misses       3543     3543
  Partials      666      666

Impacted Files
Coverage Δ

internal/action/edit.go
44.44% <0.00%> (ø)

internal/store/leaf/list.go
60.00% <0.00%> (ø)

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 6fae0c2...916517b. Read the comment docs.

Codecov Report

Merging #1683 (916517b) into master (6fae0c2) will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##           master    #1683   +/-   ##
=======================================
  Coverage   57.09%   57.09%
=======================================
  Files         205      205
  Lines        9808     9808
=======================================
  Hits         5599     5599
  Misses       3543     3543
  Partials      666      666

Impacted Files
Coverage Δ

internal/action/edit.go
44.44% <0.00%> (ø)

internal/store/leaf/list.go
60.00% <0.00%> (ø)

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 6fae0c2...916517b. Read the comment docs.

Good point, thanks.

Good point, thanks.


Include remaining event types

PullRequestReviewCommentEvent
PublicEvent
GistEvent
CommitCommentEvent

see:
https://github.com/caseyscarborough/github-activity
https://developer.github.com/v3/activity/events/types/

PullRequestReviewCommentEvent wrapped on IssueCommentEvent


Show output from the runtime system process

The runtime BEAM process may produce some relevant output, for example if the runtime terminates due to a segfault, it would be helpful to know it's a segfault, while currently we only show that the runtime terminates unexpectedly. When we start the BEAM process we get a Port, so we could spawn a separate process that only listens to this port and logs any {:data, _} messages. Note that we want to avoid logs being duplicated.
Also, generally it may be useful to have a separate notebook side panel with relevant logs.

Perhaps it is also a good idea to include whenever there is a connection/disconnection/reconection in the logs, effectively keeping a history of the runtime. Given this is somewhat related to runtimes, maybe we want to hide this inside the runtime modal, but it may deserve its own section on the sidebar.


Adding network attribute to ILB "backend_service" to access multiNIC

Thanks for the PR! 🚀✅ Lint checks have passed.


Threshold limit on the amount the faucet can dispense to an account

Fixes #70
I've defaulted this to 100 but let me know if you prefer another limit

@chevdor what do you think, 100 is enough for the cap?

100 sounds like a reasonable value to get started yes.


Cursor jumps into statusline

environment

vim: Vim 8.1
vim-airline: c213f2ac44292a6c5548872e63acb0648cc07a9a
OS: macOS 10.14.5
Have you reproduced with a minimal vimrc: Yes
What is your airline configuration: Default
if you are using terminal:
terminal: iTerm2 Build 3.2.9
$TERM variable: xterm-256color
color configuration (:set t_Co?): 256

actual behavior

Install:

'vim-airline/vim-airline'
'airblade/vim-gitgutter'
'sjl/vitality.vim'

Open a git-managed file in Vim in iTerm 2
Enter command mode
Move focus to another program
Return focus to Vim

You will see that the mode changes from NORMAL to COMMAND and the cursor has jumped to the status line:

I believe that the combination of gitgutter, vitality, a git-managed file, and a focus change causes a statusredraw which triggers the buggy behavior.
expected behavior
The cursor should remain in the command line as it does when any of the three plugins mentioned above is not installed.

Please Report the exact vim version. Also please try with different terminals. I believe this is either a termcap issue or a vim bug

Am 01.08.2019 um 13:47 schrieb Bryan Enders<EMAIL_ADDRESS>environment
vim: Vim 8.1
vim-airline: c213f2a
OS: macOS 10.14.5
Have you reproduced with a minimal vimrc: Yes
What is your airline configuration: Default
if you are using terminal:
terminal: iTerm2 Build 3.2.9
$TERM variable: xterm-256color
color configuration (:set t_Co?): 256
actual behavior
Install:
'vim-airline/vim-airline'
'airblade/vim-gitgutter'
'sjl/vitality.vim'
Open a git-managed file in Vim
Enter command mode
Move focus to another program
Return focus to Vim
You will see that the mode changes from NORMAL to COMMAND and the cursor has jumped to the status line:
I believe that the combination of gitgutter, vitality, a git-managed file, and a focus change causes a statusredraw which triggers the buggy behavior.
expected behavior
The cursor should remain in the command line as it does when any of the three plugins mentioned above is not installed.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@chrisbra
VIM - Vi IMproved 8.1 (2018 May 18, compiled Mar 11 2019 08:36:40)
macOS version
Included patches: 1-1000
Compiled by Homebrew

I don’t have the issue in Terminal.app (and the mode indicator doesn’t switch from NORMAL to COMMAND), since the FocusGained event isn’t supported and so never fires. In MacVim, the mode indicator switches to COMMAND, but the cursor remains on the command line.
I tried wincent/terminus in place of sjl/vitality.vim which adds focus event support to both iTerm2 and Terminal.app. The buggy behavior remained in iTerm2 and spread to Terminal.app. There were no changes to MacVim with terminus.

As said, this is nothing I can fix from airline. This is either a Vim bug or a terminal bug.


Compiler: avoid gcc@* formula

We should never use gcc@* as the default compiler.
Otherwise, the bottle will be linked to the wrong gcc libraries.
This replaces #670, #674

This is also true for brew test-bot that it should always use gcc 5 to build bottles.

gcc@7 will not be installed on test-bot unless a formula depends_on "gcc@7".

To change the default behaviour is simple: export HOMEBREW_CC=gcc-5.

Also, this is not entirely true. Explicitly setting HOMEBREW_CC will bypass the compiler selection logics. For example, it will cause formula building to be failed if we support needs :cxx17.

Good point.

I'd like to know the extent to which GCC 5 and GCC 7 are ABI compatible.

From my understanding, it is not designed to work like this. That is GCC 7 should preserve backwards ABI compatibility to older version. But not the other way around, GCC 5 is never designed to maintain forwards ABI compatibility to newer version.

I'd like to know whether a C++ executable can be compiled with GCC 7 and linked against C++ libraries compiled with GCC 5 (and installed from bottles).
A more stressing test is whether a C++ executable can be compiled with GCC 5 (and installed from a bottle) and linked against C++ libraries compiled with GCC 7.
A quick litmus test I ran just now. A simple "Hello, world!" compiled with GCC 7 can be run using libstdc++.so.6 and libgcc_s.so.1 of GCC 5. That's not a comprehensive test, but a necessary one.

@sjackman I have updated the PR according to your suggestion.

I'm happy with the style of this PR. I'm not yet convinced that its purpose is necessary. If gcc@7 is installed on a user's system, perhaps it should be the default compiler. I'd like to know to what extent GCC 5 and GCC 7 are interoperable.
@iMichka Do you have an opinion?

I put
export HOMEBREW_CC=gcc-5
export HOMEBREW_CCX=g++-5

in my .zshrc. I have seen some packages fail to build with gcc7.
Not sure if it was due to a real failure to build with gcc7, or a mismatch between gcc5 bottles and gcc7 source builds. I am sorry, I did not take any notes about what packages were failing to build like this, but it happened 2-3 times in the last months on my Ubuntu 17.10.
I personally think the default compiler for Linuxbrew should be gcc (with gcc being gcc7). I do not know enough about ABI mismatches. Between gcc4 and gcc5 it was quite clear, because of the c++11 changes. Now, between gcc5 and gcc7, I do not know. I bet it is ABI compatible in theory, but in practice you may always stumble on some broken stuff.

If gcc@7 is installed on a user's system, perhaps it should be the default compiler, which is the current behaviour.

I don't think it should be like this. The reason is that gcc is kinda a special formula for Linuxbrew users. More specifically, we expect all users install gcc formula (or use system gcc). But there will be only a few users to install gcc@7.
For example, if we default to use gcc@7, it will cause break in the following situation:

User installs gcc@7 for a side project or temporary use.
User installs other formulae. As a result, these formulae will be built by gcc@7.
User finds that there is no use for gcc@7 at more. So brew uninstall gcc@7 is invoked.
The formulae built by gcc@7 may be broken.

I'd like to know to what extent GCC 5 and GCC 7 are interoperable / ABI compatible.

First of all, we should not use GCC 7 to build formulae and run them with GCC 5 libraries. This is forward compatibility (in contrast to the backward compatibility). And gcc is never being designed to work in this way.
Second, there are definitely some incompatible ABI changes. For example, C++17 vs C++11, OpenMP 4.0 vs 4.5.
Third, gcc ships many libraries. In fact, the libraries shipped in GCC 7 are different from the ones in GCC 5.
$ find $(brew --prefix gcc@7)/lib/ -name '*.so' -exec basename {} \; | uniq | sort | wc -l
19

$ find $(brew --prefix gcc)/lib/ -name '*.so' -exec basename {} \; | uniq | sort | wc -l
18

Ping @sjackman

Merged. Thanks for your contribution to Linuxbrew, @xu-cheng !


Pacemaker

Position target score and remove target graph

Make the score visible with and without NPS graph
Remove target graph code as it will not fit onto the screen — might revisit with a very narrow bar on the edge, later
Remove the option to select target score or data visualizations as neither will be properly visible

Please ignore the first commit — it's equivalent to the PR from target, and I will learn to git eventually :<

Is that position right? It looks good with background disabled but a bit weird with bg on

Nice catch, moved it up a bit.


SignUp Refactor

Overview:

Stripped SignUp to only require Email, Username, and Password
Created UserPropertyAvailabilityService and UserPropertyAvailabilityView to dynamically display Username and Email availability on SignUp
Created PreventDuplicateUsername rule on localUserDAO to prevent possible duplications
Gave StepWizardletView options to display in fullscreen, hide the close button, and disable back

Note: Needs to be Tested/Merged after #3717
Refs:
https://nanopay.atlassian.net/browse/NP-1198
https://nanopay.atlassian.net/browse/NP-1481
https://nanopay.atlassian.net/browse/NP-1587
https://nanopay.atlassian.net/browse/NP-1616
#TimeSpent: 23d

@googlebot I consent.


WSL not working after windows update

Windows Version
10.0.19045
WSL Version
<IP_ADDRESS>
Are you using WSL 1 or WSL 2?

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>
Distro Version
No response
Other Software
No response
Repro Steps
Any attempt to launch wsl is met with:
WslRegisterDistribution failed with error: 0x80370102
Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS.
For information please visit https://aka.ms/enablevirtualization
I have uninstalled all windows components and reinstalled. Turned virtualization off and back on in the bios. Everything.
Expected Behavior
Working wsl
Actual Behavior
Non working wsl
Diagnostic Logs
WslLogs-2023-06-11_12-37-18.zip

`FeatureName : Microsoft-Windows-Subsystem-Linux
State       : Enabled
FeatureName : HypervisorPlatform
State       : Enabled
FeatureName : Microsoft-Hyper-V-All
State       : Enabled
FeatureName : Microsoft-Hyper-V
State       : Enabled
FeatureName : Microsoft-Hyper-V-Tools-All
State       : Enabled
FeatureName : Microsoft-Hyper-V-Management-PowerShell
State       : Enabled
FeatureName : Microsoft-Hyper-V-Hypervisor
State       : Enabled
FeatureName : Microsoft-Hyper-V-Services
State       : Enabled
FeatureName : Microsoft-Hyper-V-Management-Clients
State       : Enabled`

Same issue here

same issue here

For anyone still dealing with this, I was able to resolve my issue by resetting windows as described here https://github.com/microsoft/WSL/issues/7183. I was able to keep all of my files and settings, so it wasn't a big deal though the issue was very troublesome. Once it was fixed and WSL was working, I just copied my old VM to the right location and it was back online.


Make licensed status detect dependencies that have been removed

Hello,
Would it be possible for licensed status to detect when a record exists for a dependency, but that dependency is not present anymore?
Thanks!

@Mathbl :wave: typically we expect that users will run the cache command after dependencies on a project change to update the stored record files, including removing any outdated record files.  Would that solve your need, or am I misunderstanding the request?

Indeed, cache will do the trick! Our use case is that our CI runs licensed status on push and will fail in case a dev forgot to run licensed cache, hence my request.
But, it can also be the dev responsibility to think about running the cache command when adding/removing dependency. You can close the issue if you feel like there is not much value for status to detect dependency removal 🙂.

Ahhh I see what you mean now.  From a usage perspective, would you want to see the status command treat these stale files as errors or warnings?  Errors are meant to be blocking and will cause the licensed status command to exit with a failing code (1), whereas warnings are meant to be non blocking and will return a success exit code.

Good question! In the case of a missing license/notice, it could cause legal issues, so throwing an error seems correct.
For an extra license/notice from a previously removed dependency, I guess this is less problematic.
If I only take our use case into account, I would like the CI build (running status) to fail, because if it's just a warning and the build succeed, the dev will probably not notice the warning at all.
What do you think?

Configuration option seems like a great idea. Thank you 😃

Opened https://github.com/github/licensed/pull/657 which adds the configuration option to ignore, warn, or error on "stale" metadata files from licensed status.

@Japottatweet :wave: you can configure the option in the licensed configuration file.  If the configuration option doesn't work please make sure you're using licensed v4.4.0 or greater 🙏


Error in imagenet/network-slimming

Two errors that I have found:

There is no --arch in prune.py, but it is used in README
There should be --prune in prune.py because it is used in the following code, see https://github.com/Eric-mingjie/rethinking-network-pruning/blob/master/imagenet/network-slimming/prune.py#L81

Did you test the code before the release?

Hi, Thanks for pointing out this issue! I just pushed a commit to fix this problem.


how to use ecapture with nodejs fetch and python urllib.request

I want to capture the http traffic in nodejs fetch and python urllib.request
run
sudo ecapture tls

first
then in node run
await globalThis.fetch('https://httpbin.org/ip').then(_ => _.json())

and ipython run
from urllib.request import urlopen
with urlopen("https://httpbin.org/ip") as response:
    print(response.read())

But I do not see anything print out under sudo ecapture tls, please help

for nodejs, I run LD_DEBUG=libs node and then
await globalThis.fetch('https://httpbin.org/ip').then(_ => _.json())

find library=libnss_mdns4_minimal.so.2 [0]; searching
    225365:	 search cache=/etc/ld.so.cache
    225365:	  trying file=/lib/x86_64-linux-gnu/libnss_mdns4_minimal.so.2
    225365:
    225365:
    225365:	calling init: /lib/x86_64-linux-gnu/libnss_mdns4_minimal.so.2

how to hook libnss_mdns4_minimal.so.2 in ecapture?
For python3, You said Python uses libssl.so to initiate HTTPS requests, but not the SSL_write function, instead it uses the SSL_write_ex function. The current version of eCapture has removed the HOOK code for the SSL_write_ex function. You can restore it yourself and then compile it again. Is there anyway not to recompile but pass parameter to ecapture command line?

Sorry, I have been on vacation recently and replied a bit late.
Currently, it is not possible to fix this issue through command line parameters.
The parameters of eCapture are already numerous, and there is no intention to add any more parameters.

For nodejs, any idea to fix the problem?

try ecapture nss --nspr=/lib/x86_64-linux-gnu/libnss_mdns4_minimal.so.2 .
If it still doesn't work, then you'll need to write the code yourself.

No response for more than 7 days


C++ methods should be searchable

To reproduce:
Try to search the web for "RunWithPriorityAndOptionsAsync". 0 hits on most engines.
(Though bing seems to have some smarts)
It seems this method has been projected as an overload of RunAsync. In general there
should be a way for people to find the right content using the interface names.
And when they get there, to see the projected vs raw names.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 8d09968d-d6f4-eee7-ff2c-943ceb4025c5
Version Independent ID: ac8915b6-a8ef-d629-0bef-c0e16293eff2
Content: ThreadPool Class (Windows.System.Threading) - Windows UWP applications
Content Source: https://cpubwin.visualstudio.com/DefaultCollection/windows-uwp/_git/winrt-api-build?path=%2fwinrt-api-build%2fwindows.system.threading.threadpool.yml&version=GBlive&_a=contents
Product: uwp
Git Login: drewbatgit
Microsoft Alias: drewbat

Thanks for your input. This will require some investigation and, potentially, an engineering fix. I've added this issue to our queue to investigate.


Data discrepancy found!

invalid year 3003 for Lost in Translation. Should be 2003 :-)

Thanks for info. The release year has been fixed with release 1.0.0


fix: dispose the this.documentListener

I'm not sure if I should submit a PR on master or elsewhere.
I'm fixing this issue :
Uncaught Exception:  Error: illegal state - object is disposed
Error: illegal state - object is disposed
    at r.e._checkDisposed (/usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:10:25284)
    at r.e.set (/usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:10:23310)
    at Socket.<anonymous> (/usr/share/code/resources/app/extensions/php/out/features/validationProvider.js:189:52)
    at emitNone (events.js:91:20)
    at Socket.emit (events.js:185:7)
    at endReadableNT (_stream_readable.js:974:12)
    at _combinedTickCallback (internal/process/next_tick.js:74:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)

Case to reproduce this error : extensionService.deactivate('vscode.php')

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

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

TTYL, MSBOT;


[🐛] Alternative solution for "Manipulate Basket"

:bug: Bug report
Description
There's an alternative solution for the "Manipulate Basket" challenge. This solution is, however, not recognized by the Juice shop.
So, I think this solution should be either recognized as the correct one, or it should not be allowed.
:microscope: Minimal Reproduction
1) Create new basket item
POST /api/BasketItems/
Content-type: application/json

{"quantity":3,"ProductId":19}
---
{"status":"success","data":{"id":21,"ProductId":19,"quantity":3,"updatedAt":"2020-08-26T22:22:36.821Z","createdAt":"2020-08-26T22:22:36.821Z"}}

The trick here is to delete the basketId property! New basket item is created with null basketId.
Just to confirm it:
GET /api/BasketItems/21
---
{"status":"success","data":{"id":21,"quantity":3,"createdAt":"2020-08-26T22:22:36.821Z","updatedAt":"2020-08-26T22:22:36.821Z","BasketId":null,"ProductId":19}}

2) Add basket item to basket
Now we can put the basket item into another user's basket (this wouldn't possible if the basket item had already been in someone's basket):
PUT /api/BasketItems/21
Content-type: application/json

{"BasketId":"8"}
---
{"status":"success","data":{"id":21,"quantity":3,"createdAt":"2020-08-26T22:22:36.821Z","updatedAt":"2020-08-26T22:23:45.932Z","BasketId":"8","ProductId":19}}

:deciduous_tree: Your Environment
Docker image, Juice shop version v11.1.3

Good catch, currently the challenge is only checked on POST requests. I'll check if adding the same logic to the PUT path will fix this without breaking anything else.

Hmm, thast PUT you're doing shouldn't even work... I just wrote a test reproducing your steps, but it kept getting 500 errors on that PUT. This is how the test passes:
  it('PUT update basket ID of basket item without basket ID is forbidden', () => {
    return frisby.post(API_URL + '/BasketItems', {
      headers: authHeader,
      body: {
        ProductId: 8,
        quantity: 8
      }
    })
      .expect('status', 200)
      .then(({ json }) => {
        expect(json.data.BasketId).toBeUndefined()
        return frisby.put(API_URL + '/BasketItems/' + json.data.id, {
          headers: authHeader,
          body: {
            BasketId: 42
          }
        })
          .expect('status', 500)
          .expect('json', { message: 'internal error', errors: ['SQLITE_CONSTRAINT: FOREIGN KEY constraint failed'] })
      })
  })

Any idea what might be different? I also tried passing the ID as a String, but that doesn't change the outcome.

Hi, maybe one of

Does basket with ID 42 exists?
I remember I was getting some errors if quantity > 5
I used basket ID as String, not Integer (not sure if it matters though)

It was 1.) ... 🤦♂


XCode 14.3 and Xamarin <IP_ADDRESS> on macos-12 images

Tool name
XCode and Xamarin.iOS
Tool license
Apple, inc
Add or update?

[ ] Add
[X] Update

Desired version
XCode 14.3, Xamarin.iOS <IP_ADDRESS>
Approximate size
No response
Brief description of tool
There's a breaking issue with Xamarin.iOS apps running on iOS 17 if they haven't linked away the references to deprecated NewsStand APIs.
Details can be seen here...
https://github.com/xamarin/xamarin-macios/issues/18964
A fix has been published in Xamarin.iOS <IP_ADDRESS> - which I think also requires Xcode 14.3
Are there plans to update the macos-12 image with this update?
Current the macos-12 image appears to have Xcode 14.2 installed and Xamarin.iOS <IP_ADDRESS>
URL for tool's homepage
No response
Provide a basic test case to validate the tool's functionality.
No response
Platforms where you need the tool

[X] Azure DevOps
[ ] GitHub Actions

Runner images where you need the tool

[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 11
[X] macOS 12
[ ] macOS 13
[ ] Windows Server 2019
[ ] Windows Server 2022

Can this tool be installed during the build?
No response
Tool installation time in runtime
No response
Are you willing to submit a PR?
No response

Hello! Xcode 14.3 requires macOS 13+ to be used, but at the time we do not have plans to provide Xamarin bundles in macOS13, that is why we are unable to assist here, if you want the fix to be available you should switch to macos13.
I'm going to close the issue for now, if you have more questions, feel free to reach us out again in this ticket.

Does macos-13 image have Xamarin support? It wasn't listed in the installed tools/libraries

@IainS1986 , you should be able to create a custom build step and install Xamarin bundles with boots.


SvelteKit - AreaSeries props not honored

Under SvelteKit, with 'lightweight-charts' excluded from SSR, like below:
const config = {
	kit: {
		adapter: adapter(),
		vite: {
			ssr: {
				noExternal: ['lightweight-charts']
			}
		}
	}
};

using:
<Chart height={280} width={220} {...theme.chart} ref={(ref) => (chartApi = ref)}>
	<AreaSeries
		{data}
		topColor="rgba(102, 102, 102, 0.56)"
		bottomColor="rgba(102, 102, 102, 0.04)"
		lineColor="rgba(171, 71, 188, 1)"
		lineWidth={2}
	/>
</Chart>

has no effects, i.e. custom colors are not applied.

Hi, do you have any errors in node console or in browser console?
Have you tried to import module with svelte-lightweight-chart dynamically?
{#await import('path to your chart component') then { default: ChartComponent } }
<ChartComponent/>
{/await}

I know that lightweight-charts (base package) does not support SSR. It fails even on simple import into node environment. This bug will be fixed in 4.0. I know some workarounds via webpack. I can try to find something for SvelteKit.

Well, no I did not load the component dynamically, as I try to use ResizeObserver to scale chart dynamically. But everything seems to work but the props mentioned.

And no, no errors on the console.

I tried to reproduce the problem, but everything is fine in my environment. I tried with adapter-node and adapter-auto.

There may be something wrong with other code. I'm guessing the issue might be with resize-observer or theme.chart. Could you please give a minimal reproduction or a bit more code for the chart in your project.

It turned out indeed using ResizeObserver (or rather calling chartApi.addAreaSeries(); was the problem. The solution is to call
chartApi.addAreaSeries((theme.series)

instead. Apologies for the false alarm.


Hide specific words

Feature Request
Problem.
Hey, I love this idea and would love to use it. Sadly it is currently quiet limited in it's functionality. With any language in general, this is a problem: There are words, which just appear very often.
Additionally, whenever other repeating content is present in files, those (obviously) overpower "normal" words. The dataview plugin, for example, allows to set attributes in the beginning of each file to later on formulate SQL querries based on these attributes. The downside: The top 100 used words are almost completely made up of the attribute keys, as they are constantly contained in every file, no matter the content.
Solution?
The easiest solution would probably be to make it possible to define a set of words that should be excluded in the search (either in the settings, or even simply in a config file). This way one could filer out unwanted words.
This of course could be then fitted with many options, like pre-defined top english words, or even being able to click directly on the graph. But that would all just be "extras". A simle config file with excluded words would already be enough.

Hello!
You make a very valid point, I will be working on this issue as soon as possible in the form of a word blacklist. I'll update you as soon as the feature has been deployed.

You should be able to update it now. If there are any issues or further requests, let me know.


Admin export confirm page runs a query for the entire table

When the export page is loaded, the code runs a query for the entire table of the model (i.e. the equivalent of SELECT * FROM table):
https://github.com/django-import-export/django-import-export/blob/9839a28089575baef1ecab686ab81682751ed761/import_export/admin.py#L736
When trying to export even a moderately sized table, which I think is a common scenario for django-import-export, such a query is very problematic, especially because it ignores any filtering on the queryset.
I'm not sure if this query is really intentional, but if it is, would it possible to add a way to turn it off?

Thanks for raising - you make a valid point.  I will take a look.

I have improved this in #1827

Thank you @matthewhegarty, I can confirm that this no longer happens with 4.0.2.

Thanks for raising and confirming fix


comoilation error for await keyword

Im using the below code to get the live stream but cant get to run the code.
Im relatively new to python.. Not sure what I am doing wrong here
from tastytrade.session import Session
from tastytrade.streamer import DataStreamer, EventType

session = Session('username', 'password')
streamer = await DataStreamer.create(session)
subs_list = ['SPY', 'SPX']

# this function fetches quotes once, then closes the subscription
quotes = await streamer.oneshot(EventType.QUOTE, subs_list)
print(quotes)

 python3 tasty.py
  File "tasty.py", line 5
    streamer = await DataStreamer.create(session)
               ^
SyntaxError: 'await' outside function

You can only use await in an async environment:
import asyncio
from tastytrade.session import Session
from tastytrade.streamer import DataStreamer, EventType

async def stream(session: Session):
  streamer = await DataStreamer.create(session)
  subs_list = ['SPY', 'SPX']
  # this function fetches quotes once, then closes the subscription
  quotes = await streamer.oneshot(EventType.QUOTE, subs_list)
  print(quotes)

session = Session('username', 'password')
asyncio.run(stream(session))

If you just want to play around with things, I'd suggest a Jupyter notebook which makes async pretty easy.

thanks... this worked..
is there a way/api to get the volume for all the strike prices for a ticker on a given day?

Great!
Yes, you'd need to do something like this:
from tastytrade.instruments import get_option_chain

chain = get_option_chain(session, 'SPLG')
subs_list = [o.streamer_symbol for o in chain[date]]

trades = await streamer.oneshot(EventType.TRADE, subs_list)
total_volume = 0
for t in trades:
    total_volume += t.dayVolume

Check the docs for more information about available streamer options, options chains, etc.


Update dev/demo dependencies

rand 0.7
rand_xorshift 0.2
glium 0.25

The only code churn is that Rng::sample_iter now takes self by value
instead of &mut self. So in some places we now had an unused mut, and
in others we need an explicit &mut to reach &mut R: Rng instead.

bors r+

Well that's annoying -- on Rust 1.26:
$ cargo build
    Updating registry `https://github.com/rust-lang/crates.io-index`
error: no matching package named `getrandom_package` found
location searched: registry `https://github.com/rust-lang/crates.io-index`
required by package `rand v0.7.0`
    ... which is depended on by `rayon-core v1.5.0 (file:///home/travis/build/rayon-rs/rayon/rayon-core)`
    ... which is depended on by `rayon v1.1.0 (file:///home/travis/build/rayon-rs/rayon)`
The command "cargo build" exited with 101.

Their use of dependency renaming (Rust 1.31) means it won't resolve for older Rust at all, even when we're trying to check a plain build without dev-dependencies.
So, this is blocked on our minimum Rust.

We could still update glium, but TBH that was kind of an afterthought in this PR.


Refactor: useAsync signature

Use an array signature for easier naming of returned variables
Pass a callback and the list of dependencies instead of useCallback

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

13 of 14 (92.86%)  changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.01%) to 36.911%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/routes/safe/components/Transactions/TxList/TxSingularDetails.tsx
0
1
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.01%

Covered Lines:
3836

Relevant Lines:
9457

💛  - Coveralls


Fix duplicated Traversy Media Youtube link

Currently the Youtube Channels list contains two links to Traversy Media's channel, one at the very top of the list and another one towards the end of the list, this pull request removes the second link.

Solved in https://github.com/markodenic/web-development-resources/pull/301


Flaky tests: RazorPagesTemplate_IndividualAuth_Works_NetFramework etc

I set:

RazorPagesTemplateTest.RazorPagesTemplate_IndividualAuth_Works_NetCore
RazorPagesTemplate_IndividualAuth_Works_NetFramework
MvcTemplate_IndividualAuth_Works_NetFramework
MvcTemplate_IndividualAuth_Works_NetCore

to ignore for now because they fail sometimes. It should be investigated and re-enabled once fixed.

Reverted for now: https://github.com/aspnet/templating/pull/294.
We will keep an eye on these (and skip again) and investigate if required.

@ryanbrandenburg @Eilon Closing for now. I'll reopen if we need to revert again.

Do we know anything about the cause? Did we change anything that would make us think they would no longer be flaky?

@javiercn can confirm but he made changes to the Identity UI package responding to RazorPages changes related to UI as a library. And the errors were:
Could not find the precompiled views assembly for 'Microsoft.AspNetCore.Identity.UI'

I believe I fixed this already during the weekend

Ah ok.

This was fixed


MINOR: Fix bug where we would incorrectly load partition reassignment info from ZK

Due to a typo in the initial PR, we would load the adding_replicas structure as the removing_replicas when loading reassignment info from ZK. This meant that API reassignments would not work during a failover.

cc @cmccabe

JDK 8 failure was unrelated -
kafka.api.GroupEndToEndAuthorizationTest.testNoDescribeProduceOrConsumeWithoutTopicDescribeAcl

org.scalatest.exceptions.TestFailedException: Consumed 0 records before timeout instead of the expected 1 records
	at org.scalatest.Assertions$class.newAssertionFailedException(Assertions.scala:530)

LGTM.  Thanks, @stanislavkozlovski

retest this please

Had a failure in the new test. Weird, I could swear I got it to pass the first time (how would I develop it otherwise)

LGTM


[Question]: Multithread VectorStoreIndex for PGVectoRsStore

Question Validation

[X] I have searched both the documentation and discord for an answer.

Question
I'm using PGVectoRsStore and creating a VectorStoreIndex. From the docs, I got this code:
from llama_index.core import SimpleDirectoryReader, VectorStoreIndex
from llama_index.vector_stores.pgvecto_rs import PGVectoRsStore

from llama_index.core import StorageContext

vector_store = PGVectoRsStore(client=client)
storage_context = StorageContext.from_defaults(vector_store=vector_store)
index = VectorStoreIndex.from_documents(
    docs, storage_context=storage_context
)

I'm using a Huggingface Embedding model to embed the docs with an embedding dimension of 768. I have over 400K docs that need to be embedded and it's running extremely slow. Is there a way to multi-thread this to speed up the performance?

You can't really multi-thread local embeddings. Or you kind of can, but each thread needs to have its own instance of the embeddings in memory (effectively creating X embedding models per X threads)
If you have the memory, you can increase the batch size on embeddings: HuggingFaceEmbedding(..., embed_batch_size=20)
If you aren't already running on a GPU, you'll also want that.
Tbh I would also maybe try using TEI, it's much more optimized. At the end of the day throughput is mostly limited by how much you can scale
https://docs.llamaindex.ai/en/stable/examples/embeddings/text_embedding_inference/?h=text+embedding+inference

I got it to finally increase the batch size in vectorstoreindex:
index = VectorStoreIndex.from_documents(
    docs, storage_context=storage_context, insert_batch_size=3000
)

If I increase it too high, I get CUDA out of memory.
Thanks for the help and I'll close the issue.


Bug on dart migrate tool (typedef causing it?)

We have a large project here and we migrated every single module we have except the last module, the app module that contains our main.dart file. That main module also is the module that have the dependency from every other module.
Some of our already migrate modules are using the new feature, typedefs for non function types available in flutter >=2.13.
If you pay attention to the log, it mentions the MoneyCents wich is a typedef MoneyCents = int; inside our core module.
After running dart migrate --skip-import-check this exception occurs:
Aborting migration due to an exception.  This most likely is due to a
bug in the migration tool.  Please consider filing a bug report at:

https://github.com/dart-lang/sdk/issues/new
Please include the SDK version (2.14.2) in your bug report.

To attempt to perform migration anyway, you may re-run with
--ignore-exceptions.

Exception details:

NoSuchMethodError: The getter 'library' was called on null.
Receiver: null
Tried calling: library at offset 572 in C:\path_to_the_project\lib\logic\home_bloc.dart (MoneyCents)

#0      Object.noSuchMethod (dart:core-patch/object_patch.dart:63:5)
#1      Variables._createDecoratedElementType (package:nnbd_migration/src/variables.dart:375:40)
#2      Variables.decoratedElementType (package:nnbd_migration/src/variables.dart:97:9)
#3      EdgeBuilder.visitTypeName (package:nnbd_migration/src/edge_builder.dart:1869:41)
#4      TypeNameImpl.accept (package:analyzer/src/dart/ast/ast.dart:10061:50)
#5      EdgeBuilder._dispatch (package:nnbd_migration/src/edge_builder.dart:2296:24)
#6      EdgeBuilder.visitNode (package:nnbd_migration/src/edge_builder.dart:1418:9)
#7      GeneralizingAstVisitor.visitFormalParameter (package:analyzer/dart/ast/visitor.dart:312:52)
#8      GeneralizingAstVisitor.visitNormalFormalParameter (package:analyzer/dart/ast/visitor.dart:465:7)
#9      GeneralizingAstVisitor.visitSimpleFormalParameter (package:analyzer/dart/ast/visitor.dart:517:7)
#10     SimpleFormalParameterImpl.accept (package:analyzer/src/dart/ast/ast.dart:8669:15)
#11     EdgeBuilder._dispatch (package:nnbd_migration/src/edge_builder.dart:2296:24)
#12     EdgeBuilder.visitNode (package:nnbd_migration/src/edge_builder.dart:1418:9)
#13     GeneralizingAstVisitor.visitFormalParameterList (package:analyzer/dart/ast/visitor.dart:315:60)
#14     FormalParameterListImpl.accept (package:analyzer/src/dart/ast/ast.dart:4406:50)
#15     EdgeBuilder._dispatch (package:nnbd_migration/src/edge_builder.dart:2296:24)
#16     EdgeBuilder.visitNode (package:nnbd_migration/src/edge_builder.dart:1418:9)
#17     GeneralizingAstVisitor.visitTypeAnnotation (package:analyzer/dart/ast/visitor.dart:576:50)
#18     GeneralizingAstVisitor.visitGenericFunctionType (package:analyzer/dart/ast/visitor.dart:363:7)
#19     GenericFunctionTypeImpl.accept (package:analyzer/src/dart/ast/ast.dart:5314:20)
#20     EdgeBuilder._dispatch (package:nnbd_migration/src/edge_builder.dart:2296:24)
#21     EdgeBuilder.visitNode (package:nnbd_migration/src/edge_builder.dart:1418:9)
#22     GeneralizingAstVisitor.visitAnnotatedNode (package:analyzer/dart/ast/visitor.dart:137:48)
#23     GeneralizingAstVisitor.visitDeclaration (package:analyzer/dart/ast/visitor.dart:235:44)
#24     GeneralizingAstVisitor.visitCompilationUnitMember (package:analyzer/dart/ast/visitor.dart:205:7)
#25     GeneralizingAstVisitor.visitNamedCompilationUnitMember (package:analyzer/dart/ast/visitor.dart:444:7)
#26     GeneralizingAstVisitor.visitTypeAlias (package:analyzer/dart/ast/visitor.dart:574:40)
#27     GeneralizingAstVisitor.visitGenericTypeAlias (package:analyzer/dart/ast/visitor.dart:366:54)
#28     GenericTypeAliasImpl.accept (package:analyzer/src/dart/ast/ast.dart:5403:20)
#29     EdgeBuilder._dispatch (package:nnbd_migration/src/edge_builder.dart:2296:24)
#30     EdgeBuilder.visitNode (package:nnbd_migration/src/edge_builder.dart:1418:9)
#31     GeneralizingAstVisitor.visitCompilationUnit (package:analyzer/dart/ast/visitor.dart:202:52)
#32     CompletenessTracker.visitCompilationUnit.<anonymous closure> (package:nnbd_migration/src/utilities/completeness_tracker.dart:52:24)
#33     PermissiveModeVisitor.reportExceptionsIfPermissive (package:nnbd_migration/src/utilities/permissive_mode.dart:26:24)
#34     CompletenessTracker.visitCompilationUnit (package:nnbd_migration/src/utilities/completeness_tracker.dart:43:5)
#35     CompilationUnitImpl.accept (package:analyzer/src/dart/ast/ast.dart:2060:50)
#36     NullabilityMigrationImpl.processInput (package:nnbd_migration/src/nullability_migration_impl.dart:231:12)
#37     NonNullableFix.processUnit (package:nnbd_migration/src/front_end/non_nullable_fix.dart:164:16)
#38     _FixCodeProcessor.runLaterPhases.<anonymous closure> (package:nnbd_migration/migration_cli.dart:1092:20)
#39     _FixCodeProcessor.runLaterPhases.<anonymous closure> (package:nnbd_migration/migration_cli.dart:1090:28)
#40     _FixCodeProcessor.processResources (package:nnbd_migration/migration_cli.dart:1024:26)
<asynchronous suspension>
#41     _FixCodeProcessor.runLaterPhases (package:nnbd_migration/migration_cli.dart:1090:5)
<asynchronous suspension>
#42     MigrationCliRunner.run (package:nnbd_migration/migration_cli.dart:697:24)
<asynchronous suspension>
#43     MigrateCommand.run (package:dartdev/src/commands/migrate.dart:37:7)
<asynchronous suspension>
#44     CommandRunner.runCommand (package:args/command_runner.dart:209:13)
<asynchronous suspension>
#45     DartdevRunner.runCommand (package:dartdev/dartdev.dart:202:18)
<asynchronous suspension>
#46     runDartdev (package:dartdev/dartdev.dart:54:16)
<asynchronous suspension>
#47     main (file:///C:/b/s/w/ir/cache/builder/sdk/pkg/dartdev/bin/dartdev.dart:11:3)
<asynchronous suspension>

And this is my flutter doctor:
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 2.5.1, on Microsoft Windows [versÃ£o 10.0.19043.1237], locale pt-BR)
[√] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
[√] Chrome - develop for the web
[√] Android Studio (version 2020.3)
[√] IntelliJ IDEA Community Edition (version 2021.2)
[√] Connected device (3 available)

• No issues found!

Hi @shinayser,
I ran into the same issue today. Did you find any way around this or better: a fix?
For me it's probably not related to typedefs, since I don't use them.
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 2.10.3, on Microsoft Windows [Version 10.0.17763.2686], locale de-DE)
[√] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
[√] Chrome - develop for the web
[√] Visual Studio - develop for Windows (Visual Studio Community 2019 16.11.5)
[√] Android Studio (version 2020.3)
[√] Android Studio (version 4.2)
[√] Android Studio
[√] VS Code (version 1.65.2)
[√] Connected device (2 available)
[√] HTTP Host Availability

Best regards

Yes. We removed our typedefs. Then we migrate the test of the app.
Only after the num safety was entirely migrated, we then added back our typedefs.

Unassigning myself because I'm not actively working on the migration tool right now.

As of 1c7fe7196dd7a542f7f91cd6ea2ac81e1a13146c, the null safety migration tool has been removed from active development and retired. No further work on the tool is planned.
If you still need help, or you believe this issue has been closed in error, please feel free to reopen.


 Unable to continue with install: CustomResourceDefinition "onepassworditems.onepassword.com" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-namespace" must equal "qa": current value is "dev"

What did you expect to happen?

The second install command with skip-crds would not create the CRD again
Steps to reproduce

Create two environments for connect on 1password
generate a token and credentials for each
create two namespces
deploy connect with the operator to the first namespace
attempt to create the operator in a second namespace
Notes & Logs

Not entirely sure if this is me missing something obvious or wether it's the checks for those annotiation labels causing the issues.  Essentially we have 4 isolated namespaces in our cluster.  We want to have 4 environments each with it's own access-token and credentials which has access to a single vault for (one per namespace)

I think this is because the CRD is defined in the helm templates dir instead of in the Helm 3-standard crds dir. I've opened a PR on the Helm charts repo to address this.


Add option to perform dummy entries

Add the option to add datasets to the registry, without needing any actual data.
Used for debugging, testing and CI.
Idea:

Envisioned as a flag on dataset registry, --dummy or similar.
Add a row to the dataset column to say if that dataset is a true or dummy dataset

Added feature to u/stuart/query_api_dummy_entry branch, (which is based off the u/stuart/query_api_metadata branch)
When registering a dataset can include the --is_dummy flag. No data needs to exist or will be copied, just a dummy entry created in the dataset table.
There is a new dataset_organization type called "dummy" (as opposed to "file" "directory")
Will merge this in after the dataset branch is merged


Scroll loading on collection

once the end is reached and you want to scroll up, there is a weird event when it removes some items, than add them again, hover them all and again.
see video:
https://user-images.githubusercontent.com/90852205/232286855-8bae145e-a0b6-450d-9935-a32358d5d446.mov
tested here: https://canary.kodadot.xyz/ksm/collection/a0c4801b6dbf04c674-P1Z70?listed=true&sort=price_ASC

infinity scroll booty call

I seem could not reproduce the scroll bug on my side.

@Jarsen136 dont scroll continuously, the thing is that its loading in a weird way, just wait on the end a bit, once it loads scroll down, wait, scroll up - still happens to me, try that on explore as well

@Jarsen136 dont scroll continuously, the thing is that its loading in a weird way, just wait on the end a bit, once it loads scroll down, wait, scroll up - still happens to me, try that on explore as well

I did scroll down and wait on the end for a while, but still could not reproduce it. I guess it's a compatibility issue related to Windows OS or browser.

@Jarsen136 I am on osx, chrome

I have the same issue when I tried to sort Kusama NFTs by price low.
https://user-images.githubusercontent.com/104380776/233967354-4f36b401-56ac-42b7-add8-40bfeb87f8ff.mov

closed by #7110


attribute renovation for construction elements

renovation date for construction elements - reason of renovation should be stored
see Energy ADE: http://en.wiki.energy.sig3d.org/index.php/Main_Page
OR
more General: important Event in the life time of a Building.
construction, renovation, demolition,
Date, meaning, free text?

issues #27 "consider offering the possibility to provide Building Events...

In the web conference on 7 March 2019 we discussed and decided on removing the attribute dateOfRenovation.
Instead, we will add an attribute constructionEvent with multiplicity [0..*] that allows for defining the type of event (attribute event) via values defined in a code list (e.g. building permit, start of renovation, end of renovation), the date of event (attribute dateOfEvent) and for providing additional information on the event (attribute description).


Export BaseIssueDetector?

Would love to make my own custom detectors that follow the format of the provided issue detectors. However, it looks like the library does not export the BaseIssueDetector that every detector extends.
Would it be possible to export this so that custom detectors can extend it and take advantage of the pre-defined class functions?
Thanks!

Hi @MFarejowicz ! Of course, created the PR, will notify you here when the the release is built.

@MFarejowicz thanks for pointing this out, missed it

Thanks for the quick response. The file actually already exported it, but I think we also want to add a line for it in here: https://github.com/VLprojects/webrtc-issue-detector/blob/master/src/detectors/index.ts, so that it'll get exported from the base index.ts?

Yes) Because of the hurry missed that there's already export expression. Will make the changes soon in index.ts

@MFarejowicz Done. Added export to https://github.com/VLprojects/webrtc-issue-detector/blob/master/src/detectors/index.ts#L1.
You can use the latest 1.9.2 version to check it

Resolved in this commit:
https://github.com/VLprojects/webrtc-issue-detector/pull/18/commits/46ebb2dc72ad3ddc67dd212d119bf4f4eddd9afe

Thank you 🙏


feat: port GroupTheory.FreeAbelianGroup

Remaining task:

Fix error in FreeAbelianGroup.lift.of

bors r+

bors crashed
bors r-
bors r+


Update document of Post-install steps for expo user

I dig in with the problem here #209 . After plenty of hours, I finally work through it.
As the author mention in Post-install steps Android must update AndroidManifest.xml. But in the Expo section it only says how it works on iOS, doesn't mention how to work on android while using Expo.
So I searched how to change AndroidManifest.xml file in Expo. And the answer is using plugins, but this only work on Expo SDK 41 or greater, please check for the SDK first.
So follow the steps below:

create a file called withAndroidPackageVisibile.js, and paste this to the file. This will write the same AndroidManifest.xml mention in Post-install steps Android steps.

const { withAndroidManifest } = require("@expo/config-plugins");

module.exports = function androidManifestPlugin(config) {
  return withAndroidManifest(config, async (config) => {
    let androidManifest = config.modResults.manifest;
    androidManifest["queries"] = [
      ...androidManifest["queries"],
      packageVisibilityList,
    ];
    return config;
  });
};
const packageVisibilityList = {
  intent: [
    {
      action: {
        $: {
          "android:name": "android.intent.action.VIEW",
        },
      },
      data: {
        $: {
          "android:scheme": "geo",
        },
      },
    },
    {
      action: {
        $: {
          "android:name": "android.intent.action.VIEW",
        },
      },
      data: {
        $: {
          "android:scheme": "google.navigation",
        },
      },
    },
    {
      action: {
        $: {
          "android:name": "android.intent.action.VIEW",
        },
      },
      data: {
        $: {
          "android:scheme": "applemaps",
        },
      },
    },
    {
      action: {
        $: {
          "android:name": "android.intent.action.VIEW",
        },
      },
      data: {
        $: {
          "android:scheme": "citymapper",
        },
      },
    },
    {
      action: {
        $: {
          "android:name": "android.intent.action.VIEW",
        },
      },
      data: {
        $: {
          "android:scheme": "uber",
        },
      },
    },
    {
      action: {
        $: {
          "android:name": "android.intent.action.VIEW",
        },
      },
      data: {
        $: {
          "android:scheme": "lyft",
        },
      },
    },
    {
      action: {
        $: {
          "android:name": "android.intent.action.VIEW",
        },
      },
      data: {
        $: {
          "android:scheme": "transit",
        },
      },
    },
    {
      action: {
        $: {
          "android:name": "android.intent.action.VIEW",
        },
      },
      data: {
        $: {
          "android:scheme": "truckmap",
        },
      },
    },
    {
      action: {
        $: {
          "android:name": "android.intent.action.VIEW",
        },
      },
      data: {
        $: {
          "android:scheme": "waze",
        },
      },
    },
    {
      action: {
        $: {
          "android:name": "android.intent.action.VIEW",
        },
      },
      data: {
        $: {
          "android:scheme": "yandexnavi",
        },
      },
    },
    {
      action: {
        $: {
          "android:name": "android.intent.action.VIEW",
        },
      },
      data: {
        $: {
          "android:scheme": "moovit",
        },
      },
    },
    {
      action: {
        $: {
          "android:name": "android.intent.action.VIEW",
        },
      },
      data: {
        $: {
          "android:scheme": "yandexmaps://maps.yandex.",
        },
      },
    },
    {
      action: {
        $: {
          "android:name": "android.intent.action.VIEW",
        },
      },
      data: {
        $: {
          "android:scheme": "yandextaxi",
        },
      },
    },
    {
      action: {
        $: {
          "android:name": "android.intent.action.VIEW",
        },
      },
      data: {
        $: {
          "android:scheme": "kakaomap",
        },
      },
    },
    {
      action: {
        $: {
          "android:name": "android.intent.action.VIEW",
        },
      },
      data: {
        $: {
          "android:scheme": "mapycz",
        },
      },
    },
    {
      action: {
        $: {
          "android:name": "android.intent.action.VIEW",
        },
      },
      data: {
        $: {
          "android:scheme": "mapsme",
        },
      },
    },
    {
      action: {
        $: {
          "android:name": "android.intent.action.VIEW",
        },
      },
      data: {
        $: {
          "android:scheme": "osmand.geo",
        },
      },
    },
    {
      action: {
        $: {
          "android:name": "android.intent.action.VIEW",
        },
      },
      data: {
        $: {
          "android:scheme": "gett",
        },
      },
    },
    {
      action: {
        $: {
          "android:name": "android.intent.action.VIEW",
        },
      },
      data: {
        $: {
          "android:scheme": "nmap",
        },
      },
    },
    {
      action: {
        $: {
          "android:name": "android.intent.action.VIEW",
        },
      },
      data: {
        $: {
          "android:scheme": "dgis",
        },
      },
    },
  ],
};

Then switch to app.json and change the following

{
  "expo": {
      ...
    "plugins": [
        ... ,
        "./the/path/to/withAndroidPackageVisibile.js"
      ]
  }
}

Finally re-build the app, I only test on eas build. I can't assure there is no problem with expo build.

You can learn more about how to use plugins in here.
Happy coding guys!

Hi,
It still won't open for me. Are there any permission that need to be added?

Hi, It still won't open for me. Are there any permission that need to be added?

@emehmet I didn't add any extra permission, so I recommend you to check if AndroidManifest.xml has correctly been changed. You can check it by below.
You can first type expo eject in the command line. Then find AndroidManifest.xml under android folder and check for if the permission is like this.
By doing this you can check if withAndroidPackageVisibile.js works like what you want.

I dig in with the problem here #209 . After plenty of hours, I finally work through it. As the author mention in Post-install steps Android must update AndroidManifest.xml. But in the Expo section it only says how it works on iOS, doesn't mention how to work on android while using Expo.
So I searched how to change AndroidManifest.xml file in Expo. And the answer is using plugins, but this only work on Expo SDK 41 or greater, please check for the SDK first.
So follow the steps below:

create a file called withAndroidPackageVisibile.js, and paste this to the file. This will write the same AndroidManifest.xml mention in Post-install steps Android steps.

const { withAndroidManifest } = require("@expo/config-plugins");

module.exports = function androidManifestPlugin(config) {
  return withAndroidManifest(config, async (config) => {
    let androidManifest = config.modResults.manifest;
    androidManifest["queries"] = [
      ...androidManifest["queries"],
      packageVisibilityList,
    ];
    return config;
  });
};

thanks for your solution but it seems should modify it a little bit here.
module.exports = function androidManifestPlugin(config) {
   return withAndroidManifest(config, async (config) => {
     let androidManifest = config.modResults.manifest;
     androidManifest["queries"] = [
       ...androidManifest["queries"],
       packageVisibilityList,
     ];

     config.modResults.manifest = androidManifest; // here

     return config;
   });
 };

It worked for me when I deleted node_modules and build again with eas build on development-client.

Thanks, I will have to migrate the project to EAS cli, I will post an update if it is working on EAS build. (it may take few days as  it's not a priority for now).

I think this is now resolved, but please do feel free to open a PR if more changes are needed. Thanks everyone!

This appears to be right with one issue I keep running across: there are duplicate query keeps in the AndroidManifest.xml after following the post install steps here.
With duplicate query keys, the app is not installable on devices w/ a silent fail.

Do you think this is due to a bug in the Expo plugin? Or is it because of following both the Android instructions + Expo instructions from the README?

@tschoffelen thanks for the quick reply. It is due to my misunderstanding of the js -> xml conversion I think. Using the above code in this (old) comment ended up with duplicate query keys which broke installs like I mentioned.
The duplicate query keys were happening when adding map intents to the existing query key as such
androidManifest["queries"] = [
      ...androidManifest["queries"],
      packageVisibilityList,
    ];

I updated that piece to concat the first intent with the intents the app required to open map apps on Android.
const supportedApps = [
  "geo",
  "google.navigation",
  "waze",
  "lyft",
  "uber",
  "transit",
];

const mapAppIntents = supportedApps.map((app) => {
  return {
    action: {
      $: { "android:name": "android.intent.action.VIEW" }
    },
    data: {
      $: { "android:scheme": app },
    },
  };
});

module.exports = function androidManifestPlugin(config) {
  return withAndroidManifest(config, async (config) => {
    const androidManifest = config.modResults.manifest;
    const existingIntent = androidManifest.queries[0].intent;

    androidManifest.queries[0].intent = existingIntent.concat(mapAppIntents); <-- modification

    return config;
  });
};

Oh amazing! Would you be able to open a PR to get this change merged in?


DESIGN -> DSIGN

The cardano-crypto-class source contains a number of occurrences of encodedSignKeyDESIGNSizeExpr which should clearly be encodedSignKeyDSIGNSizeExpr (see https://github.com/input-output-hk/cardano-base/issues/275).  This fixes that.

@lehins @michaelpj


Add unused seed peers to the AddressBook

Motivation
As described in #2931, Zebra drops some initial peers, but these peers could be useful to connect to.
Solution
This PR adds the unused peers from add_initial_peers to the address_book.
Will close #2931.

All new suggestions have been implemented.


Title bar changes for MetroWindow

I made some changes regarding the title bar of MetroWindow:

title bar is now part of the MetroWindow template
window icon can be displayed in title bar
window can be moved only when clicking the title bar

Found a bug, if you change tabs in the demo app, the title bar disappears. If you then change the theme, it reappears and seems to stick.
I like the idea of the titlebar but for all apps/windows, it isn't needed - for example, all the dialogs in MarkPad could (will?) use MetroWindow, but none of them have/want a titlebar. Could you add in another boolean (ShowTitlebar perhaps) to toggle it on off?
Other than those two little niggles, looking great :)

I'll look into this bug.
Regarding the ShowTitlebar flag: I'd like to set it to true per default. Is that ok for you?

Awesome on both acounnts @thoemmi. Looks like we might have a new release candidate :D


Add MinimalTlsVersion Property to MI and Sql DB APIs

Test generation is pending our Prod deployment. ETA 2/28

@erich-wang Also want to commen that running generate.ps1 is broken now as it keeps trying to pass in the latest for verison parameter when calling autorest. I have to run the following cmd manually:
cmd.exe /c autorest.cmd https://github.com/Azure/azure-rest-api-specs/blob/master/specification/sql/resource-manager/readme.md --csharp --reflect-api-versions --csharp-sdks-folder=.

@erich-wang Also want to commen that running generate.ps1 is broken now as it keeps trying to pass in the latest for verison parameter when calling autorest. I have to run the following cmd manually:

Thanks for the feedback! Could you share more info about how generate.ps1 was broken? What was the error?

@erich-wang Also want to commen that running generate.ps1 is broken now as it keeps trying to pass in the latest for verison parameter when calling autorest. I have to run the following cmd manually:

Thanks for the feedback! Could you share more info about how generate.ps1 was broken? What was the error?

error is:
Write-ErrorLog : FATAL: System.InvalidOperationException: Found incompatible property types ,  for property 'type' in schema inheritance chain
at AutoRest.Modeler.SchemaResolver.ExpandAllOf(Schema schema) in /opt/vsts/work/1/s/src/SchemaResolver.cs:line 157
at AutoRest.Modeler.SchemaResolver.Unwrap(Schema schema) in /opt/vsts/work/1/s/src/SchemaResolver.cs:line 75
at AutoRest.Modeler.SchemaBuilder.BuildServiceType(String serviceTypeName, Boolean required) in /opt/vsts/work/1/s/src/SchemaBuilder.cs:line 35
at AutoRest.Modeler.SwaggerModeler.BuildCompositeTypes() in /opt/vsts/work/1/s/src/SwaggerModeler.cs:line 348
at AutoRest.Modeler.SwaggerModeler.Build(ServiceDefinition serviceDefinition) in /opt/vsts/work/1/s/src/SwaggerModeler.cs:line 66
at AutoRest.Modeler.Program.d__2.MoveNext() in /opt/vsts/work/1/s/src/Program.cs:line 60
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NewPlugin.d__15.MoveNext()
Error: Plugin imodeler1 reported failure.
At C:\Users\ziwa\Documents\WindowsPowerShell\Modules\CodeGenerationModules\AutoRestCodeGenerationModule\AutoRestCodeGenerationModule.psm1:104 char:5

Write-ErrorLog $stderr

~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Write-ErrorLog

@erich-wang Also want to commen that running generate.ps1 is broken now as it keeps trying to pass in the latest for verison parameter when calling autorest. I have to run the following cmd manually:

Thanks for the feedback! Could you share more info about how generate.ps1 was broken? What was the error?

It is due the fact that latest is passed in as an parameter when running the script for --version:
cmd.exe /c autorest.cmd https://github.com/Azure/azure-rest-api-specs/blob/master/specification/sql/resource-manager/readme.md --csharp --version=latest --reflect-api-versions --csharp-sdks-folder=.
I unblocked myself by running without --version=latest

It looks like the build is still failing:
Tried to execute:
msbuild build.proj /t:Build /p:Scope=SqlManagement

Got the following error:
"D:\AzureGit\ziwa\azure-sdk-for-net\build.proj" (Build target) (1) ->
"D:\AzureGit\ziwa\azure-sdk-for-net\eng\mgmt.proj" (default target) (2) ->
"D:\AzureGit\ziwa\azure-sdk-for-net\sdk\SqlManagement\Microsoft.Azure.Management.SqlManagement\src\Microsoft.Azure.Management.Sql.csproj" (default target) (3:27) ->
"D:\AzureGit\ziwa\azure-sdk-for-net\sdk\SqlManagement\Microsoft.Azure.Management.SqlManagement\src\Microsoft.Azure.Management.Sql.csproj" (Build target) (3:29) ->
  Generated\SqlManagementClient.cs(493,24): error CS0246: The type or namespace name 'ILongTermRetentionManagedInstanceBackupsOperations' could not be found (are you missing a using directive or an assembly reference?) [D:\AzureGit\ziwa\azure-sdk-for-net\sdk\SqlManagement\Microsof
t.Azure.Management.SqlManagement\src\Microsoft.Azure.Management.Sql.csproj]
  Generated\SqlManagementClient.cs(498,24): error CS0246: The type or namespace name 'IManagedInstanceLongTermRetentionPoliciesOperations' could not be found (are you missing a using directive or an assembly reference?) [D:\AzureGit\ziwa\azure-sdk-for-net\sdk\SqlManagement\Microso
ft.Azure.Management.SqlManagement\src\Microsoft.Azure.Management.Sql.csproj]
  Generated\SqlManagementClient.cs(503,24): error CS0246: The type or namespace name 'IWorkloadGroupsOperations' could not be found (are you missing a using directive or an assembly reference?) [D:\AzureGit\ziwa\azure-sdk-for-net\sdk\SqlManagement\Microsoft.Azure.Management.SqlMan
agement\src\Microsoft.Azure.Management.Sql.csproj]
  Generated\SqlManagementClient.cs(508,24): error CS0246: The type or namespace name 'IWorkloadClassifiersOperations' could not be found (are you missing a using directive or an assembly reference?) [D:\AzureGit\ziwa\azure-sdk-for-net\sdk\SqlManagement\Microsoft.Azure.Management.S
qlManagement\src\Microsoft.Azure.Management.Sql.csproj]
  Generated\SqlManagementClient.cs(30,84): error CS0535: 'SqlManagementClient' does not implement interface member 'ISqlManagementClient.ManagedDatabaseRestoreDetails' [D:\AzureGit\ziwa\azure-sdk-for-net\sdk\SqlManagement\Microsoft.Azure.Management.SqlManagement\src\Microsoft.Azur
e.Management.Sql.csproj]

@isra-fel Can you advise on why the generated code has errors, preventing the build to be successful?

You likely want to usee --version-V2 when running this - this is what the SDK automation is currnetly doing, it uses the 2.x version fo autorest-core.

You likely want to usee --version-V2 when running this - this is what the SDK automation is currnetly doing, it uses the 2.x version fo autorest-core.

 Hopefully it solves the issue. But for some reason each iteration is taking ~3 hours which is not expected.

You likely want to usee --version-V2 when running this - this is what the SDK automation is currnetly doing, it uses the 2.x version fo autorest-core.

 Hopefully it solves the issue. But for some reason each iteration is taking ~3 hours which is not expected.

Just synced with another team member and he suggested to use the following:
Start-AutoRestCodeGeneration -ResourceProvider "sql/resource-manager" -SdkRepoRootPath "." -AutoRestVersion "2.0.4413"
Retrying now.


Add --all-features flag to cargo

As (more or less) requested in #1173 I added a --all-features flag to cargo that builds all available features.
I hope I documented it in all the right places.
If there's something weird or wrong, please give me a heads up.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @alexcrichton (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

Thanks for the PR @esclear! Looking pretty good to me, but the println! may want to get converted into actually enabling all features? Can you also be sure to add some tests for this functionality as well?
cc @rust-lang/tools, a new flag to cargo

Well…
It does enable all featues, since it overwrites the features vec.
But you're right, one wouldn't want to see this kind of debugging information :flushed:.
I'll try to think of some test and get back to this PR.
Am 26. August 2016 01:48:26 MESZ, schrieb Alex Crichton<EMAIL_ADDRESS>
Thanks for the PR @esclear! Looking pretty good to me, but the
println! may want to get converted into actually enabling all
features? Can you also be sure to add some tests for this functionality
as well?
cc @rust-lang/tools, a new flag to cargo
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/rust-lang/cargo/pull/3038#issuecomment-242581393

--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

@alexcrichton Removed the println! and added a simple test.

Seems reasonable to me given the current design of features. It might be worth considering how this plays out with any future changes to cargo features. For example, some features may be mutually-incompatible. Cargo has no way to encode that today, but maybe not forever.

Given that exclusive features are already being discussed in #2980 this should be considered.
My main intent behind this flag was to simplify enabling all features while building crate documentation or testing.
I think in that case you'd still want all features to be built.
On the other hand, there might be problems when testing with exclusive features enabled.
In my opinion, the user would have to enable all of the needed features manually if there are any exclusive features.
In case one uses the --all-features flag when building a crate with exclusive features, cargo should warn the user and stop.

Looking good! I think though that this'll also need to enable any optional dependencies as well as [feature]-style features. Perhaps this could look into using Method::Everything as that should enable all features by default as well?

Could you also add a test for an optional dependency getting activated as well?

(other than that though looks good to me)

Thanks! Could you squash the commits down as well?

I'll try, eventhough I merged multiple times now.

After some manual rebasing it should be fine now.

@bors: r+ 1f8b398802d6bb78d7d8d32415967b85662cd3c8
Thanks!

:hourglass: Testing commit 1f8b398 with merge e713e7f...

:sunny: Test successful - cargo-cross-linux, cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-gnu-32, cargo-win-gnu-64, cargo-win-msvc-32, cargo-win-msvc-64
Approved by: alexcrichton
Pushing e713e7fa33ca502779cee4a17dbb9f7cd05e0594 to master...


Feature Request: Bot Builder Composer with Custom Adapter sample

Use this query to search for the most popular feature requests.
Is your feature request related to a problem? Please describe.
No, just something I am trying to see how it could be done, cant find any concrete examples
Describe the solution you'd like
Echobot with adapter to one of whatsapp/sms/etc
Describe alternatives you've considered
Not using bot framework composer
Additional context
I am exploring possiblities with bot framework composer and checking how hard it is to add custom adapters

The Bot Builder Community has created custom adapters for some services, which you can find in their Github repo, along with implementation instructions. Do note that since these are Community adapters, Microsoft will not directly support them.