Do you support grpc?

Here is my code：
 local p, err = proto.new("proto-file/student.proto")
if err then
    ngx.log(ngx.ERR, ("proto load error: %s"):format(err))
    return
end
local m = util.find_method(p, "htsc.grpc.streamtest.Greeter", "GetStudentFamily")
if not m then
	return
end
-- Build request binary as method input type from request data (query string, post body, or JSON body)
local encoded = pb.encode(m.input_type, util.map_message(m.input_type, default_values or {}))
local size = string.len(encoded)
 -- Prepend gRPC specific prefix data
-- request is compressed (always 0)
-- requesdt body size (4 bytes)
local prefix = {
	string.char(0),
	string.char(bit.band(bit.rshift(size, 24), 0xFF)),
	string.char(bit.band(bit.rshift(size, 16), 0xFF)),
	string.char(bit.band(bit.rshift(size, 8), 0xFF)),
	string.char(bit.band(size, 0xFF))
  }
  local message = table.concat(prefix, "") .. encoded
  local url = "<IP_ADDRESS>:50033"
  local opts = {
	  --stream = false,
	  http2 = true,
	  headers ={
		[":path"] = "/htsc.grpc.streamtest.Greeter/GetStudentFamily",
		["te"] = "trailers",
		["content-type"] = "application/grpc",
		["user-agent"] = "grpc-c++/1.24.0-dev grpc-c/8.0.0 (linux; chttp2; ganges)",
		["grpc-accept-encoding"] = "identity,deflate,gzip",
		["accept-encoding"] = "identity,gzip",
	  },
	  body = message
  }
  local r, err = req.request("POST",url,opts)
  if not r then
	ngx.log(ngx.ERR, err)
	return
  end
  local body = r:body()
  ngx.print(body)

but  the body is not available for the response，my grpc server return response OK, also have body

@majc08149 Thanks for report. I will try to reproduce it on my machine.

in file  http2.lua，the function read_body，it seems that  if there is a header, the the following data must have a data as body. the grpc response is  header-->data-->header，so i think  it is the problem
function _M:read_body(stream)
if stream.done then
return ""
end
local session = stream.session

while not self.cached_body do
    local ok, err = handle_frame(self, session, stream)
    if not ok then
        return nil, err
    end
end

local body = self.cached_body.data
self.cached_body = self.cached_body.next

return body

end

in file http2.lua，the function read_body，it seems that if there is a header, the the following data must have a data as body. the grpc response is header-->data-->header，so i think it is the problem
function _M:read_body(stream)
if stream.done then
return ""
end
local session = stream.session

while not self.cached_body do
    local ok, err = handle_frame(self, session, stream)
    if not ok then
        return nil, err
    end
end

local body = self.cached_body.data
self.cached_body = self.cached_body.next

return body

end

So have you tried to remove the trailer headers? By just sending a trivial HTTP/2 request.

@majc08149 I have observed this problem, I will try to fix it.

@majc08149 I have submitted a PR to fix this problem, just see https://github.com/tokers/lua-resty-http2/pull/4 for the details.


Add message box widgets

For example, enaml has 'about', 'critical', 'information', 'question', and 'warning' functions that display an appropriate message box popup. Possibly relies on resolving #11, as they need to be in a separate window. In my opinion these are as important as the grid layout. It seems logical to use the Qt Dialog class for this:
https://doc.qt.io/qt-5/qdialog.html

Agreed. I'll get around to adding these.

We now have WindowPopView in v1.5.0 https://pyedifice.github.io/versions.html#v1-5-0


Add CC blocks to Sidekick block library

New CC interactive marquee blocks are currently not visible in sidekick library.
Updating the library url to pull cc blocks as well.
Resolves: MWPW-140466
Test URLs:

Before: https://milo.adobe.com/tools/library
After: https://milo.adobe.com/tools/library?ref=main&repo=cc&owner=adobecom&host=adobe.com&project=CC

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (1875ebf) 100.00% compared to head (30bfc3a) 88.28%.
Report is 65 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##              main     #145       +/-   ##
============================================
- Coverage   100.00%   88.28%   -11.72%
============================================
  Files            2        8        +6
  Lines           14      657      +643
============================================
+ Hits            14      580      +566
- Misses           0       77       +77

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


ColdFusion 9 errors fixed

I downloaded this source and tried to run it on ColdFusion 9 but got various errors. Made the changes and committed them. Didn't test these changes in any other CF engine.

All your errors are specific to ColdFusion 9 : the Facebook SDK requires ColdFusion 9.0.1 (which is a recommended upgrade).

damn it. you're right. argh! why doesn't adobe not put the most up to date version when you download it from them? grrr.
My bad!


[Feature]: Text in both Hindi and English

Hi, I would like to add both Hindi and English text to the website which will be helpful for multilingual population to access this website and would help a large number of population to be influenced by Chanakya's teachings.
I have suggested the following chnages.

@Avdhesh-Varshney Please Assign this to me.

@ISHITA1234 Not required. This will distort the ui.


hello my Korean friend

Wanted to ask how does it compare to other STR, that are multilingual
thank you

Hi,
You can use our train/test datasets for comparison.
Note that the purpose of this work is to investigate cross-lingual learning in multilingual STR, not to compare existing methods.


Update quickstart-onboard-powershell.md

Added New-AzRoleAssignment

@jianyunt : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

@Jak-MS : Thanks for your contribution! The author(s) have been notified to review your proposed change.


setup_repo_sicknetwork not found

Hello
The "setup_repo_sicknetwork.bat" file is not in the repo.
Is it still necessary to work inside the SICK network?
Thank you
Rotem

Hello Rotem,
setup_repo_sicknetwork.bat is not necessary anymore to work inside the SICK network. This is a mistake in the documentation. This will be corrected in the next release.

Thank you!


Add Programs for Array Operations

Hi, Shall I work on this?

Hey there, I'd like to work on this

Hello @KeerthanaHK  and @aakash-hacks. You are free to contribute.

@Anushka-codergirl  please add hacktoberfest in topics or else our PRs won't be considered

Done. Check it.

Hi,
Can i work on this ?


Remove version: Ruihu.Apifox version 2.5.3

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: http://cdn.apifox.com/download/2.5.3/Apifox-2.5.3.exe
OK
(Automated message - build 923)

Close with reason: Package still available;


Ability to change details of an order with pending payment

Buyer should be able to change details (quantity, shipping address, e-mail, coupon code and memo) of an ongoing order with pending payment.
This happens when buyer closes the order when QR code for payment is being shown and access it later through Menu > Purchases (orders with "Awaiting Payment" status).
Maybe first-time buyers will close the order window when they see QR code, buy some bitcoins and return later, but wanting to change shipping address or quantity. Maybe buyer doesn't want to rewrite all his long memo instructions again.

At this point I don't think the transaction is changeable. Is that correct, @cpacia ?

If contract can't be changed at this point, at least there should be an option to create a new order of that listing (with a new order #), which would import Discussion (chat with vendor) and Details (address, coupons, moderator, quantity and memo) of the previous order.

How would that be different from just making a new order, other than pre-selecting a few options? That seems like an edge case to me.
If there is a minor issue with the order, you could use the built in order discussion to clear it up with the seller.

You could avoid the hassle of typing a long memo/coupon code again, or searching a moderator again.
All discussion would be in the same place.
Buyers that change address won't have to pay more if price goes up after purchase (original purchase had a discount).
When buying multiple listings on same order is implemented (shopping cart), users won't have to search all listings and set its quantities again.

I'm closing this issue, contracts are intentionally not changeable.


Fix the advanced settings view and functionality

So, I kind of broke things...
This fixes some styling that was broken on Firefox as well as some validation that was broken overall.

:+1:


RFC: add complex asset transfers instructions

Summary
This RFC proposes new instructions that provide a way to initiate asset transfers which transfer multiple types (teleports, local-reserve, destination-reserve) of assets, on remote chains using XCM alone.
The currently existing instructions are too opinionated and force each XCM asset transfer to a single transfer type (teleport, local-reserve, destination-reserve). This results in inability to combine different types of transfers in single transfer which results in overall poor UX when trying to move assets across chains.
Example usage
    // XCM to be executed locally
    let xcm = Xcm::<penpal_runtime::RuntimeCall>(vec![
        // Withdraw both ROCs and PENs from origin account
        WithdrawAsset(assets.clone().into()),
        // ROCs are reserve-withdrawn on AHR
        DestinationReserveWithdrawAssets(rocs.into()),
        // PENs are teleported to AHR
        TeleportTransferAssets(pens.into()),
        // Execute the transfers while paying remote fees with ROCs
        ExecuteAssetTransfers {
            dest: local_asset_hub,
            remote_fees: Some(AssetFilter::Wild(AllOf { id: rocs_id.into(), fun })),
            remote_xcm: xcm_on_ahr,
        },
    ]);

Proof-of-Concept
I also have a proof-of-concept implementation and a proof-of-concept asset transfer test, transferring 2 different types of assets across 3 chains.

cc @mrshiposha @xlc

PS: We could also probably do this in the one big instruction, further coupling concepts that work together. It would always require specifying a vector of AssetTransferType, even if it has only one element. That makes it good UX even when just doing a simple teleport.

enum Instruction {
  ...
  InitiateAssetTransfer {
    destination: Location,
    assets: Vec<AssetTransferType>,
    remote_fees: Option<AssetFilter>,
    remote_xcm: Xcm<()>,
  },
  ...
}

Yes, I like this ^

This pull request has been mentioned on Polkadot Forum. There might be relevant details there:
https://forum.polkadot.network/t/xcm-user-and-developer-experience-improvements/4511/21

This pull request has been mentioned on Polkadot Forum. There might be relevant details there:
https://forum.polkadot.network/t/managing-sas-on-multiple-reserve-chains-for-same-asset/7538/7

Unfortunately, following the repo migration to the new org, I lost write access to the PR (upstream) branch. I've opened the PR from a fork branch here https://github.com/polkadot-fellows/xcm-format/pull/63
Closing this one.


Improved U-Net for the ISIC 2018 Skin Lesion Segmentation Dataset - 45293915

