StrawberryShake.Blazor causes thousands of build errors

Is there an existing issue for this?

[X] I have searched the existing issues

Product
Strawberry Shake
Describe the bug
Just creating a simple Blazor WASM project in .NET 7 and adding StrawberryShake.Blazor causes a bunch of errors when I try to build it. The first thing that happens is that I get a warning, and if I ctrl+c the console, I'm able to copy that warning. It seems to indicate that the build is enumerating my ENTIRE DRIVE, which is crazy:
MSBUILD : warning MSB5029: The value "\**\*.cs" of the "Include" attribute in element <ItemGroup> in file "C:\Users\evshe\.nuget\packages\strawberryshake.blazor\13.1.0\build\Straw
berryShake.Blazor.targets (23,16)" is a wildcard that results in enumerating all files on the drive, which was likely not intended. Check that referenced properties are always def
ined. [C:\Users\evshe\source\repos\TestBlazorGraphQL\TestBlazorGraphQL.csproj]

Also, when I added it originally in VS2022, it started downloading tons of files from OneDrive into a Unity folder which was in a completely separate place than this project. It froze up VS and I had to completely redo a lot of things. My guess is that this drive enumeration is causing it to try to download ALL my OneDrive files, which is not acceptable. The only way I was able to safely reproduce the issue was in VS Code with CLI commands.
Expected: Do not enumerate all files in my drive
Steps to reproduce

Create a new Blazor WASM project and add StrawberryShake.Blazor, then build it:

dotnet new blazorwasm -o TestBlazorGraphQL
cd TestBlazorGraphQL
dotnet add package StrawberryShake.Blazor
dotnet build

Relevant log output
Warning (if Ctrl+c):

MSBUILD : warning MSB5029: The value "\**\*.cs" of the "Include" attribute in element <ItemGroup> in file "C:\Users\evshe\.nuget\packages\strawberryshake.blazor\13.1.0\build\StrawberryShake.Blazor.targets (23,16)" is a wildcard that results in enumerating all files on the drive, which was likely not intended. Check that referenced properties are always defined. [C:\Users\evshe\source\repos\TestBlazorGraphQL\TestBlazorGraphQL.csproj]

End of error output if I let it go:

C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\ItemTemplates\Web\CSharp\1033\DynamicDataWebSiteField.cs\DynamicData\FieldTemplates\CodeBeside_Edit.cs(37,1): error CS1022: Type or namespace definition, or end-of-file expected [C:\Users\evshe\source\repos\TestBlazorGraphQL\TestBlazorGraphQL.csproj]
    5 Warning(s)
    15077 Error(s)

Additional Context?
No response
Version
13.1.0

I decided to take a look at that StrawberryShake.Blazor.targets file and noticed a couple lines that were very weird and suspicious:
<Compile Include="$(GraphQLCodeGenerationRoot)\**\*.cs" />
...
<GraphQLCodeGenerationRoot>$([System.IO.Path]::GetFullPath('$(IntermediateOutputPath)berry'))</GraphQLCodeGenerationRoot>

I feel like $(IntermediateOutputPath)berry is not a real path that would cause the generation root to be empty, thus resulting in the full drive enumeration. I tried clearing my NuGet cache, which ended up deleting that file, but the rebuild created it again with the same unusual lines.
It also happens with all the following versions:

13.0.0
13.0.4
13.0.5
13.1.0
14.0.0-preview.11.3

im having this issue as well !

I figured out the issue. You actually have to generate the graphql files following this tutorial BEFORE building. I feel like this needs a safeguard.
Also, that ended up being a pain, because I'm using a ASP.NET hosted version of my client, from the MudBlazor Wasm-PWA-Hosted template. This adds the Client project as a reference in the Server, so I had to temporarily remove this reference in order to start my server so that dotnet graphql init would work.

OK, apparently having to generate the graphql files is a red herring. It seems that the _GenerateGraphQLCode target only runs in the following situations:

There's something named .graphql in the project
Something has changed with one of the .graphql files OR a change to obj was detected

Therefore, the build seems to work partway, but then fails literally by running dotnet build again a 2nd time. This is because it skips the  _GenerateGraphQLCode target.
This was reproduced by doing the following:

Create a new Blazor WASM project:

dotnet new blazorwasm -o TestBlazorGraphQL
cd TestBlazorGraphQL

