icudt_EFIGS.dat blocked by firewall #89073

socreative · 2023-07-18T10:22:24Z

We have integrated the dotnet.js Wasm runtime (.NET 8) into our existing Angular front-end app but we're having issue with the icudt_EFIGS.dat file being blocked by the firewall.

Failed to load resource: the server responded with a status of 403 (forbidden)

Is there a workaround for this? A way to use another extension for that file maybe?

The text was updated successfully, but these errors were encountered:

am11 · 2023-07-18T10:45:23Z

One approach is to use custom file https://www.meziantou.net/reducing-blazor-application-size-by-providing-custom-icu-data.htm#use-custom-icu-data (e.g. by downloading the prebuilt file in on your build server and pointing to it in:
<Target Name="UseCustomICU" AfterTargets="ResolveRuntimePackAssets">).

radical · 2023-07-18T14:36:49Z

cc @ilonatommy @maraf

ghost · 2023-07-18T14:37:03Z

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

We have integrated the dotnet.js Wasm runtime (.NET 8) into our existing Angular front-end app but we're having issue with the icudt_EFIGS.dat file being blocked by the firewall.

Failed to load resource: the server responded with a status of 403 (forbidden)

Is there a workaround for this? A way to use another extension for that file maybe?

Author:	socreative
Assignees:	-
Labels:	`arch-wasm`, `untriaged`, `area-Build-mono`, `needs-area-label`
Milestone:	-

ts-indikaf · 2023-07-18T14:58:27Z

I'm also having the same issue. I followed the instructions in @am11's link and created a custom icudt_EFIGS.dat file but getting the following build errors in dotnet8 preview6. The main difference between the link and my project is that mine is a pure Dotnet Wasm project created using WebAssembly Browser App template and so using Microsoft.NET.Sdk not Microsoft.NET.Sdk.BlazorWebAssembly as in the example.

PS C:.....\CalcEngine.Csharp> dotnet build -c release
MSBuild version 17.7.0+5785ed5c2 for .NET
Determining projects to restore...
Restored C:....\CalcEngine.csproj (in 181 ms).
C:\Program Files\dotnet\sdk\8.0.100-preview.6.23330.14\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.RuntimeIdentifierInference.targets(314,5): message NETSDK1057: You are using a preview version of .NET. See: https://aka.ms/dotnet-support-policy [
C:....\CalcEngine.csproj]
C:....\CalcEngine.csproj(13,5): error MSB4036: The "ReferenceCopyLocalPaths" task was not found. Check the following:
1.) The name of the task in the project file is the same as the name of the task class.
2.) The task class is "public" and implements the Microsoft.Build.Framework.ITask interface.
3.) The task is correctly declared with UsingTask in the project file, or in the *.tasks files located in the "C:\Program
Files\dotnet\sdk\8.0.100-preview.6.23330.14" directory.

Build FAILED.

C:... \CalcEngine.csproj(13,5): error MSB4036: The "ReferenceCopyLocalPaths" task was not found. Check the following:
1.) The name of the task in the project file is the same as the name of the task class.
2.) The task class is "public" and implements the Microsoft.Build.Framework.ITask interface.
3.) The task is correctly declared with UsingTask in the project file, or in the *.tasks files located in the "C:\Program
Files\dotnet\sdk\8.0.100-preview.6.23330.14" directory.
0 Warning(s)
1 Error(s)

maraf · 2023-07-18T15:30:07Z

@ts-indikaf The ReferenceCopyLocalPaths needs to be put in <ItemGroup>, because it is an item collection.

ilonatommy · 2023-07-18T15:51:58Z

We have integrated the dotnet.js Wasm runtime (.NET 8) into our existing Angular front-end app but we're having issue with the icudt_EFIGS.dat file being blocked by the firewall.

