Invalid Schnorr Siganture - Example: Basic spend using key-path

I have a method to send sats from one p2tr address to another one. I followed this example to implement it.
The validation goes through, but when I submit the transaction to mempool.space (or blockstream, same thing), I get the following response:
sendrawtransaction RPC error: {"code":-26,"message":"non-mandatory-script-verify-flag (Invalid Schnorr signature)"}
Here is the code I send sats with (essentially the same as the example, but with many UTXOs in tx input):
https://pastebin.com/hBGXNnJe

Here is the decoded TX that fails to be broadcast:
{
  version: 2,
  vin: [
    {
      txid: 'fd13e6e779960e0ba56405928524d1077575568a58b8e123275f11cb8630a816',
      vout: 0,
      scriptSig: [],
      sequence: 'fffffffd',
      witness: [Array]
    }
  ],
  vout: [
    {
      value: 1000n,
      scriptPubKey: '5120b32ce90751de8b076dc9c8f6d46f967abe6cc7a4e97c452ff17444bb60c5890b'
    }
  ],
  locktime: 0
}

I think the problem may be here with txInput.vout:
Signer.taproot.sign(taprootPk, txData, txInput.vout)

The index value should be the index of the input being signed, so like this:
for (let i = 0; i < txData.vin.length; i++) {
      txData.vin[i].witness = [
        Signer.taproot.sign(taprootPk, txData, i),
      ];
    }

Try that change and let me know if it works.
p.s the n notes a BigInt type. They are a relatively new type in javascript.

@cmdruid thanks, fixed this one! But the error is still there, unfortunately :( something else is also wrong

Where are you getting the keys from?
You may want to try skipping this part:
const [taprootPk] = Tap.getSecKey(pk);
const [taprootPub] = Tap.getPubKey(pub);

This step adds an empty tweak to each key in your key-pair, which obfuscates the keys for privacy.
However it is not necessary and not all wallets bother to do this step, so you may want to try omitting it and signing with the keys you have directly.

@cmdruid I tried skipping tweaking, but no luck, same error.
I generate the keys myself, then tweak them, then give the taproot address to the user.
Then somewhere in the future the user funds the taproot address and I do this sending method (I invoke it with not tweaked private key and the method tweaks the key inside it, so that it has access to the taproot address the user has funded).
Also, so that you don't have to waste time, while trying to guess what's wrong, I created this minimal example with all the method inputs, how I generate the keys etc., before I invoke the method:
https://pastebin.com/qH73NDqC#google_vignette

Do you end up getting the same tweaked key-pair in both cases? Does the tweaked public key, when encoded as an address, match the address of the utxo being spent?

@cmdruid Yes, the same tweaked key-pair in both cases 😢
UTXO address matches as well, yes, I re-verify UTXO data for the address being spent doing this request:
GET https://blockstream.info/testnet/api/address/tb1pxez9u8zkzhgephpus2a3fuz7jujhpeujml32a5d4g57aj9wjdqrqh02yen/utxo

What does Signer.taproot.verify(txData, i) not check during verification? I know UTXOs could be one thing, but those are correct, what else could it miss?
Maybe it will be easier for me to debug, if I at least know what could be wrong.

@cmdruid I also can reproduce this error in keyspend.test.ts.
I just removed the wallet stuff, as I don't have a local node.
Then I put my private key there, my UTXO input data/output data and set the network to 'testnet'.
Then, after running the test (it runs successfully), I took the TX hex and posted it to the blockstream node like this:
curl --request POST
--url https://blockstream.info/testnet/api/tx
--header 'Content-Type: text/plain'
--header 'User-Agent: insomnia/9.3.2'
--data<PHONE_NUMBER>01010449081422de6fda2d995662ab51909a3a45bf422bcf47b40af047c94d467b360000000000fdffffff015203000000000000160014d0829aa329e5716e71b10cb17a6a33df8caf72a3014095df63eff8710b308c2f69b693cf7db731cd320c0789d5fad412a1911d1105e243efbd39d2d74cfd3dd0b9fe6b8e1e5387b92b61364c4d664b609441b984d2a000000000

The pubkey that I am decoding from the address "tb1pxez9u8zkzhgephpus2a3fuz7jujhpeujml32a5d4g57aj9wjdqrqh02yen" is the following:
36445e1c5615d190dc3c82bb14f05e972570e792dfe2aed1b5453dd915d26806
Are you signing with a private key that matches this public key?

@cmdruid
Secret: c8ec44f2fd52560af4aaab3210c104d18cf5904c75288d182124c2905da69102
You can import into Unisat Testnet to see for yourself. Address is derived from public and you'll see the correct address there.
Just try this test and see for yourself:
https://pastebin.com/raw/vhn2YJvt
You'll see all the correct keys in the test, the UTXO used here is also correct. And the test will pass, of course.
But then, use the TX Hex and submit it to blockstream (or mempool.space). The BTC node will reject it.
Submission request:
curl --request POST
--url https://blockstream.info/testnet/api/tx
--header 'Content-Type: text/plain'
--data

@cmdruid okay, I realized my error, incorrect value was inputted into prevout.
Sorry for disturbing :)

no problem. I'm glad that you were able to get it working!


Correct Manta issue

Error is:

Reference fasta and 'Normal' BAM/CRAM file conflict on chromosome: 'hs37d5'

using:
mantaRef = '/sw/data/uppnex/ToolBox/ReferenceAssemblies/hg38make/bundle/2.8/b37/MANTA_human_g1k_v37_decoy.fasta'
mantaIndex = '/sw/data/uppnex/ToolBox/ReferenceAssemblies/hg38make/bundle/2.8/b37/MANTA_human_g1k_v37_decoy.fasta.fai'

and the Downsampled data

Dynamic exception type: N5boost16exception_detail10clone_implIN8illumina6common14LogicExceptionEEE
std::exception::what: SVbreakend has unknown or invalid chromosome id in candidate sv.
        local_bam_record: D0ENMACXX111207:1:2104:3567:112276/2 tid:pos:strand 1:162136647:- cigar: 21S80M mate_tid:pos:strand 85:20824988:+
        remote_bam record: NONE
        SVCandidate: SVCandidate:
        isImprecise?: 1
        fwReads: 0 ; rvReads: 0
        index candidate:assemblyAlign:assemblySegment: 0:0:0
        Breakend: GenomeInterval: 1:[162136454,162136647) LEFT_OPEN
        SVBreakendLowResEvidence: pair: 0 local_pair: 1 cigar: 0 softclip: 0 semialign: 0 shadow: 0 split_align: 0 unknown: 0

        Breakend: GenomeInterval: 85:[20825089,20825282) RIGHT_OPEN
        SVBreakendLowResEvidence: pair: 0 local_pair: 0 cigar: 0 softclip: 0 semialign: 0 shadow: 0 split_align: 0 unknown: 0

: SVbreakend has unknown or invalid chromosome id in candidate sv.
        local_bam_record: D0ENMACXX111207:1:2104:3567:112276/2 tid:pos:strand 1:162136647:- cigar: 21S80M mate_tid:pos:strand 85:20824988:+
        remote_bam record: NONE
        SVCandidate: SVCandidate:
        isImprecise?: 1
        fwReads: 0 ; rvReads: 0
        index candidate:assemblyAlign:assemblySegment: 0:0:0
        Breakend: GenomeInterval: 1:[162136454,162136647) LEFT_OPEN
        SVBreakendLowResEvidence: pair: 0 local_pair: 1 cigar: 0 softclip: 0 semialign: 0 shadow: 0 split_align: 0 unknown: 0

        Breakend: GenomeInterval: 85:[20825089,20825282) RIGHT_OPEN
        SVBreakendLowResEvidence: pair: 0 local_pair: 0 cigar: 0 softclip: 0 semialign: 0 shadow: 0 split_align: 0 unknown: 0

Seems NC_007605 was left in the Manta reference. Deleted now, will start a new test.

Seems now works on bianca, @malinlarsson could you please eventually check on milou, or shall I check first?

It works on both milou and bianca: all we have to do is to leave the reference as it is, and do not remove the decoys - easier to simply filter out false calls laters, since manta runtime is about 2-3 hours only.


Design title/heading props to avoid usage of html attribute names

Feature Request
Description
In action header and section header we use title as a prop name. We've decided before we want to avoid using HTML attributes unless the prop maps directly to the attribute.
Let's sync up and figure out how we want to rename this prop along with prop APIs for all the other headers.
cc/ @neilpfeiffer @tbiethman

Here is a design being used in data-grid:
<SectionHeader
  text="Default Text"
  startAccessory={
Start
}
  endAccessory={
End
}
  component={<CustomComponent />}
/>

<ToggleSectionHeader
  text="Default Text"
  startAccessory={
Start
}
  endAccessory={
End
}
  component={<CustomComponent />}
>
Children would display when toggled
</ToggleSectionHeader>

Discussed dropping component prop until use-case comes up.
@neilpfeiffer is going to talk with UX team and see if there is a use case where the content in the header would need to change on toggle.


Provide doc and/or script to circumvent golang.org blockage in China

As reported in coderzh/gohugo.org#1 by a friend of mine in China, go get -v github.com/spf13/hugo fails to complete because golang.org, hence golang.org/x/text/transform and golang.org/x/text/unicode/norm used in hugo/helpers/path.go, are blocked in China.  (Why?  Beats me.  Perhaps it is because golang.org is hosted on Google servers, and most Google servers are blocked in China nowadays?)
Using an overseas VPN is a way to circumvent the blockage, but thankfully, there is another way for Chinese netizens who do not have access to an overseas VPN, as suggested by Lars Seipel:

mkdir -p $GOPATH/src/golang.org/x
git clone https://github.com/golang/net $GOPATH/src/golang.org/x/net

Repeat the latter for all x repos. Do this once when setting up a new
machine for Go development, then just git pull for updates. It's maybe
not as nice as 'go get' but at least you don't need to change import
paths in other packages depending on the x repos.

