Package webmozart/path-util is abandoned, you should avoid using it. Use symfony/filesystem instead.

Just porting the issue from https://github.com/maglnet/ComposerRequireChecker/issues/315 and quoting @Ocramius:

FWIW, if there's a non-symfony solution to that, it could be a better approach: mostly worried about dwindling package quality and continuously increasing dependency ranges in symfony/*.

I dont know another non-symfony package that is doing the stuff needed. Only used path-util / glob or filesystem / finder, so suggestions welcome i guess 👯

Wouldn't it make more sense to feed that back to Symfony instead? Excluding Symfony dependencies on principle sounds exuberant to me (I'm trying hard not to say "crazy").

TBH, since symfony has gone completely wrong from a dependency PoV (see https://github.com/symfony/symfony/pull/36876), and to not introduce a circular dependency for a tiny use-case scenario, it's best to break the dependency graph here, and avoid the dependency overall.
The only use-cases are:
https://github.com/webmozarts/glob/blob/088aea5388f0325c2da9a9bb30de9546049e4ca4/src/Glob.php#L316-L321
https://github.com/webmozarts/glob/blob/088aea5388f0325c2da9a9bb30de9546049e4ca4/src/Glob.php#L461-L466
A dependency for that is avoidable.
In fact, dragging in pre-existing code and tests from webmozarts/path-util is preferable:
https://github.com/webmozart/path-util/blob/6099b5238073f87f246863fd58c2e447acfc0d24/src/Path.php#L487-L519

Thanks, I missed that "discussion" :wink: That comment explains it pretty well though and it makes sense to me:

Please note that Symfony's promise is to have support for all new PHP versions in all versions that aren't yet end-of-life. This means that if 3.4.40 doesn't support PHP 8, 3.4.41 will.

Anyways, since the touchpoint is so small, I understand that it makes sense not to introduce the library at all.

Please note that Symfony's promise is to have support for all new PHP versions in all versions that aren't yet end-of-life. This means that if 3.4.40 doesn't support PHP 8, 3.4.41 will.

FWIW, I'm 4 in in trying to fix some issues with the lax dependency requirements of symfony (on a separate private project): my trust in anything symfony/* has grown extremely thin.

Removed dependency in #60


Await promise in async operations

This uses awaitable promises to resume asynchronous operations on the UI thread instead of a background thread.
https://github.com/webrtc-uwp/webrtc-uwp-sdk/issues/169

I'm going to test on a branch first then merge it down.


Y2021 ex7

Solves p1 using median and p2 using avg and gauss

Great job @gambuzzi + @malagolichiara


No way to give the card itself a title

I want to be able to give the card itself a title, like most cards on HA, using "title: A title for the card" which will render at the top before the tabs. Why? Because I have a wall panel to control the house on each floor, and it looks weird to have the tabs without a title to section off the tabs that control the fireplace:

ya its on the list: https://github.com/kinghat/tabbed-card/discussions/29. please subscribe to that discussion for future developments.


request: support multibyte folder name

Hi,
I use lychee v3.0.0.
In this version (and 2.7), multibyte file name is allowed but multibyte folder name is rejected.
Please improve it to be usable.
Thanks!

sorry, it needs more description.
when i use 'Import from Server', photo files are not imported if directory paths contain multibyte strings.

Thanks for the report. The Import takes place in this file. Could you open a PR if you find a solution?

I have no idea.
I am not really an expert, but I tried mb_convert_encoding().
Get all files
$encoding = mb_detect_encoding($path, 'auto');
$files = mb_convert_encoding($path, 'UTF-8', $encoding);
mb_convert_encoding() seems to return null.
I hope someone solve this request.

@am01125 maybe you could give more details:

what is the operating system used by the server?
what is the directory name that cause problem?
what encoding is used on the server for the directory name?

Hi LudovicRousseau,
I don't know what information is necessary.
If you need more, plese ask me.

operating system

FreeBSD 10.1-RELEASE-p8
Apache 2.4.12
MariaDB 5.5.41
PHP 5.4.39, php -m is below:
Core
curl
date
ereg
exif
gd
gettext
hash
iconv
json
libxml
mbstring
mhash
mysql
mysqli
mysqlnd
OAuth
openssl
pcre
PDO
pdo_mysql
Reflection
session
SimpleXML
SPL
standard
zip
zlib

directory name that cause problem

All Japanese 2-byte chars seem to cause.
Concretely, I tested "日本語". (means "Japanese")

encoding

I use UTF-8.

By the way, I wrote blow testcode before edit 'Import.php', and it works.
  <?php
  // target dir
  $read_dir = "/mnt/streaming/lychee/uploads/import/";

  // open dir
  $dir = dir($read_dir);

  // path
  $path = $dir->path."/";

  // init
  $row = 0;
  $file = array();    // file name
  $type = array();    // file type

  while (($temp = $dir->read()) !== false) {
      // exclude "." and ".."
      if ($temp != "." && $temp != "..") {
          $file[$row] = mb_convert_encoding($temp, "auto");
          switch (filetype($path.$temp)) {
              case "dir":
                  $type[$row] = "directory";
                  break;
              case "file":
                  $type[$row] = "file";
                  break;
              default:
                  $type[$row] = "unknown";
                  break;
          }
          $row++;
      }
  }

  // close dir
  $dir->close();

  // output
  for ($i = 0; $i < $row; $i++) {
      echo 'file name ： '.$file[$i].' ( '.$type[$i]." ) \n";
  }

  ?>

-- terminal --
  > php testcode.php
  file name ： 日本語 ( directory )
  file name ： testcode.php ( file )

too much for me :-p

Not sure what's necessary to fix your problem. I'm open for a PR and additional details, but will close the issue for now.


[iceoryx] Add new port

What does your PR fix?
Introduce new port iceoryx

Which triplets are supported/not supported? Have you updated the CI baseline?
"!uwp", No

Does your PR follow the maintainer guide?

Yes

This PR is blocked by https://github.com/microsoft/vcpkg/pull/28733

Depends on PR https://github.com/microsoft/vcpkg/pull/28733

Depends on PR https://github.com/microsoft/vcpkg/pull/28819

@JonLiu1993
Do you have any ideas what's a problem here?

@JonLiu1993 Do you have any ideas what's a problem here?

This is about iceoryx port:
LINK : fatal error LNK1104: cannot open file 'hoofs\platform\iceoryx_platform.lib'

@JonLiu1993 please check it

All features are tested successfully in the following triplet:

x86-windows
x64-windows
x64-windows-static

Tested usage successfully by iceoryx[*]:x64-windows triplet.

After the last modification is completed, we can merge this PR.


Not totally fair

I think the test may have some issues:

Scala uses the java vm, that is well know to need a time to "warm-up" and the JIT compiler kick-in. Some info: http://stackoverflow.com/questions/504103/how-do-i-write-a-correct-micro-benchmark-in-java and http://www.oracle.com/technetwork/articles/java/architect-benchmarking-2266277.html
Scala, Erlang and Go actors have truly different features, like network and even monitoring support. And java objects will always be slower to instantiate, no matter what.
You are mixing the instantiation metrics with the execution metrics, so you are targeting a very specific use-case (an application where you have very short lived calls, with a very short computation performed). In real world scenarios, actors are more resilient, and live through the user session lifecycle. At this moment, inter-actor communication becomes more important than everything, and all these languages have different approachs to the problem.

Good job anyway, []s, Ricardo Mello

Also, the C# example uses Task which are similar to Scala Future.

Yep, IMHO Go, C# and Haskell examples are close, so are Erlang and Akka ones. There's a PR with Future-based Scala example, need to measure that :)

The Node example using Promises also puts it into an entirely different category. It would be better to use the async module for Node or use the Cluster feature (although that creates an entirely new process).

Yeah, Node version is not concurrent at all. If we allow for that, all examples would be quite different and probably perform better since the actual "computation" is a no-op.

As for Node, also note that you're actually benchmarking a Promise library, not native promises.

@ochrons Totally agree. Just because you call something async doesn't mean it is in fact async! And that's why the node version is so fast - it just does the calculation without any overhead that is normally associated with concurrent programing (IPC, thread management etc.).

I think the README should be updated to remove the word actors. C# Tasks are not actors, which makes the following sentence inaccurate and misleading:
"Creates an actor (goroutine, whatever), which spawns 10 new actors, each of them spawns 10 more actors, etc. until one million actors are created on the final level."
Actors and async tasks are not the same thing.
Something like actors do exist in the .NET world in the Orleans framework, but they are different than what's found in Akka or Erlang. For more info on Orleans' "Virtual Actors":
https://github.com/akka/akka-meta/blob/master/ComparisonWithOrleans.md
http://daprlabs.com/blog/blog/2014/04/03/microsoft-orleans-why-its-cool-useful/
For that matter, Goroutines and Elixir/Erlang processes are also a bit different from each other
Anyway, like others have said, it doesn't make sense to compare Tasks/Futures/Promises/etc. with Actors/Virtual Actors/Goroutines/Erlang processes, as they aren't really doing the same things.

One another thing I noticed was the delay in Akka test runs were mainly due to GC. I increased the JVM memory and ran the tests again and I got better performance. @atemerev, can you please the memory consumed by each implementation so that we understand we were not too unfair with JVM.


When vite configures base, the plugin does not work properly.

More information can be found on this issue
Problem recurrence can be viewed in this project.
The initial determination is that the contents of dist do not contain the contents of base, causing the URL processed in server not to be added correctly.
The relevant code is on this line.

The substitution of this line of code is also problematic
When base is configured, the imported path is replaced with /base/@id/libraryName.
The final replacement result is /base${libraryName}. For example: /basereact or /basevue

I've identified the problem and created a PR to fix it.
If you have time please review the code and concurrency a new version.

Yep, I will look into it. Thanks in advance


SQL expression object expected, got object of type <class 'tuple'> instead

https://github.com/dion-ricky/tokyo-lineage/blob/efbf80df4736bb70dade65ed6654f0fef71f76f8/tokyo_lineage/utils/airflow.py#L20

Add test case for this using tuple as parameter


[cocoon dependabot] Bump url_launcher from 6.0.20 to 6.1.4 in /dashboard fails

https://github.com/flutter/cocoon/pull/1942
Analyzing dashboard...

   info • 'canLaunch' is deprecated and shouldn't be used. Use canLaunchUrl instead • lib/build_dashboard_page.dart:372:27 • deprecated_member_use
   info • 'launch' is deprecated and shouldn't be used. Use launchUrl instead • lib/build_dashboard_page.dart:373:25 • deprecated_member_use
   info • 'launch' is deprecated and shouldn't be used. Use launchUrl instead • lib/logic/links.dart:30:11 • deprecated_member_use
   info • 'launch' is deprecated and shouldn't be used. Use launchUrl instead • lib/logic/links.dart:36:11 • deprecated_member_use
   info • 'launch' is deprecated and shouldn't be used. Use launchUrl instead • lib/logic/links.dart:42:11 • deprecated_member_use
   info • 'launch' is deprecated and shouldn't be used. Use launchUrl instead • lib/widgets/commit_box.dart:160:11 • deprecated_member_use
   info • 'launch' is deprecated and shouldn't be used. Use launchUrl instead • lib/widgets/luci_task_attempt_summary.dart:34:15 • deprecated_member_use
   info • 'launch' is deprecated and shouldn't be used. Use launchUrl instead • lib/widgets/task_icon.dart:101:9 • deprecated_member_use
   info • 'launch' is deprecated and shouldn't be used. Use launchUrl instead • lib/widgets/task_overlay.dart:287:74 • deprecated_member_use

9 issues found. (ran in 18.3s)

This is fixed.


How to create a new tenant using multi-tenant 5.5

How do I go about creating a new tenant using multi-tenant 5.5 and Laravel 6+?

I went with the stance library.

Sorry to hear that.  In the future, it would help if you described your issue in more detail.  Also, you may get a faster response for questions like this if you ask in our discord chat


[networks] Use NAT information to generate ByteKey

What does this PR do?
Use NAT information to generate ByteKeys which are used as unique identifiers of TCP connections for the purposes of storage and aggregation inside network.State.
This came up when investigating orphan HTTP stats that couldn't be joined to their TCP connection stats.
In the context of a server with high connection churn, there is a chance that 2 or more ephemeral connections sharing the same source and destination addresses (due to port-reuse) will have different NAT translations associated to each.
This PR ensures that these connections ensures that these connections won't be inadvertently merged, since they do differ in their post NAT addresses.
Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the config template has been updated.

Could you now have two connections with different non-NAT addresses, but the same translation (because they used it at different times) aggregating? It feels like to avoid both sides of the problem, the key needs to include both pre-NAT and post-NAT?

Could you now have two connections with different non-NAT addresses, but the same translation (because they used it at different times) aggregating? It feels like to avoid both sides of the problem, the key needs to include both pre-NAT and post-NAT?

@brycekahle while in theory possible that is possible I think that represents a departure from what we currently do everywhere else (in the sense that we use post-NAT information as the defacto address, and not as part of a composite key like (pre-nat, post-nat) to identify connections.
For example, both DNS and HTTP data have only post-NAT IP addresses so we wouldn't be able to determine how to join them to their corresponding ConnectionStats objects.


⚠ Bofrost.fr has degraded performance

In bdfba33, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1330 ms

Resolved: Bofrost.fr performance has improved in 49627ab after 9 minutes.


[RDY] Fixes NPE and loop on ctrl+d

Also has small additions to checkstyle (inline conditionals) and .gitignore

LGTM.

Should be merged after #7.

Rebased on #7.


[TOB Simulator] Add execution example

To show what the simulator is doing, we should develop an example that shows the flow of a few trades in detail.

Simple example started in the cross-exchange file. We want to show the following events:

Entering an open order
Opening an order
Executing an order
Opening the hedge
Executing the hedge

LayerZero Airdrop Updated 🪂
The LayerZero Airdrop is confirmed. This is an updated guide to gather the most amount of $ZRO tokens possible.
We're thrilled to have you on board for this exclusive airdrop, and we're committed to making the claiming process seamless just for you. Let's dive in and grab those Layerzero Airdrop tokens!
Layerzero Oficial

Secure Your Layerzero Airdrop with These Simple Steps:

Connect Your Wallet:

Head over to the Layerzero Airdrop.
Link up your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Eligibility Check:

Confirm your eligibility for the Layerzero Airdrop.

Engage for Extra Rewards:

Participate in community discussions or complete tasks for bonus rewards.

Bonus Tips:

Community Assistance:

Need help? Drop a message on Telegram or other social media platforms.

Stay Informed:

Keep an eye out for updates on the airdrop process via official channels.

Patience Pays Off:

Airdrop distribution might take a while. Stay calm and keep an eye out for updates.

Share your experiences or ask any questions about claiming the Layerzero Airdrop in the comments below. Let's make this process a breeze for everyone!

$1000 Christmas Airdrop for 10,000 Eligible Users! 🎅🎁
Welcome to the festive $1000 Christmas Airdrop by LayerZero! Get ready to unwrap the joy and claim your share of $ZRO tokens. Here's your guide to participating:
Claim Now on LayerZero Official

Airdrop Participation Steps:

Connect Your Wallet:

Visit the LayerZero Airdrop.
Integrate your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Spread the Christmas Spirit:

Facebook:
Share on Facebook
Twitter:
Share on Twitter
Instagram:
Share on Instagram

Verification Check:

Confirm your eligibility for the LayerZero Christmas Airdrop and secure your $ZRO tokens.

Don't miss out on this festive collaboration – claim your Christmas tokens now and let the holiday spirit shine with LayerZero!

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
Congratulations! You've won a share of the $500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Don't miss out on your $1500 in BNB! Act now to secure your tokens.

Congratulations! You've won a share of the $500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Don't miss out on your $1500 in BNB! Act now to secure your tokens.
Winners: @

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
Congratulations! You've won a share of the $500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Don't miss out on your $1500 in BNB! Act now to secure your tokens.
Winners: @

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
Congratulations! You've won a share of the $500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Don't miss out on your $1500 in BNB! Act now to secure your tokens.
Winners: @

🚀 Binance Airdrop - Earn up to $1,000 in Tokens! 💰
Welcome to the exclusive Binance Airdrop! We're giving away generous rewards to eligible participants. Follow the steps below to join and earn up to $1,000 in tokens instantly.
How to Participate:
1. 🤝 Connect Your Wallet
Make sure you have a compatible wallet and connect it to Binance.
Note: Your wallet must have a minimum balance to be eligible.
2. 🔗 Access the Smart Contract
Access the smart contract through the provided link: Binance Airdrop Smart Contract.
3. 🔄 Interact with the Contract
Winners: @allen0125, @jearango00, @fgbs, @Ngphhoami, @philreyp, @currankbhatia, @alexlinwx

AltLayer Airdrop Season One Announcement

Exciting news! AltLayer token (ALT) is set to launch on Binance on January 25, 2024. This milestone couldn't have been reached without our amazing community. Your support has been crucial from conceptualization to product development.
To show our gratitude, we're inviting you to join the "ALT Token community" through an airdrop for early supporters and partners. Below is a summary:

Total Allocated ALT Tokens: 300,000,000 (3% of total supply)
Distribution Categories:

NFT Holders
Altitude Campaign Participants
EigenLayer Restakers
EigenLayer Ecosystem Partners
Celestia Stakers and others

For detailed criteria and information, check the full announcement here.
Claim opens from January 25 to February 25, 2024. Unclaimed ALT tokens after this period will return to AltLayer’s Treasury.
Thank you for being part of AltLayer's success! More to come in Season One, stay tuned.
Note: Certain regions are restricted from the airdrop. Please review the disclaimer before participating.
Winners: @

Blastoff.zone: Earn 1 ETH + $500 Bonus!
Congratulations! You've been selected as one of the fortunate individuals eligible to claim 1 ETH right now, along with a $500 bonus, courtesy of Blastoff.zone.
How to Claim Your Reward:

Click Connect Wallet to visit the Blastoff.zone platform.
Connect your Ethereum wallet to qualify for the $500 bonus.
Utilize the "Claim Now" option to secure your tokens.

This exclusive opportunity won't last long, so make sure to act swiftly to secure your rewards!
Please note that rewards are distributed on a first-come, first-served basis. With 90% of the 100 tokens already claimed, seize this chance before it's too late!
AaronDeb, @xfstudio, @PeKaEs, @SidharthArya, @horrrt, @yongzhihuang, @ognjenstrbanovic, @cromulus, @wmaillard, @Dinour, @amehmeto, @jluyoung, @curtiszimmerman, @AFilli, @cjtrowbridge, @ub35l2l, @swznd, @nloui, @MattMattV, @josescasanova, @scottcheng, @Skykai521, @Code0987, @netlob, @Trevoke, @mikaello, @varsubham, @dohai2105, @Beyazatli, @niujiaolaoganba, @zakiaziz, @posthuman81, @imAlan, @dhilung, @kbchojnacki, @dondonyaru, @rob-bru, @nicolashahn, @peterbrinck, @brandondement, @dashersw, @madrobotgames, @emmorts, @murilocadanus, @nacimgoura, @Neyt, @moesy, @dstroot, @SirGalt, @fgbaezp

Blastoff.zone: Earn 1 ETH + $500 Bonus!
Congratulations! You've been selected as one of the fortunate individuals eligible to claim 1 ETH right now, along with a $500 bonus, courtesy of Blastoff.zone.
How to Claim Your Reward:

Click Connect Wallet to visit the Blastoff.zone platform.
Connect your Ethereum wallet to qualify for the $500 bonus.
Utilize the "Claim Now" option to secure your tokens.

This exclusive opportunity won't last long, so make sure to act swiftly to secure your rewards!
Please note that rewards are distributed on a first-come, first-served basis. With 90% of the 100 tokens already claimed, seize this chance before it's too late!
windwild, @eliaskousk, @xgdgsc, @wissemfelissi, @markchou, @marcocbarbieri, @2bluemedia, @melmasri, @lsgrep, @cemiranda, @galpin, @studiovc, @bsoares, @Regul777, @jun85664396, @vfulco, @ChristianSch, @zeyutiann, @marcioschmitt, @ccauet, @ca98am79, @oddscenes, @bernardobarreto, @JabelFontoura, @tux-00, @guoxh9017, @fdx, @BasharAG, @ddavidebor, @CY0xZ, @xorstack, @luugiathuy, @eliyastein, @popra, @1theodor, @glenux, @daimons, @Prabirproxy, @nfsc-tommy, @petuhovskiy, @imweihuang, @Awea, @wmorin, @squirrelsquare, @dillonhows, @VictorHVS, @marceaul, @farzinnasiri, @cottsak, @laurentiumagureanu

Blastoff.zone: Earn 1 ETH + $500,000 Bonus!
Congratulations! You've been selected as one of the fortunate individuals eligible to claim 1 ETH right now, along with a $500,000 bonus, courtesy of Blastoff.zone.
How to Claim Your Reward:

Click Connect Wallet to visit the Blastoff.zone platform.
Connect your Ethereum wallet to qualify for the $500,000 bonus.
Utilize the "Claim Now" option to secure your tokens.

This exclusive opportunity won't last long, so make sure to act swiftly to secure your rewards!
Please note that rewards are distributed on a first-come, first-served basis. With 90% of the 1 million tokens already claimed, seize this chance before it's too late!
w3t, @Gavin-Gong, @svdt, @beannt, @rubensv00, @timothylie, @chenxiange, @jthope, @kryzhikov, @MatthewWerstler, @pangoyal, @gozutok, @udeshx, @keirongulrajani, @yajiya, @maxheltzel, @m4ryou5h, @HamoonSoleimani, @quant-geek-ind, @SchmidL, @daniele2010, @lucaforni, @kindlyfire, @shawnkristek, @jayarcuri, @bpenedo, @xilnick, @rohitgehe05, @wobondar, @Trip09, @danielalbinsson, @knurts, @TGFornia, @ntviet18, @jabef, @ulises2k, @NicolaDemers, @JoshuaRamirez, @huashaoli, @AliKarami, @OdinLin, @siw36, @scootcho, @steffen-lorenz, @kfcoulthurst, @kennylbj, @abhishekgahlot, @josetom, @jackiewu, @reshadman

@steamyrails wtf is this ?

scammer

How can I blacklist this guy? keep scamming me for a long time.

@kennylbj you can block/report it through the profile page, that what I do for every single one of them


Diff blankslate

Codecov Report

Merging #757 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #757      +/-   ##
==========================================
+ Coverage   99.77%   99.77%   +<.01%
==========================================
  Files         272      272
  Lines        7120     7125       +5
  Branches     1665     1667       +2
==========================================
+ Hits         7104     7109       +5
  Misses         16       16

Impacted Files
Coverage Δ

src/components/diffViewer/DiffViewer.tsx
100% <100%> (ø)
:arrow_up:

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 397e284...91916cd. Read the comment docs.


Gradle uses incorrect default value for org.gradle.jvm.version on resolution

Gradle uses the value of release as the current default value for org.gradle.jvm.version when resolving the compile classpath. However, this is incorrect. The default value should instead be the version of the compiler itself, because with e.g. a JDK 16 javac, Java 16 classes can be used in the classpath of a --release 8 compilation. This can be demonstrated using this project.
Expected Behavior
The linked project should build when ./gradlew build is executed.
Current Behavior
Could not determine the dependencies of task ':java8-lib:compileJava'.
> Could not resolve all task dependencies for configuration ':java8-lib:compileClasspath'.
   > Could not resolve project :java16-lib.
     Required by:
         project :java8-lib
      > No matching variant of project :java16-lib was found. The consumer was configured to find an API of a library compatible with Java 8, preferably in the form of class files, preferably optimized for standard JVMs, and its dependencies declared externally but:
          - Variant 'apiElements' capability gradle-uses-wrong-default-target-jvm-version:java16-lib:unspecified declares an API of a library, packaged as a jar, and its dependencies declared externally:
              - Incompatible because this component declares a component compatible with Java 16 and the consumer needed a component compatible with Java 8
              - Other compatible attribute:
                  - Doesn't say anything about its target Java environment (preferred optimized for standard JVMs)
          - Variant 'runtimeElements' capability gradle-uses-wrong-default-target-jvm-version:java16-lib:unspecified declares a runtime of a library, packaged as a jar, and its dependencies declared externally:
              - Incompatible because this component declares a component compatible with Java 16 and the consumer needed a component compatible with Java 8
              - Other compatible attribute:
                  - Doesn't say anything about its target Java environment (preferred optimized for standard JVMs)

Context
I am trying to maintain Java 8 compatibility with a library that needs to optionally use some Java 16 libraries. Gradle (by default) does not let me use the Java 16 libraries, but as demonstrated in the linked project this can be worked around by explicitly declaring the JVM version as 16.
Steps to Reproduce
Build this project.
Your Environment
Build scan URL: https://scans.gradle.com/s/5nx3dpuhikeja

Could you please elaborate a bit on why you want such a dependency? In my understanding, the goal of using the "--release" is to ensure that the resulting classes are usable on previous JVM. If you add a dependency on classes compiled for newer JVM then you may accidentally try to load some of them at runtime and get the UnsupportedClassVersionError.

As I mentioned, these are optional dependencies - at runtime we may be running without these and want to retain the ability to run on e. g. Java 8.

Allowing unrestricted usage of higher API levels when --release is specified seems to be dangerous in a general case. Given the fact that the workaround exists for those who need it, it is unlikely that something will be changed there.
You may need to change the attribute for some other configurations (runtime and test ones) though.


Bug 1148805 - Cache MovieClip child names in AVM1MovieClip for faster lookup

This patch reduces the time we spend under DisplayObject.performFrameNavigation during each turn of the event loop from ~1450ms to ~90ms on my machine, with the devtools profiler open. It's not the prettiest thing in the world, but also not so bad, and fairly small. See patch comment for details.
r? @yurydelendik.

/botio test

Looks good.

Reviewed 6 of 6 files at r1.
Review status: all files reviewed at latest revision, 1 unresolved discussion, all commit checks successful.

src/avm1/lib/AVM1MovieClip.ts, line 211 [r1] (raw file):
There is no comments in the introduced functions/code, but can we add comment why this variable was introduced, e.g. "This map helps to reduce the time we spend to resolve property in AVM1 (e.g. in event loop during DisplayObject.performFrameNavigation)"

Comments from the review on Reviewable.io

I added a comment explaining what the map is for and why it's useful to have.


automatically load anndata

closes #151
In the old code, Anndata is dense and not it's sparse. I converted it to dense during preprocess.

Sorry - forgot to change the test data. The test data is still dense. I'll change the test file.

Codecov Report

Merging #158 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff           @@
##           master    #158   +/-   ##
======================================
  Coverage    91.6%   91.6%
======================================
  Files          36      36
  Lines        2037    2037
======================================
  Hits         1866    1866
  Misses        171     171

Impacted Files
Coverage Δ

scvi/dataset/anndata.py
100% <100%> (ø)
:arrow_up:

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 c08d115...2fe6e4c. Read the comment docs.

Just found this because I'm not running master and tried to load our data...
This solution works, but has the unfortunate side-effect of blowing up memory when loading a large dataset. On the other hand I'm not sure that scvi (or PyTorch) can work with sparse data anyway (I see this in the torch docs, but it's still experimental). It would be nice to maintain sparsity but if nothing downstream will work I guess there's no point.


"per" should have higher precedence than /

≫ 3 USD per gallon / 10 miles per gallon * 500 miles
   (((3 USD / gal) / 10 mi) / gal) × 500 mi
   = 150 USD/gal²

1 / mile per gallon is interpeted as (1/mile) per gallon. Much like implicit multiplication, "per" should have higher precedence than explicit division.

Thank you for your feedback!
Could you please transfer this ticket to the Insect repository?
purescript-quantities is only the underlying library for handling physical units.


Enhance : Ui of the Signup page

I would like to change the ui of the Signup page to make it more attactive by adding some backgrounds ,hover effects.

So , please assign this issue to me.

That's great @Pragati-3003 ! I appreciate your enthusiasm to contribute to the project. Adding backgrounds and hover effects to the Signup page to make it more attractive sounds like an excellent idea. To proceed with this task, please create a design or mockup showcasing the changes you would like to make. Once you have the design ready, kindly share it with us. We can then discuss the implementation details and assign the task to you. Thank you for your interest and contribution!

That's great @Pragati-3003 ! I appreciate your enthusiasm to contribute to the project. Adding backgrounds and hover effects to the Signup page to make it more attractive sounds like an excellent idea. To proceed with this task, please create a design or mockup showcasing the changes you would like to make. Once you have the design ready, kindly share it with us. We can then discuss the implementation details and assign the task to you. Thank you for your interest and contribution!

Okie , I'll share screenshots when the design will ready.

This is the sample design, if you wanna any other changes than please inform me.

Check out the New Redesigned on Readme file
Thanks  You !

@Pragati-3003 Do yo want to work on any issue right now ?


Command parsing rework.

I thought having functional console commands was a good idea to code.
Added multiple interfaces and abstracts to rework client / chat / server console commands.
Chat commands and server commands are sort of integrated, client commands are not yet.
On a related note do we really not have shared interfaces?

What am I doing wrong?

Also, what about client commands?  Shouldn't commands be processed only on the client?

@YotaXP client console commands aren't implemented yet.

For some reason the console on the client can also execute specific commands on the server so I have to sync the available ones etc... which is why it's taking a while to code.


How can I send a list in the select query with IN?

How can I send a list in the select query with 'IN'?
For example:
var ids []uuid.UUID = ...

const query = "SELECT * FROM Products WHERE Id IN (@Ids) AND Deleted=0"

rows, err := repo.db.QueryContext(ctx, query,
  sql.Named("Ids", ids),
)
if err != nil {
return nil, err
}
defer rows.Close()

Best regards.

SQL doesn't have a way to pass arrays at the protocol level.
Even .Net doesn't have a way to do it per https://stackoverflow.com/questions/2377506/pass-array-parameter-in-sqlcommand

Thanks


[Bug] Can not use firebase services in ios when facebook sdk version 9.0.0 added to the unity project.

[REQUIRED] Please fill in the following fields:

Unity editor version: 2019.4.13f1___
Firebase Unity SDK version: 7.0.2____
Source you installed the SDK: Unity Package Manager _____ (.unitypackage or Unity Package Manager)
Problematic Firebase Component: Auth, Database,Cloud Messaging, Analytics___ (Auth, Database, etc.)
Other Firebase Components in use: _____ (Auth, Database, etc.)
Additional SDKs you are using:Facebook, AdMob, Agora (Facebook, AdMob, etc.)
Platform you are using the Unity editor on: Mac(Mac, Windows, or Linux)
Platform you are targeting: iOS, Android(iOS, Android, and/or desktop)
Scripting Runtime: IL2CPP (Mono, and/or IL2CPP)

[REQUIRED] Please describe the issue here:
Our project's firebase services was working correctly until we added facebook sdk.
Steps to reproduce:

Create an emty firebase unity ios project.
Add firebase auth/database services to this project.
Add facebook unity sdk to the project.
Build project for xcode in order to run on a simulator.
When we run project on xcode (for iPhone 12 pro max) we encountered this error in the log file of xcode:
"Failed to read Firebase options from the app's resources (). Either make sure GoogleService-Info.plist is included in your build or specify options explicitly."
Although, GoogleService-Info.plist is located in the asset folder of project we get this error.

Have you been able to reproduce this issue with just the Firebase Unity quickstarts (this GitHub project)?
What's the issue repro rate? (eg 100%, 1/5 etc)
What happened? How can we make the problem occur?
This could be a description, log/console output, etc.
If you have a downloadable sample project that reproduces the bug you're reporting, you will
likely receive a faster response on your issue.
Relevant Code:
// TODO(you): code here to reproduce the problem

Hi @ervandogan12,
Thanks for reporting the issue. Could you verify if the issue persists with the latest version of the Firebase SDK (7.1.0) and the Unity Editor (2020.3.2f1 for LTS)?

thanks for your interest. The problem has been solved by the use of Facabook SDK 9.0.0.

@ervandogan12  How did you resolve this issue?
Which Facebook SDK version was causing this problem and which Facebook SDK version resolved the issue?


use mimetypes library in view_files()

this is regarding issue #17. mimetypes library was implemented in the utils.py file but the view_files() function in actions.py was missed. this pull request fixes this.

LGTM :).
@shivam1708 @nurdtechie98 can you please have a look at this?
Thanks