Add any.graphql to the project (you don't even have to put anything in it)
Add StrawberryShake.Blazor (DO NOT build yet):

dotnet add package StrawberryShake.Blazor

DELETE both the /bin and /obj directories
Build the first time (succeeds and output shows "Generate C# Clients" target running)

dotnet build

Build the 2nd time (fails with an error about the .NET version and the warning about the Include attribute enumerating all files on the drive)

dotnet build

I discovered this by running the build with diagnostics and viewing the resulting file:
dotnet build /v:diag | Out-File -FilePath ./build-output.txt

Note that the output contains the following when no changes have been detected:
Skipping target "_GenerateGraphQLCode" because all output files are up-to-date with respect to the input files.
                   Input files:
                       any.graphql
                       C:\Users\evshe\source\repos\TestBlazorGraphQL\TestBlazorGraphQL.csproj
                       C:\Users\evshe\.nuget\packages\strawberryshake.blazor\13.1.0\build\StrawberryShake.Blazor.targets

Skipping this target is bad because then it doesn't create the $(GraphQLCodeGenerationRoot) variable (does not even come up in a search in diagnostics build output). When I delete the /bin and /obj and run it with diagnostics again, I can see the value of that variable:
Set Property: GraphQLCodeGenerationRoot=C:\Users\evshe\source\repos\TestBlazorGraphQL\obj\Debug\net7.0\berry

i've removed everything graphql related from my client side, and followed the tutorial again, also we gotta update the Strawberry.Shake Tools, im still debuggin my project, i'll get back to report any findings !

Just to rule out any possible environmental issues with my machine, I used docker and got the same result (I also added the tool manifest and the Strawberry Shake tools, but it really doesn't make any difference). Run from the app directory:
docker run --rm -v ${PWD}:/app mcr.microsoft.com/dotnet/sdk:7.0 dotnet build /app

Same issue, although the errors were a lot smaller, since it is a container:
user@machine TestBlazorGraphQL % docker run --rm -v ${PWD}:/app mcr.microsoft.com/dotnet/sdk:7.0 dotnet build /app
MSBuild version 17.4.0+18d5aef85 for .NET
  Determining projects to restore...
  Restored /app/TestBlazorGraphQL.csproj (in 5.09 sec).
  Generate C# Clients started.
  Generate C# Clients completed in 57 ms
  TestBlazorGraphQL -> /app/bin/Debug/net7.0/TestBlazorGraphQL.dll
  TestBlazorGraphQL (Blazor output) -> /app/bin/Debug/net7.0/wwwroot

Build succeeded.
    0 Warning(s)
    0 Error(s)

Time Elapsed 00:00:15.49
user@machine TestBlazorGraphQL % docker run --rm -v ${PWD}:/app mcr.microsoft.com/dotnet/sdk:7.0 dotnet build /app
MSBuild version 17.4.0+18d5aef85 for .NET
  Determining projects to restore...
  Restored /app/TestBlazorGraphQL.csproj (in 4.64 sec).
/root/.nuget/packages/strawberryshake.blazor/13.1.0/build/StrawberryShake.Blazor.targets(38,20): error MSB4184: The expression "[MSBuild]::VersionGreaterThanOrEquals('', 6)" cannot be evaluated. Version string was not in a correct format. [/app/TestBlazorGraphQL.csproj]
MSBUILD : warning MSB5029: The value "\**\*.cs" of the "Include" attribute in element <ItemGroup> in file "/root/.nuget/packages/strawberryshake.blazor/13.1.0/build/StrawberryShake.Blazor.targets (23,16)" is a wildcard that results in enumerating all files on the drive, which was likely not intended. Check that referenced properties are always defined. [/app/TestBlazorGraphQL.csproj]
CSC : error CS2021: File name '/**/*.cs' is empty, contains invalid characters, has a drive specification without an absolute path, or is too long [/app/TestBlazorGraphQL.csproj]
CSC : error CS2001: Source file '/**/*.cs' could not be found. [/app/TestBlazorGraphQL.csproj]

Build FAILED.

MSBUILD : warning MSB5029: The value "\**\*.cs" of the "Include" attribute in element <ItemGroup> in file "/root/.nuget/packages/strawberryshake.blazor/13.1.0/build/StrawberryShake.Blazor.targets (23,16)" is a wildcard that results in enumerating all files on the drive, which was likely not intended. Check that referenced properties are always defined. [/app/TestBlazorGraphQL.csproj]
/root/.nuget/packages/strawberryshake.blazor/13.1.0/build/StrawberryShake.Blazor.targets(38,20): error MSB4184: The expression "[MSBuild]::VersionGreaterThanOrEquals('', 6)" cannot be evaluated. Version string was not in a correct format. [/app/TestBlazorGraphQL.csproj]
CSC : error CS2021: File name '/**/*.cs' is empty, contains invalid characters, has a drive specification without an absolute path, or is too long [/app/TestBlazorGraphQL.csproj]
CSC : error CS2001: Source file '/**/*.cs' could not be found. [/app/TestBlazorGraphQL.csproj]
    1 Warning(s)
    3 Error(s)

Time Elapsed 00:00:07.23

For those who are interested, I found a workaround. After adding the StrawberryShake.Blazor package, find the targets file for that version at: %USERPROFILE%/.nuget/packages/strawberryshake.blazor/{VERSION}/build/StrawberryShake.Blazor.targets
Find the target below and remove the "Inputs" attribute:
  <Target
    Name="_GenerateGraphQLCode"
    Inputs="@(GenerateGraphQLCodeItems)"
    Outputs="$(MSBuildProjectDirectory)\$(IntermediateOutputPath)berry\.build.info"
    DependsOnTargets="_ParseVersion"
    Condition="'@(GraphQL)' != ''">

This will force it to regenerate the client every time and thus properly create the $(GraphQLCodeGenerationRoot) variable.

@holotrek thanks for the analysis, this saved me a lot of time in creating a fix which should be available with the next 13.2 preview.


788 alembic

Feature or Bugfix

Bugfix
Refactoring

Detail

Alembic migrations are now synchronised with the current code-state
make generate-migrations command is added. It can be applied right after the docker container with psql is started
Readme about migrations

Relates
data.all in local environment starts in a broken db state #788
Security
N/A
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

From a code perspective I think this PR is good to go. I will do a final test by deploying the PR to an AWS deployment to verify that the migrations run successfully on pre-existing AWS deployments.


Total duration of zoom, change attributes and resize events

Actions before raising this issue

[X] I searched the existing issues and did not find anything similar.
[X] I read/searched the docs

Is your feature request related to a problem? Please describe.
I'm working with CVAT 2.14.0, I've labeled some images using zoom, changing attributes and resizing some polygons. When I checked the events in analytics, I saw that the duration column of those events was set to 0. I can get an approximation with the working_time field in the payload, but the time of those events may be distorted if I don't label in less than 100 seconds, as the difference between timestamps is computed and not the duration itself. In the case of not labeling for more than 100 seconds, the working_time is also set to 0.

Are both behavours expected to be this way? Otherwise, is it planned to be fixed in next releases?
Thanks in advance. Cheers,
Manuel

I recently documented how working time calculated, please read here: https://docs.cvat.ai/docs/administration/advanced/analytics/#working-time-calculation
Briefly speaking, duration of zoom and resize are not considered at all.
The only difference is that in v2.14.0 working_time appended to the following event payload.
Starting from v2.14.1 we have a dedicated event to store working time.

Hi @bsekachev,
Thanks for the quick response. Would it make sense to include the duration of such events in next releases?

Yep, it makes sense, but that is not a priority.
Anybody is welcome to contribute :)


Use a real database

Thanks so much for providing this. It's very interesting to see these technologies used together
One thing I noticed is that it looks like there is no database and perhaps data is just stored in memory. I was wondering what your thoughts were on adding a database like Postgres and using a data access layer like Prisma? It would also be interesting to see an example of that. Potentially I could add it if it's something you're open to, but no promises since I'm not sure yet whether I would have the time

Yeah it's cool but that would be like a separate project really. You are welcome to fork if you want to provide it!
It's using in-memory data because YCombinator provides a public Hacker News API. They have limited data available though so this app mostly just implements those things that are available.


Selection modifier inheritance differs from TailwindCSS

UnoCSS version
0.59.4
Describe the bug
Tailwind applies selection:* to all descendants while UNO does this only to the next decendant. In order to use the selection specifier you must use it on all text containing parent nodes or use a global selector.
Tailwind reference: https://tailwindcss.com/docs/hover-focus-and-other-states#highlighted-text
Reproduction
Try the following code with tailwind and with UNO (playgrounds).
Tailwind Playground: https://playcode.io/tailwind
UNO Playground: https://unocss.dev/play/

            Hello Tailwind

              Start editing to see some magic happen.

                Button

                Button

System Info
No response
Validations

[X] Read the Contributing Guidelines.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Fixed in #3771
See playground


feat: allow same repository with different branches

Resolves https://github.com/BetaHuhn/repo-file-sync-action/discussions/51

Thanks!

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


Add hotkeys

User Story
As a player, I should be able to toggle the when elytra is automatically recast when holding space using a hotkey
and I should be able to toggle the jump cooldown logic with a separate hotkey
Goals

Add a hotkey to toggle elytra recasting logic
Add a hotkey to toggle jump cooldown logic

You can now bind a hotkey to toggle both elytra and jumping logic from the config


Atom does not function with the latest freetype2

Prerequisites

[X] Can you reproduce the problem in safe mode?
[X] Are you running the latest version of Atom?
[X] Did you check the debugging guide?
[X] Did you check the FAQs on Discuss?
[X] Are you reporting to the correct repository?
[X] Did you perform a cursory search to see if your bug or enhancement is already reported?

Description
Using freetype 2.6.3 on the latest commits of Atom cause the editor to crash open opening. freetype 2.6.2 works just fine.
Steps to Reproduce

Install freetype 2.6.3
Open Atom

Versions
$ freetype-config --ftversion
2.6.3
$ atom --version && apm --version
1.7.0-dev-a613fa5
apm  1.6.0
npm  2.13.3
node 0.10.40
python 3.5.1
git 2.7.1

Stacktrace

Already reported on the Electron page here. Closing.


Add ability to custom format time in TimePicker TextField

Problem description
Cannot custom format TimePicker TextField string: it'd be great if there was a prop similar to dateFormat in DatePicker that lets us custom format the time based on the Date passed in.
Link to minimally-working code that reproduces the issue

Versions

Material-UI: 0.17.0
React: 16.0.0-alpha3
Browser:

Sounds reasonable. We currently have a rather primitive formatter, but should probably be using date.toLocaleTimeString() instead. I'll mark this for consideration when TimePicker gets migrated to next.

+1
Hope we can pass a function / library to format time in TextField
And another separated switch for 24hr/ampm clock inside dialog.

Closing for #4796


Add blur handler to hide volume slider

When "alwaysShowControls" is set to true, using the keyboard to focus on the mute button causes the volume slider to appear, but leaving the control fails to hide the volume slider again. This modification updates the event handler to use the .on() method (as .bind() is deprecated in jQuery) and adds a handler for the "blur" event that explicitly hides the control.

@peterh-capella You can add a PR based on the 3.x-dev, so it can be merged immediately and be available for the 3.0 version; otherwise, you may have to wait until that version is released

I'd be happy to create another PR. Where is the 3.x-dev repository?

Look in the Code tab and then you will see branches. There you will find it

Closing this PR since it has been merged in 3.x-dev branch. Thanks


Unsupervised learning clustering metrics

Unsupervised learning clustering metrics online version: https://alibek228k.github.io/kbtu-ml-book/unsupervised_learning/clustering_metrics.html

Merging to master is prohibited


Update config.rs

I'm pretty sure that llvm path should not contain lib as per https://pub.dev/packages/ffigen.
On my computer I used --llvm-path /usr/lib/llvm-14 in justfile, when changing to /usr/lib/llvm-14/lib it does not work.

Can confirm that it is working now.


ListView: ToDo List view underlaps status bar on Android

I'm using a Samsung Nexus 10.1" tablet.

Same on Nexus 5X

This should be resolved in vNext


[vite] Internal server error: Failed to load PostCSS config

Qwik Version
<EMAIL_ADDRESS>"0.0.38"<EMAIL_ADDRESS>"0.0.23"
Operating System (or Browser)
Win10
Node Version (if applicable)
16.13.1 (Currently using 64-bit executable)
Which component is affected?
Starters / CLI
Expected Behaviour
Opening the initial page in the browser
Actual Behaviour
Steps to reproduce from the terminal:

npm init qwik@latest

Select a name to the project

Select starter: Qwik city

Select server: Cloudflare Pages

Select features: Prettier, Tailwindcss

Move to the project folder

Run npm install

Run npm start

Additional Information
Full error output: qwik_terminal_output.txt

I don't know, but it seems related to https://github.com/vitejs/vite/issues/5316

I ran into the same issue on linux. Following the error message I could at least rename the files to postcss.config.cjs and tailwind.config.cjs as a workaround.

Qwik City is using Vite 3 now, which went all in on ESM. CommonJS files need to be explicitly named as .cjs, like @dacki said. :+1:

had the same error. i removed the postcss.config.js and it works.
Vite 3.1.3

Thanks! also worked for me too!

mee too @chmich

do you mean renaming from postcss.config.ts to postcss.config.js? it works for me.

I solved this issue by deleting the node_modules directory, and ran npm i again.

mee too @chmich
Vite 3.2.0

Tive esse erro usando o linux ubuntu. Eu removi trocando a extensão .js do arquivo (postcss.config.js) para extensão .cjs ( postcss.config.cjs).

I solved this issue by deleting the node_modules directory, and ran npm i again.

This worked instantly

I have the same problem with vuetify 3, none of this above works for me. Any ideas ?

I had the same issue but when I removed postCSS.config file it worked!

For those who are trying to make Tailwind work with Vite, follow below steps:

Rename postcss.config.js to postcss.config.cjs (keep tailwind.config.js as it is)
Change the content of postcss.config.cjs as follows:
module.exports = ({ env }) => ({ plugins: [    require('tailwindcss')(), require('autoprefixer')() ] })

The above is array format for plugins.
Ref: Vite Postcss Config Postcss Load Config

In my case deleted type: mode from package.json resolved the issue

Add
"type": "module"
to package.json

What @phukao said also solved another problem for me. Only way to get svelte to run on vite.

``dfdf

@chmich, I'm using Svelte on WSL2. I was getting the same error, but I just run npm install -D tailwindcss postcss autoprefixer and it worked.

had the same error. i removed the postcss.config.js and it works. Vite 3.1.3

its worked

had the same error. i removed the postcss.config.js and it works. Vite 3.1.3

the best solution

Resolved this by upgrading to<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(on vite@3.1.3).

I ran into the same issue on linux. Following the error message I could at least rename the files to postcss.config.cjs and tailwind.config.cjs as a workaround.

Thaaaaaaaaaaaaaaaaaaaaks

module.exports = ({ env }) => ({ plugins: [ require('tailwindcss')(), require('autoprefixer')() ] })

nice. it works. thank you so much.

Replacing module.exports with export default worked for me
// postcss.config.js

export default {
  plugins: {
    tailwindcss: {},
    autoprefixer: {},
  }
}

I solved this issue by deleting the node_modules directory, and ran npm i again.

the best solutions thank you

Replacing module.exports with export default worked for me
// postcss.config.js

export default {
  plugins: {
    tailwindcss: {},
    autoprefixer: {},
  }
}

This is bext solution.

not working for me
"postcss": "^8.4.38",
"tailwindcss": "^3.4.1",
"vite": "^5.2.0"

@adamaslan looks like there's a ( on line 4 in your index.css file that it doesn't expect.

VITE v4.5.3. I rename postcss.config.js and this works for me. thanks....
Anyway, there is still no fixed solution to this problem, the solutions still vary. I don't know the root cause.

For those who are trying to make Tailwind work with Vite, follow below steps:
* Rename `postcss.config.js` to `postcss.config.cjs` (keep `tailwind.config.js` as it is)

* Change the content of `postcss.config.cjs` as follows:
  `module.exports = ({ env }) => ({ plugins: [ require('tailwindcss')(), require('autoprefixer')() ] })`

The above is array format for plugins. Ref: Vite Postcss Config Postcss Load Config

I had same issue and it worked for me using the above reference

I ran into the same issue on linux. Following the error message I could at least rename the files to postcss.config.cjs and tailwind.config.cjs as a workaround.

This helped me too 19/04/24

Here's the reworded response:

Here are the steps that worked for me:

I converted postcss.config.js to postcss.config.cjs.
I updated my tailwind.config.js file as follows:

/** @type {import('tailwindcss').Config}*/
export const content = ['./src/**/*.{js,jsx,ts,tsx}']
export const theme = {
  extend: {},
}
export const plugins = []

Finally, I ran npm run dev.

"postcss": "^8.4.38",
"postcss-import": "^16.1.0",
"tailwindcss": "^3.4.3",
"vite": "^5.2.10"

Only deleting the file postcss.config.js works.
Nothing else works

with VITE 4.5.3 Rename postcss.config.js to `postcss.config.mjs

removed the postcss.config.js and it will works.

remove autoprefixer: {} 22-06-2024

For those who are trying to make Tailwind work with Vite, follow below steps:

Rename postcss.config.js to postcss.config.cjs (keep tailwind.config.js as it is)
Change the content of postcss.config.cjs as follows:
module.exports = ({ env }) => ({ plugins: [ require('tailwindcss')(), require('autoprefixer')() ] })

The above is array format for plugins. Ref: Vite Postcss Config Postcss Load Config

thanks it works for me.

hi everyone.
I changed this code
module.exports = {   plugins: {     'postcss-import': {},     tailwindcss: {},     autoprefixer: {},   } }
to this
export default {   plugins: {     'postcss-import': {},     tailwindcss: {},     autoprefixer: {},   } }
and it helped

Tryed to change module.exports = { plugins: { 'postcss-import': {}, tailwindcss: {}, autoprefixer: {}, } }  to export default { plugins: { 'postcss-import': {}, tailwindcss: {}, autoprefixer: {}, } } and didnt worked, somehow deleting postcss.config.js and running "npm run dev" worked fine.

I ran into the same issue on linux. Following the error message I could at least rename the files to postcss.config.cjs (or postcss.config.mjs) and tailwind.config.cjs (or tailwind.config.mjs) as a workaround.

Thank you a lot! Good hint!!!


.locate_mask fails silently

Describe the bug
The .locate_mask command fails when run on local data. This is despite working if I run the example : https://histolab.readthedocs.io/en/latest/tissue_masks.html.
To Reproduce
The below is the code that fails
`
from histolab.slide import Slide
from histolab.masks import TissueMask
from histolab.filters.image_filters import (
BluePenFilter,
GreenPenFilter,
ApplyMaskImage,
Invert,
OtsuThreshold,
RgbToGrayscale
)
from histolab.filters.morphological_filters import (
RemoveSmallHoles,
RemoveSmallObjects
)
import os
import glob
#0. declare Test slides
blue_pen_markings = [
"slide_name"
]
#1. Declare paths
base_path = "base_path"
blue_pen_fullpath = glob.glob(os.path.join(base_path,blue_pen_markings[0],"*"))
slide_processed_path = os.path.join(blue_pen_fullpath[0], 'processed')
print(blue_pen_fullpath)
#2. create slide object and do checks - all good
attune_slide = Slide(blue_pen_fullpath[0], processed_path=slide_processed_path)
print(f"Slide name: {attune_slide.name}")
print(f"Levels: {attune_slide.levels}")
print(f"Dimensions at level 0: {attune_slide.dimensions}")
print(f"Dimensions at level 1: {attune_slide.level_dimensions(level=1)}")
print(f"Dimensions at level 2: {attune_slide.level_dimensions(level=2)}")
#3. look at slide - this works
attune_slide.thumbnail
attune_slide.show()
#4. create mask object
mask = TissueMask()
#5. print mask - this fails - no mask is shown
attune_slide.locate_mask(custom_mask)
#6. This will still print
print("success")
`
Expected behavior
I expect locate mask to show an image of the resulting mask overlaid on the slide, or to give an error warning. Instead, no image is shown and the next bit of code still runs.
Software (please complete the following information):

OS: Linux 3.10.0-1160.11.1.el7.x86_64
Python Version: 3.9.12
histolab version: 0.5.1
openslide version: 3.4.1
pillow version: 8.4.0

Additional context
If I run the test case from histolab I do not encounter this problem, which suggests to me that something is happening with regards to the images themselves. The .thumbnail and .show commands still work, so histolab does manage to import the images and show the initial details.
I appreciate this will probably be difficult to solve since it appears to be an image-based problem, but some guidance debugging this would still be appreciated if possible.

Dear @OncologyDS, thank you for opening this issue.
From the code snippet you posted, I can understand that you are calculating the locate_mask result but you are not storing it anywhere and so the value gets lost. This is because that method returns a PIL image, it doesn't show it automatically.
If you still want to run this as a script you can do
mask_location = attune_slide.locate_mask(custom_mask)
mask_location.show()

I hope this makes sense! :)
PS next time please format your markdown text to highlight your code, so it's easier to read :) you can find more information here

Dear @alessiamarcolini,
Thank you so much for the prompt reply. Indeed, storing the mask then using show worked. I should have thought of that! I'm confused as to why that's not needed in the test case but is for this.
I will have a read of those rules and try and format the code appropriately, it is indeed hard to read.
Hope you have a nice day.


assertVisible and scrollUntilVisible do not work as expected in webviews

Description
It looks like assertVisible and scrollUntilVisible do not respect visibility of ui elements in webviews as they are reported to be "visible" even if they are further down on the website.
Example script
- openLink: https://en.wikipedia.org/wiki/Elton_John
- assertVisible: "Early life"
- scrollUntilVisible:
   element:
     text: "Early life"
   timeout: 10000

Output

Expected Output
Failed assertion
(tested mainly on android, but i think iOS does not work either)

could be related to https://github.com/mobile-dev-inc/maestro/pull/698

Thanks for taking the time to raise this issue! There has been a lot of improvements and fixes on Maestro since this was raised so we’ll go ahead and close this one out as part of an issue cleanup - if you still experience issues after upgrading to the latest version of Maestro, please open a new issue with reproduction steps. Thanks again for using maestro!


Improve the Activity cell styles

This is very, very close to the design. Few, minor changes need to be made and we are good.
 Just a quick alignment and we are ready.
a) The date "11:13" is in the same line as "to: 0x9F...967E". Both are Source Sans Pro, 12 pt, Dove #727272. I think this is 6sp for Android.

b) Please move "Send ETH" and the "-1.503 ETH" a bit lower. They have to start after 7dp. In other words, we need more distance between the gray line at the top and "Send ETH". Everything else is place well.

Sorry for being picky, but paying attention to symmetry is a key for aesthetic look.
Good job!

@colourfreak please check the latest version and close if complete.

@colourfreak please check the latest version and close if complete.

"to colourfreak.eth" is not the right color - it should be #727272 and we are good.

in latest version it's dove / #727272


Deliver States Waiting App Store Connect Processing Even though Build has been Processed Already.

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description

When using deliver to upload an app to App Store Connect with version 2.02.30(2.2.30) with the following parameters:

After the upload, I see that the console:
INFO [2018-10-23 00:48:30.07]: You can tweet: "App Store Connect #iosprocessingtime 51 minutes"
INFO [2018-10-23 00:49:07.19]: Waiting App Store Connect processing for build 2.2.30 (2.2.30)... this might take a while...

However, the build has already been processed. On the Activity section on App Store Connect, I see the version as 2.02.30 and the build as 2.2.30. So it looks like Deliver command is truncating the leading zeros from the CFBundleShortVersionString. However, according to the Apple documentation the leading zeros are only truncated for CFBundleVersion and not CFBundleShortVersionString.

what fastlane build do you use?
probably the same issue

@pparmaei can you share the fastlane version you are using? Did similar version numbers cause problems in the past already?
The issues @Nov1kov linked to and created is very similar, and points to this being a regression of a change made in fastlane.

Hello @janpio
Using version 2.107.0
I have come across the same issue with multiple different apps that have leading zeros in their release version.


Implement pipelines + DevOps tooling

[x] set up main pipeline

[x] unit and integration tests
[x] code coverage reports (codecov has worked well in the Python version)
[x] publish to crates.io

[x] controlled by release-please
[x] split current bin-only package to bin + lib

[x] set up pre-commit hooks

Publishing to crates.io blocked by #13 , as we need all crates be publicly resolvable, aka we cannot have local dependencies such as common.

#13 done, and the last remaining pipeline step (publishing) was done in 52348c6 . Hasn't run yet but it's identical to other projects, where it works.


Support for client-side cache maximum size and eviction policies

Feature Request
The current implementation of ClientSideCaching adds elements to local cache when fetched from remote Redis cache however this local cache can grow indefinitely, there is no limit and no eviction policy.
It would be great to able to configure the local cache with a maximum size and a eviction policy to be able to limit the size and remove selected elements when local cache is full.
Is your feature request related to a problem? Please describe
The current client-side caching implementation can add elements indefinitely which can consume all available memory.
Describe the solution you'd like
Pass a maximum size an a eviction policy to ClientSideCaching which in turn will check the map size upon each put operation and perform the eviction when cache is full.

Lettuce doesn't try to abstract a fully fledged client-side cache, its support is limited to cache value loading and eviction upon notification. The map implementation is a simple variant to explain how the Map interface can be used to leverage proper cache implementations (Infinispan, Ehcache, Caffeine).


Improve history panel in streamlit app

[x] I've worked out how to convert one hot encoded obs back into obs, so make use of that to show the history from the agent pov (optionally)
[x] I think the action listed seems off/janky. worth a look
[x] Rather than use a streamlit slider, use a plotly slider so this doesn't trigger refreshes.

Could still use some improvements, like labelling  the tokens. but good enough for now.


Support VPA

Some notions about VPA:

It's applied to all containers of a pod, including sidecar containers(but not init containers)

it will keep the original ratio of requests and limits, for example
the original resource definitions are:
resources:
  requests:
    cpu: "0.1"
    memory: 1G
  limits:
    cpu: "0.2" // 2 times of the requests.cpu
    memory: 2G // 2 times of the requests.memory

and the recommendation resources are:
Target:
  Cpu:     100m
  Memory:  262144k

then the generated resource for pod are:
Limits:
  cpu:     200m // still keep 2 times of the requests.cpu
  memory:  524288k // still keep 2 times of the requests.memory
Requests:
  cpu:     100m
  memory:  262144k


adapt to whether we are root or not

local_action respect the become option.
ansible -s or become: yes inside the role. In such a case local files created belong to root.
For that reason it may be interesting to not create these files as root (although it's the developer machine).
But using become=no is not an option because the only task run on the server needs a root privilege.
owner=root group=http in tasks/issue-certs-copy.yml.
Since it's a file that is expected to be modified, at least this trick could be documented.

Well, the task in tasks/issue-certs-copy.yml is an example. It really depends on how your server environment looks like / works. I could remove the owner=root group=http and change the access rights to 0755 / 0644 in the example. It doesn't really matter in the end; you (as an admin) must know how your infrastructure looks like before you can adjust this task.


Empty lists on Welcome screen after upgrade to 0.28.1

Make sure these boxes are checked before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if any
[x] I have reproduced the issue with at least the latest released version of superset
[x] I have checked the issue tracker for the same issue and I haven't found one similar

Superset version
0.28.1
Expected results
After upgrade to Superset 0.28.1 (from 0.27.0) via Pip, there's nothing on welcome screen (dashboards, recently viewed, favourites), although I have for instance 3 favourites and I see they are being returned via Ajax call (Google Developer Tools). Happens in firefox and chrome.

@williaster I think this may be related to your recent SupersetClient refactor.

@mistercrunch are you saying that because you've you've debugged it and you can see that it's related to my changes?
I think this is actually due to broken reactable version. Basically we can either have a version that works in Prod, or one that works in Dev, but not both. Maybe 28.1 was cut with a version that only works for Dev? See #6142.
cc @kristw

@williaster to be honest I have no evidence it's due to SupersetClient just operating on intuition here.
0.28 was cut without much testing as an emergency fix to 0.27 that started failing, and knowing that it would be a while before we'd come up with a proper Apache release.

I am confident this is due to reactable.
I first increased the version because this behavior happens in development.
Then found that it fixes dev but breaks prod so I reported an issue (#5935).
A few weeks ago I downgraded reactable to make sure production works (#6142).

^That's consistent with my experience, production works right now and for dev you have to manually change the version for it to work locally.

I've downloaded repo from master, build assets and used them with 0.28.1 (with reactable on 1.0.02) and it works fine

So we have no reactable version that work in both cases? :(

sorry about the trouble @wowo, glad you found a workaround.
I agree we should move away from this one, @kristw has noted that there are ~10 components that use this lib now, so it's not super easy.
we could look into how hard it is to install different versions depending on dev vs prod to take away some of the urgency?

@mistercrunch It seems related to react 16
https://github.com/abdulrahman-khankan/reactable/issues/3


Add new data source type var

Describe your changes
Add claims_enabled var to dbt_project.yml to trigger Tuva Project claims marts to run following changes in the latest release of The Tuva Project package.
How has this been tested?
Ran dbt deps && dbt build in Snowflake, BigQuery, and Redshift.
Reviewer focus
Please summarize the specific items you’d like the reviewer(s) to look into.
Checklist before requesting a review

[ ]  (Optional) I have recorded a Loom performing a self-review of my code
[ ]  My code follows style guidelines
[ ]  I have commented my code as necessary
[ ]  (New models only) I have implemented generic dbt tests to validate primary keys/uniqueness in my model
[ ]  I have added at least one Github label to this PR

(Optional) Gif of how this PR makes you feel

Loom link

Review complete but GitHub is giving me a 404 when I submit my Approval.  By passing that step and merging.


Cargo install fails

Description
Compiling psm v0.1.21
error[E0282]: type annotations needed for Box<_>
--> /Users/mac/.cargo/registry/src/index.crates.io-6f17d22bba15001f/time-0.3.34/src/format_description/parse/mod.rs:83:9
|
83 |     let items = format_items
|         ^^^^^
...
86 |     Ok(items.into())
|              ---- type must be known at this point
|
= note: this is an inference error on crate time caused by an API change in Rust 1.80.0; update time to version >=0.3.35 by calling cargo update
Compiling crossbeam-epoch v0.9.18
Compiling serde_derive v1.0.197
Compiling zerofrom-derive v0.1.3
Compiling yoke-derive v0.7.3
For more information about this error, try rustc --explain E0282.
error: could not compile time (lib) due to 1 previous error
warning: build failed, waiting for other jobs to finish...
error: failed to compile typst-cli v0.11.1, intermediate artifacts can be found at /var/folders/t8/nxzks_d15vqfwlgttv2pdnq40000gp/T/cargo-install6WvTnp.
To reuse those artifacts with a future compilation, set the environment variable CARGO_TARGET_DIR to that path.
Reproduction URL
No response
Operating system
macOS
Typst version

[X] I am using the latest version of Typst

See https://github.com/typst/typst/issues/4659


[WIP] device: add xiaomi-lavender

I will probably merge this soon, but I still need to do a clean rebuild of the system image with the fbdev hack applied.
Though, let's see some reviews if you have it in yourselves :).

This is an "omnibus" PR of all features the new device required.
This adds the required plumbing to use mainline usb gadget through configfs for rndis only. Since I have observed that the rndis function name can change, I have added a temporary quirk for this specific gadget. I assume that the coming google-taimen port will add an additional target using gadgetfs. Hopefully ffs and adb works better there. For xiaomi-lavender there were some issues enabling it with rndis_bam. I do not know if it is expected to work or not. I may need to dive deeper into a MIUI system.
Other notable changes:

gcc 4.9 kernel builder (ugh)
fbdev hack

I figured out in e09a65311cf14f1de7a210d61346cbdc58b214bc what was up. This was keeping me up at night! Why was only this one device weird during initrd.
Turns out that pointing console= to a wrong location breaks things subtly.


Continuous fuzzing intergation

Hi Maintainers,
I would like to set up continuous fuzzing of jinja by way of OSS-Fuzz. Essentially, OSS-Fuzz is a free service run by Google that performs continuous fuzzing of important open source projects. OSS-Fuzz recently added support for Python and it would be great to have Jinja integrated. The only expectation of integrating into OSS-Fuzz is that bugs will be fixed. This is not a "hard" requirement in that no one enforces this and the main point is if bugs are not fixed then it is a waste of resources to run the fuzzers, which we would like to avoid.
In this PR https://github.com/google/oss-fuzz/pull/4761 I have done exactly that, namely created the necessary logic from an OSS-Fuzz perspective to integrate Jinja. This includes developing initial fuzzers as well as integrating into OSS-Fuzz. If you would like to integrate, could you please provide a set of email(s) that will get access to the data produced by OSS-Fuzz, such as bug reports, coverage reports and more stats. The emails should be linked to a Google account in order to view the detailed reports and notice the emails affiliated with the project will be public in the OSS-Fuzz repo, as they will be part of a configuration file.

Thanks, this looks interesting, however I don't have the time to manage another service like this. I know Google uses our projects extensively internally and externally, and I'd be happy to accept PRs their employees find as part of this program, all contributions are welcome. :-) Thank you.

Thanks, this looks interesting, however I don't have the time to manage another service like this. I know Google uses our projects extensively internally and externally, and I'd be happy to accept PRs their employees find as part of this program, all contributions are welcome. :-) Thank you.


Accessing property with bracket notation can sometimes incorrectly return an implicit any type

Bug Report

🔎 Search Terms
implicit any, property access
🕗 Version & Regression Information

This changed between versions 4.2.3 and 4.3.5

⏯ Playground Link

Playground link with relevant code
💻 Code

const obj = {
	A: 1,
	B: 1
};

// Ignore the implementation, it's about the inferred return type of the function, which should be "A" | "B"
const getRandomKey = () => Math.random() > 0.5 ? "A" : "B"

type Foo =  ReturnType<typeof getRandomKey> extends keyof typeof obj ? ReturnType<typeof getRandomKey> : never;

const randomKey = getRandomKey();
const casted: Foo = getRandomKey();

const randomKeyResult = obj[randomKey];
const castedResult = obj[casted];

🙁 Actual behavior
randomKeyResult has type 'number', but castedResult has type any
🙂 Expected behavior
Both randomKeyResult and castedResult should be type number.
If you look at the type of casted and randomKey, the types are identical: "A" | "B". Yet when using them to access a property, they behave differently. Note that in 4.2.3, this expected behavior was also the actual behavior.

looks like something changed in newer version where they are interpreting this line outputs differently
type Foo =  ReturnType<typeof getRandomKey> extends keyof typeof obj ? ReturnType<typeof getRandomKey> : never;
if I change this to
type Foo =  ReturnType<typeof getRandomKey>;
type of casted and randomKey both are numbers.
OR
if i type cast it at access time
type t = ReturnType1<typeof getRandomKey>; const castedResult = obj[casted as t];


Missing md files in the pipeline page

cf #269

[ ] CONTRIBUTING.md: https://nf-co.re/sarek/.github/CONTRIBUTING -> https://github.com/nf-core/sarek/blob/master/.github/CONTRIBUTING.md
[ ] CHANGELOG.md: https://nf-co.re/sarek/CHANGELOG -> https://github.com/nf-core/sarek/blob/master/CHANGELOG.md
[ ] CITATIONS.md: https://nf-co.re/atacseq/CITATIONS -> https://github.com/nf-core/atacseq/blob/master/CITATIONS.md

Won't fix this now that https://github.com/nf-core/nf-co.re/pull/456 is implemented, but the 404 errors that these give now suggest the correct GitHub URL 👍🏻


Build failure: error: 'GIT_BRANCH' was not declared in this scope

Compiling from master at 91d0cf1138ca52d4208aad49a753122b231d8a01 I get:
src/main.cpp: In function 'int main(int, char**)':
src/main.cpp:21:37: error: 'GIT_BRANCH' was not declared in this scope
   21 |                    .arg(VERSIONSTR, GIT_BRANCH, GIT_HASH, BUILD_TIMESTAMP);
      |                                     ^~~~~~~~~~
src/main.cpp:21:49: error: 'GIT_HASH' was not declared in this scope
   21 |                    .arg(VERSIONSTR, GIT_BRANCH, GIT_HASH, BUILD_TIMESTAMP);
      |                                                 ^~~~~~~~
src/main.cpp:21:59: error: 'BUILD_TIMESTAMP' was not declared in this scope; did you mean 'GL_TIMESTAMP'?
   21 |                    .arg(VERSIONSTR, GIT_BRANCH, GIT_HASH, BUILD_TIMESTAMP);
      |                                                           ^~~~~~~~~~~~~~~
      |                                                           GL_TIMESTAMP

Do you reproduce this issue?

Hi, can you check now? With 14f190c03bba24aafb22f85134fb85d9b3ddf4ab it should be fixed.

it works for me now


Remove whole $KUBECONFIG_ROOT_DIR when cleanup

Instead of only removing config-kepler file, remove the whole .kube dir created by cluster_up().

sorry for reply late, as we enabled DCO checking, please follow the hint here to sign your commit. https://github.com/sustainable-computing-io/local-dev-cluster/pull/81/checks?check_run_id=25121982308
It seems no harmful for remove the config folder. @marceloamaral wdyt?


Improvements suggestions

Add schema and comment support in tableInfo and columnInfo for all vendors
Add primary information in tableInfo
Add is_view information in tableInfo and stop filtering them out
Delegate name aliasing and type conversion to the database query to bypass conversion from RawColumn to Column
Refactor knex queries to raw SQL to improve readability when appropriate
Unify test between vendors
Move table creation SQL code to test specs.

Opinion? 🥬

Initially I was for using Knex queries wherever possible, but this turned a bit to more a hack with all those Knex raw mixtures.
Eventually it is all raw queries, so we might just enter them directly instead double translating then through Knex.

Fully agree with @gpetrov here! The only perks to the Knex approach are the conditional "if A then query.where(A)" thingies, but those should be easy enough to refactor too.
For the other points:
✅ Add schema and comment support in tableInfo and columnInfo for all vendors
(for the vendors that support them. IIRC MySQL doesn't differentiate between schema/database, and sqlite doesn't have comments f.e.)
✅ Add primary information in tableInfo
✅ Add is_view information in tableInfo and stop filtering them out
✅ Delegate name aliasing and type conversion to the database query to bypass conversion from RawColumn to Column
The only reason it isn't like that right now is my lack of knowledge of all the specific SQL casting stuff in the different vendors 😁
✅ Refactor knex queries to raw SQL to improve readability when appropriate
❓ Unify test between vendors
Mind clarifying what you mean by unify in this case?
✅ Move table creation SQL code to test specs.

✅  Adding schema and comment support in tableInfo and columnInfo for all vendors
✅  Adding primary information in tableInfo
Adding is_view information in tableInfo and stop filtering them out
Delegate name aliasing and type conversion to the database query to bypass conversion from RawColumn to Column
Refactor knex queries to raw SQL to improve readability when appropriate
Unify test between vendors

IIRC MySQL doesn't differentiate between schema/database

It's just that the default schema in MySQL is named after its database, instead of being named public like others vendors - but it behaves exactly like them.

Mind clarifying what you mean by unify in this case?

Creating the exact same table configuration in each database so the expected result from each test can be shared (avoid code duplication, and reduce chances of error when adding a new feature (like the generated attribute, or upcoming is_view )).

Awesome! Thank you @Oreilles ❤

It's just that the default schema in MySQL is named after its database, instead of being named public like others vendors - but it behaves exactly like them.

Are you sure about that? From MySQL's reference manual:

In MySQL, physically, a schema is synonymous with a database. You can substitute the keyword SCHEMA instead of DATABASE in MySQL SQL syntax, for example using CREATE SCHEMA instead of CREATE DATABASE.
Some other database products draw a distinction. For example, in the Oracle Database product, a schema represents only a part of a database: the tables and other objects owned by a single user.

As far as I can tell, MySQL treats SCHEMA == DATABASE and schema's don't have behavioral characteristics you'd find in the other vendors 🤔

OK, that's weird... It means that  their concept of a database is different than others. (You can't query table from a database while being in another one in other vendors, but apparently with MySQL you can).

So it'd be better to say that they don't support databases, but only support schemas? 🤔


✨(models) add marsha video events pydantic models

Purpose
Video events from marsha will be tracked for Potsie dashboards. We implement their pydantic models to stream them in ralph.
Proposal

[x] initialized
[x] paused
[x] seeked
[x] completed
[x] terminated
[x] interacted

(played already implemented in PR #96)

Nice work!
I tried to validate real world statements using your model definitions for video statements and I found that we should add minor improvements to this work/ralph:

We should define the __selector__ attribute for every xAPI model (video + navigation),

It's a miss on my part. Thanks!

The ralph.models.xapi module should define every active model (for reference see https://github.com/openfun/ralph/blob/master/src/ralph/models/edx/init.py),

:+1:

The validate command should add xapi to supported formats, and,

Indeed. Thanks!

The ModelSelector should raise an exception if no rules have been found for a format*.

This point can be handled in a new PR (ping @SergioSim )


Correct process to add a Collider

Hello and thank you for bevy_ecs_tilemap! I'm playing with tilemaps and bevy_xpbd, and I wonder if perhaps this is just inexperience or if I'm encountering a side effect of #500, but I'm having a hard time getting tiles in a tilemap to collide with a player object (just a 2d mesh with a transform, an xpbd RigidBody::Dynamic and an xpbd Collider).
Given something like this, I notice there are invisible colliders in the middle of the tilemap square, but nothing around its edges:
fn generate_level_map(asset_server: Res<AssetServer>, mut commands: Commands) {
    let tilemap_entity = commands.spawn_empty().id();
    let map_size = TilemapSize { x: 64, y: 64 };
    let texture_handle = asset_server.load("textures/tiles.png");
    let map_type = TilemapType::Square;
    let tile_size = TilemapTileSize { x: 16., y: 16. };
    let grid_size = tile_size.into();

    // Each room can have its own tilemap, at least for now.
    let mut room_storage = TileStorage::empty(map_size);

    for x in 0..map_size.x {
        for y in 0..map_size.y {
            if x == 0 || x == map_size.x - 1 || y == 0 || y == map_size.y - 1 {
                let tile_pos = TilePos { x, y };
                let center = tile_pos.center_in_world(&grid_size, &map_type);

                let tile_entity = commands
                    .spawn((
                        RigidBody::Static,
                        Collider::cuboid(16., 16.),
                        SpatialBundle::from_transform(Transform::from_xyz(center.x, center.y, 0.)),
                        TileBundle {
                            position: tile_pos,
                            tilemap_id: TilemapId(tilemap_entity),
                            ..Default::default()
                        },
                    ))
                    .id();
                room_storage.set(&tile_pos, tile_entity);
            }
        }
    }

    let transform = get_tilemap_center_transform(&map_size, &grid_size, &map_type, 0.0);

    commands.entity(tilemap_entity).insert(TilemapBundle {
        grid_size,
        map_type,
        size: map_size,
        storage: room_storage,
        texture: TilemapTexture::Single(texture_handle),
        tile_size,
        transform,
        ..Default::default()
    });

    #[cfg(all(not(feature = "atlas"), feature = "render"))]
    {
        array_texture_loader.add(TilemapArrayTexture {
            texture: TilemapTexture::Single(asset_server.load("textures/tiles.png")),
            tile_size,
            ..Default::default()
        });
    }
}

(adapted from the basic example). I'd be happy to contribute an example once I get all this cleared up, but it's entirely possible I've just misunderstood the basics. Any pointers to examples or clarifying where I'm going wrong would be super helpful.

(screenshot shows player in green, enemy in red, tile "wall" in orange and obviously not colliding with anything).

Adding a physics debug visualization will help you here. Here's how to do that in xpbd.
Your issue seems to be that your Tilemap has a transform that our individual tiles aren't inheriting. You can either add
commands.entity(tilemap_entity).add_child(tile_entity);

to your tile spawning code, or remove the offset from the Tilemap.

That's immediately so much clearer! Colliders were nowhere near the tiles.

Adding the tile as a child of the map works a treat (I wasn't sure how to go about removing the offset).
Would a simple example of tile collision be useful, or is it a bit much given it'd add bevy_xpbd as a dev dependency?

or is it a bit much given it'd add bevy_xpbd as a dev dependency?

I know @StarArawn has been contemplating removing the tiled and ldtk examples recently, with the goal of reducing the scope of this project a bit. So I think that a PR like that would be unlikely to get merged. It seems like a useful example to show the world, but maybe not as an example in this repository.

Exactly right. I might chuck something in a gist and link it from here, should be sufficient documentation.

This should do the trick: https://github.com/richchurcher/tile_collision_example_xpbd
Cheers!


[vm] dartaotruntime_stripped_binary Build argument has no effect.

When building the latest commit from master.
WARNING at build arg file (use "gn args <out_dir>" to edit):28:34: Build argument has no effect.
dartaotruntime_stripped_binary = "exe.stripped/dartaotruntime"
                                 ^----------------------------
The variable "dartaotruntime_stripped_binary" was set as a build argument
but never appeared in a declare_args() block in any buildfile.

To view all possible args, run "gn args --list <out_dir>"

The build continued as if that argument was unspecified.

cc @cskau-g

I believe this might be a result of a recent change of @mkustermann's.

@dcharkes Might this be due to an left-over out/<build-dir> folder?
Try either re-running tools/gn.py ... or removing the out directory.

Gonna close the issue, please re-open if above steps don't work.


HALON-467: Repair not starting after second drive failure (#1066)

Created by: nc6

Add additional debug lines

Introduce 'RestartSNSOperation' rule.

This is needed for when an SNS operation is in progress as a drive
transitions to FAILED. In this case, we need to abort and then
restart repair.

HALON-540: store pool repair information before starting repair.

Re-organise rules in Repair module.

Means we don't have to edit multiple files
if we add new rules.

HALON-358: Remove allProcessChangesNode rule. (#1064)

This rule is no longer required.

Do not start rebalance when drives are REPAIRING.

Revert "HALON-540: store pool repair information before starting repair."

This partially reverts commit c09cec509bca00b408288cc66645e921f6c9450b.
We keep the additional calls to 'unsetPoolRepairStatus'.

Verify pool device state after starting repair.

Couple of random fixes (not sure why these are needed).

Allow 'PAUSED" as a ready state.

This was suggested by Mandar at https://seagate.slack.com/archives/mero/p1478771740000264

Remove timeout in restart rule.

Given this is waiting for other jobs, just remove this in
its entirety. Doesn't help to have the restart job die but
underlying jobs keep running.

Allow PAUSED state in other check.

Closing as an obsolete


Disable failing distributed actor tests.

Example Failure: https://ci.swift.org/job/oss-swift-incremental-ASAN-RA-macos//408/console
Resolves rdar://92277271

Thanks


[main] Upgrade to latest dependencies

Cron -knative-prow-robot
/cc knative-sandbox/networking-wg-leads
/assign knative-sandbox/networking-wg-leads
Produced by: knative-sandbox/knobots/actions/update-deps
Details:
bumping knative.dev/hack 69a2295...813559c:
  > 813559c [pre-1.0] Use the TAG unmodified when publishing dot releases (# 119)
  > 9f34905 Update community files (# 118)
bumping knative.dev/networking bab26a8...75d86c5:
  > 75d86c5 upgrade to latest dependencies (# 574)

/lgtm
/approve


Release stable version for Interactive audits

v0.3.5 should be released (a version that's in sync with the driver/spec/interactive repository)

Done: https://github.com/ldbc/ldbc_snb_datagen_hadoop/releases/tag/v0.3.5


Fix Indent

Thanks, but we're not interested in specifying a coding style for our automatically deployed demo assets.

gh-pages branch is generated automatically with npm run publish-to-gh-pages. Your PR will be overridden as soon as we publish a new version of the demo. In the future, don't hesitate to start an issue before actually doing a Pull-Request. However we gladly accept your help, don't hesitate to take one of our current issue :)


fishnet: 2.5.1 -> 2.7.1

Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Builds and runs with doCheck = false. Otherwise fails because Stockfish/src/${nnueFile} somehow disappears from the source directory during the build (it's still there after postPatch), which causes make net to fail trying to download the file.

I added a line to copy the nnue file again after the build so that the checks that happen next don't fail.
@tu-maurice can please review this?

Note that whatever caused fishnet to be marked as only supporting x86_64 doesn't seem to be an issue anymore, everything is working fine on on aarch64-linux.
So the platforms limitation can probably be removed.

I found the autoPatchelfHook issue at #113930. Since autoPatchelfHook is no longer used, I will remove the platform restriction.

The package is actually not building  on darwin, I will limit the platforms to aarch64-linux and x86_64-linux


"AttributeError: module 'deep_tabular_augmentation' has no attribute 'AutoencoderModel'"

Hi,
I have tried to execute the tutorial on this page:
https://github.com/lschmiddey/fastpages_/blob/master/_notebooks/2021-04-10-DeepLearning_TabularDataAugmentation.ipynb
But when I installed the library and initiated the model, I got this error:
AttributeError: module 'deep_tabular_augmentation' has no attribute 'AutoencoderModel'
Thanks

Hi Nada,
I did some refactoring to the package since then, basically the model itself is now only called "Autoencoder":
`D_in = X_train_fraud.shape[1]
VAE_arch = [50, 12, 12]
target_name = 'Class'
target_class = 1
df_cols = list(df.columns)
model = dta.Autoencoder(D_in, VAE_arch, latent_dim=5).to(device)`
Try for example this tutorial here: https://lschmiddey.github.io/fastpages_/2022/02/19/DataAugmentation_vs_SMOTE.html
I hope this helps :) If not just message me.
Lasse

Hi Lasse,
Sorry, I followed an old tutorial -_-.
Thank you very much for the clarification.


Rename Yoga imports to capital case

Summary
In addition of the issue resolved by https://github.com/facebook/react-native/pull/26360 (already merged), machines with case-sensitive disks are still not able to build a project on Xcode due mis-spelled <yoga/... imports:
'yoga/Yoga.h' file not found

Changelog

[iOS] [Fixed] - Fix Yoga imports case sensitivity
Test Plan

Build command on Xcode now runs successfully in a Mac with disk in case-sensitive mode

Thanks for the fix :)

Hey @gabrielfurini this PR isn't landing internally because we use an internal version of Yoga which is defined in lowercase.
I'm quite surprised this broke actually. Looking at the cocoapods docs the module_name modifier set to 'yoga' here should've been enough to nullify the podspec rename.
Can you try adding spec.header_dir = 'yoga' to the podspec and seeing if that fixes your issue?

Hey @PeteTheHeat, I see...
Actually adding spec.header_dir = 'yoga' to the podspec fixes the problem and makes the project build again w/o renaming imports or includes. 🙌
What should we do now? Should I close this PR and open another one or you guys are gonna take care of it anyways?
Btw, would be a pleasure contributing to the repo :)

Oh sweet, glad that fixes the issue :D
If you undo the header changes and amend that one line to this PR, I can re-import and land it for you 👍

I will cherry-pick this directly to 0.61-stable as soon as it lands

Amazing, guys!
The commits renaming things are reverted and Yoga.podspec file is updated.
Also edited the PR title and description.

@grabbou I don't think a cherry pick to 0.61 is needed, I don't think the Flipper/yoga changes made it into 0.61 did it?

@PeteTheHeat we have cherry-picked one Yoga commit at the beginning and unfortunately, it caused this issue. I'll pick it.


Kobo Glo bricked

Hello, I tried to update my Kobo Glo HD but I miss used with a standard Kobo Glo firmware. It is now stuck to black screen of the death. How to factory reset the device?
Thanks

OK I solved this by detaching the rear case, removing the SD card, inserting it in my PC, unzip the kobo glo upgrade in .kobo folder, replacing the SD card into the Kobo device and it worked flawlessly.


Incompatible with flutter_driver

[test_projectt] flutter pub get
Running "flutter pub get" in test_projectt...
Because every version of flutter_driver from sdk depends on file 6.0.0-nullsafety.2 and every version of flutter_audio_recorder depends on file ^5.0.4, flutter_driver from sdk is incompatible with flutter_audio_recorder.
So, because test_projectt depends on both flutter_audio_recorder ^0.5.5 and flutter_driver any from sdk, version solving failed.
pub get failed (1; So, because test_projectt depends on both flutter_audio_recorder ^0.5.5 and flutter_driver any from sdk, version solving failed.)
exit code 1
Flutter verbose:
PS C:\Users\Harry\Desktop\Repo\test_projectt> flutter doctor -v
[√] Flutter (Channel stable, 1.22.2, on Microsoft Windows [Version 10.0.18363.1256], locale en-PK)
    • Flutter version 1.22.2 at C:\src\flutter
    • Framework revision 84f3d28555 (10 weeks ago), 2020-10-15 16:26:19 -0700
    • Engine revision b8752bbfff
    • Dart version 2.10.2

[√] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at C:\Users\Harry\AppData\Local\Android\sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    • All Android licenses accepted.

[√] Android Studio (version 4.0)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 46.0.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[√] VS Code (version 1.52.1)
    • VS Code at C:\Users\Harry\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.13.2

[√] Connected device (1 available)
    • Android SDK built for x86 (mobile) • emulator-5554 • android-x86 • Android 10 (API 29) (emulator)

• No issues found!

Any help will be appreciated.

same issue

same issue


bcmemmc2: Change NTarm64 to NT$ARCH$

CI indicates that InfVerif is throwing build errors.
d:\a\windows-drivers\windows-drivers\drivers\sd\bcm2711\bcmemmc2\bcmemmc2.inx
: error 1203: Section [broadcom.ntarm] not found.
[D:\a\windows-drivers\windows-drivers\drivers\sd\bcm2711\bcmemmc2\bcmemmc2.vcxproj]
Change the section naming to NT$ARCH$
Signed-off-by: Christopher Co<EMAIL_ADDRESS>

Looking a bit closer, this is probably not the full fix. On the ARM64 CI builds, looks like bcmemmc2 is actually building for ARM - https://github.com/christopherco/windows-drivers/pull/3/checks?check_run_id=2154886827
Not sure if bcmemmc2 is meant to build for both ARM and ARM64, but at least this change makes CI happy.

There's a mistake in the solution file that makes bcmemmc2 build for ARM when the configuration is in fact set to ARM64 Debug. I'll push the fix after merging this.

https://github.com/raspberrypi/windows-drivers/commit/7e437d47fa6e68247aa9722411dea9d40d7ce49d


Initialize 'ret' value

Initialize value to prevent run-time check failures: "The variable 'ret' is being used without being initialized"

Looks good to me. Does someone want to merge it?

@avinash-palleti - can you please merge this?


feat: add retryWithBackoff utility

Codecov Report

Merging #22 (2a62aab) into main (0bc651b) will decrease coverage by 1.14%.
The diff coverage is 62.50%.

@@            Coverage Diff             @@
##             main      #22      +/-   ##
==========================================
- Coverage   95.53%   94.39%   -1.15%
==========================================
  Files          26       26
  Lines        1389     1427      +38
  Branches      369      383      +14
==========================================
+ Hits         1327     1347      +20
- Misses         60       78      +18
  Partials        2        2

Impacted Files
Coverage Δ

src/tree/tree.ts
96.58% <33.33%> (-2.91%)
:arrow_down:

src/node.tsx
92.10% <40.00%> (-7.90%)
:arrow_down:

src/use-hotkeys.ts
96.21% <40.00%> (-2.23%)
:arrow_down:

src/use-dnd.ts
95.32% <50.00%> (-4.68%)
:arrow_down:

src/use-file-tree-snapshot.ts
96.29% <50.00%> (-3.71%)
:arrow_down:

src/index.ts
76.92% <100.00%> (ø)

src/utils.ts
96.47% <100.00%> (+0.81%)
:arrow_up:

Continue to review full report at Codecov.

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


Less-than operator in Javascript is parsed incorrectly

When you use the '<' operator for an if statement or a for loop in javascript (in the cshtml file) it seems to get parsed weirdly which results in an 'unexpected end of input' error in the console.

When you look at the Element pane in the browser dev tools you can see that it seems to have split the code on the '<' operator.

This is what my page looks like:
@page "/grid"

<script type="text/javascript">
    (function () {
        console.log("hello");
        for (var i = 0; i < 10; i++) {

        }
    })();
</script>

I have the following installed:

Visual Studio Community 2017 Preview (15.7 Preview 3)
.NET Core 2.1 Preview 1 SDK
ASP.NET Core Blazor Language Service Extension

A simple workaround for the above code snippet is to reverse the check to '10 > i' as the '>' operator seems to be parsed correctly. However I would expect 'i < 10' to work.

@ig-robstoffers You are not allowed to put script tags in components.

@miroslavp Interesting...  Then if you have javascript that you want to run when your component is initialized, what is the expected process?  Do I keep put the javascript in index.html and then interop to it in my components OnInit?

If you upgrade to 0.2.0, it will block script tags in components because they almost certainly aren’t helpful there. Script tags must go into a static context such as index.html.
Please see #552 for more info.

And yes you are correct in your last comment :)

Thanks for the help!  That clears that up.


adding ddmpraha9.cz

@maskac First stage of verification passed, official domain for Dům dětí mládeže Praha 9 is ddmpraha9.cz as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@maskac Regrettably, I have to close the request without merging, because this organization is a training center, not a college, nor a university. Please ensure that you are familiar with this repository rules located at the bottom of this page.
Please apply for an appropriate licensing option (which may also be free) at https://www.jetbrains.com/community/education/#courses.
Thank you for your understanding!