Flutter Web profile mode works but release does not

Hi Frank,
while building a project for web in release (--release) mode I noticed that the resulting application can't run and it displays the error below:

If I try to run the application in profile mode everything works as expected,
The really difficult thing is that nothing gets displayed into the console. I had to enable the Chrome debugger to stop the execution on exception. After digging into the code (dart and minified js) i trace back the cause of the exception in the remoteAdapter method of Repository (here) . The problem is related to a minification of the generic type T that, for example, if the type T=Users when minified became T=minified:bs . So when remoteAdapter is called, null is retrieved from the _adapters map because it contains {'users': Instance ...}
I think that's maybe it's something more related to dart2js but maybe you have some advice on how to overcome this weird behavior. I try different ways but none of them seems to work.
Tested on:

Flutter 3.0.5
flutter_data_todos (latest)

I'm sorry to hear this. I always reluctantly supported Flutter web because of things like these.
A kind soul submitted a PR and after a while it brought up several of these toString on null errors that were very difficult to debug and find.
@Skycoder42 by any chance would you happen to know what is causing this error?

Could you find workarounds to turn your profile mode into release?

Okay, so I do kinda now whats going on. When dart is compiled to JS in release mode, there are no guarantees given on how the types are named (kinda as if you would enable obfuscation in standard dart). This is not a bug but standard behaviour. I think the dart documentation even states to not use toString on typenames in JS somewhere (I found a lint: avoid_type_to_string). I do not know if you can disable minification for dart2js, but maybe adding "-O0" will help.
Other than that, the only workaround I can think of is to overwrite the type (and maybe even the internalType) of each repository for every data model and to explicitly specify a sensible type name.
@frank06 Another way to help from the library side could be to add a DataHelper.defineTypeName<T>(String name) to allow developers specify the type name globally in there, overwriting the default name generation - this would also help with reserver type names etc.  As the implementation of getType already uses an internal cache, this would be very easy to implement.

Could you find workarounds to turn your profile mode into release?

Actually I started propagating the type to initialize totally replacing the DataHelpers.getType<T>(); invocation in _internalType . That helped with the first point but then I saw that DataHelpers.getType<T>(); is also used in other places as well. So maybe we should never use it without a type  parameter but at the moment I'm not sure if this is feasible in other places.

I do not know if you can disable minification for dart2js, but maybe adding "-O0" will help.

That was my last attempt but it seems not supported yet the ability to pass parameters (according to this issue ). Even if there is this Dart official package that seems to be helpful but I can't make it work during Flutter build .

Another way to help from the library side could be to add a DataHelper.defineTypeName(String name) to allow developers specify the type name globally in there, overwriting the default name generation - this would also help with reserved type names etc. As the implementation of getType already uses an internal cache, this would be very easy to implement.

That's a good point, I added the function you suggested in DataHelper:
static void defineTypeName<T>(String type) {
    _types[T] = type.decapitalize().pluralize();
  }

In main.dart I added:
void main() {
  DataHelpers.defineTypeName<User>("user");
  DataHelpers.defineTypeName<Todo>("todo");
  runApp(
    ProviderScope(
      child: const MyApp(),
      overrides: [
        configureRepositoryLocalStorage(clear: false),
      ],
    ),
  );
}

A little hacky but it works. We could use it but I think that the root cause to the error is to use T.toString() . As explained in this other issue it seems to be a bad practice even if the problem appears just on Flutter Web.

Thank you @Skycoder42 @andreacioni !
I thought I could take this opportunity to improve the internal types. There is no more runtime type resolving, everything is done during codegen. If you want to override a type use e.g.:
@DataRepository([JSONServerAdapter], internalType: 'todos')
class Task extends DataModel<Task> {

Can you let me know if this helped?

Thanks @frank06 ! I had no time to check the insight of the solution but if I use the internalType everything works just fine even on a Web release build.

That's great!

I have this same issue. I performed a 'flutter pub upgrade' and added the internalType to my DataRepository annotation, yet I still get this message. I cleared cache and cookies from my browser. Did I miss a step?

Did you run the build_runner after upgrading ?

I realized that just 5 minutes after I posted this, but I was not in front of my computer when I did so. It is working now. Thanks.


panzer won't start install due to Unicode error

After
git clone https://github.com/msprev/panzer
cd panzer
python3 setup.py install

I get
Traceback (most recent call last):
  File "setup.py", line 5, in <module>
    readme_text = file.read()
  File "/usr/local/Cellar/python3/3.4.3/Frameworks/Python.framework/Versions/3.4/lib/python3.4/encodings/ascii.py", line 26, in decode
    return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 127: ordinal not in range(128)

Any setting in the python3 package system needed?
Many thanks,
Leo

Thanks for catching this! I believe it was a unicode error in setup.py. You probably have your python3 default encoding set to something other than 'utf8'. I've pushed a fix now. It should install if you pull the latest version. Let me know if it doesn't.

Mmmmh. I did:
$ git pull
remote: Counting objects: 3, done.
remote: Compressing objects: 100% (3/3), done.
remote: Total 3 (delta 2), reused 1 (delta 0), pack-reused 0
Unpacking objects: 100% (3/3), done.
From https://github.com/msprev/panzer
   bf9e5a4..21429b9  master     -> origin/master
Updating bf9e5a4..21429b9
Fast-forward
 setup.py | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

and still got the unicode error:
$ python3 setup.py install --force
Traceback (most recent call last):
File "setup.py", line 7, in
readme_text = file.read()
File "/usr/local/Cellar/python3/3.4.3/Frameworks/Python.framework/Versions/3.4/lib/python3.4/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 127: ordinal not in range(128)

Where do I check what's my  python3 default coding?

Strange... What do you get if you type this into the terminal prompt?
python3
import sys
sys.getdefaultencoding()

I've pushed another change that should fix it. I believe the encoding are all being correctly handled in setup.py. Please give it a try and let me know if it doesn't work.

For sys.getdefaultencoding() I get:
utf-8

The install goes with the newest commit further, but still gives an error for me:
$ python3 setup.py install --force
running install
running bdist_egg
running egg_info
creating panzer.egg-info
writing entry points to panzer.egg-info/entry_points.txt
writing top-level names to panzer.egg-info/top_level.txt
writing dependency_links to panzer.egg-info/dependency_links.txt
writing panzer.egg-info/PKG-INFO
Traceback (most recent call last):
  File "setup.py", line 36, in <module>
    zip_safe=False)
  File "/usr/local/Cellar/python3/3.4.3/Frameworks/Python.framework/Versions/3.4/lib/python3.4/distutils/core.py", line 148, in setup
    dist.run_commands()
  File "/usr/local/Cellar/python3/3.4.3/Frameworks/Python.framework/Versions/3.4/lib/python3.4/distutils/dist.py", line 955, in run_commands
    self.run_command(cmd)
  File "/usr/local/Cellar/python3/3.4.3/Frameworks/Python.framework/Versions/3.4/lib/python3.4/distutils/dist.py", line 974, in run_command
    cmd_obj.run()
  File "/usr/local/lib/python3.4/site-packages/setuptools/command/install.py", line 67, in run
    self.do_egg_install()
  File "/usr/local/lib/python3.4/site-packages/setuptools/command/install.py", line 109, in do_egg_install
    self.run_command('bdist_egg')
  File "/usr/local/Cellar/python3/3.4.3/Frameworks/Python.framework/Versions/3.4/lib/python3.4/distutils/cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "/usr/local/Cellar/python3/3.4.3/Frameworks/Python.framework/Versions/3.4/lib/python3.4/distutils/dist.py", line 974, in run_command
    cmd_obj.run()
  File "/usr/local/lib/python3.4/site-packages/setuptools/command/bdist_egg.py", line 151, in run
    self.run_command("egg_info")
  File "/usr/local/Cellar/python3/3.4.3/Frameworks/Python.framework/Versions/3.4/lib/python3.4/distutils/cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "/usr/local/Cellar/python3/3.4.3/Frameworks/Python.framework/Versions/3.4/lib/python3.4/distutils/dist.py", line 974, in run_command
    cmd_obj.run()
  File "/usr/local/lib/python3.4/site-packages/setuptools/command/egg_info.py", line 173, in run
    writer(self, ep.name, os.path.join(self.egg_info, ep.name))
  File "/usr/local/lib/python3.4/site-packages/setuptools/command/egg_info.py", line 388, in write_pkg_info
    metadata.write_pkg_info(cmd.egg_info)
  File "/usr/local/Cellar/python3/3.4.3/Frameworks/Python.framework/Versions/3.4/lib/python3.4/distutils/dist.py", line 1108, in write_pkg_info
    self.write_pkg_file(pkg_info)
  File "/usr/local/Cellar/python3/3.4.3/Frameworks/Python.framework/Versions/3.4/lib/python3.4/distutils/dist.py", line 1129, in write_pkg_file
    long_desc = rfc822_escape(self.get_long_description())
  File "/usr/local/Cellar/python3/3.4.3/Frameworks/Python.framework/Versions/3.4/lib/python3.4/distutils/util.py", line 470, in rfc822_escape
    lines = header.split('\n')
TypeError: 'str' does not support the buffer interface
$

Sorry to be a pain with this! But I like the idea of panzer, so I really would like to try it...

Thanks. My 2 previous commits had clobbered each other and caused it to erroneously try to do a double utf8 decoding. I've just pushed a fix, that should -- fingers crossed -- resolve your problem.

Thanks heaps. Works now.

Great! Thank you for catching this bug for me.


Allow broadcast in distances

@seanmor5, let me know if this is sufficient in terms of distances. I will focus on classification metrics tomorrow.

@msluszniak this worked for what I needed! Thank you!

:green_heart: :blue_heart: :purple_heart: :yellow_heart: :heart:


Request for integration of ASE with AppLensv2 to have better access to ASE troubleshooting data & queries

AppServiceEnvironmentName: rtp
ImpactStartTime:

Thursday Feb 09 around 15:00 EST (GMT -0500)
Friday Feb 10 around 07:30 EST (GMT -0500)
ImpactEndTime:
-Wednesday Feb 15th 2pm EST ((GMT -0500)
Feedback: what would you like to see in AppLensV2 to help with this case, provide kusto queries, etc
Case:<PHONE_NUMBER>96828
Background: Customer tried to scale down the ASE rtp Front End instance count from 4 to 2. They did this twice on Feb 9 & 10. But still see the instance count at 4. So they think scaling is not working & need us to fix this.
Challenges

For FrontEnd and WP activities or events, Primary Portal does not log/Activity log for scaling events.
The existing JSON details might be improved to add operation type instead of simply saying “write operation”
Operations blade within the ASE Overview blade & FE pool blade should show operations events like scaling and others for FE and WP.
It was difficult to get the exact kusto queries since the current tooling (Web appTroubleshooter queries did not expose the scaling operations when checking into some of the Admin tables.
Also, it is not clear which specific Admin table will contain those details. Hawk Foreste was very kind to provide some details from these tables
AntaresAdminGeoEvents, AntaresAdminSubscriptionAuditEvents, AntaresCloudDeploymentAuditEvents
So it requires jumping through various backend system tables/queries to be able to find all the data.
=============================================
ASK: So it will be nice if AppLensv2 can integrate with ASE sites & expose data like how it wonderfully does for sites in public stamps. If applensv2 can expose data on ASE for below operations, it can help resolve these ASE cases faster.

ASE Scaling operations (on FE & Worker Pool
ASE creation/deletion operations.
Errors during ASE integration with VNET/Gateway/On-Premise Resources etc.
Any LSI/UD walk impacting ASE site availability.
Recommendation engine which can compare customer ASE configuration & give feedback if minimum requirements for ASE are not met.

Currently, almost all ASE cases miss FDR since our tooling does not allow faster/easier/intuitive way of looking into the data like applensv2 does.
Thanks
Jatin Bavishi

We resolved the above scaling issue by finding out that one of customer’s other colleagues has set a scale profile ‘rtp-default-prod-rg’  on the FE pool to be a minimum of 4:
So it seems the instance count rolled back to 4 even after customer tried to manually scale down to 2 on FE instance. Our backend queries confirmed on 2/9 going from 4 to 2. But customer portal always showed 4. So it was not possible for them to see an explanation why this happened & they thought scaling is not working for them.
It can help resolve these issues faster if somehow our backend system tooling can check if there are any scaling rule setup which can be overriding such behavior & expose them via applensv2 etc.
Or if portal has additional logic to check any scaling rules existing before customer attempts to make a manual scale change which is in conflict with the rule.

This query shows it clearly that changes are occurring in pairs:
https://wawscus.kusto.windows.net:443/wawsprod [Run in Kusto.Explorer] [Run in Kusto.WebExplorer]
AntaresAdminSubscriptionAuditEvents | where TIMESTAMP >= ago(7d)
| where SubscriptionId == "af58ba63-c0fa-4a75-91e1-3d97cd401cb9"
| where SourceMoniker == "WAWSPRODSN1"
| where ResourceGroupName  == "prod-rg"

It seems the heart of this ask is visibility into current deployments (scale, creation, deletion). Surfacing any errors or progress. Did it pass/fail and if fail then why.
I have an issue that address this problem #415


ISPN-12732 Replace org.wildfly with ${appserver.groupId} in pom.xml

https://issues.redhat.com/browse/ISPN-12732

Thanks @diegolovison


Enhancement: Row Click should propagate original event

The original mouse/touch event should be propagated, so additional checks can be performed.

This has been implemented so I close the issue.


Error when flashing LSTM model onto ESP32

Hi Developers, hi all!
I'm making some experiments with LSTM networks using Keras, TensorFlow (specifically, tf-nightly 2.11.0-dev20220911), and TensorFlowLite. On the model authoring side, I'm able to successfully build the model, apply compression techniques and get the equivalent Lite model, and the .cc file.
However, when it's time to flash the model onto the ESP32, I always get an error, typically of the kind "Failed to get registration from op code CUSTOM". Therefore, I've decided to do something simpler, such as 1) using an existing example from Keras LSTM fusion Codelab, 2) avoiding the adoption of compression techniques.
Despite such a try, I still face an error when flashing onto ESP32, which is the following:
Didn't find op for builtin opcode 'UNIDIRECTIONAL_SEQUENCE_LSTM' version '1'. An older version of this builtin might be supported. Are you using an old TFLite binary with a newer model?
Failed to get registration from op code UNIDIRECTIONAL_SEQUENCE_LSTM
To recap:

the existing example I'm using to generate the very simple model is from Keras LSTM fusion Codelab, which uses TensorFlow version 2.4;
I use espressif, toolchain version esp-idf-v4.4
my target is esp32;
my specific HW onto which I try to flash the model is ESP32-WROOM-32.

I'm stuck on trying to understand the source of the problem, i.e., if it is a matter of TensorFlow version, or espressif version, or something that is not yet supported on the espressif side. Can you please help me try to shed a light on this?
Here attached you can find the TFLite model and the .cc generated with xxd starting from the simple Keras LSTM fusion Codelab example if this can be of help to reproduce the error.
Please, let me know if you need any further information.
Chiara
material.zip

Hi @ChicchiPhD UNIDIRECTIONAL_SEQUENCE_LSTM is supported on current version.
Can you please make sure you have registered this OP in your code?
Something like this:
  static tflite::MicroMutableOpResolver<5> micro_op_resolver;
  micro_op_resolver.AddReshape();
  micro_op_resolver.AddSoftmax();
  micro_op_resolver.AddFullyConnected();
  micro_op_resolver.AddUnidirectionalSequenceLSTM();

and check if this works?
Reference from example: https://github.com/espressif/tflite-micro-esp-examples/blob/2a93aa3106f181768d75f64bcac629f344a2ca22/examples/person_detection/main/main_functions.cc#L94

Hi Vikram,
thanks for your reply!
In the code there is actually static tflite::AllOpsResolver resolver; Therefore
it should include all supported operOP, am I right?
Il giorno mar 13 set 2022 alle ore 09:17 Vikram Dattu <
@.***> ha scritto:

Hi @ChicchiPhD https://github.com/ChicchiPhD
UNIDIRECTIONAL_SEQUENCE_LSTM is supported on current version.
Can you please make sure you have registered this OP in your code?
Something like this:
static tflite::MicroMutableOpResolver<5> micro_op_resolver;
micro_op_resolver.AddReshape();
micro_op_resolver.AddSoftmax();
micro_op_resolver.AddFullyConnected();
micro_op_resolver.AddUnidirectionalSequenceLSTM();
and check if this works?
Reference from example:
https://github.com/espressif/tflite-micro-esp-examples/blob/2a93aa3106f181768d75f64bcac629f344a2ca22/examples/person_detection/main/main_functions.cc#L94
—
Reply to this email directly, view it on GitHub
https://github.com/espressif/tflite-micro-esp-examples/issues/23#issuecomment-1244999093,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AYFUMNCAUXVDBMJFWGBZGZTV6AS7DANCNFSM6AAAAAAQKHYJHY
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Chiara Contoli, Ph.D.
Junior Assistant Professor (fixed-term)
Department of Pure and Applied Sciences (DiSPeA)
University of Urbino "Carlo Bo"
Piazza della Repubblica 13, 61029 Urbino, Italy

Hi @ChicchiPhD yes, you're right. AllOpsResolver should just work fine but code pulled in will be larger!
I used model from your model.cc with AllOpsResolver and this works fine.
I think you need to update your local code. Just checkout latest master from espressif/tflite-micro-esp-examples. This should solve your problem.

Hi Vikram,
my bad, I had misunderstood the guidelines ((For ESP32-S3 target, IDF
version release/v4.4 is needed)), therefore I thought that for the ESP32 an
older version was needed. I checked out the latest version, the simple
example worked.
I switched back to my experiment, so I've built my LSTM network, applied
both pruning and quantization (specifically, fully integer) and, as I've
said in my very first message, I got the equivalent Lite models, and the
.cc file. When I try to flash the model onto the ESP32, I get this error
also with the latest espressif version, "Failed to get registration from op
code CUSTOM Allocate Tensors() Failed".
Is this related to the fact that the network model contains something not
supported by espressif? is there a way to discover which is, or are, the
things contained in the model that are not supported?
Here attached you can find two .tflite files (one it's related to the model
not quantized yet and the other to the quantized one), the third one is the
.cc file of the quantized model.
Thanks for your support!
Il giorno mar 13 set 2022 alle ore 11:17 Vikram Dattu <
@.***> ha scritto:

Hi @ChicchiPhD https://github.com/ChicchiPhD yes, you're right.
AllOpsResolver should just work fine but code pulled in will be larger!
I used model from your model.cc with AllOpsResolver and this works fine.
I think you need to update your local code. Just checkout latest master
from espressif/tflite-micro-esp-examples. This should solve your problem.
—
Reply to this email directly, view it on GitHub
https://github.com/espressif/tflite-micro-esp-examples/issues/23#issuecomment-1245129011,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AYFUMNFAPXXGM27NITWQFFLV6BBBJANCNFSM6AAAAAAQKHYJHY
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Chiara Contoli, Ph.D.
Junior Assistant Professor (fixed-term)
Department of Pure and Applied Sciences (DiSPeA)
University of Urbino "Carlo Bo"
Piazza della Repubblica 13, 61029 Urbino, Italy

Hi @ChicchiPhD I was referring to updating tflite-micro-esp-examples repo.
If this is the problem with CUSTOM ops, it is not Espressif specific as it concerns core tflite-micro framework!
Previous model you attached (with UnidirectionalSequenceLSTM) works fine for me. I cannot find attachments in your recent message. I could take a look.

Hi @vikramdattu ,
Sorry, maybe uploading the attachment from the email failed, had to switch to github page to upload the zip folder again. Can you please check if you incur the same error with this file?
Thank you so much for your help.
material (1).zip

Hey @ChicchiPhD sorry for late reply. Did you figure out yourself how to add custom ops? Do you still want me to try the model?

hi @vikramdattu sorry to disturb you. I have an issue like that when i try an implementation of my LSTM model on ESP32 : Failed to get registration from op code CUSTOM
AllocateTensors() failed
Model begin: ERROR
Guru Meditation Error: Core  0 panic'ed (Load access fault). Exception was unhandled.
There is the tflite model that ive convert into a char array for the implementation, can you help me with this please ? :
modele_sans_quantification.zip


Require at least v0.6 of guzzlehttp/oauth-subscriber

This PR adjusts the dependencies in composer.json to require at least version 0.6.0 of guzzlehttp/oauth-subscriber. Fixes #3.

Hi Sven, thanks for providing an update. I have used a separate commit for other minor updates to composer.json and reviews, so I will close your PR. Regards, Joey


Compatibility check and testing for Responsive Design (jsonConfig)

Notification from ioBroker Check and Service Bot
Dear Adapter developer,
ioBroker should be fully usable and operable on mobile devices
So please check your adapter jsonConfig for Responsive Design.
You can perform these tests in the developer console of your browser (F12)

For jsonConfig, all resolutions should be taken into account in the respective inputs.
The following resolutions are provided:

xl - width in 1/12 of screen on extra large screens (1536px < width)
lg - width in 1/12 of screen on large screens (1200px <= width < 1536px)
md - width in 1/12 of screen on middle screens (900px <= width < 1200px)
sm - width in 1/12 of screen on small screen (600px <= width < 900px)
xs - width in 1/12 of screen on tiny screens (width < 600px)

We recommend the following values for the standard layout
"xs": 12,
"sm": 12,
"md": 6,
"lg": 4,
"xl": 4

The following entry should be made below  "type": "tabs" in order to display a clearly legible table bar:
"tabsStyle": {
  width: "calc(100% - 100px)"
},

Please close the issue after you checked it.
Feel free to contact me (@iobroker-bot) if you have any questions.
And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.
your
ioBroker Check and Service Bot
@simatec for evidence
Note: If you added Responsive Design tests already, simply close this issue.

see https://github.com/copystring/ioBroker.roborock/issues/679#issuecomment-2500864802

Feel free to close as @simatec already stated the the UI looks good.
We max evaluate how to exclude the checker errors in you case. As this is currently the only adapter I know which states to have worse look when using the size attributes I'm not sure how to proceed.
You can keep the issue open too to discuss a solution for your adapter which is not closed / updated by checker bot.


feat(redis): Undefined array key "persistent" in Drupal\redis\ClientF…

…actory::getClient()

Hi @zachomedia does this look ok to merge?


enums as const

I believe there's an example here: https://github.com/dotansimha/graphql-code-generator/pull/3569

also, please fix the tests snapshots


Encode/Embed Functionality

For users that just want to use embedding extraction  - without touching any other building blocks - for their texts at hand, add encode or embed function that takes text, desired embedding type (bert, w2vec, tfidf) and level (sentence, document) as a parameter and returns fixed length array(s) for the downstream task user wants.

Related to that, I think it would be a nice idea to expose the functionalities of Sadedegel as procedural interface, though that might require a bit of an architecture change.

Waiting for the pull request as we have talked.

This functionality is provided by extensions.sklearn. No need for and extra endpoint for embedding generation.


Support for AWS provider 3

Currently terraform used aws provider ~> 2.23. cannot resolve aws provider 3.1.0.
terraform {
  required_version = "~> 0.12.6"

  required_providers {
    aws = "~> 2.23"
  }
}

v2.13.0 has been just released with the support of Terraform 0.13 and AWS provider v3.


Docker images - too many requests

Hi,
I recently started using geneshot and when I run the tool, I get the following error:
Error executing process > 'annotation_wf:shard_genes (Split the gene catalog into smaller shards)'

Caused by:
  Failed to pull singularity image
  command: singularity pull  --name ubuntu-18.04.img.pulling.1626155307848 docker://ubuntu:18.04 > /dev/null
  status : 255
  message:
    FATAL:   While making image from oci registry: error fetching image to cache: failed to get checksum for docker://ubuntu:18.04: Error reading manifest 18.04 in docker.io/library/ubuntu: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

It seems like docker has recently changed its policy on how many pulls you can do every couple hours. I'm not sure if that is the problem. Is there a way to pull these images and store them locally rather than pulling them every time geneshot runs?

Hi again,
I was wondering if there has been any kind of update on this issue?
Thank you.

My apologies for losing track of this issue! I'm not aware of a specific fix for this, but you might be able to get some help by asking people in the Nextflow Slack channel (https://www.nextflow.io/blog/2022/nextflow-is-moving-to-slack.html), since it seems to be related to the core functioning of Nextflow.


chore: Remove obsolete functions from StringFormatter

This PR removes some obsolete functions that I forgot to remove a long time ago.
User story:
https://dasch.myjetbrains.com/youtrack/issue/DSP-130

@subotic ping

Sorry, didn't see that I should review it. Maybe we could try adding the reviewer as a second assignee on YT when moving the ticket to "To Review"? I'm relatively frequently scanning the Agile Boards on YouTrack for my picture :-)

