Postfix service not starting with 'puppet apply'

resolution_fixed   |    by<EMAIL_ADDRESS>
Running 'puppet apply' on accessdev is reporting the following error:
Error: Could not start Service[postfix]: Execution of '/sbin/service postfix start' returned 1:
Error: /Stage[main]/Postfix/Service[postfix]/ensure: change from stopped to running failed: Could not start Service[postfix]: Execution of '/sbin/service postfix start' returned 1:

Issue migrated from trac:88 at 2024-01-31 17:32:15 +1100

<EMAIL_ADDRESS>commented

saw562@accessdev puppet $ sudo service postfix status
master dead but pid file exists

<EMAIL_ADDRESS>commented

What output do you get from:
$ sudo service postfix status

<EMAIL_ADDRESS>commented

$ sudo stat /proc/32432/exe

<EMAIL_ADDRESS>commented

Sorry, that was my workstation. Similar results for accessdev:
saw562@accessdev ~ $ sudo cat /var/spool/postfix/pid/master.pid
[sudo] password for saw562:
                           32432
saw562@accessdev ~ $ ps 32432
  PID TTY      STAT   TIME COMMAND
32432 ?        Ss     0:14 /usr/libexec/postfix/master

<EMAIL_ADDRESS>commented

swales@walesnix accessdev $ sudo cat /var/spool/postfix/pid/master.pid
                            1365

swales@walesnix accessdev $ ps 1365
  PID TTY      STAT   TIME COMMAND
 1365 ?        Ss     0:05 /usr/lib/postfix/master

<EMAIL_ADDRESS>commented

$ sudo cat /var/spool/postfix/pid/master.pid

<EMAIL_ADDRESS>commented

Actually newline not the problem, but they aren't allowing for the fact that the service executable having been replaced.
$ cd /etc/rc.d/init.d
$ sudo cp -p functions functions.centos

Then apply the following patch:
--- functions.centos	2014-02-20 21:44:13.000000000 +1100
+++ functions	2014-03-13 12:40:30.374003358 +1100
@@ -66,7 +66,7 @@
 }

 __readlink() {
-    ls -bl "$@" 2>/dev/null| awk '{ print $NF }'
+    ls -bl "$@" 2>/dev/null| sed -e 's/\\ (deleted)$//' | awk '{ print $NF }'
 }

 __fgrep() {

<EMAIL_ADDRESS>commented

Just for reference, this has already been reported upstream:
https://bugzilla.redhat.com/show_bug.cgi?id=1067686
https://bugzilla.redhat.com/show_bug.cgi?id=1067696

<EMAIL_ADDRESS>commented

I see what the problem is, RedHat made a change to their initscripts as part of RHBA-2014:0191-1 and they've introduced a bug.  Their code tries to compare a string without removing the trailing new line first.  I'll give you a patch in a minute.
btw, I take it you applied some updates recently?

<EMAIL_ADDRESS>commented

Thanks Chris, is this an accessdev-specific change or will it be handled by the NCI puppet?

No worries.  It's just a temporary workaround.  In fact, you'll only see the problem when the "postfix" RPM is updated (as occurred in this case) since that's the only time the executable would be replaced.  So you could restart the service now, and then restore the original version of the initscript and everything should work fine.

Yeah, I've been trying to clean up the 'puppet apply' output a little, so it's easier to see what's actually changed. When packages are managed using Pip the check to see if the package is installed is case-sensitive, d78b145 fixes this for the python packages

OK, I actually meant yum updates must have been installed.

<EMAIL_ADDRESS>commented

Thanks Chris, is this an accessdev-specific change or will it be handled by the NCI puppet?

btw, I take it you applied some updates recently?

Yeah, I've been trying to clean up the 'puppet apply' output a little, so it's easier to see what's actually changed. When packages are managed using Pip the check to see if the package is installed is case-sensitive, d78b145 fixes this for the python packages

<EMAIL_ADDRESS>changed status from new to closed

<EMAIL_ADDRESS>changed resolution from `` to fixed

<EMAIL_ADDRESS>commented

Issue resolved with
sudo service postfix stop
sudo service postfix restart

<EMAIL_ADDRESS>commented

Yum updates are being done by a weekly cron job

<EMAIL_ADDRESS>removed milestone (was Future)

<EMAIL_ADDRESS>commented

Milestone Future deleted


[Refactor] VoteNet refactor

Modified backbone feature extraction in order that ImVoteNet can directly use VoteHead.

Made sure the performance was unaffected


Feat: allow keeping homedir

Greetings,
This is a change proposal coming from my forked version which I needed it to handle user deletion but keeping their home directories intact for those who were configured like so.

Hi, thanks for the PR!
I renamed remove_homedir to remove to keep in sync with ansible's options for better understanding and I added the option to still just list the usernames for backward compatibility.


Create parent directories if config dir doesn't exist (fixes #251)

This fixes #251, though I am still confused as to why the config dir might not exist.

I figured I'd make myself useful :P


Further clean up helper.py

https://github.com/ryansurf/cli-surf/pull/85#discussion_r1704734292
Thanks @K-dash for the suggestions, these are great ideas

I'm going to start working on this

can I take a crack at this?


How can I custom the magento2.conf nginx

I am trying without success to tweak te nginx.conf used in a Magento2 project. How can this be done? I have modified the magento2.conf in images/nginx/context/etc/nginx/available.d and warden env up --force-recreate but nginx conf is not changing. How can I achieve this. I am runing a Magento2 with storeviews in subdirectories and I am needing to introduce some locations in nginx to make them work.
Any Help? Any Clue? I have not too much experience with docker / warden. Any help would be much appreciated.

@oreales I just did this recently... It's pretty easy to do...
Step 1: Update warden-env.yml
.warden/warden-env.yml
services:
    nginx:
        volumes:
            - ./.warden/nginx/nginx.conf:/etc/nginx/available.d/magento2.conf

Next add your new nginx.conf
.warden/nginx/nginx.conf
Will need to spin down the warden container and spin it back up for the changes to take effect.

thx a lot. It is working like a charms. Now I am trying to make the nginx configuration to work with a magento2 with storeviews in subdirectories, but everypage returns a 404 except home. But well, that is another question. Thanks for your solution.

@oreales see https://github.com/davidalger/warden/issues/231.
This solution worked for me.


RAW-images are transferred with image/jpeg MIME type.

What Operating system and version is LibrePhotos running on:
Debian
What architecture is LibrePhotos running on:
x64
How is LibrePhotos installed:
Docker
How is your picture library mounted on the host (or in the virtual machine):
Local file system (ext4)
Description of issue:
RAW-images are transferred with image/jpeg MIME type, so it's impossible to directly download original file.

This is correct and expected behavior. You only see a thumbnail of your image for compatibility reasons in the browser and not the file itself. The feature #198 is implemented, but I hadn't had the time to build a new frontend image and push it to docker hub.


App catalog entry readme section shows horizontal scroll bar placeholder

With a mouse attached, there is this white bar in the bottom of the README section:

Seen in Chrome

Guess I created a duplicate of https://github.com/giantswarm/roadmap/issues/1000 , right?

Also fixed by https://github.com/giantswarm/happa/pull/3736 🙂


Security issue [CVE-2022-2421] CWE-89 - Score 10.0

Describe the bug
Security Issue (the same one was resolved in on 'socket.io' v4.5.4 - here)
The same critical vulnerability mentioned above is flagged when scanning the @socket.io/redis-emitter package (due to it's dependency on socket.io-parser~4.0.4).
Would it be possible to cut another minor/patch v4 version that pins the socket.io-parser to "~4.2.1" to mitigate this?

This should be fixed in latest version: https://github.com/socketio/socket.io-redis-emitter/blob/bfefbdefd963b59279b7f55673a88296a660f7d8/package.json#L24
Thanks for the heads-up!


Create Chart from data in Firebase db

Hi.
I'm trying to create a PieChart from my data stored in Firebase DB. My probem is that the legend contains only the first element of the array. If i put the example code in ViewDidLoad (without any observer) all works good. How can I refresh legend to be regenerated?
 firebase.observeEventType(.Value, withBlock: { snapshot in
            for item in snapshot.children {
......
            }
   self.setChart(self.answers, values: self.counts)

Make sure this change is happening on the main thread.

Call notifyDataSetChanged to trigger rending of the chart for new data.

notifyDataSetChanged solved!!! Thanks Sir :)


#210 : Allow list in Measure function

support the 1, 2 requests from the issue but not a empty Measure() object.
updates repr() test for Measure object

Thanks for the PR @arcturusannamalai.
I wouldn't say not meeting point 3 is important at the moment. Actually, it is desirable, as I think we have to keep consistency between the language and the CircuitBuilder.
@elenbaasc @juanboschero I think we have to be more specific about this issue. I think the idea would be that, as well as you can use SGMQ (Single Gate Multiple Qubit) notation in the language, you should also be able to use it in the CircuitBuilder. But that doesn't mean that the Measure IR node can have multiple qubits (which is what is being done in this PR). I think that would complicate the work on the rest of the compiler passes (imagine treating a measure q[1, 3, 5] as a single node instead of as 3 separate nodes, in terms of moving instructions around, dependencies with other instructions and so on...).
@arcturusannamalai Is the paragraph above clear to you? In OpenSquirrel, we can build a circuit 1) using the CircuitBuilder, and 2) from a cQASM string. For both paths, we end up creating the same types (nodes in an IR, Intermediate Representation, structure). In this case a Measure instruction type. At the moment, when we build a Measure instruction from a cQASM string, and that instruction uses SGMQ (Single Gate Multiple Qubit) notation, we create as many instructions as qubits are used. For the CircuitBuilder path, we don't have the option of using SGMQ (that's what this issue would like to add). But the Measure IR node should remain the same (a type receiving a single qubit).

So you need "Allow measure all functionality when user does not specify a qubit, i.e Measure() performs a measure all". We can add that perhaps. But seems like there is more requirements beyond that.

So you need "Allow measure all functionality when user does not specify a qubit, i.e Measure() performs a measure all". We can add that perhaps. But seems like there is more requirements beyond that.

We will add a measure instruction without arguments at some point. But the problem with this PR is other, in my opinion. I don't think a Measure IR node should have multiple qubits.


[x] Post Processing API
[x] Tonemapping
[x] Kawase Bloom

yAy


Missing styling for Pressable component

Current behavior
In one of my projects, since version 0.3.0 of react-native-a11y, a number of styling attributes no longer work, such as border-radius, border-color, etc. I created a project to replicate the issue. In my example I used the Pressable component and as soon as I update the package from 0.2.1 to 0.3.0 (or even 0.4.5), the styling of the borders disappeared.
Expected behavior
The styling attributes such as border-radius and border-color should work consistently across different versions of the package. Upgrading the package should not cause the styles to disappear.
Steps to Reproduce

Use version 0.2.1 of react-native-a11y
Add border styling to a pressable component
Upgrade to version 0.3.0 or above
Rebuild the app and the styling will be gone

Context (Environment)

React Native version: 0.73.7
react-native-a11y version: 0.3.0 and above (for bug)
Platform(s): Android
Device info: Google Pixel 4

