Unhandled Runtime Error when download jpeg

Unhandled Runtime Error
InvalidCharacterError: Failed to execute 'atob' on 'Window': The string to be decoded contains characters outside of the Latin1 range.
Source
components/Download.tsx (19:25) @ _callee$
17 | }
18 | const base64String = await response.text()

19 | const decodeString = atob(base64String)
|                     ^
20 | let array = new Uint8Array(decodeString.length);
21 | for (let i = 0; i < decodeString.length; i++){
22 |     array[i] = decodeString.charCodeAt(i);
Show collapsed frames

the jpeg file uploaded before commit e36f936226504411e6b88fdc21ac9311dee999f5.
close

the jpeg file uploaded before commit e36f936226504411e6b88fdc21ac9311dee999f5.
close


Failure when running migrations

It looks like django-comment-migrate is not taking into consideration that a model might be removed - our investorticker model was removed in a later migration.

You can submit a pull request to catch the exception. Refer to the pull request:  https://github.com/starryrbs/django-comment-migrate/pull/43/files#diff-b9b440b2c40b366c0156b96601676c723ee6180ee3ac10a0503096f25b5916f9R40


feat: added custom scroll bar

Added scrollbar according to theme of application.

all right and also add your profile to about us | contribution page for template read the contribution.md file

Changes done.


issue with adds

Tip : https://umaar.com/dev-tips/83-console-time/
when i click the adds its show the wrong url
https://www.browseemall.com/DevTips
expected  url
https://www.browseemall.com

@umaar FYI

Good catch, thank you @ kasiriveni, fixed.


Finalize intergration of OIDC

Integrate changes which were kindly provided by @MariusDieckmann on branch feature/oidcsupport.

#42 would be great to have for this.


pre-commit: PRmichaelmaitland/llvm-project/commit/94ff86ef997cf2cce9c58c02c88d27056b68859e

Link: https://github.com/michaelmaitland/llvm-project/commit/94ff86ef997cf2cce9c58c02c88d27056b68859e
Requested by: @michaelmaitland

@michaelmaitland You should use https://github.com/llvm/llvm-project/compare/main...michaelmaitland:llvm-project:94ff86ef997cf2cce9c58c02c88d27056b68859e.

/close


setup script not working on macos

I cloned the repo and navigated to create_repository. I ran the setup script and got an error message, see below. I think there is some difference in the macos version of bash that doesn't accept some of the bash syntax you're using. Suggest using Python? :-)
~/workspace/trainings/artifactory-kata/create_repository (master) ✗  > ./setup.sh
../.shared/utils.sh: line 32: syntax error near unexpected token >' ../.shared/utils.sh: line 32:     rest_delete_repository $GENERIC_REPO1 &>> $LOGFILE'
./setup.sh: line 4: initkata: command not found
These are the names you should use for your generic repositories:
1:
2:
Remember to navigate to the exercises folder created.

I did a global search and replace for &>> and changed it to &> and then so far everything works ok. Could the same syntax work on other platforms perhaps?


Large memory footprint for version 0.5

Recently, I have updated into pcdet v0.5. However, when I am training on waymo, I have noticed larger memory footprint compared with the old version (0.3). On the same machine, I have to use a smaller number of workers for v0.5. Is this normal?

Hello, it seems that the default sampled interval for gt database in openpcdet before v0_3_1 is 10. So, if you have regenerate the gt database, the larger memory footprint might caused by the larger gt database.

That makes sense. I guess a smaller sampling interval is adopted for better precision? Is there any quantitative result?


Drain mode

Is there a way to figure out if a subscriber has drained all the messages in a given channel and is caught up? I would still want to process all the messages, but change behavior once have seen all the messages in the channel.

In this PR I’m adding a ‘pending_queue_size’ method to the subscription so that it is possible to check how far behind is the consumer https://github.com/nats-io/asyncio-nats-streaming/pull/21


Datatypes

Data Types

Methods of Primitives
Numbers
BigInt
Strings
Arrays and Array Methods
Iterables
Map and Set
WeakMap and WeakSet
Object.keys, values, entries, groupBy
Destructuring Assignment
Date and Time | Intro to Intl API | Temporal
JSON methods, toJSON

I will start working on this.


bug: NoSuchBeanDefinitionException with com.netflix.graphql.dgs.autoconfig.DgsIntrospectionConfigurationProperties in docker container

Using the following dependencies in build.gradle:
implementation(platform('com.netflix.graphql.dgs:graphql-dgs-platform-dependencies:4.9.21'))
implementation 'com.netflix.graphql.dgs:graphql-dgs-spring-boot-starter:4.9.21'
implementation 'com.netflix.graphql.dgs:graphql-dgs-subscriptions-websockets:4.9.21'
implementation 'com.netflix.graphql.dgs:graphql-dgs-spring-webmvc:4.9.21'
implementation 'com.netflix.graphql.dgs:graphql-dgs-spring-webmvc-autoconfigure:4.9.21'
implementation 'com.apollographql.federation:federation-graphql-java-support:0.9.0'
implementation 'com.netflix.graphql.dgs:graphql-dgs-spring-boot-oss-autoconfigure:4.9.22'
Expected behavior
Local builds work fine. Unit tests pass. Deployment to VMs works.
Actual behavior
Local builds work fine. Unit tests pass.
When deploying to VMs, encountered the error below: Note: Build jar file works locally as well.
Error creating bean with name 'dgs.graphql.introspection- com.netflix.graphql.dgs.autoconfig.DgsIntrospectionConfigurationProperties': Unsatisfied dependency expressed through constructor parameter 0; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'boolean' available: expected at least 1 bean which qualifies as autowire candidate. Dependency annotations: {@org.springframework.boot.context.properties.bind.DefaultValue(value={"true"})}
Description:
Parameter 0 of constructor in com.netflix.graphql.dgs.autoconfig.DgsIntrospectionConfigurationProperties required a bean of type 'boolean' that could not be found.
The injection point has the following annotations:
- @org.springframework.boot.context.properties.bind.DefaultValue(value={"true"})
Action:
Consider defining a bean of type 'boolean' in your configuration.
Consider adding a dependency on kotlin-reflect so that the constructor used for @ConstructorBinding can be located. Also, ensure that @ConstructorBinding is present on 'com.netflix.graphql.dgs.autoconfig.DgsIntrospectionConfigurationProperties' if you intended to use constructor-based configuration property binding.

This should have been resolved by #1026.


[Bug]: How can I only do experiment burst ID ?

Checked for duplicates
Yes - I've already checked
Describe the bug
I want to do experiment only 1 burst ID which is " t64_135523_iw2 " in rosamond CR site
so I add burst id in yaml.file below
  input_file_group:
      # Required. List of SAFE files (min=1)
      safe_file_path:
      # Required. List of orbit (EOF) files (min=1)
      orbit_file_path:
      # The unique burst ID(s) to process. If nothing provided, all bursts
      # in a SAFE will processed
      **burst_id: ["135523"]**

but the error message says that it can not find the burst id in SAFE.file
I downloaded the sentinel-1 image from "https://scihub.copernicus.eu/"
and it has "s1b-iw2-slc-vv-20180528t014925-20180528t014951-011115-01461c-005" xml file
but I can not find the burst id in xml file
so I want to know how to put burst ID in yaml.file. If my guess is correct, "135523" is burst id.
my question is that
Q1. Burst ID that I want to put is 135523, how to put that number in yaml.file
Q2. It seems like no burst ID in xml file, do I have to download other file than xml?
thank you for reading my quetion sir
What did you expect?
I expected [...]
Reproducible steps
1.
2.
3.
...

Environment
- Version of this software [e.g. vX.Y.Z]
- Operating System: [e.g. MacOSX with Docker Desktop vX.Y]
...

I solved myself


updated the langchain tools

Updated every class under langchain to implement Action interface without changing it's functionalities.
This pull request was created for https://app.gib.work/bounties/1a071256-33aa-4369-8d24-21839bcd4192 in an attempt to solve a bounty #53 . Payment for the bounty is immediately sent to the contributor after merge.

hey @shubhiscoding - awesome work just 1 thing will need to change
the action for each tool needs to be independent, so can be in a file under src/action/index.ts
and then import those action in src/langchain/index.ts and use them there, as per the orignal tool without extending it to Action interface

for validator, you'll need to use zod

hey @shubhiscoding - awesome work just 1 thing will need to change
the action for each tool needs to be independent, so can be in a file under src/action/index.ts
and then import those action in src/langchain/index.ts and use them there, as per the orignal tool without extending it to Action interface

So you what I'm thinking is to move all of class implementations that implement Action to src/action/index.ts and then all the classes in src/langchain/index.ts will have a private action object created for each tool and use that action object.
for example:
src/langchain/index.ts
export class SolanaBalanceTool extends Tool {
  private action: SolanaBalanceAction;
  name: string;
  description: string;

  constructor(solanaKit: SolanaAgentKit) {
    super();
    this.action = new SolanaBalanceAction(solanaKit);
    this.name = this.action.name;
    this.description = this.action.description;
  }

  async _call(input: string): Promise<string> {
    return this.action._call(input);
  }

  async handler(context: any, ...args: any[]): Promise<ActionResult> {
    return this.action.handler(context, ...args);
  }

  async validate(context: any, ...args: any[]): Promise<boolean> {
    return this.action.validate(context, ...args);
  }
}

src/actions/index.ts
export class SolanaBalanceAction extends Tool implements Action {
  name = "solana_balance";
  similes = ["check_balance", "get_wallet_balance"];
  description = `Get the balance of a Solana wallet or token account.

  If you want to get the balance of your wallet, you don't need to provide the tokenAddress.
  If no tokenAddress is provided, the balance will be in SOL.

  Inputs:
  tokenAddress: string, eg "So11111111111111111111111111111111111111112" (optional)`;
  examples: ActionExample[][] = [
    [
      {
        input: {
          message: {
            id: "1",
            content: { text: "Get my balance" },
            userId: "user1",
            timestamp: Date.now(),
          },
        },
        output: { success: true, data: { balance: "100 SOL" } },
      },
    ],
  ];

  constructor(private solanaKit: SolanaAgentKit) {
    super();
  }

   async _call(input: string): Promise<string> {
    try {
      const tokenAddress = input ? new PublicKey(input) : undefined;
      const balance = await this.solanaKit.getBalance(tokenAddress);

      return JSON.stringify({
        status: "success",
        balance: balance,
        token: input || "SOL",
      });
    } catch (error: any) {
      return JSON.stringify({
        status: "error",
        message: error.message,
        code: error.code || "UNKNOWN_ERROR",
      });
    }
  }

