Advancement Type: Race Properties

This advancement type allows a race to set a character's type, movement, senses, and size.
Level Up Interface
This interface will display the values for the race being added. If the race offers a choice of size, that option will be presented.
Configuration
The type, movement, and senses object are the same as are presented in actor data, and are null if they are not set (e.g. Humans don't get darkvision, so senses will be null for them).
The size property is an array of size choices.
{
  "type": {
    // Matching the type object on an NPC, but without the swarm size
  },
  "movement": {
    // Matching the movement object on an actor
  },
  "senses": {
    // Matching the senses object on an actor
  },
  "size": ["med"]
}

Value
Stores the size choice selected as well as the former value of any other properties that were replaced so they can be accurately reversed.

I find the name Race Properties slightly deceiving as some classes also set movement or senses, but I am at a loss with suggesting a better name. Character Properties sounds a little too generic to me, swinging too far on the opposite direction..

If you're still taking name suggestions, maybe Racial Traits since the feature sounds similar to #1405

Perhaps what you're discussing is Body Properties or Physical Properties. I have no strong feelings about it.


Implement Soft Searching

Overview
Added +/- 24 hour getting ride capability to the search feature
Changes Made

Added filtering by date time as well, including returning those that are within -24 hours of inputted departure time and + 24 hours of inputted departure time
Deleted some comments from the previous PR
Added the iexact for casing

Test Coverage
Manual testing with postman
Endpoint: http://<IP_ADDRESS>:8000/api/search/ -- GET
{
    "departure_datetime": "2020-03-27",
    "start_location_name": "home",
    "end_location_name": "test end"
}

[
    {
        "id": 1,
        "creator": {
            "id": 1,
            "netid": "test18",
            "first_name": "Tester",
            "last_name": "Test",
            "profile_pic_url": null,
            "grade": null,
            "pronouns": null
        },
        "max_travelers": 4,
        "min_travelers": 1,
        "departure_datetime": "2020-03-27T00:00:00Z",
        "description": "",
        "driver": null,
        "is_flexible": true,
        "riders": [],
        "estimated_cost": null,
        "path": {
            "id": 1,
            "start_location_place_id": "test13",
            "start_location_name": "home",
            "end_location_place_id": "test2",
            "end_location_name": "test end"
        },
        "type": "rideshare"
    },
    {
        "id": 2,
        "creator": {
            "id": 1,
            "netid": "test18",
            "first_name": "Tester",
            "last_name": "Test",
            "profile_pic_url": null,
            "grade": null,
            "pronouns": null
        },
        "max_travelers": 4,
        "min_travelers": 1,
        "departure_datetime": "2020-03-27T00:00:00Z",
        "description": "",
        "driver": null,
        "is_flexible": true,
        "riders": [],
        "estimated_cost": null,
        "path": {
            "id": 1,
            "start_location_place_id": "test13",
            "start_location_name": "home",
            "end_location_place_id": "test2",
            "end_location_name": "test end"
        },
        "type": "rideshare"
    },
    {
        "id": 3,
        "creator": {
            "id": 1,
            "netid": "test18",
            "first_name": "Tester",
            "last_name": "Test",
            "profile_pic_url": null,
            "grade": null,
            "pronouns": null
        },
        "max_travelers": 4,
        "min_travelers": 1,
        "departure_datetime": "2020-03-27T00:00:00Z",
        "description": "",
        "driver": null,
        "is_flexible": true,
        "riders": [],
        "estimated_cost": null,
        "path": {
            "id": 1,
            "start_location_place_id": "test13",
            "start_location_name": "home",
            "end_location_place_id": "test2",
            "end_location_name": "test end"
        },
        "type": "rideshare"
    },
    {
        "id": 4,
        "creator": {
            "id": 1,
            "netid": "test18",
            "first_name": "Tester",
            "last_name": "Test",
            "profile_pic_url": null,
            "grade": null,
            "pronouns": null
        },
        "max_travelers": 4,
        "min_travelers": 1,
        "departure_datetime": "2020-03-28T00:00:00Z",
        "description": "",
        "driver": null,
        "is_flexible": true,
        "riders": [],
        "estimated_cost": null,
        "path": {
            "id": 1,
            "start_location_place_id": "test13",
            "start_location_name": "home",
            "end_location_place_id": "test2",
            "end_location_name": "test end"
        },
        "type": "rideshare"
    }
]

Related PRs or Issues (delete if not applicable)
Implement search feature -- can delete that PR tho

@chalo2000 the datetime format for the departure datetime is YYYY-MM-DDZ(plus the time) so we will know which rides are departing first


Support :host in stylesheets

:host in component stylesheets should be translated into [is="COMPONENT_PATH"] .

Solved in #176


Setting manual time after a cluster was already created should be prevented

Environment info

Version: VERSION
Deployment: AZURE | AWS | GCLOUD | ESX | VBOX | DEV
Customer: NAME

Actual behavior

This scenario is already prevented by the BE, should be prevented and explained in the FE as well.

Expected behavior

Steps to reproduce

Screenshots or Logs or other output that would be helpful

No longer relevant due to OVA deployment support removal


[Proposal] Add en files.

Hi, @caouecs , I am working on my package overtrue/laravel-lang, I want to make it lumen support.
So, do you think is that alright?

Hi,
lumen doesn't have language files since 5.2 version ;) and before, it's the same validation file.

@caouecs No, the lang path of lumen is vendor/laravel/lumen-framework/resources/lang 😆 ，so, I will update my package to load it. Thanks.

Ah !!! OK ;) But it's the same validation file, no ?

@caouecs Yes, it is.

@caouecs https://github.com/overtrue/laravel-lang


New version: Sudoku v0.1.2

Registering package: Sudoku
Repository: https://github.com/scheinerman/Sudoku.jl
Created by: @scheinerman
Version: v0.1.2
Commit: 436bb40f1aa187f13377cf1ac7217b35cdf0ea5f
Git reference: HEAD

Is there a way to delete this?


develop.py test --xvfb option not documented

This tip from the developers mailing list isn't documented:
"If you have some sort of X installed, you can pip install xvfbwrapper in the venv and run the tests with --xvfb and they won't need a physical display."
Any reason not to do so?

No reason :)
Actually just a general lack of documentation on how develop.py works
Related to #3783

I wish to do it but...
Where is the best place to insert it? Maybe after the "Getting the source code" section in the Contribution doc?
Also, as this is target to 3.1 and 3.1.x I should wait for a support/3.1 branch or base this on the develop branch?
Thanks.

@dirtycoder thanks for your availability. I'd add a section before "Running and writing tests" called "The develop.py command" so that all the options can be properly documented
You can use http://django-cms.readthedocs.org/en/develop/reference/cli.html#command-line-interface as a template for styles and strcuture.
target develop as 3.1.1 will still be developed from it

Thanks, I will take a look at it in the weekend.

There's already a section after "Running and writing tests" covering some options for develop.py, I think it makes more sense to move it all to a separated page focusing on develop.py only.
Let me know if I can do it.

Fixed in #4073


Test with individual processes for the simultaneous requests tests

It's better to test these as parallel async tasks, but I have to find a way to ensure that the conn_2 task always goes shortly after conn_1 task.
This is a prerequisite to properly test the issues from #356 and solution like the set-global-lock branch.

Only makes sense for the set-global-lock branch. This will highlights the race condition problem.


[RFC] Version 0.82 release candidate