Detailed Description
Sinsce upgrading to version 0.3.0 of react-native-a11y, specific styling properties like border-radius and border-color are no longer being applied to the Pressable component. This issue persists even with the latest version 0.4.5. It seems like there might have been changes in the package that affect how styles are processed or applied.
Link to my project: https://github.com/RickVellingaa/a11y-repro
This project has 3 different branches with the different react-native-a11y versions.

Hello @RickVellingaa,
Thank you a lot for publishing the issue. Unfortunately, I don't have project to test this package thoroughly, and I am really sorry that you came across with such expiriense. I really appreciate that you make such repport and provide the sample app, you are awesome)
I will check the problems with styles asap, but this package requires a lot of updates.
FYI:
In honest, even react-native-a11y is ok to use kit, but I would recomend to check a separate package https://github.com/ArturKalach/react-native-external-keyboard, there are additional features (TextInput focus) and it has better API, additionaly it doesn't require additional configuration. I am going to add new features to react-native-external-keyboard firslty.

Hello @RickVellingaa,
I found a problem and will publish a fix soon.  The problem appeared becouse of wrong component extending in Android.

Hello @ArturKalach ,
Sorry for waiting, there were some problems with NewArch.
Issue has been fixed and added to the 0.4.6 version for both arch.

Thanks for the help and quick response @ArturKalach! Greatly appreciated 😄

There is a lot of work and many things that can be done. Your well-written issue has helped me greatly with this. If you could provide any feedback or ideas, it would be greatly appreciated.
If there aren't any comments or problems, I will close the issue a little bit later.

Hey @ArturKalach, Just tested within my project and everything seems to be working without further issues or bugs. Thanks a lot for the quick response. The issue can be closed!


docs: fix typos

Just caught a couple of small typos while browsing the documentation, I believe the meaning of everything is still conveyed as intended as it's just single words.

Coverage decreased (-0.02%) to 84.853% when pulling 43b3d40b8c38b1571da75af86b5088be96cccec2 on hexjelly:fix-doc-typos into 16c693a6dbd702d7e1b32acda0923af01af36c5b on kbknapp:master.

Awesome, thanks for catching and fixing all these! :+1:
@homu r+

:pushpin: Commit 43b3d40 has been approved by kbknapp

:hourglass: Testing commit 43b3d40 with merge 3803b94...

:sunny: Test successful - status

:tada: Happy Rust Doc day :tada:

Totally missed one thing, but I'm on Windows and not able to build the project to check if this fixes the docs for it or not: group.rs line 55/56. The second example's formatting is messed up, and I think it's because there should be a empty doc comment line between 55 and 56? Not really warranting an own issue or a PR, specially since I'm not 100% sure :)


logged_in issue [Windows]

So basically when the user closes their tab or leaves the game, it doesn't update in the database logged_in so the next time the user logs in they will get Maximum Logged in Attempts Error.

Let me know if this works...In TCP.rb find the line while (data = connection.gets("\0"))
below that add the following:
				if data.length == 0
					if @parent.game_sys.iglooMap.has_key?(client.ID)
						@parent.game_sys.iglooMap.delete(client.ID)
					end
					if client.logged_in.to_bool == true
						@parent.mysql.updateLoggedIn(0, client.username)
					end
					client.handleBuddyOffline
					client.removePlayerFromRoom
					self.handleRemoveClient(connection)
				end

Unfortunately, the fix did not work.

May as well close this since it can't be fixed lol


Never send empty frames

After the refactoring it is possible that empty stream frames are sent. We should not do that.
Empty stream frames are allowed if the FIN bit is set.

546ba27013a6045f0dbfc40eb0f7912edf111255 adds an error when this happens.


[BEAM-1454] Correcting the name _append_trailing_newlines

R: @robertwb

Changes Unknown when pulling 1677e10277fbdd8fabcfea8765646242b1be9019 on aaltay:fa into ** on apache:master**.

LGTM. Wonder how this slipped through...


Added a python implementation of the Knapsack problem

Added a knapsack problem implemented in python.
Also according to issue #16

Feel free to reopen as soon you fix it.


Do not delete manually defined definite barriers below WCT observations

If a barrier is defined in misc_barriers_definite, it is safe to assume that we want it to be a barrier regardless of whether there are fish observations upstream. Do not delete features downstream of WCT observations from bcfishpass.definitebarriers_wct.
For current work for CWF WCRPs, above fix is sufficent.  However, old/erroneous observations will continue to throw off the model in other watersheds if we use them to override all definite barriers as per FPTWG model. QA of the observation data is probably manageable (but still significant work) for salmon/anadromous species - but for resident species this may be a significant challenge.

Current data model does not explicitly link from definitebarriers_wct back to misc_barriers_definite.
Rather than messing with ids, make measure/blkey the pk in the source table and standardize barrier types to allow for easy deletion via barrier_type = MISC


feat: Support parsing of SQL code blocks in Markdown files

Closes https://github.com/tconbeer/sqlfmt/issues/593
There are two caveats that would be good to consider:

Because we parse to AST -> rebuild from AST, we can actually lose some trivial whitespace characters. mistletoe keeps all the important whitespace, but can toss out some unnecessary whitespace, such as trailing whitespace or double newlines. A good example is in the README.md of this very repo:

 ~/sqlfmt
❯ poetry run sqlfmt README.md
1 file formatted.
0 files left unchanged.
README.md formatted.

 ~/sqlfmt
❯ git diff
diff --git a/README.md b/README.md
index 7d292f9..5a3f457 100755
--- a/README.md
+++ b/README.md
@@ -9,7 +9,7 @@

 sqlfmt formats your dbt SQL files so you don't have to. It is similar in nature to black, gofmt,
-and rustfmt (but for SQL).
+and rustfmt (but for SQL).

 1. **sqlfmt promotes collaboration.** An auto-formatter makes it easier to collaborate with your team and solicit contributions from new people. You will never have to mention (or argue about) code style in code reviews again.
 2. **sqlfmt is fast.** Forget about formatting your code, and spend your time on business logic instead. sqlfmt processes hundreds of files per second and only operates on files that have changed since the last run.
