a package issue with v6.3.0

ERROR in ./node_modules/vscode/dist/service-override/languageDetectionWorker.js 7:79-156
Module not found: Error: Can't resolve<EMAIL_ADDRESS>in '/node_modules/vscode/dist/service-override'
resolve<EMAIL_ADDRESS>in '/node_modules/vscode/dist/service-override'
  Parsed request is a module
  using description file: /node_modules/vscode/package.json (relative path: ./dist/service-override)
    using description file: /node_modules/vscode/package.json (relative path<EMAIL_ADDRESS>      no extension
<EMAIL_ADDRESS>doesn't exist
      .js
<EMAIL_ADDRESS>doesn't exist
      as directory
<EMAIL_ADDRESS>doesn't exist
    resolve as module
      /node_modules/vscode/dist/service-override/node_modules doesn't exist or is not a directory
      looking for modules in /node_modules/vscode/dist/node_modules
        /node_modules/vscode/dist/node_modules/@vscode/vscode-languagedetection doesn't exist
      /node_modules/vscode/node_modules doesn't exist or is not a directory
      /node_modules/node_modules doesn't exist or is not a directory
      looking for modules in /node_modules
        /node_modules/@vscode/vscode-languagedetection doesn't exist
      /Desktop/DevelopmentApps/node_modules doesn't exist or is not a directory
      /Desktop/node_modules doesn't exist or is not a directory
      looking for modules in /node_modules
        /node_modules/@vscode/vscode-languagedetection doesn't exist
      /Users/node_modules doesn't exist or is not a directory
      /node_modules doesn't exist or is not a directory
 @ ./node_modules/monaco-languageclient/lib/monaco-vscode-api-services.js 104:46-103
 @ ./node_modules/monaco-languageclient/lib/index.js 6:0-48 6:0-48
 @ ./public/javascripts/monacoLangClientLoader.js 4:0-59 4:0-59

ERROR in ./node_modules/vscode/dist/service-override/languageDetectionWorker.js 8:89-176
Module not found: Error: Can't resolve<EMAIL_ADDRESS>in '/node_modules/vscode/dist/service-override'
resolve<EMAIL_ADDRESS>in '/node_modules/vscode/dist/service-override'
  Parsed request is a module
  using description file: /node_modules/vscode/package.json (relative path: ./dist/service-override)
    using description file: /node_modules/vscode/package.json (relative path<EMAIL_ADDRESS>      no extension
<EMAIL_ADDRESS>doesn't exist
      .js
<EMAIL_ADDRESS>doesn't exist
      as directory
<EMAIL_ADDRESS>doesn't exist
    resolve as module
      /node_modules/vscode/dist/service-override/node_modules doesn't exist or is not a directory
      looking for modules in /node_modules/vscode/dist/node_modules
        /node_modules/vscode/dist/node_modules/@vscode/vscode-languagedetection doesn't exist
      /node_modules/vscode/node_modules doesn't exist or is not a directory
      /node_modules/node_modules doesn't exist or is not a directory
      looking for modules in /node_modules
        /node_modules/@vscode/vscode-languagedetection doesn't exist
      /Desktop/DevelopmentApps/node_modules doesn't exist or is not a directory
      /Desktop/node_modules doesn't exist or is not a directory
      looking for modules in /node_modules
        /node_modules/@vscode/vscode-languagedetection doesn't exist
      /Users/node_modules doesn't exist or is not a directory
      /node_modules doesn't exist or is not a directory
 @ ./node_modules/monaco-languageclient/lib/monaco-vscode-api-services.js 104:46-103
 @ ./node_modules/monaco-languageclient/lib/index.js 6:0-48 6:0-48
 @ ./public/javascripts/monacoLangClientLoader.js 4:0-59 4:0-59

webpack 5.88.2 compiled with 2 errors in 18084 ms

Got the above error after upgrading to v6.3.0
any suggestions?
@CGNonofr

Hi @OliverwengFiltered
npm list (version 9.6.7) resolves this from the monaco-languageclient package:

Which package manager are you using?

Hi @kaisalmen
I'm using yarn.
this is the list I get from yarn. (I don't have @codingame/monaco-vscode-api@1.80.2), I had to install  xterms and vscode-oniguruma and vscode-textmate etc on my end manually. which means, probably I have to install the vscode-languagedetection on my end manually too.
any insights why yarn package manager doesn't install monaco-vscode-api ?
<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  │  └─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  └─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  │  └─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  │  └─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  └─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  └─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  └─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  └─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  └─<EMAIL_ADDRESS>

@OliverwengFiltered vscode is defined as "vscode": "npm<EMAIL_ADDRESS>and it npm installs all its peerDependencies automatically. Did you define the "vscode" dependency?

Hi @kaisalmen
I did not define vscode on my end manually, assuming that it's defined in monaco-languageclient already as a peer dependency.

@OliverwengFiltered ok, it is just how yarn prints it. It is the correct dependency as toposort is a direct dependency of monaco-vscode-api. Is it possible to instruct yarn to install peerDependencies if they aren't fulfilled. npm's default behaviour is exactly that since a couple of major versions.

@kaisalmen
this should be all set, I completely dumped the yarn, I have switched back to npm, which solved the problem.


Error when I use the plugin

dyld: Library not loaded: libgit2.21.dylib
Referenced from: /usr/local/bin/gitql
Reason: image not found
[1]    56160 abort      gitql "select message from commits"
I'm on Mac OSX

Hi @piclemx .
Did you exported the DYLD_LIBRARY_PATH environment variable ?

Yes

Actually that export variable DYLD_LIBRARY_PATH step should be mentioned before the make step under installation section in README.md. make for me failed at first attempt then i set that DYLD_LIBRARY_PATH variable then make step worked fine for me.

@piclemx there are other thread trying to make the installation easily.
Can you help us with a test?
I did a commit and you could follow the steps
cd $GOPATH/src/github.com/cloudson/gitql/
cp libgit2/install/lib/lib*  /usr/local/lib
gitql

It solves your problem?

It seems to be duplicated from https://github.com/cloudson/gitql/issues/30 @piclemx, take a look

@cloudson Yes this is working 👍

Sweet, @piclemx, could you close this issue? :)

Done ;)


Can you provide the best parameters for each dataset?

Can you provide the best parameters for each dataset?

And semantic descriptor for each dataset？Thank you very much.

If can,thank you very much.

Hi, @mrzhu666 ! Thanks for your interest in our work!
We are collecting the parameters for each dataset, and we will release the parameters as soon as possible.
Best wishes!

@Hanzy1996 Do you have a plan for when to release the best hyperparameters that can reproduce the reported results?

I am sorry for the delay in releasing the parameters. Maybe I can firstly share with you some key parameters:
manualSeed：AWA1&2 (9182), FLO (806), SUN (4115)
nz=attSize
manualSeed：AWA1(1800) AWA2 (2400), FLO (600), SUN (100)
nhza: AWA1&2(2048), FLO (1024), SUN (1024)
ins_weight: AWA1&2(0.001), FLO (0,01), SUN (0,01)
cls_weight: AWA1&2(o.001), FLO (0.01), SUN (0,01)

@Hanzy1996 does nhza correspond to --nhF?
In manualSeed (second entry) you mean --syn_num, right?

@webcsm Sorry for the mistake. Yes, much appreciation for your remind. I have correct my comments.

@Hanzy1996 you don't mention in the paper but in the code I see it's possible to run a preprocessing or standardization step. Did you use any of those to obtain the results?

Hi, @webcsm . In the code, I only use the preprocessing step on all datasets and conduct the MinMax normalization on the visual features. Sorry for the missing in the paper.

Thank you, @Hanzy1996 . No worries. I'm running one experiment on AWA1 with the parameters you provided.

Hi @Hanzy1996 do you have an idea of the number of epochs you used? My first experiment with AWA1 showed that 2k epochs (the default value) was not enough. I'm resuming training now with 4k epochs to see if the generator converges.
These are the parameters I used:
INFO:root:Namespace(attSize=85, batch_size=4096, beta1=0.5, class_embedding='att', classifier_lr=0.001, cls_temp=0.1, cls_weight=0.001, critic_iter=5, cuda=True, dataroot='xlsa17', dataset='AWA1', embedSize=2048, gpus='0', gzsl=False, image_embedding='res101', ins_temp=0.1, ins_weight=0.001, lambda1=10, lr=0.0001, lr_dec_rate=0.99, lr_decay_epoch=100, manualSeed=3483, matdataset=True, nclass_all=50, nclass_seen=40, ndh=4096, nepoch=2000, ngh=4096, nhF=2048, nz=85, outzSize=512, preprocessing=True, resSize=2048, standardization=False, syn_num=1800, validation=False, workers=2)

I guess my question is: what was your stopping criteria for the training?

Hi, @webcsm , for AWA1, I take about 150 epochs to achieve the best results.
For these hyper-parameters, I tune them based on the performance on the validation set. For more details about splitting the validation set, please refer to [1].
With the tuned hyper-parameter, I re-train the model from the scratch with the entire training set from seen classes and take the generator end the embedding function when the fake loss (fake_ins_contras_loss and cls_loss_fake) converges.
[1] Yongqin Xian, Christoph H. Lampert, Bernt Schiele, and Zeynep Akata. Zero-Shot Learning - A Comprehensive Evaluation of the Good, the Bad and the Ugly. TPAMI, 2018.

thank you @Hanzy1996 for your time and patience. Now I understood the whole flow so I can reproduce the experiments. I'm still getting a convergence for the fake losses around epoch 350, and not 150. What was the logic? Like a delta loss < threshold for a given number of epochs?

This gives me worse results than the ones reported (63% for ZSL for example). Could you confirm the parameter for AWA1?
attSize=85
batch_size=4096
beta1=0.5
class_embedding='att'
classifier_lr=0.001
cls_temp=0.1
cls_weight=0.001
critic_iter=5
cuda=True
dataroot='xlsa17'
dataset='AWA1'
embedSize=2048
gpus='0'
gzsl=False
image_embedding='res101'
ins_temp=0.1
ins_weight=0.001
lambda1=10
lr=0.0001
lr_dec_rate=0.99
lr_decay_epoch=100
manualSeed=3483
matdataset=True
nclass_all=50
nclass_seen=40
ndh=4096
nepoch=2000
ngh=4096
nhF=2048
nz=85
outzSize=512
preprocessing=True
resSize=2048
standardization=False
syn_num=1800
validation=False
workers=2

Hi @Hanzy1996 , I can only kind of reproduce the results if I consider the minimum loss of the generator as my stopping criteria.

Could you provide the full params for all datasets? I find I can not achieve the reported results with

I am sorry for the delay in releasing the parameters. Maybe I can firstly share with you some key parameters:
manualSeed：AWA1&2 (9182), FLO (806), SUN (4115) nz=attSize syn_num：AWA1(1800) AWA2 (2400), FLO (600), SUN (100) nhF: AWA1&2(2048), FLO (1024), SUN (1024) ins_weight: AWA1&2(0.001), FLO (0,01), SUN (0,01) cls_weight: AWA1&2(0.001), FLO (0.01), SUN (0,01)

Could you provide the full params for all datasets? I find I can not achieve the reported results with those parameters.

Hi, @zhihou7! I think these are all the required parameters, and other parameters are basically the same for each dataset Could you please show the logs and all the parameters you used?

Could you please provide the full best parameters of FLO dataset? I can't reproduce the optimal result on this data set. Thank you！

For example, on SUN dataset, I train the network as follow,
python CE_GZSL.py --dataset SUN --nepoch 300 --class_embedding att --syn_num 100 --batch_size 768 --attSize 102 --nz 102 \

--embedSize 2048 --outzSize 512 --nhF 1024 --ins_weight 0.01 --cls_weight 0.01 --ins_temp 0.1 --cls_temp 0.1
--manualSeed 4115 --nclass_all 717 --nclass_seen 645
I can only achieve 40.0%, though I have used early stop strategy.
But on SUN dataset, I can achieve better performance than the reported.

Thank you very much for your reply.  We are students and are following up on this paper.  Have you tried the APY dataset on this framework?  If so, is it convenient to provide the hyperparameters?
At 2022-03-15 16:51:02, "zhihou7" @.***> wrote:
For example, on SUN dataset, I train the network as follow,
python CE_GZSL.py --dataset SUN --nepoch 300 --class_embedding att --syn_num 100 --batch_size 768 --attSize 102 --nz 102 \
--embedSize 2048 --outzSize 512 --nhF 1024 --ins_weight 0.01 --cls_weight 0.01 --ins_temp 0.1 --cls_temp 0.1
--manualSeed 4115 --nclass_all 717 --nclass_seen 645
I can only achieve 40.0%, though I have used early stop strategy.
But on SUN dataset, I can achieve better performance than the reported.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you commented.Message ID: @.***>

hi, @zhihou7, the experiments on SUN may not need the early stop strategy. I have updated the epochs each dataset needs here.


Add: Methods for CommandPosition

Add: Methods for CommandPosition, and an example

Thanks for your contribution
This looks very useful!


Add RE Engine

SteamDB app page links to a few games using this
Resident Evil 7: Biohazard
Resident Evil 2
Devil May Cry 5
Resident Evil 3
Resident Evil: Resistance
Capcom Arcade Stadium
Ghosts 'n Goblins Resurrection
Monster Hunter Rise
Resident Evil Village
Capcom Arcade 2nd Stadium
Resident Evil Re:Verse
Resident Evil 4
Street Fighter 6
Exoprimal
Brief explanation of the change
Added a rule for Capcom's in-house engine called RE Engine

Looks good to me, thanks for the PR!


React native 0.64 build error

Describe the bug
When building the application in App center I'm facing the below bug. I'm using React Native 0.64
Environment (please complete the following information):
React Native:
What react-native-track-player version are you using? - "react-native-track-player": "^1.2.3",
Are you testing on a real device or in the simulator? Which OS version are you running? - Everything builds fine locally however facing it when building in App center I get the below
Code
Jetifier is deprecated. Future versions of react-native CLI may not run it by default.
Jetifier found 1274 file(s) to forward-jetify. Using 3 workers...
 Future versions of react-native CLI may not run it by default.

##[error]Jetifier: propose an AndroidX conversion PR to this repository: node_modules/react-native-track-player/android/src/main/java/com/guichaguri/trackplayer/module/MusicModule.java

##[error]Jetifier: propose an AndroidX conversion PR to this repository: node_modules/react-native-track-player/android/src/main/java/com/guichaguri/trackplayer/module/MusicModule.java

##[error]Jetifier: propose an AndroidX conversion PR to this repository: node_modules/react-native-track-player/android/src/main/java/com/guichaguri/trackplayer/service/Utils.java

##[error]Jetifier: propose an AndroidX conversion PR to this repository: node_modules/react-native-track-player/android/src/main/java/com/guichaguri/trackplayer/service/Utils.java

##[error]Jetifier: propose an AndroidX conversion PR to this repository: node_modules/react-native-track-player/android/src/main/java/com/guichaguri/trackplayer/service/metadata/ButtonEvents.java

##[error]Jetifier: propose an AndroidX conversion PR to this repository: node_modules/react-native-track-player/android/src/main/java/com/guichaguri/trackplayer/service/metadata/ButtonEvents.java

##[error]Jetifier: propose an AndroidX conversion PR to this repository: node_modules/react-native-track-player/android/src/main/java/com/guichaguri/trackplayer/service/metadata/MetadataManager.java

##[error]Jetifier: propose an AndroidX conversion PR to this repository: node_modules/react-native-track-player/android/src/main/java/com/guichaguri/trackplayer/service/metadata/MetadataManager.java

##[error]Jetifier: propose an AndroidX conversion PR to this repository: node_modules/react-native-track-player/android/src/main/java/com/guichaguri/trackplayer/service/metadata/MetadataManager.java

##[error]Jetifier: propose an AndroidX conversion PR to this repository: node_modules/react-native-track-player/android/src/main/java/com/guichaguri/trackplayer/service/metadata/MetadataManager.java

##[error]Jetifier: propose an AndroidX conversion PR to this repository: node_modules/react-native-track-player/android/src/main/java/com/guichaguri/trackplayer/service/models/Track.java

##[error]Jetifier: propose an AndroidX conversion PR to this repository: node_modules/react-native-track-player/android/src/main/java/com/guichaguri/trackplayer/service/models/Track.java

##[error]Jetifier: propose an AndroidX conversion PR to this repository: node_modules/react-native-track-player/android/src/main/java/com/guichaguri/trackplayer/service/models/Track.java

##[error]Jetifier: propose an AndroidX conversion PR to this repository: node_modules/react-native-track-player/android/src/main/java/com/guichaguri/trackplayer/service/models/Track.java

##[error]Jetifier: propose an AndroidX conversion PR to this repository: node_modules/react-native-track-player/android/src/main/java/com/guichaguri/trackplayer/service/player/ExoPlayback.java

Is this issue still relevant for the main (v2) branch?

Closing this issue as there was no further feedback.


Pytorch转Onnx错误

我尝试使用export_det.py转化ultralytics官方给的yolov8s.pt模型，但转化出来的onnx模型与你提供的onnx模型结构有差异
本项目提供的：

我转化的：

可以看到在接近输出端的时候，多了一个constantofshape的输入

你转的是batch=2的吗？那你可能需要改 export.py 中 torch.onnx.export 的传参

这是我用的命令，batch应该是设置的是1
python3 export-det.py \ --weights yolov8s.pt \ --iou-thres 0.65 \ --conf-thres 0.25 \ --topk 100 \ --opset 11 \ --input-shape 1 3 640 640

这是我用的命令，batch应该是设置的是1
`python3 export-det.py \
--weights yolov8s.pt \
--iou-thres 0.65 \
--conf-thres 0.25 \
--topk 100 \
--opset 11 \
--input-shape 1 3 640 640`

加一个--sim

Tensorrt： <IP_ADDRESS>
cuda 11.4
输入模型: 官方模型yolov8s.pt
平台：Jetson Orin Nano
问题：engine推理结果不对
流程：pt 转onnx
python3 export-det.py --weights yolov8s.pt --sim

YOLOv8s summary (fused): 168 layers, 11156544 parameters, 0 gradients, 28.6 GFLOPs
WARNING: The shape inference of TRT::EfficientNMS_TRT type is missing, so it may result in wrong shape inference for the exported graph. Please consider adding it in symbolic function.
WARNING: The shape inference of TRT::EfficientNMS_TRT type is missing, so it may result in wrong shape inference for the exported graph. Please consider adding it in symbolic function.
WARNING: The shape inference of TRT::EfficientNMS_TRT type is missing, so it may result in wrong shape inference for the exported graph. Please consider adding it in symbolic function.
WARNING: The shape inference of TRT::EfficientNMS_TRT type is missing, so it may result in wrong shape inference for the exported graph. Please consider adding it in symbolic function.
WARNING: The shape inference of TRT::EfficientNMS_TRT type is missing, so it may result in wrong shape inference for the exported graph. Please consider adding it in symbolic function.
WARNING: The shape inference of TRT::EfficientNMS_TRT type is missing, so it may result in wrong shape inference for the exported graph. Please consider adding it in symbolic function.
WARNING: The shape inference of TRT::EfficientNMS_TRT type is missing, so it may result in wrong shape inference for the exported graph. Please consider adding it in symbolic function.
WARNING: The shape inference of TRT::EfficientNMS_TRT type is missing, so it may result in wrong shape inference for the exported graph. Please consider adding it in symbolic function.
WARNING: The shape inference of TRT::EfficientNMS_TRT type is missing, so it may result in wrong shape inference for the exported graph. Please consider adding it in symbolic function.
WARNING: The shape inference of TRT::EfficientNMS_TRT type is missing, so it may result in wrong shape inference for the exported graph. Please consider adding it in symbolic function.
WARNING: The shape inference of TRT::EfficientNMS_TRT type is missing, so it may result in wrong shape inference for the exported graph. Please consider adding it in symbolic function.
WARNING: The shape inference of TRT::EfficientNMS_TRT type is missing, so it may result in wrong shape inference for the exported graph. Please consider adding it in symbolic function.
 Attempting to cast down to INT32.
[08/29/2023-19:39:08] [W] [TRT] onnx2trt_utils.cpp:403: One or more weights outside the range of INT32 was clamped
[08/29/2023-19:39:08] [I] [TRT] MatMul_268: broadcasting input1 to make tensors conform, dims(input0)=[1,4,8400,16][NONE] dims(input1)=[1,1,16,1][NONE].
[08/29/2023-19:39:08] [I] [TRT] No importer registered for op: EfficientNMS_TRT.  Profiling results in this builder pass will not be stored.
[08/29/2023-19:40:24] [W] [TRT] Tactic Device request: 161MB Available: 154MB. Device memory is insufficient to use tactic.
[08/29/2023-19:40:24] [W] [TRT] Skipping tactic 0 due to insufficient memory on requested size of 161 detected for tactic 0x00000000000003e8.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:40:24] [W] [TRT] Tactic Device request: 161MB Available: 153MB. Device memory is insufficient to use tactic.
[08/29/2023-19:40:24] [W] [TRT] Skipping tactic 1 due to insufficient memory on requested size of 161 detected for tactic 0x00000000000003ea.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:40:24] [W] [TRT] Tactic Device request: 161MB Available: 153MB. Device memory is insufficient to use tactic.
[08/29/2023-19:40:24] [W] [TRT] Skipping tactic 2 due to insufficient memory on requested size of 161 detected for tactic 0x0000000000000000.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:40:25] [W] [TRT] Tactic Device request: 260MB Available: 152MB. Device memory is insufficient to use tactic.
[08/29/2023-19:40:25] [W] [TRT] Skipping tactic 0 due to insufficient memory on requested size of 260 detected for tactic 0x00000000000003e8.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:40:25] [W] [TRT] Tactic Device request: 260MB Available: 152MB. Device memory is insufficient to use tactic.
[08/29/2023-19:40:25] [W] [TRT] Skipping tactic 1 due to insufficient memory on requested size of 260 detected for tactic 0x00000000000003ea.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:40:25] [W] [TRT] Tactic Device request: 260MB Available: 152MB. Device memory is insufficient to use tactic.
[08/29/2023-19:40:25] [W] [TRT] Skipping tactic 2 due to insufficient memory on requested size of 260 detected for tactic 0x0000000000000000.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:40:27] [W] [TRT] Tactic Device request: 175MB Available: 157MB. Device memory is insufficient to use tactic.
[08/29/2023-19:40:27] [W] [TRT] Skipping tactic 0 due to insufficient memory on requested size of 175 detected for tactic 0x00000000000003e8.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:40:27] [W] [TRT] Tactic Device request: 175MB Available: 157MB. Device memory is insufficient to use tactic.
[08/29/2023-19:40:27] [W] [TRT] Skipping tactic 1 due to insufficient memory on requested size of 175 detected for tactic 0x00000000000003ea.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:40:27] [W] [TRT] Tactic Device request: 175MB Available: 157MB. Device memory is insufficient to use tactic.
[08/29/2023-19:40:27] [W] [TRT] Skipping tactic 2 due to insufficient memory on requested size of 175 detected for tactic 0x0000000000000000.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:40:36] [W] [TRT] Tactic Device request: 166MB Available: 164MB. Device memory is insufficient to use tactic.
[08/29/2023-19:40:36] [W] [TRT] Skipping tactic 0 due to insufficient memory on requested size of 166 detected for tactic 0x00000000000003e8.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:40:36] [W] [TRT] Tactic Device request: 166MB Available: 164MB. Device memory is insufficient to use tactic.
[08/29/2023-19:40:36] [W] [TRT] Skipping tactic 1 due to insufficient memory on requested size of 166 detected for tactic 0x00000000000003ea.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:40:36] [W] [TRT] Tactic Device request: 166MB Available: 165MB. Device memory is insufficient to use tactic.
[08/29/2023-19:40:36] [W] [TRT] Skipping tactic 2 due to insufficient memory on requested size of 166 detected for tactic 0x0000000000000000.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:40:38] [W] [TRT] Tactic Device request: 166MB Available: 165MB. Device memory is insufficient to use tactic.
[08/29/2023-19:40:38] [W] [TRT] Skipping tactic 0 due to insufficient memory on requested size of 166 detected for tactic 0x00000000000003e8.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:40:38] [W] [TRT] Tactic Device request: 166MB Available: 165MB. Device memory is insufficient to use tactic.
[08/29/2023-19:40:38] [W] [TRT] Skipping tactic 1 due to insufficient memory on requested size of 166 detected for tactic 0x00000000000003ea.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:40:38] [W] [TRT] Tactic Device request: 166MB Available: 165MB. Device memory is insufficient to use tactic.
[08/29/2023-19:40:38] [W] [TRT] Skipping tactic 2 due to insufficient memory on requested size of 166 detected for tactic 0x0000000000000000.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:40:39] [W] [TRT] Tactic Device request: 229MB Available: 165MB. Device memory is insufficient to use tactic.
[08/29/2023-19:40:39] [W] [TRT] Skipping tactic 0 due to insufficient memory on requested size of 229 detected for tactic 0x00000000000003e8.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:40:39] [W] [TRT] Tactic Device request: 229MB Available: 165MB. Device memory is insufficient to use tactic.
[08/29/2023-19:40:39] [W] [TRT] Skipping tactic 1 due to insufficient memory on requested size of 229 detected for tactic 0x00000000000003ea.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:40:39] [W] [TRT] Tactic Device request: 229MB Available: 165MB. Device memory is insufficient to use tactic.
[08/29/2023-19:40:39] [W] [TRT] Skipping tactic 2 due to insufficient memory on requested size of 229 detected for tactic 0x0000000000000000.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:40:44] [W] [TRT] Tactic Device request: 166MB Available: 163MB. Device memory is insufficient to use tactic.
[08/29/2023-19:40:44] [W] [TRT] Skipping tactic 0 due to insufficient memory on requested size of 166 detected for tactic 0x00000000000003e8.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:40:44] [W] [TRT] Tactic Device request: 166MB Available: 163MB. Device memory is insufficient to use tactic.
[08/29/2023-19:40:44] [W] [TRT] Skipping tactic 1 due to insufficient memory on requested size of 166 detected for tactic 0x00000000000003ea.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:40:44] [W] [TRT] Tactic Device request: 166MB Available: 163MB. Device memory is insufficient to use tactic.
[08/29/2023-19:40:44] [W] [TRT] Skipping tactic 2 due to insufficient memory on requested size of 166 detected for tactic 0x0000000000000000.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:40:46] [W] [TRT] Tactic Device request: 166MB Available: 163MB. Device memory is insufficient to use tactic.
[08/29/2023-19:40:46] [W] [TRT] Skipping tactic 0 due to insufficient memory on requested size of 166 detected for tactic 0x00000000000003e8.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:40:46] [W] [TRT] Tactic Device request: 166MB Available: 163MB. Device memory is insufficient to use tactic.
[08/29/2023-19:40:46] [W] [TRT] Skipping tactic 1 due to insufficient memory on requested size of 166 detected for tactic 0x00000000000003ea.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:40:46] [W] [TRT] Tactic Device request: 166MB Available: 163MB. Device memory is insufficient to use tactic.
[08/29/2023-19:40:46] [W] [TRT] Skipping tactic 2 due to insufficient memory on requested size of 166 detected for tactic 0x0000000000000000.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:40:47] [W] [TRT] Tactic Device request: 213MB Available: 164MB. Device memory is insufficient to use tactic.
[08/29/2023-19:40:47] [W] [TRT] Skipping tactic 0 due to insufficient memory on requested size of 213 detected for tactic 0x00000000000003e8.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:40:47] [W] [TRT] Tactic Device request: 213MB Available: 164MB. Device memory is insufficient to use tactic.
[08/29/2023-19:40:47] [W] [TRT] Skipping tactic 1 due to insufficient memory on requested size of 213 detected for tactic 0x00000000000003ea.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:40:47] [W] [TRT] Tactic Device request: 213MB Available: 164MB. Device memory is insufficient to use tactic.
[08/29/2023-19:40:47] [W] [TRT] Skipping tactic 2 due to insufficient memory on requested size of 213 detected for tactic 0x0000000000000000.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:41:29] [W] [TRT] Tactic Device request: 2108MB Available: 218MB. Device memory is insufficient to use tactic.
[08/29/2023-19:41:29] [W] [TRT] Skipping tactic 3 due to insufficient memory on requested size of 2108 detected for tactic 0x0000000000000004.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:41:29] [W] [TRT] Tactic Device request: 2108MB Available: 215MB. Device memory is insufficient to use tactic.
[08/29/2023-19:41:29] [W] [TRT] Skipping tactic 8 due to insufficient memory on requested size of 2108 detected for tactic 0x000000000000003c.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:41:29] [W] [TRT] Tactic Device request: 2108MB Available: 215MB. Device memory is insufficient to use tactic.
[08/29/2023-19:41:29] [W] [TRT] Skipping tactic 13 due to insufficient memory on requested size of 2108 detected for tactic 0x0000000000000074.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:41:31] [W] [TRT] Tactic Device request: 541MB Available: 201MB. Device memory is insufficient to use tactic.
[08/29/2023-19:41:31] [W] [TRT] Skipping tactic 3 due to insufficient memory on requested size of 541 detected for tactic 0x0000000000000004.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:41:31] [W] [TRT] Tactic Device request: 541MB Available: 201MB. Device memory is insufficient to use tactic.
[08/29/2023-19:41:31] [W] [TRT] Skipping tactic 9 due to insufficient memory on requested size of 541 detected for tactic 0x000000000000003c.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:41:32] [W] [TRT] Tactic Device request: 541MB Available: 201MB. Device memory is insufficient to use tactic.
[08/29/2023-19:41:32] [W] [TRT] Skipping tactic 15 due to insufficient memory on requested size of 541 detected for tactic 0x0000000000000074.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:41:34] [W] [TRT] Tactic Device request: 538MB Available: 201MB. Device memory is insufficient to use tactic.
[08/29/2023-19:41:34] [W] [TRT] Skipping tactic 3 due to insufficient memory on requested size of 538 detected for tactic 0x0000000000000004.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:41:35] [W] [TRT] Tactic Device request: 538MB Available: 201MB. Device memory is insufficient to use tactic.
[08/29/2023-19:41:35] [W] [TRT] Skipping tactic 9 due to insufficient memory on requested size of 538 detected for tactic 0x000000000000003c.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:41:35] [W] [TRT] Tactic Device request: 538MB Available: 198MB. Device memory is insufficient to use tactic.
[08/29/2023-19:41:35] [W] [TRT] Skipping tactic 15 due to insufficient memory on requested size of 538 detected for tactic 0x0000000000000074.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:42:18] [W] [TRT] Tactic Device request: 3160MB Available: 184MB. Device memory is insufficient to use tactic.
[08/29/2023-19:42:18] [W] [TRT] Skipping tactic 3 due to insufficient memory on requested size of 3160 detected for tactic 0x0000000000000004.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:42:19] [W] [TRT] Tactic Device request: 3160MB Available: 184MB. Device memory is insufficient to use tactic.
[08/29/2023-19:42:19] [W] [TRT] Skipping tactic 8 due to insufficient memory on requested size of 3160 detected for tactic 0x000000000000003c.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:42:19] [W] [TRT] Tactic Device request: 3160MB Available: 184MB. Device memory is insufficient to use tactic.
[08/29/2023-19:42:19] [W] [TRT] Skipping tactic 13 due to insufficient memory on requested size of 3160 detected for tactic 0x0000000000000074.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:42:25] [W] [TRT] Tactic Device request: 2102MB Available: 174MB. Device memory is insufficient to use tactic.
[08/29/2023-19:42:25] [W] [TRT] Skipping tactic 3 due to insufficient memory on requested size of 2102 detected for tactic 0x0000000000000004.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:42:25] [W] [TRT] Tactic Device request: 2102MB Available: 174MB. Device memory is insufficient to use tactic.
[08/29/2023-19:42:25] [W] [TRT] Skipping tactic 8 due to insufficient memory on requested size of 2102 detected for tactic 0x000000000000003c.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:42:25] [W] [TRT] Tactic Device request: 2102MB Available: 174MB. Device memory is insufficient to use tactic.
[08/29/2023-19:42:25] [W] [TRT] Skipping tactic 13 due to insufficient memory on requested size of 2102 detected for tactic 0x0000000000000074.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:42:26] [W] [TRT] Tactic Device request: 532MB Available: 171MB. Device memory is insufficient to use tactic.
[08/29/2023-19:42:26] [W] [TRT] Skipping tactic 3 due to insufficient memory on requested size of 532 detected for tactic 0x0000000000000004.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:42:27] [W] [TRT] Tactic Device request: 532MB Available: 171MB. Device memory is insufficient to use tactic.
[08/29/2023-19:42:27] [W] [TRT] Skipping tactic 9 due to insufficient memory on requested size of 532 detected for tactic 0x000000000000003c.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:42:27] [W] [TRT] Tactic Device request: 532MB Available: 171MB. Device memory is insufficient to use tactic.
[08/29/2023-19:42:27] [W] [TRT] Skipping tactic 15 due to insufficient memory on requested size of 532 detected for tactic 0x0000000000000074.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:42:29] [W] [TRT] Tactic Device request: 531MB Available: 171MB. Device memory is insufficient to use tactic.
[08/29/2023-19:42:29] [W] [TRT] Skipping tactic 3 due to insufficient memory on requested size of 531 detected for tactic 0x0000000000000004.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:42:29] [W] [TRT] Tactic Device request: 531MB Available: 171MB. Device memory is insufficient to use tactic.
[08/29/2023-19:42:29] [W] [TRT] Skipping tactic 9 due to insufficient memory on requested size of 531 detected for tactic 0x000000000000003c.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:42:29] [W] [TRT] Tactic Device request: 531MB Available: 171MB. Device memory is insufficient to use tactic.
[08/29/2023-19:42:29] [W] [TRT] Skipping tactic 15 due to insufficient memory on requested size of 531 detected for tactic 0x0000000000000074.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:01] [W] [TRT] Tactic Device request: 2123MB Available: 171MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:01] [W] [TRT] Skipping tactic 3 due to insufficient memory on requested size of 2123 detected for tactic 0x0000000000000004.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:01] [W] [TRT] Tactic Device request: 2123MB Available: 169MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:01] [W] [TRT] Skipping tactic 8 due to insufficient memory on requested size of 2123 detected for tactic 0x000000000000003c.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:01] [W] [TRT] Tactic Device request: 2123MB Available: 169MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:01] [W] [TRT] Skipping tactic 13 due to insufficient memory on requested size of 2123 detected for tactic 0x0000000000000074.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:03] [W] [TRT] Tactic Device request: 535MB Available: 168MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:03] [W] [TRT] Skipping tactic 3 due to insufficient memory on requested size of 535 detected for tactic 0x0000000000000004.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:03] [W] [TRT] Tactic Device request: 535MB Available: 166MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:03] [W] [TRT] Skipping tactic 9 due to insufficient memory on requested size of 535 detected for tactic 0x000000000000003c.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:03] [W] [TRT] Tactic Device request: 535MB Available: 166MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:03] [W] [TRT] Skipping tactic 15 due to insufficient memory on requested size of 535 detected for tactic 0x0000000000000074.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:05] [W] [TRT] Tactic Device request: 534MB Available: 165MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:05] [W] [TRT] Skipping tactic 3 due to insufficient memory on requested size of 534 detected for tactic 0x0000000000000004.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:05] [W] [TRT] Tactic Device request: 534MB Available: 165MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:05] [W] [TRT] Skipping tactic 9 due to insufficient memory on requested size of 534 detected for tactic 0x000000000000003c.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:05] [W] [TRT] Tactic Device request: 534MB Available: 165MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:05] [W] [TRT] Skipping tactic 15 due to insufficient memory on requested size of 534 detected for tactic 0x0000000000000074.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:11] [W] [TRT] Tactic Device request: 555MB Available: 164MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:11] [W] [TRT] Skipping tactic 3 due to insufficient memory on requested size of 555 detected for tactic 0x0000000000000005.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:11] [W] [TRT] Tactic Device request: 555MB Available: 164MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:11] [W] [TRT] Skipping tactic 7 due to insufficient memory on requested size of 555 detected for tactic 0x000000000000003d.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:11] [W] [TRT] Tactic Device request: 555MB Available: 164MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:11] [W] [TRT] Skipping tactic 11 due to insufficient memory on requested size of 555 detected for tactic 0x0000000000000075.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:13] [W] [TRT] Tactic Device request: 552MB Available: 161MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:14] [W] [TRT] Skipping tactic 3 due to insufficient memory on requested size of 552 detected for tactic 0x0000000000000005.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:14] [W] [TRT] Tactic Device request: 552MB Available: 161MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:14] [W] [TRT] Skipping tactic 7 due to insufficient memory on requested size of 552 detected for tactic 0x000000000000003d.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:14] [W] [TRT] Tactic Device request: 552MB Available: 161MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:14] [W] [TRT] Skipping tactic 11 due to insufficient memory on requested size of 552 detected for tactic 0x0000000000000075.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:17] [W] [TRT] Tactic Device request: 2182MB Available: 190MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:17] [W] [TRT] Skipping tactic 3 due to insufficient memory on requested size of 2182 detected for tactic 0x0000000000000004.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:17] [W] [TRT] Tactic Device request: 2182MB Available: 190MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:17] [W] [TRT] Skipping tactic 8 due to insufficient memory on requested size of 2182 detected for tactic 0x000000000000003c.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:17] [W] [TRT] Tactic Device request: 2182MB Available: 190MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:17] [W] [TRT] Skipping tactic 13 due to insufficient memory on requested size of 2182 detected for tactic 0x0000000000000074.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:19] [W] [TRT] Tactic Device request: 549MB Available: 197MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:19] [W] [TRT] Skipping tactic 3 due to insufficient memory on requested size of 549 detected for tactic 0x0000000000000004.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:19] [W] [TRT] Tactic Device request: 275MB Available: 197MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:19] [W] [TRT] Skipping tactic 4 due to insufficient memory on requested size of 275 detected for tactic 0x0000000000000005.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:19] [W] [TRT] Tactic Device request: 549MB Available: 197MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:19] [W] [TRT] Skipping tactic 9 due to insufficient memory on requested size of 549 detected for tactic 0x000000000000003c.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:19] [W] [TRT] Tactic Device request: 275MB Available: 197MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:19] [W] [TRT] Skipping tactic 10 due to insufficient memory on requested size of 275 detected for tactic 0x000000000000003d.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:19] [W] [TRT] Tactic Device request: 549MB Available: 197MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:19] [W] [TRT] Skipping tactic 15 due to insufficient memory on requested size of 549 detected for tactic 0x0000000000000074.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:19] [W] [TRT] Tactic Device request: 275MB Available: 197MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:19] [W] [TRT] Skipping tactic 16 due to insufficient memory on requested size of 275 detected for tactic 0x0000000000000075.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:21] [W] [TRT] Tactic Device request: 549MB Available: 197MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:21] [W] [TRT] Skipping tactic 3 due to insufficient memory on requested size of 549 detected for tactic 0x0000000000000004.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:21] [W] [TRT] Tactic Device request: 274MB Available: 197MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:21] [W] [TRT] Skipping tactic 4 due to insufficient memory on requested size of 274 detected for tactic 0x0000000000000005.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:21] [W] [TRT] Tactic Device request: 549MB Available: 197MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:21] [W] [TRT] Skipping tactic 9 due to insufficient memory on requested size of 549 detected for tactic 0x000000000000003c.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:21] [W] [TRT] Tactic Device request: 274MB Available: 197MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:21] [W] [TRT] Skipping tactic 10 due to insufficient memory on requested size of 274 detected for tactic 0x000000000000003d.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:21] [W] [TRT] Tactic Device request: 549MB Available: 197MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:21] [W] [TRT] Skipping tactic 15 due to insufficient memory on requested size of 549 detected for tactic 0x0000000000000074.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:21] [W] [TRT] Tactic Device request: 274MB Available: 197MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:21] [W] [TRT] Skipping tactic 16 due to insufficient memory on requested size of 274 detected for tactic 0x0000000000000075.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:24] [W] [TRT] Tactic Device request: 3273MB Available: 192MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:24] [W] [TRT] Skipping tactic 3 due to insufficient memory on requested size of 3273 detected for tactic 0x0000000000000004.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:24] [W] [TRT] Tactic Device request: 3273MB Available: 190MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:25] [W] [TRT] Skipping tactic 8 due to insufficient memory on requested size of 3273 detected for tactic 0x000000000000003c.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:25] [W] [TRT] Tactic Device request: 3273MB Available: 190MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:25] [W] [TRT] Skipping tactic 13 due to insufficient memory on requested size of 3273 detected for tactic 0x0000000000000074.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:27] [W] [TRT] Tactic Device request: 1093MB Available: 186MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:27] [W] [TRT] Skipping tactic 3 due to insufficient memory on requested size of 1093 detected for tactic 0x0000000000000004.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:27] [W] [TRT] Tactic Device request: 1093MB Available: 186MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:27] [W] [TRT] Skipping tactic 8 due to insufficient memory on requested size of 1093 detected for tactic 0x000000000000003c.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:27] [W] [TRT] Tactic Device request: 1093MB Available: 187MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:27] [W] [TRT] Skipping tactic 13 due to insufficient memory on requested size of 1093 detected for tactic 0x0000000000000074.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:36] [W] [TRT] Tactic Device request: 3184MB Available: 175MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:36] [W] [TRT] Skipping tactic 3 due to insufficient memory on requested size of 3184 detected for tactic 0x0000000000000004.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:37] [W] [TRT] Tactic Device request: 3184MB Available: 175MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:37] [W] [TRT] Skipping tactic 8 due to insufficient memory on requested size of 3184 detected for tactic 0x000000000000003c.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:37] [W] [TRT] Tactic Device request: 3184MB Available: 175MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:37] [W] [TRT] Skipping tactic 13 due to insufficient memory on requested size of 3184 detected for tactic 0x0000000000000074.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:41] [W] [TRT] Tactic Device request: 3152MB Available: 175MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:41] [W] [TRT] Skipping tactic 3 due to insufficient memory on requested size of 3152 detected for tactic 0x0000000000000004.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:41] [W] [TRT] Tactic Device request: 3152MB Available: 175MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:41] [W] [TRT] Skipping tactic 8 due to insufficient memory on requested size of 3152 detected for tactic 0x000000000000003c.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:42] [W] [TRT] Tactic Device request: 3152MB Available: 175MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:42] [W] [TRT] Skipping tactic 13 due to insufficient memory on requested size of 3152 detected for tactic 0x0000000000000074.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:45] [W] [TRT] Tactic Device request: 278MB Available: 169MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:45] [W] [TRT] Skipping tactic 3 due to insufficient memory on requested size of 278 detected for tactic 0x0000000000000005.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:45] [W] [TRT] Tactic Device request: 278MB Available: 169MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:45] [W] [TRT] Skipping tactic 7 due to insufficient memory on requested size of 278 detected for tactic 0x000000000000003d.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:45] [W] [TRT] Tactic Device request: 278MB Available: 169MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:45] [W] [TRT] Skipping tactic 11 due to insufficient memory on requested size of 278 detected for tactic 0x0000000000000075.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:47] [W] [TRT] Tactic Device request: 3144MB Available: 168MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:47] [W] [TRT] Skipping tactic 3 due to insufficient memory on requested size of 3144 detected for tactic 0x0000000000000004.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:48] [W] [TRT] Tactic Device request: 3144MB Available: 168MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:48] [W] [TRT] Skipping tactic 9 due to insufficient memory on requested size of 3144 detected for tactic 0x000000000000003c.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:49] [W] [TRT] Tactic Device request: 3144MB Available: 167MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:49] [W] [TRT] Skipping tactic 15 due to insufficient memory on requested size of 3144 detected for tactic 0x0000000000000074.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:55] [W] [TRT] Tactic Device request: 533MB Available: 146MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:55] [W] [TRT] Skipping tactic 3 due to insufficient memory on requested size of 533 detected for tactic 0x0000000000000004.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:55] [W] [TRT] Tactic Device request: 533MB Available: 146MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:55] [W] [TRT] Skipping tactic 8 due to insufficient memory on requested size of 533 detected for tactic 0x000000000000003c.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:55] [W] [TRT] Tactic Device request: 533MB Available: 146MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:55] [W] [TRT] Skipping tactic 13 due to insufficient memory on requested size of 533 detected for tactic 0x0000000000000074.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:56] [W] [TRT] Tactic Device request: 531MB Available: 143MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:56] [W] [TRT] Skipping tactic 3 due to insufficient memory on requested size of 531 detected for tactic 0x0000000000000004.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:56] [W] [TRT] Tactic Device request: 531MB Available: 144MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:56] [W] [TRT] Skipping tactic 8 due to insufficient memory on requested size of 531 detected for tactic 0x000000000000003c.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:56] [W] [TRT] Tactic Device request: 531MB Available: 144MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:56] [W] [TRT] Skipping tactic 13 due to insufficient memory on requested size of 531 detected for tactic 0x0000000000000074.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:57] [W] [TRT] Tactic Device request: 2103MB Available: 144MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:57] [W] [TRT] Skipping tactic 3 due to insufficient memory on requested size of 2103 detected for tactic 0x0000000000000004.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:58] [W] [TRT] Tactic Device request: 2103MB Available: 196MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:58] [W] [TRT] Skipping tactic 9 due to insufficient memory on requested size of 2103 detected for tactic 0x000000000000003c.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:43:58] [W] [TRT] Tactic Device request: 2103MB Available: 195MB. Device memory is insufficient to use tactic.
[08/29/2023-19:43:58] [W] [TRT] Skipping tactic 15 due to insufficient memory on requested size of 2103 detected for tactic 0x0000000000000074.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:02] [W] [TRT] Tactic Device request: 1322MB Available: 159MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:02] [W] [TRT] Skipping tactic 3 due to insufficient memory on requested size of 1322 detected for tactic 0x0000000000000004.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:02] [W] [TRT] Tactic Device request: 1322MB Available: 158MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:02] [W] [TRT] Skipping tactic 8 due to insufficient memory on requested size of 1322 detected for tactic 0x000000000000003c.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:02] [W] [TRT] Tactic Device request: 1322MB Available: 158MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:02] [W] [TRT] Skipping tactic 13 due to insufficient memory on requested size of 1322 detected for tactic 0x0000000000000074.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:03] [W] [TRT] Tactic Device request: 1321MB Available: 158MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:03] [W] [TRT] Skipping tactic 3 due to insufficient memory on requested size of 1321 detected for tactic 0x0000000000000004.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:03] [W] [TRT] Tactic Device request: 1321MB Available: 158MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:03] [W] [TRT] Skipping tactic 8 due to insufficient memory on requested size of 1321 detected for tactic 0x000000000000003c.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:03] [W] [TRT] Tactic Device request: 1321MB Available: 158MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:03] [W] [TRT] Skipping tactic 13 due to insufficient memory on requested size of 1321 detected for tactic 0x0000000000000074.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:05] [W] [TRT] Tactic Device request: 1596MB Available: 156MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:05] [W] [TRT] Skipping tactic 3 due to insufficient memory on requested size of 1596 detected for tactic 0x0000000000000004.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:05] [W] [TRT] Tactic Device request: 210MB Available: 156MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:05] [W] [TRT] Skipping tactic 4 due to insufficient memory on requested size of 210 detected for tactic 0x0000000000000005.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:05] [W] [TRT] Tactic Device request: 1596MB Available: 156MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:05] [W] [TRT] Skipping tactic 9 due to insufficient memory on requested size of 1596 detected for tactic 0x000000000000003c.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:05] [W] [TRT] Tactic Device request: 210MB Available: 156MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:05] [W] [TRT] Skipping tactic 10 due to insufficient memory on requested size of 210 detected for tactic 0x000000000000003d.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:06] [W] [TRT] Tactic Device request: 1596MB Available: 156MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:06] [W] [TRT] Skipping tactic 15 due to insufficient memory on requested size of 1596 detected for tactic 0x0000000000000074.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:06] [W] [TRT] Tactic Device request: 210MB Available: 156MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:06] [W] [TRT] Skipping tactic 16 due to insufficient memory on requested size of 210 detected for tactic 0x0000000000000075.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:13] [W] [TRT] Tactic Device request: 335MB Available: 154MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:13] [W] [TRT] Skipping tactic 3 due to insufficient memory on requested size of 335 detected for tactic 0x0000000000000004.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:13] [W] [TRT] Tactic Device request: 335MB Available: 154MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:13] [W] [TRT] Skipping tactic 8 due to insufficient memory on requested size of 335 detected for tactic 0x000000000000003c.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:13] [W] [TRT] Tactic Device request: 335MB Available: 154MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:13] [W] [TRT] Skipping tactic 13 due to insufficient memory on requested size of 335 detected for tactic 0x0000000000000074.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:14] [W] [TRT] Tactic Device request: 335MB Available: 154MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:14] [W] [TRT] Skipping tactic 3 due to insufficient memory on requested size of 335 detected for tactic 0x0000000000000004.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:14] [W] [TRT] Tactic Device request: 335MB Available: 154MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:14] [W] [TRT] Skipping tactic 8 due to insufficient memory on requested size of 335 detected for tactic 0x000000000000003c.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:14] [W] [TRT] Tactic Device request: 335MB Available: 154MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:14] [W] [TRT] Skipping tactic 13 due to insufficient memory on requested size of 335 detected for tactic 0x0000000000000074.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:15] [W] [TRT] Tactic Device request: 824MB Available: 148MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:15] [W] [TRT] Skipping tactic 3 due to insufficient memory on requested size of 824 detected for tactic 0x0000000000000004.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:15] [W] [TRT] Tactic Device request: 411MB Available: 148MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:15] [W] [TRT] Skipping tactic 4 due to insufficient memory on requested size of 411 detected for tactic 0x0000000000000005.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:15] [W] [TRT] Tactic Device request: 824MB Available: 148MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:15] [W] [TRT] Skipping tactic 9 due to insufficient memory on requested size of 824 detected for tactic 0x000000000000003c.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:15] [W] [TRT] Tactic Device request: 411MB Available: 149MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:15] [W] [TRT] Skipping tactic 10 due to insufficient memory on requested size of 411 detected for tactic 0x000000000000003d.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:15] [W] [TRT] Tactic Device request: 824MB Available: 149MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:16] [W] [TRT] Skipping tactic 15 due to insufficient memory on requested size of 824 detected for tactic 0x0000000000000074.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:16] [W] [TRT] Tactic Device request: 411MB Available: 149MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:16] [W] [TRT] Skipping tactic 16 due to insufficient memory on requested size of 411 detected for tactic 0x0000000000000075.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:32] [W] [TRT] Tactic Device request: 229MB Available: 154MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:32] [W] [TRT] Skipping tactic 0 due to insufficient memory on requested size of 229 detected for tactic 0x0000000000000018.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:32] [W] [TRT] Tactic Device request: 229MB Available: 140MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:32] [W] [TRT] Skipping tactic 1 due to insufficient memory on requested size of 229 detected for tactic 0x0000000000000019.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:33] [W] [TRT] Tactic Device request: 229MB Available: 148MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:33] [W] [TRT] Skipping tactic 2 due to insufficient memory on requested size of 229 detected for tactic 0x000000000000001a.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:33] [W] [TRT] Tactic Device request: 229MB Available: 136MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:33] [W] [TRT] Skipping tactic 3 due to insufficient memory on requested size of 229 detected for tactic 0x000000000000001b.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:34] [W] [TRT] Tactic Device request: 229MB Available: 136MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:34] [W] [TRT] Skipping tactic 4 due to insufficient memory on requested size of 229 detected for tactic 0x000000000000001f.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:38] [W] [TRT] Tactic Device request: 164MB Available: 133MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:38] [W] [TRT] Skipping tactic 0 due to insufficient memory on requested size of 164 detected for tactic 0x0000000000000018.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:38] [W] [TRT] Tactic Device request: 164MB Available: 133MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:38] [W] [TRT] Skipping tactic 1 due to insufficient memory on requested size of 164 detected for tactic 0x0000000000000019.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:38] [W] [TRT] Tactic Device request: 164MB Available: 133MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:38] [W] [TRT] Skipping tactic 2 due to insufficient memory on requested size of 164 detected for tactic 0x000000000000001a.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:38] [W] [TRT] Tactic Device request: 164MB Available: 133MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:38] [W] [TRT] Skipping tactic 3 due to insufficient memory on requested size of 164 detected for tactic 0x000000000000001b.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:38] [W] [TRT] Tactic Device request: 164MB Available: 133MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:38] [W] [TRT] Skipping tactic 4 due to insufficient memory on requested size of 164 detected for tactic 0x000000000000001f.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:39] [W] [TRT] Tactic Device request: 164MB Available: 133MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:39] [W] [TRT] Skipping tactic 0 due to insufficient memory on requested size of 164 detected for tactic 0x0000000000000000.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:39] [W] [TRT] Tactic Device request: 166MB Available: 133MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:39] [W] [TRT] Skipping tactic 1 due to insufficient memory on requested size of 166 detected for tactic 0x0000000000000001.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:39] [W] [TRT] Tactic Device request: 1183MB Available: 132MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:40] [W] [TRT] Skipping tactic 3 due to insufficient memory on requested size of 1183 detected for tactic 0x0000000000000004.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:40] [W] [TRT] Tactic Device request: 1183MB Available: 132MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:40] [W] [TRT] Skipping tactic 8 due to insufficient memory on requested size of 1183 detected for tactic 0x000000000000003c.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:44:40] [W] [TRT] Tactic Device request: 1183MB Available: 140MB. Device memory is insufficient to use tactic.
[08/29/2023-19:44:40] [W] [TRT] Skipping tactic 13 due to insufficient memory on requested size of 1183 detected for tactic 0x0000000000000074.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().
[08/29/2023-19:45:01] [I] [TRT] Total Activation Memory:<PHONE_NUMBER>
[08/29/2023-19:45:01] [I] [TRT] Detected 1 inputs and 4 output network tensors.
[08/29/2023-19:45:02] [I] [TRT] Total Host Persistent Memory: 219312
[08/29/2023-19:45:02] [I] [TRT] Total Device Persistent Memory: 0
[08/29/2023-19:45:02] [I] [TRT] Total Scratch Memory: 16128768
[08/29/2023-19:45:02] [I] [TRT] [MemUsageStats] Peak memory usage of TRT CPU/GPU memory allocators: CPU 10 MiB, GPU 164 MiB
[08/29/2023-19:45:02] [I] [TRT] [BlockAssignment] Started assigning block shifts. This will take 225 steps to complete.
[08/29/2023-19:45:02] [I] [TRT] [BlockAssignment] Algorithm ShiftNTopDown took 25.669ms to assign 8 blocks to 225 nodes requiring 37019648 bytes.
[08/29/2023-19:45:02] [I] [TRT] Total Activation Memory: 37019648
[08/29/2023-19:45:02] [I] [TRT] [MemUsageChange] Init cuBLAS/cuBLASLt: CPU +0, GPU +1, now: CPU 1584, GPU 3170 (MiB)
[08/29/2023-19:45:02] [I] [TRT] [MemUsageChange] Init cuDNN: CPU +1, GPU +0, now: CPU 1585, GPU 3170 (MiB)
[08/29/2023-19:45:02] [I] [TRT] [MemUsageChange] TensorRT-managed allocation in building engine: CPU +6, GPU +64, now: CPU 6, GPU 64 (MiB)
[08/29/2023-19:45:02] [I] Engine built in 358.262 sec.
[08/29/2023-19:45:04] [I] [TRT] Loaded engine size: 44 MiB
[08/29/2023-19:45:04] [I] [TRT] [MemUsageChange] Init cuBLAS/cuBLASLt: CPU +0, GPU +4, now: CPU 1284, GPU 3189 (MiB)
[08/29/2023-19:45:04] [I] [TRT] [MemUsageChange] Init cuDNN: CPU +0, GPU -4, now: CPU 1284, GPU 3185 (MiB)
[08/29/2023-19:45:04] [I] [TRT] [MemUsageChange] TensorRT-managed allocation in engine deserialization: CPU +0, GPU +42, now: CPU 0, GPU 42 (MiB)
[08/29/2023-19:45:04] [I] Engine deserialized in 0.0963974 sec.
[08/29/2023-19:45:04] [I] [TRT] [MemUsageChange] Init cuBLAS/cuBLASLt: CPU +0, GPU +3, now: CPU 1284, GPU 3185 (MiB)
[08/29/2023-19:45:04] [I] [TRT] [MemUsageChange] Init cuDNN: CPU +1, GPU -1, now: CPU 1285, GPU 3183 (MiB)
[08/29/2023-19:45:05] [I] [TRT] [MemUsageChange] TensorRT-managed allocation in IExecutionContext creation: CPU +0, GPU +36, now: CPU 0, GPU 78 (MiB)
[08/29/2023-19:45:05] [I] Setting persistentCacheLimit to 0 bytes.
[08/29/2023-19:45:05] [I] Using random values for input images
[08/29/2023-19:45:05] [I] Created input binding for images with dimensions 1x3x640x640
[08/29/2023-19:45:05] [I] Using random values for output num_dets
[08/29/2023-19:45:05] [I] Created output binding for num_dets with dimensions 1x1
[08/29/2023-19:45:05] [I] Using random values for output bboxes
[08/29/2023-19:45:05] [I] Created output binding for bboxes with dimensions 1x100x4
[08/29/2023-19:45:05] [I] Using random values for output scores
[08/29/2023-19:45:05] [I] Created output binding for scores with dimensions 1x100
[08/29/2023-19:45:05] [I] Using random values for output labels
[08/29/2023-19:45:05] [I] Created output binding for labels with dimensions 1x100
[08/29/2023-19:45:05] [I] Starting inference
[08/29/2023-19:45:08] [I] Warmup completed 4 queries over 200 ms
[08/29/2023-19:45:08] [I] Timing trace has 80 queries over 3.11034 s
[08/29/2023-19:45:08] [I]
[08/29/2023-19:45:08] [I] === Trace details ===
[08/29/2023-19:45:08] [I] Trace averages of 10 runs:
[08/29/2023-19:45:08] [I] Average on 10 runs - GPU latency: 38.371 ms - Host latency: 38.9641 ms (enqueue 2.90137 ms)
[08/29/2023-19:45:08] [I] Average on 10 runs - GPU latency: 38.3834 ms - Host latency: 38.9785 ms (enqueue 2.88069 ms)
[08/29/2023-19:45:08] [I] Average on 10 runs - GPU latency: 38.3909 ms - Host latency: 38.9816 ms (enqueue 2.86994 ms)
[08/29/2023-19:45:08] [I] Average on 10 runs - GPU latency: 38.4392 ms - Host latency: 39.0593 ms (enqueue 2.81237 ms)
[08/29/2023-19:45:08] [I] Average on 10 runs - GPU latency: 38.3848 ms - Host latency: 38.9955 ms (enqueue 2.88234 ms)
[08/29/2023-19:45:08] [I] Average on 10 runs - GPU latency: 38.4054 ms - Host latency: 39.0343 ms (enqueue 2.8696 ms)
[08/29/2023-19:45:08] [I] Average on 10 runs - GPU latency: 38.445 ms - Host latency: 39.0595 ms (enqueue 2.70129 ms)
[08/29/2023-19:45:08] [I] Average on 10 runs - GPU latency: 38.3911 ms - Host latency: 39.0244 ms (enqueue 2.89941 ms)
[08/29/2023-19:45:08] [I]
[08/29/2023-19:45:08] [I] === Performance summary ===
[08/29/2023-19:45:08] [I] Throughput: 25.7206 qps
[08/29/2023-19:45:08] [I] Latency: min = 38.7737 ms, max = 39.2764 ms, mean = 39.0121 ms, median = 39.0211 ms, percentile(90%) = 39.1119 ms, percentile(95%) = 39.1799 ms, percentile(99%) = 39.2764 ms
[08/29/2023-19:45:08] [I] Enqueue Time: min = 1.69238 ms, max = 3.12146 ms, mean = 2.85213 ms, median = 2.88138 ms, percentile(90%) = 2.95351 ms, percentile(95%) = 2.9668 ms, percentile(99%) = 3.12146 ms
[08/29/2023-19:45:08] [I] H2D Latency: min = 0.512878 ms, max = 0.822021 ms, mean = 0.594181 ms, median = 0.594849 ms, percentile(90%) = 0.641602 ms, percentile(95%) = 0.674927 ms, percentile(99%) = 0.822021 ms
[08/29/2023-19:45:08] [I] GPU Compute Time: min = 38.1471 ms, max = 38.6589 ms, mean = 38.4013 ms, median = 38.4033 ms, percentile(90%) = 38.4765 ms, percentile(95%) = 38.5371 ms, percentile(99%) = 38.6589 ms
[08/29/2023-19:45:08] [I] D2H Latency: min = 0.0100098 ms, max = 0.0180664 ms, mean = 0.016621 ms, median = 0.0167236 ms, percentile(90%) = 0.0177002 ms, percentile(95%) = 0.0178223 ms, percentile(99%) = 0.0180664 ms
[08/29/2023-19:45:08] [I] Total Host Walltime: 3.11034 s
[08/29/2023-19:45:08] [I] Total GPU Compute Time: 3.07211 s
[08/29/2023-19:45:08] [I] Explanations of the performance metrics are printed in the verbose logs.
[08/29/2023-19:45:08] [I]
&&&& PASSED TensorRT.trtexec [TensorRT v8502] # /usr/src/tensorrt/bin/trtexec --onnx=yolov8s.onnx --saveEngine=yolov8s.engine