Does it also happen for full ICU (icudt.dat)? To switch on full ICU, add <WasmIncludeFullIcuData>true</WasmIncludeFullIcuData> to pure wasm browser app or <BlazorWebAssemblyLoadAllGlobalizationData>true</BlazorWebAssemblyLoadAllGlobalizationData> to Blazor wasm app.

ts-indikaf · 2023-07-18T15:56:31Z

@maraf thanks. Build works now.
However, I have two versions of icudt_EFIGS.dat files after the build. Build copies my custom file into the browser-wasm folder and the dotnet generated files is in browser-wasm\AppBundle folder.

We are looking for a solution similar to packaging .dll as .wasm using WebCil provided by the dotnet8. ie. Is there a way to get rid of *.dat files?

@ilonatommy firewall blocks all .DAT files in my case so switching to full icudt.dat isn't a solution.

ilonatommy · 2023-07-18T16:04:45Z

Is there a workaround for this? A way to use another extension for that file maybe?

The only other extension that ICU theoretically supports is .so / .dll. Before we investigate this option: would your firewall block it as well?

ts-indikaf · 2023-07-18T21:05:08Z

@ilonatommy .so files are okay but .dll are blocked. Thanks

maraf · 2023-07-19T07:58:48Z

@ts-indikaf I have created a sample that uses custom extension for ICU using some of the new APIs added in .NET 8 https://github.com/maraf/dotnet-wasm-rename-icu

It doesn't change the content/structure of ICU files like webcil does for assemblies, it only changes the extenion

ts-indikaf · 2023-07-20T13:55:15Z

@maraf - Many thanks for the solution. Unfortunately, it throws the following run time error from the dotnet.js file. I'm on dotnet8 preview6 and I have installed wasm-tools as well.

However, following your idea, we can temporally unblock ourselves with a manual hack but renaming the file extension is not going to be a permanent solution for us.

maraf · 2023-07-20T16:37:24Z

@ts-indikaf Can you share a simple repro?

ts-indikaf · 2023-07-21T10:44:06Z

@maraf here is a simple test repo https://github.com/ts-indikaf/dotnet-wasm-rename-icu

I compared the two projects and the only difference I can see is that they are referencing dotnet.js file from two difference locations.
Your project:
https://github.com/maraf/dotnet-wasm-rename-icu/blob/16a74033bff4391eec23ca52dfd46eed786ffab1/main.js#L4C1-L4C48
import { dotnet } from './_framework/dotnet.js'
This throws 404 but can be fixed by removing _framework folder name in the path.

My project created using WebAssembly Browser app template in VS 2022 v17.6.5:
https://github.com/ts-indikaf/dotnet-wasm-rename-icu/blob/7668ab91799b948fbf5667bf5f485e4e9ce0b79d/main.js#L4
import { dotnet } from './dotnet.js'

Both projects are throwing the following error even with the correct dotnet.js path.

maraf · 2023-07-25T20:05:07Z

@ts-indikaf Oh, sorry. In preview6 using loadBootResource doesn't work correctly. Can you wait for preview7?

ts-indikaf · 2023-07-26T07:15:54Z

@maraf yes, no problem. thanks.
Can we also think about a better solution rather than renaming .dat files as some firewalls, if content scanning is on, could still block them?

maraf · 2023-07-26T09:14:07Z

It is a quite complicated. One possible solution could be providing a single file bundle #86162, or delivering the runtime in preinitialized state (with all/some data already loaded in wasm memory). Another one could be wrapping icu the same/similar way as we do for webcil (but webcil for dlls probably helped by removing PE headers). AFAIK we don't have other reports of blocking ICU data files, because of the content

maraf · 2023-07-26T12:18:24Z

Also, in .NET 8 the common bits of SDK and startup has been unified with Blazor and so this setup (with slight modifications) should work https://devblogs.microsoft.com/dotnet/custom-deployment-layout-for-blazor-webassembly-apps/. It would allow you to wrap icu in some envelope or bundle it together with other assets and than extract it during startup.

