Ad suddenly stop showing without any notice - Ad failed to load : 3

I/Ads     (27163): GMA Debug BEGIN
I/Ads     (27163): GMA Debug CONTENT {"timestamp":1702926880842,"event":"onNetworkResponseBody","components":["network_request_3d3c029d-36f6-4a2c-b357-7eb3468877d4"],"params":{"body":"","bodylength":0}}
I/Ads     (27163): GMA Debug FINISH
I/Ads     (27163): Ad failed to load : 3
I/Ads     (27163): GMA Debug BEGIN
I/Ads     (27163): GMA Debug CONTENT {"timestamp":1702926880949,"event":"onNetworkRequest","components":["network_request_6842d61e-38eb-4368-acd7-167fa51353ec"],"params":{"firstline":{"uri":"https://csi.gstatic.com/csi?app=com.bulbulcse01.italian_card_leader_board&is_bstar=0&os=12&e=318496669%2C318500618%2C318486317%2C318491267%2C318482078%2C318483611%2C318484141%2C318484497%2C318501517%2C318508442%2C318503827%2C318509850%2C318512169%2C318512455%2C318512673%2C318513021%2C318512225%2C318512272&network_coarse=1&task.request-parcel=s.1&task.renderer=f.5&task.webview-cookie=s.14&task.server-transaction=s.837&task.signals=s.50&s=gmob_sdk&scar=false&is_lite_sdk=0&v=3&task.render-config-init=f.1&action=ftl&api_v=31&sdkVersion=afma-sdk-a-v234310999.233702000.1&network_fine=0&device=Xiaomi POCO M2 Pro&gqi=IJqAZdK-KNCb9fwPtqWsOA&ftl=3&ed=com.google.android.gms.ads","verb":"GET"},"headers":[{"name":"User-Agent","value":"Mozilla/5.0 (Linux; Android 12; POCO M2 Pro Build/SKQ1.211019.001; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/120.0.6099.43 Mobile Safari/537.36 (Mobile; afma-sdk-a-v234310999.233702000.1)"}]}}
I/Ads     (27163): GMA Debug FINISH
I/flutter (27163): Inline adaptive banner failedToLoad: LoadAdError(code: 3, domain: com.google.android.gms.ads, message: No fill., responseInfo: ResponseInfo(responseId: null, mediationAdapterClassName: , adapterResponses: [], loadedAdapterResponseInfo: null), responseExtras: {})
I/Ads     (27163): GMA Debug BEGIN
I/Ads     (27163): GMA Debug CONTENT {"timestamp":1702926883187,"event":"onNetworkResponse","components":["network_request_6842d61e-38eb-4368-acd7-167fa51353ec"],"params":{"firstline":{"code":204},"headers":[{"name":null,"value":"HTTP/1.1 204 No Content"},{"name":"Alt-Svc","value":"h3=":443"; ma=2592000,h3-29=":443"; ma=2592000"},{"name":"Server","value":"Golfe2"},{"name":"Access-Control-Allow-Origin","value":"*"},{"name":"Last-Modified","value":"Wed, 21 Jan 2004 19:51:30 GMT"},{"name":"Pragma","value":"no-cache"},{"name":"X-Android-Received-Millis","value":"1702926883182"},{"name":"Date","value":"Mon, 18 Dec 2023 19:14:42 GMT"},{"name":"X-Android-Selected-Protocol","value":"http/1.1"},{"name":"Cache-Control","value":"no-cache, no-store, must-revalidate"},{"name":"X-Android-Response-Source","value":"NETWORK 204"},{"name":"Cross-Origin-Resource-Policy","value":"cross-origin"},{"name":"Expires","value":"Fri, 01 Jan 1990 00:00:00 GMT"},{"name":"X-Android-Sent-Millis","value":"1702926882140"},{"name":"Content-Length","value":"0"},{"name":"Content-Type","value":"image/gif"}]}}
I/Ads     (27163): GMA Debug FINISH
D/DecorView: onWindowFocusChanged hasWindowFocus false
D/DecorView: onWindowFocusChanged hasWindowFocus true

flutter doctor
┌─────────────────────────────────────────────────────────┐
│ A new version of Flutter is available!                  │
│                                                         │
│ To update to the latest version, run "flutter upgrade". │
└─────────────────────────────────────────────────────────┘
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.16.3, on Microsoft Windows [Version 10.0.19045.2965], locale en-US)
[√] Windows Version (Installed version of Windows is version 10 or higher)
[!] Android toolchain - develop for Android devices (Android SDK version 33.0.2)
X cmdline-tools component is missing
Run path/to/sdkmanager --install "cmdline-tools;latest"
See https://developer.android.com/studio/command-line for more details.
X Android license status unknown.
Run flutter doctor --android-licenses to accept the SDK licenses.
See https://flutter.dev/docs/get-started/install/windows#android-setup for more details.
[√] Chrome - develop for the web
[!] Visual Studio - develop Windows apps (Visual Studio Build Tools 2019 16.11.32)
X Visual Studio is missing necessary components. Please re-run the Visual Studio installer for the "Desktop development with C++" workload, and include these components:
MSVC v142 - VS 2019 C++ x64/x86 build tools
- If there are multiple build tool versions available, install the latest
C++ CMake tools for Windows
Windows 10 SDK
[√] Android Studio (version 2022.2)
[√] Connected device (5 available)
! Device emulator-5578 is offline.
[√] Network resources
! Doctor found issues in 2 categories.
flutter analyze
Resolving dependencies...
intl 0.18.1 (0.19.0 available)
matcher 0.12.16 (0.12.16+1 available)
material_color_utilities 0.5.0 (0.8.0 available)
meta 1.10.0 (1.11.0 available)
package_info_plus 4.2.0 (5.0.1 available)
package_rename 1.5.1 (1.5.2 available)
path 1.8.3 (1.9.0 available)
synchronized 3.1.0 (3.1.0+1 available)
test_api 0.6.1 (0.7.0 available)
url_launcher 6.2.1 (6.2.2 available)
url_launcher_linux 3.1.0 (3.1.1 available)
url_launcher_web 2.2.1 (2.2.2 available)
url_launcher_windows 3.1.0 (3.1.1 available)
web 0.3.0 (0.4.0 available)
Got dependencies!
14 packages have newer versions incompatible with dependency constraints.
Try flutter pub outdated for more information.
Analyzing card_score_counter_updated...
warning - The include file 'package:flutter_lints/flutter.yaml' in 'C:\Users\Administrator\StudioProjects\card_score_counter_updated\analysis_options.yaml' can't be found when analyzing
'C:\Users\Administrator\StudioProjects\card_score_counter_updated' - analysis_options.yaml:10:10 - include_file_not_found
info - 'canLaunch' is deprecated and shouldn't be used. Use canLaunchUrl instead - lib\AboutUs.dart:90:15 - deprecated_member_use
info - 'launch' is deprecated and shouldn't be used. Use launchUrl instead - lib\AboutUs.dart:91:13 - deprecated_member_use
warning - Unused import: 'package:italian_card_leader_board/AppDrawer.dart' - lib\CustomScore\CustomPlayersScore.dart:4:8 - unused_import
warning - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: customPlayersScore.playerList - lib\CustomScore\CustomPlayersScore.dart:16:7 -
must_be_immutable
warning - Unused import: 'dart:convert' - lib\CustomScore\ScoreBoard.dart:1:8 - unused_import
info - The import of 'package:flutter/cupertino.dart' is unnecessary because all of the used elements are also provided by the import of 'package:flutter/material.dart' - lib\CustomScore\ScoreBoard.dart:4:8 - unnecessary_import
warning - Unused import: 'package:italian_card_leader_board/AppDrawer.dart' - lib\CustomScore\ScoreBoard.dart:10:8 - unused_import
warning - The value of the field '_fadeInFadeOut' isn't used - lib\CustomScore\ScoreBoard.dart:53:26 - unused_field
warning - The left operand can't be null, so the right operand is never executed - lib\CustomScore\ScoreBoard.dart:653:44 - dead_null_aware_expression
warning - The exception variable 'e' isn't used, so the 'catch' clause can be removed - lib\CustomScore\ScoreBoard.dart:658:27 - unused_catch_clause
warning - The exception variable 'e' isn't used, so the 'catch' clause can be removed - lib\CustomScore\ScoreBoard.dart:681:37 - unused_catch_clause
warning - The value of the local variable 'result' isn't used - lib\CustomScore\ScoreBoard.dart:748:11 - unused_local_variable
warning - This function has a nullable return type of 'FutureOr<List?>', but ends without returning a value - lib\CustomScore\ScoreBoard.dart:754:25 - body_might_complete_normally_nullable
warning - The exception variable 'e' isn't used, so the 'catch' clause can be removed - lib\CustomScore\ScoreBoard.dart:969:43 - unused_catch_clause
warning - The operand can't be null, so the condition is always 'true' - lib\CustomScore\ScoreBoard.dart:1340:35 - unnecessary_null_comparison
warning - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: ScoreList.isDark - lib\CustomScore\ScoreBoard.dart:1460:7 - must_be_immutable
warning - The operand can't be null, so the condition is always 'true' - lib\CustomScore\databaseModel\model.dart:29:12 - unnecessary_null_comparison
warning - The operand can't be null, so the condition is always 'true' - lib\CustomScore\databaseModel\model.dart:87:12 - unnecessary_null_comparison
warning - Unused import: 'package:italian_card_leader_board/AppDrawer.dart' - lib\CustomScore\history.dart:6:8 - unused_import
warning - Unused import: 'dart:io' - lib\ItalianScore\admobAdd.dart:2:8 - unused_import
warning - The value of the field '_interstitialAd' isn't used - lib\ItalianScore\admobAdd.dart:17:19 - unused_field
warning - The value of the field '_numInterstitialLoadAttempts' isn't used - lib\ItalianScore\admobAdd.dart:18:7 - unused_field
warning - The value of the field '_rewardedAd' isn't used - lib\ItalianScore\admobAdd.dart:20:15 - unused_field
warning - The value of the field '_numRewardedLoadAttempts' isn't used - lib\ItalianScore\admobAdd.dart:21:7 - unused_field
warning - Unused import: 'ItalianScore/ItalianLeaderBoard.dart' - lib\splashScreen.dart:3:8 - unused_import
warning - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: SplashScreen.splash - lib\splashScreen.dart:6:7 - must_be_immutable
info - The import of 'package:flutter/cupertino.dart' is unnecessary because all of the used elements are also provided by the import of 'package:flutter/material.dart' - lib\utilits\CommonFunctions.dart:3:8 - unnecessary_import
info - 'canLaunch' is deprecated and shouldn't be used. Use canLaunchUrl instead - lib\utilits\CommonFunctions.dart:8:13 - deprecated_member_use
info - 'launch' is deprecated and shouldn't be used. Use launchUrl instead - lib\utilits\CommonFunctions.dart:9:11 - deprecated_member_use
warning - Unused import: 'package:italian_card_leader_board/model/model.dart' - lib\utilits\DB_Helper.dart:2:8 - unused_import
warning - Unused import: '../ItalianScore/ItalianLeaderBoard.dart' - lib\widgets\widgets.dart:3:8 - unused_import
warning - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: BoardGroup.CallButtonPressed, BoardGroup.BonusCallButton, BoardGroup.onDismissed,
BoardGroup.GroupScore, BoardGroup.GroupName, BoardGroup.GrupCallText, BoardGroup.isCalled, BoardGroup.GroupCalled, BoardGroup.isFinised - lib\widgets\widgets.dart:7:7 - must_be_immutable
warning - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: CustomHistoryListView.GroupA1, CustomHistoryListView.GroupA2,
CustomHistoryListView.GroupAresult, CustomHistoryListView.GroupB1, CustomHistoryListView.GroupB2, CustomHistoryListView.GroupBresult, CustomHistoryListView.isGroupASuccess, CustomHistoryListView.isGroupBSuccess -
lib\widgets\widgets.dart:403:7 - must_be_immutable
error - Target of URI doesn't exist: 'package:card_score_counter_updated/main.dart' - test\widget_test.dart:11:8 - uri_does_not_exist
error - The name 'MyApp' isn't a class - test\widget_test.dart:16:35 - creation_with_non_type
36 issues found. (ran in 11.3s)