推理：
python3 infer-det.py \
--engine yolov8s.engine \
--imgs data \
--show \
--out-dir outputs \
--device cuda:0

/home/jetson/YOLOv8-TensorRT/data/bus.jpg: no object!
/home/jetson/YOLOv8-TensorRT/data/zidane.jpg: no object!

我刚才使用你提供的yolov8s.onnx转tensorrt engine，发现推理结果是正确的。所以现在还是pytorch转onnx的问题

这次在pc上完成pytorch转onnx，终于成功了


Vina del Mar tournament in 2013 (Rafa's 1st after knee injury that forced him to withdraw from London Olympics) wasn't Santiago

Tournament Ext Id 505 was Vina del Mar in 2012 and 2013, not Santiago


BetterDiscord Support. (read description)

i went ahead and added automatic scss compiling to your repo through the use of github actions. because i dont have direct access to your repo here are some things youre going to need to do if you merge.

Change import links from snappercord -> your githack/gitpages import links
Change the meta (if needed) in the dracula.theme.css file
Change the readme to add better discord support.

after that is done it should be somewhat compatible with better discord.
Of course, everything wont work out of the gate, so you will need to tweak some things in your main scss file, but the only things i could see you tweaking are the selectors using the [src*=powercord] selector. (which is a dead selector i think) besides that, bd support should be basically complete :D
one more thing, in the current state of powercord, there is no git updates for themes, meaning that a user who doesnt know this, or doesnt know youre updating your theme, will not receive updates.  to combat this you either want to add a disclaimer to the repo stating that if you use powercord you will need to git pull every update, or you can create a separate file, and import dracula.scss into it, and use it as your main file by switching the preferred file in the manifest.
if you have any questions, or need any help. feel free to let me know. loving the theme.

thank you so much i truly appreciate all the help❤, merging:D

thank you so much i truly appreciate all the help❤, merging:D


Wrong URL for running

Instructions at https://github.com/NDLANO/h5p-ndla-timeline#running say:
Open the file dist/index.html in your browser
Which does not work. there is no index.html file in the dist folder.
The following works for me:
Open the file<EMAIL_ADDRESS>in your browser

That seems to be outdated information. The H5P CLI tool should be used if one wants to run the content type without a platform (IMHO, instead of having custom solutions in a repository).

Yeah, this seem more like a lacking README rather than an issue per se. We will try to make them better so they give a brief introduction and correct information.


Logo

I'd love to have a logo to represent this lib :v:
Some thoughts:

a nod to the Redux logo could make sense, but isn't necessary
the notion of a "resource" doesn't really have a set image that I'm aware of. Two ideas are basic shapes (sphere, pyramid, box), which could represent how resources are abstract things of different kinds. Or maybe a document, since resources on the web are often transferred within the body of an HTTP request.

shrug – I'm open to more ideas or possible logos :)

The first thing I thought of turns out to be a nod to the redux logo. Theirs is a bit more 'reacty' but I was thinking the idea of just 3 dots/boxes/shapes arranged in a circle with some arrows on the lines indicating 'direction'. The thought there was just that our resources tend to make trips back and forth between machines while they're being CRUDed.
+shrug

Still interested in this, but I'll be closing this issue out and labeling it revisit. Open to more ideas still though! :v:


EnvironmentNameNotFound: Could not find conda environment: textgen

I was trying to add this extension by this command prompt in Oobabooga_windows folder.
conda activate textgen
pip install oobabot-plugin
I got this error. Any idea why?
Thank you.
PS C:\oobabooga_windows> conda activate textgen
EnvironmentNameNotFound: Could not find conda environment: textgen
You can list all discoverable environments with conda info --envs.
PS C:\oobabooga_windows> pip install oobabot-plugin

Not sure if this is an oobabot specific error, but have you verified that the conda environment has been created?  If not, something like this would create it for you:
conda create -n textgen python=3.10
Let me know if that helps!

Closing due to lack of activity, let me know if this is still happening!


Extraction option

This is what I did to make extraction optional. It adds a command line argument -z, --zipped to the CLI that means "leave them zipped". The JavaScript API also has a new last argument that is optional and defaults to false called leaveZipped.
Let me know if that's cool and if so I'll add a to test/downloadRelease.js
fixes #2

Perfect thanks!


LP view data provider

This is a bug. LP table did not auto-update.

Hey @MadalinaRaicu is this blocked by core? if so could you pop that label on it and link to the ticket in core repo that is blocking it (either one that already exists or that you have created). Thank you!!

issue is fixed in core https://github.com/vegaprotocol/vega/issues/6408 but we are waiting for the 0.58 testnet release. if the subscriptions get deployed to console and someone runs it on testnet 0.57 it will bring data nodes down.


Add integration tests

[ ] Use Dredd to verify that the documentation matches the implementation.
[x] Write integration tests.

It doesn't look like dredd is going to be ready for a few years


Add Helm chart and docs

Similar to the kustomize section.

Looking at this I don't think this fits neither as a kubernetes "application" nor a helm "library". Might revisit later but won't do for now.


Suggestion: Expose join API on Builder Class

I've mentioned in https://github.com/danielrearden/sqlmancer/issues/132, I've now come across multiple instances where I need to alter plain one to many or many to many statements. A scenario will arise where I'd like to have a connection of one type to another, but can only return data from my API if those have a certain status. This is easy to alleviate with a simple where clause to a sql statement, which I can do by manually creating the resolver using sqlmancer models for a one to many relationship. However, for many to many there is no such easy solution in the API. Since under the hood sqlmancer is making these sql statements, I'm wondering how easy would it be to expose this API as public methods on models?

Thanks for opening this issue :)
This is something I've also been wrestling with. The core of the problem is that the library currently has no concept of where a foreign key resides. It simply captures the necessary information needed for the join condition (i.e. match this column on table A with this column on table B). The fix would be to identify individual relationships between models like how traditional ORM libraries do (belongsTo, hasMany, etc.). But that sort of thing adds even more complexity to the @relate directive and it's already a bit hard to grok. That said, I'm down to adding this if we can figure out a palpable way of handling it through directives... maybe by breaking up @relate into individual directives like @hasMany, @hasOne, @belongsTo and @belongsToMany like Lighthouse does 🤔
As a workaround, for many-to-many relationships, you can just add a model to the schema that represents the join table and then hide it with the @private directive. For all other relationships, joining two models is just a question of updating the correct column on one of the models.

