target check: rework specs, refine messaging

Re-works the specs to add layers of conditions, which ensures we capture all of the edge-cases we are looking to specify.
In doing so, I discovered that the messaging I suggested earlier in some cases was less helpful than it could be 🤦🏼♂  so I introduced a new message for when (a) ECS is enabled and (b) the target is unspecified and (c) the codec supports a target but it isn't specified there either. This message encourages them to jump straight to configuring the codec. In theory, they will get a companion log message from the codec (if it uses this library), but I figured both together will be helpful.
I also memoised the calls to target_set? and codec_target_set? to local variables so we can avoid calling them repeatedly.
logstash_1  | LogStash::PluginMixins::ECSCompatibilitySupport::TargetCheck
logstash_1  |   with a plugin
logstash_1  |     filter
logstash_1  |       ECS disabled
logstash_1  |         does not log info about setting the target
logstash_1  |       ECS enabled
logstash_1  |         when target not set
logstash_1  |           emits a helpful info log
logstash_1  |         when target is provided
logstash_1  |           does not emit an info log about setting the target
logstash_1  |     input
logstash_1  |       when configured with a codec that does not support `target`
logstash_1  |         ECS disabled
logstash_1  |           does not log info about setting the target
logstash_1  |         ECS enabled
logstash_1  |           when target not set
logstash_1  |             emits a helpful info log
logstash_1  |           when target is provided
logstash_1  |             does not emit an info log about setting the target
logstash_1  |       when configured with a codec that supports `target`
logstash_1  |         and neither the input's target nor the codec's target is set
logstash_1  |           and ECS compatibility is enabled
logstash_1  |             logs info advocating for setting the codec's target
logstash_1  |           and ECS compatibility is disabled
logstash_1  |             does not log info about targets
logstash_1  |         and both the input's target and the codec's target are specified
logstash_1  |           logs a warning about target being specified multiple places
logstash_1  |         and target is provided in the input but not the codec
logstash_1  |           logs info about preferring the codec's target
logstash_1  |         and target is provided in the codec but not the input
logstash_1  |           does not log info about target
logstash_1  |   with a plugin that does not have target config
logstash_1  |     raises an error at registration

closing, will re-open as a PR against upstream.


Allow password to take in a generator/callback to support temporary passwords that must be refreshed.

Motivation
Use case
Recently AWS introduced an option to connect to ElastiCache instances that are running Redis 7+, using IAM authentication: https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/auth-iam.html
This poses a problem for the typical static password property, e.g. you might write an Elasticache/Redis client code with node-redis like:
import { createClient } from "redis";

const authToken = await generateIAMAuthToken(...);

const client = createClient({
  // ...
  password: authToken,
  // ^ This token will expire in 15 minutes, and the connection will automatically be disconnected after 12 hours!
  //   This forces consumers of the package to implement their own method to manually re-create a client & re-establish a valid connection with a new, valid password before expiry.
});

Proposed Solution
It would be useful if createClient could take in a callback for the password option, that may be invoked on reconnect attempts to properly refresh/regenerate a password in such scenarios where the password may be referring to a temporary auth string that must be refreshed on a TTL.
import { createClient } from "redis";

const client = createClient({
  // ...
  password: async () => generateIAMAuthToken(...),
  // node-redis client should leverage this callback to regenerate a valid password on client disconnect.
  // perhaps include a TTL option to also detect when reusing existing auth may be valid before regenerating?
});

Basic Code Example
No response

+1 this is supported in other language clients like Go and Java. In addition to the AWS specific authentication, this provides more flexibility into how credentials are provided in an application.

Duplicate of #821.
It's on our roadmap, but no one started implementing it yet.
You can use the workaround suggested in https://github.com/redis/node-redis/issues/821#issuecomment-1894291132 in the meantime.

I would lean towards the credentials (i.e. user / password) like other client implementations.


Visual Studio Project Files

Hello everyone!
I was wondering whether the already generated Visual Studio project files need to be in the repository, now that Premake is supported and anyone can generate them by themselves.

Nope, they are useless in this case
niedz., 3 lut 2019, 12:04 użytkownik Philip Katis<EMAIL_ADDRESS>napisał:

Hello everyone!
I was wondering whether the already generated Visual Studio project files
need to be in the repository, now that Premake is supported and anyone can
generate them by themselves.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/TheCherno/Hazel/issues/25, or mute the thread
https://github.com/notifications/unsubscribe-auth/Akz10ePB2aOOrdWJ19cYW4cr7UQ3CrZZks5vJsJPgaJpZM4agDQv
.

It probably makes sense for them to be ignored, as it could be the case that someone is trying to build with an out of date configuration if they haven't been checked in after an update and someone clones the repository.

Nope, the Visual Studio Project files are obsolete when Premake comes in because everybody have different machine setups and Premake should generate them accordingly with your system's specs.
And like what @DrBarnabus said, things can get outdated pretty quickly, so its best if you compile and generate the necessary files the moment you finish cloning the repo 😃

Closing since this has been merged.


Correct or support Triggers for target Cloud Run service?

Hello ahmetb, thanks for providing support for this project.
I would like to know what is the supported Cloud Run Triggers I should be configuring on my target-services?
For example originally, we used Ingress configured to "Allow all traffic"
and Authentication configured to "Allow unauthenticated invocations"
which I know, for obvious reasons is very bad.
With this project/module/runsd, we are now able to configure "Require authentication" on the target-service (which is a big improvement)
However, when we tried to configure the Ingress to "Internal traffic only", we get a 403 Access forbidden - that's all we know, error
The target-service is being requested via an nginx reverse-proxy service (our frontend-app), so we should be correct to assume both source and target service is "internal traffic"
Or are we missing something / some core-concept?
edit**
additionally, from what I can tell, the target-service didn't even receive the request; and the source-service (our frontend nginx service) just logged a 403, and nothing else

This tool predates "Ingress" configuration so I have not tested.
I don't know if Internal only ingress allows Cloud Run to Cloud Run. Please consult the feature documentation.
runsd is a simple tool, it just rewrites your request with an Authorization header and adds HTTPS. (See README for architecture diagram). So the request still originates from your container –there's no magic that would make runsd relevant to the Ingress feature.

thanks for the info


[BUG]

I tried this code:
./rr -c .rr.yaml serve

I expected to see this happen: The program is running normally
Instead, this happened:

The version of RR used: 2.0.3
The operation system used: cenots7
RR configuration file content:
http:
  address: <IP_ADDRESS>:8080
  pool:
    num_workers: 8
    max_jobs: 0
    supervisor:
      # watch_tick defines how often to check the state of the workers (seconds)
      watch_tick: 1s
      # ttl defines maximum time worker is allowed to live (seconds)
      ttl: 0
      # idle_ttl defines maximum duration worker can spend in idle mode after first use. Disabled when 0 (seconds)
      idle_ttl: 10s
      # exec_ttl defines maximum lifetime per job (seconds)
      exec_ttl: 10s
      # max_worker_memory limits memory usage per worker (MB)
      max_worker_memory: 100
  headers:
    cors:
      allowed_origin: "*"
      allowed_headers: "*"
      allowed_methods: "GET,POST,PUT,DELETE"
      allow_credentials: true
      exposed_headers: "Cache-Control,Content-Language,Content-Type,Expires,Last-Modified,Pragma"
      max_age: 600

server:
  command: "php ./vendor/bin/rr-worker start --relay-dsn unix:///var/run/rr-rpc.sock"
  relay: "unix:///var/run/rr-rpc.sock"
  env:
    RR_MODE: http

logs:
  mode: development
  level: debug
  encoding: console
  output: stderr
  err_output: stderr
  channels:
    http:
      mode: development
      level: panic
      encoding: console
      output: stdout

# healthcheck
status:
  address: "<IP_ADDRESS>:8090"

reload:
  # sync interval
  interval: 1s
  # global patterns to sync
  patterns: [ ".php" ]
  # list of included for sync services
  plugins:
    http:
      # recursive search for file patterns to add
      recursive: true
      # ignored folders
      ignore: [ "vendor" ]
      # service specific file pattens to sync
      patterns: [ ".php", ".go", ".md" ]
      # directories to sync. If recursive is set to true,
      # recursive sync will be applied only to the directories in `dirs` section
      dirs: [ "." ]

remarks: I can run normally on the cloud server, including centos8 and Ubuntu. The local server is not working properly. spiral/roadrunner-laravel version: 4.0.1. And  The CentOS7 of my local machine can run normally, spiral/framework.

Hey @Alexei007. You have the wrong relay value, it should be in the form of  unix://file.sock, in your case - unix://var/run/rr-rpc.sock

I might be wrong because I guess your socket has the path from the root /var/run/rr-rpc.sock. Could you also try to run your worker separately, because as I see from the logs, there is an error while RR tries to run your worker.

Hey @Alexei007. You have the wrong relay value, it should be in the form of  unix://file.sock, in your case - unix://var/run/rr-rpc.sock

Hello, Valery Piashchynski, Thank you for your reply.
It doesn't seem to be a configuration file problem. I test the same code on the local server and the cloud server. The cloud server is running normally, and the local server is running incorrectly.
I use exactly the same project, include . rr.yaml file.
server:
  command: "php ./vendor/bin/rr-worker start --relay-dsn unix:///var/run/rr-rpc.sock"
  relay: "unix:///var/run/rr-rpc.sock"

http:
  address: <IP_ADDRESS>:8080
  middleware: ["headers", "static", "gzip"]
  pool:
    max_jobs: 64 # feel free to change this
    supervisor:
      exec_ttl: 60s
  headers:
    response:
      X-Powered-By: "RoadRunner"
  static:
    dir: "public"
    forbid: [".php"]

@Alexei007 Check the 8080 port in your local env. And try to run worker without RR, not to work with, but to check the problem.

Also, add these lines to your config:
# RoadRunner internal container configuration (docs: https://github.com/spiral/endure).
endure:
  grace_period: 30s
  print_graph: false
  log_level: error

Большое спасибо за терпение )
No error reported, relevant process can be found, When running
php ./vendor/bin/rr-worker start

When running the code, port 6061 is normal and port 8080 is unused.

Firewall, hm... Do you use a firewall in your local env? If so, could you please try to turn it off and re-run the application (temporary)?

Let me explain, exactly the same project. The cloud server is running normally (centos8 and Ubuntu). The local server, centos7 system, couldn't work normally. At first, I thought it was a system problem, so I tried to install centos8 to run the code. But it still doesn't work, I can't solve the problem. I would like to use RR + laravel in my new project, but the current situation may not work.