  handler: Handler = async (context, ...args) => {
    const input = args[0];
    const convert = async (): Promise<ActionResult> => {
      const promise_string = await this._call(input);
      return JSON.parse(promise_string);
    };
    return convert();
  };

  validate: Validator = async (context, ...args) => {
    const input = args[0];
    return typeof input === "string";
  };
}

Is that what you want?

Hey @thearyanag I have pushed changes, If I misunderstood the assignment do tell, I'll make the necessary changes

Hii @thearyanag I have made the changes you asked for and tested  it too, Please review it once!

@thearyanag are there any changes to be made?

I reviewed your test, I think this can be submitted for a PR.

I reviewed your test, I think this can be submitted for a PR.

Can it be merged then? @thearyanag?

hey @shubhiscoding - this looks good

it's not working for single input functions
what's the use of validator if you are not using it anywhere?
you have defined types from Eliza repo, but those are not used anywhere in the kit

closing this in favour of #72

Hii @thearyanag  I have fixed the single input function issue, also removed all  the unsed types and have added input vallidation in the lastest commit I just pushed, can you please reopen this?

I'm raising another PR #101 just review it once, If it doesn't fixes the issue close it and I won't raise a PR again for this issue.


A file is missing.

The file，which may be called “Paviau.mat”,is missing,I suppose.

Hi, you can click here for this file.

Thank you for your reply.I have no idea about this dataset before.Now,I have realized this dataset,which can be downloaded in many places,is a public dataset.Thank you again.
At 2019-10-05 10:07:30, "YonghaoXu"<EMAIL_ADDRESS>wrote:
Hi, you can click here for this file.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

exm,may i ask for some pakeage about SSFCN-CRF,some code about this algorithm.Thx

The code of SSFCN-CRF has already been included in SSFCN.py @HazelSCUT


Bug: Interferes with vim-surround in LaTeX

Self Checks

[x] I'm using the latest lualine.
[x] I didn't find the issue in existing issues or PRs.

How to reproduce the problem
Run the following shell commands:
git clone https://github.com/tpope/vim-surround.git
git clone https://github.com/nvim-lualine/lualine.nvim.git
nvim --clean tmp.tex -u <(tee <<EOF
  setlocal shiftwidth=2 expandtab
  set rtp+=$PWD/vim-surround,$PWD/lualine.nvim
  lua require('lualine').setup()
  call nvim_input('i<Space><Space><C-S><C-S><Bslash>itemize<CR>')
EOF)

Expected behaviour
Buffer content is
  \begin{itemize}

  \end{itemize}

Actual behaviour
Buffer content is
 \begin{itemize}

  \end{itemize}

Note that there is a trailing space on the last line.
Minimal config to reproduce the issue
call plug#begin("/tmp/surround/.local/share/nvim/plugged")
Plug 'tpope/vim-surround'
Plug 'nvim-lualine/lualine.nvim'

call plug#end()

setlocal shiftwidth=2 expandtab

lua << END
require'lualine'.setup {}
END

Additional information

This seems to fix the problem:
diff --git a/lua/lualine.lua b/lua/lualine.lua
index 49e38a1..d34e79f 100644
--- a/lua/lualine.lua
+++ b/lua/lualine.lua
@@ -342,7 +342,6 @@ local function refresh(opts)
   --   https://github.com/nvim-lualine/lualine.nvim/issues/791
   if
     opts.trigger == 'autocmd'
-    and vim.v.event.new_mode ~= 'c'
     -- scheduling in op-pending mode seems to call the callback forever.
     -- so this is restricted in op-pending mode.
     -- https://github.com/neovim/neovim/issues/22263


Error importing pygments.lexers.web on Python 2.5

(Original issue 778 created by mfontenele on 2012-05-31T19:52:32.831644+00:00)
{{{
$ python
Python 2.5 (r25:51908, May 15 2012, 16:19:31)
[GCC 4.1.2 20080704 (Red Hat 4.1.2-52)] on linux2
Type "help", "copyright", "credits" or "license" for more information.

import pygments.lexers.web
Traceback (most recent call last):
File "", line 1, in
UnicodeDecodeError: 'rawunicodeescape' codec can't decode bytes in position 12-22: \Uxxxxxxxx out of range

}}}

(Original issue 778 last updated on 2012-11-12T23:05:23.234300+00:00)
(Issue automaticaly closed due to status in Bitbucket: resolved)

(Original comment by None on 2012-06-05T12:51:04.511805+00:00)
Hey I had the same problem: The import of pygments.lexers.web did not work.
I switched to Python version 2.5.4 and there is the bug fixed. I hope this helps.

(Original comment by tshatch on 2012-06-07T00:48:40.662328+00:00)
Yes, this is an issue with one of my last commits.  It affects all narrow builds of python (sys.maxunicode == 65535ish).
I'm working on a fix as well as making regexlint recognize this case.
Tim

(Original comment by None on 2012-07-19T11:12:57.792577+00:00)
Any updates on this?

(Original comment by tshatch on 2012-08-28T15:44:31.814885+00:00)
The fix is merged to pygments-main here.

(Original comment by tshatch on 2012-11-01T16:48:05.579420+00:00)
Georg, I think this can be closed.


[ADDITION] servers.guru

Category
Cloud Hosting
Software to be added
https://servers.guru
Servers.guru provide cloud hosting (VPS and cloud servers with dedicated CPU resources). It is a reseller with an emphasis on privacy. No private informations beside a working email address are required from the customer if crypto-currencies are used as a payment method. It is also on the lower end of the usually costly alternatives.
Why it should be added?
It should be added as there is little alternatives in the list and one of them is even a dead link.
Supporting Material
website is here: https://servers.guru
Association Disclosure
I'm the funder of servers.guru
Would you like to submit a PR?
Yes!
Please tick the boxes

[X] You have filled out this form accurately, and to the best of your knowledge
[X] You have indicated weather or not you are associated with the suggested addition
[X] A similar submission has not already been opened for this software/ service
[X] You agree to the code of conduct

Hi @slade991
servers.guru looks awesome, nice work!
Would you be up for submitting a PR? As the description, just summarize what you put as this issue description, (accepts crypto, server locations, affordable, is reseller)
And you're right- there aren't a lot of decent anonymous hosting providers at the moment. You might have me as a new customer very shortly!
Out of interest, which upstream provider are you using?
I shall also delete Vindo now it's offline...

Hey!
Thanks :) i will do the pull request.
For upstream providers, at the moment we use Hetzner, we are always looking to incorporate new ones, but so far didn't find any other that caught our attention.
We'll be very happy to count you as a customer, if you have any questions don't hesitate to contact me :)


Incorrect implementation of getNewAddress()

https://github.com/sgsshankar/blockonomics-node/blob/06b79753a1f8cba5216908b618b33e4920dece94/blockonomics.js#L59-L67
Solution below, I can submit a pull request if you'd like
	getNewAddress: function(APIKEY, reset, match_account) {
		var url = config.config.newAddress;
		if (reset == 1)
			url = url + "?reset=1";
		if (match_account)
			url = ( url + ( ( reset == 1 ) ? "&": "?" ) ) + "match_account=" + match_account;
		var result = sendRequest(url, "POST", {}, APIKEY);
		return result;
	}

Hi @boulosda this repo is no longer being maintained by owner.. can you please do the changes in your repo /any other errors you find and let me know.
I will fork official blockonomics repo from that


Add integration test for firestore python client

Let's see how Kokoro works

Closing. There isn't a hermetic way to run the system test.


Players slides on right purple GEL

while standing on purple gel that is facing the right side the player will slowly slide upwards and you're unable to control their direction

1ecdcc9402ae1f461b91af454d740b9173789f09


Update curl submodule on 02/11 for vulnerability fixes

https://curl.haxx.se/mail/lib-2016-10/0076.html

In two weeks time, on Wednesday November 2nd, we will release curl and libcurl
7.51.0 unless something earth shattering happens.
This release will bundle no less than eleven security advisories and their
associated fixes (unless we get more reported in the time we have left). Each
individual security issue will be documented in detail in their own advisories
as usual and sent out as separate emails and get documented on the curl web
site. Chances are big several of these affects your use of curl.
We have never before handled anywhere close to this many security problems in
a single release.

👍 Thanks for the heads up! I'll be sure to try to update this library very quickly.

Ok, this update is now on master.
I'll publish new versions once CI passes


WIP Use DNSProvider secret ref in DNSPolicy

closes #715
Removes the requirement for a ManagedZone to be configured for a host in order for the DNSPolicy to create dns records for it.
Implements the providerRef option for DNSPolicy, ManagedZone and DNSRecord as described here https://github.com/Kuadrant/architecture/blob/main/rfcs/0005-single-cluster-dnspolicy.md
Todo:
[] Update docs

/hold
Will come back to these changes after https://github.com/Kuadrant/multicluster-gateway-controller/pull/780 is merged, or when all DNS code is moved to it's new repo.

/close
This PR will need to be considerably reworked. Closing for now.


Precedence of |>

On the left, |> is as tight as assignment operators. This allows parsing x = y |> z as x = (y |> z), and x ? y : z |> w as (x ? y : z) |> w.
On the right, there are two options:

|> PipeExpression
|> AssignmentExpression

(2) matches the precedence of =>, which is the most similar operator to |> (they both take something on their left and put it in the expression on their right). It also allows thinks like x |> res = % and x |> () => %. However when used in longer chains, x |> y = % |> f(%) would be parsed as x |> (y = % |> f(%)) and  not as x |> (y = %) |> f(%).
(1) disallows unparenthesized assignments and arrows on the right of |>.

I think, more often than not, the pipeline operator is going to be used over multiple lines. With that in mind:
let temp
const x = data
  |> temp = doStuff(%)
  |> g()

I don't think you would expect that assignment to also grab the |> g() from the following lines - for this reason, I would rather force parentheses (option 1) rather than go with option 2.

ick, why is doing an assignment inside a pipe even allowed in the first place? (i know the answer, because JS allows assignment in expression positions, sadly)
that's indeed what should require forced parens, since nobody should be doing that anyways and linters and styleguides will ban it regardless

Would it be possible to make it so if you're currently on the RHS of a pipeline operator, and you've entered the body of an arrow function, and another "|>" token is encountered, then you auto-close the arrow function body? This sort of makes "|>" act like delimiters, separating out one expression from the next. This would mean the following:
const result = x
  |> x => x + 1
  |> y => y + 1