That makes sense to me. I've been digging through the source code myself, and I wonder if it'd easier to just change the @relate API to add a field like relation or something along those lines to describe the relationship. So if you have the following in your schema define say a many to many.
  type Post @model(table: "posts", pk: "id", include: ["id"]) {
    id: ID!
    authors: [Author!]!
      @relate(
        relation: "hasMany"
        through: "posts_authors"
        on: [{ from: "id", to: "post_id" }, { from: "author_id", to: "id" }]
        pagination: OFFSET
      )
      @many
      @paginate
    franchise: Franchise @relate(
      relation: "belongsTo"
      on: { from: "franchise_id", to: "id"}
     )
  }

As for the work around. Do you have an example of how the schema and resolver would look for a join table and the model it's trying to join through? Having a bit of difficulty figuring out how to make it work

type Post @model(table: "posts", pk: "id", include: ["id"]) {
  id: ID!
  authors: [Author!]!
    @relate(
      through: "posts_authors"
      on: [{ from: "id", to: "post_id" }, { from: "author_id", to: "id" }]
      pagination: OFFSET
      )
    @many
    @paginate
}

type Author @model(table: "authors", pk: "id", include: ["id"]) {
  id: ID!
  posts: [Post!]!
    @relate(
      through: "posts_authors"
      on: [{ from: "id", to: "author_id" }, { from: "post_id", to: "id" }]
      pagination: OFFSET
      )
    @many
    @paginate
  body: String
}