(from http://grokbase.com/t/gg/golang-nuts/152cgxd8jh/go-nuts-golang-org-is-blocked-in-china)
And the good news?  My friend from China tested it and reported: "This method works; a very good solution indeed."
So yes, this is a note-to-self to follow up by documenting it and probably writing a small bash script and/or MS-DOS / Windows batch file to automate the whole process, both the initial fetch and subsequent updating.
Cheers,
Anthony

Note/Update: This issue is marked as stale, and I may have said something earlier about "opening a thread on the discussion forum". Please don't.
If this is a bug and you can still reproduce this error on the latest release or the master branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, and you feel that it is still relevant and valuable, please tell us why.


CLI Command: dotnet ef fails to run on Windows 7

OS: Windows 7 Enterprise (Version 6.1 Build 7601)
dotnet --version: 1.0.0-rc2-002678
Microsoft.EntityFrameworkCore.Tools: 1.0.0-rc2-20828
Running dotnet ef fails with
System.IO.FileNotFoundException: Could not load file or assembly 'System, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e, Retargetable=Yes' or one of its dependencies. The system cannot find the file specified.
File name: 'System, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e, Retargetable=Yes'
   at Microsoft.DotNet.ProjectModel.ProjectReader.ReadProject(Stream stream, String projectName, String projectPath, ProjectReaderSettings settings)
   at Microsoft.DotNet.ProjectModel.ProjectReader.GetProject(String projectPath, ProjectReaderSettings settings)
   at Microsoft.EntityFrameworkCore.Tools.DispatchCommand.<>c__DisplayClass2_0.<Create>b__0()
   at Microsoft.Extensions.CommandLineUtils.CommandLineApplication.Execute(String[] args)
   at Microsoft.EntityFrameworkCore.Tools.Program.Main(String[] args)
Could not load file or assembly 'System, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e, Retargetable=Yes' or one of its dependencies. The system cannot find the file specified.

This indicates something has the wrong import. However the same app works fine on Windows 10, CentOS 7.1, Ubuntu 14.04
Repo: https://github.com/pranavkm/ef-migration

Also on OSX El Capitan. I believe this might be a bug in how Microsoft.NETCore.App is created.

cc @davidfowl \ @ericstj

Maybe related to https://github.com/dotnet/cli/issues/2926#issuecomment-217745629?

Apparently the CLI doesn't regenerate the lock file for tools when the project.json changes. I'll file a bug for this, but this should unblock testing on Win7.


Replace 'zapcore.Level' with more general 'zapcore.LevelEnabler'.

This PR implements and closes #22.

could you please add test to cover use case with level enabler?

could you please add test to cover use case with level enabler?

Sure! I added a test that illustrates that the log level can be changed after creation of the otlpCore instance.

Thanks for fixing slog test!

@jenshans sorry, missed your message.
You can use git-hash from main branch.
also, just released:
https://github.com/agoda-com/opentelemetry-go/releases/tag/otelzap%2Fv0.2.4
Thanks for heads-up


User register - All users

Registrations works, if UI changes are required reopen

closing

First name and last name are required. Check the user model in the backend.

fixed in 8d6c3fb](https://github.com/La-Fresca/la-fresca-frontend/commit/8d6c3fbd020d387102346c00b913d7a18ce8f9e5). reopen if neccesary


Not getting clang completion immediately

Hi,
I am using this plugin for C/C++ programming and I think it is great, especially for the parameters placeholders that avoid the sometimes annoying switches between tabs to have a look at man.
However, I noticed that the translation is not immediate/automatic: let's say I want to type mmap (includes are there already). What happens is that I don't get the clang completion immediately but I have to type a space in the middle of the word then go back and continue typing. Only now the clang completion appears. This is quite annoying since I would like to get the completion in realtime.
Anyone having the same issue?
Currently using nvim 0.2.0, clang 4.0 (tested also with 3.4.2 and seen the same behavior) and latest deoplete and deoplete-clang2 sources.
My init.vim
let g:deoplete#enable_at_startup = 1
let g:deoplete#sources#clang#sort_algo = 'priority'
set completeopt-=preview

Thanks,
Christian

same issue here, any update?

Same Issue, on  Fedora 26

same issue:
Ubuntu 16.04
NVIM v0.2.3-dev
clang version 3.8.0-2

Hi, I am deoplete author.
I have reproduced the problem.
But you can configure it manually.
call deoplete#custom#set('clang2', 'min_pattern_length', 2)

Any fix for this issue? Using Arch linux with nvim 0.2.3, clang 6.0.0, latest deoplete & deoplete-clang2 (installed with vim-plug)
I'm getting the same problem as OP. I don't immediately get completion from clang when I start typing a word. I've tried a few different configurations.
Here's my default:
" deoplete
let g:deoplete#enable_at_startup = 1
" deoplete-clang
let g:deoplete#sources#clang#autofill_neomake = 1
let g:deoplete#sources#clang#executable = '/usr/bin/clang'
let g:deoplete#sources#clang#clang_header = '/usr/lib/clang/6.0.0/include'

With the default config, clang completion only appears after typing 'space BS' or typing '.' or '->' . Member/struct completion works however.
When I test this with struct point {int x; int y;} point1;, as I start to type point1, no clang completion shows. When I type point1. it successfully shows point1's members as options.
When I add
call deoplete#custom#source('clang2', 'min_pattern_length', 2)
Testing the same structure, as I start to type point1, clang completion shows point1 as an option. But now when I type point1., there are no members shown as options anymore. I might look through the source for anything obvious but I'm not quite sure how to debug a plugin.

You can use deoplete-clangx instead.
https://github.com/Shougo/deoplete-clangx


[anaconda]-auto install vuln pkgs from conda / pip

Dev container name:

Anaconda

Description:
This PR adds the following functionality :

Auto install vulnerable packages from conda channel / pip pkg managers

@gauravsaini04 @samruddhikhandale @Stam098c @eljog


Move form help text into legend

This is an alternative solution to #485.
What problem does the pull request solve?
Most groups of checkboxes and radio buttons within Elements have an additional introductory help text which isn't a hint. It's usually there to help less technical people understand that you can select multiple checkboxes, but can also be used for other purposes.
This moves that text into the legend to also make it accessible to assistive technologies like screen readers. The styling is nearly the same as before and adds a class to the current paragraph declaration to re-use its styling.
There is a bit more spacing above the help text in the new version (probably 0.26316em which translates to 5px with default settings), even though it uses the same CSS. That is because previously the margins were collapsing as the p came directly after the h3 and now they aren't anymore because the text has been moved into the legend. I'm not sure if it's worth fixing as spacing within Elements is quite inconsistent and it doesn't look wrong.
Let me know if you think I should do something about it.
How has this been tested?
I've tested in multiple browsers via BrowserStack.
Screenshots
Before

After

Differences

What type of change is it?

Bug fix (non-breaking change which fixes an issue)

I have added some documentation (as suggested by @gemmaleigh on #485), changed the "hack" to use overflow:hidden instead (as suggested by @igloosi) and re-tested in a couple of browsers.

This looks good, thanks @selfthinker and @igloosi 👍


Feat/collections

can you add some description about this commit?

About this PR, you mean? @TheCodeTalker


Instagram - no videos

The Instagram bridge doesn't include videos.
For example, I generate a RSS feed for https://www.instagram.com/kimkardashian. The RSS item for this post (which contains a video): https://www.instagram.com/p/B5A8gRKA_zH looks like that:

only pictures...
Is it the expected behavior?

Support for embedded videos was added via #1361


Remove $50 minimum for Thorchain Swaps into ETH mainnet

Overview
We previously made trades into ETH mainnet have a $50 minimum to avoid failures on Thorchain, but now that we've completed https://github.com/shapeshift/lib/issues/1050, we should be able to remove the hard-coded minimum, in favor of proper estimations.
References and additional details
The minimum trade amount is at least the outbound_fee that the node/midgard reports
Acceptance Criteria
As a user I should be able to swap via Thorchain without a hard coded $50 minimum
Need By Date
No response
Screenshots/Mockups
No response
Estimated effort
No response

@DiggyDiggy2 turns out I already did this in https://github.com/shapeshift/lib/pull/1080
We are good here 👌


'self' as pseudo-identifier in resource paths

Please check if the PR https://github.com/zalando/restful-api-guidelines/pull/603 introduces changes which are relevant to the Zally project.

We need to add self as exception for the pluralization rules.
May be also check whether other regular expression patterns for path rules need to be adapted.


Added code snippets, other content edits

Something went wrong with PR preview build please check

Preview is available here:http://developers-pr24.previews.kube001.services.stellar-ops.com/docs


Update 3-hpa-http-requests.yaml : Fixing metrics name to http_requests_per_second

Fixing metrics name to http_requests_per_second

sorry, don't get notifications, need to fix that. Is there any other references to this metric that need to be updated? or I can merge?


feat(cli): add platform information on DIContext

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

v5.2.0
GitHub release

Your semantic-release bot :package::rocket:


Template literal index does not transform the key and value types.

Bug Report
I have a data store that uses prefixes to store different types of data.  One of the types is "preferences".
data = {
  "preferences.a": string,
  "preferences.b": number
}

I have a getter interface for preferences that allows the user to query without the prefix:
type PreferencesSchema = {
  a: string,
  b: number
}
function getPreference<KeyT extends keyof PreferencesSchema>(key: KeyT): PreferencesSchema[KeyT] {
  return data[`preferences.${key}`];
}

Unfortunately, this gives an error, because TS looks for a and b on the data instead of the actual indexes preferences.a and preferences.b.  I understand template literal types are relatively new, but I think in this case, the compiler should see that the prefixed keys are being used and that the associated values are the same as the value types in the preference schema.
I found a similar looking issue: https://github.com/microsoft/TypeScript/issues/13948, but I don't think this error can be attributed to type-widening.
🔎 Search Terms
template literal missing properties
🕗 Version & Regression Information

This changed between versions 4.3.5 and 4.4.4 (4.3.5 still gives a noImplicitAny error, but the introduction of template literal types makes this issue arise even without strict checks)

⏯ Playground Link
Playground link with relevant code
💻 Code
type PreferencesSchema = {
  a: string,
  b: number
}

interface DataSchema {
  "preferences.a": string,
  "preferences.b": number
}

const data: DataSchema = {
  "preferences.a": "hello world",
  "preferences.b": 12345
}

// the issue
function getPreference<KeyT extends keyof PreferencesSchema>(key: KeyT): PreferencesSchema[KeyT] {
  return data[`preferences.${key}`];
}

// workaround
function workingGetPreference<KeyT extends keyof PreferencesSchema>(key: KeyT): DataSchema[`preferences.${KeyT}`] {
  return data[`preferences.${key}`];
}

🙁 Actual behavior
An error occurs:
Type 'DataSchema[`preferences.${KeyT}`]' is not assignable to type 'PreferencesSchema[KeyT]'.
  Type 'DataSchema' is missing the following properties from type 'PreferencesSchema': a, b

🙂 Expected behavior
TypeScript should recognize that preferences.a/preferences.b is being used as an index, not a/b.  Therefore it shouldn't matter that DataSchema is missing a and b as properties.

I think the error message is misleading.  Looks like the compiler can't see that DataSchema[`preferences.${K}`] and PreferencesSchema[K] are the same type.  It reports the failure in the mechanism available for comparing two generic indexed access types, which is presumably comparing both the object types and the key types.
As evidence that the compiler is definitely able to recognize that you are indexing into DataSchema with keyof DataSchema, note that there is no such error for a non-generic version of your function:
function getPreferenceNonGeneric(key: keyof PreferencesSchema): PreferencesSchema[keyof PreferencesSchema] {
  return data[`preferences.${key}`]; // okay
}

So the problem is the abstract relationship between T[K] and {[P in keyof T as F<P>]: T[P]}[F<K>] for generic K.
It seems like this is related to #30581, but I can't see a reasonable way to make the fix in #47109 help here.

This is broken in the same way in 4.3 if you add an as const
   return data[`preferences.${key}` as const];

The error message is indeed super wrong. It seems like we're trying to relate T[K] to U[K] via the relationship between T and U but there's just no reason to do that.

So the reported error here comes from this check and this check doesn't have a chance to be satisfied here:
https://github.dev/microsoft/TypeScript/blob/1071240907ab7aae63ecc9c0bbde42aa51dc7669/src/compiler/checker.ts#L19410-L19416
This is not the only check that is performed here because if this fails then the constraint-based fallback is used~:
https://github.dev/microsoft/TypeScript/blob/1071240907ab7aae63ecc9c0bbde42aa51dc7669/src/compiler/checker.ts#L19440
This check doesn't succeed either because the computed constraint is never and that creates an error like this:
Type 'DataSchema[`preferences.${KeyT}`]' is not assignable to type 'PreferencesSchema[KeyT]'.
  Type 'DataSchema[`preferences.${KeyT}`]' is not assignable to type 'never'.
    Type 'string | number' is not assignable to type 'never'.
      Type 'string' is not assignable to type 'never'.

There is some heuristic in place that makes the first error to be displayed here - but this somewhat doesn't matter as the second one is almost as confusing as the first one :p
https://github.dev/microsoft/TypeScript/blob/1071240907ab7aae63ecc9c0bbde42aa51dc7669/src/compiler/checker.ts#L19445
So... how this potentially could be fixed? I think that instead of checking isRelatedTo(source.objectType, target.objectType) and isRelatedTo(source.indexType, target.indexType) we should actually check this property value by property value with instantiated indexTypes, using all possible permutations of the involved type arguments (received from the base constraints of those indexTypes). I'm not entirely sure if this logic could just replace the existing logic but I don't see why it couldn't

This is working as intended. What's missing in the example is the presence of a mapped type to demonstrate the relationship between PreferencesSchema and DataSchema. Once you add that it works as intended due to #47109:
type PreferencesSchema = {
  a: string,
  b: number,
}

type DataSchema<T> = { [P in keyof T as `preferences.${P & string}`]: T[P] }

const data: DataSchema<PreferencesSchema> = {
  "preferences.a": "hello world",
  "preferences.b": 12345
}

function getPreference<K extends keyof PreferencesSchema>(key: K) {
  return data[`preferences.${key}`];
}

@ahejlsberg how the demonstrated relationship helps conceptually cases like this? type of data is concrete~ and it shouldn't matter if it's being computed using a reference to PreferencesSchema or not. I mean - DataSchema<PreferencesSchema> should work exactly the same as the "inlined" version that is present in the repro.
I also think that your example is closer to the presented workaround (workingGetPreference in the repro) - it just doesn't declare the return type. Once we annotate the return type to your snippet then we end up with almost the same error as in the repro case:
type PreferencesSchema = {
  a: string,
  b: number,
}

type DataSchema<T> = { [P in keyof T as `preferences.${P & string}`]: T[P] }

const data: DataSchema<PreferencesSchema> = {
  "preferences.a": "hello world",
  "preferences.b": 12345
}

function getPreference<K extends keyof PreferencesSchema>(key: K): PreferencesSchema[K] {
  // Type 'DataSchema<PreferencesSchema>[`preferences.${K}`]' is not assignable to type 'PreferencesSchema[K]'.
  //   Type 'DataSchema<PreferencesSchema>' is missing the following properties from type 'PreferencesSchema': a, b
  return data[`preferences.${key}`];
}

TS playground

Hmm, I missed that the type annotation is using an indexed access on the original type instead of the mapped type. I think it is bit of a stretch to expect that to type check. Specifically, given non-generic object types A and B, a generic type K extends keyof A, you are expecting that an indexed access B[M<K>] be assignable to A[K], where M is some higher-order mapping. In order for that to type check, we'd have to prove that M is an isomorphic (i.e. reversible) mapping, and that keyof A is a subtype of M<keyof B>, and for each property P in keyof B, B[M<K>] is assignable to A[K]. It's probably possible to do this, but I'm not sure the complexity is worth it. Seems to me the example I give above is satisfactory. In particular since, with the mapped type, you're not repeating yourself in two types.

Ye, I see how it gets pretty gnarly for the compiler - from the user's perspective it isn't that obvious that this might be the limitation (in such cases it usually isn't obvious because we, users, have no idea how the compiler works under the hood) and the reported error is quite confusing. Perhaps at least this error could be improved?

Seems to me the example I give above is satisfactory. In particular since, with the mapped type, you're not repeating yourself in two types.

Right, this is a good example of how to make the relationship more explicit and "sync" both of those schema types over time.

Hm, should the bot close after 3 days since the last comment? That seems to be... pretty fast 😬


Videos longer than a minute?

Is there a way to get recordings longer than a minute?
My intention is to send the video by telegram and sending it in parts is horrible.
Thank you for the work done 👌

Video recording is made by a yi process.
Sorry but I can't change it.

It's a shame... 😢


custom backgrounds for modcore?

Why not lol it will be cool

wdym?  Like the menu background is an asset that already exists so you can include it in a modcore mod and it'll replace during the loading of the game.

ohhh.  Yeah as far as I'm aware that's being worked on.  They just need to make an implementation for the stages to be loaded through json

extra keys fnf has this thing


Automated build and release

Steam Deck's read-only root partition and misconfigured repositories makes getting the build environment for this library rather difficult. This PR adds a github actions file that will automatically build and upload the library whenever a new release is published or on-demand, so that Steam Deck users can skip that step.

This is great, thank you!


fix(repo): stop trimming whitespace of inputs

:pencil: Description

Inputs such as delimiter are unable to be parsed due to trimWhitespace defaulting to true. I don't imagine enforcing no whitespace should be an issue for any helper.

:tada: This PR is included in version 1.45.9 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


1.7.32: Why impose max sizes for field types? Admin fails on large content sizes.

In Grav 1.7.32, in commit 3e7f67f, max sizes for field types have been imposed.
According the CHANGELOG:

Set default maximum length for text fields

password: 256
email: 320
text, url, hidden, commalist: 2048
text (multiline), textarea: 65536

Why have these limits been imposed? Grav seems to be working fine when pages have content larger then 65536. A page with size 86691 (500 lorum ipsum paragraphs) is working just fine. But when saving a large page in Admin, an error is thrown after Grav core validates the page's content.
This has lead to issues when users create pages with long content using Admin.

Github Admin: Limitation of large .md failing to save in admin (unless in expert mode) #2308
Discourse: Invalid input in “Content” Failed to save entry: Form validation failed, please check your input]

Can we get an update on this?
I'm working on a markdown table listing, it has "only" 280 rows (forced by updating the file directly) and 11 columns and it already broke at the 172 rows. I need to have  almost 10 times that number.
This is really too limiting to need to directly change files when the admin should suffice


Use of 'yyyy' instead of 'YYYY' breaking the component

Describe the bug
As soon as a date is set to the component it breaks, throwning the error

Use of 'yyyy' instead of 'YYYY' for formatting years

To Reproduce
this.state = {
    startDate: new Date(),
}
<Datepicker
              id="input-start-date"
              selected={startDate}
              onChange={e => this.handleStartDate(e)}
              dateFormat="d MMM, YYYY h:mm aa"
/>

Additional context
I've seen people were having a similar issue, but as I've updated it and the problem still happening to me I decided to open this issue.
"react-datepicker": "^2.11.0",
"date-fns": "^2.9.0",

I've downgraded to the version 2.3 and It's working. Reopening in case anyone has the same problem and find a solution for the problem.

how did intergrate the css for react datepicker??


Iss60 utilfunctions

Thank you for submitting your PR. Please read the template below, fill it out as appropriate, and make additional changes to your code as needed. Please feel free to submit your PR even if it doesn't satisfy all of the requirements below - simply prepend [WIP] to the PR title until it is ready for review by a maintainer. If you need assistance or review from a maintainer, add the label Status: Help Needed or Status: Review Needed respectively. After review, a maintainer will add the label Status: Revision Needed if further work is required for the PR to be merged.
Description
Please include a summary of the change and which issue is resolved. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected - these changes will not be merged until major releases!)
[ ] This change requires a documentation update - describe below.

How Has This Been Tested?
Please describe tests that you added to the pytest codebase (if applicable).
Checklist:

[x] My PR has a descriptive title
[x] My code follows PEP8
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new errors
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] My PR passes Travis CI tests
[ ] My PR does not reduce coverage in Codecov

