Make generation of conversion buff optional

I would say make it off by default. Since it's often wrong, it's unreliable. If you can't trust it worked properly and have to double-check everything anyway, adjusting manually should be the assumed method of dealing with imports.

Making the numbers correct without the corrective buff is definitely the desired goal.
If there's issues with doing that due to math not working correctly in PF1 should be reported to the game system.

There will never be a complete parity between the values in the statblock and the ones in the system simply because a non-zero number of statblocks has wrong values in them. So the question is do we want the "correct" values as derived by the system, or do we want the values as presented in the statblock. That was one of the reasons i've started using the conversion buff in the first place.
Apart from the conversion buffs (which are created after the actor is complete) a number of adjustments are done while parsing, e.g. attack or damage modifiers.
I'll have to find all these and only invoke them if this future setting "try to validate values and create adjustments and conversion buffs" is set to true.

When the derived values in a statblock are clearly miscalculated, they are a mistake. When the publisher has made a mistake, I go with the correct derived values rather than what is written.


Standalone version of the asm cleaner

Would be handy to be able to clean up arbitrary code locally by running a tool that basically wraps asm-parser.js
(Suggested by @brevzin)

I cobbled together a quick and dirty version of this if someone wants to look at it, I put it in lib/tooling/asm-file-parser.js.
const fs = require('fs');
const getStdin = require('get-stdin');
const parser = new (require('../asm-parser'))();
const utils = require('../utils');

getStdin(function(str) {
  for (let line of parser.processAsm(str, {})) {
    console.log(line.text);
  }
}, {});

So this is absolutely terrible code but I did get it to strip most of the directives using the default filters given by BaseCompiler.getDefaultFilters.
const getStdin = require('get-stdin');
const parser = new (require('../asm-parser'))();
// this is a kludge because we don't care about the source or assembly language
const compiler = new (require('../base-compiler'))({lang: "c"}, {compilerProps: (id, _) => ""});

getStdin(str => {
    for (let line of parser.processAsm(str, compiler.getDefaultFilters())) {
        console.log(line.text);
    }
}, {});