@@ -138,7 +138,6 @@ Config for other integrations is detailed in the docs linked below:
 - [SQLFluff](https://docs.sqlfmt.com/integrations/sqlfluff)
 - [VSCode](https://docs.sqlfmt.com/integrations/vs-code)

-
 ## The sqlfmt style
 The only thing you can configure with sqlfmt is the desired line length of the formatted file. You can do this with the `--line-length` or `-l` options. The default is 88.

I think this is acceptable since it does not affect readability and should not affect output (i.e. when it's rendered to HTML).

Nested sql blocks are not formatted. I think this is acceptable. See example:

``````markdown

# Hello

```sql
SELECT 1 -- this is not formatted
```

``````

Thank you for this! I'm mostly away from my computer this week but I'll try to review next week.

@michael-the1 Sorry I dropped the ball on this. I'd love to get this finalized. Looks like there are quite a few failing tests and lints. Do you want to work through those? Let me know if you get stuck.

@tconbeer Life can get busy which I totally understand.
The reason the tests are failing is because mistletoe is not installed in the test workflows. Should I add it to the dev or test group in pyproject.toml?

Ah, I see not that in the workflow, the dependencies are installed with poetry install --sync --no-interaction -E jinjafmt --only main,test, so it needs to be in the test group instead.

@tconbeer I think I fixed all issues, but with two notes:

mypy was giving some errors due importing mistletoe.

mypy --disallow-any-unimported will fail with the new mistletoe import. I removed the option from the Makefile.
I also set ignore-missing-imports for mistletoe (see docs). The alternative is to change the type hints to Any and work from there, but it's not my preference since we'd change the code and hurt readability just to wrangle with mypy.

The code coverage check was failing, but I think it's related to a repository setting - something with the CC_TEST_REPORTER_ID env variable not being set (see workflow logs)


Move data to s3

Which version of the AzCopy was used?
10.4.3
Note: The version is visible when running AzCopy without any argument
Which platform are you using? (ex: Windows, Mac, Linux)
Linux
What command did you run?
azcopy copy "https://xxx.blob.core.windows.net/xxx?SASTOKEN" "https://yyyy.s3.amazonaws.com/yyyy/" --recursive=True
Note: Please remove the SAS to avoid exposing your credentials. If you cannot remember the exact command, please retrieve it from the beginning of the log file.
What problem was encountered?
INFO: Based on the parameters supplied, a valid source-destination combination could not automatically be found. Please check the parameters you supplied.  If they are correct, please specify an exact source and destination type using the --from-to switch. Valid values are two-word phases of the form BlobLocal, LocalBlob etc.  Use the word 'Blob' for Blob Storage, 'Local' for the local file system, 'File' for Azure Files, and 'BlobFS' for ADLS Gen2. If you need a combination that is not supported yet, please log an issue on the AzCopy GitHub issues list.
when from-to is specified
failed to parse user input due to error: invalid --from-to value specified: "BlobS3". Valid values are two-word phases of the form BlobLocal, LocalBlob etc.  Use the word 'Blob' for Blob Storage, 'Local' for the local file system, 'File' for Azure Files, and 'BlobFS' for ADLS Gen2. If you need a combination that is not supported yet, please log an issue on the AzCopy GitHub issues list.
How can we reproduce the problem in the simplest way?
try to copy a container to s3 folder
Have you found a mitigation/solution?
None

Hi there, we don't currently support Azure -> S3. Furthermore, this is a duplicate of #348, and I'll be closing the issue now.


add Yoruba NER dataset

Added Yoruba GV dataset based on this paper

Thank you. Okay, other pull requests only have one dataset

The RemoteDatasetTest error in the CI is just a connection error, we can ignore it

merging since the CI is fixed on master

Thank you very much


Game FPS drops when manipulating editor camera

Godot version:
Godot master, commit bbb1af91
OS/device including version:
OS: Windows 10
GPU: NVIDIA GeForce GTX 960M
GPU Driver version: 430.86
Issue description:
When launching game from the editor, the game FPS drops drastically when editor viewport camera is manipulated while the game is running.
Steps to reproduce:

Add a label that gets updated with the current FPS (e.g. Engine.get_frames_per_second() function. Don't use print(...) in _process(delta), because that also prints to stdout in case you have a console running which alone makes FPS drop drastically if printing each frame and makes the effects less visible.
Disable VSync
Launch the game
In editor, go to either 2D or 3D viewport and start moving the camera
Watch the FPS plummet

Minimal reproduction project:
CameraTest.zip

This is kind of expected, as the editor and running game will "compete" in re-rendering their respective viewports.

Yes, it is indeed expected. I just thoought that the FPS drop is rather extreme. As an example, on my machine this causes a completely empty scene with just a label in it to drop from 500 FPS to 100 FPS. Maybe the complexity of a scene in this case doesn't play a role and the main reason of the FPS drop is all the OpenGL state changes that have to take place to serve both applications running? I wasn't sure, that's why I opened this issue after all.


fix setup, to clarify .env usage

I had issues with connecting to mongodb.
In the end, it was a collection of wrong assumptions I had that made me miss some information.
So this PR tried to make this info hard to miss.
My wrong assumptions were:

.env is the only active file (while there is magic in the background to update it per the active configuration).
the mongo_db_uri might include the ending "/". The term mongodb_uri kind of confused me - what exactly does it include?

Some other wrong assumptions I had that might worth fixing are:

that the setup is "more mature" so I came with a user state of mind, not a developer
as a result I treated modal as a black box while trying to install it the first time, in the end, it is a Python library for the cloud that you can play with its code for debugging as well.
The explanation today is not mature enough to hold the 2 different configurations for a newcomer. so
Either

The setup installation should be dealing with only one setup, probably production because as a developer you might be tempted to start the dev env.
Or
A  detailed explanation of the difference between dev and production should be in the prefix, as well as the difference between running the modal locally or in the cloud (and maybe the difference in the requirement.txt and other differences if they exist).

Thanks for the suggestions! I'll take them into account as I update the setup documentation #53. See also bef02e48063912ce1310605cf7784108d3255020.
To be clear: this codebase is both in development and intended as an example for developers during education events, not for end-users who just want to interact with an LLM discord bot. During this period where the LLM app tooling space is changing rapidly, it is further not intended that someone should be able to self-onboard to running the application.
As an example: the dev and prod environment setting is experimental, hence not documented and likely broken in some setups, and I intend to replace it pretty much entirely once environments are added to Modal in a week or two.


pyprimemesh/f1_rear_wing: Input Files

Input stl files for pyprimemesh example
f1_rear_wing

The source of these files are from the AIC
https://courses.ansys.com/index.php/courses/aerodynamics-discovery-day/lessons/explore-lift-through-simulations-lesson-3/topic/downforce-on-an-f1-car-rear-wing/

@agvarghe Is this PR ready for merge?


Variables to plot in output_plots.plot_gdp_ratio

Two things should be done to provide a better user experience in output_plots.plot_gdp_ratio

Expand the list of variables in constants.py
If a user enters a variable not in that list, then raise an assertion providing a warning that it's not in the list and guide them as to why.

Resolved with PR #962


CodeGenerator

Hey @neozhu and @Bram1903
Still extremly happy with the project. I'm trying to use the codegenerator (yes i know it's on different github repo). I've installed vs 2022 community edition and when I generate stuff for any class i've is that it isn't compilable after.
In the DTO's mapFrom is used and that isn't the case in this source code.
Code it generates:
public class SoftwareDto:IMapFrom<Software>
{
    public void Mapping(Profile profile)
    {
        profile.CreateMap<Software, SoftwareDto>().ReverseMap();
    }
    // TODO: define data transfer object (DTO) fields, for example:
        [Description("Id")]
    public int Id {get;set;}
    [Description("Name")]
    public string Name {get;set;} = String.Empty;
    [Description("Description")]
    public string? Description {get;set;}

}

ProductDTO in this repo is like:
// Licensed to the .NET Foundation under one or more agreements.
// The .NET Foundation licenses this file to you under the MIT license.

namespace myapp.Application.Features.Products.DTOs;

[Description("Products")]
public class ProductDto
{
    [Description("Id")] public int Id { get; set; }

    [Description("Product Name")] public string? Name { get; set; }

    [Description("Description")] public string? Description { get; set; }

    [Description("Unit")] public string? Unit { get; set; }

    [Description("Brand Name")] public string? Brand { get; set; }

    [Description("Price")] public decimal Price { get; set; }

    [Description("Pictures")] public List<ProductImage>? Pictures { get; set; }

    private class Mapping : Profile
    {
        public Mapping()
        {
            CreateMap<Product, ProductDto>().ReverseMap();
        }
    }
}

MapFrom is used in multiple files it generates so its a little bit of cleaning up to make use of it.
It's still quite a headstart to use the generator. But could you take a look and see what's wrong compared to project here?

Thank you @Bram1903 for labelling it.
I also notice in the Export<Item>Query.cs that the structure of getting localizer names has changed

Your project's source code isn't up-to-date, and neither is your code generation extension. Therefore, the code that's being generated is unusable and compiled.

@neozhu will try to update it, I just downloaded the extension from the store.

@neozhu how should I update it? should I build it myself based on the repo? this is the installed version.

I created my solution max two weeks ago when we talked about the command line install.

Hey @neozhu thank you for the quick reply. I see the repo is updated on 9 april and the vsix extension on here https://marketplace.visualstudio.com/items?itemName=SmartCodeMVC5Enginever3898.247365 is updated on 23 march. Maybe the last version isn't in the marketplace? Or am I missing something.

@neozhu will try to update it, I just downloaded the extension from the store.

no, you need clone this repo:https://github.com/neozhu/CleanArchitectureCodeGenerator , and build it then install it in bin

@neozhu will try to update it, I just downloaded the extension from the store.

no, you need clone this repo:https://github.com/neozhu/CleanArchitectureCodeGenerator , and build it then install it in bin

I've done that and it still keeps generating the old one, even after removing the old version. Rebooting the full pc. But it feels like this part is an issue on my end.
I would advise to put this in the readme

I will set a action for Publish extension to Marketplace

I will set a action for Publish extension to Marketplace

Thank you but its also really cool to have access to the extension code, if I e.g. want to update generated UI template I can do that. It's really cool, ty for learning me all this by having this repo public and answering questions

I will set a action for Publish extension to Marketplace

Thank you but its also really cool to have access to the extension code, if I e.g. want to update generated UI template I can do that. It's really cool, ty for learning me all this by having this repo public and answering questions

https://www.vsixgallery.com/extension/6A168388-B6A2-42F9-BA5A-B577D3CD4DB5

@neozhu you're amazing !


Mounts previous component, causes loop

Current Behavior

If i have a splash screen that basically changes to screen2 during componentWillMount, doing a NavigationActions.reset back to the splash creates a loop. in my case i have an app in which when it goes to the background i want to reset back to the splash to protect sensitive information.

it goes a little bit like this
-Splash
-screen2
-login
-user does whatever, presses home button and gets out of the app

reset to splash
screen2 for some reason after the reset, when navigating to screen2 the splash componentWillMount gets called over and over
loops splash and screen2

Expected Behavior
no loop, stays at screen2
Your Environment
using<EMAIL_ADDRESS>tested on ios
here is the resetaction that is dispatched when user exits app
const resetAction = NavigationActions.reset({
index: 0,
actions: [
NavigationActions.navigate({ routeName: 'Splash'})
]
});

software
version

react-navigation

react-native

node

npm or yarn

it seems to happen on navigate too. so i have screen2 (it does fingerprint auth on mount) and when it passes and i go to authorizedScreen screen2's componentDidMount gets called.

+1 on this.

@spencercarli what questions do you have?

need a reproduction of this issue. I don't know what componentWillMount would ever be called more than once because past screens in a stack aren't unmounted

Closing in favor of https://github.com/react-community/react-navigation/issues/2473


Update Dependencies

Would it be possible to update the dependency for Jasmine to 2.5.1 or higher?
When installing, the following warning is displayed (npm install -g protractor):
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
Thank you!
JT

The dependency on Jasmine 2.5.1 was addressed yesterday as we are trying to keep up with new releases.
https://github.com/angular/protractor/pull/3525/files
With the updated jasmine-core 2.5.1, the other dependencies we use have a dependency on an out-of-date minimatch:
>: grep "\"minimatch\":" **/package.json

node_modules/glob/package.json:    "minimatch": "^3.0.2",
node_modules/gulp/node_modules/liftoff/node_modules/findup-sync/node_modules/micromatch/node_modules/braces/node_modules/expand-range/package.json:    "minimatch": "^3.0.0",
node_modules/gulp/node_modules/liftoff/node_modules/findup-sync/node_modules/micromatch/node_modules/braces/package.json:    "minimatch": "^3.0.0",
node_modules/gulp/node_modules/liftoff/node_modules/findup-sync/node_modules/micromatch/node_modules/extglob/package.json:    "minimatch": "^2.0.1",
node_modules/gulp/node_modules/liftoff/node_modules/findup-sync/node_modules/micromatch/package.json:    "minimatch": "^3.0.0",
node_modules/gulp/node_modules/vinyl-fs/node_modules/glob-stream/node_modules/glob/package.json:    "minimatch": "^2.0.1",
node_modules/gulp/node_modules/vinyl-fs/node_modules/glob-stream/package.json:    "minimatch": "^2.0.1",
node_modules/gulp/node_modules/vinyl-fs/node_modules/glob-watcher/node_modules/gaze/node_modules/globule/node_modules/glob/package.json:    "minimatch": "~0.2.11",
node_modules/gulp/node_modules/vinyl-fs/node_modules/glob-watcher/node_modules/gaze/node_modules/globule/package.json:    "minimatch": "~0.2.11"
node_modules/jshint/package.json:    "minimatch": "~3.0.2",
node_modules/mocha/node_modules/glob/package.json:    "minimatch": "0.3"

So this means dependencies for gulp, jshint, and mocha are out of date.
Our outdated dependencies include:
>: npm outdated
Package             Current  Wanted        Latest  Location
mocha                 2.5.3   2.5.3         3.0.2  mocha
selenium-webdriver   2.53.3  2.53.3  3.0.0-beta-2  selenium-webdriver
typescript            2.0.2   2.0.2        1.8.10  typescript

Mocha and selenium-webdriver require additional work to update these to the latest. TypeScript dependency appears here because we are sort of ahead of the curve on version 2.


feat: Allow IPv4 or IPv6 configuration

Issue
https://github.com/gravitee-io/issues/issues/10247
Description
The option -Djava.net.preferIPv4Stack=true , block a deployment on an IPv6 cluster.
We can always add this option in the configuration  JAVA_OPTS
(Original PR: https://github.com/gravitee-io/gravitee-api-management/pull/10142)

📚  View the storybook of this branch here

Once again, thank you @francisko0 🙏🏻.


Issue calculating the font size

I'm new to react and just started using this component so maybe my observations are far from correct but there we go.
My issue is that sometimes the font-size calculated is by far too small. By adding some logs I've observed that the issue was that the originalWidth calculated at first wasn't correct (it returned a less width of what it should) so the algorithm resulted in an incorrect font-size. I corrected the issue by making sure that every time the algorithm called assertElementFitsHeight and assertElementFitsWidth the innerWidth and innerHeight was retrieved again from the element. Does this make any sense?
Thanks!

Thank you for details provided in the post. Do you think you could demonstrate an example using something like jsfiddle.net, or a fork or any tooling of your choice?

https://codesandbox.io/s/73AJMQ7jO
Hi, I have created a demo. Font unpredictably enlages by clicking.

@StipJey thanks for the example. That's exactly what I'm observing

Beautiful, thank you, @StipJey! Seems like definitely a bug, indeed.


cmd/bosun: add crop function

fixes #1773 (Year of the Boston Tea Party)

A little awkward because the arguments can't be strings since we don't have a stringSet at this time and lookups don't support strings. Also can't use the d() func since lookups don't support expressions.
However, it gets the job done, and I think the most fitting thing would be to add support for expressions in the lookup.

cc @Dieterbe

@captncraig please review one more time for sanity check on breaking out of loop

looks ok to me.


ci: Enable webhooks for v0.34.x

Fixes #N/A
Description

Enable webhooks for the 0.33.x branch

How was this change tested?

N/A

Does this change impact docs?

[ ] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[x] No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>6
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 77.267%

Totals

Change from base Build<PHONE_NUMBER>4:
0.02%

Covered Lines:
5360

Relevant Lines:
6937

💛  - Coveralls


suppress unused param warning on MSVC

This fixes #4057 by suppressing the warnings on MSVC as well

@scoder is there still something, which has to be changed on this PR?

This seems to break the Cython compilation on Windows:
https://ci.appveyor.com/project/cython/cython/builds/38327971
e.g. https://ci.appveyor.com/project/cython/cython/builds/38327971/job/5snecsmhb3d23woh

Hm is there a way to get the _tempita.c file from appveyor.
It appears like in the version generated by appveyor has e.g. the following error:
C:\projects\cython\Cython\Tempita\_tempita.c(1841) : see declaration of '__Pyx_Method_ClassMethod'

which indicates, that
static CYTHON_UNUSED PyObject* __Pyx_Method_ClassMethod(PyObject *method);

is on line 1841. However when I generate the file it is on Line 1829.

Closing this after merging #4162.


Reduce the length of generated animation files

The NANR files generated by NitroPaint are currently unnecessarily big. This has various causes but all related to the animationData.

When a sequence is in Index+T mode, each animation field is followed by 8 byte junk data. This is probably caused by a copy paste error. In the following three lines the last sizeof(ANIM_DATA_SRT) should be changed to sizeof(ANIM_DATA_T).
https://github.com/Garhoogin/NitroPaint/blob/64738a03b54a6af72c5e80ba0afc4a268135392f/NitroPaint/nanr.c#L106
https://github.com/Garhoogin/NitroPaint/blob/64738a03b54a6af72c5e80ba0afc4a268135392f/NitroPaint/nanr.c#L166
https://github.com/Garhoogin/NitroPaint/blob/64738a03b54a6af72c5e80ba0afc4a268135392f/NitroPaint/nanr.c#L181

https://github.com/Garhoogin/NitroPaint/blob/64738a03b54a6af72c5e80ba0afc4a268135392f/NitroPaint/nanr.h#L10-L13
I don't see a reason to add a padding field here. The original NANR files I observed don't "BEEF" after every index. My suggestion is to delete everything that depends on ANIM_DATA.pad_ and add something like this behind the ABNK writer:
//padding for DWORD alignment
BYTE pad = 0xFF;
while (stream->size % 4 != 0) {
	bstreamWrite(stream, &pad, 1);
}

With the current structure, everything is saved as it lays in the buffer. This can cause many duplicates in the output stream if different frames do the same thing. It would be nice if multiple frames pointed to the same address, if the target data is identical.

About the animation viewer, I know it's in an early stage of development but I would like to use this issue to ask a few things.

Is there a reason you didn't add [-][+] buttons for the Sequence? The sequences could also be named with the LABL data.
Why doesn't it appear under Menu -> File/New/?
Wouldn't it be really easy to add NMAR support? The data structure is almost identical to NANR. It has an ABNK and a LABL section. Well, it would collide with the names of the source files but apart from that I don't see an obstacle.

Hey,
The size of Index+T being too large does look to be a bug, that should not be written the way it is. That should be a pretty straightforward fix.
As for the BEEF padding, the files that I observed seemed to do this as I recall, though I can double check this. In theory the padding should only be needed at the very end if it's misaligned I imagine, I can take a look at doing this as well.
As for the  layout of the data saved, currently yeah there is no code in place to attempt to condense the animation data. I wasn't sure if the size differences would be  enough to warrant implementing this but that is something I can get to implementing as well.
For the viewer, I just don't think I ever got around to adding +/- buttons for them. The naming with LABL should also be possible in NCER files, though is unimplemented there as of now as well. Most of NitroPaint's features are written as they come up, and mostly in Mario Kart DS, which does not make use of many of these features, which is probably why they haven't been implemented yet.
Adding support for reading NMAR files should in theory be pretty simple, though I fear also making a viewer for those as well, I still want to clean up and finish the NMCR viewer.
As of now I'm working on some stuff for CTGP, but once that cools off a bit I should be able to get to this stuff. Thanks for taking the time to leave such a detailed issue.

Thanks for the reply. I'm not sure how the indices are usually listed in NANR files. In the NMARs I observed there is often just a 00 00 01 00 (without BEEF in between) and the frames point either to 0x0 or to 0x2.
About the NCER, I strongly advise against using the included LABL for naming the cells. It looks like these and the UEXT section there are just copies of the ones in the corresponding NANR file.

Quick update about the BEEF padding on simple sequences. It looks like the other animation types that include translating need DWORD alignment, meaning my 2nd suggestion in the initial issue text above would break things. But it should be possible to just pad once after each sequence of indices, for example instead of
00 00 EF BE 01 00 EF BE 02 00 EF BE

generate
00 00 01 00 02 00 EF BE

I finally got around to taking a look at this. I've corrected the wrong Index+T frames, and I've reworked it to only insert padding bytes when the data immediately following it requires an alignment. This should make just plain Index animations take about half the space as before.
On the subject of reducing the overall animation sizes by reusing bytes, I was able to get this working as of my latest commit (referenced above). It will do a search through the existing animation frame data for matching bytes (with proper alignment for the frame type of course). I know this isn't the most optimal solution of course (in terms of size), but it does produce sizes comparable to the sizes that g2dcvtr produced.
I realize that trying to get the most optimal size of animation data by overlapping parts of animations with each other in a more intelligent manner may get slightly smaller file sizes, but I don't think this is exactly worth all that complexity. If you disagree, you can always just reopen this issue and let me know.
As for things like adding/deleting sequences, I think that was just something that had slipped my mind at the time. It would pobably be trivial to add, and may be able to get around to it today or soon. Same goes for creating a new NANR file. As for supporting NMAR files, given that the structure is what it is, maybe I can have NitroPaint treat NMAR as an alternate format of NANR files, like I have right now with NCGR/NCBR files. For now though, I'll mark this closed since the main bugs/issues at hand are tackled. :)


[API] Better support for SQL databases

This is multipart proposal.
First: Change method name: from_sqls intuitive understanding is "from SQL database dump" (file or string, containing something like INSERT INTO ... VALUES ... -- such dumps any database could produce and in some context it is a common format for data exchange), which is not the case.
I think from_db could express the intention better.
Second: as far as I can see in practice, there are 3 distinct cases we need to cover for easy loading data from DB:

load entire table into the dataframe;
load some columns of table into the dataframe;
load results of some SQL query into the dataframe.

So, the most reasonable API is:
DataFrame.from_db(adapter, table: 'tbl')
DataFrame.from_db(adapter, table: 'tbl', columns: [:id, :name, :gender])
DataFrame.from_db(adapter, query: 'SELECT * FROM employees JOIN departments...' )

columns param could be provided with the query also. And also, it can be a hash, or mix of array/hash, for column renaming while loading:
DataFrame.from_db(adapter, table: 'tbl', columns: [:id, Name: :name, employee_gender: :gender])

Alright. We should keep compatibility with from_sql because many people use that. The enhanced behavior looks good.

Just throwing my cents in here.

I don't have any strong opinions on naming for the method but I'd be curious to hear more rationale for the change. The pandas method is read_sql so I don't think it's non-standard to use sql instead of db. Do you have any examples of other libraries which use db instead of sql? I agree that continued support of from_sql or at least a deprecation period would be a good idea.

It seems like the first two cases can be easily handled directly in a very basic SQL query. Is it worth the additional complexity in the method?

Just wanting to better understand the motivations behind the changes and happy to discuss.

Do you have any examples of other libraries which use db instead of sql?

Not sure about it. That was rather "personal taste-based" than "example-based" suggestion. But it can be considered other way round: from_sql means import from SQL database (in constranst for some No-SQL or specialized databases). So, I suppose, current name should work also.

It seems like the first two cases can be easily handled directly in a very basic SQL query. Is it worth the additional complexity in the method?

Yeah, I think it is. First, not everyone is familiary with SQL (and there would be constant need for some users for refering to docs about this SELECT * FROM table or was it FETCH FROM table (*) or should I use some kinde of parens, or waht); second, shortening most common cases is almost always a good thing (at least, for my taste), and Ruby's keyword arguments allow to handle it gracefully. Personally, I'd hate the necessity to write from_sql(adapter, 'SELECT * FROM employees') each and every time for quick fire-and-forget experimental scripts.

I also prefer from_sql.  Not everything that supports SQL(-like) syntax is a "database".  For example, Salesforce and Apache Spark are not traditional databases, but can both be accessed using a SQL-like syntax.

I think we can use ActiveRecord gem to support queries such as
User.where(name: 'David', occupation: 'Code Artist').order(created_at: :desc)

which is way simpler than (SELECT * ...) and quite popular because of Rails.

+1 to @lokeshh though the implementation of that would need to be looked into. And I agree with @gnilrets about from_sql. We should ideally be able to swap out the underlying SQL adapter in the future in order to accommodate for Spark or Salesforce.

Yeah, I think it is. First, not everyone is familiary with SQL (and there would be constant need for some users for refering to docs about this SELECT * FROM table or was it FETCH FROM table (*) or should I use some kinde of parens, or waht); second, shortening most common cases is almost always a good thing (at least, for my taste), and Ruby's keyword arguments allow to handle it gracefully. Personally, I'd hate the necessity to write from_sql(adapter, 'SELECT * FROM employees') each and every time for quick fire-and-forget experimental scripts.

@zverok agreed.

@lokeshh

In addition, I think we can use ActiveRecord gem to support queries such as

How do you imagine it? If by adding direct integration/dependencies, I'd be pretty much against it.

Maybe put in a separate gem (daru-activerecord?) that depends on both activerecord and daru for doing this.

Closing in favor of daru-io


Added Free or Paid Labels

Fixes: #81
Preview Link

@NishithP2004 Please take the latest pull and resolve the conflicts which probably came from another PR that I've merged now

@NishithP2004 Please take the latest pull and resolve the conflicts which probably came from another PR that I've merged now

Done


updated about maple cards text

Closes issue #747
@alexjball Please review

@sammymyi WDYT of these content changes? You can view the changes in the preview URL

this looks good to me - but let me run it past our UX researcher Minqi since she's done a lot of work/research into making our website easily comprehensible to folks! if she gives the thumbs up too, ill approve the ticket :)

The updated content is much more concise than the previous version! Thank you! I would make some minor changes to the "When" card, as we still want to keep the message that users are allowed to submit testimony at any time. Something like:

MAPLE welcomes testimony at any time, but we recommend submitting your testimony before the scheduled hearing date for the greatest impact. The relevant committees dates are listed on the bill pages of this website.

I am also excited to announce that we have a UX content writer joining us soon, who will help us to optimize MAPLE'S content strategy. This task is definitely his zone!

Great! @alexjball  should I close this pull request and make a new one with @mchai1218 's update for the When card? Or will you accept this one first and then I'll make another one?

great point minqi! i agree with updating the text for when with your suggestion. i think this will work for now since we don't have a definite timeline for when our ux content writer is joining :)


questions: isn't it annoying to touch so many files if upgrading a remote dependency?

for instance: if you want to upgrade component/dom you need to touch 24 files:
https://github.com/DemocracyOS/app/search?p=2&q=component%2Fdom&utf8=✓

Yeah, that's one of the problem's we've faced with component, as well as hitting the github API rate-limit way too often.
We've been exploring with browserfify as a solution for the frontend build recently and we're probably adopting it as a definite solution for this. We love the component approach to modularization, but the absence of a registry and depending entirely on the github API dosn't scale for mid-to-large project like ours :/

as well as hitting the github API rate-limit way too often.

even if you use a token?

but the absence of a registry and depending entirely on the github API dosn't scale for mid-to-large project like ours :/

yes, totally agree. There are also some other drawbacks.
Currently I'm experimenting with jspm. It is really awesome, it's like component also a package manager and support github and npm.
Just now I setup a configuration in jspm to support component styled directory structures and require paths, so it's working without touching the code!
I will write a blog article and maybe a small tool to convert component apps into jspm.
R.I.P component

even if you use a token?

Yeah, even with a token, 2 out of 3 (clean) builds would fail. For new instances, we would usually have to push 2-4 times to heroku to get a working deployment.
We'll definitely check jspm out. Is there any repo/gist you'd recommend us checking out?

I will write a blog article and maybe a small tool to convert component apps into jspm.

Looking forward to it!

R.I.P component
:(

https://github.com/jspm/demo-es6
https://github.com/guybedford/jspm-demo
Am 14.06.2015 17:00 schrieb "Guido Vilariño"<EMAIL_ADDRESS>
even if you use a token?
Yeah, even with a token, 2 out of 3 (clean) builds would fail. For new
instances, we would usually have to push 2-4 times to heroku to get a
working deployment.
We'll definitely check jspm out. Is there any repo/gist you'd recommend
us checking out?
I will write a blog article and maybe a small tool to convert component
apps into jspm.
Looking forward to it!
R.I.P component
:(
—
Reply to this email directly or view it on GitHub
https://github.com/DemocracyOS/app/issues/927#issuecomment-111837908.

Thanks!

turns out webpack has a better and more configurable API.
see https://github.com/componentjs/component/issues/639

:+1:


Pip install error on macOS

Using Python 3.6.10+ on macOS 10.15.3.
Tried:
pip install -e git+https://github.com/parlance/ctcdecode.git#egg=ctcdecode

And I get the error:
Obtaining ctcdecode from git+https://github.com/parlance/ctcdecode.git#egg=ctcdecode
  Updating /Users/shamoon/.local/share/virtualenvs/pytorch-lstm-audio-Pq4zK81J/src/ctcdecode clone
  Running command git fetch -q --tags
  Running command git reset --hard -q d4da7fa300d11cae0bc050489f8b51f4a939304d
  Running command git submodule update --init --recursive -q
Installing collected packages: ctcdecode
  Running setup.py develop for ctcdecode
    ERROR: Command errored out with exit status 1:
     command: /Users/shamoon/.local/share/virtualenvs/pytorch-lstm-audio-Pq4zK81J/bin/python3 -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/Users/shamoon/.local/share/virtualenvs/pytorch-lstm-audio-Pq4zK81J/src/ctcdecode/setup.py'"'"'; __file__='"'"'/Users/shamoon/.local/share/virtualenvs/pytorch-lstm-audio-Pq4zK81J/src/ctcdecode/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' develop --no-deps
         cwd: /Users/shamoon/.local/share/virtualenvs/pytorch-lstm-audio-Pq4zK81J/src/ctcdecode/
    Complete output (12 lines):
    running develop
    running egg_info
    writing ctcdecode.egg-info/PKG-INFO
    writing dependency_links to ctcdecode.egg-info/dependency_links.txt
    writing top-level names to ctcdecode.egg-info/top_level.txt
    reading manifest file 'ctcdecode.egg-info/SOURCES.txt'
    writing manifest file 'ctcdecode.egg-info/SOURCES.txt'
    running build_ext
    copying build/lib.macosx-10.15-x86_64-3.6/ctcdecode/_ext/ctc_decode.cpython-36m-darwin.so -> ctcdecode/_ext
    /Users/shamoon/.pyenv/versions/3.6-dev/lib/python3.6/distutils/extension.py:131: UserWarning: Unknown Extension options: 'package', 'with_cuda'
      warnings.warn(msg)
    error: could not create 'ctcdecode/_ext/ctc_decode.cpython-36m-darwin.so': No such file or directory
    ----------------------------------------
ERROR: Command errored out with exit status 1: /Users/shamoon/.local/share/virtualenvs/pytorch-lstm-audio-Pq4zK81J/bin/python3 -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/Users/shamoon/.local/share/virtualenvs/pytorch-lstm-audio-Pq4zK81J/src/ctcdecode/setup.py'"'"'; __file__='"'"'/Users/shamoon/.local/share/virtualenvs/pytorch-lstm-audio-Pq4zK81J/src/ctcdecode/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' develop --no-deps Check the logs for full command output.

I also tried with CFLAGS=-stdlib=libc++ pip3 install -e git+https://github.com/parlance/ctcdecode.git#egg=ctcdecode, but have the same error.

Did you solve this problem? How?

Hey @shamoons did you fixed your problem would be nice to know:)

Did you solve it? This problem confuse me for a long time. if you solve it, please tell me how. Thanks.


RuntimeError

Initializing BaseSegmenter to cuda:0
Traceback (most recent call last):
File "D:\pythonProject\Track-Anything-master\app.py", line 383, in
model = TrackingAnything(SAM_checkpoint, xmem_checkpoint, e2fgvi_checkpoint,args)
File "D:\pythonProject\Track-Anything-master\track_anything.py", line 18, in init
self.samcontroler = SamControler(self.sam_checkpoint, args.sam_model_type, args.device)
File "D:\pythonProject\Track-Anything-master\tools\interact_tools.py", line 37, in init
self.sam_controler = BaseSegmenter(SAM_checkpoint, model_type, device)
File "D:\pythonProject\Track-Anything-master\tools\base_segmenter.py", line 25, in init
self.model = sam_model_registrymodel_type
File "D:\anaconda\envs\my_pytorch\lib\site-packages\segment_anything\build_sam.py", line 15, in build_sam_vit_h
return _build_sam(
File "D:\anaconda\envs\my_pytorch\lib\site-packages\segment_anything\build_sam.py", line 105, in _build_sam
state_dict = torch.load(f)
File "D:\anaconda\envs\my_pytorch\lib\site-packages\torch\serialization.py", line 777, in load
with _open_zipfile_reader(opened_file) as opened_zipfile:
File "D:\anaconda\envs\my_pytorch\lib\site-packages\torch\serialization.py", line 282, in init
super(_open_zipfile_reader, self).init(torch._C.PyTorchFileReader(name_or_buffer))
RuntimeError: PytorchStreamReader failed reading zip archive: failed finding central directory
进程已结束,退出代码1
What is this problem?

Hello, it seems pre-trained weights for SAM are not downloaded completely. Please clear the cached files in checkpoints folder and try again. Thanks.

Hello, it seems pre-trained weights for SAM are not downloaded completely. Please clear the cached files in checkpoints folder and try again. Thanks.

yes, I just solved that problem, too. Thank you very much.  And then I want to ask you how much memory i need to run the TAM, which always say is out of memory.

Hello, please check our previous discussions for more details about memory: https://github.com/gaomingqi/Track-Anything/issues/4#issuecomment-1522055186 (run TAM for tracking), https://github.com/gaomingqi/Track-Anything/issues/4#issuecomment-1528198165 (run TAM for inpainting). Thanks.

Hello, please check our previous discussions for more details about memory: #4 (comment) (run TAM for tracking), #4 (comment) (run TAM for inpainting). Thanks.

Hello, I have a new problem. When I opened this url(Running on local URL:  http://<IP_ADDRESS>:6080
) I encountered the problem as shown in the figure. I would like to ask what caused this?

Then, this problem occurred when I was using a linux server.
Initializing BaseSegmenter to cuda:0
Hyperparameters read from the model weights: C^k=64, C^v=512, C^h=64
Single object mode: False
load pretrained SPyNet...
Loads checkpoint by http backend from path: https://download.openmmlab.com/mmediting/restorers/basicvsr/spynet_20210409-c6c1bd09.pth
/home/ubuntu/anaconda3/envs/wyz/lib/python3.9/site-packages/gradio/deprecation.py:43: UserWarning: You have unused kwarg parameters in Row, please remove them: {'scale': 0.4}
warnings.warn(
/home/ubuntu/anaconda3/envs/wyz/lib/python3.9/site-packages/gradio/deprecation.py:43: UserWarning: You have unused kwarg parameters in Video, please remove them: {'autosize': True}
warnings.warn(
/home/ubuntu/anaconda3/envs/wyz/lib/python3.9/site-packages/gradio/components.py:164: UserWarning: Unknown style parameter: height
warnings.warn(f"Unknown style parameter: {key}")
Traceback (most recent call last):
File "/home/ubuntu/wyz/Track-Anything/app.py", line 588, in
gr.Examples(
File "/home/ubuntu/anaconda3/envs/wyz/lib/python3.9/site-packages/gradio/blocks.py", line 1285, in exit
self.config = self.get_config_file()
File "/home/ubuntu/anaconda3/envs/wyz/lib/python3.9/site-packages/gradio/blocks.py", line 1261, in get_config_file
"input": list(block.input_api_info()),  # type: ignore
File "/home/ubuntu/anaconda3/envs/wyz/lib/python3.9/site-packages/gradio_client/serializing.py", line 41, in input_api_info
return (api_info["serialized_input"][0], api_info["serialized_input"][1])
KeyError: 'serialized_input'
Finally, I think your work is excellent and I'm personally very interested!!


Filtering DataFrames from feather files segfault after GC.

I am getting a segfault from an interaction of WeakRefStrings, DataFrames, Feather, and Query.
If you read in a DataFrame with feather, then apply a Query to it that filters it down and makes a new DataFrame, and garbage collection takes the original data frame, then any operation on the WeakRefStrings in the filtered DataFrame will crash the program. Is there a way around this?
Possibly copying all the WeakRefStrings from the original DataFrame before GC takes them?

An immediate fix would be to do Feather.read(file; weakrefstrings=false) which will avoid using WeakRefStrings at all. Not sure what the query is doing to invalidate things, but I'll try to take a look.

I think it is just building a DF that has WRS's that reference the same underlying data which goes away. My immediate workaround is to write the filtered DF to disk before GC happens and read it back in.

This might be slightly off topic, but WeakRefStrings will no longer be necessary in 0.6, correct?

I don't think they'll be as necessary, but we still can't get to quite the speed of WeakRefStrings, even with 0.6 improvements. I think it'd be enough to make them off by default, but I think there's still a use-case when you need ultimate speed.

@jpfairbanks Can you post the code you are using? I go through some hoops to make sure that you don't end up with WeakRefStrings when you query a DataStream source, so this kind of bug shouldn't happen in theory. One important thing is that you read in the feather file via Feather.Source and not via Feather.read. If you use Feather.read it will actually create a DataFrame that uses WeakRefStrings, and at that point I can't do anything about it anymore. You also would end up with way too much memory allocation. If you use Feather.Source on the other hand, my code should make sure that you end up with something after the query that has no WeakRefStrings in it.

@jpfairbanks, if you could try your original code again on current master, I believe this should be addressed. WeakRefStrings have now moved to a WeakRefStringArray representation, which ends up being much "safer" while retaining the excellent performance benefits. Let me know if you're still seeing issues.

Here is a MWE
Download https://archive.ics.uci.edu/ml/machine-learning-databases/abalone/abalone.data as ~/Downloads/abalone.data.txt
using DataFrames, Query, WeakRefStrings, CSV
df = CSV.read("Downloads/abalone.data.txt"; weakrefstrings=true)
b = @from i in df begin
       @select {i.M}
       @collect DataFrame
       end

df = []
gc()
whos()
#=...
                           ans      0 bytes  Void
                             b    130 KB     4176×1 DataFrames.DataFrame
                            df      0 bytes  0-element Array{Any,1}
=#
b[1,:]

#=
signal (11): Segmentation fault: 11
while loading no file, in expression starting on line 0
show at /Users/jfairbanks6/.julia/v0.6/WeakRefStrings/src/WeakRefStrings.jl:36
show at ./nullable.jl:65
showcompact at ./show.jl:1735 [inlined]
ourshowcompact at /Users/jfairbanks6/.julia/v0.6/DataFrames/src/abstractdataframe/show.jl:63
ourstrwidth at /Users/jfairbanks6/.julia/v0.6/DataFrames/src/abstractdataframe/show.jl:37
unknown function (ip: 0x126fd1e52)
getmaxwidths at /Users/jfairbanks6/.julia/v0.6/DataFrames/src/abstractdataframe/show.jl:118
unknown function (ip: 0x115d2e2c2)
show at /Users/jfairbanks6/.julia/v0.6/DataFrames/src/abstractdataframe/show.jl:454
unknown function (ip: 0x115d2cd6d)
display at ./REPL.jl:122
unknown function (ip: 0x115d2c596)
display at ./REPL.jl:125
unknown function (ip: 0x115d2c1a6)
display at ./multimedia.jl:194
unknown function (ip: 0x115d2bfa2)
do_call at /Users/osx/buildbot/slave/package_osx10_9-x64/build/src/interpreter.c:75
eval at /Users/osx/buildbot/slave/package_osx10_9-x64/build/src/interpreter.c:242
eval_body at /Users/osx/buildbot/slave/package_osx10_9-x64/build/src/interpreter.c:539
jl_toplevel_eval_body at /Users/osx/buildbot/slave/package_osx10_9-x64/build/src/interpreter.c:511
jl_toplevel_eval_flex at /Users/osx/buildbot/slave/package_osx10_9-x64/build/src/toplevel.c:571
jl_toplevel_eval_in at /Users/osx/buildbot/slave/package_osx10_9-x64/build/src/builtins.c:496
eval at ./boot.jl:235
jlcall_eval_17976 at /Applications/Julia-0.6.app/Contents/Resources/julia/lib/julia/sys.dylib (unknown line)
print_response at ./REPL.jl:144
unknown function (ip: 0x115cea0f8)
print_response at ./REPL.jl:129
unknown function (ip: 0x115ce9a68)
do_respond at ./REPL.jl:646
unknown function (ip: 0x115cd0571)
do_call at /Users/osx/buildbot/slave/package_osx10_9-x64/build/src/interpreter.c:75
eval at /Users/osx/buildbot/slave/package_osx10_9-x64/build/src/interpreter.c:242
eval_body at /Users/osx/buildbot/slave/package_osx10_9-x64/build/src/interpreter.c:539
jl_toplevel_eval_body at /Users/osx/buildbot/slave/package_osx10_9-x64/build/src/interpreter.c:511
jl_toplevel_eval_flex at /Users/osx/buildbot/slave/package_osx10_9-x64/build/src/toplevel.c:571
jl_toplevel_eval_in at /Users/osx/buildbot/slave/package_osx10_9-x64/build/src/builtins.c:496
eval at ./boot.jl:235
jlcall_eval_17976 at /Applications/Julia-0.6.app/Contents/Resources/julia/lib/julia/sys.dylib (unknown line)
run_interface at ./LineEdit.jl:1583
jlcall_run_interface_20033 at /Applications/Julia-0.6.app/Contents/Resources/julia/lib/julia/sys.dylib (unknown line)
run_frontend at ./REPL.jl:945
run_repl at ./REPL.jl:180
unknown function (ip: 0x11aabe302)
_start at ./client.jl:413
jlcall__start_18910 at /Applications/Julia-0.6.app/Contents/Resources/julia/lib/julia/sys.dylib (unknown line)
true_main at /usr/local/bin/julia (unknown line)
main at /usr/local/bin/julia (unknown line)
Allocations: 233470485 (Pool: 233427265; Big: 43220); GC: 549
[1]    60539 segmentation fault  julia
=#

Relevant package versions:
 required packages:
 - CSV                           0.1.5
 - DataFrames                    0.10.1
 - Feather                       0.2.5
 - Query                         0.7.2
 - ResultTypes                   1.0.0
 - Unitful                       0.2.6
 - WeakRefStrings                0.2.0
 - CatIndices                    0.0.2
 - CategoricalArrays             0.1.6
 - ChunkedArrays                 0.1.1
 - Compat                        0.31.0
 - DataArrays                    0.6.2
 - DataFlow                      0.3.0
 - DataStreams                   0.1.3
 - DataStructures                0.7.1
 - DataValues                    0.3.0
 - DateParser                    0.1.1
 - FileIO                        0.5.1
 - FlatBuffers                   0.2.0
 - GZip                          0.3.0
 - IndexedTables                 0.3.2
 - IterTools                     0.1.0
 - IterableTables                0.5.2
 - Iterators                     0.3.1
 - JuliaParser                   0.7.4
 - Lazy                          0.11.7
 - LegacyStrings                 0.2.2
 - MacroTools                    0.3.7
 - MappedArrays                  0.0.7
 - Memoize                       0.1.0+             returntypes (dirty)
 - NamedTuples                   4.0.0
 - NullableArrays                0.1.2
 - OffsetArrays                  0.3.0
 - PooledArrays                  0.1.1
 - Reexport                      0.0.3
 - Requires                      0.4.3
 - SimpleTraits                  0.5.1
 - SortingAlgorithms             0.1.1
 - StaticArrays                  0.6.2
 - StructIO                      0.0.2
 - TableTraits                   0.0.1
 - TableTraitsUtils              0.1.0

@jpfairbanks, I don't see any issues using current master versions of CSV, DataFrames, and WeakRefStrings. Let me know if you still see issues.


Make LowMemoryNotification object allocated

This makes a separate allocation for the callback object.  This makes
it easier for different callbacks to be used.

For #272 I need some time/timer bits in the Pal, and this is a minor tidying to make that cleaner.  Making the memory_provider inherit from the callback class makes it hard to be notified of two things uniformly.


Wrong unit test for Mixture packing

https://github.com/NavAbility/NavAbilitySDK.jl/blob/c8a087dc40a7a6cdfd92cec651c4e71f98e0709c/test/unit/testFactors.jl#L42-L47

oops, could you clarify a bit more -- i'm not following the issue?

I looked at the source code and this was not the part that I had wrong, I'ts only misleading. Will close.

I looked at the unit test to figure out how to create a mixture factor, but it didn't work. Sam helped and we ended up with:
md = MixtureData("LinearRelative", (slip=Rayleigh(5), noslip=Uniform(35, 60)), [0.4, 0.6], 2)
mmo = Factor("x1x2f1", "Mixture", ["x1","x2"], md)

So I think the LinearRelativeData part should be "LinearRelative"


BUG: Handle reading empty panels in MinuteBarUpdateReader.

Coverage decreased (-1.0%) to 87.221% when pulling bf3cffe590e99a0e74ede17ad3365f47e172707d on h5-why into 129a4486b7bc9f60454b987e0b1757b74f920ba7 on master.


Support loading an adapter object

Hi,
loadAdapter() as it is implemented here does not support loading an adapter object that is created elsewhere and passed as an argument. I've found that this is very useful when creating tests for adapters and robots alike. So I've had to override the method like using an approach like this:
Hubot.Robot::loadAdapter = (adapter) ->
  @adapter = adapter

In order to have more control.
Would you consider adding extra support for this scenario on loadAdapter()?
Thanks!

It looks like a good and low-risk idea. Do you have some published example test code that takes advantage of this feature? Just curious.

I think this would be a good candidate for the evolution process


Can not open/close indices anymore

Hello,
I was using 1.4.3 version before, but installed 1.4.6 today, and I can not open or close index anymore. It was a really useful feature for us, any chance of having it back ? (it was really faster than a curl command :p)
Edit: Actually, sometimes the option is available, sometimes isn't :/

hum... I can't reproduce this(and this is not intentional). If this happens again(even better if you can somehow reproduce), could you copy the output given by the REST APIs? A screen shot would also help me understand what exactly is missing.

Here is one screenshot with the open/close feature, and another without

I think it might comes from the fact that 3 of our 13 nodes, still have 1.4.3 version :(
Is the feature still available in 1.4.6 ?

hum, on the second picture I can read shards: 0 * 1... which is a bit odd. Maybe your cluster has problems atm?

it's because the index is closed

hum, odd then, because the color of the text indicates otherwise. When an index is closed, the text should by this dark gray:

Could you send me the output of /_cluster/state ?

yes, this is one of the others things I noticed with the new version, before closed indices had the dark gray colors. I would love to give you the output, unfortunately it contains informations about our clients (names at least).
Once I'll shutdown the 3 old nodes, I will try again, and I'll come back to you ;)

I'm only interested in a couple of things:
blocks: {
  indices: {
    INDEX_NAME: { }

so here the content of index_name
and then:
metadata: {
  indices: {
    INDEX_NAME: {
      state: THIS_VALUE

(of course, both referring to the index of the screenshot)

filter for open/closed indices is working, I have only 67 open indices over 212 indices, and the API gives the right state. I really think the problem is due to the difference of version, since this is the only change we got on our cluster ;) (I should have wait before opening an issue, my bad)

sure, let me know how it goes. but, having different versions of kopf on different nodes should not be a problem :)

I stopped old nodes, and problem is solved ;)
I have open/close feature, and closed indices have dark grey color \o/
Sorry for the false positive :(


Add possibility to create identity providers via SAML

Assign to me please...

Refer to https://github.com/zoitech/terraform-aws-saml


UpdateSObject functionaliy implemented to Salesforce

Update functionality to update different SObjects in Salesforce. Is dynamic and can be used in different objects, accounts, contacts, cases, etc.

It would seem that if you try to use the Result-object in another task with #result.Body.id, you get an error. It would seem that returning the body as pure object doesn't work. I think it would be better to return a JToken instead of an object to fix this issue. This seems to be a problem with other Salesforce tasks as well. Another problem is that the inheritance doesn't work quite well, since you cannot use the returned token in another task using #var.result.Token, so I would say that the two result objects need to be combined into one Result-object and then just set the Token-property to null if user doesn't want to get the token. I will create a separate ticket about fixing the Body-property and combination of Result-objects into one object, but these should be fixed for this task.

Created new issue to fix this problem to other SF-tasks: #9


Fix git push error for protected CLA branch

The pull request is created from master636947493489801775 to master to fix git push error for protected CLA branch

@Taojunshen : Thanks for your contribution! The author, @madskristensen, has been notified to review your proposed change.


[CAMERA] Excessive BufferQueueProducer Logs and Camera Initialization Issue / BufferQueueProducer spamming

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce

I want to create a simple app with a straightforward flow: taking a photo and displaying it.
However, after taking a photo or displaying the picture, there are excessive log entries from BufferQueueProducer flooding the logs.
The app works fine if I exit and take another photo (or navigate to another page). However, if I remain on the "display picture" page for an extended period and then return to the "take photo" section, the camera doesn't initialize correctly. I suspect there might be an excessive data flow causing the camera to fail to initialize properly.

additional information :
I am following the code from: https://docs.flutter.dev/cookbook/plugins/picture-using-camera.
My device for testing : infinix hot 10

Expected results
The app is now working correctly, and the camera can be activated again without any log flooding
Actual results
If the flooding persists for an extended period, the camera doesn't initialize properly (Black screen)
Code sample
Code sample
 Future<DisplayPictureScreen?> previewImageResult () async
  {
      String activity = "PREVIEW IMAGE RESULT";
      LoggingUtils.logStartFunction(activity);
      try {
        await _initializeCameraFuture;
        final image = await _cameraController.takePicture();
        if(!mounted) return null;
        Navigator.of(context).push(
          MaterialPageRoute(
            builder: (context)
            {
              count ++;
              LoggingUtils.logDebugValue("get image on previewImageResult".toUpperCase(),"image.path :  ${image.path}");
              return DisplayPictureScreen(imagePath: image.path);
              },
            ),
        );
      } catch (e) {
        LoggingUtils.logError(activity, e.toString());
        return null;
      }
      return null;
  }

 Future<DisplayPictureScreen?> previewImageResult () async
  {
      String activity = "PREVIEW IMAGE RESULT";
      LoggingUtils.logStartFunction(activity);
      try {
        await _initializeCameraFuture;
        final image = await _cameraController.takePicture();
        if(!mounted) return null;
        Navigator.of(context).push(
          MaterialPageRoute(
            builder: (context)
            {
              count ++;
              LoggingUtils.logDebugValue("get image on previewImageResult".toUpperCase(),"image.path :  ${image.path}");
              return DisplayPictureScreen(imagePath: image.path);
              },
            ),
        );
      } catch (e) {
        LoggingUtils.logError(activity, e.toString());
        return null;
      }
      return null;
  }

class DisplayPictureScreen extends StatefulWidget {
  final String imagePath;

  const DisplayPictureScreen({Key? key, required this.imagePath}): super(key: key);

  @override
  State<DisplayPictureScreen> createState() => _DisplayPictureScreenState();
}

class _DisplayPictureScreenState extends State<DisplayPictureScreen> {
  File? fileResult;

  @override
  void initState() {
    fileResult = File(widget.imagePath);
    super.initState();
  }
  @override
  Widget build(BuildContext context) {
    LoggingUtils.logStartFunction("Build DisplayPictureScreen");
    return Scaffold(
      appBar: AppBar(title: const Text('Display the Picture')),
      body: Image.file(fileResult!),
    );
  }
}

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
I/BufferQueueProducer(22983): [SurfaceTexture-0-22983-2](this:0x703d8ad800,id:6,api:4,p:587,c:22983) queueBuffer: slot 2 is dropped, handle=0x706bdd4380
I/BufferQueueProducer(22983): [SurfaceTexture-0-22983-2](this:0x703d8ad800,id:6,api:4,p:587,c:22983) queueBuffer: slot 3 is dropped, handle=0x706bdd4600
I/BufferQueueProducer(22983): [SurfaceTexture-0-22983-2](this:0x703d8ad800,id:6,api:4,p:587,c:22983) queueBuffer: slot 5 is dropped, handle=0x706bdd49c0
I/BufferQueueProducer(22983): [SurfaceTexture-0-22983-2](this:0x703d8ad800,id:6,api:4,p:587,c:22983) queueBuffer: slot 6 is dropped, handle=0x706bf52140
I/BufferQueueProducer(22983): [SurfaceTexture-0-22983-2](this:0x703d8ad800,id:6,api:4,p:587,c:22983) queueBuffer: slot 4 is dropped, handle=0x706bdd4880
I/BufferQueueProducer(22983): [SurfaceTexture-0-22983-2](this:0x703d8ad800,id:6,api:4,p:587,c:22983) queueBuffer: slot 1 is dropped, handle=0x70c0febf40
I/BufferQueueProducer(22983): [SurfaceTexture-0-22983-2](this:0x703d8ad800,id:6,api:4,p:587,c:22983) queueBuffer: slot 7 is dropped, handle=0x70c805c640
I/BufferQueueProducer(22983): [SurfaceTexture-0-22983-2](this:0x703d8ad800,id:6,api:4,p:587,c:22983) queueBuffer: slot 2 is dropped, handle=0x706bdd4380
I/BufferQueueProducer(22983): [SurfaceTexture-0-22983-2](this:0x703d8ad800,id:6,api:4,p:587,c:22983) queueBuffer: slot 3 is dropped, handle=0x706bdd4600
I/BufferQueueProducer(22983): [SurfaceTexture-0-22983-2](this:0x703d8ad800,id:6,api:4,p:587,c:22983) queueBuffer: slot 5 is dropped, handle=0x706bdd49c0
I/BufferQueueProducer(22983): [SurfaceTexture-0-22983-2](this:0x703d8ad800,id:6,api:4,p:587,c:22983) queueBuffer: slot 6 is dropped, handle=0x706bf52140

Flutter Doctor output
Doctor output
[Paste your output here]

Hi @AlfonsInfo
Could you elaborate on the steps to reproduce this?

if I remain on the "display picture" page for an extended period

How long did you stay on the Display the Picture page?
I used the sample code from cookbook page and checked it on my device Realme 6, Android 11 but can't see this issue. There are only two message with tag BufferQueueProducer printed in the output console and the camera didn't turn black screen after going back to Take a picture screen.


Wiki page explaining commonly encountered Server Errors and how to prevent them

This document contains an overview of the server errors encountered in this project and lists some ways to prevent them in the future. It would be good to have this on the wiki page for better visibility to the community and so we can learn from it (and add to it if we see any new patterns / fixes)
https://docs.google.com/document/d/1hIQIaFNVvyNiZBcCx0X7-_2lc0r1yvjxGfn4GJMjwEs/edit#heading=h.4nsx9mmay1nn

Hey @kevintab95 can I take on this issue?

As requested in our getting started wiki page, please make sure your comment does the following:

describes in more detail how you'd tackle the issue (e.g. explain which file(s) you would modify and what changes you would make). If your explanation makes sense, we'll assign the issue to you.

Sorry, my apologies. I will do the following:
1. Create a Server-errors-and-preventions.md file.
2. I will write about server errors from the link
3. I will write the following:
This document presents an overview of different categories of server errors, based on errors that have been fixed in the past, and proposes ways to prevent such errors from occurring in the future. The categories include: Data-related issues, Scalability issues, Corner cases, Supporting old browsers, Logic errors, Race conditions/issues on slow networks, and Errors that didn't need to be logged. For each category, an example of an error is provided and preventive actions are suggested.
Server Errors are a common issue faced by developers and can be caused by a variety of factors. In this document, we will present the main categories of server errors based on common issues that have been fixed so far, and propose ways to prevent such errors from occurring in the future.

Scalability Issue: These issues are related to features not scaling well on production. For example, exploration state data may be too large for some explorations and prevent further changes from being made, or suggestion models being fetched for review may exceed the query limit, resulting in an incomplete result.

Preventive action:

During design doc reviews, ask questions about performance and scalability when dealing with large amounts of data. Examples include: "How big do you expect X to get?", "Are there any limits to the size?", and "What happens when it reaches this limit and is it possible to handle it?"
Implement a functionality to generate dummy data for testing locally.

Corner Cases: These are user-facing issues where certain corner case scenarios are not considered (e.g. empty lists, undefined objects). Examples include errors caused by deleting a hint that is active in the editor view. These issues can be tricky to debug due to lack of reproduction steps.

Preventive action:

Use strongly typed frontend to help catch some of these issues.
Encourage developers to test edge cases and use template users in testing to uncover and test edge case scenarios.

Supporting old browsers: Certain JS functionality may not be supported in older browsers. Examples include using String.prototype.match, which lacks support in IE browsers.

Preventive action:

Fix a JS standard that we expect all clients to support and specify a "target version" in typescript so that the code will be compiled to that version/JS standard.

Logic errors: These are logical errors in the code. Examples include "this" scope referring to the global scope when it should refer to a local one. These issues are quite rare.

Preventive action:

Flag these issues during code reviews, as they often happen when developers are refactoring existing code but haven't fully tested their changes.

Data-related Issues: These issues result in corrupt or missing data on the server. They can be hard to debug and involve complicated one-off jobs to be run. Examples include missing exploration stats models on the production server.

Preventive action:

When testing, perform destructive operations on entities that have related supplementary entities to check if the supplementary objects reflect the correct state of the original ones.
Test with foreign/special characters.
Audit jobs need to account for all instances or occurrences of the relevant item on the server, sufficient written proof/explanation about the "thoroughness" of the audit can be added as a comment in the audit job code.

Race Conditions / Slow Network Issues: These errors happen when interacting too fast with the application or when the network is too slow. Examples include clicking on the "content" tab in the translation editor before it has fully loaded.

Preventive action:

For code that has a lot of "async" functionality, encourage authors to try throttling their network and/or interacting with the UI before it has completely loaded. This can help catch potential race conditions.

Related to a migration: One-off errors from migration of libraries or frameworks e.g. missing imports in the module files.

Preventive action:

Documentation: Record common issues in the relevant migration page when they are identified.

Errors that didn't need to be logged: Sometimes there may be unexpected errors thrown that do not impact user actions. Such errors can be ignored on a case-by-case basis. Example: Navigating away from a page when there are pending requests or if the request timed out caused some console errors.

Preventive action:

Code / review: When adding logging statements or throwing errors that are not handled, always consider what scenarios and how often they will get called. If the frequency is high, discuss with the server error coordinator for the month to check if there are alternatives to achieve the same (e.g. it may be possible to add logs on stackdriver interface directly in a controlled way.)

In conclusion,  by implementing these preventive actions, it is possible to ensure a smoother experience for users and reduce the likelihood of server errors.

@kevintab95 can you please review my solution?

@U8NWXD Sorry, my apologies.
I will do the following:
1. Create a Server-errors-and-preventions.md file.
2. I will write about server errors from the link
3. I will write the following in the .md file:
This document presents an overview of different categories of server errors, based on errors that have been fixed in the past, and proposes ways to prevent such errors from occurring in the future. The categories include: Data-related issues, Scalability issues, Corner cases, Supporting old browsers, Logic errors, Race conditions/issues on slow networks, and Errors that didn't need to be logged. For each category, an example of an error is provided and preventive actions are suggested.
Server Errors are a common issue faced by developers and can be caused by a variety of factors. In this document, we will present the main categories of server errors based on common issues that have been fixed so far, and propose ways to prevent such errors from occurring in the future.

Scalability Issue: These issues are related to features not scaling well on production. For example, exploration state data may be too large for some explorations and prevent further changes from being made, or suggestion models being fetched for review may exceed the query limit, resulting in an incomplete result.

Preventive action:

During design doc reviews, ask questions about performance and scalability when dealing with large amounts of data. Examples include: "How big do you expect X to get?", "Are there any limits to the size?", and "What happens when it reaches this limit and is it possible to handle it?"
Implement a functionality to generate dummy data for testing locally.

Corner Cases: These are user-facing issues where certain corner case scenarios are not considered (e.g. empty lists, undefined objects). Examples include errors caused by deleting a hint that is active in the editor view. These issues can be tricky to debug due to lack of reproduction steps.

Preventive action:

Use strongly typed frontend to help catch some of these issues.
Encourage developers to test edge cases and use template users in testing to uncover and test edge case scenarios.

Supporting old browsers: Certain JS functionality may not be supported in older browsers. Examples include using String.prototype.match, which lacks support in IE browsers.

Preventive action:

Fix a JS standard that we expect all clients to support and specify a "target version" in typescript so that the code will be compiled to that version/JS standard.

Logic errors: These are logical errors in the code. Examples include "this" scope referring to the global scope when it should refer to a local one. These issues are quite rare.

Preventive action:

Flag these issues during code reviews, as they often happen when developers are refactoring existing code but haven't fully tested their changes.

Data-related Issues: These issues result in corrupt or missing data on the server. They can be hard to debug and involve complicated one-off jobs to be run. Examples include missing exploration stats models on the production server.

Preventive action:

When testing, perform destructive operations on entities that have related supplementary entities to check if the supplementary objects reflect the correct state of the original ones.
Test with foreign/special characters.
Audit jobs need to account for all instances or occurrences of the relevant item on the server, sufficient written proof/explanation about the "thoroughness" of the audit can be added as a comment in the audit job code.

Race Conditions / Slow Network Issues: These errors happen when interacting too fast with the application or when the network is too slow. Examples include clicking on the "content" tab in the translation editor before it has fully loaded.

Preventive action:

For code that has a lot of "async" functionality, encourage authors to try throttling their network and/or interacting with the UI before it has completely loaded. This can help catch potential race conditions.

Related to a migration: One-off errors from migration of libraries or frameworks e.g. missing imports in the module files.

Preventive action:

Documentation: Record common issues in the relevant migration page when they are identified.

Errors that didn't need to be logged: Sometimes there may be unexpected errors thrown that do not impact user actions. Such errors can be ignored on a case-by-case basis. Example: Navigating away from a page when there are pending requests or if the request timed out caused some console errors.

Preventive action:

Code / review: When adding logging statements or throwing errors that are not handled, always consider what scenarios and how often they will get called. If the frequency is high, discuss with the server error coordinator for the month to check if there are alternatives to achieve the same (e.g. it may be possible to add logs on stackdriver interface directly in a controlled way.)

In conclusion, by implementing these preventive actions, it is possible to ensure a smoother experience for users and reduce the likelihood of server errors.

@kevintab95 can you please review the wiki?

is this issue still open? can I work on it? @kevintab95 @U8NWXD

Hey @U8NWXD @kevintab95
I created a server-error-and-solutions.md page.
Followed the oppia coding style and instructions to form a new page. If it seems right, kindly assign me this issue!

@vaishnavi192 Seems like a good start, thanks. One note though, we should make sure this page is discoverable by developers. I suggest putting it in the sidebar, under "Coding Guidelines", just below the "Revert and Regression Policy" bullet point, Maybe we can call it "Coding safely to avoid server errors".
I'll assign you to this, feel free to create a PR. Thanks!

Hey @seanlip yes I a created a pr with required changes. Have a look at it. Thanks!

This was fixed in https://github.com/oppia/oppia-web-developer-docs/pull/242. Closing.


Keyring / keychain CLI option being ignored after 1.80 change

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

VS Code Version: 1.80.0
OS Version: Kubuntu 23.04

$ gnome-keyring version
gnome-keyring: 42.1

Steps to Reproduce:

Have Kwallet disabled and gnome-keyring installed.
Launch VS Code with --password-store="gnome" option as in the docs.
Using code --verbose --disable-extensions --password-store="gnome" here.
Getting kwallet warning despite specifying gnome's keyring: "You're running in a KDE environment but the OS keyring is not available for encryption. Ensure you have kwallet running." error.

Logs
Main
Many instances of
[error] Error: Error while encrypting the text provided to safeStorage.encryptString. Encryption is not available.

No other relevant logging source found.

Since the 'Unlock keyring' dialog on startup really sucks (even if no file/project is opened and no extension installed!!!), I use code --password-store=basic on Ubuntu 20.04 to disable this non-sense. Before I found this solution I used mv /usr/libexec/gcr-prompter /usr/libexec/gcr-prompter.disabled (part of the gcr package) to get rid off it. Not sure, whether this helps, but yes, code should use lazy initialization (i.e. ask when secrets are actually needed) as well as make it customizable, what kind of store (if any) to use.

Let's follow up in https://github.com/microsoft/vscode/issues/187284 @jelmd since you are seeing a different issue.

So since I posted this issue, I enabled the KDE Wallet system to be able to use VS Code as usual.
Now I tried to replicate the original problem by disabling the KDE Wallet system (as it was before); terminating all kwallet processes; terminating all VS Code instances; then I re-opened VS Code. And now it works (yay?).
So I am unable to replicate it now, but should I have keyring issues again I'll try that increased logging approach to get more messages.

Thanks for following up @lucaspar! I'll close this since we don't have the repro but if you see it again don't hesitate to reach out. Also I updated the redirection link to point to the new docs location rather than the GitHub link so now the docs are a bit more readable :)

how to suppress this error?
don't care about
at all ...

@chiboreache the docs can help you get passed the error:
https://code.visualstudio.com/docs/editor/settings-sync#_other-linux-desktop-environments

It is getting worse! :((((((((
With 1.80.1 even the suggested measure do not work anymore, neither via CLI nor argv.json! It really sucks.

@jelmd please open a new issue with what you are seeing so we can further debug together.


[SERV-345] Add script for importing items

Will mark as ready for review once the API endpoint exists.

Rebased to incorporate changes from #31


"ROS Way" to kill goal or the whole Coverage Server?

I have been either leaving the coverage server in the foreground of one terminal window and killing it with cntl-c, or with the PID if running in the background.
Is there a more ROS-way such as sending a kill "goal"?
How do I abort the explore goal?

If you have a handle to the Coverage Server in a node, you can look at:
https://github.com/iRobotEducation/create3_examples/blob/galactic/create3_coverage/src/behaviors/dock-behavior.cpp
as an example for how to manage an action client programmatically.  Specifically, to cancel a goal, it calls:
m_dock_action_client->async_cancel_goal(m_dock_goal_handle);


Create an Arrow Coder for Beam that allows us to create Ray Datasets

This coder is the first step to allow us to create Ray Datasets based on Beam PCollections.
fyi @TheNeuralBit

Thanks, I think it's worth tracking this in a Beam issue as well. Could you provide some references for Ray Datasets that would inform how an Arrow encoded PCollection can integrate with it?

theres's very silly superficial stuff I wrote here: https://docs.google.com/document/d/1DcuKhCPnZezIvu9vFMsM4BRdBv0kgAWewOJqRbS42GI/edit#
Specifically, I would say read_datasource may be a good point to look at - it spins up several Ray Tasks that read individual blocks. Each block is usually stored as a block of Arrow records.
I suppose an integration we could have is something like:
class RayPCollection(beam.PCollection):

  def to_dataset(self):
    pipeline_result = self.pipeline.run()
    pcoll = pipeline_result.get_pcoll(pcoll)
    return ray.data.Dataset(BlockList(pcoll.block_list))

or something like that

Beam has a few utilities to convert to-from Beam and Arrow schemas (see here).
A first step would be to write an ArrowRecordBatchCoder, which can be constructed with a Beam Schema or an Arrow Schema, where each individual element is an Arrow RecordBatch

Coder interfaces for Beam - https://github.com/apache/beam/blob/master/sdks/python/apache_beam/coders/coders.py
An example of a Row Coder (complex) and a VarIntCoder (simple)

And then we can write a simple PTransform that takes a Beam PCollection of rows with schema, into a Beam PCollection where each element is an Arrow RecordBatch. (and viceversa)
Then it becomes easier to pass this to Ray's Datasets (and also into Beam from Datasets).

A second step could be to encode Beam Rows as batches of Arrow Records, but we can think about that once we do the first step.


fix: Failing regression tests: Added-to-cart modal (#2675)

Closes: #2675

I think we fixed the same issue. Here is mine PR: https://github.com/SAP/cloud-commerce-spartacus-storefront/pull/2754/files
@Zeyber You agree to close this one?

I think we fixed the same issue. Here is mine PR: SAP/cloud-commerce-spartacus-storefront/pull/2754/files
@Zeyber You agree to close this one?

Yes, we can close this one in favour of your pr.


[BUG] Does not style table when create table is called in a loop

🐛 Bug Report
Want to create multiple tables in the same worksheet. ofcourse with styling.. BUt exclJS fails to do so.
It formats only the last table. I have used simple loop as well as asynchronous calling to createTable method. but no luck with styling. 👎
Lib version: 1.14.0
Steps To Reproduce
create table using worksheet.addTable method in a loop. add styling in the method.

const worksheet = this.workbook.worksheets[0];
    let i = 0;
    while (i < 2) {
      this.address = this.calculateExcelCoords(this.lastRow, this.lastCol);
      this.ceate(worksheet, this.address).subscribe((res) => {
        this.lastRow = this.lastRow + 9;
        i++;
      });

    }
    this.save(this.workbook);

 ceate(ws, add): Observable<any> {
    return of(ws.addTable({
      name: 'MyTable',
      ref: add,
      headerRow: true,
      style: {
        theme: 'TableStyleDark3',
        showRowStripes: true,
      },
      columns: [
        { name: 'Date', filterButton: true },
        { name: 'Amount', filterButton: false },
      ],
      rows: [
        ['fjksdf', 'sdkjhfsd'],
        ['fjksdf', 'sdkjhfsd'],
        ['fjksdf', 'sdkjhfsd'],
        ['fjksdf', 'sdkjhfsd'],
        ['fjksdf', 'sdkjhfsd'],
        ['fjksdf', 'sdkjhfsd'],
        ['fjksdf', 'sdkjhfsd'],
        ['fjksdf', 'sdkjhfsd'],
      ],
    }));
  }

The expected behaviour:
The result of the following code is ::It formats only the last created table and not others.
Expected Behaviour:: It should format all tables

After some more trials I got to know that styleing the table works only when the name of the table  i.e. 'tableName' is unique. Otherwise it styles the last table with the name.


Update all services with the single completion handler

This finishes up where we left off with #851, which will resolve https://github.ibm.com/arf/planning-sdk-squad/issues/400
All remaining services and their unit tests are now updated to use the new single completion handler, (WatsonResponse<T>?, Error?) -> Void, instead of the dual success and failure callbacks.

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

Closing this since too many new, unrelated API changes were introduced. I'll reopen a new pull request with API definitions in commit https://github.ibm.com/Watson/developer-cloud--api-definitions/commit/9b9df9ec88478c15edab46b016d70abcee4a0b2f