Please help me compile for Fedora 24

Hello,
I am new to Linux and the instruction for how to compile for Fedora relate to Fedora 20 which is many years old... and I have no idea what is involved :(
It's taken me about 5 hours research to just get to the point of narrowing down this software as the best chance to get Valhalla Vintage Verb working in Linux... it's all I want! (pathetic humble face)
I understand the legal issues with distributing the Steinberg stuff but.... AAARGGGHHHH?! :)
Can anyone help me with a pre-compiled file so I can try to get this working in Fedora 24 and Ardour? There were some ancient versions in this thread, but I would really like the latest:
https://www.kvraudio.com/forum/search.php?keywords=fedora&t=415929&sf=msgonly
The thought of dealing with SELinux issues right now makes me want to vomit!

Hi!
I don't use RPM based Linux distribution myself thus I can't build the package for you. But... could you please contact the user "StudioDave" on kvr forums and ask him to send you his build? He uses Fedora and I think he will be glad to help you.

We'll get him squared away. :) I'll be happy to send my binaries, but note that I'm on Fedora 21 x86_64. If I recall correctly I was unable to build the 64-bit version of Airwave, so I can send only the 32-bit version now, i.e. he'll only be able to convert 32-bit plugins. I'll double-check to see if I have a 64-bit version from a previous build.

Cheers guys!!!
64bit would be amazing as nearly all my plugins i want to use are 64bit :) Maybe I can locate 32 bit versions if I need to... but 32 bit is legacy now?
I don't yet understand the differences between a Fedora 21 build and a Fedora 24 build, does that mean older versions of dependencies would be compiled into it?

Some time ago I tried building the 64-bit version. Unfortunately the process of installing the required dependencies completely wrecked my rpm and apt systems. In the end I had to re-install the distro, so I am very unwilling to try building the 64-bit version again.

Okay, here's the files from /usr/local/bin in a tarball. Open the tarball in your $HOME directory, it will create a directory named aw4lda. Copy all the files from that directory into your /usr/local/bin, make sure then try running the airwave-manager GUI. Let us know what happens next. :)
aw4lda.tar.gz

If I were use Windows, I would use 64 bit plugins, of course. But in the case of Linux and wine I prefer 32 bit ones. Usually they work better for me.

I am running the airwave manager right now! :) THANKS!
I think i figured out how to use it,  this Fedora version only for 32bit VST plugins? I tried to add an x64 plugin and Ardour just kept scanning and never accepted it.
I tried to add spitfish.dll, and Ardour did accept it but when I loaded it Ardour just exited and I got the following message. Is this just a plugin that won't work, or maybe something is wrong with my install or the compiled binary? Thanks!
1478611102.856734533          SPITFISH.so : Initializing plugin endpoint 1.3.2
1478611102.856744605          SPITFISH.so : Plugin binary: /home/david/vst-win/SPITFISH.so
1478611102.856760313          SPITFISH.so : WINE prefix:   /home/david/.wine
1478611102.856788115          SPITFISH.so : WINE loader:   /usr/bin/wine32
1478611102.856796126          SPITFISH.so : VST binary:    /home/david/.wine/drive_c/VSTPlugIns/SPITFISH.dll
1478611102.858697646          SPITFISH.so : Host binary:   /usr/local/bin/airwave-host-32.exe
1478611102.858704359          SPITFISH.so : Log level:     trace
1478611102.859054124          SPITFISH.so : Callback thread started
1478611102.859085675          SPITFISH.so : Waiting response from host endpoint...
1478611102.973337838         SPITFISH.dll : Initializing host endpoint 1.3.2
1478611102.975077306         SPITFISH.dll : Waiting for plugin endpoint request...
1478611102.975087633         SPITFISH.dll : Request from plugin endpoint received, sending response
1478611102.975095633         SPITFISH.dll : Initializing VST plugin...
1478611103.270422880         SPITFISH.dll : VST plugin is initialized
1478611103.270435782         SPITFISH.dll : Host endpoint is initialized
1478611103.270463844          SPITFISH.so : Plugin endpoint is initialized
1478611103.270727710         SPITFISH.dll : Audio thread started
1478611103.271314856          SPITFISH.so : Closing plugin
1478611103.271323654          SPITFISH.so : Waiting for callback thread termination...
1478611103.369404359          SPITFISH.so : Callback thread terminated
1478611103.369524314          SPITFISH.so : Waiting for child process termination...
1478611103.372923385         SPITFISH.dll : Control port isn't connected anymore, exiting
1478611103.372935443         SPITFISH.dll : Terminating the host endpoint...
1478611103.372938334         SPITFISH.dll : Waiting for audio thread termination...
1478611103.470908823         SPITFISH.dll : Audio thread terminated
1478611103.481729739         SPITFISH.dll : Host endpoint terminated
1478611103.483594614          SPITFISH.so : Child process terminated
1478611103.483622438          SPITFISH.so : Plugin endpoint terminated
1478611125.839947312          SPITFISH.so : Initializing plugin endpoint 1.3.2
1478611125.839965160          SPITFISH.so : Plugin binary: /home/david/vst-win/SPITFISH.so
1478611125.839992195          SPITFISH.so : WINE prefix:   /home/david/.wine
1478611125.840129155          SPITFISH.so : WINE loader:   /usr/bin/wine32
1478611125.840142343          SPITFISH.so : VST binary:    /home/david/.wine/drive_c/VSTPlugIns/SPITFISH.dll
1478611125.841515127          SPITFISH.so : Host binary:   /usr/local/bin/airwave-host-32.exe
1478611125.841519307          SPITFISH.so : Log level:     trace
1478611125.844284116          SPITFISH.so : Callback thread started
1478611125.844349423          SPITFISH.so : Waiting response from host endpoint...
1478611125.916900362         SPITFISH.dll : Initializing host endpoint 1.3.2
1478611125.918243751         SPITFISH.dll : Waiting for plugin endpoint request...
1478611125.918253915         SPITFISH.dll : Request from plugin endpoint received, sending response
1478611125.918262358         SPITFISH.dll : Initializing VST plugin...
1478611126.021022117         SPITFISH.dll : VST plugin is initialized
1478611126.021034597         SPITFISH.dll : Host endpoint is initialized
1478611126.021070849          SPITFISH.so : Plugin endpoint is initialized
1478611126.021371854         SPITFISH.dll : Audio thread started
1478611126.121466540         SPITFISH.dll : Audio thread terminated
1478611126.132047222         SPITFISH.dll : Audio thread started
1478611126.314094821         SPITFISH.dll : Unable to create window: Resource data not found.
1478611126.314143540         SPITFISH.dll : Terminating the host endpoint...
1478611126.314147634         SPITFISH.dll : Waiting for audio thread termination...
1478611126.332740574         SPITFISH.dll : Audio thread terminated
1478611126.343610129         SPITFISH.dll : Host endpoint terminated
1478611126.344961844          SPITFISH.so : Child process terminated

https://github.com/phantom-code/airwave/issues/60
No, this line tells that CreateWindowEx() call failed

I have successfully added MJUC, TDR Nova and TDR VOS SlickEQ! Congratulations on this software!
Unfortunately 30 seconds into testing when I pressed the ? button in slickEQ I got a crash with this error report:
backtrace.txt
I think it will take a lot of testing to see what is really working stably. Thanks again davephillips for the upload.
In my humble opinion this plugin could really revolutionize Linux audio and help give the finger to microsoft, but it needs:

A binary download.

I can see this is a 'grey area' legally, but there needs to be some 'unofficial' build link. For example, the http://rpmfusion.org guys host all kinds of 'grey area' programs such as mp3 codecs etc. Also there are sites like https://copr.fedorainfracloud.org/ which

"is an easy-to-use automatic build system providing a package repository as its output"

Publicity, which will lead to more testing, which will lead to bug eradication.

I run a site which gets about 200 individual hits a day from computer audio people, but I can't really write a tutorial and review if my readers can't download the software :( I don't mind hosting a compiled version... If Steinberg give me a take down notice I will comply of course, but i really doubt they would bother.

@Learn-Digital-Audio  Some plugins require a native dll's to work in wine. Some i've had to add the d2d1.dll by hand to the Wine prefix i was using for them and in one case i had to add native d3dx10  dlls using winetricks. Other plugins might require installing gdiplus also installed using winetricks. For example to get winetricks to use the prefix in a terminal you could try (assuming you have winetricks installed):
env WINEPREFIX=~/.wine.vsts winetricks gdiplus d3dx10 to install both
Other times some will run better with various versions of windows settings and you can tweak that by running:
env WINEPREFIX=~/.wine.vsts winecfg
Each plugin that fails may require special attention to get it running.
Note this is true of any windows based program or app running through Wine. Sometimes though no matter some software will just fail to run in Wine no matter how much tweaking you do usually because some bit of Windows API isn't support or due to bugs in the plugin or software.

cheers  draekko! if you, or anyone else, has any settings to make valhalla vintage reverb work please share the wealth :)

I'm using wine staging just tried it on Ubuntu (using wine staging ppa's) and it worked flawlessly. I piped DSK Dynamic guitar into it. I tried it with the demo from https://valhalladsp.com/shop/reverb/valhalla-vintage-verb/ and am on wine staging 1.9.22. Ran the setup with :
env WINEPREFIX=~/.wine.vst.valhalla wine ValhallaVintageVerbWinDemo_V1_5_0dot6.exe
it created a new prefix and then i updated with airwave-manager as usual.  Maybe your version of wine is to "old" :)