type PostAuthor @model(table: "posts_authors", pk: "id") {
  postId: ID
  authorId: ID
}

type Mutation {
  writePost(input: WritePostInput!): Post
}

input WritePostInput {
  body: String!
}

const resolvers = {
  Mutation: {
    writePost: (root, args, ctx, info) => {
      const postId = await Post.createOne({ body: args.input.body }).execute()
      const authorId = ctx.userId

      await PostAuthor.createOne({ postId, authorId })

      return Post.findById(postId).resolveInfo(info).execute()
    }
  }
}


C++ compiler should not be enforced globally

When doing add_subdirectory(ThirdParty/rocThrust) from a project, rocThrust fails to install rocprim with the following error message:
CMake Error at cmake/VerifyCompiler.cmake:29 (message):
  On ROCm platform 'hipcc' or HIP-aware Clang must be used as C++ compiler.
Call Stack (most recent call first):
  CMakeLists.txt:82 (include)

Please correct me, if I'm wrong: this message requests that the CMAKE_CXX_COMPILER must be hipcc. I believe this requirement contradicts with the way how modern CMake is designed. Starting from CMake 3.18/3.23, CUDA and HIP are CMake "languages" that could be enabled with e.g. enable_language(HIP). The hipcc compiler is then provided by CMAKE_HIP_COMPILER, independently of the main CMAKE_CXX_COMPILER. Furthermore, CMake chooses the C++ compiler variant, depending on the file extension (.cpp, .cu, .hip, etc.). In order to comply with this flexibility of CMake, rocThrust should not post this error, and instead check for CMAKE_HIP_COMPILER, and use it internally if it wishes so.