Hi @BulbulH
It seems your issue is best suited on Developer Forum. I can see there are some similar issue there with above error code and message:
https://groups.google.com/g/google-admob-ads-sdk/c/1Q9rRNVAKYo/m/XBhQseM2AQAJ
https://groups.google.com/g/google-admob-ads-sdk/c/iyh17o76g44/m/UozyrWyHAAAJ
That being said, this googleads-mobile-flutter plugin and ads SDK in general don't have control on ad request fill rate. So I will close this issue as it's not a plugin issue. Thanks!

any possible solution ?


[GitRepository] Add methods to get and set remotes

This is needed because we want to reset the remote of the editable
clone.

LGTM


Rebuild to update toolchain

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] ~Reset the build number to 0 (if the version changed)~
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Closes #8.

This repo needs a bit of TLC to come up to speed. That should be the foundation to include the outstanding version updates and pave the way to bring subversion to arm64.

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@mariusvniekerk, could you please have a look? This is the first step towards bringing subversion to arm64. If you agree, I will next take care of version updates here, then migrate to arm64 and then move on to the rest of the deps.

@conda-forge/core, I'd like to move the migration of subversion to arm64 forward. Could you have a look?

you don't want to update the version too? it looks quite old. But it seems you want to start with this, then update the version later?

@hmaarrfk that's exactly my thinking. Since there are a number of versions outstanding, I wanted to try to successively build those to give us options.


Clean up dashboards

Have a dashboard running on Unix, Windows and Mac.
Have the dashboard run the tests

Thanks to @matthieuheitz, the mac dashboard should run tonight (see 155a52b71173afabf895ab11d3f1117966d0c2d3)

Fixed Errai dashboard: eb2f43aa31026387d9c94ef77bbb817c4948959c

Keep me updated if it works or not :smiley:

@matthieuheitz
Move Errai from an experimental build to a nightly build

maybe try to set the variable dashboard_track to make it appear in the good track

@matthieuheitz Seems the nighly bat file is already associated with nightly .. see https://github.com/KitwareMedical/VesselView/blob/44bc96e37bbb75a08057da26701cc1ce14d9ff61/Utilities/Dashboards/VesselView-errai-master-nightly.cmake#L21

It's not for errai, it's for Kitwares-MacBook-Pro.
https://github.com/KitwareMedical/VesselView/blob/44bc96e37bbb75a08057da26701cc1ce14d9ff61/Utilities/Dashboards/VesselView-Kitwares-MacBook-Pro-master-nightly.cmake#L22
It's the same thing, but in the dashboard, it doesn't appear in the same
section as the others.
I cannot find the usual view of the dashboards on the TubeTk dashboard, has
it been updated ? https://open.cdash.org/index.php?project=TubeTK
On Mon, Feb 16, 2015 at 11:26 AM, Jean-Christophe Fillion-Robin <
<EMAIL_ADDRESS>wrote:

@matthieuheitz https://github.com/matthieuheitz Seems the nighly bat
file is already associated with nightly .. see
https://github.com/KitwareMedical/VesselView/blob/44bc96e37bbb75a08057da26701cc1ce14d9ff61/Utilities/Dashboards/VesselView-errai-master-nightly.cmake#L21
—
Reply to this email directly or view it on GitHub
https://github.com/KitwareMedical/VesselView/issues/45#issuecomment-74534274
.

Hi Matthieu,
Humm .. looking at the TubeTK dashboard, you probably mean this build
"VesselView-Windows-VS2010Express-64-QT4.8.4-CMake3.0.2-Release"
Check the associated script and scheduled tasks ..
Thanks
Jc
On Mon, Feb 16, 2015 at 11:42 AM, Matthieu Heitz<EMAIL_ADDRESS>wrote:

It's not for errai, it's for Kitwares-MacBook-Pro.
https://github.com/KitwareMedical/VesselView/blob/44bc96e37bbb75a08057da26701cc1ce14d9ff61/Utilities/Dashboards/VesselView-Kitwares-MacBook-Pro-master-nightly.cmake#L22
It's the same thing, but in the dashboard, it doesn't appear in the same
section as the others.
I cannot find the usual view of the dashboards on the TubeTk dashboard, has
it been updated ? https://open.cdash.org/index.php?project=TubeTK
On Mon, Feb 16, 2015 at 11:26 AM, Jean-Christophe Fillion-Robin <
<EMAIL_ADDRESS>wrote:

@matthieuheitz https://github.com/matthieuheitz Seems the nighly bat
file is already associated with nightly .. see

https://github.com/KitwareMedical/VesselView/blob/44bc96e37bbb75a08057da26701cc1ce14d9ff61/Utilities/Dashboards/VesselView-errai-master-nightly.cmake#L21

—
Reply to this email directly or view it on GitHub
<
https://github.com/KitwareMedical/VesselView/issues/45#issuecomment-74534274
.

—
Reply to this email directly or view it on GitHub
https://github.com/KitwareMedical/VesselView/issues/45#issuecomment-74536834
.

--
+1<PHONE_NUMBER>


Stellargraph model does not improve over multiple epochs

When I am using stellargraph and I fit the generator to my training data, the accuracy and the loss remain the same over all the epochs. I always get this warning when I run following code:
history = model.fit_generator(     train_gen,     epochs=50,     validation_data=val_gen,     verbose=2,     shuffle=False,       callbacks=[es_callback, mc_callback], )

WARNING:tensorflow:From C:\Users\X\Anaconda3\lib\site-packages\tensorflow\python\ops\math_grad.py:1250: add_dispatch_support..wrapper (from tensorflow.python.ops.array_ops) is deprecated and will be removed in a future version.
Instructions for updating:
Use tf.where in 2.0, which has the same broadcast rule as np.where

I don't know if the warning has anything to do with this. I played around with all parameters and I used a weighted loss function and I also switched weights.

I'm using Stellargraph version 0.8.4; Python 3.6; NetworkX 2.3.
Given that I followed the example code when building the stellargraph and given I don't get an error code, I assume that the problem occurs during the preprocessing step.
I built the network on 1 node type (transaction) and I connected the transaction nodes to eachother when they had the same merchant/client ID.
I used the undirected GraphSAGE method.
G= nx.Graph()

G.add_nodes_from(target_data.transid)
edgelist = []
for i  in range(len(target_data.client)):
    for j in range(len(target_data.client)):
        if target_data.client.iloc[i] == target_data.client.iloc[j]:
            edgelist.append([target_data.transid.iloc[i], target_data.transid.iloc[j]])

print(edgelist)
edgelist2 = []
for i  in range(len(target_data.merchant)):
    for j in range(len(target_data.merchant)):
        if target_data.merchant.iloc[i] == target_data.merchant.iloc[j]:
            edgelist2.append([target_data.transid.iloc[i], target_data.transid.iloc[j]])

Then I added the edges from the two edgelists while removing the selfloop_edges
Next, I made all features numeric
train_gen = generator.flow(train_data.transid, train_targets, shuffle=True)
The node features I use only have 5 columns. When looking at the example code, I noticed that the number of columns is a lot higher. Could this be a problem?
The weird thing is that it predicts only the minority class (of which only 2 instances were fed to the train generator). The most logical problem would be that it'd predict only the majority class, however, in my case, it predicts the minority class.
Another difference between my code and the example code is that my node features can be large numerical values, whereas in the example code, it is mainly between 0 and 1. However, it remains weird that the model does not improve and predicts the minority class.


Resolve an issue with add functionality when budget is not set and you add an expense

Looks like if budget is not set and we add an expense it shows the exception.
Line number : 134 in add.py

Recreated the issue in my local and adding telegram conversation here

Raised a pr for the issue https://github.com/tpanati/DollarBot/pull/39


Typing error in subscription-faq.md?

taster or tester? pretty sure we are not tasting something

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

taster or tester? pretty sure we are not tasting something

:laughing: It is actually correct (2nd definition from https://dictionary.cambridge.org/dictionary/english/taster is "a small amount or short experience of something") but I can see how this is confusing!
I'm actually working on a complete revamp of the site at the moment, so I can't merge this directly, but I will find a way to make sure this is rephrased on the new site once it's live, it could definitely be clearer. Thanks for the suggestion @spiritualnulll!


Failed to compile with error when trying to use a 3rd party data generator file like "namorjs"

Describe the bug
When trying to use a library like namor.js to generate mock data, story fail to compile throwing issues about crypto.randomBytes inaccessible

It's not necessary about using Namor.js. I'm happy to use any library, but given that crypto.randomBytes is part of a Node.js, I think it might be necessary to look into the issue
Reproduction
See the stackblitz -> Controls.tsx story.
https://stackblitz.com/edit/ladle-5uhk6y?file=package.json,src%2Fcontrols.stories.tsx
Environment

OS: IOS
Browser: chrome
Version: 104.0.5112.101 (Official Build) (x86_64)

I'm happy to use any library, but given that crypto.randomBytes is part of a Node.js, I think it might be necessary to look into the issue

So why would you expect it to work in browser (as a part of story)?

i think it's use case that might happen where user uses library to generate mock data for a story. I've use the same library in Storybook to do things like that and it's working as expected.

It probably works in Storybook because Webpack 4 polyfills crypto out of the box (removed in Webpack 5).
You can attempt resolve.alias crypto to something like crypto-browserify but I would strongly recommend avoiding this altogether and just using some other library that's built for browsers.


problem about config path in windows

Can I use your code to train in the windows system?
I tried once ,but I found the config path is not suit for the code,like the path below

Can you tell me how to change the path Thanks

@yuyijie1995  you can change ("") into ("/")
it would be like: "train_image_folder: "D:/postgraduateworking/yolo3keras/keras-yolo3-master/images/"


Change Int to Int32 in DatabaseType array documentation

The example mentioned, casting to [Int] does not actually work because Int is not a type that is supported by VectorElementDataDecoder.SingleValueContainer. Doing so causes an infinite loop inside VectorElementDataDecoder as it tries to decode an unsupported type. Here's a minimal repro for that issue:
let connection = try Database(store: .inMemory).connect()
try connection.execute("""
  CREATE TABLE list_table (int_list INT[]);
  INSERT INTO list_table VALUES ([1, NULL, 3]);
""")
let results = try connection.query("SELECT * FROM list_table");
print(results[0].cast(to: [Int?].self)[0] ?? [])

For now, this PR fixes the docs so the example described works. There should then be an additional change to either:
a) Add Int/UInt as supported types (mapping to either Int32/Int64 based on the platform)
b) Throw an immediate error on an unsupported type without going into the infinite decoding loop
I'm also happy to make one of these two changes, let me know which one you'd prefer.