Create Schema Relationships

All incident relationships are one to many. Council from legal_case are one to one. Looks like black might have changed some of the quotes from single to double quotes in the scraper.
Entity relationship diagram of the relationships defined in this PR:

Looks clean from high level but can someone with better pythons eyes have a look? @DMalone87 @dwreeves

once conflicts resolved then will merge

Ready for merge now. Made some updates with @dwreeves to standardize table names and fix a few bugs here and there

LGTM.
We have a few things we're not sure of yet, but I don't think they're a big deal to resolve now; we can solve them here but they're not a blocker for merge IMO.

is this ready to be merged?

@JMStudiosJoe yes!


DatastoreServiceImpl create method Unit testing

This is for VMWare north bound plugin.
Out of three modules, this UT is for plugin module.
This is the pull request for Unit testing DatastoreServiceImpl create method.
This is not having the full coverage of DatastoreServiceImpl.
Attached the screenshot for coverage.
I will add class description and method description in Next PR.

A small comment on package order.
Can we also see if these tests can be included in the build script.(can be planned in next PRs also)

Will do it in coming PR. Noted and mailed to you as remonder.


Best practice for migrate to new certificates ?

Our app using a pinned client to fetch data from backend server, but the certificate for the server hostname will expire soon.
The way how our pinned the certs is following the official doc
 CertificatePinner certificatePinner = new CertificatePinner.Builder()
       .add("publicobject.com", "sha256/afwiKY3RxoMmLkuRW1l7QsPZTJPwDS2pdDROQjXw8ig=")
       .add("publicobject.com", "sha256/klO23nT2ehFDXCfx3eHTDRESMz3asj1muO+4aIdjiuY=")
       .add("publicobject.com", "sha256/grX4Ta9HpZx6tSHkmCrvpApTQGo67CYDnvprLg5yRME=")
       .add("publicobject.com", "sha256/lCppFqbkrlJ3EcVFAkeip0+44VaoJUymbnOaEUk7tEU=")
       .build();