@subotic Sorry for asking you to review this very long PR. :)


Remove --docker-bridge-address

Option '--docker-bridge-address' has been deprecated and will be removed in a future release.

#sign-off


Documenting avn service command

What should we add to our content collections?
Documenting Aiven client avn service command. This is the commands with more options and also the one mostly used by our customers
List of issues within this epic

[x] #219
[x] #220
[x] #221
[x] #222
[x] #223
[x] #224
[x] #225
[x] #226
[x] #227
[ ] #228
[x] #229
[ ] #230
[x]  #231
[ ]  #232
[x]  #233
[x]  #234
[x]  #235
[x]  #236
[x]  #237
[x]  #238
[ ]  #239
[x]  #240
[x]  #241
[x]  #242
[x]  #246
[ ]  #247
[ ]  #248
[ ]  #249
[ ]  #250
[x]  #251
[x]  #254
[x]  #255
[x]  #256
[x]  #257
[x]  #258
[x]  #259
[ ]  #772

This shows the usage of the -v even if it's not listed as parameter
https://developer.aiven.io/docs/tools/cli/service.html#avn-service-types


FederatedStore to handle namedOperations

FederatedStore either needs to (temp) safely be stopped from using named operations or correctly know how to execute a namedOperation against multiple graphs.
Ref: gh-955

Named Operations should work due to the change made in issue: #1083


RuntimeException: The service "currency_converter" does not exist (using laravel-swap)

Note that this error happened on using of currently undocumented functionality (florianv/laravel-swap v1.3.0 docs doesn't contain any info about currency_converter service but its dependency florianv/exchanger v1.3.0 includes this service). Thus, this issue is not critical right now
dependency tree:

florianv/laravel-swap: ~1.0 (1.3.0  installed, v1.3.0 is the latest available)

florianv/swap: "^3.4", (3.5.0 installed, 3.5.0 is the latest available)

florianv/exchanger: "^1.1" (1.3.0 installed, 1.3.0 is the latest available)

I know, it's not a laravel-swap package repo, but this issue should be fixed on this repo (IMO).
Stacktrace
RuntimeException: The service "currency_converter" does not exist. in ../vendor/florianv/laravel-swap/src/SwapServiceProvider.php:105
Stack trace:
#0 ../vendor/florianv/laravel-swap/src/SwapServiceProvider.php(128): Swap\Laravel\SwapServiceProvider->registerServices(Object(Illuminate\Foundation\Application))
#1 ../vendor/laravel/framework/src/Illuminate/Container/Container.php(776): Swap\Laravel\SwapServiceProvider->Swap\Laravel\{closure}(Object(Illuminate\Foundation\Application), Array)
...

Cause of the problem
There is a getServiceClass method from the laravel-swap package https://github.com/florianv/laravel-swap/blob/1.3.0/src/SwapServiceProvider.php#L201-L210 that trying to find a class using its alias. This method can't resolve the classname because alias is currency_converter but classname is CurrencyConverterApi
Solution(s)

Easy/quick-fix and (almost)non-breaking: Rename CurrencyConverterApi to CurrencyConverter so getServiceClass() will be able to resolve class
Easy and breaking: rename currency_converter to currency_converter_api
Comprehensive: refactor alias to FQCN mapping to make it more flexible
Ugly and 100% non-breaking: add a new if condition to getServiceClass()

I think 1st option is the best one because:

I have enough time to fix it right now
It's (almost)non-breaking (laravel-swap v1.3 doesn't contain docs about CurrencyConverterApi service)

Todo