// same as
const result = x
  |> (x => x + 1) // Note how this function definition got auto-closed
  |> y => y + 1

const fn = x => a |> f
// same as
const fn = x => (a |> f) // This "|>" token was the first one found, so it didn't auto close the arrow function.

I don't see any issues with this yet ...

```jsa |> b(c |> d) |> e`

Good call. I think the concept should still be possible, I'm just not sure the best way to formulate it in a rigorous way.
But, the gist of the idea is to try and treat "|>" similar to how commas are treated when separating function parameters, i.e. anything between two "|>" in the same expression should be treated as one unit. i.e. a |> whatever... |> c is the same as a |> (whatever...) |> c, just like f(a, whatever..., c) is the same as f(a, (whatever...), c). Just like you can nest function calls, and the comma delimiter still works properly (e.g. f(a, b(c, d), e)), likewise, you should be able to nest pipelines, when things like parentheses get involved.
Does that make any sense?

ick, why is doing an assignment inside a pipe even allowed in the first place? (i know the answer, because JS allows assignment in expression positions, sadly)
that's indeed what should require forced parens, since nobody should be doing that anyways and linters and styleguides will ban it regardless

We could do the same thing we’re doing with yield expressions and make in unparenthesized assignment in pipe bodies an early error.

Note that AssignmentExpression is:

yield (disallowed)
actual assignments (maybe disallowed)
arrow functions
conditional expressions

So the decision becomes: do we want to allow things like
const makeAdderLogger = add => add
                                |> num => % + num |> console.log(%)

const add2AndLog = makeAdderLogger(2);

add2AndLog(4); // logs "6"

or not.

For clarification @nicolo-ribaudo - would your code example be interpreted as this?
const makeAdderLogger = add => (add
                                |> num => ((% + num) |> console.log(%))
)

In the decision is, whether or not your example should be allowed without being forced to put parentheses around the function definitions?

Yes, both your interpretations are correct.

We can view this situation as an analogue of confusing grouping when we combine || and ??.
?? functionally has the same precedence level as ||, but ?? and || cannot be used together without parentheses, in order to prevent confusion like with a || b ?? c || d ?? e.
Likewise, we could prohibit (from both the left- and right-hand sides of |>) all unparenthesized expressions that are at the same precedence level of |>.
“|> functionally has the same precedence level as =>, ? :, and yield, but |> and =>, ? :, or yield cannot be used together without parentheses, in order to prevent confusion like with a => b |> c => d |> e.

After more thought, I don’t see any way to reconcile unparenthesized conditionals in pipe heads/bodies (like a |> b : % : c) with avoiding confusing pipelines in conditionals (like a ? b : c |> %.d). I think we should require all conditionals to be parenthesized in pipe bodies.
I’m thinking that the most desirable behavior might be to ban any mixing of the pipe operator and any other assignment-level operation without parentheses. (The other assignment-level operations are =>, =, +=, etc., ? :, and yield.)
This would be similar to the ban on mixing ?? with || or && without parentheses.
I plan to edit the spec and explainer with this change.

Arrows

a |> (b => %.c) |> %.d
a |> (b => %.c) |> %.d

a |> (b => %.c |> %.d)
a |> (b => %.c |> %.d)

a |> b => %.c |> %.d
SyntaxError
Assignment

a = b |> %.c
a = (b |> %.c)

a |> (b = %) |> %.c
a |> (b = %) |> %.c

a |> (b = % |> %.c)
a |> (b = % |> %.c)

a |> b = % |> %.c
SyntaxError
Conditionals

(a ? b : c) |> %.d
(a ? b : c) |> %.d

a ? b : (c |> %.d)
a ? b : (c |> %.d)

a ? b : c |> %.d
SyntaxError

a ? (b |> %.c) : d
a ? (b |> %.c) : d

a ? b |> %.c : d
SyntaxError

a |> %.b ? c : d
a |> (%.b ? c : d)

a ? (b |> %.c) : d
a ? (b |> %.c) : d

a ? b |> %.c : d
SyntaxError
Yields

a |> (yield %) |> %.b
a |> (yield %) |> %.b

a |> (yield % |> %.b)
a |> (yield % |> %.b)

a |> yield % |> %.b
SyntaxError

This was addressed in 6c458b5. A |> PipeExpression now has ShortCircuitExpression on its left and AssignmentExpression on its right, and the right-hand AssignmentExpression must not cover ArrowFunction, AsyncArrowFunction, YieldExpression, ConditionalExpression, or an assignment operation.
The specification has been updated.


nixos: Fix cross compilation of derivations defined in NixOS via pkgs

Description of changes
Fixes #190289
Following example will fail without this patch:
(import ./nixos/lib/eval-config.nix {
  modules = [
    ({ pkgs, ... }: {
      config = {
        nixpkgs.crossSystem.system = "aarch64-linux";
        system.build = pkgs.runCommand "test"
          { nativeBuildInputs = [ pkgs.jq ]; } "jq > $out";
      };
    })
  ];
}).config.system.build

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

[x] Fits CONTRIBUTING.md.

Would this make changes like #190215 obsolete?

After this PR, you have to write it like:
pkgs.runCommand "validate-vector-conf" { nativeBuildInputs = [ pkgs.vector ]; } ''
  vector validate --no-environment "${file}"
  ln -s "${file}" "$out"
''

You do not need to add buildPackages, but you have to put vector into nativeBuildInputs.

Following derivation fail to cross compile right now:

https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/services/web-apps/hedgedoc.nix#L19
https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/services/monitoring/thanos.nix#L66
https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/services/databases/dgraph.nix#L9
https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/services/misc/redmine.nix#L29
https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/services/databases/influxdb.nix#L99
... and many more.

They get fixed automatically with this PR.

You do not need to add buildPackages, but you have to put vector into nativeBuildInputs.

Would you be so kind to add a fix for this to this PR? Otherwise with my limited knowledge I think this sounds good.

Existing code will not break with this PR. Your PR is compatible with this PR. If you want, you can do a cleanup in one line
from
nativeBuildInputs = [ pkgs.buildPackages.vector ];

to
nativeBuildInputs = [ pkgs.vector ];

This PR allows you to write derivations as you do it for nixpkgs.

I didn't receive an answer from @Ericson2314 so lets try it

Thanks! We will see if we face issues.

I'd like to understand this. @ck3d can you explain why __splicedPackages is needed?

I'd like to understand this. @ck3d can you explain why __splicedPackages is needed?

So that the packages will have a __spliced attrset which contains buildHost hostTarget etc

Ah I see now, normally packages are obtained via callPackage ({ hello, ... }: ...) which takes care of the splicing.
Is there a reason that import nixpkgs { ... } does not return the spliced packages by default? Does this affect performance?


Disable IAST opt-out to fix test errors

Motivation
Remove bug annotation for library java weblog-variant play as it's not really a bug of the tracer is a problem with the test configuration
standalone scenario allows IAST opt-out vulnerabilities to be reported, this can drives into some test failures like tests/appsec/test_asm_standalone.py::Test_AppSecStandalone_UpstreamPropagation::test_no_appsec_upstream__no_attack__is_kept_with_priority_1__from_minus_1 -> is reporting a WEAK_HASH vulnerability so we have an asm event in a test that is not expected
Changes
Add DD_IAST_ENABLED false to fully disable IAST
Remove the bug annotation to allow test execution

Workflow

⚠ Create your PR as draft ⚠
Work on you PR until the CI passes (if something not related to your task is failing, you can ignore it)
Mark it as ready for review

Test logic is modified? -> Get a review from RFC owner. We're working on refining the codeowners file quickly.
Framework is modified, or non obvious usage of it -> get a review from R&P team

:rocket: Once your PR is reviewed, you can merge it!
🛟 #apm-shared-testing 🛟
Reviewer checklist

[ ] If PR title starts with [<language>], double-check that only <language> is impacted by the change
[ ] No system-tests internal is modified. Otherwise, I have the approval from R&P team
[ ] CI is green, or failing jobs are not related to this change (and you are 100% sure about this statement)
[ ] A docker base image is modified?

[ ] the relevant build-XXX-image label is present

[ ] A scenario is added (or removed)?

[ ] Get a review from R&P team

rebasing, to fix CI issue.


Revert "remove alt text from screenshot (#469)"

This reverts commit ec7ec7b52d4d3671e1d2129481c5b3250cb7f84b.
Restoring the alt text for screenshots in some of the readmes that previously removed as it was causing issues with the sample viewer.

Thanks @Rachael-E , I think those alt-texts you have spotted were still on the 'to do' list for the readmes, but now that we have them here it's already sorted!


Added macros for currently implemented ops

TODO:

[ ] Add arange! macro after #72 is merged
[ ] Add macros for linalg ops after #51 is merged

Closing this in favour of new PR that gives a cleaner commit history


Generate a warning, not a fatal error, on insufficient glucose data for autosens

This should fix #117.
edison@edison-rl ~/openaps-dev $ openaps report invoke settings/autosens.json
detect-sensitivity://text/shell/settings/autosens.json
Optional feature autosens disabled: not enough glucose data to calculate sensitivity
reporting settings/autosens.json
edison@edison-rl ~/openaps-dev $ cat settings/autosens.json
{ "ratio": 1, "reason": "not enough glucose data to calculate autosens" }

Hi @scottleibrand , yes this fix is working correctly. Deliberately reducing the glucose data to 2 hours of data only resulted in this response:
{"ratio":1,"reason":"not enough glucose data to calculate autosens"} and determine-basal continued correctly. Thanks for the fix.


"Exec format error" on Raspberry Pi 3/Debian

Hello! I downloaded the precompiled Linux build with wget and unzipped it, but upon chmod a+x'ing it and running it, it says:
-bash: ./discordo: cannot execute binary file: Exec format error
Was it compiled with a different Linux distro or in mind or am I doing something wrong?
Either way I'll try to build from source instead and see how that goes. Thank you so much for making this, I use a tiny B&W portable CRT TV as a display for my Raspberry Pi and using discord on it would be cool as hell.

It obviously will not work as the binary builds were intended for x86_64, you must compile discordo natively for your pi (arm)'s architecture.

Oh, that makes sense.
I just tried to compile from source, and running go build doesn't produce any binaries and says:
../../go/pkg/mod/github.com/mattn/go-runewidth@v0.0.14/runewidth.go:7:2: found packages uniseg (doc.go) and main (gen_breaktest.go) in<EMAIL_ADDRESS>(I apologize, I have never used golang before)

go build -modcacherw