If your PR does not fulfill all of the requirements in the checklist above, that's OK! Just prepend [WIP] to the PR title until they are all satisfied. If you need help, @-mention a maintainer and/or add the Status: Help Needed label.

This looks awesome @jshermeyer! Just a couple of minor changes.


Formatting - replace google-java-format

Let's replace google-java-format for 2 reasons

Requires Java 11
Doesn't allow customization - the only two built-in configurations don't meet the requirements of current Java authoring guidelines

We could possibly use the Eclipse language server
Also fix ClientLogger checkstyle error.

Closing as this has been removed and replaced with Spotless


Shutdown request blocks if connection attempts fail

The call to GrpcClient.shutdown() blocks indefinitely if the client has failed to connect to the EventStoreDB.
Flow:

Create EventStoreDBClient instance.
Try to connect to a EventStoreDB server which is not available.
Issue an shutdown requests to the EventStoreDBClient.

Expected behavior:

Shutdown request finishes.

Observed behavior:

Shutdown request blocks indefinitely

The reason is that the Shutdown message in the GrpcClient is ignoried during the "drain" phase of the client after shutdown and the connected CompletableFuture is never completed. The Shutdown message is still handled as the client is not yet shutdown when the reconnect attempts are performed.

This solution works, but still has the issue that the shutdown request only completes after all reconnection attempts. Currently it is not possible to cancelling the connection attempts by calling shutdown() on the client. The Shutdown message will be queued inside the message loop after the CreateChannel message, which performs the reconnect attempts.
This issue should not be part of this bugticket, but might be an additional improvement on the client. It should be possible to cancel the reconnection attempts with performing a shutdown of the client instance.

Works fine now. Issue has been fixed.


Issue 772 Test User.AddTournamentId

You should also check that the tournament is properly added to the collection
for example by querying the user tournaments and getting the proper number.

:+1:


Support absolute paths in .fx-build-dir

According to [1], the path in .fx-build-dir can be absolute.
[1] https://cs.opensource.google/fuchsia/fuchsia/+/main:tools/devshell/lib/vars.sh;l=142;drc=177f2940747db40d498ad4ef2442cd8f78edb965

@richkadel I don't have access to Azure Pipelines and hence can't see the failure.


How to delete Items in ListBindingSectionController

New issue checklist

[ ] I have reviewed the README and documentation
[ ] I have searched existing issues and this is not a duplicate
[ ] I have attempted to reproduce the issue and include an example project.