Add test contact to instantiate all available services by their aliases
Try to find a time to refactor laravel-swap and symfony-swap to have more flexible way to add new services (and add custom services to ANY place in the chain (now it's possible to add them at the top of the chain (at least for laravel-swap)))

I am closing the issue since the PR was merged in the master branch (will be released soon).
Thanks for your work @lptn 👍


Add samples for ClientCertificateCredential

The other 3 primary langs have docs like this:
https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/identity/Azure.Identity/samples/ClientCertificateCredentialSamples.md

This is covered by the key_vault_cert.py sample, but we don't cover rolling certificates. I'll look into adding that to our sample by writing an example custom credential, as other languages do.


[QUESTION] Is posible disable the request logger middleware?

Hi... Is possible toggle on/off the request logger?

Hi, if you need to prevent request/response log and you DO NOT want to use logger in current route, you can do this via config params (forRoutes, exclude)
if you need to prevent request/response log and you DO want to use logger in current route you can look at API of related library (autoLogging, autoLogging.ignorePaths), which params is passed via pinoHttp

Also see this comment in another issue, seems like it is not shipped now, but may be soon

@iamolegga even when use forRoute and exclude to disable the route logging, the middleware is still configured, so in this particular case when I want exclude all routes, the middleware is not necessary...

@gperdomor Excuse me, I didn't get it, what is your case?

@iamolegga don't worry... In my case, I only want to use the logger service, not the middleware...
Here is where the middleware is registered... Maybe one parameter middleware: boolean should be sufficient to enable or disable the middleware https://github.com/iamolegga/nestjs-pino/blob/d338c54f6c4c06ce1ea69f00805eb75344c00c1c/src/LoggerCoreModule.ts#L67

Got you, sorry, but middleware is required, because it creates logger object which is used internally by Logger/PinoLogger, so yes, you can rely on autoLogging/autoLogging.ignorePaths properties of pinoHttp object of params.
Just saw, that new pino-http's types are shipped already, so you can wait for new release with this soon

check out v1.2.0

Does the request logging work with fastify? I can't seem to get a configuation that will do access/error logs or include the request id in general logging throughout a request.

Does the request logging work with fastify?

It should, if it's not please provide example repo with bug

Does the request logging work with fastify?

It should, if it's not please provide example repo with bug

I think the issue is with express-ctx, the middleware doesn't seem to be running on fastify.
https://github.com/btilford/nestjs-pino-fastify-bug
I was able to hack around it by writing custom middleware, express-ctx isn't doing very much either. If you used cls-hooked directly I think nestjs-pino could also work for lambdas or cloud functions where you have an invocation id.

Exception thrown when using nestjs-pino with FastifyAdapter.
(node:85089) UnhandledPromiseRejectionWarning: TypeError: Unexpected MODIFIER at 3, expected END
    at mustConsume (/backend/node_modules/middie/node_modules/path-to-regexp/dist/index.js:113:15)
    at parse (/backend/node_modules/middie/node_modules/path-to-regexp/dist/index.js:172:9)
    at stringToRegexp (/backend/node_modules/middie/node_modules/path-to-regexp/dist/index.js:329:27)
    at pathToRegexp (/backend/node_modules/middie/node_modules/path-to-regexp/dist/index.js:403:12)
    at Object.use (/backend/node_modules/middie/engine.js:23:16)
    at Object.use (/backend/node_modules/middie/index.js:30:21)
    at /backend/node_modules/@nestjs/platform-fastify/adapters/fastify-adapter.js:130:27
    at MiddlewareModule.registerHandler (/backend/node_modules/@nestjs/core/middleware/middleware-module.js:138:9)
    at MiddlewareModule.bindHandler (/backend/node_modules/@nestjs/core/middleware/middleware-module.js:96:25)
    at async /backend/node_modules/@nestjs/core/middleware/middleware-module.js:84:13

@btilford, Can you please post the custom middleware you used to bypass this issue.

@gowrav-scienaptic So I basically setup NestJS middleware instead of express middleware.
import {setValue} from 'express-ctx/dist';
import {middleware as ectx} from 'express-ctx';

// Middleware to create the logger
app.use((req, res, next) => {

    if (req.url.match(options.accessLogIgnore)) {
      const phto: Options = options.pinoHttpOptions.pinoHttp as Options;
      const copy: Options = clone<Options>(phto);
      copy.autoLogging = false;
      pinoHttp(copy)(req, res);
    }
    else {
      pinoHttp({
        ...options.pinoHttpOptions.pinoHttp as pinoHttp.Options,
      })(req, res);
    }
    next();
  });

  // Middleware to add the logger to the context. This part isn't ideal and should just use `cls-hooked` but does work.
  app.use((req, res, next) => {

    ectx(req, res, () => {
      // Make the logger available to PinoLogger's
      setValue(LOGGER_KEY, req.log);
      next();
    });
  });

@btilford, Thank you for the response. On debugging my issue, I found that using nestjs-pino with app.setGlobalPrefix('api'); throws the UnhandledPromiseRejectionWarning.

@gowrav-scienaptic https://github.com/nestjs/nest/issues/5568#issuecomment-708510442


Add note about stats api permission model, fixes #1547

r+
There's a weird test failure that has obviously nothing to do with this PR, maybe @diox has an idea about it?

Yeah the failure is mine following the post request task revert, I'll take care of it.


list and installed use different version names

:wave: :sparkling_heart:
$ xcode-install list
7
...

After xcode-install install 7:
$ xcode-install installed
7.0
...

The difference of 7 vs. 7.0 makes this harder to script.

(Presumably 7 is how the dev center reports it, but xcode-install should probably standardize that to 7.0.)

Yep, the reason for this is dev center vs. xcodebuild -version — this also causes #29. I'm not sure, though, how to do the standardisation well, next time -version might report 8.0.0? Maybe the best solution is having an additional mapping file distributed with the gem which fixes some well-known versions which differ?

this also causes #29

Oh gross :mask:

Maybe the best solution is having an additional mapping file distributed with the gem which fixes some well-known versions which differ?

Probably :cry:


Add support for only hours in time format with tests

Per issue #603 add support for just hours in the time format. This allows leaving out the minutes when parsing a time or datetime object.
If it is necessary to add more tests for specific cases or if the enhancement needs to be implemented through a different method than this simple change, please let me know.
The time macro was not adjusted as I think it does not makes sense to make time!(12) convert to 12:00 instead of 00:12. The user can simply write out the desired time.

I will need to check and possibly update the documentation. Will add this

Diff looks good. There's one thing I thought of while looking at it, but I don't want to put it on you. Merging as-is :slightly_smiling_face:


Add register example for symfony 4

Fixes # Example how to register this Twig extension in symfony 4
NB When force minifying on development, the symfony debug bar stops working (it is injected though). Can you look into that?

Coverage remained the same at 100.0% when pulling 1b674a174ca86cc60c92f3c42cd76508513f5df1 on Mondane:patch-1 into bdb0c775b1bb7ac9b304d671506c27c51e5fedc6 on voku:master.

Thanks for the documentation update.


add dubbing agent & elevenlabs tools

closes : https://github.com/video-db/Director/issues/36

Can elevenlabs give us a download URL instead of local file download?
If yes that can speed up the upload process (no need to download and then upload just give url)

@ashish-spext , no option present to get download url on this endpoint Get Dubbed File,
Also no option present in Dub a video or endpoint
Notes for optimization for later:

Try Dub a Audio endpoint, excepting that it can reduce elevenlabs processing time
Try text to speech api endpoint


Warning on supplying a Dataset to the Dataset constructor

In [1]: import xarray as xr

In [3]: ds=xr.Dataset({'a':xr.DataArray([1,2,3])})

In [4]: xr.Dataset(ds)
/Users/maximilian/drive/workspace/xarray/xarray/core/dataset.py:373: FutureWarning: iteration over an xarray.Dataset will change in xarray v0.11 to only include data variables, not coordinates. Iterate over the Dataset.variables property instead to preserve existing behavior in a forwards compatible manner.
  both_data_and_coords = [k for k in data_vars if k in coords]
Out[4]:
<xarray.Dataset>
Dimensions:  (dim_0: 3)
Dimensions without coordinates: dim_0
Data variables:
    a        (dim_0) int64 1 2 3

Problem description
Currently we run both_data_and_coords = [k for k in data_vars if k in coords], where data_vars is the first arg to the constructor. So, when data_vars is a Dataset, we'll raise a warning.
More importantly: this raises the question of how we should handle xr.Dataset(ds)
Currently we retain the coords, but discard attrs. That seems arbitrary?
I'd have to check, but when we change __iter__ to only reference data_vars, we may also discard coords
I don't have a strong view. If you think that Foo(foo) should always return foo (which is often the case in pandas), then we should retain the full object.
 This warning message is slightly unfortunate indeed.

Currently we retain the coords, but discard attrs. That seems arbitrary?

Agreed!

I don't have a strong view. If you think that Foo(foo) should always return foo (which is often the case in pandas), then we should retain the full object.

Yes, we could defensibly go either way here.
Generally, I don't think this is an important invariant, and it certainly doesn't make sense for every type. But maybe it does make sense for Dataset, given that we do do so for DataArray:
https://github.com/pydata/xarray/blob/a9d1f3a36229636f0d519eb36a8d4a7c91f6e1cd/xarray/core/dataarray.py#L205-L223
(But to be clear, this wasn't a terribly careful design decision for DataArray, either.)

Closing with 0.11 release


How to configure bluetooth connection in  the NFC tag

Is it possible to configure a Bluetooth connection in the NFC tag?

any luck?

any luck?


Using Docker Beaker notebook 1.3.1: R language backend failed

When running the docker image and executing an R cell, I get an "R language backend failed!" error.
When starting the container there is also an Nginx error message:
Stderr log from starting the container and running an R cell:
starting nginx instance (/home/beaker/src/core/nginx)
nginx-stderr>nginx: [alert] could not open error log file: open() "/var/log/nginx/error.log" failed (13: Permission denied)
[main] INFO org.eclipse.jetty.server.Server - jetty-8.1.13.v20130916
[main] INFO org.eclipse.jetty.server.AbstractConnector - Started SelectChannelConnector@<IP_ADDRESS>:8802

Connecting to https://c569e0a45634:8800/
Submit this password: 4API07iR6WF0MVh

restart-nginx-IPython-stderr>nginx: [alert] could not open error log file: open() "/var/log/nginx/error.log" failed (13: Permission denied)
restart-nginx-IPython-stderr>2015/07/11 19:29:10 [notice] 77#0: signal process started
Running
0: /home/beaker/src/core/config/plugins/eval/ipythonPlugins/ipython/ipythonPlugin
1: 8804
IPython-stderr>[I 19:29:11.138 NotebookApp] Using existing profile dir: u'/home/beaker/.beaker/v1/nginx1353221801172463837/profile_beaker_backend_IPython'
IPython-stderr>[I 19:29:11.142 NotebookApp] Writing notebook server cookie secret to /home/beaker/.beaker/v1/nginx1353221801172463837/profile_beaker_backend_IPy
thon/security/notebook_cookie_secret
IPython-stderr>[I 19:29:11.143 NotebookApp] Using MathJax from CDN: https://cdn.mathjax.org/mathjax/latest/MathJax.js
IPython-stderr>[W 19:29:11.157 NotebookApp] Terminals not available (error was No module named terminado)
IPython-stderr>[I 19:29:11.157 NotebookApp] Serving notebooks from local directory: /home/beaker/src/core
IPython-stderr>[I 19:29:11.157 NotebookApp] 0 active kernels
IPython-stderr>[I 19:29:11.157 NotebookApp] The IPython Notebook is running at: http://<IP_ADDRESS>:8804/
IPython-stderr>[I 19:29:11.157 NotebookApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation).
Done starting IPython
IPython-stderr>[I 19:29:11.237 NotebookApp] 302 POST /login?next=%2F (<IP_ADDRESS>) 0.99ms
IPython-stderr>[I 19:29:11.331 NotebookApp] Kernel started: 52175351-dae0-406a-ae79-498d30f99be0
restart-nginx-R-stderr>nginx: [alert] could not open error log file: open() "/var/log/nginx/error.log" failed (13: Permission denied)
restart-nginx-R-stderr>2015/07/11 19:29:12 [notice] 109#0: signal process started
Running
0: /home/beaker/src/core/config/plugins/eval/r/rPlugin
1: 8805
nginx-stderr>2015/07/11 19:29:12 [error] 80#0: *56 open() "/home/beaker/.beaker/v1/nginx1353221801172463837/html/restart.694315355365/present.html" failed (2: N
o such file or directory), client: <IP_ADDRESS>, server: , request: "GET /restart.694315355365/present.html HTTP/1.1", host: "<IP_ADDRESS>:8803"
nginx-stderr>2015/07/11 19:29:12 [error] 80#0: *56 open() "/home/beaker/.beaker/v1/nginx1353221801172463837/html/restart.694315355365/present.html" failed (2: N
o such file or directory), client: <IP_ADDRESS>, server: , request: "GET /restart.694315355365/present.html HTTP/1.1", host: "<IP_ADDRESS>:8803"
nginx-stderr>2015/07/11 19:29:12 [error] 80#0: *56 open() "/home/beaker/.beaker/v1/nginx1353221801172463837/html/restart.694315355365/present.html" failed (2: N
o such file or directory), client: <IP_ADDRESS>, server: , request: "GET /restart.694315355365/present.html HTTP/1.1", host: "<IP_ADDRESS>:8803"
nginx-stderr>2015/07/11 19:29:12 [error] 80#0: *56 open() "/home/beaker/.beaker/v1/nginx1353221801172463837/html/restart.694315355365/present.html" failed (2: N
o such file or directory), client: <IP_ADDRESS>, server: , request: "GET /restart.694315355365/present.html HTTP/1.1", host: "<IP_ADDRESS>:8803"
Done starting R
nginx-stderr>2015/07/11 19:29:12 [error] 113#0: *70 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: c569e
0a45634, request: "GET /3072e5e/r.611479655664/rest/rsh/ready HTTP/1.1", upstream: "http://<IP_ADDRESS>:8805/rest/rsh/ready", host: "<IP_ADDRESS>:8800", referrer
: "https://<IP_ADDRESS>:8800/beaker/"
nginx-stderr>2015/07/11 19:29:12 [error] 113#0: *70 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: c569e
0a45634, request: "GET /3072e5e/r.611479655664/rest/rsh/ready HTTP/1.1", upstream: "http://<IP_ADDRESS>:8805/rest/rsh/ready", host: "<IP_ADDRESS>:8800", referrer
: "https://<IP_ADDRESS>:8800/beaker/"
nginx-stderr>2015/07/11 19:29:12 [error] 113#0: *70 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: c569e
0a45634, request: "GET /3072e5e/r.611479655664/rest/rsh/ready HTTP/1.1", upstream: "http://<IP_ADDRESS>:8805/rest/rsh/ready", host: "<IP_ADDRESS>:8800", referrer
: "https://<IP_ADDRESS>:8800/beaker/"
nginx-stderr>2015/07/11 19:29:12 [error] 113#0: *70 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: c569e
0a45634, request: "GET /3072e5e/r.611479655664/rest/rsh/ready HTTP/1.1", upstream: "http://<IP_ADDRESS>:8805/rest/rsh/ready", host: "<IP_ADDRESS>:8800", referrer
: "https://<IP_ADDRESS>:8800/beaker/"
nginx-stderr>2015/07/11 19:29:12 [error] 113#0: *70 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: c569e
0a45634, request: "GET /3072e5e/r.611479655664/rest/rsh/ready HTTP/1.1", upstream: "http://<IP_ADDRESS>:8805/rest/rsh/ready", host: "<IP_ADDRESS>:8800", referrer
: "https://<IP_ADDRESS>:8800/beaker/"
nginx-stderr>2015/07/11 19:29:12 [error] 113#0: *70 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: c569e
0a45634, request: "GET /3072e5e/r.611479655664/rest/rsh/ready HTTP/1.1", upstream: "http://<IP_ADDRESS>:8805/rest/rsh/ready", host: "<IP_ADDRESS>:8800", referrer
: "https://<IP_ADDRESS>:8800/beaker/"
nginx-stderr>2015/07/11 19:29:12 [error] 113#0: *70 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: c569e
0a45634, request: "GET /3072e5e/r.611479655664/rest/rsh/ready HTTP/1.1", upstream: "http://<IP_ADDRESS>:8805/rest/rsh/ready", host: "<IP_ADDRESS>:8800", referrer
: "https://<IP_ADDRESS>:8800/beaker/"
nginx-stderr>2015/07/11 19:29:13 [error] 113#0: *70 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: c569e
0a45634, request: "GET /3072e5e/r.611479655664/rest/rsh/ready HTTP/1.1", upstream: "http://<IP_ADDRESS>:8805/rest/rsh/ready", host: "<IP_ADDRESS>:8800", referrer
: "https://<IP_ADDRESS>:8800/beaker/"
R-stderr>[main] INFO org.eclipse.jetty.server.Server - jetty-8.1.13.v20130916
nginx-stderr>2015/07/11 19:29:13 [error] 113#0: *70 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: c569e
0a45634, request: "GET /3072e5e/r.611479655664/rest/rsh/ready HTTP/1.1", upstream: "http://<IP_ADDRESS>:8805/rest/rsh/ready", host: "<IP_ADDRESS>:8800", referrer
: "https://<IP_ADDRESS>:8800/beaker/"
nginx-stderr>2015/07/11 19:29:13 [error] 113#0: *70 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: c569e
0a45634, request: "GET /3072e5e/r.611479655664/rest/rsh/ready HTTP/1.1", upstream: "http://<IP_ADDRESS>:8805/rest/rsh/ready", host: "<IP_ADDRESS>:8800", referrer
: "https://<IP_ADDRESS>:8800/beaker/"
R-stderr>[main] INFO org.eclipse.jetty.server.AbstractConnector - Started SelectChannelConnector@<IP_ADDRESS>:8805
R-stderr waiting over
R-stderr>Jul 11, 2015 7:29:14 PM com.twosigma.beaker.r.utils.RServerEvaluator$workerThread startRserve
R-stderr>SEVERE: exception starting RServe
R-stderr>org.rosuda.REngine.Rserve.RserveException: eval failed, request status: error code: 127
R-stderr>       at org.rosuda.REngine.Rserve.RConnection.eval(RConnection.java:234)
R-stderr>       at com.twosigma.beaker.r.utils.RServerEvaluator$workerThread.startRserve(RServerEvaluator.java:431)
R-stderr>       at com.twosigma.beaker.r.utils.RServerEvaluator$workerThread.run(RServerEvaluator.java:460)
R-stderr>Jul 11, 2015 7:29:14 PM com.twosigma.beaker.r.utils.RServerEvaluator$workerThread startRserve
R-stderr>SEVERE: exception starting RServe
R-stderr>org.rosuda.REngine.Rserve.RserveException: eval failed, request status: error code: 127
R-stderr>       at org.rosuda.REngine.Rserve.RConnection.eval(RConnection.java:234)
R-stderr>       at com.twosigma.beaker.r.utils.RServerEvaluator$workerThread.startRserve(RServerEvaluator.java:431)
R-stderr>       at com.twosigma.beaker.r.utils.RServerEvaluator$workerThread.run(RServerEvaluator.java:473)