ghost · 2023-07-27T20:48:15Z

This issue has been marked needs-author-action and may be missing some important information.

socreative · 2023-08-02T11:08:49Z

@maraf thanks for your reply. We're using pure WebAssembly, not Blazor though

socreative · 2023-09-08T10:10:11Z

@maraf
What particularly do you need to modify? Are those required by integration into Angular or are they valid even standalone?

Upon the inititialisattion in our angular app dotnet.js tries to fetch all files from the filesystem. I added additional method to rewrite URLs for and fetch all files from the server

maraf · 2023-09-08T10:44:10Z

Upon the inititialisattion in our angular app dotnet.js tries to fetch all files from the filesystem. I added additional method to rewrite URLs for and fetch all files from the server

Can you please create a simple repro to share? Is webpack involved on dotnet.js?

ghost · 2023-09-08T10:44:28Z

This issue has been marked needs-author-action and may be missing some important information.

ts-indikaf · 2023-09-08T13:46:57Z

@maraf

Q: Would the RunAOTCompilation = true work with dotnet publish command in DotNet8?

A: Yes, it does. Do you have any problems with it?

This is a screenshot of a project created using Console Wasm template in DotNet8 - preview7. It has only the basic template code. See the error in red.

Yes, the scenario outside of Blazor is fully supported. You can reach to use here, we provide fixes for servicing releases, etc. What exactly do you mean by "DevOps pipeline level"?

Currently, DevOps pipeline build fails - probably due to the preview version. I'd like to make sure pipeline builds are fully supported for Wasm projects in the DotNet8 LTS release?

socreative · 2023-09-11T08:17:38Z

Upon the inititialisattion in our angular app dotnet.js tries to fetch all files from the filesystem. I added additional method to rewrite URLs for and fetch all files from the server

Can you please create a simple repro to share? Is webpack involved on dotnet.js?

yeah we're using Angular CLI and it uses Webpack under the hood. I am creating an example repo for you. Will post the link when done

socreative · 2023-09-11T10:17:34Z

@maraf Here's a demo repo with using Angular + Webpack to initialise the dotnet runtime environment.
https://github.com/socreative/angular-dotnet

Note that I have to use custom webpack config to create fallbacks for node's process and module (see webpack.config.ts)