I just tried this and it gives the same error message about the packages.

Well I don't know much about setup of Go on other architectures, consult arbitrary documentation about it perhapd

@livvy94 https://github.com/golang/go/wiki/GoArm

@livvy94 @livvy94 https://github.com/golang/go/wiki/GoArm
GOARCH=arm64 go build .

Try to build the binary from the latest commit:
git clone https://github.com/ayn2op/discordo
cd discordo
go build -v .

Unfortunately it just gives the same message about uniseg (doc.go) and main (gen_breaktest.go)

ayn2op try not to close issue without original creator verifying its fixed challenge

Oh, that makes sense.
I just tried to compile from source, and running go build doesn't produce any binaries and says: ../../go/pkg/mod/github.com/mattn/go-runewidth@v0.0.14/runewidth.go:7:2: found packages uniseg (doc.go) and main (gen_breaktest.go) in<EMAIL_ADDRESS>(I apologize, I have never used golang before)
EDIT: I'm running go version go1.15.15 linux/arm64

The minimum Go version required to compile Discordo is 1.19. Please upgrade the Go toolchain and try again.

After a lot of wrestling with golang's downloads (I'm on a raspberry pi so apt-get has an old version), I was able to install 1.20 and build the code! Thank you for being patient with me.


Add aliases for Kotlin

Added file extensions kt and kts as aliases for Kotlin.

Thank you for making this @osipxd!
To make the tests pass, you also have to change prism-kotlin.js. (For more information, see the "adding aliases" section here.)

Ah, missed it. Fixed now.

Thank you for contributing!


Added the new view modifier named "customBack"

with custom back button implemented.

Decided to stick with the standard navigation.


Fix capital/fuel cost switch for centreposts in STEP TF cost model

Fix ifueltyp switch for different i_tf_sup cases in step_a22010301, specifically the cryo-Al case. It currently only works in the copper (i_tf_sup == 0) case. The Al conductor mass for the centrepost can be extracted from the sctfcoil_module for the purpose of working out the centrepost cost in the cryo-Al case. Recommended by @stuartmuldrew in !389.

This seems like a STEP cost model issue, is that right @j-a-foster ?

Yeah and it appears that it was implemented so this can be closed.


all-books error: JSONDecodeError when doing search

I'm getting error from other types of searches as well, but as an example here's the results of all-books author search.
$ bookcut all-books --author 'Stephen King'

results in:
 ____              _     ____      _
| __ )  ___   ___ | | __/ ___|   _| |_
|  _ \ / _ \ / _ \| |/ / |  | | | | __|
| |_) | (_) | (_) |   <| |__| |_| | |_
|____/ \___/ \___/|_|\_\\____\__,_|\__|

**********************************
Welcome to BookCut! I'm here to
help you to read your favourite books!
**********************************

Start searching for all books by Stephen king:
Connected to: http://www.openlibrary.org
Traceback (most recent call last):
  File "/home/dmwyatt/.local/bin/bookcut", line 8, in <module>
    sys.exit(entry())
  File "/home/dmwyatt/.local/pipx/venvs/bookcut/lib/python3.8/site-packages/click/core.py", line 1137, in __call__
    return self.main(*args, **kwargs)
  File "/home/dmwyatt/.local/pipx/venvs/bookcut/lib/python3.8/site-packages/click/core.py", line 1062, in main
    rv = self.invoke(ctx)
  File "/home/dmwyatt/.local/pipx/venvs/bookcut/lib/python3.8/site-packages/click/core.py", line 1668, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/dmwyatt/.local/pipx/venvs/bookcut/lib/python3.8/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/dmwyatt/.local/pipx/venvs/bookcut/lib/python3.8/site-packages/click/core.py", line 763, in invoke
    return __callback(*args, **kwargs)
  File "/home/dmwyatt/.local/pipx/venvs/bookcut/lib/python3.8/site-packages/bookcut/bookcut.py", line 103, in bibliography
    lista = allbooks(author, ratio)
  File "/home/dmwyatt/.local/pipx/venvs/bookcut/lib/python3.8/site-packages/bookcut/bibliography.py", line 21, in main
    data = json.loads(jason)
  File "/usr/lib/python3.8/json/__init__.py", line 357, in loads
    return _default_decoder.decode(s)
  File "/usr/lib/python3.8/json/decoder.py", line 337, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/lib/python3.8/json/decoder.py", line 355, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 3 column 1 (char 2)

Not sure if it's an error from openlibrary or an error in parsing and don't have time to investigate at the moment...

My guess is openlibrary was having connectivity problems or something right when I was trying out bookcut for the first time, because it's working fine now.  Bad luck for me!
Maybe add a check to see if you're getting back valid JSON and provide a friendlier error message to the user?

Issue resolved in version 1.3.6.


Fix to jazzy install appears needed in 3.7 recipes

https://github.com/flutter/flutter/issues/118464 is still affecting the engine release branch, preventing cherry-picks, and potentially also blocking creating the release bits? Marking P0 in case this affects the release.
See: https://github.com/flutter/engine/pull/39002
cc @godofredoc

cc @itsjustkevin

Also affecting https://github.com/flutter/engine/pull/38988

Duplicate of https://github.com/flutter/flutter/issues/118729

Fixed, please re-run any failing tests on PRs not included in the bug. I already ran the PRs included here.


improvement(build-tools): Add build-infrastructure package

This change introduces a new package containing types and helper functions that will be used across multiple build-tools packages, including @fluidframework/build-tools and @fluid-tools/build-cli.
The primary purpose of this package is to provide a common way to enumerate Packages, Release Groups, and Workspaces
across a Fluid repo.
The package is private and nothing depends on it yet, so it should cause no problems when merged in its current state.

[!IMPORTANT]
I have found it easiest to write this as a new package, but I am not fanatical about this. There are practical reasons why a package is a little easier right now (the direction of dependencies between the packages in particular) but for the purposes of this review, if you think this should be organized into modules within an existing package instead, try and ignore that feedback for now and focus on the function and scope of the code.

Background
Today both fluid-build and build-cli (flub) need to understand the layout of the repo - what packages belong to what release groups, what folders are workspace roots vs. independent packages, etc. We have been using the types and classes from fluid-build in the flub code, but the relationship has always been strange because flub has a concept of release groups while fluid-build uses a MonoRepo class which is analogous to a Workspace.
Conceptually, Release Groups and Workspaces are distinct, but in code there is not a strong representation of the "release group" concept. In flub we use the MonoRepo class and a type ReleaseGroup = string together as a stand-in for the ReleaseGroup concept which has meant that release groups and workspaces (the MonoRepo class) are more or less the same thing in practice.
That has always been a very weird situation that has gotten complicated as the repo has grown, and now we find that we want the benefits of interdependencies in between packages provided by workspaces but the flexibility of releasing and versioning groups of packages within those workspaces. These changes are a step towards that future.
How the API and interfaces were developed
The interfaces exposed by this package were extracted from the uses of packages and release groups in build-tools and build-cli. The minimal set of properties and functions necessary by both of those packages was used. In some cases, duplicative properties or functions were removed. For example, the Package type had dependencies and combinedDependencies; now it just has the latter and the caller can filter out what it doesn't want or extend the shared interface.
The goal
The eventual goal state - far beyond this PR - is to have all the shared types and data about the repo layout and other shared code in the build-infrastructure package, and then have flub and fluid-build be in individual packages. They shouldn't depend on each other - all the shared logic - especially the types - should be in the infra package.
To do before merge

[x] There is no way in the current PR to load the repo from the old repoPackages config. I think it is feasible to write a load function that works with the old config, which will make it easier to transition to the new config format. Update September 26: Legacy configs can now be loaded.

See the package README in this PR for more details. Excerpts are included here for convenience.
API Overview
The API is built around four key types which form a hierarchy: IFluidRepo, IWorkspace, IReleaseGroup, and
IPackage. For the purposes of this documentation, the terms "Fluid repo," "workspace," "release group," and "package"
generally refer to these types.
The Fluid repo
The primary entrypoint for the API is the IFluidRepo type. A Fluid repo can contain multiple workspaces and release
groups. Both workspaces and release groups represent ways to organize packages in the repo, but their purpose and
function are different.
Workspaces
Workspaces are a generally a feature provided by the package manager (npm, yarn, pnpm, etc.). A workspace defines the
physical layout of the packages within it. A workspace is rooted in a particular folder, and uses the configuration
within that folder to determine what packages it contains. The config used is specific to the package manager.
The workspace is also the boundary at which dependencies are installed and managed. When you install dependencies for a
package in a workspace, all dependencies for all packages in the workspace will be installed. Within a workspace, it is
trivial to link multiple packages so they can depend on one another. The IWorkspace type is a thin wrapper on top of
these package manager features.
Importantly, this package does not attempt to re-implement any features provided by workspaces themselves. Users are
expected to configure their package managers' workspace features in addition to the Fluid repo configuration.
A Fluid repo will only load packages identified by the package manager's workspace feature. That is, any package in the
repo that is not configured as part of a workspace is invisible to tools using the Fluid repo.
Release groups
While workspaces manage dependencies and physical layout of packages, release groups are focused on groups of packages
that are versioned and released together. Release groups are always a subset of a workspace, and must contain at least
one package. Release groups cannot span multiple workspaces.
Importantly, release groups are the unit of packages that are released and versions together.

[!IMPORTANT]
A workspace must have at least one release group, and all packages must be a part of a release group.

[!NOTE]
In the v0 version of build-tools, release groups and workspaces have a 1:1 relationship. In contrast, with the types
defined here in build-infrastructure, workspaces can contain multiple release groups.

Packages
Packages are the lowest-level entity in build-infrastructure. A package must be a part of both a release group and
workspace in order to be managed with build-infrastructure. In general, developers should prefer using release groups -
which are ultimately just groups of packages - to working with individual packages.
What about "independent packages?"
In the v0 version of build-tools, we have the concept of independent packages: packages that are not part of a release
group and are released independently. This concept no longer exists. There are only release groups. Packages that
release independently can either be part of a single-package workspace (and release group), or they can be part of
another larger workspace, contained within a single-package release group.
Features
Git repo capabilities
A Fluid repo is often contained within a Git repository, and some functionality expects to be used within a Git
repository. Features that need to execute Git operations can asynchronously retrieve the SimpleGit instance using the
IFluidRepo.getGitRepository API. If the Fluid repo is not within a Git repo, then that call will throw a
NotInGitRepository exception that callers should handle appropriately. If they don't, though, the exception makes it
clear what has happened.