Thanks for the bug report.  Let me see what I can do about that, I think it should just be a matter of getting cherry picking the fix and pushing the container.
https://github.com/twosigma/beaker-notebook/commit/cd664b34ccd3bc19e365d4c1f7150694af02967c

container updated to v1.3.2
build time: 2015-07-12 03:08 UTC
version: v1.3.2-0-g2da061b


Enhanced FindBugs plugin to work with SpotBugs which is FindBugs successor

successor.
FindBugs development has been discontinued. SpotBugs is the spiritual
successor of FindBugs, carrying on from the point where it left off
with support of its community.
The FindBugs plugin made an assumption that the FindBugs code was
present in an artifact named "findbugs-3.0.1.jar" in order to
extract the FindBugs version number to ensure it was compatible
with the current JDK.
In order to work with SpotBugs a new optional parameter
named "validateClasspath" which defaults to true was added.
Each updated file was also improved to use immutable parameters and
local variables whenever possible. This is common strategy in other
languages (Kotlin, Scala, JavaScript, etc.)
The documents were also updated to include some helpful tips with
using the FindBugs plugin (e.g. adding the "Find Security Bugs")
See "https://spotbugs.github.io/" and "http://find-sec-bugs.github.io/" for more information.
Context

Contributor Checklist

[x] Review Contribution Guidelines
[x] Sign Gradle CLA
[ ] Link to Design Spec for changes that affect more than 1 public API (that is, not in an internal package) or updates to > 20 files
[ ] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
[ ] Provide unit tests (under <subproject>/src/test) to verify logic
[x] Update User Guide, DSL Reference, and Javadoc for public-facing changes
[x] Ensure that tests pass locally: ./gradlew quickCheck <impacted-subproject>:check

Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation including proper use of @since and @Incubating annotations for all public APIs
[ ] Recognize contributor in release notes

I didn't see an easy way to test my change other than trivial verification of setter values. I did test it against a sample Gradle project:
apply plugin: 'java'
apply plugin: 'findbugs'
sourceCompatibility = 1.8
repositories {
mavenCentral()
}
dependencies {
findbugs 'com.github.spotbugs:spotbugs:3.1.0-RC3'
findbugs configurations.findbugsPlugins.dependencies
findbugsPlugins 'com.h3xstream.findsecbugs:findsecbugs-plugin:1.6.0'
}
dependencies {
testCompile group: 'junit', name: 'junit', version: '4.12'
}
findbugs {
ignoreFailures = true
validateClasspath = false
}
tasks.withType(FindBugs) {
extraArgs = ['-html:fancy-hist.xsl']
reports {
xml.enabled = false
html.enabled = true
}
}

Thanks for providing the contribution. What's the name associated with your account you used to sign the CLA?

@blackbeltdev Thanks for the PR!
I have a few comments:

We're still using Java 6 syntax due to some backwards compatibility with Java5/6 we need to maintain for a small part of the Gradle code base (and Intellij doesn't like to mix versions).  So we can't use the diamond syntax.
Thanks for catching the lack of documentation around extraArgs/findBugsPlugins. It'll get merged quicker as a separate PR.
I think disabling the classpath validation is the wrong direction for implementing this. We should just bite the bullet and build a classloader with the findbugs configuration.  Then in that classloader, we can inspect edu.umd.cs.findbugs.Version.RELEASE_BASE and get a version for FindBugs that doesn't require applying a regex to file names.
I think we should add a dedicated section to the FindBugs documentation chapter about SpotBugs and a sample that uses SpotBugs.
We need integration coverage for this added to AbstractFindBugsPluginIntegrationTest.  Unfortunately, this test is old enough that it's not doing cross-version testing.  We need that too, but I don't expect you to add it.  I think it might make sense to just extend AbstractFindBugsPluginIntegrationTest, call it SpotBugsIntegrationTest and change the setup method to add the appropriate dependencies to the build script to use SpotBugs.

We're happy to help move this along through our process and answer any questions you have.

Kirk Rasmussen
On Thursday, July 20, 2017, 2:49:42 PM CDT, Benjamin Muschko<EMAIL_ADDRESS>wrote:
Thanks for providing the contribution. What's the name associated with your account you used to sign the CLA?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Sorry I had checked the minimum system requirements for Gradle 4 and it said Java 7 so I had assumed diamond operator was ok.
IMO at this point I kind of think FindBugs is dead so not sure worth investing too much into it. I use the IJ plugin w/ Java 8 on a regular basis and it seems to work but I've seen bug reports claiming its buggy. AFAIK JDK 8 isn't officially supported by FindBugs. SpotBugs does however. OTOH SpotBugs hasn't had an official release yet :(
Glad I could help. Is there anything specific I can do to help here? I don't think I quite got the document XML correct. I couldn't figure out how to get the new property I added "validateClasspath" to show up in the user guide. It did show up in the javadoc though. I noticed that updating the XML file in the class section did affect user guide generation but not my new parameter.
Regards,Kirk Rasmussen
On Friday, July 21, 2017, 12:25:51 AM CDT, Sterling Greene<EMAIL_ADDRESS>wrote:
@blackbeltdev Thanks for the PR!
I have a few comments:

We're still using Java 6 syntax due to some backwards compatibility with Java5/6 we need to maintain for a small part of the Gradle code base (and Intellij doesn't like to mix versions). So we can't use the diamond syntax.
Thanks for catching the lack of documentation around extraArgs/findBugsPlugins. It'll get merged quicker as a separate PR.
I think disabling the classpath validation is the wrong direction for implementing this. We should just bite the bullet and build a classloader with the findbugs configuration. Then in that classloader, we can inspect edu.umd.cs.findbugs.Version.RELEASE_BASE and get a version for FindBugs that doesn't require applying a regex to file names.
I think we should add a dedicated section to the FindBugs documentation chapter about SpotBugs and a sample that uses SpotBugs.
We need integration coverage for this added to AbstractFindBugsPluginIntegrationTest. Unfortunately, this test is old enough that it's not doing cross-version testing. We need that too, but I don't expect you to add it. I think it might make sense to just extend AbstractFindBugsPluginIntegrationTest, call it SpotBugsIntegrationTest and change the setup method to add the appropriate dependencies to the build script to use SpotBugs.

We're happy to help move this along through our process and answer any questions you have.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Will this be coming to a Gradle release soon?


WIP: Use a hash of the template field as the template version

Previously the resourceVersion of the template resource was used, but resourceVersion changes when status changes.  Switching to a hash paves the way to store propagated version in the status of a template resource.
Part 1 of #479

I'm having trouble replicating the ci failure locally, marking WIP until I figure it out.


Added warning if Imagick is not installed/enabled.

If GD is used instead of Imagick, rotating uploaded pictures leads to
a loss of their metadata. Since this is unexpected and maybe a problem,
the diagnostics should show a warning.
This commit displays a warning if it's either not installed or not
enabled in settings.
Maybe, rotating pictures etc. should even be optional in case the user
can't install imagick and still doesn't want to lose the metadata?

Fantastic idea! Thanks.

Maybe, rotating pictures etc. should even be optional in case the user can't install imagick and still doesn't want to lose the metadata?

Showing a warning should be enough. Complaints are relative low. It seems like most users want their photos rotated correctly rather than keeping the metadata.


Fixes

Added an updated Fortran icon. Replaces the old one.
Fixes #2832
Changes proposed:

[ ] Add
[ ] Delete
[x] Fix
[ ] Prepare

For the record, it looks like this:

Thanks @jacobwilliams for your contribution. The icon needs some small refactor to follow our guidelines but don't worry. I'll take care of it before merging.

Cool! Let me know if you need me to do anything else.


FedCM not used in googleOneTap

When using googleOneTap() I still get this warning:
[GSI_LOGGER]: Your client application uses one of the Google One Tap prompt UI status methods that may stop functioning when FedCM becomes mandatory.
Refer to the migration guide to update your code accordingly and opt-in to FedCM to test your changes.
Learn more: https://developers.google.com/identity/gsi/web/guides/fedcm-migration?s=dc#display_moment and
https://developers.google.com/identity/gsi/web/guides/fedcm-migration?s=dc#skipped_moment

I saw use_fedcm_for_prompt is enabled by default but it doesn't seem to solve it even when enabling it manually:
app.use(vue3GoogleLogin,
    clientId: <CLIENTID>
    idConfiguration: {
        use_fedcm_for_prompt: true,
    },
});

@ShakedGold Can you check the latest version? I have added a patch to remove this warning


Release documentation points to snapshots

Issue description
For some reason, the latest link in the docs points to the SNAPSHOT version of the plugin.

Probably a release glitch as it's fixed in 3.3.2.


Version number

We should publish this package in coq-release repo. Should we start with 0.1.0 or follow ITree version number?

0.1.0 sounds fine, feel free to add it. It doesn't seem necessary to entangle with coq-itree releases.


I need to have ImageView, or other custom layout as DayView, suggestions?

Is it possible to implement with this library or I'll have to mod it?

you can add span to each day. what kind of custom layout do you need

@osrl I need it to be ImageView, as I said. Span won't do it.

Is it loading from somewhere else? You can add a background drawable to your dayview or use LineBackgroundSpan. You probably can't use ImageView. Why do you need ImageView?

@osrl Yeah I need to load an image from the internet with Glide..


Debugging ANGULAR project in VSCode not working.

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.87.2
OS Version: Windows 10 Enterprise

Steps to Reproduce:

In launch.json created Launch Chrome against localhost as:

{
"version": "0.2.0",
"configurations": [
{
"type": "chrome",
"request": "launch",
"name": "Launch Chrome against localhost",
"url":"https://anonymous.local:3200/Home/Welcome",
"webRoot": "${workspaceFolder}"
}
]
}
The url indicates the login page of the application

Putting breakpoints at the required places in the angular code(ts files)

Selecting  "Launch Chrome against localhost" from and start debugging(f5)

Application starts and logged in successfuly, navigate to page where breakpoint will be hitted->
application hangs and nothing happens, neither the breakpoint is reached, after few minutes of wait the break point is reached and when press f10 or f5 this message appears:

I have to then either reopen or close vscode which ends up everything.
This is really frustrating as it hampers my daily development,
this was working perfectly fine but from last few updates i am seeing this error.
I have tried uninstalling and re installing vs code, also updated to version 1.87.2 but nothing worked.
Please help me out in resolving this on priority.

Thanks for the issue, unfortunately I'm not able to reproduce it at the moment. Could you share your user settings so I can see if there's something in there I might be missing?

Hi @connor4312 , as suggested i've updated to the latest version 1.89.1 today and unfortunately the issue still persists.

Whenever I attach a debugger it takes a lot of time to the debugger to hit and if it hits and i try to proceed this message appears after waiting for few minutes and i have to restart vscode .

my launch.json file

This is really frustrating as i have to be dependent on browser dev tools to debug any piece of code. I would really appreciate help from your end.

Could you share your user settings as well? Thanks!

Which settings are you referring to?
On Thu, 16 May 2024, 22:26 Connor Peet, @.***> wrote:

Could you share your user settings as well? Thanks!
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/210717#issuecomment-2115763611,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEFODZZHTFFJXG6LROREDKDZCTQKZAVCNFSM6AAAAABGOSI76GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJVG43DGNRRGE
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Could you share your user settings as well? Thanks!

if you can be more specific which user settings you're referring, will share.

You can open the settings.json though the command Preferences: Open User Settings (JSON)

settings.json
Pls find the file attached.

@connor4312 any suggestions?

I have the same problem. When debugging Edge or Chrome the browser crawls to 1/100th of normal speed. If one tries to stop the debug session, VS Code freezes completely. Only using reload from the "window is not responding" -dialog restores functionality.
In my experience using FireFox and "Debugger for Firefox" extension works and I'm currently using it as a work-around.
I also have a colleague who has the same issue. Updating or complete re-install doesn't resolve the issue.

Additional datapoints:

Ms Edge is completely unusable. Slowdown by factor >1000, huge cpu utilization even when page and debugger are idle.
Brave seems to work just fine based on a few days usage.
Vivaldi is also viable though noticeably slower than Brave

Thus I'm using Brave as current work-around

Using Code I attach the debugger to a browser that is running an Angular Typescript application. I can hit breakpoints and debug using VSCode 1.94.2. But after upgrading VSCode to 1.95.1, if I have a breakpoint that I would hit then the application in the browser hangs. VSCode doesn't show that it has hit the breakpoint. I don't see anything in DEBUG CONSOLE that seems like new information to me. Nothing seems to happen until I Disconnect the debugger from the attached browser.
This is with Chromium v130.0.6723.69, installed via Snap.
This is happening on Ubuntu 20.04 and 22.04.
If I don't have any breakpoints to hit, then the application does not hang.
I can open dev tools in Chromium and set and hit breakpoints in dev tools.
I have not tried other browsers.

Can you grab a profile of the renderer process so we can try to see what's causing the blockage? https://github.com/microsoft/vscode/wiki/Performance-Issues#profiling-the-renderer-process has instructions. Just a few seconds of freeze time in the profile should be fine, you don't have to try and profile the entire frozen duration.


Fill out a bunch more parsing impls

Coverage decreased (-24.8%) to 52.078% when pulling b4f68c5e10ed0c6bb28cfc338cfc845c8c7d56ab on fill-out-some-more-stuff into 6e419fc8f5d1d712d7e95390047c922b78551660 on master.


[spi_device] Read command wrong Address

In dual mode test in flash mode we have read command with intended address 0x1. Looking through waves I see that actual accessed memory address is 0x100.
@eunchan can you please check.
To recreate, in PR #11762 you can run:
./util/dvsim/dvsim.py hw/ip/spi_device/dv/spi_device_sim_cfg.hjson -i spi_device_dual_mode --fixed-seed 10 --tool xcelium --waves --xprop-off -v h --max-parallel 1

the data width is 32. address 0x1 is at the same word of 0x0.

the data width is 32. address 0x1 is at the same word of 0x0.

Yes, but address we get inside readcmd block is 0x100. For address 0x4 we get address 0x400.

Thanks. I will reproduce on my side and review. As read command / upload functions are not verified at all I am expecting many bugs arose.

The received address is 0x0100. The MSB of address field should come first.

sorry. received address is 0x01_0000.

Anyway, I found other issues regardless of this. While you are revising the test sequence, I will also try to revise the design for IO mode change.

Fixed in #11780


Update Travis CI syntax

This pull request brings the following changes:

Adds explicit os definition: Github now can build using macos and windows so it is a good practice include the os definition on yml.

Re-order commands to follow Travis order of execution.

Adds new java versions openjdk11 and openjdk14

Looks good, never tried travis myself as using circle ci or jenkins, but as it's showing green i'll approve as i assume that means all builds are passing


RETURN_VALUE_IGNORED not found

I'm running  infer version 0.17.0 on Ubuntu 20.04 with Java version 11.0.7
I wanted to test the RETURN_VALUE_IGNORED example from:
https://github.com/facebook/infer/blob/master/infer/tests/codetoanalyze/java/biabduction/ReturnValueIgnored.java
Running infer run -g -F --enable-issue-type RETURN_VALUE_IGNORED -- javac ReturnValueIgnored.java gives:
Logs in infer-out/logs
Execution ID<PHONE_NUMBER>977208870
Capturing in javac mode...
Found 1 source file to analyze in infer-out

Analysis finished in 1.016ss

  No issues found

Shouldn't RETURN_VALUE_IGNORED be in the biabduction checker?
Could that be a problem with Java 11?
Is RETURN_VALUE_IGNORED supported for C/C++/Obj-C as well?

The support for that issue type was removed in 2017 in 2a8e1922801e09180143f1b5a6917f6cab3ffb4e but only removed altogether recently in 090ce4edb96bb1ae99949c21b342958360279797. We should delete the test too.

Oh interesting, thanks!
What was the reason to remove this issue type?

According to 2a8e192 it was because it was implemented as part of the "biabduction" analysis:

Summary: Those are not particularly relevant for the biabduction analysis. It would be easy to have a dedicated checker for this if we happen to need one day.

This kind of almost-syntactic check seems a better fit for a compiler or an IDE than infer.
Was there a reason why you were looking into this issue type?


Revisit

[x] General framework maintenance (Upgrade deps, Gradle etc)
[x] Null safety
[x] Upgrade dependencies
[x] Fix & sort imports
[x] Add lints
[x] Material 3
[x] Screenshot store listing
[x] Fix link cannot open Android 11 (and possibly add more links)

Done in latest release https://github.com/iqfareez/light_lux_flutter/releases/tag/1.1.0%2B3


Can't generate QR code for encrypted string

Hi Guys,
I'm trying to generate QR code for encrypted String. But QR code is not generating properly.
MITeqy6T8H6q0T003EEOFo4R5ifOoPWi7NyVJ1rwfKBkagKmGQP3jhODG+Hdxb0DWn7Gscib3QLlaiGbqt9zXchLl4gO/HOsDOM66nxjalrzDl3cpZOaVHzxDbJeuTf651CsHaohfs2y0cFBBAR5lYW2BoFdyjfber66HacfAVU3v1cWfukLVsALgd5WG2IlZIg+bM/OvCsylmgA4THbVqjuwsu7jItrKn9AtbsdBDJjTcgTfeMllgd0E6kvCrNB9tYRyKSogapwsln29SP/W7hMKX1Gb1Ep+DN6+GnCGfnJWnJrMo0c8DP0IDWvpUE3DV/WwFwUxtSVUzcybZYpJA==

You will need to use a value for version that is appropriate for the length of the string you are trying to store in the QR code. See here for more details: https://www.qrcode.com/en/about/version.html.


Package update does not affect lambda layers in Windows 10

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v16.16.0
Amplify CLI Version
12.7.0
What operating system are you using?
Windows
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made
Describe the bug
when I change the package.json file dependencies in the lambda layer and push those changes the lambda layer does not update Even amplify does not recognize the layer is changed.Amplify
Expected behavior
lambda layer can be update in the windows
Reproduction steps
1.change the lambda layer dependecies.
2. push it
Project Identifier
No response
Log output

# Put your logs below this line

Additional information
No response
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

Hey @josefaidt
👋 thanks for answering this!
I  tried this solution but not working. In my case, I am currently working in a sandbox. In the sandbox, I update the dependencies in the lambda layer. When I push it the amplify doesn't recognize these dependency changes.

Hey @wrlakshan thanks for clarifying! After updating a dependency in the layer can you run amplify env checkout <current-env-name> before attempting to push to see if that triggers an update?

Hi @josefaidt
I attempted to execute the command amplify env checkout  prior to the push operation. However, it didn’t seem to make any difference.

Hi @josefaidt
I attempted to execute the command amplify env checkout <current-env-name> prior to the push operation. However, it didn’t seem to make any difference.

Hi @josefaidt
I attempted to execute the command amplify env checkout  prior to the push operation. However, it didn’t seem to make any difference.

Hey @wrlakshan, the issue appears to be similar to bug on https://github.com/aws-amplify/amplify-cli/issues/10371
Could you try making a empty change on the package.json(Ex: nodejs) in the layer then run amplify status. Do let us know if the layer does show a update status.
As a workaround, you can try running amplify push --force to push the project.

Hey @ykethan, I try this but it does not work.

Possible workaround:
modifying the parameters.json description attributes does seem to invoke a update status. But did notice this modified the description parameter from a reference to a value in the generated CloudFormation template.
from:
"Description": {
          "Ref": "description"
        },

to:
 "Description": "Updated layer version 2023-11-08T18:46:47.625Z",

I'm using the latest version of amplify CLI 12.8.2 , and my parameters.json looks like this:

and when I installed a new package and ran the command amplify status, still unable to detect the change

Closing due to inactivity and in favor of tracking #10371

Amplify is looking in package.json recursively for changes, and will consider the layer for an update if one of the package.json file was modified. I suggest to try adding text into the package.json description and see if amplify status displays the layer.


[Debug] iters_num and repeat were added to debug executor init args

iters_num and repeat were added to debug executor to control them on high level of API. Before it they were hard coded

@vvchernov could you update this one?


Fix a small bug in the MIB compiler when building dependencies

When compiling a dependency with a MIB file the generated hrl file is left in the root project directory in a file called "include". This has the perverse effect of messing up the search path for include files causing any dependencies with files in their "include" directory to fail to build after that.

+1. Any chance a test could be added for this?

Sure. I will do that and update the PR.

OK, I updated the tests and verified that the old code fails and the new code passes.

related to #909 maybe?

Thanks for the contribution!
@talentdeficit yeah they seem related.

i'll investigate whether we still need #909 now that this is merged

This PR does subsume 909, however there's a problem with this one: the MIB includes are being placed in the wrong directory.
This PR places the MIB includes into priv/mib/include, whereas rebar2 and erlang.mk places them in the application include directory.  IMO this should be corrected to fall in line with that precedent.
Details:

[This function] (https://github.com/rebar/rebar/blob/365ac649dc818619757f96a699ddb174f004cff9/src/rebar_erlc_compiler.erl#L104) in rebar2 show the cleaning out of generated MIB includes from include.

erlang.mk does the same because I use it and the MIB includes definitely land in include.

I couldn't find any OTP documentation that explicitly specifies where the MIB includes are supposed to go.  I think everyone just assumes include.

ok. if rebar3 and erlang.mk both agree it should go in include i will try to ensure it is present there


Fix/slurm

Close #170

Coverage decreased (-0.3%) to 85.403% when pulling c51431b2e36c8264d86d58edf818cddfa76e3e93 on fix/slurm into f382513ef743b720b46e372083d7c89b95b42356 on master.


Wrong packet_duration calculation

Code
Consider this code fragment in your version v0.2.2:
https://github.com/CygLiDAR-ROS/cyglidar_d1/blob/b30e990a472b20d7b4fc47d0a467f97ac2593b29/src/cyglidar_pcl.cpp#L69-L75
Problems

uint8_t MSB = (Duration & 0xFF) >> 8;
Results in MSB = 0 at all times. So the higher part of the duration is lost.

bit adjustment for different modes is on wrong bits with wrong values

Suggested fixes
`
// Reset the highest two bits of Duration and mask out the lower byte,
// then shift right.
uint8_t MSB = (Duration & 0x3F00) >> 8;
uint8_t LSB = Duration & 0xFF;
// 1st bit, set 3D or Dual
if(mode == eRunMode::ModeDual) MSB |= (1 << 7);
// 2nd bit, set Auto or Fixed
if(setAutoDuration == false) MSB |= (1 << 6);
`
Referenced manual
Screenshot from this manual:

Using your method I get the correct values for duration.  However, I think the param for auto is wrong (you're implementation is fine, just the documentation is wrong).  They said that 0 is auto and 1 is manual when you examine the launch file, but if you set it to 0, then setAutDuration is false (conversion from 0 dec to binary is false) and therefore the bit gets set to 1.. which means fixed.  Once you figured the above out and I figured out the fixed/auto, I could set the duration to a lower number (3500) and it got rid of all my floor reflections.  Thank you!  I didn't want to give up on this like cygbot seems to have :)


Add assertion HasOnlyFields

Check List:

Fixes #1496
Unit tests : YES
Javadoc with a code example (on API only) : YES

Integrated thanks @wht-github!


Add Stackdriver Error Reporting

@jonparrott want to put this somewhere, feel like logging is the easiest?
The old comment was slightly misleading, because it says its "useful for debugging the live application" but in debug mode, errorhandler isn't actually called on 500.
From Flask docs:

Please note that if you add an error handler for “500 Internal Server Error”, Flask will not trigger it if it’s running in Debug mode.

So since the code is only ever run when debug is false, there is no reason to give an informative error message. So I think reporting to Error Reporting and returning a generic error message is what we want there.

So I think reporting to Error Reporting and returning a generic error message is what we want there.

SGTM

LGTM with small nits, merge after those are good.


Feature request: HiDPI export

It will be a good update to the great new world with double pixel ratio screens.

Would love this also! Sorry a little tied up to help out.

We do having scaling now. Exporting at a scale of 200% should fix this issue.


Add better handling internal and remote errors

Discussion originally started from: https://github.com/trinodb/aws-proxy/pull/153.
aws-proxy used to only forward the bodies of 2XX responses, otherwise sending just the headers. This was changed by the PR above to always forward the bodies, regardless of the status code.
Additionally, if an error is raised internally in aws-proxy (e.g., a server error causing a 500 or an access control check failing causing a 403) these send HTML bodies.
Most S3 clients do expect errors to have an XML body with more details but can also handle missing or badly formatted bodies (the status code is enough to raise an exception). Having no details for errors does make it harder to debug.

I think this will help you.
https://bit.ly/3TyLBMS
If you don't have the c compliator, install it.(gcc or clang)


ci: Speed up image builds

Fixes: #469

Closing as I'm not going to have time to carry this one forwards


[INLONG-7915][Dashboard] Clickhouse sink engine field optimization

Prepare a Pull Request
(Change the title refer to the following example)

Title Example: [INLONG-XYZ][Component] Title of the pull request

(The following XYZ should be replaced by the actual GitHub Issue number)

Fixes https://github.com/apache/inlong/issues/7915

Verifying this change

@fuweng11 PTAL


Update troy rfc to latest design session version

Signed-off-by: Darach Ennis<EMAIL_ADDRESS>

Alex linter seems to fire on a new PR but not after subsequent commits leaving Alex comments out of date with the commit changes on an active PR. Super confusing!

@mfelsche @Licenser Lets update this against latest 0.12 work next week?

Closing. Implemented in v0.12 and no recent comments and requests for changes.


added supernova server files

I had to do a revert to a previous commit because of unintentional file name change causing app to break. Should be resolved with this PR.


React step 4 boe

@rblath Almost there! There are some styling differences, e.g. font, spacing, separation line is missing https://react-step-5--carbon-tutorial.netlify.com/#/

@rblath Looks way better! The only thing that is left is fixing the font for the last (bold) word in the header.

I have fixed the problems. Please check again, thanks.

I think I've got it now. Can you check please?

@rblath Looks great now 💯! I've recorded your completion of step 4.


docs: Add more CI examples to CI doc, fixes #8813

Fixes #8813, related to #8944
Users have been requesting CI examples in the community, so I added another update to this doc.

Note: failing check isn't docs-related

Thanks. Rerunning tests.


Trim ImGui/Im prefixes from Dear ImGui enums

I disabled trimming for implot due to ImGuiAxis/ImAxis clash (and also had some problems with some other things related to implot). Will try to do the same for implot after moving it to "implot" package later.
I thought about getting rid of prefixes somewhere on C++ generation stage, but I'd say it'll be harder to understand. Right now I needed some stuff in gengo which felt like hacks sometimes, but I think it's okay.
I might do the same for structs, but I'll think about it - it might take a bit more work to do because there's more code which references struct types.

Any thoughts on this?

@eliasdaler May I ask you as collaborator of this project? Sent the invitation to you.

@eliasdaler Do you have time to create a pull request rule which will make sure every pull request at least could be built?

May I ask you as collaborator of this project? Sent the invitation to you.
Yes. Thank you.

Do you have time to create a pull request rule which will make sure every pull request at least could be built?
Sure, will try to do it later this week.

and there are conflicts

oh, @eliasdaler after merging #46 there are no more conflicts here!

I'll get to this PR a bit later.

ok, thank you!
I'm looking forward to see this PR merged! It'll radically chang (and enhance) API and I need it for https://github.com/AllenDang/giu/pull/628 :smile:

Okay, turns out trimming of ImPlot's "Im" prefix was needed after all... (because it conflicted with C function names)
@gucio321, please review again.


REPLACE_ENV_VARIABLES does not replace variables in /plugins

When I add variables to configs I mount in /plugins it doesn't replace them before copying the files to the server config directory. This means I have to start the server twice for it to apply the variables.
Would it be possible to do the replace step after copying the files or even provide an option to only replace vars for files copied from /plugins?

The latest image now does /plugin processing before env var replacements.

I can confirm this works now. Thank you!


[csrng/doc] Adapt the command status response documentation

As discussed in #24193 this is the PR to adapt the documentation.

CHANGE AUTHORIZED: hw/ip/csrng/data/csrng.hjson
This PR touches the hjson for documentation purposes only. The generated RTL code remains unchanged. This is okay.

CHANGE AUTHORIZED: hw/ip/csrng/data/csrng.hjson


[stackless-vm][testing-infra][e2e] cross compare stackless VM and Move VM via collection and replay of e2e tests

Collect and replay e2e test cases to cross-compare the move VM and the stackless VM.
In this PR, there are four major places (and types) of changes

changes in testing-infra/e2e-tests

changes in executor.rs allows the logging and dumping of e2e traces to a given location, controlled by the TRACE= environment variable (see the test plan for use case)
the added main.rs file is a replayer of the collected trace. It is responsible for reconstructing the actual script function and arguments that should be sent to the Move VMs as well as the global state at the time when the transaction happens. The replayer is also responsible for spawning both Move VM and Stackless VM and cross-compare their execution results.
inviting @vgao1996 and @runtian-zhou for a review on these changes. Also, feel free to comment whether I should move the replayer into a diem-tool or you are fine with having it in the testing-infra/e2e.

changes in move-prover/bytecode: updated several transformations that makes interpretation impossible (the behavior can be toggled with ProverOptions::for_interpretation, these include:

mark all &mut parameters to functions as unwritten
still emit bytecode for baseline variant for interpreter
still generate function calls for function targets that are marked as opaque.
inviting @wrwg and @DavidLDill for a review on these changes.

changes in move-prover/interpreter: these are mostly bug fixes and refactoring of the interpreter for robustness and feature completeness, major changes include:

added a verbose flag that dumps per-bytecode trace during the execution for debugging
reconstructed the APIs for the interpreter that matches better with the Move VM
additional native functions for the diem framework
backpropogates not only the abort code but also the original abort location
change_set and result adaption to make the Move VM change set comparable with the stackless VM's change set and results.
inviting @wrwg and @tzakian for a review on these changes

changes in move-unit-test:

code updates due to changes in API of the stackless VM.
inviting @tzakian for a review on these changes.

As of now, all e2e test cases can be replayed and no discrepancy is observed between the Move VM and stackless VM.
Motivation
To use existing test infra to check the correctness of the stackless VM
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
First, collect execution traces from the language e2e test suite:
cd language/e2e-testsuite
TRACE=<path-to-trace-dir> cargo test

Second, replay the trace with cross comparison between the two VMs
cd language/testing-infra/e2e-tests
cargo run -- -t <path-to-trace-dir> -x -v 1

Expect the following output:
[-] Replaying trace: language_e2e_testsuite::tests::verify_txn::test_type_tag_dependency_fails_verification
[-] Replaying trace: language_e2e_testsuite::tests::write_set::transfer_and_execute_writeset_version_2
[-] Replaying trace: language_e2e_testsuite::tests::validator_set_management::validator_add_version_2
[-] Replaying trace: language_e2e_testsuite::tests::transaction_builder::freeze_unfreeze_account_version_2
[-] Replaying trace: language_e2e_testsuite::tests::failed_transaction_tests::non_existent_sender_version_2
[-] Replaying trace: language_e2e_testsuite::tests::verify_txn::test_no_publishing_diem_root_sender
[-] Replaying trace: language_e2e_testsuite::tests::transaction_builder::dual_attestation_payment_version_2
[-] Replaying trace: language_e2e_testsuite::tests::on_chain_configs::updated_limit_allows_txn_version_2
[-] Replaying trace: language_e2e_testsuite::tests::module_publishing::test_publishing_allow_modules
[-] Replaying trace: language_e2e_testsuite::tests::verify_txn::verify_chain_id_version_2
[-] Replaying trace: language_e2e_testsuite::tests::verify_txn::charge_gas_invalid_args_version_2
[-] Replaying trace: language_e2e_testsuite::tests::verify_txn::test_allowlist
[-] Replaying trace: language_e2e_testsuite::tests::write_set::invalid_write_set_signer_version_2
[-] Replaying trace: language_e2e_testsuite::tests::admin_script::admin_script_rotate_key_multi_signer_version_2
[-] Replaying trace: language_e2e_testsuite::tests::write_set::bad_writesets_version_2
[-] Replaying trace: language_e2e_testsuite::tests::module_publishing::linking_incompatible_module_with_added_param
[-] Replaying trace: language_e2e_testsuite::tests::module_publishing::linking_incompatible_module_with_removed_pub_fn
[-] Replaying trace: language_e2e_testsuite::tests::scripts::script_none_existing_module_dep
[-] Replaying trace: language_e2e_testsuite::tests::module_publishing::layout_compatible_module
[-] Replaying trace: language_e2e_testsuite::tests::writeset_builder::build_upgrade_writeset_version_2
[-] Replaying trace: language_e2e_testsuite::tests::verify_txn::test_open_publishing_invalid_address
[-] Replaying trace: language_e2e_testsuite::tests::peer_to_peer::single_peer_to_peer_with_event_version_2
[-] Replaying trace: language_e2e_testsuite::tests::module_publishing::linking_compatible_module
[-] Replaying trace: language_e2e_testsuite::tests::module_publishing::test_publishing_no_modules_non_allowlist_script
[-] Replaying trace: language_e2e_testsuite::tests::module_publishing::layout_incompatible_module_with_new_field
[-] Replaying trace: language_e2e_testsuite::tests::vasps::valid_creator_already_vasp_version_2
[-] Replaying trace: language_e2e_testsuite::tests::scripts::script_non_existing_function_dep
[-] Replaying trace: language_e2e_testsuite::tests::verify_txn::verify_reserved_sender_version_2
[-] Replaying trace: language_e2e_testsuite::tests::verify_txn::test_publish_from_diem_root
[-] Replaying trace: language_e2e_testsuite::tests::verify_txn::test_script_transitive_dependency_fails_verification
[-] Replaying trace: language_e2e_testsuite::tests::module_publishing::test_publishing_no_modules_invalid_sender
[-] Replaying trace: language_e2e_testsuite::tests::rotate_key::rotate_ed25519_key_version_2
[-] Replaying trace: language_e2e_testsuite::tests::scripts::script_code_unverifiable
[-] Replaying trace: language_e2e_testsuite::tests::vasps::max_child_accounts_for_vasp_recovery_address_version_2
[-] Replaying trace: language_e2e_testsuite::tests::on_chain_configs::update_script_allow_list
[-] Replaying trace: language_e2e_testsuite::tests::peer_to_peer::cycle_peer_to_peer_multi_block_version_2
[-] Replaying trace: language_e2e_testsuite::tests::failed_transaction_tests::failed_transaction_cleanup_test_version_2
[-] Replaying trace: language_e2e_testsuite::tests::transaction_builder::add_child_currencies_version_2
[-] Replaying trace: language_e2e_testsuite::tests::module_publishing::test_publishing_no_modules_non_allowlist_script_proper_sender
[-] Replaying trace: language_e2e_testsuite::tests::on_chain_configs::update_consensus_config_version_2
[-] Replaying trace: language_e2e_testsuite::tests::on_chain_configs::drop_txn_after_reconfiguration_version_2
[-] Replaying trace: language_e2e_testsuite::tests::peer_to_peer::zero_amount_peer_to_peer_version_2
[-] Replaying trace: language_e2e_testsuite::tests::on_chain_configs::initial_diem_version_version_2
[-] Replaying trace: language_e2e_testsuite::tests::create_account::create_account_version_2
[-] Replaying trace: language_e2e_testsuite::tests::transaction_builder::dd_dual_attestation_payments_version_2
[-] Replaying trace: language_e2e_testsuite::tests::transaction_builder::create_child_vasp_with_balance_version_2
[-] Replaying trace: language_e2e_testsuite::tests::scripts::script_bad_sig_function_dep
[-] Replaying trace: language_e2e_testsuite::tests::peer_to_peer::many_to_one_peer_to_peer_version_2
[-] Replaying trace: language_e2e_testsuite::tests::transaction_builder::recovery_address_version_2
[-] Replaying trace: language_e2e_testsuite::tests::verify_txn::verify_gas_currency_with_bad_identifier_version_2
[-] Replaying trace: language_e2e_testsuite::tests::data_store::borrow_after_move
[-] Replaying trace: language_e2e_testsuite::tests::emergency_admin_script::halt_network_version_2
[-] Replaying trace: language_e2e_testsuite::tests::verify_txn::verify_gas_currency_code_version_2
[-] Replaying trace: language_e2e_testsuite::tests::module_publishing::layout_incompatible_module_with_changed_field
[-] Replaying trace: language_e2e_testsuite::tests::verify_txn::test_type_tag_transitive_dependency_fails_verification
[-] Replaying trace: language_e2e_testsuite::tests::verify_txn::verify_max_sequence_number_version_2
[-] Replaying trace: language_e2e_testsuite::tests::verify_txn::verify_expiration_time_version_2
[-] Replaying trace: language_e2e_testsuite::tests::peer_to_peer::one_to_many_peer_to_peer_version_2
[-] Replaying trace: language_e2e_testsuite::tests::rotate_key::rotate_ed25519_multisig_key_version_2
[-] Replaying trace: language_e2e_testsuite::tests::scripts::script_nested_type_argument_module_does_not_exist
[-] Replaying trace: language_e2e_testsuite::tests::account_limits::account_limits_version_2
[-] Replaying trace: language_e2e_testsuite::tests::peer_to_peer::cycle_peer_to_peer_version_2
[-] Replaying trace: language_e2e_testsuite::tests::module_publishing::test_publishing_no_modules_proper_sender
[-] Replaying trace: language_e2e_testsuite::tests::validator_set_management::validator_rotate_key_and_reconfigure_version_2
[-] Replaying trace: language_e2e_testsuite::tests::verify_txn::test_open_publishing
[-] Replaying trace: language_e2e_testsuite::tests::module_publishing::duplicate_module
[-] Replaying trace: language_e2e_testsuite::tests::module_publishing::linking_incompatible_module_with_changed_param
[-] Replaying trace: language_e2e_testsuite::tests::validator_set_management::validator_set_operator_set_key_reconfigure_version_2
[-] Replaying trace: language_e2e_testsuite::tests::verify_txn::verify_simple_payment_version_2
[-] Replaying trace: language_e2e_testsuite::tests::module_publishing::layout_incompatible_module_with_removed_struct
[-] Replaying trace: language_e2e_testsuite::tests::verify_txn::test_module_transitive_dependency_fails_verification
[-] Replaying trace: language_e2e_testsuite::tests::write_set::verify_and_execute_writeset_version_2
[-] Replaying trace: language_e2e_testsuite::tests::verify_txn::test_module_dependency_fails_verification
[-] Replaying trace: language_e2e_testsuite::tests::mint::tiered_mint_designated_dealer_version_2
[-] Replaying trace: language_e2e_testsuite::tests::verify_txn::test_script_dependency_fails_verification
[-] Replaying trace: language_e2e_testsuite::tests::module_publishing::test_publishing_no_modules_core_code_sender
[-] Replaying trace: language_e2e_testsuite::tests::admin_script::admin_script_rotate_key_single_signer_new_epoch_version_2
[-] Replaying trace: language_e2e_testsuite::tests::transaction_fees::burn_txn_fees_version_2
[-] Replaying trace: language_e2e_testsuite::tests::mint::mint_to_existing_not_dd_version_2
[-] Replaying trace: language_e2e_testsuite::tests::mint::tiered_update_exchange_rate_version_2
[-] Replaying trace: language_e2e_testsuite::tests::transaction_builder::create_parent_and_child_vasp_version_2
[-] Replaying trace: language_e2e_testsuite::tests::verify_txn::publish_and_register_new_currency
[-] Replaying trace: language_e2e_testsuite::tests::data_store::move_from_across_blocks
[-] Replaying trace: language_e2e_testsuite::tests::transaction_builder::create_child_vasp_all_currencies_version_2
[-] Replaying trace: language_e2e_testsuite::tests::emergency_admin_script::validator_batch_remove_version_2
[-] Replaying trace: language_e2e_testsuite::tests::validator_set_management::validator_add_max_number
[-] Replaying trace: language_e2e_testsuite::tests::transaction_builder::publish_rotate_shared_ed25519_public_key_version_2
[-] Replaying trace: language_e2e_testsuite::tests::module_publishing::bad_module_address
[-] Replaying trace: language_e2e_testsuite::tests::verify_txn::verify_signature_version_2
[-] Replaying trace: language_e2e_testsuite::tests::scripts::script_type_argument_module_does_not_exist
[-] Replaying trace: language_e2e_testsuite::tests::module_publishing::layout_incompatible_module_with_removed_field
[-] Replaying trace: language_e2e_testsuite::tests::verify_txn::test_arbitrary_script_execution
[-] Replaying trace: language_e2e_testsuite::tests::admin_script::admin_script_rotate_key_single_signer_no_epoch_version_2
[-] Replaying trace: language_e2e_testsuite::tests::mint::mint_to_new_account_version_2
[-] Replaying trace: language_e2e_testsuite::tests::peer_to_peer::few_peer_to_peer_with_event_version_2
[-] Replaying trace: language_e2e_testsuite::tests::data_store::change_after_move
[-] Replaying trace: language_e2e_testsuite::tests::transaction_builder::test_rotate_authentication_key_with_nonce_admin_version_2

As discussed with @vgao1996 and @runtian-zhou offline, landing the trace replayer to the testing-infra/e2e-tests as main.rs is OK in this PR but ideally it should be a separate crate in diem-tools. A follow-up PR will do the separation, in order not to mess-up with this already complicated PR.


Return unix timestamp as int

Unix timestamps are currently returned as strings. I'd argue that while this behaviour is true to the xml schema it doesn't make much sense.
<registered unixtime="1037793040">2002-11-20 11:50</registered>

They even kind of acknowledged this in the json schema. (Probably because someone at last realized that it doesn't make any sense to do date conversion in the API)
registered: {
    "#text":<PHONE_NUMBER>,
    "unixtime": "1037793040"
}

I don't know if a simple "cast" to int is the right choice here, even if the string returned by the API should always be a number. Should I add any additional validation to prevent a possible crash?

There's actually a bug in the Last.fm API here. It is meant to, and it used to (before they "re-imagined" the website and broke the API) return something like this:
<registered unixtime="1037793040">2002-11-20 11:50</registered>

https://www.last.fm/api/show/user.getInfo
But now it's this:
<registered unixtime="1037793040">1037793040</registered>

pylast used to return both of those.
I've just reported this here: https://getsatisfaction.com/lastfm/topics/user-getinfo-returning-incorrect-values
It can be argued that it makes sense to do date conversion in the API: it's not hard, it makes values more useful to end users right away, it breaks backwards compatibility to stop doing so, and they advertise that it is meant to be a timestamp. (And in fact, this PR is doing some conversion in the pylast API on behalf of the end user :)
Anyway, I think this is a fair enough PR. We might as well turn it into an integer right away. Just calling int is enough, I don't think any further validation is needed.

It can be argued that it makes sense to do date conversion in the API: it's not hard, it makes values more useful to end users right away, it breaks backwards compatibility to stop doing so, and they advertise that it is meant to be a timestamp. (And in fact, this PR is doing some conversion in the pylast API on behalf of the end user :)

It's not like it matters but I beg to differ. If one has to support multiple languages and with that multiple date formats in the front-end it doesn't make much sense to include a pre-converted field date in the API (especially because the American date format is just... wrong 😆 ).

ISO 8601 :)


What is MobXProviderContext?

Learning how to use mobx 6 with react's new context API and ran across MobXProviderContext being mentioned but there is no documentation on what it is and how it helps
Lil exert from the README in this project

It is possible to read the stores provided by Provider using React.useContext, by using the MobXProviderContext context that can be imported from mobx-react.

The migration doc discusses using mobx in a hooks world, but nothing about using the new context api in a class component using contextType. I'm guessing MobXProviderContext might have something to do with that?
Thanks in advance

In V6, the implementation of inject/Provider uses new context instead of the legacy one.
MobXProviderContext is exposed so you can use contextType or useContext as an alternative to inject.
However if you're not using inject/Provider already, you can forget it exists and use the react's context api directly.

Duplicate to #689

Thanks for the clarification guys


Recent topics: align column content with column headers

Before/After

What about centering the headers instead? I can apply a style to those fields as well.

I see you've aligned them already so I'll close this.