General information

IGListKit version:
iOS version(s):
CocoaPods/Carthage version:
Xcode version:
Devices/Simulators affected:
Reproducible in the demo project? (Yes/No):
Related issues:

Debug information
erminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Invalid update: invalid number of items in section 0.  The number of items contained in an existing section after the update (3) must be equal to the number of items contained in that section before the update (3), plus or minus the number of items inserted or deleted from that section (0 inserted, 1 deleted) and plus or minus the number of items moved into or out of that section (0 moved in, 0 moved out).
# Please include debug logs using the following lldb command:
po [IGListDebugger dump]

This is my code ,I want to delete this item  but crash
func deleteComment(_ comment: CommentListData) {
        guard let index = sectionObjects.firstIndex(of: comment) else {
            return
        }

        self.collectionContext?.performBatch(animated: true, updates: { (batchContext) in
            self.sectionObjects.remove(at: index)
            batchContext.delete(in: self, at: IndexSet(integer: deleteIndex))
        }, completion: nil)
    }

You can try to use this method to change ListBindingSectionControllerDataSource
/**
 Tells the section controller to query for new view models, diff the changes, and update its cells.

 @param animated A flag indicating if the transition should be animated or not.
 @param completion An optional completion block executed after updates finish. Parameter is YES if updates were applied.
 */
- (void)updateAnimated:(BOOL)animated completion:(nullable void (^)(BOOL updated))completion;


nixos/device-tree: preprocess overlays before compiling

Description of changes
This PR applies the C preprocessor to device tree overlays before compiling them, using the same command as the kernel build system. This makes overlays easier to write and improves compatibility with existing overlays found in the wild.
I've tested this with the following overlay: https://github.com/lopsided98/nixos-config/blob/master/modules/local/machine/beagle-bone/BB-GATEWAY-WL1837-00A0.dts. This overlay also demonstrates the new (since 2018) simpler overlay syntax supported by dtc. I updated the dtsText example to use this syntax.
Things done

Built on platform(s)

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

[ ] 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.

cc @sorki @flokli

Thanks! I sucessfully tested this with my (file-based) overlays (on aarch64-linux)


Do not index layers without bounding box into elasticsearch

Coverage increased (+0.0007%) to 99.472% when pulling a397fe8127f6e4a8b8de47ba64d5fe288be14023 on JorgeMartinezG:no_wkt into 20bec8ca51b425dc677a7e1fca6f15abe695ebff on boundlessgeo:master.


Add support for parsing CSeq headers

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

Project coverage is 100.00%. Comparing base (f09c223) to head (9c8e5d0).

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #18   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            6         7    +1
  Lines          189       213   +24
=========================================
+ Hits           189       213   +24

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


PhpSpec version bump

Could you bump the version phpspec required to anything above 3.0 for example ^3.0?

@gpkoltermann I made PR #6


Updates for DVT head and pipette behavior

This is a branch that contains a couple PRs updating behavior for DVT. It should not be merged through the UI, but rebase-merged when we're ready.

Superceded by #571, though the branch and tag will remain.


Upgrade ChromeDriver to 2.37

Hi thanks for creating this image. We use it in our CI and it works like a charm.
We also use WebDriverManager which reports
INFO: Reading https://chromedriver.storage.googleapis.com/ to seek [chromedriver]
Mar 16, 2018 11:56:16 AM io.github.bonigarcia.wdm.WebDriverManager getLatest
INFO: Latest version of [chromedriver] is 2.37

later we get
Caused by: org.openqa.selenium.SessionNotCreatedException:
session not created exception: Chrome version must be >= 64.0.3282.0
  (Driver info: chromedriver=2.37.543610 (afd36256570660b5a2f0e4dbd1b040f3dcfe9cb5),platform=Linux 4.4.44-39.55.amzn1.x86_64 x86_64)

We managed to fix it by setting the ChromeDriver version to 2.35. However, we would like to stay up to date, so could you please update and publish the image to use the newest ChromeDriver/Chrome?
Thank you

Hi Andreas, no problem, glad you find it useful! I've upgraded ChromeDriver to 2.37 and a new build is available on Docker Hub.

Thanks Mark, that was quick.


Cannot use SSO credentials

What is the problem?
I run the official aws cli to configure SSO credentials and everything works. I set up the env var AWS_PROFILE to the right value, and running aws s3 ls works as expected.
However, when trying to run some code using the rust sdk I am greeted with:
Error: failed to construct request: Failed to load credentials from the credentials provider: An error occurred while loading credentials: An error occurred while loading credentials: SSO Token was invalid (expected JSON): Invalid field in response: `expiresAt`. invalid date-time: invalid RFC-3339 date-time: the 'offset hour' component could not be parsed

Caused by:
    Failed to load credentials from the credentials provider: An error occurred while loading credentials: An error occurred while loading credentials: SSO Token was invalid (expected JSON): Invalid field in response: `expiresAt`. invalid date-time: invalid RFC-3339 date-time: the 'offset hour' component could not be parsed

Under ~/.aws/sso/cache there are three json files with the following content:
{
  "startUrl": "REDACTED",
  "region": "eu-west-1",
  "accessToken": "REDACTED",
  "expiresAt": "2021-12-07T01:19:12UTC"
}
{
  "startUrl": "REDACTED",
  "region": "eu-west-1",
  "accessToken": "REDACTED",
  "expiresAt": "2022-02-03T19:44:13UTC"
}
{
  "clientId": "REDACTED",
  "clientSecret": "REDACTED",
  "expiresAt": "2022-02-23T10:56:02UTC"
}

Version
0.6.0
Platform
Linux arch-desktop 5.16.2-arch1-1 #1 SMP PREEMPT Thu, 20 Jan 2022 16:18:29 +0000 x86_64 GNU/Linux

Thanks for submitting this issue. I'm looking into it. In the meantime, can you post the version of the AWS CLI that you're using? We'd expect the expiresAt dates to end with Z instead of UTC.

$ aws --version
aws-cli/2.0.56 Python/3.7.3 Linux/5.16.2-arch1-1 exe/x86_64.arch

v2.0.56 of the CLI was released on Oct 8 , 2020, are you able to update to a more recent version an see if that fixes things? I believe v2.4.12 is the latest.

Alright, I updated my cli to latest version, and indeed, the expiresAt field now ends with a Z.
Feel free to close the bug if you don't plan to support older format.

@mrjeanjoseph - That looks like a different problem. Please file a separate issue or discussion.


code.json: Add required fields from code.json and publiccode.yml to repometrics cookiecutter

MENTOR

@natalialuzuriaga
USDC SWE Fellow, OSPO
Slack

BRIEF DESCRIPTION
After Natalia's research sprint on code.json and publiccode.yml, we have decided to update the CMS code.json to include required fields from code.json and publiccode.yml so that we can comply with both metadata standards. This rotation is focused on adding these new fields to repometrics and using cookiecutter to populate as many of the fields as possible.

Mural with comparison of code.json + publiccode.yml fields: https://app.mural.co/t/ccs9461/m/ccs9461/1720012298215/591f89739a9a842d37e1b7508d4f14c17fe7e740?sender=ubadd8a347114498c913e6865
Google Planning Doc: https://docs.google.com/document/d/1gYLvfoyUT4Db3TyL9EPQAgePk_q6KSFPX0LHcccewd8/edit

SCOPING

1 week

SKILLS NEEDED
Python, Cookiecutter
REQUIRED DELIVERABLES
Make as clear of a step-by-step list as you can:

Natalia will make a table with the list of all required fields in the Google Doc
EDIT: this is done! https://docs.google.com/document/d/1gYLvfoyUT4Db3TyL9EPQAgePk_q6KSFPX0LHcccewd8/edit#heading=h.ez3m3cjembkv
Identify fields can be populated using cookiecutter vs can be automatically filled out using GitHub API in post_gen_project.py
Add fields to cookiecutter.

DESIRED DELIVERY WINDOW

August

NOTES/INSPO
Super super excited for this one 🥳
ACKNOWLEDGEMENTS

[X] - Yes, I agree to spend file a project proposal ticket
[X] - Yes, I agree this project falls within a 2 week or less (ideally less) scope of time
[X] - Yes, I agree to spend an hour per week of office hours and 1x1 mentoring
[X] - Yes, I agree to spend an hour at the end of the sprint for filling out a Retro Template

9/30:

Labor hours hacksesh scheduled for tomorrow 10/1
We will talk about the date created logic as well as the labor hours logic and code.json broadly

10/4:

@sachin-panayil fixed issue with default date being removed: https://github.com/DSACMS/repo-scaffolder/pull/165
@IsaacMilarky created labor hours calculation: https://github.com/DSACMS/repo-scaffolder/pull/157
@sachin-panayil created the date calculation for age and date created of project.
Update the rest once @natalialuzuriaga gets back from GHC

10/07:

All PRs have been merged. Main is updated with all changes


Fix BASE_URL configuration

BASE_URL in docker-compose.env.tpl is currently set to 'localhost, <IP_ADDRESS>'.
Because the variable is also concatenated with APP_PATH to build API_URL, the resulting URL becomes invalid (result is: 'localhost, <IP_ADDRESS>/api').
How about we remove the SSL-related default configurations altogether and add a section to the documentation on how to set up SSL? This ensures that the top framework runs on localhost without any modifications and Caddy quirks.

I'll create a pull request to illustrate the changes I have in mind.


[WIP] bazel: use GCS remote cache

Signed-off-by: Lizan Zhou<EMAIL_ADDRESS>Partially addresses #3741
Description:
Use GCS remote cache for CI builds when key is provided.
Risk Level: Low
Testing: CI
Docs Changes:
Release Notes:

Closing since our CircleCI config doesn't expose env to forked PRs, use #4050 instead.


Nan occurs in backward loss_otherwise

Hi, I encounter a weird nan error in general.py during training after multiple epochs.
Any idea why this error occurs or how to fix it?

Error message of torch.autograd.detect_anomaly().
Cheers and many thanks in advance
Christoph

Hard to say without more info, but my guess at the most likely cause is 1) the input residual to the loss being extremely large (in which case clipping it should work) or NaN itself, or 2) alpha or scale becoming extremely large or small, in which case you probably want to manually constrain the range of values they take using the module interface.

Hard to say without more info, but my guess at the most likely cause is 1) the input residual to the loss being extremely large (in which case clipping it should work) or NaN itself, or 2) alpha or scale becoming extremely large or small, in which case you probably want to manually constrain the range of values they take using the module interface.


Improvement of Agro Blogs

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
In the Agro blogs section,

There is more space between "climate" and "smart" in "climate smart agriculture".
4 cards per row is reducing the readability. So, 3 cards per row will be better than this.
The heading and content and date are not evenly aligned- varies with each card, we can make it look consistent and even through all the cards. Which will improve user experience.

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Hey can you design a separate blog page where the user gets redirected on clicking blog option of navbar.