mmm, i am on wine-1.9.19 (Staging) right now, i will try updating it, cheers!

Thanks for help, but I moved to LinVST.


Add SMCIPMITool for ibmcloud BM deployments

I was getting errors when trying to manually mount virtual media on some ibmcloud nodes, however I tried this new PR and the SMCIPMITool method (using smcipmitool_url) worked beautifully, great work!!


Update minimum version of typing extensions in pre-commit

Attempt to fix the pre-commit build failure I keep seeing in the CI (e.g. this failure from https://github.com/pydata/xarray/pull/7881)

That seems to have fixed the issue, so I'll plan to merge this soon.


[SPARK-39686][INFRA][FOLLOW-UP] Disable SparkR build in branch-3.2 with Scala 2.13

What changes were proposed in this pull request?
This PR is a followup of https://github.com/apache/spark/pull/37091 that disables the SparkR build that has never passed in history at branch-3.2 with Scala 2.13.
See also SPARK-39712 (https://github.com/apache/spark/runs/7228058532?check_suite_focus=true)
Why are the changes needed?
To have the very first green in the build.
Does this PR introduce any user-facing change?
No, dev-only.
How was this patch tested?
CI in the scheduled jobs should test it out.

cc @Yikun FYI

Merged to master.


Create 132-pattern.cpp

this is amazing @aryangulati
thanks for the contribution in my repo and please share in social media and tag me on twitter


Allow command-line block to be indented

Allow a command-line code block to be indented. Prior to this change, an indented block would not close properly and the rest of the page was messed up. Indented code blocks is necessary to continue numbered lists. Now the regex allows zero or more whitespace at the beginning of each line. The change includes tests.
Fixes #13

Seems incredibly legit. Thank you! I'll put this out as 0.4.7.

@gjtorikian That's amazingly fast! Thanks

I dislike PRs that linger and don't get released. 😃  It's literally a TextExpander (;gembump) and a single command (be rake release) to get it all out.


feat: Restructure Into Workspace

Description
Restructure amble into a workspace.
Fixes #30.

Current dependencies on/for this PR:

main

PR #62   👈

This comment was auto-generated by Graphite.


[BugFix] Update corePoolSize before maximumPoolSize in task executor

Must set corePoolSize first, because setMaximumPoolSize() will throw IllegalArgumentException if maximumPoolSize < corePoolSize.
Fixes #issue
What type of PR is this:

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.1
[x] 3.0
[x] 2.5
[ ] 2.4

[FE Incremental Coverage Report]
:heart_eyes: pass : 1 / 1 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/task/PriorityLeaderTaskExecutor.java
1
1
100.00%
[]

[BE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

@Mergifyio backport branch-3.1

@Mergifyio backport branch-3.0

@Mergifyio backport branch-2.5


chore: remove cds from devDependencies and update node matrix test versions

With node 14 it was necessary to keep cds in devDependencies as well as a peerDependencies since node 14 comes with npm 6 and npm<7 does not install peerDependencies. Now that node 14 has reached End-of-Life, it has been removed from the matrix tests and the entry from devDependencies can be removed. As node 20 is the current node version, it has been added to the matrix tests.
related: https://github.com/cap-js/graphql/commit/6fac2c0372faa888d0a1c2cbcd0eed51242fde7b https://github.com/cap-js/graphql/pull/88

test (14.x) Expected — Waiting for status to be reported

seems like this test needs to be removed from the expected/required tests in the repo settings (and 20 should be added)

it's now set to only require 16 and 18 as mandatory


Rework Bubble Sort C++

Bring on the criticism!

Do you need to update https://github.com/algorithm-archivists/algorithm-archive/blob/master/chapters/algorithms/bubble_sort/bubble_sort.md ?

I don't really have any criticism for your code, but I can tell you that we already have an open pull request about Bubble Sort in C++, which is #244. We can't possible merge both of them because they will certainly cause merge conflicts.
Because we use a "first come - first serve" approach, I'm going to have to close this issue. I'm sorry for that, @benchislett.
We still appreciate your contribution, though! I hope that you will stay around and find something else you can do for the Algorithm Archive. Just next time, make sure that there's not already a PR that does the same thing. ;)


I don't understand...

how in the world this is not the official hires fix in webui? I really wasn't expecting much when I stumbled in on this repo, but your hires fix actually had my jaw dropping in a couple cases.  Obviously this is all highly subjective, but after having now compared the official hires fix with yours in about 100ish different prompts, I'm more than prepared to declare you the unconditional victor.  I've yet to come across a single prompt where I thought the OG was better... at best, it managed to be about as good as yours.  On the other hand, there were more than a few prompts on which your version just straight up kicked the official version's ass; I'm talking stealing its lunch money and sending it home crying levels of beatdown in a few instances..   Damn fine work with this one good sir, well done!  But... uh... yeah, that's really all I had to say.
Hmm, I suppose I should probably mention an actual issue while I'm, ya know, in the issues section.  I think I just didn't realize where I was for a moment because there were no posts from people angrily criticizing all the personal failings of the repo maintainer (that's one benefit of a relatively obscure project like this one I suppose anyway).  Well I did notice that the upscaler dropdown doesn't seem to be functioning at the moment; although honestly that could very easily be something exclusive to users of vladmandic's automatic fork or even potentially something unique to myself and my own heavily customized version of said fork.  It also barely qualifies as an issue since you can just change it in the config json or, as I did, the default value listed in the hires_fix_pg.py file;  So in summary, nothing of value has been gained by you continuing to read this far, why haven't you clicked away yet? :P.  Alrighty then, I suppose with my business here thusly concluded and having exhausted my supply of  witty remarks, I shall take my leave of this place, good day drops the mic.

Hey friend, your words are real passionate rapping~ 🤣
For the performance you praise, hires.fix-pg might not promise too much, since it is really a plain improvement -- compared with the original one, even more slow. If any miracle happens, I owe them all to your nice model weights and parameter tuning.
For your problem, you mean your Upscaler dropdown is dead while Resize mode is ok? Then it might (?) be a naming conflict with original hires.fix widgets. But not certain, not sure, I'm still on auto1111's stream, not familiar vladmandic's feature. Even my another extension is complained to cause extras network button dead 🤔 I cannot tell if it is a gradio compatible error or some other thing -- everything goes well on my machine, I have no error trace to debug locally...
So, if manully modifying code works for the moment, just let it be (((((lol
PS: In fact, I did not get very satisfying results using this script months ago when I wrote it, later even about to forgot it. However if it really helps you in any sense, thank for your appreciation and support ;)


seed is not a required prop but generator fails if it is not provided

If you leave the seed property of a Side undefined, BracketGenerator fails on this line.
Since seed is not required, maybe you should check for falsy value instead of explicitly checking if it is null? I can open a PR for this if you don't mind.
Worked around this by setting seed to null in Side object.

@ikovic I did a PR today that converts the module to TypeScript, so if you're using it in a TypeScript project, you should get type errors if you provide incorrect types. I also saw a place where I was checking seed against null, and replaced it with checking if seed was truthy


Caja and configuration is currently not provided

I am manually configuring caja and the panels. Can't have that.

MATE panel is treated separately in issue #21.


feat: watch containers in launcher pod

need to make the launcher cli watch the container that gets spun up in the dind pod and die if it has any issues

basic implementation in #57


Does not work - produced paths for require are incorrect.

Please, observe the following TypeScript file:
import { Component } from "@angular/core";

@Component({
    selector: 'app-root',
    templateUrl: './app/app.component.html'
})
export class AppComponent {
}

And it works fine before I use angular2-template-loader. When I am trying to use the latter and run webpack it fails with the following message:
    polyfills.js     283 kB       1  [emitted]  polyfills
       vendor.js    3.32 MB       2  [emitted]  vendor
     main.js.map    17.2 kB       0  [emitted]  main
polyfills.js.map     353 kB       1  [emitted]  polyfills
   vendor.js.map    3.94 MB       2  [emitted]  vendor
      index.html  607 bytes          [emitted]
    + 912 hidden modules

ERROR in ./src/client/app/app.component.ts
Module not found: Error: Cannot resolve 'file' or 'directory' ./app/app.component.html in C:\Users\markk\IdeaProjects\QuestionarySample2\src\client\app
 @ ./src/client/app/app.component.ts 18:22-57

...
Child html-webpack-plugin for "index.html":
        + 1 hidden modules

C:\Users\markk\IdeaProjects\QuestionarySample2>

(there are more errors like that for other components, I replaced them with an ellipsis)
The loader converts the aforementioned source into:
import { Component } from "@angular/core";

@Component({
    selector: 'app-root',
    template: require('./app/app.component.html')
})
export class AppComponent {
}

And now it fails.
As I understand, the reason is that require works off the current directory, whereas the templateUrl is relative to the root. So, './app/app.component.html' is correct when taken relative to the root, but wrong when relative to the current location.
It is worth noting, that I do not use require anywhere in the source code, only the ES6 import statement, which is also relative to the current location. It is only the Angular2 templateUrl and styleUrls that are relative to the root.
Anyway, I must be doing something wrong, because nobody seems to have my problem. But what am I doing wrong?
The file name is src/client/app/app.component.ts. The source code directory structure is:
C:.
│   .gitignore
│   karma.conf.js
│   package.json
│   tsconfig.json
│   tslint.json
│   typings.json
│   webpack.config.js
│
├───config
│       karma-test-shim.js
│       karma.conf.js
│       webpack.common.js
│       webpack.dev.js
│       webpack.prod.js
│       webpack.scratch.js
│       webpack.test.js
│
└───src
    ├───client
    │   │   global.css
    │   │   index.html
    │   │   main.ts
    │   │   polyfills.ts
    │   │   tsconfig.json
    │   │   vendor.ts
    │   │
    │   └───app
    │       │   app.component.html
    │       │   app.component.ts
    │       │   app.module.ts
    │       │   app.routing.ts
    │       │   settings.component.ts
    │       │   signout.component.ts
    │       │
    │       ├───assets
    │       │       ...
    │       │
    │       ├───questionnaire
    │       │       ...
    │       │
    │       └───shared
    │               ...
    │
    └───server
            api.ts
            main.ts
            tsconfig.json

The webpack configuration is:
webpack.config.js
module.exports = require('./config/webpack.dev.js');
./config/webpack.dev.js
var webpackMerge = require('webpack-merge');
var ExtractTextPlugin = require('extract-text-webpack-plugin');
var commonConfig = require('./webpack.common.js');
const path = require('path');

module.exports = webpackMerge(commonConfig, {
    // devtool: 'cheap-module-eval-source-map',
    devtool: 'source-map',

    output: {
        publicPath: `http://localhost:${commonConfig.port}/`,
        filename: '[name].js',
        sourceMapFilename: '[name].js.map',
        chunkFilename: '[id].chunk.js'
    },

    plugins: [
        new ExtractTextPlugin('[name].css')
    ],

    devServer: {
        inline: true,
        hot: true,
        progress: true,
        port: commonConfig.port,
        proxy: {
            '/api*': {
                target: `http://localhost:${commonConfig.port - 1}`
            }
        },
        historyApiFallback: true,
        watchOptions: {
            aggregateTimeout: 300,
            poll: 1000
        }
    }
});

./config/webpack.common.js
var webpack = require('webpack');
var HtmlWebpackPlugin = require('html-webpack-plugin');
var ExtractTextPlugin = require('extract-text-webpack-plugin');
const path = require('path');

module.exports = {
    port: process.env.PORT || 3000,

    entry: {
        polyfills: './src/client/polyfills',
        vendor: './src/client/vendor',
        main: './src/client/main'
    },

    output: {
        path: path.join(__dirname, '../dist/client'),
    },

    resolve: {
        extensions: ['', '.js', '.ts']
    },

    module: {
        loaders: [
            {
                test: /\.ts$/,
                loaders: ['ts', 'angular2-template-loader']
            },
            {
                test: /\.html$/,
                // loader: 'html'
                loader: 'raw'
            },
            {
                test: /\.(png|jpe?g|gif|svg|woff|woff2|ttf|eot|ico)$/,
                loader: 'file?name=assets/[name].[hash].[ext]'
            },
            // {
            //     test: /\.css$/,
            //     exclude: path.join(__dirname, '../src/client/app'),
            //     loader: ExtractTextPlugin.extract('style', 'css?sourceMap')
            // },
            {
                test: /\.css$/,
                // exclude: path.join(__dirname, '../src/client/app'),
                loader: 'raw'
            }
        ]
    },

    plugins: [
        new webpack.optimize.CommonsChunkPlugin({
            name: ['main', 'vendor', 'polyfills']
        }),

        new HtmlWebpackPlugin({
            template: 'src/client/index.html'
        })
    ]
};

It's not angular2-template-loader which is complaining it's webpack. i have post an answer on your question on stackoverflow you can find explanation there.

The alternative you give me is as follows:

When using templateUrl and styleUrls in Angular2 use paths relative to the current directory. At this point Angular2 no longer able to find the html and css associated with the component. The code is broken.

Make sure to use this loader, otherwise the produced code will not run, because it is broken - see 1.

If this is my choice, then I will just use require myself and I do not need this loader.

@jorawarsingh is correct, your path can simply be expressed as './app.component.html'. If you'd like to use the flat require that is fine also.
I mean, the whole point of this loader is to not have angular try and make hundreds of requests to access your templates at runtime, so avoiding using their non-cannonical resolution strategy is a given.
Also you could create a custom resolver plugin to emulate this behavior instead when a request is being called for x.component.html, and alias it to be ./app/x.component.html.

I would also be more than happy to merge a PR that adds a loader option called useAngularResolution that will switch this behavior based upon the option. Would need to have tests and coverage included ofcourse.

Angular2 expects templateUrl: './app/app.component.ts'. This is how we write it in Angular 2. What you guys are telling me that I should be writing templateUrl: './app.component.ts'. This will only work if I use this loader later on. As is the component is broken.
I think it is wrong. This loader carries angular2 in its name. For me it means it should use "angular resolution" by default. I.e. rewrite templateUrl: './app/app.component.ts' into template: require('./app.component.ts').

No also, this is the relative path strategy for the angular AoT compiler as well. See https://github.com/angular/angular/issues/8953 for more information. Like I said, I'm more than happy to accept a PR for an added feature.
Candidly speaking maintaining webpack, working on the angular-cli is more of a priority right now, that edge cases. I hope you can understand.

I do understand. Thank you for your work and effort.

Can someone tell me how to resolve this?  I agree that i do not see why i should have to change all my templateUrls when using this loader should really do it for me?  What happens if later on down the line i do not want to use this loader, i will have to go all through my code and change the templateUrls

Has someone found a fix for this yet?

Anyone found a solution for this? spent days with no luck. Any input will be appreciated.


Time Warp in Stride

PR Details
This PR is here to add a slow motion / time warp effect to Stride.
Description

First is to add some public fields in GameTime :

Factor is the factor by which the time will be slowed down from 0 to 1.
WarpedTotal will represent the total game time accounting for slowed moments.
WarpedElapsed will represent the elapsed time times the factor.

I'm yet unsure of next steps but from what I understood, slowing down the actual game time will slow the UI and everything related to time. So far the only thing that I believe needs to be slowed down in games are game logic, physics, animation and effects.
I'm still wondering about use cases, should we make every processors use the warped time by default or should we let the user decide what entities is slowed down?
Related Issue

This PR is related to #749
Motivation and Context

Types of changes

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

Checklist

[x] My change requires a change to the documentation.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

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

The slow motion works for particles, animations and physics.
For particles and animation, the update time is multiplied by the time factor in the GameTime class. As for physics, the simulation resolution is multiplied by the same value.
Users can also use the WarpElapsed value in the GameTime class for logic.
I consider it finished but i'd be happy to receive any critics about it.

works fine for me now, thnx for the contribution, maybe tag xen2 to review it now ?

Thanks @salahchafai for reviewing!
And yes maybe @xen2 could review it as it's relatively simple?

LGTM, thanks again @ykafia !


Resume to support multiple networks

It is possible to run a multi network testnet with xcm command. We need to be able to resume such setup.

If db path are all different in config files, I think resume will work. I can test it to see if it works


xDSCWebService - $PhysicalPath default not a good one

The defaults for the physical path for the two new DSC pull server sites are:
$env:SystemDrive\inetpub\wwwroot\$EndpointName

which means these files are physically located under the document root of the default web site, that's a bad idea. These files should be separate from each other. I suggest changing the defaults to:
$env:SystemDrive\inetpub\$EndpointName

I'm happy to fix this. Do you agree with my suggestion?

Thanks! I'll let @rayhayes chime in

Closed by #30


Feedback fixes

Commits on this PR address missing solution details and exercise setup changes to no longer assume persisted state between exercises.

@kikiya Overall a huger improvement, I think!
Some inconsistencies spotted. The biggest one is that the pricing DB is still not created in exercises where it needs to be, because init_db does not run pricing_data.sql


updated the image to reflect changes

What changed?

one of the PNGs that shows the bash script in a deployment pipeline if I recall correctly. It didn't reflect the text (now the text has been updated)

This image will be removed in https://github.com/microsoft/MLOpsPython/pull/90


Add watch on HMC D-Bus property

PowerVMHandler should offload dumps only for Non HMC managed systems. Also system might change from non-hmc to HMC managed systems.
At present application is checking is system is HMC managed prior to every offload , it is a D-Bus call. Rather than that if we can watch on the property and cache the value it would be better.
isHMCManaged should be replaced with watch.

this issue is fixed


Select nested values based on the selection

Hello, I needed to make nested select, so that depending on the option the user chooses in the first select that is filled with a query to the database, the second select is filled with another query to the database. I don't know how to obtain the result of the selection of the first select and use it in a variable for the query of the second select, I have tried to do it by adding the id of the first select to the second query, without obtaining results. I haven't seen anything similar in the documentation, I wonder if you can tell me if you have this documented somewhere or an example. Thank you so much. All the best.

@abrahammarco7 we are preparing a blog post how to accomplish it. Please follow on the updates


Bid input, thousands seperator

Hi,
when possible add thousands seperator to bid input

makes it easier to enter value manually.

Hi,
Thanks for your input. I will look into this as soon as I can. I'm currently on vacation, which is why it probably won't happen for 2 weeks.
Greetings,
Fabian

Hi @Quotic,
I just want to let you know that I'm still working on the feature. I hope to be able to release it in the next week.
Fabian

Hi @Quotic ,
I just updated the preview version with a working thousand separators in the number field.
You can check it out here: https://kickbaseplus.fabian-fischer.com/#/transfermarket
It still has a small bug: if an offer is rejected by Kickbase's server, the value of the offer is set to 0 and you need to reload the TM. I will fix it asap.

Hi @fabfischer,
Nice, exactly what I expected. But found another bug. When you erase the complete value to enter a new one it switch back to the original one. I hope you understand what I mean.

@all-contributors please add @Quotic for ideas


Payment method Creditcards requires MollieComponent to be set to true in the react checkout but returns errors when it is false

Our situation:
Creditcards enabled
Mollie components for creditcards false
We dont want to use Mollie Components and the customer should only fill in creditcard details into Mollie
In our situation the following error has been fired:
Not all required components are mounted yet. Card holder, card number, expiry date, and verification code are required.
Please fix this, because this setup was working in the normal Luma checkout.

@Frank-Magmodules This issue is maybe quite important

Hi @erwinschaap , sure, will investigate this and get back to you.

Hi there, @erwinschaap! Thanks a lot for your patience regarding this issue.
I'm happy to inform you that we have successfully reproduced and fixed your issue within the latest release of the plugin. In addition to resolving the Credit Card component issue, we've also added support for some new payment methods.
I'm closing this issue for now, but please feel free to reopen it if necessary.
Thanks again for your patience!

I think there is something wrong with the code in the release (you can view the renderers.js in de main branch and the creditcardRenderer is not being used


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update podspec

It's not so a big problem though :sweat_smile:

Coverage remained the same at 70.43% when pulling 1e1748e47287b30da5454567f3b9cf33a8097757 on hironytic:other-than-swift into 4137d07f3f121e0c5d9a6650d20950892b137c0f on kishikawakatsumi:master.

Oh...I'm bad, mistaken copy & paste... Thanks!! :pray:


path_provider [2.1.5] Execution failed for task ':path_provider_android:compileDebugJavaWithJavac'.

Steps to reproduce
Flutter 3.24.4
Dart 3.5.4
DevTools 2.37.3
Gradle 8.3.0
JDK 21.0.5
android sdk 34
path_provider 2.1.5

When packaging Android applications with version 2.1.5 of [path_provider], an error occurred. Annotated [path_provider] in [pubspec.yaml] to package Android applications normally
I am sure I have performed the following operation:
Flutter clean
./gradlew clean
flutter pub get

Expected results
Flutter assets will be downloaded from https://storage.flutter-io.cn. Make sure you trust this source!
Launching lib\main.dart on ASUS I003DD in debug mode...
Flutter assets will be downloaded from https://storage.flutter-io.cn. Make sure you trust this source!

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':path_provider_android:compileDebugJavaWithJavac'.
> Could not resolve all files for configuration ':path_provider_android:androidJdkImage'.
   > Failed to transform core-for-system-modules.jar to match attributes {artifactType=_internal_android_jdk_image, org.gradle.libraryelements=jar, org.gradle.usage=java-runtime}.
      > Execution failed for JdkImageTransform: D:\Android\SDK\platforms\android-34\core-for-system-modules.jar.
         > Error while executing process D:\Android\Android Studio\jbr\bin\jlink.exe with arguments {--module-path C:\Users\Administrator\.gradle\caches\transforms-3\4a46fc89ed5f9adfe3afebf74eb8bfeb\transformed\output\temp\jmod --add-modules java.base --output C:\Users\Administrator\.gradle\caches\transforms-3\4a46fc89ed5f9adfe3afebf74eb8bfeb\transformed\output\jdkImage --disable-plugin system-modules}

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.

BUILD FAILED in 9s
Error: Gradle task assembleDebug failed with exit code 1

Actual results
Packaging failed
Code sample
https://github.com/ugpinout/storage_box
Screenshots or Video

Screenshots / Video demonstration
Uploading Err.mp4…

Logs
Packaging failed

Flutter Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.24.4, on Microsoft Windows)
[√] Windows Version (Installed version of Windows is version 10 or higher)
[√] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[√] Chrome - develop for the web
[√] Visual Studio - develop Windows apps (Visual Studio Community 2022 17.11.2)
[√] Android Studio (version 2024.2)
[√] Connected device (4 available)
[√] Network resources
• No issues found!
</details>

This has been fixed on the master channel and there's a solution you can use in your app in the meantime. See https://github.com/flutter/flutter/issues/156304#issuecomment-2397707812
Closing from here as this has already been fixed.
Thank you


Promotion of dimension coordinates when loading

The load pipeline of iris is inflexibly opinionated, and doesn't allow the user to easily control the final coordinates that will describe the dimensions of the cube. Rather iris uses hard-wired criteria to make these decisions, and doesn't allow the user to influence this decision making during the merge at the end of the loading pipeline.
At times, users want the ability to easily influence the coordinates that will describe a dimension once a cube is loaded, rather than having to change the coordinates that describe a dimension post-load.
For example, for NEMO/XIOS data iris does the following:
>>> cube = iris.load_cube(fname)
>>> print(cube)
EIV Ocean Mass X Transport / (kg/s) (time_counter: 1; depth: 75; -- : 332; -- : 362)
     Dimension coordinates:
          time_counter                           x         -        -         -
          depth                                  -         x        -         -
     Auxiliary coordinates:
          time                                   x         -        -         -
          latitude                               -         -        x         x
          longitude                              -         -        x         x
     Cell Measures:
          cell_area                              -         -        x         x
     Attributes:
          Conventions: CF-1.5
          TimeStamp: 23/12/2018 07:40:38 +0000
          description: ocean U grid variables
          file_name: nemo_be393o_1m_20151201-20160101_grid-U.nc
          ibegin: 0
          interval_operation: 2700 s
          interval_write: 1 month
          invalid_standard_name: bolus_ocean_mass_x_transport
          jbegin: 0
          name: be393o_1m_20151001_20151230
          ni: 362
          nj: 56
          online_operation: average
          production: An IPSL model
          timeStamp: 2018-Dec-23 05:43:41 UTC
          title: ocean U grid variables
     Cell methods:
          mean: time (2700 s)

Which is actually correct, given the NetCDF file and the CF Conventions.
Rather than forcing the user, for this example, to use iris.util.promote_aux_coord_to_dim_coord(cube, 'time') post-load to get what they want, I think that it would be preferable for the user to influence iris explicitly during the load pipeline e.g.
cube = iris.load_cube(fname, promote='time')

Where the promote keyword, allows the user to influence the choice of one or more coordinates picked by merge to describe a dimension.
Clearly, the promote keyword should also be supported to other relevant parts of the API e.g. iris.cube.CubeList.merge and iris.cube.CubeList.merge_cube et al.

Ping @jonseddon


[FEATURE]: Support Raw SQL in CTE Query Builder

Describe what you want
Summary
Developers should be able to define CTEs using the sql escape hatch.
Current State
CTE definitions use a query builder that can be of type TypedQueryBuilder<TSelection, unknown> or (qb: QueryBuilder) => TypedQueryBuilder<TSelection, unknown>). Developers need to implement a custom query builder if they use the first type option or are limited to selects with they use the second option.
Candidate API
Something like this would allow access to the underlying sql:
db.$with('my-cte)
    .as(sql<MyCustomType[]>`
        select * from sometable
    `)

Additional Context
I'm reaching for this because I have a CTE that makes use of a lateral join, which is not currently supported in the select API. I'm watching this MR, which appears to add this support: https://github.com/drizzle-team/drizzle-orm/pull/1079.

That would be great

This can be very helpful for introducing drizzle into existing codebases – put an existing query into a CTE and then combine it with drizzle queries. Right now you can more or less achieve this with subqueries, but CTEs would be more convenient.


Excluder interfaceimpl

Implementation of AddExcluder interface for remote/local enforcer.
This allows you to add ip's to be excluded.

Codecov Report

Merging #149 into master will increase coverage by -0.38%.

@@            Coverage Diff             @@
##           master     #149      +/-   ##
==========================================
- Coverage   57.27%   56.89%   -0.38%
==========================================
  Files          30       30
  Lines        3773     3791      +18
==========================================
- Hits         2161     2157       -4
- Misses       1467     1492      +25
+ Partials      145      142       -3

Impacted Files
Coverage Δ

supervisor/ipsetctrl/ipsetctrl.go
66.05% <ø> (-2.52%)
:x:

supervisor/supervisormock.go
0% <ø> (ø)
:white_check_mark:

supervisor/iptablesctrl/acls.go
86.56% <100%> (+0.03%)
:white_check_mark:

supervisor/iptablesctrl/iptables.go
60.66% <100%> (ø)
:white_check_mark:

supervisor/supervisor.go
79.78% <20%> (-0.65%)
:x:

trireme.go
50% <33.33%> (-0.64%)
:x:

monitor/linuxmonitor/linuxMonitor.go
61% <ø> (-7%)
:x:

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 89cc304...fa10eb6. Read the comment docs.


ttf corruption when requiring emoji

Just after updating to last ruby 2.4 (brew), my projects using emoji are drawing the normal .ttf fonts numbers as circled emoji numbers.  Total disaster.  The only solution is banning emoji and rewrite it all

We're facing the same issue using prawn 2.1.0 with Ruby 2.3 compiled from source on macOS 10.12.3 as well as Ubuntu 16.04.

OK, I'll confirm it.

same here ;(

I have released 2.0.1. Thank you everyone.
https://github.com/hidakatsuya/prawn-emoji/releases/tag/2.0.1

Great job!
Thanks @hidakatsuya

Thanks, working nice!

El 21 may 2017, a las 12:35, Erdem Gezer<EMAIL_ADDRESS>escribió:
Great job!
Thanks @hidakatsuya https://github.com/hidakatsuya
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/hidakatsuya/prawn-emoji/issues/17#issuecomment-302928440, or mute the thread https://github.com/notifications/unsubscribe-auth/AA2qbB4mvVB5uw09DaZgNhvU6rRGgLoGks5r8BOOgaJpZM4Lw59x.


Update all_pattern_test.rb

remove duplicate test names

Good catch, thanks!
The error needs to be fixed in the generator: https://github.com/turingschool/enums-exercises/blob/master/lib/generator/all_problem.rb#L27 - and then the problem needs to be regenerated. Want to give it a whirl?

Good catch, thanks!
The error needs to be fixed in the generator: https://github.com/turingschool/enums-exercises/blob/master/lib/generator/all_problem.rb#L27 - and then the problem needs to be regenerated. Want to give it a whirl?

Yes
On Thursday, January 1, 2015, Katrina Owen<EMAIL_ADDRESS>wrote:

Good catch, thanks!
The error needs to be fixed in the generator:
https://github.com/turingschool/enums-exercises/blob/master/lib/generator/all_problem.rb#L27

and then the problem needs to be regenerated. Want to give it a whirl?

—
Reply to this email directly or view it on GitHub
https://github.com/turingschool/enums-exercises/pull/26#issuecomment-68482445
.

Yes
On Thursday, January 1, 2015, Katrina Owen<EMAIL_ADDRESS>wrote:

Good catch, thanks!
The error needs to be fixed in the generator:
https://github.com/turingschool/enums-exercises/blob/master/lib/generator/all_problem.rb#L27

and then the problem needs to be regenerated. Want to give it a whirl?

—
Reply to this email directly or view it on GitHub
https://github.com/turingschool/enums-exercises/pull/26#issuecomment-68482445
.

Hey Katrina,
Would you like to leave the enums-exercise repository as it is, so that
us students can see how we would go about changing the generator file and
regenerating the problems , or would you prefer I fix it as the readme
instructs and submit a pull request?
Sorry for the questions - I'm still pretty new to this. I hope you're
having a great new year!
Markus
On Thu, Jan 1, 2015 at 1:28 AM, Markus Olsen<EMAIL_ADDRESS>wrote:

Yes
On Thursday, January 1, 2015, Katrina Owen<EMAIL_ADDRESS>wrote:

Good catch, thanks!
The error needs to be fixed in the generator:
https://github.com/turingschool/enums-exercises/blob/master/lib/generator/all_problem.rb#L27

and then the problem needs to be regenerated. Want to give it a whirl?

—
Reply to this email directly or view it on GitHub
https://github.com/turingschool/enums-exercises/pull/26#issuecomment-68482445
.

Hey Katrina,
Would you like to leave the enums-exercise repository as it is, so that
us students can see how we would go about changing the generator file and
regenerating the problems , or would you prefer I fix it as the readme
instructs and submit a pull request?
Sorry for the questions - I'm still pretty new to this. I hope you're
having a great new year!
Markus
On Thu, Jan 1, 2015 at 1:28 AM, Markus Olsen<EMAIL_ADDRESS>wrote:

Yes
On Thursday, January 1, 2015, Katrina Owen<EMAIL_ADDRESS>wrote:

Good catch, thanks!
The error needs to be fixed in the generator:
https://github.com/turingschool/enums-exercises/blob/master/lib/generator/all_problem.rb#L27

and then the problem needs to be regenerated. Want to give it a whirl?

—
Reply to this email directly or view it on GitHub
https://github.com/turingschool/enums-exercises/pull/26#issuecomment-68482445
.

I think it would be best to fix the generator and regenerate the exercises, so that they're exactly what people need.
An additional pull request to tweak the README would also be great, if you have any ideas there.
Thanks :)


example with functionalities

Hi! Awesome project, I read the paper and really want to try this idea! @vinid @patrickjohncyh
I am trying to run the basic example provided in the readme and I get this error.
Do you have a notebook showing all basic functionalities or something like that?
Thank you!
Input In [24], in <cell line: 2>()
1 #get_last_embeddings_for_sessions
----> 2 results = pb.run_next_item_predictions(next_element_prediction)
File ~/Desktop/Labs/notebooks/prodb/prodb/prodb.py:312, in ProdB.run_next_item_predictions(self, sessions, subword_prefix)
310     joined = " ".join(splitted)
311     gt.append(to_predict)
--> 312     predictions.append(self.predict_from_tokens(joined))
313     pbar.update(1)
314 pbar.close()
File ~/Desktop/Labs/notebooks/prodb/prodb/prodb.py:332, in ProdB.predict_from_tokens(self, string_ids)
330 for i in range(len(top_indices)):
331     p = top_indices[i]
--> 332     answers.append(self.convert_ids_to_tokens(p))
334 return answers
File ~/Desktop/Labs/notebooks/prodb/prodb/prodb.py:230, in ProdB.convert_ids_to_tokens(self, id)
229 def convert_ids_to_tokens(self, id):
--> 230     return self.id2token[id]
KeyError: 1497

Ah yes, the example is a bad example (my fault).
Here a colab that works: https://colab.research.google.com/drive/1YBF8b7zM2sRkQy1ZPiM3TXF35WaRTbTh?usp=sharing
More Details
You might get the error because you  have more vocabulary items than actual items in the training set:
Suppose you have
VOCAB_SIZE = 20000

and only 5 distinct items in the training set ("item1 item2....").
when we get the top-10 best predictions for "item1 item2 [MASK]", the predictions will be a mix between your items and uninitialized vocab elements (20000 elements - 5 of your vocab). When the model access those uninitialized vocab positions, it breaks.
Note that the code comes from https://keras.io/examples/nlp/masked_language_modeling/ if you want to get the "original" version


aur-srcver: Handle errors with running parallel

Simple way to fix #380: print a message and exit if parallel exit code is >101.
Also adds a special check if parallel is not available, because it is a required tool and we want to be as clear about this as possible.
❯ lib/aur-srcver ~/.cache/aurutils/sync/*-git
srcver: "parallel" is not found in $PATH

:+1:

In hindsight, what was the reasoning for https://github.com/AladW/aurutils/pull/381/commits/532699d4f9e6d918cd61c6cca53a5f38bd330951? If a job was successful, you might as well print the new version, and if parallel itself fails, we have already bailed.

Half of the jobs could fail, and previously we printed lots of errors, and then full list of versions, half of which were up-to-date and another half is obsolete. So I thought, maybe let's print versions only if there are no failed jobs, to have a consistent output... Now if versions are printed, you can be sure that these are truly the latest versions.
We could have also made the script to print versions of only successful jobs and skip failed jobs, but I'm not sure if we need that complexity at all - we would likely want people to solve their issues with srcver first anyway, right?

We could have also made the script to print versions of only successful jobs and skip failed jobs, but I'm not sure if we need that complexity at all - we would likely want people to solve their issues with srcver first anyway, right?

Yeah, you're probably right. Even it this were desired, I don't see a straighforward way to get the job arguments from parallel


Chat Style

Hiii !!!
Thanks for your amazing work...
well...actually im goin crazy cause i'm tring to make a page in chat style and my only problem actually is just one and i'm hitting my head over the table last 5 hours...i feel stupid....
The only thing i need is to understand how to make the msgbox (where user write his msg) be the 80% of the page width and the 20% being occupied by the button for send the message.
Ofc,...when i end i send here the code so, if you want @godesign , you can implement in next release or in the demo

nevermind ! Solved by myself...coffe and hit head worked!

                <textarea cols="40" rows="8" name="msgbox" id="msgbox" maxlength="250" placeholder="Scrivi qui il tuo messaggio"></textarea>

@pazDontExist thanks for the input. I'll check what I can do :+1:  Such things are always welcome.


Proper parsing of elements and attribute dicts

Pulls in older work by @bcoughlan and @a1s, adds support for boolean attributes and Python 3

Agree re code structure. Is that something you want to tackle?
We should also keep an eye on performance. From just playing with the tests I noticed a very minimal slow down with these changes, but worth it for proper parsing.

Agree re code structure. Is that something you want to tackle?

That would be fun but looking at my too-busy life I'm not sure that this will be reasonable for me, so feel free to do it (it's very possible that I'll end up doing it anyway).

We should also keep an eye on performance. From just playing with the tests I noticed a very minimal slow down with these changes, but worth it for proper parsing.

Do you have experience in including that into CI/tests? That would allow us to avoid loosing sigh of this.

Not sure about performance tests in CI, but I'm gonna look at making it easier to run repeated timed tests on the set of hamlpy/html files

@Psycojoker I've merged and am now gonna have a look at improving the tests. Can you get your PEP changes into a PR or just push them?

@rowanseymour done.
Do you think we are ready for a release? You weren't as confident as for the previous PR iirc

@Psycojoker I'd like to finish working on the tests first - see if that brings up any issues


State name conflict

Can we change the name of the vendor "state" to "status"? State is a bit confusing for us since are adding address, city, state, zipcode, etc as some extra fields to the vendor. Status seems like a more descriptive word and less likely to conflict with anyone's additional fields.

'State' made sense to me because it was in line with other fields from Spree (e.g. order or shipment have a state for a similar purpose). I think Vendor can be associated with Address model, so there would be no need to add another 'state' field directly to the Vendor model. Anyway, it may be confusing, so I'll keep your remark in mind when adding extra fields.


Some words return no meaning

I was testing out this program and found that some words don't return any meaning. It turns out that some pages on merriam-webster.com place the definition of the word inside
of
 tags, where other pages store the definition inside of  tags. I haven't run into any other places that the definition is stored, but just thought I'd let you know about this issue!
 Don't ask me why I was searching those lol.

@jkazuop : Thanks. I will look into this and fix it out soon.

I have fixed the issue. You can upgrade the package by running
pip install --upgrade greb

Issue is resolved as of 0.0.3 release.

@jkazuop : version 0.0.4 also lists suggestion in case the word is not spelled correctly. Try upgrading it once and let me know if it breaks in any case.

@staranjeet : I like the new feature! Sure, I'll let you know.


Fix Birthday lookup when there’s no birthday

When there is no birthday it doesn’t show the potion to open that person in People

Done. It now will offer to search for the person in People if it doesn't find any birthday information.


add wakatime-oauth

Hello,
I have developed an integration for the Wakatime API's OAuth provider for PocketBase, as I could not find any existing helpers for this purpose. My implementation is largely based on the Notion integration.
I have followed all the recommendations outlined on the contributions page, including building the frontend, adding tests, and running the linter. My implementation did not flag any new issues.
I have also tested the integration on a local build, and it appears to be functioning correctly. I would appreciate any feedback you may have.
Thank you.

added the requested changes

I've tested the provider and squash merged the changes locally with some minor adjustments. It will be available with the next v0.23.0 release (there are no ETAs yet).


Can't interact with points when using showArea

What I want to achieve
I want a line graph with showArea in which I can interact with the points. By interact I mean have tooltips on hover and actions on click.
Problem
As far as I can tell due to the drawing order of the graph components, the points end up under polygons that represent the "area" portion of the lines. This means I can't have pointer events on them.
I don't have that much experience with SVG but as far as I understand z-index is represented by drawing order and can't be manipulated any other way.
Potential Solutions

It would be cool if there would be an option that would make all points of the graph be drawn last so that you can interact with them.
Or maybe there could be a plugin that queues up the points instead of drawing them and then draws them at the end of the drawing cycle --- tho I'm not sure it's possible.

Disclaimer: I might be totally off bat and I'm looking for some validation on my thought process. I haven't fully investigated this but I thought it would be cool if somebody with a better understanding could point me in the right direction and I would be more than happy to work on a PR if you think this makes sense.

Hi there. Nice disclaimer :-)
For a quick solution you could use the CSS style:
.ct-area {
  pointer-events: none;
}

This will make your areas irrelevant for mouse interaction and therefore pass on to the points below.

Well, don't I feel silly now 👍 I dunno why in my head that wouldn't have worked with SVG elements, but I didn't even look it up. Thanks a lot!


'display float with precision' block

Basically the same as the roundwithprecision block, but make it always output a string & fill out with 0's to the given number of precisions.
Also might want to allow negative precision for > 0 e.g. -1 would be round w/out ones place
also maybe a 'display time' block for ms -> hrs:mins:secs

added & fixed


Renovator not activating moved pages

Required Information

[ ] AEM Version, including Service Packs, Cumulative Fix Packs, etc: 6.5.0
[ ] ACS AEM Commons Version: 4.8.4
[ ] Reproducible on Latest? yes

Expected Behavior
When I move content using the renovator I expect the moved content to be activated/published.
Actual Behavior
Content is not activated
Steps to Reproduce
Add a test to see if the asset is activated. For example, add a test to the testMoveManyAssets() method.
assertTrue("Should publish new asset", queue.getActivateOperations().containsKey("/content/dam/folderC/subfolder/asset1-renamed"));
Links

It was really designed to just republish pages if they were referring to assets which were moved.  Moving pages and republishing has other implications such as caching concerns and what not -- gets a little messy.
As an alternative you can take the report and filter the list of pages; then use Curly to republish those pages.  It's an extra step but still better than the alternative (or rather, the lack thereof).  I'm happy to leave this issue open in case someone has time to take up this issue but I do not at the moment, would require more time than I have available, sadly.


⚠ GitHub has degraded performance

In b0781f8, GitHub (https://www.githubstatus.com/api/v2/status.json) experienced degraded performance:

HTTP code: 200
Response time: 310 ms

Resolved: GitHub performance has improved in c96a95f.


Congratulations! Could you please share the complete project? Thanks.

Thank you for sharing the code.
Could you please share the complete project? Thanks.

When can you release your training code?


Update documentation

Documentation should contain:

stability description
general description of the package
ways of how to install the package
common issues during installation and usage
optional stuff like credits, license, etc

Done


dropWhile(), takeWhile() exercise checks for the wrong value

The Exercise describes the task using "END" but the test actually checks for "STOP"

Thank you for reporting this issue! I have submitted the new course version for review to the marketplace.

Glad to help.


Required ruby version is incorrect

The required ruby version of sorbet-runtime is listed as >= 2.3.0.
However, the gem uses endless ranges, which is a Ruby 2.6 feature, breaking on earlier ruby releases.
Could I also humbly request that the test suite be updated to run on the latest patch of each supported minor ruby release (e.g. 2.6, 2.7)? Thanks!

We document what versions of Ruby Sorbet supports here:
https://sorbet.org/docs/faq#what-platforms-does-sorbet-support
If you feel particularly strongly that we should capture that in the gemspec I can, but I tend to think that version ranges are brittle, because the true test is whether it works, not whether the versions match.

Could I also humbly request that the test suite be updated to run on the latest patch of each supported minor ruby release (e.g. 2.6, 2.7)? Thanks!

The sorbet-runtime test suite already runs against both ruby 2.6 and ruby 2.7.

Thanks for the quick reply! The version range is critical, so external developers know if they're on a supported path (and internal ones know which ruby features they can use).
It doesn't have to be required_ruby_version though, but please remove the entry if it won't be maintained (it's an optional part of a gemspec).

The version range is critical

I agree with this. Honestly, I personally can't think of a reason why not to have the required_ruby_version reflect the versions these gems are tested against. To me, required_ruby_version is a commitment saying

this gem works with the stated Ruby versions, and if it doesn't then a bug exists

As I mentioned in https://github.com/sorbet/sorbet/pull/4281#issuecomment-870939262, I think it is entirely Stripe's prerogative which Ruby versions are supported, but I think setting required_ruby_version to a version less than those that the gem is tested against is not an ideal choice as it can lead to the scenario discussed here: a breaking change was made for Ruby < 2.6 (the use of an endless change), but it was not caught by automated tests.
As for the alternative of removing required_ruby_version entirely, I don't think that would be a step in the right direction, as it conveys useful information to application developers and library authors, and removing it seems like a workaround to get away from a formally validated commitment to supported versions.

the true test is whether it works, not whether the versions match.

While I agree with this in theory (it is indeed the true test), I think there is value in having library authors explicitly exclude unsupported versions (which may incidentally work, but are not covered by tests and may break without warning at any time, as is the case for Ruby < 2.6 for Sorbet), because it saves everyone time to handle incompatibilities up front.


Draft up initial Medium article

@SFSandra hey thanks for being attentive to this. This project is evolving quite organically and I'm working on cementing the fundamental ideas with Venezuelans inside and outside of the country. We're considering ideas such as a series of articles (not just one) and/or having a sort of manifesto (basically foundational ideas). This issue's title may be a bit outdated, will update. All of this is initially being discussed in Spanish but will translate and share more as soon as I can.

Moving to appropriate communication channel


[HOLD for Payment 2024-09-06][$250] mWeb - Video - In welcome video, all playback speed options is not shown in normal mode

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.18
Reproducible in staging?: Y
Reproducible in production?: Y
Issue reported by: Applause Internal Team
Action Performed:

Go to https://staging.new.expensify.com/home
Login as a Gmail account
In the Welcome Expensify video, tap 3 dots
Select playback speed
Note the number of playback speed options
Go to full screen mode
Tap 3 dots - playback speed
Note the number of playback speed options

Expected Result:
In the welcome video, all playback speed options shown is full screen mode must be shown in normal mode.
Actual Result:
In the welcome video, all playback speed options shown is full screen mode is not shown in normal mode.
Workaround:
Unknown
Platforms:

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

Screenshots/Videos
https://github.com/user-attachments/assets/7b786d01-cf13-4576-b4f9-d480de7d4569

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~014d75aeb575f9f1ea
Upwork Job ID:<PHONE_NUMBER>470479721
Last Price Increase: 2024-08-13
Automatic offers:

ikevin127 | Reviewer | 103548572
neonbhai | Contributor | 103548574

Issue OwnerCurrent Issue Owner: @ikevin127

We think that this bug might be related to #vip-vsb

@slafortune  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

Adding BZ again - I'll be out until 8/21

Awaiting proposal review by @ikevin127

♻ Reviewing proposals today.

@daledah Thank you for the proposal. While I appreciate the more detailed proposal, unfortunately it came after the first one which I think was detailed enough since this issue has a simple root cause / solution.
ℹ Keep in mind the contributor guidelines (6.) which state:

Note: Before submitting a proposal on an issue, be sure to read any other existing proposals. ALL NEW PROPOSALS MUST BE DIFFERENT FROM EXISTING PROPOSALS. The difference should be important, meaningful or considerable.

Otherwise you could get a ⚠ warning, which after 2 (same month) or 3 (per year) you risk being removed from the contributor program.

@neonbhai's proposal looks good to me even though it's not extremely detailed, since this issue has a simple root cause / solution. The root cause was pointed out correctly and the proposed solution fixes the issue, even though it does not mention all the details, it mentions enough to be acceptable.
Notes for PR (if assigned):

Make sure to adjust the types as well based on the new added values.
Make sure to adjust the initial state variable currentPlaybackSpeed to match the Normal speed, given the new values.
To fully fulfil the Expected result, please have the value 1 show the label Normal in order to match the native player.
Note: The label Normal should be translated (en/es) and placed in translations at videoPlayer.playbackSpeedNormal (or similar).

🎀👀🎀 C+ reviewed

@daledah Don't worry - you will not get a warning in this case, I was just mentioning to be mindful of that contributor guideline in the future as it might lead to warnings.
Of course it's subjective, there are cases in which a more detailed RCA and solution are required - I don't consider this one to be that case.

Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑💻

Currently awaiting for @neonbhai to give a timeline on the PR.

⚠ We just got confirmation on Slack that the Deploy Checklist: New Expensify 2024-08-26 which includes the PR of this issue was only deployed to production today in Deploy Checklist: New Expensify 2024-08-28. More context on why this happened can be found in this Slack thread and this Slack comment.
Given the context above, this issue should be on [HOLD for Payment 2024-09-6] according to today’s production deploy from Deploy Checklist: New Expensify 2024-08-28.
cc @slafortune

⚠ We just got confirmation on Slack that the Deploy Checklist: New Expensify 2024-08-26 which includes the PR of this issue was only deployed to production today in Deploy Checklist: New Expensify 2024-08-28. More context on why this happened can be found in this Slack thread and this Slack comment.
Given the context above, this issue should be on [HOLD for Payment 2024-09-06] according to 4 days' ago production deploy from Deploy Checklist: New Expensify 2024-08-28.
cc @slafortune @techievivek

@ikevin127 Thanks! - Can you  please complete the checklist -
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[ ]  [@ikevin127   ] The PR that introduced the bug has been identified. Link to the PR:
[ ]  [@ikevin127   ] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
[ ]  [@ikevin127   ] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
[ ]  [@ikevin127   ] Determine if we should create a regression test for this bug.
[ ]  [@ikevin127   ] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
[ ]  [@slafortune ] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

[x]  [@ikevin127] The PR that introduced the bug has been identified. Link to the PR: https://github.com/Expensify/App/pull/30829
[x]  [@ikevin127] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: https://github.com/Expensify/App/pull/30829/files#r1744646106
[x]  [@ikevin127] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: N/A.
[x]  [@ikevin127] Determine if we should create a regression test for this bug.
[x]  [@ikevin127] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.

Regression Test Proposal

Open Expensify app and login.
Open a chat and send a video attachment.
Click on Expand (to make video fullscreen).
Click on three dots -> Playback speed.
Verify that the 1x speed is labeled Normal.
Verify that all playback speed options (0.25, 0.5, 0.75, Normal, 1.25, 1.5, 1.75, 2) can be observed.

Do we agree 👍 or 👎.

Regression Test - https://github.com/Expensify/Expensify/issues/426444
@ikevin127 @neonbhai Paid ✅ ✅


add a displayName string for each anchor

Can we add these to the directory?
My use case is the operations lists in steexp. It's nice to show a short name instead of the addresses.

I prefer just displaying the domain names because it keeps things simpler and doesn't abstract away too much of StellarTerm. StellarTerm is designed for people who have used other cryptocurrencies before and I want to emphasize the fact that the anchors are tied to domain names.

But the directory will be shared / imported into different apps in the ecosystem and I suspect some of these may find these display names useful too.

Hm okay i'll keep thinking about this.


For the CLI, is there a way to change the build export path?

There a way to change the path of where the slide deck is being exported to?

I didn't find anything in the docs about this.  As a workaround, this worked for my needs:
"scripts": {
    // ...
    "build": "rimraf docs && mdx-deck build slides.mdx && mv public docs"
  },

It looks like the CLI option to customize the build output directory was removed in v3:
https://github.com/jxnblk/mdx-deck/blob/master/MIGRATION.md


which lidars are supported?

e.g. for orin devkit
which lidars are supported by the package?
Thanks

Any lidar that has a ROS driver that publishes flat laser scans to a topic of type LaserScan.msg is supported. You can look at the .msg file for specifications on the input.
We have provided a node that converts from LaserScan.msg to FlatScan.msg. Example launch file here.
Also any lidar that produces a 3D point cloud of type PointCloud2.msg is supported since we provide a cuda accelerated PointCloud2.msg to FlatScan.msg converter node here.

This function has been used with the SICK Microscan 3 flat laser scan, and 3D LIDAR's Hesai XT32 and Velodyne VLP16.


Dependencies
NA
Testing
Try to type in the navigator and assert it does not cutoff letters
Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

[ ] ~Added tests~ - css only
[ ] Ran npm test, and it succeeded
[ ] Updated documentation if necessary

@swift-ci test


[AMBARI-23811] TimelineMetricsFilterTest fails if dir name contains @

What changes were proposed in this pull request?
Same as #2031, for branch-2.7.
How was this patch tested?
$ mv ambari Ambari-Github-PullRequest-Builder@2
$ cd Ambari-Github-PullRequest-Builder@2
$ mvn -am -pl ambari-metrics/ambari-metrics-timelineservice clean test
...
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.447 sec - in org.apache.ambari.metrics.core.timeline.TimelineMetricsFilterTest
...
[INFO] BUILD SUCCESS

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/3550/
Test PASSed.


Feature/asciimath

I've updated the contents of the asciimath page to include the symbols added in Asciimath as of https://github.com/asciidoctor/asciimath/issues/14 ; that means that the only features on asciimath.org not supported in asciimath are the cancel and color operators. The latest additions are not released yet, but they will be soon.

Asciimath upgraded.


Pkg compat

support for .packages file.

I have signed the CLA

k, tnx.

Yes I am okay with the commit I made being contributed to the project

All this just for a single line change :-)

eh, the good news is that you have to do this only once for any google project. But the first time is cumbersome.

True, but I can't help but see the funny side

Um, I assume I've done what I need to do?

Actually I don't know! I figure some google guy should approve your contribution ?

Lets hope that's all that's needed.

@jakemac53 made some minor fixes. Do you know also how to clear the CLA issue ? I think @terrasea has already signed it.


prioritize using istio-ca-secret even if USE_CACERTS_FOR_SELF_SIGNED_…

Please provide a description of this PR:

@Xieql: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
d697c3b41d02f47d0a5b86c6e6d07e28d7cb47aa
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@hzxuzhonghu that plan sounds really similar to the design doc that @jaellio circulated around the community. I'm sure she'd appreciate prompt reviews and support in implementing her design!

/cherry-pick release-1.20

@hzxuzhonghu: new pull request created: #47769

In response to this:

/cherry-pick release-1.20

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@hzxuzhonghu @costinm @Xieql To the best of my knowledge this PR is the same as #47654. We were still having an ongoing discussion on that PR on whether this change should be included in v1.20 and why I had removed similar logic that I had already implemented in a previous PR when adding the feature flag. I was at KubeCon this past week and did not have time to review this PR. I would appreciate in the future if we could reach consensus on an issue before an identical PR is opened and merged.
I have documented my plan for adding this feature flag in multiple issues and I would have appreciated that if there were concerns surrounding the feature flag, those conversations could have continued on those issues.

And in 1.21, we can turn on the flag, and copy istio-ca-secret to cacerts if exist. In a future release maybe 1.24, we can completely remove istio-ca-secret secret support.

I have documented the plan for the cacert merging work in multiple locations and I have documented and had an open conversation surrounding the feature flag addition.


service and systemd_unit resources attempt to mask an already-masked service

Description
chef-client attempts to mask a service that is already masked, using both a service and systemd_unit resource.
Only seems to impact CentOS 7 systems, do not have the same issue on CentOS 8.
This issue does not occur on chef-client version 16.16.13, but seems to start in version 17.1.35.
Chef Version
17.7.29
Platform Version
CentOS Linux release 7.4.1708 (Core)
Replication Case
Using the firewalld service as an example:

Stop, disable, and mask the firewalld service using sudo systemctl stop firewalld, sudo systemctl disable firewalld and sudo systemctl mask firewalld
Confirm that the service is masked using systemctl status firewalld, the output should look like:

[username@server ~]$ systemctl status firewalld
● firewalld.service
   Loaded: masked (/dev/null; bad)
   Active: inactive (dead)

create a new test.rb recipe with the following content:

service 'firewalld' do
  action :mask
end

OR
systemd_unit 'firewalld' do
  action :mask
end

Run this file using sudo chef-client -z -W test.rb
The output of this dry-run should indicate that it "would mask" the firewalld service

Client Output
  * service[firewalld] action mask
    * Service status not available. Assuming a prior action would have installed the service.
    * Assuming status of not running.
    - Would mask service service[firewalld]

  * systemd_unit[firewalld.service] action mask
    - Would masking unit: firewalld.service

The debug output:
 * systemd_unit[firewalld.service] action mask[2021-11-03T16:49:36-04:00] INFO: Processing systemd_unit[firewalld.service] action mask (redacted::redacted line 19)

    - Would masking unit: firewalld.service

  * service[firewalld] action mask[2021-11-03T16:49:37-04:00] INFO: Processing service[firewalld] action mask (redacted::redacted line 15)

    * Service status not available. Assuming a prior action would have installed the service.
    * Assuming status of not running.
    - Would mask service service[firewalld]

This problem still exists in Chef 17.9.42 and RHEL7

This is still a problem on Ubuntu 20.04.  chef-client will attempt to mask the service during every client run.  For example:

systemd_unit[systemd-journald-audit.socket] action mask
- masking unit: systemd-journald-audit.socket

The issue appears to be with how systemctl reports the unit status.
A masked service shows the unit file status as "bad", not "masked".

root@A3520A-VM:/etc/systemd/system# /bin/systemctl --system show  -p UnitFileState -p ActiveState systemd-journald-audit.socket
ActiveState=inactive
UnitFileState=bad


Workflow change

Changed the workflow file to support building and building on linux platform. Also corrected a minor typo in the readme file

Thanks for the contribution


Revert "Handle IPFS Stalling W/ Timeouts & Fallback Providers"

Reverts Web3-API/monorepo#294

Whoops, meant to merge this into prealpha-dev


After droping, database name still present in selection list

my environment running ArangoDB
I'm using the latest ArangoDB of the respective release series:

[x] 3.1

On this operating system:

[ ] Linux

[x] RedHat .rpm

Foxx
this is a web interface-related issue:
I'm using the web interface with this browser: Google Chrome    running on this OS: Windows 7 x64

[x] authentication is enabled?
[ ] using the cluster?
[x] _system database?

These are the steps to reproduce:

open the browser on http://server.db:8529
log in as root
create user test
create datadase data with owner test
relogin as test and selest data database
relogin as root
delete data database
relogin as test

After these steps data database still present in list of all databases for selection:

And deleted database still present in permission tab of user profile:

Thanks for spotting. Closing this issue because it is a duplicate of #2047 and #2303. Latest bugfix date will be 3.2 release.


Audit logs in JSON format

The modsecurity documentation says I should be able to get audit logs in JSON format with SecAuditLogFormat json.
Is this supposed to work with proxy-wasm? I still get logs in the native format when this option is set. Also, How do I get the logs to print the request headers and bodies? I have SecAuditLogParts ABIJDEFHZ but it seems to emit very limited logs like the following:
[2024-02-16 03:59:46.363][29][warning][wasm] [source/extensions/common/wasm/context.cc:1151] wasm log coraza-waf-filter coraza-waf coraza-filter-vm-id: [client "<IP_ADDRESS>"] Coraza: Warning. Host header is a numeric IP address [file<EMAIL_ADDRESS>[line "2203"] [id "920350"] [rev ""] [msg "Host header is a numeric IP address"] [data "<IP_ADDRESS>:5102"] [severity "warning"] [ver "OWASP_CRS/4.0.0-rc2"] [maturity "0"] [accuracy "0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-protocol"] [tag "paranoia-level/1"] [tag "OWASP_CRS"] [tag "capec/1000/210/272"] [tag "PCI/6.5.10"] [hostname "<IP_ADDRESS>"] [uri "/hello"] [unique_id "aRgeEOhlzYsdFohxxpc"]

Just checking if there's anything super obvious I am missing. If it's supposed to work, I can dig deeper.

Initially we had issues with JSON and I think disabled JSON audit logging here but TinyGo and our own JSON infrastructure has improved a lot so we can probably look into enabling it.
Though either way with the native formatter and that configuration, I think full logs are supposed to be printed so we should doublecheck what could be going wrong.

Oh yeah now I remember, currently audit logs are disabled
https://github.com/corazawaf/coraza/blob/main/internal/auditlog/init_tinygo.go
I think we were hoping for https://github.com/proxy-wasm/spec/pull/38 to land someday but I guess it won't. In the meantime, we should probably implement audit logging anyways printing to the normal envoy logs as a start.


Formatting

Auto format using pycodestyle

Looks like there's a conflict in the tests. You should be able to do a pull from stable and do formatting on the missing function, and do another commit here to fix it. Thanks for your work on this @martin-marty !

Thanks for your work on this @martin-marty .


Fix for IE11 (ES5) compatibility

This fix is to cover the PR feedback given by @StephenAWalsh on my previous PR (#291).
It was as simple as running the JS through babel's babel-loader rather than having it use whatever it does by default (I honestly never delved into it)
It should be ES5 compatible now, I ran it through es-check:
$ es-check es5 ./dist/fuse.js
ES-Check: there were no ES version matching errors!  �

(and manually confirmed the arrow functions are gone)

I also updated the Jest dependencies in ebfdc6d since they were showing as having updates available and might as well stay updated I'd say.

Should be addressed by #295 already

Thank you!!


Action fails if directory in target branch does not exist

When the directory where the built documentation should be place does not exist in the target branch, the action creates it as it should, but then tries to run git rm -r . which, in turn, triggers an error, failing the step in a workflow.
To reproduce the issue just pass a directory: name to the action where the retype branch does not initially have a name  directory (nor file) in it.

Fix pushed to main. Close this once the fix is synced up to v1 tag.


Upgraded nuget to 5.4

Not ready to merge yet. Prerequisites:

Remove duplicate package.config logic (duality already has such logic).
Fix any remaining bugs

Is there any equivalent in NuGet 5, which we can query for project "status quo"

If I understand correctly you want a list of all packages needed including all dependencies. Nuget provides a API for this and the PackageConfig.xml itself can be used as input for this. With some logic you can then figure out what packages to install and what to uninstall.

If I understand correctly you want a list of all packages needed including all dependencies.

Ah, no, not the needed ones - I might have explained it all a bit convoluted. I'll try again, in short.
This is what we have now:

PackageConfig.xml: Which Duality packages the project wants.
Source\Packages via NuGet API: Which (NuGet) packages are installed right now.
Duality triggers NuGet to un/install so the list of Duality packages matches in both.

What we need now, since the packages folder no longer seems to play that role in NuGet:

PackageConfig.xml: Which Duality packages the project wants.
???: Which (NuGet) packages are installed right now.
Duality triggers NuGet to un/install so the list of Duality packages matches in both.

That second ??? part is what I meant. Is there some sort of NuGet-managed package lock file or something else that tells you what is actually installed right now? If not, we could probably write our own in some bookkeeping file inside the Source\Packages folder.

Rebased on the latest master. Changes are now down from 39 to 9 files :)

???: Which (NuGet) packages are installed right now.

Isn't this something duality could provide based upon the files present?

In that case, I'd probably go with an InstalledPackages.xml inside Source\Packages that gets updated immediately after an individual package install / uninstall is complete. That way, NuGet would be out of the equation for bookkeeping here, and we don't risk falling into ambiguity traps when checking plugin, lib and sample files. For a first iteration, behavior would also be equal to what we have right now, which is nice. Could also be an opportunity to clean up a bit of local package setup code.
I can look into this, provided I manage to carve out some time, fingers crossed 😄

Yup might be better that you look into this particular part.
In the current commit of this PR there is still the package config on the nuget side that is not needed anymore I think btw.

Okay, so right now I'm the bottleneck for moving this forward, but I'll try to briefly summarize what I think needs to be done here before we can merge:
ToDo

Get the basics for unit testing of package management back up and running.

Respect repository URLs specified in Duality PackageSetup, including local folder paths.
Check out if packing dummy packages for testing still works, fix if necessary.
Ensure the most basic install / uninstall tests succeed.

Sandbox NuGet settings used in Duality package management.

Use a default, then modify local instance.
Do not rely on system or user settings for NuGet to avoid interference in various dev setups.
NuGet settings links for research:

https://docs.microsoft.com/en-us/nuget/consume-packages/configuring-nuget-behavior
https://github.com/NuGet/Home/issues/3972
https://github.com/NuGet/Home/wiki/[Spec]-NuGet-settings-in-MSBuild

Introduce a Duality InstalledPackages.xml in Source\Packages to reflect which (NuGet) packages are currently installed, to replace the previous "local repository" mechanic that was based simply on existing folder structures. (See above)
Gradually fix things until all tests are green again.
Do a full DualityEditor test locally.

Fresh install from local repository
Fresh install from remote repository
Package restore, install, uninstall and update via PackageConfig.xml changes and restart.
Package install, uninstall and update via package manager UI
Test performance now that PackageCache is gone and re-introduce some equivalent if it's too bad.

Final cleanup, API and style tweaks.

I'll report back with progress and help requests as soon as I get to it.

@ilexp do you still have time to implement this? If not maybe we should make it clear that somebody else can take it over.
Not that I have much time lately though...

@ilexp do you still have time to implement this? If not maybe we should make it clear that somebody else can take it over.

Good call - I'm honestly a bit overwhelmed with real life stuff lately and since I'm clearly the bottleneck here, I'd be happy to let someone take over, and try to help with advice.

Seems like PackagePathResolver and PackageIdentity truncate the revision number. Meaning a version like <IP_ADDRESS> will end up as 1.0.0. Seems nuget doesnt want you to use <IP_ADDRESS>? Needs some more research to be sure.

Closing this as we have decided to take a different route in #786


Include Tuist

Project URL
https://github.com/tuist/tuist
Category
Tools
Description
Add Tuist to the list of tools.
Checklist

[x] Only one project/change is in this pull request
[x] Has unit tests, integration tests or UI tests
[x] Addition in chronological order (bottom of category)
[x] Supports iOS 9 / tvOS 10 or later
[x] Supports Swift 4 or later
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

          1 Warning

:warning:
Found 2 link issues, a project collaborator will take care of these, thanks :)

Link issues by awesome_bot

Line
Status
Link

1211
301
https://github.com/prynt/PryntTrimmerView redirects tohttps://github.com/HHK1/PryntTrimmerView

1570
301
https://github.com/facebook/facebook-ios-sdk redirects tohttps://github.com/facebook/facebook-objc-sdk

  Generated by :no_entry_sign: Danger

@pepibumur I think Project setup section would be better.

Done @serhii-londar

@pepibumur Thanks for contributing.


Removes auth_access_token and auth_id from user schema

Removes ghost_auth_id and ghost_auth_access_token from schema
Removes usage of fields from code
Removes usage of fields from tests
Adds migration for dropping ghost_auth_id and ghost_auth_access_token columns on user table

@gargol lmk if this is good to merge 😄