Oops, missed that I should open a PR on the main repo. Opened as: https://github.com/duckdb/duckdb/pull/7318


Debugging is slowing down our processing

Hello Guys,
I recently integrated camelot to convert my pdf files to dataframes, with a fastapi upload process. Currently the processing time is taking 3mins per file after digging deeper i found out this is because of the pdfminer.psparser debugging, would it be possible to have this turned off.

Do you mean the log.debug statements?
Can you be more precise about what is slowing it down? Did you use a profiler?

@professorr-x I also use Camelot and I am all for having faster running processes. Would be great if you posted your findings and we could look into options of seeing what could be done to speed this up.

Hi guys,
As a workaround, you may disable logging by adding these lines of code after importing the PDFMiner libraries:
`from pdfminer import pdfinterp, psparser, pdfdocument, pdfpage, cmapdb, pdfparser
import logging
pdfinterp.log.level = logging.ERROR
psparser.log.level = logging.ERROR
pdfdocument.log.level = logging.ERROR
pdfpage.log.level = logging.ERROR
cmapdb.log.level = logging.ERROR
pdfparser.log.level = logging.ERROR
logging.getLogger("pdfminer").setLevel(logging.ERROR)`
I hope this helps.

I don't think the logging is actually slowing this package down.
Debug logs are not formatted if it can be avoided. If you disable the debug logs (by default) the only overhead is an empty function call.
If you experience otherwise, feel free to share a reproducible example that shows that debug logs slow pdfminer down.


Implement BreadcrumbNav Component(s)

@patrickdevivo
icons always should be there, or they should match to each element?

Icon should be passable as a prop to each "section" of the breadcrumb, so user can decide whether to display an icon or not based on context.


"untrusted X11 forwarding" causes createReleaseTag to fail

This is not a fatal error, usually, but it looks like this message is being picked up as an error and causing the createReleaseTag task to fail.
Here's my output with --info:
Running [git, remote] in [/Users/bedge/git/server/store-develop]
Running [git, remote] produced output: []
Running [git, push, --porcelain, origin, 3.49.0] in [/Users/bedge/git/server/store-develop]
Running [git, push, --porcelain, origin, 3.49.0] produced output: []
Running [git, push, --porcelain, origin, 3.49.0] produced an error: [Warning: untrusted X11 forwarding setup failed: xauth key data not generated
X11 forwarding request failed on channel 0
remote: === hooks/update.secondary.d/catch-conflicts.sh ===
remote: ==== hooks/update.secondary.d/check-forbidden-names.sh ====
remote: fatal: Invalid revision range<PHONE_NUMBER>000000000000000000000000000000..34cb9ec24a5b22e2bb3d2ee866bf0ec430e255bc]
:store-develop:createReleaseTag FAILED
:createReleaseTag (Thread[Daemon worker Thread 18,5,main]) completed. Took 2.087 secs.

Fixing the hook that was complaining about t rev range:
remote: fatal: Invalid revision range<PHONE_NUMBER>000000000000000000000000000000..34cb9ec24a5b22e2bb3d2ee866bf0ec430e255bc]

git rid of the problem.
I suppose one could argue that parsing stdout for errors is not reliable as the command can complete successfully but still log error messages.


REST API tests refactoring (Part 3)

Description
Removed test:

SecurityHealthActionTest
LegacySecurityHealthActionTests