v0.82 (2019.03.03)
This release is packed with many new features and bug fixes.
Roadmap: better performance scaling for multi-core CPUs (#3957)

Poor performance scaling of the hist algorithm for multi-core CPUs has been under investigation (#3810). #3957 marks an important step toward better performance scaling, by using software pre-fetching and replacing STL vectors with C-style arrays. Special thanks to @Laurae2 and @SmirnovEgorRu.
See #3810 for latest progress on this roadmap.

New feature: Distributed Fast Histogram Algorithm (hist) (#4011, #4102, #4140, #4128)

It is now possible to run the hist algorithm in distributed setting. Special thanks to @CodingCat. The benefits include:

Faster local computation via feature binning
Support for monotonic constraints and feature interaction constraints
Simpler codebase than approx, allowing for future improvement

Depth-wise tree growing is now performed in a separate code path, so that cross-node syncronization is performed only once per level.

New feature: Multi-Node, Multi-GPU training (#4095)

Distributed training is now able to utilize clusters equipped with NVIDIA GPUs. In particular, the rabit AllReduce layer will communicate GPU device information. Special thanks to @mt-jones, @RAMitchell, @rongou, @trivialfis, @canonizer, and @jeffdk.
Resource management systems will be able to assign a rank for each GPU in the cluster.
In Dask, users will be able to construct a collection of XGBoost processes over an inhomogeneous device cluster (i.e. workers with different number and/or kinds of GPUs).

New feature: Multiple validation datasets in XGBoost4J-Spark (#3904, #3910)

You can now track the performance of the model during training with multiple evaluation datasets. By specifying eval_sets or call setEvalSets over a XGBoostClassifier or XGBoostRegressor, you can pass in multiple evaluation datasets typed as a Map from String to DataFrame. Special thanks to @CodingCat.
See the usage of multiple validation datasets here

New feature: Additional metric functions for GPUs (#3952)

Element-wise metrics have been ported to GPU: rmse, mae, logloss, poisson-nloglik, gamma-deviance, gamma-nloglik, error, tweedie-nloglik. Special thanks to @trivialfis and @RAMitchell.
With supported metrics, XGBoost will select the correct devices based on your system and n_gpus parameter.

New feature: Column sampling at individual nodes (splits) (#3971)

Columns (features) can now be sampled at individual tree nodes, in addition to per-tree and per-level sampling. To enable per-node sampling, set colsample_bynode parameter, which represents the fraction of columns sampled at each node. This parameter is set to 1.0 by default (i.e. no sampling per node). Special thanks to @canonizer.
The colsample_bynode parameter works cumulatively with other colsample_by* parameters: for example, {'colsample_bynode':0.5, 'colsample_bytree':0.5} with 100 columns will give 25 features to choose from at each split.

Major API change: consistent logging level via verbosity (#3982, #4002, #4138)

XGBoost now allows fine-grained control over logging. You can set verbosity to 0 (silent), 1 (warning), 2 (info), and 3 (debug). This is useful for controlling the amount of logging outputs. Special thanks to @trivialfis.
Parameters silent and debug_verbose are now deprecated.
Note: Sometimes XGBoost tries to change configurations based on heuristics, which is displayed as warning message.  If there's unexpected behaviour, please try to increase value of verbosity.

Major bug fix: external memory (#4040, #4193)

Clarify object ownership in multi-threaded prefetcher, to avoid memory error.
Correctly merge two column batches (which uses CSC layout).
Add unit tests for external memory.
Special thanks to @trivialfis and @hcho3.

Major bug fix: early stopping fixed in XGBoost4J and XGBoost4J-Spark (#3928, #4176)

Early stopping in XGBoost4J and XGBoost4J-Spark is now consistent with its counterpart in the Python package. Training stops if the current iteration is earlyStoppingSteps away from the best iteration. If there are multiple evaluation sets, only the last one is used to determinate early stop.
See the updated documentation here
Special thanks to @CodingCat, @yanboliang, and @mingyang.

Major bug fix: infrequent features should not crash distributed training (#4045)

For infrequently occuring features, some partitions may not get any instance. This scenario used to crash distributed training due to mal-formed ranges. The problem has now been fixed.
In practice, one-hot-encoded categorical variables tend to produce rare features, particularly when the cardinality is high.
Special thanks to @CodingCat.

Performance improvements

Faster, more space-efficient radix sorting in gpu_hist (#3895)
Subtraction trick in histogram calculation in gpu_hist (#3945)
More performant re-partition in XGBoost4J-Spark (#4049)

Bug-fixes

Fix semantics of gpu_id when running multiple XGBoost processes on a multi-GPU machine (#3851)
Fix page storage path for external memory on Windows (#3869)
Fix configuration setup so that DART utilizes GPU (#4024)
Eliminate NAN values from SHAP prediction (#3943)
Prevent empty quantile sketches in hist (#4155)
Enable running objectives with 0 GPU (#3878)
Parameters are no longer dependent on system locale (#3891, #3907)
Use consistent data type in the GPU coordinate descent code (#3917)
Remove undefined behavior in the CLI config parser on the ARM platform (#3976)
Initialize counters in GPU AllReduce (#3987)
Prevent deadlocks in GPU AllReduce (#4113)
Load correct values from sliced NumPy arrays (#4147, #4165)
Fix incorrect GPU device selection (#4161)
Make feature binning logic in hist aware of query groups when running a ranking task (#4115). For ranking task, query groups are weighted, not individual instances.
Generate correct C++ exception type for LOG(FATAL) macro (#4159)
Python package

Python package should run on system without PATH environment variable (#3845)
Fix coef_ and intercept_ signature to be compatible with sklearn.RFECV (#3873)
Use UTF-8 encoding in Python package README, to support non-English locale (#3867)
Add AUC-PR to list of metrics to maximize for early stopping (#3936)
Allow loading pickles without self.booster attribute, for backward compatibility (#3938, #3944)
White-list DART for feature importances (#4073)
Update usage of h2oai/datatable (#4123)

XGBoost4J-Spark

Address scalability issue in prediction (#4033)
Enforce the use of per-group weights for ranking task (#4118)
Fix vector size of rawPredictionCol in XGBoostClassificationModel (#3932)
More robust error handling in Spark tracker (#4046, #4108)
Fix return type of setEvalSets (#4105)
Return correct value of getMaxLeaves (#4114)

API changes

Add experimental parameter single_precision_histogram to use single-precision histograms for the gpu_hist algorithm (#3965)
Python package

Add option to select type of feature importances in the scikit-learn inferface (#3876)
Add trees_to_df() method to dump decision trees as Pandas data frame (#4153)
Add options to control node shapes in the GraphViz plotting function (#3859)
Add xgb_model option to XGBClassifier, to load previously saved model (#4092)
Passing lists into DMatrix is now deprecated (#3970)

XGBoost4J

Support multiple feature importance features (#3801)

Maintenance: Refactor C++ code for legibility and maintainability

Refactor hist algorithm code and add unit tests (#3836)
Minor refactoring of split evaluator in gpu_hist (#3889)
Removed unused leaf vector field in the tree model (#3989)
Simplify the tree representation by combining TreeModel and RegTree classes (#3995)
Simplify and harden tree expansion code (#4008, #4015)
De-duplicate parameter classes in the linear model algorithms (#4013)
Robust handling of ranges with C++20 span in gpu_exact and gpu_coord_descent (#4020, #4029)
Simplify tree training code (#3825). Also use Span class for robust handling of ranges.

Maintenance: testing, continuous integration, build system

Disallow std::regex since it's not supported by GCC 4.8.x (#3870)
Add multi-GPU tests for coordinate descent algorithm for linear models (#3893, #3974)
Enforce naming style in Python lint (#3896)
Refactor Python tests (#3897, #3901): Use pytest exclusively, display full trace upon failure
Address DeprecationWarning when using Python collections (#3909)
Use correct group for maven site plugin (#3937)
Jenkins CI is now using on-demand EC2 instances exclusively, due to unreliability of Spot instances (#3948)
Better GPU performance logging (#3945)
Fix GPU tests on machines with only 1 GPU (#4053)
Eliminate CRAN check warnings and notes (#3988)
Add unit tests for tree serialization (#3989)
Add unit tests for tree fitting functions in hist (#4155)
Add a unit test for gpu_exact algorithm (#4020)
Correct JVM CMake GPU flag (#4071)
Fix failing Travis CI on Mac (#4086)
Speed up Jenkins by not compiling CMake (#4099)
Analyze C++ and CUDA code using clang-tidy, as part of Jenkins CI pipeline (#4034)
Fix broken R test: Install Homebrew GCC (#4142)
Check for empty datasets in GPU unit tests (#4151)
Fix Windows compilation (#4139)
Comply with latest convention of cpplint (#4157)
Fix a unit test in gpu_hist (#4158)
Speed up data generation in Python tests (#4164)

Usability Improvements

Add link to InfoWorld 2019 Technology of the Year Award (#4116)
Remove outdated AWS YARN tutorial (#3885)
Document current limitation in number of features (#3886)
Remove unnecessary warning when gblinear is selected (#3888)
Document limitation of CSV parser: header not supported (#3934)
Log training parameters in XGBoost4J-Spark (#4091)
Clarify early stopping behavior in the scikit-learn interface (#3967)
Clarify behavior of max_depth parameter (#4078)
Revise Python docstrings for ranking task (#4121). In particular, weights must be per-group in learning-to-rank setting.
Document parameter num_parallel_tree (#4022)
Add Jenkins status badge (#4090)
Warn users against using internal functions of Booster object (#4066)
Reformat benchmark_tree.py to comply with Python style convention (#4126)
Clarify a comment in objectiveTrait (#4174)
Fix typos and broken links in documentation (#3890, #3872, #3902, #3919, #3975, #4027, #4156, #4167)

Acknowledgement
Contributors (in no particular order): Jiaming Yuan (@trivialfis), Hyunsu Cho (@hcho3), Nan Zhu (@CodingCat), Rory Mitchell (@RAMitchell), Yanbo Liang (@yanboliang), Andy Adinets (@canonizer), Tong He (@hetong007), Yuan Tang (@terrytangyuan)
First-time Contributors (in no particular order): Jelle Zijlstra (@JelleZijlstra), Jiacheng Xu (@jiachengxu), @ajing, Kashif Rasul (@kashif), @theycallhimavi, Joey Gao (@pjgao), Prabakaran Kumaresshan (@nixphix), Huafeng Wang (@huafengw), @lyxthe, Sam Wilkinson (@scwilkinson), Tatsuhito Kato (@stabacov), Shayak Banerjee (@shayakbanerjee), Kodi Arfer (@Kodiologist), @KyleLi1985, Egor Smirnov (@SmirnovEgorRu), @tmitanitky, Pasha Stetsenko (@st-pasha), Kenichi Nagahara (@keni-chi), Abhai Kollara Dilip (@abhaikollara), Patrick Ford (@pford221), @hshujuan, Matthew Jones (@mt-jones), Thejaswi Rao (@teju85), Adam November (@anovember)
First-time Reviewers (in no particular order): Mingyang Hu (@mingyang), Theodore Vasiloudis (@thvasilo), Jakub Troszok (@troszok), Rong Ou (@rongou), @Denisevi4, Matthew Jones (@mt-jones), Jeff Kaplan (@jeffdk)

Any change in particular you'd like us to try testing @hcho3 ?

One thing I am interested in is, how experimental is our external memory implementation?  We can't mark it beta forever...

@thvasilo I'm mainly soliciting feedback with regard to the release notes. After a short while, committers will approve the release.

@trivialfis I'd like to see external memory implemented for hist, with robust unit tests. Then we can remove the beta label.

LGTM.

just noticed one thing, @hcho3
actually the latest code in distributed hist only syncs stats at root level (for both loss-guided and depth-width) and the stats of all other nodes are derived from the cache (https://github.com/dmlc/xgboost/blob/master/src/tree/updater_quantile_hist.cc#L743-L780) (thanks for the suggestion from @RAMitchell )
instead of
"""
Depth-wise tree growing is now performed in a separate code path, so that cross-node synchronization is performed only once per level.
"""

@CodingCat Wait, I thought depthwise had fewer sync steps than lossguide?

nvm, I am brain-damaged.....

With 5 approvals, I am going to release 0.82. Thanks all!

When would binary wheels for 0.82 be available? (especially multi-gpu)
https://s3-us-west-2.amazonaws.com/xgboost-wheels/list.html

@hlbkin It is already available on PyPI. Run pip install xgboost==0.82. This one will have multi-GPU enabled.

When will CRAN get a new release of the R package?

There's a recent change in R-devel which causes failure in unittests.
I'll patch 0.82 with a fix and submit to CRAN before March 20th.
Best regards,
Tong He
Kodi Arfer<EMAIL_ADDRESS>于2019年3月8日周五 上午6:18写道：

When will CRAN get a new release of the R package?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dmlc/xgboost/pull/4201#issuecomment-470943526, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABOugE2LmEOSRgZQK1JaPA7wnxz_Qhowks5vUnFMgaJpZM4bbzn5
.

@Kodiologist 0.82 is now released on CRAN: https://cran.r-project.org/web/packages/xgboost/index.html


Give all four players in team games their own pool cues.

Will not have this in 1.2.0.
Reason: pool in real life generally only uses two cues. Four cues works in theory but it would require some dangerous refactoring, is hard to test, and seems like it'd be of limited use.


RAM-#1993: Importing distant DXFs bug

modified:   Nucleus/Nucleus.DXF/DXFReader.cs
Small change to DXFReader to add functionality to pull out a custom header (in this case, the origin position of the file) - and also exposed a ReadDXF function to public so that it can be called directly from sitesolve core (the alternative would be loading the DXF a second time just to get the header out).

Added a further change to DXFReader - it now checks for an origin in the file and, if present, subtracts it from all the geometry in the file on import. This doesn't affect the file itself, just makes sure that data passed to Unity has a sensible 0,0,0 origin point.


ROX-22197: Turn on ROX_MOVE_INIT_BUNDLES_UI feature flag

Description
Open now to give CI plenty of time, but do not merge until after #9707
Checklist

[ ] Investigated and inspected CI test results
[x] ~Unit test and regression tests added~

Testing Performed

/test gke-nongroovy-e2e-tests


Image Support

Image Support
As a user, I want to be able to associate images with items to easily identify items.
Currently, placeholder images are used for all items.  Allow users to drag and drop images and associate them.
Acceptance Criteria

Drag'n'drop functionality works, user can upload an image.
User's image is sent to the backend for necessary processing.
Item abstraction has new property imageUrl.
Item displays image if property is set, otherwise drag'n'drop box.

Notes
See: https://react-dropzone.js.org/

Alternatively, we could avoid having the backend handle this.  We could instead make the frontend responsible for sending the image to imgur.  Either approach would work.
But either way, the backend would have to be notified of changes.  i.e, imageUrl being set.


RFC Warn users for missing slots of the model card template.

xref: https://github.com/skops-dev/skops/pull/37/files#r928169418
We should decide if we want to warn users if the user fails to pass any or certain fields of the model card. Previously we have discussed that we should have very few mandatory fields in the card to reduce the entry barrier.
We could warn the users about all or some of the fields, or leave it to the user since the missing fields are rendered as missing in the README.md file anyway, i.e. the user would see that they are missing.
cc @meg-huggingface @osanseviero @skops-dev/maintainers

Also cc @nateraw as I was wondering if this could be implemented directly as a param within the modelcards utilities (e.g. mode="strict" vs mode="warn" vs mode="light" or something like that, and then each library user could determine how they want to handle this.

@BenjaminBossan this can be achieved easily now, right?

There are ways to achieve that, yes. Personally, I don't think it's super useful though.

Yea totally possible to do this in hf_hub version...would want to default to being quiet though, so as to not overwhelm the terminal of users by default (as I'm guessing in many cases they will leave many jinja template vars blank).
imo I don't know how helpful this is though (in terms of dev effort vs payoff). Mostly because once you see the rendered card its fairly obvious which vars you didn't pass. just my two cents tho - would love other opinions. 😄


Multiple errors: Cannot open/create empty project using GLES2-only machine - I guess memory leaks (8c435a343*)

Remark
I will try the version of today (08.26) as it seems there have been memory leak or resource leak fixes and autoclose this issue if it will fix my problem...
I open the issue for documenting the thing and because I am not sure the new build will fix it or not and I already collected the relevant information...
Godot version:
8c435a343e9739f30cb2e347df95835c91c1ff1a
OS/device including version:

Ubuntu 16.04
32 bit Intel CPU @ 1.6Ghz
Ati Mobility radeon Xpress 200M @ 128Mb
OpenGL ES 2.0 Renderer: Gallium 0.4 on ATI RC410

Issue description:
I must use the GLES 2.x renderer as that is what my machine supports. Tried to run the editor built from latest version with godot.x11.tools.32.llvm --video-driver GLES2 which works, but when tried to create a project I get the error of not having GLES 3.x capable card. I figured from an unofficial godot 3.0 backport that also uses the GLES 2.x renderer, that I can get around this using "-e" and starting godot from the directory of the (created) project.
<path-to-godot>/godot.x11.tools.32.llvm --video-driver GLES2 -e
This lead to properly use the GLES 2.x renderer, but I got into some endless resouce leak - I can see all of my memory and swap slowly eaten up until my 800mb ram + 1Gb swap completely get exhausted.
Also I kind of dislike the errors in the terminal that says the depth buffer cannot be written to. That seems to be harmless, just I added the full logs so it is visible to others as maybe it only happens on my machine.
Steps to reproduce:

godot.x11.tools.32.llvm --video-driver GLES2
Create a new project
Editor crashes because it tries to use GLES3 renderer
Go to the directory of the created project
/godot.x11.tools.32.llvm --video-driver GLES2 -e

Log of the terminal
prenex@ubuntu:~/munka/Godot_projets/TestProject$ /media/prenex/Plan9\(Outer\ Space\)/godot31/bin/godot.x11.tools.32.llvm --video-driver GLES2 -eOpenGL ES 2.0 Renderer: Gallium 0.4 on ATI RC410
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL	Type: Error	ID: 1	Severity: High	Message: GL_INVALID_OPERATION in glTexImage2D(bad target for depth texture)
   At: drivers/gles2/rasterizer_gles2.cpp:111.
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL	Type: Error	ID: 1	Severity: High	Message: GL_INVALID_OPERATION in glTexImage2D(bad target for depth texture)
   At: drivers/gles2/rasterizer_gles2.cpp:111.
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL	Type: Error	ID: 1	Severity: High	Message: GL_INVALID_OPERATION in glTexImage2D(bad target for depth texture)
   At: drivers/gles2/rasterizer_gles2.cpp:111.
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL	Type: Error	ID: 1	Severity: High	Message: GL_INVALID_OPERATION in glTexImage2D(bad target for depth texture)
   At: drivers/gles2/rasterizer_gles2.cpp:111.
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL	Type: Error	ID: 1	Severity: High	Message: GL_INVALID_OPERATION in glTexImage2D(bad target for depth texture)
   At: drivers/gles2/rasterizer_gles2.cpp:111.
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL	Type: Error	ID: 1	Severity: High	Message: GL_INVALID_OPERATION in glTexImage2D(bad target for depth texture)
   At: drivers/gles2/rasterizer_gles2.cpp:111.
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL	Type: Error	ID: 1	Severity: High	Message: GL_INVALID_OPERATION in glTexImage2D(bad target for depth texture)
   At: drivers/gles2/rasterizer_gles2.cpp:111.
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL	Type: Error	ID: 1	Severity: High	Message: GL_INVALID_OPERATION in glTexImage2D(bad target for depth texture)
   At: drivers/gles2/rasterizer_gles2.cpp:111.
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL	Type: Error	ID: 1	Severity: High	Message: GL_INVALID_OPERATION in glTexImage2D(bad target for depth texture)
   At: drivers/gles2/rasterizer_gles2.cpp:111.
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL	Type: Error	ID: 1	Severity: High	Message: GL_INVALID_OPERATION in glTexImage2D(bad target for depth texture)
   At: drivers/gles2/rasterizer_gles2.cpp:111.
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL	Type: Error	ID: 1	Severity: High	Message: GL_INVALID_OPERATION in glTexImage2D(bad target for depth texture)
   At: drivers/gles2/rasterizer_gles2.cpp:111.
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL	Type: Error	ID: 1	Severity: High	Message: GL_INVALID_OPERATION in glTexImage2D(bad target for depth texture)
   At: drivers/gles2/rasterizer_gles2.cpp:111.
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL	Type: Error	ID: 1	Severity: High	Message: GL_INVALID_OPERATION in glTexImage2D(bad target for depth texture)
   At: drivers/gles2/rasterizer_gles2.cpp:111.
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL	Type: Error	ID: 1	Severity: High	Message: GL_INVALID_OPERATION in glTexImage2D(bad target for depth texture)
   At: drivers/gles2/rasterizer_gles2.cpp:111.
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL	Type: Error	ID: 1	Severity: High	Message: GL_INVALID_OPERATION in glTexImage2D(bad target for depth texture)
   At: drivers/gles2/rasterizer_gles2.cpp:111.
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL	Type: Error	ID: 1	Severity: High	Message: GL_INVALID_OPERATION in glTexImage2D(bad target for depth texture)
   At: drivers/gles2/rasterizer_gles2.cpp:111.
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL	Type: Error	ID: 1	Severity: High	Message: GL_INVALID_OPERATION in glTexImage2D(bad target for depth texture)
   At: drivers/gles2/rasterizer_gles2.cpp:111.
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL	Type: Error	ID: 1	Severity: High	Message: GL_INVALID_OPERATION in glTexImage2D(bad target for depth texture)
   At: drivers/gles2/rasterizer_gles2.cpp:111.
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL	Type: Error	ID: 1	Severity: High	Message: GL_INVALID_OPERATION in glTexImage2D(bad target for depth texture)
   At: drivers/gles2/rasterizer_gles2.cpp:111.
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL	Type: Error	ID: 1	Severity: High	Message: GL_INVALID_OPERATION in glTexImage2D(bad target for depth texture)
   At: drivers/gles2/rasterizer_gles2.cpp:111.
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL	Type: Error	ID: 1	Severity: High	Message: GL_INVALID_OPERATION in glTexImage2D(bad target for depth texture)
   At: drivers/gles2/rasterizer_gles2.cpp:111.
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL	Type: Error	ID: 1	Severity: High	Message: GL_INVALID_OPERATION in glTexImage2D(bad target for depth texture)
   At: drivers/gles2/rasterizer_gles2.cpp:111.
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL	Type: Error	ID: 1	Severity: High	Message: GL_INVALID_OPERATION in glTexImage2D(bad target for depth texture)
   At: drivers/gles2/rasterizer_gles2.cpp:111.
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL	Type: Error	ID: 1	Severity: High	Message: GL_INVALID_OPERATION in glTexImage2D(bad target for depth texture)
   At: drivers/gles2/rasterizer_gles2.cpp:111.
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL	Type: Error	ID: 1	Severity: High	Message: GL_INVALID_OPERATION in glTexImage2D(bad target for depth texture)
   At: drivers/gles2/rasterizer_gles2.cpp:111.
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL	Type: Error	ID: 1	Severity: High	Message: GL_INVALID_OPERATION in glTexImage2D(bad target for depth texture)
   At: drivers/gles2/rasterizer_gles2.cpp:111.
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL	Type: Error	ID: 1	Severity: High	Message: GL_INVALID_OPERATION in glTexImage2D(bad target for depth texture)
   At: drivers/gles2/rasterizer_gles2.cpp:111.
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL	Type: Error	ID: 1	Severity: High	Message: GL_INVALID_OPERATION in glTexImage2D(bad target for depth texture)
   At: drivers/gles2/rasterizer_gles2.cpp:111.
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL	Type: Error	ID: 1	Severity: High	Message: GL_INVALID_OPERATION in glTexImage2D(bad target for depth texture)
   At: drivers/gles2/rasterizer_gles2.cpp:111.
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL	Type: Error	ID: 1	Severity: High	Message: GL_INVALID_OPERATION in glTexImage2D(bad target for depth texture)
   At: drivers/gles2/rasterizer_gles2.cpp:111.
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL	Type: Error	ID: 1	Severity: High	Message: GL_INVALID_VALUE in glTexImage2D(invalid width or height or depth)
   At: drivers/gles2/rasterizer_gles2.cpp:111.
ERROR: initialize: Directional shadow framebuffer status invalid
   At: drivers/gles2/rasterizer_scene_gles2.cpp:2474.
WARNING: _get: Property not found: _global_script_class_icons
   At: core/project_settings.cpp:194.
handle_crash: Program crashed with signal 11
Dumping the backtrace. Please include this when reporting the bug on https://github.com/godotengine/godot/issues
ERROR: execute: Condition ' !f ' is true. returned: ERR_CANT_OPEN
   At: drivers/unix/os_unix.cpp:281.
[1] [0xb7736c14] ()
ERROR: execute: Condition ' !f ' is true. returned: ERR_CANT_OPEN
   At: drivers/unix/os_unix.cpp:281.
[2] /usr/lib/i386-linux-gnu/dri/r300_dri.so(+0x544fd7) [0xb5d0dfd7] ()
ERROR: execute: Condition ' !f ' is true. returned: ERR_CANT_OPEN
   At: drivers/unix/os_unix.cpp:281.
[3] /usr/lib/i386-linux-gnu/dri/r300_dri.so(+0x55b85b) [0xb5d2485b] ()
ERROR: execute: Condition ' !f ' is true. returned: ERR_CANT_OPEN
   At: drivers/unix/os_unix.cpp:281.
[4] /usr/lib/i386-linux-gnu/dri/r300_dri.so(+0x552b48) [0xb5d1bb48] ()
ERROR: execute: Condition ' !f ' is true. returned: ERR_CANT_OPEN
   At: drivers/unix/os_unix.cpp:281.
[5] /usr/lib/i386-linux-gnu/dri/r300_dri.so(+0x5532b6) [0xb5d1c2b6] ()
ERROR: execute: Condition ' !f ' is true. returned: ERR_CANT_OPEN
   At: drivers/unix/os_unix.cpp:281.
[6] /usr/lib/i386-linux-gnu/dri/r300_dri.so(+0x54e45a) [0xb5d1745a] ()
ERROR: execute: Condition ' !f ' is true. returned: ERR_CANT_OPEN
   At: drivers/unix/os_unix.cpp:281.
[7] /usr/lib/i386-linux-gnu/dri/r300_dri.so(+0x54e514) [0xb5d17514] ()
ERROR: execute: Condition ' !f ' is true. returned: ERR_CANT_OPEN
   At: drivers/unix/os_unix.cpp:281.
[8] /usr/lib/i386-linux-gnu/dri/r300_dri.so(+0x547a23) [0xb5d10a23] ()
ERROR: execute: Condition ' !f ' is true. returned: ERR_CANT_OPEN
   At: drivers/unix/os_unix.cpp:281.
[9] /usr/lib/i386-linux-gnu/dri/r300_dri.so(+0x5323c5) [0xb5cfb3c5] ()
ERROR: execute: Condition ' !f ' is true. returned: ERR_CANT_OPEN
   At: drivers/unix/os_unix.cpp:281.
[10] /usr/lib/i386-linux-gnu/dri/r300_dri.so(+0x533316) [0xb5cfc316] ()
ERROR: execute: Condition ' !f ' is true. returned: ERR_CANT_OPEN
   At: drivers/unix/os_unix.cpp:281.
[11] /usr/lib/i386-linux-gnu/dri/r300_dri.so(+0x53f6e3) [0xb5d086e3] ()
ERROR: execute: Condition ' !f ' is true. returned: ERR_CANT_OPEN
   At: drivers/unix/os_unix.cpp:281.
[12] /usr/lib/i386-linux-gnu/dri/r300_dri.so(+0x533f06) [0xb5cfcf06] ()
ERROR: execute: Condition ' !f ' is true. returned: ERR_CANT_OPEN
   At: drivers/unix/os_unix.cpp:281.
[13] /usr/lib/i386-linux-gnu/dri/r300_dri.so(+0x535e32) [0xb5cfee32] ()
ERROR: execute: Condition ' !f ' is true. returned: ERR_CANT_OPEN
   At: drivers/unix/os_unix.cpp:281.
[14] /usr/lib/i386-linux-gnu/dri/r300_dri.so(+0x31fb4d) [0xb5ae8b4d] ()
ERROR: execute: Condition ' !f ' is true. returned: ERR_CANT_OPEN
   At: drivers/unix/os_unix.cpp:281.
[15] /usr/lib/i386-linux-gnu/dri/r300_dri.so(+0x1c5e9c) [0xb598ee9c] ()
ERROR: execute: Condition ' !f ' is true. returned: ERR_CANT_OPEN
   At: drivers/unix/os_unix.cpp:281.
[16] /usr/lib/i386-linux-gnu/dri/r300_dri.so(+0x18b6a9) [0xb59546a9] ()
ERROR: execute: Condition ' !f ' is true. returned: ERR_CANT_OPEN
   At: drivers/unix/os_unix.cpp:281.
[17] RasterizerStorageGLES2::sky_set_texture(RID, RID, int) ()
ERROR: execute: Condition ' !f ' is true. returned: ERR_CANT_OPEN
   At: drivers/unix/os_unix.cpp:281.
[18] VisualServerRaster::sky_set_texture(RID, RID, int) ()
ERROR: execute: Condition ' !f ' is true. returned: ERR_CANT_OPEN
   At: drivers/unix/os_unix.cpp:281.
[19] VisualServerWrapMT::sky_set_texture(RID, RID, int) ()
ERROR: execute: Condition ' !f ' is true. returned: ERR_CANT_OPEN
   At: drivers/unix/os_unix.cpp:281.
[20] ProceduralSky::_radiance_changed() ()
ERROR: execute: Condition ' !f ' is true. returned: ERR_CANT_OPEN
   At: drivers/unix/os_unix.cpp:281.
[21] ProceduralSky::_update_sky() ()
ERROR: execute: Condition ' !f ' is true. returned: ERR_CANT_OPEN
   At: drivers/unix/os_unix.cpp:281.
[22] MethodBind0<ProceduralSky>::call(Object*, Variant const**, int, Variant::CallError&) ()
ERROR: execute: Condition ' !f ' is true. returned: ERR_CANT_OPEN
   At: drivers/unix/os_unix.cpp:281.
[23] Object::call(StringName const&, Variant const**, int, Variant::CallError&) ()
ERROR: execute: Condition ' !f ' is true. returned: ERR_CANT_OPEN
   At: drivers/unix/os_unix.cpp:281.
[24] MessageQueue::_call_function(Object*, StringName const&, Variant const*, int, bool) ()
ERROR: execute: Condition ' !f ' is true. returned: ERR_CANT_OPEN
   At: drivers/unix/os_unix.cpp:281.
[25] MessageQueue::flush() ()
ERROR: execute: Condition ' !f ' is true. returned: ERR_CANT_OPEN
   At: drivers/unix/os_unix.cpp:281.
[26] SceneTree::iteration(float) ()
ERROR: execute: Condition ' !f ' is true. returned: ERR_CANT_OPEN
   At: drivers/unix/os_unix.cpp:281.
[27] Main::iteration() ()
ERROR: execute: Condition ' !f ' is true. returned: ERR_CANT_OPEN
   At: drivers/unix/os_unix.cpp:281.
[28] OS_X11::run() ()
ERROR: execute: Condition ' !f ' is true. returned: ERR_CANT_OPEN
   At: drivers/unix/os_unix.cpp:281.
[29] /media/prenex/Plan9(Outer Space)/godot31/bin/godot.x11.tools.32.llvm(main+0x12c) [0x8c8051c] ()
ERROR: execute: Condition ' !f ' is true. returned: ERR_CANT_OPEN
   At: drivers/unix/os_unix.cpp:281.
[30] /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf7) [0xb6efb637] ()
ERROR: execute: Condition ' !f ' is true. returned: ERR_CANT_OPEN
   At: drivers/unix/os_unix.cpp:281.
[31] /media/prenex/Plan9(Outer Space)/godot31/bin/godot.x11.tools.32.llvm() [0x8c8031b] ()
-- END OF BACKTRACE --
Aborted (core dumped)

Also I needed use_llvm=yes to build, otherwise gcc could not build the project because of some ordering issues... See below for the g++ build error messages.
prenex@ubuntu:/media/prenex/Plan9(Outer Space)/godot31$ scons platform=x11
scons: Reading SConscript files ...
Enabling ALSA
Enabling PulseAudio
YASM is necessary for WebM SIMD optimizations.
WebM SIMD optimizations are disabled. Check if your CPU architecture, CPU bits or platform are supported!
Checking for C header file mntent.h... (cached) yes
scons: done reading SConscript files.
scons: Building targets ...
[  5%] Compiling ==> main/main.cpp
[  6%] Linking Static Library ==> main/libmain.x11.tools.32.a
Ranlib Library         ==> main/libmain.x11.tools.32.a
[  6%] Linking Static Library ==> main/tests/libtests.x11.tools.32.a
Ranlib Library         ==> main/tests/libtests.x11.tools.32.a
[ 17%] Compiling ==> thirdparty/cvtt/ConvectionKernels.cpp
thirdparty/cvtt/ConvectionKernels.cpp: In member function 'void cvtt::Internal::IndexSelectorHDR<TVectorSize>::InitHDR(int, bool, bool, const float*)':
thirdparty/cvtt/ConvectionKernels.cpp:3157:32: error: 'MakeBoolInt16' is not a member of 'cvtt::ParallelMath'
                 m_isInverted = ParallelMath::MakeBoolInt16(false);
                                ^
thirdparty/cvtt/ConvectionKernels.cpp: In static member function 'static void cvtt::Internal::BC7Computer::TrySinglePlane(uint32_t, const MUInt15 (*)[4], const MFloat (*)[4], const float*, int, int, cvtt::Internal::BC7Computer::WorkInfo&, const cvtt::ParallelMath::RoundTowardNearestForScope*)':
thirdparty/cvtt/ConvectionKernels.cpp:3820:62: error: 'MakeBoolInt16' is not a member of 'cvtt::ParallelMath'
                 ParallelMath::Int16CompFlag isPunchThrough = ParallelMath::MakeBoolInt16(true);
                                                              ^
thirdparty/cvtt/ConvectionKernels.cpp:4047:58: error: 'MakeBoolInt16' is not a member of 'cvtt::ParallelMath'
                             punchThroughInvalid[pIter] = ParallelMath::MakeBoolInt16(false);
                                                          ^
thirdparty/cvtt/ConvectionKernels.cpp: In static member function 'static void cvtt::Internal::BC6HComputer::EvaluatePartitionedLegality(const MAInt16 (*)[3], const MAInt16 (*)[3], int, const int*, bool, cvtt::Internal::BC6HComputer::MAInt16 (*)[2][3], cvtt::ParallelMath::Int16CompFlag&)':
thirdparty/cvtt/ConvectionKernels.cpp:5315:56: error: 'MakeBoolInt16' is not a member of 'cvtt::ParallelMath'
                 ParallelMath::Int16CompFlag allLegal = ParallelMath::MakeBoolInt16(true);
                                                        ^
thirdparty/cvtt/ConvectionKernels.cpp: In static member function 'static void cvtt::Internal::BC6HComputer::EvaluateSingleLegality(const MAInt16 (*)[3], int, const int*, bool, cvtt::Internal::BC6HComputer::MAInt16 (*)[3], cvtt::ParallelMath::Int16CompFlag&)':
thirdparty/cvtt/ConvectionKernels.cpp:5356:56: error: 'MakeBoolInt16' is not a member of 'cvtt::ParallelMath'
                 ParallelMath::Int16CompFlag allLegal = ParallelMath::MakeBoolInt16(true);
                                                        ^
thirdparty/cvtt/ConvectionKernels.cpp: In static member function 'static void cvtt::Internal::BC6HComputer::Pack(uint32_t, const cvtt::PixelBlockF16*, uint8_t*, const float*, bool, int, int)':
thirdparty/cvtt/ConvectionKernels.cpp:5571:83: error: 'MakeBoolInt16' is not a member of 'cvtt::ParallelMath'
                                             ParallelMath::Int16CompFlag anySame = ParallelMath::MakeBoolInt16(false);
                                                                                ^
thirdparty/cvtt/ConvectionKernels.cpp:5577:84: error: 'MakeBoolInt16' is not a member of 'cvtt::ParallelMath'
                                                 ParallelMath::Int16CompFlag same = ParallelMath::MakeBoolInt16(true);
                                                                                ^
scons: *** [thirdparty/cvtt/ConvectionKernels.x11.tools.32.o] Error 1
scons: building terminated because of errors.

Still have the errors after building with the named fixes...
Version
db55d8a4b6ad6c14f2131e02b50689eb8380276f

Gdb backtrace (core)
This seems to be more helpful than the above backtrace as this has more line numbers in it. As far as I see the bug constantly happens in the point described by this stack trace (for the sky texture). I will see if I can fix this, but I am completely noob when it comes to your codebase :-). This would be the first try of your engine - except I installed 2.1 some days ago and tried very basic hello world in that.
The core file is 1.2Gb so I did not dare to upload here, but I can put it out to somewhere downloadable if some of you are interested - also just tell me what more info you want and I will try my best to tell so ;-)
I think Godot 3.1 will be great if it can work on my machine. Looks like a much better engine (for my liking) than others. The scene handling ideas seem to be great.
(gdb) bt
#0  0xb7775c31 in __kernel_vsyscall ()
#1  0xb6f4de89 in __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:54
#2  0xb6f4f3e7 in __GI_abort () at abort.c:89
#3  0x08c8302d in handle_crash (sig=11) at platform/x11/crash_handler_x11.cpp:113
#4  <signal handler called>
#5  0xb5d4cfd7 in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so
#6  0xb5d6385b in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so
#7  0xb5d5ab48 in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so
#8  0xb5d5b2b6 in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so
#9  0xb5d5645a in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so
#10 0xb5d56514 in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so
#11 0xb5d4fa23 in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so
#12 0xb5d3a3c5 in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so
#13 0xb5d3b316 in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so
#14 0xb5d476e3 in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so
#15 0xb5d3bf06 in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so
#16 0xb5d3de32 in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so
#17 0xb5b27b4d in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so
#18 0xb59cde9c in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so
#19 0xb59936a9 in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so
#20 0x09aed0fd in RasterizerStorageGLES2::sky_set_texture (this=0x103dadd0, p_sky=..., p_panorama=..., p_radiance_size=512)
    at drivers/gles2/rasterizer_storage_gles2.cpp:969
#21 0x0c6d622a in VisualServerRaster::sky_set_texture (this=0x102869b8, arg1=..., arg2=..., arg3=512)
    at servers/visual/visual_server_raster.h:183
#22 0x0c74fd58 in VisualServerWrapMT::sky_set_texture (this=0xb2b4a018, p1=..., p2=..., p3=512) at servers/visual/visual_server_wrap_mt.h:117
#23 0x0c0e89fd in ProceduralSky::_radiance_changed (this=0x10bc18d8) at scene/resources/sky_box.cpp:129
#24 0x0c0ec61d in ProceduralSky::_update_sky (this=0x10bc18d8) at scene/resources/sky_box.cpp:410
#25 0x0c0f6e8e in MethodBind0<ProceduralSky>::call (this=0x109ba460, p_object=0x10bc18d8, p_args=0x0, p_arg_count=0, r_error=...)
    at core/method_bind.gen.inc:137
#26 0x0d1816c6 in Object::call (this=0x10bc18d8, p_method=..., p_args=0x0, p_argcount=0, r_error=...) at core/object.cpp:968
#27 0x0d167440 in MessageQueue::_call_function (this=0x1025d5b8, p_target=0x10bc18d8, p_func=..., p_args=0xb64e3028, p_argcount=0,
    p_show_error=false) at core/message_queue.cpp:256
#28 0x0d16774d in MessageQueue::flush (this=0x1025d5b8) at core/message_queue.cpp:300
#29 0x0af3dc70 in SceneTree::iteration (this=0x10b5ea48, p_time=0,0166666675) at scene/main/scene_tree.cpp:476
#30 0x08cd5a84 in Main::iteration () at main/main.cpp:1773
#31 0x08c92f77 in OS_X11::run (this=0xbfbdd760) at platform/x11/os_x11.cpp:2695
#32 0x08c805ec in main (argc=4, argv=0xbfbddc44) at platform/x11/godot_x11.cpp:55

** RELEVANT INFO **
It seems that if I change the whole method to just "return" without doing anything, then I can start the editor. I did not try too many things, but I see the editor and can move the camera with my mouse.
Also I added a simple stderr log in this function that sets the sky texture and so far I see it is only called once and not many-many times, so it is really weird to have the memory depletion problem. I wonder what causes the issue.
Is this function rendering something to an offscreen frame buffer to do something for the sky (generate a sky texture)?
Also I still get the texture errors from:  drivers/gles2/rasterizer_gles2.cpp:111

Test results with the fake (no-op) sky-function
Actually things quite work if I exchange the sky-texture setter method with a no-operation. I tried to add an obj file and some textures as results and I can see them show up if I drag the obj into the scene add a material and set its main texture. I can click on "play" and see my little starship on screen - well textured. I have a camera,a light, the starship and a main spatial (3d) node that has all the other three below it. The material is a "spatial material" which seemed to be the default godot thingy. A slight user experience issue is that clicking play first crashed the newly starting app until I changed the GLES2 backend in its project settings, but that was not a big deal.
What was weird to me is that only basic texturing seemed to work: In any way I was positioning my light I always saw the object in the same way so it seems no lightning calculations are in effect. Maybe this is normal as I used all the defaults when creating the material so I thought I should (maybe) enable "vertex lightning" on the material, but when I clicked that I got the memory leak once again and the editor have crashed. The backtrace is the following one.
ERROR: _get_uniform: Condition ' !version ' is true. returned: -1
   At: drivers/gles2/shader_gles2.h:509.
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL	Type: Error	ID: 1	Severity: High	Message: GL_INVALID_VALUE in glGetProgramiv(program)
   At: drivers/gles2/rasterizer_gles2.cpp:111.
ERROR: alloc_static: Condition ' !mem ' is true. returned: __null
   At: core/os/memory.cpp:85.
ERROR: resize: Condition ' !ptr ' is true. returned: ERR_OUT_OF_MEMORY
   At: core/cowdata.h:262.
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL	Type: Error	ID: 1	Severity: High	Message: GL_INVALID_VALUE in glGetActiveUniform
   At: drivers/gles2/rasterizer_gles2.cpp:111.
ERROR: operator[]: FATAL: Index p_index=0 out of size (_parent->size()=0)
   At: core/vector.h:54.
handle_crash: Program crashed with signal 4
Dumping the backtrace.
-- END OF BACKTRACE --
Aborted (core dumped)

But at least some basic functionality works. Actually that is even more than I expected as I did not know the system can start on my machine! I am waiting for 3.1 because that supports older cards like I have and just got bored waiting and thought maybe it already "kind of works" if I get the latest git sources. I think godot has a big potential and other than the issues the whole editor works charming-fast on my decade old computer which is really awsome!!! I can imagine there are a lot of work now closing on the 3.1 version, so please not be offended by my results so far. I am just trying to give all the information I can readily provide and help in sorting out the things.
I know some opengl, but I do not feel so sure about that I can fix these issues on my own - surely not without help - but it seems if RasterizerStorageGLES2::sky_set_texture(...) could be fixed then people like me would be at least able to start the engine properly and do some basic stuff.
I guess 2D things would somewhat work. I tested 3D immediately just out of curiosity ;-)

Now as I read in the "spatial material" docs I kind of think I should see the effect of lights in the scene as per default setup without enabling "vertex lightning" flag as it is per-pixel the docs say:
http://docs.godotengine.org/en/3.0/tutorials/3d/spatial_material.html
I also read there about a "depth pre-pass". Maybe that is not working on my machine then and those are the error messages about the "GL_INVALID_OPERATION in glTexImage2D(bad target for depth texture)"? Those are mostly only coming on startup, so maybe the initialization of the depth prepass might be wrong too? I am just thinking. But first I think it would be good to fix the original main problem with the sky texture generation.

Anyone?

@prenex Someone will get to your issue eventually. Some issues take longer than others. :)
That being said, @karroffel I believe GLES2 is your domain?

@LikeLakers2 Thank you for your fast answer. I try not to be impatient, just I did fear a bit "what if they see there are many comments and not read the issue as everyone will think maybe already someone works on it" haha. Sorry. I am still happy that at least I can start the engine and see something on screen even though not everthing is completely well.
@karroffel I am not sure about the architecture but are the shaders always the very same or they get recompiled according to what features I use? I am asking because I have also spotted these kind of errors lately:
r300 FP: Compiler Error:
Too many constants. Max: 32, Got: 39
Using a dummy shader instead.
r300 FP: Compiler Error:
Too many constants. Max: 32, Got: 39
Using a dummy shader instead.
r300 FP: Compiler Error:
Too many constants. Max: 32, Got: 39
Using a dummy shader instead.
r300 FP: Compiler Error:
Too many constants. Max: 32, Got: 39
Using a dummy shader instead.
r300 FP: Compiler Error:
../../../../../src/gallium/drivers/r300/compiler/r300_fragprog_emit.c::emit_alu(): Too many ALU instructions
Using a dummy shader instead.
r300 FP: Compiler Error:
Too many constants. Max: 32, Got: 39
Using a dummy shader instead.

The r300_fragprog_emit.c one is coming very rarely (only one I saw so I pasted that), but the other seems to come both when I open the project and maybe when I mess with the material. It can be that it is only unlit because of this issue of the driver needing a "dummy shader instead". 32 constants does not seem to be too much and these messages seems to come from the driver, but maybe I can get the shader code somewhere and remove some parts I will never need? I mean...Maybe there is a way to get the otherwise used standard spatial material and copy its code into a shader-material so parameterization is nearly the same but fits into my limits or whatever... Just for testing...
Also I tried to turn off things in the shader to see what affects this usage number, but I could not change anything to affect it so far.

I see I can convert the standard stuff into a shader material according to this info:
http://docs.godotengine.org/en/latest/tutorials/shading/shader_materials.html
I don't see how is this being done and cannot find the menu item though :-(

Does anyone have the shader material corresponding to the main spatial-material?

When I write my own "shadermaterial" to only show the normals of the object or just simple color I see it is working and that must mean the shader runs - but I still get errors complaining there are 35-36 constants. I wonder how I can go below 32 but I also wonder to see the effect of my vertex and fragment shader despite this error message.


Create hmon.localplayer.dev.json

Description
Personal web proxy service. I create this for some of my friends and the domains often get blocked by their school administration so I like to just use random domains.
Link to Website
https://hmon.gives:8080

CLA Assistant Lite bot: 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 can sign the CLA by just posting a Pull Request Comment same as the below format.

I have read the CLA Document and I hereby sign the CLA

You can retrigger this bot by commenting recheck in this Pull Request

I have read the CLA Document and I hereby sign the CLA

Is the CNAME valid?

recheck


fix wrong error and hard coded json backend filepath

Fixes:
https://github.com/jonathaneeckhout/jdungeon/issues/85
Additional fix:
I've made it so that depending on what backend is chosen you require certain env variables.
How to test this fix:
Test 1:
Set your backend to "json" and modify the .env variable SERVER_JSON_BACKEND_FILE to a location you prefer and have write access to. When creating accounts and closing the client, all persistent data should be stored in the new location.
Test 2:
When you set the backend to "json" remove or comment out the following variables from the .env file:
POSTGRES_ADDRESS=<IP_ADDRESS>
POSTGRES_PORT=5432
POSTGRES_USER=testuser
POSTGRES_PASSWORD=testpassword
POSTGRES_DB=jdungeon

The server should start
Test 3:
When you set the backend to "postgres" remove or comment out the following variable from the .env file:
SERVER_JSON_BACKEND_FILE="data/users.json"

The server should start

In the meantime, conflicts in the example file most likely since I just added the mute thing.

In the meantime, conflicts in the example file most likely since I just added the mute thing.

fixed

👍


CI (Execute tests on the Verilated system) fails on timeout.

The test is consistently hit the timeout of 120 minute. This is most likely as a result of the por_ni derived resets behaviour change.
The CI include 35 test that 29 of them passes before the timeout reached. The reset delay need to be reduced to shorten the test time.
If the individual test time can not be reduce, the CI need to be split into more then one CI.
As a temporary bypass, the timeout need to be increased to 150-180 minutes.

@lowRISC/ot-dv-reviewers

@Jacob-Levy i'm having a look at the logs now, I think actually in your case most of the tests have passed.
As an example, the first test (mask_rom_epmp) passes, but on the second test, crt_test it immediately fails.  The tests afterwards fail, and if i'm reading it right, they don't appear to printing anything on uart or the console log (we usually have a log message that indicates rom / flash has been reached).
Usually we should see this line 128174: (../src/lowrisc_dv_sw_test_status_0/sw_test_status_if.sv:51) [TOP.chip_sim_tb.u_sw_test_status_if] SW test transitioned to SwTestStatusInBootRom, but i dont even see that in your logs right now.

Issue got resolved by PR 10437.

@Jacob-Levy to @rswarbrick point, I really should not jam your PR into that one. I had to include yours in there because I needed to check CI behavior.
I will remove your commit from mine and individually merge the top level fix.  Then we can review this PR standalone.

i will close this now since i think this problem is resolved.


Mobs

I'm having an issue where if the Magic Mobs go into unloaded-chunks their disguise dis-apears.
Not only that but the game no-longer reconizes them to be that mob
For example:
if i summon a Dark Wizard, i could remove it using /mmob clear Dark_Wizard.
However if i summon the Dark wizard and than run far away or relog, the skin has vanished (Showing the actual mob - Zombie Pigman.) But more importantly i am unable to get rid of the mob using commands (important since i am using command blocks to manage this)
i was wondering if there was a way to either set it so that the mobs despawn all together, or another work-around of sorts?
-PS- This plug-in is amazing, adds a whole unique aspect to a server.

I don't think there will be a work-around for this, it would be a LibsDisguise issue. Magic is also unable to track them across unloads.
Generally I am working towards making sure Magic Mobs despawn completely when they unload, though so far that does not look possible.


ldap: add tests for udp and frames

Ticket
If your pull request is related to a Suricata ticket, please provide
the full URL to the ticket here so this pull request can monitor
changes to the ticket status:
Redmine ticket:
https://redmine.openinfosecfoundation.org/issues/1199

Merged in #2003, thanks!


block quotes

Hi, thanks again for the hard work!
I am trying to do block quotes such as:

The problem is the line after the paragraph is always indented upon rendering. I probably just don't know what command to use for the following line, been trying to google but to no avail. Is there an easy way to make the line after a block quote left justified (no indent)?

Thanks for alerting me to this issue. I have added the ability to create paragraphs with no indenting. I demonstrated its use in the new template.qmd in the Block Quotation section. Basically, you enclose the paragraph in a div and give it a .NoIndent class:
:::{.NoIndent}
This paragraph will not be indented.
:::

Works great! Thank you for the prompt fix.

On Nov 10, 2023, at 06:24, W. Joel Schneider @.***> wrote:
Thanks for alerting me to this issue. I have added the ability to create paragraphs with no indenting. I demonstrated its use in the new template.qmd in the Block Quotation section. Basically, you enclose the paragraph in a div and give it a .NoIndent class:
:::{.NoIndent}
This paragraph will not be indented.
:::
—
Reply to this email directly, view it on GitHub https://github.com/wjschne/apaquarto/issues/21#issuecomment-1806036710, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF2IXWS3GXC2OOHZLTLHGJ3YDZIKRAVCNFSM6AAAAAA7GECKNSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBWGAZTMNZRGA.
You are receiving this because you authored the thread.

Glad it worked!


Save stakeholder choices

User choices for stakeholders need to be saved to db using endpoint for put request. This should be done in the conversation component.

Done


cmd/go2go: another parsing ambiguity

Consider the following code (playground):
type R(type T) struct{}
func F(type T)() {
     _ = func() R(T) { return R(T){} }
}

That is, we have some parameterized type R(T), and a function literal which returns that type R(T). (This is simplified from an example I found while writing generic composition with a result type.)
This currently fails with the following error message: prog.go:5:23: expected operand, found 'return' (the referenced location is indeed the return). (As an aside, this error message was pretty opaque -- not sure if improving that sort of thing is in-scope for the prototype.)
The issue appears to be a parsing ambiguity similar to the one described in the design draft, where func() R(T) has been interpreted as (func() R)(T). But the solution described there doesn't work: writing func() (R(T)) gets parsed as (and gofmted to) func() (R T). That is, it runs into another parsing ambiguity described in the draft. As a further workaround, I eventually realized to use func() (_ R(T)); from there things work fine.
Presumably the solution to the second parsing ambiguity could also work here, if applied to function returns; of course that expands the compatibility break described there.  Or, this could be documented similar to [](R(T)).
See also golang-nuts thread.

@griesemer @ianlancetaylor

To be clear, the workaround in full looks like:
type R(type T) struct{}
func F(type T)() {
	_ = func() (_ R(T)) { return R(T){} }
}

There's only one issue here, which is the ambiguity of instantiated (result) parameter types. As you say, this works.
In short, this is working as expected at the moment. I am going to close this as not a bug; but we are looking into changing the parsing here. This is obviously a very common issue for lots of people.


custom controls for an app bar and a rating bar

Hi,
I saw your great port of the Material Design for C# and WPF last weekend. However, I missed an easily reusable control for the app bar and a rating bar in the demo project. I will need them for a project of mine. Therefore I implemented them on my own and ask you to pull them into your original repository.
Thanks

Hi there...the AppBar looks great, but I don't really want to go down the route of having UserControls in the library.  My feeling is that UserControls typically sit at the application level, whereas this library is a bit more low level than that.  Having said that the XAML and code is clean, and I think you've created a great little example of the library in use.
Also am currently considering how I am going to add a "Drawer" control as this may have some relation with a possible dialogs implementation, as they both grey out underlying content.  Again this could affect the AppBar.

Regarding the RatingBar, I have a few suggestions:

Turn it into a custom control (derive from Control) with a default theme defined in Generic.xaml. This would bring it inline with the rest of the toolkit.
Make the number of stars/values a configurable int.  5 may be the most popular number, but we shouldn't limit it, other people will have other requirements.  Then, we might just populate an ItemsControl with sequential numbers, leading us onto:
Instead of having an Icon or PathData property, expose a RatingItemTemplate (DataTemplate) which would be much more "WPF-ish" and allow the user to use anything for each rating item.  We could set a default value in the Style in generic.xaml to https://materialdesignicons.com/icon/star-outline

If you want any clarification on this give me a shout.
Thanks,
James

Hi,
the dynamic and more customizable version of the RatingBar is working. It is a strange feeling to write an user interface (partly) in code, if you are used to write XAML and XHTML for years.
What is about the AppBar and the Drawer? I was already thinking about a Drawer implementation and possible integrations one week ago. Should I remove the AppBar from the branch or are you planning any integrations or migrations?
Philipp

Hi, yes...can you remove the AppBar please, we already have ToolBar themes, and the ColorZone which are flexible enough to build any menu/app bar the user desires.

I've made a few changes for the final version:

Used an ItemsControl as the template, this means we can rely on standard WPD layout mechanisms rather that generating Grid layout in the Control code.
Renamed primary properties to Min/Max/Value to bring in line with ProgressBar
Exposed templates and templates selector (and orientation) so it's more of a standard WPF mechanism to allow users to customise the control.
Exposes a routed command so users can really override everything should they desire

Doing the above makes this a more standard WPF control and allows better customisation in the XAML (instead of setting opacity in code for instance), allows us to run animations easier, and also exposes the actual value in each item (which can be seen in the demo).

I had a look on your changes of the rating bar and I noticed that the ripple effect is cut off by the control's edges. Seems to be an issue with the position of the buttons inside the control. The grid in the previous version filled the control and aligned the buttons in the center of the cells. The paddings might avoided the ripple to be cut off.
A funny rotation animation on the click event. Remembering the theory back in university, it might distract the user from the content. It's not such a big deal for a simple rating bar. I think that the users won't forget that they wanted to set a specific value. In my opinion, it could be a little bit more decent for the item. However that's just a subjective perception of mine.
Nevertheless the RatingBar have had a great evolution since the last changes.

I'm actually gonna change the animation, but the effect I want is a bit more complicated so will come back to it.


DNS-8918: DNS Firewall: rename origin_ips to upstream_ips

This field has been renamed for consistency.
I've renamed the Go field too, but if we want to avoid making a breaking change, we can find a different solution.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] This change is using publicly documented (api.cloudflare.com or developers.cloudflare.com) and stable APIs.

will the API response have a cut over phase where both values will be present? we can update the SDK here but i worry we may be leaving some folks behind on older versions if we don't.

Yes, that's the plan (at least 6 months)

@jacobbednarz, could you hit the merge button for me please? :pray:

Thanks :orange_heart:


Launch URL from Run

Ability to open a website in a choice of browsers after typing a URL, or at the very least, the default browser

Duplicate of #3245


See empty space on dragging the scrollbar

When your scrollbar is on top, try to drag it up with the mouse.
You'll see empty space

that is desired behavior, sort of a "bounce" effect.


Feature/interpolation adjoint

This implements a capability to do the adjoint of the interpolation in atlas where sparse matrices are used.
I have tested this with bi-linear on structured grid.

Hi @MarekWlasak
You should be able to create the matrix transpose in the setup(),
e.g. after this line: https://github.com/ecmwf/atlas/blob/develop/src/atlas/interpolation/method/Method.cc#L176
provided that the method is not matrix_free.

This has been merged in upstream PR ecmwf/atlas#72
The tolerance I had to adapt to 1.e-8 for double and 0.3 for float to pass all tests

@wdeconinck - thank you for the putting the PR upstream. @odlomax The adjoint tolerances that have been added are an absolute not a relative error.  That is the reason that they are so high.  I agree that the adjoint tolerances should be relative to the size of the total sum in the inner products. Is that something that I can add in a follow on PR?  Also, I have only added the adjoint capability when building the interpolation object using functionspaces. Is it worth adding that capability to the other constructors?

@MarekWlasak You're more than welcome to create more PRs that fine-tune your tests.
Getting it working with functionspaces was the crucial one. The other functions in principle only delegate to the one with function spaces. If something is obviously missing it will be easy to add, at a later point. Just make sure that you have what you need.

@MarekWlasak If you're happy that they're absolute errors, then I'm satisfied. Just checking it wasn't an oversight.

PR superceded by ecmwf  PR


Wallet simplification

removed unnecessary functions like clear, rm (YAGNI)
refactored to use array instead of object for accounts
improved wrong index detection
some bluebird callback refactorings

Pull Request Test Coverage Report for Build 1024

28 of 29 (96.55%)  changed or added relevant lines in 1 file are covered.
5 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-3.3%) to 76.306%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/Wallet/Wallet.ts
28
29
96.55%

Files with Coverage Reduction
New Missed Lines
%

src/EconomicStrategy/EconomicStrategyHelpers.ts
1
57.69%

src/Actions/Pending.ts
4
38.41%

Totals

Change from base Build 1016:
-3.3%

Covered Lines:
460

Relevant Lines:
573

💛  - Coveralls


Add Throbber host component

This component is rendered to UIActivityViewIndicator in TokamakUIKit. This component would be a great helper for future examples that demonstrate asynchronous effects, e.g. networking.

Codecov Report

Merging #71 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #71   +/-   ##
=======================================
  Coverage   95.05%   95.05%
=======================================
  Files           5        5
  Lines         384      384
=======================================
  Hits          365      365
  Misses         19       19

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 901e0f7...2bcf44e. Read the comment docs.


Ubuntu agents in Azure DevOps fail to run hooks from .sh script file even with chmod

[ ] Make sure you've installed the latest version using instructions in the wiki

Output from azd version
azd version 1.5.1 (commit 3856d1e98281683b8d112e222c0a7c7b3e148e96)
Describe the bug
/bin/sh: 1: ./hooks/RunDbMigrations.sh: Permission denied
ERROR: failed running post hooks: 'postprovision' hook failed with exit code: '126', Path: './hooks/RunDbMigrations.sh'. : exit code: 126, stdout: , stderr: /bin/sh: 1: ./hooks/RunDbMigrations.sh: Permission denied
To Reproduce
Write any hook as a .sh script file and include it with its relative path in azure.yaml, and run azd (command) from an Azure DevOps pipeline.
I have included chmod u+r+x '$(System.DefaultWorkingDirectory)\hooks\RunDbMigrations.sh' as the preceding command and this makes no difference. The same command runs fine on a Windows-2022 agent. Full step syntax:

task: AzureCLI@2
displayName: Azure CI Provision
inputs:
azureSubscription: $(AZURE_RESOURCE_MANAGER_CONNECTION)
scriptType: bash
scriptLocation: inlineScript
inlineScript: |
chmod u+r+x '$(System.DefaultWorkingDirectory)\hooks\RunDbMigrations.sh'
chmod +x '$(System.DefaultWorkingDirectory)\migrations\efbundle.exe'
azd provision --no-prompt --debug

(the hook runs the compiled result of EF core bundling to update a remote database, but removing it makes no difference)
Expected behavior
I expect that this is nothing specific to Azd and I'm just not understanding some aspect of the Linux permissions model as it pertains to pipelines, but I don't have anywhere else to ask. I expect the hook to just run, as it does locally on a Windows development environment.
Environment
Information on your environment:
* Language name and version
* IDE and version : [e.g. Visual Studio 16.3]
Additional context
Add any other context about the problem here.

@danieljurek can you triage this?

@TWolversonReply -- Is the $(System.DefaultWorkingDirectory)\migrations\efbundle.exe file a Windows-only executable?
Is there a reason AzureCLI@2 is being used to run this instead of script?

After some looking, using azd config set auth.useAzCliAuth "true", AzureCLI@2, and a service connection simplifies authentication and AzureCLI@2's script invocation isn't doing anything unexpected. It's fine to keep using it.
If you're still seeing failures with hooks when there's a Linux binary in place, let me know and we can continue investigating.
You mentioned that the build is done on Windows and provision is done on Linux. During the Windows build can you run the dotnet ef migrations bundle step with a --runtime parameter to produce a Linux binary?
https://learn.microsoft.com/en-us/ef/core/cli/dotnet#dotnet-ef-migrations-bundle
Runtime identifiers: https://learn.microsoft.com/en-us/dotnet/core/rid-catalog

@TWolversonReply -- Were you able to resolve the issue?


Case file related tables

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

Project coverage is 30.47%. Comparing base (07c83c4) to head (2e8a104).

Additional details and impacted files
@@             Coverage Diff             @@
##           develop      #17      +/-   ##
===========================================
- Coverage    33.01%   30.47%   -2.54%
===========================================
  Files           48       30      -18
  Lines          518      899     +381
  Branches       100        0     -100
===========================================
+ Hits           171      274     +103
- Misses         326      625     +299
+ Partials        21        0      -21

Flag
Coverage Δ

compliance-api
30.47% <100.00%> (?)

compliance-web
?

Flags with carried forward coverage won't be shown. Click here to find out more.

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


[NewPlugin]  matteyeux comments-viewer 1.0.0

Please add my plugin to the repository.
Yes, I've read the instructions, especially the part about creating an actual release and creating the tag.
I either used the UI, or the hub command to create a real release.
Author: matteyeux
Repo name: comments-viewer
Release: 1.0.0

added, thanks!


Define layouts in plugin (requires Eleventy v3.0.0)

See https://github.com/11ty/eleventy/issues/1612#issuecomment-2204420952
With virtual templates defined in the plugin, consumers no longer need to worry about configuring the path to the layouts folder in node_modules, and it should hopefully be easier to extend (instead of overwrite) plugin-provided layouts.

Good intro here: https://www.aleksandrhovhannisyan.com/blog/eleventy-virtual-templates/


fix: comment out serialization/deserialization of source locations

We were getting a deserialization error on the node when submitting a proven mint transaction:
cargo run --release --features testing,concurrent tx new mint 0x031cb9e685e6f6fa 0x29df14411f9b1667 20
    Finished release [optimized] target(s) in 0.11s
     Running `target/release/miden-client tx new mint 0x031cb9e685e6f6fa 0x29df14411f9b1667 20`
rpc api error: rpc request failed for submit_proven_transaction: status: InvalidArgument, message: "Invalid transaction", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "date": "Wed, 10 Apr 2024 03:56:04 GMT", "content-length": "0"} }

Particularly, the point of failure was when deserializing the AccountDetails of the ProvenTransaction. And more specifically when serializing the account's code during source locations' deserialization. We checked that by removing that serialization the error doesn't happen anymore and we were able to submit the mint transaction to the node. Perhaps a fix on miden-assembly is needed, but this at least unblocks us on the client side.
Steps to reproduce

clone the client and checkout to mFragaBA-add-account-details-endpoint
add these lines on submit_proven_transaction of src/client/transactions.rs:

+        let serialized_details = proven_transaction.account_details().to_bytes();
+
+        let _deserialized_details = <Option<AccountDetails>>::read_from_bytes(&serialized_details).expect("should be able to deserialize");

run the client, create a fungible faucet with cargo run --release --features testing,concurrent account new fungible-faucet --token-symbol BTC --decimals 10 --max-supply 10000 -s on-chain
create a regular onchain account with cargo run --release --features testing,concurrent account new basic-immutable -s on-chain
do a sync with cargo run --release --features testing,concurrent sync
list the created accounts with cargo run --release --features testing,concurrent account list
run a mint tx with cargo run --release --features testing,concurrent tx new mint <TARGET_ACCOUNT_ID_HEX> <FAUCET_ACCOUNT_ID_HEX> 33

Looks good! Thank you!
One question (possibly for a different PR): do we need to do the same thing for note script serialization?

To be honest I'm not sure. At least note serialization didn't give us trouble when testing on-chain accounts. I think eventually we shouldn't serialize them but provide an interface to override defaults if needed.

Doesn't seem like it's a problem on notes as @mFragaBA mentioned.


Settings ask me to restart while sync is initializing

have a setting that requires a restart
use settings sync
add another device
🤔 while sync'ing for the first time there, I am asked to restart and I don't know how well that ends

It seems you have a setting that needs VS Code restart is updated. Choosing to Restart will ask you to cancel / continue the settings sync.

/duplicate

https://github.com/microsoft/vscode/issues/122132


No such module 'Kingfisher' in macOS Catalyst

Check List
Thanks for considering to open an issue. Before you submit your issue, please confirm these boxes are checked.

[x] I have read the wiki page and cheat sheet, but there is no information I need.
[x] I have searched in existing issues, but did not find a same one.
[x] I want to report a problem instead of asking a question. It'd better to use kingfisher tag in Stack Overflow to ask a question.

Issue Description
What
Error message "No such module 'Kingfisher'" in Kingfisher-Demo - AVAssetImageGeneratorViewController.swift with macOS Catalyst

Reproduce
N/A
Other Comment
N/A

This is a tricky setting used to provide a "universal" framework in a single target. To make it build even in the sample project, please set the Base SDK to iOS. It explicitly specifies a base SDK to guide Kingfisher build on mac with iOS SDK (Catalyst).

Got it, thanks~~~


list; use flexbox for all the header items

The commit efccc73d179 introduced the usage of flexbox to properly align
the filter form. It also introduced a regression with mobile device.
The issue was due to a mixed usage of flexbox and floating div.
This commit add flexbox layout for the whole list header:

title
add filter/create/refresh buttons
filter form.

Some small changes are observed, the main one is the alignement of the
"Refresh" button on the right on mobile.
Closes: #754

Please use mui's autoprefixer when using flexbox, because of IE11 compatibility. See the example usage in Layout.js.

@fzaninotto it's done. But I'm not sure how to test it properly.

Looks pretty good to me. Thx !

This one would have been better merged on next... too late

I considered it a fix. Sorry :)


Use prepended modules instead of undef for OS-specific code

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[x] Have you successfully run brew tests with your changes locally?

Relates to https://github.com/Homebrew/brew/issues/17998
Switches from using undef, which results in (suppressed) sorbet errors, with prepended modules.
The latest proposal on the thread suggested creating an interface with three implementations, rather than using the generic-OS version in the default implementation, with methods undefined in OS-specific code. In building that out, I noticed that there wasn't a consistent, common interface among the OS variations, specifically in the case of Formula.
Thus, I've landed on OS extensions written as modules, which are then prepended to be used ahead of the generic implementations. (Note that in some cases, the modules are prepended to the singleton class, which admittedly gets pretty esoteric.)

This approach looks good and makes sense to me, nice work!
I wonder if there's any way to avoid the need for the require at the bottom of the existing class? That'd be nice if possible.

Yes, that would be very nice, but right now https://github.com/sorbet/sorbet/issues/5025 requires the prepend to come after the methods being replaced.

This seems to be causing an error at https://github.com/Homebrew/homebrew-core/pull/191090


Rename to @openzeppelin/contracts-ethereum-package

I'm opening this PR against a new @openzeppelin branch, since I'm not sure if we want to merge this into master right away. I don't see any reason not to though!

Not sure we want to merge into master yet since this includes links to repos that don't yet exist, to the old zos docsite, etc.

LGTM. I have no idea why the CI is failing, but it was failing before too. :slightly_smiling_face:
I'm contacting Travis support to migrate the repo to from travis-ci.org to travis-ci.com.

Not sure we want to merge into master yet since this includes links to repos that don't yet exist, to the old zos docsite, etc.

@nico I'd merge either way, so we ensure we keep working on the renamed version.


Adds RedisLock

Motivation
Mitchy saids 'There is no way to implement DistributedLock'. So I wanna add lock related commands as RedisLock.
https://twitter.com/mitchydeath/status/1100967088871489536

naming: Extend -> ExtendAsync

Although this library's naming policy is NOT to add Async suffix for async method, would you modify it?

Naming policy will be changed.
This PR is OK once.


Generic server support

For clients, we generate a generic interface / implementation that is agnostic to the protocol.
The actual protocol implementation is delegated to a "transport".
A similar concept can be applied to servers. We generate a generic interface for a server, and provide the protocol in "backend" packages.
Proof of concept:

generic server
adapter for @grpc/grpc-js, could be provided in package @protobuf-ts/grpc-backend

TODO

[x] come up with sensible method signatures
[x] adapter for unary
[x] adapter for server streaming
[x] adapter for client streaming
[x] adapter for bidi streaming
[x] check cancellation support
[x] test deadlines

[x] client-side, grpc-transport #77
[x] server-side, grpc-backend

[x] test error handling
[x] fix UnhandledPromiseRejectionWarning when cancelling client call, see client-cancel-test.ts
[x] generate generic server interfaces (proto-file-name.server.ts)
[x] add plugin parameter "server_generic"
[x] add server style GENERIC
[x] example package
[x] documentation (example-chat-system, MANUAL.md)

Released in v2.0.0-alpha.9

Updated in v2.0.0-alpha.10

Deadline cancellation on server through grpc-backend do not work correctly. Getting the same error about incomplete chunked encoding as in ngx-grpc/ngx-grpc#41

Running with generic servers as experimental.
Fixed the readme of @protobuf-ts/grpc-backend,  added the plugin option in the manual, added a very short section in the manual, making sure to note experimental status.


Add instrumentation to Django's db.connect() call

This is a really interesting metric to know since this is sometimes
cause of performance issues

duplicate of https://github.com/getsentry/sentry-python/pull/1250
closing


Remote Debugger attaches to multiple session

Issue Type: Bug
I have 2 remote debug sessions attached to different docker containers. One is attaching to port 9231 the other one attaching to port 9232. Configs are as follows:
"configurations": [
    {
        "name": "Attach to messaging on Ubuntu",
        "type": "node",
        "request": "attach",
        "port": 9231,
        "address": "localhost",
        "localRoot": "${workspaceFolder}",
        "remoteRoot": "/",
        "protocol": "inspector",
        "restart": true
    },
]

"configurations": [
    {
        "name": "Attach to chores on Ubuntu",
        "type": "node",
        "request": "attach",
        "port": 9232,
        "address": "localhost",
        "localRoot": "${workspaceFolder}",
        "remoteRoot": "/",
        "protocol": "inspector",
        "restart": true
    },
]

After I have upgraded from VS Code 1.44 to 1.60.2 it appears that the debuggers attach to all debugger sessions. When debugging one particular docker container the debugger switches between the debugger windows i.e is jumping from one window over to the other window even though the code is only executed in 1. Each window also provides outputs of all session with the debug console.
 The new debugger attaches to all child processes spawned by the parent by default, as you can see. If you're working on related code, you may want to add multiple folders to the workspace to have everything in one window.
Alternatively, you can disable attaching to child process by setting autoAttachChildProcesses: false in your launch config to keep the old behavior.

Hi Connor.
Thanks a lot for your response. Unfortunately the flag autoAttachChildProcesses does not work. Please see recording:
https://user-images.githubusercontent.com/12291453/137435242-dea1e887-4b2c-44f6-ad09-ec9e263d5b0e.mp4
Is there another setting I have to make?
Thanks, Nils


“editable” props in the InputField is not taking effect.

Description
I need to stop the keyboard from popping up in the InputField. While in RN TextInput, we can use "editable=false" to prevent the keyboard from popping up, this property doesn't work in InputField component.
CodeSandbox/Snack link
No response
Steps to reproduce

The keyboard still pops up even when “editable=false” is set.
gluestack-ui Version
@gluestack-ui/themed  v1.0.3
Platform

[X] Expo
[ ] React Native CLI
[ ] Next
[ ] Web
[X] Android
[ ] iOS

Other Platform
No response
Additional Information
I need to keep the input in a focused state, so I don’t want to use “isDisable=true” to prevent the keyboard from popping up.

Hey @Vvaraz, This issue has been fixed in latest version of @gluestack-ui/themed.


Vehicle created by "Supply drop" wouldn't be deleted after finishing the job

the Vehicle created by "Supply drop" called by JTAC wouldn't be deleted after finishing the job.
Only happend on dedicated Server

Support-link dependes on the original "support requester","support provider" modules used in this mission

Support-link dependes on the original "support requester","support provider" modules used in this mission

Any vehicle created by this moudle can’t be deleted after finishing the airdrop order
Only happend on dedicated Server

Sorry, completely forgot the mission had those modules! Personally I'm not the one that introduced them and I haven't done much research into how they function. If anything I'd rather these modules be reimplemented as SQF functions or dropped entirely, since I can't maintain those features otherwise.
I guess as a workaround, it might suffice to put a timer in that vehicle init field to despawn the vehicle and its crew after a few minutes.


isort 5.3.2 is not compatible with Python 2.7

See the test output here:
https://github.com/microsoft/vscode-python/runs/1008662413
Looks like isort 5.3.2 does not work with 2.7
Run python -m pip --disable-pip-version-check install -t ./pythonFiles/lib/python --no-cache-dir --implementation py --no-deps --upgrade -r requirements.txt
DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. pip 21.0 will drop support for Python 2.7 in January 2021. More details about Python 2 support in pip can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support
Collecting future==0.18.2
  Downloading future-0.18.2.tar.gz (829 kB)
ERROR: Could not find a version that satisfies the requirement isort==5.3.2 (from -r requirements.txt (line 10)) (from versions: 1.0.0, 1.0.1, 1.2.0, 1.2.2, 1.2.3, 1.2.5, 1.3.0, 1.3.1, 1.3.2, 2.0.0, 2.0.1, 2.1.0, 2.2.0, 2.2.1, 2.3.0, 2.4.0, 2.4.1, 2.5.0, 2.6.0, 2.6.1, 2.6.2, 2.6.3, 3.0.0, 3.1.0, 3.1.1, 3.1.2, 3.2.0, 3.3.0, 3.3.1, 3.4.0, 3.4.1, 3.4.2, 3.5.0, 3.6.0, 3.6.1, 3.6.2, 3.7.0, 3.7.1, 3.7.2, 3.8.0, 3.8.1, 3.8.2, 3.8.3, 3.9.0, 3.9.1, 3.9.2, 3.9.3, 3.9.4, 3.9.5, 3.9.6, 4.0.0, 4.1.0, 4.1.1, 4.1.2, 4.2.0, 4.2.1, 4.2.2, 4.2.3, 4.2.4, 4.2.5, 4.2.8, 4.2.9, 4.2.11, 4.2.12, 4.2.13, 4.2.14, 4.2.15, 4.3.0, 4.3.1, 4.3.2, 4.3.3, 4.3.4, 4.3.5, 4.3.6, 4.3.7, 4.3.8, 4.3.9, 4.3.10, 4.3.11, 4.3.12, 4.3.13, 4.3.14, 4.3.15, 4.3.16, 4.3.17, 4.3.18, 4.3.19, 4.3.20, 4.3.21)
ERROR: No matching distribution found for isort==5.3.2 (from -r requirements.txt (line 10))
##[error]Process completed with exit code 1.```

Fixed


CSI sidecar image version updates

Updates the CSI sidecar image versions to match those used by TopoLVM.

/cherry-pick release-4.12


Adding another scientist to the hall of fame.

I've added Mr. Dijkstra to the list of famous scientists. Please accept.
Thank you.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "master" git@github.com:michaelhuettermann/docker.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

LGTM

LGTM

Awesome!
Can you check this comment out and see if you can help?
https://github.com/docker/docker/pull/16405/files#diff-a461eecf31e5c471572678b08330893aR71


[IMPROVEMENT] results handlers also called for pushed line handlers

Some responses don't currently pass through ProtocolHandlerResultHandler, for instance the response to the base64 encoded identifiers after the SMTP AUTH PLAIN command (i.e. 235 or 535), because these responses are issued by a dynamically pushed LineHandler, so this MR adds a call to the result handlers in this case.

My use case was getting the result of UsersRepositoryAuthHook; after taking a second look, I noticed there was already the HookResultHook mecanism but it's partially implemented on AuthCmdHandler, so I created #2345.
About the data lines there is already DataLineFilter that seem to cover this use case, so indeed this PR is not needed, I'm closing it.


Update workflows

See https://github.com/senzing-garage/go-grpcing/issues/58

Pull requests:

https://github.com/senzing-garage/observe/pull/92


boards: arm: Add RAK4631 Wisblock Core LPWAN board

Add rak4631 board from RAKWireless based on nrf52840 and SX1262.
Board Documentation is completed
Signed-off-by: Guillaume Paquet<EMAIL_ADDRESS>

@gpaquet85 Out of curiosity. Did you test the lora and lorawan samples on this board?

@gpaquet85 Out of curiosity. Did you test the lora and lorawan samples on this board?

I just made some tests and I can see that there are some instabilities. I am waiting for schematics and I will fix it.
For my information, did you make some tries on SX126x ? If yes, what was your microC in front of tranceiver ?

@gpaquet85 Out of curiosity. Did you test the lora and lorawan samples on this board?

@Mani-Sadhasivam I corrected what you suggested.
Please let me knwo if it is ok for you.
For reference, LoRaWAN is not working yet. LoRa test looks ok.
I will investigate on it

@Mani-Sadhasivam sorry for late reply. It looks ok for me now

@Mani-Sadhasivam @sophiekovalevsky any more comments here?

@ioannisg LGTM.

@anangl done for me ;)


Breaks in A-Frame 7.0

Looks like this component doesn't work in A-Frame 7.0 because of the new .gltf loader!

Thanks for letting me know. I added A-Frame 7 support in https://github.com/archilogic-com/aframe-gblock/commit/2d2b09b3c944029519377b3454a06d7a99168f66
Pls let me know if you still encounter issues. I'm happy to fix it.


SignInManager.RefreshSignInAsync(inputuser) signs in current user instead of refreshing inputuser

Environment:

ASP.Net Core 2.1
Identity with EF

By my understanding RefreshSignInAsync can be used to refresh roles for an user after you have given it new roles. However, when I do, all it does is log the CURRENT_USER user in as the CHANGING_USER user.
Here is a simplified, but still bugging version of the code, with comments of debugging state
private readonly SignInManager<User> _signInManager;

public EditModel(SignInManager<User> signInManager)
{
    _signInManager = signInManager;
}

public async Task<IActionResult> OnPostAsync()
{
    //Debugging shows that the User.Identity.Name shows CURRENT_USER data.

    User changingUser = await _userManager.FindByIdAsync(InputUser.Id);
    // Debugging shows that changingUser shows CHANGING_USER data

    await _signInManager.RefreshSignInAsync(changingUser);
    return RedirectToPage("./Index");
}

On the redirect request I again check the debugging state to se which user data is present, and here the CHANGED_USER is now "logged in"
public async Task OnGetAsync()
{
    //Debugging shows that the User.Identity.Name now wrongly shows CHANGING_USER data.
}

The same happens with SignInManager.SignInAsync(dbUser, false, null);
Have I

Missunderstood RefreshSignInAsync/SignInAsync?
Or is this a straight up bug that happens for everyone?
Or do I have to provide more contextual information because its a specific problem with my project. If so, what can influence something this?

Sounds like you are misunderstanding how these work, Both SignIn/Refresh typically result in the user you pass in being the User.Identitiy.Name.  Refresh sign in just carries over the authentication mode claim from the currently signed in user.  And then signs in the user you pass in.

@HaoK : Hmm. Why does the RefreshSignInAsync() accept an ApplicationUser input then? If it just uses the User.Identitiy.Name anyway?

its the same thing as sign in basically, see https://github.com/aspnet/Identity/blob/dev/src/Identity/SignInManager.cs#L164

Hmm, I am sorry to be pushing this, but I am not convinced @HaoK : "The user to sign-in." and where the user derived princal.

The input user is documented in your code as the user that is being signed in.
Yes, it seems like some auth claim is also used further down the stack. I cant reach the final code that actual checks in, but I assume the Context.SignInAsync uses the current HttpContext or current auth to (wrongly?) sign in current user and not input user. Is this intended? Still not convinced due to the Input user and the method comment, which indicate that your intent of SignInAsync is to sign in input user.

It doesn't, it uses the claims principal you pass it

Ok. I give up. You dont take your time to address

Why it accepts a TUser object
Why it is documented like it is <param name="user">The user to sign-in.</param> ref

I have figured out a workaround for this lacking functionality, feel free to close the question.