@mfep Please take a look at this.

@dmikushin Our libraries are transitioning to better support for cmake's HIP language support. I appreciate your bug report. A fix will be targeted for a future release.

This item is still in progress.  A fix will should appear in a future release.

Would you just consider making this a warning for now anyway? It's not easy to work around in our builds (a large project supporting multiple GPU/CPU backends).


Concurrent Test Execution worker number

Are you requesting a feature or reporting a bug?
Feature.
What is the current behavior?
You can pass in a number to get a pool of browsers to run tests but there does not seem to be any way to determine which worker the test is running on.
What is the expected behavior?
It would be helpful if testcafe could expose some sort of WORKER_NUMBER variable. For example - lets say I am testing against an api where the tests do something where a call has to be made to the api to modify state in the database. I don't think concurrency would work too well here if you had 4 tests running at the same time hitting the same api.
It would be helpful if a WORKER_NUMBER variable is exposed so users could set up their workers to an isolated api. For example, you could run your api on 4 different ports, which talk to separate databases this way any tests modifying state won't potentially contaminate the other.
fixture `Example page`
    .page `localhost:300${WORKER_NUMBER}`;

// 4 workers =
//   worker 0: localhost:3000
//   worker 1: localhost:3001
//   worker 2: localhost:3002
//   worker 3: localhost:3003