Yes, I can do that!


Add support for integrating with the Canonical Observability Stack

Enhancement Proposal
For application deployments that use the Canonical Observability Stack (COS), it would be useful to see nginx-ingress-integrator  logs, metrics, alerts and Grafana dashboards generated from them alongside the application's observability data.
From my brief reserach, this should be possible through:

adding support for the COS Loki LogForwarder charm interface: https://charmhub.io/loki-k8s/libraries/loki_push_api
enabling nginx-prometheus-exporter and supporting the COS Prometheus MetricsEndpointProvider interface: https://github.com/nginxinc/nginx-prometheus-exporter and https://charmhub.io/prometheus-k8s/libraries/prometheus_scrap
creating Grafana dashboard(s) and exposing them to COS Grafana through the grafana_dashboard relation:  https://charmhub.io/grafana-k8s/libraries/grafana_dashboard
exposing alert rules under the loki_alert_rules and prometheus_alert_rules folders in the charm, as described in the Prometheus and Loki documentation: https://charmhub.io/cos-lite

@weiiwang01 Can you give your opinion here, please? Thanks.

The nginx-ingress-integrator charm is a configurator charm that generates Kubernetes resources, such as ingress resources, service resources, rtc. It doesn't run the Nginx server itself; that’s the responsibility of the Nginx ingress controller. So, I think that observability integration on the nginx-ingress-integrator itself wouldn't be very useful.

I see, thank you for your reply @weiiwang01 If I understand right, the only way to interact with the Nginx server through Juju is using the nginx-ingress-integrator charm. If this is the case, what would be the right place to add COS support for Nginx on Juju?

This would be difficult, and there is no one-size-fits-all solution. The nginx Ingress Controller is usually managed by the deployment of the Kubernetes cluster, which means that it is often not charmed. For example, if juju is bootstrapped in microk8s, the nginx Ingress Controller will be managed by microk8s and deployed as a Kubernetes service, meaning it is not charmed and cannot be integrated into COS.

That makes sense, thanks. So would the only somewhat easy solution be to switch to the charmed Traefik operator that supports COS integrations?

Yes, if you do not have control over the Kubernetes cluster, the Traefik charm would be a better choice for getting COS integration for ingresses. It basically creates its own ingress for your application instead of using the Kubernetes cluster's ingress.

Thank you, that sounds like a better solution for my use case then. Please feel free to close this issue.


Remove null check on UserAuthenticationFailureEvent

If this null check was ever true the user.getUsername() call would
raise a NullPointerException.
These events only occur when user passwords don't match, more precisely
the event is only created here:
org/cloudfoundry/identity/uaa/authentication/manager/AuthzAuthenticationManager.java:107

In this case the user object has already been null checked.

Coverage decreased (-0.09%) to 84.888% when pulling 9c63413cdfe5198041e6b5d7f915c2245c22937f on davbo:remove-auth-error-null-check into fd7cd3c106ca0aae7528b20aa41cca7a075f5e63 on cloudfoundry:develop.

Coverage decreased (-0.09%) to 84.888% when pulling 9c63413cdfe5198041e6b5d7f915c2245c22937f on davbo:remove-auth-error-null-check into fd7cd3c106ca0aae7528b20aa41cca7a075f5e63 on cloudfoundry:develop.

One of the test runs seems to have failed. We just looked into the failure and it appears to be caused by this assertion https://github.com/cloudfoundry/uaa/blob/master/server/src/test/java/org/cloudfoundry/identity/uaa/scim/ScimCoreTests.java#L54
The new Date() calls on ScimMeta construction could happen milliseconds apart (the accuracy of Date) this looks likely to be the cause of this failure and makes the test unreliable.
I don't know the code very well but given that ScimCore doesn't implement patch() I'm not sure what the test is testing.

PR to be merged


Assertion Error on Insert