When you run the app have a look in browser devtools to see that it's trying to fetch blazor.boot.json from the filesystem
(see the URL - file:///...)

Also, to enable dynamic importing in dotnet.js using webpack I have to directly modify dotnet.js file to make it possible with webpack, like so

[import($.runtimeModuleUrl),import($.nativeModuleUrl)]

edited to

[import(/* webpackIgnore: true / $.runtimeModuleUrl),import(/ webpackIgnore: true */ $.nativeModuleUrl)]

maraf · 2023-09-12T11:18:05Z

You should omit dotnet files from bundling with webpack. I was investigating integration with react/webpack last year https://github.com/maraf/dotnet-wasm-react and the rest was that until we have a single file solution #86162, there isn't a good way to integrate with it, as it rewrites all imports and URLs in sources. We have this sample that bundles dotnet files with webpack, but it requires extra configuration https://github.com/dotnet/runtime/tree/d67314ee8018b27748a8d0a1f4e38172ff680599/src/mono/sample/wasm/browser-webpack

We have all imports annotated in sources to be ignored by webpack, but they might get dropped when the runtime is built in release configuration. I'll investigate it

runtime/src/mono/wasm/runtime/loader/run.ts

Line 389 in d67314e

const process = await import(/* webpackIgnore: true */"process");

ts-indikaf · 2023-09-27T06:21:02Z

@maraf any updates on RunAOTCompilation issue as mentioned above? I get the same error with the dotnet8 RC1. I also notice that publish command outputs .dll files not .wasm extension.

maraf · 2023-10-01T16:49:13Z

@ts-indikaf Sorry for late reply, I was OOF. I wasn't able to reproduce the error with Preview 7 nor RC1. Can you please share a binlog? https://github.com/dotnet/project-system-tools#getting-higher-fidelity-logs-from-vs-vs2022-onwards

ghost · 2023-10-01T16:49:29Z

This issue has been marked needs-author-action and may be missing some important information.

ts-indikaf · 2023-10-02T09:49:49Z

@maraf No worries.
I installed DotNet8 RC1 and created a new project using the WebAssembly Browser App template. Still getting the same error.

Environment:
Dotnet8 RC1, VS 17.7.4

Project configs.

  <PropertyGroup>
    <TargetFramework>net8.0</TargetFramework>
    <RuntimeIdentifier>browser-wasm</RuntimeIdentifier>
    <OutputType>Exe</OutputType>
    <AllowUnsafeBlocks>true</AllowUnsafeBlocks>
    <RunAOTCompilation>true</RunAOTCompilation>
  </PropertyGroup>

dotnet publish -c release output

MSBuild version 17.8.0-preview-23418-03+0125fc9fb for .NET
MSBuild logs and debug information will be at "C:\WORKING\Repo\Web Assembly\DotNet8rc1PublishTest\binlogs"
  Determining projects to restore...
  Restored C:\WORKING\Repo\Web Assembly\DotNet8rc1PublishTest\DotNet8rc1PublishTest.csproj (in 3.31 sec).
C:\Program Files\dotnet\sdk\8.0.100-rc.1.23463.5\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.RuntimeIdentifierInference.targets(311,5): message NETSDK1057: You are using
 a preview version of .NET. See: https://aka.ms/dotnet-support-policy [C:\WORKING\Repo\Web Assembly\DotNet8rc1PublishTest\DotNet8rc1PublishTest.csproj]
  DotNet8rc1PublishTest -> C:\WORKING\Repo\Web Assembly\DotNet8rc1PublishTest\bin\Release\net8.0\browser-wasm\DotNet8rc1PublishTest.dll
  Optimizing assemblies for size. This process might take a while.
  DotNet8rc1PublishTest -> C:\WORKING\Repo\Web Assembly\DotNet8rc1PublishTest\bin\Release\net8.0\browser-wasm\publish\
  DotNet8rc1PublishTest -> C:\WORKING\Repo\Web Assembly\DotNet8rc1PublishTest\bin\Release\net8.0\browser-wasm\DotNet8rc1PublishTest.dll
  DotNet8rc1PublishTest -> C:\WORKING\Repo\Web Assembly\DotNet8rc1PublishTest\bin\Release\net8.0\browser-wasm\publish\
  AOT'ing 4 assemblies
  [aot-instances.dll] Exec (with response file contents expanded) in C:\WORKING\Repo\Web Assembly\DotNet8rc1PublishTest\obj\Release\net8.0\browser-wasm\wasm\for-publish\a
  ot-in: MONO_PATH=C:\WORKING\Repo\Web Assembly\DotNet8rc1PublishTest\obj\Release\net8.0\browser-wasm\wasm\for-publish\aot-in;C:\Program Files\dotnet\packs\Microsoft.NETC
  ore.App.Runtime.Mono.browser-wasm\8.0.0-rc.1.23419.4\runtimes\browser-wasm\native\;C:\Program Files\dotnet\packs\Microsoft.NETCore.App.Runtime.Mono.browser-wasm\8.0.0-r
  c.1.23419.4\runtimes\browser-wasm\lib\net8.0 MONO_ENV_OPTIONS= C:\Program Files\dotnet\packs\Microsoft.NETCore.App.Runtime.AOT.win-x64.Cross.browser-wasm\8.0.0-rc.1.234
  19.4\Sdk\..\tools\mono-aot-cross.exe --wasm-exceptions --debug --llvm "--aot=no-opt,static,direct-icalls,deterministic,mattr=simd,dwarfdebug,llvm-path=C:\Program Files\
  dotnet\packs\Microsoft.NET.Runtime.Emscripten.3.1.34.Sdk.win-x64\8.0.0-rc.1.23415.5\tools\bin\,static,dedup-include=aot-instances.dll,llvmonly,interp,asmonly,llvm-outfi
  le=C:\WORKING\Repo\Web Assembly\DotNet8rc1PublishTest\obj\Release\net8.0\browser-wasm\wasm\for-publish\aot-instances.dll.bc.tmp,temp-path=C:\WORKING\Repo\Web Assembly\D
  otNet8rc1PublishTest\obj\Release\net8.0\browser-wasm\wasm\for-publish\aot-instances.dll.tmp" C:\WORKING\Repo\Web Assembly\DotNet8rc1PublishTest\obj\Release\net8.0\brows
  er-wasm\wasm\for-publish\aot-in\DotNet8rc1PublishTest.dll C:\WORKING\Repo\Web Assembly\DotNet8rc1PublishTest\obj\Release\net8.0\browser-wasm\wasm\for-publish\aot-in\Sys
  tem.Console.dll C:\WORKING\Repo\Web Assembly\DotNet8rc1PublishTest\obj\Release\net8.0\browser-wasm\wasm\for-publish\aot-in\System.Private.CoreLib.dll C:\WORKING\Repo\We
  b Assembly\DotNet8rc1PublishTest\obj\Release\net8.0\browser-wasm\wasm\for-publish\aot-in\System.Runtime.InteropServices.JavaScript.dll C:\WORKING\Repo\Web Assembly\DotN
  et8rc1PublishTest\obj\Release\net8.0\browser-wasm\wasm\for-publish\aot-in\aot-instances.dll

#### ERROR STRTS HERE #######

C:\Program Files\dotnet\packs\Microsoft.NET.Runtime.WebAssembly.Sdk\8.0.0-rc.1.23419.4\Sdk\WasmApp.Native.targets(681,5): error : Precompiling failed for C:\WORKING\Repo\
Web Assembly\DotNet8rc1PublishTest\obj\Release\net8.0\browser-wasm\wasm\for-publish\aot-in\aot-instances.dll with exit code 1. [C:\WORKING\Repo\Web Assembly\DotNet8rc1Pub
lishTest\DotNet8rc1PublishTest.csproj]
C:\Program Files\dotnet\packs\Microsoft.NET.Runtime.WebAssembly.Sdk\8.0.0-rc.1.23419.4\Sdk\WasmApp.Native.targets(681,5): error : Can not open image C:\WORKING\Repo\Web [
C:\WORKING\Repo\Web Assembly\DotNet8rc1PublishTest\DotNet8rc1PublishTest.csproj]

#### ERROR ENDS HERE #######

  [1/5] DotNet8rc1PublishTest.dll -> DotNet8rc1PublishTest.dll.bc

Binlog zip file
binlogs.zip

ilonatommy · 2023-10-02T09:53:53Z

This might be connected with #92335. Could you place your project in a path with no spaces? I mean C:\WORKING\Repo\Web Assembly\DotNet8rc1PublishTest\DotNet8rc1PublishTest.csproj -> C:\WORKING\Repo\WebAssembly\DotNet8rc1PublishTest\DotNet8rc1PublishTest.csproj

maraf · 2023-10-02T10:32:39Z

Confirmed on windows

project with space in path/name
publish + aot

ts-indikaf · 2023-10-02T10:34:30Z

@ilonatommy @maraf yes, that was the issue. Thanks!

maraf · 2023-10-02T12:48:06Z

I'm going to close this issue as the original topic is resolved and tracked in different issue.
Please feel free to reopen this one or open new issue if you find more questions

ts-indikaf · 2023-10-02T17:51:33Z

@ts-indikaf Oh, sorry. In preview6 using loadBootResource doesn't work correctly. Can you wait for preview7?

@maraf @ilonatommy Thanks for helping out with the AOT compilation issue.

Original issue is half fixed though. ie. .dat file renaming works and they are .icu files now in AppBundle\_framework folder but main.js throws a run time error in my sample browser app in DotNet8 RC1.

maraf · 2023-10-03T07:25:59Z

The withStartupOptions was removed in RC1 and replaced with withResourceLoader, please see

runtime/src/mono/wasm/runtime/dotnet.d.ts

Line 93 in 82fee26

    
           withResourceLoader(loadBootResource?: LoadBootResourceCallback): DotnetHostBuilder;

ts-indikaf · 2023-10-03T08:25:24Z

@maraf thanks for your help.

dotnet run -c release/debug works fine. However, dotnet publish -c release fails.

PS C:\WORKING\Repo\WebAssembly\DotNet8rc1PublishTest> dotnet publish -c release
MSBuild version 17.8.0-preview-23418-03+0125fc9fb for .NET
  Determining projects to restore...
  Restored C:\WORKING\Repo\WebAssembly\DotNet8rc1PublishTest\DotNet8rc1PublishTest.csproj (in 321 ms).
C:\Program Files\dotnet\sdk\8.0.100-rc.1.23463.5\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.RuntimeIdentifierInference.targets(311,5): message NETSDK1057: You are using
 a preview version of .NET. See: https://aka.ms/dotnet-support-policy [C:\WORKING\Repo\WebAssembly\DotNet8rc1PublishTest\DotNet8rc1PublishTest.csproj]
  DotNet8rc1PublishTest -> C:\WORKING\Repo\WebAssembly\DotNet8rc1PublishTest\bin\Release\net8.0\browser-wasm\DotNet8rc1PublishTest.dll
MSBUILD : warning MSB5029: The value "\**\*.dat" of the "Include" attribute in element <ItemGroup> in file "C:\WORKING\Repo\WebAssembly\DotNet8rc1PublishTest\DotNet8rc1Pu
blishTest.csproj (20,17)" is a wildcard that results in enumerating all files on the drive, which was likely not intended. Check that referenced properties are always def
ined. [C:\WORKING\Repo\WebAssembly\DotNet8rc1PublishTest\DotNet8rc1PublishTest.csproj]

**** ERROR *****
C:\WORKING\Repo\WebAssembly\DotNet8rc1PublishTest\DotNet8rc1PublishTest.csproj(24,5): error MSB3680: The source file "\**\*.dat" does not exist.

socreative · 2023-10-03T11:39:11Z

Yes, the issue still persists

maraf · 2023-10-03T15:55:49Z

You are missing the "root" path to start looking for ICU files in $(OutputPath)\**\*.dat https://github.com/maraf/dotnet-wasm-rename-icu/blob/main/WasmRenameIcu.csproj#L18

ts-indikaf · 2023-10-03T17:47:53Z

@maraf that's great. Thanks again.

Maybe you want to update the ReadMe file per project configs, for future reference? Just a suggestion. Unfortunately, I cannot update and push it into your repo due to access restrictions.

maraf · 2023-10-03T17:53:26Z

PR is welcome 🙂, or I'll come back to that sample later

ts-indikaf · 2023-10-03T17:57:54Z

I actually tried to update myself but had a permission issue - still the same. You can do it later - no hurry :)

dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Jul 18, 2023

ghost added the untriaged New issue has not been triaged by the area owner label Jul 18, 2023

radical added arch-wasm WebAssembly architecture area-Build-mono labels Jul 18, 2023

radical removed the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Jul 18, 2023

lewing assigned maraf Jul 21, 2023

lewing added this to the 8.0.0 milestone Jul 21, 2023

ghost removed the untriaged New issue has not been triaged by the area owner label Jul 21, 2023

maraf added the needs-author-action An issue or pull request that requires more info or actions from the author. label Jul 27, 2023

ghost added needs-further-triage Issue has been initially triaged, but needs deeper consideration or reconsideration and removed needs-author-action An issue or pull request that requires more info or actions from the author. labels Aug 2, 2023

ghost removed the needs-author-action An issue or pull request that requires more info or actions from the author. label Sep 8, 2023

maraf added the needs-author-action An issue or pull request that requires more info or actions from the author. label Sep 8, 2023

ghost removed the needs-author-action An issue or pull request that requires more info or actions from the author. label Sep 11, 2023

maraf added the needs-author-action An issue or pull request that requires more info or actions from the author. label Oct 1, 2023

maraf mentioned this issue Oct 2, 2023

[wasm] Fix AOT for projects with space in path/name #92880

Closed