The test moved into DefaultApiAvailabilityIntegrationTest`
Check List

[ ] New functionality includes testing
[ ] New functionality has been documented
[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Capturing this to look back on later.
The new tests are located here: https://github.com/opensearch-project/security/blob/main/src/integrationTest/java/org/opensearch/security/api/DefaultApiAvailabilityIntegrationTest.java#L66-L70
And securityPath does randomization to pick the legacy _opendistro/ prefix or _plugins: https://github.com/opensearch-project/security/blob/main/src/integrationTest/java/org/opensearch/security/api/AbstractApiIntegrationTest.java#L248-L256


This makes QGC connect with crazyflie

Discussed in https://github.com/PX4/Firmware/issues/8924

@bueng is the crazyradio UART correctly configured and all input handling (CR, LF) disabled? This change looks like it’s working around that.

Please compare how the UART is configured in the MAVLink app. It needs that.

The change here looks strange to me too. I already gave @barzanisar a commit to test that changes the settings to disable input handling (as gps does): https://github.com/bkueng/Firmware/commit/b8ba1b74436f0be29469c1c7c9de0a2b8e6ecaa8. @barzanisar can you try this again instead?

Ok I tried @bkueng 's changes instead and QGC connects.  So I guess no need to change # CONFIG_DEV_LOWCONSOLE to CONFIG_DEV_LOWCONSOLE=y


feature: Raft-based message queues

This FINALLY closes #1.
This is a bit WIP still, but the groundwork is there at least.

Also yay fun PR number


feat: Add KubeRocketCI platform to the CI/CD Stack

We've changed the brand from the EPAM Delivery Platform (EDP) to the KubeRocketCI. And this is the first step on our migration path. The EDP will be removed in the next PRs
Thank you for wanting to submit a Pull Request to the Civo Kubernetes Marketplace repository!
If your pull request is to submit a new application to the marketplace, please answer the following questions:

[x] Have you followed the guidelines in our Contributing document in setting up the application?
[x] Have you checked that the application your submission is proposing to add does not yet exist on the Marketplace, or as a pull request to be processed?
[x] Have you tested your application on the Civo managed Kubernetes service? Please include a screenshot.
[x] Can you confirm that the software you are submitting licensed for use in a publicly-available Kubernetes marketplace?
[x] Have you included the specific version of the application to be installed?

If your pull request concerns an existing Marketplace application, please make sure you have:

[ ] Notified the Maintainer of the application in this pull request so that they are aware of your proposal.
[ ] Outlined the changes you are proposing, and the reasons these are required (e.g. stability, compatibility with new versions of Kubernetes implementations, etc).
[ ] Tested that the application works with the proposed updates applied (including a screenshot).
[ ] Updated the version number of the app if that has changed.

Hello, @kunal-kushwaha @civo-claire, any chance for review and merge? Thank you

@kunal-kushwaha here is how I checked:
Create Job:
apiVersion: batch/v1
kind: Job
metadata:
  name: install-kuberocketci
  namespace: default
spec:
  parallelism: 1
  completions: 1
  backoffLimit: 0
  manualSelector: false
  template:
    spec:
      containers:
        - name: install-kuberocketci-demo
          image: gcr.io/consummate-yew-302509/marketplace-installer:latest
          args:
            - install
            - kuberocketci
            - '-d'
            - https://github.com/SergK/kubernetes-marketplace.git
          env:
            - name: GITPROVIDER
              value: github
            - name: CLUSTER_ID
              value: 11d73884-0482-4364-9cfa-b6a74a5e7562
          resources: {}
          terminationMessagePath: /dev/termination-log
          terminationMessagePolicy: File
          imagePullPolicy: Always
      restartPolicy: Never
      terminationGracePeriodSeconds: 30
      dnsPolicy: ClusterFirst
      serviceAccountName: default
      serviceAccount: default
      securityContext: {}
      schedulerName: default-scheduler
  ttlSecondsAfterFinished: 172800
  completionMode: NonIndexed
  suspend: false
  podReplacementPolicy: TerminatingOrFailed

Check the results of the installer job (I've use repo from pull request):
{"time":"2024-07-02T13:50:57.225655312Z","level":"INFO","msg":"Cloneing git repo https://github.com/SergK/kubernetes-marketplace.git\n"}
{"time":"2024-07-02T13:50:57.225936479Z","level":"INFO","msg":"Creating temp dir to clone git repo"}
{"time":"2024-07-02T13:50:57.226185834Z","level":"INFO","msg":"Created temp dir: /tmp/prefix1235398467"}
{"time":"2024-07-02T13:50:58.527034416Z","level":"INFO","msg":"Validating that app exists: kuberocketci\n"}
{"time":"2024-07-02T13:50:58.527106429Z","level":"INFO","msg":"Running App PreInstall"}
{"time":"2024-07-02T13:50:58.52714973Z","level":"INFO","msg":"Cheking the pre_install.sh is preset or not"}
{"time":"2024-07-02T13:50:58.527198971Z","level":"INFO","msg":"No pre_install.sh found fo kuberocketci"}
{"time":"2024-07-02T13:50:58.527209019Z","level":"INFO","msg":""}
{"time":"2024-07-02T13:50:58.527216717Z","level":"INFO","msg":"Running App Install"}
{"time":"2024-07-02T13:50:58.528143507Z","level":"INFO","msg":"Cheking the install.sh is preset or not"}
{"time":"2024-07-02T13:50:58.528179717Z","level":"INFO","msg":"Running the install.sh"}
{"time":"2024-07-02T13:50:58.528202975Z","level":"INFO","msg":"Making the shell file executable"}
{"time":"2024-07-02T13:50:58.532646279Z","level":"INFO","msg":"Command output","stdout":""}
{"time":"2024-07-02T13:50:58.532716075Z","level":"ERROR","msg":"Command output","stderr":""}
{"time":"2024-07-02T13:50:58.532728878Z","level":"INFO","msg":"Running the shell file"}
{"time":"2024-07-02T13:50:58.532811143Z","level":"INFO","msg":"Shell file contents","shellFile":"OMIT-HERE=="}
{"time":"2024-07-02T13:51:15.28938529Z","level":"INFO","msg":"Command output","stdout":"\"epamedp\" has been added to your repositories\nHang tight while we grab the latest from your chart repositories...\n...Successfully got an update from the \"epamedp\" chart repository\nUpdate Complete. ⎈Happy Helming!⎈\ndeployment.apps/tekton-pipelines-webhook condition met\nclusterinterceptor.triggers.tekton.dev/cel unchanged\nclusterinterceptor.triggers.tekton.dev/github unchanged\nclusterinterceptor.triggers.tekton.dev/gitlab unchanged\nnamespace/edp created\nNAME: edp\nLAST DEPLOYED: Tue Jul  2 13:51:00 2024\nNAMESPACE: edp\nSTATUS: deployed\nREVISION: 1\nTEST SUITE: None\n"}
{"time":"2024-07-02T13:51:15.289548932Z","level":"ERROR","msg":"Command output","stderr":""}
{"time":"2024-07-02T13:51:15.289617382Z","level":"INFO","msg":"\"epamedp\" has been added to your repositories\nHang tight while we grab the latest from your chart repositories...\n...Successfully got an update from the \"epamedp\" chart repository\nUpdate Complete. ⎈Happy Helming!⎈\ndeployment.apps/tekton-pipelines-webhook condition met\nclusterinterceptor.triggers.tekton.dev/cel unchanged\nclusterinterceptor.triggers.tekton.dev/github unchanged\nclusterinterceptor.triggers.tekton.dev/gitlab unchanged\nnamespace/edp created\nNAME: edp\nLAST DEPLOYED: Tue Jul  2 13:51:00 2024\nNAMESPACE: edp\nSTATUS: deployed\nREVISION: 1\nTEST SUITE: None\n"}


Problem with orderBy

When you fill a tree with ngrepeat and orderBy, if you drag and drop an item, it fails and drop the item that was in the source position without orderBy applied.
It's possible? Or is my fault?

@clementprevot - In my case I'm not using drag/drop but I still am unable to use a custom orderBy. Is this a known limitation? Anything that could be done to fix it?

Use filter in your controller to sort data
$scope.TreeObject = $filter('orderBy')(data, 'Sort');


fix microsoft/vscode#117095 de-duplicate reference results

This commit de-duplicates reference and other location results from
API endpoints executeDefinitionProvider, executeDeclarationProvider,
executeImplementationProvider, executeTypeDefinitionProvider, and executeReferenceProvider
(all commands registered in goToSymbol.ts which share the
getLocationsLinks helper).
Previously, this work was only done in the ReferencesModel which is used by
the editor.action.findReferences command. Extensions which called the
vscode.executeReferenceProvider would still get the duplicate results.
fix microsoft/vscode#117095

Thanks

@atscott I'm not sure if I'm in the right place but -
I use these settings:
  "editor.gotoLocation.multipleDefinitions": "goto",
  "editor.gotoLocation.multipleTypeDefinitions": "goto",
  "editor.gotoLocation.multipleDeclarations": "goto",
  "editor.gotoLocation.multipleImplementations": "goto",
  "editor.gotoLocation.multipleReferences": "goto",

With previous public build when clicking through on a JSX element like:
<MyComponent foo />

It would go to the spot where MyComponent was defined in my source code
With current public build it now goes to the React jsx definition for what a Component is.
In essence, with previous build the goto would go to the last (?) reference that it found, which was always (?) the source code definition. Now it seems to go to the first?

@coreylight - this is likely due to the sorting change.
@jrieken - The change to the result order by sorting the references rather than maintaining results based on the registration order may have some unforeseen consequences like what @coreylight mentioned. What are your thoughts on this?

With current public build it now goes to the React jsx definition for what a Component is.

That's an issue with TypeScript (likely https://github.com/microsoft/vscode/issues/119086) and unrelated to the work here

wait, maybe it is an issue with the sorting...


Spotify Player v2

Description
Spotify Player first launched in October 2021. It was one of our first extensions, and to this day it stands as one of the most popular in the store. Since then, we've learned a lot, received plenty of feedback, and released new, more performant APIs.
So now it's time for a refresher ✨
Spotify Player v2 is a complete re-write, focusing on performance, maintainability, and user experience. One of our main goals was to keep the list of commands to a minimum but still allow users to tailor their own experience. This way, both new users of Raycast, as well as more advanced ones, can make the most of Spotify Player.
New Features

Updated Extension icon
Updated Menu Bar icon
Support Podcasts and Episodes in "Now Playing"/"Menu Bar Player"
Support Podcasts and Episodes in "Search"/"Your Library"
Support "Transfer Playback" action, available in "Now Playing"/"Menu Bar Player"
Support "Add to Playlist" action, available in "Now Playing"/"Menu Bar Player"

New Commands

Search: A single unified search command. Use this to search for artists, albums, songs, playlists, podcasts, and episodes. Use the dropdown menu to filter your search to a specific category. Each category offers contextual actions, so you can dive deeper into the search.
Your Library: Use this to see your saved artists, albums, songs, playlists, and podcasts. Similar to the "Search" command, it includes a category dropdown and contextual actions.
Quick Actions: This is a list of lots of Spotify actions. For example: Play/Pause, Like/Dislike current song, Change Volume, and more. If you'd like to have any of these available as a Root Command, you can create Quicklinks via the actions menu (⌘ K).
Toggle Play/Pause: Use this to toggle the playback of the current song.
Next: Use this to skip to the next song/episode.
Previous: Use this to skip to the previous song/episode.

Disabled Commands
This extension includes a few commands that are disabled by default. You can enable them by going to the extension's settings. These commands are:

Like:
Use this to like the current song.
Dislike:
Use this to dislike the current song.
Set Volume to 0%:
Use this to mute the volume.
Set Volume to 25%:
Use this to set the volume to 25%.
Set Volume to 50%:
Use this to set the volume to 50%.
Set Volume to 75%:
Use this to set the volume to 75%.
Set Volume to 100%:
Use this to set the volume to 100%.
Turn Volume Down:
Use this to turn the volume down by 10%.
Turn Volume Up:
Use this to turn the volume up by 10%.
Toggle Shuffle:
Use this to toggle shuffle.
Toggle Repeat:
Use this to toggle repeat.
Start Radio:
Use this to start a radio station based on the current song.
Copy URL:
Use this to copy the URL of the current song/episode.
Just Play:
Use this to quickly start playing a song based on your query.

Removed Commands

Search Artists: Use "Search" instead. You can use the dropdown menu to narrow your search to artists only
Search Albums: Use "Search" instead. You can use the dropdown menu to narrow your search to albums only
Search Tracks: Use "Search" instead. You can use the dropdown menu to narrow your search to songs only
Search Playlists: Use "Search" instead. You can use the dropdown menu to narrow your search to playlists only
Browse All: Use the Spotify App instead
Featured Playlists: Use the Spotify App instead

General improvements

Menu Bar Player Preferences: "Max Text Length" has a default value of 20
Menu Bar Player Preferences: "showEllipsis" setting has been removed. It'll always show ellipsis if the title needs to be truncated (based on the "Max Text Length" setting)

We hope you enjoy the new and improved Spotify Player Extension — we've obsessed over every detail.
Screencast
Here's a video walkthrough: https://www.youtube.com/watch?v=UtHobW2HR0A
Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

@peduarte Is there a way to hide the icon when nothing is playing? This used to be the old behaviour. I listen to music like 30% of the day so I really don't enjoy the fact that it now shows an icon the other 70% of the day.

@florisdg https://github.com/raycast/extensions/pull/7735


Suggestion: Don't display turnip price averages or min/max values for days where data has been entered

When turnip pricing data has been entered, it would seem sensible to display the actual price it was on those days rather than the average, or min/max prices. If data wasn't entered, maybe just a - for that day. It could also use a different colour for days that re real data, rather than predictions? Just to make it even clearer.
That way, at a glance, I can see which days my predictions are based on, and what those prices were. At the same time, it makes it clear that future days are predictions.

Totally on point, I think the ideal solution would be to display the - for average and the exact price in min - max / profits
It's in the work but we're not yet totally happy with it
https://github.com/Dimillian/ACHNBrowserUI/pull/156

Fab! Feel free to close this if it's being taken care of in #156.

🚀

Yeah will be in next update :) thanks to @renaudjenny


Fix Foxx API error

Manager should distinguish between errors and services
Foxx API should not require service to exist for uninstall
if force option is used

YOLO :man_shrugging:


Predefined scope appears to be resetting

Pre-existing scopes for projects appear to be reset upon opening a project.
Steps to reproduce:

Using burpsuite, open a new project & add https://example.com to the scope. Exit burpsuite.
Using burp-rest-api, open the previously created project. At this point it appears that the https://example.com scope is no longer there.

Burpsuite version: 1.7.34

If you are using burpa with it, then you should make a curl before you start your tests. It helps

I believe you're using the wrong argument for loading the configuration file.
On the latest release, the following command works and properly restores the scope:
$ java -jar burp-rest-api-2.0.0.jar --headless.mode=false --burp.jar=./lib/burpsuite_pro_v2.0.10.jar --config-file=<PATH TO Project Config File .json>


Machine Learning Pipeline usage

I have questions on the step number 2, "A preconfigured pipeline in Azure Machine Learning".
I was wondering what this step should do ?
Since what i understand, the video will be split into frames, and then the image will be classified/detection using the Azure Vision AI.
So the detection is in the Azure Vision.
What is the purposed machine learning on step number 2 ?

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

ID: 8baf9729-fadf-83d7-e449-50a1b98e8159
Version Independent ID: 8baf9729-fadf-83d7-e449-50a1b98e8159
Content: Analyze video content with Computer Vision and Azure Machine Learning - Azure Architecture Center
Content Source: docs/ai-ml/architecture/analyze-video-computer-vision-machine-learning.yml
Service: architecture-center
Sub-service: example-scenario
GitHub Login: @OscarSH
Microsoft Alias: oscarsh

@eftech13
Thanks for your feedback! We will investigate and update as appropriate.

The pipeline in AML is pre-configured so that we are automating some notebooks where we've previously wrote some code which is able to handle the decomposition of frames. The code was written in Python and is using ffmpeg. The rest of the statement "the video will be split into frames, and then the image will be classified/detection using the Azure Vision AI.
So the detection is in the Azure Vision" is correct. AML pipeline is only used to orchestrate the notebooks.

We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


fix(PeriphDrivers): Calculate I3C timeout based on data size

Description
Default timeout values used for transactions fall short on large data transfers. Use data size and SCL frequency to calculate a proper timeout value.
Below formulas are used to come up with rough estimations.
timeout = (40 * period_in_us) * writeCount
timeout = (80 * period_in_us) * readCount

Will merge after Alperen reviews.


Unable to reproduce the result

Sir
I successfully created the environment with the YAML file given in the repository. But I got the following error. Could you please help me to sort it out. For your information I am using NVIDIA RTX A5000 GPU.

Hello @sastry3009,
The issue you're facing stems from the incompatibility between sm_86 and the current version of PyTorch. To resolve this, you'll need CUDA11+ for your Ampere GPU, whereas your current installation relies on cudatoolkit=<10.2, which won't function properly. The CUDA10.2 binaries don't include sm_86 for the same reason. To fix the problem, please install the CUDA11.3 binary. If you encounter any conflicts, I recommend creating a new conda environment and reinstalling it. Additionally, when using Torch-Nilm, ensure that you can change the version of PyTorch (this will not produce any conflict) and try using only one GPU (without DDP) to ensure smooth operation. Let me know if this solution resolves the issue for you.


AnimatedSize needs an example

Especially because of the vsync argument.

Will this code do? It shows how AnimatedSize can be used to animate inflating of images once loaded instead of simply popping them.
import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Code Sample for AnimatedSize',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: MyStatefulWidget(),
    );
  }
}

class MyStatefulWidget extends StatefulWidget {
  MyStatefulWidget({Key key}) : super(key: key);

  @override
  _MyStatefulWidgetState createState() => _MyStatefulWidgetState();
}

class _MyStatefulWidgetState extends State<MyStatefulWidget>
    with TickerProviderStateMixin {
  Widget build(BuildContext context) {
    return Scaffold(
      body: Center(
        child: AnimatedSize(
          vsync: this,
          duration: const Duration(milliseconds: 500),
          child: Image.network('https://picsum.photos/300/500'),
        ),
      ),
    );
  }
}

OUTPUT

Someone did use this with stateless widget or only with a single widget? thanks


A few fixes for nemesis' Windows port

Awesome, thanks!
Q: Is there some Windows code that uses u_int32_t?

You're very welcome.

Q: Is there some Windows code that uses u_int32_t?

u_int32_t is in udp_cmdline() in nemesis-udp.c
Windows is generally totally unaware of these u_* types

Ah, my bad. I thought I had replaced all of them with their stdint.h counterparts during the weekend, must've missed that single one.  Thanks for noticing this! fixing

Fixed in 14c7c0c.

👍


module field in 3rd-party package.json compile error --aot

Bug Report or Feature Request (mark with an x)
- [X] bug report -> please search issues before submitting
- [ ] feature request

Versions.
@angular/cli: 1.0.1
node: 8.6.0
os: darwin x64
@angular/animations: 4.1.0
@angular/common: 4.1.0
@angular/compiler: 4.1.0
@angular/core: 4.1.0
@angular/forms: 4.1.0
@angular/http: 4.1.0
@angular/platform-browser: 4.1.0
@angular/platform-browser-dynamic: 4.1.0
@angular/router: 4.1.0
@angular/cli: 1.0.1
@angular/compiler-cli: 4.1.0
@angular/language-service: 4.1.0
Repro steps.
When importing a library that uses the "module" entry in their package.json file --aot build fails with the Unexpected token: name  Error.
I've encountered this with the dates-chinese package since lately they added the "module" entry point that points to es2015 code.
After that change, my ng builds are failing.
The log given by the failure.
ERROR in 0.a821737870a81bd01043.chunk.js from UglifyJs
Unexpected token: name (CalendarVietnamese) [0.a821737870a81bd01043.chunk.js:8779,6]

npm verb lifecycle @rcenter/backoffice@0.0.1~build:staging: unsafe-perm in lifecycle true
npm verb lifecycle @rcenter/backoffice@0.0.1~build:staging: CWD: /Users/dmitrigrossman/projects/rec-backoffice
npm info lifecycle @rcenter/backoffice@0.0.1~build:staging: Failed to exec build:staging script
npm verb stack Error<EMAIL_ADDRESS>build:staging: `ng build --env=staging --aot --prod`
npm verb stack Exit status 1
npm verb stack     at EventEmitter.<anonymous> (/Users/dmitrigrossman/.nvm/versions/node/v8.6.0/lib/node_modules/npm/lib/utils/lifecycle.js:289:16)
npm verb stack     at emitTwo (events.js:125:13)
npm verb stack     at EventEmitter.emit (events.js:213:7)
npm verb stack     at ChildProcess.<anonymous> (/Users/dmitrigrossman/.nvm/versions/node/v8.6.0/lib/node_modules/npm/lib/utils/spawn.js:40:14)
npm verb stack     at emitTwo (events.js:125:13)
npm verb stack     at ChildProcess.emit (events.js:213:7)
npm verb stack     at maybeClose (internal/child_process.js:927:16)
npm verb stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)

Desired functionality.
Is this something need to be fixed on the cli? or am I doing something wrong?

The module entry is expected to be es5 with es2015 modules; not full es2015.  Angular packages use an additional “es2015” entry to point to full es2015 code.

@scopsy Please try the suggestion by @clydin above.
If successful, please close this issue... Thanks!


catch invalidPDFException in getImagesFromPDF when pdf is boken

Prerequisites
Put an X between the brackets on this line if you have done all of the following:

[X] Reproduced the problem or exposed a new need
[X] Checked the github existing issues

Description
React mindee js is missing a catch block getImagesFromPDF method.
When an remote PDF Url is corrupted (for example file size is 0 bytes or cannot be parsed) the pdf-dist library throw invalidPDFException.
Since it's not catched it cannot be on our side of the code
Steps to Reproduce

call method getImagesFromPDF with a broken file ex: fb375f80-ccbf-4829-b61b-f1764b017221.pdf

Expected behavior:
if an error occurs the catch block should be called
      getImagesFromPDF(src)
        .then((pages: string[]) => {
        })
        .catch(() => {
          // --> HERE
        });

Actual behavior:
      getImagesFromPDF(src)
        .then((pages: string[]) => {
        })
        .catch(() => {
          // --> THE ERROR IS NEVER CATCHED
        });

Reproduces how often:
100%
Versions
"react-mindee-js": "1.3.7",
Additional Information
Patch to fix the bug and handle error in promise
diff --git a/node_modules/react-mindee-js/dist/utils/getImagesFromPDF.js b/node_modules/react-mindee-js/dist/utils/getImagesFromPDF.js
index c85c266..91ad2ac 100644
--- a/node_modules/react-mindee-js/dist/utils/getImagesFromPDF.js
+++ b/node_modules/react-mindee-js/dist/utils/getImagesFromPDF.js
@@ -50,6 +50,8 @@ export default function getImagesFromPDF(file, maxPages = Infinity, onSuccess, r
                 .catch((e) => {
                 reject({ error: e });
             });
+        }).catch((e) => {
+            reject({ error: e });
         });
     });
 }

Hello @nicolibeo
Thank you for reporting the issue. We will schedule a minor patch release to fix this shortly.

A new version of the package v1.3.9 was released to handle the current issue.


Refactor IDR round 1

This is the first of several PRs involved in refactoring these playbooks and variables. Mostly involves moving and renaming.

Rearranges the IDR baremetal playbooks into an idrsystems group (to distinguish it from the IDR itself)
See README.md for explanation of the two toplevel idrsystems-*yml playbooks

One thing I'm uncertain about is whether idrsystems-playbook/idr-initial.yml should actually be a top-level standalone playbook, since in most cases you should reboot the server after initialising the network card and updating system packages.

Merging as a first proposal for new directory names. I'll update gh-88 to match this structure and add onto the proposal. @manics will open the mgmt docs PR once PXE'ing is done.


jedi throwing errror while entering multi-line code

Trying to put in the multi-line code below. When I get to the o in 'for' it throws the exception below. To eliminate module issues I'm running ptpython from a minimal virtualenv.
>>> from timeit import timeit
  2 setup = """\
  3 import netaddr
  4 import netlib
  5 import struct
  6 import socket
  7 import ipcalc
  8 net = '<IP_ADDRESS>/24'
  9 ip = '<IP_ADDRESS>'
 10 filename='/tmp/nets_to_check'
 11 nets_to_check = netlib.slurp(filename=filename)
 12 print 'nets in nets_to_check', len(nets_to_check)
 13 """
>>> code = """\
  2 fException in thread Thread-296:
Traceback (most recent call last):
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", line 810, in __bootstrap_inner
    self.run()
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", line 763, in run
    self.__target(*self.__args, **self.__kwargs)e mode                                                                            [F2] Menu - CPython 2.7.10
  File "/Users/joeschmoe/dev/ptpython/lib/python2.7/site-packages/prompt_toolkit/interface.py", line 860, in run
    completions = list(buffer.completer.get_completions(document, complete_event))
  File "/Users/joeschmoe/dev/ptpython/lib/python2.7/site-packages/ptpython/completer.py", line 127, in get_completions
    completions = script.completions()
  File "/Users/joeschmoe/dev/ptpython/lib/python2.7/site-packages/jedi/api/__init__.py", line 171, in completions
    self._evaluator, self._get_module(), self._code_lines,
  File "/Users/joeschmoe/dev/ptpython/lib/python2.7/site-packages/jedi/api/__init__.py", line 396, in _get_module
    parser_module = super(Interpreter, self)._get_module_node()
  File "/Users/joeschmoe/dev/ptpython/lib/python2.7/site-packages/jedi/cache.py", line 89, in wrapper
    result = method(self, *args, **kwargs)
  File "/Users/joeschmoe/dev/ptpython/lib/python2.7/site-packages/jedi/api/__init__.py", line 137, in _get_module_node
    parser = FastParser(self._grammar, self._source, self.path)
  File "/Users/joeschmoe/dev/ptpython/lib/python2.7/site-packages/jedi/parser/diff.py", line 33, in __call__
    parser.module = parser._parsed = d.update(new_lines)
  File "/Users/joeschmoe/dev/ptpython/lib/python2.7/site-packages/jedi/parser/diff.py", line 203, in update
    % (last_pos, line_length, ''.join(diff))
Exception: There's an issue (1 != 2) with the diff parser. Please report:

$ pip freeze
appdirs==1.4.0
docopt==0.6.2
jedi==0.10.0
packaging==16.8
prompt-toolkit==1.0.13
ptpython==0.36
Pygments==2.2.0
pyparsing==2.1.10
six==1.10.0
wcwidth==0.1.7
>>> for d in sys.path:
  2     print d

/Users/joeschmoe/dev/ptpython/bin
/Users/joeschmoe
/Users/joeschmoe/dev/ptpython/lib/python27.zip
/Users/joeschmoe/dev/ptpython/lib/python2.7
/Users/joeschmoe/dev/ptpython/lib/python2.7/plat-darwin
/Users/joeschmoe/dev/ptpython/lib/python2.7/plat-mac
/Users/joeschmoe/dev/ptpython/lib/python2.7/plat-mac/lib-scriptpackages
/Users/joeschmoe/dev/ptpython/Extras/lib/python
/Users/joeschmoe/dev/ptpython/lib/python2.7/lib-tk
/Users/joeschmoe/dev/ptpython/lib/python2.7/lib-old
/Users/joeschmoe/dev/ptpython/lib/python2.7/lib-dynload
/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-darwin
/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-tk
/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-mac
/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-mac/lib-scriptpackages
/Users/joeschmoe/dev/ptpython/lib/python2.7/site-packages

I downgraded to jedi 0.9.0, which seems to have resolved the issue.

This is a bug in Jedi, but thanks for mentioning because we should suppress this bug.


this.req vs this.__req?

What is the difference between these two, "this.req" and "this.__req"? Various sample code I've been looking at uses both. I can't find anything in docs for locomotive, express, or node.

Sorry, this was probably better on SO, but here we are.

Assuming you are referring to code inside a controller, they are the same.  Use of this.req is preferred.  Underscores indicate things used internally, and should not show up in example code.

Thanks!


⚠ Bofrost.be has degraded performance

In 8d08233, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1149 ms

Resolved: Bofrost.be performance has improved in d9ff4fc after 6 minutes.


unsupport php7

Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Installation request for microweber/screen ^1.0.1 -> satisfiable by microweber/screen[v1.0.1].
- microweber/screen v1.0.1 requires php ~5.3 -> your PHP version (7.0.4) does not satisfy that requirement.

fixed by #57


Setup/build-time instructions for Docker images

Expected Behavior
I have a Docker image I'm building with the Micronaut Gradle Plugin. Specifically, it's an optimized native image, using the built-in GraalVM integration. It is generated in the following steps:

optimizedDockerfileNative is executed to build the dockerfile
optimizedDockerPrepareContext is executed to build the config dirs
optimizedBuildNativeLayersTask is executed to build the native layers

during this process, i copy a file, server.iprof, into the native image root, so that i can use PGO with my native image. the profile is generated ahead of time, so I just need to place it where Docker can find it, and execute a COPY ... instruction to make it available during subsequent native image builds.
so, i have added an instruction to do this:
optimizedDockerfileNative {
    graalImage.set("...")
    baseImage("...")
    args(*baseJvmArgs.plus(listOf(
      "...",
    )).toTypedArray())

    instruction("COPY server.iprof /home/app/server.iprof")
}

i expect this to be added at build-time, because all the runtime resources for the image are on the classpath, and embedded in the binary.
Actual Behaviour
rather than injecting this instruction during the build stage of the Dockerfile, using this mechanism, the instruction is injected during the runtime assembly stage:
FROM ... AS graalvm
WORKDIR /home/app
COPY layers/libs /home/app/libs
COPY layers/classes /home/app/classes
COPY layers/resources /home/app/resources
COPY layers/application.jar /home/app/application.jar
RUN mkdir /home/app/config-dirs
COPY config-dirs/generateResourcesConfigFile /home/app/config-dirs/generateResourcesConfigFile
COPY config-dirs/... /home/app/config-dirs/...
RUN native-image ... --pgo=server.iprof
FROM ...
EXPOSE 8080
COPY --from=graalvm /home/app/application /app/application

> COPY server.iprof /home/app/server.iprof < instruction injected here

ENTRYPOINT ["/app/application", "..."]

Steps To Reproduce

try to inject an instruction at build time
observe that the NativeImageDockerfile code does not inject from user instructions at such time

Environment Information

Operating System: macOS Ventura 13.2.1
JDK Version: 19 (GraalVM)

Example Application
No response
Version
3.8.7

perhaps there is a different instruction directive for build-stage? but i couldn't locate one in the source or docs. if a PR is welcome for this let me know and I think it would be a rather small change to add the same mechanism, but for build time (i.e. something like buildTimeInstruction(...)).


Inventory Kits

Need a new item category for Kits;

Kits contain several inventoried items,
Item count of kit will be # of kits it can make with current inventory.

"Item count of kit will be # of kits it can make with current inventory."
That is not the way to keep inventory. Instead, when a kit is sold, each item in the kit is decremented from stock.

Done!


Fixes #9151 - Drilldown event issue

Updated by mistake ... Correcting now!
Closes #9151

Not sure why we should remove the word menu, can you explain?

See #9151

The event name is still open.zf.drilldownMenu in docs, and needs to be open.zf.drilldown
Looks like it was fixed in f7e63fd by changing the docs title, but then the title was changed back 72844c8 for consistency. That probably reintroduced the issue.

Oh wow, the event is tied to the name in the docs? We will likely want to decouple that in the future.
Sounds good for now - thanks @IamManchanda !!

Then again... this shows why good commit messages are very important!
Your welcome @rafibomb ... please request you to deploy it soon also... thank you
Thanks @shready for helping us figure it out... thumbs up!


Generating AES B64 input for the decryptAES function with openssl

Output of helm version: version.BuildInfo{Version:"v3.6.2", GitCommit:"ee407bdf364942bcb8e8c665f82e15aa28009b71", GitTreeState:"dirty", GoVersion:"go1.16.5"}
Output of kubectl version: NA
Cloud Provider/Platform (AKS, GKE, Minikube etc.):  NA
I am trying to generate a base64 AES encrypted string to use with helm's decryptAES function. I'm using the following command in openSSL echo "encryptMe" | openssl aes-256-cbc -e -k examplePassword -nosalt -base64
When I take the ouput of that command and attempt to render it with the following:
password: {{ "+oaBHwsZhx6OeWmJDihT4Q==" | decryptAES "examplePassword" }}
I get the error:

Error: (removed)  at <decryptAES "examplePassword">: error calling decryptAES: runtime error: index out of range [-1]

Looking at the sprig library functions here:
https://github.com/Masterminds/sprig/blob/master/crypto.go#L597
It looks like the sprig functions aren't generating the IV the same way open-ssl is, but I'm not sure what value to set as the IV for openssl.
I would ask in the sprig github, but the project appears to be dead.
Any help would be greatly appreciated!

I would ask in the sprig github, but the project appears to be dead.

The project is still active - two of Helm's core maintainers are maintainers of that project. I would suggest continuing the discussion in the relevant repository - there's nothing we can do here other than contribute PRs to sprig.
Thanks.


Unexpected error: expected declaration, found 'package'

This version of my test project ...
https://github.com/st3fan/hello-templ/tree/2180138d135afbc505cc8960dfaa4eab61fb69d7
... is giving me the following errors that I don't understand:
templ generate
Processing path: /Users/stefan/go/src/github.com/st3fan/hello-templ
Generated code for "/Users/stefan/go/src/github.com/st3fan/hello-templ/hello.templ" in 1.097917ms
Error processing path: /Users/stefan/go/src/github.com/st3fan/hello-templ/page.templ source formatting error: 16:1: expected declaration, found 'package'
/Users/stefan/go/src/github.com/st3fan/hello-templ/counter.templ source formatting error: 16:1: expected declaration, found 'package' (and 1 more errors)
Generated code for 3 templates with 2 errors in 1.704333ms

Neither page.templ or counter.templ have a package declaration on line 16.
I'm really confused where this went wrong. I had working code. But after splitting it up in two files (page.templ and counter.templ) things stopped working. As an experiment I merged the code back into one file but I am still getting the source formatting error: 16:1: expected declaration, found 'package' (and 1 more errors) error.
Is anything cached anywhere?

Ohhh removing the license header comment made the errors go away ... are comments not allowed?
diff --git a/counter.templ b/counter.templ
index 5be0d2a..6d6a3a7 100644
--- a/counter.templ
+++ b/counter.templ
@@ -1,7 +1,3 @@
-// This Source Code Form is subject to the terms of the Mozilla Public
-// License, v. 2.0. If a copy of the MPL was not distributed with this
-// file, You can obtain one at http://mozilla.org/MPL/2.0/
-
 package main

 import (
diff --git a/page.templ b/page.templ
index a759250..8744088 100644
--- a/page.templ
+++ b/page.templ
@@ -1,7 +1,3 @@
-// This Source Code Form is subject to the terms of the Mozilla Public
-// License, v. 2.0. If a copy of the MPL was not distributed with this
-// file, You can obtain one at http://mozilla.org/MPL/2.0/
-
 package main

 templ page() {

Answering my own question here after a bit more debugging .. comments are certainly allowed but it seems a comment before the package declaration is not. (It is in Go, but not in Templ)
I'm tempted to turn this issue into a bug report or feature request - what do you think @a-h ?

This relates closely to #79, not quite a duplicate but something to consider when we're reworking comments!

I think that allowing comments before the package declaration is completely reasonable. It's common in the standard library, for example https://cs.opensource.google/go/go/+/refs/tags/go1.21.1:src/time/format.go
templ doesn't really need to parse the package declaration at all in the current design. In earlier verisons, you could leave out the package declaration). In the current version, up until you type templ  or css  or script  to make a template, it's just Go code. So maybe it's time to rethink that section of the parser and make it more general.
v2 has been out since June 2022. In another 9 months, it will be time to consider dropping the v1 parser and the templ migrate command from the codebase.

I've started work on this at https://github.com/a-h/templ/tree/issue_159_go_comments_before_package
Need to add tests though.

I believe I've resolved this issue in https://github.com/a-h/templ/commit/c1998f6ad53c473a3bbc6ab299e0410099640143
It will be included in the next release.
Feel free to re-open this issue if it hasn't solved your issue.


Hide the honeypot field on collections-edit (bug 1219617).

This is a regression of bug 1211012

r+


Include JVM version in published Dependency Graph

It's very likely that the version of the JVM used to build the project will match the one used in production.
It would be useful to end-users to report this so they can determine if they are using a JDK with known vulnerabilities

It's very likely that the version of the JVM used to build the project will match the one used in production.

I actually tend to disagree. In my experience, the exact JVM distribution and patch level version is implied by what's available by the package management system you build or run on. So people usually care about nothing more than the major JVM version. That's why I don't believe that reporting the exact build JVM is of much value for runtime issues.

I concur with @sschuberth . In the build pipelines I manage, we build with one image and run with a different base image. We obscure the patch version from our build containers (users only know they build with Java 8, 11, or 17). Users do, however, choose the patch version for their runtime containers (for now).
Our build images contain various tools that are only needed during build (git and ssh tools, for example). They are not included in our runtime images because they are unnecessary and many pose security vulnerabilities of their own.

I don't think this adds much value. Even when the build has configured a JVM Toolchain, it's likely that this would only verify the JDK installed on the GitHub runner.


chore(ci): fix SSH key test and document project name max length

At some point, the Metal API introduced validation that rejects project names longer than 80 characters.  This broke one of our device tests, which was using the public SSH key contents as the project suffix instead of a random number.
This updates the broken test to use a random number suffix for project names so that the test can pass again.  The project resource docs are also updated to mention the 80-character limit.

Pass line for the affected test: https://github.com/equinix/terraform-provider-equinix/actions/runs/5786997385/job/15682943280?pr=352#step:5:2899
At the moment, retrying tests won't lead to a fully-passing suite because of an issue with one of the organization acceptance tests that is being investigated by the billing team.

Affected test is still passing: https://github.com/equinix/terraform-provider-equinix/actions/runs/5798496984/job/15716390685?pr=352#step:5:2875


[WIP] Spack

Add documentation for TPLs, working on the Spack DTK variant.

Codecov Report

Merging #223 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #223   +/-   ##
=======================================
  Coverage   97.34%   97.34%
=======================================
  Files          42       42
  Lines        1960     1960
=======================================
  Hits         1908     1908
  Misses         52       52

Continue to review full report at Codecov.

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


Fix Get started, it should be "yarn start-live-local"

Fix Get started, it should be "yarn start-live-local"

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Wei Li seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


[wip] add flag to enable fraud proofs

Fixes https://github.com/celestiaorg/rollmint/issues/619 by adding a flag to enable fraud proofs. Note that, there is a change in the default behavior after this commit is merged, where previously by default the fraud proofs were enabled, but now they will be disabled and the flag --rollmint.experimental_insecure_fraud_proofs must be passed enable fraud proofs.

Since previously the fraud proofs were enabled by default (fraudProofsEnabled = true), where there any dependencies that assumed this behavior?

IIRC no. @Manav-Aggarwal please confirm.

Since previously the fraud proofs were enabled by default (fraudProofsEnabled = true), where there any dependencies that assumed this behavior?

IIRC no. @Manav-Aggarwal please confirm.

Yep that's correct. No dependencies assuming it.

@tzdybal @Manav-Aggarwal i think this PR is ready for review.


Update language-server and testing libraries

It seems like the 8.0.2 update of the language-server-protocol library contains a breaking change, see https://github.com/langium/langium/discussions/674. Users downloading that update will encounter a breaking change in Langium.
Also updates jest to 29.0.0, that should also resolve the issue brought up in https://github.com/langium/langium/discussions/653.

Test failure:

packages/langium-cli/test/generator/module-generator.test.ts:21:34 - error TS2339: Property 'not' does not exist on type 'Matchers<string, {}>'.


Object based format params

Pull Request Test Coverage Report for Build 61

0 of 0   changed or added relevant lines in 0 files are covered.
4 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-15.4%) to 84.615%

Files with Coverage Reduction
New Missed Lines
%

src/I18n/I18n.tsx
1
75.0%

src/utils/handleNotFound.ts
3
50.0%

Totals

Change from base Build 59:
-15.4%

Covered Lines:
50

Relevant Lines:
54

💛  - Coveralls

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Feature aviv vocabulary update

Please add npm-commands-vocabulary.md and pix folder to vocabulary.

@aviv82 Regarding your vocabulary, everything looks great 🚀 . As we have seen it yesterday on the video, the problem persists from the GitHub action which me and @colevandersWands are working on. Just to be sure run npm run lint:md  one last time and share it with me via Slack

👍


How To Login with Rails Applications

Hi,
This is kishore cheruku from India, First of all thank you very much for CASino clear explanation. I successfully install this CASino in my local machine. But my question is i have 3 rails applications , now i would like to take sso for those 3 applications.Am getting confusion for how to configure with CASino and rails applications...

Check out this documentation. CASino is your CAS server, you will need a CAS client such as Rack-CAS for the Rails applications.


Master to Live

Docs Build status updates of commit 7c8874b:
:clock10: Full build: the average full build time is 14 min(s) 15 sec(s), this is based on the last 62 build(s) for this repository.
:warning: This is a FULL build due to the incremental build being disabled in configuration file (.openpublishing.publish.config.json in 'live' branch). For more detailed info, please click here.

Docs Build status updates of commit 7c8874b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/exchange-server/recipient-filters/filter-properties.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[Do Not Review] Generic Gateway Instantiation

I was recently looking to move a server instantiation side-effect out of gateway instantiation LnGateway::new(). What was looking like a simple mod to add an Option<webserver> to this line, quickly spiraled out of hand the moment I tried to hide webserver messaging channel opening within the LnGateway instance.

Note: Making webserver optional while we are still getting channel (sender, receiver) from outside LnGateway is sufficient to move webserver instantiation side-effect out of LnGateway::new(), but is not very useful

Currently, the channel is opened before LnGateway instantiation so we can use the message channel sender to share state with a cln-plugin used to spawn a c-ln rpc we use as ln-client within LnGateway
Ideas:

Generalize basic configs options for initializing a gateway: { 'workdir', 'host', 'port' }, and decouple these from cln-plugin builder
Hide the message channel sharing between the ln rpc and LnGateway webserver : This probably just needs some indirection on how we create and compose Lightning client rpc with the gateway

in case #497 gets merged this needs rebase and change of logic I think (not sure though didn't review)

Reference

That's alright. This not-for-review PR highlights my exploration of how we instantiate a gateway, and some ideas on how we can refactor it to be more generic so we can remove all side effects from instantiation and move towards generic support for different LN clients


Change the return value of the exec function

Codecov Report

Merging #3 (02125e9) into master (f07f0d2) will decrease coverage by 0.31%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master       #3      +/-   ##
==========================================
- Coverage   99.34%   99.02%   -0.32%
==========================================
  Files           7        7
  Lines         307      309       +2
==========================================
+ Hits          305      306       +1
- Misses          2        3       +1

Flag
Coverage Δ

unittests
99.02% <100.00%> (-0.32%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

lib/exec.lua
93.54% <100.00%> (+0.69%)
:arrow_up:

lib/global.lua
95.65% <0.00%> (-4.35%)
:arrow_down:

lib/install.lua
100.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


Katacoda course broken

Expected Behavior
After the initial install during the Katacoda course the pods should be running and healthy.
Actual Behavior
The pods fail to start as the Katacoda Kubernetes environment is 1.18 which is incompatible with the current version of TektonCD so you get an error in the pod logs:
k logs tekton-pipelines-controller-5d79c5d5f8-5llhm
2021/08/17 12:00:49 Registering 4 clients
2021/08/17 12:00:49 Registering 4 informer factories
2021/08/17 12:00:49 Registering 8 informers
2021/08/17 12:00:49 Registering 2 controllers
2021/08/17 12:00:49 Readiness and health check server listening on port 8080
{"level":"info","ts":"2021-08-17T12:00:49.920Z","caller":"logging/config.go:116","msg":"Successfully created the logger."}
{"level":"info","ts":"2021-08-17T12:00:49.920Z","caller":"logging/config.go:117","msg":"Logging level set to: info"}
{"level":"info","ts":"2021-08-17T12:00:49.920Z","logger":"tekton-pipelines-controller","caller":"profiling/server.go:64","msg":"Profiling enabled: false","commit":"445b835"}
{"level":"fatal","ts":"2021-08-17T12:00:49.921Z","logger":"tekton-pipelines-controller","caller":"sharedmain/main.go:273","msg":"Version check failed","commit":"445b835","error":"kubernetes version \"1.18.0\" is not compatible, need at least \"1.19.0-\" (this can be overridden with the env var \"KUBERNETES_MIN_VERSION\")","stacktrace":"github.com/tektoncd/pipeline/vendor/knative.dev/pkg/injection/sharedmain.CheckK8sClientMinimumVersionOrDie\n\tgithub.com/tektoncd/pipeline/vendor/knative.dev/pkg/injection/sharedmain/main.go:273\ngithub.com/tektoncd/pipeline/vendor/knative.dev/pkg/injection/sharedmain.MainWithConfig\n\tgithub.com/tektoncd/pipeline/vendor/knative.dev/pkg/injection/sharedmain/main.go:177\nmain.main\n\tgithub.com/tektoncd/pipeline/cmd/controller/main.go:110\nruntime.main\n\truntime/proc.go:225"}

Steps to Reproduce the Problem

Start the Katacoda course.
Install the linked manifest
Monitor pods until they start crash looping.
Get pod logs.

Additional Info

Kubernetes version: 1.18
Output of kubectl version:

controlplane $ kubectl version
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.0", GitCommit:"9e991415386e4cf155a24b1da15becaa390438d8", GitTreeState:"clean", BuildDate:"2020-03-25T14:58:59Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.0", GitCommit:"9e991415386e4cf155a24b1da15becaa390438d8", GitTreeState:"clean", BuildDate:"2020-03-25T14:50:46Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"linux/amd64"}

Tekton Pipeline version:
Output of tkn version or kubectl get pods -n tekton-pipelines -l app=tekton-pipelines-controller -o=jsonpath='{.items[0].metadata.labels.version}'

NAME                                           READY   STATUS             RESTARTS   AGE
tekton-pipelines-controller-5d79c5d5f8-5llhm   0/1     CrashLoopBackOff   5          5m21s```