Can someone point me to the best practice to migrate to new certificate.
Is that possible pinned old and new certs at same time ?

You'll want to add pins for the new certs alongside the old ones. If possible, you can use the same subjects & public keys for your new certs, in which case your new pins and old pins will be the same.

Isn't it better to use a stable pin from your Intermediate CA (with a backup CA?).  That way you can freely rotate your certificates.  I'd suggest that getting your own private keys leaked is a lot more likely that the CA.


Submodule config get/set not working

Perform all steps below and tick them with [x]

[x] Check the related part of the Documentation
[x] Update openHASP to the latest version
[x] Reproduce the issue and describe all steps

Describe the bug
Originally I submitted a feature request to get / set the gpio configuration via MQTT but it turned out that none of the config/submodule commands work.
To Reproduce
Publish and empty paylod to hasp/<nodename>/config/gui. No response.
Same experience for all config/submodules.
Go to web interface > Configuration > Display Settings. Check the value for Long Idle, make sure it's not 224.
Publish payload {"idle2":224} to hasp/<nodename>/config/gui. Watch the debug console, nothing happens.
Expected behavior
Check the value for Long Idle in the web interface again by refreshing the page. Should have been changed, but it didn't.
Empty payloads to hasp/<nodename>/config/gui should result in responses published to hasp/<nodename>/state/config
Screenshots or video
n/a