maraf closed this as completed Oct 2, 2023

ghost locked as resolved and limited conversation to collaborators Nov 2, 2023

icudt_EFIGS.dat blocked by firewall #89073

icudt_EFIGS.dat blocked by firewall #89073

Comments

socreative commented Jul 18, 2023

am11 commented Jul 18, 2023

radical commented Jul 18, 2023

ghost commented Jul 18, 2023

ts-indikaf commented Jul 18, 2023 • edited Loading

maraf commented Jul 18, 2023

ilonatommy commented Jul 18, 2023

ts-indikaf commented Jul 18, 2023 • edited Loading

ilonatommy commented Jul 18, 2023 • edited Loading

ts-indikaf commented Jul 18, 2023

maraf commented Jul 19, 2023 • edited Loading

ts-indikaf commented Jul 20, 2023 • edited Loading

maraf commented Jul 20, 2023

ts-indikaf commented Jul 21, 2023 • edited Loading

maraf commented Jul 25, 2023

ts-indikaf commented Jul 26, 2023

maraf commented Jul 26, 2023

maraf commented Jul 26, 2023

ghost commented Jul 27, 2023

socreative commented Aug 2, 2023

socreative commented Sep 8, 2023 • edited Loading

maraf commented Sep 8, 2023

ghost commented Sep 8, 2023