Hey @alanjjenkins ! Sorry you're running into this :(
Is this the katacoda course you see at https://tekton.dev/try/ (which links to https://katacoda.com/tektoncd/scenarios/dashboard) or https://katacoda.com/tektoncd/scenarios/playground, or a different katacoda tutorial? Unfortunately we kinda added those tutorials and didn't really follow up on them 😅  though we really want to improve this experience in the future!!
I'm also going to move this over to tektoncd/website which is where we track docs related issues and source.


Add using-transactional-scope-in-jms-to-database sample

Purpose

Add sample to showcase the usage of transactions using databases.

As discussed, the example need to have DB insert and JMS send need to be in a same transaction. Using transaction mediator can we do that? Please check with @isudana after having a look at the code.

Please remove unnecessary logging.

Please use script mediator to generate the error. @sajithaliyanage knows details.

On hold due to the issue identified in [1].
[1] https://github.com/wso2/integration-studio-examples/issues/123

Draft PR: https://github.com/wso2/integration-studio-examples/pull/137


new-image-drawn event not fired when image added with chooseFile() method

When adding a new image to a croppa instance using the chooseFile() method the new-image-drawn event is not fired.
https://codepen.io/anon/pen/zLYQVz
Not necessarily a bug as you can force hasImage() to false by using remove() before the new image is selected which will result in the event being emitted.
In my case I'd like to replace the existing image and still have the event fired so that the new image will be sized correctly according to my initial-size prop value