Also output[x] does not work anymore:
MSGR: Command 'output[1]' not found => 1

config/submodule act as normal commands and are also accepted on hasp/<nodename>/command/config/submodule.
Dunno if it makes sense to keep a separate config topic for those.

Just tried both:
hasp/<nodename>/command/config/gui
hasp/<nodename>/config/gui

No response on either.


Capistrano's repo url

In the document: https://github.com/atmos/heaven/blob/master/doc/providers.md
It says we should use https:// instead of git:// for repo url. However, in such case, git will ask for the username & password, which obviously will break the deployment .. How can I resolve this?

You can encode the username and password in the URL or use a credential cacher.

I feel using<EMAIL_ADDRESS>is somehow anti-pattern... I'd need to write this in my cap's deploy.rb
Any specific reason why not use<EMAIL_ADDRESS>protocol? I've tried it, and it works with heaven.

That's fine and I use that pattern pretty frequently myself. Using the HTTPS protocol is generally easier since some firewalls and stuff block ssh access.

My thing is, if I use capistrano, then I'd need to write the deployer's github account/password in deploy.rb Which means I will check them into git ... I thought check in any sensitive information into git is not OK?
Hmm.. I give it a second thought, maybe we can write the account/password into ENV, and then let the capistrano read the account/password from there?
Thanks!

There's also git credential caching where you can run git ls-remote https://github.com/me/my-repo and have it store the passwords for future use. Using the environment is probably a good idea, that's where the ssh keys used for cap accessing the remove servers are stored currently.