Hope @Taylor Otwell will bring a surprise next Monday.

Firewall, hm... Do you use a firewall in your local env? If so, could you please try to turn it off and re-run the application (temporary)?

It's not a firewall problem, the port is open, and I'm running locally.

As I see from the error log, that by some reason, RR can't allocate a worker at your local system. This is definitely some local system issue. Might be some outdated package or something else. If you paste here the steps on how to reproduce your issue with the *.php worker I'll try to help you.

Hi @Alexei007! Could you please try to change relay from unix:///var/run/rr-rpc.sock to unix:///tmp/rr-rpc.sock or tcp://<IP_ADDRESS>:6001 (any unused port)?

Many thanks ) You are so handsome )
There is a great possibility that there are some outdated packages, Because there are some restrictions on the Internet in China. And I saw in China's technology forum that many developers couldn't run RR normally and didn't find a solution.
But the question now is how to find out that outdated packages.

Hi @Alexei007! Could you please try to change relay from unix:///var/run/rr-rpc.sock to unix:///tmp/rr-rpc.sock or tcp://<IP_ADDRESS>:6001 (any unused port)?

@tarampampam
Thanks for your comment, I tried, That should not be the problem.
This project can run normally on the cloud server.
server:
  command: "php ./vendor/bin/rr-worker start --relay-dsn unix:///tmp/rr-rpc.sock"
  relay: "unix:///tmp/rr-rpc.sock"

http:
  address: <IP_ADDRESS>:8080
  middleware: ["headers", "static", "gzip"]
  pool:
    max_jobs: 64 # feel free to change this
    supervisor:
      exec_ttl: 60s
  headers:
    response:
      X-Powered-By: "RoadRunner"
  static:
    dir: "public"
    forbid: [".php"]

...many developers couldn't run RR normally and didn't find a solution.

Sounds very-very strange.. Anyway, could you please to make an attempt to run your application using isolated environment like docker? This tutorial (ru lang; a little bit outdated) can helps you with this.

Have you tried to use pipes relay or TCP relay? Can you post your worker code?

Have you tried to use pipes relay or TCP relay? Can you post your worker code?

Thanks, @wolfy-j . The project can run normally in the cloud server, with exactly the same code. Therefore, It shouldn't be a code problem. It might be some package used by RR that I installed locally is outdated.
I installed it with composer. By the way, My local CentOS can run spiral/framework normally.
composer require spiral/roadrunner-laravel "^4.0"

File: ./vendor/bin/rr-worker
#!/usr/bin/env php
<?php

declare(strict_types=1);

\define('RR_WORKER_START', \microtime(true));

\ini_set('display_errors', 'stderr');

/*
|--------------------------------------------------------------------------
| Register The Auto Loader
|--------------------------------------------------------------------------
|
| Composer provides a convenient, automatically generated class loader
| for our application. We just need to utilize it! We'll require it
| into the script here so that we do not have to worry about the
| loading of any our classes "manually". Feels great to relax.
|
*/

$loaded = false;

foreach (['../../..', '../..', '..', 'vendor', '../vendor', '../../vendor'] as $path) {
    if (\is_file($autoload_file = __DIR__ . '/' . $path . '/autoload.php')) {
        require $autoload_file;
        $loaded = true;
        break;
    }
}

if ($loaded !== true) {
    \fwrite(\STDERR, 'Composer autoload file was not found. Try to install project dependencies' . PHP_EOL);
    exit(1);
}

/*
|--------------------------------------------------------------------------
| Find Application Base Path
|--------------------------------------------------------------------------
|
| This file can be located in package `./bin` directory, used as a symbolic
| link or something else. In this case we will try to find application
| base directory using the most obvious application locations.
|
*/

/** @var string|null $base_path */
$base_path = null;

foreach (['../../../..', '../../..', '../..', '..', '../vendor/laravel/laravel'] as $path) {
    if (\is_file(__DIR__ . '/' . $path . '/bootstrap/app.php')) {
        $base_path = (string) \realpath(__DIR__ . '/' . $path);
        break;
    }
}

/*
|--------------------------------------------------------------------------
| Create And Run Console Application
|--------------------------------------------------------------------------
|
| Symfony console component is a nice wrapper around worker CLI options.
|
*/

$app = new \Symfony\Component\Console\Application(
    'RoadRunner worker',
    \Composer\InstalledVersions::getPrettyVersion('spiral/roadrunner-laravel')
);

$app->add(new \Spiral\RoadRunnerLaravel\Console\Commands\StartCommand(
    new \Spiral\RoadRunnerLaravel\Worker(),
    $base_path
));

$app->run();

@48d90782 @wolfy-j  @tarampampam
Спасибо за помощь )
I tried to reinstall laravel, RR  And PHP, And it works. I'm very confused that I didn't succeed in the same steps I did yesterday, It's really crazy to try so many times these days without solving it.
You are all great, Thank you so much~~~

@wolfy-j  @48d90782
Just now, I found out the reasons for success and failure.
I install the CentOS system locally on the visualbox, My projects are usually placed in a shared folder with windows.

Case 1: when I create spiral/roadrunner-laravel in the local folder of CentOS, the project can run normally
Case 2: when I create spiral/roadrunner-laravel in the shared folder, It doesn't work.
Case 3: spiral/framework , This project works well in both shared and local folders

What I still don't understand is that my other projects can work normally. Why does this happen to spiral/roadrunner-laravel.

@Alexei007 Thanks for your investigation :) We will try to reproduce it.


Breaking Change: Fix argument name in CompareInfo.IsPrefix (suffix -> prefix)

Fix argument name in CompareInfo.IsPrefix (suffix -> prefix)
This CompareInfo.IsPrefix() API was added in .NET 5.0 RC1, but there is a mistake in the argument name where suffix was used instead of prefix.  The implementation is correct, but the reference assembly was wrong. dotnet/runtime#41803 fixed the argument name. This fix will ship with .NET 5.0 RC2.
Version introduced
.NET 5.0 RC2
Old behavior
The previous method signature was the following, with an argument named suffix.
public bool IsPrefix(System.ReadOnlySpan<char> source, System.ReadOnlySpan<char> suffix, System.Globalization.CompareOptions options, out int matchLength)

New behavior
The updated method signature is the following, with the argument renamed to prefix.
public bool IsPrefix(System.ReadOnlySpan<char> source, System.ReadOnlySpan<char> prefix, System.Globalization.CompareOptions options, out int matchLength)

Reason for change
This corrects a mistake in the argument name and will improve the API, avoiding confusion by users.
Recommended action
If the argument was being used as a named argument, update calling code to correct the argument name to match the renamed prefix name.
Category

[ ] ASP.NET Core
[ ] C#
[ ] Code analysis
[x] Core .NET libraries
[ ] Cryptography
[ ] Data
[ ] Debugger
[ ] Deployment
[ ] Globalization
[ ] Interop
[ ] JIT
[ ] LINQ
[ ] Managed Extensibility Framework (MEF)
[ ] MSBuild
[ ] Networking
[ ] Printing
[ ] Security
[ ] Serialization
[ ] Visual Basic
[ ] Windows Forms
[ ] Windows Presentation Foundation (WPF)
[ ] XML, XSLT

Affected APIs
CompareInfo.IsPrefix(ReadOnlySpan<char>, ReadOnlySpan<char>, CompareOptions, out int)
The affected overload was added in .NET 5.0 RC1 and was not yet present in documentation at the time of this breaking change in RC2.

Issue metadata

Issue type: breaking-change

Updated the description to reflect that the breaking change was introduced in 5.0 RC2.


[e2e tests] VM details: Nertwork tab

Create e2e tests for VM details (Network tab) functionality

Here you can use #1257 (editing of firewall rules)


Add experimental WebGPU HAL backend.

This merges the webgpu development branch after over a year of on and off development.
For now, this code will live in the experimental/ folder, while the code matures and reaches feature parity with the supported HAL drivers. While some work has been started to add unit and integration tests for the web platform, that work is not complete yet (and it will likely be substantially different from our existing "native" tests). See also the discussion on RFC: Promoting IREE web platform / Emscripten builds to "stable".
Major components:

A runtime HAL driver in experimental/webgpu/ that targets the recently released WebGPU API

This uses webgpu-headers to connect with API implementations, either via Emscripten's library_webgpu.js or via other implementations like Dawn / wgpu-native (we originally had a platform switch for these, but dropped that for now)

A sample application in experimental/web/sample_webgpu/

Build script compiles programs with --iree-hal-target-backends=webgpu
Build script configures CMake with -DIREE_EXTERNAL_HAL_DRIVERS=webgpu
Code shows how to interface between runtime C code, browser JavaScript APIs, and Emscripten

Tested that ./experimental/web/testing/build_tests.sh still works with this (and pushed one fix :P). Going to wait until tomorrow to merge.


Show reflecting percentage before block confirmation, show on file page

There's still confusion on Desktop about when a file is full playable/ready to be shared / when the client can be closed. Today we show the confirmation process first, and then reflection percentage, and also a notification when the confirmation is done. This causes confusion since users think that the file is fully available and can either share it, or close the app.
Users may also navigate away from the publishes page, which is the only place we show reflection percentage.

[ ] show reflection percentage first, then confirmation if still valid
[ ] don't show publish complete notification until reflection done? Or put a better note?
[ ] show reflection percentage on file page / claim preview on channel

Just tried this again and it showed confirming and not upload % as I originally thought we fixed.  Showing the percentage upfront will make it clearer that something is happening so that they don't close the app.

It didn't show the percentage either after it confirmed - so maybe a timing issue.


Failing tests after merge of EmberCli-1.13.8 branch

mine

got merged but not closed
https://github.com/softlayer/sl-ember-components/pull/1203#event-469199130


Support image signatures & attestations

This should be done using sigstore/cosign and supporting technologies.
We discussed this feature in our own internal "dogfooding" scenario. We envision this giving us the ability to promote a hub release from staging to production. Here's the less than ideal options we have now:

To promote now, we might need to create a new tag (like going from a -rc to a non-rc image so that auto-deploy picks it up), but that means we are fundamentally doing another build and creating a new binary. That is not the ideal. The ideal is to promote an existing binary.
We could also completely control it via gitops and not use acorn's auto-deploy feature, changing a tag value from the "old" to "new" in our flux git repo, but we really want to get to an acorn native approach that doesn't rely on a gitops tol for this.

So, our ideal scenario for our own process is to have auto-deploy working off of an attestation on existing release. And then the trigger to deploy would be someone signing the image somewhere. It could even be QA signing off on the image.
We want this to be general purpose enough to fit different org's use cases. So, an app owner should be able to define what signatures/attestations/attributes need to be on an image to qualify it for promotion.
Once we get the core functionality down, we need to also consider other things like:

auditing
rollback
What happens if you revoke a sign-off?

Beyond just generically signable, we want attestations and/or annotations to indicate arbitrary checks or approvals the image has gone through

In dogfooding scenario:

creating a new tag is not good because its a new binary
updating gitops is still making an external change
ideal scenario for our own process is auto-deploy working off of an attestation on existing binary

@thedadams just a heads up - i've asked thorsten to start looking at this.


[feat]: radio set FormControl

radio buttons are form controls that are grouped together, and allow only one to be selected.
Implement the property that indicates the group too which a radio button belongs with, and allow only one button to be selected in this group

Hi @ayoayco, Can I work on this issue?
My first idea is to make the radio buttons can be accepted and rendered the value like this
{
    name: "agreement",
    label: "Agreement",
    type: "radio",
    value: ["yes", "no"] // string[]
}

and you can custom the label next to the radio like this
{
    name: "agreement",
    label: "Agreement",
    type: "radio",
    value: [
      { label: "Agree", value: "yes" },
      { label: "Disagree", value: "no" }
    ]
}

What do you think?

Hi @Icyscools it looks good! Let's try this approach. :)

great job @Icyscools 🚀


Page0 long polling for hosts and environments

Should be merged after #191
Add long polling for host creation, host deletion, and env creation
Host deletion updates corresponding environment to be status "stopping"

@ikicha @k311093 PTAL

Can you please rebase this PR to the main?

Can you please rebase this PR to the main?

Done!


Chat encryption happening too early for client side mods

Modloader
Fabric
Minecraft Version
1.19.4
Modloader Version

No Chat Reports Version
1.19.4-v2.1.1
Modpack Info
No response
The latest.log File
N/A
Bug Description
NCR encrypts messages too early in the process for most client-side mods to handle properly.
This is fixable by injecting into the chat message s2c/c2s packets initializers and doing the encryption there instead
Steps to Reproduce

enable encryption
have baritone
try to use baritone

Other Information
https://github.com/cabaletta/baritone/issues/3894
looks like meteor also injects at the same spot https://github.com/MeteorDevelopment/meteor-client/blob/03d17cd4a6d5f8102cdbe2c5f2ed9cebc8b80b10/src/main/java/meteordevelopment/meteorclient/mixin/ClientPlayNetworkHandlerMixin.java#L130
also some mods such as jsmacros will end up bypassing the encryption by sending at that lower level;
https://github.com/JsMacros/JsMacros/blob/274c80c0d817276733a3d05ef20a477ec228f2af/common/src/main/java/xyz/wagyourtail/jsmacros/client/api/library/impl/FChat.java#L154
I'm sure there are many other mods like this
I suggest moving the encryption/decryption to happen when the packet classes are constructed in order to be compatible with most if not all client mods

I have decided against fixing this in 1.19. Changing injection point for encryption can potentially lead to other issues, and since I do not plan to release 1.19 updates after porting, I will do this after porting to 1.20, where I will be able to address them as part of ongoing maintenance.

IT ALSO APPEARS ON FORGE 1.20.1 WITH BARITONE MOD!

It would be nice if this issue could be resolved, as having to toggle encryption manually to run Baritone commands is rather tedious.


Replace the current gmail id with the official bridgeconn id in the app

Issue description : Include Vachan project official email id in the website app by replacing the gmail id

@JesniJ please verify on the latest apk1.3.6-alpha.3

Testing is done and verified that current gmail id is replaced with the official bridgeconn id. Thus moving this issue to done.


Is it a correct way to create kitura web using xcode11's swift package?

Context and Description
I create a kitura web using xcode11's swift package.

adding main.swift in Sources/ProjectName.
adding dependencies Kitura-StencilTemplateEngine and Configuration packages.

let projectPath = ConfigurationManager.BasePath.project.path

run in xcode11
the projectPath doesn't point to project folder, StencilTemplateEngine also can't points to default folder Views.
run in command line
Kitura-StencilTemplateEngine and Configuration are working very well.

Question: is it possible to create kitura web+kitura-nio using xcode11's swift package.
thanks
Environment Details
MacOS 10.15 beta
Xcode 11.0 beta 4

I think the best way to create web app is this
step 1  -- run this command inside the folder where you want your app to be
swift package init --type executable
step 2 open package.Swift
and add this

// swift-tools-version:5.1
import PackageDescription