[!NOTE]
This design addresses a major problem with build-tools v0, which was that code often made assumptions that it was
operating within a Git repo. That's often true, and some fetures can and should only work in that context, but the
implementation attempted to load the Git functionality blindly and would fail outright outside a Git context. With
IFluidRepo, the Git integration is more loosely coupled and the APIs make it clearer that it is not safe to assume
the presence of a Git repo.

Package selection and filtering APIs
The IFluidRepo object provides access to workspaces, release groups, and their constiuent packages, but often one wants
to operate on a subset of all packages in the repo. To support this, build-infrastructure provides a selection and
filtering API. Packages can be selected based on criteria like workspace and release group, and the lists can be further
filtered by scope or private/not private. Advanced filtering not covered by the built-in filters can be implemented
using Array.prototype.filter on the results of package selection.
Loading old config formats
The repoPackages configuration currently used by fluid-build will be loaded if the newer repoLayout config can't be
found. This is for back-compat only and will not be maintained indefinitely. Users should convert to repoLayout when
possible.
Configuration
Configuration for the repo layout is stored in a config file at the root of the repo. This can either be part of the
fluidBuild.config.cjs file in the repoLayout property, or in an independent config file named
repoLayout.config.cjs (or mjs).
Example
The following example configures three workspaces demonstrating the three archetypes - a workspace with multiple release
groups, a workspace with a single release group that contains multiple packages, and a workspace with a single release
group that contains a single package.
repoLayout: {
  workspaces: {
    // This is the name of the workspace which is how it's referenced in the API.
    "client": {
      // This workspace is rooted at the root of the Git repo.
      directory: ".",
      releaseGroups: {
        // This key is the name of the release group. It must be unique across all
        // release groups.
        client: {
          // The include property can contain package names OR package scopes. If
          // a scope is provided, all packages with that scope will be a part of
          // the release group.
          include: [
            // Include all the Fluid Framework scopes and packages except for
            // @fluid-example.
            "@fluidframework",
            "@fluid-experimental",
            "@fluid-internal",
            "@fluid-private",
            "@fluid-tools",
            "@types/jest-environment-puppeteer"
            "fluid-framework",
          ],
          // A release group can have an OPTIONAL root package. This package
          // is typically private and is similar to the root package for a workspace.
          // This release group root package may be useful to store scripts or other
          // configuration only applies on the release group,
          rootPackageName: "client-release-group-root",

          // A release group may have an ADO pipeline URL associated with it. This
          // URL is used to provide direct links to the pipeline when running releases.
          adoPipelineUrl:
            "https://dev.azure.com/fluidframework/internal/_build?definitionId=12",
        },
        examples: {
          // This release group contains only the @fluid-example packages.
          include: ["@fluid-example"],
        },
        // If any packages in the workspace don't match a release group, loading the
        // repo layout config will throw an error.
      },
    },
    "build-tools": {
      // This workspace is rooted in the build-tools folder. This folder must contain
      // a workspace config. The specific config depends on the package manager being used.
      directory: "./build-tools",
      releaseGroups: {
        // Release groups can have the same name as workspaces, but all release group names
        // must be unique regardless of the workspace they belong to.
        "build-tools": {
          include: [
            // Include all Fluid Framework scopes. Only packages contained in the workspace
            // will be included, so it is safe to use the same scopes in multiple release
            // group definitions as long as they're in different workspaces.
            "@fluidframework",
            "@fluid-example",
            "@fluid-experimental",
            "@fluid-internal",
            "@fluid-private",
            "@fluid-tools",
          ],
          rootPackageName: "build-tools-release-group-root",
          adoPipelineUrl:
            "https://dev.azure.com/fluidframework/internal/_build?definitionId=14",
        },
      },
    },
  },
}

Loading a Fluid repo from a configuration file
To load a Fluid repo, you use the loadFluidRepo function. You can pass in a path to a Git repository root, or if one
is not provided, then the Git repository nearest to the working directory can be used.
This function will look for a repo layout configuration in that folder and load the workspaces, release groups, and
packages accordingly and return an IFluidRepo object that includes Maps of workspaces, release groups, and packages as
properties.
Other APIs
Type guards
You can use the isIPackage and isIReleaseGroup functions to determine if an object is an IPackage or
IReleaseGroup respectively.
Base classes
The PackageBase abstract class can be used as a base class to create custom IPackage classes.
Miscellaneous improvements
Fluid repos can be rooted anywhere
Fluid repos are rooted where their config file is located, not at the root of a Git repo. There can be multiple Fluid
repos within a Git repo, though this is usually only needed for testing. In typical use only a single Fluid repo per
Git repo is needed. However, the Fluid repo does not need to be rooted at the root of Git repo, and code should not
assume that the root of the Fluid repo is the same as the root of a Git repo.
Better testing
There is now a test project within the repo that is a fully functional Fluid repo. There are basic unit tests that verify the
loading of the Fluid repo config and that packages are organized as expected. This is a dramatic improvement from v0
build-tools, in which all package traversal logic was effectively untested.
There are also tests for the selection and filtering APIs.
This infrastructure also provides a foundation for further test improvements, and testing other new features of Fluid
repos. In the past it was challenging to add new features because there was no way to test those features effectively.
That should be much easier now.
Known gaps

Inadequate testing of git-related APIs - can we mock git somehow?

Marking as a draft while I figure out how to split this into smaller changes.

Closing in favor of https://github.com/microsoft/FluidFramework/pull/22853


Melior unable to find LLVM/MLIR-17

when i try to use melior 0.17.0 in my project on wsl (ubuntu 20.04.6) it gives me an error saying
failed to find correct version (17.x.x) of llvm-config (found )
However, i have LLVM/MLIR-17 installed and inkwell seems to work without no problems.
llvm-config-17 command is exposed to bash and can be invoked from any path.
what am i doing wrong here?

I think it's because Ubuntu somehow puts all LLVM tools' names with a -17 suffix. This is more like an issue of https://github.com/femtomc/mlir-sys.

@ctrlv0 If you still have this issue, please post it on mlir-rs/mlir-sys!


Make the widget showcase use the current version of is.js

Right now, we use the current stable version to generate the widget showcase on our documentation website. However, for consistency and dev purposes we should use the built version of instantsearch.js (which is generated by docgen).
Bug: What is the current behavior?
If we try to use, the built version it fails with preact errors and no widget are displayed.
Bug: What is the expected behavior?
No errors and we can see all the widgets.
Bug: What browsers are impacted? Which versions?
All
Bug: What is the proposed solution?
Use the footer_script block to load the scripts after instantsearch.js and make the built version work.

Doc will be moved out of this project. Closing it.


OperationID Fixes: Account and oneClicks

Changing naming of operationIds and files for account for a smoother Autorest ingestion and consistency. I also ran these endpoints through autorest and it properly grouped the endpoints by resources as expected.
operationID changes:
account:
get_user_information -> account_get
oneClicks:
install_kubernetes -> oneClicks_install_kubernetes
list -> oneClicks_list

odd. running this branch locally gives no errors at all ...


Provide workaround for regression in AddDataProtection

TODO: Update migration docs too
This will close https://github.com/dotnet/aspnetcore/issues/38274

TODO: Update migration docs too
This will close dotnet/aspnetcore#38274

I'll take care of that in #26021


bug: Title bar overlaps with menu on iOS

Type: bug
Ionic Version: 2.x
Platform: ios 9 webview
When opening a menu then iOS status bar overlaps with the content. Desired behavior would be the same as with normal pages where additional padding on top is added automatically in order to give some space for status bar.

Hello! Thanks for opening an issue with us, we just need a little more info from you so that we can better help you with your issue. Would you mind posting a code sample, plunkr or codepen that we can use to reproduce your issue? Also, would you mind running ionic info and posting the output? Thanks again!

Hi,
Sorry for the delay, in case you haven't notices it yourself I added cropped screenshot.

Hello! Thanks for opening an issue with us! We have added this to the beta.5 milestone so you can expect this bug to be fixed once it comes out! In the meantime, as a workaround I would recommend adding margin to your menu title. Thanks again!

Confirmed this one

Thanks again for the issue! This should be fixed in the next release 2.0.0-beta.5. :smile:

Any built-in option to disable this padding? I'm working currently on a full screen application where status bar is hidden, so the padding seems odd.

Yes, in the config of your app:
@App({
  config: {
    statusbarPadding: false
  }
})

Love ya <3 thanks!


[MMCA-4365] - Address Feedback to customs-manage-authorities-frontend changes made in 4339

Description - Use of common method for application builder and remove warnings

@AdamCoops for the below test (in RemoveCheckYourAnswersControllerSpec) , the common method to create the mocks is not being used as due to some reason its failing on Dev env, hence I kept the previous mocks (setup in the test itself)
"redirect to confirmation page and use XI Eori as ownerEori when authorisedEori is XI Eori and account type is CdsDutyDefermentAccount"


Print hyperlinks

https://gist.github.com/egmontkob/eb114294efbcd5adb1944c9f3cb5feda
The list of applications supporting this is increasing, even the Windows terminal appears to support now.

This would actually be a neat feature for console. Any thoughts on this from the devs?


Release 0.12.0-m2

This is a tracker issue to synchronise issues blocking 0.12.0-m2 and PRs which shouldn’t be merged before 0.12.0-m2 is released.
This issue should be updated to depend on any blocker, and any PR which is targeted post-0.12.0-m2 should be updated to depend on this issue.
Depends on https://github.com/submariner-io/submariner/pull/1571
Depends on https://github.com/submariner-io/shipyard/pull/701

Moved to release m3 https://github.com/submariner-io/releases/issues/291


test: tweak some time based test values

Some unit tests require some time alignment
to test the right behavior.
This could cause some failures if there isn't
a reasonable tolerance on the margin of error.
Let's reduce the flakiness, increasing the
tolerance.

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes https://github.com/kubevirt/kubevirt/issues/10670
Special notes for your reviewer:

Retry manager flakyness:
https://search.ci.kubevirt.io/?search=Should+do+exponential+backoff+on+failure+retries&maxAge=336h&context=1&type=bug%2Bissue%2Bjunit&name=^pull-kubevirt-unit-test%24&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job

Migration test flakyness:
https://search.ci.kubevirt.io/?search=state+in+scheduling+state+but+timeout+not+hit&maxAge=336h&context=1&type=bug%2Bissue%2Bjunit&name=^pull-kubevirt-unit-test%24&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job

Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note:

NONE

/kind flake
/cc @dhiller @xpivarc

