Allow Multiple Hosts

So this may just be how we have our logging infrastructure structured, but I'd figure I'd toss it out there for discussion.
We use NXLog to ship from our application servers to a Logstash collector which then routes the events based on log type and version to their own queue within RabbitMQ local on the server. We have one collector per datacenter that balance the load via geographical DNS resolution (so application servers write to the collector in their DC).
On the indexing side, we currently have 2 servers that read from both RabbitMQ instances. The configurations are identical and how the inputs are currently defined, we have to specify them twice (one for each host).
rabbitmq {
	codec => "json"
	host => "broker1.contoso.com"
	port => "5671"
	ssl => "true"
	vhost => "logging"
	queue => "software.dotnet.iis.access.v1"
	passive => "true"
	tags => ["software","dotnet","iis","access_logs","unprocessed"]
	type => "iis_access_v1"
}

rabbitmq {
	codec => "json"
	host => "broker2.contoso.com"
	port => "5671"
	ssl => "true"
	vhost => "logging"
	queue => "software.dotnet.iis.access.v1"
	passive => "true"
	tags => ["software","dotnet","iis","access_logs","unprocessed"]
	type => "iis_access_v1"
}

Ideally, I'd like to be able to pass in an array for the host(s) value, since the rest of the values are identical.
rabbitmq {
	codec => "json"
	hosts => ["broker1.contoso.com","broker2.contoso.com"]
	port => "5671"
	ssl => "true"
	vhost => "logging"
	queue => "software.dotnet.iis.access.v1"
	passive => "true"
	tags => ["software","dotnet","iis","access_logs","unprocessed"]
	type => "iis_access_v1"
}

Thoughts?

Could be hard, since this plugin relies on https://github.com/rabbitmq/rabbitmq-java-client which not support this.
You could use HAProxy between?

This is now possible though our docs are not yet updated. See https://github.com/logstash-plugins/logstash-mixin-rabbitmq_connection/commit/21b121c83f8cb84265fa9788147aa87b90e0299a#diff-5a4e6da9864c64f906837378a6f551e6R21


Use project locations instead of project names in open

when using cppm to open a project from another directory:
user@hostname ~/dir $ cppm open ~/owo
Project does not exist or was not created with cppm!

@rubyowo Why should locations be used? that would defeat the entire purpose of open.

wait

Closing this because im dumb.


Transitive sets don't aggregate across cells

This seems like a bug, because you can do this with any of the rules in the prelude. My instinct is that the hackery to get stuff in the prelude somehow gets around this problem.
Repro: https://github.com/cormacrelf/buck2-tset-bug

library and binary rules in cell one//, doing pretty much what the cxx rules in prelude do
Define some libraries in one cell
Define a binary in another cell
???
Breaks

# root BUCK file
load("@one//:rules.bzl", "binary", "library")

library(name = "a")
library(name = "b", deps = [":a"])
binary(name = "works", deps = [":a", ":b"])

# these fail though
binary(name = "fails", deps = ["one//:lib"])
binary(name = "fails2", deps = ["two//:lib"])

buck2 build :works    # works
buck2 build :fails    # fails

Full error:

Transitive set transitive values must be of the same transitive set type
(expected: TransitiveSetDefinition(InfoTSet declared in one//rules.bzl@root),
got: TransitiveSetDefinition(InfoTSet declared in one//rules.bzl))

BUILD FAILED
Error running analysis for `root//:fails (prelude//platforms:default#200212f73efcd57d)`

Caused by:
    Traceback (most recent call last):
      File <builtin>, in <module>
      * one/rules.bzl:38, in __binary
          tset = ctx.actions.tset(
    error: Transitive set transitive values must be of the same transitive set type (expected: `TransitiveSetDefinition(InfoTSet declared in one//rules.bzl@root)`, got: `TransitiveSetDefinition(InfoTSet declared in one//rules.bzl)`)
      --> one/rules.bzl:38:12
       |
    38 |       tset = ctx.actions.tset(
       |  ____________^
    39 | |         InfoTSet,
    40 | |         children = [
    41 | |             dep[InfoGraph].tset
    42 | |             for dep in ctx.attrs.deps
    43 | |         ],
    44 | |     )
       | |_____^
       |

This is likely due to the fact we load bzl files once for each cell.
Internally we do it for historical reasons.
I think for OSS version, which does not have such legacy, we should just load each bzl files once (as we want to migrate internally too).

Note to self on where this lives:
https://github.com/facebook/buck2/blob/main/app/buck2_interpreter_for_build/src/interpreter/interpreter_for_cell.rs


Fix protocol ternaries

Fixed in https://github.com/kevva/caw/commit/2c68b53f8d9e6f1e73e4a018781066392e5f3d1a. Huge thanks for all the additional tests :).


browser support issue in chrome

Hi all, i'm using react-speech-recognition like so in my react project:
import React, { Component } from "react";
import SpeechRecognition from "react-speech-recognition";
import { Button } from 'react-bootstrap';
class Dictaphone extends Component {

componentDidUpdate=(prevProps)=>{
  console.log(prevProps,this.props.cursor)

  if (this.props.readAlongHighlightState===true){
      let {transcript} = prevProps

              if(this.props.cursor !== '' && this.props.cursor !== undefined){
                var cursor = this.props.cursor

                  //console.log("cursor parentNode ",cursor.anchorNode.parentNode)
                  //console.log("just cursor",cursor)
                  //console.log("just inner html",cursor.anchorNode.parentNode.textContent)
                  //console.log("cursor innerhtml",cursor.anchorNode.innerhtml)

                    if(transcript.includes(" ")){
                        transcript = transcript.split(" ").pop()
                        console.log(transcript)
                      }

                        console.log("cursor anchor node textcontent:",cursor.anchorNode.textContent)
                        if(transcript === cursor.anchorNode.textContent.toString().toLowerCase()){
                          cursor.anchorNode.parentNode.style.backgroundColor = 'yellow';
                          cursor = cursor.anchorNode.parentNode.nextElementSibling
                            this.props.updatecursor (cursor); //highlight the span matching the intent

                        }else{
                              console.log("no cursor")
                              }
                          }
                        }
                      }

  render() {
   const {transcript, resetTranscript, browserSupportsSpeechRecognition} = this.props

    if (!browserSupportsSpeechRecognition) {
      return null
    }
    if(transcript==="notes"||transcript==="cards"||transcript==="home"|| transcript==="settings" || transcript==="read document"){
      this.libraryOfIntents(transcript,resetTranscript);
    }

    return (

         {transcript}
        <Button variant="outline-dark" onClick={resetTranscript}>Reset</Button>

    )
  }
}

for some reason, all of a sudden my browser is not recognizing any speech from my microphone. I have used different microphones and even different computers. I have tried using npm update and I have tried using an older version of my app I have saved where I know the component works. However now that version of the app has the same issue.
I'm wondering if there are new updates in chrome that might be causing a bug in the current version of react-speech-recognition?

I'm wondering if there are new updates in chrome that might be causing a bug in the current version of react-speech-recognition?

I don't see this. I had my app working with 78.0.3904.70, updated to
78.0.3904.87 just now, and the app still works, speech recognition
and all. (live demo)

Thanks for the demo! i'm still having trouble but I'm honestly not sure where to begin. My browser isn't actually requesting access to the microphone at all if that's any indicator that something is off

@lwardlegit Check the right side of your browser location bar to make sure Chrome isn't denying access automatically. I had that happen once - I assume I accidentally clicked "deny" and then Chrome doesn't ask again.
If that's not it, I'd try logging to make sure startListening is called. That's the point at which Chrome should ask for permission.

Hey Stephen, it looks like it was an issue with my browser. After removing microphone access for my app's url I was prompted to allow the microphone and now its working again! thank you for all your help.
I really appreciate it


huge slow downs

Type: Bug
this add on may be malicious
Extension version: 12.10.0
VS Code version: Code 1.96.0 (Universal) (138f619c86f1199955d53b4166bef66ef252935c, 2024-12-11T02:29:09.626Z)
OS version: Darwin x64 24.1.0
Modes:

System Info

Item
Value

CPUs
Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz (16 x 2300)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabledwebgpu: enabledwebnn: disabled_off

Load (avg)
13, 12, 9

Memory (System)
16.00GB (0.89GB free)

Process Argv
--crash-reporter-id e67cb61e-ddf4-4273-90f3-5448f178fed7

Screen Reader
no

VM
0%

Hi @jaws777, thank you for reporting this. The extension is definitely not malicious. We have lots of users and almost nobody is reporting this kind of slow downs.
This may indicate that it may be something with your system or configuration. Or a combination of extensions in your system. Or everything together.
Have you tried Extension Bisect?
We would need more information in order to find what's going on. I'm personally running the extension in Sequoia 15.2 along with many others and haven't found any issue.

It's no secret that we have a HUGE number of icons, which in some cases can cause a slow down.
In my experience, I often get slowed down by file watcher.
Have a look at what Microsoft has to say about it.
@robertohuertasm Have a read  on it yourself.
@jaws777 Try using the files.watcherExclude vscode setting to exclude our icons folder and see if it makes any difference. Where is the extension folder?


d2619083-d70c-41dc-9073-50e4f8057f8e

this is for automated testing

1987749e-ce70-4e56-9300-f3d67f8032d5


[Impeller] Create a way to run the golden image tests locally.

Skia gold is super helpful on CI, but if it identifies a problem and you want to fix it locally it takes too long to verify the fix since the golden image tests can't be run locally and the golden image test is the last step for CI.
impeller_golden_tests keeps the images around when it executes, maybe we could make a quick and dirty Dart script that will compare 2 runs using some local diff.  That wouldn't match the diffing happening on skia gold but may be helpful for local testing.

I'm highly supportive of this but I don't know how to achieve this.


DocumentIntelligenceClient is not a function

Edit 5/24/2024 5:50 PM
I have tried running the example from the legacy 3.1 documents and do not run into this issue. It seems this is only an issue with the v4.0 documentation.
Output is
`Pages:

Page 1 (unit: inch)
8.5x11, angle: 0
67 lines, 413 words
Tables:
Extracted table: 3 columns, 5 rows (15 cells)
Extracted table: 2 columns, 2 rows (4 cells)`

Original
I have tried running the example from the v 4.0 documentation and received this error.
I am running Node 16.13.0 on Windows 10.
I'm not sure what I am doing wrong or if the example has faulty code. Any guidance or resolution would be helpful. Thank you.

Please provide us with the following information:

This issue is for a: (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request
- [x] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Copy and run the prebuilt model example from the javascript documentation
Any log messages given by the failure

An error occurred: TypeError: DocumentIntelligenceClient is not a function

Expected/desired behavior

Successfully analyze the sample document

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)
Windows 10

Versions

Mention any other details that might be useful

Thanks! We'll be in touch soon.

Here is an example that works.
const DocumentIntelligence = require("@azure-rest/ai-document-intelligence").default,
    { getLongRunningPoller, isUnexpected } = require("@azure-rest/ai-document-intelligence");
const { AzureKeyCredential } = require("@azure/core-auth");

const { config } = require("dotenv")
config()

// sample document
const invoiceUrl = "https://raw.githubusercontent.com/Azure-Samples/cognitive-services-REST-api-samples/master/curl/form-recognizer/sample-invoice.pdf"

// set `<your-key>` and `<your-endpoint>` variables with the values from the Azure portal.
const key = process.env.KEY;
const endpoint = process.env.ENDPOINT;

async function main() {

    const client = DocumentIntelligence(endpoint, new AzureKeyCredential(key));

    const initialResponse = await client
        .path("/documentModels/{modelId}:analyze", "prebuilt-invoice")
        .post({
            contentType: "application/json",
            body: {
                // The Document Intelligence service will access the URL to the invoice image and extract data from it
                urlSource: invoiceUrl,
            },
        });

    if (isUnexpected(initialResponse)) {
        throw initialResponse.body.error;
    }

    const poller = await getLongRunningPoller(client, initialResponse);

    poller.onProgress((state) => console.log("Operation:", state.result, state.status));
    const analyzeResult = (await poller.pollUntilDone()).body.analyzeResult;

    const documents = analyzeResult?.documents;

    const result = documents && documents[0];
    if (result) {
        console.log(result.fields);
    } else {
        throw new Error("Expected at least one invoice in the result.");
    }

    console.log(
        "Extracted invoice:",
        result.docType,
        `(confidence: ${result.confidence || "<undefined>"})`,
    );
    console.log("Fields:", result.fields);
}

main().catch((error) => {
    console.error("An error occurred:", error);
    process.exit(1);
});

DocumentIntelligence is the default export of the SDK.
createClient method can also be imported which returns an object of type DocumentIntelligenceClient.
Moreover, you can name it however you want while importing a default export and it will work exactly the same.
For instance,
const DocumentIntelligenceClient = require("@azure-rest/ai-document-intelligence").default,
        { getLongRunningPoller, isUnexpected } = require("@azure-rest/ai-document-intelligence");


Add "expect nothing" call to verify

Duplicating the PR by @thomashilzendegen to the new repo
"This fixes the warning/error of jasmine that a test has no expectations.
See https://github.com/NagRock/ts-mockito/issues/128."

I'm not too sure how I can reliably test this one to meet codecov requirements due to the use of globalThis. Would appreciate some suggestions.

@mikeporterdev is this fix specific for jasmine? I less like this concepts, as there are many other runners and the lib should be agnostic to the runner,
Today the tests run using Jest as well, but what about newer popular runners such as vitest for e.g.?
I started to use vitest in every new project, Jest has annoying issues with esmodules..
WDYT?

@LironHazan indeed this fix is specific to Jasmine but it's written in a way that shouldn't affect any other test runner. I actually only use ts-mockito with jest.
Supporting all test runners should definitely be something we seek to support imo


nix-prefetch-url fails to fetch local file (1.5G)

$ nix-prefetch-url file:///home/ielectric/Downloads/PA_Linux_79317.tar.bz2
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
 52 1463M   52  767M    0     0   519M      0  0:00:02  0:00:01  0:00:01  520M
curl: (23) Failed writing body (12256 != 16383)
/run/current-system/sw/bin/nix-prefetch-url: download of ‘file:///home/ielectric/Downloads/PA_Linux_79317.tar.bz2’ failed

Do you know about this: https://nixos.org/wiki/How_to_add_large_files_to_the_nix-store? BTW, it's more of a nix issue, not nixpkgs.

Yeah. I used sha256sum /home/ielectric/Downloads/PA_Linux_79317.tar.bz2 to get the hash and nix-store --add-fixed to get the file inside the store. But why does curl bark? I have 8G of memory and the file is only 1.5G so this shouldn't be a problem.

Figured it out, it's because of tmpfs
tmpfs           768M   20K  768M   1% /run/user/499

Running it as root results into:
$ nix-prefetch-url file:///home/ielectric/Downloads/PA_Linux_79317.tar.bz2
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 1463M  100 1463M    0     0   514M      0  0:00:02  0:00:02 --:--:--  479M
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
Aborted

$  nix-env --version
nix-env (Nix) 1.9pre4045_bd91064

cc @edolstra

It seems the file can't fit into your /tmp/.

Yeah, I figured. This should be better documented.

I don't get what you want to document. Printing a better error message in this case?

Clearly, curl failing is not a good error message if the file doesn't fit into /tmp. Ideally we could handle file:// as a special case.

Ah, yes: that way we would avoid the double copying.

(triage) @vcunat @domenkozar solved?

I don't think so, looking at git log for <nix/src/nix-prefetch-url/>.

Moved to https://github.com/NixOS/nix/issues/1014


Fix typos

Found few misspellings with typos.
Are you interested in the configuration?

Thanks @szepeviktor!


DBZ-5824 refactor GitHub Actions deprecated set-output command

https://issues.redhat.com/browse/DBZ-5824

Applied to main (=2.1) and branch 2.0.


CLIENT SYSTEM IS NOT GOING TO SLEEP MODE

Hi,
I am implementing the HID keyboard using ESP32 through ESP-IDF for that i am using the below library
https://github.com/asterics/esp32_mouse_keyboard
It is working fine but when my BLE is connected ,client system is not going to sleep mode it is waking automatically after few seconds.
i am requesting you could you please help on this

Hi,
i think sleep mode is not implemented in HID, but you can try to stop sending notifications.
In HID keyboard there are OUTPUT and INPUT report characteristic, one is to send key codes the other is to receive info from client, for example info about CAPS LOCk etc. It is possible that client is sending data to let keyboard know when is entering sleep mode (but im not sure). Try to catch all messages on that characteristic.

Hi thanks for your reply we are stopping the notifications  when client is disconnecting using below functions even though it is waking automatically i guess because of advertising how can i stop the advertising please help me.
if(activateKeyboard)
{
desc = (BLE2902*) inputKbd->getDescriptorByUUID(BLEUUID((uint16_t)0x2902));
desc->setNotifications(false);
kbd->stop();
}
if(activateMouse)
{
  desc = (BLE2902*) inputMouse->getDescriptorByUUID(BLEUUID((uint16_t)0x2902));
  desc->setNotifications(false);
  mouse->stop();
}

if(activateJoystick)
{
  desc = (BLE2902*) inputJoystick->getDescriptorByUUID(BLEUUID((uint16_t)0x2902));
  desc->setNotifications(false);
  joystick->stop();
}

i want to stop the advertising when client is going to sleep mode because of advertising my client system is not going to sleep mode  mode .as well as i want connect automatically when client is wakes please help me on this


[DOC] How to use Grafana

Preliminary Checks

[X] This issue is not a question, feature request, RFC, or anything other than a bug report. Please post those things in GitHub Discussions: https://github.com/nebari-dev/nebari/discussions

Summary
How to setup/use Grafana
Steps to Resolve this Issue
.

As discussed on Slack, we can close because we have https://www.nebari.dev/docs/how-tos/monitoring/#grafana


HRotate examples missing import

Hey @clintjhill, thanks for this.  Josh is currently reworking the examples. Once that's ready we will merge your changes.

resolved in #98


loadMore Setting Missing/Not Working

I used the loadMore setting in the previous version of this plugin, but I can't get it to work in the latest version. After looking at both versions of JS,  it's clear that a lot has changed from the previous version, and in terms of the loadMore setting, there is no sign of it in the new one.
Based on the ReadMe file though, it sounds like the setting should be or was intended on being available: "An integer that indicates the amount of photos to be returned. If loadMore is set, the limit property will determine how many photos are loaded each time. (default: 10)."
Any help is appreciated. Cheers!

Ah, the docs need to be updated. Good catch, and sorry about that. The API only allows you to display a maximum of 20 pieces of media, so the loadMore option is now unfortunately obsolete. I will keep the limit option but I may need to update the plugin. Obviously it will only allow an integer from 1-20.


Intermittent empty fetch response

Bug report

[x ] I confirm this is a bug with Supabase, not with my own application.
[x ] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug
I have an expo app in which I have a lists of posts that you can click into. The list of posts works fine. However, when clicking into a post and I try to fetch an individual post, the first time will be successful, but each subsequent fetch will be unsuccessful, even when going back to the same post.
To Reproduce
import { PostgrestError, QueryData } from "@supabase/supabase-js";
import { supabase } from "../lib/supabase";
import { useEffect, useState } from "react";

const query = supabase.from("Post").select(`
  id,
  summary,
  date,
  Profile (
    id,
    name,
    Image (
      thumbnail,
      index
    )
  ),
  Image (
    full,
    thumbnail,
    index
  ),
  Like (profileId),
  Post (count)
`);

export type Post = QueryData<typeof query>[number];

export default function usePost(postId?: string) {
  const [post, setPost] = useState<Post | null>(null);
  const [loading, setLoading] = useState(true);
  const [error, setError] = useState<PostgrestError | null>(null);

  useEffect(() => {
    if (!postId) {
      return;
    }

    (async () => {
      console.log("FETCHING", postId);
      const { data, error, status } = await query.eq("id", postId).single();

      setLoading(false);

      if (error) {
        console.error("ERROR", error, "STATUS", status);
        setError(error);
        return;
      }

      console.log("POST:", data);
      setPost(data);
    })();
  }, [postId]);

  return { post, loading, error };
}

On initial fetch I receive the post as expected:
POST: {"Image": [], "Like": [], "Post": [{"count": 1}], "Profile": [{"Image": [Array], "id": "92afb876-133b-40bb-9bfc-a1a8146d6526", "name": "jonlaing"}], "date": "2024-04-18T01:06:08.018", "id": "d7ddb757-75de-4218-abb5-0b60b975cc3a", "summary": "Dhjjfgjbdd"}

But if I go back, and try again, I'll receive an error:
ERROR {"code": "PGRST116", "details": "The result contains 0 rows", "hint": null, "message": "JSON object requested, multiple (or no) rows returned"} STATUS 406

Expected behavior
I would expect the fetch to return a post given a valid id. I've checked and it is indeed using valid id's, as evidenced by it working the first time.
Screenshots
If applicable, add screenshots to help explain your problem.
System information

OS: Manjaro
Browser (if applies): Expo Go
Version of supabase-js: 2.42.0
Version of Node.js: 20.4.0

Additional context
I'm using expo-router and the page in question is named /posts/[id].tsx so I don't know if that's relevant. I have the app logging the postId, and it's correct every time, so I can't imagine there's an issue there, but I could be wrong.
Also, I used Prisma for all of my database creation and migration, so also not sure if that's relevant.
Thanks!

Okay, I just figured out what I did wrong. The query variable is instantiated at load time of the file, rather than at runtime of the useEffect, so it's essentially chaining the eq('id', postId) portion every time the useEffect runs, rather than building a new query each time. That's my bad. Closing the issue, but leaving this for posterity in case anyone else makes the silly mistake I did.


nixos/signald: automatically migrate db

Description of changes
Run --migrate-data on every start, so that the database migrations don’t need to be run manually.
I’ve been running this on my server for a while.

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Ups, didn’t want to delete the branch

Is this safe to use?

Yes.

Why doesn't signald does this by itself?

No idea. It should be quite easy to run migrations in code but for a reason I don’t understand, some applications don’t do this.


[Request]:  Get IP Address of Cellular network.

Plugin
connectivity_plus
Use case
Sometimes user may be connected to cellular network and we would require the ip address of the same.
Proposal
Now connectivity plus only gets the ip address of wifi network that you are connected, I propose that there should also be a way to get the ip address of the cellular network.

I need it, too.. Will it be possible?

Maybe this should be for network_info_plus rather than connectivity_plus

Duplicated of https://github.com/fluttercommunity/plus_plugins/issues/420


Redshift Update - init_copy

Independently check the 3 possible init_copy paths, allowing multiple of them to execute, if applicable.

Trying to familiarize myself with the RedShift code path in order to be able to better review, but this change LGTM :+1:


fix: add missing import statement, and correct controlled component s…

…tate tracking
Issue #, if available:
N/A
Description of changes:

Adding Missing import statement for state hook.
Use event input for controlled component onChange, rather than passing full payload back.
Move use*Action to managed imports, rather than just importing inline.
Remove erroneous properties declaration for datastore test cases (were being overwritten by a subsequent declaration.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report

Merging #374 (b98a8f4) into tagged-release/q1-release (c62df4d) will increase coverage by 0.05%.
The diff coverage is 92.59%.

@@                      Coverage Diff                      @@
##           tagged-release/q1-release     #374      +/-   ##
=============================================================
+ Coverage                      93.10%   93.16%   +0.05%
=============================================================
  Files                             40       40
  Lines                           1566     1579      +13
  Branches                         339      340       +1
=============================================================
+ Hits                            1458     1471      +13
  Misses                           106      106
  Partials                           2        2

Impacted Files
Coverage Δ

...s/codegen-ui-react/lib/react-component-renderer.ts
78.26% <33.33%> (ø)

...ges/codegen-ui-react/lib/imports/import-mapping.ts
100.00% <100.00%> (ø)

...eact/lib/react-component-with-children-renderer.ts
95.00% <100.00%> (ø)

...gen-ui-react/lib/react-studio-template-renderer.ts
91.27% <100.00%> (ø)

packages/codegen-ui-react/lib/workflow/action.ts
94.91% <100.00%> (ø)

packages/codegen-ui-react/lib/workflow/mutation.ts
91.93% <100.00%> (+1.02%)
:arrow_up:

Continue to review full report at Codecov.

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


image_picker crash app on selecting large mb file more than 550mb solve the issue 800mb not work

Steps to Reproduce

Run flutter create bug.
Update the files as follows: ...
...

Expected results:
Actual results:

Logs

@gadgetsteach
Provide a detailed description of the issue you are facing along with flutter doctor -v, pubspec.yaml and a minimal complete reproducbile code sample that shows the issue.

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


https://author-tools.ietf.org/ XML to TXT weirdness.

Describe the issue
Hi,
The https://author-tools.ietf.org/ XML to TXT seems wrong. It was working fine with the old experimental tool.
.
https://github.com/graf3net/draft-tgraf-opsawg-ipfix-srv6-srh/blob/main/draft-tgraf-opsawg-ipfix-srv6-srh-06.xml

https://github.com/graf3net/draft-tgraf-opsawg-ipfix-srv6-srh/blob/main/draft-tgraf-opsawg-ipfix-srv6-srh-06.txt

I re-generate the .txt file from https://author-tools.ietf.org/ and got the same weirdness.
Code of Conduct

[X] I agree to follow the IETF's Code of Conduct

This warning is broken and points to a bug (of omission) in xml2rfc:
draft-tgraf-opsawg-ipfix-srv6-srh/draft-tgraf-opsawg-ipfix-srv6-srh-06.xml(254): Warning: Deprecated  element removed, but no good conversion found  The output will most likely need fixup.
The good conversion is now available in the form of the <br element.

The other bug is the relocation of the text after the xref.

Finally, I see inconsistent handling of
    <references title="Normative References">
      <?rfc include='reference.RFC.2119'?>

This is handled correctly in --v2v3, but not in direct rendering to TXT:
 draft-tgraf-opsawg-ipfix-srv6-srh-06.xml: Line 502: Unable to resolve external request: "reference.RFC.2119"

Thanks. I was not too sure how to use , so I used  as mentioned in https://datatracker.ietf.org/doc/html/draft-hoffman-xml2rfc-23#section-2.56

    <t>Name: srhFlagsIPv6</t>
    <t>ElementID: TBD1</t>
    <t>Description: This Information Element identifies the
    8-bit flags defined in the SRH. Values for this Information Element
    are listed in the "IPFIX IPv6 SRH Flags" registry, see <xref
    target="IANA-IPFIX"/>. srhFlagsIPv6 values must not be directly added
    to this "IPFIX IPv6 SRH Flags" registry. They must instead be added to
    the "Segment Routing Header Flags" registry. Both the "IPFIX IPv6 SRH
    Flags" and the "Segment Routing Header Flags" registries must be kept
    in synch. Initial values in the registry are defined by the table
    below.

        <artwork><![CDATA[

+--------+-------------------+--------------------------------------+
| Value  |    Description    |              Reference               |
+--------+-------------------+--------------------------------------+
| 0-1    | Unassigned        |                                      |
+--------+-------------------+--------------------------------------+
| 2      | O-flag            |  [RFC-ietf-6man-spring-srv6-oam-13]  |
+--------+-------------------+--------------------------------------+
| 3-7    | Unassigned        |                                      |
+--------+-------------------+--------------------------------------+
  Table 2: "IPFIX IPv6 SRH Flags" registry

   ]]></artwork>

 <vspace blankLines="0"/> Abstract Data Type: unsigned8
    <vspace blankLines="0"/> Data Type Semantics: flags <vspace
    blankLines="0"/> Reference: [RFC-to-be], RFC8754</t>

The other bug is the relocation of the text after the xref.

Hi Cabo, Would you have a way to solve this one? Or we'll just post the XML, waiting for the bug to be fixed?

The other bug is the relocation of the text after the xref.

Hi Cabo, Would you have a way to solve this one? Or we'll just post the XML, waiting for the bug to be fixed in the .txt?

Actually, this one solves itself when using  all the way

    <t>Name: srhSegmentIPv6BasicList </t>
    <t>ElementID: TBD5</t>
    <t>Description: This Information Element
    identifies the Ordered basicList [RFC6313] of zero or more 128-bit
    IPv6 addresses in the SRH that represents the SRv6 segment list. As
    described in section 2 of <xref target="RFC8754"/>, theSegment List is
    encoded starting from the last segment of the SR Policy. That is, the
    first element of the Segment List (Segment List[0]) contains the last
    segment of the SR Policy, the second element contains the penultimate
    segment of the SR Policy, and so on.</t>
    <t>Abstract
    Data Type: basicList</t>
    <t>Data Type Semantics: list</t>
    <t>Reference: [RFC-to-be], RFC8754</t>

4.5.  srhSegmentIPv6BasicList
Name: srhSegmentIPv6BasicList
ElementID: TBD5
Description: This Information Element identifies the Ordered
basicList [RFC6313] of zero or more 128-bit IPv6 addresses in the SRH
that represents the SRv6 segment list.  As described in section 2 of
[RFC8754], theSegment List is encoded starting from the last segment
of the SR Policy.  That is, the first element of the Segment List
(Segment List[0]) contains the last segment of the SR Policy, the
second element contains the penultimate segment of the SR Policy, and
so on.
Abstract Data Type: basicList
Data Type Semantics: list
Reference: [RFC-to-be], RFC8754

For this type of list (definition list), RFCXMLv3 has direct support (dl definition list, dt definition term, dd definition definition):

Name:

srhSegmentIPv6BasicList

ElementID:

TBD5

Description:

This Information Element
    identifies the Ordered basicList [RFC6313] of zero or more 128-bit
    IPv6 addresses in the SRH that represents the SRv6 segment list. As
    described in section 2 of <xref target="RFC8754"/>, theSegment List is
    encoded starting from the last segment of the SR Policy. That is, the
    first element of the Segment List (Segment List[0]) contains the last
    segment of the SR Policy, the second element contains the penultimate
    segment of the SR Policy, and so on.

Abstract
    Data Type:

basicList

Data Type Semantics:

list

Reference:

[RFC-to-be], RFC8754

So that would be canonical XML for your use.


[Bug][Release] tar.gz tarball decompression error and some files are missing on Windows

To Reproduce

Go to https://dolphinscheduler.apache.org/en-us/download/download.html
Download tar.gz tarball
Decompress the tarball
See decompression error and some files are missing

Expected behavior
Bug fixed
Which version of Dolphin Scheduler:
-[1.3.x]
-[dev]
Additional context
Add any other context about the problem here.
Requirement or improvement

Please describe about your requirements or improvement suggestions.

https://www.apache.org/dyn/closer.lua/dolphinscheduler/1.3.6/apache-dolphinscheduler-1.3.6-src.tar.gz

https://www.apache.org/dyn/closer.lua/dolphinscheduler/1.3.4/apache-dolphinscheduler-incubating-1.3.4-dolphinscheduler-bin.tar.gz

While everything goes well in https://github.com/apache/dolphinscheduler/releases: https://github.com/apache/dolphinscheduler/archive/refs/tags/1.3.6.tar.gz

Considering that this is not an urgent question, we will release it in 1.3.8.


#68 shortcode prefilter registration

Codebase: https://projects.torchbox.com/projects/wordpress-to-wagtail-importer-package/tickets/68
This work includes the shortcode handler pre-filter when the import is run. It converts the [caption ... shortcode to wagtail_block_html tag. At this stage the new tag is not processed any further.
Added some extra documentation around Creating shortcode handlers

This looks good, Nick. Thanks.


HyperVClient is not reporting additional drives

HyperVClient.GetVmDrives() only returns the primary book drive, not any other attached drives.
We should fix this eventually, but it's not a big deal right now.

I'm going to close this for now and address this next time we touch/refactor the Hyper-V implementation.


ttf with cpp target is working

Hello,
NB: the reference i make to the the documentation is not the one on this website (which doesn't address the subject). It is the one in git tree: haxelib/heaps/git/doc/ref.html
So, the documentation says you cannot use TTF fonts with CPP target.

To instancied a h2d.Font we must have:
a bitmap and his font attached file (customFont.fnt) or a True Type font (exept in C++).

That said, the sample given in the source tree ( sample/2d ) seems to confirm that.
The ttf font loading is skipped if target is CPP :
    #if !cpp
    // load a true type font, can be not very high quality
    // la font se situe ici: ../Res/trueTypeFont.ttf
    // elle est chargée grâce à la classe res/FileTree.hx
		var font = hxd.Res.trueTypeFont.build(64);

    ( … )

    // set the text position
    tf.x = 20;
    tf.y = s2d.height - 80;
    #end

But reading the source of the res loader for TTF ( res/FileTree.hx )
 } else if( isJS || isCPP ) {
           switch( ext.toLowerCase() ) {
           case "ttf" if( isJS ):
                   Embed.doEmbedFont(name, fullPath, options.fontsChars);
                   embedTypes.push("hxd._res." + name);
                   return true;

i've believed that CPP was supported (i've just seen the if (isJS) conditionnal, when typing this bug report).
So, believing that, i've just commented the conditionnal in sample/2d ( the block « #if !cpp … #end » is now compiled inconditionally).
And when exporting to linux native, with CPP target, i've seen the TTF font appearing, just like in the JS target.
So, it seems you can use TTF fonts even in CPP targets (but i don't know where the support is in the sources).
I've did some searches with git history, but didn't find changes about this.
My question is: is it safe to think that TTF fonts can be used with CPP target ?
Thank you.
ps : i understand that it's not exactly a bug, so i'm bothered to write kind of things like these here. May be there is a better place to discuss those sort of things, so tell me please.

ping @kiroukou

Hello,
We do have TTF fonts working on native platforms using Lime.
So far, the official repo of lime seens dead, so you'll need our current fork here : https://github.com/motion-twin/lime/tree/mt_light   (light meaning we removed some features we do not need from lime).
I also have a pull request to make on heaps ir order to prived our latest improvements on native.  This should be done next week in the worst case , meanwhile you can check our fork here : https://github.com/motion-twin/heaps/tree/lime
++

@kiroukou @pperidont please submit some patches to sync with Heaps master.

I don't Have access To or anymore, so i let pperidont manage this.
Le 25 sept. 2016 14:55, "Nicolas Cannasse"<EMAIL_ADDRESS>a
écrit :

Closed #169 https://github.com/ncannasse/heaps/issues/169.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ncannasse/heaps/issues/169#event-801498251, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACxyqy0hWnxS77DTMuhBxfB_AevzYZvRks5qtm8ngaJpZM4IUoz-
.


feat: ibc migrations with no ICA

Description

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[ ] included the correct type prefix in the PR title
[ ] added ! to the type prefix if API or client breaking change
[ ] added appropriate labels to the PR
[ ] targeted the correct branch (see PR Targeting)
[ ] provided a link to the relevant issue or specification
[ ] added a changelog entry to CHANGELOG.md
[ ] included comments for documenting Go code
[ ] updated the relevant documentation or specification
[ ] reviewed "Files changed" and left comments if necessary
[ ] confirmed all CI checks have passed

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed all author checklist items have been addressed
[ ] reviewed state machine logic
[ ] reviewed API design and naming
[ ] reviewed documentation is accurate
[ ] reviewed tests and test coverage
[ ] manually tested (if applicable)

Codecov Report

Merging #1425 (96badd5) into main (421da96) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main    #1425   +/-   ##
=======================================
  Coverage   52.77%   52.78%
=======================================
  Files          71       71
  Lines        6759     6760    +1
=======================================
+ Hits         3567     3568    +1
  Misses       2922     2922
  Partials      270      270

Impacted Files
Coverage Δ

app/upgradev3/min_commission.go
85.71% <ø> (ø)

ante/ante.go
60.00% <100.00%> (+1.37%)
:arrow_up:

done in https://github.com/umee-network/umee/pull/1441


Need to be able to mitigate loss of projects in skillmap

Describe the bug
Skillmap doesn't have an easy way to save your progress in case the cache gets wiped (which it FREQUENTLY does in schools.)  The best we have right now is a download button to save an individual activity, but even that doesn't have an option to just save to the machine…and how would they continue with their skillmap progress by bringing that back up?
Skillmap has only been out a short while, but we're already getting messages like this:
"Others log into our class PCs, but when they log on the next day, their save information isn't stored in the browser like it's supposed to - it resets them. Any workaround for this? Today, I just had them click through the ones they had already completed to be able to get to the next parts in the skill maps."
If that happens to a classroom that worked hard for hours, it won't be long before they decide to look elsewhere for CS tutorials, and we may never get them back.
If we can't prevent it from happening, we at least need something they can proactively do to protect their work.

Closing this as this is addressed by identity work on saving skillmap progress.


Fix arkitscenes example failing to project boxes

That code should go away soon, but atm main is this clearly regressed due to the recent transform changes
Checklist

[x] I have read and agree to Contributor Guide and the Code of Conduct

PR Build Summary: https://build.rerun.io/pr/2248

actually, let's just do the right thing and use the experimental blueprint api to not need this projection!

properly fixed by #2351
blueprint for not needing this projection is coming soooon


[Feature]: Adapt trino for Streaming-Inline-Upsert

Description
No response
Use case/motivation
No response
Describe the solution
No response
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

Subtask of #256


Add descriptions for general_settings_ui_density_* strings

A translator asked for more context here: https://hosted.weblate.org/translate/tb-android/app-strings/en/?q=general_settings_ui_density_relaxed#comments

Note to self: Only merge after #7238 has been merged.


DynamicDependencies: Change IsElevated check from FAIL_FAST to RETURN(ErrorNotSupported)

https://task.ms/36535227
Change DynamicDependencies+Bootstrap is-elevated response from FailFast to ReturnError(NOT_SUPPORTED)
Added test case for Bootstrap API elevation invocation. Did NOT add a test case for DynamicDependencies elevation invocation as the tests aren't wired up to facilitate that (wrong process configurations). Doing this would require bigly-invasive restructurings so not justified; you can't get there w/o going thru the bootstrapper anyway so more theoretical than actual problem. Will consider in the future when more test work occurs.
Also:

Tweaked DevCheck.cmd powershell invocation to work regardless of machine config (i.e. like we do elsewhere)
Fixed file misname winrt_msixdynamicdepednency to the correct ...dependency (I keep transposing those 2 letters. My nemesis :-)
Fixed GetCurrentPackageInfoTests to run IsolationLevel=Class to avoid false errors due to process pollution if you run all DynDep tests in 1 pass. NOTE: IsolationLevel=Method would be too fine grained as the Setup fixture wouldn't happen in the right process context (plus test execution time would be greatly extended). No real need to go =Method and negative value so nah, =Class will do.

/azp run

/azp run

Thanks, a very welcome change. I've dove into the debugger multiple times already to debug a crash on startup, only to realize I was launching elevated.


Check for placeholder nodes in proof verification

Certain proofs (like those for a SMT) can contain empty nodes which are equal to the EmptyChild, but currently these will cause verification to fail for non-existence proofs if they appear where a real sibling node would be invalid, i.e. on a path that must be the leftmost or rightmost path of a subtree.
This adds a check to detect and ignore such nodes during verification of left- and rightmost paths. This will be needed in order to support SMT proofs in https://github.com/confio/ics23/pull/57.

Will add tests today, and port to the other languages. #57 is rebased on this, so this code is at least tested on those generated cases, but of course I'll add unit tests too, and maybe some proof tests.

Will add tests today, and port to the other languages. #57 is rebased on this, so this code is at least tested on those generated cases, but of course I'll add unit tests too, and maybe some proof tests.

Thank you

I've added unit tests and ported the code to Rust. I took a stab at adding the test data as JSON and deserializing in both languages, but I'm not sure how to cleanly match Go's base64 serialization in Rust, so for now, I've just hard coded and ported the test cases.
I also worked on porting the code to Typescript, but I'm not familiar with Node. I may need some help or extra time on that, or maybe it can be added in a separate PR.

We should update the JS / TS implementation as well.

I've added unit tests and ported the code to Rust. I took a stab at adding the test data as JSON and deserializing in both languages, but I'm not sure how to cleanly match Go's base64 serialization in Rust, so for now, I've just hard coded and ported the test cases.
I also worked on porting the code to Typescript, but I'm not familiar with Node. I may need some help or extra time on that, or maybe it can be added in a separate PR.

Thank you for taking that on. I will take a quick stab at this.

I was going to add a commit, then realized it was on a fork, and better just to merge this, then I can make a new branch

Thanks, I will push what I have for Typescript so far, it should be usable. I just didn't want to delay this while I study up on the node build system and testing.
Made a draft PR - https://github.com/confio/ics23/pull/62

Okay, this is blocking #57 right?
I am mostly back from holidays, I will take a look this week or early next week. Please ping me here

Alright, I think the Go and Rust work on this is complete. @ethanfrey could you review again, and if it looks good let's move on to the TS port.

Please review my comments. I made my suggested fixes to the Go side and it works. Or at least seems like it works for me.
There is some broken test in vectors as some previously invalid proof becomes valid... it would be good to investigate, but not critical - I think that setup is a bit artificial anyway.
Can you fix up the Rust side to match the Go side? Then we can merge this (comment out the vector test if you don't see what changed).
As a followup PR, IsLeftNeighbor also needs to be aware of such EmptyChild.
I assume you have 16-wide innernodes for the SMT, so we may very well set idx3 and idx6 but 4 and 5 are empty and yet those paths are adjacent. The current code works where spec.ChildSize == 2 but not for all cases when it is larger.

Thanks for the fix, and for straightening me out here! I think I got confused by how InnerOp describes the sibling nodes of a branch, and starting reversing indices in a misguided workaround for my confusion.
Let me finish the fixes and send it back to you tomorrow.
btw. We have a 2-wide inner node in this SMT implementation, but it would be interesting to test 3, 4, and 16, and I could look into that later.

Okay, with this fix, this is correct for 2-wide.
We can make another PR later to ensure it works for 16-wide (needed for parity/substrate inter work) @seunlanlege

Ready for another look now. I will try to start on the neighbor check fix and wider node support soon, could be interesting.

Ready for another look now. I will try to start on the neighbor check fix and wider node support soon, could be interesting.

Yeah, let's do that in another PR.
I'd be happy to get this in soon, and https://github.com/confio/ics23/pull/57 for full Go support to validate SMT proofs, which I could get into IBC Go v3 hopefully.
I will follow up on https://github.com/confio/ics23/pull/62 but that is less critical as it requires a client sided update not a blockchain update (which takes longer to roll out)

We can argue of the semantics of all on an empty set, but it's a valid placeholder on a leftmost path signals to me that we are looking for leftmost non-empty, which is true here

Right, this function should be defined for ops that describe branches with valid left siblings (empty or not), and checks if those siblings are empty. An op that describe a leftmost branch has no left siblings, so it shouldn't be valid input anyway IMO. I will defer to you on the final behavior - if we go with true, I will look at why it breaks that vector test case.
I wonder if leftSiblingsAreEmpty might reflect the meaning more clearly?

if we go with true, I will look at why it breaks that vector test case.

Returning false here fixes the vector test case? Weird. But a good hint.
I am off next two days, can look towards the end of the week

@ethanfrey hey, do you expect to be able to review this week?


Missing "dso" and "packages" subfolders

I went to install v2.0.0+b6-hdn19-5-640.prt3-0-8905.win10-vc1427-x86_64-rel-opt, and the documentation says to extract it into documents/Houdini19.5 so the folders end up in the corresponding config, dso and packages subfolders, but my documents folder only has the config subfolder. Is there another directory somewhere else, something wrong with my houdini installation or some other problem?

Hi,
it is ok if the dso/packages folder do not exist yet, just copy the contents of the palladio archive in there which will create dso/packages and merge into config.
Best,
Simon


Installation steps update

Installation steps update for ubuntu

[ ] Bug Report

Problem:
The current steps mentioned result into build and execution errors due to dependencies.
Proposed Solution:
sudo apt-get install software-properties-common
sudo apt-add-repository ppa:brightbox/ruby-ng
sudo apt-get update
sudo apt-get install ruby2.2
sudo apt-get install ruby2.2-dev
sudo gem install github-pages
sudo gem install jekyll bundler
sudo bundle install
Page to Update:
https://github.com/thingsboard/thingsboard.github.io

Hi! Do you want to submit PR with this change? Also what OS/version you are using?

I am using Ubuntu 17.04. This is documentation update. I haven't tried submitting PR but if required, I can give it a try. Is there any recommended process for submitting PRs?

@ssmaurya no specific steps, just see old PRs for the reference. All you need to do is sign the CLA once the PR is submitted

I have updated the doc.


plot updates

would be nice to have a way to refresh plots in the editor so that when changes are made on Plotly they could easily be reflected back in the editor.

Couple ways to force this. Clicking on another slide then back to the slide with the plot should refresh the plot. Resubmitting the embed url in the plot menu should also cause a refresh.


Cleanup TestCommon

Fixes https://github.com/aspnet/Mvc/issues/4627

@pranavkm the integration test project fails to build because TestModelMetadataProvider can't be found. Is this just a missing using?

Might have deleted too many things accidentally. I'll fix it up

🆙 📅


Fixup tests of Store transform

This clearly shows that Store can fill the .grad field of a tensor that doesn't require grad.
I think this is unintended and that we should fix this (regardless of #89).

Well no need to fix it if we do #89 , so it is probably worth thinking about #89 before doing anything.

Well no need to fix it if we do #89 , so it is probably worth thinking about #89 before doing anything. I don't like your fix, I would raise and exception if it does not require grad.

Yeah, don't we want an exception in this case?


Consider generating mocks for types outside solution

There are times when it is useful to be able to have mocks for third party interfaces. The code generator does not currently provide a means of doing so. Perhaps it could also traverse third party assemblies and feed them into the generation pipeline.

On further thought, I don't think this makes sense. It would require Roslyn be able to disassemble an assembly into a Compilation, which I'm fairly certain is outside the scope of Roslyn.
Closing this for now because it wouldn't be overly useful anyway. There are only maybe 2 or 3 third party interfaces that I regularly require mocks for.


perf(Picky): 50% performance improvement

All Option components were re-rendering on a change. Used recompose/onlyUpdateForKeys to help with that.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add support for type precedence hints (#3860)

Pull request opened by the merge tool on behalf of #3860

Merged into branches iso5 in 0bd82fbeca6b659202d776b740c25d3c2826f268


Invalid email Sailthru_Client_Exception error code doesn't match

I'm getting a code 99 for the "Invalid email: {EMAIL}" error, but the documentation and error code const (https://github.com/sailthru/sailthru-php5-client/blob/master/sailthru/Sailthru_Client_Exception.php#L11) say it should be 11.

Yup, getting 11 now. You might want to update the Notes line for error code 11 to say "Email is invalid or banned".
Thanks!


Refactoring to convert to "named parameters"

It would look something like this

CC @rauschma @appsforartists in case you want to 👍

Apologies for being ungrateful: this doesn’t reflect how I use this pattern – I don’t see the parameters as a whole, I see each parameter individually. As a work-around, I inline the type and don’t define it externally.
Let me try, one last time, to convince you of the usefulness of a better notation for destructuring (nested destructuring will profit, too!). The following is an extreme example, but there are many similar functions in my code:
function slidesToNodeTree(
  {conf, configShowoff, inputDir, slideDeckDir, slideFileName, parentPartNode, visitedSlideFiles}
  : {conf: ConfigSlideLink, configShowoff: ConfigShowoff, inputDir: string,
    slideDeckDir: ServePath, slideFileName: string, parentPartNode: PartNode,
    visitedSlideFiles: SlideFileDesc[]}) {
  ···
}

With a better notation:
function slidesToNodeTree(
  { conf as ConfigSlideLink, configShowoff as ConfigShowoff, inputDir as string,
    slideDeckDir as ServePath, slideFileName as string, parentPartNode as PartNode,
    visitedSlideFiles as SlideFileDesc[]}) {
  ···
}

Alternatively:
function slidesToNodeTree(
  { (conf: ConfigSlideLink), (configShowoff: ConfigShowoff), (inputDir: string),
    (slideDeckDir: ServePath), (slideFileName: string), (parentPartNode: PartNode),
    (visitedSlideFiles: SlideFileDesc[])}) {
  ···
}

Note how, in the last two examples, you actually see parameters with names (vs. a single type for all parameters). The first example looks messy, the last two examples don’t.
If you have ever used a programming language with named parameters and liked them there – isn’t this a compelling use case? Given the thumbs-up at a recent comment of mine, there are quite a few people who agree.
This is the only aspect of my plain JavaScript code that became less usable after I moved to TypeScript.

I love that you're exploring this, but I agree with @rauschma.
I think there's a bit of a cargo-cult bias in the TS community to always prefer interfaces (because they can be extended).  Type literals seem like a more appropriate model for the kwargs pattern, because they allow users to treat each named argument individually.
If a third party made a "convert to named arguments" command, I would probably find it useful to be able to write function signatures normally and then convert them to an interface/type literal.  However, I'd rather the language supported setting the type for a named arg adjacent to the declaration of its name and default value.  It's both hard to read and cumbersome to maintain when the types are separated from the rest of the definition.

This refactor also must refactor all references to the method in the whole project right ? But a very helpful refactor , in my experience, happened many times when an API signature that needs to be backwards compatible, is defined with multiple params and then you keep adding parameters to implement new features or even change parameter type to OR, like existing: PreviousType|NewSemanticType....

This refactor also must refactor all references to the method in the whole project right ?

IMO, it should

This is great!
Have you thought about the default arguments with no types? Would you infer types there?
function foo(a = 1, b?: string)

Also would it work in constructor function with private or public keyword? I think it won't, right?
class Foo {
  constructor(private a: string) {}
}

where would you generate a type name if function is anonymous?
function (a = 1, b?: string){}.call(1)

This would be super helpful to me, even if others would rather a new destructuring syntax for function parameters.
So, if the proposed refactoring somehow loses favour over new destructuring syntax, I would still like for this particular one to be implemented.
I personally use interfaces instead of inlining, especially for large projects. And projects I write that get consumed by others.
I've had to wrap a function many times. And if the library doesn't have those function arguments as an interface, then I have to copy-paste code instead of just using an interface that should already be there.
People like to think of interfaces as being "code duplication". But in the big picture, not having those interfaces causes code duplication.

✨ 🚲 🏠 ✨
Naming poll! Vote:

🎉 "Convert to named parameters"
❤ "Convert to parameters object"
👎 Other (specify)

I call them named parameters, but just throwing another idea out there: "convert parameters to destructed object"

I wish we wouldn't encourage the pattern of making functions take a single object - it thwarts currying.

I know @rauschma said he'd stop and seems to have kept his word, but he's absolutely right that doesn't express what people want to express.
Have people discussed using is yet? Example from the top using this syntax follows:
function foo({a is number, b is string, c? is boolean}): void {
  a; b; c
}

And the TypeScript code base itself is chock full of long lists of parameters with optionals etc. Empirical evidence for where this could help.

Have people discussed using is yet? Example from the top using this syntax follows:
function foo({a is number, b is string, c? is boolean}): void {
  a; b; c
}

There were some discussions about as in an earlier issue -- mostly involving concerns about introducing a new keyword in a very specific context. I suspect is would have the same complaints.
I haven't thought through every issue, but I'm wondering about using : twice, where the renamed variable name can be optional. So instead of [object_key]: [variable_name] = [default_value] you end up with [object_key]: [variable_name]: [type] = [default_value]. This kind of makes sense since you're typing the variable name, rather than the object key, anyway.
So the most verbose version of this would be:
function someFunc({ foo: bar: string = 'default' }): void {
  bar;
}

... whereas the common case would be:
function someFunc({ foo:: string }): void {
  foo;
}

I wish we wouldn't encourage the pattern of making functions take a single object - it thwarts currying.

There are cases where it is beneficial to take a single object with many parameters.
For example, that object can be an immutable data structure and the function is just performing some operation on it and returning a new instance of the data structure.
In some cases, those data structures can have dozens of properties... You're not really suggesting we curry in those cases as well, right?

@DanielRosenwasser what's the reason this was closed?
I was looking for this feature earlier and came across this issue.

@jasonwilliams it was closed because it was implemented

I love this refactoring, but is there a a reason why it does not work on constructors?
I sometimes find myself creating a class where the number of constructor parameters grows out of control, with too many optional ones and I wished that I had instead made one "config" or "options" interface that can be passed in to the constructor.   The advantages being:

the constructor calls would be clearer, with objects passed in which explicitly have {key:value, key:value} rather than just a bunch of unnamed values passed in as constructor parameters, and
it makes it easier/cleaner to deal with a lot of optional parameters, since they can simply be omitted from the configuration object instead of all of the constructor parameters needing to be passed in the correct order (avoiding the awkward situation where you need to pass a dummy value to the 4th optional parameter so that you can a desired value to a 5th optional parameter)

I notice that @mohsen1 asked about using it on constructors earlier in this thread and @DanielRosenwasser  kiboshed the idea unceremoniously (simply saying "It probably should not for now.").  Maybe that's just because it was early on in the development of this refactoring and you all were trying to keep things as simple as possible?   What extra complications do using this for constructors create that aren't present for functions?
Since this issue is old and closed should I open a new issue called "Make 'Convert parameters to destructured object' refactoring work for constructors"?

Yes, please open a new issue. Thanks!

If anyone tried this and wonder why it doesn't work, it might be because you are selecting multiple lines.
Placing the cursor on just one parameter in a function and then opening the refactor menu should do it.


Allow Sorting across LinkingObjects Relationships

Problem
Consider this relationship:
final class Parent: Object
{
    @Persisted var name: String
    @Persisted var kids: List<Child>
}

final class Child: Object
{
    // There should only ever be one parent, but Realm does not provide singular LinkingObjects
    @Persisted var parents: LinkingObjects<Parent> = LinkingObjects(fromType: Parent.self, property: "kids")
    var parent: Parent? {
        return parents.first
    }
}

Now suppose I query a bunch of Child objects into a Results<Child>. I want to sort them by parent.name. This is not possible.
If you try to use the computed property parent in a SortDescriptor, you get an error that "parent does not exist". If you try to do parents.first.name, you get an error "Cannot sort on key path 'parents.first.name': property 'Child.parents' is of unsupported type 'linking objects'."
The only way to solve the problem is to abandon Realm, copy the objects to an Array and sort them. But then you lose the auto-updating nature of Results<T>.
Solution
Sorting should be allowed through computed properties and/or through LinkingObjects so that an entity can be sorted by a property of its parent.
This is not some edge-case functionality. It's really common. To use the standard Realm example, suppose you're displaying an NSTableView of Dog objects. One column in the table is "Owner's Name". You want to sort the Dogs by their Owner's name. You currently cannot accomplish that very simple task without either (1) ditching Realm collections as the datasource for the table or (2) bludgeoning the data model in the face with needless, duplicated properties that you must store and then keep in sync JUST to support sorting (for example, the Child object could have a string property called parentName that we must then keep in sync when the parent's property changes.)
How important is this improvement for you?
Would be a major improvement

Hi @bdkjones This is a feature we would like to implement, but as of now I cannot give a timeline. In the meantime a workaround would be to place an object link to the parent in the child like so:
final class Child: Object
{
    @Persisted var name: String
    @Persisted var parent: Parent?
}

This is going to require some careful memory management when the objects are first being created an in memory. But once they are retrieved from the Realm you will not get a retain cycle as the object accessors are lazily instantiated.

Was there an update on the timeline for this? It's been 2.5 years.

No. When we have an update, we'll share it in the issue.

Hello, any update on this subject ?
I face the same issue and transforming Results to anArray to sort myself the data leads me to major issues like crashes like 'Object has been deleted or invalidated.' when I delete data of a @Published Array because ForEach will look into the Identifier of my Realm model that has been invalidated.
Even if I carefully delete the element of my array before removing it from the database, the async behaviour of Publish will delete the object before the UI updated.


Check that object is not a Date object before building connect variables

Using DateTimeInput in react-admin cause the input data to be a Date object. Without additional checks for this, it was interpreted as an object that needed connect. This failed, and the operation as a whole failed.

I stumble on an error fail isObject_2 is not a function on a ReferenceArrayInput on v0.0.7. Since this Pr was the only change, i think it might come from this.
@larsivi did you encounter it ?
I'll look into it

my bad, i didn't saw your second PR a few weeks ago, thank you !


[20.09] dnsmasq: 2.82 -> 2.83

Motivation for this change
Backport of #109968
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

@NixOS/backports Would be nice if you could take a look, as this is a somewhat serious security fix.

@NixOS/backports Would be nice if you could take a look, as this is a somewhat serious security fix.

I'm going to forgo batching this, since there is nothing else ready right now.

I'm going to forgo batching this, since there is nothing else ready right now.


DASH parser sometimes uses MPD-level BaseURL over Period-level BaseURL

Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?
v3.0.0 and master
Can you reproduce the issue with our latest release version?
yes
Can you reproduce the issue with the latest code from master?
yes
Are you using the demo app or your own custom app?
demo
What browser and OS are you using?
ChromeOS stable 83
What are the manifest and license server URIs?
Sent privately as part of issue #2620
What did you do?
Try to play the content in v3.0
What did you expect to happen?
It should play, as it does in v2.5.13
What actually happened?
The URLs seem to be incorrect.  Analysis of the manifest shows that there is a BaseURL at the MPD level and another inside each Period element.  For some reason, the constructed segment URLs are using the wrong BaseURL.
Stranger still, I am unable to reproduce this behavior in a simple unit test which has the same MPD structure.

The behavior is specific to SegmentTemplate+SegmentTimeline, and for simplicity, I had written a test using SegmentTemplate+duration.  I can now reproduce the behavior outside of the content from #2620.  It seems to be a bug in DashParser, not PeriodCombiner, though it was introduced in the refactoring that led up to PeriodCombiner's introduction.


feat(chart): add aws-specific idle timeout annotation to router service

Ref https://github.com/deis/router/issues/326

Codecov Report

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

@@           Coverage Diff           @@
##           master     #327   +/-   ##
=======================================
  Coverage   55.69%   55.69%
=======================================
  Files           6        6
  Lines         386      386
=======================================
  Hits          215      215
  Misses        151      151
  Partials       20       20

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 f81d872...3dd0d3e. Read the comment docs.

For anyone who may have this concern, please note that this AWS-annotation will not have any adverse effect when this chart is installed elsewhere.

:shipit: ?


Undefined in transclusion URL

On the web gateway when a transclusion is made, the url includes undefined in the block part of the url

I think this is fixed now. Let me know if this happens on new versions of the gateway


Puppeteer.launch

Launching puppeteer. I am passing options from another file. The options for ‘headless:’ are a lodash index of(process.argv, ‘—headless-browser’) I would like to make headless false using this format. I have args and a time-out 2000. It keeps timing out.

Please file bugs using our included issue template.


Additionally, its current behavior is to checkout the commit hash that originally triggered the GH workflow to run (https://github.com/actions/checkout/issues/439).
This becomes undesired behavior in the case that the version stage runs successfully and pushes a version bump commit, but the publish stage fails. After fixing the node-versioner library you'd want to rerun the workflow and have it pull down the latest commit of the branch it ran on. Instead, it will pull down an old commit hash, the version stage will try to push a new version bump commit, and fail because it conflicts with an existing commit.
To work around this, zowe-deploy-test currently runs this command after @actions/checkout:
    - run: git pull --no-rebase --no-tags
https://github.com/t1m0thyj/zowe-deploy-test/blob/b7d4b770d71ae35ee21862a83ad4c69ba1bea641/.github/workflows/zowe-cli.yml#L60
Perhaps there is a better solution? If not, we'll need to document this behavior.

The required configuration to support reruns is documented here:

To allow the workflow to be rerun after changes have been pushed, add this input to @actions/checkout:ref: ${{ github.ref }}


All floats are written as 64bit

https://github.com/ihedvall/mdflib/blob/16b8f111ee66388ed741687445674cdefc92a932/mdflib/src/cn4block.cpp#L1012
the code compares the given byte size against bit sizes, resulting in the cases never matching and defaulting to 64bit.

Thanks for finding the bug. I will correct the code ASAP.

Fixed the bug so 4 and 8 bytes floats are supported. 2 bytes float are supported for reading but not for writing.


Bounding box orientation incorrect on custom nuscenes formatted dataset

Hi,
We've been using mmdetection3d to train a custom dataset that we've created that is in the nuscenes format, using our own classes and data. We can render the ground truth annotations using the nuscenes devkit, with nuscenes.render_sample_data(), and this visualisation is correct.

We altered nuscenes_converter.py to work with our dataset. As there were several instances of things being hard coded to work specifically with the nuscenes dataset, we had to change several things to get the converter working with our dataset.
We can use an altered version of browse_datasets.py to visualise the ground truth annotations after the conversion. When we visualise these, the translation is correct, but the orientation of the box is incorrect. Since translation appears perfectly, this leads me to think that there is no issue with the ego or sensor rotation and that it's a problem with only the annotation orientation. We can also train on the dataset and get a high mAP, but the predictions, as expected, have the same orientation as the ground truth data when visualised using mono_det_demo.py

After spending a lot of time attempting to understand where this rotation issue is coming from, we're at a loss. Hopefully someone could offer some help with this issue. @ZwwWayne I see that you've done this PR which seems quite relevant to what we've been working on. Perhaps you have an idea of what is going on?
I have packaged a dataset with a few images, and the conversion and visualisation scripts we've been using.
mmdetection3d.zip
If someone gets the time to help us out with this, it would be very appreciated.
If you want to run the conversion and visualisation scripts, build and run the docker container using the latest repo, and use the data folder in the attached zip as the DATA_DIR in docker run --gpus all --shm-size=8g -it -v {DATA_DIR}:/mmdetection3d/data mmdetection3d. Then place the scoville folder from the attached zip in /mmdetection/ in the docker instance. Dataset conversion and visualisation can then be done using the following commands:

python scoville/pencil_nuscenes_converter.py data/nuscenes_pencil_example/ data/nuscenes_pencil_example/
python scoville/browse_dataset_pencil.py scoville/pencil_finetune.py --output-dir visualisations --task mono-det

Aha, I didn't realise this (I assumed incorrectly aligned boxes would produce poor mAP, similar to the 2D case with a low IoU threshold).
img_bbox_NuScenes/pencil_AP_dist_0.5: 0.8536, img_bbox_NuScenes/pencil_AP_dist_1.0: 0.8536, img_bbox_NuScenes/pencil_AP_dist_2.0: 0.8536, img_bbox_NuScenes/pencil_AP_dist_4.0: 0.8536, img_bbox_NuScenes/pencil_trans_err: 0.1198, img_bbox_NuScenes/pencil_scale_err: 0.9782, img_bbox_NuScenes/pencil_orient_err: 2.0613, img_bbox_NuScenes/pencil_vel_err: 1.0000, img_bbox_NuScenes/pencil_attr_err: 1.0000, img_bbox_NuScenes/mATE: 0.1198, img_bbox_NuScenes/mASE: 0.9782, img_bbox_NuScenes/mAOE: 2.0613, img_bbox_NuScenes/mAVE: 1.0000, img_bbox_NuScenes/mAAE: 1.0000, img_bbox_NuScenes/NDS: 0.5170, img_bbox_NuScenes/mAP: 0.8536

I am not too familiar with this metric: img_bbox_NuScenes/mAOE: 2.0613 but if I understand correctly it would suggest that the orientation is on average about 2 radians (118 degrees) out?
If so that helps us a lot, it would guess that it suggests that the visualization is not the issue after all, but in fact there is something wrong the with the orientation of ground truth data being fed in mmdet library such that the model is learning to provide inappropriate orientation.
The mystery still remains though as to why we can visualise the raw nuscenes ground data fine with the NuScenes visualiser. It would suggest there is a bug somewhere in our nuscenes converter I think - can you spot anything that looks suspicious?

Tried rewriting our converter using the latest version as a starting point, but ended with the same issue :( Sadly we might have to abandon this unless anyone has any further ideas on how we could debug.

Is there any solution for this? I am facing exactly same issue. When my yaw angle is zero, it works fine but if there is yaw angle, the visualization goes for toss as showed above. Would be great help if there is some solution for this. Thanks!

FYI, I fixed this issue. I have taken yaw = -yaw While converting from json files to .pkl  file, when i took yaw without any changes, the GTs are getting drawn as expected.  So this is basically a change in my converting script, but predictions are in wrong orientation while running inference as i have raised the same in https://github.com/open-mmlab/mmdetection3d/issues/1287.

In my case, predictions are wrong becuase my training set samples are wrong.


Update save_estimated_reference.py

In case of camera rotation covariance should use localframe according to ypr (ecef_crs.localframe) or opk (crs.localframe) to reflect different angle references.......
By the way could you explain the math behind the use of dmat2euler utility?

Thanks, again :)
The dmat2euler method calculates the Euler angle difference that will cause specified infinitesimal change in rotation matrix coefficients (dR).
For example, for YPR angles:
yaw       = atan2(-R(0, 1), R(1, 1))
pitch     = asin(R(2, 1))
roll        = atan2(-R(2, 0), R(2, 2))
So for YPR angle convention dmat2euler performs the following calculation:
dyaw     = (dR(0, 1) * R(1, 1) - dR(1, 1) * R(0, 1)) / (R(0, 1) * R(0, 1) + R(1, 1) * R(1, 1))
dpitch   = dR(2, 1) / sqrt(1.0 - R(2, 1) * R(2, 1))
droll      = (dR(2, 2) * R(2, 0) - dR(2, 0) * R(2, 2)) / (R(2, 0) * R(2, 0) + R(2, 2) * R(2, 2))
dyaw     *= 180.0 / math.pi
dpitch   *= 180.0 / math.pi
droll      *= 180.0 / math.pi
The resulting values are in degrees.


azblob: Return io.ErrUnexpectedEOF as error in UploadStream

Fixes #21837

[x] The purpose of this PR is explained in this or a referenced issue.
[x] The PR does not update generated files.

These files are managed by the codegen framework at Azure/autorest.go.

[x] Tests are included and/or updated for code changes.
[x] Updates to module CHANGELOG.md are included.
[x] MIT license headers are included in each file.

/azp run go - azblob


Create setup folder

I think it's a very good idea, but the template folder would also have to be moved there for it to work, so I don't know if it wouldn't be better to make the src folder and put the setup files and pinkcord code there

I create a scr folder soon

I can do it when I get home in half an hour

okay i actually have to go home too

I think I'll be home in 45 minutes


fix Fix bug in follow cooldowned data

Proposed changes
#32798
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Customising the snackbar persist duration

Currently, there doesn't seem to be a way to customise the duration of how long the snackbar would persist on the screen before it gets dismissed automatically.
The duration parameter is used for how long the animation would take.
I don't want to persist the snackbar for eternity but would like it to get dismissed after like 5 seconds automatically. Is there a way to control that?

I am planning to release advanced package of this package so will this feature in it.
I will update here once it is available in pub.dev


WIP: Mono support

These changes are based closely on the work by @4garbage in #788
I'm structuring the PR as a series of incremental commits in order to make the changes easy to follow and check.

This is now ready for review. I have manually verified that I can run a simple test program that uses Confluent.Kafka.Producer on linux with mono in the official mono <IP_ADDRESS> docker image (and that I can't without this change). Setting up testing for this would be much more work than actually making the change, and not of commensurate value, so I suggest not doing that, at least until we have a more general automated test framework set up for many environments.
This change is conceptually very simple - before, in the .NET Framework case, we never tried to load librdkafka unless on windows. Now we do (which is the problem mono is solving for). In order to realize this, a bit of a refactor was necessary resulting in a difficult to follow diff. To make that easier to follow i did the change as a series of focussed commits.
The main thing to check for is that I didn't screw up existing scenarios (I don't think so).
I followed what @4garbage did closely, and I thought about it from scratch, so a review of this is effectively a 3rd check.

merging since we won't claim support for mono. if we do start claiming this, I can add CI tests then.


The npm package does not have compiled .js files

The example in README.md does not work:
$ npm install structured-headers

+<EMAIL_ADDRESS>added 1 package from 1 contributor and audited 1 package in 1.869s
found 0 vulnerabilities

$ node
> const sh = require('structured-headers');
Thrown:
{ Error: Cannot find module 'structured-headers'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    at Module.require (internal/modules/cjs/loader.js:692:17)
    at require (internal/modules/cjs/helpers.js:25:18) code: 'MODULE_NOT_FOUND' }

It looks the npm package does not have dist/ and browser/ directories, probably because these are listed in .gitignore and there's no .npmignore file.
Also, "main": "index.js" in package.json should be "main": "dist/index.js".

related:
> const sh = require('structured-headers');
Uncaught:
Error: Cannot find module '/home/liminal18/Programs/nodeJS/digital_bazaar/http-signature-header/node_modules/structured-headers/index.js'. Please verify that the package.json has a valid "main" entry
    at tryPackage (internal/modules/cjs/loader.js:303:19)
    at Function.Module._findPath (internal/modules/cjs/loader.js:516:18)
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:867:27)
    at Function.Module._load (internal/modules/cjs/loader.js:725:27)
    at Module.require (internal/modules/cjs/loader.js:952:19)
    at require (internal/modules/cjs/helpers.js:88:18) {
  code: 'MODULE_NOT_FOUND',
  path: '/home/liminal18/Programs/nodeJS/digital_bazaar/http-signature-header/node_modules/structured-headers/package.json',
  requestPath: 'structured-headers'
}
> .exit

[liminal18@nixos:~/Programs/nodeJS/digital_bazaar/http-signature-header]$ ls node_modules/structured-headers/
changelog.md  Makefile  package.json  readme.md  src  test  tsconfig.json  tslint.json  webpack.config.js

Given that it's a typescript package, I believe this import style should work in javascript:
const sh = require('structured-headers');

If that fails, i'll dig a bit deeper. This package needs some work to be back up to date with the current standard though, it's been a bit hard to find time =(

If there is interest in adopting this, I can spend some time fully bringing this up to par with the latest standards. Something I planned to do anyway, but I can potentially prioritize this

As the Signing HTTP Headers specification now uses structured fields it might be a good idea. The spec that brought me here. I tried your import method:
const sh = require('structured-headers').default;
Uncaught:
Error: Cannot find module '/home/liminal18/Programs/nodeJS/digital_bazaar/http-signature-header/node_modules/structured-headers/index.js'. Please verify that the package.json has a valid "main" entry
    at tryPackage (internal/modules/cjs/loader.js:303:19)
    at Function.Module._findPath (internal/modules/cjs/loader.js:516:18)
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:867:27)
    at Function.Module._load (internal/modules/cjs/loader.js:725:27)
    at Module.require (internal/modules/cjs/loader.js:952:19)
    at require (internal/modules/cjs/helpers.js:88:18) {
  code: 'MODULE_NOT_FOUND',
  path: '/home/liminal18/Programs/nodeJS/digital_bazaar/http-signature-header/node_modules/structured-headers/package.json',
  requestPath: 'structured-headers'
}

still doesn't work. The issue I'm running into is that HTTP signatures are both front end and back end and the other structured fields library uses the node only Buffer class which requires a 200kb polyfill. So there doesn't seem to be a good cross environment structured fields library surprisingly.

This library was several drafts behind, and instead of trying to get it up to date with the current RFC, I rewrote it yesterday.
The new parser passes all official tests, but the serializer is not done yet.
I've kept the 'No buffer' requirement in mind, so the eventual release will use ArrayBuffer instead, which is available in browsers.
If this can wait a few more days, I can have a fully functioning npm package ready to go.


How do I install WordPress?

Hello to everyone.
I want to install WordPress inside the app directory. But mySQL does not accept the information. Can you help with this?

Which connection settings have you tried?
Hostname: mysql
User: root (or dev)
Password: dev
Database: database

Hi @mblaschke,
Thank u for responsive my issue.
Yes, it worked when I wrote mysql. This is definitely my mistake. I wrote "hostname: localhost". So where do I change the "mysql" name there?

The name mysql is coming from the name of the mysql container. If you change the name inside the docker-compose.yml file the hostname of the container will also be changed.
Each container is an own server environment (sandboxed) with it's own ip address.
And that's why you should use the hostname mysql for connecting to the mysql database which runs in a container :)

Yes I understood. I have one more question. Do I also need to type "links: -phpmyadmin" in the "docker-compose.yml" file? So, the code below is correct?
version: '2'
services:
  #######################################
  # PHP application Docker container
  #######################################
  app:
    build:
      context: .
      dockerfile: Dockerfile.development
    links:
       - mysql
       - phpmyadmin
    ports:
      - "8000:80"
      - "8443:443"
      - "10022:22"
    volumes:
      - ./app/:/app/
      - ./:/docker/
    # cap and privileged needed for slowlog
    cap_add:
      - SYS_PTRACE
    privileged: true
    env_file:
      - etc/environment.yml
      - etc/environment.development.yml
    environment:
      - VIRTUAL_HOST=.app.boilerplate.docker
      - VIRTUAL_PORT=80
      - POSTFIX_RELAYHOST=[mail]:1025

The links are the network links so that these the app container can discover the mysql container using the hostname mysql. Same for phpmyadmin and all other containers.
These containers are linked together.
The app container doesn't connect to phpmyadmin but phpmyadmin connects to mysql.

You are awesome. Thank you for everything. Best regards.


chore: add a matrix to lint, dont lint on other jobs

@zackarychapple please take a look.

LGTM

LGTM


Add varags for tab -w

I'm not implementing autocomplete support in this PR.  After looking at fish and zsh docs, dynamic completion for variadic arguments is not a well supported feature.


Group by directory/project for monorepos

First of all thanks for working on this!
We just installed it on our dual language monorepo (Haskell & Typescript) and the report is a bit hard to read since all projects are included in one giant list.
Some ideas that would help us out in this situation

Would be great if we could group the report somehow. For example if multiple directories are detected, then use directory names to group? We can also configure these in the config file too, if that's easier.
Maybe add a third icon that links to the offending dependency file?

Example showing a mix of JS and Haskell libs

Thanks for the feedback!
I think this is a good call, it isn't immediately clear which language or file each package corresponds to, which makes the report harder to visually interpret.
My initial inclination is to start with breaking down each section of Unhealthy, Healthy With Warnings and Healthy down by language headings. This is probably a good low hanging fruit starting point at least. What do you think?
Breaking down by file is interesting, because the same dependency may exist in multiple files (or multiple times in a single file). As such after loading all the dependencies, Deadpendency will deduplicate to get the final list to be checked.
So to include the file information, you would either break down the report by dependency file name and multiple files may have the same dependency report. Or, you would break down by language, but each dependency would link to 1 to many dependency files that included that dependency. I think I prefer the latter as it avoids duplication to keep the report smaller. Any thoughts?

My initial inclination is to start with breaking down each section of Unhealthy, Healthy With Warnings and Healthy down by language headings. This is probably a good low hanging fruit starting point at least. What do you think?

Sounds good!

Breaking down by file is interesting, because the same dependency may exist in multiple files (or multiple times in a single file). As such after loading all the dependencies, Deadpendency will deduplicate to get the final list to be checked.

Personally I would prefer duplication as it shows every project that may not "be in compliance", but not sure what the general population prefers.

So to include the file information, you would either break down the report by dependency file name and multiple files may have the same dependency report. Or, you would break down by language, but each dependency would link to 1 to many dependency files that included that dependency. I think I prefer the latter as it avoids duplication to keep the report smaller. Any thoughts?

Again my personal preference is towards verbosity and directness since it makes it harder to ignore... but I don't mind scrolling, but probably not as "pretty" as a more concise approach. I would like each language as a heading and then the failure / warning list under it.
This is a super hard combinatorial issue so I don't know if there is an elegant approach 😬

Thanks. I'll start with the language splitting.
In terms of making monorepos more manageable, I'll start with linking the related dependency file(s) next to each dependency. That addition seems beneficial to everyone, without introducing duplication or increasing the size of the report. So is a clear win I think.
I can understand why you may want to break down by dependency file, or by directory. I believe a good starting point would be some config setting like splitByDependencyFile: true. That would split each section of Unhealthy, Healthy With Warnings and Healthy down by files. I don't imagine having completely separate reports for each dependency file would be good, as mostly you want to ignore the healthy dependencies and just focus on the failing/warning dependencies.

Thanks! Sounds good to me, looking forward to it. Thanks for taking the feedback
Should I close this issue or do you want to keep it open?

I'll close this and create 3 other issues to track the 3 proposed changes thanks.


Update schemas to Pipeline 0.15.1

Schemas taken from https://github.com/redhat-developer/intellij-tekton/pull/178
Needed for #345

Codecov Report

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

@@           Coverage Diff           @@
##           master     #392   +/-   ##
=======================================
  Coverage   73.62%   73.62%
=======================================
  Files          52       52
  Lines        3564     3564
  Branches      640      640
=======================================
  Hits         2624     2624
  Misses        940      940

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 64103e6...57654e1. Read the comment docs.


filechooser: Support current_folder with OpenFile

https://github.com/flatpak/xdg-desktop-portal/pull/874

@sophie-h Why is this marked as draft? What still needs to be done?
Just an observation, but at least it will need to be rebased and use Option<FilePath> instead of Option<Vec<u8>>, to align with bc8f66dbf55dc45375f5f5f34a3bb0f0fffe2991.

Replaced it with #173


ElastAlert time field error running the rule

Elastalert throws an error when the timestamp_field specified in the yaml is named 'time'.
ERROR:root:Traceback (most recent call last):   File "/home/ubuntu/elastalert/elastalert/elastalert.py", line 892, in alert     return self.send_alert(matches, rule, alert_time=alert_time)   File "/home/ubuntu/elastalert/elastalert/elastalert.py", line 965, in send_alert     alert.alert(matches)   File "/home/ubuntu/elastalert/elastalert/alerts.py", line 230, in alert     body = self.create_alert_body(matches)   File "/home/ubuntu/elastalert/elastalert/alerts.py", line 166, in create_alert_body     body += unicode(BasicMatchString(self.rule, match))   File "/home/ubuntu/elastalert/elastalert/alerts.py", line 100, in __str__     self._add_rule_text()   File "/home/ubuntu/elastalert/elastalert/alerts.py", line 56, in _add_rule_text     self.text += self.rule['type'].get_match_str(self.match)   File "/home/ubuntu/elastalert/elastalert/ruletypes.py", line 473, in get_match_str     ts = match[self.rules['timestamp_field']] KeyError: 'time'
# Rule name, must be unique
name: impr-flatline

# (Required)
# Type of alert.
# the change rule will alert when a certain field changes in two documents within a timeframe
type: flatline

# (Required)
# Index to search, wildcard supported
index: logstash-impr-*
timestamp_field: time
threshold: 100

use_count_query: true
doc_type: impr

Was working fine with older version.

Do you know which version it worked with?
I'll look into this bug.
If possible, could you print what is in match right before that error?

elastalert_logger.info(match)
Curious to see if it's got @timestamp or just nothing.


feat: MaxTokensLimiter extension

Limit the maximum number of tokens in a GraphQL document.
Implementation

ExecutionContext: add parse_options
pass parse_options to graphql.language.parser.parse

Docs

deployment docs: mention security extensions

Other
max_aliases docstring: fix copy-paste error

Description

Types of Changes

[ ] Core
[ ] Bugfix
[x] New feature
[ ] Enhancement/optimization
[x] Documentation

Issues Fixed or Closed by This PR

Checklist

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[ ] I have tested the changes and verified that they work and don't break anything (as well as I can manage).

Thanks for adding the RELEASE.md file!

Here's a preview of the changelog:

This PR adds a MaxTokensLimiter extension which limits the number of tokens in a GraphQL document.
Usage example:
import strawberry
from strawberry.extensions import MaxTokensLimiter

schema = strawberry.Schema(
    Query,
    extensions=[
        MaxTokensLimiter(max_token_count=1000),
    ],
)

Here's the preview release card for twitter:

Here's the tweet text:
🆕 Release (next) is out! Thanks to reka for the PR 👏

Get it here 👉 https://github.com/strawberry-graphql/strawberry/releases/tag/(next)


Use configured variables for rtags binary names

rtags supports custom binary names.

Looks good. Thanks for your help!