This repository contains the code for the Improved U-Net model for the ISIC 2018 Skin Lesion Segmentation dataset (https://challenge.isic-archive.com/data/#2018). Contains the following files:

“modules.py" containing the source code of the components of your model where each componented is implemented as functions
“dataset.py" containing the data loader for loading and preprocessing the data
“train.py" containing the source code for training, validating, testing and saving your model.
“predict.py" showing example usage of the trained model.

Riley Ball | 45293915

Well organized files.
Algorithm solves the problem appropriately. Average Dice Coefficient in testing dataset: 0.81. Very good output.
Correctly using TensorFlow to construct the Improved U-Net models and functions.
Good coding design.
Sufficient docstring and comment in the code.
Easy difficulty problem, no higher difficulty marks.

Marking
Good Practice (Design/Commenting, TF/Torch Usage)
Adequate design and implementation
Good spacing and comments
Header blocks missing -1
Recognition Problem
Solves problem
Driver Script present
File structure present
Shows Usage & Demo & Visualisation & Data usage
Module present
Commenting
No Data leakage
Difficulty: Easy -10
Commit Log
Meaningful commit messages
Progressive commits used
Documentation
ReadMe acceptable, missing refs -1
Model/technical explanation
Good Description and Comments
Markdown used and PDF submitted
Pull Request
Successful Pull Request (Working Algorithm Delivered on Time in Correct Branch)
No Feedback required
Request Description good

Please revert changes to repo README files for merging, does not affect grade only merge.

Sorry a bit confused, which README file is this in relation to and which changes? (did I modify a README I wasn't supposed to or is this in relation to the README that documents my model?)

Please revert changes to repo README files for merging, does not affect grade only merge.

Sorry a bit confused, which README file is this in relation to and which changes? (did I modify a README I wasn't supposed to or is this in relation to the README that documents my model?)

Please revert changes to repo README files for merging, does not affect grade only merge.

Sorry a bit confused, which README file is this in relation to and which changes? (did I modify a README I wasn't supposed to or is this in relation to the README that documents my model?)

You shouldn't modify the original ReadMe.md files when you first fork Shakes' repository. All student-constructed folders/files, including your own Readme.md for your project, should be packed in one folder under the ‘recognition’ folder. So you need to recover the original README file and move your own readme file into your own folder.

No feedback attempt and no feedback marks lost.


Document pipeline.yml environment interpolation and caveats

Our current trigger documentation uses environment variable interpolation in the examples, but that's not supported in Buildkite Agent 2.0, only in the new Buildkite Agent 3.0 betas. Which can cause confusion (buildkite/feedback#260).
It is very common to want to use trigger steps in this way, so instead of just modifying those examples not to use interpolation, this adds documentation to the pipeline upload command, and a note below the trigger examples. The idea is that people will upgrade to 3.0 if necessary, or use the workaround if they can't upgrade their agent.

[x] First cut
[x] Update pipeline upload docs for $VAR, ${VAR} and ${VAR:-default} support etc

I had a read over the agent tests and source, and put together these docs.
@keithpitt as the author of said source code, could you please give this a quick check for accuracy?
@harrietgrace can I get you to check if there's anything you see that could be fixed, or any glaring problems?

Thanks!

I think we're ready to go:

Will await @keithpitt’s eyes…

Nice, there's a few extra nuggets of into that you may wanna mention. Aside from that, 🚀

Ok, all done!


Attempting to login to a disabled account will not render the page with the alert.

What is the difference between a res.render
https://github.com/benrobson/zander-web/blob/677f3c9773872783b917c0937f7687ac036dd09c/controllers/passport.js#L28
and a return done(...)
https://github.com/benrobson/zander-web/blob/677f3c9773872783b917c0937f7687ac036dd09c/controllers/passport.js#L48
...maybe this is how you can show it's disabled?


QueryDSL add Support for 5.0

I tried to update QueryDSL to 5.0 and it failed with an Exception like:
java.lang.NoSuchFieldError: hints

	at com.blazebit.persistence.querydsl.AbstractBlazeJPAQuery.getQueryable(AbstractBlazeJPAQuery.java:234)

Are there plans to update to 5.0.0?

Hi, would you mind trying out the current snapshot? Support for 5.0 was committed recently: https://github.com/Blazebit/blaze-persistence/commit/ecdb6858b134b9265253905f45c3a4c97677526e

Thanks for the hint. Can I find a snapshot build on any maven repository? Did not find it in the docs. Or do I have to build my own?

The OSS snapshots are available in the Sonatype repository: https://oss.sonatype.org/content/repositories/snapshots/

Thanks for letting me know. I tired some basic examples, which seem to work!

Great to hear that. I will try to publish a release this weekend after integrating some GraphQL related updates.


Can't get ExplicitNonNullaryApply working

Hey! I'm on Scala 2.13.3, SemanticDB 4.3.17, sbt-scalafix 0.9.17, I've locally published this repo and added this to SBT:
      ThisBuild / scalacOptions += "-Yrangepos"
      ThisBuild / scalacOptions += "-P:semanticdb:synthetics:on"
      ThisBuild / scalafixDependencies += "org.scala-lang" %% "scala-rewrites" % "0.1.0-SNAPSHOT"

and I can't get anything to work.
> scalafix ExplicitNonNullaryApply
scalafix.sbt.InvalidArgument: Unknown rule 'ExplicitNonNullaryApply'

Hmmm, ok, look at source code - try again:
> scalafix fix.scala213.ExplicitNonNullaryApply
java.lang.IllegalArgumentException: requirement failed: List(-target:11, -unchecked, -Wconf:msg=may.not.be.exhaustive:e, -Wdead-code, -Wunused:explicits, -Wunused:implicits, -Wunused:imports, -Wunused:locals, -Wunused:nowarn, -Wunused:patvars, -Wunused:privates, -Xlint:adapted-args, -Xlint:constant, -Xlint:delayedinit-select, -Xlint:deprecation, -Xlint:eta-zero, -Xlint:implicit-not-found, -Xlint:inaccessible, -Xlint:infer-any, -Xlint:missing-interpolator, -Xlint:nonlocal-return, -Xlint:nullary-unit, -Xlint:option-implicit, -Xlint:poly-implicit-overload, -Xlint:private-shadow, -Xlint:stars-align, -Xlint:valpattern, -Xmixin-force-forwarders:false, -Xno-forwarders, -Xsource:2.13, -Ybackend-parallelism, 16, -Ycache-macro-class-loader:last-modified, -Ycache-plugin-class-loader:last-modified, -Yjar-compression-level, 9, -Ymacro-annotations, -Yno-generic-signatures, -Ypatmat-exhaust-depth, off, -Xcheckinit, -Xplugin:/home/golly/.cache/coursier/v1/https/repo1.maven.org/maven2/org/scala-js/scalajs-compiler_2.13.3/1.1.0/scalajs-compiler_2.13.3-1.1.0.jar, -Xplugin:/home/golly/.cache/coursier/v1/https/repo1.maven.org/maven2/org/typelevel/kind-projector_2.13.3/0.11.0/kind-projector_2.13.3-0.11.0.jar, -Xplugin:/home/golly/.cache/coursier/v1/https/repo1.maven.org/maven2/com/olegpy/better-monadic-for_2.13/0.3.1/better-monadic-for_2.13-0.3.1.jar, -Xplugin:/home/golly/.cache/coursier/v1/https/repo1.maven.org/maven2/org/scalameta/semanticdb-scalac_2.13.3/4.3.17/semanticdb-scalac_2.13.3-4.3.17.jar, -P:semanticdb:targetroot:/tmp/shipreq.sbt/webapp-client-loaders/target/scala-2.13/meta)

I'm I doing something wrong or there something wrong with the rule?

Hey.  I think you're running into https://github.com/scala/scala-rewrites/pull/34/files, which I hadn't realised until that PR.

Ok cool, I'm glad it makes sense to you. I did read through that PR though and I confess, it didn't quite make sense to me. Actually let me add a comment over there :)

Actually, I think I've got it! We need to wait for Scalafix 1.0 to be released before that rule can work, is that right?
Also do you know when that will be?

More immediately I think you should be able to fix your code by compiling it with 2.12 and then running the ExplicitNonNullaryApply rewrite.  I'm not sure where the failure is triggering (that "requirement failed" could be clearer) but basically while there is a scalameta semanticdb-scalac for 2.13, Scalafix doesn't support 2.13 yet.  And I'm not sure when Scalfix 1.0 will be out.

Merged #34, so people don't fall into this pitfall.  Improvement feedback is still welcome.


cant get plyr to work with require js

this is related to an issue that was opened in v2 ( #288 ) however i am using v3
for brevity i am only including prod code:
requirejs.config({
"paths":{
"plyrjs":"https://cdnjs.cloudflare.com/ajax/libs/plyr/3.5.6/plyr.min.js",
"swiperjs":"https://unpkg.com/swiper/js/swiper.min.js"},
"shim":{
"plyrjs":{"exports":"plyrjs"},
"swiperjs":{"exports":"swiperjs"}
}});
require(['plyrjs','swiperjs'], function()
{"use strict";

Expected behaviour
Actual behaviour
Steps to reproduce
Environment

Browser:
Version:
Operating System:
Version:

Console errors (if any)
Link to where the bug is happening

closing so i can add in diff issue and steps to reproduce


[Feat] Update the bio tab for characters.

@NekroDarkmoon Can you expand on what you mean by this? Is it just about removing the class and archetype boxes once classes have been added?


Recommended Updates.

Here's a list of things to update for possible new developers wanting to pick up with epic club.

Rewrite class based
Update password hashing to argon
Better error handling (Right now they are HTML static pages)
Switch from in-line styles to CSS files with HTML classes
Update to work on php8 and php7.x and take advantage of their syntax.
Maybe use PDO instead of MySQLI

The source is old, but not dead.
Why rewrite class based:
Because class based structures are much more maintainable than php-to-html code. Dividing the PHP from the HTML will help make the code cleaner and easier.
Why update password hashing to argon
Primarily because it's much more secure than the normal hashing, having won the competition of last year.
Why better error handling:
Because of the current one it's not functional, and tends to leave the user in a stall page.
why switch to CSS files instead of in-line CSS?
Because it helps and allows editing CSS easily and making new themes without having to edit every single piece of code.
Soon more...

Awesome! Will update once ready

Already working on it


stereo calibration

System information (version)

Operating System / Platform => Ubuntu20
OpenCV => 4.10
Ceres => NO
Boost => NO
C++ => NO
Compiler => NO

Vision system

Number of cameras => 2
Types of cameras => fisheye
Multicamera configurations => converging (overlapping, non-overlapping, converging)
Configuration file =>  *.YML(i.e. *.yml)
Image sequences =>  197

number of images per camera
if relevant and possible, please share image sequences

Describe the issue / bug
I am using your method for stereo calibration and then applying cv2.stereoRectify for stereo rectification. Since this function requires the camera's intrinsic and extrinsic parameters, I directly used the parameters from the yml file. However, the rectification result is very poor. Can you help me?

Thank you for using MC-Calib!
Could you please provide a pair of images from your camera setup along with the calibration results?
I suspect the issue might be due to the transformation being inverted compared to the OpenCV standard. If you share these details with me, I can provide the corrected code here, which could also be useful for future users.
What was the reprojection error you obtained from the calibration process?

The problem has been solved. I reversed the left and right camera


unable to run nni under window 10, as my company restrict the powershell script running

Short summary about the issue/question: my company restricts the powershell script running which nni depends on it, so I got all failed on the trials, but I can run bash script under my window 10, so am wondering if there is anyway to let nni generate and run bash script for the trails under window 10. I saw this code: https://github.com/microsoft/nni/blob/69cae211e2790a14f5a0c667b4ac92daaad5ea00/src/nni_manager/training_service/common/util.ts
but not sure if other codes need to be changed
Brief what process you are following:

How to reproduce it:

nni Environment:

nni version:latest
nni mode(local|pai|remote): local
OS:windows 10
python version:3.7
is conda or virtualenv used?: conda
is running in docker?:no

need to update document(yes/no):
Anything else we need to know:
Log message:

nnimanager.log and dispatcher.log :

nnictl stdout and stderr :

If you mean WSL or Cygwin, you can use NNI inside it but you are unlikely to be able to use CUDA.
Otherwise NNI does not support Windows OS without powershell. This environment is too unique so NNI will not support it.

does run Linux APP on Windows help with this problem?

hello @haoshuji, I will close this issue as it has not been updated for more than three months, feel free to reopen it if you still think it an active issue.


HDDS-9332. Handle empty unit check

What changes were proposed in this pull request?
If neither unit, nor native check is required, PR check is successful, but email notification says "PR run failed", which is confusing.  PR run is annotated with:
Error when evaluating 'strategy' for job 'unit'. apache/ozone/.github/workflows/ci.yml@d74a8a98c243d5b0a9a82f5b3c21525cfea89933 (Line: 231, Col: 16): Matrix vector 'check' does not contain any values

https://issues.apache.org/jira/browse/HDDS-9332
How was this patch tested?
Tested the case when no unit check is required:
https://github.com/adoroszlai/hadoop-ozone/actions/runs/6251667755
Full CI:
https://github.com/adoroszlai/hadoop-ozone/actions/runs/6251652835

@devmadhuu this is minor follow-up for HDDS-6618

@devmadhuu this is minor follow-up for HDDS-6618

Thanks @adoroszlai for handling this. LGTM +1

Thanks @devmadhuu, @sadanand48 for the review.


Generated Kernel is NULL

Hello,
In a fresh git clone, I'm getting the following error when I run "make tests":
Test: class uk.ac.manchester.tornado.unittests.TestHello
	Running test: testHello                  ................  [FAILED]
		\_[REASON] Task was not executed.
	Running test: testVectorAddition         ................  [FAILED]
		\_[REASON] [ERROR] Generated Kernel is NULL.
Please report this issue to https://github.com/beehive-lab/TornadoVM
	Running test: testSimpleCompute          ................  [FAILED]
		\_[REASON] [ERROR] Generated Kernel is NULL.
Please report this issue to https://github.com/beehive-lab/TornadoVM
	Running test: testSimpleCompute2         ................  [FAILED]
		\_[REASON] [ERROR] Generated Kernel is NULL.
Please report this issue to https://github.com/beehive-lab/TornadoVM
	Running test: testSimpleInOut            ................  [FAILED]
		\_[REASON] [ERROR] Generated Kernel is NULL.
Please report this issue to https://github.com/beehive-lab/TornadoVM
Test ran: 5, Failed: 5

And also more similar output for the rest of the unittests.
Also, on a simple test program of mine, adapted from the testHello unittest:
uk.ac.manchester.tornado.api.exceptions.TornadoRuntimeException: [ERROR] Generated Kernel is NULL.
Please report this issue to https://github.com/beehive-lab/TornadoVM
	at tornado.drivers.opencl@0.6/uk.ac.manchester.tornado.drivers.opencl.graal.OCLInstalledCode.checkKernelNotNull(OCLInstalledCode.java:353)
	at tornado.drivers.opencl@0.6/uk.ac.manchester.tornado.drivers.opencl.graal.OCLInstalledCode.submitWithoutEvents(OCLInstalledCode.java:359)
	at tornado.drivers.opencl@0.6/uk.ac.manchester.tornado.drivers.opencl.graal.OCLInstalledCode.launchWithoutDeps(OCLInstalledCode.java:389)
	at tornado.runtime@0.6/uk.ac.manchester.tornado.runtime.TornadoVM.execute(TornadoVM.java:498)
	at tornado.runtime@0.6/uk.ac.manchester.tornado.runtime.TornadoVM.execute(TornadoVM.java:194)
	at tornado.runtime@0.6/uk.ac.manchester.tornado.runtime.tasks.TornadoTaskSchedule.scheduleInner(TornadoTaskSchedule.java:421)
	at tornado.runtime@0.6/uk.ac.manchester.tornado.runtime.tasks.TornadoTaskSchedule.schedule(TornadoTaskSchedule.java:642)
	at tornado.api@0.6/uk.ac.manchester.tornado.api.TaskSchedule.execute(TaskSchedule.java:230)
	at TestHello.testHello(TestHello.java:69)
	at TestHello.main(TestHello.java:33)
Exception in thread "main" java.lang.AssertionError: Task was not executed.
	at junit@4.12/org.junit.Assert.fail(Assert.java:88)
	at junit@4.12/org.junit.Assert.assertTrue(Assert.java:41)
	at TestHello.testHello(TestHello.java:73)
	at TestHello.main(TestHello.java:33)

'tornado --devices' shows:
Number of Tornado drivers: 1
Total number of devices  : 1
Tornado device=0:0
	Clover -- AMD Radeon RX 5700 XT (NAVI10, DRM 3.36.0, 5.6.13-arch1-1, LLVM 10.0.0)
		Global Memory Size: 8.0 GB
		Local Memory Size: 32.0 KB
		Workgroup Dimensions: 3
		Max WorkGroup Configuration: [256, 256, 256]
		Device OpenCL C version: OpenCL C 1.1

Hi, can you run the following command?
$ tornado-test.py -V --debug -J"-Dtornado.fullDebug=True" uk.ac.manchester.tornado.unittests.TestHello#testVectorAddition

Additionally, we have tested on AMD using the ROCM drivers. We support from OpenCL 1.2 (I am not sure if that's the issue). Is it possible to update the drivers for your AMD?

Okay, so I got a useful error:
INFO: fatal error: cannot open file '/usr/lib/clc/gfx1010-amdgcn-mesa-mesa3d.bc': No such file or directory

A similar error also appears in clinfo, and from some searching it's possible that Navi 10 is not yet supported by mesa-opencl (?).
I'm currently educating myself on different frameworks related to OpenCL on AMD and seeing what is possible at the current time with this specific GPU.

Yes, it looks like an installation/configuration problem with OpenCL.

Yes exactly. I'll see if I can fix it for my Navi 10 or use another GPU...
Thanks for the support


Bid won message get trigger multi times if native template has multi  tag

Describe the bug
If native template has multi click links, then message: "Prebid Native" will get fired multi times, and it ends up bidWon event get fired multi times.
To Reproduce
Suppose there is a native template having following html:
%%PATTERN:hb_native_title%%

both title and icon both are clickable.
With such html, the issue will happen.
Reason:
code fire native ad impression are:
  function loadImpTrackers(adElements) {
      for(var i = 0; i < adElements.length; i++){
          let adId = readAdIdFromSingleElement(adElements[i]);
          fireTracker(adId, 'impression');
      }
  }

      if (adElements.length > 0) {
        loadImpTrackers(adElements);
      }

So the impression tracker get triggered for each  with pb-click class.
Suggest solution:
change loadImpTrackers so it only fires impress tracker for first element.

Since improvements from https://github.com/prebid/Prebid.js/issues/5149 is coming, this is no need anymore.


Update rdbms-types to support Date / Tmestamp

Purpose of this PR is to add datetime and timestamp support.

Note this will also require updating the conversion routines in the MySQL and Postgres factors.

Would love to handle this, but bandwidth is limited as I'm on holiday/PTO. I'm happy to punt as this would be a challenge on my side. Happy to do anything to assist.

I'm closing this in favour of #2890 - @tyler-harpool is aware.  Thank you again Tyler for getting this process under way!


docs: Remove outdated section

Description
Removes an outdated section in the README.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes.
Minimal checklist:

[ ] I have performed a self-review of my own code
[ ] I have added DocC code-level documentation for any public interfaces exported by the package
[ ] I have added unit and/or integration tests that prove my fix is effective or that my feature works

Thanks!


Remove AvroConverter plugin from Confluent Hub archive

The kafka-connect-avro-converter dependency is added to the POM for this connector so that the AvroData class can be used to convert from Avro to the Connect record format, but the actual AvroConverter class (or any of its nested classes) is never used. However, the Connect framework will still sometimes pick up the AvroConverter present in the plugin archive for the datagen connector and try to use that as an actual converter plugin, even though most of the transitive dependencies for the kafka-connect-avro-converter dependency are excluded, which then causes classloading issues.
The changes here are a bit of a hack: they alter the Confluent Hub archive generated during the connector build by removing the AvroConverter class (and all of its nested classes) from the kafka-connect-avro-converter JAR file, so that the converter is never picked up as a plugin by the Connect framework.
We could consider publishing the AvroData class as a separate Maven artifact so that people could add it as a dependency to their project without risk of this happening, but in the meantime, here's a quick-and-dirty solution that allows the connector to work alongside the Avro converter when both are loaded using the plugin path mechanism in Connect.

@chrise do you recall what classloading issues you ran into because of this setup?

@wicknicks the dependencies for the Avro converter are excluded from packaging with this connector.

Merging into master to address issues with CC-7254


Introduce IconSelectorWindow

Introduces IconSelectorWindow. Allows selecting icons from multiple libraries. Libraries can be set through iconLibraries prop on every relevant component (e.g. Style, IconEditor, etc.). Type definition of IconLibrary can be found in src/Components/.../IconSelectorWindow.tsx and looks as follows:
export type IconLibrary = {
  name: string;
  icons: {
    src: string;
    caption: string;
  }[];
};

Example:
var library = [{
    name: 'lib 1',
    icons: [{
      src: 'https://upload.wikimedia.org/.../128px-Parking_icon.svg.png',
      caption: 'first image'
    }, {
      src: 'https://upload.wikimedia.org/.../128px-Parking_icon2.svg.png',
      caption: 'second image'
    }]
  }, {
    name: 'lib 2',
    icons: [{
      src: 'https://upload.wikimedia.org/.../128px-Parking_icon3.svg.png',
      caption: 'first image second library'
    }]
  }];

IconSelectorWindow was integrated into ImageField. If property iconLibraries is undefined, ImageField behaves as before. If property iconLibraries is defined, a Button behind the input field appears that opens the IconSelectorWindow.
The selected Icon will be highlighted with a blue border. Hovering over an Icon sets the background color greyish.

@jansule https://commons.wikimedia.org/wiki/Category:Map_icons This could be source for some free icons... Maybe we add this to the demo

@KaiVolland added requested changes. please review again


/api/embed uses 512 token context window even though model was configured with 8192

What is the issue?
I'm using Continue.dev and have configured the following to generate embeddings:
"embeddingsProvider": {
    "provider": "ollama",
    "model": "mxbai-embed-large:latest"
  },

When inspecting the model, we see context is 8192:
ollama show --modelfile nomic-embed-text:latest | grep num_ctx
PARAMETER num_ctx 8192

However, it only seems to use 512 tokens in Ollama, while indexing we get:
[GIN] 2024/09/27 - 21:40:26 | 200 |  145.149375ms |       <IP_ADDRESS> | POST     "/api/embed"
INFO [update_slots] input truncated | n_ctx=512 n_erase=258 n_keep=0 n_left=512 n_shift=256 tid="0x1ebf88f40" timestamp=1727466026

OS
macOS
GPU
Apple
CPU
No response
Ollama version
0.3.12

Is it possible that Continue.dev is sending "options":{"num_ctx":512} in the request?
$ curl -s localhost:11434/api/embed -d '{"model":"nomic-embed-text:latest","input":"'"$(echo {1..1000})"'"}'
$ docker compose logs ollama | grep update_slots.*released
ollama-1  | DEBUG [update_slots] slot released | n_cache_tokens=1557 n_ctx=8192 n_past=1557 n_system_tokens=0 slot_id=0 task_id=58 tid="140157435772928" timestamp=1727489100 truncated=false
$ curl -s localhost:11434/api/embed -d '{"model":"nomic-embed-text:latest","options":{"num_ctx":512},"input":"'"$(echo {1..1000})"'"}'
ollama-1  | DEBUG [update_slots] slot released | n_cache_tokens=256 n_ctx=512 n_past=256 n_system_tokens=0 slot_id=0 task_id=11 tid="139978549817344" timestamp=1727489269 truncated=true

Hey @khromov it looks like you're using mxbai-embed-large with continue.dev, but nomic-embed-text with ollama show.
mxbai-embed-large has a 512 token context, while nomic-embed-text has an 8192 token context.
I'll go ahead and close the issue.


Docker volume plugin

Summary
Need instructions for how to specify the default EBS volume type and size when using the Docker Volume plugin.
I see how you can set some parameters (below) but not others.  I can get the full list by running docker plugin inspect rexray/ebs.
EBS_ACCESSKEY	The AWS access key
EBS_KMSKEYID	The encryption key for all volumes that are created with a truthy encryption request field
EBS_MAXRETRIES	the number of retries that will be made for failed operations by the AWS SDK	10
EBS_REGION	The AWS region	us-east-1
EBS_SECRETKEY	The AWS secret key
EBS_STATUSINITIALDELAY	Time duration used to wait when polling volume status	100ms
EBS_STATUSMAXATTEMPTS	Number of times the status of a volume will be queried before giving up	10
EBS_STATUSTIMEOUT	Maximum length of time that polling for volume status can occur	2m
EBS_USELARGEDEVICERANGE	Use largest available device range /dev/xvd[b-c][a-z] for EBS volumes	false
HTTP_PROXY	Address of HTTP proxy server to gain access to API endpoint

Version
Please paste the output of rexray version. For example:
docker.io/rexray/ebs:latest

Unfortunately this isn't an option currently with the plugin. The following file configures the settings that are available to be set as a managed plugin. If there are missing env variables, they can be added and the plugin can be built and used. Can you give this a try and see if it satisfies your needs?
https://github.com/rexray/rexray/blob/master/.docker/plugins/ebs/config.json


Overflow bug when running tf.raw_ops.Tile on colab

Issue type
Bug
Have you reproduced the bug with TensorFlow Nightly?
Yes
Source
binary
TensorFlow version
2.13.0
Custom code
Yes
OS platform and distribution
No response
Mobile device
No response
Python version
No response
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
Due to large list elements
Standalone code to reproduce the issue
import tensorflow as tf
import os
import numpy as np
try:
  input_tensor = tf.random.uniform([4, 1, 1, 20], dtype=tf.float32)
  input = tf.identity(input_tensor)
  multiples_0 =<PHONE_NUMBER>51
  multiples_1 = True
  multiples_2 =<PHONE_NUMBER>51
  multiples_3 =<PHONE_NUMBER>51
  multiples = [multiples_0,multiples_1,multiples_2,multiples_3,]
  name = None
  out = tf.raw_ops.Tile(input=input,multiples=multiples,name=name,)
except Exception as e:
  print("Error:"+str(e))

### Relevant log output

```shell
Error:{{function_node __wrapped__Tile_device_/job:localhost/replica:0/task:0/device:CPU:0}} Encountered overflow when multiplying<PHONE_NUMBER>04 with<PHONE_NUMBER>51, result: -1 [Op:Tile]

Not an issue, that's an error that is being returned to the user instead of performing bad computations.
Please consult again the SECURITY.md guide, please don't spam with low quality issues.


archive succeeded but cannot continue????

New Issue Checklist

[✅] Updated fastlane to the latest version
[✅ ] I read the Contribution Guidelines
[✅ ] I read docs.fastlane.tools
[✅ ] I searched for existing GitHub issues

Issue Description

▸ Archive Succeeded
[14:46:45]: Exit status: 1
+---------------+-------------------------+
|            Build environment            |
+---------------+-------------------------+
| xcode_path    | /Applications/Xcode.app |
| gym_version   | 2.154.0                 |
| export_method | app-store               |
| sdk           | iPhoneOS13.2.sdk        |
+---------------+-------------------------+
[14:46:45]: ▸ warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 7.0, but the range of supported deployment target versions is 8.0 to 13.2.99. (in target 'FBRetainCycleDetector' from project 'Pods')
[14:46:45]: ▸ warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 6.0, but the range of supported deployment target versions is 8.0 to 13.2.99. (in target 'JSONModel' from project 'Pods')
[14:46:45]: ▸ warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 6.1, but the range of supported deployment target versions is 8.0 to 13.2.99. (in target 'MQTTClient' from project 'Pods')
[14:46:45]: ▸ warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 7.0, but the range of supported deployment target versions is 8.0 to 13.2.99. (in target 'Protobuf' from project 'Pods')
[14:46:45]: ▸ warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 7.0, but the range of supported deployment target versions is 8.0 to 13.2.99. (in target 'Number' from project 'Pods')
[14:46:45]:
[14:46:45]: ⬆  Check out the few lines of raw xcodebuild output above for potential hints on how to solve this error
[14:46:45]: 📋  For the complete and more detailed error log, check the full log at:
[14:46:45]: 📋  /Users/ios_package/Library/Logs/gym/StockGlobal-StockGlobal.log
[14:46:45]:
[14:46:45]: Looks like fastlane ran into a build/archive error with your project
[14:46:45]: It's hard to tell what's causing the error, so we wrote some guides on how
[14:46:45]: to troubleshoot build and signing issues: https://docs.fastlane.tools/codesigning/getting-started/
[14:46:45]: Before submitting an issue on GitHub, please follow the guide above and make
[14:46:45]: sure your project is set up correctly.
[14:46:45]: fastlane uses xcodebuild commands to generate your binary, you can see the
[14:46:45]: the full commands printed out in yellow in the above log.
[14:46:45]: Make sure to inspect the output above, as usually you'll find more error information there
[14:46:45]:
+-----------------------------------+-----------------------------------------------------------+
|                                         Lane Context                                          |
+-----------------------------------+-----------------------------------------------------------+
| DEFAULT_PLATFORM                  | ios                                                       |
| PLATFORM_NAME                     | ios                                                       |
| LANE_NAME                         | ios iosAppStore                                           |
| GET_INFO_PLIST_VALUE_CUSTOM_VALUE |                                                           |
| VERSION_NUMBER                    | 1.21.0                                                    |
| SIGH_PROFILE_PATH                 | /Users/ios_package/.jenkins/jobs/StockGlobal_Release/wor  |
|                                   | kspace/AppStore_com.itradeup.ustradeup.mobileprovision    |
| SIGH_PROFILE_PATHS                | ["/Users/ios_package/.jenkins/jobs/StockGlobal_Release/w  |
|                                   | orkspace/AppStore_com.itradeup.ustradeup.mobileprovision  |
|                                   | "]                                                        |
| SIGH_UDID                         | cd6bd836-2b88-4cd0-9e6c-1b5be6abec49                      |
| SIGH_UUID                         | cd6bd836-2b88-4cd0-9e6c-1b5be6abec49                      |
| SIGH_NAME                         | TradeUP US Release                                        |
| SIGH_PROFILE_TYPE                 | app-store                                                 |
+-----------------------------------+-----------------------------------------------------------+
[14:46:45]: Error building the application - see the log above
+------+----------------------------+-------------+
|                fastlane summary                 |
+------+----------------------------+-------------+
| Step | Action                     | Time (in s) |
+------+----------------------------+-------------+
| 1    | default_platform           | 0           |
| 2    | xcode_select               | 0           |
| 3    | get_info_plist_value       | 0           |
| 4    | get_info_plist_value       | 0           |
| 5    | set_info_plist_value       | 0           |
| 6    | Switch to ios package lane | 0           |
| 7    | cocoapods                  | 23          |
| 8    | get_version_number         | 0           |
| 9    | get_info_plist_value       | 0           |
| 10   | sigh                       | 11          |
| 💥   | gym                        | 572         |
+------+----------------------------+-------------+
[14:46:45]: fastlane finished with errors
[!] Error building the application - see the log above
Command executed

Complete output when running fastlane, including the stack trace and command used

 [REPLACE THIS WITH YOUR INFORMATION]

Environment

 [REPLACE THIS WITH YOUR INFORMATION]

✅ fastlane environment ✅
Stack

Key
Value

OS
10.14.6

Ruby
2.7.1

Bundler?
false

Git
git version 2.21.0 (Apple Git-122.2)

Installation Source
/usr/local/Cellar/fastlane/2.154.0/libexec/bin/fastlane

Host
Mac OS X 10.14.6 (18G95)

Ruby Lib Dir
/usr/local/Cellar/ruby/2.7.1_2/lib

OpenSSL Version
OpenSSL 1.1.1f  31 Mar 2020

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
11.2.1

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE
en_US.UTF-8
✅

fastlane files:
`./fastlane/Fastfile`
# This file contains the fastlane.tools configuration
# You can find the documentation at https://docs.fastlane.tools
#
# For a list of all available actions, check out
#
#     https://docs.fastlane.tools/actions
#
# For a list of all available plugins, check out
#
#     https://docs.fastlane.tools/plugins/available-plugins
#

default_platform(:ios)

APP_NAME = "trade up"
WORKSPACE = "StockGlobal.xcworkspace"
SCHEME = "StockGlobal"
IPA_TIME = Time.now.strftime("%Y%m%d_%H%M")
OUTPUT_DIRECTORY = "packages"
APP_INFO_PLIST_PATH = './Stock/Info.plist'
ENV_PREFIX=""
IPA_NAME = "StockGlobal_new.ipa"
CHANGE_LOG="自动打包"

#build ENV
ENV["FASTLANE_XCODEBUILD_SETTINGS_TIMEOUT"] = "180"
ENV["FASTLANE_XCODE_LIST_TIMEOUT"] = "180"

platform :ios do
  #
  before_all do |lane, options|
       xcode_select "/Applications/Xcode.app"
       FASTLANE_XCODEBUILD_SETTINGS_TIMEOUT = "40"
       CHANGE_LOG=options[:changeLog]
  end

  # #debug包
  # lane :iosDebug do
  #   ENV_PREFIX="debug_"
  #   EXPORT_METHOD = "development"
  #   package(configuration: "Debug")
  # end

  #发布包
  lane :iosAppStore do
    ENV_PREFIX="appstore_"
    EXPORT_METHOD = "app-store"

  PLIST_BUILD_VERSION = get_info_plist_value(path: "#{APP_INFO_PLIST_PATH}", key: 'CFBundleVersion')

  shortVersionString = get_info_plist_value(
    path: APP_INFO_PLIST_PATH,
    key: "CFBundleShortVersionString"
  )

  job_number = ENV['BUILD_NUMBER']

  set_info_plist_value(
    key: 'CFBundleVersion',
    value: job_number.to_s,
    path: APP_INFO_PLIST_PATH
  )

  package(configuration: "Release")
  upload_to_app_store(force: true)
  # upload_to_testflight(skip_submission: true) # to only upload the build
  end

  lane :packTestflight do
    ENV_PREFIX="debug_"
    EXPORT_METHOD = "development"
    package(configuration: "Debug")
    upload_to_testflight(force: true)
  end

  #打包函数
  lane :package do |option|
      cocoapods(use_bundle_exec: false)

      PLIST_INFO_VERSION = get_version_number(target: "#{SCHEME}")
      PLIST_BUILD_VERSION = get_info_plist_value(path: "#{APP_INFO_PLIST_PATH}", key: 'CFBundleVersion')
      IPA_NAME = "#{IPA_TIME}_" + "#{ENV_PREFIX}" + "#{APP_NAME}_"  + "#{PLIST_INFO_VERSION}" + ".ipa"

    sigh(
      username<EMAIL_ADDRESS>      app_identifier: 'com.itradeup.ustradeup',
      force: true,
      provisioning_name: 'TradeUP US Release',
      ignore_profiles_with_different_name: true,
    )

     #打包
     gym(
      scheme: "#{SCHEME}",
      export_method: "#{EXPORT_METHOD}",
      configuration: option[:configuration],
      output_directory: "#{OUTPUT_DIRECTORY}",
      include_symbols: true,
      include_bitcode: false,
      xcargs: 'DEBUG_INFORMATION_FORMAT="dwarf-with-dsym"',
      output_name: "#{IPA_NAME}",
      export_xcargs: "-allowProvisioningUpdates"
      )

      xcclean(
       workspace: "#{WORKSPACE}",
       scheme: "#{SCHEME}"
      )
  end

end

`./fastlane/Appfile`
app_identifier("com.itradeup.ustradeup") # The bundle identifier of your app
<EMAIL_ADDRESS># Your Apple email address

team_id("JWL23C692U") # Developer Portal Team ID

# For more information about the Appfile, see:
#     https://docs.fastlane.tools/advanced/#appfile

fastlane gems

Gem
Version
Update-Status

fastlane
2.154.0
💥 Check failed

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.4.0

slack-notifier
2.3.2

atomos
0.1.3

CFPropertyList
3.0.2

claide
1.0.3

colored2
3.1.2

nanaimo
0.3.0

xcodeproj
1.17.1

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
2.0.0

unicode-display_width
1.7.0

terminal-table
1.8.0

plist
3.5.0

public_suffix
4.0.5

addressable
2.7.0

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.8.1

tty-cursor
0.7.1

tty-spinner
0.9.3

babosa
1.0.3

colored
1.2

highline
1.7.10

commander-fastlane
4.4.6

excon
0.76.0

faraday
1.0.1

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

faraday_middleware
1.0.0

fastimage
2.2.0

gh_inspector
1.1.3

json
2.3.0

mini_magick
4.10.1

rubyzip
2.3.0

security
0.1.3

xcpretty-travis-formatter
1.0.0

dotenv
2.7.6

bundler
2.1.2

naturally
2.2.0

simctl
1.6.8

jwt
2.2.1

uber
0.1.0

declarative
0.0.20

declarative-option
0.1.0

representable
3.0.4

retriable
3.1.2

mini_mime
1.0.2

multi_json
1.15.0

signet
0.14.0

memoist
0.16.2

os
1.1.0

googleauth
0.13.1

httpclient
2.8.3

google-api-client
0.38.0

google-cloud-env
1.3.3

google-cloud-errors
1.0.1

google-cloud-core
1.5.0

rake
13.0.1

digest-crc
0.6.1

google-cloud-storage
1.27.0

emoji_regex
3.0.0

jmespath
1.4.0

aws-partitions
1.348.0

aws-eventstream
1.1.0

aws-sigv4
1.2.1

aws-sdk-core
3.104.3

aws-sdk-kms
1.36.0

aws-sdk-s3
1.75.0

uri
0.10.0

forwardable
1.3.1

logger
1.4.2

cgi
0.1.0

timeout
0.1.0

stringio
0.1.0

ipaddr
1.2.2

openssl
2.1.2

ostruct
0.2.0

strscan
1.0.3

date
3.0.0

delegate
0.1.0

fileutils
1.4.1

io-console
0.5.6

zlib
1.1.0

singleton
0.1.0

rexml
3.2.3

open3
0.1.0

yaml
0.1.0

psych
3.1.0

mutex_m
0.1.0

webrick
1.6.0

generated on: 2020-08-07

fix


Utilities.scss - generating 'state' definitions like hover/focus also generates stateless output.

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
There seems to be an issue with the utility API that generates 'state' classes
https://github.com/twbs/bootstrap/pull/31643
The hover/focus state generates fine, but also comes along with the stateless definition like so:
.something {}   // <-- this shouldn't be there according to docs
.something:hover{}
.something:focus{}

The additional definition renders the utility useless when trying to set something like a colour change on hover.
I'm running 5.2 but I've tried other 5.x versions in case it was a recent glitch.
Docs under "States" indicate that the above definition should only produce the :hover output.
https://getbootstrap.com/docs/5.2/utilities/api/
Reduced test cases
In utilities.scss:
$utilities: (
	"hover-bg": (
		property: background-color,
		class: hover-bg,
		state: hover,
		values: $colors,
	)
);

This will generate the correct output for the :hover state but also generates duplicate output for the non-hover(?) state, rendering it useless.
Output CSS:
.hover-bg-blue {
  background-color: #00539b !important;
}

.hover-bg-blue-hover:hover {
  background-color: #00539b !important;
}

What operating system(s) are you seeing the problem on?
macOS
What browser(s) are you seeing the problem on?
Chrome
What version of Bootstrap are you using?
5.2, 5.1.3

This is unclear in the docs Indeed, but you're seeing the intended behaviour: state and other properties in the Utilities API are meant to extend utilities, without the need to add specific  entries for states, responsive variants, RTL conditions, etc.
To get hover state on background-color, you only need to extend existing .bg-* utitilies with the state property. Would this work for you?
I think the docs need some clarifications regarding properties and how to use them.

That makes sense. That would probably work for me. My use case was setting different hover colours (bg/text) for buttons.
For example, something like:
btn bg-yellow bg-hover-red text-black text-hover-white
How does one extend the bg-utilities as you suggest? The docs show how to declare a new util but I'm not clear on how to add 'state' to an existing one. Would you just redeclare the whole shebang? I'm feeding it my colours array rather than the "theme colours".

@oobi I let you confirm if it would work for you. In the meantime, I'm adding "docs" and "enhancement" labels to this issue so that we try to add some clarifications regarding properties and how to use them.

The docs explain how to extend a utility to enable responsable variants. Adding states is the same, using the state property.

Thanks so much - this worked perfectly. It took me a few tries to find exactly where to import this, but if you're hitting the docs at some stage, it may be worth mentioning that the custom utils need be imported after _utilities.scss and before bootstrap.scss.
// custom variables
@import "variables";

@import "~bootstrap/scss/functions";
@import "~bootstrap/scss/variables";
@import "~bootstrap/scss/mixins";
@import "~bootstrap/scss/utilities";

// custom utilities (must be declared before bootstrap and after BS utilities)
@import "utilities";

@import "~bootstrap/scss/bootstrap";

In case this helps some future reader (most likely me when I forget next time), here's the snippet to add hover states to background colours and text colours (bg-primary-hover, text-primary-hover)
$utilities: map-merge(
    $utilities,
    (
        // extend existing bg/text classes for hover state
        "background-color":
            map-merge(
                map-get($utilities, "background-color"),
                (
                    state: hover,
                )
            ),
        "color":
            map-merge(
                map-get($utilities, "color"),
                (
                    state: hover,
                )
            ),
    )
);

You might have had issues because you use both exclusive approaches to include Bootstrap Sass files. Based on our Cutomize > Sass docs, it's either @import "~bootstrap/scss/bootstrap"; ("Include all of Bootstrap"), either including parts of Bootstrap.
I haven't tried in details your use case so maybe it's useful here but it sounded strange to me when I read your last comment.
But this is cool if you succeeded to make it work! Neat!

Echoing Julien's comments and closing out. I could see us maybe revisiting the states options to provide a default that could be optional in some way, such that you could remove the initial non-pseudo element states. Tagging for v6 to consider.


Rename serve_directly to experimental_serve_directly

Fixes #0000

Tests

[ ] TODO (before merge)
[X] Tests included
[ ] Tests not necessary because:

E2E Tests CI Job required? (Use "e2e" label or ask maintainer to run separately)

[ ] I don't know
[ ] Required
[X] Not required because: n/a

Public documentation

[ ] TODO (before merge)
[ ] Cloudflare docs PR(s):
[X] Documentation not necessary because: n/a

Updated the previous changeset associated with serve_directly. No new changeset required.


Bean 'com.example.demo.Client' of type [org.springframework.cloud.openfeign.FeignClientFactoryBean] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)

Describe the bug
we have a lot of FeignClients in our application which are triggering a lot of INFO log messages regarding the problem then the clients are not eligible for being processed by all bean post-processors. these messages indicate that something is going wrong but not exactly what is the problem.
as this message is triggered by the core springframework it would be nice that the feign clients can be created in such a way that they are not triggering the information log message.
Sample
sample project: https://github.com/BigMichi1/openfeign-warning
the problem is when @EnableAsync annotation is added then the info message is triggered, if it is removed then no message is shown

a similiar issue was reported already in #361 but when I debugged it this was not true anymore that a null was returned

Hi, @BigMichi1 if I understand your comment correctly, the only issue here is that a warning or info log appears?

@OlgaMaciaszek as far as i can tell yes it might be the "only" issue that a message is displayed tellingme that something is fishy even if it is not. But i have a feeling that there might be something else that has an influence on the functionallity of the created clients. this is the thing i do not know. i have only seen during debugging that 8 out of 12 postprocessors were called for the created client bean and 4 were just skipped. Do they have an impact on the client bean, i can not tell for sure as during mytesting it "seems" that everything works.
What the most confuses me and other devs inmy project is that no message is shown until someone adds an '@EnableAsync' annotation to one configuration and then the log file is full of these messages during the startup.

@BigMichi1 Thanks for the answer.  These warnings are a known issue, but since we have not observed that the behaviour is hindered in any way, it has a very low priority, and we will not be working on it at this time.

looks like this behaviour has been fixed now in spring-framework 5.3.14 with https://github.com/spring-projects/spring-framework/issues/27808


Please publish yoga-layout on Maven Central

Report

[x] I have searched existing issues and this is not a duplicate

https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/
JCenter will be unavailable on May 1, 2021.
But it seems yoga-layout is available on JCenter only.
https://mvnrepository.com/artifact/com.facebook.yoga.android/yoga-layout?repo=jcenter

React Native depends on com.facebook.yoga:proguard-annotations which is also available on JCenter only.
It means we can't build any project that uses React Native after May 1, 2021.

Yes please. As of posting this, jcenter is down due to some technical issues and I'm unable to get this dependency.

This is really important and just shows how brittle external dependencies really are.
Can we work with offline caches easily or create our own artifact respository clone?

This is really important and just shows how brittle external dependencies really are.
Can we work with offline caches easily or create our own artifact respository clone?

I'm honestly surprised the build process didn't use any offline cache. I had compiled this project many times before on MacOS and WSL2. When jcenter went down, both would not compile.

You can force gradle to prefer offline or go offline only, it's a command line flag.
That said this is a vital change.

Note that:

jitpack.io is not even able to find tag 1.14.1 (the react-native dependency for the 0.64.0 release) because it was apparently never tagged here so it obviously can't build it
jitpack.io did try to build some recent ones plus I just triggered a build of 1.14.0 and they all fail with this:

{"cookie":"","inReplyTo":"configure","message":"CMake Error: CMake was unable to find a build program corresponding to "Ninja".  CMAKE_MAKE_PROGRAM is not set.  You probably need to select a different build tool.","title":"Error","type":"message"}

Which looks like this failure to set the CMAKE program more or less (yes, windows paths, but probably adaptable): https://stackoverflow.com/a/64917390/9910298
This project appears to be a transitive dependency of react-native via flipper as well, so it is critical this is updated soon as multiple projects needs updated releases I think before jcenter can be purged

Here's a work-around for the time being:
I also got bit by the proguard-annotations artifact (as the indirect dep through react native), personally, but this should work for yoga-layout as well.
In any case, I don't like to wait for the last minute, and also - we're all expecting another prescheduled brown-out downtime next week (April 26th) by Bintray. So here's what I moved forward with:

Directly download (TODAY) the missing artifact from Bintray. For example, for proguard-annotations version 1.14.1, browse your way to the .jar file in https://bintray.com/facebook/maven/com.facebook.yoga%3Aproguard-annotations/1.14.1#files.
Place the .jar in your project's android/libs (yes, it should be commited+pushed to Github until this is fixed).
In your root build.gradle, apply this repo definition:

allprojects {
    repositories {
        google()
        mavenLocal()
        mavenCentral()
        // ...
+        flatDir {
+            dirs "$rootProject.projectDir/libs"
+        }
    }
}
(Add `allproject` entirely, if it's missing in your project)

Replace the standard react native dep in your app/build.gradle like so:

dependencies {
-    implementation 'com.facebook.react:react-native:+'
+    implementation 'com.facebook.fbjni:fbjni-java-only:0.0.4'
+    implementation('com.facebook.react:react-native:+') {
+        exclude group: 'com.facebook.fbjni', module: 'fbjni-java-only'
+        exclude group: 'com.facebook.yoga', module: 'proguard-annotations'
+    }
}

@d4vidi that's an interesting approach, you are on to something there. This is a potential start towards something automated for people that can't update.
Examine this if you have time: https://github.com/ankidroid/Anki-Android/blob/master/AnkiDroid/robolectricDownloader.gradle - the idea is to pre-download maven artifacts you'll need later
I wrote that in order to have external dependency downloaded de-flaked in an E2E CI type pipeline where the downloads were failing builds and giving me a fail signal outside of my code changes. With that and an exponential-back-off-retry I have great signal to noise.
But - if the general idea of "you can have a gradle task that downloads dependencies before your real build" is combined with the idea of "react-native jcenter dependencies may be downloaded"...
1- store the problematic in-use artifacts on the official react-native github somewhere (or on their respective project pages) as downloadable things - have a known list of them, I think there are only a handful (yoga android-annotations, 2 flipper plugins, fbjni)
2- write a downloader script for them like the above
3- integrate that in to patch releases of RN CLI?
It could be just as terrible + functional as https://github.com/mikehardy/jetifier :-), which is and was kind of gross but also just glossed over the whole AndroidX migration for everyone at once and made it go away...

If done well it requires no external approval or waiting actually - a repo could simply get them now even if it wouldn't be officially blessed, write the task and throw them in the local ~/.m2 and integration of the package is to add an apply ... statement in your build script (something semi-normal for packages to ask) and make sure mavenLocal is in your repo list in build.gradle, so as a proof-of-concept it could be demonstrated prior to involving the official repos (so the artifacts are more official) or the RN CLI (so the task is included / default-on like jetifier for everyone)

@mikehardy That could actually make a really cool solution. Perhaps we could even publish it as a Gradle plugin - I wonder.

Just a quick note here: JCenter is on record as saying they will leave the repo up in read-only mode, so this is not urgent any longer
However it is important (despite not being urgent) to have ability to publish somewhere/anywhere else, so I believe the issue is still valid
Cheers

I know there's an update that JCenter will be kept as a read-only repository indefinitely but yoga-layout is failing with a 403 on JCenter but works on maven.

As of Monday (5th July 2021) I've been getting this issue, and it seems I've missed the boat in terms of grabbing the artefact from Bintray so feel like I'm a bit stuck. I'm not really an Android dev and use Yoga through React Native.
`Could not resolve all task dependencies for configuration ':app:releaseCompileClasspath'.

Could not find com.facebook.yoga:proguard-annotations:1.14.1.
Required by:
project :app > com.facebook.react:react-native:0.63.2
Could not find com.facebook.fbjni:fbjni-java-only:0.0.3.
Required by:
project :app > com.facebook.react:react-native:0.63.2`

Full build scan is here: https://scans.gradle.com/s/lyge6fz762tsu/

@PhilipBrew So for now you just need the jcenter maven repository and it should work?
https://github.com/facebook/react-native/blob/757bb75fbf837714725d7b2af62149e8e2a7ee51/template/android/build.gradle#L13
I'm still building successfully at least
Appears that react-native 0.65 when it's released will have evicted jcenter completely based on the template alterations visible on that branch https://github.com/facebook/react-native/commit/9a923be8979ddd7da5ea3dc68232a7c36aa0380d

@mikehardy Yeah I think so long as I can grab the .jar file I will be able to do @d4vidi workaround above. I then anticipate some of the other packages I'm using to throw the same issues however.
I'm really unsure why I'm suddenly unable to build Android but the wider community as a whole seem to be fine, at least for now. Apologies if we should be having this conversation somewhere else, but it feels like I'm missing something when a base create-react-native-app does indeed build

It seems like yoga-layout is actually on Maven Central:
https://search.maven.org/artifact/com.facebook.yoga.android/yoga-layout/1.19.0/aar
Is there anything left to be done here then?

com.facebook.yoga:proguard-annotations still not published to Maven Central

com.facebook.yoga:proguard-annotations still not published to Maven Central

It seems like it is https://search.maven.org/artifact/com.facebook.yoga/proguard-annotations/1.19.0/jar

Oops, somehow I was unable to find it...
Indeed, It looks like the issue is resolved.

https://search.maven.org/artifact/com.facebook.yoga/proguard-annotations/1.19.0/jar

Our project needs com.facebook.yoga:proguard-annotations:1.14.1 which is still absent on Maven Central

Our project needs com.facebook.yoga:proguard-annotations:1.14.1 which is still absent on Maven Central

Out of curiosity: why can't you update to the latest version?

maybe this help: it looks like to be on 1.19 you need to be using RN65 - RN64 is still on 1.14: https://github.com/facebook/react-native/blob/0.64-stable/ReactAndroid/build.gradle

@cortinico @kelset You are right, guys. This is my fault. Since we moved to RN 0.65, 1.14 is not needed anymore. Didn't see it myself. Thanks! :-)

Our project needs com.facebook.yoga:proguard-annotations:1.14.1 which is still absent on Maven Central

Just a heads up: com.facebook.yoga:proguard-annotations:1.14.1 has now been republished to MavenCentral so users on RN 0.64.x would be able to build while fetching this artifact from mavenCentral() rather than jcenter() in case of an outage:
https://repo1.maven.org/maven2/com/facebook/yoga/proguard-annotations/1.14.1/

It looks like @cortinico has taken care of this. Please let me know if there is anything still pending on this issue.


[Feature] when deleting image from gallery view: stay in zoomed-mode when deleting from zoomed-mode

Hi there, it is me again ;)
Currently I have a large number of images in my gallery and to be able to decide which of the "experiments" are good enough to keep, I browse through the images while being in zoomed-mode (i.e. seeing a single picture at a time).
When deleting a picture in that mode, the mode is cancelled after deletion and the gallery view returns to the gallery list mode.
Would it be possible to stay in zoomed mode and show the previous or next picture in zoomed mode instead?
Depending on what is easier to implement both would be fine for me, but probably both is on the same level of difficulty, because when deleting the first or last image of the gallery you have to go in one or the other direction dynamically anyway ;)
Having that feature would drastically speed up the clean-up of my gallery :)
Thanks a lot for reading and considering 👍
Kind regards
LZ

Thank you for suggesting this. I think this way would work much better. I’ll add it to the feature list.
I’m currently deep into a refactor to handle some API updates but I will tackle that in the near future.

sounds great, thanks a lot :)


Add "pgAdmin" to local dev environment

Add "pgAdmin" to local dev env.
Makes it possible to have an insight into the data of MIW.

Done


Update docker.md

What is the purpose of the change
(For example: This pull request makes task deployment go through the blob server, rather than through RPC. That way we avoid re-transferring them on each deployment (during recovery).)
Brief change log
(for example:)

The TaskInfo is stored in the blob store on job creation time as a persistent artifact
Deployments RPC transmits only the blob storage reference
TaskManagers retrieve the TaskInfo from the blob cache

Verifying this change
Please make sure both new and modified tests in this PR follows the conventions defined in our code quality guide: https://flink.apache.org/contributing/code-style-and-quality-common.html#testing
(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (100MB)
Extended integration test for recovery after master (JobManager) failure
Added test that validates that TaskInfo is transferred only once across recoveries
Manually verified the change by running a 4 node cluster with 2 JobManagers and 4 TaskManagers, a stateful streaming program, and killing one JobManager and two TaskManagers during the execution, verifying that recovery happens correctly.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@mattfysh Thanks for the PR but please take the code contribution guide into account https://flink.apache.org/contributing/contribute-code.html
I can't see why it's important to add this; Flink also works without add, so why is it needed?

Hi @MartijnVisser - my apologies, I am short on time and hoped someone with PyFlink familiarity would pick this up and immediately identify why this change is required.
The current instructions do not work in Docker, which means they won't work on anyone's machine regardless of host setup
To reproduce, stand up a local cluster in session mode using the following steps:

Create a new folder

Create a Dockerfile inside the folder with the contents of "Using Flink Python on Docker": https://nightlies.apache.org/flink/flink-docs-release-1.16/docs/deployment/resource-providers/standalone/docker/#using-flink-python-on-docker

Create a docker-compose.yaml file with the contents of "Session Mode": https://nightlies.apache.org/flink/flink-docs-release-1.16/docs/deployment/resource-providers/standalone/docker/#session-cluster-yml

Change both instances of image: flink:1.16.0-scala_2.12 to be build: .

Add a volumes entry to the jobmanager as:
 volumes:
     - .:/input

Create a word_count.py file with the contents of "The complete code so far" section https://nightlies.apache.org/flink/flink-docs-release-1.16/docs/dev/python/table_api_tutorial/

Run docker-compose up

Enter the jobmanager via docker exec -it [job_manager_container_id] bash

Run ./bin/flink run --python /input/word_count.py

This does not work, and throws the following error:
Caused by: java.lang.RuntimeException: Failed to create stage bundle factory! Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/fastavro/read.py", line 2, in <module>
    from . import _read
  File "fastavro/_read.pyx", line 11, in init fastavro._read
  File "/usr/local/lib/python3.7/lzma.py", line 27, in <module>
    from _lzma import *
ModuleNotFoundError: No module named '_lzma

This is occurring because when building Python from source, as instructed in the Flink documentation I have updated, certain "optional modules" in Python are not built if host dependencies could not be found. This includes things like readline, sqlite, etc, but also lzma - more information can be found at https://devguide.python.org/getting-started/setup-building/#unix particularly the "optional modules were not found" message
From what I gather, the latest version of PyFlink uses a version of fastavro that requires lzma to be present in the Python build. I assume the instructions I have updated used to work with older version of PyFlink.

Flink also works without add, so why is it needed?

Did you test on v1.16?

Did you test on v1.16?

@dianfu @HuangXingBo I'm assuming we've done that, but you're the Python experts :)

Is there a desire within the Flink team to ensure that PyFlink achieves similar uptake and robustness as PySpark?

Is there a desire within the Flink team to ensure that PyFlink achieves similar uptake and robustness as PySpark?

I think any open source community strives to improve their product :)
Let me ping the maintainers on this PR once more

Sorry for late response. I have missed this PR. The PR LGTM and I guess it should be caused by the bump of fastavro version which is introduced in https://issues.apache.org/jira/browse/FLINK-27058.


[API Store][API Publisher]When the user account is locked, provide a suitable error message other than saying the provided credentials are invalid.

Description:
Once a user account is locked, the error message displayed in the UI is 'Error! Login failed. Please recheck the username and password and try again' which may mislead the user. In the carbon log, it displays as below.
[2018-09-28 10:49:19,184]  WARN - IdentityMgtEventListener User account is locked for user : uyanage. cannot login until the account is unlocked
[2018-09-28 10:49:19,185] ERROR - AuthenticationAdmin System error while Authenticating/Authorizing User : 17003 User account is locked for user : uyanage. cannot login until the account is unlocked

It would increase the usability if we propagate the same message to the user or a suitable general message such as 'Your account is locked' at the time the user account gets locked and the user is unable to login.
Suggested Labels:
Type/New Feature
Severity/Major
Priority/High
Affected/2.5.0
Affected Product Version:
2.5.0
Steps to reproduce:

Setup account locking as in [1]
Create a user, user1.
Try to login to API Store with invalid credentials for user1. Do three attempts.
In the 4th attempt, provide correct credentials.

Still, you get the error message as below which misleads user since the user has provided the correct credentials but actually the account is locked.

[1] - https://docs.wso2.com/display/AM250/Identity+Management+for+the+API+Store#IdentityManagementfortheAPIStore-Accountlockingbyfailedloginattempts

Thanks, do we have ETA on this feature request? please let me know if it is available via wum update. thanks.

In-order to invoke the login flow, we use the  stub [1] of AuthenticationAdmin service [2] provided by carbon kernel. And the functionality provided by kernel only returns a boolean indicating whether the login is successful or not. It doesn't return any other info as invalid credentials, account locked, disabled etc.
Changing the admin service method to return this information will cause an api change and will break other components using the same admin service.
If we are to implement this, it will be a drastic change to number of components.
If one needs this information, a workaround would be to enable sso for the store application and enable the setting described at [3] so that IDP component will send the required information to the application side.
On a side note, if the account is locked after defined failed attempts, it is a security vulnerability to provide the message that account is locked once the user provides the correct credentials. Because a malicious use can do a brute force attack and identify the correct password once he gets the account locked message.
Ideally expected scenario would be to show the "account locked" message for all different combinations of username and password ( either correct credentials or not) after defined number of failed attempts.
[1] https://github.com/wso2/carbon-apimgt/blob/6.x/components/apimgt/org.wso2.carbon.apimgt.hostobjects/src/main/java/org/wso2/carbon/apimgt/hostobjects/APIStoreHostObject.java#L681
[2] https://github.com/wso2/carbon-kernel/blob/4.4.x/core/org.wso2.carbon.core.services/src/main/java/org/wso2/carbon/core/services/authentication/AuthenticationAdmin.java#L61
[3] https://docs.wso2.com/display/IS550/Customizing+Authentication+Error+Messages


XDebug shouldn't be enabled by default due to performance

Thanks Janne from kehittämö for finding out this bug

This is bug report is invalid.
First of all this WP Vagrant image is only for development, there is no need to optimize performance here. Secondly XDebug is installed yes, but is only does profiling when get parameter XDEBUG_PROFILE=1 is present.
The production environment does not have XDebug installed at all, and that is where performance matters.
The feature is documented here: https://docs.wp-palvelu.fi/development/xdebug/
The documentation however could be extended and the RADME.md in this repo should advertise the existence of dosc.wp-palvelu.fi

This is a verified performance issue.
Tested with a real multisite installation, disabling the plugin gave a significant performance improvement from 1-3 seconds per page to around 200ms.

How slow is it then when you run the actual profiling with ?XDEBUG_PROFILE=1
Xdebug also does other things, like provide extended error messages and stack traces.
Disabling Xdebug from everybody's development environment because it slows down somebody's development environment in isolated cases would be a huge trade-off.

Just ran some tests on the kehittamo box front page php.
xdebug.ini disabled
avg: 0.531s
xdebug ini enabled, no ?XDEBUG_PROFILE
avg: 1.546
xdebug ini enabled, with ?XDEBUG_PROFILE
avg: 2.793

If it's on by default it lowers the barriers to use it. The box could have option to disable it in config.yml. Or it could have another php backend (possibly hhvm) which doesn't have any debug options.
Ofc it's annoying if it's that slow, but I wouldn't change the default setting to be something else than the current one.

It's not just annoying, on slower machines the current situation is almost unbearable.
I would suggest a small script in vagrantfile to either enable or disable xdebug via a config.yml option. The default can be on, but it needs to be documented that it may slow down your dev site.
wp-vagrant box seems to be suffering from other performance issues on some machines as well. might have something to do with virtualbox...

Installation dialog / documentation / config option seems to be the correct way to approach this.
Vagrant is anyway slow because it is a Virtual Box virtual machine, it accesses the files via weird mounts etc.. Vagrant version 2 can support also Docker as a provider, that would be much faster at least on all Linux machines: https://www.vagrantup.com/docs/docker/

@anttiviljami What would your benchmark show if the debugger was shut off by disabling line https://github.com/Seravo/wp-vagrant/blob/master/roles/xdebug/templates/20-xdebug.ini.j2#L26 ?
Maybe the performance hit is caused by the debugger being active? Most people don't use the debugger. If having it running is the fault, then I'd be OK by making it off by default, but easy to enable (the config is already there, user just need to make one switch). The rest of xdebug could be kept enabled.

checking now..

With xdebug.default_enable = 0 average front page load is 1.532s. Sadly, that's not a significant improvement.

Tried fiddling around with all the xdebug conf options, but nothing seemed to make a real difference. Looks like the only viable option is to have a configuration option. (I would suggest adding a prompt within vagrant up) to ask whether to enable xdebug or not.

Re-opening. Vagrant is still slow and disabling XDebug is one of the biggest single items that decreases Virtualbox I/O.

I think it must be a separate issue. Vagrant works beautifully fast for me right now, even with XDebug enabled. Could you post your system information here? Virtualbox, Vagrant, OS versions?

One solution would be to implement #39 and then run Vagrant with XDebug off by default.

Test from latest seravo/wordpress-beta Vagrant box:
vagrant@vagrant:~$ wp-xdebug-off
...
All versions of PHP restarted!
vagrant@vagrant:~$ wp-speed-test
Testing speed URL https://seravocom.local...

URL                       TOTAL NAMELOOKUP CONNECT APPCONNECT PRETRANSFER STARTTRANSFER    = AVG
...
https://seravocom.local   0.381      0.000   0.000      0.000       0.000         0.381    0.436
https://seravocom.local   0.191      0.000   0.000      0.000       0.000         0.191    0.421
https://seravocom.local   0.294      0.000   0.000      0.000       0.000         0.293    0.413
https://seravocom.local   0.329      0.000   0.000      0.000       0.000         0.329    0.408
https://seravocom.local   0.212      0.000   0.000      0.000       0.000         0.211    0.398
https://seravocom.local   0.195      0.000   0.000      0.000       0.000         0.195    0.388
...

vagrant@vagrant:~$ wp-xdebug-on
...
All versions of PHP restarted!
vagrant@vagrant:~$ wp-speed-test
Testing speed URL https://seravocom.local...

URL                       TOTAL NAMELOOKUP CONNECT APPCONNECT PRETRANSFER STARTTRANSFER    = AVG
...
https://seravocom.local   0.381      0.000   0.000      0.000       0.000         0.381    0.559
https://seravocom.local   0.491      0.000   0.000      0.000       0.000         0.490    0.555
https://seravocom.local   0.397      0.000   0.000      0.000       0.000         0.396    0.546
https://seravocom.local   0.577      0.000   0.000      0.000       0.000         0.576    0.547
https://seravocom.local   0.374      0.000   0.000      0.000       0.000         0.374    0.538
https://seravocom.local   0.386      0.000   0.000      0.000       0.000         0.385    0.531

The overhead of Vagrant is about 200 milliseconds of 2x in this example.

Xdebug off is recommended here in case of slowness: https://seravo.com/docs/development/vagrant-box/#if-you-experience-slowness

https://seravo.com/docs/get-started/release-notes/#vagrant-box-seravowordpress-2019100800

XDebug is disabled by default to improve PHP speed. Run wp-xdebug-on to enable it


[Feature Request] Per-Frame Quantization Control (AVC/HEVC/SVT-AV1 like)

x265 doc
SVT-AV1 doc
Rate control ability to set--quantizer value on per frame basis.
Rav1e reads text file where each line represents quantizer number for the next frame.
--quantizer_file qp.txt
qp.txt:
60
80
90

Behavior if file end first: Repeat last quantizer. Print warning
Behavior if video end first: Print warning to console
I might do it myself if I get familiar with Rust

Thank you! If you need directions please contact us on irc.


[Bug] Bottom sheet has a visual issue at the edge

Hey 👋,
There is a visual error at the edge in the bottom sheet as shown in the picture. You can easily see through it. On the left side it is correct.

Yeah, I am aware of the 'bugs' that the Material3 Modal Bottom Sheet currently has. At this particular moment I can't do anything but to wait for the material3 library to fix these issues. The other solution would be to move the media details to a complete different screen, like Gallery Go does

Hello,
That's right. I hadn't thought of that at all. 😄
Then we just wait for a fix for the library.

Waiting for Material3 Compose library to fix the issue


fix: show biometrics prompt everytime authenticate is invoked for MacOS

Issue: I encountered a behavior where the biometrics prompt appeared only during the initial authentication. Subsequent authentication attempts done shortly after, did not trigger the said prompt. Our specific use case requires the biometrics prompt to be displayed consistently to prevent misuse.
Solution:
Updated the FlutterLocalAuthenticationPlugin.swift and passed context to the respective methods instead of using it globally to persist touchIDAuthenticationAllowableReuseDuration = 0. This ensures that the biometrics prompt is displayed consistently whenever the user attempts to authenticate, regardless of the time elapsed since the previous authentication.

Would you mind testing version 1.0.0 (published and available in main branch)? Thanks very much

@eaceto and @hpelitebook745G2 - I also want this behavior but reading the code and checking the apple docs this looks like a bug with Apple.
According to the Apple docs the default value is 0 which indicates that the authentication should not be re-used however I see a previous authentication being reused even when the value is zero.
The code in this plugin looks good to me.

Given that this is an Apple Bug as far as I can tell I wanted to understand what the cost of creating an LAContext is and ChatGPT had this to say:

Creating an LAContext in macOS (or iOS) is not typically an expensive operation in terms of performance. LAContext is a lightweight object used for interacting with the Local Authentication framework, which includes features like Touch ID and Face ID.

The LAContext object itself does not perform any actual authentication or validation until you make specific requests, such as fingerprint or facial recognition checks. These checks are the operations that can be computationally more expensive, as they involve cryptographic operations and hardware checks to ensure the security of biometric data.

Creating an LAContext is relatively inexpensive because it's mainly an object for managing authentication requests, storing settings, and handling the communication between your app and the system framework. It doesn't perform any intensive tasks during its creation.

The actual cost in terms of time and system resources comes when you call methods like evaluatePolicy(_:localizedReason:reply:) to perform authentication checks, as this is when the system performs the necessary computations and communicates with biometric hardware. These operations can vary in complexity and duration depending on the specific request and the device's capabilities.

So, creating an LAContext should not be a significant performance concern on its own, but it's the actual biometric authentication checks that may have an impact on performance, especially if they are called frequently or if they involve a large amount of data. Therefore, it's essential to use these features judiciously and consider the performance implications when integrating biometric authentication into your macOS application.

So @eaceto if you are adamant that this is not a worthwhile workaround I am happy to maintain a fork with this fix otherwise let's work together to implement a workaround which addresses this problem.

Would you mind testing version 1.0.0 (published and available in main branch)? Thanks very much

hi @eaceto , thanks for the updates!
setTouchIDAuthenticationAllowableReuseDuration(0.0) doesn't seem to work.
is there another way to make the biometrics prompt everytime i want it?


Respond with 404 on non existent route

Mostly just to get rid of the errors in the cloudflare dashboard

That makes total sense! Maybe also wrap router.handle in a try/catch and return a 500 error if it fails?

good call. Added


[LIVE-2722] Stellar sync error instead of 0 balance fallback (#909)

LIVE-2722 Stellar sync error instead of 0 fallback

📝 Description
Network error instead of (scary) fallback to 0 for Stellar balance
❓ Context

Impacted projects: ``
Linked resource(s): ``

✅ Checklist

[x] Test coverage
[x] Atomic delivery
[x] No breaking changes

📸 Demo

🚀 Expectations to reach
Please make sure you follow these Important Steps.
Pull Requests must pass the CI and be internally validated in order to be merged.

Bot running here : https://github.com/LedgerHQ/ledger-live/actions/runs/2883265468


Kpack gs

updated to new kpack install

added dockerhub examples/config

added simple deploy to k8s

added layouts/shortcodes/expand.html so users can expand different configs

@everythingeverywhere Looks like there is some old stuff getting pulled into this too. Maybe we need a new branch for just the kpack update?

@bryanfriedman I think I resolved the conflict that was pulled in, also I had deleted the blog I wrote previously by accident but added it back in just now. I am waiting for the spell checkts etc and will verify the files that are within again

@everythingeverywhere Looks like there is some old stuff getting pulled into this too. Maybe we need a new branch for just the kpack update?

@bryanfriedman I think I resolved the conflict that was pulled in, also I had deleted the blog I wrote previously by accident but added it back in just now. I am waiting for the spell checks etc and will verify the files that are within agai

passing all checks finally I had messed up merge on last blog, headers have been fixed and ready to merge to tanzu-dev-portal

Pretty strange all checks had passed a moment ago.. the broken links reported are http://localhost:1313/developer/ but the ugo serve instance that comes up goes to http://localhost:1313/
PR should be ready to go.

thanks @tybritten !! reverted the file to commit before I stashed the file ready to goooooo


feat: mobile editor toolbar

Some feedback after testing:

Mobile: on a new line, I can still see the "+" menu, it should be disabled
Mobile: try to press enter many times with the keyboard open, you will see that the new line appears under the new mobile menu. It should appear on top so the user can see his writing on the new line.
Desktop: the new breakpoints seems off, now on my 14-inch I see the mobile styles for some part of the editor 🤔
For the technical approach, I am wondering if having a react state value listening the window size and handling the logic based on this value would make the code cleaner. I have the feeling that some things might be better handled that way, for example, the bubble menu is still computed on mobile even tho it's hidden, it would be better to not render the react component at all. Wdyt @gregogun ?

agreed, this feels like a more practical approach to solve the issues mentioned. Will use this instead 👍

Mobile: try to press enter many times with the keyboard open, you will see that the new line appears under the new mobile menu. It should appear on top so the user can see his writing on the new line.

regarding this one, it seems the issue is with the fact that the footer is fixed but we of course need the toolbar to stick on top of the keyboard. One solution I tried was to attach a ref to the EditorContent and detect if the bottom is intersecting with the toolbar position and programmatically scroll, but I didn't manage to get a value returned from the ref.current. Just wondering if you know another way to approach this?


ḟ doesn't overload for functions

The Map over truthy indexes overload for ḟ isn't implemented.

I dunno ... looks implemented to me