I imported the translated script from the Tsukihimates github into deepLuna. That worked, but whenever I click insert I get this error:
AssertionError: Unhandled control code 'justify_right' in line '%{justify_right}A dissolving dog.'
I dig some digging and this line's from Arc route day 2. I'm also using the main branch of deepLuna, not any releases, so that shouldn't be an issue.
Am I using the wrong version of the translated script or something by any chance?
Full Traceback just in case:
Exception in Tkinter callback
Traceback (most recent call last):
File "/usr/lib/python3.10/tkinter/init.py", line 1921, in call
return self.func(*args)
File "/mnt/c/Users/prasa/deepLuna/luna/ui/translation_window.py", line 403, in insert_translation
mzp_data = self._translation_db.generate_script_text_mrg(
File "/mnt/c/Users/prasa/deepLuna/luna/translation_db.py", line 184, in generate_script_text_mrg
offset_to_string = self.generate_linebroken_text_map(perform_charswap)
File "/mnt/c/Users/prasa/deepLuna/luna/translation_db.py", line 243, in generate_linebroken_text_map
coded_text = RubyUtils.apply_control_codes(tl_text)
File "/mnt/c/Users/prasa/deepLuna/luna/ruby_utils.py", line 222, in apply_control_codes
assert False,
AssertionError: Unhandled control code 'justify_right' in line '%{justify_right}A dissolving dog.'

The script is not finished. We would ask that you wait for the final release if you wish to read the game. Thank you for your patience.


Inserts stop at 150 records out of 2600

I am parsing a series of files, and the net data is 2600 objects
passed to a function which calls conn.query.
The console logs all 2600 items, but the mysql inserts stop at 150 records.
function insertData(data) {
  const conn = mysql.createConnection(datasource)
  const values = [data.one, data.two, `${data.three}`, data.four]
  let sql = "INSERT INTO resource (one, two, three, four) VALUES (?, ?, ?, ?)";

  console.log(`Processing #[${counter}] ${data['one']}`)

  return new Promise(async () => {
    await conn.query(sql, values, (error, results, fields) => {
      if (error) return error
      console.log(JSON.stringify(results))
    })

    conn.end()
  })
}

Is there something in particular that I need to be doing here?

An error may be occurring, but your code will never display it. Can you add a if (error) console.log(error) to the top of your query callback to check if there is some error that is occurring?

Also, unless you are leaving something out, you cannot actually await the return value of conn.query with this module, so your conn.end() call may be occurring prior to the query completing, possibility.

Ok. I'll check these two things first.

You were right. I don't know how I forgot to console.log(error).
Any tips on throttling this a bit so that the connections aren't piling up?
Should I use connection pooling? I'm not sure how to incorporate it.
Error: ER_CON_COUNT_ERROR: Too many connections
    at Handshake.Sequence._packetToError (/home/kingram/PROJECTS/government/node_modules/mysql/lib/protocol/sequences/Sequence.js:47:14)
    at Handshake.ErrorPacket (/home/kingram/PROJECTS/government/node_modules/mysql/lib/protocol/sequences/Handshake.js:123:18)
    at Protocol._parsePacket (/home/kingram/PROJECTS/government/node_modules/mysql/lib/protocol/Protocol.js:291:23)
    at Parser._parsePacket (/home/kingram/PROJECTS/government/node_modules/mysql/lib/protocol/Parser.js:433:10)
    at Parser.write (/home/kingram/PROJECTS/government/node_modules/mysql/lib/protocol/Parser.js:43:10)
    at Protocol.write (/home/kingram/PROJECTS/government/node_modules/mysql/lib/protocol/Protocol.js:38:16)
    at Socket.<anonymous> (/home/kingram/PROJECTS/government/node_modules/mysql/lib/Connection.js:88:28)
    at Socket.<anonymous> (/home/kingram/PROJECTS/government/node_modules/mysql/lib/Connection.js:526:10)
    at Socket.emit (events.js:210:5)
    at addChunk (_stream_readable.js:308:12)
    --------------------
    at Protocol._enqueue (/home/kingram/PROJECTS/government/node_modules/mysql/lib/protocol/Protocol.js:144:48)
    at Protocol.handshake (/home/kingram/PROJECTS/government/node_modules/mysql/lib/protocol/Protocol.js:51:23)
    at Connection.connect (/home/kingram/PROJECTS/government/node_modules/mysql/lib/Connection.js:116:18)
    at Connection._implyConnect (/home/kingram/PROJECTS/government/node_modules/mysql/lib/Connection.js:454:10)
    at Connection.query (/home/kingram/PROJECTS/government/node_modules/mysql/lib/Connection.js:196:8)
    at /home/kingram/PROJECTS/government/process.js:100:10
    at new Promise (<anonymous>)
    at insertData (/home/kingram/PROJECTS/government/process.js:99:10)
    at proccessHTML (/home/kingram/PROJECTS/government/process.js:64:7)
    at ReadStream.<anonymous> (/home/kingram/PROJECTS/government/process.js:81:5) {
  code: 'ER_CON_COUNT_ERROR',
  errno: 1040,
  sqlMessage: 'Too many connections',
  sqlState: undefined,
  fatal: true
}

Ah, ok. So it seems like you are likely calling your insertData in a direct for or forEach loop perhaps, as it is likely trying to create all the connections up front as fast as it can instead of doing it one after the other. A simple "fix" would indeed be to just use a pool -- then you're just scheduling all the queries at once on the pool, which will constrain your parallelism to the max pool size. Another option is to pull in an async scheduling module such as https://www.npmjs.com/package/async

If you use a single insert for each datarow you will run into problems (memory / heap stack) when you run more than 2600 rows, let say 20k rows or more.
i would use bulk insert queries with 500 to 1000 rows like
INSERT INTO resource (one, two, three, four) VALUES (?, ?, ?, ?), (?, ?, ?, ?), (?, ?, ?, ?), (?, ?, ?, ?), [...];

This way you would need only one connection per 1000 rows and have much less overhead.

This way you would need only one connection per 1000 rows and have much less overhead.

Sounds like a good idea, though I don't see more than 3000 inserts at a time with this project, it may
be true for the next one.
Once I get a handle on connection pooling, since I'm there now, I'll try the batch inserts.

Currently I'm having this error using connection pooling:
Error: Handshake inactivity timeout
    at Handshake.<anonymous> (/home/kingram/PROJECTS/government/node_modules/mysql/lib/protocol/Protocol.js:160:17)
    at Handshake.emit (events.js:210:5)
    at Handshake._onTimeout (/home/kingram/PROJECTS/government/node_modules/mysql/lib/protocol/sequences/Sequence.js:124:8)
    at Timer._onTimeout (/home/kingram/PROJECTS/government/node_modules/mysql/lib/protocol/Timer.js:32:23)
    at listOnTimeout (internal/timers.js:531:17)
    at processTimers (internal/timers.js:475:7)
    --------------------
    at Protocol._enqueue (/home/kingram/PROJECTS/government/node_modules/mysql/lib/protocol/Protocol.js:144:48)
    at Protocol.handshake (/home/kingram/PROJECTS/government/node_modules/mysql/lib/protocol/Protocol.js:51:23)
    at PoolConnection.connect (/home/kingram/PROJECTS/government/node_modules/mysql/lib/Connection.js:116:18)
    at Pool.getConnection (/home/kingram/PROJECTS/government/node_modules/mysql/lib/Pool.js:48:16)
    at insertData (/home/kingram/PROJECTS/government/process.js:89:8)
    at proccessHTML (/home/kingram/PROJECTS/government/process.js:66:7)
    at ReadStream.<anonymous> (/home/kingram/PROJECTS/government/process.js:83:5)
    at ReadStream.emit (events.js:215:7)
    at endReadableNT (_stream_readable.js:1183:12)
    at processTicksAndRejections (internal/process/task_queues.js:80:21) {
  code: 'PROTOCOL_SEQUENCE_TIMEOUT',
  fatal: true,
  timeout: 50000
}

/home/kingram/PROJECTS/government/process.js:97
    connection.query(sql, values, (error, results, fields) => {
               ^

TypeError: Cannot read property 'query' of undefined
    at /home/kingram/PROJECTS/government/process.js:97:16
    at Handshake.onConnect (/home/kingram/PROJECTS/government/node_modules/mysql/lib/Pool.js:58:9)
    at Handshake.<anonymous> (/home/kingram/PROJECTS/government/node_modules/mysql/lib/Connection.js:526:10)
    at Handshake._callback (/home/kingram/PROJECTS/government/node_modules/mysql/lib/Connection.js:488:16)
    at Handshake.Sequence.end (/home/kingram/PROJECTS/government/node_modules/mysql/lib/protocol/sequences/Sequence.js:83:24)
    at /home/kingram/PROJECTS/government/node_modules/mysql/lib/protocol/Protocol.js:404:18
    at Array.forEach (<anonymous>)
    at /home/kingram/PROJECTS/government/node_modules/mysql/lib/protocol/Protocol.js:403:13
    at processTicksAndRejections (internal/process/task_queues.js:75:11)
    at runNextTicks (internal/process/task_queues.js:62:3)
(END)

My code looks like this:
const dataPool = {
  // debug: ['ComQueryPacket', 'RowDataPacket'],
  //debug: true,
  acquireTimeout: 50000,
  host: ***,
  user: ***,
  password: ***,
  database: 'test',
  port: '3306',
  charset: 'utf8mb4'
}

const pool = mysql.createPool(dataPool)

function insertData(data) {
  pool.getConnection((err, connection) => {
    if (err) console.log(err)
    const values = [one, two, three, four]
    const sql = "INSERT INTO resource (one, two, three, four) VALUES (?, ?, ?, ?)";

    console.log(`Processing #[${counter}] ${data['one']}`)

    connection.query(sql, values, (error, results, fields) => {
      connection.release()
      if (error) console.log(error)
      console.log(JSON.stringify(results))
    })
  })
}

function processData(input){
	// stuff
	insertData(input)
}

source.forEach((item) => {
	processData(item)
})

I would definitely follow the advice of @kai-koch. This way you would need less connections and that means it's less error-prone.
For proper error handling processData and insertData need a callback parameter. At least you should add a return statement:
if (err) {
  console.log(err);
  return;
}

I would also look at the MySQL log to see what the server is doing when the script fails.

Check the console for the Error.
If an error occurs in pool.getConnection(), the execution continues after if(err). But query is undefined in this case. Hence the undefined error.
see the answer of mbaumgartl to stop execution, if an error occurs. You should add more error-handling, than just console.log.


Uninstall script does not delete the KA Lite data folder.

Branch develop
Target 0.16.0
Expected Behaviour The OS X uninstall script does not delete the KA Lite data folder even when user answers "yes" when asked.
Current Behaviour It doesn't delete the KA Lite data folder.

Fixed in #329.


Refactor DeliveryRequestWorker and DeliveryRequestService

I wanted to continue the work of https://github.com/alphagov/email-alert-api/pull/1272 and found myself fighting against a number of inconsistencies and unconventional approaches. I decided for ease of review it'd be best to separate the refactor into a separate PR and open one that builds on this for the metrics change.
A brief summary of changes are:

fixed a global exception being defined in the DeliveryRequestWorker file
added a test for Sidekiq worker exhausted retries since that was untested
upped the 30 second rate limit retry to 5 minutes as 30 seconds seemed suspiciously short for a job that has already been retrying for 2 hours 30 mins
moved public methods in DeliveryRequestWorker to be private, removed unused instance variables/methods
moved the DeliveryRequestService::EmailAddressOverrider to a separate file since it's unit tested
gave DeliveryRequestService a more convention .call interface where all arguments are passed to the initialize method, moved various tested public methods that aren't used publicly to private

The easiest way to remove this is to do this commit by commit - not that much has actually changed despite what the overall diff looks like.
This work does leave two things dangling for follow up work. We're left with an unusued _queue argument to DeliveryRequestWorker, I resolve that in the next PR. The EmailAddressOverrider stuff all looks a bit of a mess with confusing environment variables and whitelist/blacklist terminology.

Thanks @benthorner, I've amended.


Feature: High-level mocking support

In order to test our Redis integration, we need to be able to mock a Redis client. Please let me know which of the various options (if any) would be perferable, I might shoot a PR.
While possible with a miniredis, this would be testing rueidis in addition to our integration code. As rueidis has tests of its own, this potentially increases maintenance load.
A more elegant way to test seems to be through a mock rueidis client. However, the Client interface depends on internal/cmds, which cannot be imported by external packages, preventing us from making a mock.
It seems to me there are two ways to work around this:

Add a mock client as a mock package into rueidis.
Move cmds.Builder outside of the internal package.
Replace cmds.Builder by an interface.

As for the actual mock, it seems there are two available strategies:
a. A high-level mock, like Testify's one.
b. A low-level mock, as in: https://github.com/rueian/rueidis/blob/28ab1a08c9f96629aa1115a9b313230227fee0f0/pipe_test.go#L25
This issue/feature request is specific to a. as b. can already be performed through miniredis.

Hi @dokterbob,
There is a new mock package in rueidis v0.0.79.
Please check it out: https://github.com/rueian/rueidis/tree/master/mock


flow: 0.72.0 -> 0.75.0

Motivation for this change
Using newer version at work.
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

@globin


9.0.0 Features/Roadmap - MAJOR RELEASE

I want to start to think about angular-modal-gallery 9.0.0. In particular I want to create a list with some possibile features.
9.0.0 Project board to see progress
Changes in 9.0.0

[x] #235 (BREAKING CHANGE)
[x] remove keyCode in keyboard-navigation.directive.ts (drop IE11) #200 (BREAKING CHANGE)
[x] #228 (BREAKING CHANGE)
[x] #229 (BREAKING CHANGE)
[x] #230 (BREAKING CHANGE)
[x] upgrade main example with the new APIs
[x] upgrade other examples with the new APIs (/examples folder)
[x] upgrade stackblitz example
[x] update tests for carousel component
[x] update tests for carousel-previews component
[x] upgrade carousel APIs on doc website
[x] upgrade carousel examples on doc website
[x] #242
[x] #241 (BREAKING CHANGE)
[x] #240 (BREAKING CHANGE)
[x] #239 (BREAKING CHANGE)
[x] #231
[x] #232 (BREAKING CHANGE)
[x] #233 (BREAKING CHANGE)
[x] carousel should work also with 0 images or at least show a loading spinner #209
[x] #236
[x] #238 (BREAKING CHANGE)

Optional with low priority

[ ] #208
[ ]  #223

I'll release alphas, betas and so on as always. Feel free to report feedbacks and ideas.

Version 8.0.0 was very huge so with this new release it's time to improve what I made in 8.0.0 and remove deprecated stuff, like IE11, because Angular 13 won't support IE.

To be transparent I created a Project board for both version 9.0.0 and 10.0.0
As you can see I scheduled most of the new features to 10.0.0, because I want to release 9.0.0 as an improvement release with many breaking changes (required to remove IE11 legacy code)

I already implemented some features and I pushed everything into branch called 900

Upgraded to angular 13.0.0:

library
main example
other examples
doc website

There is only one missing thing in the "migration" page of the official doc website to release 9.0.0 final.
I hope to release 9.0.0 this weekend

released on npm
doc website available here: https://ks89.github.io/angular-modal-gallery-2021-v9.github.io/


Add TensorBoard file system watcher test

[ ] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
[ ] Title summarizes what is changing.
[ ] Has a news entry file (remember to thank yourself!).
[ ] Appropriate comments and documentation strings in the code.
[ ] Has sufficient logging.
[ ] Has telemetry for enhancements.
[ ] Unit tests & system/integration tests are added/updated.
[ ] Test plan is updated as appropriate.
[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed).
[ ] The wiki is updated with any design decisions/details.

Codecov Report

Merging #15078 (b0e377a) into main (98d22e7) will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##            main   #15078   +/-   ##
======================================
  Coverage     65%      65%
======================================
  Files        558      558
  Lines      26231    26231
  Branches    3728     3728
======================================
  Hits       17155    17155
  Misses      8381     8381
  Partials     695      695

Codecov Report

Merging #15078 (b0e377a) into main (98d22e7) will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##            main   #15078   +/-   ##
======================================
  Coverage     65%      65%
======================================
  Files        558      558
  Lines      26231    26231
  Branches    3728     3728
======================================
  Hits       17155    17155
  Misses      8381     8381
  Partials     695      695


Supplementary  metrics-server latency measurement

Signed-off-by: JunYang<EMAIL_ADDRESS>
What type of PR is this?
/kind feature

What this PR does / why we need it:
implement of issue: #710
Which issue(s) this PR fixes:

Fixes #1839
part of issue: #710
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

Add metrics-server latency measurement, Controlled by flag --prometheus-scrape-metrics-server

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

/cc @mm4tt  @marseel

I will take a look at this PR soon. If you want to ask for review please assign it to me, otherwise I will probably miss it.
/assign @marseel

/lgtm
/hold
Let's merge it on Monday ;)

/unhold


2D MPR not working on Safari

I am having issues with the 2D MPR functionality in Safari:

The same study loads perfectly fine if I use Chrome:

I am using Safari 13.1.2 (146<IP_ADDRESS>.5). I built the viewer using the current master build (ohif/viewer@4.5.1).

Thanks for the report.  I can reproduce this on Safari Version 13.1.2 (156<IP_ADDRESS>.3) using this link:
https://viewer.ohif.org/viewer/<IP_ADDRESS>.4.1.25403.345050719074.3824.20170125113417.1
@fedorov this also occurs in the IDC viewer.  I marked it as candidate and we can discuss whether it's a priority.

So after a bunch of testing I realised this was only happening on CTs, and wasn't due to strange array sizes or anything.
Data inserted in react-vtkjs-viewport had no difference between browsers, and I could get individual slices of the problematic data to render using the vtkImageSlice.
Turns out the issue is WebGL 1 and large textures:
https://github.com/Kitware/vtk-js/blob/acd940c9eb35efde4d16ffe2946ae31fe1d02507/Sources/Rendering/OpenGL/Texture/index.js#L1166
The max texture size is throttled here to stop the context from throwing errors, but this means not all of the data is being copied fully, this will happen with any large dataset.
Unfortuantely turning on Safari's experimental "Web GL 2.0" feature does not help here, as safari's implementation is far from complete.
So it looks like there is no easy fix for this. We could detect the browser being used and the volume size, and throw a warning when MPR is used or something?

Yes, it sounds like detecting the issue and displaying a warning is the best we can do here.  Kind of a shame, but not really under our control.

@pieper do we have the fix above in the IDC?

No, I don't believe anything has been implemented yet.  Detecting the browser and bringing up a warning still seems like the best thing.  To me the correct implementation would be to detect the issue at the lowest level (vtk.js) and propagate the information up through the layers and present it to the user at the application level.  But maybe the best short-term would be just to detect Safari in the IDC viewer and generate a warning.

I mean, did #2106 make it into the IDC fork?

Yes, at the OHIF level: https://github.com/ImagingDataCommons/Viewers/commits/idc-ohif-2020-10-15

Thanks! @wlongabaugh FYI

Please review the latest code in the master branch. This issue might have been resolved. If it persists, kindly reopen the issue with updated details.
Try viewer-dev.ohif.org instead of viewer.ohif.org
Our viewer.ohif.org is deployed from release branch while viewer-dev.ohif.org is our master  branch
Read more about branch explanations here https://docs.ohif.org/development/getting-started#developing


Add domain and protocol validation to pvl checkers

This PR is in line behind https://github.com/keybase/client/pull/4325.
This fixes problems with generic_web_site and dns checking (in pvl).
generic_web_site used to match case insensitively which is bad for paths. https://example.com/keybase.txt isn't http://example.com/keYBAse.txt.
Both generic_web_site and dns used to accept whatever the hint provided as a domain. Now they check that it's a valid domain with no port, query string, path, or any such funny business. The non-pvl system needs this too, but that's not in this PR.
generic_web_site used to accept either http or https as a hint from the server regardless of the protocol specified in the sig. Now it requires that the hint match the sig protocol exactly. Also the protocol is validated so you can only have http or https (plus some funky colons).
r? @oconnor663

:mag_right: The commits d420d2929da5...b97e4c83fb3f introduced some visual changes on linux:

Changed: New_Proof_PGP_generating-Generating_PGP (before) (after)

Changed validateDomain to disallow IPs. It disallows all valid IPs and then makes attempts to disallow things that are close to IPs like <IP_ADDRESS>.


Upgrade eBPF to 0.9.0 postrelease

eBPF has fixed https://github.com/microsoft/ebpf-for-windows/issues/2457, so consume that fix and all intermediate changes since 0.9.0 was officially released.

rather than downloading ebpf-for-windows from some xdp-for-windows location, why not ask for a 0.10 release from ebpf-for-windows?  Usually ebpf-for-windows does one at the end of each month, which would only be 1 week away now.

rather than downloading ebpf-for-windows from some xdp-for-windows location, why not ask for a 0.10 release from ebpf-for-windows? Usually ebpf-for-windows does one at the end of each month, which would only be 1 week away now.

We're helping eBPF find and fix bugs ASAP, because XDP can take an official, supported dependency on eBPF only once we have confidence in end-to-end quality and reliability. Over the 3+ months since we started integrating with eBPF, each batch of bug fixes from eBPF (thanks!) has uncovered a new tranche of bugs. We can delay this effort as needed.


Suspicious login

When i use the library with this:
        Instagram4j instagram = Instagram4j.builder().username("user").password("pass").build(); //proxy(proxy).credentialsProvider(credentialsProvider)         instagram.setup();         instagram.login();
It makes the following messages,
2020-01-28 12:58:07 [main] INFO  org.brunocvcunha.instagram4j.Instagram4j  - Setup... 2020-01-28 12:58:07 [main] INFO  org.brunocvcunha.instagram4j.Instagram4j  - Device ID is: android-de8d17b33b1ad4c4, random id: 3a5a6811-d00f-4609-bb6b-9b1ce1e1bf8c 2020-01-28 12:58:08 [main] INFO  org.brunocvcunha.instagram4j.Instagram4j  - Logging with user username and password **************** 2020-01-28 12:58:08 [main] INFO  org.brunocvcunha.instagram4j.Instagram4j  - Sending request: org.brunocvcunha.instagram4j.requests.internal.InstagramReadMsisdnHeaderRequest 2020-01-28 12:58:08 [main] INFO  org.brunocvcunha.instagram4j.Instagram4j  - Sending request: org.brunocvcunha.instagram4j.requests.internal.InstagramFetchHeadersRequest 2020-01-28 12:58:09 [main] INFO  org.brunocvcunha.instagram4j.requests.InstagramRequest  - Reading StatusResult from {"status": "ok"} 2020-01-28 12:58:09 [main] INFO  org.brunocvcunha.instagram4j.requests.InstagramRequest  - Reading StatusResult from {"status": "ok"} 2020-01-28 12:58:09 [main] INFO  org.brunocvcunha.instagram4j.Instagram4j  - Sending request: org.brunocvcunha.instagram4j.requests.internal.InstagramSyncFeaturesRequest 2020-01-28 12:58:10 [main] INFO  org.brunocvcunha.instagram4j.requests.InstagramRequest  - Reading InstagramSyncFeaturesResult from {"ig_search_client_h1_2017_holdout": {"behavior": "pass"}, "ig_android_video_captions_universe": {"mode": "only_muted"}, "ig_and 2020-01-28 12:58:10 [main] INFO  org.brunocvcunha.instagram4j.Instagram4j  - Sending request: org.brunocvcunha.instagram4j.requests.internal.InstagramZeroRatingTokenRequest 2020-01-28 12:58:10 [main] INFO  org.brunocvcunha.instagram4j.Instagram4j  - Sending request: org.brunocvcunha.instagram4j.requests.internal.InstagramLogAttributionRequest 2020-01-28 12:58:11 [main] INFO  org.brunocvcunha.instagram4j.requests.InstagramRequest  - Reading StatusResult from {"status": "ok"} 2020-01-28 12:58:11 [main] INFO  org.brunocvcunha.instagram4j.Instagram4j  - Sending request: org.brunocvcunha.instagram4j.requests.InstagramLoginRequest 2020-01-28 12:58:14 [main] INFO  org.brunocvcunha.instagram4j.requests.InstagramRequest  - Reading InstagramLoginResult from {"message": "The password you entered is incorrect. Please try again or log in with Facebook.", "status": "fail", "error_type":  2020-01-28 12:58:16 [main] INFO  org.brunocvcunha.instagram4j.Instagram4j  - Sending request: org.brunocvcunha.instagram4j.requests.InstagramSearchUsernameRequest 2020-01-28 12:58:16 [main] INFO  org.brunocvcunha.instagram4j.requests.InstagramRequest  - Reading InstagramSearchUsernameResult from {"message": "login_required", "error_title": "You've Been Logged Out", "error_body": "Please log back in.", "logout_reason": 2,
it does not login, Ive tried with a proxy and the ip im using to run this is my home wifi which is connected to my phone.
I cannot seem to use this library at all, any tips/help?

You need to confirm your actions programmatically rather than manually. There are 4 additional classes for this purpose, which you must perform before authorization. Look at a sample of my code, if you don't understand - write to me.

Exception in thread "main" java.lang.Error: Unresolved compilation problems:  	UserStatus cannot be resolved to a variable 	The method sendRequest(InstagramRequest<T>) in the type Instagram4j is not applicable for the arguments (InstagramSendSecurityCodeRequest) 	code cannot be resolved to a variable 	UserStatus cannot be resolved to a variable 	status cannot be resolved to a variable 	UserStatus cannot be resolved to a variable
Can you help me?


feat: Simplify setup process and configure platform-specific desktop files

This pull request introduces the following changes:
Commit 1: feature: Create electron-forge and configure for Linux packaging

Created electron-forge.config.js to include more specific builds for Linux packaging, addressing failures with default settings.
Updated package.json to include electron-forge and electron-squirrel-startup as dev dependencies.
Updated package-lock.json to include the new dependencies.
Set executableName, outDir, and dir options for proper binary location.
Changed name and productName to "smolmenubar" to match the executable name in package.json, resolving an issue where npm run build/make was unable to find the executable (it was looking for 'smol-menubar').

Commit 2: feat: Simplify setup process and generate platform-specific desktop files

This commit simplifies the setup and launch process of the application by introducing a setup.js file.
setup.js detects the user's system environment and platform, generating the appropriate desktop file or shortcut for Linux, macOS, and Windows platforms.
The new process simplifies the setup to cloning the repository, navigating into it, running npm install, and then running npm run start.
The start script executes setup.js, which determines the environment and platform, generates the appropriate desktop file, and launches the application.
Updating the application can now be achieved by pulling the latest changes from the repository.
package.json and electron-forge configurations have been updated to accommodate these changes.

These changes aim to streamline the setup process and improve compatibility across different platforms. They simplify the steps required to launch the application and make updating easier. Please review and merge this pull request.

Updated README.md to reflect installation and run changes

ok took me a little while to understand the "first run file" but i think i get it. thanks very much!


logging for tools are incomplete/broken

Using tools the logging is looking like this:
2023-12-14 08:49:28,633 DEBUG [io.qua.lan.run.too.QuarkusToolExecutor] (main) Attempting to convert {0} JSON string into args map
2023-12-14 08:49:28,634 DEBUG [io.qua.lan.run.too.QuarkusToolExecutor] (main) Converted {0} JSON string into args map {1}
2023-12-14 08:49:28,634 DEBUG [io.qua.lan.run.too.QuarkusToolExecutor] (main) Attempting to invoke tool {0} with parameters {1}
2023-12-14 08:49:28,635 DEBUG [io.qua.lan.run.too.QuarkusToolExecutor] (main) Tool execution result: {0}

Seems like no formatting/templating is occurring?

This is super weird...
Logging from QuarkusToolExecutor is indeed not working as you point out, but the same exact pattern used from AiServiceMethodImplementationSupport works just fine...

Actually no, it's even more complicated... I need to look more

#154 fixes it


Warning: CocoaPods not installed. Skipping pod install.

Describe the bug
I am running the command: fvm flutter run --flavor $FLAVOR -t lib/main/${FLAVOR}/main_${FLAVOR}_${ENV}.dart
Which is gives the error:
Warning: CocoaPods not installed. Skipping pod install.
  CocoaPods is used to retrieve the iOS and macOS platform side's plugin code that responds to your plugin usage on the Dart side.
  Without CocoaPods, plugins will not work on iOS or macOS.
  For more info, see https://flutter.dev/platform-plugins
To install see https://guides.cocoapods.org/using/getting-started.html#installation for instructions.

CocoaPods not installed or not in valid state.

To Reproduce
I am not sure how to reproduce this. It is just happening, I'm sorry I don't have more information than I have provided.
Expected behavior
FVM should find cocoapods and run the application, as flutter run ... does.
Logs from fvm doctor:
FVM Version: 2.3.1

FVM config found:

Project: Ottalaus_MobileDev
Directory: /Users/sterlinglong/Desktop/m1pro-desktop/work/lztek/Ottalaus/Ottalaus_MobileDev
Version: 2.8.1
Project Flavor: None selected

Version is currently cached locally.
Cache Path: /Users/sterlinglong/fvm/versions/2.8.1
Channel: false
SDK Version: 2.8.1
IDE Links
VSCode: .fvm/flutter_sdk
Android Studio: /Users/sterlinglong/Desktop/m1pro-desktop/work/lztek/Ottalaus/Ottalaus_MobileDev/.fvm/flutter_sdk
Configured env paths:

Flutter:
/usr/local/bin/flutter
Dart:
/usr/local/bin/dart
FVM_HOME:
not set
Desktop:

OS: macOS Monterey, 12.2.1
FVM Version 2.3.1

Additional context
I have tried brew installing ruby and then installing an updated version of Cocoapods, but FVM still does not find it.
I have followed the information provided in this bug report, but that didn't work either.

@leoafarias Yes, running normally works as intended.
I have updated the original post with a way to reproduce the error.


docs(pattern): upload pattern

Migrated upload pattern. This was a contribution.
Original PR here: https://github.com/carbon-design-system/carbon-website-archive/pull/1712

This is the same as the Import pattern. https://www.carbondesignsystem.com/experimental/import-pattern/


add SparkPool into Grin Friends page

Tx Id: https://etherscan.io/tx/0x34460d9d8c9610109fe16f88939e03e8b2982613dcb95fa0459b995e75df5499
To: Yeastplume Funding Campaign
From: SparkPool
Amount: 100 ETH
Notes from SparkPool founder:

More will come
And constantly

Thank you very much!

Updated to keep a record here for Sparkpool's 2nd donation:
Tx Id: https://www.blockchain.com/zh/btc/tx/147b921ac69042cd1bac5ca0b2715b8a2951f0bd9f27232260ed0a7a6d0563b0
To: Yeastplume Funding Campaign
From: SparkPool
Amount: 2.38217288 BTC

Updated to keep a record here for Sparkpool's 3rd donation on 2019.03.03:
To: Grin General Fund
Amount: 5500 GRIN (on the current price $3.68 USD / Grin, it's 20,240 USD).
ignotus
4:39 AM I can confirm a 5500 grins donation on our wallet

@garyyu just to make you aware that we now have this: https://github.com/mimblewimble/grin-pm/blob/master/financials/income_log.csv -> Would be awesome if you could help me keep track of these donations in there. :)

@lehnberg Cool!
and can we move grin-pm/financials/income_log.csv into site repo?  then we can avoid using two PR to modify both repo.

I think the governance meeting decided it should be in grin-pm, which also makes sense to me intuitively. I believe it  should be straight forward to point any logic on site to look into grin-pm for this.

I think the governance meeting decided it should be in grin-pm.

At that time, we didn't know we will have Hall of Fame and didn't know we will have History feature on Hall of Fame. So we'd better to discuss again and change it, to use same repo.

which also makes sense to me intuitively

I'm afraid now it's not so intuitively :-)  when a donation is done, we need a PR to modify the site to add the Friends page, and we need another PR to modify grin-pm/financials/income_log.csv.
So, I still think moving it into site repo is the best choice.


QAP Anatomical Crash [TypeError in pool.py]

160807-20:48:22,747 workflow INFO:
Configuration settings:
{'write_graph': False, 'write_all_outputs': False, 'num_subjects_at_once': 24, 'output_directory': '/Volumes/Archive.ADS/ADS/analysis/qap', 'write_report': True, 'working_directory': '/Volumes/Archive.ADS/ADS/analysis/qap/werk', 'num_cores_per_subject': 1, 'template_skull_for_anat': '/usr/local/fsl/data/standard/MNI152_T1_2mm.nii.gz', 'pipeline_config_yaml': '/Volumes/Archive.ADS/ADS/analysis/qap/Anatomical.yml', 'template_brain_for_anat': '/usr/local/fsl/data/standard/MNI152_T1_2mm_brain.nii.gz', 'qap_type': 'anatomical_spatial'}
Traceback (most recent call last):
File "/Users/shad/quality-assessment-protocol/scripts/qap_anatomical_spatial.py", line 10, in
obj.run()
File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/qap/cli.py", line 244, in run
results = self._run_here(run_name)
File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/qap/cli.py", line 187, in _run_here
results = pool.map(_run_workflow, wfargs)
File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/multiprocessing/pool.py", line 251, in map
return self.map_async(func, iterable, chunksize).get()
File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/multiprocessing/pool.py", line 567, in get
raise self._value
TypeError: coercing to Unicode: need string or buffer, NoneType found

Hi Seldamat,
Which version of QAP are you running?

I used pip to install version 1.0.5 -- i've also tried building from this repo but that never seems to work for me.

This issue should be resolved in the 1.0.6_dev_parallel branch (which is slated for an upcoming official release). I would recommend trying that version, though there have been quite a few changes since 1.0.5 - you may need to update your configuration files if you choose to do so.
The most recent format for the configuration files are available here, under the files ending with _TEMPLATE:
https://github.com/preprocessed-connectomes-project/quality-assessment-protocol/tree/1.0.6_dev_parallel/configs

Hi @sgiavasis,
Sure, I'd love to give it a shot to see if I can get this running on some of my data. Is the right way to install the development version?

Select the branch in the dropdown menu
Downloaded the .zip
copied over all the scripts to my macports install of python
sudo cp Downloads/quality-assessment-protocol-1.0.6_dev_parallel/scripts/* /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/
Installed the dev version

python setup.py -v build
python setup.py -v install

I'm running the pipeline now - I'll update this post with the results!

We appreciate your willingness to help us debug/test. :D

Of course! This is a great suite of tools for neuroimaging research so I'm happy to help out in any way I can :)
One thing I noticed is that your new template configuration files for the functional pipelines do not have the start/stop IDX nor the slice_timing_correction or ghost direction fields.  Should these be included or is it ok to leave them out?
The anatomical pipeline is still running but it appears that the segmentation step is crashing out on subjects that were successfully run in the past.  Here is a link to the pklz files and associated logs
https://drive.google.com/open?id=0B62ZUf2RblCDVjlhRjVSZ25nb28
Please let me know if you need any more information or whether you'd like me to open this up as a separate issue.

The change in the configuration template will be reflected in the new release's documentation- sorry for the gap in info.
The start/stop IDX now defaults to 0 and End respectively, but you can override these with your own settings by including the options if you'd like (you just don't have to anymore).
Slice timing correction has been removed from QAP.
And ghost direction defaults to Y, as this is the most prevalent configuration. However, you can override this just like with the start/stop IDX by including the parameter and setting it to either X or Z if appropriate.
I'm going to take a look at those crashes in the meantime.

Hi Seldamat,
For the run that produced those segmentation crash files-  was this a run you had started earlier, stopped, then started again? It looks like something funny might have happened in the working directory and it just can't find where to pick up from with segmentation.
I would try, at least for one of the crashed subjects, clearing out the working directory for that one subject and re-running and seeing if that crash still occurs.
Did you have any issues installing the 1.0.6_dev_parallel branch, by the way?

Hi sgiavasis,
Yes, it was a run that I interrupted because I wanted to modify the config
file.
Since then I've reinstalled the 1.0.6_dev_parallel branch by cloning it,
building and installing and copying the scripts to my python bin path.
I deleted the directory and reran everything from scratch and I am not
getting the same error anymore.
However, I am getting a new error
Configuration settings:
{'num_subjects_per_bundle': 24, 'resource_manager': 'None', 'scan_id':
'Anat_1', 'pipeline_config_yaml':
'/Volumes/Archive.ADS/ADS/analysis/qap-testdev-2/Anatomical.yml',
'subject_id': 'J31344', 'write_all_outputs': True, 'num_bundles_at_once':
1, 'session_id': 'w1', 'output_directory':
'/Volumes/Archive.ADS/ADS/analysis/qap-testdev-2', 'write_report': False,
'working_directory':
'/Volumes/Archive.ADS/ADS/analysis/qap-testdev-2/werk',
'template_skull_for_anat':
'/usr/local/fsl/data/standard/MNI152_T1_2mm.nii.gz', 'run_name':
'Anatomical', 'template_brain_for_anat':
'/usr/local/fsl/data/standard/MNI152_T1_2mm_brain.nii.gz', 'qap_type':
'anatomical_spatial'}
Traceback (most recent call last):
File
"/opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/qap_anatomical_spatial.py",
line 10, in
obj.run()
File
"/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/qap/cli.py",
line 244, in run
results = self._run_here(run_name)
File
"/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/qap/cli.py",
line 178, in _run_here
results.append(_run_workflow(a))
File
"/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/qap/cli.py",
line 358, in _run_workflow
if not op.isfile(resource_pool[resource]):
File
"/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/genericpath.py",
line 37, in isfile
st = os.stat(path)
TypeError: coercing to Unicode: need string or buffer, NoneType found
On Thu, Aug 18, 2016 at 12:15 PM, sgiavasis<EMAIL_ADDRESS>wrote:

Hi Seldamat,
For the run that produced those segmentation crash files- was this a run
you had started earlier, stopped, then started again? It looks like
something funny might have happened in the working directory and it just
can't find where to pick up from with segmentation.
I would try, at least for one of the crashed subjects, clearing out the
working directory for that one subject and re-running and seeing if that
crash still occurs.
Did you have any issues installing the 1.0.6_dev_parallel branch, by the
way?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/preprocessed-connectomes-project/quality-assessment-protocol/issues/59#issuecomment-240775256,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABfJPUg5F9esZJej6_XQyOqJNfJ1WGsKks5qhIU1gaJpZM4JfT04
.

How does your participant list look? First thing, I would double-check the filepaths of the "anatomical_scan" entries to see if any of them look off.

The paths all exist, I'm 100% sure of that -- I've rerun this a bunch of times now and I keep getting the same error message. Any suggestions?

Further up in the stream you printed above, do you have a "Contents of resource pool:" message? If you don't have the text anymore, you can also check the pypeline.log file.

@jpellman We should do some final runs/checks on this to make extra sure it's not still happening.


MSID: 88414 Version: 2 DOI: 10.1101/2<IP_ADDRESS>3421

MSID: 88414
Version: 2
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>3421
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=88414
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>3421

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/88414v2
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>3421
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/88414/v2/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c20) has a publication-type='other'. Is that correct?
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c26) has a publication-type='other'. Is that correct?
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c37) has a publication-type='other'. Is that correct?
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c39) has a publication-type='other'. Is that correct?