Thanks!

Hi @ervoiox,
Thanks for your proposal. Since the test file is executed one time regardless of browsers count we can't add this number to the global scope as you did in your example.
For example if you run tests with the following command: testcafe chrome,firefox test.js it works in the following way:
fixture `my fixture`;

// this code is executed once

test('Test', async t => {
    // this code is executed twice (in chrome and in firefox)
});

But we have proposal to Implement t.browserInfo. I think we can add the concurrent worker number there.
So I close this issue in favor of the #481.


Add Blazor Quick Start Link to Introduction

I think we may want to consider having this as a button at the top to get started with Blazor quickly. cc/ @danroth27
https://dotnet.microsoft.com/en-us/learn/aspnet/blazor-tutorial/intro
This page is currently the top search result when you search for Blazor.

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

ID: 5bc28995-6784-a7d2-5c0b-9811a8d19c1a
Version Independent ID: 1668c8fb-024c-c86d-d4d5-e22e3355c04b
Content: Introduction to ASP.NET Core Blazor
Content Source: aspnetcore/blazor/index.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

Tutorials is currently the forth entry in the ToC. We could move the Tutorials node up to just under the Overview ... make it next after this topic ...

Overview
Tutorials
Supported platforms
Tooling
Hosting models
Project structure
...

Note to self: I see that I need to reverse the order of the WASM and Server sections of this topic.