@fossedihelm thank you!


Unusual amount of ECIES TagCheckDecryptFailed errors on incoming connections

Describe the bug
It seems like every incoming connection I get is broken off with ECIESErrorImpl::TagCheckDecryptFailed. This happens in
the following code in decrypt_message:
https://github.com/paradigmxyz/reth/blob/3a67809cb730e63de8a37e1da6928f3a509d83b1/crates/net/ecies/src/algorithm.rs#L226-L229
Relevant example of a trace:
2023-01-03T16:56:43.645163Z TRACE net::session: new pending incoming session remote_addr=<IP_ADDRESS>:21712 session_id=SessionId(140)
2023-01-03T16:56:43.645207Z TRACE net: Incoming connection session_id=SessionId(140) remote_addr=<IP_ADDRESS>:21712
2023-01-03T16:56:43.645332Z DEBUG incoming{peer="Some(<IP_ADDRESS>:21712)"}: reth_ecies::stream: incoming ecies stream ...
2023-01-03T16:56:43.646252Z TRACE incoming{peer="Some(<IP_ADDRESS>:21712)"}:decode{peer="None" state="Auth"}: reth_ecies::codec: parsing auth
2023-01-03T16:56:43.646384Z  WARN net::session: ecies auth failed error=TagCheckDecryptFailed session_id=SessionId(140) remote_addr=<IP_ADDRESS>:21712
2023-01-03T16:56:43.646395Z  WARN net: Incoming pending session failed remote_addr=<IP_ADDRESS>:21712 error=Some(Ecies(TagCheckDecryptFailed))
2023-01-03T16:56:43.646406Z DEBUG net: Banning discovery ip=<IP_ADDRESS>

This is an example of the inputs to that function:
mac_key = 0x3ec16ddf13133bcc3bc2b07d4bde38956d68beb26b3b21277f7bf34100880999
iv = 0xa0cc193f8bb59cda4c7b6e6eaf2bdf63
encrypted_data = 0xc5071e8681b03fbdfee829caaaac456e75167510641739505d275b009aec53b1e2f5c686518dd50c20abddb515c3002cce231bcfb8689e824fe9ae40ee0d7d06ebb37a136f1aa03bd2dc28b64b46ca08515d0399b6acf403c0c1d6e9cac0c875fb5a24bf000d73bda60032373b13c92282f32128e41edd275dac921f9ffa83d99d95a3b99a4ad95a7dc955ff2c842d85250baf1469291ea9e9714f6182594bdf1f17b1450e317535d1c8e1b712fd952eb564800b3aaa6cf1dc7b03770ddc0d1e472f0ef472eccf7f31523b2abb2c8443291ead9301110278171b0e526e0b10c245ecc65039442f10243ae43556f961f12193aabd6896e986312d5928dce3b8d4f772cf0b174ef5b2db62debde00536fed3b8b954795a93f583e79d88b0b90f84d51d27c1f5fc510588e52eef36bc1979ba86b25303316c1f612521cf8dd952b4d7da4c7c16eeb699e6a6b76d123c979e323e4e9a709e90411e8c5c72dd59a4cbc1de033045830360f8127e21902151d8ab7540c5998afe5a3ddfd696fad4f19d27906070dc36f8c6c21e34b27b2636474d5f3983e9fbaa73ba72225b9c761a5aaefcef43b57af1ca40279159de00aa6da7efbc22d648879d17b24cece1
auth_data = 0x022e

Steps to reproduce
Run the node with relevant ports open to allow for incoming connections
Platform(s)
Linux (x86)
Code of Conduct

[X] I agree to follow the Code of Conduct

I think we can close this @Rjected since this appears to be due to high amount of useless peers on the network?

@mattsse yeah, going to close

This will be easier to repro locally once #1753 is in, but the basic setup would be running two reth nodes, and connecting them:
RUST_LOG=reth_ecies=trace,net::session=trace,net=trace reth node --disable-discovery --http --http.port 8545

In another shell:
LOCAL_ENODE=$(curl --location 'localhost:8545' --header 'Content-Type: application/json' --data '{ "jsonrpc":"2.0", "method":"admin_nodeInfo", "params":[], "id":1 }' | jq '.result.enode' -r)
# replace the IP in the enode if necessary
reth node --disable-discovery --trusted-peers $LOCAL_ENODE

Confirmed that this is only caused by peers connecting with a stale PeerId / pubkey, and failing the pending session on TagCheckDecrypt is the right thing to do here

I started getting this error, here is some context:
We do have incoming connection tests from both from reth and geth nodes, which pass.
The TagCheckDecryptFailed error happens here:
https://github.com/paradigmxyz/reth/blob/57a19f91f0eebeb3952a260c28412494701d4ede/crates/net/ecies/src/algorithm.rs#L234-L237
The tag is created here:
https://github.com/paradigmxyz/reth/blob/57a19f91f0eebeb3952a260c28412494701d4ede/crates/net/ecies/src/algorithm.rs#L212-L213
This check is described in the ECIES portion of the RLPx spec:
https://github.com/ethereum/devp2p/blob/master/rlpx.md#ecies-encryption

Bob verifies the authenticity of the message by checking whether d == MAC(sha256(kM), iv || c) then obtains the plaintext as m = AES(kE, iv || c).

This is a simple MAC tag check, and could fail for the following reasons:

A bug in either side's MAC or ECDH implementation
A bug in either side's ECIES handshake implementation
Incoming peer uses the wrong peer id to generate the shared secret before initiating the connection

I don't think this is still the case, so closing, feel free to re-open @mattsse / @Rjected / @gakonst if still the case

Yeah I think when encountered it has to do with bad peers and not with us.


How to build?

Can you please add a short docu how to compile this library?
Where do i get the protos, how to run buf generate etc.

There is a just file inside the repository. You can see the "buf gen" command in there :)
You may use Just, to run the command and you'll need buf installed to work with it.


Keep alive

From #16