I tried the demo and the event is fired. I record the screen:
https://www.useloom.com/share/d88cec876178418a8647adbcca24c108

Load one and then use the chooseFile() to load another. Only fires on the first load.
My use case is a profile image. The user may already have a profile image and may choose to edit the existing image OR replace it with a new one. In this case I pass an initial image prop and so I must display a button with chooseFile(). Since an initial image is loaded on init adding a replacement image does not fire the new-image-drawn event. Try for yourself with the same codepen.
The work around is to remove() the initial image before the second one is added. The problem here is if the user cancels the file input there is no way to capture that event and replace the initial image.

@rwfresh Indeed. Will fix the bug. Please use remove() for now.

@zhanziyang Thank you very much for making this component. I really appreciate it. I went through the code to see if I could modify and make a pull request but I haven't had enough time to actually track it down.

Also, might be of value for other users, I have a demo where I place an overlay that helps end users frame their image much like linkedIn's profile image editor. This fix will make it run much smoother. I will create a codepen demo.

@rwfresh  Sounds awesome!

@rwfresh  Bug fixed in new version 1.3.7. Please upgrade : )

Hi @zhanziyang Thanks for this fix. Finally had a chance to review my code. Here's a codepen with the overlay I was talking about. https://codepen.io/rwfresh/pen/zLYQVz