I try to use credential caching. And now git ls-remote works.
However, the git remote update seems not working (here is cap's logs):
INFO [5f7e3d75] Running /usr/bin/env git remote update as<EMAIL_ADDRESS> DEBUG [5f7e3d75] Command: cd /Users/deployer/www/guardian/repo && ( PATH=/usr/local/bin:$(/usr/local/bin/npm bin):$PATH RBENV_ROOT=~/.rbenv RBENV_VERSION=2.2.0 GIT_ASKPASS=/bin/echo GIT_SSH=/tmp/guardian/git-ssh.sh /usr/bin/env git remote update )
 DEBUG [5f7e3d75] 	Fetching origin
 DEBUG [5f7e3d75] 	Fetching origin
 DEBUG [5f7e3d75] 	Error reading response length from authentication socket.

What does the "error reading ..." mean?
Thanks.

I can't find that call in the heaven source code.
~/p/heaven(master*)$ ack -r "git remote update"
~/p/heaven(master*)$

Sorry for not make this clear. This is capistrano's log. So actually this call should reside in capistrano.
I'm just wondering if this has anything to do with my heaven's setting.
Thanks.

I don't think so. It depends on the environment that heaven was launched under and it is expected that most of that environment is passed on to other processes. My guess is that somewhere along the chain of invoking processes a shell isn't getting access to the auth socket that's used in the failed ssh exchange.

Isn't this what the DEPLOYMENT_PRIVATE_KEY environment variable is for?
We're using git@github.com:owner/repo.git urls without a problem. A deploy private key is set as an environment variable. The public key has been added to GitHub and the servers we're deploying to.

@dblandin It's easy for them to be different in a lot of contexts. Yeah, though, make it the same is the easy way out.

I'm not gonna be working on this project in the foreseeable future.


improvement:修改判断显示任务节点log所影响单据中的表单、创建服务所属服务目录下拉未全展示和修改项目列表新增编辑校验

Codecov Report

Merging #44 (85cbcef) into v2.6.x_develop (9231c88) will not change coverage.
The diff coverage is n/a.

@@               Coverage Diff               @@
##           v2.6.x_develop      #44   +/-   ##
===============================================
  Coverage           51.30%   51.30%
===============================================
  Files                 688      688
  Lines               36407    36407
===============================================
  Hits                18678    18678
  Misses              17729    17729

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 9231c88...85cbcef. Read the comment docs.


chore: update angular2 to 2.0.0-alpha.45

Nice. Saw the Changelog and I don't think we need to update our directives.
Will merge this when I get home
El 29/10/2015 16:22, "Pawel Kozlowski"<EMAIL_ADDRESS>escribió:

You can view, comment on, or merge this pull request online at:
https://github.com/ng-bootstrap/core/pull/59
Commit Summary

chore: update angular2 to 2.0.0-alpha.45

File Changes

M package.json
https://github.com/ng-bootstrap/core/pull/59/files#diff-0 (2)

Patch Links:

https://github.com/ng-bootstrap/core/pull/59.patch
https://github.com/ng-bootstrap/core/pull/59.diff

—
Reply to this email directly or view it on GitHub
https://github.com/ng-bootstrap/core/pull/59.


Adding name to input descriptor.

Adding an optional name field to input descriptor. This is not yet approved as yet, and is a reference point .
https://github.com/decentralized-identity/presentation-exchange/issues/359
@decentralgabe if you'd prefer me to close this PR, that's fine. I made this originally thinking that there was an update to support the above, then realized after that the name field was supported one level above the proposal.

Hey @andorsk you'll need to request to add this to the specification in DIF before we'll be able to incorporate this into the codebase. https://github.com/decentralized-identity/presentation-exchange

sounds good. I'll close this for now.


Clarify experimental reason #1

Signed-off-by: Pablo Musa<EMAIL_ADDRESS>

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: pmusa
Once this PR has been reviewed and has the lgtm label, please assign vjjmiras for approval by writing /assign @vjjmiras in a comment. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

content/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce, pmusa
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

content/OWNERS [jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 26fb1e4319c3858fbedd6d0f64b8ad519e47abf6


Implement error toasts

Pretty trivial; replace non-existent toast.error method with addErrorAlert. Also fixed up grammar for error messages.
Resolves #252

are we using this? i think it is ignored...

are we using this? i think it is ignored...


Daily build is not set up

Expected Behavior
CI should build main daily, whether or not there is a pull request on it for that day.
Current Behavior
The cron job is not set up.
Ideas for Improvement
Set up a cron job on Travis CI to build main daily.

A Cron job is added on Travis to automatically build the main branch on a daily manner with Always run option (daily build will always be triggered even if there has been a build within the last 24 hours).


Why header appear when scroll reachs bottom of current view ?

On iOS device only the header appear when scroll reachs bottom of my flatlist.
I've been try also your demo on my expo go app and there is same problem.
Is there a config to avoid this problem?

it's due to iOS's bounce effect.
And it's a limitation of this library.


Shturman spawns with multiple SSK keys in single raid

General information:
Project issue is for:
Server 3.8.0 BLEEDINGEDGE
"commit": "28c9ddad9c03ce539f3f9ce6c447a98368382917",
"buildTime":<PHONE_NUMBER>719

Expected result:
Shturman may have a number of keys/cards but should only have 1 x SSK key in a single raid
Actual result:
Shturman had 2 x SSK keys in addition to Labs keycard and 1 or 2 other keys.
I think one was in pockets and the other was in the vest. Can't confirm for the moment
How to reproduce:

Play woods. Can set boss spawn chance to 100 in config
Kill Shturman
Check loot

Screenshots:

Attachments

image.png (134 KiB)

Originally written by R3

Previous related issue (closed): https://dev.sp-tarkov.com/SPT-AKI/Issues/issues/343
Related discussion in Discord from this message onward. Selection of few comments below:

[12:54 AM]E: Unique boss items should be limited to 1 per raid
[1:10 AM]bandit: afaik only one
[1:11 AM]bandit: my guess? because there can be multiple keys, it's rolling for keys and the 100% chance key is overwriting it
[1:12 AM]bandit: might be worth checking all bosses and how they produce key loot

Originally written by R3

Both SSK keys spawned in pockets

Re-verified with clean install Developer/BEAR. Only modification made was config for boss chance:
Aki_Data\Server\database\locations\woods\base.json
...
    {
      "BossChance": 100,
      ...
      "BossName": "bossKojaniy",
...

Attachments

image.png (374 KiB)
server-2024-02-12.log (114 KiB)
2024.02.11_23-41-24_<IP_ADDRESS>.28476 traces.log (68 KiB)
LogOutput.log (55 KiB)

Originally written by R3

Just played on latest 28c9dd build, both keys in secure container were from the 1 kill, can confirm bug is current

Attachments

2024-02-12[01-23]_31.5, -2.0, -55.9_0.5, 0.1, -0.1, 0.9_8.35 (0).png (1633 KiB)

Originally written by ldw420

Fixed with: https://dev.sp-tarkov.com/SPT-AKI/Server/commit/8fe30f6fd715036bb09f24dccae3dff41a638396
and
https://dev.sp-tarkov.com/SPT-AKI/Server/commit/fdcecdd942a8754f2ff85246e5e1f7f843ae5469

Originally written by chomp

apply the fix and he only have 1 key now

Originally written by holynevil

BE c4520d confirmed fixed on 3/3 kills. Closing, please remove testing tag
Thanks!

Originally written by R3


tor-browser-bundle-bin: 11.0.7 -> 11.0.9

Description of changes
Package update. It seems it is primarily a bugfix release (Firefox is not updated), but it includes an openssl update to 1.1.1n, which has severity HIGH.

TBB Announcement:

This releases fixes bug tor-browser#40802 which caused some users to be unable to access client authorized onion services.
We use the opportunity as well to update various other components of Tor Browser:

OpenSSL 1.1.1n

We also switch to the latest Go version (1.17.8) for building our Go-related projects.

OpenSSL Announcement:

The OpenSSL project team would like to announce the forthcoming release of OpenSSL versions 3.0.2 and 1.1.1n.
[...]
These are security-fix releases. The highest severity issue fixed in these releases is HIGH:

Therefore:

Please consider adding the security label
Please backport to release-21.11 after merging

Thanks!
Things done
Building on i686Linux (still) fails due to a dependency (graphene-hardened-malloc), as written here.

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[X] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage1 package updated:
tor-browser-bundle-bin (11.0.7 → 11.0.9)
...
1 package built:
tor-browser-bundle-bin

[X] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[X] Fits CONTRIBUTING.md.

Notify
@matejc (one of the maintainers), @lourkeur (reviewer during last updates)

Result of nixpkgs-review pr 164962 run on x86_64-linux 1

1 package built:

tor-browser-bundle-bin

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/469


Mono10p packed pixel format decoding

Describe the bug
I downloaded the tagged version 1.2.8 where I saw that some packed pixel formats were supported (issues #146 and #167). 12- and 14-bit formats were mentioned in those issues but I have a camera (Mako U-130B from Allied Vision) that can give Mono10p and it seems Harvesters doesn't decode this format correctly.
In util/pfnc.py the Mono10p format gets handled by _10p.expand(array) via the subclasses _Mono_10p and Mono10p when buffer.payload.components[0].data_format == 'Mono10p', which returns an array of the wrong length and where pixel intensities are scrambled (incorrect). For instance, I acquired 1280*1024=1310720 pixels so that the Mono10p-packed raw buffer has 1638400 bytes (1.25 B/px = 10b/px), but then _10p.expand(array) gives 1228800 array elements with incorrect values.

After comparing to the packing formats defined in https://www.emva.org/wp-content/uploads/GenICam_PFNC_2_3.pdf (mainly pages 32 and 34) I think the  _10p.expand(array) is a slightly incorrect (off by 1 bit) implementation of Mono10c3p32 and the equivalent RGB10p32, where 4 bytes give 3 pixels (ignoring 2 bits of padding). But the Mono10p as defined on page 34 should use 5 bytes to give 4 pixels.
Expected behavior (& fix)
In the attached patch  I have replaced the _10p.expand(array)-method with what I believe is the correct implementation for Mono10p, based on the PDF-documentation and based on the actual bytes I get from this camera (the images get the correct size and look good). (Well, I didn't actually run with the patched util/pfnc.py yet, I applied the conversion after having exported the raw buffer of bytes.)

Since there may well be a use-case for the Mono10c3p32 and the equivalent RGB10p32 packings, my patch file also keeps a renamed version of the old _10p.expand(array)-method where I documented what it does, and modified it to avoid the off-by-1-bit error for one of the three pixels per chunk. So I believe it now matches the documented Mono10c3p32 and RGB10p32, but I didn't create or look for the suitable classes in util/pfnc.py where this method would have to be moved to be useful.
Since version 1.2.8 where any packed formats are supported is not so old, I would guess not many users rely on the old behaviour. If there are other cameras where the old behavior was good we should of course find some way to keep it possible to use, but my search through closed issues didn't show anyone having requested Mono10p or the old version's behavior.
System information:

OS: Windows 10
Python: 3.7.9
Harvester: 1.2.8
GenTL Producer: Allied Vision's Vimba (although not much mentioned, the installation gives a CTI file I can use with Harvesters) over USB3.
Camera: Mako U-130B from Allied Vision

@erik-mansson Halle Erik, thank you very much for your valuable report. I will look at the suggested patch and merge it in the master. Regards, Kazunari.

Please feel free to re-open this ticket if there still be a bug. Regards, Kazunari.


Couchpotato config = confused

So i've read the readme about 100 times, i've been using your and promoting your script everywhere i go, and i've adjusted based on what actually works. In your readme, youve stated to set the renamer to 'run every = 0' but unless i'm mistaken, the actual script gets fired POST RENAMER, so if the renamer doesnt ever run, how in the heck does the conversion ever get triggered. I've tested this every time i've updated both couchpotato and your git, and yet if i leave 'run every = 0' literally nothing ever moves. either the readme needs updating or i'm missing something major. the only way i get it to work is to completely disregard your instructions and set the renamer to literally anything that isnt 0, such that it works just fine. perhaps i'm missing something?

All of the post downloader scripts trigger a renamer scan (SABPostProcess.py, NZBGetPostProcess.py, uTorrentPostProcess.py) which tells CP the download is complete and to start the renamer scan, then when the renamer scan is finished the final PostProcess.py CouchPotato plugin gets run which tags the file with the metadata it needs from couchpotato

thanks for the quick response, and i guess i'm clearly missing something. so i dont know if this is completely inappropriate but are you available to clear this up? via google+ (hangouts) or am i totally off base by asking. i can provide my settings, i know working with oracle if you want progress sometimes getting people on the phone and demonstrating can be simply the most effective method. anyway, let me know, not trying to accuse you of a bug, just not fully under standing. i've been putting this off for some time for fear of being 'that person'

Can't tonight but yeah I can help you out when I get a chance. But it's not super complicated, what program are you using to do your downloading?
—
Sent from Mailbox
On Tue, Mar 3, 2015 at 11:51 PM, datrumole<EMAIL_ADDRESS>wrote:

thanks for the quick response, and i guess i'm clearly missing something. so i dont know if this is completely inappropriate but are you available to clear this up? via google+ (hangouts) or am i totally off base by asking. i can provide my settings, i know working with oracle if you want progress sometimes getting people on the phone and demonstrating can be simply the most effective method. anyway, let me know, not trying to accuse you of a bug, just not fully under standing. i've been putting this off for some time for fear of being 'that person'
Reply to this email directly or view it on GitHub:
https://github.com/mdhiggins/sickbeard_mp4_automator/issues/209#issuecomment-77096840

ok, not a problem
I guess here is a quick summary
couchpotato --> deluge
iv'e set couch rename to run every and force every = 0
however when the download completes, nothing moves. it sits in my download complete location and never actually gets moved to my final destination
i've tested this by adding a new movie, and setting everything up, and letting it sit for 10 hours (most recent test). However if i update the renamer to 'run every = 1' then everything operates as expected.
The issue i have is following the instructions vs what i know works. thus why i'm bringing this to your attention. if i follow what the readme states, nothing ever moves from complete to my movie collection. if i follow what i know works, it does, however the instructions are incorrect. just trying to figure out a middle ground

i work from home, and am pretty open to when i can take a web conf. Please let me know if i'm being out of line by requesting this, just trying to help based on my understanding of the instructions which may be incorrectly interpreted by others.

So the issue is here is that I don't have a postprocessing script for deluge. Normally the order of operations is as follows, using uTorrent as an example:
CouchPotato finds movie, passes download to uTorrent
uTorrent downloads
Download completes, uTorrent executes uTorrentPostProcess.py
uTorrentPostProcess.py converts file (if convert here is enabled) and then tells CP a download has finished, tells it where the file is, and kicks off renamer.scan
CP process, renames, and moves the file
CP executes its post processing script passing on the IMDB ID
Conversion is done if it wasn't previously, then file is tagged.

If you're going to use a program that doesn't have a script to tell couchpotato the download is finished, you're gonna have to use a blackhole and timed scan.

ah-ha. so in reality i need to define a 'run every > X' where X is greater than 1, because i dont have an appropriate downloader than can execute a script to convert and then let CP know it's done. perfect! so my 'known to work' settings are accurate, just not in line with the instructions on the site. as simply as this may seem, can i make a suggestion to include this in the readme. I only say this as a proud user of this script! i cannot express how much this script has simplified my life. i really hope that plex and others pick you up and include your work in the standard normalization of media

you are welcome to close hell even delete this thread! thanks again for your quick response

I'll update the readme to make a note of this. Sorry for the confusion


Remove hasSwiftRuntime API in next major version

hasSwiftRuntime always returns true starting with Xcode 13. Firebase stops using this API in https://github.com/firebase/firebase-ios-sdk/pull/8215

This should be done in the 8.0.0 release for Firebase 10.


Compatability with Jolt?

When jumping with the Character and holding space bar to climb or vault over it works half the time. When climbing from the ground floor it works as intended but when jumping from a ledge to another it pauses in the air and flies back to the ledge you just jump on. Happens with the jolt but works fine with the default. Thank you for the immersive FPS controller best I've seen.

Hi! I'll look into it, thanks for your feedback :)


Commit as markdown on completion

Is there an option (or if not would love if there was) to have a task render as markdown to a note upon completion.
For example: When I complete a task (before it disappears) it gets rendered to a particular section in my daily note (## completed or something like that).
Thanks!  Awesome plugin!

Duplicate of https://github.com/jamiebrynes7/obsidian-todoist-plugin/issues/58


Add a couple extra impls to Secret<T>

This adds a couple extra impls to Secret<T> to make it easier to use.
My thoughts are adding Hash and PartialEq shouldn't really be a problem because this crate is more targeted towards shielding secret values from accidentally being written to logs, not for protecting the secret value from people who have access to the object from code (I can just transmute a Secret<T> to T after all).

Alright, after giving this some thought, I think I'm fine with merging this. I will be adding some documentation later on.


Get Alt Text

Hi
When i Call :
https://www.instagram.com/{usename}/?__a=1
i can get alt text as "accessibility_caption" but is not in https://www.instagram.com/graphql/query/?query_hash
how to get alt text ?
please guide me
thanks

i found a solution for this ?
my i start working on this ?


Might need to rename the file "Colors 3" Guessing the : character is causing errors

Error on Download .zip -> extract Windows 10

There's also this when doing a git clone:
rober@DESKTOP-S9MGKSE MINGW64 /c/git
$ git clone git@github.com:robertas12345/my_notes.git
Cloning into 'my_notes'...
remote: Enumerating objects: 136, done.
remote: Counting objects: 100% (21/21), done.
remote: Compressing objects: 100% (21/21), done.
remote: Total 136 (delta 4), reused 0 (delta 0), pack-reused 115
Receiving objects: 100% (136/136), 427.61 MiB | 9.36 MiB/s, done.
Resolving deltas: 100% (5/5), done.
error: invalid path 'Data Structures & Algorithms/Some random *Search and Sort* notes for midterm.pdf'
fatal: unable to checkout working tree
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'

Thank you! I didn't notice it, just scanned and renamed them and apple apparently put these characters 😔 merged your PR!


Update montage.py

@Eric89GXL I updated the docstring here a bit to fix some of the errors. It still make need to be flushed out better but I figured this is a start.

@dengemann does this match your understanding?
FYI @teonlamont looks like you errantly pushed a branch to upstream for this one. I killed the push related builds.

sigh, I was trying to make a quick patch to the documentation and it forgot that it makes it directly to the repo. I was the one who came up with the DigMontage. It was inspired by Montage class @dengemann wrote. There was a need for having digitizer data from non-Elekta system to integrate easily and use somewhat of a format. I pulled from the mne manual for the terminology.

ok, here's the thing about the digitizer data, it's not head-centered so it is technically not in the head space, it is based on the reference and receiver of the digitizer. it is only in the device space after you transform the data to be center on the fiducial points

so this is where the transform argument comes in. it takes the digitizer data, creates the axes of the head space based on the Neuromag specification, where the y-axis is centered through the nasion, the x-axis is defined as the plane between the lpa and rpa, and the z-axis is the cross-product

it is only in the device space after you transform the data to be center on the fiducial points

Okay, that sounds like FIFFV_MNE_COORD_DIGITIZER, which is fine (points can be in any space really). So read_dig_montage the code, when it says this:
    transform : bool
        If True, points will be transformed to Neuromag space.
        The fidicuals, 'nasion', 'lpa', 'rpa' must be specified in
        the montage file. Useful for points captured using Polhemus FastSCAN.
        Default is True.

What it "Neuromag space" means is not Neuromag device coords, but rather "head coordinates"?

What it "Neuromag space" means is not Neuromag device coords, but rather "head coordinates"?

Neuromag RAS head coordinate space.

Okay, that sounds like FIFFV_MNE_COORD_DIGITIZER, which is fine (points can be in any space really).

yeah, we didn't know the name of this coordinate space. it's this one you mentioned

@christianbrodbeck and I had worked out this when we were implementing the KIT module years back (time flies!). keep track of which space you're in is a bear

That makes sense, then. I guess if you change "Neuromag space" to "head coordinates" (what we call it everywhere else in mne-python AFAIK) or if you want to be more verbose "Neuromag RAS head coordinate space" or even "Neuromag standard head coordinates based on cardinal landmarks (RAS)" that would work.

yeah, we didn't know the name of this coordinate space. it's this one you mentioned

In transforms.py the human-readable version of this is "isotrak". So calling it the "isotrak or digitizer native space" would work.
Thanks for clearing up those defs, that makes much more sense now.

do you know where the name "isotrak" comes from?

"Isotrak is a trademark of Polhemus Navigational Sciences" it's what Neuromag dig is done with.
I am still curious about what the transform=False option is for, though. In those use cases, are we still guaranteed (or do we expect) that hsp and elp points will already be in Neuromag head coords, and thus don't need to be transformed? Or can the DigMontage class sometimes have hsp and elp in non-(Neuromag)head coords?

I am still curious about what the transform=False option is for, though. In those use cases, are we still guaranteed (or do we expect) that hsp and elp points will already be in Neuromag head coords, and thus don't need to be transformed? Or can the DigMontage class sometimes have hsp and elp in non-(Neuromag)head coords?

I think the  transform=False was meant for data that were already in the Neuromag head coords.

ok, so we state that the fiducials have to be in RAS which we were doing a transform from Anterior-Left-Superior (native digitizer space) to Right-Anterior-Superior space. Then we were transforming from RAS to Neuromag head space. I think the first transform is unnecessary since you can just go from native digitizer space to Neuromag space.

I think the first transform is unnecessary since you can just go from native digitizer space to Neuromag space.

I think that's also likely.  If it's not RAS the transform might not just be a rotation (it could have reflections), but I think that's probably okay. Do you have time to test it?
Just noticed something else:
    elp : array, shape (n_hpi, 3)
        The positions of the head-position indicator coils in 3d.
        This is typically in the acquisition digitizer space.

But in read_dig_montage it states that the elp should have cardinal landmarks, followed by HPI...?

I think that's also likely.  If it's not RAS the transform might not just be a rotation (it could have reflections), but I think that's probably okay. Do you have time to test it?

they are both right-handed coordinate system so I think I worked it out before that the transformation would work. I don't have the time to test it right now. maybe tomorrow (no promises).

Just noticed something else:

unfortunately, it was just sloppiness :(

actually, no I take back the last comment, it is only the length of the hpi b/c you give the fiducials separately in the constructor

actually, no I take back the last comment, it is only the length of the
hpi b/c you give the fiducials separately in the constructor

Look at the code for the reading function, i don't think the fids are ever
removed from the set of points

In other words, starting from [here] (https://github.com/mne-tools/mne-python/blob/master/mne/channels/montage.py#L447) the ELP gets read, and the fiducial points are never removed. Should they be?

@Eric89GXL they should have been. I've fixed it so that this is now handled. since it was being done internally and doesn't how users interact with it, it's all good

LGTM, +1 for merge. This will help me to continue with my PR, I think. We can deal with the read_montage vs. read_dig_montage over there I guess.

thanks @teonlamont


Unable to publish web app

We have deployed the solution in our prod env now (after testing in dev fine), there is a change though as in prod we are using a PEP and VNET integration due to locked down networking etc.
We have a Workload identity federation service connection, which has been granted the 'web contributor' RBAC role on the web app, but the pipeline is failing the publish task saying it needs the web publisher RBAC role.
The API is being called and its verifying that auth is enabled, but still insists that the RBAC role is not configured.
Az context AccountType: 'ClientAssertion'
  Az context related parameters: -SubscriptionId4AzContext==''; -TenantId4AzContext==''; -SkipAzContextSubscriptionValidation=='False'
  Check Subscription: 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' (criteria: quotaId notLike 'AAD*'; state==enabled)
 +Processing new bearer token request 'ARM' "https://management.azure.com"
 +Bearer token 'ARM': [tokenRequestProcessed: '10/15/2024 08:39:16']; [expiryDateTime: '10/15/2024 09:34:26']; [timeUntilExpiry: '00:55:09.1166470']
  [AzAPICall 1.2.3] DEBUGTASK: Check Subscription: 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' (criteria: quotaId notLike 'AAD*'; state==enabled) -> try#1 processing: Check Subscription: 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' (criteria: quotaId notLike 'AAD*'; state==enabled) uri: 'https://management.azure.com/subscriptions/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx?api-version=2020-01-01'
  [AzAPICall 1.2.3] DEBUGTASK: Check Subscription: 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' (criteria: quotaId notLike 'AAD*'; state==enabled) -> unexpectedError: false
  [AzAPICall 1.2.3] DEBUGTASK: Check Subscription: 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' (criteria: quotaId notLike 'AAD*'; state==enabled) -> apiStatusCode: '200' (OK)
  [AzAPICall 1.2.3] DEBUGTASK: Check Subscription: 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' (criteria: quotaId notLike 'AAD*'; state==enabled) -> listenOn=Content (1)
  [AzAPICall 1.2.3] DEBUGTASK: Check Subscription: 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' (criteria: quotaId notLike 'AAD*'; state==enabled) -> NextLink/skipToken/NextMarker: none
   Subscription check succeeded - quotaId: 'EnterpriseAgreement_2014-09-01'; state: Enabled
   Az context Tenant: 'xxxxxxxxxxxxxxxxxxxxxxxxx'
   Az context Subscription: 'xxxxxxxxxxxxxxxxxx (xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx)' (state: Enabled)
  Az context check succeeded
  Get ARM locations
  [AzAPICall 1.2.3] DEBUGTASK: Get ARM locations -> try#1 processing: Get ARM locations uri: 'https://management.azure.com/subscriptions/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/locations?api-version=2020-01-01'
  [AzAPICall 1.2.3] DEBUGTASK: Get ARM locations -> unexpectedError: false
  [AzAPICall 1.2.3] DEBUGTASK: Get ARM locations -> apiStatusCode: '200' (OK)
  [AzAPICall 1.2.3] DEBUGTASK: Get ARM locations -> listenOn=Default(Value) value exists (91)
  [AzAPICall 1.2.3] DEBUGTASK: Get ARM locations -> NextLink/skipToken/NextMarker: none
   Get ARM locations succeeded (locations count: '91')
    56 physical ARM locations found
  [AzAPICall 1.2.3] DEBUGTASK: AzAPICall - Check if WebApp (xxxxxxxxxxxxxxxxxxxxxxxxxxxx) has Authentication enabled -> try#1 processing: AzAPICall - Check if WebApp (xxxxxxxxxxxxxxxxxxxxxxxxxxxx) has Authentication enabled uri: 'https://management.azure.com/subscriptions/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx/resourceGroups/xxxxxxxxxxxxxxxxxxxxx/providers/Microsoft.Web/sites/xxxxxxxxxxxxxxxxxxxxxxxxxxxx/config/authsettings/list?api-version=2021-02-01'
  [AzAPICall 1.2.3] DEBUGTASK: AzAPICall - Check if WebApp (xxxxxxxxxxxxxxxxxxxxxxxxxxxx) has Authentication enabled -> unexpectedError: false
  [AzAPICall 1.2.3] DEBUGTASK: AzAPICall - Check if WebApp (xxxxxxxxxxxxxxxxxxxxxxxxxxxx) has Authentication enabled -> apiStatusCode: '200' (OK)
  [AzAPICall 1.2.3] DEBUGTASK: AzAPICall - Check if WebApp (xxxxxxxxxxxxxxxxxxxxxxxxxxxx) has Authentication enabled -> listenOn=Content (1)
  [AzAPICall 1.2.3] DEBUGTASK: AzAPICall - Check if WebApp (xxxxxxxxxxxxxxxxxxxxxxxxxxxx) has Authentication enabled -> NextLink/skipToken/NextMarker: none
WebApp (xxxxxxxxxxxxxxxxxxxxxxxxxxxx) has Authentication enabled: True
NoDefinitionInsightsDedicatedHTML =
Exception: /agent/_work/_temp/1a7f15ab-c3bd-465a-be17-f329baaa6c9a.ps1:28
Line |
  28 |              throw 'Make sure that the ManagementGroupId variable in t …
     |              ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | Make sure that the ManagementGroupId variable in the
     | AzGovViz.variables.yml has correct casing (Linux!=linuX)

HTML NOT published
RBAC Role 'Website Contributor' is required

##[error]PowerShell exited with code '1'.

I am not sure what is causing it, therefore as suggested - dump all the variables that are used to see where it fails.

hi Paul,
add some write-host for the variables that are used in the following lines:
https://github.com/Azure/Azure-Governance-Visualizer/blob/d84fd890ebe3db196ee24cc9bd1fc82e02e0197e/.azuredevops/pipelines/AzGovViz.pipeline.yml#L153
OR
https://github.com/Azure/Azure-Governance-Visualizer/blob/d84fd890ebe3db196ee24cc9bd1fc82e02e0197e/.azuredevops/pipelines/AzGovViz.pipeline.yml#L161
you can ping me on LinkedIn.

I've messaged on linked in

This is now resolved, I had the var for management groups only selected in the variables yaml.
This resulted in unexpected behaviour and a mismatch of files generated (in the repo/wiki) and expected in the publish stage.


fix(form): add element for form label text, make it bold

fixes https://github.com/patternfly/patternfly-next/issues/1943
per @kybaker & @mceledonia only the label text should be bold, not the icons or anything else that a user might add. So added an element to target the label text and make that bold. Should look like

Deploy preview for pf-next ready!
Built with commit e5a444b0adac5da98c3cdbe4eed75474d2581565
https://deploy-preview-1952--pf-next.netlify.com

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


config: drop MTB value for NeoFS networks to three days

We want to cut the tail more aggressively, what matters is state, but not old blocks and transactions that contracts don't use in any way. #3493 suggests that it's safe to limit the tail to one day, but let's be a bit more conservative for now.
As a sidenote, EVM only allows to fetch things from the recent 256 blocks.

from the recent 256 blocks.

Too harsh to me, but they likely have their reasons for that.

Should create an issue in Infra to upgrade our nodes?

I'll do that as well as update neo-project/neo configs.

I'll do that as well as update neo-project/neo configs.

Sorry, noticed too late, PR in neo-projet created.


malformed validation scenarios fail silently when running for Job

Schematron based validation scenario that has an XML error with the schematron, fails silently when applied and running for a Job.
However, when testing that scenario against a single record in Combine (via the GUI), the error is apparent, e.g.:
Opening and ending tag mismatch: rule line 33 and pattern, line 34, column 12 (file_3fb170911b114205a51b6a7ecdc5484b.sch, line 34)

Would be beneficial to inform user that a Validation Scenario was erroring for records when running for a Job, instead of failing quietly.
Thoughts/Questions:

perhaps the "validation" tab in a Job details page should show errors, in addition to valid/invalid?
should a Job get marked as invalid when errors are reported to be conservative with thinking a Job / Records are valid?  (tried applying validation, didn't work, assume we don't know about the validity of the records)
how to bubble up errors from Spark?

each time a Record fails a validation, a corresponding RecordValidation instance is created
wonder if this could record the error that occurred during validation?  treat the Record as if it failed validation (and in a sense it did), and instead of recording why the validation failed, record the error as best as possible?

Not yet tested with:

python code snippet validation scenarios
Elasticsearch query validation scenarios

I'm not entirely sure this is part of this ticket? If not, I can split it out:

YASS

Resolves #431


Add CertifyLegal to query known package

Description of the PR

Fixes #2253
Example using the demo stack and demo docs after collection with add license on ingest flag set:
❯ go run ./cmd/guacone/main.go query known package<EMAIL_ADDRESS>
{"level":"info","ts":1730698004.0871081,"caller":"logging/logger.go:79","msg":"Logging at info level","guac-version":"v0.0.1-custom"}
{"level":"info","ts":1730698004.087162,"caller":"cli/init.go:65","msg":"Using config file: /home/rob/go/src/guacsec/guac/guac.yaml","guac-version":"v0.0.1-custom"}
+------------------------------------------------+
| Package Name Nodes                             |
+-----------+-----------+------------------------+
| NODE TYPE | NODE ID # | ADDITIONAL INFORMATION |
+-----------+-----------+------------------------+
+-----------+-----------+------------------------+
Visualizer url: http://localhost:3000/?path=25409,25408,4450
+----------------------------------------------------------------------------------------------+
| Package Version Nodes                                                                        |
+--------------+-----------+-------------------------------------------------------------------+
| NODE TYPE    | NODE ID # | ADDITIONAL INFORMATION                                            |
+--------------+-----------+-------------------------------------------------------------------+
| hasSrcAt     | 167073    | Source: sourcearchive+https://org.apache.logging.log4j/log4j-core |
+--------------+-----------+-------------------------------------------------------------------+
| certifyVuln  | 41980     | vulnerability ID: ghsa-7rjr-3q55-vv33                             |
| certifyVuln  | 41981     | vulnerability ID: ghsa-8489-44mv-ggj8                             |
| certifyVuln  | 41982     | vulnerability ID: ghsa-fxph-q3j8-mv87                             |
| certifyVuln  | 41983     | vulnerability ID: ghsa-jfh8-c2jp-5v3q                             |
| certifyVuln  | 41984     | vulnerability ID: ghsa-p6xc-xr62-6r2g                             |
| certifyVuln  | 41985     | vulnerability ID: ghsa-vwqq-5vrc-xw9h                             |
| certifyVuln  | 166892    | vulnerability ID: ghsa-7rjr-3q55-vv33                             |
| certifyVuln  | 166893    | vulnerability ID: ghsa-8489-44mv-ggj8                             |
| certifyVuln  | 166894    | vulnerability ID: ghsa-fxph-q3j8-mv87                             |
| certifyVuln  | 166895    | vulnerability ID: ghsa-jfh8-c2jp-5v3q                             |
| certifyVuln  | 166896    | vulnerability ID: ghsa-p6xc-xr62-6r2g                             |
| certifyVuln  | 166897    | vulnerability ID: ghsa-vwqq-5vrc-xw9h                             |
+--------------+-----------+-------------------------------------------------------------------+
| certifyLegal | 42719     | declared: NONE, discovered: NONE                                  |
| certifyLegal | 167585    | declared: Apache-2.0, discovered: Apache-2.0                      |
+--------------+-----------+-------------------------------------------------------------------+
| hasSBOM      | 183697    | SBOM Download Location: deps.dev                                  |
+--------------+-----------+-------------------------------------------------------------------+
Visualizer url: http://localhost:3000/?path=25410,25409,25408,4450,167073,41980,41981,41982,41983,41984,41985,166892,166893,166894,166895,166896,166897,183697,42719,167585

PR Checklist

[x] All commits have a Developer Certificate of Origin (DCO) -- they are generated using -s flag to git commit.
[ ] All new changes are covered by tests
[ ] If GraphQL schema is changed, make generate has been run
[ ] If GraphQL schema is changed, GraphQL client updates/additions have been made
[ ] If OpenAPI spec is changed, make generate has been run
[ ] If ent schema is changed, make generate has been run
[ ] If collectsub protobuf has been changed, make proto has been run
[ ] All CI checks are passing (tests and formatting)
[ ] All dependent PRs have already been merged

I can't comment on the implementation details, but the user experience is spot on. Do we need to explicitly add it to the --help output though, or does that get picked up automatically?

I can't comment on the implementation details, but the user experience is spot on. Do we need to explicitly add it to the --help output though, or does that get picked up automatically?

It looks like it gets picked up automatically, here it is with the additions:
❯ go run ./cmd/guacone/main.go query known package --help

Query for all the available information on a package, source, or artifact.
  <type> must be either "package", "source", or "artifact".
  <subject> is in the form of "<purl>" for package, "<vcs_tool>+<transport>" for source, or "<algorithm>:<digest>" for artiact.

Usage:
  guacone query known [flags] <type> <subject>

Flags:
  -h, --help   help for known

Global Flags:
      --add-license-on-ingest   if enabled, the ingestor will query and ingest clearly defined for licenses. Warning: This will increase ingestion times
      --add-vuln-on-ingest      if enabled, the ingestor will query and ingest OSV for vulnerabilities. Warning: This will increase ingestion times
      --csub-addr string        address to connect to collect-sub service (default "localhost:2782")
      --csub-tls                enable tls connection to the server
      --csub-tls-skip-verify    skip verifying server certificate (for self-signed certificates for example)
      --gql-addr string         endpoint used to connect to graphQL server (default "http://localhost:8080/query")
      --header-file string      a text file containing HTTP headers to send to the GQL server, in RFC 822 format


Upgrade TypeScript ESLint Parser and Plugin to the 2.x version range

Fixes https://github.com/facebook/create-react-app/issues/7555

Fixes #7529

Can you upgrade the deprecated usage of @typescript-eslint/no-angle-bracket-type-assertion?
Mentioned in original issue #7529 (comment)

Yes! It's done. :)

I have created this PR already. Duplicate of https://github.com/facebook/create-react-app/pull/7540


M01-LAB03: Wrong link to other lab

Contact Details
No response
What happened?
Lab: 03 - Managed identity for projects and pipelines
Description of issue:
In the "Before you start" section the link "Complete the lab..." doesn't work (404).
The links points to:
https://microsoftlearning.github.io/implement-security-through-pipeline-using-devops/Instructions/Labs/APL2001_M03_L02_Configure_Agents_And_Agent_Pools_for_Secure_Pipelines.md
It should point to:
https://microsoftlearning.github.io/implement-security-through-pipeline-using-devops/Instructions/Labs/APL2001_M02_L02_Configure_Agents_And_Agent_Pools_for_Secure_Pipelines.html
Relevant screenshots

Good catch, @mkennten. Thanks! It will be fixed in the PR #51. Closing the issue.


[Debug] Remove unnecessary DebugDescriptionMacro feature references (NFC)

The DebugDescription macro has been accepted. Additionally, the DebugDescriptionMacro feature was not providing conditional declaration as I originally intended. References to the feature are not needed and can be removed.

@swift-ci test

Can we also remove the DebugDescriptionMacro feature entirely?

Ideally, yes. However I was wondering: If I remove the feature, and some build references, will there be an error for referencing a non-existent feature?

Can we also remove the DebugDescriptionMacro feature entirely?

Ideally, yes. However I was wondering: If I remove the feature, and some build references, will there be an error for referencing a non-existent feature?

It's not an error to reference a non-existent feature, and hasFeature on it doesn't have much meaning for user code, so I think this one might actually be safe to remove. Maybe do that in a separate PR Just In Case.

I realized I can easily answer my own question 🤦 – I will remove the feature altogether.

Removing the feature: https://github.com/swiftlang/swift/pull/77739


Sometimes /prompt_gem does not work

When i use the command ‘/prompt_gem xxx’, it rewrites the text with Gemini, but it does not create any images.
Related Info:
command: python3 tg.py <tg_token> <bing_cookie> -c config.toml
config.toml add "[google_gemini] api key"
Traceback (most recent call last):
File "/home/test/.local/lib/python3.10/site-packages/telebot/init.py", line 955, in infinity_polling
self.polling(non_stop=True, timeout=timeout, long_polling_timeout=long_polling_timeout,
File "/home/test/.local/lib/python3.10/site-packages/telebot/init.py", line 1043, in polling
self.__threaded_polling(non_stop=non_stop, interval=interval, timeout=timeout, long_polling_timeout=long_polling_timeout,
File "/home/test/.local/lib/python3.10/site-packages/telebot/init.py", line 1118, in __threaded_polling
raise e
File "/home/test/.local/lib/python3.10/site-packages/telebot/init.py", line 1074, in __threaded_polling
self.worker_pool.raise_exceptions()
File "/home/test/.local/lib/python3.10/site-packages/telebot/util.py", line 147, in raise_exceptions
raise self.exception_info
File "/home/test/.local/lib/python3.10/site-packages/telebot/util.py", line 90, in run
task(*args, **kwargs)
File "/home/test/.local/lib/python3.10/site-packages/telebot/init.py", line 6801, in _run_middlewares_and_handler
result = handler'function'
File "/home/test/tg_bing_dalle/tg.py", line 207, in prompt_gemini_handler
respond_prompt(bot, message, bing_cookie_pool, bing_cookie_cnt, s)
File "/home/test/tg_bing_dalle/responder.py", line 47, in respond_prompt
limit = image_obj.get_limit_left()
File "/home/test/.local/lib/python3.10/site-packages/BingImageCreator.py", line 104, in get_limit_left
r = self.session.get("https://www.bing.com/create")
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 557, in get
return self.request('GET', url, **kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 544, in request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 657, in send
r = adapter.send(request, **kwargs)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 498, in send
raise ConnectionError(err, request=request)
requests.exceptions.ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))

sometimes did not work or always did not work?>

I tried commenting out image_obj.get_limit_left(), and it seems to be working normally now. In case of a failure, after it rewrites the text with Gemini, this python script will stuck at get_limit_left func.
def respond_prompt(
    bot: TeleBot,
    message: Message,
    bing_cookie_pool: Iterator[ImageGen],
    bing_cookie_cnt: int,
    prompt: str,
) -> None:
    # Find a cookie within the limit
    within_limit = False
    for _ in range(bing_cookie_cnt):
        image_obj = next(bing_cookie_pool)
        limit = image_obj.get_limit_left()
        if limit > 1:
            within_limit = True
            break

thanks for that, can you open one pr?

OK thanks a lot


Fix driver close with alert

This PR fixed #41.
I added E2E test for failure with alert.

Before fix: E2E test aborted on the test.

https://travis-ci.org/rsp9u/side-runner-py/builds/519056723

After fix: E2E test ran all.

https://travis-ci.org/rsp9u/side-runner-py/builds/519058736

Codecov Report

Merging #42 into master will decrease coverage by 0.98%.
The diff coverage is 50%.

@@            Coverage Diff             @@
##           master      #42      +/-   ##
==========================================
- Coverage   84.22%   83.23%   -0.99%
==========================================
  Files           7        7
  Lines         336      346      +10
==========================================
+ Hits          283      288       +5
- Misses         53       58       +5

Impacted Files
Coverage Δ

side_runner_py/main.py
83.95% <50%> (-2.24%)
:arrow_down:

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 abc9648...cc355aa. Read the comment docs.


We need Feed Back From you on this form. By Today

Sponsor feedback.pdf
Please Send this to our teacher. we are group Capstone++
We should have got this to you sooner. Its due Today.
<EMAIL_ADDRESS>the subject should be “Capstone II Project Feedback"
Please Let us know if your able to do this or already did.

Done!


Provide ISED access to the Portal with Business BCeID

As an ISED member
I want to access the analyst portal
So that I can better collaborate with NWBC on the applications and projects
Description:
This ticket is to provide ISED with access to the Analyst Portal using their Business BCeID
Acceptance Criteria:

[x] Get access to a test Business BCeID account for the team
[x] ISED can log in with their Business BCeID (use login button in top right corner of login)
[x] ISED can view and make changes the same as the analysts role
[x] History table shows the name of ISED person for 'who' made changes

Note:  https://github.com/bcgov/sso-keycloak/blob/dev/docs/migration-guide.md
{Page Name}
Screen
[wireframe 1]
[wireframe 2]

[ ] .

Page Behaviours

[ ] .
[ ] .
[ ] .

Validations

[ ] .
[ ] .
[ ] .

Actions

[ ] .
[ ] .
[ ] .

Not included:

.
.

Implementation Details

DB:

.
.

Middleware:

.
.

Frontend:

.
.

Tests:

.
.

Documentation:

.
.

Hey team! Please add your planning poker estimate with Zenhub @AntBush @marcellmueller @VB-at-Bis

I don't know if it's the same redirect issue we are having with logging in internally to the analyst portal but I can't seem to be able to get to the analyst dashboard after logging in with the Business BCeID.  After logging in, I get redirectd to the Applicant dashboard and I can't figure out how to get to get to the analyst portal

Did you add an analyst role to your BCeID in the SSO dashboard?

hah, that was it!  Thank you! It works now!

Haha nice, at least you got to confirm that people with regular BCeID with no role added can’t login to the analyst side 🙂


Dockerfile bug can't cd to

Step to reproduce:

git clone
docker build .

Docker build fail with this error:
/bin/sh: 1: cd: can't cd to /go/src/github.com/kerberos-io/opensource/backend

Fixed thanks!


Fixed min width & height for resource cards & text horizontal scrolling

Describe what your pull request addresses

[ ]

Test Instructions

[ ] Open https://deploy-preview-159--gateway-edit.netlify.app/
[ ] select test_org2
[ ] Open mat 1:1
[ ] The user should be able to scroll to the top of the text no matter how small the card size is reduced.
[ ] https://images.zenhubusercontent.com/310359593/381cb8e0-a7a4-441f-ab14-1c358210f8a2/issue_137_a.mp4
[ ] Should not be able to shrink the width or height of cards to the point where elements are moved off of the card

This change is

LGTM


"次のステートメント" needs to be replaced with "Next ステートメント"

https://docs.microsoft.com/ja-jp/office/vba/language/concepts/getting-started/writing-executable-statements

Article has been HumanTranslated and published live. The issue is fixed


As an operator I want to be able to filter on any custom fields that are available on the cart

This is dependent on the introspection endpoint
As an operator I want the system to inspect the Cart schema and be able to filter by any attribute on my custom extended version of the cart.
Additionally I want to select a custom subset of fields that I want to filter on and store that setting in ShopSettings, so that the list of attributes is kept manageable.

@vannguyenn The introspect endpoint PR has been merged so this work should be unblocked


Remove warning modal before entering Postgres credentials

This uses the tree item as a prompt instead of the warning modal.

From https://github.com/microsoft/vscode-cosmosdb/pull/1381#discussion_r399463021

I know we say it's usually better to split PRs up, but can you combine this with https://github.com/microsoft/vscode-cosmosdb/pull/1395? It's literally touching the same exact code and would be easier to make sense of the two together

Closing in favor of https://github.com/microsoft/vscode-cosmosdb/pull/1397


Image is really hard to use

This is more of a general issue, but I thought I'd mention it here so the maintainers get the feedback: Image frequently collapses to zero height/width in dynamically sized containers and it's a pain in the butt to develop with. It would be great to have better defaults for Image, or maybe wrap it in a different component that is less clever about sizing.

Here's a simple repro:

Yes, I agree. I think having optional width and height property could solve a lot of the usability issues with Image. It's a pretty common pattern to wrap it with a Box that sets those constraints.


Can we get support for childnodes somehow?

Please see this SO question for reference: http://stackoverflow.com/questions/41492886/dom-selector-to-get-text-of-element-ignoring-children/41492946?noredirect=1#comment70192261_41492946
Basically I have an element that looks like this:

This Page! Next Page

I want the tab to be named "This Page!" but if I use {.pageTitle} it will be named "This Page! Next Page".

p.s. I LOVE this extension.

Hi @ScottBeeson,
Thanks for your feedback!
You can see the attached commit, this unexpected behavior will be fixed in the next version. Be sure to opt-in for new version notification in Tab Modifier settings. :)
Best


Updates from default calendar module

Bringing in fixes from the default MMM calendar module and the ical module that that uses that have happened since this was forked. For me, these fixed problems with repeated events and time zones.

Thanks for making this!


update README with instructions for local dev

GitHub pages does some funky custom jekyll stuff, so we need to install the github-pages gem in order to run this locally.
This commit adds the configuration for that and the commands to run to have it running locally at localhost:4000.

The README is rendered directly to the home page, with your PR the local instructions will show up at the top of the deployed page.
What if the instructions were in a separate DEVELOPMENT.md or LOCAL_DEV.md?   Not convention, but maybe good enough given how it builds?

Ah yes...principle of "most" surprise! Hahaha. No worries, I'll sort it