let package = Package(
    name: "YOURappName",
    dependencies: [
        .package(url: "https://github.com/IBM-Swift/Kitura", from: "2.8.0")

        .package(url: "https://github.com/IBM-Swift/HeliumLogger.git", from: "1.9.0"),

        .package(url: "https://github.com/IBM-Swift/Kitura-StencilTemplateEngine.git", from: "1.11.1"),
    ],
    targets: [
        .target(
            name: "YOURappName"",
            dependencies: ["Kitura"]),
        .testTarget(
            name: "YOURappName"Tests",
            dependencies: ["YOURappName""]),
    ]
)

step 2
swift package generate-xcodeproj to open the project
your app code goes inside -->YOURAppName-->Sources-->main.swift
note that templates go into the Views folder and you can also set a /public folder to serve images, css etc. like this
router.all("/public", middleware: StaticFileServer()) // public folder

Just enable Working Directory


Windows stringzillite might be broken

Describe the bug
I think after #181, the stringzillite dll may have been broken.
The addition of the static lib changes, might have made the dll dependent on other dlls.
I have not tested this, but I'm quite sure the problem exists and can look into it when I get chance.
Steps to reproduce
Build the stringzillite dll on windows.
Expected behavior
The dll Is completely standalone.
StringZilla version
3.10.5
Operating System
Windows 10
Hardware architecture
x86
Which interface are you using?
C implementation
Contact Details
No response
Are you open to being tagged as a contributor?

[X] I am open to being mentioned in the project .git history as a contributor

Is there an existing issue for this?

[X] I have searched the existing issues

Code of Conduct

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

I wouldn't say I'm that experienced, but I know some things.
For these changes:
https://github.com/ashvardanian/StringZilla/blob/main/CMakeLists.txt#L331-L338
Were these just trial and error to get it to build, or from external build issues?

It was research-driven, but took multiple attempts 😄

I could be wrong, but here's my understanding of what has caused this.

Issue #178 and pr #180, removed the _DllMainCRTStartup function. Which led to the linker error:
LINK : error LNK2001: unresolved external symbol _DllMainCRTStartup
Because that function must exist for dlls to be built.
It then got fixed by #181, by linking against the crt libs. Which provide the required functions for the dll.
Which now means the dll depends of the crt dlls now.

Now I do think the solution to #178 was correct, by adding the sz_dispatch_table_init to the .CRT$XCU section. As thus gets called as part of the global static initialisers, from the crt implementation of _DllMainCRTStartup only.
And as for why these functions weren't being called from the rust library, I have a hunch that they were there but either maybe rust inserts a custom _DllMainCRTStartup function,  or simply the linker preferred the version in the crt libs instead.
I probably need to read up of how rust creates its library packages, to know for sure why it worked.
crt init docs


Upgrade Stellar tests to use STD network

Description

Tests needs to be upgraded from using TEST network wallet to use STD network wallet

see also pools test, chatflows test, stellar tests, automated tests

need proper clean up to send the XLMs to specific wallet address


Syntax highlighting on script cfc's

I'm trying to move to ST3 from ST2 and I can't get the syntax highlighting to work for cfc's written entirely in cfscript. I'm running the "development" branch of the plugin and .cfm files are fine.
I figured it might be connected to the identified scopes. But having checked this, I always get the result "source.cfc.cfscript". How can I narrow down the cause of the issue?

Set your syntax to "ColdFusion Component", on the far right of your status bar.

Yes, that was already set. I've spoken to a couple of colleagues and they say that with some files they see the colour highlighting, and with other cfc's they don't. Unfortunately they haven't been able to figure out what the similarity is with the files that end up looking like plain text.

The last commit dc81fc3 broke syntax highlighting for me as well. I'm on Mac OS X 10.9.5. Reverting fixed the issue. After following the install / git checkout instructions, run the following in the same folder: git revert dc81fc3 --no-edit --no-commit

Yeah the <hidden> element was added in Build 3067 of Sublime Text which was only released a few days ago. I'll revert the change for now.

IMO since using ST3 requires the development branch of this plugin, but ST3 offers both stable and unstable release branches, we need tagged development builds (to make them available for stable ST3 channel users) or just to ban ST3-unstable features from the development branch (new development-st3-unstable branch?)

sounds good to me

Reverting out the  element has fixed things for me. Thanks for the help.


functions to modify (filter) array values

Is there a way to filter array value of a column? Something like filter function
Inside a "A Team" note have a list of people related to that team:
```dataview
table name, emails, teams
from ""
where type = "person" and contains(teams, "A Team")
sort name
```

But it doesn't make sense for me to "A Team" appear in the teams column, since I'm already inside "A Team" note context.
It would be nice to have something like:
```dataview
table name, emails, filter(teams, t => t != "A Team") as "other teams"
from ""
where type = "person" and contains(teams, "A Team")
sort name
```

Yes, there is now a filter and map function.


Automated cherry pick of #3681: fix: baremetal server rebuild root fail to cache image

Cherry pick of #3681 on release/2.13.
#3681: fix: baremetal server rebuild root fail to cache image

/lgtm
/approve


Revert "Accept Join type as parameter default value as it returns a s…

…tring (#752)"
This reverts commit 3b78644106368c195399477f2e47552f4497bd0d.
This was a incorrect change - cloudformation also rejects it with a validation error - "Template validation error: Template format error: Every Default member must be a string."

Thanks!


added "máquina" word

The word máquina wasn't at the array. It was at the example though.

Coverage remained the same at 95.833% when pulling 9e3412aecd7ff2689a008f23cc0e42651b02abb4 on Trocaflosquen:master into bb9d1c7e4af767a879b2efd95d8a5db982d71352 on Kikobeats:master.


Connect Github to Trello

Hi, we need to connect between the repo and the Trello board for easier following.

 open Git organization

Github connected to Trello board


Draw a distinction between slow tests and very slow tests

There are tests that are slow that involve pulling lots of data, performing preprocessing, training small models, etc. Then there are mega end-to-end tests which could take days to run on a CPU-only machine. These should be categorized differently slow that tox -- --slow is different from tox -- --veryslow.
Related note: I've started using the notravis mark for tests that can't be run on Travis. This is orthogonal to speed (.travis.yml doesn't run the slow tests anyway), and is mostly because they rely on data that is not public, or would require fixtures that last between builds.

You could always make a veryslow test marker as well, then you can specify to run those tests only if that option is set.

I've thought a bit more about how to manage the experiments and this is what I've come up with:

If no flags are set, then tests are run that are both fast to run and don't require authentication to access non-public data. These can be run on travis.
--notravis activates tests designated with a pytest.mark.notravis mark that can't be run via Travis because they are a bit slower or require non-public data. However, these tests should in the slowest case complete in a few hours.
--experiment is for reproducing experiments and most tests that involve assertions about the error rate reaching a given value. These are typically long-running experiments, taking days. I've made a tests/experiments/ subdirectory mostly for tests marked with the relevant mark pytest.mark.experiment.

As many tests as possible should be run when no flags are specified.
An additional flag, --preprocess is orthogonal to the others and is used to force re-preprocessing of input data. If the purpose of the testing is to make sure the tests run end-to-end with the most recent preprocessing, then this flag should be set. In such cases, the test fixture responsible for preprocessing will request the data from online (where applicable) and perform preprocessing. (Ideally ensuring up-to-date preprocessing of data would be handled by checking hashes of input data and git commits, but this forced preprocessing should be an option in any case). Without this flag, tests will used cached data where available, which for the --notravis tests will speed things up considerably since preprocessing will typically be larger relative to training time than in the --experiment case.


Create an explanation of algorithm using jupyter notebook

Provide examples and explanation of how the algorithm works using jupyter notebook

the documentation is written in doc directory


On merge member add ability to search for members also by organization

Change placeholder in merge member modal to "Search for members or organizations"
Create separate endpoint which will support searching members by member displayName and organization name.
Remove populating organizations in member/autocomplete endpoint so we don't slow down other member searches

Hi I wanted to work on this issue can you assign me this issue

@joanagmaia Can you help me setup crowd.dev on my local machine

Hey @TheOjasSingh, have you checked https://github.com/CrowdDotDev/crowd.dev/blob/main/CONTRIBUTING.md?
If so, did you face any issue while setting it up?

yes, when I am trying to clone the repo it is asking for permission.

yes, when I am trying to clone the repo it is asking for permission.

You will need to fork the repo and make a PR from there. Did you try that way?

Yes I also tried that way but still when I am trying to commit it ask for permission.

@TheOjasSingh this might be helpful for you
https://docs.github.com/en/get-started/quickstart/fork-a-repo

@TheOjasSingh any success?


Add backoff with Jitter to load-balancing scripts

The current Load Balancing scripts do not work well at scale (deploying concurrently to over 50 instances). As all instances will simultaneously attempt to deregister / standby and then poll for status changes. This will cause API throttling which is currently not handled in the scripts processing.
This change adds a generic function called exec_with_fulljitter_retry which performs all CLI execution (AWS_CLI variable ha been modified to call this function rather than call the CLI directly) this function has functionality to

Optionally perform pre-jitter. This will slow initial execution (hence why its optional) but will likely speed up the processing of 00's of simultaneous instances

Perform CLI retry on the event of a failure using the "FullJitter" algorithm (exponential backoff with jitter) taken from AWS blog: https://www.awsarchitectureblog.com/2015/03/backoff.html

All variables related to the number of retries, base level of the exponential backoff etc can be modified at the top of this function.
Additional note variable WAITER_INTERVAL_ASG had also been increased to 3 seconds rather than 1 as typically setting an instance to standby takes ~15 seconds, retry'ing every second seems wasteful / non-valuable given the expected time for the change to complete.
Testing that has been performed:

Putting instance in standby / active within a ASG on an ELB
Deregistering / Registration of an instance on an ELB (without ASG method of script)
Points 1 & 2 for an ALB using elb-v2 versions of scripts
Testing to some extent (on elb version of script) the “HANDLE_PROCS” additional functions

This change has also now been used in production for a week with code-deploy deploying simultaneously to 200+ instances.

Thanks for the PR.
The change looks good to me. Can you confirm that you are OK this change to be under Apache 2.0 license?

Confirmed this change can be under the Apache 2.0 license.

The additional escaping in check_cli_version actually breaks for me.  Running on Ubuntu 12.04.  Version ends up never getting set.
Some debugging I did (added right before x, y, and z set set):
    msg "Min CLI version is $MIN_CLI_VERSION"
    msg "Second parameter is $2"
    aws_cli_version=$($AWS_CLI --version)
    msg "AWS CLI version check: $aws_cli_version"
    msg "First parameter is $1"
    msg "Version got set to $version"

Min CLI version is 1.3.25
Second parameter is
AWS CLI version check: aws-cli/1.11.80 Python/2.7.3 Linux/3.2.0-126-virtual botocore/1.5.43
First parameter is
Version got set to

get_instance_state_asg also seems to be broken with the additional escaping added here.
[stderr]Checking if this instance has already been moved out of Standby state
[stderr]
[stderr]Bad value for --query "AutoScalingInstances[?InstanceId: Bad jmespath expression: Unclosed " delimiter:
[stderr]"AutoScalingInstances[?InstanceId


Disable DocLint in JDK7 and JDK8

(according to Thiago Porciunclula https://stackoverflow.com/users/2352699/thiago-porciúncula)

Ugh.    This pull-request fixes #208


Adding places with examples

Could we have the ability to use places library with this wrapper? Specifically, an option to load the places API within the Maps script on load. Autocomplete would be a great feature to have.

This library uses @googlemaps/js-api-loader, so you can simply pass in libraries to your Wrapper component and load the places API. Ex:
  <Wrapper apiKey={...} libraries={['places']}>
    {....}
  </Wrapper>

This library uses @googlemaps/js-api-loader, so you can simply pass in libraries to your Wrapper component and load the places API. Ex:
  <Wrapper apiKey={...} libraries={['places']}>
    {....}
  </Wrapper>

Thank you so much, you made my day!


Submit testimony e2e

Summary
#1514
Known issues
I am hitting timeout errors related to the Create Testimony button. I have included console logs to check if the page URL updates after clicking on a specific bill within the browse bills page, and it does, however the content does not seem to update. The screenshot taken by playright also shows browse-bills content instead of a specific bill page. This helps explain why playwright cannot find the Create Testimony button, but I am not sure how to remedy it. I have tried adding a longer timeout.
I was also able to log some failed requests, but I am unsure if they are related to this problem.
#playright error screenshot

Steps to test/reproduce
run npx playwright test submit-testimony.spec.ts

getting networkidle issues too, but can successfully waitfor domcontentload. unsure if that provides any clues.


Compile: hints validation switch

This PR introduces a structure allowing to add flags available in starknet-compile to nile compile.
For now only only --disable_hints_validation is supported.

I think it's ok to ignore those lines, can you disable the linter for those?

@marcellobardus are you interested in updating this PR?

Temporary closing


Powerline symbols in the terminal get wrong colors

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

VS Code Version: Version: 1.66.0
OS Version: macOS Monterey 12.3 (21E230)

Steps to Reproduce:

Use a powerline-friently prompt with fancy triangles (\ue0b0) in the terminal.
Open the terminal.

Expected
How this should look (before 1.66.0)

Actual

The triangles got some mixed colors.
Info

The prompt works correctly in iTerm, Terminal, etc. (so this is VSCode),
This fails in all shells in VSCode: bash, zsh, or fish.
This fails with or without customizations to workbench.colorCustomizations like terminal.ansi*.

"terminal.integrated.minimumContrastRatio": 1

"terminal.integrated.minimumContrastRatio": 1

Works like a charm, thanks. This could be mentioned in https://code.visualstudio.com/api/references/theme-color, though.

"terminal.integrated.minimumContrastRatio": 1

Thanks. Would love to know why this isn't the default.

"terminal.integrated.minimumContrastRatio": 1

Thanks. Would love to know why this isn't the default.

WCAG accessibility guidelines. To make colorful terminal applications look at least okayish no matter the user theme. Makes sense. Mentioned in https://code.visualstudio.com/updates/v1_41#_minimum-contrast-ratio.
I wonder why this affected my setup now since this has been implemented since 1.41 in 2019? What changed in the recent 1.66 update? 🤔

WCAG accessibility guidelines. To make colorful terminal applications look at least okayish no matter the user theme. Makes sense. Mentioned in https://code.visualstudio.com/updates/v1_41#_minimum-contrast-ratio.

Yeah, but IMO 4.5 shouldn't be the default because suddenly the ansi terminal colors requested aren't the ones requested. It's another layer of confusion on top of something already confusing. This change isn't really a net benefit.

I'm also confused why it changes the color of the powerline rectangles? This doesn't seem to be correct or am I missing something here?

My prompt uses Powerline symbols, so I had this issue after upgrading to 1.66 as well. I think making the terminal accessible by default is a good call, but it also presents a problem for prompts that switch between using the same color for background and foreground to create the illusion of shaped blocks (like Powerline). I'm sure this affects heavily-customized vim and Emacs setups that do similar things, too.
If a user still wanted to have the contrast ratio functionality, it might be nice to have a setting like terminal.integrated.excludeContrastRatioAdjustment that would be a string of characters to exclude from contrast ratio adjustment.

This feature has been around for a long time but we changed the default in 1.66 as we're trying to make VS Code the most accessible code editor out there. You can see some of the background on the change here: https://github.com/microsoft/vscode/issues/144411, I know this might cause an inconvenience but the net benefit is quite large:

Themes/shells with incompatible colors (#144411) will no longer be invisible or super low contrast
The terminal should be accessible regardless of your shell and operating system - accessibility is very important to our team
It's trivial to disable by setting "terminal.integrated.minimumContrastRatio": 1, you could argue that it's hard to discover this but it's equally hard for users where this makes the terminal unusable to discover it for the inverse problem.

FYI @isidorn about feedback

Works like a charm, thanks. This could be mentioned in https://code.visualstudio.com/api/references/theme-color, though.

@oleq good idea!

I'm also confused why it changes the color of the powerline rectangles? This doesn't seem to be correct or am I missing something here?

@levrik yes it's because how powerlines works is a bit of a hack; for the triangle character, it inverts the background/foreground color so the shape on the left is the foreground and the negative space on the right is the background.

If a user still wanted to have the contrast ratio functionality, it might be nice to have a setting like terminal.integrated.excludeContrastRatioAdjustment that would be a string of characters to exclude from contrast ratio adjustment.

@jaminthorns I like the idea of excluding at the least the triangle powerline char from minimum contrast ratio :+1:, this character will almost always be used to simulate the background color so it's a nice compromise. This also comes with the nice benefit of still retaining min contrast ratio in the prompt when a powerline is used.

This feature has been around for a long time but we changed the default in 1.66

Why was this not mentioned in the release notes? Control-F on "contrast" or "terminal" don't find this change.

@chtenb I stand corrected, it wasn't mentioned in the release notes. No reason other than we just missed including it. Added it in https://github.com/microsoft/vscode-docs/commit/c4320f6377dcda99fbe72e99f39378114ed5074a, it will be updated when we next publish the website.

Hi, @Tyriar, I'm a theme maker. I have customized various terminal colors in my theme. This feature makes these colors not match my theme anymore...

How do I set up in my theme file to make "terminal.integrated.minimumContrastRatio": 1 as the default setting for my theme? Then my theme users don't have to set it up themselves. I tried to write it in my theme's JSON file or Package.json, but it doesn't work.

I am looking forward to your solution. Very Thanks!

I have the same issue as @fisheva, I am using also zsh:
I tried to change it in the settings.json:
"workbench.colorCustomizations": {
"terminal.integrated.minimumContrastRatio": 1,
"terminal.foreground":"#bbbbbb",
"terminal.ansiBrightBlue":"#56B6C2",
....
but the minimunContrastRatio is not fixing anything with the terminal colors, seems that the gamut of available colors has been drastically reduced, for example, some dark colors like #303030 now look like bright gray in the console.

Hi, @Tyriar, I'm a theme maker. I have customized various terminal colors in my theme. This feature makes these colors not match my theme anymore...
How do I set up in my theme file to make "terminal.integrated.minimumContrastRatio": 1 as the default setting for my theme? Then my theme users don't have to set it up themselves. I tried to write it in my theme's JSON file or Package.json, but it doesn't work.
I am looking forward to your solution. Very Thanks!

@fisheva, I guess you can set it here:

@rmarinbe Sorry, that's not the point. I know how to set it on my own VSCode. I want to know how to set it for all my theme users.

@rmarinbe emmm, I know how to set it on my own VSCode. I want to know how to set it for all my theme users.

ok got it, sorry for the confusion, I also tried from the JSON but it is not working for me.

The amount of additional work (issues, Twitter replies) this change has brought to maintainers across the globe is not sustainable. I understand the need for accessibility, yet this introduces unwanted side effects for a majority of people. Can we think about how to solve this challenge differently?

I agree - IMO if you're changing something for any reason so it doesn't display how settings say it should (in this instance, changing the colours of things from what the colour is set to), that should be an option that a user enables by choice if they require it.
So default it back to 1 in the settings, then do a proper release annoucement about it, so if people who want/need it on know about it and can choose to enable the compliance settings.

Right now it's only fixed for terminal.integrated.gpuAcceleration: canvas

to verify:

install a powerline font
verify that changing the terminal.integrated.minimumContrastRatio does not alter the color of the powerline glyphs for all values of the terminal.integrated.gpuAcceleration setting

@meganrogge awesome work! I'll validate it in the morning (evening here).

@jstm88 we obviously value accessibility more that you 🤷
This issue is closed with a fix that should work for everyone. If the extra contrast still bothers you you can switch it off by tweaking terminal.integrated.minimumContrastRatio, I trust that you can set up your computer the way you want 😉

@jstm88 we obviously value accessibility more that you 🤷
This issue is closed with a fix that should work for everyone. If the extra contrast still bothers you you can switch it off by tweaking terminal.integrated.minimumContrastRatio, I trust that you can set up your computer the way you want 😉

There are two basic types of accessibility that are relevant here:

Designing the parts of the application you control to have good accessibility properties
Options that modify expected behavior

1 is obviously good, but 2 is a problem if enabled by default. We don't ship computers with high-contrast mode, large type, and text-to-speech enabled by default, do we? It would be silly.
The way I understand the fix that's been proposed is that it will make an exception for specific fonts, but it will still modify the colors displayed. This is still bad - you're making edge cases that have to be maintained, and you're opening the door for more of those edge cases as people inevitably discover all of the additional places where it breaks.
I'll further propose that, perhaps, this setting doesn't really make a lot of sense in the context of a terminal. There's a very simple solution that doesn't require these modifications - just add additional themes for the Terminal with an accessible color palette. Simple and it doesn't introduce edge cases.
I'm glad this is being thought of, but I just think this implementation (specifically making it the default) was ill-advised.

1 is obviously good, but 2 is a problem if enabled by default. We don't ship computers with high-contrast mode, large type, and text-to-speech enabled by default, do we? It would be silly.

@jstm88 Yes it would be silly, but this is a special case where we cannot guarantee contrast between the theme and the application/shell running in the terminal and many users would run into contrast issues because of this where characters were invisible. Plus the default isn't "high contrast", it's to shift the colors towards the minimum recommended contrast as recommended by WCAG AA (4.5) which is not particularly high.
Bottom line is we have requirements we need to meet around accessibility and this is one of those. You could argue this goes above and beyond what is required, but the tradeoff here after the fix is a good and worth it as contrast will be guaranteed regardless of theme, it only modifies the foreground color so shouldn't be particularly noticeable to most users and it can be easily disabled if it's bothersome.

I'll further propose that, perhaps, this setting doesn't really make a lot of sense in the context of a terminal.

The feature was inspired by iTerm2, so we're not the only ones that think it's a good idea. The "just change your theme" approach doesn't work for all background/foreground combinations as that's impossible and we also don't have distinct editor/terminal themes (like Atom), so you'd be forcing those users who want reasonable contrast to use the few (and ugly) high contrast themes.

@Tyriar Those are some good points, and I do see where the setting could still make sense even if there was theme support.
Still, though, if the option is going to be enabled by default, there absolutely needs to be a notification. There's an established UI paradigm for exactly this case - a panel in the corner, informing the user that the option was automatically changed, with a choice to disable it or accept the change. The notification could appear the first time the Terminal feature is used.

@jstm88 we've been fighting "notification fatigue" for a long time, adding a notification for such a minor thing would annoy people. Adding notifications to VS Code core are all heavy scrutinized to protect the user experience and keep VS Code feeling "lightweight".


irmEncryptFailedToFindProtector error response when download file

Category

[x] Question
[ ] Documentation issue
[x] Bug

Hi,
I try to download a file by api
GET /items/{item-id}/content

and I get the error code like this
{"error":{"code":"resourceModified","innerError":{"code":"irmEncryptFailedToFindProtector"},"message":"The resource has changed since the caller last read it; usually an eTag mismatch"}}

It seems like the error on server side. What is the root cause of this error?
Furthermore, I'm wondering if there is any query option to bypass this error and force download?
Or, do you have recommanded way to handle this kind of error ?
Thank you.
[ ]: http://aka.ms/onedrive-api-issues
[x]: http://aka.ms/onedrive-api-issues

This could be due to the file not being published, it could be checked out, or there could be running operations on the file. There is no special query to bypass this. Resolving this would be based on the situation with the particular file. Publishing it may resolve this, adjusting running workflows, or taking other actions. Many results in search indicate possible resolution depending on scenario.

Closing this issue as answered. If you have additional questions or we did not answer your question, please open a new issue, ref this issue, and provide any additional details available. Thank you!


Add performance sections to CHANGELOG

Codecov Report

Merging #79 (71d5677) into master (63dca16) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master       #79   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            3         3
  Lines          488       488
  Branches        93        93
=========================================
  Hits           488       488

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 63dca16...71d5677. Read the comment docs.


Bump k8s to 1.27

Description
Changes proposed in this pull request:

Bump k8s to 1.27

Related issue(s)

#390

Golang 1.22.0 introduced errors in tests


Remove customer.io service

Slingbot currently sends events to customer.io when customers have been throttled on AWS. Remove customer.io service hack since there were no plans for GA.

Looks good. :+1:


Module build failed: provided an invalid property of "wrapped"

I've been following the instructions on how to get react-google-maps working and I always get this error after launching my webpack server:

Module build failed: provided an invalid property of "wrapped"

If I shut the server and do a
npm install --save react-google-maps
And start it again, it works OK, If I stop the server and start it again I get the same error. Anyone else gettin this error?
Thanks.

I have the same error and
package.json
{
"name": "Ichigun",
"version": "0.0.1",
"private": true,
"scripts": {
"start": "node node_modules/react-native/local-cli/cli.js start",
"test": "jest"
},
"dependencies": {
"lodash": "^4.17.5",
"react": "^16.3.0-alpha.1",
"react-google-maps": "^9.4.5",
"react-native": "0.54.3",
"react-native-code-push": "^5.3.2",
"react-native-fbsdk": "^0.7.0",
"react-native-hud-view": "^1.2.2",
"react-native-read-more-text": "^1.0.0",
"react-native-splash-screen": "^3.0.6",
"react-native-vector-icons": "^4.5.0",
"react-navigation": "^1.5.8"
},
"devDependencies": {
"babel-jest": "22.4.3",
"babel-preset-react-native": "4.0.0",
"jest": "22.4.3",
"react-test-renderer": "^16.3.0-alpha.1"
},
"jest": {
"preset": "react-native"
}
}


Automated Package Upgrade

:tada: This PR is included in version 5.0.34 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


I'd like to remove myself, but cannot find a way

is it possible?
I've got no knowledge of ruby/rails/devise :/

@leonardodino Can you elaborate on what you want and why?


Make default merge_method of kubesphere/ks-devops be squash

What this PR dose / Why we need it
Make default merge_method of kubesphere/ks-devops be squash.
Squash and merge method is clearer than merging directly, please see the commit history:

/cc @kubesphere/sig-infra

/ping @kubesphere/sig-infra

/ping @kubesphere/sig-infra

/lgtm

/approve

/assign @zryfish

This setting doesn't seem to work well. Please see a real PR: https://github.com/kubesphere/ks-devops/pull/455, and we get two commits here:


Use a better abstraction for code generation

Right now, JavaScript code is generated by building pieces of it in arrays and manually concatenating them using .join('\n'). It’s conceptually simple, but the resulting code is messy and at a wrong level of abstraction. It should be talking about building and combining parts of the code, not doing array manipulation.
A better abstraction is needed. I imagine some kind of CodeBuilder class which would be used like this:
let code = new CodeBuilder();

code.emit("let list = [1, 2, 3];");
code.emit("let sum = 0;");
code.emit("");
code.emit("for (let item of list) {");
code.indented(() => {
  code.emit("sum += item;");
})
code.emit("}");
code.emit("console.log(sum);");

console.log(code.toString());

Note such class wouldn’t be PEG.js-specific and it could be split into a separate project.

Could you explain what this means for the peg.js project? What do you need exactly?

I have what amounts to an implementation of this as my solution to #638
One really nice thing about it is that it wouldn't be a huge hike from there to #628 as I initially understand it for things that don't involve user JS
I haven't figured out how your testing works yet so I'm not very confident of the change


Set TCP_NODELAY on the TcpStream to disable Nagle's algorithm.

Due to the way the async-h1 crate writes HTTP responses to the TcpStream the head and body end up in separate write calls to the underlying socket.  If we're responding to more than one request received from the same TcpStream it means that we did two sends and then tried to read.  That read can take up to 500 milliseconds to complete due to bad interactions between Nagle's algorithm and delayed ACK.  (In practice this is 40 ms on Linux.)
Disabling Nagle's algorithm works around this until async-h1 is fixed.
https://github.com/http-rs/async-h1/issues/199

Finally got around to figuring out how to fix this properly in async-h1.  C.f. http-rs/async-h1#200


Add: LEARNING PERFORMANCE-IMPROVING CODE EDITS 🥧

PR to add LEARNING PERFORMANCE-IMPROVING CODE EDITS with PIE dataset, few shot evaluations for program performance improvement

Nice! Some comments:

Remove .pyc .DS_Store and other files from the PR that are not important
Can't we upload all those .txt files to the hub? / Do we even need them? This PR adds way too many files imo
Can you share any results you got?

@Muennighoff Those are test cases and are needed in order to evaluate the correctness of the generated program.

@Muennighoff Those are test cases and are needed in order to evaluate the correctness of the generated program.

I think they should be uploaded to a dataset on the HF Hub that is then loaded like it's done for the other eval tasks

Nice! Some comments:

Remove .pyc .DS_Store and other files from the PR that are not important
Can't we upload all those .txt files to the hub? / Do we even need them? This PR adds way too many files imo
Can you share any results you got?

@Muennighoff

.pyc , DS_Store and other irrelevant files are removed
test cases are pushed to hub and integrated into the code without creating any variance during runtime evaluation


Whats New In Webpack 2 - Resolvers

This will be a sub issue, under "Whats New in Webpack 2"

We can stub this out. In a "Whats New in Webpack2" folder? Any opinions on this? @bebraw

Maybe start with a section at #20 given that's a priority item. If it looks like the ideas can be split into separate articles, then we'll split.

Perfect I like. Absolutely.

Webpack 2.0 Resolving
Webpack 2.0 has an updated enhanced resolving mechanism:
resolve: {
  extensions: ['', '.js', '.jsx'],
  modules: ['src', 'node_modules'],
  plugins: [new DirectoryNamedWebpackPlugin()]
  ...
},

This is a complete list of all possible fields within resolve:

Field
Default
Description

modules
["node_modules"]
A list of directories to resolve modules from, can be absolute path or folder name

descriptionFiles
["package.json"]
A list of description files to read from

plugins
[]
A list of additional resolve plugins which should be applied

mainFields
["main"]
A list of main fields in description files

aliasFields
[]
A list of alias fields in description files

mainFiles
["index"]
A list of main files in directories

extensions
[".js", ".json", ".node"]
A list of extensions which should be tried for files

enforceExtension
false
Enforce that a extension from extensions must be used

moduleExtensions
[]
A list of module extsions which should be tried for modules

enforceModuleExtension
false
Enforce that a extension from moduleExtensions must be used

alias
[]
A list of module alias configurations or an object which maps key to value

resolveToContext
false
Resolve to a context instead of a file

unsafeCache
false
Use this cache object to unsafely cache the successful requests

cachePredicate
function() { return true };
A function which decides wheter a request should be cached or not. An object is passed to the function with path and request properties.

fileSystem

The file system which should be used

resolver
undefined
A prepared Resolver to which the plugins are attached

Upgrade from Webpack 1.x to Webpack 2.x

resolve.root has been removed if you need it add the directory to the modules list
Instead of adding a resolver to plugins of your webpack config use the new resolve.plugin field

Looks great. 👍

The defaults in webpack are different: https://github.com/webpack/webpack/blob/master/lib/WebpackOptionsDefaulter.js#L73-L93

Would it make sense to align these defaults in this repo - I could work on this.

Yes I think it would.

@sebastiandeutsch I'd love to see a PR on this. If you aren't already working on it. We can provide some direction if needed.

@TheLarkInn You can see it here: https://github.com/webpack/enhanced-resolve/pull/39 I'll update the docs accordingly when it's accepted.

Webpack 2.0 Resolving
Webpack 2.0 has an updated enhanced resolving mechanism:
resolve: {
  extensions: ['', '.js', '.jsx'],
  modules: ['src', 'node_modules'],
  plugins: [new DirectoryNamedWebpackPlugin()]
  ...
},

This is a complete list of all possible fields within resolve:

Field
Default
Description

modules
["node_modules"]
A list of directories to resolve modules from, can be absolute path or folder name

descriptionFiles
["package.json"]
A list of description files to read from

plugins
[]
A list of additional resolve plugins which should be applied

mainFields
["main"]
A list of main fields in description files

aliasFields
[]
A list of alias fields in description files

mainFiles
["index"]
A list of main files in directories

extensions
[".js", ".json"]
A list of extensions which should be tried for files

enforceExtension
false
Enforce that a extension from extensions must be used

moduleExtensions
[]
A list of module extsions which should be tried for modules

enforceModuleExtension
false
Enforce that a extension from moduleExtensions must be used

alias
[]
A list of module alias configurations or an object which maps key to value

resolveToContext
false
Resolve to a context instead of a file

unsafeCache
true
Use this cache object to unsafely cache the successful requests

cachePredicate
function() { return true };
A function which decides wheter a request should be cached or not. An object is passed to the function with path and request properties.

fileSystem

The file system which should be used

resolver
undefined
A prepared Resolver to which the plugins are attached

Upgrade from Webpack 1.x to Webpack 2.x

resolve.root has been removed if you need it add the directory to the modules list
Instead of adding a resolver to plugins of your webpack config use the new resolve.plugin field

I've updated the defaults as @sokra pointed out.

Where does DirectoryNamedWebpackPlugin come from? could not find it in source.

@akomm it's an example Plugin that can be used.

It's not in the source.

Okay. I was just looking for a reason, why this does not work and thought that the plugin is responsible to provide the descriptionFiles functionality.

Looks like a related PR was merged. Time to close.

Correction
For those who gets the error like below;
Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
 - configuration.resolve.extensions[0] should not be empty.

Try not to use '' (empty string), use '*' instead.
example:
...
extensions: ['*', '.js', '.jsx'],
...

@drac no, * has not effect other that accepting module* as filename... Instead omit the empty string as it's added by default.

@sokra you are absolutely right, I edited my comment according to yours.


M1 Benchmarks

Making a separate issue for cleanliness.
Issue #10 point (3) described needing ARM / aarch64 benchmarks. Attached are M1 benchmarks that I can include into BENCHMARKS.md if helpful?
 If you could submit a pull request updating BENCHMARKS.md, that wouldbe wonderful. I will update the graphs with your new benchmarks.


Conflict with rye python shims

Description
In some Rye-using setups:

Starting jlab succeeds. Opening notebooks inside the jlab interface works, after selecting appropriate jupyterlab venv
Starting jlab notebookfile.ipynb fails to start. Dragging notebook to jlab window fails to open it the same way
The error there is "Jupyter server process terminated before the initialization completed"

Reproduce

Install Rye
~/.rye/shims/python is now the first python on $PATH
Install jupyterlab-desktop
Install jupyterlab as python -m pip --user  (~/.rye.shims/python user site environment) (Python 3.10)
Install jupyterlab separately in a more appropriate virtual environment "V"  (Python 3.12)
Open jlab. Select that you use virtual environment "V" in the drop down in the top of the window
Now try to open a notebook file using jlab notebookfile.ipynb

Expected behavior
jlab notebookfile.ipynb should maybe use the same selected virtual environment "V" that the user interface otherwise defaulted to.
jlab should not try to launch ~/.rye/bin/python as if it is a virtual environment, because it's not (it's a shim for a system interpreter).
Context
The following appeared in the debug log, and this obviously fails, because that activate script does not exist:
source "/home/ulrik/.rye/bin/activate"

This is quite suspicious - the "system python path" is "$HOME/.rye/bin/python" and jlab is treating that as if it's a .venv (it's not, that shim will reexecute to /usr/bin/python which is python 3.10)

Operating System and version: Ubuntu 22.04
JupyterLab-Desktop version: 4.2.1-1
Installer: .deb
platform: linux (x86_64)

Troubleshoot Output

Paste the output from running `jupyter troubleshoot` from the terminal inside of JupyterLab Desktop here.
You may want to sanitize the paths in the output.

Browser Output (required for interface issues after loading)

Paste the output from the DevTools JavaScript console here, if applicable.

Logs (required for issues with loading, server and startup)

Paste the logs from the `main.log` file here (optionally also from `renderer.log`).

Suggested Workaround
Make sure jupyter is not installed in any system interpreter's user site.
Thanks for the nice work on jupyterlab desktop :)

This looks like the same error message as in #847, although that issue mentions Windows 10 and doesn't mention Rye.

Out of curiosity, if you're not using Rye, do you see the same "Jupyter server process terminated before the initialization completed" error? If so, this might effectively be a duplicate of #847.

It's a very generic error message, I'm not surprised if separate problems can lead to the same place.
If I don't use rye I don't have the problem.

When this happens I can grab the launch script from the log - something like /tmp/jlab_desktopfiS6Bd/launch.sh - and that script starts jupyterlab correctly when I run it. So that's mysterious.

I can see now later that the source "/home/ulrik/.rye/bin/activate" is a red herring. (or maybe not?) but even cases that work print commands like source "/usr/bin/activate"  - another path that doesn't usually exist. (Which by the way is a correctness or even safety hazard - one can't just rely on that path not existing. It could be something that wrecks the execution.)

I'll abandon this bug as uv has taken over all rye's features, and I do not use rye anymore.


xSQLServerAlwaysOnAvailabilityGroup & xSQLServerAlwaysOnAvailabilityGroupReplica: Create helper function to check cluster permissions

Details of the scenario you try and problem that is occurring:
Code is duplicated in xSQLServerAlwaysOnAvailabilityGroup and xSQLServerAlwaysOnAvailabilityGroupReplica for testing the permissions on the cluster. Need to create a help function to reduce code duplication.
The DSC configuration that is using the resource (as detailed as possible):
N/A
Version of the Operating System, SQL Server and PowerShell the DSC Target Node is running:
All
Version of the DSC module you're using, or 'dev' if you're using current dev branch:
Dev

I'm working this one

Thanks @randomnote1! Labeled as in progress.


[T2A2][T17-A3]Sin Yu Fan

Refactor Main Function

Good job but you forgot to add the comment "Ready for review"

Please comment "Ready for review" next time.


[WIP] go1.19.4

Description
A detailed explanation of the changes in your PR.
Feel free to remove this section if it is overkill for your PR, and the title of your PR is sufficiently descriptive.
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
TODO(replace-me)
Use this space to explain how you tested your PR, or, if you didn't test it, why
you did not do so. Valid reasons include, for example, "CI is sufficient",
"No testable changes". Feel free to attach JSON snippets, curl commands,
screenshots.
In addition to reviewing your code, reviewers must also review your testing
instructions and make sure they are sufficient.

Closed by

https://github.com/stackrox/stackrox/pull/4769


updated markdown-link-check to address marked security issue

Security Fix
What are you trying to address
There is a security vulnerability in markdown-link-check version we use and this PR updates the version to address the vulnerability
Description of new changes
updates to markdown-link-check": "3.9.3"
For all pull requests

[ ] Link to the issue you are solving (so it gets closed)
[x] Label the pull request with the appropriate area(s)
[x] Assign potential reviewers (you may also want to contact them on Teams to ensure timely reviews)
[ ] Assign the project - Engineering Playbook Backlog
[x] Assign the pull request to yourself

@fnocera @brockneedscoffee I have fixed the broken links in https://github.com/microsoft/code-with-engineering-playbook/pull/789 if you want to review that - then we can merge and this should pass

#789

approved, let me know when it is merged and we will get this updated and merged in


Use TryComplete instead of Complete in ChannelExecutor dispose

We are seeing dispose problems sometimes in our integration test suite utilizing test harness and in-memory setup. As the Complete just calls TryComplete and throws exception if unsuccessful it feels that having the Try version in dispose makes more sense to ensure proper cleanup.
TearDown : System.Threading.Channels.ChannelClosedException : The channel has been closed.
 StackTrace: --TearDown
    at System.Threading.Channels.ChannelWriter`1.Complete(Exception error)
    at MassTransit.Util.ChannelExecutor.DisposeAsync() in /_/src/MassTransit/Util/ChannelExecutor.cs:line 63
    at MassTransit.InMemoryTransport.InMemoryReceiveTransport.ReceiveTransportAgent.ActiveAndActualAgentsCompleted(StopContext context) in /_/src/MassTransit/InMemoryTransport/InMemoryTransport/InMemoryReceiveTransport.cs:line 162
    at MassTransit.Middleware.Agent.Stop(StopContext context) in /_/src/MassTransit.Abstractions/Middleware/Middleware/Agent.cs:line 88
    at MassTransit.Middleware.Agent.Stop(StopContext context) in /_/src/MassTransit.Abstractions/Middleware/Middleware/Agent.cs:line 88
    at MassTransit.Transports.ReceiveEndpoint.Stop(Boolean removed, CancellationToken cancellationToken) in /_/src/MassTransit/Transports/ReceiveEndpoint.cs:line 175
    at MassTransit.Transports.ReceiveEndpoint.Stop(Boolean removed, CancellationToken cancellationToken) in /_/src/MassTransit/Transports/ReceiveEndpoint.cs:line 175
    at MassTransit.Transports.ReceiveEndpointCollection.StopAgent(StopContext context) in /_/src/MassTransit/Transports/ReceiveEndpointCollection.cs:line 106
    at MassTransit.Middleware.Agent.Stop(StopContext context) in /_/src/MassTransit.Abstractions/Middleware/Middleware/Agent.cs:line 88
    at MassTransit.Middleware.Agent.Stop(StopContext context) in /_/src/MassTransit.Abstractions/Middleware/Middleware/Agent.cs:line 88
    at MassTransit.Transports.BaseHost.Stop(CancellationToken cancellationToken) in /_/src/MassTransit/Transports/BaseHost.cs:line 154
    at MassTransit.MassTransitBus.Handle.StopAsync(CancellationToken cancellationToken) in /_/src/MassTransit/MassTransitBus.cs:line 386
    at MassTransit.MassTransitBus.Handle.StopAsync(CancellationToken cancellationToken) in /_/src/MassTransit/MassTransitBus.cs:line 386
    at MassTransit.MassTransitBus.Handle.StopAsync(CancellationToken cancellationToken) in /_/src/MassTransit/MassTransitBus.cs:line 402
    at MassTransit.MassTransitBus.StopAsync(CancellationToken cancellationToken) in /_/src/MassTransit/MassTransitBus.cs:line 265
    at MassTransit.MassTransitBus.StopAsync(CancellationToken cancellationToken) in /_/src/MassTransit/MassTransitBus.cs:line 265
    at MassTransit.MassTransitHostedService.StopAsync(CancellationToken cancellationToken) in /_/src/MassTransit/MassTransitHostedService.cs:line 59
    at MassTransit.MassTransitHostedService.StopAsync(CancellationToken cancellationToken) in /_/src/MassTransit/MassTransitHostedService.cs:line 59

Since MassTransit now uses TaskExecutor, does this same change apply there as well?

OK so it seems that I'm basing my fix based on old information 😅 ChannelExecutor seems to only be used by ActiveMqConsumer.. There are other places which call Complete in dispose though - TaskExecutor not being one of them. Should I update the PR to call TryComplete in all places Dispose it isn't called yet or should I just close this?

Don't close it, it's a valid fix. If there are other places where TryComplete could be used, it would be good to catch those as well. I just checked, and TaskExecutor does in fact already use TryComplete.


Improve speed of transferring foam to periodic box

Using OpenCASCADE through python bindings could be faster than doing it through gmsh. Installation can be done from through conda. Demos are here.

Resolved by commit aeeef34bf47389c811cddc4e6ee918782637c38e.
Used pythonocc to gain significant improvents. Also improved definition of meshing files, so that it is not necessary to translate between different CAD formats.
Further improvements are possible if we do the definition of foam walls using pythonocc and not in pure python.


"Archive" finalised tosti transactions

Related to #337, it would be nice if the orders that have been picked up are removed from the main list and are placed in a drawer of some sort.

Duplicate of #258.


stm32H7  cannot XiP  from dual quad nor in Memorymapped mode

When executing the samples/application_development/code_relocation_nocopy/ on the stm32h745i_disco//m7 disco kit,
the function_in_ext_flash cannot execute correctly fro theexternal NOR flash
The external NOR flash is configured in memoryMapped mode with
CONFIG_STM32_MEMMAP=y
The samples/application_development/code_relocation_nocopy/ is build with quadspi memory region set at 0x90000000
The function_in_ext_flash is downloaded  in ext flash, but execution fails
*** Booting Zephyr OS build v3.6.0-4147-gadeb19b30cbf ***
Address of main function 0x800066d
[00:00:00.000,000] <err> os: ***** BUS FAULT *****
[00:00:00.000,000] <err> os:   Instruction bus error
[00:00:00.000,000] <err> os: r0/a1:  0x00000003  r1/a2:  0x00000000  r2/a3:  0x00000004
[00:00:00.000,000] <err> os: r3/a4:  0x00000000 r12/ip:  0x00000000 r14/lr:  0x08000681
[00:00:00.000,000] <err> os:  xpsr:  0x61000000
[00:00:00.000,000] <err> os: Faulting instruction address (r15/pc): 0x90000000
[00:00:00.000,000] <err> os: >>> ZEPHYR FATAL ERROR 27: Unknown error on CPU 0
[00:00:00.000,000] <err> os: Current thread: 0x24000800 (unknown)
[00:00:00.042,000] <err> os: Halting system

Environment (please complete the following information):

OS: (e.g. Linux, MacOS, Windows) ubuntu
Toolchain (e.g Zephyr SDK, ...) 0.16.3
Commit SHA or Version used  adeb19b30cbfb3552cb2d19c6c6676a872afe6c0

Code is correctly flashed in the external NOR at address 0x90000000
file:///local/home/frq09495/Pictures/Screenshots/Screenshot%20from%202024-05-20%2015-31-39.png

On the stm32h745i_disco, the  external NOR memory is made of two  quad NOR connected to 2 qspi banks
but the stm32 qspi driver does not set the DualFlashMode (DFM) bit in the QUAD_SPI control rgister.


Switch from LGTM to GitHub code scanning

Describe the bug
On pvlib's GitHub landing page (readme file), there's a shield/link to LGTM. While following this link, I noticed the following warning message:

LGTM.com will be shut down in December 2022 — we recommend that you use GitHub code scanning instead. Read more in our blog post on the GitHub blog.

So sometime before December, we should address this issue by either:

removing the LGTM shield from the readme file
switch to GitHub code scanning
find a third alternative

Upon reading the blog post linked in the message, it seems that the best option might be to just wait:

October: help migrate repositories to GitHub code scanning
We will do our best to help migrate repositories that actively use LGTM.com to flag potential security issues in their pull requests. For those repositories, we will create pull requests that add a GitHub Actions workflow that runs code scanning. Once that configuration file is merged, the repository’s source code (and future pull requests) will be scanned by GitHub code scanning. GitHub code scanning will flag any potential security issues in pull requests and on the repository’s security tab. Once that’s all working as it should, you can disable the LGTM.com integration.

As described above, a PR has been made by GitHub #1600.

I'm not convinced that LGTM/GitHub code scanning is particularly useful for us.  Security vulnerability analysis doesn't seem relevant for pvlib (to me, anyway), and I think its other functionality (linting, static analysis) is redundant with our other CI checks.  I'm also not excited about curating the list of "dismissed alerts".  If it were me I would probably get rid of it for this repository.  But I also haven't looked into it very much and would be happy to learn I am overlooking some nice aspects :)

Just as a comment, many of the issues that were flagged by LGTM were recently fixed in https://github.com/pvlib/pvlib-python/pull/1559.

For reference #554 added the LGTM badges. I liked them at the time because they showed that pvlib's code quality was very good and it did find a couple of minor bugs. I've been less than enthusiastic about it since then. I don't have a preference on this, just wanted to point to that context.

Closing the PR and issue related to adding GitHub code scanning due to lack of interest from maintainers.


Add missing locale conversions

These characters were flagged by the script in https://github.com/espruino/BangleApps/pull/3268 - they are used in some of the locales but are not supported by Banglejs.
Some of them are only used in the CLDR data, but some of them are also used right now in real locales, so those locales are just broken. Even if we never merge the CLDR script, I don't see the harm in adding a few characters to this list.

Sorry this might be more complicated than I first thought. I think something else is breaking the locales, these characters seem to only be present in the CLDR data. Either way if you don't mind adding them, it would make my life a bit easier :)

Thanks! Yes, no problem at all adding these. Anything to map from char code >256 down to ISO8859-1 is great


Flatpak build

Please, consider supporting Flatpak and publishing Microsoft Edge on Flathub.

@TheLarkInn as FYI. @LeandroStanger thanks for the suggestion.

@LeandroStanger feel free to maintain and publish in Flathub: https://github.com/TheEvilSkeleton/com.microsoft.Edge

@LeandroStanger http://github.com/MicrosoftEdge/MSEdgeExplainers/issues/399
git clone https://github.com/TheEvilSkeleton/flathub.git
cd flathub/
git checkout com.microsoft.Edge
git clone https://github.com/flathub/shared-modules/
flatpak-builder --force-clean --install-deps-from=flathub --install --user build-dir com.microsoft.Edge.yaml

@travisleithead in case you're interested: https://github.com/flathub/flathub/pull/1992
Just keep in mind that they want the flatpak to be officially maintained by a member of the Edge team: https://github.com/flathub/flathub/pull/1992#issuecomment-744427689


Is there any way to make this work with a local model?

Feature Request: I'd really like to make this work with a local model running on my own computer. Is this possible? Can it be made possible?

Hi. Yep, i think it possible right now, if you will use local API, but i don't know how the local model works and does the local model has a API for work with them. Can you give more information about installing and running local model for debug and develop?

I mean, if the local model have web API like reference API from site, you can use them changing URL of API in extension settings to localhost.

I am running it locally with auto gptq and 10gig of GPU ram. Bits quite fast. But I am now looking for how to set up the api so that the plugin can prompt it correctly

I readed docs for Star Coder and i think, for work with plugin necessary write driver. I can write it but i need to install StarCoder on computer. So, wait changes in that issue branch.

I just found the server side code for the plugin. https://github.com/LucienShui/huggingface-vscode-endpoint-server. Would this work?

Yes, i think it must work. Please, after test tell me results ;)

I think it works. It was a bit buggy but it did return some responses. I think it's an issue with the version of remote vscode I am using.

Thanks for feedback!


Implement semver

Looks like we need to do some bugfix releasing, and with the new and simpler docs versioning, that may be feasible.
So we may have a Hugo 0.18.1 etc.

I want to add some kind of semver lib to Hugo, I found these candidates (there are more):

https://github.com/blang/semver
https://github.com/Masterminds/semver

The former have more stars, but I kind of like the last one: It supports "v" prefix and have caret and tilde support in its range matching.
Thoughts anyone?
/cc @moorereason

Yes, yes, yes!  We should be using Semantic Versioning.
Read this if you haven't yet.  It looks like gps will be the basis of whatever gets merged into the go tool chain, and gps uses https://github.com/Masterminds/semver.
However, what's the point of using a semver library in Hugo?  Why do we need to parse semver?  All Hugo needs is a version string.  What are you wanting to do other than just using a proper vMAJOR.MINOR.PATCH release version and creating a git tag?

What are you wanting to do other than just using a proper vMAJOR.MINOR.PATCH release version and creating a git tag?

I'm currently doing calculations on "what is next release version" and "is this theme compatible with the current Hugo version?" That math is trivial with the current versioning scheme; it's not too hard with 3 digits, either, but it gets complicated once we get some range logic.


Add _original_ordering to estimator public API

Since we must use argsort to simultaneously sort the X, and y, a workaround we have been using in the bema application is to assure we maintain the original ordering using argsort_1d_idx utility and then attach the _original_ordering of the X method so we can later take the inverse and return the original unsorted args.
This was done on the original rpc server as a hack so it would be best to set this directly using fit_one and then expose this object more formally on the estimator object for later retrieval in the results.

Added this in last PR... you can now set this publicly.
I don't want to have the estimator implicitly set this because side effects are bad. It is just useful to be able to move the Ordering object along with the estimator for purposes of batching


Threadsafety of Library?

Hello!
I was interested in some information regarding the threadsafety of this library (the GerritApi object).  I did some reading of the source and found some low level locking (in CookieStore for example), but I wanted to make sure that the library is considered threadsafe in its entirety.  How will it handle 15-20 threads pounding the same GerritApi object?
Also as a sidenote, is it safe to have multiple GerritApi objects floating around in the wild (do they share any static non-threadsafe members?)
Thank you very much for your time, and for creating this library.
Liam.

I think it should be thread safe.
One thing which probably not plays very nicely, is LoginCache, but it should not cause any issues.

Also as a sidenote, is it safe to have multiple GerritApi objects floating around in the wild (do they share any static non-threadsafe members?)

That should also work. The cache mentioned above is not shared, but it works nevertheless.
If you find any issues, please let me know.


Make the history layout more consistant with the search layout

Current search: https://user-images.githubusercontent.com/1689815/36647480-913da272-1a86-11e8-8cdd-49973013ec46.png
Proposed history:

Related: #840

Seems good. Can I work on it?

Looks like there is no progress here, so I've taken this issue.


Logger - derived class implementation guide

As switched to C style implementation, this issue is not valid.
Please refer to https://github.com/souravbatabyal-github/deccenc/issues/13


Rest API for uploaded YANG modules

Is it possible to upload a set of zipped yang modules using the rest API and get them validated ?
What is the first part of the URL
https://www.yangvalidator.com/yangvalidator/rest
or
https://www.yangvalidator.com/yangvalidator
Thanks Balazs

This API is CSRF procted and therefore browser is required. This is for security reasons.
The response would come in HTML format anyway so parsing that would be probably a nightmare .
regards,
Miroslav Kovac

IMHO the reason for the REST API is to allow automation. It would be nice to use it for uploaded files too.
I understand there are issues.
I don't understand the CSRF part, as in the browser, there is no login or authentication.
Anyways thanks for the answer.

We will be rebuilding the whole UI so I ll take this into consideration for that as well. Should be done like in late February with new release.

Hello,
after release of the new YANG Catalog UI functionality of uploading set of zipped yang modules using the rest API is available.
Feel free to check it here: https://yangcatalog.org/yangvalidator
API Documentation: https://yangcatalog.org/yangvalidator/api
Regards,
Slavomir Mazur


RangeError when used with videojs-youtube and videojs-vimeo

Hi there.
It seems that this plugin only works if the source is a video file. I get this error when it's used with videos from YouTube or Vimeo, and sometimes the browser crashes:
VIDEOJS: RangeError: Maximum call stack size exceeded(…) videojs.js:19296 VIDEOJS: RangeError: Maximum call stack size exceeded(…)
The stack looks like this:

Please let me know if anyone could help me solve this problem.

This is an infinite loop issue: this.currentTime(0) calls the function setCurrentTimein videojs-youtube, which itself triggers a timeupdate event. Since we are already in the onPlayerTimeUpdate function, this leads to infinite function calls.
A workaround would be to switch timeupdate off and on again:
this.off('timeupdate', onPlayerTimeUpdate);
this.currentTime(0);
this.on('timeupdate', onPlayerTimeUpdate);

Thank you @Yi-Zhou and @bjmrey I'll take a look ASAP.

Yeah, stumbled here too


Added some helmet headers, easter egg(URL path) and godotenv

Added basic security headers (Was not able to find any thing such as helmetjs for go so added a middleware). Added an Easter egg (middleware) which display a message/page that you visited the Easter egg page.
Added godotenv for easier management of  environment variables.

Undo godotenv

Done


Refactoring to es6 - vars and functions.

Updated client/services code to es6 - replaced vars with const and let, and updated some functions to arrow functions.

 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.


Adding web stories to Post categories on WordPress

Feature Description

I would like to request for the feature that allows web stories to be categorized as we do it for other posts on our website.
Would
Alternatives Considered

Additional Context

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria

Implementation Brief

Thanks for your suggestion!
We're already tracking this enhancement in #489. Please follow that ticket for any updates on the matter.


No module named 'gfootball-engine'

How can I solve it? please

You haven't installed gfootball properly. Please follow the instructions in README.md. You can also try Docker.
Your log suggests that you're using anaconda, so you should install gfootball in the environment. When posting an error, please use code block  instead of a screenshot.

Thank you very much!
发自我的iPhone
------------------ Original ------------------
From: Victor Khaustov @.>
Date: Tue,Jul 20,2021 7:35 PM
To: google-research/football @.>
Cc: minhoooo1 @.>, Author @.>
Subject: Re: [google-research/football] No module named 'gfootball-engine' (#281)
You haven't installed gfootball properly. Please follow the instructions in README.md. You can also try Docker.
Your log suggests that you're using anaconda, so you should install gfootball in the environment. When posting an error, please use code block  instead of a screenshot.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Selection is sometimes not cleared

[x] I have read through the manual page (man fzf)
[x] I have the latest version of fzf
[x] I have searched through the existing issues

Info

OS

[x] Linux
[ ] Mac OS X
[ ] Windows
[ ] Etc.

Shell

[x] bash
[ ] zsh
[ ] fish

Problem / Steps to reproduce
With the last action executed, fzf fails to reset selection if a query is specified and then later cleared.

Launch fzf like this:
{ echo $'npm1\nnpm2\nnpm3'; seq 3; } | fzf --tac --bind=home:last

Press Home key to move selection to the first entry.

Type npm as the query.

Press Delete key 3 times (or Ctrl+u) to clear the query.

Observed Behavior
Fourth line, i.e. 1 is selected.
Expected Behavior
The very first (oldest input in this case) shall be selected.
Notes
This issue also reproduces if the selection is changed using the arrow keys in Step 2.
$ fzf --version
0.30.0 (2093667)

fzf wasn't designed to work that way. The cursor simply stays at the same vertical position if possible regardless of the query string.


Fix find last backup method

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (5a87c9f) 20.08% compared to head (7967d01) 20.89%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #80      +/-   ##
==========================================
+ Coverage   20.08%   20.89%   +0.81%
==========================================
  Files          28       28
  Lines        1205     1206       +1
==========================================
+ Hits          242      252      +10
+ Misses        941      932       -9
  Partials       22       22

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


QueryState now spits out FunctionState

Motivation
Instead of spitting some unformatted stuff, made querystate print out a proper json object.
Modifications
Describe the modifications you've done.
Result
After your change, what will change.

over all lgtm. a small comments


fixed unnecessary border around code

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #51009

Thank you for your interest in contributing.
We typically merge the first pull request that comprehensively resolves the issue. As such, we are closing this in favour of #50968.