I agree that'd be helpful, however I think we may want to also include it as (one of) the first things on the Overview page as well, simply because it's the first result when you search for Blazor. I believe that tutorial may be a "quicker start" than reading through the overview and so on. This is entirely my opinion, and I'd love to hear other feedback on it (this isn't necessarily a request to make the change yet).

Yeah, that's cool. We could do both.
We should keep in mind that the first tutorial links directly to the Todo List tutorial before returning the reader back over here. Right now just following our links, we kind'a force readers into a double-tutorial experience. Perhaps, they should return to the Overview after the first tutorial, knowing that they'll hit the Tutorial node PDQ for the other two tutorials.
WRT the best path for pushing readers one way or the other, I think we'd need the results of a properly-designed A-B test. Personally, I like to read a little bit of the basics of a framework before I spend my time in a tutorial, but I'm sure others prefer the other learning path.


sans-serif on windows displays Arial instead of Segoe UI

Due to a less known Windows bug feature, Arial is always matched for Helvetica when Helvetica is not installed on the system.
The current sans-serif class on _font-family.scss
.sans-serif {
  font-family: -apple-system, BlinkMacSystemFont,
               'avenir next', avenir,
               'helvetica neue', helvetica,
               ubuntu,
               roboto, noto,
               'segoe ui', arial,
               sans-serif;
}