Thanks @rwfresh. That's a cool demo. Maybe later I will add it to the demo page.

@zhanziyang right on. Again, thanks to you for taking the time to put this together.

@zhanziyang , it seems not update in demo.


[FancyZones] Add automatic tabbed interface to each zone

Description of the new feature / enhancement
When stacking multiple applications in a single zone, the zone would add a tabs that allow switching between the stacked applications. This could be enabled as a feature in the options. Another option could determine if the tabs are shown even if there's only one application in a zone.
Scenario when this would be used?
This would make it much faster to switch between applications that share a zone. This would be useful when you use more applications than the number of zones you have defined.
Supporting information
There are some applications that allow you to create the tabbed style (e.g. Groupy from Stardock) but having it built into FancyZones would make the experience very slick.

Yes please


Upstream fix: Can't focus component that was just mounted

Environment
RNTester app. I am adding a test page to demonstrate the issue.

I have repro on 0.66 in my environment -- but I also repro on against main in the tester app.

Steps to reproduce the bug

Open RNTester app (macOS)
Click on "Focus on Mount"
Observe

Expected Behavior
Based on how the test page is written, the component should be focused.
Actual Behavior
It isn't focused.
Reproducible Demo
See repro instructions for demo in tester app. I will be adding a page to the tester app after creating this issue.
Additional context