Chromium kills the connection after some time (in both cases, I didn't get any headers or so):
  * If there was never a message (since the client is up to date) after 240s the connection gets closed:

net::ERR_EMPTY_RESPONSE

status: 0
statusText: "Unknown Error"
url: "/system/autoupdate"
ok: false
name: "HttpErrorResponse"
message: "Http failure response for /system/autoupdate: 0 Unknown Error"

* If there was a message, after 120s the connection is closed, if no new message arrived:

net::ERR_INCOMPLETE_CHUNKED_ENCODING 200 (OK)

status: 0
statusText: "Unknown Error"
url: "http://localhost:4200/system/autoupdate?change_id=135252742000"
ok: false
name: "HttpErrorResponse"
message: "Http failure response for http://localhost:4200/system/autoupdate?change_id=135252742000: 0 Unknown Error"

I'm not sure about other browsers, but I can see the reason: Since this is still a "normal" http request, it is closed, if there is no activity. See: https://tools.ietf.org/id/draft-loreto-http-bidirectional-07.html
-> We have two possibilities:
1. Send a layer-7 keep alive. E.g. a message with the key `keep-alive`, which gets discarded in the client code.

2. The client always must reopen the connection.

Solution 1 is nearer to the old behavior. Solution 2 would mean a complete rewrite of the communication stack, since it is builded upon the idea of having steady connections and an abort is something unusual. It would be nice, if you implement keep alive messages.
TL;DR:

@FinnStutzenstein
I can not reproduce this. I opened a connection in firefox and chromium and it did not break for more then 10 minutes.
The link fro ietf.org is from 2011. Can you find any newer informations about this issue or help me to reproduce it?
The solution 2 is not possible for OpenSlides4 thins it would send all requred data every 120 Seconds. If this is really a problem, then we have to send some keep alive data. Could an empty object {} work?
Before we do this, it would be nice to get the information, how often it has to be  send from a good and up-to-date source.

I still have this problem. An empty object is good IMO. Do you currently have some kind of settings? The keep-alive interval should be configurable as well are the redis host, port, OS host, port. I think env variables should be sufficient.

See #27
Could you ask around if it is possible to fix this issue on another network layer? Maybe it is possible on the tcp or http layer to send keep alive messages that are ignored by the application layer. Maybe there is a better solution in http2?

We need http/1.1 for development (otherwise you have to deal with https...). This is not tcp related (tcp KAs is not the problem here), and the http keep-alive header is for handling multiple requests through the same tcp connection. This is not the case here either. We have one request, and from the clients point of view, there is no response. I can understand, if browsers (and nginx and haproxy also have timeouts for this) close the connection, if there is no response.

@FinnStutzenstein can this be closed?


MaterialToolkitTheme ColorOverrideSource breaks CommandBar content

Current behavior
If in App.xaml there is
<utum:MaterialToolkitTheme   ColorOverrideSource="ms-appx:///Styles/ColorPaletteOverride.xaml">
the content of a CommandBar is not shown.

Expected behavior
The content is visible with the MaterialToolkitTheme.
How to reproduce it (as minimally and precisely as possible)
UnoApp1.zip
Workaround
Comment <utum:MaterialToolkitTheme ColorOverrideSource="ms-appx:///Styles/ColorPaletteOverride.xaml"> in App.xaml
Works on UWP/WinUI
None
Environment
Uno.WinUI / Uno.WinUI.WebAssembly / Uno.WinUI.Skia
NuGet package version(s)
5.2.132
Affected platforms
WebAssembly, Windows (WinAppSDK)
IDE
Visual Studio 2022
IDE version
17.10.0
Relevant plugins
No response
Anything else we need to know?
No response

Hello @DCorrBECare!
The Material styles for the CommandBar  are built for a specific usage that, at this point, has been deprecated in favor of the NavigationBar coming from Uno Toolkit. Which I see you already have a NavigationBar at the top of your page there.
Are you trying to use a CommandBar for navigation purposes or is it going to be used for something else? If you want to use CommandBar as something to drive navigation and have a page title and a back button, you can use NavigationBar for that. Otherwise, yes we will need to refactor the Material styles for CommandBar so it is consistent across all platforms.
Let me know what you use case is and we can figure it out!
Thanks!

Hi @kazo0,
I am working on the porting of an app from WinUI to the Uno Platform and in the WinUI one we used the CommandBar, that's why I was testing the control.
We will probably use the NavigationBar in our Uno app.


YouTube Brand Account not passing Watch History updates

Watching videos on MicroG YouTube Apps will not update YouTube's Watch History if the account being used is a Brand Account.
Repro: Sign in with a Brand Account on a MicroG YouTube app (I'm using YouTube Vanced, but probably try others as well), watch a video or two, and check your Watch History.
This isn't super urgent, but it's annoying if you like YouTube Vanced, Watch History, and Not Using your Real Name on YouTube™ equally. Apologies if it's a known issue, and I'm also kinda taking Vanced at their word that it's not their fault.

what keeps you from leaving YT for NewPipe?

same problem, would love a fix!

It's fixed! SInce big G is shutting down G+

@mrDodojo Why would that be related?

@MrDodojo Why would that be related?

Because the whole Brand account thing was a G+ thing

@mrDodojo Highly doubt that. If so, those accounts would be managed through Google Plus, which they are not. It's a separate thing that works with Google+, but also YouTube, Google Photos and maybe more.

@MrDodojo Highly doubt that. If so, those accounts would be managed through Google Plus, which they are not. It's a separate thing that works with Google+, but also YouTube, Google Photos and maybe more.

Tho strangely the issue got fixed on the day brand account got a YouTube ONLY feature since G+ is down   soon

Aka Google is removing the mess they created with G+

It's fixed! SInce big G is shutting down G+

Not fixed. Using latest version of MicroG Services Core and latest version of YouTube Vanced, same problem still, with same repro steps.
I even moved my channel temporarily to test that non-brand account watch history is synced properly, which it is.

Tho strangely the issue got fixed on the day brand account got a YouTube ONLY feature since G+ is down soon

Youtube has allowed you to unlink a Google+ account for quite some time, and I already had long before opening this issue.

It's fixed! SInce big G is shutting down G+

Not fixed. Using latest version of MicroG Services Core and latest version of YouTube Vanced, same problem still, with same repro steps.
I even moved my channel temporarily to test that non-brand account watch history is synced properly, which it is.

Tho strangely the issue got fixed on the day brand account got a YouTube ONLY feature since G+ is down soon

Youtube has allowed you to unlink a Google+ account for quite some time, and I already had long before opening this issue.

Their BRAND account issue is fixed. No the adblocked and other (way too complicated stuff) isn't fixed yet

Their BRAND account issue is fixed. No the adblocked and other (way too complicated stuff) isn't fixed yet

Ads are blocked just fine. This issue is that, when using MicroG Core Services, YouTube watch history is not recorded for brand accounts.
I'm not sure what issue you're talking about, but I'm glad that it's fixed. The one this thread is about still isn't.

Their BRAND account issue is fixed. No the adblocked and other (way too complicated stuff) isn't fixed yet

Ads are blocked just fine. This issue is that, when using MicroG Core Services, YouTube watch history is not recorded for brand accounts.
I'm not sure what issue you're talking about, but I'm glad that it's fixed. The one this thread is about still isn't.

Straaange.................. I'm one of the YouTube Vanced Testers, Translators and Reddit moderators and a big part of our community said history on brand accounts started working again. And I was talking about an adblocker(and or virus scanner or other modification) on your phone blocking history tracking on YouTube.

I can confirm watch history is working after the following:
Updated to new vanced version 14.10.53
Clear user data for app MicroG version 0.2.4-105

I can confirm watch history is working after the following:
Updated to new vanced version 14.10.53
Clear user data for app MicroG version 0.2.4-105

Now there are only 2 major Vanced bugs that need fixing noice

Confirmed! Thanks for steps, @Incog5.
And sorry for getting smarmy over my own misunderstanding, @MrDodojo.
Now to go complain about Chromecast support...

Now to go complain about Chromecast support...

MVP cast stuff is fixing that in the future and no I should've said that better too

@Incog5 It doesn't work with me. I have even removed and reinstalled both microG and Vanced latest version, no success

Over here it's working. Are you sure you are updated to 14.10.53?

How come the latest versions of YouTube Vanced (14.06.54 and 14.10.53) require android 4.4+? The older versions required 4.2+. My tablet is on android 4.2.1 and I cannot update my YouTube Vanced 13.37.52 to 14.x because of this :/
Works like a charm on my phone but I use my tablet exclusively for YouTube every single night. I would have loved to be able to FINALLY ditch the official app and start using Vanced but as it stands I still can't!

How come the latest versions of YouTube Vanced (14.06.54 and 14.10.53) require android 4.4+? The older versions required 4.2+. My tablet is on android 4.2.1 and I cannot update my YouTube Vanced 13.37.52 to 14.x because of this :/
Works like a charm on my phone but I use my tablet exclusively for YouTube every single night. I would have loved to be able to FINALLY ditch the official app and start using Vanced but as it stands I still can't!

youtube stopped support.

There is NewPipe Legacy that works on Android 4.1+

Oh cool, NewPipe Legacy works with YouTube accounts? I had no idea, I'll check it out tomorrow!

There is NewPipe Legacy that works on Android 4.1+

Yup, there is a chance youtube will be releasing one last api 17 version.
Sadly you can't log in in NewPipe xD

No, no account, but you can see videos and listen music without ads.

Oh, if there's no account I'm not interested. Hence why I'm using Vanced..

But still you can import subscriptions from Youtube and export to file.

And have it reflect on my actual youtube account? How about likes, watch history, playlists? Can I comment?

There are only things that are kept local on the phone, nothing that allow Google to track you, it has a different philosophy.

So it's useless to me. I'm interested in Vanced, not NewPipe. I like to unwind on the youtube app, not manage all sorts of things to have a fraction of the functionality the official youtube app or vanced already does.

So it's useless to me. I'm interested in Vanced, not NewPipe. I like to unwind on the youtube app, not manage all sorts of things to have a fraction of the functionality the official youtube app or vanced already has.

Then maybe you should start using newer software, instead of using software over 5 years old and then start complaining about all kinds of issues you may or may not have.

So it's useless to me. I'm interested in Vanced, not NewPipe. I like to unwind on the youtube app, not manage all sorts of things to have a fraction of the functionality the official youtube app or vanced already has.

Then maybe you should start using newer software, instead of using software over 5 years old and then start complaining about all kinds of issues you may or may not have.

How exactly are you posting this thinking you're being helpful? Or were you offering to buy me a new device so I can use the latest version of youtube vanced? :)

Well, there isn't a solution, it doesn't make sense to start a discussion.

Well, there isn't a solution, it doesn't make sense to start a discussion.

Then why did you do just that? I had already accepted that youtube dropped support for android 4.2 with MrDodojo's reply.

So it's useless to me. I'm interested in Vanced, not NewPipe. I like to unwind on the youtube app, not manage all sorts of things to have a fraction of the functionality the official youtube app or vanced already has.

Then maybe you should start using newer software, instead of using software over 5 years old and then start complaining about all kinds of issues you may or may not have.

How exactly are you posting this thinking you're being helpful? Or were you offering to buy me a new device so I can use the latest version of youtube vanced?  In return to that you are just complaining and saying how you are not interested in this or that. Then start spending some money, and buy a new tablet. 💃

So it's useless to me. I'm interested in Vanced, not NewPipe. I like to unwind on the youtube app, not manage all sorts of things to have a fraction of the functionality the official youtube app or vanced already has.

Then maybe you should start using newer software, instead of using software over 5 years old and then start complaining about all kinds of issues you may or may not have.

How exactly are you posting this thinking you're being helpful? Or were you offering to buy me a new device so I can use the latest version of youtube vanced?  In return to that you are just complaining and saying how you are not interested in this or that. Then start spending some money, and buy a new tablet. 💃

How in god's name do you think I'm acting like a spoiled child? I asked a simple question and got my answer. Is stating that I am not interested in newpipe what you're talking about? Please grow up.

Please grow up.

Right back at you, sir!


Detailed and More tutorials

rasa NLU version (e.g. 0.7.3):
Used backend / pipeline (mitie, spacy_sklearn, ...):
Operating system (Linux):
Recommendation/Suggestion:
Hi, First of all thank you for developing such a useful product. Your efforts are much appreciated.
However I feel that for any product to lift-off and be in the main stream, its documentation plays a vital role. It would be very helpful if you include couple of more tutorials (step by step) in using rasa_nlu tackling different scenarios. My experience so far is that a good product may fail to get mainstream due to lack of resources.
Currently there's not much if you search for rasa_nlu on stackoverflow.com, or elsewhere on search engines, I couldn't find a single tutorial and/or documentation/forums except here on github.
Thanks & regards,
Imran
Content of configuration file (if used & relevant):

Yes! totally agree. But please also see this an an invitation to contribute to the documentation and /or write blog posts / tutorials :)

@amn41
I wish if I could contribute, but this is the first time I'm trying it.
I think there should be a guide(s) explaining the project folder structure, the architecture and some tuning parameters (if applicable) . Some information on the best practices to avoid common errors would be helpful too.
P.S. I'm from java world :) and this is the first time I'm getting my hands on Python, of-course rasa is driving me into this :dango:

Hey @imraansarwar, thank you for bringing this up. Have you had a look at http://rasa-nlu.readthedocs.io/en/stable/tutorial.html ? Could you point out a few places where you loose track in the tutorial?

Let's collect some ideas about possible tutorials. I'll keep this updated :

[ ] How to setup rasa NLU using docker
[ ] Tuning parameters and evaluating a trained pipeline / model

I believe this is fixed with the Community section, hopefully, it keeps growing!


image out of box

How to fix this issue

Add a width in the theme's sass.
Here's a simple fix:

Add a width variable
Use the width variable in global setting width to img

This will all be done within the themes folder in your project root.
In the _variables.scss add the following somewhere:
// Images

$img-width: 100%;

In the _global.scss add the following somewhere:
img {
  width: $img-width;
}

Hope this helps. Though, keep in mind, it will apply to all img across the entire site. So you might wish to be more specific on what this width is being applied to.


Fail to report address sanitizer errors

One of our tests has an error but the test still shows as green.
==8529==ERROR: AddressSanitizer: unknown-crash on address 0x632000014ceb at pc 0x7fc6dd17b31a bp 0x7ffd31281aa0 sp 0x7ffd31281a90

...

Free space of 5998 is less than minimum of 6000
1577
           ✗
1578
Failures: 6

I wonder if my change to check for size at the end of the tests ended up masking the errors.

The problem was in the way we called the test script in our project, not with arduino_ci. That's a relief!


Merge to ApiGen repository

@jankal  Could you please send PR to ApiGen repository? Like this: https://github.com/ApiGen/ApiGen/pull/840
We're gonna keep it up-to-date with the ApiGen code, so people can use it.
Nice theme btw :+1:

Sent as ApiGen/ApiGen#842


update embedded links for documents moved

Signed-off-by: Kyle Den Hartog<EMAIL_ADDRESS>

Removed in place of PR #734 to move docs back to the original locations so that the links can be found by those who have already had them shared and included in documents referencing this work.


Support case insensitive tags

What version are you using?
master
What JSDoc comment were you trying to parse?
/** @Const {String} constname */
What Doctrine options were you using (sloppy, unwrap, etc.)?
{ unwrap: true }
What happened? Include output if possible.
Tag gets parsed as
{ description: '{String} constname', title: 'Const' }

What did you expect to happen?
Tag gets parsed as
{
  description: null,
  name: 'constname',
  title: 'Const',
  type: { name: 'String', type: 'NameExpression' }
}

See eslint related issues: https://github.com/eslint/eslint/issues/6121 https://github.com/eslint/eslint/issues/6145

Confirmed: JSDoc is case-insensitive. https://github.com/jsdoc3/jsdoc/issues/1046


Check key for RSA header otherwise use EC, and output fix.

Performing a check on the uploaded key looking for -----BEGIN RSA (should it be less specific like just BEGIN RSA?).
Then modify the openssl command to:

Use either rsa or ec to validate the key.
Sending standard error to standard output to catch all output (ec validation seems to send it to output error even when successful)

Finally modify the result verification by adding the string to be found on EC key validation (key valid) which is different than the one in RSA validation (key ok).

Docker Image for build 2 is available on DockerHub as jc21/nginx-proxy-manager:github-pr-666

Docker Image for build 3 is available on DockerHub as jc21/nginx-proxy-manager:github-pr-666


AddDefaultIdentity should be in the D.I. namespace

It's currently in the Identity namespace. Note that the templates already use both namespaces, so there is no need to update there.

PR is: https://github.com/aspnet/Identity/pull/1781


RSS broken in Thunderbird

It seems that since article 20200506a, <guid> in feed entry contains trailing slash.
I guess that Thunderbird uses them to navigate to articles, because it tries to open one ending with a slash.
Previous articles did not contain it and they work fine.
I don't know about other clients, but even if they work it seems weird to have this slash when <link> doesn't.

If this is an issue for the new official website's RSS feed as well (kisslinux.xyz), You should also make an issue here https://github.com/kisslinux/website -- future plans for k1sslinux.org involve the site being repurposed and this problem will be solved "a different way".


UnixPB: apt_cache update on Ubuntu s390x Install

Ref: #1444
WIP PR to keep a track of all changes needed to fix the S390x run of QEMUPlaybookCheck ( https://ci.adoptopenjdk.net/job/QEMUPlaybookCheck/ARCHITECTURE=s390x,label=vagrant/ )

https://ci.adoptopenjdk.net/job/QEMUPlaybookCheck/ARCHITECTURE=s390x,label=vagrant/42/console
It can get through the playbook now! I expected it to take more than that but apparently not.

Is this still WIP? It's not formally listed as such in github

Yep, ready for review 👍


statics.streamable.com

statics.streamable.com is a false-positive. It will not display streamable.com webpage, a low-bloat video hosting platform.

Thanks for reporting,fixed


Generated typescript is importing a non existent file

Hi! I'm using buf to generate typescript code for my connect service.
import "google/type/money.proto"; I'm using that import in my proto file, and the generated typescript  file is trying to import this file: import { Money } from "../../../../google/type/money_pb.js"; which does not exist
version: v1
plugins:
  - plugin: buf.build/protocolbuffers/go
    out: gen/go
    opt: paths=source_relative
  - plugin: buf.build/bufbuild/connect-go
    out: gen/go
    opt: paths=source_relative
  - plugin: buf.build/bufbuild/validate-go
    out: gen/go
    opt: paths=source_relative
  - plugin: buf.build/bufbuild/es
    out: gen/ts
    opt: target=ts
  - plugin: buf.build/bufbuild/connect-es
    out: gen/ts
    opt: target=ts

That's my buf gen config

Hey Juan,
I suppose you have a dependency on buf.build/googleapis/googleapis in your buf.yaml? If you run buf generate, only the code for your module is generated, not the code for your dependencies.
In Go, you don't notice this, because money.proto has the following file option:
option go_package = "google.golang.org/genproto/googleapis/type/money;money";

When protoc-gen-go generates a proto file that imports money.proto, the import is redirected to this Go package, which is a precompiled version of googleapis.
There is no file option for a JS package, and there is no precompiled version of googleapis for protobuf-es either, so protoc-gen-es generates an import to a local file, just like any other regular import. The only exception are the well-known types, which are ship with every protobuf compiler.
To generate a module and dependencies, you can use buf generate --include-imports. The buf CLI currently does not have an option to specify this behaviour per plugin, so you will have to split your buf.gen.yaml into two files, one for Go, one for TypeScript, and generate the latter with the --include-imports flag.
See also the related report https://github.com/bufbuild/connect-es/issues/262, and https://github.com/bufbuild/buf/issues/1407, which was opened to improve the behavior.
I'm going to close this issue because I don't see any reasonable way for protobuf-es to improve the experience, but I'll raise it again with the team. Thank you for opening the issue!

There are several options to generate select parts, but in general, I think that it is desirable to avoid maintaining filters, and keep the generate commands as simple as possible.

@timostamm thanks!

Would it make sense to have an option, in the protobuf-es / connect-es plugin, to specify "module path prefix". This could be either directory, or a package. If you specify a package, e.g. "@acme/protobuf", then the generated code would contain import ... from<EMAIL_ADDRESS>instead of e.g. import ... from '../../acme/protobuf/foo.proto.
This would allow users to split modules into npm packages.


Convert some inline styles to CSS custom properties

Simply converts a handful of hard-coded CSS values to custom properties, so that they can be overridden by the consuming context as needed.

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


Add a way to delete color input fields

Describe the solution you'd like
A small close button in the top right corner of each input field that deletes it. This may require moving the circular color swatch slightly to accommodate the button

I would like to work on this issue.

My approach to this problem
We can create a delete icon button on the top right corner of the text field. And if the user click that button we will simply remove that index from our color array

My approach to this problem We can create a delete icon button on the top right corner of the text field. And if the user click that button we will simply remove that index from our color array

Sounds good, that's how I was thinking to approach it too. I've installed react icons in the project so you can add the icon from there.
However, it should probably not be possible to delete the first 2 inputs.

Okay thanks for clarifying.


Add TorchHub tests to torchvision

Drop-in replacement for PyTorch Hub tests.
I only modified a few things:

assertObjectIn -> assertIn
SUM_OF_PRETRAINED_RESNET18_PARAMS = -12703.992365 -> -12703.99609375

Codecov Report

Merging #1319 into master will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1319      +/-   ##
==========================================
+ Coverage   65.52%   65.53%   +0.01%
==========================================
  Files          75       75
  Lines        5821     5821
  Branches      892      892
==========================================
+ Hits         3814     3815       +1
+ Misses       1738     1737       -1
  Partials      269      269

Impacted Files
Coverage Δ

torchvision/transforms/transforms.py
80.39% <0%> (ø)
:arrow_up:

torchvision/transforms/functional.py
71.26% <0%> (+0.28%)
: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 5d5d425...d762d7a. Read the comment docs.


Allow for functions when overriding default validator messages

When overriding default validator messages it should be possible to use functions :
_.extend(Backbone.Validation.messages, {
  required: -> I18n.t('activerecord.errors.messages.blank')
})

similar to how it's done for validator message inside the model. Without this fix we're getting error :
Uncaught TypeError: Object function () { ...} has no method 'replace'

I imagine this would require some more thought for error messages all around. If the default error messages can be functions but custom messages (included on validator configuration or returned from custom validator functions) are generally not expected to be functions... At the very least, I think any msg configuration properties should also support this.
Also, I don't see any unit tests.
I'm not a project collaborator, but if I were, those would be my reasons for not merging the pull request. If I were you, I would get ahead of the eventual discussion by at least adding unit tests for your changes. (You could test that the _.result bits work by using _.constant in your tests, instead of actually trying to make the I18n library work in the unit tests.)


fix to rabbitmq

personal spaces would crash an upload
images now pushed to ghcr.io

Review Time Estimate

[X] Immediately
[ ] Within one week
[ ] When possible

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My change requires a change to the documentation.
[x] I have updated the CHANGELOG.md.
[ ] I have signed the CLA
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

would like to get 2 more things fixed

no parameters for extractor in submission page throws error in console.
error when receiving message from extractor in rabbitmq plugin.

[ERROR] [11/06/2020 04:08:47.270] [application-akka.actor.default-dispatcher-3] [akka://application/user/EventFilter] JsResultException(errors:List((,List(ValidationError(error.expected.jsstring,WrappedArray())))))
 play.api.libs.json.JsResultException: JsResultException(errors:List((,List(ValidationError(error.expected.jsstring,WrappedArray())))))
 at play.api.libs.json.JsValue$$anonfun$2.apply(JsValue.scala:64)
 at play.api.libs.json.JsValue$$anonfun$2.apply(JsValue.scala:64)
 at play.api.libs.json.JsResult$class.fold(JsResult.scala:71)
 at play.api.libs.json.JsError.fold(JsResult.scala:10)
 at play.api.libs.json.JsValue$class.as(JsValue.scala:62)
 at play.api.libs.json.JsUndefined.as(JsValue.scala:94)
 at services.EventFilter$$anonfun$receive$3.applyOrElse(RabbitmqPlugin.scala:1208)
 at akka.actor.ActorCell.receiveMessage(ActorCell.scala:498)
 at akka.actor.ActorCell.invoke(ActorCell.scala:456)
 at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:237)
 at akka.dispatch.Mailbox.run(Mailbox.scala:219)
 at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(AbstractDispatcher.scala:386)
 at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
 at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
 at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
 at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)

need to check this on an empty space that has never had extractors enabled in it.


Export Metaflow Runs into Tar File.

I wanted to make a feature request. I am using a Service-based Metadata provider and S3 datastore. Now after running quite a few ML experiments, All my models are easily accessible when I want to showcase them to someone using the Metaflow.
I wanted a way to export the Flows into a tar file so I can provide them to someone else. As Metaflow is self-contained, the exported tar file should ideally replicate a local datastore/metadata setup in file structure. And hence when untared into .metaflow folder anyone else can view the results of my Flow.
The reason I want this because a lot of people I know don't have AWS. If we can export flow to a tar file, The only thing the other person needs to investigate my flow is Metaflow and my dependencies.

Additional context: https://gitter.im/metaflow_org/community?at=5e79a3478fc8ea15af725280