will display arial and not segoe ui on Windows.
Solution is to move segoe ui above helvetica, but because I'm not sure of the font stack strategy it might not be as simple as that :-).
If we move segoe between helvetica neue and helvetica it will never load Ubuntu, Roboto and Noto even if the user has those fonts installed.
Codepen demo: http://codepen.io/koriolis/pen/BWNwMV/
Screenshot (for those not on Windows):

@koriolis Thanks so much for the detailed description of what is going on. I'll take a stab at a fix.

for some reference:

github uses the following stack: -apple-system, BlinkMacSystemFont, "Segoe UI", Helvetica, Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol"
and System Font Stack https://css-tricks.com/snippets/css/system-font-stack/

@mrmrs Any progress on this?
I'm a noob at OSS collaboration, but I'll be happy to open a PR with this change.

This will definitely be an improvement. Arial does not deserve to make it to any other website and we can prevent it.  Helvetica has earned its place in typographic history honestly. But Arial, only by Microsoft imposing it upon us for 20+ years as the main user-interface font in Windows. That’s the only reason you’ve heard of it. That’s the only reason you might consider using it. That’s a terrible reason. I try to keep the litmus tests to a minimum, but this must be one: you cannot create good typography with Arial.

Practical Typography by Matthew Butterick - Helvetica and Arial alternatives


Refactor rerender

Refactor the node lookup inside rerender to instead pass the next nodes as parameters to the function
There is a comment indicating the lines in https://github.com/nullstack/nullstack/blob/master/client/rerender.js

Already coded this one in nullstack/refactor-rerender
Needs some insight if the issue was fully fixed, though.

Merged into master 💖


Set up container and migrate image-pipeline feature

The image pipeline feature is migrated from art-bot to art-dash so that art-dashboard UI could use the same API endpoint. For art-dashboard server(which is also the API server now) to handle the functions of art-bot, a container similar to art-bot is setup.
In future, any functionality that is required by more than one tool, can be defined in art-dash-server-api to maintain single source of truth and ease of debugging

Todo:

[ ] Check/Setup keytab in art-dashboard-server
[ ] Enhance API usage documentation
[ ] Add tests

Issues

cache header not working in test deployment. Disabled for now.
oc commands not working in deployment. Authorization issue with keytab
Have to change keytab mounting location in art-dash aos-art-dev namespace

Removed pr_in build feature, since its being developed for art-bot first. Will migrate later to art-dash.

Migration file build/migrations/0001_initial.py added, since production does not allow to write the file in workspaces/art-dash

Related PR to update production docs: https://github.com/openshift-eng/art-config/pull/13


Readme: Updated README.md

Fix typos and clean up the content
Signed-off-by: Chaitanya<EMAIL_ADDRESS>

This PR looks good to me. :=)


How to install without composer ?

Hi,
I'm writing a Wordpress Plugin and would like to use FluentDOM + Selectors-Symfony selector within.
I don't know much about composer so I would like to avoid using it to install the whole thing.
So I downloaded FluentDOM and Selectors-Symfony.
I extracted them like this :
[..]/lib/FluentDOM-master
[..]/lib/Selectors-Symfony-master
and I'm loading FluentDOM like this :
        if (!class_exists('FluentDOM'))             require_once([..]/lib/FluentDOM-master/src/FluentDOM.php');
But I'm not sure of the place where I extracted  Selectors-Symfony, and I don't know how to "register" it.
Got PHP Fatal error:  Interface 'FluentDOM\Node\QuerySelector' not found in...
When trying to run
$fd = FluentDOM::load($htmlstring, 'text/html');
Could you help me ?
Thanks !

Here was an bug in "_require.php". It included file that needed the interface before the interface itself.
https://github.com/FluentDOM/FluentDOM/commit/93db8d4f6478bbb8180cd42f88b05f22e432829e
FluentDOM uses this file, if it the classes/interfaces are not loaded.
The selectors will be more complex. If the Symfony library is installed and available you can copy the src/Transformer.php somewhere and register an callback that provides it:
FluentDOM::registerXpathTransformer(
  function() {
    require_once(__DIR__.'/Transformer.php');
    return new \FluentDOM\Symfony\CssSelector\Transformer;
  }
);

Composer
Composer does several things for you. It installs packages including their dependencies. For example if you install fluentdom/selectors-symfony it will install fluentdom\fluentdom and symfony/css-selector, too. It handles versions, too.
The second part is the autoloader. Composer includes an autoloader that is configured by the composer.json files. You only need to require vendor/autoload.php and all classes/inerfaces from the installed packages will be available.

Ok, thanks for the reply, very useful !
Now, I manage to load it with
    require_once($this->plugin_dir . '_inc/lib/FluentDOM-master/src/FluentDOM.php');

    FluentDOM::registerXpathTransformer(
      function() {
        require_once($this->plugin_dir . '_inc/lib/Selectors-Symfony-master/src/Transformer.php');
        return new \FluentDOM\Symfony\CssSelector\Transformer;
      }
    );

But the next part of my code make the browser to crash, without any php error fired (ERR_EMPTY_RESPONSE).
    $html='hello';
    $fd = FluentDOM::load($html, 'text/html');

Any idea on this ?  Thanks !

Ok !
I finally managed to make it with composer.  Thanks for the explanations.
So I used

$ composer require fluentdom/selectors-symfony --ignore-platform-reqs

Now the libraries are loaded, but it throws an error :
require_once($this->plugin_dir . '_inc/php/autoload.php');

Fatal error: Call to undefined method FluentDOM::registerXpathTransformer() in .../_inc/php/fluentdom/selectors-symfony/src/plugin.php on line 5

Any idea bout this ?

If you download the files from GitHub, you will fetch "master". This is the current development version (5.3dev). Composer will install 5.2 stable by default. One of the differences is the CSS selector integration. In 5.2 is is a part of the FluentDOM core, so you do not need fluentdom/selectors-symfony. 5.3 has got the registration and separate integration packages.


Potential SKU issue

States "article discusses Basic Load Balancer".
Does this definitely apply to Basic Load Balancer (Internet Facing) as the "All settings" button is not shown during testing?
Additionally when configuring the logs to storage account via "Diagnostics settings" they are not saving to specified storage account?

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

ID: d797fa9d-3a8c-6775-978d-c4e9420872c2
Version Independent ID: 8770fb75-b8fd-af32-10a8-5d1391217333
Content: Monitor operations, events, and counters for Load Balancer
Content Source: articles/load-balancer/load-balancer-monitor-log.md
Service: load-balancer
GitHub Login: @KumudD
Microsoft Alias: kumud

@brett-todd  We are actively investigating and will get back to you soon.

@brett-todd Thanks for the feedback! This article appears to have some dated instructions.
Diagnostics will be saved in Table Storage in the specified storage account. Usually if logs are not being saved, it is because no relevant logs age being produced.
I have assigned the issue to the content author to evaluate and update as appropriate.

Is there an update on this for the Basic and Standard SKU?
How does one enable logging for the Standard LB?

@bearrito There should not be an update needed for this. Logging on Standard LBs should be enabled by default. Here is a document explaining Standard Load Balancer Logs and Metrics.

Logging is working.
However, the screenshot in section 4 of this article is for the Standard Load Balancer rather than Basic.

#please-close

@brett-todd We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.