reactFocusIsNeeded is never called for a plain RCTView
focus state is tracked on a per-view basis; should ideally be per-window, perhaps simply tracking it globally is sufficient as well. It should not be tracked per-view, because only one can ultimately win (the last one -- assuming it also didn't give up on focus while it was "winning").

Going to re-open this issue as a "potentially upstream able fix" kinda issue. Will revisit once we've let our fix make it's way downstream and has had time to be tested/verified more


Trailing slash on "init" confuses attic

Mind the trailing slashes in this. It all would have worked fine if I had initially left it off but it seems that attic itself gets confused. Not sure what the behaviour should be but when I posted it to IRC earlier, it was suggested to post as bug here.
$ attic init /mnt/hdd/atticbk/
Initializing repository at "/mnt/hdd/atticbk/"

$ attic create /mnt/hdd/atticbk::`date +%Y-%m-%d_%H%M%S` /home/me/somedir
Warning: The repository at location /mnt/hdd/atticbk was previously located at /mnt/hdd/atticbk/
attic: Error: Repository access aborted

$ attic init /mnt/hdd/atticbk
Initializing repository at "/mnt/hdd/atticbk"
attic: Error: Repository /mnt/hdd/atticbk already exists

$ attic create /mnt/hdd/atticbk/::`date +%Y-%m-%d_%H%M%S` /home/me/somedir
this works fine

+1 - I just had same effect.
Note: when using tab completion on pathes, bash adds the trailing slash for directories, so line 2 of above somehow comes naturally.

Looks like the same problem as #292


default ClusterInfo in mcad-system namespace

Closing this since it will conflict with #124.  Will revisit in the next step of enabling multi-cluster.


Fully Center the Image (Vertical / Horizontal)

As we can see the image is only centered horizontal but how can i fix it to center it vertical also?
I tried several things but can't fix it.
Does someone have a solution?

The modal body should resize to your image. Post a link?

Someone?

https://stackoverflow.com/questions/18422223/bootstrap-3-modal-vertical-position-center


Timber Archives: Resolving 'monthly-nested' issue (Tree too nested)

More details here.

Thanks @eightyfive! Looks good


Fan physics

Prototype fan is working

What's the dealio with star.png? Otherwise this is 🎉 🎉 👍

@BethFromAbove but what was the dealio with star.png? We have to know


Chore/update dev tooling black and flake8

Description
After releasing v0.23 and #1181, we take the opportunity to also upgrade two libraries in our dev/CI/ code hygiene tooling.
Look & Feel
This results in a list of code format changes from black, but mostly in db migrations.


Container name unique per environment

https://github.com/rancher/rancher/issues/7384
@ibuildthecloud @vincent99 still uncertain whether putting this restriction on API side is correct, given that internally we do allow duplicated names (during in service upgrade use case, failed health check instance recreate, etc)

I think it's fine to attempt to prevent this knowing that we really can't stop it fully.

What's the point of disallowing it? Are we still going to allow null names?

Containers can go on stacks which now have to have unique (and not null) names for DNS

What do you mean "can go on stacks" @vincent99?

@vincent99 I didn't put not null restriction on the container name yet, should I do it?


TLS/SSL Support

Hello
I believe this package does not yet support connecting to Sentinel over TLS/SSL ?
Are you considering implementation ?
If it does exist, could you point me to where the configuration is done ?
Much appreciated

Based on the sentinel documentation of phpredis/phpredis, I'm not sure this is even supported?!

I'm afraid you are right :'(
Thanks for the quick response!
Now to find a solution, because our production clusters have mandatory TLS

But here I see a TLS commit : https://github.com/phpredis/phpredis/issues/2114

Interesting find, maybe it is possible. This should mostly affect the following part of the code:
https://github.com/Namoshek/laravel-redis-sentinel/blob/3d6fad1c4d07fe4098fd2af260697ebe86c63304/src/Connectors/PhpRedisSentinelConnector.php#L84-L129
However, the way the phpredis library works, you can only pass the object when its actually being used. So the workaround of L128 needs to be used for this as well, making the code a bit bulky. If you want to give it a try, feel free. Otherwise I'll see when I find the time.

By the statement "workaround L128" , you mean the fact that RedisSentinel doesn't accept more then 6 function parameters ?
Not sure why it's not complaining about the $auth .... or I'm misunderstanding you.

Sorry if that wasn't very helpful. I'm not sure if the SSL context works similar to the auth options. With the auth options, the RedisSentinel class complains if you pass them as null. Instead, the parameter needs to be omitted entirely. Which, to be honest, is kinda problematic if you need to pass an argument after it... I guess that needs some fiddling and testing.

Hmmm, if RedisSentinel indeed requires it not to be null, then it would be impossible to provide any following parameters without the auth option (given we can't rewrite the function declaration ourselves).
One could argue that if you want to secure your connection with TLS , you would not want to use NOAUTH.
So , if TLS is to be used AUTH is mandatory. However, that limits the functionality for cases where this is required.
Could you work out an example of connecting with both AUTH and TLS/SSL Context ?

By the way ... coincidence (5 hours ago) :-) : https://github.com/phpredis/phpredis/commit/8144db374338006a316beb11549f37926bd40c5d

Apparantly the latest version 6.1 , released 4 weeks ago includes support for TLS/SSL : https://github.com/phpredis/phpredis/commit/f2bb2cdb5a8cc770d22b6d516e230d2cf544929b#diff-16398f4eda044362a02548e382f2ec7dfd1aae291be015c075d2409928ddf295R11

I've pulled the branch and added it to my local repos. I changed the configuration as follows :
`    'redis' => [
'client' => 'phpredis-sentinel',
    'redis_with_tls' => [
        'sentinel_host' => 'tls://my_sentinel_host',
        'sentinel_port' => 26379,
        'sentinel_service' => 'mymaster',
        'sentinel_timeout' => 0,
        'sentinel_persistent' => false,
        'sentinel_retry_interval' => 0,
        'sentinel_read_timeout' => 0,
        'sentinel_username' => 'my_sentinel_username',
        'sentinel_password' => 'my_sentinel_password',
        'sentinel_ssl' => [
            'verify_peer' => false,
            'verify_peer_name' => false,
        ],
        'username' => 'my_redis_username',
        'password' => 'my_redis_password',
        'database' => 1,
    ],
]

`
When using Redis::connection('redis_with_tls') , I get the error :
read error on connection to <IP_ADDRESS>:6379   (one of the Redis nodes)

That's interesting because it seems that the Redis instance resolution through Sentinel worked at this point. Is your Sentinel configured to resolve non-SSL connections or should it return the Redis address with an SSL port?
Anyway, you might want to add 'scheme'' => 'tls' to your config, it may be used by the underlying PhpRedisConnector when establishing the actual connection.

I was indeed just testing adding 'scheme' => 'tls'
Strangely I get back :
Redis::connect(): Peer certificate CN=redacted_redis_node_name' did not match expected CN=<IP_ADDRESS>'
Even though I have "verify_peer" set to false.
So yes, indeed , it looks like the resoliution to Redis Sentinel instance is fine, but the connection afterwards fails.
I'll check with our SRE on how our Redis Sentinel is configured and get back to you.

I think if you add your SSL options as context option, it adds them as SSL context for the Redis connection itself:
https://github.com/laravel/framework/blob/0be1995727a7c9341d13a08253a12140b8fc84fd/src/Illuminate/Redis/Connectors/PhpRedisConnector.php#L155-L157

I've got it working ! The SSL context needs to be inside streaming .
Just to be clear, the full config that is working with AUTH and TLS/SSL
`
'redis' => [
    'client' => 'phpredis-sentinel',

    'redis_with_tls' => [
        'sentinel_host' => 'tls://sentinel_host',
        'sentinel_port' => 26379,
        'sentinel_service' => 'mymaster',
        'sentinel_timeout' => 0,
        'sentinel_persistent' => false,
        'sentinel_retry_interval' => 0,
        'sentinel_read_timeout' => 0,
        'sentinel_username' => 'sentinel_username',
        'sentinel_password' => 'sentinel_password',
        'sentinel_ssl' => [
            'verify_peer' => false,
            'verify_peer_name' => false,
        ],
        'options' => [
            'context' => [
                'stream' => [
                    'verify_peer' => false,
                    'verify_peer_name' => false,
                ]
            ]
        ],
        'scheme' => 'tls',
        'username' => 'redis_username',
        'password' => 'redis_password',
        'database' => 1,
    ],
]

`

Awesome , I truly appreciate all the efforts !
Will be pulling the newest version and doing some tests tomorrow.


Update Reference App Withdraw Flow

Looking really good! Just the one comment.

Looking really good! Just the one comment.


chore: restructure navigation

Remove navigation tabs. It's not a complex site anyway with multiple levels of nested documents, so might as well keeps things simple.
Before
Home, best practices and module library in separate tabs, so you have to open a new page to see the documents under each tab:

After
Home, best practices and module library in a single tab, so you can see all documents on a single tab:

Just to add to this, and why its a good change, here are some examples of the navigation tabs viewed on mobile:

The experience is the same for the website in a minimized browser window

Before:

Main navigation bar
"Home" navigation bar

After:

The "Home" navigation bar seems redundant (and lonely) in the previous version.


Pre v1 cleanup - first PR

Assorted small cleanups of confusing code and unused files.

Looks good! I especially like the find_by_name addition to benchmark definition.

That was definitely inspired by your suggestion.

I’m curious about the choice to remove the v0.5 hazard content files because I thought we wanted to preserve v0.5 for now.

Those files were never actually used. I believe all actual 0.5 functionality is preserved.

Added a fair bit more cleanup, this time around the SUTs.

I guess don't really understand the purpose of ModelGaugeSut. It doesn't seem to provide any functionality that doesn't already exist in the regular model gauge SUT objects.