ts-indikaf commented Sep 8, 2023 • edited Loading

socreative commented Sep 11, 2023

socreative commented Sep 11, 2023

maraf commented Sep 12, 2023

ts-indikaf commented Sep 27, 2023

maraf commented Oct 1, 2023

ghost commented Oct 1, 2023

ts-indikaf commented Oct 2, 2023 • edited Loading

ilonatommy commented Oct 2, 2023 • edited Loading

maraf commented Oct 2, 2023

ts-indikaf commented Oct 2, 2023

maraf commented Oct 2, 2023

ts-indikaf commented Oct 2, 2023 • edited Loading

maraf commented Oct 3, 2023

ts-indikaf commented Oct 3, 2023 • edited Loading

socreative commented Oct 3, 2023

maraf commented Oct 3, 2023 • edited Loading

ts-indikaf commented Oct 3, 2023

maraf commented Oct 3, 2023

ts-indikaf commented Oct 3, 2023

ts-indikaf commented Jul 18, 2023 •

edited

Loading

ts-indikaf commented Jul 18, 2023 •

edited

Loading

ilonatommy commented Jul 18, 2023 •

edited

Loading

maraf commented Jul 19, 2023 •

edited

Loading

ts-indikaf commented Jul 20, 2023 •

edited

Loading

ts-indikaf commented Jul 21, 2023 •

edited

Loading

socreative commented Sep 8, 2023 •

edited

Loading

ts-indikaf commented Sep 8, 2023 •

edited

Loading

ts-indikaf commented Oct 2, 2023 •

edited

Loading

ilonatommy commented Oct 2, 2023 •

edited

Loading

ts-indikaf commented Oct 2, 2023 •

edited

Loading

ts-indikaf commented Oct 3, 2023 •

edited

Loading

maraf commented Oct 3, 2023 •

edited

Loading