Need to "Activate" every time

Hi, I love this Eq, it works well. There is just one bug which bothers me. If I close Chrome (I'm on OS-X, all up to date) Eq won't work again until I open the icon and choose another preset, or change one of the slider in the current preset. It seems as it would be in a "Sleeping" state... My elderly mother always forget this, and sometimes even me myself until I few songs was played. I'd really appreciate if you could point me to the problem, or fix it if it's possible.
Thanks.

+1. Came here for this.

Hi, just adding some extra info. Now after some more use I have noticed that even without closing Chrome the above problem could occur. Sometimes when I open a YouTube video on a new tab the EQ won't come on. It is very random, mostly it is working automatically, at least until I have the first tab open where I made it active, but not always.


multi index signatures

TypeScript Version:  3.8.3
Search Terms: index signature
Code
type ExtendObj<T, Q> = {
  [key in keyof T]: T[key];
 // error
  [key1 in keyof Q]: Q[key1];
};

let foo = {
  foo:1
}
let bar = {
  bar:1
}

let foobar:ExtendObj<typeof foo,typeof bar> = {
  foo:1,
  bar:1
}

Expected behavior:
foobar can combine two object properties.
Actual behavior:
can't find "key1”。ts(2304)
can't find "keyof”。ts(2304)
In spec 3.9.4 Index Signatures  I find  An object type can contain at most one string index signature and one numeric index signature.
So Why we can't use multi-index signature ?
My suggestion we can offer better error for this situation
like Can't declare duplicate index signature ts(xxxx)! or add  multi-index signature feature.
Playground Link:
https://www.typescriptlang.org/play/index.html?ssl=1&ssc=1&pln=16&pc=2#code/C4TwDgpgBAogHsCA7AJgeQEYCsA8AVAGigEUA+KAXigG8AoKBqAbQGsIQoBLJKNkAewBmUPAF0AXCNbtRAbnoNpIAIxcefISQkklyubQC+82gBsIwKIP79KNBQyv9Jyw6fNQMAQwBOtuow8fZ1c3C0cvb0l4RFRMXFBITUciBIhNCPIqf0ZHZwJ7QMioFwMgA

You're not defining an index signature, you're creating a mapped type. An index signature would look like: [key: string]: Type, while a mapped type contains the in keyword.
You can easily create the desired result by using an intersection type or a conditional type:
type ExtendObj<T, Q> = {
    [key in keyof T]: T[key];
} & { [key in keyof Q]: Q[key] };

type ExtendObj2<T, Q> = {
    [key in (keyof T | keyof Q)]: key extends keyof T ? T[key] : key extends keyof Q ? Q[key] : never
}

In spec 3.9.4 Index Signatures I find An object type can contain at most one string index signature and one numeric index signature.

Forget the spec. TypeScript has no specification. The document you refer to is heavily outdated, it hasn't been updated in over 3 years.


We should be able to change a mesh's transform origin

Godot version:
Godot Engine v3.0.6.stable.official.8314054
OS/device including version:
Windows 10
Issue description:
We should be able to change a mesh's transform origin, so that we don't have to do things like e.g. adding a spatial as a parent. Besides that doesn't even work with meshLibraries and gridmaps

Meshes don't have a transform to begin with, so this would either be a destructive import step, or an extra transform on every mesh instance but I'm not sure how it would be manipulated / if everyone want to pay the price of this on every single mesh.

Just to clarify, because English isn't my mother language, I meant the pivot point also

Fixed by #35006.

@akien-mga This doesn't solve the issue with built in godot mesh shapes


Cannot scroll left or right on Floor 2

Start on Floor 1, you can "scroll" right with the right arrow key. When you click the escalator to go up, you come to Floor 2. You cannot "scroll" right or left with the right arrow key. When you click the escalator to go back down to Floor 1, you can still scroll on that floor.

Figured that out earlier tonight. Thought I hadn't pushed the bug to the server, but apparently did. Will push the local fix ASAP.

GO TO SLEEP
On Fri, Feb 27, 2015 at 12:29 AM, leodenault<EMAIL_ADDRESS>wrote:

Figured that out earlier tonight. Thought I hadn't pushed the bug to the
server, but apparently did. Will push the local fix ASAP.
—
Reply to this email directly or view it on GitHub
https://github.com/leodenault/fashion/issues/9#issuecomment-76338317.


Join us form select input not visible properly

Describe the bug
The select input in the join us form has a transparent background which makes it merge with the content behind, making it hard to select the domains and looks unprofessional.
To Reproduce
Steps to reproduce the behavior:

Go to join us page
Click on select button below interested domains
See error

Expected behavior
The background should be opaque and not transparent
Screenshots

fixed:

Desktop (please complete the following information):

OS: windows 10
Browser: firefox

Have you read the Code of Conduct?
Yes.

@Stiffpixels  thanks for pointing, along with the fix you mentioned, can you add this effect in select field? We get it in dark mode but not in light mode.

@Stiffpixels  thanks for pointing, along with the fix you mentioned, can you add this effect in select field? We get it in dark mode but not in light mode.

Sure will do.

@Kajol-Kumari  can you guide me through these errors I got while setting up the project I fixed the python2 error but now a new set of errors have emerged.

@Stiffpixels  yes, you should be on node version 14.19.0
I have added it in readme's installation guide - https://github.com/HITK-TECH-Community/Community-Website?tab=readme-ov-file#getting-started-


Add python to Readme build instructions

I'm following the build instructions and immediately hit with python runtime errors that I'm now diving into. The build instructions don't even mention that having python installed is a prerequisite / dependency of the build system -- can the build documentation be updated to list the requirements of the build environment?
8>------ Build started: Project: core_tables, Configuration: Release x64 ------
8>Building Custom Rule D:/projects/SPIRV-Tools-src/source/CMakeLists.txt
8>CMake does not need to re-run because D:\projects\SPIRV-Tools-src\build\source\CMakeFiles\generate.stamp is up-to-date.
8>Generate info tables for SPIR-V vunified1 core instructions and operands.
8>Traceback (most recent call last):
8>  File "D:/projects/SPIRV-Tools-src/utils/generate_grammar_tables.py", line 749, in <module>
8>    main()
8>  File "D:/projects/SPIRV-Tools-src/utils/generate_grammar_tables.py", line 612, in main
8>    import argparse
8>ImportError: No module named argparse

I've done this in #2424, where we make explicit that Python 2 is required, but we need to make sure it work in all of the environments that we care about.

This might change when we fix #1856.


Invalid html produced for 2 labels in classification

There is a label inversion in the HTML produced by LIME when the following conditions are met:

classification mode
only 2 labels
winning label is the first one

See https://github.com/marcotcr/lime/blob/master/lime/js/explanation.js#L23. If we modify it slightly to introduce some debug information:
let names = [`NOT ${this.names[label]}`, this.names[label]];
console.log("Names are in the general case:", names);
if (this.names.length == 2) {
  colors=[this.colors_i(0), this.colors_i(1)];
  names = this.names;
  console.log("Names are in this specific case:", names);
}

We get this output (with labels label1 and label2 for instance):
Names are in the general case: (2) ["NOT label1", "label1"]
Names are in this specific case: (2) ["label1", "label2"]

There is a clear mismatch in the transformation, leading to inverted results.
I'm working on a patch proposal.

Sorry for the long delay in responding. Let me just make sure this is wrong before I merge the pull request, because I think the behavior is as expected.
When we have two labels, we don't want each explanation to change what the right side is based on the predicted class (because that is confusing), so even if the prediction is the first one we want it to be on the left.
I think the results are still correct, see for example line 13 here, where we have the 3 conditions you listed.

Thanks for your comment :smiley:
Indeed, your example seems to work well. It seems that the issue comes from the "Tabular" case.
Here is a little toy test with a basic classifier.
import numpy as np
import lime
from lime.lime_tabular import LimeTabularExplainer

data = np.array([
    [12],
    [16],
])

features = ["temp"]
classes = ["cold", "hot"]

def toy_predictor(vectors):
    """
    This trivial predictor returns "cold" when temperature is less than 15 degrees.
    Otherwise, it returns "hot".
    """
    output = np.zeros((len(vectors), len(classes)))
    for i, v in enumerate(vectors):
        [temp] = v
        if temp > 15:
            output[i][1] = 1
        else:
            output[i][0] = 1
    return output

explainer = LimeTabularExplainer(data, feature_names=features, class_names=classes)
for d in data:
    exp = explainer.explain_instance(d, toy_predictor, num_features=1)
    exp.show_in_notebook()

The first "cold" case seems very wrong to me (as displayed), but maybe I'm not using lime properly?

The issue might comes from deeper levels in the labels orders, but here is the updated version that my PR proposes (it does not modify the output produced for the TextExplainer from what I can tell)

Ok, it seems that the version I first downloaded had an issue...
It was <IP_ADDRESS>, downloaded on october 4th with pip3.
I just cleared my workspace and retried from latest pip version (again, <IP_ADDRESS> but with a different hash?!)
This time (as you said) it works! :thinking:
So, this issue might be solved! Sorry for the trouble.
Please close this issue and the PR as you wish  :smiley:

Sorry you had the trouble to do this, but thanks for trying to help! I appreciate it!


Ecto.Query inspect missing on: with assoc

Environment

Elixir version (elixir -v): 1.7.0-dev
Database and version: 9.6
Ecto version (mix deps): master, 2.1.6
Database adapter and version (mix deps): master
Operating system: macOS X Sierra

Current behavior
for query:
from(x in Post, select: x.id, left_join: y in assoc(x, :comments), on: y.text == "foo")

we get inspect without on:
#Ecto.Query<from p in Ecto.Integration.Post,
 left_join: c in assoc(p, :comments), select: p.id>

note the generated SQL has it:
{"SELECT p0.\"id\" FROM \"posts\" AS p0 LEFT OUTER JOIN \"comments\" AS c1 ON (c1.\"post_id\" = p0.\"id\") AND (c1.\"text\" = 'foo')",

Expected behavior
#Ecto.Query<from p in Ecto.Integration.Post,
 left_join: c in assoc(p, :comments), on: c.text == "foo", select: p.id>

Closing in favor of #2478


RollupError when using Nuxt 3.13.1 with Nuxt 4 compatibility mode

So far the nuxt-graphql-middleware module was working fine in Nuxt 4 compatibility mode, but after upgrading to Nuxt 3.13.1 the following error occurs during nuxi build:

[nitro 8:24:16 AM]  ERROR  RollupError: playground/node_modules/.cache/nuxt/.nuxt/graphqlMiddleware.serverOptions.ts (2:12): Expected ',', got '{' (Note that you need plugins to import files that are not JavaScript)

1:
2: import type { GraphqlMiddlewareServerOptions } from '../../../../../src/types'
               ^
3: const serverOptions: GraphqlMiddlewareServerOptions = {}
4: import type { GraphqlServerResponse } from '#graphql-middleware/types'

 ERROR  playground/node_modules/.cache/nuxt/.nuxt/graphqlMiddleware.serverOptions.ts (2:12): Expected ',', got '{' (Note that you need plugins to import files that are not JavaScript)                8:24:16 AM

  at getRollupError (node_modules/.pnpm/rollup@4.21.2/node_modules/rollup/dist/es/shared/parseAst.js:392:41)
  at ParseError.initialise (node_modules/.pnpm/rollup@4.21.2/node_modules/rollup/dist/es/shared/node-entry.js:11494:28)
  at convertNode (node_modules/.pnpm/rollup@4.21.2/node_modules/rollup/dist/es/shared/node-entry.js:13192:10)
  at convertProgram (node_modules/.pnpm/rollup@4.21.2/node_modules/rollup/dist/es/shared/node-entry.js:12536:12)
  at Module.setSource (node_modules/.pnpm/rollup@4.21.2/node_modules/rollup/dist/es/shared/node-entry.js:14355:24)
  at async ModuleLoader.addModuleSource (node_modules/.pnpm/rollup@4.21.2/node_modules/rollup/dist/es/shared/node-entry.js:19046:13)

 ERROR  playground/node_modules/.cache/nuxt/.nuxt/graphqlMiddleware.serverOptions.ts (2:12): Expected ',', got '{' (Note that you need plugins to import files that are not JavaScript)                8:24:16 AM

 ELIFECYCLE  Command failed with exit code 1.

I was able to reproduce this by cloning this repo, upgrading the packages and adding this to nuxt.config.ts in the playground:
  future: {
    compatibilityVersion: 4
  },

I added a reproduction here: https://github.com/vernaillen/nuxt-graphql-middleware-rolluperror
Also set srcDir to ./  to make the app work with "npm run dev".
The build error occurs when running "npm run dev:build"

I managed to install on Vercel and Coolify by using this as build command:
npx nuxi cleanup && rm -rf .nuxt && pnpm build
The issue seems to be caused by the new buildCache feature introduced in Nuxt 3.13.1 and I have the impression this feature can't be disabled when using Nuxt 4 compatibility mode.
The above command removes the build cache created by previous deployment(s)

So this seems to be due to the new "app" folder structure. I wonder how Nuxt 4 works with the previous "app/router.options.ts" file? But it seems that there is still no official way for module authors to implement "runtime options that are functions". I'll have to see what the solution here is.

@dulnan Thanks for looking into it. If it helps, I also get this error when not using the new app folder structure. So I still have everything on my root and then a app/graphqlMiddleware.serverOptions.ts file.
The Nuxt 4 Upgrade Docs at https://nuxt.com/docs/getting-started/upgrade#new-directory-structure state, that Nuxt 4 looks for the router.options.ts file in the new app directory root, so the path is still app/router.options.ts

I think I've already found a way to fix it. Looking at the upgrade guide, with Nuxt 4 the correct place to put the file would be in ./server/graphqlMiddleware.serverOptions.ts, because app is exclusively for "Nuxt App" stuff (and the serverOptions are only ever used in a Nitro context, so they actually do belong there). That should likely also give DX improvements because currently you "can use" Nuxt composables in this file (according to TypeScript), but it would fail in runtime because these composables are not actually auto imported. I will probably change the expected path to be in ./server in an upcoming release, which should then fix this issue here as well.
Backwards compatibility should also be possible I think. Let's see

Went into a similar issue where schemaPath: 'server/linear/schema.graphql' was resolving to app/server/linear/schema.graphql
I also believe most of the configurable files paths  should use serverDir instead of srcDir .
Had the same problem in an other nuxt module and it was retrocompatible with nuxt 3

Started working on adding Nuxt 4 compatibility. The bug mentioned in this issue has been resolved: I'm now generating two separate templates (.mjs and .d.ts) instead of a single template (.ts), the latter is what causes the rollup build error. And it seems this just happened to work previously and is not really supported.
@blqke Indeed the paths should not resolve via srcDir. You mentioned serverDir instead. I guess for the graphqlMiddleware.options.ts file using the server dir makes sense, since the file is exclusively used in a server context. However, for schemaPath or autoImportPatterns, the rootDir would likely make more sense. WDYT?

Started working on adding Nuxt 4 compatibility. The bug mentioned in this issue has been resolved: I'm now generating two separate templates (.mjs and .d.ts) instead of a single template (.ts), the latter is what causes the rollup build error. And it seems this just happened to work previously and is not really supported.
@blqke Indeed the paths should not resolve via srcDir. You mentioned serverDir instead. I guess for the graphqlMiddleware.options.ts file using the server dir makes sense, since the file is exclusively used in a server context. However, for schemaPath or autoImportPatterns, the rootDir would likely make more sense. WDYT?

Yes I agree, it make sense, people should have the ability to store .gql near .vue if they want cf https://github.com/dulnan/nuxt-graphql-middleware/blob/d3f7dc62cb5acb8683411416ed300acceeacff78/docs/configuration/full-example.md?plain=1#L38

I've tested it in several of my own projects (without compatibilityVersion: 4) to make sure it doesn't break existing setups. The module's playground uses compatibilityVersion: 4 where it also works fine. With the upcoming release the default path for the server options file will be <serverDir>/graphqlMiddleware.serverOptions.ts, however the module still checks for the legacy path in app for backwards compatibility. In addition the alias/resolving has been cleaned up, so you should be able to use schemaPath: 'server/schema.graphql' or schemaPath: '~/schema.graphql' and it will resolve correctly. Same is true for autoImportPatterns.


add a safety check for invalid request

IndieAuth\Client (https://github.com/indieweb/indieauth-client-php) does not send 'me' in the query parameters.
This change should more gracefully handle that issue.

I have also added a change to IndieAuth\Client to support this: https://github.com/indieweb/indieauth-client-php/pull/26

It seems like there is already a commit here that would eliminate this, but it is not merged to master: https://github.com/Zegnat/php-mintoken/compare/master...no-more-me


Add support for title to be pulled from dataset (measure)

PowerBI visuals sometimes let you use a measure for text-based fields like the title.
This might allow for quicker automation of titles.

Done in #26


Unresolved project-to-project reference

I am having the issue with missing namespaces on latest everything (Windows 10, vs & msbuild 16.7, vscode 1.47.3, omnisharp is 'latest' and pre-release v1.23.0-beta2 ).

Steps to Reproduce
I just open the project in VSCode. Opening it in VS or running it with dotnet CLI works normally.
OmniSharp log
My debug log of omnisharp is here ( 'latest' version)

11.35.5-beta.80 - https://gist.github.com/majkinetor/d7985109c607ca9420e07cc4a2627f61
1.36.0 - https://gist.github.com/majkinetor/46cb9c6b4fa9d27832bad1d9782c8a4c

C# log
Installing C# dependencies...
Platform: win32, x86_64
Downloading package 'OmniSharp for Windows (.NET 4.6 / x64)' (35348 KB).................... Done!
Validating download...
Integrity Check succeeded.
Installing package 'OmniSharp for Windows (.NET 4.6 / x64)'
Downloading package '.NET Core Debugger (Windows / x64)' (42010 KB).................... Done!
Validating download...
Integrity Check succeeded.
Installing package '.NET Core Debugger (Windows / x64)'
Downloading package 'Razor Language Server (Windows / x64)' (50405 KB).................... Done!
Installing package 'Razor Language Server (Windows / x64)'
Finished

Environment information
VSCode version: 1.47.3
C# Extension: 1.23.0
Dotnet Information
.NET Core SDK (reflecting any global.json):
 Version:   3.1.400
 Commit:    035fb2aa2f
Runtime Environment:
OS Name:     Windows
OS Version:  10.0.19041
OS Platform: Windows
RID:         win10-x64
Base Path:   C:\Program Files\dotnet\sdk\3.1.400\
Host (useful for support):
Version: 3.1.6
Commit:  3acd9b0cd1
.NET Core SDKs installed:
3.1.400 [C:\Program Files\dotnet\sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.20 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.20 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.0.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.1.20 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.0.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.0.3 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 3.1.6 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download

Visual Studio Code Extensions

Extension
Author
Version

align-by-regex
janjoerke
1.0.4

align-mode
Gruntfuggly
0.0.21

better-align
wwm
1.1.6

better-toml
bungcip
0.3.2

Bookmarks
alefragnani
11.3.1

chat
karigari
0.35.0

code-settings-sync
Shan
3.4.3

codestream
CodeStream
8.3.1

codetour
vsls-contrib
0.0.34

csharp
ms-dotnettools
1.23.0

dakara-foldplus
dakara
1.4.1

emojisense
bierner
0.7.0

excel-to-markdown-table
csholmq
1.2.2

filter-lines
earshinov
0.2.0

gistfs
vsls-contrib
0.1.8

gitlab-workflow
GitLab
3.2.0

gitlens
eamodio
10.2.2

haml
karunamurti
1.3.0

hexeditor
ms-vscode
1.2.1

markdown-all-in-one
yzhang
3.2.0

markdown-checkbox
bierner
0.1.3

markdown-pdf
yzane
1.4.4

output-colorizer
IBM
0.1.2

pdf
tomoki1207
1.1.0

plantuml
jebbs
2.13.13

powershell
ms-vscode
2020.6.0

project-manager
alefragnani
11.1.0

remote-containers
ms-vscode-remote
0.128.0

remove-empty-lines
usernamehw
0.0.6

restructuredtext
lextudio
129.0.0

ruby
rebornix
0.27.0

spellright
ban
3.0.52

swagger-viewer
Arjun
3.0.1

todo-tree
Gruntfuggly
0.0.178

vetur
octref
0.26.1

vscode-autohotkey
slevesque
0.2.2

vscode-docker
ms-azuretools
1.4.1

vscode-format-context-menu
lacroixdavid1
1.0.4

vscode-JS-CSS-HTML-formatter
lonefy
0.2.3

vscode-postgres
ckolkman
1.1.11

vscode-ruby
wingrunr21
0.27.0

vscode-solution-explorer
fernandoescolar
0.3.10

vscode-sql-formatter
adpyke
1.4.4

vscode-table-formatter
shuworks
1.2.1

vscode-textile-preview
GehDoc
1.3.4

vscode-todo-highlight
wayou
1.0.4

vscode-xml
redhat
0.13.0

vscode-yaml
redhat
0.9.1

vsliveshare
ms-vsliveshare
1.0.2478

NOTE: Initially reported here

if you don't wish to share this project, perhaps you could create a simple repro with this problem and provide that instead.

Here is the complete code: service.zip

thanks a lot.
the problem is the usage of $(SolutionName) moniker in project references, which we don't resolve correctly - this is likely a bug in our MSBuild project loader. A workaround would be to get rid of $(SolutionName) and using proper names resolves the problem e.g.:

Thanks a lot @filipw for fast and right response, this fixed my problem.


Closing #30 by connecting to Heroku

A couple questions:

Is there a way to have automate the deployment process to heroku?  I've set up a script in package.json to run all the build commands in the past, so maybe we could do that again, or maybe heroku supports that somewhere.

Can we get an update to the README going for deploying to Heroku?

@phuchle

Is there a way to have automate the deployment process to heroku? I've set up a script in package.json to run all the build commands in the past, so maybe we could do that again, or maybe heroku supports that somewhere.

Heroku Dashboard supports auto-deployments for specific branches and we can set up pipelines there. I know the auto-deployments can build the pages we want but won't do "react-scripts build" since it only installs dependencies and not DevDepends. I think to achieve this you would want to use the Pipeline feature which I haven't deep-dived yet.

Can we get an update to the README going for deploying to Heroku?

I can write one if we need it, but it would probably be mostly around Heroku since the only thing we have to do in AAF is locally run npm build then push up the resulting build folder.

@rainrivas

Heroku Dashboard supports auto-deployments for specific branches and we can set up pipelines there. I know the auto-deployments can build the pages we want but won't do "react-scripts build" since it only installs dependencies and not DevDepends. I think to achieve this you would want to use the Pipeline feature which I haven't deep-dived yet.

OK, I think that can be saved until later on in the dev. pipeline.

I can write one if we need it, but it would probably be mostly around Heroku since the only thing we have to do in AAF is locally run npm build then push up the resulting build folder.

Yeah that would be great.  Can we review the steps on discord whenever you're free so I can learn how the deployment goes down?

@phuchle Yeah I think for now we can keep the build files but we definitely want to revisit later. However, in the end when we host this, we would be pushing build files and storing them on the server. I really do think that setting up the pipeline process has to be done eventually.
I can show everyone how to use the Heroku environment. If any of the team members don't have access to Heroku I can add them later too.

@rainrivas @phuchle
If heroku reads from the designated branch build folder, could we just make sure our build script sets up everything we need, if not, would we need to consider looking into a simple task runner like gulp?

@jwu910 I think webpack handles the compiling and transpiling. All heroku does (right now) is read the build folder that react-scripts creates. Eventually we should sophisticate our pipeline to include more than 1 step. We can discuss this over discord in more detail on tuesday


Refactor loaders

A proposal to refactor the giant loaders.js file:

Have helpers in server/graphql/loaders/helpers.ts
Create loaders in files like server/graphql/loaders/comments.ts
Tie everything up in server/graphql/loaders/index.js

Moved server/graphql/loaders/comments.ts for demonstration purpose.

Also introduced a sortResultsSimple that does the same job as sortResults but without any magic implemented.

@Betree uhm, this will heavily conflict with https://github.com/opencollective/opencollective-api/pull/2981

I missed that in https://github.com/opencollective/opencollective-api/pull/2981, let's wait for it to be merged, the changes in this PR can easily be re-done if needed.

Hello, I think it's a great idea to split loaders.js, it was a headache to work on such a big file and now it's hard to review all the changes.
If you think it's necessary I can adapt the pull-request again after you split the file.
Whatever you want to happen first is fine with me.

@gmarcos87 Agree that the length of this file makes it hard to work with :wink:
But let's prioritize https://github.com/opencollective/opencollective-api/pull/2981 over this one, it's a far more important change. I did this revamp cause I needed to add a loader and wanted to do it clean, but there's no rush.

Rebased the PR upon changes from https://github.com/opencollective/opencollective-api/pull/2981.
It's very similar to the initial change, main difference is that loaders should now export functions instead of objects so that we can pass down the request and the cache (see generateCommentsLoader).

Hi @betree, So far everything look fine, you're going to create a file for each dataloader right?
I recommend running the E2E test before the merge, in the case of #2981 detected a bug that api's tests do not catch.
PS: Is there any preference on the use of typescript over javascirpt? So I take it into account for future contributions.

So far everything look fine, you're going to create a file for each dataloader right?

@gmarcos87 I was thinking of grouping them by business unit (one file for collectives, one for expenses, one for contributors...etc).

I recommend running the E2E test before the merge, in the case of #2981 detected a bug that api's tests do not catch.

@gmarcos87 Should be fine, I tested the endpoints manually.

Is there any preference on the use of typescript over javascirpt? So I take it into account for future contributions.

As per https://github.com/opencollective/opencollective/blob/1d2b8016f64e79390724a82d4707943da46bbd8f/rfcs/006-typescript.md#L53-L55:

We don't have a plan to migrate the existing codebase for now, nor to enforce it for all new
developments. However, we should encourage its usage for issues like https://github.com/opencollective/opencollective/issues/2274
where type checking and interfaces have a lot of benefits to offer.

For dataloaders I think it's interesting because we can easily specify the expected input and return types, see for example https://github.com/opencollective/opencollective-api/blob/bc396bf6753f9cbab493e1da3d075a91c5195ddb/server/graphql/loaders/conversation.ts#L4-L7

@znarf I'd like to remove createDataLoaderWithOptions. It was introduced in https://github.com/opencollective/opencollective-api/pull/1005 to cache the created DataLoader but because dataloaders are instantiated only once per request I don't understand what's its purpose. Do you have more insights?

@Betree I'm not sure, feel free to remove it and ship that in an isolated deploy so we can monitor the impact in production performance

@znarf Alright, I'm merging this PR as-is and will follow up with createDataLoaderWithOptions separately


More examples on Either chaining

There is no enough examples on using Either when multiple function calls chained together, and each function could return an error using Either.left(...).

We removed Either.left() and Either.right(). See #2286


Provide a publicly-accessible Core ID

Allow distinguishing between multiple Cores and associating data with
them through a HashMap or similar.
This is a proposal for #147.

Could the Ord and PartialOrd implementations get dropped for now? I wouldn't want anything accidentally relying on an unintentional ordering.
I think it may also be worth documenting that ids are never recycled. I doubt anyone's going to create more than 2^32 event loops in one process...

I don't mind dropping them, I was thinking someone might prefer using Map instead of HashMap, but I don't see a good reason for anyone wanting to do that.
I tried to add that documentation. Though, I'm not 100% sure someone won't try creating so many event loops, people do all kinds of crazy stuff, and someone might be creating a short-lived event loops and then drooping them for some reason. But that's certainly out of the scope of this issue.
(I hope you don't mind me just force-pushing an amended commit ‒ usually I stack fixup commits and squash them before merge to make reviewing the new changes easier, but this seems like a very small thing to bother)

Well, technically I'd say 2^32 loops easily possible.
Consider some curl-like library creates a loop on curl::fetch(), just because providing a synchronous API on top of async is a very sensible thing. And you can have a long running crawler that does fetches in multiple threads. You know, making just a 1000 requests per second in such a system will overflow a counter in 49 days :)

@tailhook We could change the usize to u64, but u64 atomic is still unstable (https://github.com/rust-lang/rust/issues/32976), so it would need to be under a mutex currently (which probably isn't that bad, creating new loops wouldn't be performance-sensitive operation).
But as this limitation isn't brought in by this PR, should we create a separate issue for that?

@tailhook heh true! If we stick with the opaque representation as-is though then we're at least flexible to add more bits in the future :)


Support for lints with extended contexts

:bow: request for an issue description. I can infer from the link to #581 and the title but it would be better for everyone if we can capture more context here.


View Log option is  not available

Describe the bug
The view publish log arrow / option is not visible for the certain screen sizes. Please refer below screen shot
Version
V2.1.1
OS

[ ] macOS
[x] Windows
[ ] Ubuntu

Expected behavior
View log option should be available
Screenshots

Additional context
Screen size:

HI @sarul84 we have added this work item to the backlog for future iterations.


[$250] Key Navigation - Pressing CTRL+K in attachment and closing search, leads to different chat

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.25-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4891152&group_by=cases:section_id&group_order=asc&group_id=229066
Issue reported by: Applause - Internal Team
Action Performed:

Open the staging.new.expensify website
Open any chat in which an attachment was sent
Click the attachment to open preview modal
Press CTRL+K to open search page
Dismiss the opened search page
Verify if you are redirected to the correct chat

Expected Result:
When the user opens the preview modal of an attachment in any chat, presses CTRL+K and closes the search page, the website should return to the same chat where the user was in
Actual Result:
After the user opens the preview modal of an attachment in any chat, presses CTRL+K and closes the search page, is redirected to a different chat
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/user-attachments/assets/3db4ac96-4a3d-4e9d-8e90-f5180e3f55b7
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01212d967034d02032
Upwork Job ID:<PHONE_NUMBER>564304374
Last Price Increase: 2024-09-13

Issue OwnerCurrent Issue Owner: @DylanDylann

@kevinksullivan  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

Proposal
Please re-state the problem that we are trying to solve in this issue.
Key Navigation - Pressing CTRL+K in attachment and closing search, leads to different chat
What is the root cause of that problem?
When press the shortcut key Modal.close will be called here
https://github.com/Expensify/App/blob/e32430cf15b3fcdf35e8d43f82c027fea50c20d3/src/libs/Navigation/AppNavigator/AuthScreens.tsx#L308
This will call the modal onClose here
https://github.com/Expensify/App/blob/e32430cf15b3fcdf35e8d43f82c027fea50c20d3/src/libs/actions/Modal.ts#L29-L37
the onModalClose in this case is this
https://github.com/Expensify/App/blob/e32430cf15b3fcdf35e8d43f82c027fea50c20d3/src/pages/home/report/ReportAttachments.tsx#L41-L44
Which dismissModal and it will pop the report attachment modal route but this onModalClose will be called again via onModalDidClose (because the modal itself calls the onModalDidClose on its onModalHide) here
https://github.com/Expensify/App/blob/e32430cf15b3fcdf35e8d43f82c027fea50c20d3/src/libs/actions/Modal.ts#L52-L57
so another pop on the route will navigate the user to another report
What changes do you think we should make in order to solve the problem?

In closeTop here, we need to pop the last closeModals becasue there is no need we will call the onClose of the topmost modal again after it is called  here
https://github.com/Expensify/App/blob/e32430cf15b3fcdf35e8d43f82c027fea50c20d3/src/libs/actions/Modal.ts#L28-L37
    if (onModalClose) {
        closeModals[closeModals.length - 1](isNavigate);
        closeModals.pop();
        return;
    }
    closeModals[closeModals.length - 1]();
    closeModals.pop();

What alternative solutions did you explore? (Optional)

@FitseTLT Could you reproduce this issue anymore?

@DylanDylann The reason you are not reproducing it for report attachment is because of this pr which tried to solve the same problem with wrong RCA and wrong solution. So instead of solving the issue from the root cause they applied a partial fix to report attachment so the problem still exists for other modals such as receipt attachment (Transaction Receipt), here is a video:
the page navigates back from transaction details page to the iou report page when CTRL+K, so I suggest we revert that fix and apply the right fix that solves problem from the root cause.
https://github.com/user-attachments/assets/7f9def89-e53c-4394-bbef-4f3e5dd326ca

On my list today

@kevinksullivan I think this should be handled in https://github.com/Expensify/App/issues/46388 I added a comment to the original issue. We can close this one

@DylanDylann the issue is payedout/closed and way past its regression period, how is that suppose to be handled there while I have found the correct root cause and solution here.
CC @kevinksullivan

@dominictb / @allgandalf Can you comment on the proposal? Ideally, if this can resolve all cases - we should undo the fix and have this fixed universally

Agree with @thienlnam that it's worth addressing the broader issue if we can.

Also going OOO so I'm looping in another BZ

Sorry, was OoO myself when this was assigned!

@DylanDylann where are we at with this?

@dominictb @allgandalf Bump on this comment: https://github.com/Expensify/App/issues/48113#issuecomment-2344360516

@allgandalf Here: https://github.com/Expensify/App/issues/48113#issuecomment-2328734043 Please help to check

@allgandalf @dominictb Thanks for your response. Hmm, I think we will handle the new bug that @FitseTLT mentioned separately in this issue. It is hard to say this is a regression from the previous PR because this bug is in another place and isn't known at that time. The previous issue also be closed 2 weeks ago.
I will review @FitseTLT's proposal and handle this as a new issue

@dominictb Would you like to post your proposal to fix this bug globally on this issue? It looks promising

@FitseTLT The same bug still happen when reloading page
https://github.com/user-attachments/assets/1ecc4e7a-3ab8-4678-a27f-ad2b0690d81f

@FitseTLT The same bug still happen when reloading page
Screen.Recording.2024-09-24.at.16.40.04.mov

@DylanDylann What you found here is a totally different bug that is not occuring because onMOdalHide is being called twice as the main bug here but it is caused by Navigation.goBack being called without fallbackRoute because we haven't passed shouldEnforceFallback true. We have options to solve this

We can use dismissModal with report id here
https://github.com/Expensify/App/blob/a99cf941a355a412e7498c41a69a99b01e35431c/src/pages/TransactionReceiptPage.tsx#L68

                Navigation.dismissModal(report?.reportID ?? '-1');

Because dismissModal correctly handles the case of transaction receipt page here ( and also dismissModal is the most appropriate as we are dismissing a modal)
https://github.com/Expensify/App/blob/a99cf941a355a412e7498c41a69a99b01e35431c/src/libs/Navigation/dismissModalWithReport.ts#L42
2. We can also pass shouldEnforceFallback to goBack
                Navigation.goBack(ROUTES.REPORT_WITH_ID.getRoute(report?.reportID ?? '-1'), true);

Let's go with @FitseTLT's proposal. Please include the change to address this bug
🎀 👀 🎀 C+ reviewed

@CortneyOfstad This is ready for payment. The PR is deployed to production on 1/10

Payment Summary
@DylanDylann — paid $250 via Upwork
@FitseTLT — pid $250 via Upwork


Fix typo and link

The README for the hint component referred to a "label". The jump-link also needed to be updated.

Thanks @frankieroberto :)


RN > 0.59 bug fix

https://github.com/react-native-community/lottie-react-native/issues/253

Summary

Test Plan

What's required for testing (prerequisites)?
What are the steps to reproduce (after prerequisites)?
Compatibility

OS
Implemented

iOS
✅❌

Android
✅❌

Checklist

[x] I have tested this on a device and a simulator
[ ] I added the documentation in README.md
[ ] I mentioned this change in CHANGELOG.md
[ ] I updated the typed files (TS and Flow)
[ ] I added a sample use of the API in the example project (example/App.js)

merge this pr please

@emilioicai do you have any idea when this will be released?

@BrendanJMurray I'm planning a release for today


removed ruby1.9.3 and jruby-19mode from travis.yml

bundler cannot install the required mime-types-data version on the rubies that have been removed in this PR.

closing because admittedly this isn't the best solution


Feature Request: Auto minimize NERDTree window

Can NERDTree window be minimized automatically when opening a file node (o, go, i, gi, s, gs)?

+1

@lifecrisis I propose this way of implementing the request: If zoomed (using key A) and a file is chosen to be opened, and NERDTreeQuitOnOpen == 0, then set NERDTree's width back to the NERDTreeWinSize value.

Implemented by #870.


Updater - Bug - Updater sometimes incorrectly thinks package was not updated when it was

(This might only apply to the latest version of the updater)

This is most likely caused by the updates/refactoring to getPackageInstalledVersion in src/Model/Cli/Runner/Composer.php which is run by the Updater in updateMinorComposerDependency


bind: 9.18.0 -> 9.18.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/bind/versions.
meta.description for bind is: "Domain name server"
meta.homepage for bind is: "https://www.isc.org/bind/"
meta.changelog for bind is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
Warning: no invocation of /nix/store/8cnaxlrmq22blw7idqr1mzvzxspcnmpi-bind-9.18.1/bin/named-compilezone had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/8cnaxlrmq22blw7idqr1mzvzxspcnmpi-bind-9.18.1/bin/named-checkzone had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/8cnaxlrmq22blw7idqr1mzvzxspcnmpi-bind-9.18.1/bin/dnssec-dsfromkey had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/8cnaxlrmq22blw7idqr1mzvzxspcnmpi-bind-9.18.1/bin/dnssec-settime had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/8cnaxlrmq22blw7idqr1mzvzxspcnmpi-bind-9.18.1/bin/dnssec-verify had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/8cnaxlrmq22blw7idqr1mzvzxspcnmpi-bind-9.18.1/bin/tsig-keygen had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/8cnaxlrmq22blw7idqr1mzvzxspcnmpi-bind-9.18.1/bin/nsec3hash had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/8cnaxlrmq22blw7idqr1mzvzxspcnmpi-bind-9.18.1/bin/dnssec-signzone had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/8cnaxlrmq22blw7idqr1mzvzxspcnmpi-bind-9.18.1/bin/ddns-confgen had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/8cnaxlrmq22blw7idqr1mzvzxspcnmpi-bind-9.18.1/bin/dnssec-importkey had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/8cnaxlrmq22blw7idqr1mzvzxspcnmpi-bind-9.18.1/bin/named-journalprint had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/8cnaxlrmq22blw7idqr1mzvzxspcnmpi-bind-9.18.1/bin/dnssec-cds had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/8cnaxlrmq22blw7idqr1mzvzxspcnmpi-bind-9.18.1/bin/dnssec-revoke had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/8cnaxlrmq22blw7idqr1mzvzxspcnmpi-bind-9.18.1/bin/dnssec-keygen had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/8cnaxlrmq22blw7idqr1mzvzxspcnmpi-bind-9.18.1/bin/rndc-confgen had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/8cnaxlrmq22blw7idqr1mzvzxspcnmpi-bind-9.18.1/bin/arpaname had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/8cnaxlrmq22blw7idqr1mzvzxspcnmpi-bind-9.18.1/bin/mdig had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/8cnaxlrmq22blw7idqr1mzvzxspcnmpi-bind-9.18.1/bin/named-rrchecker had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/8cnaxlrmq22blw7idqr1mzvzxspcnmpi-bind-9.18.1/bin/rndc had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/8cnaxlrmq22blw7idqr1mzvzxspcnmpi-bind-9.18.1/bin/named had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/8cnaxlrmq22blw7idqr1mzvzxspcnmpi-bind-9.18.1/bin/dnssec-keyfromlabel had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/8cnaxlrmq22blw7idqr1mzvzxspcnmpi-bind-9.18.1/bin/named-checkconf had a zero exit code or showed the expected version
0 of 22 passed binary check by having a zero exit code.
0 of 22 passed binary check by having the new version present in output.
found 9.18.1 with grep in /nix/store/8cnaxlrmq22blw7idqr1mzvzxspcnmpi-bind-9.18.1
found 9.18.1 in filename of file in /nix/store/8cnaxlrmq22blw7idqr1mzvzxspcnmpi-bind-9.18.1

Rebuild report (if merged into master) (click to expand)

42 total rebuild path(s)

34 package rebuild(s)

34 x86_64-linux rebuild(s)
8 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
acme-sh
autofs5
bashSnippets
bind
blueberry
check-wmiplus
cinnamon.cinnamon-common
cinnamon.cinnamon-gsettings-overrides
cinnamon.cinnamon-screensaver
cinnamon.cinnamon-session
cinnamon.cjs
cinnamon.nemo
cinnamon.pix
cinnamon.warpinator
cinnamon.xapps
cinnamon.xreader
cinnamon.xviewer
dig
dnsutils
dwm-status
host
inxi
monitoring-plugins
nmapsi4
python310Packages.xapp
python39Packages.xapp
sssd
tests.nixos-functions.nixos-test
tests.nixos-functions.nixosTest-test
tests.trivial-builders.references
testssl
twa
xed-editor
xplayer

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/8cnaxlrmq22blw7idqr1mzvzxspcnmpi-bind-9.18.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A bind https://github.com/r-ryantm/nixpkgs/archive/87657e9158eb37d7a4e7137c756d5dc122f7eb1b.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/8cnaxlrmq22blw7idqr1mzvzxspcnmpi-bind-9.18.1
ls -la /nix/store/8cnaxlrmq22blw7idqr1mzvzxspcnmpi-bind-9.18.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @globin for testing.

FWIW this fixed bind not compiling for me on aarch64.

FWIW this fixed bind not compiling for me on aarch64.

but ofborg can build it :thin

@SuperSandro2000 what I mean is that when I updated my system, nix tried to install bind 9.18.0, which failed.It also seems to fail in hydra – https://hydra.nixos.org/build/168894692. Not 100% sure if I had the exact same failure. And using package from this PR it worked correctly.
Anyway, I have just noticed that this PR was already merged – https://github.com/NixOS/nixpkgs/pull/164586 – so this one can be probably closed?


Refactor doppler to hide internals

This is the first part of the doppler app refactor. This moves all of the implementation details into the internal directory to prevent them from being linked against. I also fixed a few tests that were broken on Go 1.8 and used gobindata for fixture files that were not working correctly on my mac.

@enocom This is ready for you to click Rebase and merge when you are ready.  scripts/test passed and I built and deployed most of the release. Consul was having issues so I didn't get to run LATs.


Sysbuild-configured project using west flash --recover will wrongly recover (and reset) the MCU each time it flashes an image

Describe the bug
Issue noticed whilst testing https://github.com/zephyrproject-rtos/zephyr/pull/49552
It seems that with a sysbuild project, with multiple images e.g. sample application and mcuboot, using west flash --recover will wrongly have the west flash runner recover the module for every instance it is used, which results in a non-working board. It also resets the board after each programming cycle, which can cause issues if e.g. readback protection is enabled or if an application needs something else to start, in which case the following programming cycles will fail.
Output:
west flash --recover
WARNING: can't find the zephyr repository
 - no --zephyr-base given
 - ZEPHYR_BASE is unset
 - west config contains no zephyr.base setting
 - no manifest project has name or path "zephyr"

 If this isn't a Zephyr workspace, you can   silence this warning with something like this:
   west config zephyr.base not-using-zephyr
-- west flash: rebuilding
[0/9] Performing build step for 'test_mcuboot'
ninja: no work to do.
[1/9] Performing build step for 'swapped_app'
ninja: no work to do.
[3/9] Performing build step for 'mcuboot'
ninja: no work to do.
[9/9] Completed 'mcuboot'
-- west flash: using runner nrfjprog
-- runners.nrfjprog: mass erase requested
Using board 483128317
-- runners.nrfjprog: Recovering and erasing flash memory for both the network and application cores.
Recovering device. This operation might take 30s.
Writing image to disable ap protect.
Erasing user code and UICR flash areas.
Recovering device. This operation might take 30s.
Writing image to disable ap protect.
Erasing user code and UICR flash areas.
-- runners.nrfjprog: Flashing file: /tmp/bb/zephyr/twister-out/bl5340_dvk_cpuapp/tests/boot/test_mcuboot/boot.mcuboot/mcuboot/zephyr/z
ephyr.hex
Parsing image file.
Verifying programming.
Verified OK.
Applying pin reset.
-- runners.nrfjprog: Board with serial number 483128317 flashed successfully.
-- west flash: using runner nrfjprog
Using board 483128317
-- runners.nrfjprog: Recovering and erasing flash memory for both the network and application cores.
Recovering device. This operation might take 30s.
Writing image to disable ap protect.
Erasing user code and UICR flash areas.
Recovering device. This operation might take 30s.
Writing image to disable ap protect.
Erasing user code and UICR flash areas.
-- runners.nrfjprog: Flashing file: /tmp/bb/zephyr/twister-out/bl5340_dvk_cpuapp/tests/boot/test_mcuboot/boot.mcuboot/swapped_app/zeph
yr/zephyr.signed.hex
Parsing image file.
Verifying programming.
Verified OK.
Applying pin reset.
-- runners.nrfjprog: Board with serial number 483128317 flashed successfully.
-- west flash: using runner nrfjprog
Using board 483128317
-- runners.nrfjprog: Recovering and erasing flash memory for both the network and application cores.
Recovering device. This operation might take 30s.
Writing image to disable ap protect.
Erasing user code and UICR flash areas.
Recovering device. This operation might take 30s.
Writing image to disable ap protect.
Erasing user code and UICR flash areas.
-- runners.nrfjprog: Flashing file: /tmp/bb/zephyr/twister-out/bl5340_dvk_cpuapp/tests/boot/test_mcuboot/boot.mcuboot/test_mcuboot/zep
hyr/zephyr.signed.hex
Parsing image file.
Verifying programming.
Verified OK.
Applying pin reset.
-- runners.nrfjprog: Board with serial number 483128317 flashed successfully.

To Reproduce
Build PR sample application for an nrf5340-based board and manually run west flash --recover in the build directory
Expected behavior
One recovery - at the start of the programming process.
One reset - after all images have been programmed.
Impact
Showstopper
Environment (please complete the following information):

OS: Linux
Toolchain: Zephyr SDK 0.15.0
Commit SHA or Version used: https://github.com/zephyrproject-rtos/zephyr/pull/49552 but should apply with current main

CC @tejlmand @mbolivar-nordic probably need to plan how this works in future

this is not a bug, but using runner specific arguments on multiple domains are considered experimental at current stage.
There was however a flaw in warning printed, that it was not printed until 2 or more arguments were used.

closed, as this is experimental feature, and the issue regarding correct printing of the error message has been fixed here: #50422

Reopening this as this is becoming a big problem with sysbuild, there are 2 issues here:

Sysbuild will reset after each image has been flashed, with the case of the nRF5340 which has application readback protection, this can mean that this security system is engaged during flashing of one image after which, no more images can be flashed and the whole flash process aborts with an error. One possible method of fixing this is to have sysbuild halt the CPU(s), flash all images that need to be flashed, and then do a reboot once all images have been flashed.
Arguments passed to west flash in a sysbuild-configured project need a level of granularity, if a device ID is provided, should this be provided to all runners? This will work if sysbuild is working with 1 SoC on 1 board, but if there are 2 SoCs/boards then this is wrong and going to fail. The other issue is the --recover argument which is used to erase the contents of the flash, using the nRF5340 example, in a normal non-sysbuild project, this works as expected, but in a sysbuild project this supplies the argument to every image that is flashed, which means if you flash 3 images, it will recover, flash image 1, recover, flash image 2, recover, flash image 3 - leaving the board in a non-working state. So if this command is used, it should be used from a "global" perspective in sysbuild projects, recover all boards/cores when the script runs without running it once per flash invocation.

in a sysbuild project this supplies the argument to every image that is flashed, which means if you flash 3 images, it will recover, flash image 1, recover, flash image 2, recover, flash image 3 - leaving the board in a non-working state.

Two years have passed.  This is a very annoying issue.
Have you found a solution?

in a sysbuild project this supplies the argument to every image that is flashed, which means if you flash 3 images, it will recover, flash image 1, recover, flash image 2, recover, flash image 3 - leaving the board in a non-working state.

Two years have passed. This is a very annoying issue. Have you found a solution?

It's been fixed for ages https://github.com/zephyrproject-rtos/zephyr/pull/69748

in a sysbuild project this supplies the argument to every image that is flashed, which means if you flash 3 images, it will recover, flash image 1, recover, flash image 2, recover, flash image 3 - leaving the board in a non-working state.

Two years have passed. This is a very annoying issue. Have you found a solution?

It's been fixed for ages #69748

Great. Thank you for pointing to this feature.
Now, I have the west flash erase issue with an MCUBoot sysbuild application, which still does unwanted repetitive erasing & reset.
I will try to find a solution using the provided information.


scripts: Clean up output from 'clean_unused_caches'

The output log from running clean_unused_caches was too verbose and is only
needed when running it directly. Running it otherwise seems to imply it
anyhow. So a new flag --no-print-headers is introduced. It suppresses
the header outputs for the sub-tools.
Fixes #13214.
Tested the flag on clean-unused-caches.

@timabbott please check. Thanks.


Fix Python 3.9 Deprecation Warning

While working on wagtail-bakery, I came across a deprecation warning for Python 3.9 on Wagtail itself:

DeprecationWarning: Using or importing the ABCs from 'collections'
instead of from 'collections.abc' is deprecated since Python 3.3,
and in 3.9 it will stop working

Since we only support Python 3.5+, it there shouldn't be any compatibility issue.
I haven't checked if there are other deprecation warnings just yet.

Thanks @loicteixeira!


Testbench example for FP8, using cocotb

PR Summary

Related to #40.
This PR adds an example of how to make a testbench using cocotb+APyTypes for an eight-bit floating-point multiplier.
The format used is E5M2 with round to nearest, ties to odd. The implementation is a bit naive.
Currently only a Python file and a VHDL file is present, but further documentation will be added in this PR.
The example should ideally also be added to the pipeline to make sure it isn't broken.
PR Checklist

[ ] "closes #0000" is in the body of the PR description to link the related issue
[ ] new and changed code is tested
[ ] relevant changes added to CHANGELOG.md
[ ] new functionality is documented

What's strange is that a lot of warnings are generated from nanobind regarding APyTypes when a test fails. Many instances, types, and functions are considered "leaked":
** Note:<PHONE_NUMBER>01fs+0: VHPI plugin requested end of simulation
nanobind: leaked 5 types!
 - leaked type "apytypes._apytypes.ContextManager"
 - leaked type "apytypes._apytypes.APyFloat"
 - leaked type "apytypes._apytypes.APyFloatQuantizationContext"
 - leaked type "QuantizationMode"
 - leaked type "apytypes._apytypes.APyFloatArray"
nanobind: leaked 117 functions!
 - leaked function "__sub__"
 - leaked function "__truediv__"
 - leaked function "identity"
 - leaked function "__invert__"
 - leaked function ""
 - leaked function "nanmax"
 - leaked function ""
 - leaked function "__ge__"
 - leaked function "squeeze"
 - leaked function "from_float"
 - leaked function "__radd__"
 - ... skipped remainder
nanobind: this is likely caused by a reference counting issue in the binding code.

*** Caught signal 6 (SIGABRT) ***

[0x55d039220a35] ../src/util.c:872 signal_handler.lto_priv.0
[0x7fdb202e304f] (/usr/lib/x86_64-linux-gnu/libc.so.6)
[0x7fdb20331e3c] (/usr/lib/x86_64-linux-gnu/libc.so.6)
[0x7fdb202e2fb1] (/usr/lib/x86_64-linux-gnu/libc.so.6) raise
[0x7fdb202cd471] (/usr/lib/x86_64-linux-gnu/libc.so.6) abort
[0x7fdb18b3533a] (/usr/local/lib/python3.9/site-packages/apytypes/_apytypes.cpython-39-x86_64-linux-gnu.so) _ZN8nanobind6detailL17internals_cleanupEv.lto_priv.0.cold
[0x7fdb1a1c5c3e] (/usr/local/lib/libpython3.9.so.1.0) Python/pylifecycle.c:2423 call_ll_exitfuncs
[0x7fdb1a1c5c3e] (/usr/local/lib/libpython3.9.so.1.0) Python/pylifecycle.c:1506 Py_FinalizeEx.cold
[0x7fdb1c757be8] (/usr/local/lib/python3.9/site-packages/cocotb/libs/libcocotb.so) cocotb/share/lib/embed/gpi_embed.cpp:201 _embed_sim_cleanup
[0x7fdb1c757be8] (/usr/local/lib/python3.9/site-packages/cocotb/libs/libcocotb.so) cocotb/share/lib/embed/gpi_embed.cpp:191 _embed_sim_cleanup
[0x7fdb1c7c92bc] (/usr/local/lib/python3.9/site-packages/cocotb/libs/libgpi.so) cocotb/share/lib/gpi/GpiCommon.cpp:138 gpi_cleanup
[0x7fdb1c7c92bc] (/usr/local/lib/python3.9/site-packages/cocotb/libs/libgpi.so) cocotb/share/lib/gpi/GpiCommon.cpp:600 _Z16gpi_to_simulatorv
[0x55d039327cc8] ../src/vhpi/vhpi-model.c:1553 vhpi_global_cb
[0x55d0392f7419] ../src/rt/model.c:2687 async_timeout_callback.lto_priv.0
[0x55d0392f33a0] ../src/rt/model.c:393 deferq_run.lto_priv.0
[0x55d03921dc7a] ../src/rt/model.c:3269 model_run
[0x55d03921dc7a] ../src/rt/model.c:857 run_cmd
[0x55d03921830d] ../src/nvc.c:2117 process_command
[0x55d03921baa7] ../src/nvc.c:533 elaborate
[0x55d039218324] ../src/nvc.c:2115 process_command
[0x55d039214317] ../src/nvc.c:2257 main

nvc 1.14.0 (1.14.0.r0.g157b0f62) (Using LLVM 14.0.6) [x86_64-pc-linux-gnu]

Please report this bug at https://github.com/nickg/nvc/issues

Not sure it is an NVC bug, but that really depends on who is sending SIGABRT. My guess is that it is cocotb that sends it as a consequence of a failed test and NVC is just pre-cautious and outputs that as a standard thing.

See https://github.com/wjakob/nanobind/issues/19#issuecomment-1278110330
Worth a try. (I guess this should go into __init__.py).

See wjakob/nanobind#19 (comment)
Worth a try. (I guess this should go into __init__.py).

Thank you for the tip but the error still occurs. Tested with Python 3.11 and 3.12.

Also tried changing all nanobind::steal to nanobind::borrow as suggested from @miklhh, but no difference.

As static variables may be the culprit, like mentioned in #533, it would be interesting to try removing them and see if the crashes still happen. By removing I mean just deleting that part of the code and make it compile.
(I'm also trying to find the exact line number which causes the abort in nanobind::detail::internals_cleanup().)

Are you sure it is a "crash"? I'm thinking that APyTypes sends an abort as a consequence of leaking memory?

Crash was perhaps the wrong word, but yes the abort is probably intentional from nanobind due to the leaks.

@Theodor-Lindberg, don't commit any nanobind::borrow change, as it is supposed to be nanobind::steal. Thanks for testing.

The problem with the nanobind and cocotb interaction has been resolved in:

#535

The problem with the nanobind and cocotb interaction has been resolved in:
* [Fix nanobind interaction with cocotb #535](https://github.com/apytypes/apytypes/pull/535)

It still seems to


on clicking any item of explore list, the app crashes

Thanks for pointing out the issue! To get more specific, did the crash occur when you tapped on a search result? Or when you tried to filter by a different menu option (restaurants/hotels/attractions)?


Max Selection Limit not working .

Here is my code, which is I used to show selection menu. provided max limit of 4 but Im still able to select more then 4.

    let selectionMenu  = RSSelectionMenu(selectionType: .Multiple, dataSource: source, cellType:
      .Basic) { (cell, object, indexPath) in
            cell.textLabel?.text = object
        }
        selectionMenu.maxSelectionLimit = 4
        selectionMenu.onDismiss = { selectedItems in
            print(selectedItems)
            self.txt_topic.text = self.selectedTopics.joined(separator: ",")

        }
        selectionMenu.setSelectedItems(items: selectedTopics) { (text, Selected, selectedItems) in
            self.selectedTopics = selectedItems
        }
        selectionMenu.dismissAutomatically = false
        selectionMenu.show(style: .Actionsheet(title: kAppName, action: nil, height: nil), from: self)

@subhash08
Try to put this line
 selectionMenu.maxSelectionLimit = 4
after
selectionMenu.setSelectedItems(items: selectedTopics) { (text, Selected, selectedItems) in
     self.selectedTopics = selectedItems
}

Like below:
selectionMenu.setSelectedItems(items: selectedTopics) { (text, Selected, selectedItems) in
     self.selectedTopics = selectedItems
}
selectionMenu.maxSelectionLimit = 4

One more thing selectionMenu.dismissAutomatically = false will only work for single selection.

@subhash08 Did you try this?

@rushisangani  Thank you man, it's working now.
closing issue now.


8 Ball Not Displaying It's Indispensable Knowledge

8 Ball – 8 Ball
Author: @Gitsack
Description
Nothing displays when the extension is run
Steps To Reproduce
1.Run 8 Ball
The current behavior

Run 8 Ball
Nothing is displayed

The expected behavior

Run 8 Ball
Dispense indispensable knowledge

Raycast version
Version: 1.41.1

Hi @gitatmax thanks for the report 😁
I'll take a look!

Many thanks, love the extension :)

This should be fixed in 1.42.1 - nothing to fix 😊

Glad to hear! Thanks


Fix for new NSRL zip without folder path

Modified unzip command to deal with new NSRL zip files where the .txt files are in the root of the archive, instead of inside a subfolder.
It should fix #2.

@morallo much thanks for creating and then fixing #2. You are awesome!

No problem! However, I realized https://github.com/kost/docker-kf is probably a better solution (smaller, more functionality).
But not as easy to find! So if you are not really eager on maintaining this repo, maybe you could link that in the README?
But thx for creating it in the first place! :-D


Update German translation file

Fix typo and change strange/wrong translations

Hey @oliworx Thanks for the PR 👍🙏


feat: app.bsky.feed.defs#generatorView (#428)

1. Description

1.1. Checklist

[ ] The title of my PR starts with a Conventional Commit prefix (fix:, feat:, docs: etc).
[ ] I have read the Contributor Guide and followed the process outlined for submitting PRs.
[ ] I have updated/added tests for ALL new/updated/fixed functionality.
[ ] I have updated/added relevant documentation in docs and added dartdoc comments with ///.
[ ] I have updated/added relevant examples in examples.

1.2. Breaking Change

[ ] Yes, this is a breaking change.
[ ] No, this is not a breaking change.

1.3. Related Issues

Codecov Report

Merging #445 (c403e3f) into main (9839ac4) will increase coverage by 11.52%.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@             Coverage Diff             @@
##             main     #445       +/-   ##
===========================================
+ Coverage   72.82%   84.34%   +11.52%
===========================================
  Files         159        5      -154
  Lines        1424      115     -1309
===========================================
- Hits         1037       97      -940
+ Misses        387       18      -369

see 154 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Fix +1 macros to 1+ and update some timer types

Pull Request Test Coverage Report for Build 772971322

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.002%) to 69.256%

Files with Coverage Reduction
New Missed Lines
%

game/system/iop_thread.cpp
1
96.08%

Totals

Change from base Build 765419526:
-0.002%

Covered Lines:
33680

Relevant Lines:
48631

💛  - Coveralls


(blaming models.py revision from feature/add_category_image)

override for models is back again
from branch https://github.com/Air-Mark/djangocms-blog/tree/f/overridable_blog_models

Current coverage is 93.76%

Merging #6 into develop will decrease coverage by -0.20% as of 6a61b38

@@            develop      #6   diff @@
=======================================
  Files            18      20     +2
  Stmts           978    1010    +32
  Branches        109     109
  Methods           0       0
=======================================
+ Hit             919     947    +28
  Partial          30      30
- Missed           29      33     +4

Review entire Coverage Diff as of 6a61b38

Powered by Codecov. Updated on successful CI builds.


feat: add auto scroll when dragging

Very barebones implementation. Open to any contribs here.

Is there anything stopping this from being merged @andrewdoro? Would be a very useful QOL change to have in the main package.

@chinnuu05 hey this should have been fixed by https://github.com/steven-tey/novel/pull/361, I first have to update the config for it


Add a datepicker with popup option

I need a datepicker with popup option. This is also usefull for mobile first.
I want to validate the a choosen date and give immediate response over the datepicker-Textfield with a red validation message. With your datepicker shown as a "dialog" you cover everything on the screen.
Also opening and closing a datepicker like a dialog is too much distortion for the user IMHO.

Hi!
The datepicker we made is directly from the MD spec. I don't think we'll have a dropdown version. But it will be updated to manage some validation like an interval for example.

That does not make sense. When I simply want to change a date then I do not want to be distorted by a fading popup dialog...


[helpers] add missing helpers

Describe the feature
Some helpers that are missing from h3, and require users to explicitly rely on event.node.
We should provide the following helpers as a part of the migration to  #73
Once everything is covered, we can start deprecating event.node usage for end-users, as they should not rely on node agnostic API for their needs.
Header :

removeResponseHeaders
removeResponseHeader
getRequestRawHeader
getResponseHeaders
getResponseHeader

Response :

sendResponse

URL :

setOriginalUrlPath
getOriginalUrlPath
setUrlPath
getUrlPath
getRequestPath

Note specific :

nodeResWritableEnded (event.node.res.writableEnded)

Reference for implementation and test https://github.com/Hebilicious/h3/pull/2/files
Additional information

[X] Would you be willing to help implement this feature?

I think now we have most missing utils as event.[] props. Let's see what is missing in the future.


Diagnostics / Tables - Large Tables Perf Band-Aid

Here's my band-aid proposal for large tables performance issue.
I would prefer for large tables be un-formated and usable than formated and unusable.

Thank you.


Update record with ZOOM extended services

Implementation to update records using ZOOM extended services https://software.indexdata.com/yaz/doc/zoom.extendedservices.html
Usage:
zoom.connection('host:2100')
  .set('password', 'password123')
  .updateRecord({
    record: marcRecordInISO2709,
    action: "recordInsert"
  }, function (err, data) {
    console.log("Data: " + JSON.stringify(data));
    console.log("Err: " + err);
  });

Coverage decreased (-5.4%) to 80.812% when pulling 31c8d8c3ca8a6d13aa51d016c2ce0ccef692945b on NatLibFi:update-record-implementation into 1818b895a1ee4c636fe1fed5c53bcf7ff0db5d59 on dengelke:master.

Coverage decreased (-5.4%) to 80.812% when pulling 31c8d8c3ca8a6d13aa51d016c2ce0ccef692945b on NatLibFi:update-record-implementation into 1818b895a1ee4c636fe1fed5c53bcf7ff0db5d59 on dengelke:master.

Thanks for the PR! Looks like tests are failing on Node 0.10 and 0.12 due to some of the syntax, see here for details. Will merge once fixed.

Thanks! The code coverage went down since it is a bit difficult to make tests for this. I'd rather not try to insert something to the db used in tests. 😄


Ticket ID's

They are obviously randomly generated, but why?  Can there be a slightly more user-friendly way to generate these?  Maybe use the player's name or something in the id.

Completed for v1.1.0.


release-19.1: ui: adjust QPS Summary to match Time Series and Node Map values.

PR: https://github.com/cockroachdb/cockroach/pull/35905
From release notes:

The Queries per second metric in the Summary bar now summarizes only the query types displayed in the SQL Queries graph and Node Map. [#35905][#35905] {% comment %}doc{% endcomment %}

Closed via #4597


Upload step for copy process completion added

It was not clear to the user that the copy process must be completed by the project manager by uploading the project copy from RPA Builder to RPA Manager before process team members added to the project could open the project copy in RPA Builder.
-> Added missing step
-> Reworded

Dear SME,
please review for accuracy and completeness.
Please check in a production cluster if making a dummy change in a workflow before uploading the project is needed.
Thank you.

Dear editor,
please review the changes. The first two commits contain missing information. The last two commits result from using Vale as a linter.
Thank you.


Fix: Update notify linting

Latest ansible-lint now requires notifiy pass casing test.

Remove obsolete listen in handlers.
Make single notify consistent.

Ugh, I don't like this.
Raised my concerns over at https://github.com/ansible/ansible-lint/issues/4035#issuecomment-2116272270

superseded by https://github.com/prometheus-community/ansible/pull/363


Scatter plot of cost curve slopes vs capacity

To be done for each zone/type combination

Example below


TimeoutError: Timeout awaiting 'request' for 30000ms

Just installed everything from the starter, wordpress is running the plugins and getting pages, posts and so on works. However, the script encounters and error when fetching MediaItems.
$ npm run develop

><EMAIL_ADDRESS>develop C:\projects2\gatsby-project-exp
> gatsby develop

success open and validate gatsby-configs - 0.039s
success load plugins - 1.514s

 ERROR

(node:2504) ExperimentalWarning: The dns.promises API is experimental

success onPreInit - 0.052s
success initialize cache - 0.026s
success copy gatsby files - 0.080s
success onPreBootstrap - 0.019s

info  gatsby-source-wordpress

        This is either your first build or the cache was cleared.
        Please wait while your WordPress data is synced to your Gatsby cache.

        Maybe now's a good time to get up and stretch? :D

success  gatsby-source-wordpress  writing GraphQL queries to disk at ./WordPress/GraphQL/ - 0.258s
success  gatsby-source-wordpress  ingest WPGraphQL schema - 1.158s
success createSchemaCustomization - 1.618s
success  gatsby-source-wordpress  fetch root fields - 0.582s
success  gatsby-source-wordpress  Comment - 0.647s - fetched 0
success  gatsby-source-wordpress  Menu - 0.712s - fetched 2
success  gatsby-source-wordpress  Category - 0.806s - fetched 5
success  gatsby-source-wordpress  ContentType - 0.810s - fetched 3
success  gatsby-source-wordpress  MenuItem - 0.896s - fetched 36
success  gatsby-source-wordpress  PostFormat - 0.993s - fetched 0
success  gatsby-source-wordpress  Post - 1.003s - fetched 0
success  gatsby-source-wordpress  Tag - 1.006s - fetched 1
success  gatsby-source-wordpress  Taxonomy - 1.027s - fetched 3
success  gatsby-source-wordpress  UserRole - 1.020s - fetched 0
success  gatsby-source-wordpress  User - 1.019s - fetched 2
success  gatsby-source-wordpress  Page - 3.227s - fetched 34

 ERROR

(node:2504) ExperimentalWarning: Readable[Symbol.asyncIterator] is an experimental feature. This feature could change at any time

warn Received the below error when trying to fetch
http://www.nottherealdomain.com/wp-content/uploads/2018/06/51AdY5oO2-L-1.jpg
from Page #1386 "Page name test"

https://www.nottherealdomain.com/wp-admin/post.php?post=1386&action=edit

 ERROR

 gatsby-source-wordpress  failed to process http://wwwnottherealdomain.com/wp-content/uploads/2018/06/51AdY5oO2-L-1.jpg
TimeoutError: Timeout awaiting 'request' for 30000ms

not finished source and transform nodes - 34.401s
not finished  gatsby-source-wordpress  fetching nodes - 34.336s - 105 total
not finished  gatsby-source-wordpress  creating nodes - 31.027s
not finished  gatsby-source-wordpress  MediaItem - 31.029s - fetched 19
not finished Downloading remote files - 30.521s
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>develop: `gatsby develop`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>develop script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      C:\Users\pboch\AppData\Roaming\npm-cache\_logs\2020-10-11T12_13_28_209Z-debug.log

Logfile:
0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Users\\pboch\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'run',
1 verbose cli   'develop' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'predevelop', 'develop', 'postdevelop' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>7 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
8 verbose lifecycle<EMAIL_ADDRESS>PATH: C:\Users\pboch\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\projects2\gatsby-project-exp\node_modules\.bin;C:\Program Files\Git\mingw64\bin;C:\Program Files\Git\usr\bin;C:\Users\pboch\bin;C:\Program Files\Git\mingw64\bin;C:\Program Files\Git\usr\bin;C:\Users\pboch\bin;C:\Python37\Scripts;C:\Python37;C:\Program Files (x86)\Common Files\Intel\Shared Libraries\redist\intel64\compiler;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Calibre2;C:\Program Files (x86)\QuickTime\QTSystem;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\wamp64\bin\php\php5.6.16;C:\Program Files (x86)\Skype\Phone;C:\Program Files\Git\cmd;C:\ProgramData\chocolatey\bin;C:\WINDOWS\System32\OpenSSH;C:\Program Files\Microsoft VS Code\bin;C:\Users\pboch\.dnx\bin;C:\Program Files\Microsoft DNX\Dnvm;C:\Program Files\Microsoft SQL Server\130\Tools\Binn;C:\Program Files (x86)\Yarn\bin;C:\Users\pboch\AppData\Roaming\nvm;C:\Program Files\nodejs;C:\Program Files\nodejs;C:\Program Files\NVIDIA Corporation\NVIDIA NvDLISR;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\Docker\Docker\resources\bin;C:\ProgramData\DockerDesktop\version-bin;C:\Users\pboch\AppData\Local\Microsoft\WindowsApps;C:\Program Files\Microsoft VS Code\bin;C:\Program Files\Git\usr\bin;C:\Users\pboch\AppData\Roaming\Dashlane\<IP_ADDRESS>21\bin\Firefox_Extension\{442718d9-475e-452a-b3e1-fb1ee16b8e9f}\components;C:\Users\pboch\AppData\Roaming\Dashlane\<IP_ADDRESS>21\ucrt;C:\Users\pboch\AppData\Local\Microsoft\WindowsApps;C:\Users\pboch\AppData\Local\Yarn\bin;C:\Users\pboch\AppData\Roaming\nvm;C:\Program Files\nodejs;C:\Users\pboch\AppData\Roaming\npm;C:\Users\pboch\AppData\Roaming\Dashlane\6.1907.0.17833\bin\Firefox_Extension\{442718d9-475e-452a-b3e1-fb1ee16b8e9f}\components;C:\Users\pboch\AppData\Roaming\Dashlane\6.1907.0.17833\ucrt;C:\Users\pboch\AppData\Roaming\Dashlane\6.1907.0.17833\bin\Qt;C:\Users\pboch\AppData\Roaming\Dashlane\6.1907.0.17833\bin\Ssl;C:\Users\pboch\AppData\Local\GitHubDesktop\bin
9 verbose lifecycle<EMAIL_ADDRESS>CWD: C:\projects2\gatsby-project-exp
10 silly lifecycle<EMAIL_ADDRESS>Args: [ '/d /s /c', 'gatsby develop' ]
11 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null
12 info lifecycle<EMAIL_ADDRESS>Failed to exec develop script
13 verbose stack Error<EMAIL_ADDRESS>develop: `gatsby develop`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (C:\Users\pboch\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\index.js:301:16)
13 verbose stack     at EventEmitter.emit (events.js:182:13)
13 verbose stack     at ChildProcess.<anonymous> (C:\Users\pboch\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:182:13)
13 verbose stack     at maybeClose (internal/child_process.js:962:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:251:5)
14 verbose pkgid<EMAIL_ADDRESS>15 verbose cwd C:\projects2\gatsby-project-exp
16 verbose Windows_NT 10.0.18362
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\pboch\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "run" "develop"
18 verbose node v10.15.0
19 verbose npm  v6.5.0
20 error code ELIFECYCLE
21 error errno 1
22 error<EMAIL_ADDRESS>develop: `gatsby develop`
22 error Exit status 1
23 error Failed at the<EMAIL_ADDRESS>develop script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

possibly an issue with requesting the images? for example, it may be that if you’re using a CDN, it may have triggered some kind of bot detection mechanism. a request timeout on the wordpress could have many sources, and there are of course many factors

Hi @acao! Thank you for your help. I'm not using a CDN and so far I didn't run into any similar issues with v3 of the plugin. I also checked and the image can be accessed manually.

Hey @phbo85 any luck so far?

Hi @uzomao, today I tried upgrading my packages and node to the latest versions, but it's still stuck at the same point. I removed the image that can't be loaded and the reference from the WP post, but then it's stuck on another image. I'm out of ideas.
If anybody wants to try it with my WP installation, I can give you the URL in private.

because this error is coming from your wordpress installation, its very difficult to track down. is it self hosted? wp engine? apache or nginx?

Hi @acao, the installation is self-hosted... here is some more info, I hope it's helping. If you want to I can send you a mail with the domain.
Server OS : Linux / 64Bit OS
Server Software : Apache
Memcached Enabled : No
Database Software : (Ubuntu)
Database Version : 5.7.28
Maximum No. of Connections : 500
Maximum Packet Size : 64 MB
Database Disk Usage : 24 MB
Index Disk Usage : 6 MB
Check More Database Info
PHP Version : 7.4.10
PHP Max Upload Size : 200 MB
PHP Max Post Size : 200 MB
PHP Max Execution Time : 30 sec
PHP Short Tag : On
PHP Memory Limit : 256 MB

maybe try increasing max execution time to 90 seconds? looks like the
timeout error your getting is exactly 30 seconds
On Thu, Oct 15, 2020 at 5:15 AM Philipp Bochmann<EMAIL_ADDRESS>wrote:

Hi @acao https://github.com/acao, the installation is self-hosted...
here is some more info, I hope it's helping. If you want to I can send you
a mail with the domain.
Server OS : Linux / 64Bit OS
Server Software : Apache
Memcached Enabled : No
Database Software : (Ubuntu)
Database Version : 5.7.28
Maximum No. of Connections : 500
Maximum Packet Size : 64 MB
Database Disk Usage : 24 MB
Index Disk Usage : 6 MB
Check More Database Info
PHP Version : 7.4.10
PHP Max Upload Size : 200 MB
PHP Max Post Size : 200 MB
PHP Max Execution Time : 30 sec
PHP Short Tag : On
PHP Memory Limit : 256 MB
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gatsbyjs/gatsby-source-wordpress-experimental/issues/220#issuecomment-709027421,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKOFFZAW4GBXPSS5ZYHKCLSK24TTANCNFSM4SLXQ6UA
.

I tried setting it to 90 seconds, but still getting the same error.

I've updated to the latest version today, also updated node and npm. The problem is solved for me.


Terrain category support

I've been looking at implementing terrain grouping, and I have figured out a way to implement it whilst at the same time improving performance across the board. This will be my next feature, and I would like to get it done before Godot 4.0 releases, as it will likely be a breaking change.
In general, I want terrain types to belong to a category (or multiple categories), and then be able to connect to other terrains of those categories. For example, if you have different types of ground - sand, dirt and paved - you can give them all the same category and set up their peering bits to connect to their category. That's easier than setting up every combination of connections between them.
At the same time, I want to be able to support the terrain's uniqueness, so if there a specific special connection, that can be supported. In the same example, if you have water tiles that can connect with sand but not dirt/paved, then that should still be supported.
There are a number of ways that groups or categories could be implemented. For example:

Perhaps it could be an extra property on the terrain which allows it to appear as any other type of terrain, or a selection of other types. This is the most flexible (maybe overly so) but a poor UI.

Another option which is more clear and intuitive is to arrange terrain types in a hierarchy. This is a slightly less flexible, but very easy to understand. This is probably what I will go with unless there is a strong reason to do something different.
If you have any feedback about this, feel free to comment.

I implemented something similar to the first mockup in the original post. The underlying code uses arbitrary length bitfields to match terrain categories together. Although this is much faster in theory, relying on sequential bitwise operations rather than linear searches of arrays, the actual result is considerably slower due to the overhead of GDScript.
Functionally, it works very well. The only real issue is that the speed is bad, probably too bad for real time usage.
Overall, I'm not exactly sure what I can do to improve the quality of this plugin, but the obvious strategy is to use GDExtension to strip out some of the GDScript overhead. I'll experiment with that and see if I can make significant gains. Perhaps there is some way to have it run some components natively, but fallback on a pure GDScript solution in situations where native is unavailable.

I've pushed the changes into a category branch, but I'm unhappy with the performance. I'm looking into GDExtension because that should be able to speed it up a lot.

I'm going to make some adjustments to the category branch to remove certain implementation details from the internal API. That will simplify making a C++ version of the matching engine via GDExtension. I will do this over the next few weeks.

Reworking the precalculation / caching allowed the performance to be comparable (almost equivalent) to previous. I will skip a GDExtension for now, as I think the plugin works sufficiently well with just GDScript, and that is most versatile.

I appreciate you taking a look at my PR as inspiration to solve the problem in a way that better suited your goals for this project (also a much better develop experience than what I came up with). I'll be kicking the tires on it this weekend! https://opengameart.org/content/dawnlike-16x16-universal-rogue-like-tileset-v181 Dawnlike has been a challenging tileset to set rules for, but your terrain tool has been up to the task so far!

Merged back to master now.


Style cards on events search

Replicate how Search Event cards display on /events but make it work with the Content API response format.
Mockups for extra context

Waiting on https://github.com/wellcomecollection/content-api/issues/92

Fully booked is on prod.
I believe we're done for now on styling cards, so will move this card to done.
There's a TODO left that might be good to have once we have date filtering, but that's it.


"AzureFunctionsJobHost__Logging__Console__IsEnabled=true" should have ":" instead of "__"

"func init --worker-runtime dotnet-isolated --docker" generates a Dockerfile with "AzureFunctionsJobHost__Logging__Console__IsEnabled=true". When I run my Azure function with this code console logging does not appear. I changed this to "AzureFunctionsJobHost:Logging:Console:IsEnabled=true" and then console logging appeared.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 5d505ab9-d351-6650-6d0c-bb65d2daa229
Version Independent ID: 2a1d3487-a93d-2206-7ef9-a91aa275ec4e
Content: Create Azure Functions on Linux using a custom image
Content Source: articles/azure-functions/functions-create-function-linux-custom-image.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@kbiondi Thank you for your feedback. We will investigate and update the thread further.

@kbiondi , Thanks for the feedback.
Both the commands, AzureFunctionsJobHost__Logging__Console__IsEnabled=true and AzureFunctionsJobHost:Logging:Console:IsEnabled=true works for me.

So I dont think the documentation needs to be changed. I am closing this issue for now. Feel free to reopen if you have any queries or concerns.

Thanks @kbiondi and @MughundhanRaveendran-MSFT To provide more context...the colon (:) delimiters for nested app settings are supported only when running on Windows. The double underscore (__) delimiters are supported on both Windows and Linux, which is why we use them in our docs.


generateInviteLink and OG tags

Hello, how can I add the OG tags to the link generated with the function generateInviteLink?
I found this guide: https://support.appsflyer.com/hc/en-us/articles/207032246#create-a-social-media-preview, but it's not clear how to use the OG tags params with the SDK.

Hi @cark1 and thank you for reaching out! You can add OG tags inside the userParams nested object like this:
appsFlyer.generateInviteLink(
 {
   channel: 'gmail',
   campaign: 'myCampaign',
   customerID: '1234',
   userParams: {
      af_og_title: "dwed",
      af_og_description: "ddd",
      af_og_image: "test",
     // more data //
   },
 },
 (link) => {
   console.log(link);
 },
 (err) => {
   console.log(err);
 }
);

Thank you! The problem was with the af_og_image. I passed an empty string. Passing an empty string all the other params were ignored.

Hi @cark1 ,
As per this doc ( https://support.appsflyer.com/hc/en-us/articles/207032246#create-a-social-media-preview), I added all three params for my link, But when I am sharing my link on social media , Its showing OLD text and Image only.
OG tags are not getting updated.


Make istio.io support quality print output.

Get rid of all the chrome when printing a page. So no headers, sidebars, etc.

Generate endnotes for each page printed which lists the URLs of the various links
on the page. Each link site is annotated with a superscript number referencing this
table.

Staging: https://geeknoid.github.io/istio.github.io/

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: geeknoid
Assign the PR to them by writing /assign @geeknoid in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Gradients look more visually pleasing.  I don't see any delta in print mode though.  I don't know much about HTML (my last HTML work was with vi in 1999 making a website for my Father's business).  I don't have anything to offer on the technical review of the work.
Cheers
-steve

@sdake Can you clarify? Do you want gradient somewhere?
My goal with this first print-friendly effort was to get rid of the chrome (nav bars, sidebars, etc) so that the printed page looks good.
After that, I'll improve the CSS to prevent some elements from being broken up across page boundaries, I'll add support for footnotes that show the full URLs of the different links, will improve colors a bit, and will do other minor tweaks.
But gradients weren't on my list :-)

Maybe this wasn't your change, but there is a gradient in the change (and it looks good).  I'll check out the other elements you mentioned.
Screenshot of your rendered page:

vs. Screenshot of istio.io:

I see the delta now in print mode - should print much better now.
Cheers
-steve

btw I'm the last person you want judging web page user interfaces :)

Ah, that gradient. We have three color schemes for Istio:
archive.istio.io - old stuff, in a darker blue
istio.io - current stuff, in "Istio" blue
preliminary.istio - future stuff, in a lighter blue
They all three have a gradient on the landing page and in the
header/footer, it's just that it's more apparent with the
preliminary.istio.io colors (which is what staging sites build as
nowadays).
Of course, printing web pages is really intended for content pages, I don't
expect many people to print the home page :-)
On Sun, Apr 8, 2018 at 7:55 AM Steven Dake<EMAIL_ADDRESS>wrote:

btw I'm the last person you want judging web page user interfaces :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio.github.io/pull/1163#issuecomment-379556569,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVucHakVMWcfw4Xf82OB9oO_TME3FLQKks5tmiT_gaJpZM4TK8VS
.

@geeknoid thanks for the explanation.  My eyesight isn't all that fantastic so have trouble seeing the other gradients, but if you say they are there, they are ;)  Agree printing is for content pages not headers.
I went through several and took a look at print mode, and IMO this PR works as intended.
Cheers
-steve

This is a nice improvement over today, but there's still a few problems:

Some of the context overlaps the print headers
The code boxes aren't expanded, which means they're still scroll areas and don't actually render when printing.

Here's a screenshot with both issues:

IMO we should also drop the styling on the boxes in print mode, and just outline them (get rid of the bar on the left of the code blocks, basically)

I fixed the scroll bars on PRE blocks, those are gone. I kept the thick border on the left though for the sake of consistency with the web view.
As for the content overlapping the header/footer, that's really out of my control. The header/footer are things inserted by the browser around the rendered content. The only way I was able to repro your case in Chrome was to set a custom margin in the print dialog and to explicitly make the margin too skinny for the header/footer to fit in. Is this your case per chance? Otherwise, using Chrome's Minimum or Default margins, there was plenty of room for the header/footer.
Thanks.


Eager Loading Filter and Search Issues

Summary of problem or feature request
I'm having issues with search and filters on company eager loading relationship.
Also, the company model has a MorphTo relationship where filter or search also didn't work.
Could someone point me out why it is not working?
Code snippet of problem

class Contributor extends Model
{
    protected $fillable = ['name', 'enrollment', 'function', 'cpf', 'rg', 'phone', 'role'];

    public function company()
    {
        return $this->belongsTo(Company::class);
    }

    public function user()
    {
        return $this->belongsTo(User::class);
    }
}

class Company extends Model
{
    protected $fillable = ['name', 'contact', 'email', 'phone', 'color'];

    public function address()
    {
        return $this->morphOne(Address::class, 'addressable');
    }

    public function contributors()
    {
        return $this->hasMany(Contributor::class);
    }
}

class UserController extends Controller
{
    /**
     * @var \Yajra\Datatables\Datatables
     */
    private $dataTable;

    /**
     * UserController constructor.
     *
     * @param \Yajra\Datatables\Datatables $dataTable
     */
    public function __construct(Datatables $dataTable)
    {
        $this->dataTable = $dataTable;
    }

    public function index(Request $request)
    {
        if($request->ajax()) {
            $model = Contributor::with('user')->withTrashed()->select('contributors.*');
            return $this->dataTable
                ->eloquent($model)
                ->addColumn('name', function (Contributor $contributor) {
                    return '

'.$contributor->name.'
'.$contributor->enrollment.'
';
                })
                ->addColumn('company.name', function (Contributor $contributor) {
                    return $contributor->company->name;
                })
                ->addColumn('company.city', function (Contributor $contributor) {
                    return $contributor->company->address->city;
                })
                ->addColumn('role', function (Contributor $contributor) {
                    if($contributor->role == 'Admin')
                        return ''.$contributor->role.'';
                    elseif($contributor->role == 'Client')
                        return ''.$contributor->role.'';
                    elseif($contributor->role == 'User')
                        return ''.$contributor->role.'';
                    else
                        return ''.$contributor->role.'';
                })
                ->addColumn('deleted_at', function (Contributor $contributor) {
                    if($contributor->trashed())
                        return 'INACTIVE';
                    return 'ACTIVE';
                })
                ->addColumn('edit', function (Contributor $contributor) {
                    return '
 $contributor]).'" class="item" data-toggle="tooltip" data-placement="top" data-original-title="Edit">
';
                })
                ->rawColumns(['name', 'role', 'deleted_at', 'edit'])
                ->make(true);
        }
    }
}

System details

Operating System
Operating System: Windows 10
PHP Version: 7.2
Laravel Version: 5.8
Laravel Datatables Version: Oracle 9.0

Hi,
I am also facing same problem - searching and sorting not working for 'Eager Loading'.
Thanks

I have the same problem.
The problem seems like that "deleted_at" timestamp is referring to not-aliased table, while table is aliased.
The error I got:
Exception Message: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'logistics_providers.deleted_at' in 'where clause' (SQL: select count(*) as aggregate from (select '1' as `row_count` from `orders` left join `logistics_providers` as `logistics_providers_0` on `orders`.`logistics_provider_id` = `logistics_providers_0`.`id` where  `logistics_providers`.`deleted_at` is null and LOWER(`logistics_providers_0`.`name`) LIKE %%test%% and `orders`.`deleted_at` is null) count_row_table)

The above query should refer to logistics_providers_0.deleted_at but generated query refereed to logistics_providers.deleted_at
Problem seems come from this commit: https://github.com/yajra/laravel-datatables/commit/6c7f997e442a35e99435260b61d594484a87d877#diff-d7663255b88a6aed388d85442e3ec2e0

Downgrading to 9.0.1 fixed my issue.

Thanks for reporting. Reverted the support for self join in relation to this.

v9.1.1 released, kindly check again. Thanks!

Hello @yajra, it still not working for me when trying to filter by deleted_at column.
Any hint?

Hi,
The "Self Joins" stopped working (#2051 ), the alias was removed. When do you plan to get this working again?

@Morinohtar we need to resolved the issue on soft deletes first as it breaks existing apps. Haven't got the chance to check it further though.

Well, maybe this would work, assuming the PR i did...
Adding this new line:
$deletedAtAs = $deletedAt ? "{$alias}.{$deletedAt}" : $deletedAt;

And then replace the performJoin() with:
$this->performJoin($tableAs ?? $table, $foreign, $owner ?? $other, $deletedAtAs ?? $deletedAt);

I added this to the fork i used for the PR.

Yes, that may work. But we need to find a way to identify if the relation uses SoftDeletes trait before applying the delete column. The challenged I think of here was that Laravel automatically appends the delete scope for every query thus it does not uses the table alias that we generated.

Ok, i will leave that to you then ;) But the working self joins are needed.
Awesome job, keep up, and tks :)


Navbar is not properly aligned in mobile version

In our achievements page:

In blogs page also:

Hello @smaranjitghose sir, I found this issue. Please assign me this issue if it is a valid issue.

Sir @anushbhatia , please review the PRs #656 and #657