The main issue is getDefaultFilters can't be called as a static function because BaseCompilers uses the new ES6 class keyword. If you're willing to change it to be static I could make my code much cleaner.
diff --git a/lib/base-compiler.js b/lib/base-compiler.js
index 0ea1a53e..b9af1066 100644
--- a/lib/base-compiler.js
+++ b/lib/base-compiler.js
@@ -860,7 +860,7 @@ Please select another pass or change filters.`;
         return this.compiler;
     }

-    getDefaultFilters() {
+    static getDefaultFilters() {

const getStdin = require('get-stdin');
const parser = new (require('../asm-parser'))();
const compiler = require('../base-compiler');

getStdin(str => {
    for (let line of parser.processAsm(str, compiler.getDefaultFilters())) {
        console.log(line.text);
    }
}, {});


chore(main): release 1.1.0

:robot: I have created a release beep boop
1.1.0 (2024-09-23)
Features

add callback and utility functions for chat completion (fde4cc2)
ci: update ci to base.nvim template (0a69989)
ci: update ci to base.nvim template #17 (c6f92aa)

Bug Fixes

workflows: update Lua workspace and add environment variable for tests (4e8a974)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v1.1.0
:sunflower:


Building from source

Dear VAPOR Team,
I wanted to build a native Apple Silicon version of VAPOR and noticed there is a lack of information how to build VAPOR from source. I had a look into your CI for checking how you build the releases. There I saw you download the necessary dependencies from a Google Drive.
Would it be possible to publish your way of building the dependencies? Maybe you even have a scripted build system for the complete workflow.

Sure, you can find instructions at the link below.  Please let us know if you find any inconsistencies or errors.
https://vapor.readthedocs.io/en/readthedocs/contributing.html#building-vapor-from-source

Thanks a lot. I didn‘t find it in the documentation.
I now managed to build a a fully native Apple Silicon version with your August-2019 source and some updated source packages. I qualitatively compared the performance of a more complex rendering task with the standard Intel binary and it‘s definitely way faster and snappier, especially for CPU heavy things like flows.
If there is any interest from your side, I can share my compilation procedurey

That's great.  Did you rebuild the third party libraries, or just Vapor?  Please do share your proceedure.

It‘s full a recompilation with all dependencies and OpenMP support. I had to update packages like Python and HDF5 to recent versions to be able to compile on Apple Silicon.
I will share my steps when I am at work again tomorrow.

Great, thanks again and I'm looking forward to seeing your steps.

I am having a bit a hard time to package it. QT5 from homebrew doesn't work properly since it uses a different freetype version. I will now build QT5 from source as well.
So the current state: The build is working and I can package it with CPack. But it won't work on other macs since rpath management doesn't work yet.

I think I managed to build a portable version. There are some problems with it:

I have to use macdeployqt for correctly handling dependencies. If I use the OSX_PostBuild.py script to manage rpath on the ThirdParty libs the resulting vapor will crash when loading some QT pluging. I still have no idea why. So packaging is:

make
make installer
cd _CPack_Packages/Darwin/DragNDrop/VAPOR3-3.8.0-Darwin/ALL_IN_ONE
macdeployqt vapor.app
Then you have fully portable version.

This deployment leads to two folders, lib and Frameworks in the app. Frameworks contains then most of the needed libraries but lib will need to have the shared libraries of vapor itself.
The result is a bigger vapor.app.

So as a first step I suggest you test my build:
https://polybox.ethz.ch/index.php/s/FCyAaoYGrc5sSGO
Maybe you have some benchmark cases at hand.
We can then maybe dive further into building and packaging.

I now managed to build it completely with the CMake buildsystem without any other deployment tool. 😃
I updated the build under https://polybox.ethz.ch/index.php/s/FCyAaoYGrc5sSGO
Here is my workflow:
As a base, I used your source distribution available under:
https://drive.google.com/open?id=1sWIV-Y66aFuDkC2oDnceIIUJDDH4puKI
The following packages were updated:
Python-3.9.16
HDF5 1.14
udunits 2.28
The following packages were added:
zlib 1.2.13 (for minizip)
libpng 1.6.37 (to prevent using system libpng)
In addition, I had to compile qt5 by hand since homebrew qt5 has lots of dependencies to other homebrew packages.
I used the one file version here:
https://download.qt.io/archive/qt/5.15/5.15.8/single/qt-everywhere-opensource-src-5.15.8.tar.xz
Compiling QT5
export MACOSX_DEPLOYMENT_TARGET=11.0
export PREF=/User/strebdom/BUILD_VAPOR/QT5
./configure -prefix $PREF
make -j 15
# wait for a long time. ;-)
make install

Compiling other dependencies
brew install xz openssl zlib glm llvm libomp

export MACOSX_DEPLOYMENT_TARGET=11.0
export PREF=/User/strebdom/BUILD_VAPOR/THIRD_PARTY_LIBS/

# libpng
cd libpng-1.6.37
CC=clang CXX=clang++ ./configure --prefix=$PREF
make install -j 15

# Minizip from zlib
cd zlib-1.2.13/contrib/minizip
autoreconf -i
CC=clang CXX=clang++ ./configure --prefix=$PREF
make install -j 15

# assimp
cd assimp-4.1.0
mkdir build
cd build
cmake -DCMAKE_INSTALL_PREFIX=$PREF -DCMAKE_EXE_LINKER_FLAGS=$PREF/lib -DCMAKE_BUILD_TYPE=Release ..
make install -j 15

# szip
cd szip-2.1.1
CC=clang CXX=clang++ ./configure --prefix=$PREF
make install -j 15

# HDF5
cd hdf5-1.14.0
CC=clang CXX=clang++ ./configure --prefix=$PREF --with-szlib=$PREF
make install -j 15

# NetCDF
cd netcdf-c-4.7.0
LDFLAGS=-L$PREF/lib/ CPPFLAGS=-I$PREF/include/ CC=clang CXX=clang++ ./configure --prefix=$PREF --disable-dap
make install -j 15

# Udunits
cd udunits-2.2.28
CC=clang CXX=clang++ ./configure --prefix=$PREF
make install -j 15

# freetype
cd freetype-2.10.1
LIBPNG_CFLAGS="-I$PREF/include" LIBPNG_LIBS="-L$PREF/lib -lpng16”  CC=clang CXX=clang++ ./configure --prefix=$PREF --with-harfbuzz=no
make install -j 15

# jpeg
cd jpeg9c
CC=clang CXX=clang++ ./configure --prefix=$PREF
make install -j 15

# libtiff
cd tiff-4.0.10
 LDFLAGS=-L$PREF/lib/ CPPFLAGS=-I$PREF/include/ CC=clang CXX=clang++ ./configure --prefix=$PREF
make install -j 15

# sqlite
cd sqlite-autoconf-3290000
CC=clang CXX=clang++ ./configure --prefix=$PREF

# libproj
cd proj-6.1.1
mkdir build
cd build
 cmake -DEXE_SQLITE3=$PREF/bin/sqlite3 -DSQLITE3_INCLUDE_DIR=$PREF/include -DSQLITE3_LIBRARY=$PREF/lib/libsqlite3.dylib -DCMAKE_INSTALL_PREFIX=$PREF -DPROJ_COMPILER_NAME=clang++ ..
 unzip ../../proj-datumgrid-1.8.zip -d data/
make install -j 15

# libgeotiff
cd libgeotiff-1.5.1
LDFLAGS=-L$PREF/lib/ CPPFLAGS=-I$PREF/include/ CC=clang CXX=clang++ ./configure --prefix=$PREF --with-zlib=yes --with-jpeg=yes
make install -j 15

# glew
I just set GLEW_DEST to $PREF.
make install

# Python
cd Python-3.9.16
CPPFLAGS="-I$PREF/include -I$(brew --prefix zlib)/include -I$(brew --prefix openssl)/include" LDFLAGS="-L$PREF/lib -L$(brew --prefix zlib)/lib  -L$(brew --prefix openssl)/lib" CC=clang CXX=clang++ ./configure  --with-openssl=/opt/homebrew/opt/openssl prefix=$PREF --enable-shared --with-ensurepip=install --with-suffix=.vapor --enable-optimizations
# Somehow pip didn't get installed. I then used https://bootstrap.pypa.io/get-pip.py with python3.vapor to install it.
$PREF/bin/python3.vapor get.pip.py
$PREF/bin/pip  install --upgrade --target $PREF/lib/python3.9/site-packages numpy scipy matplotlib
# I had to make a symlink from $PREF/include/python3.9 to $PREF/include/python3.9m since CMake wants to have Python include path there.
ln -s python3.9 python3.9m

Then the most recent problem was not all rpath were updated with the current configuration of OSX_PostBuild.py. I had to run it twice with changeFileID=False and changeFileID=True until all rpaths were changed. Also libGLEW was not detected with the script. I had to remove the os.access(filename, os.X_OK) condition. I will send a pull request later.
Check with otool -L that all rpaths are correctly set and no $PREF path is still active
Next is to edit you site.NCAR (or ../site.local?) with the appropriate paths.
Then building vapor is not difficult anymore:
cd ~/git/Vapor/builtutils
unzip GTE.zip
cd ...
mkdir build
cd build
cmake -DCMAKE_C_COMPILER="/opt/homebrew/opt/llvm/bin/clang" -DCMAKE_CXX_COMPILER="/opt/homebrew/opt/llvm/bin/clang++" -DCMAKE_C_FLAGS="-I/Users/strebdom/git/VAPOR/buildutils -I/opt/homebrew/include" -DCMAKE_CXX_FLAGS="-I/Users/strebdom/git/VAPOR/buildutils -I/opt/homebrew/include" -DCMAKE_BUILD_TYPE="RELEASE" -DBUILD_OSP="OFF" -DUSE_OMP="ON" -DDIST_INSTALLER="ON" ..
make -j 15
make installer

This should then lead to your shiny new Apple silicon VAPOR version.
I hope I didn't forget anything. If something doesn't work, please let me know.

To just try out a build:
https://polybox.ethz.ch/index.php/s/FCyAaoYGrc5sSGO

Thanks for doing this @pick2510.  These notes will help us with our next release.  Cheers!


added onBlur and onFocus props

Updated version of pull request #79

+1

+1

+1 please merge this

I've solved conflicts on #167


Update install commands

Please @PipKat if you can have a super quick look :)

@PipKat @germa89 thank you both so much for your help!

Problem with left-side navigation panels:

Problem with left-side navigation panels:
Is there perhaps a heading level skipped? I did note a strange navigation issue in pyansys/dev-guide#267, which is now closed. At the bottom of this dev guide page (https://dev.docs.pyansys.com/dev/doc-style/index.html), there is a link to the "Documenting" page. When it is clicked, the nav pane on the right doesn't show the page title. I assumed it was a font color issue, but maybe something in the latest changes to the Ansys Sphinx template is causing issues? @Revathyvenugopal162

@PProfizi the style has been fixed in ansys-sphinx-theme 0.9.5, to fix the sidebar please remove https://github.com/pyansys/pydpf-post/blob/master/docs/source/_templates/sidebar-nav-bs.html doc as i explaned in yesterdays meeting.

Thx @Revathyvenugopal162! This fixed the issue!


Nativescript FilePicker for ios

I want to perform file (pdf) upload functionality in my application (Android and ios). I see that filepicker is currently available only for Android . Is there any way by which I can use it for ios?

Yes , this dialog is just for android because I used some java code in it.like this one https://github.com/kazemihabib/nativescript-FilePicker/blob/master/app/dialogs/file_picker/file_picker_dialog.ts#L64
just port them to objective-c or use nativescript Files api.
As I don't use nativescript any more I can't update this.

Thanks . I also wanted to know If I want to create a plugin to connect
Nativescript with NativeMapSDK since I have never made a plugin, I don't
know how much time can it take. So can you please tell me how much time
estimate it can take?
Regards,
Shifa Salheen
Lead Programmer Analyst
Argusoft India Limited.
www.argusoft.com
On Thu, Jul 20, 2017 at 7:42 PM, habib kazemi<EMAIL_ADDRESS>wrote:

Yes , this dialog is just for android because I used some java code in
it.like this one https://github.com/kazemihabib/nativescript-
FilePicker/blob/master/app/dialogs/file_picker/file_picker_dialog.ts#L64
just port them to objective-c or use nativescript Files api.
As I don't use nativescript any more I can't update this.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kazemihabib/nativescript-FilePicker/issues/2#issuecomment-316715888,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AX_H_BdJFKXZj7uOqG8OgwWGRPWI5UHFks5sP2BBgaJpZM4OeEmI
.

nativescript changes a lot in these months that I didn't follow it and I can't tell you how much it might take I think it's better if you ask it here : https://nativescriptcommunity.slack.com


Stacked bar charts - would be so great

This is a great library. Data in a table is so much more usable than Google charts that we are currently using.
Would it be easy to add stacked bar charts? I.e. each bar is the stacked "sum" of multiple components? Then we could switch.

@JohnCClarke The framework supports stacking.
Check the Stacked Bars documentation https://chartscss.org/components/stacked/#stacked-bars

OMG! - Thanks for pointing that out. Somehow I just didn't spot them.
Marvellous!


Text on Annotations page for adding a new annotation file blends with background

Text on the annotations page is white or super light gray, so it’s difficult to see where to add label title/select file

Same underlying issue as #66

Fixed.


fix snowflake bugs with 0.10.1 functionality

In the pre-0.10.1 world, dbt's quoting of relations was inconsistent, leading to bugs in the below macros when run against Snowflake. This PR uses Relation objects to fix those bugs.
This build is failing because 0.10.1 is unreleased. We should merge this code only after the release is published.

Most of these changes have been superseded by other changes. Except for the cleanup to the tests, which I implemented over here.
As a result, closing this out!


implement duckduckgo as a source

Given the domain google.com:
Could search something like the following:
https://duckduckgo.com/html/?kd=-1&q=google.com

Fixed with https://github.com/subfinder/research/commit/7acf24cebf9356de6411133f633f67cf15dd06b0


Add monitoring for RFC6962/CT logs

Description

There is currently no log monitor for Fulcio's CT log (ctfe.sigstore.dev). We should implement support for querying a RFC6962 API, for monitoring consistency and verifying identities from logged certificates.

Looking into reusing https://github.com/google/certificate-transparency-go/tree/master/client/ctclient


Add support for path namespaces.

Issue
When looking into timber for a project I'm currently working on, I was looking to make use of path namespaces (e.g. https://symfony.com/doc/current/templating/namespaced_paths.html#registering-your-own-namespaces) but it seems that Timber doesn't currently support this.
Solution
This patch introduces support for path namespace, at time of writing only as part of user defined locations, however this could easily be added to to support namespace in theme dirs as well if you wanted.
Impact
It should be backwards compatible, so it shouldn't have any negative impact on existing users.
Usage Changes
Users who wish to make use of path namespaces can now do so, e.g. with a styleguide namespace
Timber::$locations = array(
    '/Users/jared/Sandbox/templates',
    '~/Sites/timber-templates/',
    ABSPATH.'/wp-content/templates',
    ABSPATCH.'/wp-content/styleguide' => 'styleguide'
);

Considerations
I've not spent too much time on this patch, I'm hoping for some guidance/advice if there are any edge cases I may not have considered as I am very new to this library.
It's also worth noting that I've just checked for a namespace presence and ignored if none there, but we could easily change to give each location the default namespace (__MAIN__) if none is configured, to cut down on an if statement.
Testing
I included one basic unit test, but would be happy to add more if you think this patch is worth including.

Coverage decreased (-0.02%) to 94.222% when pulling 7e3e17238b2cb0d09959c42f9b8b3ba3618019bb on jenkoian:add-twig-namespace-support into fefd9353dbf556916eacf441cc9de4dc703a8cc8 on timber:master.

Coverage decreased (-0.02%) to 94.222% when pulling 7e3e17238b2cb0d09959c42f9b8b3ba3618019bb on jenkoian:add-twig-namespace-support into fefd9353dbf556916eacf441cc9de4dc703a8cc8 on timber:master.

@jenkoian thanks for the contrib! I'll confess we're deep into work on 2.x so I won't be able to start a review right away.
My biggest concern is just double-tripple checking that the use of a namespace will not disrupt rendering a .twig file from a non-namespaced path (ie. inside the /templates or /views directory. Can you write a test that demonstrates and verifies this?

@jarednova thanks for taking a look at the PR! Yeah I figured it was all hands to the pump re. 2.x release (what a great 2.x feature namespace support would be btw! 😃). I'll add some more tests later today.

@jarednova I've added a few more tests, let me know if that's what you had in mind 👍

Yep! Those tests show namespaced and non-namespaced template calls living side-by-side in harmony. I think we're good here, but I'd still like @gchtr or @pascalknecht to give it a look as well to make sure there's something we're not missing/considering

Looks like build failed due to a composer issue on one of the jobs, are you able to restart the job?

@jarednova @jenkoian Codewise it looks good to me. Only objection to merge for me is documentation which is currently missing and code style which is currently not according to WordPress Guidelines.

@pascalknecht agreed! @jenkoian can you format according to WordPress Coding Standards and update the docs? I think this would belong in the template-locations.md file:
https://github.com/timber/timber/blob/master/docs/guides/template-locations.md
https://timber.github.io/docs/guides/template-locations/

Oh, this is a really nice addition! I just have one question: In the linked Symfony documentation, the pattern to describe namespaces is defined through path => namespace. Here, we would add it as namespace => path. Is this a deliberate solution that was chosen because of technical reasons? Or would it make sense to have 'ABSPATH.'/wp-content/styleguide' => styleguide' instead of 'styleguide' => ABSPATH.'/wp-content/styleguide' to follow Symfony’s style?

I'd echo @gchtr about following the Symfony convention. Anywhere Timber can follow existing conventions would be fantastic!

Thanks for your comments!

Codewise it looks good to me. Only objection to merge for me is documentation which is currently missing and code style which is currently not according to WordPress Guidelines.

Docs now added, have amended code style, although it doesn't look like this is enforced throughout the lib?

Oh, this is a really nice addition! I just have one question: In the linked Symfony documentation, the pattern to describe namespaces is defined through path => namespace. Here, we would add it as namespace => path. Is this a deliberate solution that was chosen because of technical reasons? Or would it make sense to have 'ABSPATH.'/wp-content/styleguide' => styleguide' instead of 'styleguide' => ABSPATH.'/wp-content/styleguide' to follow Symfony’s style?

Excellent spot! 🦅 👁 I initially planned to follow what symfony do (i.e. path => namespace) but I didn't think it made as much sense here as we're not configuring via yaml. For example, in Symfony you can imagine..
'path/to/templates1': namespace1
'path/to/templates2': namespace2
'path/to/templates3': ~

Would map to PHP as..
array(
    'path/to/templates1' => 'namespace1',
    'path/to/templates2' => 'namespace2',
    'path/to/templates3' => null,
);

Which makes looping over etc. really easy. However, if you imagine the following...
Timber::$locations = array(
    'path/to/templates1' => 'namespace1',
    'path/to/templates2' => 'namespace2',
    'path/to/templates3',
);

We'd end up with...
array(
    'path/to/templates1' => 'namespace1',
    'path/to/templates2' => 'namespace2',
    0 => 'path/to/templates3',
);

So we end up with the path being the key in some instances and the value in others, we can of course code around that, but it seemed simpler to me to just flip them around.
However I noticed Symfony supports multiple paths per namespace, which obviously won't work if we have the namespace as our key as we can't have duplicate keys. So, I've gone ahead and made this change. It's quite involved unfortunately, but all the tests pass. Only concern I have is that it will potentially change the following filters:
timber/loader/paths
timber/loader/loader
timber_locations
timber/locations
As previously they would get a list of paths like so:
array(
    'path/of/templates1',
    'path/of/templates2'
);

Where as now it'll be:
array(
    '__MAIN__' => array(
        'path/of/templates1'
    ),
    'namespace' => array(
        'path/of/templates2'
    )
);

Finally, I've added a test for multiple paths per namespace and I've also thought of nested namespaces, so I've added a test to cover that too.
Cheers!

Ok so it will affect the filters you mentioned:
timber/loader/paths timber/loader/loader timber_locations timber/locations
We will need to include this in the upgrade guide to 2.0 then. Agreed @jarednova ?

Cool stuff 😎. This looks good for me in terms of documentation.
I have to admit that the Loader isn’t my strongest suit, so I’d be happy if someone else could look at the code in detail, @jarednova maybe?
If the filters are going to change, we definitely need to add this in the Upgrade Guide for 2.0. I normally do this separately, as soon as a feature is merged. Currently, this pull request wants to merge into master. I guess when the existing filters will change, we would have to pull this into the 2.x branch.

Do you want me to rebase against 2.x ?

@jenkoian thanks so much for hanging with us through all these Qs. I think we're very close, but I get caught on the issue of the filters and how it could potentially break compatibility with anyone who's using timber/loader/paths or some of the others.
I just wrote a test in 9f4ed02d98b61f25679a1d66b3bdf8d640552826 to validate the current behavior and see how it compares to this PR (on my local the new test fails against this PR). I think there are two routes to go to merge this in:

Merge into 1.x and write some functions to adapt old filter behavior into the how things are handled with the namespaces
Merge into 2.x and handle write the info in the upgrade guide.

My vote is for #2; but I want to see what @jenkoian thinks of this

Also voting for option 2

Awesome test! I'll take a closer look and get back to you 👍

Ok had chance to review the failing test. Yes agree with your two options, I am happy to add the backwards compatibility workaround if you'd like, but yeah would probably vote for option 2. I guess one thing on that, is it would require the user to add a namespace, even if using the default, e.g.
$paths[Timber\Loader::MAIN_NAMESPACE][] = __DIR__.'/october/';
as opposed to simply
$paths[] = __DIR__.'/october/';
They would also need to ensure they're appending to an existing array (or passing an array if using a new namespace they've created).
Not sure if we deem this too much of a departure even for 2.x or not? I'm not sure how used these filters are for the community? I guess as long as we document the filter and it's usage it should be ok, I can't seem to find much docs on the filter at the mo, so perhaps that's something else I can add?

I also vote for option 2. In addition to that, could we get rid of the following pattern, where locations are assigned through a static variable?
Timber::$locations = array(
    'path/to/templates1' => 'namespace1',
    'path/to/templates2' => 'namespace2',
    'path/to/templates3',
);

Instead, I’d only use the timber/locations filter and make this the primary filter for custom locations.

They would also need to ensure they're appending to an existing array (or passing an array if using a new namespace they've created).

This is also a reason why I think using a filter only would be better, because that’s the established behavior for filters: You filter something, or you append to something existing. If we provide good examples, I don’t see a problem.
For the deprecation, I’d do it like this:

Let Timber::$locations work like before, but issue a deprecation warning through Helper::deprecated().
Add a check for the filters, whether the resulting array is associative or not. If it’s not associative, then do not apply the namespacing functionality and issue a deprecation warning through Helper::deprecated().

@jenkoian There’s not so much documentation about the filters yet, but if you’re going to rebase against 2.x, then you’re gonna see that there’s the base for the upcoming filter documentation (read more about this here.
https://github.com/timber/timber/blob/7efcfb222ed8bf88c3c37f9468feef5b5af7c35e/lib/LocationManager.php#L25-L34
I’d be very happy if you could complete that with descriptions and examples, etc. We’d still have the main documentation in the Template Locations Guide. The filter documentation is more some kind of technical reference.

@gchtr that is an awesome approach (love this project!). When I get some time i'll add the filter documentation.
I've not rebased this against 2.x yet, do you want me to do that now, or should I open up a new PR with this against 2.x for comparison?

@jenkoian please open a fresh PR against 2.x (referencing this PR), I think things will be easiest to track there — thanks!

Ok opened against 2.x here: https://github.com/timber/timber/pull/1811 struggling for time a bit at the mo, so not had chance to make the recommended changes. Will do so as soon as I can!

Great, thanks @jenkoian! I'm going to close this PR so we can follow-up on #1811 and resolve that last change there


Polysemy is deprecating MemberWithError

The MemberWithError type in Polysemy is being deprecated and will be removed in the next version. The upgrade path is simply to replace it with Member. I'm happy to send a PR if you'd like.

PRs are welcome, thanks in advance!


chore(cli): clarify codes

Types of changes
What kind of change does this PR introduce? (check at least one)

[ ] Breaking change
[ ] Bugfix
[ ] Feature
[ ] Code style update
[x] Refactoring
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

Description

Issue Number: N/A

Codecov Report

Merging #122 into develop will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           develop   #122   +/-   ##
======================================
  Coverage      100%   100%
======================================
  Files           12     12
  Lines          108    108
  Branches        18     22    +4
======================================
  Hits           108    108

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 bef7d14...bd8b66e. Read the comment docs.


Bug/fix conversion test failure

This updates the conversion tests to match the output from Pandoc 1.13.2. rake tests will now be more useful.

Thanks for the updates. Works great now!

No problem! Glad to help!


Find does not work for Jupyter notebooks

When using Jupyter notebook with Vs Code, Edit -> Find, or pressing Ctrl + F, does nothing.
No search text box appears.
The notebook works fine in the Jupyter lab but not in VS Code.

Please file this issue on the vscode-python extension's repo: https://github.com/microsoft/vscode-python/issues


minor: Fix an artifact of delivery email migration in populate_analytics_db.

See: https://chat.zulip.org/#narrow/stream/49-development-help/topic/login.20error/near/712226
Probably we should do a cleanup to only have a single way of creating users.

Merged, but yeah, we should make populate_analytics_db do do_create_user, or at least call what we call in populate_db.  (populate_db uses somewhat hacky methods to make it a bit faster, which was very much justified before we had the database state caching we have in place now)


[SDP-928] serve/anchor: Make receiver registration handler tenant aware

What
Upgrade Anchor to use version 2.4.0 which includes the following change
Change SEP24QueryTokenAuthenticateMiddleware and SEP24HeaderTokenAuthenticateMiddleware to parse the home domain from the SEP24 token claims.
Why
The home domain will be used to determine which tenant we're targeting.
Loading the tenant in the request’s context, will allow the MultiTenantDataSourceRouter to select the correct tenant.
Known limitations
N/A
Checklist
PR Structure

[x] This PR has reasonably narrow scope (if not, break it down into smaller PRs).
[x] This PR does not mix refactoring changes with feature changes (split into two PRs otherwise).
[x] This PR's title starts with the name of the package, area, or subject affected by the change.

Thoroughness

[x] This PR adds tests for the new functionality or fixes.
[x] This PR contains the link to the Jira ticket it addresses.

Configs and Secrets

[x] No new CONFIG variables are required -OR- the new required ones were added to the helmchart's values.yaml file.
[x] No new CONFIG variables are required -OR- the new required ones were added to the deployments (pr-preview, dev, demo, prd).
[x] No new SECRETS variables are required -OR- the new required ones were mentioned in the helmchart's values.yaml file.
[x] No new SECRETS variables are required -OR- the new required ones were added to the deployments (pr-preview secrets, dev secrets, demo secrets, prd secrets).

Release

[x] This is not a breaking change.
[x] This is ready for production.. If your PR is not ready for production, please consider opening additional complementary PRs using this one as the base. Only merge this into develop or main after it's ready for production!

Deployment

[ ] Does the deployment work after merging?

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr117.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr117.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr117.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr117.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr117.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr117.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr117.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr117.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr117.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr117.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr117.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr117.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr117.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr117.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr117.previews.kube001.services.stellar-ops.com


Click on map to create post in App

Required for https://github.com/Hylozoic/HyloReactNative/issues/523. It won’t break anything currently and it'd be good to have it merged soon than later so it's "just there" once the related release of the App is ready.

Change MapExplorer to enable "Create Post from Map" feature on Mobile


Pressing key during progress bar causes rerender

When spawning a progress bar like so:
for _ in 0..miles_to_travel {
            thread::sleep(Duration::from_millis(60));
            miles_traveled += 1;
            progress.set_position(((miles_traveled as f32 / miles_to_travel as f32) * 100.0) as u64);
        }

If I press any key during the progress bar, I get a rerender of the progress bar.
███░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 7/100
██████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 12/100
███████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 14/100
████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 16/10

How do I prevent this?

I don't think there is a way to prevent this. It's kind of just a fact of life for terminal UIs. Try pressing enter during a git clone for instance. It will mess up the output too.

Try pressing enter during a git clone for instance. It will mess up the output too.

Yup, I tried this for git clone, cargo build --release, npm install, they all behave the same.

Unless you go with something like ncurses/curses, I don't think there is a way to prevent this.

Yeah I think my usecase (game) might actually be better met with either a more low level terminal library (crossterm) or a full fledged TUI framework (ratatui).
That said, while I don't see an easy way to fix this at the level of abstraction indicatif  and console operate at, I think it's definitely something that can be fixed. The solution is basically to disregard all terminal inputs while the progress bar is updated, or at least provide a way for users to selectively disregard terminal inputs.
I was able to get it to work somewhat how I want by constantly calling term.read_key() in a separate thread while I update the progress bar.
let (sx, rx) = mpsc::channel::<()>();
let thread_term = term.clone();
let handle = thread::spawn(move || loop {
    if rx.try_recv().is_ok() {
        break;
    }
    thread_term.read_key().unwrap();
});
for _ in 0..miles_to_travel {
    thread::sleep(Duration::from_millis(60));
    miles_traveled += 1;
    progress.set_position(((miles_traveled as f32 / miles_to_travel as f32) * 100.0) as u64);
}
progress.finish();
term.write_line("Done!").unwrap();
sx.send(()).unwrap();
handle.join().unwrap();

This has the side effect that you must press a key to continue after the progress bar is done, but for my usecase that's fine. Also I can see how this might be a problem if you wanted to, say prompt the user for input in the middle of a suspend call.


[Bug]: nuxt installation not work at all!

Reproduction
Just look at the complete log below
Describe the bug
step by step -> https://www.shadcn-vue.com/docs/installation/nuxt.html
and then:
⬢ [Docker] ❯ npx nuxi@latest init my-app

✔ Which package manager would you like to use?
pnpm
[start] Installing dependencies...
! The local project doesn't define a 'packageManager' field. Corepack will now add one referencing<EMAIL_ADDRESS>! For more details about this field, consult the documentation at https://nodejs.org/api/packages.html#packagemanager

Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 80, reused 80, downloaded 0, added 0
Progress: resolved 350, reused 304, downloaded 0, added 0
Progress: resolved 694, reused 600, downloaded 0, added 0
 WARN  7 deprecated subdependencies found<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Packages: +603
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Progress: resolved 697, reused 603, downloaded 0, added 86
Progress: resolved 697, reused 603, downloaded 0, added 437
Progress: resolved 697, reused 603, downloaded 0, added 474
Progress: resolved 697, reused 603, downloaded 0, added 603, done

> nuxt-app@ postinstall /workspace/my-app
> nuxt prepare

[success] Types generated in .nuxt

dependencies:
+ nuxt 3.13.2
+ vue 3.5.12
+ vue-router 4.4.5

Done in 11.4s
[success] Installation completed.

✔ Initialize git repository?
No
[log]
✨ Nuxt project has been created with the `v3` template. Next steps:
[log]  › `cd my-app`
[log]  › Start development server with `pnpm run dev`

root in workspace on  main [?] via  v20.18.0 took 18s
⬢ [Docker] ❯ cd my-app

root in workspace/my-app on  main [?] via  v20.18.0
⬢ [Docker] ❯ pnpm add typescript -D
Progress: resolved 0, reused 1, downloaded 0, added 0
Progress: resolved 33, reused 33, downloaded 0, added 0
Progress: resolved 442, reused 418, downloaded 0, added 0
 WARN  7 deprecated subdependencies found<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Packages: +14
++++++++++++++
Progress: resolved 698, reused 604, downloaded 0, added 14, done

devDependencies:
+ typescript 5.6.3

Done in 3.4s

root in workspace/my-app on  main [?] via  v20.18.0 took 3s
⬢ [Docker] ❯ pnpm add @nuxtjs/tailwindcss -D
Progress: resolved 0, reused 1, downloaded 0, added 0
Progress: resolved 26, reused 19, downloaded 0, added 0
Progress: resolved 534, reused 510, downloaded 0, added 0
Progress: resolved 771, reused 677, downloaded 0, added 0
 WARN  7 deprecated subdependencies found<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Packages: +76
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Progress: resolved 774, reused 680, downloaded 0, added 76, done

devDependencies:
+ @nuxtjs/tailwindcss 6.12.2

Done in 4.5s

root in workspace/my-app on  main [?] via  v20.18.0 took 4s
⬢ [Docker] ❯ npx nuxi@latest module add shadcn-nuxt
[info] Installing `shadcn-nuxt@latest` dependency
Progress: resolved 0, reused 1, downloaded 0, added 0
Progress: resolved 148, reused 148, downloaded 0, added 0
Progress: resolved 480, reused 456, downloaded 0, added 0
 WARN  7 deprecated subdependencies found<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Packages: +2
++
Progress: resolved 776, reused 682, downloaded 0, added 2, done

dependencies:
+ shadcn-nuxt 0.10.4

Done in 3.5s
[info] Adding `shadcn-nuxt` to the `modules`
[warn] ENOENT: no such file or directory, scandir '/workspace/my-app/components/ui'
[warn] Components directory not found: `/workspace/my-app/components/ui`
[success] Types generated in .nuxt

root in workspace/my-app on  main [?] via  v20.18.0 took 10s
⬢ [Docker] ❯ npx shadcn-vue@latest init
✔ Would you like to use TypeScript? (recommended)? … no / yes
✔ Which framework are you using? › Nuxt
✔ Which style would you like to use? › New York
✔ Which color would you like to use as base color? › Slate
✔ Where is your tsconfig.json file? … .nuxt/tsconfig.json
✔ Where is your global CSS file? (this file will be overwritten) … assets/css/tailwind.css
✔ Would you like to use CSS variables for colors? … no / yes
✔ Are you using a custom tailwind prefix eg. tw-? (Leave blank if not) …
✔ Where is your tailwind.config located? (this file will be overwritten) … tailwind.config.js
✔ Configure the import alias for components: … @/components
✔ Configure the import alias for utils: … @/lib/utils
✔ Write configuration to components.json. Proceed? … yes
[log]
- Writing components.json...
✔ Writing components.json...
- Initializing project...
[log]
[info] Detected a Nuxt project with 'shadcn-nuxt' v0.10.4...
✔ Initializing project...
- Installing dependencies...
✔ Installing dependencies...
[log]
[info] Success! Project initialization completed.
[log]

root in workspace/my-app on  main [?] via  v20.18.0 took 26s
⬢ [Docker] ❯ pnpm dev

> nuxt-app@ dev /workspace/my-app
> nuxt dev

[log] Nuxt 3.13.2 with Nitro 2.9.7
[log]
  ➜ Local:    http://localhost:3000/
  ➜ Network:  use --host to expose

[info] Using `2024-04-03` as fallback compatibility date.
[info] [nuxt:tailwindcss] Using Tailwind CSS from ~/assets/css/tailwind.css
[warn] ENOENT: no such file or directory, scandir '/workspace/my-app/components/ui'
[log]   ➜ DevTools: press Shift + Alt + D in the browser (v1.6.0)

[warn] [nuxt:tailwindcss] Failed to load config `./tailwind.config.js` due to the error below. Skipping..
 Cannot find module 'tailwindcss-animate'
Require stack:
- /workspace/my-app/tailwind.config.js
  Require stack:
  - tailwind.config.js
  at Module._resolveFilename (node:internal/modules/cjs/loader:1225:15)
  at Function.resolve (node:internal/modules/helpers:190:19)
  at _resolve (/workspace/node_modules/.pnpm/jiti@1.21.6/node_modules/jiti/dist/jiti.js:1:241814)
  at jiti (/workspace/node_modules/.pnpm/jiti@1.21.6/node_modules/jiti/dist/jiti.js:1:244531)
  at tailwind.config.js:1:92
  at evalModule (/workspace/node_modules/.pnpm/jiti@1.21.6/node_modules/jiti/dist/jiti.js:1:247313)
  at jiti (/workspace/node_modules/.pnpm/jiti@1.21.6/node_modules/jiti/dist/jiti.js:1:245241)
  at /workspace/node_modules/.pnpm/tailwindcss@3.4.14/node_modules/tailwindcss/lib/lib/load-config.js:56:30
  at loadConfig (/workspace/node_modules/.pnpm/tailwindcss@3.4.14/node_modules/tailwindcss/lib/lib/load-config.js:58:6)
  at /workspace/node_modules/.pnpm/@nuxtjs+tailwindcss@6.12.2/node_modules/@nuxtjs/tailwindcss/dist/module.mjs:230:41
[info] [nuxt:tailwindcss] Tailwind Viewer: http://localhost:3000/_tailwind/
[warn] Components directory not found: `/workspace/my-app/components/ui`
[info] Compiled `plugins/server.mjs` in 4541.18ms
[info] Compiled `plugins/client.mjs` in 5279.67ms
[info] Compiled `types/plugins.d.ts` in 5713.31ms
[success] Vite client built in 230ms
[success] Vite server built in 1077ms
[warn]
[warn] warn - No utility classes were detected in your source files. If this is unexpected, double-check the `content` option in your Tailwind CSS configuration.
[warn] warn - https://tailwindcss.com/docs/content-configuration
[error] Pre-transform error: [postcss] /workspace/my-app/assets/css/tailwind.css:1:1: The `border-border` class does not exist. If `border-border` is a custom class, make sure it is defined within a `@layer` directive.
[success] [nitro] Nuxt Nitro server built in 1517 ms
[info] Nuxt now supports pinning the behavior of provider and deployment presets with a compatibility date. We recommend you specify a `compatibilityDate` in your `nuxt.config` file, or set an environment variable, such as `COMPATIBILITY_DATE=2024-11-01`.
[info] Vite client warmed up in 1ms
[info] Vite server warmed up in 699ms
^C
root in workspa

root in workspace/my-app on  main [?] via  v20.18.0 took 30s
⬢ [Docker] ❯ npx shadcn-vue@latest add button
- Installing components...
✔ Done.

root in workspace/my-app on  main [?] via  v20.18.0 took 3s
⬢ [Docker] ❯ pnpm dev

> nuxt-app@ dev /workspace/my-app
> nuxt dev

[log] Nuxt 3.13.2 with Nitro 2.9.7
[log]
  ➜ Local:    http://localhost:3000/
  ➜ Network:  use --host to expose

[info] Using `2024-04-03` as fallback compatibility date.
[info] [nuxt:tailwindcss] Using Tailwind CSS from ~/assets/css/tailwind.css
[log]   ➜ DevTools: press Shift + Alt + D in the browser (v1.6.0)

[warn] [nuxt:tailwindcss] Failed to load config `./tailwind.config.js` due to the error below. Skipping..
 Cannot find module 'tailwindcss-animate'
Require stack:
- /workspace/my-app/tailwind.config.js
  Require stack:
  - tailwind.config.js
  at Module._resolveFilename (node:internal/modules/cjs/loader:1225:15)
  at Function.resolve (node:internal/modules/helpers:190:19)
  at _resolve (/workspace/node_modules/.pnpm/jiti@1.21.6/node_modules/jiti/dist/jiti.js:1:241814)
  at jiti (/workspace/node_modules/.pnpm/jiti@1.21.6/node_modules/jiti/dist/jiti.js:1:244531)
  at tailwind.config.js:1:92
  at evalModule (/workspace/node_modules/.pnpm/jiti@1.21.6/node_modules/jiti/dist/jiti.js:1:247313)
  at jiti (/workspace/node_modules/.pnpm/jiti@1.21.6/node_modules/jiti/dist/jiti.js:1:245241)
  at /workspace/node_modules/.pnpm/tailwindcss@3.4.14/node_modules/tailwindcss/lib/lib/load-config.js:56:30
  at loadConfig (/workspace/node_modules/.pnpm/tailwindcss@3.4.14/node_modules/tailwindcss/lib/lib/load-config.js:58:6)
  at /workspace/node_modules/.pnpm/@nuxtjs+tailwindcss@6.12.2/node_modules/@nuxtjs/tailwindcss/dist/module.mjs:230:41
[info] [nuxt:tailwindcss] Tailwind Viewer: http://localhost:3000/_tailwind/
[info] Compiled `plugins/server.mjs` in 4045.46ms
[info] Compiled `plugins/client.mjs` in 4742.87ms
[info] Compiled `types/plugins.d.ts` in 4973.53ms
[success] Vite client built in 185ms
[success] Vite server built in 917ms
[error] Pre-transform error: [postcss] /workspace/my-app/assets/css/tailwind.css:1:1: The `border-border` class does not exist. If `border-border` is a custom class, make sure it is defined within a `@layer` directive.
[error] Pre-transform error: Failed to resolve import "class-variance-authority" from "components/ui/button/index.ts". Does the file exist?
[error] Pre-transform error: [@vue/compiler-sfc] Failed to resolve extends base type.
If this previously worked in 3.2, you can instruct the compiler to ignore this extend by adding /* @vue-ignore */ before it, for example:

interface Props extends /* @vue-ignore */ Base {}

Note: both in 3.2 or with the ignore, the properties in the base type are treated as fallthrough attrs at runtime.

/workspace/my-app/components/ui/button/Button.vue
5  |  import { type ButtonVariants, buttonVariants } from '.'
6  |
7  |  interface Props extends PrimitiveProps {
   |                          ^^^^^^^^^^^^^^
8  |    variant?: ButtonVariants['variant']
9  |    size?: ButtonVariants['size']
[success] [nitro] Nuxt Nitro server built in 1022 ms
[info] Nuxt now supports pinning the behavior of provider and deployment presets with a compatibility date. We recommend you specify a `compatibilityDate` in your `nuxt.config` file, or set an environment variable, such as `COMPATIBILITY_DATE=2024-11-01`.
[info] Vite client warmed up in 1ms
[info] Vite server warmed up in 589ms
^C
root in workspace/my-app on  main [?] via  v20.18.0 took 18s
⬢ [Docker] ❯

root in workspace/my-app on  main [?] via  v20.18.0
⬢ [Docker] ❯ tree
.
├── README.md
├── app.vue
├── assets
│   └── css
│       └── tailwind.css
├── components
│   └── ui
│       └── button
│           ├── Button.vue
│           └── index.ts
├── components.json
├── lib
│   └── utils.ts
├── node_modules
│   ├── @nuxtjs
│   │   └── tailwindcss -> ../.pnpm/@nuxtjs+tailwindcss@6.12.2_magicast@0.3.5_rollup@4.24.3/node_modules/@nuxtjs/tailwindcss
│   ├── @radix-icons
│   │   └── vue -> ../.pnpm/@radix-icons+vue@1.0.0_vue@3.5.12_typescript@5.6.3_/node_modules/@radix-icons/vue
│   ├── nuxt -> .pnpm/nuxt@3.13.2_@parcel+watcher@2.4.1_@types+node@22.8.6_ioredis@5.4.1_magicast<EMAIL_ADDRESS>│   ├── shadcn-nuxt -> .pnpm/shadcn-nuxt@0.10.4_magicast<EMAIL_ADDRESS>│   ├── typescript -><EMAIL_ADDRESS>│   ├── vue -> .pnpm/vue<EMAIL_ADDRESS>│   └── vue-router -> .pnpm/vue-router@4.4.5_vue<EMAIL_ADDRESS>├── nuxt.config.ts
├── package.json
├── pnpm-lock.yaml
├── public
│   ├── favicon.ico
│   └── robots.txt
├── server
│   └── tsconfig.json
├── tailwind.config.js
└── tsconfig.json

19 directories, 15 files

System Info
cloud ide(cnb.coo) - code server
node lts: v20.18.0
pnpm: 9.12.2

System Information:

Linux d57f78a70171 5.4.241-1-tlinux4-0017.12 #1 SMP Fri Aug 2 14:51:21 CST 2024 x86_64 GNU/Linux

OS Release Info:

PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

Memory Info:

               total        used        free      shared  buff/cache   available
Mem:            16Gi       1.0Gi        14Gi          0B       803Mi        14Gi
Swap:             0B          0B          0B

Disk Info:

Filesystem             Size  Used Avail Use% Mounted on
overlay                128G  466M  128G   1% /
tmpfs                   64M     0   64M   0% /dev
tmpfs                  252G     0  252G   0% /sys/fs/cgroup
shm                    2.0G     0  2.0G   0% /dev/shm
/dev/vda1               50G  9.1G   38G  20% /usr/sbin/docker-init
git-clone-yyds         128G  617M  128G   1% /workspace
/dev/mapper/vg01-lv01  128G  617M  128G   1% /run/.git
tmpfs                  252G     0  252G   0% /proc/acpi
tmpfs                  252G     0  252G   0% /proc/scsi
tmpfs                  252G     0  252G   0% /sys/firmware

CPU Info:

Architecture:            x86_64
  CPU op-mode(s):        32-bit, 64-bit
  Address sizes:         43 bits physical, 48 bits virtual
  Byte Order:            Little Endian
CPU(s):                  192
  On-line CPU(s) list:   0-7
  Off-line CPU(s) list:  8-191

Contributes

[ ] I am willing to submit a PR to fix this issue
[ ] I am willing to submit a PR with failing tests

I'm having the same issue.
Did you made  the PR?

Fixed the issue:
"aliases": {
    "components": "components", //was "@/components"
    "utils": "lib/utils" //was "@/"lib/utils"
  }

the problem here was that components and utils had @ on it, i just removed it.
Also there are missing dependency that i had to manually install:
class-variance-authority and radix-vue as exemple.
I think that shadcn-vue should be used in production or big projects, its pretty and cool but its all broken.

Fixed the issue:
"aliases": {
    "components": "components", //was "@/components"
    "utils": "lib/utils" //was "@/"lib/utils"
  }

the problem here was that components and utils had @ on it, i just removed it.
Also there are missing dependency that i had to manually install:
class-variance-authority and radix-vue as exemple.
I think that shadcn-vue shouldn't be used in production or big projects, its pretty and cool but its all broken.

thanks, this helped me fix the issue also

👍Sent from my iPhoneOn Nov 3, 2024, at 11:34 AM, Björn @.> wrote:
Did you do step 5 https://www.shadcn-vue.com/docs/installation/nuxt.html ?
export default defineNuxtConfig({
modules: @./tailwindcss', 'shadcn-nuxt'],
shadcn: {
/**
* Prefix for all the imported component
/
prefix: '',
/*
* Directory that the component lives in.
* @default "./components/ui"
*/
componentDir: './components/ui'
}
})
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

Fixed the issue:
"aliases": {
    "components": "components", //was "@/components"
    "utils": "lib/utils" //was "@/"lib/utils"
  }

the problem here was that components and utils had @ on it, i just removed it.
Also there are missing dependency that i had to manually install:
class-variance-authority and radix-vue as exemple.
I think that shadcn-vue shouldn't be used in production or big projects, its pretty and cool but its all broken.

Hey @jamesallan93, this PR intends on fixing the issue above 😊.

Thanks, this worked for me as well.

Fixed the issue:
"aliases": {
    "components": "components", //was "@/components"
    "utils": "lib/utils" //was "@/"lib/utils"
  }

the problem here was that components and utils had @ on it, i just removed it.
Also there are missing dependency that i had to manually install:
class-variance-authority and radix-vue as exemple.
I think that shadcn-vue shouldn't be used in production or big projects, its pretty and cool but its all broken.

v0.11.2
https://www.shadcn-vue.com/docs/installation/nuxt.html step 4:
npx nuxi@latest module add shadcn-nuxt
root@85767f5c8e47:/workspace/my-app# npx nuxi@latest module add shadcn-nuxt
(node:1874) ExperimentalWarning: Support for loading ES Module in require() is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
[info] Installing `shadcn-nuxt@latest` dependency
Progress: resolved 0, reused 1, downloaded 0, added 0
Progress: resolved 18, reused 17, downloaded 1, added 0
Progress: resolved 117, reused 116, downloaded 1, added 0
Progress: resolved 434, reused 433, downloaded 1, added 0
 WARN  6 deprecated subdependencies found<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Packages: +2
++
Progress: resolved 765, reused 690, downloaded 1, added 1
Progress: resolved 765, reused 690, downloaded 2, added 2, done

dependencies:
+ shadcn-nuxt 0.11.2

Done in 5s
[info] Adding `shadcn-nuxt` to the `modules`
[info] [nuxt:tailwindcss] Using default Tailwind CSS file
[error] Nuxt module should be a function: @nuxtjs/color-mode
  at loadNuxtModuleInstance (node_modules/.pnpm/@nuxt+kit@3.14.159_magicast@0.3.5_rollup@4.25.0/node_modules/@nuxt/kit/dist/index.mjs:2460:11)
  at async installModule (node_modules/.pnpm/@nuxt+kit@3.14.159_magicast@0.3.5_rollup@4.25.0/node_modules/@nuxt/kit/dist/index.mjs:2389:47)
  at async setup (node_modules/.pnpm/shadcn-nuxt@0.11.2_magicast@0.3.5_rollup@4.25.0/node_modules/shadcn-nuxt/dist/module.mjs:46:5)
  at async normalizedModule (node_modules/.pnpm/@nuxt+kit@3.14.159_magicast@0.3.5_rollup@4.25.0/node_modules/@nuxt/kit/dist/index.mjs:2140:17)
  at async installModule (node_modules/.pnpm/@nuxt+kit@3.14.159_magicast@0.3.5_rollup@4.25.0/node_modules/@nuxt/kit/dist/index.mjs:2397:95)
  at async initNuxt (node_modules/.pnpm/nuxt@3.14.159_@parcel+watcher@2.5.0_@types+node@22.9.0_ioredis@5.4.1_magicast@0.3.5_rollup@4._oj52vvaqwdjakw7vhfwwy7k6ee/node_modules/nuxt/dist/index.mjs:4669:5)
  at async loadNuxt (node_modules/.pnpm/nuxt@3.14.159_@parcel+watcher@2.5.0_@types+node@22.9.0_ioredis@5.4.1_magicast@0.3.5_rollup@4._oj52vvaqwdjakw7vhfwwy7k6ee/node_modules/nuxt/dist/index.mjs:4839:5)
  at async loadNuxt (node_modules/.pnpm/@nuxt+kit@3.14.159_magicast@0.3.5_rollup@4.25.0/node_modules/@nuxt/kit/dist/index.mjs:2627:19)
  at async Object.run (/root/.npm/_npx/b95349761371180e/node_modules/nuxi/dist/chunks/prepare.mjs:61:18)
  at async runCommand$1 (/root/.npm/_npx/b95349761371180e/node_modules/nuxi/dist/shared/nuxi.bd0a2fa0.mjs:1648:16)
  at async runCommand (/root/.npm/_npx/b95349761371180e/node_modules/nuxi/dist/shared/nuxi.bd0a2fa0.mjs:2019:10)
  at async Object.setup (/root/.npm/_npx/b95349761371180e/node_modules/nuxi/dist/chunks/add2.mjs:197:5)
  at async runCommand$1 (/root/.npm/_npx/b95349761371180e/node_modules/nuxi/dist/shared/nuxi.bd0a2fa0.mjs:1620:5)
  at async runCommand$1 (/root/.npm/_npx/b95349761371180e/node_modules/nuxi/dist/shared/nuxi.bd0a2fa0.mjs:1639:11)
  at async runCommand$1 (/root/.npm/_npx/b95349761371180e/node_modules/nuxi/dist/shared/nuxi.bd0a2fa0.mjs:1639:11)
  at async runMain$1 (/root/.npm/_npx/b95349761371180e/node_modules/nuxi/dist/shared/nuxi.bd0a2fa0.mjs:1777:7)

[error] Nuxt module should be a function: @nuxtjs/color-mode
root@85767f5c8e47:/workspace/my-app#

try pnpx nuxi@latest module add shadcn-nuxt
root@85767f5c8e47:/workspace/my-app# pnpx nuxi@latest module add shadcn-nuxt
Progress: resolved 1, reused 0, downloaded 0, added 0
Packages: +1
+
Progress: resolved 1, reused 0, downloaded 1, added 1, done
[info] Installing `shadcn-nuxt@latest` dependency
Progress: resolved 0, reused 1, downloaded 0, added 0
Progress: resolved 16, reused 16, downloaded 0, added 0
Progress: resolved 182, reused 182, downloaded 0, added 0
Progress: resolved 581, reused 557, downloaded 0, added 0
 WARN  6 deprecated subdependencies found<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Already up to date
Progress: resolved 765, reused 692, downloaded 0, added 0, done

Done in 4.1s
[info] `shadcn-nuxt` is already in the `modules`
[info] [nuxt:tailwindcss] Using default Tailwind CSS file
[error] Nuxt module should be a function: @nuxtjs/color-mode
  at loadNuxtModuleInstance (node_modules/.pnpm/@nuxt+kit@3.14.159_magicast@0.3.5_rollup@4.25.0/node_modules/@nuxt/kit/dist/index.mjs:2460:11)
  at async installModule (node_modules/.pnpm/@nuxt+kit@3.14.159_magicast@0.3.5_rollup@4.25.0/node_modules/@nuxt/kit/dist/index.mjs:2389:47)
  at async setup (node_modules/.pnpm/shadcn-nuxt@0.11.2_magicast@0.3.5_rollup@4.25.0/node_modules/shadcn-nuxt/dist/module.mjs:46:5)
  at async normalizedModule (node_modules/.pnpm/@nuxt+kit@3.14.159_magicast@0.3.5_rollup@4.25.0/node_modules/@nuxt/kit/dist/index.mjs:2140:17)
  at async installModule (node_modules/.pnpm/@nuxt+kit@3.14.159_magicast@0.3.5_rollup@4.25.0/node_modules/@nuxt/kit/dist/index.mjs:2397:95)
  at async initNuxt (node_modules/.pnpm/nuxt@3.14.159_@parcel+watcher@2.5.0_@types+node@22.9.0_ioredis@5.4.1_magicast@0.3.5_rollup@4._oj52vvaqwdjakw7vhfwwy7k6ee/node_modules/nuxt/dist/index.mjs:4669:5)
  at async loadNuxt (node_modules/.pnpm/nuxt@3.14.159_@parcel+watcher@2.5.0_@types+node@22.9.0_ioredis@5.4.1_magicast@0.3.5_rollup@4._oj52vvaqwdjakw7vhfwwy7k6ee/node_modules/nuxt/dist/index.mjs:4839:5)
  at async loadNuxt (node_modules/.pnpm/@nuxt+kit@3.14.159_magicast@0.3.5_rollup@4.25.0/node_modules/@nuxt/kit/dist/index.mjs:2627:19)
  at async Object.run (/root/.cache/pnpm/dlx/p6mpn5xjw7rpzdkp6svcvil6ve/19313c47a9b-e32/node_modules/.pnpm/nuxi@3.15.0/node_modules/nuxi/dist/chunks/prepare.mjs:61:18)
  at async runCommand$1 (/root/.cache/pnpm/dlx/p6mpn5xjw7rpzdkp6svcvil6ve/19313c47a9b-e32/node_modules/.pnpm/nuxi@3.15.0/node_modules/nuxi/dist/shared/nuxi.bd0a2fa0.mjs:1648:16)

[error] Nuxt module should be a function: @nuxtjs/color-mode
root@85767f5c8e47:/workspace/my-app#

Yep, same here

v0.11.2
https://www.shadcn-vue.com/docs/installation/nuxt.html step 4:
npx nuxi@latest module add shadcn-nuxt
root@85767f5c8e47:/workspace/my-app# npx nuxi@latest module add shadcn-nuxt
(node:1874) ExperimentalWarning: Support for loading ES Module in require() is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
[info] Installing `shadcn-nuxt@latest` dependency
Progress: resolved 0, reused 1, downloaded 0, added 0
Progress: resolved 18, reused 17, downloaded 1, added 0
Progress: resolved 117, reused 116, downloaded 1, added 0
Progress: resolved 434, reused 433, downloaded 1, added 0
 WARN  6 deprecated subdependencies found<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Packages: +2
++
Progress: resolved 765, reused 690, downloaded 1, added 1
Progress: resolved 765, reused 690, downloaded 2, added 2, done

dependencies:
+ shadcn-nuxt 0.11.2

Done in 5s
[info] Adding `shadcn-nuxt` to the `modules`
[info] [nuxt:tailwindcss] Using default Tailwind CSS file
[error] Nuxt module should be a function: @nuxtjs/color-mode
  at loadNuxtModuleInstance (node_modules/.pnpm/@nuxt+kit@3.14.159_magicast@0.3.5_rollup@4.25.0/node_modules/@nuxt/kit/dist/index.mjs:2460:11)
  at async installModule (node_modules/.pnpm/@nuxt+kit@3.14.159_magicast@0.3.5_rollup@4.25.0/node_modules/@nuxt/kit/dist/index.mjs:2389:47)
  at async setup (node_modules/.pnpm/shadcn-nuxt@0.11.2_magicast@0.3.5_rollup@4.25.0/node_modules/shadcn-nuxt/dist/module.mjs:46:5)
  at async normalizedModule (node_modules/.pnpm/@nuxt+kit@3.14.159_magicast@0.3.5_rollup@4.25.0/node_modules/@nuxt/kit/dist/index.mjs:2140:17)
  at async installModule (node_modules/.pnpm/@nuxt+kit@3.14.159_magicast@0.3.5_rollup@4.25.0/node_modules/@nuxt/kit/dist/index.mjs:2397:95)
  at async initNuxt (node_modules/.pnpm/nuxt@3.14.159_@parcel+watcher@2.5.0_@types+node@22.9.0_ioredis@5.4.1_magicast@0.3.5_rollup@4._oj52vvaqwdjakw7vhfwwy7k6ee/node_modules/nuxt/dist/index.mjs:4669:5)
  at async loadNuxt (node_modules/.pnpm/nuxt@3.14.159_@parcel+watcher@2.5.0_@types+node@22.9.0_ioredis@5.4.1_magicast@0.3.5_rollup@4._oj52vvaqwdjakw7vhfwwy7k6ee/node_modules/nuxt/dist/index.mjs:4839:5)
  at async loadNuxt (node_modules/.pnpm/@nuxt+kit@3.14.159_magicast@0.3.5_rollup@4.25.0/node_modules/@nuxt/kit/dist/index.mjs:2627:19)
  at async Object.run (/root/.npm/_npx/b95349761371180e/node_modules/nuxi/dist/chunks/prepare.mjs:61:18)
  at async runCommand$1 (/root/.npm/_npx/b95349761371180e/node_modules/nuxi/dist/shared/nuxi.bd0a2fa0.mjs:1648:16)
  at async runCommand (/root/.npm/_npx/b95349761371180e/node_modules/nuxi/dist/shared/nuxi.bd0a2fa0.mjs:2019:10)
  at async Object.setup (/root/.npm/_npx/b95349761371180e/node_modules/nuxi/dist/chunks/add2.mjs:197:5)
  at async runCommand$1 (/root/.npm/_npx/b95349761371180e/node_modules/nuxi/dist/shared/nuxi.bd0a2fa0.mjs:1620:5)
  at async runCommand$1 (/root/.npm/_npx/b95349761371180e/node_modules/nuxi/dist/shared/nuxi.bd0a2fa0.mjs:1639:11)
  at async runCommand$1 (/root/.npm/_npx/b95349761371180e/node_modules/nuxi/dist/shared/nuxi.bd0a2fa0.mjs:1639:11)
  at async runMain$1 (/root/.npm/_npx/b95349761371180e/node_modules/nuxi/dist/shared/nuxi.bd0a2fa0.mjs:1777:7)

[error] Nuxt module should be a function: @nuxtjs/color-mode
root@85767f5c8e47:/workspace/my-app#

try pnpx nuxi@latest module add shadcn-nuxt
root@85767f5c8e47:/workspace/my-app# pnpx nuxi@latest module add shadcn-nuxt
Progress: resolved 1, reused 0, downloaded 0, added 0
Packages: +1
+
Progress: resolved 1, reused 0, downloaded 1, added 1, done
[info] Installing `shadcn-nuxt@latest` dependency
Progress: resolved 0, reused 1, downloaded 0, added 0
Progress: resolved 16, reused 16, downloaded 0, added 0
Progress: resolved 182, reused 182, downloaded 0, added 0
Progress: resolved 581, reused 557, downloaded 0, added 0
 WARN  6 deprecated subdependencies found<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Already up to date
Progress: resolved 765, reused 692, downloaded 0, added 0, done

Done in 4.1s
[info] `shadcn-nuxt` is already in the `modules`
[info] [nuxt:tailwindcss] Using default Tailwind CSS file
[error] Nuxt module should be a function: @nuxtjs/color-mode
  at loadNuxtModuleInstance (node_modules/.pnpm/@nuxt+kit@3.14.159_magicast@0.3.5_rollup@4.25.0/node_modules/@nuxt/kit/dist/index.mjs:2460:11)
  at async installModule (node_modules/.pnpm/@nuxt+kit@3.14.159_magicast@0.3.5_rollup@4.25.0/node_modules/@nuxt/kit/dist/index.mjs:2389:47)
  at async setup (node_modules/.pnpm/shadcn-nuxt@0.11.2_magicast@0.3.5_rollup@4.25.0/node_modules/shadcn-nuxt/dist/module.mjs:46:5)
  at async normalizedModule (node_modules/.pnpm/@nuxt+kit@3.14.159_magicast@0.3.5_rollup@4.25.0/node_modules/@nuxt/kit/dist/index.mjs:2140:17)
  at async installModule (node_modules/.pnpm/@nuxt+kit@3.14.159_magicast@0.3.5_rollup@4.25.0/node_modules/@nuxt/kit/dist/index.mjs:2397:95)
  at async initNuxt (node_modules/.pnpm/nuxt@3.14.159_@parcel+watcher@2.5.0_@types+node@22.9.0_ioredis@5.4.1_magicast@0.3.5_rollup@4._oj52vvaqwdjakw7vhfwwy7k6ee/node_modules/nuxt/dist/index.mjs:4669:5)
  at async loadNuxt (node_modules/.pnpm/nuxt@3.14.159_@parcel+watcher@2.5.0_@types+node@22.9.0_ioredis@5.4.1_magicast@0.3.5_rollup@4._oj52vvaqwdjakw7vhfwwy7k6ee/node_modules/nuxt/dist/index.mjs:4839:5)
  at async loadNuxt (node_modules/.pnpm/@nuxt+kit@3.14.159_magicast@0.3.5_rollup@4.25.0/node_modules/@nuxt/kit/dist/index.mjs:2627:19)
  at async Object.run (/root/.cache/pnpm/dlx/p6mpn5xjw7rpzdkp6svcvil6ve/19313c47a9b-e32/node_modules/.pnpm/nuxi@3.15.0/node_modules/nuxi/dist/chunks/prepare.mjs:61:18)
  at async runCommand$1 (/root/.cache/pnpm/dlx/p6mpn5xjw7rpzdkp6svcvil6ve/19313c47a9b-e32/node_modules/.pnpm/nuxi@3.15.0/node_modules/nuxi/dist/shared/nuxi.bd0a2fa0.mjs:1648:16)

[error] Nuxt module should be a function: @nuxtjs/color-mode
root@85767f5c8e47:/workspace/my-app#

It is not mentioned in docs but you must install color-mode first as it does not installs auto.
Run npx nuxi@latest module add @nuxtjs/color-mode.
Ordering: tailwind, color mode, shadcn

@arshx86 npx nuxi module add color-mode
Waiting for https://github.com/unovue/shadcn-vue/pull/886, there is fix for dependencies.


Thanks :wink:


What is a "node migration"?

The table under "Impact to drive data during Cloud Service upgrades" has helpful information about what happens to data on a cloud service, but I can't find any explanation of when these various types of upgrades occur.
In particular, the loss of all drives in a node migration seems like a critically important situation to be aware of. Is this something that can occur automatically?
I'm assuming the upgrades described below are "In-place upgrades", is that right?
https://docs.microsoft.com/en-us/azure/cloud-services/cloud-services-guestos-msrc-releases

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f35a321f-48ac-8a4b-49fc-f97c06b81bc3
Version Independent ID: 676c77dc-8905-a957-01f8-b6310e144ef9
Content: How to update a cloud service
Content Source: articles/cloud-services/cloud-services-update-azure-service.md
Service: cloud-services
GitHub Login: @jpconnock
Microsoft Alias: jeconnoc

There is some more information on these blogs that seems to have informed this document.
https://blogs.msdn.microsoft.com/kwill/2016/03/08/paas-cloud-service-role-restart-scenarios/
https://blogs.msdn.microsoft.com/kwill/2012/10/05/windows-azure-disk-partition-preservation/
There isn't a lot of clarity in these documents regarding how cloud services actually work and the best way to persist files. There are the startup task examples but nothing really explains when and why they are useful.

Thanks for the feedback! We are currently investigating and will update you shortly.

@dcbrown16 I have assigned the issue to the content author to investigate further and update the document as appropriate.
Meanwhile @mmccrory Can you please share your insights on this customer's question related to node migration.

In particular, the loss of all drives in a node migration seems like a critically important situation to be aware of. Is this something that can occur automatically?

@RichardScheel Could you please help in answering the customer's question related to this doc -

I'm assuming the upgrades described below are "In-place upgrades", is that right?
https://docs.microsoft.com/en-us/azure/cloud-services/cloud-services-guestos-msrc-releases

I'm checking into this deeper. I'll let you know what I find out.

I stand corrected. I found a dev who works on that, and he says that the data on the disk is discarded when the monthly Guest OS patching happens. Sorry of the erroneous initial answer.

@RichardScheel thanks for checking on that!
I assume "the disk" in this case is referring to the D: Windows drive, which is indicated as "Rebuilt" in the link below under Portal Reimage or Guest OS Update?
https://blogs.msdn.microsoft.com/kwill/2012/10/05/windows-azure-disk-partition-preservation/
In that case, the document in question here is actually correct, but "Portal reimage" needs to be defined so we see that this happens when you allow auto updates. If the blog I linked above is correct, a "node migration" occurs when the hardware fails and we (Microsoft) migrate the role to new hardware.
So again, my proposal would be to add even one sentence or so describing what each of the "Scenario" values in the table mean and why they would occur.

I found a little more information about the scenarios. Here is what one of the devs gave me:
a) VM reboot can be both internal/external, even triggered by customer within VM like restart.
b) Portal Reboot : Hardly anyone uses it until VM is stuck somewhere.
c) Portal Reimage: this is basically to get fresh copy of OS latched to VM.
d) In-Place Upgrade: this I am also not sure of what does this mean.  Could be App update?
e) Node Migration is when node is bad or container needs service healing to move to better node.
@dcbrown16, does this give you enough? I could also put you in touch with the dev if you need more clarification about the scenarios.

@RichardScheel thanks so much for following up. I was able to resolve the case in question with the information that, ultimately, one should not rely on having files persist on the local drives in a Cloud Service.
At this point my interest would be in clarifying the documentation so that customers can resolve their issues before coming to support. If nobody knows what "In-Place Upgrade" means, that seems like a major concern. If possible, I would like the table under "Impact to drive data during Cloud Service upgrades" updated to include descriptions of what each of these scenarios are.

@dcbrown16, I haven't had time to get back to this. Unfortunately, I will be leaving Microsoft in about a week due to medical issues, so I probably will not be able to get to this issue.
Our team hired a new contractor to fill my spot. His name is Pieter Wijsman. After he has a chance to ramp up, he might be able to help, but this is not an area he is familiar with. Sachin Mittal is a dev who knows quite a bit about this topic. However, he is critical path on an important project right now.

@RichardScheel Thank you for sharing the information. I have assigned the issue to Pieter Wijsman.

@RichardScheel thanks for following up and best wishes!
I imagine Cloud Services doesn't have a lot of resources being put into documentation at this point so I understand.
For me, the remaining action item is just to define the items under "Impact to drive data during Cloud Service upgrades" to the best of our knowledge. We have a good start in this thread but the "In-Place Upgrade" definition is particularly unclear so that's where I would start if possible, @v-piwijs. Thanks!

thanks @dcbrown16.   Reading through the thread, my plan is:

to find someone to define what an in-place upgrade is and add this definition to the page
to update the impact to drive data page, since your experience did not match the expectation that data on C: was preserved

The page owners is where I'll start

@Karishma-Tiwari-MSFT I am not the owner of the below page, could @jpconnock take care of updating the doc?   I can help in finding the right contacts in Cosine/Host.
cloud-services/cloud-services-update-azure-service#impact-to-drive-data-during-cloud-service-upgrades

@v-piwijs Thanks. I have assigned it to him.

@dcbrown16 thanks for the feedback on this. We have been having internal discussion on this for a while now.
I also want to point you to these docs
https://docs.microsoft.com/en-us/azure/virtual-machines/windows/maintenance-and-updates
https://docs.microsoft.com/en-us/azure/virtual-machines/troubleshooting/understand-vm-reboot
It goes over what causes a VM to reboot and talks about different types of maintenance. Since Cloud Services run on VMs both docs are relevant.
As per an in-place upgrade, that refers to when the OS version is updated. This does not mean for example from windows server 2012 to 2016 but rather a large 2012 update applied to the system. Such as we have had for Windows 10 quite a few times. These upgrades drastically change the OS but it is still consider the same version.
The in-place upgrade is not a scenario that many come in contact with as the platform will handle that for cloud services.
As per adding to this doc, we are continuing the discussion but at this time we don't feel we want to add any additional details to the doc. That being said, this comment will remain on the doc so if we see further traction on this issue we can always come back and revisit. Hope that helps.

@MicahMcKittrick-MSFT thanks, I'll maybe ping you internally if this comes up again for our team.

@dcbrown16 ping me anytime :)


Update quickstart.html

Fix v2.4.x~v2.5.x console producer script doesn't supports  --bootstrap-server option.
We should use --broker-list instead.
More detailed description of your change,
if necessary. The PR title and PR message become
the squashed commit message, so use a separate
comment to ping reviewers.
Summary of testing strategy (including rationale)
for the feature or bug fix. Unit and/or integration
tests are expected for any behaviour change and
system tests should be considered for larger changes.
Committer Checklist (excluded from commit message)

[x] Verify design and implementation
[x] Verify test coverage and CI build status
[x] Verify documentation (including upgrade notes)

In the quickstart, the 1st step we described is to download V2.5.0, and the following steps work well in V2.5.0. @tonytony2020 , could you try again with V2.5.0? Thanks.

I'm going to go ahead and close this. If we have missed something, please reopen and let us know.

In the quickstart, the 1st step we described is to download V2.5.0, and the following steps work well in V2.5.0. @tonytony2020 , could you try again with V2.5.0? Thanks.

Everything works well on v2.5.0, ignore me and this issue.


Start time milliseconds format is wrong.

1 second = 1000 milliseconds.
The extension allows only 2 digits for milliseconds.

Start Time feature will be soon replaced with a new extension called schedule URL which has much more options than just defining start time

This issue is fixed and available in DEV verion


Consider using SipHash instead of CityHash to protect against hash flooding attacks

Since CityHash (used by asbl::hash) has been shown to be weak with respect to hash flooding attacks (https://131002.net/siphash/siphashdos_appsec12_slides.pdf) it's worth considering replacing it with SipHash (https://131002.net/siphash/). SipHash seems to have received more security analysis than CityHash.

We are considering replacing CityHash, but not with SipHash, as the performance would suffer too much. We do randomize our hashes, which provides a good (but not perfect, as the slides show) default. I think if hash-flooding is a concern, you need to do a detailed threat analysis and decide if using a stronger hash function is good enough, or if you need to go further and use a different data structure altogether.


Issue to fix for the avitool

Hello all,
we need to have the avitool update with the min version as follow:
ansible==4.2.0
ansible-core==2.11.2
avisdk==20.1.6
certifi==2021.5.30
cffi==1.14.6
chardet==4.0.0
cryptography==3.4.7
idna==2.10
Jinja2==3.0.1
jmespath==0.10.0
MarkupSafe==2.0.1
packaging==21.0
pycparser==2.20
pyparsing==2.4.7
PyYAML==5.4.1
requests==2.25.1
resolvelib==0.5.4
urllib3==1.26.6

@itlinux Can you please provide some more details ?

No response so closing this.


ci: push to gh and npm registries

/canary-release

/canary-release

/canary-release

🎉 Canary Release build started

🎉 Canary Release build started

/canary-release

🎉 Canary Release build started

/canary-release

🎉 Canary Release build started

/canary-release

hello

hello

/canary-release

/canary-release

/canary-release

/canary-release

/canary-release

/canary-release


[IE Fix] OSF-3425 Prevent line breaks in file extension

Fix
The previous pull request (https://github.com/CenterForOpenScience/osf.io/pull/4501) was working on all browsers except for IE. This pull request is an attempt to fix the incompatibility issue with IE. The issue occurs because two CSS rules are conflicting in IE. To fix this, I changed the value of one of the rules.
http://stackoverflow.com/questions/18129005/white-space-nowrap-is-not-working-in-ie-in-a-horizontally-scrolling-box

Purpose
Currently, if the window is resized on a file page, there is a possibility of an "awkward" line break with the file name. This means that part of the file extension could be split and a .docx could be interpreted as a .doc.

Changes

Add a new CSS rule to the file-view-page.css file using the "file-ext" id
Modify the view_file.mako file so that it splits the file name into two parts: with and without extension
Apply the CSS id to the extension part

I'm not sure this is the right approach. If you only want to apply nowrap to the file extension and .break-word to the file name, why not surround those parts in a span and apply the proper classes rather than adding new CSS rules?
Something like:

      ## Split file name into two parts: with and without extension

            ${file_name_title | h}

        ${file_name_ext | h}

Pass finished.

Merged into release/0.61.0


Invert Issue (Suggested fix included)

Firstly, thank you for adding the Invert feature!
I noticed that fully black pixel values (0) were not getting inverted. I managed to fix it myself, here's the change:-
ImageUtility.cs Line 115
if (intensity > 0 & intensity <= 255)     {         if (invert) { intensity = 255 - intensity; }
The invert logic is only applied if greater than 0, because the corresponding else to this if does not invert
I fixed the invert by changing greater-than (>) to greater-than-or-equals (>=) ie if (intensity >= 0...

I'll patch it in on the afternoon.

Just wanted to let you know that while adding that fix is pretty much immediate, I'm going to also try to cram in this new image generation algorithm while I'm at it, which is presumably hundreds of times faster than what there is currently in place. Adding this second bit is likely going to be the bit that takes a while.

The new version with this fix has been uploaded, you can find it at:
https://github.com/heisarzola/multi-channel-image/releases/tag/V.1.2.0
I do have to admit that the main change (41e80a0314d1fe42caf235ebc00b8b968aefef55) had to do with the algorithm that generates the merged image, and the algorithm that extracts individual channels, so it's sped up dramatically compared to before though.
In case I totally missed the mark and the issue is still there, feel free to reopen this.


HttpRequest.MultiPart missing member 'name' and 'fileName' (when using Carthage)

I included Swifter 1.0.6 in my project using Carthage and then simply copied the server.POST["/upload"] block from demoServer.swift, but the line:
response += "Name: \(multipart.name) File name: \(multipart.fileName) Size: \(multipart.body.count)<br>" does not build.  I get unresolved identifier, "value of type 'HttpRequests.MultiPart' has no member 'fileName' " (and the same for .name).
Note that if I download the full source from GitHub, everything builds and runs just fine - the issue is only when I use Carthage to include Swifter in my project.  Lastly, I am new to both Xcode & swift, so if I am missing something stupid, please let me know what...

hi @Laban1
Thanks for the report. Multipart was not in 1.0.6 release. I've added is just now ( 1.0.7 ).
best
dk

Thanks, works fine now!!  Minor note: the Readme.md file still has 1.0.6 for Carthage.

@Laban1 thanks !


WhereGroup example in docs is wrong and old

err := db.NewSelect().
    Model(book).
    Where("title LIKE ?", "my%").
    WhereGroup(" AND ", func(q *bun.Query) *bun.Query {
        q = q.WhereOr("id = 1").
            WhereOr("id = 2")
        return q, nil
    }).
    Limit(1).
    Scan(ctx)

Above example in docs  is wrong https://bun.uptrace.dev/guide/queries.html#select

This can be modified to:
err := db.NewSelect().
    Model(book).
    Where("title LIKE ?", "my%").
    WhereGroup(" AND ", func(q *bun.SelectQuery) *bun.SelectQuery {
        q = q.WhereOr("id = 1").
            WhereOr("id = 2")
        return q
    }).
    Limit(1).
    Scan(ctx)

Should be fixed - thanks for the report.


does not work with github pages

Due to the cross-loading of a couple of assets (e.g., bootstrap), which is not allowed by Github Pages, this theme does not work with Github Pages.
Other than this issue, this theme is excellent. Is it possible to move these assets into the theme itself to expand the use cases a bit more?

Scratch that, just need to RTFM!


 Instead the business logic exception should come in the Temporal UI
Steps to Reproduce the Problem

Version a piece of code
Send an exception immediately after that line

Specifications

Version: 1.16
Platform: Java SDK

https://gist.github.com/hrishirc/68c6fcc23b7c943f858d91fe451f689a

any update on this?

any update on this?

This issue needs a reproduction or more information about the specific code structure causing it.
I wrote a test verifying the behavior of a simple getVersion + exception right after and verified that it passes against the current master and 1.16.0.

Closing for now as not enough information is here, if more is provided we can reopen


update littlefs2-sys bindgen dependency to 0.60

Per https://github.com/rust-lang/rust-bindgen/issues/2030, this seems to interact poorly with other bindgen dependents that also specify features = ["runtime"] (and perhaps other dependents that don't specify default-features = "false" at all).

Per the recommendation from @codysch in Slack, I've updated this crate's bindgen dependency to 0.60 instead of removing default-features = false. That's the version of bindgen we use elsewhere, and it enables cargo xtask build -t esp32s3 -p example-hummingbird-littlefs2 to succeed for me locally.
This change is a little less upstreamable than updating the bindgen dependency to the latest available version of bindgen (0.63), which is presumably what the maintainers would do if they were doing it themselves (and perhaps what they will request if we try to upstream this change).
If we instead update this crate's bindgen dependency to 0.63, then we'd need to either update the bindgen dependencies in JOSL crates to the same version or add an unused build-dependency on bindgen 0.63 in some JOSL crate to ensure feature unification when building this crate along with JOSL crates for esp32s3. I haven't done that for now.
@codysch, are you ok with this approach?

Agreed about updating to the latest bindgen everywhere.
Also worth noting, https://github.com/junelife/littlefs2-sys/commit/da42d4ea109d39d6eb9c86cbd064a86463bb80b7 suggests default features were disabled for bindgen to avoid enabling log/std, presumably for non-build dependencies, which is a problem that can now be solved by enabling the v2 Cargo resolver. So perhaps we can upstream a change that updates bindgen to 0.63, removes default-features = false, and sets resolver = "2" in the [package].


an analysis-synthesis example

So many stuff in the tutorials, but I can't find something like the analysis and synthesis of an existing wav file. I mean, given a wav file, first do an analysis of it and use the result of the analysis to synthesize a new wav file.

Hello, thanks for the nice suggestion.
I updated the tutorial book s1_demostration_hn-nsf.ipynb and s2_demonstration_music_nsf.ipynb in this newfunctions branch https://github.com/nii-yamagishilab/project-NN-Pytorch-scripts/tree/newfunctions/
In Section 2.2

Prepare input data: extract F0 and mel-spectrogram from input waveform
Generate sample: waveform synthesize given the extracted features.

The reason why not doing so is due to the complicated dependency on other libraries.
F0 extractor is the https://github.com/bjbschmitt/AMFM_decompy/blob/master/amfm_decompy/pYAAPT.py
Mel-spec extractor for music data is based on librosa
Mel-spec extractor for speech data is based on numpy (for historical reasons)
Please let me know whether they work on your computer.

Thanks for your quick response. Should I use sub_get_mel.py to compute the mel? Just want to make sure I use the same mel as your model training mels.

If you use the pre-trained speech model, then, yes, please use the mel from that tool so that the input mel is compatible with the mel in the training set.
Two ways to use it:

Load it as module, then use get_melsp() to extract the mel. This is how s1_demostration_hn-nsf.ipynb works;
Use it as a script to extract mel and save the mel as a file on the disk. The commandline is  $: python sub_get_mel.py PATH_INPUT_WAV PATH_OUTPUT_MEL

Finally, if you want to train a new model, of course, you can use any tool you prefer.


MSDKUI-1914: [Android] Improve guidance components layouts

Improved GuidanceManeueverView inner margin, Added several options in devapp for GuidanceManeuverview, NextManeuverView, EstimatedArrivalVIew
Signed-off-by: Vijay Yadav<EMAIL_ADDRESS>

Codecov Report

Merging #107 into master will increase coverage by 1.61%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##             master    #107      +/-   ##
===========================================
+ Coverage     73.09%   74.7%   +1.61%
+ Complexity     1641     995     -646
===========================================
  Files           129      69      -60
  Lines          5660    3938    -1722
  Branches        871     437     -434
===========================================
- Hits           4137    2942    -1195
+ Misses          855     749     -106
+ Partials        668     247     -421

Impacted Files
Coverage Δ
Complexity Δ

.../here/msdkui/guidance/GuidanceStreetLabelView.java
85% <100%> (+0.51%)
10 <2> (ø)
:arrow_down:

...e/msdkuiapp/routing/RoutingInstructionsFragment.kt

...java/com/here/msdkuiapp/common/PermissionsUtils.kt

.../com/here/msdkuiapp/routing/OptionPanelFragment.kt

...ere/msdkuiapp/routing/RouteManeuverListFragment.kt

.../here/msdkuiapp/routing/SubOptionPanelPresenter.kt

...m/here/msdkuiapp/routing/SubOptionPanelFragment.kt

...msdkuiapp/guidance/GuidanceNextManeuverFragment.kt

...com/here/msdkuiapp/routing/OptionPanelPresenter.kt

...m/here/msdkuiapp/position/AppPositioningManager.kt

... and 51 more

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 50b8036...753efa8. Read the comment docs.


Rebuild APK is bigger than original, from 30 MB to 65 MB

Information

Apktool Version (apktool -version) - 2.2.0
Operating System (Mac, Linux, Windows) - Windows
APK From? (Playstore, ROM, Other) - https://apkpure.com/heroes-charge/com.ucool.hero

I just decompile the apk, then recompile and the rebuild apk is so much bigger. From 30 MB jump to 65 MB, and I have this bug in some others apk also.

Can't be fixed currently. This APK has one extension (.ddx) that is sometimes deflated and sometimes stored.
Apktool previously wrote the absolute path to each file needed to be deflated, however that caused a problem due to applications much like this one that has a ton of files. This makes the generated command  far too long to execute, thus fails.
AAPT has update support so theoretically we could go back to absolute paths per compressed file and execute after we've hit ~50 files to keep the command low. However, our aapt code for executing the binary is currently expecting it to be ran once instead of x times.
Would be a large rewrite of the internal code that communicates with aapt. Marking this as a feature enhancement for the back burner.

Thank you very much for answering me.  Merging this into #1272
Same goal, one bug. A staged aapt execution for unknown files.


[WIP] Move default values in build.gradle for Android DRAFT WIP 1 - NOT WORKING

I tried to refactor the defaults all into one place back in April, did not seem to work for me.
These are old values, which have since been updated for React Native 0.59. This is also missing the enhancements proposed in PR #24…
I am raising this PR in hopes that someone can help me get this working.
/cc @SaeedZhiany

closing as outdated


<EMAIL_ADDRESS>

Coverage remained the same at 56.001% when pulling 27456bf8e5e065da43405e90cec58f1d162114df on<EMAIL_ADDRESS>into 7ac204a6c3fdd3e9facce65ab3e8c2c3db78c9d5 on master.

Coverage remained the same at 56.001% when pulling 27456bf8e5e065da43405e90cec58f1d162114df on<EMAIL_ADDRESS>into 7ac204a6c3fdd3e9facce65ab3e8c2c3db78c9d5 on master.


Fixed all references to the old docker-compose command to use newer 'docker compose'

#94 kept dc up from working. This PR fixes the issue.

The are some automation scripts in this repo that launch images that likely don't have the docker compose plugin, just the docker-compose command, so we should probably wait on this PR as part of a broader upgrade? Or to land sooner, do some sort of availability check?

I see now that this is only a partial fix for the src/docker folder and the rest of the repo has a lot of docker-compose instances. What if we did an environment / version specific alias in the build as part of a fix here when we do the entire repo, such as:
alias "docker-compose"="docker compose"

That way the old command will work if the build expects it, otherwise it won't? We could detect the docker-ce version.

maybe reuse what we have elsewhere as a stop gap: https://github.com/graphistry/graphistry/blob/9a93d7c90346b8cf35e16468ce8774645e0b16dd/compose/etc/scripts/migrate.sh#L159


Layout is not working as expected

Describe the bug
Centering StackPanel and then TextBlocks inside the StackPanel is not working as expected.
To Reproduce
Execute the minimal repro case: https://github.com/danipen/LayoutReproCase.git
Actual behavior
The text is not centered.

Expected behavior
The text is centered.

Desktop

OS: Windows
Version latest master

This seems to be a rendering issue. Measurements are updated properly.


Clear original response code in send_error_bucket function

If this is left intact, then apache thinks that this code was generated during processing of ErrorDocument and does not handle it properly
Fix #2849

Could this be merged? I can provide further help if needed.

FYI: We're using it on prod for 2 months on several huge sites

I haven't had opportunity to do a detailed analysis of this.
It looks simple, but this is the type of change that could potentially have unintended consequences -- perhaps only for some configurations and/or use cases.
Some questions that spring to mind immediately:

why is the new line of code setting status to a hard-coded 200, when the assignment to status_line (just above the new code) has been set using the status value passed in to the function?
is 200 really always the correct setting here? What if the original response was some other non-error response code like 301?

I haven't had opportunity to do a detailed analysis of this.
It looks simple, but this is the type of change that could potentially have unintended consequences -- perhaps only for some configurations and/or use cases.
Some questions that spring to mind immediately:
* why is the new line of code setting status to a hard-coded 200, when the assignment to status_line (just above the new code) has been set using the status value passed in to the function?

I admit it seemed strange to me as well but fortunately i described the breaking point in #2849, so let me clarify.
There is a code in Apache httpd which assumes that when ap_die function is called and request record contains status code other than 200, then this error code was encountered while trying to access custom response URL. Setting response code to 200 here has in fact no effect on the final response because just after the check for recursive error, original response code gets overwritten by the output of filter.
r->status = type;

* is 200 really always the correct setting here? What if the original response was some other non-error response code like 301?

I think so, because it looks to me that send_error_bucket is used only when mod_security wants to change status code of the response and if the original status code, so it does not matter what the old response code was.
Please correct me if i am wrong.

Hi @martinhsv ,
Just wanted to check in on my pull request - any updates or plans to merge it? Thanks!
Please let me know if there are further actions required from my side.

Hi @TomasKorbar ,
No imminent plans. As I suggested previously, I'd need to gain higher confidence of the correctness of this change before merging. In the meantime, the PR is available for anyone who wishes to merge in their own environment to make use of it.


freerdp_set_last_error ERRCONNECT_AUTHENTICATION_FAILED [0x00020009]

Hello,
I am trying to connect to my work computer which is on an azure RD gateway. When I try to connect I get the following errors:
[16:09:11:672] [26659:26660] [INFO][com.freerdp.client.common.cmdline] - loading channelEx cliprdr
[16:09:12:075] [26659:26660] [ERROR][com.freerdp.core.gateway.rpc] - error! Status Code: 401
[16:09:12:075] [26659:26660] [ERROR][com.freerdp.core.gateway.http] - HTTP/1.1 401 Unauthorized
[16:09:12:075] [26659:26660] [ERROR][com.freerdp.core.gateway.http] - Content-Type: text/plain
[16:09:12:075] [26659:26660] [ERROR][com.freerdp.core.gateway.http] - Server: Microsoft-IIS/8.5
[16:09:12:075] [26659:26660] [ERROR][com.freerdp.core.gateway.http] - WWW-Authenticate: Negotiate
[16:09:12:075] [26659:26660] [ERROR][com.freerdp.core.gateway.http] - WWW-Authenticate: NTLM
[16:09:12:075] [26659:26660] [ERROR][com.freerdp.core.gateway.http] - WWW-Authenticate: Basic realm="psyterm.psy.fsu.edu"
[16:09:12:075] [26659:26660] [ERROR][com.freerdp.core.gateway.http] - Date: Mon, 01 Jan 2018 21:09:12 GMT
[16:09:12:075] [26659:26660] [ERROR][com.freerdp.core.gateway.http] - Content-Length: 13
[16:09:12:075] [26659:26660] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_AUTHENTICATION_FAILED [0x00020009]
[16:09:12:075] [26659:26660] [ERROR][com.freerdp.core.gateway.tsg] - tsg_check failure
[16:09:12:076] [26659:26660] [ERROR][com.freerdp.core.nego] - Protocol Security Negotiation Failure
[16:09:12:076] [26659:26660] [ERROR][com.freerdp.core.connection] - Error: protocol security negotiation or connection failure
I have tried both the old 1.1 version on Linux Mint's software manager and the 2.0 12/30/17 nightly build. I am assuming this is a bug but maybe I am missing something?
Thanks,
Shawn

I tried specifying only the gateway and computer name and entered gateway information when prompted and got this instead:
[16:41:36:874] [28239:28240] [ERROR][com.freerdp.core.gateway.rpc] - RPC Fault PDU:
[16:41:36:874] [28239:28240] [ERROR][com.freerdp.core.gateway.rpc] - status: E_PROXY_TS_CONNECTFAILED (0x800759DD)
[16:41:36:874] [28239:28240] [ERROR][com.freerdp.core.gateway.tsg] - tsg_check failure
[16:41:36:875] [28239:28240] [ERROR][com.freerdp.core.nego] - Protocol Security Negotiation Failure
[16:41:36:875] [28239:28240] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_SECURITY_NEGO_CONNECT_FAILED [0x0002000C]
[16:41:36:875] [28239:28240] [ERROR][com.freerdp.core.connection] - Error: protocol security negotiation or connection failure

Do #4547 or #4539 fix your issue?

Hello,
do you have found a solution on this problème ?
Because i have the same problem but i do not find the solution.

Hi everybody,
I'm tying to switch to Linux as my daily driver.
Is all quite new to me so you could call me a noob.
So far I've managed to get things working exept rdp with the sam error as described in this topic.
The administrator told me to use MS or MAC but I don really trust those companies.
I hope you can help me out because #4547 and #4539 raise more questions for me than awnsers.
Thanks in advance :-)

Nevermind,
Found the solution, just use the ms.rdp file instead of manually filling in the connection.
Then I made a little Bash script to launch it.

This issue is closed due to no feedback from reporter. However I'm experiencing this issue now and would like to assist in getting it fixed.
I have tried both the nightly build and also tried building from source with no effect. Please let me know how I can help.
Current output:
[16:25:44:882] [20647:20648] [INFO][com.freerdp.client.common.cmdline] - loading channelEx cliprdr
[16:25:44:889] [20647:20648] [INFO][com.freerdp.client.x11] - Property 334 does not exist
GatewayPassword:
[16:25:50:658] [20647:20648] [INFO][com.freerdp.core.gateway.rdg] - RD Gateway does not support HTTP transport.
[16:25:50:990] [20647:20648] [ERROR][com.freerdp.core.gateway.rpc] - error! Status Code: 401
[16:25:50:990] [20647:20648] [ERROR][com.freerdp.core.gateway.http] - HTTP/1.1 401 Unauthorized
[16:25:50:990] [20647:20648] [ERROR][com.freerdp.core.gateway.http] - Content-Type: text/plain
[16:25:50:990] [20647:20648] [ERROR][com.freerdp.core.gateway.http] - Server: Microsoft-IIS/7.5
[16:25:50:990] [20647:20648] [ERROR][com.freerdp.core.gateway.http] - WWW-Authenticate: Negotiate
[16:25:50:990] [20647:20648] [ERROR][com.freerdp.core.gateway.http] - WWW-Authenticate: NTLM
[16:25:50:990] [20647:20648] [ERROR][com.freerdp.core.gateway.http] - WWW-Authenticate: Basic
[16:25:50:990] [20647:20648] [ERROR][com.freerdp.core.gateway.http] - X-Powered-By: ASP.NET
[16:25:50:990] [20647:20648] [ERROR][com.freerdp.core.gateway.http] - Date: Sun, 05 Aug 2018 14:25:49 GMT
[16:25:50:990] [20647:20648] [ERROR][com.freerdp.core.gateway.http] - Content-Length: 13
[16:25:50:990] [20647:20648] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_AUTHENTICATION_FAILED [0x00020009]
[16:25:50:990] [20647:20648] [ERROR][com.freerdp.core.gateway.tsg] - tsg_check failure
helge@Modalen:~/Source/FreeRDP$


Can I upload Lottie json files with this library?

Hello,
When using library for animations, a json file has to be loaded per animation.
I can put that json file inside Assets.xcassets
Is there any way to use R.string to load that json file from the assets?
Or do I have to put the file outside and use:
https://github.com/mac-cain13/R.swift/blob/master/Documentation/Examples.md#resource-files
Thanks a lot.

I haven't used Lottie recently, but the last time I used it, I placed the json files in some directory and used it like so:
LOTAnimationView(name: R.file.moreJson.name)

Closing due to inactivity.
Feel free to leave further comments on this issue.


CSS are not adapted in nz-form.

Reproduction link
https://stackblitz.com/edit/ng-zorro-antd-button-v9-0-0-beta-3-ttj2o7
Steps to reproduce
NZ-form is used to build the form.
What is expected?
The stylesheet is correctly adapted in the form.
What is actually happening?
The following error occurs and NgZorro's style is not adapted.
WARNING: sanitizing unsafe style value [object Object] (see http://g.co/ng/security#xss).

Environment
Info

ng-zorro-antd
9.0.0-beta.3

Browser
Chrome80

Sample code is available in stackblitz. Please check it out. You can also check for errors.

@wenqi73  try using [ngStyle] directive instead of [style]

closed via #5081